kdb
[Top] [All Lists]

Re: Fw: Trouble with i386 KDB current and 2.6.7

To: keith <kmannth@xxxxxxxxxx>
Subject: Re: Fw: Trouble with i386 KDB current and 2.6.7
From: Kevin Stansell <stanselk@xxxxxxxxxx>
Date: Wed, 23 Jun 2004 13:51:32 -0400
Cc: kdb@xxxxxxxxxxx
In-reply-to: <1088008061.19474.281.camel@knk>
References: <OF826468A0.EA4881CD-ON85256EBC.0045CC35-85256EBC.0045F406@xxxxxxxxxx> <40D97BCB.8020800@xxxxxxxxxx> <1088008061.19474.281.camel@knk>
Sender: kdb-bounce@xxxxxxxxxxx
User-agent: Mozilla Thunderbird 0.6 (Windows/20040502)
keith wrote:

> On Wed, 2004-06-23 at 05:47, Kevin Stansell wrote:
> 
>>>On Tue, 2004-06-22 at 15:39, Keith Owens wrote:
>>> > On Tue, 22 Jun 2004 14:54:43 -0700,
>>> > keith <kmannth@xxxxxxxxxx> wrote:
>>> > >linux 2.6.7-bk4
>>> > >kdb-v4.4-2.6.7-common-1
>>> > >kdb-v4.4-2.6.7-i386-1
>>> > >
>>> > >My issue is as follows...
>>> > >  If I don't enable kdb everything works fine.  When I enable and boot
>>> > >with KDB I fall into kdb when I bring the secondary cpus online.  KDB
>>> > >claims it was entered via an NMI.  Without kdb there are no nmis being
>>> > >registered by the system.  
>>> >
>>> > This debug patch should get you up and running, and tell you where the
>>> > nmi is coming from.  Untested.
>>>
>>>Ok booted without kdb and I did not see that zone alignment error.  Has
>>>kdb ran on a numa i386 system before?  It looks to be tinkering with the
>>>VM somehow. Tomorrow I'll try disabling numa and seeing if things work.
>>
>>As a datapoint: I have ran KDB (with the 2.4 kernel) on a summit box in 
>>the past with no problems.
>>
> 
> 
> Do you know if the CONFIG_NUMA options were set?  
> 
> Keith 
> 
> 

Yes, with SLES8 the CONFIG_X86_NUMA option is set along with 
CONFIG_X86_SUMMIT.

-- 
Sincerely,

Kevin Stansell
IBM Software Engineer
stanselk@xxxxxxxxxx (linux)
kstansel@xxxxxxxxxx (notes)
---------------------------
Use http://oss.sgi.com/ecartis to modify your settings or to unsubscribe.
<Prev in Thread] Current Thread [Next in Thread>