From: Jan Kara <jack@suse.cz>
To: Chris Murphy <lists@colorremedies.com>
Cc: "Jan Kara" <jack@suse.cz>,
"Holger Hoffstätte" <holger@applied-asynchrony.com>,
"Nikolay Borisov" <nborisov@suse.com>,
"Jens Axboe" <axboe@kernel.dk>,
"Paolo Valente" <paolo.valente@linaro.org>,
Linux-RAID <linux-raid@vger.kernel.org>,
linux-block <linux-block@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
"Josef Bacik" <josef@toxicpanda.com>
Subject: Re: stalling IO regression since linux 5.12, through 5.18
Date: Wed, 17 Aug 2022 20:15:54 +0200 [thread overview]
Message-ID: <20220817181554.znqljc6mmci45ukd@quack3> (raw)
In-Reply-To: <51cd43f9-ab6b-4dd6-814f-e0c1ace3143c@www.fastmail.com>
On Wed 17-08-22 13:57:00, Chris Murphy wrote:
> On Wed, Aug 17, 2022, at 12:47 PM, Chris Murphy wrote:
> Can you boot with
> >> "megaraid_sas.host_tagset_enable = 0" kernel option and see whether the
> >> issue reproduces?
>
> This has been running an hour without symptoms. It's strongly suggestive,
> but needs to run overnight to be sure. Anecdotally, the max write IO is
> less than what I'm used to seeing.
OK, if this indeed passes then b6e68ee82585 ("blk-mq: Improve performance
of non-mq IO schedulers with multiple HW queues") might be what's causing
issues (although I don't know how yet...).
Honza
>
> [ 0.583121] Kernel command line: BOOT_IMAGE=(md/0)/vmlinuz-5.12.5-300.fc34.x86_64 root=UUID=04f1fb7f-5cc4-4dfb-a7cf-b6b6925bf895 ro rootflags=subvol=root rd.md.uuid=e7782150:092e161a:68395862:31375bca biosdevname=1 net.ifnames=0 log_buf_len=8M plymouth.enable=0 megaraid_sas.host_tagset_enable=0
> ...
> [ 6.745964] megasas: 07.714.04.00-rc1
> [ 6.758472] megaraid_sas 0000:02:00.0: BAR:0x1 BAR's base_addr(phys):0x0000000092000000 mapped virt_addr:0x00000000c54554ff
> [ 6.758477] megaraid_sas 0000:02:00.0: FW now in Ready state
> [ 6.770658] megaraid_sas 0000:02:00.0: 63 bit DMA mask and 32 bit consistent mask
> [ 6.795060] megaraid_sas 0000:02:00.0: firmware supports msix : (96)
> [ 6.807537] megaraid_sas 0000:02:00.0: requested/available msix 49/49
> [ 6.819259] megaraid_sas 0000:02:00.0: current msix/online cpus : (49/48)
> [ 6.830800] megaraid_sas 0000:02:00.0: RDPQ mode : (disabled)
> [ 6.842031] megaraid_sas 0000:02:00.0: Current firmware supports maximum commands: 928 LDIO threshold: 0
> [ 6.871246] megaraid_sas 0000:02:00.0: Performance mode :Latency (latency index = 1)
> [ 6.882265] megaraid_sas 0000:02:00.0: FW supports sync cache : No
> [ 6.893034] megaraid_sas 0000:02:00.0: megasas_disable_intr_fusion is called outbound_intr_mask:0x40000009
> [ 6.988550] megaraid_sas 0000:02:00.0: FW provided supportMaxExtLDs: 1 max_lds: 64
> [ 6.988554] megaraid_sas 0000:02:00.0: controller type : MR(2048MB)
> [ 6.988555] megaraid_sas 0000:02:00.0: Online Controller Reset(OCR) : Enabled
> [ 6.988556] megaraid_sas 0000:02:00.0: Secure JBOD support : No
> [ 6.988557] megaraid_sas 0000:02:00.0: NVMe passthru support : No
> [ 6.988558] megaraid_sas 0000:02:00.0: FW provided TM TaskAbort/Reset timeout : 0 secs/0 secs
> [ 6.988559] megaraid_sas 0000:02:00.0: JBOD sequence map support : No
> [ 6.988560] megaraid_sas 0000:02:00.0: PCI Lane Margining support : No
> [ 7.025160] megaraid_sas 0000:02:00.0: megasas_enable_intr_fusion is called outbound_intr_mask:0x40000000
> [ 7.025162] megaraid_sas 0000:02:00.0: INIT adapter done
> [ 7.025164] megaraid_sas 0000:02:00.0: JBOD sequence map is disabled megasas_setup_jbod_map 5707
> [ 7.029878] megaraid_sas 0000:02:00.0: pci id : (0x1000)/(0x005d)/(0x1028)/(0x1f47)
> [ 7.029881] megaraid_sas 0000:02:00.0: unevenspan support : yes
> [ 7.029882] megaraid_sas 0000:02:00.0: firmware crash dump : no
> [ 7.029883] megaraid_sas 0000:02:00.0: JBOD sequence map : disabled
> [ 7.029915] megaraid_sas 0000:02:00.0: Max firmware commands: 927 shared with nr_hw_queues = 1
> [ 7.029918] scsi host11: Avago SAS based MegaRAID driver
>
>
>
>
> --
> Chris Murphy
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2022-08-17 18:16 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-10 16:35 stalling IO regression in linux 5.12 Chris Murphy
2022-08-10 17:48 ` Josef Bacik
2022-08-10 18:33 ` Chris Murphy
2022-08-10 18:42 ` Chris Murphy
2022-08-10 19:31 ` Josef Bacik
2022-08-10 19:34 ` Chris Murphy
2022-08-12 16:05 ` stalling IO regression since linux 5.12, through 5.18 Chris Murphy
2022-08-12 17:59 ` Josef Bacik
2022-08-12 18:02 ` Jens Axboe
2022-08-14 20:28 ` Chris Murphy
2022-08-16 14:22 ` Chris Murphy
2022-08-16 15:25 ` Nikolay Borisov
2022-08-16 15:34 ` Chris Murphy
2022-08-17 9:52 ` Holger Hoffstätte
2022-08-17 11:49 ` Jan Kara
2022-08-17 14:37 ` Chris Murphy
2022-08-17 15:09 ` Chris Murphy
2022-08-17 16:30 ` Jan Kara
2022-08-17 16:47 ` Chris Murphy
2022-08-17 17:57 ` Chris Murphy
2022-08-17 18:15 ` Jan Kara [this message]
2022-08-17 18:18 ` Chris Murphy
2022-08-17 18:33 ` Jan Kara
2022-08-17 18:54 ` Chris Murphy
2022-08-17 19:23 ` Chris Murphy
2022-08-18 2:31 ` Chris Murphy
2022-08-17 18:21 ` Holger Hoffstätte
2022-08-17 11:57 ` Chris Murphy
2022-08-17 12:31 ` Holger Hoffstätte
2022-08-17 18:16 ` Chris Murphy
2022-08-17 18:38 ` Holger Hoffstätte
2022-08-17 12:06 ` Ming Lei
2022-08-17 14:34 ` Chris Murphy
2022-08-17 14:53 ` Ming Lei
2022-08-17 15:02 ` Chris Murphy
2022-08-17 15:34 ` Ming Lei
2022-08-17 16:34 ` Chris Murphy
2022-08-18 1:03 ` Ming Lei
2022-08-18 2:30 ` Chris Murphy
2022-08-18 3:24 ` Ming Lei
2022-08-18 4:12 ` Chris Murphy
2022-08-18 4:18 ` Chris Murphy
2022-08-18 4:27 ` Chris Murphy
2022-08-18 4:32 ` Chris Murphy
2022-08-18 5:15 ` Ming Lei
2022-08-18 18:52 ` Chris Murphy
2022-08-18 5:24 ` Ming Lei
2022-08-18 13:50 ` Chris Murphy
2022-08-18 15:10 ` Ming Lei
2022-08-19 19:20 ` Chris Murphy
2022-08-20 7:00 ` Ming Lei
2022-09-01 7:02 ` Yu Kuai
2022-09-01 8:03 ` Jan Kara
2022-09-01 8:19 ` Yu Kuai
2022-09-06 9:49 ` Paolo Valente
2022-09-02 16:53 ` Chris Murphy
2022-09-06 9:45 ` Paolo Valente
2022-08-15 11:25 ` stalling IO regression in linux 5.12 Thorsten Leemhuis
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=20220817181554.znqljc6mmci45ukd@quack3 \
--to=jack@suse.cz \
--cc=axboe@kernel.dk \
--cc=holger@applied-asynchrony.com \
--cc=josef@toxicpanda.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=lists@colorremedies.com \
--cc=nborisov@suse.com \
--cc=paolo.valente@linaro.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