netdev - RE: kernel 3.1.1 message: <IRQ> warn_alloc

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 13 Dec 2011 11:42:13 -0600
From:	Rajesh Borundia <rajesh.borundia@...gic.com>
To:	"starlight@...nacle.cx" <starlight@...nacle.cx>,
	Stephen Hemminger <shemminger@...tta.com>,
	Sony Chacko <sony.chacko@...gic.com>
CC:	linux-kernel <linux-kernel@...r.kernel.org>,
	netdev <netdev@...r.kernel.org>
Subject: RE: kernel 3.1.1 message:  <IRQ> warn_alloc_failed

Hi All,

Sorry for late reply.

Stephan,
Thanks for analyzing.

Yes, the netxen adapter does not support fragmented page memory.
They are not harmful messages. At that instant of time it may fail allocating
memory for some buffers in the ring but after enough memory is available
it will try to allocate memory for unallocated buffers in ring.

Or the other option could be to turn LRO off.

Rajesh  

________________________________________
From: starlight@...nacle.cx [starlight@...nacle.cx]
Sent: Friday, December 09, 2011 11:33 PM
To: Stephen Hemminger; Sony Chacko; Rajesh Borundia
Cc: linux-kernel; netdev
Subject: Re: kernel 3.1.1 message:  <IRQ> warn_alloc_failed

At 09:50 AM 12/9/2011 -0800, Stephen Hemminger wrote:
>On Thu, 08 Dec 2011 21:10:02 -0500 starlight@...nacle.cx wrote:
>
>You are seeing memory allocation failures because device
>is allocating a 16K (order 2) size socket buffer. You are using
>netxen device, and it looks like the problem.
>
>>From reading the netxen driver source. The LRO buffers
>in this device are very large (8060+skb overhead).
>Until the driver is fixed to use fragmented page size memory,
>I recommend turning off LRO.

Thank you for the analysis.  As an alternative
would it make sense to double or quadruple

    /proc/sys/vm/min_free_kbytes

or perhaps do the same for

    /proc/slabinfo(size-16384)

or both?



--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html