| Summary: | Recent DRM r200 driver stop working with 'failure adding irq handler' | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | DRI | Reporter: | Marcin Kurek <morgoth6> | ||||||||||||
| Component: | DRM/other | Assignee: | Default DRI bug account <dri-devel> | ||||||||||||
| Status: | RESOLVED FIXED | QA Contact: | |||||||||||||
| Severity: | normal | ||||||||||||||
| Priority: | high | ||||||||||||||
| Version: | XOrg git | ||||||||||||||
| Hardware: | Other | ||||||||||||||
| OS: | Linux (All) | ||||||||||||||
| Whiteboard: | |||||||||||||||
| i915 platform: | i915 features: | ||||||||||||||
| Attachments: |
|
||||||||||||||
|
Description
Marcin Kurek
2006-09-12 19:24:09 UTC
Created attachment 6935 [details]
Xorg log
Created attachment 6936 [details]
xorg conf
Created attachment 6937 [details]
drm log
Part of debug with 'modprobe drm debug=1'
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? Created attachment 6958 [details]
glxgears libgl debug
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. Most likely the same problem as in bug 7770, though it looks like this commit might actually fix that one... Workaround from 7770 (https://bugs.freedesktop.org/attachment.cgi?id=6560) seems to fix both problems here. 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. Created attachment 7018 [details]
Kernel opps after glxgears try
wow our domain support sucks ass.... I think I've fixed this in git.. please close bug if I have. 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.