[10:12] <cpaelzer> jfh: xnox: hey have you seen this on artful: http://paste.ubuntu.com/25871628/ ?
[10:12] <cpaelzer> I'm on a rather old kernel 4.11 in Artful, so I reboot now
[10:12] <cpaelzer> it might all be solved for ages but I wanted to ask to be sure
[10:12] <xnox> cpaelzer, not sure. Is this lpar, z/vm, or kvm?
[10:12] <cpaelzer> usually I remember ASCE differences with KVM, but this seems to pop up every now and then without a guest running
[10:12] <cpaelzer> in lpar
[10:13] <xnox> cpaelzer, are crypto CPACF (?!) instructions enabled in the HMC? and yeah 4.11 is not supported, so do check if you can reproduce with final kernels (4.13?)
[10:13] <cpaelzer> I'll keep the dmesg up after the reboot is complete and IFF it shows again with the most recent kernel I'll file a bug
[10:13] <cpaelzer> xnox: as you see I'm already on repro with 4.13
[10:13] <cpaelzer> :-)
[10:14] <cpaelzer> why would cpacf matter in this case, but well I can check
[10:15] <jfh> cpaelzer: well, there are customer w/o CPACF (even if not many), so that should not be required ...
[10:16] <cpaelzer> I'm on the default with both cpacf checkboxes set
[10:17] <cpaelzer> the error is on a wrong ASCE which I only would connect with KVM - remember the old home/secondary setting
[10:17] <cpaelzer> but as I said no guests required
[10:17] <jfh> ^but didn't saw that so far - tried CDK on s390x on a artful machine last week which is causing heavy load and didn't came across this so far ...
[10:19] <cpaelzer> I have another one on 4.13.0-16-generic without this issue
[10:20] <jfh> cpaelzer: which LPAR are you using?
[10:20] <cpaelzer> so lets assume it was just the too old kernel for now
[10:20] <cpaelzer> s1lp5
[10:26] <jfh> cpaelzer: settings look good ... (anyway, if you want to check if the system is really able to use CPACF just install libica-utils and run icainfo - but looks like 4.13 is fine anyway ...)
[10:27] <cpaelzer> I never asked about cpacf, just referred to xnox question
[10:27] <cpaelzer> but thanks for the double check jfh
[10:28] <cpaelzer> and in any case this dmesg entry might still look known to e.g. hca - any known issue Heiko?
[10:57] <hca> cpaelzer: that looks like a branch into nowhere-land ... if you would happen to know what was mapped at 0x3ff817064e0 then that might give you an idea
[10:58] <hca> but this doesn't have to do anything with cpacf and/or kvm
[10:59] <cpaelzer> hca: I don't know what was around that addr
[10:59] <cpaelzer> hca: thanks for confirming my thoughts on what is not related
[10:59] <cpaelzer> hca: if it happens again I'll look at the addr
[10:59] <cpaelzer> hca: always gpr14 to look at?
[11:00] <cpaelzer> need to find my old docs what usually is in 14
[11:01] <hca> is this included in your kernel: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1708399
[11:01] <hca> ?
[11:03] <cpaelzer> yes that would have been in
[11:03] <cpaelzer> on the kernel I had
[11:04] <cpaelzer> I really think this was just an too-old-non-released-kernel issue, don't spend too much cycles on it if it is not "ah that is Foo"
[12:09] <hca> cpaelzer: gpr14 contains the return address if a function gets called
[12:56] <cpaelzer> I found my  old s390x ELF spec pdf in the meantime
[12:56] <cpaelzer> thanks