* Re: Fw: bttv error: vmalloc_32(8519680) failed
[not found] ` <20040630183711.GA5064@bytesex>
@ 2004-07-01 15:49 ` Devel
0 siblings, 0 replies; only message in thread
From: Devel @ 2004-07-01 15:49 UTC (permalink / raw)
To: linux-kernel
Hi,
Thanks for your reply, i'm tring the 2.4.26 kernel with patch-2.4.26-kraxel.gz and i haven't error.
My IEI video grabber have the watchdog also do you think it work with bttv driver?
Saluti Carlo!
Il Wed, 30 Jun 2004 20:37:11 +0200
Gerd Knorr <kraxel@bytesex.org> scrisse:
> On Wed, Jun 30, 2004 at 10:27:32AM -0700, Andrew Morton wrote:
> >
> > Begin forwarded message:
> >
> > Date: Wed, 30 Jun 2004 11:51:21 +0200
> > From: Devel <devel@integra-sc.it>
> > To: linux-kernel@vger.kernel.org
> > Subject: bttv error: vmalloc_32(8519680) failed
> >
> >
> > Hi all, on my AMD XP+3000 with kernel 2.4.22 and bttv driver ver.
> > 0.7.107 i have 16 devices video grabber /dev/video0-->/dev/video15. If
> > i start programs that load images from the device /dev/video14 and
> > /dev/video15 i receive this error: bttv: vmalloc_32(8519680) failed
>
> Looks like the machine runs out of vmalloc address space when using all
> devices at the same time ...
>
> with gbuffers + gbufsize insmod options it is possible to adjust the
> amount of vmalloc memory used per device.
>
> The other option is to use bttv 0.9.x which doesn't use vmalloc any
> more. Making that one work with 2.4.22 isn't trivial through, easiest
> is to use either 2.6 (as-is) or a more recent 2.4.x kernel + patches
> from http://dl.bytesex.org/patches/
>
> Gerd
>
> --
> return -ENOSIG;
>
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2004-07-01 15:45 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <20040630102732.04f08d5a.akpm@osdl.org>
[not found] ` <20040630183711.GA5064@bytesex>
2004-07-01 15:49 ` Fw: bttv error: vmalloc_32(8519680) failed Devel
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®