Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751097AbZG0PKC (ORCPT ); Mon, 27 Jul 2009 11:10:02 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750779AbZG0PKB (ORCPT ); Mon, 27 Jul 2009 11:10:01 -0400 Received: from iolanthe.rowland.org ([192.131.102.54]:43386 "HELO iolanthe.rowland.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1750759AbZG0PKA (ORCPT ); Mon, 27 Jul 2009 11:10:00 -0400 Date: Mon, 27 Jul 2009 11:09:58 -0400 (EDT) From: Alan Stern X-X-Sender: stern@iolanthe.rowland.org To: list@phuk.ath.cx cc: "Rafael J. Wysocki" , Oliver Neukum , Linux Kernel Mailing List , Kernel Testers List Subject: Re: [Bug #13624] usb: wrong autosuspend initialization In-Reply-To: <4A6DBD51.6040103@phuk.ath.cx> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1735 Lines: 45 On Mon, 27 Jul 2009 list@phuk.ath.cx wrote: > Alan Stern wrote: > > On Sun, 26 Jul 2009, Rafael J. Wysocki wrote: > > > >> This message has been generated automatically as a part of a report > >> of regressions introduced between 2.6.29 and 2.6.30. > >> > >> The following bug entry is on the current list of known regressions > >> introduced between 2.6.29 and 2.6.30. Please verify if it still should > >> be listed and let me know (either way). > >> > >> > >> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=13624 > >> Subject : usb: wrong autosuspend initialization > >> Submitter : > >> Date : 2009-06-25 18:18 (32 days old) > > > > There's some question as to whether this should be considered a kernel > > bug. The kernel isn't doing anything wrong; the problem is that > > various userspace programs enable autosuspend for devices that can't > > support it properly. > > > > Alan Stern > > > > I'm currently working on a patch for laptop_mode. The maintainer tells > me there's work going on in the kernel to blacklist USB devices that > don't implement autosuspend correctly (like mice turning their light > off, etc...). Is that true? No, it isn't. The kernel has no way to tell whether mice behave that way or not. The only suspend-related blacklisting in the kernel is concerned with broken devices that can't be resumed after they have been suspended. The kernel has to reset these devices instead of resuming them. Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/