Messages in this thread | | | Date | Wed, 15 May 2013 10:29:47 +0200 | From | Pavel Machek <> | Subject | Re: 3.10-rc1 system starts regular boot when waking from s2ram |
| |
Hi!
> > > $ 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? > > > > No. > > > > > Can I provide more information to help with debugging this issue. > > > > I'm not sure. > > > > > I am quite busy to bisect this ATM but can do it > > > if this is the only choice left. > > > > Well, it probably is. I'll try to reproduce it, but if I can't ... > > OK, I am bisecting now. 6 iterations left...
Do you have any watchdog active? Resume got slower and someone bisected it:
Date: Sat, 11 May 2013 20:04:50 +0200 From: Bj??rn Mork <bjorn@mork.no> To: "Paul E. McKenney" <paul.mckenney@linaro.org> Cc: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>, linux-kernel@vger.kernel.org Subject: Bisected post-3.9 regression: Resume takes 5 times as much time as with v3.9 User-Agent: Gnus/5.11002 (No Gnus v0.20) Emacs/23.4 (gnu/linux)
[-- Attachment #1 --] [-- Type: text/plain, Encoding: quoted-printable, Size: 1.6K --]
Hello,
resuming from system suspend is intolerably slow in current mainline. I am not the most patient person around, and I actually started out bisecting this believing it was hanging... Turned out it wasn't really hanging. It just took 15 seconds to wake up from suspend-to-ram. Timing v3.9 I found that it used less than 3 seconds on this ancient laptop I'm using.
Bisecting it ended up pointing to
commit c0f4dfd4f90f1667d234d21f15153ea09a2eaa66
-- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
| |