linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Willy Tarreau <willy@w.ods.org>
To: Clayton Weaver <cgweav@email.com>
Cc: willy@w.ods.org, linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.21-rc7
Date: Sun, 8 Jun 2003 23:47:11 +0200	[thread overview]
Message-ID: <20030608214711.GA4584@alpha.home.local> (raw)
In-Reply-To: <20030608201700.3850.qmail@email.com>

 
> Note that "nodma" is unnecessary on this
> same box running kernel 2.4.19-rc2. Why would
> 2.4.21-rcX need it? To pin down whether the
> problem is in the ide dma code or some other
> part of the ide code?

exactly, because DMA needs more conditions than PIO to run at all
and even more to run reliably. There are lots of cases where DMA
doesn't work while PIO does.
 
> It does not die more easily with 2.4.19-rc2
> (in my opinion). It dies in a threads context
> but not in a forks context, where the threads
> and the forks are doing the same i/o to/from
> the same controller/disk (different versions
> of same program).
>
> I have also seen it freeze with an unlucky
> mouse click in XFree86 4.0 under 2.4.19-rc2,
> so I did not assume that the threads hang
> was necessarily ide-relevant. Something
> disk i/o intensive was merely what it
> happened to be doing with those threads,
> but that problem seemed to me more thread
> related than ide related. (Guess I'll have
> to spawn a bunch of threads doing some other
> kind of i/o to test that assumption.)

OK, but a freeze isn't acceptable anyway, whatever you were doing,
because it always means a bug somewhere.

Cheers,
Willy

PS: your lines were shorter this way :-)


  parent reply	other threads:[~2003-06-08 21:37 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-08 20:17 Linux 2.4.21-rc7 Clayton Weaver
2003-06-08 20:51 ` Bartlomiej Zolnierkiewicz
2003-06-08 21:47 ` Willy Tarreau [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-06-08  8:54 Clayton Weaver
2003-06-08  9:47 ` Willy Tarreau
2003-06-03 18:45 Margit Schubert-While
2003-06-03 18:50 ` Marc-Christian Petersen
2003-06-03 19:38   ` Christoph Hellwig
2003-06-03 17:04 Marcelo Tosatti
2003-06-03 18:02 ` Tomas Szepe
2003-06-03 18:07   ` Marcelo Tosatti
2003-06-03 19:15     ` lk
2003-06-03 19:40       ` Alan Cox
2003-06-03 18:30 ` Alex Romosan
2003-06-03 19:27   ` Jeff Garzik
2003-06-03 19:58     ` Alex Romosan
2003-06-03 20:14       ` Tom Rini
2003-06-04  3:35         ` David S. Miller
2003-06-04 15:09           ` Mr. James W. Laferriere
2003-06-04 23:37           ` Alex Romosan
2003-06-05 12:09 ` Andreas Haumer
2003-06-07 15:46   ` Andreas Haumer
2003-06-11 20:48     ` Marcelo Tosatti
     [not found]       ` <1055408183.2552.18.camel@tor.trudheim.com>
2003-06-12  9:35         ` Andreas Haumer

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=20030608214711.GA4584@alpha.home.local \
    --to=willy@w.ods.org \
    --cc=cgweav@email.com \
    --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;
as well as URLs for NNTP newsgroup(s).