Description of problem: Although network config appears normal, cannot reach any host except local machine ip addr. Version-Release number of selected component (if applicable): kernel: 2.6.18-1.2857.4.2.fc6.0.2.sctxen How reproducible: always Steps to Reproduce: 1. Boot into xen kernel 2.6.18-1.2857.4.2.fc6.0.2.sctxen 2. Attempt to ping local gateway or any other host 3. Actual results: Ping unsuccessful to any host except local machine ip address "dmesg" reports truncated IRQ numbers compared to non-xen kernel "dmesg" reports 251 instances of "late interrupt" on eth0 Expected results: Successful ping to any reachable network host "dmesg" report normal IRQ numbers No "late interrupt" messages Additional info: The IRQ assignments don't look right to me. Here's how they differ in "dmesg" between non-Xen (<) and Xen (>) kernel boots. At a glance, it looks like the IRQ numbers are being truncated. 191c163 < ACPI: PCI Interrupt 0000:00:01.0[A] -> GSI 16 (level, low) -> IRQ 169 --- > ACPI: PCI Interrupt 0000:00:01.0[A] -> GSI 16 (level, low) -> IRQ 16 193c165 < ACPI: PCI Interrupt 0000:00:1c.0[A] -> GSI 16 (level, low) -> IRQ 169 --- > ACPI: PCI Interrupt 0000:00:1c.0[A] -> GSI 16 (level, low) -> IRQ 16 195c167 < ACPI: PCI Interrupt 0000:00:1c.1[B] -> GSI 17 (level, low) -> IRQ 177 --- > ACPI: PCI Interrupt 0000:00:1c.1[B] -> GSI 17 (level, low) -> IRQ 17 197c169 < ACPI: PCI Interrupt 0000:00:1c.3[D] -> GSI 19 (level, low) -> IRQ 185 --- > ACPI: PCI Interrupt 0000:00:1c.3[D] -> GSI 19 (level, low) -> IRQ 18 Also, there are over 250 of these messages in "dmesg": eth0: late interrupt. Here are the last several lines from "dmesg": eth0: late interrupt. device vif0.0 entered promiscuous mode xenbr0: port 1(vif0.0) entering learning state xenbr0: topology change detected, propagating xenbr0: port 1(vif0.0) entering forwarding state device peth0 entered promiscuous mode
The interrupt numbers haven't been truncated. The IRQs you get in dom0 are actually virtualised by the hypervisor. Please attach the complete dmesg as well as a dmesg from a baremetal kernel. Thanks.
Created attachment 143645 [details] dmesg from kernel 2.6.18-1.2857.6.1.fc6.jwltest.15 As requested, dmesg content from baremetal kernel
Created attachment 143647 [details] dmesg from kernel 2.6.18-1.2857.4.2.fc6.0.2.sctxen As requested, dmesg from xen kernel
*** This bug has been marked as a duplicate of 219277 ***