Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: rob.r374 at gmail.com <rob.r374@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Weird ping behaviour
Date: Tue, 15 Sep 2020 12:18:48 +0200	[thread overview]
Message-ID: <008a01d68b49$9ab9a720$d02cf560$@gmail.com> (raw)

Hello,

 

I'm following this buildroot build and get quite strange behaviour on
ethernet network.

Ping response times vary quite a lot and then ping crashes at the end.

 

Is there any setting, compile option that would help in this case ?

 

Thanks,

Regards,

Rob.

 

Log :

 .

64 bytes from 192.168.0.2: seq=1282 ttl=64 time=152.114 ms

64 bytes from 192.168.0.2: seq=1283 ttl=64 time=1001.781 ms

64 bytes from 192.168.0.2: seq=1284 ttl=64 time=1.992 ms

64 bytes from 192.168.0.2: seq=1285 ttl=64 time=850.570 ms

[ 2345.039206][    C0] ------------[ cut here ]------------

[ 2345.044434][    C0] WARNING: CPU: 0 PID: 0 at net/sched/sch_generic.c:448
dev_watchdog+0x7f/0xe8

[ 2345.053163][    C0] NETDEV WATCHDOG: eth0 (stm32-dwmac): transmit queue 0
timed out

[ 2345.060813][    C0] CPU: 0 PID: 0 Comm: swapper Not tainted 5.4.10 #2

[ 2345.067216][    C0] Hardware name: STM32 (Device Tree Support)

[ 2345.073110][    C0] [<c000c325>] (unwind_backtrace) from [<c000b33f>]
(show_stack+0xb/0xc)

[ 2345.081330][    C0] [<c000b33f>] (show_stack) from [<c000f053>]
(__warn+0x6f/0x80)

[ 2345.088872][    C0] [<c000f053>] (__warn) from [<c000f095>]
(warn_slowpath_fmt+0x31/0x60)

[ 2345.097035][    C0] [<c000f095>] (warn_slowpath_fmt) from [<c01ade8f>]
(dev_watchdog+0x7f/0xe8)

[ 2345.105722][    C0] [<c01ade8f>] (dev_watchdog) from [<c003992b>]
(call_timer_fn.constprop.6+0xf/0x58)

[ 2345.115003][    C0] [<c003992b>] (call_timer_fn.constprop.6) from
[<c0039d47>] (__run_timers+0x197/0x1b0)

[ 2345.124547][    C0] [<c0039d47>] (__run_timers) from [<c0039d6b>]
(run_timer_softirq+0xb/0x18)

[ 2345.133139][    C0] [<c0039d6b>] (run_timer_softirq) from [<c0009a01>]
(__do_softirq+0x111/0x170)

[ 2345.141998][    C0] [<c0009a01>] (__do_softirq) from [<c0010d03>]
(irq_exit+0x33/0x70)

[ 2345.149901][    C0] [<c0010d03>] (irq_exit) from [<c002cf05>]
(__handle_domain_irq+0x47/0x6a)

[ 2345.158406][    C0] [<c002cf05>] (__handle_domain_irq) from [<c000bb93>]
(__irq_entry+0x53/0x84)

[ 2345.167134][    C0] ---[ end trace 223f53e900000001 ]---

[ 2345.172635][    T7] stm32-dwmac 40028000.ethernet eth0: Reset adapter.

 



-- 
Ta e-po?ta je bila pregledana z Avast protivirusnim programom.
https://www.avast.com/antivirus
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20200915/a9fc3e67/attachment.html>

             reply	other threads:[~2020-09-15 10:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-15 10:18 rob.r374 at gmail.com [this message]
2020-09-15 13:28 ` [Buildroot] Weird ping behaviour Thomas Petazzoni

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='008a01d68b49$9ab9a720$d02cf560$@gmail.com' \
    --to=rob.r374@gmail.com \
    --cc=buildroot@busybox.net \
    /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