netdev - Re: r8169 doesn't work after boot until `transmit queue 0 timed out`

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAKzrAgSGdLTTFn5Tw=4DSAeikStsLw8mWmv-HEtmVUNFu+yrZA@mail.gmail.com>
Date:   Thu, 3 May 2018 08:09:27 +0000
From:   "ojab //" <ojab@...b.ru>
To:     nic_swsd@...ltek.com, netdev@...r.kernel.org
Subject: Re: r8169 doesn't work after boot until `transmit queue 0 timed out`

On Fri, Apr 27, 2018 at 8:22 PM, ojab // <ojab@...b.ru> wrote:
> Oh hai!
>
> I've created bugzilla ticket about this, but I'm not sure if anyone
> reads it, so duplicating here.
>
> I have new motherboard (ASUS A320-K) with 10ec:8168 realtek network
> card installed and it doesn't work (i. e. `tcpdump` shows outgoing
> packets but no packets are actually transmitted and `tcpdump` doesn't
> show incoming packets while they are trasmitted from the other side)
> then after 200-300 seconds I see [full stacktrace [1] and lspci [2]
> output are attached to bugzilla ticket]
>
> [  256.996145] ------------[ cut here ]------------
> [  256.997574] NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out
> [  256.998992] WARNING: CPU: 6 PID: 0 at dev_watchdog+0x1f2/0x200
> …
>
> [  257.012243] RIP: 0010:dev_watchdog+0x1f2/0x200
> …
> [  257.032044]  <IRQ>
> [  257.033829]  ? pfifo_fast_init+0x150/0x150
> [  257.035618]  call_timer_fn+0x2b/0x120
> [  257.037400]  run_timer_softirq+0x2f4/0x410
> [  257.039170]  ? pfifo_fast_init+0x150/0x150
> [  257.040931]  ? timerqueue_add+0x52/0x80
> [  257.042694]  ? __hrtimer_run_queues+0x161/0x2e0
> [  257.044462]  __do_softirq+0x111/0x32c
> [  257.046223]  irq_exit+0x85/0x90
> [  257.047966]  smp_apic_timer_interrupt+0x6c/0x120
> [  257.049720]  apic_timer_interrupt+0xf/0x20
> [  257.051475]  </IRQ>
>
> and everything starts working normally. How can I make it work right after boot?
>
> The issue is reproducible in linux-4.16.5 & linux-4.17-rc2 with
> rtl_nic fw from linux-firmware git master.
>
> [1] https://bugzilla.kernel.org/attachment.cgi?id=275627
> [2] https://bugzilla.kernel.org/attachment.cgi?id=275629
>


ping?

//wbr ojab