From: Mike Fedyk <mfedyk@matchmail.com>
To: Greg KH <greg@kroah.com>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Hotplug Oops Re: Linux v2.6.0-test1
Date: Fri, 18 Jul 2003 11:45:12 -0700 [thread overview]
Message-ID: <20030718184512.GD2289@matchmail.com> (raw)
In-Reply-To: <20030718023141.GC5828@kroah.com>
On Thu, Jul 17, 2003 at 07:31:41PM -0700, Greg KH wrote:
> On Wed, Jul 16, 2003 at 01:15:12PM -0700, Mike Fedyk wrote:
> > Ok, I only see it when the system is booting, and after looking at the
> > hotplug script in init.d there is different behaviour on boot, and on later
> > invocations.
>
> This is really wierd. I can't see anything strange in your logs, until
> the oops :)
It looks like it's a bug in the core code because when I was testing 2.5.70,
it was on a athlon XP pr2600, and the via-rhine module oopsed (because it
was started before the usb modules), and then it would hang.
I didn't report it because I wasn't able to capture the oops. :(
I'll do more to try to reproduce manually without the hotplug scripts.
(I'll bet it has something to do with one of the hotplug modules being
loaded).
Mike
next prev parent reply other threads:[~2003-07-18 18:30 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
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 [this message]
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=20030718184512.GD2289@matchmail.com \
--to=mfedyk@matchmail.com \
--cc=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 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.