-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
nodelet manager process has died, exit code -11, dmesg --> usb usb2-port3: cannot disable, segfault #10624
Comments
Hi @byhang Is launch able to complete successfully if you use the original rs_camera.launch instead of your own copy of it? Also, I note that your roslaunch log is identifying two separate cameras with unique serial numbers, a D435 and D435i. Can you confirm whether you are launching more than one camera, please? Thanks! |
Hi @MartyG-RealSense ➜ ~ roslaunch realsense2_camera rs_camera.launch camera:=fcb_hu_cam usb_port_id:=2-2 started roslaunch server http://Eros:41353/ SUMMARYPARAMETERS
NODES ROS_MASTER_URI=http://localhost:11311 process[fcb_hu_cam/realsense2_camera_manager-1]: started with pid [28333] [ INFO] [1656216895.387487237]: Device with physical ID 2-2-12 was found. dmesg[ 2666.520371] input: Intel(R) RealSense(TM) Depth Ca as /devices/pci0000:00/0000:00:14.0/usb2/2-2/2-2:1.0/input/input28 |
The cause of the 'entity type' kernel messages tends to be difficult to trace and if they are corrected then you may never find out for sure what caused them in the first place. I previously enquired to the RealSense development team about them in 2020 and received the following explanation. The message “Entity camera ... not initialized" is related to UVC topology defined in the firmware descriptor for USB device. The most recent RealSense ROS user who experienced the errors suspected at #10158 (comment) that the problem had occurred because they had several different versions of the librealsense SDK installed on their computer. Is the presence of multiple librealsense installations a possibility on your own computer, please? |
Hi @MartyG-RealSense , This is my installed deb version, all are the default, lasted versions in Ubuntu-16.04.
install log➜ sudo apt-get install librealsense2-dkms uvcvideo:
videodev.ko:
hid-sensor-accel-3d.ko:
hid-sensor-gyro-3d.ko:
depmod.... DKMS: install completed. uvcvideo:
videodev.ko:
hid-sensor-accel-3d.ko:
hid-sensor-gyro-3d.ko:
depmod.... DKMS: install completed. ➜ sudo apt-get install ros-$ROS_DISTRO-realsense2-camera |
From the information at the top of this case, it looks as though your intention was to use librealsense 2.45.0 and its matching ROS wrapper 2.3.0. Indeed, this is shown in the roslaunch log. In your latest comment at #10624 (comment) the logs have references to both librealsense 2.45.0 and 2.50.0, and two different kernel versions (4.13.0-36-generic and 4.15.0-142-generic). In that comment, it also logs that the ROS wrapper's 'Method 1' installation process of sudo apt-get install ros-$ROS_DISTRO-realsense2-camera was used. This would install both the librealsense SDK and the ROS wrapper from packages at the same time. This install method will also install the currently latest librealsense version and its matching wrapper. So using that command today would not install 2.45.0 and 2.3.0, but instead install librealsense 2.50.0 and wrapper 2.3.2. So if you had already installed librealsense 2.45.0 previously and then ran the Method 1 command then you could end up with two potentially conflicting installations of different versions of librealsense on the same computer. My recommendations would therefore be:
|
Hi @MartyG-RealSense https://github.com/IntelRealSense/librealsense/blob/master/doc/distribution_linux.md apt search realsenseSorting... Done librealsense2/xenial 2.50.0-0~realsense0.6126 amd64 librealsense2-dbg/xenial 2.50.0-0~realsense0.6126 amd64 librealsense2-dev/xenial 2.50.0-0~realsense0.6126 amd64 librealsense2-dkms/xenial 1.3.18-0ubuntu1 all librealsense2-gl/xenial 2.50.0-0~realsense0.6126 amd64 librealsense2-gl-dbg/xenial 2.50.0-0~realsense0.6126 amd64 librealsense2-gl-dev/xenial 2.50.0-0~realsense0.6126 amd64 librealsense2-net/xenial 2.50.0-0~realsense0.6126 amd64 librealsense2-net-dbg/xenial 2.50.0-0~realsense0.6126 amd64 librealsense2-net-dev/xenial 2.50.0-0~realsense0.6126 amd64 librealsense2-udev-rules/xenial 2.50.0-0~realsense0.6126 amd64 librealsense2-utils/xenial 2.50.0-0~realsense0.6126 amd64 librscalibrationapi/xenial 2.6.8.0 amd64 librscalibrationtool/xenial 2.11.1.0 amd64 realsense-sdk/xenial 2.7.7-0~realsense0.29 amd64 realsense-sdk-dbg/xenial 2.7.7-0~realsense0.29 amd64 realsense-sdk-dev/xenial 2.7.7-0~realsense0.29 amd64 realsense-sdk-udev-rules/xenial 2.7.7-0~realsense0.29 amd64 realsense-sdk-utils/xenial 2.7.7-0~realsense0.29 amd64 realsense-uvcvideo/xenial 1.1.0-0ubuntu3 all ros-kinetic-librealsense/xenial 1.12.2-1xenial-20210506-081035-0800 amd64 ros-kinetic-librealsense2/xenial 2.45.0-1xenial-20210506-081043-0800 amd64 ros-kinetic-realsense-camera/xenial 1.8.1-1xenial-20210506-082012-0800 amd64 ros-kinetic-realsense2-camera/xenial 2.3.0-1xenial-20210506-084151-0800 amd64 ros-kinetic-realsense2-description/xenial 2.3.0-1xenial-20210506-081408-0800 amd64 rs-dfu-tool/xenial 0.9.6 amd64 |
Hi @MartyG-RealSense , I have to test at 2.3.0, because the newest official version is 2.3.0 in Ubuntu-16.04.
$ dpkg -l | grep realsense
$ roslaunch realsense2_camera rs_camera.launch usb_port_id:=2-2[ INFO] [1656321482.793619608]: Stereo Module was found. dmesg[ 268.246154] nodelet[5891]: segfault at 1 ip 00007f762eef24a1 sp 00007f760127ba80 error 6 in librostime.so[7f762eedb000+2b000] |
Regarding the [camera/realsense2_camera_manager-1] process has died error at the end of the launch process, a RealSense ROS user of Kinetic experienced it in IntelRealSense/realsense-ros#473 and the solution for them in their particular case was a completely fresh installation. In another similar case at IntelRealSense/realsense-ros#1774 where the error number was -2 instead of -1, building the ROS wrapper from source code instead of packages resolved it. |
Thank you @MartyG-RealSense very much for your careful assistance. |
Before opening a new issue, we wanted to provide you with some useful suggestions (Click "Preview" above for a better view):
All users are welcomed to report bugs, ask questions, suggest or request enhancements and generally feel free to open new issue, even if they haven't followed any of the suggestions above :)
Issue Description
Hi Intel,
I got error when launch official realsense-ros-2.3.0, use my launch file which copy from rs_camera.launch and include/nodelet.launch.xml.
roslaunch error:
[ WARN] [1656065577.814077970]: Param '/fl_cam/stereo_module/auto_exposure_limit' has value 0 that is not in range [1, 200000]. Removing this parameter from dynamic reconfigure options.
[ WARN] [1656065577.827148874]: Param '/fl_cam/stereo_module/auto_gain_limit' has value 0 that is not in range [16, 248]. Removing this parameter from dynamic reconfigure options.
[ INFO] [1656065577.962120107]: Done Setting Dynamic reconfig parameters.
[ INFO] [1656065577.963537216]: depth stream is enabled - width: 848, height: 480, fps: 15, Format: Z16
[ INFO] [1656065577.964731016]: color stream is enabled - width: 640, height: 480, fps: 6, Format: RGB8
[ INFO] [1656065577.968293423]: setupPublishers...
[fl_cam/fl_cam_manager-2] process has died [pid 8828, exit code -11, cmd /opt/ros/kinetic/lib/nodelet/nodelet manager __name:=fl_cam_manager __log:=/home/byhang/.ros/log/2a5b1e34-f3a5-11ec-86dd-74e5f9ec52bb/fl_cam-fl_cam_manager-2.log].
log file: /home/byhang/.ros/log/2a5b1e34-f3a5-11ec-86dd-74e5f9ec52bb/fl_cam-fl_cam_manager-2*.log
dmesg error
[ 82.557328] audit: type=1400 audit(1656065110.496:34): apparmor="DENIED" operation="open" profile="/usr/lib/telepathy/mission-control-5" name="/etc/dconf/profile/user" pid=2878 comm="mission-control" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
[ 113.897267] usb 2-2: USB disconnect, device number 2
[ 116.283063] usb 2-2: new SuperSpeed USB device number 4 using xhci_hcd
[ 116.303670] usb 2-2: New USB device found, idVendor=8086, idProduct=0b07
[ 116.303677] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 116.303682] usb 2-2: Product: Intel(R) RealSense(TM) Depth Camera 435
[ 116.303686] usb 2-2: Manufacturer: Intel(R) RealSense(TM) Depth Camera 435
[ 116.303690] usb 2-2: SerialNumber: 901523021387
[ 116.305049] uvcvideo: Found UVC 1.50 device Intel(R) RealSense(TM) Depth Camera 435 (8086:0b07)
[ 116.306993] uvcvideo: Unable to create debugfs 2-4 directory.
[ 116.307146] uvcvideo 2-2:1.0: Entity type for entity Intel(R) RealSense(TM) Depth Ca was not initialized!
[ 116.307153] uvcvideo 2-2:1.0: Entity type for entity Processing 2 was not initialized!
[ 116.307158] uvcvideo 2-2:1.0: Entity type for entity Camera 1 was not initialized!
[ 116.307485] input: Intel(R) RealSense(TM) Depth Ca as /devices/pci0000:00/0000:00:14.0/usb2/2-2/2-2:1.0/input/input21
[ 116.308545] uvcvideo: Found UVC 1.50 device Intel(R) RealSense(TM) Depth Camera 435 (8086:0b07)
[ 116.309485] uvcvideo: Unable to create debugfs 2-4 directory.
[ 116.309666] uvcvideo 2-2:1.3: Entity type for entity Processing 7 was not initialized!
[ 116.309672] uvcvideo 2-2:1.3: Entity type for entity Extension 8 was not initialized!
[ 116.309677] uvcvideo 2-2:1.3: Entity type for entity Camera 6 was not initialized!
[ 117.522720] xhci_hcd 0000:00:14.0: Cannot set link state.
[ 117.522732] usb usb2-port3: cannot disable (err = -32)
[ 117.522743] usb 2-3: USB disconnect, device number 3
[ 117.523917] hid-sensor-hub 0003:8086:0B3A.0001: No report with id 0xffffffff found
[ 117.523939] hid-sensor-hub 0003:8086:0B3A.0001: No report with id 0xffffffff found
[ 117.524161] hid-sensor-hub 0003:8086:0B3A.0001: No report with id 0xffffffff found
[ 119.082831] usb 2-3: new SuperSpeed USB device number 5 using xhci_hcd
[ 119.103201] usb 2-3: New USB device found, idVendor=8086, idProduct=0b3a
[ 119.103202] usb 2-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 119.103203] usb 2-3: Product: Intel(R) RealSense(TM) Depth Camera 435i
[ 119.103204] usb 2-3: Manufacturer: Intel(R) RealSense(TM) Depth Camera 435i
[ 119.103205] usb 2-3: SerialNumber: 903223053633
[ 119.104302] uvcvideo: Found UVC 1.50 device Intel(R) RealSense(TM) Depth Camera 435i (8086:0b3a)
[ 119.105887] uvcvideo: Unable to create debugfs 2-5 directory.
[ 119.105910] uvcvideo 2-3:1.0: Entity type for entity Intel(R) RealSense(TM) Depth Ca was not initialized!
[ 119.105911] uvcvideo 2-3:1.0: Entity type for entity Processing 2 was not initialized!
[ 119.105912] uvcvideo 2-3:1.0: Entity type for entity Camera 1 was not initialized!
[ 119.105956] input: Intel(R) RealSense(TM) Depth Ca as /devices/pci0000:00/0000:00:14.0/usb2/2-3/2-3:1.0/input/input22
[ 119.106282] uvcvideo: Found UVC 1.50 device Intel(R) RealSense(TM) Depth Camera 435i (8086:0b3a)
[ 119.107060] uvcvideo: Unable to create debugfs 2-5 directory.
[ 119.107087] uvcvideo 2-3:1.3: Entity type for entity Processing 7 was not initialized!
[ 119.107087] uvcvideo 2-3:1.3: Entity type for entity Extension 8 was not initialized!
[ 119.107088] uvcvideo 2-3:1.3: Entity type for entity Camera 6 was not initialized!
[ 119.166972] hid-sensor-hub 0003:8086:0B3A.0003: No report with id 0xffffffff found
[ 119.167442] hid-sensor-hub 0003:8086:0B3A.0003: No report with id 0xffffffff found
[ 119.227542] hid-sensor-hub 0003:8086:0B3A.0003: No report with id 0xffffffff found
[ 119.227925] hid-sensor-hub 0003:8086:0B3A.0003: No report with id 0xffffffff found
[ 119.323565] hid-sensor-hub 0003:8086:0B3A.0003: No report with id 0xffffffff found
[ 122.333234] hid-sensor-hub 0003:8086:0B3A.0003: No report with id 0xffffffff found
[ 131.717974] nodelet[4038]: segfault at 1 ip 00007f84746844a1 sp 00007f843fffda80 error 6 in librostime.so[7f847466d000+2b000]
[ 137.668587] nodelet[4020]: segfault at 1 ip 00007fbe2436a4a1 sp 00007fbdefffda80 error 6 in librostime.so[7fbe24353000+2b000]
my launch file:
The text was updated successfully, but these errors were encountered: