LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Dave Young" <hidave.darkstar@gmail.com>
To: "Thomas Gleixner" <tglx@linutronix.de>
Cc: "Marcel Holtmann" <marcel@holtmann.org>,
	"Quel Qun" <kelk1@comcast.net>,
	LKML <linux-kernel@vger.kernel.org>,
	"Jiri Kosina" <jkosina@suse.cz>, "Ingo Molnar" <mingo@elte.hu>
Subject: Re: Kernel oops with bluetooth usb dongle
Date: Thu, 21 Feb 2008 15:30:58 +0800	[thread overview]
Message-ID: <a8e1da0802202330q67f7b5ffo1258b08b043a6ac3@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.1.00.0802200908250.7583@apollo.tec.linutronix.de>

On Wed, Feb 20, 2008 at 4:11 PM, Thomas Gleixner <tglx@linutronix.de> wrote:
> On Wed, 20 Feb 2008, Thomas Gleixner wrote:
>  > On Tue, 19 Feb 2008, Marcel Holtmann wrote:
>
> > > I don't really have any idea. Nothing has been changed in this area for a
>  > > couple of years. The command TX timeout is the timeout that indicates a
>  > > missing answer to a command sent down to the Bluetooth chip.
>  > >
>  > > However this involves some atomic and tasklet stuff. Did we have some changes
>  > > that I missed and might now render this usage as broken.
>  >
>  > Not that I'm aware off, but this might as well be some old use after
>  > free bug which got exposed by some unrelated change. The good news is
>  > that it is reproducible. I'll hack up some nasty debug patch which
>  > lets us - hopefully - decode where the timer was armed.
>
>  Quel, before I do that, is there any chance that you retest with the
>  latest mainline git version ?
>
>  http://www.kernel.org/pub/linux/kernel/v2.6/snapshots/patch-2.6.25-rc2-git4.bz2

And please test with this patch as well:

http://lkml.org/lkml/2008/2/20/121

>
>  Is the delta which applies on top of rc2.
>
>
>
>  Thanks,
>
>         tglx
>  --
>  To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>  the body of a message to majordomo@vger.kernel.org
>  More majordomo info at  http://vger.kernel.org/majordomo-info.html
>  Please read the FAQ at  http://www.tux.org/lkml/
>

  reply	other threads:[~2008-02-21  7:31 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-18  0:01 Quel Qun
2008-02-18 12:43 ` Sebastian Siewior
2008-02-18 13:12 ` Thomas Gleixner
2008-02-19 21:07   ` Marcel Holtmann
2008-02-20  0:14     ` Thomas Gleixner
2008-02-20  8:11       ` Thomas Gleixner
2008-02-21  7:30         ` Dave Young [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-02-26 15:49 Quel Qun
2008-02-26  0:03 Quel Qun
2008-02-26  3:13 ` Marcel Holtmann
2008-02-28  1:03 ` Dave Young
2008-02-28  1:37   ` Dave Young
2008-02-22  2:40 Quel Qun
2008-02-22  3:23 ` Dave Young
2008-02-22  7:23 ` Thomas Gleixner
2008-02-22 11:34   ` David Woodhouse
2008-02-22 11:43     ` Thomas Gleixner
2008-02-21 16:49 Quel Qun
2008-02-21 19:37 ` Thomas Gleixner
2008-02-16 21:37 Quel Qun
2008-02-16 23:59 ` Thomas Gleixner
2008-02-16  0:41 Quel Qun
2008-02-16 11:05 ` Jiri Kosina
2008-02-16 11:50   ` Thomas Gleixner

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=a8e1da0802202330q67f7b5ffo1258b08b043a6ac3@mail.gmail.com \
    --to=hidave.darkstar@gmail.com \
    --cc=jkosina@suse.cz \
    --cc=kelk1@comcast.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcel@holtmann.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    --subject='Re: Kernel oops with bluetooth usb dongle' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).