mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Svetoslav Slavtchev <galia@st-peter.stw.uni-erlangen.de>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: 2.6 test3-bk7 & -mm3 : HPT374 - cable missdetection, lock-ups
Date: Wed, 20 Aug 2003 14:53:39 +0200	[thread overview]
Message-ID: <1061384019.3f436f531a333@secure.st-peter.stw.uni-erlangen.de> (raw)

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 





-- 



             reply	other threads:[~2003-08-20 12:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-20 12:53 Svetoslav Slavtchev [this message]
2003-08-20 19:35 ` Jurriaan
2003-08-20 20:47   ` Svetoslav Slavtchev
2003-08-20 23:09 Duncan Laurie

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1061384019.3f436f531a333@secure.st-peter.stw.uni-erlangen.de \
    --to=galia@st-peter.stw.uni-erlangen.de \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®