http://bugzilla.novell.com/show_bug.cgi?id=553690 http://bugzilla.novell.com/show_bug.cgi?id=553690#c32 --- Comment #32 from Boris Derzhavets <bderzhavets@yahoo.com> 2009-11-19 16:47:25 UTC --- (In reply to comment #31)
This log together with one of the earlier provided ones makes it clear that swiotlb code is being instructed to write over a page table, due to running off the end of a valid buffer. It is not clear however whether the buffer was originally specified improperly, or whether stored data got corrupted e.g. during I/O. Since I can't reproduce the issue myself, I'm hoping that you would be able to rebuild your kernel with the debugging patch just attached, and then try and see whether it captures the problem any earlier (and of course doesn't have any adverse side effects). Will try. Do you, btw, also run into this issue when using mem=4G on the Xen command line?
Installer hangs downloading installation image. I just cannot get so far
Also I assume you're not having the machine do any other things while starting the guest?
Sure.
And from the last log I'm having the impression that only the third guest that got started actually crashed the machine - were the first two of different type, or does the problem not always occur?
Problem occurs always. The first F12 guest been installed, crashed Dom0 either via pygrub profile (guest's /boot of ext3fs type) or via regular xm-profile (guest's /boot of ext4fs type) attempting to load DomU via already built up image. I reproduced it twice with F12 (final release guest).Now i passed packages deployment phase via installation profile. Shut down DomU , then attempted to load and crashed right away in both cases. I just submitted only one serial log.
It would also be nice if you attached "lspci -nn" output for the machine, unless you know the problem is present on two sufficiently different ones.
No problem. It's C2D E8400, ASUS P5Q3, 4x2GB Kingston 1333, SATA 250 GB Seagate Barracuda -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.