All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephan von Krawczynski <skraw@ithnet.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Memory problem with bttv driver
Date: Mon, 14 Jan 2002 20:48:18 +0100	[thread overview]
Message-ID: <20020114204818.24a253cc.skraw@ithnet.com> (raw)
In-Reply-To: <E16QBLq-0002Mu-00@the-village.bc.nu>
In-Reply-To: <20020114184334.0a1712d4.skraw@ithnet.com> <E16QBLq-0002Mu-00@the-village.bc.nu>

On Mon, 14 Jan 2002 17:56:54 +0000 (GMT)
Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:

> > Can this be highmem-related?
> 
> That would make complete sense if so. The bttv uses vmalloc_32(), as the
> card has 32bit limits, and I am not running bttv (nor I suspect are most
> people) with highmem enabled

Ok. I tracked it down. It is definitely VMALLOC-stuff. I increased the
VMALLOC_RESERVE from 128 to 256 MB and now it _works_. Here is a list of loaded
modules, maybe one (or several) of those are known to be vmalloc-fans :-)


Module                  Size  Used by
tuner                   8048   1  (autoclean)
bttv                   60848   0 
i2c-algo-bit            7040   1  [bttv]
i2c-core               12224   0  [tuner bttv i2c-algo-bit]
videodev                4768   2  [bttv]
NVdriver              720128  14  (autoclean)
parport_pc             12432   1  (autoclean)
lp                      5984   0  (autoclean)
parport                12736   1  (autoclean) [parport_pc lp]
nfs                    73024   2  (autoclean)
lockd                  47056   1  (autoclean) [nfs]
sunrpc                 62496   1  (autoclean) [nfs lockd]
ipv6                  158464  -1  (autoclean)
uhci                   24896   0  (unused)
usbcore                48640   1  [uhci]
3c59x                  25312   1  (autoclean)
emu10k1                58080   0 
sound                  54064   0  [emu10k1]
ac97_codec              9504   0  [emu10k1]
hisax                 168112   4 
isdn                  115088   6  [hisax]
slhc                    4304   0  [isdn]
serial                 44128   0  (autoclean)


How can I find out?

Regards,
Stephan


  parent reply	other threads:[~2002-01-14 19:50 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-14 17:12 Memory problem with bttv driver Stephan von Krawczynski
2002-01-14 17:40 ` Alan Cox
2002-01-14 17:43   ` Stephan von Krawczynski
2002-01-14 17:56     ` Alan Cox
2002-01-14 18:38       ` Stephan von Krawczynski
2002-01-14 19:48       ` Stephan von Krawczynski [this message]
2002-01-14 20:03         ` Alan Cox
2002-01-14 20:00           ` Stephan von Krawczynski
2002-01-14 21:17             ` Alan Cox
2002-01-14 23:42               ` J.A. Magallon
2002-01-15 10:17                 ` Gerd Knorr
2002-01-15 11:14                   ` Stephan von Krawczynski
2002-01-15 13:20                     ` Gerd Knorr
2002-01-15 13:46                       ` Stephan von Krawczynski
2002-01-15 15:16                         ` Gerd Knorr
2002-01-15 16:35                           ` Stephan von Krawczynski
2002-01-16  9:57                             ` Gerd Knorr
2002-01-16 17:24                               ` Stephan von Krawczynski
     [not found] <Pine.LNX.4.21.0201142245040.2118-100000@localhost.localdomain>
2002-01-15  1:55 ` Stephan von Krawczynski

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=20020114204818.24a253cc.skraw@ithnet.com \
    --to=skraw@ithnet.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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 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.