All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Marius Gröger" <marius.groeger@googlemail.com>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: Suspend lockup: How to bisect d-r-t specific commits?
Date: Tue, 20 Jul 2010 13:15:46 +0200	[thread overview]
Message-ID: <4C458562.4070207@googlemail.com> (raw)
In-Reply-To: <AANLkTimaSqiOANcgopajlkSW3NfECP8CEE5uJS1jd4Vp@mail.gmail.com>

Am 20.07.2010 12:14, schrieb Rafał Miłecki:
> I've installed openSUSE 11.3 which comes with 2.6.34 kernel and added
> 2.6.35-rc5 from package. In both cases suspending and resuming works
> fine.
>
> Then I downloaded 2.6.35-rc5 and compiled it myself. Suspending and
> resuming works fine.
>
> When trying d-r-t with the same config my machine locks up on
> suspending, just before machine is expected to turn off.
>
> How can I use "git bisect" command to bisect d-r-t specific commits?

Fwiw, for me (HD3200, RS780) current d-r-t resume from suspend to ram 
does not work. Last thing it shows is the text console with some random 
colored pixels, but not the X display where it was suspended from. It 
appeared liked the kernel was still running, but X was completely 
crashed and stuck. I haven't had the time yet to further debug this.

Regards
Marius
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2010-07-20 11:15 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-20 10:14 Suspend lockup: How to bisect d-r-t specific commits? Rafał Miłecki
2010-07-20 11:15 ` Marius Gröger [this message]
2010-07-20 21:23   ` Rafał Miłecki
2010-07-20 21:37     ` Rafał Miłecki
2010-07-20 22:36       ` Dave Airlie
2010-07-21  9:30         ` Rafał Miłecki
2010-07-21 14:21           ` Rafał Miłecki
2010-07-21 17:23             ` Alex Deucher
2010-07-24  8:38               ` Rafał Miłecki
2010-07-24 20:41                 ` Alex Deucher
2010-07-25 12:14                   ` Rafał Miłecki
2010-07-26  5:57                     ` Alex Deucher
2010-07-26 12:02                       ` Rafał Miłecki
2010-07-26 18:55                         ` Alex Deucher
2010-07-26 23:26                           ` Rafał Miłecki
2010-07-26 23:33                             ` Alex Deucher
2010-07-27 15:27                             ` Alex Deucher
2010-07-27 21:53                               ` Rafał Miłecki
2010-07-27 21:53                                 ` Rafał Miłecki
2010-07-27 23:01                                 ` Alex Deucher
2010-07-28  8:44                                   ` Rafał Miłecki
2010-07-28 14:13                                     ` Alex Deucher
2010-07-20 16:21 ` Alex Deucher
2010-07-20 18:13   ` Rafał Miłecki
2010-07-20 18:44     ` Alex Deucher
2010-07-20 20:22       ` Rafał Miłecki

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=4C458562.4070207@googlemail.com \
    --to=marius.groeger@googlemail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=zajec5@gmail.com \
    /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.