public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
	Folkert van Heusden <folkert@vanheusden.com>,
	Oliver Neukum <oliver@neukum.org>,
	linux-kernel@vger.kernel.org,
	USB list <linux-usb@vger.kernel.org>
Subject: Re: [2.6.27-rc7] oops in usbcore
Date: Fri, 24 Oct 2008 15:16:39 -0700	[thread overview]
Message-ID: <20081024221639.GA23702@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0810241809110.2180-100000@iolanthe.rowland.org>

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

  reply	other threads:[~2008-10-24 22:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-09  8:29 [2.6.27-rc7] oops in usbcore Folkert van Heusden
2008-10-09  8:33 ` Oliver Neukum
2008-10-09  8:42   ` Folkert van Heusden
2008-10-24 21:53     ` Rafael J. Wysocki
2008-10-24 22:13       ` Alan Stern
2008-10-24 22:16         ` Greg KH [this message]
2008-10-25 11:26           ` Rafael J. Wysocki

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=20081024221639.GA23702@kroah.com \
    --to=greg@kroah.com \
    --cc=folkert@vanheusden.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=oliver@neukum.org \
    --cc=rjw@sisk.pl \
    --cc=stern@rowland.harvard.edu \
    /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