linux-kernel - Re: [linux-usb-devel] [PATCH] USB: Only enable autosuspend by default on certain device classes

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20070803200336.GA20376@redhat.com>
Date:	Fri, 3 Aug 2007 16:03:36 -0400
From:	Dave Jones <davej@...hat.com>
To:	Oliver Neukum <oliver@...kum.org>
Cc:	Matthew Garrett <mjg59@...f.ucam.org>,
	linux-usb-devel@...ts.sourceforge.net, Greg KH <gregkh@...e.de>,
	linux-kernel@...r.kernel.org, David Brownell <david-b@...bell.net>,
	Alan Stern <stern@...land.harvard.edu>,
	Rogan Dawes <lists@...es.za.net>
Subject: Re: [linux-usb-devel] [PATCH] USB: Only enable autosuspend by
	default on certain device classes

On Fri, Aug 03, 2007 at 06:08:11PM +0200, Oliver Neukum wrote:
 > Am Freitag 03 August 2007 schrieb Matthew Garrett:
 > > > Which is why I didn't suggest doing that, of course.  The only
 > > > one making that kind of straw man argument seems to be you.
 > > 
 > > But however you phrase it, that's effectively what it is. "Does your 
 > > device work?" just makes users wonder why the damn computer doesn't know 
 > > already. "This option may prevent your device from working. Click here 
 > > to switch it off" results in them wondering why it was switched on in 
 > > the first place. Many of our users aren't technical - they don't care 
 > > about saving 200mW, they just care about their printer working when they 
 > > plug it in.
 > 
 > Devices rarely simply crash. Although Windows doesn't do runtime power
 > management, it certainly will suspend all devices when the system goes
 > into suspension. Buggy devices typically disconnect and reconnect when
 > resumed. This is testable for in software without user intervention.

The printer I mentioned earlier this thread wouldn't work again
until I physically unplugged and replugged the usb cable.
It spewed descriptor read errors every time I tried to talk to it.
Even unloading and reloading the usb modules didn't bring it back
to life.

	Dave

-- 
http://www.codemonkey.org.uk
-
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/