From: Oliver Neukum <oneukum@suse.de>
To: Pavel Machek <pavel@ucw.cz>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
kernel list <linux-kernel@vger.kernel.org>,
linux-bluetooth@vger.kernel.org, marcel@holtmann.org,
gustavo@padovan.org, johan.hedberg@gmail.com
Subject: Re: 3.4.0-rc7 regression: bluetooth vs. s2ram
Date: Wed, 16 May 2012 11:03:50 +0200 [thread overview]
Message-ID: <201205161103.50317.oneukum@suse.de> (raw)
In-Reply-To: <20120515180105.GA1923@elf.ucw.cz>
Am Dienstag, 15. Mai 2012, 20:01:06 schrieb Pavel Machek:
> On Tue 2012-05-15 15:29:01, Oliver Neukum wrote:
> > Am Dienstag, 15. Mai 2012, 15:14:57 schrieb Pavel Machek:
> > > If I suspend without bnep0 active, resume works.
> > >
> > > (This has worked before, but "before" may mean 3.2 in this case).
> > >
> > > Can someone test/reproduce this? Ideas?
> > >
> > > PS: Under normal suspend/resume, I see these warnings in the
> > > log. Maybe relevant?
> >
> > Most likely. Something has introduced a bug that crashes if the controller
> > over which a bnep is run is getting away. Does it survive a surprise removal
> > of the BT device while bnep is up?
>
> No, it does not. If I turn off hardware radio kill switch, machine
> dies in the same way. So not just sleep related...
You lose power, btusb cannot deal with that and you get an unplug/replug cycle.
Can you get an oops when you are hitting the kill switch?
Regards
Oliver
prev parent reply other threads:[~2012-05-16 9:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-15 13:14 3.4.0-rc7 regression: bluetooth vs. s2ram Pavel Machek
2012-05-15 13:29 ` Oliver Neukum
2012-05-15 18:01 ` Pavel Machek
2012-05-16 9:03 ` Oliver Neukum [this message]
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=201205161103.50317.oneukum@suse.de \
--to=oneukum@suse.de \
--cc=gustavo@padovan.org \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
/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).