Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932128AbVLaKjp (ORCPT ); Sat, 31 Dec 2005 05:39:45 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932130AbVLaKjp (ORCPT ); Sat, 31 Dec 2005 05:39:45 -0500 Received: from smtp-6.smtp.ucla.edu ([169.232.48.138]:30686 "EHLO smtp-6.smtp.ucla.edu") by vger.kernel.org with ESMTP id S932128AbVLaKjp (ORCPT ); Sat, 31 Dec 2005 05:39:45 -0500 Date: Sat, 31 Dec 2005 02:39:43 -0800 (PST) From: Chris Stromsoe To: Willy Tarreau cc: Marcelo Tosatti , linux-kernel@vger.kernel.org Subject: Re: bad pmd filemap.c, oops; 2.4.30 and 2.4.32 In-Reply-To: <20051231071215.GX15993@alpha.home.local> Message-ID: References: <20051228001047.GA3607@dmt.cnet> <20051231071215.GX15993@alpha.home.local> 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: 1550 Lines: 37 On Sat, 31 Dec 2005, Willy Tarreau wrote: > On Fri, Dec 30, 2005 at 05:48:15PM -0800, Chris Stromsoe wrote: > >> I'm starting to suspect bad hardware. Booting is now hanging (with >> 2.4.27, 2.4.30 and 2.4.32) after scsi drivers load: > > And nothing changed since previous boot, except UP ? All I changed was adding nosmp to the kernel boot line. > It's not necessarily bad hardware. I also had trouble on one version of > the 29160 bios where it hanged during device scan if there were too many > terminations. Oh, BTW, please check that you have disabled "automatic" > termination in the BIOS. Manually set it either to ON or OFF (low/high > depending on your setup). I'll have to check it tomorrow or on Monday. >> How likely is it that a failing scsi controller contribute to the other >> problems I was seeing? > > Not much. Perhaps at worst, a failing controller could corrupt memory by > writing garbage at wrong locations, but you would not always get the > same messages. It seems to be a different problem here. To be honnest, > it's where I think you should try the new driver. The machine has been running 2.6.14.4 for the last 6 hours. It came up fine. I did not try booting it with nosmp. If I have time, I will revert back to 2.4 with the newer driver to test. -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/