> After a few day of off and on testing it would appear that > adding "nousb" to the 2.6 kernel boot options in the grub > config fixes this problem. I have tested with the last few > days of unstable builds without a hang. I have no idea why > this works but, so far it does. I have not had a chance to > test much with 2.0.6 so I can''t say for sure if the same > holds true there.Interesting. This might turn out just to be a differnce in kernel config between the xen and native kernels you''ve tried. It might be interesting to compile up a stock 2.6.11.10 native kernel with a config as close as possible to the xen0 one, and see if the same problem is exhibited. Also, if there are any USB options in the BIOS (e.g. legacy support) it might be interesting to know if they have any effect. It would be particularly interesting to know what the unstable tree does on these systems, as the code is quite different. Best, Ian _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> 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. David On 5/27/05, Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk> wrote:> > > After a few day of off and on testing it would appear that > > adding "nousb" to the 2.6 kernel boot options in the grub > > config fixes this problem. I have tested with the last few > > days of unstable builds without a hang. I have no idea why > > this works but, so far it does. I have not had a chance to > > test much with 2.0.6 so I can''t say for sure if the same > > holds true there. > > Interesting. This might turn out just to be a differnce in kernel config > between the xen and native kernels you''ve tried. It might be interesting > to compile up a stock 2.6.11.10 native kernel with a config as close as > possible to the xen0 one, and see if the same problem is exhibited. > > Also, if there are any USB options in the BIOS (e.g. legacy support) it > might be interesting to know if they have any effect. > > It would be particularly interesting to know what the unstable tree does > on these systems, as the code is quite different. > > Best, > Ian >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
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@lists.xensource.com http://lists.xensource.com/xen-users
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@flanagan.ie> 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@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users