linux-kernel - 3.10-rc1 system starts regular boot when waking from s2ram

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <20130514160108.GA5055@dhcp22.suse.cz>
Date:	Tue, 14 May 2013 18:01:08 +0200
From:	Michal Hocko <mhocko@...e.cz>
To:	linux-pm@...r.kernel.org
Cc:	Len Brown <len.brown@...el.com>, Pavel Machek <pavel@....cz>,
	"Rafael J. Wysocki" <rjw@...k.pl>,
	LKML <linux-kernel@...r.kernel.org>
Subject: 3.10-rc1 system starts regular boot when waking from s2ram

Hi,
I am not able to make my system wake up from s2ram with 3.10-rc1. The
system simply starts booting as if it wasn't suspended. 3.9 works
without any issues.

pm_test testing (with no_console_suspend) shows that platform is the
last mode which wakes up normally. processors mode already starts with a
regular boot. The log doesn't say anything interesting:

$ echo processors > /sys/power/pm_test
$ echo mem > /sys/power/state
[   61.012533] PM: Syncing filesystems ... done.
[   61.017944] Freezing user space processes ... (elapsed 0.01 seconds) done.
[   61.033050] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.
[   61.081647] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[   61.081724] sd 0:0:0:0: [sda] Stopping disk

then it waits for 5s as expected and starts booting from scratch without
anything in the log.

Same test with
$ echo platform > /sys/power/pm_test
$ echo mem > /sys/power/state
[   34.960477] PM: Syncing filesystems ... done.
[   34.967624] Freezing user space processes ... (elapsed 0.01 seconds) done.
[   34.983936] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.
[   35.056655] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[   35.056800] sd 0:0:0:0: [sda] Stopping disk
[   41.255957] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[   41.316267] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[   41.316354] ata5: SATA link down (SStatus 0 SControl 300)
[   41.316428] ata4: SATA link down (SStatus 0 SControl 300)
[   41.316507] ata6: SATA link down (SStatus 0 SControl 300)
[   41.316958] ata1.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device (Stat=0x51 Err=0x04)
[   41.388315] ata1.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device (Stat=0x51 Err=0x04)
[   41.389142] ata1.00: configured for UDMA/133
[   41.391172] ata2.00: configured for UDMA/100
[   41.396198] sd 0:0:0:0: [sda] Starting disk
[   41.396533] iwlwifi 0000:02:00.0: L1 Enabled; Disabling L0S
[   41.396767] iwlwifi 0000:02:00.0: Radio type=0x0-0x3-0x1
[   41.638698] PM: resume of devices complete after 724.548 msecs
[   41.638835] Restarting tasks ... done.
[   41.640747] video LNXVIDEO:00: Restoring backlight state
[   42.848988] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
[   42.850380] e1000e 0000:00:19.0 eth0: Detected Hardware Unit Hang:
[   42.850380]   TDH                  <0>
[   42.850380]   TDT                  <11>
[   42.850380]   next_to_use          <11>
[   42.850380]   next_to_clean        <0>
[   42.850380] buffer_info[next_to_clean]:
[   42.850380]   time_stamp           <ffff034b>
[   42.850380]   next_to_watch        <0>
[   42.850380]   jiffies              <ffff04d9>
[   42.850380]   next_to_watch.status <0>
[   42.850380] MAC Status             <80000>
[   42.850380] PHY Status             <7949>
[   42.850380] PHY 1000BASE-T Status  <0>
[   42.850380] PHY Extended Status    <3000>
[   42.850380] PCI Status             <10>
[   44.066855] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx

Is the issue known? Can I provide more information to help with
debugging this issue. I am quite busy to bisect this ATM but can do it
if this is the only choice left.

Thanks
-- 
Michal Hocko
SUSE Labs

View attachment "config-3.10.0-rc1-fullnohzdisabled" of type "text/plain" (82837 bytes)

View attachment "dmesg-3.10.0-rc1-fullnohzdisabled" of type "text/plain" (51320 bytes)