On Wed, Oct 23, 2019 at 8:46 AM Johannes Weiner wrote:
>
> On Wed, Oct 23, 2019 at 08:40:12AM +0200, Michal Hocko wrote:
> > On Tue 22-10-19 19:37:08, Johannes Weiner wrote:
> > > While upgrading from 4.16 to 5.2, we noticed these allocation errors
> > > in the log of the new kernel:
> > >
> > >
On Wed, Oct 23, 2019 at 08:40:12AM +0200, Michal Hocko wrote:
> On Tue 22-10-19 19:37:08, Johannes Weiner wrote:
> > While upgrading from 4.16 to 5.2, we noticed these allocation errors
> > in the log of the new kernel:
> >
> > [ 8642.253395] SLUB: Unable to allocate memory on node -1,
> >
On Tue 22-10-19 19:37:08, Johannes Weiner wrote:
> While upgrading from 4.16 to 5.2, we noticed these allocation errors
> in the log of the new kernel:
>
> [ 8642.253395] SLUB: Unable to allocate memory on node -1,
> gfp=0xa20(GFP_ATOMIC)
> [ 8642.269170] cache: tw_sock_TCPv6(960:helper-logs),
+Suleiman Souhlal
On Tue, Oct 22, 2019 at 4:37 PM Johannes Weiner wrote:
>
> While upgrading from 4.16 to 5.2, we noticed these allocation errors
> in the log of the new kernel:
>
> [ 8642.253395] SLUB: Unable to allocate memory on node -1,
> gfp=0xa20(GFP_ATOMIC)
> [ 8642.269170] cache:
While upgrading from 4.16 to 5.2, we noticed these allocation errors
in the log of the new kernel:
[ 8642.253395] SLUB: Unable to allocate memory on node -1, gfp=0xa20(GFP_ATOMIC)
[ 8642.269170] cache: tw_sock_TCPv6(960:helper-logs), object size: 232,
buffer size: 240, default order: 1, min
5 matches
Mail list logo