From: Michal Hocko <mhocko@suse.cz>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: linux-pm@vger.kernel.org, Len Brown <len.brown@intel.com>,
Pavel Machek <pavel@ucw.cz>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: 3.10-rc1 system starts regular boot when waking from s2ram
Date: Wed, 15 May 2013 10:01:22 +0200 [thread overview]
Message-ID: <20130515080122.GC8625@dhcp22.suse.cz> (raw)
In-Reply-To: <1368567715.t1rym2H3RB@vostro.rjw.lan>
On Tue 14-05-13 22:09:34, Rafael J. Wysocki wrote:
> On Tuesday, May 14, 2013 06:01:08 PM Michal Hocko wrote:
> > 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?
>
> 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...
> Anyway, the general PM changes essentially are not so invasive as to cause
> something like this to happen, so I'm kind of suspecting x86.
>
> Thanks,
> Rafael
>
>
> --
> I speak only for myself.
> Rafael J. Wysocki, Intel Open Source Technology Center.
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2013-05-15 8:01 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-14 16:01 Michal Hocko
2013-05-14 20:09 ` Rafael J. Wysocki
2013-05-15 8:01 ` Michal Hocko [this message]
2013-05-15 8:29 ` Pavel Machek
2013-05-15 9:05 ` Pavel Machek
2013-05-15 9:56 ` Michal Hocko
2013-05-17 7:54 ` Michal Hocko
2013-05-17 12:11 ` Rafael J. Wysocki
2013-05-17 12:09 ` Michal Hocko
2013-05-17 12:23 ` Rafael J. Wysocki
2013-05-17 12:30 ` Michal Hocko
2013-05-15 13:17 ` CONFIG_HYPERVISOR_GUEST=y {-- replace -- CONFIG_PARAVIRT_GUEST=y {= { # CONFIG_HYPERVISOR_GUEST is not set } Re: 3.10-rc1 system starts regular boot when waking from s2ram Fw: [PATCH 2/2] x86: Make Linux guest support optional Victor Miasnikov
2013-05-15 13:34 ` Michal Hocko
2013-05-15 13:44 ` Victor Miasnikov
2013-05-15 13:46 ` Michal Hocko
2013-05-15 14:05 ` CONFIG_HYPERVISOR_GUEST=y {-- replace -- CONFIG_PARAVIRT_GUEST=y {= { # CONFIG_HYPERVISOR_GUEST is not set } Re: 3.10-rc1 " Victor Miasnikov
2013-05-15 14:21 ` Borislav Petkov
2013-05-15 14:52 ` Victor Miasnikov
2013-05-15 17:34 ` Luck, Tony
2013-05-20 15:03 ` [PATCH] Revert "x86-64, init: Do not set NX bits on non-NX capable hardware" Michal Hocko
2013-05-20 15:58 ` H. Peter Anvin
2013-05-20 16:43 ` Michal Hocko
2013-05-20 17:21 ` Linus Torvalds
2013-05-20 18:13 ` H. Peter Anvin
2013-05-20 18:18 ` Linus Torvalds
2013-05-20 18:19 ` H. Peter Anvin
2013-05-20 18:23 ` Michal Hocko
2013-05-20 18:30 ` H. Peter Anvin
2013-05-20 18:31 ` Michal Hocko
2013-05-20 18:31 ` Linus Torvalds
2013-05-20 18:36 ` H. Peter Anvin
2013-05-20 18:42 ` [tip:x86/urgent] x86-64: Make early_pmd_flags __cpuinitdata tip-bot for H. Peter Anvin
2013-05-20 18:50 ` tip-bot for H. Peter Anvin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130515080122.GC8625@dhcp22.suse.cz \
--to=mhocko@suse.cz \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®