LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Ed Tomlinson <edt@aei.ca>
To: Oliver Neukum <oneukum@suse.de>
Cc: linux-kernel@vger.kernel.org, linux-bluetooth@vger.kernel.org,
	linux-usb@vger.kernel.org
Subject: Re: [BUG] usb problems in .38-rc3+
Date: Mon, 7 Feb 2011 21:15:20 -0500	[thread overview]
Message-ID: <201102072115.20858.edt@aei.ca> (raw)
In-Reply-To: <201102071920.22543.edt@aei.ca>

On Monday 07 February 2011 19:20:21 Ed Tomlinson wrote:
> On Monday 07 February 2011 04:09:51 Oliver Neukum wrote:
> > Am Samstag, 5. Februar 2011, 20:17:57 schrieb Ed Tomlinson:
> > > Hi,
> > > 
> > > My bluetooth usb dongle has stopped working in .38-rc3+
> > > 
> > > Bus 002 Device 008: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
> > > 
> > > and in dmesg
> > > 
> > > [108495.369056] usb 5-1: new full speed USB device using ohci_hcd and address 3
> > > [108495.573077] usb 5-1: New USB device found, idVendor=0a12, idProduct=0001
> > > [108495.580099] usb 5-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
> > > [108652.971977] usb 5-1: USB disconnect, address 3
> > > [108652.972718] btusb_bulk_complete: hci0 urb ffff8800684e99c0 failed to resubmit (19)
> > > [108652.973725] btusb_bulk_complete: hci0 urb ffff8800684e9c00 failed to resubmit (19)
> > > [108652.974707] btusb_intr_complete: hci0 urb ffff8800684e9840 failed to resubmit (19)
> > > [108653.001690] btusb_send_frame: hci0 urb ffff8800bb42a240 submission failed
> > > [108657.007541] usb 2-4.7: new full speed USB device using ehci_hcd and address 8
> > > [108657.147736] usb 2-4.7: New USB device found, idVendor=0a12, idProduct=0001
> > > [108657.154954] usb 2-4.7: New USB device strings: Mfr=0, Product=0, SerialNumber=0
> > > 
> > > Its been working for years here.
> > > 
> > > Any ideas on what to try or additional info to gather?
> > 
> > Please test what happens if you disable runtime power management.
> 
> After a pointer from Oliver I booted with usbcore.autosuspend=30000 and verified the device used
> the parm via /sys/bus...   Still did not work.  Bisect or are there some other things to try?

I tried bisecting without much luck.  It started with about 4000 commits to check.  It was still bad
when it reached the first 1000 commits post .37.  Then all boots started crashing.  I think its possible
to restrict a bisect to a directory - if so, what dir should I try?

TIA
Ed

  reply	other threads:[~2011-02-08  2:15 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-05 19:17 Ed Tomlinson
2011-02-05 20:16 ` Alan Stern
2011-02-05 22:50   ` Przemo Firszt
2011-02-06  4:27   ` Ed Tomlinson
2011-02-07  9:09 ` Oliver Neukum
2011-02-08  0:20   ` Ed Tomlinson
2011-02-08  2:15     ` Ed Tomlinson [this message]
2011-02-08  6:46       ` Gadiyar, Anand
2011-02-09  4:31         ` Ed Tomlinson
2011-02-09  6:17           ` Anand Gadiyar
2011-02-09 23:48             ` Ed Tomlinson
2011-02-12 14:38             ` Ed Tomlinson
2011-02-16 14:00 ` Gustavo F. Padovan
2011-02-16 18:38   ` Ed Tomlinson
2011-02-16 18:47     ` Gustavo F. Padovan
     [not found]       ` <201102201209.20799.edt@aei.ca>
2011-02-20 20:49         ` Ed Tomlinson

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=201102072115.20858.edt@aei.ca \
    --to=edt@aei.ca \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=oneukum@suse.de \
    --subject='Re: [BUG] usb problems in .38-rc3+' \
    /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).