From: Greg KH <greg@kroah.com>
To: Richard Gooch <rgooch@ras.ucalgary.ca>
Cc: "Sandino Araico Sánchez" <sandino@sandino.net>,
linux-kernel@vger.kernel.org
Subject: Re: 2.4.17,2.4.18 ide-scsi+usb-storage+devfs Oops
Date: Wed, 6 Mar 2002 10:19:56 -0800 [thread overview]
Message-ID: <20020306181956.GC16003@kroah.com> (raw)
In-Reply-To: <3C7EA7CB.C36D0211@sandino.net> <20020302075847.GE20536@kroah.com> <3C84294C.AE1E8CE9@sandino.net> <200203060528.g265Sh502430@vindaloo.ras.ucalgary.ca> <20020306053355.GA13072@kroah.com> <200203060545.g265jwL02756@vindaloo.ras.ucalgary.ca>
In-Reply-To: <200203060545.g265jwL02756@vindaloo.ras.ucalgary.ca>
On Tue, Mar 05, 2002 at 10:45:58PM -0700, Richard Gooch wrote:
> Greg KH writes:
> > On Tue, Mar 05, 2002 at 10:28:43PM -0700, Richard Gooch wrote:
> > >
> > > I suspect the USB-UHCI driver is doing a double-unregister on a devfs
> > > entry. Please set CONFIG_DEVFS_DEBUG=y, recompile and boot the new
> > > kernel. Send the new Oops (passed through ksymoops, of course).
> >
> > None of the USB host controller drivers (like usb-uhci.c) call any
> > devfs functions.
>
> Well, usb-uhci was in the call trace. Perhaps ksymoops was being given
> bogus input?
I agree, with symbols like:
<[usb-uhci]__module_license+9099/fcd5>
it looks like this is the case.
thanks,
greg k-h
next prev parent reply other threads:[~2002-03-06 18:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-28 21:57 2.4.17,2.4.18 ide-scsi+usb-storage+devfs Oops Sandino Araico Sánchez
2002-03-02 7:58 ` Greg KH
2002-03-05 2:11 ` Sandino Araico Sánchez
2002-03-06 5:28 ` Richard Gooch
2002-03-06 5:33 ` Greg KH
2002-03-06 5:45 ` Richard Gooch
2002-03-06 18:19 ` Greg KH [this message]
2002-03-06 20:58 ` Sandino Araico Sánchez
2002-03-13 15:27 ` Juan Quintela
2002-04-04 0:52 ` Sandino Araico Sánchez
2002-04-04 16:14 ` Richard Gooch
2002-03-06 20:56 ` Sandino Araico Sánchez
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=20020306181956.GC16003@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rgooch@ras.ucalgary.ca \
--cc=sandino@sandino.net \
/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