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

2020-05-21 Thread Eric Desrochers
Related public bugs found here and there:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960355
https://github.com/systemd/systemd/issues/15783
https://github.com/systemd/systemd/issues/15656

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

** Bug watch added: github.com/systemd/systemd/issues #15783
   https://github.com/systemd/systemd/issues/15783

** Bug watch added: github.com/systemd/systemd/issues #15656
   https://github.com/systemd/systemd/issues/15656

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

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

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

2020-05-21 Thread Eric Desrochers
I observed the random kernel spew on my reproducer but I also want to
add that it was also noticed on my VMware impacted contact who brought
this up to my attention at the first place.

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

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

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

2020-05-21 Thread Eric Desrochers
I don't know yet if related, but I also observed the following:

syslog:May 21 17:25:27 ubuntu kernel: [0.00] random: get_random_bytes 
called from start_kernel+0x99/0x4fd with crng_init=0
syslog:May 21 17:25:27 ubuntu kernel: [1.902484] random: lvm: uninitialized 
urandom read (4 bytes read)


Could the missing ttyS* have an effect on entropy ?

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

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

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

2020-05-21 Thread Eric Desrochers
from dmesg (took from virsh dump)

[0.00] Command line: BOOT_IMAGE=/vmlinuz-4.15.0-101-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro console=ttyS4
..
[1.053683] Warning: unable to open an initial console.

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

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

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

2020-05-21 Thread Guilherme G. Piccoli
** Attachment added: "console_issue.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879987/+attachment/5375272/+files/console_issue.txt

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

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

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

2020-05-21 Thread Eric Desrochers
** Changed in: linux (Ubuntu)
   Importance: Medium => High

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

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

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

2020-05-21 Thread Eric Desrochers
** Description changed:

  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*' fixes the situation.
+ 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, but I would suspect the same behaviour (until
  I'm proving wrong).

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

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

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

2020-05-21 Thread Guilherme G. Piccoli
I've managed to reproduce in 4.4, 4.15, 5.4 (all from Ubuntu releases)
and 5.7-rc4-next; also, I think bare-metal usually doesn't reproduce.

Seems like a live-lock situation, I'll attach some calltraces I gathered using 
sysrqs.
Cheers,


Guilherme

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

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

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

2020-05-21 Thread Guilherme G. Piccoli
** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)

** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu)
   Status: New => Confirmed

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

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

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

2020-05-21 Thread Eric Desrochers
** Description changed:

  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, but I would suspect the same behaviour (until
- I'm proving wrong).
+ Didn't test on baremetal yet.

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

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

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs