Re: OOM in v4.8

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed 12-10-16 16:24:47, Aaron Lu wrote:
> On 10/12/2016 04:00 PM, Michal Hocko wrote:
[...]
> > which is an atomic high order request that failed which is not all that
> > unexpected when the system is low on memory. The allocation failure
> > report is hard to read because of unexpected end-of-lines but I suspect
> 
> Sorry about that, I'll try to find out why dmesg is saved so ugly on
> that test box.

Not your fault. This seems to be 4bcc595ccd80 ("printk: reinstate
KERN_CONT for printing continuation lines")

> > that again we are not able to allocate because of the CMA standing in
> > the way. I wouldn't call the above failure critical though.
>  
> I'll test that commit and v4.8 again with cma=0 added to cmdline.

Thanks!

-- 
Michal Hocko
SUSE Labs

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@xxxxxxxxx.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>



[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]