From: Michael Buesch <mbuesch@freenet.de>
To: Gerd Knorr <kraxel@bytesex.org>
Cc: linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [2.6-test7] [bttv] lots of warning/error messages
Date: Fri, 10 Oct 2003 18:51:31 +0200 [thread overview]
Message-ID: <200310101851.43828.mbuesch@freenet.de> (raw)
In-Reply-To: <20031010090955.GE32386@bytesex.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Friday 10 October 2003 11:09, Gerd Knorr wrote:
> > get lots of warning/error messages from the bttv driver.
> > Here are todays messages:
> >
> > Oct 9 15:51:13 lfs kernel: bttv0: skipped frame. no signal? high irq
> > latency? Oct 9 15:57:57 lfs kernel: bttv0: OCERR @ 1fd95000,bits: HSYNC
> > OFLOW OCERR*
>
> Hmm. Is the signal good?
Hm, I think so. I never had problems with the signal quality
and it looks quite good.
The whole thing works with linux-2.4 and it worked with 2.6-test1.
As far as I remember the trouble started with test2. (I posted
to lkml after I first saw the trouble. The
crashes disappeared now, but the messages are still there.)
> > I'm using a preemptible kernel.
> > Should I try it again with preemptible disabled?
>
> I would be surprised if CONFIG_PREMPT on/off makes a difference, looks
> more like a hardware issue to me. Neverless it's worth a try.
I disabled CONFIG_PREMPT and it still throws these messages.
> Gerd
- --
Regards Michael Buesch [ http://www.tuxsoft.de.vu ]
Animals on this machine: some GNUs and Penguin 2.6.0-test7
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
iD8DBQE/huOfoxoigfggmSgRAgFcAJ4r2nyywOx78fkPj+jAZUvuGO3BowCdGH3F
jSujCOIOkOEaC2zARuv2WtA=
=uIrj
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2003-10-10 14:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-09 15:29 [2.6-test7] [bttv] lots of warning/error messages Michael Buesch
2003-10-10 9:09 ` Gerd Knorr
2003-10-10 16:51 ` Michael Buesch [this message]
2003-10-11 4:32 ` Nuno Silva
2003-10-11 18:10 ` Michael Buesch
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=200310101851.43828.mbuesch@freenet.de \
--to=mbuesch@freenet.de \
--cc=kraxel@bytesex.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.