lkml.org 
[lkml]   [2002]   [Jun]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: linux 2.4.19-preX IDE bugs
    On Thu, 13 Jun 2002, Nick Evgeniev wrote:

    > Hi,
    >
    > First of all I have to claim that it's a driver fault not a hardware!
    > Because after switching
    > the same cable on different (VIA UDMA66) controller everything seems to work
    > ok for last 3 days.

    That sounds more like USER ERROR. If you still had the error after
    switching cable, I would still suspect hardware given it is VIA.
    It also still may be hardware, since cables can come odd or even in
    grounding.

    > And I have no kernel errors. Hence I conclude that it's a DRIVER bug.

    If you had connected them correct the first time like they are now, you
    would not have had a complaint. Next, maybe spend more money to get
    quality hardware, since VIA hardware has a history of being poorly
    intergrated.

    Now think for two seconds or longer if needed.

    It now works and the driver has not changed.

    Conclusion, it is not the driver!

    Have a good day,

    Andre Hedrick
    LAD Storage Consulting Group


    > Well, lets get to hardware... I've got dual PIII MSI motheboard based on VIA
    > chipset with extra IDE controller (promise) on board.
    > Details:
    > 1. CPU
    > >---------------------------------------------------------------------------
    > ----------------------------------
    > processor : 1
    > vendor_id : GenuineIntel
    > cpu family : 6
    > model : 8
    > model name : Pentium III (Coppermine)
    > stepping : 3
    > cpu MHz : 600.027
    > cache size : 256 KB
    > fdiv_bug : no
    > hlt_bug : no
    > f00f_bug : no
    > coma_bug : no
    > fpu : yes
    > fpu_exception : yes
    > cpuid level : 2
    > wp : yes
    > flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
    > cmov pat pse36 mmx fxsr sse
    > bogomips : 1199.30
    > 2. PCI info:
    > >---------------------------------------------------------------------------
    > --------------------------------------------------------------
    > 00:00.0 Host bridge: VIA Technologies, Inc. VT82C693A/694x [Apollo PRO133x]
    > (rev c4)
    > Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
    > Stepping- SERR- FastB2B-
    > Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
    > <TAbort- <MAbort+ >SERR- <PERR+
    > Latency: 0
    > Region 0: Memory at d0000000 (32-bit, prefetchable) [size=64M]
    > Capabilities: [a0] AGP version 2.0
    > Status: RQ=31 SBA+ 64bit- FW- Rate=x1,x2
    > Command: RQ=0 SBA- AGP- 64bit- FW- Rate=<none>
    > Capabilities: [c0] Power Management version 2
    > Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
    > PME(D0-,D1-,D2-,D3hot-,D3cold-)
    > Status: D0 PME-Enable- DSel=0 DScale=0 PME-
    >
    > 00:01.0 PCI bridge: VIA Technologies, Inc. VT82C598/694x [Apollo
    > MVP3/Pro133x AGP] (prog-if 00 [Normal decode])
    > Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
    > Stepping- SERR- FastB2B-
    > Status: Cap+ 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
    > <TAbort- <MAbort+ >SERR- <PERR-
    > Latency: 0
    > Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
    > I/O behind bridge: 0000f000-00000fff
    > Memory behind bridge: d4000000-dbffffff
    > Prefetchable memory behind bridge: fff00000-000fffff
    > BridgeCtl: Parity- SERR- NoISA+ VGA+ MAbort- >Reset- FastB2B-
    > Capabilities: [80] Power Management version 2
    > Flags: PMEClk- DSI- D1+ D2- AuxCurrent=0mA
    > PME(D0-,D1-,D2-,D3hot-,D3cold-)
    > Status: D0 PME-Enable- DSel=0 DScale=0 PME-
    >
    > 00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South]
    > (rev 22)
    > Subsystem: VIA Technologies, Inc. VT82C686/A PCI to ISA Bridge
    > Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
    > Stepping+ SERR- FastB2B-
    > Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
    > <TAbort- <MAbort- >SERR- <PERR-
    > Latency: 0
    >
    > 00:07.1 IDE interface: VIA Technologies, Inc. Bus Master IDE (rev 10)
    > (prog-if 8a [Master SecP PriP])
    > Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
    > Stepping- SERR- FastB2B-
    > Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
    > <TAbort- <MAbort- >SERR- <PERR-
    > Latency: 32
    > Region 4: I/O ports at 9000 [size=16]
    > Capabilities: [c0] Power Management version 2
    > Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
    > PME(D0-,D1-,D2-,D3hot-,D3cold-)
    > Status: D0 PME-Enable- DSel=0 DScale=0 PME-
    >
    > 00:07.2 USB Controller: VIA Technologies, Inc. UHCI USB (rev 10) (prog-if 00
    > [UHCI])
    > Subsystem: Unknown device 0925:1234
    > Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
    > Stepping- SERR- FastB2B-
    > Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
    > <TAbort- <MAbort- >SERR- <PERR-
    > Latency: 32, cache line size 08
    > Interrupt: pin D routed to IRQ 19
    > Region 4: I/O ports at 9400 [size=32]
    > Capabilities: [80] Power Management version 2
    > Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
    > PME(D0-,D1-,D2-,D3hot-,D3cold-)
    > Status: D0 PME-Enable- DSel=0 DScale=0 PME-
    >
    > 00:07.3 USB Controller: VIA Technologies, Inc. UHCI USB (rev 10) (prog-if 00
    > [UHCI])
    > Subsystem: Unknown device 0925:1234
    > Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
    > Stepping- SERR- FastB2B-
    > Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
    > <TAbort- <MAbort- >SERR- <PERR-
    > Latency: 32, cache line size 08
    > Interrupt: pin D routed to IRQ 19
    > Region 4: I/O ports at 9800 [size=32]
    > Capabilities: [80] Power Management version 2
    > Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
    > PME(D0-,D1-,D2-,D3hot-,D3cold-)
    > Status: D0 PME-Enable- DSel=0 DScale=0 PME-
    >
    > 00:07.4 Host bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI]
    > (rev 30)
    > Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
    > Stepping- SERR- FastB2B-
    > Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
    > <TAbort- <MAbort- >SERR- <PERR-
    > Interrupt: pin ? routed to IRQ 9
    > Capabilities: [68] Power Management version 2
    > Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
    > PME(D0-,D1-,D2-,D3hot-,D3cold-)
    > Status: D0 PME-Enable- DSel=0 DScale=0 PME-
    >
    > 00:07.5 Multimedia audio controller: VIA Technologies, Inc. AC97 Audio
    > Controller (rev 20)
    > Subsystem: VIA Technologies, Inc. AC97 Audio Controller
    > Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
    > Stepping- SERR- FastB2B-
    > Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
    > <TAbort- <MAbort- >SERR- <PERR-
    > Interrupt: pin C routed to IRQ 18
    > Region 0: I/O ports at 9c00 [size=256]
    > Region 1: I/O ports at a000 [size=4]
    > Region 2: I/O ports at a400 [size=4]
    > Capabilities: [c0] Power Management version 2
    > Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
    > PME(D0-,D1-,D2-,D3hot-,D3cold-)
    > Status: D0 PME-Enable- DSel=0 DScale=0 PME-
    >
    > 00:0c.0 Unknown mass storage controller: Promise Technology, Inc. 20265 (rev
    > 02)
    > Subsystem: Promise Technology, Inc.: Unknown device 4d33
    > Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
    > Stepping- SERR- FastB2B-
    > Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
    > <TAbort- <MAbort- >SERR- <PERR-
    > Latency: 32
    > Interrupt: pin A routed to IRQ 18
    > Region 0: I/O ports at ac00 [size=8]
    > Region 1: I/O ports at b000 [size=4]
    > Region 2: I/O ports at b400 [size=8]
    > Region 3: I/O ports at b800 [size=4]
    > Region 4: I/O ports at bc00 [size=64]
    > Region 5: Memory at dd100000 (32-bit, non-prefetchable) [size=128K]
    > Expansion ROM at <unassigned> [disabled] [size=64K]
    > Capabilities: [58] Power Management version 1
    > Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
    > PME(D0-,D1-,D2-,D3hot-,D3cold-)
    > Status: D0 PME-Enable- DSel=0 DScale=0 PME-
    >
    > 00:0d.0 FireWire (IEEE 1394): Texas Instruments: Unknown device 8020
    > (prog-if 10 [OHCI])
    > Subsystem: Texas Instruments: Unknown device 8020
    > Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
    > Stepping- SERR- FastB2B-
    > Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
    > <TAbort- <MAbort- >SERR- <PERR-
    > Latency: 32 (750ns min, 1000ns max), cache line size 08
    > Interrupt: pin A routed to IRQ 19
    > Region 0: Memory at dd125000 (32-bit, non-prefetchable) [size=2K]
    > Region 1: Memory at dd120000 (32-bit, non-prefetchable) [size=16K]
    > Capabilities: [44] Power Management version 1
    > Flags: PMEClk- DSI- D1- D2+ AuxCurrent=0mA
    > PME(D0-,D1-,D2+,D3hot+,D3cold-)
    > Status: D0 PME-Enable- DSel=0 DScale=0 PME-
    >
    > 00:0e.0 Ethernet controller: Intel Corp. 82557 [Ethernet Pro 100] (rev 08)
    > Subsystem: Intel Corp. EtherExpress PRO/100+ Management Adapter
    > Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
    > Stepping- SERR- FastB2B-
    > Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
    > <TAbort- <MAbort- >SERR- <PERR-
    > Latency: 32 (2000ns min, 14000ns max), cache line size 08
    > Interrupt: pin A routed to IRQ 16
    > Region 0: Memory at dd124000 (32-bit, non-prefetchable) [size=4K]
    > Region 1: I/O ports at c000 [size=64]
    > Region 2: Memory at dd000000 (32-bit, non-prefetchable) [size=1M]
    > Expansion ROM at <unassigned> [disabled] [size=1M]
    > Capabilities: [dc] Power Management version 2
    > Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA
    > PME(D0+,D1+,D2+,D3hot+,D3cold+)
    > Status: D0 PME-Enable- DSel=0 DScale=2 PME-
    >
    > 01:00.0 VGA compatible controller: S3 Inc. 86c368 [Trio 3D/2X] (rev 02)
    > (prog-if 00 [VGA])
    > Subsystem: S3 Inc. Trio3D/2X
    > Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
    > Stepping- SERR- FastB2B-
    > Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
    > <TAbort- <MAbort- >SERR- <PERR-
    > Latency: 32 (1000ns min, 63750ns max)
    > Region 0: Memory at d4000000 (32-bit, non-prefetchable) [size=64M]
    > Expansion ROM at <unassigned> [disabled] [size=64K]
    > Capabilities: [dc] Power Management version 1
    > Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA
    > PME(D0-,D1-,D2-,D3hot-,D3cold-)
    > Status: D0 PME-Enable- DSel=0 DScale=0 PME-
    > Capabilities: [80] AGP version 1.0
    > Status: RQ=31 SBA- 64bit- FW- Rate=x1,x2
    > Command: RQ=0 SBA- AGP- 64bit- FW- Rate=x2
    >
    >
    >
    >
    > > Well be more specific on the hardware.
    > > Remember Promise came in and started dorking the driver.
    > > Next they will not admit to an asic bug even thought I have called them on
    > > the existance. 2.5 can not fix it, it will only blow up in 2.5. Hell it
    > > is possiblely blowing up in 2.4 but less likely.
    > >
    > > So spell out the hardware in question.
    > >
    > > The new chip hardware lost its interrupt parse because promise took it out
    > > of the pci space and it made the driver less stable because the hardware
    > > is less stable.
    > >
    > > On Tue, 11 Jun 2002, Nick Evgeniev wrote:
    > >
    > > > Hi,
    > > >
    > > > > > I added it to the collection of IDE oddities I'm looking at. There
    > are
    > > > > > also some promise requested changes due to get merged at the end of
    > this
    > > > > > week. Then we can see where we stand
    > > > >
    > > > > Also, it is hard to answer email without connectivity in the air.
    > > >
    > > > Agreed. But all what I see is that STABLE Linux kernel DOESN'T has
    > working
    > > > driver for promise controller (including latest ac patches) for SEVERAL
    > > > MONTHS.
    > > > And as for now there is no any progress in fixing it. I don't blame on
    > you,
    > > > or Alan,
    > > > or whoever else. All I have to suggest is to drop promise support in
    > stable
    > > > kernel,
    > > > then rewrite/fix it in 2.5 tree... and then backport it to 2.4.
    > > >
    > > > I don't want to make experiments in production environment anymore...
    > And
    > > > it's
    > > > unfair to the rest of Linux users to keep broken drivers in stable
    > kernel...
    > > > Because
    > > > nobody expects that stable kernel will rip your fs _daily_.
    > > >
    > > >
    > > >
    > >
    > > Andre Hedrick
    > > LAD Storage Consulting Group
    > >
    > >
    >

    -
    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/

    \
     
     \ /
      Last update: 2005-03-22 13:26    [W:0.046 / U:40.272 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site