Bug 67903

On Sun, Jun 13, 2004 at 02:43:08PM +0200, Stefan Schmidt wrote:
> 
> >Number:         67903
> >Category:       alpha
> >Synopsis:       hw.chipset.memory: 1099511627776 - thats way to much :)
> >Confidential:   no
> >Severity:       non-critical
> >Priority:       low
> >Responsible:    freebsd-alpha
> >State:          open
> >Quarter:        
> >Keywords:       
> >Date-Required:
> >Class:          sw-bug
> >Submitter-Id:   current-users
> >Arrival-Date:   Sun Jun 13 12:50:14 GMT 2004
> >Closed-Date:
> >Last-Modified:
> >Originator:     Stefan Schmidt
> >Release:        FreeBSD 5.2-CURRENT alpha
> >Organization:
> >Environment:
> System: FreeBSD wheeler.zaphods.net 5.2-CURRENT FreeBSD 5.2-CURRENT #3: Sun Jun 13 02:19:56 CEST 2004 root@wheeler.zaphods.net:/usr/src/sys/alpha/compile/WHEELER alpha
> 
> Chipset memory size has value way out of limits. I got suspicious when i saw the
> following line in top:
>  2574 root      78    0 12347M 57952K select  12:33  3.12%  3.12% XFree86

What's wrong with this?
OK 12347M is big, but not a problem for alphas.
It could be that this is memory mapped space for your graphic card and
likely to be an absolute correct value.

> sysctl:
> No unusually high values in kern.malloc or vm.zone.
> vm.vmtotal: 
> System wide totals computed every five seconds: (values in kilobytes)
> ===============================================
> Processes:              (RUNQ: 5 Disk Wait: 1 Page Wait: 0 Sleep: 84)
> Virtual Memory:         (Total: 18014398507962985K, Active 21213936K)
> Real Memory:            (Total: 418416K Active 213808K)
> Shared Virtual Memory:  (Total: 66408K Active: 64272K)
> Shared Real Memory:     (Total: 59448K Active: 58192K)
> Free Memory Pages:      580872K

Well having 21213936K active is clearly wrong.

> hw.chipset.ports: 1108034453504
> hw.chipset.memory: 1099511627776
> hw.chipset.dense: 1099511627776

What's wrong with those values?
That's addressspace not physical memory.
Alphas have plenty of addressspace no need to be thrifty with it.

-- 
B.Walter                   BWCT                http://www.bwct.de
bernd@bwct.de                                  info@bwct.de

This PR is about 2 seperate issues really:

1- hw.chipset.memory
    as said previously this value is about address space,
    the value reported seems to be correct for Tsunami alpha's
    ( confirmed on ds10 ). An 164SX seems to have about half the space.

2- The vm space reported
    This seemlingly is caused by xfree doing large mmaps of video memory.
    I have never seen these kind of values.
    I would propose opening a new pr for xfree/vmspace if this proplem
    still exists in CURRENT.

-- 
Sten Spans

"There is a crack in everything, that's how the light gets in."
Leonard Cohen - Anthem

Comment 3 John Baldwin 2010-11-03 13:25:56 UTC

State Changed
From-To: open->closed

Not a bug, X was just mmaping a large chunk of virtual memory.