From: Michal Hocko <mhocko@kernel.org>
To: Fengguang Wu <fengguang.wu@intel.com>
Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>,
linux-kernel@vger.kernel.org, lkp@01.org
Subject: Re: [dummy_stm_init] swapper/0: page allocation failure: order:9, mode:0x14040c0(GFP_KERNEL|__GFP_COMP), nodemask=(null)
Date: Thu, 19 Apr 2018 08:51:11 +0200 [thread overview]
Message-ID: <20180419065111.GM17484@dhcp22.suse.cz> (raw)
In-Reply-To: <20180419023639.cddsueaq47mohfma@wfg-t540p.sh.intel.com>
On Thu 19-04-18 10:36:39, Wu Fengguang wrote:
> Hi Alexander,
>
> FYI this happens in mainline kernel 4.17.0-rc1.
> It dates back to at least v4.15.
>
> It occurs in 4 out of 4 boots. Here KVM has 1G memory.
>
> This high order allocation caused lots of noises in our boot testing.
> We could disable this device in our tests, but it would be great if
> there are better ways out.
>
> [ 75.039408] Product name: fake-design-for-testing
> [ 75.040995] fmc fake-design-for-testing-f001: Driver has no ID: matches all
> [ 75.042509] fmc_trivial: probe of fake-design-for-testing-f001 failed with error -95
> [ 75.044323] fmc fake-design-for-testing-f001: Driver has no ID: matches all
> [ 75.045644] fmc_chardev fake-design-for-testing-f001: Created misc device "fake-design-for-testing-f001"
> [ 75.061570] swapper/0: page allocation failure: order:9, mode:0x14040c0(GFP_KERNEL|__GFP_COMP), nodemask=(null)
Is there any reason why
> [ 75.063338] stm_register_device+0xf3/0x5c0:
> stm_register_device at drivers/hwtracing/stm/core.c:695
cannot use kvzalloc?
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2018-04-19 6:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-19 2:36 Fengguang Wu
2018-04-19 6:51 ` Michal Hocko [this message]
2018-04-19 9:57 ` Alexander Shishkin
2018-04-19 10:21 ` Kirill A. Shutemov
2018-04-22 13:44 ` Michal Hocko
2018-04-24 11:27 ` Kirill A. Shutemov
2018-04-25 14:51 ` Alexander Shishkin
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=20180419065111.GM17484@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.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
all inboxes | Powered by JetHome®