Macnish wrote: > I don't know if it is the case here, but sometimes printk is your best > friend on debug task.
If it happens on our test cluster, certainly, I'm using printk quite extensively here, but this was on a customer system. Neither can we reboot the system there easily, nor can I reproduce this here, so all I have is this trace. Cheers, Bernd -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to [EMAIL PROTECTED] Please read the FAQ at http://kernelnewbies.org/FAQ
