| View previous topic :: View next topic |
| Author |
Message |
Tronic
Apprentice
Joined: 28 Jul 2003
Posts: 194
Location: Finland
|
 Posted: Mon Oct 30, 2006 3:51 am Post subject: Portage ACCESS VIOLATIONS building modules for 2.6.19 kernel |
 |
|
None of the modules from Portage build OK for 2.6.19 kernels, even though there is no trouble building them for 2.6.18. I have seen this on two machines (x86 and amd64), but there doesn't seem to be anything about it here or on the Bugzilla. What's up?
Here is one log snippet as example:
| Code: |
* Determining the location of the kernel source code
* Found kernel source directory:
* /usr/src/linux
* Found sources for kernel version:
* 2.6.19-rc3
* Checking for suitable kernel configuration options... [ ok ]>>> Unpacking source...
>>> Unpacking loop-AES-v3.1e.tar.bz2 to /var/tmp/portage/loop-aes-3.1e/work
* Converting loop-AES-v3.1e/Makefile to use M= instead of SUBDIRS= ... [ ok ]>>> Source unpacked.
>>> Compiling source in /var/tmp/portage/loop-aes-3.1e/work/loop-AES-v3.1e ...
* Preparing loop module
cd /usr/src/linux && make M=/var/tmp/portage/loop-aes-3.1e/work/loop-AES-v3.1e modules Q='@cd /var/tmp/portage/loop-aes-3.1e/work/loop-AES-v3.1e && if [ "$@" = "modules" ]; then make modules; fi; # '
ACCESS DENIED unlink: /usr/src/linux-2.6.19-rc3/astest32498.out
rm: cannot remove `astest32498.out': Permission denied
ACCESS DENIED unlink: /usr/src/linux-2.6.19-rc3/astest32502.out
rm: cannot remove `astest32502.out': Permission denied
ACCESS DENIED unlink: /usr/src/linux-2.6.19-rc3/astest32509.out
rm: cannot remove `astest32509.out': Permission denied
ACCESS DENIED unlink: /usr/src/linux-2.6.19-rc3/astest32514.out
rm: cannot remove `astest32514.out': Permission denied
make[1]: Entering directory `/usr/src/linux-2.6.19-rc3'
make[1]: warning: jobserver unavailable: using -j1. Add `+' to parent make rule.
/bin/sh: -c: line 6: syntax error near unexpected token `)'
/bin/sh: -c: line 6: `/bin/false)'
Building modules, stage 2.
rm -f *.o *.ko *.orig *.rej *.mod.c patched-loop.[ch] test-file[1234]
rm -f -r test-dir1 tmp-d-kbuild
rm -f patched-loop.[ch]
cp loop.c-2.6.patched patched-loop.c
cd /usr/src/linux && i686-pc-linux-gnu-gcc -nostdinc -isystem /usr/lib/gcc/i686-pc-linux-gnu/4.1.1/include -D__KERNEL__ -Iinclude -include include/linux/autoconf.h -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -O2 -pipe -msoft-float -mpreferred-stack-boundary=2 -march=i686 -mtune=pentium4 -ffreestanding -maccumulate-outgoing-args -Iinclude/asm-i386/mach-default -fno-omit-frame-pointer -fno-optimize-sibling-calls -fasynchronous-unwind-tables -g -fno-stack-protector -Wdeclaration-after-statement -Wno-pointer-sign -DMODULE -D"KBUILD_STR(s)=#s" -DX86_ASM -D"KBUILD_BASENAME=KBUILD_STR(patched_loop)" -D"KBUILD_MODNAME=KBUILD_STR(loop)" -DEXPORT_SYMTAB -c /var/tmp/portage/loop-aes-3.1e/work/loop-AES-v3.1e/patched-loop.c -o /var/tmp/portage/loop-aes-3.1e/work/loop-AES-v3.1e/patched-loop.o
/var/tmp/portage/loop-aes-3.1e/work/loop-AES-v3.1e/patched-loop.c: In function loop_thread:
/var/tmp/portage/loop-aes-3.1e/work/loop-AES-v3.1e/patched-loop.c:957: warning: x may be used uninitialized in this function
cd /usr/src/linux && i686-pc-linux-gnu-gcc -nostdinc -isystem /usr/lib/gcc/i686-pc-linux-gnu/4.1.1/include -D__KERNEL__ -Iinclude -include include/linux/autoconf.h -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -O2 -pipe -msoft-float -mpreferred-stack-boundary=2 -march=i686 -mtune=pentium4 -ffreestanding -maccumulate-outgoing-args -Iinclude/asm-i386/mach-default -fno-omit-frame-pointer -fno-optimize-sibling-calls -fasynchronous-unwind-tables -g -fno-stack-protector -Wdeclaration-after-statement -Wno-pointer-sign -DMODULE -D"KBUILD_STR(s)=#s" -DX86_ASM -D"KBUILD_BASENAME=KBUILD_STR(glue)" -D"KBUILD_MODNAME=KBUILD_STR(loop)" -c /var/tmp/portage/loop-aes-3.1e/work/loop-AES-v3.1e/glue.c -o /var/tmp/portage/loop-aes-3.1e/work/loop-AES-v3.1e/glue.o
cd /usr/src/linux && i686-pc-linux-gnu-gcc -D__ASSEMBLY__ -Iinclude/asm-i386/mach-default -c /var/tmp/portage/loop-aes-3.1e/work/loop-AES-v3.1e/aes-x86.S -o /var/tmp/portage/loop-aes-3.1e/work/loop-AES-v3.1e/aes-x86.o
cd /usr/src/linux && i686-pc-linux-gnu-gcc -D__ASSEMBLY__ -Iinclude/asm-i386/mach-default -c /var/tmp/portage/loop-aes-3.1e/work/loop-AES-v3.1e/md5-x86.S -o /var/tmp/portage/loop-aes-3.1e/work/loop-AES-v3.1e/md5-x86.o
ld -m elf_i386 -r patched-loop.o glue.o aes-x86.o md5-x86.o -o loop.o
cd /usr/src/linux && ./scripts/mod/modpost -m vmlinux /var/tmp/portage/loop-aes-3.1e/work/loop-AES-v3.1e/loop.o >/dev/null 2>&1
cd /usr/src/linux && i686-pc-linux-gnu-gcc -nostdinc -isystem /usr/lib/gcc/i686-pc-linux-gnu/4.1.1/include -D__KERNEL__ -Iinclude -include include/linux/autoconf.h -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -O2 -pipe -msoft-float -mpreferred-stack-boundary=2 -march=i686 -mtune=pentium4 -ffreestanding -maccumulate-outgoing-args -Iinclude/asm-i386/mach-default -fno-omit-frame-pointer -fno-optimize-sibling-calls -fasynchronous-unwind-tables -g -fno-stack-protector -Wdeclaration-after-statement -Wno-pointer-sign -DMODULE -D"KBUILD_STR(s)=#s" -DX86_ASM -D"KBUILD_BASENAME=KBUILD_STR(loop_mod)" -D"KBUILD_MODNAME=KBUILD_STR(loop)" -c /var/tmp/portage/loop-aes-3.1e/work/loop-AES-v3.1e/loop.mod.c -o /var/tmp/portage/loop-aes-3.1e/work/loop-AES-v3.1e/loop.mod.o
ld -m elf_i386 -r loop.o loop.mod.o -o loop.ko
rm -f loop.o loop.mod.[co]
sync
Currently running kernel is 2.6.18
Module was built for kernel 2.6.19-rc3
WARNING - THIS MODULE WILL NOT WORK WITH CURRENTLY RUNNING KERNEL
make[1]: Leaving directory `/usr/src/linux-2.6.19-rc3'
>>> Source compiled.
--------------------------- ACCESS VIOLATION SUMMARY ---------------------------LOG FILE = "/var/log/sandbox/sandbox-sys-fs_-_loop-aes-3.1e-32383.log"
open_wr: /usr/src/linux-2.6.19-rc3/astest32498.out
unlink: /usr/src/linux-2.6.19-rc3/astest32498.out
open_wr: /usr/src/linux-2.6.19-rc3/astest32502.out
unlink: /usr/src/linux-2.6.19-rc3/astest32502.out
open_wr: /usr/src/linux-2.6.19-rc3/astest32509.out
unlink: /usr/src/linux-2.6.19-rc3/astest32509.out
open_wr: /usr/src/linux-2.6.19-rc3/astest32514.out
unlink: /usr/src/linux-2.6.19-rc3/astest32514.out
--------------------------------------------------------------------------------
|
_________________
There are no alternative energy sources to fossil fuels. Whoever claims otherwise doesn't know the difference between mW and MW. -Kurki-Suonio |
|
| Back to top |
|
 |
Nick C
Guru
Joined: 18 Mar 2005
Posts: 526
Location: Portsmouth, England
|
| Posted: Mon Oct 30, 2006 4:12 am Post subject: |
|
|
dont forget 2.6.19 is still in development, not all software that builds against the kernel source will have been updated yet (and in some cases wont be until 2.6.19 is officially released), sadly its the price you pay living on the bleeding edge.
_________________
Please add [solved] to the initial post's subject line if you feel your problem is resolved.
www.monkeydust.net |
|
| Back to top |
|
|
Tronic
Apprentice
Joined: 28 Jul 2003
Posts: 194
Location: Finland
|
| Posted: Mon Oct 30, 2006 4:44 am Post subject: |
|
|
Yeah.. You don't live on the bleeding edge and your NIC driver keeps crashing all the time, while your RAID card is simply not supported. And when you do, you are not supported :P
Meanwhile, any hints where to get started if I want to mess with this issue? What the heck are these astest files and what is generating them?
_________________
There are no alternative energy sources to fossil fuels. Whoever claims otherwise doesn't know the difference between mW and MW. -Kurki-Suonio |
|
| Back to top |
|
|
Nick C
Guru
Joined: 18 Mar 2005
Posts: 526
Location: Portsmouth, England
|
| Posted: Mon Oct 30, 2006 3:31 pm Post subject: |
|
|
can you live without that package? Its obviously trying to do something that doesnt work on the .19 kernel series. Id imagine the only way to get it to work would be to check the packages homepage incase they have an updated version, or checkout a cvs/svn snapshot and try building that in the hope they have already added 2.6.19 support. Dont complain about it on bugzilla though as i suspect they will say that they cant/wont do anything until 2.6.19 goes stable (or at least gets released officially)
_________________
Please add [solved] to the initial post's subject line if you feel your problem is resolved.
www.monkeydust.net |
|
| Back to top |
|
|
kallamej
Administrator
Joined: 27 Jun 2003
Posts: 4975
Location: Gothenburg, Sweden
|
|
| Back to top |
|
|
|
Duplicate Threads
