Hi, this is your Linux kernel regression tracker speaking.
On 25.11.21 09:41, Stefan Dietrich wrote:
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.
What is the status here? There afaics hasn't been any progress since nearly a week.
Vinicius, do you still have this on your radar? Or was there some progress?
Or is this really related to another issue, as Jakub suspected? Then it might be solved by the patch here:
https://bugzilla.kernel.org/show_bug.cgi?id=215129
Ciao, Thorsten
On Wed, 2021-11-24 at 17:07 -0800, Vinicius Costa Gomes wrote:
Hi Stefan,
Jakub Kicinski kuba@kernel.org 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@intel.com 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.
P.S.: As a Linux kernel regression tracker I'm getting a lot of reports on my table. I can only look briefly into most of them. Unfortunately therefore I sometimes will get things wrong or miss something important. I hope that's not the case here; if you think it is, don't hesitate to tell me about it in a public reply. That's in everyone's interest, as what I wrote above might be misleading to everyone reading this; any suggestion I gave they thus might sent someone reading this down the wrong rabbit hole, which none of us wants.
BTW, I have no personal interest in this issue, which is tracked using regzbot, my Linux kernel regression tracking bot (https://linux-regtracking.leemhuis.info/regzbot/). I'm only posting this mail to get things rolling again and hence don't need to be CC on all further activities wrt to this regression.
#regzbot poke