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 22:59:24 -0800 [thread overview]
Message-ID: <1040281164.1709.5.camel@ixodes.goop.org> (raw)
In-Reply-To: <20021219063839.40F322C080@lists.samba.org>
On Wed, 2002-12-18 at 21:55, Rusty Russell wrote:
> Yes, it would be a problem. But I don't think that's the problem
> here, and I don't think it can actually happen (it's a pretty insane
> idea).
>
> BTW, I can't reproduce your problem, maybe because I can't unload
> parport_pc here:
>
> Module parport cannot be unloaded due to unsafe usage in drivers/parport/init.c:234
> Module parport_pc cannot be unloaded due to unsafe usage in drivers/parport/parport_pc.c:1239
Well, I don't have any problem unloading it. It doesn't show any
messages or other warnings. It also doesn't crash any more, so I'm not
sure what's happening...
J
prev parent reply other threads:[~2002-12-19 6:51 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
2002-12-19 4:19 ` Jeremy Fitzhardinge
2002-12-19 5:55 ` Rusty Russell
2002-12-19 6:59 ` Jeremy Fitzhardinge [this message]
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=1040281164.1709.5.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.