pk.khobdeh at nsn
Oct 14, 2011, 6:39 AM
Post #2 of 2
(197 views)
Permalink
|
|
Re: Errors when loading kernel with pf_ring
[In reply to]
|
|
Here is input I received from another channel:
>From what I've seen posted in other Linux distributions, there are cases
where the PCI device manufacturer intentionally specifies a base address
register's (BAR's) range to be out of range in order to force the kernel
to disable the use of that BAR on the device. As such, some Linux
distributions suppress the error below from being seen. So, it may be
that the messages seen are not contributing to the stability issues.
________________________________
From: ntop-misc-bounces [at] listgateway
[mailto:ntop-misc-bounces [at] listgateway] On Behalf Of Khobdeh
Payam-APK005
Sent: Monday, October 10, 2011 11:26 AM
To: ntop-misc [at] listgateway
Subject: [Ntop-misc] Errors when loading kernel with pf_ring
Hi Guys,
Has anyone ever seen errors such as this when booting linux after
pf_ring has been installed?
pci 0000:04:00.0 BAR 1: no parent found for device
[0xdd4000000-0xdd7fffff]
pci 0000:04:00.1 BAR 1: no parent found for device
[0xdd8000000-0xddbfffff]
pci 0000:05:00.0 BAR 1: no parent found for device
[0xde0000000-0xde3fffff]
pci 0000:05:00.1 BAR 1: no parent found for device
[0xde4000000-0xde7fffff]
ata2: failed to resume link (SControl 0)
kvm: disabled by bios
We see these errors and then sporatically we end up with PCIe bus faults
during captures that sometimes lead to a system reset...
PK
|
