Hi
first test run of 2.6 on Epox 8k9a3+ VIA KT400 VT8235,
HPT374 and 4 IBM Deskstar GXP120 80Gb on each chanel as master
Mandrake-cooker gcc-3.3.1
the 3rd and the 4th chanel of the HPT374 are saying that the used cable
is 40 wires, so it forces the drives in UDMA33 which i think causes the lock-
ups several seconds after booting in runlevel 1
tried enabling "ignore word94 validation bits", didn't change anything
any hints ?
no dmesg or logs available because of the hard lock-ups
.configs from test3-bk7 & test3-mm3
cp -a /proc/ide & /sys
are at http://varna.demon.co.uk/~svetlio/2.6test3bk7/
svetljo
PS.
please CC me as i'm not subscribed to the list
/proc/ide/hpt366 2.4.22rc2
-------------------------
Controller: 0
Chipset: HPT374
--------------- Primary Channel --------------- Secondary Channel --------------
Enabled: yes yes
Cable: ATA-66 ATA-66
--------------- drive0 --------- drive1 ------- drive0 ---------- drive1 -------
DMA capable: yes no yes no
Mode: UDMA off UDMA off
Controller: 1
Chipset: HPT374
--------------- Primary Channel --------------- Secondary Channel --------------
Enabled: yes yes
Cable: ATA-66 ATA-66
--------------- drive0 --------- drive1 ------- drive0 ---------- drive1 -------
DMA capable: yes no yes no
Mode: UDMA off UDMA off
/proc/ide/hpt366 2.6 test3-bk7
----------------------------------
Controller: 0
Chipset: HPT374
--------------- Primary Channel --------------- Secondary Channel --------------
Enabled: yes yes
Cable: ATA-66 ATA-66
--------------- drive0 --------- drive1 ------- drive0 ---------- drive1 -------
DMA capable: yes no yes no
Mode: UDMA off UDMA off
Controller: 1
Chipset: HPT374
--------------- Primary Channel --------------- Secondary Channel --------------
Enabled: yes yes
Cable: ATA-33 ATA-33
--------------- drive0 --------- drive1 ------- drive0 ---------- drive1 -------
DMA capable: yes no yes no
Mode: UDMA off UDMA off
--
From: Svetoslav Slavtchev <[email protected]>
Date: Wed, Aug 20, 2003 at 02:53:39PM +0200
> Hi
>
> first test run of 2.6 on Epox 8k9a3+ VIA KT400 VT8235,
> HPT374 and 4 IBM Deskstar GXP120 80Gb on each chanel as master
> Mandrake-cooker gcc-3.3.1
>
> the 3rd and the 4th chanel of the HPT374 are saying that the used cable
> is 40 wires, so it forces the drives in UDMA33 which i think causes the lock-
> ups several seconds after booting in runlevel 1
>
As far as I know, I have no problems with my 3rd channel on my Epox
8K9A3+ motherboard. I've got a WD 80 Gb disk (8 Mb cache model) on it.
However, I've noticed something else.
As soon as I type
cat /proc/ide/hpt366
I get hit by the dreaded 'status=0x58 .... hdi interrupt lost' thing.
It tries to reset ide4, but keeps telling 'interrupt lost' and finally I
have to use the reset button. If I never cat /proc/ide/hpt366 I can run
the system for a week at a time, where hdi is part of a raid-0 partition
that contains both /home and my newsspool - so it's used frequently.
Kind regards,
Jurriaan
--
Carson heaved a sigh. "Easley tried to kill you. You retaliate by calling
yourself Jim Harrison. It seems a subtle revenge. Perhaps I'm stupid..."
Jack Vance - The Deadly Isles
Debian (Unstable) GNU/Linux 2.6.0-test3-mm3 4259 bogomips 1.04 0.41
Quoting Jurriaan <[email protected]>:
> From: Svetoslav Slavtchev <[email protected]>
> Date: Wed, Aug 20, 2003 at 02:53:39PM +0200
> > Hi
> >
> > first test run of 2.6 on Epox 8k9a3+ VIA KT400 VT8235,
> > HPT374 and 4 IBM Deskstar GXP120 80Gb on each chanel as master
> > Mandrake-cooker gcc-3.3.1
> >
> > the 3rd and the 4th chanel of the HPT374 are saying that the used cable
> > is 40 wires, so it forces the drives in UDMA33 which i think causes the
> lock-
> > ups several seconds after booting in runlevel 1
> >
> As far as I know, I have no problems with my 3rd channel on my Epox
> 8K9A3+ motherboard. I've got a WD 80 Gb disk (8 Mb cache model) on it.
a WD 80Gb, as in a single hard drive on the HPT374 ?
my first 2 chanels seems to be OK (couldn't test them good)
but they survive hdparm -d1 -u1 -c1 -X69, where as the 3rd & 4th chanel
reported UDMA4/5/6 not functional (or smth similar) and the system went down
> However, I've noticed something else.
>
> As soon as I type
>
> cat /proc/ide/hpt366
there might be smth similar here, but i get the lockups even if i don't play
with /proc/ide hdparm, and 1st, 2nd chanel are running at UDMA100 3rd, 4th at
UDMA33
> I get hit by the dreaded 'status=0x58 .... hdi interrupt lost' thing.
> It tries to reset ide4, but keeps telling 'interrupt lost' and finally I
> have to use the reset button. If I never cat /proc/ide/hpt366 I can run
> the system for a week at a time, where hdi is part of a raid-0 partition
> that contains both /home and my newsspool - so it's used frequently.
>
> Kind regards,
> Jurriaan
best,
svetljo
> first test run of 2.6 on Epox 8k9a3+ VIA KT400 VT8235,
> HPT374 and 4 IBM Deskstar GXP120 80Gb on each chanel as master
> Mandrake-cooker gcc-3.3.1
>
> the 3rd and the 4th chanel of the HPT374 are saying that the used
> cable is 40 wires, so it forces the drives in UDMA33 which i think
> causes the lock-ups several seconds after booting in runlevel 1
Here is a patch (against 2.6.0-test3) for the cable detect problem
on the 3rd/4th channels of the hpt374. This same patch made its
way into 2.4 via the -ac tree but hasn't been put in 2.6 yet.
It fixes some cable detect issues that stem from the fact that the
cable detect pins are also used as address/data lines, so they need
to first be configured as inputs to read valid cable detect state.
For everything from the 370 to function 0 of the 374:
bit 0 of register 0x5b must be cleared in order to make the
SCBLID/MA15 and PCBLID/MA16 pins as input.
For the 374 third/fourth channels (function 1):
bit 15 of register 0x52 and bit 15 of register 0x56 must be
set for TCBLID/MD6 and FCBLID/MD1 pins to be input.
I'm not sure it will actually help with your lockups, but at least
things will be detected right...
-duncan