search for: 10a7

...ice [8086:340a] error status/mask=00002000/00001001 pcieport 0000:00:03.0: [13] Advisory Non-Fatal pcieport 0000:00:03.0: Error of this Agent(0018) is reported first igb 0000:04:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=0400(Receiver ID) igb 0000:04:00.0: device [8086:10a7] error status/mask=00002001/00002000 igb 0000:04:00.0: [ 0] Receiver Error (First) igb 0000:04:00.1: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=0401(Receiver ID) igb 0000:04:00.1: device [8086:10a7] error status/mask=00002001/00002000 igb 0000:04:00.1: [ 0] Receiver...

...g an updated "igb" driver into the CentOS 5.2 installation for a HP DL165G5p(I'm not ready yet for CentOS 5.3). Anyways, I had a pretty basic question, I added a bunch of entries into the pci.ids file that were not there previously that came with the newer driver, including: 10a7 82575EB Gigabit Network Connection 10a9 82575EB Gigabit Backplane Connection 10c9 82576 Gigabit Network Connection 10d6 82575GB Gigabit Network Connection 10e6 82576 Gigabit Network Connection 10e7 82576 Gigabit Network Connection 10e8 82576 Gi...

...ice [8086:340a] error status/mask=00002000/00001001 pcieport 0000:00:03.0: [13] Advisory Non-Fatal pcieport 0000:00:03.0: Error of this Agent(0018) is reported first igb 0000:04:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=0400(Receiver ID) igb 0000:04:00.0: device [8086:10a7] error status/mask=00002001/00002000 igb 0000:04:00.0: [ 0] Receiver Error (First) igb 0000:04:00.1: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=0401(Receiver ID) igb 0000:04:00.1: device [8086:10a7] error status/mask=00002001/00002000 igb 0000:04:00.1: [ 0] Receiver...

...tus/mask=00002000/00001001 > pcieport 0000:00:03.0: [13] Advisory Non-Fatal > pcieport 0000:00:03.0: Error of this Agent(0018) is reported first > igb 0000:04:00.0: PCIe Bus Error: severity=Corrected, type=Physical > Layer, id=0400(Receiver ID) > igb 0000:04:00.0: device [8086:10a7] error status/mask=00002001/00002000 > igb 0000:04:00.0: [ 0] Receiver Error (First) > igb 0000:04:00.1: PCIe Bus Error: severity=Corrected, type=Physical > Layer, id=0401(Receiver ID) > igb 0000:04:00.1: device [8086:10a7] error status/mask=00002001/00002000 > igb 0000:...

...ut in that case they're throwing AER errors instead of just unit hangs: pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: id=0000 igb 0000:04:00.1: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, id=0401(Requester ID) igb 0000:04:00.1: device [8086:10a7] error status/mask=00004000/00000000 igb 0000:04:00.1: [14] Completion Timeout (First) igb 0000:04:00.1: broadcast error_detected message igb 0000:04:00.1: broadcast slot_reset message igb 0000:04:00.1: broadcast resume message igb 0000:04:00.1: AER: Device recovery successful Spammed conti...

...001001 >> pcieport 0000:00:03.0: [13] Advisory Non-Fatal >> pcieport 0000:00:03.0: Error of this Agent(0018) is reported first >> igb 0000:04:00.0: PCIe Bus Error: severity=Corrected, type=Physical >> Layer, id=0400(Receiver ID) >> igb 0000:04:00.0: device [8086:10a7] error status/mask=00002001/00002000 >> igb 0000:04:00.0: [ 0] Receiver Error (First) >> igb 0000:04:00.1: PCIe Bus Error: severity=Corrected, type=Physical >> Layer, id=0401(Receiver ID) >> igb 0000:04:00.1: device [8086:10a7] error status/mask=00002001/0000200...

...tus/mask=00002000/00001001 > pcieport 0000:00:03.0: [13] Advisory Non-Fatal > pcieport 0000:00:03.0: Error of this Agent(0018) is reported first > igb 0000:04:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, > id=0400(Receiver ID) > igb 0000:04:00.0: device [8086:10a7] error status/mask=00002001/00002000 > igb 0000:04:00.0: [ 0] Receiver Error (First) > igb 0000:04:00.1: PCIe Bus Error: severity=Corrected, type=Physical Layer, > id=0401(Receiver ID) > igb 0000:04:00.1: device [8086:10a7] error status/mask=00002001/00002000 > igb 0000:...

...rowing AER errors instead of > just unit hangs: > > pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: id=0000 > igb 0000:04:00.1: PCIe Bus Error: severity=Uncorrected (Non-Fatal), > type=Transaction Layer, id=0401(Requester ID) > igb 0000:04:00.1: device [8086:10a7] error status/mask=00004000/00000000 > igb 0000:04:00.1: [14] Completion Timeout (First) > igb 0000:04:00.1: broadcast error_detected message > igb 0000:04:00.1: broadcast slot_reset message > igb 0000:04:00.1: broadcast resume message > igb 0000:04:00.1: AER: Device recovery...

...64.iso,hdc:cdrom,r''] boot="dc" # enable remote vnc access until video card driver is installed vnc = 1 acpi=1 sdl=0 #serial=''pty'' gfx_passthru=1 pci=[''00:02.0''] my dmesg contains the following: Command line: placeholder root=UUID=05509dc2-10a7-4332-8782-e13a77144f7d ro rd.md=0 rd.lvm=0 rd.dm=0 rd.luks=0 vconsole.keymap=us rhgb quiet intel_iommu=on xm dmesg: (XEN) Intel VT-d supported page sizes: 4kB. (XEN) Intel VT-d supported page sizes: 4kB. (XEN) Intel VT-d Snoop Control not enabled. (XEN) Intel VT-d Dom0 DMA Passthrough not enabled....

Hi experts I use xen-4.0.0 and dom0 is 2.6.33 and domU is 2.6.34 #lspci ............... 01:00.0 Ethernet controller: Intel Corporation Unknown device 10a7 (rev 02) 01:00.1 Ethernet controller: Intel Corporation Unknown device 10a7 (rev 02) 05:00.0 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet Controller (rev 06) 05:00.1 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet Controller (rev 06) my *intent* it to let domU to...

Miredo is run as a server from the command line: /usr/sbin/miredo The man page says the signal SIGTERM stops the server. How do I send SIGTERM to the server? Or SIGHUP, as I want to make a change to the config file. And once I get this as I want it, how do I run it at system boot?

...;> just unit hangs: >> >> pcieport 0000:00:03.0: AER: Uncorrected (Non-Fatal) error received: >> id=0000 >> igb 0000:04:00.1: PCIe Bus Error: severity=Uncorrected (Non-Fatal), >> type=Transaction Layer, id=0401(Requester ID) >> igb 0000:04:00.1: device [8086:10a7] error >> status/mask=00004000/00000000 >> igb 0000:04:00.1: [14] Completion Timeout (First) >> igb 0000:04:00.1: broadcast error_detected message >> igb 0000:04:00.1: broadcast slot_reset message >> igb 0000:04:00.1: broadcast resume message >> igb 0000:0...

...RX packets:24 errors:0 dropped:0 overruns:0 frame:0 TX packets:4 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:500 RX bytes:2223 (2.1 KiB) TX bytes:368 (368.0 B) tap2.0 Link encap:Ethernet HWaddr 12:a7:b2:a4:26:1c inet6 addr: fe80::10a7:b2ff:fea4:261c/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:18 errors:0 dropped:0 overruns:0 frame:0 TX packets:4 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:500 RX bytes:1863 (1.8 KiB) TX bytes:36...

On 01/27/2017 06:08 AM, Karel Hendrych wrote: > Have you tried to eliminate all power management features all over? I've been trying to find and disable all power management features but having relatively little luck with that solving the problems. Stabbing the the dark I've tried different ACPI settings, including completely disabling it, disabling CPU frequency scaling, and setting

...[ 48.306564] Event-channel device installed. Aug 5 15:05:17 ubuntu kernel: [ 139.755233] pcifront pci-0: Installing PCI frontend Aug 5 15:05:17 ubuntu kernel: [ 139.755392] pcifront pci-0: Creating PCI Frontend Bus 0000:00 Aug 5 15:05:17 ubuntu kernel: [ 139.755999] pci 0000:00:00.1: [8086:10a7] type 0 class 0x000200 Aug 5 15:05:17 ubuntu kernel: [ 139.756171] pci 0000:00:00.1: reg 10: [mem 0xfa3e0000-0xfa3fffff] Aug 5 15:05:17 ubuntu kernel: [ 139.756295] pci 0000:00:00.1: reg 14: [mem 0xfa600000-0xfa7fffff] Aug 5 15:05:17 ubuntu kernel: [ 139.756410] pci 0000:00:00.1: reg 18: [io...