From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Ian Jackson <ian.jackson@eu.citrix.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: Linux 3.18 and Linux 4.1 reproducible OOM crashes
Date: Thu, 14 Jul 2016 19:34:35 -0400 [thread overview]
Message-ID: <20160714233435.GA32434@localhost.localdomain> (raw)
In-Reply-To: <22407.35832.132931.105809@mariner.uk.xensource.com>
On Thu, Jul 14, 2016 at 01:56:24PM +0100, Ian Jackson wrote:
> osstest service owner writes ("[linux-3.18 test] 97278: regressions - FAIL"):
> > flight 97278 linux-3.18 real [real]
> > http://logs.test-lab.xenproject.org/osstest/logs/97278/
> >
> > Regressions :-(
> >
> > Tests which did not succeed and are blocking,
> > including tests which could not be run:
> ...
> > test-amd64-amd64-xl 6 xen-boot fail REGR. vs. 96188
>
> Loads of these. It seems it can't boot at all. Seems to affect amd64
> dom0 kernels but not i386 or armhf. (See flight 97279 for 4.1
> results.)
>
> It seems that the oom killer is tripping. Obviously something is
> seriously wrong.
>
> It seems likely that this is a real bug, but whether it's in Xen or
> Linux is not clear right now. If it's in Linux it's because a similar
> patch has been backported to both.
Yikes! Is the tool able to narrow down the bisect that causes this?
Thanks.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-07-14 23:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-14 5:03 [linux-3.18 test] 97278: regressions - FAIL osstest service owner
2016-07-14 12:56 ` Linux 3.18 and Linux 4.1 reproducible OOM crashes Ian Jackson
2016-07-14 23:34 ` Konrad Rzeszutek Wilk [this message]
2016-07-15 10:00 ` Ian Jackson
2016-07-18 11:17 ` Linux 3.18 and Linux 4.1 reproducible OOM crashes under Xen Ian Jackson
2016-07-18 11:25 ` Michal Hocko
2016-07-18 11:43 ` Odzioba, Lukasz
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=20160714233435.GA32434@localhost.localdomain \
--to=konrad.wilk@oracle.com \
--cc=ian.jackson@eu.citrix.com \
--cc=xen-devel@lists.xensource.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 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).