All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Dietrich <roots@gmx.de>
To: Vinicius Costa Gomes <vinicius.gomes@intel.com>,
	Jakub Kicinski <kuba@kernel.org>
Cc: Greg KH <greg@kroah.com>,
	netdev@vger.kernel.org, stable@vger.kernel.org,
	 regressions@lists.linux.dev,
	Dvora Fuxbrumer <dvorax.fuxbrumer@linux.intel.com>,
	 Tony Nguyen <anthony.l.nguyen@intel.com>,
	intel-wired-lan@lists.osuosl.org
Subject: Re: [REGRESSION] Kernel 5.15 reboots / freezes upon ifup/ifdown
Date: Thu, 25 Nov 2021 09:41:56 +0100	[thread overview]
Message-ID: <227af6b0692a0a57f5fb349d4d9c914301753209.camel@gmx.de> (raw)
In-Reply-To: <87a6htm4aj.fsf@intel.com>

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@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.
>
>
> Cheers,


WARNING: multiple messages have this Message-ID (diff)
From: Stefan Dietrich <roots@gmx.de>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [REGRESSION] Kernel 5.15 reboots / freezes upon ifup/ifdown
Date: Thu, 25 Nov 2021 09:41:56 +0100	[thread overview]
Message-ID: <227af6b0692a0a57f5fb349d4d9c914301753209.camel@gmx.de> (raw)
In-Reply-To: <87a6htm4aj.fsf@intel.com>

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@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.
>
>
> Cheers,


  parent reply	other threads:[~2021-11-25  8:42 UTC|newest]

Thread overview: 53+ 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-24 23:34       ` [Intel-wired-lan] " Jakub Kicinski
2021-11-25  1:07       ` Vinicius Costa Gomes
2021-11-25  1:07         ` [Intel-wired-lan] " Vinicius Costa Gomes
2021-11-25  1:13         ` Jakub Kicinski
2021-11-25  1:13           ` [Intel-wired-lan] " Jakub Kicinski
2021-11-25  8:41         ` Stefan Dietrich [this message]
2021-11-25  8:41           ` Stefan Dietrich
2021-12-01 11:45           ` Thorsten Leemhuis
2021-12-01 11:45             ` [Intel-wired-lan] " Thorsten Leemhuis
2021-12-01 17:47             ` Vinicius Costa Gomes
2021-12-01 17:47               ` [Intel-wired-lan] " Vinicius Costa Gomes
2021-12-01 18:57               ` [PATCH] igc: Avoid possible deadlock during suspend/resume Vinicius Costa Gomes
2021-12-01 18:57                 ` [Intel-wired-lan] " Vinicius Costa Gomes
2021-12-02  6:41                 ` Greg KH
2021-12-02  6:41                   ` [Intel-wired-lan] " Greg KH
2021-12-02  6:50                   ` Vinicius Costa Gomes
2021-12-02  6:50                     ` [Intel-wired-lan] " Vinicius Costa Gomes
2021-12-02  8:34                 ` Stefan Dietrich
2021-12-02  8:34                   ` [Intel-wired-lan] " Stefan Dietrich
2021-12-02 22:34                   ` Vinicius Costa Gomes
2021-12-02 22:34                     ` [Intel-wired-lan] " Vinicius Costa Gomes
2021-12-10  9:40                     ` Thorsten Leemhuis
2021-12-10  9:40                       ` [Intel-wired-lan] " Thorsten Leemhuis
2021-12-10 13:45                       ` Stefan Dietrich
2021-12-10 13:45                         ` [Intel-wired-lan] " Stefan Dietrich
2021-12-10 14:01                         ` Thorsten Leemhuis
2021-12-10 14:01                           ` [Intel-wired-lan] " Thorsten Leemhuis
2021-12-10 14:51                           ` Stefan Dietrich
2021-12-10 14:51                             ` [Intel-wired-lan] " Stefan Dietrich
2021-12-11  0:41                             ` Vinicius Costa Gomes
2021-12-11  0:41                               ` [Intel-wired-lan] " Vinicius Costa Gomes
2021-12-11  9:50                               ` Stefan Dietrich
2021-12-11  9:50                                 ` [Intel-wired-lan] " Stefan Dietrich
2021-12-13 18:32                                 ` Vinicius Costa Gomes
2021-12-13 18:32                                   ` [Intel-wired-lan] " Vinicius Costa Gomes
2021-12-14  0:39                                   ` [PATCH net v1] igc: Do not enable crosstimestamping for i225-V models Vinicius Costa Gomes
2021-12-14  0:39                                     ` [Intel-wired-lan] " Vinicius Costa Gomes
2021-12-14  5:49                                     ` Thorsten Leemhuis
2021-12-14  5:49                                       ` [Intel-wired-lan] " Thorsten Leemhuis
2021-12-23  7:21                                       ` Thorsten Leemhuis
2021-12-23  7:21                                         ` [Intel-wired-lan] " Thorsten Leemhuis
2021-12-27 20:35                                     ` Kraus, NechamaX
2021-12-27 20:35                                       ` Kraus, NechamaX
2021-12-14  6:39                                   ` [PATCH] igc: Avoid possible deadlock during suspend/resume Stefan Dietrich
2021-12-14  6:39                                     ` [Intel-wired-lan] " Stefan Dietrich
2021-11-24  7:48 ` [REGRESSION] Kernel 5.15 reboots / freezes upon ifup/ifdown Thorsten Leemhuis
2021-11-25 11:15   ` 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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=227af6b0692a0a57f5fb349d4d9c914301753209.camel@gmx.de \
    --to=roots@gmx.de \
    --cc=anthony.l.nguyen@intel.com \
    --cc=dvorax.fuxbrumer@linux.intel.com \
    --cc=greg@kroah.com \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=regressions@lists.linux.dev \
    --cc=stable@vger.kernel.org \
    --cc=vinicius.gomes@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.