On Thu, Dec 21, 2006 at 12:01:05AM +0100, Joel CARNAT wrote:
> On Mer, dc 20 2006 - 21:54, Manuel Bouyer wrote:
> > On Wed, Dec 20, 2006 at 06:58:44PM +0100, Joel CARNAT wrote:
> > > Hi,
> > > 
> > > I have this Intel dual-NIC:
> > > fxp0 at pci3 dev 4 function 0: i82550 Ethernet, rev 13
> > > fxp0: interrupting at irq 5
> > > fxp0: Ethernet address 00:02:b3:d6:cc:f9
> > > inphy0 at fxp0 phy 1: i82555 10/100 media interface, rev. 4
> > > fxp1 at pci3 dev 5 function 0: i82550 Ethernet, rev 13
> > > fxp1: interrupting at irq 12
> > > fxp1: Ethernet address 00:02:b3:d6:cc:fa
> > > inphy1 at fxp1 phy 1: i82555 10/100 media interface, rev. 4
> > > 
> > > I have NO timeout using NetBSD 4.99.4/i386.
> > > Since I switch to Xen, I get timeouts back (4.99.5/dom0 and 4.0_BETA2/dom0).
> > > 
> > > Can anyone details which patch have been applied on /i386 so I can try
> > > them on /xen please.
> > 
> > Probably none, the driver source is shared. Is it Xen2 or Xen3 ?
> > Do you get the timeout only under high network load, or is the adapter
> > completely non-functionnal ?
> > 
> 
> I'm running Xen3.
> 
> The adapter seems straight non-functionnal.
> 
> I can affect an IP, set parameters (media, capabilities, ...) but none
> traffic seem to pass through it - pinging don't answer, SSH never get
> the prompt, ...
> 
> If I wait long enough, the "buffer still DELWRI" is repeated on console.

Looks like an interrupt issue. Make sure you've not a mismatch in ACPI
between Xen and the dom0 kernel. Eventually try to disable acpi in
both Xen and the dom0 kernel (acpi=off on the xen command line,
and a kernel without APCI, or -c on the netbsd command line and
disable acpi
quit)

-- 
Manuel Bouyer <bouyer@antioche.eu.org>
     NetBSD: 26 ans d'experience feront toujours la difference
--