From: "Steve Wise" <swise@opengridcomputing.com>
To: "'nborisov'" <n.borisov.lkml@gmail.com>, <linux-kernel@vger.kernel.org>
Subject: RE: vmcore not getting created on linux-4.7
Date: Thu, 14 Jul 2016 14:19:39 -0500 [thread overview]
Message-ID: <02cc01d1de04$aaaaf0e0$0000d2a0$@opengridcomputing.com> (raw)
In-Reply-To: <00ca01d1dc58$52f00730$f8d01590$@opengridcomputing.com>
> >
> > Updating to 1.6.0 of makedumpfile didn't help. :(
> >
>
> Does anyone else have suggestions on how to debug this? From my original
> post, the dump kernel just reboots and I'm not sure why. Where can I add
> printks to gather more info on why the dump kernel gives on on the dump?
Seems this issue was a bug in makedumpfile that is fixed with this commit:
commit 2c21d4656e8d3c2af2b1e14809d076941ae69e96
Author: Vitaly Kuznetsov <vkuznets@redhat.com>
Date: Fri Jun 17 18:41:26 2016 +0900
[PATCH v2] Support _count -> _refcount rename in struct page
_count member was renamed to _refcount in linux commit 0139aa7b7fa12
("mm: rename _count, field of the struct page, to _refcount") and this
broke makedumpfile. The reason for making the change was to find all users
accessing it directly and not through the recommended API. I tried
suggesting to revert the change but failed, I see no other choice than to
start supporting both _count and _refcount in makedumpfile.
Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.com>
I found this fix in the devel branch of
git://git.code.sf.net/p/makedumpfile/code.
I'm surprised others aren't seeing this? All 6 of my development systems stop
being able to get vmcore dumps with 4.7-rc...
Steve.
next prev parent reply other threads:[~2016-07-14 19:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-24 14:45 vmcore not getting created on linux-4.7 Steve Wise
2016-06-24 15:06 ` nborisov
2016-06-24 15:12 ` Steve Wise
2016-06-24 16:37 ` nborisov
2016-06-24 20:19 ` Steve Wise
[not found] ` <014e01d1ce55$aa4ba040$fee2e0c0$@opengridcomputing.com>
2016-07-12 16:13 ` Steve Wise
[not found] ` <00ca01d1dc58$52f00730$f8d01590$@opengridcomputing.com>
2016-07-14 19:19 ` Steve Wise [this message]
[not found] ` <00b501d1ce2a$cad610f0$608232d0$@opengridcomputing.com>
2016-06-24 16:37 ` Steve Wise
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='02cc01d1de04$aaaaf0e0$0000d2a0$@opengridcomputing.com' \
--to=swise@opengridcomputing.com \
--cc=linux-kernel@vger.kernel.org \
--cc=n.borisov.lkml@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.