linux-kernel - Re: 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-prev] [thread-next>] [day] [month] [year] [list]

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

On Sun, Nov 22, 2009 at 9:15 AM, Rafael J. Wysocki <rjw@...k.pl> 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).]

You are using radeonfb on it? or vesafb?

first test is to try without either of those installed.

>From memory though that machines an Xpress 200M which is the the worst
graphics card for use with open drivers and has always caused no-end of pain.

Its also mostly undocumented when it comes to errata and workarounds.

Dave.
--
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/