All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 42678] [3.3-rc1] radeon stuck in kernel after lockup
Date: Fri, 4 May 2012 17:27:16 GMT	[thread overview]
Message-ID: <201205041727.q44HRGia009728@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-42678-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=42678


Alexandre Demers <alexandre.f.demers@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |alexandre.f.demers@gmail.co
                   |                            |m




--- Comment #20 from Alexandre Demers <alexandre.f.demers@gmail.com>  2012-05-04 17:27:14 ---
As a side note, it could be related to Bug 45018. For me, it all started at the
same time. Since, it happens a lot less with latest drm, ddx, mesa, kernel and
X server, but it still happens from time to time randomly. As I was saying it
may be related, or not, but since everything happened at the same time as Bug
45018 and using a 3.2 kernel fixes most of what I see, I think there is a
similar root to all this. I can usually reproduce the lockup followed by a
stucked X by playing a movie (this is the easiest way I've been able to do it
or with what I reported in bug 45018). It often locks up after nearly 40
minutes of video. In a few seconds, image skips, turns greenish on some parts,
and BAM! Locks up, resets and hangs with X unable to come back on its feet.
Lately, in some occasions, it was able to get in X, but everything related to
3D is then dead.

I may have missed it, but which video card/chipset is Maciej using? Radeon 6950
over here.

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

  parent reply	other threads:[~2012-05-04 17:27 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-28 15:16 [Bug 42678] New: [3.3-rc1]radeon 0000:07:00.0: GPU lockup CP stall for more than 10000msec bugzilla-daemon
2012-01-28 15:16 ` [Bug 42678] " bugzilla-daemon
2012-01-28 18:27 ` [Bug 42678] [3.3-rc1] radeon stuck in kernel after lockup bugzilla-daemon
2012-01-29 20:31 ` bugzilla-daemon
2012-02-04  8:39 ` bugzilla-daemon
2012-02-06 22:11 ` bugzilla-daemon
2012-02-07  6:59 ` bugzilla-daemon
2012-02-23 22:32 ` bugzilla-daemon
2012-02-24  2:53 ` bugzilla-daemon
2012-02-24  8:42 ` bugzilla-daemon
2012-03-29 22:07 ` bugzilla-daemon
2012-03-29 22:57 ` bugzilla-daemon
2012-04-03 19:38 ` bugzilla-daemon
2012-04-03 21:24 ` bugzilla-daemon
2012-04-04 12:43 ` bugzilla-daemon
2012-05-03 11:17 ` bugzilla-daemon
2012-05-04  8:10 ` bugzilla-daemon
2012-05-04 12:50 ` bugzilla-daemon
2012-05-04 13:04 ` bugzilla-daemon
2012-05-04 13:08 ` bugzilla-daemon
2012-05-04 14:21 ` bugzilla-daemon
2012-05-04 17:27 ` bugzilla-daemon [this message]
2013-05-01 17:50 ` bugzilla-daemon
2013-07-12 20:13 ` bugzilla-daemon
  -- strict thread matches above, loose matches on Subject: below --
2012-02-23 22:51 3.3-rc4+: Reported regressions from 3.2 Rafael J. Wysocki
2012-02-23 22:55 ` [Bug #42678] [3.3-rc1] radeon stuck in kernel after lockup Rafael J. Wysocki
2012-02-24  9:14   ` Torsten Kaiser
2012-02-24  9:14     ` Torsten Kaiser
2012-03-04 20:29 3.3-rc6: Reported regressions from 3.2 Rafael J. Wysocki
2012-03-04 20:31 ` [Bug #42678] [3.3-rc1] radeon stuck in kernel after lockup Rafael J. Wysocki
2012-03-04 20:31   ` Rafael J. Wysocki
2012-03-11 21:23 3.3-rc7: Reported regressions from 3.2 Rafael J. Wysocki
2012-03-11 21:23 ` [Bug #42678] [3.3-rc1] radeon stuck in kernel after lockup Rafael J. Wysocki
2012-03-11 21:23   ` Rafael J. Wysocki
2012-03-12 19:15   ` Torsten Kaiser
2012-03-12 19:15     ` Torsten Kaiser

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=201205041727.q44HRGia009728@bugzilla.kernel.org \
    --to=bugzilla-daemon@bugzilla.kernel.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 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.