mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: nakai <nakai@neo.shinko.co.jp>
To: linux-kernel@vger.kernel.org
Subject: badblocks fails with promise 100TX2
Date: Wed, 14 Nov 2001 11:50:39 +0900	[thread overview]
Message-ID: <3BF1DBFF.C02A5274@neo.shinko.co.jp> (raw)

When I run badblocks, it failed, sometime it hanged OS.

Condition:
    runs 2 badblocks command at same time, check different drives.
    EX) badblocks /dev/hdh4; badblocks /dev/hde4
    /dev/hdh and /dev/hde is connected to promise fasttrak 66
    (with pdc20267 chip). I also tested with fasttrak 100TX2 (with
    pdc20268), and got same results.
    Duron(800)/VT133/VIA686b
    RedHat7.1(with 2.4.10 kernel)
Results:
    They report many blocks(are broken). If I kill one badblocks
    command, another badblocks command stops reporting blocks. 
    I think there is conflict when read out.
    On 2.4.2, there is no problem (but can not use fasttrak 100).
    
I know, there is some changes on ide-pci.c between 2.4.2 and 2.4.10,
and many changes on pdc202xx.c. Something go wrong?
I just want to build software RAID. But by this problem, I can
not build Software RAID with new promise 100TX2 card.

-- 
-=-=-=-=  SHINKO ELECTRIC INDUSTRIES CO., LTD.           =-=-=-=-
=-=-=-=-    Core Technology Research & Laboratory,       -=-=-=-=
-=-=-=-=      Infomation Technology Research Dept.       =-=-=-=-
=-=-=-=-  Name:Hisakazu Nakai          TEL:026-283-2866  -=-=-=-=
-=-=-=-=  Mail:nakai@neo.shinko.co.jp  FAX:026-283-2820  =-=-=-=-

                 reply	other threads:[~2001-11-14  2:51 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3BF1DBFF.C02A5274@neo.shinko.co.jp \
    --to=nakai@neo.shinko.co.jp \
    --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®