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.
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.
Cheers,
Andre Hedrick
LAD Storage Consulting Group
On Fri, 22 Mar 2002, Zwane Mwaikambo wrote:
> On Fri, 22 Mar 2002, Jörn Engel wrote:
>
> > "handler not null, ..."
> > if (...handler == NULL) BUG();
> >
> > I am completely unaware of the real problem, but this doesn't match,
> > does it?
>
> ooh, Andre just pointed that out.
>
> Thanks,
> 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/
>
-
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/