On 04/29/2010 10:41 AM, Mike Viau wrote:
>
Thu, 29 Apr 2010 09:54:07 -0400 <greno@xxxxxxxxxxx> wrote: 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-2.6.32.10
> >>>>>>
root=/dev/mapper/vg--grp--01--23--02--2-LogVol00 dummy=dummy ro
> >>>>>> earlyprintk=xen console=hvc0
console=ttyS0 console=ttyUSB0,115200n8
> >>>>>> text
> >>>>>>
> >>>>>> 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:
> >>>>> http://www.youtube.com/watch?v=jePyapeHpSI
> >>>>>
> >>>>> -Gerry
> >>>> If you have somewhere I can ftp original video
file, it is clearer.
> >>>> File is about 90 MB.
> >>>>
> >>>> -Gerry
> >>>>
> >>> Original video is posted here:
> >>> http://greno-misc.googlecode.com/files/MOV03932.MPG
> >>>
> >> 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:
> >> http://wiki.xensource.com/xenwiki/XenParavirtOps
> >>
> >> 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.
> >
> > -Gerry
> >
>
> 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.
>
I get these message on boot too (note there is not long delay to get
these messages but they do appear closer to the end of my boot up
sequence). FYI, it has not affected XEN for as far as I could see.
> 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?
>
> -Gerry
>
Mike, what processor are you running on?
-Gerry
|
