Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S264265AbUAMNb7 (ORCPT ); Tue, 13 Jan 2004 08:31:59 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S264285AbUAMNb7 (ORCPT ); Tue, 13 Jan 2004 08:31:59 -0500 Received: from pop.gmx.net ([213.165.64.20]:37815 "HELO mail.gmx.net") by vger.kernel.org with SMTP id S264265AbUAMNb6 (ORCPT ); Tue, 13 Jan 2004 08:31:58 -0500 X-Authenticated: #4512188 Message-ID: <4003F34E.5080508@gmx.de> Date: Tue, 13 Jan 2004 14:31:58 +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> In-Reply-To: <20040110014542.2acdb968.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 Content-Length: 874 Lines: 23 Hi, mm2 (or even mm1 or even vanilla, have not tested (long enough)) locks hard on my and someone else' machine. Sometimes we get this line in our logs before the lock happens: 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.) bye, Prakash - 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/