Re: FW: [Xen-users] Problem with Dell Poweredge 1850

To:	Barry Flanagan <barryf-lists@xxxxxxxxxxx>
Subject:	Re: FW: [Xen-users] Problem with Dell Poweredge 1850
From:	David H <davidh.davidh@xxxxxxxxx>
Date:	Fri, 27 May 2005 10:52:39 -0700
Cc:	xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date:	Fri, 27 May 2005 17:52:01 +0000
Domainkey-signature:	a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=NzJFYp+HryPLMrnOZZELKT1RNdKK6gqf3PmryXiNQ3cgBvjT71oFRKJwsKgRJ1Vi5al0BI3zmvi7MDqzw3pePBvgiP+TVpMzvg3VmuGtbuNQN4Jqk5nyf+dSM4d02oHsJfIgy4PzGIZP4QSc+VxlQcJKqnMNa6IH0qwihWfeXWA=
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to:	<429747EC.3090401@xxxxxxxxxxx>
List-help:	<mailto:xen-users-request@lists.xensource.com?subject=help>
List-id:	Xen user discussion <xen-users.lists.xensource.com>
List-post:	<mailto:xen-users@lists.xensource.com>
List-subscribe:	<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe:	<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References:	<A95E2296287EAD4EB592B5DEEFCE0E9D1E424B@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <c4e0079f05052708551a597c88@xxxxxxxxxxxxxx> <429747EC.3090401@xxxxxxxxxxx>
Reply-to:	David H <davidh.davidh@xxxxxxxxx>
Sender:	xen-users-bounces@xxxxxxxxxxxxxxxxxxx

I am using a SuperMicro server with the same Intel E7520 "Lindenhurst"
chipset as the dell 1850.  It looks like the 1600SC has a ServerWorksR
GC-SL chipset.  Both have onboard intel NICs(82540/82544), they may
share other componets.

David

On 5/27/05, Barry Flanagan <barryf-lists@xxxxxxxxxxx> wrote:
> David H wrote:
> >>It would be particularly interesting to know what the unstable tree does
> >>on these systems, as the code is quite different.
> >
> >
> > I may not have been clear; I have been testing with "unstable".  If I
> > build unstable with the default configuration and boot dom0 with the
> > following grub entry I can make dom0 hang using a number of IO
> > intensive commands.  Tar, cp, mkfs, all can cause the problem and
> > using scp to copy a large file to another machine will hang the domain
> > in no time.  Xen still responds on the serial console.
> >
> > title Xen 2.0.6 / XenLinux 2.6.11
> >         root (hd0,0)
> >         kernel /xen.gz dom0_mem=131072 console=com1 watchdog com1=115200,8n1
> >         module /vmlinuz-2.6.11-xen0 root=/dev/VolGroup00/LogVol00 ro
> > console=tty0
> >         module /initrd-xen-2.0.img
> >
> > Add "nousb"
> > module /vmlinuz-2.6.11-xen0 root=/dev/VolGroup00/LogVol00 ro console=tty0 
> > nousb
> > and the problem goes away.
> >
> 
> This corresponds with my experience. I had the same type of problem and
> got around it by disabling all USB in the xen-0 kernel config. This was
> also on a dell box, but an SC1600 rather than an 1850.
> 
> --
> 
> -Barry Flanagan
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
>

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