[Kernel-packages] [Bug 1514711] Re: Installer doesn't include ast GPU driver for OpenPower machines
@henrix: I'll need some help with testing this; it's not like we can just boot into the new kernel directlyb. We'll chase this up with #ubuntu-devel. -- 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/1514711 Title: Installer doesn't include ast GPU driver for OpenPower machines Status in linux package in Ubuntu: Fix Committed Status in linux source package in Vivid: Fix Committed Status in linux source package in Wily: Fix Committed Status in linux source package in Xenial: Fix Committed Bug description: When booting the Ubuntu 14.03.4 installer on an OpenPower machine with a VGA monitor attached, we see no output - the only installer output is over the physical UART (or SOL session). Petitboot is displayed over both VGA and UART, but not the installer UI. It seems like the ast GPU driver isn't present on the installer image (but is present for the non-installer kernels), which is required for graphics output on these machines. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1514711/+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 1514711] Re: Installer doesn't include ast GPU driver for OpenPower machines
Any news on this one? It's preventing folks from installing on OpenPOWER machines if they're relying on VGA. -- 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/1514711 Title: Installer doesn't include ast GPU driver for OpenPower machines Status in linux package in Ubuntu: Triaged Bug description: When booting the Ubuntu 14.03.4 installer on an OpenPower machine with a VGA monitor attached, we see no output - the only installer output is over the physical UART (or SOL session). Petitboot is displayed over both VGA and UART, but not the installer UI. It seems like the ast GPU driver isn't present on the installer image (but is present for the non-installer kernels), which is required for graphics output on these machines. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1514711/+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 1514711] Re: Installer doesn't include ast GPU driver for OpenPower machines
hi Tim, Yep, that looks like it'll sort it. Is there any reference around for building an installer image with this? -- 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/1514711 Title: Installer doesn't include ast GPU driver for OpenPower machines Status in linux package in Ubuntu: In Progress Status in linux source package in Vivid: In Progress Status in linux source package in Wily: In Progress Status in linux source package in Xenial: In Progress Bug description: When booting the Ubuntu 14.03.4 installer on an OpenPower machine with a VGA monitor attached, we see no output - the only installer output is over the physical UART (or SOL session). Petitboot is displayed over both VGA and UART, but not the installer UI. It seems like the ast GPU driver isn't present on the installer image (but is present for the non-installer kernels), which is required for graphics output on these machines. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1514711/+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 1439562] Re: backport request: include support for OpenPower hardware
Hi Chris, Thanks for taking this on for a utopic backport. Instead of using that ubuntu/utopic branch in the openpower tree, I'd suggest using the upstream commits that we have listed in this bug (and Tim has applied); that way, you'll be getting the latest changes, and have less merging to do later. We also have some patches that are on their way upstream (mentioned above, making their way to vivid as a SRU). Those are at: http://patchwork.ozlabs.org/bundle/jk/prd/ For config changes, we'll want: CONFIG_IPMI_POWERNV CONFIG_MTD_POWERNV_FLASH CONFIG_OPAL_PRD -- 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/1439562 Title: backport request: include support for OpenPower hardware Status in linux package in Ubuntu: Fix Released Status in linux source package in Utopic: New Status in linux source package in Vivid: Fix Released Bug description: [Impact] This is a HWE SRU for OpenPower support in 3.16. [Fix] upstream commits: 4c3b2168 a4bcbe6a 529d235a \ 08135139 c1c3a526 b921e902 \ 3bf57561 e8a51e1b 5590f319 [Test Case] Ensure kernel boots on specific OpenPower hardware. -- We've prepared a series of patches (ported to Ubuntu-3.19.0-11.11), which add OpenPower support to the Ubuntu kernel. The changes are available in the ubuntu/vivid branch of: https://github.com/open-power/linux.git (or I can attach them separately). Changelogs are as follows: commit 2f0190bd43764559b250a5bd11aca050f909aa21 Author: Benjamin Herrenschmidt Date: Fri Nov 14 16:13:50 2014 +1100 powerpc/powernv: Support OPAL requested heartbeat If OPAL requests it, call it back via opal_poll_events() at a regular interval. Some versions of OPAL on some machines require this to operate some internal timeouts properly. Signed-off-by: Benjamin Herrenschmidt Backport notes: cherry-picked from mpe-next, 3bf57561d4dbd36ba45ce05656b0469bfdcc7ef2 minor conflicts resolved Signed-off-by: Jeremy Kerr commit e1c89541e7163494ad091f3c2622649d91ac7597 Author: Benjamin Herrenschmidt Date: Mon Feb 16 14:59:08 2015 +1100 device: Add dev_of_node() accessor Suggested by Arnd Bergmann, this gives a practical accessor for the of_node field of struct device while instructing the compiler that it will be NULL if CONFIG_OF is not set. Signed-off-by: Benjamin Herrenschmidt Acked-by: Rob Herring Backport notes: Submission to LKML at: https://patchwork.kernel.org/patch/5831161/ Signed-off-by: Jeremy Kerr commit 2c242b30756f77528516a4e9e986818ac4e90490 Author: Benjamin Herrenschmidt Date: Wed Feb 18 11:25:18 2015 +1100 drivers/core/of: Add symlink to device-tree from devices with an OF node So I've been annoyed lately with having a bunch of devices such as i2c eeproms (for use by VPDs, server world !) and other bits and pieces that I want to be able to identify from userspace, and possibly provide additional data about from FW. Basically, it boils down to correlating the sysfs device with the OF tree device node, so that user space can use device-tree info such as additional "location" or "label" (or whatever else we can come up with) propreties to identify a given device, or get some attributes of use about it, etc... Now, so far, we've done that in some subsystem in a fairly ad-hoc basis using "devspec" properties. For example, PCI creates them if it can correlate the probed device with a DT node. Some powerpc specific busses do that too. However, i2c doesn't and it would be nice to have something more generic since technically any device can have a corresponding device tree node. This patch adds an "of_node" symlink to devices that have a non-NULL dev->of_node pointer, the patch is pretty trivial and seems to work just fine for me. Signed-off-by: Benjamin Herrenschmidt Acked-by: Rob Herring Backport notes: Submission to LKML at: https://patchwork.kernel.org/patch/5842241/ Signed-off-by: Jeremy Kerr commit 1d9d9bdad2553f39de92eba40f8663eb45819e8c Author: Michael Ellerman Date: Sat Mar 28 21:35:16 2015 +1100 powerpc: Add a proper syscall for switching endianness We currently have a "special" syscall for switching endianness. This is syscall number 0x1ebe, which is handled explicitly in the 64-bit syscall exception entry. That has a few problems, firstly the syscall number is outside of the usual range, which confuses various tools. For example strace doesn't recognise the syscall at all. Secondly it's handled explicitly as a sp
[Kernel-packages] [Bug 1439562] Re: backport request: include support for OpenPower hardware
Hi Chris, Yes, 6a11e5c6 adds the IPMI driver. Is that not already in the vivid tree? The PRD and MTD changes are headed upstream, I was just sending to you for an indication of what to expect. -- 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/1439562 Title: backport request: include support for OpenPower hardware Status in linux package in Ubuntu: Fix Released Status in linux source package in Utopic: New Status in linux source package in Vivid: Fix Released Bug description: [Impact] This is a HWE SRU for OpenPower support in 3.16. [Fix] upstream commits: 4c3b2168 a4bcbe6a 529d235a \ 08135139 c1c3a526 b921e902 \ 3bf57561 e8a51e1b 5590f319 [Test Case] Ensure kernel boots on specific OpenPower hardware. -- We've prepared a series of patches (ported to Ubuntu-3.19.0-11.11), which add OpenPower support to the Ubuntu kernel. The changes are available in the ubuntu/vivid branch of: https://github.com/open-power/linux.git (or I can attach them separately). Changelogs are as follows: commit 2f0190bd43764559b250a5bd11aca050f909aa21 Author: Benjamin Herrenschmidt Date: Fri Nov 14 16:13:50 2014 +1100 powerpc/powernv: Support OPAL requested heartbeat If OPAL requests it, call it back via opal_poll_events() at a regular interval. Some versions of OPAL on some machines require this to operate some internal timeouts properly. Signed-off-by: Benjamin Herrenschmidt Backport notes: cherry-picked from mpe-next, 3bf57561d4dbd36ba45ce05656b0469bfdcc7ef2 minor conflicts resolved Signed-off-by: Jeremy Kerr commit e1c89541e7163494ad091f3c2622649d91ac7597 Author: Benjamin Herrenschmidt Date: Mon Feb 16 14:59:08 2015 +1100 device: Add dev_of_node() accessor Suggested by Arnd Bergmann, this gives a practical accessor for the of_node field of struct device while instructing the compiler that it will be NULL if CONFIG_OF is not set. Signed-off-by: Benjamin Herrenschmidt Acked-by: Rob Herring Backport notes: Submission to LKML at: https://patchwork.kernel.org/patch/5831161/ Signed-off-by: Jeremy Kerr commit 2c242b30756f77528516a4e9e986818ac4e90490 Author: Benjamin Herrenschmidt Date: Wed Feb 18 11:25:18 2015 +1100 drivers/core/of: Add symlink to device-tree from devices with an OF node So I've been annoyed lately with having a bunch of devices such as i2c eeproms (for use by VPDs, server world !) and other bits and pieces that I want to be able to identify from userspace, and possibly provide additional data about from FW. Basically, it boils down to correlating the sysfs device with the OF tree device node, so that user space can use device-tree info such as additional "location" or "label" (or whatever else we can come up with) propreties to identify a given device, or get some attributes of use about it, etc... Now, so far, we've done that in some subsystem in a fairly ad-hoc basis using "devspec" properties. For example, PCI creates them if it can correlate the probed device with a DT node. Some powerpc specific busses do that too. However, i2c doesn't and it would be nice to have something more generic since technically any device can have a corresponding device tree node. This patch adds an "of_node" symlink to devices that have a non-NULL dev->of_node pointer, the patch is pretty trivial and seems to work just fine for me. Signed-off-by: Benjamin Herrenschmidt Acked-by: Rob Herring Backport notes: Submission to LKML at: https://patchwork.kernel.org/patch/5842241/ Signed-off-by: Jeremy Kerr commit 1d9d9bdad2553f39de92eba40f8663eb45819e8c Author: Michael Ellerman Date: Sat Mar 28 21:35:16 2015 +1100 powerpc: Add a proper syscall for switching endianness We currently have a "special" syscall for switching endianness. This is syscall number 0x1ebe, which is handled explicitly in the 64-bit syscall exception entry. That has a few problems, firstly the syscall number is outside of the usual range, which confuses various tools. For example strace doesn't recognise the syscall at all. Secondly it's handled explicitly as a special case in the syscall exception entry, which is complicated enough without it. As a first step toward removing the special syscall, we need to add a regular syscall that implements the same functionality. The logic is simple, it simply toggles the MSR_LE bit in the userspace MSR. This is the same as the special syscall, with the caveat that the special s
[Kernel-packages] [Bug 1439562] [NEW] backport request: include support for OpenPower hardware
Public bug reported: We've prepared a series of patches (ported to Ubuntu-3.19.0-11.11), which add OpenPower support to the Ubuntu kernel. The changes are available in the ubuntu/vivid branch of: https://github.com/open-power/linux.git (or I can attach them separately). Changelogs are as follows: commit 2f0190bd43764559b250a5bd11aca050f909aa21 Author: Benjamin Herrenschmidt Date: Fri Nov 14 16:13:50 2014 +1100 powerpc/powernv: Support OPAL requested heartbeat If OPAL requests it, call it back via opal_poll_events() at a regular interval. Some versions of OPAL on some machines require this to operate some internal timeouts properly. Signed-off-by: Benjamin Herrenschmidt Backport notes: cherry-picked from mpe-next, 3bf57561d4dbd36ba45ce05656b0469bfdcc7ef2 minor conflicts resolved Signed-off-by: Jeremy Kerr commit e1c89541e7163494ad091f3c2622649d91ac7597 Author: Benjamin Herrenschmidt Date: Mon Feb 16 14:59:08 2015 +1100 device: Add dev_of_node() accessor Suggested by Arnd Bergmann, this gives a practical accessor for the of_node field of struct device while instructing the compiler that it will be NULL if CONFIG_OF is not set. Signed-off-by: Benjamin Herrenschmidt Acked-by: Rob Herring Backport notes: Submission to LKML at: https://patchwork.kernel.org/patch/5831161/ Signed-off-by: Jeremy Kerr commit 2c242b30756f77528516a4e9e986818ac4e90490 Author: Benjamin Herrenschmidt Date: Wed Feb 18 11:25:18 2015 +1100 drivers/core/of: Add symlink to device-tree from devices with an OF node So I've been annoyed lately with having a bunch of devices such as i2c eeproms (for use by VPDs, server world !) and other bits and pieces that I want to be able to identify from userspace, and possibly provide additional data about from FW. Basically, it boils down to correlating the sysfs device with the OF tree device node, so that user space can use device-tree info such as additional "location" or "label" (or whatever else we can come up with) propreties to identify a given device, or get some attributes of use about it, etc... Now, so far, we've done that in some subsystem in a fairly ad-hoc basis using "devspec" properties. For example, PCI creates them if it can correlate the probed device with a DT node. Some powerpc specific busses do that too. However, i2c doesn't and it would be nice to have something more generic since technically any device can have a corresponding device tree node. This patch adds an "of_node" symlink to devices that have a non-NULL dev->of_node pointer, the patch is pretty trivial and seems to work just fine for me. Signed-off-by: Benjamin Herrenschmidt Acked-by: Rob Herring Backport notes: Submission to LKML at: https://patchwork.kernel.org/patch/5842241/ Signed-off-by: Jeremy Kerr commit 1d9d9bdad2553f39de92eba40f8663eb45819e8c Author: Michael Ellerman Date: Sat Mar 28 21:35:16 2015 +1100 powerpc: Add a proper syscall for switching endianness We currently have a "special" syscall for switching endianness. This is syscall number 0x1ebe, which is handled explicitly in the 64-bit syscall exception entry. That has a few problems, firstly the syscall number is outside of the usual range, which confuses various tools. For example strace doesn't recognise the syscall at all. Secondly it's handled explicitly as a special case in the syscall exception entry, which is complicated enough without it. As a first step toward removing the special syscall, we need to add a regular syscall that implements the same functionality. The logic is simple, it simply toggles the MSR_LE bit in the userspace MSR. This is the same as the special syscall, with the caveat that the special syscall clobbers fewer registers. This version clobbers r9-r12, XER, CTR, and CR0-1,5-7. Signed-off-by: Michael Ellerman Backport notes: Cherry-picked (with conflicts resolved) from mpe-next, commit 529d235a0e190ded1d21ccc80a73e625ebcad09b Signed-off-by: Jeremy Kerr commit 352598493e72d80fcf136b5c30add7f9dd32b30a Author: Cyril Bur Date: Tue Feb 17 18:27:34 2015 +1100 powerpc/powernv: Add interfaces for flash device access This change adds the OPAL interface definitions to allow Linux to read, write and erase from system flash devices. We register platform devices for the flash devices exported by firmware. We clash with the existing opal_flash_init function, which is really for the FSP flash update functionality, so we rename that initcall to opal_flash_update_init(). A future change will add an mtd driver that uses this in
[Kernel-packages] [Bug 1439562] Re: backport request: include support for OpenPower hardware
Also: these changes add a config var: CONFIG_MTD_POWERNV_FLASH, for the
presence of the powernv mtd driver.
Will the new "ipmi_powernv" and "powernv_flash" modules appear in the
linux-image package (rather than linux-image extras)?
--
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/1439562
Title:
backport request: include support for OpenPower hardware
Status in linux package in Ubuntu:
Confirmed
Bug description:
We've prepared a series of patches (ported to Ubuntu-3.19.0-11.11),
which add OpenPower support to the Ubuntu kernel.
The changes are available in the ubuntu/vivid branch of:
https://github.com/open-power/linux.git
(or I can attach them separately).
Changelogs are as follows:
commit 2f0190bd43764559b250a5bd11aca050f909aa21
Author: Benjamin Herrenschmidt
Date: Fri Nov 14 16:13:50 2014 +1100
powerpc/powernv: Support OPAL requested heartbeat
If OPAL requests it, call it back via opal_poll_events() at a
regular interval. Some versions of OPAL on some machines require
this to operate some internal timeouts properly.
Signed-off-by: Benjamin Herrenschmidt
Backport notes:
cherry-picked from mpe-next, 3bf57561d4dbd36ba45ce05656b0469bfdcc7ef2
minor conflicts resolved
Signed-off-by: Jeremy Kerr
commit e1c89541e7163494ad091f3c2622649d91ac7597
Author: Benjamin Herrenschmidt
Date: Mon Feb 16 14:59:08 2015 +1100
device: Add dev_of_node() accessor
Suggested by Arnd Bergmann, this gives a practical accessor for
the of_node field of struct device while instructing the compiler
that it will be NULL if CONFIG_OF is not set.
Signed-off-by: Benjamin Herrenschmidt
Acked-by: Rob Herring
Backport notes:
Submission to LKML at: https://patchwork.kernel.org/patch/5831161/
Signed-off-by: Jeremy Kerr
commit 2c242b30756f77528516a4e9e986818ac4e90490
Author: Benjamin Herrenschmidt
Date: Wed Feb 18 11:25:18 2015 +1100
drivers/core/of: Add symlink to device-tree from devices with an OF node
So I've been annoyed lately with having a bunch of devices such as i2c
eeproms (for use by VPDs, server world !) and other bits and pieces that
I want to be able to identify from userspace, and possibly provide
additional data about from FW.
Basically, it boils down to correlating the sysfs device with the OF
tree device node, so that user space can use device-tree info such as
additional "location" or "label" (or whatever else we can come up with)
propreties to identify a given device, or get some attributes of use
about it, etc...
Now, so far, we've done that in some subsystem in a fairly ad-hoc basis
using "devspec" properties. For example, PCI creates them if it can
correlate the probed device with a DT node. Some powerpc specific busses
do that too.
However, i2c doesn't and it would be nice to have something more generic
since technically any device can have a corresponding device tree node.
This patch adds an "of_node" symlink to devices that have a non-NULL
dev->of_node pointer, the patch is pretty trivial and seems to work just
fine for me.
Signed-off-by: Benjamin Herrenschmidt
Acked-by: Rob Herring
Backport notes:
Submission to LKML at: https://patchwork.kernel.org/patch/5842241/
Signed-off-by: Jeremy Kerr
commit 1d9d9bdad2553f39de92eba40f8663eb45819e8c
Author: Michael Ellerman
Date: Sat Mar 28 21:35:16 2015 +1100
powerpc: Add a proper syscall for switching endianness
We currently have a "special" syscall for switching endianness. This is
syscall number 0x1ebe, which is handled explicitly in the 64-bit syscall
exception entry.
That has a few problems, firstly the syscall number is outside of the
usual range, which confuses various tools. For example strace doesn't
recognise the syscall at all.
Secondly it's handled explicitly as a special case in the syscall
exception entry, which is complicated enough without it.
As a first step toward removing the special syscall, we need to add a
regular syscall that implements the same functionality.
The logic is simple, it simply toggles the MSR_LE bit in the userspace
MSR. This is the same as the special syscall, with the caveat that the
special syscall clobbers fewer registers.
This version clobbers r9-r12, XER, CTR, and CR0-1,5-7.
Signed-off-by: Michael Ellerman
Backport notes:
Cherry-picked (with confli
[Kernel-packages] [Bug 1439562] Re: backport request: include support for OpenPower hardware
Tim - yes, they're both related to OpenPower hardware, and aren't required for guest VMs. Sounds fine then. -- 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/1439562 Title: backport request: include support for OpenPower hardware Status in linux package in Ubuntu: Triaged Bug description: We've prepared a series of patches (ported to Ubuntu-3.19.0-11.11), which add OpenPower support to the Ubuntu kernel. The changes are available in the ubuntu/vivid branch of: https://github.com/open-power/linux.git (or I can attach them separately). Changelogs are as follows: commit 2f0190bd43764559b250a5bd11aca050f909aa21 Author: Benjamin Herrenschmidt Date: Fri Nov 14 16:13:50 2014 +1100 powerpc/powernv: Support OPAL requested heartbeat If OPAL requests it, call it back via opal_poll_events() at a regular interval. Some versions of OPAL on some machines require this to operate some internal timeouts properly. Signed-off-by: Benjamin Herrenschmidt Backport notes: cherry-picked from mpe-next, 3bf57561d4dbd36ba45ce05656b0469bfdcc7ef2 minor conflicts resolved Signed-off-by: Jeremy Kerr commit e1c89541e7163494ad091f3c2622649d91ac7597 Author: Benjamin Herrenschmidt Date: Mon Feb 16 14:59:08 2015 +1100 device: Add dev_of_node() accessor Suggested by Arnd Bergmann, this gives a practical accessor for the of_node field of struct device while instructing the compiler that it will be NULL if CONFIG_OF is not set. Signed-off-by: Benjamin Herrenschmidt Acked-by: Rob Herring Backport notes: Submission to LKML at: https://patchwork.kernel.org/patch/5831161/ Signed-off-by: Jeremy Kerr commit 2c242b30756f77528516a4e9e986818ac4e90490 Author: Benjamin Herrenschmidt Date: Wed Feb 18 11:25:18 2015 +1100 drivers/core/of: Add symlink to device-tree from devices with an OF node So I've been annoyed lately with having a bunch of devices such as i2c eeproms (for use by VPDs, server world !) and other bits and pieces that I want to be able to identify from userspace, and possibly provide additional data about from FW. Basically, it boils down to correlating the sysfs device with the OF tree device node, so that user space can use device-tree info such as additional "location" or "label" (or whatever else we can come up with) propreties to identify a given device, or get some attributes of use about it, etc... Now, so far, we've done that in some subsystem in a fairly ad-hoc basis using "devspec" properties. For example, PCI creates them if it can correlate the probed device with a DT node. Some powerpc specific busses do that too. However, i2c doesn't and it would be nice to have something more generic since technically any device can have a corresponding device tree node. This patch adds an "of_node" symlink to devices that have a non-NULL dev->of_node pointer, the patch is pretty trivial and seems to work just fine for me. Signed-off-by: Benjamin Herrenschmidt Acked-by: Rob Herring Backport notes: Submission to LKML at: https://patchwork.kernel.org/patch/5842241/ Signed-off-by: Jeremy Kerr commit 1d9d9bdad2553f39de92eba40f8663eb45819e8c Author: Michael Ellerman Date: Sat Mar 28 21:35:16 2015 +1100 powerpc: Add a proper syscall for switching endianness We currently have a "special" syscall for switching endianness. This is syscall number 0x1ebe, which is handled explicitly in the 64-bit syscall exception entry. That has a few problems, firstly the syscall number is outside of the usual range, which confuses various tools. For example strace doesn't recognise the syscall at all. Secondly it's handled explicitly as a special case in the syscall exception entry, which is complicated enough without it. As a first step toward removing the special syscall, we need to add a regular syscall that implements the same functionality. The logic is simple, it simply toggles the MSR_LE bit in the userspace MSR. This is the same as the special syscall, with the caveat that the special syscall clobbers fewer registers. This version clobbers r9-r12, XER, CTR, and CR0-1,5-7. Signed-off-by: Michael Ellerman Backport notes: Cherry-picked (with conflicts resolved) from mpe-next, commit 529d235a0e190ded1d21ccc80a73e625ebcad09b Signed-off-by: Jeremy Kerr commit 352598493
[Kernel-packages] [Bug 1439562] Re: backport request: include support for OpenPower hardware
OK, I'll keep this bug updated as the patches are merged. -- 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/1439562 Title: backport request: include support for OpenPower hardware Status in linux package in Ubuntu: In Progress Status in linux source package in Vivid: In Progress Bug description: We've prepared a series of patches (ported to Ubuntu-3.19.0-11.11), which add OpenPower support to the Ubuntu kernel. The changes are available in the ubuntu/vivid branch of: https://github.com/open-power/linux.git (or I can attach them separately). Changelogs are as follows: commit 2f0190bd43764559b250a5bd11aca050f909aa21 Author: Benjamin Herrenschmidt Date: Fri Nov 14 16:13:50 2014 +1100 powerpc/powernv: Support OPAL requested heartbeat If OPAL requests it, call it back via opal_poll_events() at a regular interval. Some versions of OPAL on some machines require this to operate some internal timeouts properly. Signed-off-by: Benjamin Herrenschmidt Backport notes: cherry-picked from mpe-next, 3bf57561d4dbd36ba45ce05656b0469bfdcc7ef2 minor conflicts resolved Signed-off-by: Jeremy Kerr commit e1c89541e7163494ad091f3c2622649d91ac7597 Author: Benjamin Herrenschmidt Date: Mon Feb 16 14:59:08 2015 +1100 device: Add dev_of_node() accessor Suggested by Arnd Bergmann, this gives a practical accessor for the of_node field of struct device while instructing the compiler that it will be NULL if CONFIG_OF is not set. Signed-off-by: Benjamin Herrenschmidt Acked-by: Rob Herring Backport notes: Submission to LKML at: https://patchwork.kernel.org/patch/5831161/ Signed-off-by: Jeremy Kerr commit 2c242b30756f77528516a4e9e986818ac4e90490 Author: Benjamin Herrenschmidt Date: Wed Feb 18 11:25:18 2015 +1100 drivers/core/of: Add symlink to device-tree from devices with an OF node So I've been annoyed lately with having a bunch of devices such as i2c eeproms (for use by VPDs, server world !) and other bits and pieces that I want to be able to identify from userspace, and possibly provide additional data about from FW. Basically, it boils down to correlating the sysfs device with the OF tree device node, so that user space can use device-tree info such as additional "location" or "label" (or whatever else we can come up with) propreties to identify a given device, or get some attributes of use about it, etc... Now, so far, we've done that in some subsystem in a fairly ad-hoc basis using "devspec" properties. For example, PCI creates them if it can correlate the probed device with a DT node. Some powerpc specific busses do that too. However, i2c doesn't and it would be nice to have something more generic since technically any device can have a corresponding device tree node. This patch adds an "of_node" symlink to devices that have a non-NULL dev->of_node pointer, the patch is pretty trivial and seems to work just fine for me. Signed-off-by: Benjamin Herrenschmidt Acked-by: Rob Herring Backport notes: Submission to LKML at: https://patchwork.kernel.org/patch/5842241/ Signed-off-by: Jeremy Kerr commit 1d9d9bdad2553f39de92eba40f8663eb45819e8c Author: Michael Ellerman Date: Sat Mar 28 21:35:16 2015 +1100 powerpc: Add a proper syscall for switching endianness We currently have a "special" syscall for switching endianness. This is syscall number 0x1ebe, which is handled explicitly in the 64-bit syscall exception entry. That has a few problems, firstly the syscall number is outside of the usual range, which confuses various tools. For example strace doesn't recognise the syscall at all. Secondly it's handled explicitly as a special case in the syscall exception entry, which is complicated enough without it. As a first step toward removing the special syscall, we need to add a regular syscall that implements the same functionality. The logic is simple, it simply toggles the MSR_LE bit in the userspace MSR. This is the same as the special syscall, with the caveat that the special syscall clobbers fewer registers. This version clobbers r9-r12, XER, CTR, and CR0-1,5-7. Signed-off-by: Michael Ellerman Backport notes: Cherry-picked (with conflicts resolved) from mpe-next, commit 529d235a0e190ded1d21ccc80a73e625ebcad09b Signed-off-by: Jeremy Kerr commit 35259849
[Kernel-packages] [Bug 1439562] Re: backport request: include support for OpenPower hardware
We've had a few patches merged to linux-next: 6f4b0f5 drivers/sbus/char/envctrl.c: ignore orderly_poweroff return value -> merged to linux-next/master: dc4f016cb8b67128c42f165802794f0b6d70405c 53cffb5 kernel/reboot.c: add orderly_reboot for graceful reboot -> merged to linux-next/master: c162cd23253587741207fcb08c20c56922dd5fdb 63df164 powerpc/powernv: reboot when requested by firmware -> merged to linux-next/master: 62a68d4f51accd3ffa3f38d4a85f41b031ff13b7 Leaving the following pending patches: 2f0190b powerpc/powernv: Support OPAL requested heartbeat e1c8954 device: Add dev_of_node() accessor 2c242b3 drivers/core/of: Add symlink to device-tree from devices with an OF node 1d9d9bd powerpc: Add a proper syscall for switching endianness 3525984 powerpc/powernv: Add interfaces for flash device access 1acd5dd drivers/mtd: add powernv flash MTD abstraction driver 37889e2 powerpc/powernv: Add OPAL message notifier unregister function 744b976 powerpc/powernv: Add OPAL soft-poweroff routine 8589e12 powerpc/powernv: Add opal-prd channel -- 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/1439562 Title: backport request: include support for OpenPower hardware Status in linux package in Ubuntu: In Progress Status in linux source package in Vivid: In Progress Bug description: We've prepared a series of patches (ported to Ubuntu-3.19.0-11.11), which add OpenPower support to the Ubuntu kernel. The changes are available in the ubuntu/vivid branch of: https://github.com/open-power/linux.git (or I can attach them separately). Changelogs are as follows: commit 2f0190bd43764559b250a5bd11aca050f909aa21 Author: Benjamin Herrenschmidt Date: Fri Nov 14 16:13:50 2014 +1100 powerpc/powernv: Support OPAL requested heartbeat If OPAL requests it, call it back via opal_poll_events() at a regular interval. Some versions of OPAL on some machines require this to operate some internal timeouts properly. Signed-off-by: Benjamin Herrenschmidt Backport notes: cherry-picked from mpe-next, 3bf57561d4dbd36ba45ce05656b0469bfdcc7ef2 minor conflicts resolved Signed-off-by: Jeremy Kerr commit e1c89541e7163494ad091f3c2622649d91ac7597 Author: Benjamin Herrenschmidt Date: Mon Feb 16 14:59:08 2015 +1100 device: Add dev_of_node() accessor Suggested by Arnd Bergmann, this gives a practical accessor for the of_node field of struct device while instructing the compiler that it will be NULL if CONFIG_OF is not set. Signed-off-by: Benjamin Herrenschmidt Acked-by: Rob Herring Backport notes: Submission to LKML at: https://patchwork.kernel.org/patch/5831161/ Signed-off-by: Jeremy Kerr commit 2c242b30756f77528516a4e9e986818ac4e90490 Author: Benjamin Herrenschmidt Date: Wed Feb 18 11:25:18 2015 +1100 drivers/core/of: Add symlink to device-tree from devices with an OF node So I've been annoyed lately with having a bunch of devices such as i2c eeproms (for use by VPDs, server world !) and other bits and pieces that I want to be able to identify from userspace, and possibly provide additional data about from FW. Basically, it boils down to correlating the sysfs device with the OF tree device node, so that user space can use device-tree info such as additional "location" or "label" (or whatever else we can come up with) propreties to identify a given device, or get some attributes of use about it, etc... Now, so far, we've done that in some subsystem in a fairly ad-hoc basis using "devspec" properties. For example, PCI creates them if it can correlate the probed device with a DT node. Some powerpc specific busses do that too. However, i2c doesn't and it would be nice to have something more generic since technically any device can have a corresponding device tree node. This patch adds an "of_node" symlink to devices that have a non-NULL dev->of_node pointer, the patch is pretty trivial and seems to work just fine for me. Signed-off-by: Benjamin Herrenschmidt Acked-by: Rob Herring Backport notes: Submission to LKML at: https://patchwork.kernel.org/patch/5842241/ Signed-off-by: Jeremy Kerr commit 1d9d9bdad2553f39de92eba40f8663eb45819e8c Author: Michael Ellerman Date: Sat Mar 28 21:35:16 2015 +1100 powerpc: Add a proper syscall for switching endianness We currently have a "special" syscall for switching endianness. This is syscall number 0x1ebe, which is handled explicitly in the 64-bit syscall exception entry.
[Kernel-packages] [Bug 1439562] Re: backport request: include support for OpenPower hardware
Also: 744b976 powerpc/powernv: Add OPAL soft-poweroff routine -> in linus/master: 7f43e71e8c538356efd5b33a183e6d9ace4739a5 - this is a prerequisite for: 63df164 powerpc/powernv: reboot when requested by firmware -- 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/1439562 Title: backport request: include support for OpenPower hardware Status in linux package in Ubuntu: In Progress Status in linux source package in Vivid: In Progress Bug description: We've prepared a series of patches (ported to Ubuntu-3.19.0-11.11), which add OpenPower support to the Ubuntu kernel. The changes are available in the ubuntu/vivid branch of: https://github.com/open-power/linux.git (or I can attach them separately). Changelogs are as follows: commit 2f0190bd43764559b250a5bd11aca050f909aa21 Author: Benjamin Herrenschmidt Date: Fri Nov 14 16:13:50 2014 +1100 powerpc/powernv: Support OPAL requested heartbeat If OPAL requests it, call it back via opal_poll_events() at a regular interval. Some versions of OPAL on some machines require this to operate some internal timeouts properly. Signed-off-by: Benjamin Herrenschmidt Backport notes: cherry-picked from mpe-next, 3bf57561d4dbd36ba45ce05656b0469bfdcc7ef2 minor conflicts resolved Signed-off-by: Jeremy Kerr commit e1c89541e7163494ad091f3c2622649d91ac7597 Author: Benjamin Herrenschmidt Date: Mon Feb 16 14:59:08 2015 +1100 device: Add dev_of_node() accessor Suggested by Arnd Bergmann, this gives a practical accessor for the of_node field of struct device while instructing the compiler that it will be NULL if CONFIG_OF is not set. Signed-off-by: Benjamin Herrenschmidt Acked-by: Rob Herring Backport notes: Submission to LKML at: https://patchwork.kernel.org/patch/5831161/ Signed-off-by: Jeremy Kerr commit 2c242b30756f77528516a4e9e986818ac4e90490 Author: Benjamin Herrenschmidt Date: Wed Feb 18 11:25:18 2015 +1100 drivers/core/of: Add symlink to device-tree from devices with an OF node So I've been annoyed lately with having a bunch of devices such as i2c eeproms (for use by VPDs, server world !) and other bits and pieces that I want to be able to identify from userspace, and possibly provide additional data about from FW. Basically, it boils down to correlating the sysfs device with the OF tree device node, so that user space can use device-tree info such as additional "location" or "label" (or whatever else we can come up with) propreties to identify a given device, or get some attributes of use about it, etc... Now, so far, we've done that in some subsystem in a fairly ad-hoc basis using "devspec" properties. For example, PCI creates them if it can correlate the probed device with a DT node. Some powerpc specific busses do that too. However, i2c doesn't and it would be nice to have something more generic since technically any device can have a corresponding device tree node. This patch adds an "of_node" symlink to devices that have a non-NULL dev->of_node pointer, the patch is pretty trivial and seems to work just fine for me. Signed-off-by: Benjamin Herrenschmidt Acked-by: Rob Herring Backport notes: Submission to LKML at: https://patchwork.kernel.org/patch/5842241/ Signed-off-by: Jeremy Kerr commit 1d9d9bdad2553f39de92eba40f8663eb45819e8c Author: Michael Ellerman Date: Sat Mar 28 21:35:16 2015 +1100 powerpc: Add a proper syscall for switching endianness We currently have a "special" syscall for switching endianness. This is syscall number 0x1ebe, which is handled explicitly in the 64-bit syscall exception entry. That has a few problems, firstly the syscall number is outside of the usual range, which confuses various tools. For example strace doesn't recognise the syscall at all. Secondly it's handled explicitly as a special case in the syscall exception entry, which is complicated enough without it. As a first step toward removing the special syscall, we need to add a regular syscall that implements the same functionality. The logic is simple, it simply toggles the MSR_LE bit in the userspace MSR. This is the same as the special syscall, with the caveat that the special syscall clobbers fewer registers. This version clobbers r9-r12, XER, CTR, and CR0-1,5-7. Signed-off-by: Michael Ellerman Backp
[Kernel-packages] [Bug 1439562] Re: backport request: include support for OpenPower hardware
OK, we have a new set of patches merged. Would you like these in a
separate bug?
[the first does change a powerpc-specific syscall number, if that
affects your preference of SRU vs. freeze]
The following patches have been merged to linux-next:
1d9d9bd powerpc: Add a proper syscall for switching endianness
-> merged to linux-next/master: 529d235a0e190ded1d21ccc80a73e625ebcad09b
37889e2 powerpc/powernv: Add OPAL message notifier unregister function
-> merged to linux-next/master: b921e90260cec1e04988bb3763491de885b67b51
2f0190b powerpc/powernv: Support OPAL requested heartbeat
-> merged to linux-next/master: 3bf57561d4dbd36ba45ce05656b0469bfdcc7ef2
e1c8954 device: Add dev_of_node() accessor
-> merged to linux-next/master: e8a51e1b51ee5730ad3913f3962e3099a5e19359
2c242b3 drivers/core/of: Add symlink to device-tree from devices with an OF node
-> merged to linux-next/master: 5590f3196b293574a12be58d06d5e1120d8856ec
Leaving the following patches pending:
3525984 powerpc/powernv: Add interfaces for flash device access
1acd5dd drivers/mtd: add powernv flash MTD abstraction driver
-> pending mtd review
8589e12 powerpc/powernv: Add opal-prd channel
-> pending powerpc review.
-> Ensure we have the DPO member of enum opal_msg_type present
--
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/1439562
Title:
backport request: include support for OpenPower hardware
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Vivid:
Fix Committed
Bug description:
We've prepared a series of patches (ported to Ubuntu-3.19.0-11.11),
which add OpenPower support to the Ubuntu kernel.
The changes are available in the ubuntu/vivid branch of:
https://github.com/open-power/linux.git
(or I can attach them separately).
Changelogs are as follows:
commit 2f0190bd43764559b250a5bd11aca050f909aa21
Author: Benjamin Herrenschmidt
Date: Fri Nov 14 16:13:50 2014 +1100
powerpc/powernv: Support OPAL requested heartbeat
If OPAL requests it, call it back via opal_poll_events() at a
regular interval. Some versions of OPAL on some machines require
this to operate some internal timeouts properly.
Signed-off-by: Benjamin Herrenschmidt
Backport notes:
cherry-picked from mpe-next, 3bf57561d4dbd36ba45ce05656b0469bfdcc7ef2
minor conflicts resolved
Signed-off-by: Jeremy Kerr
commit e1c89541e7163494ad091f3c2622649d91ac7597
Author: Benjamin Herrenschmidt
Date: Mon Feb 16 14:59:08 2015 +1100
device: Add dev_of_node() accessor
Suggested by Arnd Bergmann, this gives a practical accessor for
the of_node field of struct device while instructing the compiler
that it will be NULL if CONFIG_OF is not set.
Signed-off-by: Benjamin Herrenschmidt
Acked-by: Rob Herring
Backport notes:
Submission to LKML at: https://patchwork.kernel.org/patch/5831161/
Signed-off-by: Jeremy Kerr
commit 2c242b30756f77528516a4e9e986818ac4e90490
Author: Benjamin Herrenschmidt
Date: Wed Feb 18 11:25:18 2015 +1100
drivers/core/of: Add symlink to device-tree from devices with an OF node
So I've been annoyed lately with having a bunch of devices such as i2c
eeproms (for use by VPDs, server world !) and other bits and pieces that
I want to be able to identify from userspace, and possibly provide
additional data about from FW.
Basically, it boils down to correlating the sysfs device with the OF
tree device node, so that user space can use device-tree info such as
additional "location" or "label" (or whatever else we can come up with)
propreties to identify a given device, or get some attributes of use
about it, etc...
Now, so far, we've done that in some subsystem in a fairly ad-hoc basis
using "devspec" properties. For example, PCI creates them if it can
correlate the probed device with a DT node. Some powerpc specific busses
do that too.
However, i2c doesn't and it would be nice to have something more generic
since technically any device can have a corresponding device tree node.
This patch adds an "of_node" symlink to devices that have a non-NULL
dev->of_node pointer, the patch is pretty trivial and seems to work just
fine for me.
Signed-off-by: Benjamin Herrenschmidt
Acked-by: Rob Herring
Backport notes:
Submission to LKML at: https://patchwork.kernel.org/patch/5842241/
Signed-off-by: Jeremy Kerr
commit 1d9d9bdad2553f39de92eba40f8663eb45819e8c
Author: Michael Ellerman
Date: Sat Mar 28 21:35:16 2015 +1100
powerpc: Add a proper syscall fo
[Kernel-packages] [Bug 1439562] Re: backport request: include support for OpenPower hardware
Sure thing. The patch in my ubuntu-vivid git tree is slightly modified from the upstream commit - just so we don't need to include those prerequisites. However, if you're after pristine upstream commits, the following will work on top of the vivid tree (as at 83f803a6): commit 4c3b21686111e0ac6018469dacbc5549f9915cf8 Author: Michael Ellerman Date: Fri Dec 5 21:16:59 2014 +1100 powerpc/kernel: Make syscall_exit a local label Currently when we back trace something that is in a syscall we see something like this: [c000] [c000] SyS_read+0x6c/0x110 [c000] [c000] syscall_exit+0x0/0x98 Although it's entirely correct, seeing syscall_exit at the bottom can be confusing - we were exiting from a syscall and then called SyS_read() ? If we instead change syscall_exit to be a local label we get something more intuitive: [c001fa46fde0] [c026719c] SyS_read+0x6c/0x110 [c001fa46fe30] [c0009264] system_call+0x38/0xd0 ie. we were handling a system call, and it was SyS_read(). Signed-off-by: Michael Ellerman commit a4bcbe6a41adcaa5e7f1830a7c1da8691d9d2b1d Author: Michael Ellerman Date: Wed Jan 14 14:47:56 2015 +1100 powerpc: Remove old compile time disabled syscall tracing code We have code to do syscall tracing which is disabled at compile time by default. It's not been touched since the dawn of time (ie. v2.6.12). There are now better ways to do syscall tracing, ie. using the raw_syscall, or syscall tracepoints. For the specific case of tracing syscalls at boot on a system that doesn't get to userspace, you can boot with: trace_event=syscalls tp_printk=on Which will trace syscalls from boot, and echo all output to the console. Signed-off-by: Michael Ellerman -- 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/1439562 Title: backport request: include support for OpenPower hardware Status in linux package in Ubuntu: Fix Committed Status in linux source package in Vivid: Fix Committed Bug description: We've prepared a series of patches (ported to Ubuntu-3.19.0-11.11), which add OpenPower support to the Ubuntu kernel. The changes are available in the ubuntu/vivid branch of: https://github.com/open-power/linux.git (or I can attach them separately). Changelogs are as follows: commit 2f0190bd43764559b250a5bd11aca050f909aa21 Author: Benjamin Herrenschmidt Date: Fri Nov 14 16:13:50 2014 +1100 powerpc/powernv: Support OPAL requested heartbeat If OPAL requests it, call it back via opal_poll_events() at a regular interval. Some versions of OPAL on some machines require this to operate some internal timeouts properly. Signed-off-by: Benjamin Herrenschmidt Backport notes: cherry-picked from mpe-next, 3bf57561d4dbd36ba45ce05656b0469bfdcc7ef2 minor conflicts resolved Signed-off-by: Jeremy Kerr commit e1c89541e7163494ad091f3c2622649d91ac7597 Author: Benjamin Herrenschmidt Date: Mon Feb 16 14:59:08 2015 +1100 device: Add dev_of_node() accessor Suggested by Arnd Bergmann, this gives a practical accessor for the of_node field of struct device while instructing the compiler that it will be NULL if CONFIG_OF is not set. Signed-off-by: Benjamin Herrenschmidt Acked-by: Rob Herring Backport notes: Submission to LKML at: https://patchwork.kernel.org/patch/5831161/ Signed-off-by: Jeremy Kerr commit 2c242b30756f77528516a4e9e986818ac4e90490 Author: Benjamin Herrenschmidt Date: Wed Feb 18 11:25:18 2015 +1100 drivers/core/of: Add symlink to device-tree from devices with an OF node So I've been annoyed lately with having a bunch of devices such as i2c eeproms (for use by VPDs, server world !) and other bits and pieces that I want to be able to identify from userspace, and possibly provide additional data about from FW. Basically, it boils down to correlating the sysfs device with the OF tree device node, so that user space can use device-tree info such as additional "location" or "label" (or whatever else we can come up with) propreties to identify a given device, or get some attributes of use about it, etc... Now, so far, we've done that in some subsystem in a fairly ad-hoc basis using "devspec" properties. For example, PCI creates them if it can correlate the probed device with a DT node. Some powerpc specific busses do that too. However, i2c doesn't and it would be nice to have something more generic
[Kernel-packages] [Bug 1439562] Re: backport request: include support for OpenPower hardware
Also, the 'powerpc/powernv: Support OPAL requested heartbeat' change
requires a couple of prereqs if you're looking to use the pristine
upstream version too:
commit 08135139430fabdeaa990da8a9e0d436aad0672b
Author: Michael Ellerman
Date: Wed Jan 28 15:10:33 2015 +1100
powerpc/powernv: Remove "opal" prefix from pr_xxx()s
In commit c8742f85125d "powerpc/powernv: Expose OPAL firmware symbol
map" I added pr_fmt() to opal.c. This left some existing pr_xxx()s with
duplicate "opal" prefixes, eg:
opal: opal: Found 0 interrupts reserved for OPAL
Fix them all up. Also make the "Not not found" message a bit more
verbose.
Signed-off-by: Michael Ellerman
commit c1c3a526bb4ddbec7639a9fb3b84fede25b201d9
Author: Gavin Shan
Date: Fri Jan 23 14:25:05 2015 +1100
powerpc/powernv: Separate function for OPAL IRQ setup
The patch put the OPAL interrupt setup logic in opal_init() into
seperate function opal_irq_init() for easier code maintaining. The
patch doesn't introduce logic changes except:
* Rename variable names.
* Release virtual IRQ upon error from request_irq().
* Don't cache the virtual IRQ to opal_irqs[] upon error from
request_irq().
Suggested-by: Michael Ellerman
Signed-off-by: Gavin Shan
Signed-off-by: Michael Ellerman
--
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/1439562
Title:
backport request: include support for OpenPower hardware
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Vivid:
Fix Committed
Bug description:
We've prepared a series of patches (ported to Ubuntu-3.19.0-11.11),
which add OpenPower support to the Ubuntu kernel.
The changes are available in the ubuntu/vivid branch of:
https://github.com/open-power/linux.git
(or I can attach them separately).
Changelogs are as follows:
commit 2f0190bd43764559b250a5bd11aca050f909aa21
Author: Benjamin Herrenschmidt
Date: Fri Nov 14 16:13:50 2014 +1100
powerpc/powernv: Support OPAL requested heartbeat
If OPAL requests it, call it back via opal_poll_events() at a
regular interval. Some versions of OPAL on some machines require
this to operate some internal timeouts properly.
Signed-off-by: Benjamin Herrenschmidt
Backport notes:
cherry-picked from mpe-next, 3bf57561d4dbd36ba45ce05656b0469bfdcc7ef2
minor conflicts resolved
Signed-off-by: Jeremy Kerr
commit e1c89541e7163494ad091f3c2622649d91ac7597
Author: Benjamin Herrenschmidt
Date: Mon Feb 16 14:59:08 2015 +1100
device: Add dev_of_node() accessor
Suggested by Arnd Bergmann, this gives a practical accessor for
the of_node field of struct device while instructing the compiler
that it will be NULL if CONFIG_OF is not set.
Signed-off-by: Benjamin Herrenschmidt
Acked-by: Rob Herring
Backport notes:
Submission to LKML at: https://patchwork.kernel.org/patch/5831161/
Signed-off-by: Jeremy Kerr
commit 2c242b30756f77528516a4e9e986818ac4e90490
Author: Benjamin Herrenschmidt
Date: Wed Feb 18 11:25:18 2015 +1100
drivers/core/of: Add symlink to device-tree from devices with an OF node
So I've been annoyed lately with having a bunch of devices such as i2c
eeproms (for use by VPDs, server world !) and other bits and pieces that
I want to be able to identify from userspace, and possibly provide
additional data about from FW.
Basically, it boils down to correlating the sysfs device with the OF
tree device node, so that user space can use device-tree info such as
additional "location" or "label" (or whatever else we can come up with)
propreties to identify a given device, or get some attributes of use
about it, etc...
Now, so far, we've done that in some subsystem in a fairly ad-hoc basis
using "devspec" properties. For example, PCI creates them if it can
correlate the probed device with a DT node. Some powerpc specific busses
do that too.
However, i2c doesn't and it would be nice to have something more generic
since technically any device can have a corresponding device tree node.
This patch adds an "of_node" symlink to devices that have a non-NULL
dev->of_node pointer, the patch is pretty trivial and seems to work just
fine for me.
Signed-off-by: Benjamin Herrenschmidt
Acked-by: Rob Herring
Backport notes:
Submission to LKML at: https://patchwork.kernel.org/patch/5842241/
Signed-off-by: Jeremy Kerr
commit 1d9
[Kernel-packages] [Bug 1439562] Re: backport request: include support for OpenPower hardware
This should do the trick: git cherry-pick 4c3b2168 a4bcbe6a 529d235a \ 08135139 c1c3a526 b921e902 \ 3bf57561 e8a51e1b 5590f319 -- 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/1439562 Title: backport request: include support for OpenPower hardware Status in linux package in Ubuntu: Fix Committed Status in linux source package in Vivid: Fix Committed Bug description: We've prepared a series of patches (ported to Ubuntu-3.19.0-11.11), which add OpenPower support to the Ubuntu kernel. The changes are available in the ubuntu/vivid branch of: https://github.com/open-power/linux.git (or I can attach them separately). Changelogs are as follows: commit 2f0190bd43764559b250a5bd11aca050f909aa21 Author: Benjamin Herrenschmidt Date: Fri Nov 14 16:13:50 2014 +1100 powerpc/powernv: Support OPAL requested heartbeat If OPAL requests it, call it back via opal_poll_events() at a regular interval. Some versions of OPAL on some machines require this to operate some internal timeouts properly. Signed-off-by: Benjamin Herrenschmidt Backport notes: cherry-picked from mpe-next, 3bf57561d4dbd36ba45ce05656b0469bfdcc7ef2 minor conflicts resolved Signed-off-by: Jeremy Kerr commit e1c89541e7163494ad091f3c2622649d91ac7597 Author: Benjamin Herrenschmidt Date: Mon Feb 16 14:59:08 2015 +1100 device: Add dev_of_node() accessor Suggested by Arnd Bergmann, this gives a practical accessor for the of_node field of struct device while instructing the compiler that it will be NULL if CONFIG_OF is not set. Signed-off-by: Benjamin Herrenschmidt Acked-by: Rob Herring Backport notes: Submission to LKML at: https://patchwork.kernel.org/patch/5831161/ Signed-off-by: Jeremy Kerr commit 2c242b30756f77528516a4e9e986818ac4e90490 Author: Benjamin Herrenschmidt Date: Wed Feb 18 11:25:18 2015 +1100 drivers/core/of: Add symlink to device-tree from devices with an OF node So I've been annoyed lately with having a bunch of devices such as i2c eeproms (for use by VPDs, server world !) and other bits and pieces that I want to be able to identify from userspace, and possibly provide additional data about from FW. Basically, it boils down to correlating the sysfs device with the OF tree device node, so that user space can use device-tree info such as additional "location" or "label" (or whatever else we can come up with) propreties to identify a given device, or get some attributes of use about it, etc... Now, so far, we've done that in some subsystem in a fairly ad-hoc basis using "devspec" properties. For example, PCI creates them if it can correlate the probed device with a DT node. Some powerpc specific busses do that too. However, i2c doesn't and it would be nice to have something more generic since technically any device can have a corresponding device tree node. This patch adds an "of_node" symlink to devices that have a non-NULL dev->of_node pointer, the patch is pretty trivial and seems to work just fine for me. Signed-off-by: Benjamin Herrenschmidt Acked-by: Rob Herring Backport notes: Submission to LKML at: https://patchwork.kernel.org/patch/5842241/ Signed-off-by: Jeremy Kerr commit 1d9d9bdad2553f39de92eba40f8663eb45819e8c Author: Michael Ellerman Date: Sat Mar 28 21:35:16 2015 +1100 powerpc: Add a proper syscall for switching endianness We currently have a "special" syscall for switching endianness. This is syscall number 0x1ebe, which is handled explicitly in the 64-bit syscall exception entry. That has a few problems, firstly the syscall number is outside of the usual range, which confuses various tools. For example strace doesn't recognise the syscall at all. Secondly it's handled explicitly as a special case in the syscall exception entry, which is complicated enough without it. As a first step toward removing the special syscall, we need to add a regular syscall that implements the same functionality. The logic is simple, it simply toggles the MSR_LE bit in the userspace MSR. This is the same as the special syscall, with the caveat that the special syscall clobbers fewer registers. This version clobbers r9-r12, XER, CTR, and CR0-1,5-7. Signed-off-by: Michael Ellerman Backport notes: Cherry-picked (with conflicts resolved) from mpe-next, commit 5
[Kernel-packages] [Bug 1439562] Re: backport request: include support for OpenPower hardware
OK, the prd changes have hit linux-next: 48c0615 powerpc/powernv: Merge common platform device initialisation 594fcb9 powerpc/powernv: Expose OPAL APIs required by PRD interface 0d7cd85 powerpc/powernv: Add opal-prd channel Would you prefer me to open a separate LP issue for these? Once these are included, we just the the MTD change to go. -- 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/1439562 Title: backport request: include support for OpenPower hardware Status in linux package in Ubuntu: Fix Released Status in linux source package in Utopic: Fix Committed Status in linux source package in Vivid: Fix Released Bug description: [Impact] This is a HWE SRU for OpenPower support in 3.16. [Fix] upstream commits: backported from commit 6a11e5c67a397e9a64cfde6961c83a7a64d7980c) backported from commit 608b286d1ddf38a7ceb624d2b689af095816d91c) cherry picked from commit 3bf57561d4dbd36ba45ce05656b0469bfdcc7ef2) cherry picked from commit 4c3b21686111e0ac6018469dacbc5549f9915cf8) cherry picked from commit a4bcbe6a41adcaa5e7f1830a7c1da8691d9d2b1d) backported from commit 08135139430fabdeaa990da8a9e0d436aad0672b) cherry picked from commit c1c3a526bb4ddbec7639a9fb3b84fede25b201d9) cherry picked from commit b921e90260cec1e04988bb3763491de885b67b51) backported from commit e8a51e1b51ee5730ad3913f3962e3099a5e19359) cherry picked from commit 5590f3196b293574a12be58d06d5e1120d8856ec) backported from commit 529d235a0e190ded1d21ccc80a73e625ebcad09b) [Test Case] Ensure kernel boots on specific OpenPower hardware. -- We've prepared a series of patches (ported to Ubuntu-3.19.0-11.11), which add OpenPower support to the Ubuntu kernel. The changes are available in the ubuntu/vivid branch of: https://github.com/open-power/linux.git (or I can attach them separately). Changelogs are as follows: commit 2f0190bd43764559b250a5bd11aca050f909aa21 Author: Benjamin Herrenschmidt Date: Fri Nov 14 16:13:50 2014 +1100 powerpc/powernv: Support OPAL requested heartbeat If OPAL requests it, call it back via opal_poll_events() at a regular interval. Some versions of OPAL on some machines require this to operate some internal timeouts properly. Signed-off-by: Benjamin Herrenschmidt Backport notes: cherry-picked from mpe-next, 3bf57561d4dbd36ba45ce05656b0469bfdcc7ef2 minor conflicts resolved Signed-off-by: Jeremy Kerr commit e1c89541e7163494ad091f3c2622649d91ac7597 Author: Benjamin Herrenschmidt Date: Mon Feb 16 14:59:08 2015 +1100 device: Add dev_of_node() accessor Suggested by Arnd Bergmann, this gives a practical accessor for the of_node field of struct device while instructing the compiler that it will be NULL if CONFIG_OF is not set. Signed-off-by: Benjamin Herrenschmidt Acked-by: Rob Herring Backport notes: Submission to LKML at: https://patchwork.kernel.org/patch/5831161/ Signed-off-by: Jeremy Kerr commit 2c242b30756f77528516a4e9e986818ac4e90490 Author: Benjamin Herrenschmidt Date: Wed Feb 18 11:25:18 2015 +1100 drivers/core/of: Add symlink to device-tree from devices with an OF node So I've been annoyed lately with having a bunch of devices such as i2c eeproms (for use by VPDs, server world !) and other bits and pieces that I want to be able to identify from userspace, and possibly provide additional data about from FW. Basically, it boils down to correlating the sysfs device with the OF tree device node, so that user space can use device-tree info such as additional "location" or "label" (or whatever else we can come up with) propreties to identify a given device, or get some attributes of use about it, etc... Now, so far, we've done that in some subsystem in a fairly ad-hoc basis using "devspec" properties. For example, PCI creates them if it can correlate the probed device with a DT node. Some powerpc specific busses do that too. However, i2c doesn't and it would be nice to have something more generic since technically any device can have a corresponding device tree node. This patch adds an "of_node" symlink to devices that have a non-NULL dev->of_node pointer, the patch is pretty trivial and seems to work just fine for me. Signed-off-by: Benjamin Herrenschmidt Acked-by: Rob Herring Backport notes: Submission to LKML at: https://patchwork.kernel.org/patch/5842241/ Signed-off-by: Jeremy Kerr commit 1d9d9bdad2553f39de92eba40f8663eb45819e8c Author: Michael Ellerman Date: Sat Mar 28 21:35:16 2015 +1100 powerpc: Add a proper syscall for switching endianness We curre
[Kernel-packages] [Bug 1464560] [NEW] Backport request: include PRD support for OpenPower kernels
Public bug reported: Following up on patches that were skipped in bug 1439562, this request is for the PRD (Processor Runtime Diagnostics) support in the ppc64le kernel. Patches have recently hit linux-next: 0d7cd85 powerpc/powernv: Add opal-prd channel 594fcb9 powerpc/powernv: Expose OPAL APIs required by PRD interface 48c0615 powerpc/powernv: Merge common platform device initialisation Let me know if you need any info (or dependencies) for these. ** 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/1464560 Title: Backport request: include PRD support for OpenPower kernels Status in linux package in Ubuntu: New Bug description: Following up on patches that were skipped in bug 1439562, this request is for the PRD (Processor Runtime Diagnostics) support in the ppc64le kernel. Patches have recently hit linux-next: 0d7cd85 powerpc/powernv: Add opal-prd channel 594fcb9 powerpc/powernv: Expose OPAL APIs required by PRD interface 48c0615 powerpc/powernv: Merge common platform device initialisation Let me know if you need any info (or dependencies) for these. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1464560/+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 1464560] Re: Backport request: include PRD support for OpenPower kernels
We've just had the last of our feature-enablement patches hit linux- next: 1cbb4a1 mtd: powernv: Add powernv flash MTD abstraction driver The MTD driver is required for full PRD functionality, but I can open a separate issue if you prefer. -- 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/1464560 Title: Backport request: include PRD support for OpenPower kernels Status in linux package in Ubuntu: Triaged Bug description: Following up on patches that were skipped in bug 1439562, this request is for the PRD (Processor Runtime Diagnostics) support in the ppc64le kernel. Patches have recently hit linux-next: 0d7cd85 powerpc/powernv: Add opal-prd channel 594fcb9 powerpc/powernv: Expose OPAL APIs required by PRD interface 48c0615 powerpc/powernv: Merge common platform device initialisation Let me know if you need any info (or dependencies) for these. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1464560/+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 1464560] Re: Backport request: include PRD support for OpenPower kernels
And we've just had a couple of fixes hit linux-next too: 7185795 powerpc/powernv: fix construction of opal PRD messages cdf2bc1 powerpc/include: Add opal-prd to installed uapi headers Yes, as Breno has mentioned, we're looking at 3.19 and (if possible) 3.16. -- 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/1464560 Title: Backport request: include PRD support for OpenPower kernels Status in linux package in Ubuntu: In Progress Bug description: Following up on patches that were skipped in bug 1439562, this request is for the PRD (Processor Runtime Diagnostics) support in the ppc64le kernel. Patches have recently hit linux-next: 0d7cd85 powerpc/powernv: Add opal-prd channel 594fcb9 powerpc/powernv: Expose OPAL APIs required by PRD interface 48c0615 powerpc/powernv: Merge common platform device initialisation Let me know if you need any info (or dependencies) for these. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1464560/+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 1572712] Re: console hung during Ubuntu 16.04 netboot install 4.4.0-12-generic [soft lockup]
.811243] swapper/2 R running task0 0 1 0x0804 [ 57.811246] Call Trace: [ 57.811248] [c03c97532fe0] [c00fb8c0] sched_show_task+0xe0/0x180 (unreliable) [ 57.811251] [c03c97533050] [c013e714] rcu_dump_cpu_stacks+0xe4/0x150 [ 57.811253] [c03c975330a0] [c0143e24] rcu_check_callbacks+0x6b4/0x9b0 [ 57.811255] [c03c975331d0] [c014bc88] update_process_times+0x58/0xa0 [ 57.811258] [c03c97533200] [c0162d38] tick_sched_handle.isra.6+0x48/0xe0 [ 57.811260] [c03c97533240] [c0162e34] tick_sched_timer+0x64/0xd0 [ 57.811262] [c03c97533280] [c014c7b4] __hrtimer_run_queues+0x134/0x470 [ 57.811263] [c03c97533310] [c014d7ec] hrtimer_interrupt+0xec/0x2c0 [ 57.811266] [c03c975333d0] [c001f59c] __timer_interrupt+0x8c/0x290 [ 57.811268] [c03c97533420] [c001f950] timer_interrupt+0xa0/0xe0 [ 57.811269] [c03c97533450] [c0002714] decrementer_common+0x114/0x180 [ 57.811272] --- interrupt: 901 at arch_local_irq_restore+0x74/0x90 [ 57.811272] LR = arch_local_irq_restore+0x74/0x90 [ 57.811274] [c03c97533740] [c03c8af61ad8] 0xc03c8af61ad8 (unreliable) [ 57.811277] [c03c97533760] [c0ad8cdc] _raw_spin_unlock_irqrestore+0x4c/0xb0 == Comment: #3 - NAVEED A. UPPINANGADY SALIH - 2016-03-15 07:47:16 == Please note: we did not face this hung issue with netboot of 4.4.0-11-generic, hence we can call this bug as regression.. Also note, this soft lock up issue does not completely block installation , we can proceed with installation but we do see occasional console hangs and soft lockup console messages. == Comment: #19 - Jeremy Kerr - 2016-03-22 06:37:28 == Seeing the same issue with the current installer build (20101020ubuntu440) - soft lockup at the language selection screen, with no input possible. It's intermittent, but is happening about two times out of three. == Comment: #59 - Murilo Fossa Vicentini - 2016-04-12 17:05:26 == If I blacklist the ast driver (along with drm, ttm and so on) from being loaded by passing modprobe.blacklist=ast in the boot arguments, I don't hit this issue. I also wasn't able to reproduce this issue in a tuleta box, so it seems to be related to the graphics driver. Indira can you double check this "workaround" solves the issue in your system as well? I am uploading the installation logs of a failure in the latest netboot image. == Comment: #73 - INDIRA P. JOGA - 2016-04-14 06:00:43 == Verified below test scenarios with workaround .Did not hit with BUG soft lockup error and also hang issue. Fix is working fine. > Installed ubuntu16.04 over Travis3EN, while ray system is in Habanero LC FW ( OP810.30 OP810 1603G) > Updated to SL FW (TN71-BP012-810.1611.20160406a) & reinstalled ray with ubuntu16.04 via Travis3EN. Regards, Indira To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1572712/+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 1464560] Re: Backport request: include PRD support for OpenPower kernels
Hi Chris,
The following commits should bring the PRD support into the current
vivid branch, using only pristine upstream changes:
d800ba1 powerpc/powernv: Move OPAL API definitions to opal-api.h
d7cf83f powerpc/powernv: Move opal-api.h closer to the Skiboot version
ed59190 powerpc/powernv: Add interfaces for flash device access
1cbb4a1 mtd: powernv: Add powernv flash MTD abstraction driver
48c0615 powerpc/powernv: Merge common platform device initialisation
594fcb9 powerpc/powernv: Expose OPAL APIs required by PRD interface
646b54f powerpc/powernv: Remove powernv RTAS support
0d7cd85 powerpc/powernv: Add opal-prd channel
7185795 powerpc/powernv: fix construction of opal PRD messages
cdf2bc1 powerpc/include: Add opal-prd to installed uapi headers
(the last two are fixes that have hit mainline since the original merge)
However, we'll also need the changes in the actual merge commit to
mainline:
commit df60f57684529a1dde4461cf84354453b440806a
Merge: 605f302 b921e90
Author: Michael Ellerman
Date: Thu Mar 26 20:03:16 2015 +1100
Merge branch 'next-misc' of
git://git.kernel.org/pub/scm/linux/kernel/git/benh/powerpc into test
Merge miscellaneous bits from benh. Fix a minor conflict with
OpalMessageType changing names to opal_msg_type.
diff --cc arch/powerpc/include/asm/opal.h
index 0ef0fd6,4ea21ea..c08de77
--- a/arch/powerpc/include/asm/opal.h
+++ b/arch/powerpc/include/asm/opal.h
@@@ -208,8 -946,10 +208,10 @@@ extern void hvc_opal_init_early(void)
extern int opal_notifier_register(struct notifier_block *nb);
extern int opal_notifier_unregister(struct notifier_block *nb);
-extern int opal_message_notifier_register(enum OpalMessageType msg_type,
+extern int opal_message_notifier_register(enum opal_msg_type msg_type,
struct notifier_block *nb);
-extern int opal_message_notifier_unregister(enum OpalMessageType msg_type,
++extern int opal_message_notifier_unregister(enum opal_msg_type msg_type,
+ struct notifier_block *nb);
extern void opal_notifier_enable(void);
extern void opal_notifier_disable(void);
extern void opal_notifier_update_evt(uint64_t evt_mask, uint64_t evt_val);
diff --cc arch/powerpc/platforms/powernv/opal.c
index 142a08a,8b3834a..d403b2b
--- a/arch/powerpc/platforms/powernv/opal.c
+++ b/arch/powerpc/platforms/powernv/opal.c
@@@ -302,16 -305,11 +305,11 @@@ void opal_notifier_disable(void
* Opal message notifier based on message type. Allow subscribers to get
* notified for specific messgae type.
*/
-int opal_message_notifier_register(enum OpalMessageType msg_type,
+int opal_message_notifier_register(enum opal_msg_type msg_type,
struct notifier_block *nb)
{
- if (!nb) {
- pr_warning("%s: Invalid argument (%p)\n",
- __func__, nb);
- return -EINVAL;
- }
- if (msg_type > OPAL_MSG_TYPE_MAX) {
- pr_warning("%s: Invalid message type argument (%d)\n",
+ if (!nb || msg_type >= OPAL_MSG_TYPE_MAX) {
+ pr_warning("%s: Invalid arguments, msg_type:%d\n",
__func__, msg_type);
return -EINVAL;
}
@@@ -319,6 -318,13 +318,13 @@@
&opal_msg_notifier_head[msg_type], nb);
}
-int opal_message_notifier_unregister(enum OpalMessageType msg_type,
++int opal_message_notifier_unregister(enum opal_msg_type msg_type,
+struct notifier_block *nb)
+ {
+ return atomic_notifier_chain_unregister(
+ &opal_msg_notifier_head[msg_type], nb);
+ }
+
static void opal_message_do_notify(uint32_t msg_type, void *msg)
{
/* notify subscribers */
- but I'm not sure how you'd prefer to apply this diff from a merge.
--
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/1464560
Title:
Backport request: include PRD support for OpenPower kernels
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Utopic:
New
Status in linux source package in Vivid:
New
Bug description:
[Impact]
Following up on patches that were skipped in bug 1439562, this request
is for the PRD (Processor Runtime Diagnostics) support in the ppc64le
kernel.
[Fix]
cdf2bc1 powerpc/include: Add opal-prd to installed uapi headers
7185795 powerpc/powernv: fix construction of opal PRD messages
0d7cd85 powerpc/powernv: Add opal-prd channel
594fcb9 powerpc/powernv: Expose OPAL APIs required by PRD interface
48c0615 powerpc/powernv: Merge common platform device initialisation
$ git describe 0d7cd85 594fcb9 48c0615 7185795 cdf2bc1
v4.1-rc3-86-g0d7cd85
v4.1-rc3-85-g594fcb9
v4.1-rc3-84-g48c0615
v4.1-rc3-147-g7185795
v4.1-rc3-148-gcdf2bc1
Let me know if you need any info (or
[Kernel-packages] [Bug 1464560] Re: Backport request: include PRD support for OpenPower kernels
Just booted 3.19.0-26-generic, all looks good! ** Tags removed: verification-needed-vivid ** Tags added: verification-done-vivid -- 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/1464560 Title: Backport request: include PRD support for OpenPower kernels Status in linux package in Ubuntu: Fix Released Status in linux source package in Utopic: In Progress Status in linux source package in Vivid: Fix Committed Bug description: [Impact] Following up on patches that were skipped in bug 1439562, this request is for the PRD (Processor Runtime Diagnostics) support in the ppc64le kernel. [Fix] For Wily: 1cbb4a1 mtd: powernv: Add powernv flash MTD abstraction driver * 48c0615 powerpc/powernv: Merge common platform device initialisation * 594fcb9 powerpc/powernv: Expose OPAL APIs required by PRD interface * 0d7cd85 powerpc/powernv: Add opal-prd channel * 7185795 powerpc/powernv: fix construction of opal PRD messages * cdf2bc1 powerpc/include: Add opal-prd to installed uapi headers * d8ea782 powerpc/powernv: Fix vma page prot flags in opal-prd driver * For Vivid: d800ba1 powerpc/powernv: Move OPAL API definitions to opal-api.h d7cf83f powerpc/powernv: Move opal-api.h closer to the Skiboot version ed59190 powerpc/powernv: Add interfaces for flash device access 1cbb4a1 mtd: powernv: Add powernv flash MTD abstraction driver 48c0615 powerpc/powernv: Merge common platform device initialisation 594fcb9 powerpc/powernv: Expose OPAL APIs required by PRD interface 646b54f powerpc/powernv: Remove powernv RTAS support 0d7cd85 powerpc/powernv: Add opal-prd channel 7185795 powerpc/powernv: fix construction of opal PRD messages cdf2bc1 powerpc/include: Add opal-prd to installed uapi headers d8ea782 powerpc/powernv: Fix vma page prot flags in opal-prd driver All commits are in at most v4.2 Plus config changes. [Test Case] 'modprobe opal_prb' and use PRD support. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1464560/+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 1482343] Re: Trigger a checkstop on unrecoverable MCE/HMI errors to inform BMC/OCC about the error.
** Package changed: ubuntu => linux (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/1482343 Title: Trigger a checkstop on unrecoverable MCE/HMI errors to inform BMC/OCC about the error. Status in linux package in Ubuntu: New Bug description: The current implementation of Machine Check handler and HMI handler in Linux, goes down kernel panic path for unrecoverable errors. On FSP based system FSP also gets notified about these errors which then forwards it to PRD (that runs on FSP) for error analysis and gard record creation. On OpenPower (BMC based system e.g. Habanero from TYAN) where PRD runs in Linux host, it never gets a chance to do error analysis at the time of Linux crash and no gard record is created for such errors. Since the faulty component never gets de-configured, the system is vulnerable to get hit by same HW error again. To fix this issue, a new OPAL call 'opal_cec_reboot2()' has been introduced to trigger a checkstop on BMC based system to inform BMC/OCC about this error, so that BMC can collect relevant data for error analysis and decide what component to de-configure before rebooting. Linux kernel should invoke this opal call for unrecoverable MCE and HMI instead before calling kernel panic so that OCC is informed about the error. The kernel changes has already been posted to upstream and are listed below: https://lists.ozlabs.org/pipermail/linuxppc-dev/2015-May/128341.html https://lists.ozlabs.org/pipermail/linuxppc-dev/2015-May/128342.html https://lists.ozlabs.org/pipermail/linuxppc-dev/2015-August/132045.html https://lists.ozlabs.org/pipermail/linuxppc-dev/2015-August/132114.html Above patches needs to be included in ubuntu 14.04.3+ We will update this bug with commit ids, once the above patches are accepted upstream. Contact Information = mahesh.salgaon...@in.ibm.com ---uname output--- Linux rcx2d403 3.19.0-26-generic #27 SMP Tue Aug 4 01:38:15 CDT 2015 ppc64le ppc64le ppc64le GNU/Linux ---Additional Hardware Info--- Habanero pass2 system Machine Type = OpenPower, Habanero ---System Hang--- If system is hung, it can be recovered by sending ipmi power off/on command. $ ipmitool -H -I lanplus -U -P power off $ ipmitool -H -I lanplus -U -P power on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1482343/+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 1514711] Re: Installer doesn't include ast GPU driver for OpenPower machines
Assigning to linux package, as per https://wiki.ubuntu.com/Bugs/FindRightPackage. ** Package changed: ubuntu => linux (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/1514711 Title: Installer doesn't include ast GPU driver for OpenPower machines Status in linux package in Ubuntu: Incomplete Bug description: When booting the Ubuntu 14.03.4 installer on an OpenPower machine with a VGA monitor attached, we see no output - the only installer output is over the physical UART (or SOL session). Petitboot is displayed over both VGA and UART, but not the installer UI. It seems like the ast GPU driver isn't present on the installer image (but is present for the non-installer kernels), which is required for graphics output on these machines. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1514711/+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
