Indeed, the commit is in in 4.15.0-1057 and has been released. Marking
this bug as fixed released.
commit b502cfeffec81be8564189e5498fd3f252b27900
Author: Taehee Yoo
Date: Wed Sep 4 14:40:49 2019 -0300
ip: frags: fix crash in ip_do_fragment()
BugLink:
"ip: frags: fix crash in ip_do_fragment()" is in 4.15.0-1057 in proposed
right now for a separate issue.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1822133
Title:
Azure
@Vald: This is from your attachment:
[21965.367843] kernel BUG at
/build/linux-azure-njdnVX/linux-azure-4.15.0/net/ipv4/ip_output.c:636!
[21965.377590] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.15.0-1056-azure
#61-Ubuntu
[21965.435777] RIP: 0010:ip_do_fragment+0x571/0x860
[21965.435777]
Hi,
We got this issue many times last week even after redeploying VM (i.e
moving it to another physical host)!
Attached is the serial log with the kernel panic.
** Attachment added: "Serial log with the Kernel panic"
** Changed in: linux-azure (Ubuntu)
Status: In Progress => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1822133
Title:
Azure Instance never recovered during
@rnsc: Can you please share the VM's full serial log, which can be
obtained from Azure portal's Boot Diagnostics -> Serial log?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
@rnsc, what kernel were you using?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1822133
Title:
Azure Instance never recovered during series of instance reboots.
Status in
Hello, I noticed the same behavior on one of my Azure VM.
It wasn't rebooted thought, it just started blurting out "hyperv_fb" errors in
a loop. (that's all I could display in the Serial Console on Azure, even
sending SysRq to reboot the machine wasn't doing anything, I was forced to
@sfeole, checking with our devops folks. I don't have Azure access to
the hosts in question.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1822133
Title:
Azure Instance never
@tom-wilberding Hey Tom, are you able to capture the console logs of
the instance when this occurs?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1822133
Title:
Azure Instance
It looks like people are resolving this by upgrading to latest Disco
with 5.0.0-1007.7 kernel?
We are on 18.04.1 LTS and having similar symptoms. Is there a fix in the
works for 18.04.1?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
@Dexuan, the error 'WARNING ExtHandler CGroup walinuxagent.service:
Crossed the Memory Threshold' started when the vm was first created on
May 24, persisted until I stopped/dealocated the VM, and has not
returned in syslog. Nor for what it's worth has this error been seen in
over six months on
I rebooted our VM over 60 times today without any further issues. Since
the VM network went down before I restarted the VM or lost access to the
serial console login, I'm also thinking now it was a network issue to
begin with. It could always be coincidence that I was able to get the VM
back by
I tried to reproduce the bug but couldn't.
My Ubuntu 18.04 VM (in West US 2, the VM size is: Basic A3 (4 vcpus, 7
GiB memory)) is still running fine, after I rebooted the VM 100 times
with the below /etc/rc.local script:
#!/bin/bash
date >> /root/reboot.log
NUM=`wc -l /root/reboot.log | cut -d'
On 5/29/19 6:58 PM, Sean Feole wrote:
> I revisited this particular problem today. I ran a series of restart
> tests across westus2 and westus, utilizing the same instance and
> series, but with the latest kernel in -proposed. I was unable to
> reproduce this problem as originally reported in
I see now 5.0.0-1007.7 is also available for 19.04, but I'll wait and
see what you advise @Dexuan after looking at my serial log.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
I got the VM back by force stopping, then starting. It looks like
5.0.0-1007.7 only comes with 19.10, which is not available yet on Azure?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
How do I upgrade the kernel to 5.0.0-1007.7 if that is what is
recommended to avoid this issue? apt-get dist-upgrade on another vm with
4.18.0-1018-azure did not upgrade the kernel. Thank God it restarted! Or
is 5.0.0-1007.7 not an Azure kernel so I would need to switch to stock
Ubuntu kernel?
@Dexuan I emailed you my serial log. I restarted via portal a number of
times without success. I tried to redeploy twice and it failed. Trying
to restart via cli now.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
@Kirk: I suppose you can get your VM back by Restarting the VM by force
via Azure Portal (or Azure cmd line)?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1822133
Title:
Azure
@Kirk: Can you please share the VM's serial log, which can be obtained
from Azure portal's Boot Diagnostics -> Serial log?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1822133
kernel is 4.18.0-1018-azure
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1822133
Title:
Azure Instance never recovered during series of instance reboots.
Status in linux-azure
This bit me tonight on a few days old 18.04 VM with stock kernel. So far
I can not get back in with reboot or redeploy to upgrade the kernel.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
It's glad to see the issue can not repro with the 5.0.0-1007.7 kernel.
@sfeole: The line "[ 84.247704]hyperv_fb: unable to send packet via
vmbus" usually means the VM has panicked. Do you happen to still keep
the full serial log containing this line of error? It would be good to
understand this
Test Parameters for comment #4
Series: Disco
Regions: westus2 & westus
Instance: Basic_A3
Kernel: 5.0.0-1007.7
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1822133
Title:
Azure
I revisited this particular problem today. I ran a series of restart
tests across westus2 and westus, utilizing the same instance and
series, but with the latest kernel in -proposed. I was unable to
reproduce this problem as originally reported in the bug. I also have
not seen any of our SRU
walinuxagent is a package from the Ubuntu repository, but the upstream
is here: https://github.com/Azure/WALinuxAgent
The error message is seen in line 884 here:
https://github.com/Azure/WALinuxAgent/blob/ce58412bc50cee1d066bd01f0e52ad89d75f1a0d/azurelinuxagent/common/osutil/default.py
Likely
** Tags added: kernel-hyper-v
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1822133
Title:
Azure Instance never recovered during series of instance reboots.
Status in
I believe the "ERROR ExtHandler /proc/net/route contains no routes" is
from the "Azure Linux Agent", so that's proprietary code that I don't
have any idea how or why it is emitting that message.
--
You received this bug notification because you are a member of Kernel
Packages, which is
The "hyperv_fb: Unable to send packet via vmbus" message is from
synthvid_send(), drivers/video/fbdev/hyperv_fb.c (the Microsoft Hyper-V
Synthetic Video Frame Buffer Driver). This error occurs when
vmbus_sendpacket() fails to send a packet via the write ring buffer (see
hv_ringbuffer_write())
** Changed in: linux-azure (Ubuntu)
Importance: Undecided => High
** Changed in: linux-azure (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
** Description changed:
Description: During SRU Testing of various Azure Instances, there will
be some cases where the instance will not respond following a system
reboot. SRU Testing only restarts a giving instance once, after it
preps all of the necessary files to-be-tested.
32 matches
Mail list logo
