tests/net/net_pkt failed on mimxrt1050_evk board. #21257
Assignees
Labels
area: Networking
bug
The issue is a bug, or the PR is fixing a bug
priority: low
Low impact/importance bug
Comments
|
I just tested this and I could only trigger the issue half of the time. This is some timing issue that happens semi-randomly, I will investigate. |
jukkar
added a commit
to jukkar/zephyr
that referenced
this issue
Dec 11, 2019
It is possible that the network interface is not yet initialized when status of the PHY changes. In this case we must not call net_eth_carrier_on() as that will cause a crash. This was noticed with mimxrt1050_evk board. Fixes: zephyrproject-rtos#21257 Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
jukkar
added a commit
that referenced
this issue
Dec 12, 2019
It is possible that the network interface is not yet initialized when status of the PHY changes. In this case we must not call net_eth_carrier_on() as that will cause a crash. This was noticed with mimxrt1050_evk board. Fixes: #21257 Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
armandciejak
pushed a commit
to riedonetworks/zephyr
that referenced
this issue
Jun 19, 2020
It is possible that the network interface is not yet initialized when status of the PHY changes. In this case we must not call net_eth_carrier_on() as that will cause a crash. This was noticed with mimxrt1050_evk board. Fixes: zephyrproject-rtos#21257 (cherry picked from commit e124c1c) Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
Zhaoningx
pushed a commit
to Zhaoningx/zephyr
that referenced
this issue
Sep 15, 2020
It is possible that the network interface is not yet initialized when status of the PHY changes. In this case we must not call net_eth_carrier_on() as that will cause a crash. This was noticed with mimxrt1050_evk board. Fixes: zephyrproject-rtos#21257 Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
nashif
pushed a commit
that referenced
this issue
Sep 23, 2020
It is possible that the network interface is not yet initialized when status of the PHY changes. In this case we must not call net_eth_carrier_on() as that will cause a crash. This was noticed with mimxrt1050_evk board. Fixes: #21257 Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
It was similar to the issue #20088 and #20007.
To Reproduce
Steps to reproduce the behavior:
Screenshots or console output
E: ***** BUS FAULT *****
E: Precise data bus error
E: BFAR Address: 0x3a4f7828
E: r0/a1: 0x00000000 r1/a2: 0x6000b7f9 r2/a3: 0x00000000
E: r3/a4: 0x3a4f7820 r12/ip: 0x00000000 r14/lr: 0x60003ceb
E: xpsr: 0x41000000
E: Faulting instruction address (r15/pc): 0x60006a46
E: >>> ZEPHYR FATAL ERROR 0: CPU exception on CPU 0
E: Current thread: 0x800011d0 (sysworkq)
E: Halting system
Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: