同问：
我的R4S也是。。。lan口崩了，灯不亮或者常亮，然后卡死，一般1-2天之内。。。
这是硬件问题还是软件问题，如果排查啊
报错日志有：
2025/9/4 2:55:38 R4S daemon procd Got unexpected signal 1
2025/9/4 2:55:37 R4S daemon dropbear Consider using option 'DirectInterface' to bind directly to interface
2025/9/4 2:55:37 R4S daemon dropbear Option 'Interface' binds to address(es) but not to interface
2025/9/4 2:55:37 R4S daemon odhcp6c Failed to send SOLICIT message to ff02::1:2 (Address not available)
2025/9/4 2:55:36 R4S daemon netifd Interface 'wan_6' is setting up now
2025/9/4 2:55:36 R4S daemon netifd Interface 'wan_6' has link connectivity
2025/9/4 2:55:36 R4S daemon netifd Interface 'wan_6' is enabled
2025/9/4 2:55:36 R4S daemon netifd Network alias 'pppoe-wan' link is up
2025/9/4 2:55:36 R4S daemon netifd Interface 'wan' is now up
2025/9/4 2:55:36 R4S daemon netifd Network device 'pppoe-wan' link is up
2025/9/4 2:55:36 R4S daemon pppd secondary DNS address xxxxxxx
2025/9/4 2:55:36 R4S daemon pppd primary DNS address xxxxxxx
2025/9/4 2:55:36 R4S daemon pppd remote IP address xxxxxxx
2025/9/4 2:55:36 R4S daemon pppd local IP address xxxxxxxx
2025/9/4 2:55:36 R4S daemon pppd remote LL address fe80::b438:04ff:xxxxxx
2025/9/4 2:55:36 R4S daemon pppd local LL address fe80::8234:282e:xxxxxxxx
2025/9/4 2:55:36 R4S daemon pppd peer from calling number xxxxx authorized
2025/9/4 2:55:36 R4S daemon pppd PAP authentication succeeded
2025/9/4 2:55:36 R4S daemon pppd Remote message: Authentication Successful,Welcome!
2025/9/4 2:55:36 R4S daemon pppd syncppp not active
2025/9/4 2:55:36 R4S daemon pppd Connect: pppoe-wan <--> eth0
2025/9/4 2:55:36 R4S daemon pppd Using interface pppoe-wan
2025/9/4 2:55:36 R4S daemon pppd Connected to xxxxxxxxx via interface eth0
2025/9/4 2:55:36 R4S daemon pppd PPP session is 63765
2025/9/4 2:55:00 R4S kern kernel [101629.962666] rk3x-i2c ff3c0000.i2c: timeout, ipd: 0x10, state: 1
2025/9/4 2:54:59 R4S kern kernel [101628.938662] rk3x-i2c ff3c0000.i2c: timeout, ipd: 0x10, state: 1
2025/9/4 2:54:58 R4S kern kernel [101627.914658] rk3x-i2c ff3c0000.i2c: timeout, ipd: 0x10, state: 1
2025/9/4 2:54:53 R4S kern kernel [101623.788532] cpufreq: __target_index: Failed to change cpu frequency: -110
2025/9/4 2:54:53 R4S kern kernel [101623.788012] cpu cpu4: Failed to set regulator voltages: -110
2025/9/4 2:54:53 R4S kern kernel [101623.787215] cpu cpu4: _set_opp_voltage: failed to set voltage (1025000 1025000 1250000 mV): -110
2025/9/4 2:54:53 R4S kern kernel [101623.786638] rk3x-i2c ff3c0000.i2c: timeout, ipd: 0x10, state: 1
2025/9/4 2:54:52 R4S kern kernel [101622.762633] rk3x-i2c ff3c0000.i2c: timeout, ipd: 0x10, state: 1
2025/9/4 2:54:51 R4S kern kernel [101621.738624] rk3x-i2c ff3c0000.i2c: timeout, ipd: 0x10, state: 1
2025/9/4 2:54:50 R4S kern kernel [101620.714619] rk3x-i2c ff3c0000.i2c: timeout, ipd: 0x10, state: 1
2025/9/4 2:54:49 R4S kern kernel [101619.690612] rk3x-i2c ff3c0000.i2c: timeout, ipd: 0x10, state: 1
2025/9/4 2:54:48 R4S kern kernel [101618.666607] rk3x-i2c ff3c0000.i2c: timeout, ipd: 0x10, state: 1
2025/9/4 2:54:47 R4S kern kernel [101617.678585] dwmmc_rockchip fe320000.mmc: Unexpected interrupt latency
2025/9/4 2:54:47 R4S daemon pppd Sent 3686835501 bytes, received 1881978798 bytes.
2025/9/4 2:54:47 R4S daemon pppd Connect time 1693.4 minutes.
2025/9/4 2:54:47 R4S daemon pppd Serial link appears to be disconnected.
2025/9/4 2:54:47 R4S daemon pppd No response to 5 echo-requests
