All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 25717] Radeon: system locks up when sending many vertices.
Date: Mon, 15 Mar 2010 07:57:53 -0700 (PDT)	[thread overview]
Message-ID: <20100315145753.7C156130086@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-25717-502@http.bugs.freedesktop.org/>

http://bugs.freedesktop.org/show_bug.cgi?id=25717





--- Comment #2 from Andy Furniss <lists@andyfurniss.entadsl.com>  2010-03-15 07:57:52 PST ---
(In reply to comment #1)

Running todays drt things have changed a bit -

With AGP gart I can now run gltestperf OK, though I suspect this could be by
luck as the "glxgears type perf" is a bit lower than recent kernels @ 800fps so
maybe the (poor) caching is slowing things down a bit and avoiding it.

With PCIE gart, where glxgears is 1200, I still hit the lockup, but now I am
saved by the new GPU reset code. 

Mar 15 14:29:37 nf7 kernel: radeon 0000:02:00.0: GPU lockup CP stall for more
than 1000msec
Mar 15 14:29:37 nf7 kernel: ------------[ cut here ]------------
Mar 15 14:29:37 nf7 kernel: WARNING: at
drivers/gpu/drm/radeon/radeon_fence.c:234 radeon_fence_wait+0x262/0x2c0
[radeon]()
Mar 15 14:29:37 nf7 kernel: Hardware name:  
Mar 15 14:29:37 nf7 kernel: GPU lockup (waiting for 0x000017D3 last fence id
0x000017CB)
Mar 15 14:29:37 nf7 kernel: Modules linked in: radeon ttm drm_kms_helper drm
i2c_algo_bit cfbcopyarea cfbimgblt cfbfillrect fbcon font bitblit softcursor fb
mt352 saa7134_dvb videobuf_dvb dvb_core mt20xx tea5767 tda9887 tda8290 tuner
saa7134 v4l2_common videodev v4l1_compat videobuf_dma_sg videobuf_core tveeprom
i2c_core nvidia_agp ehci_hcd agpgart ohci_hcd usbhid usbcore snd_intel8x0
snd_ac97_codec ac97_bus forcedeth
Mar 15 14:29:37 nf7 kernel: Pid: 2526, comm: gltestperf Tainted: G        W 
2.6.33-50657-g5894684 #1
Mar 15 14:29:37 nf7 kernel: Call Trace:
Mar 15 14:29:37 nf7 kernel:  [<fa1164a2>] ? radeon_fence_wait+0x262/0x2c0
[radeon]
Mar 15 14:29:37 nf7 kernel:  [<fa1164a2>] ? radeon_fence_wait+0x262/0x2c0
[radeon]
Mar 15 14:29:37 nf7 kernel:  [<c102f811>] warn_slowpath_common+0x81/0xa0
Mar 15 14:29:37 nf7 kernel:  [<fa1164a2>] ? radeon_fence_wait+0x262/0x2c0
[radeon]
Mar 15 14:29:37 nf7 kernel:  [<c102f87b>] warn_slowpath_fmt+0x2b/0x30
Mar 15 14:29:37 nf7 kernel:  [<fa1164a2>] radeon_fence_wait+0x262/0x2c0
[radeon]
Mar 15 14:29:37 nf7 kernel:  [<c104b950>] ? autoremove_wake_function+0x0/0x40
Mar 15 14:29:37 nf7 kernel:  [<fa117230>] ? radeon_sync_obj_wait+0x0/0x20
[radeon]
Mar 15 14:29:37 nf7 kernel:  [<fa117241>] radeon_sync_obj_wait+0x11/0x20
[radeon]
Mar 15 14:29:37 nf7 kernel:  [<f96b6e82>] ttm_bo_wait+0xf2/0x1d0 [ttm]
Mar 15 14:29:37 nf7 kernel:  [<fa12bb34>] radeon_gem_wait_idle_ioctl+0x84/0x120
[radeon]
Mar 15 14:29:37 nf7 kernel:  [<f954f719>] drm_ioctl+0x259/0x3e0 [drm]
Mar 15 14:29:37 nf7 kernel:  [<fa12bab0>] ?
radeon_gem_wait_idle_ioctl+0x0/0x120 [radeon]
Mar 15 14:29:37 nf7 kernel:  [<c10c05e9>] ? do_sync_read+0xb9/0xf0
Mar 15 14:29:37 nf7 kernel:  [<c10edd6e>] ? __fsnotify_parent+0xe/0x110
Mar 15 14:29:37 nf7 kernel:  [<f954f4c0>] ? drm_ioctl+0x0/0x3e0 [drm]
Mar 15 14:29:37 nf7 kernel:  [<c10ce35d>] vfs_ioctl+0x2d/0xa0
Mar 15 14:29:37 nf7 kernel:  [<c10ce51a>] do_vfs_ioctl+0x6a/0x560
Mar 15 14:29:37 nf7 kernel:  [<c10edb0e>] ? fsnotify+0xe/0x120
Mar 15 14:29:37 nf7 kernel:  [<c10edd6e>] ? __fsnotify_parent+0xe/0x110
Mar 15 14:29:37 nf7 kernel:  [<c10c0634>] ? rw_verify_area+0x14/0xc0
Mar 15 14:29:37 nf7 kernel:  [<c10c0e46>] ? vfs_read+0x146/0x150
Mar 15 14:29:37 nf7 kernel:  [<c10c1b44>] ? fget_light+0x14/0xe0
Mar 15 14:29:37 nf7 kernel:  [<c10c1b44>] ? fget_light+0x14/0xe0
Mar 15 14:29:37 nf7 kernel:  [<c10cea4e>] sys_ioctl+0x3e/0x60
Mar 15 14:29:37 nf7 kernel:  [<c1002c0c>] sysenter_do_call+0x12/0x22
Mar 15 14:29:37 nf7 kernel: ---[ end trace eae1ac44941f0643 ]---
Mar 15 14:29:37 nf7 kernel: [drm] Disabling audio support
Mar 15 14:29:37 nf7 kernel: radeon 0000:02:00.0: f72844e0 unpin not necessary
Mar 15 14:29:37 nf7 kernel: radeon 0000:02:00.0: GPU softreset 
Mar 15 14:29:37 nf7 kernel: radeon 0000:02:00.0:  
R_008010_GRBM_STATUS=0xE7731CE0
Mar 15 14:29:37 nf7 kernel: radeon 0000:02:00.0:  
R_008014_GRBM_STATUS2=0x00880103
Mar 15 14:29:37 nf7 kernel: radeon 0000:02:00.0:  
R_000E50_SRBM_STATUS=0x200018C0
Mar 15 14:29:37 nf7 kernel: radeon 0000:02:00.0:  
R_008020_GRBM_SOFT_RESET=0x00007FEE
Mar 15 14:29:37 nf7 kernel: radeon 0000:02:00.0:
R_008020_GRBM_SOFT_RESET=0x00000001
Mar 15 14:29:37 nf7 kernel: radeon 0000:02:00.0:  
R_008010_GRBM_STATUS=0xA0003030
Mar 15 14:29:37 nf7 kernel: radeon 0000:02:00.0:  
R_008014_GRBM_STATUS2=0x00000003
Mar 15 14:29:37 nf7 kernel: radeon 0000:02:00.0:  
R_000E50_SRBM_STATUS=0x200080C0
Mar 15 14:29:37 nf7 kernel: radeon 0000:02:00.0: GPU reset succeed


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
--

  parent reply	other threads:[~2010-03-15 14:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-25717-502@http.bugs.freedesktop.org/>
2010-03-08 15:28 ` [Bug 25717] Radeon: system locks up when sending many vertices bugzilla-daemon
2010-03-08 21:27 ` bugzilla-daemon
2010-03-15 14:57 ` bugzilla-daemon [this message]
2010-08-01 11:10 ` bugzilla-daemon
2010-09-23 10:19 ` bugzilla-daemon
2011-02-09 15:48 ` bugzilla-daemon
2011-02-09 16:37 ` bugzilla-daemon
2011-02-09 17:25 ` bugzilla-daemon
2011-02-09 18:44 ` bugzilla-daemon
2014-01-23 11:31 ` 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=20100315145753.7C156130086@annarchy.freedesktop.org \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.sourceforge.net \
    /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.