请注意，本文内容源自机器翻译，可能存在语法或其它翻译错误，仅供参考。如需获取准确内容，请参阅链接中的英语原文或自行翻译。
部件号：PROCESSOR-SDK-J784S4 工具/软件：
你(们)好
我们在一段时间前迁移到 SDK 10.1、现在正在迁移到11.0。
自10.0更新以来、CPSW9G 存在零星的载波损耗问题。
这在内核日志中如下所示：
[ 2311.782322] am65-cpsw-nuss c000000.ethernet xg19: yt8614_read_status, phy addr: 10, link down [ 2311.782577] am65-cpsw-nuss c000000.ethernet xg19: Link is Down [ 2311.805434] switch: port 4(xg19) entered disabled state [ 2312.810441] am65-cpsw-nuss c000000.ethernet xg19: yt8614_read_status, phy addr: 10, link up, media UTP [ 2312.811138] am65-cpsw-nuss c000000.ethernet xg19: Link is Up - 100Mbps/Full - flow control off [ 2312.811183] switch: port 4(xg19) entered blocking state [ 2312.811190] switch: port 4(xg19) entered forwarding state [ 2329.190115] am65-cpsw-nuss c000000.ethernet xg19: yt8614_read_status, phy addr: 10, link down [ 2329.190394] am65-cpsw-nuss c000000.ethernet xg19: Link is Down [ 2329.205651] switch: port 4(xg19) entered disabled state [ 2330.214723] am65-cpsw-nuss c000000.ethernet xg19: yt8614_read_status, phy addr: 10, link up, media UTP [ 2330.215908] am65-cpsw-nuss c000000.ethernet xg19: Link is Up - 100Mbps/Full - flow control off [ 2330.217375] switch: port 4(xg19) entered blocking state [ 2330.217385] switch: port 4(xg19) entered forwarding state [ 2354.790451] ------------[ cut here ]------------ [ 2354.790466] phy_check_link_status+0x0/0xf8: returned: -5 [ 2354.790546] WARNING: CPU: 4 PID: 12616 at drivers/net/phy/phy.c:1233 phy_state_machine+0xac/0x2f0 [ 2354.790559] Modules linked in: rpmsg_ctrl rpmsg_char virtio_rpmsg_bus rpmsg_ns rpmsg_core ti_k3_r5_remoteproc r8169 atemsys *** fuse [ 2354.790582] CPU: 4 PID: 12616 Comm: kworker/4:2 Tainted: G W 6.6.44-krc5-productive #1 Debian 6.6.44-3 d15816b0e2f7511437461580b670dfedb41c32d7 [ 2354.790590] Hardware name: *** KR C5 basic-2 (J784S4) (DT) [ 2354.790592] Workqueue: events_power_efficient phy_state_machine [ 2354.790598] pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 2354.790602] pc : phy_state_machine+0xac/0x2f0 [ 2354.790607] lr : phy_state_machine+0xac/0x2f0 [ 2354.790611] sp : ffff800085de3d60 [ 2354.790613] x29: ffff800085de3d60 x28: 0000000000000000 x27: 0000000000000000 [ 2354.790619] x26: ffffd90ecc92e360 x25: ffff39670940b940 x24: ffff396ec0109a05 [ 2354.790624] x23: 00000000fffffffb x22: ffff3966c0248ce8 x21: 0000000000000005 [ 2354.790629] x20: ffff3966c0248d40 x19: ffff3966c0248800 x18: ffff8000800d7020 [ 2354.790635] x17: 0000000000000000 x16: 0000000000000000 x15: 0000000000000000 [ 2354.790640] x14: 0000000000000000 x13: ffffd90ecae15e60 x12: ffffd90ecae82784 [ 2354.790645] x11: ffffd90ecae8b08c x10: 0000000000000b10 x9 : ffffd90ecbb843ac [ 2354.790650] x8 : 0000000000000000 x7 : 0000000000000000 x6 : 0000000000000000 [ 2354.790655] x5 : 0000000000000000 x4 : 0000000000000000 x3 : 0000000000000000 [ 2354.790659] x2 : 0000000000000000 x1 : 0000000000000000 x0 : 0000000000000000 [ 2354.790665] Call trace: [ 2354.790667] phy_state_machine+0xac/0x2f0 [ 2354.790672] process_one_work+0x148/0x3d0 [ 2354.790681] worker_thread+0x354/0x470 [ 2354.790686] kthread+0x11c/0x128 [ 2354.790692] ret_from_fork+0x10/0x20 [ 2354.790698] ---[ end trace 0000000000000000 ]---
就我们现在所看到的情况而言、这发生在随机端口上。
我们发现、随机设备连接到该设备时、不太可能出现连接设备的问题。
您能帮助我们找到问题的根本原因吗？
此致
Daniel
