Thanks for your reply. Actually, I got this messages on the screen during runtime: <blockquote style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;" class="gmail_quote"> Message from syslogd@foo at Thu Jul 7 13:06:35 2005 ... foo kernel: Assertion failure in journal_write_metadata_buffer() at journal.c:406: "buffer_jdirty(jh2bh(jh_in))" </blockquote> The machine would then hang and I have to do hard reboot I did fsck on the harddisk once and fsck said it is fine. Maybe there are hardware problem. So, I want some more hints from the kernel. Thanks, Koala Yeung <div>2005/10/18, Sam Varshavchik <<a href="mailto:mrsam@courier-mta.com">mrsam@courier-mta.com</a>>: <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Shu Hung (Koala) writes: > Dear all, > > I do receive some kernel error recently and I want to put on some kind of > "debug mode" for my kernel. > Seems something terrible happened to filesystem handling. I'm not quite > sure about that. > > Is there any "debug mode" for kernel? > How do I get more details log from kernel? > Do I have to recompile the kernel? Or is there other way? If you have to ask this question, even if you manage to recompile the kernel with additional debug stuff, you're not likely to make much sense out of the output. If you suspect filesystem corruption, the easiest thing to do is to create a dummy zero-length file "/forcefsck", then reboot. Then, during boot, all of your filesystems will get checked. -- fedora-list mailing list <a href="mailto:fedora-list@redhat.com">fedora-list@redhat.com</a> To unsubscribe: <a href="https://www.redhat.com/mailman/listinfo/fedora-list">https://www.redhat.com/mailman/listinfo/fedora-list </a> </blockquote></div> -- Technical Support, DigitalOne Limited Tel: 8100-2616 / 2545-1383 Fax: 2815-0593