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
Filesystem            Size  Used Avail Use% Mounted on
/dev/sda11             11G  7.6G  2.7G  74% /
/proc                    0     0     0   -  /proc
sysfs                    0     0     0   -  /sys
devpts                   0     0     0   -  /dev/pts
tmpfs                 760M     0  760M   0% /dev/shm
/dev/sdd10            5.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
sysfs                    0     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: 0000 [#1]
Nov 23 22:20:57 lfs kernel: last sysfs file:
/sys/devices/pci0000:00/0000:00:01.0/0000: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: ffffffff
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: 0000 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
00008180 00000000 00000000 f687a320
Nov 23 22:20:57 lfs kernel: <0> f689c800 c13365c0 f700eea0 c3a4df28
c107208d 00000000 ffffffff f6d7f400
Nov 23 22:20:57 lfs kernel: <0> 00000003 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>] ? _call_console_drivers+0x4b/0x90
Nov 23 22:20:57 lfs kernel:  [<c1322946>] ? out_of_line_wait_on_bit+0xd6/0xf0
Nov 23 22:20:57 lfs kernel:  [<c1033fc0>] ? wake_bit_function+0x0/0x60
Nov 23 22:20:57 lfs kernel:  [<c132396e>] error_code+0x5e/0x64
Nov 23 22:20:57 lfs kernel:  [<c1003c70>] ? do_invalid_op+0x0/0xa0
Nov 23 22:20:57 lfs kernel:  [<c10c2926>] ? ext3_put_super+0x1f6/0x200
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: ---[ end trace a11c2efe1c36f7b5 ]---

Also in sys.log, I see again:
Nov 23 18:43:28 lfs kernel: Maximum lock depth 1024 reached task:
ld-linux.so.2 (10679)

What is lock depth? Is that a problem? How to fix?

I can
 A. try a different disk if you think it is the disk.
 B. build a diffenent kernel if you think it is the kernel.

The host system is LFS-6.4
uname -a
Linux lfs 2.6.31.4-noremap #2 Sun Oct 18 17:31:07 EDT 2009 i686
pentium3 i386 GNU/Linux

This same system was used as a host to build a LFS-6.3 last month
without having any problems.
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Reply via email to