Hi Andreas,
On Mon, Sep 16, 2019 at 4:25 PM wrote:
>
>
>
> On 16.09.2019 13:14, Andreas Schwab wrote:
> > External E-Mail
> >
> >
> > On Sep 16 2019, wrote:
> >
> >> I will have a look on it. It would be good if you could give me some
> >> details about the steps to reproduce it.
> >
> > You nee
On 16.09.2019 13:14, Andreas Schwab wrote:
> External E-Mail
>
>
> On Sep 16 2019, wrote:
>
>> I will have a look on it. It would be good if you could give me some
>> details about the steps to reproduce it.
>
> You need to trigger OOM.
Ok, thank you!
>
> Andreas.
>
On Sep 16 2019, wrote:
> I will have a look on it. It would be good if you could give me some
> details about the steps to reproduce it.
You need to trigger OOM.
Andreas.
--
Andreas Schwab, SUSE Labs, sch...@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And
Hi Andreas,
I will have a look on it. It would be good if you could give me some
details about the steps to reproduce it.
Thank you,
Claudiu Beznea
On 16.09.2019 10:41, Andreas Schwab wrote:
> When there is an OOM situation, the macb driver cannot recover from it:
>
> [245622.872993] macb 10090
When there is an OOM situation, the macb driver cannot recover from it:
[245622.872993] macb 1009.ethernet eth0: Unable to allocate sk_buff
[245622.891438] macb 1009.ethernet eth0: inconsistent Rx descriptor chain
After that, the interface is dead. Since this system is using NFS root,
it
