public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rambaldi <rambaldi@xs4all.nl>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: linux-kernel@vger.kernel.org, Xen-devel <xen-devel@lists.xensource.com>
Subject: Re: kernel BUG at arch/x86/xen/multicalls.c:204!
Date: Tue, 07 Jul 2009 20:24:11 +0200	[thread overview]
Message-ID: <4A5392CB.9090306@xs4all.nl> (raw)
In-Reply-To: <4A222E7C.3030504@xs4all.nl>


Rambaldi wrote:
> Jeremy Fitzhardinge wrote:
>> Rambaldi wrote:
>>> Hi,
>>>
>>> while booting the 2.6.29-gentoo-r5 kernel as xen domU guest I got the
>>> following kernel BUG.
>>>
>>> I have not tried a vanilla 2.6.29 kernel, but can if requested,
>>> .config is also available on reguest.
>>>   
>> That would be useful, particularly if you enable the various debugging
>> options:
>> CONFIG_DEBUG_KERNEL
>> CONFIG_FRAME_POINTER
>>
>> It's not clear to me what's failing.  Are there any messages on the Xen
>> concole (xm dmesg)?
>>
>>    J
>>
> Hi Jeremy,
> 
> thanks for looking at it.
> 
> I tried with a vanilla 2.6.29.4 kernel. I added CONFIG_FRAME_POINTER. CONFIG_DEBUG_KERNEL was already set.
> I got the same result as with the gentoo kernel and in both cases not a single line in the xen console.
> 
> Any other options or kernels I can try?
> 
> tia
> 
> R
> 

Hi Again,

it has been a while, but I finally found the setting that caused this issue.
by removing:
	Configure Maximum number of SMP Processors and NUMA Nodes

I can boot my sytem again without the kernel BUG.

hope this helps

regards.

R.








      reply	other threads:[~2009-07-07 18:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-30  8:45 kernel BUG at arch/x86/xen/multicalls.c:204! Rambaldi
2009-05-31  0:23 ` Jeremy Fitzhardinge
2009-05-31  7:15   ` Rambaldi
2009-07-07 18:24     ` Rambaldi [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=4A5392CB.9090306@xs4all.nl \
    --to=rambaldi@xs4all.nl \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --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