Kosolapov Dmitry
2006-Apr-09 07:20 UTC
[syslinux] Switchroot: mount failed: 22, Kernel panic - not syncing: Attempted tp kill init!
Hi, everybody! My pxelinux.0/default file is: LABEL linux KERNEL vmlinuz-2.6.16 APPEND initrd=initrd-2.6.16.img root=192.168.4.110:/clients/192.168.4.100/root When mounting I get: switchroot: mount failed: 22 Kernel panic - not syncing: Attempted tp kill init! Before it I get some messages about: Can't find /dev/console. /clients/192.168.4.100/root/dev was empty. I've copied my /dev to /clients/192.168.4.100/root/dev/ but the errors weren't fixed. What is the problem with mounting? Thanks advance. PS. I do everything according to FM at linux-mag.com
Eli Stair
2006-Apr-09 07:32 UTC
[syslinux] Switchroot: mount failed: 22, Kernel panic - not syncing: Attempted tp kill init!
Guess: your kernel was built with an initramfs that contains an init script... the init script is doing a switch_root to some hardcoded/defined/detected local device which doesn't exist (or isn't bootable) in your situation. I'm _guessing_ that you're trying to do an old-school nfsroot mount. That doesn't work anymore, as of 2.6.15. See: ramfs-rootfs-initramfs.txt Or I could be entirely off base, I'm basing this scenario on the little info you gave... not sure that "root=IP" does in fact do anything. (nfsroot= maybe?) Most likely, this doesn't come down to an issue with syslinux, it seems to have done its job :) /eli -----Original Message----- From: syslinux-bounces at zytor.com on behalf of Kosolapov Dmitry Sent: Sun 4/9/2006 12:20 AM To: SYSLINUX at zytor.com Subject: [syslinux] Switchroot: mount failed: 22, Kernel panic - not syncing: Attempted tp kill init! Hi, everybody! My pxelinux.0/default file is: LABEL linux KERNEL vmlinuz-2.6.16 APPEND initrd=initrd-2.6.16.img root=192.168.4.110:/clients/192.168.4.100/root When mounting I get: switchroot: mount failed: 22 Kernel panic - not syncing: Attempted tp kill init! Before it I get some messages about: Can't find /dev/console. /clients/192.168.4.100/root/dev was empty. I've copied my /dev to /clients/192.168.4.100/root/dev/ but the errors weren't fixed. What is the problem with mounting? Thanks advance. PS. I do everything according to FM at linux-mag.com _______________________________________________ SYSLINUX mailing list Submissions to SYSLINUX at zytor.com Unsubscribe or set options at: http://www.zytor.com/mailman/listinfo/syslinux Please do not send private replies to mailing list traffic.
Kosolapov Dmitry
2006-Apr-09 08:02 UTC
[syslinux] Switchroot: mount failed: 22, Kernel panic - not syncing: Attempted tp kill init!
Eli Stair wrote:> > Guess: your kernel was built with an initramfs that contains an init > script... the init script is doing a switch_root to some > hardcoded/defined/detected local device which doesn't exist (or isn't > bootable) in your situation. I'm _guessing_ that you're trying to do an > old-school nfsroot mount. That doesn't work anymore, as of 2.6.15. > > See: ramfs-rootfs-initramfs.txt > > Or I could be entirely off base, I'm basing this scenario on the little > info you gave... not sure that "root=IP" does in fact do anything. > (nfsroot= maybe?) Most likely, this doesn't come down to an issue with > syslinux, it seems to have done its job > > :) > > /eliThe verbose of my booting: Mounting root filesystem: mount: error 6 mounting ext3 Switching to newroot Error opening /dev/console !!!!: 2 error dup2' ing fd of 0 to 0 error dup2' ing fd of 0 to 1 error dup2' ing fd of 0 to 2 unmounting old /proc unmounting old /sys switchroot: mount failed: 22 Kernel panic - not syncing: Attempted tp kill init! Now my /tftpboot/pxelinux.cfg/default is: LABEL linux KERNEL vmlinuz-2.6.16 APPEND initrd=initrd-2.6.16.img nfsroot=192.168.4.110:/clients/192.168.4.100/root My /etc/exports is: /clients/192.168.4.100/root *(rw,no_root_squash) /clients/192.168.4.100/usr *(rw,no_root_squash) /clients/192.168.4.100/var *(rw,no_root_squash) /clients/192.168.4.100/tmp *(rw,no_root_squash) /home *(rw) Client's fstab (/clients/192.168.4.100/root/etc/fstab) is: 192.168.4.110:/clients/192.168.4.100/root / nfs rw,hard,intr,nolock 0 0 192.168.4.110:/clients/192.168.4.100/usr /usr nfs rw,hard,intr,nolock 0 0 192.168.4.110:/clients/192.168.4.100/var /var nfs rw,hard,intr,nolock 0 0 192.168.4.110:/clients/192.168.4.100/tmp /tmp nfs rw,hard,intr,nolock 0 0 192.168.4.110:/home /home nfs rw,hard,intr,nolock 0 0 /clients/192.168.4.100/root has 777-chmoded -R And I used my system kernel 2.6.16 (because my own compiled didn't booted at all) and system initrd. Thanks advance.
Kosolapov Dmitry
2006-Apr-09 08:53 UTC
[syslinux] Switchroot: mount failed: 22, Kernel panic - not syncing: Attempted tp kill init!
Eli Stair wrote:> > Guess: your kernel was built with an initramfs that contains an init > script... the init script is doing a switch_root to some > hardcoded/defined/detected local device which doesn't exist (or isn't > bootable) in your situation. I'm _guessing_ that you're trying to do an > old-school nfsroot mount. That doesn't work anymore, as of 2.6.15. > > See: ramfs-rootfs-initramfs.txt > > Or I could be entirely off base, I'm basing this scenario on the little > info you gave... not sure that "root=IP" does in fact do anything. > (nfsroot= maybe?) Most likely, this doesn't come down to an issue with > syslinux, it seems to have done its job > > :) > > /eliAnd problem may be in kernel 2.6.16. # lsmod nfsd 223825 15 exportfs 9921 1 nfsd lockd 63145 2 nfsd nfs_acl 7745 1 nfsd ipv6 270081 18 parport_pc 31149 1 lp 16897 0 parport 40073 2 parport_pc,lp autofs4 23365 1 rfcomm 45141 0 l2cap 32833 5 rfcomm bluetooth 56357 4 rfcomm,l2cap sunrpc 150373 11 nfsd,lockd,nfs_acl video 19141 0 button 10577 0 battery 13381 0 ac 8901 0 ohci1394 38917 0 ieee1394 300697 1 ohci1394 ohci_hcd 25949 0 ehci_hcd 36429 0 snd_intel8x0 36061 0 snd_ac97_codec 92769 1 snd_intel8x0 snd_ac97_bus 6465 1 snd_ac97_codec snd_seq_dummy 7749 0 snd_seq_oss 35365 0 snd_seq_midi_event 11201 1 snd_seq_oss snd_seq 54413 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event snd_seq_device 13005 3 snd_seq_dummy,snd_seq_oss,snd_seq snd_pcm_oss 52721 0 snd_mixer_oss 21441 1 snd_pcm_oss snd_pcm 88517 3 snd_intel8x0,snd_ac97_codec,snd_pcm_oss snd_timer 28101 2 snd_seq,snd_pcm snd 56353 9 snd_intel8x0,snd_ac97_codec,snd_seq_oss,snd_seq, snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer soundcore 13729 1 snd snd_page_alloc 14665 2 snd_intel8x0,snd_pcm r8169 33993 0 dc395x 38609 0 dm_snapshot 20717 0 dm_zero 6081 0 dm_mirror 25205 0 ext3 133705 2 jbd 60885 1 ext3 dm_mod 57429 6 dm_snapshot,dm_zero,dm_mirror sata_sis 11973 0 libata 62801 1 sata_sis sd_mod 22081 0 scsi_mod 136013 3 dc395x,libata,sd_mod So ext3-support is module and we can't do remote mount of this FS. But, when I've compiled my own static kernel (without modules) and tried to boot it remotely I got error: Image is corrupted. It even didn't try to download to the client PC. My actions before: when kernel was compiled, I put it into /tftpboot Nothing more. What should I do? Is problem actually in it?
Geert Stappers
2006-Apr-09 23:07 UTC
[syslinux] Switchroot: mount failed: 22, Kernel panic - not syncing: Attempted tp kill init!
On Sun, Apr 09, 2006 at 06:20:08PM +1100, Kosolapov Dmitry wrote:> Hi, everybody! > > My pxelinux.0/default file is: > > LABEL linux > KERNEL vmlinuz-2.6.16 > APPEND initrd=initrd-2.6.16.img > root=192.168.4.110:/clients/192.168.4.100/rootAPPEND initrd=initrd-2.6.16.img root=/dev/ram> When mounting I get: > > switchroot: mount failed: 22 > Kernel panic - not syncing: Attempted tp kill init! > > Before it I get some messages about: Can't find /dev/console. > /clients/192.168.4.100/root/dev was empty.Seems like you assume that the client does do NFS and you can monitor it at the NFS-server. That only works if the client is actual doing NFS ...> I've copied my /dev to > /clients/192.168.4.100/root/dev/ but the errors weren't fixed.Copying /dev ???> What is the problem with mounting? Thanks advance. > > PS. I do everything according to FM at linux-mag.comPlease provide a deep link to the Fantastic Manual at linux-mag.com. Cheers Geert Stappers
Jim Cromie
2006-Apr-14 03:23 UTC
[syslinux] Switchroot: mount failed: 22, Kernel panic - not syncing: Attempted tp kill init!
Kosolapov Dmitry wrote:> Hi, everybody! > > My pxelinux.0/default file is: > > LABEL linux > KERNEL vmlinuz-2.6.16 > APPEND initrd=initrd-2.6.16.img > root=192.168.4.110:/clients/192.168.4.100/root > >either you or mailer has wrapped that line. (you cannot). you also cannot do shell-style \ line continuations like \ these. Also, you cannot use both global and per-item APPENDs.> When mounting I get: > > switchroot: mount failed: 22 > Kernel panic - not syncing: Attempted tp kill init! > >do you actually need an initrd ? Ive had one in my pxelinux.cfg/default file since ~ 2.6.11, and the same entries worked until 2.6.16, at which point I got errors like yours. The light bulb went on when I realized the initrd was running Redhat nash, on a debian box - IOW, the initrd was made on/for my FC-4 laptop, where I built kernels for the 266mhz debian box. Once I removed the initrd=foo part of the APPEND, it just worked. Forex, this works here. LABEL C 2.6.16-sk MENU LABEL ^c. 2.6.16-sk KERNEL vmlinuz-2.6.16-sk APPEND console=ttyS0,115200n81 root=/dev/nfs nfsroot=192.168.42.1:/nfshost/soekris nfsaddrs=192.168.42.100:192.168.42.1:192.168.42.1:255.255.255.0:soekris:eth0 panic=5 (I imagine this could be shorter, more implied parameter, yes/no ?) FWIW, the nfsroot docs imply that you cannot put the nfs-root modules in an initrd. This seems an over-simplification of the truth; why wouldnt all the nfs* modules, in an initrd, work properly ? Anyone ever tried it ? (I havent yet, someday)