All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gianluca Gennari <gennarone@gmail.com>
To: Devin Heitmueller <dheitmueller@kernellabs.com>
Cc: Andy Furniss <andyqos@ukfsn.org>, linux-media@vger.kernel.org
Subject: Re: PCTV 290e page allocation failure
Date: Fri, 03 Feb 2012 00:06:07 +0100	[thread overview]
Message-ID: <4F2B16DF.3040400@gmail.com> (raw)
In-Reply-To: <CAGoCfiyTHNkr3gNAZUefeZN88-5Vd9SEyGUeFjYO-ddG1WqgzA@mail.gmail.com>

Il 02/02/2012 20:07, Devin Heitmueller ha scritto:
> On Thu, Feb 2, 2012 at 2:02 PM, Gianluca Gennari <gennarone@gmail.com> wrote:
>> I'm trying to reproduce the problem with another em28xx-dvb device to
>> see if it is not restricted to the PCTV 290e. Before the PCTV 290e, I
>> was using a different device with a driver based on the dvb-usb
>> framework, and I never observed similar crashes.
> 
> On ARM based platforms it is very likely you will run into this issue
> with most USB based tuners.  It's because over time there is memory
> fragmentation that occurs which prevents being able to allocate large
> enough chunks of coherent memory.
> 
> Making such a scenario work would require hacks to the driver code to
> preallocate the memory in some form of static pool at system boot (or
> perhaps at driver initialization), and then reuse that memory instead
> of attempting to allocate it as needed.
> 
> Devin
> 

Hi Devin,
thanks for the explanation. The CPU is MIPS based (not ARM) but I guess
there is not much of a difference from this point of view.
As I mentioned in my first reply, I never had this kind of errors when I
was using a dvb-usb USB stick. Now I'm trying to replicate the problem
with a Terratec Hybrid XS (em28xx-dvb + zl10353 + xc2028), and so far
I've stressed it for a few hours without problems. We will see in a day
or two if I can make it fail in the same way.

Regards,
Gianluca



  reply	other threads:[~2012-02-02 23:06 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-02 17:28 PCTV 290e page allocation failure Andy Furniss
2012-02-02 19:02 ` Gianluca Gennari
2012-02-02 19:07   ` Devin Heitmueller
2012-02-02 23:06     ` Gianluca Gennari [this message]
2012-02-02 23:12       ` Devin Heitmueller
2012-02-02 23:28         ` Gianluca Gennari
2012-02-07 10:44         ` Gianluca Gennari
2012-02-07 14:49           ` Andy Furniss
2012-02-07 15:18           ` Devin Heitmueller
2012-02-07 16:01             ` Gianluca Gennari
2012-02-07 16:53               ` Devin Heitmueller
2012-02-02 19:56   ` Andy Furniss
2012-02-02 23:12     ` Gianluca Gennari
2012-02-03 11:04       ` Andy Furniss
2012-02-03 18:47         ` Gianluca Gennari
2012-02-07 14:57 ` Andy Furniss
2012-02-07 18:10   ` Gianluca Gennari
2012-02-07 20:28     ` Devin Heitmueller

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=4F2B16DF.3040400@gmail.com \
    --to=gennarone@gmail.com \
    --cc=andyqos@ukfsn.org \
    --cc=dheitmueller@kernellabs.com \
    --cc=linux-media@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.