Re: port-amd64/54988: possible memory leaks/swap problems

[mlh%goathill.org@localhost (MLH)]

Andrew Doran wrote:
> The following reply was made to PR port-amd64/54988; it has been noted by GNATS.
> 
> From: Andrew Doran <ad%netbsd.org@localhost>
> To: MLH <mlh%goathill.org@localhost>
> Cc: gnats-bugs%netbsd.org@localhost
> Subject: Re: port-amd64/54988: possible memory leaks/swap problems
> Date: Sun, 23 Feb 2020 21:55:48 +0000
> 
>  Stress testing under low memory conditions I'm not able to reproduce this,
>  however the machine is headless.  I'll try more I/O intensive stuff when I
>  get a chance.
>  
>  If you are still able to run vmstat, then the output of "vmstat -s" say
>  every 10 seconds over the course of a minute would be very useful.  If you
>  have "top -t" running, it would be interesting to observe if pgdaemon is
>  consuming a lot of CPU time.

Unfortunately I saw there were updates to uvm so rebuilt everything
and now it crashes towards the end of X starting up, right after
Initializing extension GLX.

[    57.167] (II) Initializing extension X-Resource
[    57.167] (II) Initializing extension XVideo
[    57.168] (II) Initializing extension XVideo-MotionCompensation
[    57.168] (II) Initializing extension GLX
crashes here

(gdb) target kvm netbsd.1.core  
_kvm_kvatop(0)
(gdb) bt
_kvm_kvatop(0)

So I am having to boot an earlier kernel off of a thumbdrive to
bring the box up from NetBSD 9.99.41 Thu Jan 23 13:54:41 EST 2020
Still has the freeze that looks like a uvm issue.

This is what normally follows Initializing extension GLX :

[    75.828] (II) AIGLX: Loaded and initialized r600 
[    75.828] (II) GLX: Initialized DRI2 GL provider for screen 0
[    75.828] (II) Initializing extension XFree86-VidModeExtension
[    75.829] (II) Initializing extension XFree86-DGA
[    75.829] (II) Initializing extension XFree86-DRI
[    75.829] (II) Initializing extension DRI2
[    75.881] (II) RADEON(0): Setting screen physical size to 1016 x 317
[    75.881] (II) RADEON(0): Allocate new frame buffer 3840x1200
[    75.926] (II) RADEON(0): VRAM usage limit set to 1858971K
[    78.235] (II) Using input driver 'mouse' for 'Mouse0'
[    78.235] (**) Option "CorePointer"
[    78.235] (**) Mouse0: always reports core events
[    78.277] (**) Option "Protocol" "wsmouse" 
[    78.277] (**) Option "Device" "/dev/wsmouse" 
[    78.277] (**) Mouse0: Protocol: "wsmouse"
[    78.277] (**) Mouse0: always reports core events
[    78.278] (==) Mouse0: Emulate3Buttons, Emulate3Timeout: 50
[    78.278] (**) Option "ZAxisMapping" "4 5 6 7"
[    78.278] (**) Mouse0: ZAxisMapping: buttons 4, 5, 6 and 7
[    78.278] (**) Mouse0: Buttons: 11
[    78.278] (II) XINPUT: Adding extended input device "Mouse0" (type: MOUSE, id
[    78.278] (**) Mouse0: (accel) keeping acceleration scheme 1
[    78.278] (**) Mouse0: (accel) acceleration profile 0
[    78.278] (**) Mouse0: (accel) acceleration factor: 2.000
[    78.278] (**) Mouse0: (accel) acceleration threshold: 4
[    78.278] (II) Using input driver 'kbd' for 'Keyboard0'
[    78.278] (**) Option "CoreKeyboard"
[    78.278] (**) Keyboard0: always reports core events
[    78.278] (**) Keyboard0: always reports core events
[    78.278] (**) Option "Protocol" "standard"
[    78.278] (**) Option "XkbRules" "base"
[    78.278] (**) Option "XkbModel" "pc105"
[    78.279] (**) Option "XkbLayout" "us"
[    78.279] (**) Option "XkbOptions" "ctrl:swapcaps"
[    78.279] (II) XINPUT: Adding extended input device "Keyboard0" (type: KEYBOA
[    92.114] (II) RADEON(0): Allocate new frame buffer 1920x1200
[    92.115] (II) RADEON(0): VRAM usage limit set to 1867071K
[    92.154] (II) RADEON(0): Allocate new frame buffer 3840x1200
[    92.159] (II) RADEON(0): VRAM usage limit set to 1858971K