[Bug 2058052] Re: Enable Intel IDPF support on ARM64
** Description changed: [Impact] * Request from Google to enable Intel IDPF driver support on ARM64 [Fix] - * Mantic - - * Jammy - + UBUNTU: [Config] gcp: Add ARM64 support for IDPF driver + [Test Case] * Compile tested * Boot tested + * Google performed some basic validation of the IDPF driver on arm64 [Where things could go wrong] * Low chance of regression, changes have been upstream since 6.6 kernel * Bulk of changes in IDPF driver * Other changes to network drivers largely adding #include directives [Other Info] * SF #00381197 ** Also affects: linux-gke (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-gcp (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: linux-gcp (Ubuntu Noble) Status: New => In Progress ** Changed in: linux-gcp (Ubuntu Noble) Importance: Undecided => Medium ** Changed in: linux-gcp (Ubuntu Noble) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux-gke (Ubuntu Noble) Status: New => In Progress ** Changed in: linux-gke (Ubuntu Noble) Importance: Undecided => Medium ** Changed in: linux-gke (Ubuntu Noble) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058052 Title: Enable Intel IDPF support on ARM64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2058052/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2042564] Re: Performance regression in the 5.15 Ubuntu 20.04 kernel compared to 5.4 Ubuntu 20.04 kernel
** Changed in: linux (Ubuntu Focal) Status: Triaged => Won't Fix ** Changed in: linux (Ubuntu) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2042564 Title: Performance regression in the 5.15 Ubuntu 20.04 kernel compared to 5.4 Ubuntu 20.04 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042564/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063315] Re: Suspend & Resume functionality broken/timesout in GCE
A kernel bisect is underway. We should have further details regarding the commit that introduced this regression soon. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063315 Title: Suspend & Resume functionality broken/timesout in GCE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/2063315/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063315] Re: Suspend & Resume functionality broken/timesout in GCE
** Changed in: linux-gcp (Ubuntu Noble) Status: New => In Progress ** Changed in: linux-gcp (Ubuntu Noble) Importance: Undecided => High ** Changed in: linux-gcp (Ubuntu Noble) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063315 Title: Suspend & Resume functionality broken/timesout in GCE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/2063315/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054810] Re: Adding bpf to CONFIG_LSM in linux kernel
Thanks, Eric! I'm going to build some test kernels and will post them shortly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054810 Title: Adding bpf to CONFIG_LSM in linux kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054810/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964941] Re: Adding bpf to CONFIG_LSM in 5.13 kernels
*** This bug is a duplicate of bug 2054810 *** https://bugs.launchpad.net/bugs/2054810 ** Changed in: linux (Ubuntu) Status: Expired => Triaged ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** This bug has been marked a duplicate of bug 2054810 Adding bpf to CONFIG_LSM in linux kernel -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964941 Title: Adding bpf to CONFIG_LSM in 5.13 kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964941/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054810] Re: Adding bpf to CONFIG_LSM in linux kernel
** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Noble) Importance: Medium Assignee: Joseph Salisbury (jsalisbury) Status: Confirmed ** Changed in: linux (Ubuntu Mantic) Status: New => Triaged ** Changed in: linux (Ubuntu Jammy) Status: New => Triaged ** Changed in: linux (Ubuntu Noble) Status: Confirmed => Triaged ** Changed in: linux (Ubuntu Mantic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Mantic) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054810 Title: Adding bpf to CONFIG_LSM in linux kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054810/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2053101] Re: Backported rename of GENHD_FL_NO_PART_SCAN to GENHD_FL_NO_PART breaks existing modules
** Changed in: linux (Ubuntu) Assignee: Joseph Salisbury (jsalisbury) => (unassigned) ** Changed in: linux (Ubuntu Jammy) Assignee: Joseph Salisbury (jsalisbury) => (unassigned) ** No longer affects: linux-gcp (Ubuntu) ** No longer affects: linux-realtime (Ubuntu) ** Changed in: linux (Ubuntu Jammy) Status: In Progress => Won't Fix ** Changed in: linux (Ubuntu) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2053101 Title: Backported rename of GENHD_FL_NO_PART_SCAN to GENHD_FL_NO_PART breaks existing modules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2053101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2053101] Re: Backported rename of GENHD_FL_NO_PART_SCAN to GENHD_FL_NO_PART breaks existing modules
As a general rule, the kernel internal interface changes all the time and it cannot take into account out of tree module. It's the responsibility of the maintainers of these modules to keep up with upstream changes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2053101 Title: Backported rename of GENHD_FL_NO_PART_SCAN to GENHD_FL_NO_PART breaks existing modules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2053101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2053101] Re: Backported rename of GENHD_FL_NO_PART_SCAN to GENHD_FL_NO_PART breaks existing modules
The following commit changed the name of that variable: 99a4e9bce56b block: rename GENHD_FL_NO_PART_SCAN to GENHD_FL_NO_PART That commit was applied to the gcp kernel via stable updates from Jammy (22.04) version: 5.15.0-93.103 Jammy received it from upstream stable updates via: c6ce1c5dd327 block: rename GENHD_FL_NO_PART_SCAN to GENHD_FL_NO_PART That commit was applied to upstream stable in version: v5.15.132 I'll report this to upstream and see what the suggested fix may be. ** Changed in: linux-signed-gcp-5.15 (Ubuntu) Importance: Undecided => High ** Changed in: linux-signed-gcp-5.15 (Ubuntu) Status: Confirmed => In Progress ** Changed in: linux-signed-gcp-5.15 (Ubuntu) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Package changed: linux-signed-gcp-5.15 (Ubuntu) => linux (Ubuntu) ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => High ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Tags added: kernel-key ** Also affects: linux-realtime (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux-realtime (Ubuntu Jammy) ** Changed in: linux-realtime (Ubuntu) Importance: Undecided => High ** Changed in: linux-realtime (Ubuntu) Status: New => In Progress ** Changed in: linux-realtime (Ubuntu) Status: In Progress => Triaged ** Also affects: linux-gcp (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-gcp (Ubuntu) Status: New => Triaged ** Changed in: linux-gcp (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2053101 Title: Backported rename of GENHD_FL_NO_PART_SCAN to GENHD_FL_NO_PART breaks existing modules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2053101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2039720] Re: Intel IDPF support
** Tags removed: verification-needed-jammy-linux-gke ** Tags added: verification-done-jammy-linux-gke -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2039720 Title: Intel IDPF support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2039720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2049922] Re: PCI ATS quirk patch needed for IDPF
** Tags removed: verification-needed-bionic-linux-gcp-5.4 ** Tags added: verification-done-bionic-linux-gcp-5.4 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2049922 Title: PCI ATS quirk patch needed for IDPF To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2049922/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2049922] Re: PCI ATS quirk patch needed for IDPF
** Tags removed: verification-needed-focal-linux-gcp ** Tags added: verification-done-focal-linux-gcp -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2049922 Title: PCI ATS quirk patch needed for IDPF To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2049922/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2049922] Re: PCI ATS quirk patch needed for IDPF
** Tags removed: verification-needed-bionic-linux-gcp-4.15 ** Tags added: verification-done-bionic-linux-gcp-4.15 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2049922 Title: PCI ATS quirk patch needed for IDPF To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2049922/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058052] [NEW] Enable Intel IDPF support on ARM64
Public bug reported: [Impact] * Request from Google to enable Intel IDPF driver support on ARM64 [Fix] * Mantic - * Jammy - [Test Case] * Compile tested * Boot tested [Where things could go wrong] * Low chance of regression, changes have been upstream since 6.6 kernel * Bulk of changes in IDPF driver * Other changes to network drivers largely adding #include directives [Other Info] * SF #00381197 ** Affects: linux-gcp (Ubuntu) Importance: Medium Assignee: Joseph Salisbury (jsalisbury) Status: In Progress ** Affects: linux-gke (Ubuntu) Importance: Medium Assignee: Joseph Salisbury (jsalisbury) Status: In Progress ** Affects: linux-gcp (Ubuntu Jammy) Importance: Medium Assignee: Joseph Salisbury (jsalisbury) Status: In Progress ** Affects: linux-gke (Ubuntu Jammy) Importance: Medium Assignee: Joseph Salisbury (jsalisbury) Status: In Progress ** Affects: linux-gcp (Ubuntu Mantic) Importance: Medium Assignee: Joseph Salisbury (jsalisbury) Status: In Progress ** Changed in: linux-gcp (Ubuntu) Status: New => In Progress ** Changed in: linux-gcp (Ubuntu) Importance: Undecided => Medium ** Changed in: linux-gcp (Ubuntu) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Also affects: linux-gcp (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-gcp (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: linux-gcp (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-gcp (Ubuntu Mantic) Status: New => In Progress ** Changed in: linux-gcp (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux-gcp (Ubuntu Mantic) Importance: Undecided => Medium ** Changed in: linux-gcp (Ubuntu Jammy) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux-gcp (Ubuntu Mantic) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Also affects: linux-gke (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux-gke (Ubuntu Mantic) ** Changed in: linux-gke (Ubuntu) Status: New => In Progress ** Changed in: linux-gke (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-gke (Ubuntu) Importance: Undecided => Medium ** Changed in: linux-gke (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux-gke (Ubuntu) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux-gke (Ubuntu Jammy) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058052 Title: Enable Intel IDPF support on ARM64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2058052/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2042564] Re: Performance regression in the 5.15 Ubuntu 20.04 kernel compared to 5.4 Ubuntu 20.04 kernel
I performed a bisect between the 5.4 and 5.15 kernels. The performance
regression was introduced by a stable update in 5.15.57 by the following
commit:
62b4db57eefec ("x86/entry: Add kernel IBRS implementation")
This commit applies IBRS kernel mitigation for Spectre_v2. IBRS is:
Indirect Branch Restricted Speculation.
This commit was also applied up upstream stable 5.4 with the following SHA1:
a3111faed5c1d ("x86/entry: Add kernel IBRS implementation")
However, the backport to 5.4 did not introduce as much as a performance
regression as the backport to 5.15. There are many difference between
the 5.4 and 5.15 backports of the commit. Much of the assembly logic in
5.15 does not exist in 5.4, since it was not needed.
There are several commits that are later applied to 5.15 stable that
depend on this patch, so it would not be easily reverted.
One option is to use a boot option to disable IBRS mitigation. However,
the security versus performance trade-off must be considered carefully.
IBRS can be disabled with the boot parameter "noibrs"
There is a wiki page that describes the various boot parameters here:
https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/SpectreAndMeltdown/MitigationControls
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2042564
Title:
Performance regression in the 5.15 Ubuntu 20.04 kernel compared to 5.4
Ubuntu 20.04 kernel
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042564/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972899] Re: [Regression] Real-time Kernel Build Failure
** Also affects: linux (Ubuntu Kinetic) Importance: High Assignee: Joseph Salisbury (jsalisbury) Status: In Progress ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => High ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** No longer affects: linux (Ubuntu Kinetic) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972899 Title: [Regression] Real-time Kernel Build Failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1972899/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970077] Re: efivars file system missing in Ubuntu 22.04 real-time kernel
** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Incomplete => Triaged ** Package changed: linux (Ubuntu) => ubuntu-realtime -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970077 Title: efivars file system missing in Ubuntu 22.04 real-time kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-realtime/+bug/1970077/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968902] Re: ARM64_SW_TTBR0_PAN Should Be Enabled For Oracle Kernels
** Description changed:
- The ARM64_SW_TTBR0_PAN was disabled by commit:
+ == SRU Justification ==
+ The config option CONFIG_ARM64_SW_TTBR0_PAN was unintentionally disabled in
the
+ linux-oracle kernels by the following commit:
c25f2bf469b3 ("UBUNTU: [config] oracle: Bring-up for arm64 support")
- This config option is enabled on all other Ubuntu kernels and should be
- enabled for the Oracle kernel.
+ CONFIG_ARM64_SW_TTBR0_PAN is enabled for all other kernels and should be
enabled
+ for the oracle kernels.
+
+ v2: * Add enforcment line to annotations.
+ * Removed patch for Impish, since config was re-enabled by someone else
in
+ that relese.
+
+ == Fix ==
+ UBUNTU: [config] oracle: Enable CONFIG_ARM64_SW_TTBR0_PAN
+
+ == Regression Potential ==
+ Low. Option was previously enabled.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968902
Title:
ARM64_SW_TTBR0_PAN Should Be Enabled For Oracle Kernels
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1968902/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968902] Re: ARM64_SW_TTBR0_PAN Should Be Enabled For Oracle Kernels
** No longer affects: linux (Ubuntu Xenial) ** No longer affects: linux (Ubuntu Bionic) ** Changed in: linux (Ubuntu Impish) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968902 Title: ARM64_SW_TTBR0_PAN Should Be Enabled For Oracle Kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968902/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968902] [NEW] ARM64_SW_TTBR0_PAN Should Be Enabled For Oracle Kernels
Public bug reported:
The ARM64_SW_TTBR0_PAN was disabled by commit:
c25f2bf469b3 ("UBUNTU: [config] oracle: Bring-up for arm64 support")
This config option is enabled on all other Ubuntu kernels and should be
enabled for the Oracle kernel.
** Affects: linux (Ubuntu)
Importance: Medium
Assignee: Joseph Salisbury (jsalisbury)
Status: In Progress
** Affects: linux (Ubuntu Xenial)
Importance: Medium
Assignee: Joseph Salisbury (jsalisbury)
Status: In Progress
** Affects: linux (Ubuntu Bionic)
Importance: Medium
Assignee: Joseph Salisbury (jsalisbury)
Status: In Progress
** Affects: linux (Ubuntu Focal)
Importance: Medium
Assignee: Joseph Salisbury (jsalisbury)
Status: In Progress
** Affects: linux (Ubuntu Impish)
Importance: Medium
Assignee: Joseph Salisbury (jsalisbury)
Status: New
** Changed in: linux (Ubuntu)
Status: New => In Progress
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Impish)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Status: New => In Progress
** Changed in: linux (Ubuntu Bionic)
Status: New => In Progress
** Changed in: linux (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Bionic)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu Impish)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu Impish)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968902
Title:
ARM64_SW_TTBR0_PAN Should Be Enabled For Oracle Kernels
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968902/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938048] Re: 5.13 RT kernel hangs on SMP shutdown
Could not reproduce in 5.15. ** Changed in: linux (Ubuntu) Status: Triaged => Incomplete ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938048 Title: 5.13 RT kernel hangs on SMP shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938048/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938918] Re: 5.13 RT kernel hits scheduling while atomic with stress-ng enosys stressor
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938918 Title: 5.13 RT kernel hits scheduling while atomic with stress-ng enosys stressor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938918] Re: 5.13 RT kernel hits scheduling while atomic with stress-ng enosys stressor
** Changed in: linux (Ubuntu) Assignee: Krzysztof Kozlowski (krzk) => Joseph Salisbury (jsalisbury) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938918 Title: 5.13 RT kernel hits scheduling while atomic with stress-ng enosys stressor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938048] Re: 5.13 RT kernel hangs on SMP shutdown
** Changed in: linux (Ubuntu) Assignee: Krzysztof Kozlowski (krzk) => Joseph Salisbury (jsalisbury) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938048 Title: 5.13 RT kernel hangs on SMP shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938048/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959610] [NEW] ubuntu_kernel_selftests / ftrace:ftracetest do_softirq failure on Jammy realtime
Public bug reported: do_softirq does not exist on preempt RT kernel. This is causing a failure in ftrace:ftracetest which reports: "echo: I/O error". Failure is reported for step 32 in Jenkins job: 23:48:45 DEBUG| [stdout] # selftests: ftrace: ftracetest 23:48:45 DEBUG| [stdout] # === Ftrace unit tests === 23:48:45 DEBUG| [stdout] # [1] Basic trace file check [PASS] 23:48:49 DEBUG| [stdout] # [2] Basic test for tracers [PASS] 23:48:49 DEBUG| [stdout] # [3] Basic trace clock test [PASS] 23:48:49 DEBUG| [stdout] # [4] Basic event tracing check[PASS] 23:48:50 DEBUG| [stdout] # [5] Change the ringbuffer size [PASS] 23:48:50 DEBUG| [stdout] # [6] Snapshot and tracing setting [PASS] 23:48:50 DEBUG| [stdout] # [7] trace_pipe and trace_marker [PASS] 23:49:38 DEBUG| [stdout] # [8] Test ftrace direct functions against tracers [PASS] 23:49:57 DEBUG| [stdout] # [9] Test ftrace direct functions against kprobes [PASS] 23:49:57 DEBUG| [stdout] # [10] Generic dynamic event - add/remove eprobe events[PASS] 23:49:57 DEBUG| [stdout] # [11] Generic dynamic event - add/remove kprobe events[PASS] 23:49:57 DEBUG| [stdout] # [12] Generic dynamic event - add/remove synthetic events [PASS] 23:49:57 DEBUG| [stdout] # [13] Generic dynamic event - selective clear (compatibility) [PASS] 23:49:58 DEBUG| [stdout] # [14] Generic dynamic event - generic clear event [PASS] 23:49:58 DEBUG| [stdout] # [15] Generic dynamic event - check if duplicate events are caught[PASS] 23:49:58 DEBUG| [stdout] # [16] event tracing - enable/disable with event level files [PASS] 23:49:58 DEBUG| [stdout] # [17] event tracing - restricts events based on pid notrace filtering [PASS] 23:49:59 DEBUG| [stdout] # [18] event tracing - restricts events based on pid [PASS] 23:49:59 DEBUG| [stdout] # [19] event tracing - enable/disable with subsystem level files [PASS] 23:50:00 DEBUG| [stdout] # [20] event tracing - enable/disable with top level files [PASS] 23:50:01 DEBUG| [stdout] # [21] Test trace_printk from module [PASS] 23:50:04 DEBUG| [stdout] # [22] ftrace - function graph filters with stack tracer [PASS] 23:50:05 DEBUG| [stdout] # [23] ftrace - function graph filters [PASS] 23:50:06 DEBUG| [stdout] # [24] ftrace - function pid notrace filters [PASS] 23:50:06 DEBUG| [stdout] # [25] ftrace - function pid filters [PASS] 23:50:08 DEBUG| [stdout] # [26] ftrace - stacktrace filter command [PASS] 23:50:08 DEBUG| [stdout] # [27] ftrace - function trace with cpumask[PASS] 23:50:12 DEBUG| [stdout] # [28] ftrace - test for function event triggers [PASS] 23:50:13 DEBUG| [stdout] # [29] ftrace - function trace on module [PASS] 23:50:16 DEBUG| [stdout] # [30] ftrace - function profiling [PASS] 23:50:21 DEBUG| [stdout] # [31] ftrace - function profiler with function tracing[PASS] 23:50:22 DEBUG| [stdout] # [32] ftrace - test reading of set_ftrace_filter [FAIL] 23:50:24 DEBUG| [stdout] # [33] ftrace - test for function traceon/off triggers [PASS] 23:50:24 DEBUG| [stdout] # [34] ftrace - test tracing error log support [PASS] 23:50:28 DEBUG| [stdout] # [35] Test creation and deletion of trace instances while setting an event[PASS] 23:50:29 DEBUG| [stdout] # [36] Test creation and deletion of trace instances [PASS] 23:50:30 DEBUG| [stdout] # [37] Kprobe dynamic event - adding and removing [PASS] 23:50:30 DEBUG| [stdout] # [38] Kprobe dynamic event - busy event check [PASS] 23:50:30 DEBUG| [stdout] # [39] Kprobe dynamic event with arguments [PASS] 23:50:30 DEBUG| [stdout] # [40] Kprobe event with comm arguments[PASS] 23:50:30 DEBUG| [stdout] # [41] Kprobe event string type argument [PASS] 23:50:31 DEBUG| [stdout] # [42] Kprobe event symbol argument[PASS] 23:50:32 DEBUG| [stdout] # [43] Kprobe event argument syntax[PASS] 23:50:32 DEBUG| [stdout] # [44] Kprobes event arguments with types [PASS] 23:50:32 DEBUG| [stdout] # [45] Kprobe event user-memory access [PASS] 23:50:33 DEBUG| [stdout] # [46] Kprobe event auto/manual naming [PASS] 23:50:33 DEBUG| [stdout] # [47] Kprobe dynamic event with function tracer [PASS] 23:50:34 DEBUG| [stdout] # [48] Create/delete multiprobe on kprobe event [PASS] 23:50:34 DEBUG| [stdout] # [49] Kprobe event parser error log check [PASS] 23:50:35 DEBUG| [stdout] # [50] Kretprobe dynamic event with arguments [PASS] 23:50:35 DEBUG| [stdout] # [51] Kretprobe dynamic event with maxactive [PASS] 23:50:35 DEBUG| [stdout] # [52] Kretprobe %return suffix test [PASS] 23:51:00 DEBUG| [stdout] # [53] Register/unregister many kprobe events [PASS] 23:51:00 DEBUG| [stdout] # [54] Kprobe dynamic event - adding and removing [PASS] 23:51:01 DEBUG| [stdout] # [55] Uprobe event parser error log check [PASS] 23:51:01 DEBUG| [stdout] # [56] test for the preemptirqsoff tracer [UNSUPPORTED] 23:51:32 DEBUG| [stdout] # [57] Meta-selftest:
[Bug 1946486] Re: Unable to reboot ARM64 node with 5.15 realtime
** Changed in: linux (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946486 Title: Unable to reboot ARM64 node with 5.15 realtime To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1946486/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950968] Re: v5.15 RT kernel fails to boot on some arm64 instances
** Changed in: linux (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950968 Title: v5.15 RT kernel fails to boot on some arm64 instances To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950968/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946486] Re: Unable to reboot ARM64 node with 5.11.0-27-realtime
The 5.11 kernel will not support realtime, so updating bug to reflect Focal and 5.15. ** Changed in: linux (Ubuntu) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Hirsute) Status: Confirmed => Invalid ** Summary changed: - Unable to reboot ARM64 node with 5.11.0-27-realtime + Unable to reboot ARM64 node with 5.15 realtime -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946486 Title: Unable to reboot ARM64 node with 5.15 realtime To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1946486/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950968] Re: v5.15 RT kernel fails to boot on some arm64 instances
The linux-modules-extra package is not a dependency for this kernel, which prevented installation of the qede module. I'll submit a patch to add extra as a dependency. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950968 Title: v5.15 RT kernel fails to boot on some arm64 instances To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950968/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950968] Re: v5.15 RT kernel fails to boot on some arm64 instances
** Changed in: linux (Ubuntu Jammy) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950968 Title: v5.15 RT kernel fails to boot on some arm64 instances To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950968/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946486] Re: Unable to reboot ARM64 node with 5.11.0-27-realtime
** Changed in: linux (Ubuntu Hirsute) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu Hirsute) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946486 Title: Unable to reboot ARM64 node with 5.11.0-27-realtime To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1946486/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950968] Re: v5.15 RT kernel fails to boot on some arm64 instances
** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950968 Title: v5.15 RT kernel fails to boot on some arm64 instances To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950968/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931497] Re: Patch To Fix Bug in the Linux Block Layer Responsible For Merging BIOs
** Description changed:
There is a bug in the Linux block layer responsible for merging BIOs
that go across the page boundary. This bug was introduced in Linux 5.1
when the block layer BIO page tracking is enhanced to support multiple
pages.
Without this patch, data corruption can occur. The change to the kernel
block layer in Linux 5.1 changes the way multiple pages are merged to a
single block I/O descriptor, and how contiguous block I/O descriptors
are merged with previous descriptors.
If contiguous block I/O requests cross a page boundary of 4k, defined by
the hv_storvsc driver, the new block merge process can create two pages
of block I/O requests (the latter page with an offset) that refer to the
same physical sector on disk. This page list is then assembled for the
SCSI generic driver.
In the above scenario, when the block I/O request sizes are 512 bytes,
the Azure LIS driver (hv_storvsc module) is not able to correctly parse
the page array from the SCSI generic driver due to this bug in Linux
block layer and creates a potential overflow of offset I/O requests and
corruption of data on disk.
Mitigation of data loss is proven with filesystems with block size 4k.
When block I/O requests are of sizes 4k or multiples of 4k, they are the
page aligned in the memory and are not affected by the block I/O merging
algorithm introduced in Linux 5.1. Most modern file systems use 4k I/O
block size by default, thus mitigating this problem.
We have submitted a patch to Linux mainline kernel to fix this:
- https://patchwork.kernel.org/project/linux-
- block/patch/1623094445-22332-1-git-send-email-lon...@linuxonhyperv.com/
+ https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-
+ block.git/commit/?h=for-next=c9c9762d4d44dcb1b2ba90cfb4122dc11ceebf31
c9c9762d4d44 ("block: return the correct bvec when checking for gaps")
Please include this patch in any supported kernels that are 5.1 or
later.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1931497
Title:
Patch To Fix Bug in the Linux Block Layer Responsible For Merging
BIOs
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1931497/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931497] [NEW] Patch To Fix Bug in the Linux Block Layer Responsible For Merging BIOs
Public bug reported:
There is a bug in the Linux block layer responsible for merging BIOs
that go across the page boundary. This bug was introduced in Linux 5.1
when the block layer BIO page tracking is enhanced to support multiple
pages.
Without this patch, data corruption can occur. The change to the kernel
block layer in Linux 5.1 changes the way multiple pages are merged to a
single block I/O descriptor, and how contiguous block I/O descriptors
are merged with previous descriptors.
If contiguous block I/O requests cross a page boundary of 4k, defined by
the hv_storvsc driver, the new block merge process can create two pages
of block I/O requests (the latter page with an offset) that refer to the
same physical sector on disk. This page list is then assembled for the
SCSI generic driver.
In the above scenario, when the block I/O request sizes are 512 bytes,
the Azure LIS driver (hv_storvsc module) is not able to correctly parse
the page array from the SCSI generic driver due to this bug in Linux
block layer and creates a potential overflow of offset I/O requests and
corruption of data on disk.
Mitigation of data loss is proven with filesystems with block size 4k.
When block I/O requests are of sizes 4k or multiples of 4k, they are the
page aligned in the memory and are not affected by the block I/O merging
algorithm introduced in Linux 5.1. Most modern file systems use 4k I/O
block size by default, thus mitigating this problem.
We have submitted a patch to Linux mainline kernel to fix this:
https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-
block.git/commit/?h=for-next=c9c9762d4d44dcb1b2ba90cfb4122dc11ceebf31
c9c9762d4d44 ("block: return the correct bvec when checking for gaps")
Please include this patch in any supported kernels that are 5.1 or
later.
** Affects: linux-azure (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1931497
Title:
Patch To Fix Bug in the Linux Block Layer Responsible For Merging
BIOs
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1931497/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930609] [NEW] Parameterize number hardware queues
Public bug reported:
Microsoft would like to request inclusion of the following patch in the
5.4 and later kernels:
a81a38cc6dda ("scsi: storvsc: Parameterize number hardware queues")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/scsi/storvsc_drv.c?id=a81a38cc6ddaf128c7ca9e3f21c243f33c97
This patch adds the ability to set the number of hardware queues with
new module parameter, storvsc_max_hw_queues.
This functionality is useful in Microsoft Azure) where decreasing the
number of hardware queues has been shown to improve performance.
** Affects: linux-azure (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1930609
Title:
Parameterize number hardware queues
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1930609/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927493] [NEW] Add a driver for Microsoft Azure Network Adapter (MANA)
Public bug reported: This patch set consists of 5 patches that are now in mainline. The patches add the VF driver for Microsoft Azure Network Adapter (MANA), and also changes the hv_netvsc driver's netvsc/VF binding logic to check both the MAC address and the serial number (this is required by the MANA VF driver). Microsoft would like to request the following 5 patches in all supported releases: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=64ff412ad41fe3a5bf759ff4844dc1382176485c https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net- next.git/commit/?id=ca9c54d2d6a5ab2430c4eda364c77125d62e5e0f https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net- next.git/commit/?id=55cdc26a91ac270887583945aef2bd460a2805f7 https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net- next.git/commit/?id=45b102dd81491e30ac7596b5515856141f99319f https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net- next.git/commit/?id=d90a94680bc0a8069d93282bc5f2966d00b9c4a4 ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927493 Title: Add a driver for Microsoft Azure Network Adapter (MANA) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1927493/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927438] [NEW] Commits To Fix Kdump Failures
Public bug reported: Microsoft received a customer report of failures when trying to take a kdump. This issue was resolved by three small Linux kernel fixes. Microsoft would like to request this following three commits in all supported releases: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/video/fbdev/hyperv_fb.c?id=aa5b7d11c7cb87c266d705b237368985e7171958 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/hv/channel_mgmt.c?id=77db0ec8b7764cb9b09b78066ebfd47b2c0c1909 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/hv/channel_mgmt.c?id=8c2d5e0640e53c14b6240e9bf1e32a2226e6e6ca Patch #1 solves a problem where the “Unable to send packet via vmbus” message is output continuously. But with that problem fixed, the second problem can occur where the kdump kernel panics due to receiving an unexpected VMbus UNLOAD complete message. Patch #2 prevents the UNLOAD complete message from ever occurring in the kdump kernel. But if the UNLOAD complete message does occur at some unexpected time, Patch #3 prevents it from causing a panic. ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927438 Title: Commits To Fix Kdump Failures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1927438/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923888] [NEW] Apply Patch to 4.15 kernels which will resolve a netvsc bug
Public bug reported: A soft lockup is happening to Customers due to a bug in netvsc_poll. Ubuntu 4.15.0-1103 has CONFIG_NET_POLL_CONTROLLER=y in kernel config file, there is a bug in netvsc that may cause CPU lockup with POLL_CONTROLLER. This bug has been fixed by the following patch: commit 2a7f8c3b1d3feedee3aa319ac220cbde3725b5d5 Author: Stephen Hemminger Date: Sat Sep 29 14:52:56 2018 +0200 hv_netvsc: remove ndo_poll_controller This commit is in mainline as of 4.20-rc1. Microsoft would like to request this patch in 4.15 based Azure kernels. ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Apply Patch to 4.15 kernels to resolve netvsc bug + Apply Patch to 4.15 kernels which will resolve a netvsc bug -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923888 Title: Apply Patch to 4.15 kernels which will resolve a netvsc bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1923888/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917958] Re: Latest linux-generic package (kernel 4.15.0-136) doesn't work on HyperV Gen2 VM
It looks like a fix for this issue is already in the 137 kernel. The change log for the -136 update shows a single change related to Hyper-V, and that change broke the ability to open /dev/fb0 and mmap it, which is what the graphic desktop will do. Running in non-graphics mode with just a shell and with ‘ssh’ access works fine, which is why Azure VMs didn’t see the issue. The original change went into the mainline Linux kernel version 5.10, and the change is correct there. It provides a significant performance improvement for the Hyper-V frame buffer. So we wanted it backported to the older releases. Unfortunately, a straight backport breaks in kernel version 5.4 and earlier. The backport needs a minor modification to work correctly 4.15, but we didn’t spot that immediately, mostly because we rarely use graphic desktops. The 4.15.0-137.141 kernel in the queue already, so this issue will be resolved and it only affects 136 - not 135 or 137. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917958 Title: Latest linux-generic package (kernel 4.15.0-136) doesn't work on HyperV Gen2 VM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917958/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914830] [NEW] Mellanox Patches To Prevent Kernel Hang In MLX4
Public bug reported:
We have had customer reports of kernel hangs related to MLX4. Mellanox
has addressed the issue with the following two patches:
fed91613c9dd ("net/mlx4_en: Avoid scheduling restart task if it is already
running")
ba603d9d7b12 ("net/mlx4_en: Handle TX error CQE")
Microsoft would like to request these two commits in all releases
supported on Azure.
** Affects: linux-azure (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1914830
Title:
Mellanox Patches To Prevent Kernel Hang In MLX4
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1914830/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908571] [NEW] Enable boot from NVMe device for all images
Public bug reported: Azure is planning to have VM sizes that boot from NVMe storage, so the NVMe drivers need to be in the kernel image itself, or if the NVMe driver is built as a module, the module needs to be included in the initramfs file. Setting CONFIG_HYPERV=Y, CONFIG_PCI_HYPERV=Y and CONFIG_BLK_DEV_NVME=Y does the former, but the latter is acceptable. Two out of the three configs are set to Y, but we would need CONFIG_PCI_HYPERV set to Y to build the NVMe driver into the kernel. Otherwise, we would need an initrd to all booting from NVMe Microsoft would like to request either of these changes in all the supported releases. ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908571 Title: Enable boot from NVMe device for all images To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1908571/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908569] [NEW] video: hyperv_fb: Fix the cache type when mapping the VRAM
Public bug reported:
We identified a problem that is causing slow logging to the console for
customers.
The following commit resolves this issue as well as other cache relates issues:
325073ae3485 ("video: hyperv_fb: Fix the cache type when mapping the VRAM")
Patch details from it's commit message:
x86 Hyper-V used to essentially always overwrite the effective cache type
of guest memory accesses to WB. This was problematic in cases where there
is a physical device assigned to the VM, since that often requires that
the VM should have control over cache types. Thus, on newer Hyper-V since
2018, Hyper-V always honors the VM's cache type, but unexpectedly Linux VM
users start to complain that Linux VM's VRAM becomes very slow, and it
turns out that Linux VM should not map the VRAM uncacheable by ioremap().
Fix this slowness issue by using ioremap_cache().
With this change, the VRAM on new Hyper-V is as fast as regular RAM, so
it's no longer necessary to use the hacks we added to mitigate the
slowness, i.e. we no longer need to allocate physical memory and use
it to back up the VRAM in Generation-1 VM, and we also no longer need to
allocate physical memory to back up the framebuffer in a Generation-2 VM
and copy the framebuffer to the real VRAM. A further big change will
address these for v5.11.
Microsoft would like to request this patch in all supported releases.
** Affects: linux-azure (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1908569
Title:
video: hyperv_fb: Fix the cache type when mapping the VRAM
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1908569/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902531] Re: [linux-azure] IP forwarding issue in netvsc
Marcelo, will these fixes be avaiable in the last SRU cycle of 2020? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902531 Title: [linux-azure] IP forwarding issue in netvsc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1902531/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904463] [NEW] [linux-azure] Fix hibernation in case interrupts are not re-created
Public bug reported: Microsoft would like to request the following commit in all supported releases that run on Azure: 915cff7f38c5 (“PCI: hv: Fix hibernation in case interrupts are not re-created”) Commit details: pci_restore_msi_state() directly writes the MSI/MSI-X related registers via MMIO. On a physical machine, this works perfectly; for a Linux VM running on a hypervisor, which typically enables IOMMU interrupt remapping, the hypervisor usually should trap and emulate the MMIO accesses in order to re-create the necessary interrupt remapping table entries in the IOMMU, otherwise the interrupts can not work in the VM after hibernation. Hyper-V is different from other hypervisors in that it does not trap and emulate the MMIO accesses, and instead it uses a para-virtualized method, which requires the VM to call hv_compose_msi_msg() to notify the hypervisor of the info that would be passed to the hypervisor in the case of the trap-and-emulate method. This is not an issue to a lot of PCI device drivers, which destroy and re-create the interrupts across hibernation, so hv_compose_msi_msg() is called automatically. However, some PCI device drivers (e.g. the in-tree GPU driver nouveau and the out-of-tree Nvidia proprietary GPU driver) do not destroy and re-create MSI/MSI-X interrupts across hibernation, so hv_pci_resume() has to call hv_compose_msi_msg(), otherwise the PCI device drivers can no longer receive interrupts after the VM resumes from hibernation. Hyper-V is also different in that chip->irq_unmask() may fail in a Linux VM running on Hyper-V (on a physical machine, chip->irq_unmask() can not fail because unmasking an MSI/MSI-X register just means an MMIO write): during hibernation, when a CPU is offlined, the kernel tries to move the interrupt to the remaining CPUs that haven't been offlined yet. In this case, hv_irq_unmask() -> hv_do_hypercall() always fails because the vmbus channel has been closed: here the early "return" in hv_irq_unmask() means the pci_msi_unmask_irq() is not called, i.e. the desc->masked remains "true", so later after hibernation, the MSI interrupt always remains masked, which is incorrect. Refer to cpu_disable_common() -> fixup_irqs() -> irq_migrate_all_off_this_cpu() -> migrate_one_irq(): ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Fix hibernation in case interrupts are not re-created + [linux-azure] Fix hibernation in case interrupts are not re-created -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904463 Title: [linux-azure] Fix hibernation in case interrupts are not re-created To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1904463/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904458] [NEW] [linux-azure] Batch hibernate and resume IO requests
Public bug reported:
Microsoft would like to request the following upstream commit in all
releases supported on Azure. This commit improves a signification delay
in hibernation/resume:
55c4478a8f0e("PM: hibernate: Batch hibernate and resume IO requests")
Details of this commit:
Hibernate and resume process submits individual IO requests for each page of
the data, so use blk_plug to improve the batching of these requests.
Testing this change with hibernate and resumes consistently shows
merging of the IO requests and more than an order of magnitude
improvement in hibernate and resume speed is observed.
One hibernate and resume cycle for 16GB RAM out of 32GB in use takes
around 21 minutes before the change, and 1 minutes after the change on a
system with limited storage IOPS.
** Affects: linux-azure (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1904458
Title:
[linux-azure] Batch hibernate and resume IO requests
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1904458/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902531] Re: [linux-azure] IP forwarding issue in netvsc
If possible, can we also get a test kernel for this bug when avaiable? Folks would like to confirm the two patches fix the issue prior to release of the image. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902531 Title: [linux-azure] IP forwarding issue in netvsc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1902531/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902531] Re: [linux-azure] IP forwarding issue in netvsc
It would be great if we can get the fixes into the next SRU cycle, which is the last one for 2020. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902531 Title: [linux-azure] IP forwarding issue in netvsc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1902531/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902531] [NEW] [linux-azure] IP forwarding issue in netvsc
Public bug reported: We identified an issue with the Linux netvsc driver when used in IP forwarding mode. The problem is that the RSS hash value is not propagated to the outgoing packet, and so such packets go out on channel 0. This produces an imbalance across outgoing channels, and a possible overload on the single host-side CPU that is processing channel 0. The problem does not occur when Accelerated Networking is used because the packets go out through the Mellanox driver. Because it is tied to IP forwarding, the problem is presumably most likely to be visible in a virtual appliance device that is doing network load balancing or other kinds of packet filtering and redirection. We would like to request fixes to this issue in 16.04, 18.04 and 20.04. Two fixes are already in the upstream v5.5+, so they’re already in 5.8.0-1011.11. For 5.4.0-1031.32, the 2 fixes can apply cleanly: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1fac7ca4e63bf935780cc632ccb6ba8de5f22321 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6f3aeb1ba05d41320e6cf9a60f698d9c4e44348e For 5.0.0-1036.38, we need 1 more patch applied first, so the list is: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b441f79532ec13dc82d05c55badc4da1f62a6141 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1fac7ca4e63bf935780cc632ccb6ba8de5f22321 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6f3aeb1ba05d41320e6cf9a60f698d9c4e44348e For 4.15.0-1098.109~16.04.1, the 2 patches can not apply cleanly, so Dexuan backported them here: https://github.com/dcui/linux/commit/4ed58762a56cccfd006e633fac63311176508795 https://github.com/dcui/linux/commit/40ad7849a6365a5a485f05453e10e3541025e25a (The 2 patches are on the branch https://github.com/dcui/linux/commits/decui/ubuntu_16.04/linux-azure/Ubuntu-azure-4.15.0-1098.109_16.04.1) ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902531 Title: [linux-azure] IP forwarding issue in netvsc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1902531/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896784] [NEW] Use Azure host for time keeping in all images
Public bug reported: Microsoft would like to request a change to the time keeping method in the Azure images. We would like to request that an Azure image uses the Azure host for time sync by default. This will require the use of the Chrony package. The Chrony package would need to be installed by default in all images and be configured to use /dev/ptp0 for timekeeping. ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Use Azure host for time keeping + Use Azure host for time keeping in all images -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896784 Title: Use Azure host for time keeping in all images To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1896784/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895527] [NEW] [linux-azure] [SRU] UBUNTU: SAUCE: Drivers: hv: vmbus: Add timeout to vmbus_wait_for_unload
Public bug reported:
This is a request to inclue a patch, submitted to the upstream linux-
hyperv mailing list, in the linux-azure kernels.
Microsoft would like to request this patch in the 16.04 (4.15) and newer
azure kernels. This patch fixes a prior commit, hence the SRU request:
Fixes: 415719160de3 ("Drivers: hv: vmbus: avoid scheduling in interrupt
context in vmbus_initiate_unload()")
The patch specfically performs the following:
"vmbus_wait_for_unload() looks for a CHANNELMSG_UNLOAD_RESPONSE message
coming from Hyper-V. But if the message isn't found for some reason,
the panic path gets hung forever. Add a timeout of 10 seconds to
prevent this."
The requested patch can be found at:
https://lkml.org/lkml/2020/9/13/196
** Affects: linux-azure (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895527
Title:
[linux-azure] [SRU] UBUNTU: SAUCE: Drivers: hv: vmbus: Add timeout to
vmbus_wait_for_unload
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1895527/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883261] Re: [linux-azure] Two Fixes For kdump Over Network
An investigation is currently underway for the issue with the 4.15 kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883261 Title: [linux-azure] Two Fixes For kdump Over Network To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1883261/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883261] Re: [linux-azure] Two Fixes For kdump Over Network
The following link holds test kernels for 5.4, 5.3, and 4.15: https://kernel.ubuntu.com/~kms/azure/lp1883261/ 5.4 was a clean apply, though 5.3 and 4.15 required some changes. Please test to verify the added patches resolve the issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883261 Title: [linux-azure] Two Fixes For kdump Over Network To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1883261/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883261] Re: [linux-azure] Two Fixes For kdump Over Network
I've been testing with the 4.15 kernel and using the following wiki for guidance of using kdump/ssh: https://ubuntu.com/server/docs/kernel-crash-dump I first confirmed I could kdump to local disk. Next, I configured kdump per the wiki to use ssh. However, everytime I cause a crash, the kexec kernel hangs and seems like it cannot reach the network to write the crash file to. Here is the error I see: [ 387.778745] kdump-tools[735]: Starting kdump-tools: [ 387.790249] kdump-tools[763]: Connection closed by 13.77.154.182 port 22 [ 387.794756] kdump-tools[744]: * Network not reachable; will try 15 more times I'm not sure if this is due to a config error on my part or because of the test kernel. Is there any information you could provide to confirm my configration is correct? I'll attach my /etc/default/kexec file. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883261 Title: [linux-azure] Two Fixes For kdump Over Network To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1883261/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891222] Re: Only notify Hyper-V for die events that are oops
The requested commit has now landed upstream: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/hv?h=v5.9-rc1=608a973bd52ef1705941b18f55e39655fcfe9cdb -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891222 Title: Only notify Hyper-V for die events that are oops To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1891222/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891222] [NEW] Only notify Hyper-V for die events that are oops
Public bug reported:
Currently, Hyper-V may be notified of a panic for any die event.
However, this results in false panic notifications for various user space traps
that are die events.
The following commit fixes this by ignoring die events that is not an
oops:
608a973bd52e ("Drivers: hv: vmbus: Only notify Hyper-V for die events
that are oops")
We would like to request this commit in all releases supported on Azure
and Hyper-V.
** Affects: linux-azure (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891222
Title:
Only notify Hyper-V for die events that are oops
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1891222/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1883261
Title:
[linux-azure] Two Fixes For kdump Over Network
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1883261/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1882268
Title:
[linux-azure] Request for two CIFS commits in 16.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1882268/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879559 Title: net/bpfilter: remove superfluous testing message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879559/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881787 Title: High rate of packet loss upgrading to kernel 5.3 and later. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1881787/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881662
Title:
Add Description To Hyper-V Modules
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1881662/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880975
Title:
Request to include two NUMA related commits in Azure kernels
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1880975/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856375 Title: [linux-azure] Request to autoload mlx4/mlx5 modules for DPDK To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1856375/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880032 Title: [linux-azure] Enable Hibernation on The 18.04 and 20.04 5.4 Kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1880032/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877647
Title:
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
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877647 Title: 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878492 Title: Partition naming regression with linux-azure 5.3 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1878492/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878075 Title: Request to blacklist floppy for images on Azure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1878075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877654 Title: Add XDP support to hv_netvsc driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1877654/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877647
Title:
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
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876770
Title:
speed for CX4 VF showing as unknown in ethtool output
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1876770/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875467
Title:
Enable Invariant TSC Support
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1875467/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875456
Title:
Azure diagnostic/serviceability improvement
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1875456/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874503 Title: Mellanox Check For Write Combining Support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1874503/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870189
Title:
initramfs does not get loaded
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1870189/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869996 Title: Hibernation can NOT work due to incorrect RESUME= To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1869996/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867220] [NEW] Assignment of VDEV Somtimes Fails using Intel QAT
Public bug reported: The QAT is a PCIe device which supports SR-IOV. It is used to accelerate the crypto and compression operations by hardware. There is additional info for this hardware on the Intel website: https://www.intel.com/content/www/us/en/products/docs/network-io/ethernet/10-25-40-gigabit-adapters/quickassist-adapter-for-servers.html https://01.org/intel-quick-assist-technology On Ubuntu, when the QAT device is enabled with SR-IOV, one device will have 16 VFs. When we assign the VDEV to Linux VM, sometimes, it will fail but sometimes it will not. This issue was debugged and is resolved by applying three patches and removing some buggy code that was added as SAUCE. The following three patches are needed: f73f8a504e27 PCI: hv: Use bytes 4 and 5 from instance ID as the PCI domain numbers be700103efd1 PCI: hv: Detect and fix Hyper-V PCI domain number collision 6ae91579061c PCI: hv: Add __aligned(8) to struct retarget_msi_interrupt Also, revert the patch Revert "PCI: hv: Make sure the bus domain is really unique", i.e. the line "if (list_empty(>children)) hbus->sysdata.domain = desc->ser" in new_pcichild_device() should be completely removed. The patch “UBUNTU: SAUCE: pci-hyperv: Use only 16 bit integer for PCI domai” is also pointless now. ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Assignment of VDEV Sometimes Fails + Assignment of VDEV Somtimes Fails using Intel QAT -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867220 Title: Assignment of VDEV Somtimes Fails using Intel QAT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1867220/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866407 Title: GPU Driver extension issue (NVIDIA) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1866407/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866407 Title: GPU Driver extension issue (NVIDIA) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1866407/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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, , 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, , 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 *dentry,
[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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864233
Title:
Commits to resolve high network latency
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1864233/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863951 Title: [linux-azure] Missing user mode io driver - uio_pci_generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1863951/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860603
Title:
[linux-azure] VMs crashing due to 503 SMB errors
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1860603/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856605 Title: [linux-azure] Ubuntu 16.04 + INFINIBAND-OPEN-MPI-2VM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1856605/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856605 Title: [linux-azure] Ubuntu 16.04 + INFINIBAND-OPEN-MPI-2VM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1856605/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856375 Title: [linux-azure] Request to autoload mlx4/mlx5 modules for DPDK To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1856375/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1855461
Title:
[linux-azure] SAUCE patch to "Fix skb protocol value in
tpacket_fill_skb()"
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1855461/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855461 Title: [linux-azure] SAUCE patch to "Fix skb protocol value in tpacket_fill_skb()" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1855461/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853014 Title: GPU device disable/enable test failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1853014/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853014 Title: GPU device disable/enable test failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1853014/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853014 Title: GPU device disable/enable test failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1853014/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853014 Title: GPU device disable/enable test failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1853014/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853014 Title: GPU device disable/enable test failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1853014/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853014 Title: GPU device disable/enable test failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1853014/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848739 Title: [linux-azure] Patch to prevent possible data corruption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1848739/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850185 Title: [linux-azure] 19.04 regression of KDUMP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1850185/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850185 Title: [linux-azure] 19.04 regression of KDUMP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1850185/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849495
Title:
[linux-azure] Add ability to change scsi queue depth
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1849495/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848739
Title:
[linux-azure] Patch to prevent possible data corruption
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1848739/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847139 Title: [linux-azure] Request of mainline commit f73f8a504e27 in azure 16.04 and 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1847139/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
