Motion - Support Question 2011x 08x 01x 135341

It looks like motion is running with interrupts off, ignoring the scheduler, or something even more wonky on OMAP3 (gumstix) system

Question

I've just installed linux 2.6.34, ffmpeg 31717 (libs as below) and motion v 8.0.2 and an MT9V032-based sensor. The system is a hacked-together 2.6.34 kernel running on an OMAP3503 motherboard manufactured by Gumstix. The watchdog thread times out, the ccdc driver can't be unloaded, and the system complains that motion is not responding.

I thought I had downloaded/installed motion 3.2.12 but "--version" says "8.0.2"

I think this problem is different than 2009x 07x 05x 075301

Thanks.

ffmpeg -version:
ffmpeg N-31717-g29d854d
libavutil    51. 11. 1 / 51. 11. 1
libavcodec   53.  9. 0 / 53.  9. 0
libavformat  53.  6. 0 / 53.  6. 0
libavdevice  53.  2. 0 / 53.  2. 0
libavfilter   2. 27. 5 /  2. 27. 5
libswscale    2.  0. 0 /  2.  0. 0

motion output
[0] [ALR] [ALL] conf_load: could not open configfile /usr/local/etc/motion.conf: 
[0] [CRT] [ALL] conf_load: Not config file to process using default values
[0] [NTC] [ALL] motion_startup: Using default log level (NTC) (6)
[0] [NTC] [ALL] motion_startup: Motion 8.0.2 Started
[0] [NTC] [ALL] motion_startup: Logging to syslog
[0] [NTC] [ALL] motion_startup: Using default log type (ALL)
[0] [NTC] [ALL] motion_startup: Using log type (ALL) log level (NTC)
[0] [NTC] [ALL] main: Thread 1 is device: /dev/video0 input -1
[0] [NTC] [ALL] main: Stream port 0
[0] [NTC] [ALL] main: Waiting for threads to finish, pid: 1305
[1] [NTC] [ALL] motion_init: Thread 1 started
[1] [NTC] [VID] vid_v4lx_start: Using videodevice /dev/video0 and input -1
[1] [NTC] [VID] v4l2_get_capability: 
------------------------
cap.driver: "omap3"
cap.card: "omap3/mt9v032//"
cap.bus_info: ""
cap.capabilities=0x04000001
------------------------
[1] [NTC] [VID] v4l2_get_capability: - VIDEO_CAPTURE
[1] [NTC] [VID] v4l2_get_capability: - STREAMING
[1] [NTC] [VID] v4l2_select_input: name = "camera", type 0x00000002, status 00000000
[1] [NTC] [VID] v4l2_select_input: - CAMERA
[1] [WRN] [VID] v4l2_select_input: Device doesn't support VIDIOC_G_STD
[1] [NTC] [VID] v4l2_set_pix_format: Config palette index 17 (YU12) doesn't work.
[1] [NTC] [VID] v4l2_set_pix_format: Supported palettes:
[1] [NTC] [VID] v4l2_set_pix_format: (0) UYVY (UYVY, packed)
[1] [NTC] [VID] v4l2_set_pix_format: 0 - UYVY, packed (compressed : 0) (0x59565955)
[1] [NTC] [VID] v4l2_set_pix_format: (1) YUYV (YUYV (YUV 4:2:2), packed)
[1] [NTC] [VID] v4l2_set_pix_format: 1 - YUYV (YUV 4:2:2), packed (compressed : 0) (0x56595559)
[1] [NTC] [VID] v4l2_set_pix_format: (2) BA10 (Bayer10 (GrR/BGb))
[1] [NTC] [VID] v4l2_set_pix_format: 2 - Bayer10 (GrR/BGb) (compressed : 0) (0x30314142)
[1] [NTC] [VID] v4l2_set_pix_format Selected palette YUYV
[1] [NTC] [VID] v4l2_do_set_pix_format: Testing palette YUYV (352x288)
[1] [NTC] [VID] v4l2_do_set_pix_format: Using palette YUYV (352x288) bytesperlines 704 sizeimage 204800 colorspace 00000007
[1] [NTC] [VID] v4l2_scan_controls: found control 0x00980900, "Brightness", range 0,255 
[1] [NTC] [VID] v4l2_scan_controls:    "Brightness", default 1, current 1
[1] [NTC] [VID] v4l2_scan_controls: found control 0x00980901, "Contrast", range 0,255 
[1] [NTC] [VID] v4l2_scan_controls:    "Contrast", default 16, current 16
[1] [NTC] [VID] v4l2_scan_controls: found control 0x00980911, "Exposure", range 2,480 
[1] [NTC] [VID] v4l2_scan_controls:    "Exposure", default 480, current 566
[1] [NTC] [VID] v4l2_scan_controls: found control 0x00980912, "Automatic Gain", range 0,1 
[1] [NTC] [VID] v4l2_scan_controls:    "Automatic Gain", default 1, current 1
[1] [NTC] [VID] v4l2_scan_controls: found control 0x00980913, "Analog Gain", range 16,64 
[1] [NTC] [VID] v4l2_scan_controls:    "Analog Gain", default 16, current 16
[1] [NTC] [VID] vid_v4lx_start: Using V4L2
[1] [NTC] [ALL] image_ring_resize: Resizing pre_capture buffer to 1 items
[0] [ERR] [ALL] main: Thread 1 - Watchdog timeout, trying to do a graceful restart
[0] [ERR] [ALL] main: Thread 1 - Watchdog timeout, did NOT restart graceful,killing it!
[0] [NTC] [VID] vid_close: Closing video device /dev/video0
omap3isp omap3isp: __isp_disable_modules: can't stop ccdc
BUG: soft lockup - CPU#0 stuck for 61s! [motion:1306]
Modules linked in: ipv6 libertas_sdio option libertas usbserial mt9v032 ads7846 lib80211

Pid: 1306, comm:               motion
CPU: 0    Not tainted  (2.6.34 #1)
PC is at v7_dma_inv_range+0x30/0x44
LR is at ___dma_page_dev_to_cpu+0x34/0x44
pc : [<c00fce40>]    lr : [<c00f9ec0>]    psr: 80000013
sp : cef29c08  ip : c06c6000  fp : cfe104e0
r10: cef29c3c  r9 : cef29c48  r8 : cfe10588
r7 : 00000032  r6 : 00000002  r5 : 0000000f  r4 : d09d20e0
r3 : 0000003f  r2 : 00000040  r1 : ce604000  r0 : ce603f80
Flags: Nzcv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment user
Control: 10c5387d  Table: 8ff24019  DAC: 00000015
BUG: soft lockup - CPU#0 stuck for 61s! [motion:1306]
Modules linked in: ipv6 libertas_sdio option libertas usbserial mt9v032 ads7846 lib80211
(repeats)

Environment

Motion version: 8.0.2
ffmpeg version: N-31717-g29d854d
Libraries: ffmpeg, mysql, postgresql
Server OS: Linux 2.6.34 (openembedded environment)
-- ThorFarrish - 01 Aug 2011

Answer

SupportForm edit

TopicTitle It looks like motion is running with interrupts off, ignoring the scheduler, or something even more wonky on OMAP3 (gumstix) system
SupportStatus AskedQuestions
AssignedQuestionTo
SubmittedBy ThorFarrish
Topic revision: r1 - 02 Aug 2011, ThorFarrish
Copyright © 1999-2017 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Please do not email Kenneth for support questions (read why). Use the Support Requests page or join the Mailing List.
This website only use harmless session cookies. See Cookie Policy for details. By using this website you accept the use of these cookies.