From: Bill Davidsen <davidsen@tmr.com>
To: James Bruce <bruce@andrew.cmu.edu>
Cc: Gerd Knorr <kraxel@bytesex.org>, linux-kernel@vger.kernel.org
Subject: Re: Potentially dead bttv cards from 2.6.10
Date: Mon, 28 Feb 2005 18:14:11 -0500 [thread overview]
Message-ID: <4223A5C3.6010000@tmr.com> (raw)
In-Reply-To: <42232DFC.6090000@andrew.cmu.edu>
James Bruce wrote:
> Well, are there any theories as to why it would work flawlessly, then
> after a hard lockup (due to what I think is a buggy V4L2 application),
> that the cards no longer work? That was with 2.6.10, but after they
> started failing I tried 2.6.11-rc5 and it doesn't work either. By the
> way, I sent the wrong output; what I sent was from 2.6.11-rc5. The
> 2.6.10 output is below, and looks similar except for generating a
> different error message.
Is there any chance that the lockup was related to an external event,
like a spike on the line to the video? Or any other outside event? It
seems like a very odd failure mode, but since I'm about to drop in a
bttv card and digitize about a hundred old tapes, I'd like to know.
Did you try the "card=" suggestion?
--
-bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
last possible moment - but no longer" -me
next prev parent reply other threads:[~2005-02-28 23:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-26 4:57 Potentially dead bttv cards from 2.6.10 James Bruce
2005-02-28 13:44 ` Gerd Knorr
2005-02-28 14:43 ` James Bruce
2005-02-28 16:02 ` Gerd Knorr
2005-02-28 16:45 ` Folkert van Heusden
2005-02-28 16:52 ` Gerd Knorr
2005-03-01 6:41 ` James Bruce
2005-03-01 8:44 ` Gerd Knorr
2005-03-01 13:10 ` James Bruce
2005-03-04 20:37 ` James Bruce
2005-02-28 23:14 ` Bill Davidsen [this message]
2005-03-01 7:06 ` James Bruce
2005-03-01 14:11 ` Paulo Marques
2005-03-01 15:44 ` James Bruce
2005-03-01 16:03 ` Gerd Knorr
2005-03-01 20:32 ` Bill Davidsen
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=4223A5C3.6010000@tmr.com \
--to=davidsen@tmr.com \
--cc=bruce@andrew.cmu.edu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox