From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 33309] [855GM] GPU freeze due to overlay hang
Date: Mon, 09 Jul 2012 18:18:52 +0000 [thread overview]
Message-ID: <bug-33309-502-chmqyAB87U@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-33309-502@http.bugs.freedesktop.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=33309
--- Comment #30 from stefan <fdo.12.bendus@xoxy.net> 2012-07-09 11:18:52 PDT ---
Hi Daniel,
(In reply to comment #29)
> (In reply to comment #28)
> > are there any news on this issue?
> > The 3.4 and 3.5-rc series seem stable wrt this issue,
> > but unfortunately something broke resume from s2ram badly,
> > the backlight stays off and the machine does not respond
> > even to SysRq and I need to do a hard power-off.
>
> That's good&bad news. Can you try to bisect the backlight regression that has
> been introduce in 3.4 and open a new bug report? That usually helps in fixing
> it ...
It turns out to be an ACPICA regression not related to graphics at all.
As for this issue, I did not observe any more hangs with v3.4 or 3.5-rc, *yet*.
It is hard to tell for sure since it usually takes a while (sometimes hours)
for it to occure. Which makes it also almost impossible to bisect and to find
the commit that might have fixed it.
Cheers,
Stefan.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2012-07-09 11:18 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-33309-502@http.bugs.freedesktop.org/>
2011-09-08 22:55 ` [Bug 33309] [855GM] GPU freeze due to overlay hang bugzilla-daemon
2011-09-09 6:50 ` bugzilla-daemon
2011-09-09 9:20 ` bugzilla-daemon
2011-09-09 9:20 ` bugzilla-daemon
2012-03-26 20:17 ` bugzilla-daemon
2012-03-26 20:40 ` bugzilla-daemon
2012-04-14 14:22 ` bugzilla-daemon
2012-04-26 14:48 ` bugzilla-daemon
2012-04-26 14:50 ` bugzilla-daemon
2012-05-14 20:52 ` bugzilla-daemon
2012-05-14 20:58 ` bugzilla-daemon
2012-05-15 19:58 ` bugzilla-daemon
2012-05-15 19:59 ` bugzilla-daemon
2012-05-15 20:00 ` bugzilla-daemon
2012-05-15 20:01 ` bugzilla-daemon
2012-05-15 20:02 ` bugzilla-daemon
2012-05-15 20:03 ` bugzilla-daemon
2012-05-15 20:03 ` bugzilla-daemon
2012-05-15 20:04 ` bugzilla-daemon
2012-05-15 20:08 ` bugzilla-daemon
2012-05-15 20:16 ` bugzilla-daemon
2012-05-15 20:18 ` bugzilla-daemon
2012-07-02 20:13 ` bugzilla-daemon
2012-07-02 20:29 ` bugzilla-daemon
2012-07-09 18:18 ` bugzilla-daemon [this message]
2012-07-09 18:37 ` bugzilla-daemon
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=bug-33309-502-chmqyAB87U@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.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