[Bug 1879987] Re: machine get stuck at boot if specified 'console=ttyS* ' doesn't exist.

[Guilherme G. Piccoli]

Let me clarify why I'm un-marking this as duplicate of #1573095. This LP
bug is indeed a duplicate of #1573095, but we have a lot of noise there,
and potentially multiple different issues reported. The main one is the
wrong ttySX causing the infinite loop in initramfs-tools due to error on
write.

Hence, I'll use this LP to do the SRU for Ubuntu initramfs-tools. Also,
worth notice that we have Debian bugs reported [0] and a Merge Request
in Debian Salsa [1], both ignored by the Debian maintainer for 6 weeks.
So, we'll go with Ubuntu fix for now, and hopefully Debian will merge
that in the future.

Cheers,


Guilherme


[0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962545 and https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960355

[1] https://salsa.debian.org/kernel-team/initramfs-
tools/-/merge_requests/30

** Bug watch added: Debian Bug tracker #962545
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962545

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1879987

Title:
  machine get stuck at boot if specified 'console=ttyS* ' doesn't exist.

Status in initramfs-tools package in Ubuntu:
  In Progress
Status in initramfs-tools source package in Trusty:
  Won't Fix
Status in initramfs-tools source package in Xenial:
  In Progress
Status in initramfs-tools source package in Bionic:
  In Progress
Status in initramfs-tools source package in Eoan:
  Won't Fix
Status in initramfs-tools source package in Focal:
  In Progress
Status in initramfs-tools source package in Groovy:
  In Progress

Bug description:
  kernel get stucks at boot if console=ttyS* is specified in the kernel
  cmdline and that serial HW isn't available on the system.

  Reproduced with:
  4.4 (from Xenial), 4.15 (from Bionic), 5.4 (native, Focal) and 5.7-next (mainline)

  Removing the non-existent 'console=ttyS*' parameter fixes the
  situation.

  I tested it using KVM/qemu, but it has been brought to my attention
  that it was reproducible in VMware as well.

  I think it is safe to say that it is unlikely to be specifics to a
  certain virtualization technology type.

  Didn't test on baremetal yet.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1879987/+subscriptions