From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Dave Airlie <airlied@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
pm list <linux-pm@lists.linux-foundation.org>,
DRI <dri-devel@lists.sourceforge.net>
Subject: Re: Weird suspend/resume problem on HP nx6325 w/ openSUSE 11.2 w/ -rc8
Date: Fri, 27 Nov 2009 02:04:15 +0100 [thread overview]
Message-ID: <200911270204.15100.rjw@sisk.pl> (raw)
In-Reply-To: <21d7e9970911211955i69c12969n3085b6fc2c4a95f9@mail.gmail.com>
On Sunday 22 November 2009, Dave Airlie wrote:
> On Sun, Nov 22, 2009 at 9:15 AM, Rafael J. Wysocki <rjw@sisk.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?
vesafb
> first test is to try without either of those installed.
That doesn't change the behavior AFAICS.
> From memory though that machines an Xpress 200M
Yes, it has this one.
> which is the the worst graphics card for use with open drivers and has
> always caused no-end of pain.
Too bad. :-(
> Its also mostly undocumented when it comes to errata and workarounds.
Well, so I guess this is a hardware errata.
Still, it worked with the older X, so I wonder if I can make the new X work
like the old one?
Best,
Rafael
next prev parent reply other threads:[~2009-11-27 1:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-21 23:15 Rafael J. Wysocki
2009-11-22 3:55 ` Dave Airlie
2009-11-27 1:04 ` Rafael J. Wysocki [this message]
2009-11-27 20:02 ` Justin Mattock
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=200911270204.15100.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.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
all inboxes | Powered by JetHome®