From: Stephen Hemminger <shemminger@osdl.org>
To: "David S. Miller" <davem@redhat.com>
Cc: Kernel List <linux-kernel@vger.kernel.org>
Subject: 2.5.44 crash on reboot
Date: 21 Oct 2002 15:19:20 -0700 [thread overview]
Message-ID: <1035238760.1186.22.camel@dell_ss3.pdx.osdl.net> (raw)
The following happens on 2-way SMP box every time I reboot using
serial console. Not sure if it is a socket or inode problem but it looks
like a close race.
--------------------------------------------------------------------
Unable to handle kernel NULL pointer dereference at virtual address
00000000
printing eip:
c01b1a38
*pde = 00000000
Oops: 0000
ide-cd cdrom soundcore mga agpgart autofs nfs lockd sunrpc eepro100 mii
mousede
CPU: 0
EIP: 0060:[<c01b1a38>] Not tainted
EFLAGS: 00010246
EIP is at device_shutdown+0x78/0x9e
eax: ffffffff ebx: 00000000 ecx: c0392650 edx: 00000000
esi: 00000001 edi: ec3ee000 ebp: bffffdb8 esp: ec3efe8c
ds: 0068 es: 0068 ss: 0068
Process reboot (pid: 19350, threadinfo=ec3ee000 task=f01a6cc0)
Stack: c0299ffc 00000077 00000000 01234567 c0130ae2 c03f5bac 00000001
00000000
c01372f8 c19fd0d0 00000007 f0270d10 00001000 00000002 fffee334
f0270d10
f0270ce0 ec57b420 c01394f9 f0270ce0 eed08b40 420cdaf0 00000000
fffee334
Call Trace:
[<c0130ae2>] sys_reboot+0x182/0x380
[<c01372f8>] pte_alloc_map+0x128/0x140
[<c01394f9>] handle_mm_fault+0xb9/0x1c0
[<c0156f23>] invalidate_inode_buffers+0x13/0xc0
[<c022e65b>] sock_destroy_inode+0x1b/0xa0
[<c016f41a>] destroy_inode+0x6a/0x70
[<c01704fc>] generic_forget_inode+0x14c/0x180
[<c0276906>] inet_release+0x56/0x70
[<c01705ac>] iput+0x5c/0x80
[<c016cff0>] dput+0x30/0x200
[<c0155958>] __fput+0x108/0x140
[<c0152fd8>] filp_close+0xf8/0x130
[<c0153089>] sys_close+0x79/0x90
[<c0109a0f>] syscall_call+0x7/0xb
next reply other threads:[~2002-10-21 22:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-21 22:19 Stephen Hemminger [this message]
2002-10-21 22:31 ` Patrick Mochel
2002-10-21 22:39 ` Patrick Mochel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1035238760.1186.22.camel@dell_ss3.pdx.osdl.net \
--to=shemminger@osdl.org \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®