From: smoch@web.de (Sören Moch)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2 1/4] arm: mvebu: increase atomic coherent pool size for armada 370/XP
Date: Tue, 06 Nov 2012 22:28:45 +0100 [thread overview]
Message-ID: <5099810D.9040902@web.de> (raw)
resent as plain text, sorry.
> For Armada 370/XP we have the same problem that for the commit
> cb01b63, so we applied the same solution: "The default 256 KiB
> coherent pool may be too small for some of the Kirkwood devices, so
> increase it to make sure that devices will be able to allocate their
> buffers with GFP_ATOMIC flag"
I see a regression from linux-3.5 to linux-3.6 and think there might be
a fundamental problem
with this patch. On my Kirkwood system (guruplug server plus) with
linux-3.6.2 I see following
errors and corresponding malfunction even with further increased (2M,
4M) pool size:
Oct 19 00:41:22 guru kernel: ERROR: 4096 KiB atomic DMA coherent pool is
too small!
Oct 19 00:41:22 guru kernel: Please increase it with coherent_pool=
kernel parameter!
So I had to downgrade to linux-3.5 which is running without problems.
I use SATA and several DVB sticks (em28xx / drxk and dib0700).
I already sent this bug report to m.szyprowski and
gregory.clementearlier, but
Sebastian suggested to send it to the mailing list and the responsible
maintainers, too.
Please write to my e-mail directly if you have further questions or
patches for me to test.
Regards,
Soeren
next reply other threads:[~2012-11-06 21:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-06 21:28 Sören Moch [this message]
2012-11-06 22:32 ` [PATCH V2 1/4] arm: mvebu: increase atomic coherent pool size for armada 370/XP Andrew Lunn
2012-11-06 22:55 ` Sebastian Hesselbarth
2012-11-06 23:07 ` Sören Moch
-- strict thread matches above, loose matches on Subject: below --
2012-10-26 12:30 [PATCH V2 0/4] Adding SATA support for Armada 370/XP Gregory CLEMENT
2012-10-26 12:30 ` [PATCH V2 1/4] arm: mvebu: increase atomic coherent pool size for armada 370/XP Gregory CLEMENT
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=5099810D.9040902@web.de \
--to=smoch@web.de \
--cc=linux-arm-kernel@lists.infradead.org \
/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).