From: Nick Sanders <sandersn@btinternet.com>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel Panic 2.5.39 when starting hotplug
Date: Wed, 2 Oct 2002 11:16:01 +0100 [thread overview]
Message-ID: <200210021116.02036.sandersn@btinternet.com> (raw)
In-Reply-To: <20021002015903.GA11453@kroah.com>
On Wednesday 02 October 2002 2:59 am, Greg KH wrote:
> On Wed, Oct 02, 2002 at 02:22:40AM +0100, Nick Sanders wrote:
> > Sorry about the last report not the most informative, I'm still getting a
> > kernel panic with 2.5.40. I think it's my Alcatel USB Speedtouch Modem as
> > it only panics when I plug it in.
>
> Are you using the new "in-kernel" driver for this device? Or the
> userspace driver? Hm, in looking at your .config, you're not using the
> kernel driver, any reason you aren't?
>
> And if you move usbmodules to something else (like usbmodules.orig), it
> will not be run by the hotplug code. Does that prevent the oops?
>
I used the kernel driver about 9 months ago but it wasn't reliable, the
userspace driver is brilliantly reliable and also I don't have to patch the
kernel, just looked at 2.5.40 and see it's in the kernel but I have been
using 2.4 till recently but there is still the speedmgmt application which
used to hang the machine on shutdown and also when the link was dropped and
you also need a ATM aware PPP daemon so the userpace driver is IMHO simpler
use.
Moving /usr/sbin/usbmodules to /usr/sbin/usbmodules.orig stops the kernel
panic, I get the following on boot
Starting hotplug subsystem: usb** can't synthesize root hub events.
Thanks
Nick
prev parent reply other threads:[~2002-10-02 10:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-28 12:24 Kernel Panic 2.5.39 when starting hotplug Nick Sanders
2002-09-28 12:36 ` jbradford
2002-09-28 18:55 ` Greg KH
2002-10-02 1:22 ` Nick Sanders
2002-10-02 1:59 ` Greg KH
2002-10-02 10:16 ` Nick Sanders [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=200210021116.02036.sandersn@btinternet.com \
--to=sandersn@btinternet.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 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).