From: Moses <mo...@ne...> - 2010-08-14 19:47:53
|
I spoke too soon.. it crashed this morning with the following messages from motion, these were the last lines in the log file. Aug 14 10:48:26 video motion.3.2.12: [3] mcapture error in proc 2517: Aug 14 10:48:26 video motion.3.2.12: [3] Video device fatal error - Closing video device Aug 14 10:48:26 video motion.3.2.12: [3] Closing video device /dev/video0 Aug 14 10:48:26 video motion.3.2.12: [2] mcapture error in proc 2517: Aug 14 10:48:26 video motion.3.2.12: [2] Video device fatal error - Closing video device Aug 14 10:48:26 video motion.3.2.12: [2] Closing video device /dev/video6 Aug 14 10:48:30 video motion.3.2.12: [3] Retrying until successful connection with camera Aug 14 10:48:30 video motion.3.2.12: [3] Not a V4L2 device? Aug 14 10:48:30 video motion.3.2.12: [2] Retrying until successful connection with camera Aug 14 10:48:30 video motion.3.2.12: [2] Not a V4L2 device? Any clues? I'm not sure what process 2517 is, since the box crashed. On 8/11/2010 1:36 PM, Moses wrote: > Hello, > > Just an update, the box has been up for 15 days now! The last change I > made was to add "v4l2=0" to the bttv options in modprobe, motion > complained about not running V4L2, but its working just like before. > > I've been dealing with these crashes for a long time now, last stable > box I had was either FC5 or FC6, but needed to upgrade because of new > hardware/kernel drivers. Crashes seem to strike anywhere from 2-30 days > uptime, although its usually never over 10 days, so a 15 day uptime is > very good news. If it makes it passed 30 days I would consider it pretty > stable, as I think it made it to 30 days only one time before. > > I couldn't find much documentation on "v4l2=0", I'm assuming this turns > off V4L2 and just leaves the V4L1 commands. Hopefully this will fix my > crashes. I would appreciate any comments. > > Regards, > -Moses > > > On 7/26/2010 10:52 PM, Krzysztof Błaszkowski wrote: >> Hello Moses, >> >> On Mon, 2010-07-26 at 13:43 -0700, Moses wrote: >> >>> Hello, >>> >>> I've been struggling with my motion box for some time.. latest crashes >>> seem to always involve the following error (with differing /dev/video >>> devices), followed by a hard crash. Anyone have any idea as to where I >>> should look? May this be a known problem? >>> >>> Jul 26 09:25:45 video motion.3.2.12: [2] v4l2_next: VIDIOC_DQBUF: >>> Jul 26 09:25:45 video motion.3.2.12: [2] Video device fatal error - >>> Closing video device >>> Jul 26 09:25:45 video motion.3.2.12: [2] Closing video device /dev/video6 >>> >>> Sometimes motion will try to restart and I would get a few more seconds >>> of that in the logs, but most of the time this is the last entry. >>> >> This issue seems to be kernel related i think. Try to use different one. >> Sometimes older work better because regression happens all the time. >> >> There can be also bug in the driver for video device you use, e.g. it >> may not perform well under oom condition nor cpu(s) intensive load. >> >> all these are just guesses (but possible) >> >> Regards, >> >>> Regards, >>> -Moses >>> >>> >> > |