From: Adrian Bunk <bunk@stusta.de>
To: Mauro Carvalho Chehab <mchehab@infradead.org>
Cc: mdharm-usb@one-eyed-alien.net,
usb-storage@lists.one-eyed-alien.net,
linux-kernel@vger.kernel.org, v4l-dvb-maintainer@linuxtv.org,
video4linux-list@redhat.com,
linux-usb-devel@lists.sourceforge.net
Subject: Re: [v4l-dvb-maintainer] 2.6.16-rc: saa7134 + usb-storage = freeze
Date: Thu, 16 Mar 2006 02:30:04 +0100 [thread overview]
Message-ID: <20060316013004.GA3914@stusta.de> (raw)
In-Reply-To: <1142454448.4666.44.camel@praia>
On Wed, Mar 15, 2006 at 05:27:28PM -0300, Mauro Carvalho Chehab wrote:
> Adrian,
> hmm... VIA vt8237... We have several similar reports with current VIA
> chipsets (KT800 and KT880) and PCI2PCI transfers (Overlay mode in
> xawtv). Would you please download the latest Mercurial development tree
> at
> http://linuxtv.org/hg/v4l-dvb and try modprobing saa7134 with the insmod
> option no_overlay=1.
>...
"Capture: grabdisplay" in xawtv seems to fix the problem.
I'll do some further tries whether this was only luck.
I don't know whether it's related, but xawtv sometimes spits warnings
like the following (independent of whether the USB disk is plugged in):
ioctl: VIDIOC_TRY_FMT(type=VIDEO_OVERLAY;fmt.win.w.left=306;fmt.win.w.top=191;fmt.win.w.width=43;fmt.win.w.height=35;fmt.win.field=ANY;fmt.win.chromakey=0;fmt.win.clips=(nil);fmt.win.clipcount=0;fmt.win.bitmap=(nil)): Invalid argument
ioctl: VIDIOC_S_FMT(type=VIDEO_OVERLAY;fmt.win.w.left=306;fmt.win.w.top=192;fmt.win.w.width=43;fmt.win.w.height=32;fmt.win.field=ANY;fmt.win.chromakey=0;fmt.win.clips=0x80c9a04;fmt.win.clipcount=0;fmt.win.bitmap=(nil)): Invalid argument
ioctl: VIDIOC_TRY_FMT(type=VIDEO_OVERLAY;fmt.win.w.left=306;fmt.win.w.top=191;fmt.win.w.width=43;fmt.win.w.height=35;fmt.win.field=ANY;fmt.win.chromakey=0;fmt.win.clips=(nil);fmt.win.clipcount=0;fmt.win.bitmap=(nil)): Invalid argument
ioctl: VIDIOC_S_FMT(type=VIDEO_OVERLAY;fmt.win.w.left=306;fmt.win.w.top=192;fmt.win.w.width=43;fmt.win.w.height=32;fmt.win.field=ANY;fmt.win.chromakey=0;fmt.win.clips=0x80c9a04;fmt.win.clipcount=0;fmt.win.bitmap=(nil)): Invalid argument
ioctl: VIDIOC_OVERLAY(int=0): Invalid argument
ioctl: VIDIOC_DQBUF(index=0;type=VIDEO_CAPTURE;bytesused=0;flags=0x0 [];field=ANY;;timecode.type=0;timecode.flags=0;timecode.frames=0;timecode.seconds=0;timecode.minutes=0;timecode.hours=0;timecode.userbits="";sequence=0;memory=unknown): Input/output error
> Cheers,
> Mauro.
>...
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
prev parent reply other threads:[~2006-03-16 1:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-15 18:51 2.6.16-rc: saa7134 + usb-storage = freeze Adrian Bunk
2006-03-15 19:38 ` [linux-usb-devel] " Alan Stern
2006-03-15 20:18 ` Duncan Sands
2006-03-15 21:15 ` Adrian Bunk
2006-03-15 20:27 ` [v4l-dvb-maintainer] " Mauro Carvalho Chehab
2006-03-16 1:30 ` Adrian Bunk [this message]
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=20060316013004.GA3914@stusta.de \
--to=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=mchehab@infradead.org \
--cc=mdharm-usb@one-eyed-alien.net \
--cc=usb-storage@lists.one-eyed-alien.net \
--cc=v4l-dvb-maintainer@linuxtv.org \
--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