Bug#1014793: linux-image-5.10.0-16-amd64: Kernel crashes while serving NFS
Hi Arne,
Thanks a lot for your time into debugging the issue.
On Fri, Jul 15, 2022 at 10:28:17AM +0200, Arne Nordmark wrote:
> Sorry for the late reply.
>
> Den 2022-07-13 kl. 12:07, skrev Salvatore Bonaccorso:
> > Control: tags -1 + moreinfo
> >
> > Hello Arne,
> >
>
> ...
>
> >
> > As you seem to reliably reproduce the issue, do you have the
> > possiblity (on the nonproduction instance) to try to bisect down the
> > problem? Additionally to the bisect, on a testinstance were the issue
> > is reproducible, can you run a selfcompiled 5.10.130 upstream to see
> > if the problem is still present?
>
> I have now set up a test environment, and been able to reproduce NFS crashes
> with the Debian linux-image-5.10.0-16-amd64 and self-compiled upstream
> v5.10.127 kernels.
Thats great. I have not reached yet the point to replicate it myself.
But it's good you have now a base test environment where it's safe to
experiment.
> I have not been able to get a self-compiled upstream v5.10.130 to crash.
That are good news.
> As for bisection, I am not entirely clear what is expected from me. Do you
> mean bisect the upstream kernels? Between which points? v5.10.120 to
> v5.10.127?
I would be interested to either pinpoint the regressing commit
upstream beween 5.10.120 and 5.10.127 or conversely the fixing commit
beween 5.10.127 upstream and 5.10.130 where you are not able anymore
to reproduce the error. What I can say, I have already imported
5.10.130 for furture upload (cf.
https://salsa.debian.org/kernel-team/linux/-/merge_requests/506).
> Bisection would be a new experience for me, even compiling the kernel seem
> like ages ago ... (using Debian since 0.93R6).
Would the following help?
https://wiki.debian.org/DebianKernel/GitBisect
Do you need any more specifc help to get it rolling?
Regards,
Salvatore
Reply to: