From: Iain Barker (ibarker@aastra.com)
Date: Thu Jun 30 2005 - 16:01:36 EDT
I was asked to provide additional information regarding the background, cause and the fix for this problem. Here's what I received from HP:
This issue has been identified and is scheduled to be resolved in patch, IN7 v4.1-5 P11
P11 may not be out for a while and does not have a release schedule. IN7 Engineering will be waiting for other fixes, etc, before even marking up a schedule for P11. My advise would be to continue deployment, since the Panic/Crash issue is recoverable and only occurs during upgrades.
-----Original Message-----
From: tru64-unix-managers-owner@ornl.gov
[mailto:tru64-unix-managers-owner@ornl.gov]On Behalf Of Iain Barker
Sent: Thursday, 09 June, 2005 11:02
To: tru64-unix-managers@ornl.gov
Subject: SUMMARY: Kernel panic during shutdown/reboot with Tru64 5.1b-3
(PK5)
Helpful suggestions received from:
Dr. Tom Blinn
Christian Klein
David (davegu1@...)
Johan Brusche
Roberto Mackun
Dr. Kieran Lynch
After a lot of in-depth analysis and debugging from Dr.Tom Blinn
and Christian Klein at HP, I managed to isolate the problem to a
device driver (dnb.mod) used for the HP DNBE1-BQ interface card.
Looks like the driver doesn't unload correctly from Tru64 5.1b-3
and causes the corruption within the kernel stack for adjacent
drivers in memory (in our case, AdvFS and the ace console driver).
Fortunatly the problem only seems to occur when the driver is being
unloaded, so the problem doesn't cause any ongoing stability issue.
thanks again for your help.
-----Original Message-----
From: tru64-unix-managers-owner@ornl.gov
[mailto:tru64-unix-managers-owner@ornl.gov]On Behalf Of Iain Barker
Sent: Monday, 06 June, 2005 14:46
To: tru64-unix-managers@ornl.gov
Subject: Kernel panic during shutdown/reboot with Tru64 5.1b-3 (PK5)
Hi Managers,
Has anyone experienced kernel panics during shutdown/reboot when using the latest Tru64 5.1b-3 (pk5) ?
It doesn't seem to be related to the actual PK5 installation operation and doesn't impact system stability, the panic seems to occurs later when the system is subsequently shut down (shutdown -h now) or during a scheduled reboot.
thanks.
Shutdown at 19:07 (in 0 minutes) [pid 8052]
System shutdown time has arrived
/proc: Invalid argument
Rebooting . . .
trap: invalid memory read access from kernel mode
faulting virtual address: 0x000000010000000c
pc of faulting instruction: 0xffffffff000ddb94
ra contents at time of fault: 0xffffffff000ddb94
sp contents at time of fault: 0xfffffe0450737690
panic (cpu 0): kernel memory fault
syncing disks... done
DUMP: blocks available: 12000000
DUMP: blocks wanted: 115682 (partial compressed dump) [OKAY]
DUMP: Device Disk Blocks Available
DUMP: ------ ---------------------
DUMP: 0x1300007 9004095 - 11999997 (of 11999998) [primary swap]
DUMP.prom: Open: dev 0x5100003, block 4004096: SCSI 0 8 0 0 0 0 0
DUMP: Writing header... [1024 bytes at dev 0x1300007, block 11999998]
DUMP: Writing data........ [8MB]
DUMP: Writing header... [1024 bytes at dev 0x1300007, block 11999998]
DUMP: crash dump complete.
halted CPU 0
halt code = 5
HALT instruction executed
PC = ffffffff0048be30
CPU 0 booting
resetting all I/O buses
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:50:20 EDT