On 5/29/22 11:16, Mark Millard wrote:
FYI, the combination:
vm.pageout_oom_seq=120 # in /boot/loader.conf
vm.swap_enabled=0 # in /etc/sysctl.conf
vm.swap_idle_enabled=0 # in /etc/sysctl.conf
still has not caused me any additional problems
and helps avoid loss of access by avoiding the
On 2022-May-29, at 10:07, Pete Wright wrote:
> On 5/14/22 01:09, Mark Millard wrote:
>>
>> One of the points is to see if I get any evidence of
>> vm.swap_enabled=0 with vm.swap_idle_enabled=0 ending up
>> contributing to any problems in my normal usage. So far: no.
>> vm.pageout_oom_seq=120 is
On 5/14/22 01:09, Mark Millard wrote:
One of the points is to see if I get any evidence of
vm.swap_enabled=0 with vm.swap_idle_enabled=0 ending up
contributing to any problems in my normal usage. So far: no.
vm.pageout_oom_seq=120 is in use for this, my normal
context since sometime in 2018.
Pete Wright wrote on
Date: Fri, 13 May 2022 13:43:11 -0700 :
> On 5/11/22 12:52, Mark Millard wrote:
> >
> >
> > Relative to avoiding hang-ups, so far it seems that
> > use of vm.swap_enabled=0 with vm.swap_idle_enabled=0
> > makes hang-ups less likely/less frequent/harder to
> > produce
On 5/11/22 12:52, Mark Millard wrote:
Relative to avoiding hang-ups, so far it seems that
use of vm.swap_enabled=0 with vm.swap_idle_enabled=0
makes hang-ups less likely/less frequent/harder to
produce examples of. But is no guarantee of lack of
a hang-up. Its does change the cause of the
On 2022-May-10, at 20:31, Mark Millard wrote:
> On 2022-May-10, at 17:49, Mark Millard wrote:
>
>> On 2022-May-10, at 11:49, Mark Millard wrote:
>>
>>> On 2022-May-10, at 08:47, Jan Mikkelsen wrote:
>>>
On 10 May 2022, at 10:01, Mark Millard wrote:
>
> On 2022-Apr-29, at
On 2022-May-10, at 17:49, Mark Millard wrote:
> On 2022-May-10, at 11:49, Mark Millard wrote:
>
>> On 2022-May-10, at 08:47, Jan Mikkelsen wrote:
>>
>>> On 10 May 2022, at 10:01, Mark Millard wrote:
On 2022-Apr-29, at 13:57, Mark Millard wrote:
> On 2022-Apr-29, at
On 2022-May-10, at 11:49, Mark Millard wrote:
> On 2022-May-10, at 08:47, Jan Mikkelsen wrote:
>
>> On 10 May 2022, at 10:01, Mark Millard wrote:
>>>
>>> On 2022-Apr-29, at 13:57, Mark Millard wrote:
>>>
On 2022-Apr-29, at 13:41, Pete Wright wrote:
>
>> . . .
>
>
On 2022-May-10, at 08:47, Jan Mikkelsen wrote:
> On 10 May 2022, at 10:01, Mark Millard wrote:
>>
>> On 2022-Apr-29, at 13:57, Mark Millard wrote:
>>
>>> On 2022-Apr-29, at 13:41, Pete Wright wrote:
> . . .
d'oh - went out for lunch and workstation locked up. i *knew*
On 10 May 2022, at 10:01, Mark Millard wrote:
>
> On 2022-Apr-29, at 13:57, Mark Millard wrote:
>
>> On 2022-Apr-29, at 13:41, Pete Wright wrote:
>>>
. . .
>>>
>>> d'oh - went out for lunch and workstation locked up. i *knew* i shouldn't
>>> have said anything lol.
>>
>> Any
On 2022-Apr-29, at 13:57, Mark Millard wrote:
> On 2022-Apr-29, at 13:41, Pete Wright wrote:
>>
>>> . . .
>>
>> d'oh - went out for lunch and workstation locked up. i *knew* i shouldn't
>> have said anything lol.
>
> Any interesting console messages ( or dmesg -a or /var/log/messages )?
>
On 2022-Apr-29, at 13:41, Pete Wright wrote:
>
> On 4/29/22 11:38, Mark Millard wrote:
>> On 2022-Apr-29, at 11:08, Pete Wright wrote:
>>
>>> On 4/23/22 19:20, Pete Wright wrote:
> The developers handbook has a section debugging deadlocks that he
> referenced in a response to another
On 4/29/22 11:38, Mark Millard wrote:
On 2022-Apr-29, at 11:08, Pete Wright wrote:
On 4/23/22 19:20, Pete Wright wrote:
The developers handbook has a section debugging deadlocks that he
referenced in a response to another report (on freebsd-hackers).
On 2022-Apr-29, at 11:08, Pete Wright wrote:
> On 4/23/22 19:20, Pete Wright wrote:
>>
>>> The developers handbook has a section debugging deadlocks that he
>>> referenced in a response to another report (on freebsd-hackers).
>>>
>>>
On 4/23/22 19:20, Pete Wright wrote:
The developers handbook has a section debugging deadlocks that he
referenced in a response to another report (on freebsd-hackers).
https://docs.freebsd.org/en/books/developers-handbook/kerneldebug/#kerneldebug-deadlocks
d'oh - thanks for the
: Chasing OOM Issues - good sysctl metrics to use?
On 2022-Apr-23, at 10:26, Pete Wright
mailto:p...@nomadlogic.org>> wrote:
> On 4/22/22 18:46, Mark Millard wrote:
>> On 2022-Apr-22, at 16:42, Pete Wright
>> mailto:p...@nomadlogic.org>> wrote:
>>
&g
On 4/23/22 12:31, Mark Millard wrote:
I think you may have taken my suggestion backwards . . .
Unfortunately, vnode (file) based swap space should be *avoided*
and partitions are what should be used in order to avoid deadlocks:
On 2017-Feb-13, at 7:20 PM, Konstantin Belousov wrote
on the
On 2022-Apr-23, at 10:26, Pete Wright wrote:
> On 4/22/22 18:46, Mark Millard wrote:
>> On 2022-Apr-22, at 16:42, Pete Wright wrote:
>>
>>> On 4/21/22 21:18, Mark Millard wrote:
Messages in the console out would be appropriate
to report. Messages might also be available via
the
On 4/22/22 18:46, Mark Millard wrote:
On 2022-Apr-22, at 16:42, Pete Wright wrote:
On 4/21/22 21:18, Mark Millard wrote:
Messages in the console out would be appropriate
to report. Messages might also be available via
the following at appropriate times:
that is what is frustrating. i
On Fri, 22 Apr 2022 16:46:20 -0700, Pete Wright wrote:
>
>
> On 4/22/22 13:39, tech-lists wrote:
> > Hi,
> >
> > On Thu, Apr 21, 2022 at 07:16:42PM -0700, Pete Wright wrote:
> >> hello -
> >>
> >> on my workstation running CURRENT (amd64/32g of ram) i've been running
> >> into a scenario
On 2022-Apr-22, at 16:42, Pete Wright wrote:
> On 4/21/22 21:18, Mark Millard wrote:
>>
>> Messages in the console out would be appropriate
>> to report. Messages might also be available via
>> the following at appropriate times:
>
> that is what is frustrating. i will get notification that
On 4/22/22 13:39, tech-lists wrote:
Hi,
On Thu, Apr 21, 2022 at 07:16:42PM -0700, Pete Wright wrote:
hello -
on my workstation running CURRENT (amd64/32g of ram) i've been running
into a scenario where after 4 or 5 days of daily use I get an OOM event
and both chromium and firefox are
On 4/21/22 21:18, Mark Millard wrote:
Messages in the console out would be appropriate
to report. Messages might also be available via
the following at appropriate times:
that is what is frustrating. i will get notification that the processes
are killed:
Apr 22 09:55:15 topanga kernel:
Hi,
On Thu, Apr 21, 2022 at 07:16:42PM -0700, Pete Wright wrote:
hello -
on my workstation running CURRENT (amd64/32g of ram) i've been running
into a scenario where after 4 or 5 days of daily use I get an OOM event
and both chromium and firefox are killed. then in the next day or so
the
Pete Wright wrote on
Date: Thu, 21 Apr 2022 19:16:42 -0700 :
> on my workstation running CURRENT (amd64/32g of ram) i've been running
> into a scenario where after 4 or 5 days of daily use I get an OOM event
> and both chromium and firefox are killed. then in the next day or so
> the system
hello -
on my workstation running CURRENT (amd64/32g of ram) i've been running
into a scenario where after 4 or 5 days of daily use I get an OOM event
and both chromium and firefox are killed. then in the next day or so
the system will become very unresponsive in the morning when i unlock my
26 matches
Mail list logo
