Hi all,
=> Using the follwing steps to verifity wake-on-lan function
It will fail and system reboot.
Steps:
- Direct using ethernet cable to connect Xavier-NX and PC
- Setting static IP on both sides.
- Xavier-NX Commands:
sudo ethtool -s eth0 wol g
sudo systemctl suspend - PC(Windows) Commands:
WolCmd.exe [MAC] [IP] [Subnet-Mask]
- Wake-on-lan function fail and system reboot.
xavier-nx-wol.log.log (30.4 KB)
Pass-Log(xavier-nx-wol.log)
…
adc_resume done
tegra_clks_resume
tegra_clks_resume done
ec_resume done
resume check ok
pe exiting sc7
ier2 wake event received wake id = 20
146.135057] tegra_cec 3960000.tegra_cec: suspended
[ 146.250093] CPU1: shutdown
[ 146.290098] CPU2: shutdown
[ 146.322583] CPU3: shutdown
[ 146.360746] cache: parent cpu1 should not be sleeping
[ 146.378376] cache: parent cpu2 should not be sleeping
[ 146.404154] cache: parent cpu3 should not be sleeping
[ 148.145260] tegra_cec 3960000.tegra_cec: Resuming
[ 148.145280] tegra_cec 3960000.tegra_cec: tegra_cec_init started
[ 149.145537] tegra_cec 3960000.tegra_cec: tegra_cec_init Done.
…
Fail-Log(xavier-nx-wol.log)
…
adc_resume done
tegra_clks_resume
tegra_clks_resume done
ec_resume done
resume check ok
pe exiting sc7
ier2 wake event received wake id = 20
hutdown state requested 1
Rebooting system …
?
[0000.024] W> RATCHET: MB1 binary ratchet value 4 is too large than ratchet level 2 from HW fuses.
[0000.033] I> MB1 (prd-version: 1.5.1.9-t194-41334769-73a9b7ef)
…
=> Using xavier-nx + L4T32.7.1 always can reproduce the problem.
Any help will be appreciated.