> I am trying to close all possible points where the double timer could
> happen. The object is to isolate it to hardware behavior, and determine
> what the event sequence is which is committing the sin.
Out of interest, which other situations have you seen it happen? I'm only
aware of the one.
> Once constrained, it goes to a lab where I have access to a 320 channel
> or 8 x 40 channel POD digital trace/recorder to map the HOST driver
> against the device(s) response. This is a major pain in the debugging
> process but it will close the issue for good.
Bugs, like roaches, have a terrible habit of surviving the worst nuking
you can possibly inflict ;)
Goodluck,
Zwane
-
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/