[Kernel-packages] [Bug 1865419] Re: bionic/linux-aws-fips: 4.15.0-2012.12 -proposed tracker
** Summary changed: - bionic/linux-aws-fips: -proposed tracker + bionic/linux-aws-fips: 4.15.0-2012.12 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Manoj Iyer (manjo) ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-lrm Assignee: Canonical Kernel Team (canonical-kernel-team) => Manoj Iyer (manjo) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Manoj Iyer (manjo) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Manoj Iyer (manjo) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1865419 Title: bionic/linux-aws-fips: 4.15.0-2012.12 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid 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-lrm 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 verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid 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 -- kernel-stable-master-bug: 1865269 packages: lrm: linux-restricted-modules-aws-fips main: linux-aws-fips meta: linux-meta-aws-fips signed: linux-signed-aws-fips phase: Packaging phase-changed: Wednesday, 04. March 2020 22:46 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-lrm: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded replaces: bug 1864732 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865419/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1865197] Re: trusty/linux-azure: 4.15.0-1074.79~14.04.1 -proposed tracker
** Summary changed: - trusty/linux-azure: -proposed tracker + trusty/linux-azure: 4.15.0-1074.79~14.04.1 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Manoj Iyer (manjo) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Manoj Iyer (manjo) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Manoj Iyer (manjo) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1865197 Title: trusty/linux-azure: 4.15.0-1074.79~14.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 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 stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Trusty: Confirmed 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 -- kernel-stable-master-bug: 1865198 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Packaging phase-changed: Wednesday, 04. March 2020 03:51 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded replaces: bug 1864744 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865197/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1865246] Re: trusty/linux-aws: 4.4.0-1064.68 -proposed tracker
** Summary changed: - trusty/linux-aws: -proposed tracker + trusty/linux-aws: 4.4.0-1064.68 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Manoj Iyer (manjo) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Manoj Iyer (manjo) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1865246 Title: trusty/linux-aws: 4.4.0-1064.68 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid 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 promote-signing-to-proposed series: Invalid 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 verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: Confirmed 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 -- kernel-stable-master-bug: 1865106 packages: main: linux-aws meta: linux-meta-aws phase: Packaging phase-changed: Tuesday, 03. March 2020 18:01 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded replaces: bug 1863334 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865246/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1865199] Re: xenial/linux-fips: 4.4.0-1031.36 -proposed tracker
** Summary changed: - xenial/linux-fips: -proposed tracker + xenial/linux-fips: 4.4.0-1031.36 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Manoj Iyer (manjo) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Manoj Iyer (manjo) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Manoj Iyer (manjo) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1865199 Title: xenial/linux-fips: 4.4.0-1031.36 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid 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 verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid 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 -- kernel-stable-master-bug: 1865106 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Packaging phase-changed: Tuesday, 03. March 2020 02:46 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded replaces: bug 1863331 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865199/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1865203] Re: bionic/linux-fips: 4.15.0-1025.30 -proposed tracker
** Summary changed: - bionic/linux-fips: -proposed tracker + bionic/linux-fips: 4.15.0-1025.30 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Manoj Iyer (manjo) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Manoj Iyer (manjo) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Manoj Iyer (manjo) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1865203 Title: bionic/linux-fips: 4.15.0-1025.30 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid 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 verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid 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 -- kernel-stable-master-bug: 1865109 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Packaging phase-changed: Tuesday, 03. March 2020 00:11 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865203/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1865201] Re: bionic/linux-ibm-gt: 4.15.0-1051.57 -proposed tracker
** Summary changed: - bionic/linux-ibm-gt: -proposed tracker + bionic/linux-ibm-gt: 4.15.0-1051.57 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Manoj Iyer (manjo) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Manoj Iyer (manjo) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1865201 Title: bionic/linux-ibm-gt: 4.15.0-1051.57 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid 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 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 verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid 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 -- kernel-stable-master-bug: 1865109 packages: main: linux-ibm-gt meta: linux-meta-ibm-gt phase: Packaging phase-changed: Monday, 02. March 2020 16:41 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded replaces: bug 1864739 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865201/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1865190] Re: eoan/linux-azure: 5.3.0-1015.16 -proposed tracker
** Summary changed: - eoan/linux-azure: -proposed tracker + eoan/linux-azure: 5.3.0-1015.16 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Manoj Iyer (manjo) ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-lrm Assignee: Canonical Kernel Team (canonical-kernel-team) => Manoj Iyer (manjo) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Manoj Iyer (manjo) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Manoj Iyer (manjo) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1865190 Title: eoan/linux-azure: 5.3.0-1015.16 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-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-lrm 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-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New 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: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Eoan: Confirmed 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 -- kernel-stable-master-bug: 1865111 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Packaging phase-changed: Monday, 02. March 2020 14:46 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-lrm: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded replaces: bug 1863274 trackers: bionic/linux-azure-5.3: bug 1865189 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865190/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863334] Re: trusty/linux-aws: 4.4.0-1063.67 -proposed tracker
** Summary changed: - trusty/linux-aws: -proposed tracker + trusty/linux-aws: 4.4.0-1063.67 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Manoj Iyer (manjo) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Manoj Iyer (manjo) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1863334 Title: trusty/linux-aws: 4.4.0-1063.67 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid 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 promote-signing-to-proposed series: Invalid 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 verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: Confirmed 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 -- kernel-stable-master-bug: 1863338 packages: main: linux-aws meta: linux-meta-aws phase: Packaging phase-changed: Wednesday, 19. February 2020 22:46 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863334/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863317] Re: bionic/linux-aws-fips: 4.15.0-2010.10 -proposed tracker
** Summary changed: - bionic/linux-aws-fips: -proposed tracker + bionic/linux-aws-fips: 4.15.0-2010.10 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Manoj Iyer (manjo) ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-lrm Assignee: Canonical Kernel Team (canonical-kernel-team) => Manoj Iyer (manjo) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Manoj Iyer (manjo) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Manoj Iyer (manjo) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1863317 Title: bionic/linux-aws-fips: 4.15.0-2010.10 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid 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-lrm 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 verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid 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 -- kernel-stable-master-bug: 1863325 packages: lrm: linux-restricted-modules-aws-fips main: linux-aws-fips meta: linux-meta-aws-fips signed: linux-signed-aws-fips phase: Packaging phase-changed: Wednesday, 19. February 2020 18:31 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-lrm: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863317/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863331] Re: xenial/linux-fips: 4.4.0-1030.35 -proposed tracker
** Summary changed: - xenial/linux-fips: -proposed tracker + xenial/linux-fips: 4.4.0-1030.35 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Manoj Iyer (manjo) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Manoj Iyer (manjo) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Manoj Iyer (manjo) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1863331 Title: xenial/linux-fips: 4.4.0-1030.35 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid 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 verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid 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 -- kernel-stable-master-bug: 1863338 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Packaging phase-changed: Wednesday, 19. February 2020 17:06 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863331/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863324] Re: xenial/linux-raspi2: 4.4.0-1130.139 -proposed tracker
** Summary changed: - xenial/linux-raspi2: -proposed tracker + xenial/linux-raspi2: 4.4.0-1130.139 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Manoj Iyer (manjo) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Manoj Iyer (manjo) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1863324 Title: xenial/linux-raspi2: 4.4.0-1130.139 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New 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 promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Xenial: Confirmed 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 -- kernel-stable-master-bug: 1863338 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Packaging phase-changed: Wednesday, 19. February 2020 16:16 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded trackers: xenial/linux-raspi2/pi2-kernel: bug 1863322 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863324/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863341] Re: bionic/linux-fips: 4.15.0-1024.27 -proposed tracker
** Summary changed: - bionic/linux-fips: -proposed tracker + bionic/linux-fips: 4.15.0-1024.27 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Manoj Iyer (manjo) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Manoj Iyer (manjo) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Manoj Iyer (manjo) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1863341 Title: bionic/linux-fips: 4.15.0-1024.27 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid 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 verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid 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 -- kernel-stable-master-bug: 1863350 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Packaging phase-changed: Wednesday, 19. February 2020 03:41 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863341/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863335] Re: bionic/linux-ibm-gt: 4.15.0-1049.53 -proposed tracker
** Summary changed: - bionic/linux-ibm-gt: -proposed tracker + bionic/linux-ibm-gt: 4.15.0-1049.53 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Manoj Iyer (manjo) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Manoj Iyer (manjo) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1863335 Title: bionic/linux-ibm-gt: 4.15.0-1049.53 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid 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 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 verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid 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 -- kernel-stable-master-bug: 1863350 packages: main: linux-ibm-gt meta: linux-meta-ibm-gt phase: Packaging phase-changed: Tuesday, 18. February 2020 20:47 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863335/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861152] Re: bionic/linux-fips: 4.15.0-1023.26 -proposed tracker
** Summary changed: - bionic/linux-fips: -proposed tracker + bionic/linux-fips: 4.15.0-1023.26 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Manoj Iyer (manjo) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Manoj Iyer (manjo) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Manoj Iyer (manjo) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1861152 Title: bionic/linux-fips: 4.15.0-1023.26 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid 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 verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid 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 -- kernel-stable-master-bug: 1861165 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Packaging phase-changed: Tuesday, 04. February 2020 16:52 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1861152/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861149] Re: bionic/linux-ibm-gt: 4.15.0-1047.51 -proposed tracker
** Summary changed: - bionic/linux-ibm-gt: -proposed tracker + bionic/linux-ibm-gt: 4.15.0-1047.51 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Manoj Iyer (manjo) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Manoj Iyer (manjo) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1861149 Title: bionic/linux-ibm-gt: 4.15.0-1047.51 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid 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 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 verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid 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 -- kernel-stable-master-bug: 1861165 packages: main: linux-ibm-gt meta: linux-meta-ibm-gt phase: Packaging phase-changed: Monday, 03. February 2020 19:56 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1861149/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861151] Re: bionic/linux-oracle: 4.15.0-1032.35 -proposed tracker
** Summary changed: - bionic/linux-oracle: -proposed tracker + bionic/linux-oracle: 4.15.0-1032.35 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Manoj Iyer (manjo) ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-lrm Assignee: Canonical Kernel Team (canonical-kernel-team) => Manoj Iyer (manjo) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Manoj Iyer (manjo) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Manoj Iyer (manjo) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1861151 Title: bionic/linux-oracle: 4.15.0-1032.35 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-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-lrm 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-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New 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: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle source package in Bionic: Confirmed 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 -- kernel-stable-master-bug: 1861165 packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Packaging phase-changed: Monday, 03. February 2020 17:13 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-lrm: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded trackers: xenial/linux-oracle: bug 1861150 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1861151/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861116] Re: xenial/linux-fips: 4.4.0-1029.34 -proposed tracker
** Summary changed: - xenial/linux-fips: -proposed tracker + xenial/linux-fips: 4.4.0-1029.34 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Manoj Iyer (manjo) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Manoj Iyer (manjo) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Manoj Iyer (manjo) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1861116 Title: xenial/linux-fips: 4.4.0-1029.34 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid 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 verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid 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 -- kernel-stable-master-bug: 1861122 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Packaging phase-changed: Wednesday, 29. January 2020 17:06 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1861116/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859799] Re: xenial/linux-deeplens: 4.15.0-1015.15 -proposed tracker
** Summary changed: - xenial/linux-deeplens: -proposed tracker + xenial/linux-deeplens: 4.15.0-1015.15 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Manoj Iyer (manjo) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Manoj Iyer (manjo) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859799 Title: xenial/linux-deeplens: 4.15.0-1015.15 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: New 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 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: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid 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 -- kernel-stable-master-bug: 1859704 packages: main: linux-deeplens meta: linux-meta-deeplens phase: Packaging phase-changed: Thursday, 16. January 2020 17:22 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1859799/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859793] Re: bionic/linux-snapdragon: 4.15.0-1071.78 -proposed tracker
** Summary changed: - bionic/linux-snapdragon: -proposed tracker + bionic/linux-snapdragon: 4.15.0-1071.78 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Manoj Iyer (manjo) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Manoj Iyer (manjo) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1859793 Title: bionic/linux-snapdragon: 4.15.0-1071.78 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New 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 promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Bionic: Confirmed 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 -- kernel-stable-master-bug: 1859705 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Packaging phase-changed: Wednesday, 15. January 2020 21:16 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded trackers: bionic/linux-snapdragon/dragonboard-kernel: bug 1859791 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1859793/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859692] Re: eoan/linux-raspi2: 5.3.0-1017.19 -proposed tracker
** Summary changed: - eoan/linux-raspi2: -proposed tracker + eoan/linux-raspi2: 5.3.0-1017.19 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Manoj Iyer (manjo) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Manoj Iyer (manjo) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1859692 Title: eoan/linux-raspi2: 5.3.0-1017.19 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New 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 promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Eoan: Confirmed 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 -- kernel-stable-master-bug: 1859694 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Packaging phase-changed: Wednesday, 15. January 2020 21:11 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded replaces: bug 1858941 trackers: bionic/linux-raspi2-5.3: bug 1859691 eoan/linux-raspi2/pi-kernel: bug 1859690 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1859692/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1858589] Re: xenial/linux-fips: 4.4.0-1028.33 -proposed tracker
** Summary changed: - xenial/linux-fips: -proposed tracker + xenial/linux-fips: 4.4.0-1028.33 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Manoj Iyer (manjo) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Manoj Iyer (manjo) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Manoj Iyer (manjo) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1858589 Title: xenial/linux-fips: 4.4.0-1028.33 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid 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 verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid 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 -- kernel-stable-master-bug: 1858594 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Packaging phase-changed: Monday, 13. January 2020 21:16 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1858589/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1858529] Re: disco/linux-raspi2: 5.0.0-1025.26 -proposed tracker
** Summary changed: - disco/linux-raspi2: -proposed tracker + disco/linux-raspi2: 5.0.0-1025.26 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Manoj Iyer (manjo) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Manoj Iyer (manjo) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1858529 Title: disco/linux-raspi2: 5.0.0-1025.26 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New 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 promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Disco: Confirmed 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 -- kernel-stable-master-bug: 1858547 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Packaging phase-changed: Friday, 10. January 2020 23:35 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1858529/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1858586] Re: xenial/linux-raspi2: 4.4.0-1128.137 -proposed tracker
** Summary changed: - xenial/linux-raspi2: -proposed tracker + xenial/linux-raspi2: 4.4.0-1128.137 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Manoj Iyer (manjo) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Manoj Iyer (manjo) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1858586 Title: xenial/linux-raspi2: 4.4.0-1128.137 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New 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 promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Xenial: Confirmed 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 -- kernel-stable-master-bug: 1858594 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Packaging phase-changed: Thursday, 09. January 2020 21:01 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded trackers: xenial/linux-raspi2/pi2-kernel: bug 1858585 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1858586/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848193] Re: Fixup tlbie vs store ordering issue on POWER9
Fixed by https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848039
** Also affects: linux (Ubuntu Eoan)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Eoan)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Eoan)
Status: New => Fix Released
** Changed in: linux (Ubuntu)
Status: Triaged => Fix Released
** Changed in: ubuntu-power-systems
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1848193
Title:
Fixup tlbie vs store ordering issue on POWER9
Status in The Ubuntu-power-systems project:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Eoan:
Fix Released
Bug description:
== Comment: #0 - Michael Ranweiler - 2019-10-07 01:52:38 ==
On POWER9, under some circumstances, a broadcast TLB invalidation will fail
to invalidate the ERAT cache on some threads when there are parallel
mtpidr/mtlpidr happening on other threads of the same core. This can cause
stores to continue to go to a page after it's unmapped.
The workaround is to force an ERAT flush using PID=0 or LPID=0 tlbie
flush. This additional TLB flush will cause the ERAT cache
invalidation. Since we are using PID=0 or LPID=0, we don't get
filtered out by the TLB snoop filtering logic.
We need to still follow this up with another tlbie to take care of
store vs tlbie ordering issue explained in commit: a5d4b5891c2f
("powerpc/mm: Fixup tlbie vs store ordering issue on POWER9"). The
presence of ERAT cache implies we can still get new stores and they
may miss store queue marking flush.
The upstream git commits to resolve the problem:
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes=677733e296b5c7a37c47da391fc70a43dc40bd67
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes=09ce98cacd51fcd0fa0af2f79d1e1d3192f4cbb0
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes=047e6575aec71d75b765c22111820c4776cd1c43
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1848193/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848193] Re: Fixup tlbie vs store ordering issue on POWER9
$ uname -a
Linux bobone 5.3.0-24-generic #26-Ubuntu SMP Thu Nov 14 01:12:58 UTC 2019
ppc64le ppc64le ppc64le GNU/Linux
$ sudo ./tlbie_test
start_cpu list:0
number of worker threads:4 + 1 snapshot thread
Allocated address:0x75e53581 + secondary map:0x75e53557
logdir at : /tmp/logdir-26561
Timeout: 1200 seconds
=
Starting Test
Mon Dec 16 16:59:06 2019
=
$
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1848193
Title:
Fixup tlbie vs store ordering issue on POWER9
Status in The Ubuntu-power-systems project:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Eoan:
Fix Released
Bug description:
== Comment: #0 - Michael Ranweiler - 2019-10-07 01:52:38 ==
On POWER9, under some circumstances, a broadcast TLB invalidation will fail
to invalidate the ERAT cache on some threads when there are parallel
mtpidr/mtlpidr happening on other threads of the same core. This can cause
stores to continue to go to a page after it's unmapped.
The workaround is to force an ERAT flush using PID=0 or LPID=0 tlbie
flush. This additional TLB flush will cause the ERAT cache
invalidation. Since we are using PID=0 or LPID=0, we don't get
filtered out by the TLB snoop filtering logic.
We need to still follow this up with another tlbie to take care of
store vs tlbie ordering issue explained in commit: a5d4b5891c2f
("powerpc/mm: Fixup tlbie vs store ordering issue on POWER9"). The
presence of ERAT cache implies we can still get new stores and they
may miss store queue marking flush.
The upstream git commits to resolve the problem:
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes=677733e296b5c7a37c47da391fc70a43dc40bd67
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes=09ce98cacd51fcd0fa0af2f79d1e1d3192f4cbb0
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes=047e6575aec71d75b765c22111820c4776cd1c43
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1848193/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848193] Re: Fixup tlbie vs store ordering issue on POWER9
IBM, any progress on testing results ?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1848193
Title:
Fixup tlbie vs store ordering issue on POWER9
Status in The Ubuntu-power-systems project:
Incomplete
Status in linux package in Ubuntu:
Incomplete
Bug description:
== Comment: #0 - Michael Ranweiler - 2019-10-07 01:52:38 ==
On POWER9, under some circumstances, a broadcast TLB invalidation will fail
to invalidate the ERAT cache on some threads when there are parallel
mtpidr/mtlpidr happening on other threads of the same core. This can cause
stores to continue to go to a page after it's unmapped.
The workaround is to force an ERAT flush using PID=0 or LPID=0 tlbie
flush. This additional TLB flush will cause the ERAT cache
invalidation. Since we are using PID=0 or LPID=0, we don't get
filtered out by the TLB snoop filtering logic.
We need to still follow this up with another tlbie to take care of
store vs tlbie ordering issue explained in commit: a5d4b5891c2f
("powerpc/mm: Fixup tlbie vs store ordering issue on POWER9"). The
presence of ERAT cache implies we can still get new stores and they
may miss store queue marking flush.
The upstream git commits to resolve the problem:
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes=677733e296b5c7a37c47da391fc70a43dc40bd67
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes=09ce98cacd51fcd0fa0af2f79d1e1d3192f4cbb0
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes=047e6575aec71d75b765c22111820c4776cd1c43
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1848193/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854806] Re: bionic/linux-ibm-gt: 4.15.0-1045.49 -proposed tracker
** Summary changed: - bionic/linux-ibm-gt: 4.15.0-1045.48 -proposed tracker + bionic/linux-ibm-gt: 4.15.0-1045.49 -proposed tracker -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854806 Title: bionic/linux-ibm-gt: 4.15.0-1045.49 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid 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 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 verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid 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 -- kernel-stable-master-bug: 1854819 packages: main: linux-ibm-gt meta: linux-meta-ibm-gt phase: Packaging phase-changed: Wednesday, 04. December 2019 19:02 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854806/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854071] Re: Backport In-Memory Collection Counters (IMC) trace-mode patches
** Changed in: ubuntu-power-systems Status: Triaged => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854071 Title: Backport In-Memory Collection Counters (IMC) trace-mode patches Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Status in linux source package in Disco: Incomplete Bug description: == Comment: #0 - Murilo Opsfelder Araujo - 2019-11-08 06:30:06 == ---Problem Description--- The following patches may be wanted in >= Bionic kernels: 1. powerpc/include: Add data structures and macros for IMC trace mode https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=next=d1720adff3783a2ba7c128e304a385d18962835b 2. powerpc/perf: Rearrange setting of ldbar for thread-imc https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=next=dd50cf7cbc7bdd86483b797ac3d27b37d5aeeaa4 3. powerpc/perf: Add privileged access check for thread_imc https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=next=216c3087a346db8d7c8a064d2b8f0f49e4694934 4. powerpc/perf: Trace imc events detection and cpuhotplug https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=next=72c69dcddce103338de558c5c6e9ef9e4f607ce1 5. powerpc/perf: Trace imc PMU functions https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=next=012ae244845f19d5f6ca2a90426851bc5044a0dc Patch #3 addresses a security issue. ---uname output--- na Machine Type = na ---Debugger--- A debugger is not configured Stack trace output: no Oops output: no System Dump Info: The system is not configured to capture a system dump. == Comment: #12 - Murilo Opsfelder Araujo - 2019-11-22 07:41:20 == Please mirror to Canonical to backporting this single patch for >= Bionic kernels (or for which kernels they find appropriate): https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?id=216c3087a346db8d7c8a064d2b8f0f49e4694934 commit 216c3087a346db8d7c8a064d2b8f0f49e4694934 Author: Madhavan Srinivasan Date: Tue Apr 16 15:18:29 2019 +0530 powerpc/perf: Add privileged access check for thread_imc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1854071/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848127] Re: [LTCTest][OPAL][OP930] Machine hangs after injecting the Machine Check Error
** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: ubuntu-power-systems Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1848127 Title: [LTCTest][OPAL][OP930] Machine hangs after injecting the Machine Check Error Status in The Ubuntu-power-systems project: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Disco: Fix Released Status in linux source package in Eoan: Fix Released Bug description: [IMPACT] MCE test renders the system unresponsive on P9 open power hardware (Withersoon) [TEST] A test kernel is available in ppa:ubuntu-power-triage/lp1848127. Please see the [OTHER] section for test details and comment #7 for results with the PPA kernel. [FIX] IBM has identified the following patch that fixes this issue: commit 99ead78afd1128bfcebe7f88f3b102fb2da09aee Author: Balbir Singh Date: Tue Aug 20 13:43:47 2019 +0530 powerpc/mce: Fix MCE handling for huge pages [REGRESSION POTENTIAL] The patch is applicable the powerpc architecture and limited in scope to MCE handling for huge pages. Patch does not touch any generic code. Regression if any is limited to powerpc MCE handling. [OTHER] == Comment: #0 - PAVAMAN SUBRAMANIYAM - 2019-05-07 23:31:20 == Install a P9 Open Power Hardware with the latest OP930 Firmware images built from the upstream op-build git tree. root@witherspoon:~# cat /etc/os-release ID="openbmc-phosphor" NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro)" VERSION="ibm-v2.3" VERSION_ID="ibm-v2.3-476-g2d622cb-r32-0-g9973ab0" PRETTY_NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro) ibm-v2.3" BUILD_ID="ibm-v2.3-476-g2d622cb-r32" root@witherspoon:~# cat /var/lib/phosphor-software-manager/pnor/ro/VERSION open-power-witherspoon-v2.3-rc2-58-g59fd0743 buildroot-2019.02.2-17-g93b841d204 skiboot-v6.3-rc2 hostboot-19a436e occ-58e422d linux-5.0.9-openpower1-p3a4d5a4 petitboot-v1.10.3 machine-xml-a6f4df3 hostboot-binaries-hw043019a.940 capp-ucode-p9-dd2-v4 sbe-249671d hcode-hw040319a.940 Then enable sw xstop manually by using below command: root@ltc-wspoon11:~# nvram -p ibm,skiboot --update-config opal-sw-xstop=enable root@ltc-wspoon11:~# nvram -p ibm,skiboot --print-config "ibm,skiboot" Partition -- experimental-fast-reset=1 snarf-mode=noo opal-sw-xstop=enable Then from the Linux HOST injected the MCE UE Error on the machine as follows: root@ltc-wspoon11:~# ./probe_cpus.sh -L CHIP ID: 0 CORE ID: 0 THREADS: 4 CPUs: 0 1 2 3 CHIP ID: 0 CORE ID: 1 THREADS: 4 CPUs: 4 5 6 7 CHIP ID: 0 CORE ID: 2 THREADS: 4 CPUs: 8 9 10 11 CHIP ID: 0 CORE ID: 3 THREADS: 4 CPUs: 12 13 14 15 CHIP ID: 0 CORE ID: 6 THREADS: 4 CPUs: 16 17 18 19 CHIP ID: 0 CORE ID: 7 THREADS: 4 CPUs: 20 21 22 23 CHIP ID: 0 CORE ID: 8 THREADS: 4 CPUs: 24 25 26 27 CHIP ID: 0 CORE ID: 9 THREADS: 4 CPUs: 28 29 30 31 CHIP ID: 0 CORE ID: 10 THREADS: 4 CPUs: 32 33 34 35 CHIP ID: 0 CORE ID: 11 THREADS: 4 CPUs: 36 37 38 39 CHIP ID: 0 CORE ID: 12 THREADS: 4 CPUs: 40 41 42 43 CHIP ID: 0 CORE ID: 13 THREADS: 4 CPUs: 44 45 46 47 CHIP ID: 0 CORE ID: 16 THREADS: 4 CPUs: 48 49 50 51 CHIP ID: 0 CORE ID: 17 THREADS: 4 CPUs: 52 53 54 55 CHIP ID: 0 CORE ID: 18 THREADS: 4 CPUs: 56 57 58 59 CHIP ID: 0 CORE ID: 19 THREADS: 4 CPUs: 60 61 62 63 CHIP ID: 0 CORE ID: 20 THREADS: 4 CPUs: 64 65 66 67 CHIP ID: 0 CORE ID: 21 THREADS: 4 CPUs: 68 69 70 71 CHIP ID: 8 CORE ID: 6 THREADS: 4 CPUs: 72 73 74 75 CHIP ID: 8 CORE ID: 7 THREADS: 4 CPUs: 76 77 78 79 CHIP ID: 8 CORE ID: 8 THREADS: 4 CPUs: 80 81 82 83 CHIP ID: 8 CORE ID: 9 THREADS: 4 CPUs: 84 85 86 87 CHIP ID: 8 CORE ID: 10 THREADS: 4 CPUs: 88 89 90 91 CHIP ID: 8 CORE ID: 11 THREADS: 4 CPUs: 92 93 94 95 CHIP ID: 8 CORE ID: 12 THREADS: 4 CPUs: 96 97 98 99 CHIP ID: 8 CORE ID: 13 THREADS: 4 CPUs: 100 101 102 103 CHIP ID: 8 CORE ID: 14 THREADS: 4 CPUs: 104 105 106 107 CHIP ID: 8 CORE ID: 15 THREADS: 4 CPUs: 108 109 110 111 CHIP ID: 8 CORE ID: 16 THREADS: 4 CPUs: 112 113 114 115 CHIP ID: 8 CORE ID: 17 THREADS: 4 CPUs: 116 117 118 119 CHIP ID: 8 CORE ID: 18 THREADS: 4 CPUs: 120 121 122 123 CHIP ID: 8 CORE ID: 19 THREADS: 4 CPUs: 124 125 126 127 CHIP ID: 8 CORE ID: 20 THREADS: 4 CPUs: 128 129 130 131 CHIP ID: 8 CORE ID: 21 THREADS: 4 CPUs: 132 133 134 135 CHIP ID: 8 CORE ID: 22 THREADS: 4 CPUs: 136 137 138 139 CHIP ID: 8 CORE ID: 23 THREADS: 4 CPUs: 140 141 142 143 - p[0] eq[0,1,2,3,4,5] ex[0,1,3,4,5,6,8,9,10]
[Kernel-packages] [Bug 1854071] Re: Backport In-Memory Collection Counters (IMC) trace-mode patches
IBM, Please test the Disco kernel available in https://launchpad.net/~ubuntu- power-triage/+archive/ubuntu/lp1854071/ Also, please share following details 1. What impact does it have without these patches? 2. The testcase used, and how to run the tests. Thanks ** Changed in: linux (Ubuntu Disco) Status: In Progress => Incomplete ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854071 Title: Backport In-Memory Collection Counters (IMC) trace-mode patches Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: Incomplete Status in linux source package in Disco: Incomplete Bug description: == Comment: #0 - Murilo Opsfelder Araujo - 2019-11-08 06:30:06 == ---Problem Description--- The following patches may be wanted in >= Bionic kernels: 1. powerpc/include: Add data structures and macros for IMC trace mode https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=next=d1720adff3783a2ba7c128e304a385d18962835b 2. powerpc/perf: Rearrange setting of ldbar for thread-imc https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=next=dd50cf7cbc7bdd86483b797ac3d27b37d5aeeaa4 3. powerpc/perf: Add privileged access check for thread_imc https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=next=216c3087a346db8d7c8a064d2b8f0f49e4694934 4. powerpc/perf: Trace imc events detection and cpuhotplug https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=next=72c69dcddce103338de558c5c6e9ef9e4f607ce1 5. powerpc/perf: Trace imc PMU functions https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=next=012ae244845f19d5f6ca2a90426851bc5044a0dc Patch #3 addresses a security issue. ---uname output--- na Machine Type = na ---Debugger--- A debugger is not configured Stack trace output: no Oops output: no System Dump Info: The system is not configured to capture a system dump. == Comment: #12 - Murilo Opsfelder Araujo - 2019-11-22 07:41:20 == Please mirror to Canonical to backporting this single patch for >= Bionic kernels (or for which kernels they find appropriate): https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?id=216c3087a346db8d7c8a064d2b8f0f49e4694934 commit 216c3087a346db8d7c8a064d2b8f0f49e4694934 Author: Madhavan Srinivasan Date: Tue Apr 16 15:18:29 2019 +0530 powerpc/perf: Add privileged access check for thread_imc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1854071/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854071] Re: Backport In-Memory Collection Counters (IMC) trace-mode patches
** Changed in: linux (Ubuntu Disco) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854071 Title: Backport In-Memory Collection Counters (IMC) trace-mode patches Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: New Status in linux source package in Disco: In Progress Bug description: == Comment: #0 - Murilo Opsfelder Araujo - 2019-11-08 06:30:06 == ---Problem Description--- The following patches may be wanted in >= Bionic kernels: 1. powerpc/include: Add data structures and macros for IMC trace mode https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=next=d1720adff3783a2ba7c128e304a385d18962835b 2. powerpc/perf: Rearrange setting of ldbar for thread-imc https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=next=dd50cf7cbc7bdd86483b797ac3d27b37d5aeeaa4 3. powerpc/perf: Add privileged access check for thread_imc https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=next=216c3087a346db8d7c8a064d2b8f0f49e4694934 4. powerpc/perf: Trace imc events detection and cpuhotplug https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=next=72c69dcddce103338de558c5c6e9ef9e4f607ce1 5. powerpc/perf: Trace imc PMU functions https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=next=012ae244845f19d5f6ca2a90426851bc5044a0dc Patch #3 addresses a security issue. ---uname output--- na Machine Type = na ---Debugger--- A debugger is not configured Stack trace output: no Oops output: no System Dump Info: The system is not configured to capture a system dump. == Comment: #12 - Murilo Opsfelder Araujo - 2019-11-22 07:41:20 == Please mirror to Canonical to backporting this single patch for >= Bionic kernels (or for which kernels they find appropriate): https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?id=216c3087a346db8d7c8a064d2b8f0f49e4694934 commit 216c3087a346db8d7c8a064d2b8f0f49e4694934 Author: Madhavan Srinivasan Date: Tue Apr 16 15:18:29 2019 +0530 powerpc/perf: Add privileged access check for thread_imc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1854071/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854071] Re: Backport In-Memory Collection Counters (IMC) trace-mode patches
Since this is not a critical bug fix or regression this might not be a candidate for LTS Bionic kernel. ** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Disco) Assignee: (unassigned) => Manoj Iyer (manjo) ** Changed in: linux (Ubuntu Disco) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854071 Title: Backport In-Memory Collection Counters (IMC) trace-mode patches Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: New Status in linux source package in Disco: New Bug description: == Comment: #0 - Murilo Opsfelder Araujo - 2019-11-08 06:30:06 == ---Problem Description--- The following patches may be wanted in >= Bionic kernels: 1. powerpc/include: Add data structures and macros for IMC trace mode https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=next=d1720adff3783a2ba7c128e304a385d18962835b 2. powerpc/perf: Rearrange setting of ldbar for thread-imc https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=next=dd50cf7cbc7bdd86483b797ac3d27b37d5aeeaa4 3. powerpc/perf: Add privileged access check for thread_imc https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=next=216c3087a346db8d7c8a064d2b8f0f49e4694934 4. powerpc/perf: Trace imc events detection and cpuhotplug https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=next=72c69dcddce103338de558c5c6e9ef9e4f607ce1 5. powerpc/perf: Trace imc PMU functions https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=next=012ae244845f19d5f6ca2a90426851bc5044a0dc Patch #3 addresses a security issue. ---uname output--- na Machine Type = na ---Debugger--- A debugger is not configured Stack trace output: no Oops output: no System Dump Info: The system is not configured to capture a system dump. == Comment: #12 - Murilo Opsfelder Araujo - 2019-11-22 07:41:20 == Please mirror to Canonical to backporting this single patch for >= Bionic kernels (or for which kernels they find appropriate): https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?id=216c3087a346db8d7c8a064d2b8f0f49e4694934 commit 216c3087a346db8d7c8a064d2b8f0f49e4694934 Author: Madhavan Srinivasan Date: Tue Apr 16 15:18:29 2019 +0530 powerpc/perf: Add privileged access check for thread_imc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1854071/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854071] Re: Backport In-Memory Collection Counters (IMC) trace-mode patches
** Changed in: linux (Ubuntu) Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) => Manoj Iyer (manjo) ** Changed in: linux (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854071 Title: Backport In-Memory Collection Counters (IMC) trace-mode patches Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: New Bug description: == Comment: #0 - Murilo Opsfelder Araujo - 2019-11-08 06:30:06 == ---Problem Description--- The following patches may be wanted in >= Bionic kernels: 1. powerpc/include: Add data structures and macros for IMC trace mode https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=next=d1720adff3783a2ba7c128e304a385d18962835b 2. powerpc/perf: Rearrange setting of ldbar for thread-imc https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=next=dd50cf7cbc7bdd86483b797ac3d27b37d5aeeaa4 3. powerpc/perf: Add privileged access check for thread_imc https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=next=216c3087a346db8d7c8a064d2b8f0f49e4694934 4. powerpc/perf: Trace imc events detection and cpuhotplug https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=next=72c69dcddce103338de558c5c6e9ef9e4f607ce1 5. powerpc/perf: Trace imc PMU functions https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=next=012ae244845f19d5f6ca2a90426851bc5044a0dc Patch #3 addresses a security issue. ---uname output--- na Machine Type = na ---Debugger--- A debugger is not configured Stack trace output: no Oops output: no System Dump Info: The system is not configured to capture a system dump. == Comment: #12 - Murilo Opsfelder Araujo - 2019-11-22 07:41:20 == Please mirror to Canonical to backporting this single patch for >= Bionic kernels (or for which kernels they find appropriate): https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?id=216c3087a346db8d7c8a064d2b8f0f49e4694934 commit 216c3087a346db8d7c8a064d2b8f0f49e4694934 Author: Madhavan Srinivasan Date: Tue Apr 16 15:18:29 2019 +0530 powerpc/perf: Add privileged access check for thread_imc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1854071/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854755] Re: eoan/linux-oracle: 5.3.0-1008.9 -proposed tracker
** Summary changed: - eoan/linux-oracle: -proposed tracker + eoan/linux-oracle: 5.3.0-1008.9 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Manoj Iyer (manjo) ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-lrm Assignee: Canonical Kernel Team (canonical-kernel-team) => Manoj Iyer (manjo) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Manoj Iyer (manjo) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Manoj Iyer (manjo) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1854755 Title: eoan/linux-oracle: 5.3.0-1008.9 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-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-lrm 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-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New 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: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle source package in Eoan: Confirmed 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 -- kernel-stable-master-bug: 1854762 packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Packaging phase-changed: Thursday, 05. December 2019 01:30 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-lrm: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded trackers: bionic/linux-oracle-5.3: bug 1854754 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854755/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854806] Re: bionic/linux-ibm-gt: 4.15.0-1045.48 -proposed tracker
** Summary changed: - bionic/linux-ibm-gt: -proposed tracker + bionic/linux-ibm-gt: 4.15.0-1045.48 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Manoj Iyer (manjo) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Manoj Iyer (manjo) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854806 Title: bionic/linux-ibm-gt: 4.15.0-1045.48 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid 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 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 verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid 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 -- kernel-stable-master-bug: 1854819 packages: main: linux-ibm-gt meta: linux-meta-ibm-gt phase: Packaging phase-changed: Wednesday, 04. December 2019 19:02 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854806/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854766] Re: disco/linux-raspi2: 5.0.0-1024.25 -proposed tracker
** Summary changed: - disco/linux-raspi2: -proposed tracker + disco/linux-raspi2: 5.0.0-1024.25 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Manoj Iyer (manjo) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Manoj Iyer (manjo) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1854766 Title: disco/linux-raspi2: 5.0.0-1024.25 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New 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 promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Disco: Confirmed 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 -- kernel-stable-master-bug: 1854788 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Packaging phase-changed: Tuesday, 03. December 2019 21:51 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854766/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854784] Re: disco/linux-snapdragon: 5.0.0-1028.30 -proposed tracker
** Summary changed: - disco/linux-snapdragon: -proposed tracker + disco/linux-snapdragon: 5.0.0-1028.30 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Manoj Iyer (manjo) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Manoj Iyer (manjo) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1854784 Title: disco/linux-snapdragon: 5.0.0-1028.30 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New 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 promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Disco: Confirmed 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 -- kernel-stable-master-bug: 1854788 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Packaging phase-changed: Tuesday, 03. December 2019 16:08 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854784/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852287] Re: xenial/linux-deeplens: 4.15.0-1013.13 -proposed tracker
** Summary changed: - xenial/linux-deeplens: -proposed tracker + xenial/linux-deeplens: 4.15.0-1013.13 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Manoj Iyer (manjo) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Manoj Iyer (manjo) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1852287 Title: xenial/linux-deeplens: 4.15.0-1013.13 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: New 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 promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid 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 -- kernel-stable-master-bug: 1852288 packages: main: linux-deeplens meta: linux-meta-deeplens phase: Ready for Packaging phase-changed: Monday, 18. November 2019 15:51 UTC reason: prepare-package: Pending -- version not specified variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852287/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852274] Re: bionic/linux-ibm-gt: 4.15.0-1042.44 -proposed tracker
** Summary changed: - bionic/linux-ibm-gt: -proposed tracker + bionic/linux-ibm-gt: 4.15.0-1042.44 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Manoj Iyer (manjo) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Manoj Iyer (manjo) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1852274 Title: bionic/linux-ibm-gt: 4.15.0-1042.44 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid 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 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 verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid 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 -- kernel-stable-master-bug: 1852289 packages: main: linux-ibm-gt meta: linux-meta-ibm-gt phase: Packaging phase-changed: Monday, 18. November 2019 17:15 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852274/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852302] Re: xenial/linux-snapdragon: 4.4.0-1130.138 -proposed tracker
** Summary changed: - xenial/linux-snapdragon: -proposed tracker + xenial/linux-snapdragon: 4.4.0-1130.138 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Manoj Iyer (manjo) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Manoj Iyer (manjo) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1852302 Title: xenial/linux-snapdragon: 4.4.0-1130.138 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New 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 promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Xenial: Confirmed 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 -- kernel-stable-master-bug: 1852306 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Packaging phase-changed: Friday, 15. November 2019 15:11 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded trackers: xenial/linux-snapdragon/dragonboard-kernel: bug 1852301 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852302/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852300] Re: xenial/linux-raspi2: 4.4.0-1126.135 -proposed tracker
** Summary changed: - xenial/linux-raspi2: -proposed tracker + xenial/linux-raspi2: 4.4.0-1126.135 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Manoj Iyer (manjo) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Manoj Iyer (manjo) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1852300 Title: xenial/linux-raspi2: 4.4.0-1126.135 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New 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 promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Xenial: Confirmed 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 -- kernel-stable-master-bug: 1852306 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Ready for Packaging phase-changed: Thursday, 14. November 2019 13:31 UTC reason: prepare-package: Pending -- version not specified trackers: xenial/linux-raspi2/pi2-kernel: bug 1852299 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852300/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848127] Re: [LTCTest][OPAL][OP930] Machine hangs after injecting the Machine Check Error
Bionic: merged from upstream stable: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849576 ** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Disco) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Eoan) Status: In Progress => Fix Committed ** Changed in: ubuntu-power-systems Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1848127 Title: [LTCTest][OPAL][OP930] Machine hangs after injecting the Machine Check Error Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: Fix Committed Bug description: [IMPACT] MCE test renders the system unresponsive on P9 open power hardware (Withersoon) [TEST] A test kernel is available in ppa:ubuntu-power-triage/lp1848127. Please see the [OTHER] section for test details and comment #7 for results with the PPA kernel. [FIX] IBM has identified the following patch that fixes this issue: commit 99ead78afd1128bfcebe7f88f3b102fb2da09aee Author: Balbir Singh Date: Tue Aug 20 13:43:47 2019 +0530 powerpc/mce: Fix MCE handling for huge pages [REGRESSION POTENTIAL] The patch is applicable the powerpc architecture and limited in scope to MCE handling for huge pages. Patch does not touch any generic code. Regression if any is limited to powerpc MCE handling. [OTHER] == Comment: #0 - PAVAMAN SUBRAMANIYAM - 2019-05-07 23:31:20 == Install a P9 Open Power Hardware with the latest OP930 Firmware images built from the upstream op-build git tree. root@witherspoon:~# cat /etc/os-release ID="openbmc-phosphor" NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro)" VERSION="ibm-v2.3" VERSION_ID="ibm-v2.3-476-g2d622cb-r32-0-g9973ab0" PRETTY_NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro) ibm-v2.3" BUILD_ID="ibm-v2.3-476-g2d622cb-r32" root@witherspoon:~# cat /var/lib/phosphor-software-manager/pnor/ro/VERSION open-power-witherspoon-v2.3-rc2-58-g59fd0743 buildroot-2019.02.2-17-g93b841d204 skiboot-v6.3-rc2 hostboot-19a436e occ-58e422d linux-5.0.9-openpower1-p3a4d5a4 petitboot-v1.10.3 machine-xml-a6f4df3 hostboot-binaries-hw043019a.940 capp-ucode-p9-dd2-v4 sbe-249671d hcode-hw040319a.940 Then enable sw xstop manually by using below command: root@ltc-wspoon11:~# nvram -p ibm,skiboot --update-config opal-sw-xstop=enable root@ltc-wspoon11:~# nvram -p ibm,skiboot --print-config "ibm,skiboot" Partition -- experimental-fast-reset=1 snarf-mode=noo opal-sw-xstop=enable Then from the Linux HOST injected the MCE UE Error on the machine as follows: root@ltc-wspoon11:~# ./probe_cpus.sh -L CHIP ID: 0 CORE ID: 0 THREADS: 4 CPUs: 0 1 2 3 CHIP ID: 0 CORE ID: 1 THREADS: 4 CPUs: 4 5 6 7 CHIP ID: 0 CORE ID: 2 THREADS: 4 CPUs: 8 9 10 11 CHIP ID: 0 CORE ID: 3 THREADS: 4 CPUs: 12 13 14 15 CHIP ID: 0 CORE ID: 6 THREADS: 4 CPUs: 16 17 18 19 CHIP ID: 0 CORE ID: 7 THREADS: 4 CPUs: 20 21 22 23 CHIP ID: 0 CORE ID: 8 THREADS: 4 CPUs: 24 25 26 27 CHIP ID: 0 CORE ID: 9 THREADS: 4 CPUs: 28 29 30 31 CHIP ID: 0 CORE ID: 10 THREADS: 4 CPUs: 32 33 34 35 CHIP ID: 0 CORE ID: 11 THREADS: 4 CPUs: 36 37 38 39 CHIP ID: 0 CORE ID: 12 THREADS: 4 CPUs: 40 41 42 43 CHIP ID: 0 CORE ID: 13 THREADS: 4 CPUs: 44 45 46 47 CHIP ID: 0 CORE ID: 16 THREADS: 4 CPUs: 48 49 50 51 CHIP ID: 0 CORE ID: 17 THREADS: 4 CPUs: 52 53 54 55 CHIP ID: 0 CORE ID: 18 THREADS: 4 CPUs: 56 57 58 59 CHIP ID: 0 CORE ID: 19 THREADS: 4 CPUs: 60 61 62 63 CHIP ID: 0 CORE ID: 20 THREADS: 4 CPUs: 64 65 66 67 CHIP ID: 0 CORE ID: 21 THREADS: 4 CPUs: 68 69 70 71 CHIP ID: 8 CORE ID: 6 THREADS: 4 CPUs: 72 73 74 75 CHIP ID: 8 CORE ID: 7 THREADS: 4 CPUs: 76 77 78 79 CHIP ID: 8 CORE ID: 8 THREADS: 4 CPUs: 80 81 82 83 CHIP ID: 8 CORE ID: 9 THREADS: 4 CPUs: 84 85 86 87 CHIP ID: 8 CORE ID: 10 THREADS: 4 CPUs: 88 89 90 91 CHIP ID: 8 CORE ID: 11 THREADS: 4 CPUs: 92 93 94 95 CHIP ID: 8 CORE ID: 12 THREADS: 4 CPUs: 96 97 98 99 CHIP ID: 8 CORE ID: 13 THREADS: 4 CPUs: 100 101 102 103 CHIP ID: 8 CORE ID: 14 THREADS: 4 CPUs: 104 105 106 107 CHIP ID: 8 CORE ID: 15 THREADS: 4 CPUs: 108 109 110 111 CHIP ID: 8 CORE ID: 16 THREADS: 4 CPUs: 112 113 114 115 CHIP ID: 8 CORE ID: 17 THREADS: 4 CPUs: 116 117 118 119 CHIP ID: 8 CORE ID: 18 THREADS: 4 CPUs: 120 121 122 123 CHIP ID: 8 CORE ID: 19 THREADS: 4 CPUs: 124 125
[Kernel-packages] [Bug 1848127] Re: [LTCTest][OPAL][OP930] Machine hangs after injecting the Machine Check Error
Disco: merged from upstream stable: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850870 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1848127 Title: [LTCTest][OPAL][OP930] Machine hangs after injecting the Machine Check Error Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Disco: In Progress Status in linux source package in Eoan: In Progress Bug description: [IMPACT] MCE test renders the system unresponsive on P9 open power hardware (Withersoon) [TEST] A test kernel is available in ppa:ubuntu-power-triage/lp1848127. Please see the [OTHER] section for test details and comment #7 for results with the PPA kernel. [FIX] IBM has identified the following patch that fixes this issue: commit 99ead78afd1128bfcebe7f88f3b102fb2da09aee Author: Balbir Singh Date: Tue Aug 20 13:43:47 2019 +0530 powerpc/mce: Fix MCE handling for huge pages [REGRESSION POTENTIAL] The patch is applicable the powerpc architecture and limited in scope to MCE handling for huge pages. Patch does not touch any generic code. Regression if any is limited to powerpc MCE handling. [OTHER] == Comment: #0 - PAVAMAN SUBRAMANIYAM - 2019-05-07 23:31:20 == Install a P9 Open Power Hardware with the latest OP930 Firmware images built from the upstream op-build git tree. root@witherspoon:~# cat /etc/os-release ID="openbmc-phosphor" NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro)" VERSION="ibm-v2.3" VERSION_ID="ibm-v2.3-476-g2d622cb-r32-0-g9973ab0" PRETTY_NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro) ibm-v2.3" BUILD_ID="ibm-v2.3-476-g2d622cb-r32" root@witherspoon:~# cat /var/lib/phosphor-software-manager/pnor/ro/VERSION open-power-witherspoon-v2.3-rc2-58-g59fd0743 buildroot-2019.02.2-17-g93b841d204 skiboot-v6.3-rc2 hostboot-19a436e occ-58e422d linux-5.0.9-openpower1-p3a4d5a4 petitboot-v1.10.3 machine-xml-a6f4df3 hostboot-binaries-hw043019a.940 capp-ucode-p9-dd2-v4 sbe-249671d hcode-hw040319a.940 Then enable sw xstop manually by using below command: root@ltc-wspoon11:~# nvram -p ibm,skiboot --update-config opal-sw-xstop=enable root@ltc-wspoon11:~# nvram -p ibm,skiboot --print-config "ibm,skiboot" Partition -- experimental-fast-reset=1 snarf-mode=noo opal-sw-xstop=enable Then from the Linux HOST injected the MCE UE Error on the machine as follows: root@ltc-wspoon11:~# ./probe_cpus.sh -L CHIP ID: 0 CORE ID: 0 THREADS: 4 CPUs: 0 1 2 3 CHIP ID: 0 CORE ID: 1 THREADS: 4 CPUs: 4 5 6 7 CHIP ID: 0 CORE ID: 2 THREADS: 4 CPUs: 8 9 10 11 CHIP ID: 0 CORE ID: 3 THREADS: 4 CPUs: 12 13 14 15 CHIP ID: 0 CORE ID: 6 THREADS: 4 CPUs: 16 17 18 19 CHIP ID: 0 CORE ID: 7 THREADS: 4 CPUs: 20 21 22 23 CHIP ID: 0 CORE ID: 8 THREADS: 4 CPUs: 24 25 26 27 CHIP ID: 0 CORE ID: 9 THREADS: 4 CPUs: 28 29 30 31 CHIP ID: 0 CORE ID: 10 THREADS: 4 CPUs: 32 33 34 35 CHIP ID: 0 CORE ID: 11 THREADS: 4 CPUs: 36 37 38 39 CHIP ID: 0 CORE ID: 12 THREADS: 4 CPUs: 40 41 42 43 CHIP ID: 0 CORE ID: 13 THREADS: 4 CPUs: 44 45 46 47 CHIP ID: 0 CORE ID: 16 THREADS: 4 CPUs: 48 49 50 51 CHIP ID: 0 CORE ID: 17 THREADS: 4 CPUs: 52 53 54 55 CHIP ID: 0 CORE ID: 18 THREADS: 4 CPUs: 56 57 58 59 CHIP ID: 0 CORE ID: 19 THREADS: 4 CPUs: 60 61 62 63 CHIP ID: 0 CORE ID: 20 THREADS: 4 CPUs: 64 65 66 67 CHIP ID: 0 CORE ID: 21 THREADS: 4 CPUs: 68 69 70 71 CHIP ID: 8 CORE ID: 6 THREADS: 4 CPUs: 72 73 74 75 CHIP ID: 8 CORE ID: 7 THREADS: 4 CPUs: 76 77 78 79 CHIP ID: 8 CORE ID: 8 THREADS: 4 CPUs: 80 81 82 83 CHIP ID: 8 CORE ID: 9 THREADS: 4 CPUs: 84 85 86 87 CHIP ID: 8 CORE ID: 10 THREADS: 4 CPUs: 88 89 90 91 CHIP ID: 8 CORE ID: 11 THREADS: 4 CPUs: 92 93 94 95 CHIP ID: 8 CORE ID: 12 THREADS: 4 CPUs: 96 97 98 99 CHIP ID: 8 CORE ID: 13 THREADS: 4 CPUs: 100 101 102 103 CHIP ID: 8 CORE ID: 14 THREADS: 4 CPUs: 104 105 106 107 CHIP ID: 8 CORE ID: 15 THREADS: 4 CPUs: 108 109 110 111 CHIP ID: 8 CORE ID: 16 THREADS: 4 CPUs: 112 113 114 115 CHIP ID: 8 CORE ID: 17 THREADS: 4 CPUs: 116 117 118 119 CHIP ID: 8 CORE ID: 18 THREADS: 4 CPUs: 120 121 122 123 CHIP ID: 8 CORE ID: 19 THREADS: 4 CPUs: 124 125 126 127 CHIP ID: 8 CORE ID: 20 THREADS: 4 CPUs: 128 129 130 131 CHIP ID: 8 CORE ID: 21 THREADS: 4 CPUs: 132 133 134 135 CHIP ID: 8 CORE ID: 22 THREADS: 4 CPUs: 136 137 138 139 CHIP ID: 8 CORE ID: 23 THREADS: 4 CPUs: 140 141 142 143 - p[0] eq[0,1,2,3,4,5] ex[0,1,3,4,5,6,8,9,10] c[0,1,2,3,6,7,8,9,10,11,12,13,16,17,18,19,20,21] p[8]
[Kernel-packages] [Bug 1849281] Re: seccomp: fix SECCOMP_USER_NOTIF_FLAG_CONTINUE test
** Changed in: linux (Ubuntu Disco) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1849281 Title: seccomp: fix SECCOMP_USER_NOTIF_FLAG_CONTINUE test Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Fix Committed Status in linux source package in Disco: In Progress Status in linux source package in Eoan: In Progress Bug description: SRU Justification Impact: We recently backported SECCOMP_USER_NOTIF_FLAG_CONTINUE in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847744. On a kernel that supports SECCOMP_FILTER_FLAG_NEW_LISTENER but not SECCOMP_USER_NOTIF_FLAG_CONTINUE the selftests currently fail to compile. The reason is that the ifndef for SECCOMP_USER_NOTIF_FLAG_CONTINUE is placed under the ifndef for SECCOMP_FILTER_FLAG_NEW_LISTENER. Fix: The ifndef for SECCOMP_USER_NOTIF_FLAG_CONTINUE was placed under the ifndef for the SECCOMP_FILTER_FLAG_NEW_LISTENER feature. This will not work on systems that do support SECCOMP_FILTER_FLAG_NEW_LISTENER but do not support SECCOMP_USER_NOTIF_FLAG_CONTINUE. So move the latter ifndef out of the former ifndef's scope. Regression Potential: Limited to seccomp selftests. Test Case: Compile the selftests on a kernel that supports SECCOMP_FILTER_FLAG_NEW_LISTENER but does not support SECCOMP_USER_NOTIF_FLAG_CONTINUE and see that compilations succeeds. Target Kernels: All current LTS kernels with access to a 5.0 kernel. Patches: https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git/commit/?h=for-next/seccomp=2aa8d8d04ca29c3269154e1d48855e498be8882f To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1849281/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849281] Re: seccomp: fix SECCOMP_USER_NOTIF_FLAG_CONTINUE test
** Changed in: linux (Ubuntu Eoan) Status: Confirmed => In Progress ** Changed in: ubuntu-kernel-tests Importance: Undecided => High ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu Disco) Importance: Undecided => High ** Changed in: linux (Ubuntu Eoan) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1849281 Title: seccomp: fix SECCOMP_USER_NOTIF_FLAG_CONTINUE test Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Fix Committed Status in linux source package in Disco: Confirmed Status in linux source package in Eoan: In Progress Bug description: SRU Justification Impact: We recently backported SECCOMP_USER_NOTIF_FLAG_CONTINUE in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847744. On a kernel that supports SECCOMP_FILTER_FLAG_NEW_LISTENER but not SECCOMP_USER_NOTIF_FLAG_CONTINUE the selftests currently fail to compile. The reason is that the ifndef for SECCOMP_USER_NOTIF_FLAG_CONTINUE is placed under the ifndef for SECCOMP_FILTER_FLAG_NEW_LISTENER. Fix: The ifndef for SECCOMP_USER_NOTIF_FLAG_CONTINUE was placed under the ifndef for the SECCOMP_FILTER_FLAG_NEW_LISTENER feature. This will not work on systems that do support SECCOMP_FILTER_FLAG_NEW_LISTENER but do not support SECCOMP_USER_NOTIF_FLAG_CONTINUE. So move the latter ifndef out of the former ifndef's scope. Regression Potential: Limited to seccomp selftests. Test Case: Compile the selftests on a kernel that supports SECCOMP_FILTER_FLAG_NEW_LISTENER but does not support SECCOMP_USER_NOTIF_FLAG_CONTINUE and see that compilations succeeds. Target Kernels: All current LTS kernels with access to a 5.0 kernel. Patches: https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git/commit/?h=for-next/seccomp=2aa8d8d04ca29c3269154e1d48855e498be8882f To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1849281/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1847948] Re: Improve NVMe guest performance on Bionic QEMU
** Changed in: ubuntu-power-systems Status: Triaged => Fix Released ** Changed in: ubuntu-power-systems Status: Fix Released => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1847948 Title: Improve NVMe guest performance on Bionic QEMU Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: Fix Released Status in qemu package in Ubuntu: Fix Released Status in linux source package in Bionic: Won't Fix Status in qemu source package in Bionic: Triaged Bug description: [Impact] * In the past qemu has generally not allowd MSI-X BAR mapping on VFIO. But there can be platforms (like ppc64 spapr) that can and want to do exactly that. * Backport two patches from upstream (in since qemu 2.12 / Disco). * Due to that there is a tremendous speedup, especially useful with page size bigger than 4k. This avoids that being split into chunks and makes direct MMIO access possible for the guest. [Test Case] * On ppc64 pass through an NVME device to the guest and run I/O benchmarks, see below for Details how to set that up. Note: this needs the HWE kernel or another kernel fixup for [1]. Note: the test should also be done with the non-HWE kernel, the expectation there is that it would not show the perf benefits, but still work fine [Regression Potential] * Changes: a) if the host driver allows mapping of MSI-X data the entire BAR is mapped. This is only done if the kernel reports that capability [1]. This ensures that only on kernels able to do so qemu does expose the new behavior (safe against regression in that regard) b) on ppc64 MSI-X emulation is disabled for VFIO devices this is local to just this HW and will not affect other HW. Generally the regressions that come to mind are slight changes in behavior (real HW vs the former emulation) that on some weird/old guests could cause trouble. But then it is limited to only PPC where only a small set of certified HW is really allowed. The mapping that might be added even on other platforms should not consume too much extra memory as long as it isn't used. Further since it depends on the kernel capability it isn't randomly issues on kernels where we expect it to fail. So while it is quite a change, it seems safe to me. [Other Info] * I know, one could as well call that a "feature", but it really is a performance bug fix more than anything else. Also the SRU policy allows exploitation/toleration of new HW especially for LTS releases. Therefore I think this is fine as SRU. [1]: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a32295c612c57990d17fb0f41e7134394b2f35f6 == Comment: #0 - Murilo Opsfelder Araujo - 2019-10-11 14:16:14 == ---Problem Description--- Back-port the following patches to Bionic QEMU to improve NVMe guest performance by more than 200%: ?vfio-pci: Allow mmap of MSIX BAR? https://git.qemu.org/?p=qemu.git;a=commit;h=ae0215b2bb56a9d5321a185dde133bfdd306a4c0 ?ppc/spapr, vfio: Turn off MSIX emulation for VFIO devices? https://git.qemu.org/?p=qemu.git;a=commit;h=fcad0d2121976df4b422b4007a5eb7fcaac01134 ---uname output--- na ---Additional Hardware Info--- 0030:01:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller 172Xa/172Xb (rev 01) Machine Type = AC922 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Install or setup a guest image and boot it. Once guest is running, passthrough the NVMe disk to the guest using the XML: host$ cat nvme-disk.xml host$ virsh attach-device nvme-disk.xml --live On the guest, run fio benchmarks: guest$ fio --direct=1 --rw=randrw --refill_buffers --norandommap --randrepeat=0 --ioengine=libaio --bs=4k --rwmixread=100 --iodepth=16 --runtime=60 --name=job1 --filename=/dev/nvme0n1 --numjobs=4 Results are similar with numjobs=4 and numjobs=64, respectively: READ: bw=385MiB/s (404MB/s), 78.0MiB/s-115MiB/s (81.8MB/s-120MB/s), io=11.3GiB (12.1GB), run=30001-30001msec READ: bw=382MiB/s (400MB/s), 2684KiB/s-12.6MiB/s (2749kB/s-13.2MB/s), io=11.2GiB (12.0GB), run=30001-30009msec With the two patches applied, performance improved significantly for numjobs=4 and numjobs=64 cases, respectively: READ: bw=1191MiB/s (1249MB/s), 285MiB/s-309MiB/s (299MB/s-324MB/s), io=34.9GiB (37.5GB), run=30001-30001msec READ: bw=4273MiB/s (4481MB/s), 49.7MiB/s-113MiB/s (52.1MB/s-119MB/s), io=125GiB (134GB), run=30001-30005msec Userspace tool common name: qemu Userspace rpm: qemu The userspace tool has the following bit modes: 64-bit Userspace tool obtained from project
[Kernel-packages] [Bug 1850548] Re: Unable to install kdump tools: post install script returning fail
Would it be acceptable if we suggest a workaround of incorporating config file changes in the "diskless custom image" that you are using to boot? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1850548 Title: Unable to install kdump tools: post install script returning fail Status in The Ubuntu-power-systems project: Triaged Status in makedumpfile package in Ubuntu: New Bug description: ---Problem Description--- Unable to install Kdump-tools. ---Steps to Reproduce--- Unable to Install Kdump-tool Debian package kdump-tools_1.6.3-2_ppc64el.deb Note: Unable to install the Kdump-tool. The problem comes when postinst script is run: root@pok1-qz1-sr1-rk005-s10:~/tar# uname -a Linux pok1-qz1-sr1-rk005-s10 4.15.0-1039-ibm-gt #41-Ubuntu SMP Wed Oct 2 10:52:25 UTC 2019 ppc64le ppc64le ppc64le GNU/Linux root@pok1-qz1-sr1-rk005-s10:~/tar# dmesg | grep crash [0.00] Kernel command line: imgurl=http://192.168.0.2:80//install/netboot/ubuntu18.04/ppc64el/hostos-boot_bionic-4.15.0.1039-20191003-6f8d26a/rootimg.tar.gz XCAT=192.168.0.2:3001 XCATHTTPPORT=80 BOOTIF=08:94:EF:80:1B:54 console=tty0 console=hvc0,115200 default_hugepagesz=1G hugepagesz=1G hugepages=1 transparent_hugepage=never intel_iommu=on iommu=pt cloud-config-url=http://192.168.0.2/install/netboot/cloud-init/pok1-qz1-sr1-rk005-s10.txt ds=nocloud crashkernel=768M,low crashkernel=4G,high Error: = update-alternatives: using /usr/bin/bsd-write to provide /usr/bin/write (write) in auto mode^M update-alternatives: warning: skip creation of /usr/share/man/man1/write.1.gz because associated file /usr/share/man/man1/bsd-write.1.gz (of link group write) doesn't exist^M update-alternatives: using /usr/bin/bsd-from to provide /usr/bin/from (from) in auto mode^M update-alternatives: warning: skip creation of /usr/share/man/man1/from.1.gz because associated file /usr/share/man/man1/bsd-from.1.gz (of link group from) doesn't exist^M Setting up ifenslave (2.9ubuntu1) ...^M Setting up file (1:5.32-2ubuntu0.2) ...^M Setting up kdump-tools (1:1.6.3-2) ...^M ^M Creating config file /etc/default/kdump-tools with new version^M dpkg: error processing package kdump-tools (--configure):^M installed kdump-tools package post-installation script subprocess returned error exit status 1^M dpkg: dependency problems prevent configuration of linux-crashdump:^M linux-crashdump depends on kdump-tools; however:^M Package kdump-tools is not configured yet.^M ^M Detail Log: === root@pok1-qz1-sr1-rk005-s10:~/tar# dpkg -i libmagic1_5.32-2ubuntu0.2_ppc64el.deb (Reading database ... 65250 files and directories currently installed.) Preparing to unpack libmagic1_5.32-2ubuntu0.2_ppc64el.deb ... Unpacking libmagic1:ppc64el (1:5.32-2ubuntu0.2) over (1:5.32-2ubuntu0.2) ... Setting up libmagic1:ppc64el (1:5.32-2ubuntu0.2) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... root@pok1-qz1-sr1-rk005-s10:~/tar# dpkg -i libmagic-mgc_5.32-2ubuntu0.2_ppc64el.deb (Reading database ... 65250 files and directories currently installed.) Preparing to unpack libmagic-mgc_5.32-2ubuntu0.2_ppc64el.deb ... Unpacking libmagic-mgc (1:5.32-2ubuntu0.2) over (1:5.32-2ubuntu0.2) ... Setting up libmagic-mgc (1:5.32-2ubuntu0.2) ... root@pok1-qz1-sr1-rk005-s10:~/tar# dpkg -i file_5.32-2ubuntu0.2_ppc64el.deb (Reading database ... 65250 files and directories currently installed.) Preparing to unpack file_5.32-2ubuntu0.2_ppc64el.deb ... Unpacking file (1:5.32-2ubuntu0.2) over (1:5.32-2ubuntu0.2) ... Setting up file (1:5.32-2ubuntu0.2) ... root@pok1-qz1-sr1-rk005-s10:~/tar# dpkg -i bsdmainutils_11.1.2ubuntu1_ppc64el.deb (Reading database ... 65250 files and directories currently installed.) Preparing to unpack bsdmainutils_11.1.2ubuntu1_ppc64el.deb ... Unpacking bsdmainutils (11.1.2ubuntu1) over (11.1.2ubuntu1) ... Setting up bsdmainutils (11.1.2ubuntu1) ... root@pok1-qz1-sr1-rk005-s10:~/tar# dpkg -i makedumpfile_1.6.5-1ubuntu1~18.04.1_ppc64el.deb (Reading database ... 65250 files and directories currently installed.) Preparing to unpack makedumpfile_1.6.5-1ubuntu1~18.04.1_ppc64el.deb ... Unpacking makedumpfile (1:1.6.5-1ubuntu1~18.04.1) over (1:1.6.5-1ubuntu1~18.04.1) ... Setting up makedumpfile (1:1.6.5-1ubuntu1~18.04.1) ... root@pok1-qz1-sr1-rk005-s10:~/tar# dpkg -i kexec-tools_2.0.16-1ubuntu1.1_ppc64el.deb (Reading database ... 65250 files and directories currently installed.) Preparing to unpack kexec-tools_2.0.16-1ubuntu1.1_ppc64el.deb ... Unpacking kexec-tools (1:2.0.16-1ubuntu1.1) over (1:2.0.16-1ubuntu1.1) ... Setting up kexec-tools (1:2.0.16-1ubuntu1.1) ... debconf: unable to initialize frontend: Dialog debconf: (No usable dialog-like program
[Kernel-packages] [Bug 1850548] Re: Unable to install kdump tools: post install script returning fail
** Changed in: ubuntu-power-systems Importance: Undecided => Low -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1850548 Title: Unable to install kdump tools: post install script returning fail Status in The Ubuntu-power-systems project: Incomplete Status in makedumpfile package in Ubuntu: New Bug description: ---Problem Description--- Unable to install Kdump-tools. ---Steps to Reproduce--- Unable to Install Kdump-tool Debian package kdump-tools_1.6.3-2_ppc64el.deb Note: Unable to install the Kdump-tool. The problem comes when postinst script is run: root@pok1-qz1-sr1-rk005-s10:~/tar# uname -a Linux pok1-qz1-sr1-rk005-s10 4.15.0-1039-ibm-gt #41-Ubuntu SMP Wed Oct 2 10:52:25 UTC 2019 ppc64le ppc64le ppc64le GNU/Linux root@pok1-qz1-sr1-rk005-s10:~/tar# dmesg | grep crash [0.00] Kernel command line: imgurl=http://192.168.0.2:80//install/netboot/ubuntu18.04/ppc64el/hostos-boot_bionic-4.15.0.1039-20191003-6f8d26a/rootimg.tar.gz XCAT=192.168.0.2:3001 XCATHTTPPORT=80 BOOTIF=08:94:EF:80:1B:54 console=tty0 console=hvc0,115200 default_hugepagesz=1G hugepagesz=1G hugepages=1 transparent_hugepage=never intel_iommu=on iommu=pt cloud-config-url=http://192.168.0.2/install/netboot/cloud-init/pok1-qz1-sr1-rk005-s10.txt ds=nocloud crashkernel=768M,low crashkernel=4G,high Error: = update-alternatives: using /usr/bin/bsd-write to provide /usr/bin/write (write) in auto mode^M update-alternatives: warning: skip creation of /usr/share/man/man1/write.1.gz because associated file /usr/share/man/man1/bsd-write.1.gz (of link group write) doesn't exist^M update-alternatives: using /usr/bin/bsd-from to provide /usr/bin/from (from) in auto mode^M update-alternatives: warning: skip creation of /usr/share/man/man1/from.1.gz because associated file /usr/share/man/man1/bsd-from.1.gz (of link group from) doesn't exist^M Setting up ifenslave (2.9ubuntu1) ...^M Setting up file (1:5.32-2ubuntu0.2) ...^M Setting up kdump-tools (1:1.6.3-2) ...^M ^M Creating config file /etc/default/kdump-tools with new version^M dpkg: error processing package kdump-tools (--configure):^M installed kdump-tools package post-installation script subprocess returned error exit status 1^M dpkg: dependency problems prevent configuration of linux-crashdump:^M linux-crashdump depends on kdump-tools; however:^M Package kdump-tools is not configured yet.^M ^M Detail Log: === root@pok1-qz1-sr1-rk005-s10:~/tar# dpkg -i libmagic1_5.32-2ubuntu0.2_ppc64el.deb (Reading database ... 65250 files and directories currently installed.) Preparing to unpack libmagic1_5.32-2ubuntu0.2_ppc64el.deb ... Unpacking libmagic1:ppc64el (1:5.32-2ubuntu0.2) over (1:5.32-2ubuntu0.2) ... Setting up libmagic1:ppc64el (1:5.32-2ubuntu0.2) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... root@pok1-qz1-sr1-rk005-s10:~/tar# dpkg -i libmagic-mgc_5.32-2ubuntu0.2_ppc64el.deb (Reading database ... 65250 files and directories currently installed.) Preparing to unpack libmagic-mgc_5.32-2ubuntu0.2_ppc64el.deb ... Unpacking libmagic-mgc (1:5.32-2ubuntu0.2) over (1:5.32-2ubuntu0.2) ... Setting up libmagic-mgc (1:5.32-2ubuntu0.2) ... root@pok1-qz1-sr1-rk005-s10:~/tar# dpkg -i file_5.32-2ubuntu0.2_ppc64el.deb (Reading database ... 65250 files and directories currently installed.) Preparing to unpack file_5.32-2ubuntu0.2_ppc64el.deb ... Unpacking file (1:5.32-2ubuntu0.2) over (1:5.32-2ubuntu0.2) ... Setting up file (1:5.32-2ubuntu0.2) ... root@pok1-qz1-sr1-rk005-s10:~/tar# dpkg -i bsdmainutils_11.1.2ubuntu1_ppc64el.deb (Reading database ... 65250 files and directories currently installed.) Preparing to unpack bsdmainutils_11.1.2ubuntu1_ppc64el.deb ... Unpacking bsdmainutils (11.1.2ubuntu1) over (11.1.2ubuntu1) ... Setting up bsdmainutils (11.1.2ubuntu1) ... root@pok1-qz1-sr1-rk005-s10:~/tar# dpkg -i makedumpfile_1.6.5-1ubuntu1~18.04.1_ppc64el.deb (Reading database ... 65250 files and directories currently installed.) Preparing to unpack makedumpfile_1.6.5-1ubuntu1~18.04.1_ppc64el.deb ... Unpacking makedumpfile (1:1.6.5-1ubuntu1~18.04.1) over (1:1.6.5-1ubuntu1~18.04.1) ... Setting up makedumpfile (1:1.6.5-1ubuntu1~18.04.1) ... root@pok1-qz1-sr1-rk005-s10:~/tar# dpkg -i kexec-tools_2.0.16-1ubuntu1.1_ppc64el.deb (Reading database ... 65250 files and directories currently installed.) Preparing to unpack kexec-tools_2.0.16-1ubuntu1.1_ppc64el.deb ... Unpacking kexec-tools (1:2.0.16-1ubuntu1.1) over (1:2.0.16-1ubuntu1.1) ... Setting up kexec-tools (1:2.0.16-1ubuntu1.1) ... debconf: unable to initialize frontend: Dialog debconf: (No usable dialog-like program is installed, so the dialog based frontend cannot be used. at
[Kernel-packages] [Bug 1848127] Re: [LTCTest][OPAL][OP930] Machine hangs after injecting the Machine Check Error
IBM, Please test the Bionic *and* Disco kernels available in PPA: https://launchpad.net/~ubuntu-power-triage/+archive/ubuntu/lp1848127 Post the test output from *both* the kernels to this report. Once I get positive test results I can SRU the patches. ** Changed in: linux (Ubuntu Disco) Status: New => Incomplete ** Changed in: linux (Ubuntu Bionic) Status: New => Incomplete ** Changed in: ubuntu-power-systems Status: In Progress => Incomplete ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Manoj Iyer (manjo) ** Changed in: linux (Ubuntu Disco) Assignee: (unassigned) => Manoj Iyer (manjo) ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Critical ** Changed in: linux (Ubuntu Disco) Importance: Undecided => Critical -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1848127 Title: [LTCTest][OPAL][OP930] Machine hangs after injecting the Machine Check Error Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Incomplete Status in linux source package in Disco: Incomplete Status in linux source package in Eoan: In Progress Bug description: [IMPACT] MCE test renders the system unresponsive on P9 open power hardware (Withersoon) [TEST] A test kernel is available in ppa:ubuntu-power-triage/lp1848127. Please see the [OTHER] section for test details and comment #7 for results with the PPA kernel. [FIX] IBM has identified the following patch that fixes this issue: commit 99ead78afd1128bfcebe7f88f3b102fb2da09aee Author: Balbir Singh Date: Tue Aug 20 13:43:47 2019 +0530 powerpc/mce: Fix MCE handling for huge pages [REGRESSION POTENTIAL] The patch is applicable the powerpc architecture and limited in scope to MCE handling for huge pages. Patch does not touch any generic code. Regression if any is limited to powerpc MCE handling. [OTHER] == Comment: #0 - PAVAMAN SUBRAMANIYAM - 2019-05-07 23:31:20 == Install a P9 Open Power Hardware with the latest OP930 Firmware images built from the upstream op-build git tree. root@witherspoon:~# cat /etc/os-release ID="openbmc-phosphor" NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro)" VERSION="ibm-v2.3" VERSION_ID="ibm-v2.3-476-g2d622cb-r32-0-g9973ab0" PRETTY_NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro) ibm-v2.3" BUILD_ID="ibm-v2.3-476-g2d622cb-r32" root@witherspoon:~# cat /var/lib/phosphor-software-manager/pnor/ro/VERSION open-power-witherspoon-v2.3-rc2-58-g59fd0743 buildroot-2019.02.2-17-g93b841d204 skiboot-v6.3-rc2 hostboot-19a436e occ-58e422d linux-5.0.9-openpower1-p3a4d5a4 petitboot-v1.10.3 machine-xml-a6f4df3 hostboot-binaries-hw043019a.940 capp-ucode-p9-dd2-v4 sbe-249671d hcode-hw040319a.940 Then enable sw xstop manually by using below command: root@ltc-wspoon11:~# nvram -p ibm,skiboot --update-config opal-sw-xstop=enable root@ltc-wspoon11:~# nvram -p ibm,skiboot --print-config "ibm,skiboot" Partition -- experimental-fast-reset=1 snarf-mode=noo opal-sw-xstop=enable Then from the Linux HOST injected the MCE UE Error on the machine as follows: root@ltc-wspoon11:~# ./probe_cpus.sh -L CHIP ID: 0 CORE ID: 0 THREADS: 4 CPUs: 0 1 2 3 CHIP ID: 0 CORE ID: 1 THREADS: 4 CPUs: 4 5 6 7 CHIP ID: 0 CORE ID: 2 THREADS: 4 CPUs: 8 9 10 11 CHIP ID: 0 CORE ID: 3 THREADS: 4 CPUs: 12 13 14 15 CHIP ID: 0 CORE ID: 6 THREADS: 4 CPUs: 16 17 18 19 CHIP ID: 0 CORE ID: 7 THREADS: 4 CPUs: 20 21 22 23 CHIP ID: 0 CORE ID: 8 THREADS: 4 CPUs: 24 25 26 27 CHIP ID: 0 CORE ID: 9 THREADS: 4 CPUs: 28 29 30 31 CHIP ID: 0 CORE ID: 10 THREADS: 4 CPUs: 32 33 34 35 CHIP ID: 0 CORE ID: 11 THREADS: 4 CPUs: 36 37 38 39 CHIP ID: 0 CORE ID: 12 THREADS: 4 CPUs: 40 41 42 43 CHIP ID: 0 CORE ID: 13 THREADS: 4 CPUs: 44 45 46 47 CHIP ID: 0 CORE ID: 16 THREADS: 4 CPUs: 48 49 50 51 CHIP ID: 0 CORE ID: 17 THREADS: 4 CPUs: 52 53 54 55 CHIP ID: 0 CORE ID: 18 THREADS: 4 CPUs: 56 57 58 59 CHIP ID: 0 CORE ID: 19 THREADS: 4 CPUs: 60 61 62 63 CHIP ID: 0 CORE ID: 20 THREADS: 4 CPUs: 64 65 66 67 CHIP ID: 0 CORE ID: 21 THREADS: 4 CPUs: 68 69 70 71 CHIP ID: 8 CORE ID: 6 THREADS: 4 CPUs: 72 73 74 75 CHIP ID: 8 CORE ID: 7 THREADS: 4 CPUs: 76 77 78 79 CHIP ID: 8 CORE ID: 8 THREADS: 4 CPUs: 80 81 82 83 CHIP ID: 8 CORE ID: 9 THREADS: 4 CPUs: 84 85 86 87 CHIP ID: 8 CORE ID: 10 THREADS: 4 CPUs: 88 89 90 91 CHIP ID: 8 CORE ID: 11 THREADS: 4 CPUs: 92 93 94 95 CHIP ID: 8 CORE ID: 12 THREADS: 4 CPUs: 96 97 98 99 CHIP ID: 8 CORE ID: 13 T
[Kernel-packages] [Bug 1848193] Re: Fixup tlbie vs store ordering issue on POWER9
** Changed in: linux (Ubuntu)
Status: In Progress => Incomplete
** Changed in: ubuntu-power-systems
Status: In Progress => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1848193
Title:
Fixup tlbie vs store ordering issue on POWER9
Status in The Ubuntu-power-systems project:
Incomplete
Status in linux package in Ubuntu:
Incomplete
Bug description:
== Comment: #0 - Michael Ranweiler - 2019-10-07 01:52:38 ==
On POWER9, under some circumstances, a broadcast TLB invalidation will fail
to invalidate the ERAT cache on some threads when there are parallel
mtpidr/mtlpidr happening on other threads of the same core. This can cause
stores to continue to go to a page after it's unmapped.
The workaround is to force an ERAT flush using PID=0 or LPID=0 tlbie
flush. This additional TLB flush will cause the ERAT cache
invalidation. Since we are using PID=0 or LPID=0, we don't get
filtered out by the TLB snoop filtering logic.
We need to still follow this up with another tlbie to take care of
store vs tlbie ordering issue explained in commit: a5d4b5891c2f
("powerpc/mm: Fixup tlbie vs store ordering issue on POWER9"). The
presence of ERAT cache implies we can still get new stores and they
may miss store queue marking flush.
The upstream git commits to resolve the problem:
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes=677733e296b5c7a37c47da391fc70a43dc40bd67
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes=09ce98cacd51fcd0fa0af2f79d1e1d3192f4cbb0
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes=047e6575aec71d75b765c22111820c4776cd1c43
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1848193/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848127] Re: [LTCTest][OPAL][OP930] Machine hangs after injecting the Machine Check Error
** Changed in: ubuntu-power-systems Status: Triaged => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1848127 Title: [LTCTest][OPAL][OP930] Machine hangs after injecting the Machine Check Error Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: New Status in linux source package in Disco: New Status in linux source package in Eoan: In Progress Bug description: [IMPACT] MCE test renders the system unresponsive on P9 open power hardware (Withersoon) [TEST] A test kernel is available in ppa:ubuntu-power-triage/lp1848127. Please see the [OTHER] section for test details and comment #7 for results with the PPA kernel. [FIX] IBM has identified the following patch that fixes this issue: commit 99ead78afd1128bfcebe7f88f3b102fb2da09aee Author: Balbir Singh Date: Tue Aug 20 13:43:47 2019 +0530 powerpc/mce: Fix MCE handling for huge pages [REGRESSION POTENTIAL] The patch is applicable the powerpc architecture and limited in scope to MCE handling for huge pages. Patch does not touch any generic code. Regression if any is limited to powerpc MCE handling. [OTHER] == Comment: #0 - PAVAMAN SUBRAMANIYAM - 2019-05-07 23:31:20 == Install a P9 Open Power Hardware with the latest OP930 Firmware images built from the upstream op-build git tree. root@witherspoon:~# cat /etc/os-release ID="openbmc-phosphor" NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro)" VERSION="ibm-v2.3" VERSION_ID="ibm-v2.3-476-g2d622cb-r32-0-g9973ab0" PRETTY_NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro) ibm-v2.3" BUILD_ID="ibm-v2.3-476-g2d622cb-r32" root@witherspoon:~# cat /var/lib/phosphor-software-manager/pnor/ro/VERSION open-power-witherspoon-v2.3-rc2-58-g59fd0743 buildroot-2019.02.2-17-g93b841d204 skiboot-v6.3-rc2 hostboot-19a436e occ-58e422d linux-5.0.9-openpower1-p3a4d5a4 petitboot-v1.10.3 machine-xml-a6f4df3 hostboot-binaries-hw043019a.940 capp-ucode-p9-dd2-v4 sbe-249671d hcode-hw040319a.940 Then enable sw xstop manually by using below command: root@ltc-wspoon11:~# nvram -p ibm,skiboot --update-config opal-sw-xstop=enable root@ltc-wspoon11:~# nvram -p ibm,skiboot --print-config "ibm,skiboot" Partition -- experimental-fast-reset=1 snarf-mode=noo opal-sw-xstop=enable Then from the Linux HOST injected the MCE UE Error on the machine as follows: root@ltc-wspoon11:~# ./probe_cpus.sh -L CHIP ID: 0 CORE ID: 0 THREADS: 4 CPUs: 0 1 2 3 CHIP ID: 0 CORE ID: 1 THREADS: 4 CPUs: 4 5 6 7 CHIP ID: 0 CORE ID: 2 THREADS: 4 CPUs: 8 9 10 11 CHIP ID: 0 CORE ID: 3 THREADS: 4 CPUs: 12 13 14 15 CHIP ID: 0 CORE ID: 6 THREADS: 4 CPUs: 16 17 18 19 CHIP ID: 0 CORE ID: 7 THREADS: 4 CPUs: 20 21 22 23 CHIP ID: 0 CORE ID: 8 THREADS: 4 CPUs: 24 25 26 27 CHIP ID: 0 CORE ID: 9 THREADS: 4 CPUs: 28 29 30 31 CHIP ID: 0 CORE ID: 10 THREADS: 4 CPUs: 32 33 34 35 CHIP ID: 0 CORE ID: 11 THREADS: 4 CPUs: 36 37 38 39 CHIP ID: 0 CORE ID: 12 THREADS: 4 CPUs: 40 41 42 43 CHIP ID: 0 CORE ID: 13 THREADS: 4 CPUs: 44 45 46 47 CHIP ID: 0 CORE ID: 16 THREADS: 4 CPUs: 48 49 50 51 CHIP ID: 0 CORE ID: 17 THREADS: 4 CPUs: 52 53 54 55 CHIP ID: 0 CORE ID: 18 THREADS: 4 CPUs: 56 57 58 59 CHIP ID: 0 CORE ID: 19 THREADS: 4 CPUs: 60 61 62 63 CHIP ID: 0 CORE ID: 20 THREADS: 4 CPUs: 64 65 66 67 CHIP ID: 0 CORE ID: 21 THREADS: 4 CPUs: 68 69 70 71 CHIP ID: 8 CORE ID: 6 THREADS: 4 CPUs: 72 73 74 75 CHIP ID: 8 CORE ID: 7 THREADS: 4 CPUs: 76 77 78 79 CHIP ID: 8 CORE ID: 8 THREADS: 4 CPUs: 80 81 82 83 CHIP ID: 8 CORE ID: 9 THREADS: 4 CPUs: 84 85 86 87 CHIP ID: 8 CORE ID: 10 THREADS: 4 CPUs: 88 89 90 91 CHIP ID: 8 CORE ID: 11 THREADS: 4 CPUs: 92 93 94 95 CHIP ID: 8 CORE ID: 12 THREADS: 4 CPUs: 96 97 98 99 CHIP ID: 8 CORE ID: 13 THREADS: 4 CPUs: 100 101 102 103 CHIP ID: 8 CORE ID: 14 THREADS: 4 CPUs: 104 105 106 107 CHIP ID: 8 CORE ID: 15 THREADS: 4 CPUs: 108 109 110 111 CHIP ID: 8 CORE ID: 16 THREADS: 4 CPUs: 112 113 114 115 CHIP ID: 8 CORE ID: 17 THREADS: 4 CPUs: 116 117 118 119 CHIP ID: 8 CORE ID: 18 THREADS: 4 CPUs: 120 121 122 123 CHIP ID: 8 CORE ID: 19 THREADS: 4 CPUs: 124 125 126 127 CHIP ID: 8 CORE ID: 20 THREADS: 4 CPUs: 128 129 130 131 CHIP ID: 8 CORE ID: 21 THREADS: 4 CPUs: 132 133 134 135 CHIP ID: 8 CORE ID: 22 THREADS: 4 CPUs: 136 137 138 139 CHIP ID: 8 CORE ID: 23 THREADS: 4 CPUs: 140 141 142 143 - p[0] eq[0,1,2,3,4,5] ex[0,1,3,4,5,6,8,9,10] c[0,1,2,3,6,7,8,9,10,11,12,13,16,17,18,19,20,21] p[8] eq[1,2,3,4,5] ex[3,4,5,6,7,8,9,10,11]
[Kernel-packages] [Bug 1848193] Re: Fixup tlbie vs store ordering issue on POWER9
** Changed in: linux (Ubuntu)
Status: New => In Progress
** Changed in: ubuntu-power-systems
Status: New => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1848193
Title:
Fixup tlbie vs store ordering issue on POWER9
Status in The Ubuntu-power-systems project:
In Progress
Status in linux package in Ubuntu:
In Progress
Bug description:
== Comment: #0 - Michael Ranweiler - 2019-10-07 01:52:38 ==
On POWER9, under some circumstances, a broadcast TLB invalidation will fail
to invalidate the ERAT cache on some threads when there are parallel
mtpidr/mtlpidr happening on other threads of the same core. This can cause
stores to continue to go to a page after it's unmapped.
The workaround is to force an ERAT flush using PID=0 or LPID=0 tlbie
flush. This additional TLB flush will cause the ERAT cache
invalidation. Since we are using PID=0 or LPID=0, we don't get
filtered out by the TLB snoop filtering logic.
We need to still follow this up with another tlbie to take care of
store vs tlbie ordering issue explained in commit: a5d4b5891c2f
("powerpc/mm: Fixup tlbie vs store ordering issue on POWER9"). The
presence of ERAT cache implies we can still get new stores and they
may miss store queue marking flush.
The upstream git commits to resolve the problem:
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes=677733e296b5c7a37c47da391fc70a43dc40bd67
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes=09ce98cacd51fcd0fa0af2f79d1e1d3192f4cbb0
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes=047e6575aec71d75b765c22111820c4776cd1c43
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1848193/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848193] Re: Fixup tlbie vs store ordering issue on POWER9
IBM can you please test the Eoan kernel in this PPA:
https://launchpad.net/~ubuntu-power-triage/+archive/ubuntu/lp1848193/
Also, please share the following information with us:
1. Your testcase, and instructions on how to run the test cases.
2. Your system config information and firmware levels.
3. Is there any significant customer impact if this is not backported to
earlier releases?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1848193
Title:
Fixup tlbie vs store ordering issue on POWER9
Status in The Ubuntu-power-systems project:
New
Status in linux package in Ubuntu:
New
Bug description:
== Comment: #0 - Michael Ranweiler - 2019-10-07 01:52:38 ==
On POWER9, under some circumstances, a broadcast TLB invalidation will fail
to invalidate the ERAT cache on some threads when there are parallel
mtpidr/mtlpidr happening on other threads of the same core. This can cause
stores to continue to go to a page after it's unmapped.
The workaround is to force an ERAT flush using PID=0 or LPID=0 tlbie
flush. This additional TLB flush will cause the ERAT cache
invalidation. Since we are using PID=0 or LPID=0, we don't get
filtered out by the TLB snoop filtering logic.
We need to still follow this up with another tlbie to take care of
store vs tlbie ordering issue explained in commit: a5d4b5891c2f
("powerpc/mm: Fixup tlbie vs store ordering issue on POWER9"). The
presence of ERAT cache implies we can still get new stores and they
may miss store queue marking flush.
The upstream git commits to resolve the problem:
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes=677733e296b5c7a37c47da391fc70a43dc40bd67
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes=09ce98cacd51fcd0fa0af2f79d1e1d3192f4cbb0
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes=047e6575aec71d75b765c22111820c4776cd1c43
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1848193/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848193] Re: Fixup tlbie vs store ordering issue on POWER9
** Changed in: linux (Ubuntu)
Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) =>
Manoj Iyer (manjo)
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1848193
Title:
Fixup tlbie vs store ordering issue on POWER9
Status in The Ubuntu-power-systems project:
New
Status in linux package in Ubuntu:
New
Bug description:
== Comment: #0 - Michael Ranweiler - 2019-10-07 01:52:38 ==
On POWER9, under some circumstances, a broadcast TLB invalidation will fail
to invalidate the ERAT cache on some threads when there are parallel
mtpidr/mtlpidr happening on other threads of the same core. This can cause
stores to continue to go to a page after it's unmapped.
The workaround is to force an ERAT flush using PID=0 or LPID=0 tlbie
flush. This additional TLB flush will cause the ERAT cache
invalidation. Since we are using PID=0 or LPID=0, we don't get
filtered out by the TLB snoop filtering logic.
We need to still follow this up with another tlbie to take care of
store vs tlbie ordering issue explained in commit: a5d4b5891c2f
("powerpc/mm: Fixup tlbie vs store ordering issue on POWER9"). The
presence of ERAT cache implies we can still get new stores and they
may miss store queue marking flush.
The upstream git commits to resolve the problem:
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes=677733e296b5c7a37c47da391fc70a43dc40bd67
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes=09ce98cacd51fcd0fa0af2f79d1e1d3192f4cbb0
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=fixes=047e6575aec71d75b765c22111820c4776cd1c43
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1848193/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848127] Re: [LTCTest][OPAL][OP930] Machine hangs after injecting the Machine Check Error
SRU for Eoan: https://lists.ubuntu.com/archives/kernel- team/2019-October/104757.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1848127 Title: [LTCTest][OPAL][OP930] Machine hangs after injecting the Machine Check Error Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: New Status in linux source package in Bionic: New Status in linux source package in Disco: New Status in linux source package in Eoan: New Bug description: [IMPACT] MCE test renders the system unresponsive on P9 open power hardware (Withersoon) [TEST] A test kernel is available in ppa:ubuntu-power-triage/lp1848127. Please see the [OTHER] section for test details and comment #7 for results with the PPA kernel. [FIX] IBM has identified the following patch that fixes this issue: commit 99ead78afd1128bfcebe7f88f3b102fb2da09aee Author: Balbir Singh Date: Tue Aug 20 13:43:47 2019 +0530 powerpc/mce: Fix MCE handling for huge pages [REGRESSION POTENTIAL] The patch is applicable the powerpc architecture and limited in scope to MCE handling for huge pages. Patch does not touch any generic code. Regression if any is limited to powerpc MCE handling. [OTHER] == Comment: #0 - PAVAMAN SUBRAMANIYAM - 2019-05-07 23:31:20 == Install a P9 Open Power Hardware with the latest OP930 Firmware images built from the upstream op-build git tree. root@witherspoon:~# cat /etc/os-release ID="openbmc-phosphor" NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro)" VERSION="ibm-v2.3" VERSION_ID="ibm-v2.3-476-g2d622cb-r32-0-g9973ab0" PRETTY_NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro) ibm-v2.3" BUILD_ID="ibm-v2.3-476-g2d622cb-r32" root@witherspoon:~# cat /var/lib/phosphor-software-manager/pnor/ro/VERSION open-power-witherspoon-v2.3-rc2-58-g59fd0743 buildroot-2019.02.2-17-g93b841d204 skiboot-v6.3-rc2 hostboot-19a436e occ-58e422d linux-5.0.9-openpower1-p3a4d5a4 petitboot-v1.10.3 machine-xml-a6f4df3 hostboot-binaries-hw043019a.940 capp-ucode-p9-dd2-v4 sbe-249671d hcode-hw040319a.940 Then enable sw xstop manually by using below command: root@ltc-wspoon11:~# nvram -p ibm,skiboot --update-config opal-sw-xstop=enable root@ltc-wspoon11:~# nvram -p ibm,skiboot --print-config "ibm,skiboot" Partition -- experimental-fast-reset=1 snarf-mode=noo opal-sw-xstop=enable Then from the Linux HOST injected the MCE UE Error on the machine as follows: root@ltc-wspoon11:~# ./probe_cpus.sh -L CHIP ID: 0 CORE ID: 0 THREADS: 4 CPUs: 0 1 2 3 CHIP ID: 0 CORE ID: 1 THREADS: 4 CPUs: 4 5 6 7 CHIP ID: 0 CORE ID: 2 THREADS: 4 CPUs: 8 9 10 11 CHIP ID: 0 CORE ID: 3 THREADS: 4 CPUs: 12 13 14 15 CHIP ID: 0 CORE ID: 6 THREADS: 4 CPUs: 16 17 18 19 CHIP ID: 0 CORE ID: 7 THREADS: 4 CPUs: 20 21 22 23 CHIP ID: 0 CORE ID: 8 THREADS: 4 CPUs: 24 25 26 27 CHIP ID: 0 CORE ID: 9 THREADS: 4 CPUs: 28 29 30 31 CHIP ID: 0 CORE ID: 10 THREADS: 4 CPUs: 32 33 34 35 CHIP ID: 0 CORE ID: 11 THREADS: 4 CPUs: 36 37 38 39 CHIP ID: 0 CORE ID: 12 THREADS: 4 CPUs: 40 41 42 43 CHIP ID: 0 CORE ID: 13 THREADS: 4 CPUs: 44 45 46 47 CHIP ID: 0 CORE ID: 16 THREADS: 4 CPUs: 48 49 50 51 CHIP ID: 0 CORE ID: 17 THREADS: 4 CPUs: 52 53 54 55 CHIP ID: 0 CORE ID: 18 THREADS: 4 CPUs: 56 57 58 59 CHIP ID: 0 CORE ID: 19 THREADS: 4 CPUs: 60 61 62 63 CHIP ID: 0 CORE ID: 20 THREADS: 4 CPUs: 64 65 66 67 CHIP ID: 0 CORE ID: 21 THREADS: 4 CPUs: 68 69 70 71 CHIP ID: 8 CORE ID: 6 THREADS: 4 CPUs: 72 73 74 75 CHIP ID: 8 CORE ID: 7 THREADS: 4 CPUs: 76 77 78 79 CHIP ID: 8 CORE ID: 8 THREADS: 4 CPUs: 80 81 82 83 CHIP ID: 8 CORE ID: 9 THREADS: 4 CPUs: 84 85 86 87 CHIP ID: 8 CORE ID: 10 THREADS: 4 CPUs: 88 89 90 91 CHIP ID: 8 CORE ID: 11 THREADS: 4 CPUs: 92 93 94 95 CHIP ID: 8 CORE ID: 12 THREADS: 4 CPUs: 96 97 98 99 CHIP ID: 8 CORE ID: 13 THREADS: 4 CPUs: 100 101 102 103 CHIP ID: 8 CORE ID: 14 THREADS: 4 CPUs: 104 105 106 107 CHIP ID: 8 CORE ID: 15 THREADS: 4 CPUs: 108 109 110 111 CHIP ID: 8 CORE ID: 16 THREADS: 4 CPUs: 112 113 114 115 CHIP ID: 8 CORE ID: 17 THREADS: 4 CPUs: 116 117 118 119 CHIP ID: 8 CORE ID: 18 THREADS: 4 CPUs: 120 121 122 123 CHIP ID: 8 CORE ID: 19 THREADS: 4 CPUs: 124 125 126 127 CHIP ID: 8 CORE ID: 20 THREADS: 4 CPUs: 128 129 130 131 CHIP ID: 8 CORE ID: 21 THREADS: 4 CPUs: 132 133 134 135 CHIP ID: 8 CORE ID: 22 THREADS: 4 CPUs: 136 137 138 139 CHIP ID: 8 CORE ID: 23 THREADS: 4 CPUs: 140 141 142 143 - p[0] eq[0,1,2,3,4,5] ex[0,1,3,4,5,6,8,9,10] c[0,1,2,3,6,7,8,9,10,11,12,13,16,17,18,19,20,21] p[8] eq[1,2,3,4,5] ex[3,4,5,6,7,8,9,10,11]
[Kernel-packages] [Bug 1848127] Re: [LTCTest][OPAL][OP930] Machine hangs after injecting the Machine Check Error
** Description changed: + [IMPACT] + MCE test renders the system unresponsive on P9 open power hardware (Withersoon) + + [TEST] + A test kernel is available in ppa:ubuntu-power-triage/lp1848127. Please see the [OTHER] section for test details and comment #7 for results with the PPA kernel. + + [FIX] + IBM has identified the following patch that fixes this issue: + commit 99ead78afd1128bfcebe7f88f3b102fb2da09aee + Author: Balbir Singh + Date: Tue Aug 20 13:43:47 2019 +0530 + + powerpc/mce: Fix MCE handling for huge pages + + [REGRESSION POTENTIAL] + The patch is applicable the powerpc architecture and limited in scope to MCE handling for huge pages. Patch does not touch any generic code. Regression if any is limited to powerpc MCE handling. + + [OTHER] == Comment: #0 - PAVAMAN SUBRAMANIYAM - 2019-05-07 23:31:20 == Install a P9 Open Power Hardware with the latest OP930 Firmware images built from the upstream op-build git tree. root@witherspoon:~# cat /etc/os-release ID="openbmc-phosphor" NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro)" VERSION="ibm-v2.3" VERSION_ID="ibm-v2.3-476-g2d622cb-r32-0-g9973ab0" PRETTY_NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro) ibm-v2.3" BUILD_ID="ibm-v2.3-476-g2d622cb-r32" root@witherspoon:~# cat /var/lib/phosphor-software-manager/pnor/ro/VERSION - open-power-witherspoon-v2.3-rc2-58-g59fd0743 - buildroot-2019.02.2-17-g93b841d204 - skiboot-v6.3-rc2 - hostboot-19a436e - occ-58e422d - linux-5.0.9-openpower1-p3a4d5a4 - petitboot-v1.10.3 - machine-xml-a6f4df3 - hostboot-binaries-hw043019a.940 - capp-ucode-p9-dd2-v4 - sbe-249671d - hcode-hw040319a.940 + open-power-witherspoon-v2.3-rc2-58-g59fd0743 + buildroot-2019.02.2-17-g93b841d204 + skiboot-v6.3-rc2 + hostboot-19a436e + occ-58e422d + linux-5.0.9-openpower1-p3a4d5a4 + petitboot-v1.10.3 + machine-xml-a6f4df3 + hostboot-binaries-hw043019a.940 + capp-ucode-p9-dd2-v4 + sbe-249671d + hcode-hw040319a.940 Then enable sw xstop manually by using below command: root@ltc-wspoon11:~# nvram -p ibm,skiboot --update-config opal-sw-xstop=enable root@ltc-wspoon11:~# nvram -p ibm,skiboot --print-config "ibm,skiboot" Partition -- experimental-fast-reset=1 snarf-mode=noo opal-sw-xstop=enable Then from the Linux HOST injected the MCE UE Error on the machine as follows: root@ltc-wspoon11:~# ./probe_cpus.sh -L CHIP ID: 0 CORE ID: 0 THREADS: 4 CPUs: 0 1 2 3 CHIP ID: 0 CORE ID: 1 THREADS: 4 CPUs: 4 5 6 7 CHIP ID: 0 CORE ID: 2 THREADS: 4 CPUs: 8 9 10 11 CHIP ID: 0 CORE ID: 3 THREADS: 4 CPUs: 12 13 14 15 CHIP ID: 0 CORE ID: 6 THREADS: 4 CPUs: 16 17 18 19 CHIP ID: 0 CORE ID: 7 THREADS: 4 CPUs: 20 21 22 23 CHIP ID: 0 CORE ID: 8 THREADS: 4 CPUs: 24 25 26 27 CHIP ID: 0 CORE ID: 9 THREADS: 4 CPUs: 28 29 30 31 CHIP ID: 0 CORE ID: 10 THREADS: 4 CPUs: 32 33 34 35 CHIP ID: 0 CORE ID: 11 THREADS: 4 CPUs: 36 37 38 39 CHIP ID: 0 CORE ID: 12 THREADS: 4 CPUs: 40 41 42 43 CHIP ID: 0 CORE ID: 13 THREADS: 4 CPUs: 44 45 46 47 CHIP ID: 0 CORE ID: 16 THREADS: 4 CPUs: 48 49 50 51 CHIP ID: 0 CORE ID: 17 THREADS: 4 CPUs: 52 53 54 55 CHIP ID: 0 CORE ID: 18 THREADS: 4 CPUs: 56 57 58 59 CHIP ID: 0 CORE ID: 19 THREADS: 4 CPUs: 60 61 62 63 CHIP ID: 0 CORE ID: 20 THREADS: 4 CPUs: 64 65 66 67 CHIP ID: 0 CORE ID: 21 THREADS: 4 CPUs: 68 69 70 71 CHIP ID: 8 CORE ID: 6 THREADS: 4 CPUs: 72 73 74 75 CHIP ID: 8 CORE ID: 7 THREADS: 4 CPUs: 76 77 78 79 CHIP ID: 8 CORE ID: 8 THREADS: 4 CPUs: 80 81 82 83 CHIP ID: 8 CORE ID: 9 THREADS: 4 CPUs: 84 85 86 87 CHIP ID: 8 CORE ID: 10 THREADS: 4 CPUs: 88 89 90 91 CHIP ID: 8 CORE ID: 11 THREADS: 4 CPUs: 92 93 94 95 CHIP ID: 8 CORE ID: 12 THREADS: 4 CPUs: 96 97 98 99 CHIP ID: 8 CORE ID: 13 THREADS: 4 CPUs: 100 101 102 103 CHIP ID: 8 CORE ID: 14 THREADS: 4 CPUs: 104 105 106 107 CHIP ID: 8 CORE ID: 15 THREADS: 4 CPUs: 108 109 110 111 CHIP ID: 8 CORE ID: 16 THREADS: 4 CPUs: 112 113 114 115 CHIP ID: 8 CORE ID: 17 THREADS: 4 CPUs: 116 117 118 119 CHIP ID: 8 CORE ID: 18 THREADS: 4 CPUs: 120 121 122 123 CHIP ID: 8 CORE ID: 19 THREADS: 4 CPUs: 124 125 126 127 CHIP ID: 8 CORE ID: 20 THREADS: 4 CPUs: 128 129 130 131 CHIP ID: 8 CORE ID: 21 THREADS: 4 CPUs: 132 133 134 135 CHIP ID: 8 CORE ID: 22 THREADS: 4 CPUs: 136 137 138 139 CHIP ID: 8 CORE ID: 23 THREADS: 4 CPUs: 140 141 142 143 - p[0] -eq[0,1,2,3,4,5] -ex[0,1,3,4,5,6,8,9,10] - c[0,1,2,3,6,7,8,9,10,11,12,13,16,17,18,19,20,21] + eq[0,1,2,3,4,5] + ex[0,1,3,4,5,6,8,9,10] + c[0,1,2,3,6,7,8,9,10,11,12,13,16,17,18,19,20,21] p[8] -eq[1,2,3,4,5] -ex[3,4,5,6,7,8,9,10,11] - c[6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23]
[Kernel-packages] [Bug 1848127] Re: [LTCTest][OPAL][OP930] Machine hangs after injecting the Machine Check Error
Please test with the eoan kernel in this PPA https://launchpad.net /~ubuntu-power-triage/+archive/ubuntu/lp1848127/ and report back here. After you have successfully verified this kernel I will submit the SRU for Eoan. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1848127 Title: [LTCTest][OPAL][OP930] Machine hangs after injecting the Machine Check Error Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: New Status in linux source package in Bionic: New Status in linux source package in Disco: New Status in linux source package in Eoan: New Bug description: == Comment: #0 - PAVAMAN SUBRAMANIYAM - 2019-05-07 23:31:20 == Install a P9 Open Power Hardware with the latest OP930 Firmware images built from the upstream op-build git tree. root@witherspoon:~# cat /etc/os-release ID="openbmc-phosphor" NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro)" VERSION="ibm-v2.3" VERSION_ID="ibm-v2.3-476-g2d622cb-r32-0-g9973ab0" PRETTY_NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro) ibm-v2.3" BUILD_ID="ibm-v2.3-476-g2d622cb-r32" root@witherspoon:~# cat /var/lib/phosphor-software-manager/pnor/ro/VERSION open-power-witherspoon-v2.3-rc2-58-g59fd0743 buildroot-2019.02.2-17-g93b841d204 skiboot-v6.3-rc2 hostboot-19a436e occ-58e422d linux-5.0.9-openpower1-p3a4d5a4 petitboot-v1.10.3 machine-xml-a6f4df3 hostboot-binaries-hw043019a.940 capp-ucode-p9-dd2-v4 sbe-249671d hcode-hw040319a.940 Then enable sw xstop manually by using below command: root@ltc-wspoon11:~# nvram -p ibm,skiboot --update-config opal-sw-xstop=enable root@ltc-wspoon11:~# nvram -p ibm,skiboot --print-config "ibm,skiboot" Partition -- experimental-fast-reset=1 snarf-mode=noo opal-sw-xstop=enable Then from the Linux HOST injected the MCE UE Error on the machine as follows: root@ltc-wspoon11:~# ./probe_cpus.sh -L CHIP ID: 0 CORE ID: 0 THREADS: 4 CPUs: 0 1 2 3 CHIP ID: 0 CORE ID: 1 THREADS: 4 CPUs: 4 5 6 7 CHIP ID: 0 CORE ID: 2 THREADS: 4 CPUs: 8 9 10 11 CHIP ID: 0 CORE ID: 3 THREADS: 4 CPUs: 12 13 14 15 CHIP ID: 0 CORE ID: 6 THREADS: 4 CPUs: 16 17 18 19 CHIP ID: 0 CORE ID: 7 THREADS: 4 CPUs: 20 21 22 23 CHIP ID: 0 CORE ID: 8 THREADS: 4 CPUs: 24 25 26 27 CHIP ID: 0 CORE ID: 9 THREADS: 4 CPUs: 28 29 30 31 CHIP ID: 0 CORE ID: 10 THREADS: 4 CPUs: 32 33 34 35 CHIP ID: 0 CORE ID: 11 THREADS: 4 CPUs: 36 37 38 39 CHIP ID: 0 CORE ID: 12 THREADS: 4 CPUs: 40 41 42 43 CHIP ID: 0 CORE ID: 13 THREADS: 4 CPUs: 44 45 46 47 CHIP ID: 0 CORE ID: 16 THREADS: 4 CPUs: 48 49 50 51 CHIP ID: 0 CORE ID: 17 THREADS: 4 CPUs: 52 53 54 55 CHIP ID: 0 CORE ID: 18 THREADS: 4 CPUs: 56 57 58 59 CHIP ID: 0 CORE ID: 19 THREADS: 4 CPUs: 60 61 62 63 CHIP ID: 0 CORE ID: 20 THREADS: 4 CPUs: 64 65 66 67 CHIP ID: 0 CORE ID: 21 THREADS: 4 CPUs: 68 69 70 71 CHIP ID: 8 CORE ID: 6 THREADS: 4 CPUs: 72 73 74 75 CHIP ID: 8 CORE ID: 7 THREADS: 4 CPUs: 76 77 78 79 CHIP ID: 8 CORE ID: 8 THREADS: 4 CPUs: 80 81 82 83 CHIP ID: 8 CORE ID: 9 THREADS: 4 CPUs: 84 85 86 87 CHIP ID: 8 CORE ID: 10 THREADS: 4 CPUs: 88 89 90 91 CHIP ID: 8 CORE ID: 11 THREADS: 4 CPUs: 92 93 94 95 CHIP ID: 8 CORE ID: 12 THREADS: 4 CPUs: 96 97 98 99 CHIP ID: 8 CORE ID: 13 THREADS: 4 CPUs: 100 101 102 103 CHIP ID: 8 CORE ID: 14 THREADS: 4 CPUs: 104 105 106 107 CHIP ID: 8 CORE ID: 15 THREADS: 4 CPUs: 108 109 110 111 CHIP ID: 8 CORE ID: 16 THREADS: 4 CPUs: 112 113 114 115 CHIP ID: 8 CORE ID: 17 THREADS: 4 CPUs: 116 117 118 119 CHIP ID: 8 CORE ID: 18 THREADS: 4 CPUs: 120 121 122 123 CHIP ID: 8 CORE ID: 19 THREADS: 4 CPUs: 124 125 126 127 CHIP ID: 8 CORE ID: 20 THREADS: 4 CPUs: 128 129 130 131 CHIP ID: 8 CORE ID: 21 THREADS: 4 CPUs: 132 133 134 135 CHIP ID: 8 CORE ID: 22 THREADS: 4 CPUs: 136 137 138 139 CHIP ID: 8 CORE ID: 23 THREADS: 4 CPUs: 140 141 142 143 - p[0] eq[0,1,2,3,4,5] ex[0,1,3,4,5,6,8,9,10] c[0,1,2,3,6,7,8,9,10,11,12,13,16,17,18,19,20,21] p[8] eq[1,2,3,4,5] ex[3,4,5,6,7,8,9,10,11] c[6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23] - --Processor Layout--- p[0] +---EQ00+ +---EQ02+ +---EQ04+ |EX-0C0 | |EX-4C8 | |EX-8C16| + - - - - - + + - - - - - + + - - - - - + |EX-0C1 | |EX-4C9 | |EX-8C17| + - - - - - + + - - - - - + + - - - - - + |EX-1C2 | |EX-5C10| |EX-9C18| + - - - - - + + - - - - - + + - - - - - + |EX-1C3 | |EX-5C11| |EX-9C19| +---+
[Kernel-packages] [Bug 1848127] Re: [LTCTest][OPAL][OP930] Machine hangs after injecting the Machine Check Error
Please test with the eoan kernel in this PPA https://launchpad.net /~ubuntu-power-triage/+archive/ubuntu/lp1848127/+packages and report back here. sudo add-apt-repository ppa:ubuntu-power-triage/lp1848127 sudo apt-get update -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1848127 Title: [LTCTest][OPAL][OP930] Machine hangs after injecting the Machine Check Error Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: New Status in linux source package in Bionic: New Status in linux source package in Disco: New Status in linux source package in Eoan: New Bug description: == Comment: #0 - PAVAMAN SUBRAMANIYAM - 2019-05-07 23:31:20 == Install a P9 Open Power Hardware with the latest OP930 Firmware images built from the upstream op-build git tree. root@witherspoon:~# cat /etc/os-release ID="openbmc-phosphor" NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro)" VERSION="ibm-v2.3" VERSION_ID="ibm-v2.3-476-g2d622cb-r32-0-g9973ab0" PRETTY_NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro) ibm-v2.3" BUILD_ID="ibm-v2.3-476-g2d622cb-r32" root@witherspoon:~# cat /var/lib/phosphor-software-manager/pnor/ro/VERSION open-power-witherspoon-v2.3-rc2-58-g59fd0743 buildroot-2019.02.2-17-g93b841d204 skiboot-v6.3-rc2 hostboot-19a436e occ-58e422d linux-5.0.9-openpower1-p3a4d5a4 petitboot-v1.10.3 machine-xml-a6f4df3 hostboot-binaries-hw043019a.940 capp-ucode-p9-dd2-v4 sbe-249671d hcode-hw040319a.940 Then enable sw xstop manually by using below command: root@ltc-wspoon11:~# nvram -p ibm,skiboot --update-config opal-sw-xstop=enable root@ltc-wspoon11:~# nvram -p ibm,skiboot --print-config "ibm,skiboot" Partition -- experimental-fast-reset=1 snarf-mode=noo opal-sw-xstop=enable Then from the Linux HOST injected the MCE UE Error on the machine as follows: root@ltc-wspoon11:~# ./probe_cpus.sh -L CHIP ID: 0 CORE ID: 0 THREADS: 4 CPUs: 0 1 2 3 CHIP ID: 0 CORE ID: 1 THREADS: 4 CPUs: 4 5 6 7 CHIP ID: 0 CORE ID: 2 THREADS: 4 CPUs: 8 9 10 11 CHIP ID: 0 CORE ID: 3 THREADS: 4 CPUs: 12 13 14 15 CHIP ID: 0 CORE ID: 6 THREADS: 4 CPUs: 16 17 18 19 CHIP ID: 0 CORE ID: 7 THREADS: 4 CPUs: 20 21 22 23 CHIP ID: 0 CORE ID: 8 THREADS: 4 CPUs: 24 25 26 27 CHIP ID: 0 CORE ID: 9 THREADS: 4 CPUs: 28 29 30 31 CHIP ID: 0 CORE ID: 10 THREADS: 4 CPUs: 32 33 34 35 CHIP ID: 0 CORE ID: 11 THREADS: 4 CPUs: 36 37 38 39 CHIP ID: 0 CORE ID: 12 THREADS: 4 CPUs: 40 41 42 43 CHIP ID: 0 CORE ID: 13 THREADS: 4 CPUs: 44 45 46 47 CHIP ID: 0 CORE ID: 16 THREADS: 4 CPUs: 48 49 50 51 CHIP ID: 0 CORE ID: 17 THREADS: 4 CPUs: 52 53 54 55 CHIP ID: 0 CORE ID: 18 THREADS: 4 CPUs: 56 57 58 59 CHIP ID: 0 CORE ID: 19 THREADS: 4 CPUs: 60 61 62 63 CHIP ID: 0 CORE ID: 20 THREADS: 4 CPUs: 64 65 66 67 CHIP ID: 0 CORE ID: 21 THREADS: 4 CPUs: 68 69 70 71 CHIP ID: 8 CORE ID: 6 THREADS: 4 CPUs: 72 73 74 75 CHIP ID: 8 CORE ID: 7 THREADS: 4 CPUs: 76 77 78 79 CHIP ID: 8 CORE ID: 8 THREADS: 4 CPUs: 80 81 82 83 CHIP ID: 8 CORE ID: 9 THREADS: 4 CPUs: 84 85 86 87 CHIP ID: 8 CORE ID: 10 THREADS: 4 CPUs: 88 89 90 91 CHIP ID: 8 CORE ID: 11 THREADS: 4 CPUs: 92 93 94 95 CHIP ID: 8 CORE ID: 12 THREADS: 4 CPUs: 96 97 98 99 CHIP ID: 8 CORE ID: 13 THREADS: 4 CPUs: 100 101 102 103 CHIP ID: 8 CORE ID: 14 THREADS: 4 CPUs: 104 105 106 107 CHIP ID: 8 CORE ID: 15 THREADS: 4 CPUs: 108 109 110 111 CHIP ID: 8 CORE ID: 16 THREADS: 4 CPUs: 112 113 114 115 CHIP ID: 8 CORE ID: 17 THREADS: 4 CPUs: 116 117 118 119 CHIP ID: 8 CORE ID: 18 THREADS: 4 CPUs: 120 121 122 123 CHIP ID: 8 CORE ID: 19 THREADS: 4 CPUs: 124 125 126 127 CHIP ID: 8 CORE ID: 20 THREADS: 4 CPUs: 128 129 130 131 CHIP ID: 8 CORE ID: 21 THREADS: 4 CPUs: 132 133 134 135 CHIP ID: 8 CORE ID: 22 THREADS: 4 CPUs: 136 137 138 139 CHIP ID: 8 CORE ID: 23 THREADS: 4 CPUs: 140 141 142 143 - p[0] eq[0,1,2,3,4,5] ex[0,1,3,4,5,6,8,9,10] c[0,1,2,3,6,7,8,9,10,11,12,13,16,17,18,19,20,21] p[8] eq[1,2,3,4,5] ex[3,4,5,6,7,8,9,10,11] c[6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23] - --Processor Layout--- p[0] +---EQ00+ +---EQ02+ +---EQ04+ |EX-0C0 | |EX-4C8 | |EX-8C16| + - - - - - + + - - - - - + + - - - - - + |EX-0C1 | |EX-4C9 | |EX-8C17| + - - - - - + + - - - - - + + - - - - - + |EX-1C2 | |EX-5C10| |EX-9C18| + - - - - - + + - - - - - + + - - - - - + |EX-1C3 | |EX-5C11| |EX-9C19|
[Kernel-packages] [Bug 1848127] Re: [LTCTest][OPAL][OP930] Machine hangs after injecting the Machine Check Error
** Changed in: linux (Ubuntu Eoan) Assignee: Canonical Kernel Team (canonical-kernel-team) => Manoj Iyer (manjo) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1848127 Title: [LTCTest][OPAL][OP930] Machine hangs after injecting the Machine Check Error Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: New Status in linux source package in Bionic: New Status in linux source package in Disco: New Status in linux source package in Eoan: New Bug description: == Comment: #0 - PAVAMAN SUBRAMANIYAM - 2019-05-07 23:31:20 == Install a P9 Open Power Hardware with the latest OP930 Firmware images built from the upstream op-build git tree. root@witherspoon:~# cat /etc/os-release ID="openbmc-phosphor" NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro)" VERSION="ibm-v2.3" VERSION_ID="ibm-v2.3-476-g2d622cb-r32-0-g9973ab0" PRETTY_NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro) ibm-v2.3" BUILD_ID="ibm-v2.3-476-g2d622cb-r32" root@witherspoon:~# cat /var/lib/phosphor-software-manager/pnor/ro/VERSION open-power-witherspoon-v2.3-rc2-58-g59fd0743 buildroot-2019.02.2-17-g93b841d204 skiboot-v6.3-rc2 hostboot-19a436e occ-58e422d linux-5.0.9-openpower1-p3a4d5a4 petitboot-v1.10.3 machine-xml-a6f4df3 hostboot-binaries-hw043019a.940 capp-ucode-p9-dd2-v4 sbe-249671d hcode-hw040319a.940 Then enable sw xstop manually by using below command: root@ltc-wspoon11:~# nvram -p ibm,skiboot --update-config opal-sw-xstop=enable root@ltc-wspoon11:~# nvram -p ibm,skiboot --print-config "ibm,skiboot" Partition -- experimental-fast-reset=1 snarf-mode=noo opal-sw-xstop=enable Then from the Linux HOST injected the MCE UE Error on the machine as follows: root@ltc-wspoon11:~# ./probe_cpus.sh -L CHIP ID: 0 CORE ID: 0 THREADS: 4 CPUs: 0 1 2 3 CHIP ID: 0 CORE ID: 1 THREADS: 4 CPUs: 4 5 6 7 CHIP ID: 0 CORE ID: 2 THREADS: 4 CPUs: 8 9 10 11 CHIP ID: 0 CORE ID: 3 THREADS: 4 CPUs: 12 13 14 15 CHIP ID: 0 CORE ID: 6 THREADS: 4 CPUs: 16 17 18 19 CHIP ID: 0 CORE ID: 7 THREADS: 4 CPUs: 20 21 22 23 CHIP ID: 0 CORE ID: 8 THREADS: 4 CPUs: 24 25 26 27 CHIP ID: 0 CORE ID: 9 THREADS: 4 CPUs: 28 29 30 31 CHIP ID: 0 CORE ID: 10 THREADS: 4 CPUs: 32 33 34 35 CHIP ID: 0 CORE ID: 11 THREADS: 4 CPUs: 36 37 38 39 CHIP ID: 0 CORE ID: 12 THREADS: 4 CPUs: 40 41 42 43 CHIP ID: 0 CORE ID: 13 THREADS: 4 CPUs: 44 45 46 47 CHIP ID: 0 CORE ID: 16 THREADS: 4 CPUs: 48 49 50 51 CHIP ID: 0 CORE ID: 17 THREADS: 4 CPUs: 52 53 54 55 CHIP ID: 0 CORE ID: 18 THREADS: 4 CPUs: 56 57 58 59 CHIP ID: 0 CORE ID: 19 THREADS: 4 CPUs: 60 61 62 63 CHIP ID: 0 CORE ID: 20 THREADS: 4 CPUs: 64 65 66 67 CHIP ID: 0 CORE ID: 21 THREADS: 4 CPUs: 68 69 70 71 CHIP ID: 8 CORE ID: 6 THREADS: 4 CPUs: 72 73 74 75 CHIP ID: 8 CORE ID: 7 THREADS: 4 CPUs: 76 77 78 79 CHIP ID: 8 CORE ID: 8 THREADS: 4 CPUs: 80 81 82 83 CHIP ID: 8 CORE ID: 9 THREADS: 4 CPUs: 84 85 86 87 CHIP ID: 8 CORE ID: 10 THREADS: 4 CPUs: 88 89 90 91 CHIP ID: 8 CORE ID: 11 THREADS: 4 CPUs: 92 93 94 95 CHIP ID: 8 CORE ID: 12 THREADS: 4 CPUs: 96 97 98 99 CHIP ID: 8 CORE ID: 13 THREADS: 4 CPUs: 100 101 102 103 CHIP ID: 8 CORE ID: 14 THREADS: 4 CPUs: 104 105 106 107 CHIP ID: 8 CORE ID: 15 THREADS: 4 CPUs: 108 109 110 111 CHIP ID: 8 CORE ID: 16 THREADS: 4 CPUs: 112 113 114 115 CHIP ID: 8 CORE ID: 17 THREADS: 4 CPUs: 116 117 118 119 CHIP ID: 8 CORE ID: 18 THREADS: 4 CPUs: 120 121 122 123 CHIP ID: 8 CORE ID: 19 THREADS: 4 CPUs: 124 125 126 127 CHIP ID: 8 CORE ID: 20 THREADS: 4 CPUs: 128 129 130 131 CHIP ID: 8 CORE ID: 21 THREADS: 4 CPUs: 132 133 134 135 CHIP ID: 8 CORE ID: 22 THREADS: 4 CPUs: 136 137 138 139 CHIP ID: 8 CORE ID: 23 THREADS: 4 CPUs: 140 141 142 143 - p[0] eq[0,1,2,3,4,5] ex[0,1,3,4,5,6,8,9,10] c[0,1,2,3,6,7,8,9,10,11,12,13,16,17,18,19,20,21] p[8] eq[1,2,3,4,5] ex[3,4,5,6,7,8,9,10,11] c[6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23] - --Processor Layout--- p[0] +---EQ00+ +---EQ02+ +---EQ04+ |EX-0C0 | |EX-4C8 | |EX-8C16| + - - - - - + + - - - - - + + - - - - - + |EX-0C1 | |EX-4C9 | |EX-8C17| + - - - - - + + - - - - - + + - - - - - + |EX-1C2 | |EX-5C10| |EX-9C18| + - - - - - + + - - - - - + + - - - - - + |EX-1C3 | |EX-5C11| |EX-9C19| +---+ +---
[Kernel-packages] [Bug 1848127] Re: [LTCTest][OPAL][OP930] Machine hangs after injecting the Machine Check Error
** Also affects: linux (Ubuntu Eoan) Importance: Critical Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1848127 Title: [LTCTest][OPAL][OP930] Machine hangs after injecting the Machine Check Error Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: New Status in linux source package in Bionic: New Status in linux source package in Disco: New Status in linux source package in Eoan: New Bug description: == Comment: #0 - PAVAMAN SUBRAMANIYAM - 2019-05-07 23:31:20 == Install a P9 Open Power Hardware with the latest OP930 Firmware images built from the upstream op-build git tree. root@witherspoon:~# cat /etc/os-release ID="openbmc-phosphor" NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro)" VERSION="ibm-v2.3" VERSION_ID="ibm-v2.3-476-g2d622cb-r32-0-g9973ab0" PRETTY_NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro) ibm-v2.3" BUILD_ID="ibm-v2.3-476-g2d622cb-r32" root@witherspoon:~# cat /var/lib/phosphor-software-manager/pnor/ro/VERSION open-power-witherspoon-v2.3-rc2-58-g59fd0743 buildroot-2019.02.2-17-g93b841d204 skiboot-v6.3-rc2 hostboot-19a436e occ-58e422d linux-5.0.9-openpower1-p3a4d5a4 petitboot-v1.10.3 machine-xml-a6f4df3 hostboot-binaries-hw043019a.940 capp-ucode-p9-dd2-v4 sbe-249671d hcode-hw040319a.940 Then enable sw xstop manually by using below command: root@ltc-wspoon11:~# nvram -p ibm,skiboot --update-config opal-sw-xstop=enable root@ltc-wspoon11:~# nvram -p ibm,skiboot --print-config "ibm,skiboot" Partition -- experimental-fast-reset=1 snarf-mode=noo opal-sw-xstop=enable Then from the Linux HOST injected the MCE UE Error on the machine as follows: root@ltc-wspoon11:~# ./probe_cpus.sh -L CHIP ID: 0 CORE ID: 0 THREADS: 4 CPUs: 0 1 2 3 CHIP ID: 0 CORE ID: 1 THREADS: 4 CPUs: 4 5 6 7 CHIP ID: 0 CORE ID: 2 THREADS: 4 CPUs: 8 9 10 11 CHIP ID: 0 CORE ID: 3 THREADS: 4 CPUs: 12 13 14 15 CHIP ID: 0 CORE ID: 6 THREADS: 4 CPUs: 16 17 18 19 CHIP ID: 0 CORE ID: 7 THREADS: 4 CPUs: 20 21 22 23 CHIP ID: 0 CORE ID: 8 THREADS: 4 CPUs: 24 25 26 27 CHIP ID: 0 CORE ID: 9 THREADS: 4 CPUs: 28 29 30 31 CHIP ID: 0 CORE ID: 10 THREADS: 4 CPUs: 32 33 34 35 CHIP ID: 0 CORE ID: 11 THREADS: 4 CPUs: 36 37 38 39 CHIP ID: 0 CORE ID: 12 THREADS: 4 CPUs: 40 41 42 43 CHIP ID: 0 CORE ID: 13 THREADS: 4 CPUs: 44 45 46 47 CHIP ID: 0 CORE ID: 16 THREADS: 4 CPUs: 48 49 50 51 CHIP ID: 0 CORE ID: 17 THREADS: 4 CPUs: 52 53 54 55 CHIP ID: 0 CORE ID: 18 THREADS: 4 CPUs: 56 57 58 59 CHIP ID: 0 CORE ID: 19 THREADS: 4 CPUs: 60 61 62 63 CHIP ID: 0 CORE ID: 20 THREADS: 4 CPUs: 64 65 66 67 CHIP ID: 0 CORE ID: 21 THREADS: 4 CPUs: 68 69 70 71 CHIP ID: 8 CORE ID: 6 THREADS: 4 CPUs: 72 73 74 75 CHIP ID: 8 CORE ID: 7 THREADS: 4 CPUs: 76 77 78 79 CHIP ID: 8 CORE ID: 8 THREADS: 4 CPUs: 80 81 82 83 CHIP ID: 8 CORE ID: 9 THREADS: 4 CPUs: 84 85 86 87 CHIP ID: 8 CORE ID: 10 THREADS: 4 CPUs: 88 89 90 91 CHIP ID: 8 CORE ID: 11 THREADS: 4 CPUs: 92 93 94 95 CHIP ID: 8 CORE ID: 12 THREADS: 4 CPUs: 96 97 98 99 CHIP ID: 8 CORE ID: 13 THREADS: 4 CPUs: 100 101 102 103 CHIP ID: 8 CORE ID: 14 THREADS: 4 CPUs: 104 105 106 107 CHIP ID: 8 CORE ID: 15 THREADS: 4 CPUs: 108 109 110 111 CHIP ID: 8 CORE ID: 16 THREADS: 4 CPUs: 112 113 114 115 CHIP ID: 8 CORE ID: 17 THREADS: 4 CPUs: 116 117 118 119 CHIP ID: 8 CORE ID: 18 THREADS: 4 CPUs: 120 121 122 123 CHIP ID: 8 CORE ID: 19 THREADS: 4 CPUs: 124 125 126 127 CHIP ID: 8 CORE ID: 20 THREADS: 4 CPUs: 128 129 130 131 CHIP ID: 8 CORE ID: 21 THREADS: 4 CPUs: 132 133 134 135 CHIP ID: 8 CORE ID: 22 THREADS: 4 CPUs: 136 137 138 139 CHIP ID: 8 CORE ID: 23 THREADS: 4 CPUs: 140 141 142 143 - p[0] eq[0,1,2,3,4,5] ex[0,1,3,4,5,6,8,9,10] c[0,1,2,3,6,7,8,9,10,11,12,13,16,17,18,19,20,21] p[8] eq[1,2,3,4,5] ex[3,4,5,6,7,8,9,10,11] c[6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23] - --Processor Layout--- p[0] +---EQ00+ +---EQ02+ +---EQ04+ |EX-0C0 | |EX-4C8 | |EX-8C16| + - - - - - + + - - - - - + + - - - - - + |EX-0C1 | |EX-4C9 | |EX-8C17| + - - - - - + + - - - - - + + - - - - - + |EX-1C2 | |EX-5C10| |EX-9C18| + - - - - - + + - - - - - + + - - -
[Kernel-packages] [Bug 1848127] Re: [LTCTest][OPAL][OP930] Machine hangs after injecting the Machine Check Error
** Changed in: linux (Ubuntu) Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: linux (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1848127 Title: [LTCTest][OPAL][OP930] Machine hangs after injecting the Machine Check Error Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: New Bug description: == Comment: #0 - PAVAMAN SUBRAMANIYAM - 2019-05-07 23:31:20 == Install a P9 Open Power Hardware with the latest OP930 Firmware images built from the upstream op-build git tree. root@witherspoon:~# cat /etc/os-release ID="openbmc-phosphor" NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro)" VERSION="ibm-v2.3" VERSION_ID="ibm-v2.3-476-g2d622cb-r32-0-g9973ab0" PRETTY_NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro) ibm-v2.3" BUILD_ID="ibm-v2.3-476-g2d622cb-r32" root@witherspoon:~# cat /var/lib/phosphor-software-manager/pnor/ro/VERSION open-power-witherspoon-v2.3-rc2-58-g59fd0743 buildroot-2019.02.2-17-g93b841d204 skiboot-v6.3-rc2 hostboot-19a436e occ-58e422d linux-5.0.9-openpower1-p3a4d5a4 petitboot-v1.10.3 machine-xml-a6f4df3 hostboot-binaries-hw043019a.940 capp-ucode-p9-dd2-v4 sbe-249671d hcode-hw040319a.940 Then enable sw xstop manually by using below command: root@ltc-wspoon11:~# nvram -p ibm,skiboot --update-config opal-sw-xstop=enable root@ltc-wspoon11:~# nvram -p ibm,skiboot --print-config "ibm,skiboot" Partition -- experimental-fast-reset=1 snarf-mode=noo opal-sw-xstop=enable Then from the Linux HOST injected the MCE UE Error on the machine as follows: root@ltc-wspoon11:~# ./probe_cpus.sh -L CHIP ID: 0 CORE ID: 0 THREADS: 4 CPUs: 0 1 2 3 CHIP ID: 0 CORE ID: 1 THREADS: 4 CPUs: 4 5 6 7 CHIP ID: 0 CORE ID: 2 THREADS: 4 CPUs: 8 9 10 11 CHIP ID: 0 CORE ID: 3 THREADS: 4 CPUs: 12 13 14 15 CHIP ID: 0 CORE ID: 6 THREADS: 4 CPUs: 16 17 18 19 CHIP ID: 0 CORE ID: 7 THREADS: 4 CPUs: 20 21 22 23 CHIP ID: 0 CORE ID: 8 THREADS: 4 CPUs: 24 25 26 27 CHIP ID: 0 CORE ID: 9 THREADS: 4 CPUs: 28 29 30 31 CHIP ID: 0 CORE ID: 10 THREADS: 4 CPUs: 32 33 34 35 CHIP ID: 0 CORE ID: 11 THREADS: 4 CPUs: 36 37 38 39 CHIP ID: 0 CORE ID: 12 THREADS: 4 CPUs: 40 41 42 43 CHIP ID: 0 CORE ID: 13 THREADS: 4 CPUs: 44 45 46 47 CHIP ID: 0 CORE ID: 16 THREADS: 4 CPUs: 48 49 50 51 CHIP ID: 0 CORE ID: 17 THREADS: 4 CPUs: 52 53 54 55 CHIP ID: 0 CORE ID: 18 THREADS: 4 CPUs: 56 57 58 59 CHIP ID: 0 CORE ID: 19 THREADS: 4 CPUs: 60 61 62 63 CHIP ID: 0 CORE ID: 20 THREADS: 4 CPUs: 64 65 66 67 CHIP ID: 0 CORE ID: 21 THREADS: 4 CPUs: 68 69 70 71 CHIP ID: 8 CORE ID: 6 THREADS: 4 CPUs: 72 73 74 75 CHIP ID: 8 CORE ID: 7 THREADS: 4 CPUs: 76 77 78 79 CHIP ID: 8 CORE ID: 8 THREADS: 4 CPUs: 80 81 82 83 CHIP ID: 8 CORE ID: 9 THREADS: 4 CPUs: 84 85 86 87 CHIP ID: 8 CORE ID: 10 THREADS: 4 CPUs: 88 89 90 91 CHIP ID: 8 CORE ID: 11 THREADS: 4 CPUs: 92 93 94 95 CHIP ID: 8 CORE ID: 12 THREADS: 4 CPUs: 96 97 98 99 CHIP ID: 8 CORE ID: 13 THREADS: 4 CPUs: 100 101 102 103 CHIP ID: 8 CORE ID: 14 THREADS: 4 CPUs: 104 105 106 107 CHIP ID: 8 CORE ID: 15 THREADS: 4 CPUs: 108 109 110 111 CHIP ID: 8 CORE ID: 16 THREADS: 4 CPUs: 112 113 114 115 CHIP ID: 8 CORE ID: 17 THREADS: 4 CPUs: 116 117 118 119 CHIP ID: 8 CORE ID: 18 THREADS: 4 CPUs: 120 121 122 123 CHIP ID: 8 CORE ID: 19 THREADS: 4 CPUs: 124 125 126 127 CHIP ID: 8 CORE ID: 20 THREADS: 4 CPUs: 128 129 130 131 CHIP ID: 8 CORE ID: 21 THREADS: 4 CPUs: 132 133 134 135 CHIP ID: 8 CORE ID: 22 THREADS: 4 CPUs: 136 137 138 139 CHIP ID: 8 CORE ID: 23 THREADS: 4 CPUs: 140 141 142 143 - p[0] eq[0,1,2,3,4,5] ex[0,1,3,4,5,6,8,9,10] c[0,1,2,3,6,7,8,9,10,11,12,13,16,17,18,19,20,21] p[8] eq[1,2,3,4,5] ex[3,4,5,6,7,8,9,10,11] c[6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23] - --Processor Layout--- p[0] +---EQ00+ +---EQ02+ +---EQ04+ |EX-0C0 | |EX-4C8 | |EX-8C16| + - - - - - + + - - - - - + + - - - - - + |EX-0C1 | |EX-4C9 | |EX-8C17| + - - - - - + + - - - - - + + - - - - - + |EX-1C2 | |EX-5C10| |EX-9C18| + - - - - - + + - - - - - + + - - - - - + |EX-1C3 | |EX-5C11| |EX-9C19| +---+ +---+ +---+ +---EQ01+ +---EQ03+ +---EQ05+ | | |EX-6C12| |EX-10
[Kernel-packages] [Bug 1846237] Re: Kernel Panic while virsh dump of Guest with 300G RAM is triggered.
Adding the kernel track to this bug after checking with Michael (IBM). Although the bug was found in a flavor kernel of Ubuntu, it sounds like (from the notes in the description) that this might a generic issue with 18.04.3 and newer kernels. The next steps for IBM is to reproduce this issue on 18.04.3 or newer released kernel. Also, compare with the upstream kernel to see if issue was already fixed. You could use the mainline builds to compare https://kernel.ubuntu.com/~kernel-ppa/mainline/daily/current/ ** Changed in: libvirt (Ubuntu) Status: Triaged => Invalid ** Changed in: ubuntu-power-systems Assignee: Canonical Server Team (canonical-server) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1846237 Title: Kernel Panic while virsh dump of Guest with 300G RAM is triggered. Status in The Ubuntu-power-systems project: Triaged Status in libvirt package in Ubuntu: Invalid Status in linux package in Ubuntu: New Bug description: == Comment: #0 - HARIHARAN T. SUNDARESH REDDY - 2019-04-01 12:23:14 == ---Problem Description--- Kernel panic occurred when `virsh dump` is triggered on the guest with 300G of RAM. ---uname output--- Linux ltcgen6 4.15.0-1017.19-bz175922-ibm-gt #bz175922 SMP Thu Mar 21 09:34:09 CDT 2019 ppc64le ppc64le ppc64le GNU/Linux ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. Define guest with 300G RAM, Start the guest 2. Run the following command `virsh dump ubuntui_hsr /home/vm.core --memory-only --live' 3. Wait for some time, kernel panic will be see in the console. --Log--- [ 1692.657251] INFO: task journal-offline:7763 blocked for more than 120 seconds. [ 1692.657251] INFO: task journal-offline:7763 blocked for more than 120 seconds. [ 1692.657754] Not tainted 4.15.0-1017.19-bz175922-ibm-gt #bz175922 [ 1692.657754] Not tainted 4.15.0-1017.19-bz175922-ibm-gt #bz175922 [ 1692.658220] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 1692.658220] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 1692.658839] Kernel panic - not syncing: hung_task: blocked tasks [ 1692.658839] Kernel panic - not syncing: hung_task: blocked tasks [ 1692.659238] CPU: 48 PID: 785 Comm: khungtaskd Not tainted 4.15.0-1017.19-bz175922-ibm-gt #bz175922 [ 1692.659238] CPU: 48 PID: 785 Comm: khungtaskd Not tainted 4.15.0-1017.19-bz175922-ibm-gt #bz175922 [ 1692.659835] Call Trace: [ 1692.659835] Call Trace: [ 1692.660025] [c08fd0eefbf8] [c0cea13c] dump_stack+0xb0/0xf4 (unreliable) [ 1692.660025] [c08fd0eefbf8] [c0cea13c] dump_stack+0xb0/0xf4 (unreliable) [ 1692.660564] [c08fd0eefc38] [c0110020] panic+0x148/0x328 [ 1692.660564] [c08fd0eefc38] [c0110020] panic+0x148/0x328 [ 1692.661004] [c08fd0eefcd8] [c0233a08] watchdog+0x2c8/0x420 [ 1692.661004] [c08fd0eefcd8] [c0233a08] watchdog+0x2c8/0x420 [ 1692.661429] [c08fd0eefdb8] [c0140068] kthread+0x1a8/0x1b0 [ 1692.661429] [c08fd0eefdb8] [c0140068] kthread+0x1a8/0x1b0 [ 1692.661881] [c08fd0eefe28] [c000b654] ret_from_kernel_thread+0x5c/0x88 [ 1692.661881] [c08fd0eefe28] [c000b654] ret_from_kernel_thread+0x5c/0x88 [ 1692.662439] Sending IPI to other CPUs [ 1692.662439] Sending IPI to other CPUs [ 1693.971250] IPI complete [ 1693.971250] IPI complete [ 1694.122536] kexec: Starting switchover sequence. [ 1694.122536] kexec: Starting switchover sequence. [ 1827.285354188,3] PHB#0003[0:3]: CRESET: Unexpected slot state 0102, resetting... [ 1831.426449832,3] PHB#0030[8:0]: CRESET: Unexpected slot state 0102, resetting... [ 1832.158844758,3] PHB#0033[8:3]: CRESET: Unexpected slot state 0102, resetting... [ 1832.403055326,3] PHB#0034[8:4]: CRESET: Unexpected slot state 0102, resetting... [1.924644] integrity: Unable to open file: /etc/keys/x509_ima.der (-2) [1.924644] integrity: Unable to open file: /etc/keys/x509_ima.der (-2) [1.924647] integrity: Unable to open file: /etc/keys/x509_evm.der (-2) [1.924647] integrity: Unable to open file: /etc/keys/x509_evm.der (-2) [1.991351] vio vio: uevent: failed to send synthetic uevent [1.991351] vio vio: uevent: failed to send synthetic uevent [2.524824] nouveau
[Kernel-packages] [Bug 1846237] Re: Kernel Panic while virsh dump of Guest with 300G RAM is triggered.
** Also affects: linux Importance: Undecided Status: New ** No longer affects: linux ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1846237 Title: Kernel Panic while virsh dump of Guest with 300G RAM is triggered. Status in The Ubuntu-power-systems project: Triaged Status in libvirt package in Ubuntu: Triaged Status in linux package in Ubuntu: New Bug description: == Comment: #0 - HARIHARAN T. SUNDARESH REDDY - 2019-04-01 12:23:14 == ---Problem Description--- Kernel panic occurred when `virsh dump` is triggered on the guest with 300G of RAM. ---uname output--- Linux ltcgen6 4.15.0-1017.19-bz175922-ibm-gt #bz175922 SMP Thu Mar 21 09:34:09 CDT 2019 ppc64le ppc64le ppc64le GNU/Linux ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. Define guest with 300G RAM, Start the guest 2. Run the following command `virsh dump ubuntui_hsr /home/vm.core --memory-only --live' 3. Wait for some time, kernel panic will be see in the console. --Log--- [ 1692.657251] INFO: task journal-offline:7763 blocked for more than 120 seconds. [ 1692.657251] INFO: task journal-offline:7763 blocked for more than 120 seconds. [ 1692.657754] Not tainted 4.15.0-1017.19-bz175922-ibm-gt #bz175922 [ 1692.657754] Not tainted 4.15.0-1017.19-bz175922-ibm-gt #bz175922 [ 1692.658220] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 1692.658220] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 1692.658839] Kernel panic - not syncing: hung_task: blocked tasks [ 1692.658839] Kernel panic - not syncing: hung_task: blocked tasks [ 1692.659238] CPU: 48 PID: 785 Comm: khungtaskd Not tainted 4.15.0-1017.19-bz175922-ibm-gt #bz175922 [ 1692.659238] CPU: 48 PID: 785 Comm: khungtaskd Not tainted 4.15.0-1017.19-bz175922-ibm-gt #bz175922 [ 1692.659835] Call Trace: [ 1692.659835] Call Trace: [ 1692.660025] [c08fd0eefbf8] [c0cea13c] dump_stack+0xb0/0xf4 (unreliable) [ 1692.660025] [c08fd0eefbf8] [c0cea13c] dump_stack+0xb0/0xf4 (unreliable) [ 1692.660564] [c08fd0eefc38] [c0110020] panic+0x148/0x328 [ 1692.660564] [c08fd0eefc38] [c0110020] panic+0x148/0x328 [ 1692.661004] [c08fd0eefcd8] [c0233a08] watchdog+0x2c8/0x420 [ 1692.661004] [c08fd0eefcd8] [c0233a08] watchdog+0x2c8/0x420 [ 1692.661429] [c08fd0eefdb8] [c0140068] kthread+0x1a8/0x1b0 [ 1692.661429] [c08fd0eefdb8] [c0140068] kthread+0x1a8/0x1b0 [ 1692.661881] [c08fd0eefe28] [c000b654] ret_from_kernel_thread+0x5c/0x88 [ 1692.661881] [c08fd0eefe28] [c000b654] ret_from_kernel_thread+0x5c/0x88 [ 1692.662439] Sending IPI to other CPUs [ 1692.662439] Sending IPI to other CPUs [ 1693.971250] IPI complete [ 1693.971250] IPI complete [ 1694.122536] kexec: Starting switchover sequence. [ 1694.122536] kexec: Starting switchover sequence. [ 1827.285354188,3] PHB#0003[0:3]: CRESET: Unexpected slot state 0102, resetting... [ 1831.426449832,3] PHB#0030[8:0]: CRESET: Unexpected slot state 0102, resetting... [ 1832.158844758,3] PHB#0033[8:3]: CRESET: Unexpected slot state 0102, resetting... [ 1832.403055326,3] PHB#0034[8:4]: CRESET: Unexpected slot state 0102, resetting... [1.924644] integrity: Unable to open file: /etc/keys/x509_ima.der (-2) [1.924644] integrity: Unable to open file: /etc/keys/x509_ima.der (-2) [1.924647] integrity: Unable to open file: /etc/keys/x509_evm.der (-2) [1.924647] integrity: Unable to open file: /etc/keys/x509_evm.der (-2) [1.991351] vio vio: uevent: failed to send synthetic uevent [1.991351] vio vio: uevent: failed to send synthetic uevent [2.524824] nouveau 0004:04:00.0: unknown chipset (14a1) [2.524824] nouveau 0004:04:00.0: unknown chipset (14a1) [2.525314] nouveau 0004:05:00.0: unknown chipset (14a1) [2.525314] nouveau 0004:05:00.0: unknown chipset (14a1) [2.525831] nouveau 0035:03:00.0: unknown chipset (14a1) [2.525831] nouveau 0035:03:00.0: unknown chipset (14a1) [2.526315] nouveau 0035:04:00.0: unknown chipset (14a1) [2.526315] nouveau 0035:04:00.0: unknown chipset (14a1) /dev/sda2: recovering journal systemd-update-utmp.service
[Kernel-packages] [Bug 1845572] Re: udevadm trigger will fail when trying to add /sys/devices/vio/
** Changed in: ubuntu-power-systems Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1845572 Title: udevadm trigger will fail when trying to add /sys/devices/vio/ Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Bug description: [Impact] This will cause the installer to exit early, causing a kernel panic before any prompt to the user. This is restricted to some Power systems. [Test case] A build vmlinux was used to boot the installer, and a prompt was available. 'add' was written to /sys/devices/vio/uevent was written to, and no error was found. 'add' was written to /sys/devices/vio/*/uevent, and modalias information was found when 'udevadm monitor -p' was run in the background. A complete install was completed with a fixed kernel. [Regression potential] Events may be missing and coldplug/hotplug of vio devices may fail. That was tested in the test case and not found to be the case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1845572/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1845572] Re: udevadm trigger will fail when trying to add /sys/devices/vio/
** Also affects: ubuntu-power-systems Importance: Undecided Status: New ** Changed in: ubuntu-power-systems Importance: Undecided => Critical ** Changed in: ubuntu-power-systems Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1845572 Title: udevadm trigger will fail when trying to add /sys/devices/vio/ Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Bug description: [Impact] This will cause the installer to exit early, causing a kernel panic before any prompt to the user. This is restricted to some Power systems. [Test case] A build vmlinux was used to boot the installer, and a prompt was available. 'add' was written to /sys/devices/vio/uevent was written to, and no error was found. 'add' was written to /sys/devices/vio/*/uevent, and modalias information was found when 'udevadm monitor -p' was run in the background. A complete install was completed with a fixed kernel. [Regression potential] Events may be missing and coldplug/hotplug of vio devices may fail. That was tested in the test case and not found to be the case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1845572/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837726] Re: Installation fails on eoan/PowerVM : missing /dev/nvram
** Also affects: ubuntu-power-systems
Importance: Undecided
Status: New
** Changed in: ubuntu-power-systems
Importance: Undecided => High
** Changed in: ubuntu-power-systems
Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1837726
Title:
Installation fails on eoan/PowerVM : missing /dev/nvram
Status in The Ubuntu-power-systems project:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Bug description:
Hi,
since eoan and kernel 5.2, the installation fails when installing grub at the
end.
Actually /dev/nvram does not exist.
nvram support was previously built in the kernel and is now built as a module,
and the module is not shipped within the iso or in udebs.
This is probably due to commit d7d73492dc5f2 in Ubuntu's linux git tree :
---
commit d7d73492dc5f2ccc5c76b042341370838af148e4
Author: Seth Forshee
Date: Wed Jun 5 10:47:33 2019 -0500
UBUNTU: [Config] update annotations following config review
...
-CONFIG_NVRAMpolicy<{'amd64': 'm',
'i386': 'm'}>
+CONFIG_NVRAMpolicy<{'amd64': 'm',
'i386': 'm', 'ppc64el': 'm'}>
...
---
F.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1837726/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1690225] Re: nvidia-docker on ppc64le-ubuntu16.04 issue due to cross-thread naming if !PR_DUMPABLE
** Changed in: linux (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1690225 Title: nvidia-docker on ppc64le-ubuntu16.04 issue due to cross-thread naming if !PR_DUMPABLE 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: == Comment: #0 - Breno Henrique Leitao - 2017-05-11 15:30:52 == The PR_DUMPABLE flag causes the pid related paths of the proc file system to be owned by ROOT. The implementation of pthread_set/getname_np however needs access to /proc//task//comm. If PR_DUMPABLE is false this implementation is locked out. This patch installs a special permission function for the file "comm" that grants read and write access to all threads of the same group regardless of the ownership of the inode. For all other threads the function falls back to the generic inode permission check. Nvidia-docker issue on ppc64le: 1b3044e39a89cb1d4d5313da477e8dfea2b5232d This is fixed by commit 1b3044e39a89cb1d4d5313da477e8dfea2b5232d To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1690225/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1843533] Re: powerpc/tm: Fix restoring FP/VMX facility incorrectly on interrupts (CVE-2019-15031) / powerpc/tm: Fix FP/VMX unavailable exceptions inside a transaction (CVE-2019-
** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => High ** Changed in: linux (Ubuntu Disco) Importance: Undecided => Critical ** Changed in: linux (Ubuntu Disco) Importance: Critical => High ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: linux (Ubuntu Disco) Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1843533 Title: powerpc/tm: Fix restoring FP/VMX facility incorrectly on interrupts (CVE-2019-15031) / powerpc/tm: Fix FP/VMX unavailable exceptions inside a transaction (CVE-2019-15030) Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Confirmed Status in linux source package in Disco: Fix Released Bug description: SRU Justification: == [Impact] * Fix FP/VMX vulerabilities - CVE-2019-15030 and CVE-2019-15031 [Fix] * a8318c13e79badb92bc6640704a64cc022a6eb97 a8318c1 "powerpc/tm: Fix restoring FP/VMX facility incorrectly on interrupts" * 8205d5d98ef7f155de211f5e2eb6ca03d95a5a60 8205d5d "powerpc/tm: Fix FP/VMX unavailable exceptions inside a transaction" [Test Case] * the commits point to a simple test case in tools/testing/selftests/powerpc/tm/tm-poison.c [Regression Potential] * The regression potential can be considered as moderate [Other Info] * a8318c1 fixes CVE-2019-15031 * 8205d5d fixes CVE-2019-15030 * the commits are in 5.3, hence already in Eoan * simple cherry-pick (on bionic master-next with '--strategy=recursive -X theirs -s -e -x') could be done __ == Comment: #0 - Michael Ranweiler - 2019-09-11 00:49:28 == There are two problems/CVEs for power that we'd appreciate adding: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a8318c13e79badb92bc6640704a64cc022a6eb97 powerpc/tm: Fix restoring FP/VMX facility incorrectly on interrupts When in userspace and MSR FP=0 the hardware FP state is unrelated to the current process. This is extended for transactions where if tbegin is run with FP=0, the hardware checkpoint FP state will also be unrelated to the current process. Due to this, we need to ensure this hardware checkpoint is updated with the correct state before we enable FP for this process. Unfortunately we get this wrong when returning to a process from a hardware interrupt. A process that starts a transaction with FP=0 can take an interrupt. When the kernel returns back to that process, we change to FP=1 but with hardware checkpoint FP state not updated. If this transaction is then rolled back, the FP registers now contain the wrong state. The process looks like this: Userspace: Kernel Start userspace with MSR FP=0 TM=1 < - ... tbegin bne Hardware interrupt > ret_from_except restore_math() /* sees FP=0 */ restore_fp() tm_active_with_fp() /* sees FP=1 (Incorrect) */ load_fp_state() FP = 0 -> 1 < - Return to userspace with MSR TM=1 FP=1 with junk in the FP TM checkpoint TM rollback reads FP junk When returning from the hardware exception, tm_active_with_fp() is incorrectly making restore_fp() call load_fp_state() which is setting FP=1. The fix is to remove tm_active_with_fp(). tm_active_with_fp() is attempting to handle the case where FP state has been changed inside a transaction. In this case the checkpointed and transactional FP state is different and hence we must restore the FP state (ie. we can't do lazy FP restore inside a transaction that's used FP). It's safe to remove tm_active_with_fp() as this case is handled by restore_tm_state(). restore_tm_state() detects if FP has been using inside a transaction and will set load_fp and call restore_math() to ensure the FP state (checkpoint and transaction) is restored. This is a data integrity problem for the current process as the FP registers are corrupted. It's also a security problem as the FP registers from one process
[Kernel-packages] [Bug 1843533] Re: powerpc/tm: Fix restoring FP/VMX facility incorrectly on interrupts (CVE-2019-15031) / powerpc/tm: Fix FP/VMX unavailable exceptions inside a transaction (CVE-2019-
** Changed in: linux (Ubuntu)
Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) =>
Canonical Kernel Team (canonical-kernel-team)
** Changed in: linux (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1843533
Title:
powerpc/tm: Fix restoring FP/VMX facility incorrectly on interrupts
(CVE-2019-15031) / powerpc/tm: Fix FP/VMX unavailable exceptions
inside a transaction (CVE-2019-15030)
Status in The Ubuntu-power-systems project:
In Progress
Status in linux package in Ubuntu:
In Progress
Bug description:
SRU Justification:
==
[Impact]
* Fix FP/VMX vulerabilities - CVE-2019-15030 and CVE-2019-15031
[Fix]
* a8318c13e79badb92bc6640704a64cc022a6eb97 a8318c1 "powerpc/tm: Fix
restoring FP/VMX facility incorrectly on interrupts"
* 8205d5d98ef7f155de211f5e2eb6ca03d95a5a60 8205d5d "powerpc/tm: Fix
FP/VMX unavailable exceptions inside a transaction"
[Test Case]
* the commits point to a simple test case in
tools/testing/selftests/powerpc/tm/tm-poison.c
[Regression Potential]
* The regression potential can be considered as moderate
[Other Info]
* a8318c1 fixes CVE-2019-15031
* 8205d5d fixes CVE-2019-15030
* the commits are in 5.3, hence already in Eoan
* simple cherry-pick (on bionic master-next with '--strategy=recursive -X
theirs -s -e -x') could be done
__
== Comment: #0 - Michael Ranweiler - 2019-09-11
00:49:28 ==
There are two problems/CVEs for power that we'd appreciate adding:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a8318c13e79badb92bc6640704a64cc022a6eb97
powerpc/tm: Fix restoring FP/VMX facility incorrectly on interrupts
When in userspace and MSR FP=0 the hardware FP state is unrelated to
the current process. This is extended for transactions where if tbegin
is run with FP=0, the hardware checkpoint FP state will also be
unrelated to the current process. Due to this, we need to ensure this
hardware checkpoint is updated with the correct state before we enable
FP for this process.
Unfortunately we get this wrong when returning to a process from a
hardware interrupt. A process that starts a transaction with FP=0 can
take an interrupt. When the kernel returns back to that process, we
change to FP=1 but with hardware checkpoint FP state not updated. If
this transaction is then rolled back, the FP registers now contain the
wrong state.
The process looks like this:
Userspace: Kernel
Start userspace
with MSR FP=0 TM=1
< -
...
tbegin
bne
Hardware interrupt
>
ret_from_except
restore_math()
/* sees FP=0 */
restore_fp()
tm_active_with_fp()
/* sees FP=1 (Incorrect) */
load_fp_state()
FP = 0 -> 1
< -
Return to userspace
with MSR TM=1 FP=1
with junk in the FP TM checkpoint
TM rollback
reads FP junk
When returning from the hardware exception, tm_active_with_fp() is
incorrectly making restore_fp() call load_fp_state() which is setting
FP=1.
The fix is to remove tm_active_with_fp().
tm_active_with_fp() is attempting to handle the case where FP state
has been changed inside a transaction. In this case the checkpointed
and transactional FP state is different and hence we must restore the
FP state (ie. we can't do lazy FP restore inside a transaction that's
used FP). It's safe to remove tm_active_with_fp() as this case is
handled by restore_tm_state(). restore_tm_state() detects if FP has
been using inside a transaction and will set load_fp and call
restore_math() to ensure the FP state (checkpoint and transaction) is
restored.
This is a data integrity problem for the current process as the FP
registers are corrupted. It's also a security problem as the FP
registers from one process may be leaked to another.
Similarly for VMX.
A simple testcase to replicate this will be posted to
tools/testing/selftests/powerpc/tm/tm-poison.c
This fixes CVE-2019-15031.
Fixes: a7771176b439 ("powerpc: Don't enable FP/Altivec if not checkpointed")
Cc: sta...@vger.kernel.org # 4.15+
Signed-off-by: Gustavo Romero
Signed-off-by: Michael Neuling
Signed-off-by: Michael Ellerman
Link:
https://lore.kernel.org/r/20190904045529.23002-2-grom...@linux.vnet.ibm.com
.
2.
[Kernel-packages] [Bug 1841984] Re: [Backport] Crypto VMX Fixes
** Changed in: linux (Ubuntu)
Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) =>
Canonical Kernel Team (canonical-kernel-team)
** Changed in: linux (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1841984
Title:
[Backport] Crypto VMX Fixes
Status in The Ubuntu-power-systems project:
Fix Committed
Status in linux package in Ubuntu:
Fix Committed
Bug description:
Ubuntu Disco is missing the fix for "5c380d623ed3 - crypto: vmx - Add
support for VMS instructions by ASM (4 years, 5 months ago) " ... which is fixed by 'crypto: vmx - fix copy-paste error
in CTR mode', it fixes a couple of incorrect branch targets, and usage
of an incorrect vector assembly instruction.
The others two patches ("crypto: vmx - CTR: always increment IV as
quadword ", "crypto: vmx - ghash: do nosimd fallback manually ") fixes
for ghash replaces the fallback mechanism that is used on powerpc an
operation is required to operate in interrupt context.
Not having these patches might lead to data integrity issues.
patches
crypto: vmx - fix copy-paste error in CTR mode
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=dcf7b48212c0fab7df69e84fab22d6cb7c8c0fb9
crypto: vmx - CTR: always increment IV as quadword
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=009b30ac7444c17fae34c4f435ebce8e8e2b3250
crypto: vmx - ghash: do nosimd fallback manually
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=357d065a44cdd77ed5ff35155a989f2a763e96ef
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1841984/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828597] Re: KDump boot fails with nr_cpus=1
** Changed in: linux (Ubuntu Disco) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Eoan) Status: Confirmed => Invalid ** Changed in: ubuntu-power-systems Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/1828597 Title: KDump boot fails with nr_cpus=1 Status in The Ubuntu-power-systems project: Fix Committed Status in kexec-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in makedumpfile package in Ubuntu: Fix Released Status in makedumpfile source package in Bionic: Fix Committed Status in kexec-tools source package in Cosmic: Invalid Status in kexec-tools source package in Disco: Invalid Status in linux source package in Disco: Invalid Status in makedumpfile source package in Disco: Fix Committed Status in kexec-tools source package in Eoan: Invalid Status in linux source package in Eoan: Invalid Status in makedumpfile source package in Eoan: Fix Released Bug description: [Impact] The kdump kernel will crash during its boot if booted on a CPU other than 0. [Test case] Trigger a crash using taskset -c X, where X is not 0 and is a present CPU. Check that the dump is successful. echo c | sudo taskset -c 1 tee /proc/sysrq-trigger [Regression potential] This will cause more memory to be used by the dump kernel, which may cause OOMs during the dump. The fix is restricted to ppc64el. == Comment: #0 - Hari Krishna Bathini - 2019-05-10 06:38:21 == ---Problem Description--- kdump boots fails in some environments when nr_cpus=1 is passed ---uname output--- na Machine Type = na ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. configure kdump 2. trigger crash on non-boot cpu Expected result: Capture dump and reboot Actual result: Hang in early kdump boot process after crash Userspace tool common name: kdump-tools The userspace tool has the following bit modes: 64-bit Userspace rpm: kdump-tools Userspace tool obtained from project website: na == Comment: #1 - Hari Krishna Bathini - 2019-05-10 06:45:46 == Launchpad bug 1560552 added "nr_cpus=1" support on ppc64 though this change never made it upstream as maintainer has a few apprehensions.. With 4.18 kernels, this change is dropped on Ubuntu kernels too. With nr_cpus=1 support in kernel, kdump-tools was also updated to use "nr_cpsu=1" by default instead of "maxcpus=1" (see launchpad bug 1568952). This kdump-tools change has to be reverted to make it consist with the kernel change. Note that "nr_cpus=1 change had a issues in kdump guest environment even with "nr_cpus=1" support for kdump in kernel. So, even not withstanding the kernel revert, it is better to default to "maxcpus=1" on all kernel versions. So, please revert the kdump-tools fix that went in with launchpad bug 1568952 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1828597/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842465] Re: Watchdog error about hard lockup
** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) => Canonical Kernel Team (canonical-kernel-team) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1842465 Title: Watchdog error about hard lockup Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: Fix Committed Bug description: ---Problem Description--- Got a message from Watchdog about self-detected hard LOCKUP ---uname output--- Linux power 5.0.0-23-generic #24~18.04.1-Ubuntu SMP Mon Jul 29 16:08:34 UTC 2019 ppc64le ppc64le ppc64le GNU/Linux ---Additional Hardware Info--- Architecture:ppc64le Byte Order: Little Endian CPU(s): 128 On-line CPU(s) list: 0-127 Thread(s) per core: 4 Core(s) per socket: 16 Socket(s): 2 NUMA node(s):6 Model: 2.2 (pvr 004e 1202) Model name: POWER9, altivec supported CPU max MHz: 3800. CPU min MHz: 2300. L1d cache: 32K L1i cache: 32K L2 cache:512K L3 cache:10240K NUMA node0 CPU(s): 0-63 NUMA node8 CPU(s): 64-127 NUMA node252 CPU(s): NUMA node253 CPU(s): NUMA node254 CPU(s): NUMA node255 CPU(s): --- free totalusedfree shared buff/cache available Mem: 1071807104 5110016 985192768 622944081504320 1056273664 Swap: 2097088 0 2097088 -- lsblk NAMEMAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:01 894.3G 0 disk ??sda18:11 7M 0 part ??sda28:21 894.3G 0 part / sdb 8:16 1 894.3G 0 disk nvme0n1 259:10 2.9T 0 disk /nvmdisk1 --- Machine Type = AC922, bare metal ---Steps to Reproduce--- This problem I encountered when running customer workload and I switched SMT levels from SMT2 to SMT1 and I got a lockup error right away!! this seems to be a different one... postgresql DB daemon was running on the system. Stack trace output: [756383.688067] watchdog: CPU 53 self-detected hard LOCKUP @ _raw_spin_lock+0x54/0xe0 [756383.688068] watchdog: CPU 53 TB:387344180861438, last heartbeat TB:387337108856720 (13812ms ago) [756383.688069] Modules linked in: binfmt_misc veth ipt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_nat_ipv4 xt_addrtype iptable_filter bpfilter xt_conntrack nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 br_netfilter bridge stp llc aufs overlay vmx_crypto ofpart cmdlinepart powernv_flash ipmi_powernv opal_prd mtd ipmi_devintf at24 ibmpowernv ipmi_msghandler uio_pdrv_genirq uio sch_fq_codel ib_iser rdma_cm iw_cm ib_cm iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mlx5_ib ib_uverbs ib_core ast crct10dif_vpmsum i2c_algo_bit crc32c_vpmsum ttm mlx5_core drm_kms_helper syscopyarea nvme sysfillrect sysimgblt fb_sys_fops drm nvme_core ahci libahci tls mlxfw devlink tg3 drm_panel_orientation_quirks [756383.688088] CPU: 53 PID: 119744 Comm: postgres Not tainted 5.0.0-23-generic #24~18.04.1-Ubuntu [756383.688088] NIP: c0e0fcc4 LR: c015fd90 CTR: c0600460 [756383.688089] REGS: c07fffb3bd70 TRAP: 0900 Not tainted (5.0.0-23-generic) [756383.688089] MSR: 90009033 CR: 28242824 XER: [756383.688091] CFAR: c0e0fcec IRQMASK: 1 [756383.688092] GPR00: c015fd90 c000206f2cdf7970 c185c700 c00020732ea49100 [756383.688093] GPR04: c000206f2cdf7a38 c000206f2cdf7b00 0001 [756383.688095] GPR08: 0003 807d 8035 fffd [756383.688096] GPR12: 2000 c07c5080 7cde07504dd8 0f495eee0d68 [756383.688097] GPR16: 7fffc0eb2bd7 7fffc0eb2aa0 0f496c289088 7fffc0eb2a74 [756383.688098] GPR20: 0001 0001 [756383.688099] GPR24: c000206f2cdf7a38 c1349100 20732d70 [756383.688100] GPR28: c1891c70 c000206f36d8b400 c1895c78 c00020732ea49100 [756383.688102] NIP [c0e0fcc4] _raw_spin_lock+0x54/0xe0 [756383.688102] LR [c015fd90] __task_rq_lock+0x80/0x150 [756383.688102] Call Trace: [756383.688103] [c000206f2cdf7970] [c000206f2cdf79d0] 0xc000206f2cdf79d0 (unreliable) [756383.688103] [c000206f2cdf79a0] [c07fd3847818] 0xc07fd3847818 [756383.688104] [c000206f2cdf7a10] [c01649c0] try_to_wake_up+0x380/0x710 [756383.688105]
[Kernel-packages] [Bug 1788098] Re: Avoid migration issues with aligned 2MB THB
This bug has expired, marking it as invalid, please reopen if this is still a valid issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1788098 Title: Avoid migration issues with aligned 2MB THB Status in The Ubuntu-power-systems project: Invalid Status in linux package in Ubuntu: Expired Status in qemu package in Ubuntu: Invalid Status in linux source package in Bionic: Expired Status in linux source package in Cosmic: Invalid Bug description: FYI: This blocks bug 1781526 - once this one here is resolved we can go on with SRU considerations for 1781526 --- Comment From jhop...@us.ibm.com 2018-08-20 17:12 EDT--- Hi, in some environments it was observed that this qemu patch to enable THP made it more likely to hit guest migration issues, however the following kernel patch resolves those migration issues: https://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git/commit/?h=kvm-ppc-next=c066fafc595eef5ae3c83ae3a8305956b8c3ef15 KVM: PPC: Book3S HV: Use correct pagesize in kvm_unmap_radix() Once merged upstream, it would be good to include that change as well to avoid potential migration problems. Should I open a new bug for that or is it better to track here? Note Paelzer: I have not seen related migration issues myself, but it seems reasonable and confirmed by IBM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1788098/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828597] Re: KDump boot fails with nr_cpus=1
** No longer affects: makedumpfile (Ubuntu Cosmic) ** No longer affects: linux (Ubuntu Cosmic) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/1828597 Title: KDump boot fails with nr_cpus=1 Status in The Ubuntu-power-systems project: Confirmed Status in kexec-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Status in makedumpfile package in Ubuntu: Fix Released Status in kexec-tools source package in Cosmic: Invalid Status in kexec-tools source package in Disco: Invalid Status in linux source package in Disco: Confirmed Status in makedumpfile source package in Disco: New Status in kexec-tools source package in Eoan: Invalid Status in linux source package in Eoan: Confirmed Status in makedumpfile source package in Eoan: Fix Released Bug description: [Impact] The kdump kernel will crash during its boot if booted on a CPU other than 0. [Test case] Trigger a crash using taskset -c X, where X is not 0 and is a present CPU. Check that the dump is successful. echo c | sudo taskset -c 1 tee /proc/sysrq-trigger [Regression potential] This will cause more memory to be used by the dump kernel, which may cause OOMs during the dump. The fix is restricted to ppc64el. == Comment: #0 - Hari Krishna Bathini - 2019-05-10 06:38:21 == ---Problem Description--- kdump boots fails in some environments when nr_cpus=1 is passed ---uname output--- na Machine Type = na ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. configure kdump 2. trigger crash on non-boot cpu Expected result: Capture dump and reboot Actual result: Hang in early kdump boot process after crash Userspace tool common name: kdump-tools The userspace tool has the following bit modes: 64-bit Userspace rpm: kdump-tools Userspace tool obtained from project website: na == Comment: #1 - Hari Krishna Bathini - 2019-05-10 06:45:46 == Launchpad bug 1560552 added "nr_cpus=1" support on ppc64 though this change never made it upstream as maintainer has a few apprehensions.. With 4.18 kernels, this change is dropped on Ubuntu kernels too. With nr_cpus=1 support in kernel, kdump-tools was also updated to use "nr_cpsu=1" by default instead of "maxcpus=1" (see launchpad bug 1568952). This kdump-tools change has to be reverted to make it consist with the kernel change. Note that "nr_cpus=1 change had a issues in kdump guest environment even with "nr_cpus=1" support for kdump in kernel. So, even not withstanding the kernel revert, it is better to default to "maxcpus=1" on all kernel versions. So, please revert the kdump-tools fix that went in with launchpad bug 1568952 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1828597/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1833716] Re: System crashes on hot adding a core with drmgr command (4.15.0-48-generic)
** Changed in: linux (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1833716 Title: System crashes on hot adding a core with drmgr command (4.15.0-48-generic) Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: [Impact] On Bionic GA kernel (4.15.0), hot add of cpu with drmgr causes the kernel to crash. The patches identified to fix these issues disables changing the NUMA associations for CPUs and Memory at runtime by default. [Test] # drmgr -c cpu -r -q 1 # drmgr -c cpu -a -q 1 Test kernel available in ppa:ubuntu-power-triage/lp1833716 Please see comment #2 for before and after results with the patches applied. [Fix] 558f86493df0 powerpc/numa: document topology_updates_enabled, disable by default 2d4d9b308f8f powerpc/numa: improve control of topology updates [Regression Potential] The two patches relate to powerpc/numa and does not impact other architectures or platform code. Regression potential is low. [Other Information] == Comment: #0 - Hari Krishna Bathini - 2019-05-07 13:18:35 == ---Problem Description--- On 4.15.0-48-generic kernel, hot adding a cpu with drmgr is crashing the kernel with below traces: --- root@ubuntu:~# drmgr -c cpu -r -q 1 Validating CPU DLPAR capability...yes. CPU 9 root@ubuntu:~# root@ubuntu:~# root@ubuntu:~# root@ubuntu:~# root@ubuntu:~# root@ubuntu:~# drmgr -c cpu -a -q 1 Validating CPU DLPAR capability...yes. [ 218.555493] BUG: arch topology borken [ 218.03] the DIE domain not a subset of the NODE domain [ 218.12] BUG: arch topology borken [ 218.16] the DIE domain not a subset of the NODE domain [ 218.23] BUG: arch topology borken [ 218.28] the DIE domain not a subset of the NODE domain [ 218.35] BUG: arch topology borken [ 218.39] the DIE domain not a subset of the NODE domain [ 218.45] BUG: arch topology borken [ 218.50] the DIE domain not a subset of the NODE domain [ 218.56] BUG: arch topology borken [ 218.60] the DIE domain not a subset of the NODE domain [ 218.67] BUG: arch topology borken [ 218.71] the DIE domain not a subset of the NODE domain [ 218.77] BUG: arch topology borken [ 218.81] the DIE domain not a subset of the NODE domain [ 218.555672] Unable to handle kernel paging request for data at address 0x9332ae80f961139f [ 218.555679] Faulting instruction address: 0xc01768cc [ 218.555686] Oops: Kernel access of bad area, sig: 11 [#1] [ 218.555691] LE SMP NR_CPUS=2048 NUMA pSeries [ 218.555699] Modules linked in: vmx_crypto crct10dif_vpmsum sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear ibmvscsi ibmveth crc32c_vpmsum [ 218.555745] CPU: 8 PID: 276 Comm: kworker/8:1 Not tainted 4.15.0-48-generic #51-Ubuntu [ 218.555757] Workqueue: events cpuset_hotplug_workfn [ 218.555763] NIP: c01768cc LR: c01769a8 CTR: [ 218.555770] REGS: c001f5f1f530 TRAP: 0380 Not tainted (4.15.0-48-generic) [ 218.555776] MSR: 80009033 CR: 22824228 XER: 0004 [ 218.555789] CFAR: c0176920 SOFTE: 1 [ 218.555789] GPR00: c01769a8 c001f5f1f7b0 c16eb400 c001f7bfd200 [ 218.555789] GPR04: 0001 0008 0010 [ 218.555789] GPR08: 0018 c001f7bfd408 [ 218.555789] GPR12: 8000 c7a35800 0007 c001f549d900 [ 218.555789] GPR16: 0040 c1722494 c001f0f29400 0001 [ 218.555789] GPR20: c001ffb68580 0008 c11d8580 c171dd78 [ 218.555789] GPR24: e830 ec30 12af [ 218.555789] GPR28: 102f c001f7bfd200 9332ae80f961139f 9332ae80f961139f [ 218.555859] NIP [c01768cc] free_sched_groups.part.2+0x4c/0xf0 [ 218.555866] LR [c01769a8] destroy_sched_domain+0x38/0xc0 [ 218.555871] Call Trace: [ 218.555875] [c001f5f1f7b0] [ec30] 0xec30 (unreliable) [ 218.555884] [c001f5f1f7f0] [c01769a8] destroy_sched_domain+0x38/0xc0 [ 218.555892] [c001f5f1f820] [c0176eb0] cpu_attach_domain+0xf0/0x870 [ 218.555900] [c001f5f1f960] [c0178884] build_sched_domains+0x1254/0x12f0 [
[Kernel-packages] [Bug 1833716] Re: System crashes on hot adding a core with drmgr command (4.15.0-48-generic)
ubuntu@P8lpar4:~$ uname -a Linux P8lpar4 4.15.0-55-generic #60-Ubuntu SMP Tue Jul 2 18:21:40 UTC 2019 ppc64le ppc64le ppc64le GNU/Linux ubuntu@P8lpar4:~$ ubuntu@P8lpar4:~$ apt policy linux-image-generic linux-image-generic: Installed: 4.15.0.55.57 Candidate: 4.15.0.55.57 Version table: *** 4.15.0.55.57 500 500 http://ports.ubuntu.com/ubuntu-ports bionic-proposed/main ppc64el Packages 100 /var/lib/dpkg/status 4.15.0.54.56 500 500 http://ports.ubuntu.com/ubuntu-ports bionic-updates/main ppc64el Packages 500 http://ports.ubuntu.com/ubuntu-ports bionic-security/main ppc64el Packages 4.15.0.20.23 500 500 http://ports.ubuntu.com/ubuntu-ports bionic/main ppc64el Packages ubuntu@P8lpar4:~$ ubuntu@P8lpar4:~$ sudo su root@P8lpar4:/home/ubuntu# drmgr -c cpu -r -q 1 Validating CPU DLPAR capability...yes. CPU 121 root@P8lpar4:/home/ubuntu# drmgr -c cpu -a -q 1 Validating CPU DLPAR capability...yes. CPU 121 root@P8lpar4:/home/ubuntu# -- dmesg -- [ 476.574556] cpu 120 (hwid 120) Ready to die... [ 476.647003] cpu 121 (hwid 121) Ready to die... [ 476.710155] cpu 122 (hwid 122) Ready to die... [ 476.766678] cpu 123 (hwid 123) Ready to die... [ 476.829791] cpu 124 (hwid 124) Ready to die... [ 476.883594] cpu 125 (hwid 125) Ready to die... [ 476.933738] cpu 126 (hwid 126) Ready to die... [ 476.986045] cpu 127 (hwid 127) Ready to die... root@P8lpar4:/home/ubuntu# ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1833716 Title: System crashes on hot adding a core with drmgr command (4.15.0-48-generic) Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Committed Bug description: [Impact] On Bionic GA kernel (4.15.0), hot add of cpu with drmgr causes the kernel to crash. The patches identified to fix these issues disables changing the NUMA associations for CPUs and Memory at runtime by default. [Test] # drmgr -c cpu -r -q 1 # drmgr -c cpu -a -q 1 Test kernel available in ppa:ubuntu-power-triage/lp1833716 Please see comment #2 for before and after results with the patches applied. [Fix] 558f86493df0 powerpc/numa: document topology_updates_enabled, disable by default 2d4d9b308f8f powerpc/numa: improve control of topology updates [Regression Potential] The two patches relate to powerpc/numa and does not impact other architectures or platform code. Regression potential is low. [Other Information] == Comment: #0 - Hari Krishna Bathini - 2019-05-07 13:18:35 == ---Problem Description--- On 4.15.0-48-generic kernel, hot adding a cpu with drmgr is crashing the kernel with below traces: --- root@ubuntu:~# drmgr -c cpu -r -q 1 Validating CPU DLPAR capability...yes. CPU 9 root@ubuntu:~# root@ubuntu:~# root@ubuntu:~# root@ubuntu:~# root@ubuntu:~# root@ubuntu:~# drmgr -c cpu -a -q 1 Validating CPU DLPAR capability...yes. [ 218.555493] BUG: arch topology borken [ 218.03] the DIE domain not a subset of the NODE domain [ 218.12] BUG: arch topology borken [ 218.16] the DIE domain not a subset of the NODE domain [ 218.23] BUG: arch topology borken [ 218.28] the DIE domain not a subset of the NODE domain [ 218.35] BUG: arch topology borken [ 218.39] the DIE domain not a subset of the NODE domain [ 218.45] BUG: arch topology borken [ 218.50] the DIE domain not a subset of the NODE domain [ 218.56] BUG: arch topology borken [ 218.60] the DIE domain not a subset of the NODE domain [ 218.67] BUG: arch topology borken [ 218.71] the DIE domain not a subset of the NODE domain [ 218.77] BUG: arch topology borken [ 218.81] the DIE domain not a subset of the NODE domain [ 218.555672] Unable to handle kernel paging request for data at address 0x9332ae80f961139f [ 218.555679] Faulting instruction address: 0xc01768cc [ 218.555686] Oops: Kernel access of bad area, sig: 11 [#1] [ 218.555691] LE SMP NR_CPUS=2048 NUMA pSeries [ 218.555699] Modules linked in: vmx_crypto crct10dif_vpmsum sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear ibmvscsi ibmveth crc32c_vpmsum [ 218.555745] CPU: 8 PID: 276 Comm: kworker/8:1 Not tainted 4.15.0-48-generic #51-Ubuntu [ 218.555757] Workqueue: events cpuset_hotplug_workfn [ 218.555763] NIP: c01768cc LR: c01769a8 CTR: [ 218.555770] REGS: c001f5f1f530
[Kernel-packages] [Bug 1828596] Re: kdump fails when crash is triggered after DLPAR cpu add operation
** Changed in: ubuntu-power-systems Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1828596 Title: kdump fails when crash is triggered after DLPAR cpu add operation Status in The Ubuntu-power-systems project: Incomplete Status in kexec-tools package in Ubuntu: Invalid Status in makedumpfile package in Ubuntu: Fix Released Status in kexec-tools source package in Xenial: New Status in makedumpfile source package in Xenial: New Status in kexec-tools source package in Bionic: New Status in makedumpfile source package in Bionic: New Status in kexec-tools source package in Cosmic: New Status in makedumpfile source package in Cosmic: New Status in kexec-tools source package in Disco: New Status in makedumpfile source package in Disco: New Status in kexec-tools source package in Eoan: Invalid Status in makedumpfile source package in Eoan: Fix Released Bug description: [Impact] After a CPU add/hotplug operation on Power systems, kdump will fail after a crash. The kdump kernel needs to be reloaded after a CPU add/hotplug. [Test case] Do CPU add/hotplug, trigger a crash, and check for a successful kdump. [Regression potential] Multiple reloads caused by multiple sequential CPU adds may cause spurious log results, and systemd may fail to properly reload the kdump kernel. == Comment: #0 - Hari Krishna Bathini - 2019-05-10 05:55:40 == ---Problem Description--- kdump fails when crash is triggered after CPU add operation. Machine Type = na ---System Hang--- Crashed in early boot process of kdump kernel after crash Had to issue system reset from HMC to reclaim ---Steps to Reproduce--- 1. Configure kdump. 2. Add cpu from HMC. 3. Trigger crash. 4. Machine hangs after crash as below: --- [169250.213166] IPI complete [169250.234331] kexec: Starting switchover sequence. I'm in purgatory --- STRUCK HERE --- ---uname output--- na ---Debugger--- A debugger is not configured == Comment: #1 - Hari Krishna Bathini - 2019-05-10 05:56:46 == The problem is, kexec udev rule to restart kdump-tools service - when a core is added, is not being triggered. The old DT created by kexec (before the core is added) is being used by KDump Kernel. So, when system crashes on a thread from the added core(s), KDump kernel is failing to get the 'boot_cpuid' and eventually failing to boot.. == Comment: #2 - Hari Krishna Bathini - 2019-05-10 06:02:27 == The udev rule when CPU is added is not triggered because ppc64 does not eject add/remove event when a CPU is hot added/removed. It only ejects online/offline event to user space when CPU is hot added/removed. So, the below udev rules are never triggered when needed: SUBSYSTEM=="cpu", ACTION=="add", PROGRAM="/bin/systemctl try-restart kdump-tools.service" SUBSYSTEM=="cpu", ACTION=="remove", PROGRAM="/bin/systemctl try-restart kdump-tools.service" Also, with how CPU hot add & remove are handled in ppc64, a udev trigger to reload kdump after CPU is hot removed is NOT necessary. So, fix the CPU hot add case by updating the udev rule and drop the udev rule meant for CPU hot remove in the kdump udev rules file: SUBSYSTEM=="cpu", ACTION=="online", PROGRAM="/bin/systemctl try- restart kdump-tools.service" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1828596/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1833716] Re: System crashes on hot adding a core with drmgr command (4.15.0-48-generic)
** Changed in: ubuntu-power-systems Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Manoj Iyer (manjo) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1833716 Title: System crashes on hot adding a core with drmgr command (4.15.0-48-generic) Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Committed Bug description: [Impact] On Bionic GA kernel (4.15.0), hot add of cpu with drmgr causes the kernel to crash. The patches identified to fix these issues disables changing the NUMA associations for CPUs and Memory at runtime by default. [Test] # drmgr -c cpu -r -q 1 # drmgr -c cpu -a -q 1 Test kernel available in ppa:ubuntu-power-triage/lp1833716 Please see comment #2 for before and after results with the patches applied. [Fix] 558f86493df0 powerpc/numa: document topology_updates_enabled, disable by default 2d4d9b308f8f powerpc/numa: improve control of topology updates [Regression Potential] The two patches relate to powerpc/numa and does not impact other architectures or platform code. Regression potential is low. [Other Information] == Comment: #0 - Hari Krishna Bathini - 2019-05-07 13:18:35 == ---Problem Description--- On 4.15.0-48-generic kernel, hot adding a cpu with drmgr is crashing the kernel with below traces: --- root@ubuntu:~# drmgr -c cpu -r -q 1 Validating CPU DLPAR capability...yes. CPU 9 root@ubuntu:~# root@ubuntu:~# root@ubuntu:~# root@ubuntu:~# root@ubuntu:~# root@ubuntu:~# drmgr -c cpu -a -q 1 Validating CPU DLPAR capability...yes. [ 218.555493] BUG: arch topology borken [ 218.03] the DIE domain not a subset of the NODE domain [ 218.12] BUG: arch topology borken [ 218.16] the DIE domain not a subset of the NODE domain [ 218.23] BUG: arch topology borken [ 218.28] the DIE domain not a subset of the NODE domain [ 218.35] BUG: arch topology borken [ 218.39] the DIE domain not a subset of the NODE domain [ 218.45] BUG: arch topology borken [ 218.50] the DIE domain not a subset of the NODE domain [ 218.56] BUG: arch topology borken [ 218.60] the DIE domain not a subset of the NODE domain [ 218.67] BUG: arch topology borken [ 218.71] the DIE domain not a subset of the NODE domain [ 218.77] BUG: arch topology borken [ 218.81] the DIE domain not a subset of the NODE domain [ 218.555672] Unable to handle kernel paging request for data at address 0x9332ae80f961139f [ 218.555679] Faulting instruction address: 0xc01768cc [ 218.555686] Oops: Kernel access of bad area, sig: 11 [#1] [ 218.555691] LE SMP NR_CPUS=2048 NUMA pSeries [ 218.555699] Modules linked in: vmx_crypto crct10dif_vpmsum sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear ibmvscsi ibmveth crc32c_vpmsum [ 218.555745] CPU: 8 PID: 276 Comm: kworker/8:1 Not tainted 4.15.0-48-generic #51-Ubuntu [ 218.555757] Workqueue: events cpuset_hotplug_workfn [ 218.555763] NIP: c01768cc LR: c01769a8 CTR: [ 218.555770] REGS: c001f5f1f530 TRAP: 0380 Not tainted (4.15.0-48-generic) [ 218.555776] MSR: 80009033 CR: 22824228 XER: 0004 [ 218.555789] CFAR: c0176920 SOFTE: 1 [ 218.555789] GPR00: c01769a8 c001f5f1f7b0 c16eb400 c001f7bfd200 [ 218.555789] GPR04: 0001 0008 0010 [ 218.555789] GPR08: 0018 c001f7bfd408 [ 218.555789] GPR12: 8000 c7a35800 0007 c001f549d900 [ 218.555789] GPR16: 0040 c1722494 c001f0f29400 0001 [ 218.555789] GPR20: c001ffb68580 0008 c11d8580 c171dd78 [ 218.555789] GPR24: e830 ec30 12af [ 218.555789] GPR28: 102f c001f7bfd200 9332ae80f961139f 9332ae80f961139f [ 218.555859] NIP [c01768cc] free_sched_groups.part.2+0x4c/0xf0 [ 218.555866] LR [c01769a8] destroy_sched_domain+0x38/0xc0 [ 218.555871] Call Trace: [ 218.555875] [c001f5f1f7b0] [ec30] 0xec30 (unreliable) [ 218.555884] [c001f5f1f7f0] [c01769a8] destroy_sched_domain+0x38/0xc0 [ 218.555892] [c001f5f1f820] [c0176eb0] cpu_attach_domain+0xf0
[Kernel-packages] [Bug 1741860] Re: Use the kernel default for crashkernel offset
** Changed in: ubuntu-power-systems Status: Incomplete => Confirmed ** Changed in: makedumpfile (Ubuntu) Status: Incomplete => Confirmed ** Changed in: makedumpfile (Ubuntu) Importance: Medium => High ** Changed in: ubuntu-power-systems Importance: Medium => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1741860 Title: Use the kernel default for crashkernel offset Status in The Ubuntu-power-systems project: Confirmed Status in makedumpfile package in Ubuntu: Confirmed Bug description: == Comment: #0 - Hari Krishna Bathini - 2018-01-08 01:06:41 == ---Problem Description--- A default offset of 128MB is enforced for crashkernel by kdump-tools utility overriding the kernel default. While the kernel default offset for crashkernel is also 128MB, that may change and the right thing to do would be to let the kernel decide on the offset of crashkernel in the default scenario.. Get rid of "@128M" in kdump-tools.cfg file Contact Information = hbath...@in.ibm.com ---uname output--- na Machine Type = na ---Debugger--- A debugger is not configured ---Steps to Reproduce--- # cat /etc/default/grub.d/kdump-tools.cfg GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M@128M" --- The offset is specified via kdump-tools where as the kernel may be the right place to set an offset by default.. Userspace tool common name: kdump-tools The userspace tool has the following bit modes: 64-bit Userspace rpm: kdump-tools Userspace tool obtained from project website: na *Additional Instructions for hbath...@in.ibm.com: -Attach ltrace and strace of userspace application. == Comment: #3 - MAMATHA INAMDAR - 2018-01-08 03:05:05 == This bug is opened to follow-up other bug based on the comment 19 https://bugzilla.linux.ibm.com/show_bug.cgi?id=152905#c19 (Canonical Launchpad1676884 ) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1741860/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802233] Re: hwclock test failed on Power9 due to 0.x sec differences / time out waiting for time change
** Changed in: ubuntu-power-systems
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1802233
Title:
hwclock test failed on Power9 due to 0.x sec differences / time out
waiting for time change
Status in ubuntu-kernel-tests:
New
Status in The Ubuntu-power-systems project:
Fix Released
Status in linux package in Ubuntu:
Invalid
Bug description:
The hwclock test will fail on the Power9 system "baltar" due to a
<0.02 second difference.
Traceback (most recent call last):
File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec
_call_test_function(self.execute, *p_args, **p_dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 823, in
_call_test_function
return func(*args, **dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute
postprocess_profiled_run, args, dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 212, in
_call_run_once
self.run_once(*args, **dargs)
File "/home/ubuntu/autotest/client/tests/hwclock/hwclock.py", line 50, in
run_once
raise error.TestFail("Failed to set hwclock back to Warthog's birthday.
Output of hwclock is '%s'" % date)
TestFail: Failed to set hwclock back to Warthog's birthday. Output of hwclock
is '2004-10-20 04:09:59.582146+'
Didn't see this on Power8 boxes
Sometimes it will fail because "time out waiting for time change" on the same
node:
$ sudo /sbin/hwclock --set --date "2004/10/20 04:10:00"; sudo /sbin/hwclock
hwclock: Timed out waiting for time change.
Workaround for these is to add "sleep 1".
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-38-generic 4.15.0-38.41
ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
Uname: Linux 4.15.0-38-generic ppc64le
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Nov 8 03:45 seq
crw-rw 1 root audio 116, 33 Nov 8 03:45 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: ppc64el
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord':
'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CurrentDmesg:
Date: Thu Nov 8 06:03:54 2018
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0451:80ff Texas Instruments, Inc.
Bus 001 Device 004: ID 0557:2419 ATEN International Co., Ltd
Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
PciMultimedia:
ProcFB: 0 astdrmfb
ProcKernelCmdLine: root=UUID=acd1a0d7-f6fc-4130-928c-c8b11ad6e4be ro
console=hvc0
ProcLoadAvg: 0.31 0.11 0.03 1/1392 5654
ProcLocks:
1: POSIX ADVISORY WRITE 3544 00:17:582 0 EOF
2: POSIX ADVISORY WRITE 1798 00:17:338 0 EOF
3: POSIX ADVISORY WRITE 3603 00:17:576 0 EOF
4: FLOCK ADVISORY WRITE 3535 00:17:564 0 EOF
5: FLOCK ADVISORY WRITE 4081 00:17:481 0 EOF
ProcSwaps:
Filename TypeSizeUsedPriority
/swap.img file 8388544 0 -2
ProcVersion: Linux version 4.15.0-38-generic (buildd@bos02-ppc64el-018) (gcc
version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #41-Ubuntu SMP Wed Oct 10 10:57:45 UTC
2018
RelatedPackageVersions:
linux-restricted-modules-4.15.0-38-generic N/A
linux-backports-modules-4.15.0-38-generic N/A
linux-firmware 1.173.1
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
VarLogDump_list: total 0
cpu_cores: Number of cores present = 40
cpu_coreson: Number of cores online = 40
cpu_dscr: DSCR is 16
cpu_freq:
min: 2.862 GHz (cpu 159)
max: 2.862 GHz (cpu 1)
avg: 2.862 GHz
cpu_runmode:
Could not retrieve current diagnostics mode,
No kernel interface to firmware
cpu_smt: SMT=4
-- Firmware information on Baltar --
pnor: P9DSU20190404_IBM_prod_sign.pnor
bmc: SMT_P9_206.bin
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1802233/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802233] Re: hwclock test failed on Power9 due to 0.x sec differences / time out waiting for time change
@cypressyew that sounds reasonable, the only word of caution here is we
should not dismiss future bugs detected on this system as "expected to
fail", because the problem is in the 3rd party BMC firmware *and not* in
the Pnor FW or Power9 hardware.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1802233
Title:
hwclock test failed on Power9 due to 0.x sec differences / time out
waiting for time change
Status in ubuntu-kernel-tests:
New
Status in The Ubuntu-power-systems project:
Fix Committed
Status in linux package in Ubuntu:
Invalid
Bug description:
The hwclock test will fail on the Power9 system "baltar" due to a
<0.02 second difference.
Traceback (most recent call last):
File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec
_call_test_function(self.execute, *p_args, **p_dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 823, in
_call_test_function
return func(*args, **dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute
postprocess_profiled_run, args, dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 212, in
_call_run_once
self.run_once(*args, **dargs)
File "/home/ubuntu/autotest/client/tests/hwclock/hwclock.py", line 50, in
run_once
raise error.TestFail("Failed to set hwclock back to Warthog's birthday.
Output of hwclock is '%s'" % date)
TestFail: Failed to set hwclock back to Warthog's birthday. Output of hwclock
is '2004-10-20 04:09:59.582146+'
Didn't see this on Power8 boxes
Sometimes it will fail because "time out waiting for time change" on the same
node:
$ sudo /sbin/hwclock --set --date "2004/10/20 04:10:00"; sudo /sbin/hwclock
hwclock: Timed out waiting for time change.
Workaround for these is to add "sleep 1".
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-38-generic 4.15.0-38.41
ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
Uname: Linux 4.15.0-38-generic ppc64le
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Nov 8 03:45 seq
crw-rw 1 root audio 116, 33 Nov 8 03:45 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: ppc64el
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord':
'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CurrentDmesg:
Date: Thu Nov 8 06:03:54 2018
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0451:80ff Texas Instruments, Inc.
Bus 001 Device 004: ID 0557:2419 ATEN International Co., Ltd
Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
PciMultimedia:
ProcFB: 0 astdrmfb
ProcKernelCmdLine: root=UUID=acd1a0d7-f6fc-4130-928c-c8b11ad6e4be ro
console=hvc0
ProcLoadAvg: 0.31 0.11 0.03 1/1392 5654
ProcLocks:
1: POSIX ADVISORY WRITE 3544 00:17:582 0 EOF
2: POSIX ADVISORY WRITE 1798 00:17:338 0 EOF
3: POSIX ADVISORY WRITE 3603 00:17:576 0 EOF
4: FLOCK ADVISORY WRITE 3535 00:17:564 0 EOF
5: FLOCK ADVISORY WRITE 4081 00:17:481 0 EOF
ProcSwaps:
Filename TypeSizeUsedPriority
/swap.img file 8388544 0 -2
ProcVersion: Linux version 4.15.0-38-generic (buildd@bos02-ppc64el-018) (gcc
version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #41-Ubuntu SMP Wed Oct 10 10:57:45 UTC
2018
RelatedPackageVersions:
linux-restricted-modules-4.15.0-38-generic N/A
linux-backports-modules-4.15.0-38-generic N/A
linux-firmware 1.173.1
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
VarLogDump_list: total 0
cpu_cores: Number of cores present = 40
cpu_coreson: Number of cores online = 40
cpu_dscr: DSCR is 16
cpu_freq:
min: 2.862 GHz (cpu 159)
max: 2.862 GHz (cpu 1)
avg: 2.862 GHz
cpu_runmode:
Could not retrieve current diagnostics mode,
No kernel interface to firmware
cpu_smt: SMT=4
-- Firmware information on Baltar --
pnor: P9DSU20190404_IBM_prod_sign.pnor
bmc: SMT_P9_206.bin
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1802233/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1833716] Re: System crashes on hot adding a core with drmgr command (4.15.0-48-generic)
The issue does not reproduce on Disco. root@P8lpar4:/home/ubuntu# uname -a Linux P8lpar4 5.0.0-19-generic #20-Ubuntu SMP Wed Jun 19 21:50:53 UTC 2019 ppc64le ppc64le ppc64le GNU/Linux root@P8lpar4:/home/ubuntu# root@P8lpar4:/home/ubuntu# drmgr -c cpu -r -q 1 Validating CPU DLPAR capability...yes. CPU 121 root@P8lpar4:/home/ubuntu# drmgr -c cpu -a -q 1 Validating CPU DLPAR capability...yes. CPU 121 root@P8lpar4:/home/ubuntu# -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1833716 Title: System crashes on hot adding a core with drmgr command (4.15.0-48-generic) Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Bug description: [Impact] On Bionic GA kernel (4.15.0), hot add of cpu with drmgr causes the kernel to crash. The patches identified to fix these issues disables changing the NUMA associations for CPUs and Memory at runtime by default. [Test] # drmgr -c cpu -r -q 1 # drmgr -c cpu -a -q 1 Test kernel available in ppa:ubuntu-power-triage/lp1833716 Please see comment #2 for before and after results with the patches applied. [Fix] 558f86493df0 powerpc/numa: document topology_updates_enabled, disable by default 2d4d9b308f8f powerpc/numa: improve control of topology updates [Regression Potential] The two patches relate to powerpc/numa and does not impact other architectures or platform code. Regression potential is low. [Other Information] == Comment: #0 - Hari Krishna Bathini - 2019-05-07 13:18:35 == ---Problem Description--- On 4.15.0-48-generic kernel, hot adding a cpu with drmgr is crashing the kernel with below traces: --- root@ubuntu:~# drmgr -c cpu -r -q 1 Validating CPU DLPAR capability...yes. CPU 9 root@ubuntu:~# root@ubuntu:~# root@ubuntu:~# root@ubuntu:~# root@ubuntu:~# root@ubuntu:~# drmgr -c cpu -a -q 1 Validating CPU DLPAR capability...yes. [ 218.555493] BUG: arch topology borken [ 218.03] the DIE domain not a subset of the NODE domain [ 218.12] BUG: arch topology borken [ 218.16] the DIE domain not a subset of the NODE domain [ 218.23] BUG: arch topology borken [ 218.28] the DIE domain not a subset of the NODE domain [ 218.35] BUG: arch topology borken [ 218.39] the DIE domain not a subset of the NODE domain [ 218.45] BUG: arch topology borken [ 218.50] the DIE domain not a subset of the NODE domain [ 218.56] BUG: arch topology borken [ 218.60] the DIE domain not a subset of the NODE domain [ 218.67] BUG: arch topology borken [ 218.71] the DIE domain not a subset of the NODE domain [ 218.77] BUG: arch topology borken [ 218.81] the DIE domain not a subset of the NODE domain [ 218.555672] Unable to handle kernel paging request for data at address 0x9332ae80f961139f [ 218.555679] Faulting instruction address: 0xc01768cc [ 218.555686] Oops: Kernel access of bad area, sig: 11 [#1] [ 218.555691] LE SMP NR_CPUS=2048 NUMA pSeries [ 218.555699] Modules linked in: vmx_crypto crct10dif_vpmsum sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear ibmvscsi ibmveth crc32c_vpmsum [ 218.555745] CPU: 8 PID: 276 Comm: kworker/8:1 Not tainted 4.15.0-48-generic #51-Ubuntu [ 218.555757] Workqueue: events cpuset_hotplug_workfn [ 218.555763] NIP: c01768cc LR: c01769a8 CTR: [ 218.555770] REGS: c001f5f1f530 TRAP: 0380 Not tainted (4.15.0-48-generic) [ 218.555776] MSR: 80009033 CR: 22824228 XER: 0004 [ 218.555789] CFAR: c0176920 SOFTE: 1 [ 218.555789] GPR00: c01769a8 c001f5f1f7b0 c16eb400 c001f7bfd200 [ 218.555789] GPR04: 0001 0008 0010 [ 218.555789] GPR08: 0018 c001f7bfd408 [ 218.555789] GPR12: 8000 c7a35800 0007 c001f549d900 [ 218.555789] GPR16: 0040 c1722494 c001f0f29400 0001 [ 218.555789] GPR20: c001ffb68580 0008 c11d8580 c171dd78 [ 218.555789] GPR24: e830 ec30 12af [ 218.555789] GPR28: 102f c001f7bfd200 9332ae80f961139f 9332ae80f961139f [ 218.555859] NIP [c01768cc] free_sched_groups.part.2+0x4c/0xf0 [ 218.555866] LR [c01769a8] destroy_sched_domain+0x38/0xc0 [ 218.555871] Call Trace: [ 218.555875] [c001f5f1f7b0] [ec30]
[Kernel-packages] [Bug 1833716] Re: System crashes on hot adding a core with drmgr command (4.15.0-48-generic)
** Changed in: ubuntu-power-systems Importance: High => Critical ** Changed in: linux (Ubuntu) Importance: High => Critical -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1833716 Title: System crashes on hot adding a core with drmgr command (4.15.0-48-generic) Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Bug description: [Impact] On Bionic GA kernel (4.15.0), hot add of cpu with drmgr causes the kernel to crash. The patches identified to fix these issues disables changing the NUMA associations for CPUs and Memory at runtime by default. [Test] # drmgr -c cpu -r -q 1 # drmgr -c cpu -a -q 1 Test kernel available in ppa:ubuntu-power-triage/lp1833716 Please see comment #2 for before and after results with the patches applied. [Fix] 558f86493df0 powerpc/numa: document topology_updates_enabled, disable by default 2d4d9b308f8f powerpc/numa: improve control of topology updates [Regression Potential] The two patches relate to powerpc/numa and does not impact other architectures or platform code. Regression potential is low. [Other Information] == Comment: #0 - Hari Krishna Bathini - 2019-05-07 13:18:35 == ---Problem Description--- On 4.15.0-48-generic kernel, hot adding a cpu with drmgr is crashing the kernel with below traces: --- root@ubuntu:~# drmgr -c cpu -r -q 1 Validating CPU DLPAR capability...yes. CPU 9 root@ubuntu:~# root@ubuntu:~# root@ubuntu:~# root@ubuntu:~# root@ubuntu:~# root@ubuntu:~# drmgr -c cpu -a -q 1 Validating CPU DLPAR capability...yes. [ 218.555493] BUG: arch topology borken [ 218.03] the DIE domain not a subset of the NODE domain [ 218.12] BUG: arch topology borken [ 218.16] the DIE domain not a subset of the NODE domain [ 218.23] BUG: arch topology borken [ 218.28] the DIE domain not a subset of the NODE domain [ 218.35] BUG: arch topology borken [ 218.39] the DIE domain not a subset of the NODE domain [ 218.45] BUG: arch topology borken [ 218.50] the DIE domain not a subset of the NODE domain [ 218.56] BUG: arch topology borken [ 218.60] the DIE domain not a subset of the NODE domain [ 218.67] BUG: arch topology borken [ 218.71] the DIE domain not a subset of the NODE domain [ 218.77] BUG: arch topology borken [ 218.81] the DIE domain not a subset of the NODE domain [ 218.555672] Unable to handle kernel paging request for data at address 0x9332ae80f961139f [ 218.555679] Faulting instruction address: 0xc01768cc [ 218.555686] Oops: Kernel access of bad area, sig: 11 [#1] [ 218.555691] LE SMP NR_CPUS=2048 NUMA pSeries [ 218.555699] Modules linked in: vmx_crypto crct10dif_vpmsum sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear ibmvscsi ibmveth crc32c_vpmsum [ 218.555745] CPU: 8 PID: 276 Comm: kworker/8:1 Not tainted 4.15.0-48-generic #51-Ubuntu [ 218.555757] Workqueue: events cpuset_hotplug_workfn [ 218.555763] NIP: c01768cc LR: c01769a8 CTR: [ 218.555770] REGS: c001f5f1f530 TRAP: 0380 Not tainted (4.15.0-48-generic) [ 218.555776] MSR: 80009033 CR: 22824228 XER: 0004 [ 218.555789] CFAR: c0176920 SOFTE: 1 [ 218.555789] GPR00: c01769a8 c001f5f1f7b0 c16eb400 c001f7bfd200 [ 218.555789] GPR04: 0001 0008 0010 [ 218.555789] GPR08: 0018 c001f7bfd408 [ 218.555789] GPR12: 8000 c7a35800 0007 c001f549d900 [ 218.555789] GPR16: 0040 c1722494 c001f0f29400 0001 [ 218.555789] GPR20: c001ffb68580 0008 c11d8580 c171dd78 [ 218.555789] GPR24: e830 ec30 12af [ 218.555789] GPR28: 102f c001f7bfd200 9332ae80f961139f 9332ae80f961139f [ 218.555859] NIP [c01768cc] free_sched_groups.part.2+0x4c/0xf0 [ 218.555866] LR [c01769a8] destroy_sched_domain+0x38/0xc0 [ 218.555871] Call Trace: [ 218.555875] [c001f5f1f7b0] [ec30] 0xec30 (unreliable) [ 218.555884] [c001f5f1f7f0] [c01769a8] destroy_sched_domain+0x38/0xc0 [ 218.555892] [c001f5f1f820] [c0176eb0] cpu_attach_domain+0xf0/0x870 [ 218.555900] [c001f5f1f960] [c0178884] build_sched_domains+0x1254/0x12f0 [ 218.555908]
[Kernel-packages] [Bug 1833716] Re: System crashes on hot adding a core with drmgr command (4.15.0-48-generic)
SRU submitted: https://lists.ubuntu.com/archives/kernel- team/2019-June/101539.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1833716 Title: System crashes on hot adding a core with drmgr command (4.15.0-48-generic) Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Bug description: [Impact] On Bionic GA kernel (4.15.0), hot add of cpu with drmgr causes the kernel to crash. The patches identified to fix these issues disables changing the NUMA associations for CPUs and Memory at runtime by default. [Test] # drmgr -c cpu -r -q 1 # drmgr -c cpu -a -q 1 Test kernel available in ppa:ubuntu-power-triage/lp1833716 Please see comment #2 for before and after results with the patches applied. [Fix] 558f86493df0 powerpc/numa: document topology_updates_enabled, disable by default 2d4d9b308f8f powerpc/numa: improve control of topology updates [Regression Potential] The two patches relate to powerpc/numa and does not impact other architectures or platform code. Regression potential is low. [Other Information] == Comment: #0 - Hari Krishna Bathini - 2019-05-07 13:18:35 == ---Problem Description--- On 4.15.0-48-generic kernel, hot adding a cpu with drmgr is crashing the kernel with below traces: --- root@ubuntu:~# drmgr -c cpu -r -q 1 Validating CPU DLPAR capability...yes. CPU 9 root@ubuntu:~# root@ubuntu:~# root@ubuntu:~# root@ubuntu:~# root@ubuntu:~# root@ubuntu:~# drmgr -c cpu -a -q 1 Validating CPU DLPAR capability...yes. [ 218.555493] BUG: arch topology borken [ 218.03] the DIE domain not a subset of the NODE domain [ 218.12] BUG: arch topology borken [ 218.16] the DIE domain not a subset of the NODE domain [ 218.23] BUG: arch topology borken [ 218.28] the DIE domain not a subset of the NODE domain [ 218.35] BUG: arch topology borken [ 218.39] the DIE domain not a subset of the NODE domain [ 218.45] BUG: arch topology borken [ 218.50] the DIE domain not a subset of the NODE domain [ 218.56] BUG: arch topology borken [ 218.60] the DIE domain not a subset of the NODE domain [ 218.67] BUG: arch topology borken [ 218.71] the DIE domain not a subset of the NODE domain [ 218.77] BUG: arch topology borken [ 218.81] the DIE domain not a subset of the NODE domain [ 218.555672] Unable to handle kernel paging request for data at address 0x9332ae80f961139f [ 218.555679] Faulting instruction address: 0xc01768cc [ 218.555686] Oops: Kernel access of bad area, sig: 11 [#1] [ 218.555691] LE SMP NR_CPUS=2048 NUMA pSeries [ 218.555699] Modules linked in: vmx_crypto crct10dif_vpmsum sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear ibmvscsi ibmveth crc32c_vpmsum [ 218.555745] CPU: 8 PID: 276 Comm: kworker/8:1 Not tainted 4.15.0-48-generic #51-Ubuntu [ 218.555757] Workqueue: events cpuset_hotplug_workfn [ 218.555763] NIP: c01768cc LR: c01769a8 CTR: [ 218.555770] REGS: c001f5f1f530 TRAP: 0380 Not tainted (4.15.0-48-generic) [ 218.555776] MSR: 80009033 CR: 22824228 XER: 0004 [ 218.555789] CFAR: c0176920 SOFTE: 1 [ 218.555789] GPR00: c01769a8 c001f5f1f7b0 c16eb400 c001f7bfd200 [ 218.555789] GPR04: 0001 0008 0010 [ 218.555789] GPR08: 0018 c001f7bfd408 [ 218.555789] GPR12: 8000 c7a35800 0007 c001f549d900 [ 218.555789] GPR16: 0040 c1722494 c001f0f29400 0001 [ 218.555789] GPR20: c001ffb68580 0008 c11d8580 c171dd78 [ 218.555789] GPR24: e830 ec30 12af [ 218.555789] GPR28: 102f c001f7bfd200 9332ae80f961139f 9332ae80f961139f [ 218.555859] NIP [c01768cc] free_sched_groups.part.2+0x4c/0xf0 [ 218.555866] LR [c01769a8] destroy_sched_domain+0x38/0xc0 [ 218.555871] Call Trace: [ 218.555875] [c001f5f1f7b0] [ec30] 0xec30 (unreliable) [ 218.555884] [c001f5f1f7f0] [c01769a8] destroy_sched_domain+0x38/0xc0 [ 218.555892] [c001f5f1f820] [c0176eb0] cpu_attach_domain+0xf0/0x870 [ 218.555900] [c001f5f1f960] [c0178884] build_sched_domains+0x1254/0x12f0 [ 218.555908] [c001f5f1fa90] [c0179a70]
[Kernel-packages] [Bug 1833716] Re: System crashes on hot adding a core with drmgr command (4.15.0-48-generic)
== Bionic GA 4.15.0 kernel == ubuntu@P8lpar4:~$ sudo su root@P8lpar4:/home/ubuntu# drmgr -c cpu -r -q 1 Validating CPU DLPAR capability...yes. CPU 121 root@P8lpar4:/home/ubuntu# drmgr -c cpu -a -q 1 [262984.440091] BUG: arch topology borken [262984.440110] the DIE domain not a subset of the NODE domain [262984.440114] BUG: arch topology borken [262984.440116] the DIE domain not a subset of the NODE domain [262984.440120] BUG: arch topology borken [262984.440122] the DIE domain not a subset of the NODE domain [262984.443241] Unable to handle kernel paging request for data at address 0x50dbee4a [262984.443261] Faulting instruction address: 0xc017982c [262984.443281] LE SMP NR_CPUS=2048 NUMA pSeries m iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables ync_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear ibmvscs [262984.443323] CPU: 120 PID: 1467 Comm: kworker/120:2 Not tainted 4.15.0-52-generic #56-Ubuntu [262984.443331] Workqueue: events cpuset_hotplug_workfn [262984.443334] NIP: c017982c LR: c0179908 CTR: [262984.443341] MSR: 80009033 CR: 22824228 XER: 000 5 [262984.443349] GPR00: c0179908 c00fcec0b7b0 c16eb800 c00f7c4 [262984.443349] GPR04: 0001 0008 000 [262984.443349] GPR08: 0018 c00fe22f5808 000 1c600 [262984.443349] GPR16: 03c0 c1722494 c00fd249d800 000 1 [262984.443349] GPR20: c00ff7068580 0008 c11d8580 c17 [262984.443349] GPR24: e830 ec30 000 0102f 65d75 [262984.443389] LR [c0179908] destroy_sched_domain+0x38/0xc0 [262984.443392] Call Trace: [262984.443395] [c00fcec0b7b0] [ec30] 0xec30 (unreliable) [262984.443400] [c00fcec0b7f0] [c0179908] destroy_sched_domain+0x38/0xc0 [262984.443404] [c00fcec0b820] [c0179e10] cpu_attach_domain+0xf0/0x870 [262984.443408] [c00fcec0b960] [c017b7e4] build_sched_domains+0x1254/0x12 f0 [262984.443412] [c00fcec0ba90] [c017c9d0] partition_sched_domains+0x2d0/0 x410 [262984.443416] [c00fcec0bb20] [c0202b20] rebuild_sched_domains_locked+0x 60/0x80 [262984.443420] [c00fcec0bb50] [c0205e28] rebuild_sched_domains+0x38/0x60 [262984.443424] [c00fcec0bb80] [c0205f88] cpuset_hotplug_workfn+0x138/0xb 60 [262984.443429] [c00fcec0bc90] [c0138798] process_one_work+0x298/0x5a0 [262984.443433] [c00fcec0bd20] [c0138b38] worker_thread+0x98/0x630 [262984.443436] [c00fcec0bdc0] [c0141728] kthread+0x1a8/0x1b0 [262984.451901] [c00fcec0be30] [c000b65c] ret_from_kernel_thread+0x5c/0x8 0 [262984.451904] Instruction dump: [262984.451906] 7d908026 fbe1fff8 91810008 f8010010 f821ffc1 7c7d1b78 2e24 7c7f1b 78 [262984.451912] 4810 7fbee840 7fdff378 419e0074 4192002c 7c0004ac e95f 0010 [262984.451919] ---[ end trace b6da6a7114e365f9 ]--- [262984.454656] == After the patches are applied 4.15.0 == ubuntu@P8lpar4:~$ uname -a Linux P8lpar4 4.15.0-53-generic #57~lp1833716+build.1-Ubuntu SMP Fri Jun 21 15:18:40 UTC 2019 ppc64le ppc64le ppc64le GNU/Linux ubuntu@P8lpar4:~$ ubuntu@P8lpar4:~$ sudo su root@P8lpar4:/home/ubuntu# drmgr -c cpu -r -q 1 Validating CPU DLPAR capability...yes. CPU 121 root@P8lpar4:/home/ubuntu# drmgr -c cpu -a -q 1 Validating CPU DLPAR capability...yes. CPU 121 root@P8lpar4:/home/ubuntu# Ubuntu 18.04.2 LTS P8lpar4 hvc0 P8lpar4 login: [ 25.687520] cloud-init[3439]: Cloud-init v. 19.1-1-gbaa47854-0ubunt
[Kernel-packages] [Bug 1833716] Re: System crashes on hot adding a core with drmgr command (4.15.0-48-generic)
** Description changed: + [Impact] + On Bionic GA kernel (4.15.0), hot add of cpu with drmgr causes the kernel to crash. + + [Test] + # drmgr -c cpu -r -q 1 + # drmgr -c cpu -a -q 1 + + [Fix] + 558f86493df0 powerpc/numa: document topology_updates_enabled, disable by default + + 2d4d9b308f8f powerpc/numa: improve control of topology updates + + + [Regression Potential] + The two patches + + == Comment: #0 - Hari Krishna Bathini - 2019-05-07 13:18:35 == ---Problem Description--- On 4.15.0-48-generic kernel, hot adding a cpu with drmgr is crashing the kernel with below traces: --- root@ubuntu:~# drmgr -c cpu -r -q 1 Validating CPU DLPAR capability...yes. CPU 9 - root@ubuntu:~# - root@ubuntu:~# - root@ubuntu:~# - root@ubuntu:~# - root@ubuntu:~# + root@ubuntu:~# + root@ubuntu:~# + root@ubuntu:~# + root@ubuntu:~# + root@ubuntu:~# root@ubuntu:~# drmgr -c cpu -a -q 1 Validating CPU DLPAR capability...yes. [ 218.555493] BUG: arch topology borken [ 218.03] the DIE domain not a subset of the NODE domain [ 218.12] BUG: arch topology borken [ 218.16] the DIE domain not a subset of the NODE domain [ 218.23] BUG: arch topology borken [ 218.28] the DIE domain not a subset of the NODE domain [ 218.35] BUG: arch topology borken [ 218.39] the DIE domain not a subset of the NODE domain [ 218.45] BUG: arch topology borken [ 218.50] the DIE domain not a subset of the NODE domain [ 218.56] BUG: arch topology borken [ 218.60] the DIE domain not a subset of the NODE domain [ 218.67] BUG: arch topology borken [ 218.71] the DIE domain not a subset of the NODE domain [ 218.77] BUG: arch topology borken [ 218.81] the DIE domain not a subset of the NODE domain [ 218.555672] Unable to handle kernel paging request for data at address 0x9332ae80f961139f [ 218.555679] Faulting instruction address: 0xc01768cc [ 218.555686] Oops: Kernel access of bad area, sig: 11 [#1] [ 218.555691] LE SMP NR_CPUS=2048 NUMA pSeries [ 218.555699] Modules linked in: vmx_crypto crct10dif_vpmsum sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear ibmvscsi ibmveth crc32c_vpmsum [ 218.555745] CPU: 8 PID: 276 Comm: kworker/8:1 Not tainted 4.15.0-48-generic #51-Ubuntu [ 218.555757] Workqueue: events cpuset_hotplug_workfn [ 218.555763] NIP: c01768cc LR: c01769a8 CTR: [ 218.555770] REGS: c001f5f1f530 TRAP: 0380 Not tainted (4.15.0-48-generic) [ 218.555776] MSR: 80009033 CR: 22824228 XER: 0004 - [ 218.555789] CFAR: c0176920 SOFTE: 1 - [ 218.555789] GPR00: c01769a8 c001f5f1f7b0 c16eb400 c001f7bfd200 - [ 218.555789] GPR04: 0001 0008 0010 - [ 218.555789] GPR08: 0018 c001f7bfd408 - [ 218.555789] GPR12: 8000 c7a35800 0007 c001f549d900 - [ 218.555789] GPR16: 0040 c1722494 c001f0f29400 0001 - [ 218.555789] GPR20: c001ffb68580 0008 c11d8580 c171dd78 - [ 218.555789] GPR24: e830 ec30 12af - [ 218.555789] GPR28: 102f c001f7bfd200 9332ae80f961139f 9332ae80f961139f + [ 218.555789] CFAR: c0176920 SOFTE: 1 + [ 218.555789] GPR00: c01769a8 c001f5f1f7b0 c16eb400 c001f7bfd200 + [ 218.555789] GPR04: 0001 0008 0010 + [ 218.555789] GPR08: 0018 c001f7bfd408 + [ 218.555789] GPR12: 8000 c7a35800 0007 c001f549d900 + [ 218.555789] GPR16: 0040 c1722494 c001f0f29400 0001 + [ 218.555789] GPR20: c001ffb68580 0008 c11d8580 c171dd78 + [ 218.555789] GPR24: e830 ec30 12af + [ 218.555789] GPR28: 102f c001f7bfd200 9332ae80f961139f 9332ae80f961139f [ 218.555859] NIP [c01768cc] free_sched_groups.part.2+0x4c/0xf0 [ 218.555866] LR [c01769a8] destroy_sched_domain+0x38/0xc0 [ 218.555871] Call Trace: [ 218.555875] [c001f5f1f7b0] [ec30] 0xec30 (unreliable) [ 218.555884] [c001f5f1f7f0] [c01769a8] destroy_sched_domain+0x38/0xc0 [ 218.555892] [c001f5f1f820] [c0176eb0] cpu_attach_domain+0xf0/0x870 [ 218.555900] [c001f5f1f960] [c0178884]
[Kernel-packages] [Bug 1804149] Re: Kernel panic, Oops: 0004 ilc:3 [#1] SMP, iscsi_q_20 iscsi_xmitworker [libiscsi]
** Changed in: linux (Ubuntu) Importance: High => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1804149 Title: Kernel panic,Oops: 0004 ilc:3 [#1] SMP, iscsi_q_20 iscsi_xmitworker [libiscsi] Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: Triaged Bug description: == Comment: #0 - Michael Finnegan - 2018-11-19 14:14:40 == ---Problem Description--- Kernel panic,Oops: 0004 ilc:3 [#1] SMP, iscsi_q_20 iscsi_xmitworker [libiscsi] ---uname output--- Linux ilabg3 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:13:24 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = IBM 3906 M05 7G4 (z/VM 7.1.0) ---Debugger--- A debugger is not configured Contact Information = Michael Finnegan/finne...@us.ibm.com Stack trace output: dmesg.201811161956 [1363037.322472] Unable to handle kernel pointer dereference in virtual kernel address space [1363037.322481] Failing address: TEID: 0483 [1363037.322483] Fault in home space mode while using kernel ASCE. [1363037.322486] AS:00ea0007 R3:f37d0007 S:f37ff000 P:013d [1363037.322524] Oops: 0004 ilc:3 [#1] SMP [1363037.322529] Modules linked in: iptable_filter binfmt_misc rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache qeth_l3 qeth_l2 s390_trng ghash_s390 prng aes_s390 des_s390 des_generic sha512_s390 sha256_s390 sha1_s390 sha_common qeth vmur ccwgroup vfio_ccw vfio_mdev mdev vfio_iommu_type1 vfio sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core sunrpc iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables dm_round_robin dm_service_time crc32_vx_s390 dasd_eckd_mod zfcp qdio scsi_transport_fc dasd_fba_mod dasd_mod scsi_dh_emc scsi_dh_rdac scsi_dh_alua dm_multipath [1363037.322567] CPU: 3 PID: 37970 Comm: kworker/u128:19 Not tainted 4.15.0-36-generic #39-Ubuntu [1363037.322573] Hardware name: IBM 3906 M05 7G4 (z/VM 7.1.0) [1363037.322581] Workqueue: iscsi_q_20 iscsi_xmitworker [libiscsi] [1363037.322583] Krnl PSW : c8051cf6 e49a28f4 (__iscsi_get_task+0x6/0x18 [libiscsi]) [1363037.322587]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:2 PM:0 RI:0 EA:3 [1363037.322589] Krnl GPRS: 02923ce0 0400 [1363037.322591]03ff80277640 0008 788efc00 03ff802777cc [1363037.322592]03ff8027769c 78ce8310 [1363037.322594]f3689800 78ce83a2 03ff80272e8e 02923c90 [1363037.322601] Krnl Code: 03ff80272624: c0f4fcf6 brcl 15,3ff80272010 03ff8027262a: c0f4377b brcl 15,3ff80279520 #03ff80272630: c004 brcl 0,3ff80272630 >03ff80272636: eb012078006a asi 120(%r2),1 03ff8027263c: c0f43772 brcl 15,3ff80279520 03ff80272642: 0707 bcr 0,%r7 03ff80272644: 0707 bcr 0,%r7 03ff80272646: 0707 bcr 0,%r7 [1363037.322618] Call Trace: [1363037.322621] ([<03ff80272ec6>] iscsi_xmit_task+0x86/0x138 [libiscsi]) [1363037.322625] [<03ff8027769c>] iscsi_data_xmit+0x44c/0x548 [libiscsi] [1363037.322636] [<03ff802777cc>] iscsi_xmitworker+0x34/0x58 [libiscsi] [1363037.322642] [<001918f2>] process_one_work+0x262/0x4d8 [1363037.322644] [<00191bc0>] worker_thread+0x58/0x4e8 [1363037.322648] [<00198d24>] kthread+0x14c/0x168 [1363037.322652] [<008e3eb2>] kernel_thread_starter+0xa/0x10 [1363037.322654] [<008e3ea8>] kernel_thread_starter+0x0/0x10 [1363037.322655] Last Breaking-Event-Address: [1363037.322657] [<03ff80272e88>] iscsi_xmit_task+0x48/0x138 [libiscsi] [1363037.322658] [1363037.322660] Kernel panic - not syncing: Fatal exception in interrupt Oops output: Oops: 0004 ilc:3 [#1] SMP *Additional Instructions for Michael Finnegan/finne...@us.ibm.com: -Post a private note with access information to the machine that the bug is occuring on. -Attach sysctl -a output output to the bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1804149/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1741860] Re: Use the kernel default for crashkernel offset
Is this issue even reproducible on Disco or Eoan? Looks like there are fixes that could have landed for this issue in 18.10. Can IBM please confirm this is an issue in Disco and Eoan? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1741860 Title: Use the kernel default for crashkernel offset Status in The Ubuntu-power-systems project: Incomplete Status in makedumpfile package in Ubuntu: Incomplete Bug description: == Comment: #0 - Hari Krishna Bathini - 2018-01-08 01:06:41 == ---Problem Description--- A default offset of 128MB is enforced for crashkernel by kdump-tools utility overriding the kernel default. While the kernel default offset for crashkernel is also 128MB, that may change and the right thing to do would be to let the kernel decide on the offset of crashkernel in the default scenario.. Get rid of "@128M" in kdump-tools.cfg file Contact Information = hbath...@in.ibm.com ---uname output--- na Machine Type = na ---Debugger--- A debugger is not configured ---Steps to Reproduce--- # cat /etc/default/grub.d/kdump-tools.cfg GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M@128M" --- The offset is specified via kdump-tools where as the kernel may be the right place to set an offset by default.. Userspace tool common name: kdump-tools The userspace tool has the following bit modes: 64-bit Userspace rpm: kdump-tools Userspace tool obtained from project website: na *Additional Instructions for hbath...@in.ibm.com: -Attach ltrace and strace of userspace application. == Comment: #3 - MAMATHA INAMDAR - 2018-01-08 03:05:05 == This bug is opened to follow-up other bug based on the comment 19 https://bugzilla.linux.ibm.com/show_bug.cgi?id=152905#c19 (Canonical Launchpad1676884 ) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1741860/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802233] Re: hwclock test failed on Power9 due to 0.x sec differences / time out waiting for time change
IBM indicated that they do not have an ETA for a GA release of the BMC
firmware with this fix. Would the kernel team be ok with working around
this issue in the testcase by adding a .5 delay?
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1802233
Title:
hwclock test failed on Power9 due to 0.x sec differences / time out
waiting for time change
Status in ubuntu-kernel-tests:
New
Status in The Ubuntu-power-systems project:
Fix Committed
Status in linux package in Ubuntu:
Invalid
Bug description:
The hwclock test will fail on the Power9 system "baltar" due to a
<0.02 second difference.
Traceback (most recent call last):
File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec
_call_test_function(self.execute, *p_args, **p_dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 823, in
_call_test_function
return func(*args, **dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute
postprocess_profiled_run, args, dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 212, in
_call_run_once
self.run_once(*args, **dargs)
File "/home/ubuntu/autotest/client/tests/hwclock/hwclock.py", line 50, in
run_once
raise error.TestFail("Failed to set hwclock back to Warthog's birthday.
Output of hwclock is '%s'" % date)
TestFail: Failed to set hwclock back to Warthog's birthday. Output of hwclock
is '2004-10-20 04:09:59.582146+'
Didn't see this on Power8 boxes
Sometimes it will fail because "time out waiting for time change" on the same
node:
$ sudo /sbin/hwclock --set --date "2004/10/20 04:10:00"; sudo /sbin/hwclock
hwclock: Timed out waiting for time change.
Workaround for these is to add "sleep 1".
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-38-generic 4.15.0-38.41
ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
Uname: Linux 4.15.0-38-generic ppc64le
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Nov 8 03:45 seq
crw-rw 1 root audio 116, 33 Nov 8 03:45 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: ppc64el
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord':
'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CurrentDmesg:
Date: Thu Nov 8 06:03:54 2018
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0451:80ff Texas Instruments, Inc.
Bus 001 Device 004: ID 0557:2419 ATEN International Co., Ltd
Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
PciMultimedia:
ProcFB: 0 astdrmfb
ProcKernelCmdLine: root=UUID=acd1a0d7-f6fc-4130-928c-c8b11ad6e4be ro
console=hvc0
ProcLoadAvg: 0.31 0.11 0.03 1/1392 5654
ProcLocks:
1: POSIX ADVISORY WRITE 3544 00:17:582 0 EOF
2: POSIX ADVISORY WRITE 1798 00:17:338 0 EOF
3: POSIX ADVISORY WRITE 3603 00:17:576 0 EOF
4: FLOCK ADVISORY WRITE 3535 00:17:564 0 EOF
5: FLOCK ADVISORY WRITE 4081 00:17:481 0 EOF
ProcSwaps:
Filename TypeSizeUsedPriority
/swap.img file 8388544 0 -2
ProcVersion: Linux version 4.15.0-38-generic (buildd@bos02-ppc64el-018) (gcc
version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #41-Ubuntu SMP Wed Oct 10 10:57:45 UTC
2018
RelatedPackageVersions:
linux-restricted-modules-4.15.0-38-generic N/A
linux-backports-modules-4.15.0-38-generic N/A
linux-firmware 1.173.1
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
VarLogDump_list: total 0
cpu_cores: Number of cores present = 40
cpu_coreson: Number of cores online = 40
cpu_dscr: DSCR is 16
cpu_freq:
min: 2.862 GHz (cpu 159)
max: 2.862 GHz (cpu 1)
avg: 2.862 GHz
cpu_runmode:
Could not retrieve current diagnostics mode,
No kernel interface to firmware
cpu_smt: SMT=4
-- Firmware information on Baltar --
pnor: P9DSU20190404_IBM_prod_sign.pnor
bmc: SMT_P9_206.bin
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1802233/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827335] Re: Unable to put offline CPU back online on Bionic/B-hwe-edge P9
Based on my debugging as well as confirmation from IBM this appears to be a hardware issue that triggers the firmware to offline faulty cores. This is not a kernel issue so closing this bug as invalid. ** Changed in: ubuntu-power-systems Status: Incomplete => Invalid ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1827335 Title: Unable to put offline CPU back online on Bionic/B-hwe-edge P9 Status in The Ubuntu-power-systems project: Invalid Status in linux package in Ubuntu: Invalid Bug description: You will see these CPUs in offline state after boot. ubuntu@baltar:~$ cat /sys/devices/system/cpu/offline 156-159 ubuntu@baltar:~$ echo 1 | sudo tee /sys/devices/system/cpu/cpu156/online 1 tee: /sys/devices/system/cpu/cpu156/online: Invalid argument ubuntu@baltar:~$ echo 1 | sudo tee /sys/devices/system/cpu/cpu157/online 1 tee: /sys/devices/system/cpu/cpu157/online: Invalid argument ubuntu@baltar:~$ echo 1 | sudo tee /sys/devices/system/cpu/cpu158/online 1 tee: /sys/devices/system/cpu/cpu158/online: Invalid argument ubuntu@baltar:~$ echo 1 | sudo tee /sys/devices/system/cpu/cpu159/online 1 tee: /sys/devices/system/cpu/cpu159/online: Invalid argument ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.0.0-14-generic 5.0.0-14.15~18.04.1+signed1 ProcVersionSignature: Ubuntu 5.0.0-14.15~18.04.1-generic 5.0.6 Uname: Linux 5.0.0-14-generic ppc64le ApportVersion: 2.20.9-0ubuntu7.6 Architecture: ppc64el Date: Thu May 2 06:46:36 2019 ProcLoadAvg: 0.00 0.00 0.00 1/1298 6496 ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -2 ProcVersion: Linux version 5.0.0-14-generic (buildd@bos02-ppc64el-014) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #15~18.04.1-Ubuntu SMP Thu Apr 25 18:55:27 UTC 2019 SourcePackage: linux-signed-hwe-edge UpgradeStatus: No upgrade log present (probably fresh install) VarLogDump_list: total 0 cpu_cores: Number of cores present = 40 cpu_coreson: Number of cores online = 39 cpu_dscr: DSCR is 16 cpu_freq: min: 2.862 GHz (cpu 79) max: 2.945 GHz (cpu 81) avg: 2.903 GHz cpu_runmode: Could not retrieve current diagnostics mode, No kernel interface to firmware cpu_smt: SMT=4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1827335/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1833716] Re: System crashes on hot adding a core with drmgr command (4.15.0-48-generic)
** Changed in: linux (Ubuntu) Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: ubuntu-power-systems Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: linux (Ubuntu) Assignee: Canonical Kernel Team (canonical-kernel-team) => Manoj Iyer (manjo) ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: ubuntu-power-systems Assignee: Canonical Kernel Team (canonical-kernel-team) => Manoj Iyer (manjo) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1833716 Title: System crashes on hot adding a core with drmgr command (4.15.0-48-generic) Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: New Bug description: == Comment: #0 - Hari Krishna Bathini - 2019-05-07 13:18:35 == ---Problem Description--- On 4.15.0-48-generic kernel, hot adding a cpu with drmgr is crashing the kernel with below traces: --- root@ubuntu:~# drmgr -c cpu -r -q 1 Validating CPU DLPAR capability...yes. CPU 9 root@ubuntu:~# root@ubuntu:~# root@ubuntu:~# root@ubuntu:~# root@ubuntu:~# root@ubuntu:~# drmgr -c cpu -a -q 1 Validating CPU DLPAR capability...yes. [ 218.555493] BUG: arch topology borken [ 218.03] the DIE domain not a subset of the NODE domain [ 218.12] BUG: arch topology borken [ 218.16] the DIE domain not a subset of the NODE domain [ 218.23] BUG: arch topology borken [ 218.28] the DIE domain not a subset of the NODE domain [ 218.35] BUG: arch topology borken [ 218.39] the DIE domain not a subset of the NODE domain [ 218.45] BUG: arch topology borken [ 218.50] the DIE domain not a subset of the NODE domain [ 218.56] BUG: arch topology borken [ 218.60] the DIE domain not a subset of the NODE domain [ 218.67] BUG: arch topology borken [ 218.71] the DIE domain not a subset of the NODE domain [ 218.77] BUG: arch topology borken [ 218.81] the DIE domain not a subset of the NODE domain [ 218.555672] Unable to handle kernel paging request for data at address 0x9332ae80f961139f [ 218.555679] Faulting instruction address: 0xc01768cc [ 218.555686] Oops: Kernel access of bad area, sig: 11 [#1] [ 218.555691] LE SMP NR_CPUS=2048 NUMA pSeries [ 218.555699] Modules linked in: vmx_crypto crct10dif_vpmsum sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear ibmvscsi ibmveth crc32c_vpmsum [ 218.555745] CPU: 8 PID: 276 Comm: kworker/8:1 Not tainted 4.15.0-48-generic #51-Ubuntu [ 218.555757] Workqueue: events cpuset_hotplug_workfn [ 218.555763] NIP: c01768cc LR: c01769a8 CTR: [ 218.555770] REGS: c001f5f1f530 TRAP: 0380 Not tainted (4.15.0-48-generic) [ 218.555776] MSR: 80009033 CR: 22824228 XER: 0004 [ 218.555789] CFAR: c0176920 SOFTE: 1 [ 218.555789] GPR00: c01769a8 c001f5f1f7b0 c16eb400 c001f7bfd200 [ 218.555789] GPR04: 0001 0008 0010 [ 218.555789] GPR08: 0018 c001f7bfd408 [ 218.555789] GPR12: 8000 c7a35800 0007 c001f549d900 [ 218.555789] GPR16: 0040 c1722494 c001f0f29400 0001 [ 218.555789] GPR20: c001ffb68580 0008 c11d8580 c171dd78 [ 218.555789] GPR24: e830 ec30 12af [ 218.555789] GPR28: 102f c001f7bfd200 9332ae80f961139f 9332ae80f961139f [ 218.555859] NIP [c01768cc] free_sched_groups.part.2+0x4c/0xf0 [ 218.555866] LR [c01769a8] destroy_sched_domain+0x38/0xc0 [ 218.555871] Call Trace: [ 218.555875] [c001f5f1f7b0] [ec30] 0xec30 (unreliable) [ 218.555884] [c001f5f1f7f0] [c01769a8] destroy_sched_domain+0x38/0xc0 [ 218.555892] [c001f5f1f820] [c0176eb0] cpu_attach_domain+0xf0/0x870 [ 218.555900] [c001f5f1f960] [c0178884] build_sched_domains+0x1254/0x12f0 [ 218.555908] [c001f5f1fa90] [c0179a70] partition_sched_domains+0x2d0/0x410 [ 218.555916] [c001f5f1fb20] [c01ffb60] rebuild_sched_domains_locked+0x60/0x80 [ 218.555924] [c001f5f1fb50] [c0202e68] rebuild_sched_domains+0x38/0x60 [ 218.555932] [c001f5f1fb80] [c
[Kernel-packages] [Bug 1832388] Re: [power9] [Cosmic] kernel panic while testing kdump
** Changed in: ubuntu-power-systems Importance: Critical => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1832388 Title: [power9] [Cosmic] kernel panic while testing kdump Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Status in linux source package in Cosmic: Incomplete Bug description: I installed cosmic on power9 (boston) a non-nvme system, installed initramfs-tools from -proposed and install kdump-tools. Triggered a dump, but I got a kernel panic. This might be a kernel bug/regression. ubuntu@tiselius:~$ uname -a Linux tiselius 4.18.0-21-generic #22-Ubuntu SMP Wed May 15 13:12:45 UTC 2019 ppc64le ppc64le ppc64le GNU/Linux ubuntu@tiselius:~$ ubuntu@tiselius:~$ apt policy initramfs-tools initramfs-tools: Installed: 0.131ubuntu15.2 Candidate: 0.131ubuntu15.2 Version table: *** 0.131ubuntu15.2 500 500 http://ports.ubuntu.com/ubuntu-ports cosmic-proposed/main ppc64el Packages ubuntu@tiselius:~$ ubuntu@tiselius:~$ apt policy kdump-tools kdump-tools: Installed: 1:1.6.5-1ubuntu1~18.10.1 Candidate: 1:1.6.5-1ubuntu1~18.10.1 Version table: *** 1:1.6.5-1ubuntu1~18.10.1 500 500 http://ports.ubuntu.com/ubuntu-ports cosmic-updates/main ppc64el Packages 100 /var/lib/dpkg/status 1:1.6.4-2ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports cosmic/main ppc64el Packages ubuntu@tiselius:~$ ubuntu@tiselius:~$ sudo kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.18.0-21-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.18.0-21-generic current state:ready to kdump kexec command: /sbin/kexec -p --command-line="root=UUID=295f571b-b731-4ebb-b752-60aadc80fc1b ro console=hvc0 nr_cpus=1 systemd.unit=kdump-tools-dump.service irqpoll noirqdistrib nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz ubuntu@tiselius:~$ ubuntu@tiselius:~$ cat /proc/cmdline root=UUID=295f571b-b731-4ebb-b752-60aadc80fc1b ro console=hvc0 crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M@128M ubuntu@tiselius:~$ ubuntu@tiselius:~$ dmesg | grep Reser [0.00] Reserving 4096MB of memory at 128MB for crashkernel (System RAM: 131072MB) [0.00] cma: Reserved 6560 MiB at 0x200e6200 ubuntu@tiselius:~$ root@tiselius:/home/ubuntu# echo 1 > /proc/sys/kernel/sysrq root@tiselius:/home/ubuntu# echo c > /proc/sysrq-trigger tiselius login: [ 150.167288] cloud-init[4529]: Cloud-init v. 19.1-1-gbaa47854-0ubuntu1~18.10.1 running 'modules:final' at Mon, 10 Jun 2019 19:53:40 +. Up 149.80 seconds. [ 150.167687] cloud-init[4529]: Cloud-init v. 19.1-1-gbaa47854-0ubuntu1~18.10.1 finished at Mon, 10 Jun 2019 19:53:40 +. Datasource DataSourceMAAS [http://10-245-64-0--21.maas-internal:5248/MAAS/metadata/]. Up 150.11 seconds [ 360.313029] kdump-tools[4915]: Stopping kdump-tools: * unloaded kdump kernel [ 376.552452] kdump-tools[10449]: Starting kdump-tools: * Creating symlink /var/lib/kdump/vmlinuz [ 376.553743] kdump-tools[10449]: * Creating symlink /var/lib/kdump/initrd.img [ 376.585085] kdump-tools[10449]: Modified cmdline:root=UUID=295f571b-b731-4ebb-b752-60aadc80fc1b ro console=hvc0 nr_cpus=1 systemd.unit=kdump-tools-dump.service irqpoll noirqdistrib nousb elfcorehdr=158784K [ 376.953223] kdump-tools[10449]: * loaded kdump kernel [ 398.517900] sysrq: SysRq : Trigger a crash [ 398.517952] Unable to handle kernel paging request for data at address 0x [ 398.518000] Faulting instruction address: 0xc082a3a8 [ 398.518071] Oops: Kernel access of bad area, sig: 11 [#1] [ 398.518115] LE SMP NR_CPUS=2048 NUMA PowerNV [ 398.518172] Modules linked in: joydev input_leds mac_hid vmx_crypto ofpart crct10dif_vpmsum ipmi_powernv ipmi_devintf at24 uio_pdrv_genirq ipmi_msghandler uio cmdlinepart powernv_flash mtd opal_prd ibmpowernv sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear ses enclosure scsi_transport_sas hid_generic usbhid hid ast i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm crc32c_vpmsum i40e aacraid drm_panel_orientation_quirks [ 398.518769] CPU: 0 PID: 10529 Comm: bash Kdump: loaded Not tainted 4.18.0-21-generic #22-Ubuntu [ 398.518881] NIP: c082a3a8 LR: c082b234 CTR: c082a380 [
[Kernel-packages] [Bug 1802233] Re: hwclock test failed on Power9 due to 0.x sec differences / time out waiting for time change
** Changed in: ubuntu-power-systems
Status: Incomplete => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1802233
Title:
hwclock test failed on Power9 due to 0.x sec differences / time out
waiting for time change
Status in ubuntu-kernel-tests:
New
Status in The Ubuntu-power-systems project:
Fix Committed
Status in linux package in Ubuntu:
Incomplete
Bug description:
The hwclock test will fail on the Power9 system "baltar" due to a
<0.02 second difference.
Traceback (most recent call last):
File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec
_call_test_function(self.execute, *p_args, **p_dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 823, in
_call_test_function
return func(*args, **dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute
postprocess_profiled_run, args, dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 212, in
_call_run_once
self.run_once(*args, **dargs)
File "/home/ubuntu/autotest/client/tests/hwclock/hwclock.py", line 50, in
run_once
raise error.TestFail("Failed to set hwclock back to Warthog's birthday.
Output of hwclock is '%s'" % date)
TestFail: Failed to set hwclock back to Warthog's birthday. Output of hwclock
is '2004-10-20 04:09:59.582146+'
Didn't see this on Power8 boxes
Sometimes it will fail because "time out waiting for time change" on the same
node:
$ sudo /sbin/hwclock --set --date "2004/10/20 04:10:00"; sudo /sbin/hwclock
hwclock: Timed out waiting for time change.
Workaround for these is to add "sleep 1".
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-38-generic 4.15.0-38.41
ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
Uname: Linux 4.15.0-38-generic ppc64le
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Nov 8 03:45 seq
crw-rw 1 root audio 116, 33 Nov 8 03:45 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: ppc64el
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord':
'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CurrentDmesg:
Date: Thu Nov 8 06:03:54 2018
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0451:80ff Texas Instruments, Inc.
Bus 001 Device 004: ID 0557:2419 ATEN International Co., Ltd
Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
PciMultimedia:
ProcFB: 0 astdrmfb
ProcKernelCmdLine: root=UUID=acd1a0d7-f6fc-4130-928c-c8b11ad6e4be ro
console=hvc0
ProcLoadAvg: 0.31 0.11 0.03 1/1392 5654
ProcLocks:
1: POSIX ADVISORY WRITE 3544 00:17:582 0 EOF
2: POSIX ADVISORY WRITE 1798 00:17:338 0 EOF
3: POSIX ADVISORY WRITE 3603 00:17:576 0 EOF
4: FLOCK ADVISORY WRITE 3535 00:17:564 0 EOF
5: FLOCK ADVISORY WRITE 4081 00:17:481 0 EOF
ProcSwaps:
Filename TypeSizeUsedPriority
/swap.img file 8388544 0 -2
ProcVersion: Linux version 4.15.0-38-generic (buildd@bos02-ppc64el-018) (gcc
version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #41-Ubuntu SMP Wed Oct 10 10:57:45 UTC
2018
RelatedPackageVersions:
linux-restricted-modules-4.15.0-38-generic N/A
linux-backports-modules-4.15.0-38-generic N/A
linux-firmware 1.173.1
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
VarLogDump_list: total 0
cpu_cores: Number of cores present = 40
cpu_coreson: Number of cores online = 40
cpu_dscr: DSCR is 16
cpu_freq:
min: 2.862 GHz (cpu 159)
max: 2.862 GHz (cpu 1)
avg: 2.862 GHz
cpu_runmode:
Could not retrieve current diagnostics mode,
No kernel interface to firmware
cpu_smt: SMT=4
-- Firmware information on Baltar --
pnor: P9DSU20190404_IBM_prod_sign.pnor
bmc: SMT_P9_206.bin
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1802233/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802233] Re: hwclock test failed on Power9 due to 0.x sec differences / time out waiting for time change
I upgraded the firmware on tiselius (boston p9) and ran the testcase and
it works as expected.
ubuntu@tiselius:~$ sudo /sbin/hwclock --set --date "2019/06/10 12:55:00"; sudo
/sbin/hwclock
2019-06-10 12:54:59.969984+00:00
ubuntu@tiselius:~$
should I wait for the release version of the firmware before I upgrade
the other boston systems?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1802233
Title:
hwclock test failed on Power9 due to 0.x sec differences / time out
waiting for time change
Status in ubuntu-kernel-tests:
New
Status in The Ubuntu-power-systems project:
Incomplete
Status in linux package in Ubuntu:
Incomplete
Bug description:
The hwclock test will fail on the Power9 system "baltar" due to a
<0.02 second difference.
Traceback (most recent call last):
File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec
_call_test_function(self.execute, *p_args, **p_dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 823, in
_call_test_function
return func(*args, **dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute
postprocess_profiled_run, args, dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 212, in
_call_run_once
self.run_once(*args, **dargs)
File "/home/ubuntu/autotest/client/tests/hwclock/hwclock.py", line 50, in
run_once
raise error.TestFail("Failed to set hwclock back to Warthog's birthday.
Output of hwclock is '%s'" % date)
TestFail: Failed to set hwclock back to Warthog's birthday. Output of hwclock
is '2004-10-20 04:09:59.582146+'
Didn't see this on Power8 boxes
Sometimes it will fail because "time out waiting for time change" on the same
node:
$ sudo /sbin/hwclock --set --date "2004/10/20 04:10:00"; sudo /sbin/hwclock
hwclock: Timed out waiting for time change.
Workaround for these is to add "sleep 1".
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-38-generic 4.15.0-38.41
ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
Uname: Linux 4.15.0-38-generic ppc64le
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Nov 8 03:45 seq
crw-rw 1 root audio 116, 33 Nov 8 03:45 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: ppc64el
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord':
'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CurrentDmesg:
Date: Thu Nov 8 06:03:54 2018
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0451:80ff Texas Instruments, Inc.
Bus 001 Device 004: ID 0557:2419 ATEN International Co., Ltd
Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
PciMultimedia:
ProcFB: 0 astdrmfb
ProcKernelCmdLine: root=UUID=acd1a0d7-f6fc-4130-928c-c8b11ad6e4be ro
console=hvc0
ProcLoadAvg: 0.31 0.11 0.03 1/1392 5654
ProcLocks:
1: POSIX ADVISORY WRITE 3544 00:17:582 0 EOF
2: POSIX ADVISORY WRITE 1798 00:17:338 0 EOF
3: POSIX ADVISORY WRITE 3603 00:17:576 0 EOF
4: FLOCK ADVISORY WRITE 3535 00:17:564 0 EOF
5: FLOCK ADVISORY WRITE 4081 00:17:481 0 EOF
ProcSwaps:
Filename TypeSizeUsedPriority
/swap.img file 8388544 0 -2
ProcVersion: Linux version 4.15.0-38-generic (buildd@bos02-ppc64el-018) (gcc
version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #41-Ubuntu SMP Wed Oct 10 10:57:45 UTC
2018
RelatedPackageVersions:
linux-restricted-modules-4.15.0-38-generic N/A
linux-backports-modules-4.15.0-38-generic N/A
linux-firmware 1.173.1
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
VarLogDump_list: total 0
cpu_cores: Number of cores present = 40
cpu_coreson: Number of cores online = 40
cpu_dscr: DSCR is 16
cpu_freq:
min: 2.862 GHz (cpu 159)
max: 2.862 GHz (cpu 1)
avg: 2.862 GHz
cpu_runmode:
Could not retrieve current diagnostics mode,
No kernel interface to firmware
cpu_smt: SMT=4
-- Firmware information on Baltar --
pnor: P9DSU20190404_IBM_prod_sign.pnor
bmc: SMT_P9_206.bin
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1802233/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help :
[Kernel-packages] [Bug 1812822] Re: Guest crashed when detaching the ovs interface device
** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1812822 Title: Guest crashed when detaching the ovs interface device Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: Invalid Status in qemu package in Ubuntu: Incomplete Bug description: When detaching one openvswitch interface device with virsh detach-device, if the port has been deleted from the ovs and the interface device has been deleted. The virsh detach-device will fail with "error: Unable to read from monitor: Connection reset by peer", the qemu is terminated and the log shows " UNSETVNETLE ioctl() failed, File descriptor in bad state". [Background] This error is originally found from the openstack KVM CI tempest test. By investigating I found it's introduced by one ovs-vif patch, which deletes the ovs port and delete the interface before detaching the device. You can find the commit from https://bugs.launchpad.net/os-vif/+bug/1801072 Reproduced: root@:~# ovs-vsctl del-port br0 tap9273235a-dd root@:~# ip link del tap9273235a-dd The interface device tap9273235a-dd has been removed from the host(ifconfg, ovs-vsctl show) and can be found in the guest.(logon the guest, ip a it's in down state) root@:~# virsh detach-device kvm net.xml error: Failed to detach device from net.xml error: Unable to read from monitor: Connection reset by peer The qemu has terminated and the log in /var/log/libvirt/qemu/kvm.log TUNSETVNETLE ioctl() failed: File descriptor in bad state. 2019-01-18 08:16:11.304+: shutting down, reason=crashed It seems the qemu tried to handle this interface, but in fact it has been deleted. qemu couldn't read the file and give the error. But I don't think the guest should be crashed directly for the file descriptor error. Environment: Ubuntu 16.04.5 LTS Linux (EC12) 4.4.0-141-generic QEMU emulator version 2.11.1(Debian 1:2.11+dfsg-1ubuntu7.5~cloud0) libvirtd (libvirt) 4.0.0 net.xml kvm.xml kvm 59f71b47-16e4-401d-9d33-30bc1605a84a 524288 524288 1 /machine hvm destroy restart destroy /usr/bin/qemu-system-s390x libvirt-59f71b47-16e4-401d-9d33-30bc1605a84a libvirt-59f71b47-16e4-401d-9d33-30bc1605a84a +0:+0 +0:+0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1812822/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828166] Re: perf top problem on z with Ubuntu 18.04
** Changed in: linux (Ubuntu) Status: Fix Released => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828166 Title: perf top problem on z with Ubuntu 18.04 Status in Ubuntu on IBM z Systems: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Bug description: SRU Justification: == [Impact] * The perf top tool hangs and shows error messages, like 'Not enough memory for annotating' [Fix] * edeb0c90df3581b821a764052d185df985f8b8dc edeb0c9 "perf tools: Stop fallbacking to kallsyms for vdso symbols lookup" [Test Case] * start a benchmark (mem_alloc, but it doesn't really matter what) * execute perf top in a second terminal * the output of perf top is correct * now stop the benchmark * and perf top shows an error message, like "Not enough memory for annotating '__irf_end' symbol!)" * and perf top can't be exited anymore [Regression Potential] * The regression potential can be considered as low since this happens only while using the perf top tool * and it is known that the commit (above) fixes the problem * and the fix is upstream since 4.19 [Other Info] * current disco and eoan kernels don't show that problem * bisecting result points to above commit * applies cleanly on cosmic, but has a little conflict on bionic (both master-next) _ perf top hangs and shows error messages ---uname output--- Linux weather 4.15.0-46-generic #49-Ubuntu SMP Wed Feb 6 09:32:27 UTC 2019 s390x s390x s390x GNU/Linux ---Steps to Reproduce--- I start a benchmark (mem_alloc, but it really doesn't matter) and then issue perf top in a second terminal, the output from perf top is correct. Now I stop the benchmark: perf top shows a error message (Not enough memory for annotating '__irf_end' symbol!) and I can't quit from perf top anymore Following analyse took place: No problem with current kernel . Bi-Secting of perf tool took place and following commit was found: commit edeb0c90df3581b821a764052d185df985f8b8dc (HEAD, refs/bisect/bad) Author: Arnaldo Carvalho de Melo Date: Tue Oct 16 17:08:29 2018 -0300 perf tools: Stop fallbacking to kallsyms for vdso symbols lookup When you apply this patch the issue is gone, however it is contained in these versions: git tag --contains edeb0c90df3581b821 v4.19 v4.20 The level I was debugging was kernel 4.15 which does not contain this patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1828166/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829972] Re: Require improved hypervisor detection patch in Ubuntu 18.04
** Changed in: linux (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1829972 Title: Require improved hypervisor detection patch in Ubuntu 18.04 Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: == Justification == The s390x early machine detection code check will set all the uknown hypervisors to z/VM, this will cause crash for any non KVM, z/VM system. == Fixes == 03aa047e (s390/early: improve machine detection) Patch can be cherry-picked into Bionic kernel. Instead of setting all the other hypervisors to z/VM, it will only set MACHINE_FLAG_VM if it matches the case. == Tests == A test kernel could be found here: https://people.canonical.com/~phlin/kernel/lp-1829972-s390x-early/ Boot tested on a s390x KVM node and verified by IBM as well. == Regression Potential == Low, this just improves the detection logic and the changes are specific to s390x. == Original Bug Report == This kernel commit is requested to be included into the bionic's 4.15.0 LTS kernel: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=03aa047ef2db4985e444af6ee1c1dd084ad9fb4c s390/early: improve machine detection Right now the early machine detection code check stsi 3.2.2 for "KVM" and set MACHINE_IS_VM if this is different. As the console detection uses diagnose 8 if MACHINE_IS_VM returns true this will crash Linux early for any non z/VM system that sets a different value than KVM. So instead of assuming z/VM, do not set any of MACHINE_IS_LPAR, MACHINE_IS_VM, or MACHINE_IS_KVM. This is required for a dedicated SSC exploiter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1829972/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832388] Re: [power9] [Cosmic] kernel panic while testing kdump
** Changed in: ubuntu-power-systems Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1832388 Title: [power9] [Cosmic] kernel panic while testing kdump Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Status in linux source package in Cosmic: Incomplete Bug description: I installed cosmic on power9 (boston) a non-nvme system, installed initramfs-tools from -proposed and install kdump-tools. Triggered a dump, but I got a kernel panic. This might be a kernel bug/regression. ubuntu@tiselius:~$ uname -a Linux tiselius 4.18.0-21-generic #22-Ubuntu SMP Wed May 15 13:12:45 UTC 2019 ppc64le ppc64le ppc64le GNU/Linux ubuntu@tiselius:~$ ubuntu@tiselius:~$ apt policy initramfs-tools initramfs-tools: Installed: 0.131ubuntu15.2 Candidate: 0.131ubuntu15.2 Version table: *** 0.131ubuntu15.2 500 500 http://ports.ubuntu.com/ubuntu-ports cosmic-proposed/main ppc64el Packages ubuntu@tiselius:~$ ubuntu@tiselius:~$ apt policy kdump-tools kdump-tools: Installed: 1:1.6.5-1ubuntu1~18.10.1 Candidate: 1:1.6.5-1ubuntu1~18.10.1 Version table: *** 1:1.6.5-1ubuntu1~18.10.1 500 500 http://ports.ubuntu.com/ubuntu-ports cosmic-updates/main ppc64el Packages 100 /var/lib/dpkg/status 1:1.6.4-2ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports cosmic/main ppc64el Packages ubuntu@tiselius:~$ ubuntu@tiselius:~$ sudo kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.18.0-21-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.18.0-21-generic current state:ready to kdump kexec command: /sbin/kexec -p --command-line="root=UUID=295f571b-b731-4ebb-b752-60aadc80fc1b ro console=hvc0 nr_cpus=1 systemd.unit=kdump-tools-dump.service irqpoll noirqdistrib nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz ubuntu@tiselius:~$ ubuntu@tiselius:~$ cat /proc/cmdline root=UUID=295f571b-b731-4ebb-b752-60aadc80fc1b ro console=hvc0 crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M@128M ubuntu@tiselius:~$ ubuntu@tiselius:~$ dmesg | grep Reser [0.00] Reserving 4096MB of memory at 128MB for crashkernel (System RAM: 131072MB) [0.00] cma: Reserved 6560 MiB at 0x200e6200 ubuntu@tiselius:~$ root@tiselius:/home/ubuntu# echo 1 > /proc/sys/kernel/sysrq root@tiselius:/home/ubuntu# echo c > /proc/sysrq-trigger tiselius login: [ 150.167288] cloud-init[4529]: Cloud-init v. 19.1-1-gbaa47854-0ubuntu1~18.10.1 running 'modules:final' at Mon, 10 Jun 2019 19:53:40 +. Up 149.80 seconds. [ 150.167687] cloud-init[4529]: Cloud-init v. 19.1-1-gbaa47854-0ubuntu1~18.10.1 finished at Mon, 10 Jun 2019 19:53:40 +. Datasource DataSourceMAAS [http://10-245-64-0--21.maas-internal:5248/MAAS/metadata/]. Up 150.11 seconds [ 360.313029] kdump-tools[4915]: Stopping kdump-tools: * unloaded kdump kernel [ 376.552452] kdump-tools[10449]: Starting kdump-tools: * Creating symlink /var/lib/kdump/vmlinuz [ 376.553743] kdump-tools[10449]: * Creating symlink /var/lib/kdump/initrd.img [ 376.585085] kdump-tools[10449]: Modified cmdline:root=UUID=295f571b-b731-4ebb-b752-60aadc80fc1b ro console=hvc0 nr_cpus=1 systemd.unit=kdump-tools-dump.service irqpoll noirqdistrib nousb elfcorehdr=158784K [ 376.953223] kdump-tools[10449]: * loaded kdump kernel [ 398.517900] sysrq: SysRq : Trigger a crash [ 398.517952] Unable to handle kernel paging request for data at address 0x [ 398.518000] Faulting instruction address: 0xc082a3a8 [ 398.518071] Oops: Kernel access of bad area, sig: 11 [#1] [ 398.518115] LE SMP NR_CPUS=2048 NUMA PowerNV [ 398.518172] Modules linked in: joydev input_leds mac_hid vmx_crypto ofpart crct10dif_vpmsum ipmi_powernv ipmi_devintf at24 uio_pdrv_genirq ipmi_msghandler uio cmdlinepart powernv_flash mtd opal_prd ibmpowernv sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear ses enclosure scsi_transport_sas hid_generic usbhid hid ast i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm crc32c_vpmsum i40e aacraid drm_panel_orientation_quirks [ 398.518769] CPU: 0 PID: 10529 Comm: bash Kdump: loaded Not tainted 4.18.0-21-generic #22-Ubuntu [ 398.518881] NIP: c082a3a8 LR: c082b234 CTR: c082a380 [
Re: [Kernel-packages] [Bug 1832388] Re: [power9] [Cosmic] kernel panic while testing kdump
On Fri, Jun 14, 2019 at 11:20 AM Thadeu Lima de Souza Cascardo < 1832...@bugs.launchpad.net> wrote: > Manoj, > > How reproducible is this? Did you try multiple times? Did you only see > this on cosmic? > It reproduces in this form only on Cosmic, and I have been able to repro this a few times on this particular power9 (tesilius) > > I haven't been able to see this on an LPAR. This is certainly specific > to Power9, by the stack trace, as it involves the power9 idle driver. > However this issue seems to be isolated to this particular power9 system (tesilius) which is development grade system, and I was not able to repro this on lewis which is another development grade power9 system. I have done a few experiments and looks like the issue might be hardware related. I was sometimes running into CPU hard lockups on this system during my experiments. The production level power9s are currently being used by others, and IBM is shipping us our witherspoon power9 back next week after proc/fw upgrades. Also these two development systems are scheduled to be shipped back to IBM soon for upgrade to production hardware. I will retest this on the witherpoon that we will receive next week and report back if this can be reproduced there. If not I will close this as invalid. > Still, I haven't found anything on new kernels that seem to fix anything > like this, so it's possible newer releases are still affected. > > On the other hand, there doesn't seem to be anything here that looks > specific to kdump. Maybe the use of nr_cpus=1 or a kernel that is > kexec'ed. So, it would be interesting to try these as well. > > Finally, if you can reproduce it, we should coordinate, so we turn xmon > on and I can grab the system and take a look. > > Thanks. > Cascardo. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1832388 > > Title: > [power9] [Cosmic] kernel panic while testing kdump > > Status in The Ubuntu-power-systems project: > New > Status in linux package in Ubuntu: > Incomplete > Status in linux source package in Cosmic: > Incomplete > > Bug description: > I installed cosmic on power9 (boston) a non-nvme system, installed > initramfs-tools from -proposed and install kdump-tools. Triggered a > dump, but I got a kernel panic. This might be a kernel bug/regression. > > ubuntu@tiselius:~$ uname -a > Linux tiselius 4.18.0-21-generic #22-Ubuntu SMP Wed May 15 13:12:45 UTC > 2019 ppc64le ppc64le ppc64le GNU/Linux > ubuntu@tiselius:~$ > > ubuntu@tiselius:~$ apt policy initramfs-tools > initramfs-tools: > Installed: 0.131ubuntu15.2 > Candidate: 0.131ubuntu15.2 > Version table: >*** 0.131ubuntu15.2 500 > 500 http://ports.ubuntu.com/ubuntu-ports cosmic-proposed/main > ppc64el Packages > ubuntu@tiselius:~$ > > ubuntu@tiselius:~$ apt policy kdump-tools > kdump-tools: > Installed: 1:1.6.5-1ubuntu1~18.10.1 > Candidate: 1:1.6.5-1ubuntu1~18.10.1 > Version table: >*** 1:1.6.5-1ubuntu1~18.10.1 500 > 500 http://ports.ubuntu.com/ubuntu-ports cosmic-updates/main > ppc64el Packages > 100 /var/lib/dpkg/status >1:1.6.4-2ubuntu1 500 > 500 http://ports.ubuntu.com/ubuntu-ports cosmic/main ppc64el > Packages > ubuntu@tiselius:~$ > > ubuntu@tiselius:~$ sudo kdump-config show > DUMP_MODE:kdump > USE_KDUMP:1 > KDUMP_SYSCTL: kernel.panic_on_oops=1 > KDUMP_COREDIR:/var/crash > crashkernel addr: > /var/lib/kdump/vmlinuz: symbolic link to > /boot/vmlinux-4.18.0-21-generic > kdump initrd: > /var/lib/kdump/initrd.img: symbolic link to > /var/lib/kdump/initrd.img-4.18.0-21-generic > current state:ready to kdump > > kexec command: > /sbin/kexec -p > --command-line="root=UUID=295f571b-b731-4ebb-b752-60aadc80fc1b ro > console=hvc0 nr_cpus=1 systemd.unit=kdump-tools-dump.service irqpoll > noirqdistrib nousb" --initrd=/var/lib/kdump/initrd.img > /var/lib/kdump/vmlinuz > ubuntu@tiselius:~$ > > ubuntu@tiselius:~$ cat /proc/cmdline > root=UUID=295f571b-b731-4ebb-b752-60aadc80fc1b ro console=hvc0 > crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M@128M > ubuntu@tiselius:~$ > > ubuntu@tiselius:~$ dmesg | grep Reser > [0.00] Reserving 4096MB of memory at 128MB for crashkernel > (System RAM: 131072MB) > [0.00] cma: Reserved 6560 MiB at 0x200e6200 > ubuntu@tiselius:~$ > > root@tiselius:/home/ubuntu# echo 1 > /proc/sys/kernel/sysrq > root@tiselius:/home/ubuntu# echo c > /proc/sysrq-trigger > > tiselius login: [ 150.167288] cloud-init[4529]: Cloud-init v. > 19.1-1-gbaa47854-0ubuntu1~18.10.1 running 'modules:final' at Mon, 10 Jun > 2019 19:53:40 +. Up 149.80 seconds. > [ 150.167687] cloud-init[4529]: Cloud-init v. > 19.1-1-gbaa47854-0ubuntu1~18.10.1 finished at Mon, 10 Jun 2019 19:53:40 > +. Datasource DataSourceMAAS [ >
[Kernel-packages] [Bug 1827162] Re: "vio vio: uevent: failed to send synthetic uevent" errors on ppc64el
Based on our analysis and comments from IBM confirming that this is an expected behavior, I am marking this as wont fix. ** Changed in: ubuntu-power-systems Status: Incomplete => Won't Fix ** Changed in: linux (Ubuntu) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1827162 Title: "vio vio: uevent: failed to send synthetic uevent" errors on ppc64el Status in The Ubuntu-power-systems project: Won't Fix Status in linux package in Ubuntu: Won't Fix Bug description: This bug is created from bug LP #1766201 which reported multiple errors in the kernel log on ppc64el. This bug is for tracking the issue of the error message "vio vio: uevent: failed to send synthetic uevent" (see the original bug, and https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766201/comments/12 for more info) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1827162/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
