public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephan von Krawczynski <skraw@ithnet.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Memory problem with bttv driver
Date: Mon, 14 Jan 2002 18:43:34 +0100	[thread overview]
Message-ID: <20020114184334.0a1712d4.skraw@ithnet.com> (raw)
In-Reply-To: <E16QB5s-0002J9-00@the-village.bc.nu>
In-Reply-To: <20020114181210.67650995.skraw@ithnet.com> <E16QB5s-0002J9-00@the-village.bc.nu>

On Mon, 14 Jan 2002 17:40:24 +0000 (GMT)
Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:

> > yesterday we came across another MM related problem. This time its related
to> > the bttv-driver. We do very simple things:
> 
> Do you trust your kernel build ?

Yes.

> The bt848 drivers are working beautifully
> for me in 2.4.18pre

Well, I had a quick look at the code, and it seems that vmalloc is just
failing, the source line is obvious./proc/meminfo before modprobe and xawtv:

        total:    used:    free:  shared: buffers:  cached:
Mem:  1054728192 120070144 934658048        0 10420224 65257472
Swap: 1085652992        0 1085652992
MemTotal:      1030008 kB
MemFree:        912752 kB
MemShared:           0 kB
Buffers:         10176 kB
Cached:          63728 kB
SwapCached:          0 kB
Active:          26056 kB
Inactive:        73692 kB
HighTotal:      131056 kB
HighFree:        36720 kB
LowTotal:       898952 kB
LowFree:        876032 kB
SwapTotal:     1060208 kB
SwapFree:      1060208 kB

And afterwards:

        total:    used:    free:  shared: buffers:  cached:
Mem:  1054728192 120537088 934191104        0 10612736 65273856
Swap: 1085652992        0 1085652992
MemTotal:      1030008 kB
MemFree:        912296 kB
MemShared:           0 kB
Buffers:         10364 kB
Cached:          63744 kB
SwapCached:          0 kB
Active:          26140 kB
Inactive:        73812 kB
HighTotal:      131056 kB
HighFree:        36608 kB
LowTotal:       898952 kB
LowFree:        875688 kB
SwapTotal:     1060208 kB
SwapFree:      1060208 kB

Can this be highmem-related?

Regards,
Stephan



  reply	other threads:[~2002-01-14 17:44 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-14 17:12 Memory problem with bttv driver Stephan von Krawczynski
2002-01-14 17:40 ` Alan Cox
2002-01-14 17:43   ` Stephan von Krawczynski [this message]
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=20020114184334.0a1712d4.skraw@ithnet.com \
    --to=skraw@ithnet.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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