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: "peter bier" <peter_bier@xxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] problem with the pro/1000 driver for intel gigabitethernet card
From: "James Harper" <james.harper@xxxxxxxxxxxxxxxx>
Date: Thu, 12 May 2005 10:09:58 +1000
Delivery-date: Thu, 12 May 2005 00:09:39 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcVWR4WeA8UwE1BMT0SVsnINNYQJ6AAPy9kQ
Thread-topic: [Xen-devel] problem with the pro/1000 driver for intel gigabitethernet card
On a server where I use an e1000 card, it seems to work perfectly until
I start a domain at which point things crash and burn (kernel oops - see
previous post).

The exact point at which it crashes is when the new domain starts to
access the disks or network. My disks are all iSCSI so it seems that
there might be a race somewhere.

James

> -----Original Message-----
> From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-devel-
> bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of peter bier
> Sent: Thursday, 12 May 2005 02:25
> To: xen-devel@xxxxxxxxxxxxxxxxxxx
> Subject: [Xen-devel] problem with the pro/1000 driver for intel
> gigabitethernet card
> 
> 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