From: Greg KH <greg@kroah.com>
To: Kyle Rose <krose+linux-kernel@krose.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Oops during USB unloading, 2.6.0-test{4,5}. sysfs?
Date: Fri, 12 Sep 2003 12:16:05 -0700 [thread overview]
Message-ID: <20030912191605.GA19628@kroah.com> (raw)
In-Reply-To: <87he3hg8vb.fsf@nausicaa.krose.org>
On Fri, Sep 12, 2003 at 02:27:36PM -0400, Kyle Rose wrote:
> In both test4 and test5, I get the following panic when I attempt to
> do a clean shutdown. It happens every time. The problem may be in
> the sysfs code given where the trace begins. The error message given
> before reboot was that the kernel couldn't handle a NULL pointer
> dereference, but for some reason, that didn't make it into
> /var/log/messages.
>
> BTW, if I'm not giving you guys enough interesting information about
> these problems, please let me know. There's no such thing as too much
> information. :) I can also recompile with frame pointers, if that will
> help.
Do you have the same error if you only unload the ohci-hcd and ehci-hcd
modules?
thanks,
greg k-h
prev parent reply other threads:[~2003-09-12 19:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-12 18:27 Oops during USB unloading, 2.6.0-test{4,5}. sysfs? Kyle Rose
2003-09-12 19:16 ` Greg KH [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=20030912191605.GA19628@kroah.com \
--to=greg@kroah.com \
--cc=krose+linux-kernel@krose.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