Comment #29 From Øyvind Stegard 2010-05-10 17:31:29 (-) [reply] -------
(In reply to comment #28)
> Thank you for testing. Appearently, there might be a clash in the PCI device or
> bus configuration. Unfortunately, I'm not expert in this area. It might be a
> good idea to check the PCI device setup using lspci (compare good and bad
> behaviour).
Indeed, the PCI configuration for radeon is different under KMS (bad) compared
to UMS (good):
Code:
--- lspci-radeon-good.txt 2010-05-10 19:13:21.003538070 +0200
+++ lspci-radeon-bad.txt 2010-05-10 19:19:45.254230183 +0200
[...]
- Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
+ Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+
[...]
- Interrupt: pin A routed to IRQ 16
+ Interrupt: pin A routed to IRQ 30
[...]
- Capabilities: [80] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
- Address: 0000000000000000 Data: 0000
+ Capabilities: [80] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable+
+ Address: 00000000fee0100c Data: 41b9
+ Kernel driver in use: radeon
There is no difference for the HDA Intel PCI configuration.
Also, KMS causes problems for my wireless PCI network controller/driver iwl3945 (drops connection during Flash fullscreen video streaming, when snd-hda-intel crackling is at its worst

. So, my system probably has issues out of scope for this bug report, wrt. to KMS. Thank you for all help.