170, 170.1, 171 crashed the same

using:
title Xen
         root (hd0,0)
         kernel /xen.gz loglvl=all guest_loglvl=all sync_console 
console_to_ring com2=115200,8n1 console=com2,vga lapic=debug 
apic_verbosity=debug apic=debug iommu=off
         module /vmlinuz-2.6.32.25-171.rc1.xendom0.fc12.x86_64 ro 
root=UUID=84e6a109-84c5-4288-80de-ea368a224a3a 
rd_MD_UUID=c557e3e8:d9ef50b8:b5e9861f:26975533 
rd_MD_UUID=5825fd8c:77ea8324:ae0c8804:8a0c2
487 rd_NO_LUKS rd_NO_LVM rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 
KEYTABLE=us console=hvc0 earlyprintk=xen nomodeset initcall_debug debug 
loglevel=10
         module /initramfs-2.6.32.25-171.rc1.xendom0.fc12.x86_64.img


Latest output is:
http://pastie.org/1243649

I could give you a login on the box if that would help...

Let me know if I should try other debug options/settings, thanks.


On 10/23/10 10:04 AM, M A Young wrote:
> On Sat, 23 Oct 2010, fcxen user wrote:
>
>> I am having trouble with F14, and this and the previous kernel:
>>
>> http://pastie.org/1242707
>>
>> The problem seems to start around line 687:
>> xen_balloon: Initialising balloon driver with page order 0.
>> last_pfn = 0x444690 max_arch_pfn = 0x400000000
>> BUG: unable to handle kernel paging request at ffffea000e700030
>> IP: [<ffffffff812351b7>] __list_add+0x6c/0x81
>
> Did earlier kernels work or not or didn't you try them? Also do you have a log
> from the 170.1 kernel or the newly built 171 kernel? These still have the
> debuginfo packages available which means I can get a bit more information
> about the crash.
>
> Michael Young
--
xen mailing list
xen@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/xen

Reply via email to