lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 28 Aug 2006 07:55:55 +0200
From:	Jan De Luyck <ml_linuxkernel_20060528@...re.org>
To:	linux-kernel@...r.kernel.org
Subject: [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
-- 
Q:	How do you keep a moron in suspense?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists