klesk
Posts: 3
Joined: Tue Aug 08, 2017 7:16 am

[MOTION] Overexposure using YUV format

Tue Aug 08, 2017 7:57 am

Hello,

I have a brand new 8MP raspi v2.1 camera. I had good experience with these indoors using motion so I bought one for outdoors (it's built into a case).
I deal with over exposure, too bright images such as:

Image

https://publiclab.org/notes/jarrarte/08 ... ram-webcam

I am using:

ii motion 3.2.12+git20140228-4+b2 armhf V4L capture program supporting motion detection

With the following config:

Code: Select all

daemon on
process_id_file /home/pi/motion.pid
setup_mode off
logfile /home/pi/cam/log/motion.log
log_level 5
log_type all
v4l2_palette 17
input -1
norm 0
frequency 0
rotate 0
width 1280
height 720
framerate 30
minimum_frame_time 0
netcam_keepalive off
netcam_tolerant_check off
auto_brightness off
brightness 0
contrast 0
saturation 0
hue 0
roundrobin_frames 1
roundrobin_skip 1
switchfilter off
threshold 1500
threshold_tune off
noise_level 32
noise_tune on
despeckle_filter EedDl
smart_mask_speed 0
lightswitch 0
minimum_motion_frames 1
pre_capture 0
post_capture 0
event_gap 60
max_movie_time 0
emulate_motion off
output_pictures off
output_debug_pictures off
quality 75
picture_type jpeg
ffmpeg_output_movies off
ffmpeg_output_debug_movies off
ffmpeg_timelapse 0
ffmpeg_timelapse_mode daily
ffmpeg_bps 500000
ffmpeg_variable_bitrate 0
ffmpeg_video_codec mpeg4
use_extpipe off
snapshot_interval 0
locate_motion_mode off
locate_motion_style box
text_right %Y-%m-%d\n%T-%q
text_changes off
text_event %Y%m%d%H%M%S
text_double on
snapshot_filename %v-%Y%m%d%H%M%S-snapshot
picture_filename %v-%Y%m%d%H%M%S-%q
movie_filename %v-%Y%m%d%H%M%S
timelapse_filename %Y%m%d-timelapse
ipv6_enabled off
stream_port 8081
stream_quality 50
stream_motion off
stream_maxrate 100
stream_localhost off
stream_limit 0
stream_auth_method 1
stream_authentication admin:hold
webcontrol_port 8082
webcontrol_localhost on
webcontrol_html_output on
track_type 0
track_auto off
track_iomojo_id 0
track_step_angle_x 10
track_step_angle_y 10
track_move_wait 10
track_speed 255
track_stepsize 40
quiet on
Now as you see here the v4l2palette set to 17:

Code: Select all

# Values :
# V4L2_PIX_FMT_SN9C10X : 0  'S910'
# V4L2_PIX_FMT_SBGGR16 : 1  'BYR2'
# V4L2_PIX_FMT_SBGGR8  : 2  'BA81'
# V4L2_PIX_FMT_SPCA561 : 3  'S561'
# V4L2_PIX_FMT_SGBRG8  : 4  'GBRG'
# V4L2_PIX_FMT_SGRBG8  : 5  'GRBG'
# V4L2_PIX_FMT_PAC207  : 6  'P207'
# V4L2_PIX_FMT_PJPG    : 7  'PJPG'
# V4L2_PIX_FMT_MJPEG   : 8  'MJPEG'
# V4L2_PIX_FMT_JPEG    : 9  'JPEG'
# V4L2_PIX_FMT_RGB24   : 10 'RGB3'
# V4L2_PIX_FMT_SPCA501 : 11 'S501'
# V4L2_PIX_FMT_SPCA505 : 12 'S505'
# V4L2_PIX_FMT_SPCA508 : 13 'S508'
# V4L2_PIX_FMT_UYVY    : 14 'UYVY'
# V4L2_PIX_FMT_YUYV    : 15 'YUYV'
# V4L2_PIX_FMT_YUV422P : 16 '422P'
# V4L2_PIX_FMT_YUV420  : 17 'YU12'
and this 17 is not good for outside, causing the over exposure. I have tried all variations here like auto brightness on, off, setting values. The worst part is that fiddling around with the camera can get it screwed up until next reboot (eg no picture, gray picture, failed to open video device).

I have found the value 8

# V4L2_PIX_FMT_MJPEG : 8 'MJPEG'

working however with this mode over couple of hours period the cam gonna crash with error, I can't copy right now because it's down and will not respond until complete reboot again.

Pls help

nanonite
Posts: 9
Joined: Tue Jul 10, 2018 8:45 am

Re: [MOTION] Overexposure using YUV format

Tue Jul 10, 2018 8:51 am

Image

I bumping this up, I can't believe nobody cares about this overexposure issue?!

Especially on the summer. I using the 8MP regular camera module outdoor as well.

During winter/cloudy days the camera is ok but in the summer this is about what I get as picture.

This is completely unusable...

jamesh
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 20059
Joined: Sat Jul 30, 2011 7:41 pm

Re: [MOTION] Overexposure using YUV format

Tue Jul 10, 2018 9:27 am

Since its been brought up by a total of two people that almost always means its a setup issue. Or in a tiny number of cases a HW problem. Not a general problem that everyone is seeing, otherwise we would be inundated by complaints.

So what software are you using to take the pictures? And what parameters in that software?
Principal Software Engineer at Raspberry Pi (Trading) Ltd.
Please direct all questions to the forum, I do not do support via PM.

nanonite
Posts: 9
Joined: Tue Jul 10, 2018 8:45 am

Re: [MOTION] Overexposure using YUV format

Wed Jul 18, 2018 7:41 am

This is a software issue, not a hardware.

I experience the same thing with:

motion Version 4.0, Copyright 2000-2016 Jeroen Vreeken/Folkert van Heusden/Kenneth Lavrsen/Motion-Project maintainers


motion Version 4.1.1+git20180626-43b9c2b, Copyright 2000-2017 Jeroen Vreeken/Folkert van Heusden/Kenneth Lavrsen/Motion-Project maintainers


if using : V4L2_PIX_FMT_MJPEG : 8 'MJPEG' the screen is ok but then after random amount of time the camera goes nutcase:

Code: Select all

[48478.545577] bcm2835_v4l2: error 0 waiting for sync completion
[48478.547232] bcm2835-v4l2: vidioc_s_fmt_vid_cap device busy
[48478.549046] bcm2835-v4l2: vidioc_s_fmt_vid_cap device busy
[48485.465610] bcm2835_v4l2: error 0 waiting for sync completion
[48485.467288] bcm2835-v4l2: vidioc_s_fmt_vid_cap device busy
[48485.469138] bcm2835-v4l2: vidioc_s_fmt_vid_cap device busy
[48488.545593] bcm2835_v4l2: error 0 waiting for sync completion
[48488.547292] bcm2835-v4l2: vidioc_s_fmt_vid_cap device busy
[48488.549104] bcm2835-v4l2: vidioc_s_fmt_vid_cap device busy
[48495.465585] bcm2835_v4l2: error 0 waiting for sync completion
[48495.467280] bcm2835-v4l2: vidioc_s_fmt_vid_cap device busy
[48495.469125] bcm2835-v4l2: vidioc_s_fmt_vid_cap device busy
[48498.545575] bcm2835_v4l2: error 0 waiting for sync completion
[48498.547223] bcm2835-v4l2: vidioc_s_fmt_vid_cap device busy
[48498.549058] bcm2835-v4l2: vidioc_s_fmt_vid_cap device busy
[48505.465593] bcm2835_v4l2: error 0 waiting for sync completion
[48505.467278] bcm2835-v4l2: vidioc_s_fmt_vid_cap device busy
[48505.469087] bcm2835-v4l2: vidioc_s_fmt_vid_cap device busy
[48508.555584] bcm2835_v4l2: error 0 waiting for sync completion
[48508.557270] bcm2835-v4l2: vidioc_s_fmt_vid_cap device busy
[48508.559120] bcm2835-v4l2: vidioc_s_fmt_vid_cap device busy
[48515.485587] bcm2835_v4l2: error 0 waiting for sync completion
[48515.487250] bcm2835-v4l2: vidioc_s_fmt_vid_cap device busy
[48515.489117] bcm2835-v4l2: vidioc_s_fmt_vid_cap device busy
[48518.555614] bcm2835_v4l2: error 0 waiting for sync completion
[48518.557307] bcm2835-v4l2: vidioc_s_fmt_vid_cap device busy
[48518.559125] bcm2835-v4l2: vidioc_s_fmt_vid_cap device busy
[48525.475654] bcm2835_v4l2: error 0 waiting for sync completion
[48525.477332] bcm2835-v4l2: vidioc_s_fmt_vid_cap device busy
[48525.479261] bcm2835-v4l2: vidioc_s_fmt_vid_cap device busy
[48528.555611] bcm2835_v4l2: error 0 waiting for sync completion
[48528.557310] bcm2835-v4l2: vidioc_s_fmt_vid_cap device busy
[48528.559154] bcm2835-v4l2: vidioc_s_fmt_vid_cap device busy
[48535.475614] bcm2835_v4l2: error 0 waiting for sync completion
[48535.477312] bcm2835-v4l2: vidioc_s_fmt_vid_cap device busy
[48535.479154] bcm2835-v4l2: vidioc_s_fmt_vid_cap device busy
[48538.555604] bcm2835_v4l2: error 0 waiting for sync completion
[48538.557288] bcm2835-v4l2: vidioc_s_fmt_vid_cap device busy
[48538.559115] bcm2835-v4l2: vidioc_s_fmt_vid_cap device busy
[48545.475569] bcm2835_v4l2: error 0 waiting for sync completion
[48545.477258] bcm2835-v4l2: vidioc_s_fmt_vid_cap device busy
[48545.479081] bcm2835-v4l2: vidioc_s_fmt_vid_cap device busy
[48548.555576] bcm2835_v4l2: error 0 waiting for sync completion
[48548.557255] bcm2835-v4l2: vidioc_s_fmt_vid_cap device busy
[48548.559072] bcm2835-v4l2: vidioc_s_fmt_vid_cap device busy
[48555.475579] bcm2835_v4l2: error 0 waiting for sync completion
[48555.477249] bcm2835-v4l2: vidioc_s_fmt_vid_cap device busy
[48555.479054] bcm2835-v4l2: vidioc_s_fmt_vid_cap device busy
[48558.555634] bcm2835_v4l2: error 0 waiting for sync completion
[48558.557312] bcm2835-v4l2: vidioc_s_fmt_vid_cap device busy
[48558.559110] bcm2835-v4l2: vidioc_s_fmt_vid_cap device busy
[48565.475602] bcm2835_v4l2: error 0 waiting for sync completion
[48565.477262] bcm2835-v4l2: vidioc_s_fmt_vid_cap device busy
[48565.479071] bcm2835-v4l2: vidioc_s_fmt_vid_cap device busy
[48568.555588] bcm2835_v4l2: error 0 waiting for sync completion
[48568.557264] bcm2835-v4l2: vidioc_s_fmt_vid_cap device busy
[48568.559061] bcm2835-v4l2: vidioc_s_fmt_vid_cap device busy
[48575.475650] bcm2835_v4l2: error 0 waiting for sync completion
[48575.477319] bcm2835-v4l2: vidioc_s_fmt_vid_cap device busy
[48575.479156] bcm2835-v4l2: vidioc_s_fmt_vid_cap device busy
At this state the system goes into a broken state where you cant restart the cam daemon because it will just do this, you cant restart the pi because the init scripts would just hang forever and needs to be hardreset with:

Code: Select all

echo 1 > /proc/sys/kernel/sysrq
echo b > /proc/sysrq-trigger

It does not do this using the YUV (does not crash at all thats why I dont think its a hardware issue):

# V4L2_PIX_FMT_YUV420 : 17 'YU12'

but then the screen is just a white platter on the summer.

BlueWolf
Posts: 27
Joined: Fri Aug 25, 2017 8:59 pm

Re: [MOTION] Overexposure using YUV format

Wed Jul 18, 2018 10:59 am

I have no experience with Motion on the Raspberry but it sounds like a motion problem? I have the same camera outdoor for about a year and have had no problems with it (using both RPi Cam Control and raw raspivid).
Right now it is super sunny and this is the view: https://i.imgur.com/kPaLAhR.jpg. The white van is a tad bit over exposed but with the bright sun right behind us, that thing really is bright right now.

Have you tried it with anything else but Motion? Just do something like

Code: Select all

raspistill -o image.jpg
on the device and review the image.
If it errors with something like 'camera component couldn't be enabled' then Motion is still using it, make sure Motion is turned off.

6by9
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5352
Joined: Wed Dec 04, 2013 11:27 am
Location: ZZ9 Plural Z Alpha, aka just outside Cambridge.

Re: [MOTION] Overexposure using YUV format

Wed Jul 18, 2018 11:29 am

What kernel and firmware versions are you running?

Code: Select all

vcgencmd version
uname -a
I haven't seen lockups from MJPEG since some fixes went in Novermber 2017.

Assuming you've got the desktop Raspbian installed, then test with qv4l2 in YU12 and your desired resoution. Two niggles with qv4l2.
First qv4l2 has regressed and doesn't allow setting the resolution. Use "v4l2-ctl -v width=1280,height=720,pixelformat=YU12" before running qv4l2 to set the resolution.
Secondly if the option is present, then disable OpenGL from the menus before streaming as it doesn't work (it doesn't appear to be present as an option in the version from the Raspbian repos, but is with built from source).

The one thing that may be causing problems is that the GPU has a concept of video modes and stills modes, whereas V4L2 doesn't. Stills mode doesn't let AE run which may explain your problem. Stills mode is used for YU12 over 1280x720.
When loading the V4L2 driver, use "sudo modprobe bcm2835_v4l2 max_video_width=1920 max_video_height=1088" to request video mode up to 1080P.

Motion is not an application that we support. Do you have issues capturing images using raspistill? The JPEGs that raspistill produces have some debug data in that we can use to analyse problems.
Software Engineer at Raspberry Pi Trading. Views expressed are still personal views.
Please don't send PMs asking for support - use the forum.
I'm not interested in doing contracts for bespoke functionality - please don't ask.

nanonite
Posts: 9
Joined: Tue Jul 10, 2018 8:45 am

Re: [MOTION] Overexposure using YUV format

Thu Jul 19, 2018 10:27 am

It is kali linux with kernel: Kernel: armv7l Linux 4.4.50-v7
apt-file search vcgencmd returns nothing.

I will try the module options and if it crashes again, I will dist-upgrade it to the latest.

6by9
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5352
Joined: Wed Dec 04, 2013 11:27 am
Location: ZZ9 Plural Z Alpha, aka just outside Cambridge.

Re: [MOTION] Overexposure using YUV format

Thu Jul 19, 2018 10:59 am

4.4.50 is pretty ancient - history implies Feb 2017. The currently supported kernel is 4.14.56.

vcgencmd is part of the userland repo.

Code: Select all

sudo apt install cmake git
git clone https://github.com/raspberrypi/userland.git
cd userland
./buildme
should build all the userland apps. It'll try installing the apps in /opt/vc/bin, but that may not exist or be in your path. Alternatively look in build/bin.

We have no involvement in supporting Kali Linux. If you can reproduce on the latest Raspbian image then we will generally investigate, but there are just too many permutations otherwise.
Software Engineer at Raspberry Pi Trading. Views expressed are still personal views.
Please don't send PMs asking for support - use the forum.
I'm not interested in doing contracts for bespoke functionality - please don't ask.

nanonite
Posts: 9
Joined: Tue Jul 10, 2018 8:45 am

Re: [MOTION] Overexposure using YUV format

Tue Jul 24, 2018 9:02 am

Sadly after spending a day upgrading, dist-upgrading, full upgrading my kali and firmware to the latest (which is btw based on even latest kernel than the current Raspbian Stretch):


Code: Select all

          ......''';lxO.                         OS: Kali Linux
.....''''..........,:ld;                         Kernel: armv7l Linux 4.14.56-v7+
           .';;;:::;,,.x,                        Uptime: 11h 51m
      ..'''.            0Xxoc:,.  ...            Packages: 1447
  ....                ,ONkc;,;cokOdc',.          Shell: 2669
 .                   OMo           ':ddo.        CPU: ARMv7 rev 5 (v7l) @ 4x 900MHz
                    dMc               :OO;       GPU: BCM2708
Using both the stock:

ii motion 4.1.1-1.1 armhf V4L capture program

And my latest compiled git version:

motion Version 4.1.1+git20180626-43b9c2b, Copyright 2000-2017 Jeroen Vreeken/Folkert van Heusden/Kenneth Lavrsen/Motion-Project maintainers

The error still comes out within a day:

Code: Select all

2018-07-22T21:12:37+02:00 outboxen kernel: [179121.726049] bcm2835_v4l2: error 0 waiting for sync completion
2018-07-22T21:12:37+02:00 outboxen kernel: [179121.727689] bcm2835-v4l2: vidioc_s_fmt_vid_cap device busy
2018-07-22T21:12:37+02:00 outboxen kernel: [179121.729542] bcm2835-v4l2: vidioc_s_fmt_vid_cap device busy
2018-07-22T21:12:43+02:00 outboxen kernel: [179127.746081] bcm2835_v4l2: error 0 waiting for sync completion
2018-07-22T21:12:43+02:00 outboxen kernel: [179127.747745] bcm2835-v4l2: vidioc_s_fmt_vid_cap device busy
2018-07-22T21:12:43+02:00 outboxen kernel: [179127.749569] bcm2835-v4l2: vidioc_s_fmt_vid_cap device busy
2018-07-22T21:12:47+02:00 outboxen kernel: [179131.736078] bcm2835_v4l2: error 0 waiting for sync completion
2018-07-22T21:12:47+02:00 outboxen kernel: [179131.737791] bcm2835-v4l2: vidioc_s_fmt_vid_cap device busy
2018-07-22T21:12:47+02:00 outboxen kernel: [179131.739650] bcm2835-v4l2: vidioc_s_fmt_vid_cap device busy
2018-07-22T21:12:53+02:00 outboxen kernel: [179137.716057] bcm2835_v4l2: error 0 waiting for sync completion
2018-07-22T21:12:53+02:00 outboxen kernel: [179137.717702] bcm2835-v4l2: vidioc_s_fmt_vid_cap device busy
2018-07-22T21:12:53+02:00 outboxen kernel: [179137.719488] bcm2835-v4l2: vidioc_s_fmt_vid_cap device busy


Suggested module options are there

Code: Select all

# /etc/modules: kernel modules to load at boot time.
#
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored.
bcm2835-v4l2 max_video_width=1920 max_video_height=1088

Code: Select all


[    6.595226] bcm2835-v4l2: scene mode selected 0, was 0
[    6.595925] bcm2835-v4l2: V4L2 device registered as video0 - stills mode > 1920x1088
[    6.609017] bcm2835-v4l2: Broadcom 2835 MMAL video capture ver 0.0.2 loaded.

Code: Select all

Vgencmd after build crashes btw (I don't think it could help debugging anything any further).
/opt/vc/bin/vcgencmd: error while loading shared libraries: libvchiq_arm.so: cannot open shared object file: No such file or directory
I have switched it back to YUV and no issue again but white screen on the sun.
At this point I don't think that switching to Raspbian with an earlier kernel would help and I rather no to because the cam is on a difficult to access place.

It would take me many hours to take it off, disassemble it and replace the SDcard so I rather play around with software solutions before touching the hardware.

6by9
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5352
Joined: Wed Dec 04, 2013 11:27 am
Location: ZZ9 Plural Z Alpha, aka just outside Cambridge.

Re: [MOTION] Overexposure using YUV format

Tue Jul 24, 2018 9:30 am

Hackier way to get the build information

Code: Select all

sudo vcdbg dump vcos_build_version
sudo vcdbg dump vcos_build_date
sudo vcdbg dump vcos_build_time
Sorry, but without knowing roughly the firmware you're running there is almost no point in continuing to try and debug.

Have you tried using raspivid to capture the video at the point that motion is over exposed? Add "-set" to your command line and it will dump out the exposure time and gains being used.

Unless i've missed it you haven't stated what resolution you're using.
Software Engineer at Raspberry Pi Trading. Views expressed are still personal views.
Please don't send PMs asking for support - use the forum.
I'm not interested in doing contracts for bespoke functionality - please don't ask.

nanonite
Posts: 9
Joined: Tue Jul 10, 2018 8:45 am

Re: [MOTION] Overexposure using YUV format

Wed Jul 25, 2018 10:28 am

Hello,

Ok I made this tool work, just needed to add the libdir to ld.so.conf.


/opt/vc/bin/vcgencmd version
Jul 17 2018 13:28:45
Copyright (c) 2012 Broadcom
version 4da89b2ba95c8826c492b1d734296c8a1a2c7d2b (clean) (release)


It should be the latest since I also upgraded the firmware with:

https://github.com/Hexxeh/rpi-update


Here is my whole motion config:

Code: Select all

daemon on
process_id_file /home/cam/motion.pid
setup_mode off
logfile /home/cam/motion.log
log_level 5
log_type all
v4l2_palette 17
input -1
norm 0
frequency 0
rotate 90
width 720
height 1280
framerate 30
minimum_frame_time 0
netcam_keepalive off
netcam_tolerant_check off
auto_brightness off
brightness 70
contrast 0
saturation 0
hue 0
roundrobin_frames 1
roundrobin_skip 1
switchfilter off
threshold 1500
threshold_tune off
noise_level 32
noise_tune on
despeckle_filter EedDl
smart_mask_speed 0
lightswitch 0
minimum_motion_frames 1
pre_capture 0
post_capture 0
event_gap 60
max_movie_time 0
emulate_motion off
output_pictures off
output_debug_pictures off
quality 75
picture_type jpeg
ffmpeg_output_movies off
ffmpeg_output_debug_movies off
ffmpeg_timelapse 0
ffmpeg_timelapse_mode daily
ffmpeg_bps 500000
ffmpeg_variable_bitrate 0
ffmpeg_video_codec mpeg4
use_extpipe off
snapshot_interval 0
locate_motion_mode off
locate_motion_style box
text_right %Y-%m-%d\n%T-%q
text_changes off
text_event %Y%m%d%H%M%S
text_double on
snapshot_filename %v-%Y%m%d%H%M%S-snapshot
picture_filename %v-%Y%m%d%H%M%S-%q
movie_filename %v-%Y%m%d%H%M%S
timelapse_filename %Y%m%d-timelapse
ipv6_enabled off
stream_port 8081
stream_quality 50
stream_motion off
stream_maxrate 100
stream_localhost off
stream_limit 0
stream_auth_method 1
stream_authentication admin:admin
webcontrol_port 8082
webcontrol_localhost on
webcontrol_html_output on
track_type 0
track_auto off
track_iomojo_id 0
track_step_angle_x 10
track_step_angle_y 10
track_move_wait 10
track_speed 255
track_stepsize 40
quiet on

6by9
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5352
Joined: Wed Dec 04, 2013 11:27 am
Location: ZZ9 Plural Z Alpha, aka just outside Cambridge.

Re: [MOTION] Overexposure using YUV format

Wed Jul 25, 2018 5:10 pm

Hang on, what's

Code: Select all

brightness 70
doing in your config?
You're telling it to crank the brightness up (actually via digital processing), and then complaining about the image being badly exposed?
Default brightness is 50.

Checking with "raspistill -br 70" and I'll agree the images look overexposed. (Curious that that setting apparently doesn't affect your MJPEG stream).
Software Engineer at Raspberry Pi Trading. Views expressed are still personal views.
Please don't send PMs asking for support - use the forum.
I'm not interested in doing contracts for bespoke functionality - please don't ask.

nanonite
Posts: 9
Joined: Tue Jul 10, 2018 8:45 am

Re: [MOTION] Overexposure using YUV format

Fri Jul 27, 2018 8:22 am

Hello,

Thanks for all your help. I will give up with this device since I want to build a new 360 degree camera instead of it later this year.
In my case it is probably a conjunction of hardware+software issues then.

The brightness 60 was just left in there when I used MJPEG, even if I have it on 0 with YUV its the same white screen on sun effect.

BTW that auto_brightness feature in MJPEG mode is terrible, it cannot properly adjust the brightness and it will also cause external programs like ispy to keep turning on the recording.

I will leave this here for closure for others who might run into the same issue:

Code: Select all

[ 1500.711300] bcm2835_v4l2: module is from the staging directory, the quality is unknown, you have been warned.
[ 1501.341414] bcm2835-v4l2: scene mode selected 0, was 0
[ 1501.341873] bcm2835-v4l2: V4L2 device registered as video0 - stills mode > 1280x720
[ 1501.347378] bcm2835-v4l2: Broadcom 2835 MMAL video capture ver 0.0.2 loaded.
[ 1503.506074] bcm2835-v4l2: Failed to enable encode tunnel - error -2
[ 1503.506247] ------------[ cut here ]------------
[ 1503.506392] WARNING: CPU: 0 PID: 2049 at drivers/media/v4l2-core/videobuf2-core.c:1344 vb2_start_streaming+0xe4/0x160 [videobuf2_core]
[ 1503.506639] Modules linked in: bcm2835_v4l2(C) v4l2_common videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core videodev media binfmt_misc ipv6 ev                                 dev ir_lirc_codec lirc_dev r820t rtl2832 i2c_mux dvb_usb_rtl28xxu dvb_usb_v2 dvb_core uio_pdrv_genirq uio fixed
[ 1503.507213] CPU: 0 PID: 2049 Comm: ml1 Tainted: G         C      4.14.56-v7+ #1128
[ 1503.510015] Hardware name: BCM2835
[ 1503.512744] [<8010ffd8>] (unwind_backtrace) from [<8010c240>] (show_stack+0x20/0x24)
[ 1503.518297] [<8010c240>] (show_stack) from [<80786aa4>] (dump_stack+0xd4/0x118)
[ 1503.521149] [<80786aa4>] (dump_stack) from [<8011da6c>] (__warn+0xf8/0x110)
[ 1503.523969] [<8011da6c>] (__warn) from [<8011db54>] (warn_slowpath_null+0x30/0x38)
[ 1503.529695] [<8011db54>] (warn_slowpath_null) from [<7f22d5f0>] (vb2_start_streaming+0xe4/0x160 [videobuf2_core])
[ 1503.535638] [<7f22d5f0>] (vb2_start_streaming [videobuf2_core]) from [<7f22ebb0>] (vb2_core_streamon+0x130/0x178 [videobuf2_core])
[ 1503.541769] [<7f22ebb0>] (vb2_core_streamon [videobuf2_core]) from [<7f23d1dc>] (vb2_streamon+0x40/0x60 [videobuf2_v4l2])
[ 1503.547916] [<7f23d1dc>] (vb2_streamon [videobuf2_v4l2]) from [<7f23d24c>] (vb2_ioctl_streamon+0x50/0x54 [videobuf2_v4l2])
[ 1503.554209] [<7f23d24c>] (vb2_ioctl_streamon [videobuf2_v4l2]) from [<7f1ede40>] (v4l_streamon+0x28/0x2c [videodev])
[ 1503.560603] [<7f1ede40>] (v4l_streamon [videodev]) from [<7f1f0974>] (__video_do_ioctl+0x2a0/0x314 [videodev])
[ 1503.567032] [<7f1f0974>] (__video_do_ioctl [videodev]) from [<7f1f0318>] (video_usercopy+0x224/0x5bc [videodev])
[ 1503.573465] [<7f1f0318>] (video_usercopy [videodev]) from [<7f1f06d0>] (video_ioctl2+0x20/0x24 [videodev])
[ 1503.579892] [<7f1f06d0>] (video_ioctl2 [videodev]) from [<7f1ec720>] (v4l2_ioctl+0xd4/0xe8 [videodev])
[ 1503.586333] [<7f1ec720>] (v4l2_ioctl [videodev]) from [<8029e180>] (do_vfs_ioctl+0xac/0x7c4)
[ 1503.592858] [<8029e180>] (do_vfs_ioctl) from [<8029e8dc>] (SyS_ioctl+0x44/0x6c)
[ 1503.596190] [<8029e8dc>] (SyS_ioctl) from [<80108060>] (ret_fast_syscall+0x0/0x28)
[ 1503.602892] ---[ end trace 885126ddcd77afdf ]---
This is that the camera board went into another crazy state where you cannot even load the module anymore after restarting the pi multiple times (I tried normal shutdowns and hard resets). At this stage the hardware most likely needs to be power cycled but as I say I give up with this setup.

Return to “Camera board”

Who is online

Users browsing this forum: No registered users and 8 guests