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: Wed, 4 Apr 2012 12:43:53 GMT	[thread overview]
Message-ID: <201204041243.q34ChrAG004297@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-42678-2300@https.bugzilla.kernel.org/>

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





--- Comment #13 from Adrien Nader <camaradetux@gmail.Com>  2012-04-04 12:43:51 ---
My previous comment was missing some bits because of my lack of sleep.

My first issue was that, with a new laptop, which has two AMD cards (one
integrated, one discrete), the both cards are enabled and running even though
it's the integrated one which is actually used. That makes the laptop use a lot
more power than it should and it gets very hot.

I finally found out that I could save a lot of power by using vga_switcheroo to
switch to the dedicated card and then to the integrated one. That saves almost
45W of power consumption.

However, when I start X, even with only twm, I get MANY MANY MANY lockups as
soon as X is starting. At some point, X seems unable to recover. After
something like maybe 20 lockups...

Maybe that X could manage better but the current rate of lockups is one every
10 seconds, and that's with each lockup taking 10 seconds before a reset.

Maybe that this should go in another bug report however.


At Jérôme's request, I've exported my dmesg in order to check that X was stuck
inside the kernel. It contains my dmesg output with several executions of "echo
t > /proc/sysrq-trigger".

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

I've tried on 3.2.13; 3.3.0, 3.4-rc1(+) and I've had issues with all of these.
I'm running the latest individual tarballs of X (as of 5 days ago), along with
the latest libdrm, and a mesa git.

PS: I've started my laptop a bit after starting to write this. I've just
reached the 53 lockups, after  abit more than 10 minutes after issuing "startx"
(and X is still recovering, oh, it seeems it has stopped recovering after 56
lockups)

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2012-04-04 12:43 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
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 [this message]
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=201204041243.q34ChrAG004297@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).