From: Jakub Kicinski <kuba@kernel.org>
To: Takashi Iwai <tiwai@suse.de>, Sasha Neftin <sasha.neftin@intel.com>
Cc: Paul Menzel <pmenzel@molgen.mpg.de>,
regressions@lists.linux.dev, netdev@vger.kernel.org,
Jesse Brandeburg <jesse.brandeburg@intel.com>,
linux-kernel@vger.kernel.org, intel-wired-lan@lists.osuosl.org,
Bagas Sanjaya <bagasdotme@gmail.com>,
Tony Nguyen <anthony.l.nguyen@intel.com>
Subject: Re: [Intel-wired-lan] [REGRESSION] e1000e probe/link detection fails since 6.2 kernel
Date: Wed, 29 Mar 2023 12:12:32 -0700 [thread overview]
Message-ID: <20230329121232.7873ad95@kernel.org> (raw)
In-Reply-To: <87a5zwosd7.wl-tiwai@suse.de>
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?
Adding Sasha.
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
WARNING: multiple messages have this Message-ID (diff)
From: Jakub Kicinski <kuba@kernel.org>
To: Takashi Iwai <tiwai@suse.de>, Sasha Neftin <sasha.neftin@intel.com>
Cc: 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: Wed, 29 Mar 2023 12:12:32 -0700 [thread overview]
Message-ID: <20230329121232.7873ad95@kernel.org> (raw)
In-Reply-To: <87a5zwosd7.wl-tiwai@suse.de>
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?
Adding Sasha.
next prev parent reply other threads:[~2023-03-29 19:12 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-28 12:40 [Intel-wired-lan] [REGRESSION] e1000e probe/link detection fails since 6.2 kernel Takashi Iwai
2023-03-28 12:40 ` Takashi Iwai
2023-03-28 14:39 ` [Intel-wired-lan] " Paul Menzel
2023-03-28 14:39 ` Paul Menzel
2023-03-28 15:16 ` Takashi Iwai
2023-03-28 15:16 ` Takashi Iwai
2023-03-29 8:40 ` Bagas Sanjaya
2023-03-29 8:40 ` Bagas Sanjaya
2023-03-29 8:48 ` Takashi Iwai
2023-03-29 8:48 ` Takashi Iwai
2023-03-29 19:12 ` Jakub Kicinski [this message]
2023-03-29 19:12 ` Jakub Kicinski
2023-03-30 6:30 ` Takashi Iwai
2023-03-30 6:30 ` Takashi Iwai
2023-03-30 10:35 ` Takashi Iwai
2023-03-30 10:35 ` Takashi Iwai
2023-04-02 7:38 ` Neftin, Sasha
2023-04-02 7:38 ` Neftin, Sasha
2023-03-29 8:43 ` Bagas Sanjaya
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=20230329121232.7873ad95@kernel.org \
--to=kuba@kernel.org \
--cc=anthony.l.nguyen@intel.com \
--cc=bagasdotme@gmail.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jesse.brandeburg@intel.com \
--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 \
--cc=tiwai@suse.de \
/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.