Fw: [Bug 206615] New: WARNING: CPU: 1 PID: 0 at net/sched/sch_generic.c:447 dev_watchdog+0x232/0x240

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.