View Full Version : "[drm] failure adding irq handler"

Steve Snyder
26th May 2003, 17:42
Last weekend I installed RHL v9 on the same hardware I previously ran RHL v7.3 on, including my G400MAX. Now I'm getting behavior that I haven't seen before.

Is it a problem that an IRQ can't be found for use with DRM (see below)? It's not shown in the log file as either an error or a warning, but it seems that the use of an IRQ is desireable.

It doesn't say what IRQ it wants. Typically, video wants IRQ 11, but that is not currently in use by any other device.

Any thoughts on this? Thanks.


(II) MGA(0): [drm] bpp: 32 depth: 24
(II) MGA(0): [drm] Sarea 2200+664: 2864
drmOpenDevice: minor is 0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 6, (OK)
drmOpenDevice: minor is 0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 6, (OK)
drmOpenDevice: minor is 0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 6, (OK)
drmGetBusid returned ''
(II) MGA(0): [drm] created "mga" driver at busid "PCI:1:0:0"
(II) MGA(0): [drm] added 8192 byte SAREA at 0xf894e000
(II) MGA(0): [drm] mapped SAREA 0xf894e000 to 0x40015000
(II) MGA(0): [drm] framebuffer handle = 0xec000000
(II) MGA(0): [drm] added 1 reserved context for kernel
(II) MGA(0): [agp] Mode 0x1f000217 [AGP 0x8086/0x2531; Card 0x102b/0x0525]
(II) MGA(0): [agp] 12288 kB allocated with handle 0xf8951000
(II) MGA(0): [agp] WARP microcode handle = 0xe8000000
(II) MGA(0): [agp] WARP microcode mapped at 0x42891000
(II) MGA(0): [agp] Primary DMA handle = 0xe8008000
(II) MGA(0): [agp] Primary DMA mapped at 0x42899000
(II) MGA(0): [agp] DMA buffers handle = 0xe8108000
(II) MGA(0): [agp] DMA buffers mapped at 0x42999000
(II) MGA(0): [drm] Added 128 65536 byte DMA buffers
(II) MGA(0): [agp] agpTexture handle = 0xe8908000
(II) MGA(0): [agp] agpTexture size: 2816 kb
(II) MGA(0): [drm] Registers handle = 0xee000000
(II) MGA(0): [drm] Status handle = 0xf895a000
(II) MGA(0): [agp] Status page mapped at 0x40017000
(II) MGA(0): [dri] visual configs initialized
(II) MGA(0): Memory manager initialized to (0,0) (1280,2047)
(II) MGA(0): Largest offscreen area available: 1280 x 1023
(II) MGA(0): Reserved back buffer at offset 0xa00000
(II) MGA(0): Reserved depth buffer at offset 0xf00000
(II) MGA(0): Reserved 12288 kb for textures at offset 0x1400000
(II) MGA(0): Using XFree86 Acceleration Architecture (XAA)
Screen to screen bit blits
Solid filled rectangles
Solid filled trapezoids
8x8 mono pattern filled rectangles
8x8 mono pattern filled trapezoids
Indirect CPU to Screen color expansion
Screen to Screen color expansion
Solid Lines
Dashed Lines
Scanline Image Writes
Offscreen Pixmaps
Driver provided FillMono8x8PatternRects replacement
Setting up tile and stipple cache:
32 128x128 slots
9 256x256 slots
(==) MGA(0): Backing store disabled
(==) MGA(0): Silken mouse enabled
(**) Option "dpms"
(**) MGA(0): DPMS enabled
(II) MGA(0): Using overlay video
(II) MGA(0): X context handle = 0x00000001
(II) MGA(0): [drm] installed DRM signal handler
(II) MGA(0): [DRI] installation complete
(II) MGA(0): [drm] Mapped 128 DMA buffers
(II) MGA(0): [drm] failure adding irq handler, there is a device already using t
hat irq
[drm] falling back to irq-free operation
(==) MGA(0): Direct rendering enabled

27th May 2003, 04:16
I have the same "symptoms" and it all works fine for me.

Check if your BIOS has the option to reserve an IRQ for the video card (although I've got that set and I still get this behaviour).

Unless you're actually having problems, I wouldn't worry about it.