All of lore.kernel.org
 help / color / mirror / Atom feed
From: VDR User <user.vdr@gmail.com>
To: Heiner Kallweit <hkallweit1@gmail.com>
Cc: Alexander Duyck <alexander.h.duyck@linux.intel.com>,
	netdev@vger.kernel.org
Subject: Re: r8169 driver from kernel 5.0 crashing - napi_consume_skb
Date: Thu, 4 Apr 2019 07:28:17 -0700	[thread overview]
Message-ID: <CAA7C2qgSd3XBdH9Kq2erzFCU8Z_f7XBFOj5RkbJip9TdKf6YJw@mail.gmail.com> (raw)
In-Reply-To: <CAA7C2qjTLj9RenYLrNoRWDBy1Ti1EDrnLkGrn4ouDsZBy4aW9w@mail.gmail.com>

Hi,

Unfortunately I have to report that the crashing has resurfaced. I'm
currently using kernel 5.0 with Heiner's fix applied. In the last few
days I've had the crash occur 4 times now. I'm not sure how to further
investigate this but I'm guessing a patch that adds more debugging
output will be needed to track down where exactly things go bad and
hopefully what exactly is triggering it? In 2 cases there was
bi-directional traffic, in the other 2 cases there was only incoming
traffic. In all cases the nic became unresponsive, all connections to
the box died/timed out. After roughly 10 minutes the nic came back to
life on its own without my intervention. The odd thing I noticed was
the dmesg log showing the problem only shows up once in dmesg instead
of 4 times to coincide with the 4 crashes/freezes. I don't think the
box reboot itself, and if it did then dmesg should be clean.

Please let me know what you think and how we should proceed. Thanks!
Derek

[1126370.489823] ------------[ cut here ]------------
[1126370.489905] NETDEV WATCHDOG: enp4s0 (r8169): transmit queue 0 timed out
[1126370.489989] WARNING: CPU: 1 PID: 0 at net/sched/sch_generic.c:461
dev_watchdog+0x1bb/0x1e0
[1126370.490040] Modules linked in: snd_hda_codec_realtek
snd_hda_codec_generic snd_hda_codec_hdmi ohci_pci snd_hda_intel
snd_hda_codec snd_hwdep snd_hda_core ohci_hcd ehci_pci ehci_hcd
xhci_pci xhci_hcd snd_pcm usbcore snd_timer usb_common snd soundcore
nfsd auth_rpcgss oid_registry lockd grace sunrpc ip_tables x_tables
ipv6
[1126370.490118] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 5.0.0-amd #3
[1126370.490152] Hardware name: ECS A75F-A/A75F-A, BIOS 4.6.5 09/14/2011
[1126370.490187] EIP: dev_watchdog+0x1bb/0x1e0
[1126370.490220] Code: 8b 50 3c 89 f8 e8 3d aa 0a 00 8b 7e f4 eb a4 89
f8 c6 05 e7 1c 6d c1 01 e8 72 4f fd ff 53 50 57 68 78 05 66 c1 e8 e5
ac ba ff <0f> 0b 83 c4 10 eb c9 eb 1c 8d b4 26 00 00 00 00 8d b4 26 00
00 00
[1126370.490271] EAX: 0000003b EBX: 00000000 ECX: 00000800 EDX: 00000103
[1126370.490305] ESI: f4cb8264 EDI: f4cb8000 EBP: f4c99f74 ESP: f4c99f4c
[1126370.490339] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 EFLAGS: 00210296
[1126370.490374] CR0: 80050033 CR2: b719b10c CR3: 0d7a6000 CR4: 00000690
[1126370.490407] Call Trace:
[1126370.490439]  <SOFTIRQ>
[1126370.490473]  ? qdisc_put_unlocked+0x40/0x40
[1126370.490508]  call_timer_fn+0x19/0xa0
[1126370.490541]  run_timer_softirq+0x337/0x380
[1126370.490572]  ? qdisc_put_unlocked+0x40/0x40
[1126370.490601]  ? rcu_process_callbacks+0xcb/0x380
[1126370.490630]  ? net_rx_action+0x152/0x220
[1126370.490660]  __do_softirq+0xd6/0x21c
[1126370.490688]  ? __irqentry_text_end+0x18/0x18
[1126370.490718]  call_on_stack+0x10/0x60
[1126370.490746]  </SOFTIRQ>
[1126370.490774]  ? irq_exit+0x91/0xc0
[1126370.490802]  ? smp_apic_timer_interrupt+0x56/0xa0
[1126370.490831]  ? apic_timer_interrupt+0xd5/0xdc
[1126370.490863]  ? acpi_idle_enter_s2idle+0x60/0x60
[1126370.490893]  ? cpuidle_enter_state+0x122/0x360
[1126370.490922]  ? tick_nohz_idle_stop_tick+0x27b/0x2a0
[1126370.490952]  ? cpuidle_enter+0xf/0x20
[1126370.490981]  ? call_cpuidle+0x1c/0x40
[1126370.491011]  ? do_idle+0x1e6/0x220
[1126370.491039]  ? cpu_startup_entry+0x25/0x40
[1126370.491068]  ? start_secondary+0x1a5/0x220
[1126370.491097]  ? startup_32_smp+0x15f/0x164
[1126370.491126] ---[ end trace 8a26c9ba9d20b87b ]---

  reply	other threads:[~2019-04-04 14:28 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-10 19:02 r8169 driver from kernel 5.0 crashing VDR User
2019-03-10 19:35 ` Heiner Kallweit
2019-03-14  3:04   ` VDR User
2019-03-14  6:43     ` Heiner Kallweit
2019-03-14 15:10       ` VDR User
2019-03-14 18:08         ` Heiner Kallweit
2019-03-14 21:36           ` VDR User
2019-03-15 20:09             ` VDR User
2019-03-15 20:26               ` r8169 driver from kernel 5.0 crashing - napi_consume_skb Heiner Kallweit
2019-03-15 20:40                 ` Alexander Duyck
2019-03-15 20:46                   ` Heiner Kallweit
2019-03-15 22:09                     ` Alexander Duyck
2019-03-15 22:27                       ` Heiner Kallweit
     [not found]                         ` <b470f0ee6071bded8e78e15e18df14ffbc32cd18.camel@linux.intel.com>
2019-03-16  9:07                           ` Heiner Kallweit
2019-03-16 14:38                           ` VDR User
2019-03-16 15:10                             ` Heiner Kallweit
2019-03-16 17:08                               ` Alexander Duyck
2019-03-17  8:25                                 ` Heiner Kallweit
2019-03-17 11:35                             ` Heiner Kallweit
2019-03-17 15:23                               ` VDR User
2019-03-17 15:41                               ` VDR User
2019-03-17 15:49                                 ` Heiner Kallweit
2019-03-18 16:17                                   ` VDR User
2019-03-18 18:36                                     ` Heiner Kallweit
2019-03-21 19:35                                       ` VDR User
2019-03-22 19:03                                         ` Heiner Kallweit
2019-03-22 20:44                                           ` VDR User
2019-04-04 14:28                                             ` VDR User [this message]
2019-04-04 19:41                                               ` Heiner Kallweit
2019-04-04 22:11                                                 ` VDR User

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=CAA7C2qgSd3XBdH9Kq2erzFCU8Z_f7XBFOj5RkbJip9TdKf6YJw@mail.gmail.com \
    --to=user.vdr@gmail.com \
    --cc=alexander.h.duyck@linux.intel.com \
    --cc=hkallweit1@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.