boot problem LFS 6.5
I went through the lfs 6.5 book and copied and pasted all the commands in the book to a series of shell scripts. I only made changes where it was necessary like with stuff like hda1 and hda5 other than that I left the commands in the book in tact. I used two partitions hda1 and hda5. The lfs build was done on an empty drive (with no installed OS on the machine) using the lfs 6.3 LiveCD the last release of that LiveCD. I had no compilation errors and no problems until I tried to boot. My problem originated with a problem addressed here: FAQ Kernel panic: VFS: unable to mount root fs So I checked everything and even compiled the kernel again (3 more times) to make sure and got the same kernel panic telling me the same thing. I also ran the grub configuration 4 times: at the grub prompt root (hd0,0) setup (hd0) My HDD is hda1 and in Grub I had: title LFS 6.5 root (hd0,0) kernel /boot/lfskernel-2.6.30.2 root=/dev/hda1 The kernel panic error was telling me to correct the root= part of the grub menu.lst. It was telling me to use sda1 instead of hda1 (why I don't know). So I tried that to see what would happen. title LFS 6.5 root (hd0,0) kernel /boot/lfskernel-2.6.30.2 root=/dev/sda1 I got a new set of errors and I have not been able to find anything that addresses the problem. The new series of errors are: sawpon: /dev/hda5: stat failed: No such file or directory mounting root file system in read-only mode... Checking file systems... fsck.ext3: No such file or directory while trying to open /dev/hda1 /dev/hda1: The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 device Then it said it has to be fixed manually and to press enter so the machine will stop and be powered off. I have no idea what to do now. If I change grub back to hda1 like I had it then I get the kernel panic, if I leave grub set as root=/dev/sda1 then I get the swap and ext3 problem. So where and what is the problem? Where did I make my mistake? -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: boot problem LFS 6.5
Hi, I had a similar problem and the solution was to recompile the kernel with the correct driver for the hard disk. In my case the hard disk was a vmware partition. In your case seems that the kernel can't read the hda1. If you can, try to do an lspci and look for what HD you have than check you kernel conf file if the driver is set =yes. Hope helps. Simone 2009/11/23 stosss sto...@gmail.com I went through the lfs 6.5 book and copied and pasted all the commands in the book to a series of shell scripts. I only made changes where it was necessary like with stuff like hda1 and hda5 other than that I left the commands in the book in tact. I used two partitions hda1 and hda5. The lfs build was done on an empty drive (with no installed OS on the machine) using the lfs 6.3 LiveCD the last release of that LiveCD. I had no compilation errors and no problems until I tried to boot. My problem originated with a problem addressed here: FAQ Kernel panic: VFS: unable to mount root fs So I checked everything and even compiled the kernel again (3 more times) to make sure and got the same kernel panic telling me the same thing. I also ran the grub configuration 4 times: at the grub prompt root (hd0,0) setup (hd0) My HDD is hda1 and in Grub I had: title LFS 6.5 root (hd0,0) kernel /boot/lfskernel-2.6.30.2 root=/dev/hda1 The kernel panic error was telling me to correct the root= part of the grub menu.lst. It was telling me to use sda1 instead of hda1 (why I don't know). So I tried that to see what would happen. title LFS 6.5 root (hd0,0) kernel /boot/lfskernel-2.6.30.2 root=/dev/sda1 I got a new set of errors and I have not been able to find anything that addresses the problem. The new series of errors are: sawpon: /dev/hda5: stat failed: No such file or directory mounting root file system in read-only mode... Checking file systems... fsck.ext3: No such file or directory while trying to open /dev/hda1 /dev/hda1: The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 device Then it said it has to be fixed manually and to press enter so the machine will stop and be powered off. I have no idea what to do now. If I change grub back to hda1 like I had it then I get the kernel panic, if I leave grub set as root=/dev/sda1 then I get the swap and ext3 problem. So where and what is the problem? Where did I make my mistake? -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
menu.lst and fstab
Also for the record the book LFS 6.5 does not tell you that the entries in menu.lst and fstab need to be sd now and not hd. LFS 6.5 chapter 8.4.2 the last entry before EOF should be sdxx and not hdxx cat boot/grub/menu.lst EOF # Begin /boot/grub/menu.lst # By default boot the first menu entry. default 0 # Allow 30 seconds before booting the default. timeout 30 # Use prettier colors. color green/black light-green/black # The first entry is for LFS. title LFS 6.5 root (hd0,0) kernel /boot/lfskernel-2.6.30.2 root=/dev/sda1 EOF LFS 6.5 chapter 8.2 the /dev/hd should be /dev/sd cat /etc/fstab EOF # Begin /etc/fstab # file system mount-point type options dump fsck #order /dev/sda1 /ext3 defaults1 1 /dev/sda5 swap swap pri=1 0 0 proc /procproc defaults0 0 sysfs /sys sysfs defaults0 0 devpts /dev/pts devpts gid=4,mode=620 0 0 tmpfs /dev/shm tmpfs defaults0 0 # End /etc/fstab EOF Once I changed these entries with the help of Paul my LFS system booted with no problem. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: grub problem
On Monday 23 November 2009 21:27:37 su.sinnes wrote: Hi im stuck with grub, as soon as i restart i get into the grub shell and when i type boot it says no loaded kernel. but if i do: 1) made a file under /boot/grub/device.map as Bruce (hd0) /dev/sda 2) grub-install --root-directory=/boot/ /dev/sda 3) grub-mkconfig -o /boot/boot/grub/grub.cfg then it boots up and i get a kernel panic , not syncing:VFS:unable to mount root fs on unknown-block(2,0) i have recompiled the kernel 4 times now and i have selected all SATA drivers, and ext 2 filesystem. but no luck. Anyone got any ideas? Thank you. Can you show me the last few lines of the screen when the machine hangs? signature.asc Description: This is a digitally signed message part. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: menu.lst and fstab
On Monday November 23 2009 05:19:32 am stosss wrote: Also for the record the book LFS 6.5 does not tell you that the entries in menu.lst and fstab need to be sd now and not hd. It really depends on how you build your kernel; hd* is still valid, as far as I'm aware. -- Trent. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: KDE4 kdebase-workspace compile error
On Sunday November 22 2009 11:58:26 pm Simon Geard wrote: I'm afraid I can't be more specific, but it may be that your X libraries are too old for KDE (or less likely, too new). I can confirm the 4.3 branch built against Xorg-7.5 for me. -- Trent. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: 8.4. GRUB-0.97
I solved that problem by doing this:
grub-install --root-directory=/boot/ /dev/sda
grub-mkconfig -o /boot/boot/grub/grub.cfg
but now i got a new problem.
kernel panic , not syncing:VFS:unable to mount root
fs on unknown-block(2,0)
I read that i might need to install SATA drivers for it to work.
i recompiled the kernel with alla drivers named SATA i could find, but
no luck.
Anyone got any ideas?
Thanks for all the help.
-Original Message-
From: Bruce Dubbs bruce.du...@gmail.com
To: LFS Support List lfs-support@linuxfromscratch.org
Sent: Fri, Nov 20, 2009 8:11 pm
Subject: Re: 8.4. GRUB-0.97
linux fan wrote:
On 11/20/09, su.sin...@mail.com su.sin...@mail.com wrote:
What should i do now?
menuentry GNU/Linux, Linux 2.6.30.2 {
insmod ext2
set root=(hd0,1)
search --no-floppy --fs-uuid --set
e4adbac2-a338-4305-bafe-73f2adb307da
linux/boot/vmlinux-2.6.30.2 root=/dev/sda1 ro
}
What is output of this command:
find /boot -maxdepth 1 -type f
It should show /boot/vmlinux-2.6.30.2 and if it doesn't, something is
not in the right place.
What is the output of 'mount' ?
What is the output of 'ls /dev/sd*' ?
What is the output of 'ls -l /boot' ?
You can remove the search line above. It is not valid for LFS.
-- Bruce
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
Re: LFS 6.5 chapter 8.4.2
On 11/23/2009 07:06 AM, stosss wrote: Just for the record. The grub configuration commands won't work in chroot. They do work when you get out of chroot. There is nothing in the chapter to tell you to do that. Yes they do. If they didn't work for you, my guess is that /dev probably wasn't mounted. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: boot problem LFS 6.5
stosss wrote:
All Right! I did what you suggested and now I have a command prompt!
Congratulations on being a new LFS user!
Three cheers!
Mike
--
p=p=%c%s%c;main(){printf(p,34,p,34);};main(){printf(p,34,p,34);}
Oppose globalization and One World Governments like the UN.
This message made from 100% recycled bits.
You have found the bank of Larn.
I speak only for myself, and I am unanimous in that!
--
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: UDEV - Not Leaving Well Enough Alone
Alex:
In the past, I was able to avoid creation
of unnecessary fd nodes.
Mike McCarty:
In what sense unnecessary?
Do your floppy drives not support those modes?
There are tools which use the name of the device
to select their mode of operation, and
if you don't have a /dev node for that then they
don't operate properly or even refuse to operate.
...
I have encountered some which don't respond to what
setfdprm does.
Hello Mike,
Thank you very much for your comments.
SHORT ANSWER
Unnecessarily from _my_ standpoint (obviously limited).
GORY DETAILS (in the order of increasing blood content)
1. I do happen to have 'setfdprm', a carry over from
my original 2005-LFS system (on two machines - mirrored)
I've never used it nor do I foresee a need in the future.
No mode tools have ever failed on me, to my recollection.
Not that I ever used them consciously.
2. For reference
01/20/2005 util-linux-2.12qMy setfdprm version
09/23/2005 util-linux-2.12rLast of the series
The new ng series no longer contain 'setfdprm'
(by accident??):
09/10/2008 util-linux-ng-2.14.1My version
09/07/2009 util-linux-ng-2.16 Latest non-rc
3. Each of my two machines has a garden-variety floppy.
In Linux, I use them regularly with various size floppies,
360, 720 but, by far, 1440. The numerous floppy drives
I've encountered just accepted/read the floppies.
Never a need to change the mode.
The last thing is to start a flame here; I still see a
need for floppies on Linux due to the relatively small
sizes of files in need to be quickly sneakered among
machines.
I also understand the people who rave and rant against
using floppies at this day and age (God Bless'em).
I would also understand someone who still uses/needs
cmos/setfdprm/modes if I ever hear a real case in the
developed world (Got Bless her too, in advance).
4. As I said, I'll personally be just fine with only
'/dev/fd0' for the rest of my Linux life.
HOWEVER, modes or no modes, my actual
POINT has been that the situation when last_rule
existed, while ugly, was manageable for me.
Once that OPTION was arbitrarily eliminated
(Its use breaks too many things ...) everything
becomes a nightmare (in relative terms :) for me,
with the ATTRS{cmos} rule imposed by the UDEV
developers (and reinforced by LFS) as a default.
That's why I hoped someone might know another
semi-permanent workaround in the 147+ world.
5. My bad luck (I suppose, like many others who use
a floppy as a floppy - like me) is that the mostly
intractable by mere mortals, the '/sys' file system,
has a file '/sys/devices/platform/floppy.0/cmos'
with a mysterious content, one byte of value ASCII 4.
This makes my system(s) eligible for the famous
cmos rule, whether I like it or not, or whether
99% of the population couldn't tell a CMOS floppy
drive from a hole in the ground.
Thanks again,
-- Alex
PS. If someone (a System Administrator?) could help
and delete my FIRST post (the one without the
Hello NOTE disclaimer.), that'd mean a lot to me.
It's obviously been a disgrace and a confusion.
I was testing if my Verizon (as opposed to GMail)
had acceptable plain text I could use.
Unfortunately, the self-test went awry and the draft
escaped into the world wide web.
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
Re: menu.lst and fstab
I went through the menuconfig 4 times. Compiling/not compiling scsi made no difference when it came to error I was getting. I am not at the computer now and won't be for several more hours. Where is the setting and why did changing the two files and three entries from hd to sd work? I don't have any scsi drives on that box. On Nov 23, 2009 10:29 AM, Trent Shea trent.s...@gmail.com wrote: On Monday November 23 2009 05:19:32 am stosss wrote: Also for the record the book LFS 6.5 does not... It really depends on how you build your kernel; hd* is still valid, as far as I'm aware. -- Trent. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page -- 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
