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

2020-09-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Sep 2020 20:36:04 +
with message-id 
and subject line Bug#960355: fixed in initramfs-tools 0.138
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 ow...@bugs.debian.org
immediately.)


-- 
960355: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960355
Debian Bug Tracking System
Contact ow...@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 ---
Source: initramfs-tools
Source-Version: 0.138
Done: Ben Hutchings 

We believe that the bug you reported is fixed in the latest version of
initramfs-tools, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 960...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ben Hutchings  (supplier of updated initramfs-tools package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 11 Sep 2020 20:37:29 +0100
Source: initramfs-tools
Architecture: source
Version: 0.138
Distribution: unstable
Urgency: medium
Maintainer: Debian kernel team 
Changed-By: Ben Hutchings 
Closes: 857054 923400 955469 959768 960355
Changes:
 initramfs-tools (0.138) unstable; urgency=medium
 .
   [ Ben Hutchings ]
   * [0b034b4] docs/maintainer-notes.md: Delete the horizontal rules
   * [ba883cb] docs/maintainer-notes.md: Use Gitlab markup for table of contents
   * [5284a00] docs/maintainer-notes.md: Use Gitlab markup for definition table
   * [a469b7e] docs/maintainer-notes.md: Use archive.org URL for Daniel Baumann
 doc
   * [424260e] debian/control, docs/maintainer-notes.md: Use my @debian.org
 address
   * [181a35c] update-initramfs: Remove test for direct invocation from kernel
 package
   * [6ebe41b] Remove obsolete update-initramfs state in
 /var/lib/initramfs-tools
   * [2f2ad0d] hook-functions: copy_exec: Copy libgcc_s.so with any soversion up
 to 9 (Closes: #959768)
   * [0f24cc1] Add CI configuration for salsa.debian.org
   * [9877542] initramfs.conf: Delete "NFS Section" comment
   * [4309c3b] Add FSTYPE config parameter to allow overriding filesystem type
 detection (Closes: #923400)
   * [6300aa1] Change "panic" parameter handling to work more like the kernel
   * [90d64bd] debian/tests: Add common test preparation code
   * [3dd2984] debian/tests: Add basic test for amd64 using klibc and not
 busybox
   * [69240b1] debian/tests: Add basic test for amd64 using busybox
   * [3d834c8] debian/tests: Add basic tests for amd64 with only ata/virtio
 driver
   * [c14b760] debian/tests: Add test for separate /usr device
   * [6b3b361] debian/tests: Add test of the panic shell and parameter handling
 .
   [ Vagrant Cascadian ]
   * [482897b] hook-functions: Add modules needed for Pinebook LCD display.
 .
   [ Guilherme G. Piccoli ]
   * [c3cbf35] scripts/functions: Prevents 

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

2020-05-15 Thread Debian Bug Tracking System
Your message dated Fri, 15 May 2020 23:48:38 +0100
with message-id <79d76a6cb696073e28d9659460657b46b34a5e26.ca...@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 ow...@bugs.debian.org
immediately.)


-- 
960355: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960355
Debian Bug Tracking System
Contact ow...@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  
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.




signature.asc
Description: This is a digitally signed message part
--- End Message ---