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 er
@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
Titl
@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 In
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' '
@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.
https://bugs.launchpad.net/bugs/1822133
I can confirm the fix is included in the kernel "4.4.0-152.179":
https://kernel.ubuntu.com/git/ubuntu/ubuntu-
xenial.git/tree/include/linux/hyperv.h?h=Ubuntu-4.4.0-152.179
I installed the kernel, did some network tests, and it worked fine for
me:
#apt-get install linux-image-4.4.0-152-generic
#re
When the issue happens, there is no error message in dmesg or syslog,
and it's just the host side NetVSP driver stops reading from the guest-
to-host ring, and the guest network stops working. So we don't really
have any logs to provide here.
--
You received this bug notification because you are
I guess you might have already included this patch:
15becc2b56c6 ("PCI: hv: Add hv_pci_remove_slots() when we unload the
driver")
Unluckily it turns out it is buggy and just now I had to post a further patch
for it:
[PATCH] PCI: hv: Fix panic by calling hv_pci_remove_slots() earlier
This is the screenshot of the graphic artifact mentioned in the previous
comment.
** Attachment added: "graphic_artifact.png"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1848534/+attachment/5352858/+files/graphic_artifact.png
--
You received this bug notification because you are a me
Today I installed a Generation-2 VM (4 virtual CPUS, 4 GB memory) from the this
.iso file:
http://releases.ubuntu.com/19.10/ubuntu-19.10-desktop-amd64.iso.
My host is Win10: Version 1909 (OS Build 18383.720) -- I got the info by
running the built-in "winver.exe" program.
The CPU type is Intel C
BTW, my Linux kernel version is 5.3.0-46-generic #38-Ubuntu (17:37:05,
3/27/2020).
The "graphic artifact" is somehow caused by the "$vt_hanoff" kernel parameter
(check "cat /proc/cmdline").
If I manually remove the "$vt_hanoff" at the grub screen, I won't see the
"graphic artifact" -- Ubuntu gu
@msgallery: BTW, you mentioned 'The "restart" button is not functional'
-- actually it is not functional only when we try to click the button by
mouse -- if we press Tab to focus on the button and then press Enter,
the VM should reboot. :-) I'll try to mention this to Hyper-V team, but
I'm not sur
Today I installed a Generation-1 Ubuntu 20.04 VM on my local Hyper-V
host from the ISO file: https://releases.ubuntu.com/20.04/ubuntu-20.04
-live-server-amd64.iso (released on 4/23/2020) and I don't see this bug
and the grub version is 2.04-1ubuntu26.
Today I also created a VM on my host from http
Sorry, this statement is wrong:
==
Today I also created a VM on my host from
https://cloud-images.ubuntu.com/focal/20200430.1/focal-server-cloudimg-amd64-azure.vhd.zip
and can not see the bug either, and the grub version is also 2.04-1ubuntu26.
Today I just repeated the test "Create a Gen-1 Ubuntu 19.10 VM on Azure,
and upgrade it to Ubuntu 20.04 by “do-release-upgrade –d" and I
reproduced this bug again, and the grub version is also 2.04-1ubuntu26!
So I suspect grub itself should be good, but some grub config file (i.e.
/etc/grub.d/10_
I think commen #6 is correct: it looks the 2018 patch introduced the
issue for us, but the patch is originally for "initrd-less boot
capabilities." and here we do need the initramfs file.
I guess the patch "ubuntu-add-initrd-less-boot-fallback.patch" is not
included into the grub shipped in the 20
Anyone knows who maintains the grub package shipped in the cloud-images?
Should we report a bug at https://bugs.launchpad.net/ubuntu/+source/grub2 ?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launch
> If someone is using a kernel other than the one we provide for the
cloud, or in the case of a bug, the system will still boot (slower)
after a panic and a reboot to try again with the initrd.
Hi Steve, I guess you assume the pattern is
"panic/success/success/success/...", but actually the patter
BTW, the symptom described in the Bug Description also exists in the
Ubuntu 20.04 image in Azure Marketplace.
--
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/1870189
Title:
initramf
Hi Marcelo, I'm not sure which v5.3 kernel you mean -- the v5.3 in
Ubuntu 19.10, v5.4 in Ubuntu 20.04 or the upstream stable tree's v5.3
and newer? :-)
Here we need to make sure the 3 patches in the Bug Description are
included, and also make sure the line "if (list_empty(&hbus->children))
hbus->s
It looks #48 shows some service is causing the long delay -- can you try
'systemctl list-jobs' to see active jobs, as the "Hint" says? :-)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/184
I created a Ubuntu 19.10 VM via "Quick Create..." and still can not
reproduce the long delay of > 1 minute: the VM can boot up to the Xorg
GUI desktop in 26 seconds.
My Windows 10 has the same version info: Version 1909 (OS Build
18363.778).
At the grub screen, can you press 'e' and, manually edi
I agree with David. IMO this bug should be fixed ASAP. Thanks!
--
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/1870189
Title:
initramfs does not get loaded
Status in grub2 package
Sorry, I did miss this part of your previous reply:
root@stock19:~# systemctl list-jobs
JOB UNIT TYPE STATE
48 setvtrgb.service start waiting
137 system-getty.slice start waiting
1 graphical.target start waiting
102 systemd-update-utmp-runlevel.service start waiting
83 plymouth-quit-wait.servi
I also tried xrdp mode and the VM booted up to the xrdp login window in
14 seconds, which is faster than the "native Xorg GUI mode" (which needs
30s)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.n
Since Alt-SysRq-w gives nothing, I'm sure the long delay is not a
kernel/driver issue but a user space issue. It looks due to some reason
I just can not reproduce the long delay. :-(
In the Hyper-V Virtual Machine Connection window's "View" menu, there is
an item "Enhanced Session". In my Ubuntu 1
Sorry, I made a typo above: systemd.dsystemd.default_standard_output=kmsg ==>
systemd.default_standard_output=kmsg.
BTW, it looks systemd.show_status=true makes no difference for me. I don't see
any status info during the boot-up time -- not sure if I did something wrong.
--
You received this b
I don't have much knowledge bout systemd, either :-) I just did a "man
systemd" and found the options of systemd. "man systemd" says that we
can use pass these kernel parameters to systemd:
systemd.service_watchdogs=true systemd.show_status=true
systemd.log_level=debug systemd.dsystemd.default_st
Thanks for the reminder! I just realized Ubuntu 20.02 was already
released on 4/23. We should try it.
For the CPU firmware (CPU microcode?) update issue: sorry, it's
completely out of my scope -- I only work on Linux. Hopefully that issue
will be resolved in the near future.
--
You received this
When the bug was originally reported on Apr 1, "We installed a Ubuntu
20.04 VM from the .iso file from http://cdimage.ubuntu.com/daily-
live/pending/ and don’t see the strange grub issue". It looks the grub
version used in the .iso file (on Apr 1) does not have the bug.
I don't think the patch in
So it looks this is considered as a feature rather than a bug for the
Ubuntu 20.04 VM image in Azure Marketplacet. To whoever uses such an
image on Azure: if you're installing a new kernel that doesn't have the
necessary drivers built-in (CONFIG_HYPERV=y, CONFIG_HYPERV_STORAGE=y),
you're supposed t
There is another important bug fix for hibernation:
net/mlx5: Fix crash upon suspend/resume
(https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=8fc3e29be9248048f449793502c15af329f35c6e).
So far the fix is only present in the net.git tree, but I expect it will
be in the mai
FYI: the patch "net/mlx5: Fix crash upon suspend/resume" is in v5.7 now
(i.e. today's latest mainline):
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.7&id=8fc3e29be9248048f449793502c15af329f35c6e
--
You received this bug notification because you are a member of K
Hi M, I can not reproduce the issue: just now I downloaded
http://dt0cinyuc0rrg.cloudfront.net/ubuntu-19.10-desktop-amd64.iso and
created a Generation-2 VM on Hyper-V with the .iso file. The VM boots up
fast: it boots up to the Xorg desktop in 28 seconds with 1 CPU and 2GB
memory, and in 21 seconds
I'm not sure what exact issues you're reporting.
Your VM takes too much time to boot up? How long? "systemd-analyze
blame" should collect the info for your VM.
Your VM's screen is somehow messed up temporarily during the boot-up
process? Or the boot-up process is stuck in the "text cursor" scree
Hi M, since I can not reproduce the delay issue, I don't know what I can
do now. :-(
Do you think if it's related to Xorg?
Can you install a new VM from scratch from the server .iso
(http://releases.ubuntu.com/19.10/ubuntu-19.10-live-server-amd64.iso)
and see if you can reproduce the same issue?
The typical boot-up time of my Ubuntu VM on Hyper-V is 20~30 seconds for
a Desktop version of Ubuntu, and 10~20 seconds for a Server version. I
tried Ubuntu 19.04 just now and it also took 20+ seconds.
I never achieve a boot-up time of 2s.
I do know Ubuntu can boot up fast in 2~3 seconds in WSL (
Can Ubuntu devs please try to repro the issue? I can not repro it. :-(
Hi M, I assume you can also repro the issue with a VM created from
scratch from the server .iso (see comment #28) with a minimal
installation? If yes, can you please share the vhdx file? If you
configure the disk size to 15GB a
So let me summarize your findings on the same host of yours (I suppose
your VMs use the same config for the number of vCPUs and the memory
size. I also suppose you only tested Hyper-V Generation 2 VMs or you
confirmed Gen-1 vs. Gen-2 makes no difference):
("fast" means you can see the GUI desktop
@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] ip_fr
4.15.0-1022 (https://git.launchpad.net/~canonical-kernel/ubuntu/+source
/linux-azure/tree/drivers/net/hyperv/netvsc.c?h=master-next&id=Ubuntu-
azure-4.15.0-1022.22_16.04.1) does NOT have the fix
(6b81b193b83e87da1ea13217d684b54fccf8ee8a).
I'm not sure why the bug status was changed to Fix Committe
Thanks, Marcolo!
--
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/1786313
Title:
[Hyper-V] hv_netvsc: Fix napi reschedule while receive completion is
busy
Status in linux-azure pa
I guess we can close the bug now?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1777128
Title:
[Hyper-V] patches for SR-IOV post-bionic GA
Status in linux package in Ubuntu:
Fix Comm
ernel/git/next/linux-next.git/commit/drivers/hv?h=next-20181126&id=4a5f3cde4d51c7afce859aed9d74d197751896d5
From: Dexuan Cui
We can concurrently try to open the same sub-channel from 2 paths:
path #1: vmbus_onoffer() -> vmbus_process_offer() -> handle_sc_
More patches are required: https://lkml.org/lkml/2018/11/2/182
It looks we'll have to wait for some time, before the kernel stabilizes...
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1792
Thanks, Marcelo! I tested all the 3 kernels and they worked as we
expected.
--
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/1902531
Title:
[linux-azure] IP forwarding issue in netvs
I can confirm now hibernation can work with 5.4.0-1023, despite a
harmless warning:
root@decui-tmp-2004:~# echo disk >/sys/power/state
[ 56.945758] PM: hibernation entry
[ 57.165520] Filesystems sync: 0.007 seconds
[ 57.169492] Freezing user space processes ... (elapsed 0.001 seconds) done.
Public bug reported:
There are failed logs after resume from hibernation in NV6 (GPU passthrough
size) VM in Azure:
[ 1432.153730] hv_pci 47505500-0001--3130-444531334632: hv_irq_unmask()
failed: 0x5
[ 1432.167910] hv_pci 47505500-0001--3130-444531334632: hv_irq_unmask()
failed: 0x5
Th
Public bug reported:
Description of problem:
On Azure, if the VM is Stopped(deallocated) and later Started, the VF NIC's
VMBus Instance GUID may change, and as a result hibernation/resume can hang
forever.
This happens to the latest stable release of the linux-azure
5.4.0-1023.23 kernel and the
Public bug reported:
Description of problem:
In a VM with CX4 VF NIC on Azure, after hibernation/resume, the TX/RX packet
counters stop increaseing.
This issue doesn't exist in VM with a CX3 VF NIC.
This happens to the latest stable release of the linux-azure
5.4.0-1023.23 kernel and the latest
We also need the second and the third patch:
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=de214e52de1bba5392b5b7054924a08dbd57c2f6
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=da26658c3d7005aa67a706dceff7b2807b59e123
--
You received this
rcu_access_pointer(sk->sk_filter) is basically the same as
sk->sk_filter.
If sk->sk_filter is true, the change makes no difference.
If sk->sk_filter is false, the change also drops a UDP packet with incorrect
UDP checksum by "goto csum_error;". Without the change, the packet is dropped
in udp_re
https://lore.kernel.org/netdev/20200728015505.37830-1-de...@microsoft.com/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1888715
Title:
UDP data corruption caused by buggy udp_recvmsg()
Unluckily this commit breaks hibernation:
0a14dbaa0736 ("video: hyperv_fb: Fix hibernation for the deferred IO feature"):
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-azure/+git/focal/commit/?h=Ubuntu-azure-5.4.0-1022.22&id=0a14dbaa0736a6021c02e74d42cf3a7ca5438da6
We should inc
The fix is in the PCI tree now:
"PCI: hv: Fix hibernation in case interrupts are not re-create" (
https://git.kernel.org/pub/scm/linux/kernel/git/lpieralisi/pci.git/commit/?h=pci/hv&id=915cff7f38c5e4d47f187f8049245afc2cb3e503
)
--
You received this bug notification because you are a member of K
The fix is in the mainline kernel now:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=19873eec7e13fda140a0ebc75d6664e57c00bfb1
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bu
Hyper-V team just identified a bug where the Hyper-V hypervisor can
truncate the host SYSENTER_ESP/EIP to 16 bits on VMexit for some reason.
A further investigation is ongoing.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in
VM Exit is a term in the Intel CPU's Virtualization support (VMX). It
means the execution of the guest CPU is interrupted and the execution
"jumps" to some function in the hypervisor; the hypervisor analyzes the
reason of the VM Exit, and handles the VM exit properly, and then the
execution "jumps"
VM exits are pretty frequent and normal. "VM exits occur in response to certain
instructions and events in VMX non-root operation" (see CHAPTER 27
VM EXITS of
https://software.intel.com/content/www/us/en/develop/download/intel-64-and-ia-32-architectures-sdm-volume-3c-system-programming-guide-part
Sure, will do. But AFAICT, there is no ETA yet. Even if the fix was made
today, it would take quite some time (at least a few months?) to deploy
the fix to the whole Azure fleet. :-(
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-az
Unluckily this commit breaks hibernation:
0a14dbaa0736 ("video: hyperv_fb: Fix hibernation for the deferred IO feature"):
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-azure/+git/focal/commit/?h=Ubuntu-azure-5.4.0-1022.22&id=0a14dbaa0736a6021c02e74d42cf3a7ca5438da6
The kernel he
To reproduce the issue, I created a Ubuntu 20.04 VM on Azure (the kernel
version was "5.4.0-1022-azure #22-Ubuntu"), and I ran "echo disk >
/sys/power/state" in the VM and then checked the Azure serial console of
the VM and found the warning in commen #8 and suspending couldn't finish
normally (it
Hi Marcelo, yes, please revert
0a14dbaa0736 ("video: hyperv_fb: Fix hibernation for the deferred IO feature").
No other change is needed.
In the future, when a4ddb11d297e is included, 0a14dbaa0736 should also
be included.
--
You received this bug notification because you are a member of Kernel
Detailed steps to repro the issueo on Azure:
1. Create a VM with the image "Ubuntu Server 20.04 LTS - Gen1". Any VM size
should be fine. Here I use "Standard E4-2ds_v4 (2 vcpus, 32 GiB memory)".
2. Add an extra disk of 64GB to the VM via Azure portal.
3. Login the VM via ssh and check the kernel
FYI: the fix is in the upstream linux-4.4.y branch now:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v4.4.233&id=c514bb4147e2c667cf82f9aa7689cf442078c13f
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux i
I'll provide the instructions to reproduce the bug on 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/1902531
Title:
[linux-azure] IP forwarding issue in netvsc
Status in li
Since the 5.0 linux-azure kernel is not maintained anymore, IMO we don't
have to fix this bug for it.
--
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/1902531
Title:
[linux-azure] IP
Here is how I reproduce the bug:
Create 3 Ubuntu 16.04 VMs (VM-1, VM gateway, VM-2) on Azure in the same
Resource Group. The kernel should be the linux-azure kernel
4.15.0-1098.109~16.04.1 (or newer). I use Gen1 VM but Gen2 should also
has the same issue; I use the "East US 2" region, but the iss
To use Azure UDR, I referred to this page:
https://campus.barracuda.com/product/cloudgenfirewall/doc/72516173/how-
to-configure-azure-route-tables-udr-using-azure-portal-and-arm/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure
This is the network config. Let me know if you need more info.
** Attachment added: "network-config.png"
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1902531/+attachment/5430820/+files/network-config.png
--
You received this bug notification because you are a member of Kernel
P
People are working on this issue: e.g. it looks the patch may work around it:
https://patchwork.kernel.org/patch/10012603/ (it would be great if somebody can
test the patch)
Long will send one more patch:
https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1517902.html
--
You receive
@fastlanejb are you on Windows Server 2012 R2 or 2016? Is your VM
running some I/O intensive workload when the live backup happens? It
looks you get the OOM issue every time you do the live backup? I'm
digging into the issue, and trying to reproduce it first.
--
You received this bug notification
The patch has been in the mainline tree:
https://github.com/torvalds/linux/commit/e89ce1f89f62c7e527db3850a91dab3389772af3
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1713884
Title:
[
First I created a Ubuntu 16.04 VM on Azure, which could reproduce the bug, and
"uname -a" showed:
Linux decui-u1604-hwe 4.4.0-92-generic #115~14.04.1-Ubuntu SMP Thu Aug 10
15:06:53 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
I installed the xenial/, and confirmed it resolved the bug:
Linux decui-u16
I read through the long bug log and found an interesting thing:
In #36, Andrey Vertexx (vertexx) reported the issue was fixed by the
kernel in #30, but later Andrey thought the same kernel couldn't work
any more?
In #47, #48, #54, #59 a lot of people , Aleksey (noirfry) , Khallaf
(mkhallaf), E
@jrp, it looks the patch in comment #26 is unrelated to this bug?
The patch is for cxlflash (Support for IBM CAPI Flash), which doesn't exist in
a VM running on Hyper-V.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
htt
I happened to see this bug and want to add one more patch:
https://git.kernel.org/cgit/linux/kernel/git/helgaas/pci.git/commit/?h=pci/host-hv&id=60e2e2fbafdd1285ae1b4ad39ded41603e0c74d0
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
@Joshph
Can you please confirm the patch
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1665097/comments/4) is
included in the test kernel in #25?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launc
@Joshph, "the test kernel in #25" means the #4 in the link of #25,
i.e. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667007/comments/4
It looks to me the patch is not included. Just want to confirm my guess.
--
You received this bug notification because you are a member of Kernel
Packag
Thanks, Joseph!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1650058
Title:
[Hyper-V/Azure] Please include Mellanox OFED drivers in Azure kernel
and image
Status in linux package in
It turns out the issue also exists in the latest mainline kernel!
The fix "x86, pageattr: Prevent overflow in slow_virt_to_phys() for X86_PAE" is
there, but a later patch "x86/mm: Fix slow_virt_to_phys() to handle large PAT
bit"
(https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/
My update:
It looks the issue is somehow related to the backup, but I tend to think there
is a bug somewhere in the storvsc driver code -- it's very hard to track it
down because before the ext4 read-only issue happens, the ext4 file system may
have been somewhat corrupted.
--
You received t
Sorry, I was moved to another project so I couldn't debug the issue with
full-time.
Hi Joshua R. Poulson (jrp), can you please find more resource for this
bug?
My previous debugging made me think the root cause might be in the
storvsc driver code, but unluckily I'm not an expert in that area. :-
The root cause of the bug is:
Ubuntu 14.10(I'm using the daily build of Aug 27 ) blacklists hyperv_fb:
/etc/modprobe.d/fbdev-blacklist.conf: blacklist hyperv_fb
Is there a reason?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
I believe it’s a configuration issue:
If we use the default Ubuntu kernel as the ”dump capture kernel“[1], we
need to reserve more memory – the default 128MB, generated by the linux-
crashdump post-install script, is not enough, causing a -ENOMEM
failure/BUG in a function of tree_plugin.h.
This i
FYI: another colleague confirmed the above finding:
"
I looked into it and I can confirm the finding.
Tested on Ubuntu 1410
Linux ubuntu 3.16.0-9-generic #14-Ubuntu SMP Fri Aug 15 15:03:57 UTC 2014
x86_64 x86_64 x86_64 GNU/Linux
VMname: ubuntu1410
With the default crashkernel=128M@64M w
FYI: the patches have been merged into Linus's tree:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=45d727cee9e200f5b351528b9fb063b69cf702c8
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=b29ef3546aecb253a5552b198cef23750d56e1e4
--
You recei
This is caused by a bug kernel API used by recent hyper-v synthetic
network driver in Ubuntu 14.04 (Ubuntu 13.10 is not affected).
This only affects 32-PAE Linux VM when the VM has more-than-about-4GB
memory.
I have fixed the issue:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/
This turns out a host issue:
https://bugzilla.redhat.com/show_bug.cgi?id=1052743#c31
Anyway, it's a minor issue.
So let's wait for the host update (the next release :-)
** Bug watch added: Red Hat Bugzilla #1052743
https://bugzilla.redhat.com/show_bug.cgi?id=1052743
--
You received this bug
ext2.ko itself does support fsfreeze, but typical linux distros, like
Ubuntu, don't supply ext2.ko at all now -- instead, they usually supply
ext3.ko and have ext4 built-in.
So when we mount an ext2 partition, actually the kernel is registering
the ext4 driver as an ext2 driver and in this case th
The patch has been in the mainline tree:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=30467e0b3be83c286d60039f8267dd421128ca74
Can Ubuntu people please check if the patch has been included in Ubuntu?
--
You received this bug notification because you are a member of
@f-bosch Hi Frederik, we're really sorry that this backup-can-cause-
filesystem-remounted-readonly issue has been there for long time! We
definitely want to get it fixed as soon as possible. Unluckily according
to my understanding of the long thread here, I think we had difficulty
trying to reprod
@f-bosch Hi Frederik, about the second issue you mentioned ("The more
data getting on the disk, the higher the spikes are...requests that
involve write operations tend to have these characteristics") in #54,
it looks there is a storage I/O performance downgrade somehow.
Do you think if it's relat
Frederik, Thanks for the new information!
About the I/O perf downgrade:
1. I don't think more occupied disk space should harm the perf so greatly (http
resopnse time: from <100ms to several seconds).
2. The perf downgrade appeared recently but the backup issue appeared
long long ago. Why do you
Thanks @f-bosch for your clarification in #62. So my understanding is:
the (temporary) I/O downgrade during the period of backup might be
caused by the fact the disk space has been almost used up (?) recently,
but it also might be somehow related to the backup. Let's focus on the
backup issue at
@f-bosch @jsalisbury
I can reproduce the issue consistently within 5~6 hours with a Ubuntu 15.10 VM.
In /var/log/syslog, several minutes before the file system is remounted
as read-only, the hv_vss_daemon has stopped working: the daemon just
always hangs on the poll() , not receiving freeze/thaw
> "BTW, Since Ubuntu 15.04's "
typo.. 15.04 -> 15.10.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1470250
Title:
[Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based
B
I suspect the race condition may be in vss_on_msg() with the non-thread-
safe variable vss_transaction.state.
And I guess the below patch may have fixed the issue (the patch hasn't be in
the upstream yet):
http://lkml.iu.edu/hypermail/linux/kernel/1510.3/04218.html
I can only test the patch tomo
The patch mentioned in #72 can't help -- still bad luck. :-(
But I can confirm: before the issue happens, somehow athe host doesn't send us
freeze/thaw commands any longer.
we need further debugging...
--
You received this bug notification because you are a member of Kernel
Packages, which is s
When the issue happens (it looks due to the layout of the struct somehow...),
can you try the small workaround patch at
https://patchwork.ozlabs.org/patch/518469/?
I paste it below:
diff --git a/include/linux/netdevice.h b/include/linux/netdevice.h
index 88a0069..7233790 100644
--- a/include/li
1 - 100 of 111 matches
Mail list logo
