[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#852192: using boot_delay=500 renders system unbootable



Control: severity -1 minor
Control: tag -1 moreinfo

On Sun, 2017-01-22 at 19:47 +0800, 積丹尼 Dan Jacobson wrote:
> Package: src:linux
> Version: 4.8.15-2
> 
> $ cat /proc/cmdline
> BOOT_IMAGE=/boot/vmlinuz-4.8.0-2-amd64 root=UUID=50c0e259-55bb-4fc0-867e-63160edef01f ro single systemd.log_level=debug systemd.log_target=kmsg log_buf_len=262144 enforcing=0 panic=33 earlyprintk=vga
> worked fine. But if boot_delay=500 is added to it,
> all that happens is two lines are printed on the screen, and one has to
> power cycle.

The delay is applied after every line that is logged, whether or not
it's displayed on the console.  I'm fairly sure the system will
eventually boot.  To support your claim that it is hanging, you would
need to verify that e.g. the system has not booted after waiting 5
times as long as it took with boot_delay=100.

Ben.

-- 
Ben Hutchings
For every complex problem
there is a solution that is simple, neat, and wrong.

Attachment: signature.asc
Description: This is a digitally signed message part


Reply to: