1 |
On 13/07/2015 19:47, Mick wrote: |
2 |
> On Monday 13 Jul 2015 17:42:22 Alexander Kapshuk wrote: |
3 |
>> On Mon, Jul 13, 2015 at 5:29 PM, Alan McKinnon <alan.mckinnon@×××××.com> |
4 |
> wrote: |
5 |
>>> Did a new install, the new kernel can't load modules: |
6 |
>>> |
7 |
>>> # modprobe nfsv3 |
8 |
>>> modprobe: ERROR: could not insert 'nfsv3': Exec format error |
9 |
>>> |
10 |
>>> Odd. Never had this before. The module file itself is a regular 64-bit |
11 |
>>> ELF file, just as it should be (compared to a working module on another |
12 |
>>> machine) |
13 |
>>> |
14 |
>>> gcc is 4.8.4 as supplied by a recent stage3-amd64-20150709.tar.bz2: |
15 |
>>> # gcc -v |
16 |
>>> Using built-in specs. |
17 |
>>> COLLECT_GCC=/usr/x86_64-pc-linux-gnu/gcc-bin/4.8.4/gcc |
18 |
>>> COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-pc-linux-gnu/4.8.4/lto-wrappe |
19 |
>>> r Target: x86_64-pc-linux-gnu |
20 |
>>> Configured with: |
21 |
>>> /var/tmp/portage/sys-devel/gcc-4.8.4/work/gcc-4.8.4/configure |
22 |
>>> --host=x86_64-pc-linux-gnu --build=x86_64-pc-linux-gnu --prefix=/usr |
23 |
>>> --bindir=/usr/x86_64-pc-linux-gnu/gcc-bin/4.8.4 |
24 |
>>> --includedir=/usr/lib/gcc/x86_64-pc-linux-gnu/4.8.4/include |
25 |
>>> --datadir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.8.4 |
26 |
>>> --mandir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.8.4/man |
27 |
>>> --infodir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.8.4/info |
28 |
>>> --with-gxx-include-dir=/usr/lib/gcc/x86_64-pc-linux-gnu/4.8.4/include/g++ |
29 |
>>> -v4 --with-python-dir=/share/gcc-data/x86_64-pc-linux-gnu/4.8.4/python |
30 |
>>> --enable-languages=c,c++,fortran --enable-obsolete --enable-secureplt |
31 |
>>> --disable-werror --with-system-zlib --enable-nls |
32 |
>>> --without-included-gettext --enable-checking=release |
33 |
>>> --with-bugurl=https://bugs.gentoo.org/ --with-pkgversion='Gentoo 4.8.4 |
34 |
>>> p1.6, pie-0.6.1' --enable-libstdcxx-time --enable-shared |
35 |
>>> --enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu |
36 |
>>> --enable-multilib --with-multilib-list=m32,m64 --disable-altivec |
37 |
>>> --disable-fixed-point --enable-targets=all --disable-libgcj |
38 |
>>> --enable-libgomp --disable-libmudflap --disable-libssp --enable-lto |
39 |
>>> --without-cloog --enable-libsanitizer |
40 |
>>> Thread model: posix |
41 |
>>> gcc version 4.8.4 (Gentoo 4.8.4 p1.6, pie-0.6.1) |
42 |
>>> |
43 |
>>> make.conf seems correct: |
44 |
>>> CHOST="x86_64-pc-linux-gnu" |
45 |
>>> CFLAGS="-march=native -O2 -pipe" |
46 |
>>> CXXFLAGS="${CFLAGS}" |
47 |
>>> ACCEPT_KEYWORDS="~amd64" |
48 |
>>> |
49 |
>>> The kernel loads and runs OK: |
50 |
>>> # uname -a |
51 |
>>> Linux download 4.1.2-gentoo #1 SMP Mon Jul 13 13:28:40 SAST 2015 x86_64 |
52 |
>>> Intel(R) Core(TM) i7-2720QM CPU @ 2.20GHz GenuineIntel GNU/Linux |
53 |
>>> |
54 |
>>> and the kernel was built with gcc auto-detection: |
55 |
>>> # grep NATIVE /boot/config-4.1.2-gentoo |
56 |
>>> CONFIG_MNATIVE=y |
57 |
>>> |
58 |
>>> and the .config was grabbed from a working machine with very similar |
59 |
>>> hardware (one minor hardware upgrade ahead) |
60 |
>>> |
61 |
>>> I haven't done a full world update yet, most code is still what's in the |
62 |
>>> stage3, but always in the past that hasn't been a problem; the stage |
63 |
>>> must successfully build a kernel and load the modules. |
64 |
>>> |
65 |
>>> Module loading works just fine when booted from the Gentoo minimal |
66 |
>>> install image. |
67 |
>>> |
68 |
>>> So, what dumbass n00b error did I make today? |
69 |
>>> |
70 |
>>> |
71 |
>>> -- |
72 |
>>> Alan McKinnon |
73 |
>>> alan.mckinnon@×××××.com |
74 |
>> |
75 |
>> Does 'modprobe -nv' say anything useful? |
76 |
>> |
77 |
>> Anything of interest in '/var/log/dmesg'? |
78 |
> |
79 |
> |
80 |
> Just in case you missed it on the enthusiasm of a new install, have you set: |
81 |
> |
82 |
> CONFIG_MODULES=y |
83 |
|
84 |
Yes, that's set. And the kernel correctly loads modules it finds it |
85 |
needs on startup. I just can't do it from userspace. |
86 |
|
87 |
> |
88 |
> and of course built as modules whatever you're modprobing. |
89 |
> |
90 |
> BTW, is the module in question called 'nfsv3', or is it 'nfs'? I don't use it |
91 |
> myself to know. |
92 |
|
93 |
The name is correct. There's a module "nfs" for core stuff and "nfsv3" & |
94 |
"nfsv4" fr the different versions. |
95 |
|
96 |
|
97 |
|
98 |
-- |
99 |
Alan McKinnon |
100 |
alan.mckinnon@×××××.com |