ide.2.4.1-p3.01112001.patch

In-Reply-To: <[email protected]>
In article <[email protected]>, [email protected]

...

It's not an Abit KT7 or similar is it?
I was just helping my dad upgrade a machine based with one of those to 2.4 today and until we turned off Generic PCI bus-master DMA Support and the VIA82CXXX drivers we kept getting the same messages the second the system booted up.
It was rather annoying, as I'm not sure if it was because of this or something else, but we ended up with some minor disk corruption mainly around /usr/src/linux where I made the mistake of doing a make mrproper while it was like this. Went back to 2.2 temporarily and it was fine. Can dig out/try anything on request.

TonyP
[email protected]

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/

Good! I'm not the only ome getting this error! Mine is also a VT82C686 though mine is a VT82C686A (352 BGA). This is on an MSI Model 694D Pro motherboard running dual PIII-733 FC-PGA 133MHz Coppermines. RAM is 4 256MB PC133 unbuffered 7ns non mixed-cell DIMMs. I bring up the RAM and CPU info because this board is also giving me random SIG11 errors even though all equipment passes lab testing.

I was beginning to think the board was flaky until i saw this posting. Almost exactly matche smy errors. Also, since I'm using the Promise PDC20265 (rev 2) ATA33/66 + 100 controller on the mobo, I wasn't sure if my errors were stemming from that. The 2.4.0 kernel driver picks up the controller fine and it's only under heavy I/O (aka dd if=/dev/hdc of=/root/testdd.img bs=1024M count=2k ) that it REALLY goes nuts and drops loses it's lunch all over the floor. Accessing a standard 48X CDROM in the same manner doesn't kill the kernel but I get quite a few DriveReady errors like you got. I'm wondering if this is just a flaky chipset or if this is a Promise controller issue. This is one reason i'm extremely interested in what controller you have on your board, and if you are using it.

I also had to remove the USB support totally since it would stream errors at me about usb devices not accepting new addresses.
Funny thing is, I don't have any USB devices attached to the machine! Thought address assignments were only when you attached devices.

Anyone else out there with troubles with either of these 3 items?

David D.W. Downey

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/

I feel it important to note that the distrib in use for all of this is of my own design. The specs are at www.kixolinux.com.

Why do I feel this is important? Possibly something I've done in the distrib could be affecting this as well. I remember reading some weeks ago about the 2.4.0-test## series + SCSI + SMP were having some problems.

The drives are as follows

    ide0: BM-DMA at 0xb000-0xb007, BIOS settings: hda:DMA, hdb:DMA

hda: WDC WD153AA, ATA DISK drive
hda: 30064608 sectors (15393 MB) w/2048KiB Cache, CHS=1871/255/63, UDMA(66)

    ide0: BM-DMA at 0xb000-0xb007, BIOS settings: hda:DMA, hdb:DMA

hdb: WDC WD300BB-00AUA1, ATA DISK drive
hdb: 58633344 sectors (30020 MB) w/2048KiB Cache, CHS=3649/255/63, UDMA(66)

    ide1: BM-DMA at 0xb008-0xb00f, BIOS settings: hdc:DMA, hdd:pio

hdc: SAMSUNG CD-ROM SC-148F, ATAPI CDROM drive
hdc: ATAPI 48X CD-ROM drive, 128kB Cache, DMA

The errors are as follows

hdc: timeout waiting for DMA
hdc: irq timeout: status=0xd0 { Busy }
hdc: DMA disabled
hdc: ATAPI reset complete
hdc: command error: status=0x51 { DriveReady SeekComplete Error }
hdc: command error: error=0x54
end_request: I/O error, dev 16:00 (hdc), sector 929520
hdc: irq timeout: status=0xd0 { Busy }
hdc: ATAPI reset complete
hdc: command error: status=0x51 { DriveReady SeekComplete Error }
hdc: command error: error=0x54
end_request: I/O error, dev 16:00 (hdc), sector 929522

I get the same thing for hda and hdb though not as frequently as with hdc. (Controller doesn't like switchign between DMA and PIO modes possibly? ::shrug::)

David D.W. Downey

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/

I've got two 694D Pro's (the AIR variant) and at the moment I'm not especially happy with them - whether it's Linux, the boards or a combination of both I don't know. Problems so far have been

- With disks on the Promise controller I have to disable the M/B sound or Linux (everything from 2.2.14(RH 6.2) up to 2.4.0-ac4) hangs when probing the IDE interfaces. The sound shares the PCI IRO line with the Promise.

With no disks on the Promise I can leave the sound enabled

- I get the same CRC errors when I move the disks (Maxtor 33073H3's) to the VIA interfaces (ATA/66).

- 2.4.0-ac8 gives errors on /dev/md1 (S/W RAID-1 pair) on boot (and then panics as /dev/md1 is the root fs), 2.2.x is happy with the mirror. I'm not sure whether this is a 2.4.0 problem, one introduced by Alan or hardware because I'm lucky to get a kernel compile without the thing OOPSing on me.

My set-up is similar to David's except that I have 2x866 PIII FC-PGAs, If I can figure out whether some of the problems are hardware (we have 4 of these boards two were to have Linux, one one of the BSDs and one W2k so we should be able to spot problems that are common to all the OSes) I'll send some better bug reports.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/