From: Devel <devel@integra-sc.it>
To: linux-kernel@vger.kernel.org
Subject: Re: Fw: bttv error: vmalloc_32(8519680) failed
Date: Thu, 1 Jul 2004 17:49:55 +0200 [thread overview]
Message-ID: <20040701174955.46c63ffe.devel@integra-sc.it> (raw)
In-Reply-To: <20040630183711.GA5064@bytesex>
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;
>
parent reply other threads:[~2004-07-01 15:45 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20040630183711.GA5064@bytesex>]
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=20040701174955.46c63ffe.devel@integra-sc.it \
--to=devel@integra-sc.it \
--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 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®