On Thu, 8 Dec 2005, Adam Heath wrote:
> On Thu, 8 Dec 2005, Adam Heath wrote:
>
> > On Thu, 8 Dec 2005, Ian Pratt wrote:
> >
> > > > Attached are the xen3+2.6.12.6 and plain 2.6.12.6 boot logs
> > > > and configs.
> > >
> > > You might want to try putting maxcpus=1 on the Linux command line. If
> > > this works, I suspect it might be the nash module loading bug; try
> > > upgrading nash on the machine you run mkinitrd on.
> >
> > I'm not using an initrd.
>
> I just tried maxcpus=1 on both the xen and linux lines; still no go.
So, I'm stilling having problems with this hardware; however, now it's with
xen 2.0.6, and 2.6.11.9.
The symptoms are like memory corruption; bzip2 reported inconsisent checksums;
/var/lib/dpkg/diversions was all nulls. Successive logins returned varying
syntax errors in /etc/bash_completion, with the last login having no errors.
However, memtest86+.bin reported no problems at all.
I'm at a loss as to explain this; the exact same hardware has been running a
production server for over a year now, without any problems whatsoever. This
issue is solely occuring inside xen.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
Home