All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Marc - A. Dahlhaus" <mad@wol.de>
To: bderzhavets@yahoo.com
Cc: Jeremy Fitzhardinge <jeremy@goop.org>, xen-devel@lists.xensource.com
Subject: Re: Problems with load the most recent 2.6.29-rc6 & Xen unstable on ASUS P5K Premium
Date: Sat, 28 Feb 2009 16:11:38 +0100	[thread overview]
Message-ID: <49A9542A.1020906@wol.de> (raw)
In-Reply-To: <49A919DE.3000101@wol.de>

[-- Attachment #1: Type: text/plain, Size: 3323 bytes --]

Here we go...

Grub config used to boot:

title XEN pv_ops dom0 with serial console
root (hd0,1)
kernel /boot/xen-3.4-unstable.gz dom0_mem=256M loglvl=all 
guest_loglvl=all com1=9600,8n1 console=com1
module /boot/bzImage-2.6.29-rc6-tip ro root=LABEL=ROOT console=hvc0 
earlyprintk=xen 4
module /boot/init.rd-2.6.29-rc6-tip

Did a boot test on 3.4-unstable tip and 3.3.1 with dom0-loader-bzImage 
patch. Logs attached.

Xen and dom0 kernel are freshly pulled and build from a clean tree. 
Kernel config attached. Xen was build with this command after hg clone: 
make KERNELS='' dist

After xen hands over the console to dom0 the screen stays blank...

I'll do another tests and boot dom0 with console=ttyS0,9600n8 maybe we 
get outputs from the kernel itself then.

Marc

Marc - A. Dahlhaus schrieb:
> Hello Boris,
> hello Jeremy,
>
> i've the same problems here (but i also didn't got Dom0 up and running 
> beyond that point before on my Boxes here...).
> I'll got logs over serial console yesterday (Boris: i hope your box 
> actually have a serial port as i had to get me a cheap Asus Barebone 
> for that ;o) and watched them with the screen utility and there are 
> quite a few repeating backtraces before the whole box stops 
> responding. I'll do another run (after pulling and building Jeremys 
> remaining changes in) and catch the backtraces into log files over the 
> the next few hours to post them here.
>
> Marc
>
> Boris Derzhavets schrieb:
>> The most recent 2.6.29-rc6 with pvops Dom0 support been compiled
>> on my old box (ASUS P5K Premium)  behaves similar to situation 
>> described bellow for ASUS P5Q-E :-
>>
>> Screen output interrupts immediately after Xen prints scrubbing for free
>> ram  .  .  .  .   .   .
>> Just black screen for several second followed by Xen host reboot ( 
>> system
>> hangs on box built up on ASUS P5Q-E)
>> At mean time i have no any idea how to get boot logs.
>>
>> --- On *Fri, 2/27/09, Jeremy Fitzhardinge /<jeremy@goop.org>/* wrote:
>>
>>     From: Jeremy Fitzhardinge <jeremy@goop.org>
>>     Subject: Re: [Xen-devel] Problems with load the most recent
>>     2.6.29-rc6 & Xen unstable on ASUS P5Q-E
>>     To: bderzhavets@yahoo.com
>>     Cc: xen-devel@lists.xensource.com
>>     Date: Friday, February 27, 2009, 12:59 PM
>>
>>     Boris Derzhavets wrote:
>>     > Screen output interrupts immediately after Xen prints 
>> scrambling for free
>>     > ram  .  .  .  .   .   .
>>     > Just black screen for ever.
>>     > Novell's 2.6.27 loads fine under same Xen Unstable.
>>     > 2.6.29-rc3 ( pvops ) also loads fine under same Xen Unstable.
>>     > Box with rc4,rc5 is temporary unavailable.
>>     >
>>     >
>>
>>     Do you have any diagnostics?  Even a screenshot?
>>
>>         J
>>
>>     _______________________________________________
>>     Xen-devel mailing list
>>     Xen-devel@lists.xensource.com
>>     http://lists.xensource.com/xen-devel
>>              
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com
>> http://lists.xensource.com/xen-devel
>>   
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel


[-- Attachment #2: xen-3.4-tip.log.gz --]
[-- Type: application/x-gzip, Size: 7491 bytes --]

[-- Attachment #3: xen-3.3.1.log.gz --]
[-- Type: application/x-gzip, Size: 5009 bytes --]

[-- Attachment #4: config-2.6.29-rc6-tip.gz --]
[-- Type: application/x-gzip, Size: 24403 bytes --]

[-- Attachment #5: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

  reply	other threads:[~2009-02-28 15:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-27  0:50 Kernel build failure jonr
2009-02-27 10:55 ` Problems with load the most recent 2.6.29-rc6 & Xen unstable on ASUS P5Q-E Boris Derzhavets
2009-02-27 17:59   ` Jeremy Fitzhardinge
2009-02-28  9:09     ` Problems with load the most recent 2.6.29-rc6 & Xen unstable on ASUS P5K Premium Boris Derzhavets
2009-02-28 10:20       ` Boris Derzhavets
2009-02-28 11:02       ` Marc - A. Dahlhaus
2009-02-28 15:11         ` Marc - A. Dahlhaus [this message]
2009-03-02 17:13     ` Dmesg report for 2.6.29-rc3 & Xen unstable on ASUS P5Q-E (the only one kernel could be loaded) Boris Derzhavets
2009-02-27 12:38 ` Kernel build failure Boris Derzhavets

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=49A9542A.1020906@wol.de \
    --to=mad@wol.de \
    --cc=bderzhavets@yahoo.com \
    --cc=jeremy@goop.org \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.