All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Bastian Mäuser" <mephisto@mephis.to>
To: xen-devel@lists.xensource.com
Subject: Re: reboot after "scrubbing free ram"
Date: Wed, 09 Feb 2011 12:48:30 +0100	[thread overview]
Message-ID: <4D527F0E.9000802@mephis.to> (raw)
In-Reply-To: <4D527D44.2050106@mephis.to>

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

  reply	other threads:[~2011-02-09 11:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-09 10:16 reboot after "scrubbing free ram" Bastian Mäuser
2011-02-09 11:12 ` Ian Campbell
2011-02-09 11:40   ` Bastian Mäuser
2011-02-09 11:48     ` Bastian Mäuser [this message]
2011-02-09 11:50     ` Ian Campbell
2011-02-09 12:51       ` Bastian Mäuser
2011-02-09 14:43         ` Stefano Stabellini
2011-02-09 14:49           ` [SPAM] " Stefano Stabellini
2011-02-09 15:36             ` Bastian Mäuser

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=4D527F0E.9000802@mephis.to \
    --to=mephisto@mephis.to \
    --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.