From: Guenter Roeck <linux@roeck-us.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
Sabrina Dubroca <sd@queasysnail.net>
Subject: Re: linux-next: Tree for Feb 13 (runtime failures and 'non-zero nr_pmds' messages)
Date: Fri, 13 Feb 2015 20:45:40 -0800 [thread overview]
Message-ID: <54DED2F4.50009@roeck-us.net> (raw)
In-Reply-To: <20150214103734.3052cd2f@canb.auug.org.au>
Hi Stephen,
On 02/13/2015 03:37 PM, Stephen Rothwell wrote:
> Hi Guenter,
>
> On Fri, 13 Feb 2015 10:54:28 -0800 Guenter Roeck <linux@roeck-us.net> wrote:
>>
>> I see a number of runtime failures with this version.
>> It affects alpha, mips64, ppc64, and x86_64.
>> Symptom is always the same. There are lots of
>>
>> BUG: non-zero nr_pmds on freeing mm: X (where X is 1..4)
>>
>> messages in the log, and the affected VMs don't reboot.
>>
>> I don't see the problem in curent mainline, nor in mmotm.
>> Bisect points to "Merge branch 'akpm-current/current'",
>> which isn't really helpful.
>>
>> Not sure if this is a bad merge resolution, so just take this
>> as a heads-up for now.
>
> Yours is the second report overnight (see attached). Almost certainly
> a bad merge resolution on my part (its a bit hard when Andrew get part
> of his patch set merged by Linus :-()
>
And now Fengguang's tests caught it as well.
> I will fix up the merge on Monday (unless Andrew gets more stuff merged
> or updates mmotm for me).
>
> Sorry about that.
>
No worries. Good news is that test coverage is getting better.
Guenter
next prev parent reply other threads:[~2015-02-14 4:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-13 5:56 linux-next: Tree for Feb 13 Stephen Rothwell
2015-02-13 11:03 ` Sabrina Dubroca
2015-02-13 18:18 ` linux-next: Tree for Feb 13 (nfsd) Randy Dunlap
2015-02-13 18:54 ` linux-next: Tree for Feb 13 (runtime failures and 'non-zero nr_pmds' messages) Guenter Roeck
2015-02-13 23:37 ` Stephen Rothwell
2015-02-14 4:45 ` Guenter Roeck [this message]
2015-02-14 0:32 ` linux-next: Tree for Feb 13 (iio/magnetometer/ak8975.c) Randy Dunlap
2015-02-14 0:32 ` Randy Dunlap
2015-02-14 0:34 ` Randy Dunlap
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=54DED2F4.50009@roeck-us.net \
--to=linux@roeck-us.net \
--cc=akpm@linux-foundation.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sd@queasysnail.net \
--cc=sfr@canb.auug.org.au \
/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.