Re: OOMA kill with vm.pfault_oom_attempts="-1" on RPi3 at r357147 (a vm_pfault_oom_attempts < 0 handling bug as of head -r357026)

2020-01-28 Thread Mark Millard
[I recommend not sending kib our other exchanges: that he has been notified is enough. I also sent the material to 2 folks that I forgot at the time and replied to one more related message with the information. For most of these folks our general exchange is likely viewed as noise after then basic,

Re: OOMA kill with vm.pfault_oom_attempts="-1" on RPi3 at r357147 (a vm_pfault_oom_attempts < 0 handling bug as of head -r357026)

2020-01-28 Thread bob prohaska
On Tue, Jan 28, 2020 at 11:28:14AM -0800, Mark Millard wrote: > > > On 2020-Jan-28, at 11:02, bob prohaska wrote: > > > On Tue, Jan 28, 2020 at 09:42:17AM -0800, Mark Millard wrote: > >> > >> > >> > > The (partly)modified kernel compiled and booted without > > obvious trouble. It's trying to

Re: OOMA kill with vm.pfault_oom_attempts="-1" on RPi3 at r357147 (a vm_pfault_oom_attempts < 0 handling bug as of head -r357026)

2020-01-28 Thread Mark Millard
On 2020-Jan-28, at 11:02, bob prohaska wrote: > On Tue, Jan 28, 2020 at 09:42:17AM -0800, Mark Millard wrote: >> >> >> > The (partly)modified kernel compiled and booted without > obvious trouble. It's trying to finish buildworld now. > >> If you are testing with vm.pfault_oom_attempts="-1"

Re: OOMA kill with vm.pfault_oom_attempts="-1" on RPi3 at r357147

2020-01-28 Thread Mark Millard
On 2020-Jan-27, at 21:29, Mark Millard wrote: > On 2020-Jan-27, at 19:53, bob prohaska wrote: > >> On Mon, Jan 27, 2020 at 06:22:20PM -0800, Mark Millard wrote: >>> >>> So far as I know, in the past progress was only made when someone >>> already knowledgable got involved in isolating what was

Re: OOMA kill with vm.pfault_oom_attempts="-1" on RPi3 at r357147

2020-01-27 Thread Mark Millard
On 2020-Jan-27, at 19:53, bob prohaska wrote: > On Mon, Jan 27, 2020 at 06:22:20PM -0800, Mark Millard wrote: >> >> So far as I know, in the past progress was only made when someone >> already knowledgable got involved in isolating what was happening >> and how to control it. >> > Indeed. One c

Re: OOMA kill with vm.pfault_oom_attempts="-1" on RPi3 at r357147

2020-01-27 Thread bob prohaska
On Mon, Jan 27, 2020 at 06:22:20PM -0800, Mark Millard wrote: > > So far as I know, in the past progress was only made when someone > already knowledgable got involved in isolating what was happening > and how to control it. > Indeed. One can only hope said knowledgeables are reading Thanks