Hi, admins.
I asked:
>I am the administrator of a (somewhat :-) old alpha (DEC 2000 AXP 300),
>running DU 4.0d with patch kit 2 applied.
>
>A few minutes ago it paniced. uerf says:
>
>----- EVENT INFORMATION -----
>
>EVENT CLASS ERROR EVENT
>OS EVENT TYPE 302. PANIC
>SEQUENCE NUMBER 1.
>OPERATING SYSTEM DEC OSF/1
>OCCURRED/LOGGED ON Wed Oct 14 11:56:02 1998
>OCCURRED ON SYSTEM haddock
>SYSTEM ID x00020006 CPU TYPE: DEC 2000
>SYSTYPE x00000000
>MESSAGE panic (cpu 0): Unaligned kernel space
> _access from kernel mode
>
>and the kern syslog says:
>
>Oct 14 11:57:09 haddock vmunix: Unaligned kernel access va=0xfffffc0002e7a487
> pc=0xfffffc000037a0b4 ra=0xfffffc000037a414 inst=0xffffffff
>Oct 14 11:57:09 haddock vmunix: panic (cpu 0): Unaligned kernel space access
> from kernel mode
>Oct 14 11:57:09 haddock vmunix: syncing disks... 50 12 done
>
>(the two first lines are splitted for readability)
>
>Does anyone know any possible cause? The machine hadn't paniced since the
>DU 2.0 days.
Thanks to:
Bill Antoniadis <sysadmin_at_horseracinginfo.com>
"Dr. Tom Blinn, 603-884-0646" <tpb_at_doctor.zk3.dec.com>
"Alan Rollow - Dr. File System's Home for Wayward Inodes."
<alan_at_nabeth.cxo.dec.com>
Bruce Kelly <kellybe_at_llnl.gov>
(see their replies at the end of the message)
Looking at the crash dump files (specially /var/adm/crash/crash-data.0)
I've seen that the panic came from netisr_thread() in module
src/kernel/net/netisr.c, so it seems to be network related. Before the
crash, the machine was up (except some manteinance stops) for some months,
so I suppose that the error was caused by a very unusual situation, and I
have no idea on how to reproduce it.
I don't think that the error is the same as Bill's, because my machine was
not so busy and it has only one processor.
Anyway, I have the crash dump files available if someone at Compaq/Digital
wishes to have a look at them.
The original responses follow:
====================================================================
From: Bill Antoniadis <sysadmin_at_horseracinginfo.com>
To: "Pedro J. Lobo" <pjlobo_at_euitt.upm.es>
Subject: Re: Panic: unaligned acces from kernel mode
Pedro,
I had the same error on my 2100 with two processors and found out that
it was an error that rarely occurs with a VERY busy machine that has 2 or
more processors. I found this info from Digital Unix's Web Site. It's never
happened to me again. You may want to call the Support Line to confirm what
I'm saying.
Regards,
Bill Antoniadis
=====================================================================
From: "Dr. Tom Blinn, 603-884-0646" <tpb_at_doctor.zk3.dec.com>
To: "Pedro J. Lobo" <pjlobo_at_euitt.upm.es>
Subject: Re: Panic: unaligned acces from kernel mode
The log messages aren't particularly useful. Once the system reboots, in
/var/adm/crash you should find a crash dump and an analysis file produced
automatically by the system software. The "crash-data" file has output from
looking at the crash dump with dbx. The problem that occurred is probably
due to a software bug, although an uncommon hardware event might be what got
the kernel to the software where it failed. The crash data can usually be
used to figure out just where the system failed.
I personally still run V3.2G on my primary system, because it has proven to
be extremely reliable (I usually only reboot when the power fails, not due
to software faults). The V4.0D release has a number of new features that
may not have been tested as thoroughly as we would have liked, and you may
have tripped over one of them.
If you have a service contract that covers the system software, then get in
touch with your support center and ask them to look at the crash data.
Since you've got the "up to date" patches, there's not much more that I can
suggest.
Tom
Dr. Thomas P. Blinn + UNIX Software Group + Compaq Computer Corporation
110 Spit Brook Road, MS ZKO3-2/U20 Nashua, New Hampshire 03062-2698
Technology Partnership Engineering Phone: (603) 884-0646
Internet: tpb_at_zk3.dec.com Digital's Easynet: alpha::tpb
ACM Member: tpblinn_at_acm.org PC_at_Home: tom_at_felines.mv.net
Worry kills more people than work because more people worry than work.
Keep your stick on the ice. -- Steve Smith ("Red Green")
My favorite palindrome is: Satan, oscillate my metallic sonatas.
-- Phil Agre, pagre_at_ucsd.edu
Yesterday it worked / Today it is not working / UNIX is like that
-- apologies to Margaret Segall
Opinions expressed herein are my own, and do not necessarily represent
those of my employer or anyone else, living or dead, real or imagined.
=======================================================================
From: "Alan Rollow - Dr. File System's Home for Wayward Inodes."
<alan_at_nabeth.cxo.dec.com>
To: pjlobo_at_euitt.upm.es
Subject: Re: Panic: unaligned acces from kernel mode
Look at the crash dump listing to see which driver caused the
crash. Then contact our Multi-vendor Customer Services to
see if they have a patch for the particular problem. There's
not enough information in the console listing to even guess
at the cause.
=======================================================================
From: Bruce Kelly <kellybe_at_llnl.gov>
To: "Pedro J. Lobo" <pjlobo_at_euitt.upm.es>
Subject: Re: Panic: unaligned acces from kernel mode
DEC has a patch for this that envolves replacing vfs.mod and vm.mod. They
say this patch is working for everyone but us.
Bruce Kelly
Bruce Kelly PO Box 808, Livermore, CA 94451
510-423-0640 L-73, Computer Systems Group
fax 510-422-9429 Lawrence Livermore National Laboratory
kellybe_at_llnl.gov University of California
=======================================================================
-------------------------------------------------------------------
Pedro José Lobo Perea Tel: +34 91 336 78 19
Centro de Cálculo Fax: +34 91 331 92 29
EUIT Telecomunicación - UPM e-mail: pjlobo_at_euitt.upm.es
Received on Fri Oct 16 1998 - 08:28:07 NZDT