Messages in this thread | | | Date | Mon, 14 Jan 2002 20:48:18 +0100 | From | Stephan von Krawczynski <> | Subject | Re: Memory problem with bttv driver |
| |
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
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |