public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: John Cavan <johnc@damncats.org>
To: "Dieter Nützel" <Dieter.Nuetzel@hamburg.de>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>,
	DRI-Devel <dri-devel@lists.sourceforge.net>,
	Alan Cox <alan@redhat.com>
Subject: Re: Linux 2.4.5-ac14
Date: Fri, 15 Jun 2001 07:24:06 -0400	[thread overview]
Message-ID: <3B29F056.97C353C@damncats.org> (raw)
In-Reply-To: <20010615022033Z261561-17720+4111@vger.kernel.org> <3B29734A.738A95D5@damncats.org> <200106150442.AAA22505@spqr.damncats.org>

Dieter Nützel wrote:
> 
> Am Freitag, 15. Juni 2001 05:32 schrieb Dieter Nützel:
> > Am Freitag, 15. Juni 2001 04:30 schrieb John Cavan:
> > > Dieter Nützel wrote:
> > > > Hello Alan,
> > > >
> > > > I see 4.29 GB under shm with your latest try.
> > > > something wrong?
> > >
> > >         total:    used:    free:  shared: buffers:  cached:
> > > Mem:  1053483008 431419392 622063616   122880 24387584 260923392
> > > Swap: 394764288        0 394764288
> > > MemTotal:      1028792 kB
> > > MemFree:        607484 kB
> > > MemShared:         120 kB
> > > Buffers:         23816 kB
> > > Cached:         254808 kB
> > > Active:         225536 kB
> > > Inact_dirty:     53208 kB
> > > Inact_clean:         0 kB
> > > Inact_target:       44 kB
> > > HighTotal:      131056 kB
> > > HighFree:         1048 kB
> > > LowTotal:       897736 kB
> > > LowFree:        606436 kB
> > > SwapTotal:      385512 kB
> > > SwapFree:       385512 kB
> > >
> > > I don't seem to have the problem...
> >
> > You are using HIGHMEM?!

Sort of necessary when you have 1gb of RAM. My machine is also a dual
CPU box.

> I tested some more and found this.
> 
> It is XFree86 4.1.0 DRI (tdfx driver) related.
> During my first run I used the 2.4.5-ac14 kernel DRM module.
> Now I am running with the latest DRI trunk DRM module.
> Both show the same symptoms.

Well, I'm running XFree86 4.1.0 DRI with the Radeon driver and I don't
show the symptoms. I use the Radeon module from DRI on SourceForge.

Have you tried it with CONFIG_HIGHMEM in the kernel?

John

  parent reply	other threads:[~2001-06-15 11:24 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-15  2:33 Linux 2.4.5-ac14 Dieter Nützel
2001-06-15  2:30 ` John Cavan
2001-06-15  3:32   ` Dieter Nützel
2001-06-15  4:55   ` Dieter Nützel
     [not found]   ` <200106150442.AAA22505@spqr.damncats.org>
2001-06-15 11:24     ` John Cavan [this message]
2001-06-15 10:01 ` Christoph Rohland
     [not found] <200106162255.SAA02119@olimpo.networx.com.br.suse.lists.linux.kernel>
     [not found] ` <E15B0vv-000780-00@the-village.bc.nu.suse.lists.linux.kernel>
     [not found]   ` <15146.33742.299279.102372@pizda.ninka.net.suse.lists.linux.kernel>
2001-06-16  5:57     ` Andi Kleen
2001-06-16  6:15       ` Alexander Viro
2001-06-16  7:37       ` Alexander Viro
2001-06-16  8:20         ` Marc ZYNGIER
2001-06-16  8:36           ` Alexander Viro
2001-06-17 20:47         ` Olaf Hering
2001-06-16 16:33       ` David S. Miller
  -- strict thread matches above, loose matches on Subject: below --
2001-06-14 22:44 Alan Cox
2001-06-15 21:05 ` Thiago Vinhas de Moraes
2001-06-15 21:15   ` Alan Cox
2001-06-15 21:37     ` Andreas Dilger
2001-06-15 21:53     ` David S. Miller
2001-06-16 20:56     ` Thiago Vinhas de Moraes
2001-06-16 21:14       ` Arnaldo Carvalho de Melo

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=3B29F056.97C353C@damncats.org \
    --to=johnc@damncats.org \
    --cc=Dieter.Nuetzel@hamburg.de \
    --cc=alan@redhat.com \
    --cc=dri-devel@lists.sourceforge.net \
    --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