Bug#1120831: Acknowledgement (eslinux-image-6.17.8+deb14-amd64: failed command: READ FPDMA QUEUED after boot)

[Salvatore Bonaccorso <carnil@debian.org>]

Hi Wolf

Please always include the Debian bug address as well. This can be done
by a normal reply-to or including 1120831@bugs.debian.org manually.

On Sat, Jan 10, 2026 at 06:40:18PM +0000, Wolf wrote:
> 
> On Saturday, 10 January 2026 at 14:13, Salvatore Bonaccorso <carnil@debian.org> wrote:
> 
> >
> >
> > Hi Wolf,
> >
> > On Wed, Jan 07, 2026 at 03:10:59PM +0000, Wolf wrote:
> >
> > > On Wednesday, 7 January 2026 at 11:29, Salvatore Bonaccorso carnil@debian.org wrote:
> > >
> > > > Hi,
> > >
> > > > On Wed, Jan 07, 2026 at 04:41:21AM +0000, Wolf wrote:
> > >
> > > > > Hi Salvatore,
> > >
> > > > > I did a new test against v6.17-rc1, which is the first bugged version after v6.16.
> > >
> > > > > root@gdeltop# git bisect log
> > > > > git bisect start
> > > > > # status: waiting for both good and bad commits
> > > > > # good: [038d61fd642278bab63ee8ef722c50d10ab01e8f] Linux 6.16
> > > > > git bisect good 038d61fd642278bab63ee8ef722c50d10ab01e8f
> > > > > # status: waiting for bad commit, 1 good commit known
> > > > > # bad: [8f5ae30d69d7543eee0d70083daf4de8fe15d585] Linux 6.17-rc1
> > > > > git bisect bad 8f5ae30d69d7543eee0d70083daf4de8fe15d585
> > >
> > > > Yes, but now according to the outlined procedure you need to continue
> > > > with the commits as described until you get the first bad commit.
> > >
> > > > Regards,
> > > > Salvatore
> > >
> > > Hi, Salvatore,
> > >
> > > I tested, as you suggested, the good v6.16 vs. v6.17, I found the bug and I sent you the first mail with the bisect log.
> > >
> > > Then I found (https://github.com/torvalds/linux/tags?after=v6.18-rc3) that there are 7 release
> > >
> > > candidates before v6.17 and I decided to reset bisect and to test each of them until I find the bug.
> > >
> > > I found the bug in first of them (v6.17-rc1) and sent you the second mail.
> > >
> > > Is not this, v6.17-rc1, the bad one?
> >
> >
> > We seem to not understand each other :). I pointed out how the
> > bisection between the two versions should happen. Once you started
> > with the bisect, and marked one bad and one good version you will be
> > pointed to the next commit to test. You should test this one according
> > to the outlined procedure and then based on the result you get, mark
> > it as good or bad. A couple of steps will be required until you have
> > pinpointed the first bad commit, at which point we can move further.
> >
> > Hope this helps,
> >
> > Regards,
> > Salvatore
> 
> Hi, Salvatore,
> 
> I tested all from v6.16 to v6.17-rc1, here is the log:
> 
> git bisect start
> # status: waiting for both good and bad commits
> # good: [038d61fd642278bab63ee8ef722c50d10ab01e8f] Linux 6.16
> git bisect good 038d61fd642278bab63ee8ef722c50d10ab01e8f
> # status: waiting for bad commit, 1 good commit known
> # bad: [8f5ae30d69d7543eee0d70083daf4de8fe15d585] Linux 6.17-rc1
> git bisect bad 8f5ae30d69d7543eee0d70083daf4de8fe15d585
> # bad: [8be4d31cb8aaeea27bde4b7ddb26e28a89062ebf] Merge tag 'net-next-6.17' of git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next
> git bisect bad 8be4d31cb8aaeea27bde4b7ddb26e28a89062ebf
> # bad: [115e74a29b530d121891238e9551c4bcdf7b04b5] Merge tag 'soc-dt-6.17' of git://git.kernel.org/pub/scm/linux/kernel/git/soc/soc
> git bisect bad 115e74a29b530d121891238e9551c4bcdf7b04b5
> # bad: [177bf8620cf4ed290ee170a6c5966adc0924b336] Merge tag 'sound-6.17-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound
> git bisect bad 177bf8620cf4ed290ee170a6c5966adc0924b336
> # bad: [6e11664f148454a127dd89e8698c3e3e80e5f62f] Merge tag 'for-6.17/block-20250728' of git://git.kernel.dk/linux
> git bisect bad 6e11664f148454a127dd89e8698c3e3e80e5f62f
> # good: [953e117bf4aad7e1d01419d4bcc03ab93420387c] Merge tag 'pull-fd' of git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs
> git bisect good 953e117bf4aad7e1d01419d4bcc03ab93420387c
> # good: [672dcda246071e1940eab8bb5a03d04ea026f46e] Merge tag 'vfs-6.17-rc1.pidfs' of git://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs
> git bisect good 672dcda246071e1940eab8bb5a03d04ea026f46e
> # good: [c3018a2c6adae9b32f7b9259f5b38257ba9a758e] Merge tag 'for-6.17/io_uring-20250728' of git://git.kernel.dk/linux
> git bisect good c3018a2c6adae9b32f7b9259f5b38257ba9a758e
> # bad: [790abe4d77af736e2521ef121fae8c6ed2799773] md: remove/add redundancy group only in level change
> git bisect bad 790abe4d77af736e2521ef121fae8c6ed2799773
> # bad: [8a8fe42d765bb22cc0e91b053bfebf0fbdec3b5a] ublk: optimize UBLK_IO_REGISTER_IO_BUF on daemon task
> git bisect bad 8a8fe42d765bb22cc0e91b053bfebf0fbdec3b5a
> # bad: [7ce3c1dd78fca86ea8b9aee370db10c7a8cfc3c2] nvme-pci: convert the data mapping to blk_rq_dma_map
> git bisect bad 7ce3c1dd78fca86ea8b9aee370db10c7a8cfc3c2
> # bad: [409f9287dab3b53bffe8d28d883a529028aa6a42] dm: Check for forbidden splitting of zone write operations
> git bisect bad 409f9287dab3b53bffe8d28d883a529028aa6a42
> # bad: [f70291411ba20d50008db90a6f0731efac27872c] block: Introduce bio_needs_zone_write_plugging()
> git bisect bad f70291411ba20d50008db90a6f0731efac27872c
> # bad: [3f66ccbaaef3a0c5bd844eab04e3207b4061c546] block: Make REQ_OP_ZONE_FINISH a write operation
> git bisect bad 3f66ccbaaef3a0c5bd844eab04e3207b4061c546
> 
> 
> I hope it's all right now.

Almost, the bisect is not finished, as it requests to test further the merge
base, with the above it halts at:

Bisecting: a merge base must be tested
[d0b3b7b22dfa1f4b515fd3a295b3fd958f9e81af] Linux 6.16-rc4

So can you continue here and report back? Unless we have overseen something on
the way there at the end you will have a first bad commit shown.
Thank you very much for doing the bisect.

Thanks already!

Regards,
Salvatore