Suspend and resume on ASUS Laptops

Suspend and resume on ASUS Laptops

[Steven Rostedt]

For Black Friday I bought myself a ASUS-U56E-RBL8 at Staples for a
decent price. I installed Linux on it but it would not suspend. It would
always hang with the hard drive light on, as well as other leds and the
power light.

Searching the web, I found this link:

http://thecodecentral.com/2011/01/18/fix-ubuntu-10-10-suspendhibernate-not-working-bug

That talks about adding a script found here:

http://ubuntuforums.org/showpost.php?p=10359462&postcount=47

I added the script and sure enough, my suspend and even resume now work.

Before using this script, I've tried this on latest Debian testing and
with the latest Linus kernel (as of last night), and it didn't work. But
with this script, it works there and also with Debian stable and 3.0.10
kernel. (I hate gnome3 and lack of gnome2 so I created a separate
partition to run Debian testing, but I'm back to Debian stable).

The reason I'm writing you is, can we fix this without needing this
script?  Is there a modification to pm-suspend, or something that can
handle these laptops?

It just seems crazy to have everyday users add this script.

Thanks,

-- Steve

Re: Suspend and resume on ASUS Laptops

[Rafael J. Wysocki]

Hi,

On Thursday, December 01, 2011, Steven Rostedt wrote:
> For Black Friday I bought myself a ASUS-U56E-RBL8 at Staples for a
> decent price. I installed Linux on it but it would not suspend. It would
> always hang with the hard drive light on, as well as other leds and the
> power light.
> 
> Searching the web, I found this link:
> 
> http://thecodecentral.com/2011/01/18/fix-ubuntu-10-10-suspendhibernate-not-working-bug
> 
> That talks about adding a script found here:
> 
> http://ubuntuforums.org/showpost.php?p=10359462&postcount=47
> 
> I added the script and sure enough, my suspend and even resume now work.

Now, that's interesting, but I would lie if I said I knew what it was
actually doing, so let me add some USB people to the CC list.

> Before using this script, I've tried this on latest Debian testing and
> with the latest Linus kernel (as of last night), and it didn't work. But
> with this script, it works there and also with Debian stable and 3.0.10
> kernel. (I hate gnome3 and lack of gnome2 so I created a separate
> partition to run Debian testing, but I'm back to Debian stable).
> 
> The reason I'm writing you is, can we fix this without needing this
> script?  Is there a modification to pm-suspend, or something that can
> handle these laptops?
> 
> It just seems crazy to have everyday users add this script.

I totally agree, I had no idea it was necessary.

Thanks,
Rafael

Re: Suspend and resume on ASUS Laptops

[Oliver Neukum]

Am Donnerstag, 1. Dezember 2011, 10:35:57 schrieb Rafael J. Wysocki:
> > Searching the web, I found this link:
> > 
> > http://thecodecentral.com/2011/01/18/fix-ubuntu-10-10-suspendhibernate-not-working-bug
> > 
> > That talks about adding a script found here:
> > 
> > http://ubuntuforums.org/showpost.php?p=10359462&postcount=47
> > 
> > I added the script and sure enough, my suspend and even resume now work.
> 
> Now, that's interesting, but I would lie if I said I knew what it was
> actually doing, so let me add some USB people to the CC list.

What errors are seen in the kernel log?

	Regards
		Oliver

Re: Suspend and resume on ASUS Laptops

[Steven Rostedt]

On Thu, 2011-12-01 at 12:48 +0100, Oliver Neukum wrote:

> What errors are seen in the kernel log?

Without the script, I don't see any errors. Is there some debug thing
you want me to do? There's no error messages but the system just hangs
on suspend. It never makes it to the suspend state. The only way out of
it is to press and hold the power button for 10 seconds to force a hard
reboot.

Now when I add the script, I get the following messages from the kernel
for a full suspend/resume:

[  153.654339] ehci_hcd 0000:00:1a.0: remove, state 1
[  153.655383] usb usb1: USB disconnect, device number 1
[  153.656305] usb 1-1: USB disconnect, device number 2
[  153.657235] usb 1-1.1: USB disconnect, device number 3
[  153.658259] btusb_intr_complete: hci0 urb ffff8802289f52c0 failed to resubmit (19)
[  153.659469] btusb_bulk_complete: hci0 urb ffff8802289f4180 failed to resubmit (19)
[  153.660499] btusb_bulk_complete: hci0 urb ffff8802289f4540 failed to resubmit (19)
[  153.661485] usb 1-1: clear tt 1 (9032) error -19
[  153.661516] btusb_send_frame: hci0 urb ffff880233697800 submission failed
[  153.911024] usb 1-1.2: USB disconnect, device number 4
[  153.974262] ehci_hcd 0000:00:1a.0: USB bus 1 deregistered
[  153.975382] ehci_hcd 0000:00:1a.0: PCI INT A disabled
[  153.976582] ehci_hcd 0000:00:1d.0: remove, state 4
[  153.977616] usb usb2: USB disconnect, device number 1
[  153.978675] usb 2-1: USB disconnect, device number 2
[  154.038169] ehci_hcd 0000:00:1d.0: USB bus 2 deregistered
[  154.039340] ehci_hcd 0000:00:1d.0: PCI INT A disabled
[  154.043886] xhci_hcd 0000:03:00.0: remove, state 4
[  154.044944] usb usb4: USB disconnect, device number 1
[  154.046171] xHCI xhci_drop_endpoint called for root hub
[  154.046176] xHCI xhci_check_bandwidth called for root hub
[  154.098174] xhci_hcd 0000:03:00.0: USB bus 4 deregistered
[  154.099638] xhci_hcd 0000:03:00.0: remove, state 4
[  154.100785] usb usb3: USB disconnect, device number 1
[  154.102066] xHCI xhci_drop_endpoint called for root hub
[  154.102073] xHCI xhci_check_bandwidth called for root hub
[  154.202467] xhci_hcd 0000:03:00.0: USB bus 3 deregistered
[  154.257840] xhci_hcd 0000:03:00.0: PCI INT A disabled
[  154.789259] PM: Syncing filesystems ... done.
[  154.790059] PM: Preparing system for mem sleep
[  154.790203] Freezing user space processes ... (elapsed 0.01 seconds) done.
[  154.804993] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.
[  154.820979] PM: Entering mem sleep
[  154.821077] Suspending console(s) (use no_console_suspend to debug)
[  154.821365] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[  154.927537] sd 0:0:0:0: [sda] Stopping disk
[  155.064782] HDA Intel 0000:00:1b.0: PCI INT A disabled
[  155.352105] PM: suspend of devices complete after 531.680 msecs
[  155.384199] PM: late suspend of devices complete after 32.138 msecs
[  155.384403] ACPI: Preparing to enter system sleep state S3
[  156.878041] PM: Saving platform NVS memory
[  156.879218] Disabling non-boot CPUs ...
[  156.981674] CPU 1 is now offline
[  157.085514] CPU 2 is now offline
[  157.189360] CPU 3 is now offline
[  157.189572] Extended CMOS year: 2000
[  157.189828] ACPI: Low-level resume complete
[  157.189869] PM: Restoring platform NVS memory
[  157.190251] Extended CMOS year: 2000
[  157.190271] Enabling non-boot CPUs ...
[  157.198357] Booting Node 0 Processor 1 APIC 0x2
[  157.198358] smpboot cpu 1: start_ip = 99000
[  157.306126] NMI watchdog enabled, takes one hw-pmu counter.
[  157.306340] CPU1 is up
[  157.306388] Booting Node 0 Processor 2 APIC 0x1
[  157.306389] smpboot cpu 2: start_ip = 99000
[  157.309859] Switched to NOHz mode on CPU #1
[  157.414054] NMI watchdog enabled, takes one hw-pmu counter.
[  157.414331] CPU2 is up
[  157.414381] Booting Node 0 Processor 3 APIC 0x3
[  157.414383] smpboot cpu 3: start_ip = 99000
[  157.417699] Switched to NOHz mode on CPU #2
[  157.521895] NMI watchdog enabled, takes one hw-pmu counter.
[  157.522161] CPU3 is up
[  157.524120] ACPI: Waking up from system sleep state S3
[  157.525542] Switched to NOHz mode on CPU #3
[  157.598005] i915 0000:00:02.0: restoring config space at offset 0xf (was 0x100, writing 0x10b)
[  157.598015] i915 0000:00:02.0: restoring config space at offset 0x1 (was 0x900007, writing 0x900407)
[  157.598036] pci 0000:00:16.0: restoring config space at offset 0xf (was 0x100, writing 0x10b)
[  157.598052] pci 0000:00:16.0: restoring config space at offset 0x4 (was 0xfedb0004, writing 0xdfc0b004)
[  157.598059] pci 0000:00:16.0: restoring config space at offset 0x1 (was 0x180006, writing 0x100006)
[  157.598083] pci 0000:00:1a.0: restoring config space at offset 0xf (was 0x100, writing 0x10b)
[  157.598100] pci 0000:00:1a.0: restoring config space at offset 0x4 (was 0x0, writing 0xdfc08000)
[  157.598108] pci 0000:00:1a.0: restoring config space at offset 0x1 (was 0x2900000, writing 0x2900002)
[  157.598137] HDA Intel 0000:00:1b.0: restoring config space at offset 0xf (was 0x100, writing 0x105)
[  157.598152] HDA Intel 0000:00:1b.0: restoring config space at offset 0x4 (was 0x4, writing 0xdfc00004)
[  157.598158] HDA Intel 0000:00:1b.0: restoring config space at offset 0x3 (was 0x0, writing 0x10)
[  157.598164] HDA Intel 0000:00:1b.0: restoring config space at offset 0x1 (was 0x100000, writing 0x100002)
[  157.598193] pcieport 0000:00:1c.0: restoring config space at offset 0xf (was 0x100, writing 0x10010b)
[  157.598210] pcieport 0000:00:1c.0: restoring config space at offset 0x3 (was 0x810000, writing 0x810010)
[  157.598217] pcieport 0000:00:1c.0: restoring config space at offset 0x1 (was 0x100000, writing 0x100407)
[  157.598263] pcieport 0000:00:1c.1: restoring config space at offset 0xf (was 0x200, writing 0x100205)
[  157.598280] pcieport 0000:00:1c.1: restoring config space at offset 0x3 (was 0x810000, writing 0x810010)
[  157.598287] pcieport 0000:00:1c.1: restoring config space at offset 0x1 (was 0x100000, writing 0x100407)
[  157.598331] pcieport 0000:00:1c.3: restoring config space at offset 0xf (was 0x400, writing 0x10040a)
[  157.598348] pcieport 0000:00:1c.3: restoring config space at offset 0x3 (was 0x810000, writing 0x810010)
[  157.598355] pcieport 0000:00:1c.3: restoring config space at offset 0x1 (was 0x100000, writing 0x100407)
[  157.598398] pcieport 0000:00:1c.5: restoring config space at offset 0xf (was 0x200, writing 0x100205)
[  157.598415] pcieport 0000:00:1c.5: restoring config space at offset 0x3 (was 0x810000, writing 0x810010)
[  157.598422] pcieport 0000:00:1c.5: restoring config space at offset 0x1 (was 0x100007, writing 0x100407)
[  157.598465] pci 0000:00:1d.0: restoring config space at offset 0xf (was 0x100, writing 0x105)
[  157.598482] pci 0000:00:1d.0: restoring config space at offset 0x4 (was 0x0, writing 0xdfc07000)
[  157.598490] pci 0000:00:1d.0: restoring config space at offset 0x1 (was 0x2900000, writing 0x2900002)
[  157.598564] ahci 0000:00:1f.2: restoring config space at offset 0x1 (was 0x2b00007, writing 0x2b00407)
[  157.598605] i801_smbus 0000:00:1f.3: restoring config space at offset 0x1 (was 0x2800001, writing 0x2800003)
[  157.598720] iwlagn 0000:02:00.0: restoring config space at offset 0xf (was 0x100, writing 0x105)
[  157.598760] iwlagn 0000:02:00.0: restoring config space at offset 0x4 (was 0x4, writing 0xde800004)
[  157.598770] iwlagn 0000:02:00.0: restoring config space at offset 0x3 (was 0x0, writing 0x10)
[  157.598782] iwlagn 0000:02:00.0: restoring config space at offset 0x1 (was 0x100000, writing 0x100006)
[  157.598899] pci 0000:03:00.0: restoring config space at offset 0xf (was 0x100, writing 0x10a)
[  157.598932] pci 0000:03:00.0: restoring config space at offset 0x4 (was 0x4, writing 0xdde00004)
[  157.598939] pci 0000:03:00.0: restoring config space at offset 0x3 (was 0x0, writing 0x10)
[  157.598949] pci 0000:03:00.0: restoring config space at offset 0x1 (was 0x100000, writing 0x100002)
[  157.599005] atl1c 0000:04:00.0: restoring config space at offset 0xf (was 0x100, writing 0x105)
[  157.599033] atl1c 0000:04:00.0: restoring config space at offset 0x3 (was 0x0, writing 0x10)
[  157.599042] atl1c 0000:04:00.0: restoring config space at offset 0x1 (was 0x100006, writing 0x100007)
[  157.599118] PM: early resume of devices complete after 1.154 msecs
[  157.599184] i915 0000:00:02.0: setting latency timer to 64
[  157.599196] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
[  157.599210] HDA Intel 0000:00:1b.0: setting latency timer to 64
[  157.599259] ahci 0000:00:1f.2: setting latency timer to 64
[  157.599272] HDA Intel 0000:00:1b.0: irq 45 for MSI/MSI-X
[  157.599338] sd 0:0:0:0: [sda] Starting disk
[  157.635986] Extended CMOS year: 2000
[  157.924972] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[  157.952075] ata3.00: ACPI cmd ef/10:06:00:00:00:a0 (SET FEATURES) succeeded
[  157.952084] ata3.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
[  158.037042] ata3.00: ACPI cmd ef/10:06:00:00:00:a0 (SET FEATURES) succeeded
[  158.037052] ata3.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
[  158.070553] ata3.00: configured for UDMA/100
[  160.217594] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[  160.224697] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
[  160.225011] ata1.00: ACPI cmd ef/10:06:00:00:00:a0 (SET FEATURES) succeeded
[  160.225020] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
[  160.226948] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
[  160.227224] ata1.00: ACPI cmd ef/10:06:00:00:00:a0 (SET FEATURES) succeeded
[  160.227234] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
[  160.228079] ata1.00: configured for UDMA/133
[  160.252503] PM: resume of devices complete after 2657.291 msecs
[  160.252615] PM: Finishing wakeup.
[  160.252616] Restarting tasks ... done.
[  160.260544] video LNXVIDEO:00: Restoring backlight state
[  160.384782] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[  160.386988] atl1c 0000:04:00.0: irq 46 for MSI/MSI-X
[  160.470856] ADDRCONF(NETDEV_UP): eth0: link is not ready
[  160.478772] ehci_hcd 0000:00:1a.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[  160.480255] ehci_hcd 0000:00:1a.0: setting latency timer to 64
[  160.480263] ehci_hcd 0000:00:1a.0: EHCI Host Controller
[  160.481786] ehci_hcd 0000:00:1a.0: new USB bus registered, assigned bus number 1
[  160.483317] ehci_hcd 0000:00:1a.0: debug port 2
[  160.488701] ehci_hcd 0000:00:1a.0: cache line size of 64 is not supported
[  160.488728] ehci_hcd 0000:00:1a.0: irq 16, io mem 0xdfc08000
[  160.505179] ehci_hcd 0000:00:1a.0: USB 2.0 started, EHCI 1.00
[  160.505716] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[  160.506179] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[  160.506654] usb usb1: Product: EHCI Host Controller
[  160.507135] usb usb1: Manufacturer: Linux 3.0.10-custom ehci_hcd
[  160.507629] usb usb1: SerialNumber: 0000:00:1a.0
[  160.508222] hub 1-0:1.0: USB hub found
[  160.508905] hub 1-0:1.0: 2 ports detected
[  160.509615] ehci_hcd 0000:00:1d.0: PCI INT A -> GSI 23 (level, low) -> IRQ 23
[  160.510449] ehci_hcd 0000:00:1d.0: setting latency timer to 64
[  160.510453] ehci_hcd 0000:00:1d.0: EHCI Host Controller
[  160.511319] ehci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 2
[  160.512037] ehci_hcd 0000:00:1d.0: debug port 2
[  160.516484] ehci_hcd 0000:00:1d.0: cache line size of 64 is not supported
[  160.516495] ehci_hcd 0000:00:1d.0: irq 23, io mem 0xdfc07000
[  160.529151] ehci_hcd 0000:00:1d.0: USB 2.0 started, EHCI 1.00
[  160.530648] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
[  160.532008] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[  160.533400] usb usb2: Product: EHCI Host Controller
[  160.534819] usb usb2: Manufacturer: Linux 3.0.10-custom ehci_hcd
[  160.536192] usb usb2: SerialNumber: 0000:00:1d.0
[  160.537740] hub 2-0:1.0: USB hub found
[  160.539397] hub 2-0:1.0: 2 ports detected
[  160.540968] xhci_hcd 0000:03:00.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
[  160.543013] xhci_hcd 0000:03:00.0: setting latency timer to 64
[  160.543023] xhci_hcd 0000:03:00.0: xHCI Host Controller
[  160.543980] xhci_hcd 0000:03:00.0: new USB bus registered, assigned bus number 3
[  160.549086] xhci_hcd 0000:03:00.0: irq 19, io mem 0xdde00000
[  160.549747] xhci_hcd 0000:03:00.0: irq 47 for MSI/MSI-X
[  160.549751] xhci_hcd 0000:03:00.0: irq 48 for MSI/MSI-X
[  160.549754] xhci_hcd 0000:03:00.0: irq 49 for MSI/MSI-X
[  160.549757] xhci_hcd 0000:03:00.0: irq 50 for MSI/MSI-X
[  160.549761] xhci_hcd 0000:03:00.0: irq 52 for MSI/MSI-X
[  160.549855] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002
[  160.550449] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[  160.551037] usb usb3: Product: xHCI Host Controller
[  160.551629] usb usb3: Manufacturer: Linux 3.0.10-custom xhci_hcd
[  160.552226] usb usb3: SerialNumber: 0000:03:00.0
[  160.552885] xHCI xhci_add_endpoint called for root hub
[  160.552886] xHCI xhci_check_bandwidth called for root hub
[  160.552903] hub 3-0:1.0: USB hub found
[  160.553593] hub 3-0:1.0: 2 ports detected
[  160.554353] xhci_hcd 0000:03:00.0: xHCI Host Controller
[  160.555013] xhci_hcd 0000:03:00.0: new USB bus registered, assigned bus number 4
[  160.555968] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003
[  160.556656] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[  160.557306] usb usb4: Product: xHCI Host Controller
[  160.557958] usb usb4: Manufacturer: Linux 3.0.10-custom xhci_hcd
[  160.558562] usb usb4: SerialNumber: 0000:03:00.0
[  160.559234] xHCI xhci_add_endpoint called for root hub
[  160.559236] xHCI xhci_check_bandwidth called for root hub
[  160.559253] hub 4-0:1.0: USB hub found
[  160.559937] hub 4-0:1.0: 2 ports detected
[  160.820711] usb 1-1: new high speed USB device number 2 using ehci_hcd
[  160.952976] usb 1-1: New USB device found, idVendor=8087, idProduct=0024
[  160.955141] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[  160.957992] hub 1-1:1.0: USB hub found
[  160.960907] hub 1-1:1.0: 6 ports detected
[  161.076317] usb 2-1: new high speed USB device number 2 using ehci_hcd
[  161.208585] usb 2-1: New USB device found, idVendor=8087, idProduct=0024
[  161.209303] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[  161.210602] hub 2-1:1.0: USB hub found
[  161.211402] hub 2-1:1.0: 6 ports detected
[  161.288236] usb 1-1.1: new full speed USB device number 3 using ehci_hcd
[  161.383792] usb 1-1.1: New USB device found, idVendor=8086, idProduct=0189
[  161.385776] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[  161.388679] bluetoothd[1639]: segfault at 7fd10bc5f4d0 ip 00007fd00a26adf4 sp 00007fff223959a0 error 4 in libc-2.11.2.so[7fd00a1f9000+158000]
[  161.459831] usb 1-1.2: new high speed USB device number 4 using ehci_hcd
[  161.614861] usb 1-1.2: New USB device found, idVendor=13d3, idProduct=5710
[  161.617543] usb 1-1.2: New USB device strings: Mfr=3, Product=1, SerialNumber=2
[  161.620172] usb 1-1.2: Product: USB 2.0 UVC VGA WebCam
[  161.622700] usb 1-1.2: Manufacturer: Azurewave
[  161.625061] usb 1-1.2: SerialNumber: 0x0001
[  161.630485] uvcvideo: Found UVC 1.00 device USB 2.0 UVC VGA WebCam (13d3:5710)
[  161.638614] input: USB 2.0 UVC VGA WebCam as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0/input/input13

Let me know if there's any more info you need. I could also perform
other debugging tasks for you too. Just let me know what you want me to
do.

Thanks,


-- Steve

Re: Suspend and resume on ASUS Laptops

[Oliver Neukum]

Am Donnerstag, 1. Dezember 2011, 15:28:54 schrieb Steven Rostedt:
> On Thu, 2011-12-01 at 12:48 +0100, Oliver Neukum wrote:
> 
> > What errors are seen in the kernel log?
> 
> Without the script, I don't see any errors. Is there some debug thing
> you want me to do? There's no error messages but the system just hangs
> on suspend. It never makes it to the suspend state. The only way out of
> it is to press and hold the power button for 10 seconds to force a hard
> reboot.

I see. I thought the system just refuses to enter S3/4. That it hangs was
new to me. Has there been a mail thread about this problem already?
If not, what is the last thing you see if you go to S3 after you booted
with no_console_suspend on the kernel command line?

	Regards
		Oliver

Re: Suspend and resume on ASUS Laptops

[Srivatsa S. Bhat]

On 12/01/2011 08:08 PM, Oliver Neukum wrote:

> Am Donnerstag, 1. Dezember 2011, 15:28:54 schrieb Steven Rostedt:
>> On Thu, 2011-12-01 at 12:48 +0100, Oliver Neukum wrote:
>>
>>> What errors are seen in the kernel log?
>>
>> Without the script, I don't see any errors. Is there some debug thing
>> you want me to do? There's no error messages but the system just hangs
>> on suspend. It never makes it to the suspend state. The only way out of
>> it is to press and hold the power button for 10 seconds to force a hard
>> reboot.
> 
> I see. I thought the system just refuses to enter S3/4. That it hangs was
> new to me. Has there been a mail thread about this problem already?
> If not, what is the last thing you see if you go to S3 after you booted
> with no_console_suspend on the kernel command line?
> 


Hi Steven,
Since without the script your system refuses to suspend, you could also use the
'pm_test' framework (documented in Documentation/power/basic-pm-debugging.txt)
to find out more about the failing step when suspend is attempted without using
the script. Trying 'echo devices > /sys/power/pm_test' might be helpful in your
case.

Regards,
Srivatsa S. Bhat
IBM Linux Technology Center

Re: Suspend and resume on ASUS Laptops

[Steven Rostedt]

On Thu, 2011-12-01 at 20:31 +0530, Srivatsa S. Bhat wrote:

> 
> Hi Steven,
> Since without the script your system refuses to suspend, you could also use the
> 'pm_test' framework (documented in Documentation/power/basic-pm-debugging.txt)
> to find out more about the failing step when suspend is attempted without using
> the script. Trying 'echo devices > /sys/power/pm_test' might be helpful in your
> case.

Interesting, all the pm_tests work. Even core. But when I switch it to
'none' it locks up.

If I just remove the ehci_hcd module, it suspends fine, so the issue is
with this module (or some usb device). There seems to be two devices
under ehci_hcd, and I played with the script to only unbind one at a
time. If I only unbind one (either one) it still hangs. I need to unbind
both for the suspend to work.

Without the script, here's the dmesg from the suspend to resume using
pm_test == core.

[  143.866718] PM: Syncing filesystems ... done.
[  143.867508] PM: Preparing system for mem sleep
[  143.867573] Freezing user space processes ... (elapsed 0.01 seconds) done.
[  143.882142] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.
[  143.898124] PM: Entering mem sleep
[  143.898235] Suspending console(s) (use no_console_suspend to debug)
[  143.898423] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[  143.934860] snd_hda_intel 0000:00:1b.0: PCI INT A disabled
[  143.949557] sd 0:0:0:0: [sda] Stopping disk
[  143.949981] ehci_hcd 0000:00:1a.0: PCI INT A disabled
[  144.005897] ehci_hcd 0000:00:1d.0: PCI INT A disabled
[  144.373349] PM: suspend of devices complete after 475.751 msecs
[  144.437292] PM: late suspend of devices complete after 64.034 msecs
[  144.437491] ACPI: Preparing to enter system sleep state S3
[  145.931187] PM: Saving platform NVS memory
[  145.932381] Disabling non-boot CPUs ...
[  146.034855] CPU 1 is now offline
[  146.138709] CPU 2 is now offline
[  146.242558] CPU 3 is now offline
[  146.242778] Extended CMOS year: 2000
[  146.242854] suspend debug: Waiting for 5 seconds.
[  151.195310] Extended CMOS year: 2000
[  151.195339] Enabling non-boot CPUs ...
[  151.199375] Booting Node 0 Processor 1 APIC 0x2
[  151.199376] smpboot cpu 1: start_ip = 99000
[  151.210396] Calibrating delay loop (skipped) already calibrated this CPU
[  151.230638] NMI watchdog enabled, takes one hw-pmu counter.
[  151.230829] CPU1 is up
[  151.230872] Booting Node 0 Processor 2 APIC 0x1
[  151.230873] smpboot cpu 2: start_ip = 99000
[  151.231034] Switched to NOHz mode on CPU #1
[  151.241885] Calibrating delay loop (skipped) already calibrated this CPU
[  151.262176] NMI watchdog enabled, takes one hw-pmu counter.
[  151.262428] CPU2 is up
[  151.262474] Booting Node 0 Processor 3 APIC 0x3
[  151.262476] smpboot cpu 3: start_ip = 99000
[  151.262986] Switched to NOHz mode on CPU #2
[  151.273489] Calibrating delay loop (skipped) already calibrated this CPU
[  151.293822] NMI watchdog enabled, takes one hw-pmu counter.
[  151.294063] CPU3 is up
[  151.295563] Switched to NOHz mode on CPU #3
[  151.295859] ACPI: Waking up from system sleep state S3
[  151.382813] i915 0000:00:02.0: BAR 0: set to [mem 0xdd000000-0xdd3fffff 64bit] (PCI address [0xdd000000-0xdd3fffff])
[  151.382819] i915 0000:00:02.0: BAR 2: set to [mem 0xc0000000-0xcfffffff 64bit pref] (PCI address [0xc0000000-0xcfffffff])
[  151.382822] i915 0000:00:02.0: BAR 4: set to [io  0xe000-0xe03f] (PCI address [0xe000-0xe03f])
[  151.382834] i915 0000:00:02.0: restoring config space at offset 0x1 (was 0x900403, writing 0x900407)
[  151.398789] ehci_hcd 0000:00:1a.0: BAR 0: set to [mem 0xdfc08000-0xdfc083ff] (PCI address [0xdfc08000-0xdfc083ff])
[  151.398802] ehci_hcd 0000:00:1a.0: restoring config space at offset 0xf (was 0x100, writing 0x10b)
[  151.398822] ehci_hcd 0000:00:1a.0: restoring config space at offset 0x1 (was 0x2900000, writing 0x2900002)
[  151.414767] snd_hda_intel 0000:00:1b.0: BAR 0: set to [mem 0xdfc00000-0xdfc03fff 64bit] (PCI address [0xdfc00000-0xdfc03fff])
[  151.414780] snd_hda_intel 0000:00:1b.0: restoring config space at offset 0xf (was 0x100, writing 0x105)
[  151.414796] snd_hda_intel 0000:00:1b.0: restoring config space at offset 0x3 (was 0x0, writing 0x10)
[  151.414802] snd_hda_intel 0000:00:1b.0: restoring config space at offset 0x1 (was 0x100000, writing 0x100002)
[  151.430746] ehci_hcd 0000:00:1d.0: BAR 0: set to [mem 0xdfc07000-0xdfc073ff] (PCI address [0xdfc07000-0xdfc073ff])
[  151.430759] ehci_hcd 0000:00:1d.0: restoring config space at offset 0xf (was 0x100, writing 0x105)
[  151.430779] ehci_hcd 0000:00:1d.0: restoring config space at offset 0x1 (was 0x2900000, writing 0x2900002)
[  151.446740] ahci 0000:00:1f.2: restoring config space at offset 0x1 (was 0x2b00403, writing 0x2b00407)
[  151.462704] xhci_hcd 0000:03:00.0: BAR 0: set to [mem 0xdde00000-0xdde07fff 64bit] (PCI address [0xdde00000-0xdde07fff])
[  151.478790] PM: early resume of devices complete after 111.626 msecs
[  151.478873] i915 0000:00:02.0: setting latency timer to 64
[  151.478876] ehci_hcd 0000:00:1a.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[  151.478879] snd_hda_intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
[  151.478882] ehci_hcd 0000:00:1a.0: setting latency timer to 64
[  151.478886] snd_hda_intel 0000:00:1b.0: setting latency timer to 64
[  151.478940] snd_hda_intel 0000:00:1b.0: irq 50 for MSI/MSI-X
[  151.478942] ehci_hcd 0000:00:1d.0: PCI INT A -> GSI 23 (level, low) -> IRQ 23
[  151.478950] ehci_hcd 0000:00:1d.0: setting latency timer to 64
[  151.478978] ahci 0000:00:1f.2: setting latency timer to 64
[  151.478997] xhci_hcd 0000:03:00.0: setting latency timer to 64
[  151.479020] usb usb3: root hub lost power or was reset
[  151.479021] usb usb4: root hub lost power or was reset
[  151.488652] sd 0:0:0:0: [sda] Starting disk
[  151.488946] xhci_hcd 0000:03:00.0: irq 45 for MSI/MSI-X
[  151.488952] xhci_hcd 0000:03:00.0: irq 46 for MSI/MSI-X
[  151.488957] xhci_hcd 0000:03:00.0: irq 47 for MSI/MSI-X
[  151.488962] xhci_hcd 0000:03:00.0: irq 48 for MSI/MSI-X
[  151.488967] xhci_hcd 0000:03:00.0: irq 49 for MSI/MSI-X
[  151.524742] Extended CMOS year: 2000
[  151.798256] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[  151.806242] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[  151.809758] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
[  151.819268] ata1.00: ACPI cmd ef/10:06:00:00:00:a0 (SET FEATURES) succeeded
[  151.819271] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
[  151.821084] ata3.00: ACPI cmd ef/10:06:00:00:00:a0 (SET FEATURES) succeeded
[  151.821094] ata3.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
[  151.850068] ata3.00: ACPI cmd ef/10:06:00:00:00:a0 (SET FEATURES) succeeded
[  151.850078] ata3.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
[  151.862944] ata3.00: configured for UDMA/100
[  153.738354] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
[  153.738642] ata1.00: ACPI cmd ef/10:06:00:00:00:a0 (SET FEATURES) succeeded
[  153.738652] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
[  153.739521] ata1.00: configured for UDMA/133
[  153.771247] PM: resume of devices complete after 2295.808 msecs
[  153.771418] PM: Finishing wakeup.
[  153.771420] Restarting tasks ... done.
[  153.774966] video LNXVIDEO:00: Restoring backlight state
[  153.810988] atl1c 0000:04:00.0: irq 51 for MSI/MSI-X
[  153.892934] ADDRCONF(NETDEV_UP): eth0: link is not ready

Thanks,

-- Steve

Re: Suspend and resume on ASUS Laptops

[Steven Rostedt]

Not sure if this is useful, but here's the lspci -vv output of the
devices under ehci_hcd

00:1a.0 USB Controller: Intel Corporation Cougar Point USB Enhanced Host Controller #2 (rev 05) (prog-if 20 [EHCI])
	Subsystem: ASUSTeK Computer Inc. Device 1157
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 16
	Region 0: Memory at dfc08000 (32-bit, non-prefetchable) [size=1K]
	Capabilities: [50] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [58] Debug port: BAR=1 offset=00a0
	Capabilities: [98] PCI Advanced Features
		AFCap: TP+ FLR+
		AFCtrl: FLR-
		AFStatus: TP-
	Kernel driver in use: ehci_hcd

00:1d.0 USB Controller: Intel Corporation Cougar Point USB Enhanced Host Controller #1 (rev 05) (prog-if 20 [EHCI])
	Subsystem: ASUSTeK Computer Inc. Device 1157
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 23
	Region 0: Memory at dfc07000 (32-bit, non-prefetchable) [size=1K]
	Capabilities: [50] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [58] Debug port: BAR=1 offset=00a0
	Capabilities: [98] PCI Advanced Features
		AFCap: TP+ FLR+
		AFCtrl: FLR-
		AFStatus: TP-
	Kernel driver in use: ehci_hcd

-- Steve

Re: Suspend and resume on ASUS Laptops

[Alan Stern]

On Thu, 1 Dec 2011, Steven Rostedt wrote:

> On Thu, 2011-12-01 at 20:31 +0530, Srivatsa S. Bhat wrote:
> 
> > 
> > Hi Steven,
> > Since without the script your system refuses to suspend, you could also use the
> > 'pm_test' framework (documented in Documentation/power/basic-pm-debugging.txt)
> > to find out more about the failing step when suspend is attempted without using
> > the script. Trying 'echo devices > /sys/power/pm_test' might be helpful in your
> > case.
> 
> Interesting, all the pm_tests work. Even core. But when I switch it to
> 'none' it locks up.
> 
> If I just remove the ehci_hcd module, it suspends fine, so the issue is
> with this module (or some usb device). There seems to be two devices
> under ehci_hcd, and I played with the script to only unbind one at a
> time. If I only unbind one (either one) it still hangs. I need to unbind
> both for the suspend to work.

It's possible that this problem is related to wakeup settings.  Have 
you tried disabling wakeup for the EHCI controllers?

This certainly appears to be some sort of bug in the firmware.  Finding 
it and working around it isn't likely to be easy.  Unbinding (or 
unloading) ehci-hcd may indeed be the path of least resistance.

Alan Stern

Re: Suspend and resume on ASUS Laptops

[Steven Rostedt]

Hi Alan,

On Fri, 2011-12-02 at 10:43 -0500, Alan Stern wrote:

> It's possible that this problem is related to wakeup settings.  Have 
> you tried disabling wakeup for the EHCI controllers?

I'm totally ignorant of the inner workings of suspend to ram and how
devices deal with it. How do I disable wakeup for the EHCI controllers?

Also, does wakeup have anything to do with suspend. As the name
suggests, it sounds like its more of a resume thing. But again, I'm
ignorant when it comes to these matters. I just want to point out that
without the script, the machine never makes it to a suspend state.

> 
> This certainly appears to be some sort of bug in the firmware.  Finding 
> it and working around it isn't likely to be easy.  Unbinding (or 
> unloading) ehci-hcd may indeed be the path of least resistance.

I wounder what windows does. Of course, vendors bend over backwards for
MS, so it may not need to do much, or MS does something completely
different. I do have this still as a dual boot with Windows7. I don't
wipe my boxes clean of windows anymore. If I have to pay the damn MS
tax, I might as well keep what I paid for :-p

-- Steve

Re: Suspend and resume on ASUS Laptops

[Alan Stern]

On Fri, 2 Dec 2011, Steven Rostedt wrote:

> Hi Alan,
> 
> On Fri, 2011-12-02 at 10:43 -0500, Alan Stern wrote:
> 
> > It's possible that this problem is related to wakeup settings.  Have 
> > you tried disabling wakeup for the EHCI controllers?
> 
> I'm totally ignorant of the inner workings of suspend to ram and how
> devices deal with it. How do I disable wakeup for the EHCI controllers?

Take a look at the two files

	/sys/bus/pci/devices/0000:00:1[ad].0/power/wakeup

If they contain the word "enabled", write "disabled" to them.  See 
Documentation/ABI/testing/sysfs-devices-power.

> Also, does wakeup have anything to do with suspend. As the name
> suggests, it sounds like its more of a resume thing. But again, I'm
> ignorant when it comes to these matters. I just want to point out that
> without the script, the machine never makes it to a suspend state.

The wakeup setting affects the hardware, which could cause the system 
to hang.  And of course, the wakeup setting has to be installed in the 
hardware during the suspend procedure, so that it will remain in effect 
while the system is asleep.

> > This certainly appears to be some sort of bug in the firmware.  Finding 
> > it and working around it isn't likely to be easy.  Unbinding (or 
> > unloading) ehci-hcd may indeed be the path of least resistance.
> 
> I wounder what windows does.

As in many other cases, it would be nice to know.

>  Of course, vendors bend over backwards for
> MS, so it may not need to do much, or MS does something completely
> different. I do have this still as a dual boot with Windows7. I don't
> wipe my boxes clean of windows anymore. If I have to pay the damn MS
> tax, I might as well keep what I paid for :-p

I know; me too.  Even though I almost never use it.

Alan Stern

Re: Suspend and resume on ASUS Laptops

[Steven Rostedt]

On Fri, 2011-12-02 at 11:23 -0500, Alan Stern wrote:

> Take a look at the two files
> 
> 	/sys/bus/pci/devices/0000:00:1[ad].0/power/wakeup
> 
> If they contain the word "enabled", write "disabled" to them.  See 
> Documentation/ABI/testing/sysfs-devices-power.

The files do exist, but they are already set to "disabled".


> >  Of course, vendors bend over backwards for
> > MS, so it may not need to do much, or MS does something completely
> > different. I do have this still as a dual boot with Windows7. I don't
> > wipe my boxes clean of windows anymore. If I have to pay the damn MS
> > tax, I might as well keep what I paid for :-p
> 
> I know; me too.  Even though I almost never use it.

But it is nice to have to double check if things are screwed up on it
too.

-- Steve

Re: Suspend and resume on ASUS Laptops

[Alan Stern]

On Fri, 2 Dec 2011, Steven Rostedt wrote:

> On Fri, 2011-12-02 at 11:23 -0500, Alan Stern wrote:
> 
> > Take a look at the two files
> > 
> > 	/sys/bus/pci/devices/0000:00:1[ad].0/power/wakeup
> > 
> > If they contain the word "enabled", write "disabled" to them.  See 
> > Documentation/ABI/testing/sysfs-devices-power.
> 
> The files do exist, but they are already set to "disabled".

Bummer.  This sounds like something for the ACPI/BIOS people to work 
on...

Alan Stern

Re: Suspend and resume on ASUS Laptops

[Pavel Machek]

On Fri 2011-12-02 16:57:06, Alan Stern wrote:
> On Fri, 2 Dec 2011, Steven Rostedt wrote:
> 
> > On Fri, 2011-12-02 at 11:23 -0500, Alan Stern wrote:
> > 
> > > Take a look at the two files
> > > 
> > > 	/sys/bus/pci/devices/0000:00:1[ad].0/power/wakeup
> > > 
> > > If they contain the word "enabled", write "disabled" to them.  See 
> > > Documentation/ABI/testing/sysfs-devices-power.
> > 
> > The files do exist, but they are already set to "disabled".
> 
> Bummer.  This sounds like something for the ACPI/BIOS people to work 
> on...

Is "USB legacy emulation" enabled in the BIOS? That caused problems
before...
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

Re: Suspend and resume on ASUS Laptops

[Steven Rostedt]

On Mon, 2011-12-05 at 12:03 +0100, Pavel Machek wrote:

> Is "USB legacy emulation" enabled in the BIOS? That caused problems
> before...

Yes it was set. I turned it off and removed the script but it still
failed to suspend. It locked up the exact same way with that option
enabled.

-- Steve

Re: Suspend and resume on ASUS Laptops

[Michal Jaegermann]

On Fri, Dec 02, 2011 at 10:43:30AM -0500, Alan Stern wrote:
> 
> It's possible that this problem is related to wakeup settings.  Have 
> you tried disabling wakeup for the EHCI controllers?

On my ASUS K52Jc these controllers are also reported "disabled".  This
is after switching to Fedora 16 with its 3.1.2-1 kernel.

After doing these updates I had also to add "ath ath9k" to my list of
SUSPEND_MODULES (which are removed and reinserted in these operations)
or otherwise I will loose my wireless connection on a resume and a
reboot after hibernate will silently die.  In logs I can find

 irq 17: nobody cared (try booting with the "irqpoll" option)
 Pid: 0, comm: swapper Not tainted 3.1.2-1.fc16.x86_64 #1
 Call Trace:
  <IRQ>  [<ffffffff810b2222>] __report_bad_irq+0x38/0xc3
  [<ffffffff810b24bc>] note_interrupt+0x176/0x1fa
  [<ffffffff810b0a0f>] handle_irq_event_percpu+0x15d/0x1a5
  [<ffffffff810b0a92>] handle_irq_event+0x3b/0x59
  [<ffffffff81078268>] ? sched_clock_cpu+0x42/0xc6
  [<ffffffff810b2c7c>] handle_fasteoi_irq+0x80/0xa4
  [<ffffffff81010af9>] handle_irq+0x88/0x8e
  [<ffffffff814c040d>] do_IRQ+0x4d/0xa5
  [<ffffffff814b756e>] common_interrupt+0x6e/0x6e
  <EOI>  [<ffffffff814b71ac>] ? _raw_spin_unlock_irqrestore+0x17/0x19
  [<ffffffff813a5cc3>] ? poll_idle+0x28/0x65
  [<ffffffff813a5cb6>] ? poll_idle+0x1b/0x65
  [<ffffffff813a5fe6>] cpuidle_idle_call+0xe8/0x182
  [<ffffffff8100e2e3>] cpu_idle+0xa4/0xe8
  [<ffffffff81494a8e>] rest_init+0x72/0x74
  [<ffffffff81b76b7d>] start_kernel+0x3ab/0x3b6
  [<ffffffff81b762c4>] x86_64_start_reservations+0xaf/0xb3
  [<ffffffff81b76140>] ? early_idt_handlers+0x140/0x140
  [<ffffffff81b763ca>] x86_64_start_kernel+0x102/0x111
 handlers:
 [<ffffffffa02c0d80>] ath_isr
 Disabling IRQ #17

These "irq 17: nobody cared" were happening before but I could get away
without touching ath and aht9k modules.

   Michal

Re: Suspend and resume on ASUS Laptops

[Alan Stern]

On Fri, 2 Dec 2011, Michal Jaegermann wrote:

> On Fri, Dec 02, 2011 at 10:43:30AM -0500, Alan Stern wrote:
> > 
> > It's possible that this problem is related to wakeup settings.  Have 
> > you tried disabling wakeup for the EHCI controllers?
> 
> On my ASUS K52Jc these controllers are also reported "disabled".  This

What exactly do you mean by that?

> is after switching to Fedora 16 with its 3.1.2-1 kernel.

Alan Stern

Re: Suspend and resume on ASUS Laptops

[Michal Jaegermann]

On Sat, Dec 03, 2011 at 10:19:27AM -0500, Alan Stern wrote:
> On Fri, 2 Dec 2011, Michal Jaegermann wrote:
> > 
> > On my ASUS K52Jc these controllers are also reported "disabled".  This
> 
> What exactly do you mean by that?

I mean that you asked Steven about a content of
/sys/bus/pci/devices/0000\:00\:1[ad].0/power/wakeup
On my ASUS K52Jc these ids also happen to belong to ehci_hcd devices
(both "Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host
Controller") and both 'wakeup' files show "disabled" too.

With that above I have to do all these manipulations with unbinding
and binding drivers and removing inserting modules or a laptop will hang
after a suspend.  Now with a recent kernel I need additionally put
wireless driver modules on a "special handling" list or I will loose
such connection (no hang here, just a dead driver).

All of this looks like pretty consistent, from what one can find on the
net, across various models of ASUS laptops.

   Michal

Re: Suspend and resume on ASUS Laptops

[Alan Stern]

On Sat, 3 Dec 2011, Michal Jaegermann wrote:

> On Sat, Dec 03, 2011 at 10:19:27AM -0500, Alan Stern wrote:
> > On Fri, 2 Dec 2011, Michal Jaegermann wrote:
> > > 
> > > On my ASUS K52Jc these controllers are also reported "disabled".  This
> > 
> > What exactly do you mean by that?
> 
> I mean that you asked Steven about a content of
> /sys/bus/pci/devices/0000\:00\:1[ad].0/power/wakeup
> On my ASUS K52Jc these ids also happen to belong to ehci_hcd devices
> (both "Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host
> Controller") and both 'wakeup' files show "disabled" too.

Oh, sorry -- I didn't realize you meant the power/wakeup file contained 
"disabled".  It sounded like you were saying that the controllers were 
somehow disabled.

> With that above I have to do all these manipulations with unbinding
> and binding drivers and removing inserting modules or a laptop will hang
> after a suspend.  Now with a recent kernel I need additionally put
> wireless driver modules on a "special handling" list or I will loose
> such connection (no hang here, just a dead driver).
> 
> All of this looks like pretty consistent, from what one can find on the
> net, across various models of ASUS laptops.

Yes, apparently ASUS's recent chipsets or firmware has a problem with
suspend and resume.  On the other hand, I'm writing this on an ASUS
UL20A laptop, which suspends and resumes with no difficulty.

Alan Stern

Re: Suspend and resume on ASUS Laptops

[Rafael J. Wysocki]

On Sunday, December 04, 2011, Alan Stern wrote:
> On Sat, 3 Dec 2011, Michal Jaegermann wrote:
> 
> > On Sat, Dec 03, 2011 at 10:19:27AM -0500, Alan Stern wrote:
> > > On Fri, 2 Dec 2011, Michal Jaegermann wrote:
> > > > 
> > > > On my ASUS K52Jc these controllers are also reported "disabled".  This
> > > 
> > > What exactly do you mean by that?
> > 
> > I mean that you asked Steven about a content of
> > /sys/bus/pci/devices/0000\:00\:1[ad].0/power/wakeup
> > On my ASUS K52Jc these ids also happen to belong to ehci_hcd devices
> > (both "Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host
> > Controller") and both 'wakeup' files show "disabled" too.
> 
> Oh, sorry -- I didn't realize you meant the power/wakeup file contained 
> "disabled".  It sounded like you were saying that the controllers were 
> somehow disabled.
> 
> > With that above I have to do all these manipulations with unbinding
> > and binding drivers and removing inserting modules or a laptop will hang
> > after a suspend.  Now with a recent kernel I need additionally put
> > wireless driver modules on a "special handling" list or I will loose
> > such connection (no hang here, just a dead driver).
> > 
> > All of this looks like pretty consistent, from what one can find on the
> > net, across various models of ASUS laptops.
> 
> Yes, apparently ASUS's recent chipsets or firmware has a problem with
> suspend and resume.  On the other hand, I'm writing this on an ASUS
> UL20A laptop, which suspends and resumes with no difficulty.

I wonder, though, who figured out what quirk to use before suspend on those
particular machines and on what basis (some information from the vendor or
what?).

Thanks,
Rafael

Re: Suspend and resume on ASUS Laptops

[Mantas M.]

On 2011-12-03 04:43, Michal Jaegermann wrote:
> After doing these updates I had also to add "ath ath9k" to my list of
> SUSPEND_MODULES (which are removed and reinserted in these operations)
> or otherwise I will loose my wireless connection on a resume and a
> reboot after hibernate will silently die.  In logs I can find
> 
>  irq 17: nobody cared (try booting with the "irqpoll" option)
>  Pid: 0, comm: swapper Not tainted 3.1.2-1.fc16.x86_64 #1
>  Call Trace:
> 
> These "irq 17: nobody cared" were happening before but I could get away
> without touching ath and aht9k modules.

This should have been fixed in commit a7d5b76 (jme: fix irq storm after
suspend/resume) -- at least it worked on my own laptop (K52JT).

-- 
Mantas M.

Re: Suspend and resume on ASUS Laptops

[Steven Rostedt]

On Thu, 2011-12-01 at 15:38 +0100, Oliver Neukum wrote:
> Am Donnerstag, 1. Dezember 2011, 15:28:54 schrieb Steven Rostedt:
> > On Thu, 2011-12-01 at 12:48 +0100, Oliver Neukum wrote:
> > 
> > > What errors are seen in the kernel log?
> > 
> > Without the script, I don't see any errors. Is there some debug thing
> > you want me to do? There's no error messages but the system just hangs
> > on suspend. It never makes it to the suspend state. The only way out of
> > it is to press and hold the power button for 10 seconds to force a hard
> > reboot.
> 
> I see. I thought the system just refuses to enter S3/4. That it hangs was
> new to me. Has there been a mail thread about this problem already?

No idea, but I did reference a website that posted this fix. I'm not
sure how the fix came about, or what discussions were done. The fix
seems to have been made by Ubuntu, which means its just another thing
they looked at without sending upstream :-p

> If not, what is the last thing you see if you go to S3 after you booted
> with no_console_suspend on the kernel command line?

Hmm, no_console_suspend on the kernel command line seems to do nothing.
It still hangs hard without the script, and suspend works fine with the
script.

I noticed that /sys/module/printk/parameters/console_suspend doesn't
exist. Am I missing a kernel config option?

-- Steve

Re: Suspend and resume on ASUS Laptops

[Michal Jaegermann]

On Thu, Dec 01, 2011 at 10:35:57AM +0100, Rafael J. Wysocki wrote:
> On Thursday, December 01, 2011, Steven Rostedt wrote:
> > For Black Friday I bought myself a ASUS-U56E-RBL8 at Staples for a
> > decent price. I installed Linux on it but it would not suspend.
.....
> > 
> > It just seems crazy to have everyday users add this script.
> 
> I totally agree, I had no idea it was necessary.

On  2011-04-16 I filed a pretty similar bug report in Red Hat bugzilla.
It sits here: https://bugzilla.redhat.com/show_bug.cgi?id=697150
still as ASSIGNED.  A kernel was based on 2.6.35 running on Asus K52Jc
but the problem really looks the same.  Assorted additional information
is attached to that bugzilla entry.  There is also
https://bugzilla.redhat.com/show_bug.cgi?id=675564

After all modifications described in my report, which included adding a line
SUSPEND_MODULES="xhci_hcd sdhci_pci sdhci"
in /etc/pm/config.d/hci.cfg I never had suspend/hibernate issues
again.  As a matter of fact I forgot about the problem. :-)

  Michal