Have others seen this? Current DRI CVS tree, current 2.5.x kernel (which 
is pretty current kernel-module-wise, the only difference to the current 
DRI tree _seems_ to be the documentation updates).

Same thing happens with an older DRI CVS tree too (with new kernel
modules), for that matter.

It's not really an endless loop, since radeon_do_wait_for_idle() will 
return eventually, but the callers will just call it again on failure.

It works on another Radeon box I have access to, and one difference is 
that the failing box does not have access to interrupts for the video 
card:

        ...
        Linux agpgart interface v0.100 (c) Dave Jones
        agpgart: Detected an Intel 440GX Chipset.
        agpgart: Maximum main memory to use for agp memory: 816M
        agpgart: AGP aperture is 256M @ 0xe0000000
        [drm] Initialized radeon 1.8.0 20020828 on minor 0
        ...
        agpgart: Found an AGP 1.0 compliant device at 00:00.0.
        agpgart: Putting AGP V2 device at 00:00.0 into 1x mode
        agpgart: Putting AGP V2 device at 01:00.0 into 1x mode
        PCI: No IRQ known for interrupt pin A of device 01:00.0. Probably buggy MP 
table.

This same machine _used_ to work fine last time I tested it, but that's a 
month or two ago. 

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] created "radeon" driver at busid "PCI:1:0:0"
        (II) RADEON(0): [drm] added 8192 byte SAREA at 0xf892c000
        (II) RADEON(0): [drm] mapped SAREA 0xf892c000 to 0x40017000
        (II) RADEON(0): [drm] framebuffer handle = 0xd0000000
        (II) RADEON(0): [drm] added 1 reserved context for kernel
        (II) RADEON(0): [agp] Mode 0x1f000201 [AGP 0x8086/0x71a0; Card 0x1002/0x5144]
        (II) RADEON(0): [agp] 8192 kB allocated with handle 0x00000000
        (II) RADEON(0): [agp] ring handle = 0xe0000000
        (II) RADEON(0): [agp] Ring mapped at 0x4012a000
        (II) RADEON(0): [agp] ring read ptr handle = 0xe0101000
        (II) RADEON(0): [agp] Ring read ptr mapped at 0x40019000
        (II) RADEON(0): [agp] vertex/indirect buffers handle = 0xe0102000
        (II) RADEON(0): [agp] Vertex/indirect buffers mapped at 0x4022b000
        (II) RADEON(0): [agp] AGP texture map handle = 0xe0302000
        (II) RADEON(0): [agp] AGP Texture map mapped at 0x4042b000
        (II) RADEON(0): [drm] register handle = 0xff580000
        (II) RADEON(0): [dri] Visual configs initialized
        (II) RADEON(0): CP in BM mode
        ...
        (II) RADEON(0): [drm] installed DRM signal handler
        (II) RADEON(0): [DRI] installation complete
        (II) RADEON(0): [drm] Added 32 65536 byte vertex/indirect buffers
        (II) RADEON(0): [drm] Mapped 32 vertex/indirect buffers
        (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

Does that "irq-free operation" fallback work for other people? It's the 
only half-way suspicious thing I see.

                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

Reply via email to