archive mirror
 help / color / mirror / Atom feed
From: Thorsten Leemhuis <>
To: Stefan Dietrich <>,
	Vinicius Costa Gomes <>,
	Jakub Kicinski <>
Cc: Greg KH <>,,,,
	Dvora Fuxbrumer <>,
	Tony Nguyen <>,
Subject: Re: [REGRESSION] Kernel 5.15 reboots / freezes upon ifup/ifdown
Date: Wed, 1 Dec 2021 12:45:38 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

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:

Ciao, Thorsten

> On Wed, 2021-11-24 at 17:07 -0800, Vinicius Costa Gomes wrote:
>> Hi Stefan,
>> Jakub Kicinski <> 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 <>
>>>> 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
( 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

  reply	other threads:[~2021-12-01 11:45 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-24  7:28 [REGRESSION] Kernel 5.15 reboots / freezes upon ifup/ifdown Stefan Dietrich
2021-11-24  7:33 ` Greg KH
2021-11-24  7:42   ` Stefan Dietrich
2021-11-24 17:20   ` Stefan Dietrich
2021-11-24 23:34     ` Jakub Kicinski
2021-11-25  1:07       ` Vinicius Costa Gomes
2021-11-25  1:13         ` Jakub Kicinski
2021-11-25  8:41         ` Stefan Dietrich
2021-12-01 11:45           ` Thorsten Leemhuis [this message]
2021-12-01 17:47             ` Vinicius Costa Gomes
2021-12-01 18:57               ` [PATCH] igc: Avoid possible deadlock during suspend/resume Vinicius Costa Gomes
2021-12-02  6:41                 ` Greg KH
2021-12-02  6:50                   ` Vinicius Costa Gomes
2021-11-24  7:48 ` [REGRESSION] Kernel 5.15 reboots / freezes upon ifup/ifdown Thorsten Leemhuis
2021-11-24  8:05 ` Stefan Dietrich

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).