Attachment 49419 Details for Bug 39469 – Kernel output after lockup detection

Kernel output after lockup detection

HD5770_GPU_CRASH (text/plain), 3.51 KB, created by jdk on 2011-07-22 04:29:54 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: jdk

Created: 2011-07-22 04:29:54 UTC

Size: 3.51 KB

patch

obsolete

>[ 1192.587886] chrome[2626]: segfault at 0 ip 00007f52daf3a7b0 sp 00007f52c752c660 error 6 in chrome[7f52da340000+36e5000]
>[ 1193.422531] chrome[2613]: segfault at 0 ip 00007ffa8fb2e908 sp 00007ffffbc9cbb0 error 4 in chrome[7ffa8d9ae000+36e5000]
>[ 1195.909271] radeon 0000:01:00.0: GPU lockup CP stall for more than 10020msec
>[ 1195.909274] ------------[ cut here ]------------
>[ 1195.909292] WARNING: at drivers/gpu/drm/radeon/radeon_fence.c:269 radeon_fence_wait+0x2a8/0x325 [radeon]()
>[ 1195.909294] Hardware name: MS-7673
>[ 1195.909295] GPU lockup (waiting for 0x0006FDB7 last fence id 0x0006FDB2)
>[ 1195.909296] Modules linked in: fuse coretemp sunrpc sco bnep l2cap bluetooth rfkill ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep snd_seq snd_seq_device snd_pcm microcode r8169 xhci_hcd snd_timer shpchp snd serio_raw iTCO_wdt i2c_i801 iTCO_vendor_support mii soundcore snd_page_alloc wmi ipv6 radeon ttm drm_kms_helper drm i2c_algo_bit i2c_core [last unloaded: speedstep_lib]
>[ 1195.909314] Pid: 1352, comm: Xorg Not tainted 2.6.38.8-35.fc15.x86_64 #1
>[ 1195.909315] Call Trace:
>[ 1195.909321]  [<ffffffff8105511a>] warn_slowpath_common+0x83/0x9b
>[ 1195.909323]  [<ffffffff810551d5>] warn_slowpath_fmt+0x46/0x48
>[ 1195.909336]  [<ffffffffa00d86c5>] ? evergreen_gpu_is_lockup+0xba/0xc2 [radeon]
>[ 1195.909345]  [<ffffffffa009fdff>] radeon_fence_wait+0x2a8/0x325 [radeon]
>[ 1195.909348]  [<ffffffff8106f26e>] ? autoremove_wake_function+0x0/0x3d
>[ 1195.909356]  [<ffffffffa00a03b9>] radeon_sync_obj_wait+0x11/0x13 [radeon]
>[ 1195.909360]  [<ffffffffa00655da>] ttm_bo_wait+0xbf/0x17a [ttm]
>[ 1195.909364]  [<ffffffffa0066002>] ? ttm_bo_list_ref_sub+0x29/0x2b [ttm]
>[ 1195.909374]  [<ffffffffa00b006b>] radeon_bo_wait+0x7b/0x9f [radeon]
>[ 1195.909383]  [<ffffffffa00b05dd>] radeon_gem_wait_idle_ioctl+0x3d/0x74 [radeon]
>[ 1195.909390]  [<ffffffffa0019861>] drm_ioctl+0x29e/0x37b [drm]
>[ 1195.909399]  [<ffffffffa00b05a0>] ? radeon_gem_wait_idle_ioctl+0x0/0x74 [radeon]
>[ 1195.909402]  [<ffffffff81476e98>] ? _cond_resched+0xe/0x22
>[ 1195.909405]  [<ffffffff8104127e>] ? should_resched+0xe/0x2d
>[ 1195.909407]  [<ffffffff8104127e>] ? should_resched+0xe/0x2d
>[ 1195.909408]  [<ffffffff81476e98>] ? _cond_resched+0xe/0x22
>[ 1195.909411]  [<ffffffff81012411>] ? might_fault+0x21/0x23
>[ 1195.909414]  [<ffffffff8112f3ac>] do_vfs_ioctl+0x47e/0x4bf
>[ 1195.909416]  [<ffffffff8109fc99>] ? audit_syscall_exit+0x12d/0x148
>[ 1195.909418]  [<ffffffff8112f443>] sys_ioctl+0x56/0x7b
>[ 1195.909420]  [<ffffffff81009e75>] ? int_check_syscall_exit_work+0x34/0x3d
>[ 1195.909422]  [<ffffffff81009bc2>] system_call_fastpath+0x16/0x1b
>[ 1195.909424] ---[ end trace 9d7c5d6b702bed77 ]---
>[ 1195.910492] radeon 0000:01:00.0: GPU softreset 
>[ 1195.910495] radeon 0000:01:00.0:   GRBM_STATUS=0xA27338A0
>[ 1195.910496] radeon 0000:01:00.0:   GRBM_STATUS_SE0=0x1C000007
>[ 1195.910498] radeon 0000:01:00.0:   GRBM_STATUS_SE1=0x00000007
>[ 1195.910500] radeon 0000:01:00.0:   SRBM_STATUS=0x200000C0
>[ 1195.910510] radeon 0000:01:00.0:   GRBM_SOFT_RESET=0x00007F6B
>[ 1195.910613] radeon 0000:01:00.0:   GRBM_STATUS=0x00003828
>[ 1195.910615] radeon 0000:01:00.0:   GRBM_STATUS_SE0=0x00000007
>[ 1195.910616] radeon 0000:01:00.0:   GRBM_STATUS_SE1=0x00000007
>[ 1195.910618] radeon 0000:01:00.0:   SRBM_STATUS=0x200000C0
>[ 1195.911623] radeon 0000:01:00.0: GPU reset succeed
>[ 1195.949088] radeon 0000:01:00.0: WB enabled
>[ 1195.965343] [drm] ring test succeeded in 1 usecs
>[ 1195.965351] [drm] ib test succeeded in 1 usecs

Actions: View

Attachments on bug 39469: 49419 | 49420

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.