From: Stephen Hemminger <stephen@networkplumber.org>
To: alexandre.torgue@foss.st.com, joabreu@synopsys.com
Cc: netdev@vger.kernel.org
Subject: Fw: [Bug 217772] SoC development environment Linux LAN disconnection
Date: Wed, 9 Aug 2023 07:45:46 -0700 [thread overview]
Message-ID: <20230809074546.6ecc484e@hermes.local> (raw)
This bug report doesn't have a lot of info.
But in the dmesg is:
WARNING: CPU: 0 PID: 0 at /home/kaihatsu/linux_home/thread_\\\\\\\\\\/firm/kernel/linux-4.4-*****/net/sched/sch_generic.c:303 dev_watchdog+0x230/0x23c()
NETDEV WATCHDOG: eth0 (stmmaceth): transmit queue 0 timed out
Modules linked in: qgpio(O) qm3(O) qmem(O)
CPU: 0 PID: 0 Comm: swapper Tainted: G W O 4.4.0 #1
Hardware name: ********* (Flattened Device Tree)
[<8002a2e0>] (unwind_backtrace) from [<800289a4>] (show_stack+0x10/0x14)
[<800289a4>] (show_stack) from [<800357b0>] (warn_slowpath_common+0x84/0xb0)
[<800357b0>] (warn_slowpath_common) from [<8003580c>] (warn_slowpath_fmt+0x30/0x40)
[<8003580c>] (warn_slowpath_fmt) from [<8048bd20>] (dev_watchdog+0x230/0x23c)
[<8048bd20>] (dev_watchdog) from [<80075028>] (call_timer_fn+0x30/0x110)
[<80075028>] (call_timer_fn) from [<80075370>] (run_timer_softirq+0x140/0x264)
[<80075370>] (run_timer_softirq) from [<8003851c>] (__do_softirq+0xf4/0x2cc)
[<8003851c>] (__do_softirq) from [<8006b144>] (__handle_domain_irq+0x58/0xa8)
[<8006b144>] (__handle_domain_irq) from [<8000942c>] (gic_handle_irq+0x38/0x64)
[<8000942c>] (gic_handle_irq) from [<8056a280>] (__irq_svc+0x40/0x54)
Exception stack(0x807d7f50 to 0x807d7f98)
7f40: 807e3a78 0000067f 807dd6f8 80031b20
7f60: 80849050 807d6000 807d810c 808413c0 80840643 80840643 80849000 807c5a28
7f80: 00a00000 807d7fa0 80025c4c 80025c50 60010013 ffffffff
[<8056a280>] (__irq_svc) from [<80025c50>] (arch_cpu_idle+0x38/0x3c)
[<80025c50>] (arch_cpu_idle) from [<8005e5d4>] (cpu_startup_entry+0x110/0x14c)
[<8005e5d4>] (cpu_startup_entry) from [<80789c9c>] (start_kernel+0x3d0/0x3dc)
---[ end trace cb88537fdc8fa202 ]---
Begin forwarded message:
Date: Wed, 09 Aug 2023 12:29:07 +0000
From: bugzilla-daemon@kernel.org
To: stephen@networkplumber.org
Subject: [Bug 217772] SoC development environment Linux LAN disconnection
https://bugzilla.kernel.org/show_bug.cgi?id=217772
Ryosuke Motoyoshi (motoyoshi@phoenix-group.co.jp) changed:
What |Removed |Added
----------------------------------------------------------------------------
Kernel Version| |Linux 4.4
--- Comment #2 from Ryosuke Motoyoshi (motoyoshi@phoenix-group.co.jp) ---
(In reply to Stephen Hemminger from comment #1)
> Need to know both the kernel config, and which network device is being used.
Our designer
He said that he uses the Linux kernel as it is, so he doesn't know how to
answer.
> Did you check the kernel log (dmesg).
Attach separately.
> Check with LWN articles or kernel newbies
> https://kernelnewbies.org/Linux_4.19
Let me check them in parallel.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2023-08-09 14:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230809074546.6ecc484e@hermes.local \
--to=stephen@networkplumber.org \
--cc=alexandre.torgue@foss.st.com \
--cc=joabreu@synopsys.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).