VIA/PDC/Athlon
I tested 2.4.4-ac9 today on A7V133 machine. It booted up, but can't stand any load. It will deadlock (without oops) when the network/disk system faces any load.
There is also some new bug in VIA IDE driver. It misdetects cable as 80-w when it's only 40-w and causes some CRC errors and speed dropping. Some older kernels correctly detected the cable as 40-w and used UDMA33, this one tries to use UDMA100 and fails (of course). Is there any way to force cable detection to 40-w?
- Jussi Laako
Signature · 2 lines
PGP key fingerprint: 161D 6FED 6A92 39E2 EB5B 39DD A4DE 63EB C216 1E4B Available at PGP keyservers
Quoted 9 lines · Jussi Laako
I tested 2.4.4-ac9 today on A7V133 machine. It booted up, but can't stand any load. It will deadlock (without oops) when the network/disk system faces any load.
There is also some new bug in VIA IDE driver. It misdetects cable as 80-w when it's only 40-w and causes some CRC errors and speed dropping. Some older kernels correctly detected the cable as 40-w and used UDMA33, this one tries to use UDMA100 and fails (of course). Is there any way to force cable detection to 40-w?
There were no changes lately in the VIA driver. Can you spot where the problems begun?
Signature · 2 lines
Vojtech Pavlik SuSE Labs
Quoted 3 lines
I tested 2.4.4-ac9 today on A7V133 machine. It booted up, but can't stand any load. It will deadlock (without oops) when the network/disk system faces any load.
Let me guess 'ide=nodma' fixes that ?
Quoted 2 lines
There is also some new bug in VIA IDE driver. It misdetects cable as 80-w when it's only 40-w and causes some CRC errors and speed dropping. Some
Since when - the VIA driver in -ac has not changed for a very long time
Quoted 3 lines
older kernels correctly detected the cable as 40-w and used UDMA33, this one tries to use UDMA100 and fails (of course). Is there any way to force cable detection to 40-w?
it shouldnt ever misdetect - thats a bug.
Quoted 4 lines · Jussi Laako
I tested 2.4.4-ac9 today on A7V133 machine. It booted up, but can't stand any load. It will deadlock (without oops) when the network/disk system faces any load.
reset/clear CMOS with jumper. I get this kind of instability each time I have to boot to win9x (with latest and greatest via drivers) and back to linux. Just of sudden linux freezes or if I have apcid running sometimes it oops' on boot sometimes later ... lots of defunc kacpid ... threads.
looks like VIA drivers do something to hardware (or maybe only ACPI part of hardware ... I don't know.) and linux can't handle hardware is this new "after win9x" state ...
reset/clear CMOS with jumper helped.
MB ABit KT7A-RAID
00:00.0 Host bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133] (rev 03) 00:01.0 PCI bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133 AGP] 00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 40)
VT82C686b actually :)
00:07.1 IDE interface: VIA Technologies, Inc. Bus Master IDE (rev 06) 00:07.2 USB Controller: VIA Technologies, Inc. UHCI USB (rev 16) 00:07.3 USB Controller: VIA Technologies, Inc. UHCI USB (rev 16) 00:07.4 Host bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 40) 00:08.0 Ethernet controller: Bridgecom, Inc: Unknown device 0985 (rev 11) 00:0f.0 Multimedia audio controller: Creative Labs SB Live! EMU10000 (rev 07) 00:0f.1 Input device controller: Creative Labs SB Live! (rev 07) 01:00.0 VGA compatible controller: ATI Technologies Inc: Unknown device 5144
Quoted 11 lines
- Jussi Laako
Signature · 7 lines
PGP key fingerprint: 161D 6FED 6A92 39E2 EB5B 39DD A4DE 63EB C216 1E4B Available at PGP keyservers - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Signature · 1 line
Zilvinas Valinskas
Quoted 5 lines · Vojtech Pavlik
Quoted 3 lines
There is also some new bug in VIA IDE driver. It misdetects cable as 80-w when it's only 40-w and causes some CRC errors and speed dropping.
There were no changes lately in the VIA driver. Can you spot where the problems begun?
RH 2.4.2-2 works correctly, but 2.4.4-ac9 doesn't. I think 2.4.3 didn't work.
- Jussi Laako
Signature · 2 lines
PGP key fingerprint: 161D 6FED 6A92 39E2 EB5B 39DD A4DE 63EB C216 1E4B Available at PGP keyservers
Quoted 5 lines
Quoted 2 lines
There were no changes lately in the VIA driver. Can you spot where the problems begun?
RH 2.4.2-2 works correctly, but 2.4.4-ac9 doesn't. I think 2.4.3 didn't work.
RH 2.4.2-2 and 2.4.4-ac9 are I believe the same driver exactly. 2.4.3 is an ancient known not to work well driver
Quoted 3 lines · Alan Cox
RH 2.4.2-2 and 2.4.4-ac9 are I believe the same driver exactly. 2.4.3 is an ancient known not to work well driver
Ummm... Here's stripped dmesg of both kernels... Is this compiler thingie or Athlon optimizations?
Notice also different detected PDC20265 BIOS settings! So 2.4.4-ac9 detects those BIOS settings correctly and 2.4.2-2 doesn't. That's probably reason why 2.4.2-2 works?
--- 8< ---
Linux version 2.4.4-ac9 (root@davinci) (gcc version 2.95.3 20010315 (release)) #1 Wed May 16 17:37:30 EEST 2001
Uniform Multi-Platform E-IDE driver Revision: 6.31
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xxVP_IDE: IDE controller on PCI bus 00 dev 21VP_IDE: chipset revision 6VP_IDE: not 100% native mode: will probe irqs later
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xxVP_IDE: VIA vt82c686b (rev 40) IDE UDMA100 controller on pci00:04.1
ide0: BM-DMA at 0xb800-0xb807, BIOS settings: hda:DMA, hdb:DMA
PDC20265: IDE controller on PCI bus 00 dev 88
PCI: Found IRQ 10 for device 00:11.0
PDC20265: chipset revision 2
PDC20265: not 100% native mode: will probe irqs later
PDC20265: (U)DMA Burst Bit ENABLED Primary PCI Mode Secondary PCI Mode.
ide2: BM-DMA at 0x7400-0x7407, BIOS settings: hde:DMA, hdf:DMA
ide3: BM-DMA at 0x7408-0x740f, BIOS settings: hdg:DMA, hdh:DMAhda: IBM-DTLA-307030, ATA DISK drive
hdb: SONY CDU4811, ATAPI CD/DVD-ROM drive
hde: IBM-DTLA-307030, ATA DISK drive
hdf: IBM-DTLA-307030, ATA DISK drive
hdg: IBM-DTLA-307030, ATA DISK drive
hdh: IBM-DTLA-307030, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide2 at 0x8800-0x8807,0x8402 on irq 10
ide3 at 0x8000-0x8007,0x7802 on irq 10
hda: 60036480 sectors (30739 MB) w/1916KiB Cache, CHS=3737/255/63, UDMA(100)
hde: 60036480 sectors (30739 MB) w/1916KiB Cache, CHS=59560/16/63, UDMA(100)
hdf: 60036480 sectors (30739 MB) w/1916KiB Cache, CHS=59560/16/63, UDMA(100)
hdg: 60036480 sectors (30739 MB) w/1916KiB Cache, CHS=59560/16/63, UDMA(100)
hdh: 60036480 sectors (30739 MB) w/1916KiB Cache, CHS=59560/16/63, UDMA(100) Partition check:
hda:hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide0: reset: success
hda1 hda2 hda3 hda4
hde: hde1 hde2 hde3 hde4
hdf: unknown partition table
hdg: unknown partition table
hdh: unknown partition table
--- 8< ---
Linux version 2.4.2-2 ([email protected]) (gcc version 2.96 20000731 (Red Hat Linux 7.1 2.96-79)) #1 Sun Apr 8 20:41:30 EDT 2001
Uniform Multi-Platform E-IDE driver Revision: 6.31
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xxVP_IDE: IDE controller on PCI bus 00 dev 21VP_IDE: chipset revision 6VP_IDE: not 100% native mode: will probe irqs later
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xxVP_IDE: VIA vt82c686b (rev 40) IDE UDMA100 controller on pci00:04.1
ide0: BM-DMA at 0xb800-0xb807, BIOS settings: hda:DMA, hdb:DMA
PDC20265: IDE controller on PCI bus 00 dev 88
PCI: Found IRQ 10 for device 00:11.0
PDC20265: chipset revision 2
PDC20265: not 100% native mode: will probe irqs later
PDC20265: (U)DMA Burst Bit ENABLED Primary PCI Mode Secondary PCI Mode.
ide2: BM-DMA at 0x7400-0x7407, BIOS settings: hde:DMA, hdf:pio
ide3: BM-DMA at 0x7408-0x740f, BIOS settings: hdg:pio, hdh:piohda: IBM-DTLA-307030, ATA DISK drive
hdb: SONY CDU4811, ATAPI CD/DVD-ROM drive
hde: IBM-DTLA-307030, ATA DISK drive
hdf: IBM-DTLA-307030, ATA DISK drive
hdg: IBM-DTLA-307030, ATA DISK drive
hdh: IBM-DTLA-307030, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide2 at 0x8800-0x8807,0x8402 on irq 10
ide3 at 0x8000-0x8007,0x7802 on irq 10
hda: 60036480 sectors (30739 MB) w/1916KiB Cache, CHS=3737/255/63, UDMA(33)
hde: 60036480 sectors (30739 MB) w/1916KiB Cache, CHS=59560/16/63, UDMA(100)
hdf: 60036480 sectors (30739 MB) w/1916KiB Cache, CHS=59560/16/63, UDMA(100)
hdg: 60036480 sectors (30739 MB) w/1916KiB Cache, CHS=59560/16/63, UDMA(100)
hdh: 60036480 sectors (30739 MB) w/1916KiB Cache, CHS=59560/16/63, UDMA(100) Partition check:
hda: hda1 hda2 hda3 hda4
hde: hde1 hde2 hde3 hde4
hdf: unknown partition table
hdg: unknown partition table
hdh: unknown partition table
--- 8< ---
- Jussi Laako
Signature · 2 lines
PGP key fingerprint: 161D 6FED 6A92 39E2 EB5B 39DD A4DE 63EB C216 1E4B Available at PGP keyservers
Quoted 2 lines
Ummm... Here's stripped dmesg of both kernels... Is this compiler thingie or Athlon optimizations?
Neither by the look of it
Quoted 3 lines
Notice also different detected PDC20265 BIOS settings! So 2.4.4-ac9 detects those BIOS settings correctly and 2.4.2-2 doesn't. That's probably reason why 2.4.2-2 works?
Could be.
Quoted 2 lines
hda:
dma_intr: error=0x84 { DriveStatusError BadCRC }
hda:dma_intr: status=0x51 { DriveReady SeekComplete Error }
CRC errors are cable errors so that bit is reasonable in itself
Re: VIA/PDC/Athlon - IDE error theory
Quoted 4 lines · Alan Cox
Quoted 2 lines
hda:
dma_intr: error=0x84 { DriveStatusError BadCRC }
hda:dma_intr: status=0x51 { DriveReady SeekComplete Error }CRC errors are cable errors so that bit is reasonable in itself
Could this be caused by the RAID configuration? The first sector of the first disk holds the partition table. The other disks in the raid have no valid partition table:
dmesg message from Jussi Laako:
hdf: unknown partition table
hdg: unknown partition table
hdh: unknown partition table
[snip]
If there is a raid (1+)0 configured you got a volume that is bigger than the first hd. So if you have extended partitions or freebsd slices which are located beyond the capacity of the hd, then the partition table check would have to read datastructures which have an offset which is to high. => read error during partition check => nasty error messages
I have the error message problem on my box. DMA is disabled because of the error on /dev/hda. But a hdparm -d 1 /dev/hda fixes this, and I do not get more errors regarding that. Everything works fine. (I did not compile with Athlon optimization.)
regards,
Wilfried
Re: VIA/PDC/Athlon - IDE error theory
In reply to Alan CoxQuoted 4 lines · Wilfried Weissmann
Quoted 3 lines
Quoted 2 lines
hda:
dma_intr: error=0x84 { DriveStatusError BadCRC }
hda:dma_intr: status=0x51 { DriveReady SeekComplete Error }CRC errors are cable errors so that bit is reasonable in itself
Could this be caused by the RAID configuration? The first sector of the
Yes, it's RAID5. But the error message is because of misdetected cable...
- Jussi Laako
Signature · 2 lines
PGP key fingerprint: 161D 6FED 6A92 39E2 EB5B 39DD A4DE 63EB C216 1E4B Available at PGP keyservers
Quoted 6 lines · Zilvinas Valinskas
looks like VIA drivers do something to hardware (or maybe only ACPI part of hardware ... I don't know.) and linux can't handle hardware is this new "after win9x" state ...
reset/clear CMOS with jumper helped.
I have ACPI disabled from the kernel. The machine have never seen any windows...
- Jussi Laako
Signature · 2 lines
PGP key fingerprint: 161D 6FED 6A92 39E2 EB5B 39DD A4DE 63EB C216 1E4B Available at PGP keyservers