public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@infradead.org>
To: hermann pitton <hermann-pitton@arcor.de>
Cc: video4linux-list@redhat.com, g.liakhovetski@pengutronix.de,
	Brandon Philips <bphilips@suse.de>
Subject: Re: kernel oops since changeset e3b8fb8cc214
Date: Fri, 14 Mar 2008 11:15:06 -0300	[thread overview]
Message-ID: <20080314111506.0c4cab80@gaivota> (raw)
In-Reply-To: <1205448483.6359.15.camel@pc08.localdom.local>

On Thu, 13 Mar 2008 23:48:03 +0100
hermann pitton <hermann-pitton@arcor.de> wrote:

> definitely I'm not enough into it to be of much help soon, especially
> not for cx88xx and to answer offhand if Guennadi has the bug already,
> starting obviously with errors in the irq handler there.
> 
> Thanks Matthias for your report, we seem to have the same. On my
> uniprocessor 32bit 2.6.25-rc5 stuff and saa7131e, running since lunch
> with DVB-T and analog video at once, all seems to be normal and still
> totally stable.

I did yesterday a quick test on an AMD dual core machine, with a Linux 64 bits
distro. I didn't got any errors with Pixelview 8000GT (cx88+xc3028). Yet, the
tests are not conclusive, since I left the application running for some seconds
only (*). I did some start/stop procedures. I intend to run Brandon's pthread
version of capture-example during the weekend.

(*) Yet, generally, just a couple of seconds is enough to cause big troubles
when videobuf is suffering troubles.

Cheers,
Mauro

--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

  parent reply	other threads:[~2008-03-14 14:16 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-26 12:26 kernel oops since changeset e3b8fb8cc214 Eric Thomas
2008-03-08  7:45 ` Eric Thomas
2008-03-08  9:37   ` Guennadi Liakhovetski
2008-03-09  8:41     ` Eric Thomas
2008-03-09 11:32       ` Guennadi Liakhovetski
2008-03-11 22:04         ` Guennadi Liakhovetski
2008-03-12  0:23           ` hermann pitton
2008-03-12  7:34             ` Guennadi Liakhovetski
2008-03-12 22:28               ` hermann pitton
2008-03-13 16:07                 ` Guennadi Liakhovetski
2008-03-08 10:59   ` Mauro Carvalho Chehab
2008-03-09  8:55     ` Eric Thomas
2008-03-11  9:45       ` Craig Whitmore
2008-03-11 17:39     ` Matthias Schwarzott
2008-03-12  0:26       ` hermann pitton
2008-03-13 15:55         ` Matthias Schwarzott
2008-03-13 17:59           ` Mauro Carvalho Chehab
2008-03-13 22:48             ` hermann pitton
2008-03-13 22:56               ` hermann pitton
2008-03-14 14:15               ` Mauro Carvalho Chehab [this message]
2008-03-14 14:33                 ` Guennadi Liakhovetski
2008-03-14 16:16                   ` Craig Whitmore
2008-03-15  7:22                     ` Eric Thomas

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=20080314111506.0c4cab80@gaivota \
    --to=mchehab@infradead.org \
    --cc=bphilips@suse.de \
    --cc=g.liakhovetski@pengutronix.de \
    --cc=hermann-pitton@arcor.de \
    --cc=video4linux-list@redhat.com \
    /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