From: Takashi Iwai <tiwai@suse.de>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Sasha Neftin <sasha.neftin@intel.com>,
Bagas Sanjaya <bagasdotme@gmail.com>,
Paul Menzel <pmenzel@molgen.mpg.de>,
Jesse Brandeburg <jesse.brandeburg@intel.com>,
Tony Nguyen <anthony.l.nguyen@intel.com>,
netdev@vger.kernel.org, intel-wired-lan@lists.osuosl.org,
regressions@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [Intel-wired-lan] [REGRESSION] e1000e probe/link detection fails since 6.2 kernel
Date: Thu, 30 Mar 2023 12:35:21 +0200 [thread overview]
Message-ID: <87edp6msra.wl-tiwai@suse.de> (raw)
In-Reply-To: <87wn2yn43q.wl-tiwai@suse.de>
On Thu, 30 Mar 2023 08:30:17 +0200,
Takashi Iwai wrote:
>
> On Wed, 29 Mar 2023 21:12:32 +0200,
> Jakub Kicinski wrote:
> >
> > On Wed, 29 Mar 2023 10:48:36 +0200 Takashi Iwai wrote:
> > > On Wed, 29 Mar 2023 10:40:44 +0200,
> > > Bagas Sanjaya wrote:
> > > >
> > > > On Tue, Mar 28, 2023 at 04:39:01PM +0200, Paul Menzel wrote:
> > > > > Does openSUSE Tumbleweed make it easy to bisect the regression at least on
> > > > > “rc level”? It be great if narrow it more down, so we know it for example
> > > > > regressed in 6.2-rc7.
> > > > >
> > > >
> > > > Alternatively, can you do bisection using kernel sources from Linus's
> > > > tree (git required)?
> > >
> > > That'll be a last resort, if no one has idea at all :)
> >
> > I had a quick look yesterday, there's only ~6 or so commits to e1000e.
> > Should be a fairly quick bisection, hopefully?
>
> *IFF* it's an e1000e-specific bug, right?
>
> Through a quick glance, the only significant change in e1000e is the
> commit 1060707e3809
> ptp: introduce helpers to adjust by scaled parts per million
>
> Others are only for MTP/ADP and new devices, which must be irrelevant.
> The tracing must be irrelevant, and the kmap change must be OK.
>
> Can 1060707e3809 be the cause of such a bug?
The bug reporter updated the entry and informed that this can be
false-positive; the problem could be triggered with the older kernel
out of sudden. So he closed the bug as WORKSFORME.
#regzbot invalid: Problems likely not in kernel changes
thanks,
Takashi
next prev parent reply other threads:[~2023-03-30 10:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-28 12:40 [REGRESSION] e1000e probe/link detection fails since 6.2 kernel Takashi Iwai
2023-03-28 14:39 ` [Intel-wired-lan] " Paul Menzel
2023-03-28 15:16 ` Takashi Iwai
2023-03-29 8:40 ` Bagas Sanjaya
2023-03-29 8:48 ` Takashi Iwai
2023-03-29 19:12 ` Jakub Kicinski
2023-03-30 6:30 ` Takashi Iwai
2023-03-30 10:35 ` Takashi Iwai [this message]
2023-04-02 7:38 ` Neftin, Sasha
2023-03-29 8:43 ` Bagas Sanjaya
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=87edp6msra.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=anthony.l.nguyen@intel.com \
--cc=bagasdotme@gmail.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jesse.brandeburg@intel.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pmenzel@molgen.mpg.de \
--cc=regressions@lists.linux.dev \
--cc=sasha.neftin@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 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).