From: Stephan von Krawczynski <skraw@ithnet.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Memory problem with bttv driver
Date: Mon, 14 Jan 2002 18:12:10 +0100 [thread overview]
Message-ID: <20020114181210.67650995.skraw@ithnet.com> (raw)
Hello,
yesterday we came across another MM related problem. This time its related to
the bttv-driver. We do very simple things:
First load it:
# modprobe bttv
Jan 14 17:28:14 fred kernel: bttv: driver version 0.7.83 loaded
Jan 14 17:28:14 fred kernel: bttv: using 2 buffers with 2080k (4160k total) for
capture Jan 14 17:28:14 fred kernel: bttv: Host bridge is VIA Technologies,
Inc. VT82C693A/694x [Apollo PRO133x] Jan 14 17:28:14 fred kernel: bttv: Host
bridge is VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] Jan 14 17:28:14
fred kernel: bttv: Bt8xx card found (0). Jan 14 17:28:14 fred kernel: bttv0:
Bt848 (rev 18) at 00:0c.0, irq: 16, latency: 32, memory: 0xef000000 Jan 14
17:28:14 fred kernel: bttv0: using: BT848A( *** UNKNOWN/GENERIC **)
[card=0,autodetected] Jan 14 17:28:14 fred kernel: i2c-core.o: adapter bt848 #0
registered as adapter 0. Jan 14 17:28:14 fred kernel: bttv0: i2c: checking for
MSP34xx @ 0x80... not found Jan 14 17:28:14 fred kernel: bttv0: i2c: checking
for TDA9875 @ 0xb0... not found Jan 14 17:28:14 fred kernel: bttv0: i2c:
checking for TDA7432 @ 0x8a... not found Jan 14 17:28:14 fred kernel:
i2c-core.o: driver i2c TV tuner driver registered. Jan 14 17:28:14 fred kernel:
tuner: chip found @ 0xc2 Jan 14 17:28:14 fred kernel: bttv0: i2c attach
[client=(unset),ok] Jan 14 17:28:14 fred kernel: i2c-core.o: client [(unset)]
registered to adapter [bt848 #0](pos. 0).
Then try to use it:
# xawtv
Jan 14 17:46:53 fred kernel: bttv: vmalloc_32(4259840) failed
... and exit of course.
Uh?
Interesting about it:
Does not work with 2.4.17 nor 2.4.18-pre3, but does work with 2.4.10-SUSE.
(Same setup, only booting another kernel)
Any hints?
Regards,
Stephan
next reply other threads:[~2002-01-14 17:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-14 17:12 Stephan von Krawczynski [this message]
2002-01-14 17:40 ` Memory problem with bttv driver 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
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=20020114181210.67650995.skraw@ithnet.com \
--to=skraw@ithnet.com \
--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