Linux Media Controller development
 help / color / mirror / Atom feed
From: khalasa@piap.pl (Krzysztof Hałasa)
To: Andrey Utkin <andrey.utkin@corp.bluecherry.net>
Cc: "hans.verkuil" <hans.verkuil@cisco.com>,
	Linux Media <linux-media@vger.kernel.org>
Subject: Re: [RFC] solo6x10 freeze, even with Oct 31's linux-next... any ideas or help?
Date: Fri, 14 Nov 2014 12:00:59 +0100	[thread overview]
Message-ID: <m3sihmf3mc.fsf@t19.piap.pl> (raw)
In-Reply-To: <CAM_ZknVTqh0VnhuT3MdULtiqHJzxRhK-Pjyb58W=4Ldof0+jgA@mail.gmail.com> (Andrey Utkin's message of "Tue, 11 Nov 2014 19:46:46 +0200")

Andrey Utkin <andrey.utkin@corp.bluecherry.net> writes:

> The problem is the following: after ~1 hour of uptime with working
> application reading the streams, one card (the same one every time)
> stops producing interrupts (counter in /proc/interrupts freezes), and
> all threads reading from that card hang forever in
> ioctl(VIDIOC_DQBUF).

There is a race condition in the IRQ handler, at least in 3.17.
I don't know if it's related, will post a patch.
-- 
Krzysztof Halasa

Research Institute for Automation and Measurements PIAP
Al. Jerozolimskie 202, 02-486 Warsaw, Poland

  parent reply	other threads:[~2014-11-14 11:08 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-11 17:46 [RFC] solo6x10 freeze, even with Oct 31's linux-next... any ideas or help? Andrey Utkin
2014-11-11 18:05 ` Hans Verkuil
2014-11-11 18:16   ` Andrey Utkin
2014-11-14  7:29     ` Andrey Utkin
2014-11-27  5:45   ` Ismael Luceno
2014-11-14 11:00 ` Krzysztof Hałasa [this message]
2014-11-14 11:42   ` Andrey Utkin
2014-11-15 13:48     ` Andrey Utkin
2014-11-15 14:08       ` Hans Verkuil
2014-11-15 14:23         ` Andrey Utkin
2014-11-15 20:42       ` Krzysztof Hałasa
2014-11-15 22:12         ` Andrey Utkin
2014-11-27  5:49         ` Ismael Luceno

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m3sihmf3mc.fsf@t19.piap.pl \
    --to=khalasa@piap.pl \
    --cc=andrey.utkin@corp.bluecherry.net \
    --cc=hans.verkuil@cisco.com \
    --cc=linux-media@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox