Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 12 Nov 2001 16:48:33 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 12 Nov 2001 16:48:24 -0500 Received: from gw.lowendale.com.au ([203.26.242.120]:61800 "EHLO marina.lowendale.com.au") by vger.kernel.org with ESMTP id ; Mon, 12 Nov 2001 16:48:07 -0500 Date: Tue, 13 Nov 2001 08:59:04 +1100 (EST) From: Neale Banks To: Alan Cox cc: Jeronimo Pellegrini , Nils Philippsen , vojtech@suse.cz, linux-kernel@vger.kernel.org Subject: Re: [PATCH] VIA timer fix was removed? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org > > Attached (untested) patch against 21.2.20 (which still has the $SUBJECT > > code) should implement timer=no-via686a option to disable this. Hopefully > > I'll get it tested in the next day or two. Oops, my typo: s/21.2.20/2.2.20/ On Mon, 12 Nov 2001, Alan Cox wrote: > This isnt the real problem - we are seeing it triggered by cases we dont > underatand that seem to be software. We need to find those Fair enough (and I make no pretence to knowing where to start to address the real problem here). Meanwhile, for those of us that have either suspected or confirmed problems with the VIA686a workaround ( possibly due to entirely different hardware/BIOS bugs? ), a method of nobbling the VIA686a fix at compile or boot time could be somewhat useful? Mmm... boot-time is probably best as it allows easiet experimentation? Thanks, Neale. - 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/