On 17.03.21 13:39, John Paul Adrian Glaubitz wrote:
On 3/17/21 1:22 PM, Frank Scheiner wrote:
johndoe@x4270:~/git-projects/torvalds/linux$ git bisect bad
028abd9222df0cf5855dab5014a5ebaf06f90565 is the first bad commit
Did you verify that reverting this commit or - if reverting is not possible -
out the revision just before the commit?
I did not yet revert the bad commit in a current kernel and test it, but
from my understanding the parent commit of the first bad one must have
been a good one and indeed, [67e306c6906137020267eb9bbdbc127034da3627]
is the parent of [028abd9222df0cf5855dab5014a5ebaf06f90565] and was
working for me on my T1000:
johndoe@x4270:~/git-projects/torvalds/linux$ git bisect log
# good: [67e306c6906137020267eb9bbdbc127034da3627] fs,nfs: lift compat
nfs4 mount data handling into the nfs code
git bisect good 67e306c6906137020267eb9bbdbc127034da3627
# bad: [028abd9222df0cf5855dab5014a5ebaf06f90565] fs: remove
git bisect bad 028abd9222df0cf5855dab5014a5ebaf06f90565
# first bad commit: [028abd9222df0cf5855dab5014a5ebaf06f90565] fs:
Just to be safe you found the correct commit.
If that has been verified, please report the issue to the sparclinux LKML and
Will do that soon-ish but maybe also try to revert that commit in
Debian's 5.10.0-4 and test it for additional assurance (then not so
soon-ish - maybe this weekend). I'll put you and Riccardo in CC, too.
Hopefully this will be easier to fix than the kernel breakage on the
rx2800 i2 - assuming that problem is still there (, ).
Cheers and thanks for the pointers,