search for: pciehp

I have begun to see these messages in my morning reports: WARNING: Kernel Errors Present pciehp 0000:00:1c.0:pcie04: Link Training Error occurs ...: 146 Time(s) pciehp 0ng Error occurs ...: 1 Time(s) pcieport 0000:00:1c.0: bridge window [mem 0xd0a000000.0 failed with error -22 ...: 1 Time(s) r8168: probe of 0000:01:00.0 failed with error -22 ...: 702 Time(s) r8168: pro...

...system is first powered on, the boot sequence hangs after Starting udev: Initializing hardware ... storage network audio If I then hit the reset button, it reboots and successfully proceeds. Looking at rc.sysinit and the output of kmodule, it would appear that the problem is with loading the pciehp module. In dmesg after the successful boot I can see a bunch of errors from that module (cut'n'paste appended at the end of this message), but everything appears to be working correctly -- graphical boot was fine, gdm starts up and I have a functional X session when I log in. Any clues?...

...0 IO-APIC-edge timer 1: 240 0 IO-APIC-edge i8042 9: 0 0 IO-APIC-level acpi 169: 1361816047 0 IO-APIC-level wcte11xp, eth0 177: 648682 0 IO-APIC-level 3ware Storage Controller 201: 0 0 PCI-MSI pciehp 209: 0 0 PCI-MSI pciehp NMI: 1 0 LOC: 1327446761 1327446897 ERR: 0 MIS: 0 Thank you for answering ! Regards, Jan Prunk -- +------------------------------------------------------------------+ | Jan Prunk...

Hi Yum has just updated 5 of my Linux boxes running CentOS 4.3 to the 2.6.9-42 kernel. All is well on four of the boxes, but on the fifth the network card (eth0) will not work. I've downgraded the kernel to the previous version and the network card works fine again. I've tried removing and re-installing the new kernel, but the network card won't work with it. The details of the

Today I updated several servers running CentOS 4.3, and got the new 2.6.9-42 kernel. One of the machines serves as our firewall. After rebooting I lost all forwarding thru the machine. I reverted back to the 2.6.9-34 kernel and connectivity returned. During the few minutes that the new kernel was running I checked that the routing table looked OK, and with tcpdump I saw that indeed no traffic

...9; function='0x0'/> </hostdev> This all works fine during normal operation, but I noticed when we remove the NVMe drive (surprise hotplug event), the PCIe EP then seems "stuck"... here we see the link-down event on the host (when the drive is removed): [67720.177959] pciehp 0000:40:01.2:pcie004: Slot(238-1): Link Down [67720.178027] vfio-pci 0000:42:00.0: Relaying device request to user (#0) And naturally, inside of the Linux VM, we see the NVMe controller drop: [ 1203.491536] nvme nvme1: controller is down; will reset: CSTS=0xffffffff, PCI_STATUS=0xffff [ 1203.52275...

...o100 initializes and operates perfectly. Attached to this email is a copy of the kernel's configuration, and a list of currently loaded modules is as follows: Module Size Used by md5 4992 1 ipv6 260352 16 hw_random 6548 0 pciehp 97540 0 shpchp 101124 0 pci_hotplug 13060 2 pciehp,shpchp e1000 86788 0 evdev 10368 0 And output from /proc/interrupts immediately after loading the wctdm module: CPU0 CPU1 CPU2 CPU3 0:...

...x20 TTL=45 ID=26123 DF PROTO=TCP SPT =54197 DPT=445 WINDOW=8192 RES=0x00 SYN URGP=0 Jun 6 07:40:49 gway02 kernel: PROBE_BLACKIST: IN=eth0 OUT=eth1 SRC=183.179.211. 126 DST=216.185.71.132 LEN=48 TOS=0x08 PREC=0x40 TTL=111 ID=14994 PROTO=UDP SPT= 35947 DPT=49591 LEN=28 Jun 6 07:40:49 gway02 kernel: pciehp 0000:00:1c.4:pcie04: Card not present on Slot(0-1) Jun 6 07:40:49 gway02 kernel: e1000e 0000:02:00.0: eth0: removed PHC Jun 6 07:40:49 gway02 kernel: pciehp 0000:00:1c.4:pcie04: Card present on Slot(0-1) Jun 6 07:40:50 gway02 kernel: e1000e 0000:02:00.0: eth0: Timesync Tx Control register not se...

I need to work on a host which has been offline and powered down for some time. I has CentOS-6.9 installed. At some point it had two nics, one on the motherboard (still present and working) and one as an expansion card. When booted the console displays: pciehp 0000:00:1c:0:pcie04: Failed to check link status repeatedly. How do I tell the host to ignore the missing nic or remove it from the system configuration so that the error is removed. -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail...

...0003) [ 1.767005] pcieport 0000:06:04.0: enabling device (0000 -> 0003) [ 1.767368] pcieport 0000:06:05.0: enabling device (0000 -> 0002) [ 1.767738] pcieport 0000:06:06.0: enabling device (0000 -> 0002) [ 1.768112] pci_hotplug: PCI Hot Plug PCI Core version: 0.5 [ 1.768139] pciehp 0000:06:00.0:pcie24: Slot #0 AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug+ Surprise+ Interlock- NoCompl- LLActRep+ [ 1.768414] pciehp 0000:06:00.0:pcie24: service driver pciehp loaded [ 1.768431] pciehp 0000:06:03.0:pcie24: Slot #3 AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug+ Surprise+...

...</hostdev> > > This all works fine during normal operation, but I noticed when we > remove the NVMe drive (surprise hotplug event), the PCIe EP then seems > "stuck"... here we see the link-down event on the host (when the drive > is removed): > [67720.177959] pciehp 0000:40:01.2:pcie004: Slot(238-1): Link Down > [67720.178027] vfio-pci 0000:42:00.0: Relaying device request to user (#0) > > And naturally, inside of the Linux VM, we see the NVMe controller drop: > [ 1203.491536] nvme nvme1: controller is down; will reset: > CSTS=0xffffffff, PCI_S...

...roduce is_virtual_link instead * Drop unnecessary patches Mario Limonciello (7): drm/nouveau: Switch from pci_is_thunderbolt_attached() to dev_is_removable() drm/radeon: Switch from pci_is_thunderbolt_attached() to dev_is_removable() PCI: Drop pci_is_thunderbolt_attached() PCI: pciehp: Move check for is_thunderbolt into a quirk PCI: ACPI: Detect PCIe root ports that are used for tunneling PCI: Split up some logic in pcie_bandwidth_available() to separate function PCI: Exclude PCIe ports used for virtual links in pcie_bandwidth_available() drivers/gpu/drm/nouveau/...

...power or was reset Jan 20 17:42:15 laptop kernel: ehci-pci 0000:00:1a.0: cache line size of 64 is not supported Jan 20 17:42:15 laptop kernel: ehci-pci 0000:00:1d.0: cache line size of 64 is not supported Jan 20 17:42:15 laptop kernel: sd 0:0:0:0: [sda] Starting disk Jan 20 17:42:15 laptop kernel: pciehp 0000:3c:03.0:pcie204: Device 0000:5f:00.0 already exists at 0000:5f:00, cannot hot-add Jan 20 17:42:15 laptop kernel: pciehp 0000:3c:03.0:pcie204: Cannot add device at 0000:5f:00 Jan 20 17:42:15 laptop kernel: usb 1-1: reset high-speed USB device number 3 using ehci-pci Jan 20 17:42:15 laptop kerne...

...ot-cache hash table entries: 512 (order 0, 4096 bytes) msgmni has been set to 1975 Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253) io scheduler noop registered io scheduler deadline registered io scheduler cfq registered (default) pci_hotplug: PCI Hot Plug PCI Core version: 0.5 pciehp: PCI Express Hot Plug Controller Driver version: 0.4 acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5 Event-channel device installed. Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled Non-volatile memory driver v1.3 Linux agpgart interface v0.103 ipmi message handler version 39.2 IPM...

...works on Windows but not Linux because they handle ACPI hotplug slightly differently? Martin did some nice debug [1] and found that _DSM, _PS0, and _PS3 functions write the config bit at 0x488. The dmesg log [2] from zigarrre seems to show that _OSC failed (which I *think* means we won't use pciehp) and that there's a slot registered by acpiphp. Maybe this works on Windows via an ACPI hotplug event that runs AML to flip the 0x488 bit and rescans the bus? That would make more sense to me than the idea that the Nvidia driver does it. I could imagine the driver flipping the bit, but the b...

Konrad, et al, I am seeing visual corruption (almost like an interlacing problem) with i915 under Xen on some platforms using linux-3.8. See attached file for an example of the visual corruption. This particular platform is an HP Elitebook 2540p The same kernel and ramdisk, when booted as native linux does not show this corruption. dmesg is attached, as well (out.txt) - but I did not see

...in any of the working configurations. In non-working mode, all three displays (laptop + 2 external) are black and I've found no intervention that will revive them. One other notable difference that shows up is the BIOS initial video mode is different in native EFI mode: @@ -374,11 +379,11 @@ pciehp: PCI Express Hot Plug Controller Driver version: 0.4 nvidiafb: Device ID: 10de0ff6 efifb: probing for efifb -efifb: framebuffer at 0x81000000, using 3072k, total 3072k -efifb: mode is 1024x768x32, linelength=4096, pages=1 +efifb: framebuffer at 0x70000000, using 8100k, total 8100k +efifb: mode i...

From: Lukas Wunner <lukas at wunner.de> The integrated HDA controller on Nvidia GPUs can be hidden with a bit in the GPU's config space. Information about this scheme was provided by NVIDIA on their forums. Many laptops now ship with this device hidden, meaning that Linux users of affected platforms (where the HDMI connector comes off the NVIDIA GPU) cannot use HDMI audio

...i8042.nopnp psmouse.proto=bare" added to the kernel command line (and then you don't see any PS/2 and mousedev). So something immediately after the mousy things triggers the crash: 0.2293541 io scheduler cfq registered 0.2295071 pci_hotplug: PCI Hot Plug PCI Core version: 0.5 0.2295241 pciehp: PCI Express Hot Plug Controller Driver version: 0.4 0.2301241 Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled 0.2306111 Non-volatile memory driver u1.3 0.2306601 Linux agpgart interface u0.103 0.2307641 crash memory driver: version 1.1 0.2308301 rdac: device handler registered 0.2308...

On Thu, 2014-05-15 at 11:01 +0100, Ian Campbell wrote: > Please can you also post Xen's own dmesg (from "xl dmesg"). Please boot with loglvl=all on the hypervisor command line for this too. Ian.