sync error in proc 9705: Input/output error

Question

I'm getting above error, unfortunately google did not come up with any reasonable answer to this error message. There isn't much documentation on motion errormessages though I cannot find out from where this error is coming from.

The video device works just fine, since XawTV is producing video feed no problem on /dev/video0 input0.

All the stuff here is installed for ubuntu repositories, thoe some of the packages might be outadted.

[0] Processing thread 0 - config file /etc/motion/motion.conf
[0] Motion running in setup mode.
[0] Thread device: /dev/video input 0
[1] Thread is from /etc/motion/motion.conf
[1] Waiting for threads to finish, pid: 9705
[1] Thread started
[1] motion-httpd/3.2.3 running, accepting connections
[1] motion-httpd: waiting for data on port TCP 8080
[1] sync error in proc 9705: Input/output error
[1] bind(): Address already in use
[1] Problem enabling stream server: Address already in use
[1] Started stream webcam server in port 8080
[1] Thread exiting
[1] Closing webcam listen socket
[1] Closing active webcam sockets: Bad file descriptor
[1] Threads finished
[1] Motion terminating

motion.conf :
daemon off
quiet on

videodevice /dev/video0
input 0

width 40
height 30

framerate 25
quality 85
auto_brightness off

brightness 0
contrast 0
saturation 0
hue 0

ffmpeg_cap_new off

ffmpeg_video_codec msmpeg4

target_dir /survilance_video

webcam_port 8080

webcam_localhost on

webcam_quality 50
webcam_maxrate 8

control_port 8080

control_localhost on

control_html_output on

; control_authentication username:password

lspci :
00:08.0 Multimedia controller: Philips Semiconductors SAA7130 Video Broadcast Decoder (rev 01)
        Subsystem: Avermedia Technologies Inc AVerMedia DVD EZMaker
        Flags: bus master, medium devsel, latency 32, IRQ 193
        Memory at f6000000 (32-bit, non-prefetchable) [size=1K]
        Capabilities: [40] Power Management version 1

ffmpeg -version
FFmpeg version SVN-rUNKNOWN, Copyright (c) 2000-2004 Fabrice Bellard
  configuration:  --enable-gpl --enable-pp --enable-pthreads --enable-vorbis --enable-libogg --enable-a52 --enable-dts --enable-libgsm --enable-dc1394 --disable-debug --enable-shared --prefix=/usr
  libavutil version: 0d.49.0.0
  libavcodec version: 0d.51.11.0
  libavformat version: 0d.50.5.0
  built on Sep 20 2006 00:26:15, gcc: 4.1.2 20060906 (prerelease) (Ubuntu 4.1.1-13ubuntu2)
ffmpeg      SVN-rUNKNOWN
libavutil   3211264
libavcodec  3345152
libavformat 3278080

Environment

Motion version:	3.2.3
ffmpeg version:	see above
Libraries:	ffmpeg
Server OS:	kubuntu 6.10 edgy, kernel 2.6.17-10-generic

-- PavelTaboracek - 15 Jan 2007

Answer

Yes that version of motion is quite old , latest formal release is 3.2.7. Anyway notice about motion message logs:

[1] motion-httpd: waiting for data on port TCP 8080
[1] sync error in proc 9705: Input/output error
[1] bind(): Address already in use
[1] Problem enabling stream server: Address already in use
[1] Started stream webcam server in port 8080
[1] Thread exiting
[1] Closing webcam listen socket
[1] Closing active webcam sockets: Bad file descriptor

You are using the same port por http web control control_port 8080 and webcam_port 8080 so that seems the problem, please fix that on your motion config file and reopen the support question if the problem still remains.

-- AngelCarpintero - 15 Jan 2007

Thanks for your quick reply, I've should have read the manual more deeply:(. However, the sync error message is still returned by motion as seen below :

[0] Processing thread 0 - config file /etc/motion/motion.conf
[0] Motion running in setup mode.
[0] Thread device: /dev/video0 input 0
[1] Thread is from /etc/motion/motion.conf
[1] Waiting for threads to finish, pid: 4663
[1] Thread started
[1] motion-httpd/3.2.3 running, accepting connections
[1] motion-httpd: waiting for data on port TCP 8081
[1] sync error in proc 4663: Input/output error
[1] Started stream webcam server in port 8080
[1] sync error in proc 4663: Input/output error
[1] Changes:     0 - noise level: 25
[1] sync error in proc 4663: Input/output error
[1] Changes:     0 - noise level: 25
[1] sync error in proc 4663: Input/output error
[1] Changes:     0 - noise level: 22
[1] sync error in proc 4663: Input/output error
[1] Changes:     0 - noise level: 22
[1] sync error in proc 4663: Input/output error
[1] Changes:     0 - noise level: 20
[1] sync error in proc 4663: Input/output error
[1] Changes:     0 - noise level: 20
[1] sync error in proc 4663: Input/output error
[1] Changes:     0 - noise level: 19
[1] sync error in proc 4663: Input/output error
[1] Changes:     0 - noise level: 19
[1] sync error in proc 4663: Input/output error
[1] Motion detected - starting event 1
[1] File of type 1 saved to: /survilance_video/01-20070115154045-00.jpg
[1] Changes:  4193 - noise level: 19
[1] sync error in proc 4663: Input/output error
[1] File of type 1 saved to: /survilance_video/01-20070115154045-01.jpg
[1] Changes:  4371 - noise level: 19
[1] sync error in proc 4663: Input/output error
[1] File of type 1 saved to: /survilance_video/01-20070115154046-00.jpg
[1] Changes:  4361 - noise level: 19
[1] sync error in proc 4663: Input/output error
[1] [0] Processing thread 0 - config file /etc/motion/motion.conf
[0] Motion running in setup mode.
[0] Thread device: /dev/video0 input 0
[1] Thread is from /etc/motion/motion.conf
[1] Waiting for threads to finish, pid: 4663
[1] Thread started
[1] motion-httpd/3.2.3 running, accepting connections
[1] motion-httpd: waiting for data on port TCP 8081
[1] sync error in proc 4663: Input/output error
[1] Started stream webcam server in port 8080
[1] sync error in proc 4663: Input/output error
[1] Changes:     0 - noise level: 25
[1] sync error in proc 4663: Input/output error
[1] Changes:     0 - noise level: 25
[1] sync error in proc 4663: Input/output error
[1] Changes:     0 - noise level: 22
[1] sync error in proc 4663: Input/output error
[1] Changes:     0 - noise level: 22
[1] sync error in proc 4663: Input/output error
[1] Changes:     0 - noise level: 20
[1] sync error in proc 4663: Input/output error
[1] Changes:     0 - noise level: 20
[1] sync error in proc 4663: Input/output error
[1] Changes:     0 - noise level: 19
[1] sync error in proc 4663: Input/output error
[1] Changes:     0 - noise level: 19
[1] sync error in proc 4663: Input/output error
[1] Motion detected - starting event 1
[1] File of type 1 saved to: /survilance_video/01-20070115154045-00.jpg
[1] Changes:  4193 - noise level: 19
[1] sync error in proc 4663: Input/output error
[1] File of type 1 saved to: /survilance_video/01-20070115154045-01.jpg
[1] Changes:  4371 - noise level: 19
[1] sync error in proc 4663: Input/output error
[1] File of type 1 saved to: /survilance_video/01-20070115154046-00.jpg
[1] Changes:  4361 - noise level: 19
[1] sync error in proc 4663: Input/output error
[1] File of type 1 saved to: /survilance_video/01-20070115154046-01.jpg
File of type 1 saved to: /survilance_video/01-20070115154046-01.jpg

Anyway, motion produces a video output (on the webcam webserver) which is black and white and way too dark. The brightness and color of the output video is probably related to the motion video settings, but what for the sync error?

Thank you -- PavelTaboracek - 15 Jan 2007

Okay,

I'm the bad guy, it works just fine, the saved images are fine in color and so on. Only the webpage is producing B/W and too dark image. I'm going to look into this myself first than bugging you guys.

Anyway, thank you for your support.

-- PavelTaboracek - 15 Jan 2007

I've already answer you in the other support question about sync and the lack of setup_mode off in motion.conf that makes motion run in setup mode and show in webcam stream the debug mode.

-- AngelCarpintero - 16 Jan 2007

Please give me a link to the answered question "about sync and the lack of setup_mode off in motion.conf". I have same problem as AngelCarpintero "sync error in proc 4663: Input/output error"

-- DmitryBolshakoff - 24 Feb 2007

Usually the problem of sync problem is because a poor implementation of the kernel module, but for further information open a new support question with a detailed information about your problem . Please put your capture device , driver module version , kernel version and how did you load the module.

-- AngelCarpintero - 25 Feb 2007

Thank you for reply.
I do not think that new request needed. Short description of my problem - after ~5 minutes from Motion started, began "sync error in proc NNN: Input/output error" in console and "
kernel: bttv0: OCERR @ 07b73014,bits: VSYNC HSYNC OFLOW FBUS PPERR OCERR*
...several similar lines...
kernel: bttv0: timeout: drop=1 irq=48361/68518, risc=07b7301c, bits: VSYNC HSYNC OFLOW PPERR
kernel: bttv0: reset, reinitialize
"
in /var/log/messages
In one forum I found that closely same problem was solved with reinserting capture card in other pci slot, and it helped me too. So I just want to read generally about this problem. It seems hardware problem.
I can insert card back in "bad" slot and try to recreate error and post detailed config and messages if you have an interest

sorry for my poor english

-- DmitryBolshakoff - 26 Feb 2007

---

Yeah , that makes sense to me.

Sure i would like if your problem will be fixed just changing your capture card to another pci slot.

P.S: Your english is ok mine is poor too.

Thanks.

-- AngelCarpintero - 28 Feb 2007

---

I'm sorry for a delay. I cannot recreate error. I try all slots but it works and works! Most likely first time I just push it not enough.
That is the link where I found solution http://nkz.net.ru/forum/topic_show.pl?tid=3690

Rough translation is:
-I had old computer with FlyVideo capture card and bttv driver and motion installed
I bought new machine and had installed Slackware 11 2.6.18 and I cant make motion works
logs logs logs
-I do not like cascade irq 9 and 255. Although it is allowed if APIC but irq=0/0 adding suspicion that something wrong. I offer reset card in other slot
-Yes, and look at how pnp devices will change in second screen while the computer booting (plug off hdd and you can freeze it). And disable "pnp os" in bios
-I change slot and it help me! that is my new logs:
logs logs logs
it would be very nice if tuner works too

the rest is about tuner and my own question - copy of presented here

-- DmitryBolshakoff - 17 Mar 2007