I thought I would have a look at the code with kgdb. Firstly I noticed
that schedule is not defined in the kgdb enabled kernel. Also even
if I put this detect routine in a spin for a while my interrupts do not
get serviced until after this spin and quite possibly not until the
detect routine returns.
I would like to know the correct way to facilitate a delay in a scsi
module detect routine, while waiting for a hardware condition which
gets satisfied by a number of interrupts. If this condition is not met
in a timeout period the code also continue.
I would also like to understand the kgdb kernel behaviour.
I am running a 2.4.16 kernel.
Cheers
Simon.
__________________________
Simon Haynes - Baydel
Phone : 44 (0) 1372 378811
Email : simon@baydel.com
__________________________
-
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/