[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20081024221639.GA23702@kroah.com>
Date: Fri, 24 Oct 2008 15:16:39 -0700
From: Greg KH <greg@...ah.com>
To: Alan Stern <stern@...land.harvard.edu>
Cc: "Rafael J. Wysocki" <rjw@...k.pl>,
Folkert van Heusden <folkert@...heusden.com>,
Oliver Neukum <oliver@...kum.org>,
linux-kernel@...r.kernel.org, USB list <linux-usb@...r.kernel.org>
Subject: Re: [2.6.27-rc7] oops in usbcore
On Fri, Oct 24, 2008 at 06:13:03PM -0400, Alan Stern wrote:
> On Fri, 24 Oct 2008, Rafael J. Wysocki wrote:
>
> > On Thursday, 9 of October 2008, Folkert van Heusden wrote:
> > > > > lpc-ntpd is a atomic clock receiver driver doing read()-calls on an fd
> > > > > from a serial device (connected via usb), nothing fancy
> > > > > (http://vanheusden.com/lpc-ntpd/ ).
> > > >
> > > > Which devices? Please post lsusb -v
> > >
> > > thegate:/home/folkert# lsusb -v > lsusb
> > > cannot read device status, Broken pipe (32)
> > >
> > > Isn't that error odd?
> > >
> > > The output is:
>
> ...
>
> > > > But you do get this oops even without running that script, don't you?
> > >
> > > No, only with that script.
> >
> > Is this still reproducible in mainline?
> >
> > If not, is it reproducible with 2.6.27 final?
>
> I submitted a patch for this:
>
> http://marc.info/?l=linux-usb&m=122461735606713&w=2
>
> It hasn't been merged yet, in any tree.
I'm a bit hesitant to add it for .28, especially as this isn't a
"regression" per-say, but something that we have always done wrong, and
it changes the core USB code.
But, I can probably be convinced otherwise if needed :)
thanks,
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists