From: jackdeth@jippii.fi
To: linux-kernel@vger.kernel.org
Subject: 2.4.17 & bttv: vmalloc failures with 1GB memory
Date: Fri, 4 Jan 2002 20:36:56 +0200 (EET) [thread overview]
Message-ID: <1200795.1010169416398.JavaMail.jackdeth@jippii.fi> (raw)
i'm having problems using video capture under linux. i've tried several
capturing programs using libavifile. i can sometimes get capturing to
work right after reboot, but after using machine for some time
(cache/buffers fill up etc?), it stops working and i get messages like
this:
Jan 2 23:25:44 xxx kernel: bttv: vmalloc_32(4259840) failed
Jan 2 23:25:44 xxx kernel: bttv: vmalloc_32(4259840) failed
Jan 2 23:26:50 xxx last message repeated 13 times
currently i'm using stock kernel 2.4.17 with 4gb highmem support and
bttv. my system is as follows:
athlonxp 1600+
epox 8kha+
1GB memory
bt878 tv-card
could this be related to the recent allocation and cache freeing problems?
please cc me on replys.
__
Tämän ilmaisen suomalaisen sähköpostin tarjosi http://www.jippii.fi/
Käy tutustumassa netin parhaaseen pelipaikkaan Pasimaailmaan.
reply other threads:[~2002-01-04 18:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1200795.1010169416398.JavaMail.jackdeth@jippii.fi \
--to=jackdeth@jippii.fi \
--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