[Kernel-packages] [Bug 1831268] Re: Ubuntu 19.04: Random SR-IOV issues
This issues is due to a test case bug. Please close. ** Changed in: linux-azure (Ubuntu) Status: New => Invalid -- 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/1831268 Title: Ubuntu 19.04: Random SR-IOV issues Status in linux-azure package in Ubuntu: Invalid Bug description: No VFs inside the VM. Unfortunately this issue doesn’t have a 100% repro. Sometimes all the VFs are missing, other times a few are available and the rest are missing. The best test case to catch this issue is VERIFY-ENABLE-DISABLE-SRIOV- ON-EXISTING-VM. Comparing the logs between working/not working VMs, the only difference was that these 2 messages were missing from the broken VMs: mlx4_en: rename9: Steering Mode 2 mlx4_en: rename9: Link Up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1831268/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835322] Re: [linux-azure] panic in ext4_resize_fs() found during storage testing
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
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/1835322
Title:
[linux-azure] panic in ext4_resize_fs() found during storage testing
Status in linux-azure package in Ubuntu:
Confirmed
Status in linux-azure source package in Xenial:
Fix Committed
Status in linux-azure source package in Cosmic:
Fix Committed
Bug description:
A panic was observed during file system testing. The trace is the
following:
[ 8783.243586] kernel BUG at
/build/linux-azure-3iFJ9j/linux-azure-4.18.0/fs/ext4/resize.c:266!
[ 8783.252751] invalid opcode: [#1] SMP PTI
[ 8783.256735] CPU: 7 PID: 39476 Comm: resize2fs Not tainted
4.18.0-1023-azure #24~18.04.1-Ubuntu
[ 8783.256735] Hardware name: Microsoft Corporation Virtual Machine/Virtual
Machine, BIOS 090007 06/02/2017
[ 8783.256735] RIP: 0010:ext4_resize_fs+0x73b/0xf10
[ 8783.256735] Code: 50 ff ff ff 41 8b 75 10 4d 8b 65 00 85 f6 0f 94 c0 4d 85
e4 0f 94 c1 09 c8 83 bd 5c ff ff ff 01 7e 48 84 c0 0f 84 43 06 00 00 <0f> 0b 48
c7 c2 68 a7 8d 8f 48 c7 c6 00 fb 88 8f 4c 89 f7 e8 0d f8
[ 8783.256735] RSP: 0018:984e8dce7cb0 EFLAGS: 00010202
[ 8783.256735] RAX: 00205c01 RBX: 001f RCX:
[ 8783.256735] RDX: 8b1dbe1367d0 RSI: RDI:
[ 8783.256735] RBP: 984e8dce7d88 R08: 984e8dce7d4c R09:
984e8dce7d54
[ 8783.256735] R10: 0120 R11: 0001 R12:
8b1dbe136800
[ 8783.256735] R13: 8b1d74aefe80 R14: 8b1dbdeb9000 R15:
[ 8783.256735] FS: 7f213fed30c0() GS:8b1ded7c()
knlGS:
[ 8783.256735] CS: 0010 DS: ES: CR0: 80050033
[ 8783.256735] CR2: 556aa08ae9b8 CR3: 001b8e324005 CR4:
003606e0
[ 8783.256735] DR0: DR1: DR2:
[ 8783.256735] DR3: DR6: fffe0ff0 DR7:
0400
[ 8783.256735] Call Trace:
[ 8783.256735] ? security_capable+0x3c/0x60
[ 8783.256735] ext4_ioctl+0xf91/0x14d0
[ 8783.256735] ? audit_filter_rules.constprop.14+0x325/0xf90
[ 8783.256735] ? audit_filter_rules.constprop.14+0x24b/0xf90
[ 8783.256735] do_vfs_ioctl+0xa8/0x630
[ 8783.256735] ksys_ioctl+0x75/0x80
[ 8783.256735] __x64_sys_ioctl+0x1a/0x20
[ 8783.256735] do_syscall_64+0x6a/0x1a0
[ 8783.256735] entry_SYSCALL_64_after_hwframe+0x44/0xa9
[ 8783.256735] RIP: 0033:0x7f213f3825d7
[ 8783.256735] Code: b3 66 90 48 8b 05 b1 48 2d 00 64 c7 00 26 00 00 00 48 c7
c0 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 b8 10 00 00 00 0f 05 <48> 3d 01
f0 ff ff 73 01 c3 48 8b 0d 81 48 2d 00 f7 d8 64 89 01 48
[ 8783.256735] RSP: 002b:7ffe8effd688 EFLAGS: 0246 ORIG_RAX:
0010
[ 8783.256735] RAX: ffda RBX: 556aa08aa980 RCX:
7f213f3825d7
[ 8783.256735] RDX: 7ffe8effd7d0 RSI: 40086610 RDI:
0004
[ 8783.256735] RBP: 0004 R08: R09:
[ 8783.256735] R10: R11: 0246 R12:
556aa08ac980
[ 8783.256735] R13: 7ffe8effd7d0 R14: 556aa08a92d0 R15:
This issue is resolved by the following upstream commit:
f96c3ac8dfc2 ("ext4: fix crash during online resizing")
Commit f96c3ac8dfc2 is in mainline as of v5.1-rc1. This commit was requested
in the upstream stable kernels. However, the Ubuntu kernels are EOL upstream.
Please include this commit in the 16.04 and 18.04 linux-azure kernels.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1835322/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837661] [NEW] [linux-azure] CRI-RDOS | Live migration only takes 10 seconds, but the VM was unavailable for 2 hours
Public bug reported: Can you please pick up the following 4 patches? They resolve this live migration that was reported by a mutual customer. PCI: hv: Add pci_destroy_slot() in pci_devices_present_work(), if necessary PCI: hv: Add hv_pci_remove_slots() when we unload the driver PCI: hv: Fix a memory leak in hv_eject_device_work() PCI: hv: Fix a use-after-free bug in hv_eject_device_work()pci/hv This is a known issue in linux pci-hyperv driver and is fixed by these patches. ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: New -- 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/1837661 Title: [linux-azure] CRI-RDOS | Live migration only takes 10 seconds, but the VM was unavailable for 2 hours Status in linux-azure package in Ubuntu: New Bug description: Can you please pick up the following 4 patches? They resolve this live migration that was reported by a mutual customer. PCI: hv: Add pci_destroy_slot() in pci_devices_present_work(), if necessary PCI: hv: Add hv_pci_remove_slots() when we unload the driver PCI: hv: Fix a memory leak in hv_eject_device_work() PCI: hv: Fix a use-after-free bug in hv_eject_device_work()pci/hv This is a known issue in linux pci-hyperv driver and is fixed by these patches. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1837661/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821934] Re: [Hyper-V] Enable CONFIG_HOTPLUG_CPU in linux-azure
Will do. Thanks, Marcelo! -- 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/1821934 Title: [Hyper-V] Enable CONFIG_HOTPLUG_CPU in linux-azure Status in linux-azure package in Ubuntu: In Progress Status in linux-azure source package in Xenial: Fix Committed Status in linux-azure source package in Cosmic: Fix Committed Status in linux-azure source package in Disco: In Progress Bug description: We requested that CONFIG_HOTPLUG_CPU be disabled in bug 1776293. However, due to a recently discovered security issue, CONFIG_HOTPLUG_CPU needs to be re-enabled. There are some patches on LKML to address this security issue, but they are not in the Azure kernel yet, and may not be accepted upstream in their current form. If your interested, those two patches are available here: https://lkml.org/lkml/2019/3/26/893 https://lkml.org/lkml/2019/3/26/894 https://lkml.org/lkml/2019/3/26/895 To mitigate this security issue, the nosmt option needs to be passed on the boot line. However, the nosmt option will not work if CONFIG_HOTPLUG_CPU is disabled, which is the primary reason it needs to be turned back on at this time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1821934/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822118] Re: Kernel Panic while rebooting cloud instance
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 Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1822118 Title: Kernel Panic while rebooting cloud instance Status in linux-azure package in Ubuntu: In Progress Status in systemd package in Ubuntu: New Bug description: Description: In the event a particular Azure cloud instance is rebooted it's possible that it may never recover and the instance will break indefinitely. In My case, it was a kernel panic. See specifics below.. Series: Disco Instance Size: Basic_A3 Region: (Default) US-WEST-2 Kernel Version: 4.18.0-1013-azure #13-Ubuntu SMP Thu Feb 28 22:54:16 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux I had a simple script to reboot an instance (X) amount of times, I chose 50, so the machine would power cycle by issuing a "reboot" from the terminal prompt just as a user would. Once the machine came up, it captured dmesg and other bits then rebooted again until it reached 50. After the 4th attempt, my script timed out, I took a look at the instance console log and the following displayed on the console. [ OK ] Reached target Reboot. /shutdown: error while loading shared libra[ 89.498980] Kernel panic - not syncing: Attempted to kill init! exitcode=0x7f00 [ 89.498980] [ 89.500042] CPU: 0 PID: 1 Comm: shutdown Not tainted 4.18.0-1013-azure #13-Ubuntu [ 89.508026] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090007 06/02/2017 [ 89.508026] Call Trace: [ 89.508026] dump_stack+0x63/0x8a [ 89.508026] panic+0xe7/0x247 [ 89.508026] do_exit.cold.23+0x26/0x75 [ 89.508026] do_group_exit+0x43/0xb0 [ 89.508026] __x64_sys_exit_group+0x18/0x20 [ 89.508026] do_syscall_64+0x5a/0x110 [ 89.508026] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 89.508026] RIP: 0033:0x7f7bf0154d86 [ 89.508026] Code: Bad RIP value. [ 89.508026] RSP: 002b:7ffd6be693b8 EFLAGS: 0206 ORIG_RAX: 00e7 [ 89.508026] RAX: ffda RBX: 7f7bf015e420 RCX: 7f7bf0154d86 [ 89.508026] RDX: 007f RSI: 003c RDI: 007f [ 89.508026] RBP: 7f7bef9449c0 R08: 00e7 R09: [ 89.508026] R10: 7ffd6be6974c R11: 0206 R12: 0018 [ 89.508026] R13: 7f7bef944ac8 R14: 7f7bef944a00 R15: [ 89.508026] Kernel Offset: 0x1600 from 0x8100 (relocation range: 0x8000-0xbfff) [ 89.508026] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x7f00 [ 89.508026] ]--- this only occurred once in my testing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1822118/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1747463] Re: kernel crashes during boot unless IOMMU is disabled on Ryzen 1800X
** Changed in: linux (Ubuntu) Assignee: Joseph Salisbury (jsalisbury) => (unassigned) ** Changed in: linux (Ubuntu Bionic) Assignee: Joseph Salisbury (jsalisbury) => (unassigned) ** Changed in: linux (Ubuntu Cosmic) Assignee: Joseph Salisbury (jsalisbury) => (unassigned) -- 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/1747463 Title: kernel crashes during boot unless IOMMU is disabled on Ryzen 1800X Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Status in linux source package in Cosmic: Confirmed Bug description: I'm on a Ryzen 1800X and Biostar B350GT5 on bionic kubuntu. There are lots of AMD-Vi logged events and I get irq crashes or acpi hangups with a 'normal' boot. I got it to boot by disabling IOMMU in the BIOS and adding "iommu=soft" to the kernel booting options in grub. linux can then detect everything properly (all cores) and I've had zero crashes. The only issue is that it's using software IOMMU which could have a performance penalty because it has to copy all the data of some PCI devices to sub 4G regions. Alternatively it boots with the kernel option "acpi=off" but only detects a single core/thread. I attached a kernel log. I believe(d) this might be related to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360 and https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1690085 --- ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: fixme 1487 F pulseaudio /dev/snd/controlC0: fixme 1487 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=bc971fcc-8e63-4fa5-a149-af4af6c8eece InstallationDate: Installed on 2018-01-31 (4 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180131) IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: BIOSTAR Group B350GT5 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed root=/dev/mapper/kubuntu--vg-root ro iommu=soft quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-32-generic N/A linux-backports-modules-4.13.0-32-generic N/A linux-firmware 1.170 RfKill: Tags: bionic Uname: Linux 4.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/30/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.13 dmi.board.asset.tag: None dmi.board.name: B350GT5 dmi.board.vendor: BIOSTAR Group dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.13:bd11/30/2017:svnBIOSTARGroup:pnB350GT5:pvr:rvnBIOSTARGroup:rnB350GT5:rvr:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: None dmi.product.name: B350GT5 dmi.sys.vendor: BIOSTAR Group To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1747463/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823805] [NEW] The 4.18.0-1015.15 Azure Kernel Panics Due to Missing Commit
Public bug reported: The following commit was requested in the 18.04 Bionic kernel for Azure: c967590457ca scsi: storvsc: Fix a race in sub-channel creation that can cause panic This commit was included when it was requested in bug 1805304. However, the 18.04 Bionic kernel for Azure was based on the upstream 4.15 kernel at that time. The patch was applied to the 4.15 based kernel as an Ubuntu SAUCE patch. The 18.04 Bionic kernel for Azure has since been re-based to the 4.18 kernel. This requested commit was applied to mainline as of v4.20-rc6. The patch was cc’d to upstream stable, but upstream 4.18 was EOL by that point. Due to this, the patch never made it into any 4.18 kernels, which is why it is now missing from 18.04, it was rebased to 4.18. This is a critical issue. The 4.18.0-1015 kernel immediately panics on boot without this commit. ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: New ** Tags: kernel-hyper-v kernel-key -- 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/1823805 Title: The 4.18.0-1015.15 Azure Kernel Panics Due to Missing Commit Status in linux-azure package in Ubuntu: New Bug description: The following commit was requested in the 18.04 Bionic kernel for Azure: c967590457ca scsi: storvsc: Fix a race in sub-channel creation that can cause panic This commit was included when it was requested in bug 1805304. However, the 18.04 Bionic kernel for Azure was based on the upstream 4.15 kernel at that time. The patch was applied to the 4.15 based kernel as an Ubuntu SAUCE patch. The 18.04 Bionic kernel for Azure has since been re-based to the 4.18 kernel. This requested commit was applied to mainline as of v4.20-rc6. The patch was cc’d to upstream stable, but upstream 4.18 was EOL by that point. Due to this, the patch never made it into any 4.18 kernels, which is why it is now missing from 18.04, it was rebased to 4.18. This is a critical issue. The 4.18.0-1015 kernel immediately panics on boot without this commit. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1823805/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823805] Re: The 4.18.0-1015.15 Azure Kernel Panics Due to Missing Commit
The reason this missing commit is now causing a panic is because it Fixes the following commit, which is added by 4.18.0-1015: c40598d9e67c vmbus: split ring buffer allocation from open git describe --contains c40598d9e67c Ubuntu-azure-4.18.0-1015.15_18.04.1~57 -- 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/1823805 Title: The 4.18.0-1015.15 Azure Kernel Panics Due to Missing Commit Status in linux-azure package in Ubuntu: New Bug description: The following commit was requested in the 18.04 Bionic kernel for Azure: c967590457ca scsi: storvsc: Fix a race in sub-channel creation that can cause panic This commit was included when it was requested in bug 1805304. However, the 18.04 Bionic kernel for Azure was based on the upstream 4.15 kernel at that time. The patch was applied to the 4.15 based kernel as an Ubuntu SAUCE patch. The 18.04 Bionic kernel for Azure has since been re-based to the 4.18 kernel. This requested commit was applied to mainline as of v4.20-rc6. The patch was cc’d to upstream stable, but upstream 4.18 was EOL by that point. Due to this, the patch never made it into any 4.18 kernels, which is why it is now missing from 18.04, it was rebased to 4.18. This is a critical issue. The 4.18.0-1015 kernel immediately panics on boot without this commit. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1823805/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823805] Re: The 4.18.0-1015.15 Azure Kernel Panics Due to Missing Commit
And looking a little further, commit ae6935ed7d42(Bionic commit
c40598d9e67c) was added per bug 1812123 for DPDK. In that bug, we
requested two commits:
b5679cebf780 ("vmbus: fix subchannel removal")
5e3c420dcca5 ("uio_hv_generic: set callbacks on open")
However, commit b5679cebf780 is a fix for commit ae6935ed7d42, so commit
ae6935ed7d42 was also included. That then led to this bug, because with
commit ae6935ed7d42, commit c967590457ca is now also needed.
--
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/1823805
Title:
The 4.18.0-1015.15 Azure Kernel Panics Due to Missing Commit
Status in linux-azure package in Ubuntu:
New
Bug description:
The following commit was requested in the 18.04 Bionic kernel for Azure:
c967590457ca scsi: storvsc: Fix a race in sub-channel creation that can cause
panic
This commit was included when it was requested in bug 1805304.
However, the 18.04 Bionic kernel for Azure was based on the upstream
4.15 kernel at that time. The patch was applied to the 4.15 based
kernel as an Ubuntu SAUCE patch.
The 18.04 Bionic kernel for Azure has since been re-based to the 4.18
kernel. This requested commit was applied to mainline as of
v4.20-rc6. The patch was cc’d to upstream stable, but upstream 4.18
was EOL by that point. Due to this, the patch never made it into any
4.18 kernels, which is why it is now missing from 18.04, it was
rebased to 4.18.
This is a critical issue. The 4.18.0-1015 kernel immediately panics on boot
without this commit.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1823805/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823805] Re: The 4.18.0-1015.15 Azure Kernel Panics Due to Missing Commit
** Description changed: - The following commit was requested in the 18.04 Bionic kernel for Azure: + The following commit is requested in the 18.04 Bionic kernel for Azure: c967590457ca scsi: storvsc: Fix a race in sub-channel creation that can cause panic This commit was included when it was requested in bug 1805304. However, the 18.04 Bionic kernel for Azure was based on the upstream 4.15 kernel at that time. The patch was applied to the 4.15 based kernel as an Ubuntu SAUCE patch. The 18.04 Bionic kernel for Azure has since been re-based to the 4.18 kernel. This requested commit was applied to mainline as of v4.20-rc6. The patch was cc’d to upstream stable, but upstream 4.18 was EOL by that point. Due to this, the patch never made it into any 4.18 kernels, which is why it is now missing from 18.04, it was rebased to 4.18. - - This is a critical issue. The 4.18.0-1015 kernel immediately panics on boot without this commit. + This is a critical issue. The 4.18.0-1015 kernel immediately panics on + boot without this commit. ** Description changed: - The following commit is requested in the 18.04 Bionic kernel for Azure: + The following commit is being requested in the 18.04 4.18 based Bionic kernel for Azure: c967590457ca scsi: storvsc: Fix a race in sub-channel creation that can cause panic This commit was included when it was requested in bug 1805304. However, the 18.04 Bionic kernel for Azure was based on the upstream 4.15 kernel at that time. The patch was applied to the 4.15 based kernel as an Ubuntu SAUCE patch. The 18.04 Bionic kernel for Azure has since been re-based to the 4.18 kernel. This requested commit was applied to mainline as of v4.20-rc6. The patch was cc’d to upstream stable, but upstream 4.18 was EOL by that point. Due to this, the patch never made it into any 4.18 kernels, which is why it is now missing from 18.04, it was rebased to 4.18. This is a critical issue. The 4.18.0-1015 kernel immediately panics on boot without this commit. -- 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/1823805 Title: The 4.18.0-1015.15 Azure Kernel Panics Due to Missing Commit Status in linux-azure package in Ubuntu: New Bug description: The following commit is being requested in the 18.04 4.18 based Bionic kernel for Azure: c967590457ca scsi: storvsc: Fix a race in sub-channel creation that can cause panic This commit was included when it was requested in bug 1805304. However, the 18.04 Bionic kernel for Azure was based on the upstream 4.15 kernel at that time. The patch was applied to the 4.15 based kernel as an Ubuntu SAUCE patch. The 18.04 Bionic kernel for Azure has since been re-based to the 4.18 kernel. This requested commit was applied to mainline as of v4.20-rc6. The patch was cc’d to upstream stable, but upstream 4.18 was EOL by that point. Due to this, the patch never made it into any 4.18 kernels, which is why it is now missing from 18.04, it was rebased to 4.18. This is a critical issue. The 4.18.0-1015 kernel immediately panics on boot without this commit. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1823805/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837661] Re: [linux-azure] CRI-RDOS | Live migration only takes 10 seconds, but the VM was unavailable for 2 hours
These commits are not needed in the 4.15 kernel. The only kernels that
need the fixes are the ones that include the following commit:
a15f2c08c708 ("PCI: hv: support reporting serial number as slot
information")
--
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/1837661
Title:
[linux-azure] CRI-RDOS | Live migration only takes 10 seconds, but the
VM was unavailable for 2 hours
Status in linux-azure package in Ubuntu:
New
Status in linux-azure source package in Xenial:
Incomplete
Status in linux-azure source package in Disco:
Fix Committed
Bug description:
Can you please pick up the following 4 patches? They resolve this live
migration that was reported by a mutual customer.
PCI: hv: Add pci_destroy_slot() in pci_devices_present_work(), if necessary
PCI: hv: Add hv_pci_remove_slots() when we unload the driver
PCI: hv: Fix a memory leak in hv_eject_device_work()
PCI: hv: Fix a use-after-free bug in hv_eject_device_work()pci/hv
This is a known issue in linux pci-hyperv driver and is fixed by these
patches.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1837661/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840189] [NEW] Four Mellanox Patches needed for kernels that have that have SRIOV
Public bug reported: The following and their prerequisites should be applied to all releases that have SRIOV. The patches originated from Mellanox. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/infiniband/hw/mlx5?id=e5366d309a772fef264ec85e858f9ea46f939848 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/infiniband/hw/mlx5?id=76d5581c87045 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/infiniband/hw/mlx5?id=5df816e7f43f https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/infiniband/hw/mlx5?id=bd85fbc2038a Because of the “fixes:” tags on these, We expect them to work their way through stable eventually, but we should start the ball rolling. ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: New -- 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/1840189 Title: Four Mellanox Patches needed for kernels that have that have SRIOV Status in linux-azure package in Ubuntu: New Bug description: The following and their prerequisites should be applied to all releases that have SRIOV. The patches originated from Mellanox. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/infiniband/hw/mlx5?id=e5366d309a772fef264ec85e858f9ea46f939848 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/infiniband/hw/mlx5?id=76d5581c87045 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/infiniband/hw/mlx5?id=5df816e7f43f https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/infiniband/hw/mlx5?id=bd85fbc2038a Because of the “fixes:” tags on these, We expect them to work their way through stable eventually, but we should start the ball rolling. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1840189/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828248] Re: [linux-azure] Storage performance drop on RAID
The following commit was added in bug fa55b5d226dd. 7ac257b862f2c (“blk-mq: remove the request_list usage”) This commit cleans up unused code in block-mq (mq uses pre-allocated tags to allocate request, not request_list as it's used only in legacy queue). A test kernel with a revert of this commit would prove if it is the cause of this regression. -- 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/1828248 Title: [linux-azure] Storage performance drop on RAID Status in linux-azure package in Ubuntu: New Bug description: In Azure, FIO 4k tests are showing performance drops on latest proposed 4.15.0 linux-azure kernels - from 52K IOPS to ~38K IOPS (max value reached on both sequential and random read tests). The setup used is 12 disks in RAID0. The affected kernels are: Ubuntu 14.04 + 4.15.0-1043 Ubuntu 16.04 + 4.15.0-1044 Previous kernel versions had reached max IOPS, ~52K IOPS on both read tests (e.g. 16.04 + 4.15.0-1043 kernel). Right now, it seems like the issue is in the diff from 1043 kernel on trusty vs 1044 kernel on xenial. The 52K IOPS is expected at qdepth=256. The repro cmd (as ran by the automation) is this: fio --size=1023G --direct=1 --ioengine=libaio --filename=/dev/md0 --overwrite=1 --readwrite=randread --bs=4K --runtime=300 --iodepth=32 --numjob=8 --output-format=json --output=/root/FIOLog/jsonLog/fio-result-randread-4K-256td.json --name='repro' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1828248/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828248] Re: [linux-azure] Storage performance drop on RAID
The bug number from comment one should have been bug 1819689 -- 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/1828248 Title: [linux-azure] Storage performance drop on RAID Status in linux-azure package in Ubuntu: New Bug description: In Azure, FIO 4k tests are showing performance drops on latest proposed 4.15.0 linux-azure kernels - from 52K IOPS to ~38K IOPS (max value reached on both sequential and random read tests). The setup used is 12 disks in RAID0. The affected kernels are: Ubuntu 14.04 + 4.15.0-1043 Ubuntu 16.04 + 4.15.0-1044 Previous kernel versions had reached max IOPS, ~52K IOPS on both read tests (e.g. 16.04 + 4.15.0-1043 kernel). Right now, it seems like the issue is in the diff from 1043 kernel on trusty vs 1044 kernel on xenial. The 52K IOPS is expected at qdepth=256. The repro cmd (as ran by the automation) is this: fio --size=1023G --direct=1 --ioengine=libaio --filename=/dev/md0 --overwrite=1 --readwrite=randread --bs=4K --runtime=300 --iodepth=32 --numjob=8 --output-format=json --output=/root/FIOLog/jsonLog/fio-result-randread-4K-256td.json --name='repro' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1828248/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828248] Re: [linux-azure] Storage performance drop on RAID
This commit was also added to the Ubuntu-azure-4.18.0-1017 kernel. Are we seeing expected performing with that kernel? -- 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/1828248 Title: [linux-azure] Storage performance drop on RAID Status in linux-azure package in Ubuntu: New Bug description: In Azure, FIO 4k tests are showing performance drops on latest proposed 4.15.0 linux-azure kernels - from 52K IOPS to ~38K IOPS (max value reached on both sequential and random read tests). The setup used is 12 disks in RAID0. The affected kernels are: Ubuntu 14.04 + 4.15.0-1043 Ubuntu 16.04 + 4.15.0-1044 Previous kernel versions had reached max IOPS, ~52K IOPS on both read tests (e.g. 16.04 + 4.15.0-1043 kernel). Right now, it seems like the issue is in the diff from 1043 kernel on trusty vs 1044 kernel on xenial. The 52K IOPS is expected at qdepth=256. The repro cmd (as ran by the automation) is this: fio --size=1023G --direct=1 --ioengine=libaio --filename=/dev/md0 --overwrite=1 --readwrite=randread --bs=4K --runtime=300 --iodepth=32 --numjob=8 --output-format=json --output=/root/FIOLog/jsonLog/fio-result-randread-4K-256td.json --name='repro' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1828248/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819689] Re: [linux-azure] Commit To Improve NVMe Performance
If it would be best, I can open a new bug for those two additional commits. -- 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/1819689 Title: [linux-azure] Commit To Improve NVMe Performance Status in linux-azure package in Ubuntu: New Status in linux-azure source package in Xenial: Fix Committed Status in linux-azure source package in Cosmic: Fix Committed Bug description: In bug 1818138, the config option CONFIG_NO_HZ_FULL was requested to be enabled in the linux-azure kernels(currently 4.15 and 4.18) in order to increase NVME disks performance. To achieve the peak IOPs we are seeing in testing, the following commit is also needed: 7ac257b862f2c (“blk-mq: remove the request_list usage”) This commit cleans up unused code in block-mq (mq uses pre-allocated tags to allocate request, not request_list as it's used only in legacy queue). The commit saves a bunch of rcu locks on I/O queuing path, which increases the achievable IOPs seen in testing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1819689/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819689] Re: [linux-azure] Commit To Improve NVMe Performance
It was found that 4.15 has a couple more patches missing for NVMe, those patches are required to get to the target number of IOPS. The commits are: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/nvme/host/pci.c?h=v5.1&id=f9dde187fa921c12a8680089a77595b866e65455 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/nvme/host/pci.c?h=v5.1&id=1ab0cd6966fc4a7e9dfbd7c6eda917ae9c977f42 Would it be possible to pick up those two patches for 4.15. The 1st patch is a clean apply. The 2nd patch needs back porting. We can help, if it is needed for the second patch. -- 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/1819689 Title: [linux-azure] Commit To Improve NVMe Performance Status in linux-azure package in Ubuntu: New Status in linux-azure source package in Xenial: Fix Committed Status in linux-azure source package in Cosmic: Fix Committed Bug description: In bug 1818138, the config option CONFIG_NO_HZ_FULL was requested to be enabled in the linux-azure kernels(currently 4.15 and 4.18) in order to increase NVME disks performance. To achieve the peak IOPs we are seeing in testing, the following commit is also needed: 7ac257b862f2c (“blk-mq: remove the request_list usage”) This commit cleans up unused code in block-mq (mq uses pre-allocated tags to allocate request, not request_list as it's used only in legacy queue). The commit saves a bunch of rcu locks on I/O queuing path, which increases the achievable IOPs seen in testing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1819689/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828248] Re: [linux-azure] Storage performance drop on RAID
@Marcelo Cerri, just to confirm, the test kernel posted in comment #6 only had commit 7ac257b862f2c reverted? -- 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/1828248 Title: [linux-azure] Storage performance drop on RAID Status in linux-azure package in Ubuntu: New Status in linux-azure source package in Xenial: Fix Committed Bug description: In Azure, FIO 4k tests are showing performance drops on latest proposed 4.15.0 linux-azure kernels - from 52K IOPS to ~38K IOPS (max value reached on both sequential and random read tests). The setup used is 12 disks in RAID0. The affected kernels are: Ubuntu 14.04 + 4.15.0-1043 Ubuntu 16.04 + 4.15.0-1044 Previous kernel versions had reached max IOPS, ~52K IOPS on both read tests (e.g. 16.04 + 4.15.0-1043 kernel). Right now, it seems like the issue is in the diff from 1043 kernel on trusty vs 1044 kernel on xenial. The 52K IOPS is expected at qdepth=256. The repro cmd (as ran by the automation) is this: fio --size=1023G --direct=1 --ioengine=libaio --filename=/dev/md0 --overwrite=1 --readwrite=randread --bs=4K --runtime=300 --iodepth=32 --numjob=8 --output-format=json --output=/root/FIOLog/jsonLog/fio-result-randread-4K-256td.json --name='repro' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1828248/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828248] Re: [linux-azure] Storage performance drop on RAID
This patch was intended to increase performance, not reduce it. Is it too late to revert 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/1828248 Title: [linux-azure] Storage performance drop on RAID Status in linux-azure package in Ubuntu: New Status in linux-azure source package in Xenial: Fix Committed Bug description: In Azure, FIO 4k tests are showing performance drops on latest proposed 4.15.0 linux-azure kernels - from 52K IOPS to ~38K IOPS (max value reached on both sequential and random read tests). The setup used is 12 disks in RAID0. The affected kernels are: Ubuntu 14.04 + 4.15.0-1043 Ubuntu 16.04 + 4.15.0-1044 Previous kernel versions had reached max IOPS, ~52K IOPS on both read tests (e.g. 16.04 + 4.15.0-1043 kernel). Right now, it seems like the issue is in the diff from 1043 kernel on trusty vs 1044 kernel on xenial. The 52K IOPS is expected at qdepth=256. The repro cmd (as ran by the automation) is this: fio --size=1023G --direct=1 --ioengine=libaio --filename=/dev/md0 --overwrite=1 --readwrite=randread --bs=4K --runtime=300 --iodepth=32 --numjob=8 --output-format=json --output=/root/FIOLog/jsonLog/fio-result-randread-4K-256td.json --name='repro' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1828248/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828248] Re: [linux-azure] Storage performance drop on RAID
@marcelo, we do want the changes requested in comment #5 in bug 1819689. We can wait for the results of Long Li's investigation before proceeding there. -- 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/1828248 Title: [linux-azure] Storage performance drop on RAID Status in linux-azure package in Ubuntu: New Status in linux-azure source package in Xenial: Fix Committed Bug description: In Azure, FIO 4k tests are showing performance drops on latest proposed 4.15.0 linux-azure kernels - from 52K IOPS to ~38K IOPS (max value reached on both sequential and random read tests). The setup used is 12 disks in RAID0. The affected kernels are: Ubuntu 14.04 + 4.15.0-1043 Ubuntu 16.04 + 4.15.0-1044 Previous kernel versions had reached max IOPS, ~52K IOPS on both read tests (e.g. 16.04 + 4.15.0-1043 kernel). Right now, it seems like the issue is in the diff from 1043 kernel on trusty vs 1044 kernel on xenial. The 52K IOPS is expected at qdepth=256. The repro cmd (as ran by the automation) is this: fio --size=1023G --direct=1 --ioengine=libaio --filename=/dev/md0 --overwrite=1 --readwrite=randread --bs=4K --runtime=300 --iodepth=32 --numjob=8 --output-format=json --output=/root/FIOLog/jsonLog/fio-result-randread-4K-256td.json --name='repro' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1828248/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828248] Re: [linux-azure] Storage performance drop on RAID
Yes, that is correct. Comment #6. Sorry for the typo. -- 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/1828248 Title: [linux-azure] Storage performance drop on RAID Status in linux-azure package in Ubuntu: New Status in linux-azure source package in Xenial: Fix Committed Bug description: In Azure, FIO 4k tests are showing performance drops on latest proposed 4.15.0 linux-azure kernels - from 52K IOPS to ~38K IOPS (max value reached on both sequential and random read tests). The setup used is 12 disks in RAID0. The affected kernels are: Ubuntu 14.04 + 4.15.0-1043 Ubuntu 16.04 + 4.15.0-1044 Previous kernel versions had reached max IOPS, ~52K IOPS on both read tests (e.g. 16.04 + 4.15.0-1043 kernel). Right now, it seems like the issue is in the diff from 1043 kernel on trusty vs 1044 kernel on xenial. The 52K IOPS is expected at qdepth=256. The repro cmd (as ran by the automation) is this: fio --size=1023G --direct=1 --ioengine=libaio --filename=/dev/md0 --overwrite=1 --readwrite=randread --bs=4K --runtime=300 --iodepth=32 --numjob=8 --output-format=json --output=/root/FIOLog/jsonLog/fio-result-randread-4K-256td.json --name='repro' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1828248/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830242] [NEW] [linux-azure] Commits Requested in 16.04 for the Azure Kernel
Public bug reported:
The 4.15 kernel require three patches for NVMe, those patches are
required to get to the target number of IOPS.
The commits are:
7ac257b862f2c (“blk-mq: remove the request_list usage”)
f9dde187fa921 ("nvme-pci: remove cq check after submission")
1ab0cd6966fc4 ("nvme-pci: split the nvme queue lock into submission and
completion locks")
Please include these commits in the 4.15 based kernel.
** Affects: linux-azure (Ubuntu)
Importance: Undecided
Status: New
--
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/1830242
Title:
[linux-azure] Commits Requested in 16.04 for the Azure Kernel
Status in linux-azure package in Ubuntu:
New
Bug description:
The 4.15 kernel require three patches for NVMe, those patches are
required to get to the target number of IOPS.
The commits are:
7ac257b862f2c (“blk-mq: remove the request_list usage”)
f9dde187fa921 ("nvme-pci: remove cq check after submission")
1ab0cd6966fc4 ("nvme-pci: split the nvme queue lock into submission and
completion locks")
Please include these commits in the 4.15 based kernel.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1830242/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830242] Re: [linux-azure] Commits Requested in 16.04 for the Azure Kernel
** Summary changed:
- [linux-azure] Commits Requested in 16.04 and 18.04 for Azure Kernel
+ [linux-azure] Commits Requested in 16.04 for the Azure Kernel
--
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/1830242
Title:
[linux-azure] Commits Requested in 16.04 for the Azure Kernel
Status in linux-azure package in Ubuntu:
New
Status in linux-azure source package in Xenial:
In Progress
Bug description:
The 4.15 kernel require three patches for NVMe, those patches are
required to get to the target number of IOPS.
The commits are:
7ac257b862f2c (“blk-mq: remove the request_list usage”)
f9dde187fa921 ("nvme-pci: remove cq check after submission")
1ab0cd6966fc4 ("nvme-pci: split the nvme queue lock into submission and
completion locks")
Please include these commits in the 4.15 based kernel.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1830242/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830266] [NEW] [linux-azure] Please Include Mainline Commit ebaf39e6032f in the 16.04 and 18.04 linux-azure kernels
Public bug reported: A team within Microsoft is running the linux-azure Ubuntu kernel on a large AI cluster. They are hitting an issue which is resolved by the following commit: https://github.com/torvalds/linux/commit/ebaf39e6032faf77218220707fc3fa22487784e0 The bug is that threads can get stuck in the kernel. This bug can happen when removing network namespaces. This is something docker swarm does anytime it removes a container. Commit ebaf39e6032f was added to the mainline kernel tree in v4.20-rc6. It was not cc’d to upstream stable, so only v4.20-rc6 and newer kernels will have it. A test kernel was built with this commit, which resolves the issue. ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: New -- 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/1830266 Title: [linux-azure] Please Include Mainline Commit ebaf39e6032f in the 16.04 and 18.04 linux-azure kernels Status in linux-azure package in Ubuntu: New Bug description: A team within Microsoft is running the linux-azure Ubuntu kernel on a large AI cluster. They are hitting an issue which is resolved by the following commit: https://github.com/torvalds/linux/commit/ebaf39e6032faf77218220707fc3fa22487784e0 The bug is that threads can get stuck in the kernel. This bug can happen when removing network namespaces. This is something docker swarm does anytime it removes a container. Commit ebaf39e6032f was added to the mainline kernel tree in v4.20-rc6. It was not cc’d to upstream stable, so only v4.20-rc6 and newer kernels will have it. A test kernel was built with this commit, which resolves the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1830266/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830740] [NEW] [linux-azure] Delay during boot of some instance sizes
Public bug reported: We are seeing a long delay, about 100s, when booting new E32s_v3 VMs. We don’t see this delay with smaller sized Ubuntu VMs(D2s and NC6 sizes). I attached a screen shot of the boot delay. You can see between 7.022911 and 101.325958 seconds there is no activity. ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: New ** Attachment added: "BootDelay.PNG" https://bugs.launchpad.net/bugs/1830740/+attachment/5267156/+files/BootDelay.PNG -- 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/1830740 Title: [linux-azure] Delay during boot of some instance sizes Status in linux-azure package in Ubuntu: New Bug description: We are seeing a long delay, about 100s, when booting new E32s_v3 VMs. We don’t see this delay with smaller sized Ubuntu VMs(D2s and NC6 sizes). I attached a screen shot of the boot delay. You can see between 7.022911 and 101.325958 seconds there is no activity. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1830740/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820063] Re: [Hyper-V] KVP daemon fails to start on first boot of disco VM
** Tags added: kernel-hyper-v -- 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/1820063 Title: [Hyper-V] KVP daemon fails to start on first boot of disco VM Status in linux package in Ubuntu: Confirmed Bug description: Launching a recent daily image of disco on azure results in a VM in which the hv-kvp-daemon.service fails to start: $ systemctl status -o cat hv-kvp-daemon.service ● hv-kvp-daemon.service - Hyper-V KVP Protocol Daemon Loaded: loaded (/lib/systemd/system/hv-kvp-daemon.service; enabled; vendor pr Active: failed (Result: exit-code) since Thu 2019-03-14 13:07:15 UTC; 11min a Main PID: 219 (code=exited, status=1/FAILURE) Started Hyper-V KVP Protocol Daemon. KVP starting; pid is:219 open /dev/vmbus/hv_kvp failed; error: 2 No such file or directory hv-kvp-daemon.service: Main process exited, code=exited, status=1/FAILURE hv-kvp-daemon.service: Failed with result 'exit-code'. The instance was created with: $ az vm create --resource-group [redacted] --image Canonical:UbuntuServer:19.04-DAILY:19.04.201903130 --size Standard_D2_v2 --name disco-0313 As best as I can tell, the /dev/vmbus/hv_kvp isn't available when the hv-kvp-daemon.service starts, but it is available a few seconds later. Manually starting the daemon once I can ssh in works. --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' CRDA: N/A DistroRelease: Ubuntu 19.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-1011-azure root=PARTUUID=11894199-2ca2-4912-9c41-d28128744d57 ro console=tty1 console=ttyS0 panic=-1 ProcVersionSignature: User Name 4.18.0-1011.11-azure 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-1011-azure N/A linux-backports-modules-4.18.0-1011-azure N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: disco uec-images Uname: Linux 4.18.0-1011-azure x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 06/02/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 090007 dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: 7.0 dmi.chassis.asset.tag: 7783-7084-3265-9085-8269-3286-77 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: 7.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr090007:bd06/02/2017:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0: dmi.product.name: Virtual Machine dmi.product.uuid: 3b0f2160-7fc4-a646-904c-4248f04792d4 dmi.product.version: 7.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820063/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818138] Re: Add CONFIG_NO_HZ_FULL=y to linux-azure kernels
bug 1819689 is a complimentary performance bug. -- 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/1818138 Title: Add CONFIG_NO_HZ_FULL=y to linux-azure kernels Status in linux-azure package in Ubuntu: New Status in linux-azure source package in Xenial: Fix Committed Status in linux-azure source package in Cosmic: Fix Committed Bug description: This is a request to enable CONFIG_NO_HZ_FULL=y in the linux-azure kernels(currently 4.15 and 4.18) in order to increase NVME disks performance. The current CONFIG_NO_HZ configuration in linux-azure kernels is the following (tested on 4.15.0-1037, 4.15.0-1039 and 4.18.0-1011): CONFIG_NO_HZ=y CONFIG_NO_HZ_COMMON=y # CONFIG_NO_HZ_FULL is not set CONFIG_NO_HZ_IDLE=y To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1818138/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814069] Re: kernel linux-image-4.15.0-44 not booting on Hyperv Server 2008R2
** Tags added: kernel-hyper-v -- 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/1814069 Title: kernel linux-image-4.15.0-44 not booting on Hyperv Server 2008R2 Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: New Bug description: === SRU Justification === [Impact] NULL pointer dereference in netvsc_probe(). Module hv_netvsc is included in initramfs, so this blocks the boot process. For Hyper-V only supports single channel, rndis_filter_device_add() bails early and jump to tag "out". Subsequent code calls rndis_filter_device_remove() and returns ERR_PTR(ret), where ret is 0 (sucess). Because of that, it passes IS_ERR(nvdev) check in netvsc_probe() and cause a NULL pointer dereference, as nvdev now is 0: ... if (nvdev->num_chn > 1) schedule_work(&nvdev->subchan_work); [Fix] Correctly return net_device at the end of rndis_filter_device_add(). [Test] Users report positive result. [Regression Potenial] Low. Trivial change, patches are in upstream sometime. === Original Bug Report === Ubuntu stuck on booting on HyperV Server 2008R2. I saw kernel messages, seems to load ram image the boot is stuck. Seems to be a problem with hyperv drivers propably harddrive. Reverted back to the previous kernel. Description:Ubuntu 18.04.1 LTS Release:18.04Description:Ubuntu 18.04.1 LTS Release:18.04 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 31 08:52 seq crw-rw 1 root audio 116, 33 Jan 31 08:52 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=86036ccb-bc11-11e8-93c9-00155dfd7535 ro maybe-ubiquity ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 03/19/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 090004 dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: 7.0 dmi.chassis.asset.tag: 8531-7125-9206-2460-7819-2663-90 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: 7.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr090004:bd03/19/2009:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0: dmi.product.name: Virtual Machine dmi.product.version: 7.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814069/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821378] [NEW] [linux-azure] Include mainline commits fc96df16a1ce and ba50bf1ce9a5 in Azure kernel
Public bug reported:
This is a request to include the following two commits in 16.04 and
18.04 linux-azure:
fc96df16a1ce ("Drivers: hv: vmbus: Return -EINVAL for the sys files for
unopened channels")
ba50bf1ce9a5 ("Drivers: hv: vmbus: Check for ring when getting debug info")
Both commits are fixes to prior commits and have been cc'd to upstream
stable.
Commit fc96df16a1ce is in mainline as of v4.20
Commit ba50bf1ce9a5 is in mainline as of v5.0-rc4
The problem these commits fix is that some of the code for displaying
values for entries in /sys/bus/vmbus don't have appropriate locking to
prevent reading an entry while it is being created or being freed. The
result is accessing a bogus memory address.
** Affects: linux-azure (Ubuntu)
Importance: Undecided
Status: New
** Tags: kernel-hyper-v
** 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/1821378
Title:
[linux-azure] Include mainline commits fc96df16a1ce and ba50bf1ce9a5
in Azure kernel
Status in linux-azure package in Ubuntu:
New
Bug description:
This is a request to include the following two commits in 16.04 and
18.04 linux-azure:
fc96df16a1ce ("Drivers: hv: vmbus: Return -EINVAL for the sys files for
unopened channels")
ba50bf1ce9a5 ("Drivers: hv: vmbus: Check for ring when getting debug info")
Both commits are fixes to prior commits and have been cc'd to upstream
stable.
Commit fc96df16a1ce is in mainline as of v4.20
Commit ba50bf1ce9a5 is in mainline as of v5.0-rc4
The problem these commits fix is that some of the code for displaying
values for entries in /sys/bus/vmbus don't have appropriate locking to
prevent reading an entry while it is being created or being freed.
The result is accessing a bogus memory address.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1821378/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1804054] Re: [Hyper-V] kdump is broken on trusty with linux-azure 4.15.0-1032 kernel
** Changed in: linux-azure (Ubuntu) Status: Triaged => New -- 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/1804054 Title: [Hyper-V] kdump is broken on trusty with linux-azure 4.15.0-1032 kernel Status in linux-azure package in Ubuntu: New Bug description: While testing linux-azure 4.15.0-1032 kernel from proposed we found that kdump is no longer working as expected, on trusty only. Here are some info and versions. We'll have to verify a few more scenarios with other images and try to isolate this, but as least the kdump on trusty issue is there. Also remains to be checked in which release this regression was introduced. The below can be repro'd on Azure. On Xenial it works with ubuntu provided latest kexec-tools 2.0.16. It looks like the kexec might require some patches from upstream as far as I can tell from the data we have so far. Distro / kernel: 4.15.0-1032-azure #33~14.04.2-Ubuntu Package: kdump-tools1.5.5-2ubuntu1.6 Errors from logs: kdump-config: failed to load kdump kernel kernel: [ 230.772409] init: kdump-tools main process (1726) terminated with status 1 # cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-4.15.0-1032-azure root=x ro console=tty1 console=ttyS0 earlyprintk=ttyS0 rootdelay=300 crashkernel=384M --- This issue looks resolved with the kexec package build from the official kernel.org kexec repo, on top of 14.04. kexec-tools 2.0.18 https://git.kernel.org/pub/scm/utils/kernel/kexec/kexec-tools.git # cat /sys/kernel/kexec_* 1 402653184 And kdump core file gets created when running with 1032 kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1804054/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821934] Re: [Hyper-V] Enable CONFIG_HOTPLUG_CPU in linux-azure
** Information type changed from Private Security to Public -- 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/1821934 Title: [Hyper-V] Enable CONFIG_HOTPLUG_CPU in linux-azure Status in linux-azure package in Ubuntu: New Bug description: We requested that CONFIG_HOTPLUG_CPU be disabled in bug 1776293. However, due to a recently discovered security issue, CONFIG_HOTPLUG_CPU needs to be re-enabled. There are some patches on LKML to address this security issue, but they are not in the Azure kernel yet, and may not be accepted upstream in their current form. If your interested, those two patches are available here: https://lkml.org/lkml/2019/3/26/893 https://lkml.org/lkml/2019/3/26/894 https://lkml.org/lkml/2019/3/26/895 To mitigate this security issue, the nosmt option needs to be passed on the boot line. However, the nosmt option will not work if CONFIG_HOTPLUG_CPU is disabled, which is the primary reason it needs to be turned back on at this time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1821934/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822133] Re: Azure Instance never recovered during series of instance reboots.
** 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 linux-azure package in Ubuntu: In Progress Bug description: 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. Series: Disco Instance Size: Basic_A3 Region: (Default) US-WEST-2 Kernel Version: 4.18.0-1013-azure #13-Ubuntu SMP Thu Feb 28 22:54:16 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux I initiated a series of tests which rebooted Azure Cloud instances 50 times. During the 49th Reboot, an Instance failed to return from a reboot.. Upon grabbing the console output the following was seen scrolling endlessly. I have seen this failure in cases where the instance only restarted a handful of times >5 [84.247704]hyperv_fb: unable to send packet via vmbus [84.247704]hyperv_fb: unable to send packet via vmbus [84.247704]hyperv_fb: unable to send packet via vmbus [84.247704]hyperv_fb: unable to send packet via vmbus [84.247704]hyperv_fb: unable to send packet via vmbus [84.247704]hyperv_fb: unable to send packet via vmbus [84.247704]hyperv_fb: unable to send packet via vmbus [84.247704]hyperv_fb: unable to send packet via vmbus In another test attempt I saw the following failure: ERROR ExtHandler /proc/net/route contains no routes ERROR ExtHandler /proc/net/route contains no routes ERROR ExtHandler /proc/net/route contains no routes ERROR ExtHandler /proc/net/route contains no routes ERROR ExtHandler /proc/net/route contains no routes ERROR ExtHandler /proc/net/route contains no routes ERROR ExtHandler /proc/net/route contains no routes Both of these failures broke networking, Both of these failures were seen at least twice to three times, thus may explain why in some cases we never recover from an instance reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1822133/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822118] Re: Kernel Panic while rebooting cloud instance
** 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/1822118 Title: Kernel Panic while rebooting cloud instance Status in linux-azure package in Ubuntu: In Progress Bug description: Description: In the event a particular Azure cloud instance is rebooted it's possible that it may never recover and the instance will break indefinitely. In My case, it was a kernel panic. See specifics below.. Series: Disco Instance Size: Basic_A3 Region: (Default) US-WEST-2 Kernel Version: 4.18.0-1013-azure #13-Ubuntu SMP Thu Feb 28 22:54:16 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux I had a simple script to reboot an instance (X) amount of times, I chose 50, so the machine would power cycle by issuing a "reboot" from the terminal prompt just as a user would. Once the machine came up, it captured dmesg and other bits then rebooted again until it reached 50. After the 4th attempt, my script timed out, I took a look at the instance console log and the following displayed on the console. [ OK ] Reached target Reboot. /shutdown: error while loading shared libra[ 89.498980] Kernel panic - not syncing: Attempted to kill init! exitcode=0x7f00 [ 89.498980] [ 89.500042] CPU: 0 PID: 1 Comm: shutdown Not tainted 4.18.0-1013-azure #13-Ubuntu [ 89.508026] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090007 06/02/2017 [ 89.508026] Call Trace: [ 89.508026] dump_stack+0x63/0x8a [ 89.508026] panic+0xe7/0x247 [ 89.508026] do_exit.cold.23+0x26/0x75 [ 89.508026] do_group_exit+0x43/0xb0 [ 89.508026] __x64_sys_exit_group+0x18/0x20 [ 89.508026] do_syscall_64+0x5a/0x110 [ 89.508026] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 89.508026] RIP: 0033:0x7f7bf0154d86 [ 89.508026] Code: Bad RIP value. [ 89.508026] RSP: 002b:7ffd6be693b8 EFLAGS: 0206 ORIG_RAX: 00e7 [ 89.508026] RAX: ffda RBX: 7f7bf015e420 RCX: 7f7bf0154d86 [ 89.508026] RDX: 007f RSI: 003c RDI: 007f [ 89.508026] RBP: 7f7bef9449c0 R08: 00e7 R09: [ 89.508026] R10: 7ffd6be6974c R11: 0206 R12: 0018 [ 89.508026] R13: 7f7bef944ac8 R14: 7f7bef944a00 R15: [ 89.508026] Kernel Offset: 0x1600 from 0x8100 (relocation range: 0x8000-0xbfff) [ 89.508026] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x7f00 [ 89.508026] ]--- this only occurred once in my testing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1822118/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822118] Re: Kernel Panic while rebooting cloud instance
Are you able to share the script that reporduces this bug and bug 1822133? -- 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/1822118 Title: Kernel Panic while rebooting cloud instance Status in linux-azure package in Ubuntu: In Progress Bug description: Description: In the event a particular Azure cloud instance is rebooted it's possible that it may never recover and the instance will break indefinitely. In My case, it was a kernel panic. See specifics below.. Series: Disco Instance Size: Basic_A3 Region: (Default) US-WEST-2 Kernel Version: 4.18.0-1013-azure #13-Ubuntu SMP Thu Feb 28 22:54:16 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux I had a simple script to reboot an instance (X) amount of times, I chose 50, so the machine would power cycle by issuing a "reboot" from the terminal prompt just as a user would. Once the machine came up, it captured dmesg and other bits then rebooted again until it reached 50. After the 4th attempt, my script timed out, I took a look at the instance console log and the following displayed on the console. [ OK ] Reached target Reboot. /shutdown: error while loading shared libra[ 89.498980] Kernel panic - not syncing: Attempted to kill init! exitcode=0x7f00 [ 89.498980] [ 89.500042] CPU: 0 PID: 1 Comm: shutdown Not tainted 4.18.0-1013-azure #13-Ubuntu [ 89.508026] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090007 06/02/2017 [ 89.508026] Call Trace: [ 89.508026] dump_stack+0x63/0x8a [ 89.508026] panic+0xe7/0x247 [ 89.508026] do_exit.cold.23+0x26/0x75 [ 89.508026] do_group_exit+0x43/0xb0 [ 89.508026] __x64_sys_exit_group+0x18/0x20 [ 89.508026] do_syscall_64+0x5a/0x110 [ 89.508026] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 89.508026] RIP: 0033:0x7f7bf0154d86 [ 89.508026] Code: Bad RIP value. [ 89.508026] RSP: 002b:7ffd6be693b8 EFLAGS: 0206 ORIG_RAX: 00e7 [ 89.508026] RAX: ffda RBX: 7f7bf015e420 RCX: 7f7bf0154d86 [ 89.508026] RDX: 007f RSI: 003c RDI: 007f [ 89.508026] RBP: 7f7bef9449c0 R08: 00e7 R09: [ 89.508026] R10: 7ffd6be6974c R11: 0206 R12: 0018 [ 89.508026] R13: 7f7bef944ac8 R14: 7f7bef944a00 R15: [ 89.508026] Kernel Offset: 0x1600 from 0x8100 (relocation range: 0x8000-0xbfff) [ 89.508026] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x7f00 [ 89.508026] ]--- this only occurred once in my testing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1822118/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822118] Re: Kernel Panic while rebooting cloud instance
Thanks Sean and Colin! I'm going to see if I can reproduce it. If I can, I do the usual investigation to see if its a regression, fixed upstream and if a bisect will help. -- 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/1822118 Title: Kernel Panic while rebooting cloud instance Status in linux-azure package in Ubuntu: In Progress Bug description: Description: In the event a particular Azure cloud instance is rebooted it's possible that it may never recover and the instance will break indefinitely. In My case, it was a kernel panic. See specifics below.. Series: Disco Instance Size: Basic_A3 Region: (Default) US-WEST-2 Kernel Version: 4.18.0-1013-azure #13-Ubuntu SMP Thu Feb 28 22:54:16 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux I had a simple script to reboot an instance (X) amount of times, I chose 50, so the machine would power cycle by issuing a "reboot" from the terminal prompt just as a user would. Once the machine came up, it captured dmesg and other bits then rebooted again until it reached 50. After the 4th attempt, my script timed out, I took a look at the instance console log and the following displayed on the console. [ OK ] Reached target Reboot. /shutdown: error while loading shared libra[ 89.498980] Kernel panic - not syncing: Attempted to kill init! exitcode=0x7f00 [ 89.498980] [ 89.500042] CPU: 0 PID: 1 Comm: shutdown Not tainted 4.18.0-1013-azure #13-Ubuntu [ 89.508026] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090007 06/02/2017 [ 89.508026] Call Trace: [ 89.508026] dump_stack+0x63/0x8a [ 89.508026] panic+0xe7/0x247 [ 89.508026] do_exit.cold.23+0x26/0x75 [ 89.508026] do_group_exit+0x43/0xb0 [ 89.508026] __x64_sys_exit_group+0x18/0x20 [ 89.508026] do_syscall_64+0x5a/0x110 [ 89.508026] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 89.508026] RIP: 0033:0x7f7bf0154d86 [ 89.508026] Code: Bad RIP value. [ 89.508026] RSP: 002b:7ffd6be693b8 EFLAGS: 0206 ORIG_RAX: 00e7 [ 89.508026] RAX: ffda RBX: 7f7bf015e420 RCX: 7f7bf0154d86 [ 89.508026] RDX: 007f RSI: 003c RDI: 007f [ 89.508026] RBP: 7f7bef9449c0 R08: 00e7 R09: [ 89.508026] R10: 7ffd6be6974c R11: 0206 R12: 0018 [ 89.508026] R13: 7f7bef944ac8 R14: 7f7bef944a00 R15: [ 89.508026] Kernel Offset: 0x1600 from 0x8100 (relocation range: 0x8000-0xbfff) [ 89.508026] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x7f00 [ 89.508026] ]--- this only occurred once in my testing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1822118/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831254] [NEW] [linux-azure] XDP generic fixes
Public bug reported:
These two commits were needed to to get XDP working on Azure.
This set of patches came about while investigating and XDP generic issue
on Azure. The split brain nature of the accelerated networking exposed
issues with the stack device model.
The following two commits are currently in linux-next and were tested to
resolve this issue:
996ed04741467 ("netvsc: unshare skb in VF rx handler")
458bf2f224f04 ("net: core: support XDP generic on stacked devices.")
** Affects: linux-azure (Ubuntu)
Importance: Undecided
Status: New
--
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/1831254
Title:
[linux-azure] XDP generic fixes
Status in linux-azure package in Ubuntu:
New
Bug description:
These two commits were needed to to get XDP working on Azure.
This set of patches came about while investigating and XDP generic
issue on Azure. The split brain nature of the accelerated networking
exposed issues with the stack device model.
The following two commits are currently in linux-next and were tested
to resolve this issue:
996ed04741467 ("netvsc: unshare skb in VF rx handler")
458bf2f224f04 ("net: core: support XDP generic on stacked devices.")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1831254/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831268] [NEW] Ubuntu 19.04: Random SR-IOV issues
Public bug reported: No VFs inside the VM. Unfortunately this issue doesn’t have a 100% repro. Sometimes all the VFs are missing, other times a few are available and the rest are missing. The best test case to catch this issue is VERIFY-ENABLE-DISABLE-SRIOV- ON-EXISTING-VM. Comparing the logs between working/not working VMs, the only difference was that these 2 messages were missing from the broken VMs: mlx4_en: rename9: Steering Mode 2 mlx4_en: rename9: Link Up ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: New -- 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/1831268 Title: Ubuntu 19.04: Random SR-IOV issues Status in linux-azure package in Ubuntu: New Bug description: No VFs inside the VM. Unfortunately this issue doesn’t have a 100% repro. Sometimes all the VFs are missing, other times a few are available and the rest are missing. The best test case to catch this issue is VERIFY-ENABLE-DISABLE-SRIOV- ON-EXISTING-VM. Comparing the logs between working/not working VMs, the only difference was that these 2 messages were missing from the broken VMs: mlx4_en: rename9: Steering Mode 2 mlx4_en: rename9: Link Up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1831268/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826416] [NEW] [Xenial] Customer can not SSH to Linux VM due to "VSC State Unhealthy"
Public bug reported: A mutual customer is reporting ssh is not working on a Xenial based VM. This VM is running the 4.4 based Xenial kernel and not a custom linux- azure kernel. After an investigation this is a known old signaling issue. The 4.4 based Xenial kernels require the following patch: vmbus: fix missing signaling in hv_signal_on_read() (https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=13c5e97701091f9b02ded0c68809f8a6b08c747a). The patch is not in the upstream stable 4.4 tree, because it’s not needed there. Compared to the upstream 4.4 tree, Ubuntu 4.4.0-124-generic integrated more hv patches from the mainline kernel, e.g. Drivers: hv: vmbus: finally fix hv_need_to_signal_on_read(), so it must pick up the above patch. We checked the latest Ubuntu 4.4 kernel (https://kernel.ubuntu.com/git/ubuntu/ubuntu- xenial.git/tree/?h=Ubuntu-4.4.0-146.172) and the patch is also absent there. The patch (13c5e97701091f9b02ded0c68809f8a6b08c747a) can be cleanly cherry-picked into Ubuntu-4.4.0-146.172. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: kernel-hyper-v ** Summary changed: - [Xenial] Customer could not SSH to Linux VM due to "VSC State Unhealthy" + [Xenial] Customer can not SSH to Linux VM due to "VSC State Unhealthy" -- 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/1826416 Title: [Xenial] Customer can not SSH to Linux VM due to "VSC State Unhealthy" Status in linux package in Ubuntu: New Bug description: A mutual customer is reporting ssh is not working on a Xenial based VM. This VM is running the 4.4 based Xenial kernel and not a custom linux-azure kernel. After an investigation this is a known old signaling issue. The 4.4 based Xenial kernels require the following patch: vmbus: fix missing signaling in hv_signal_on_read() (https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=13c5e97701091f9b02ded0c68809f8a6b08c747a). The patch is not in the upstream stable 4.4 tree, because it’s not needed there. Compared to the upstream 4.4 tree, Ubuntu 4.4.0-124-generic integrated more hv patches from the mainline kernel, e.g. Drivers: hv: vmbus: finally fix hv_need_to_signal_on_read(), so it must pick up the above patch. We checked the latest Ubuntu 4.4 kernel (https://kernel.ubuntu.com/git/ubuntu/ubuntu- xenial.git/tree/?h=Ubuntu-4.4.0-146.172) and the patch is also absent there. The patch (13c5e97701091f9b02ded0c68809f8a6b08c747a) can be cleanly cherry-picked into Ubuntu-4.4.0-146.172. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826416/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822118] Re: Kernel Panic while rebooting cloud instance
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 would have an effect, but I'll look into 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/1822118 Title: Kernel Panic while rebooting cloud instance Status in linux-azure package in Ubuntu: In Progress Status in systemd package in Ubuntu: New Bug description: Description: In the event a particular Azure cloud instance is rebooted it's possible that it may never recover and the instance will break indefinitely. In My case, it was a kernel panic. See specifics below.. Series: Disco Instance Size: Basic_A3 Region: (Default) US-WEST-2 Kernel Version: 4.18.0-1013-azure #13-Ubuntu SMP Thu Feb 28 22:54:16 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux I had a simple script to reboot an instance (X) amount of times, I chose 50, so the machine would power cycle by issuing a "reboot" from the terminal prompt just as a user would. Once the machine came up, it captured dmesg and other bits then rebooted again until it reached 50. After the 4th attempt, my script timed out, I took a look at the instance console log and the following displayed on the console. [ OK ] Reached target Reboot. /shutdown: error while loading shared libra[ 89.498980] Kernel panic - not syncing: Attempted to kill init! exitcode=0x7f00 [ 89.498980] [ 89.500042] CPU: 0 PID: 1 Comm: shutdown Not tainted 4.18.0-1013-azure #13-Ubuntu [ 89.508026] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090007 06/02/2017 [ 89.508026] Call Trace: [ 89.508026] dump_stack+0x63/0x8a [ 89.508026] panic+0xe7/0x247 [ 89.508026] do_exit.cold.23+0x26/0x75 [ 89.508026] do_group_exit+0x43/0xb0 [ 89.508026] __x64_sys_exit_group+0x18/0x20 [ 89.508026] do_syscall_64+0x5a/0x110 [ 89.508026] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 89.508026] RIP: 0033:0x7f7bf0154d86 [ 89.508026] Code: Bad RIP value. [ 89.508026] RSP: 002b:7ffd6be693b8 EFLAGS: 0206 ORIG_RAX: 00e7 [ 89.508026] RAX: ffda RBX: 7f7bf015e420 RCX: 7f7bf0154d86 [ 89.508026] RDX: 007f RSI: 003c RDI: 007f [ 89.508026] RBP: 7f7bef9449c0 R08: 00e7 R09: [ 89.508026] R10: 7ffd6be6974c R11: 0206 R12: 0018 [ 89.508026] R13: 7f7bef944ac8 R14: 7f7bef944a00 R15: [ 89.508026] Kernel Offset: 0x1600 from 0x8100 (relocation range: 0x8000-0xbfff) [ 89.508026] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x7f00 [ 89.508026] ]--- this only occurred once in my testing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1822118/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824879] Re: linux-azure: Add the Catapult FPGA Driver
** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- 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/1824879 Title: linux-azure: Add the Catapult FPGA Driver Status in linux-azure package in Ubuntu: New Status in linux-azure source package in Xenial: New Status in linux-azure source package in Cosmic: Fix Committed Bug description: [Impact] Add the Catapult FPGA Driver to the custom linux-azure kernel while a version is not available upstream. [Test Case] The catapult driver must be present as a module in the linux-modules package (not in the linux-modules-extra). [Regression Potential] Low risk of regression since that's a new driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1824879/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827916] [NEW] Enable eBPF JIT in the linux-azure kernels
Public bug reported: eBPF is available as of kernel version 4.15, which is used on AKS nodes. Enabling JIT eBPF (built-in kernel feature) will speed-up execution of eBPF aware tools. eBPF JIT is controlled by the file /proc/sys/net/core/bpf_jit_enable. More details for eBPF JIT - https://www.kernel.org/doc/Documentation/sysctl/net.txt The file /proc/sys/net/core/bpf_jit_enable is not present on AKS nodes. Also, to support eBPF in AKS, we are requesting to switch the mlx* and ib* drivers to loadable modules instead of static. ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: New ** Tags: 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/1827916 Title: Enable eBPF JIT in the linux-azure kernels Status in linux-azure package in Ubuntu: New Bug description: eBPF is available as of kernel version 4.15, which is used on AKS nodes. Enabling JIT eBPF (built-in kernel feature) will speed-up execution of eBPF aware tools. eBPF JIT is controlled by the file /proc/sys/net/core/bpf_jit_enable. More details for eBPF JIT - https://www.kernel.org/doc/Documentation/sysctl/net.txt The file /proc/sys/net/core/bpf_jit_enable is not present on AKS nodes. Also, to support eBPF in AKS, we are requesting to switch the mlx* and ib* drivers to loadable modules instead of static. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1827916/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827916] Re: Enable eBPF JIT in the linux-azure kernels
This request is for the 16.04 and 18.04 kernels. -- 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/1827916 Title: Enable eBPF JIT in the linux-azure kernels Status in linux-azure package in Ubuntu: New Bug description: eBPF is available as of kernel version 4.15, which is used on AKS nodes. Enabling JIT eBPF (built-in kernel feature) will speed-up execution of eBPF aware tools. eBPF JIT is controlled by the file /proc/sys/net/core/bpf_jit_enable. More details for eBPF JIT - https://www.kernel.org/doc/Documentation/sysctl/net.txt The file /proc/sys/net/core/bpf_jit_enable is not present on AKS nodes. Also, to support eBPF in AKS, we are requesting to switch the mlx* and ib* drivers to loadable modules instead of static. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1827916/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828101] [NEW] [linux-azure] Disk Partition Issue
Public bug reported: In testing with the “Canonical UbuntuServer 19.04 latest” image from the Azure Marketplace, we’re seeing these lines output in dmesg: lisa@LISAv2-OneVM8NIC-v-stlups-AQ63-20190507075423-role-0:~$ dmesg | grep GPT [ 17.228278] GPT:Primary header thinks Alt. header is not at the end of the disk. [ 17.237240] GPT:4612095 != 62914559 [ 17.259079] GPT:Alternate GPT header not at the end of the disk. [ 17.259080] GPT:4612095 != 62914559 [ 17.259080] GPT: Use GNU Parted to correct GPT errors. It looks like maybe the disk partition structure in the image isn’t quite correct. Linux continues to boot, and the reported errors don’t cause any obvious problems, but it seems like this is something that should be corrected. ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: New ** Tags: 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/1828101 Title: [linux-azure] Disk Partition Issue Status in linux-azure package in Ubuntu: New Bug description: In testing with the “Canonical UbuntuServer 19.04 latest” image from the Azure Marketplace, we’re seeing these lines output in dmesg: lisa@LISAv2-OneVM8NIC-v-stlups-AQ63-20190507075423-role-0:~$ dmesg | grep GPT [ 17.228278] GPT:Primary header thinks Alt. header is not at the end of the disk. [ 17.237240] GPT:4612095 != 62914559 [ 17.259079] GPT:Alternate GPT header not at the end of the disk. [ 17.259080] GPT:4612095 != 62914559 [ 17.259080] GPT: Use GNU Parted to correct GPT errors. It looks like maybe the disk partition structure in the image isn’t quite correct. Linux continues to boot, and the reported errors don’t cause any obvious problems, but it seems like this is something that should be corrected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1828101/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839673] Re: [linux-azure] Important InfiniBand patches for Ubuntu 18.04
** Patch added:
"0002-Expose-extended-attributes-for-user-IB-verbs-QUERY_D.patch"
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1839673/+attachment/5281841/+files/0002-Expose-extended-attributes-for-user-IB-verbs-QUERY_D.patch
--
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/1839673
Title:
[linux-azure] Important InfiniBand patches for Ubuntu 18.04
Status in linux-azure package in Ubuntu:
New
Bug description:
The following two patches are critical for unblocking kernel sign-off
for the 5.0 kernel in Ubuntu 18.04:
("Don't wait in hvnd_query_gid after interface is already bound to ND")
("Expose extended attributes for user IB verbs QUERY_DEVICE, CREATE_CQ and
CREATE_QP")
The patches have not landed in linux-next yet, but are needed to
unblock 18.04 IB. The patches have been attached to this bug report.
Please consider
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1839673/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839673] Re: [linux-azure] Important InfiniBand patches for Ubuntu 18.04
** Patch added:
"0001-Don-t-wait-in-hvnd_query_gid-after-interface-is-alre.patch"
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1839673/+attachment/5281840/+files/0001-Don-t-wait-in-hvnd_query_gid-after-interface-is-alre.patch
--
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/1839673
Title:
[linux-azure] Important InfiniBand patches for Ubuntu 18.04
Status in linux-azure package in Ubuntu:
New
Bug description:
The following two patches are critical for unblocking kernel sign-off
for the 5.0 kernel in Ubuntu 18.04:
("Don't wait in hvnd_query_gid after interface is already bound to ND")
("Expose extended attributes for user IB verbs QUERY_DEVICE, CREATE_CQ and
CREATE_QP")
The patches have not landed in linux-next yet, but are needed to
unblock 18.04 IB. The patches have been attached to this bug report.
Please consider
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1839673/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839673] [NEW] [linux-azure] Important InfiniBand patches for Ubuntu 18.04
Public bug reported:
The following two patches are critical for unblocking kernel sign-off
for the 5.0 kernel in Ubuntu 18.04:
("Don't wait in hvnd_query_gid after interface is already bound to ND")
("Expose extended attributes for user IB verbs QUERY_DEVICE, CREATE_CQ and
CREATE_QP")
The patches have not landed in linux-next yet, but are needed to unblock
18.04 IB. The patches have been attached to this bug report. Please
consider
** Affects: linux-azure (Ubuntu)
Importance: Undecided
Status: New
--
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/1839673
Title:
[linux-azure] Important InfiniBand patches for Ubuntu 18.04
Status in linux-azure package in Ubuntu:
New
Bug description:
The following two patches are critical for unblocking kernel sign-off
for the 5.0 kernel in Ubuntu 18.04:
("Don't wait in hvnd_query_gid after interface is already bound to ND")
("Expose extended attributes for user IB verbs QUERY_DEVICE, CREATE_CQ and
CREATE_QP")
The patches have not landed in linux-next yet, but are needed to
unblock 18.04 IB. The patches have been attached to this bug report.
Please consider
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1839673/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839673] Re: [linux-azure] Important InfiniBand patches for Ubuntu 18.04
** Description changed:
The following two patches are critical for unblocking kernel sign-off
for the 5.0 kernel in Ubuntu 18.04:
("Don't wait in hvnd_query_gid after interface is already bound to ND")
("Expose extended attributes for user IB verbs QUERY_DEVICE, CREATE_CQ and
CREATE_QP")
The patches have not landed in linux-next yet, but are needed to unblock
18.04 IB. The patches have been attached to this bug report. Please
- consider
+ consider including these patches as SAUCE until they land in mainline.
--
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/1839673
Title:
[linux-azure] Important InfiniBand patches for Ubuntu 18.04
Status in linux-azure package in Ubuntu:
New
Bug description:
The following two patches are critical for unblocking kernel sign-off
for the 5.0 kernel in Ubuntu 18.04:
("Don't wait in hvnd_query_gid after interface is already bound to ND")
("Expose extended attributes for user IB verbs QUERY_DEVICE, CREATE_CQ and
CREATE_QP")
The patches have not landed in linux-next yet, but are needed to
unblock 18.04 IB. The patches have been attached to this bug report.
Please consider including these patches as SAUCE until they land in
mainline.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1839673/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877647] [NEW] Make sched clock return nanoseconds correctly
Public bug reported:
The problem was introduced in Linux kernel version 5.4, and was fixed in
5.6. So only users of the 5.4 and 5.5 kernels will see this problem,
which means Ubuntu 20.04 at the moment.
The fix was backported to upstream stable 5.4, so it should be picked up
via stable updates. This bug is primary to ensure the fix is not
missed.
The commit to fix this issue is:
749da8ca978f ("clocksource/drivers/hyper-v: Make sched clock return
nanoseconds correctly")
** Affects: linux-azure (Ubuntu)
Importance: Undecided
Status: New
--
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/1877647
Title:
Make sched clock return nanoseconds correctly
Status in linux-azure package in Ubuntu:
New
Bug description:
The problem was introduced in Linux kernel version 5.4, and was fixed
in 5.6. So only users of the 5.4 and 5.5 kernels will see this
problem, which means Ubuntu 20.04 at the moment.
The fix was backported to upstream stable 5.4, so it should be picked
up via stable updates. This bug is primary to ensure the fix is not
missed.
The commit to fix this issue is:
749da8ca978f ("clocksource/drivers/hyper-v: Make sched clock return
nanoseconds correctly")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1877647/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877654] [NEW] Add XDP support to hv_netvsc driver
Public bug reported: Microsoft would like to request the following three patches in all releases supported on Azure: 351e1581395fc (“hv_netvsc: Add XDP support”) 12fa74383ed4d (“hv_netvsc: Update document for XDP support”) 184367dce4f7 (“hv_netvsc: Fix XDP refcnt for synthetic and VF NICs”) These patches add support of XDP in native mode to the hv_netvsc driver, and transparently sets the XDP program on the associated VF NIC as well. ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: New -- 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/1877654 Title: Add XDP support to hv_netvsc driver Status in linux-azure package in Ubuntu: New Bug description: Microsoft would like to request the following three patches in all releases supported on Azure: 351e1581395fc (“hv_netvsc: Add XDP support”) 12fa74383ed4d (“hv_netvsc: Update document for XDP support”) 184367dce4f7 (“hv_netvsc: Fix XDP refcnt for synthetic and VF NICs”) These patches add support of XDP in native mode to the hv_netvsc driver, and transparently sets the XDP program on the associated VF NIC as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1877654/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878075] [NEW] Request to blacklist floppy for images on Azure
Public bug reported: After booting, there's an error message in dmesg: "blk_update_request: I/O error, dev fd0, sector 0" There’s no point in having a floppy driver, and the “I/O error dev fd0 sector 0” messages are distracting where there is no real issue. Blacklisting floppy can avoid this error. Adding a file into the /etc/modprobe.d directory is one approach. You can name the file whatever you want that ends with .conf, and the contents just need to be “blacklist floppy”. Using a separate file means you don’t have to edit any existing files, so it’s easy to update an existing image. However, another approach might be needed if the floppy driver is initramfs. ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: New -- 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/1878075 Title: Request to blacklist floppy for images on Azure Status in linux-azure package in Ubuntu: New Bug description: After booting, there's an error message in dmesg: "blk_update_request: I/O error, dev fd0, sector 0" There’s no point in having a floppy driver, and the “I/O error dev fd0 sector 0” messages are distracting where there is no real issue. Blacklisting floppy can avoid this error. Adding a file into the /etc/modprobe.d directory is one approach. You can name the file whatever you want that ends with .conf, and the contents just need to be “blacklist floppy”. Using a separate file means you don’t have to edit any existing files, so it’s easy to update an existing image. However, another approach might be needed if the floppy driver is initramfs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1878075/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878492] [NEW] Partition naming regression with linux-azure 5.3 kernel
Public bug reported: This issue is happening with a Bionic VM on Azure. The VM has a separate data disk mounted in addition to the root disk. The separate data disk is used to hold kernel git repos and is formatted as ext4. After applying the latest Bionic updates, the kernel was upgraded to linux 5.3.0-1020-azure from 5.0.0-10365-azure. Upon reboot the root disk was found, but the data disk could not be found and therefor not mounted. The data disk could not be found because the partition name changed after booting with the 5.3 kernel. With the 5.0 kernel, the partition name (/dev/sdc1) stays the same after every reboot. However, with the 5.3 kernel, the partition name changes after every reboot. For example, the name changes to /dev/sda1, /dev/sdb1, /dev/sdc1, etc. Mounting of this data disk is configured in the /etc/fstab file with the following: jsalisbury@jsalisbury-ubuntu18-04-git-repos:~/$ more /etc/fstab # CLOUD_IMG: This file was created/modified by the Cloud Image build process UUID=6004921f-4fdb-4fc8-a409-4a1f079f0150 /ext4 defaults,discard0 0 LABEL=UEFI /boot/efi vfatdefaults,discard0 0 /dev/sdc1 /src ext4 defaults,discard0 0 With this configuration, the disk cannot be found when the name changes, which happens with the 5.3 kernel. Here is an example of /proc/partition when booting the 5.3 kernel(On this boot, the disk name changed to sdb): major minor #blocks name 80 67108864 sda 81 67107776 sda1 8 16 1072693248 sdb 8 17 1072692224 sdb1 8 32 31457280 sdc 8 33 31343599 sdc1 8 46 4096 sdc14 8 47 108544 sdc15 Here is what happens on every boot with the 5.0 kernel(Note the name is sdc, as expected, and always stays sdc): major minor #blocks name 80 31457280 sda 81 31343599 sda1 8 14 4096 sda14 8 15 108544 sda15 8 16 67108864 sdb 8 17 67107776 sdb1 8 32 1072693248 sdc 8 33 1072692224 sdc1 ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: New -- 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/1878492 Title: Partition naming regression with linux-azure 5.3 kernel Status in linux-azure package in Ubuntu: New Bug description: This issue is happening with a Bionic VM on Azure. The VM has a separate data disk mounted in addition to the root disk. The separate data disk is used to hold kernel git repos and is formatted as ext4. After applying the latest Bionic updates, the kernel was upgraded to linux 5.3.0-1020-azure from 5.0.0-10365-azure. Upon reboot the root disk was found, but the data disk could not be found and therefor not mounted. The data disk could not be found because the partition name changed after booting with the 5.3 kernel. With the 5.0 kernel, the partition name (/dev/sdc1) stays the same after every reboot. However, with the 5.3 kernel, the partition name changes after every reboot. For example, the name changes to /dev/sda1, /dev/sdb1, /dev/sdc1, etc. Mounting of this data disk is configured in the /etc/fstab file with the following: jsalisbury@jsalisbury-ubuntu18-04-git-repos:~/$ more /etc/fstab # CLOUD_IMG: This file was created/modified by the Cloud Image build process UUID=6004921f-4fdb-4fc8-a409-4a1f079f0150 /ext4 defaults,discard0 0 LABEL=UEFI /boot/efi vfatdefaults,discard0 0 /dev/sdc1 /src ext4 defaults,discard0 0 With this configuration, the disk cannot be found when the name changes, which happens with the 5.3 kernel. Here is an example of /proc/partition when booting the 5.3 kernel(On this boot, the disk name changed to sdb): major minor #blocks name 80 67108864 sda 81 67107776 sda1 8 16 1072693248 sdb 8 17 1072692224 sdb1 8 32 31457280 sdc 8 33 31343599 sdc1 8 46 4096 sdc14 8 47 108544 sdc15 Here is what happens on every boot with the 5.0 kernel(Note the name is sdc, as expected, and always stays sdc): major minor #blocks name 80 31457280 sda 81 31343599 sda1 8 14 4096 sda14 8 15 108544 sda15 8 16 67108864 sdb 8 17 67107776 sdb1 8 32 1072693248 sdc 8 33 1072692224 sdc1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1878492/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net
[Kernel-packages] [Bug 1883261] [NEW] [linux-azure] Two Fixes For kdump Over Network
Public bug reported:
Microsoft would like to request two kdump related fixes in all releases
supported on Azure. The two commits are:
c81992e7f4aa1 ("PCI: hv: Retry PCI bus D0 entry on invalid device state")
83cc3508ffaa6 ("PCI: hv: Fix the PCI HyperV probe failure path to release
resource properly")
These are in the virtual PCI driver for Hyper-V. The customer visible
symptom is that the network is not functional in the kdump kernel, so
the dump file must be stored on the local disk and cannot be written
over the network.
The problem only occurs when Accelerated Networking is enabled. It’s a
relatively obscure scenario, which is why the problem has not surfaced
before now. But we have an important customer who wants the “dump-file-
over-the-network” functionality to work.
** Affects: linux-azure (Ubuntu)
Importance: Undecided
Status: New
--
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/1883261
Title:
[linux-azure] Two Fixes For kdump Over Network
Status in linux-azure package in Ubuntu:
New
Bug description:
Microsoft would like to request two kdump related fixes in all
releases supported on Azure. The two commits are:
c81992e7f4aa1 ("PCI: hv: Retry PCI bus D0 entry on invalid device state")
83cc3508ffaa6 ("PCI: hv: Fix the PCI HyperV probe failure path to release
resource properly")
These are in the virtual PCI driver for Hyper-V. The customer visible
symptom is that the network is not functional in the kdump kernel, so
the dump file must be stored on the local disk and cannot be written
over the network.
The problem only occurs when Accelerated Networking is enabled. It’s
a relatively obscure scenario, which is why the problem has not
surfaced before now. But we have an important customer who wants the
“dump-file-over-the-network” functionality to work.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1883261/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1869996] Re: Hibernation can NOT work due to incorrect RESUME=
** Also affects: initramfs-tools
Importance: Undecided
Status: New
** No longer affects: initramfs-tools
** Also affects: linux-azure (Ubuntu)
Importance: Undecided
Status: New
--
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/1869996
Title:
Hibernation can NOT work due to incorrect RESUME=
Status in initramfs-tools package in Ubuntu:
New
Status in linux-azure package in Ubuntu:
New
Bug description:
In Ubuntu 18.04 I have the below 4 lines, but in Ubuntu 20.04 (dev
build) these lines are missing:
--- /usr/share/initramfs-tools/init2020-04-01 01:15:20.533208700 +
+++ /usr/share/initramfs-tools/init 2020-04-01 00:59:43.931655200 +
@@ -163,6 +163,10 @@
;;
resume=*)
RESUME="${x#resume=}"
+ case $RESUME in
+ UUID=*)
+RESUME="/dev/disk/by-uuid/${RESUME#UUID=}"
+ esac
;;
resume_offset=*)
resume_offset="${x#resume_offset=}"
As a result, hibernation can not work: the saved state in the swap
partition is lost and no resume happens.
The issue is: when I use the "resume=UUID=533b2cd9-31ac-449b-82ff-
014f09ab0a9c" kernel parameter for hibernation, due to the missing
lines, the variable 'resume' in a later place in "/usr/share
/initramfs-tools/init" is set to "UUID=533b2cd9-31ac-449b-82ff-
014f09ab0a9c" rather than "/dev/disk/by-uuid/533b2cd9-31ac-449b-82ff-
014f09ab0a9c". Next, in /usr/share/initramfs-tools/scripts/local-
premount/resume:
DEV=$(readlink "$resume")
DEV=/sys/class/block/${DEV##*/}/dev
if [ -r "$DEV" ]; then
read -r MAJMIN < "$DEV"
fi
if [ -z "$MAJMIN" ]; then
exit 1
fi
Here the 'readlink' will fail, so $DEV is not pointing to a valid device, and
then $MAJMIN is empty and
we "exit 1", so no resume can happen!
Not sure why the 4 lines are removed in Ubuntu 20.04...
PS, this is my version info:
root@localhost:~# dpkg-query -s initramfs-tools-core
Package: initramfs-tools-core
Status: install ok installed
Priority: optional
Section: utils
Installed-Size: 271
Maintainer: Ubuntu Developers
Architecture: all
Multi-Arch: foreign
Source: initramfs-tools
Version: 0.136ubuntu1
Replaces: initramfs-tools (<< 0.121~)
Depends: busybox-initramfs (>= 1:1.30.1-4ubuntu5~), initramfs-tools-bin (=
0.136ubuntu1), klibc-utils (>= 2.0.4-8~), cpio (>= 2.12), lz4, kmod, udev,
coreutils (>= 8.24), logsave | e2fsprogs (<< 1.45.3-1~)
Suggests: bash-completion
Breaks: busybox-initramfs (<< 1:1.30.1-4ubuntu5~), initramfs-tools (<< 0.121~)
Conffiles:
/etc/initramfs-tools/initramfs.conf 4ec999d424d01b9ca685e65ba0f22a13
Description: generic modular initramfs generator (core tools)
This package contains the mkinitramfs program that can be used to
create a bootable initramfs for a Linux kernel. The initramfs should
be loaded along with the kernel and is then responsible for mounting
the root filesystem and starting the main init system.
Original-Maintainer: Debian kernel team
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1869996/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1870189] [NEW] initramfs does not get loaded
Public bug reported:
A Gen-1 Ubuntu 19.10 VM on Azure was created and upgraded to Ubuntu
20.04 by “do-release-upgrade –d”.
Then the latest Ubuntu v5.6 kernel was installed from
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.6/. As soon as a
reboot was performed, a panic with the v5.6 kernel occured because the
rootfs can not be found.
It turns out by default, initramfs does not get loaded:
/boot/grub/grub.cfg:
menuentry 'Ubuntu' --class ubuntu --class gnu-linux --class gnu --class os
$menuentry_id_option 'gnulinux-simple-3d2737e8-
b95a-42bf-bac1-bb6fb4cda87f' {
…
if [ "${initrdfail}" = 1 ]; then
linux /boot/vmlinuz-5.6.0-050600-generic
root=PARTUUID=bc3d472f-401e-4774-affa-df1acba65a73 ro console=tty1
console=ttyS0 earlyprintk=ttyS0 ignore_loglevel sysrq_always_enabled
unknown_nmi_panic
initrd/boot/initrd.img-5.6.0-050600-generic
else
linux /boot/vmlinuz-5.6.0-050600-generic
root=PARTUUID=bc3d472f-401e-4774-affa-df1acba65a73 ro console=tty1
console=ttyS0 earlyprintk=ttyS0 ignore_loglevel sysrq_always_enabled
unknown_nmi_panic panic=-1
#Dexuan: here the initrd line is missing!
fi
initrdfail
}
As we can see, Ubuntu only uses the initrd.img if initrdfail=1. Normally,
initrdfail = 0, so when we boot the v5.6 kernel for the first time, we must hit
the “fail to mount rootfs” panic and the kernel will automatically reboot….
Also, the “initrdfail” here marks initrdfail=1, so when the kernel boots
for the 2nd time, the kernel should successfully boot up. Next, when
the kernel boots for the 3rd time, it panics again since the userspace
program resets initrdfail to 0, and next time when the kernel boots, it
can boot up successfully -- this “panic/success/panic/success” pattern
repeats forever…
The linux-azure kernels are not affected since they have the vmbus driver and
storage drivers built-in (i.e. “=y”):
/boot/config-5.3.0-1013-azure:CONFIG_HYPERV_STORAGE=y
/boot/config-5.3.0-1013-azure:CONFIG_HYPERV=y
/boot/config-5.4.0-1006-azure:CONFIG_HYPERV_STORAGE=y
/boot/config-5.4.0-1006-azure:CONFIG_HYPERV=y
/boot/config-5.6.0-050600-generic:CONFIG_HYPERV_STORAGE=m
/boot/config-5.6.0-050600-generic:CONFIG_HYPERV=m
The v5.6 kernel uses =m rather than =y, so is affected here.
It looks the setting may be intentional, but we should not assume a customer
kernel must have the necessary vmbus/storage drivers built-in.
This issue only happens to the Ubuntu Marketplace image (19.10 and maybe 19.04
as well?) on Azure.
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.
** Affects: grub2 (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux-azure (Ubuntu)
Importance: Undecided
Status: New
** Also affects: grub2 (Ubuntu)
Importance: Undecided
Status: New
--
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 in Ubuntu:
New
Status in linux-azure package in Ubuntu:
New
Bug description:
A Gen-1 Ubuntu 19.10 VM on Azure was created and upgraded to Ubuntu
20.04 by “do-release-upgrade –d”.
Then the latest Ubuntu v5.6 kernel was installed from
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.6/. As soon as a
reboot was performed, a panic with the v5.6 kernel occured because the
rootfs can not be found.
It turns out by default, initramfs does not get loaded:
/boot/grub/grub.cfg:
menuentry 'Ubuntu' --class ubuntu --class gnu-linux --class gnu --class os
$menuentry_id_option 'gnulinux-simple-3d2737e8-
b95a-42bf-bac1-bb6fb4cda87f' {
…
if [ "${initrdfail}" = 1 ]; then
linux /boot/vmlinuz-5.6.0-050600-generic
root=PARTUUID=bc3d472f-401e-4774-affa-df1acba65a73 ro console=tty1
console=ttyS0 earlyprintk=ttyS0 ignore_loglevel sysrq_always_enabled
unknown_nmi_panic
initrd/boot/initrd.img-5.6.0-050600-generic
else
linux /boot/vmlinuz-5.6.0-050600-generic
root=PARTUUID=bc3d472f-401e-4774-affa-df1acba65a73 ro console=tty1
console=ttyS0 earlyprintk=ttyS0 ignore_loglevel sysrq_always_enabled
unknown_nmi_panic panic=-1
#Dexuan: here the initrd line is missing!
fi
initrdfail
}
As we can see, Ubuntu only uses the initrd.img if initrdfail=1. Normally,
initrdfail = 0, so when we boot the v5.6 kernel for the first time, we must hit
the “fail to mount rootfs” panic and the kernel will automatically reboot….
Also, the “initrdfail” here marks initrdfail=1, so when the kernel
boots for the 2nd time, the kernel should successfully boot up. Next,
when the kernel boots for the 3rd time, it panics again since the
userspace program resets initrdfail to 0, and next time when the
kernel bo
[Kernel-packages] [Bug 1874503] [NEW] Mellanox Check For Write Combining Support
Public bug reported: Microsoft and Mellanox would like to request the following two commits in the releases that run on Azure: 3f89b01f4bba IB/mlx5: Align usage of QP1 create flags with rest of mlx5 defines 11f552e21755 IB/mlx5: Test write combining support These commits landed in mainline as of v5.5-rc1. These commits will improved network performance of RDMA out of the VF when WC can be used. The highest benefit is to RDMA and DPDK, but UCX should also see improved latency. The Mellanox driver uses WC to optimize posting work to the HCA, and getting this wrong in either direction can cause a significant performance loss. These patches prevent the possible performance loss. ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: New -- 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/1874503 Title: Mellanox Check For Write Combining Support Status in linux-azure package in Ubuntu: New Bug description: Microsoft and Mellanox would like to request the following two commits in the releases that run on Azure: 3f89b01f4bba IB/mlx5: Align usage of QP1 create flags with rest of mlx5 defines 11f552e21755 IB/mlx5: Test write combining support These commits landed in mainline as of v5.5-rc1. These commits will improved network performance of RDMA out of the VF when WC can be used. The highest benefit is to RDMA and DPDK, but UCX should also see improved latency. The Mellanox driver uses WC to optimize posting work to the HCA, and getting this wrong in either direction can cause a significant performance loss. These patches prevent the possible performance loss. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1874503/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1875456] [NEW] Azure diagnostic/serviceability improvement
Public bug reported:
Microsoft would like to request the inclusion of commits in all releases
supported on Azure. These commits will enable reporting 4 Kbytes of
dmesg information to Hyper-V when Linux takes a panic.
Microsoft would like to get all releases reporting this information, so
that we can automatically get a rich picture of Linux panics in Azure.
This will limit the need get serial console logs or other steps to
manually acquire debug info.
We would like to request the folloiwng commits to enable the
diagnostic/serviceability improvement:
f3a99e761efa ("x86/Hyper-V: Report crash data in die() when panic_on_oops is
set")
040026df7088 ("x86/Hyper-V: Report crash register data when
sysctl_record_panic_msg is not set")
a11589563e96 ("x86/Hyper-V: Report crash register data or kmsg before running
crash kernel")
73f26e526f19 ("x86/Hyper-V: Trigger crash enlightenment only once during system
crash.")
7f11a2cc10a4 ("x86/Hyper-V: Free hv_panic_page when fail to register kmsg dump")
74347a99e73a ("x86/Hyper-V: Unload vmbus channel in hv panic callback")
8afc06dd75c0 ("Drivers: hv: vmbus: Fix the issue with freeing up
hv_ctl_table_hdr")
ddcaf3ca4c3c ("Drivers: hv: vmus: Fix the check for return value from kmsg get
dump buffer")
81b18bce48af ("Drivers: HV: Send one page worth of kmsg dump over Hyper-V
during panic")
7ed4325a44ea ("Drivers: hv: vmbus: Make panic reporting to be more useful")
** Affects: linux-azure (Ubuntu)
Importance: Undecided
Status: New
--
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/1875456
Title:
Azure diagnostic/serviceability improvement
Status in linux-azure package in Ubuntu:
New
Bug description:
Microsoft would like to request the inclusion of commits in all
releases supported on Azure. These commits will enable reporting 4
Kbytes of dmesg information to Hyper-V when Linux takes a panic.
Microsoft would like to get all releases reporting this information,
so that we can automatically get a rich picture of Linux panics in
Azure. This will limit the need get serial console logs or other
steps to manually acquire debug info.
We would like to request the folloiwng commits to enable the
diagnostic/serviceability improvement:
f3a99e761efa ("x86/Hyper-V: Report crash data in die() when panic_on_oops is
set")
040026df7088 ("x86/Hyper-V: Report crash register data when
sysctl_record_panic_msg is not set")
a11589563e96 ("x86/Hyper-V: Report crash register data or kmsg before running
crash kernel")
73f26e526f19 ("x86/Hyper-V: Trigger crash enlightenment only once during
system crash.")
7f11a2cc10a4 ("x86/Hyper-V: Free hv_panic_page when fail to register kmsg
dump")
74347a99e73a ("x86/Hyper-V: Unload vmbus channel in hv panic callback")
8afc06dd75c0 ("Drivers: hv: vmbus: Fix the issue with freeing up
hv_ctl_table_hdr")
ddcaf3ca4c3c ("Drivers: hv: vmus: Fix the check for return value from kmsg
get dump buffer")
81b18bce48af ("Drivers: HV: Send one page worth of kmsg dump over Hyper-V
during panic")
7ed4325a44ea ("Drivers: hv: vmbus: Make panic reporting to be more useful")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1875456/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1875467] [NEW] Enable Invariant TSC Support
Public bug reported:
Microsoft would like to request two commits in all releases supported on
Azure. These commits benefit SAP workloads.
These requested commits will enable support for Invariant TSC in Linux
guest VMs. The invariant TSC means that the TSC continues at a fixed
rate regardless of the C-state or frequency of the processor (as long as
the processor remains in the ACPI S0 state).
These patches will allow guests to access the
HvSyntheticInvariantTscControl MSR and set bit 0 of this synthetic MSR,
which then enables the InvariantTSC feature. After setting the
synthetic MSR, CPUID will enumerate support for InvariantTSC.
The following two commits enable support:
9e0333ae38ee ("clocksource/drivers/hyper-v: Set TSC clocksource as default w/
InvariantTSC")
dce7cd62754b ("x86/hyperv: Allow guests to enable InvariantTSC")
** Affects: linux-azure (Ubuntu)
Importance: Undecided
Status: New
--
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/1875467
Title:
Enable Invariant TSC Support
Status in linux-azure package in Ubuntu:
New
Bug description:
Microsoft would like to request two commits in all releases supported
on Azure. These commits benefit SAP workloads.
These requested commits will enable support for Invariant TSC in Linux
guest VMs. The invariant TSC means that the TSC continues at a fixed
rate regardless of the C-state or frequency of the processor (as long
as the processor remains in the ACPI S0 state).
These patches will allow guests to access the
HvSyntheticInvariantTscControl MSR and set bit 0 of this synthetic
MSR, which then enables the InvariantTSC feature. After setting the
synthetic MSR, CPUID will enumerate support for InvariantTSC.
The following two commits enable support:
9e0333ae38ee ("clocksource/drivers/hyper-v: Set TSC clocksource as default w/
InvariantTSC")
dce7cd62754b ("x86/hyperv: Allow guests to enable InvariantTSC")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1875467/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1876770] [NEW] speed for CX4 VF showing as unknown in ethtool output
Public bug reported:
While deploying a VM in D series (D8S_V3 and D16S_V3) and enabling
accelerated networking, MLX5 drivers are getting installed. However,
accelerated networking is not showing as enabled in guest OS. The same
VM is showing enabled from portal.
The problem is in the Mellanox driver for the CX-4 VF. Mellanox has already
fixed the problem in three separate patches, which are all in mainline.
We would like to request the following three commits in all supported
releases:
2f5438ca0ee0 ("net/mlx5: Tidy up and fix reverse christmas ordring")
c268ca6087f5 ("net/mlx5: Expose port speed when possible")
dc392fc56f39 ("net/mlx5: Expose link speed directly")
** Affects: linux-azure (Ubuntu)
Importance: Undecided
Status: New
--
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/1876770
Title:
speed for CX4 VF showing as unknown in ethtool output
Status in linux-azure package in Ubuntu:
New
Bug description:
While deploying a VM in D series (D8S_V3 and D16S_V3) and enabling
accelerated networking, MLX5 drivers are getting installed. However,
accelerated networking is not showing as enabled in guest OS. The same
VM is showing enabled from portal.
The problem is in the Mellanox driver for the CX-4 VF. Mellanox has already
fixed the problem in three separate patches, which are all in mainline.
We would like to request the following three commits in all supported
releases:
2f5438ca0ee0 ("net/mlx5: Tidy up and fix reverse christmas ordring")
c268ca6087f5 ("net/mlx5: Expose port speed when possible")
dc392fc56f39 ("net/mlx5: Expose link speed directly")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1876770/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877647] Re: Make sched clock return nanoseconds correctly
I see the fix is already included in Focal, from a different commit.
This bug can be closed.
--
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/1877647
Title:
Make sched clock return nanoseconds correctly
Status in linux-azure package in Ubuntu:
New
Status in linux-azure source package in Focal:
In Progress
Bug description:
The problem was introduced in Linux kernel version 5.4, and was fixed
in 5.6. So only users of the 5.4 and 5.5 kernels will see this
problem, which means Ubuntu 20.04 at the moment.
The fix was backported to upstream stable 5.4, so it should be picked
up via stable updates. This bug is primary to ensure the fix is not
missed.
The commit to fix this issue is:
749da8ca978f ("clocksource/drivers/hyper-v: Make sched clock return
nanoseconds correctly")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1877647/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877647] Re: Make sched clock return nanoseconds correctly
For reference, the other commit that fixed this is:
e4a58cdd069e6 ("clocksource/drivers/hyper-v: Untangle stimers and timesync from
clocksources")
--
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/1877647
Title:
Make sched clock return nanoseconds correctly
Status in linux-azure package in Ubuntu:
New
Status in linux-azure source package in Focal:
In Progress
Bug description:
The problem was introduced in Linux kernel version 5.4, and was fixed
in 5.6. So only users of the 5.4 and 5.5 kernels will see this
problem, which means Ubuntu 20.04 at the moment.
The fix was backported to upstream stable 5.4, so it should be picked
up via stable updates. This bug is primary to ensure the fix is not
missed.
The commit to fix this issue is:
749da8ca978f ("clocksource/drivers/hyper-v: Make sched clock return
nanoseconds correctly")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1877647/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1880032] [NEW] [linux-azure] Enable Hibernation on The 18.04 and 20.04 5.4 Kernels
Public bug reported: Microsoft would like to request commits to enable VM hibernation in the Azure 5.4 kernels for 18.04 and 20.04. Some of the commits needed to enable VM hibernation were included in mainline 5.4 and older. However, 24 commits were added in 5.5 and later, which are required in the 5.4 kernel. The list of commits requested are: 38dce4195f0dx86/hyperv: Properly suspend/resume reenlightenment notifications 2351f8d295edPM: hibernate: Freeze kernel threads in software_resume() 421f090c819dx86/hyperv: Suspend/resume the VP assist page for hibernation 1a06d017fb3fDrivers: hv: vmbus: Fix Suspend-to-Idle for Generation-2 VM 3704a6a44579PM: hibernate: Propagate the return value of hibernation_restore() 54e19d34011fhv_utils: Add the support of hibernation ffd1d4a49336hv_utils: Support host-initiated hibernation request 3e9c72056ed5hv_utils: Support host-initiated restart request 9fc3c01a1fae6 Tools: hv: Reopen the devices if read() or write() returns 05bd330a7fd8x86/hyperv: Suspend/resume the hypercall page for hibernation 382a46221757video: hyperv_fb: Fix hibernation for the deferred IO feature e2379b30324cInput: hyperv-keyboard: Add the support of hibernation ac82fc8327088 PCI: hv: Add hibernation support a8e37506e79aPCI: hv: Reorganize the code in preparation of hibernation 1349401ff1aa4 clocksource/drivers/hyper-v: Suspend/resume Hyper-V clocksource for hibernation af13f9ed6f9aHID: hyperv: Add the support of hibernation 25bd2b2f1f053 hv_balloon: Add the support of hibernation b96f86534fa31 x86/hyperv: Implement hv_is_hibernation_supported() 4df4cb9e99f83 x86/hyperv: Initialize clockevents earlier in CPU onlining 0efeea5fb1535 hv_netvsc: Add the support of hibernation 2194c2eb6717f hv_sock: Add the support of hibernation 1ecf302021040 video: hyperv_fb: Add the support of hibernation 56fb105859345 scsi: storvsc: Add the support of hibernation f2c33ccacb2d4 PCI/PM: Always return devices to D0 when thawing ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: New -- 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/1880032 Title: [linux-azure] Enable Hibernation on The 18.04 and 20.04 5.4 Kernels Status in linux-azure package in Ubuntu: New Bug description: Microsoft would like to request commits to enable VM hibernation in the Azure 5.4 kernels for 18.04 and 20.04. Some of the commits needed to enable VM hibernation were included in mainline 5.4 and older. However, 24 commits were added in 5.5 and later, which are required in the 5.4 kernel. The list of commits requested are: 38dce4195f0d x86/hyperv: Properly suspend/resume reenlightenment notifications 2351f8d295ed PM: hibernate: Freeze kernel threads in software_resume() 421f090c819d x86/hyperv: Suspend/resume the VP assist page for hibernation 1a06d017fb3f Drivers: hv: vmbus: Fix Suspend-to-Idle for Generation-2 VM 3704a6a44579 PM: hibernate: Propagate the return value of hibernation_restore() 54e19d34011f hv_utils: Add the support of hibernation ffd1d4a49336 hv_utils: Support host-initiated hibernation request 3e9c72056ed5 hv_utils: Support host-initiated restart request 9fc3c01a1fae6 Tools: hv: Reopen the devices if read() or write() returns 05bd330a7fd8 x86/hyperv: Suspend/resume the hypercall page for hibernation 382a46221757 video: hyperv_fb: Fix hibernation for the deferred IO feature e2379b30324c Input: hyperv-keyboard: Add the support of hibernation ac82fc8327088 PCI: hv: Add hibernation support a8e37506e79a PCI: hv: Reorganize the code in preparation of hibernation 1349401ff1aa4 clocksource/drivers/hyper-v: Suspend/resume Hyper-V clocksource for hibernation af13f9ed6f9a HID: hyperv: Add the support of hibernation 25bd2b2f1f053 hv_balloon: Add the support of hibernation b96f86534fa31 x86/hyperv: Implement hv_is_hibernation_supported() 4df4cb9e99f83 x86/hyperv: Initialize clockevents earlier in CPU onlining 0efeea5fb1535 hv_netvsc: Add the support of hibernation 2194c2eb6717f hv_sock: Add the support of hibernation 1ecf302021040 video: hyperv_fb: Add the support of hibernation 56fb105859345 scsi: storvsc: Add the support of hibernation f2c33ccacb2d4 PCI/PM: Always return devices to D0 when thawing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1880032/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856375] Re: [linux-azure] Request to autoload mlx4/mlx5 modules for DPDK
Additional conversations for the bug are happening in bug 1874544 -- 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/1856375 Title: [linux-azure] Request to autoload mlx4/mlx5 modules for DPDK Status in linux-azure package in Ubuntu: New Bug description: Ubuntu 18.04 images in the marketplace do not automatically load the required mlx drivers. (mlx4_ib|mlx5_ib and mlx4_en|mlx5_en) Someone trying DPDK on Ubuntu 18.04 has raised an issue on Azure DPDK document(https://github.com/MicrosoftDocs/azure-docs/issues/44303). To reproduce, bring up an ubuntu 18.04 VM on Azure. There you can see only mlx4_en but not the other one(mlx4_ib): # lsmod | grep mlx4 mlx4_en 118784 0 mlx4_core 294912 1 mlx4_en We would expect there to be 4 kernel modules loaded such as: mlx[4|5]_ib, rdma_cm, rdma_ucm, and ib_ipoib To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1856375/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1880975] [NEW] Request to include two NUMA related commits in Azure kernels
Public bug reported:
Microsoft would like to request the following two commits in all
releases supported on Azure:
999dd956d838 ("PCI: hv: Add support for protocol 1.3 and support
PCI_BUS_RELATIONS2")
f9ad0f361cf3 ("PCI: hv: Decouple the func definition in hv_dr_state from VSP
message")
These two commits will add support for PCI protocol version 1.3. This
will allow the host to pass NUMA node information for devices on the
bus. Currently it is assumed the NUMA node is 0, which these patches
will correct. This functionality will provide an increase in
performance, especially for HPC and AI workloads.
** Affects: linux-azure (Ubuntu)
Importance: Undecided
Status: New
--
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/1880975
Title:
Request to include two NUMA related commits in Azure kernels
Status in linux-azure package in Ubuntu:
New
Bug description:
Microsoft would like to request the following two commits in all
releases supported on Azure:
999dd956d838 ("PCI: hv: Add support for protocol 1.3 and support
PCI_BUS_RELATIONS2")
f9ad0f361cf3 ("PCI: hv: Decouple the func definition in hv_dr_state from VSP
message")
These two commits will add support for PCI protocol version 1.3. This
will allow the host to pass NUMA node information for devices on the
bus. Currently it is assumed the NUMA node is 0, which these patches
will correct. This functionality will provide an increase in
performance, especially for HPC and AI workloads.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1880975/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881662] [NEW] Add Description To Hyper-V Modules
Public bug reported:
There are three modules where no description exists causing issues
during a customers certification test:
hid_hyperv
hyperv_keyboard
hv_vmbus
Three patches exist upstream which fix this issue. The mainline commits
are:
64caea53e07f ("HID: hyperv: Add a module description line")
674eecb3d35a ("drivers: hv: Add a module description line to the hv_vmbus
driver")
9d1c2f067e50 ("Input: hyperv-keyboard - add module description")
Can you pull these commits into all releases that are supported on
Azure?
** Affects: linux-azure (Ubuntu)
Importance: Undecided
Status: New
--
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/1881662
Title:
Add Description To Hyper-V Modules
Status in linux-azure package in Ubuntu:
New
Bug description:
There are three modules where no description exists causing issues
during a customers certification test:
hid_hyperv
hyperv_keyboard
hv_vmbus
Three patches exist upstream which fix this issue. The mainline
commits are:
64caea53e07f ("HID: hyperv: Add a module description line")
674eecb3d35a ("drivers: hv: Add a module description line to the hv_vmbus
driver")
9d1c2f067e50 ("Input: hyperv-keyboard - add module description")
Can you pull these commits into all releases that are supported on
Azure?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1881662/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881787] Re: High rate of packet loss upgrading to kernel 5.3 and later.
** Also affects: linux-azure (Ubuntu) Importance: Undecided Status: New -- 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/1881787 Title: High rate of packet loss upgrading to kernel 5.3 and later. Status in linux-azure package in Ubuntu: New Status in linux-meta-azure-5.3 package in Ubuntu: New Bug description: Performing testing on Ubuntu 18.04 LTS and Ubuntu 20.04 LTS. Setup: ocserv built from https://gitlab.com/openconnect/ocserv.git @ 59bdd070b6b9f893d3f552b6a8895a5f4eb014da, running in Docker container built from Ubuntu 18.04 Docker image. Test: 1000 clients connected using openconnect (https://gitlab.com/openconnect/openconnect) (clients spread across 54 VMs, each client running in a Docker container for network isolation) Simulating 3 workloads: 1) IM traffic - (TCP, with server echoing the stream and client sending [1,1024] bytes every [2500,7500]ms) 2) Audio streaming - (UDP, with server sending 128kbps, sending packets 60 times per second) 3) web-browser - (Loading of 3mb web-page, with 11 elements requiring separate HTTP gets, reloading every 60 seconds.) Results: Ubuntu 18.04 / Linux kernel version 4.15.0-101-generic (buildd@lgw01-amd64-003)) - less than 1% packet loss. Ubuntu 18.04 / Linux kernel version 5.3.0-1022-azure (buildd@lcy01-amd64-001)) - 9% packet loss. Ubuntu 20.04 / Linux kernel version 5.4.0-33 - 9% packet loss. Tested on both 18.04 and 20.04 VM running on Hyper-V and on a bare- metal install of Ubuntu 20.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1881787/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1879559] Re: net/bpfilter: remove superfluous testing message
This message can be ignored. This bogus "testing the buffer" message is
something that inadvertently got into upstream code via commit:
13d0f7b814d9 net/bpfilter: fix dprintf usage for /dev/kmsg
This message is fixed by the following commit:
41c55ea6c2a7 net/bpfilter: remove superfluous testing message
The fix will be in the Ubuntu kernel version: Ubuntu-
azure-5.3-5.3.0-1023.24
--
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/1879559
Title:
net/bpfilter: remove superfluous testing message
Status in linux package in Ubuntu:
Incomplete
Status in linux-hwe-5.0 package in Ubuntu:
Confirmed
Bug description:
[Impact]
A testing message was brought by 13d0f7b814d9 ("net/bpfilter: fix dprintf
usage for /dev/kmsg") but should've been deleted before patch submission.
Although it doesn't cause any harm to the code or functionality itself, it's
totally unpleasant to have it displayed on every loop iteration with no real
use case. Thus remove it unconditionally.
Upstream fix: 41c55ea6c2a7ca4c663eeec05bdf54f4e2419699
[Test Case]
Just check dmesg:
[ 10.635382] hv_utils: VSS: userspace daemon ver. 129 connected
[ 15.306015] bpfilter: Loaded bpfilter_umh pid 1036
[ 15.306280] Started bpfilter
[ 15.306283] testing the buffer
[ 15.306458] testing the buffer
[ 15.306880] testing the buffer
[ 15.318003] testing the buffer
[ 15.318057] testing the buffer
[ 15.318814] testing the buffer
[ 15.442147] testing the buffer
[ 15.479556] testing the buffer
[ 15.479572] testing the buffer
[Regression Potential]
Very low. The fix is a one line upstream patch that removes one
printf.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879559/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882268] [NEW] [linux-azure] Request for two CIFS commits in 16.04
Public bug reported:
There was a previous bug requesting the following two commits in 18.04:
84a1f5b1cc6f ("cifs: Fix potential softlockups while refreshing DFS cache")
2084ed57167c ("CIFS: Only send SMB2_NEGOTIATE command on new TCP connections")
There is an issue now, which requires these commits in the 4.15 based
16.04 kernel.
Can these two commits be applied to 16.04?
** Affects: linux-azure (Ubuntu)
Importance: Undecided
Status: New
--
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/1882268
Title:
[linux-azure] Request for two CIFS commits in 16.04
Status in linux-azure package in Ubuntu:
New
Bug description:
There was a previous bug requesting the following two commits in
18.04:
84a1f5b1cc6f ("cifs: Fix potential softlockups while refreshing DFS cache")
2084ed57167c ("CIFS: Only send SMB2_NEGOTIATE command on new TCP connections")
There is an issue now, which requires these commits in the 4.15 based
16.04 kernel.
Can these two commits be applied to 16.04?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1882268/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863951] [NEW] [linux-azure] Missing user mode io driver - uio_pci_generic
Public bug reported: After creating a Lv2 VM (OS - ubuntu 18.04) it was found that uio_pci_generic is missing. It is needed to attach SPDK to nvme disk. The kernel build config file that Canonical provides in Ubuntu 18.04 images shows CONFIG_UIO_PCI_GENERIC=m, indicating that the module was built. However, the module is not included in the image. Is there a reason why the uio_pci_generic module is not included in the Azure Marketplace image? If not, can we get it added back in? ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: New -- 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/1863951 Title: [linux-azure] Missing user mode io driver - uio_pci_generic Status in linux-azure package in Ubuntu: New Bug description: After creating a Lv2 VM (OS - ubuntu 18.04) it was found that uio_pci_generic is missing. It is needed to attach SPDK to nvme disk. The kernel build config file that Canonical provides in Ubuntu 18.04 images shows CONFIG_UIO_PCI_GENERIC=m, indicating that the module was built. However, the module is not included in the image. Is there a reason why the uio_pci_generic module is not included in the Azure Marketplace image? If not, can we get it added back in? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1863951/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864233] [NEW] Commits to resolve high network latency
Public bug reported:
An issue has been identified with the NETVSC driver on Azure VMs. This
issues has been fixed by four patches, which are available in the
mainline kernel.
The issues is the following:
Outgoing traffic is sent from the guest to the Azure host over multiple
parallel channels. The issue causes the traffic to be unevenly balanced across
the channels, which results in a physical CPU on the Azure host becoming
overloaded. In turn, the network traffic on the overloaded channel experiences
significantly higher latency. This higher latency is causing issues for
customers.
This issue is resolved by the following four mainline commits:
71f21959dd55 ("hv_netvsc: Fix offset usage in netvsc_send_table()")
171c1fd98df3 ("hv_netvsc: Fix send_table offset in case of a host bug")
c39ea5cba5a2 ("hv_netvsc: Fix tx_table init in rndis_set_subchannel()")
b0689faa8efc ("hv_netvsc: Fix unwanted rx_table reset")
These four commits have been submitted to upstream stable.
We would like to request these commits in Azure kernels for Xenial and
Bionic
** Affects: linux-azure (Ubuntu)
Importance: Undecided
Status: New
--
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/1864233
Title:
Commits to resolve high network latency
Status in linux-azure package in Ubuntu:
New
Bug description:
An issue has been identified with the NETVSC driver on Azure VMs. This
issues has been fixed by four patches, which are available in the
mainline kernel.
The issues is the following:
Outgoing traffic is sent from the guest to the Azure host over multiple
parallel channels. The issue causes the traffic to be unevenly balanced across
the channels, which results in a physical CPU on the Azure host becoming
overloaded. In turn, the network traffic on the overloaded channel experiences
significantly higher latency. This higher latency is causing issues for
customers.
This issue is resolved by the following four mainline commits:
71f21959dd55 ("hv_netvsc: Fix offset usage in netvsc_send_table()")
171c1fd98df3 ("hv_netvsc: Fix send_table offset in case of a host bug")
c39ea5cba5a2 ("hv_netvsc: Fix tx_table init in rndis_set_subchannel()")
b0689faa8efc ("hv_netvsc: Fix unwanted rx_table reset")
These four commits have been submitted to upstream stable.
We would like to request these commits in Azure kernels for Xenial and
Bionic
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1864233/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864669] [NEW] [linux-azure] overlayfs regression - internal getxattr operations without sepolicy checking
Public bug reported:
Bug description and repro:
Run the following commands on host instances:
Prepare the overlayfs directories:
$ cd /tmp
$ mkdir -p base/dir1/dir2 upper olwork merged
$ touch base/dir1/dir2/file
$ chown -R 10:10 base upper olwork merged
Verify that the directory is owned by user 10:
$ ls -al merged/
total 8
drwxr-xr-x 2 10 10 4096 Nov 1 07:08 .
drwxrwxrwt 16 root root 4096 Nov 1 07:08 ..
We use lxc-usernsexec to start a new shell as user 10.
$ lxc-usernsexec -m b:0:10:1 -- /bin/bash
$$ ls -al merged/
total 8
drwxr-xr-x 2 root root4096 Nov 1 07:08 .
drwxrwxrwt 16 nobody nogroup 4096 Nov 1 07:08 ..
Notice that the ownership of . and .. has changed because the new shell is
running as the remapped user.
Now, mount the overlayfs as an unprivileged user in the new shell. This is the
key to trigger the bug.
$$ mount -t overlay -o lowerdir=base,upperdir=upper,workdir=olwork none merged
$$ ls -al merged/dir1/dir2/file
-rw-r--r-- 1 root root 0 Nov 1 07:09 merged/dir1/dir2/file
We can see the file in the base layer from the mount directory. Now trigger the
bug:
$$ rm -rf merged/dir1/dir2/
$$ mkdir merged/dir1/dir2
$$ ls -al merged/dir1/dir2
total 12
drwxr-xr-x 2 root root 4096 Nov 1 07:10 .
drwxr-xr-x 1 root root 4096 Nov 1 07:10 ..
File does not show up in the newly created dir2 as expected. But it will
reappear after we remount the filesystem (or any other means that might evict
the cached dentry, such as attempt to delete the parent directory):
$$ umount merged
$$ mount -t overlay -o lowerdir=base,upperdir=upper,workdir=olwork none merged
$$ ls -al merged/dir1/dir2
total 12
drwxr-xr-x 1 root root 4096 Nov 1 07:10 .
drwxr-xr-x 1 root root 4096 Nov 1 07:10 ..
-rw-r--r-- 1 root root0 Nov 1 07:09 file
$$ exit
$
This is a recent kernel regression. I tried the above step on an old
kernel (4.4.0-1072-aws) but cannot reproduce.
I looked up linux source code and figured out where the "regression" is coming
from. The issue lies in how overlayfs checks the "opaque" flag from the
underlying upper-level filesystem. It checks the "trusted.overlay.opaque"
extended attribute to decide whether to hide the directory content from the
lower level. The logic are different in 4.4 and 4.15 kernel.
In 4.4: https://elixir.bootlin.com/linux/v4.4/source/fs/overlayfs/super.c#L255
static bool ovl_is_opaquedir(struct dentry *dentry)
{
int res;
char val;
struct inode *inode = dentry->d_inode;
if (!S_ISDIR(inode->i_mode) || !inode->i_op->getxattr)
return false;
res = inode->i_op->getxattr(dentry, OVL_XATTR_OPAQUE, &val, 1);
if (res == 1 && val == 'y')
return true;
return false;
}
In 4.15: https://elixir.bootlin.com/linux/v4.15/source/fs/overlayfs/util.c#L349
static bool ovl_is_opaquedir(struct dentry *dentry)
{
return ovl_check_dir_xattr(dentry, OVL_XATTR_OPAQUE);
}
bool ovl_check_dir_xattr(struct dentry *dentry, const char *name)
{
int res;
char val;
if (!d_is_dir(dentry))
return false;
res = vfs_getxattr(dentry, name, &val, 1);
if (res == 1 && val == 'y')
return true;
return false;
}
The 4.4 version simply uses the internal i_node callback inode->i_op->getxattr
from the host filesystem, which doesn't perform any permission check. While the
4.15 version calls the VFS interface vfs_getxattr that performs bunch of
permission checks before the calling the internal insecure callback
__vfs_getxattr:
See https://elixir.bootlin.com/linux/v4.15/source/fs/xattr.c#L317
ssize_t
vfs_getxattr(struct dentry *dentry, const char *name, void *value, size_t size)
{
struct inode *inode = dentry->d_inode;
int error;
error = xattr_permission(inode, name, MAY_READ);
if (error)
return error;
error = security_inode_getxattr(dentry, name);
if (error)
return error;
if (!strncmp(name, XATTR_SECURITY_PREFIX,
XATTR_SECURITY_PREFIX_LEN)) {
const char *suffix = name + XATTR_SECURITY_PREFIX_LEN;
int ret = xattr_getsecurity(inode, suffix, value, size);
/*
* Only overwrite the return value if a security module
* is actually active.
*/
if (ret == -EOPNOTSUPP)
goto nolsm;
return ret;
}
nolsm:
return __vfs_getxattr(dentry, inode, name, value, size);
}
In 4.15, ovl_is_opaquedir is called by the following caller:
ovl_is_opaquedir <-
ovl_lookup_single() <-
ovl_lookup_layer <-
ovl_lookup,
ovl_lookup is the entry point for directory listing in overlayfs. Importantly,
it assumes the filesystem mounter's credential to perform all internal lookup
operations:
struct dentry *ovl_lookup(struct inode *dir, struct dentry *de
[Kernel-packages] [Bug 1866407] [NEW] GPU Driver extension issue (NVIDIA)
Public bug reported: The Nvidia GPU driver cannot be installed for VM size Standard_NC6 but it is correctly installed for Standard_NV6. This is happening on Ubuntu Server 18.04 LTS. To repro this issue: 1. Create a Virtual Machine with image Ubuntu Server 18.04 LTS and size Standard_NC6 2. Add extension NvidiaGpuDriver and wait for it to fail 3. Connect to the VM and try to install following package sudo apt install -y xubuntu-desktop 4. You'll see how it is unable to install it and it suggests to run apt --fix-broken install but it doesn't work either. It should work accordingly to this doc https://docs.microsoft.com/en-us/azure/virtual-machines/extensions/hpccompute-gpu-Linux This may be related to an older bug for an older Nvidia version: bug 1753796 ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: New -- 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/1866407 Title: GPU Driver extension issue (NVIDIA) Status in linux-azure package in Ubuntu: New Bug description: The Nvidia GPU driver cannot be installed for VM size Standard_NC6 but it is correctly installed for Standard_NV6. This is happening on Ubuntu Server 18.04 LTS. To repro this issue: 1. Create a Virtual Machine with image Ubuntu Server 18.04 LTS and size Standard_NC6 2. Add extension NvidiaGpuDriver and wait for it to fail 3. Connect to the VM and try to install following package sudo apt install -y xubuntu-desktop 4. You'll see how it is unable to install it and it suggests to run apt --fix-broken install but it doesn't work either. It should work accordingly to this doc https://docs.microsoft.com/en-us/azure/virtual-machines/extensions/hpccompute-gpu-Linux This may be related to an older bug for an older Nvidia version: bug 1753796 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1866407/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1866407] Re: GPU Driver extension issue (NVIDIA)
The following can be used as a work around: For new VM: Build VM without Nvidia Extension sudo apt-get -o Dpkg::Options::="--force-overwrite" install -y nvidia-440 Apply Nvidia Extension for Linux to VM Continue with setup For existing VM with failed installation: sudo apt-get -o Dpkg::Options::="--force-overwrite" install -y nvidia-440 sudo /var/lib/waagent/Microsoft.HpcCompute.NvidiaGpuDriverLinux-1.2.0.0/scripts/enable.sh Reboot Continue with remaining setup -- 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/1866407 Title: GPU Driver extension issue (NVIDIA) Status in linux-azure package in Ubuntu: New Bug description: The Nvidia GPU driver cannot be installed for VM size Standard_NC6 but it is correctly installed for Standard_NV6. This is happening on Ubuntu Server 18.04 LTS. To repro this issue: 1. Create a Virtual Machine with image Ubuntu Server 18.04 LTS and size Standard_NC6 2. Add extension NvidiaGpuDriver and wait for it to fail 3. Connect to the VM and try to install following package sudo apt install -y xubuntu-desktop 4. You'll see how it is unable to install it and it suggests to run apt --fix-broken install but it doesn't work either. It should work accordingly to this doc https://docs.microsoft.com/en-us/azure/virtual-machines/extensions/hpccompute-gpu-Linux This may be related to an older bug for an older Nvidia version: bug 1753796 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1866407/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848739] Re: [linux-azure] Patch to prevent possible data corruption
Yes we need that patch. The commit description is misleading, as this
commit actually fixes a bug on data corruption for SCSI devices.
In the latest Ubuntu 4.15 kernel, __blk_mq_try_issue_directly() (in
"block/blk-mq.c") calls blk_mq_sched_insert_request() if
q->mq_ops->queue_rq() returns BLK_STS_RESOURCE, this is not correct and
is prone to data corruption.
The c616cbee97ae has the following change:
@@ -1785,7 +1764,7 @@ static blk_status_t __blk_mq_try_issue_directly(struct
blk_mq_hw_ctx *hctx,
if (bypass_insert)
return BLK_STS_RESOURCE;
- blk_mq_sched_insert_request(rq, false, run_queue, false);
+ blk_mq_request_bypass_insert(rq, run_queue);
return BLK_STS_OK;
}
This change is subtle, now the I/O will not get merged with other
pending I/O if a direct issue has failed. This fixed the data corruption
for SCSI devices. The bug was not introduced by commit ffe81d45322c.
I recommend them pick up all the relevant patches leading to this
commit. If this is difficult we can do a special back ported patch to
change the code in __blk_mq_try_issue_directly() to handle requeue.
--
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/1848739
Title:
[linux-azure] Patch to prevent possible data corruption
Status in linux-azure package in Ubuntu:
New
Bug description:
There are three patches that prevent possible data corruption. The
three commits are:
aef1897cd36d ("blk-mq: insert rq with DONTPREP to hctx dispatch list when
requeue")
c616cbee97ae ("blk-mq: punt failed direct issue to dispatch list")
923218f6166a ("blk-mq: don't allocate driver tag upfront for flush rq")
18.04 has all three of these patches. 16.04 has two out of the three,
but it is missing commit c616cbee97ae.
We would like to request commit c616cbee97ae be included in the 16.04 kernel:
c616cbee97ae ("blk-mq: punt failed direct issue to dispatch list")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1848739/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1846485] [NEW] lttng causes crash with 5.0 based kernel
Public bug reported: There is a regression with the 5.0 based kernel. The following is the good and bad kernels: OS Status Kernel veriosn 18.04.201906170 BAD Linux nt100 5.0.0-1014-azure 18.04.201906040 GOOD Linux nt100 4.18.0-1020-azure The crash can be reproduced with this line: sudo apt-get install lttng-tools lttng-modules-dkms liblttng-ust0 The following trace occurs 2019/09/26 17:36:30.129283 INFO ExtHandler Stopped tracking cgroup: Microsoft.OSTCExtensions.LinuxDiagnostic-2.3.9029, path: /sys/fs/cgroup/cpu/system.slice/Microsoft.OSTCExtensions.LinuxDiagnostic_2.3.9029_fa19de8a-0c72-449e-9754-451dcef4340e.scope 2019/09/26 17:36:30.130284 INFO ExtHandler Stopped tracking cgroup: Microsoft.OSTCExtensions.LinuxDiagnostic-2.3.9029, path: /sys/fs/cgroup/memory/system.slice/Microsoft.OSTCExtensions.LinuxDiagnostic_2.3.9029_fa19de8a-0c72-449e-9754-451dcef4340e.scope [ 346.729298] PKCS#7 signature not signed with a trusted key [ 346.735782] PKCS#7 signature not signed with a trusted key [ 346.744261] PKCS#7 signature not signed with a trusted key [ 346.750132] PKCS#7 signature not signed with a trusted key [ 346.755284] PKCS#7 signature not signed with a trusted key [ 346.768389] PKCS#7 signature not signed with a trusted key [ 346.778232] BUG: unable to handle kernel paging request at 32a0 [ 346.778623] #PF error: [normal kernel read fault] [ 346.778623] PGD 0 P4D 0 [ 346.778623] Oops: [#1] SMP PTI [ 346.778623] CPU: 1 PID: 26741 Comm: lttng-sessiond Kdump: loaded Tainted: G OE 5.0.0-1018-azure #19~18.04.1-Ubuntu [ 346.778623] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090007 06/02/2017 [ 346.778623] RIP: 0010:lttng_tracepoint_notify+0x172/0x210 [lttng_tracer] [ 346.778623] Code: eb 1a 49 39 c6 0f 85 ab 00 00 00 49 8b 55 10 41 83 c4 01 44 39 a2 8c 02 00 00 76 a3 48 8b 92 90 02 00 00 49 63 c4 4c 63 34 82 <49> 8b 1e 48 89 df e8 33 fbff ff 48 85 c0 49 89 c7 74 52 49 8b 47 [ 346.795750] RSP: 0018:9d5382ecbbd8 EFLAGS: 00010246 [ 346.795750] RAX: RBX: 9183eb560040 RCX: 0005 [ 346.795750] RDX: c0042420 RSI: 0001 RDI: c0739100 [ 346.795750] RBP: 9d5382ecbc08 R08: 9183f6c660c0 R09: 9183f6807600 [ 346.795750] R10: 9d5382ecbb48 R11: R12: [ 346.795750] R13: 9183eb560040 R14: 32a0 R15: c0739740 [ 346.795750] FS: 7fd33176c980() GS:9183f6c4() knlGS: [ 346.795750] CS: 0010 DS: ES: CR0: 80050033 [ 346.795750] CR2: 32a0 CR3: 00025dec6003 CR4: 001606e0 [ 346.795750] Call Trace: [ 346.795750] register_tracepoint_module_notifier+0x57/0x80 [ 346.795750] ? 0xc0778000 [ 346.795750] lttng_tracepoint_init+0x45/0xc40 [lttng_tracer] [ 346.795750] lttng_events_init+0xbc/0x233 [lttng_tracer] [ 346.795750] ? 0xc0778000 [ 346.795750] do_one_initcall+0x4a/0x1be [ 346.795750] ? _cond_resched+0x19/0x40 [ 346.795750] ? kmem_cache_alloc_trace+0x151/0x1c0 [ 346.795750] do_init_module+0x5f/0x216 [ 346.795750] load_module+0x19f6/0x20a0 [ 346.795750] __do_sys_finit_module+0xfc/0x120 [ 346.795750] ? __do_sys_finit_module+0xfc/0x120 [ 346.795750] __x64_sys_finit_module+0x1a/0x20 [ 346.795750] do_syscall_64+0x61/0x190 [ 346.795750] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 346.795750] RIP: 0033:0x7fd32f9d7839 [ 346.795750] Code: 00 f3 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c348 8b 0d 1f f6 2c 00 f7 d8 64 89 01 48 [ 346.795750] RSP: 002b:7fff8a413f88 EFLAGS: 0246 ORIG_RAX: 0139 [ 346.795750] RAX: ffda RBX: 55e7fc7d1800 RCX: 7fd32f9d7839 [ 346.795750] RDX: RSI: 7fd331354145 RDI: 0018 [ 346.795750] RBP: 7fd331354145 R08: R09: 55e7fc7d5ac0 [ 346.795750] R10: 0018 R11: 0246 R12: [ 346.795750] R13: 55e7fc7d6120 R14: R15: 55e7fc7d5ac0 [ 346.795750] Modules linked in: lttng_tracer(OE+) lttng_statedump(OE) lttng_kprobes(OE) lttng_clock(OE) lttng_lib_ring_buffer(OE) lttng_kretprobes(OE) xt_owner xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_security bpfilter nls_iso8859_1 serio_raw hv_balloon joydev sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_pclmul crc32_pclmul ghash_clmulni_intel hid_generic aesni_intel aes_x86_64 crypto_simd cryptd glue_helper hid_hyperv hyperv_keyboardhid hv_utils hv_netvsc hyperv_fb cfbfillrect
[Kernel-packages] [Bug 1847139] [NEW] [linux-azure] Request of mainline commit f73f8a504e27 in azure 16.04 and 18.04
Public bug reported: Microsoft would like to request the following mainline commit be added to linux-azure 16.04 and 18.04: f73f8a504e27 PCI: hv: Use bytes 4 and 5 from instance ID as the PCI domain numbers This commit was added to mainline in v5.4-rc1~63^2~8^2 This was recommended by Azure host team, the bytes 4, 5 have more uniqueness(info entropy) than bytes 8, 9, so we should use them as the PCI domain numbers. This patch should be added to both 16.04 and 18.04 images. ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: New -- 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/1847139 Title: [linux-azure] Request of mainline commit f73f8a504e27 in azure 16.04 and 18.04 Status in linux-azure package in Ubuntu: New Bug description: Microsoft would like to request the following mainline commit be added to linux-azure 16.04 and 18.04: f73f8a504e27 PCI: hv: Use bytes 4 and 5 from instance ID as the PCI domain numbers This commit was added to mainline in v5.4-rc1~63^2~8^2 This was recommended by Azure host team, the bytes 4, 5 have more uniqueness(info entropy) than bytes 8, 9, so we should use them as the PCI domain numbers. This patch should be added to both 16.04 and 18.04 images. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1847139/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855461] [NEW] [linux-azure] SAUCE patch to "Fix skb protocol value in tpacket_fill_skb()"
Public bug reported: The actual fix for this issue would be to backport two related patches that were accepted upstream in Feb/March 2019. But doing a full backport is complicated because of dependencies on other new code. Instead of a full backport of these patches, a SAUCE patch was generated to avoid the complicated dependencies. The SAUCE patch is attached to the bug. Microsoft and the affected customer feel this patch is pretty small and safe. Microsoft and the end customer have tested the backport and confirmed that it solves the problem. Backports are needed for both the 4.15.0 and the 5.0 azure kernels that are used in Ubuntu 16.04 and Ubuntu 18.04 images in the Azure Marketplace. The customer is using the 4.15 kernel from Ubuntu 16.04, so getting this fix included there is fairly high priority, though not “critical/emergency” level. Getting the fix included in the 5.0 kernel in Ubuntu 18.04 in the Azure Marketplace is low priority. ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: New ** Patch added: "0001-af_packet-Fix-skb-protocol-value-in-tpacket_fill_skb.patch" https://bugs.launchpad.net/bugs/1855461/+attachment/5310261/+files/0001-af_packet-Fix-skb-protocol-value-in-tpacket_fill_skb.patch -- 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/1855461 Title: [linux-azure] SAUCE patch to "Fix skb protocol value in tpacket_fill_skb()" Status in linux-azure package in Ubuntu: New Bug description: The actual fix for this issue would be to backport two related patches that were accepted upstream in Feb/March 2019. But doing a full backport is complicated because of dependencies on other new code. Instead of a full backport of these patches, a SAUCE patch was generated to avoid the complicated dependencies. The SAUCE patch is attached to the bug. Microsoft and the affected customer feel this patch is pretty small and safe. Microsoft and the end customer have tested the backport and confirmed that it solves the problem. Backports are needed for both the 4.15.0 and the 5.0 azure kernels that are used in Ubuntu 16.04 and Ubuntu 18.04 images in the Azure Marketplace. The customer is using the 4.15 kernel from Ubuntu 16.04, so getting this fix included there is fairly high priority, though not “critical/emergency” level. Getting the fix included in the 5.0 kernel in Ubuntu 18.04 in the Azure Marketplace is low priority. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1855461/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855461] Re: [linux-azure] SAUCE patch to "Fix skb protocol value in tpacket_fill_skb()"
** Description changed:
The actual fix for this issue would be to backport two related patches
that were accepted upstream in Feb/March 2019. But doing a full
- backport is complicated because of dependencies on other new code.
+ backport is complicated because of dependencies on other new code. The
+ two upstream commits are:
+
+ 75c65772c3d1 ("net/packet: Ask driver for protocol if not provided by user")
+ 18bed89107a4 ("af_packet: fix the tx skb protocol in raw sockets with
ETH_P_ALL")
Instead of a full backport of these patches, a SAUCE patch was generated
to avoid the complicated dependencies. The SAUCE patch is attached to
the bug.
Microsoft and the affected customer feel this patch is pretty small and
safe. Microsoft and the end customer have tested the backport and
confirmed that it solves the problem.
Backports are needed for both the 4.15.0 and the 5.0 azure kernels that
are used in Ubuntu 16.04 and Ubuntu 18.04 images in the Azure
Marketplace. The customer is using the 4.15 kernel from Ubuntu 16.04,
so getting this fix included there is fairly high priority, though not
“critical/emergency” level. Getting the fix included in the 5.0 kernel
in Ubuntu 18.04 in the Azure Marketplace is low priority.
--
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/1855461
Title:
[linux-azure] SAUCE patch to "Fix skb protocol value in
tpacket_fill_skb()"
Status in linux-azure package in Ubuntu:
New
Bug description:
The actual fix for this issue would be to backport two related patches
that were accepted upstream in Feb/March 2019. But doing a full
backport is complicated because of dependencies on other new code.
The two upstream commits are:
75c65772c3d1 ("net/packet: Ask driver for protocol if not provided by user")
18bed89107a4 ("af_packet: fix the tx skb protocol in raw sockets with
ETH_P_ALL")
Instead of a full backport of these patches, a SAUCE patch was
generated to avoid the complicated dependencies. The SAUCE patch is
attached to the bug.
Microsoft and the affected customer feel this patch is pretty small
and safe. Microsoft and the end customer have tested the backport and
confirmed that it solves the problem.
Backports are needed for both the 4.15.0 and the 5.0 azure kernels
that are used in Ubuntu 16.04 and Ubuntu 18.04 images in the Azure
Marketplace. The customer is using the 4.15 kernel from Ubuntu 16.04,
so getting this fix included there is fairly high priority, though not
“critical/emergency” level. Getting the fix included in the 5.0
kernel in Ubuntu 18.04 in the Azure Marketplace is low priority.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1855461/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856375] [NEW] [linux-azure] Request to autoload mlx4/mlx5 modules for DPDK
Public bug reported: Ubuntu 18.04 images in the marketplace do not automatically load the required mlx drivers. (mlx4_ib|mlx5_ib and mlx4_en|mlx5_en) Someone trying DPDK on Ubuntu 18.04 has raised an issue on Azure DPDK document(https://github.com/MicrosoftDocs/azure-docs/issues/44303). To reproduce, bring up an ubuntu 18.04 VM on Azure. There you can see only mlx4_en but not the other one(mlx4_ib): # lsmod | grep mlx4 mlx4_en 118784 0 mlx4_core 294912 1 mlx4_en We would expect there to be 4 kernel modules loaded such as: mlx[4|5]_ib, rdma_cm, rdma_ucm, and ib_ipoib ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: New -- 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/1856375 Title: [linux-azure] Request to autoload mlx4/mlx5 modules for DPDK Status in linux-azure package in Ubuntu: New Bug description: Ubuntu 18.04 images in the marketplace do not automatically load the required mlx drivers. (mlx4_ib|mlx5_ib and mlx4_en|mlx5_en) Someone trying DPDK on Ubuntu 18.04 has raised an issue on Azure DPDK document(https://github.com/MicrosoftDocs/azure-docs/issues/44303). To reproduce, bring up an ubuntu 18.04 VM on Azure. There you can see only mlx4_en but not the other one(mlx4_ib): # lsmod | grep mlx4 mlx4_en 118784 0 mlx4_core 294912 1 mlx4_en We would expect there to be 4 kernel modules loaded such as: mlx[4|5]_ib, rdma_cm, rdma_ucm, and ib_ipoib To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1856375/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853014] Re: GPU device disable/enable test failure
** Attachment added: "pipeline-cloudtest-manual_2110.msg" https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1853014/+attachment/5306232/+files/pipeline-cloudtest-manual_2110.msg -- 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/1853014 Title: GPU device disable/enable test failure Status in linux-azure package in Ubuntu: New Bug description: We found a GPU device disable/enable test failure, and it is related to below call trace. When GPU device is disable, this call-trace happens at the device disable step. The system does not panic but the driver is not loaded back. %echo 1 > /sys/bus/pci/devices/c09d:00:00.0/remove Note: after this command, PCI bus is not removed but only ‘remove’ file is disappeared with below call trace. All other PCI devices are removed successfully. [ 56.649648] hv_balloon: Max. dynamic memory size: 57344 MB [ 457.438303] NVRM: Attempting to remove minor device 0 with non-zero usage count! [ 457.438305] [ cut here ] [ 457.438465] WARNING: CPU: 4 PID: 5026 at /var/lib/dkms/nvidia/430.50/build/nvidia/nv.c:4068 nvidia_remove+0x39d/0x3b0 [nvidia] [ 457.438466] Modules linked in: xt_owner xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_security bpfilter nvidia_uvm(OE) nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops nls_iso8859_1 drm drm_panel_orientation_quirks ipmi_devintf ipmi_msghandler i2c_core pci_hyperv hv_balloon serio_raw sch_fq_codel joydev ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi parport_pc ppdev lp parport ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_pclmul crc32_pclmul ghash_clmulni_intel hid_generic aesni_intel aes_x86_64 hyperv_fb crypto_simd cryptd glue_helper hid_hyperv cfbfillrect cfbimgblt hyperv_keyboard cfbcopyarea pata_acpi hid hv_netvsc hv_utils [ 457.438493] CPU: 4 PID: 5026 Comm: bash Tainted: P OE 5.0.0-1025-azure #27~18.04.1-Ubuntu [ 457.438494] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090007 06/02/2017 [ 457.438564] RIP: 0010:nvidia_remove+0x39d/0x3b0 [nvidia] [ 457.438565] Code: ff e8 17 c5 9a f3 41 8b 95 68 04 00 00 48 c7 c6 f8 97 8e c1 bf 04 00 00 00 e8 cf 9c 00 00 48 c7 c7 b0 82 8e c1 e8 b6 8b a1 f3 <0f> 0b e8 cc a2 00 00 eb f9 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 [ 457.438566] RSP: 0018:b1578bcfbcf8 EFLAGS: 00010282 [ 457.438567] RAX: 0024 RBX: 8ec43bdf RCX: 0006 [ 457.438568] RDX: RSI: 0086 RDI: 8ec445d15580 [ 457.438568] RBP: b1578bcfbd40 R08: 0001 R09: 023c [ 457.438569] R10: b1578bcfba38 R11: R12: 8ec43d3b2000 [ 457.438569] R13: 8ec4388b3000 R14: c19411b0 R15: 0060 [ 457.438570] FS: 7f92d7263740() GS:8ec445d0() knlGS: [ 457.438573] CS: 0010 DS: ES: CR0: 80050033 [ 457.438573] CR2: 560d3d973f60 CR3: 000e4aeca004 CR4: 001606e0 [ 457.438574] Call Trace: [ 457.438579] pci_device_remove+0x3e/0xc0 [ 457.438582] device_release_driver_internal+0x18d/0x260 [ 457.438583] device_release_driver+0x12/0x20 [ 457.438585] pci_stop_bus_device+0x68/0x90 [ 457.438586] pci_stop_and_remove_bus_device_locked+0x1a/0x30 [ 457.438588] remove_store+0x7c/0x90 [ 457.438590] dev_attr_store+0x1b/0x30 [ 457.438592] sysfs_kf_write+0x3c/0x50 [ 457.438593] kernfs_fop_write+0x125/0x1a0 [ 457.438596] __vfs_write+0x1b/0x40 [ 457.438598] vfs_write+0xb1/0x1a0 [ 457.438599] ksys_write+0x5c/0xe0 [ 457.438601] __x64_sys_write+0x1a/0x20 [ 457.438603] do_syscall_64+0x64/0x1b0 [ 457.438607] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 457.438608] RIP: 0033:0x7f92d6947154 [ 457.438609] Code: 89 02 48 c7 c0 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 48 8d 05 b1 07 2e 00 8b 00 85 c0 75 13 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 54 f3 c3 66 90 41 54 55 49 89 d4 53 48 89 f5 [ 457.438610] RSP: 002b:7ffe5a69f208 EFLAGS: 0246 ORIG_RAX: 0001 [ 457.438611] RAX: ffda RBX: 0002 RCX: 7f92d6947154 [ 457.438612] RDX: 0002 RSI: 560d3d7bd8c0 RDI: 0001 [ 457.438612] RBP: 560d3d7bd8c0 R08: 000a R09: 0001 [ 457.438613] R10: 000a R11: 0246 R12: 7f92d6c23760 [ 457.438613] R13: 0002 R14: 7f92d6c1f2a0 R15: 7f92d6c1e760 [ 457.438615] ---[ end trace 64ddc7a9a2dd8bd8 ]--- Kernel: 5.0.
[Kernel-packages] [Bug 1853014] Re: GPU device disable/enable test failure
** Attachment added: "syslog" https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1853014/+attachment/5306233/+files/syslog -- 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/1853014 Title: GPU device disable/enable test failure Status in linux-azure package in Ubuntu: New Bug description: We found a GPU device disable/enable test failure, and it is related to below call trace. When GPU device is disable, this call-trace happens at the device disable step. The system does not panic but the driver is not loaded back. %echo 1 > /sys/bus/pci/devices/c09d:00:00.0/remove Note: after this command, PCI bus is not removed but only ‘remove’ file is disappeared with below call trace. All other PCI devices are removed successfully. [ 56.649648] hv_balloon: Max. dynamic memory size: 57344 MB [ 457.438303] NVRM: Attempting to remove minor device 0 with non-zero usage count! [ 457.438305] [ cut here ] [ 457.438465] WARNING: CPU: 4 PID: 5026 at /var/lib/dkms/nvidia/430.50/build/nvidia/nv.c:4068 nvidia_remove+0x39d/0x3b0 [nvidia] [ 457.438466] Modules linked in: xt_owner xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_security bpfilter nvidia_uvm(OE) nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops nls_iso8859_1 drm drm_panel_orientation_quirks ipmi_devintf ipmi_msghandler i2c_core pci_hyperv hv_balloon serio_raw sch_fq_codel joydev ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi parport_pc ppdev lp parport ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_pclmul crc32_pclmul ghash_clmulni_intel hid_generic aesni_intel aes_x86_64 hyperv_fb crypto_simd cryptd glue_helper hid_hyperv cfbfillrect cfbimgblt hyperv_keyboard cfbcopyarea pata_acpi hid hv_netvsc hv_utils [ 457.438493] CPU: 4 PID: 5026 Comm: bash Tainted: P OE 5.0.0-1025-azure #27~18.04.1-Ubuntu [ 457.438494] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090007 06/02/2017 [ 457.438564] RIP: 0010:nvidia_remove+0x39d/0x3b0 [nvidia] [ 457.438565] Code: ff e8 17 c5 9a f3 41 8b 95 68 04 00 00 48 c7 c6 f8 97 8e c1 bf 04 00 00 00 e8 cf 9c 00 00 48 c7 c7 b0 82 8e c1 e8 b6 8b a1 f3 <0f> 0b e8 cc a2 00 00 eb f9 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 [ 457.438566] RSP: 0018:b1578bcfbcf8 EFLAGS: 00010282 [ 457.438567] RAX: 0024 RBX: 8ec43bdf RCX: 0006 [ 457.438568] RDX: RSI: 0086 RDI: 8ec445d15580 [ 457.438568] RBP: b1578bcfbd40 R08: 0001 R09: 023c [ 457.438569] R10: b1578bcfba38 R11: R12: 8ec43d3b2000 [ 457.438569] R13: 8ec4388b3000 R14: c19411b0 R15: 0060 [ 457.438570] FS: 7f92d7263740() GS:8ec445d0() knlGS: [ 457.438573] CS: 0010 DS: ES: CR0: 80050033 [ 457.438573] CR2: 560d3d973f60 CR3: 000e4aeca004 CR4: 001606e0 [ 457.438574] Call Trace: [ 457.438579] pci_device_remove+0x3e/0xc0 [ 457.438582] device_release_driver_internal+0x18d/0x260 [ 457.438583] device_release_driver+0x12/0x20 [ 457.438585] pci_stop_bus_device+0x68/0x90 [ 457.438586] pci_stop_and_remove_bus_device_locked+0x1a/0x30 [ 457.438588] remove_store+0x7c/0x90 [ 457.438590] dev_attr_store+0x1b/0x30 [ 457.438592] sysfs_kf_write+0x3c/0x50 [ 457.438593] kernfs_fop_write+0x125/0x1a0 [ 457.438596] __vfs_write+0x1b/0x40 [ 457.438598] vfs_write+0xb1/0x1a0 [ 457.438599] ksys_write+0x5c/0xe0 [ 457.438601] __x64_sys_write+0x1a/0x20 [ 457.438603] do_syscall_64+0x64/0x1b0 [ 457.438607] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 457.438608] RIP: 0033:0x7f92d6947154 [ 457.438609] Code: 89 02 48 c7 c0 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 48 8d 05 b1 07 2e 00 8b 00 85 c0 75 13 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 54 f3 c3 66 90 41 54 55 49 89 d4 53 48 89 f5 [ 457.438610] RSP: 002b:7ffe5a69f208 EFLAGS: 0246 ORIG_RAX: 0001 [ 457.438611] RAX: ffda RBX: 0002 RCX: 7f92d6947154 [ 457.438612] RDX: 0002 RSI: 560d3d7bd8c0 RDI: 0001 [ 457.438612] RBP: 560d3d7bd8c0 R08: 000a R09: 0001 [ 457.438613] R10: 000a R11: 0246 R12: 7f92d6c23760 [ 457.438613] R13: 0002 R14: 7f92d6c1f2a0 R15: 7f92d6c1e760 [ 457.438615] ---[ end trace 64ddc7a9a2dd8bd8 ]--- Kernel: 5.0.0-1025-azure This issue happens with 18.04 and not 16
[Kernel-packages] [Bug 1853014] Re: GPU device disable/enable test failure
** Attachment added: "pipeline-cloudtest-manual_2109.msg" https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1853014/+attachment/5306230/+files/pipeline-cloudtest-manual_2109.msg -- 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/1853014 Title: GPU device disable/enable test failure Status in linux-azure package in Ubuntu: New Bug description: We found a GPU device disable/enable test failure, and it is related to below call trace. When GPU device is disable, this call-trace happens at the device disable step. The system does not panic but the driver is not loaded back. %echo 1 > /sys/bus/pci/devices/c09d:00:00.0/remove Note: after this command, PCI bus is not removed but only ‘remove’ file is disappeared with below call trace. All other PCI devices are removed successfully. [ 56.649648] hv_balloon: Max. dynamic memory size: 57344 MB [ 457.438303] NVRM: Attempting to remove minor device 0 with non-zero usage count! [ 457.438305] [ cut here ] [ 457.438465] WARNING: CPU: 4 PID: 5026 at /var/lib/dkms/nvidia/430.50/build/nvidia/nv.c:4068 nvidia_remove+0x39d/0x3b0 [nvidia] [ 457.438466] Modules linked in: xt_owner xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_security bpfilter nvidia_uvm(OE) nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops nls_iso8859_1 drm drm_panel_orientation_quirks ipmi_devintf ipmi_msghandler i2c_core pci_hyperv hv_balloon serio_raw sch_fq_codel joydev ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi parport_pc ppdev lp parport ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_pclmul crc32_pclmul ghash_clmulni_intel hid_generic aesni_intel aes_x86_64 hyperv_fb crypto_simd cryptd glue_helper hid_hyperv cfbfillrect cfbimgblt hyperv_keyboard cfbcopyarea pata_acpi hid hv_netvsc hv_utils [ 457.438493] CPU: 4 PID: 5026 Comm: bash Tainted: P OE 5.0.0-1025-azure #27~18.04.1-Ubuntu [ 457.438494] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090007 06/02/2017 [ 457.438564] RIP: 0010:nvidia_remove+0x39d/0x3b0 [nvidia] [ 457.438565] Code: ff e8 17 c5 9a f3 41 8b 95 68 04 00 00 48 c7 c6 f8 97 8e c1 bf 04 00 00 00 e8 cf 9c 00 00 48 c7 c7 b0 82 8e c1 e8 b6 8b a1 f3 <0f> 0b e8 cc a2 00 00 eb f9 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 [ 457.438566] RSP: 0018:b1578bcfbcf8 EFLAGS: 00010282 [ 457.438567] RAX: 0024 RBX: 8ec43bdf RCX: 0006 [ 457.438568] RDX: RSI: 0086 RDI: 8ec445d15580 [ 457.438568] RBP: b1578bcfbd40 R08: 0001 R09: 023c [ 457.438569] R10: b1578bcfba38 R11: R12: 8ec43d3b2000 [ 457.438569] R13: 8ec4388b3000 R14: c19411b0 R15: 0060 [ 457.438570] FS: 7f92d7263740() GS:8ec445d0() knlGS: [ 457.438573] CS: 0010 DS: ES: CR0: 80050033 [ 457.438573] CR2: 560d3d973f60 CR3: 000e4aeca004 CR4: 001606e0 [ 457.438574] Call Trace: [ 457.438579] pci_device_remove+0x3e/0xc0 [ 457.438582] device_release_driver_internal+0x18d/0x260 [ 457.438583] device_release_driver+0x12/0x20 [ 457.438585] pci_stop_bus_device+0x68/0x90 [ 457.438586] pci_stop_and_remove_bus_device_locked+0x1a/0x30 [ 457.438588] remove_store+0x7c/0x90 [ 457.438590] dev_attr_store+0x1b/0x30 [ 457.438592] sysfs_kf_write+0x3c/0x50 [ 457.438593] kernfs_fop_write+0x125/0x1a0 [ 457.438596] __vfs_write+0x1b/0x40 [ 457.438598] vfs_write+0xb1/0x1a0 [ 457.438599] ksys_write+0x5c/0xe0 [ 457.438601] __x64_sys_write+0x1a/0x20 [ 457.438603] do_syscall_64+0x64/0x1b0 [ 457.438607] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 457.438608] RIP: 0033:0x7f92d6947154 [ 457.438609] Code: 89 02 48 c7 c0 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 48 8d 05 b1 07 2e 00 8b 00 85 c0 75 13 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 54 f3 c3 66 90 41 54 55 49 89 d4 53 48 89 f5 [ 457.438610] RSP: 002b:7ffe5a69f208 EFLAGS: 0246 ORIG_RAX: 0001 [ 457.438611] RAX: ffda RBX: 0002 RCX: 7f92d6947154 [ 457.438612] RDX: 0002 RSI: 560d3d7bd8c0 RDI: 0001 [ 457.438612] RBP: 560d3d7bd8c0 R08: 000a R09: 0001 [ 457.438613] R10: 000a R11: 0246 R12: 7f92d6c23760 [ 457.438613] R13: 0002 R14: 7f92d6c1f2a0 R15: 7f92d6c1e760 [ 457.438615] ---[ end trace 64ddc7a9a2dd8bd8 ]--- Kernel: 5.0.
[Kernel-packages] [Bug 1853014] Re: GPU device disable/enable test failure
** Attachment added: "pipeline-cloudtest-manual_2110.msg" https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1853014/+attachment/5306231/+files/pipeline-cloudtest-manual_2110.msg -- 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/1853014 Title: GPU device disable/enable test failure Status in linux-azure package in Ubuntu: New Bug description: We found a GPU device disable/enable test failure, and it is related to below call trace. When GPU device is disable, this call-trace happens at the device disable step. The system does not panic but the driver is not loaded back. %echo 1 > /sys/bus/pci/devices/c09d:00:00.0/remove Note: after this command, PCI bus is not removed but only ‘remove’ file is disappeared with below call trace. All other PCI devices are removed successfully. [ 56.649648] hv_balloon: Max. dynamic memory size: 57344 MB [ 457.438303] NVRM: Attempting to remove minor device 0 with non-zero usage count! [ 457.438305] [ cut here ] [ 457.438465] WARNING: CPU: 4 PID: 5026 at /var/lib/dkms/nvidia/430.50/build/nvidia/nv.c:4068 nvidia_remove+0x39d/0x3b0 [nvidia] [ 457.438466] Modules linked in: xt_owner xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_security bpfilter nvidia_uvm(OE) nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops nls_iso8859_1 drm drm_panel_orientation_quirks ipmi_devintf ipmi_msghandler i2c_core pci_hyperv hv_balloon serio_raw sch_fq_codel joydev ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi parport_pc ppdev lp parport ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_pclmul crc32_pclmul ghash_clmulni_intel hid_generic aesni_intel aes_x86_64 hyperv_fb crypto_simd cryptd glue_helper hid_hyperv cfbfillrect cfbimgblt hyperv_keyboard cfbcopyarea pata_acpi hid hv_netvsc hv_utils [ 457.438493] CPU: 4 PID: 5026 Comm: bash Tainted: P OE 5.0.0-1025-azure #27~18.04.1-Ubuntu [ 457.438494] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090007 06/02/2017 [ 457.438564] RIP: 0010:nvidia_remove+0x39d/0x3b0 [nvidia] [ 457.438565] Code: ff e8 17 c5 9a f3 41 8b 95 68 04 00 00 48 c7 c6 f8 97 8e c1 bf 04 00 00 00 e8 cf 9c 00 00 48 c7 c7 b0 82 8e c1 e8 b6 8b a1 f3 <0f> 0b e8 cc a2 00 00 eb f9 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 [ 457.438566] RSP: 0018:b1578bcfbcf8 EFLAGS: 00010282 [ 457.438567] RAX: 0024 RBX: 8ec43bdf RCX: 0006 [ 457.438568] RDX: RSI: 0086 RDI: 8ec445d15580 [ 457.438568] RBP: b1578bcfbd40 R08: 0001 R09: 023c [ 457.438569] R10: b1578bcfba38 R11: R12: 8ec43d3b2000 [ 457.438569] R13: 8ec4388b3000 R14: c19411b0 R15: 0060 [ 457.438570] FS: 7f92d7263740() GS:8ec445d0() knlGS: [ 457.438573] CS: 0010 DS: ES: CR0: 80050033 [ 457.438573] CR2: 560d3d973f60 CR3: 000e4aeca004 CR4: 001606e0 [ 457.438574] Call Trace: [ 457.438579] pci_device_remove+0x3e/0xc0 [ 457.438582] device_release_driver_internal+0x18d/0x260 [ 457.438583] device_release_driver+0x12/0x20 [ 457.438585] pci_stop_bus_device+0x68/0x90 [ 457.438586] pci_stop_and_remove_bus_device_locked+0x1a/0x30 [ 457.438588] remove_store+0x7c/0x90 [ 457.438590] dev_attr_store+0x1b/0x30 [ 457.438592] sysfs_kf_write+0x3c/0x50 [ 457.438593] kernfs_fop_write+0x125/0x1a0 [ 457.438596] __vfs_write+0x1b/0x40 [ 457.438598] vfs_write+0xb1/0x1a0 [ 457.438599] ksys_write+0x5c/0xe0 [ 457.438601] __x64_sys_write+0x1a/0x20 [ 457.438603] do_syscall_64+0x64/0x1b0 [ 457.438607] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 457.438608] RIP: 0033:0x7f92d6947154 [ 457.438609] Code: 89 02 48 c7 c0 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 48 8d 05 b1 07 2e 00 8b 00 85 c0 75 13 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 54 f3 c3 66 90 41 54 55 49 89 d4 53 48 89 f5 [ 457.438610] RSP: 002b:7ffe5a69f208 EFLAGS: 0246 ORIG_RAX: 0001 [ 457.438611] RAX: ffda RBX: 0002 RCX: 7f92d6947154 [ 457.438612] RDX: 0002 RSI: 560d3d7bd8c0 RDI: 0001 [ 457.438612] RBP: 560d3d7bd8c0 R08: 000a R09: 0001 [ 457.438613] R10: 000a R11: 0246 R12: 7f92d6c23760 [ 457.438613] R13: 0002 R14: 7f92d6c1f2a0 R15: 7f92d6c1e760 [ 457.438615] ---[ end trace 64ddc7a9a2dd8bd8 ]--- Kernel: 5.0.
[Kernel-packages] [Bug 1853014] Re: GPU device disable/enable test failure
** Attachment added: "dmesg" https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1853014/+attachment/5306229/+files/dmesg -- 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/1853014 Title: GPU device disable/enable test failure Status in linux-azure package in Ubuntu: New Bug description: We found a GPU device disable/enable test failure, and it is related to below call trace. When GPU device is disable, this call-trace happens at the device disable step. The system does not panic but the driver is not loaded back. %echo 1 > /sys/bus/pci/devices/c09d:00:00.0/remove Note: after this command, PCI bus is not removed but only ‘remove’ file is disappeared with below call trace. All other PCI devices are removed successfully. [ 56.649648] hv_balloon: Max. dynamic memory size: 57344 MB [ 457.438303] NVRM: Attempting to remove minor device 0 with non-zero usage count! [ 457.438305] [ cut here ] [ 457.438465] WARNING: CPU: 4 PID: 5026 at /var/lib/dkms/nvidia/430.50/build/nvidia/nv.c:4068 nvidia_remove+0x39d/0x3b0 [nvidia] [ 457.438466] Modules linked in: xt_owner xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_security bpfilter nvidia_uvm(OE) nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops nls_iso8859_1 drm drm_panel_orientation_quirks ipmi_devintf ipmi_msghandler i2c_core pci_hyperv hv_balloon serio_raw sch_fq_codel joydev ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi parport_pc ppdev lp parport ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_pclmul crc32_pclmul ghash_clmulni_intel hid_generic aesni_intel aes_x86_64 hyperv_fb crypto_simd cryptd glue_helper hid_hyperv cfbfillrect cfbimgblt hyperv_keyboard cfbcopyarea pata_acpi hid hv_netvsc hv_utils [ 457.438493] CPU: 4 PID: 5026 Comm: bash Tainted: P OE 5.0.0-1025-azure #27~18.04.1-Ubuntu [ 457.438494] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090007 06/02/2017 [ 457.438564] RIP: 0010:nvidia_remove+0x39d/0x3b0 [nvidia] [ 457.438565] Code: ff e8 17 c5 9a f3 41 8b 95 68 04 00 00 48 c7 c6 f8 97 8e c1 bf 04 00 00 00 e8 cf 9c 00 00 48 c7 c7 b0 82 8e c1 e8 b6 8b a1 f3 <0f> 0b e8 cc a2 00 00 eb f9 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 [ 457.438566] RSP: 0018:b1578bcfbcf8 EFLAGS: 00010282 [ 457.438567] RAX: 0024 RBX: 8ec43bdf RCX: 0006 [ 457.438568] RDX: RSI: 0086 RDI: 8ec445d15580 [ 457.438568] RBP: b1578bcfbd40 R08: 0001 R09: 023c [ 457.438569] R10: b1578bcfba38 R11: R12: 8ec43d3b2000 [ 457.438569] R13: 8ec4388b3000 R14: c19411b0 R15: 0060 [ 457.438570] FS: 7f92d7263740() GS:8ec445d0() knlGS: [ 457.438573] CS: 0010 DS: ES: CR0: 80050033 [ 457.438573] CR2: 560d3d973f60 CR3: 000e4aeca004 CR4: 001606e0 [ 457.438574] Call Trace: [ 457.438579] pci_device_remove+0x3e/0xc0 [ 457.438582] device_release_driver_internal+0x18d/0x260 [ 457.438583] device_release_driver+0x12/0x20 [ 457.438585] pci_stop_bus_device+0x68/0x90 [ 457.438586] pci_stop_and_remove_bus_device_locked+0x1a/0x30 [ 457.438588] remove_store+0x7c/0x90 [ 457.438590] dev_attr_store+0x1b/0x30 [ 457.438592] sysfs_kf_write+0x3c/0x50 [ 457.438593] kernfs_fop_write+0x125/0x1a0 [ 457.438596] __vfs_write+0x1b/0x40 [ 457.438598] vfs_write+0xb1/0x1a0 [ 457.438599] ksys_write+0x5c/0xe0 [ 457.438601] __x64_sys_write+0x1a/0x20 [ 457.438603] do_syscall_64+0x64/0x1b0 [ 457.438607] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 457.438608] RIP: 0033:0x7f92d6947154 [ 457.438609] Code: 89 02 48 c7 c0 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 48 8d 05 b1 07 2e 00 8b 00 85 c0 75 13 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 54 f3 c3 66 90 41 54 55 49 89 d4 53 48 89 f5 [ 457.438610] RSP: 002b:7ffe5a69f208 EFLAGS: 0246 ORIG_RAX: 0001 [ 457.438611] RAX: ffda RBX: 0002 RCX: 7f92d6947154 [ 457.438612] RDX: 0002 RSI: 560d3d7bd8c0 RDI: 0001 [ 457.438612] RBP: 560d3d7bd8c0 R08: 000a R09: 0001 [ 457.438613] R10: 000a R11: 0246 R12: 7f92d6c23760 [ 457.438613] R13: 0002 R14: 7f92d6c1f2a0 R15: 7f92d6c1e760 [ 457.438615] ---[ end trace 64ddc7a9a2dd8bd8 ]--- Kernel: 5.0.0-1025-azure This issue happens with 18.04 and not 16.0
[Kernel-packages] [Bug 1853014] [NEW] GPU device disable/enable test failure
Public bug reported: We found a GPU device disable/enable test failure, and it is related to below call trace. When GPU device is disable, this call-trace happens at the device disable step. The system does not panic but the driver is not loaded back. %echo 1 > /sys/bus/pci/devices/c09d:00:00.0/remove Note: after this command, PCI bus is not removed but only ‘remove’ file is disappeared with below call trace. All other PCI devices are removed successfully. [ 56.649648] hv_balloon: Max. dynamic memory size: 57344 MB [ 457.438303] NVRM: Attempting to remove minor device 0 with non-zero usage count! [ 457.438305] [ cut here ] [ 457.438465] WARNING: CPU: 4 PID: 5026 at /var/lib/dkms/nvidia/430.50/build/nvidia/nv.c:4068 nvidia_remove+0x39d/0x3b0 [nvidia] [ 457.438466] Modules linked in: xt_owner xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_security bpfilter nvidia_uvm(OE) nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops nls_iso8859_1 drm drm_panel_orientation_quirks ipmi_devintf ipmi_msghandler i2c_core pci_hyperv hv_balloon serio_raw sch_fq_codel joydev ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi parport_pc ppdev lp parport ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_pclmul crc32_pclmul ghash_clmulni_intel hid_generic aesni_intel aes_x86_64 hyperv_fb crypto_simd cryptd glue_helper hid_hyperv cfbfillrect cfbimgblt hyperv_keyboard cfbcopyarea pata_acpi hid hv_netvsc hv_utils [ 457.438493] CPU: 4 PID: 5026 Comm: bash Tainted: P OE 5.0.0-1025-azure #27~18.04.1-Ubuntu [ 457.438494] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090007 06/02/2017 [ 457.438564] RIP: 0010:nvidia_remove+0x39d/0x3b0 [nvidia] [ 457.438565] Code: ff e8 17 c5 9a f3 41 8b 95 68 04 00 00 48 c7 c6 f8 97 8e c1 bf 04 00 00 00 e8 cf 9c 00 00 48 c7 c7 b0 82 8e c1 e8 b6 8b a1 f3 <0f> 0b e8 cc a2 00 00 eb f9 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 [ 457.438566] RSP: 0018:b1578bcfbcf8 EFLAGS: 00010282 [ 457.438567] RAX: 0024 RBX: 8ec43bdf RCX: 0006 [ 457.438568] RDX: RSI: 0086 RDI: 8ec445d15580 [ 457.438568] RBP: b1578bcfbd40 R08: 0001 R09: 023c [ 457.438569] R10: b1578bcfba38 R11: R12: 8ec43d3b2000 [ 457.438569] R13: 8ec4388b3000 R14: c19411b0 R15: 0060 [ 457.438570] FS: 7f92d7263740() GS:8ec445d0() knlGS: [ 457.438573] CS: 0010 DS: ES: CR0: 80050033 [ 457.438573] CR2: 560d3d973f60 CR3: 000e4aeca004 CR4: 001606e0 [ 457.438574] Call Trace: [ 457.438579] pci_device_remove+0x3e/0xc0 [ 457.438582] device_release_driver_internal+0x18d/0x260 [ 457.438583] device_release_driver+0x12/0x20 [ 457.438585] pci_stop_bus_device+0x68/0x90 [ 457.438586] pci_stop_and_remove_bus_device_locked+0x1a/0x30 [ 457.438588] remove_store+0x7c/0x90 [ 457.438590] dev_attr_store+0x1b/0x30 [ 457.438592] sysfs_kf_write+0x3c/0x50 [ 457.438593] kernfs_fop_write+0x125/0x1a0 [ 457.438596] __vfs_write+0x1b/0x40 [ 457.438598] vfs_write+0xb1/0x1a0 [ 457.438599] ksys_write+0x5c/0xe0 [ 457.438601] __x64_sys_write+0x1a/0x20 [ 457.438603] do_syscall_64+0x64/0x1b0 [ 457.438607] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 457.438608] RIP: 0033:0x7f92d6947154 [ 457.438609] Code: 89 02 48 c7 c0 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 48 8d 05 b1 07 2e 00 8b 00 85 c0 75 13 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 54 f3 c3 66 90 41 54 55 49 89 d4 53 48 89 f5 [ 457.438610] RSP: 002b:7ffe5a69f208 EFLAGS: 0246 ORIG_RAX: 0001 [ 457.438611] RAX: ffda RBX: 0002 RCX: 7f92d6947154 [ 457.438612] RDX: 0002 RSI: 560d3d7bd8c0 RDI: 0001 [ 457.438612] RBP: 560d3d7bd8c0 R08: 000a R09: 0001 [ 457.438613] R10: 000a R11: 0246 R12: 7f92d6c23760 [ 457.438613] R13: 0002 R14: 7f92d6c1f2a0 R15: 7f92d6c1e760 [ 457.438615] ---[ end trace 64ddc7a9a2dd8bd8 ]--- Kernel: 5.0.0-1025-azure This issue happens with 18.04 and not 16.04. ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: New -- 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/1853014 Title: GPU device disable/enable test failure Status in linux-azure package in Ubuntu: New Bug description: We found a GPU device disable/enable test failure, and it is related to below call trace. When GPU device is disable, this call-trace happens
[Kernel-packages] [Bug 1856605] [NEW] [linux-azure] Ubuntu 16.04 + INFINIBAND-OPEN-MPI-2VM
Public bug reported: We ran an RDMA test case against gallery image Ubuntu 16.04 (with proposed kernel), and found the below issue. The kernel prior to proposed does not exhibit this bug, so it is a regression: The issue is when ibv_devinfo is run, we get the below info: ibv_devinfo libibverbs: Warning: no userspace device-specific driver found for /sys/class/infiniband_verbs/uverbs0 No IB devices found ibv_devices libibverbs: Warning: no userspace device-specific driver found for /sys/class/infiniband_verbs/uverbs0 device node GUID -- Ibstat works as expected CA 'mlx5_0' CA type: MT4120 Number of ports: 1 Firmware version: 16.23.1020 Hardware version: 0 Node GUID: 0x00155dfffe33ff49 System image GUID: 0x506b4b0300f521ec Port 1: State: Active Physical state: LinkUp Rate: 100 Base lid: 713 LMC: 0 SM lid: 16 Capability mask: 0x2651ec48 Port GUID: 0x00155dfffd33ff49 Link layer: InfiniBand This Family exhibits the bug, with a subsystem of MT28800: lspci -v|egrep 'Mel|mlx' 0002:00:02.0 Infiniband controller: Mellanox Technologies MT27800 Family [ConnectX-5 Virtual Function] Subsystem: Mellanox Technologies MT28800 Family [ConnectX-5 Virtual Function] Kernel driver in use: mlx5_core Kernel modules: mlx5_core This issue does not occur with Ubuntu 18.04, which has a different Subsystem(MT27800): lspci -v|egrep 'Mel|mlx' 0002:00:02.0 Infiniband controller: Mellanox Technologies MT27800 Family [ConnectX-5 Virtual Function] Subsystem: Mellanox Technologies MT27800 Family [ConnectX-5 Virtual Function] Kernel driver in use: mlx5_core Kernel modules: mlx5_core If we could, we would like to move to rmda-core to version 22 or higher. ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: New -- 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/1856605 Title: [linux-azure] Ubuntu 16.04 + INFINIBAND-OPEN-MPI-2VM Status in linux-azure package in Ubuntu: New Bug description: We ran an RDMA test case against gallery image Ubuntu 16.04 (with proposed kernel), and found the below issue. The kernel prior to proposed does not exhibit this bug, so it is a regression: The issue is when ibv_devinfo is run, we get the below info: ibv_devinfo libibverbs: Warning: no userspace device-specific driver found for /sys/class/infiniband_verbs/uverbs0 No IB devices found ibv_devices libibverbs: Warning: no userspace device-specific driver found for /sys/class/infiniband_verbs/uverbs0 device node GUID -- Ibstat works as expected CA 'mlx5_0' CA type: MT4120 Number of ports: 1 Firmware version: 16.23.1020 Hardware version: 0 Node GUID: 0x00155dfffe33ff49 System image GUID: 0x506b4b0300f521ec Port 1: State: Active Physical state: LinkUp Rate: 100 Base lid: 713 LMC: 0 SM lid: 16 Capability mask: 0x2651ec48 Port GUID: 0x00155dfffd33ff49 Link layer: InfiniBand This Family exhibits the bug, with a subsystem of MT28800: lspci -v|egrep 'Mel|mlx' 0002:00:02.0 Infiniband controller: Mellanox Technologies MT27800 Family [ConnectX-5 Virtual Function] Subsystem: Mellanox Technologies MT28800 Family [ConnectX-5 Virtual Function] Kernel driver in use: mlx5_core Kernel modules: mlx5_core This issue does not occur with Ubuntu 18.04, which has a different Subsystem(MT27800): lspci -v|egrep 'Mel|mlx' 0002:00:02.0 Infiniband controller: Mellanox Technologies MT27800 Family [ConnectX-5 Virtual Function] Subsystem: Mellanox Technologies MT27800 Family [ConnectX-5 Virtual Function] Kernel driver in use: mlx5_core Kernel modules: mlx5_core If we could, we would like to move to rmda-core to version 22 or higher. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1856605/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856605] Re: [linux-azure] Ubuntu 16.04 + INFINIBAND-OPEN-MPI-2VM
Hi Juerg, The tests were pointing at a PPA that had moved. Once the tests were updated to the new PPA, the issue was resolved. This bug can be marked as invalid. ** Changed in: linux-azure (Ubuntu) Status: Confirmed => Invalid -- 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/1856605 Title: [linux-azure] Ubuntu 16.04 + INFINIBAND-OPEN-MPI-2VM Status in linux-azure package in Ubuntu: Invalid Bug description: We ran an RDMA test case against gallery image Ubuntu 16.04 (with proposed kernel), and found the below issue. The kernel prior to proposed does not exhibit this bug, so it is a regression: The issue is when ibv_devinfo is run, we get the below info: ibv_devinfo libibverbs: Warning: no userspace device-specific driver found for /sys/class/infiniband_verbs/uverbs0 No IB devices found ibv_devices libibverbs: Warning: no userspace device-specific driver found for /sys/class/infiniband_verbs/uverbs0 device node GUID -- Ibstat works as expected CA 'mlx5_0' CA type: MT4120 Number of ports: 1 Firmware version: 16.23.1020 Hardware version: 0 Node GUID: 0x00155dfffe33ff49 System image GUID: 0x506b4b0300f521ec Port 1: State: Active Physical state: LinkUp Rate: 100 Base lid: 713 LMC: 0 SM lid: 16 Capability mask: 0x2651ec48 Port GUID: 0x00155dfffd33ff49 Link layer: InfiniBand This Family exhibits the bug, with a subsystem of MT28800: lspci -v|egrep 'Mel|mlx' 0002:00:02.0 Infiniband controller: Mellanox Technologies MT27800 Family [ConnectX-5 Virtual Function] Subsystem: Mellanox Technologies MT28800 Family [ConnectX-5 Virtual Function] Kernel driver in use: mlx5_core Kernel modules: mlx5_core This issue does not occur with Ubuntu 18.04, which has a different Subsystem(MT27800): lspci -v|egrep 'Mel|mlx' 0002:00:02.0 Infiniband controller: Mellanox Technologies MT27800 Family [ConnectX-5 Virtual Function] Subsystem: Mellanox Technologies MT27800 Family [ConnectX-5 Virtual Function] Kernel driver in use: mlx5_core Kernel modules: mlx5_core If we could, we would like to move to rmda-core to version 22 or higher. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1856605/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848739] [NEW] [linux-azure] Patch to prevent possible data corruption
Public bug reported:
There are three patches that prevent possible data corruption. The
three commits are:
aef1897cd36d ("blk-mq: insert rq with DONTPREP to hctx dispatch list when
requeue")
c616cbee97ae ("blk-mq: punt failed direct issue to dispatch list")
923218f6166a ("blk-mq: don't allocate driver tag upfront for flush rq")
18.04 has all three of these patches. 16.04 has two out of the three,
but it is missing commit c616cbee97ae.
We would like to request commit c616cbee97ae be included in the 16.04 kernel:
c616cbee97ae ("blk-mq: punt failed direct issue to dispatch list")
** Affects: linux-azure (Ubuntu)
Importance: Undecided
Status: New
--
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/1848739
Title:
[linux-azure] Patch to prevent possible data corruption
Status in linux-azure package in Ubuntu:
New
Bug description:
There are three patches that prevent possible data corruption. The
three commits are:
aef1897cd36d ("blk-mq: insert rq with DONTPREP to hctx dispatch list when
requeue")
c616cbee97ae ("blk-mq: punt failed direct issue to dispatch list")
923218f6166a ("blk-mq: don't allocate driver tag upfront for flush rq")
18.04 has all three of these patches. 16.04 has two out of the three,
but it is missing commit c616cbee97ae.
We would like to request commit c616cbee97ae be included in the 16.04 kernel:
c616cbee97ae ("blk-mq: punt failed direct issue to dispatch list")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1848739/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849495] [NEW] [linux-azure] Add ability to change scsi queue depth
Public bug reported:
Microsoft would like to request the following patch in the 16.04 and
18.04 Azure kernels:
adfbd028e155 ("scsi: storvsc: Add ability to change scsi queue depth")
This patch will add functionality to allow the SCSI queue depth to be
changed by utilizing the "scsi_change_queue_depth" function.
Commit adfbd028e155 was added to mainline in v5.3-rc1
** Affects: linux-azure (Ubuntu)
Importance: Undecided
Status: New
--
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/1849495
Title:
[linux-azure] Add ability to change scsi queue depth
Status in linux-azure package in Ubuntu:
New
Bug description:
Microsoft would like to request the following patch in the 16.04 and
18.04 Azure kernels:
adfbd028e155 ("scsi: storvsc: Add ability to change scsi queue depth")
This patch will add functionality to allow the SCSI queue depth to be
changed by utilizing the "scsi_change_queue_depth" function.
Commit adfbd028e155 was added to mainline in v5.3-rc1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1849495/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850185] [NEW] [linux-azure] 19.04 regression of KDUMP
Public bug reported: By default our test cases use DS1_v2 to test KDUMP, when we trigger a kernel panic, the VM enters into emergency mode, which can be seen on the serial console. This issue can be resolved if the VM is resized from DS1_v2 (1 vcpus, 3.5 GiB memory) to DS12_v2 (4 vcpus, 28 GiB memory). However, Ubuntu 18.04 and Ubuntu 19.10 KDUMP work using a VM size of DS1_v2. This issue only happens when using Ubuntu 19.04. The following appears on the 19.04 serial console when the issue occurs: [ OK ] Reached target Local File Systems (Pre). Mounting /boot/efi... Starting File System Check…/cloud/azure_resource-part1... [FAILED] Failed to mount /boot/efi. See 'systemctl status boot-efi.mount' for details. [DEPEND] Dependency failed for Local File Systems. [ OK ] Started File System Check …sk/cloud/azure_resource-part1. [ OK ] Started File System Check Daemon to report status. Starting GRUB failed boot detection... Starting Create final runt…dir for shutdown pivot root... Starting Tell Plymouth To Write Out Runtime Data... [ OK ] Started Emergency Shell. Starting Load AppArmor profiles... Starting Create Volatile Files and Directories... [ OK ] Stopped Dispatch Password …ts to Console Directory Watch. [ OK ] Reached target Emergency Mode. REPRO STEPS: Create Ubuntu 19.04 using size Standard_DS1_v2. Install kdump tools, reboot VM - apt update && apt install linux-crashdump, reboot VM, kdump-config show check the state is - ready to kdump. Trigger kernel panic - sysctl -w kernel.sysrq=1 && echo c > /proc/sysrq-trigger Expected behavior - VM reboot successfully and crash dump file and related subdirectories generated successfully. Current behavior - The VM is inaccessible from SSH, it enters into emergency mode, have to press Ctrl + D in serial console, then VM enters into normal reboot process, crash dump file and related subdirectories generated successfully. Update value for crashkernel to reserve the memory by updating the /etc/default/grub.d/kdump-tools.cfg file, run update-grub, reboot VM, dmesg | grep -i crashkernel check the memory is reserving successfully for crashkernel. Then retest (trigger kernel panic) against different memory setting for crashkernel. ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: New ** Tags: sts -- 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/1850185 Title: [linux-azure] 19.04 regression of KDUMP Status in linux-azure package in Ubuntu: New Bug description: By default our test cases use DS1_v2 to test KDUMP, when we trigger a kernel panic, the VM enters into emergency mode, which can be seen on the serial console. This issue can be resolved if the VM is resized from DS1_v2 (1 vcpus, 3.5 GiB memory) to DS12_v2 (4 vcpus, 28 GiB memory). However, Ubuntu 18.04 and Ubuntu 19.10 KDUMP work using a VM size of DS1_v2. This issue only happens when using Ubuntu 19.04. The following appears on the 19.04 serial console when the issue occurs: [ OK ] Reached target Local File Systems (Pre). Mounting /boot/efi... Starting File System Check…/cloud/azure_resource-part1... [FAILED] Failed to mount /boot/efi. See 'systemctl status boot-efi.mount' for details. [DEPEND] Dependency failed for Local File Systems. [ OK ] Started File System Check …sk/cloud/azure_resource-part1. [ OK ] Started File System Check Daemon to report status. Starting GRUB failed boot detection... Starting Create final runt…dir for shutdown pivot root... Starting Tell Plymouth To Write Out Runtime Data... [ OK ] Started Emergency Shell. Starting Load AppArmor profiles... Starting Create Volatile Files and Directories... [ OK ] Stopped Dispatch Password …ts to Console Directory Watch. [ OK ] Reached target Emergency Mode. REPRO STEPS: Create Ubuntu 19.04 using size Standard_DS1_v2. Install kdump tools, reboot VM - apt update && apt install linux-crashdump, reboot VM, kdump-config show check the state is - ready to kdump. Trigger kernel panic - sysctl -w kernel.sysrq=1 && echo c > /proc/sysrq-trigger Expected behavior - VM reboot successfully and crash dump file and related subdirectories generated successfully. Current behavior - The VM is inaccessible from SSH, it enters into emergency mode, have to press Ctrl + D in serial console, then VM enters into normal reboot process, crash dump file and related subdirectories generated successfully. Update value for crashkernel to reserve the memory by updating the /etc/default/grub.d/kdump-tools.cfg file, run update-grub, reboot VM, dmesg | grep -i crashkernel check the memory is reserving successfully for crashkernel. Then retest (trigger kernel panic) against diffe
[Kernel-packages] [Bug 1850185] Re: [linux-azure] 19.04 regression of KDUMP
This bug only affects kdump on 19.04 and not the 5.0 kernel on 18.04. Since this is the case, I'll close this bug since 19.04 is EOL soon. ** Changed in: linux-azure (Ubuntu) Status: New => Invalid -- 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/1850185 Title: [linux-azure] 19.04 regression of KDUMP Status in linux-azure package in Ubuntu: Invalid Bug description: By default our test cases use DS1_v2 to test KDUMP, when we trigger a kernel panic, the VM enters into emergency mode, which can be seen on the serial console. This issue can be resolved if the VM is resized from DS1_v2 (1 vcpus, 3.5 GiB memory) to DS12_v2 (4 vcpus, 28 GiB memory). However, Ubuntu 18.04 and Ubuntu 19.10 KDUMP work using a VM size of DS1_v2. This issue only happens when using Ubuntu 19.04. The following appears on the 19.04 serial console when the issue occurs: [ OK ] Reached target Local File Systems (Pre). Mounting /boot/efi... Starting File System Check…/cloud/azure_resource-part1... [FAILED] Failed to mount /boot/efi. See 'systemctl status boot-efi.mount' for details. [DEPEND] Dependency failed for Local File Systems. [ OK ] Started File System Check …sk/cloud/azure_resource-part1. [ OK ] Started File System Check Daemon to report status. Starting GRUB failed boot detection... Starting Create final runt…dir for shutdown pivot root... Starting Tell Plymouth To Write Out Runtime Data... [ OK ] Started Emergency Shell. Starting Load AppArmor profiles... Starting Create Volatile Files and Directories... [ OK ] Stopped Dispatch Password …ts to Console Directory Watch. [ OK ] Reached target Emergency Mode. REPRO STEPS: Create Ubuntu 19.04 using size Standard_DS1_v2. Install kdump tools, reboot VM - apt update && apt install linux-crashdump, reboot VM, kdump-config show check the state is - ready to kdump. Trigger kernel panic - sysctl -w kernel.sysrq=1 && echo c > /proc/sysrq-trigger Expected behavior - VM reboot successfully and crash dump file and related subdirectories generated successfully. Current behavior - The VM is inaccessible from SSH, it enters into emergency mode, have to press Ctrl + D in serial console, then VM enters into normal reboot process, crash dump file and related subdirectories generated successfully. Update value for crashkernel to reserve the memory by updating the /etc/default/grub.d/kdump-tools.cfg file, run update-grub, reboot VM, dmesg | grep -i crashkernel check the memory is reserving successfully for crashkernel. Then retest (trigger kernel panic) against different memory setting for crashkernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1850185/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860603] [NEW] [linux-azure] VMs crashing due to 503 SMB errors
Public bug reported:
Several Azure VMs on AKS and are experiencing some random node restarts.
The issues was narrowed down to a NULL pointer dereference in
smb2_push_mandatory_locks().
The following commit fixes this issue:
6f582b273ec2 ("CIFS: Fix NULL-pointer dereference in smb2_push_mandatory_locks")
This commit landed in mainline as of v5.5-rc1. The commit has also been
applied to linux-azure-bionic in Ubuntu-azure-5.0.0-1029.31 via stable
updates.
However, this commit has not been applied to linux-azure-xenial, but it
is needed there. Please apply the commit to xenial.
** Affects: linux-azure (Ubuntu)
Importance: Undecided
Status: New
--
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/1860603
Title:
[linux-azure] VMs crashing due to 503 SMB errors
Status in linux-azure package in Ubuntu:
New
Bug description:
Several Azure VMs on AKS and are experiencing some random node
restarts.
The issues was narrowed down to a NULL pointer dereference in
smb2_push_mandatory_locks().
The following commit fixes this issue:
6f582b273ec2 ("CIFS: Fix NULL-pointer dereference in
smb2_push_mandatory_locks")
This commit landed in mainline as of v5.5-rc1. The commit has also
been applied to linux-azure-bionic in Ubuntu-azure-5.0.0-1029.31 via
stable updates.
However, this commit has not been applied to linux-azure-xenial, but
it is needed there. Please apply the commit to xenial.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1860603/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834364] Re: [linux-azure] Potential Hyper-V infoleak in NVMe Direct
** Information type changed from Private Security to Public Security
--
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/1834364
Title:
[linux-azure] Potential Hyper-V infoleak in NVMe Direct
Status in linux-azure package in Ubuntu:
New
Bug description:
The standard Linux NVMe driver allocates a kernel memory buffer that
is passed to the NVMe controller, but the driver does not initialize
the memory buffer to zero or any other value. It invokes the NVMe
function, which, in a Hyper-V guest, may not fill the entire buffer.
The driver then copies the buffer, including potentially uninitialized
bytes, back to user space.
This has been fixed in Linux 4.20 with the following two patches (the
1st patch had a bug, so the 2nd patch fixed the 1st patch). The
commits appear to have been cc'd to upstream stable. However, since
this is a security issue, we wanted to get them pulled into the linux-
azure kernels.
f3587d76da05 ("block: Clear kernel memory before copying to user")
f55adad601c6 ("block/bio: Do not zero user pages")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1834364/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834499] [NEW] [linux-azure] Block Layer Commits Requested in Azure Kernels
Public bug reported:
We would like to request the following two commits in the 16.04 and
18.04 linux-azure kernels:
f3587d76da05 ("block: Clear kernel memory before copying to user")
f55adad601c6 ("block/bio: Do not zero user pages")
These commits are in mainline as of v4.20 and have been cc'd to upstream
stable.
** Affects: linux-azure (Ubuntu)
Importance: Undecided
Status: New
--
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/1834499
Title:
[linux-azure] Block Layer Commits Requested in Azure Kernels
Status in linux-azure package in Ubuntu:
New
Bug description:
We would like to request the following two commits in the 16.04 and
18.04 linux-azure kernels:
f3587d76da05 ("block: Clear kernel memory before copying to user")
f55adad601c6 ("block/bio: Do not zero user pages")
These commits are in mainline as of v4.20 and have been cc'd to
upstream stable.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1834499/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835322] [NEW] [linux-azure] panic in ext4_resize_fs() found during storage testing
Public bug reported:
A panic was observed during file system testing. The trace is the
following:
[ 8783.243586] kernel BUG at
/build/linux-azure-3iFJ9j/linux-azure-4.18.0/fs/ext4/resize.c:266!
[ 8783.252751] invalid opcode: [#1] SMP PTI
[ 8783.256735] CPU: 7 PID: 39476 Comm: resize2fs Not tainted 4.18.0-1023-azure
#24~18.04.1-Ubuntu
[ 8783.256735] Hardware name: Microsoft Corporation Virtual Machine/Virtual
Machine, BIOS 090007 06/02/2017
[ 8783.256735] RIP: 0010:ext4_resize_fs+0x73b/0xf10
[ 8783.256735] Code: 50 ff ff ff 41 8b 75 10 4d 8b 65 00 85 f6 0f 94 c0 4d 85
e4 0f 94 c1 09 c8 83 bd 5c ff ff ff 01 7e 48 84 c0 0f 84 43 06 00 00 <0f> 0b 48
c7 c2 68 a7 8d 8f 48 c7 c6 00 fb 88 8f 4c 89 f7 e8 0d f8
[ 8783.256735] RSP: 0018:984e8dce7cb0 EFLAGS: 00010202
[ 8783.256735] RAX: 00205c01 RBX: 001f RCX:
[ 8783.256735] RDX: 8b1dbe1367d0 RSI: RDI:
[ 8783.256735] RBP: 984e8dce7d88 R08: 984e8dce7d4c R09: 984e8dce7d54
[ 8783.256735] R10: 0120 R11: 0001 R12: 8b1dbe136800
[ 8783.256735] R13: 8b1d74aefe80 R14: 8b1dbdeb9000 R15:
[ 8783.256735] FS: 7f213fed30c0() GS:8b1ded7c()
knlGS:
[ 8783.256735] CS: 0010 DS: ES: CR0: 80050033
[ 8783.256735] CR2: 556aa08ae9b8 CR3: 001b8e324005 CR4: 003606e0
[ 8783.256735] DR0: DR1: DR2:
[ 8783.256735] DR3: DR6: fffe0ff0 DR7: 0400
[ 8783.256735] Call Trace:
[ 8783.256735] ? security_capable+0x3c/0x60
[ 8783.256735] ext4_ioctl+0xf91/0x14d0
[ 8783.256735] ? audit_filter_rules.constprop.14+0x325/0xf90
[ 8783.256735] ? audit_filter_rules.constprop.14+0x24b/0xf90
[ 8783.256735] do_vfs_ioctl+0xa8/0x630
[ 8783.256735] ksys_ioctl+0x75/0x80
[ 8783.256735] __x64_sys_ioctl+0x1a/0x20
[ 8783.256735] do_syscall_64+0x6a/0x1a0
[ 8783.256735] entry_SYSCALL_64_after_hwframe+0x44/0xa9
[ 8783.256735] RIP: 0033:0x7f213f3825d7
[ 8783.256735] Code: b3 66 90 48 8b 05 b1 48 2d 00 64 c7 00 26 00 00 00 48 c7
c0 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 b8 10 00 00 00 0f 05 <48> 3d 01
f0 ff ff 73 01 c3 48 8b 0d 81 48 2d 00 f7 d8 64 89 01 48
[ 8783.256735] RSP: 002b:7ffe8effd688 EFLAGS: 0246 ORIG_RAX:
0010
[ 8783.256735] RAX: ffda RBX: 556aa08aa980 RCX: 7f213f3825d7
[ 8783.256735] RDX: 7ffe8effd7d0 RSI: 40086610 RDI: 0004
[ 8783.256735] RBP: 0004 R08: R09:
[ 8783.256735] R10: R11: 0246 R12: 556aa08ac980
[ 8783.256735] R13: 7ffe8effd7d0 R14: 556aa08a92d0 R15:
This issue is resolved by the following upstream commit:
f96c3ac8dfc2 ("ext4: fix crash during online resizing")
Commit f96c3ac8dfc2 is in mainline as of v5.1-rc1. This commit was requested
in the upstream stable kernels. However, the Ubuntu kernels are EOL upstream.
Please include this commit in the 16.04 and 18.04 linux-azure kernels.
** Affects: linux-azure (Ubuntu)
Importance: Undecided
Status: New
--
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/1835322
Title:
[linux-azure] panic in ext4_resize_fs() found during storage testing
Status in linux-azure package in Ubuntu:
New
Bug description:
A panic was observed during file system testing. The trace is the
following:
[ 8783.243586] kernel BUG at
/build/linux-azure-3iFJ9j/linux-azure-4.18.0/fs/ext4/resize.c:266!
[ 8783.252751] invalid opcode: [#1] SMP PTI
[ 8783.256735] CPU: 7 PID: 39476 Comm: resize2fs Not tainted
4.18.0-1023-azure #24~18.04.1-Ubuntu
[ 8783.256735] Hardware name: Microsoft Corporation Virtual Machine/Virtual
Machine, BIOS 090007 06/02/2017
[ 8783.256735] RIP: 0010:ext4_resize_fs+0x73b/0xf10
[ 8783.256735] Code: 50 ff ff ff 41 8b 75 10 4d 8b 65 00 85 f6 0f 94 c0 4d 85
e4 0f 94 c1 09 c8 83 bd 5c ff ff ff 01 7e 48 84 c0 0f 84 43 06 00 00 <0f> 0b 48
c7 c2 68 a7 8d 8f 48 c7 c6 00 fb 88 8f 4c 89 f7 e8 0d f8
[ 8783.256735] RSP: 0018:984e8dce7cb0 EFLAGS: 00010202
[ 8783.256735] RAX: 00205c01 RBX: 001f RCX:
[ 8783.256735] RDX: 8b1dbe1367d0 RSI: RDI:
[ 8783.256735] RBP: 984e8dce7d88 R08: 984e8dce7d4c R09:
984e8dce7d54
[ 8783.256735] R10: 0120 R11: 0001 R12:
8b1dbe136800
[ 8783.256735] R13: 8b1d74aefe80 R14: 8b1dbdeb9000 R15:
[ 8783.256735] FS: 7f213fed30c0() GS:8b1ded7c()
knlGS:
[ 8783.256735] CS: 0010 DS: ES: CR0: 80050033
[ 8783.256735] CR2: 556aa08ae9b8 CR3: 001b8e324005 CR4:
003606e0
[ 8783.25673
[Kernel-packages] [Bug 1759821] Re: Dell XPS 13 9360 bluetooth scan can not detect any device
** Changed in: linux (Ubuntu Xenial) Status: Triaged => In Progress ** Changed in: linux (Ubuntu) Status: Triaged => In Progress -- 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/1759821 Title: Dell XPS 13 9360 bluetooth scan can not detect any device Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: Dell XPS 13 9360 (CID 201606-22355) Image: OEM pre-installed image Kernel: 4.4.0-117-generic #141-Ubuntu SMP Tue Mar 13 11:58:07 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Click the bluetooth applet and try to add bt devices. The long scanning (> 5 mins) gets nothing. Reproducing rate: 100% [More Information] ubuntu@201606-22355:~$ lspci -nn 00:00.0 Host bridge [0600]: Intel Corporation Device [8086:5904] (rev 02) 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:5916] (rev 02) 00:04.0 Signal processing controller [1180]: Intel Corporation Skylake Processor Thermal Subsystem [8086:1903] (rev 02) 00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller [8086:9d2f] (rev 21) 00:14.2 Signal processing controller [1180]: Intel Corporation Sunrise Point-LP Thermal subsystem [8086:9d31] (rev 21) 00:15.0 Signal processing controller [1180]: Intel Corporation Sunrise Point-LP Serial IO I2C Controller [8086:9d60] (rev 21) 00:15.1 Signal processing controller [1180]: Intel Corporation Sunrise Point-LP Serial IO I2C Controller [8086:9d61] (rev 21) 00:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-LP CSME HECI [8086:9d3a] (rev 21) 00:1c.0 PCI bridge [0604]: Intel Corporation Device [8086:9d10] (rev f1) 00:1c.4 PCI bridge [0604]: Intel Corporation Sunrise Point-LP PCI Express Root Port [8086:9d14] (rev f1) 00:1c.5 PCI bridge [0604]: Intel Corporation Sunrise Point-LP PCI Express Root Port [8086:9d15] (rev f1) 00:1d.0 PCI bridge [0604]: Intel Corporation Device [8086:9d18] (rev f1) 00:1f.0 ISA bridge [0601]: Intel Corporation Device [8086:9d58] (rev 21) 00:1f.2 Memory controller [0580]: Intel Corporation Sunrise Point-LP PMC [8086:9d21] (rev 21) 00:1f.3 Audio device [0403]: Intel Corporation Device [8086:9d71] (rev 21) 00:1f.4 SMBus [0c05]: Intel Corporation Sunrise Point-LP SMBus [8086:9d23] (rev 21) 3a:00.0 Network controller [0280]: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter [168c:003e] (rev 32) 3b:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader [10ec:525a] (rev 01) 3c:00.0 Non-Volatile memory controller [0108]: Samsung Electronics Co Ltd NVMe SSD Controller [144d:a802] (rev 01) ubuntu@201606-22355:~$ rfkill list 0: hci0: Bluetooth Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no ubuntu@201606-22355:~$ So far this issue affects the following machines at least: - Dell XPS 13 9360 (CID 201606-22338) - Dell XPS 13 9360 (CID 201606-22355) - Dell Precision 5520 (201610-25144) - ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-117-generic 4.4.0-117.141 ProcVersionSignature: Ubuntu 4.4.0-117.141-generic 4.4.114 Uname: Linux 4.4.0-117-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1723 F pulseaudio Date: Thu Mar 29 18:39:27 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 HibernationDevice: RESUME=UUID=e30b2dfe-7ba1-4cde-876a-928e9bbb077b InstallationDate: Installed on 2018-03-23 (6 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. XPS 13 9360 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-117-generic.efi.signed root=UUID=488684c8-a47f-46bc-b84d-ad4bff229ccd ro automatic-oem-config quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-117-generic N/A linux-backports-modules-4.4.0-117-generic N/A linux-firmware 1.157.17 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/21/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.2 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.4.2:bd11/21/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. To manage notifications about
[Kernel-packages] [Bug 1759821] Re: Dell XPS 13 9360 bluetooth scan can not detect any device
Thanks for testing! I built a Xenial test kernel with a pick of mainline commit 7d06d5895c. The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1759821 Can you test this kernel and see if it resolves this bug? Note, to test this kernel, you need to install both the linux-image and linux-image-extra .deb packages. If we confirm this commit is the fix, I'll submit a Xenial SRU request. Thanks in advance! -- 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/1759821 Title: Dell XPS 13 9360 bluetooth scan can not detect any device Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: Dell XPS 13 9360 (CID 201606-22355) Image: OEM pre-installed image Kernel: 4.4.0-117-generic #141-Ubuntu SMP Tue Mar 13 11:58:07 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Click the bluetooth applet and try to add bt devices. The long scanning (> 5 mins) gets nothing. Reproducing rate: 100% [More Information] ubuntu@201606-22355:~$ lspci -nn 00:00.0 Host bridge [0600]: Intel Corporation Device [8086:5904] (rev 02) 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:5916] (rev 02) 00:04.0 Signal processing controller [1180]: Intel Corporation Skylake Processor Thermal Subsystem [8086:1903] (rev 02) 00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller [8086:9d2f] (rev 21) 00:14.2 Signal processing controller [1180]: Intel Corporation Sunrise Point-LP Thermal subsystem [8086:9d31] (rev 21) 00:15.0 Signal processing controller [1180]: Intel Corporation Sunrise Point-LP Serial IO I2C Controller [8086:9d60] (rev 21) 00:15.1 Signal processing controller [1180]: Intel Corporation Sunrise Point-LP Serial IO I2C Controller [8086:9d61] (rev 21) 00:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-LP CSME HECI [8086:9d3a] (rev 21) 00:1c.0 PCI bridge [0604]: Intel Corporation Device [8086:9d10] (rev f1) 00:1c.4 PCI bridge [0604]: Intel Corporation Sunrise Point-LP PCI Express Root Port [8086:9d14] (rev f1) 00:1c.5 PCI bridge [0604]: Intel Corporation Sunrise Point-LP PCI Express Root Port [8086:9d15] (rev f1) 00:1d.0 PCI bridge [0604]: Intel Corporation Device [8086:9d18] (rev f1) 00:1f.0 ISA bridge [0601]: Intel Corporation Device [8086:9d58] (rev 21) 00:1f.2 Memory controller [0580]: Intel Corporation Sunrise Point-LP PMC [8086:9d21] (rev 21) 00:1f.3 Audio device [0403]: Intel Corporation Device [8086:9d71] (rev 21) 00:1f.4 SMBus [0c05]: Intel Corporation Sunrise Point-LP SMBus [8086:9d23] (rev 21) 3a:00.0 Network controller [0280]: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter [168c:003e] (rev 32) 3b:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader [10ec:525a] (rev 01) 3c:00.0 Non-Volatile memory controller [0108]: Samsung Electronics Co Ltd NVMe SSD Controller [144d:a802] (rev 01) ubuntu@201606-22355:~$ rfkill list 0: hci0: Bluetooth Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no ubuntu@201606-22355:~$ So far this issue affects the following machines at least: - Dell XPS 13 9360 (CID 201606-22338) - Dell XPS 13 9360 (CID 201606-22355) - Dell Precision 5520 (201610-25144) - Dell Inspiron 7560 (201606-22349) - ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-117-generic 4.4.0-117.141 ProcVersionSignature: Ubuntu 4.4.0-117.141-generic 4.4.114 Uname: Linux 4.4.0-117-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1723 F pulseaudio Date: Thu Mar 29 18:39:27 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 HibernationDevice: RESUME=UUID=e30b2dfe-7ba1-4cde-876a-928e9bbb077b InstallationDate: Installed on 2018-03-23 (6 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. XPS 13 9360 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-117-generic.efi.signed root=UUID=488684c8-a47f-46bc-b84d-ad4bff229ccd ro automatic-oem-config quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-117-generic N/A linux-backports-modules-4.4.0-117-generic N/A linux-firmware 1.157.17 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/21/2017 dmi.bios.vendor: Del
[Kernel-packages] [Bug 1720219] Re: Repeated keys stop after a few characters (^@ character spam every second)
Commit 3b95206110a is now in the Artful -proposed kernel, 4.13.0-38. Would it be possible for you to test the proposed kernel and post back if it resolves this bug? See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance! ** Changed in: linux (Ubuntu Artful) Status: In Progress => Fix Committed -- 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/1720219 Title: Repeated keys stop after a few characters (^@ character spam every second) Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: In Progress Status in linux source package in Artful: Fix Committed Bug description: Long pressing a key will only repeat a few characters or won't repeat at all in the default 17.10 GNOME environment, it affects all keys including backspace and arrows. It isn't application specific, the problem is always there whether be it terminal or firefox. Setting the repeat delay to 0 will instantly trigger it, however it will still stop after a few characters. I freshly installed 17.10 on a Lenovo Ideapad 700, I haven't had the problem in 16.04 with GNOME 3.22. Edit: Happens in Xorg as well. --- ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: fecka 1156 F...m pulseaudio /dev/snd/controlC0: fecka 1156 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-09-28 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170924) MachineType: LENOVO 80RU Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic root=UUID=ec711d91-c22f-4be9-8820-b1bdca284667 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 RelatedPackageVersions: linux-restricted-modules-4.13.0-12-generic N/A linux-backports-modules-4.13.0-12-generic N/A linux-firmware 1.168 Tags: artful wayland-session Uname: Linux 4.13.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/29/2016 dmi.bios.vendor: LENOVO dmi.bios.version: E5CN56WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo ideapad 700-15ISK dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 700-15ISK dmi.modalias: dmi:bvnLENOVO:bvrE5CN56WW:bd09/29/2016:svnLENOVO:pn80RU:pvrLenovoideapad700-15ISK:rvnLENOVO:rnLenovoideapad700-15ISK:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad700-15ISK: dmi.product.family: IDEAPAD dmi.product.name: 80RU dmi.product.version: Lenovo ideapad 700-15ISK dmi.sys.vendor: LENOVO --- ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: fecka 1156 F...m pulseaudio /dev/snd/controlC0: fecka 1156 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-09-28 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170924) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 0bda:0821 Realtek Semiconductor Corp. Bus 001 Device 004: ID 174f:14e6 Syntek Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80RU Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic root=UUID=ec711d91-c22f-4be9-8820-b1bdca284667 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 RelatedPackageVersions: linux-restricted-modules-4.13.0-12-generic N/A linux-backports-modules-4.13.0-12-generic N/A linux-firmware 1.168 Tags: artful wayland-session Uname: Linux 4.13.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/29/2016 dmi.bios.vendor: LENOVO dmi.bios.version: E5CN56WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo ideapad 700-15ISK dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 700-15ISK dmi.modalias: dmi:bvnLENOVO:bvrE5CN56WW:bd09/29/2016:svnLENOVO:pn80RU:pvrLenovoideapad700-15ISK:rvnLENOVO:rnLenovoideapad700-15ISK:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideap
[Kernel-packages] [Bug 1720219] Re: Repeated keys stop after a few characters (^@ character spam every second)
Commit 3b95206110a was never applied to the upstream stable 4.4.y updates, so I'll submit an SRU request for Xenial. -- 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/1720219 Title: Repeated keys stop after a few characters (^@ character spam every second) Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: In Progress Status in linux source package in Artful: Fix Committed Bug description: Long pressing a key will only repeat a few characters or won't repeat at all in the default 17.10 GNOME environment, it affects all keys including backspace and arrows. It isn't application specific, the problem is always there whether be it terminal or firefox. Setting the repeat delay to 0 will instantly trigger it, however it will still stop after a few characters. I freshly installed 17.10 on a Lenovo Ideapad 700, I haven't had the problem in 16.04 with GNOME 3.22. Edit: Happens in Xorg as well. --- ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: fecka 1156 F...m pulseaudio /dev/snd/controlC0: fecka 1156 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-09-28 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170924) MachineType: LENOVO 80RU Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic root=UUID=ec711d91-c22f-4be9-8820-b1bdca284667 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 RelatedPackageVersions: linux-restricted-modules-4.13.0-12-generic N/A linux-backports-modules-4.13.0-12-generic N/A linux-firmware 1.168 Tags: artful wayland-session Uname: Linux 4.13.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/29/2016 dmi.bios.vendor: LENOVO dmi.bios.version: E5CN56WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo ideapad 700-15ISK dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 700-15ISK dmi.modalias: dmi:bvnLENOVO:bvrE5CN56WW:bd09/29/2016:svnLENOVO:pn80RU:pvrLenovoideapad700-15ISK:rvnLENOVO:rnLenovoideapad700-15ISK:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad700-15ISK: dmi.product.family: IDEAPAD dmi.product.name: 80RU dmi.product.version: Lenovo ideapad 700-15ISK dmi.sys.vendor: LENOVO --- ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: fecka 1156 F...m pulseaudio /dev/snd/controlC0: fecka 1156 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-09-28 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170924) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 0bda:0821 Realtek Semiconductor Corp. Bus 001 Device 004: ID 174f:14e6 Syntek Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80RU Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic root=UUID=ec711d91-c22f-4be9-8820-b1bdca284667 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 RelatedPackageVersions: linux-restricted-modules-4.13.0-12-generic N/A linux-backports-modules-4.13.0-12-generic N/A linux-firmware 1.168 Tags: artful wayland-session Uname: Linux 4.13.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/29/2016 dmi.bios.vendor: LENOVO dmi.bios.version: E5CN56WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo ideapad 700-15ISK dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 700-15ISK dmi.modalias: dmi:bvnLENOVO:bvrE5CN56WW:bd09/29/2016:svnLENOVO:pn80RU:pvrLenovoideapad700-15ISK:rvnLENOVO:rnLenovoideapad700-15ISK:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad700-15ISK: dmi.product.family: IDEAPAD dmi.product.name: 80RU dmi.product.version: Lenovo ideapad 700-15ISK dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1720219/+subscript
[Kernel-packages] [Bug 1720219] Re: Repeated keys stop after a few characters (^@ character spam every second)
** Changed in: linux (Ubuntu) Status: In Progress => Fix Released -- 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/1720219 Title: Repeated keys stop after a few characters (^@ character spam every second) Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: In Progress Status in linux source package in Artful: Fix Committed Bug description: Long pressing a key will only repeat a few characters or won't repeat at all in the default 17.10 GNOME environment, it affects all keys including backspace and arrows. It isn't application specific, the problem is always there whether be it terminal or firefox. Setting the repeat delay to 0 will instantly trigger it, however it will still stop after a few characters. I freshly installed 17.10 on a Lenovo Ideapad 700, I haven't had the problem in 16.04 with GNOME 3.22. Edit: Happens in Xorg as well. --- ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: fecka 1156 F...m pulseaudio /dev/snd/controlC0: fecka 1156 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-09-28 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170924) MachineType: LENOVO 80RU Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic root=UUID=ec711d91-c22f-4be9-8820-b1bdca284667 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 RelatedPackageVersions: linux-restricted-modules-4.13.0-12-generic N/A linux-backports-modules-4.13.0-12-generic N/A linux-firmware 1.168 Tags: artful wayland-session Uname: Linux 4.13.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/29/2016 dmi.bios.vendor: LENOVO dmi.bios.version: E5CN56WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo ideapad 700-15ISK dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 700-15ISK dmi.modalias: dmi:bvnLENOVO:bvrE5CN56WW:bd09/29/2016:svnLENOVO:pn80RU:pvrLenovoideapad700-15ISK:rvnLENOVO:rnLenovoideapad700-15ISK:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad700-15ISK: dmi.product.family: IDEAPAD dmi.product.name: 80RU dmi.product.version: Lenovo ideapad 700-15ISK dmi.sys.vendor: LENOVO --- ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: fecka 1156 F...m pulseaudio /dev/snd/controlC0: fecka 1156 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-09-28 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170924) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 0bda:0821 Realtek Semiconductor Corp. Bus 001 Device 004: ID 174f:14e6 Syntek Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80RU Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic root=UUID=ec711d91-c22f-4be9-8820-b1bdca284667 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 RelatedPackageVersions: linux-restricted-modules-4.13.0-12-generic N/A linux-backports-modules-4.13.0-12-generic N/A linux-firmware 1.168 Tags: artful wayland-session Uname: Linux 4.13.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/29/2016 dmi.bios.vendor: LENOVO dmi.bios.version: E5CN56WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo ideapad 700-15ISK dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 700-15ISK dmi.modalias: dmi:bvnLENOVO:bvrE5CN56WW:bd09/29/2016:svnLENOVO:pn80RU:pvrLenovoideapad700-15ISK:rvnLENOVO:rnLenovoideapad700-15ISK:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad700-15ISK: dmi.product.family: IDEAPAD dmi.product.name: 80RU dmi.product.version: Lenovo ideapad 700-15ISK dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1720219/+subscriptions -- Mailing list: https://launchpad.ne
[Kernel-packages] [Bug 1720219] Re: Repeated keys stop after a few characters (^@ character spam every second)
@Sergey, are you seeing this bug with the Xenial HWE kernel or the stock 4.4 kernel? Are there others seeing this bug on Xenial? I don't see that the patch was accepted in upstream stable 4.4, so I'm curious if it is still needed in Xenial. -- 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/1720219 Title: Repeated keys stop after a few characters (^@ character spam every second) Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: In Progress Status in linux source package in Artful: Fix Committed Bug description: Long pressing a key will only repeat a few characters or won't repeat at all in the default 17.10 GNOME environment, it affects all keys including backspace and arrows. It isn't application specific, the problem is always there whether be it terminal or firefox. Setting the repeat delay to 0 will instantly trigger it, however it will still stop after a few characters. I freshly installed 17.10 on a Lenovo Ideapad 700, I haven't had the problem in 16.04 with GNOME 3.22. Edit: Happens in Xorg as well. --- ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: fecka 1156 F...m pulseaudio /dev/snd/controlC0: fecka 1156 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-09-28 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170924) MachineType: LENOVO 80RU Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic root=UUID=ec711d91-c22f-4be9-8820-b1bdca284667 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 RelatedPackageVersions: linux-restricted-modules-4.13.0-12-generic N/A linux-backports-modules-4.13.0-12-generic N/A linux-firmware 1.168 Tags: artful wayland-session Uname: Linux 4.13.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/29/2016 dmi.bios.vendor: LENOVO dmi.bios.version: E5CN56WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo ideapad 700-15ISK dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 700-15ISK dmi.modalias: dmi:bvnLENOVO:bvrE5CN56WW:bd09/29/2016:svnLENOVO:pn80RU:pvrLenovoideapad700-15ISK:rvnLENOVO:rnLenovoideapad700-15ISK:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad700-15ISK: dmi.product.family: IDEAPAD dmi.product.name: 80RU dmi.product.version: Lenovo ideapad 700-15ISK dmi.sys.vendor: LENOVO --- ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: fecka 1156 F...m pulseaudio /dev/snd/controlC0: fecka 1156 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-09-28 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170924) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 0bda:0821 Realtek Semiconductor Corp. Bus 001 Device 004: ID 174f:14e6 Syntek Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80RU Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic root=UUID=ec711d91-c22f-4be9-8820-b1bdca284667 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 RelatedPackageVersions: linux-restricted-modules-4.13.0-12-generic N/A linux-backports-modules-4.13.0-12-generic N/A linux-firmware 1.168 Tags: artful wayland-session Uname: Linux 4.13.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/29/2016 dmi.bios.vendor: LENOVO dmi.bios.version: E5CN56WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo ideapad 700-15ISK dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 700-15ISK dmi.modalias: dmi:bvnLENOVO:bvrE5CN56WW:bd09/29/2016:svnLENOVO:pn80RU:pvrLenovoideapad700-15ISK:rvnLENOVO:rnLenovoideapad700-15ISK:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad700-15ISK: dmi.product.family: IDEAPAD dmi.product.name: 80RU dmi.product.version: Lenovo ideapad 700-15ISK dmi.sys.vendor:
