From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Andrew Morton <akpm@osdl.org>
Subject: Re: 2.6.16-rc4-mm1 kernel crash at bootup. parport trouble?
Date: Tue, 21 Feb 2006 01:20:09 +0100
User-Agent: KMail/1.9.1
Cc: efault@gmx.de, helge.hafting@aitel.hist.no, linux-kernel@vger.kernel.org,
       brlink@debian.org
References: <20060220042615.5af1bddc.akpm@osdl.org> <200602210102.47371.rjw@sisk.pl> <20060220160955.3f0c4671.akpm@osdl.org>
In-Reply-To: <20060220160955.3f0c4671.akpm@osdl.org>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200602210120.10206.rjw@sisk.pl>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 833
Lines: 22

On Tuesday 21 February 2006 01:09, Andrew Morton wrote:
> "Rafael J. Wysocki" <rjw@sisk.pl> wrote:
> >
> > > > An unrelated problem is that USB host drivers (ohci-hcd, ehci-hcd) refuse to
> > > > suspend.  [Investigating ...]
> > > 
> > > Me too.
> > > 
> > > Try reverting reset-pci-device-state-to-unknown-after-disabled.patch.
> > 
> > Heh, that actually helps. :-)  Still I have no idea why is that so ...
> 
> Because some PCI drivers do pci_disable_device() before
> pci_set_power_state().  pci_set_power_state() sees PCI_UNKNOWN and runs
> away in terror.

Now I see that.  Thanks!
-
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/