From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?UTF-8?B?QmFzdGlhbiBNw6R1c2Vy?= Subject: Re: reboot after "scrubbing free ram" Date: Wed, 09 Feb 2011 12:40:52 +0100 Message-ID: <4D527D44.2050106@mephis.to> References: <4D526976.80706@mephis.to> <1297249951.25694.6.camel@zakaz.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <1297249951.25694.6.camel@zakaz.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Ian Campbell Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org On 02/09/2011 12:12 PM, Ian Campbell wrote: > On Wed, 2011-02-09 at 10:16 +0000, Bastian M=C3=A4user wrote:=20 >> 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 messag= e >> "Scrubbing free Ram". I attached Screenshot of the Management Processo= rs >> 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=3D1024M dummy=3Ddummy loglvl=3Dal= l guest_loglvl=3Dall sync_console console_to_ring com1=3D115200,8n1 console=3Dcom1 lapic=3Ddebug apic_verbosity=3Ddebug apic=3Ddebug iommu=3D= off module /boot/vmlinuz-2.6.32.27 dummy=3Ddummy root=3D/dev/cciss/c0d0p1 r= o console=3Dhvc0 earlyprintk=3Dxen nomodeset initcall_debug debug loglevel=3D= 10 module /boot/initrd.img-2.6.32.27 > Limiting the amount of memory given to dom0 (using the dom0_mem > hypervisor option) would be interesting in case this is the same issue > as Debian bug #606964. As you can see i always allocate 1gb to dom0.. Bastian