The / (root) filesystem was currupted somehow by a crash/power failure (not hard drive or badblock malfunction). Although su-journal check did not show anything wrong underlying filesystem was corrupted and that lead to further kernel panic on each boot.
I guess filesystem related (or any?) kernel panic should enforce full filesystem chceck (some filesystem flag or journal timestamp modification to enforce full check).
Maybe it is possible to stop the OS in that case (filesystem), perform some sort of fsck running from memory, and then continue one time again the OS with no crash? :-)
fix synopsis and assign
For bugs matching the following criteria:
Status: In Progress Changed: (is less than) 2014-06-01
Reset to default assignee and clear in-progress tags.
Mail being skipped