This bug was fixed in the package skiboot - 5.1.13-0ubuntu1~14.04.1
---
skiboot (5.1.13-0ubuntu1~14.04.1) trusty; urgency=medium
* New upstream release, adding support for newer hardware and firmware.
LP: #1512188.
- drop no longer needed parts of
** Changed in: skiboot (Ubuntu Wily)
Status: Fix Committed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1512188
Title:
Update request: skiboot 5.1.9 for OpenPower machines
To
Wait, wily has EOLed now. So, I am removing the verification-needed tag,
and adding verification-done.
If you need me to test on any particular version, please let me know
which.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
OK, all fine on trusty! Now checking wily.
** Tags removed: removal-candidate verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1512188
Title:
Sorry - missed this one. The update is fine for xenial, testing with
trusty now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1512188
Title:
Update request: skiboot 5.1.9 for OpenPower machines
Hello Jeremy, or anyone else affected,
Accepted skiboot into wily-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/skiboot/5.1.13-0ubuntu1~15.10.1 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
I just installed a trusty on a OpenPOWER system (Habanero). Firmware is v1.8
and it is running a linux-image-generic-lts-xenial.
How do I pull the newer opal-prd to give it a try ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
For testing, a suitable check would be to ensure that the opal-prd
daemon is running; just a successful boot, then `service opal-prd
status` would be fine (and that also covers the --pnor argument too).
We can certainly test this on trusty and wily here.
--
You received this bug notification
The most important part of Steve's questions seems to have been missed
here - what testing needs to be done. Is it a simple matter of booting
the machine and checking that it does indeed still boot, or does it
require a specific workload, or series of testing steps?
Are there people ready and
Also, for completeness: running the PRD daemon is only required on
machines that have the "diagnostics" OPAL firmware feature. At present
(and this is unlikely to change), the set of these machines is
equivalent to the set of OpenPOWER machines.
To be exact, this is indicated on a running system
Hi Steve,
> I also don't know
> which systems are already supported by the version of opal-prd in trusty;
> are the openpower systems the only ones we need to watch for regressions on,
> or are there others?
The former: opal-prd is only used on OpenPOWER machines, so that's all
we'll need to
Hi,
There is a small issue with the systemd opal-prd.service file :
ExecStart=/usr/sbin/opal-prd
it should specify the mtd device, as done in the upstart and init
scripts :
ExecStart=/usr/sbin/opal-prd --pnor /dev/mtd0
I have a couple of openpower systems running xenial, so I can give
On Fri, Feb 05, 2016 at 04:28:18PM -, Cédric Le Goater wrote:
> There is a small issue with the systemd opal-prd.service file :
> ExecStart=/usr/sbin/opal-prd
> it should specify the mtd device, as done in the upstart and init
> scripts :
> ExecStart=/usr/sbin/opal-prd --pnor
** Also affects: skiboot (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: skiboot (Ubuntu Trusty)
Assignee: (unassigned) => Steve Langasek (vorlon)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug was fixed in the package skiboot - 5.1.13-0ubuntu1
---
skiboot (5.1.13-0ubuntu1) xenial; urgency=medium
* New upstream release, adding support for newer hardware and firmware.
LP: #1512188.
- drop no longer needed parts of debian/patches/uninitialized_uses.patch.
I've uploaded skiboot 5.1.13 to xenial, trusty, and wily. However,
before it can be accepted for SRU into the stable releases, we would
need a test plan for validating this update. How will we ensure that
the new binary package hasn't regressed anything, vs. the 5.1.1
currently in the release?
** Changed in: skiboot (Ubuntu)
Assignee: (unassigned) => Taco Screen team (taco-screen-team)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1512188
Title:
Update request: skiboot 5.1.9 for
** Tags added: upgrade-software-version
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1512188
Title:
Update request: skiboot 5.1.9 for OpenPower machines
To manage notifications about this bug go
18 matches
Mail list logo
