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/
Home Products Support Community News


Re: [Xen-devel] Cannot load latest kernel on AMD quad-core

On 04/27/2010 01:35 PM, Gerry Reno wrote:
On 04/27/2010 05:15 AM, Pasi Kärkkäinen wrote:
On Mon, Apr 26, 2010 at 10:48:44PM -0400, Gerry Reno wrote:
Pasi, my grub.conf is attached.

Ok, fix it to be like this:

module /vmlinuz-
root=/dev/mapper/vg--grp--01--23--02--2-LogVol00 dummy=dummy ro
earlyprintk=xen console=hvc0 console=ttyS0 console=ttyUSB0,115200n8

aka remove "quiet" and add "earlyprintk=xen console=hvc0"

-- Pasi

Pasi, this gave some more output.  Sorry the video is fuzzy but this
happens by youtube postprocessing.  Here is new link:

If you have somewhere I can ftp original video file, it is clearer.
File is about 90 MB.


Original video is posted here:

It's very difficult to see the problem from that video :(
We'd really need a serial console log.

Also you I wonder why the screen goes blank in the end?
Before that it seems to mount the root (?) filesystem OK..

Do you have some console font/videomode thingie configured?
See the "Dom0 console gets all weird and corrupted in the end of the boot process" from:

Also please add "nomodeset" option to the end of the pvops kernel boot options,
like suggested on pvops examples/docs.

-- Pasi

Ok, I finally got a little more output using nomodeset. There is a soft lockup bug. Attaching screenshots.


I've been changing various settings trying to figure out what is the problem and today after a very long wait (> 5 min) I was able to see a login prompt. But things are not well. During the boot I now see:
XENBUS: Unable to read cpu state.
XENBUS: Unable to read cpu state.
XENBUS: Unable to read cpu state.
XENBUS: Unable to read cpu state.

and while logged in I get a lot of these type of messages every few minutes:
INFO: task xxxxxxx:nnn  blocked for more than 120 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

and I notice a number of errors in the xen logs with I'm attaching.

Can someone look at these logs and see if there is anything I can do on my end to help fix the problem?


Attachment: domain-builder-ng.log
Description: Text Data

Attachment: xend.log
Description: Text Data

Attachment: xend-debug.log
Description: Text Data

Attachment: xen-hotplug.log
Description: Text Data

Xen-devel mailing list
<Prev in Thread] Current Thread [Next in Thread>