Matt, can you post the output of `dmesg` from the affected system. I
have not seen the compiler fix land in trusty-updates yet and the best
way to spot this is looking in dmesg.

On Fri, Jul 4, 2014 at 8:43 AM, Matt Bruzek
<email address hidden> wrote:
> I upgraded to the latest version of juju 1.20.0 and I got yet another
> panic on the Power systems.
>
> The original error reported in this bug is still present in the logs:
> 2014-07-03 19:54:07 DEBUG juju.worker.rsyslog worker.go:164 Reloading rsyslog configuration
> panic: runtime error: invalid memory address or nil pointer dereference
> [signal 0xb code=0x1 addr=0x0]
>
>
> $ juju --version
> 1.20.0-trusty-ppc64
>
> $ cat /proc/cpuinfo
> processor       : 0
> cpu             : POWER8E (raw), altivec supported
> clock           : 4116.000000MHz
> revision        : 2.0 (pvr 004b 0200)
>
> processor       : 1
> cpu             : POWER8E (raw), altivec supported
> clock           : 4116.000000MHz
> revision        : 2.0 (pvr 004b 0200)
>
> timebase        : 512000000
> platform        : pSeries
> model           : IBM pSeries (emulated by qemu)
> machine         : CHRP IBM pSeries (emulated by qemu)
>
>
> Machine logs are attached please let me know if there is any other information you need.
>
> ** Attachment added: "The machine logs from version 1.20.0 of juju running on Power."
>    https://bugs.launchpad.net/juju-core/+bug/1336891/+attachment/4145051/+files/machine_logs_1.20.tar.gz
>
> --
> You received this bug notification because you are subscribed to juju-
> core.
> Matching subscriptions: MOAR JUJU SPAM!
> https://bugs.launchpad.net/bugs/1336891
>
> Title:
>    intermittent panic: runtime error: invalid memory address
>
> Status in juju-core:
>   Triaged
>
> Bug description:
>   I am doing some Juju testing on the IBM power system and I found a
>   juju-core panic on 3 of the 4 systems.  The signal values are
>   different but the stack traces on machine-0 and machine-1 look the
>   same.  But machine-2's stack trace is slightly different.
>
>   Here is the stack trace from the machine-0.log file.
>
>   panic: runtime error: invalid memory address or nil pointer dereference
>   [signal 0xb code=0x1 addr=0x0]
>
>   goroutine 14 [running]:
>
>   goroutine 1 [chan receive]:
>   launchpad.net_tomb.Wait.pN23_launchpad.net_tomb.Tomb
>         /build/buildd/juju-core-1.18.4/src/launchpad.net/tomb/tomb.go:110
>   launchpad.net_juju_core_worker.Wait.pN37_launchpad.net_juju_core_worker.runner
>         /build/buildd/juju-core-1.18.4/src/launchpad.net/juju-core/worker/runner.go:124
>   main.Run.pN17_main.MachineAgent
>         /build/buildd/juju-core-1.18.4/src/launchpad.net/juju-core/cmd/jujud/machine.go:166
>   launchpad.net_juju_core_cmd.Run.pN40_launchpad.net_juju_core_cmd.SuperCommand
>         /build/buildd/juju-core-1.18.4/src/launchpad.net/juju-core/cmd/supercommand.go:303
>   launchpad.net_juju_core_cmd.Main
>         /build/buildd/juju-core-1.18.4/src/launchpad.net/juju-core/cmd/cmd.go:244
>   main.jujuDMain
>         /build/buildd/juju-core-1.18.4/src/launchpad.net/juju-core/cmd/jujud/main.go:107
>   main.Main
>         /build/buildd/juju-core-1.18.4/src/launchpad.net/juju-core/cmd/jujud/main.go:122
>   main.main
>         /build/buildd/juju-core-1.18.4/src/launchpad.net/juju-core/cmd/jujud/main.go:139
>
>
>   The version of Juju I am using is: 1.18.4
>   $ juju --version
>   1.18.4-trusty-ppc64
>
>   The version of kernel is 3.13.0-30
>   $ uname -a
>   Linux stilson-01 3.13.0-30-generic #54-Ubuntu SMP Mon Jun 9 22:46:02 UTC 2014 ppc64le ppc64le ppc64le GNU/Linux
>
>   Please let me know if you need any more information.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju-core/+bug/1336891/+subscriptions