Description of problem: The kexec reboot failed with below CKI kernel: Linux version 5.20.0-0.rc0.3bc1bc0b59d0.9.test.fc37 The back trace is pasted here. And the full log can be checked in: https://s3.us-east-1.amazonaws.com/arr-cki-prod-datawarehouse-public/datawarehouse-public/2022/08/12/redhat:611241552/build_s390x_redhat:611241552_s390x/tests/3/results_0001/console.log/console.log ==== [ 13.767212] Unable to handle kernel pointer dereference in virtual kernel add ress space [ 13.767222] Failing address: 000000022a04d000 TEID: 000000022a04d403 [ 13.767225] Fault in home space mode while using kernel ASCE. [ 13.767230] AS:000000007bf0c007 R3:0000000000000024 [ 13.767280] Oops: 003b ilc:2 [#1] SMP [ 13.767286] Modules linked in: sunrpc qeth_l2 bridge stp llc qeth qdio ccwgro up zcrypt_cex4 vfio_ccw mdev vfio_iommu_type1 vfio fuse zram xfs crc32_vx_s390 g hash_s390 prng aes_s390 des_s390 libdes sha512_s390 sha256_s390 sha1_s390 sha_co mmon dasd_eckd_mod dasd_mod pkey zcrypt [ 13.767315] Unloaded tainted modules: s390_trng():1 s390_trng():1 sha3_512_s 90():1 sha3_512_s390():1 sha3_256_s390():1 sha3_256_s390():1 sha3_512_s390():1 s ha3_256_s390():1 sha3_512_s390():1 sha3_256_s390():1 [ 13.767334] CPU: 1 PID: 1205 Comm: anamon Tainted: G W ------- --- 5.20.0-0.rc0.3bc1bc0b59d0.9.test.fc37.s390x #1 [ 13.767340] Hardware name: IBM 2964 N96 400 (z/VM 6.4.0) [ 13.767344] Krnl PSW : 0704e00180000000 000000007ad53ff2 (inet_ehash_insert+0 xba/0x2e0)00: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop from CPU 00. 00: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop from CPU 01. [ 13.767365] R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:2 PM:0 RI: 0 EA:3 [ 13.767369] Krnl GPRS: c6928754f226d278 0000000000000000 0000000200000002 000 00000073a72da [ 13.767372] 000000002c8ea9e8 00000000486419d9 0000000000001f40 000 000004303b880 [ 13.767374] 0000000000000000 0000000000000000 000000022a04dc50 000 000004f021400 [ 13.767376] 000000004499a100 0000000000000000 000000007ad54156 000 00380412b79d0 [ 13.767386] Krnl Code: 000000007ad53fe6: b90400a2 lgr %r10,%r2 [ 13.767386] 000000007ad53fea: a7180000 lhi %r1,0 [ 13.767386] #000000007ad53fee: 582003ac l %r2,940 [ 13.767386] >000000007ad53ff2: ba12a000 cs %r1,%r2, 0(%r10) [ 13.767386] 000000007ad53ff6: ec1600ea007e cij %r1,0,6, 000000007ad541ca [ 13.767386] 000000007ad53ffc: ec980053007c cgij %r9,0,8, 000000007ad540a2 [ 13.767386] 000000007ad54002: d503b0089008 clc 8(4,%r11 ),8(%r9) [ 13.767386] 000000007ad54008: a77400ec brc 7,000000 007ad541e0 [ 13.767407] Call Trace: [ 13.767409] [<000000007ad53ff2>] inet_ehash_insert+0xba/0x2e0 [ 13.767413] ([<000000007ad54156>] inet_ehash_insert+0x21e/0x2e0) [ 13.767416] [<000000007ad5423e>] inet_ehash_nolisten+0x26/0xb8 [ 13.767419] [<000000007ad54a9e>] __inet_hash_connect+0x4e6/0x568 [ 13.767431] [<000000007ae39a6e>] tcp_v6_connect+0x3ee/0x5c8 [ 13.767436] [<000000007ad988bc>] __inet_stream_connect+0x104/0x3b8 [ 13.767440] [<000000007ad98bc6>] inet_stream_connect+0x56/0x80 [ 13.767443] [<000000007ac5d332>] __sys_connect+0x8a/0xb8 [ 13.767449] [<000000007ac5f50c>] __do_sys_socketcall+0x15c/0x348 [ 13.767452] [<000000007aeed4bc>] __do_syscall+0x1d4/0x1f8 [ 13.767458] [<000000007aefd742>] system_call+0x82/0xb0 [ 13.767464] Last Breaking-Event-Address: [ 13.767465] [<000000007ad54156>] inet_ehash_insert+0x21e/0x2e0 [ 13.767470] Kernel panic - not syncing: Fatal exception in interrupt 01: HCPGIR450W CP entered; disabled wait PSW 00020001 80000000 00000000 7A2BF806 Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Hi Dan and Philipp, anything that sounds familiar to you or should I mirror this to IBM? Thanks
I suppose this is a new thing, but I would like to have a confirmation from 6.0-rc1 or even 6.0-rc2. The 5.20.0-0.rc0.3bc1bc0b59d0 kernel is very WIP snapshot.
Any update for this. From our CKI side, no new issue reported again on this, wondering if we can close this.
(In reply to Baoquan He from comment #3) > Any update for this. From our CKI side, no new issue reported again on this, > wondering if we can close this. I believe we can close it.
(In reply to Dan Horák from comment #4) > (In reply to Baoquan He from comment #3) > > Any update for this. From our CKI side, no new issue reported again on this, > > wondering if we can close this. > > I believe we can close it. Thanks, let me close it.