Bug 29327

Summary: radeon interrupts don't fire with MSI
Product: DRI Reporter: Tobias Droste <tdroste>
Component: DRM/RadeonAssignee: Default DRI bug account <dri-devel>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: medium CC: simon.j.munton
Version: DRI git   
Hardware: x86 (IA32)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
dmesg without MSI
none
lspci -vnn without MSI
none
lspci -vt without MSI
none
Xorg log without MSI
none
dmesg with MSI
none
lspci -vnn with MSI
none
lspci -vt with MSI
none
Xorg log with MSI none

Description Tobias Droste 2010-07-30 15:41:48 UTC
Created attachment 37470 [details]
dmesg without MSI

If I boot the current d-r-t kernel with MSI enabled the radeon module doesn't fire any interrupts. Without the interrupts and vblank_mode in driconf set to 3 the screen stops refreshing.

This is always reproducible. To make it work again I have to boot with pci=nomsi.

Software versions
kernel current d-r-t (2.6.35-rc2)
ddx, mesa, xserver git master

Hardware
Radeon X1950pro RV570 (AGP)
Comment 1 Tobias Droste 2010-07-30 15:42:22 UTC
Created attachment 37471 [details]
lspci -vnn without MSI
Comment 2 Tobias Droste 2010-07-30 15:43:09 UTC
Created attachment 37472 [details]
lspci -vt without MSI
Comment 3 Tobias Droste 2010-07-30 15:43:34 UTC
Created attachment 37473 [details]
Xorg log without MSI
Comment 4 Tobias Droste 2010-07-30 15:54:26 UTC
Created attachment 37474 [details]
dmesg with MSI
Comment 5 Tobias Droste 2010-07-30 15:55:00 UTC
Created attachment 37475 [details]
lspci -vnn with MSI
Comment 6 Tobias Droste 2010-07-30 15:57:58 UTC
Created attachment 37476 [details]
lspci -vt with MSI
Comment 7 Tobias Droste 2010-07-30 15:58:29 UTC
Created attachment 37477 [details]
Xorg log with MSI
Comment 8 Alex Deucher 2010-08-12 14:42:55 UTC
*** Bug 29444 has been marked as a duplicate of this bug. ***

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.