Re: [Intel-wired-lan] [PATCH] e1000e: fix link fluctuations problem

2024-05-03 Thread En-Wei WU
Dear Paul Menzel, Thank you for your quick response. > Do you mean ho*t*-plugging? > Increas*ing*? Yes, sorry about the misspelling. > Could you please document what NICs you saw this Yes. I saw this in Intel I219-LM. I haven't seen this bug on other NICs. > and if it is documented in any data

Re: [Intel-wired-lan] [PATCH v2 1/2] e1000e: let the sleep codes run every time

2024-05-06 Thread En-Wei WU
Thank you for your time. Originally, sleep codes would only be executed if the first read fails or the link status that is read is down. Some circumstances like the [v2,2/2] "e1000e: fix link fluctuations problem" would need a delay before first reading/accessing the PHY IEEE register, so that it

Re: [Intel-wired-lan] [PATCH v2 1/2] e1000e: let the sleep codes run every time

2024-05-07 Thread En-Wei WU
C workaround and I'm wondering if we can root-cause it. On Tue, 7 May 2024 at 08:22, Ruinskiy, Dima wrote: > > On 06/05/2024 19:46, En-Wei WU wrote: > > Thank you for your time. > > > > Originally, sleep codes would only be executed if the first read fails > > or

Re: [Intel-wired-lan] [PATCH] e1000e: fix link fluctuations problem

2024-05-07 Thread En-Wei WU
> Why PHY is this? It's the Intel I219-LM, and I haven't found any other device having the same issue. > It might be the PHY manufacture has an errata, since > this is probably not the MAC causing the problem, but the PHY itself. Yes. The problem seems to be a PHY problem. I'm wondering if doing a

Re: [Intel-wired-lan] [PATCH v2 2/2] e1000e: fix link fluctuations problem

2024-05-09 Thread En-Wei WU
> En-Wei, My recommendation is not to accept these patches. If you think > there is a HW/PHY problem - open a ticket on Intel PAE. > I concur. I am wary of changing the behavior of some driver > fundamentals, to satisfy a particular validation/certification flow, if > there is no real functionalit

Re: [Intel-wired-lan] [PATCH] ice: irdma hardware init failed after suspend/resume

2024-05-28 Thread En-Wei WU
Thanks for your kind and quick reply. > I think this should be called later in the reset path IMO. > You should call ice_deinit_rdma in ice_prepare_for_reset (replace > ice_unplug_aux_dev), I'm afraid this would break the existing code because in ice_deinit_rdma(), it will remove some entries in

Re: [Intel-wired-lan] [PATCH] ice: irdma hardware init failed after suspend/resume

2024-05-30 Thread En-Wei WU
ak in the original code. Best regards, Ricky. On Thu, 30 May 2024 at 04:19, Paul Menzel wrote: > > Dear En-Wei, > > > Thank you for responding so quickly. > > Am 29.05.24 um 05:17 schrieb En-Wei WU: > > […] > > >> What effect does this have on resume time?

[Intel-wired-lan] [PATCH iwl-net v2] igc: return early when failing to read EECD register

2024-12-17 Thread En-Wei Wu
4056126813 ("igc: Add NVM support") Cc: Chia-Lin Kao (AceLan) Signed-off-by: En-Wei Wu --- Changes in v2: - Added "after" logs showing improved boot time - Fixed error code (use -ENXIO instead of -ENODEV) - Added error propagation in igc_get_invariants_base() - Added Fixes

Re: [Intel-wired-lan] [REGRESSION] Packet loss after hot-plugging ethernet cable on HP Zbook (Arrow Lake)

2025-07-04 Thread En-Wei WU
the case for PHY, as I’m not familiar with how to check the power state of a PHY. Thanks, En-Wei. On Tue, 1 Jul 2025 at 20:44, Timo Teras wrote: > > On Tue, 1 Jul 2025 14:46:18 +0300 > "Lifshits, Vitaly" wrote: > > > On 7/1/2025 8:31 AM, En-Wei WU wrote: > > >

[Intel-wired-lan] [REGRESSION] Packet loss after hot-plugging ethernet cable on HP Zbook (Arrow Lake)

2025-06-30 Thread En-Wei WU
Hi, I'm seeing a regression on an HP ZBook using the e1000e driver (chipset PCI ID: [8086:57a0]) -- the system can't get an IP address after hot-plugging an Ethernet cable. In this case, the Ethernet cable was unplugged at boot. The network interface eno1 was present but stuck in the DHCP process.