public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Greg KH <gregkh@suse.de>
Cc: Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org,
	linux-usb-devel@lists.sourceforge.net
Subject: Re: [GIT PATCH] USB patches for 2.6.17
Date: Thu, 22 Jun 2006 17:05:27 -0700	[thread overview]
Message-ID: <449B3047.50704@goop.org> (raw)
In-Reply-To: <20060622234040.GB30143@suse.de>

Greg KH wrote:
> I saw this once when debugging the usb code, but could never reproduce
> it, so I attributed it to an incomplete build at the time, as a reboot
> fixed it.
>
> Is this easy to trigger for you?
>   

This is the same oops as I posted yesterday: "2.6.17-mm1: oops in 
Bluetooth stuff, usbdev_open".  I haven't seen it since...

    J

  parent reply	other threads:[~2006-06-23  0:05 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-21 22:06 [GIT PATCH] USB patches for 2.6.17 Greg KH
2006-06-21 22:22 ` Linus Torvalds
2006-06-21 22:51   ` Greg KH
2006-06-22  0:51     ` Linus Torvalds
2006-06-22  1:22     ` Linus Torvalds
2006-06-22 18:18       ` Greg KH
2006-06-22 18:30         ` Greg KH
2006-06-22 18:49           ` Randy.Dunlap
2006-06-22 18:54             ` Greg KH
2006-06-23  5:52               ` Evgeniy Polyakov
2006-06-23  6:07                 ` Greg KH
2006-06-22 19:50           ` Linus Torvalds
2006-06-22 20:01             ` Sam Ravnborg
2006-06-22 20:52               ` Petr Baudis
2006-06-22 21:01               ` Linus Torvalds
2006-06-22 21:07                 ` Linus Torvalds
2006-06-22 23:11 ` Linus Torvalds
2006-06-22 23:40   ` Greg KH
2006-06-22 23:48     ` Linus Torvalds
2006-06-22 23:52       ` Greg KH
2006-06-23  0:32         ` Andrew Morton
2006-06-23  0:41           ` Greg KH
2006-06-23  0:05     ` Jeremy Fitzhardinge [this message]
2006-06-23  0:17       ` Andrew Morton
2006-06-23  0:22         ` Greg KH
2006-06-23  0:38           ` Greg KH
2006-06-23  0:56   ` Greg KH

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=449B3047.50704@goop.org \
    --to=jeremy@goop.org \
    --cc=akpm@osdl.org \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=torvalds@osdl.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