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

Bug#960355: marked as done (Invalid serial console blocks system boot)

Your message dated Fri, 15 May 2020 23:48:38 +0100
with message-id <79d76a6cb696073e28d9659460657b46b34a5e26.camel@decadent.org.uk>
and subject line Re: Invalid serial console blocks system boot
has caused the Debian Bug report #960355,
regarding Invalid serial console blocks system boot
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
960355: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960355
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: initramfs-tools-core
Version: 0.137

Putting a serial console on a non-existent/broken serial port
via the last "console=" argument of the kernel command line
causes the initrd to hang without completing the boot process.

If the problematic serial console argument comes first in the kernel
command line, the system boots without issues.


***To reproduce:***

1. Check for a non-connected/disabled serial port.

	On the problematic system running

	[$] stty -a -F /dev/ttyS1
	stty: /dev/ttyS1: Input/output error
The serial ports are registered by the "serial8250" driver but are probably not wired to anything.
2. Boot with a kernel command line that puts serial console on a non-existent/broken serial port via last "console=" argument: 

	console=tty0 console=ttyS1,115200n8


3. Check if system boots successfully
I am using Debian GNU/Linux 11 (bullseye/testing), vanilla kernel 5.7-rc5. 


This issue was initially reported multiple times for Debian and Ubuntu
to the systemd maintainers as:

https://github.com/systemd/systemd/issues/15656  (for Ubuntu)
https://github.com/systemd/systemd/issues/15783  (for Debian, duplicate)


I am not sure if the _exact_ cause of both issues is the same,
because I observed the problem on a very minimal system without
console-setup or kbd.

--- End Message ---
--- Begin Message --- 
On Tue, 12 May 2020 01:20:35 +0200 Jonas Zeiger <jonas.zeiger@talpidae.net> wrote:
> Package: initramfs-tools-core
> Version: 0.137
> 
> Putting a serial console on a non-existent/broken serial port
> via the last "console=" argument of the kernel command line
> causes the initrd to hang without completing the boot process.
>
> If the problematic serial console argument comes first in the kernel
> command line, the system boots without issues.
[...]

The last named console device is what the kernel considers the primary
console, so it really should be a working device.

I don't think this is a bug, so closing.

Ben.
 
-- 
Ben Hutchings
If you seem to know what you are doing, you'll be given more to do.

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


--- End Message ---
Reply to: