From: paterley <paterley@DrunkenCodePoets.com>
To: paterley <paterley@DrunkenCodePoets.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.74-mm2
Date: Sat, 5 Jul 2003 18:23:59 -0400 [thread overview]
Message-ID: <20030705182359.269b404d.paterley@DrunkenCodePoets.com> (raw)
In-Reply-To: <20030705175830.4ccfead8.paterley@DrunkenCodePoets.com>
[-- Attachment #1: Type: text/plain, Size: 488 bytes --]
ok, I get 4 of a kernel oops during boot, but the kernel seems to stay happy. I'm going to keep it going for fun to see if I can cause more oopses. Attached is the first of the 4 oopses.
according to dmesg, immediately prior to the first oops, smbfs was unloaded due to unsafe usage.
Exact Error:
Module smbfs cannot be unloaded due to unsafe usage in include/linux/module.h:482
I'll be around for a few more hours if there is anything I can do to help answer questions.
Pat Erley
[-- Attachment #2: debug.log --]
[-- Type: application/octet-stream, Size: 867 bytes --]
Unable to handle kernel NULL pointer dereference at virtual address 00000000
printing eip:
00000000
*pde = 00000000
Oops: 0000 [#1]
SMP
CPU: 0
EIP: 0060:[<00000000>] Not tainted VLI
EFLAGS: 00010286
EIP is at 0x0
eax: c0380c20 ebx: fffffff4 ecx: cf07d3a0 edx: cc847f68
esi: cf3c2950 edi: cf07d2c0 ebp: cc847f18 esp: cc847efc
ds: 007b es: 007b ss: 0068
Process rc (pid: 1198, threadinfo=cc846000 task=cfd866b0)
Stack: c01637ab cf3c2950 cf07d2c0 cc847f68 cf3c29c0 cf3c2950 cc847f68 cc847f50
c0163ff7 cc847f70 cf07d380 cc847f68 cc847f40 cc847f70 00000001 cf07d380
00000002 cfa28f00 00008241 00008241 cfd9a000 cc847f9c c0153751 cfd9a000
Call Trace:
[<c01637ab>] __lookup_hash+0x9b/0xd0
[<c0163ff7>] open_namei+0x2e7/0x420
[<c0153751>] filp_open+0x41/0x70
[<c0153bd3>] sys_open+0x53/0x90
[<c010945f>] syscall_call+0x7/0xb
next prev parent reply other threads:[~2003-07-05 22:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-05 20:25 2.5.74-mm2 Andrew Morton
2003-07-05 21:58 ` 2.5.74-mm2 paterley
2003-07-05 22:23 ` paterley [this message]
2003-07-05 23:04 ` 2.5.74-mm2 Andrew Morton
2003-07-06 0:01 ` 2.5.74-mm2 paterley
2003-07-06 0:49 ` 2.5.74-mm2 Andrew Morton
2003-07-06 1:40 ` 2.5.74-mm2 [kernel BUG at include/linux/list.h:148!] Ramón Rey Vicente
2003-07-06 13:49 ` Nick Orlov
2003-07-08 0:43 ` Mike Fedyk
2003-07-08 23:17 ` Ramón Rey Vicente
2003-07-09 0:18 ` Mike Fedyk
2003-07-09 0:32 ` Ramón Rey Vicente
2003-07-09 0:34 ` Mike Fedyk
2003-07-09 0:44 ` Ramón Rey Vicente
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=20030705182359.269b404d.paterley@DrunkenCodePoets.com \
--to=paterley@drunkencodepoets.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