From: Stephen Hemminger <stephen@networkplumber.org>
To: netdev@vger.kernel.org
Subject: Fw: [Bug 206615] New: WARNING: CPU: 1 PID: 0 at net/sched/sch_generic.c:447 dev_watchdog+0x232/0x240
Date: Thu, 20 Feb 2020 20:23:14 -0800 [thread overview]
Message-ID: <20200220202314.32be327f@hermes.lan> (raw)
This looks like both a hardware/driver issue and a more generic problem
with the use of warnings in the network stack. The network code has a lot
of warnings that should really be notices, to prevent issues with panic on warn.
Begin forwarded message:
Date: Fri, 21 Feb 2020 01:06:57 +0000
From: bugzilla-daemon@bugzilla.kernel.org
To: stephen@networkplumber.org
Subject: [Bug 206615] New: WARNING: CPU: 1 PID: 0 at net/sched/sch_generic.c:447 dev_watchdog+0x232/0x240
https://bugzilla.kernel.org/show_bug.cgi?id=206615
Bug ID: 206615
Summary: WARNING: CPU: 1 PID: 0 at net/sched/sch_generic.c:447
dev_watchdog+0x232/0x240
Product: Networking
Version: 2.5
Kernel Version: 5.4.19
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Other
Assignee: stephen@networkplumber.org
Reporter: alec@onelabs.com
Regression: No
Created attachment 287525
--> https://bugzilla.kernel.org/attachment.cgi?id=287525&action=edit
kernel panic on warn message
Hi,
After a few hours/minutes/days (incredibly random) one of my servers keeps
crashing (panic_on_warn is enabled for security purposes.)
I have tried adding `acpi=off` `pcie_aspm=off` and `nowatchdog` to the kernel
params but nothing solves it for good. I disabled SMP in the BIOS as well, CPU
is an AMD Athlon II X2 B28.
Panic trace attached, server is a minimal Slackware system, nothing fancy. This
problem just started happening recently, server has been up for the past year
with no issue.
Same problem occurs on kernel version 5.4.20 as well.
Thanks!
Alec
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2020-02-21 4:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20200220202314.32be327f@hermes.lan \
--to=stephen@networkplumber.org \
--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).