From: Niraj Kumar <niraj17@iitbombay.org>
To: rusty@rustcorp.com.au, linux-kernel@vger.kernel.org
Subject: 2.6.1 : Kernel oops with rmmod
Date: Thu, 22 Jan 2004 17:08:53 +0530 [thread overview]
Message-ID: <400FB64D.2050806@iitbombay.org> (raw)
Hi ,
I am getting kernel oops after rmmod . I was doing some changes in ufs
filesystem
(basically , trying to add support for ufs2) and then loaded/unloaded
the ufs module.
Loading was fine. But rmmod crashed with "Segmentation fault" .
[root@indl195ec kernel]# rmmod -v ufs
rmmod ufs, wait=no
Segmentation fault
[niraj@indl195ec niraj]$ cat /proc/version
Linux version 2.6.1 (root@indl195ec) (gcc version 3.2.3 20030502 (Red
Hat Linux 3.2.3-20)) #2 Wed Jan 21 14:14:02 IST 2004
I am using the module-init-tools-3.0-pre7 .
The oops message is shown below (taken from dmesg):
Unable to handle kernel NULL pointer dereference at virtual address 00000000
printing eip:
00000000
*pde = 00000000
Oops: 0000 [#1]
CPU: 0
EIP: 0060:[<00000000>] Not tainted
EFLAGS: 00210246
EIP is at 0x0
eax: 00000000 ebx: f89dcd80 ecx: 00000000 edx: f89dcd80
esi: 00000000 edi: bffff8f0 ebp: eefec000 esp: eefedf68
ds: 007b es: 007b ss: 0068
Process rmmod (pid: 2037, threadinfo=eefec000 task=eefd46a0)
Stack: c0129df3 f89dcd80 bffff8f0 0000003b 00736675 00200086 f099e080
ca1cb1c6
00000033 4001a000 ca1cb1c6 00000033 f099e080 00083267 ca1cb867
00000033
eefd46a0 eefd4864 00000002 00000013 bffff8f0 bffff900 c010a7c1
bffff8f0
Call Trace:
[<c0129df3>] sys_delete_module+0x123/0x161
[<c010a7c1>] sysenter_past_esp+0x52/0x71
Code: Bad EIP value.
Niraj
next reply other threads:[~2004-01-22 11:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-22 11:38 Niraj Kumar [this message]
2004-01-22 12:34 ` 2.6.1 : Kernel oops with rmmod Rusty Russell
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=400FB64D.2050806@iitbombay.org \
--to=niraj17@iitbombay.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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