linux 2.4.3 crashed my hard disk

linux 2.4.3 crashed my hard disk

[Frank Cornelis]

Hey,

After I did put in /etc/sysconfig/harddisks 
	USE_DMA=1
my system did crash very badly, I guess after my hard disks did wake up
again. For I while I though I'd lose some sectors because of this, I had
to re-install my RedHat 7.0, had a not so productive day :) But, hard
disks are OK now.
I thought I should report this.
Below there is a copy of my dmesg log.

BTW: my motherboard runs at 112 Mhz, overclocked, was 100 Mhz.
Been running this configuration over more than 2 years now without such
major problems.
Could this be the cause?

Frank.

Linux version 2.4.3 (root@bluewall) (gcc version 2.96 20000731 (Red Hat Linux 7.0)) #16 Sun Apr 1 18:24:33 CEST 2001
BIOS-provided physical RAM map:
 BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
 BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
 BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
 BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
 BIOS-e820: 0000000000100000 - 0000000007ff0000 (usable)
 BIOS-e820: 0000000007ff3000 - 0000000008000000 (ACPI data)
 BIOS-e820: 0000000007ff0000 - 0000000007ff3000 (ACPI NVS)
Scan SMP from c0000000 for 1024 bytes.
Scan SMP from c009fc00 for 1024 bytes.
Scan SMP from c00f0000 for 65536 bytes.
Scan SMP from c009fc00 for 4096 bytes.
On node 0 totalpages: 32752
zone(0): 4096 pages.
zone(1): 28656 pages.
zone(2): 0 pages.
mapped APIC to ffffe000 (01222000)
Kernel command line: auto BOOT_IMAGE=Linux ro root=303 BOOT_FILE=/boot/bzImage idebus=66
ide_setup: idebus=66
Initializing CPU#0
Detected 392.565 MHz processor.
Console: colour VGA+ 80x25
Calibrating delay loop... 783.15 BogoMIPS
Memory: 126136k/131008k available (1327k kernel code, 4484k reserved, 479k data, 240k init, 0k highmem)
Dentry-cache hash table entries: 16384 (order: 5, 131072 bytes)
Buffer-cache hash table entries: 4096 (order: 2, 16384 bytes)
Page-cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 8192 (order: 4, 65536 bytes)
VFS: Diskquotas version dquot_6.4.0 initialized
CPU: Before vendor init, caps: 0183f9ff 00000000 00000000, vendor = 0
CPU: L1 I cache: 16K, L1 D cache: 16K
CPU: L2 cache: 512K
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
CPU: After vendor init, caps: 0183f9ff 00000000 00000000 00000000
CPU: After generic, caps: 0183f9ff 00000000 00000000 00000000
CPU: Common caps: 0183f9ff 00000000 00000000 00000000
CPU: Intel Pentium II (Deschutes) stepping 01
Enabling fast FPU save and restore... done.
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
mtrr: v1.37 (20001109) Richard Gooch (rgooch@atnf.csiro.au)
mtrr: detected mtrr type: Intel
PCI: PCI BIOS revision 2.10 entry at 0xfb3b0, last bus=1
PCI: Using configuration type 1
PCI: Probing PCI hardware
Unknown bridge resource 0: assuming transparent
PCI: Using IRQ router PIIX [8086/7110] at 00:07.0
PCI: Found IRQ 10 for device 00:07.2
PCI: The same IRQ used for device 00:09.0
Limiting direct PCI/PCI transfers.
isapnp: Scanning for Pnp cards...
isapnp: No Plug & Play device found
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
IA-32 Microcode Update Driver: v1.08 <tigran@veritas.com>
apm: BIOS version 1.2 Flags 0x07 (Driver version 1.14)
Starting kswapd v1.8
parport0: PC-style at 0x378 [PCSPP(,...)]
parport0: irq 7 detected
rivafb: RIVA MTRR set to ON
Console: switching to colour frame buffer device 80x30
rivafb: PCI nVidia NV4 framebuffer ver 0.9.2a (RIVA-VTNT2, 32MB @ 0xD4000000)
pty: 256 Unix98 ptys configured
lp0: using parport0 (polling).
block: queued sectors max/low 83690kB/27896kB, 256 slots per queue
Uniform Multi-Platform E-IDE driver Revision: 6.31
ide: Assuming 66MHz system bus speed for PIO modes
PIIX4: IDE controller on PCI bus 00 dev 39
PIIX4: chipset revision 1
PIIX4: not 100% native mode: will probe irqs later
    ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:DMA, hdb:DMA
    ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:DMA, hdd:pio
hda: QUANTUM FIREBALL EX6.4A, ATA DISK drive
hdb: ST38421A, ATA DISK drive
hdc: QUANTUM FIREBALL ST2.1A, ATA DISK drive
hdd: IDE/ATAPI CD-ROM 36X, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
hda: 12594960 sectors (6449 MB) w/418KiB Cache, CHS=784/255/63, UDMA(33)
hdb: 16498944 sectors (8447 MB) w/256KiB Cache, CHS=16368/16/63, UDMA(33)
hdc: 4124736 sectors (2112 MB) w/81KiB Cache, CHS=4092/16/63, UDMA(33)
hdd: ATAPI 16X CD-ROM drive, 128kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.12
Partition check:
 hda: hda1 hda2 hda3
 hdb: hdb1 hdb2 hdb3
 hdc: [PTBL] [1023/64/63] hdc1 hdc4
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
NTFS version 000607
Serial driver version 5.05 (2000-12-13) with MANY_PORTS SHARE_IRQ SERIAL_PCI ISAPNP enabled
ttyS00 at 0x03f8 (irq = 4) is a 16550A
ttyS01 at 0x02f8 (irq = 3) is a 16550A
ne2k-pci.c:v1.02 10/19/2000 D. Becker/P. Gortmaker
  http://www.scyld.com/network/ne2k-pci.html
PCI: Found IRQ 10 for device 00:09.0
PCI: The same IRQ used for device 00:07.2
eth0: Compex RL2000 found at 0xe400, IRQ 10, 00:80:48:C4:5A:58.
PPP generic driver version 2.4.1
PPP Deflate Compression module registered
PPP BSD Compression module registered
Linux agpgart interface v0.99 (c) Jeff Hartmann
agpgart: Maximum main memory to use for agp memory: 94M
agpgart: Detected Intel 440BX chipset
agpgart: AGP aperture is 32M @ 0xd0000000
usb.c: registered new driver hub
usb-uhci.c: $Revision: 1.251 $ time 17:26:04 Apr  1 2001
usb-uhci.c: High bandwidth mode enabled
PCI: Found IRQ 10 for device 00:07.2
PCI: The same IRQ used for device 00:09.0
usb-uhci.c: USB UHCI at I/O 0xe000, IRQ 10
usb-uhci.c: Detected 2 ports
usb.c: new USB bus registered, assigned bus number 1
hub.c: USB hub found
hub.c: 2 ports detected
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 8192 bind 8192)
IPv4 over IPv4 tunneling driver
IP-Config: Incomplete network configuration information.
ip_conntrack (1023 buckets, 8184 max)
ip_tables: (c)2000 Netfilter core team
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
NET4: Linux IPX 0.46 for NET4.0
IPX Portions Copyright (c) 1995 Caldera, Inc.
IPX Portions Copyright (c) 2000, 2001 Conectiva, Inc.
VFS: Mounted root (ext2 filesystem) readonly.
Freeing unused kernel memory: 240k freed
Adding Swap: 56216k swap-space (priority -1)
hda: timeout waiting for DMA
ide_dmaproc: chipset supported ide_dma_timeout func only: 14
hda: irq timeout: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: irq timeout: error=0x40 { UncorrectableError }, LBAsect=10371801, sector=2885472
end_request: I/O error, dev 03:03 (hda), sector 2885472
hda: timeout waiting for DMA
ide_dmaproc: chipset supported ide_dma_timeout func only: 14
hda: irq timeout: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: irq timeout: error=0x40 { UncorrectableError }, LBAsect=10371801, sector=2885480
end_request: I/O error, dev 03:03 (hda), sector 2885480
hda: timeout waiting for DMA
ide_dmaproc: chipset supported ide_dma_timeout func only: 14
hda: irq timeout: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: irq timeout: error=0x40 { UncorrectableError }, LBAsect=10371801, sector=2885488
end_request: I/O error, dev 03:03 (hda), sector 2885488
hda: timeout waiting for DMA
ide_dmaproc: chipset supported ide_dma_timeout func only: 14
hda: irq timeout: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: irq timeout: error=0x40 { UncorrectableError }, LBAsect=10371801, sector=2885496
end_request: I/O error, dev 03:03 (hda), sector 2885496
hda: timeout waiting for DMA
ide_dmaproc: chipset supported ide_dma_timeout func only: 14
hda: irq timeout: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: irq timeout: error=0x40 { UncorrectableError }, LBAsect=10371801, sector=2885504
end_request: I/O error, dev 03:03 (hda), sector 2885504
hda: timeout waiting for DMA
ide_dmaproc: chipset supported ide_dma_timeout func only: 14
hda: irq timeout: status=0xd1 { Busy }
hda: DMA disabled
hdb: DMA disabled
ide0: reset: success
hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: read_intr: error=0x40 { UncorrectableError }, LBAsect=10371802, sector=2885512
end_request: I/O error, dev 03:03 (hda), sector 2885512
hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: read_intr: error=0x40 { UncorrectableError }, LBAsect=10371802, sector=2885512
end_request: I/O error, dev 03:03 (hda), sector 2885512

Re: linux 2.4.3 crashed my hard disk

[Alan Cox]

> After I did put in /etc/sysconfig/harddisks 
> 	USE_DMA=1
> my system did crash very badly, I guess after my hard disks did wake up

So you forced DMA on

> BTW: my motherboard runs at 112 Mhz, overclocked, was 100 Mhz.

and ran overclocked

> Been running this configuration over more than 2 years now without such
> major problems.
> Could this be the cause?

Quite possibly. There are reasons we ignore bug reports from overclockers

Re: linux 2.4.3 crashed my hard disk

[Brian Gerst]

Frank Cornelis wrote:
> 
> Hey,
> 
> After I did put in /etc/sysconfig/harddisks
>         USE_DMA=1
> my system did crash very badly, I guess after my hard disks did wake up
> again. For I while I though I'd lose some sectors because of this, I had
> to re-install my RedHat 7.0, had a not so productive day :) But, hard
> disks are OK now.
> I thought I should report this.
> Below there is a copy of my dmesg log.
> 
> BTW: my motherboard runs at 112 Mhz, overclocked, was 100 Mhz.
> Been running this configuration over more than 2 years now without such
> major problems.
> Could this be the cause?
> 
> Frank.

http://www.tux.org/lkml/#s13-3

--

				Brian Gerst

Re: linux 2.4.3 crashed my hard disk

[Richard B. Johnson]

On Wed, 4 Apr 2001, Frank Cornelis wrote:

> Hey,
> 
> After I did put in /etc/sysconfig/harddisks 
> 	USE_DMA=1
> my system did crash very badly, I guess after my hard disks did wake up
[SNIPPED...]


> 
> BTW: my motherboard runs at 112 Mhz, overclocked, was 100 Mhz.
> Been running this configuration over more than 2 years now without such
> major problems.
> Could this be the cause?
> 
> Frank.

Please don't ever report any errors to linux-kernel if you are running
your machine over-clocked. All you need is to fetch ONE bad instruction
and you can evaporate ALL the data on ALL your hard disks. Think what
happens if a pointer to a structure containing the not-yet-written
to disk blocks gets adjusted to point so some spent email buffer.


Cheers,
Dick Johnson

Penguin : Linux version 2.4.1 on an i686 machine (799.53 BogoMips).

"Memory is like gasoline. You use it up when you are running. Of
course you get it all back when you reboot..."; Actual explanation
obtained from the Micro$oft help desk.

Re: linux 2.4.3 crashed my hard disk

[Ion Badulescu]

On Wed, 4 Apr 2001 20:00:29 +0100 (BST), Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:

>> Been running this configuration over more than 2 years now without such
>> major problems.
>> Could this be the cause?
> 
> Quite possibly. There are reasons we ignore bug reports from overclockers

Perhaps. But,

ide_dmaproc: chipset supported ide_dma_timeout func only: 14

is about the most ominous message one can receive from the IDE driver:

1. it's not in English, so it doesn't tell you jack
2. it's usually a sign of "mkfs + reinstall needed"
3. I've had it happen on Intel and VIA chipsets alike, 100% guaranteed
   non-overclocked
4. Andre has repeatedly claimed "he's fixed it", but experience in the
   field shows quite the contrary to be true
5. I have yet to see a coherent explanation from Andre as to what the
   message means, or what causes it.

So right now 2.4 + IDE (or 2.2 + IDE + Andre's patches) is not a combination 
I can trust my data to, unless everything is running in PIO mode. The latter
is usually way too slow for anything useful, other than maybe a pure router.

Ion

-- 
  It is better to keep your mouth shut and be thought a fool,
            than to open it and remove all doubt.

Re: linux 2.4.3 crashed my hard disk

[Alan Cox]

> ide_dmaproc: chipset supported ide_dma_timeout func only: 14
> is about the most ominous message one can receive from the IDE driver:
> 
> 1. it's not in English, so it doesn't tell you jack

It tells you the chipset doesnt support an IDE dma timeout handling function
(ie all it can do is reset and retry)

> 2. it's usually a sign of "mkfs + reinstall needed"

Not in my experience. Its just a drive throwing a fit.

> 3. I've had it happen on Intel and VIA chipsets alike, 100% guaranteed
>    non-overclocked

I've only seen it on broken boards that also needed DMA off in 2.2 and
on the VIA stuff before the VIA fixups went in and the new via driver.

> 5. I have yet to see a coherent explanation from Andre as to what the
>    message means, or what causes it.


We issued a DMA, the drive sat their and did nothing. The default handler 
asks the controller handling the request to retry it in PIO mode. Which is
readonable. On the 440BX this uses disable_irq which may also trigger a bug
in the APIC on SMP machines and hang solid unless you have -ac. I dont think
thats statistically likely here.

The code looks correct, its a bit convoluted but it does seem to correctly
reissue the request, although not as PIO. Perhaps Andre can explain why its
ignoring the 'please use pio' hint on the return

Alan

Re: linux 2.4.3 crashed my hard disk

[Alessandro Suardi]

-- 
--alessandro      <alessandro.suardi@oracle.com> <asuardi@uninetcom.it>

Linux:  kernel 2.2.19/2.4.3p8 glibc-2.2 gcc-2.96-69 binutils-2.11.90.0.1
Oracle: Oracle8i 8.1.7.0.1 Enterprise Edition for Linux
motto:  Tell the truth, there's less to remember.

Re: linux 2.4.3 crashed my hard disk

[Alessandro Suardi]

Sorry for the null message, fingers slipped :(

Alan Cox wrote:
> 
> > ide_dmaproc: chipset supported ide_dma_timeout func only: 14
> > is about the most ominous message one can receive from the IDE driver:
> >
> > 1. it's not in English, so it doesn't tell you jack
> 
> It tells you the chipset doesnt support an IDE dma timeout handling function
> (ie all it can do is reset and retry)
> 
> > 2. it's usually a sign of "mkfs + reinstall needed"
> 
> Not in my experience. Its just a drive throwing a fit.
> 

Indeed, I hit this regularly on my Samsung CD-ROM on my Dell laptop.

Everything locks up for a few seconds, then the ATAPI reset kicks
 in and all works again. The CD drive is a piece of crud.

--alessandro      <alessandro.suardi@oracle.com> <asuardi@uninetcom.it>

Linux:  kernel 2.2.19/2.4.3p8 glibc-2.2 gcc-2.96-69 binutils-2.11.90.0.1
Oracle: Oracle8i 8.1.7.0.1 Enterprise Edition for Linux
motto:  Tell the truth, there's less to remember.

Re: linux 2.4.3 crashed my hard disk

[Andre Hedrick]

You killed yourself....

You do not have a host that will do idebus=66
You have now dived you clock timing in half.
You should expect to have a driver time out before the device is
completed.

-- 
Andre Hedrick
Linux ATA Development
ASL Kernel Development
-----------------------------------------------------------------------------
ASL, Inc.                                     Toll free: 1-877-ASL-3535
1757 Houret Court                             Fax: 1-408-941-2071
Milpitas, CA 95035                            Web: www.aslab.com

Re: linux 2.4.3 crashed my hard disk

[Ion Badulescu]

On Fri, 06 Apr 2001 21:30:24 -0700, Andre Hedrick <andre@linux-ide.org> wrote:
> 
> You killed yourself....
> 
> You do not have a host that will do idebus=66

You really ought to rename this parameter to pcibus. Even though it doesn't
do justice to the VLB bus, the potential for user error is much smaller.

Ion

-- 
  It is better to keep your mouth shut and be thought a fool,
            than to open it and remove all doubt.

Re: linux 2.4.3 crashed my hard disk

[Andre Hedrick]

On Fri, 6 Apr 2001, Ion Badulescu wrote:

> On Fri, 06 Apr 2001 21:30:24 -0700, Andre Hedrick <andre@linux-ide.org> wrote:
> > 
> > You killed yourself....
> > 
> > You do not have a host that will do idebus=66
> 
> You really ought to rename this parameter to pcibus. Even though it doesn't
> do justice to the VLB bus, the potential for user error is much smaller.

Until today you had a vaild point!

Promise Ultra100TX2 (20268 chipset).

This is a 66MHz clocked Ultra100 Chipset release this week.


Andre Hedrick
Linux ATA Development
ASL Kernel Development
-----------------------------------------------------------------------------
ASL, Inc.                                     Toll free: 1-877-ASL-3535
1757 Houret Court                             Fax: 1-408-941-2071
Milpitas, CA 95035                            Web: www.aslab.com

Re: linux 2.4.3 crashed my hard disk

[Ion Badulescu]

On Fri, 6 Apr 2001, Andre Hedrick wrote:

> > You really ought to rename this parameter to pcibus. Even though it doesn't
> > do justice to the VLB bus, the potential for user error is much smaller.
> 
> Until today you had a vaild point!
> 
> Promise Ultra100TX2 (20268 chipset).
> 
> This is a 66MHz clocked Ultra100 Chipset release this week.

Ok... but how does this invalidate my point? The 66MHz still applies to 
the PCI bus, so pcibus is ok for the parameter name, no?

Ion

-- 
  It is better to keep your mouth shut and be thought a fool,
            than to open it and remove all doubt.

Re: linux 2.4.3 crashed my hard disk

[Andre Hedrick]

On Fri, 6 Apr 2001, Ion Badulescu wrote:

> On Fri, 6 Apr 2001, Andre Hedrick wrote:
> 
> > > You really ought to rename this parameter to pcibus. Even though it doesn't
> > > do justice to the VLB bus, the potential for user error is much smaller.
> > 
> > Until today you had a vaild point!
> > 
> > Promise Ultra100TX2 (20268 chipset).
> > 
> > This is a 66MHz clocked Ultra100 Chipset release this week.
> 
> Ok... but how does this invalidate my point? The 66MHz still applies to 
> the PCI bus, so pcibus is ok for the parameter name, no?

Because this card is designed to run in a 66MHz pcibus or standard 33MHz
pcibus, but the idebus/bridge is clocked at double pump or 1:1 depending
on the busses 64-bit/66MHz, 64-bit/33MHz, or 32-bit/33MHz

This is were it gets messy........so I do not have an answer that I valid
at this point, however I do know that 66MHz clocking is about to become
standard...

Cheers,

Andre Hedrick
Linux ATA Development
ASL Kernel Development
-----------------------------------------------------------------------------
ASL, Inc.                                     Toll free: 1-877-ASL-3535
1757 Houret Court                             Fax: 1-408-941-2071
Milpitas, CA 95035                            Web: www.aslab.com