Hi... On 2/1/08, Tang Rui <rui.tang@xxxxxxxxxxx> wrote: > Could anyone help me to analyse the following issue? I just > understand that during atomic operation my driver might call some methods > that can cause scheduling. > > I don't know where the problem is. Could anyone help me to figure it out? Can you show us your code too? seems like there's not much we can say from the stack trace: a. it deals with high res timer b. it call nanosleep maybe your timer function does something that blocks? regards, Mulyadi. -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx Please read the FAQ at http://kernelnewbies.org/FAQ
