[2.6.17.11] strange pcie errors/warnings on Abit KN9-SLI mainboard
Hello,
(running 2.6.17.11 vanilla on Debian SID)
I recently acquired a new pc, with an ABIT KN9-SLI mainboard, using an AMD64x2 AM2 processor.
System boots fine, but I have some messages/errors in the dmesg that I'm worried about. Googling around for them didn't really show up much.
First:
Aug 27 15:35:04 whocares kernel: PCI-DMA: Disabling IOMMU.
IOMMU is (as far as I can see) enabled:
whocares:/var/log# cat /usr/src/build/linux-2.6/.config | grep IOMMU CONFIG_GART_IOMMU=y
I can't really determine if this is normal. According to the code it seems that this is disabled by default when you don't have AGP? (I'm not a kernel-coder, so I may be very wrong on this)
Second:
Aug 27 15:35:04 whocares kernel: PCI: Setting latency timer of device 0000:00:0a.0 to 64 Aug 27 15:35:04 whocares kernel: pcie_portdrv_probe->Dev[0376:10de] has invalid IRQ. Check vendor BIOS Aug 27 15:35:04 whocares kernel: assign_interrupt_mode Found MSI capability Aug 27 15:35:04 whocares kernel: Allocate Port Service[0000:00:0a.0:pcie00] Aug 27 15:35:04 whocares kernel: Allocate Port Service[0000:00:0a.0:pcie03] Aug 27 15:35:04 whocares kernel: PCI: Setting latency timer of device 0000:00:0b.0 to 64 Aug 27 15:35:04 whocares kernel: pcie_portdrv_probe->Dev[0374:10de] has invalid IRQ. Check vendor BIOS Aug 27 15:35:04 whocares kernel: assign_interrupt_mode Found MSI capability Aug 27 15:35:04 whocares kernel: Allocate Port Service[0000:00:0b.0:pcie00] Aug 27 15:35:04 whocares kernel: Allocate Port Service[0000:00:0b.0:pcie03] Aug 27 15:35:04 whocares kernel: PCI: Setting latency timer of device 0000:00:0c.0 to 64 Aug 27 15:35:04 whocares kernel: pcie_portdrv_probe->Dev[0374:10de] has invalid IRQ. Check vendor BIOS Aug 27 15:35:04 whocares kernel: assign_interrupt_mode Found MSI capability Aug 27 15:35:04 whocares kernel: Allocate Port Service[0000:00:0c.0:pcie00] Aug 27 15:35:04 whocares kernel: Allocate Port Service[0000:00:0c.0:pcie03] Aug 27 15:35:04 whocares kernel: PCI: Setting latency timer of device 0000:00:0d.0 to 64 Aug 27 15:35:04 whocares kernel: pcie_portdrv_probe->Dev[0378:10de] has invalid IRQ. Check vendor BIOS Aug 27 15:35:04 whocares kernel: assign_interrupt_mode Found MSI capability Aug 27 15:35:04 whocares kernel: Allocate Port Service[0000:00:0d.0:pcie00] Aug 27 15:35:04 whocares kernel: Allocate Port Service[0000:00:0d.0:pcie03] Aug 27 15:35:04 whocares kernel: PCI: Setting latency timer of device 0000:00:0e.0 to 64 Aug 27 15:35:04 whocares kernel: pcie_portdrv_probe->Dev[0375:10de] has invalid IRQ. Check vendor BIOS Aug 27 15:35:04 whocares kernel: assign_interrupt_mode Found MSI capability Aug 27 15:35:04 whocares kernel: Allocate Port Service[0000:00:0e.0:pcie00] Aug 27 15:35:04 whocares kernel: Allocate Port Service[0000:00:0e.0:pcie03] Aug 27 15:35:04 whocares kernel: PCI: Setting latency timer of device 0000:00:0f.0 to 64 Aug 27 15:35:04 whocares kernel: pcie_portdrv_probe->Dev[0377:10de] has invalid IRQ. Check vendor BIOS Aug 27 15:35:04 whocares kernel: assign_interrupt_mode Found MSI capability Aug 27 15:35:04 whocares kernel: Allocate Port Service[0000:00:0f.0:pcie00] Aug 27 15:35:04 whocares kernel: Allocate Port Service[0000:00:0f.0:pcie03]
Any ideas what might be wrong? If anything is wrong, that is.
Thanks!
Jan
Signature · 1 line
Q: How do you keep a moron in suspense?
Quoted 14 lines · Jan De Luyck
Hello,
(running 2.6.17.11 vanilla on Debian SID)
I recently acquired a new pc, with an ABIT KN9-SLI mainboard, using an AMD64x2 AM2 processor.
System boots fine, but I have some messages/errors in the dmesg that I'm worried about. Googling around for them didn't really show up much.
First:
Aug 27 15:35:04 whocares kernel: PCI-DMA: Disabling IOMMU.
Quoted 7 lines
IOMMU is (as far as I can see) enabled:
whocares:/var/log# cat /usr/src/build/linux-2.6/.config | grep IOMMU CONFIG_GART_IOMMU=yI can't really determine if this is normal. According to the code it seems that this is disabled by default when you don't have AGP? (I'm not a kernel-coder, so I may be very wrong on this)
Hi,
unless you have >= 4Gb of ram you don't need an IOMMU (in fact using it would only cause extra overhead)... so the kernel will not use it in that case.
Greetings,
Arjan van de Ven