Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261685AbTISTRO (ORCPT ); Fri, 19 Sep 2003 15:17:14 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261686AbTISTRN (ORCPT ); Fri, 19 Sep 2003 15:17:13 -0400 Received: from screech.rychter.com ([212.87.11.114]:7324 "EHLO screech.rychter.com") by vger.kernel.org with ESMTP id S261685AbTISTRK (ORCPT ); Fri, 19 Sep 2003 15:17:10 -0400 To: Greg KH Cc: linux-kernel@vger.kernel.org Subject: Re: 2.4.22 USB problem (uhci) References: <20030919190628.GI6624@kroah.com> X-Spammers-Please: blackholeme@rychter.com From: Jan Rychter Date: Fri, 19 Sep 2003 12:17:11 -0700 In-Reply-To: <20030919190628.GI6624@kroah.com> (Greg KH's message of "Fri, 19 Sep 2003 12:06:28 -0700") Message-ID: User-Agent: Gnus/5.1003 (Gnus v5.10.3) XEmacs/21.4 (Rational FORTRAN, linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1099 Lines: 28 >>>>> "Greg" == Greg KH writes: Greg> On Thu, Sep 18, 2003 at 08:10:48PM -0700, Jan Rychter wrote: >> Upon disconnecting an USB mouse from a 2.4.22, I get >> >> uhci.c: efe0: host controller halted. very bad >> >> and subsequently, the machine keeps on spinning in ACPI C2 state, >> never going into C3, as it should (since the mouse is the only USB >> device). >> >> If afterwards I do 'rmmod uhci; modprobe uhci', then the machine >> starts using the C3 state again. Greg> If you use the usb-uhci driver, does it also do this? If you mean strange messages, no, it doesn't. Using usb-uhci it just says "USB disconnect..." and everything looks fine. As to C-states, usb-uhci prevents Linux from *ever* entering C3, being effectively unusable on some laptops -- so there is no way I can see the same symptoms with it. --J. - 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/