Bug 8246 - Recent DRM r200 driver stop working with 'failure adding irq handler'
Summary: Recent DRM r200 driver stop working with 'failure adding irq handler'
Status: RESOLVED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/other (show other bugs)
Version: XOrg git
Hardware: Other Linux (All)
: high normal
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-09-12 19:24 UTC by Marcin Kurek
Modified: 2006-09-25 13:03 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
Xorg log (60.36 KB, text/plain)
2006-09-12 19:24 UTC, Marcin Kurek
no flags Details
xorg conf (2.98 KB, text/plain)
2006-09-12 19:25 UTC, Marcin Kurek
no flags Details
drm log (122.47 KB, text/plain)
2006-09-12 19:40 UTC, Marcin Kurek
no flags Details
glxgears libgl debug (1.67 KB, text/plain)
2006-09-13 17:38 UTC, Marcin Kurek
no flags Details
Kernel opps after glxgears try (2.89 KB, text/plain)
2006-09-17 08:00 UTC, Marcin Kurek
no flags Details

Description Marcin Kurek 2006-09-12 19:24:09 UTC
After git update of r200 driver direct rendering stop to work on my system
(Pegasos 2 G4 1GHz 1GB Radeon 9000) Previously I used a bit older snapshot
without any problems, but recent version doesn't work.

glxinfo reports 'direct rendering: No' and looking in the logs showed me
something like that:

(II) RADEON(0): [drm] failure adding irq handler, there is a device already
using that irq
[drm] falling back to irq-free operation

I guess this is reason of my problem.
Comment 1 Marcin Kurek 2006-09-12 19:24:46 UTC
Created attachment 6935 [details]
Xorg log
Comment 2 Marcin Kurek 2006-09-12 19:25:08 UTC
Created attachment 6936 [details]
xorg conf
Comment 3 Marcin Kurek 2006-09-12 19:40:07 UTC
Created attachment 6937 [details]
drm log

Part of debug with 'modprobe drm debug=1'
Comment 4 Michel Dänzer 2006-09-13 05:04:46 UTC
It doesn't look like this should cause direct rendering to be disabled; the
output of something like

LIBGL_DEBUG=verbose glxgears

might help.

As for why the IRQ can no longer be used, can you do a git bisect?
Comment 5 Marcin Kurek 2006-09-13 17:38:03 UTC
Created attachment 6958 [details]
glxgears libgl debug
Comment 6 Marcin Kurek 2006-09-13 17:46:01 UTC
I must admit I first time use git bisect and I am impressed. Anyway a few
reboots show me this commit:

commit 205c573e449b38d759273f6a51eb8c1131585ece
Author: Dave Airlie <airlied@linux.ie>
Date:   Sat Aug 19 16:55:00 2006 +1000

    remove local copies of pci domain/bus/slot/num

Versions before that works fine. Direct rendering is enabled and there is
nothing about used irq in the logs.
Comment 7 Michel Dänzer 2006-09-14 01:47:29 UTC
Most likely the same problem as in bug 7770, though it looks like this commit
might actually fix that one...
Comment 8 Marcin Kurek 2006-09-14 08:27:20 UTC
Workaround from 7770 (https://bugs.freedesktop.org/attachment.cgi?id=6560) seems
to fix both problems here.
Comment 9 Marcin Kurek 2006-09-17 07:59:36 UTC
OK, I wrote that too soon again. It seems it fixed problem partialy only. With
recent git snap of DRM and workaround from 7770 the open DRM failed (Operation
not permitted) error is gone indeed, but the irq failure is still here.

When I try to run for example glxgears it nukes my server, but glxinfo works
fine and shows Direct Rendering: Yes.

Looking at the log's showed me kernel oops (Attached)

Anyway reverting 205c573e449b38d759273f6a51eb8c1131585ece fixes both of my
problems for sure. This time I double check it with glxinfo, glxgears and some
GL games.
Comment 10 Marcin Kurek 2006-09-17 08:00:07 UTC
Created attachment 7018 [details]
Kernel opps after glxgears try
Comment 11 Dave Airlie 2006-09-18 14:24:38 UTC
wow our domain support sucks ass.... I think I've fixed this in git.. please
close bug if I have.
Comment 12 Marcin Kurek 2006-09-25 13:03:50 UTC
Recent git snap fix this issue


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.