Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sun, 25 Feb 2001 16:57:12 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sun, 25 Feb 2001 16:57:01 -0500 Received: from [216.184.166.130] ([216.184.166.130]:55410 "EHLO scsoftware.sc-software.com") by vger.kernel.org with ESMTP id ; Sun, 25 Feb 2001 16:56:46 -0500 Date: Sun, 25 Feb 2001 13:53:51 +0000 ( ) From: John Heil To: A E Lawrence cc: Alan Cox , ian@wehrman.com, mhaque@haque.net, adilger@turbolinux.com, linux-kernel@vger.kernel.org Subject: Re: EXT2-fs error In-Reply-To: <3A99708A.679079C7@computing-services.oxford.ac.uk> 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 On Sun, 25 Feb 2001, A E Lawrence wrote: > A E Lawrence wrote: > > > > A E Lawrence wrote: > > > > > > Alan Cox wrote: > > > > > > > > > I have seen similar problems on stock 2.4.2 a machine which has not run > > > > > 2.4.1. > > > > > > > > What disk controllers ? We really need that sort of info in order to see the > > > > pattern in the odd reports of corruption we get > > > > Problems have just started to show up under 2.2.18, so it is likely that > > the hardware has become flakey. Bit of a coincidence, unless it is a > > side effect of upgrading one of the packages for 2.4.2 :-( or a damaged > > library. > > > > So you had better discount this report. Apologies. > > Now investigated: the hardware has not changed. Rather the corruption > under 2.2.18 only happens when hdparm -d1 is executed. I guess that is > well reported, but I had forgotten if I ever knew :-( > > In contrast 2.4.2 corruptions happen whether dma is explicitly turned on > by hdparm or not. > > [IDE interface: VIA Technologies, Inc. VT82C586 IDE [Apollo] (rev 10)] > The corruption I got seemed to be non-chipset related. The 2.4.1 corruption I experienced spanned 2.2.14 (RH 6.2)... The 2.4.1 IDE support was in an ALI 1535 south bridge in a Crusoe based embedded system... 00:0f.0 IDE interface: Acer Laboratories Inc. [ALi] M5229 IDE (rev c3) (prog-if b4) Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- 15uSec Fixed DTR>10Mbs } RawCHS=12416/15/63, TrkSize=36477, SectSize=579, ECCbytes=4 BuffType=3(DualPortCache), BuffSize=512kB, MaxMultSect=16, MultSect=off DblWordIO=no, OldPIO=2, DMA=yes, OldDMA=2 CurCHS=12416/15/63, CurSects=142606515, LBA=yes, LBAsects=11733120 tDMA={min:120,rec:120}, DMA modes: sword0 sword1 sword2 mword0 mword1 mword2 IORDY=yes, tPIO={min:400,w/IORDY:120}, PIO modes: mode3 mode4 UDMA modes: mode0 mode1 *mode2 mode3 mode4 When the above system couldn't adequately repair itself, I fsck'd it on the following.... 2.2.14-5.0 RH 6.2 desktop PII w PIIX4 IDE... 00:07.1 IDE interface: Intel Corporation 82371AB PIIX4 IDE (rev 01) (prog-if 80 [Master]) Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR-