From: Greg Stark <gsstark@mit.edu>
To: Jakob Oestergaard <jakob@unthought.net>
Cc: Greg Stark <gsstark@mit.edu>, linux-kernel@vger.kernel.org
Subject: Re: More tests [Was: Problem with read blocking for a long time on /dev/scd1]
Date: 23 Dec 2002 03:58:02 -0500 [thread overview]
Message-ID: <87n0mxt8md.fsf@stark.dyndns.tv> (raw)
In-Reply-To: <20021222201345.GG30634@unthought.net>
Jakob Oestergaard <jakob@unthought.net> writes:
> On Sun, Dec 22, 2002 at 11:13:14AM -0500, Greg Stark wrote:
> >
> > I've done some more tests:
> >
> > The problem still occurs with straight ide drivers, no ide-scsi
> >
> > The problem still occurs with 2.4.20-ac2
>
> Can you reproduce on 2.4.18 or 2.4.19-pre5 ?
>
> AFAIK 2.4.X broke at 2.4.19-pre6 - something was changed that related to
> the order in which read requests are scheduled.
I originally had the problem with 2.4.18 and only updated to 2.4.20-ac2 hoping
it would solve the problem. It doesn't look like the same issue as yours.
When your process is blocked, what wait channel does ps -elf list for it?
What system call does strace -T show it executing and for how long?
I wonder what else is on the ide channels, perhaps if I move things around so
it's the only device on that channel it would help?
--
greg
next prev parent reply other threads:[~2002-12-23 8:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-21 0:49 Problem with read blocking for a long time on /dev/scd1 Gregory Stark
2002-12-21 1:28 ` Greg Stark
2002-12-21 6:14 ` Greg Stark
2002-12-22 16:13 ` More tests [Was: Problem with read blocking for a long time on /dev/scd1] Greg Stark
2002-12-22 20:13 ` Jakob Oestergaard
2002-12-23 8:58 ` Greg Stark [this message]
2002-12-27 15:36 ` Jakob Oestergaard
2003-01-08 4:03 ` Jakob Oestergaard
2002-12-23 18:02 ` Problem with read blocking for a long time on /dev/scd1 Krzysztof Halasa
2003-01-08 12:03 More tests [Was: Problem with read blocking for a long time on /dev/scd1] Andrey Borzenkov
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=87n0mxt8md.fsf@stark.dyndns.tv \
--to=gsstark@mit.edu \
--cc=jakob@unthought.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
Powered by JetHome