[Group.of.nepali.translators] [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 नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1968902
Title:
ARM64_SW_TTBR0_PAN Should Be Enabled For Oracle Kernels
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Focal:
In Progress
Status in linux source package in Impish:
In Progress
Bug description:
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968902/+subscriptions
___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [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 नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1968902
Title:
ARM64_SW_TTBR0_PAN Should Be Enabled For Oracle Kernels
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
In Progress
Status in linux source package in Bionic:
In Progress
Status in linux source package in Focal:
In Progress
Status in linux source package in Impish:
New
Bug description:
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968902/+subscriptions
___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1955264] Re: xenial/linux-gcp: 4.15.0-1115.129~16.04.1 -proposed tracker
** Tags removed: regression-testing-passed ** Tags added: boot-testing-passed ** Changed in: kernel-sru-workflow/boot-testing Status: Incomplete => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1955264 Title: xenial/linux-gcp: 4.15.0-1115.129~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow boot-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow sru-review series: Fix Released Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true built: route-entry: 1 delta: promote-to-proposed: - signed - main - meta sru-review: - meta - main - signed issue: KSRU-801 kernel-stable-master-bug: 1955265 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Ready for Promote to Proposed phase-changed: Wednesday, 19. January 2022 19:23 UTC reason: promote-to-proposed: Pending -- ready for review synthetic: :promote-to-as-proposed: Invalid trackers: xenial/linux-gcp/gcp-kernel: bug 1955262 xenial/linux-gcp/gke-kernel: bug 1955263 variant: debs versions: main: 4.15.0-1115.129~16.04.1 meta: 4.15.0.1115.116 signed: 4.15.0-1115.129~16.04.1 source: 4.15.0-1115.129~16.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1955264/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1955264] Re: xenial/linux-gcp: 4.15.0-1115.129~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/boot-testing Status: Incomplete => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1955264 Title: xenial/linux-gcp: 4.15.0-1115.129~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow boot-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow sru-review series: Fix Released Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true built: route-entry: 1 delta: sru-review: - meta - main - signed issue: KSRU-801 kernel-stable-master-bug: 1955265 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Testing phase-changed: Monday, 17. January 2022 19:46 UTC reason: boot-testing: Stalled -- testing FAILED synthetic: :promote-to-as-proposed: Invalid trackers: xenial/linux-gcp/gcp-kernel: bug 1955262 xenial/linux-gcp/gke-kernel: bug 1955263 variant: debs versions: main: 4.15.0-1115.129~16.04.1 meta: 4.15.0.1115.116 signed: 4.15.0-1115.129~16.04.1 source: 4.15.0-1115.129~16.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1955264/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1955264] Re: xenial/linux-gcp: 4.15.0-1115.129~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/boot-testing Status: Incomplete => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1955264 Title: xenial/linux-gcp: 4.15.0-1115.129~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow boot-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow sru-review series: Fix Released Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true built: route-entry: 1 delta: sru-review: - meta - main - signed issue: KSRU-801 kernel-stable-master-bug: 1955265 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Testing phase-changed: Monday, 17. January 2022 19:46 UTC reason: boot-testing: Stalled -- testing FAILED synthetic: :promote-to-as-proposed: Invalid trackers: xenial/linux-gcp/gcp-kernel: bug 1955262 xenial/linux-gcp/gke-kernel: bug 1955263 variant: debs versions: main: 4.15.0-1115.129~16.04.1 meta: 4.15.0.1115.116 signed: 4.15.0-1115.129~16.04.1 source: 4.15.0-1115.129~16.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1955264/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1955264] Re: xenial/linux-gcp: 4.15.0-1115.129~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/boot-testing Status: Incomplete => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1955264 Title: xenial/linux-gcp: 4.15.0-1115.129~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow boot-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow sru-review series: Fix Released Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true built: route-entry: 1 delta: sru-review: - meta - main - signed issue: KSRU-801 kernel-stable-master-bug: 1955265 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Testing phase-changed: Monday, 17. January 2022 19:46 UTC reason: boot-testing: Stalled -- testing FAILED synthetic: :promote-to-as-proposed: Invalid trackers: xenial/linux-gcp/gcp-kernel: bug 1955262 xenial/linux-gcp/gke-kernel: bug 1955263 variant: debs versions: main: 4.15.0-1115.129~16.04.1 meta: 4.15.0.1115.116 signed: 4.15.0-1115.129~16.04.1 source: 4.15.0-1115.129~16.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1955264/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1955264] Re: xenial/linux-gcp: 4.15.0-1115.129~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/boot-testing Status: Incomplete => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1955264 Title: xenial/linux-gcp: 4.15.0-1115.129~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow boot-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow sru-review series: Fix Released Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true built: route-entry: 1 delta: sru-review: - meta - main - signed issue: KSRU-801 kernel-stable-master-bug: 1955265 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Testing phase-changed: Monday, 17. January 2022 19:46 UTC reason: boot-testing: Stalled -- testing FAILED synthetic: :promote-to-as-proposed: Invalid trackers: xenial/linux-gcp/gcp-kernel: bug 1955262 xenial/linux-gcp/gke-kernel: bug 1955263 variant: debs versions: main: 4.15.0-1115.129~16.04.1 meta: 4.15.0.1115.116 signed: 4.15.0-1115.129~16.04.1 source: 4.15.0-1115.129~16.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1955264/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1955264] Re: xenial/linux-gcp: 4.15.0-1115.129~16.04.1 -proposed tracker
Confirmed with fginther the n2d.* instances types will boot test fail, which is expected. ** Tags added: regression-testing-passed ** Changed in: kernel-sru-workflow/boot-testing Status: Incomplete => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1955264 Title: xenial/linux-gcp: 4.15.0-1115.129~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow boot-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow sru-review series: Fix Released Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true built: route-entry: 1 delta: sru-review: - meta - main - signed issue: KSRU-801 kernel-stable-master-bug: 1955265 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Testing phase-changed: Monday, 17. January 2022 19:46 UTC reason: boot-testing: Stalled -- testing FAILED synthetic: :promote-to-as-proposed: Invalid trackers: xenial/linux-gcp/gcp-kernel: bug 1955262 xenial/linux-gcp/gke-kernel: bug 1955263 variant: debs versions: main: 4.15.0-1115.129~16.04.1 meta: 4.15.0.1115.116 signed: 4.15.0-1115.129~16.04.1 source: 4.15.0-1115.129~16.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1955264/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1953655] Re: xenial/linux-gcp: 4.15.0-1114.128~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Opinion => Incomplete -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1953655 Title: xenial/linux-gcp: 4.15.0-1114.128~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow boot-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Incomplete Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow sru-review series: Fix Released Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true built: route-entry: 1 delta: promote-to-proposed: - signed - meta - main sru-review: - signed - main - meta issue: KSRU-651 kernel-stable-master-bug: 1953656 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Promote to Proposed phase-changed: Monday, 13. December 2021 21:26 UTC reason: promote-to-proposed: Pending -- packages copying to Signing (signed:P) regression-testing: Stalled -- testing FAILED synthetic: :promote-to-as-proposed: Invalid trackers: xenial/linux-gcp/gcp-kernel: bug 1953653 xenial/linux-gcp/gke-kernel: bug 1953654 variant: debs versions: main: 4.15.0-1114.128~16.04.1 meta: 4.15.0.1114.115 signed: 4.15.0-1114.128~16.04.1 source: 4.15.0-1114.128~16.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1953655/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1953655] Re: xenial/linux-gcp: 4.15.0-1114.128~16.04.1 -proposed tracker
** Tags removed: regression-testing-passed ** Changed in: kernel-sru-workflow/regression-testing Status: Fix Released => In Progress -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1953655 Title: xenial/linux-gcp: 4.15.0-1114.128~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow boot-testing series: Triaged Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow sru-review series: Fix Released Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true built: route-entry: 1 delta: sru-review: - signed - main - meta issue: KSRU-651 kernel-stable-master-bug: 1953656 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Testing phase-changed: Monday, 13. December 2021 20:47 UTC reason: boot-testing: Ongoing -- testing in progress synthetic: :promote-to-as-proposed: Invalid trackers: xenial/linux-gcp/gcp-kernel: bug 1953653 xenial/linux-gcp/gke-kernel: bug 1953654 variant: debs versions: main: 4.15.0-1114.128~16.04.1 meta: 4.15.0.1114.115 signed: 4.15.0-1114.128~16.04.1 source: 4.15.0-1114.128~16.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1953655/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1953655] Re: xenial/linux-gcp: 4.15.0-1114.128~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: New => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1953655 Title: xenial/linux-gcp: 4.15.0-1114.128~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow boot-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Committed Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Committed Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow sru-review series: Fix Released Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- built: route-entry: 1 delta: sru-review: - signed - main - meta issue: KSRU-651 kernel-stable-master-bug: 1953656 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Packaging phase-changed: Friday, 10. December 2021 19:26 UTC reason: :prepare-packages: Pending -- building in ppa (main:P signed:D) prepare-package: Ongoing -- main package not yet fully built prepare-package-signed: Ongoing -- signed package not yet fully built sru-review: Pending -- ready for review synthetic: :promote-to-as-proposed: Invalid trackers: xenial/linux-gcp/gcp-kernel: bug 1953653 xenial/linux-gcp/gke-kernel: bug 1953654 variant: debs versions: main: 4.15.0-1114.128~16.04.1 meta: 4.15.0.1114.115 signed: 4.15.0-1114.128~16.04.1 source: 4.15.0-1114.128~16.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1953655/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1952336] Re: xenial/linux-gcp: 4.15.0-1113.127~16.04.1 -proposed tracker
** Summary changed: - xenial/linux-gcp: 4.15.0-1112.126~16.04.2 -proposed tracker + xenial/linux-gcp: 4.15.0-1113.127~16.04.1 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Released => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Khaled El Mously (kmously) => Joseph Salisbury (jsalisbury) -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1952336 Title: xenial/linux-gcp: 4.15.0-1113.127~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow boot-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow sru-review series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- built: route-entry: 1 issue: KSRU-570 kernel-stable-master-bug: 1952337 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Packaging phase-changed: Tuesday, 07. December 2021 02:13 UTC reason: :prepare-packages: 'Ongoing -b Being cranked by: jsalisbury' prepare-package: Pending -- tag not published and package not uploaded prepare-package-meta: Pending -- tag not published and package not uploaded prepare-package-signed: Pending -- tag not published and package not uploaded synthetic: :promote-to-as-proposed: Invalid trackers: xenial/linux-gcp/gcp-kernel: bug 1952334 xenial/linux-gcp/gke-kernel: bug 1952335 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1952336/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1553811] Re: Thinkpad T460: Trackpoint mouse buttons instantly generate "release" event on press
** Changed in: linux-lts-utopic (Ubuntu Trusty) Status: In Progress => Fix Released ** Changed in: linux-lts-vivid (Ubuntu) Status: In Progress => Fix Released ** Changed in: linux-lts-utopic (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1553811 Title: Thinkpad T460: Trackpoint mouse buttons instantly generate "release" event on press Status in linux package in Ubuntu: Fix Released Status in linux-lts-utopic package in Ubuntu: Fix Released Status in linux-lts-vivid package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Released Status in linux-lts-utopic source package in Trusty: Fix Released Status in linux-lts-vivid source package in Trusty: Fix Released Status in linux source package in Wily: Fix Released Status in linux source package in Xenial: Fix Released Bug description: When using the trackpoint mouse buttons on the laptop, when any of the buttons are pressed a release event immediately follows, even if the mouse button is being held down. This prevents moving of windows, typical drag & drop operations, selection etc with the mouse. Example output from xev for button 1: ButtonPress event, serial 40, synthetic NO, window 0x7e1, root 0xb6, subw 0x0, time 1097221, (116,59), root:(116,142), state 0x0, button 1, same_screen YES ButtonRelease event, serial 40, synthetic NO, window 0x7e1, root 0xb6, subw 0x0, time 1097229, (116,59), root:(116,142), state 0x100, button 1, same_screen YES Button 2: ButtonPress event, serial 40, synthetic NO, window 0x7e1, root 0xb6, subw 0x0, time 1100941, (116,59), root:(116,142), state 0x0, button 2, same_screen YES ButtonRelease event, serial 40, synthetic NO, window 0x7e1, root 0xb6, subw 0x0, time 1100941, (116,59), root:(116,142), state 0x200, button 2, same_screen YES Button 3: ButtonPress event, serial 40, synthetic NO, window 0x7e1, root 0xb6, subw 0x0, time 1098467, (116,59), root:(116,142), state 0x0, button 3, same_screen YES ButtonRelease event, serial 40, synthetic NO, window 0x7e1, root 0xb6, subw 0x0, time 1098477, (116,59), root:(116,142), state 0x400, button 3, same_screen YES Possibly relevant output from journal: kernel: thinkpad_acpi: ThinkPad ACPI Extras v0.25 kernel: thinkpad_acpi: http://ibm-acpi.sf.net/ kernel: thinkpad_acpi: ThinkPad BIOS R06ET33W (1.07 ), EC unknown kernel: thinkpad_acpi: Lenovo ThinkPad T460, model 20FNCTO1WW kernel: thinkpad_acpi: detected a 8-level brightness capable ThinkPad kernel: thinkpad_acpi: unknown version of the HKEY interface: 0x200 kernel: thinkpad_acpi: please report this to ibm-acpi-de...@lists.sourceforge.net kernel: thinkpad_acpi: radio switch found; radios are enabled kernel: thinkpad_acpi: This ThinkPad has standard ACPI backlight brightness control, supported by the ACPI video driver kernel: thinkpad_acpi: Disabling thinkpad-acpi brightness events by default... kernel: thinkpad_acpi: rfkill switch tpacpi_bluetooth_sw: radio is unblocked kernel: thinkpad_acpi: Standard ACPI backlight interface available, not loading native one kernel: input: ThinkPad Extra Buttons as /devices/platform/thinkpad_acpi/input/input7 sensors[1000]: thinkpad-isa- kernel: thinkpad_acpi: EC reports that Thermal Table has changed kernel: thinkpad_acpi: acpi_evalf(GTRW, dd, ...) failed: AE_NOT_FOUND kernel: thinkpad_acpi: Cannot read adaptive keyboard mode. kernel: thinkpad_acpi: acpi_evalf(STRW, vd, ...) failed: AE_NOT_FOUND kernel: thinkpad_acpi: Cannot set adaptive keyboard mode. kernel: thinkpad_acpi: EC reports that Thermal Table has changed ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-10-generic 4.4.0-10.25 ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3 Uname: Linux 4.4.0-10-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: KDE Date: Sun Mar 6 12:38:59 2016 HibernationDevice: RESUME=UUID=04e04e17-3976-4daa-a1dd-2dd369aee83d InstallationDate: Installed on 2015-09-21 (166 days ago) InstallationMedia: It Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20FNCTO1WW ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-10-generic root=/dev/mapper/it--vg-root ro quiet intel_pstate=no_hwp RelatedPackageVersions: linux-restricted-modules-4.4.0-10-generic N/A linux-backports-modules-4.4.0-10-generic N/A linux-firmware1.156 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-02-24 (10 days ago) dmi.bios.date: 01/05/2016
[Group.of.nepali.translators] [Bug 1619766] Re: Backport E3 Skylake Support in ie31200_edac to Xenial
** Changed in: linux (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1619766 Title: Backport E3 Skylake Support in ie31200_edac to Xenial Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Bug description: Skylake E3 Support was added to ie31200_edac with the following commit: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/edac/ie31200_edac.c?id=953dee9bbd245f5515173126b9cc8b1a2c340797 Could we get this support backported to Xenial? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1619766/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1613787] Re: xfrm: ipsec crash when updating spd thresholds
** Changed in: linux (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1613787 Title: xfrm: ipsec crash when updating spd thresholds Status in linux package in Ubuntu: Fix Released Status in linux source package in Vivid: Fix Released Status in linux source package in Xenial: Fix Released Bug description: Fixed upstream by this commit (only in IPsec tree for now): https://git.kernel.org/cgit/linux/kernel/git/klassert/ipsec.git/commit/?id=6916fb3b10b3cbe3b1f9f5b680675f53e4e299eb http://patchwork.ozlabs.org/patch/654026/ To update the thresholds: 'ip xfrm policy set hthresh4 24 32' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1613787/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1633404] Re: audit: prevent a new auditd to stop an old auditd still alive
** Changed in: linux (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1633404 Title: audit: prevent a new auditd to stop an old auditd still alive Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Released Status in linux source package in Xenial: Fix Released Bug description: The following upstream patch (v4.6) has fixed this problem: audit: stop an old auditd being starved out by a new auditd http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=133e1e5acd4a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633404/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1634545] Re: ipv6: connected routes are missing after a down/up cycle on the loopback
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1634545
Title:
ipv6: connected routes are missing after a down/up cycle on the
loopback
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Trusty:
Fix Released
Status in linux source package in Vivid:
Fix Released
Status in linux source package in Xenial:
Fix Released
Status in linux source package in Yakkety:
Fix Released
Bug description:
This upstream patch is missing:
http://git.kernel.org/cgit/linux/kernel/git/davem/net.git/commit/?id=a220445f9f4382c36a53d8ef3e08165fa27f7e2c
ipv6: correctly add local routes when lo goes up
The goal of the patch is to fix this scenario:
ip link add dummy1 type dummy
ip link set dummy1 up
ip link set lo down ; ip link set lo up
After that sequence, the local route to the link layer address of dummy1 is
not there anymore.
When the loopback is set down, all local routes are deleted by
addrconf_ifdown()/rt6_ifdown(). At this time, the rt6_info entry still
exists, because the corresponding idev has a reference on it. After the rcu
grace period, dst_rcu_free() is called, and thus ___dst_free(), which will
set obsolete to DST_OBSOLETE_DEAD.
In this case, init_loopback() is called before dst_rcu_free(), thus
obsolete is still sets to something <= 0. So, the function doesn't add the
route again. To avoid that race, let's check the rt6 refcnt instead.
Fixes: 25fb6ca4ed9c ("net IPv6 : Fix broken IPv6 routing table after loopback
down-up")
Fixes: a881ae1f625c ("ipv6: don't call addrconf_dst_alloc again when enable
lo")
Fixes: 33d99113b110 ("ipv6: reallocate addrconf router for ipv6 address when
lo device up")
Reported-by: Francesco Santoro
Reported-by: Samuel Gauthier
CC: Balakumaran Kannan
CC: Maruthi Thotad
CC: Sabrina Dubroca
CC: Hannes Frederic Sowa
CC: Weilong Chen
CC: Gao feng
Signed-off-by: Nicolas Dichtel
Signed-off-by: David S. Miller
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1634545/+subscriptions
___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1683976] Re: Please backport fix to reference leak in cgroup blkio throttle
** Changed in: linux (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1683976 Title: Please backport fix to reference leak in cgroup blkio throttle Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Released Status in linux source package in Xenial: Fix Released Bug description: This is fixed in Linux 4.5 https://github.com/torvalds/linux/commit/39a169b62b415390398291080dafe63aec751e0a Basically the module reference will leak whenever you write to /sys/fs/cgroup/blkio/blkio.throttle.* $ uname -a Linux david-kvm 4.4.0-72-generic #93-Ubuntu SMP Fri Mar 31 14:07:41 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux $ lsmod | grep ^zfs zfs 2813952 1 $ sudo sh -c 'i=100; while [ $i -gt 0 ]; do echo "230:0 1024" > /sys/fs/cgroup/blkio/blkio.throttle.read_bps_device; i=$(($i - 1)); done' $ lsmod | grep ^zfs zfs 2813952 101 This patch should be applied to all kernel < 4.5 Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683976/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1667323] Re: Backlight control does not work and there are no entries in /sys/class/backlight
** Changed in: linux (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1667323 Title: Backlight control does not work and there are no entries in /sys/class/backlight Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Bug description: It was working fine until today. The folder /sys/class/backlight/ use to have "acpi_video0/brightness", but now is empty. I am using Nvidia Proprietary driver 340.101 (proprietary, tested). The problem persists even with the 304 driver. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-64-generic 4.4.0-64.85 ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44 Uname: Linux 4.4.0-64-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: desgua 2028 F pulseaudio /dev/snd/controlC0: desgua 2028 F pulseaudio CurrentDesktop: Unity Date: Thu Feb 23 11:31:18 2017 HibernationDevice: RESUME=UUID=f23a6347-9483-460e-aa29-cbc47850f890 InstallationDate: Installed on 2014-05-01 (1028 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) Lsusb: Bus 002 Device 003: ID 064e:a127 Suyin Corp. Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-64-generic root=/dev/mapper/ubuntu--vg-root ro RelatedPackageVersions: linux-restricted-modules-4.4.0-64-generic N/A linux-backports-modules-4.4.0-64-generic N/A linux-firmware1.157.8 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-08-17 (189 days ago) dmi.bios.date: 12/03/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.13 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3659 dmi.board.vendor: Hewlett-Packard dmi.board.version: 32.23 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.13:bd12/03/2009:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr049D212412102:rvnHewlett-Packard:rn3659:rvr32.23:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.name: HP Pavilion dv6 Notebook PC dmi.product.version: 049D212412102 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667323/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1745130] Re: Support rfkill-any led trigger for Fujitsu u727
** Changed in: linux (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1745130 Title: Support rfkill-any led trigger for Fujitsu u727 Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Bug description: == SRU Justification == This bug was reported against a Fujitsu u7x7 laptop series based on Skylake hardware. It has a single rfkill button and a single LED for wlan and bluetooth. Both drivers currently provide a single rfkill trigger, so the led could just be assigned to one. This was resolved by mainline commit 9b8e34e211, which added a "rfkill-any" led trigger to correctly handle the led with multiple rfkill devices. That was added by one of the fujitsu-laptop maintainers and the driver sets it as the default trigger. Commit 9b8e34e211b1 is in mainline as of 4.11-rc1. == Fix == commit 9b8e34e211b15af429b72388a8f2b3b1823d172e Author: Michał Kępień Date: Fri Jan 6 07:07:47 2017 +0100 rfkill: Add rfkill-any LED trigger == Regression Potential == Medium. This commit affects all arches, but it has been in mainline since 4.11-rc1 with no reported issues. == Test Case == A test kernel was built with this patch and tested by the original bug reporter. The bug reporter states the test kernel resolved the bug. == Original Bug Description == I got new HW from our supplier, which is the Fujitsu u7x7 laptop series based on Skylake hardware. It has a single rfkill button and a single LED for wlan and bluetooth. Both device driver currently provide a single rfkill trigger, so the led could just be assigned to one. As a result the upstream kernel got a new "rfkill-any" led trigger to correctly handle the led with multiple rfkill devices. That was added by one of the fujitsu-laptop maintainers and the driver sets it as the default trigger. commit 9b8e34e211b15af429b72388a8f2b3b1823d172e Author: Michał Kępień Date: Fri Jan 6 07:07:47 2017 +0100 rfkill: Add rfkill-any LED trigger Normally I would simply patch the affected modules using DKMS, like the i915_bpo driver, fujitsu-laptop and snd_hda_codec_realtek to support the HW without messing with the kernel packages. I'm currently waiting for some reviews, like https://www.spinics.net/lists/platform-driver-x86/msg14606.html But the rfkill support is compiled in, so I can't patch it using DKMS. So my first proposed fix would be to include a backport of this patch. Alternatively rfkill can be compiled as a module, so I can patch it and provide an updated module. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-4.4.0-111-generic 4.4.0-111.134~14.04.1 ProcVersionSignature: Ubuntu 4.4.0-111.134~14.04.1-generic 4.4.98 Uname: Linux 4.4.0-111-generic i686 ApportVersion: 2.14.1-0ubuntu3.27 Architecture: i386 Date: Wed Jan 24 10:48:28 2018 SourcePackage: linux-lts-xenial UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745130/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1713884] Re: [CIFS] Fix maximum SMB2 header size
** Changed in: linux (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1713884 Title: [CIFS] Fix maximum SMB2 header size Status in linux package in Ubuntu: Fix Released Status in linux source package in Vivid: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux source package in Zesty: Fix Released Status in linux source package in Artful: Won't Fix Bug description: Currently the maximum size of SMB2/3 header is set incorrectly which leads to hanging of directory listing operations on encrypted SMB3 connections. Fix this by setting the maximum size to 170 bytes that is calculated as RFC1002 length field size (4) + transform header size (52) + SMB2 header size (64) + create response size (56). https://git.kernel.org/pub/scm/linux/kernel/git/next/linux- next.git/commit/?id=47690ab81f4f29b12bbb0676d3579e61ab4d84de This applies across the board 3.16, 4.4, 4.10, artful, and azure. Microsoft would be happy to help test. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1713884/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1735977] Re: Using asymmetric key for IMA appraisal crashes the system in Ubuntu 16.04
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1735977
Title:
Using asymmetric key for IMA appraisal crashes the system in Ubuntu
16.04
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Fix Released
Bug description:
== SRU Justification ==
The bug reporter was trying to enable IMA appraisal with signatures for
executable
files on Xenial. However, when enabling IMA appriasl the system would crash
and generate a trace.
This bug is happening because the following commit was applied to Xenial in
bug 1569924:
db6c43bd2132 ("crypto: KEYS: convert public key and digsig asym to the
akcipher api")
However, the following commit is also required or this bug happens:
eb5798f2e28f ("integrity: convert digsig to akcipher api")
== Fix ==
commit eb5798f2e28f3b43091cecc71c84c3f6fb35c7de
Author: Tadeusz Struk
Date: Tue Feb 2 10:08:58 2016 -0800
integrity: convert digsig to akcipher api
== Regression Potential ==
The requested commit is requred to fix an existing regression caused by bug
1569924.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
== Original Bug Description ==
I'm trying to enable IMA appraisal with signatures for executable files on
xenial with Linux 4.4. I took the following steps:
* Downloaded ubuntu-xenial kernel sources
* Run fakeroot debian/rules editconfigs to set CONFIG_SYSTEM_TRUSTED_KEYS to
my key
* Run fakeroot debian/rules binary-headers binary-generic binary-perarch to
build the kernel deb packaes
* Installed the kernel
* Signed the filesystem with my key using 'evmctl sing'
* Enabled IMA policy so that it will include the following line
appraise fowner=0 appraise_type=imasig
* From this point invocation of a signed binary cases a kernel BUG():
[ 1395.036910] kernel BUG at
/home/rapoport/git/ubuntu-xenial/crypto/asymmetric_keys/public_key.c:80!
[ 1395.038963] invalid opcode: [#1] SMP
[ 1395.039973] Modules linked in: isofs ppdev kvm_intel kvm irqbypass joydev
input_leds serio_raw parport_pc parport ib_iser rdma_cm iw_cm ib_cm ib_sa
ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi
autofs4 btrfs 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 aesni_intel aes_x86_64 lrw gf128mul
glue_helper ablk_helper psmouse cryptd floppy
[ 1395.050761] CPU: 6 PID: 31586 Comm: bash Not tainted 4.4.0-101-generic #124
[ 1395.051909] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS
Ubuntu-1.8.2-1ubuntu1 04/01/2014
[ 1395.053510] task: 8800bae9c600 ti: 88042c52c000 task.ti:
88042c52c000
[ 1395.054763] RIP: 0010:[] []
public_key_verify_signature+0x46/0x50
[ 1395.056406] RSP: 0018:88042c52fa98 EFLAGS: 00010246
[ 1395.057307] RAX: 813bdb80 RBX: fff4 RCX:
0001
[ 1395.058518] RDX: 81ea73c0 RSI: 88042c52fac8 RDI:
88042a107c10
[ 1395.059709] RBP: 88042c52faa0 R08: 88042a849100 R09:
0007
[ 1395.061109] R10: 88042a0f9d00 R11: 88042c52fb07 R12:
0080
[ 1395.062289] R13: 88042abd9a80 R14: 0014 R15:
88042a849ac4
[ 1395.063404] FS: 7f5e21958700() GS:88043fd8()
knlGS:
[ 1395.064771] CS: 0010 DS: ES: CR0: 80050033
[ 1395.065809] CR2: 7f5e20f5c3cc CR3: 00042cabc000 CR4:
000406e0
[ 1395.067058] Stack:
[ 1395.067540] 813bdb95 88042c52fab0 813bdaec
88042c52fb38
[ 1395.068964] 813a759e 88042c52fac8
[ 1395.070417] 88042a849ac4 02000114 88042a849100
[ 1395.071973] Call Trace:
[ 1395.072510] [] ? public_key_verify_signature_2+0x15/0x20
[ 1395.073605] [] verify_signature+0x3c/0x50
[ 1395.074526] [] asymmetric_verify+0x17e/0x2a0
[ 1395.075475] [] integrity_digsig_verify+0x70/0x110
[ 1395.076481] [] ima_appraise_measurement+0x244/0x420
[ 1395.077518] [] process_measurement+0x3fa/0x480
[ 1395.078479] [] ima_file_check+0x18/0x20
[ 1395.079381] [] path_openat+0x1f3/0x1330
[ 1395.080274] [] ? __slab_free+0xcb/0x2c0
[ 1395.081165] [] do_filp_open+0x91/0x100
[ 1395.082050] [] ? apparmor_cred_prepare+0x2f/0x50
[ 1395.083046] [] ? security_prepare_creds+0x43/0x60
[ 1395.084056] [] do_open_execat+0x78/0x1d0
[ 1395.084952] [] do_execveat_common.isra.33+0x240/0x760
[ 1395.086016] [] SyS_execve+0x3a/0x50
[
[Group.of.nepali.translators] [Bug 1738219] Re: the kernel is blackholing IPv6 packets to linkdown nexthops
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Confirmed
** Changed in: linux (Ubuntu Bionic)
Assignee: Joseph Salisbury (jsalisbury) => (unassigned)
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1738219
Title:
the kernel is blackholing IPv6 packets to linkdown nexthops
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Fix Released
Status in linux source package in Zesty:
Won't Fix
Status in linux source package in Artful:
Fix Released
Status in linux source package in Bionic:
Confirmed
Bug description:
== SRU Justification ==
When the 'ignore_routes_with_linkdown' sysctl is set, we should not
consider linkdown nexthops during route lookup.
While the code correctly verifies that the initially selected route
('match') has a carrier, it does not perform the same check in the
subsequent multipath selection, resulting in a potential packet loss.
In case the chosen route does not have a carrier and the sysctl is set,
choose the initially selected route.
This is a regression introduced by commit 35103d11173b in 4.3-rc1. Commit
bbfcd7763 resolves this regression and is mainline as of 4.15-rc1.
== Fix ==
commit bbfcd77631573ac4a9f57eb6169e04256a111bc1
Author: Ido Schimmel
Date: Tue Nov 21 09:50:12 2017 +0200
ipv6: Do not consider linkdown nexthops during multipath
== Regression Potential ==
This fix is specific to ipv6 and fixes a current regression.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738219/+subscriptions
___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1744078] Re: linux < 4.8: x-netns vti is broken
** Changed in: linux (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1744078 Title: linux < 4.8: x-netns vti is broken Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Bug description: The following upstream patch is missing: 11d7a0bb95ea xfrm: Only add l3mdev oif to dst lookups https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=11d7a0bb95ea There are several ways to reproduce this problem. Here an example: # Prepare netns ip netns add test ip netns exec test sysctl -q -w net.ipv4.conf.all.forwarding=1 ip netns exec test ip link set lo up ip netns exec test ip addr add 172.16.1.1/24 dev lo # Create VTI iface and move it in netns test ip addr add 1.1.1.1/32 dev lo ip link add name vti_test type vti local 1.1.1.1 remote 2.2.2.2 key 0x1 ip link set dev vti_test netns test # Configure IPsec ip xfrm state add src 1.1.1.1 dst 2.2.2.2 proto esp spi 1 mode tunnel enc 'cbc(aes)' '0x' auth-trunc 'hmac(sha1)' '0x' 96 flag align4 mark 0x1 ip xfrm state add src 2.2.2.2 dst 1.1.1.1 proto esp spi 2 mode tunnel enc 'cbc(aes)' '0x' auth-trunc 'hmac(sha1)' '0x' 96 flag align4 mark 0x1 ip xfrm policy add dir out tmpl src 1.1.1.1 dst 2.2.2.2 proto esp mode tunnel mark 0x1 ip xfrm policy add dir in tmpl src 2.2.2.2 dst 1.1.1.1 proto esp mode tunnel mark 0x1 # Configure SVTI ip netns exec test ip link set dev vti_test up # Add route ip netns exec test ip route add 172.16.2.0/24 dev vti_test # Run a tcpdump on the output interface (given by "ip route get 2.2.2.2") tcpdump -nei eth0 & # Ping from the netns ip netns exec test ping 172.16.2.1 -I 172.16.1.1 -c 4 -- On 4.4.0-109-generic: (ping) From 172.16.1.1 icmp_seq=1 Destination Host Unreachable (tcpdump) no IPsec packet => Problem On 4.8.0-58-generic: (ping): no error raised (tcpdump) 15:09:45.109776 de:ad:de:01:02:03 > 52:55:0a:00:02:02, ethertype IPv4 (0x0800), length 166: 1.1.1.1 > 2.2.2.2: ESP(spi=0x0001,seq=0x2), length 132 (tcpdump) 15:10:05.422243 de:ad:de:01:02:03 > 52:55:0a:00:02:02, ethertype IPv4 (0x0800), length 166: 1.1.1.1 > 2.2.2.2: ESP(spi=0x0001,seq=0x3), length 132 => No problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1744078/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1774225] Re: netns: unable to follow an interface that moves to another netns
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => Confirmed
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Released
** Changed in: linux (Ubuntu Xenial)
Assignee: Joseph Salisbury (jsalisbury) => (unassigned)
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1774225
Title:
netns: unable to follow an interface that moves to another netns
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Confirmed
Status in linux source package in Bionic:
Fix Released
Bug description:
== SRU Justification ==
6Wind is requesting these three patches. The patches fix a bug that prevents
a user
from following an interface that moves to another netns.
These commits are also needed in Xenial. However, they will be sent in
a separate SRU request due to additional prereq commits being needed for
Xenial.
== Fixes ==
b2d3bcfa26a7 ("net: core: Expose number of link up/down transitions")
c36ac8e23073 ("dev: always advertise the new nsid when the netns iface
changes")
38e01b30563a ("dev: advertise the new ifindex when the netns iface changes")
== Regression Potential ==
Medium due to three patches needed and the changes to core networking.
== Test Case ==
A test kernel was built with these patches and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
The following upstream patches are missing (v4.16):
6621dd29eb9b ("dev: advertise the new nsid when the netns iface changes")
c36ac8e23073 ("dev: always advertise the new nsid when the netns iface
changes")
38e01b30563a ("dev: advertise the new ifindex when the netns iface changes")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6621dd29eb9b
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c36ac8e23073
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=38e01b30563a
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774225/+subscriptions
___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1779830] Re: vfio/pci: cannot assign a i40e pf device to a vm using vfio-pci
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1779830
Title:
vfio/pci: cannot assign a i40e pf device to a vm using vfio-pci
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Fix Released
Bug description:
The following upstream patch (v4.7) is missing in xenial:
450744051d20 ("vfio/pci: Hide broken INTx support from user")
http://scm/kernels/linux-upstream/commit/?id=450744051d20
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779830/+subscriptions
___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1789653] Re: regression with EXT4 file systems and meta_bg flag
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1789653
Title:
regression with EXT4 file systems and meta_bg flag
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Fix Released
Bug description:
== SRU Justification ==
A regression was introduced where ext4_check_descriptors() was getting
called before s_gdb_count was initialized. This regression was
introduced to Xenial in 4.4.0-134. This is fixed by mainline commit
44de022c4382.
Commit 44de022c4382 was also cc'd to upstream stable. However, it has
not made it's way into Xenial via stable updates as of yet.
== Fix ==
44de022c4382 ("ext4: fix false negatives *and* false positives in
ext4_check_descriptors()")
== Regression Potential ==
Low. This commit has been cc'd upstream stable, so it has had
additional upstream review.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
Hello,
In 16.04 lts (Ubuntu 4.4.0-134.160-generic 4.4.140) with all
partitions in ext4 with flag meta_bg :
kernel: [ 1905.799557] EXT4-fs (dm-7): ext4_check_descriptors: Block bitmap
for group 0 overlaps block group descriptors
kernel: [ 1905.799858] EXT4-fs (dm-7): group descriptors corrupted!
Go back with the kernel 4.4.0-133-generic and all partitions mount
correctly.
It looks like this:
https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git/commit/?id=44de022c4382541cebdd6de4465d1f4f465ff1dd
The patch is available in 4.4.147 (https://lwn.net/Articles/762083/)
---
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code
2: ls: cannot access '/dev/snd/': No such file or directory
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
CRDA: N/A
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=/dev/mapper/vg_system-lv_system_swap
InstallationDate: Installed on 2017-04-28 (488 days ago)
InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64
(20160719)
IwConfig: Error: [Errno 2] No such file or directory
Lsusb: Error: [Errno 2] No such file or directory
MachineType: VMware, Inc. VMware Virtual Platform
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=fr_FR.UTF-8
SHELL=/bin/bash
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-134-generic
root=/dev/mapper/vg_system-lv_system_root ro ipv6.disable=1
ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140
RelatedPackageVersions:
linux-restricted-modules-4.4.0-134-generic N/A
linux-backports-modules-4.4.0-134-generic N/A
linux-firmware N/A
RfKill: Error: [Errno 2] No such file or directory
Tags: xenial xenial
Uname: Linux 4.4.0-134-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
_MarkForUpload: True
dmi.bios.date: 07/31/2013
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/31/2013:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.
---
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code
2: ls: cannot access '/dev/snd/': No such file or directory
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
CRDA: N/A
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=/dev/mapper/vg_system-lv_system_swap
InstallationDate: Installed on 2017-04-28 (488 days ago)
InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64
(20160719)
IwConfig: Error: [Errno 2] No such file or directory
Lsusb: Error: [Errno 2] No such file or directory
MachineType: VMware, Inc. VMware Virtual Platform
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=fr_FR.UTF-8
SHELL=/bin/bash
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-134-generic
root=/dev/mapper/vg_system-lv_system_root ro ipv6.disable=1
[Group.of.nepali.translators] [Bug 1791790] Re: Kernel hang on drive pull caused by regression introduced by commit 287922eb0b18
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1791790
Title:
Kernel hang on drive pull caused by regression introduced by commit
287922eb0b18
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Fix Released
Bug description:
== SRU Justification ==
The following commit was applied to Xenial and introduced this
regression:
287922eb0b18 ("block: defer timeouts to a workqueue")
This regression was introduced in mainline as of v4.5-rc1. Bionc was
also affected by this regression, but it already go the fix when commit
4e9b6f20828a was applied to mainline in v4.15-rc1.
The regression caused a kernel hang because the HPSA driver has a tendency
to aggressively remove missing devices.
== Fix ==
4e9b6f20828a ("block: Fix a race between blk_cleanup_queue() and timeout
handling")
== Regression Potential ==
Low. This commit fixes a regression and has been cc'd to stable, so it
has had addition upstream review. This commit is already applied to
Bionic and Cosmic.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
A bug was introduced when backporting the fix for
http://bugs.launchpad.net/bugs/1597908. This bug exists in all Ubuntu 16.04 LTS
4.4 kernels >= 4.4.0-36, and many other non-LTS kernels.
This patch changes the context in which timeout work is scheduled for
block devices in the kernel. Previously, timeout work was executed
directly from the timer callback that fired when a deadline was met.
After the patch, timeout work is scheduled using a background work
queue. This means that by the time the work executes, the device queue
which originally scheduled the work could be torn down. In order to
prevent this, the patch takes a reference on the device queue when
executing the timeout work.
The problem is that the last reference to this queue can be removed
before the timeout work can be executed. During teardown, the block
system executes a freeze followed by a drain. The freeze drops the
last reference on the queue. The drain tries to clean up any
outstanding work, including timeout work. After a freeze, the timeout
work in the background queue is unable to obtain a reference, and
exits early without completing work. The work is now permanently stuck
in the queue and it will never be completed. The drain in the device
teardown path spins indefinitely.
The bug manifests as a hang that looks like this:
[] schedule+0x35/0x80
[] hpsa_scan_start+0x109/0x140 [hpsa]
[] ? wake_atomic_t_function+0x60/0x60
[] hpsa_rescan_ctlr_worker+0x1d2/0x652 [hpsa]
[] process_one_work+0x165/0x480
[] worker_thread+0x4b/0x4c0
[] ? process_one_work+0x480/0x480
[] kthread+0xd8/0xf0
[] ? kthread_create_on_node+0x1e0/0x1e0
[] ret_from_fork+0x3f/0x70
[] ? kthread_create_on_node+0x1e0/0x1e0
The fix exists upstream. It applies, builds, and runs cleanly on Ubuntu's
most recent 4.4 kernel.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit?id=4e9b6f20828ac880dbc1fa2fdbafae779473d1af
We hit this bug nearly 100% of the time on some of our HP hardware.
The HPSA driver has a tendency to aggressively remove missing devices,
so it widens the race. As a result, we've been building our own kernel
with this patch applied. It would be really nice if we could get it
into mainline Ubuntu.
Let me know what additional information is needed. Thanks!
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791790/+subscriptions
___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1721065] Re: NULL pointer dereference in tty_write() in kernel 4.4.0-93.116+
** Changed in: linux (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1721065 Title: NULL pointer dereference in tty_write() in kernel 4.4.0-93.116+ Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Bug description: Sometimes an Ubuntu kernel 4.4.0-93+ panics in the following way: [ 11.185347] BUG: unable to handle kernel NULL pointer dereference at (null) [ 11.185778] IP: [] tty_write+0x83/0x2d0 [ 11.186115] PGD 0 [ 11.186270] Oops: [#1] SMP [ 11.186506] Modules linked in: prl_fs(POE) prl_eth(POE) gpio_ich ppdev snd_intel8x0 snd_ac97_codec ac97_bus snd_pcm s nd_timer input_leds snd serio_raw soundcore lpc_ich shpchp sbs prl_tg(POE) sbshc pvpanic parport_pc parport mac_hid auto fs4 psmouse ahci libahci pata_acpi fjes [ 11.188034] CPU: 0 PID: 1 Comm: systemd Tainted: P OE 4.4.0-96-generic #119-Ubuntu [ 11.188482] Hardware name: Parallels Software International Inc. Parallels Virtual Platform/Parallels Virtual Platfor m, BIOS 13.1.0 (43104) 09/26/2017 [ 11.189156] task: 88003db8 ti: 88003db88000 task.ti: 88003db88000 [ 11.189546] RIP: 0010:[] [] tty_write+0x83/0x2d0 [ 11.189964] RSP: :88003db8bcc8 EFLAGS: 00010246 [ 11.190255] RAX: RBX: 8800392dd800 RCX: [ 11.190628] RDX: RSI: RDI: 8800392dd828 [ 11.191002] RBP: 88003db8bd18 R08: 88003db88000 R09: [ 11.191398] R10: 005c R11: 00401ce0 R12: 002f [ 11.191775] R13: 88003584ae70 R14: 55c8eab15f20 R15: 88003584ae00 [ 11.192152] FS: 7f649d1418c0() GS:88003de0() knlGS: [ 11.192573] CS: 0010 DS: ES: CR0: 80050033 [ 11.192882] CR2: CR3: 3d3b6000 CR4: 06f0 [ 11.193264] Stack: [ 11.193404] 813953ba 88003db8bd08 813493bd [ 11.193837] 002f 88003584ae00 55c8eab15f20 88003584ae70 [ 11.194267] 002f 88003db8bf18 88003db8bd28 8120f878 [ 11.194700] Call Trace: [ 11.194884] [] ? apparmor_file_permission+0x1a/0x20 [ 11.195248] [] ? security_file_permission+0x3d/0xc0 [ 11.195621] [] __vfs_write+0x18/0x40 [ 11.195916] [] vfs_write+0xa9/0x1a0 [ 11.196202] [] redirected_tty_write+0x60/0xa0 [ 11.196532] [] ? tty_write+0x2d0/0x2d0 [ 11.196830] [] do_loop_readv_writev+0x75/0xa0 [ 11.197160] [] ? tty_write+0x2d0/0x2d0 [ 11.197458] [] do_readv_writev+0x212/0x230 [ 11.198439] [] ? do_vfs_ioctl+0x29f/0x490 [ 11.199374] [] vfs_writev+0x39/0x50 [ 11.200268] [] SyS_writev+0x59/0xf0 [ 11.201144] [] ? SyS_ioctl+0x79/0x90 [ 11.202049] [] entry_SYSCALL_64_fastpath+0x16/0x71 [ 11.202980] Code: 47 02 00 00 48 8b 93 e0 01 00 00 83 e2 02 0f 85 37 02 00 00 48 83 78 50 00 0f 84 38 02 00 00 48 89 df e8 11 7f 00 00 48 89 45 b0 <48> 8b 00 48 8b 40 40 48 89 c2 48 89 45 c0 48 c7 c0 fb ff ff ff [ 11.208047] RIP [] tty_write+0x83/0x2d0 [ 11.208942] RSP [ 11.209713] CR2: [ 11.210517] ---[ end trace 3b933544655b49b8 ]--- [ 11.335210] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0009 [ 11.335210] [ 11.337095] Kernel Offset: disabled [ 11.338184] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x0009 The crash occurs here 1227 static ssize_t tty_write(struct file *file, const char __user *buf, [...] 1243 ld = tty_ldisc_ref_wait(tty); 1244 if (!ld->ops->write) // <=== 1245 ret = -EIO; 1246 else 1247 ret = do_tty_write(ld->ops->write, tty, file, buf, count); because tty_ldisc_ref_wait() returned NULL. It seems the issue has been introduced into 4.4.0-93+ kernels by the fix for the bug #1709126: according to the version 4.4.0-93.116 changelog the patch "tty: Destroy ldisc instance on hangup" (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=892d1fa7eaaed9d3c04954cb140c34ebc3393932) that allowed tty_ldisc_ref_wait() to return NULL has been backported into the Ubuntu Linux kernel 4.4.0-93+. However, the patch "tty: Prepare for destroying line discipline on hangup" (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e55afd11a48354c810caf6b6ad4c103016a88230) from the same patchset (https://lkml.org/lkml/2015/11/27/476) that prepares tty_ldisc_ref_wait() callers for this hasn't been backported. Additional info: Kernel
[Group.of.nepali.translators] [Bug 1729337] Re: CIFS errors on 4.4.0-98, but not on 4.4.0-97 with same config
** Changed in: linux (Ubuntu Zesty)
Status: In Progress => Fix Released
** Changed in: linux (Ubuntu Trusty)
Status: In Progress => Fix Released
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1729337
Title:
CIFS errors on 4.4.0-98, but not on 4.4.0-97 with same config
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Trusty:
Fix Released
Status in linux source package in Xenial:
Fix Released
Status in linux source package in Zesty:
Fix Released
Status in linux source package in Artful:
Won't Fix
Bug description:
== SRU Justification ==
The bug reporter stated they have a cluster of servers that applied Xenial
updates
and then were unable to mount CIFS shares after upgrading to 4.4.0-98. The
same machines on 4.4.0-97 do not hit the regression. It was found that the
regression is fixed by mainline commit:
4587eee04e2a ("SMB3: Validate negotiate request must always be signed").
This fix is required in all Ubuntu supported releases. Commit 4587eee04e2a
landed in mailine as of 4.14-rc7. It was also cc'd to upstream stable,
but it has not landed in any stable releases yet, which is the reason for
this SRU.
== Fix ==
commit 4587eee04e2ac7ac3ac9fa2bc164fb6e548f99cd
Author: Steve French
Date: Wed Oct 25 15:58:31 2017 -0500
SMB3: Validate negotiate request must always be signed
== Regression Potential ==
This patch is to fix a regression. It was also cc'd to upstream stable, so
it received addition review upstream.
We have a cluster of servers that applied a security update overnight
and were unable to mount CIFS shares after upgrading to 4.4.0-98. The
same machines on 4.4.0-97 were fine the night before, and are fine
after downgrading. The only error message CIFS would report, even on
verbose, was:
[ 257.089876] CIFS VFS: validate protocol negotiate failed: -11
[ 257.089964] CIFS VFS: cifs_mount failed w/return code = -5
Rebooting did not help. Nor did attempting to mount the share
manually using mount -t cifs.
Here's the offending line from our /etc/fstab (with hostnames
sanitized):
//server/share /mnt/share cifs
rw,user,credentials=/etc/samba/credentials.share,uid=33,gid=33,file_mode=0770,dir_mode=0770
,exec,soft,noserverino,vers=3.0 0 0
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-98-generic 4.4.0-98.121
ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
Uname: Linux 4.4.0-98-generic x86_64
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Nov 1 07:56 seq
crw-rw 1 root audio 116, 33 Nov 1 07:56 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
Date: Wed Nov 1 08:49:47 2017
HibernationDevice: RESUME=/dev/mapper/ubuntu--template--vg-swap_1
InstallationDate: Installed on 2016-12-16 (319 days ago)
InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64
(20160719)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb: Error: command ['lsusb'] failed with exit code 1:
MachineType: VMware, Inc. VMware Virtual Platform
PciMultimedia:
ProcFB: 0 svgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-98-generic
root=/dev/mapper/ubuntu--template--vg-root ro
RelatedPackageVersions:
linux-restricted-modules-4.4.0-98-generic N/A
linux-backports-modules-4.4.0-98-generic N/A
linux-firmware1.157.13
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/21/2015
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd09/21/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729337/+subscriptions
___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to :
[Group.of.nepali.translators] [Bug 1687273] Re: Shared folder randomly not mounted
** Changed in: linux (Ubuntu Xenial) Status: In Progress => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1687273 Title: Shared folder randomly not mounted Status in Linux: Unknown Status in cifs-utils package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Released Status in cifs-utils source package in Xenial: Confirmed Status in linux source package in Xenial: Fix Released Status in linux package in Debian: Fix Released Bug description: Hello Everybody, since last update from ubuntu 16.04.2, last night, my servers are randomly not able to read and write from shared folders. I got this message: lsof: WARNING: can't stat() cifs file system /mnt/record Output information may be incomplete. lsof: WARNING: can't stat() cifs file system /mnt/record Output information may be incomplete. lsof: WARNING: can't stat() cifs file system /mnt/record Output information may be incomplete. ... rsync: ERROR: cannot stat destination "/mnt/record/": Host is down (112) rsync error: errors selecting input/output files, dirs (code 3) at main.c(652) [Receiver=3.1.1] This comes from my cron script. When I type df -h it takes sometimes very long to get the list. And it also can be that the mounted share is disconnected and I have to mount -a (what also takes long) again. My fstab have this command: //address /mnt/storage cifs auto,nofail,iocharset=utf8,rw,credentials=/path/.smb,uid=1000,gid=1000,file_mode=0660,dir_mode=0770 0 0 My update list from last night was this: linux-image-4.4.0-75-generic:amd64 (4.4.0-75.96, automatic) linux-image-extra-4.4.0-75-generic:amd64 (4.4.0-75.96, automatic) linux-headers-4.4.0-75-generic:amd64 (4.4.0-75.96, automatic) linux-headers-4.4.0-75:amd64 (4.4.0-75.96, automatic) Upgrade: libdns-export162:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.5, 1:9.10.3.dfsg.P4-8ubuntu1.6) linux-headers-generic:amd64 (4.4.0.72.78, 4.4.0.75.81) linux-libc-dev:amd64 (4.4.0-72.93, 4.4.0-75.96) mysql-client-5.7:amd64 (5.7.17-0ubuntu0.16.04.2, 5.7.18-0ubuntu0.16.04.1) libapt-inst2.0:amd64 (1.2.19, 1.2.20) mysql-server-5.7:amd64 (5.7.17-0ubuntu0.16.04.2, 5.7.18-0ubuntu0.16.04.1) libsystemd0:amd64 (229-4ubuntu16, 229-4ubuntu17) linux-image-generic:amd64 (4.4.0.72.78, 4.4.0.75.81) apt:amd64 (1.2.19, 1.2.20) mysql-server:amd64 (5.7.17-0ubuntu0.16.04.2, 5.7.18-0ubuntu0.16.04.1) udev:amd64 (229-4ubuntu16, 229-4ubuntu17) libapt-pkg5.0:amd64 (1.2.19, 1.2.20) libudev1:amd64 (229-4ubuntu16, 229-4ubuntu17) cifs-utils:amd64 (2:6.4-1ubuntu1, 2:6.4-1ubuntu1.1) dpkg:amd64 (1.18.4ubuntu1.1, 1.18.4ubuntu1.2) mysql-client-core-5.7:amd64 (5.7.17-0ubuntu0.16.04.2, 5.7.18-0ubuntu0.16.04.1) libisc-export160:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.5, 1:9.10.3.dfsg.P4-8ubuntu1.6) linux-virtual:amd64 (4.4.0.72.78, 4.4.0.75.81) systemd-sysv:amd64 (229-4ubuntu16, 229-4ubuntu17) distro-info-data:amd64 (0.28ubuntu0.2, 0.28ubuntu0.3) systemd:amd64 (229-4ubuntu16, 229-4ubuntu17) mysql-common:amd64 (5.7.17-0ubuntu0.16.04.2, 5.7.18-0ubuntu0.16.04.1) apt-utils:amd64 (1.2.19, 1.2.20) libmysqlclient20:amd64 (5.7.17-0ubuntu0.16.04.2, 5.7.18-0ubuntu0.16.04.1) linux-headers-virtual:amd64 (4.4.0.72.78, 4.4.0.75.81) linux-image-extra-virtual:amd64 (4.4.0.72.78, 4.4.0.75.81) thermald:amd64 (1.5-2ubuntu3, 1.5-2ubuntu4) qemu-guest-agent:amd64 (1:2.5+dfsg-5ubuntu10.10, 1:2.5+dfsg-5ubuntu10.11) libfreetype6:amd64 (2.6.1-0.1ubuntu2.1, 2.6.1-0.1ubuntu2.2) linux-image-virtual:amd64 (4.4.0.72.78, 4.4.0.75.81) libdpkg-perl:amd64 (1.18.4ubuntu1.1, 1.18.4ubuntu1.2) mysql-server-core-5.7:amd64 (5.7.17-0ubuntu0.16.04.2, 5.7.18-0ubuntu0.16.04.1) libxslt1.1:amd64 (1.1.28-2.1, 1.1.28-2.1ubuntu0.1) dpkg-dev:amd64 (1.18.4ubuntu1.1, 1.18.4ubuntu1.2) I saw that somebody else has the same problem: https://askubuntu.com/questions/910058/updates-broke-cifs-smb-mounts- in-16-04 I had to remove the latest kernel update, after that it works. Regards To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1687273/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1587091] Re: Extended statistics from balloon for proper memory management
** Changed in: linux-lts-utopic (Ubuntu) Status: In Progress => Fix Released ** Changed in: linux (Ubuntu Wily) Status: In Progress => Fix Released ** Changed in: linux (Ubuntu Trusty) Status: In Progress => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1587091 Title: Extended statistics from balloon for proper memory management Status in linux package in Ubuntu: Fix Released Status in linux-lts-utopic package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Released Status in linux source package in Vivid: Won't Fix Status in linux source package in Wily: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Yakkety: Fix Released Bug description: There is QEMU/KVM and a Linux OS running inside the guest. Inside the Linux guest a balloon consumes memory in accordance with commands performed on the host side in QEMU and reports some statistics through memstat structure. For the Linux guest reported “free” value doesn’t describe the guest memory pressure at all. The provided patch set in Linux kernel extends the stat with available field. The problem is addressed in mainstream Linux with the following patchset: commit 5057dcd0f1aaad57e07e728ba20a99e205c6b9de Author: Igor Redko Date: Thu Mar 17 15:09:34 2016 -0700 virtio_balloon: export 'available' memory to balloon statistics Add a new field, VIRTIO_BALLOON_S_AVAIL, to virtio_balloon memory statistics protocol, corresponding to 'Available' in /proc/meminfo. It indicates to the hypervisor how big the balloon can be inflated without pushing the guest system to swap. Signed-off-by: Igor Redko Signed-off-by: Denis V. Lunev Reviewed-by: Roman Kagan Cc: Michael S. Tsirkin Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds commit d02bd27bd33dd7e8d22594cd568b81be0cb584cd Author: Igor Redko Date: Thu Mar 17 15:09:34 2016 -0700 mm/page_alloc.c: calculate 'available' memory in a separate function Add a new field, VIRTIO_BALLOON_S_AVAIL, to virtio_balloon memory statistics protocol, corresponding to 'Available' in /proc/meminfo. It indicates to the hypervisor how big the balloon can be inflated without pushing the guest system to swap. This metric would be very useful in VM orchestration software to improve memory management of different VMs under overcommit. This patch (of 2): Factor out calculation of the available memory counter into a separate exportable function, in order to be able to use it in other parts of the kernel. In particular, it appears a relevant metric to report to the hypervisor via virtio-balloon statistics interface (in a followup patch). Signed-off-by: Igor Redko Signed-off-by: Denis V. Lunev Reviewed-by: Roman Kagan Cc: Michael S. Tsirkin Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1587091/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1809168] Re: FIPS and Ubuntu standard kernels prior to 4.11.0 won't boot; root device not found
** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => Triaged ** Changed in: linux (Ubuntu) Status: Confirmed => Triaged ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => High -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1809168 Title: FIPS and Ubuntu standard kernels prior to 4.11.0 won't boot; root device not found Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: [IMPACT] Booting of the Xenial-based FIPS kernel packages failed with disk not found errors on amd64. This was also observed on standard Ubuntu kernels prior to 4.11.0. FIPS -- 1. linux-image-4.4.0-1002-fips <-- FAIL 2. linux-image-4.4.0-1006-fips <-- FAIL UBUNTU 1. Bionic kernels all WORK 2. Artful kernels: Ubuntu-4.11.0-1.6 <-- WORKS Ubuntu-4.10.0-26.30 <-- FAILS 3. Xenial kernels: Ubuntu-hwe-4.11.0-12.17_16.04.1 <--- WORKS Ubuntu-hwe-4.10.0-43.47_16.04.1 <--- FAILS Ubuntu-lts-* <--- ALL FAIL Ubuntu-4.4.0-* <--- ALL FAIL We have narrowed down the window to be: 4.11.0-1.6 (custom build) <--- WORKS 4.10.0-43.47~16.04.1 <-- FAILS Also works: https://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11/linux-image-4.11.0-041100-generic_4.11.0-041100.201705041534_amd64.deb Symptoms - System cannot find the root disk and drops into an initramfs shell: mdadm script local-block "CREATE group disk not found" "Gave up waiting for root device. Common problems: - Boot args (cat /proc/cmdline) - Check rootdelay=... - Check root= ... - Missing modules (cat /proc/modules; ls/dev) ALERT! UUID=... does not exist. Dropping to a shell! ... (initramfs)_ There does not appear to be any workaround so far. The disks are encrypted SSDs. Attaching commit list between the last known failing Artful kernel and earliest known working kernel (adjacent tags) and other info. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1809168/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1807757] Re: Drivers: hv: vmbus: Offload the handling of channels to two workqueues
SRU requests submitted:
Bionic:
https://lists.ubuntu.com/archives/kernel-team/2018-December/097360.html
Cosmic:
https://lists.ubuntu.com/archives/kernel-team/2018-December/097361.html
linux-azure:
https://lists.ubuntu.com/archives/kernel-team/2018-December/097359.html
** No longer affects: linux (Ubuntu Xenial)
** Changed in: linux (Ubuntu Bionic)
Status: Triaged => In Progress
** Changed in: linux-azure (Ubuntu)
Status: Triaged => In Progress
** Description changed:
== SRU Justification ==
Microsoft has identified a multiple-NIC-deadlock issue on Hyper-V VMs. This
bug is fixed by the following commit, which is in mainline as of v4.20-rc6:
37c2578c0c40 ("Drivers: hv: vmbus: Offload the handling of channels to two
workqueues")
A second commit is also needed to prevent a deadlock with single NIC VMs.
This commit is in mainline as of 4.19-rc3:
e04e7a7bbd4b ("hv_netvsc: Fix a deadlock by getting rtnl lock earlier in
netvsc_probe()")
The Disco development release has been rebased to upstream 4.19, and it
already has commit eceb0596548. Disco only needs 37c2578c0c40.
Cosmic does not require any dependent commits, just the two
above(37c2578c0c40, e04e7a7bbd4b).
linux-azure and Bionic(4.15+ kernels) require the following five dependent
commits:
4.18-rc1 - 7bf7bb37f16a ("hv_netvsc: fix network namespace issues with VF
support")
4.18-rc4 - 3ffe64f1a641 ("hv_netvsc: split sub-channel setup into async and
sync")
4.19-rc1 - 50229128727f ("Drivers: hv: vmbus: Fix the offer_in_progress in
vmbus_process_offer()")
4.19-rc3 - e04e7a7bbd4b ("hv_netvsc: Fix a deadlock by getting rtnl lock
earlier in netvsc_probe()")
4.19-rc4 - 6712cc9c2211 ("vmbus: don't return values for uninitalized
channels")
- Xenial(4.14 and older kernels) require the following five dependent commits:
- 4.15-rc1 - c2e5df616e1a ("vmbus: add per-channel sysfs info")
- 4.15-rc6 - 869b5567e12f ("vmbus: unregister device_obj->channels_kset")
- 4.19-rc1 - 50229128727f ("Drivers: hv: vmbus: Fix the offer_in_progress in
vmbus_process_offer()")
- 4.19-rc4 - 6712cc9c2211 ("vmbus: don't return values for uninitalized
channels")
- 4.20-rc5 - eceb05965489 ("Drivers: hv: vmbus: check the creation_status in
vmbus_establish_gpadl()")
== Fixes ==
("Dependent commits mentioned above, based on Ubuntu release")
e04e7a7bbd4b ("hv_netvsc: Fix a deadlock by getting rtnl lock earlier in
netvsc_probe()")
37c2578c0c40 ("Drivers: hv: vmbus: Offload the handling of channels to
two workqueues")
== Regression Potential ==
Low. Limited to hyperv.
== Test Case ==
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1807757
Title:
Drivers: hv: vmbus: Offload the handling of channels to two workqueues
Status in linux package in Ubuntu:
Fix Committed
Status in linux-azure package in Ubuntu:
In Progress
Status in linux source package in Bionic:
In Progress
Status in linux source package in Cosmic:
In Progress
Status in linux source package in Disco:
Fix Committed
Bug description:
== SRU Justification ==
Microsoft has identified a multiple-NIC-deadlock issue on Hyper-V VMs. This
bug is fixed by the following commit, which is in mainline as of v4.20-rc6:
37c2578c0c40 ("Drivers: hv: vmbus: Offload the handling of channels to two
workqueues")
A second commit is also needed to prevent a deadlock with single NIC VMs.
This commit is in mainline as of 4.19-rc3:
e04e7a7bbd4b ("hv_netvsc: Fix a deadlock by getting rtnl lock earlier in
netvsc_probe()")
The Disco development release has been rebased to upstream 4.19, and
it already has commit eceb0596548. Disco only needs 37c2578c0c40.
Cosmic does not require any dependent commits, just the two
above(37c2578c0c40, e04e7a7bbd4b).
linux-azure and Bionic(4.15+ kernels) require the following five dependent
commits:
4.18-rc1 - 7bf7bb37f16a ("hv_netvsc: fix network namespace issues with VF
support")
4.18-rc4 - 3ffe64f1a641 ("hv_netvsc: split sub-channel setup into async and
sync")
4.19-rc1 - 50229128727f ("Drivers: hv: vmbus: Fix the offer_in_progress in
vmbus_process_offer()")
4.19-rc3 - e04e7a7bbd4b ("hv_netvsc: Fix a deadlock by getting rtnl lock
earlier in netvsc_probe()")
4.19-rc4 - 6712cc9c2211 ("vmbus: don't return values for uninitalized
channels")
== Fixes ==
("Dependent commits mentioned above, based on Ubuntu release")
e04e7a7bbd4b ("hv_netvsc: Fix a deadlock by getting rtnl lock earlier
in netvsc_probe()")
37c2578c0c40 ("Drivers: hv: vmbus: Offload the handling of channels to
two workqueues")
== Regression Potential ==
Low. Limited to hyperv.
== Test Case ==
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1807757/+subscriptions
[Group.of.nepali.translators] [Bug 1788549] Re: powerpc/powernv/pci: Work around races in PCI bridge enabling
@Mike, do you feel comfortable with the testing you've done to submit an SRU request? Or would you like to perform some additional testing? ** Changed in: linux (Ubuntu Cosmic) Status: In Progress => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1788549 Title: powerpc/powernv/pci: Work around races in PCI bridge enabling Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: Fix Released Bug description: == Comment: #0 - Michael Ranweiler - 2018-08-21 13:52:03 == +++ This bug was initially created as a clone of Bug #170766 +++ Please apply the following kernel patch: https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=next=db2173198b9513f7add8009f225afa1f1c79bcc6 powerpc/powernv/pci: Work around races in PCI bridge enabling The generic code is racy when multiple children of a PCI bridge try to enable it simultaneously. This leads to drivers trying to access a device through a not-yet-enabled bridge, and this EEH errors under various circumstances when using parallel driver probing. There is work going on to fix that properly in the PCI core but it will take some time. x86 gets away with it because (outside of hotplug), the BIOS enables all the bridges at boot time. This patch does the same thing on powernv by enabling all bridges that have child devices at boot time, thus avoiding subsequent races. It's suitable for backporting to stable and distros, while the proper PCI fix will probably be significantly more invasive. Signed-off-by: Benjamin Herrenschmidt Cc: sta...@vger.kernel.org Signed-off-by: Michael Ellerman == Comment: #2 - Michael Ranweiler - 2018-08-21 18:23:35 == This has some fuzz and also move it back from the pci macro to dev_err so we'll attach the backported patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1788549/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1807757] Re: Drivers: hv: vmbus: Offload the handling of channels to two workqueues
** Description changed:
Microsoft has identified a multiple-NIC-deadlock issue on Hyper-V VMs. This
bug is fixed by the following commit, which is in mainline as of v4.20-rc6:
37c2578c0c40 ("Drivers: hv: vmbus: Offload the handling of channels to two
workqueues")
A second commit is also needed to prevent a deadlock with single NIC VMs.
This commit is in mainline as of 4.19-rc3:
e04e7a7bbd4b ("hv_netvsc: Fix a deadlock by getting rtnl lock earlier in
netvsc_probe()")
- The Disco development release has been rebased to upstream 4.19, so no
- prereqs are needed, only commit 37c2578c0c40.
+ The Disco development release has been rebased to upstream 4.19, so it only
needs one prereq:
+ 4.20-rc5 - eceb05965489 ("Drivers: hv: vmbus: check the creation_status in
vmbus_establish_gpadl()")
- linux-azure, Bionic and Cosmic(4.15+ kernels) require the following two
dependent commits:
+ linux-azure, Bionic and Cosmic(4.15+ kernels) require the following three
dependent commits:
4.19-rc1 - 50229128727f ("Drivers: hv: vmbus: Fix the offer_in_progress in
vmbus_process_offer()")
4.19-rc4 - 6712cc9c2211 ("vmbus: don't return values for uninitalized
channels")
+ 4.20-rc5 - eceb05965489 ("Drivers: hv: vmbus: check the creation_status in
vmbus_establish_gpadl()")
- Xenial(4.14 and older kernels) require the following four dependent commits:
+ Xenial(4.14 and older kernels) require the following five dependent commits:
4.15-rc1 - c2e5df616e1a ("vmbus: add per-channel sysfs info")
4.15-rc6 - 869b5567e12f ("vmbus: unregister device_obj->channels_kset")
4.19-rc1 - 50229128727f ("Drivers: hv: vmbus: Fix the offer_in_progress in
vmbus_process_offer()")
4.19-rc4 - 6712cc9c2211 ("vmbus: don't return values for uninitalized
channels")
+ 4.20-rc5 - eceb05965489 ("Drivers: hv: vmbus: check the creation_status in
vmbus_establish_gpadl()")
** Description changed:
Microsoft has identified a multiple-NIC-deadlock issue on Hyper-V VMs. This
bug is fixed by the following commit, which is in mainline as of v4.20-rc6:
37c2578c0c40 ("Drivers: hv: vmbus: Offload the handling of channels to two
workqueues")
A second commit is also needed to prevent a deadlock with single NIC VMs.
This commit is in mainline as of 4.19-rc3:
e04e7a7bbd4b ("hv_netvsc: Fix a deadlock by getting rtnl lock earlier in
netvsc_probe()")
- The Disco development release has been rebased to upstream 4.19, so it only
needs one prereq:
+ The Disco development release has been rebased to upstream 4.19, so it only
needs one dependent commit:
4.20-rc5 - eceb05965489 ("Drivers: hv: vmbus: check the creation_status in
vmbus_establish_gpadl()")
linux-azure, Bionic and Cosmic(4.15+ kernels) require the following three
dependent commits:
4.19-rc1 - 50229128727f ("Drivers: hv: vmbus: Fix the offer_in_progress in
vmbus_process_offer()")
4.19-rc4 - 6712cc9c2211 ("vmbus: don't return values for uninitalized
channels")
4.20-rc5 - eceb05965489 ("Drivers: hv: vmbus: check the creation_status in
vmbus_establish_gpadl()")
Xenial(4.14 and older kernels) require the following five dependent commits:
4.15-rc1 - c2e5df616e1a ("vmbus: add per-channel sysfs info")
4.15-rc6 - 869b5567e12f ("vmbus: unregister device_obj->channels_kset")
4.19-rc1 - 50229128727f ("Drivers: hv: vmbus: Fix the offer_in_progress in
vmbus_process_offer()")
4.19-rc4 - 6712cc9c2211 ("vmbus: don't return values for uninitalized
channels")
4.20-rc5 - eceb05965489 ("Drivers: hv: vmbus: check the creation_status in
vmbus_establish_gpadl()")
** Also affects: linux-azure (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: linux-azure (Ubuntu Xenial)
** No longer affects: linux-azure (Ubuntu Bionic)
** No longer affects: linux-azure (Ubuntu Cosmic)
** No longer affects: linux-azure (Ubuntu Disco)
** Changed in: linux-azure (Ubuntu)
Status: New => Triaged
** Changed in: linux-azure (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux-azure (Ubuntu)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Description changed:
Microsoft has identified a multiple-NIC-deadlock issue on Hyper-V VMs. This
bug is fixed by the following commit, which is in mainline as of v4.20-rc6:
37c2578c0c40 ("Drivers: hv: vmbus: Offload the handling of channels to two
workqueues")
A second commit is also needed to prevent a deadlock with single NIC VMs.
This commit is in mainline as of 4.19-rc3:
e04e7a7bbd4b ("hv_netvsc: Fix a deadlock by getting rtnl lock earlier in
netvsc_probe()")
- The Disco development release has been rebased to upstream 4.19, so it only
needs one dependent commit:
- 4.20-rc5 - eceb05965489 (&qu
[Group.of.nepali.translators] [Bug 1790832] Re: crypto/vmx - Backport of Fix sleep-in-atomic bugs patch for 18.04
** Changed in: linux (Ubuntu Xenial)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1790832
Title:
crypto/vmx - Backport of Fix sleep-in-atomic bugs patch for 18.04
Status in The Ubuntu-power-systems project:
Fix Committed
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Fix Released
Status in linux source package in Bionic:
Fix Released
Status in linux source package in Cosmic:
Fix Released
Bug description:
== SRU Justification ==
IBM is requesting this patch in all releases order to fix the sleep-in-atomic
bugs in AES-CBC and AES-XTS VMX implementations.
This patch is a clean cherry pick and has already been applied to
Cosmic. It is also needed in Xenial, but there was a minor context
diff, so the Xenial SRU will be sent separatly.
== Fix ==
0522236d4f9c ("crypto: vmx - Fix sleep-in-atomic bugs")
== Regression Potential ==
Low. This patch has also been cc'd to upstream stable, so it has had
additional upstream review.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
== Comment: #0 - Paulo Flabiano Smorigo
Please include the following commit in order to fix the sleep-in-atomic bugs
in AES-CBC and AES-XTS VMX implementations [1]:
0522236 crypto: vmx - Fix sleep-in-atomic bugs
[1]
https://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6.git/commit/?id=0522236d4f9c5ab2e79889cb020d1acbe5da416e
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1790832/+subscriptions
___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1798127] Re: CPU Soft Lockups when stress-ng stack stressor runs with M.2 NVMe as root FS
Would it be possible for you to test the latest upstream stable 4.18? It can be downloaded from: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18.19/ ** Tags removed: kernel-key ** Tags added: kernel-da-key ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu Bionic) Status: Confirmed => Triaged ** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Cosmic) Status: New => Triaged ** Changed in: linux (Ubuntu Cosmic) Importance: Undecided => High ** Changed in: linux (Ubuntu Cosmic) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux (Ubuntu) Status: Confirmed => Triaged ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1798127 Title: CPU Soft Lockups when stress-ng stack stressor runs with M.2 NVMe as root FS Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Invalid Status in linux source package in Bionic: Triaged Status in linux source package in Cosmic: Triaged Bug description: This was reported by a hardware partner. The system set up is a server with 512GB RAM and an M.2 NVMe drive as the root filesystem/boot device. Per the customer, when running the certification Memory Stress test (utilizing several stress-ng stressors run in sequence) the system freezes with CPU Soft Lockup errors appearing on console whe the "stack" stressor is run. Tester has tried with 2.5” SATA (1TB), 2.5” NVMe (800GB), and M.2 NVMe (1.9TB). So far, this only seems to affect the 4.15 kernel. The tester has tried using the 2.5" SATA SSD as the RootFS/Boot device and the tests pass on all attempts. It is ONLY when using the M.2 NVMe as the root / boot device that the tests cause a lockup. The tester is re-trying now with the 2.5" NVMe device to see if this only occurs with the M.2 NVMe. The tester has tried this on the following while using the M.2 NVMe as the rootFS/Boot device: Test run #1 – 16.04.5 at kernel 4.15; Result: Failed stress-ng memory on stack stressor Test run #2 – 18.04.1 at kernel 4.15; Result: Failed stress-ng memory on stack stressor Test run #3 – 16.04.5 at kernel 4.4; Result: Passed stress-ng memory test The stress-ng command invoked at the time the soft lockups occur is this: 'stress-ng -k --aggressive --verify --timeout 300 --stack 0' This can be reproduced by running the memory_stress_ng test script from the cert suite: sudo /usr/lib/plainbox-provider-certification- server/bin/memory_stress_ng It may be more easily reproducible running the stack stressor alone, or the whole memory stress script without dealing with Checkbox. UPDATE: The tester also confirms that the 2.5" NVMe drives also fail with the 4.15 kernel and pass with the 4.4 kernel. The SSD works on all kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798127/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1729637] Re: Samba mount/umount in docker container triggers kernel Oops
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1729637
Title:
Samba mount/umount in docker container triggers kernel Oops
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Fix Released
Status in linux source package in Zesty:
Fix Released
Bug description:
== SRU Justification ==
This bug causes Samba mount and umounts in docker container to trigger
a kernel Oops. When running 2 docker containers, one as samba server and
another one as samba client that mounts and umounts a smb share a kernel
OOps can be triggered.
This bug happens in Xenial and Zesty, and is fixed by the following two
commits:
76da0704507b ("ipv6: only call ip6_route_dev_notify() once for
NETDEV_UNREGISTER")
12d94a804946 ("ipv6: fix NULL dereference in ip6_route_dev_notify()")
Both commits are clean cherry picks. 76da0704507b is in mainline as of v4.12.
Commit 12d94a804946 is in mainline as of v4.13-rc6.
== Fixes ==
commit 76da0704507bbc51875013f6557877ab308cfd0a
Author: WANG Cong
Date: Tue Jun 20 11:42:27 2017 -0700
ipv6: only call ip6_route_dev_notify() once for NETDEV_UNREGISTER
commit 12d94a804946af291e24b80fc53ec86264765781
Author: Eric Dumazet
Date: Tue Aug 15 04:09:51 2017 -0700
ipv6: fix NULL dereference in ip6_route_dev_notify()
== Regression Potential ==
Both commits are specific to ipv6 and fix a regression introduced into Xenial
and Zesty.
== Test Case ==
A test kernel was built with these patches and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
The kernel message:
unregister_netdevice: waiting for lo to become free. Usage count = 1
shows up, some minutes later the oops and/or warnings happens.
The scripts to trigger the kernel Oops can be found at:
https://github.com/fho/docker-samba-loop
I was able to reproduce kernel Oopses on a clean Ubuntu 16.0.4 installation
with:
- linux-image-4.4.0-93-generic=4.4.0-93.116~14.04.1
- linux-image-4.10.0-32-generic=4.10.0-32.36~16.04.1
- linux-image-4.11.0-14-generic=4.11.0-14.20~16.04.1
In a different scenario were Ubuntu 16.04 servers were running
multiple docker containers with Nginx or small network applications in
parallel, I was also able to reproduce the kernel Oopses also on:
- linux-image-4.10.0-1004-gcp
- linux-image-4.12.10-041210-generic=4.12.10-041210.20170830
I haven't tried again to reproduce it with those kernels on a clean Ubuntu
installation and unfortunately didn't kept the kernel logs.
The "unregister_netdevice: waiting for lo to become free. Usage count
= 1" messages are related to
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1711407 which is
handled as separate issue.
According to https://github.com/moby/moby/issues/35068 the crash is fixed by:
https://patchwork.ozlabs.org/patch/801533/
https://patchwork.ozlabs.org/patch/778449/
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Nov 3 09:51 seq
crw-rw 1 root audio 116, 33 Nov 3 09:51 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
DistroRelease: Ubuntu 16.04
IwConfig: Error: [Errno 2] No such file or directory
Lsusb: Error: command ['lsusb'] failed with exit code 1:
MachineType: Google Google Compute Engine
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=rxvt-unicode-256color
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic
root=UUID=bf9a017a-931d-4191-84bc-b8434dbba527 ro scsi_mod.use_blk_mq=Y
console=ttyS0
ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
RelatedPackageVersions:
linux-restricted-modules-4.10.0-37-generic N/A
linux-backports-modules-4.10.0-37-generic N/A
linux-firmware N/A
RfKill: Error: [Errno 2] No such file or directory
Tags: xenial uec-images xenial uec-images
Uname: Linux 4.10.0-37-generic x86_64
UnreportableReason: The report belongs to a package that is not installed.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
_MarkForUpload: False
dmi.bios.date: 01/01/2011
dmi.bios.vendor: Google
dmi.bios.version: Google
dmi.board.asset.tag: A3DDBB61-646B-C60C-3999-1F1D7B7A334A
dmi.board.name: Google Compute Engine
dmi.board.vendor: Google
dmi.chassis.type: 1
dmi.chassis.vendor: Google
dmi.modalias:
[Group.of.nepali.translators] [Bug 1744300] Re: bt_iter() crash due to NULL pointer
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1744300
Title:
bt_iter() crash due to NULL pointer
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Fix Released
Status in linux source package in Artful:
Fix Released
Bug description:
SRU Justification:
[Impact]
The following crash was observed in Ubuntu 16.04 running linux-gcp kernel
version 4.13 (specifically 4.13.0-1006.9):
[ 10.972644] BUG: unable to handle kernel NULL pointer dereference at
0030
[ 10.980708] IP: bt_iter+0x31/0x50
[ 10.984310] PGD 0
[ 10.984310] P4D 0
[ 10.986439]
[ 10.990190] Oops: [#1] SMP PTI
[ 11.016282] Workqueue: kblockd blk_mq_timeout_work
[ 11.021196] task: 8e7c2e70 task.stack: b8d4c67a8000
[ 11.027234] RIP: 0010:bt_iter+0x31/0x50
[ 11.031187] RSP: 0018:b8d4c67abda0 EFLAGS: 00010206
[ 11.037730] RAX: b8d4c67abdd0 RBX: 0180 RCX:
[ 11.045172] RDX: 8e7c34c8d280 RSI: RDI:
8e7c32dd8000
[ 11.053321] RBP: b8d4c67abe20 R08: R09:
2100
[ 11.060582] R10: 0130 R11: fffee5bf R12:
8e7c3572c790
[ 11.068094] R13: 8e7c3572c780 R14: 0008 R15:
8e7c35e7c180
[ 11.075522] FS: () GS:8e7c3a4c()
knlGS:
[ 11.083721] CS: 0010 DS: ES: CR0: 80050033
[ 11.089593] CR2: 0030 CR3: 9e20a003 CR4:
001606e0
[ 11.096871] Call Trace:
[ 11.099468] ? blk_mq_queue_tag_busy_iter+0xe2/0x1f0
[ 11.104558] ? blk_mq_rq_timed_out+0x70/0x70
[ 11.109130] ? blk_mq_rq_timed_out+0x70/0x70
[ 11.114933] blk_mq_timeout_work+0xbb/0x170
[ 11.119408] process_one_work+0x156/0x410
[ 11.123641] worker_thread+0x4b/0x460
[ 11.127827] kthread+0x109/0x140
[ 11.131186] ? process_one_work+0x410/0x410
[ 11.135499] ? kthread_create_on_node+0x70/0x70
[ 11.140408] ret_from_fork+0x1f/0x30
[ 11.144110] Code: 89 d0 48 8b 3a 0f b6 48 18 48 8b 97 30 01 00 00 84 c9 75
03 03 72 04 48 8b 92 80 00 00 00 89 f6 48 8b 34 f2 48 8b 97 c0 00 00 00 <48> 39
56 30 74 06 b8 01 00 00 00 c3 55 48 8b 50 10 48 89 e5 ff
[ 11.167573] RIP: bt_iter+0x31/0x50 RSP: b8d4c67abda0
[ 11.173028] CR2: 0030
[ 11.176515] ---[ end trace 2f8e5b1cf4139fec ]---
[ 11.182589] Kernel panic - not syncing: Fatal exception
Basically, we have a NULL pointer dereference while in bt_iter()
function - this is caused because after the merge of blk-mq scheduler
capability on Linux kernel , tags->rqs[] array has been dinamically
assigned and there's a small window of time in which the bit is set
but tags->rqs[] array wasn't allocated yet. This was reported to
happen in about 5% of test runs (more details on test section).
[Fix]
The fix is small and simple, and it's upstream already. Basically, it adds a
NULL pointer check on bt_iter() and bt_tags_iter() functions.
The fix is: 7f5562d5ecc4 ("blk-mq-tag: check for NULL rq when iterating
tags"), by Jens Axboe.
(https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7f5562d5ecc4)
[Testcase]
Since the problem manifests in a small non-deterministic time window, there's
no easy test to reproduce this. In our case, it was observed while testing a
large number of CPU's and attached disks (>200 disks, >150 cores), trying to
exercise all CPUs and disks (the disks with quick dd commands). In this test
scenario, as already mentioned, issue occured in about 5% of the runs.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1744300/+subscriptions
___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1800641] Re: [Ubuntu] qeth: Fix potential array overrun in cmd/rc lookup
SRU request submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-October/096372.html
** Changed in: linux (Ubuntu)
Status: Triaged => Fix Released
** Changed in: linux (Ubuntu)
Status: Fix Released => In Progress
** Changed in: linux (Ubuntu Xenial)
Status: Triaged => In Progress
** Changed in: linux (Ubuntu Bionic)
Status: Triaged => In Progress
** Changed in: linux (Ubuntu Cosmic)
Status: Triaged => In Progress
** Description changed:
+
+ == SRU Justification ==
+ IBM is requesting these commits in s390 for X, B and C. The bug
+ description the commits fix is as follows:
+
+ Description: qeth: Fix potential array overrun in cmd/rc lookup Symptom:
+ Infinite loop when processing a received cmd.
+ Problem: qeth_get_ipa_cmd_name() and qeth_get_ipa_msg() are used to build
+ human-readable messages for received cmd data.
+
+
+ == Fixes ==
+ 065a2cdcbdf8 ("s390: qeth_core_mpc: Use ARRAY_SIZE instead of reimplementing
its function")
+ 048a7f8b4ec0 ("s390: qeth: Fix potential array overrun in cmd/rc lookup")
+
+ == Regression Potential ==
+ Low. Limited to s390.
+
+ == Test Case ==
+ A test kernel was built with these two patches and tested by IBM.
+ The bug reporter states the test kernel resolved the bug.
+
+
+
Description: qeth: Fix potential array overrun in cmd/rc lookup
Symptom: Infinite loop when processing a received cmd.
Problem: qeth_get_ipa_cmd_name() and qeth_get_ipa_msg() are used
- to build human-readable messages for received cmd data.
+ to build human-readable messages for received cmd data.
- They store the to-be translated value in the last entry of a
- global array, and then iterate over each entry until they found
- the queried value (and the corresponding message string).
- If there is no prior match, the lookup is intended to stop at
- the final entry (which was previously prepared).
+ They store the to-be translated value in the last entry of a
+ global array, and then iterate over each entry until they found
+ the queried value (and the corresponding message string).
+ If there is no prior match, the lookup is intended to stop at
+ the final entry (which was previously prepared).
- If two qeth devices are concurrently processing a received cmd,
- one lookup can over-write the last entry of the global array
- while a second lookup is in process. This second lookup will
then
- never hit its stop-condition, and loop.
+ If two qeth devices are concurrently processing a received cmd,
+ one lookup can over-write the last entry of the global array
+ while a second lookup is in process. This second lookup will
then
+ never hit its stop-condition, and loop.
Solution: Remove the modification of the global array, and limit the
number
- of iterations to the size of the array.
-
+ of iterations to the size of the array.
Upstream-ID: kernel 4.19
- 065a2cdcbdf8eb9aefb66e1a24b2d684b8b8852b
- 048a7f8b4ec085d5c56ad4a3bf450389a4aed5f9
Should also be applied, to all other Ubuntu Releases in the field !
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1800641
Title:
[Ubuntu] qeth: Fix potential array overrun in cmd/rc lookup
Status in Ubuntu on IBM z Systems:
Triaged
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
In Progress
Status in linux source package in Bionic:
In Progress
Status in linux source package in Cosmic:
In Progress
Bug description:
== SRU Justification ==
IBM is requesting these commits in s390 for X, B and C. The bug
description the commits fix is as follows:
Description: qeth: Fix potential array overrun in cmd/rc lookup Symptom:
Infinite loop when processing a received cmd.
Problem: qeth_get_ipa_cmd_name() and qeth_get_ipa_msg() are used to build
human-readable messages for received cmd data.
== Fixes ==
065a2cdcbdf8 ("s390: qeth_core_mpc: Use ARRAY_SIZE instead of reimplementing
its function")
048a7f8b4ec0 ("s390: qeth: Fix potential array overrun in cmd/rc lookup")
== Regression Potential ==
Low. Limited to s390.
== Test Case ==
A test kernel was built with these two patches and tested by IBM.
The bug reporter states the test kernel resolved the bug.
Description: qeth: Fix potential array overrun in cmd/rc lookup
Symptom: Infinite loop when processing a received cmd.
Problem: qeth_get_ipa_cmd_name() and qeth_get_ipa_msg() are used
to build human-readable messages for received cmd data.
[Group.of.nepali.translators] [Bug 1800849] Re: [Ubuntu] kvm: fix deadlock when killed by oom
Xenial and Cosmic already have commit 306d6c49ac9 via upstream stable updates. I built a Bionic test kernel with commit 306d6c49ac9. The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1800849 Can you test this kernel and see if it resolves this bug? Note about installing test kernels: • If the test kernel is prior to 4.15(Bionic) you need to install the linux-image and linux-image-extra .deb packages. • If the test kernel is 4.15(Bionic) or newer, you need to install the linux-modules, linux-modules-extra and linux-image-unsigned .deb packages. Thanks in advance! ** Changed in: linux (Ubuntu Xenial) Status: Triaged => Fix Released ** Changed in: linux (Ubuntu Bionic) Status: Triaged => In Progress ** Changed in: linux (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1800849 Title: [Ubuntu] kvm: fix deadlock when killed by oom Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: Fix Released Bug description: Description: kvm: fix deadlock when killed by oom Symptom: oom killer leaves processes in a deadlock state. Problem: The problem arises in the rare cases in which handle_mm_fault does not release the mm_sem. Solution: Correct the issue by manually relaese the mm_sem when needed. Reproduction: Create numerous KVM guests so that the host starts swapping and memory becomes overcomitted and the oom killer is triggered. kernel 4.19 Upstream-ID: 306d6c49ac9ded4cb53b0925da52f2c2ada1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1800849/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1800849] Re: [Ubuntu] kvm: fix deadlock when killed by oom
** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Status: New => Triaged ** Changed in: linux (Ubuntu) Assignee: Skipper Bug Screeners (skipper-screen-team) => Joseph Salisbury (jsalisbury) ** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => Triaged ** Changed in: linux (Ubuntu Bionic) Status: New => Triaged ** Changed in: linux (Ubuntu Cosmic) Status: New => Triaged ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => High ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => High ** Changed in: linux (Ubuntu Cosmic) Importance: Undecided => High ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu Cosmic) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu Cosmic) Status: Triaged => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1800849 Title: [Ubuntu] kvm: fix deadlock when killed by oom Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: Fix Released Bug description: Description: kvm: fix deadlock when killed by oom Symptom: oom killer leaves processes in a deadlock state. Problem: The problem arises in the rare cases in which handle_mm_fault does not release the mm_sem. Solution: Correct the issue by manually relaese the mm_sem when needed. Reproduction: Create numerous KVM guests so that the host starts swapping and memory becomes overcomitted and the oom killer is triggered. kernel 4.19 Upstream-ID: 306d6c49ac9ded4cb53b0925da52f2c2ada1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1800849/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1692538] Re: Ubuntu 16.04.02: ibmveth: Support to enable LSO/CSO for Trunk VEA
** No longer affects: linux (Ubuntu Xenial) -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1692538 Title: Ubuntu 16.04.02: ibmveth: Support to enable LSO/CSO for Trunk VEA Status in The Ubuntu-power-systems project: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Zesty: Fix Released Status in linux source package in Artful: Fix Released Bug description: == SRU Justification == Commit 66aa0678ef is request to fix four issues with the ibmveth driver. The issues are as follows: - Issue 1: ibmveth doesn't support largesend and checksum offload features when configured as "Trunk". - Issue 2: SYN packet drops seen at destination VM. When the packet originates, it has CHECKSUM_PARTIAL flag set and as it gets delivered to IO server's inbound Trunk ibmveth, on validating "checksum good" bits in ibmveth receive routine, SKB's ip_summed field is set with CHECKSUM_UNNECESSARY flag. - Issue 3: First packet of a TCP connection will be dropped, if there is no OVS flow cached in datapath. - Issue 4: ibmveth driver doesn't have support for SKB's with frag_list. The details for the fixes to these issues are described in the commits git log. == Comment: #0 - BRYANT G. LY - 2017-05-22 08:40:16 == ---Problem Description--- - Issue 1: ibmveth doesn't support largesend and checksum offload features when configured as "Trunk". Driver has explicit checks to prevent enabling these offloads. - Issue 2: SYN packet drops seen at destination VM. When the packet originates, it has CHECKSUM_PARTIAL flag set and as it gets delivered to IO server's inbound Trunk ibmveth, on validating "checksum good" bits in ibmveth receive routine, SKB's ip_summed field is set with CHECKSUM_UNNECESSARY flag. This packet is then bridged by OVS (or Linux Bridge) and delivered to outbound Trunk ibmveth. At this point the outbound ibmveth transmit routine will not set "no checksum" and "checksum good" bits in transmit buffer descriptor, as it does so only when the ip_summed field is CHECKSUM_PARTIAL. When this packet gets delivered to destination VM, TCP layer receives the packet with checksum value of 0 and with no checksum related flags in ip_summed field. This leads to packet drops. So, TCP connections never goes through fine. - Issue 3: First packet of a TCP connection will be dropped, if there is no OVS flow cached in datapath. OVS while trying to identify the flow, computes the checksum. The computed checksum will be invalid at the receiving end, as ibmveth transmit routine zeroes out the pseudo checksum value in the packet. This leads to packet drop. - Issue 4: ibmveth driver doesn't have support for SKB's with frag_list. When Physical NIC has GRO enabled and when OVS bridges these packets, OVS vport send code will end up calling dev_queue_xmit, which in turn calls validate_xmit_skb. In validate_xmit_skb routine, the larger packets will get segmented into MSS sized segments, if SKB has a frag_list and if the driver to which they are delivered to doesn't support NETIF_F_FRAGLIST feature. Contact Information = Bryant G. Ly/b...@us.ibm.com ---uname output--- 4.8.0-51.54 Machine Type = p8 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Increases performance greatly The patch has been accepted upstream: https://patchwork.ozlabs.org/patch/764533/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1692538/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1797990] Re: kdump fail due to an IRQ storm
** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Cosmic) Importance: High Assignee: Guilherme G. Piccoli (gpiccoli) Status: Confirmed ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1797990 Title: kdump fail due to an IRQ storm Status in linux package in Ubuntu: Confirmed Status in linux source package in Trusty: New Status in linux source package in Xenial: New Status in linux source package in Bionic: New Status in linux source package in Cosmic: Confirmed Bug description: We have reports of a kdump failure in Ubuntu (in x86 machine) that was narrowed down to a MSI irq storm coming from a PCI network device. The bug manifests as a lack of progress in the boot process of the kdump kernel, and a storm of kernel messages like: [...] [ 342.265294] do_IRQ: 0.155 No irq handler for vector [ 342.266916] do_IRQ: 0.155 No irq handler for vector [ 347.258422] do_IRQ: 14053260 callbacks suppressed [...] The root cause of the the issue is that the kdump kernel kexec process does not ensure PCI devices are reset and/or MSI capabilities are disabled, so a PCI device could produce a huge amount of PCI irqs which would take all the processing time for the CPU (specially since we restrict the kdump kernel to use one single CPU only). This was tested using upstream kernel version 4.18, and the problem reproduces. In the specific test scenario, the PCI NIC was an "Intel 82599ES 10-Gigabit [8086:10fb]" that was used in SR-IOV PCI passthrough mode (vfio_pci), under high load on the guest. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797990/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1798110] Re: xenial: virtio-scsi: CPU soft lockup due to loop in virtscsi_target_destroy()
** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Triaged ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => Triaged ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Medium -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1798110 Title: xenial: virtio-scsi: CPU soft lockup due to loop in virtscsi_target_destroy() Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: [Impact] * Detaching virtio-scsi disk in Xenial guest can cause CPU soft lockup in guest (and take 100% CPU in host). * It may prevent further progress on other tasks that depend on resources locked earlier in the SCSI target removal stack, and/or impact other SCSI functionality. * The fix resolves a corner case in the requests counter in the virtio SCSI target, which impacts a downstream (SAUCE) patch in the virtio-scsi target removal handler that depends on the requests counter value to be zero. [Test Case] * See LP #1798110 (this bug)'s comment #3 (too long for this section -- synthetic case with GDB+QEMU) and comment #4 (organic test case in cloud instance). [Regression Potential] * It seem low -- this only affects the SCSI command requeue path with regards to the reference counter, which is only used with real chance of problems in our downstream patch (which is now passing this testcase). * The other less serious issue would be decrementing it to a negative / < 0 value, which is not possible with this driver logic (see commit message), because the reqs counter is always incremented before calling virtscsi_queuecommand(), where this decrement operation is inserted. [Original Description] A customer reported a CPU soft lockup on Trusty HWE kernel from Xenial when detaching a virtio-scsi drive, and provided a crashdump that shows 2 things: 1) The soft locked up CPU is waiting for another CPU to finish something, and that does not happen because the other CPU is infinitely looping in virtscsi_target_destroy(). 2) The loop happens because the 'tgt->reqs' counter is non-zero, and that probably happened due to a missing decrement in SCSI command requeue path, exercised when the virtio ring is full. The reported problem itself happens because of a downstream/SAUCE patch, coupled with the problem of the missing decrement for the reqs counter. Introducing a decrement in the SCSI command requeue path resolves the problem, verified synthetically with QEMU+GDB and with test-case/loop provided by the customer as problem reproducer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798110/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1790832] Re: crypto/vmx - Backport of Fix sleep-in-atomic bugs patch for 18.04
** Changed in: linux (Ubuntu Cosmic) Status: In Progress => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1790832 Title: crypto/vmx - Backport of Fix sleep-in-atomic bugs patch for 18.04 Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: Fix Released Bug description: == Comment: #0 - Paulo Flabiano Smorigo Please include the following commit in order to fix the sleep-in-atomic bugs in AES-CBC and AES-XTS VMX implementations [1]: 0522236 crypto: vmx - Fix sleep-in-atomic bugs [1] https://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6.git/commit/?id=0522236d4f9c5ab2e79889cb020d1acbe5da416e To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1790832/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1773165] Re: openvswitch-datapath-dkms kernel module is not getting loaded
@Ridsai, Are you still see this bug with the latest updates applied? ** Tags added: kernel-key ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Xenial) Status: New => Confirmed -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1773165 Title: openvswitch-datapath-dkms kernel module is not getting loaded Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Bug description: Distributor ID: Ubuntu Description: Ubuntu 16.04.4 LTS Release: 16.04 Codename: xenial Kernel version: 4.4.0-127-generic OVS version: 2.7.0 # Issue description openvswitch-datapath-dkms kernelmodule is not getting loaded # Error from dmesg [10863.380564] openvswitch: module verification failed: signature and/or required key missing - tainting kernel [10863.381804] openvswitch: exports duplicate symbol dst_cache_destroy (owned by kernel) [10863.517173] openvswitch: exports duplicate symbol dst_cache_destroy (owned by kernel) [10878.094250] openvswitch: exports duplicate symbol dst_cache_destroy (owned by kernel) #Error from syslog May 24 08:37:06 dev65 kernel: [76508.361496] openvswitch: exports duplicate symbol dst_cache_destroy (owned by kernel) May 24 08:37:06 dev65 openvswitch-switch[18336]: modprobe: ERROR: could not insert 'openvswitch': Exec format error May 24 08:37:06 dev65 openvswitch-switch[18336]: * Inserting openvswitch module #installation logs: Selecting previously unselected package openvswitch-datapath-dkms. (Reading database ... 84707 files and directories currently installed.) Preparing to unpack openvswitch-datapath-dkms_2.7.0-1_all.deb ... Unpacking openvswitch-datapath-dkms (2.7.0-1) ... Setting up openvswitch-datapath-dkms (2.7.0-1) ... Creating symlink /var/lib/dkms/openvswitch/2.7.0/source -> /usr/src/openvswitch-2.7.0 DKMS: add completed. Kernel preparation unnecessary for this kernel. Skipping... Building module: cleaning build area(bad exit status: 2) ./configure --with-linux='/lib/modules/4.4.0-127-generic/build' && make -C datapath/linux.. cleaning build area(bad exit status: 2) DKMS: build completed. openvswitch: Running module version sanity check. - Original module - Installation - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/ vport-geneve.ko: Running module version sanity check. - Original module - Installation - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/ vport-gre.ko: Running module version sanity check. - Original module - Installation - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/ vport-lisp.ko: Running module version sanity check. - Original module - Installation - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/ vport-stt.ko: Running module version sanity check. - Original module - Installation - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/ vport-vxlan.ko: Running module version sanity check. - Original module - Installation - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/ depmod DKMS: install completed. #Dpkg status dpkg -l | grep openvswitch ii openvswitch-common 2.7.0-1 amd64Open vSwitch common components ii openvswitch-datapath-dkms2.7.0-1 all Open vSwitch datapath module source - DKMS version ii openvswitch-switch 2.7.0-1 amd64Open vSwitch switch implementations ii python-openvswitch 2.6.1-0ubuntu5.2~cloud0 all Python bindings for Open vSwitch #lsmod status No modules are listing for openvswitch-datapath-dkms #modprobe error modprobe openvswitch modprobe: ERROR: could not insert 'openvswitch': Exec format error --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.4.0-127-generic. AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory Card0.Amixer.values: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2]
[Group.of.nepali.translators] [Bug 1709784] Re: KVM on 16.04.3 throws an error
** Changed in: linux (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1709784 Title: KVM on 16.04.3 throws an error Status in The Ubuntu-power-systems project: Fix Released Status in linux package in Ubuntu: Fix Committed Status in qemu package in Ubuntu: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux source package in Zesty: Invalid Bug description: Problem Description KVM on Ubuntu 16.04.3 throws an error when used ---uname output--- Linux bastion-1 4.4.0-89-generic #112-Ubuntu SMP Mon Jul 31 19:37:08 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux Machine Type = 8348-21C Habanero ---Steps to Reproduce--- Install 16.04.3 install KVM like: apt-get install libvirt-bin qemu qemu-slof qemu-system qemu-utils then exit and log back in so virsh will work without sudo then run my spawn script $ cat spawn.sh #!/bin/bash img=$1 qemu-system-ppc64 \ -machine pseries,accel=kvm,usb=off -cpu host -m 512 \ -display none -nographic \ -net nic -net user \ -drive "file=$img" with a freshly downloaded ubuntu cloud image sudo ./spawn.sh xenial-server-cloudimg-ppc64el-disk1.img And I get nothing on the output. and errors in dmesg ubuntu@bastion-1:~$ [ 340.180295] Facility 'TM' unavailable, exception at 0xd000148b7f10, MSR=90009033 [ 340.180399] Oops: Unexpected facility unavailable exception, sig: 6 [#1] [ 340.180513] SMP NR_CPUS=2048 NUMA PowerNV [ 340.180547] Modules linked in: xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables kvm_hv kvm binfmt_misc joydev input_leds mac_hid opal_prd ofpart cmdlinepart powernv_flash ipmi_powernv ipmi_msghandler mtd at24 uio_pdrv_genirq uio ibmpowernv powernv_rng vmx_crypto ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid1 raid0 multipath linear mlx4_en hid_generic usbhid hid uas usb_storage ast i2c_algo_bit bnx2x ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops mlx4_core drm ahci vxlan libahci ip6_udp_tunnel udp_tunnel mdio libcrc32c [ 340.181331] CPU: 46 PID: 5252 Comm: qemu-system-ppc Not tainted 4.4.0-89-generic #112-Ubuntu [ 340.181382] task: c01e34c30b50 ti: c01e34ce4000 task.ti: c01e34ce4000 [ 340.181432] NIP: d000148b7f10 LR: d00014822a14 CTR: d000148b7e40 [ 340.181475] REGS: c01e34ce77b0 TRAP: 0f60 Not tainted (4.4.0-89-generic) [ 340.181519] MSR: 90009033 CR: 22024848 XER: [ 340.181629] CFAR: d000148b7ea4 SOFTE: 1 GPR00: d00014822a14 c01e34ce7a30 d000148cc018 c01e37bc GPR04: c01db9ac c01e34ce7bc0 GPR08: 0001 c01e34c30b50 0001 d000148278f8 GPR12: d000148b7e40 cfb5b500 001f GPR16: 3fff91c3 0080 3fffa8e34390 3fff9242f200 GPR20: 3fff92430010 01001de5c030 3fff9242eb60 100c1ff0 GPR24: 3fffc91fe990 3fff91c10028 c01e37bc GPR28: c01db9ac c01e37bc c01db9ac [ 340.182315] NIP [d000148b7f10] kvmppc_vcpu_run_hv+0xd0/0xff0 [kvm_hv] [ 340.182357] LR [d00014822a14] kvmppc_vcpu_run+0x44/0x60 [kvm] [ 340.182394] Call Trace: [ 340.182413] [c01e34ce7a30] [c01e34ce7ab0] 0xc01e34ce7ab0 (unreliable) [ 340.182468] [c01e34ce7b70] [d00014822a14] kvmppc_vcpu_run+0x44/0x60 [kvm] [ 340.182522] [c01e34ce7ba0] [d0001481f674] kvm_arch_vcpu_ioctl_run+0x64/0x170 [kvm] [ 340.182581] [c01e34ce7be0] [d00014813918] kvm_vcpu_ioctl+0x528/0x7b0 [kvm] [ 340.182634] [c01e34ce7d40] [c02fffa0] do_vfs_ioctl+0x480/0x7d0 [ 340.182678] [c01e34ce7de0] [c03003c4] SyS_ioctl+0xd4/0xf0 [ 340.182723] [c01e34ce7e30] [c0009204] system_call+0x38/0xb4 [ 340.182766] Instruction dump: [ 340.182788] e92d02a0 e9290a50 e9290108 792a07e3 41820058 e92d02a0 e9290a50 e9290108 [ 340.182863] 7927e8a4 78e71f87 40820ed8 e92d02a0 <7d4022a6> f9490ee8 e92d02a0 7d4122a6 [ 340.182938] ---[ end trace bc5080cb7d18f102 ]--- [ 340.276202] This was with the latest ubuntu cloud image. I get the same thing when trying to use virt-install with an ISO image. I
[Group.of.nepali.translators] [Bug 1740974] Re: [800 G3 SFF] [800 G3 DM]External microphone of headset(3-ring) is working, 2-ring mic not working, both not shown in sound settings
** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: hwe-next Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1740974 Title: [800 G3 SFF] [800 G3 DM]External microphone of headset(3-ring) is working, 2-ring mic not working, both not shown in sound settings Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Status in linux-oem source package in Xenial: Fix Released Status in linux source package in Artful: Fix Released Status in linux-oem source package in Artful: Invalid Bug description: External microphone of headset(3-ring) is working, 2-ring mic not working, both not shown in sound settings. Steps: 1. Plug headset(3-ring) or microphone (2-ring) 2. Observe input device in sound setting Expected results: Microphone should be detected and working Actual results: Microphone is not detected, only 3-ring mic (from headset) is working To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1740974/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1709032] Re: Creating conntrack entry failure with kernel 4.4.0-89
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1709032
Title:
Creating conntrack entry failure with kernel 4.4.0-89
Status in Linux:
Confirmed
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Fix Released
Bug description:
The functional job failure rate is at 100%. Every time some test gets
stuck and job is killed after timeout.
logstash query:
http://logstash.openstack.org/#dashboard/file/logstash.json?query=build_name%3A%5C
%22gate-neutron-dsvm-functional-ubuntu-
xenial%5C%22%20AND%20tags%3Aconsole%20AND%20message%3A%5C%22Killed%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20timeout%20-s%209%5C%22
2017-08-05 12:36:50.127672 | /home/jenkins/workspace/gate-neutron-
dsvm-functional-ubuntu-xenial/devstack-gate/functions.sh: line 1129:
15261 Killed timeout -s 9 ${REMAINING_TIME}m bash -c
"source $WORKSPACE/devstack-gate/functions.sh && $cmd"
There are a few test executors left, which means there are more tests
stuck:
stack15468 15445 15468 0.0 0.0 328 796 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpDTLPoX
stack15469 15468 15469 1.5 1.8 139332 150008 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpDTLPoX
stack15470 15445 15470 0.0 0.0 328 700 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpICNqRQ
stack15471 15470 15471 1.6 2.0 152056 164812 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpICNqRQ
stack15474 15445 15474 0.0 0.0 328 792 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpe646Tl
stack15475 15474 15475 1.6 1.9 149972 162516 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpe646Tl
stack15476 15445 15476 0.0 0.0 328 804 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpv2ovhz
stack15477 15476 15477 1.2 1.8 136760 149160 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpv2ovhz
stack15478 15445 15478 0.0 0.0 328 712 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpDqXE8S
stack15479 15478 15479 1.5 1.9 148784 161004 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpDqXE8S
stack15480 15445 15480 0.0 0.0 328 804 /bin/sh -c
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1}
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit} --load-list /tmp/tmpTmmShS
stack15482 15480 15482 1.6 1.9 148856 161516 python -m subunit.run
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpTmmShS
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1709032/+subscriptions
___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1777858] Re: Redpine: Observed kernel panic while running wireless regressions tests
** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1777858 Title: Redpine: Observed kernel panic while running wireless regressions tests Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Bug description: SRU Justification: -- Impact: Kernel freezes/panic when running wireless tests Test case: 1. Create a wireless soft-ap/station upon reboot. 2. Install Checkbox plano and : $ sudo snap install --devmode checkbox-plano 3. Run below wifi-ap test case $ checkbox-plano.checkbox-cli run .*device .*wireless/caracalla-wifi_ap_.*wlan0_auto 4. Upon 3-4 iteraions, observed kernel crash as below, BUG: unable to handle kernel NULL pointer dereference at (null) IP: [] exit_creds+0x1f/0x50 PGD 0 Oops: 0002 [#1] SMP CPU: 0 PID: 6502 Comm: rmmod Tainted: G OE 4.4.0-128-generic #154-Ubuntu Hardware name: Dell Inc. Edge Gateway 3003/ , BIOS 01.00.00 04/17/2017 Stack: 88007392e600 880075847dc0 8108160a 88007392e600 880075847de8 810a484b 880076127000 88003cd3a800 880074f12a00 880075847e28 c09bed15 Call Trace: [] __put_task_struct+0x5a/0x140 [] kthread_stop+0x10b/0x110 [] rsi_disconnect+0x2f5/0x300 [ven_rsi_sdio] [] ? __pm_runtime_resume+0x5b/0x80 [] sdio_bus_remove+0x38/0x100 [] __device_release_driver+0xa4/0x150 [] driver_detach+0xb5/0xc0 [] bus_remove_driver+0x55/0xd0 [] driver_unregister+0x2c/0x50 [] sdio_unregister_driver+0x1a/0x20 [] rsi_module_exit+0x15/0x30 [ven_rsi_sdio] [] SyS_delete_module+0x1b8/0x210 [] entry_SYSCALL_64_fastpath+0x1c/0xbb Fix: kthread_stop() is taking care of wait_for_completion() by default. No need of taking care separately. Issue is resolved by removing wait_for_completion() from rsi_disconnect(). Regression Petential: Ran Step 3 in 30-times. Didn't see any kernel panic. This bug is for tracking purposes only, please don't triage. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777858/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1777850] Re: Redpine: Observed kernel panic while running soft-ap tests
** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1777850 Title: Redpine: Observed kernel panic while running soft-ap tests Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Bug description: SRU Justification: -- Impact: Kernel freezes/panic when running wireless tests for soft-ap Test case: 1. Create a soft-ap upon reboot. 2. Install Checkbox plano and : $ sudo snap install --devmode checkbox-plano 3. Run below wifi-ap test case $ checkbox-plano.checkbox-cli run .*device .*wireless/caracalla-wifi_ap_.*wlan0_auto 4. Upon 3-4 iteraions, observed kernel crash as below, [ 718.83244] BUG: unable to handle page request at 001067e38 [ 718.83248] IP: cfg80211_scan_done+0xb0/0xc0 [cfg80211] [ 718.83971] __ieee80211_scan_completed+0xb1/0x390 [mac80211] [ 718.84078] ieee80211_scan_work+0x7e/0x480 [mac80211] [ 718.84098] process_one_work+0x142/0x3d0 [ 718.84111] worker_thread+0x229/0x440 [ 718.84122] kthread+0xf5/0x130 [ 718.84132] ? process_one_work+0x3d0/0x3d0 [ 718.84140] ? kthread_associate_blkcg+0x90/0x90 [ 718.84152] ret_from_fork+0x35/0x40 Fix: scan work function keeps running even after cancel_hw_scan() call. Issue is resolved by calling cancel_work_sync() in rsi_mac80211_stop(). Regression Petential: Ran Step 3 in 30-times. Didn't see any kernel panic. This bug is for tracking purposes only, please don't triage. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777850/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1757443] Re: Redpine: BLE radio lost issue
** Changed in: linux (Ubuntu Xenial) Status: Triaged => Fix Released ** Changed in: linux (Ubuntu) Status: Incomplete => Fix Released ** Changed in: linux (Ubuntu Bionic) Status: Incomplete => Fix Released ** Changed in: linux-firmware (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1757443 Title: Redpine: BLE radio lost issue Status in linux package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux-firmware source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-firmware source package in Bionic: Fix Released Bug description: SRU Justification Impact: Radio stops capturing advertisements after several hours. Fix: Updated firmware. Test Case: See below. Regression Potential: Limited to specific hardware. --- Below are the steps to replicate the issue We are doing continuous BLE scanning and monitoring the advertisements from reference device. After long periods of capture (several hours), the radio stops capturing advertisements and won't start again until we power cycle the box or manually unload/load the module via modprobe This bug is for tracking purposes only, please don't triage. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757443/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1742090] Re: Redpine: Wifi/BT not functioning after s3 resume
** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1742090 Title: Redpine: Wifi/BT not functioning after s3 resume Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Bug description: System cannot be waked by wowlan, but sometimes works. When the wowlan not works and system waked by other wakeup sources, after resume the wifi and BT would not functioning until reload driver. The driver/FW info: [ 395.217187] ven_rsi_91x: RSI Version Info == [ 395.217188] ven_rsi_91x: [ 395.217192] ven_rsi_91x: FW Version : 1.5.4 [ 395.217198] ven_rsi_91x: Driver Version : RS9113.NB0.NL.GNU.LNX.1.2 [ 395.217200] ven_rsi_91x: Operating mode : 13 [Wi-Fi STA + BT DUAL] [ 395.217201] ven_rsi_91x: Firmware file : RS9113_WLAN_BT_DUAL_MODE.rps [ 395.217202] ven_rsi_91x: Kernel version: 4.4.0-98-generic Kernel snap: caracalla-kernel version:4.4.0-98.121-1 revision:58 BIOS version: 01.00.05 (Also tested with 01.00.03) Tested SKU: T, Media, GPA The reproduce steps: 1. Enable Wowlan and Wol in BIOS 2. Boot up Ubuntu core 3. Connect to Wifi AP $ nmcli d wifi connect password 4. Enable wowlan $ sudo iw phy phy0 wowlan enable magic-packet 5. Enter suspend or hibernate $ sudo systemctl suspend or $ sudo systemctl hibernate 6. Send wake signal from another machine # wakeonlan or # sudo etherwake 7. If system not waked, try to wol or other wake source # wakeonlan 8. After resume, check the wifi/BT function, but not functioning. $ nmcli dev DEVICE TYPE STATE CONNECTION eth0 ethernet connected Wired connection 1 wlan0 wifi disconnected -- eth1 ethernet unavailable -- cdc-wdm0 gsm unavailable -- lo loopback unmanaged -- $ nmcli dev wifi rescan $ nmcli dev wfii list No wifi APs found $ sudo bluetoothctl [NEW] Controller 00:23:A7:EA:65:64 0225399 [default] [bluetooth]# power on Failed to set power on: org.bluez.Error.Failed The not functioning issue can be fixed by reload driver. Also hibernate wakeup fails, and wake by other wake source. The Wifi/BT still functioning which could be the FW is reloaded by driver. This bug is only for tracking purporse, please do not triage. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1742090/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1773410] Re: Redpine: Observed kernel panic while running wireless tests in regression mode
** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1773410 Title: Redpine: Observed kernel panic while running wireless tests in regression mode Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Bug description: SRU Justification - Impact: Kernel freezes/panic when running wireless tests in regression Test case: 1. Keep a wrong access-point name in sta.conf file and run the nmcli. 2. There will be continuous scan will be happen and do remove the module using rmmod.sh script. 3. When soft scan is happening in redpine driver, before connection. Some times, we have observed a kernel panic. like below [ 1171.913244] BUG: unable to handle page request at 001067e38 [ 1171.913248] IP: cfg80211_scan_done+0xb0/0xc0 [cfg80211] [ 1171.913971] __ieee80211_scan_completed+0xb1/0x390 [mac80211] [ 1171.914078] ieee80211_scan_work+0x7e/0x480 [mac80211] [ 1171.914098] process_one_work+0x142/0x3d0 [ 1171.914111] worker_thread+0x229/0x440 [ 1171.914122] kthread+0xf5/0x130 [ 1171.914132] ? process_one_work+0x3d0/0x3d0 [ 1171.914140] ? kthread_associate_blkcg+0x90/0x90 [ 1171.914152] ret_from_fork+0x35/0x40 Fix: scan work function keeps running even after cancel_hw_scan() call. Issue is resolved by calling cancel_work_sync(). Regression potential: Ran driver_crash.sh for 100 times and didn't see the issue. This bug is for tracking purposes only, please don't triage. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773410/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1793753] Re: kernel panic - null pointer dereference on ipset operations
** Changed in: linux (Ubuntu Xenial)
Status: Fix Committed => Fix Released
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1793753
Title:
kernel panic - null pointer dereference on ipset operations
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Fix Released
Bug description:
== SRU Justification ==
A regression was introduced in Xenial, even prior to v4.4 Final. I did
not test prior to this kernel once I found the bug was fixed in
mainline. The bug reporter experienced crashes on machines running
iptables using ipsets. He could get a trace from the console on one of
them which is attached to the bug report.
On these machines, some ipset commands are automatically run to update the
sets, and/or to dump them (ipset restore, swap, delete ... / ipset save).
I was able to reproduce this bug as was cking. This bug was found to be
fixed by mainline commits 596cf3fe5854 and e5173418ac59.
== Fixes ==
596cf3fe5854 ("netfilter: ipset: fix race condition in ipset save, swap and
delete")
e5173418ac59 ("netfilter: ipset: Fix race between dump and swap")
== Regression Potential ==
Low. This fixes a regression and is limited to netfilter.
== Test Case ==
A test kernel was built with these patches and tested by myself and cking.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1793753/+subscriptions
___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1743672] Re: the wifi driver is always hard blocked on a lenovo laptop
** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: hwe-next Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1743672 Title: the wifi driver is always hard blocked on a lenovo laptop Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Status in linux-oem source package in Xenial: Fix Released Status in linux source package in Artful: Fix Released Status in linux-oem source package in Artful: Invalid Bug description: On this machine, there is no wifi enable/disable hw switch, but the wifi driver is always reported the wifi radio is hard blocked by switch. The kernel is Artful and OEM kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1743672/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1690362] Re: Exar usb-serial doesn't restore baud rate after resume from S3/S4
** Changed in: linux (Ubuntu Bionic) Status: Triaged => Fix Released ** Changed in: linux (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1690362 Title: Exar usb-serial doesn't restore baud rate after resume from S3/S4 Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux-oem source package in Xenial: Invalid Status in linux source package in Bionic: Fix Released Status in linux-oem source package in Bionic: Fix Released Bug description: Resume from suspend-to-ram and suspend-to-disk should restore data send/receive over Exar usb-serial ports. The XR21V1412 ports were using the hardware power-on default of 9600bps after resume from S3/S4. This patch re-initializes the baud rate and fixes the re-connection issues after resume from S3/S4. This bug is to track the integration of the driver released by the vendor to fix this issue. Changelog: Version 1B, 11/6/2015 Fixed Bug: The conditional logic to support kernel 3.9 was incorrect(line 396 in xr_usb_serial_common.c). Version 1A, 1/9/2015 This driver will work with any USB UART function in these Exar devices: XR21V1410/1412/1414 XR21B1411 XR21B1420/1422/1424 XR22801/802/804 Exar serial devices are typically enuremated as /dev/ttyXRUSB[0-3] This bug is used for tracking purposes, please do not triage. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1690362/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1740973] Re: Two front mics can't work on a lenovo machine
** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: hwe-next Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1740973 Title: Two front mics can't work on a lenovo machine Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Status in linux-oem source package in Xenial: Fix Released Status in linux source package in Artful: Fix Released Status in linux-oem source package in Artful: Invalid Bug description: There are two front mics on this lenovo machine. The test case 'audio/microphone-plug-detection' is always failed To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1740973/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1626894] Re: nvme drive probe failure
** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1626894 Title: nvme drive probe failure Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Yakkety: Fix Released Bug description: After upgrading from linux-image-4.4.0-38-generic to proposed update linux-image-4.4.0-39-generic, NVMe drives are no longer working. dmesg shows a probe failure. On the previous kernel version everything is working as expected. ->%- [1.005243] Hardware name: FUJITSU D3417-B1/D3417-B1, BIOS V5.0.0.11 R1.12.0.SR.2 for D3417-B1x 04/01/2016 [1.005349] Workqueue: events nvme_remove_dead_ctrl_work [nvme] [1.005484] 0286 b6c91251 880fe6e8bce0 813f1f83 [1.005800] 880fe02150f0 c90006a7c000 880fe6e8bd00 8106bdff [1.006117] 880fe02150f0 880fe0215258 880fe6e8bd10 8106be3c [1.006433] Call Trace: [1.006509] [] dump_stack+0x63/0x90 [1.006589] [] iounmap.part.1+0x7f/0x90 [1.006668] [] iounmap+0x2c/0x30 [1.006770] [] nvme_dev_unmap.isra.35+0x1a/0x30 [nvme] [1.007048] [] nvme_remove+0xce/0xe0 [nvme] [1.007140] [] pci_device_remove+0x39/0xc0 [1.007220] [] __device_release_driver+0xa1/0x150 [1.007301] [] device_release_driver+0x23/0x30 [1.007382] [] pci_stop_bus_device+0x8a/0xa0 [1.007462] [] pci_stop_and_remove_bus_device_locked+0x1a/0x30 [1.007559] [] nvme_remove_dead_ctrl_work+0x3c/0x50 [nvme] [1.007642] [] process_one_work+0x165/0x480 [1.007722] [] worker_thread+0x4b/0x4c0 [1.007801] [] ? process_one_work+0x480/0x480 [1.007881] [] kthread+0xd8/0xf0 [1.007959] [] ? kthread_create_on_node+0x1e0/0x1e0 [1.008041] [] ret_from_fork+0x3f/0x70 [1.008120] [] ? kthread_create_on_node+0x1e0/0x1e0 [1.008222] Trying to free nonexistent resource[1.008276] genirq: Flags mismatch irq 0. 0080 (nvme1q0) vs. 00015a00 (timer) [1.008281] Trying to free nonexistent resource [1.008282] nvme :02:00.0: Removing after probe failure [1.008645] Trying to free nonexistent resource [1.027213] iounmap: bad address c90006ae [1.027456] CPU: 2 PID: 86 Comm: kworker/2:1 Not tainted 4.4.0-39-generic #59-Ubuntu -%<- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626894/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1736317] Re: ath10k: enhance rf signal strength
** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1736317 Title: ath10k: enhance rf signal strength Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Bug description: ath10k: add max_tx_power for QCA6174 WLAN.RM.2.0 firmware QCA6174 WLAN.RM.2.0 firmware uses max_tx_power instead of using max_reg_power to set transmission power. The tx power was about -50dbm, after applying this change, it become -32dbm. Signed-off-by: Alan Liu Signed-off-by: Kalle Valo https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/net/wireless/ath/ath10k?id=513527c87a7feab2a5b31db07e5b07864d3c08f7 This fix already included in Zesty/Artful/Bionic kernels. This bug is for tracking purposes only, please do not triage. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1736317/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1740971] Re: Can't detect external headset via line-out jack on some Dell machines
** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: hwe-next Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1740971 Title: Can't detect external headset via line-out jack on some Dell machines Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Status in linux-oem source package in Xenial: Fix Released Status in linux source package in Artful: Fix Released Status in linux-oem source package in Artful: Invalid Bug description: insert a headset to line-out jack Expected results: system should detect line-out port and sound output through line-out jack Actual results: Can't detect external headset via line-out jack To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1740971/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1742094] Re: [16.04][classic] Redpine: wowlan feature doesn't work
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1742094
Title:
[16.04][classic] Redpine: wowlan feature doesn't work
Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Fix Released
Bug description:
Steps to reproduce:
1. Ensure WoWLAN is enabled in BIOS.
2. Initiate connection to an AP (using nmcli)
3. Configure the device for WoWLAN, run the command:
$ sudo iw phy phy0 wowlan enable magic-packet
4. Enter S5/S4/S3 (using poweroff, etc.)
5. From another computer on the same network run the following command:
$ wakeonlan {mac} (in my case `wakeonlan 00:23:a7:ec:b4:04`)
Expected result: the device starts/resume
This bug is only for tracking purporse, please do not triage.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1742094/+subscriptions
___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1679898] Re: [Hyper-V] Ubuntu VM crash during Hyper-V backup or live migration after installing kernel 4.4.0-72
** Changed in: linux (Ubuntu) Status: In Progress => Invalid ** Changed in: linux (Ubuntu Xenial) Status: In Progress => Invalid -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1679898 Title: [Hyper-V] Ubuntu VM crash during Hyper-V backup or live migration after installing kernel 4.4.0-72 Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Bug description: Description:Ubuntu 14.04.5 LTS Release:14.04 Hi, after installing kernel 4.4.0-67 or later I cannot backup my Ubuntu VM's on Hyper-V. Microsoft Hyper-v 2012r2 Gen2 VMs See Attachment for what happens is immediately after backup starts I get an error. Eventually the kernel reports it has run out of memory and the machine just continuously scrolls errors message related to page allocation. When reseting the virtual machine no logs can be found of the problem. kernel 4.4.0-72-generic problem still here DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2016-02-20 (409 days ago) InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) Package: linux-image-4.4.0-72-generic 4.4.0-72.93~14.04.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.4.0-72.93~14.04.1-generic 4.4.49 SourcePackage: linux-lts-xenial Tags: trusty Uname: Linux 4.4.0-72-generic x86_64 --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 5 12:05 seq crw-rw 1 root audio 116, 33 Apr 5 12:05 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1 InstallationDate: Installed on 2016-02-20 (409 days ago) InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) IwConfig: lono wireless extensions. eth1 no wireless extensions. eth0 no wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=C SHELL=/bin/bash ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-72-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro ProcVersionSignature: Ubuntu 4.4.0-72.93~14.04.1-generic 4.4.49 RelatedPackageVersions: linux-restricted-modules-4.4.0-72-generic N/A linux-backports-modules-4.4.0-72-generic N/A linux-firmware1.127.23 RfKill: Error: [Errno 2] No such file or directory Tags: trusty Uname: Linux 4.4.0-72-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/26/2012 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v1.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v1.0 dmi.chassis.asset.tag: 5894-4187-8369-8212-0547-2747-15 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v1.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0: dmi.product.name: Virtual Machine dmi.product.version: Hyper-V UEFI Release v1.0 dmi.sys.vendor: Microsoft Corporation --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 10 10:33 seq crw-rw 1 root audio 116, 33 Apr 10 10:33 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1 InstallationDate: Installed on 2016-02-20 (414 days ago) InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) IwConfig: lono wireless extensions. eth1 no wireless
[Group.of.nepali.translators] [Bug 1634753] Re: srcname from mount rule corrupted under load
** Changed in: linux (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1634753
Title:
srcname from mount rule corrupted under load
Status in AppArmor:
Invalid
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Precise:
Invalid
Status in linux source package in Trusty:
Fix Released
Status in linux source package in Xenial:
Fix Released
Status in linux source package in Yakkety:
Invalid
Bug description:
This came up in snapd spread tests but can be reproduced with:
In an i386 up to date 16.04 VM:
1. in one terminal, run this:
$ cat reproducer.sh
#!/bin/sh
set -e
sudo sysctl -w kernel.printk_ratelimit=0
sudo snap install hello-world || true
count=0
while /bin/true ; do
count=$((count+1))
if [ `echo "$count % 100" | bc` -eq 0 ]; then
echo "$count runs"
fi
hello-world > /dev/null || {
tail -100 /var/log/syslog | grep DEN && exit
}
sudo cat /run/snapd/ns/hello-world.mnt 2>/dev/null || sudo
/usr/lib/snapd/snap-discard-ns hello-world
done
2. in another terminal run:
$ while /bin/true ;do sudo apparmor_parser -r /etc/apparmor.d/* >/dev/null
2>&1 ; done
3. In another terminal:
$ tail -f /var/log/syslog|grep DEN
This is not limited to i386.
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1634753/+subscriptions
___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1653162] Re: System won't boot after upgrade to 16.04 with 4.4.0 kernel
** Changed in: linux (Ubuntu) Assignee: Joseph Salisbury (jsalisbury) => (unassigned) ** Changed in: linux (Ubuntu Xenial) Assignee: Joseph Salisbury (jsalisbury) => (unassigned) ** Changed in: linux (Ubuntu Yakkety) Assignee: Joseph Salisbury (jsalisbury) => (unassigned) ** Changed in: linux (Ubuntu Xenial) Status: Incomplete => Invalid ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1653162 Title: System won't boot after upgrade to 16.04 with 4.4.0 kernel Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Status in linux source package in Yakkety: Won't Fix Bug description: I have a Dell PowerEdge 1800 with Dell CERC 1.5/6ch RAID controller in it. Everything worked fine under Ubuntu 14.04.1. When I upgraded to 16.04.1 the system won't boot. It can't find the root filesystem. I see errors about host adapter dead on the screen many times. This is with kernel 4.4.0-57 and with 4.8.0-32. When I switch back to kernel 3.13.0-105 the system boots just fine. I have mptbios 5.06.04. The CERC card says bios version 4.1-0 [Build 7403] When booting into the ercovery kernel I'm getting error messages about host adapter dead. Eventually I get a message: "aacraid: aac_fib_send: first asynchronous command timed out. Usually a result of a PCI interrupt routing problem update moher board BIOS or consider utilizing one of the SAFE mode kernel options (acpi, apic etc)" Using kernel parameter "intel_iommu=on" doesn't help. This was suggested on a post that I saw about these errors. Booting with "noapic" didn't help. Booting with "noapic noacpi" didn't help. I've also tried the dkms modules from Adaptec and that doesn't seem to help either. I can't figure out how to upgrade the firmware or BIOS on the system from Ubuntu either. This may be related to this bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1552551?comments=all --- ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=beec17b5-eac8-4e94-ac99-65b63c428b77 InstallationDate: Installed on 2014-02-24 (1039 days ago) InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) IwConfig: eth1 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Dell Computer Corporation PowerEdge 1800 Package: linux (not installed) ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-105-generic root=UUID=83e1b87e-adb9-4798-a6e0-18d401c91a4a ro nosplash noplymouth ProcVersionSignature: Ubuntu 3.13.0-105.152-generic 3.13.11-ckt39 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-105-generic N/A linux-backports-modules-3.13.0-105-generic N/A linux-firmware 1.157.6 RfKill: Tags: xenial Uname: Linux 3.13.0-105-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-12-25 (3 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/01/2004 dmi.bios.vendor: Dell Computer Corporation dmi.bios.version: A00 dmi.board.name: 0X7500 dmi.board.vendor: Dell Computer Corporation dmi.board.version: A00 dmi.chassis.type: 17 dmi.chassis.vendor: Dell Computer Corporation dmi.modalias: dmi:bvnDellComputerCorporation:bvrA00:bd09/01/2004:svnDellComputerCorporation:pnPowerEdge1800:pvr:rvnDellComputerCorporation:rn0X7500:rvrA00:cvnDellComputerCorporation:ct17:cvr: dmi.product.name: PowerEdge 1800 dmi.sys.vendor: Dell Computer Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1653162/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1685133] Re: Fix RX fail issue on Exar USB serial driver after resume from S3/S4
** Changed in: linux (Ubuntu) Status: Triaged => Fix Released ** Changed in: linux (Ubuntu Bionic) Status: Triaged => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1685133 Title: Fix RX fail issue on Exar USB serial driver after resume from S3/S4 Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux-oem source package in Xenial: Invalid Status in linux source package in Bionic: Fix Released Status in linux-oem source package in Bionic: Fix Released Bug description: Resolution of LP: #1645591 added support for Exar USB UART devices in Ubuntu Xenial kernel. However, the devices fail to RX data after system resumes from suspend-to-ram(S3) and suspend-to-disk(S4). This bug is to track the integration of the driver released by the vendor to fix this issue. Changelog: Version 1B, 11/6/2015 Fixed Bug: The conditional logic to support kernel 3.9 was incorrect(line 396 in xr_usb_serial_common.c). Version 1A, 1/9/2015 This driver will work with any USB UART function in these Exar devices: XR21V1410/1412/1414 XR21B1411 XR21B1420/1422/1424 XR22801/802/804 Exar serial devices are typically enuremated as /dev/ttyXRUSB[0-3] This bug is used for tracking purposes, please do not triage. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1685133/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1794279] Re: please include vc4 modules in pi2-kernel snap initrd
** Also affects: linux-raspi2 (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-raspi2 (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: linux-raspi2 (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1794279 Title: please include vc4 modules in pi2-kernel snap initrd Status in linux-raspi2 package in Ubuntu: New Status in linux-raspi2 source package in Xenial: New Status in linux-raspi2 source package in Bionic: New Status in linux-raspi2 source package in Cosmic: New Bug description: Impact: when using the vc4-kms-v3d devicetree overlay to get accelerated graphics /dev/fb0 is handled by the vc4 driver. since this module does not exist in the initrd currently, using the framebuffer for something like an early splash screen from the initrd is impossible (it works fine when using the vc4-fkms-v3d overlay which hands framebuffer handling back over to the kernel instead, but this sadly results in a completely unaccelerated graphics stack) the list of modules to include is: drm_kms_helper.ko drm.ko drm_mipi_dsi.ko vc4.ko sysimgblt.ko sysfillrect.ko syscopyarea.ko fb_sys_fops.ko i2c-bcm2708.ko Fix: add the i2c-bcm2708.ko to initrd How to test: generate the pi2-kernep snap after applying the below patch, unsquash it, and checks that initrd.img contains all the above kmods (see #2). Regression: None, it's a trivial one-line change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1794279/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1793753] Re: kernel panic - null pointer dereference on ipset operations
I'll try to reproduce this bug. @joel Sing do you happen to have the reproducer script available? In parallel, I'll also build a Xenial test kernel with the commit posted by @Haw Loeung in comment 4 ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => High ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu Xenial) Status: New => Triaged ** Changed in: linux (Ubuntu) Status: Confirmed => Triaged ** Changed in: linux (Ubuntu) Importance: High => Critical ** Changed in: linux (Ubuntu Xenial) Importance: High => Critical ** Tags added: kernel-key -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1793753 Title: kernel panic - null pointer dereference on ipset operations Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: Hi, We've experienced crashes on machines running iptables using ipsets. We could get a trace from the console on one of them (attached file kernel-trace.txt). On these machines, some ipset commands are automatically run to update the sets, and/or to dump them (ipset restore, swap, delete ... / ipset save). We strongly suspect the panic is happening due to a race when ipset updates happen at the same time as a dump. These machines are running xenial. Before the crash, they were on 4.4.0-116-generic #140-Ubuntu, but then rebooted into 4.4.0-135-generic #161-Ubuntu. I have an ipset save running in loops on one of these machines to try and reproduce quicker. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1793753/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1597908] Re: linux-kernel: Freeing IRQ from IRQ context
** Changed in: linux (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1597908 Title: linux-kernel: Freeing IRQ from IRQ context Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Bug description: It looks like the Ubuntu 16.04 took the nvme driver from 4.5 kernel, but is missing some critical block updates that it was depending on. Specifically this one moving the timeout handler to a work queue instead of a irq context timer task: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit?id=287922eb0b186e2a5bf54fdd04b734c25c90035c This mismatch causes lots of warnings and errors during recovery from failure. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1597908/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1791790] Re: Kernel hang on drive pull caused by incomplete backport for bug 1597908
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Status: Confirmed => In Progress ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => High ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1791790 Title: Kernel hang on drive pull caused by incomplete backport for bug 1597908 Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: A bug was introduced when backporting the fix for http://bugs.launchpad.net/bugs/1597908. This bug exists in all Ubuntu 16.04 LTS 4.4 kernels >= 4.4.0-36, and many other non-LTS kernels. This patch changes the context in which timeout work is scheduled for block devices in the kernel. Previously, timeout work was executed directly from the timer callback that fired when a deadline was met. After the patch, timeout work is scheduled using a background work queue. This means that by the time the work executes, the device queue which originally scheduled the work could be torn down. In order to prevent this, the patch takes a reference on the device queue when executing the timeout work. The problem is that the last reference to this queue can be removed before the timeout work can be executed. During teardown, the block system executes a freeze followed by a drain. The freeze drops the last reference on the queue. The drain tries to clean up any outstanding work, including timeout work. After a freeze, the timeout work in the background queue is unable to obtain a reference, and exits early without completing work. The work is now permanently stuck in the queue and it will never be completed. The drain in the device teardown path spins indefinitely. The bug manifests as a hang that looks like this: [] schedule+0x35/0x80 [] hpsa_scan_start+0x109/0x140 [hpsa] [] ? wake_atomic_t_function+0x60/0x60 [] hpsa_rescan_ctlr_worker+0x1d2/0x652 [hpsa] [] process_one_work+0x165/0x480 [] worker_thread+0x4b/0x4c0 [] ? process_one_work+0x480/0x480 [] kthread+0xd8/0xf0 [] ? kthread_create_on_node+0x1e0/0x1e0 [] ret_from_fork+0x3f/0x70 [] ? kthread_create_on_node+0x1e0/0x1e0 The fix exists upstream. It applies, builds, and runs cleanly on Ubuntu's most recent 4.4 kernel. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit?id=4e9b6f20828ac880dbc1fa2fdbafae779473d1af We hit this bug nearly 100% of the time on some of our HP hardware. The HPSA driver has a tendency to aggressively remove missing devices, so it widens the race. As a result, we've been building our own kernel with this patch applied. It would be really nice if we could get it into mainline Ubuntu. Let me know what additional information is needed. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791790/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1783110] Re: >= linux-4.4.0-130: 14 bytes memory leaked when sending AF_PACKET / SOCK_RAW frames
** Changed in: linux (Ubuntu Bionic) Status: Fix Committed => Fix Released ** Changed in: linux (Ubuntu Xenial) Status: Fix Committed => Fix Released ** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1783110 Title: >= linux-4.4.0-130: 14 bytes memory leaked when sending AF_PACKET / SOCK_RAW frames Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Bug description: Vulnerable: linux-image-4.4.0-130-generic, linux-image-4.4.0-131-generic Not vulnerable: linux-image-4.4.0-128-generic Bug (likely) introduced by commit: https://github.com/torvalds/linux/commit/b84bbaf7a6c8cca24f8acf25a2c8e46913a947ba Likely fixed upstream with (NOT VERIFIED): https://github.com/torvalds/linux/commit/9aad13b087ab0a588cd68259de618f100053360e Discussion about these commits on maillist, including someone referring to this bug: https://www.mail-archive.com/search?l=net...@vger.kernel.org=subject:%22Re%5C%3A+%5C%5BPATCH+net%5C%5D+packet%5C%3A+in+packet_snd+start+writing+at+link+layer+allocation%22=newest=1 When sending packets with AF_PACKET / SOCK_RAW, the actual transmitted packet contains 14 additional bytes at the end of the payload. Observations do show non-zero bytes getting leaked. See attached source for a simple proof of concept that sends a raw packet on the loopback interface. The payload should be 40 bytes of 0xAA, but tcpdump clearly shows 14 additional bytes are added. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1783110/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1788563] Re: L1TF mitigation not effective in some CPU and RAM combinations
** Changed in: linux (Ubuntu Cosmic)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1788563
Title:
L1TF mitigation not effective in some CPU and RAM combinations
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Trusty:
Triaged
Status in linux source package in Xenial:
Triaged
Status in linux source package in Bionic:
In Progress
Status in linux source package in Cosmic:
Fix Released
Bug description:
== SRU Justification ==
This regression has been reported in multiple bugs and affects Trust,
Xenial and Bionic. All releases need different backports, so T and X
will be sent in separate SRU requests.
Due to this bug in the original L1TF patch set, L1TF mitigation not
effective in certain CPU and installed RAM configurations.
== Fixes ==
9df9516940a6 ("x86/speculation/l1tf: Fix overflow in l1tf_pfn_limit() on
32bit")
b0a182f87568 ("x86/speculation/l1tf: Fix off-by-one error when warning that
system has too much RAM")
cc51e5428ea5 ("x86/speculation/l1tf: Increase l1tf memory limit for Nehalem+")
== Regression Potential ==
Low. These are security fixes and have all been cc'd to upstream
stable, so they have had additional upstream review.
== Test Case ==
A test kernel was built with these patches and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
Lenovo Thinkpad W530 system with 32 GB RAM
dmesg | grep -i l1tf
[0.038386] L1TF: System has more than MAX_PA/2 memory. L1TF mitigation
not effective.
[ 2652.469669] L1TF CPU bug present and SMT on, data leak possible. See
CVE-2018-3646 and https://www.kernel.org/doc/html/latest/admin-guide/l1tf.html
for details.
Related:
https://bugzilla.opensuse.org/show_bug.cgi?id=1105536
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-32-generic 4.15.0-32.35
ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
Uname: Linux 4.15.0-32-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: pgera 2809 F pulseaudio
CurrentDesktop: Unity:Unity7:ubuntu
Date: Thu Aug 23 03:38:40 2018
InstallationDate: Installed on 2018-08-11 (12 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
MachineType: LENOVO 24382LU
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic
root=UUID=e2607c8a-4bd1-49fe-ad07-83046492fac5 ro quiet splash vt.handoff=1
RelatedPackageVersions:
linux-restricted-modules-4.15.0-32-generic N/A
linux-backports-modules-4.15.0-32-generic N/A
linux-firmware 1.173.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/11/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: G5ETB2WW (2.72 )
dmi.board.asset.tag: Not Available
dmi.board.name: 24382LU
dmi.board.vendor: LENOVO
dmi.board.version: NO DPK
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias:
dmi:bvnLENOVO:bvrG5ETB2WW(2.72):bd06/11/2018:svnLENOVO:pn24382LU:pvrThinkPadW530:rvnLENOVO:rn24382LU:rvrNODPK:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad W530
dmi.product.name: 24382LU
dmi.product.version: ThinkPad W530
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788563/+subscriptions
___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1790788] Re: Customize 'crashkernel' parameter is not properly working
** Also affects: makedumpfile (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: makedumpfile (Ubuntu Cosmic)
Importance: High
Assignee: Thadeu Lima de Souza Cascardo (cascardo)
Status: In Progress
** Also affects: makedumpfile (Ubuntu Xenial)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1790788
Title:
Customize 'crashkernel' parameter is not properly working
Status in makedumpfile package in Ubuntu:
In Progress
Status in makedumpfile source package in Xenial:
New
Status in makedumpfile source package in Bionic:
New
Status in makedumpfile source package in Cosmic:
In Progress
Bug description:
Trying to use crashdump especially in a KVM machine.
Installation looks fine and the reboot is triggered.
But it does not work because the kernel does not have a 'crashkernel='
parameter.
Nothing in /proc/cmdline:
$ cat /proc/cmdline
root=LABEL=cloudimg-rootfs
Issue seems to be in adding the crashkernel line in this snippet:
# Customize crashkernel= value according to architecture
ARCH="$(arch)"
DEF_PRESET="384M-:128M"
case "$ARCH" in
s390x)
HAS_CRASHKERNEL="$(grep crashkernel /etc/zipl.conf)" || true
if test -z "$HAS_CRASHKERNEL"; then
sed -i "/parameters/{s|\"$| crashkernel=${DEF_PRESET}\"|}"
/etc/zipl.conf
zipl
fi
CIO_IGNORE="$(cio_ignore -u -k)"
sed -i "s/\#KDUMP_CMDLINE_APPEND/KDUMP_CMDLINE_APPEND/" $INITCONFFILE
sed -i "/KDUMP_CMDLINE_APPEND/{s|\"$| ${CIO_IGNORE}\"|}"
$INITCONFFILE
;;
esac
(especially 1st sed stmt)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1790788/+subscriptions
___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1790832] Re: crypto/vmx - Backport of Fix sleep-in-atomic bugs patch for 18.04
** Also affects: linux (Ubuntu Cosmic) Importance: High Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Changed in: linux (Ubuntu Cosmic) Status: New => Triaged ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => High ** Changed in: linux (Ubuntu Cosmic) Assignee: Canonical Kernel Team (canonical-kernel-team) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu Cosmic) Status: Triaged => In Progress ** Changed in: linux (Ubuntu Bionic) Status: Triaged => In Progress ** Changed in: linux (Ubuntu Xenial) Status: Triaged => In Progress -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1790832 Title: crypto/vmx - Backport of Fix sleep-in-atomic bugs patch for 18.04 Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Bug description: == Comment: #0 - Paulo Flabiano Smorigo Please include the following commit in order to fix the sleep-in-atomic bugs in AES-CBC and AES-XTS VMX implementations [1]: 0522236 crypto: vmx - Fix sleep-in-atomic bugs [1] https://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6.git/commit/?id=0522236d4f9c5ab2e79889cb020d1acbe5da416e To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1790832/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1790832] Re: crypto/vmx - Backport of Fix sleep-in-atomic bugs patch for 18.04
** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => Triaged ** Changed in: linux (Ubuntu Bionic) Status: Confirmed => Triaged ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1790832 Title: crypto/vmx - Backport of Fix sleep-in-atomic bugs patch for 18.04 Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: New Status in linux source package in Xenial: Triaged Status in linux source package in Bionic: Triaged Bug description: == Comment: #0 - Paulo Flabiano Smorigo Please include the following commit in order to fix the sleep-in-atomic bugs in AES-CBC and AES-XTS VMX implementations [1]: 0522236 crypto: vmx - Fix sleep-in-atomic bugs [1] https://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6.git/commit/?id=0522236d4f9c5ab2e79889cb020d1acbe5da416e To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1790832/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1789653] Re: regression with EXT4 file systems and meta_bg flag
** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Incomplete => Triaged ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Xenial) Status: New => Triaged -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1789653 Title: regression with EXT4 file systems and meta_bg flag Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: Hello, In 16.04 lts (Ubuntu 4.4.0-134.160-generic 4.4.140) with all partitions in ext4 with flag meta_bg : kernel: [ 1905.799557] EXT4-fs (dm-7): ext4_check_descriptors: Block bitmap for group 0 overlaps block group descriptors kernel: [ 1905.799858] EXT4-fs (dm-7): group descriptors corrupted! Go back with the kernel 4.4.0-133-generic and all partitions mount correctly. It looks like this: https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git/commit/?id=44de022c4382541cebdd6de4465d1f4f465ff1dd The patch is available in 4.4.147 (https://lwn.net/Articles/762083/) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1789653/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1788549] Re: powerpc/powernv/pci: Work around races in PCI bridge enabling
** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Critical ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1788549 Title: powerpc/powernv/pci: Work around races in PCI bridge enabling Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Bug description: == Comment: #0 - Michael Ranweiler - 2018-08-21 13:52:03 == +++ This bug was initially created as a clone of Bug #170766 +++ Please apply the following kernel patch: https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=next=db2173198b9513f7add8009f225afa1f1c79bcc6 powerpc/powernv/pci: Work around races in PCI bridge enabling The generic code is racy when multiple children of a PCI bridge try to enable it simultaneously. This leads to drivers trying to access a device through a not-yet-enabled bridge, and this EEH errors under various circumstances when using parallel driver probing. There is work going on to fix that properly in the PCI core but it will take some time. x86 gets away with it because (outside of hotplug), the BIOS enables all the bridges at boot time. This patch does the same thing on powernv by enabling all bridges that have child devices at boot time, thus avoiding subsequent races. It's suitable for backporting to stable and distros, while the proper PCI fix will probably be significantly more invasive. Signed-off-by: Benjamin Herrenschmidt Cc: sta...@vger.kernel.org Signed-off-by: Michael Ellerman == Comment: #2 - Michael Ranweiler - 2018-08-21 18:23:35 == This has some fuzz and also move it back from the pci macro to dev_err so we'll attach the backported patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1788549/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1784535] Re: ubuntu_quota_smoke_test failed with KVM kernel
** Also affects: linux-kvm (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-kvm (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1784535 Title: ubuntu_quota_smoke_test failed with KVM kernel Status in ubuntu-kernel-tests: New Status in linux-kvm package in Ubuntu: New Status in linux-kvm source package in Xenial: New Status in linux-kvm source package in Bionic: New Bug description: According to Kamal's comment: CONFIG_QUOTA (and various other quota-related-looking configs) appear to be enabled already in the linux-kvm kernels -- but the required modules just end up in the regular linux-modules package (e.g. linux-modules-x.y.z-a.b-kvm) However even with the linux-modules-x.y.z-a.b-kvm package installed, this test will still fail with KVM kernel. $ sudo /home/ubuntu/autotest/client/tests/ubuntu_quota_smoke_test/ubuntu_quota_smoke_test.sh Using block device /dev/loop0 for path /home/ubuntu/mnt PASSED (quotacheck -vucmg) quotaon: using /home/ubuntu/mnt/aquota.group on /dev/loop0 [/home/ubuntu/mnt]: No such process quotaon: Quota format not supported in kernel. quotaon: using /home/ubuntu/mnt/aquota.user on /dev/loop0 [/home/ubuntu/mnt]: No such process quotaon: Quota format not supported in kernel. FAILED (quotaon -v) Summary: 1 passed, 1 failed ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1016-kvm 4.15.0-1016.16 ProcVersionSignature: User Name 4.15.0-1016.16-kvm 4.15.18 Uname: Linux 4.15.0-1016-kvm x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jul 31 03:59:45 2018 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1784535/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1747134] Re: [bug] [BDX]Ubuntu 16.04.3 with kernel "4.10.0-32-generic_4.10.0-32.36~16.04.1_amd64" hang if set "Cores Enabled" to 2 for both CPU
** Changed in: linux (Ubuntu Xenial) Status: In Progress => Incomplete ** No longer affects: intel -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1747134 Title: [bug] [BDX]Ubuntu 16.04.3 with kernel "4.10.0-32-generic_4.10.0-32.36~16.04.1_amd64" hang if set "Cores Enabled" to 2 for both CPU Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Incomplete Status in linux source package in Artful: Won't Fix Status in linux source package in Bionic: Fix Released Bug description: Description: Customer report a Ubuntu kernel issue related to Intel BDX Core numbers setting Ubuntu 16.04.3 with kernel "4.10.0-32-generic_4.10.0-32.36~16.04.1_amd64" hang if set "Cores Enabled" to 2 for both CPU. We have reproduced this issue on 17.10 release. With latest kernel, this issue disappears. now we bisect this issue is fixed by commit 947134d9b00f (“x86/smpboot: Do not use smp_num_siblings in __max_logical_packages calculation”) which was merged in v4.15-rc4. But after applying this commit to Ubuntu 16.04.3 kernel v4.13 code base or Linux upstream mainline kernel v4.13 code base, this issue still exists. Target Release: 16.04 / 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1747134/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1751994] Re: ppc64el: Support firmware disable of RFI flush
I confirmed the two requested commits are now in Trusty and Xenial. The commits are in the following versions: Trusty: Ubuntu-3.13.0-149.199 Xenial: Ubuntu-4.4.0-127.153 ** Changed in: linux (Ubuntu Xenial) Status: In Progress => Fix Released ** Changed in: linux (Ubuntu Trusty) Status: In Progress => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1751994 Title: ppc64el: Support firmware disable of RFI flush Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Artful: Invalid Status in linux source package in Bionic: Fix Released Bug description: == Comment: #0 - Breno Leitao - 2018-02-26 13:59:55 == Hi Canonical, We still need some changes regarding spectre and meltdown. We need to backport the following commit to all supported kernel. I undertand that the backport for kernel 4.XX should be trivial. Not sure about kernel 3.13 yet. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=582605a429e20ae68fd0b041b2e840af296edd08 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=eb0a2d2620ae431c543963c8c7f08f597366fc60 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1751994/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1717382] Re: [Bug] Glibc: performance improvement patches
** Changed in: intel Status: New => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1717382 Title: [Bug] Glibc: performance improvement patches Status in GLibC: Fix Released Status in intel: Fix Released Status in glibc package in Ubuntu: Fix Released Status in glibc source package in Xenial: Confirmed Status in glibc source package in Zesty: Confirmed Status in glibc source package in Artful: Fix Released Bug description: Description: Intel’s new request – for performance related patches that need to be picked up as part of one the Ubuntu 16.04 LTS family releases and Ubuntu 17.10: Glibc 2.23 needs the first 2 patches on hjl/pr21258/2.23 branch: https://sourceware.org/git/gitweb.cgi?p=glibc.git;a=shortlog;h=refs/heads/hjl/pr21258/2.23 Patches: Address transition penalty when SSE instructions are mixed with 256-bit AVX or 512-bit AVX512 load instructions. Target Release: TBD To manage notifications about this bug go to: https://bugs.launchpad.net/glibc/+bug/1717382/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1783241] Re: [HMS] Upgrades to Support SocketCAN over USB on Dell IoT 300x Gateways
** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Critical ** Changed in: linux (Ubuntu Xenial) Status: New => Confirmed ** Tags added: kernel-da-key xenial -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1783241 Title: [HMS] Upgrades to Support SocketCAN over USB on Dell IoT 300x Gateways Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Bug description: Several scheduled upgrades to the HMS SocketCAN protocol driver over USB->CAN interface are required. SocketCAN support for USB->CAN devices was introduced in Ubuntu Xenial LTS kernel through following patch (BugLink: http://bugs.launchpad.net/bugs/1774563): cddf58207a3c UBUNTU: SAUCE: (no-up) Support IXXAT USB SocketCAN device == SRU Justification == The scheduled upgrades include following changes: - support adapters for CL1 (Communication Layer for legacy devices) and CL2 (current devices) - removed CAN-IDM100 support (Microchip Rev A microcontroller) - add CAN-IDM101 support (Microchip Rev B microcontroller) - add Error-Passive recognition - move CAN message handling to the core module - use ktime API for timestamps - fixes Linux kernel coding style issues == Fix == UBUNTU: SAUCE: (no-up) upgrade IXXAT USB SocketCAN driver == Regression Potential == Low. The driver will be built only for amd64 kernels and attach itself to IXXAT USB-CAN adapters with VID 0x08d8. Also, patches from the vendor (HMS) have already been tested by Dell/ODM, Canonical QA on Dell 300x Edge IoT gateways. This bug is for tracking purposes only, please do not triage. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1783241/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1771439] Re: [LTC Test] Ubuntu 18.04: tm_sigreturn failed on P8 compat mode 16.04.04 guest
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1771439
Title:
[LTC Test] Ubuntu 18.04: tm_sigreturn failed on P8 compat mode
16.04.04 guest
Status in The Ubuntu-power-systems project:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Fix Released
Bug description:
== SRU Justification ==
IBM is seeing tm_sigreturn test failures on P8 and P9 hosts. The bad thing
exception is being raised when executing the following line:
c004fcfc: b0 04 03 e8 ld r0,1200(r3)
-> c004fd00: a6 23 02 7c mtspr 130,r0
Which is basically restoring TEXASR in the thread.
ISA says "These registers can be written only when in Non-transactional
state" and the MSR is set to be transactional (suspended):
MSR: 800300201033 [ME][RI][IR][DR][LE][SF][HTM][TSU]
That explains why they are getting the "bad thing exception". A mtspr is
being called with a transaction suspended.
This test failure is fixed by upstream commit 78a3e8889b4b.
Upstream commit 78a3e8889b4b is in mainline as of 4.8-rc5.
== Fix ==
78a3e8889b4b ("powerpc: signals: Discard transaction state from signal
frames")
== Regression Potential ==
Low. Specific to powerpc.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
This test fails in the same way on a P8 host, so it is nothing to do with P9.
There have been many TM bugs fixed upstream since 4.4. I would suggest
starting with commit 044215d145a7 ("powerpc/tm: Fix illegal TM state
in signal handler", 2017-08-22) and see if that helps.
The bad thing exception is being raised when executing the following
line:
c004fcfc: b0 04 03 e8 ld r0,1200(r3)
-> c004fd00: a6 23 02 7c mtspr 130,r0
Which is basically restoring TEXASR in the thread.
ISA says "These registers can be written only when in Non-
transactional state" and the MSR is set to be transactional
(suspended):
MSR: 800300201033 [ME][RI][IR][DR][LE][SF][HTM][TSU]
That explains why we are getting the "bad thing exception". A mtspr is
being called with a transaction suspended.
I think we need the following commit to have this fixed:
commit 78a3e8889b4b6b99775ed954696ff3e017f5d19b
Author: Cyril Bur
Date: Tue Aug 23 10:46:17 2016 +1000
powerpc: signals: Discard transaction state from signal frames
Userspace can begin and suspend a transaction within the signal
handler which means they might enter sys_rt_sigreturn() with the
processor in suspended state.
sys_rt_sigreturn() wants to restore process context (which may have
been in a transaction before signal delivery). To do this it must
restore TM SPRS. To achieve this, any transaction initiated within the
signal frame must be discarded in order to be able to restore TM SPRs
as TM SPRs can only be manipulated non-transactionally..
>From the PowerPC ISA:
TM Bad Thing Exception [Category: Transactional Memory]
An attempt is made to execute a mtspr targeting a TM register in
other than Non-transactional state.
Not doing so results in a TM Bad Thing:
[12045.221359] Kernel BUG at c0050a40 [verbose debug info
unavailable]
[12045.221470] Unexpected TM Bad Thing exception at c0050a40 (msr
0x201033)
[12045.221540] Oops: Unrecoverable exception, sig: 6 [#1]
[12045.221586] SMP NR_CPUS=2048 NUMA PowerNV
[12045.221634] Modules linked in: xt_CHECKSUM iptable_mangle
ipt_MASQUERADE
nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4
nf_defrag_ipv4
xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp
llc ebtable_filter
ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables
kvm_hv kvm
uio_pdrv_genirq ipmi_powernv uio powernv_rng ipmi_msghandler autofs4 ses
enclosure
scsi_transport_sas bnx2x ipr mdio libcrc32c
[12045.222167] CPU: 68 PID: 6178 Comm: sigreturnpanic Not tainted 4.7.0
#34
[12045.24] task: c000fce38600 ti: c000fceb4000 task.ti:
c000fceb4000
[12045.93] NIP: c0050a40 LR: c00163bc CTR:
[12045.222361] REGS: c000fceb7ac0 TRAP: 0700 Not tainted (4.7.0)
[12045.222418] MSR: 900300201033 CR:
28444280 XER: 2000
[12045.222625] CFAR: c00163b8 SOFTE: 0 PACATMSCRATCH:
90014280f033
GPR00: 0110b801 c000fceb7d40 c139c100 c000fce390d0
GPR04: 90034280f033
[Group.of.nepali.translators] [Bug 1782544] Re: tcpreplay and veth device; extra transmit bytes on 4.4.0-130-generic kernel
Would it be possible for you to test the latest upstream stable kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.4 stable kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.141 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => Incomplete ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Medium -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1782544 Title: tcpreplay and veth device; extra transmit bytes on 4.4.0-130-generic kernel Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Incomplete Bug description: Issue found in a test harness for some code running on Ubuntu 16.04.4 LTS where we use a veth device to play in packets to the code under test. Essentially we see an extra 14 bytes being transmitted at the end of every packet that is just random garbage. Problem came in with the 4.4.0-130 kernel; if I revert to the 4.4.0-128 kernel the issue goes away. I have verified the issue on several different boxes running 16.04 The following steps reproduce the problem: 1) Veth setup sudo ip link add name nic1 type veth peer name nic2 sudo sysctl -q -w net.ipv6.conf.nic1.disable_ipv6=1 sudo sysctl -q -w net.ipv6.conf.nic2.disable_ipv6=1 sudo ip link set nic1 up sudo ip link set nic2 up 2) Configure tcpdump to collect packets on one interface: sudo tcpdump -i nic1 -w outPkts.pcap 3) Play in packets on the other (Any pcap will do): sudo tcpreplay -q -i nic2 inPkts.pcap When I check ifconfig I can see nic2/nic1 transmitting/receiving more bytes than expected. Opening the capture seen by tcpdump shows an extra 14 bytes received for every packet when compared to the input. tcpreplay version info: tcpreplay version: 3.4.4 (build 2450) (debug) Copyright 2000-2010 by Aaron Turner Cache file supported: 04 Not compiled with libdnet. Compiled against libpcap: 1.7.4 64 bit packet counters: enabled Verbose printing via tcpdump: enabled Packet editing: disabled Fragroute engine: disabled Injection method: PF_PACKET send() tcpdump version info tcpdump version 4.9.2 libpcap version 1.7.4 OpenSSL 1.0.2g 1 Mar 2016 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-130-generic 4.4.0-130.156 ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134 Uname: Linux 4.4.0-130-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: spw3336 F pulseaudio /dev/snd/controlC0: spw3336 F pulseaudio CurrentDesktop: Unity Date: Thu Jul 19 10:30:07 2018 HibernationDevice: RESUME=UUID=032369ab-18b8-41c3-a386-4ed08706f461 InstallationDate: Installed on 2016-11-03 (622 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. OptiPlex 7010 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-130-generic root=UUID=7b20f97c-4edc-4af1-bdbb-72ccb26cfbec ro quiet splash intel_iommu=on RelatedPackageVersions: linux-restricted-modules-4.4.0-130-generic N/A linux-backports-modules-4.4.0-130-generic N/A linux-firmware 1.157.20 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 0KRC95 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd08/12/2013:svnDellInc.:pnOptiPlex7010:pvr01:rvnDellInc.:rn0KRC95:rvrA02:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 7010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782544/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to :
[Group.of.nepali.translators] [Bug 1781535] Re: qdio: don't retry EQBS after CCQ 96
The requested commit is in Bionic as of Ubuntu-4.15.0-23.25~80: 25dbc82 s390/qdio: don't retry EQBS after CCQ 96 The requested commit is in Xenial as of Ubuntu-4.4.0-128.154~221: e26f413 s390/qdio: don't retry EQBS after CCQ 96 ** Changed in: linux (Ubuntu Xenial) Status: In Progress => Fix Released ** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1781535 Title: qdio: don't retry EQBS after CCQ 96 Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Status in linux source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Bug description: Description: qdio: don't retry EQBS after CCQ 96 Symptom: Queue stalls, over-/underreporting of buffer errors. Problem: Immediate retry of EQBS after CCQ 96 means that we potentially misreport the state of buffers inspected during the first EQBS call. Solution: On CCQ 96, first process the discovered state. Afterwards, higher-level code will eventually trigger an EQBS/inspection of the remaining buffers. Their state is now processed independently from the state that was discovered during the first EQBS. Upstream-ID: dae55b6fef58530c13df074bcc182c096609339e To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1781535/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1781535] Re: qdio: don't retry EQBS after CCQ 96
** No longer affects: linux (Ubuntu Trusty) -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1781535 Title: qdio: don't retry EQBS after CCQ 96 Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Bug description: Description: qdio: don't retry EQBS after CCQ 96 Symptom: Queue stalls, over-/underreporting of buffer errors. Problem: Immediate retry of EQBS after CCQ 96 means that we potentially misreport the state of buffers inspected during the first EQBS call. Solution: On CCQ 96, first process the discovered state. Afterwards, higher-level code will eventually trigger an EQBS/inspection of the remaining buffers. Their state is now processed independently from the state that was discovered during the first EQBS. Upstream-ID: dae55b6fef58530c13df074bcc182c096609339e To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1781535/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1780761] Re: kernel 4.4.0-130-generic - packet loss with ip forward
** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Xenial) Status: New => Incomplete ** Changed in: linux (Ubuntu Xenial) Status: Incomplete => Triaged ** Changed in: linux (Ubuntu) Status: Incomplete => Triaged -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1780761 Title: kernel 4.4.0-130-generic - packet loss with ip forward Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: Reproduced with 16.04.4 LTS and Citrix Xenserver 7.0, 7.1, 7.4. Some packet loss is observed after upgrading to 4.4.0-130-generic when the traffic is routed via VM. Steps to reproduce: 1) Using Citrix Xenserver, set up Ubuntu server VM, upgrade to 4.4.0-130-generic 2) Enable IP forwarding 3) Send any traffic via this VM (for ex. icmp ping) 4) Packets leaving the VM may not reach the second VM on the same physical host or not leave the physical host machine 5) Packets coming to a physical host machine interface may not reach the virtual machine Rollback to 4.4.0-128-generic helps. A file with tcpdump results and a brief explanation is attached. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-130-generic 4.4.0-130.156 ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134 Uname: Linux 4.4.0-130-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 9 11:24 seq crw-rw 1 root audio 116, 33 Jul 9 11:24 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Mon Jul 9 13:18:47 2018 InstallationDate: Installed on 2018-06-04 (34 days ago) InstallationMedia: Ubuntu-Server 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.8) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Xen HVM domU PciMultimedia: ProcEnviron: LANGUAGE=en_US:en TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-130-generic root=UUID=46979d34-98b0-470f-9f1f-29147de9f253 ro ipv6.disable=1 net.ifnames=0 biosdevname=0 RelatedPackageVersions: linux-restricted-modules-4.4.0-130-generic N/A linux-backports-modules-4.4.0-130-generic N/A linux-firmware 1.157.19 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/14/2018 dmi.bios.vendor: Xen dmi.bios.version: 4.7.5-4.4 dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.7.5-4.4:bd06/14/2018:svnXen:pnHVMdomU:pvr4.7.5-4.4:cvnXen:ct1:cvr: dmi.product.name: HVM domU dmi.product.version: 4.7.5-4.4 dmi.sys.vendor: Xen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780761/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1779830] Re: vfio/pci: cannot assign a i40e pf device to a vm using vfio-pci
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu Xenial)
Status: Triaged => In Progress
** Changed in: linux (Ubuntu)
Status: Triaged => Invalid
** Changed in: linux (Ubuntu)
Status: Invalid => In Progress
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1779830
Title:
vfio/pci: cannot assign a i40e pf device to a vm using vfio-pci
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
In Progress
Bug description:
The following upstream patch (v4.7) is missing in xenial:
450744051d20 ("vfio/pci: Hide broken INTx support from user")
http://scm/kernels/linux-upstream/commit/?id=450744051d20
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779830/+subscriptions
___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1780227] Re: locking sockets broken due to missing AppArmor socket mediation patches
** Changed in: linux (Ubuntu) Status: Confirmed => Triaged ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => Triaged ** Changed in: linux (Ubuntu Bionic) Status: New => Triaged ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => High ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => High ** Tags added: bionic kernel-da-key xenial -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1780227 Title: locking sockets broken due to missing AppArmor socket mediation patches Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Status in linux source package in Bionic: Triaged Bug description: Hey, Newer systemd makes use of locks placed on AF_UNIX sockets created with the socketpair() syscall to synchronize various bits and pieces when isolating services. On kernels prior to 4.18 that do not have backported the AppArmor socket mediation patchset this will cause the locks to be denied with EACCESS. This causes systemd to be broken in LXC and LXD containers that do not run unconfined which is a pretty big deal. We have seen various bug reports related to this. See for example [1] and [2]. If feasible it would be excellent if we could backport the socket mediation patchset to all LTS kernels. Afaict, this should be 4.4 and 4.15. This will unbreak a whole range of use-cases. The socket mediation patchset is available here: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=80a17a5f501ea048d86f81d629c94062b76610d4 [1]: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1575779 [2]: https://github.com/systemd/systemd/issues/9493 Thanks! Christian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780227/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1779830] Re: vfio/pci: cannot assign a i40e pf device to a vm using vfio-pci
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: Incomplete => Triaged
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Status: New => Triaged
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => Medium
** Tags added: kernel-da-key xenial
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1779830
Title:
vfio/pci: cannot assign a i40e pf device to a vm using vfio-pci
Status in linux package in Ubuntu:
Triaged
Status in linux source package in Xenial:
Triaged
Bug description:
The following upstream patch (v4.7) is missing in xenial:
450744051d20 ("vfio/pci: Hide broken INTx support from user")
http://scm/kernels/linux-upstream/commit/?id=450744051d20
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779830/+subscriptions
___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1778705] Re: skey in ubuntu-kvm-unit-test failed on Xenial zVM
** Changed in: linux (Ubuntu) Status: Incomplete => Triaged ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => Triaged ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Medium -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1778705 Title: skey in ubuntu-kvm-unit-test failed on Xenial zVM Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: TESTNAME=skey TIMEOUT=90s ACCEL= ./s390x/run s390x/skey.elf -smp 1 FAIL skey (2 tests) This is the only failure in this test suite on Xenial zVM, need to run it manually to see what's going on. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-130-generic 4.4.0-130.156 ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134 Uname: Linux 4.4.0-130-generic s390x NonfreeKernelModules: zfs zunicode zcommon znvpair zavl AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.18 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDmesg: [ 3288.479241] audit_printk_skb: 153 callbacks suppressed [ 3288.479246] audit: type=1400 audit(1530011067.825:63): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/snapd/snap-confine" pid=6480 comm="apparmor_parser" [ 3288.510095] audit: type=1400 audit(1530011067.865:64): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/snapd/snap-confine//mount-namespace-capture-helper" pid=6480 comm="apparmor_parser" Date: Tue Jun 26 07:05:34 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=UUID=44b0b919-a1a4-4849-9425-e71d4ac87d85 crashkernel=196M nobp=1 BOOT_IMAGE=0 RelatedPackageVersions: linux-restricted-modules-4.4.0-130-generic N/A linux-backports-modules-4.4.0-130-generic N/A linux-firmware 1.157.19 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1778705/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1763685] Re: Fix for flushing TM on coredump only if CPU has TM feature
Now that I review this again, I don't think commit
c1fa0768a8713b135848f78fd43ffc208d8ded70 is needed in Xenial proper, since it
is 4.4 based. Commit c1fa0768a871 fixes the following commit:
cd63f3c ("powerpc/tm: Fix saving of TM SPRs in core dump")
However, commit cd63f3c was not added to mainline until v4.13-rc4.
Can you confirm this? If commit c1fa0768a871 is not needed in Xenial,
there is nothing to test and this bug should be resolved since it's
specific to Artful and Xenial HWE kerenl(4.13 based).
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => Invalid
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1763685
Title:
Fix for flushing TM on coredump only if CPU has TM feature
Status in The Ubuntu-power-systems project:
In Progress
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Invalid
Status in linux source package in Artful:
Fix Released
Bug description:
Problem description
==
Fix for flushing TM on coredump only if CPU has TM feature
---Additional Hardware Info---
POWER9/POWER8/compat mode
Machine Type = P9 baremetal + VM (POWER9, POWER8, Compat mode)
---Steps to Reproduce---
On POWER9 machines it's possible that TM is disabled for use by the VMs and
if a coredump is generated in the VM it will crash since it will execute TM
instructions when coredumping if a check is not present on the VM's kernel.
Since POWER9 can run VM on P8 compatibility mode, it's necessary to patch all
kernels that run on compat mode as well.
Stack trace output:
na
Oops output:
PID: 16438 TASK: c00272f515e0 CPU: 3 COMMAND: "vma05_vdso"
#0 [c002711f7050] crash_kexec at c01a07e4
#1 [c002711f7080] die at c0025278
#2 [c002711f7120] _exception at c0025594
#3 [c002711f72b0] program_check_exception at c0a0e1b8
#4 [c002711f7330] program_check_common at c0006308
Program Check [700] exception frame:
R0: R1: c002711f7620R2: c1274700
R3: c00272f51af0R4: 80010280b033R5:
R6: 0100R7: R8:
R9: 0002R10: R11:
R12: c0010720R13: c7b81b00R14:
R15: R16: c002711f7db0R17: 00040006
R18: c0002ab95800R19: 0100R20: 0001
R21: 0002R22: c0bfc1c8R23: c002711f79b8
R24: c0a30480R25: c0a30478R26: 0018
R27: R28: c0002ab95800R29:
R30: 0100R31: c00272f515e0
NIP: c005b10cMSR: 80010288b033OR3: c00108e0
CTR: c0010720LR: c00108e4XER: 2000
CCR: 28002448MQ: 0001DAR: c00275599748
DSISR: c00274092988 Syscall Result:
#5 [c002711f7620] tm_save_sprs at c005b10c
[Link Register] [c002711f7620] vsr_get at c00108e4
#6 [c002711f7770] fill_thread_core_info at c03d8b44
#7 [c002711f7820] fill_note_info at c03d8e94
#8 [c002711f78b0] elf_core_dump at c03d94d4
#9 [c002711f7a90] do_coredump at c03dfcf4
#10 [c002711f7c20] get_signal_to_deliver at c01061d4
#11 [c002711f7d10] do_signal at c001beac
#12 [c002711f7e00] do_notify_resume at c001c2cc
#13 [c002711f7e30] ret_from_except_lite at c000a7b0
System Call [c00] exception frame:
R0: 00faR1: 3fffd0470f00R2: 3fffa8af7f00
R3: R4: 4036R5: 000b
R6: 3fffd0471428R7: 1770R8: 4036
R9: R10: R11:
R12: R13: 3fffa8babb80R14:
R15: R16: R17:
R18: R19: R20:
R21: R22: R23:
R24: R25: R26:
R27: 3fffa8b9fbb8R28: 3fffa8baR29: 3fffa8b9f550
R30: R31:
NIP: 3fffa8ad54c8MSR: 8000d033OR3: 4036
CTR: LR: 155cXER:
CCR: 42000442MQ: 0001DAR: 3fffa89b2100
DSISR: 4000
[Group.of.nepali.translators] [Bug 1776879] Re: system hangs on boot at "Cryptography Setup for cryptswap1"
Would it be possible for you to test the latest upstream stable kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.4 stable kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.137 ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => High ** Changed in: linux (Ubuntu Xenial) Status: New => Incomplete ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Tags added: kernel-da-key -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1776879 Title: system hangs on boot at "Cryptography Setup for cryptswap1" Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Incomplete Bug description: Hi, I have updated my kubuntu from 4.4.0-127-generic to 4.4.0-128-generic. When I try to boot with the new kernel, the system hangs during the Flash-Screen. When I try booting in recovery mode, I can see, that the boot hangs with the following message: Dependency failed for Cryptography Setup for cryptswap1 Dependency failed for Encrypted Volumes Dependency failed for dev-mapper-cryptswap1.device Dependency failed for /dev/mapper/cryptswap1 Dependency failed for Swap Dependency failed for /dev/disk/by-uuid/fea3e83b-933d-49fc-a3d0-88448a0b7871 When I boot with the old kernel everything works fine. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-127-generic 4.4.0-127.153 ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128 Uname: Linux 4.4.0-127-generic i686 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: leon 2229 F pulseaudio /dev/snd/controlC0: leon 2229 F pulseaudio CurrentDesktop: KDE Date: Thu Jun 14 11:57:45 2018 EcryptfsInUse: Yes HibernationDevice: #RESUME=/dev/sda5 #RESUME=UUID="4eeadd76-5400-4026-994f-7a27deaf56d2" RESUME=UUID="fea3e83b-933d-49fc-a3d0-88448a0b7871" InstallationDate: Installed on 2016-01-25 (870 days ago) InstallationMedia: Kubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805) MachineType: Acer Aspire V3-371 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-127-generic root=UUID=f42e701d-6b34-4d69-b115-e5c9b6c2fed6 ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.4.0-127-generic N/A linux-backports-modules-4.4.0-127-generic N/A linux-firmware 1.157.19 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/21/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.28 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire V3-371 dmi.board.vendor: Acer dmi.board.version: V1.28 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.28 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.28:bd08/21/2015:svnAcer:pnAspireV3-371:pvrV1.28:rvnAcer:rnAspireV3-371:rvrV1.28:cvnAcer:ct10:cvrV1.28: dmi.product.name: Aspire V3-371 dmi.product.version: V1.28 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776879/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1776005] Re: kernel instability with BTRFS filesystem as rootfs
** Changed in: linux (Ubuntu) Importance: Undecided => High ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux (Ubuntu) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => High ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1776005 Title: kernel instability with BTRFS filesystem as rootfs Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: Hello, As explained yesterday on #ubuntu-kernel, several laptop won't boot (kernel panic) with the latest kernel 4.4.0-127-generic (x86_64) and upper (proposed 4.4.0-128-generic), on Xenial 16.04 LTS I have made many tests to verify that the bootloader (GRUB) is correctly configured (I have also reinstall it, but same result). I have also verified the BTRFS system is clean and not corrupted (with a livecd). The behavior is unpredictable, because often the kernel fall in "panic" during boot, but not all the time, if i do several consecutive reboot to test stability of the boot "process". I have no search behavior with previous kernels (like 4.4.0-124-generic). I suspect (even if I'm quiet disturbed by this behavior, maybe I wrong) that something I changed on last kernel: - on BTRFS subsystem, I have "aggregate" BTRFS partitions as rootfs (for a long time) - something related with the last mitigation about the recent security processor breach But my skills stop here, and I'm not able to find the origin of this behavior despite my efforts. I can continue my investigation if I have some additional pointers. Thanks for your time, Sylvain To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776005/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1775527] Re: Ubuntu16.04:KVM - xfs_log_force: error -5 returned after stress test running after a day #345
I'll mark this bug incomplete until there are test results using the
latest Xenial 4.4 kernel.
** Tags added: kernel-da-key
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New => Incomplete
** Changed in: linux (Ubuntu Xenial)
Status: New => Incomplete
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => High
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1775527
Title:
Ubuntu16.04:KVM - xfs_log_force: error -5 returned after stress test
running after a day #345
Status in The Ubuntu-power-systems project:
Triaged
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Xenial:
Incomplete
Bug description:
== Comment: #0 - Chanh H. Nguyen - 2016-09-08 15:01:30
==
We have installed 16.04.1 on our guest and running IO stress test against via
virtual qlogic disk. After running around 8 hrs, this error popping up
"xfs_imap_to_bp: xfs_trans_read_buf() returned error -5" then with all of these
errors "xfs_log_force: error -5 returned" fill up all the log.
Jul 19 19:03:41 tinyg2 kernel: [65047.974604] XFS (vdb9): metadata I/O error:
block 0x2f140 ("xfs_trans_read_buf_map") error 5 numblks 32
Jul 19 19:03:41 tinyg2 kernel: [65047.975885] XFS (vdb9): xfs_imap_to_bp:
xfs_trans_read_buf() returned error -5.
Jul 19 19:03:41 tinyg2 kernel: [65047.976069] XFS (vdb9):
xfs_do_force_shutdown(0x8) called from line 3433 of file
/build/linux-JQcyrX/linux-4.4.0/fs/xfs/xfs_inode.c. Return address =
0xd37951f4
Jul 19 19:03:41 tinyg2 kernel: [65047.976457] XFS (vdb9): metadata I/O error:
block 0x703d54 ("xlog_iodone") error 5 numblks 64
Jul 19 19:03:41 tinyg2 kernel: [65047.976662] XFS (vdb9):
xfs_do_force_shutdown(0x2) called from line 1197 of file
/build/linux-JQcyrX/linux-4.4.0/fs/xfs/xfs_log.c. Return address =
0xd37a4c00
Jul 19 19:03:41 tinyg2 kernel: [65047.976995] XFS (vdb9): Log I/O Error
Detected. Shutting down filesystem
Jul 19 19:03:41 tinyg2 kernel: [65047.977114] XFS (vdb9): Please umount the
filesystem and rectify the problem(s)
follow with all of these error that quickly fill up dmesg log
Jul 19 19:04:37 tinyg2 kernel: [65103.515386] XFS (vdb9): xfs_log_force:
error -5 returned.
Jul 19 19:05:07 tinyg2 kernel: [65133.595369] XFS (vdb9): xfs_log_force:
error -5 returned.
Jul 19 19:05:37 tinyg2 kernel: [65163.679358] XFS (vdb9): xfs_log_force:
error -5 returned.
Jul 19 19:06:07 tinyg2 kernel: [65193.755383] XFS (vdb9): xfs_log_force:
error -5 returned.
Jul 19 19:06:37 tinyg2 kernel: [65223.835396] XFS (vdb9): xfs_log_force:
error -5 returned.
Jul 19 19:06:51 tinyg2 kernel: [65237.091455] EXT4-fs (loop1): mounting ext2
file system using the ext4 subsystem
Jul 19 19:06:51 tinyg2 kernel: [65237.093219] EXT4-fs (loop1): mounted
filesystem without journal. Opts: (null)
Jul 19 19:06:51 tinyg2 kernel: [65237.623893] Process accounting resumed
Jul 19 19:07:07 tinyg2 kernel: [65253.919361] XFS (vdb9): xfs_log_force:
error -5 returned.
Jul 19 19:07:37 tinyg2 kernel: [65283.995393] XFS (vdb9): xfs_log_force:
error -5 returned.
Jul 19 19:08:08 tinyg2 kernel: [65314.075378] XFS (vdb9): xfs_log_force:
error -5 returned.
Jul 19 19:08:38 tinyg2 kernel: [65344.155397] XFS (vdb9): xfs_log_force:
error -5 returned.
Jul 19 19:09:08 tinyg2 kernel: [65374.235367] XFS (vdb9): xfs_log_force:
error -5 returned.
Jul 19 19:09:38 tinyg2 kernel: [65404.319354] XFS (vdb9): xfs_log_force:
error -5 returned.
Jul 19 19:10:08 tinyg2 kernel: [65434.395368] XFS (vdb9): xfs_log_force:
error -5 returned.
== Comment: #1 - Chanh H. Nguyen - 2016-09-08 15:02:27
==
We recently re-created this bug on our new system "cressg2" which is using a
different SAN on kernel -36.
My Ubuntu 16.04.1 guest, cressg2, are running the IO and other stress test,
and it is hitting "xfs_log_force: error -5 returned" problem after it runs the
tests for 15 hours. It is using our lab storage (SVC SAN storage configuation
with access to DS8000 Volume) and switch, compare to tinyg3, so it is using
different storage and fabric switch.
root@cressg2:~# uname -a
Linux cressg2 4.4.0-36-generic #55-Ubuntu SMP Thu Aug 11 18:00:57 UTC 2016
ppc64le ppc64le ppc64le GNU/Linux
[Wed Sep 7 10:26:48 2016] XFS (vdb8): xfs_log_force: error -5 returned.
[Wed Sep 7 10:27:18 2016] XFS (vdb8): xfs_log_force: error -5 returned.
[Wed Sep 7 10:27:32 2016] XFS (vdb8): xfs_log_force: error -5 returned.
[Wed Sep 7 10:27:33 2016] XFS (vdb8): xfs_log_force: error -5 returned.
[Wed Sep 7 10:27:33 2016] XFS (vdb8): xfs_log_force: error -5 returned.
[Wed Sep 7 10:27:48 2016] XFS (vdb8): xfs_log_force: error -5 returned.
[Group.of.nepali.translators] [Bug 1775784] Re: inotify08 in LTP syscall test failed with X/X-LTS/X-HWE/A/B kernel
** Also affects: linux (Ubuntu Artful) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Artful) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Xenial) Status: New => Triaged ** Changed in: linux (Ubuntu Artful) Status: New => Triaged ** Changed in: linux (Ubuntu Bionic) Status: New => Triaged ** Changed in: linux (Ubuntu) Status: Incomplete => Triaged ** Changed in: linux (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1775784 Title: inotify08 in LTP syscall test failed with X/X-LTS/X-HWE/A/B kernel Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Status in linux source package in Artful: Triaged Status in linux source package in Bionic: Triaged Bug description: <<>> tag=inotify08 stime=1527762360 cmdline="inotify08" contacts="" analysis=exit <<>> incrementing stop tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s inotify08.c:201: INFO: ovl/test_file ino=27918358, dev=8:1 inotify08.c:212: INFO: ovl/test_file ino=27918363, dev=8:1 inotify08.c:150: FAIL: didn't get event: mask=4 inotify08.c:150: FAIL: didn't get event: mask=20 inotify08.c:150: FAIL: didn't get event: mask=8 Summary: passed 0 failed 3 skipped 0 warnings 0 <<>> initiation_status="ok" duration=1 termination_type=exited termination_id=1 corefile=no cutime=0 cstime=0 <<>> ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.15.0-22-generic 4.15.0-22.24~16.04.1 ProcVersionSignature: User Name 4.15.0-22.24~16.04.1-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Fri Jun 8 08:08:27 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-edge UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1775784/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1775235] Re: Ubuntu 16.04 (4.4.0-127) hangs on boot with virtio-scsi MQ enabled
I built a test kernel with the patch you posted in the description. The test
kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1775235
Can you test this kernel and see if it resolves this bug?
Note about installing test kernels:
• If the test kernel is prior to 4.15(Bionic) you need to install the
linux-image and linux-image-extra .deb packages.
• If the test kernel is 4.15(Bionic) or newer, you need to install the
linux-modules, linux-modules-extra and linux-image-unsigned .deb packages.
Thanks in advance!
** Changed in: linux (Ubuntu Xenial)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu)
Status: In Progress => Invalid
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1775235
Title:
Ubuntu 16.04 (4.4.0-127) hangs on boot with virtio-scsi MQ enabled
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Xenial:
In Progress
Bug description:
We noticed that Ubuntu 16.04 guests running on Nutanix AHV stopped
booting after they were upgraded to the latest kernel (4.4.0-127).
Only guests with scsi mq enabled suffered from this problem. AHV is
one of the few hypervisor products to offer multiqueue for virtio-scsi
devices.
Upon further investigation, we could see that the kernel would hang
during the scanning of scsi targets. More specifically, immediately
after coming across a target without any luns present. That's the
first time the kernel destroys a target (given it doesn't have luns).
This could be confirmed with gdb (attached to qemu's gdbserver):
#0 0xc0045039 in ?? ()
#1 0x88022c753c98 in ?? ()
#2 0x815d1de6 in scsi_target_destroy (starget=0x88022ad62400)
at /build/linux-E14mqW/linux-4.4.0/drivers/scsi/scsi_scan.c:322
This shows the guest vCPU stuck on virtio-scsi's implementation of
target_destroy. Despite lacking symbols, we managed to examine the
virtio_scsi_target_state to see that the 'reqs' counter was invalid:
(gdb) p *(struct virtio_scsi_target_state *)starget->hostdata
$6 = {tgt_seq = {sequence = 0}, reqs = {counter = -1}, req_vq =
0x88022cbdd9e8}
(gdb)
This drew our attention to the following patch which is exclusive to the
Ubuntu kernel:
commit f1f609d8015e1d34d39458924dcd9524fccd4307
Author: Jay Vosburgh
Date: Thu Apr 19 21:40:00 2018 +0200
In a nutshell, the patch spins on the target's 'reqs' counter waiting for the
target to quiesce:
--- a/drivers/scsi/virtio_scsi.c
+++ b/drivers/scsi/virtio_scsi.c
@@ -785,6 +785,10 @@ static int virtscsi_target_alloc(struct scsi_target
*starget)
static void virtscsi_target_destroy(struct scsi_target *starget)
{
struct virtio_scsi_target_state *tgt = starget->hostdata;
+
+ /* we can race with concurrent virtscsi_complete_cmd */
+ while (atomic_read(>reqs))
+ cpu_relax();
kfree(tgt);
}
Personally, I think this is a catastrophic way of waiting for a target
to quiesce since virtscsi_target_destroy() is called with IRQs
disabled from scsi_scan.c:scsi_target_destroy(). Devices which take a
long time to quiesce during a target_destroy() could hog the CPU for
relatively long periods of time.
Nevertheless, further study revealed that virtio-scsi itself is broken
in a way that it doesn't increment the 'reqs' counter when submitting
requests on MQ in certain conditions. That caused the counter to go to
-1 (on the completion of the first request) and the CPU to hang
indefinitely.
The following patch fixes the issue:
--- old/linux-4.4.0/drivers/scsi/virtio_scsi.c2018-06-04
10:23:07.0 -0700
+++ new/linux-4.4.0/drivers/scsi/virtio_scsi.c2018-06-05
10:03:29.083428545 -0700
@@ -641,9 +641,10 @@
scsi_target(sc->device)->hostdata;
struct virtio_scsi_vq *req_vq;
- if (shost_use_blk_mq(sh))
+ if (shost_use_blk_mq(sh)) {
req_vq = virtscsi_pick_vq_mq(vscsi, sc);
- else
+ atomic_inc(>reqs);
+ } else
req_vq = virtscsi_pick_vq(vscsi, tgt);
return virtscsi_queuecommand(vscsi, req_vq, sc);
Signed-off-by: Felipe Franciosi
Please consider this a urgent fix as all of our customers which use
Ubuntu 16.04 and have MQ enabled for better performance will be
affected by your latest update. Our workaround is to recommend that
they disable SCSI MQ while you work on the issue.
Best regards,
Felipe
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubu
[Group.of.nepali.translators] [Bug 1775235] Re: Ubuntu 16.04 (4.4.0-127) hangs on boot with virtio-scsi MQ enabled
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Status: New => Confirmed
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => High
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1775235
Title:
Ubuntu 16.04 (4.4.0-127) hangs on boot with virtio-scsi MQ enabled
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Xenial:
Confirmed
Bug description:
We noticed that Ubuntu 16.04 guests running on Nutanix AHV stopped
booting after they were upgraded to the latest kernel (4.4.0-127).
Only guests with scsi mq enabled suffered from this problem. AHV is
one of the few hypervisor products to offer multiqueue for virtio-scsi
devices.
Upon further investigation, we could see that the kernel would hang
during the scanning of scsi targets. More specifically, immediately
after coming across a target without any luns present. That's the
first time the kernel destroys a target (given it doesn't have luns).
This could be confirmed with gdb (attached to qemu's gdbserver):
#0 0xc0045039 in ?? ()
#1 0x88022c753c98 in ?? ()
#2 0x815d1de6 in scsi_target_destroy (starget=0x88022ad62400)
at /build/linux-E14mqW/linux-4.4.0/drivers/scsi/scsi_scan.c:322
This shows the guest vCPU stuck on virtio-scsi's implementation of
target_destroy. Despite lacking symbols, we managed to examine the
virtio_scsi_target_state to see that the 'reqs' counter was invalid:
(gdb) p *(struct virtio_scsi_target_state *)starget->hostdata
$6 = {tgt_seq = {sequence = 0}, reqs = {counter = -1}, req_vq =
0x88022cbdd9e8}
(gdb)
This drew our attention to the following patch which is exclusive to the
Ubuntu kernel:
commit f1f609d8015e1d34d39458924dcd9524fccd4307
Author: Jay Vosburgh
Date: Thu Apr 19 21:40:00 2018 +0200
In a nutshell, the patch spins on the target's 'reqs' counter waiting for the
target to quiesce:
--- a/drivers/scsi/virtio_scsi.c
+++ b/drivers/scsi/virtio_scsi.c
@@ -785,6 +785,10 @@ static int virtscsi_target_alloc(struct scsi_target
*starget)
static void virtscsi_target_destroy(struct scsi_target *starget)
{
struct virtio_scsi_target_state *tgt = starget->hostdata;
+
+ /* we can race with concurrent virtscsi_complete_cmd */
+ while (atomic_read(>reqs))
+ cpu_relax();
kfree(tgt);
}
Personally, I think this is a catastrophic way of waiting for a target
to quiesce since virtscsi_target_destroy() is called with IRQs
disabled from scsi_scan.c:scsi_target_destroy(). Devices which take a
long time to quiesce during a target_destroy() could hog the CPU for
relatively long periods of time.
Nevertheless, further study revealed that virtio-scsi itself is broken
in a way that it doesn't increment the 'reqs' counter when submitting
requests on MQ in certain conditions. That caused the counter to go to
-1 (on the completion of the first request) and the CPU to hang
indefinitely.
The following patch fixes the issue:
--- old/linux-4.4.0/drivers/scsi/virtio_scsi.c2018-06-04
10:23:07.0 -0700
+++ new/linux-4.4.0/drivers/scsi/virtio_scsi.c2018-06-05
10:03:29.083428545 -0700
@@ -641,9 +641,10 @@
scsi_target(sc->device)->hostdata;
struct virtio_scsi_vq *req_vq;
- if (shost_use_blk_mq(sh))
+ if (shost_use_blk_mq(sh)) {
req_vq = virtscsi_pick_vq_mq(vscsi, sc);
- else
+ atomic_inc(>reqs);
+ } else
req_vq = virtscsi_pick_vq(vscsi, tgt);
return virtscsi_queuecommand(vscsi, req_vq, sc);
Signed-off-by: Felipe Franciosi
Please consider this a urgent fix as all of our customers which use
Ubuntu 16.04 and have MQ enabled for better performance will be
affected by your latest update. Our workaround is to recommend that
they disable SCSI MQ while you work on the issue.
Best regards,
Felipe
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775235/+subscriptions
___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
