[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.44L0.0609081636310.7953-100000@iolanthe.rowland.org>
Date: Fri, 8 Sep 2006 16:44:30 -0400 (EDT)
From: Alan Stern <stern@...land.harvard.edu>
To: "Rafael J. Wysocki" <rjw@...k.pl>
cc: Andrew Morton <akpm@...l.org>, <linux-kernel@...r.kernel.org>,
USB development list <linux-usb-devel@...ts.sourceforge.net>
Subject: Re: [linux-usb-devel] 2.6.18-rc6-mm1
On Fri, 8 Sep 2006, Andrew Morton wrote:
> Alan, is this likely to be due to your USB PM changes?
It's possible. Most of those changes are innocuous. They add routines
that don't get used until a later patch. However one of them might be
responsible.
On Fri, 8 Sep 2006, Rafael J. Wysocki wrote:
> On Friday, 8 September 2006 10:13, Andrew Morton wrote:
> >
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.18-rc6/2.6.18-rc6-mm1/
>
> ohci_hcd doesn't work after a resume from disk on HPC nx6325, worked on
> 2.6.18-rc5-mm1.
>
> It helps if I rmmod and modprobe it after the resume.
This patch affects OHCI. You can try reverting it, to see if that makes
any difference. It probably should have been left out of -mm, since it
interacts pretty strongly with some later USB PM patches that did get left
out.
gregkh-usb-usbcore-remove-usb_suspend_root_hub.patch
> Here's the relevant part of the dmesg output:
>
> usb usb1: resuming
> usbdev1.1_ep00: PM: resume from 0, parent usb1 still 1
> hub 1-0:1.0: PM: resume from 0, parent usb1 still 1
> hub 1-0:1.0: resuming
> usbdev1.1: PM: resume from 0, parent usb1 still 1
If reverting that patch doesn't help, please post the relevant dmesg log
after setting CONFIG_USB_DEBUG.
Alan Stern
-
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/
Powered by blists - more mailing lists