From: Rusty Russell <rusty@rustcorp.com.au>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: modules oops in 2.5.52
Date: Thu, 19 Dec 2002 13:11:21 +1100 [thread overview]
Message-ID: <20021219024313.759EC2C075@lists.samba.org> (raw)
In-Reply-To: Your message of "18 Dec 2002 17:14:05 -0800." <1040260444.1316.4.camel@ixodes.goop.org>
In message <1040260444.1316.4.camel@ixodes.goop.org> you write:
> Hi,
>
> I just had an oops in the modules code:
>
> Dec 18 16:58:59 ixodes kernel: Unable to handle kernel paging request at virt
ual address f8980924
> Dec 18 16:58:59 ixodes kernel: printing eip:
> Dec 18 16:58:59 ixodes kernel: f896756d
> Dec 18 16:58:59 ixodes kernel: *pde = 01bfc067
> Dec 18 16:58:59 ixodes kernel: *pte = 00000000
> Dec 18 16:58:59 ixodes kernel: Oops: 0000
> Dec 18 16:58:59 ixodes kernel: CPU: 0
> Dec 18 16:58:59 ixodes kernel: EIP: 0060:[<f896756d>] Not tainted
> Dec 18 16:58:59 ixodes kernel: EFLAGS: 00010282
> Dec 18 16:58:59 ixodes kernel: EIP is at __exitfn+0xd/0x4c [parport_pc]
Actually, you had an oops in the parport_pc code, in
cleanup_module(). Now, *why* that oopsed, I don't know...
> Now, any process which touches /proc/modules hangs, I guess because a
> lock was being held.
Yes. Changing this would be particularly interesting, since you don't
want a simultaneous "modprobe" to fail.
Rusty.
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
next prev parent reply other threads:[~2002-12-19 2:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-19 1:14 modules oops in 2.5.52 Jeremy Fitzhardinge
2002-12-19 2:11 ` Rusty Russell [this message]
2002-12-19 4:19 ` Jeremy Fitzhardinge
2002-12-19 5:55 ` Rusty Russell
2002-12-19 6:59 ` Jeremy Fitzhardinge
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=20021219024313.759EC2C075@lists.samba.org \
--to=rusty@rustcorp.com.au \
--cc=jeremy@goop.org \
--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