From: Tommy Kelly <linux@tkel.ly>
To: Niklas Cassel <cassel@kernel.org>
Cc: Damien Le Moal <dlemoal@kernel.org>,
linux-ide@vger.kernel.org, John Garry <john.g.garry@oracle.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>
Subject: Re: [PATCH v4 0/4] ata: fix deferred QC handling for port multipliers
Date: Wed, 13 May 2026 23:48:51 -0700 [thread overview]
Message-ID: <8947edc4-85f7-45fe-b8db-3266ea2fcdba@tkel.ly> (raw)
In-Reply-To: <agVuwX1I1CX5EBMP@fedora>
On 5/13/26 23:42, Niklas Cassel wrote:
> Hello Tommy,
>
> On Wed, May 13, 2026 at 09:42:35PM -0700, Tommy Kelly wrote:
>>
>>> U-Boot 2026.07-rc2-dirty
>>> kernel: Linux version 7.1.0-0.rc3.1d5dcaa3bd65.25.test.fc44.aarch64
>>> [ 1539.481926] BTRFS error (device nvme0n1p4 state EA): run_delalloc_nocow failed, root=5 inode=103820306 start=274432 len=4096 cur_offset=274432 oe_cleanup=274432 oe_cleanup_len=0 untouched_start=274432 untouched_len=4096: -5
>>> [ 1539.483785] BTRFS error (device nvme0n1p4 state EA): failed to run delalloc range, root=5 ino=103820306 folio=274432 submit_bitmap=0 start=274432 len=4096: -5
>>> [ 1596.136409] systemd-journald[800]: Failed to rotate /var/log/journal/c5b05402ed674946a0b721d8b2c649d1/system.journal: Read-only file system (Dropped 122276 similar message(s))
>>
>> Those 2 `BTRFS error` lines repeated over and over every couple seconds.
>>
>> This one seems to happen randomly, unable to reproduce consistently.
>> No idea why its happening.
>> But it has happened with both patched and un-patched u-boot devicetree.
>
> Thanks a lot for testing!
>
> The problem with PMP CBS is my fault, I made a mistake when creating V4.
>
> The btrfs bug seems to be unrelated, even though it seems very bad.
>
> It is good that you have UART so you could see what was going on.
>
> Perhaps you could test on v7.0 (hopefully btrfs is more stable here) +
> v5 of this patch series (once I've sent it out).
>
> I'm sorry for my mistake... hopefully it will not go beyond v5.
>
>
> Kind regards,
> Niklas
Hi Niklas,
I'll test v5 with CBS + FBS, no problem.
I just discovered SysRq + R (Replay the kernel log messages).
I will try that over serial next time it happens.
Thanks,
Tommy
next prev parent reply other threads:[~2026-05-14 6:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-13 15:13 [PATCH v4 0/4] ata: fix deferred QC handling for port multipliers Niklas Cassel
2026-05-13 15:14 ` [PATCH v4 1/4] ata: libata-scsi: improve readability of ata_scsi_qc_issue() Niklas Cassel
2026-05-13 15:14 ` [PATCH v4 2/4] ata: libata-scsi: do not use the deferred QC feature for ATA_DEFER_PORT Niklas Cassel
2026-05-13 15:14 ` [PATCH v4 3/4] ata: libata-scsi: do not use the deferred QC feature on PMPs with CBS Niklas Cassel
2026-05-14 6:19 ` sashiko-bot
2026-05-14 6:30 ` Niklas Cassel
2026-05-13 15:14 ` [PATCH v4 4/4] ata: libata-scsi: do not needlessly defer commands when using PMP with FBS Niklas Cassel
2026-05-14 10:05 ` sashiko-bot
2026-05-14 11:08 ` Niklas Cassel
2026-05-14 4:09 ` [PATCH v4 0/4] ata: fix deferred QC handling for port multipliers Tommy Kelly
2026-05-14 4:42 ` Tommy Kelly
2026-05-14 6:42 ` Niklas Cassel
2026-05-14 6:48 ` Tommy Kelly [this message]
2026-05-14 6:49 ` Niklas Cassel
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=8947edc4-85f7-45fe-b8db-3266ea2fcdba@tkel.ly \
--to=linux@tkel.ly \
--cc=cassel@kernel.org \
--cc=dlemoal@kernel.org \
--cc=john.g.garry@oracle.com \
--cc=linux-ide@vger.kernel.org \
--cc=martin.petersen@oracle.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