On Sat, 2006-01-07 at 13:44 -0800, Kurtis D. Rader wrote:
> 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 <[email protected]> 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
mount by label fixes some of that but not all
> the initrd image, etc. The customer calls us and reports the last thing they
> see on the screen:
fwiw it would make sense (at least for distros) to make this print a
more helpful text about potential causes etc, rather than just making
people say "the kernel paniced".
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
