Howto solve: VIDIOC_QBUF error 14, Bad address ?

[Michael Barz]

Hello,

Pretty often I get the error "VIDIOC_QBUF error 14, Bad address".
Sometimes it occurs directly after starting pupil, sometimes it occurs randomly during usage (but more seldom).
If the error occurs, the world window crashes and the eye window remains open.

However, this error does not occur, when using a video stream.

Currently I use version 3.7 (from source) on Ubuntu 13.10 GNOME.
Field-Camera: Logitech C930e
Eye-Camera: MS HD-6000
Cameras are connected to different USB-Bus.

It would be great, if you could help me with this problem.


Kind regards,
Michael

[Michael Barz]

Hi, actually I used Version 3.6.
I updated from google git, but got only V3.6.
Now I have Version 3.7.
I'll report if this solved the error.


Kind regards, Michael

PS: Maybe you change the git path in your wiki to github...

[Michael Barz]

Version 3.7 does not solve the problem.
The error still occurs...

[Moritz Kassner]

Hi,

This is an error with the v4l2 backend. It must be device or OS specific as I make burn in tests with pupil on Ubuntu 12.10 and a x201 thinkpad and never get this error.

Of course we need to fix this, but its hard to debug as I cannot recreate the error.

I will create a branch and ask you to try running it. Hopefully we can debug my fix attempts on your machine this way.

To get  started can you post the full error message?

Moritz

On Jan 23, 2014 3:21 PM, "Michael Barz" <micb...@googlemail.com> wrote:

Version 3.7 does not solve the problem.
The error still occurs...

--
You received this message because you are subscribed to the Google Groups "pupil-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pupil-discus...@googlegroups.com.
To post to this group, send email to pupil-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/pupil-discuss/f79425d2-a896-4e19-a46c-094aba2c8b66%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Michael Barz]

Hi,

unfortunately that's all. There is only this one line.

Michael

[Moritz Kassner]

Hi,

I made a new branch called 4vl2_debug , I will made some changes to it now and you can pull and test.

https://github.com/Pupil-Labs/Pupil/tree/v4l2_debug

Please send me the full logs found in the pupil settings dir.

best,

M

On Thu, Jan 23, 2014 at 3:21 PM, Michael Barz <micb...@googlemail.com> wrote:

Version 3.7 does not solve the problem.
The error still occurs...

--

You received this message because you are subscribed to the Google Groups "pupil-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pupil-discus...@googlegroups.com.
To post to this group, send email to pupil-...@googlegroups.com.

[Michael Barz]

Hi,

till today I was busy with another project.
I tested the new branch. The error ocurred again.
Additionally I had another error while saving metadata when stopping record.

Find the logs attached.

Kind regards,
Michael

[Moritz Kassner]

Hi Michael,

Since the error does not show up in the logs. Could you also then a paste of the console in Terminal?

Thank you very much,

m

[Michael Barz]

Hi,

for the recording error the console shows:
WORLD Process [WARNING] recorder : No calibration data found. Please calibrate first.
WORLD Process [WARNING] recorder : Could not save metadata. Please report this bug!

for the other error (world view crashes) the console shows only the following line:

VIDIOC_QBUF error 14, Bad address

Kind regards,
Michael

[Moritz Kassner]

On the 4vl2_debug branch:

you got "VIDIOC_QBUF error 14, Bad address" and nothing else?

m

[Moritz Kassner]

And the could not save metadata bug is interesting. Have you had this before?

I will make some changes to the brach and let you know when to test again.

m

[Michael Barz]

Hello,

yes I just cloned the branch this morning on the same pc into another directory and tested it.
The only output I get is the mentioned line. I get this line when using eclipse and when running from command line (via "python main.py" and "sudo python main.py").

And yes I had the log error also once with the normal 3.7 branch.

Kind regards,
Michael

[Michael Barz]

Hi, is there anything new about this issue?

[Moritz Kassner]

Hi Michael,

I will have a look at this again. Sorry I was swamped with other stuff recently.

best,

Moritz

[Moritz Kassner]

Hi Michael,

I have worked a bit more to get the v4l2 capture to be more robust to failure. It should be in the master branch now. Could you give it a try?

Best,

Moritz

[Michael Barz]

Hi Moritz,

unfortunately I can't test this issue anymore.
After upgrading my computer with an SSD my Ubuntu installation got corrupt.
It's even not possible for me to reinstall Ubuntu, since the Ubuntu installer breaks when loading the installer...

Seems that I have to switch to my laptop... (where this issue never occurred)

Kind regards,
Michael