On Fri, 30 May 2003, Linus Torvalds wrote:
>
> Modulo that, X is happy, with no error messages apart from a mention of
> the irq issue in the logs up until the lockup:
>
> (II) RADEON(0): [drm] failure adding irq handler, there is a device already
> using that irq
> [drm] falling back to irq-free operation
> (II) RADEON(0): [drm] Initialized kernel agp heap manager, 5111808
> (II) RADEON(0): Direct rendering enabled
Forcing fifo debugging makes the thing print out an endless loop of
[drm:radeon_do_wait_for_idle] *ERROR* failed!
radeon_status:
RBBM_STATUS = 0x80010140
CP_RB_RTPR = 0x00009b6f
CP_RB_WTPR = 0x00009b6f
AIC_CNTL = 0x00000000
AIC_STAT = 0x00000004
AIC_PT_BASE = 0x00000000
TLB_ADDR = 0x00000000
TLB_DATA = 0x00000000
which doesn't tell me anything, but maybe somebody with docs can tell why
it claims to be busy. The ring buffer read and write pointers change every
printout (increment by 6), but the read pointer is always the same as
the write pointer.
Reading the header files, RBBM_STATUS seems to say that there are 64
entries in the FIFO, and that the FIFO is busy. Which doesn't make much
sense to me. Anything useful I can do to debug this?
Linus
-------------------------------------------------------
This SF.net email is sponsored by: eBay
Get office equipment for less on eBay!
http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
