RE: [Filtered!] [Xen-devel] Networking problems with xen3

["Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>]

> Everything looks fine during the boot, the network device is 
> detected, and the distro scripts bring it up as normal, going 
> as far as displaying a link up message in the log. However, 
> if I try and do something over the network, things 
> immediately go wrong.

The network card is trying to use irq3, which is normally reserved for
COM2. I'm wandering whether this is causing problems.

Can you try configuring the card for a different interrupt line?

Ian 
 
> Any attempt to do network relating stuff, including something 
> simple as a ping, and I get no response at all, with the 
> following then turning up in the system log:
> 
> NETDEV WATCHDOG: eth0: transmit timed out
> eth0: Transmit timed out, status 0003, PHY status 786d, resetting...
> eth0: link up, 100Mbps, full-duplex, lpa 0x45E1 NETDEV 
> WATCHDOG: eth0: transmit timed out
> eth0: Transmit timed out, status 0002, PHY status 786d, resetting...
> eth0: link up, 100Mbps, full-duplex, lpa 0x45E1 NETDEV 
> WATCHDOG: eth0: transmit timed out
> eth0: Transmit timed out, status 0002, PHY status 786d, resetting...
> eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
> 
> I imagine it would have kept repeating, but I cancelled the 
> ping at that point.
> 
> Booting in an equivalent non-xen kernel works fine. Nothing 
> in the linux dmesg output that shows up on diff, but i'm 
> including it anyway.
> 
> Attached:
>   dmesg.linux.ok - linux dmesg output from native 2.6.12
>   dmesg.linux.err - linux dmesg output from xen-ified 2.6.12
>   dmesg.xen.err - xen dmesg output from xen-ified 2.6.12
> 
> I didn't start up xend for retrieving the xen dmesg until 
> after capturing the network errors, so it's innocent in all this.
> 
> The last official changeset I have in my repo is:
> 
> changeset:   7622:0cae0c6436f5
> user:        kaf24@xxxxxxxxxxxxxxxxxxxx
> date:        Sat Nov  5 10:30:01 2005 +0100
> summary:     This patch is intended to make qemu support 
> ia64/vti. We have validated
> 
> The only other changesets I have are the ioports set I posted earlier.
> Anyone got any ideas as to what is going wrong?
> 
> 
> J
> --
> Jody Belka
> knew (at) pimb (dot) org
> 

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel