From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 63101] New: Hard lockup whel launching games like TF2 on kernels 3.11.5 and 3.12 rc4 and above
Date: Tue, 15 Oct 2013 20:04:09 +0000 [thread overview]
Message-ID: <bug-63101-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=63101
Bug ID: 63101
Summary: Hard lockup whel launching games like TF2 on kernels
3.11.5 and 3.12 rc4 and above
Product: Drivers
Version: 2.5
Kernel Version: 3.11.5
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: laszlo.kertesz@gmail.com
Regression: No
Created attachment 111161
--> https://bugzilla.kernel.org/attachment.cgi?id=111161&action=edit
dmesg of the locked up session
I begin to experience system lockups when launching Team Fortress 2 on an
A8-5500 (using its integrated 7560 Radeon video with the radeon driver) - it
began starting around kernel 3.12 rc4, (i build the kernel from mainline git).
I have a leftover package of 3.12 rc3+ and that works fine.
This also happens with the stable 3.11.5 kernel version.
Kernel 3.11.0 doesnt have this issue.
As i launch the game, the menus are shown fine, but as soon as i enter the
actual game, either it crashes outright and throws me back to the desktop or i
have the last screen frozen.
In any way, i can move the mouse but cannot interact with windows, the keyboard
listens only to the magic keys. From time to timethe system beeps.
Dmesg is filled with warning and BUG/Oops entries.
Begins with:
Oct 15 21:21:17 laca-desktop kernel: [ 355.859798] radeon 0000:00:01.0: GPU
lockup CP stall for more than 10000msec
Oct 15 21:21:17 laca-desktop kernel: [ 355.859807] radeon 0000:00:01.0: GPU
lockup (waiting for 0x0000000000001276 last fence id 0x0000000000001275)
Oct 15 21:21:17 laca-desktop kernel: [ 355.866308] [TTM] Buffer eviction
failed
Then follow warnings like:
WARNING: CPU: 3 PID: 4041 at drivers/gpu/drm/drm_mm.c:257
drm_mm_remove_node+0x104/0x110 [drm]()
After that the BUGs:
Oct 15 21:21:20 laca-desktop kernel: [ 358.208965] BUG: unable to handle
kernel NULL pointer dereference at 0000000000000088
The system is unusable (i can move the mouse pointer in best case), i have to
reboot with the sysrq combinations.
All of the problematic kernels share the new cpufreq code i suppose, they all
work the same way - instead of powering the CPU between 0.9-1.34v as the
kernels before, now i have 0.65-1.22 volts, the CPU barely reaching its nominal
3.2 GHz speed, and never above (before it was up to ~3.5GHz and boosting was
working, now core boosting never works).
--
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2013-10-15 20:04 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-15 20:04 bugzilla-daemon [this message]
2013-10-15 22:57 ` [Bug 63101] Hard lockup whel launching games like TF2 on kernels 3.11.5 and 3.12 rc4 and above bugzilla-daemon
2013-10-16 6:32 ` bugzilla-daemon
2013-10-16 6:39 ` bugzilla-daemon
2013-10-16 6:41 ` bugzilla-daemon
2013-10-16 6:41 ` bugzilla-daemon
2013-10-18 3:21 ` bugzilla-daemon
2013-10-18 5:54 ` bugzilla-daemon
2013-10-18 10:10 ` bugzilla-daemon
2013-10-19 6:55 ` bugzilla-daemon
2013-10-19 13:09 ` bugzilla-daemon
2013-10-19 13:13 ` bugzilla-daemon
2013-10-19 13:14 ` [Bug 63101] Hard lockup whel launching games like TF2 on kernels 3.11.5 and 3.12 rc4 and above if radeon.dpm=1 is used bugzilla-daemon
2013-10-19 13:25 ` bugzilla-daemon
2013-10-20 8:03 ` bugzilla-daemon
2013-10-22 13:25 ` bugzilla-daemon
2013-11-08 14:33 ` bugzilla-daemon
2013-11-09 12:07 ` bugzilla-daemon
2013-11-09 20:57 ` bugzilla-daemon
2013-11-11 18:38 ` bugzilla-daemon
2013-11-12 19:00 ` bugzilla-daemon
2013-11-13 7:23 ` bugzilla-daemon
2013-11-14 15:24 ` bugzilla-daemon
2013-11-14 16:26 ` bugzilla-daemon
2013-11-14 16:45 ` 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-63101-2300@https.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.