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: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	marcel@holtmann.org, maxk@qualcomm.com,
	Andrew Morton <akpm@osdl.org>,
	bluez-devel@lists.sourceforge.net
Subject: Re: 2.6.17-mm1: oops in Bluetooth stuff, usbdev_open
Date: Wed, 21 Jun 2006 14:21:49 -0700	[thread overview]
Message-ID: <4499B86D.8010700@goop.org> (raw)
In-Reply-To: <20060621204725.GB30766@suse.de>

Greg KH wrote:
> Can you duplicate this without the closed source kernel module loaded?
>   
Annoyingly not.  I doubt the ath_hal module caused a problem in itself, 
but there might have been a compilation-skew with the out-of-tree 
madwifi driver.

Or its a race which only happens sometimes.  I'll keep an eye out.

    J

      reply	other threads:[~2006-06-21 21:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-21 20:36 2.6.17-mm1: oops in Bluetooth stuff, usbdev_open Jeremy Fitzhardinge
2006-06-21 20:47 ` Greg KH
2006-06-21 21:21   ` Jeremy Fitzhardinge [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=4499B86D.8010700@goop.org \
    --to=jeremy@goop.org \
    --cc=akpm@osdl.org \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcel@holtmann.org \
    --cc=maxk@qualcomm.com \
    /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