| View previous topic :: View next topic |
| Author |
Message |
carpman
Advocate
Joined: 20 Jun 2002
Posts: 2202
Location: London - UK
|
 Posted: Tue Jan 29, 2008 6:13 pm Post subject: amd64 install kernel error |
 |
|
Hello building my new amd64bit install from inside mepis 64bit but am having problem building the kernel in chroot, the FS was created in gentoo 32bit but was told that was ok.
Errors are different each time i try, here are a couple
| Code: |
CC fs/reiserfs/bitmap.o
CC fs/reiserfs/do_balan.o
CC fs/reiserfs/namei.o
CC fs/reiserfs/inode.o
CC fs/reiserfs/file.o
CC fs/reiserfs/dir.o
CC fs/reiserfs/fix_node.o
CC fs/reiserfs/super.o
CC fs/reiserfs/prints.o
CC fs/reiserfs/objectid.o
CC fs/reiserfs/lbalance.o
CC fs/reiserfs/ibalance.o
CC fs/reiserfs/stree.o
gcc: Internal error: Segmentation fault (program as)
Please submit a full bug report.
See <URL:http://bugs.gentoo.org/> for instructions.
make[2]: *** [fs/reiserfs/stree.o] Error 1
make[1]: *** [fs/reiserfs] Error 2
make: *** [fs] Error 2
|
| Code: |
CC drivers/acpi/executer/exoparg2.o
CC drivers/acpi/executer/exregion.o
CC drivers/acpi/executer/exstore.o
CC drivers/acpi/executer/exutils.o
CC drivers/acpi/executer/exdump.o
/bin/sh: line 1: 6691 Segmentation fault gcc -Wp,-MD,drivers/acpi/executer/.exdump.o.d -nostdinc -isystem /usr/lib/gcc/x86_64-pc-linux-gnu/4.1.2/include -D__KERNEL__ -Iinclude -include include/linux/autoconf.h -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -Werror-implicit-function-declaration -Os -march=k8 -m64 -mno-red-zone -mcmodel=kernel -pipe -Wno-sign-compare -fno-asynchronous-unwind-tables -funit-at-a-time -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -maccumulate-outgoing-args -DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -fomit-frame-pointer -fno-stack-protector -Wdeclaration-after-statement -Wno-pointer-sign -Os -D"KBUILD_STR(s)=#s" -D"KBUILD_BASENAME=KBUILD_STR(exdump)" -D"KBUILD_MODNAME=KBUILD_STR(exdump)" -c -o drivers/acpi/executer/exdump.o drivers/acpi/executer/exdump.c
make[3]: *** [drivers/acpi/executer/exdump.o] Error 139
make[2]: *** [drivers/acpi/executer] Error 2
make[1]: *** [drivers/acpi] Error 2
make: *** [drivers] Error 2
|
_________________
Work Station - 64bit
Gigabyte GA X48-DQ6 Core2duo E8400
8GB GSkill DDR2-1066
SATA Areca 1210 Raid
BFG OC2 8800 GTS 640mb
--------------------------------
Notebook
Samsung Q45 7100 4gb |
|
| Back to top |
|
 |
Carnildo
Guru
Joined: 17 Jun 2004
Posts: 595
|
| Posted: Tue Jan 29, 2008 11:09 pm Post subject: |
|
|
| Random gcc segfaults usually indicate a hardware problem. Have you tested the RAM using MemTest86 to make sure it's good? Have you checked to see if the CPU is overheating? |
|
| Back to top |
|
|
carpman
Advocate
Joined: 20 Jun 2002
Posts: 2202
Location: London - UK
|
| Posted: Tue Jan 29, 2008 11:35 pm Post subject: |
|
|
| Carnildo wrote: | | Random gcc segfaults usually indicate a hardware problem. Have you tested the RAM using MemTest86 to make sure it's good? Have you checked to see if the CPU is overheating? |
Yep tested it the other day, cpu is not over heating either, had no problems on same system when it was running 32bit?
_________________
Work Station - 64bit
Gigabyte GA X48-DQ6 Core2duo E8400
8GB GSkill DDR2-1066
SATA Areca 1210 Raid
BFG OC2 8800 GTS 640mb
--------------------------------
Notebook
Samsung Q45 7100 4gb |
|
| Back to top |
|
|
carpman
Advocate
Joined: 20 Jun 2002
Posts: 2202
Location: London - UK
|
| Posted: Wed Jan 30, 2008 11:35 am Post subject: |
|
|
It is not always a segmentation fault:
| Code: |
UPD include/linux/compile.h
CC init/version.o
LD init/built-in.o
LD .tmp_vmlinux1
fs/built-in.o: In function `autofs4_kill_sb':
(.text+0xd84ba): undefined reference to `autofs4_catatonic_mode'
fs/built-in.o: In function `try_to_fill_dentry':
root.c:(.text+0xd864c): undefined reference to `autofs4_wait'
root.c:(.text+0xd867e): undefined reference to `autofs4_wait'
root.c:(.text+0xd8703): undefined reference to `autofs4_wait'
fs/built-in.o: In function `autofs4_root_ioctl':
root.c:(.text+0xd888b): undefined reference to `autofs4_catatonic_mode'
fs/built-in.o: In function `autofs4_follow_link':
root.c:(.text+0xd904f): undefined reference to `autofs4_wait'
fs/built-in.o: In function `autofs4_lookup':
root.c:(.text+0xd9632): undefined reference to `autofs4_wait'
fs/built-in.o: In function `autofs4_root_ioctl':
root.c:(.text+0xd8883): undefined reference to `autofs4_wait_release'
fs/built-in.o: In function `autofs4_expire_multi':
(.text+0xda2ee): undefined reference to `autofs4_wait'
make: *** [.tmp_vmlinux1] Error 1
|
_________________
Work Station - 64bit
Gigabyte GA X48-DQ6 Core2duo E8400
8GB GSkill DDR2-1066
SATA Areca 1210 Raid
BFG OC2 8800 GTS 640mb
--------------------------------
Notebook
Samsung Q45 7100 4gb |
|
| Back to top |
|
|
carpman
Advocate
Joined: 20 Jun 2002
Posts: 2202
Location: London - UK
|
| Posted: Wed Jan 30, 2008 1:27 pm Post subject: |
|
|
Ok i boot to gentoo x64 install cd to ensure it was not an issue with chrooting from mepis install but results are the same.
_________________
Work Station - 64bit
Gigabyte GA X48-DQ6 Core2duo E8400
8GB GSkill DDR2-1066
SATA Areca 1210 Raid
BFG OC2 8800 GTS 640mb
--------------------------------
Notebook
Samsung Q45 7100 4gb |
|
| Back to top |
|
|
DtZ
Tux's lil' helper
Joined: 09 Sep 2005
Posts: 124
|
| Posted: Wed Jan 30, 2008 2:27 pm Post subject: |
|
|
| If it causes random gcc segfaults, it's very likely to be a hardware problem. Memtest isn't a perfect tool. If you have some spare memory sticks available try them. I've had a similar problem a while back and memtest wouldn't report any errors. Still after a few tests with parts borrowed from my friends I've found out that one memory stick was faulty. |
|
| Back to top |
|
|
carpman
Advocate
Joined: 20 Jun 2002
Posts: 2202
Location: London - UK
|
| Posted: Wed Jan 30, 2008 4:00 pm Post subject: |
|
|
| DtZ wrote: | | If it causes random gcc segfaults, it's very likely to be a hardware problem. Memtest isn't a perfect tool. If you have some spare memory sticks available try them. I've had a similar problem a while back and memtest wouldn't report any errors. Still after a few tests with parts borrowed from my friends I've found out that one memory stick was faulty. |
Yep can understand that but as said worked fine on 32bit install, and can emerge other apps ok just not kernel?
_________________
Work Station - 64bit
Gigabyte GA X48-DQ6 Core2duo E8400
8GB GSkill DDR2-1066
SATA Areca 1210 Raid
BFG OC2 8800 GTS 640mb
--------------------------------
Notebook
Samsung Q45 7100 4gb |
|
| Back to top |
|
|
carpman
Advocate
Joined: 20 Jun 2002
Posts: 2202
Location: London - UK
|
| Posted: Wed Jan 30, 2008 8:21 pm Post subject: |
|
|
ok just tried this chroot install setup in another box and kernel compiled fine.
I have 4 modules of memory in box that is not compiling, 2 i have had for a while and 2 recent ones i have swap them about, 2 old ones only, 2 new ones only and still kernel compile errors but other apps compile fine?
What is that makes compiling kernel so touchy?
Not sure what the hardware problem as chances of all four modules being faulty is slim so might be motherboard memory controller?
_________________
Work Station - 64bit
Gigabyte GA X48-DQ6 Core2duo E8400
8GB GSkill DDR2-1066
SATA Areca 1210 Raid
BFG OC2 8800 GTS 640mb
--------------------------------
Notebook
Samsung Q45 7100 4gb |
|
| Back to top |
|
|
|
Kernel & Hardware
