Hi, On Thu, 2005-06-09 at 08:59, Andreas Dilger wrote: > When the problem hits use sysrq-t and/or sysrq-p on the console to dump > the stack of kjournald, as a starting point to see what it is doing. A kernel "readprofile" can also be very useful for this. --Stephen