From: Pavel Machek <pavel@suse.cz>
To: etienne <etienne.basset@numericable.fr>
Cc: airlied@linux.ie, rjw@sisk.pl, linux-kernel@vger.kernel.org,
dri-devel@lists.sourceforge.net
Subject: Re: [2.6.29-rc3][Suspend regression][DRM, RADEON]
Date: Tue, 3 Feb 2009 14:55:54 +0100 [thread overview]
Message-ID: <20090203135554.GA1560@ucw.cz> (raw)
In-Reply-To: <4980D58F.8010105@numericable.fr>
>> Are there any patch i could try?
>> Is it possible to run a git bisect excluding all drm commits to find
>> the other bug?
> hello,
>
> I tried 2.6.29-rc3, and things got a little better. Suspend/resume
> results in a garbage video, but now i have access to my desktop via SSH
> after resume; so only X/drm seems to be broken after resume.
> I (re)did the stupid replace of driver/gpu/drm and include /drm by
> 2.6.28 files, and have now been able to suspend/resume a few time.
> So in rc1-rc2 I had multiple bugs preventing me from STR, now there's
> only one left in DRM. My initial bisect was perhaps not so useless after
> all?
>
> Is it possible to run a bisect only for DRM changes? are there any logs,
> additionnal info I can provide?
I think git bisect can do that, yes.
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
prev parent reply other threads:[~2009-02-03 13:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-17 13:39 [2.6.29-rc2][Suspend regression][DRM ???? bisected] etienne
2009-01-19 21:05 ` etienne
2009-01-19 21:37 ` Rafael J. Wysocki
2009-01-28 22:00 ` [2.6.29-rc3][Suspend regression][DRM, RADEON] etienne
2009-02-03 13:55 ` Pavel Machek [this message]
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=20090203135554.GA1560@ucw.cz \
--to=pavel@suse.cz \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.sourceforge.net \
--cc=etienne.basset@numericable.fr \
--cc=linux-kernel@vger.kernel.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