From: Major Hayden <major@redhat.com>
To: Linux Stable maillist <stable@vger.kernel.org>
Subject: Re: ✅ PASS: Test report for kernel 5.2.9-rc1-2440e48.cki (stable)
Date: Thu, 15 Aug 2019 07:22:41 -0500 [thread overview]
Message-ID: <255f9af4-6087-7f56-5860-5aa0397a7631@redhat.com> (raw)
In-Reply-To: <cki.BF9724DF28.NB2ZULIYXL@redhat.com>
On 8/15/19 2:23 AM, CKI Project wrote:
> Host 2:
> ✅ Boot test [0]
> ✅ xfstests: ext4 [29]
> ✅ xfstests: xfs [29]
> ✅ selinux-policy: serge-testsuite [30]
> ⚡⚡⚡ lvm thinp sanity [31]
> ⚡⚡⚡ storage: software RAID testing [32]
> 🚧 ❌ Storage blktests [34]
The blktests suite has normally passed for the patches in the stable queue on ppc64le, but caused a kernel panic this time around:
> [ 7101.664469] run blktests nvme/004 at 2019-08-14 21:47:13
> [ 7101.790613] nvmet: adding nsid 1 to subsystem blktests-subsystem-1
> [ 7101.911992] nvmet: creating controller 1 for subsystem blktests-subsystem-1 for NQN nqn.2014-08.org.nvmexpress:uuid:ca0ba025-7552-4280-aa1b-1b73939b8b1c.
> [ 7101.912194] nvme nvme1: creating 120 I/O queues.
> [ 7101.930157] BUG: Unable to handle kernel data access at 0x800a00066b9e7e28
> [ 7101.930185] Faulting instruction address: 0xc00000000067b230
> [ 7101.930199] Oops: Kernel access of bad area, sig: 11 [#1]
> [ 7101.930211] LE PAGE_SIZE=64K MMU=Radix MMU=Hash SMP NR_CPUS=1024 NUMA PowerNV
> [ 7101.930244] Modules linked in: nvme_loop nvme_fabrics nvmet loop crypto_user nfnetlink scsi_transport_iscsi xt_multiport bluetooth ecdh_generic rfkill ecc overlay ip6table_security ip6_tables xt_CONNSECMARK xt_SECMARK xt_state xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_security ah6 ah4 sctp dm_log_writes dm_flakey at24 regmap_i2c joydev i40e ses enclosure ofpart powernv_flash vmx_crypto mtd rtc_opal opal_prd ipmi_powernv ipmi_devintf ipmi_msghandler i2c_opal crct10dif_vpmsum sunrpc ip_tables xfs libcrc32c ast i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops ttm drm crc32c_vpmsum nvme nvme_core mpt3sas drm_panel_orientation_quirks aacraid i2c_core raid_class scsi_transport_sas [last unloaded: null_blk]
> [ 7101.930371] CPU: 99 PID: 66936 Comm: nvme Not tainted 5.2.9-rc1-2440e48.cki #1
> [ 7101.930385] NIP: c00000000067b230 LR: c00000000067b1d4 CTR: c000000000029140
> [ 7101.930400] REGS: c00020391ccc35c0 TRAP: 0300 Not tainted (5.2.9-rc1-2440e48.cki)
> [ 7101.930413] MSR: 900000000280b033 <SF,HV,VEC,VSX,EE,FP,ME,IR,DR,RI,LE> CR: 44002228 XER: 20040000
> [ 7101.930433] CFAR: c0000000001d9e28 DAR: 800a00066b9e7e28 DSISR: 40000000 IRQMASK: 0
> GPR00: c00000000067b1d4 c00020391ccc3850 c0000000016cdb00 0000067578a4ab31
> GPR04: 0000000000000000 ffffffffffffffff 0000000001f3fb0e 0000000000000001
> GPR08: 800a00066b9e7d80 800a00066b9e7d80 0000000000000001 c00800000cd5db88
> GPR12: c000000000029140 c000203fff6b9800 0000000000000008 c00800000d5751e0
> GPR16: c000203985a8a6c0 c00800000e013278 c000203985a8a700 0000000000000038
> GPR20: 0000000000000030 0000000000000028 0000000000000020 fffffffffffff000
> GPR24: 0000000000000001 0000000000000400 0000000000000000 0000000000000023
> GPR28: 0000000000000000 0000000000000000 c00020391ccc38c8 c000003ef1b00000
> [ 7101.930544] NIP [c00000000067b230] blk_mq_get_request+0x260/0x4b0
> [ 7101.930557] LR [c00000000067b1d4] blk_mq_get_request+0x204/0x4b0
> [ 7101.930569] Call Trace:
> [ 7101.930577] [c00020391ccc3850] [c00000000067b1d4] blk_mq_get_request+0x204/0x4b0 (unreliable)
> [ 7101.930594] [c00020391ccc38a0] [c00000000067b688] blk_mq_alloc_request_hctx+0x108/0x1b0
> [ 7101.930617] [c00020391ccc3910] [c00800000cd51aac] nvme_alloc_request+0x54/0xe0 [nvme_core]
> [ 7101.930633] [c00020391ccc3940] [c00800000cd5641c] __nvme_submit_sync_cmd+0x64/0x290 [nvme_core]
> [ 7101.930651] [c00020391ccc39c0] [c00800000d571650] nvmf_connect_io_queue+0x148/0x1e0 [nvme_fabrics]
> [ 7101.930668] [c00020391ccc3ab0] [c00800000e0106b0] nvme_loop_connect_io_queues+0x98/0xf8 [nvme_loop]
> [ 7101.930684] [c00020391ccc3af0] [c00800000e01116c] nvme_loop_create_ctrl+0x434/0x6a0 [nvme_loop]
> [ 7101.930700] [c00020391ccc3bd0] [c00800000d5724f0] nvmf_dev_write+0xd38/0x124c [nvme_fabrics]
> [ 7101.930719] [c00020391ccc3d60] [c000000000421e58] __vfs_write+0x38/0x70
> [ 7101.930731] [c00020391ccc3d80] [c000000000426188] vfs_write+0xd8/0x250
> [ 7101.930744] [c00020391ccc3dd0] [c000000000426558] ksys_write+0x78/0x130
> [ 7101.930758] [c00020391ccc3e20] [c00000000000bde4] system_call+0x5c/0x70
> [ 7101.930770] Instruction dump:
> [ 7101.930780] f91f0108 f91f0110 e91e0018 41820018 576a051c 554a0368 7d4a0034 554ad97e
> [ 7101.930796] 69490001 79291f24 38e00001 7d284a14 <e94900a8> 394a0001 f94900a8 90ff00d4
> [ 7101.930815] ---[ end trace 46fccc83bf29e598 ]---
We are still taking a look at this one but I figured it was worth mentioning here. :)
--
Major Hayden
prev parent reply other threads:[~2019-08-15 12:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-15 7:23 ✅ PASS: Test report for kernel 5.2.9-rc1-2440e48.cki (stable) CKI Project
2019-08-15 12:22 ` Major Hayden [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=255f9af4-6087-7f56-5860-5aa0397a7631@redhat.com \
--to=major@redhat.com \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).