Date: Tue, 13 Jan 2004 11:16:39 -0800
From: Andrew Morton <akpm@osdl.org>
To: "Prakash K. Cheemplavam" <PrakashKC@gmx.de>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: 2.6.1-mm2
Message-Id: <20040113111639.60b681d2.akpm@osdl.org>
In-Reply-To: <400441BD.9020609@gmx.de>
References: <20040110014542.2acdb968.akpm@osdl.org>
	<4003F34E.5080508@gmx.de>
	<20040113095428.440762f7.akpm@osdl.org>
	<400441BD.9020609@gmx.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1266
Lines: 28

"Prakash K. Cheemplavam" <PrakashKC@gmx.de> wrote:
>
> >>kernel: Badness in pci_find_subsys at drivers/pci/search.c:132
> >>
> >>Any ideas? Or do you need detailed kernel config and dmesg? I thought 
> >>you might have an idea which atch caused this... My and his system are 
> >>quite differnt. Major Common element seems only use of Athlon XP. He has 
> >>VIA KT based system and I have nforce2. I thought it might be APIC, but 
> >>I also got a lock up without APIC. (Though it seems more stable without 
> >>APIC.)
> > 
> > 
> > If you could send us the stack backtrace that would help.  Make sure that
> > you have CONFIG_KALLSYMS enabled.  If you have to type it by hand, just the
> > symbol names will suffice - leave out the hex numbers.
> 
> Sorry, I am a noob about such things. Above option is enabled in my 
> config, but I dunno how get the stack backtrace. Could you point to me 
> to something helpful?

When the kernel prints that `badness' message it then prints a stack
backtrace.  That's what we want.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/