You are probably haunted by a bad issue with DMA memory and running out of
it. Your top is missing -SH since then you would probably see the
pagedameon go bananas. The problem is you have not enough memory below 4G
but the pagedaemon is not able to properly free memory there since it has
no proper
On Thu, May 23, 2024 at 03:37:24PM +, James Cook wrote:
> On Thu, May 23, 2024 at 08:00:37AM GMT, Nick Holland wrote:
> > On 5/23/24 03:18, Stuart Henderson wrote:
> > > On 2024-05-22, James Cook wrote:
> > > > One of my OpenBSD boxes sometimes gets in a weird locked-up or
> > > > almost-locke
On Thu, May 23, 2024 at 08:00:37AM GMT, Nick Holland wrote:
On 5/23/24 03:18, Stuart Henderson wrote:
On 2024-05-22, James Cook wrote:
One of my OpenBSD boxes sometimes gets in a weird locked-up or
almost-locked-up state. I'm wondering what I can do to debug it
further next time it happens.
.
On 5/23/24 03:18, Stuart Henderson wrote:
On 2024-05-22, James Cook wrote:
One of my OpenBSD boxes sometimes gets in a weird locked-up or
almost-locked-up state. I'm wondering what I can do to debug it
further next time it happens.
...
I would also expect the cache number to be much higher. E
On 2024-05-22, James Cook wrote:
> One of my OpenBSD boxes sometimes gets in a weird locked-up or
> almost-locked-up state. I'm wondering what I can do to debug it
> further next time it happens.
...
> I would also expect the cache number to be much higher. E.g. on
> this occasion, I was running "
Hi,
One of my OpenBSD boxes sometimes gets in a weird locked-up or
almost-locked-up state. I'm wondering what I can do to debug it
further next time it happens.
It feels like swap thrashing, but top reports plenty of memory free.
Symptoms:
1. top reports lots of free memory, small act/tot and
6 matches
Mail list logo
