From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: "Mihai Donțu" <mihai.dontu@gmail.com>
Cc: linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: 2.6.23-rc7 + radeonfb/s2ram
Date: Sun, 23 Sep 2007 20:20:10 +1000 [thread overview]
Message-ID: <1190542810.3723.27.camel@localhost.localdomain> (raw)
In-Reply-To: <200709221746.14429.mihai.dontu@gmail.com>
On Sat, 2007-09-22 at 17:46 +0300, Mihai Donțu wrote:
> On Saturday 22 September 2007, Mihai Donțu wrote:
> > Hi,
> >
> > Today, out of curiosity, I pulled 2.6.23-rc7 (leave on the edge in a quiet weekend).
> > Anyway, it seems that radeonfb and my:
> > "01:05.0 VGA compatible controller: ATI Technologies Inc ATI Radeon XPRESS 200M 5955 (PCIE)"
> > don't get along anymore, by:
> > a) X somehow fails to initialize the card and everything moves really slow (I can
> > see how surfaces are drawn pixel-by-pixel); furthermore, garbage stuff appears
> > on the screen;
> > b) after powering up from a s2ram, the system freezes;
> >
> > b) is not that bad, s2ram never worked on my machine (kjournald and some other kernel
> > processes, enter disk-sleep and in a matter of seconds, everything just... freezes.
> > I can type a few commands at the normal console but that is all);
> >
> > Following the advices in 'Documentation/power/s2ram.txt' helped. Using the regular
> > VGA console got X on the right track (no more slowness);
> >
> > Now that I got my hands "dirty", I'm in the mood to make my s2ram work (I've
> > been using Linux (exclusively) for three years now, it's about time I do a small
> > contribution). What kernel option must I enable to determine why some processes
> > enter (and stay in) disk-sleep? I'm on a laptop and I don't think it will withstand
> > too many reboots :)
> >
> > I've also attached the output of lspci and dmesg. Maybe someone spots something.
> >
> > Thanks,
> >
>
> Since there was no reply, I assume people *do* take the weekend off :)
Heh, yup.
There have been some radeonfb patches around -rc6 or so. Can you try
backing them out and letting us know if that helps a) ?
In that case, Linus, we probably want to revert them...
Though looking at your PCI ID (5955), I don't think the patches should
have changed anything.
Ben.
next prev parent reply other threads:[~2007-09-23 10:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-22 5:27 2.6.23-rc7 + radeonfb/s2ram Mihai Donțu
2007-09-22 14:46 ` Mihai Donțu
2007-09-23 10:20 ` Benjamin Herrenschmidt [this message]
2007-09-23 16:37 ` Mihai Donțu
2007-09-23 17:51 ` Mihai Donțu
2007-09-23 18:31 ` Mihai Donțu
2007-09-23 19:18 ` Rafael J. Wysocki
2007-09-23 19:22 ` Mihai Donțu
2007-09-23 21:31 ` Oleg Verych
2007-09-24 0:07 ` Benjamin Herrenschmidt
2007-09-24 0:06 ` Benjamin Herrenschmidt
2007-09-24 14:43 ` Andreas Herrmann
2007-09-25 7:09 ` Mihai Donțu
2007-09-25 15:48 ` Randy Dunlap
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=1190542810.3723.27.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mihai.dontu@gmail.com \
--cc=torvalds@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.