linux-kernel - Weird suspend/resume problem on HP nx6325 w/ openSUSE 11.2 w/ -rc8

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <200911220015.30912.rjw@sisk.pl>
Date:	Sun, 22 Nov 2009 00:15:30 +0100
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	LKML <linux-kernel@...r.kernel.org>
Cc:	pm list <linux-pm@...ts.linux-foundation.org>,
	DRI <dri-devel@...ts.sourceforge.net>,
	Dave Airlie <airlied@...il.com>
Subject: Weird suspend/resume problem on HP nx6325 w/ openSUSE 11.2 w/ -rc8

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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/