[Expired for linux-azure (Ubuntu) because there has been no activity for
60 days.]
** Changed in: linux-azure (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
** Changed in: linux-azure (Ubuntu)
Assignee: Colin Ian King (colin-king) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1822118
Title:
Kernel Panic
please reopen if this is still an issue
** Changed in: systemd (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1822118
Title:
@Finom, that's a good observation, much appreciated.
** Changed in: systemd (Ubuntu)
Importance: Undecided => High
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
** Description changed:
- Description: In the event a particular Azure cloud
Hello,
I get similar "Kernel panic" after running the following codes and
restarting the VM:
sudo gedit /etc/ld.so.conf.d/glibc_2.29.conf
And adding the full path to the library as instructed here:
https://stackoverflow.com/a/13428971
Serial log attached.
** Attachment added:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
And for Standard_D2s_v3
IP addr Mac AddrKernel Reboots
104.42.252.54 00:0d:3a:32:df:92 5.0.0-1020-azure500
104.42.150.26 00:0d:3a:31:1b:50 5.0.0-1020-azure500
104.42.147.144 00:0d:3a:32:d8:2f 5.0.0-1020-azure500
40.112.129.232
@Joseph, so I can reproduce this hang/crash issue across a variety of
instances. I can't get any info back on a console, so debugging this is
not easy.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Get more failures with Standard_B1ms
IP addr Mac AddrKernel Reboots
52.160.101.11 00:0d:3a:5b:a0:7c 5.0.0-1020-azure10
137.135.51.101 00:0d:3a:31:20:fc 5.0.0-1020-azure500
137.135.50.133 00:0d:3a:31:27:0f 5.0.0-1020-azure396 [hang]
I kicked off another ~20K reboot tests with Standard_B2S instances and
hit hangs again:
IP addr Mac AddrKernel Reboots
104.42.3.16100:0d:3a:37:82:ee 5.0.0-1020-azure100
13.91.5.23 00:0d:3a:5a:74:23 5.0.0-1020-azure57
So the best way to reproduce this issue is to run ~500 reboots across
multiple instances rather than 5000-1 reboots on once instance.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
See above, I ran several thousand reboot tests on a lot of Basic_A3
instances, ranging from 50, 250 to 500 reboots. Only one failed. So
this is *really* hard to reproduce.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
IP addr Mac AddrKernel Reboots
13.64.67.18600:0d:3a:3a:dd:04 5.0.0-1016-azure50
104.42.152.115 00:0d:3a:35:b1:e6 5.0.0-1016-azure50
65.52.121.205 00:0d:3a:3b:0f:52 5.0.0-1016-azure50
13.88.28.42 00:0d:3a:3b:c7:da
@Robert, was there a specific class of virtual machine you were using
when this issue occurred?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1822118
Title:
Kernel Panic
** Changed in: linux-azure (Ubuntu)
Status: In Progress => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1822118
Title:
Kernel Panic while rebooting
@Joseph, any ideas how we can progress on this?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1822118
Title:
Kernel Panic while rebooting cloud instance
Status in
I can confirm this bug. My VPS servers are configured to automatically
reboot daily and one of them started hanging up with similar error a few
days ago. I am using Ubuntu 18.10 x64 running on Vultr VPS. When the VPS
hanged today, the screen ended with these messages:
[ OK ] Reached target
I still haven't been able to reproduce this. If you can reproduce this
easily, maybe I can provide some kernels to be tested?
I'll keep trying to reproduce here. I compared my VM settings to why is
in the bug description, and I have the same config, except the region.
I wouldn't think that
I modified your script to perform 5000 reboots. I'm up to 3508 reboots
now without hitting the bug. I'll let it run for a while longer. I'll
also compare our environments to see if there is a difference.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
** Tags added: id-5c9e3d984ba1ad4df84a6b1c
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1822118
Title:
Kernel Panic while rebooting cloud instance
Status in
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1822118
Title:
Kernel Panic while rebooting
21 matches
Mail list logo