linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* 2.6.0-t11 /proc/<xserver pid>/status question (VmLck > 4TB)
@ 2003-12-03 15:15 Martin Zwickel
  2003-12-03 15:28 ` Måns Rullgård
  2003-12-03 15:46 ` William Lee Irwin III
  0 siblings, 2 replies; 3+ messages in thread
From: Martin Zwickel @ 2003-12-03 15:15 UTC (permalink / raw)
  To: linux-kernel

[-- Attachment #1: Type: text/plain, Size: 1526 bytes --]

Hi there,

I have a small question:

If I look into the "/proc/<xserver pid>/status" file, there is a VmLck with a
4TeraByte number.

Is that normal?

# cat /proc/7850/status 
Name:   X
State:  S (sleeping)
SleepAVG:       101%
Tgid:   7850
Pid:    7850
PPid:   7848
TracerPid:      0
Uid:    0       0       0       0
Gid:    0       0       0       0
FDSize: 256
Groups: 0 
VmSize:   377396 kB
VmLck:  4294967292 kB
VmRSS:     65724 kB
VmData:   101456 kB
VmStk:       320 kB
VmExe:      1604 kB
VmLib:      6844 kB
Threads:        1
SigPnd: 0000000000000000
ShdPnd: 0000000000000000
SigBlk: 0000000000000000
SigIgn: 8000000000301000
SigCgt: 00000000518066cb
CapInh: 0000000000000000
CapPrm: 00000000fffffeff
CapEff: 00000000fffffeff


Most other processes have 0kb.

cat /proc/*/status  | grep VmLck

...
VmLck:         0 kB
VmLck:         0 kB
VmLck:      2060 kB
VmLck:         0 kB
VmLck:         0 kB
VmLck:         4 kB
VmLck:         0 kB
...

Regards,
Martin


ps.:

I'm using the nvidia driver.
# cat /proc/driver/nvidia/version 
NVRM version: NVIDIA Linux x86 nvidia.o Kernel Module  1.0-4496  Wed Jul 16
19:03:09 PDT 2003 GCC version:  gcc version 3.2.3 20030422 (Gentoo Linux 1.4
3.2.3-r2, propolice)

# cat /proc/version 
Linux version 2.6.0-test11 (root@phoebee) (gcc version 3.2.3 20030422 (Gentoo
Linux 1.4 3.2.3-r2, propolice)) #6 Thu Nov 27 13:02:23 CET 2003

-- 
MyExcuse:
SCSI's too wide.

Martin Zwickel <martin.zwickel@technotrend.de>
Research & Development

TechnoTrend AG <http://www.technotrend.de>

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: 2.6.0-t11 /proc/<xserver pid>/status question (VmLck > 4TB)
  2003-12-03 15:15 2.6.0-t11 /proc/<xserver pid>/status question (VmLck > 4TB) Martin Zwickel
@ 2003-12-03 15:28 ` Måns Rullgård
  2003-12-03 15:46 ` William Lee Irwin III
  1 sibling, 0 replies; 3+ messages in thread
From: Måns Rullgård @ 2003-12-03 15:28 UTC (permalink / raw)
  To: linux-kernel

Martin Zwickel <martin.zwickel@technotrend.de> writes:

> Hi there,
>
> I have a small question:
>
> If I look into the "/proc/<xserver pid>/status" file, there is a VmLck with a
> 4TeraByte number.
>
> Is that normal?
>
> VmLck:  4294967292 kB

FWIW, that is -4 as an unsigned 32-bit number.

> Most other processes have 0kb.

My X shows 0.  I have a SiS chip.

-- 
Måns Rullgård
mru@kth.se


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: 2.6.0-t11 /proc/<xserver pid>/status question (VmLck > 4TB)
  2003-12-03 15:15 2.6.0-t11 /proc/<xserver pid>/status question (VmLck > 4TB) Martin Zwickel
  2003-12-03 15:28 ` Måns Rullgård
@ 2003-12-03 15:46 ` William Lee Irwin III
  1 sibling, 0 replies; 3+ messages in thread
From: William Lee Irwin III @ 2003-12-03 15:46 UTC (permalink / raw)
  To: Martin Zwickel; +Cc: linux-kernel

On Wed, Dec 03, 2003 at 04:15:05PM +0100, Martin Zwickel wrote:
> Hi there,
> I have a small question:
> If I look into the "/proc/<xserver pid>/status" file, there is a VmLck with a
> 4TeraByte number.
> Is that normal?

Nope, it's a bug.


-- wli

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2003-12-03 15:47 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-12-03 15:15 2.6.0-t11 /proc/<xserver pid>/status question (VmLck > 4TB) Martin Zwickel
2003-12-03 15:28 ` Måns Rullgård
2003-12-03 15:46 ` William Lee Irwin III

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).