linux-kernel - Re: -rc6: something (probably active usb bluetooth) blocks suspend

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <20091118172211.GC25150@elf.ucw.cz>
Date:	Wed, 18 Nov 2009 18:22:11 +0100
From:	Pavel Machek <pavel@....cz>
To:	Oliver Neukum <oliver@...kum.org>
Cc:	Alan Stern <stern@...land.harvard.edu>,
	USB list <linux-usb@...r.kernel.org>,
	kernel list <linux-kernel@...r.kernel.org>,
	marcel@...tmann.org, linux-bluetooth@...r.kernel.org,
	"Rafael J. Wysocki" <rjw@...k.pl>
Subject: Re: -rc6: something (probably active usb bluetooth) blocks suspend

Hi!

> > > Why is the device autoresumed here? Are you using autosuspend?
> > > This is odd, as the freezer should block the send path and remote
> > > wakeups should be deferred.
> > 
> > I believe I have it enabled in kconfig but not during runtime.
> 
> Please check.

CONFIG_USB_SUSPEND=y

I'm not aware of  boot scripts enabling anything.

> > (Another problem is that I need to turn the kill switch on/off to get
> > my bt usb after resume. That used not be the case long time ago.)
> 
> That is possibly another problem.

Yes, I guess so. With those many USB experts around, I thought I'd
mention it :-).
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
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/