Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sun, 23 Dec 2001 20:05:22 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sun, 23 Dec 2001 20:05:12 -0500 Received: from sproxy.gmx.net ([213.165.64.20]:34846 "HELO mail.gmx.net") by vger.kernel.org with SMTP id ; Sun, 23 Dec 2001 20:05:00 -0500 Date: Mon, 24 Dec 2001 02:04:50 +0100 From: Christian Ohm To: Mark Hahn Cc: linux-kernel@vger.kernel.org Subject: Re: file corruption in 2.4.16/17 Message-ID: <20011224010450.GB1482@moongate.thevoid.net> In-Reply-To: <20011223025752.GA20445@moongate.thevoid.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.24i Organization: theVoid X-Operating-System: Linux moongate 2.4.17 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org > none of that is meaningful (genuine companies ship invalid cables, > and the 20 could easily have had a lower max udma mode, etc.) hmmm, i'll try a new one after christmas... the bios showed them both as 'udma 66'. > are they both on the same channel? also, when you boot, do you see > a message about the "athlon bug stomper"? (which actually corrects > a bogus kt133/etal hostbridge setting.) they are on the same channel. and i've never seen a message like this. > I can't imagine any reason to use the preemption patch, since it > completely corrupts all atomicity guarantees that the kernel has > been codd on. there definitely is no problem with large disks and > via (and 80G is certainly not a large disk any more.) well, plain 2.4.17 corrupted files, too. bye christian ohm - 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/