Messages in this thread | | | Date | Fri, 15 Jun 2007 10:49:25 +0200 (CEST) | From | Jan Engelhardt <> | Subject | Re: [RFC/PATCH] Documentation of kernel messages |
| |
On Jun 13 2007 12:50, Valdis.Kletnieks@vt.edu wrote: >> In general we think, that also for Linux it is a good thing to have >> documentation for the most important kernel/driver messages. Even >> kernel hackers not always are aware of the meaning of kernel messages >> for components, which they don't know in detail. Most of the messages >> are self explaining but sometimes you get something like "Clocksource >> tsc unstable (delta = 7304132729 ns)" and you wonder if your system is >> going to explode.
I suppose no. If it is going to explode, it will tell you :-)
/* fs/super.c */ printk("VFS: Busy inodes after unmount of %s. " "Self-destruct in 5 seconds. Have a nice day...\n", sb->s_id);
>This is probably best addressed by cleaning up the actual messages so they're >a bit more informative.
Jan -- - 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/
| |