Comment 72 for bug 442194

Revision history for this message
In , Trenn-novell (trenn-novell) wrote :

I do not expect the message:
<4>ACPI: I/O resource vt596_smbus [0x400-0x407] conflicts with ACPI region SMRG
[0x400-0x40f]
Has anything to do with it -> adjusting title.

What happens is that the IRQs are assigned in a totally other way with 11.0 than with 10.3. Not only via-rhine network card driver also sata IRQs are assigned different. (Here from network card):
(11.0):
via-rhine.c:v1.10-LK1.4.3 2007-03-06 Written by Donald Becker
ACPI: PCI Interrupt 0000:00:12.0[A] -> GSI 23 (level, low) -> IRQ 23

pata_via 0000:00:0f.1: version 0.3.3
ACPI: PCI Interrupt 0000:00:0f.1[A] -> GSI 20 (level, low) -> IRQ 20

(10.3):
via-rhine.c:v1.10-LK1.4.3 2007-03-06 Written by Donald Becker
ACPI: PCI Interrupt 0000:00:12.0[A] -> GSI 23 (level, low) -> IRQ 20

pata_via 0000:00:0f.1: version 0.3.1
ACPI: PCI Interrupt 0000:00:0f.1[A] -> GSI 20 (level, low) -> IRQ 16

Strange is that I cannot see any warning/error about it.
Does pci=noacpi bring up the machine as expected?
Maybe acpi_enforce_resources=no helps?

If you still have 10.3, one might also want to attach /proc/interrupts of 10.3 and a newer version. Then we see all the IRQ assignment changes.
I am still puzzled why the IRQ setup is so totally different. Possibly it's really a "modify chipset settings" command like smbus code be used for? Reconfiguring something on the chipset. I fear the only way to find that out could be a git bisect in the end...