On Tue, 2021-02-09 at 17:14 -0500, Jean-Marc Pigeon wrote: > Hello, > On Tue, 2021-02-09 at 18:27 +0000, Ken Moffat wrote: > > On Tue, Feb 09, 2021 at 12:29:14AM +0000, Ken Moffat wrote: > > > On Mon, Feb 08, 2021 at 03:52:35AM +0000, Ken Moffat wrote: > > > > > > > > ../configure --prefix=/usr \ > > > > --disable-werror \ > > > > --enable-kernel=3.2 \ > > > > --enable-stack-protector=strong \ > > > > --with-headers=/usr/include \ > > > > libc_cv_slibdir=/lib > > > > libc_cv_include_x86_isa_level=no > > > > > > > > I've started the native build, but the machine is slow (i3, > > > > slow > > > > DRAM) and I'm not sure it will get very far before I go to > > > > bed. > > > > My > > > > revised plan is to wait for it to fail, whether that is failign > > > > the > > > > build or failing to boot. > > > > > > > > Assuming it does fail, I'll start again with that workaround. > > > > > > > Well I don't need that workaround for using '-march=native -O2' > > > on > > > my skylake, it booted successfully. Fortunately, Frans said it > > > works for him, and htat distros are using it, so I guess we too > > > should use it. > > > > > > However, there was one problem other than my own typos in editing > > > scripts - tried to build linux-5.10.13 - > > > > > > CC arch/x86/kernel/apic/apic.o > > > make[3]: *** [scripts/Makefile.build:279: > > > arch/x86/kernel/apic/apic.o] Segmentation fault > Exact same problem here (not a memory problem, or very big > "cosmic ray"). same problem on kernel-5.10.9 too. > this happen using glibc-2.33 AND binutils-2.36.1 > > rebuilding from scratch using binutils-2.36.1 and keeping > glibc-2.32 make the segmentation fault (I previously restarted > build from scratch with glibc-2.32 + binutils-2.35.1, kernel > compilation was OK). > My conclusion, binutils is the trouble maker. > Could somebody confirm this finding? > Google is mute on this subject but may be my search > keywords were not that good. > advices? suggestions?
Since you two are the only ones (among the persons on this list, up to now) who see this, I guess it has something to do with either: - an option in the config, that you use and the others don't - some CFLAGS settings, but I doubt it, because the kernel build system resets them > > > > > > > Feb 8 20:45:13 leshp klogd: [62379.838193] objtool[10870]: > > > segfault at 70 ip 000000000040c13e sp 00007ffd0f655670 error 4 in > > > objtool[402000+11000] > > > followed by a dump of the code bytes. objtool is a kernel thing. According to tools/objtool/Documentation/stack-validation.txt, " The kernel CONFIG_STACK_VALIDATION option enables a host tool named objtool which runs at compile time. It has a "check" subcommand which analyzes every .o file and ensures the validity of its stack metadata. It enforces a set of rules on asm code and C inline assembly code so that stack traces can be reliable. " Note that I do have that option set to y, but maybe other options in the "Compile-time checks and compiler options" may differ... rebuilding with "make V=1", I see that objtool is run after each compilation. It might be interesting to compare the options that are passed to objtool in my case and in yours. Mine has: ./tools/objtool/objtool check --retpoline --uaccess \ arch/x86/kernel/apic/apic.o (same options for any object file, but I show the one that might be faulty in your case). Maybe "gdb objtool" would allow to learn more (but may need to recompile objtool with debug enabled, I'm not sure how to do that) Pierre -- http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page Do not top post on this list. A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? http://en.wikipedia.org/wiki/Posting_style
