WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] problem with the pro/1000 driver for intel gigabitethern

To: "Rich Persaud" <Rich.Persaud@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] problem with the pro/1000 driver for intel gigabitethernet card
From: Jon Mason <jdmason@xxxxxxxxxx>
Date: Wed, 11 May 2005 16:30:26 -0500
Cc: Kip Macy <kip.macy@xxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, peter bier <peter_bier@xxxxxx>
Delivery-date: Wed, 11 May 2005 21:30:07 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <40F951C7DA13C0428B4A1846E7B204F301B264@xxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Organization: IBM
References: <40F951C7DA13C0428B4A1846E7B204F301B264@xxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.7.2
Thanks Rich for opening the bug.

I backleveled the e1000 driver to the one in xen-2.0, and I don't see the 
problem anymore (on my 3rd attempt now, and we seeing it every time before).

The working driver version is 5.5.4-k2. 
The non-working driver version is 5.6.10.1-k2.
The latest version available is 6.0.54.

I am going to try the latest/greatest e1000 driver available, and see if that 
makes any difference.

Thanks,
Jon

On Wednesday 11 May 2005 04:08 pm, Rich Persaud wrote:
> I have seen this (intermittent) problem on two 4P boxes and a laptop, all
> using e1000 driver.
>
> What kind of network input triggers the end of the hang? I have seen this
> hang on a busy network with lots of broadcast traffic.  Did not see it with
> a network restart that was separate from domain shutdown.
>
> Bug filed:
> http://bugzilla.xensource.com/cgi-bin/bugzilla/show_bug.cgi?id=35
>
> Rich
>
> -----Original Message-----
> From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx on behalf of Kip Macy
> Sent: Wed 5/11/2005 12:06 PM
> To: Jon Mason
> Cc: peter bier; xen-devel@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Xen-devel] problem with the pro/1000 driver for intel
> gigabitethernet card
>
> We're not seeing it on 2.0.5 either. The first thing I would do would
> be to diff the driver between 2.6.10 and 2.6.11.
>
>                       -Kip
>
> On 5/11/05, Jon Mason <jdmason@xxxxxxxxxx> wrote:
> > I have been seeing the exact same problem for a while (on xen-unstable). 
> > I think I didn't see this problem on Xen 2.0.5 (but I'm not 100% sure).
> >
> > I can open a bug in bugzilla.xensource.com if no one else is willing.
> >
> > Thanks,
> > Jon
> >
> > On Wednesday 11 May 2005 12:41 pm, Kip Macy wrote:
> > > I can confirm that I've seen the exact same behaviour.
> > >
> > >                     -Kip
> > >
> > > On 5/11/05, peter bier <peter_bier@xxxxxx> wrote:
> > > > I encountered a problem with dom0 when rebooting and running an intel
> > > > gigabit card using the pro/1000 driver. When the system tries to shut
> > > > down I get the following output of an strace command :
> > > >
> > > >    .........
> > > > 17:10:49.063616 socket(PF_INET, SOCK_DGRAM, IPPROTO_IP) = 3
> > > > <0.000029> 17:10:49.063689 ioctl(3, 0x8913, 0xbffffc80) = 0
> > > > <0.000018>
> > > > 17:10:49.063751 ioctl(3, 0x8914, 0xbffffc80) = 0 <535.114722>
> > > > 17:19:44.178567 close(3)                = 0 <0.000026>
> > > > 17:19:44.178679 exit_group(0)           = ?
> > > >
> > > > observe the more than 500 seconds it takes for the second ioctl to
> > > > complete !! I have found out that any input on the console keyboard
> > > > or network interface immediately causes the system call to return.
> > > >
> > > > Is there a problem with interrupt delivery ?
> > > >
> > > > Peter Bier
> > > >
> > > > _______________________________________________
> > > > Xen-devel mailing list
> > > > Xen-devel@xxxxxxxxxxxxxxxxxxx
> > > > http://lists.xensource.com/xen-devel
> > >
> > > _______________________________________________
> > > Xen-devel mailing list
> > > Xen-devel@xxxxxxxxxxxxxxxxxxx
> > > http://lists.xensource.com/xen-devel
> >
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@xxxxxxxxxxxxxxxxxxx
> > http://lists.xensource.com/xen-devel
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel

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