Journaling will not do anything good in such case, as damaged kernel
could write damaged data to your harddisk. You should run full fsck
after every such lockup even if you are using journaled filesystem -
- unless you are 100% sure that kernel really stoped doing anything
instead of that it started doing strange things.
> Have you investigated the problems any further? I mean, does it hang in the
> vmware module (probably vmmon as it does not seem to be related to network or
> other peripheral activity), or is it somewhere in the main kernel code?
As there are no loops in vmmon, it is mathematically provable that it
did not end in endless loop with interrupts disabled inside vmmon ;-)
But it could die anywhere else.
Probably it is time for me to try Linus's kernel, but I have so perfect
exprience with Alan ones that I'm a bit reluctant to do that.
Best regards,
Petr Vandrovec
vandrove@vc.cvut.cz
-
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/