Messages in this thread |  | | | Date | Sat, 7 Jan 2006 13:44:39 -0800 | | From | "Kurtis D. Rader" <> | | Subject | Re: oops pauser. / boot_delayer |
| |
On Thu, 2006-01-05 06:11:05, Dave Jones wrote: > On Thu, Jan 05, 2006 at 08:30:16AM +0100, Bernd Eckenfels wrote: > > Randy.Dunlap <rdunlap@xenotime.net> wrote: > > > This one delays each printk() during boot by a variable time > > > (from kernel command line), while system_state == SYSTEM_BOOTING. > > > > This sounds a bit like a aprils fool joke, what it is meant to do? You can > > read the messages in the bootlog and use the scrollback keys, no? > > could be handy for those 'I see a few messages that scroll, and the > box instantly reboots' bugs. Quite rare, but they do happen.
Another very common situation is a system which fails to boot due to failures to find the root filesystem. This can happen because of device name slippage, root disk not being found, the proper HBA driver isn't present in the initrd image, etc. The customer calls us and reports the last thing they see on the screen:
Mounting root filesystem Kmod : failed to exec /sbin/modprobe -s -k block-major-8 , error = 2 mount : error 6 mounting ext3 pivotroot : pivot_root(/sysroot,.sysroot/initrd) failed : 2 Freeing unused memory Kernel panic : No init found . Try passing init= option to kernel
Great! Only problem is the info we really need has already scrolled of the screen. An option to pause briefly after each boot time printk would be very useful. - 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/
|  |