[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <201205161103.50317.oneukum@suse.de>
Date: Wed, 16 May 2012 11:03:50 +0200
From: Oliver Neukum <oneukum@...e.de>
To: Pavel Machek <pavel@....cz>
Cc: "Rafael J. Wysocki" <rjw@...k.pl>,
kernel list <linux-kernel@...r.kernel.org>,
linux-bluetooth@...r.kernel.org, marcel@...tmann.org,
gustavo@...ovan.org, johan.hedberg@...il.com
Subject: Re: 3.4.0-rc7 regression: bluetooth vs. s2ram
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists