Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

zeus-next GPP crashes on startup, ARM 32bit #60

Open
btgoodwin opened this issue Jul 7, 2020 · 0 comments
Open

zeus-next GPP crashes on startup, ARM 32bit #60

btgoodwin opened this issue Jul 7, 2020 · 0 comments

Comments

@btgoodwin
Copy link
Contributor

btgoodwin commented Jul 7, 2020

Layers:

zeus      poky/meta
          poky/meta-poky
          poky/meta-yocto-bsp
zeus      meta-openembedded/meta-oe
          meta-openembedded/meta-python
          meta-openembedded/meta-filesystems
          meta-openembedded/meta-networking
zeus      meta-python2
zeus-next meta-redhawk-sdr

Image: redhawk-test-image

Error output:

2020-07-07 18:03:34 INFO  DeviceManagerLoader:457 - Starting Device Manager with /nodes/DevMgr-gpp/DeviceManager.dcd.xml
2020-07-07 18:03:34 INFO  DeviceManager:493 - adding in property for :DCE:fefb9c66-d14a-438d-ad59-2cfd1adb272b value : armv7vet2hf-neon
2020-07-07 18:03:34 INFO  DeviceManager:497 - adding in property for :DCE:4a23ad60-0b25-4121-a630-68803a498f75 value : Linux
2020-07-07 18:03:34 INFO  DeviceManager:664 - Connecting to Domain Manager REDHAWK_DEV/REDHAWK_DEV
2020-07-07 18:03:34 INFO  DeviceManager:1044 - Placing Component CompId: DevMgr-gpp:GPP ProfileName : GPP
2020-07-07 18:03:34 INFO  DeviceManagerLoader:511 - Starting ORB!
2020-07-07 18:03:35 INFO  GPP.system.Device:1188 - DEV-ID:DevMgr-gpp:GPP Requesting IDM CHANNEL IDM_Channel
2020-07-07 18:03:35 INFO  GPP.system.EventManager:606 - PUBLISHER - Channel:IDM_Channel Reg-Idf881e3c7-ebce-4d83-9717-bce322eeb312 RESOURCE:DevMgr-gpp:GPP
2020-07-07 18:03:35 INFO  DeviceManager:1596 - Registering device GPP device id DevMgr-gpp:GPP on Device Manager DevMgr-gpp
2020-07-07 18:03:35 INFO  DeviceManager:1636 - Device LABEL: GPP  SPD loaded: GPP' - 'DCE:4e20362c-4442-4656-af6d-aedaaf13b275
2020-07-07 18:03:35 INFO  GPP:1073 - initialize()
2020-07-07 18:03:35 INFO  GPP.system.EventManager:664 - SUBSCRIBER - Channel:ODM_Channel Reg-Id002ba541-1c97-4093-b8ec-6b72a35b3a35 resource:DevMgr-gpp:GPP
2020-07-07 18:03:35 INFO  GPP:1094 - Component Output Redirection is DISABLED.
2020-07-07 18:03:35 INFO  GPP:2241 - Affinity Disable State,  disabled=1
2020-07-07 18:03:35 INFO  GPP:2243 - Disabling affinity processing requests.
2020-07-07 18:03:35 INFO  GPP:858 -  initialize CPU Monitor --- wl size 0
terminate called without an active exception
2020-07-07 18:03:38 ERROR DeviceManager:1700 - The following CORBA exception occurred: COMM_FAILURE while attempting to initialize Device GPP. Device registration with Device Manager failed
2020-07-07 18:03:38 WARN  DeviceManager:2913 - Child process GPP (pid 821) has terminated with signal 6

My guess is that somewhere along the line, the mechanisms under the hood for probing the underlying Linux system (coreutils, etc.) have been updated to a point that there is breakage with the typical busybox counterparts that get installed. This particular error doesn't happen on qemuarm64, however, so it's unclear if this is a busybox problem if it's resolvable by replacing a tool (like eliminating the ps patch by setting an RDEPENDS against procps).

@btgoodwin btgoodwin reopened this Jul 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant