[CentOS] [EXTERNAL] Re: Strange Network Bug Locks Up CentOS 7 Laptop

[Virgo, Paul E. (GSFC-610.2)[ADNET SYSTEMS INC]]

Mark,
I don't see any hardware errors on the Dell, as of yet, and I do plan to update the BIOS today.
I'll go ahead and replace the cable, and ask the network guys to check the routers for any
errors on the port. I did do some follow-up, and see that this problem persists across other
platforms as well. Thanks for the follow-up

PEV

________________________________
From: mark <m.roth at 5-cent.us>
Sent: Monday, June 24, 2019 10:24 AM
To: Virgo, Paul E. (GSFC-610.2)[ADNET SYSTEMS INC]; CentOS mailing list
Subject: [EXTERNAL] Re: [CentOS] Strange Network Bug Locks Up CentOS 7 Laptop

Virgo, Paul E. \(GSFC-610.2\)\[ADNET SYSTEMS INC\] via CentOS wrote:
> All,
>
>
> I have a user who has a Dell Precision 7520 laptop, and we're running
> CentOS 7, latest kernel.
> This morning he had two lockup incidents. Nothing in /var/log/messages
> stands out so far, but did get this information when running 'abrt-cli
> list --since 1560891312':
>
> id c48278a875c27dd4369d971bcfc7db4267766c6d reason:         WARNING: CPU:
> 0 PID: 0 at net/sched/sch_generic.c:356 dev_watchdog+0x248/0x260 time:
> Thu 23 May 2019 07:12:57 PM EDT
> cmdline:        BOOT_IMAGE=/vmlinuz-3.10.0-957.12.1.el7.x86_64
> root=/dev/mapper/SysVG00-ROOT ro crashkernel=auto rd.lvm.lv=SysVG00/ROOT
> rd.luks.uuid=luks-29590e52-c08e-4c11-a784-cf2f3ffd98b2
> rd.lvm.lv=SysVG00/SWAP rhgb quiet LANG=en_US.UTF-8 package:        kernel
> uid:            0 (root)
> count:          4
> Directory:      /var/spool/abrt/oops-2019-05-23-19:12:57-28561-0
> Reported:       cannot be reported
>
> Has anyone seen this behavior before or this message? Seems like
> something related to network scheduling (?) or something. Any feedback
> would be appreciated. Thanks.
>
Hi, Paul,

   I just searched on sch_generic.c:356, and found a number of things,
intluding bugs from last year. I looked at the code - not sure if it's
the same version, but it looks to me as though it may possibly be
related to an issue with the network connection. If so, then it's check
the cable, check the port on the router... or look for hardware errors
on the laptop.


    mark