From: Jan De Luyck <ml_linuxkernel_20060528@kcore.org>
To: linux-kernel@vger.kernel.org
Subject: [2.6.17.11] strange pcie errors/warnings on Abit KN9-SLI mainboard
Date: Mon, 28 Aug 2006 07:55:55 +0200 [thread overview]
Message-ID: <200608280755.56015.ml_linuxkernel_20060528@kcore.org> (raw)
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?
next reply other threads:[~2006-08-28 5:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-28 5:55 Jan De Luyck [this message]
2006-08-28 8:14 ` [2.6.17.11] strange pcie errors/warnings on Abit KN9-SLI mainboard Arjan van de Ven
-- strict thread matches above, loose matches on Subject: below --
2006-08-28 9:50 Chuck Ebbert
2006-08-29 5:19 ` Jan De Luyck
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200608280755.56015.ml_linuxkernel_20060528@kcore.org \
--to=ml_linuxkernel_20060528@kcore.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.