xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Fantu <fantonifabio@tiscali.it>
To: xen-devel@lists.xensource.com
Subject: Re: Detail on 2.6.32.11 pv_ops not boot
Date: Thu, 22 Apr 2010 22:56:20 -0700 (PDT)	[thread overview]
Message-ID: <28337511.post@talk.nabble.com> (raw)
In-Reply-To: <4BD0D6DC.5020502@goop.org>


With all active stop on serial, with serial disable on bios stop on ata on
motherboard, if disable also that stop on usb ecc, can you merge last fix
about irq and msi from xen/next to xen/stable2.6.32.x for try if solve or
there is other problem?
Similar problem with boot of xen/stable compiled on 1 march i have solved
with  CONFIG_SPARSE_IRQ=n and apply patch
0001-x86-ioapic-Remove-the-hack-for-calculating-nr_irq_
Now not patch apply and for config see the first post on this topic

Jeremy Fitzhardinge wrote:
> 
> On 04/22/2010 03:17 AM, Fantu wrote:
>> Here the full output of SOL with full debug option: 
>> http://old.nabble.com/file/p28326903/xenboot-sol.log xenboot-sol.log 
>>   
> 
> Thanks for that.  Does it always hang at the same place?  Your
> screenshot shows it apparently hanging at ata_piix, whereas the sol log
> shows a hang near serial setup (which doesn't seem to overlap with the
> screenshot at all).
> 
> What does booting the same kernel natively show?
> 
> Thanks,
>     J
> 
>>
>> Fantu wrote:
>>   
>>> S.O. is Lenny 64 bit
>>> Dom0 is xen 4 from hg-testing4.0
>>> Kernel is 2.6.32.11 pv_ops update with this config: 
>>> http://old.nabble.com/file/p28287956/.config .config 
>>> Server is Dell T610 with bios 2.0.13
>>>
>>> I have start with all debug option found:
>>> menuentry "Xen 4 hg-4.0-testing, linux 2.6.32.11 DEBUG" {
>>> 	set root=(hd0,1)
>>> 	multiboot /boot/xen-4.gz dom0_mem=1024M loglvl=all guest_loglvl=all
>>> lapic=debug apic_verbosity=debug apic=debug iommu=off
>>> 	module /boot/vmlinuz-2.6.32.11 root=LABEL=root-raid ro nomodeset
>>> earlyprintk=xen nomodeset initcall_debug debug loglevel=10
>>> 	module /boot/initrd.img-2.6.32.11
>>> }
>>>
>>> The result is block here: 
>>> http://old.nabble.com/file/p28287956/2.6.32.11_pv_ops_screen.jpg
>>> 2.6.32.11_pv_ops_screen.jpg 
>>>
>>> Thanks in advantages for any help
>>>
>>>     
>>   
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
> 
> 

-- 
View this message in context: http://old.nabble.com/Detail-on-2.6.32.11-pv_ops-not-boot-tp28287956p28337511.html
Sent from the Xen - Dev mailing list archive at Nabble.com.

      reply	other threads:[~2010-04-23  5:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-21  6:52 Detail on 2.6.32.11 pv_ops not boot Fantu
2010-04-22 10:17 ` Fantu
2010-04-22 23:08   ` Jeremy Fitzhardinge
2010-04-23  5:56     ` Fantu [this message]

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=28337511.post@talk.nabble.com \
    --to=fantonifabio@tiscali.it \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).