On Wednesday, 20 June 2007 03:52, Zhang Rui wrote:
> On Tue, 2007-06-19 at 13:26 +0200, Rafael J. Wysocki wrote:
> > On Tuesday, 19 June 2007 11:55, Zhang Rui wrote:
> > > On Tue, 2007-06-19 at 18:30 +0900, Mattia Dongili wrote:
> > > > On Tue, Jun 19, 2007 at 04:57:55PM +0800, Zhang Rui wrote:
> > > > > On Sun, 2007-05-20 at 15:14 +0900, Mattia Dongili wrote:
> > > > > > On Sat, May 19, 2007 at 12:04:13AM -0700, Andrew Morton wrote:
> > > > > > > On Sat, 19 May 2007 15:48:29 +0900 Mattia Dongili <[EMAIL
> > > > > > > PROTECTED]> wrote:
> > > > > > >
> > > > > > > > On Fri, May 18, 2007 at 12:22:40AM -0700, Andrew Morton wrote:
> > > > > > > > > On Fri, 18 May 2007 16:15:24 +0900 Mattia Dongili <[EMAIL
> > > > > > > > > PROTECTED]> wrote:
> > > > > > > > >
> > > > > > > > > > Hello,
> > > > > > > > > >
> > > > > > > > > > After finally catching fw-{ohci,core} to be problematic
> > > > > > > > > > during resume,
> > > > > > > > > > I'm now experiencing an immediate resume after suspending.
> > > > > > > > > >
> > > > > > > > > > 2.6.21-rc7-mm* didn't even suspend, my last known
> > > > > > > > > > suspend-and-resuming
> > > > > > > > > > kernel was 2.6.21-rc5-mm3 (I know one other vaio SZ user
> > > > > > > > > > could STR with
> > > > > > > > > > 2.6.21-rc6-mm* after the cpuidle fixes).
> > > > > > > > > >
> > > > > > > > > > my .config is:
> > > > > > > > > > http://oioio.altervista.org/linux/config-2.6.22-rc1-mm1-1
> > > > > > > > > > and a str cycle with PM_DEBUG=y:
> > > > > > > > > > http://oioio.altervista.org/linux/dmesg-SRT-immediately-resumes.txt
> > > > > > > > ...
> > > > > > > > > > Any idea where to start from? (bisecting is ok, but it'll
> > > > > > > > > > take some
> > > > > > > > > > time...)
> > > > > > > > >
> > > > > > > > > Bisecting isn't that bad ;) I'd pick git-acpi.patch as the
> > > > > > > > > starting point.
> > > > > > > >
> > > > > > > > ok, git-acpi.patch is not the bad boy :)
> > > > > >
> > > > > > but very very close:
> > > > > > acpi-driver-model-flags-and-platform_enable_wake.patch
> > > > > >
> > > > > Hi, Mattia,
> > > > >
> > > > > I tested this patch on several platforms but can not reproduce the
> > > > > bug.
> > > > > Could you please help me do a simple test please?
> > > > >
> > > > > Any kernel release later than 2.6.22-rc1 is ok. You don't need to
> > > > > apply
> > > > > acpi-driver-model-flags-and-platform_enable_wake.patch.
> > > > >
> > > > > Try to enable the wakeup GPE for all the USB devices first.
> > > > > e.g. "#echo USB1 >/proc/acpi/wakeup" will enable GPE for USB1.
> > > > > USB1 S3 disabled pci:0000:00:1d.0
> > > > > USB2 S3 disabled pci:0000:00:1d.1
> > > > > USB3 S3 disabled pci:0000:00:1d.2
> > > > > USB4 S3 disabled pci:0000:00:1d.3
> > > > > USB7 S3 disabled pci:0000:00:1d.7
> > > > >
> > > > > Try STR and check if it resumes immediately after suspend.
> > > > > I think the same problem will happen without this patch.
> > > >
> > > > ok, building right now.
> > > > Anyway, I don't remember the details but ehci and uhci were already
> > > > spotted as being part of the problem. See the rest of the thread
> > > > starting here http://lkml.org/lkml/2007/5/20/223
> >
> > Slightly off-topic, but I have a test box that resumes immediately after an
> > STR
> > is ehci_hcd is loaded and suspends correctly otherwise (with an Intel
> > chipset).
> >
> Did you manually override /proc/acpi/wakeup?
No, I didn't.
> Attaching the content of /proc/acpi/wakeup may be helpful. :)
Well, there's nothing interesting in there, AFAICS:
Device S-state Status Sysfs node
P0P4 S4 disabled pci:0000:00:1e.0
BNIC S4 disabled pci:0000:02:05.0
USB1 S4 disabled pci:0000:00:1d.0
USB2 S4 disabled pci:0000:00:1d.1
USB3 S4 disabled pci:0000:00:1d.2
EUSB S4 disabled pci:0000:00:1d.7
PS2K S4 disabled pnp:00:0b
PS2M S4 disabled pnp:00:0c
(this is from after a successful hibernation if that matters).
Greetings,
Rafael
--
"Premature optimization is the root of all evil." - Donald Knuth
-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
