--- Comment From gpicc...@br.ibm.com 2016-09-15 17:13 EDT---
> On Tue, Sep 13, 2016 at 06:20:49PM -, bugproxy wrote:
[...]
> Based on the feedback from gpicc...@br.ibm.com, it does not appear that the
> buggy udev rule is blocking progress on this bug.
>
[...]
> > I should also ammend
On Tue, Sep 13, 2016 at 06:20:49PM -, bugproxy wrote:
> During investigation, and problem/mistake was found with systemd but is
> almost-certainly not the cause of the hang.
Agreed.
> This fixed systemd was supposedly being made available in xenial-proposed
> repositories, but so far does
--- Comment From dougm...@us.ibm.com 2016-09-13 14:16 EDT---
This bug was opened because of a hang being experienced while booting the
Ubuntu 16.04 network installer on Briggs & Stratton machines with their X710
ethernet adapters, using the i40e driver.
During investigation, and
--- Comment From dougm...@us.ibm.com 2016-09-12 11:09 EDT---
Reopening: xenial-proposed installer has not been updated, cannot verify fix.
Set back to fixed/verify once
http://ports.ubuntu.com/ubuntu-ports/dists/xenial-proposed installer has been
updated with fixed systemd to be tested.
--- Comment From dougm...@us.ibm.com 2016-09-12 08:33 EDT---
Still no new installer images for xenial-proposed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
--- Comment From dougm...@us.ibm.com 2016-09-10 08:29 EDT---
The installer images for xenial-proposed have not yet been updated.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
--- Comment From dougm...@us.ibm.com 2016-09-08 07:34 EDT---
Still waiting for updated installer images.
http://ports.ubuntu.com/ubuntu-ports/dists/xenial-proposed/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/
still showing images from August.
--
You received
--- Comment From dougm...@us.ibm.com 2016-09-07 10:25 EDT---
Waiting for xenial-proposed installer to be updated. Currently, still shows
2016-09-02.
--- Comment From dougm...@us.ibm.com 2016-09-07 10:26 EDT---
Err, should be "2016-08-02" as current content date on
--- Comment From gpicc...@br.ibm.com 2016-08-30 16:01 EDT---
pitti/vorlon, thanks for your suggestions. Unfortunately, I wasn't able to get
more information by placing a fixed delay in init script - what I did was to
execute in background a little script on the beginning of init that
9 matches
Mail list logo