View previous topic :: View next topic |
Author |
Message |
PSU_Todd n00b
Joined: 09 Jul 2003 Posts: 3
|
Posted: Wed Jul 09, 2003 9:56 pm Post subject: chroot Segmentation Fault |
|
|
I'm trying to install Gentoo on a Ultra5 machine for the first time.
The first time through, everything went fine, up until I ran bootstrap.sh. I first ran bootstrap.sh --fetchonly to get the files, but after it had finished, and I ran bootstrap.sh proper, it segfaulted while compiling portage.
I thought it was slightly unusual, so I rebooted the machine and tried again. Now I can't get back into the installation to copy down exactly what it was doing when it died. I issued
mount /dev/hda4 /mnt/gentoo
mount /dev/hda1 /mnt/gentoo/boot
mount -t proc /proc /mnt/gentoo/proc
swapon /dev/hda2
and then
chroot /mnt/gentoo /bin/bash
and it immediately quit with the message "Segmentation Fault", and no helpful information. Am I missing something? Or... |
|
Back to top |
|
|
Weeve Retired Dev
Joined: 30 Oct 2002 Posts: 641
|
Posted: Thu Jul 10, 2003 2:02 pm Post subject: |
|
|
Which stage tarball did you start with, and what are you using for CFLAGS? |
|
Back to top |
|
|
PSU_Todd n00b
Joined: 09 Jul 2003 Posts: 3
|
Posted: Thu Jul 10, 2003 7:42 pm Post subject: |
|
|
Ok I seem to have fixed the chroot segfault by rebooting and reformatting /dev/hda4. I'm using Stage1 because I get intermittent bunzip2 errors when I try to decompress the files. But 1 thing at a time.
When I try to compile portage, gcc segfaults.
>>> Source unpacked.
gcc: Internal error: Segmentation fault (program as)
Please submit a full bug report.
[gcc URL, etc.]
./create-localdecls
Checking truncate argument type... off_t
Checking libc version... gcc: Internal error: Segmentation fault (program as)
Please submit a full bug report.
[gcc URL, etc.]
ldd: ./libctest: No such file or directory
rm: cannot remove `libctest': No such file or directory
gcc -Wall -c -D_GNU_SOURCE -DPIC -D_REENTRANT libsandbox.c
In file included from libsandbox.c:56:
/usr/include/stdlib.h:274: stray '\337' in program
/usr/include/stdlib.h:274: parse error before "strtol_internal"
make: *** [libsandbox.o] Error 1
!!! ERROR: sys-apps/portage-2-0-48-r1 failed.
!!! Function src-compile, Line 31, Exitcode 2
!!! (no error messages)
It then returns to the bash prompt, and prints "cc1: Broken pipe: error writing to -".
I have used both "-mcpu=ultrasparc -O3 -pipe", and less aggressive -O settings, as well as leaving the line commented out. |
|
Back to top |
|
|
Weeve Retired Dev
Joined: 30 Oct 2002 Posts: 641
|
Posted: Fri Jul 11, 2003 12:57 am Post subject: |
|
|
Have you successfully run other operating systems on this machine before? It almost sounds like you might have a hardware problem which is causing your errors (most likely bad RAM or hard drive). |
|
Back to top |
|
|
PSU_Todd n00b
Joined: 09 Jul 2003 Posts: 3
|
Posted: Fri Jul 11, 2003 4:05 am Post subject: |
|
|
Ya know I was thinking that earlier...I tried loading Solaris 9 on the thing and it kept quitting (while loading the kernel, i presume?) and dumping me back to OpenBoot with MMU errors. |
|
Back to top |
|
|
Weeve Retired Dev
Joined: 30 Oct 2002 Posts: 641
|
Posted: Fri Jul 11, 2003 10:37 am Post subject: |
|
|
Yeah, I'd try a couple more OSs and see if you have similar behavior. One that should be easy and kinda painless to try is OpenBSD. It'll install quickly and you should be able to muck around a bit and see if it has similar problems.
But it does sound like a hardware problem. My inclination is that you might have some bad RAM. |
|
Back to top |
|
|
|