From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: modules oops in 2.5.52
Date: 18 Dec 2002 20:19:09 -0800 [thread overview]
Message-ID: <1040271549.1317.12.camel@ixodes.goop.org> (raw)
In-Reply-To: <20021219024313.759EC2C075@lists.samba.org>
On Wed, 2002-12-18 at 18:11, Rusty Russell wrote:
> 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...
It looks like it might end up calling request_module() from within
cleanup_module(). Is that going to be a problem?
J
next prev parent reply other threads:[~2002-12-19 4:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-19 1:14 Jeremy Fitzhardinge
2002-12-19 2:11 ` Rusty Russell
2002-12-19 4:19 ` Jeremy Fitzhardinge [this message]
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=1040271549.1317.12.camel@ixodes.goop.org \
--to=jeremy@goop.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
Powered by JetHome