From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S265114AbUAMTW4 (ORCPT ); Tue, 13 Jan 2004 14:22:56 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S265118AbUAMTW4 (ORCPT ); Tue, 13 Jan 2004 14:22:56 -0500 Received: from imap.gmx.net ([213.165.64.20]:23221 "HELO mail.gmx.net") by vger.kernel.org with SMTP id S265114AbUAMTWy (ORCPT ); Tue, 13 Jan 2004 14:22:54 -0500 X-Authenticated: #4512188 Message-ID: <4004458C.5040000@gmx.de> Date: Tue, 13 Jan 2004 20:22:52 +0100 From: "Prakash K. Cheemplavam" User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6b) Gecko/20031208 Thunderbird/0.4 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Andrew Morton CC: linux-kernel@vger.kernel.org, linux-mm@kvack.org Subject: Re: 2.6.1-mm2 References: <20040110014542.2acdb968.akpm@osdl.org> <4003F34E.5080508@gmx.de> <20040113095428.440762f7.akpm@osdl.org> <400441BD.9020609@gmx.de> <20040113111639.60b681d2.akpm@osdl.org> In-Reply-To: <20040113111639.60b681d2.akpm@osdl.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Andrew Morton wrote: > "Prakash K. Cheemplavam" 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. But how to get that? When the machine locks up, I don't see anything written and only *sometimes* I got above message in the log -whcih I can only see afterwards. But there is nothing else realted to it in the log... Prakash From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <4004458C.5040000@gmx.de> Date: Tue, 13 Jan 2004 20:22:52 +0100 From: "Prakash K. Cheemplavam" MIME-Version: 1.0 Subject: Re: 2.6.1-mm2 References: <20040110014542.2acdb968.akpm@osdl.org> <4003F34E.5080508@gmx.de> <20040113095428.440762f7.akpm@osdl.org> <400441BD.9020609@gmx.de> <20040113111639.60b681d2.akpm@osdl.org> In-Reply-To: <20040113111639.60b681d2.akpm@osdl.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org Return-Path: To: Andrew Morton Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org List-ID: Andrew Morton wrote: > "Prakash K. Cheemplavam" 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. But how to get that? When the machine locks up, I don't see anything written and only *sometimes* I got above message in the log -whcih I can only see afterwards. But there is nothing else realted to it in the log... Prakash -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: aart@kvack.org