With Adrian's prodding, I've gotten a capture of the boot process when
I boot a newly built 2.4.17 from CVS (Jan 5 2002ish) at oss.sgi.org.
I'm sendign this to the xfs list only -- I can send it to more places
if this is not the appropriate place to do so.
2.4.9 is working fine. 2.4.17 fails to bood during the change_root
phase. Back trace from kdb:
Console just before oops:
RAMDISK: Compressed image found at block 0
Freeing initrd memory: 1135k freed
VFS: Mounted root (ext2 filesystem).
Mounted devfs on /dev
LVM version 1.0.1-rc4(ish)(03/10/2001) module loaded
cramfs: wrong magic
lvm -- lvm_blk_ioctl: unknown command 0x5310
XFS mounting filesystem lvm(58,0)
VFS: Mounted root (xfs filesystem) readonly.
devfs: devfs_do_symlink(root): could not append to parent, err: -17
change_root: old root has d_count=2
Entering kdb (current=0xc1a08000, pid 1) Oops: invalid operand
due to oops @ 0xc0126cda
kdb> bt
EBP EIP Function(args)
0xc1a09f14 0xc0126cda kmem_cache_create+0x2b6 (0xc02fe1c7, 0x14, 0x20, 0x20000,
0x0)
kernel .text 0xc0100000 0xc0126a24 0xc0126d1c
0xc1a09f34 0xc041f9a3 mount_devfs_fs+0x17 (0xc02f4cc0, 0x2, 0xffffff9e, 0xffffff
ff, 0x10)
kernel .text.init 0xc0418000 0xc041f98c 0xc041fa0
0
0xc1a09fb8 0xc041f1b9 change_root+0xf9 (0x0, 0xc02ed7a3)
kernel .text.init 0xc0418000 0xc041f0c0 0xc041f32
0
0xc1a09fdc 0xc0105239 prepare_namespace+0x12d
kernel .text 0xc0100000 0xc010510c 0xc0105258
0xc1a09fec 0xc0105267 init+0xf
kernel .text 0xc0100000 0xc0105258 0xc0105370
0xc01056e4 kernel_thread+0x28
kernel .text 0xc0100000 0xc01056bc 0xc01056f4
output from ksymoops:
ksymoops 2.4.3 on i686 2.4.9-xfs-lvm. Options used
-V (specified)
-K (specified)
-l /proc/modules (default)
-o /lib/modules/2.4.17-xfs-lvm (specified)
-m /boot/System.map-2.4.17-xfs-lvm (specified)
No modules in ksyms, skipping objects
No ksyms, skipping lsmod
invalid operand: 0000
CPU: 0
EIP: 0010:[<c0126cda>] Not tainted
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010246
eax: 00000000 ebx: c1a765b0 ecx: c1a76618 edx: c1a765a8
esi: c1a765a1 edi: c02fe1d4 ebp: c1a09f14 esp: c1a09ef4
ds: 0018 es: 0018 ss: 0018
Process swapper (pid: 1, stackpage=c1a09000)
Stack: c1a09f64 e7ec2360 c1aaf4ce c1a09f10 c1a765d0 c0464ee8 00000004 0000000c
c1a09f34 c041f9a3 c02fe1c7 00000014 00000020 00020000 00000000 00000000
c1a09fb8 c041f1b9 c02f4cc0 00000002 ffffff9e ffffffff 00000010 c1a09fd8
Call Trace: [<c01169e6>] [<c0106e33>] [<c0105239>] [<c0105267>] [<c01056e4>]
Code: 0f 0b 8b 12 81 fa 88 92 3f c0 75 da a1 88 92 3f c0 89 48 04
>>EIP; c0126cda <kmem_cache_create+2b6/2f8> <=====
Trace; c01169e6 <sys_waitpid+16/20>
Trace; c0106e32 <system_call+32/40>
Trace; c0105238 <prepare_namespace+12c/14c>
Trace; c0105266 <init+e/118>
Trace; c01056e4 <kernel_thread+28/38>
Code; c0126cda <kmem_cache_create+2b6/2f8>
00000000 <_EIP>:
Code; c0126cda <kmem_cache_create+2b6/2f8> <=====
0: 0f 0b ud2a <=====
Code; c0126cdc <kmem_cache_create+2b8/2f8>
2: 8b 12 mov (%edx),%edx
Code; c0126cde <kmem_cache_create+2ba/2f8>
4: 81 fa 88 92 3f c0 cmp $0xc03f9288,%edx
Code; c0126ce4 <kmem_cache_create+2c0/2f8>
a: 75 da jne ffffffe6 <_EIP+0xffffffe6> c0126cc0
<kmem_cache_create+29c/2f8>
Code; c0126ce6 <kmem_cache_create+2c2/2f8>
c: a1 88 92 3f c0 mov 0xc03f9288,%eax
Code; c0126cea <kmem_cache_create+2c6/2f8>
11: 89 48 04 mov %ecx,0x4(%eax)
<0>Kernel panic: Attempted to kill init!
Some config info:
System (from proc):
model name : Pentium III (Katmai)
stepping : 2
cpu MHz : 501.149
MemTotal: 640512 kB
2 Promise controllers:
Bus 0, device 13, function 0:
Unknown mass storage controller: Promise Technology, Inc. 20267 (rev 2).
Bus 0, device 15, function 0:
Unknown mass storage controller: Promise Technology, Inc. 20267 (#2) (rev 2)
4 Maxtor hard drives:
hde: Maxtor 54610H6, ATA DISK drive
hdg: Maxtor 54610H6, ATA DISK drive
hdi: Maxtor 54610H6, ATA DISK drive
hdk: Maxtor 54610H6, ATA DISK drive
I'm using MD to get a RAID1 for my maxtor drives:
/dev/md1 is a slice from hde and hdg and makes up /boot
/dev/md2 is a slice from hde and hdg and makes up a swap partition
/dev/md3 is a slice from hde and hdg and makes up one PV for the LVM
/dev/md4 is a slice from hdi and hdk and makes up a swap partition
/dev/md5 is a slice from hdi and hdk and makes up one PV for the LVM
I'm using LVM for all partitions other than /boot. This means that I
also use LVM for my root partition. I'm using a initrd made with
lvmcreate_initrd from debian's lvm10 package (1.0.1release-1).
I have one volume group (shaktivg).
Attached are my config and the full capture of the boot process.
config-2.4.17-xfs-lvm
Description: config
boot.txt
Description: boot log
--
-rupa
|