[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <010c2d24-201e-4aba-b4a1-d973545121a7@lunn.ch>
Date: Tue, 7 May 2024 14:29:25 +0200
From: Andrew Lunn <andrew@...n.ch>
To: En-Wei WU <en-wei.wu@...onical.com>
Cc: "Ruinskiy, Dima" <dima.ruinskiy@...el.com>,
Sasha Neftin <sasha.neftin@...el.com>, netdev@...r.kernel.org,
rickywu0421@...il.com, linux-kernel@...r.kernel.org,
edumazet@...gle.com, intel-wired-lan@...ts.osuosl.org,
kuba@...nel.org, anthony.l.nguyen@...el.com, pabeni@...hat.com,
davem@...emloft.net,
"Brandeburg, Jesse" <jesse.brandeburg@...el.com>,
"Lifshits, Vitaly" <vitaly.lifshits@...el.com>
Subject: Re: [Intel-wired-lan] [PATCH v2 1/2] e1000e: let the sleep codes run
every time
> > (1) How serious this problem is. It is normal for link establishment to
> > take a few seconds from plugging the cable (due to PHY
> > auto-negotiation), and I can accept some link instability during that time.
> Actually, the problem is not critical since the link will be up
> permanently after the unstable up-down problem when hot-plugging. And
> it has no functional impact on the system. But this problem can lead
> to a failure in our script (for Canonical Certification), and it's not
> tolerable.
Please could you describe your test. We should be sure you are fixing
the right thing. Maybe the test is broken, not the driver...
Andrew
Powered by blists - more mailing lists