WARNING - OLD ARCHIVES

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

xen-devel

Re: [Xen-devel] reboot after "scrubbing free ram"

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] reboot after "scrubbing free ram"
From: Bastian Mäuser <mephisto@xxxxxxxxx>
Date: Wed, 09 Feb 2011 12:48:30 +0100
Delivery-date: Wed, 09 Feb 2011 03:49:05 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4D527D44.2050106@xxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <4D526976.80706@xxxxxxxxx> <1297249951.25694.6.camel@xxxxxxxxxxxxxxxxxxxxxx> <4D527D44.2050106@xxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.13) Gecko/20101208 Thunderbird/3.1.7
On 02/09/2011 12:40 PM, Bastian Mäuser wrote:
> On 02/09/2011 12:12 PM, Ian Campbell wrote:
>> On Wed, 2011-02-09 at 10:16 +0000, Bastian Mäuser wrote: 
>>> Hello,
>>>
>>> I have some diagnostic Info for you. Tried to get xen-4.0.1 working on
>>> another node of my cluster. Only difference: Newer revision of the
>>> Hardware. Exactly same Software Stack.
>>>
>>> Stack: Ubuntu Lucid 64bit, xen-4.0.1 from Source, selfbuilt
>>> linux-2.6.32.27 from xen/stable-2.6.32.x
>>>
>>> Nodes working: HP DL380G5 16GB (Intel X5460)
>>>
>>> Node not working: HP DL380G6 16GB (Intel X5550)
>>>
>>> Effect: Xen starts but dom0 Crashes immidiately after I see the message
>>> "Scrubbing free Ram". I attached Screenshot of the Management Processors
>>> Serial Port.
>>>
>>> I used the same dom0 kernel deb that successfully runs on other Nodes
>>> (as well on xen-4.0.1).
>>>
>>> Any ideas? I'm really stuck on this. I use XEN since 5+ years, but I
>>> never had that one..
>> Please can you convert the faulting RIP address to a line of code. e.g.
>> using
>> $ gdb vmlinux
>> (gdb) list *0xffff.....
> I need some more Info on that. GDB'ing the Kernel Image won't work right?
>> Please see also "Are there more debugging options I could enable to
>> troubleshoot problems with Xen and/or dom0 kernel?"
>> http://wiki.xen.org/xenwiki/XenParavirtOps for other debug options to
>> try.
> This is my Debugging:
>
>   multiboot /boot/xen-4.0.1.gz dom0_mem=1024M dummy=dummy loglvl=all
> guest_loglvl=all sync_console console_to_ring com1=115200,8n1
> console=com1 lapic=debug apic_verbosity=debug apic=debug iommu=off
>   module /boot/vmlinuz-2.6.32.27 dummy=dummy root=/dev/cciss/c0d0p1 ro
> console=hvc0 earlyprintk=xen nomodeset initcall_debug debug loglevel=10
>   module /boot/initrd.img-2.6.32.27
>

ffffffff8187da0a T xen_hvm_init_mmu_ops
ffffffff8187da4f t xen_set_pte_init
ffffffff8187dad4 t xen_pagetable_setup_done
ffffffff8187db94 T xen_build_dynamic_phys_to_machine

that's around the RIP Address..

Bastian

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