eth0网卡无法使用,配置ip报错:
# ifconfig eth0 192.168.3.102
SIOCSIFFLAGS: Exec format error
只出现过一次,后面都无法复现了,请帮忙分析下,谢谢
eth0网卡无法使用,配置ip报错:
# ifconfig eth0 192.168.3.102
SIOCSIFFLAGS: Exec format error
只出现过一次,后面都无法复现了,请帮忙分析下,谢谢
您好:
单次偶现eth0网卡无法使用,可考虑eth0初始化失败,所以得抓出错时的log;可以从/userdata/log下看下是否有历史log保存;
谢谢
您好:
SIOCSIFFLAGS: Exec format error一般出现在网卡up失败的情况下。
从您这两行日志看,大概率是eth0在up的时候失败了,麻烦您提供下内核的日志,进一步分析看下。
谢谢!
您好,
长稳的问题,可能还是需要出现问题的现场日志的,不知道当时有保留吗,没有的话下次出现记得保留一下现场信息
Starting kernel …
Timer summary in microseconds (34 records):
Mark Elapsed Stage
0 0 reset
437,252 437,252 spl
450,859 13,607 after_spl_sdhc_pre_init
450,864 5 hb_module_load_apdp_begin
656,995 206,131 hb_module_load_apdp_end
707,289 50,294 finish_hb_set_bootdevice
735,048 27,759 spl_dram_init_begin
774,412 39,364 spl_dram_init_ddr_vref
777,406 2,994 spl_dram_init_pmic_init
1,023,951 246,545 spl_dram_init_ddr_init_param
1,209,862 185,911 end_spl
1,569,184 359,322 board_init_f
1,626,108 56,924 before_board_early_init_f
1,626,181 73 after_board_early_init_f
1,635,680 9,499 display_text_info
1,635,960 280 dram_init
1,696,449 60,489 board_init_r
1,718,172 21,723 initr_mmc
1,827,046 108,874 initr_env
1,827,835 789 id=64
1,832,838 5,003 id=65
1,833,109 271 before_last_stage_init
1,844,891 11,782 after_last_stage_init
1,844,891 0 main_loop
2,322,881 477,990 bootm_start
2,322,883 2 id=1
2,396,000 73,117 id=7
2,440,666 44,666 id=15
2,440,919 253 start_kernel
Accumulated time:
185 dm_spl
14,249 dm_r
27,752 spl_mcore_boot
56,907 dm_f
288,918 spl_dram_init
[BL31:1970:1:1:0:0:2:645871](0) NOTICE: hb_regmap_init stl init
[BL31:1970:1:1:0:0:2:857401](1) INFO: j5_pwr_domain_on_finish
[BL31:1970:1:1:0:0:2:858255](1) INFO: j5_pwr_domain_on_finish done
[BL31:1970:1:1:0:0:2:859937](2) INFO: j5_pwr_domain_on_finish
[BL31:1970:1:1:0:0:2:860784](2) INFO: j5_pwr_domain_on_finish done
[BL31:1970:1:1:0:0:2:862429](3) INFO: j5_pwr_domain_on_finish
[BL31:1970:1:1:0:0:2:863273](3) INFO: j5_pwr_domain_on_finish done
[BL31:1970:1:1:0:0:2:864899](4) INFO: j5_pwr_domain_on_finish
[BL31:1970:1:1:0:0:2:865742](4) INFO: j5_pwr_domain_on_finish done
[BL31:1970:1:1:0:0:2:867354](5) INFO: j5_pwr_domain_on_finish
[BL31:1970:1:1:0:0:2:868197](5) INFO: j5_pwr_domain_on_finish done
[BL31:1970:1:1:0:0:2:869802](6) INFO: j5_pwr_domain_on_finish
[BL31:1970:1:1:0:0:2:870645](6) INFO: j5_pwr_domain_on_finish done
[BL31:1970:1:1:0:0:2:872266](7) INFO: j5_pwr_domain_on_finish
[BL31:1970:1:1:0:0:2:873109](7) INFO: j5_pwr_domain_on_finish done
[M:1970:01:01:00:00:02:252491] E: diag bpu0 vm check open
[M:1970:01:01:00:00:02:253138] E: diag bpu0 vm check close
[M:1970:01:01:00:00:02:253790] E: diag bpu1 vm check open
[M:1970:01:01:00:00:02:254855] E: diag bpu1 vm check close
[BL31:1970:1:1:0:0:3:517661](2) INFO: fw_clk_get_rate: value: 0x00000001 id: 0, get clock ra
te 1200000000
[BL31:1970:1:1:0:0:3:535250](2) INFO: fw_clk_get_rate: value: 0x00000001 id: 1, get clock ra
te 1200000000
[BL31:1970:1:1:0:0:3:536696](2) INFO: fw_clk_get_rate: value: 0x00000003 id: 2, get clock ra
te 512000000
[BL31:1970:1:1:0:0:3:538113](2) INFO: fw_clk_get_rate: value: 0x00000003 id: 3, get clock ra
te 512000000
[BL31:1970:1:1:0:0:3:564231](2) INFO: fw_clk_get_rate: value: 0x00000001 id: 0, get clock ra
te 1200000000
[BL31:1970:1:1:0:0:3:565594](2) INFO: fw_clk_get_rate: value: 0x00000001 id: 0, get clock ra
te 1200000000
[M:1970:01:01:00:00:02:792735] E: diag bpu0 vm check open
[M:1970:01:01:00:00:02:793376] E: diag bpu1 vm check open
[M[:1970:01:01:00:00:02:794016] E: diag bpu0 vm check close
BL31:1970:1:1:0:0:3:630154](1) INFO: fw_clk_get_rate: value: 0x00000001 id: 1, get clock rat
e 1200000000
[BL31:1970:1:1:0:0:3:632448](1) INFO: fw_clk_get_rate: value: 0x00000001 id: 1, get clock ra
te 1200000000
[M:1970:01:01:00:00:02:798318] E: diag bpu1 vm check close
[BL31:1970:1:1:0:0:3:805130](1) NOTICE: hobot_customer_key_load 599:custom_root_pubkey load su
ccessed!keyhandle 0x80130e28
[BL31:1970:1:1:0:0:3:806795](1) NOTICE: hobot_customer_key_load 612:custom_sec_prikey load suc
cessed!keyhandle 0x80130e80
[BL31:1970:1:1:0:0:3:808347](1) NOTICE: hobot_customer_key_load 625:custom_cloud_pubkey load s
uccessed!keyhandle 0x80130ed8
[BL31:1970:1:1:0:0:3:814390](1) INFO: hobot_diag_init: Trying to register 74 diag module id
[0] via rpc
[BL31:1970:1:1:0:0:3:816097](1) INFO: hobot_diag_init: Trying to register 74 diag module id
[1] via rpc
[BL31:1970:1:1:0:0:3:817847](1) INFO: hobot_diag_init: Trying to register 74 diag module id
[2] via rpc
[BL31:1970:1:1:0:0:3:819535](1) INFO: hobot_diag_init: Trying to register 74 diag module id
[3] via rpc
[BL31:1970:1:1:0:0:3:821266](1) INFO: hobot_diag_init: Trying to register 74 diag module id
[4] via rpc
[BL31:1970:1:1:0:0:3:823257](1) INFO: hobot_diag_init: Trying to register 74 diag module id
[5] via rpc
[BL31:1970:1:1:0:0:3:826752](1) INFO: hobot_diag_init: Trying to register 74 diag module id
[87] via rpc
[BL31:1970:1:1:0:0:3:828819](1) INFO: hobot_diag_init: Trying to register 74 diag module id
[20] via rpc
[BL31:1970:1:1:0:0:3:830806](1) INFO: hobot_diag_init: Trying to register 74 diag module id
[19] via rpc
[BL31:1970:1:1:0:0:3:834167](1) INFO: hobot_diag_init: Trying to register 74 diag module id
[73] via rpc
[BL31:1970:1:1:0:0:3:838152](1) INFO: hobot_diag_init: Trying to register 74 diag module id
[80] via rpc
[BL31:1970:1:1:0:0:3:840770](1) INFO: hobot_diag_init: Trying to register 74 diag module id
[67] via rpc
[BL31:1970:1:1:0:0:3:842470](1) INFO: hobot_diag_init: Trying to register 74 diag module id
[24] via rpc
[BL31:1970:1:1:0:0:3:844168](1) INFO: hobot_diag_init: Trying to register 74 diag module id
[16] via rpc
[BL31:1970:1:1:0:0:3:845918](1) INFO: hobot_diag_init: Trying to register 74 diag module id
[31] via rpc
[BL31:1970:1:1:0:0:3:847616](1) INFO: hobot_diag_init: Trying to register 74 diag module id
[84] via rpc
[BL31:1970:1:1:0:0:3:849361](1) INFO: hobot_diag_init: Trying to register 74 diag module id
[78] via rpc
[BL31:1970:1:1:0:0:3:851059](1) INFO: hobot_diag_init: Trying to register 74 diag module id
[97] via rpc
[BL31:1970:1:1:0:0:3:852808](1) INFO: hobot_diag_init: Trying to register 74 diag module id
[105] via rpc
[BL31:1970:1:1:0:0:3:854523](1) INFO: hobot_diag_init: Trying to register 74 diag module id
[77] via rpc
[BL31:1970:1:1:0:0:3:856297](1) INFO: hobot_diag_init: Trying to register 74 diag module id
[120] via rpc
[BL31:1970:1:1:0:0:3:858017](1) INFO: hobot_diag_init: Trying to register 74 diag module id
[89] via rpc
[BL31:1970:1:1:0:0:3:859715](1) INFO: hobot_diag_init: Trying to register 74 diag module id
[7] via rpc
[BL31:1970:1:1:0:0:3:861449](1) INFO: hobot_diag_init: Trying to register 74 diag module id
[36] via rpc
[BL31:1970:1:1:0:0:3:863148](1) INFO: hobot_diag_init: Trying to register 74 diag module id
[75] via rpc
[BL31:1970:1:1:0:0:3:864896](1) INFO: hobot_diag_init: Trying to register 74 diag module id
[6] via rpc
[BL31:1970:1:1:0:0:3:866583](1) INFO: hobot_diag_init: Trying to register 74 diag module id
[121] via rpc
[BL31:1970:1:1:0:0:3:868338](1) INFO: hobot_diag_init: Trying to register 74 diag module id
[98] via rpc
[BL31:1970:1:1:0:0:3:870044](1) INFO: hobot_diag_init: Trying to register 74 diag module id
[21] via rpc
[BL31:1970:1:1:0:0:3:871744](1) INFO: hobot_diag_init: Trying to register 74 diag module id
[17] via rpc
[BL31:1970:1:1:0:0:3:873484](1) INFO: hobot_diag_init: Trying to register 74 diag module id
[130] via rpc
[BL31:1970:1:1:0:0:3:875198](1) INFO: hobot_diag_init: Trying to register 74 diag module id
[28] via rpc
[BL31:1970:1:1:0:0:3:877081](1) INFO: hobot_diag_init: Trying to register 74 diag module id
[70] via rpc
[BL31:1970:1:1:0:0:3:878784](1) INFO: hobot_diag_init: Trying to register 74 diag module id
[95] via rpc
[BL31:1970:1:1:0:0:3:880530](1) INFO: hobot_diag_init: Trying to register 74 diag module id
[114] via rpc
[BL31:1970:1:1:0:0:3:882249](1) INFO: hobot_diag_init: Trying to register 74 diag module id
[96] via rpc
[BL31:1970:1:1:0:0:3:883957](1) INFO: hobot_diag_init: Trying to register 74 diag module id
[132] via rpc
[BL31:1970:1:1:0:0:3:885713](1) INFO: hobot_diag_init: Trying to register 74 diag module id
[18] via rpc
[BL31:1970:1:1:0:0:3:887417](1) INFO: hobot_diag_init: Trying to register 74 diag module id
[81] via rpc
[BL31:1970:1:1:0:0:3:889170](1) INFO: hobot_diag_init: Trying to register 74 diag module id
[27] via rpc
[BL31:1970:1:1:0:0:3:890875](1) INFO: hobot_diag_init: Trying to register 74 diag module id
[71] via rpc
[BL31:1970:1:1:0:0:3:892628](1) INFO: hobot_diag_init: Trying to register 74 diag module id
[14] via rpc
[BL31:1970:1:1:0:0:3:894333](1) INFO: hobot_diag_init: Trying to register 74 diag module id
[131] via rpc
[BL31:1970:1:1:0:0:3:896051](1) INFO: hobot_diag_init: Trying to register 74 diag module id
[113] via rpc
[BL31:1970:1:1:0:0:3:897818](1) INFO: hobot_diag_init: Trying to register 74 diag module id
[26] via rpc
[BL31:1970:1:1:0:0:3:899526](1) INFO: hobot_diag_init: Trying to register 74 diag module id
[133] via rpc
[BL31:1970:1:1:0:0:3:901284](1) INFO: hobot_diag_init: Trying to register 74 diag module id
[32] via rpc
[BL31:1970:1:1:0:0:3:902993](1) INFO: hobot_diag_init: Trying to register 74 diag module id
[13] via rpc
[BL31:1970:1:1:0:0:3:904740](1) INFO: hobot_diag_init: Trying to register 74 diag module id
[35] via rpc
[BL31:1970:1:1:0:0:3:906448](1) INFO: hobot_diag_init: Trying to register 74 diag module id
[112] via rpc
[BL31:1970:1:1:0:0:3:908167](1) INFO: hobot_diag_init: Trying to register 74 diag module id
[15] via rpc
[BL31:1970:1:1:0:0:3:909914](1) INFO: hobot_diag_init: Trying to register 74 diag module id
[29] via rpc
[BL31:1970:1:1:0:0:3:911625](1) INFO: hobot_diag_init: Trying to register 74 diag module id
[23] via rpc
[BL31:1970:1:1:0:0:3:913379](1) INFO: hobot_diag_init: Trying to register 74 diag module id
[12] via rpc
[BL31:1970:1:1:0:0:3:915088](1) INFO: hobot_diag_init: Trying to register 74 diag module id
[122] via rpc
[BL31:1970:1:1:0:0:3:916849](1) INFO: hobot_diag_init: Trying to register 74 diag module id
[22] via rpc
[BL31:1970:1:1:0:0:3:918559](1) INFO: hobot_diag_init: Trying to register 74 diag module id
[11] via rpc
[BL31:1970:1:1:0:0:3:920303](1) INFO: hobot_diag_init: Trying to register 74 diag module id
[34] via rpc
[BL31:1970:1:1:0:0:3:922016](1) INFO: hobot_diag_init: Trying to register 74 diag module id
[9] via rpc
[BL31:1970:1:1:0:0:3:923714](1) INFO: hobot_diag_init: Trying to register 74 diag module id
[66] via rpc
[BL31:1970:1:1:0:0:3:925464](1) INFO: hobot_diag_init: Trying to register 74 diag module id
[123] via rpc
[BL31:1970:1:1:0:0:3:927187](1) INFO: hobot_diag_init: Trying to register 74 diag module id
[90] via rpc
[BL31:1970:1:1:0:0:3:928937](1) INFO: hobot_diag_init: Trying to register 74 diag module id
[115] via rpc
[BL31:1970:1:1:0:0:3:930662](1) INFO: hobot_diag_init: Trying to register 74 diag module id
[79] via rpc
[BL31:1970:1:1:0:0:3:932414](1) INFO: hobot_diag_init: Trying to register 74 diag module id
[25] via rpc
[BL31:1970:1:1:0:0:3:934128](1) INFO: hobot_diag_init: Trying to register 74 diag module id
[43] via rpc
[BL31:1970:1:1:0:0:3:935812](1) INFO: hobot_diag_init: Trying to register 74 diag module id
[76] via rpc
[BL31:1970:1:1:0:0:3:937564](1) INFO: hobot_diag_init: Trying to register 74 diag module id
[10] via rpc
[BL31:1970:1:1:0:0:3:939278](1) INFO: hobot_diag_init: Trying to register 74 diag module id
[91] via rpc
[BL31:1970:1:1:0:0:3:941059](1) INFO: hobot_diag_init: Trying to register 74 diag module id
[68] via rpc
[BL31:1970:1:1:0:0:3:942775](1) INFO: hobot_diag_init: Trying to register 74 diag module id
[30] via rpc
[BL31:1970:1:1:0:0:3:944533](1) INFO: hobot_diag_init: Trying to register 74 diag module id
[33] via rpc
[BL31:1970:1:1:0:0:3:946249](1) INFO: hobot_diag_init: Trying to register 74 diag module id
[106] via rpc
[BL31:1970:1:1:0:0:3:947976](1) INFO: hobot_diag_init: Trying to register 74 diag module id
[94] via rpc
login[290]: root login on ‘console’
@j5dvb:/home/root#
@j5dvb:/home/root# [M:1970:01:01:00:00:03:536120] E: setting fchm for 2nd
@j5dvb:/home/root#
@j5dvb:/home/root# [BL31:1970:1:1:0:0:4:781786](4) INFO: fw_clk_get_rate: value: 0x00000003
id: 2, get clock rate 512000000
[BL31:1970:1:1:0:0:4:784065](3) INFO: fw_clk_get_rate: value: 0x00000003 id: 3, get clock ra
te 512000000
@j5dvb:/home/root#
@j5dvb:/home/root#
@j5dvb:/home/root#
@j5dvb:/home/root# [M:1970:01:01:00:00:04:487618] E: diag bpu0 vm check open
[M:1970:01:01:00:00:04:488259] E: diag bpu0 vm check close
[M:1970:01:01:00:00:04:504787] E: diag bpu0 vm check open
[M:1970:01:01:00:00:04:576643] E: diag bpu1 vm check open
[M:1970:01:01:00:00:04:577290] E: diag bpu1 vm check close
[M:1970:01:01:00:00:04:592746] E: diag bpu1 vm check open
[M:1970:01:01:00:00:04:631524] E: diag bpu0 vm check close
mark system success(normal boot)
@j5dvb:/home/root# [M:1970:01:01:00:00:04:719500] E: diag bpu1 vm check close
[M:1970:01:01:00:00:04:743054] E: acore_msg: 18-12-3-65535
[M:1970:01:01:00:00:04:743709] E: payload: 0x0-0x0-0x0-0x0
[M:1970:01:01:00:00:04:744497] E: magic id: 33
[M:1970:01:01:00:00:04:745032] E: magic info: 18 12 3 65535
[M:1970:01:01:00:00:04:745951] E: spi_service_diag success.
[M:1970:01:01:00:00:04:873111] E: acore_msg: 18-15-2-584
[M:1970:01:01:00:00:04:873744] E: payload: 0x0-0x0-0x0-0x0
[M:1970:01:01:00:00:04:874652] E: spi_service_diag success.
[M:1970:01:01:00:00:04:939057] E: acore_msg: 18-15-2-584
[M:1970:01:01:00:00:04:939690] E: payload: 0x0-0x0-0x0-0x0
[M:1970:01:01:00:00:05:004105] E: acore_msg: 18-15-2-584
[M:1970:01:01:00:00:05:004739] E: payload: 0x0-0x0-0x0-0x0
[M:1970:01:01:00:00:05:070048] E: acore_msg: 18-15-2-584
[M:1970:01:01:00:00:05:070681] E: payload: 0x0-0x0-0x0-0x0
[M:1970:01:01:00:00:05:135029] E: acore_msg: 18-15-2-584
[M:1970:01:01:00:00:05:135662] E: payload: 0x0-0x0-0x0-0x0
[M:1970:01:01:00:00:05:201109] E: acore_msg: 18-15-2-584
[M:1970:01:01:00:00:05:201742] E: payload: 0x0-0x0-0x0-0x0
[M:1970:01:01:00:00:05:266070] E: acore_msg: 18-15-2-584
[M:1970:01:01:00:00:05:266703] E: payload: 0x0-0x0-0x0-0x0
[M:1970:01:01:00:00:05:332029] E: acore_msg: 18-15-2-584
[M:1970:01:01:00:00:05:332662] E: payload: 0x0-0x0-0x0-0x0
[M:1970:01:01:00:00:05:397098] E: acore_msg: 18-15-2-584
内核的启动日志如上。
[M:1970:01:01:00:00:05:332662] E: payload: 0x0-0x0-0x0-0x0
[M:1970:01:01:00:00:05:397098] E: acore_msg: 18-15-2-584
-- 这些错误信息是表示什么意思呢?
现场的内核日志没了,后面也没复现出来。
[M:1970:01:01:00:00:05:332662] E: payload: 0x0-0x0-0x0-0x0
[M:1970:01:01:00:00:05:397098] E: acore_msg: 18-15-2-584
还有一种现象,配置IP后,狂打这些打印,是什么原因呢?
这些都是fusa错误的,看着好像跟问题本身没啥关系的
18-15-2-584是硬件fusa错误码,表示网卡发生了FSM timeout。
请提供下您的软件版本和硬件版本信息。是自己编译的软件还是地平线提供的软件?
软件版本:rel-j5-cs-v1.0-LNX5.10_REL_CS_PL3.0_2022081004
硬件版本:不确定,是4J5的单板
内核镜像是自己构建的,但是没有修改网卡驱动相关的代码
出现这个fusa错误的原因比较多,这个错误码表示网卡的状态机超时了,可能是CPU或者DDR带宽压力过大(若开启了内核KASAN和hpr32),也可能是开启了网卡的时隙发送功能后,发送超时引起的。
没有当时的dmesg打印的话,比较难定位。
建议出现异常时,保存下现场的打印把,有利于定位问题。
[M:1970:01:01:00:00:05:332662] E: payload: 0x0-0x0-0x0-0x0
[M:1970:01:01:00:00:05:397098] E: acore_msg: 18-15-2-584
偶现reboot后疯狂打印以上两句日志,且eth0网卡无法使用,配置ip报错:
# ifconfig eth0 192.168.3.102
SIOCSIFFLAGS: Exec format error
当时出现故障的日志只记录了这部分,请问一下该故障可以确定是ethernet网卡的问题么?有修复方案么?谢谢。
1. 偶现reboot后疯狂打印以上两句日志----这个问题大概率是ddr带宽紧张,可以看下是否开启了内核KASAN和hpr32,ETH 访问 DDR的超时时间是64ms。
2. SIOCSIFFLAGS: Exec format error-----这个问题和上面的584fusa报错没有必然联系,需要借助dmesg内核打印看下,有可能是网卡初始化失败了,需要借助内核打印才能进一步确认。
KASAN未配置,hpr32是什么功能,在代码中未搜索到