Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1577810 > unrolled thread

Alpha Kernel Regression [was Re: BRSGP relocation truncations in linking kernel for Alpha.]

Started byMichael Cree <mcree@orcon.net.nz>
First post2017-02-09 18:30 +0100
Last post2017-02-09 18:30 +0100
Articles 1 — 1 participant

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Alpha Kernel Regression [was Re: BRSGP relocation truncations in  linking kernel for Alpha.] Michael Cree <mcree@orcon.net.nz> - 2017-02-09 18:30 +0100

#1577810 — Alpha Kernel Regression [was Re: BRSGP relocation truncations in linking kernel for Alpha.]

FromMichael Cree <mcree@orcon.net.nz>
Date2017-02-09 18:30 +0100
SubjectAlpha Kernel Regression [was Re: BRSGP relocation truncations in linking kernel for Alpha.]
Message-ID<t90HD-yG-5@gated-at.bofh.it>
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.

[toc] | [standalone]


Back to top | Article view | linux.kernel


csiph-web