public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Taavo Raykoff" <traykoff@snet.net>
To: <linux-kernel@vger.kernel.org>
Subject: 2.4.18 IDE channels block each other under load?
Date: Fri, 21 Jun 2002 10:03:41 -0400	[thread overview]
Message-ID: <000801c2192c$72e37580$ad0aa8c0@trws> (raw)

Can someone tell me what is going on here?

dd if=/dev/zero of=/dev/hda bs=1024 count=1000000

then in another vt:
fdisk /dev/hdc, then immediately press "q".

fdisk "hangs" for a long, long time.
ps -aux says state of dd and fdisk are both "D"
strace says fdisk is hanging on the close()
/proc/interrupts tell me that ide1 (/dev/hdc) is getting no 
 int activity for a long, long time. ide0 is very busy.

It is not just dd/fdisk.  Any intensive writes on one IDE 
channel (direct to the hd? device) seem to block any IO on 
the other device. 

Intel SAI2 MB, ServerWorks IDE chipset, 2.4.18, two IDE 
hard drives /dev/hda and /dev/hdc, 1024MB RAM, RH73 kernel
build.

Also seen on Promise PDCx IDE controllers hanging off the PCI.

hdparm settings appear to have no influence on this behavior.

Thanks,
TR.




             reply	other threads:[~2002-06-21 14:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-21 14:03 Taavo Raykoff [this message]
2002-06-21 14:17 ` 2.4.18 IDE channels block each other under load? Roy Sigurd Karlsbakk
2002-06-21 15:14   ` T.Raykoff
     [not found] <fa.e5te67v.1s3m1qr@ifi.uio.no>
2002-07-22 20:08 ` Aniket Malatpure
2002-07-22 21:09   ` Andre Hedrick
     [not found] <Pine.LNX.4.33.0207221750210.22553-100000@coffee.psychology.mcmaster.ca>
2002-07-22 23:04 ` T.Raykoff
2002-07-30 16:18   ` Bill Davidsen
  -- strict thread matches above, loose matches on Subject: below --
2002-07-30 17:27 Roman Kagan

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='000801c2192c$72e37580$ad0aa8c0@trws' \
    --to=traykoff@snet.net \
    --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