linux-kernel - Re: 3.4.0-rc7 regression: bluetooth vs. s2ram

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 15 May 2012 15:29:01 +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, 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?
> 
>                                                                         Pavel
> 
> 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?

	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/