From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S267944AbUGaMTq (ORCPT ); Sat, 31 Jul 2004 08:19:46 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S267946AbUGaMTq (ORCPT ); Sat, 31 Jul 2004 08:19:46 -0400 Received: from dspnet.fr.eu.org ([62.73.5.179]:45829 "EHLO dspnet.fr.eu.org") by vger.kernel.org with ESMTP id S267944AbUGaMTp (ORCPT ); Sat, 31 Jul 2004 08:19:45 -0400 Date: Sat, 31 Jul 2004 14:19:44 +0200 From: Olivier Galibert To: "Hack inc." Subject: EHCI / pci power state / suspend annoying interactions Message-ID: <20040731121944.GA47191@dspnet.fr.eu.org> Mail-Followup-To: Olivier Galibert , "Hack inc." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org The EHCI on the latitude x300 does not have D2 capability: 00:1d.7 USB Controller: Intel Corp. 82801DB (ICH4) USB2 EHCI Controller (rev 01) (prog-if 20 [EHCI]) Subsystem: Dell Computer Corporation: Unknown device 014f Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- suspend which is usb_hcd_pci_suspend calls pci_set_power_state to request level D2, which fails with -EIO. The error is propagated back and the suspend aborts. What should actually happen in that case? OG.