On Wed, Apr 10, 2024 at 03:42:44PM +0200, Salvatore Bonaccorso wrote:
> Control: tags -1 - moreinfo
> Control: tags -1 + confirmed
>
> hi Cyril,
>
> On Wed, Apr 10, 2024 at 03:32:02PM +0200, Cyril Brulebois wrote:
> > Cyril Brulebois <k...@debian.org> (2024-04-10):
> > > Salvatore Bonaccorso <car...@debian.org> (2024-04-10):
> > > > On Tue, Apr 09, 2024 at 03:33:09PM +0200, Diederik de Haas wrote:
> > > > > Does the problem go away if you revert the following commits on top
> > > > > of -19?
> > > > >
> > > > > db6338f45971b4285ea368432a84033690eaf53c
> > > > > scsi: core: Move scsi_host_busy() out of host lock for waking up EH
> > > > > handler
> > > > >
> > > > > 1ebd75cefaac6fd74729a7d3157f6eaa59960ae2
> > > > > scsi: core: Move scsi_host_busy() out of host lock if it is for
> > > > > per-command
> > > > >
> > > > > cf33e6ca12d814e1be2263cb76960d0019d7fb94
> > > > > scsi: core: Add struct for args to execution functions
> > >
> > > Preparing that test right now, thanks Diederik.
> >
> > This doesn't build, but I didn't try very hard:
> >
> > /home/kibi/debian-kernel/linux.git/drivers/scsi/sd.c: In function
> > ‘sd_read_block_zero’:
> > /home/kibi/debian-kernel/linux.git/drivers/scsi/sd.c:3300:9: error:
> > implicit declaration of function ‘scsi_execute_cmd’; did you mean
> > ‘scsi_execute_req’? [-Werror=implicit-function-declaration]
> >
> > > > Or if that does not find the culprit, would you be able to bisect the
> > > > upstrema changes beweeen 6.1.76 and 6.1.82?
> >
> > I think I'll try and pinpoint when that regression came up, then figure
> > out what to try to get rid of it. Also testing v6.1.84 while I'm at it.
> >
> > > > > 4b085736e44d ("ata: libata-core: Do not try to set sleeping devices
> > > > > to standby")
> >
> > Reverting that one got me a successful build but that didn't help.
> >
> >
> > I'll need to find some more time to switch from throwing a patch into
> > the packaging repository to bindeb-pkg'ing from the mainline repository,
> > and to automate testing as much as possible. I'm familiar with the
> > exercise with Raspberry Pi thingies, but I'd expect some tweaks to be
> > required in the amd64 case.
>
> FWIW, I can reproduce the issue myself as well, so that makes us both
> already bit more independent to debug the issue.
6.7.9-2 in unstable does not exibit the issue.
Regards,
Salvatore
