From: "Justin P. Mattock" <justinmattock@gmail.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: pm list <linux-pm@lists.linux-foundation.org>,
DRI <dri-devel@lists.sourceforge.net>,
Dave Airlie <airlied@gmail.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Weird suspend/resume problem on HP nx6325 w/ openSUSE 11.2 w/ -rc8
Date: Sat, 21 Nov 2009 15:21:32 -0800 [thread overview]
Message-ID: <4B0875FC.80705@gmail.com> (raw)
In-Reply-To: <200911220015.30912.rjw@sisk.pl>
[-- Attachment #1.1: Type: text/plain, Size: 2089 bytes --]
On 11/21/09 15:15, Rafael J. Wysocki wrote:
> Hi,
>
> I'm not really sure where this should be reported, but here it goes.
>
> After installing openSUSE 11.2 on my testbed nx6325 I noticed that resume
> (from suspend to RAM) stopped working on it. Apparently, it hanged while
> switching from the console back to X and the box remained completely
> unresponsive after that (it didn't even react to the magic sysrq). However,
> it used to work just fine with -rc7 and openSUSE 11.1, so I figured the problem
> was related to the new X driver, which is radeon module version 6.12.4 (xorg
> server 1.6.5).
>
> So, I started to investigate and found that after a suspend from a framebuffer
> console, the resume had always worked. However, when I switched from X to the
> framebuffer console, suspended, resumed and switched back to X, the box hanged
> immediately just like during resume after a suspend from under X. [There also
> were some problems when switching from X to the framebuffer console and back
> which seemd to be independent of suspend/resume (in short, the screen stays
> black after a switch from the framebuffer console to X and you need to kill X
> to fix this).]
>
> Later, however, I discovered that if the box was booted into runlevel 3, then
> suspended to RAM and resumed, and then switched to runlevel 5, I could log
> into X and suspend/resume without any problems for many times. OTOH, after
> booting directly into X, the first attempt to resume always resulted in a black
> screen and a hard hang.
>
> I wonder what's up in there.
>
> [Hibernation/resume works 100% of the time AFAICS.]
>
> Thanks,
> Rafael
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
>
I just noticed today that on my macbook(radeon) using
s2ram works, but I get a long pause(black screen) before
the screen shows up.(latest stable release works fine).
Justin P. Mattock
[-- Attachment #1.2: Type: text/html, Size: 2607 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next parent reply other threads:[~2009-11-21 23:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200911220015.30912.rjw@sisk.pl>
2009-11-21 23:21 ` Justin P. Mattock [this message]
2009-11-22 3:55 ` Weird suspend/resume problem on HP nx6325 w/ openSUSE 11.2 w/ -rc8 Dave Airlie
[not found] ` <21d7e9970911211955i69c12969n3085b6fc2c4a95f9@mail.gmail.com>
2009-11-27 1:04 ` Rafael J. Wysocki
[not found] ` <200911270204.15100.rjw@sisk.pl>
2009-11-27 20:02 ` Justin Mattock
2009-11-21 23:15 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=4B0875FC.80705@gmail.com \
--to=justinmattock@gmail.com \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--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