RPI3 swap experiments

Mark Millard marklmi at yahoo.com
Thu Aug 2 01:30:12 UTC 2018


On 2018-Aug-1, at 5:04 PM, bob prohaska <fbsd at www.zefox.net> wrote:

> On Wed, Aug 01, 2018 at 05:01:23AM +0100, Jamie Landeg-Jones wrote:
>> bob prohaska <fbsd at www.zefox.net> wrote:
>> 
>>> The significance of those lines isn't totally lost on me, but 
>>> it's not obvious how to apply them. Any guidance appreciated! 
>> 
>> Hi Bob.
>> Save the patch file somewhere, e.g. /tmp/patch then:
>> 
>> cd /usr/src/sys/vm
>> patch -l < /tmp/patch
>> cd /usr/src
>> 
>> remake the kernel, and reboot!
>> cheers, Jamie
> 
> That works like a charm, the new kernel is (re)building world now. 
> So far the only surprise is that top quit with a segfault, which 
> hasn't happened in a very long time. Buildworld seems undisturbed,
> the gstat script is still running. 
> 
> Where will the output go?  Serial console?

What I originally wrote indicates that dmesg would get the output:

QUOTE
In that thread is the message:

https://lists.freebsd.org/pipermail/freebsd-current/2018-June/069835.html

that has a patch for dumping out more information to demsg before
it does the kill
END QUOTE

(More accurately: the output goes to where dmseg gets what
it reports. I tend to use dmesg -a .)

The original Mark Johnston message said:

QUOTE
The patch below prints a few stats to the dmesg before
the kill. The output of that together with "sysctl vm" output should be
enough to determine what's happening.
END QUOTE

===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)



More information about the freebsd-arm mailing list