[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <bc14863a-41f0-47d2-ab95-ed82eff5f5d7@leemhuis.info>
Date: Tue, 7 May 2024 08:31:34 +0200
From: "Linux regression tracking (Thorsten Leemhuis)"
<regressions@...mhuis.info>
To: Jacob Keller <jacob.e.keller@...el.com>, kernel.org-fo5k2w@...arbi.fr,
Jeff Daly <jeffd@...icom-usa.com>
Cc: intel-wired-lan@...ts.osuosl.org, anthony.l.nguyen@...el.com,
netdev@...r.kernel.org
Subject: Re: [Intel-wired-lan] Non-functional ixgbe driver between Intel X553
chipset and Cisco switch via kernel >=6.1 under Debian
On 06.05.24 23:18, Jacob Keller wrote:
> On 5/4/2024 6:29 AM, kernel.org-fo5k2w@...arbi.fr wrote:
>> > Ideally, if you could use git bisect on the setup that could
>> > efficiently locate what regressed the behavior.
>> I really want to, but I have no idea how to go about it. Can you write
>> me the command lines to satisfy your request?
> The steps would require that you build the kernel manually. I can
> outline the steps i would take here
TWIMC, there is a document on bisection in the kernel now, see
Documentation/admin-guide/verify-bugs-and-bisect-regressions.rst or
https://docs.kernel.org/admin-guide/verify-bugs-and-bisect-regressions.html
Ciao, Thorsten
Powered by blists - more mailing lists