.c
>> > index 280994ee5933..b47cd43ae871 100644
>> > --- a/drivers/net/ethernet/intel/ice/ice_lag.c
>> > +++ b/drivers/net/ethernet/intel/ice/ice_lag.c
>> > @@ -1981,6 +1981,8 @@ int ice_init_lag(struct ice_pf *pf)
>> >int n, err;
>> >
>&g
if (err)
>+ return err;
>+ pci_restore_state(pdev);
>+ }
>+
> /* this driver uses devres, see
>* Documentation/driver-api/driver-model/devres.rst
>*/
>
>base-commit: 6a70e5cbedaf8ad10528ac9ac114f3ec20f422df
>--
>2.39.3
>
---
-Jay Vosburgh, jay.vosbu...@canonical.com
___
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
Jesse Brandeburg wrote:
>On 10/2/2023 4:49 PM, Jay Vosburgh wrote:
>> Jesse Brandeburg wrote:
>>
>>> When the system boots into the crash dump kernel after a panic, the ice
>>> networking device may still have pending transactions that can cause errors
>>
bugzilla reporter is
also seeing TX timeouts that correlate with their ping failures.
-J
>Thanks.
>
>[1]: https://bugzilla.kernel.org/show_bug.cgi?id=218139
>
>--
>An old man doll... just what I always wanted! - Clara
---
-Jay Vosburgh, jay.vosbu...@cano
