linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jérôme de Bretagne" <jerome.debretagne@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: Re: BT / serial regression introduced during the recent 4.9-rc1 merge?
Date: Thu, 20 Oct 2016 21:31:01 +0200	[thread overview]
Message-ID: <1476991861.2007.2.camel@gmail.com> (raw)
In-Reply-To: <1476815643.1658.3.camel@gmail.com>

Hi,

> I've compiled the latest bluetooth-next branch and I'm facing what looks
> like a regression to me (still on a Lenovo ThinkPad 8 tablet): btattach
> doesn't properly initialize the Broadcom BCM2E55 chipset anymore. 
> 
> I'm getting various timeout messages in dmesg:
> 
> [   13.188057] Bluetooth: hci0 command 0xfc45 tx timeout
> [   16.093068] serial8250_interrupt: 4158 callbacks suppressed
> [   16.093072] serial8250: too much work for irq39
> [   16.094287] serial8250: too much work for irq39
> ...
> [   16.103868] serial8250: too much work for irq39
> [   21.100041] serial8250_interrupt: 4167 callbacks suppressed
> [   21.100044] serial8250: too much work for irq39
> ...
> [   21.222065] Bluetooth: hci0: BCM: failed to write clock (-110)
> [   23.238528] Bluetooth: hci0 command 0x0c03 tx timeout
> [   26.104253] serial8250_interrupt: 4165 callbacks suppressed
> [   26.104257] serial8250: too much work for irq39
> 
> which I never had before and Bluetooth never actually starts.
> 
> I've gone back in time and it doesn't work either with a kernel built at
> e6445f52d9c8b0e6557a45fa7d0e8e088d430a8c "Merge tag 'usb-4.9-rc1' of
> git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb".
> 
> It still worked at commit a2f195a73eba807006fb0cb882ecb552c06eea00
> "bluetooth: bcm203x: don't print error when allocating urb fails" though,
> which was the last previous commit modifying files in drivers/bluetooth in
> the bluetooth-next branch.

Continuing to bissect, the regression seems to have appeared during commit:
   e6dce825fba05f447bd22c865e27233182ab3d79    Merge tag 'tty-4.9-rc1' of
   git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty

   Pull tty and serial updates from Greg KH:
     "Here is the big tty and serial patch set for 4.9-rc1. [...]"

just to let you know the state of my investigation. Now, I'll switch to
bissect the 111 commits introduced within that merge. To be continued.

Regards,

Jérôme

  reply	other threads:[~2016-10-20 19:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-18 18:34 BT / serial regression introduced during the recent 4.9-rc1 merge? Jérôme de Bretagne
2016-10-20 19:31 ` Jérôme de Bretagne [this message]
2016-11-01 16:58 ` [PATCHv2 3/3] serial: 8250_dw: Add quirk for APM X-Gene SoC (was: BT / serial regression introduced during the recent 4.9-rc1 merge?) Jérôme de Bretagne
2016-11-02  3:49   ` Rafael J. Wysocki
2016-11-02  8:37     ` Heikki Krogerus
2016-11-02 13:52       ` Jérôme de Bretagne
2016-11-02 15:41         ` Heikki Krogerus
2016-11-03 14:21           ` [PATCH] ACPI / platform: Add support for build-in properties Heikki Krogerus
2016-11-03 16:12             ` Yazen Ghannam
2016-11-06 16:09             ` Jérôme de Bretagne
2016-11-09 23:40               ` Rafael J. Wysocki
2016-11-07 13:34             ` Andy Shevchenko

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=1476991861.2007.2.camel@gmail.com \
    --to=jerome.debretagne@gmail.com \
    --cc=linux-bluetooth@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;
as well as URLs for NNTP newsgroup(s).