Hi Vinicius, thanks - this was spot-on: disabling CONFIG_PCIE_PTM resolves the issue for latest 5.15.4 (stable from git) for both manual and network-manager NIC configuration. Let me know if I may assist in debugging this further. Cheers, Stefan On Wed, 2021-11-24 at 17:07 -0800, Vinicius Costa Gomes wrote: > Hi Stefan, > > Jakub Kicinski <kuba@xxxxxxxxxx> writes: > > > On Wed, 24 Nov 2021 18:20:40 +0100 Stefan Dietrich wrote: > > > Hi all, > > > > > > six exciting hours and a lot of learning later, here it is. > > > Symptomatically, the critical commit appears for me between > > > 5.14.21- > > > 051421-generic and 5.15.0-051500rc2-generic - I did not find an > > > amd64 > > > build for rc1. > > > > > > Please see the git-bisect output below and let me know how I may > > > further assist in debugging! > > > > Well, let's CC those involved, shall we? :) > > > > Thanks for working thru the bisection! > > > > > a90ec84837325df4b9a6798c2cc0df202b5680bd is the first bad commit > > > commit a90ec84837325df4b9a6798c2cc0df202b5680bd > > > Author: Vinicius Costa Gomes <vinicius.gomes@xxxxxxxxx> > > > Date: Mon Jul 26 20:36:57 2021 -0700 > > > > > > igc: Add support for PTP getcrosststamp() > > Oh! That's interesting. > > Can you try disabling CONFIG_PCIE_PTM in your kernel config? If it > works, then it's a point in favor that this commit is indeed the > problematic one. > > I am still trying to think of what could be causing the lockup you > are > seeing. > > > Cheers,
