public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Marc Pignat <Marc.Pignat@hevs.ch>,
	Roger Quadros <ext-roger.quadros@nokia.com>,
	linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [BUG] 2.6.30-rc4 hid bluetooth not working
Date: Thu, 30 Apr 2009 15:34:14 -0700	[thread overview]
Message-ID: <1241130854.3197.2.camel@localhost.localdomain> (raw)
In-Reply-To: <alpine.LNX.2.00.0904302056270.5012@wotan.suse.de>

Hi Jiri,

> > > > My bluetooth keyboard is not working any more in rc4, but was 
> > > > working in rc3. Here is the dmesg output, triggered by the first key 
> > > > press on the keyboard, fortunately, this is 100% reproductible (once 
> > > > per boot).
> > > Does reverting f3784d834c7 fix the problem?
> > we have seen a similar report where reverting f3784d834c7 didn't fix it. 
> > And I don't see anything wrong with that patch. Did something important 
> > got changed in the work queue code that I am missing?
> 
> Calling flush() from work->func() is not safe. That's what the WARN_ON() 
> in flush_cpu_workqueue() is there for, right?

I don't know since this got changed in 2.6.30-rc1. I do have this kernel
running and I have seen the WARN_ON() only once. However I have never
seen a NULL pointer because of this patch.

Regards

Marcel



  reply	other threads:[~2009-04-30 22:34 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-30 13:20 [BUG] 2.6.30-rc4 hid bluetooth not working Marc Pignat
2009-04-30 13:57 ` Jiri Kosina
2009-04-30 15:03   ` Marcel Holtmann
2009-04-30 18:58     ` Jiri Kosina
2009-04-30 22:34       ` Marcel Holtmann [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-04-30 14:49 Marc Pignat
2009-04-30 15:32 Marc Pignat
2009-05-01  0:37 Marc Pignat
2009-05-01 22:20 ` Jiri Kosina
2009-05-01 22:56   ` Marcel Holtmann
2009-05-02  8:45 Marc Pignat
2009-05-02 14:08 ` Dave Young
2009-05-02 19:42   ` Marcel Holtmann
2009-05-02 20:19     ` Justin Mattock
2009-05-02 20:21       ` Marcel Holtmann
2009-05-02 21:07         ` Justin P. Mattock
2009-05-02 21:14           ` Marcel Holtmann
2009-05-02 21:31             ` Justin P. Mattock
2009-05-02 17:03 ` Marcel Holtmann
2009-05-03 14:55 Marc Pignat
2009-05-03 20:17 ` Marcel Holtmann
2009-05-03 21:18   ` Marc Pignat
2009-05-04  7:57   ` Roger Quadros

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=1241130854.3197.2.camel@localhost.localdomain \
    --to=marcel@holtmann.org \
    --cc=Marc.Pignat@hevs.ch \
    --cc=ext-roger.quadros@nokia.com \
    --cc=jkosina@suse.cz \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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