From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 60254] New: agd5f wip kernel Oops when provoking GPU lock.
Date: Sun, 03 Feb 2013 21:43:53 +0000 [thread overview]
Message-ID: <bug-60254-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 5264 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=60254
Priority: medium
Bug ID: 60254
Assignee: dri-devel@lists.freedesktop.org
Summary: agd5f wip kernel Oops when provoking GPU lock.
Severity: normal
Classification: Unclassified
OS: All
Reporter: lists@andyfurniss.entadsl.com
Hardware: Other
Status: NEW
Version: XOrg CVS
Component: DRM/Radeon
Product: DRI
The GPU lock with Rv670 and openarena is nothing new - it seems to have been a
feature for almost a year (I haven't used rv670 for most of that time).
On noticing the new gpu reset code in drm-next-3.9-wip I decided to provoke it
on my AGP box and got -
Feb 3 20:46:56 nf7 kernel: radeon 0000:02:00.0: GPU lockup CP stall for more
than 10000msec
Feb 3 20:46:56 nf7 kernel: radeon 0000:02:00.0: GPU lockup (waiting for
0x00000000000111c8 last fence id 0x00000000000111c6)
Feb 3 20:46:56 nf7 kernel: radeon 0000:02:00.0: f51df600 unpin not necessary
Feb 3 20:46:56 nf7 kernel: radeon 0000:02:00.0: Saved 217 dwords of commands
on ring 0.
Feb 3 20:46:56 nf7 kernel: BUG: unable to handle kernel paging request at
f87aec0c
Feb 3 20:46:56 nf7 kernel: IP: [<fa033a3e>] radeon_fence_process+0x7e/0x160
[radeon]
Feb 3 20:46:56 nf7 kernel: *pde = 3702f067 *pte = 00000000
Feb 3 20:46:56 nf7 kernel: Oops: 0000 [#1] PREEMPT
Feb 3 20:46:56 nf7 kernel: Modules linked in: radeon fbcon font bitblit ttm
softcursor drm_kms_helper drm fb fbdev i2c_algo_bit i2c_core cfbcopyarea
cfbimgblt cfbfillrect ehci_pci ehci_hcd nvidia_agp agpgart ohci_hcd usbhid
usbcore usb_common snd_intel8x0 snd_ac97_codec ac97_bus forcedeth
Feb 3 20:46:56 nf7 kernel: Pid: 2511, comm: openarena.i386 Not tainted
3.8.0-rc3-gc7fb5ff #1 /NF7-S/NF7 (nVidia-nForce2)
Feb 3 20:46:56 nf7 kernel: EIP: 0060:[<fa033a3e>] EFLAGS: 00210246 CPU: 0
Feb 3 20:46:56 nf7 kernel: EIP is at radeon_fence_process+0x7e/0x160 [radeon]
Feb 3 20:46:56 nf7 kernel: EAX: f87aec0c EBX: f73b2848 ECX: f73b2848 EDX:
00000000
Feb 3 20:46:56 nf7 kernel: ESI: 00000000 EDI: f73b2000 EBP: e4765d8c ESP:
e4765d58
Feb 3 20:46:56 nf7 kernel: DS: 007b ES: 007b FS: 0000 GS: 0033 SS: 0068
Feb 3 20:46:56 nf7 kernel: CR0: 8005003b CR2: f87aec0c CR3: 1e75f000 CR4:
000007d0
Feb 3 20:46:56 nf7 kernel: DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3:
00000000
Feb 3 20:46:56 nf7 kernel: DR6: ffff0ff0 DR7: 00000400
Feb 3 20:46:56 nf7 kernel: Process openarena.i386 (pid: 2511, ti=e4764000
task=f70ad2b0 task.ti=e4764000)
Feb 3 20:46:56 nf7 kernel: Stack:
Feb 3 20:46:56 nf7 kernel: c13d4e58 00765d7c 00000018 f73b2848 f73b2888
00000872 00000003 00000872
Feb 3 20:46:56 nf7 kernel: 00000000 0000000c 00000003 f73b2a5c e4765e0c
e4765da4 fa034850 f73b2000
Feb 3 20:46:56 nf7 kernel: f73b2000 f73b2a5c e4765e0c e4765dc4 fa049bb8
f73b28e8 00000000 c12b06cd
Feb 3 20:46:56 nf7 kernel: Call Trace:
Feb 3 20:46:56 nf7 kernel: [<c13d4e58>] ? sub_preempt_count+0x8/0x80
Feb 3 20:46:56 nf7 kernel: [<fa034850>] radeon_fence_count_emitted+0x20/0x90
[radeon]
Feb 3 20:46:56 nf7 kernel: [<fa049bb8>] radeon_ring_backup+0x38/0x100
[radeon]
Feb 3 20:46:56 nf7 kernel: [<c12b06cd>] ? _dev_info+0x2d/0x30
Feb 3 20:46:56 nf7 kernel: [<fa020b22>] radeon_gpu_reset+0x62/0x1d0 [radeon]
Feb 3 20:46:56 nf7 kernel: [<f8be99c6>] ? ttm_bo_unreserve+0x26/0x50 [ttm]
Feb 3 20:46:56 nf7 kernel: [<fa04821d>]
radeon_gem_handle_lockup.part.2+0xd/0x20 [radeon]
Feb 3 20:46:56 nf7 kernel: [<fa048b13>] radeon_gem_wait_idle_ioctl+0xb3/0xd0
[radeon]
Feb 3 20:46:56 nf7 kernel: [<fa048a60>] ? radeon_gem_busy_ioctl+0xf0/0xf0
[radeon]
Feb 3 20:46:56 nf7 kernel: [<f8af9e82>] drm_ioctl+0x402/0x460 [drm]
Feb 3 20:46:56 nf7 kernel: [<fa048a60>] ? radeon_gem_busy_ioctl+0xf0/0xf0
[radeon]
Feb 3 20:46:56 nf7 kernel: [<c104f469>] ? ktime_add_safe+0x9/0x60
Feb 3 20:46:56 nf7 kernel: [<c104fe80>] ? hrtimer_forward+0xa0/0x190
Feb 3 20:46:56 nf7 kernel: [<f8af9a80>] ? drm_copy_field+0x80/0x80 [drm]
Feb 3 20:46:56 nf7 kernel: [<c10eb65a>] do_vfs_ioctl+0x7a/0x590
Feb 3 20:46:56 nf7 kernel: [<c101ef0b>] ? lapic_next_event+0x1b/0x20
Feb 3 20:46:56 nf7 kernel: [<c106978d>] ?
clockevents_program_event+0x9d/0x150
Feb 3 20:46:56 nf7 kernel: [<c106ab18>] ? tick_program_event+0x28/0x30
Feb 3 20:46:56 nf7 kernel: [<c1050612>] ? hrtimer_interrupt+0x182/0x2f0
Feb 3 20:46:56 nf7 kernel: [<c13d4e58>] ? sub_preempt_count+0x8/0x80
Feb 3 20:46:56 nf7 kernel: [<c1048cf9>] ? __rcu_read_unlock+0x9/0x60
Feb 3 20:46:56 nf7 kernel: [<c10f4bc7>] ? fget_light+0x77/0xd0
Feb 3 20:46:56 nf7 kernel: [<c10ebbac>] sys_ioctl+0x3c/0x70
Feb 3 20:46:56 nf7 kernel: [<c13d7ffa>] sysenter_do_call+0x12/0x22
Feb 3 20:46:56 nf7 kernel: Code: 8b 4d d4 8d 84 51 f0 00 00 00 8b 74 c7 08 89
75 e0 8b 74 c7 0c 8b 45 d8 83 c0 08 80 bf ec 0d 00 00 00 0f 84 bf 00 00 00 8b
40 0c <8b> 00 39 45 e8 8b 4d ec 89 c3 ba 01 00 00 00 0f 47 ce 39 f1 77
Feb 3 20:46:56 nf7 kernel: EIP: [<fa033a3e>] radeon_fence_process+0x7e/0x160
[radeon] SS:ESP 0068:e4765d58
Feb 3 20:46:56 nf7 kernel: CR2: 00000000f87aec0c
Feb 3 20:46:56 nf7 kernel: ---[ end trace 457588a7cbc40235 ]---
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 6734 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-02-03 21:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-03 21:43 bugzilla-daemon [this message]
2013-02-03 21:57 ` [Bug 60254] kernel Oops when provoking GPU lock bugzilla-daemon
2013-02-04 11:19 ` bugzilla-daemon
2013-04-24 18:40 ` [Bug 60254] [r600g] " bugzilla-daemon
2014-01-06 14:13 ` bugzilla-daemon
2015-07-30 11:55 ` 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-60254-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.