From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 66880] New: R600_DEBUG=sb hangs system after playing xonotic, spring
Date: Sat, 13 Jul 2013 19:31:48 +0000 [thread overview]
Message-ID: <bug-66880-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 3203 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=66880
Priority: medium
Bug ID: 66880
Assignee: dri-devel@lists.freedesktop.org
Summary: R600_DEBUG=sb hangs system after playing xonotic,
spring
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: pheldens@ziggo.nl
Hardware: x86-64 (AMD64)
Status: NEW
Version: git
Component: Drivers/Gallium/r600
Product: Mesa
linux 3.10.* and before
R600_DEBUG=sb
radeon 4670
crashes in xonotic and spring after indeterminate time, colours the screen with
garbage, does not crash when R600_DEBUG is unset.
all I caught so far is a kernel oops output
Oops: 0000 [#1] PREEMPT SMP
Modules linked in: snd_hda_codec_hdmi snd_cmipci snd_opl3_lib snd_mpu401_uart
snd_usb_audio snd_usbmidi_lib snd_rawmidi snd_hda_intel snd_hda_codec snd_hwdep
CPU: 0 PID: 1539 Comm: X Not tainted 3.10.0-rc6 #2
Hardware name: MICRO-STAR INTERNATIONAL CO.,LTD MS-7596/785GM-E51 (MS-7596),
BIOS V2.11 12/08/2010
task: ffff88022e9f9320 ti: ffff880226ca4000 task.ti: ffff880226ca4000
RIP: 0010:[<ffffffff813e74ca>] [<ffffffff813e74ca>]
radeon_fence_process+0x8a/0x150
RSP: 0018:ffff880226ca5c28 EFLAGS: 00010246
RAX: ffffc9001079c598 RBX: 0000000000000002 RCX: ffff880226972da0
RDX: 0000000000000041 RSI: 0000000000000000 RDI: ffff880226972000
RBP: 000000000000000c R08: ffff880226972208 R09: 0000000000000000
R10: 0000000000000005 R11: 0000000000000304 R12: ffff880226972df0
R13: 0000000000000002 R14: ffff880226972000 R15: ffffffff00000000
FS: 00007fe0a9315880(0000) GS:ffff88022fc00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: ffffc9001079c598 CR3: 00000002241b6000 CR4: 00000000000007f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Stack:
ffff88022695ce00 ffffffff8144f257 0000000000000292 ffffffff81948957
ffff88022eb8b560 ffff880226972000 0000000000000005 ffff880226972000
ffff880226972e20 ffff8802269725f8 0000000000000000 ffffffff813e7fdb
Call Trace:
[<ffffffff8144f257>] ? __dev_printk+0x37/0xa0
[<ffffffff813e7fdb>] ? radeon_fence_count_emitted+0x1b/0x70
[<ffffffff813fd8cd>] ? radeon_ring_backup+0x3d/0x120
[<ffffffff813d3601>] ? radeon_gpu_reset+0x81/0x210
[<ffffffff813fc930>] ? radeon_gem_wait_idle_ioctl+0xd0/0xf0
[<ffffffff813b0250>] ? drm_ioctl+0x460/0x560
[<ffffffff813fc860>] ? radeon_gem_busy_ioctl+0x120/0x120
[<ffffffff8108e8a4>] ? signal_delivered+0x54/0x70
[<ffffffff8112657a>] ? do_vfs_ioctl+0x8a/0x500
[<ffffffff810a98ce>] ? vtime_account_user+0x6e/0x90
[<ffffffff81126a3d>] ? SyS_ioctl+0x4d/0xa0
[<ffffffff8176bf49>] ? tracesys+0xd0/0xd5
Code: 48 39 d0 73 53 48 89 c3 41 b9 01 00 00 00 41 80 be 58 16 00 00 00 4d 8b
a8 e0 0b 00 00 48 8d 41 08 0f 84 86 00 00 00 48 8b 40 10 <8b> 00 48 89 da 89 c0
4c 21 fa 48 09 d0 48 39 c3 76 0c 4c 89 ea
RIP [<ffffffff813e74ca>] radeon_fence_process+0x8a/0x150
RSP <ffff880226ca5c28>
CR2: ffffc9001079c598
---[ end trace 2b43f4717e08f222 ]---
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 4597 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2013-07-13 19:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-13 19:31 bugzilla-daemon [this message]
2014-05-17 23:31 ` [Bug 66880] R600_DEBUG=sb hangs system after playing xonotic, spring bugzilla-daemon
2019-09-18 19:04 ` 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-66880-502@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 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.