On Mon, May 6, 2019 at 2:35 PM Vlastimil Babka wrote:
>
> On 5/3/19 7:44 PM, Pankaj Suryawanshi wrote:
> >> First possibility that comes to mind is that a usermodehelper got
> >> launched, and
> >> it then tried to fork with a very large active process image. Do we have
> >> any
> >> clues
On 5/3/19 7:44 PM, Pankaj Suryawanshi wrote:
>> First possibility that comes to mind is that a usermodehelper got launched,
>> and
>> it then tried to fork with a very large active process image. Do we have any
>> clues what was going on? Did a device get hotplugged?
>
> Yes,The system is
On Thu, May 2, 2019 at 10:51 AM Valdis Klētnieks
wrote:
>
> On Thu, 02 May 2019 04:56:05 +0530, Pankaj Suryawanshi said:
>
> > Please help me to decode the error messages and reason for this errors.
>
> > [ 3205.818891] HwBinder:1894_6: page allocation failure: order:7,
> >
On Thu, 02 May 2019 04:56:05 +0530, Pankaj Suryawanshi said:
> Please help me to decode the error messages and reason for this errors.
> [ 3205.818891] HwBinder:1894_6: page allocation failure: order:7,
> mode:0x14040c0(GFP_KERNEL|__GFP_COMP), nodemask=(null)
Order 7 - so it wants 2**7
Hi All,
Please help me to decode the error messages and reason for this errors.
System Configuration
1. Kernel 4.14.65 For Android Pie.
2. RAM 2GB
As per my understanding its because of
i) I am out of memory or due to fragmentation.
I also tried to set /proc/sys/vm/min_freekbytes from 3MB to
