Re: [gentoo-user] Troubleshooting mounting local filesystems

[Daniel Frey]

On 01/21/18 11:15, Daniel Frey wrote:

On 12/31/17 08:28, Daniel Frey wrote:

On 12/31/17 06:12, Jalus Bilieyich wrote:

Did you perform this action:

rc-update add localmount default

?


On my machine (as per my other post) it's in the boot runlevel.

Dan


OK, after turning on some logging I figured out what's happening.

When localmount runs /dev/sdc has not been created yet. Presumably it is 
getting created after localmount runs.


I suspect that this is because there's a delay during kernel 
initialization that loads firmware for some TV tuners I have, and after 
this I can see that /dev/sdc is created.


So the question now is... is it safe to add a delay to localmount? Or is 
there a better way (like... can I tell the kernel to wait a few seconds 
before running init?)


As this is mounted twice (local access and nfs access) in fstab, it 
would be best to fix it before localmount runs.


Dan


OK, I found the rootdelay paramater but it didn't do what it needed 
(presumably because the root partition wasn't mounted so creating 
entries in /dev didn't happen any faster.)


I added the following three lines to add a delay:

# Delay to allow devices to register
einfo "Waiting for RAID devices to settle/register..."
sleep 25

I've rebooted a few times and it starts up correctly now. I don't really 
care if that PC starts in two seconds, I need it to start up 
consistently as it's acting as a server.


Dan

Re: [gentoo-user] kernel 4.9.77 error segfault in compile.

[Adam Carter]

On Tue, Jan 23, 2018 at 2:51 AM, Corbin Bird  wrote:

> Anyone else getting this error? ( kernel 4.9.77 )
>
> >   CC  fs/ext4/mballoc.o
> >   CC  fs/ext4/block_validity.o
> >   CC  fs/ext4/move_extent.o
> >   CC  fs/ext4/mmp.o
> >   CC  fs/ext4/indirect.o
> > fs/ext4/indirect.o: warning: objtool: ext4_clear_blocks()+0x242: can't
> > find jump dest instruction at .text+0x56c
> >   CC  fs/ext4/extents_status.o
> > /bin/sh: line 1: 31735 Segmentation fault  ./tools/objtool/objtool
> > check "fs/ext4/extents_status.o"
> > make[2]: *** [scripts/Makefile.build:294: fs/ext4/extents_status.o]
> > Error 139
> > make[1]: *** [scripts/Makefile.build:544: fs/ext4] Error 2
> > make: *** [Makefile:995: fs] Error 2
>
>
FYI, this is from 4.14.15's ChangeLog, doesn't appear to be in 4.9.78
though.

commit f41b2d7ee791e845147a3e3cafb25493dca6870a
Author: Josh Poimboeuf 
Date:   Mon Jan 15 08:17:07 2018 -0600

objtool: Fix seg fault with gold linker

commit 2a0098d70640dda192a79966c14d449e7a34d675 upstream.

Objtool segfaults when the gold linker is used with
CONFIG_MODVERSIONS=y and CONFIG_UNWINDER_ORC=y.

With CONFIG_MODVERSIONS=y, the .o file gets passed to the linker before
being passed to objtool.  The gold linker seems to strip unused ELF
symbols by default, which confuses objtool and causes the seg fault when
it's trying to generate ORC metadata.

Objtool should really be running immediately after GCC anyway, without a
linker call in between.  Change the makefile ordering so that objtool is
called before the linker.

Re: [gentoo-user] kernel 4.9.77 error segfault in compile.

[Rich Freeman]

On Tue, Jan 23, 2018 at 8:55 PM, Corbin Bird  wrote:
>
> So ... I ran 'make mrproper' in '/opt/compile/linux-4.9.77/'

If you're doing this right make mrproper won't do anything, since
you're not writing to the source tree anyway.

What happens when you build v4.9.76?  I would be useful to confirm
that it is in fact the .77 patches that cause the issue.  The next
step would be to maybe revert commit
3d16a1315add12386894e7dc7bc86454e4f4b79d.  If that doesn't do it I'd
just start bisecting between the two releases.


-- 
Rich

Re: [gentoo-user] kernel 4.9.77 error segfault in compile.

[Corbin Bird]

On 01/23/2018 11:35 AM, Rich Freeman wrote:
> Abandoning ext4 over retpolines/etc seems a bit drastic.  My guess is
> that there is a bug in the latest kernel that will get fixed, or maybe
> a bug in gcc (which needs to be patched for spectre anyway).
>
> These Spectre changes are being merged and it has been a real mess.
> The vulnerability is relatively serious so there is a lot of pressure
> to do something, but the changes aren't trivial so they could contain
> bugs or expose compiler bugs.
>
> FWIW upstream 4.9.77 builds just fine for me,
>
> If you want to mess with building alternate kernels to debug this here
> are some instructions I created for this:
>
> As a test you might consider the following:
>
> mkdir /someplace
> cd /someplace
> git clone -b linux-4.9.y
> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
> .
> mkdir /var/tmp/linux
> cp /path/to/config /var/tmp/linux/.config
> make O=/var/tmp/linux oldconfig
> make O=/var/tmp/linux -j#
>
> That will build the latest stable upstream kernel.
>
> Depending on what you find you can do:
> git checkout v4.9.76
> rm -r /var/tmp/linux
> mkdir /var/tmp/linux
> cp /path/to/config /var/tmp/linux/.config
> make O=/var/tmp/linux oldconfig
> make O=/var/tmp/linux -j#
>
> That will see if 4.9.76 fails.  You could also substitute any version
> you want (including a 4.14 kernel, or an earlier 4.9 kernel).  This
> will give you a sense of whether your toolchain is just entirely
> broken, or if there is an issue with the objtool changes.
>
> Note that you can build away as much as you want without having to
> install any of this - so it won't affect your system at all.  In fact,
> the instructions above will work just fine if you run them as
> non-root, as long as you clone the git sources and put the temp
> directory someplace your non-root user has access to.
>

Tried this ... and here are the steps followed and results :
Note :
CPU defined as K8, NO vendor support for Intel or Centaur, AMD only.
gcc && binutils are both current stable, both r1's. Tested and working.
Both Disabled in 'menuconfig' :
>  [ ] Avoid speculative indirect branches in kernel
>  [ ] Remove the kernel mapping in user mode
The steps followed :
-
mkdir /opt/compile
cd /opt/compile
git clone -b linux-4.9.y
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
renamed 'linux-stable' to 'linux-4.9.77'
ln -s /opt/compile/linux-4.9.77 linux
cd /opt/compile/linux
make menuconfig
mkdir /var/tmp/linux
cp /opt/compile/linux/.config /var/tmp/linux/.config
make O=/var/tmp/linux oldconfig
make O=/var/tmp/linux -j9
-
The results ( first pass ) :

>   HOSTCC  arch/x86/tools/relocs_64.o
>   HOSTCC  arch/x86/tools/relocs_common.o
>   Using /opt/compile/linux-4.9.77 as source for kernel
>   /opt/compile/linux-4.9.77 is not clean, please run 'make mrproper'
>   in the '/opt/compile/linux-4.9.77' directory.
> make[1]: *** [/opt/compile/linux-4.9.77/Makefile:1021: prepare3] Error 1
> make[1]: *** Waiting for unfinished jobs
>   HOSTLD  arch/x86/tools/relocs
> make[1]: Leaving directory '/var/tmp/linux'
> make: *** [Makefile:150: sub-make] Error 2

So ... I ran 'make mrproper' in '/opt/compile/linux-4.9.77/'
The result :

>   HOSTCC  arch/x86/tools/relocs_64.o
>   HOSTCC  arch/x86/tools/relocs_common.o
>   Using /opt/compile/linux-4.9.77 as source for kernel
>   /opt/compile/linux-4.9.77 is not clean, please run 'make mrproper'
>   in the '/opt/compile/linux-4.9.77' directory.
> make[1]: *** [/opt/compile/linux-4.9.77/Makefile:1021: prepare3] Error 1
> make[1]: *** Waiting for unfinished jobs
>   HOSTLD  arch/x86/tools/relocs
> make[1]: Leaving directory '/var/tmp/linux'
> make: *** [Makefile:150: sub-make] Error 2

Something is not right 
  HOSTCC  arch/x86/tools/relocs_64.o
  HOSTCC  arch/x86/tools/relocs_common.o
  HOSTLD  arch/x86/tools/relocs
Is this the 'Spectre/Meltdown' patches again?!?

Corbin

Re: [gentoo-user] kernel 4.9.77 error segfault in compile.

[Corbin Bird]

On 01/23/2018 11:59 AM, Wol's lists wrote:
> On 23/01/18 17:35, Rich Freeman wrote:
>>> Wonderful ... just finished a complete reload of Gentoo. Now have to
>>> redo it again ...
>>> ... the mistake? I used ext2/ext3 for the fs.
>>>
>> Abandoning ext4 over retpolines/etc seems a bit drastic.  My guess is
>> that there is a bug in the latest kernel that will get fixed, or maybe
>> a bug in gcc (which needs to be patched for spectre anyway).
>
> Did you use the ext2/ext3 driver? I believe it's been abandoned?
>
> The ext4 driver is compatible with 2/3 file systems, so as I
> understand it all development effort goes into the ext4 driver, and
> any problems with the older drivers is likely to be met with "upgrade
> your driver".
>
> So if you were using that driver, it could be suffering bit-rot.
>
> Cheers,
> Wol
>
Sometime back the kernel devs decided to 'remove' the ext2 / ext3 fs
drivers.
The ext2 / ext3 fs drivers are NOT available.
Any choice of ext2 / ext3 forces the use of the ext4 fs driver.
If I could use the real ext2 / ext3 fs drivers ...
... I would in the blink of an eye.

ext2 / ext3 are the definition of 'stable' file systems.
ext4  unstable, still in development, prone to breakage.

Corbin

Re: [gentoo-user] Questions about Pale Moon

[Walter Dnes]

On Tue, Jan 23, 2018 at 11:58:52AM +, Peter Humphrey wrote

> Q 1:  I've asked this before, but I can't find the reply. How can I arrange 
> for  to step through the open tabs, one at a time, from left to 
> right. Or is there another key combination to do that?

  From the Pale Moon FAQ...
https://www.palemoon.org/faq.shtml#Preference:_I_prefer_the_old_Ctrl-Tab

> If you don't like the graphical preview pane for switching between
> browser tabs, you can restore the method as also found in Firefox:
> In the address bar, type about:config and press enter. This
> opens the advanced configuration editor.  Find the parameter
> browser.ctrlTab.previews and set it to false

 
> Q 2:  What other package do I need installed to give me the navigation 
> symbols? I've attached a section of the window to show what I mean.

  First try x11-themes/hicolor-icon-theme and if that doesn't suffice
try adwaita-icon-theme (which pulls in x11-themes/hicolor-icon-theme).
Actually, you should already have them installed if you have gtk+(2 or
3).  Is this the official Pale Moon, or an unofficial build?

-- 
Walter Dnes 
I don't run "desktop environments"; I run useful applications

Re: [gentoo-user] kernel 4.9.77 error segfault in compile.

[Wol's lists]

On 23/01/18 17:35, Rich Freeman wrote:

Wonderful ... just finished a complete reload of Gentoo. Now have to
redo it again ...
... the mistake? I used ext2/ext3 for the fs.


Abandoning ext4 over retpolines/etc seems a bit drastic.  My guess is
that there is a bug in the latest kernel that will get fixed, or maybe
a bug in gcc (which needs to be patched for spectre anyway).


Did you use the ext2/ext3 driver? I believe it's been abandoned?

The ext4 driver is compatible with 2/3 file systems, so as I understand 
it all development effort goes into the ext4 driver, and any problems 
with the older drivers is likely to be met with "upgrade your driver".


So if you were using that driver, it could be suffering bit-rot.

Cheers,
Wol

Re: [gentoo-user] kernel 4.9.77 error segfault in compile.

[Rich Freeman]

On Tue, Jan 23, 2018 at 12:28 PM, Corbin Bird  wrote:
>
>
> FYI :
> Just tried a different compile.
> Switched off expert and flipped the CPU to "Generic x86_64" ( no other
> changes ).
>
> It compiled. ??
>
> So ... what you choose for CPU in the kernel determines if the
> ext2/ext3/ext4 fs driver will compile.
>
> Been using Gentoo / "sys-kernel/gentoo-sources" w/experimental for 3+
> years now.
> First time the CPU choice has caused a problem.
>
> Suspect that a mismatch of the "Spectre / Meltdown" patches that have
> somehow gotten into the ext4 fs driver and the code for specific CPUs.
>
> Wonderful ... just finished a complete reload of Gentoo. Now have to
> redo it again ...
> ... the mistake? I used ext2/ext3 for the fs.
>

Abandoning ext4 over retpolines/etc seems a bit drastic.  My guess is
that there is a bug in the latest kernel that will get fixed, or maybe
a bug in gcc (which needs to be patched for spectre anyway).

These Spectre changes are being merged and it has been a real mess.
The vulnerability is relatively serious so there is a lot of pressure
to do something, but the changes aren't trivial so they could contain
bugs or expose compiler bugs.

FWIW upstream 4.9.77 builds just fine for me,

If you want to mess with building alternate kernels to debug this here
are some instructions I created for this:

As a test you might consider the following:

mkdir /someplace
cd /someplace
git clone -b linux-4.9.y
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
.
mkdir /var/tmp/linux
cp /path/to/config /var/tmp/linux/.config
make O=/var/tmp/linux oldconfig
make O=/var/tmp/linux -j#

That will build the latest stable upstream kernel.

Depending on what you find you can do:
git checkout v4.9.76
rm -r /var/tmp/linux
mkdir /var/tmp/linux
cp /path/to/config /var/tmp/linux/.config
make O=/var/tmp/linux oldconfig
make O=/var/tmp/linux -j#

That will see if 4.9.76 fails.  You could also substitute any version
you want (including a 4.14 kernel, or an earlier 4.9 kernel).  This
will give you a sense of whether your toolchain is just entirely
broken, or if there is an issue with the objtool changes.

Note that you can build away as much as you want without having to
install any of this - so it won't affect your system at all.  In fact,
the instructions above will work just fine if you run them as
non-root, as long as you clone the git sources and put the temp
directory someplace your non-root user has access to.

-- 
Rich

Re: [gentoo-user] kernel 4.9.77 error segfault in compile.

[Rich Freeman]

On Mon, Jan 22, 2018 at 9:34 PM, Corbin Bird  wrote:
> On 01/22/2018 11:56 AM, Rich Freeman wrote:
>
> Tried both approaches ... the results :
>>
>> make distclean
>> make mrproper
>> --> copy over .config
>> make O=/var/tmp/linux modules_prepare
>> make O=/var/tmp/linux && make O=/var/tmp/linux modules_install

Two comments:

1. You don't need to run modules_prepare, unless you're just building
modules and not the rest of the kernel.
2. .config goes in /var/tmp/linux, not in /usr/src/linux.

It probably wouldn't hurt to wipe your sources and re-download them
instead of just running make mrproper (which won't fix modifications
made to source files).  If you're using git sources you could just do
a hard git reset, which would fix any files in the repo.

I'll comment on your later reply...

-- 
Rich

Re: [gentoo-user] kernel 4.9.77 error segfault in compile.

[Corbin Bird]

> The 4.9.77 announcement upstream did introduce a number of objtool
> changes. See below.
> https://lkml.org/lkml/2018/1/17/198
> Josh Poimboeuf (4):
>   objtool, modules: Discard objtool annotation sections for modules
>   objtool: Detect jumps to retpoline thunks
>   objtool: Allow alternatives to be ignored
>   objtool: Fix retpoline support for pre-ORC objtool
>
> I can't seem to remember seeing reports of the issue you're having on
> the LMKL, since 4.9.77 was announced.
> As you said, try re-emerging the gentoo kernel, make mrproper, no need
> for distclean, which does run mrproper as part of its operation, and
> see if that helps.
> Alternatively, you could try building the upstream version of 4.9.77,
> and see if that works. Let me know if you need instructions on how to
> proceed with that.
>

FYI :
Just tried a different compile.
Switched off expert and flipped the CPU to "Generic x86_64" ( no other
changes ).

It compiled. ??

So ... what you choose for CPU in the kernel determines if the
ext2/ext3/ext4 fs driver will compile.

Been using Gentoo / "sys-kernel/gentoo-sources" w/experimental for 3+
years now.
First time the CPU choice has caused a problem.

Suspect that a mismatch of the "Spectre / Meltdown" patches that have
somehow gotten into the ext4 fs driver and the code for specific CPUs.

Wonderful ... just finished a complete reload of Gentoo. Now have to
redo it again ...
... the mistake? I used ext2/ext3 for the fs.

Corbin

[gentoo-user] Re: dev-qt/qtdeclarative fails to build

[Michael Palimaka]

On 01/20/2018 09:10 AM, Christoph Böhmwalder wrote:
> Hey everyone,
> 
> I tried building qtdeclarative-5.9.3 today, but the linker failed:
> 
> $ cat build.log
> --- >8 ---
> g++-6.4.0 -Wl,-O1 -Wl,--as-needed -Wl,--enable-new-dtags -shared -o 
> libparticlesplugin.so .obj/plugin.o
> -L/var/tmp/portage/dev-qt/qtdeclarative-5.9.3/work/qtdeclarative-opensource-src-5.9.3/lib
>  -lQt5QuickParti
> cles -lQt5Quick -lQt5Qml -lQt5Gui -lQt5Network -lQt5Core -lGL -lpthread
> /usr/lib/gcc/x86_64-pc-linux-gnu/6.4.0/../../../../lib64/libQt5Gui.so:(*IND*+0x0):
>  multiple definition of
>  `__bss_start'
> /usr/lib/gcc/x86_64-pc-linux-gnu/6.4.0/../../../../lib64/libQt5Gui.so:(*IND*+0x0):
>  multiple definition of
>  `_edata'
> /usr/lib/gcc/x86_64-pc-linux-gnu/6.4.0/../../../../lib64/libQt5Gui.so:(*IND*+0x0):
>  multiple definition of
>  `_end'
> /usr/lib/gcc/x86_64-pc-linux-gnu/6.4.0/../../../../lib64/libQt5Network.so:(*IND*+0x0):
>  multiple definitio
> n of `_edata'
> /usr/lib/gcc/x86_64-pc-linux-gnu/6.4.0/../../../../lib64/libQt5Network.so:(*IND*+0x0):
>  multiple definitio
> n of `__bss_start'
> /usr/lib/gcc/x86_64-pc-linux-gnu/6.4.0/../../../../lib64/libQt5Network.so:(*IND*+0x0):
>  multiple definitio
> n of `_end'
> collect2: error: ld returned 1 exit status
> 
> $ emerge -pqv '=dev-qt/qtdeclarative-5.9.3::gentoo'
> [ebuild  N] dev-qt/qtdeclarative-5.9.3  USE="jit widgets xml -debug 
> (-gles2) -localstorage {-test}"
> 
> 
> emerge --info output and build.log are attached.
> 
> Any ideas? Thanks!
> 
> --
> Regards,
> Christoph
> 

This is probably bug #623566. Based on this output, try rebuilding
qtcore, qtgui and qtnetwork then try qtdeclarative again.

Re: [gentoo-user] Questions about Pale Moon

[Arve Barsnes]

On 23 January 2018 at 12:58, Peter Humphrey  wrote:
> Hello list,
>
> I keep having another go at palemoon-bin, and each time I remember why I
> don't use it all the time in preference to Firefox.
>
> Q 1:  I've asked this before, but I can't find the reply. How can I arrange
> for  to step through the open tabs, one at a time, from left to
> right. Or is there another key combination to do that?

In firefox, this is done by activating tab previews with
browser.ctrlTab.previews, maybe that also works in palemoon?


> Q 2:  What other package do I need installed to give me the navigation
> symbols? I've attached a section of the window to show what I mean.

Maybe check command line output?

[gentoo-user] Questions about Pale Moon

[Peter Humphrey]

Hello list,

I keep having another go at palemoon-bin, and each time I remember why I 
don't use it all the time in preference to Firefox.

Q 1:  I've asked this before, but I can't find the reply. How can I arrange 
for  to step through the open tabs, one at a time, from left to 
right. Or is there another key combination to do that?

Q 2:  What other package do I need installed to give me the navigation 
symbols? I've attached a section of the window to show what I mean.

-- 
Regards,
Peter.

Re: [gentoo-user] kernel 4.9.77 error segfault in compile.

[Alexander Kapshuk]

On Tue, Jan 23, 2018 at 10:03 AM, Corbin Bird  wrote:
>
>
> On 01/23/2018 01:42 AM, Alexander Kapshuk wrote:
>> On Tue, Jan 23, 2018 at 4:34 AM, Corbin Bird  wrote:
>>> On 01/22/2018 11:56 AM, Rich Freeman wrote:
 On Mon, Jan 22, 2018 at 12:11 PM, Alexander Kapshuk
  wrote:
> On Mon, Jan 22, 2018 at 5:51 PM, Corbin Bird  
> wrote:
>> Anyone else getting this error? ( kernel 4.9.77 )
>>
>>>   CC  fs/ext4/mballoc.o
>>>   CC  fs/ext4/block_validity.o
>>>   CC  fs/ext4/move_extent.o
>>>   CC  fs/ext4/mmp.o
>>>   CC  fs/ext4/indirect.o
>>> fs/ext4/indirect.o: warning: objtool: ext4_clear_blocks()+0x242: can't
>>> find jump dest instruction at .text+0x56c
>>>   CC  fs/ext4/extents_status.o
>>> /bin/sh: line 1: 31735 Segmentation fault  ./tools/objtool/objtool
>>> check "fs/ext4/extents_status.o"
>>> make[2]: *** [scripts/Makefile.build:294: fs/ext4/extents_status.o]
>>> Error 139
>>> make[1]: *** [scripts/Makefile.build:544: fs/ext4] Error 2
>>> make: *** [Makefile:995: fs] Error 2
>> Corbin
>>
>>
> Based on the output you supplied, objtool isn't happy with
> fs/ext4/indirect.o and fs/ext4/extents_status.o.
> Did you do 'make clean' prior to building the kernel?
> If you did, it might be worth doing a 'make mrproper' before
> rebuilding the kernel.
> Don't forget to back up your .config before running mrproper.
>
 While this is going to cause a bit more building, I personally tend to
 redirect kernel build output.  I add O=/var/tmp/linux to all my make
 commands, which leaves /usr/src untouched and builds faster besides
 (tmpfs).

 The main downsides to this are:
 1.  Make can't re-use objects from previous builds, so rebuilds will
 go slower.  Though, IMO this is worthwhile if re-using those objects
 causes issues (which I assume is due to imperfect makefiles).
 2.  When building packages that install kernel modules the prepared
 sources won't exist.  This requires going back and re-preparing them
 (make O=/var/tmp/linux modules_prepare).  For packages like zfs-kmod
 that use Module.symvers this is even more painful as you can only get
 that by rebuilding the whole thing.

>>> Tried both approaches ... the results :
 make distclean
 make mrproper
 --> copy over .config
 make modules_prepare
 make && make modules_install

   CC  fs/ext4/block_validity.o
   CC  fs/ext4/move_extent.o
   CC  fs/ext4/mmp.o
   CC  fs/ext4/indirect.o
 fs/ext4/indirect.o: warning: objtool: ext4_clear_blocks()+0x242: can't
 find jump dest instruction at .text+0x56c
   CC  fs/ext4/extents_status.o
 /bin/sh: line 1: 24095 Segmentation fault  ./tools/objtool/objtool
 check "fs/ext4/extents_status.o"
 make[2]: *** [scripts/Makefile.build:294: fs/ext4/extents_status.o]
 Error 139
 make[1]: *** [scripts/Makefile.build:544: fs/ext4] Error 2
 make: *** [Makefile:995: fs] Error 2


>>> Try 2 :
 make distclean
 make mrproper
 --> copy over .config
 make O=/var/tmp/linux modules_prepare
 make O=/var/tmp/linux && make O=/var/tmp/linux modules_install

   CC  fs/ext4/move_extent.o
   CC  fs/ext4/mmp.o
   CC  fs/ext4/indirect.o
 fs/ext4/indirect.o: warning: objtool: ext4_clear_blocks()+0x242: can't
 find jump dest instruction at .text+0x56c
   CC  fs/ext4/extents_status.o
 /bin/sh: line 1: 21028 Segmentation fault  ./tools/objtool/objtool
 check "fs/ext4/extents_status.o"
 make[3]: *** [/usr/src/linux-4.9.77-gentoo/scripts/Makefile.build:294:
 fs/ext4/extents_status.o] Error 139
 make[2]: *** [/usr/src/linux-4.9.77-gentoo/scripts/Makefile.build:544:
 fs/ext4] Error 2
 make[1]: *** [/usr/src/linux-4.9.77-gentoo/Makefile:995: fs] Error 2
 make[1]: Leaving directory '/var/tmp/linux'
 make: *** [Makefile:150: sub-make] Error 2
>>> Try 2 gave an error warning about needing an 'make mrproper' ... the error :
   CHK include/config/kernel.release
   UPD include/config/kernel.release
   Using /usr/src/linux-4.9.77-gentoo as source for kernel
   /usr/src/linux-4.9.77-gentoo is not clean, please run 'make mrproper'
   in the '/usr/src/linux-4.9.77-gentoo' directory.
 make[1]: *** [/usr/src/linux-4.9.77-gentoo/Makefile:1021: prepare3]
 Error 1
 make[1]: Leaving directory '/var/tmp/linux'
 make: *** [Makefile:150: sub-make] Error 2
>>> So ... I followed directions :
 Darkstar /usr/src/linux # cd /usr/src/linux-4.9.77-gentoo
 Darkstar /usr/src/linux-4.9.77-gentoo # make mrproper
   CLEAN   scripts/basic
   CLEAN   scripts/kconfig
   CLEAN   .config
>>> Still get the same error ...
>>>
>>> 

Re: [gentoo-user] kernel 4.9.77 error segfault in compile.

[Corbin Bird]

On 01/23/2018 01:42 AM, Alexander Kapshuk wrote:
> On Tue, Jan 23, 2018 at 4:34 AM, Corbin Bird  wrote:
>> On 01/22/2018 11:56 AM, Rich Freeman wrote:
>>> On Mon, Jan 22, 2018 at 12:11 PM, Alexander Kapshuk
>>>  wrote:
 On Mon, Jan 22, 2018 at 5:51 PM, Corbin Bird  
 wrote:
> Anyone else getting this error? ( kernel 4.9.77 )
>
>>   CC  fs/ext4/mballoc.o
>>   CC  fs/ext4/block_validity.o
>>   CC  fs/ext4/move_extent.o
>>   CC  fs/ext4/mmp.o
>>   CC  fs/ext4/indirect.o
>> fs/ext4/indirect.o: warning: objtool: ext4_clear_blocks()+0x242: can't
>> find jump dest instruction at .text+0x56c
>>   CC  fs/ext4/extents_status.o
>> /bin/sh: line 1: 31735 Segmentation fault  ./tools/objtool/objtool
>> check "fs/ext4/extents_status.o"
>> make[2]: *** [scripts/Makefile.build:294: fs/ext4/extents_status.o]
>> Error 139
>> make[1]: *** [scripts/Makefile.build:544: fs/ext4] Error 2
>> make: *** [Makefile:995: fs] Error 2
> Corbin
>
>
 Based on the output you supplied, objtool isn't happy with
 fs/ext4/indirect.o and fs/ext4/extents_status.o.
 Did you do 'make clean' prior to building the kernel?
 If you did, it might be worth doing a 'make mrproper' before
 rebuilding the kernel.
 Don't forget to back up your .config before running mrproper.

>>> While this is going to cause a bit more building, I personally tend to
>>> redirect kernel build output.  I add O=/var/tmp/linux to all my make
>>> commands, which leaves /usr/src untouched and builds faster besides
>>> (tmpfs).
>>>
>>> The main downsides to this are:
>>> 1.  Make can't re-use objects from previous builds, so rebuilds will
>>> go slower.  Though, IMO this is worthwhile if re-using those objects
>>> causes issues (which I assume is due to imperfect makefiles).
>>> 2.  When building packages that install kernel modules the prepared
>>> sources won't exist.  This requires going back and re-preparing them
>>> (make O=/var/tmp/linux modules_prepare).  For packages like zfs-kmod
>>> that use Module.symvers this is even more painful as you can only get
>>> that by rebuilding the whole thing.
>>>
>> Tried both approaches ... the results :
>>> make distclean
>>> make mrproper
>>> --> copy over .config
>>> make modules_prepare
>>> make && make modules_install
>>>
>>>   CC  fs/ext4/block_validity.o
>>>   CC  fs/ext4/move_extent.o
>>>   CC  fs/ext4/mmp.o
>>>   CC  fs/ext4/indirect.o
>>> fs/ext4/indirect.o: warning: objtool: ext4_clear_blocks()+0x242: can't
>>> find jump dest instruction at .text+0x56c
>>>   CC  fs/ext4/extents_status.o
>>> /bin/sh: line 1: 24095 Segmentation fault  ./tools/objtool/objtool
>>> check "fs/ext4/extents_status.o"
>>> make[2]: *** [scripts/Makefile.build:294: fs/ext4/extents_status.o]
>>> Error 139
>>> make[1]: *** [scripts/Makefile.build:544: fs/ext4] Error 2
>>> make: *** [Makefile:995: fs] Error 2
>>>
>>>
>> Try 2 :
>>> make distclean
>>> make mrproper
>>> --> copy over .config
>>> make O=/var/tmp/linux modules_prepare
>>> make O=/var/tmp/linux && make O=/var/tmp/linux modules_install
>>>
>>>   CC  fs/ext4/move_extent.o
>>>   CC  fs/ext4/mmp.o
>>>   CC  fs/ext4/indirect.o
>>> fs/ext4/indirect.o: warning: objtool: ext4_clear_blocks()+0x242: can't
>>> find jump dest instruction at .text+0x56c
>>>   CC  fs/ext4/extents_status.o
>>> /bin/sh: line 1: 21028 Segmentation fault  ./tools/objtool/objtool
>>> check "fs/ext4/extents_status.o"
>>> make[3]: *** [/usr/src/linux-4.9.77-gentoo/scripts/Makefile.build:294:
>>> fs/ext4/extents_status.o] Error 139
>>> make[2]: *** [/usr/src/linux-4.9.77-gentoo/scripts/Makefile.build:544:
>>> fs/ext4] Error 2
>>> make[1]: *** [/usr/src/linux-4.9.77-gentoo/Makefile:995: fs] Error 2
>>> make[1]: Leaving directory '/var/tmp/linux'
>>> make: *** [Makefile:150: sub-make] Error 2
>> Try 2 gave an error warning about needing an 'make mrproper' ... the error :
>>>   CHK include/config/kernel.release
>>>   UPD include/config/kernel.release
>>>   Using /usr/src/linux-4.9.77-gentoo as source for kernel
>>>   /usr/src/linux-4.9.77-gentoo is not clean, please run 'make mrproper'
>>>   in the '/usr/src/linux-4.9.77-gentoo' directory.
>>> make[1]: *** [/usr/src/linux-4.9.77-gentoo/Makefile:1021: prepare3]
>>> Error 1
>>> make[1]: Leaving directory '/var/tmp/linux'
>>> make: *** [Makefile:150: sub-make] Error 2
>> So ... I followed directions :
>>> Darkstar /usr/src/linux # cd /usr/src/linux-4.9.77-gentoo
>>> Darkstar /usr/src/linux-4.9.77-gentoo # make mrproper
>>>   CLEAN   scripts/basic
>>>   CLEAN   scripts/kconfig
>>>   CLEAN   .config
>> Still get the same error ...
>>
>> Corbin
>>
> Is this a distribution supplied kernel or vanilla or one with your own
> customisations/modifications?
>

Using 'sys-kernel/gentoo-sources-4.9.77' with USE flags : modules
symlink