From: Michael Cree <mcree@orcon.net.nz>
To: Richard Henderson <rth@twiddle.net>,
linux-alpha <linux-alpha@vger.kernel.org>,
Chen Feng <puck.chen@hisilicon.com>
Cc: Helge Deller <deller@gmx.de>, LKML <linux-kernel@vger.kernel.org>,
John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
Michael Karcher <debian@mkarcher.dialup.fu-berlin.de>
Subject: Alpha Kernel Regression [was Re: BRSGP relocation truncations in linking kernel for Alpha.]
Date: Thu, 9 Feb 2017 22:58:53 +1300 [thread overview]
Message-ID: <20170209095853.yjjuaajbzxofx7xu@tower> (raw)
In-Reply-To: <20161025082638.u7c5kpi2q3kr3kld@tower>
On Tue, Oct 25, 2016 at 09:26:38PM +1300, Michael Cree wrote:
> And while I mention libc I am seeing (rather rare) random segfaults
> in programs such as cp, tar, install and dpkg ever since the upgrade
> to glibc 2.23 (or maybe it was 2.24). I am struggling to get a
> backtrace because it only happens very occassionally (but often enough
> that it is almost impossible for a build and install of large software
> packages such as libreoffice to complete without failure at some
> random point) and when I rerun the failing program manually it then
> always works. I'll keep trying to narrow this one down.
It's not glibc. Downgrading to previously known working versions does
not solve the random segfaults. But downgrading the kernel does fix
the problem on Alpha. Noted that 4.6 is good but 4.6.7 is bad so
bisected the 4.6.y stable kernel branch to get the first bad commit as
0784672d05684de901fc2aa56150d7ea9a475a2d, i.e.:
commit 0784672d05684de901fc2aa56150d7ea9a475a2d
Author: Chen Feng <puck.chen@hisilicon.com>
Date: Fri May 20 16:59:02 2016 -0700
mm/compaction.c: fix zoneindex in kcompactd()
commit 6cd9dc3e75078ef646076fa63adfb9b85ced0b66 upstream.
While testing the kcompactd in my platform 3G MEM only DMA ZONE. I
found the kcompactd never wakeup. It seems the zoneindex has already
minus 1 before. So the traverse here should be <=.
It fixes a regression where kswapd could previously compact, but
kcompactd not. Not a crash fix though.
Cheers
Michael.
next prev parent reply other threads:[~2017-02-09 9:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-22 2:41 BRSGP relocation truncations in linking kernel for Alpha Michael Cree
2016-10-24 20:59 ` Helge Deller
2016-10-25 3:13 ` Richard Henderson
2016-10-25 8:26 ` Michael Cree
2016-10-25 16:58 ` Richard Henderson
2016-10-25 18:07 ` Richard Henderson
2016-10-26 6:56 ` Michael Cree
2016-10-26 15:18 ` Richard Henderson
2017-02-09 9:58 ` Michael Cree [this message]
2016-10-25 20:01 ` Thorsten Kranzkowski
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=20170209095853.yjjuaajbzxofx7xu@tower \
--to=mcree@orcon.net.nz \
--cc=debian@mkarcher.dialup.fu-berlin.de \
--cc=deller@gmx.de \
--cc=glaubitz@physik.fu-berlin.de \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=puck.chen@hisilicon.com \
--cc=rth@twiddle.net \
/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