bus_dmamap_unload and interrupt priority

2017-10-19 Thread Mouse
Is the current IPL any part of bus_dmamap_unload()'s interface contract? Has it ever been? I'm trying to track down a crash and it looks to me as though it's happening inside bus_dmamap_unload, and the nature of the crash leads me to suspect it's priority-level related: it's the "should be able

Re: Deadlock on fragmented memory?

2017-10-19 Thread Chuck Silvers
On Thu, Oct 19, 2017 at 03:18:44PM +, Taylor R Campbell wrote: > > Date: Thu, 19 Oct 2017 14:49:24 + > > From: Taylor R Campbell > > > > Attached is a patch that attempts to restore the original behaviour of > > carving out enough KVA on boot, by

Re: Deadlock on fragmented memory?

2017-10-19 Thread Taylor R Campbell
> Date: Thu, 19 Oct 2017 09:57:02 +0200 > From: Martin Husemann > > I sometimes see my shark (arm v4, strongarm 110, 96 MB of ram, main > characteristics: very *slow* disk access) "hang" with many processes > blocked on "vmem". All of etc.daily is hit by that, lots of cron

Re: Adding a flag to sysctl_createv() to silence ARM warnings

2017-10-19 Thread Christos Zoulas
In article <20171019102654.gh16...@mail.duskware.de>, Martin Husemann wrote: >-=-=-=-=-=- > >Hey folks, > >at startup all arm machines show a warning: > >total memory = 512 MB >avail memory = 495 MB >sysctl_createv: sysctl_create(machine_arch) returned 17 >timecounter:

Adding a flag to sysctl_createv() to silence ARM warnings

2017-10-19 Thread Martin Husemann
Hey folks, at startup all arm machines show a warning: total memory = 512 MB avail memory = 495 MB sysctl_createv: sysctl_create(machine_arch) returned 17 timecounter: Timecounters tick every 10.000 msec This is because sys/arach/arm/arm32/arm32_machdep.c creates the hw.machine_arch sysctl

Re: Deadlock on fragmented memory?

2017-10-19 Thread Manuel Bouyer
On Thu, Oct 19, 2017 at 10:29:47AM +0200, Martin Husemann wrote: > On Thu, Oct 19, 2017 at 10:18:28AM +0200, Manuel Bouyer wrote: > > the key factor. From what I've seen it's virtual memory which is fragmented > > too much, not physical memory. There is plenty of free space in the vmem, > > but >

Re: Deadlock on fragmented memory?

2017-10-19 Thread Martin Husemann
On Thu, Oct 19, 2017 at 10:18:28AM +0200, Manuel Bouyer wrote: > the key factor. From what I've seen it's virtual memory which is fragmented > too much, not physical memory. There is plenty of free space in the vmem, but > no chunk is big enough (from memory, hung processes are waiting for a 256kb

Re: Deadlock on fragmented memory?

2017-10-19 Thread Manuel Bouyer
On Thu, Oct 19, 2017 at 09:57:02AM +0200, Martin Husemann wrote: > Hey folks, > > I sometimes see my shark (arm v4, strongarm 110, 96 MB of ram, main > characteristics: very *slow* disk access) "hang" with many processes > blocked on "vmem". All of etc.daily is hit by that, lots of cron

Deadlock on fragmented memory?

2017-10-19 Thread Martin Husemann
Hey folks, I sometimes see my shark (arm v4, strongarm 110, 96 MB of ram, main characteristics: very *slow* disk access) "hang" with many processes blocked on "vmem". All of etc.daily is hit by that, lots of cron instances, and no new exec(2) work (or so it seems). Various suggestions have been