[Touch-packages] [Bug 1512323] Re: devices on devel-proposed/ubuntu do not boot with systemd 227-2ubuntu1

[Jean-Baptiste Lallement]

** Changed in: canonical-devices-system-image
   Status: Confirmed => Fix Committed

** Changed in: canonical-devices-system-image
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1512323

Title:
  devices on devel-proposed/ubuntu do not boot with systemd 227-2ubuntu1

Status in Canonical System Image:
  Fix Released
Status in android package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  Last known good build: mako devel-proposed/ubuntu r336

  Affects builds from devel-proposed/ubuntu starting from first Xenial
  build.

  Test Case:
  Boot in fastboot mode and flash with:
  $ ubuntu-device-flash -v touch --channel=ubuntu-touch/devel-proposed/ubuntu 
--bootstrap
  or 
  upgrade from 336 to latest devel-proposed image

  Actual Result
  During a successful flashing operation of a device from fastboot, it boots 
once into recovery, then reboots and a rotating Ubuntu logo is displayed while 
the devices is being flashed.
  With this issue, on the second stage of the flash the phone is stuck on the 
vendor's logo (google or bq) and the rotating ubuntu logo is never displayed.

  Same problem on krillin devel-proposed/krillin.en 235

  Workaround:
  Boot into recovery, mount the system partition and downgrade systemd to 
225-1ubuntu9

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1512323/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Re: [Touch-packages] [Bug 1512323] Re: devices on devel-proposed/ubuntu do not boot with systemd 227-2ubuntu1

[Steve Langasek]

On Mon, Nov 16, 2015 at 03:49:15PM -, Martin Pitt wrote:
> > the only place where an unaligned 'out' argument is passed to
> siphash24_finalize() in practice is the test case

> No, also in networkd.

The code I see here in src/libsystemd-network/sd-dhcp-server.c is:

uint64_t hash;
siphash24_finalize((uint8_t*), );

which has no alignment issue.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1512323

Title:
  devices on devel-proposed/ubuntu do not boot with systemd 227-2ubuntu1

Status in Canonical System Image:
  Confirmed
Status in android package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  Last known good build: mako devel-proposed/ubuntu r336

  Affects builds from devel-proposed/ubuntu starting from first Xenial
  build.

  Test Case:
  Boot in fastboot mode and flash with:
  $ ubuntu-device-flash -v touch --channel=ubuntu-touch/devel-proposed/ubuntu 
--bootstrap
  or 
  upgrade from 336 to latest devel-proposed image

  Actual Result
  During a successful flashing operation of a device from fastboot, it boots 
once into recovery, then reboots and a rotating Ubuntu logo is displayed while 
the devices is being flashed.
  With this issue, on the second stage of the flash the phone is stuck on the 
vendor's logo (google or bq) and the rotating ubuntu logo is never displayed.

  Same problem on krillin devel-proposed/krillin.en 235

  Workaround:
  Boot into recovery, mount the system partition and downgrade systemd to 
225-1ubuntu9

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1512323/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Re: [Touch-packages] [Bug 1512323] Re: devices on devel-proposed/ubuntu do not boot with systemd 227-2ubuntu1

[Steve Langasek]

On Mon, Nov 16, 2015 at 08:03:57AM -, Martin Pitt wrote:
> It's still in siphash, due to a similar problem with the out argument:

> 0x2a02a9e8 in siphash24_finalize (out=0x2a065229 "", state=0xbefff970) at 
> src/basic/siphash24.c:182
> 182 *(le64_t*)out = htole64(state->v0 ^ state->v1 ^ state->v2  ^ 
> state->v3);

> I'll follow up on the upstream PR.

That is a bug in siphash24, but the only place where an unaligned 'out'
argument is passed to siphash24_finalize() in practice is the test case, so
that's not urgent to fix.

But certainly, siphash24_finalize() needs to be fixed either by changing the
argument to uint64_t* or by handling unaligned buffers.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1512323

Title:
  devices on devel-proposed/ubuntu do not boot with systemd 227-2ubuntu1

Status in Canonical System Image:
  Confirmed
Status in android package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  Last known good build: mako devel-proposed/ubuntu r336

  Affects builds from devel-proposed/ubuntu starting from first Xenial
  build.

  Test Case:
  Boot in fastboot mode and flash with:
  $ ubuntu-device-flash -v touch --channel=ubuntu-touch/devel-proposed/ubuntu 
--bootstrap
  or 
  upgrade from 336 to latest devel-proposed image

  Actual Result
  During a successful flashing operation of a device from fastboot, it boots 
once into recovery, then reboots and a rotating Ubuntu logo is displayed while 
the devices is being flashed.
  With this issue, on the second stage of the flash the phone is stuck on the 
vendor's logo (google or bq) and the rotating ubuntu logo is never displayed.

  Same problem on krillin devel-proposed/krillin.en 235

  Workaround:
  Boot into recovery, mount the system partition and downgrade systemd to 
225-1ubuntu9

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1512323/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1512323] Re: devices on devel-proposed/ubuntu do not boot with systemd 227-2ubuntu1

[Martin Pitt]

> the only place where an unaligned 'out' argument is passed to
siphash24_finalize() in practice is the test case

No, also in networkd. Anyway, fixed upstream in
https://github.com/systemd/systemd/commit/dbe81cbd2a9 . A more robust
fix for the main issue now landed as well (avoiding the malloc, which
wasn't checked and could potentially fail). Upstream master now works
fine on both x86 and ARM.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1512323

Title:
  devices on devel-proposed/ubuntu do not boot with systemd 227-2ubuntu1

Status in Canonical System Image:
  Confirmed
Status in android package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  Last known good build: mako devel-proposed/ubuntu r336

  Affects builds from devel-proposed/ubuntu starting from first Xenial
  build.

  Test Case:
  Boot in fastboot mode and flash with:
  $ ubuntu-device-flash -v touch --channel=ubuntu-touch/devel-proposed/ubuntu 
--bootstrap
  or 
  upgrade from 336 to latest devel-proposed image

  Actual Result
  During a successful flashing operation of a device from fastboot, it boots 
once into recovery, then reboots and a rotating Ubuntu logo is displayed while 
the devices is being flashed.
  With this issue, on the second stage of the flash the phone is stuck on the 
vendor's logo (google or bq) and the rotating ubuntu logo is never displayed.

  Same problem on krillin devel-proposed/krillin.en 235

  Workaround:
  Boot into recovery, mount the system partition and downgrade systemd to 
225-1ubuntu9

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1512323/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1512323] Re: devices on devel-proposed/ubuntu do not boot with systemd 227-2ubuntu1

[Martin Pitt]

No, this was more subtle, its the setting of duid->en.id in
https://github.com/systemd/systemd/commit/dbe81cbd2a9#diff-
893ccaa839a00a7a16a80dbc02631270L54 . This was caught by the two DHCP
test cases. That struct uses ((attribute __packed__)) unions with an
uint32_t preceeding the "id" field, and has an odd address, so is always
unaligned.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1512323

Title:
  devices on devel-proposed/ubuntu do not boot with systemd 227-2ubuntu1

Status in Canonical System Image:
  Confirmed
Status in android package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  Last known good build: mako devel-proposed/ubuntu r336

  Affects builds from devel-proposed/ubuntu starting from first Xenial
  build.

  Test Case:
  Boot in fastboot mode and flash with:
  $ ubuntu-device-flash -v touch --channel=ubuntu-touch/devel-proposed/ubuntu 
--bootstrap
  or 
  upgrade from 336 to latest devel-proposed image

  Actual Result
  During a successful flashing operation of a device from fastboot, it boots 
once into recovery, then reboots and a rotating Ubuntu logo is displayed while 
the devices is being flashed.
  With this issue, on the second stage of the flash the phone is stuck on the 
vendor's logo (google or bq) and the rotating ubuntu logo is never displayed.

  Same problem on krillin devel-proposed/krillin.en 235

  Workaround:
  Boot into recovery, mount the system partition and downgrade systemd to 
225-1ubuntu9

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1512323/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1512323] Re: devices on devel-proposed/ubuntu do not boot with systemd 227-2ubuntu1

[Martin Pitt]

I fixed the unaligned out parameter now in the upstream PR. 228 is
around the corner, so the simplest way would be to let this land
upstream and get fixed through a new upstream version, but if this turns
out to cause further blocking crashes I can also cherry-pick it.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1512323

Title:
  devices on devel-proposed/ubuntu do not boot with systemd 227-2ubuntu1

Status in Canonical System Image:
  Confirmed
Status in android package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  Last known good build: mako devel-proposed/ubuntu r336

  Affects builds from devel-proposed/ubuntu starting from first Xenial
  build.

  Test Case:
  Boot in fastboot mode and flash with:
  $ ubuntu-device-flash -v touch --channel=ubuntu-touch/devel-proposed/ubuntu 
--bootstrap
  or 
  upgrade from 336 to latest devel-proposed image

  Actual Result
  During a successful flashing operation of a device from fastboot, it boots 
once into recovery, then reboots and a rotating Ubuntu logo is displayed while 
the devices is being flashed.
  With this issue, on the second stage of the flash the phone is stuck on the 
vendor's logo (google or bq) and the rotating ubuntu logo is never displayed.

  Same problem on krillin devel-proposed/krillin.en 235

  Workaround:
  Boot into recovery, mount the system partition and downgrade systemd to 
225-1ubuntu9

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1512323/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1512323] Re: devices on devel-proposed/ubuntu do not boot with systemd 227-2ubuntu1

[Martin Pitt]

It's still in siphash, due to a similar problem with the out argument:

0x2a02a9e8 in siphash24_finalize (out=0x2a065229 "", state=0xbefff970) at 
src/basic/siphash24.c:182
182 *(le64_t*)out = htole64(state->v0 ^ state->v1 ^ state->v2  ^ 
state->v3);

I'll follow up on the upstream PR.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1512323

Title:
  devices on devel-proposed/ubuntu do not boot with systemd 227-2ubuntu1

Status in Canonical System Image:
  Confirmed
Status in android package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  Last known good build: mako devel-proposed/ubuntu r336

  Affects builds from devel-proposed/ubuntu starting from first Xenial
  build.

  Test Case:
  Boot in fastboot mode and flash with:
  $ ubuntu-device-flash -v touch --channel=ubuntu-touch/devel-proposed/ubuntu 
--bootstrap
  or 
  upgrade from 336 to latest devel-proposed image

  Actual Result
  During a successful flashing operation of a device from fastboot, it boots 
once into recovery, then reboots and a rotating Ubuntu logo is displayed while 
the devices is being flashed.
  With this issue, on the second stage of the flash the phone is stuck on the 
vendor's logo (google or bq) and the rotating ubuntu logo is never displayed.

  Same problem on krillin devel-proposed/krillin.en 235

  Workaround:
  Boot into recovery, mount the system partition and downgrade systemd to 
225-1ubuntu9

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1512323/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1512323] Re: devices on devel-proposed/ubuntu do not boot with systemd 227-2ubuntu1

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 227-2ubuntu2

---
systemd (227-2ubuntu2) xenial; urgency=medium

  * debian/patches/siphash24-unaligned.patch: fix siphash24
implementation to handle unaligned inputs.  Closes LP: #1512323.

 -- Steve Langasek   Sat, 14 Nov 2015
23:22:39 +

** Changed in: systemd (Ubuntu)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1512323

Title:
  devices on devel-proposed/ubuntu do not boot with systemd 227-2ubuntu1

Status in Canonical System Image:
  Confirmed
Status in android package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  Last known good build: mako devel-proposed/ubuntu r336

  Affects builds from devel-proposed/ubuntu starting from first Xenial
  build.

  Test Case:
  Boot in fastboot mode and flash with:
  $ ubuntu-device-flash -v touch --channel=ubuntu-touch/devel-proposed/ubuntu 
--bootstrap
  or 
  upgrade from 336 to latest devel-proposed image

  Actual Result
  During a successful flashing operation of a device from fastboot, it boots 
once into recovery, then reboots and a rotating Ubuntu logo is displayed while 
the devices is being flashed.
  With this issue, on the second stage of the flash the phone is stuck on the 
vendor's logo (google or bq) and the rotating ubuntu logo is never displayed.

  Same problem on krillin devel-proposed/krillin.en 235

  Workaround:
  Boot into recovery, mount the system partition and downgrade systemd to 
225-1ubuntu9

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1512323/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1512323] Re: devices on devel-proposed/ubuntu do not boot with systemd 227-2ubuntu1

[Martin Pitt]

Thanks Steve for pointing out /proc/cpu/alignment! Yesterday I tried to
reproduce this on an armhf box without success, but with "echo 4 >
/proc/cpu/alignment" this reproduces perfectly  well. I'll  forward your
patch upstream.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1512323

Title:
  devices on devel-proposed/ubuntu do not boot with systemd 227-2ubuntu1

Status in Canonical System Image:
  Confirmed
Status in android package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Fix Committed

Bug description:
  Last known good build: mako devel-proposed/ubuntu r336

  Affects builds from devel-proposed/ubuntu starting from first Xenial
  build.

  Test Case:
  Boot in fastboot mode and flash with:
  $ ubuntu-device-flash -v touch --channel=ubuntu-touch/devel-proposed/ubuntu 
--bootstrap
  or 
  upgrade from 336 to latest devel-proposed image

  Actual Result
  During a successful flashing operation of a device from fastboot, it boots 
once into recovery, then reboots and a rotating Ubuntu logo is displayed while 
the devices is being flashed.
  With this issue, on the second stage of the flash the phone is stuck on the 
vendor's logo (google or bq) and the rotating ubuntu logo is never displayed.

  Same problem on krillin devel-proposed/krillin.en 235

  Workaround:
  Boot into recovery, mount the system partition and downgrade systemd to 
225-1ubuntu9

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1512323/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1512323] Re: devices on devel-proposed/ubuntu do not boot with systemd 227-2ubuntu1

[Martin Pitt]

I cleaned this up a bit and forwarded to
https://github.com/systemd/systemd/pull/1911 .

Without this patch, about a third of the unit tests fail with SIGBUS.
With this fix, only ./test-dhcp{,6}-client still SIGBUS, apparently not
due to siphash24. I'll take a look at this as well.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1512323

Title:
  devices on devel-proposed/ubuntu do not boot with systemd 227-2ubuntu1

Status in Canonical System Image:
  Confirmed
Status in android package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  Last known good build: mako devel-proposed/ubuntu r336

  Affects builds from devel-proposed/ubuntu starting from first Xenial
  build.

  Test Case:
  Boot in fastboot mode and flash with:
  $ ubuntu-device-flash -v touch --channel=ubuntu-touch/devel-proposed/ubuntu 
--bootstrap
  or 
  upgrade from 336 to latest devel-proposed image

  Actual Result
  During a successful flashing operation of a device from fastboot, it boots 
once into recovery, then reboots and a rotating Ubuntu logo is displayed while 
the devices is being flashed.
  With this issue, on the second stage of the flash the phone is stuck on the 
vendor's logo (google or bq) and the rotating ubuntu logo is never displayed.

  Same problem on krillin devel-proposed/krillin.en 235

  Workaround:
  Boot into recovery, mount the system partition and downgrade systemd to 
225-1ubuntu9

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1512323/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1512323] Re: devices on devel-proposed/ubuntu do not boot with systemd 227-2ubuntu1

[Martin Pitt]

** Changed in: systemd (Ubuntu)
   Status: Confirmed => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1512323

Title:
  devices on devel-proposed/ubuntu do not boot with systemd 227-2ubuntu1

Status in Canonical System Image:
  Confirmed
Status in systemd package in Ubuntu:
  In Progress

Bug description:
  Last known good build: mako devel-proposed/ubuntu r336

  Affects builds from devel-proposed/ubuntu starting from first Xenial
  build.

  Test Case:
  Boot in fastboot mode and flash with:
  $ ubuntu-device-flash -v touch --channel=ubuntu-touch/devel-proposed/ubuntu 
--bootstrap
  or 
  upgrade from 336 to latest devel-proposed image

  Actual Result
  During a successful flashing operation of a device from fastboot, it boots 
once into recovery, then reboots and a rotating Ubuntu logo is displayed while 
the devices is being flashed.
  With this issue, on the second stage of the flash the phone is stuck on the 
vendor's logo (google or bq) and the rotating ubuntu logo is never displayed.

  Same problem on krillin devel-proposed/krillin.en 235

  Workaround:
  Boot into recovery, mount the system partition and downgrade systemd to 
225-1ubuntu9

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1512323/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1512323] Re: devices on devel-proposed/ubuntu do not boot with systemd 227-2ubuntu1

[Steve Langasek]

** Also affects: android (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: android (Ubuntu)
   Status: New => Triaged

** Changed in: android (Ubuntu)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1512323

Title:
  devices on devel-proposed/ubuntu do not boot with systemd 227-2ubuntu1

Status in Canonical System Image:
  Confirmed
Status in android package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Fix Committed

Bug description:
  Last known good build: mako devel-proposed/ubuntu r336

  Affects builds from devel-proposed/ubuntu starting from first Xenial
  build.

  Test Case:
  Boot in fastboot mode and flash with:
  $ ubuntu-device-flash -v touch --channel=ubuntu-touch/devel-proposed/ubuntu 
--bootstrap
  or 
  upgrade from 336 to latest devel-proposed image

  Actual Result
  During a successful flashing operation of a device from fastboot, it boots 
once into recovery, then reboots and a rotating Ubuntu logo is displayed while 
the devices is being flashed.
  With this issue, on the second stage of the flash the phone is stuck on the 
vendor's logo (google or bq) and the rotating ubuntu logo is never displayed.

  Same problem on krillin devel-proposed/krillin.en 235

  Workaround:
  Boot into recovery, mount the system partition and downgrade systemd to 
225-1ubuntu9

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1512323/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1512323] Re: devices on devel-proposed/ubuntu do not boot with systemd 227-2ubuntu1

[Steve Langasek]

Bug #1516331 opened against launchpad, to get the buildd behavior
changed to catch issues like this in the future.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1512323

Title:
  devices on devel-proposed/ubuntu do not boot with systemd 227-2ubuntu1

Status in Canonical System Image:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Committed

Bug description:
  Last known good build: mako devel-proposed/ubuntu r336

  Affects builds from devel-proposed/ubuntu starting from first Xenial
  build.

  Test Case:
  Boot in fastboot mode and flash with:
  $ ubuntu-device-flash -v touch --channel=ubuntu-touch/devel-proposed/ubuntu 
--bootstrap
  or 
  upgrade from 336 to latest devel-proposed image

  Actual Result
  During a successful flashing operation of a device from fastboot, it boots 
once into recovery, then reboots and a rotating Ubuntu logo is displayed while 
the devices is being flashed.
  With this issue, on the second stage of the flash the phone is stuck on the 
vendor's logo (google or bq) and the rotating ubuntu logo is never displayed.

  Same problem on krillin devel-proposed/krillin.en 235

  Workaround:
  Boot into recovery, mount the system partition and downgrade systemd to 
225-1ubuntu9

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1512323/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1512323] Re: devices on devel-proposed/ubuntu do not boot with systemd 227-2ubuntu1

[Steve Langasek]

I've assembled a test case for systemd, but I can't get it to fail on
the armhf porter box or under qemu.  Architecture documentation suggests
that unaligned 64-bit reads/writes with ldrd/strd are allowed on ARMv7.
But an unaligned access is still exactly what SIGBUS is supposed to
represent, which leaves it unclear what's happening here.

The crash has been reported to errors.u.c from a variety of devices,
running a variety of kernels; including mako, flo, and some devices not
running phone kernels.

Attaching the disassembly of siphash24_compressed from the udevd in the
archive, for reference.

** Attachment added: "siphash24_compress-broken-disassembly.txt"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1512323/+attachment/4519149/+files/siphash24_compress-broken-disassembly.txt

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1512323

Title:
  devices on devel-proposed/ubuntu do not boot with systemd 227-2ubuntu1

Status in Canonical System Image:
  Confirmed
Status in systemd package in Ubuntu:
  In Progress

Bug description:
  Last known good build: mako devel-proposed/ubuntu r336

  Affects builds from devel-proposed/ubuntu starting from first Xenial
  build.

  Test Case:
  Boot in fastboot mode and flash with:
  $ ubuntu-device-flash -v touch --channel=ubuntu-touch/devel-proposed/ubuntu 
--bootstrap
  or 
  upgrade from 336 to latest devel-proposed image

  Actual Result
  During a successful flashing operation of a device from fastboot, it boots 
once into recovery, then reboots and a rotating Ubuntu logo is displayed while 
the devices is being flashed.
  With this issue, on the second stage of the flash the phone is stuck on the 
vendor's logo (google or bq) and the rotating ubuntu logo is never displayed.

  Same problem on krillin devel-proposed/krillin.en 235

  Workaround:
  Boot into recovery, mount the system partition and downgrade systemd to 
225-1ubuntu9

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1512323/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1512323] Re: devices on devel-proposed/ubuntu do not boot with systemd 227-2ubuntu1

[Steve Langasek]

And here is a disassembly of a locally-built siphash24_compress, built
using the same toolchain as was used for building systemd, which I have
been unable to get to crash with unaligned input.

The code is identical with only differences in the addresses, except for
this rather surprising bit at the end:

 nop
-andeq  r12, r1, r10, lsr #16
-muleq  r1, r4, r9
-andeq  r7, r1, lr, lsr #19
+andeq  r2, r0, r10, ror #25
+   ;  instruction: 0x17b0
+ldrdeq r1, [r0], -r6
 End of assembler dump.
 (gdb) 

Not sure what to make of that.  But the added ldrdeq is in the working
code, not the code that has crashes reported against it; so it doesn't
seem to be relevant.

** Attachment added: "siphash24_compress-working-disassembly.txt"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1512323/+attachment/4519155/+files/siphash24_compress-working-disassembly.txt

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1512323

Title:
  devices on devel-proposed/ubuntu do not boot with systemd 227-2ubuntu1

Status in Canonical System Image:
  Confirmed
Status in systemd package in Ubuntu:
  In Progress

Bug description:
  Last known good build: mako devel-proposed/ubuntu r336

  Affects builds from devel-proposed/ubuntu starting from first Xenial
  build.

  Test Case:
  Boot in fastboot mode and flash with:
  $ ubuntu-device-flash -v touch --channel=ubuntu-touch/devel-proposed/ubuntu 
--bootstrap
  or 
  upgrade from 336 to latest devel-proposed image

  Actual Result
  During a successful flashing operation of a device from fastboot, it boots 
once into recovery, then reboots and a rotating Ubuntu logo is displayed while 
the devices is being flashed.
  With this issue, on the second stage of the flash the phone is stuck on the 
vendor's logo (google or bq) and the rotating ubuntu logo is never displayed.

  Same problem on krillin devel-proposed/krillin.en 235

  Workaround:
  Boot into recovery, mount the system partition and downgrade systemd to 
225-1ubuntu9

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1512323/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1512323] Re: devices on devel-proposed/ubuntu do not boot with systemd 227-2ubuntu1

[Steve Langasek]

Investigation shows that the test case is triggering kernel fix-ups for
unaligned access, as shown by the incrementing counters in
/proc/cpu/alignment on cady.  I'm investigating to see if the phone
kernels have a different default behavior for alignments (SIGBUS vs.
fixup).

So I have a valid test case, it just unfortunately won't block the build
with a test failure on our buildds because the kernel is fixing up the
unaligned access for us.  On other architectures we could build-depend
on and use prctl to force SIGBUS to be raised, but ARM doesn't support
prctl --unaligned.

I have also verified that booting the emulator shows /proc/cpu/alignment
configured for signal (4) instead of fixup (2).  This despite the fact
that CONFIG_ALIGNMENT_TRAP=y is part of the common configuration for
Ubuntu ARM kernels (config/config.common.ubuntu), and is definitely
configured that way at build and runtime in the linux-goldfish package
in the archive.

That means that *something* in the phone stack is changing the value of
/proc/cpu/alignment post-boot.  But I don't know what this "something"
is; there are no matches for /proc/cpu/alignment in /etc on the generic
image, nor in /android.  Google points at it possibly being an android-
inflicted problem. (https://groups.google.com/forum/#!topic/android-
kernel/5vl47DgDz7E)

Now, raising signals on unaligned access is a sensible default behavior.
But we currently have this exactly backwards, because we are fixing up
those unaligned accesses on our build and test infrastructure but have
them causing software failures in production!  Someone from the phone
team should investigate where this wrong setting is coming from and fix
it.

** Changed in: systemd (Ubuntu)
 Assignee: Martin Pitt (pitti) => Steve Langasek (vorlon)

** Changed in: systemd (Ubuntu)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1512323

Title:
  devices on devel-proposed/ubuntu do not boot with systemd 227-2ubuntu1

Status in Canonical System Image:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Committed

Bug description:
  Last known good build: mako devel-proposed/ubuntu r336

  Affects builds from devel-proposed/ubuntu starting from first Xenial
  build.

  Test Case:
  Boot in fastboot mode and flash with:
  $ ubuntu-device-flash -v touch --channel=ubuntu-touch/devel-proposed/ubuntu 
--bootstrap
  or 
  upgrade from 336 to latest devel-proposed image

  Actual Result
  During a successful flashing operation of a device from fastboot, it boots 
once into recovery, then reboots and a rotating Ubuntu logo is displayed while 
the devices is being flashed.
  With this issue, on the second stage of the flash the phone is stuck on the 
vendor's logo (google or bq) and the rotating ubuntu logo is never displayed.

  Same problem on krillin devel-proposed/krillin.en 235

  Workaround:
  Boot into recovery, mount the system partition and downgrade systemd to 
225-1ubuntu9

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1512323/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1512323] Re: devices on devel-proposed/ubuntu do not boot with systemd 227-2ubuntu1

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: systemd (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1512323

Title:
  devices on devel-proposed/ubuntu do not boot with systemd 227-2ubuntu1

Status in Canonical System Image:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Last known good build: mako devel-proposed/ubuntu r336

  Affects builds from devel-proposed/ubuntu starting from first Xenial
  build.

  Test Case:
  Boot in fastboot mode and flash with:
  $ ubuntu-device-flash -v touch --channel=ubuntu-touch/devel-proposed/ubuntu 
--bootstrap
  or 
  upgrade from 336 to latest devel-proposed image

  Actual Result
  During a successful flashing operation of a device from fastboot, it boots 
once into recovery, then reboots and a rotating Ubuntu logo is displayed while 
the devices is being flashed.
  With this issue, on the second stage of the flash the phone is stuck on the 
vendor's logo (google or bq) and the rotating ubuntu logo is never displayed.

  Same problem on krillin devel-proposed/krillin.en 235

  Workaround:
  Boot into recovery, mount the system partition and downgrade systemd to 
225-1ubuntu9

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1512323/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1512323] Re: devices on devel-proposed/ubuntu do not boot with systemd 227-2ubuntu1

[Jean-Baptiste Lallement]

** Description changed:

  Last known good build: mako devel-proposed/ubuntu r336
  
  Affects builds from devel-proposed/ubuntu starting from first Xenial
  build.
  
  Test Case:
  Boot in fastboot mode and flash with:
  $ ubuntu-device-flash -v touch --channel=ubuntu-touch/devel-proposed/ubuntu 
--bootstrap
+ or 
+ upgrade from 336 to latest devel-proposed image
  
  Actual Result
  During a successful flashing operation of a device from fastboot, it boots 
once into recovery, then reboots and a rotating Ubuntu logo is displayed while 
the devices is being flashed.
- With this issue, on the second stage of the flash the phone is stuck on the 
manufacturer's logo (google or bq) and the rotating ubuntu logo is never 
displayed.
+ With this issue, on the second stage of the flash the phone is stuck on the 
vendor's logo (google or bq) and the rotating ubuntu logo is never displayed.
  
  Same problem on krillin devel-proposed/krillin.en 235
+ 
+ Workaround:
+ Boot into recovery, mount the system partition and downgrade systemd to 
225-1ubuntu9

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1512323

Title:
  devices on devel-proposed/ubuntu do not boot with systemd 227-2ubuntu1

Status in Canonical System Image:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  Last known good build: mako devel-proposed/ubuntu r336

  Affects builds from devel-proposed/ubuntu starting from first Xenial
  build.

  Test Case:
  Boot in fastboot mode and flash with:
  $ ubuntu-device-flash -v touch --channel=ubuntu-touch/devel-proposed/ubuntu 
--bootstrap
  or 
  upgrade from 336 to latest devel-proposed image

  Actual Result
  During a successful flashing operation of a device from fastboot, it boots 
once into recovery, then reboots and a rotating Ubuntu logo is displayed while 
the devices is being flashed.
  With this issue, on the second stage of the flash the phone is stuck on the 
vendor's logo (google or bq) and the rotating ubuntu logo is never displayed.

  Same problem on krillin devel-proposed/krillin.en 235

  Workaround:
  Boot into recovery, mount the system partition and downgrade systemd to 
225-1ubuntu9

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1512323/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1512323] Re: devices on devel-proposed/ubuntu do not boot with systemd 227-2ubuntu1

[Jean-Baptiste Lallement]

Crash reports on errors.u.c

systemd-logind: 
https://errors.ubuntu.com/oops/d3f3bbc2-8a16-11e5-8423-fa163e525ba7
systemd-udevd: 
https://errors.ubuntu.com/oops/d265ba26-8a16-11e5-a6d8-fa163e4aaad4
urfkilld: https://errors.ubuntu.com/oops/f0ef4368-8a16-11e5-9c44-fa163e339c81

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1512323

Title:
  devices on devel-proposed/ubuntu do not boot with systemd 227-2ubuntu1

Status in Canonical System Image:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  Last known good build: mako devel-proposed/ubuntu r336

  Affects builds from devel-proposed/ubuntu starting from first Xenial
  build.

  Test Case:
  Boot in fastboot mode and flash with:
  $ ubuntu-device-flash -v touch --channel=ubuntu-touch/devel-proposed/ubuntu 
--bootstrap

  Actual Result
  During a successful flashing operation of a device from fastboot, it boots 
once into recovery, then reboots and a rotating Ubuntu logo is displayed while 
the devices is being flashed.
  With this issue, on the second stage of the flash the phone is stuck on the 
manufacturer's logo (google or bq) and the rotating ubuntu logo is never 
displayed.

  Same problem on krillin devel-proposed/krillin.en 235

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1512323/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1512323] Re: devices on devel-proposed/ubuntu do not boot with systemd 227-2ubuntu1

[Barry Warsaw]

Oh wow, Launchpad just stopped sending me emails on this issue and I got
side tracked on some changes to system-image that I thought might help
debug the problem.  At least it looks like y'all have some good leads on
the root cause though.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1512323

Title:
  devices on devel-proposed/ubuntu do not boot with systemd 227-2ubuntu1

Status in Canonical System Image:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Last known good build: mako devel-proposed/ubuntu r336

  Affects builds from devel-proposed/ubuntu starting from first Xenial
  build.

  Test Case:
  Boot in fastboot mode and flash with:
  $ ubuntu-device-flash -v touch --channel=ubuntu-touch/devel-proposed/ubuntu 
--bootstrap
  or 
  upgrade from 336 to latest devel-proposed image

  Actual Result
  During a successful flashing operation of a device from fastboot, it boots 
once into recovery, then reboots and a rotating Ubuntu logo is displayed while 
the devices is being flashed.
  With this issue, on the second stage of the flash the phone is stuck on the 
vendor's logo (google or bq) and the rotating ubuntu logo is never displayed.

  Same problem on krillin devel-proposed/krillin.en 235

  Workaround:
  Boot into recovery, mount the system partition and downgrade systemd to 
225-1ubuntu9

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1512323/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1512323] Re: devices on devel-proposed/ubuntu do not boot with systemd 227-2ubuntu1

[Steve Langasek]

Martin, it looks like we have a critical regression in systemd for the
phone in xenial (which of course didn't stop in xenial-proposed now that
we have no automated phone boot tests).  Please look at this ASAP.

** Changed in: systemd (Ubuntu)
 Assignee: (unassigned) => Martin Pitt (pitti)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1512323

Title:
  devices on devel-proposed/ubuntu do not boot with systemd 227-2ubuntu1

Status in Canonical System Image:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  Last known good build: mako devel-proposed/ubuntu r336

  Affects builds from devel-proposed/ubuntu starting from first Xenial
  build.

  Test Case:
  Boot in fastboot mode and flash with:
  $ ubuntu-device-flash -v touch --channel=ubuntu-touch/devel-proposed/ubuntu 
--bootstrap

  Actual Result
  During a successful flashing operation of a device from fastboot, it boots 
once into recovery, then reboots and a rotating Ubuntu logo is displayed while 
the devices is being flashed.
  With this issue, on the second stage of the flash the phone is stuck on the 
manufacturer's logo (google or bq) and the rotating ubuntu logo is never 
displayed.

  Same problem on krillin devel-proposed/krillin.en 235

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1512323/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1512323] Re: devices on devel-proposed/ubuntu do not boot with systemd 227-2ubuntu1

[Steve Langasek]

stack trace points at new hashtable functionality within systemd.

The crash shows udevd is crashing with SIGBUS.

The new siphash24.c code is full of dereferences of uint8_t types that
are then being handled as uint64_t values, as in le64toh() which is
defined as:

static inline uint64_t le64toh(le64_t value) { return
bswap_64_on_be((uint64_t __force)value); }

There is nothing in this code that guarantees 64-bit alignment of the
source pointer.  Dereferencing an unaligned pointer as a 64-bit int is
non-portable, and it's precisely a SIGBUS that is raised in the case of
unaligned access.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1512323

Title:
  devices on devel-proposed/ubuntu do not boot with systemd 227-2ubuntu1

Status in Canonical System Image:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Last known good build: mako devel-proposed/ubuntu r336

  Affects builds from devel-proposed/ubuntu starting from first Xenial
  build.

  Test Case:
  Boot in fastboot mode and flash with:
  $ ubuntu-device-flash -v touch --channel=ubuntu-touch/devel-proposed/ubuntu 
--bootstrap
  or 
  upgrade from 336 to latest devel-proposed image

  Actual Result
  During a successful flashing operation of a device from fastboot, it boots 
once into recovery, then reboots and a rotating Ubuntu logo is displayed while 
the devices is being flashed.
  With this issue, on the second stage of the flash the phone is stuck on the 
vendor's logo (google or bq) and the rotating ubuntu logo is never displayed.

  Same problem on krillin devel-proposed/krillin.en 235

  Workaround:
  Boot into recovery, mount the system partition and downgrade systemd to 
225-1ubuntu9

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1512323/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1512323] Re: devices on devel-proposed/ubuntu do not boot with systemd 227-2ubuntu1

[Steve Langasek]

In the failing case, the argument to le64toh() is a result returned by
basename().  Yeah, no guarantee of alignment >= 1 byte when taking a
pointer into the middle of a filename.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1512323

Title:
  devices on devel-proposed/ubuntu do not boot with systemd 227-2ubuntu1

Status in Canonical System Image:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Last known good build: mako devel-proposed/ubuntu r336

  Affects builds from devel-proposed/ubuntu starting from first Xenial
  build.

  Test Case:
  Boot in fastboot mode and flash with:
  $ ubuntu-device-flash -v touch --channel=ubuntu-touch/devel-proposed/ubuntu 
--bootstrap
  or 
  upgrade from 336 to latest devel-proposed image

  Actual Result
  During a successful flashing operation of a device from fastboot, it boots 
once into recovery, then reboots and a rotating Ubuntu logo is displayed while 
the devices is being flashed.
  With this issue, on the second stage of the flash the phone is stuck on the 
vendor's logo (google or bq) and the rotating ubuntu logo is never displayed.

  Same problem on krillin devel-proposed/krillin.en 235

  Workaround:
  Boot into recovery, mount the system partition and downgrade systemd to 
225-1ubuntu9

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1512323/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1512323] Re: devices on devel-proposed/ubuntu do not boot with systemd 227-2ubuntu1

[Steve Langasek]

Well, no guarantee of alignment > 1 byte.  There is a guarantee of 1
byte alignment.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1512323

Title:
  devices on devel-proposed/ubuntu do not boot with systemd 227-2ubuntu1

Status in Canonical System Image:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Last known good build: mako devel-proposed/ubuntu r336

  Affects builds from devel-proposed/ubuntu starting from first Xenial
  build.

  Test Case:
  Boot in fastboot mode and flash with:
  $ ubuntu-device-flash -v touch --channel=ubuntu-touch/devel-proposed/ubuntu 
--bootstrap
  or 
  upgrade from 336 to latest devel-proposed image

  Actual Result
  During a successful flashing operation of a device from fastboot, it boots 
once into recovery, then reboots and a rotating Ubuntu logo is displayed while 
the devices is being flashed.
  With this issue, on the second stage of the flash the phone is stuck on the 
vendor's logo (google or bq) and the rotating ubuntu logo is never displayed.

  Same problem on krillin devel-proposed/krillin.en 235

  Workaround:
  Boot into recovery, mount the system partition and downgrade systemd to 
225-1ubuntu9

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1512323/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp