netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: Jeroen Baten <jbaten@i2rs.nl>
Cc: netdev@vger.kernel.org
Subject: Re: newbie question on networking kernel panics.
Date: Thu, 16 Jul 2020 18:40:12 +0200	[thread overview]
Message-ID: <20200716164012.GB22540@1wt.eu> (raw)
In-Reply-To: <49a5eb70-3596-26b5-37bb-285bbdc75a95@i2rs.nl>

Hi Jeroen,

On Thu, Jul 16, 2020 at 05:38:57PM +0200, Jeroen Baten wrote:
> Hi,
> 
> I have been working on a Linux desktop for the last 20 odd years.
> Currently running Ubuntu 20.04.
> 
> Yesterday I enabled the option "Flow control" on my TP-Link TL-SG1024DE.
> 
> Subsequently I was forced to enjoy 3 kernel panics in the timespan of 18
> hours.
> 
> After disabling the "Flow control" option my system seems to be stable
> again.
> 
> I do have 3 sets of "cut here" text if somebody would be interested.
> 
> Please let me know if this information is of interest to someone or if I
> am barking up the wrong majordomo tree.
> 
> Kind regards and thanks to all here for your immensely valuable work,

Since distro kernels contain some extra patches, may miss a significant
number of fixes, or even rely on different driver sources, you really
need to report this issue to your distro, who will ask for your exact
kernel version. It may be that this issue also affects the vanilla
kernel in the end, but in this case it will be reported by the distro's
maintainers once they've verified that it's not related to their kernel's
differences.

Hoping this helps,
Willy

  reply	other threads:[~2020-07-16 16:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-16 15:38 newbie question on networking kernel panics Jeroen Baten
2020-07-16 16:40 ` Willy Tarreau [this message]
2020-07-16 19:02   ` Andrew Lunn

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200716164012.GB22540@1wt.eu \
    --to=w@1wt.eu \
    --cc=jbaten@i2rs.nl \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).