Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751215AbWAPVc5 (ORCPT ); Mon, 16 Jan 2006 16:32:57 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751217AbWAPVc5 (ORCPT ); Mon, 16 Jan 2006 16:32:57 -0500 Received: from smtp-1.smtp.ucla.edu ([169.232.46.136]:48809 "EHLO smtp-1.smtp.ucla.edu") by vger.kernel.org with ESMTP id S1751215AbWAPVc4 (ORCPT ); Mon, 16 Jan 2006 16:32:56 -0500 Date: Mon, 16 Jan 2006 13:32:50 -0800 (PST) From: Chris Stromsoe To: Roberto Nibali cc: Willy TARREAU , Alan Cox , Marcelo Tosatti , linux-kernel@vger.kernel.org Subject: Re: bad pmd filemap.c, oops; 2.4.30 and 2.4.32 In-Reply-To: <43CC079D.5060008@drugphish.ch> Message-ID: References: <43BF8785.2010703@drugphish.ch> <43C2C482.6090904@drugphish.ch> <43C2E243.5000904@drugphish.ch> <20060115224642.GA10069@w.ods.org> <43CC079D.5060008@drugphish.ch> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Probable-Spam: no X-Spam-Report: none Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1656 Lines: 40 On Mon, 16 Jan 2006, Roberto Nibali wrote: >>> Thanks for the precision. So logically we should expect it to break >>> sooner or later ? >> >> It is the same .config as one that crashed before, except that it has >> DEBUG_SLAB defined. If it does not crash, then adding pci=noacpi to >> the command fixes the problem for me. > > Hmm, I'm not fully convinced yet, however glad that it has been a bit > more stable for you. The stability only lasted for a week. Last night I got another bad pmd message, an oops, and a hang. I was not able to capture the oops. > Sidenote: We boot our systems having built-in AIC7* SCSI on moderately > cheap motherboards with "bad" interrupt routing using pci=noacpi on > 2.4.x kernels to evade instability. > > I suggest that if you experience more problems using this setup _and_ > would like to continue debugging the issue, we take this off-list into a > private discussion. At this point, I'm going to stick with 2.6. If I get more time to debug this laster, I'll drop back down to the modified 2.4 with HIGHIO disabled. > [Another thing which would be interesting to test regarding the HIGHIO > setting is a RedHat based 2.4.x kernel, since according to some SCSI > driver's documentation, RedHat had a different HIGHIO convention.] Thanks. I'll keep that on my list of things to try if I ever get back to this. I appreciate the pointers. -Chris - 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/