Send Motion-user mailing list submissions to
motion-user@lists.sourceforge.net
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/motion-user
or, via email, send a message with subject or body 'help' to
motion-user-requ...@lists.sourceforge.net
You can reach the person managing the list at
motion-user-ow...@lists.sourceforge.net
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Motion-user digest..."
Today's Topics:
1. Re: motion 4.3.1&4.3.2 both crash after a variable amount of
time on obsd 6.8 armv7 arch with 'bus error' (Roger Heflin)
2. Re: motion 4.3.1&4.3.2 both crash after a variable amount of
time on obsd 6.8 armv7 arch with 'bus error' (tosiara)
3. Re: motion crashing or stops working (S Andreason)
----------------------------------------------------------------------
Message: 1
Date: Sat, 6 Feb 2021 07:53:01 -0600
From: Roger Heflin <roger.hef...@gmail.com>
To: Motion discussion list <motion-user@lists.sourceforge.net>
Subject: Re: [Motion-user] motion 4.3.1&4.3.2 both crash after a
variable amount of time on obsd 6.8 armv7 arch with 'bus error'
Message-ID:
<CAAMCDefCQMJAiJnnoH+G2mYohX+wddHL+-mue0+Ypj_=j-g...@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
bus errors are usually errors where something is trying to access
something out of alignment. That would likely make this a compiler
issue of some sort where the compiler is not flagging the variable not
being aligned, or it is giving a warning and it is being ignored. The
compiler can be told to layout variables and structures such that they
are align, but certain options/directives call tell the compiler to
not handle alignment. The standard intel32/64 bit arch'es are very
tolerant of out of alignment (the cpu will often handle it, at the
expense of more cpu cycles) than the other arches. So if you say have
a double (8-byte) those may be required to be on a 8byte address
boundary, if you attempt to access it on a 4byte alignment the
processer has to deal with it or it gives a bus error. I think some
of the motion code did use "packet" and that may not work well if the
arch has alignment requirements.
On Sat, Feb 6, 2021 at 5:29 AM Damo Gets <damo.g...@gmail.com> wrote:
>
> Hello.
>
> I've recently switched from using Debian (well, 'armbian', actually) on
> a Cubieboard2 to OpenBSD 6.8. One of the primary functions of this
> machine is to keep tabs on at least one webcam with 'motion'.
> Unfortunately, since switching to the armv7 arch build of OBSD6.8, I've
> not been able to keep motion running for more than just a few minutes.
> It always ends up crashing with a 'bus error' and a core dump.
>
> I wasn't sure at this point if I should be posting this as a bug
> somewhere, or if I need to rule out that it isn't an obsd porting issue,
> or maybe even a hardware fault on my used cubie2 that, for some reason,
> didn't show when I was running motion on armbian previously. So I
> figured that I would check here, first.
>
> Anyway, here is the output that I last got from my crashed 'motion'
> process (this output was from 4.3.2):
>
> -
> borgi$ sudo motion
> [0:Unknown] [NTC] [ALL] conf_load: Processing thread 0 - config file
> /usr/local/etc/motion/motion.conf
> [0:Unknown] [NTC] [ALL] motion_startup: Logging to syslog
> [0:Unknown] [NTC] [ALL] motion_startup: Motion 4.3.2 Started
> [0:Unknown] [NTC] [ALL] motion_startup: Using default log type (ALL)
> [0:Unknown] [NTC] [ALL] motion_startup: Using log type (ALL) log level
> (NTC)
> [0:Unknown] [NTC] [STR] webu_start_strm: Starting all camera streams on
> port 8081
> [0:Unknown] [NTC] [STR] webu_strm_ntc: Started camera 0 stream on port
> 8081
> [0:Unknown] [NTC] [STR] webu_start_ctrl: Starting webcontrol on port
> 8080
> [0:Unknown] [NTC] [STR] webu_start_ctrl: Started webcontrol on port 8080
> [0:Unknown] [NTC] [ENC] ffmpeg_global_init: ffmpeg libavcodec version
> 58.91.100 libavformat version 58.45.100
> [0:Unknown] [NTC] [ALL] translate_init: Language: English
> [0:Unknown] [NTC] [ALL] motion_start_thread: Camera ID: 0 is from
> /usr/local/etc/motion/motion.conf
> [0:Unknown] [NTC] [ALL] motion_start_thread: Camera ID: 0 Camera Name:
> (null) Device: /dev/video0
> [0:Unknown] [NTC] [ALL] main: Waiting for threads to finish, pid: 62756
> [1:Unknown] [NTC] [ALL] motion_init: Camera 0 started: motion detection
> Enabled
> [1:Unknown] [NTC] [VID] vid_start: Opening V4L2 device
> [1:Unknown] [NTC] [VID] v4l2_device_open: Using videodevice /dev/video0
> and input -1
> [1:Unknown] [NTC] [VID] v4l2_device_capability: - VIDEO_CAPTURE
> [1:Unknown] [NTC] [VID] v4l2_device_capability: - READWRITE
> [1:Unknown] [NTC] [VID] v4l2_device_capability: - STREAMING
> [1:Unknown] [NTC] [VID] v4l2_input_select: Name = "Camera Terminal"-
> CAMERA
> [1:Unknown] [NTC] [VID] v4l2_norm_select: Device does not support
> specifying PAL/NTSC norm
> [1:Unknown] [NTC] [VID] v4l2_pixfmt_select: Configuration palette index
> 17 (YU12) for 320x240 doesn't work.
> [1:Unknown] [NTC] [VID] v4l2_pixfmt_select: Supported palettes:
> [1:Unknown] [NTC] [VID] v4l2_pixfmt_select: (0) YUYV (YUYV)
> [1:Unknown] [NTC] [VID] v4l2_pixfmt_select: (1) MJPG (MJPEG)
> [1:Unknown] [NTC] [VID] v4l2_pixfmt_set: Testing palette MJPG (320x240)
> [1:Unknown] [NTC] [VID] v4l2_pixfmt_set: Using palette MJPG (320x240)
> [1:Unknown] [NTC] [VID] v4l2_pixfmt_select: Selected palette MJPG
> [1:Unknown] [NTC] [ALL] image_ring_resize: Resizing pre_capture buffer
> to 1 items
> [1:Unknown] [NTC] [ALL] image_ring_resize: Resizing pre_capture buffer
> to 4 items
> Bus error (core dumped)
> borgi$
> -
>
> And, in case this is my fault through configuration error somehow, here
> are the non-commented lines in my motion.conf:
>
> -
> daemon off
> setup_mode off
> log_level 6
> videodevice /dev/video0
> width 320
> height 240
> framerate 5
> text_left crackstacks-entrance
> text_right %Y-%m-%d\n%T-%q
> emulate_motion off
> threshold 800
> despeckle_filter EedDl
> minimum_motion_frames 1
> event_gap 20
> pre_capture 3
> post_capture 2
> target_dir /var/motion
> picture_output off
> picture_filename %Y%m%d%H%M%S-%q
> movie_output on
> movie_max_time 300
> movie_quality 45
> movie_codec mkv
> movie_filename %t-%v-%Y%m%d%H%M%S
> webcontrol_port 8080
> webcontrol_localhost off
> webcontrol_parms 0
> stream_port 8081
> stream_localhost off
> -
>
> My thanks in advance to anybody that might be able to assist me in
> troubleshooting and getting to the bottom of this. Also, my thanks to
> the authors, as I've found motion an invaluable resource in the past
> and very much look forward to utilizing it in the future. Thanks for
> your time and assistance!
>
> --
>
> -D4m0
> _______________________________________________
> Motion-user mailing list
> Motion-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/motion-user
> https://motion-project.github.io/
>
> Unsubscribe: https://lists.sourceforge.net/lists/options/motion-user
------------------------------
Message: 2
Date: Sat, 6 Feb 2021 17:30:00 +0200
From: tosiara <tosi...@gmail.com>
To: Motion discussion list <motion-user@lists.sourceforge.net>
Subject: Re: [Motion-user] motion 4.3.1&4.3.2 both crash after a
variable amount of time on obsd 6.8 armv7 arch with 'bus error'
Message-ID:
<cachtdwtk9srv+ngp+l4vq5gdgfidtnnygigtbjinzk5nwvi...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Can you run motion from gdb and collect backtrace?
On Sat, Feb 6, 2021, 13:29 Damo Gets <damo.g...@gmail.com> wrote:
> Hello.
>
> I've recently switched from using Debian (well, 'armbian', actually) on
> a Cubieboard2 to OpenBSD 6.8. One of the primary functions of this
> machine is to keep tabs on at least one webcam with 'motion'.
> Unfortunately, since switching to the armv7 arch build of OBSD6.8, I've
> not been able to keep motion running for more than just a few minutes.
> It always ends up crashing with a 'bus error' and a core dump.
>
> I wasn't sure at this point if I should be posting this as a bug
> somewhere, or if I need to rule out that it isn't an obsd porting issue,
> or maybe even a hardware fault on my used cubie2 that, for some reason,
> didn't show when I was running motion on armbian previously. So I
> figured that I would check here, first.
>
> Anyway, here is the output that I last got from my crashed 'motion'
> process (this output was from 4.3.2):
>
> -
> borgi$ sudo motion
> [0:Unknown] [NTC] [ALL] conf_load: Processing thread 0 - config file
> /usr/local/etc/motion/motion.conf
> [0:Unknown] [NTC] [ALL] motion_startup: Logging to syslog
> [0:Unknown] [NTC] [ALL] motion_startup: Motion 4.3.2 Started
> [0:Unknown] [NTC] [ALL] motion_startup: Using default log type (ALL)
> [0:Unknown] [NTC] [ALL] motion_startup: Using log type (ALL) log level
> (NTC)
> [0:Unknown] [NTC] [STR] webu_start_strm: Starting all camera streams on
> port 8081
> [0:Unknown] [NTC] [STR] webu_strm_ntc: Started camera 0 stream on port
> 8081
> [0:Unknown] [NTC] [STR] webu_start_ctrl: Starting webcontrol on port
> 8080
> [0:Unknown] [NTC] [STR] webu_start_ctrl: Started webcontrol on port 8080
> [0:Unknown] [NTC] [ENC] ffmpeg_global_init: ffmpeg libavcodec version
> 58.91.100 libavformat version 58.45.100
> [0:Unknown] [NTC] [ALL] translate_init: Language: English
> [0:Unknown] [NTC] [ALL] motion_start_thread: Camera ID: 0 is from
> /usr/local/etc/motion/motion.conf
> [0:Unknown] [NTC] [ALL] motion_start_thread: Camera ID: 0 Camera Name:
> (null) Device: /dev/video0
> [0:Unknown] [NTC] [ALL] main: Waiting for threads to finish, pid: 62756
> [1:Unknown] [NTC] [ALL] motion_init: Camera 0 started: motion detection
> Enabled
> [1:Unknown] [NTC] [VID] vid_start: Opening V4L2 device
> [1:Unknown] [NTC] [VID] v4l2_device_open: Using videodevice /dev/video0
> and input -1
> [1:Unknown] [NTC] [VID] v4l2_device_capability: - VIDEO_CAPTURE
> [1:Unknown] [NTC] [VID] v4l2_device_capability: - READWRITE
> [1:Unknown] [NTC] [VID] v4l2_device_capability: - STREAMING
> [1:Unknown] [NTC] [VID] v4l2_input_select: Name = "Camera Terminal"-
> CAMERA
> [1:Unknown] [NTC] [VID] v4l2_norm_select: Device does not support
> specifying PAL/NTSC norm
> [1:Unknown] [NTC] [VID] v4l2_pixfmt_select: Configuration palette index
> 17 (YU12) for 320x240 doesn't work.
> [1:Unknown] [NTC] [VID] v4l2_pixfmt_select: Supported palettes:
> [1:Unknown] [NTC] [VID] v4l2_pixfmt_select: (0) YUYV (YUYV)
> [1:Unknown] [NTC] [VID] v4l2_pixfmt_select: (1) MJPG (MJPEG)
> [1:Unknown] [NTC] [VID] v4l2_pixfmt_set: Testing palette MJPG (320x240)
> [1:Unknown] [NTC] [VID] v4l2_pixfmt_set: Using palette MJPG (320x240)
> [1:Unknown] [NTC] [VID] v4l2_pixfmt_select: Selected palette MJPG
> [1:Unknown] [NTC] [ALL] image_ring_resize: Resizing pre_capture buffer
> to 1 items
> [1:Unknown] [NTC] [ALL] image_ring_resize: Resizing pre_capture buffer
> to 4 items
> Bus error (core dumped)
> borgi$
> -
>
> And, in case this is my fault through configuration error somehow, here
> are the non-commented lines in my motion.conf:
>
> -
> daemon off
> setup_mode off
> log_level 6
> videodevice /dev/video0
> width 320
> height 240
> framerate 5
> text_left crackstacks-entrance
> text_right %Y-%m-%d\n%T-%q
> emulate_motion off
> threshold 800
> despeckle_filter EedDl
> minimum_motion_frames 1
> event_gap 20
> pre_capture 3
> post_capture 2
> target_dir /var/motion
> picture_output off
> picture_filename %Y%m%d%H%M%S-%q
> movie_output on
> movie_max_time 300
> movie_quality 45
> movie_codec mkv
> movie_filename %t-%v-%Y%m%d%H%M%S
> webcontrol_port 8080
> webcontrol_localhost off
> webcontrol_parms 0
> stream_port 8081
> stream_localhost off
> -
>
> My thanks in advance to anybody that might be able to assist me in
> troubleshooting and getting to the bottom of this. Also, my thanks to
> the authors, as I've found motion an invaluable resource in the past
> and very much look forward to utilizing it in the future. Thanks for
> your time and assistance!
>
> --
>
> -D4m0
> _______________________________________________
> Motion-user mailing list
> Motion-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/motion-user
> https://motion-project.github.io/
>
> Unsubscribe: https://lists.sourceforge.net/lists/options/motion-user
-------------- next part --------------
An HTML attachment was scrubbed...
------------------------------
Message: 3
Date: Sat, 6 Feb 2021 08:45:01 -0800
From: S Andreason <sandrea...@gmail.com>
To: Motion-user <motion-user@lists.sourceforge.net>
Subject: Re: [Motion-user] motion crashing or stops working
Message-ID: <2404bbb3-381b-3278-6bbb-b72207ca0...@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Hi,
I sent a gdb backtrace on Dec.25 but never heard any reply, so am
assuming it got lost. Here is a resend. I have also had it crash
yesterday right after startup, without changing the mask file etc. Just
a few screenshots and then disappeared.
Please reply with ideas for further testing or config file changes.
Thank you
S Andreason wrote:
> Hi,
> I reported I've been having motion crash (sometimes), without error
> messages, usually when performing a restart for a single camera after
> changing the mask_file setting. (I do this a lot.)
> I now have something substantial to help figure this out, after
> running motion directly (not as a service), I saw a Segmentation Fault
> message, this time at startup instead of the restart. So I started
> gdb, and here is the backtrace.
>
> $ sudo gdb motion
> GNU gdb (Raspbian 8.2.1-2) 8.2.1
> Copyright (C) 2018 Free Software Foundation, Inc.
> [clip]
> This GDB was configured as "arm-linux-gnueabihf".
> [clip]
> Reading symbols from motion...(no debugging symbols found)...done.
> (gdb) run
> Starting program: /usr/bin/motion
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library
> "/lib/arm-linux-gnueabihf/libthread_db.so.1".
> [0:motion] [NTC] [ALL] conf_load: Processing thread 0 - config file
> /etc/motion/motion.conf
> [0:motion] [NTC] [ALL] config_camera: Processing camera config file
> /etc/motion/camera206.conf
> [0:motion] [NTC] [ALL] config_camera: Processing camera config file
> /etc/motion/camera204.conf
> [0:motion] [NTC] [ALL] motion_startup: Logging to file
> (/var/log/motion/motion.log)
> [New Thread 0xadca0a90 (LWP 3992)]
> [New Thread 0xad2fea90 (LWP 3993)]
> [New Thread 0xac484a90 (LWP 3994)]
> [New Thread 0xabc83a90 (LWP 3995)]
> [New Thread 0xaac3aa90 (LWP 3999)]
> [New Thread 0xa9c3aa90 (LWP 4000)]
>
> Thread 7 "nc4:204_Alptop_" received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 0xa9c3aa90 (LWP 4000)]
> 0xb5919790 in ?? () from
> /usr/lib/arm-linux-gnueabihf/neon/vfp/libavcodec.so.58
> (gdb) bt
> #0? 0xb5919790 in ?? () from
> /usr/lib/arm-linux-gnueabihf/neon/vfp/libavcodec.so.58
> #1? 0xb590ef7c in ?? () from
> /usr/lib/arm-linux-gnueabihf/neon/vfp/libavcodec.so.58
> Backtrace stopped: previous frame identical to this frame (corrupt
> stack?)
>
>
> Stewart
------------------------------
------------------------------
Subject: Digest Footer
_______________________________________________
Motion-user mailing list
Motion-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/motion-user
------------------------------
End of Motion-user Digest, Vol 176, Issue 17
********************************************
