Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sun, 15 Dec 2002 16:44:18 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sun, 15 Dec 2002 16:44:18 -0500 Received: from mrmorr.lnk.telstra.net ([139.130.12.153]:47621 "EHLO cheesypoof.guarana.org") by vger.kernel.org with ESMTP id ; Sun, 15 Dec 2002 16:44:18 -0500 Date: Mon, 16 Dec 2002 08:52:03 +1100 From: kevin@sylandro.com To: "Justin T. Gibbs" Cc: linux-kernel@vger.kernel.org Subject: Re: 2.4.20 st + aic7xxx (Adaptec 19160B) + VIA KT333 repeatable freeze Message-ID: <20021215215203.GA29455@guarana.org> Reply-To: kevin@sylandro.com References: <1047.1039952560@ocs3.intra.ocs.com.au> <17460000.1039982505@aslan.btc.adaptec.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <17460000.1039982505@aslan.btc.adaptec.com> User-Agent: Mutt/1.3.28i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1611 Lines: 32 On Sun, Dec 15, 2002 at 01:01:45PM -0700, Justin T. Gibbs wrote: > > On Fri, 13 Dec 2002 11:51:27 +1100, > > Kevin Easton wrote: > >> I'm not sure exactly where this problem fits in, but I'm getting a > >> completely repeatable freeze (100% lockup, no response to keyboard) > >> triggered by writing to /dev/st0 (dd if=/dev/urandom of=/dev/st0 bs=512 > >> count=163840 will reproduce it). > >> So... does anyone have any ideas how I should start trying to track this > >> down? > > You might also look into your BIOS to ensure that the option "PCI Byte > Merging" is disabled. This option allows the chipset to perform illegal > byte merging on the PCI bus that will upset the Adaptec. Since the byte > merging will only occur in certain scenarios (heavily dependent on what > is going on with the SCSI bus), you may only see the lockup when accessing > a particular device or running a certain program. > > The latest versions of the aic7xxx and aic79xx drivers will automatically > detect this broken VIA behavior and will fall back to using PIO for register > access. Although I haven't generated patches against 2.4.20, you can pull > down a src tarball for 2.4.X that should just drop in: OK, will do - thanks. I don't think the BIOS on this board has such an option, so I might have to put up with PIO register access. - Kevin. - 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/