[Touch-packages] [Bug 1472650] Re: [arm64] gccgo runtime crashes with CONFIG_ARM64_PGTABLE_LEVELS=4

[Anastasia]

>From mwhudson: we don't use gccgo on arm64 any more.

** Changed in: juju-core (Ubuntu)
   Status: Triaged => Invalid

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

Title:
  [arm64] gccgo runtime crashes with CONFIG_ARM64_PGTABLE_LEVELS=4

Status in gcc:
  Unknown
Status in gcc-5 package in Ubuntu:
  Fix Released
Status in gccgo-4.9 package in Ubuntu:
  Invalid
Status in gccgo-5 package in Ubuntu:
  Invalid
Status in juju-core package in Ubuntu:
  Invalid
Status in gccgo-4.9 source package in Trusty:
  Fix Released
Status in gccgo-4.9 source package in Vivid:
  Invalid
Status in gccgo-5 source package in Vivid:
  Fix Released
Status in gccgo-4.9 source package in Wily:
  Invalid

Bug description:
  [Impact]
  Various go-based packages crash on startup on arm64 when booted with a kernel 
where CONFIG_ARM64_PGTABLE_LEVELS=4. LXD, docker and juju are examples.

  Ubuntu does not ship with this config, so it is currently not
  impacted. However, we would like to enable this config to add new
  hardware support in 15.10. The 15.10 kernel will eventually be
  provided in trusty as an lts backport, at which point this will begin
  to break users.

  [Test Case]
  Boot an arm64 system with CONFIG_ARM64_PGTABLE_LEVELS=4 enabled in the 
kernel. Install docker.io and run "docker help". If it fails, you'll see "fatal 
error: runtime_lfstackpush" followed by a stack trace. If it succeeds, you'll 
get normal help output.

  [Regression Risk]
  The risk of regression is lessened by testing this release on existing Ubuntu 
kernels w/ 3 level page tables.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gcc/+bug/1472650/+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 1472650] Re: [arm64] gccgo runtime crashes with CONFIG_ARM64_PGTABLE_LEVELS=4

[Launchpad Bug Tracker]

** Branch linked: lp:ubuntu/trusty-proposed/gccgo-4.9

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

Title:
  [arm64] gccgo runtime crashes with CONFIG_ARM64_PGTABLE_LEVELS=4

Status in gcc:
  Unknown
Status in gcc-5 package in Ubuntu:
  Fix Released
Status in gccgo-4.9 package in Ubuntu:
  Invalid
Status in gccgo-5 package in Ubuntu:
  Invalid
Status in juju-core package in Ubuntu:
  Triaged
Status in gccgo-4.9 source package in Trusty:
  Fix Released
Status in gccgo-4.9 source package in Vivid:
  Invalid
Status in gccgo-5 source package in Vivid:
  Fix Released
Status in gccgo-4.9 source package in Wily:
  Invalid

Bug description:
  [Impact]
  Various go-based packages crash on startup on arm64 when booted with a kernel 
where CONFIG_ARM64_PGTABLE_LEVELS=4. LXD, docker and juju are examples.

  Ubuntu does not ship with this config, so it is currently not
  impacted. However, we would like to enable this config to add new
  hardware support in 15.10. The 15.10 kernel will eventually be
  provided in trusty as an lts backport, at which point this will begin
  to break users.

  [Test Case]
  Boot an arm64 system with CONFIG_ARM64_PGTABLE_LEVELS=4 enabled in the 
kernel. Install docker.io and run "docker help". If it fails, you'll see "fatal 
error: runtime_lfstackpush" followed by a stack trace. If it succeeds, you'll 
get normal help output.

  [Regression Risk]
  The risk of regression is lessened by testing this release on existing Ubuntu 
kernels w/ 3 level page tables.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gcc/+bug/1472650/+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 1472650] Re: [arm64] gccgo runtime crashes with CONFIG_ARM64_PGTABLE_LEVELS=4

[dann frazier]

Marking as impacting juju-core/trusty. This is easily reproduced by
attempting to bootstrap a juju-local environment in trusty with juju-
core 1.24.7-0ubuntu1~14.04.1 when using a kernel w/ 4 level page tables.
This will be a supported config once the xenial-lts kernel is available
in trusty.

A no-change rebuild of juju-core trusty would be sufficient to resolve
this issue.


ubuntu@cvm2s2:~$ juju bootstrap --verbose
Bootstrapping environment "local"
Starting new instance for initial state server
Building tools to upload (1.24.7.1-trusty-arm64)
Bootstrap failed, destroying environment
ERROR failed to bootstrap environment: cannot upload bootstrap tools: cannot 
get version from "/tmp/juju-tools525417221/jujud": exit status 2; 
p=0x9354f000
fatal error: runtime_lfstackpush: invalid pointer

runtime stack:

:0

:0

:0

:0

:0

:0

:0

:0

:0

:0

goroutine 1 [garbage collection]:
github.com_juju_cmd.DefaultContext

/build/juju-core-qiO5uV/juju-core-1.24.7/src/github.com/juju/cmd/cmd.go:261
main.Main

/build/juju-core-qiO5uV/juju-core-1.24.7/src/github.com/juju/juju/cmd/jujud/main.go:166
main.MainWrapper

/build/juju-core-qiO5uV/juju-core-1.24.7/src/github.com/juju/juju/cmd/jujud/main.go:151
main.main

/build/juju-core-qiO5uV/juju-core-1.24.7/src/github.com/juju/juju/cmd/jujud/main_nix.go:13

goroutine 3 [syscall]:
goroutine in C code; stack unavailable


** Also affects: juju-core (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: juju-core (Ubuntu)
   Status: New => Triaged

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

Title:
  [arm64] gccgo runtime crashes with CONFIG_ARM64_PGTABLE_LEVELS=4

Status in gcc:
  Unknown
Status in gcc-5 package in Ubuntu:
  Fix Released
Status in gccgo-4.9 package in Ubuntu:
  Invalid
Status in gccgo-5 package in Ubuntu:
  Invalid
Status in juju-core package in Ubuntu:
  Triaged
Status in gccgo-4.9 source package in Trusty:
  Fix Released
Status in gccgo-4.9 source package in Vivid:
  Invalid
Status in gccgo-5 source package in Vivid:
  Fix Released
Status in gccgo-4.9 source package in Wily:
  Invalid

Bug description:
  [Impact]
  Various go-based packages crash on startup on arm64 when booted with a kernel 
where CONFIG_ARM64_PGTABLE_LEVELS=4. LXD, docker and juju are examples.

  Ubuntu does not ship with this config, so it is currently not
  impacted. However, we would like to enable this config to add new
  hardware support in 15.10. The 15.10 kernel will eventually be
  provided in trusty as an lts backport, at which point this will begin
  to break users.

  [Test Case]
  Boot an arm64 system with CONFIG_ARM64_PGTABLE_LEVELS=4 enabled in the 
kernel. Install docker.io and run "docker help". If it fails, you'll see "fatal 
error: runtime_lfstackpush" followed by a stack trace. If it succeeds, you'll 
get normal help output.

  [Regression Risk]
  The risk of regression is lessened by testing this release on existing Ubuntu 
kernels w/ 3 level page tables.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gcc/+bug/1472650/+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 1472650] Re: [arm64] gccgo runtime crashes with CONFIG_ARM64_PGTABLE_LEVELS=4

[Launchpad Bug Tracker]

This bug was fixed in the package gccgo-4.9 - 4.9.3-0ubuntu4

---
gccgo-4.9 (4.9.3-0ubuntu4) trusty-proposed; urgency=medium

  * Upload the final GCC 4.9.3 release.
  * Merge changes from gcc-4.9 4.9.3-2ubuntu1, including:
- Fix PR go/60931, garbage collector issue with non 4kB system page size.
  LP: #1304754.
- Fix wrong-code issue in the little endian vector API (ppc64el).
  LP: #1311128.
- Fix ABI incompatibility between POWER and Z HTM builtins and intrinsics.
  LP: #1320292.
- Fix an ICE with invalid code. PR c++/61046. LP: #1313102.
- gccgo: Don't overwrite memory if an archive has a bad file name.
- Fix PR rtl-optimization/61801, sched2 miscompiles syscall sequence with 
-g.
- libgo: Fix unexpected GC interfering with closure passing.
- libgo: Fix PR other/61895, ignore small argv[0] file for backtrace.
- libgo: Fix unexpected GC interfering with closure passing.
- Fix ICE in the Go frontend. LP: #1362906.
- Enable cgo on AArch64 (Michael Hudson). LP: #1361940.
- libgo: runtime: Use the clone system call on GNU/Linux.
- libgo: Support arm64 relocations (Michael Hudson).
  * Include the cc1 binary into the gccgo-4.9 package.
  * Do not build-depend on sdt-systemtap for the trusty upload.
  * Warn about ppc ELFv2 ABI issues, which will change in GCC 5.
  * libgo: Fix PR go/67508, rewrite lfstack packing/unpacking to look more
like that in Go (Michael Hudson). LP: #1472650.

gcc-4.9 (4.9.3-2ubuntu1) wily; urgency=medium

  * Merge with Debian; remaining changes:
- Build from upstream sources.

gcc-4.9 (4.9.3-2) unstable; urgency=medium

  * Update to SVN 20150714 (r225765) from the gcc-4_9-branch.
  * Update the Linaro support to the 4.9-2015.06 release.

gcc-4.9 (4.9.3-1ubuntu1) wily; urgency=medium

  * Merge with Debian; remaining changes:
- Build from upstream sources.

gcc-4.9 (4.9.3-1) unstable; urgency=medium

  * GCC 4.9.3 release.
  * Update to SVN 20150629 (r225135) from the gcc-4_9-branch.
  * Refresh patches.

gcc-4.9 (4.9.2-22ubuntu1) wily; urgency=medium

  * Merge with Debian; remaining changes:
- Build from upstream sources.

gcc-4.9 (4.9.2-22) unstable; urgency=medium

  * Update to SVN 20150623 (r224833) from the gcc-4_9-branch.
  * Fix PR target/66483, taken from the trunk. Closes: #787689.
  * Fix "empty-binary-package" lintian warnings.
  * Fix PR tree-optimization/66233. Closes: #788812.

gcc-4.9 (4.9.2-21) unstable; urgency=medium

  * Update to SVN 20150611 (r224436) from the gcc-4_9-branch.
  * Build libstdc++6 when building the common libraries.

gcc-4.9 (4.9.2-20ubuntu1) wily; urgency=medium

  * Merge with Debian; remaining changes:
- Build from upstream sources.

gcc-4.9 (4.9.2-20) unstable; urgency=medium

  * Update to SVN 20150531 (r223898) from the gcc-4_9-branch.
  * Fix PR rtl-optimization/63843, taken from the trunk. Closes: #785475.

gcc-4.9 (4.9.2-19ubuntu1) wily; urgency=medium

  * Merge with Debian; remaining changes:
- Build from upstream sources.

gcc-4.9 (4.9.2-19) unstable; urgency=medium

  * Update to SVN 20150529 (r223861) from the gcc-4_9-branch.
  * Make symbols file symlinking for cross builds more robust.
  * Fix building cross compilers with dpkg 1.18.
  * Stop building the common libraries on m68k.
  * Disable building gdc on sh4 (bootstrap comparison failure).
  * gcc-4.9-base: Adjust gnat breaks attribute to better support
upgrades to jessie (Andreas Beckmann). Closes: #779876.

gcc-4.9 (4.9.2-18ubuntu1) wily; urgency=medium

  * Merge with Debian; remaining changes:
- Build from upstream sources.

gcc-4.9 (4.9.2-18) unstable; urgency=medium

  * Update to SVN 20150518 (r223293) from the gcc-4_9-branch.
  * Remove work arounds to build 64bit multilibs on 32bit targets,
now properly fixed upstream.
  * Re-enable running the tests.
  * Disable running the libstdc++ tests with the installed libstdc++.
Doesn't make sense anymore with the dual-abi libstdc++ from GCC 5.

gcc-4.9 (4.9.2-17ubuntu1) wily; urgency=medium

  * Merge with Debian; remaining changes:
- Build from upstream sources.

gcc-4.9 (4.9.2-17) unstable; urgency=medium

  * Update to SVN 20150516 (r223238) from the gcc-4_9-branch.
  * Again, configure with --enable-targets=powerpcle-linux on ppc64el.
Closes: #785066.
  * Remove old CFLAGS/LDFLAGS settings to build gdc.
  * Remove reference to .ico file in NEWS.html.
  * Fix -base dependency for the gcj cross packages.

gcc-4.9 (4.9.2-16ubuntu1) wily; urgency=medium

  * Update to SVN 20150508 (r222909) from the gcc-4_9-branch.

gcc-4.9 (4.9.2-16) unstable; urgency=medium

  * Update to SVN 20150503 (r222750) from the gcc-4_9-branch.
- Fix the build failure on alpha.
  * Fix gcc-itm doc-base file (Guo Yixuan). Closes: #783998.
  * On m68k, powerpcspe, sh4, sparc64, still build the libraries not
yet built by gcc-5.
  * Update the cross-biarch patch for D and Go.
  * Apply the cross-biarch patches for every 

[Touch-packages] [Bug 1472650] Re: [arm64] gccgo runtime crashes with CONFIG_ARM64_PGTABLE_LEVELS=4

[dann frazier]

Verified:

ubuntu@cvm2s:~$ juju help
p=0xa6947000
fatal error: runtime_lfstackpush: invalid pointer

runtime stack:

:0

:0

:0

:0

:0

:0

:0

:0

:0

:0

goroutine 1 [garbage collection]:
github.com_juju_cmd.DefaultContext

/build/juju-core-qiO5uV/juju-core-1.24.7/src/github.com/juju/cmd/cmd.go:261
main.Main

/build/juju-core-qiO5uV/juju-core-1.24.7/src/github.com/juju/juju/cmd/juju/main.go:54
main.main

/build/juju-core-qiO5uV/juju-core-1.24.7/src/github.com/juju/juju/cmd/juju/main.go:233

goroutine 3 [syscall]:
goroutine in C code; stack unavailable

goroutine 12 [runnable]:
ubuntu@cvm2s:~$ sudo apt-get install libgo5 -y
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following packages were automatically installed and are no longer required:
  devio libuuid-perl linux-base
Use 'apt-get autoremove' to remove them.
The following extra packages will be installed:
  gcc-4.9-base libgcc1
The following packages will be upgraded:
  gcc-4.9-base libgcc1 libgo5
3 upgraded, 0 newly installed, 0 to remove and 17 not upgraded.
Need to get 2,337 kB of archives.
After this operation, 17.4 kB of additional disk space will be used.
Get:1 http://ports.ubuntu.com/ubuntu-ports/ trusty-proposed/main libgo5 arm64 
4.9.3-0ubuntu4 [2,291 kB]
Get:2 http://ports.ubuntu.com/ubuntu-ports/ trusty-proposed/main gcc-4.9-base 
arm64 4.9.3-0ubuntu4 [15.2 kB]
Get:3 http://ports.ubuntu.com/ubuntu-ports/ trusty-proposed/main libgcc1 arm64 
1:4.9.3-0ubuntu4 [30.7 kB]
Fetched 2,337 kB in 11s (212 kB/s) 
(Reading database ... 70242 files and directories currently installed.)
Preparing to unpack .../libgo5_4.9.3-0ubuntu4_arm64.deb ...
Unpacking libgo5:arm64 (4.9.3-0ubuntu4) over (4.9.1-0ubuntu1) ...
Preparing to unpack .../gcc-4.9-base_4.9.3-0ubuntu4_arm64.deb ...
Unpacking gcc-4.9-base:arm64 (4.9.3-0ubuntu4) over (4.9.1-0ubuntu1) ...
Setting up gcc-4.9-base:arm64 (4.9.3-0ubuntu4) ...
(Reading database ... 70242 files and directories currently installed.)
Preparing to unpack .../libgcc1_1%3a4.9.3-0ubuntu4_arm64.deb ...
Unpacking libgcc1:arm64 (1:4.9.3-0ubuntu4) over (1:4.9.1-0ubuntu1) ...
Setting up libgcc1:arm64 (1:4.9.3-0ubuntu4) ...
Setting up libgo5:arm64 (4.9.3-0ubuntu4) ...
Processing triggers for libc-bin (2.19-0ubuntu6.6) ...
ubuntu@cvm2s:~$ juju help
Juju -- devops distilled
https://juju.ubuntu.com/

Juju provides easy, intelligent service orchestration on top of environments
such as Amazon EC2, HP Cloud, OpenStack, MaaS, or your own local machine.

Basic commands:
  juju init generate boilerplate configuration for juju environments
  juju bootstrapstart up an environment from scratch

  juju deploy   deploy a new service
  juju add-relation add a relation between two services
  juju expose   expose a service

  juju help bootstrap   more help on e.g. bootstrap command
  juju help commandslist all commands
  juju help glossaryglossary of terms
  juju help topics  list all help topics

Provider information:
  juju help azure-provider   use on Windows Azure
  juju help ec2-provider use on Amazon EC2
  juju help hpcloud-provider use on HP Cloud
  juju help local-provider   use on this computer
  juju help openstack-provider   use on OpenStack


** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  [arm64] gccgo runtime crashes with CONFIG_ARM64_PGTABLE_LEVELS=4

Status in gcc:
  Unknown
Status in gcc-5 package in Ubuntu:
  Fix Released
Status in gccgo-4.9 package in Ubuntu:
  Invalid
Status in gccgo-5 package in Ubuntu:
  Invalid
Status in gccgo-4.9 source package in Trusty:
  Fix Committed
Status in gccgo-4.9 source package in Vivid:
  Invalid
Status in gccgo-5 source package in Vivid:
  Fix Released
Status in gccgo-4.9 source package in Wily:
  Invalid

Bug description:
  [Impact]
  Various go-based packages crash on startup on arm64 when booted with a kernel 
where CONFIG_ARM64_PGTABLE_LEVELS=4. LXD, docker and juju are examples.

  Ubuntu does not ship with this config, so it is currently not
  impacted. However, we would like to enable this config to add new
  hardware support in 15.10. The 15.10 kernel will eventually be
  provided in trusty as an lts backport, at which point this will begin
  to break users.

  [Test Case]
  Boot an arm64 system with CONFIG_ARM64_PGTABLE_LEVELS=4 enabled in the 
kernel. Install docker.io and run "docker help". If it fails, you'll see "fatal 
error: runtime_lfstackpush" followed by a stack trace. If it succeeds, you'll 
get normal help output.

  [Regression Risk]
  The risk of regression is lessened by 

[Touch-packages] [Bug 1472650] Re: [arm64] gccgo runtime crashes with CONFIG_ARM64_PGTABLE_LEVELS=4

[Steve Langasek]

Hello dann, or anyone else affected,

Accepted gccgo-4.9 into trusty-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/gccgo-4.9/4.9.3-0ubuntu4 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: gccgo-4.9 (Ubuntu Trusty)
   Status: In Progress => Fix Committed

** Tags removed: verification-done

** Tags added: verification-needed

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

Title:
  [arm64] gccgo runtime crashes with CONFIG_ARM64_PGTABLE_LEVELS=4

Status in gcc:
  Unknown
Status in gcc-5 package in Ubuntu:
  Fix Released
Status in gccgo-4.9 package in Ubuntu:
  Invalid
Status in gccgo-5 package in Ubuntu:
  Invalid
Status in gccgo-4.9 source package in Trusty:
  Fix Committed
Status in gccgo-4.9 source package in Vivid:
  Invalid
Status in gccgo-5 source package in Vivid:
  Fix Released
Status in gccgo-4.9 source package in Wily:
  Invalid

Bug description:
  [Impact]
  Various go-based packages crash on startup on arm64 when booted with a kernel 
where CONFIG_ARM64_PGTABLE_LEVELS=4. LXD, docker and juju are examples.

  Ubuntu does not ship with this config, so it is currently not
  impacted. However, we would like to enable this config to add new
  hardware support in 15.10. The 15.10 kernel will eventually be
  provided in trusty as an lts backport, at which point this will begin
  to break users.

  [Test Case]
  Boot an arm64 system with CONFIG_ARM64_PGTABLE_LEVELS=4 enabled in the 
kernel. Install docker.io and run "docker help". If it fails, you'll see "fatal 
error: runtime_lfstackpush" followed by a stack trace. If it succeeds, you'll 
get normal help output.

  [Regression Risk]
  The risk of regression is lessened by testing this release on existing Ubuntu 
kernels w/ 3 level page tables.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gcc/+bug/1472650/+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 1472650] Re: [arm64] gccgo runtime crashes with CONFIG_ARM64_PGTABLE_LEVELS=4

[Launchpad Bug Tracker]

This bug was fixed in the package gccgo-5 - 5.1~rc1-0ubuntu1.1

---
gccgo-5 (5.1~rc1-0ubuntu1.1) vivid; urgency=medium

  * libgo: Fix PR go/67508, rewrite lfstack packing/unpacking to look more
like that in Go (Michael Hudson). LP: #1472650.

 -- dann frazier   Wed, 16 Sep 2015 13:56:48 +

** Changed in: gccgo-5 (Ubuntu Vivid)
   Status: Fix Committed => Fix Released

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

Title:
  [arm64] gccgo runtime crashes with CONFIG_ARM64_PGTABLE_LEVELS=4

Status in gcc:
  Unknown
Status in gcc-5 package in Ubuntu:
  Fix Released
Status in gccgo-4.9 package in Ubuntu:
  Invalid
Status in gccgo-5 package in Ubuntu:
  Invalid
Status in gccgo-4.9 source package in Trusty:
  In Progress
Status in gccgo-4.9 source package in Vivid:
  Invalid
Status in gccgo-5 source package in Vivid:
  Fix Released
Status in gccgo-4.9 source package in Wily:
  Invalid

Bug description:
  [Impact]
  Various go-based packages crash on startup on arm64 when booted with a kernel 
where CONFIG_ARM64_PGTABLE_LEVELS=4. LXD, docker and juju are examples.

  Ubuntu does not ship with this config, so it is currently not
  impacted. However, we would like to enable this config to add new
  hardware support in 15.10. The 15.10 kernel will eventually be
  provided in trusty as an lts backport, at which point this will begin
  to break users.

  [Test Case]
  Boot an arm64 system with CONFIG_ARM64_PGTABLE_LEVELS=4 enabled in the 
kernel. Install docker.io and run "docker help". If it fails, you'll see "fatal 
error: runtime_lfstackpush" followed by a stack trace. If it succeeds, you'll 
get normal help output.

  [Regression Risk]
  The risk of regression is lessened by testing this release on existing Ubuntu 
kernels w/ 3 level page tables.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gcc/+bug/1472650/+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 1472650] Re: [arm64] gccgo runtime crashes with CONFIG_ARM64_PGTABLE_LEVELS=4

[dann frazier]

= vivid verification =

# My kernel has the problematic config
ubuntu@cvm1:~$ grep CONFIG_ARM64_PGTABLE_LEVELS /boot/config-$(uname -r)
CONFIG_ARM64_PGTABLE_LEVELS=4

# Build a clean vivid chroot
ubuntu@cvm1:~$ mkdir lp1472650
ubuntu@cvm1:~$ sudo debootstrap --components 'main,universe' --include 
docker.io vivid lp1472650 http://ports.ubuntu.com/ubuntu-ports > /dev/null 2>&1

# docker needs proc to be mounted
ubuntu@cvm1:~$ sudo mount proc lp1472650/proc -t proc
ubuntu@cvm1:~$ sudo chroot lp1472650 docker help
p=0x88459000
fatal error: runtime_lfstackpush: invalid pointer
[--trim--]

# It's buggy. Let's install the gccgo update
ubuntu@cvm1:~$ echo 'deb http://ports.ubuntu.com/ubuntu-ports vivid-proposed 
main universe' | sudo tee -a lp1472650/etc/apt/sources.list > /dev/null
ubuntu@cvm1:~$ sudo chroot lp1472650 apt-get update > /dev/null 2>&1
ubuntu@cvm1:~$ sudo chroot lp1472650 apt-get install libgo7
Reading package lists... Done
Building dependency tree... Done
The following extra packages will be installed:
  gcc-5-base libgcc1
The following packages will be upgraded:
  gcc-5-base libgcc1 libgo7
3 upgraded, 0 newly installed, 0 to remove and 8 not upgraded.
Need to get 6243 kB of archives.
After this operation, 2048 B of additional disk space will be used.
Do you want to continue? [Y/n] 
Get:1 http://ports.ubuntu.com/ubuntu-ports/ vivid-proposed/universe libgo7 
arm64 5.1~rc1-0ubuntu1.1 [6198 kB]
Get:2 http://ports.ubuntu.com/ubuntu-ports/ vivid-proposed/main gcc-5-base 
arm64 5.1~rc1-0ubuntu1.1 [14.4 kB]
Get:3 http://ports.ubuntu.com/ubuntu-ports/ vivid-proposed/main libgcc1 arm64 
1:5.1~rc1-0ubuntu1.1 [31.0 kB]
Fetched 4733 kB in 28s (166 kB/s)   
  
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = (unset),
LC_ALL = (unset),
LANG = "en_US.UTF-8"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
E: Can not write log (Is /dev/pts mounted?) - posix_openpt (2: No such file or 
directory)
(Reading database ... 11950 files and directories currently installed.)
Preparing to unpack .../libgo7_5.1~rc1-0ubuntu1.1_arm64.deb ...
Unpacking libgo7:arm64 (5.1~rc1-0ubuntu1.1) over (5.1~rc1-0ubuntu1) ...
Preparing to unpack .../gcc-5-base_5.1~rc1-0ubuntu1.1_arm64.deb ...
Unpacking gcc-5-base:arm64 (5.1~rc1-0ubuntu1.1) over (5.1~rc1-0ubuntu1) ...
Setting up gcc-5-base:arm64 (5.1~rc1-0ubuntu1.1) ...
(Reading database ... 11950 files and directories currently installed.)
Preparing to unpack .../libgcc1_1%3a5.1~rc1-0ubuntu1.1_arm64.deb ...
Unpacking libgcc1:arm64 (1:5.1~rc1-0ubuntu1.1) over (1:5.1~rc1-0ubuntu1) ...
Setting up libgcc1:arm64 (1:5.1~rc1-0ubuntu1.1) ...
Setting up libgo7:arm64 (5.1~rc1-0ubuntu1.1) ...
Processing triggers for libc-bin (2.21-0ubuntu4) ...
ubuntu@cvm1:~$ sudo chroot lp1472650 docker help
Usage: docker [OPTIONS] COMMAND [arg...]

A self-sufficient runtime for linux containers.

[--trim--]

# It works now.
# I also noticed that there's a docker update in vivid-proposed.
# Let's make sure that works too:
ubuntu@cvm1:~$ sudo chroot lp1472650 apt-get dist-upgrade -y
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
  apt apt-utils docker.io libapt-inst1.5 libapt-pkg4.12 login ntpdate passwd
8 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 9139 kB/9437 kB of archives.
After this operation, 1219 kB of additional disk space will be used.
Get:1 http://ports.ubuntu.com/ubuntu-ports/ vivid-proposed/main libapt-pkg4.12 
arm64 1.0.9.7ubuntu4.2 [618 kB]
Get:2 http://ports.ubuntu.com/ubuntu-ports/ vivid-proposed/main apt arm64 
1.0.9.7ubuntu4.2 [976 kB]
Get:3 http://ports.ubuntu.com/ubuntu-ports/ vivid-proposed/main libapt-inst1.5 
arm64 1.0.9.7ubuntu4.2 [57.5 kB]
Get:4 http://ports.ubuntu.com/ubuntu-ports/ vivid-proposed/main ntpdate arm64 
1:4.2.6.p5+dfsg-3ubuntu6.1 [50.1 kB]
Get:5 http://ports.ubuntu.com/ubuntu-ports/ vivid-proposed/main passwd arm64 
1:4.1.5.1-1.1ubuntu4.1 [728 kB]
Get:6 http://ports.ubuntu.com/ubuntu-ports/ vivid-proposed/main apt-utils arm64 
1.0.9.7ubuntu4.2 [172 kB]
Get:7 http://ports.ubuntu.com/ubuntu-ports/ vivid-proposed/universe docker.io 
arm64 1.6.2~dfsg1-1ubuntu3~15.04.1 [6536 kB]
Fetched 9139 kB in 51s (176 kB/s)   
  
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = (unset),
LC_ALL = (unset),
LANG = "en_US.UTF-8"
are supported and installed on your system.
perl: warning: Falling back to the 

[Touch-packages] [Bug 1472650] Re: [arm64] gccgo runtime crashes with CONFIG_ARM64_PGTABLE_LEVELS=4

[dann frazier]

** Changed in: gccgo-4.9 (Ubuntu Vivid)
   Status: New => In Progress

** Changed in: gccgo-4.9 (Ubuntu Trusty)
   Status: Confirmed => Invalid

** Changed in: gccgo-4.9 (Ubuntu Trusty)
   Status: Invalid => In Progress

** Changed in: gccgo-4.9 (Ubuntu Vivid)
   Status: In Progress => Invalid

** Changed in: gccgo-4.9 (Ubuntu Wily)
   Status: New => Invalid

** Changed in: gccgo-5 (Ubuntu Vivid)
   Status: New => In Progress

** Changed in: gccgo-5 (Ubuntu)
   Status: New => Invalid

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

Title:
  [arm64] gccgo runtime crashes with CONFIG_ARM64_PGTABLE_LEVELS=4

Status in gcc:
  Unknown
Status in gcc-5 package in Ubuntu:
  Fix Released
Status in gccgo-4.9 package in Ubuntu:
  Invalid
Status in gccgo-5 package in Ubuntu:
  Invalid
Status in gccgo-4.9 source package in Trusty:
  In Progress
Status in gccgo-4.9 source package in Vivid:
  Invalid
Status in gccgo-5 source package in Vivid:
  In Progress
Status in gccgo-4.9 source package in Wily:
  Invalid

Bug description:
  lxd 0.12-0ubuntu2
  libgo7/5.1.1-12ubuntu1

  Jul 08 00:11:16 vital-beggar systemd[1]: Starting Container hypervisor based 
on LXC...
  -- Subject: Unit lxd.service has begun start-up
  -- Defined-By: systemd
  -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
  -- 
  -- Unit lxd.service has begun starting up.
  Jul 08 00:11:16 vital-beggar lxd[1712]: p=0x98d18000
  Jul 08 00:11:16 vital-beggar lxd[1712]: fatal error: runtime_lfstackpush: 
invalid pointer
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime stack:
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_dopanic
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/panic.c:135
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_throw
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/panic.c:193
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime.lfstackpush
  Jul 08 00:11:16 vital-beggar lxd[1712]: 
../../../src/libgo/runtime/lfstack.goc:40
  Jul 08 00:11:16 vital-beggar lxd[1712]: getempty
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/mgc0.c:1377
  Jul 08 00:11:16 vital-beggar lxd[1712]: enqueue1
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/mgc0.c:1255
  Jul 08 00:11:16 vital-beggar lxd[1712]: markroot
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/mgc0.c:1285
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_parfordo
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/parfor.c:88
  Jul 08 00:11:16 vital-beggar lxd[1712]: gc
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/mgc0.c:2266
  Jul 08 00:11:16 vital-beggar lxd[1712]: mgc
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/mgc0.c:2211
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_mstart
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/proc.c:1076
  Jul 08 00:11:16 vital-beggar lxd[1712]: goroutine 16 [garbage collection]:
  Jul 08 00:11:16 vital-beggar systemd[1]: lxd.service: Main process exited, 
code=exited, status=2/INVALIDARGUMENT
  Jul 08 00:11:16 vital-beggar systemd[1]: lxd.service: Unit entered failed 
state.
  Jul 08 00:11:16 vital-beggar systemd[1]: lxd.service: Failed with result 
'exit-code'.
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_mcall
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/proc.c:295
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_gc
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/mgc0.c:2187
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_mallocgc
  Jul 08 00:11:16 vital-beggar lxd[1712]: 
../../../src/libgo/runtime/malloc.goc:259
  Jul 08 00:11:16 vital-beggar lxd[1712]: :0
  Jul 08 00:11:16 vital-beggar lxd[1712]: :0
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_main
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/proc.c:626
  Jul 08 00:11:16 vital-beggar lxd[1712]: goroutine 17 [runnable]:
  Jul 08 00:11:16 vital-beggar lxd[1712]: kickoff
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/proc.c:232
  Jul 08 00:11:16 vital-beggar lxd[1712]: created by runtime_main
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/proc.c:598
  Jul 08 00:11:16 vital-beggar lxd[1712]: goroutine 18 [runnable]:
  Jul 08 00:11:16 vital-beggar lxd[1712]: kickoff
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/proc.c:232
  Jul 08 00:11:16 vital-beggar lxd[1712]: created by runtime_createfing
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/mgc0.c:2572
  Jul 08 00:11:16 vital-beggar lxd[1712]: goroutine 19 [runnable]:
  Jul 08 00:11:16 vital-beggar lxd[1712]: kickoff
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/proc.c:232
  Jul 08 00:11:16 

[Touch-packages] [Bug 1472650] Re: [arm64] gccgo runtime crashes with CONFIG_ARM64_PGTABLE_LEVELS=4

[Launchpad Bug Tracker]

** Branch linked: lp:ubuntu/vivid-proposed/gccgo-5

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

Title:
  [arm64] gccgo runtime crashes with CONFIG_ARM64_PGTABLE_LEVELS=4

Status in gcc:
  Unknown
Status in gcc-5 package in Ubuntu:
  Fix Released
Status in gccgo-4.9 package in Ubuntu:
  Invalid
Status in gccgo-5 package in Ubuntu:
  Invalid
Status in gccgo-4.9 source package in Trusty:
  In Progress
Status in gccgo-4.9 source package in Vivid:
  Invalid
Status in gccgo-5 source package in Vivid:
  Fix Committed
Status in gccgo-4.9 source package in Wily:
  Invalid

Bug description:
  [Impact]
  Various go-based packages crash on startup on arm64 when booted with a kernel 
where CONFIG_ARM64_PGTABLE_LEVELS=4. LXD, docker and juju are examples.

  Ubuntu does not ship with this config, so it is currently not
  impacted. However, we would like to enable this config to add new
  hardware support in 15.10. The 15.10 kernel will eventually be
  provided in trusty as an lts backport, at which point this will begin
  to break users.

  [Test Case]
  Boot an arm64 system with CONFIG_ARM64_PGTABLE_LEVELS=4 enabled in the 
kernel. Install docker.io and run "docker help". If it fails, you'll see "fatal 
error: runtime_lfstackpush" followed by a stack trace. If it succeeds, you'll 
get normal help output.

  [Regression Risk]
  The risk of regression is lessened by testing this release on existing Ubuntu 
kernels w/ 3 level page tables.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gcc/+bug/1472650/+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 1472650] Re: [arm64] gccgo runtime crashes with CONFIG_ARM64_PGTABLE_LEVELS=4

[dann frazier]

** Description changed:

- lxd 0.12-0ubuntu2
- libgo7/5.1.1-12ubuntu1
+ [Impact]
+ Various go-based packages crash on startup on arm64 when booted with a kernel 
where CONFIG_ARM64_PGTABLE_LEVELS=4. LXD, docker and juju are examples.
  
- Jul 08 00:11:16 vital-beggar systemd[1]: Starting Container hypervisor based 
on LXC...
- -- Subject: Unit lxd.service has begun start-up
- -- Defined-By: systemd
- -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
- -- 
- -- Unit lxd.service has begun starting up.
- Jul 08 00:11:16 vital-beggar lxd[1712]: p=0x98d18000
- Jul 08 00:11:16 vital-beggar lxd[1712]: fatal error: runtime_lfstackpush: 
invalid pointer
- Jul 08 00:11:16 vital-beggar lxd[1712]: runtime stack:
- Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_dopanic
- Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/panic.c:135
- Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_throw
- Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/panic.c:193
- Jul 08 00:11:16 vital-beggar lxd[1712]: runtime.lfstackpush
- Jul 08 00:11:16 vital-beggar lxd[1712]: 
../../../src/libgo/runtime/lfstack.goc:40
- Jul 08 00:11:16 vital-beggar lxd[1712]: getempty
- Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/mgc0.c:1377
- Jul 08 00:11:16 vital-beggar lxd[1712]: enqueue1
- Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/mgc0.c:1255
- Jul 08 00:11:16 vital-beggar lxd[1712]: markroot
- Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/mgc0.c:1285
- Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_parfordo
- Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/parfor.c:88
- Jul 08 00:11:16 vital-beggar lxd[1712]: gc
- Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/mgc0.c:2266
- Jul 08 00:11:16 vital-beggar lxd[1712]: mgc
- Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/mgc0.c:2211
- Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_mstart
- Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/proc.c:1076
- Jul 08 00:11:16 vital-beggar lxd[1712]: goroutine 16 [garbage collection]:
- Jul 08 00:11:16 vital-beggar systemd[1]: lxd.service: Main process exited, 
code=exited, status=2/INVALIDARGUMENT
- Jul 08 00:11:16 vital-beggar systemd[1]: lxd.service: Unit entered failed 
state.
- Jul 08 00:11:16 vital-beggar systemd[1]: lxd.service: Failed with result 
'exit-code'.
- Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_mcall
- Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/proc.c:295
- Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_gc
- Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/mgc0.c:2187
- Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_mallocgc
- Jul 08 00:11:16 vital-beggar lxd[1712]: 
../../../src/libgo/runtime/malloc.goc:259
- Jul 08 00:11:16 vital-beggar lxd[1712]: :0
- Jul 08 00:11:16 vital-beggar lxd[1712]: :0
- Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_main
- Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/proc.c:626
- Jul 08 00:11:16 vital-beggar lxd[1712]: goroutine 17 [runnable]:
- Jul 08 00:11:16 vital-beggar lxd[1712]: kickoff
- Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/proc.c:232
- Jul 08 00:11:16 vital-beggar lxd[1712]: created by runtime_main
- Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/proc.c:598
- Jul 08 00:11:16 vital-beggar lxd[1712]: goroutine 18 [runnable]:
- Jul 08 00:11:16 vital-beggar lxd[1712]: kickoff
- Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/proc.c:232
- Jul 08 00:11:16 vital-beggar lxd[1712]: created by runtime_createfing
- Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/mgc0.c:2572
- Jul 08 00:11:16 vital-beggar lxd[1712]: goroutine 19 [runnable]:
- Jul 08 00:11:16 vital-beggar lxd[1712]: kickoff
- Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/proc.c:232
- Jul 08 00:11:16 vital-beggar lxd[1712]: created by os_signal..import
- Jul 08 00:11:16 vital-beggar lxd[1712]: 
../../../src/libgo/go/os/signal/signal_unix.go:25
- Jul 08 00:11:16 vital-beggar systemd[1]: lxd.service: Service hold-off time 
over, scheduling restart.
- Jul 08 00:11:16 vital-beggar systemd[1]: lxd.service: Start request repeated 
too quickly.
- Jul 08 00:11:16 vital-beggar systemd[1]: Failed to start Container hypervisor 
based on LXC.
- -- Subject: Unit lxd.service has failed
- -- Defined-By: systemd
- -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
- -- 
- -- Unit lxd.service has failed.
- -- 
- -- The result is failed.
- Jul 08 00:11:16 vital-beggar systemd[1]: lxd.service: Unit entered failed 
state.
- Jul 08 00:11:16 vital-beggar systemd[1]: lxd.service: Failed with result 
'start-limit'.
+ Ubuntu does not ship with this config, so it is currently not impacted.
+ However, we would like to enable this config to add new hardware support
+ in 15.10. The 15.10 

[Touch-packages] [Bug 1472650] Re: [arm64] gccgo runtime crashes with CONFIG_ARM64_PGTABLE_LEVELS=4

[Brian Murray]

Hello dann, or anyone else affected,

Accepted gccgo-5 into vivid-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/gccgo-5/5.1~rc1-0ubuntu1.1 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: gccgo-5 (Ubuntu Vivid)
   Status: In Progress => Fix Committed

** Tags added: verification-needed

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

Title:
  [arm64] gccgo runtime crashes with CONFIG_ARM64_PGTABLE_LEVELS=4

Status in gcc:
  Unknown
Status in gcc-5 package in Ubuntu:
  Fix Released
Status in gccgo-4.9 package in Ubuntu:
  Invalid
Status in gccgo-5 package in Ubuntu:
  Invalid
Status in gccgo-4.9 source package in Trusty:
  In Progress
Status in gccgo-4.9 source package in Vivid:
  Invalid
Status in gccgo-5 source package in Vivid:
  Fix Committed
Status in gccgo-4.9 source package in Wily:
  Invalid

Bug description:
  [Impact]
  Various go-based packages crash on startup on arm64 when booted with a kernel 
where CONFIG_ARM64_PGTABLE_LEVELS=4. LXD, docker and juju are examples.

  Ubuntu does not ship with this config, so it is currently not
  impacted. However, we would like to enable this config to add new
  hardware support in 15.10. The 15.10 kernel will eventually be
  provided in trusty as an lts backport, at which point this will begin
  to break users.

  [Test Case]
  Boot an arm64 system with CONFIG_ARM64_PGTABLE_LEVELS=4 enabled in the 
kernel. Install docker.io and run "docker help". If it fails, you'll see "fatal 
error: runtime_lfstackpush" followed by a stack trace. If it succeeds, you'll 
get normal help output.

  [Regression Risk]
  The risk of regression is lessened by testing this release on existing Ubuntu 
kernels w/ 3 level page tables.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gcc/+bug/1472650/+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 1472650] Re: [arm64] gccgo runtime crashes with CONFIG_ARM64_PGTABLE_LEVELS=4

[Michael Hudson-Doyle]

Oh yes, and dann and I confirmed yesterday that the bug is no longer
present in wily.

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

Title:
  [arm64] gccgo runtime crashes with CONFIG_ARM64_PGTABLE_LEVELS=4

Status in gcc:
  Unknown
Status in gcc-5 package in Ubuntu:
  Fix Released
Status in gccgo-4.9 package in Ubuntu:
  New
Status in gccgo-5 package in Ubuntu:
  New
Status in gccgo-4.9 source package in Trusty:
  Confirmed
Status in gccgo-4.9 source package in Vivid:
  New
Status in gccgo-5 source package in Vivid:
  New
Status in gccgo-4.9 source package in Wily:
  New

Bug description:
  lxd 0.12-0ubuntu2
  libgo7/5.1.1-12ubuntu1

  Jul 08 00:11:16 vital-beggar systemd[1]: Starting Container hypervisor based 
on LXC...
  -- Subject: Unit lxd.service has begun start-up
  -- Defined-By: systemd
  -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
  -- 
  -- Unit lxd.service has begun starting up.
  Jul 08 00:11:16 vital-beggar lxd[1712]: p=0x98d18000
  Jul 08 00:11:16 vital-beggar lxd[1712]: fatal error: runtime_lfstackpush: 
invalid pointer
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime stack:
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_dopanic
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/panic.c:135
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_throw
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/panic.c:193
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime.lfstackpush
  Jul 08 00:11:16 vital-beggar lxd[1712]: 
../../../src/libgo/runtime/lfstack.goc:40
  Jul 08 00:11:16 vital-beggar lxd[1712]: getempty
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/mgc0.c:1377
  Jul 08 00:11:16 vital-beggar lxd[1712]: enqueue1
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/mgc0.c:1255
  Jul 08 00:11:16 vital-beggar lxd[1712]: markroot
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/mgc0.c:1285
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_parfordo
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/parfor.c:88
  Jul 08 00:11:16 vital-beggar lxd[1712]: gc
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/mgc0.c:2266
  Jul 08 00:11:16 vital-beggar lxd[1712]: mgc
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/mgc0.c:2211
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_mstart
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/proc.c:1076
  Jul 08 00:11:16 vital-beggar lxd[1712]: goroutine 16 [garbage collection]:
  Jul 08 00:11:16 vital-beggar systemd[1]: lxd.service: Main process exited, 
code=exited, status=2/INVALIDARGUMENT
  Jul 08 00:11:16 vital-beggar systemd[1]: lxd.service: Unit entered failed 
state.
  Jul 08 00:11:16 vital-beggar systemd[1]: lxd.service: Failed with result 
'exit-code'.
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_mcall
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/proc.c:295
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_gc
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/mgc0.c:2187
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_mallocgc
  Jul 08 00:11:16 vital-beggar lxd[1712]: 
../../../src/libgo/runtime/malloc.goc:259
  Jul 08 00:11:16 vital-beggar lxd[1712]: :0
  Jul 08 00:11:16 vital-beggar lxd[1712]: :0
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_main
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/proc.c:626
  Jul 08 00:11:16 vital-beggar lxd[1712]: goroutine 17 [runnable]:
  Jul 08 00:11:16 vital-beggar lxd[1712]: kickoff
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/proc.c:232
  Jul 08 00:11:16 vital-beggar lxd[1712]: created by runtime_main
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/proc.c:598
  Jul 08 00:11:16 vital-beggar lxd[1712]: goroutine 18 [runnable]:
  Jul 08 00:11:16 vital-beggar lxd[1712]: kickoff
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/proc.c:232
  Jul 08 00:11:16 vital-beggar lxd[1712]: created by runtime_createfing
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/mgc0.c:2572
  Jul 08 00:11:16 vital-beggar lxd[1712]: goroutine 19 [runnable]:
  Jul 08 00:11:16 vital-beggar lxd[1712]: kickoff
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/proc.c:232
  Jul 08 00:11:16 vital-beggar lxd[1712]: created by os_signal..import
  Jul 08 00:11:16 vital-beggar lxd[1712]: 
../../../src/libgo/go/os/signal/signal_unix.go:25
  Jul 08 00:11:16 vital-beggar systemd[1]: lxd.service: Service hold-off time 
over, scheduling restart.
  Jul 08 00:11:16 vital-beggar systemd[1]: lxd.service: Start request repeated 
too quickly.
  Jul 08 00:11:16 vital-beggar systemd[1]: Failed to start Container hypervisor 
based on LXC.
  -- Subject: Unit 

[Touch-packages] [Bug 1472650] Re: [arm64] gccgo runtime crashes with CONFIG_ARM64_PGTABLE_LEVELS=4

[Michael Hudson-Doyle]

Here's a patch for trusty, based on the gccgo-4.9 from ~ubuntu-
toolchain-r/+archive/ubuntu/ppa:
http://people.canonical.com/~mwh/gccgo-4.9_4.9.3-0ubuntu3_4.9.3-0ubuntu4.diff
(not tested yet).

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

Title:
  [arm64] gccgo runtime crashes with CONFIG_ARM64_PGTABLE_LEVELS=4

Status in gcc:
  Unknown
Status in gcc-5 package in Ubuntu:
  Fix Released
Status in gccgo-4.9 package in Ubuntu:
  New
Status in gccgo-5 package in Ubuntu:
  New
Status in gccgo-4.9 source package in Trusty:
  Confirmed
Status in gccgo-4.9 source package in Vivid:
  New
Status in gccgo-5 source package in Vivid:
  New
Status in gccgo-4.9 source package in Wily:
  New

Bug description:
  lxd 0.12-0ubuntu2
  libgo7/5.1.1-12ubuntu1

  Jul 08 00:11:16 vital-beggar systemd[1]: Starting Container hypervisor based 
on LXC...
  -- Subject: Unit lxd.service has begun start-up
  -- Defined-By: systemd
  -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
  -- 
  -- Unit lxd.service has begun starting up.
  Jul 08 00:11:16 vital-beggar lxd[1712]: p=0x98d18000
  Jul 08 00:11:16 vital-beggar lxd[1712]: fatal error: runtime_lfstackpush: 
invalid pointer
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime stack:
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_dopanic
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/panic.c:135
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_throw
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/panic.c:193
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime.lfstackpush
  Jul 08 00:11:16 vital-beggar lxd[1712]: 
../../../src/libgo/runtime/lfstack.goc:40
  Jul 08 00:11:16 vital-beggar lxd[1712]: getempty
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/mgc0.c:1377
  Jul 08 00:11:16 vital-beggar lxd[1712]: enqueue1
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/mgc0.c:1255
  Jul 08 00:11:16 vital-beggar lxd[1712]: markroot
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/mgc0.c:1285
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_parfordo
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/parfor.c:88
  Jul 08 00:11:16 vital-beggar lxd[1712]: gc
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/mgc0.c:2266
  Jul 08 00:11:16 vital-beggar lxd[1712]: mgc
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/mgc0.c:2211
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_mstart
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/proc.c:1076
  Jul 08 00:11:16 vital-beggar lxd[1712]: goroutine 16 [garbage collection]:
  Jul 08 00:11:16 vital-beggar systemd[1]: lxd.service: Main process exited, 
code=exited, status=2/INVALIDARGUMENT
  Jul 08 00:11:16 vital-beggar systemd[1]: lxd.service: Unit entered failed 
state.
  Jul 08 00:11:16 vital-beggar systemd[1]: lxd.service: Failed with result 
'exit-code'.
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_mcall
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/proc.c:295
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_gc
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/mgc0.c:2187
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_mallocgc
  Jul 08 00:11:16 vital-beggar lxd[1712]: 
../../../src/libgo/runtime/malloc.goc:259
  Jul 08 00:11:16 vital-beggar lxd[1712]: :0
  Jul 08 00:11:16 vital-beggar lxd[1712]: :0
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_main
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/proc.c:626
  Jul 08 00:11:16 vital-beggar lxd[1712]: goroutine 17 [runnable]:
  Jul 08 00:11:16 vital-beggar lxd[1712]: kickoff
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/proc.c:232
  Jul 08 00:11:16 vital-beggar lxd[1712]: created by runtime_main
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/proc.c:598
  Jul 08 00:11:16 vital-beggar lxd[1712]: goroutine 18 [runnable]:
  Jul 08 00:11:16 vital-beggar lxd[1712]: kickoff
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/proc.c:232
  Jul 08 00:11:16 vital-beggar lxd[1712]: created by runtime_createfing
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/mgc0.c:2572
  Jul 08 00:11:16 vital-beggar lxd[1712]: goroutine 19 [runnable]:
  Jul 08 00:11:16 vital-beggar lxd[1712]: kickoff
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/proc.c:232
  Jul 08 00:11:16 vital-beggar lxd[1712]: created by os_signal..import
  Jul 08 00:11:16 vital-beggar lxd[1712]: 
../../../src/libgo/go/os/signal/signal_unix.go:25
  Jul 08 00:11:16 vital-beggar systemd[1]: lxd.service: Service hold-off time 
over, scheduling restart.
  Jul 08 00:11:16 vital-beggar systemd[1]: lxd.service: Start request repeated 
too quickly.
  Jul 

[Touch-packages] [Bug 1472650] Re: [arm64] gccgo runtime crashes with CONFIG_ARM64_PGTABLE_LEVELS=4

[Launchpad Bug Tracker]

This bug was fixed in the package gcc-5 - 5.2.1-17ubuntu1

---
gcc-5 (5.2.1-17ubuntu1) wily; urgency=medium

  * Merge with Debian; remaining changes:
- Build from upstream sources.

 -- Matthias Klose   Fri, 11 Sep 2015 03:24:48 +0200

** Changed in: gcc-5 (Ubuntu)
   Status: New => Fix Released

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

Title:
  [arm64] gccgo runtime crashes with CONFIG_ARM64_PGTABLE_LEVELS=4

Status in gcc:
  Unknown
Status in gcc-5 package in Ubuntu:
  Fix Released
Status in gccgo-4.9 package in Ubuntu:
  New
Status in gccgo-5 package in Ubuntu:
  New
Status in gccgo-4.9 source package in Trusty:
  Confirmed
Status in gccgo-4.9 source package in Vivid:
  New
Status in gccgo-5 source package in Vivid:
  New
Status in gccgo-4.9 source package in Wily:
  New

Bug description:
  lxd 0.12-0ubuntu2
  libgo7/5.1.1-12ubuntu1

  Jul 08 00:11:16 vital-beggar systemd[1]: Starting Container hypervisor based 
on LXC...
  -- Subject: Unit lxd.service has begun start-up
  -- Defined-By: systemd
  -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
  -- 
  -- Unit lxd.service has begun starting up.
  Jul 08 00:11:16 vital-beggar lxd[1712]: p=0x98d18000
  Jul 08 00:11:16 vital-beggar lxd[1712]: fatal error: runtime_lfstackpush: 
invalid pointer
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime stack:
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_dopanic
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/panic.c:135
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_throw
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/panic.c:193
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime.lfstackpush
  Jul 08 00:11:16 vital-beggar lxd[1712]: 
../../../src/libgo/runtime/lfstack.goc:40
  Jul 08 00:11:16 vital-beggar lxd[1712]: getempty
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/mgc0.c:1377
  Jul 08 00:11:16 vital-beggar lxd[1712]: enqueue1
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/mgc0.c:1255
  Jul 08 00:11:16 vital-beggar lxd[1712]: markroot
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/mgc0.c:1285
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_parfordo
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/parfor.c:88
  Jul 08 00:11:16 vital-beggar lxd[1712]: gc
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/mgc0.c:2266
  Jul 08 00:11:16 vital-beggar lxd[1712]: mgc
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/mgc0.c:2211
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_mstart
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/proc.c:1076
  Jul 08 00:11:16 vital-beggar lxd[1712]: goroutine 16 [garbage collection]:
  Jul 08 00:11:16 vital-beggar systemd[1]: lxd.service: Main process exited, 
code=exited, status=2/INVALIDARGUMENT
  Jul 08 00:11:16 vital-beggar systemd[1]: lxd.service: Unit entered failed 
state.
  Jul 08 00:11:16 vital-beggar systemd[1]: lxd.service: Failed with result 
'exit-code'.
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_mcall
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/proc.c:295
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_gc
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/mgc0.c:2187
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_mallocgc
  Jul 08 00:11:16 vital-beggar lxd[1712]: 
../../../src/libgo/runtime/malloc.goc:259
  Jul 08 00:11:16 vital-beggar lxd[1712]: :0
  Jul 08 00:11:16 vital-beggar lxd[1712]: :0
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_main
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/proc.c:626
  Jul 08 00:11:16 vital-beggar lxd[1712]: goroutine 17 [runnable]:
  Jul 08 00:11:16 vital-beggar lxd[1712]: kickoff
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/proc.c:232
  Jul 08 00:11:16 vital-beggar lxd[1712]: created by runtime_main
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/proc.c:598
  Jul 08 00:11:16 vital-beggar lxd[1712]: goroutine 18 [runnable]:
  Jul 08 00:11:16 vital-beggar lxd[1712]: kickoff
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/proc.c:232
  Jul 08 00:11:16 vital-beggar lxd[1712]: created by runtime_createfing
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/mgc0.c:2572
  Jul 08 00:11:16 vital-beggar lxd[1712]: goroutine 19 [runnable]:
  Jul 08 00:11:16 vital-beggar lxd[1712]: kickoff
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/proc.c:232
  Jul 08 00:11:16 vital-beggar lxd[1712]: created by os_signal..import
  Jul 08 00:11:16 vital-beggar lxd[1712]: 
../../../src/libgo/go/os/signal/signal_unix.go:25
  Jul 08 00:11:16 vital-beggar systemd[1]: lxd.service: 

[Touch-packages] [Bug 1472650] Re: [arm64] gccgo runtime crashes with CONFIG_ARM64_PGTABLE_LEVELS=4

[Michael Hudson-Doyle]

Filed upstream as https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67508

** Bug watch added: GCC Bugzilla #67508
   https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67508

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

Title:
  [arm64] gccgo runtime crashes with CONFIG_ARM64_PGTABLE_LEVELS=4

Status in gcc-5 package in Ubuntu:
  New
Status in gccgo-4.9 package in Ubuntu:
  New
Status in gccgo-5 package in Ubuntu:
  New
Status in gccgo-4.9 source package in Trusty:
  Confirmed
Status in gccgo-4.9 source package in Vivid:
  New
Status in gccgo-5 source package in Vivid:
  New
Status in gccgo-4.9 source package in Wily:
  New

Bug description:
  lxd 0.12-0ubuntu2
  libgo7/5.1.1-12ubuntu1

  Jul 08 00:11:16 vital-beggar systemd[1]: Starting Container hypervisor based 
on LXC...
  -- Subject: Unit lxd.service has begun start-up
  -- Defined-By: systemd
  -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
  -- 
  -- Unit lxd.service has begun starting up.
  Jul 08 00:11:16 vital-beggar lxd[1712]: p=0x98d18000
  Jul 08 00:11:16 vital-beggar lxd[1712]: fatal error: runtime_lfstackpush: 
invalid pointer
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime stack:
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_dopanic
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/panic.c:135
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_throw
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/panic.c:193
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime.lfstackpush
  Jul 08 00:11:16 vital-beggar lxd[1712]: 
../../../src/libgo/runtime/lfstack.goc:40
  Jul 08 00:11:16 vital-beggar lxd[1712]: getempty
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/mgc0.c:1377
  Jul 08 00:11:16 vital-beggar lxd[1712]: enqueue1
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/mgc0.c:1255
  Jul 08 00:11:16 vital-beggar lxd[1712]: markroot
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/mgc0.c:1285
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_parfordo
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/parfor.c:88
  Jul 08 00:11:16 vital-beggar lxd[1712]: gc
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/mgc0.c:2266
  Jul 08 00:11:16 vital-beggar lxd[1712]: mgc
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/mgc0.c:2211
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_mstart
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/proc.c:1076
  Jul 08 00:11:16 vital-beggar lxd[1712]: goroutine 16 [garbage collection]:
  Jul 08 00:11:16 vital-beggar systemd[1]: lxd.service: Main process exited, 
code=exited, status=2/INVALIDARGUMENT
  Jul 08 00:11:16 vital-beggar systemd[1]: lxd.service: Unit entered failed 
state.
  Jul 08 00:11:16 vital-beggar systemd[1]: lxd.service: Failed with result 
'exit-code'.
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_mcall
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/proc.c:295
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_gc
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/mgc0.c:2187
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_mallocgc
  Jul 08 00:11:16 vital-beggar lxd[1712]: 
../../../src/libgo/runtime/malloc.goc:259
  Jul 08 00:11:16 vital-beggar lxd[1712]: :0
  Jul 08 00:11:16 vital-beggar lxd[1712]: :0
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_main
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/proc.c:626
  Jul 08 00:11:16 vital-beggar lxd[1712]: goroutine 17 [runnable]:
  Jul 08 00:11:16 vital-beggar lxd[1712]: kickoff
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/proc.c:232
  Jul 08 00:11:16 vital-beggar lxd[1712]: created by runtime_main
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/proc.c:598
  Jul 08 00:11:16 vital-beggar lxd[1712]: goroutine 18 [runnable]:
  Jul 08 00:11:16 vital-beggar lxd[1712]: kickoff
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/proc.c:232
  Jul 08 00:11:16 vital-beggar lxd[1712]: created by runtime_createfing
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/mgc0.c:2572
  Jul 08 00:11:16 vital-beggar lxd[1712]: goroutine 19 [runnable]:
  Jul 08 00:11:16 vital-beggar lxd[1712]: kickoff
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/proc.c:232
  Jul 08 00:11:16 vital-beggar lxd[1712]: created by os_signal..import
  Jul 08 00:11:16 vital-beggar lxd[1712]: 
../../../src/libgo/go/os/signal/signal_unix.go:25
  Jul 08 00:11:16 vital-beggar systemd[1]: lxd.service: Service hold-off time 
over, scheduling restart.
  Jul 08 00:11:16 vital-beggar systemd[1]: lxd.service: Start request repeated 
too quickly.
  Jul 08 00:11:16 vital-beggar systemd[1]: Failed to start Container 

[Touch-packages] [Bug 1472650] Re: [arm64] gccgo runtime crashes with CONFIG_ARM64_PGTABLE_LEVELS=4

[dann frazier]

** Also affects: gcc via
   https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67508
   Importance: Unknown
   Status: Unknown

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

Title:
  [arm64] gccgo runtime crashes with CONFIG_ARM64_PGTABLE_LEVELS=4

Status in gcc:
  Unknown
Status in gcc-5 package in Ubuntu:
  New
Status in gccgo-4.9 package in Ubuntu:
  New
Status in gccgo-5 package in Ubuntu:
  New
Status in gccgo-4.9 source package in Trusty:
  Confirmed
Status in gccgo-4.9 source package in Vivid:
  New
Status in gccgo-5 source package in Vivid:
  New
Status in gccgo-4.9 source package in Wily:
  New

Bug description:
  lxd 0.12-0ubuntu2
  libgo7/5.1.1-12ubuntu1

  Jul 08 00:11:16 vital-beggar systemd[1]: Starting Container hypervisor based 
on LXC...
  -- Subject: Unit lxd.service has begun start-up
  -- Defined-By: systemd
  -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
  -- 
  -- Unit lxd.service has begun starting up.
  Jul 08 00:11:16 vital-beggar lxd[1712]: p=0x98d18000
  Jul 08 00:11:16 vital-beggar lxd[1712]: fatal error: runtime_lfstackpush: 
invalid pointer
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime stack:
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_dopanic
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/panic.c:135
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_throw
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/panic.c:193
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime.lfstackpush
  Jul 08 00:11:16 vital-beggar lxd[1712]: 
../../../src/libgo/runtime/lfstack.goc:40
  Jul 08 00:11:16 vital-beggar lxd[1712]: getempty
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/mgc0.c:1377
  Jul 08 00:11:16 vital-beggar lxd[1712]: enqueue1
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/mgc0.c:1255
  Jul 08 00:11:16 vital-beggar lxd[1712]: markroot
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/mgc0.c:1285
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_parfordo
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/parfor.c:88
  Jul 08 00:11:16 vital-beggar lxd[1712]: gc
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/mgc0.c:2266
  Jul 08 00:11:16 vital-beggar lxd[1712]: mgc
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/mgc0.c:2211
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_mstart
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/proc.c:1076
  Jul 08 00:11:16 vital-beggar lxd[1712]: goroutine 16 [garbage collection]:
  Jul 08 00:11:16 vital-beggar systemd[1]: lxd.service: Main process exited, 
code=exited, status=2/INVALIDARGUMENT
  Jul 08 00:11:16 vital-beggar systemd[1]: lxd.service: Unit entered failed 
state.
  Jul 08 00:11:16 vital-beggar systemd[1]: lxd.service: Failed with result 
'exit-code'.
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_mcall
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/proc.c:295
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_gc
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/mgc0.c:2187
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_mallocgc
  Jul 08 00:11:16 vital-beggar lxd[1712]: 
../../../src/libgo/runtime/malloc.goc:259
  Jul 08 00:11:16 vital-beggar lxd[1712]: :0
  Jul 08 00:11:16 vital-beggar lxd[1712]: :0
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_main
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/proc.c:626
  Jul 08 00:11:16 vital-beggar lxd[1712]: goroutine 17 [runnable]:
  Jul 08 00:11:16 vital-beggar lxd[1712]: kickoff
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/proc.c:232
  Jul 08 00:11:16 vital-beggar lxd[1712]: created by runtime_main
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/proc.c:598
  Jul 08 00:11:16 vital-beggar lxd[1712]: goroutine 18 [runnable]:
  Jul 08 00:11:16 vital-beggar lxd[1712]: kickoff
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/proc.c:232
  Jul 08 00:11:16 vital-beggar lxd[1712]: created by runtime_createfing
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/mgc0.c:2572
  Jul 08 00:11:16 vital-beggar lxd[1712]: goroutine 19 [runnable]:
  Jul 08 00:11:16 vital-beggar lxd[1712]: kickoff
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/proc.c:232
  Jul 08 00:11:16 vital-beggar lxd[1712]: created by os_signal..import
  Jul 08 00:11:16 vital-beggar lxd[1712]: 
../../../src/libgo/go/os/signal/signal_unix.go:25
  Jul 08 00:11:16 vital-beggar systemd[1]: lxd.service: Service hold-off time 
over, scheduling restart.
  Jul 08 00:11:16 vital-beggar systemd[1]: lxd.service: Start request repeated 
too quickly.
  Jul 08 00:11:16 vital-beggar systemd[1]: Failed to start Container hypervisor 

[Touch-packages] [Bug 1472650] Re: [arm64] gccgo runtime crashes with CONFIG_ARM64_PGTABLE_LEVELS=4

[Michael Hudson-Doyle]

The fix I've sent upstream is https://go-
review.googlesource.com/#/c/13037/. It hasn't been reviewed yet, but
I've confirmed it works to my own satisfaction on arm64.

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

Title:
  [arm64] gccgo runtime crashes with CONFIG_ARM64_PGTABLE_LEVELS=4

Status in gcc-5 package in Ubuntu:
  New
Status in gccgo-4.9 package in Ubuntu:
  New
Status in gccgo-5 package in Ubuntu:
  New
Status in gccgo-4.9 source package in Trusty:
  Confirmed
Status in gccgo-4.9 source package in Vivid:
  New
Status in gccgo-5 source package in Vivid:
  New
Status in gccgo-4.9 source package in Wily:
  New

Bug description:
  lxd 0.12-0ubuntu2
  libgo7/5.1.1-12ubuntu1

  Jul 08 00:11:16 vital-beggar systemd[1]: Starting Container hypervisor based 
on LXC...
  -- Subject: Unit lxd.service has begun start-up
  -- Defined-By: systemd
  -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
  -- 
  -- Unit lxd.service has begun starting up.
  Jul 08 00:11:16 vital-beggar lxd[1712]: p=0x98d18000
  Jul 08 00:11:16 vital-beggar lxd[1712]: fatal error: runtime_lfstackpush: 
invalid pointer
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime stack:
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_dopanic
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/panic.c:135
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_throw
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/panic.c:193
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime.lfstackpush
  Jul 08 00:11:16 vital-beggar lxd[1712]: 
../../../src/libgo/runtime/lfstack.goc:40
  Jul 08 00:11:16 vital-beggar lxd[1712]: getempty
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/mgc0.c:1377
  Jul 08 00:11:16 vital-beggar lxd[1712]: enqueue1
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/mgc0.c:1255
  Jul 08 00:11:16 vital-beggar lxd[1712]: markroot
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/mgc0.c:1285
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_parfordo
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/parfor.c:88
  Jul 08 00:11:16 vital-beggar lxd[1712]: gc
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/mgc0.c:2266
  Jul 08 00:11:16 vital-beggar lxd[1712]: mgc
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/mgc0.c:2211
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_mstart
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/proc.c:1076
  Jul 08 00:11:16 vital-beggar lxd[1712]: goroutine 16 [garbage collection]:
  Jul 08 00:11:16 vital-beggar systemd[1]: lxd.service: Main process exited, 
code=exited, status=2/INVALIDARGUMENT
  Jul 08 00:11:16 vital-beggar systemd[1]: lxd.service: Unit entered failed 
state.
  Jul 08 00:11:16 vital-beggar systemd[1]: lxd.service: Failed with result 
'exit-code'.
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_mcall
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/proc.c:295
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_gc
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/mgc0.c:2187
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_mallocgc
  Jul 08 00:11:16 vital-beggar lxd[1712]: 
../../../src/libgo/runtime/malloc.goc:259
  Jul 08 00:11:16 vital-beggar lxd[1712]: :0
  Jul 08 00:11:16 vital-beggar lxd[1712]: :0
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_main
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/proc.c:626
  Jul 08 00:11:16 vital-beggar lxd[1712]: goroutine 17 [runnable]:
  Jul 08 00:11:16 vital-beggar lxd[1712]: kickoff
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/proc.c:232
  Jul 08 00:11:16 vital-beggar lxd[1712]: created by runtime_main
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/proc.c:598
  Jul 08 00:11:16 vital-beggar lxd[1712]: goroutine 18 [runnable]:
  Jul 08 00:11:16 vital-beggar lxd[1712]: kickoff
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/proc.c:232
  Jul 08 00:11:16 vital-beggar lxd[1712]: created by runtime_createfing
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/mgc0.c:2572
  Jul 08 00:11:16 vital-beggar lxd[1712]: goroutine 19 [runnable]:
  Jul 08 00:11:16 vital-beggar lxd[1712]: kickoff
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/proc.c:232
  Jul 08 00:11:16 vital-beggar lxd[1712]: created by os_signal..import
  Jul 08 00:11:16 vital-beggar lxd[1712]: 
../../../src/libgo/go/os/signal/signal_unix.go:25
  Jul 08 00:11:16 vital-beggar systemd[1]: lxd.service: Service hold-off time 
over, scheduling restart.
  Jul 08 00:11:16 vital-beggar systemd[1]: lxd.service: Start request repeated 
too quickly.
  Jul 08 00:11:16 vital-beggar systemd[1]: Failed to start 

[Touch-packages] [Bug 1472650] Re: [arm64] gccgo runtime crashes with CONFIG_ARM64_PGTABLE_LEVELS=4

[dann frazier]

** No longer affects: gccgo-5 (Ubuntu Trusty)

** Also affects: gcc-5 (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: gccgo-5 (Ubuntu Wily)

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

Title:
  [arm64] gccgo runtime crashes with CONFIG_ARM64_PGTABLE_LEVELS=4

Status in gcc-5 package in Ubuntu:
  New
Status in gccgo-4.9 package in Ubuntu:
  New
Status in gccgo-5 package in Ubuntu:
  New
Status in gccgo-4.9 source package in Trusty:
  Confirmed
Status in gccgo-4.9 source package in Vivid:
  New
Status in gccgo-5 source package in Vivid:
  New
Status in gccgo-4.9 source package in Wily:
  New

Bug description:
  lxd 0.12-0ubuntu2
  libgo7/5.1.1-12ubuntu1

  Jul 08 00:11:16 vital-beggar systemd[1]: Starting Container hypervisor based 
on LXC...
  -- Subject: Unit lxd.service has begun start-up
  -- Defined-By: systemd
  -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
  -- 
  -- Unit lxd.service has begun starting up.
  Jul 08 00:11:16 vital-beggar lxd[1712]: p=0x98d18000
  Jul 08 00:11:16 vital-beggar lxd[1712]: fatal error: runtime_lfstackpush: 
invalid pointer
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime stack:
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_dopanic
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/panic.c:135
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_throw
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/panic.c:193
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime.lfstackpush
  Jul 08 00:11:16 vital-beggar lxd[1712]: 
../../../src/libgo/runtime/lfstack.goc:40
  Jul 08 00:11:16 vital-beggar lxd[1712]: getempty
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/mgc0.c:1377
  Jul 08 00:11:16 vital-beggar lxd[1712]: enqueue1
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/mgc0.c:1255
  Jul 08 00:11:16 vital-beggar lxd[1712]: markroot
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/mgc0.c:1285
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_parfordo
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/parfor.c:88
  Jul 08 00:11:16 vital-beggar lxd[1712]: gc
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/mgc0.c:2266
  Jul 08 00:11:16 vital-beggar lxd[1712]: mgc
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/mgc0.c:2211
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_mstart
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/proc.c:1076
  Jul 08 00:11:16 vital-beggar lxd[1712]: goroutine 16 [garbage collection]:
  Jul 08 00:11:16 vital-beggar systemd[1]: lxd.service: Main process exited, 
code=exited, status=2/INVALIDARGUMENT
  Jul 08 00:11:16 vital-beggar systemd[1]: lxd.service: Unit entered failed 
state.
  Jul 08 00:11:16 vital-beggar systemd[1]: lxd.service: Failed with result 
'exit-code'.
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_mcall
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/proc.c:295
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_gc
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/mgc0.c:2187
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_mallocgc
  Jul 08 00:11:16 vital-beggar lxd[1712]: 
../../../src/libgo/runtime/malloc.goc:259
  Jul 08 00:11:16 vital-beggar lxd[1712]: :0
  Jul 08 00:11:16 vital-beggar lxd[1712]: :0
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_main
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/proc.c:626
  Jul 08 00:11:16 vital-beggar lxd[1712]: goroutine 17 [runnable]:
  Jul 08 00:11:16 vital-beggar lxd[1712]: kickoff
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/proc.c:232
  Jul 08 00:11:16 vital-beggar lxd[1712]: created by runtime_main
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/proc.c:598
  Jul 08 00:11:16 vital-beggar lxd[1712]: goroutine 18 [runnable]:
  Jul 08 00:11:16 vital-beggar lxd[1712]: kickoff
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/proc.c:232
  Jul 08 00:11:16 vital-beggar lxd[1712]: created by runtime_createfing
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/mgc0.c:2572
  Jul 08 00:11:16 vital-beggar lxd[1712]: goroutine 19 [runnable]:
  Jul 08 00:11:16 vital-beggar lxd[1712]: kickoff
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/proc.c:232
  Jul 08 00:11:16 vital-beggar lxd[1712]: created by os_signal..import
  Jul 08 00:11:16 vital-beggar lxd[1712]: 
../../../src/libgo/go/os/signal/signal_unix.go:25
  Jul 08 00:11:16 vital-beggar systemd[1]: lxd.service: Service hold-off time 
over, scheduling restart.
  Jul 08 00:11:16 vital-beggar systemd[1]: lxd.service: Start request repeated 
too quickly.
  Jul 08 00:11:16 vital-beggar systemd[1]: Failed to start 

[Touch-packages] [Bug 1472650] Re: [arm64] gccgo runtime crashes with CONFIG_ARM64_PGTABLE_LEVELS=4

[dann frazier]

** Summary changed:

- [arm64] lxd crashes on startup
+ [arm64] gccgo runtime crashes with CONFIG_ARM64_PGTABLE_LEVELS=4

** Package changed: lxd (Ubuntu) = gcc-4.9 (Ubuntu)

** Changed in: gcc-4.9 (Ubuntu)
   Status: New = Confirmed

** Also affects: gcc-4.8 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: gcc-4.8 (Ubuntu)
   Status: New = Confirmed

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

Title:
  [arm64] gccgo runtime crashes with CONFIG_ARM64_PGTABLE_LEVELS=4

Status in gcc-4.8 package in Ubuntu:
  Confirmed
Status in gcc-4.9 package in Ubuntu:
  Confirmed

Bug description:
  lxd 0.12-0ubuntu2
  libgo7/5.1.1-12ubuntu1

  Jul 08 00:11:16 vital-beggar systemd[1]: Starting Container hypervisor based 
on LXC...
  -- Subject: Unit lxd.service has begun start-up
  -- Defined-By: systemd
  -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
  -- 
  -- Unit lxd.service has begun starting up.
  Jul 08 00:11:16 vital-beggar lxd[1712]: p=0x98d18000
  Jul 08 00:11:16 vital-beggar lxd[1712]: fatal error: runtime_lfstackpush: 
invalid pointer
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime stack:
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_dopanic
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/panic.c:135
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_throw
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/panic.c:193
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime.lfstackpush
  Jul 08 00:11:16 vital-beggar lxd[1712]: 
../../../src/libgo/runtime/lfstack.goc:40
  Jul 08 00:11:16 vital-beggar lxd[1712]: getempty
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/mgc0.c:1377
  Jul 08 00:11:16 vital-beggar lxd[1712]: enqueue1
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/mgc0.c:1255
  Jul 08 00:11:16 vital-beggar lxd[1712]: markroot
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/mgc0.c:1285
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_parfordo
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/parfor.c:88
  Jul 08 00:11:16 vital-beggar lxd[1712]: gc
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/mgc0.c:2266
  Jul 08 00:11:16 vital-beggar lxd[1712]: mgc
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/mgc0.c:2211
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_mstart
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/proc.c:1076
  Jul 08 00:11:16 vital-beggar lxd[1712]: goroutine 16 [garbage collection]:
  Jul 08 00:11:16 vital-beggar systemd[1]: lxd.service: Main process exited, 
code=exited, status=2/INVALIDARGUMENT
  Jul 08 00:11:16 vital-beggar systemd[1]: lxd.service: Unit entered failed 
state.
  Jul 08 00:11:16 vital-beggar systemd[1]: lxd.service: Failed with result 
'exit-code'.
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_mcall
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/proc.c:295
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_gc
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/mgc0.c:2187
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_mallocgc
  Jul 08 00:11:16 vital-beggar lxd[1712]: 
../../../src/libgo/runtime/malloc.goc:259
  Jul 08 00:11:16 vital-beggar lxd[1712]: :0
  Jul 08 00:11:16 vital-beggar lxd[1712]: :0
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_main
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/proc.c:626
  Jul 08 00:11:16 vital-beggar lxd[1712]: goroutine 17 [runnable]:
  Jul 08 00:11:16 vital-beggar lxd[1712]: kickoff
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/proc.c:232
  Jul 08 00:11:16 vital-beggar lxd[1712]: created by runtime_main
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/proc.c:598
  Jul 08 00:11:16 vital-beggar lxd[1712]: goroutine 18 [runnable]:
  Jul 08 00:11:16 vital-beggar lxd[1712]: kickoff
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/proc.c:232
  Jul 08 00:11:16 vital-beggar lxd[1712]: created by runtime_createfing
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/mgc0.c:2572
  Jul 08 00:11:16 vital-beggar lxd[1712]: goroutine 19 [runnable]:
  Jul 08 00:11:16 vital-beggar lxd[1712]: kickoff
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/proc.c:232
  Jul 08 00:11:16 vital-beggar lxd[1712]: created by os_signal..import
  Jul 08 00:11:16 vital-beggar lxd[1712]: 
../../../src/libgo/go/os/signal/signal_unix.go:25
  Jul 08 00:11:16 vital-beggar systemd[1]: lxd.service: Service hold-off time 
over, scheduling restart.
  Jul 08 00:11:16 vital-beggar systemd[1]: lxd.service: Start request repeated 
too quickly.
  Jul 08 00:11:16 vital-beggar systemd[1]: Failed to start Container hypervisor 
based on 

[Touch-packages] [Bug 1472650] Re: [arm64] gccgo runtime crashes with CONFIG_ARM64_PGTABLE_LEVELS=4

[dann frazier]

** Also affects: gcc-4.8 (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: gcc-4.9 (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: gcc-4.8 (Ubuntu Wily)
   Importance: Undecided
   Status: Confirmed

** Also affects: gcc-4.9 (Ubuntu Wily)
   Importance: Undecided
   Status: Confirmed

** Also affects: gcc-4.8 (Ubuntu Vivid)
   Importance: Undecided
   Status: New

** Also affects: gcc-4.9 (Ubuntu Vivid)
   Importance: Undecided
   Status: New

** Changed in: gcc-4.8 (Ubuntu Trusty)
   Status: New = Confirmed

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

Title:
  [arm64] gccgo runtime crashes with CONFIG_ARM64_PGTABLE_LEVELS=4

Status in gcc-4.8 package in Ubuntu:
  Confirmed
Status in gcc-4.9 package in Ubuntu:
  Confirmed
Status in gcc-4.8 source package in Trusty:
  Confirmed
Status in gcc-4.9 source package in Trusty:
  New
Status in gcc-4.8 source package in Vivid:
  New
Status in gcc-4.9 source package in Vivid:
  New
Status in gcc-4.8 source package in Wily:
  Confirmed
Status in gcc-4.9 source package in Wily:
  Confirmed

Bug description:
  lxd 0.12-0ubuntu2
  libgo7/5.1.1-12ubuntu1

  Jul 08 00:11:16 vital-beggar systemd[1]: Starting Container hypervisor based 
on LXC...
  -- Subject: Unit lxd.service has begun start-up
  -- Defined-By: systemd
  -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
  -- 
  -- Unit lxd.service has begun starting up.
  Jul 08 00:11:16 vital-beggar lxd[1712]: p=0x98d18000
  Jul 08 00:11:16 vital-beggar lxd[1712]: fatal error: runtime_lfstackpush: 
invalid pointer
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime stack:
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_dopanic
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/panic.c:135
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_throw
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/panic.c:193
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime.lfstackpush
  Jul 08 00:11:16 vital-beggar lxd[1712]: 
../../../src/libgo/runtime/lfstack.goc:40
  Jul 08 00:11:16 vital-beggar lxd[1712]: getempty
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/mgc0.c:1377
  Jul 08 00:11:16 vital-beggar lxd[1712]: enqueue1
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/mgc0.c:1255
  Jul 08 00:11:16 vital-beggar lxd[1712]: markroot
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/mgc0.c:1285
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_parfordo
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/parfor.c:88
  Jul 08 00:11:16 vital-beggar lxd[1712]: gc
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/mgc0.c:2266
  Jul 08 00:11:16 vital-beggar lxd[1712]: mgc
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/mgc0.c:2211
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_mstart
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/proc.c:1076
  Jul 08 00:11:16 vital-beggar lxd[1712]: goroutine 16 [garbage collection]:
  Jul 08 00:11:16 vital-beggar systemd[1]: lxd.service: Main process exited, 
code=exited, status=2/INVALIDARGUMENT
  Jul 08 00:11:16 vital-beggar systemd[1]: lxd.service: Unit entered failed 
state.
  Jul 08 00:11:16 vital-beggar systemd[1]: lxd.service: Failed with result 
'exit-code'.
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_mcall
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/proc.c:295
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_gc
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/mgc0.c:2187
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_mallocgc
  Jul 08 00:11:16 vital-beggar lxd[1712]: 
../../../src/libgo/runtime/malloc.goc:259
  Jul 08 00:11:16 vital-beggar lxd[1712]: :0
  Jul 08 00:11:16 vital-beggar lxd[1712]: :0
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_main
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/proc.c:626
  Jul 08 00:11:16 vital-beggar lxd[1712]: goroutine 17 [runnable]:
  Jul 08 00:11:16 vital-beggar lxd[1712]: kickoff
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/proc.c:232
  Jul 08 00:11:16 vital-beggar lxd[1712]: created by runtime_main
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/proc.c:598
  Jul 08 00:11:16 vital-beggar lxd[1712]: goroutine 18 [runnable]:
  Jul 08 00:11:16 vital-beggar lxd[1712]: kickoff
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/proc.c:232
  Jul 08 00:11:16 vital-beggar lxd[1712]: created by runtime_createfing
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/mgc0.c:2572
  Jul 08 00:11:16 vital-beggar lxd[1712]: goroutine 19 [runnable]:
  Jul 08 00:11:16 vital-beggar lxd[1712]: kickoff
  Jul 08 

[Touch-packages] [Bug 1472650] Re: [arm64] gccgo runtime crashes with CONFIG_ARM64_PGTABLE_LEVELS=4

[dann frazier]

** No longer affects: gcc-4.8 (Ubuntu Trusty)

** No longer affects: gcc-4.8 (Ubuntu Wily)

** No longer affects: gcc-4.8 (Ubuntu Vivid)

** No longer affects: gcc-4.9 (Ubuntu Trusty)

** No longer affects: gcc-4.9 (Ubuntu Vivid)

** No longer affects: gcc-4.9 (Ubuntu Wily)

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

Title:
  [arm64] gccgo runtime crashes with CONFIG_ARM64_PGTABLE_LEVELS=4

Status in gccgo-4.9 package in Ubuntu:
  New
Status in gccgo-5 package in Ubuntu:
  New
Status in gccgo-4.9 source package in Trusty:
  Confirmed
Status in gccgo-5 source package in Trusty:
  New
Status in gccgo-4.9 source package in Vivid:
  New
Status in gccgo-5 source package in Vivid:
  New
Status in gccgo-4.9 source package in Wily:
  New
Status in gccgo-5 source package in Wily:
  New

Bug description:
  lxd 0.12-0ubuntu2
  libgo7/5.1.1-12ubuntu1

  Jul 08 00:11:16 vital-beggar systemd[1]: Starting Container hypervisor based 
on LXC...
  -- Subject: Unit lxd.service has begun start-up
  -- Defined-By: systemd
  -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
  -- 
  -- Unit lxd.service has begun starting up.
  Jul 08 00:11:16 vital-beggar lxd[1712]: p=0x98d18000
  Jul 08 00:11:16 vital-beggar lxd[1712]: fatal error: runtime_lfstackpush: 
invalid pointer
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime stack:
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_dopanic
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/panic.c:135
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_throw
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/panic.c:193
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime.lfstackpush
  Jul 08 00:11:16 vital-beggar lxd[1712]: 
../../../src/libgo/runtime/lfstack.goc:40
  Jul 08 00:11:16 vital-beggar lxd[1712]: getempty
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/mgc0.c:1377
  Jul 08 00:11:16 vital-beggar lxd[1712]: enqueue1
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/mgc0.c:1255
  Jul 08 00:11:16 vital-beggar lxd[1712]: markroot
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/mgc0.c:1285
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_parfordo
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/parfor.c:88
  Jul 08 00:11:16 vital-beggar lxd[1712]: gc
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/mgc0.c:2266
  Jul 08 00:11:16 vital-beggar lxd[1712]: mgc
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/mgc0.c:2211
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_mstart
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/proc.c:1076
  Jul 08 00:11:16 vital-beggar lxd[1712]: goroutine 16 [garbage collection]:
  Jul 08 00:11:16 vital-beggar systemd[1]: lxd.service: Main process exited, 
code=exited, status=2/INVALIDARGUMENT
  Jul 08 00:11:16 vital-beggar systemd[1]: lxd.service: Unit entered failed 
state.
  Jul 08 00:11:16 vital-beggar systemd[1]: lxd.service: Failed with result 
'exit-code'.
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_mcall
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/proc.c:295
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_gc
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/mgc0.c:2187
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_mallocgc
  Jul 08 00:11:16 vital-beggar lxd[1712]: 
../../../src/libgo/runtime/malloc.goc:259
  Jul 08 00:11:16 vital-beggar lxd[1712]: :0
  Jul 08 00:11:16 vital-beggar lxd[1712]: :0
  Jul 08 00:11:16 vital-beggar lxd[1712]: runtime_main
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/proc.c:626
  Jul 08 00:11:16 vital-beggar lxd[1712]: goroutine 17 [runnable]:
  Jul 08 00:11:16 vital-beggar lxd[1712]: kickoff
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/proc.c:232
  Jul 08 00:11:16 vital-beggar lxd[1712]: created by runtime_main
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/proc.c:598
  Jul 08 00:11:16 vital-beggar lxd[1712]: goroutine 18 [runnable]:
  Jul 08 00:11:16 vital-beggar lxd[1712]: kickoff
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/proc.c:232
  Jul 08 00:11:16 vital-beggar lxd[1712]: created by runtime_createfing
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/mgc0.c:2572
  Jul 08 00:11:16 vital-beggar lxd[1712]: goroutine 19 [runnable]:
  Jul 08 00:11:16 vital-beggar lxd[1712]: kickoff
  Jul 08 00:11:16 vital-beggar lxd[1712]: ../../../src/libgo/runtime/proc.c:232
  Jul 08 00:11:16 vital-beggar lxd[1712]: created by os_signal..import
  Jul 08 00:11:16 vital-beggar lxd[1712]: 
../../../src/libgo/go/os/signal/signal_unix.go:25
  Jul 08 00:11:16 vital-beggar systemd[1]: lxd.service: Service hold-off time 
over, scheduling