From: Martin Dalecki <dalecki@evision-ventures.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Davide Libenzi <davidel@xmailserver.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Jens Axboe <axboe@suse.de>
Subject: Re: ide timer trbl ...
Date: Mon, 11 Mar 2002 21:12:18 +0100 [thread overview]
Message-ID: <3C8D0FA2.6040803@evision-ventures.com> (raw)
In-Reply-To: <E16kWD2-0001bG-00@the-village.bc.nu>
Alan Cox wrote:
>>Would you mind as well to just apply ide-clean-18 and ide-clean-19
>>on top of each other and recheck?
>>
>
> We see that one on 2.4 if you enable some of the work in progress options.
> It seems that the timeout path is forgetting to clear the old handler. I've
> not pinned it down since its deep in the WIP stuff.
Ahh... this is really helpfull. Indeed I see the same. At most
places ide_set_handler get's just called without clearing
it before. This means that the IRQ handler routine abused as timeout handler
doesn't clear it as well. For example one could imagine that reset_pollfunc
get's called multiple times one after another on asynchronous interfaces.
Hmm but if one thinks a bit further: the timer is an entity related to a
command. If we stop sending commands with the assumption that master vers. slave
oprtations are mutual on each other, then it becomes abvious that this timeout
timer is indeed an entity, which should be hooked to a particular drive and not
just the interface (ide_hwif_t). So the fix will be a bit much
more involved. This may very well explain the problems of Zwambe as
well... (disks overlapping with CD-ROM operations).
Please correct me if my reasoning is wrong.
next prev parent reply other threads:[~2002-03-11 20:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-23 20:42 ide timer trbl Davide Libenzi
2002-02-24 4:48 ` Andre Hedrick
2002-03-11 19:53 ` Martin Dalecki
2002-03-11 20:15 ` Alan Cox
2002-03-11 20:12 ` Martin Dalecki [this message]
2002-03-11 20:31 ` Alan Cox
2002-03-12 14:21 ` Zwane Mwaikambo
2002-04-04 19:50 ` Mike Fedyk
2002-04-05 5:26 ` Andre Hedrick
2002-04-05 18:07 ` Mike Fedyk
2002-03-11 21:09 ` Davide Libenzi
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=3C8D0FA2.6040803@evision-ventures.com \
--to=dalecki@evision-ventures.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=axboe@suse.de \
--cc=davidel@xmailserver.org \
--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