Bug 86003 - oops on shutdown
Summary: oops on shutdown
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kernel
Version: 7.3
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Arjan van de Ven
QA Contact: Brian Brock
Depends On:
TreeView+ depends on / blocked
Reported: 2003-03-12 02:26 UTC by Brian Brock
Modified: 2007-04-18 16:51 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2004-09-30 15:40:38 UTC

Attachments (Terms of Use)

Description Brian Brock 2003-03-12 02:26:01 UTC
oops in 2.4.18-26.7.xsmp

system was in mid-shutdown, last line was:

Shutting down FreeWnn:  Unable to handle kernel NULL pointer dereference [...]


unable to reproduce... had just updated glibc to latest erratum candidate and
oops occured on system shutdown, so attempting to recreate with another similar

Unable to handle kernel NULL pointer dereference at virtual address 0000033c
 printing eip:
*pde = 00000000
Oops: 0000
binfmt_misc nfs lockd sunrpc eepro100 usb_uhci usbcore ext3 jbd aic7xxx sd_mod
CPU:    0
EIP:    0010:[<c887fa55>]   Not tainted
EFLAGS: 00010293
EIP is at ext3_get_inode_loc [ext3] 0x25 (2.4.18-26.7.xsmp)
eax: fffffffe   ebx: 00000000   ecx: c5c03500   edx: 00000000
esi: c0f44c80   edi: c449be34   ebp: c5c03500   esp: c449bda8
ds: 0018   es: 0018   ss: 0018
Process jserver (pid: 1005, stackpage=c449b000)
Stack: 00000000 00000000 c0f44c80 c449be34 c5c03500
(apologies about missing the rest of it... hand copied oops appears incorrect
beyond that portion of the stack trace.  interrupts did not appear disabled,
however magic sysrq keys weren't on.  )

system needed a manual fsck on reboot, after another shutdown and reboot, all
appears well.

Comment 1 Bugzilla owner 2004-09-30 15:40:38 UTC
Thanks for the bug report. However, Red Hat no longer maintains this version of
the product. Please upgrade to the latest version and open a new bug if the problem

The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases, 
and if you believe this bug is interesting to them, please report the problem in
the bug tracker at: http://bugzilla.fedora.us/

Note You need to log in before you can comment on or make changes to this bug.