dri-devel.lists.freedesktop.org archive mirror
 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: Thu, 29 Mar 2012 22:07:19 GMT	[thread overview]
Message-ID: <201203292207.q2TM7JSa021440@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-42678-2300@https.bugzilla.kernel.org/>

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


Adrien Nader <camaradetux@gmail.Com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |camaradetux@gmail.Com




--- Comment #9 from Adrien Nader <camaradetux@gmail.Com>  2012-03-29 22:07:17 ---
I think I'm hitting the same issue but I'm reproducing it very easily.
Basically, I start the computer, KDM, KDE, and boom.

  http://notk.org/~adrien/heat_issue/lockup/dmesg

As for X, I'm using xf86-video-ati 6.14.4 which came out today, and libdrm
2.4.33, along with xorg-server 1.12.0.

I'll try with a 3.2.12 kernel tomorrow instead of my 3.3.0+ (middle of the
merge window for 3.4). I'm fairly motivated to get this sorted out.

-- 
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-03-29 22:07 UTC|newest]

Thread overview: 24+ 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 [this message]
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
2013-05-01 17:50 ` bugzilla-daemon
2013-07-12 20:13 ` 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=201203292207.q2TM7JSa021440@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).