From: Andy Furniss <adf.lists@gmail.com>
To: Mauro Carvalho Chehab <mchehab@osg.samsung.com>,
"Gabor Z. Papp" <gzpapp.lists@gmail.com>
Cc: linux-media@vger.kernel.org
Subject: Re: em28xx problem with 3.10-4.0
Date: Tue, 16 Jun 2015 12:09:11 +0100 [thread overview]
Message-ID: <558003D7.1080906@gmail.com> (raw)
In-Reply-To: <20150616062056.34b4d4ef@recife.lan>
Mauro Carvalho Chehab wrote:
> Em Tue, 16 Jun 2015 08:54:58 +0200 "Gabor Z. Papp"
> <gzpapp.lists@gmail.com> escreveu:
>
>> * "Gabor Z. Papp" <gzpapp.lists@gmail.com>:
>>
>> | I would like to use my Pinnacle Dazzle DVC usb encoder with
>> kernels | 3.10-4.0, but I'm getting the same error all the time.
>>
>> | Latest working kernel is the 3.4 line.
>>
>> | What happend with the driver?
>
> Nothing. You just ran out of continuous memory. This driver requires
> long chunks of continuous memory for USB data transfer.
>
> Please see this thread:
> http://www.spinics.net/lists/linux-media/msg43868.html
>
> As far as I remember, some things changed from 3.4 on the part that
> allocates memory there, reducing the risk of getting out of memory,
> but can't remember the specific details anymore.
Oh interesting - I only recently stopped using the low mem box in that
post. I think I ended up on kernel 3.9 and had uptimes of > 200 days
without issue.
I still have the 290e but now on a box with 4 gig ram - haven't had time
to see if I'll hit it again with 4.1.
My use case was dvb not analogue.
If you just want to plug and cap something you may be able to workaround
by first, as root, doing -
sync;echo 3 >/proc/sys/vm/drop_caches
to clean out men.
next prev parent reply other threads:[~2015-06-16 11:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-11 8:11 em28xx problem with 3.10-4.0 Gabor Z. Papp
2015-06-16 6:54 ` Gabor Z. Papp
2015-06-16 9:20 ` Mauro Carvalho Chehab
2015-06-16 11:09 ` Andy Furniss [this message]
2015-06-17 6:32 ` Gabor Z. Papp
2015-06-17 11:02 ` Mauro Carvalho Chehab
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=558003D7.1080906@gmail.com \
--to=adf.lists@gmail.com \
--cc=gzpapp.lists@gmail.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@osg.samsung.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