From: Angel C. <ac...@te...> - 2009-02-22 19:50:57
|
El dom, 22-02-2009 a las 18:45 +0000, dave selby escribió: > Hi All, Hi David , > I have discovered an issue with motion / kernel driver. On stopping > and restarting motion or sending motion a SIGHUP to reread its config > it occasionally > locks up and refuses to access a feed. I get the following : > [0] Processing thread 0 - config file > /home/dave/kmotion2/core/motion_conf/motion.conf > [0] Processing config file /home/dave/kmotion2/core/motion_conf/thread01.conf > [0] Motion 3.2.9 Started Better don't report bugs with old version of motion that probably are already fixed in stable or trunk. So better try with 3.2.11 > [0] ffmpeg LIBAVCODEC_BUILD 3352064 LIBAVFORMAT_BUILD 3344896 > [0] Thread 1 is from /home/dave/kmotion2/core/motion_conf/thread01.conf > [1] Thread 1 started > [1] cap.driver: "uvcvideo" > [1] cap.card: "UVC Camera (046d:08cc)" What version of uvcvideo / kernel version ? > [0] motion-httpd/3.2.9 running, accepting connections > [0] motion-httpd: waiting for data on port TCP 8080 > [0] Failed to reset camera to starting position! Reason: Inappropriate > ioctl for device > [0] httpd - Read from client: Inappropriate ioctl for device > [1] VIDIOC_TRY_FMT failed for format YUYV (Input/output error). > [0] Failed to reset camera to starting position! Reason: Inappropriate > ioctl for device > [0] httpd - Read from client: Inappropriate ioctl for device > [1] ioctl(VIDIOCGMBUF) - Error device does not support memory map > [1] V4L capturing using read is deprecated! > [1] Motion only supports mmap. This is probably an issue with uvcvideo driver or already fixed bug in motion. Cheers, -- Angel Carpintero ack ( at ) telefonica ( dot ) net Key fingerprint = 3FD3 9C90 149E 7824 CECD 6BCF AC2C CA61 6EF1 B90D "No basta saber, hay que aplicar lo que se sabe; no basta querer hacerlas cosas, hay que hacerlas". "Knowing is not enough; we must apply. Willing is not enough; we must do" Johann Wolfgang von Goethe |