New: Resume w/USB remote working in 2.6.33.2, no longer in 2.6.33.10

https://bugzilla.kernel.org/show_bug.cgi?id=16043

Summary: Resume w/USB remote working in 2.6.33.2, no longer in
2.6.33.10

           Product: ACPI
           Version: 2.5
    Kernel Version: 2.6.33.10
          Platform: All
        OS/Version: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Power-Sleep-Wake
        AssignedTo: acpi_power-sleep-wake-ztI5WcYan/[email protected]
        ReportedBy: [email protected]
        Regression: Yes

Using the latest Arch Linux kernel (2.6.33.10-1), the contents of /proc/acpi/wakeup are:

[scott@blargh-htpc ~]$ cat /proc/acpi/wakeup
Device S-state Status Sysfs node

HUB0      S5     disabled  pci:0000:00:09.0
XVR0      S5     disabled
XVR1      S5     disabled
XVR2      S5     disabled
XVR3      S5     disabled
XVR4      S5     disabled  pci:0000:00:16.0
XVR5      S5     disabled
XVR6      S5     disabled
UAR1      S5     disabled  pnp:00:08
USB0      S4     enabled   pci:0000:00:04.0
USB1      S4     disabled  pci:0000:00:06.0
USBB      S3     disabled  pci:0000:00:06.1
USB2      S3     disabled  pci:0000:00:04.1
AZAD      S5     disabled  pci:0000:00:08.0
MMAC      S5     disabled  pci:0000:00:0a.0

[scott@blargh-htpc pkg]$ uname -a
Linux blargh-htpc 2.6.33-ARCH #1 SMP PREEMPT Thu May 13 11:32:37 CEST 2010 x86_64 Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz GenuineIntel GNU/Linu x

The machine will suspend to RAM correctly, but will no longer be resumed by a USB remote power-on event. Instead, the power button on the machine must be pressed. It then resumes correctly.

This behavior was not present in the previous kernel I was running: 2.6.33.2-1.
In that case, the machine powered back on correctly when the USB remote's
power button was pressed. There was an intermediate kernel release (2.6.33.4-1) that I have not tried, but certainly can do so if that might help determine where the regression was introduced.

Additionally if there's more information I can provide about the system and my setup, please let me know what is required.

Quoted 7 lines

https://bugzilla.kernel.org/show_bug.cgi?id=16043

Summary: Resume w/USB remote working in 2.6.33.2, no longer in
2.6.33.10

Using the latest Arch Linux kernel (2.6.33.10-1), the contents of /proc/acpi/wakeup are:

Quoted 3 lines

The machine will suspend to RAM correctly, but will no longer be resumed by a USB remote power-on event. Instead, the power button on the machine must be pressed. It then resumes correctly.

Quoted 4 lines · Andrew Morton

Quoted 4 lines

https://bugzilla.kernel.org/show_bug.cgi?id=16043

Summary: Resume w/USB remote working in 2.6.33.2, no longer in
2.6.33.10

/proc/acpi/wakeup doesn't matter. What matters are the power/wakeup files under /sys.

If you want to enable wakeup, you have to do it manually or from a boot-time script like /etc/rc.d/rc.local. For example, you might need to do:

	echo enabled >/sys/bus/pci/devices/0000:00:04.0/power/wakeup

The system has been this way a long time, but up until just now it didn't work correctly.

Quoted 4 lines

Quoted 4 lines

Quoted 4 lines

https://bugzilla.kernel.org/show_bug.cgi?id=16043

Summary: Resume w/USB remote working in 2.6.33.2, no longer in
2.6.33.10

First I need to back track and fix an error -- it's version 2.6.33.4 that this no longer works in, not 2.6.33.10 as I had indicated.

In my case, "USB1" was the partical device that was waking up the system. According to /proc/acpi/wakeup, this is what I see:

     # grep USB1 /proc/acpi/wakeup
     USB1      S4     disabled  pci:0000:00:06.0

Now, I perform the following:

     # cat /sys/bus/pci/devices/0000\:00\:06.0/power/wakeup
        disabled
     # echo enabled > /sys/bus/pci/devices/0000\:00\:06.0/power/wakeup
     # cat /sys/bus/pci/devices/0000\:00\:06.0/power/wakeup
        enabled

Sadly it still will not resume.

Thanks for the tip, in the meantime I will go back to the 2.6.33-2 kernel and try modifying the /sys.../power/wakeup file in addition to / instead of the /proc/acpi/wakeup file.