On Fri, 2004-08-20 at 19:23, Fernando Pablo Lopez-Lezcano wrote: > Here's a new one, this is 2.6.8.1 (NOT 2.4.8.1!, sigh) + voluntary P6, > voluntary+kernel preemption enabled, threaded = 0 for the soundcard. > ALSA > /usr/src/redhat/BUILD/alsa-driver-1.0.6a/alsa-kernel/core/pcm_lib.c:139: > XRUN: pcmC0D0p > [<f8ff9b8f>] snd_pcm_period_elapsed+0x36f/0x560 [snd_pcm] > [<c011eec7>] scheduler_tick+0x2b7/0x580 > [<f88e4fe4>] ehci_irq+0xe4/0x300 [ehci_hcd] > [<f90e1891>] snd_ice1712_interrupt+0x171/0x1e0 [snd_ice1712] > [<c012b2c0>] generic_handle_IRQ_event+0x30/0x60 > [<c0108506>] do_IRQ+0x146/0x3b0 > [<c0106a88>] common_interrupt+0x18/0x20 > [<c01157b8>] delay_pmtmr+0x18/0x20 > [<c0215579>] __delay+0x9/0x10 > [<f88f3aa3>] radeon_do_wait_for_fifo+0x43/0x60 [radeon] > [<f88f3ad2>] radeon_do_wait_for_idle+0x12/0x60 [radeon] > [<f88eefec>] radeon_ioctl+0xbc/0x150 [radeon] > [<f88f5290>] radeon_cp_idle+0x0/0xa0 [radeon] > [<c01968de>] sys_ioctl+0x21e/0x3d0 > [<c01068c9>] sysenter_past_esp+0x52/0x71 >
It looks like the timeout for many Radeon DRI operations is controlled by the dev_priv->usec_timeout value, which is copied from userspace via ioctl in radeon_cp_init. This value can be as large as 100 MSECS! radeon_drv.h:#define RADEON_MAX_USEC_TIMEOUT 100000 /* 100 ms */ The driver does not seem to have a default for this, so you need to find the userspace code that is initializing the DRI and find the value it is being set to. Why is this allowed to be so large? Lee ------------------------------------------------------- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 -- _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
