kernel-testers.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alan Jenkins <alan-jenkins@tuffmail.co.uk>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: pm list <linux-pm@lists.linux-foundation.org>,
	Kernel Testers List <kernel-testers@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Jesse Barnes <jbarnes@virtuousgeek.org>,
	Stefan Seyfried <stefan.seyfried@googlemail.com>
Subject: Re: 2.6.32-rc1: various BUGs on resume from hibernation
Date: Tue, 06 Oct 2009 09:58:48 +0100	[thread overview]
Message-ID: <4ACB06C8.9030209@tuffmail.co.uk> (raw)
In-Reply-To: <200910060048.41615.rjw@sisk.pl>

Rafael J. Wysocki wrote:
> On Monday 05 October 2009, Alan Jenkins wrote:
>   
>> Alan Jenkins wrote:
>>     
>>> Stefan Seyfried wrote:
>>>       
>>>> On Sun, 4 Oct 2009 22:47:43 +0200
>>>> "Rafael J. Wysocki" <rjw@sisk.pl> wrote:
>>>>         
>>>>> On Sunday 04 October 2009, Alan Jenkins wrote:
>>>>>           
>>>>>> Alan Jenkins wrote:
>>>>>>             
>>>>>>> I'm seeing a variety of BUGs on my EeePC 701 after hibernation. 
>>>>>>> Sometimes they cause a hang during resume; sometimes they happen
>>>>>>> just after resume. It doesn't happen all the time either - I've
>>>>>>> just hibernated three times in a row with no problems. It's most
>>>>>>> perplexing.
>>>>>>>               
>>>>> As I already asked in the Bugzilla, can you verify that this is
>>>>> reproducible without KMS?
>>>>>           
>>> No. I couldn't reproduce it without KMS. Then I re-enabled KMS, 
>>> hibernated a couple of times, and had another resume hang (different 
>>> again - this time in the freezer).
>>>
>>>       
>> Perhaps this GEM backtrace is more relevant than the others, or perhaps 
>> not. I closed the lid during resume from hibernation; the screen stayed 
>> black when I re-opened it, but syslogd recorded the following. (Again, 
>> I've done the exact thing before and often nothing unusual happens) -
>>     
>
> OK, let's assume it's related to KMS, then.
>
> 1. Do we already have a Bugzilla entry for it?
> 2. Did it work with 2.6.31 (and with KMS)?
>   

I thought so, but my recollection is hazy.  I didn't test it for very
long if I did.  I've tried it now and 2.6.31 behaves pretty similarly. 
Sorry for ringing the regression bell.

Firstly the _hibernation_ process hung (after a couple of suspend-to-ram
cycles).

No text on the console (despite using s2disk).  It echoed keypresses and
responds to SysRq keys.  No messages from lockdep or the hung task
detector (after waiting 5 minutes).  SysRq-P said we're in the idle
loop; SysRq-T said both events/0 and hald-addon-input were runnable.

Then suspend-to-ram hung (following a hibernation cycle).  This time it
showed the contents of vt1, but didn't appear to respond to anything
short of SysRq+B.


> 3. Are you aware of http://marc.info/?l=linux-kernel&m=125452324520623&w=4 ?
>
> Thanks,
> Rafael
>   

I guess there's no connection.  That issue seems to be about generally
flickery screens.  I've seen a few rare flickers that might be related. 
But in general nothing bad happens until I try to suspend, and the
badness is in the form of random crashes or hangs.

Also that bug is confirmed to be a regression, and my issue isn't :-).

Many thanks
Alan

      parent reply	other threads:[~2009-10-06  8:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4AC8B4A8.3050601@tuffmail.co.uk>
2009-10-04 17:03 ` 2.6.32-rc1: various BUGs on resume from hibernation Alan Jenkins
2009-10-04 20:47   ` Rafael J. Wysocki
2009-10-05  7:53     ` Stefan Seyfried
2009-10-05  8:08       ` Alan Jenkins
2009-10-05  8:10         ` Alan Jenkins
2009-10-05 20:02       ` Alan Jenkins
2009-10-05 20:59         ` Alan Jenkins
2009-10-05 22:48           ` Rafael J. Wysocki
2009-10-06  0:06             ` Rafael J. Wysocki
2009-10-06  8:58             ` Alan Jenkins [this message]

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=4ACB06C8.9030209@tuffmail.co.uk \
    --to=alan-jenkins@tuffmail.co.uk \
    --cc=jbarnes@virtuousgeek.org \
    --cc=kernel-testers@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=rjw@sisk.pl \
    --cc=stefan.seyfried@googlemail.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).