Re: Segmentation fault after stripping
linux fan wrote: On 11/24/09, Bruce Dubbs wrote: linux fan wrote: On 11/24/09, Bruce Dubbs wrote: Have you tried booting into memtest86+ and checking your memory? Thanks for that! Eliminated one memory bank at a time until it didn't fail before test #5. Rolled back to textinfo-ch5. make ... it got thru stripping and is keeping going ... Should I restart the build from ground zero (memory uncertainty), or is it OK to keep going? I'd start over. Having a suspect base is not a good idea. Try jhalfs to automate the build. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: Segmentation fault after stripping
On 11/24/09, Bruce Dubbs wrote: I'd start over. Having a suspect base is not a good idea. Try jhalfs to automate the build. Yes jhalfs has been working for me. Starting over from mke2fs. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: Segmentation fault after stripping
On 11/24/09, Bruce Dubbs wrote: linux fan wrote: Intending to umount and roll back, I get: df -ha FilesystemSize Used Avail Use% Mounted on /dev/sda11 11G 7.6G 2.7G 74% / /proc0 0 0 - /proc sysfs0 0 0 - /sys devpts 0 0 0 - /dev/pts tmpfs 760M 0 760M 0% /dev/shm /dev/sdd105.1G 2.0G 2.9G 40% /mnt/lfs /dev 760M 240K 759M 1% /mnt/lfs/dev devpts 0 0 0 - /mnt/lfs/dev/pts shm 760M 0 760M 0% /mnt/lfs/dev/shm proc 0 0 0 - /mnt/lfs/proc sysfs0 0 0 - /mnt/lfs/sys r...@lfs:~# umount /mnt/lfs/sys r...@lfs:~# umount /mnt/lfs/proc r...@lfs:~# umount /mnt/lfs/dev/shm r...@lfs:~# umount /mnt/lfs/dev/pts r...@lfs:~# umount /mnt/lfs/dev r...@lfs:~# umount /mnt/lfs umount /mnt/lfs Segmentation fault Just out of curiosity, they are looking into this kernel BUG at fs/ext3/super.c:435 http://marc.info/?l=linux-kernelm=125880707213275w=2 which happens after (re)building glibc and test, and then doing umount. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Segmentation fault after stripping
Segmentation fault occurs right after stripping in chapter05. I am building lfs trunk using jhalfs trunk. The stripping step succeeds, but the next step which is to restore-luser-env errors. The restore-luser-env step only has to copy the saved $(LUSER_HOME)/.bashrc.XXX back to .bashrc, but that fails: Building target 058-stripping [++| ] 0 min. 10 sec Target 058-stripping OK /bin/bash: line 1: 27848 Segmentation fault make BREAKPOINT=074-gcc LUSER make: *** [mk_LUSER] Error 139 As you can see, the stripping succeeded, but it immediately fails on the next bash command. Here is from sys.log: Nov 23 15:25:32 lfs sudo: wnh : TTY=pts/0 ; PWD=/mnt/lfs/jhalfs ; USER=root ; COMMAND=/bin/su - jhalfs -c source .bashrc cd /mnt/lfs/jhalfs make BREAKPOINT=074-gcc LUSER Nov 23 15:25:42 lfs kernel: make[27848]: segfault at 7b0 ip 40008fdd sp bfccaaa0 error 4 in ld-2.11.so (deleted)[4000+1d000] I have the build backed up right after textinfo-ch5. I have restored the build dir and restarted and it Segfaults every time at the same place. I tried a 20 second sleep at the end of the stripping, but it still Segfaults. Any ideas? -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: Segmentation fault after stripping
On Mon, 23 Nov 2009 16:02:12 -0500 linux fan linuxscra...@gmail.com wrote: Segmentation fault occurs right after stripping in chapter05. I am building lfs trunk using jhalfs trunk. The stripping step succeeds, but the next step which is to restore-luser-env errors. The restore-luser-env step only has to copy the saved $(LUSER_HOME)/.bashrc.XXX back to .bashrc, but that fails: Building target 058-stripping [++| ] 0 min. 10 sec Target 058-stripping OK /bin/bash: line 1: 27848 Segmentation fault make BREAKPOINT=074-gcc LUSER make: *** [mk_LUSER] Error 139 As you can see, the stripping succeeded, but it immediately fails on the next bash command. Here is from sys.log: Nov 23 15:25:32 lfs sudo: wnh : TTY=pts/0 ; PWD=/mnt/lfs/jhalfs ; USER=root ; COMMAND=/bin/su - jhalfs -c source .bashrc cd /mnt/lfs/jhalfs make BREAKPOINT=074-gcc LUSER Nov 23 15:25:42 lfs kernel: make[27848]: segfault at 7b0 ip 40008fdd sp bfccaaa0 error 4 in ld-2.11.so (deleted)[4000+1d000] I have the build backed up right after textinfo-ch5. I have restored the build dir and restarted and it Segfaults every time at the same place. I tried a 20 second sleep at the end of the stripping, but it still Segfaults. Any ideas? As I have not tried jhalfs, a question, just to be clear: you are running the make command via automated means, after stripping, in a single slurp (from the same script)? If so, try running it manually after stripping. As in - your toolchain gets stripped, jou get your shell prompt back, and then you run the make command. That used to work for me in similar arrangements. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: Segmentation fault after stripping
On 11/23/09, Aleksandar Kuktin wrote: As I have not tried jhalfs, a question, just to be clear: you are running the make command via automated means, after stripping, in a single slurp (from the same script)? jhalfs automates from start to finish. I have used it to build LFS 6.2.0, 6.3, and 6.4 and it never had a problem on the stripping. If so, try running it manually after stripping. As in - your toolchain gets stripped, jou get your shell prompt back, and then you run the make command. Last night, I tried restarting make after it came back to the shell prompt and all kinds of system problems occurred : It barfed badly when trying to umount the build dir System choked on attempt to shutdown It just got the situation to be unstable The sys.log showed that the attempted umount triggered kernel bug/oops I managed to init 1 to single user mode to get as quiet as possible before poweroff So, I don't want to pretend that everything would be ok. There seems to be something incompatible about doing stripping in the development lfs book. Right now, I set it to bypass the stripping altogether and it is in the middle of building glibc-ch6 -- ok so far. I could roll back to textinfo-ch5 if anybody has an idea to test how to keep stripping from causing the segfaults. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: Segmentation fault after stripping
linux fan wrote: Last night, I tried restarting make after it came back to the shell prompt and all kinds of system problems occurred : It barfed badly when trying to umount the build dir System choked on attempt to shutdown It just got the situation to be unstable The sys.log showed that the attempted umount triggered kernel bug/oops I managed to init 1 to single user mode to get as quiet as possible before poweroff So, I don't want to pretend that everything would be ok. There seems to be something incompatible about doing stripping in the development lfs book. There is nothing different about -dev that should make the behavior of stripping different from earlier LFS version. Is there any possibility that there could be a memory or disk problem? Are you sure you have enough disk space? -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: Segmentation fault after stripping
On 11/23/09, Bruce Dubbs bruce.du...@gmail.com wrote: Is there any possibility that there could be a memory or disk problem? Are you sure you have enough disk space? Good thinking, but doesn't seem to be space issue: top - 19:43:27 up 11:00, 1 user, load average: 1.06, 1.03, 1.04 Tasks: 77 total, 2 running, 75 sleeping, 0 stopped, 0 zombie Cpu(s): 60.0%us, 7.5%sy, 0.0%ni, 30.8%id, 1.5%wa, 0.1%hi, 0.1%si, 0.0%st Mem: 1554504k total, 1231544k used, 322960k free,81272k buffers Swap: 522072k total,0k used, 522072k free, 943912k cached df -h FilesystemSize Used Avail Use% Mounted on /dev/sda11 11G 7.6G 2.7G 74% / tmpfs 760M 0 760M 0% /dev/shm /dev/sdd105.1G 2.4G 2.5G 50% /mnt/lfs shm 760M 0 760M 0% /mnt/lfs/dev/shm /mnt/lfs is the build dir This suspicious, scary message right after strip doesn't seem to indicate hardware: Nov 23 15:10:36 lfs kernel: make[27639]: segfault at 7b0 ip 40008fdd sp bf93c390 error 4 in ld-2.11.so (deleted)[4000+1d000] -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: Segmentation fault after stripping
I must clarify my confusion. I am supposing that you would like for me to roll back to the point where it is to be stripped. Then strip. Then run /tools/command on /tools/file Correct? -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: Segmentation fault after stripping
On 11/23/09, Bruce Dubbs wrote: To check things out a little more, you can try Note: I had built up thru gmp-ch6 which is in the chroot Intending to umount and roll back, I get: df -ha FilesystemSize Used Avail Use% Mounted on /dev/sda11 11G 7.6G 2.7G 74% / /proc0 0 0 - /proc sysfs0 0 0 - /sys devpts 0 0 0 - /dev/pts tmpfs 760M 0 760M 0% /dev/shm /dev/sdd105.1G 2.0G 2.9G 40% /mnt/lfs /dev 760M 240K 759M 1% /mnt/lfs/dev devpts 0 0 0 - /mnt/lfs/dev/pts shm 760M 0 760M 0% /mnt/lfs/dev/shm proc 0 0 0 - /mnt/lfs/proc sysfs0 0 0 - /mnt/lfs/sys r...@lfs:~# umount /mnt/lfs/sys r...@lfs:~# umount /mnt/lfs/proc r...@lfs:~# umount /mnt/lfs/dev/shm r...@lfs:~# umount /mnt/lfs/dev/pts r...@lfs:~# umount /mnt/lfs/dev r...@lfs:~# umount /mnt/lfs umount /mnt/lfs Segmentation fault And triggers some kernel bug(?) in sys.log: Nov 23 22:20:57 lfs kernel: sb orphan head is 131076 Nov 23 22:20:57 lfs kernel: sb_info orphan list: Nov 23 22:20:57 lfs kernel: inode sdd10:131076 at d5762128: mode 100600, nlink 0, next 131075 Nov 23 22:20:57 lfs kernel: inode sdd10:131075 at eec1a64c: mode 100600, nlink 0, next 0 Nov 23 22:20:57 lfs kernel: [ cut here ] Nov 23 22:20:57 lfs kernel: kernel BUG at fs/ext3/super.c:435! Nov 23 22:20:57 lfs kernel: invalid opcode: [#1] Nov 23 22:20:57 lfs kernel: last sysfs file: /sys/devices/pci:00/:00:01.0/:01:00.0/resource Nov 23 22:20:57 lfs kernel: Modules linked in: usblp snd_ens1371 Nov 23 22:20:57 lfs kernel: Nov 23 22:20:57 lfs kernel: Pid: 22478, comm: umount Not tainted (2.6.31.4-noremap #2) System Name Nov 23 22:20:57 lfs kernel: EIP: 0060:[c10c2926] EFLAGS: 00010216 CPU: 0 Nov 23 22:20:57 lfs kernel: EIP is at ext3_put_super+0x1f6/0x200 Nov 23 22:20:57 lfs kernel: EAX: d5762108 EBX: f687a320 ECX: EDX: f687a320 Nov 23 22:20:57 lfs kernel: ESI: f687a260 EDI: f689c800 EBP: c3a4df10 ESP: c3a4dee4 Nov 23 22:20:57 lfs kernel: DS: 007b ES: 007b FS: GS: 0033 SS: 0068 Nov 23 22:20:57 lfs kernel: Process umount (pid: 22478, ti=c3a4c000 task=f64124f0 task.ti=c3a4c000) Nov 23 22:20:57 lfs kernel: Stack: Nov 23 22:20:57 lfs kernel: c13e0d58 f689c950 00020003 eec1a64c 8180 f687a320 Nov 23 22:20:57 lfs kernel: 0 f689c800 c13365c0 f700eea0 c3a4df28 c107208d f6d7f400 Nov 23 22:20:57 lfs kernel: 0 0003 c3a4df38 c1072135 f689c800 c145bf40 c3a4df48 c10725a7 f700eea0 Nov 23 22:20:57 lfs kernel: Call Trace: Nov 23 22:20:57 lfs kernel: [c107208d] ? generic_shutdown_super+0x4d/0xd0 Nov 23 22:20:57 lfs kernel: [c1072135] ? kill_block_super+0x25/0x40 Nov 23 22:20:57 lfs kernel: [c10725a7] ? deactivate_super+0x37/0x50 Nov 23 22:20:57 lfs kernel: [c1084eb0] ? mntput_no_expire+0x50/0x60 Nov 23 22:20:57 lfs kernel: [c108512f] ? sys_umount+0x4f/0x2d0 Nov 23 22:20:57 lfs kernel: [c10853c7] ? sys_oldumount+0x17/0x20 Nov 23 22:20:57 lfs kernel: [c1002d48] ? sysenter_do_call+0x12/0x26 Nov 23 22:20:57 lfs kernel: Code: 00 00 89 44 24 04 e8 eb f5 25 00 8b 45 f0 8b 00 89 45 f0 89 c2 8b 00 0f 18 00 90 39 d3 75 9b 3b 9e c0 00 00 00 0f 84 96 fe ff ff 0f 0b eb fe 8d b6 00 00 00 00 55 89 e5 56 53 89 c3 83 ec 08 8b Nov 23 22:20:57 lfs kernel: EIP: [c10c2926] ext3_put_super+0x1f6/0x200 SS:ESP 0068:c3a4dee4 Nov 23 22:20:57 lfs kernel: ---[ end trace a11c2efe1c36f7b4 ]--- Nov 23 22:20:57 lfs kernel: [ cut here ] Nov 23 22:20:57 lfs kernel: WARNING: at kernel/exit.c:895 do_exit+0x4df/0x5e0() Nov 23 22:20:57 lfs kernel: Hardware name: System Name Nov 23 22:20:57 lfs kernel: Modules linked in: usblp snd_ens1371 Nov 23 22:20:57 lfs kernel: Pid: 22478, comm: umount Tainted: G D 2.6.31.4-noremap #2 Nov 23 22:20:57 lfs kernel: Call Trace: Nov 23 22:20:57 lfs kernel: [c1321f09] ? printk+0x18/0x1a Nov 23 22:20:57 lfs kernel: [c102531f] ? do_exit+0x4df/0x5e0 Nov 23 22:20:57 lfs kernel: [c10222bc] warn_slowpath_common+0x6c/0xc0 Nov 23 22:20:57 lfs kernel: [c102531f] ? do_exit+0x4df/0x5e0 Nov 23 22:20:57 lfs kernel: [c1022325] warn_slowpath_null+0x15/0x20 Nov 23 22:20:57 lfs kernel: [c102531f] do_exit+0x4df/0x5e0 Nov 23 22:20:57 lfs kernel: [c1003389] ? common_interrupt+0x29/0x30 Nov 23 22:20:57 lfs kernel: [c1321f09] ? printk+0x18/0x1a Nov 23 22:20:57 lfs kernel: [c10221ef] ? oops_exit+0x2f/0x40 Nov 23 22:20:57 lfs kernel: [c1005e15] oops_end+0x85/0x90 Nov 23 22:20:57 lfs kernel: [c1005f90] die+0x50/0x70 Nov 23 22:20:57 lfs kernel: [c1003871] do_trap+0x91/0xd0 Nov 23 22:20:57 lfs kernel: [c1003c70] ? do_invalid_op+0x0/0xa0 Nov 23 22:20:57 lfs kernel: [c1003cf7] do_invalid_op+0x87/0xa0 Nov 23 22:20:57 lfs kernel: [c10c2926] ? ext3_put_super+0x1f6/0x200 Nov 23 22:20:57 lfs kernel: [c10224eb] ?
Re: Segmentation fault after stripping
linux fan wrote: On 11/23/09, Bruce Dubbs wrote: To check things out a little more, you can try Note: I had built up thru gmp-ch6 which is in the chroot Intending to umount and roll back, I get: df -ha FilesystemSize Used Avail Use% Mounted on /dev/sda11 11G 7.6G 2.7G 74% / /proc0 0 0 - /proc sysfs0 0 0 - /sys devpts 0 0 0 - /dev/pts tmpfs 760M 0 760M 0% /dev/shm /dev/sdd105.1G 2.0G 2.9G 40% /mnt/lfs /dev 760M 240K 759M 1% /mnt/lfs/dev devpts 0 0 0 - /mnt/lfs/dev/pts shm 760M 0 760M 0% /mnt/lfs/dev/shm proc 0 0 0 - /mnt/lfs/proc sysfs0 0 0 - /mnt/lfs/sys r...@lfs:~# umount /mnt/lfs/sys r...@lfs:~# umount /mnt/lfs/proc r...@lfs:~# umount /mnt/lfs/dev/shm r...@lfs:~# umount /mnt/lfs/dev/pts r...@lfs:~# umount /mnt/lfs/dev r...@lfs:~# umount /mnt/lfs umount /mnt/lfs Segmentation fault I really don't know what's causing this. It looks like you exited chroot and umounted from there. That would mean that the host system caused the segfault. It wouldn't have anything to do with the latest build. It could be a hw error of some kind if you are getting segfaults both inside and outside chroot. Have you tried booting int memtest86+ and checking your memory? -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: Segmentation fault after stripping
On 11/24/09, Bruce Dubbs wrote: Have you tried booting int memtest86+ and checking your memory? I don't know whereis or howto memtest86+. I guess this will be a multi-day adventure. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
