From: Pavel Machek <pavel@ucw.cz>
To: kernel list <linux-kernel@vger.kernel.org>,
jcliburn@gmail.com, chris.snook@gmail.com,
netdev@vger.kernel.org, "Rafael J. Wysocki" <rjw@rjwysocki.net>,
linux-mm@kvack.org, nic-devel@qualcomm.com
Cc: ronangeles@gmail.com, ebiederm@xmission.com
Subject: 4.3+: Atheros ethernet fails after resume from s2ram, due to order 4 allocation
Date: Thu, 26 Nov 2015 17:34:13 +0100 [thread overview]
Message-ID: <20151126163413.GA3816@amd> (raw)
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
[ 6961.550252] 00000000 00000000 f2ad1a04 c42ba5b8 00000000 f2ad1a2c
c40d650a c4d3ee1c
[ 6961.550260] f34ef600 00000004 02080020 c4eeef40 00000000 00000010
00000000 f2ad1ac8
[ 6961.550266] c40d8caa 02080020 00000004 00000000 00000070 f34ef200
00000060 00000010
[ 6961.550272] Call Trace:
...[ 6961.550299] [<c4006811>] dma_generic_alloc_coherent+0x71/0x120
[ 6961.550301] [<c40067a0>] ? via_no_dac+0x30/0x30
[ 6961.550307] [<c465b16e>] atl1c_open+0x29e/0x300
[ 6961.550313] [<c48b96f5>] ? call_netdevice_notifiers_info+0x25/0x50
[ 6961.550316] [<c48c081b>] __dev_open+0x7b/0xf0
[ 6961.550318] [<c48c0ac9>] __dev_change_flags+0x89/0x140
[ 6961.550320] [<c48c0ba3>] dev_change_flags+0x23/0x60
[ 6961.550325] [<c48ce416>] do_setlink+0x286/0x7b0
[ 6961.550328] [<c42ded02>] ? nla_parse+0x22/0xd0
[ 6961.550330] [<c48cf906>] rtnl_newlink+0x5d6/0x860
[ 6961.550336] [<c407f8a1>] ? __lock_acquire.isra.24+0x3a1/0xc80
[ 6961.550342] [<c4047ae2>] ? ns_capable+0x22/0x60
[ 6961.550345] [<c48e7c5d>] ? __netlink_ns_capable+0x2d/0x40
[ 6961.550351] [<c49c9c54>] ? xprt_transmit+0x94/0x220
[ 6961.550354] [<c48cd9e6>] rtnetlink_rcv_msg+0x76/0x1f0
[ 6961.550356] [<c48cd970>] ? rtnetlink_rcv+0x30/0x30
[ 6961.550359] [<c48eb35e>] netlink_rcv_skb+0x8e/0xb0
...
[ 6961.550412] Mem-Info:
[ 6961.550417] active_anon:30319 inactive_anon:25075 isolated_anon:0
active_file:327764 inactive_file:152179 isolated_file:16
unevictable:0 dirty:6 writeback:0 unstable:0
slab_reclaimable:149091 slab_unreclaimable:18973
mapped:18100 shmem:4847 pagetables:1538 bounce:0
free:57732 free_pcp:10 free_cma:0
...
[ 6961.550492] 485897 total pagecache pages
[ 6961.550494] 1086 pages in swap cache
[ 6961.550496] Swap cache stats: add 16738, delete 15652, find
6708/8500
[ 6961.550497] Free swap = 1656440kB
[ 6961.550498] Total swap = 1681428kB
[ 6961.550499] 785914 pages RAM
[ 6961.550500] 557663 pages HighMem/MovableOnly
[ 6961.550501] 12639 pages reserved
[ 6961.550506] atl1c 0000:05:00.0: pci_alloc_consistend failed
[ 6962.148358] psmouse serio1: synaptics: queried max coordinates: x
[..5772], y [..5086]
Order 4 allocation... probably doable during boot, but not really
suitable during resume.
I'm not sure how repeatable it is, but it definitely happened more
than once.
/*
* real ring DMA buffer
* each ring/block may need up to 8 bytes for alignment, hence the
* additional bytes tacked onto the end.
*/
ring_header->size = size =
sizeof(struct atl1c_tpd_desc) * tpd_ring->count * 2 +
sizeof(struct atl1c_rx_free_desc) * rx_desc_count +
sizeof(struct atl1c_recv_ret_status) * rx_desc_count +
8 * 4;
ring_header->desc = pci_alloc_consistent(pdev, ring_header->size,
&ring_header->dma);
if (unlikely(!ring_header->desc)) {
dev_err(&pdev->dev, "pci_alloc_consistend failed\n");
goto err_nomem;
}
(Note the typo in dev_err... at least it is easy to grep).
Ok, so what went on is easy.. any ideas how to fix it?
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2015-11-26 16:34 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-26 16:34 Pavel Machek [this message]
2015-11-26 21:56 ` 4.3+: Atheros ethernet fails after resume from s2ram, due to order 4 allocation Francois Romieu
2015-11-27 8:20 ` Michal Hocko
2015-11-28 14:50 ` Pavel Machek
2015-11-28 14:51 ` [PATCH] Improve Atheros ethernet driver not to do order 4 GFP_ATOMIC allocation Pavel Machek
2015-11-29 21:58 ` Sergei Shtylyov
2015-11-30 13:21 ` Michal Hocko
2015-12-01 20:35 ` David Miller
2015-12-02 22:43 ` Chris Snook
2015-12-03 7:49 ` Pavel Machek
2015-12-03 8:16 ` Michal Hocko
2015-12-03 19:26 ` Chris Snook
2015-11-30 17:58 ` Eric Dumazet
2015-12-01 20:36 ` David Miller
2015-12-03 15:59 ` Pavel Machek
2015-12-03 15:59 ` [PATCH net] atl1c: Improve " Pavel Machek
2015-12-03 16:13 ` Michal Hocko
2015-12-03 17:17 ` Eric Dumazet
2015-12-03 17:32 ` David Miller
2015-12-04 8:11 ` Pavel Machek
2015-12-04 16:21 ` David Miller
2015-12-04 21:30 ` Pavel Machek
2015-12-04 22:01 ` David Miller
2015-12-04 8:50 ` Pavel Machek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20151126163413.GA3816@amd \
--to=pavel@ucw.cz \
--cc=chris.snook@gmail.com \
--cc=ebiederm@xmission.com \
--cc=jcliburn@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=netdev@vger.kernel.org \
--cc=nic-devel@qualcomm.com \
--cc=rjw@rjwysocki.net \
--cc=ronangeles@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).