Unable to deploy Bionic ppc64le on P8 systems (kernel-panic)

[Po-Hsu Lin]

I can't deploy Bioinc on the P8 system "modoc", it will run into a kernel-panic situation (power9 system works fine).

From the test history, this P8 node was tested with 4.15.0-21, which
mean that the deployment works with some version earlier than
4.15.0-21, and at least it can boot with 4.15.0-21 in the last cycle.

So it's a bit odd to me to see the deployment failure here, as it should
be deployed with working 4.15.0-21 from the last cycle.

And it's not the 4.15.0-23 in -proposed that's causing this this problem, the system was never boot with 4.15.0-21.

+ /var/lib/jenkins/kernel-testing/metal --debug --nc --series=bionic --arch=ppc64el --flavour=generic --required-kernel-version=4.15.0-23.25 --pkg-name=None modoc
 . Provisioner setup
        Releasing...
        Allocating...
        Deploying...
Traceback (most recent call last):
  File "/var/lib/jenkins/kernel-testing/metal", line 212, in <module>
    exit(app.main(args))
  File "/var/lib/jenkins/kernel-testing/metal", line 101, in main
    if metal.provision():
  File "/var/lib/jenkins/kernel-testing/lib/provisioning.py", line 837, in provision
    if not s.ps.provision():
  File "/var/lib/jenkins/kernel-testing/lib/provisioning.py", line 66, in provision
    retval = s.server.provision()
  File "/var/lib/jenkins/kernel-testing/lib/maas.py", line 250, in provision
    s.deploy(s.hostname, s.series, s.arch)
  File "/var/lib/jenkins/kernel-testing/lib/maas.py", line 241, in deploy
    raise MachineDeploymentTimeout('The specified timeout (%d) was reached while waiting for the system (%s) to be deployed.' % ((timeout * 60), hostname))
lib.maas.MachineDeploymentTimeout: The specified timeout (108000) was reached while waiting for the system (modoc) to be deployed.

Output from IPMI console:
[ 1.910940] Loaded X.509 cert 'Build time autogenerated kernel key: c68a20e7bfd228430401173121559235d0c5ceb1'
[ 1.911145] zswap: loaded using pool lzo/zbud
[ 1.911370] Bad kernel stack pointer 7fffd1751cf0 at c00000000000b9ec
[ 1.911429] Oops: Bad kernel stack pointer, sig: 6 [#7]
[ 1.911475] LE SMP NR_CPUS=2048 NUMA PowerNV
[ 1.911522] Modules linked in:
[ 1.911557] CPU: 39 PID: 1218 Comm: modprobe Tainted: G D 4.15.0-22-generic #24-Ubuntu
[ 1.911637] NIP: c00000000000b9ec LR: 0000000000000000 CTR: 0000000000000000
[ 1.911706] REGS: c00000003fe2bd40 TRAP: 0380 Tainted: G D (4.15.0-22-generic)
[ 1.911785] MSR: 9000000000001031 <SF,HV,ME,IR,DR,LE> CR: 00000000 XER: 00000000
[ 1.911856] CFAR: c00000000000b934 SOFTE: -4611686018403131680
[ 1.911856] GPR00: 0000000000000000 00007fffd1751cf0 0000000000000000 0000000000000000
[ 1.911856] GPR04: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
[ 1.911856] GPR08: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
[ 1.911856] GPR12: 00007ef5a4501700 9000000000001000 0000000000000000 0000000000000000
[ 1.911856] GPR16: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
[ 1.911856] GPR20: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
[ 1.911856] GPR24: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
[ 1.911856] GPR28: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
[ 1.912418] NIP [c00000000000b9ec] fast_exception_return+0x9c/0x184
[ 1.912424] LR [0000000000000000] (null)
[ 1.912429] Call Trace:
[ 1.912442] Instruction dump:
[ 1.912476] e84101a0 7c4ff120 e8410170 7c5a03a6 e8010070 e8410080 e8610088 e8810090
[ 1.912547] e8210078 7db243a6 7db142a6 7c0004ac <e9ad0000> 63ff0000 7db242a6 48000010
[ 1.912619] ---[ end trace 44c2744c93d781cc ]---

[Po-Hsu Lin (cypressyew)]

Output from an IPMI console.

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1775855

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Kleber Sacilotto de Souza (kleber-souza)]

This is the same issue as reported on bug 1773162.