From: Martin Dalecki <dalecki@evision-ventures.com>
To: tomita <tomita@cinet.co.jp>
Cc: Martin Dalecki <dalecki@evision-venures.com>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] IDE PIO write Fix #2
Date: Tue, 14 May 2002 11:20:30 +0200 [thread overview]
Message-ID: <3CE0D6DE.8090407@evision-ventures.com> (raw)
In-Reply-To: <3CE0795B.62C956F0@cinet.co.jp>
Uz.ytkownik tomita napisa?:
> Hi.
> This patch solves problem (for me)
> "kernel stops without message at heavy usage of IDE HDD".
> But, "hda: lost interrupt" message appears, instead.
> My BOX has both IDE and SCSI HDD.
> This message appears at accessing SCSI HDD by another
> task, during IDE heavy accsess.
> I guess, IDE driver has "critical section" needing "cli"
> (and so on).
> Any suggestions ?
>
> --- linux-2.5.15/drivers/ide/ide-taskfile.c.orig Fri May 10 11:49:35 2002
> +++ linux-2.5.15/drivers/ide/ide-taskfile.c Tue May 14 10:40:43 2002
> @@ -606,7 +606,7 @@
> if (!ide_end_request(drive, rq, 1))
> return ide_stopped;
>
> - if ((rq->current_nr_sectors==1) ^ (stat & DRQ_STAT)) {
> + if ((rq->nr_sectors == 1) ^ ((stat & DRQ_STAT) != 0)) {
> pBuf = ide_map_rq(rq, &flags);
> DTF("write: %p, rq->current_nr_sectors: %d\n", pBuf, (int) rq->current_nr_sectors);
Hmm. There is something else that smells in the above, since the XOR operator
doesn't seem to be proper. Why shouldn't we get DRQ_STAT at all on short
request? Could you perhaps just try to replace it with an OR?
Thinking about the kernel hang and SCSI - I would have to ask whatever there
is really interrupt sharing between IDE and SCSI. If the hangs happen due to
the usage of ide-scsi then I already know what's going - ide-scsi doesn't
do proper locking on command submission to the ATA layer.
next prev parent reply other threads:[~2002-05-14 10:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-14 2:41 [PATCH] IDE PIO write Fix #2 tomita
2002-05-14 9:20 ` Martin Dalecki [this message]
2002-05-14 19:29 ` Linus Torvalds
2002-05-15 5:47 ` Andre Hedrick
2002-05-15 9:47 ` Martin Dalecki
2002-05-17 19:24 ` Gunther Mayer
2002-05-20 1:41 ` Andre Hedrick
2002-05-20 6:48 ` Gunther Mayer
2002-05-20 20:26 ` Andre Hedrick
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=3CE0D6DE.8090407@evision-ventures.com \
--to=dalecki@evision-ventures.com \
--cc=dalecki@evision-venures.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tomita@cinet.co.jp \
/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