Re: 4.3+: Atheros ethernet fails after resume from s2ram, due to order 4 allocation

2015-11-28 Thread Pavel Machek
Hi! > > /* > > > > * real ring DMA buffer > > > > * each ring/block may need up to 8 bytes for alignment, hence the > > > > *

Re: 4.3+: Atheros ethernet fails after resume from s2ram, due to order 4 allocation

2015-11-27 Thread Michal Hocko
On Thu 26-11-15 17:34:13, Pavel Machek wrote: > Hi! > > ...and dmesg tells us what is going on: > > [ 6961.550240] NetworkManager: page allocation failure: order:4, > mode:0x2080020 This is GFP_ATOMIC|___GFP_RECLAIMABLE high order request. So something that the caller should tollerate to fail.

Re: 4.3+: Atheros ethernet fails after resume from s2ram, due to order 4 allocation

2015-11-26 Thread Francois Romieu
Pavel Machek : [...] > Ok, so what went on is easy.. any ideas how to fix it ? The driver should 1) prohibit holes in its receive ring, 2) allocate before pushing data up in the stack 3) drop packets when it can't allocate a fresh buffer and 4) stop releasing receive buffers - and

4.3+: Atheros ethernet fails after resume from s2ram, due to order 4 allocation

2015-11-26 Thread Pavel Machek
Hi! ...and dmesg tells us what is going on: [ 6961.550240] NetworkManager: page allocation failure: order:4, mode:0x2080020 [ 6961.550249] CPU: 0 PID: 2590 Comm: NetworkManager Tainted: G W 4.3.0+ #124 [ 6961.550250] Hardware name: Acer Aspire 5732Z/Aspire 5732Z, BIOS V3.07 02/10/2010 [