Please let me elaborate a bit on this, to give you may be
some hints about where to look for an actual solution of
the problem:
Zwane Mwaikambo wrote:
> Please refer to Subject [PANIC] 2.5.5-pre1 elevator.c for more detailed
> explanation.
>
> I don't really like this patch mainly because it _really_ feels like a
> bandaid for a larger problem in ide-cd, namely it violating the ide
> layers command requirements. But it does stop my box from oopsing and
> lets it finish the "dd" i was doing. Oops is at the end.
>
> diffed against 2.5.6-pre3 (one down 2 quadrillion to go ;)
>
> --- linux-2.5.6-pre/drivers/ide/ide-cd.c.orig Fri Mar 8 12:09:10 2002
> +++ linux-2.5.6-pre/drivers/ide/ide-cd.c Fri Mar 8 12:04:08 2002
> @@ -666,9 +666,11 @@
> cdrom_end_request(drive, 0);
> }
>
> - /* If we got a CHECK_CONDITION status,
> - queue a request sense command. */
> - if ((stat & ERR_STAT) != 0)
> + /* If we got a CHECK_CONDITION status, queue a request sense command,
> + however if we're generating spurious errors, make sure we don't
> + attempt to queue an an already started request.
> + */
> + if (((stat & ERR_STAT) != 0) && !(rq->flags & REQ_STARTED))
> cdrom_queue_request_sense(drive, NULL, NULL, NULL);
> } else
> blk_dump_rq_flags(rq, "ide-cd bad flags");
>
After having a look at the oops I think that this may be very well a
symptom of another problem in the ide-cd.c drivers overall
way of working. Please let me elaborate a bit.
In ide.c there is one central interrupt handler, namely:
void ide_timer_expiry(unsigned long data)
This function is called upon finish of every command.
However for cd-rom there are commands, which can
take quite a long time. Therefore there is the possiblity there
to provide a polling function, which will be engaged after the
interrupt happens in the above function:
/* continue */
if ((wait = expiry(drive)) != 0) {
/* reengage timer */
hwgroup->timer.expires = jiffies + wait;
add_timer(&hwgroup->timer);
spin_unlock_irqrestore(&ide_lock, flags);
return;
}
And plase guess whot? CD-ROM is the only driver which is using
this facility. Please have a look at the last
argument of ide_set_handler(). The second argument is the
interrutp handler for a command. The third is supposed to be
the poll timerout function. But if you look at the
actual poll function found in ide-cd.c (and only there).
You may as well feel to try to just execute its commands directly in
ide_timer_expiry, thus reducing tons of possible races ind the
overall intr handling found currently there.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Fri Mar 15 2002 - 22:00:08 EST