From: "Odzioba, Lukasz" <lukasz.odzioba@intel.com>
To: Dashi DS1 Cao <caods1@lenovo.com>
Cc: "'linux-x86_64@vger.kernel.org'" <linux-x86_64@vger.kernel.org>,
"'linux-numa@vger.kernel.org'" <linux-numa@vger.kernel.org>
Subject: RE: Kernel crashes in __migration_entry_wait
Date: Mon, 14 Nov 2016 11:19:49 +0000 [thread overview]
Message-ID: <D6EDEBF1F91015459DB866AC4EE162CC024B80D7@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <23B7B563BA4E9446B962B142C86EF24A3DCF87@CNMAILEX03.lenovo.com>
On Sunday, November 13, 2016 1:40 PM Dashi Cao wrote:
> A X86_64 server repeatedly dumps once a while with the following signature:
> (snip)
>
> KERNEL: vmlinux
> DUMPFILE: 127.0.0.1-2016-10-03-09:59:36/vmcore [PARTIAL DUMP]
> CPUS: 32
> DATE: Mon Oct 3 10:13:22 2016
> UPTIME: 4 days, 17:04:52
> LOAD AVERAGE: 0.49, 0.26, 0.24
> TASKS: 657
> NODENAME: node04-priv
> RELEASE: 3.10.0-327.el7.x86_64
> (snip)
>
> It seems that this is a bug. I'm not sure if it has been identified and removed, but it cannot be found on the web. The customer was adviced to disable numa balancing to work around and I'm waiting for the latest results from them.
Hi Dashi,
Thank you for your report ,but this seems to be kernel from RedHat 7.2 not our latest one nor stable, so I am not sure how many people here may be interested in your issue. If you don't get answer you can talk to RH support. Also this kernel is not the latest available for 7.2 so you may just try to update it.
Thanks,
Lukas
next prev parent reply other threads:[~2016-11-14 11:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-13 12:39 Kernel crashes in __migration_entry_wait Dashi DS1 Cao
2016-11-14 11:19 ` Odzioba, Lukasz [this message]
2016-11-28 12:46 ` Dashi DS1 Cao
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=D6EDEBF1F91015459DB866AC4EE162CC024B80D7@IRSMSX103.ger.corp.intel.com \
--to=lukasz.odzioba@intel.com \
--cc=caods1@lenovo.com \
--cc=linux-numa@vger.kernel.org \
--cc=linux-x86_64@vger.kernel.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 read-only IMAP folder(s) and NNTP newsgroup(s).