linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: linux-bluetooth@vger.kernel.org
Cc: bugme-daemon@bugzilla.kernel.org, johannes@sipsolutions.net
Subject: Re: [Bugme-new] [Bug 12125] New: bt stops working after suspend/resume
Date: Sun, 30 Nov 2008 10:36:55 -0800	[thread overview]
Message-ID: <20081130103655.d2d202c1.akpm@linux-foundation.org> (raw)
In-Reply-To: <bug-12125-10286@http.bugzilla.kernel.org/>


(switched to email.  Please respond via emailed reply-to-all, not via the
bugzilla web interface).

On Sun, 30 Nov 2008 08:08:42 -0800 (PST) bugme-daemon@bugzilla.kernel.org wrote:

> http://bugzilla.kernel.org/show_bug.cgi?id=12125
> 
>            Summary: bt stops working after suspend/resume
>            Product: Drivers
>            Version: 2.5
>      KernelVersion: 2.6.28-rc6-wl-dirty
>           Platform: All
>         OS/Version: Linux
>               Tree: Mainline
>             Status: NEW
>           Severity: normal
>           Priority: P1
>          Component: Bluetooth
>         AssignedTo: drivers_bluetooth@kernel-bugs.osdl.org
>         ReportedBy: johannes@sipsolutions.net
> 
> 
> Latest working kernel version: unknown
> Earliest failing kernel version: unknown
> Distribution: debian/unstable
> Hardware Environment: powerbook
> Software Environment: btusb
> Problem Description: bluetooth stops working after suspend/resume
> 
> Steps to reproduce:
> 
> suspend laptop, resume:
> 
> # hcitool scan
> Device is not available: No such device
> 
> # sdptool browse
> Inquiring ...
> Inquiry failed
> 
> 
> I'm fairly sure this used to work (most of the time at least!) with hci-usb.
> 


           reply	other threads:[~2008-11-30 18:36 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <bug-12125-10286@http.bugzilla.kernel.org/>]

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=20081130103655.d2d202c1.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=bugme-daemon@bugzilla.kernel.org \
    --cc=johannes@sipsolutions.net \
    --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).