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

[Salvatore Bonaccorso <carnil@debian.org>]

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