linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Hotplug Oops Re: Linux v2.6.0-test1
Date: Tue, 15 Jul 2003 18:37:43 -0700	[thread overview]
Message-ID: <20030716013743.GA2112@kroah.com> (raw)
In-Reply-To: <20030716012948.GA1877@matchmail.com>

On Tue, Jul 15, 2003 at 06:29:48PM -0700, Mike Fedyk wrote:
> Here's a nice oops for you guys.
> 
> Hotplug is the trigger.  I can't reproduce without hotplug.
> 
> hotplug tries to load ohci, ehci, and finally uhci (the correct module), it
> oopses for each driver with hotplug, but if I try without hotplug ('apt-get
> remove hotplug' before rebooting), I can load all three usb drivers with no
> oops.

If you just load these drivers by hand, does the oops happen?

Can you enable debugging in the kobject code, or the driver base code to
try to get some better debug messages of what is going on?

thanks,

greg k-h

  reply	other threads:[~2003-07-16  1:22 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-14  3:59 Linux v2.6.0-test1 Linus Torvalds
2003-07-14 11:30 ` [trivial] " Jasper Spaans
2003-07-14 15:07 ` 2.6.0-test, how to test it? [Was: Linux v2.6.0-test1] Antonio Vargas
2003-07-14 20:08 ` Linux v2.6.0-test1 (compile stats) John Cherry
2003-07-15  4:11 ` Linux v2.6.0-test1 Matt Reppert
2003-07-15 10:56   ` Dave Jones
2003-07-15 17:38     ` Dominik Brodowski
2003-07-15 18:11       ` Dave Jones
2003-07-16  1:29 ` Hotplug Oops " Mike Fedyk
2003-07-16  1:37   ` Greg KH [this message]
2003-07-16  1:46     ` Mike Fedyk
2003-07-16  2:31       ` Greg KH
2003-07-16 20:15         ` Mike Fedyk
2003-07-16 20:26           ` Mike Fedyk
2003-07-18  2:31           ` Greg KH
2003-07-18 18:45             ` Mike Fedyk
2003-07-29 18:02             ` Mike Fedyk
2003-07-29 19:00               ` Mike Fedyk

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=20030716013743.GA2112@kroah.com \
    --to=greg@kroah.com \
    --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;
as well as URLs for NNTP newsgroup(s).