From: Gerd Knorr <kraxel@bytesex.org>
To: Michael Buesch <mbuesch@freenet.de>
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 11:09:55 +0200 [thread overview]
Message-ID: <20031010090955.GE32386@bytesex.org> (raw)
In-Reply-To: <200310091729.30465.mbuesch@freenet.de>
> 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?
> 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.
Gerd
next prev parent reply other threads:[~2003-10-10 9:10 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 [this message]
2003-10-10 16:51 ` Michael Buesch
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=20031010090955.GE32386@bytesex.org \
--to=kraxel@bytesex.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mbuesch@freenet.de \
/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