linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Knorr <kraxel@bytesex.org>
To: Sami Farin <7atbggg02@sneakemail.com>
Cc: linux-kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: bttv/v4l2/Linux 2.6.10-ac8: xawtv hanging in videobuf_waiton
Date: 10 Jan 2005 12:35:33 +0100	[thread overview]
Message-ID: <871xct1pq2.fsf@bytesex.org> (raw)
In-Reply-To: <20050110000043.GA9549@m.safari.iki.fi>

Sami Farin <7atbggg02@sneakemail.com> writes:

> when I start xawtv and alevt in the same window and press 'v' in xawtv,
> bttv goes berserk, producing around 25 lines per second of debug stuffs.
> (xawtv was also in fullscreen mode when I did this).
> alevt quits just fine.
> 
> Jan 10 00:43:26 safari kernel: bttv0: OCERR @ 0d1f9014,bits: HSYNC OFLOW OCERR*
> Jan 10 00:43:26 safari last message repeated 11 times
> Jan 10 00:43:26 safari kernel: bttv0: timeout: drop=0 irq=7236/7236, risc=0d1f901c, bits: HSYNC OFLOW
> Jan 10 00:43:26 safari kernel: bttv0: reset, reinitialize
> Jan 10 00:43:26 safari kernel: bttv0: PLL: 28636363 => 35468950 . ok
> Jan 10 00:43:55 safari kernel: bttv0: OCERR @ 0d1f901c,bits: VSYNC HSYNC OFLOW RISCI* OCERR*

Any change with latest updates from http://dl.bytesex.org/patches/ ?

I can reproduce with the latest bits.  There was a state handling bug
when using both video + vbi recently through, not sure whenever the
fix made it into 2.6.10 or not.

  Gerd

-- 
#define printk(args...) fprintf(stderr, ## args)

  reply	other threads:[~2005-01-10 12:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-10  0:00 bttv/v4l2/Linux 2.6.10-ac8: xawtv hanging in videobuf_waiton Sami Farin
2005-01-10 11:35 ` Gerd Knorr [this message]
2005-01-10 16:18   ` Sami Farin
2005-01-14  3:22     ` Sami Farin
2005-01-20 11:12       ` Gerd Knorr

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=871xct1pq2.fsf@bytesex.org \
    --to=kraxel@bytesex.org \
    --cc=7atbggg02@sneakemail.com \
    --cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).