public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: "Arend van Spriel" <arend@broadcom.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Linux PM list <linux-pm@vger.kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Hante Meuleman <meuleman@broadcom.com>
Subject: Re: Linux 3.7-rc3
Date: Tue, 30 Oct 2012 11:10:34 +0100	[thread overview]
Message-ID: <508FA79A.3030309@broadcom.com> (raw)
In-Reply-To: <26004880.qboZkUVCy9@vostro.rjw.lan>

On 10/30/2012 01:10 AM, Rafael J. Wysocki wrote:
> On Sunday, October 28, 2012 12:59:49 PM Linus Torvalds wrote:
>> It's been a week, time for -rc3!
>>
>> Nothing particularly stands out here. Lots of small fixes, exemplified
>> by the series of memory leak fixes in usb serial drivers. Just a lot
>> of random stuff..
>>
>> Most of it is drivers (all over: drm, wireless, staging, usb, sound),
>> but there's a few filesystem updates (nfs, btrfs, ext4), arch updates
>> (arm, x86 and m68k) and just random stuff. Shortlog appended.
>
> Unfortunately, s2disk is broken with this one and previous -rc.  In the
> majority of cases it just hangs the machine during hibernation, although
> sometimes it returns to user space reporting freezing problems, suspicions
> RCU usage and similar stuff, pretty much without any useful debug information.
>
> I'm quite confident that v3.6 was OK (and -stable based on that too), so
> it most likely is a recent regression.  The in-kernel hibernation
> (ie. "echo disk > /sys/power/state") works no problem.  So does suspend to
> RAM on my test boxes.

Since v3.7-rc1 I am seeing suspend to RAM fail as well. It was obscured 
by a nouveau recursive locking issue on my machine. I reverted the 3.7 
DRM merged completely. From there "echo mem > /sys/power/state" works, 
but choosing suspend like most mere mortals do results in suspend, but 
attempt to resume brings me straight to the BIOS starting anew.

> So far I have been able to reproduce this 100% of the time on two machines
> with Intel CPUs and graphics driven by i915.  I _suspect_ that this may be
> related to VT switching, because s2disk does some ugly things in that area
> which are not done by the in-kernel code.  Dunno.
>
> Anyway, it looks like nothing short of bisection is going to help debug this,
> but I'm afraid I won't have the time to bisect within the next two weeks, so if
> anyone can reproduce this issue and will be able to bisect it, please help
> (openSUSE/Tumbleweed users anyone?).
>
> Thanks,
> Rafael
>
>

Not sure if it has the same root cause. Since DRM revert did not work 
for me I put my money on ACPI (not a lot of money though ;-) ).

Gr. AvS


  parent reply	other threads:[~2012-10-30 10:10 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CA+55aFwwTc4QXKqiECgE9NOE2zjC6GsGHHydGP9YDbgQSbw9Aw@mail.gmail.com>
2012-10-30  0:10 ` Linux 3.7-rc3 Rafael J. Wysocki
2012-10-30  9:50   ` Jiri Kosina
2012-10-30 12:53     ` Michal Hocko
2012-10-30 10:10   ` Arend van Spriel [this message]
2012-10-30 11:05   ` Hugo Mills
2012-11-02 20:25   ` Linus Torvalds
2012-11-02 20:35     ` Rafael J. Wysocki
2012-11-02 21:07     ` Daniel Vetter
2012-11-02 21:40       ` Rafael J. Wysocki
2012-11-02 21:43         ` Daniel Vetter
2012-11-02 21:56           ` Rafael J. Wysocki
2012-11-02 22:23             ` Rafael J. Wysocki
2012-11-02 22:26               ` Linus Torvalds
2012-11-02 22:43                 ` Rafael J. Wysocki
2012-11-02 23:10                   ` Linus Torvalds
2012-11-03 16:35                     ` Alan Stern
2012-11-07 22:22                     ` Paul E. McKenney
2012-11-07 22:35                       ` Rafael J. Wysocki

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=508FA79A.3030309@broadcom.com \
    --to=arend@broadcom.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=meuleman@broadcom.com \
    --cc=rjw@sisk.pl \
    --cc=torvalds@linux-foundation.org \
    /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