From: Jens Axboe <axboe@kernel.dk>
To: Rachel Sibley <rasibley@redhat.com>,
CKI Project <cki-project@redhat.com>,
linux-block@vger.kernel.org
Cc: Xiong Zhou <xzhou@redhat.com>
Subject: Re: 💥 PANICKED: Test report for kernel 5.8.0-rc2-c698ae9.cki (block)
Date: Wed, 1 Jul 2020 10:42:44 -0600 [thread overview]
Message-ID: <a856bc99-eece-f56c-dc79-0ba37979f3dd@kernel.dk> (raw)
In-Reply-To: <8388a5c5-e5b9-e17b-1522-cf742bb23ad9@redhat.com>
On 7/1/20 10:37 AM, Rachel Sibley wrote:
> Hi, we're seeing multiple panics across all arches, I included a snippet of the call trace for both
> xfstests and boot test.
>
> You should be able to inspect in more detail by viewing the console.log under each build/tests directory:
> https://cki-artifacts.s3.us-east-2.amazonaws.com/index.html?prefix=datawarehouse/2020/06/30/609250
This was due to a bad patch series, which since got reverted and redone. Current
tree should be fine.
Now it doesn't matter for this one since I guessed what this was and found it
before the bot did, but I do wish the reports were easier to look at. I should
not have to dig through directories (which were empty when the report went out,
btw) to find logs, then download logs and leaf through hundreds of kb of text
to find out why the bot thought the tree was broken. It should be readily
apparent and in the email. If there's an OOPS, include the oops.
I'd much rather get a separate report for each arch, each having the oops
that got triggered, than get one massive email where it's really not obvious
where to look.
This:
> https://cki-artifacts.s3.us-east-2.amazonaws.com/datawarehouse/2020/06/30/609250/build_ppc64le_redhat%3A926155/tests/8501352/ppc64le_3_console.log
>
> [ 890.198174] run fstests generic/040 at 2020-06-30 12:03:02
> [ 891.055910] BUG: Unable to handle kernel instruction fetch (NULL pointer?)
> [ 891.055942] Faulting instruction address: 0x00000000
> [ 891.055956] Oops: Kernel access of bad area, sig: 11 [#1]
> [ 891.055969] LE PAGE_SIZE=64K MMU=Radix SMP NR_CPUS=2048 NUMA PowerNV
> [ 891.055982] Modules linked in: dm_flakey rpcsec_gss_krb5 auth_rpcgss nfsv4 dns_resolver nfs lockd grace fscache rfkill joydev i40e at24 sunrpc ses
> enclosure scsi_transport_sas regmap_i2c ofpart powernv_flash mtd crct10dif_vpmsum ipmi_powernv ipmi_devintf opal_prd ipmi_msghandler rtc_opal i2c_opal
> ip_tables xfs libcrc32c ast i2c_algo_bit drm_vram_helper drm_kms_helper syscopyarea vmx_crypto sysfillrect sysimgblt crc32c_vpmsum fb_sys_fops
> drm_ttm_helper ttm drm i2c_core aacraid drm_panel_orientation_quirks
> [ 891.056077] CPU: 25 PID: 84211 Comm: systemd-udevd Kdump: loaded Not tainted 5.8.0-rc2-c698ae9.cki #1
> [ 891.056095] NIP: 0000000000000000 LR: c00000000070eef0 CTR: 0000000000000000
> [ 891.056110] REGS: c0000007c25474e0 TRAP: 0400 Not tainted (5.8.0-rc2-c698ae9.cki)
> [ 891.056125] MSR: 9000000040009033 <SF,HV,EE,ME,IR,DR,RI,LE> CR: 24488248 XER: 20040000
> [ 891.056145] CFAR: c00000000070eeec IRQMASK: 0
> [ 891.056145] GPR00: c00000000070f050 c0000007c2547770 c000000001cb7f00 c0000002b6059af8
> [ 891.056145] GPR04: 0000000000000000 c0000007dcf6f000 c0000002b6059af8 0000000000000000
> [ 891.056145] GPR08: 00000007fc940000 c000000001c97d78 0000000000000000 0000000000000000
> [ 891.056145] GPR12: 0000000000000000 c0000007fffe2e00 c0000007c2344400 0000000000000000
> [ 891.056145] GPR16: 0000000000000000 00007fffc9b7cb50 c0000007c2344400 0000000000000000
> [ 891.056145] GPR20: c0000002b307bdd8 0000000000000000 c0000007c2547ca8 c0000007dcf6f000
> [ 891.056145] GPR24: 000000000000000c 000000000000000a c0000007c2547790 0000000000000001
> [ 891.056145] GPR28: 0000000000000000 0000000000000000 00000000ffffffff c0000002b6059af8
> [ 891.056260] NIP [0000000000000000] 0x0
> [ 891.056272] LR [c00000000070eef0] submit_bio_noacct+0x2f0/0x5c0
> [ 891.056285] Call Trace:
> [ 891.056294] [c0000007c2547770] [c00000000070f050] submit_bio_noacct+0x450/0x5c0 (unreliable)
> [ 891.056312] [c0000007c2547800] [c00000000070f228] submit_bio+0x68/0x2d0
> [ 891.056328] [c0000007c25478c0] [c000000000505fe8] mpage_readahead+0x1c8/0x290
> [ 891.056345] [c0000007c25479a0] [c0000000004fd6f8] blkdev_readahead+0x28/0x40
> [ 891.056362] [c0000007c25479c0] [c000000000383980] read_pages+0xb0/0x4a0
> [ 891.056376] [c0000007c2547a40] [c000000000384474] page_cache_readahead_unbounded+0x244/0x300
> [ 891.056395] [c0000007c2547b00] [c00000000037445c] generic_file_buffered_read+0x9bc/0x1120
> [ 891.056411] [c0000007c2547c50] [c0000000004fddc0] blkdev_read_iter+0x50/0x80
> [ 891.056428] [c0000007c2547c70] [c000000000493c64] new_sync_read+0x124/0x1a0
> [ 891.056443] [c0000007c2547d10] [c000000000496e30] vfs_read+0x100/0x200
> [ 891.056471] [c0000007c2547d70] [c000000000497368] ksys_read+0x78/0x130
> [ 891.056487] [c0000007c2547dc0] [c000000000030564] system_call_exception+0xe4/0x170
> [ 891.056504] [c0000007c2547e20] [c00000000000ca70] system_call_common+0xf0/0x278
> [ 891.056518] Instruction dump:
> [ 891.056529] XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX
> [ 891.056545] XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX
> [ 891.056564] ---[ end trace 14197a45ec121b51 ]---
Is what should be in the email, that's the important part.
--
Jens Axboe
next prev parent reply other threads:[~2020-07-01 16:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-01 13:06 💥 PANICKED: Test report for kernel 5.8.0-rc2-c698ae9.cki (block) CKI Project
2020-07-01 16:37 ` Rachel Sibley
2020-07-01 16:42 ` Jens Axboe [this message]
2020-07-01 17:16 ` Rachel Sibley
2020-07-01 17:21 ` Jens Axboe
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=a856bc99-eece-f56c-dc79-0ba37979f3dd@kernel.dk \
--to=axboe@kernel.dk \
--cc=cki-project@redhat.com \
--cc=linux-block@vger.kernel.org \
--cc=rasibley@redhat.com \
--cc=xzhou@redhat.com \
/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).