Kernel panic - not syncing: Attempted to kill init!

Kernel panic - not syncing: Attempted to kill init!

[David F Barrera]

I am trying to create an additional domain and have created a 
configuration file based on the examples.  When I try to boot the 
domain, it eventually hits a Kernel panic, as follows:

Red Hat nash version 4.1.18 starting
Mounted /proc filesystem
Mounting sysfs
Creating /dev
Starting udev
Creating root device
Mounting root filesystem
mount: error 6 mounting ext3
mount: error 2 mounting none
Switching to new root
switchroot: mount failed: 22
umount /initrd/dev failed: 2
Kernel panic - not syncing: Attempted to kill init!
 <0>Rebooting in 1 seconds..
-----------------------------------

I have tried using an initrd file, but it makes no difference. Any ideas 
or suggestions will be greatly appreciated!





David Barrera


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/

Re: Kernel panic - not syncing: Attempted to kill init!

[Derrik Pates]

David F Barrera wrote:
> I am trying to create an additional domain and have created a 
> configuration file based on the examples.  When I try to boot the 
> domain, it eventually hits a Kernel panic, as follows:
> 
> Red Hat nash version 4.1.18 starting
> Mounted /proc filesystem
> Mounting sysfs
> Creating /dev
> Starting udev
> Creating root device
> Mounting root filesystem
> mount: error 6 mounting ext3
> mount: error 2 mounting none
> Switching to new root
> switchroot: mount failed: 22
> umount /initrd/dev failed: 2
> Kernel panic - not syncing: Attempted to kill init!
> <0>Rebooting in 1 seconds..
> -----------------------------------

Which RH flavor is this? I've so far had Fedora Core 2 and 3, as well as 
CentOS, running happily inside a Xen domain. What does the fstab for the 
domain's root FS look like? Also, what does your domain definition file 
look like?

-- 
Derrik Pates
dpates@dsdk12.net


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/

Re: Kernel panic - not syncing: Attempted to kill init!

[David F Barrera]

Derrik,

Thanks for your response.  Of course I should have given more details! 
(my bad).

The distro I am using is  RHEL 4 Beta 2 (Red Hat Enterprise Linux 
Desktop release 3.90 (Nahant)

 >>What does the fstab for the domain's root FS look like?

/dev/hdc1               /                       ext2    defaults        1 1
none                    /dev/pts                devpts  gid=5,mode=620  0 0
none                    /dev/shm                tmpfs   defaults        0 0
none                    /proc                   proc    defaults        0 0
none                    /sys                    sysfs   defaults        0 0
LABEL=SWAP-hdc2         swap                    swap    defaults        0 0
/dev/hda                /media/cdrom            auto    
pamconsole,fscontext=system_u:object_r:removable_t,ro,exec,noauto,managed 
0 0
/dev/fd0                /media/floppy           auto    
pamconsole,fscontext=system_u:object_r:removable_t,exec,noauto,managed 0 0


 >>Also, what does your domain definition file look like?

#----------------------------------------------------------------------------START 
OF DEFINITION FILE
# Kernel image file.
kernel = "/boot/vmlinuz-2.6.9-xenU"

# Optional ramdisk.
ramdisk = "/boot/initrd-fc3.img"

# The domain build function. Default is 'linux'.
builder='linux'

# Initial memory allocation (in megabytes) for the new domain.
memory = 64

# A name for your domain. All domains must have different names.
name = "test1"

# disk = [ 'phy:hda1,hda1,r' ]
disk = [ 'phy:hdc1,hdc1,r' ]

# Set if you want dhcp to allocate the IP address.
dhcp="dhcp"
# Set root device.

root = "/dev/hdc1 ro"

# Sets runlevel 4.
extra = "4"
#---------------------------------------------------------------------------- 
END OF DEFINITION FILE  


Derrik Pates wrote:

> David F Barrera wrote:
>
>> I am trying to create an additional domain and have created a 
>> configuration file based on the examples.  When I try to boot the 
>> domain, it eventually hits a Kernel panic, as follows:
>>
>> Red Hat nash version 4.1.18 starting
>> Mounted /proc filesystem
>> Mounting sysfs
>> Creating /dev
>> Starting udev
>> Creating root device
>> Mounting root filesystem
>> mount: error 6 mounting ext3
>> mount: error 2 mounting none
>> Switching to new root
>> switchroot: mount failed: 22
>> umount /initrd/dev failed: 2
>> Kernel panic - not syncing: Attempted to kill init!
>> <0>Rebooting in 1 seconds..
>> -----------------------------------
>
>
> Which RH flavor is this? I've so far had Fedora Core 2 and 3, as well 
> as CentOS, running happily inside a Xen domain. What does the fstab 
> for the domain's root FS look like? Also, what does your domain 
> definition file look like?
>


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/

Re: Kernel panic - not syncing: Attempted to kill init!

[Derrik Pates]

David F Barrera wrote:
> The distro I am using is  RHEL 4 Beta 2 (Red Hat Enterprise Linux 
> Desktop release 3.90 (Nahant)

> /dev/hdc1               /                       ext2    defaults        1 1

> LABEL=SWAP-hdc2         swap                    swap    defaults        0 0
> /dev/hda                /media/cdrom            auto    
> pamconsole,fscontext=system_u:object_r:removable_t,ro,exec,noauto,managed 
> 0 0

> # disk = [ 'phy:hda1,hda1,r' ]
> disk = [ 'phy:hdc1,hdc1,r' ]

Well, the configuration of the virtual disk looks correct; the swap 
might disagree with it, but that shouldn't appear until later in the 
boot process. Perhaps it's an interaction with devfs? Do you have devfs 
enabled in your xenU (unprivileged domain) kernel? This gave me fits 
when I first began using Xen, mostly because it seems that the xenU 
prebuilt kernel that's included with the binary pack has devfs support 
enabled, and this breaks things. The only other possibility I can think 
of is that you need to change the block-device import to read-write.

-- 
Derrik Pates
dpates@dsdk12.net


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/

Re: Kernel panic - not syncing: Attempted to kill init!

[David F Barrera]

Derrik ,

Thanks for the feedback.

Derrik Pates wrote:

> David F Barrera wrote:
>
>> The distro I am using is  RHEL 4 Beta 2 (Red Hat Enterprise Linux 
>> Desktop release 3.90 (Nahant)
>
>
>> /dev/hdc1               /                       ext2    
>> defaults        1 1
>
>
>> LABEL=SWAP-hdc2         swap                    swap    
>> defaults        0 0
>> /dev/hda                /media/cdrom            auto    
>> pamconsole,fscontext=system_u:object_r:removable_t,ro,exec,noauto,managed 
>> 0 0
>
>
>> # disk = [ 'phy:hda1,hda1,r' ]
>> disk = [ 'phy:hdc1,hdc1,r' ]
>
>
> Well, the configuration of the virtual disk looks correct; the swap 
> might disagree with it, but that shouldn't appear until later in the 
> boot process. Perhaps it's an interaction with devfs? Do you have 
> devfs enabled in your xenU (unprivileged domain) kernel? This gave me 
> fits when I first began using Xen, mostly because it seems that the 
> xenU prebuilt kernel that's included with the binary pack has devfs 
> support enabled, and this breaks things. 

I will try rebuilding the xenU kernel.

> The only other possibility I can think of is that you need to change 
> the block-device import to read-write.

I've already tried changing the block-device import to read-write. No 
difference.


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/

Re: Kernel panic - not syncing: Attempted to kill init!

[David F Barrera]

Derrick,

I rebuilt the xenU kernel, with the devfs support disabled, and it makes 
no difference. It behaves in the same manner as the pre-built kernel 
that's included with the binary pack.  I am at a loss. I've been able to 
boot a kernel under xen on a SuSE Linux 9.0 machine, so I've had a 
little experience with this:-) 

Freeing unused kernel memory: 92k freed
Red Hat nash version 4.1.18 starting
Mounted /proc filesystem
Mounting sysfs
Creating /dev
Starting udev
Creating root device
Mounting root filesystem
mount: error 6 mounting ext3
mount: error 2 mounting none
Switching to new root
switchroot: mount failed: 22
umount /initrd/dev failed: 2
Kernel panic - not syncing: Attempted to kill init!
 <0>Rebooting in 1 seconds..


David Barrera


Derrik Pates wrote:

> David F Barrera wrote:
>
>> The distro I am using is  RHEL 4 Beta 2 (Red Hat Enterprise Linux 
>> Desktop release 3.90 (Nahant)
>
>
>> /dev/hdc1               /                       ext2    
>> defaults        1 1
>
>
>> LABEL=SWAP-hdc2         swap                    swap    
>> defaults        0 0
>> /dev/hda                /media/cdrom            auto    
>> pamconsole,fscontext=system_u:object_r:removable_t,ro,exec,noauto,managed 
>> 0 0
>
>
>> # disk = [ 'phy:hda1,hda1,r' ]
>> disk = [ 'phy:hdc1,hdc1,r' ]
>
>
> Well, the configuration of the virtual disk looks correct; the swap 
> might disagree with it, but that shouldn't appear until later in the 
> boot process. Perhaps it's an interaction with devfs? Do you have 
> devfs enabled in your xenU (unprivileged domain) kernel? This gave me 
> fits when I first began using Xen, mostly because it seems that the 
> xenU prebuilt kernel that's included with the binary pack has devfs 
> support enabled, and this breaks things. The only other possibility I 
> can think of is that you need to change the block-device import to 
> read-write.
>


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/

Re: Kernel panic - not syncing: Attempted to kill init!

[Ian Pratt]

> Derrick,
> 
> I rebuilt the xenU kernel, with the devfs support disabled, and it makes 
> no difference. It behaves in the same manner as the pre-built kernel 
> that's included with the binary pack.  I am at a loss. I've been able to 
> boot a kernel under xen on a SuSE Linux 9.0 machine, so I've had a 
> little experience with this:-) 

David, earlier in the boot messages do you see the hdc1 partition
being found when the partition check happens?

You'll need to export the partition 'rw' eventually, but that's
not your current problem.

You might like to try exporting it as 'sda1' or something to see
if that helps. Not sure why it would, but I've heard folklore
along these lines. 

Adding some more debugging to the linuxrc nash script might shed
some light on the problem. 

Also, what happens if you skip the initrd and try booting
directly off the disk. I doubt there's anything in the initrd you
need.

Ian

 
> Freeing unused kernel memory: 92k freed
> Red Hat nash version 4.1.18 starting
> Mounted /proc filesystem
> Mounting sysfs
> Creating /dev
> Starting udev
> Creating root device
> Mounting root filesystem
> mount: error 6 mounting ext3
> mount: error 2 mounting none
> Switching to new root
> switchroot: mount failed: 22
> umount /initrd/dev failed: 2
> Kernel panic - not syncing: Attempted to kill init!
>  <0>Rebooting in 1 seconds..
> 
> 
> David Barrera
> 
> 
> Derrik Pates wrote:
> 
> > David F Barrera wrote:
> >
> >> The distro I am using is  RHEL 4 Beta 2 (Red Hat Enterprise Linux 
> >> Desktop release 3.90 (Nahant)
> >
> >
> >> /dev/hdc1               /                       ext2    
> >> defaults        1 1
> >
> >
> >> LABEL=SWAP-hdc2         swap                    swap    
> >> defaults        0 0
> >> /dev/hda                /media/cdrom            auto    
> >> pamconsole,fscontext=system_u:object_r:removable_t,ro,exec,noauto,managed 
> >> 0 0
> >
> >
> >> # disk = [ 'phy:hda1,hda1,r' ]
> >> disk = [ 'phy:hdc1,hdc1,r' ]
> >
> >
> > Well, the configuration of the virtual disk looks correct; the swap 
> > might disagree with it, but that shouldn't appear until later in the 
> > boot process. Perhaps it's an interaction with devfs? Do you have 
> > devfs enabled in your xenU (unprivileged domain) kernel? This gave me 
> > fits when I first began using Xen, mostly because it seems that the 
> > xenU prebuilt kernel that's included with the binary pack has devfs 
> > support enabled, and this breaks things. The only other possibility I 
> > can think of is that you need to change the block-device import to 
> > read-write.
> >
> 
> 
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now. 
> http://productguide.itmanagersjournal.com/
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/xen-devel



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/

Re: Kernel panic - not syncing: Attempted to kill init!

[David F Barrera]

Ian,

Thanks for the reply and the suggestions. Some details about my setup:
/dev/hdc3  is where xen0 is running
/dev/hdc1 --  another partition that actually has a copy of RHEL 4  Beta 
2 installed (working OS)
/etc/fstab:
# This file is edited by fstab-sync - see 'man fstab-sync' for details
/dev/hdc3               /                       ext2    defaults        1 1
none                    /dev/pts                devpts  gid=5,mode=620  0 0
none                    /dev/shm                tmpfs   defaults        0 0
none                    /proc                   proc    defaults        0 0
none                    /sys                    sysfs   defaults        0 0
/dev/hdc2               swap                    swap    defaults        0 0
/dev/hda                /media/cdrom            auto    
pamconsole,ro,exec,noauto,managed 0 0
~

The config file that I am using:

# Kernel image file.
kernel = "/boot/vmlinuz-2.6.9-xenU"
# Optional ramdisk.
ramdisk = "/boot/initrd-2.6.9-xenU.img"
# The domain build function. Default is 'linux'.
builder='linux'
# Initial memory allocation (in megabytes) for the new domain.
memory = 64
# A name for your domain. All domains must have different names.
name = "test1"
# disk = [ 'phy:hda1,hda1,r' ]
disk = [ 'phy:hdc1,hdc1,w' ]
# Set if you want dhcp to allocate the IP address.
dhcp="dhcp"
# Set root device.
root = "/dev/hdc1 ro/"
# Sets runlevel 4.
extra = "4"
#============================================================================
~


Ian Pratt wrote:

>>Derrick,
>>
>>I rebuilt the xenU kernel, with the devfs support disabled, and it makes 
>>no difference. It behaves in the same manner as the pre-built kernel 
>>that's included with the binary pack.  I am at a loss. I've been able to 
>>boot a kernel under xen on a SuSE Linux 9.0 machine, so I've had a 
>>little experience with this:-) 
>>    
>>
>
>David, earlier in the boot messages do you see the hdc1 partition
>being found when the partition check happens?
>  
>
This is the entire log:

Linux version 2.6.9-xenU (root@dyn95394184.austin.ibm.com) (gcc version 
3.4.2 20041017 (Red Hat 3.4.2-6.fc3)) #1 Fri Dec 17 15:50:10 CST 2004
BIOS-provided physical RAM map:
 Xen: 0000000000000000 - 0000000004000000 (usable)
64MB LOWMEM available.
DMI not present.
Built 1 zonelists
Kernel command line:  ip=:1.2.3.4::::eth0:dhcp root=/dev/hdc1 ro/ 4
Initializing CPU#0
PID hash table entries: 512 (order: 9, 8192 bytes)
Xen reported: 866.697 MHz processor.
Using tsc for high-res timesource
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 61900k/65536k available (1569k kernel code, 3596k reserved, 429k 
data, 92k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
CPU: L1 I cache: 16K, L1 D cache: 16K
CPU: L2 cache: 256K
CPU: Intel Pentium III (Coppermine) stepping 06
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... disabled
checking if image is initramfs... it is
Freeing initrd memory: 600k freed
NET: Registered protocol family 16
Initializing Cryptographic API
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
Xen virtual console successfully installed as tty
Event-channel device installed.
Starting Xen Balloon driver
xen_blk: Initialising virtual block device driver
Using anticipatory io scheduler
xen_net: Initialising virtual ethernet driver.
NET: Registered protocol family 2
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 4096 bind 8192)
NET: Registered protocol family 1
NET: Registered protocol family 17
IP-Config: Incomplete network configuration information.
Freeing unused kernel memory: 92k freed
Red Hat nash version 4.1.18 starting
Mounted /proc filesystem
Mounting sysfs
Creating /dev
Starting udev
Creating root device
Mounting root filesystem
mount: error 6 mounting ext2
mount: error 2 mounting none
Switching to new root
switchroot: mount failed: 22
umount /initrd/dev failed: 2
Kernel panic - not syncing: Attempted to kill init!
 <0>Rebooting in 1 seconds..


>You'll need to export the partition 'rw' eventually, but that's
>not your current problem.
>  
>
Right. Already tried it.

>You might like to try exporting it as 'sda1' or something to see
>if that helps. Not sure why it would, but I've heard folklore
>along these lines. 
>  
>
I had tried that (and hda1) before, but sda1 I get an error, too:
[root@dyn95394184 xen]# xm create -c test1 vmid=1
Using config file "test1".
Error: Error creating domain: vbd: Device not found: sda1

>Adding some more debugging to the linuxrc nash script might shed
>some light on the problem. 
>  
>
I need to find out how to do this first...

>Also, what happens if you skip the initrd and try booting
>directly off the disk. I doubt there's anything in the initrd you
>need.
>  
>
I had tried it, also.  I get a VFS error if I don't use an initrd

VFS: Cannot open root device "hdc1" or unknown-block(2,0)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Unable to mount root fs on 
unknown-block(2,0)
 <0>Rebooting in 1 seconds..


>Ian
>
> 
>  
>
>>Freeing unused kernel memory: 92k freed
>>Red Hat nash version 4.1.18 starting
>>Mounted /proc filesystem
>>Mounting sysfs
>>Creating /dev
>>Starting udev
>>Creating root device
>>Mounting root filesystem
>>mount: error 6 mounting ext3
>>mount: error 2 mounting none
>>Switching to new root
>>switchroot: mount failed: 22
>>umount /initrd/dev failed: 2
>>Kernel panic - not syncing: Attempted to kill init!
>> <0>Rebooting in 1 seconds..
>>
>>
>>David Barrera
>>
>>
>>Derrik Pates wrote:
>>
>>    
>>
>>>David F Barrera wrote:
>>>
>>>      
>>>
>>>>The distro I am using is  RHEL 4 Beta 2 (Red Hat Enterprise Linux 
>>>>Desktop release 3.90 (Nahant)
>>>>        
>>>>
>>>      
>>>
>>>>/dev/hdc1               /                       ext2    
>>>>defaults        1 1
>>>>        
>>>>
>>>      
>>>
>>>>LABEL=SWAP-hdc2         swap                    swap    
>>>>defaults        0 0
>>>>/dev/hda                /media/cdrom            auto    
>>>>pamconsole,fscontext=system_u:object_r:removable_t,ro,exec,noauto,managed 
>>>>0 0
>>>>        
>>>>
>>>      
>>>
>>>># disk = [ 'phy:hda1,hda1,r' ]
>>>>disk = [ 'phy:hdc1,hdc1,r' ]
>>>>        
>>>>
>>>Well, the configuration of the virtual disk looks correct; the swap 
>>>might disagree with it, but that shouldn't appear until later in the 
>>>boot process. Perhaps it's an interaction with devfs? Do you have 
>>>devfs enabled in your xenU (unprivileged domain) kernel? This gave me 
>>>fits when I first began using Xen, mostly because it seems that the 
>>>xenU prebuilt kernel that's included with the binary pack has devfs 
>>>support enabled, and this breaks things. The only other possibility I 
>>>can think of is that you need to change the block-device import to 
>>>read-write.
>>>
>>>      
>>>
>>-------------------------------------------------------
>>SF email is sponsored by - The IT Product Guide
>>Read honest & candid reviews on hundreds of IT Products from real users.
>>Discover which products truly live up to the hype. Start reading now. 
>>http://productguide.itmanagersjournal.com/
>>_______________________________________________
>>Xen-devel mailing list
>>Xen-devel@lists.sourceforge.net
>>https://lists.sourceforge.net/lists/listinfo/xen-devel
>>    
>>
>
>
>
>-------------------------------------------------------
>SF email is sponsored by - The IT Product Guide
>Read honest & candid reviews on hundreds of IT Products from real users.
>Discover which products truly live up to the hype. Start reading now. 
>http://productguide.itmanagersjournal.com/
>_______________________________________________
>Xen-devel mailing list
>Xen-devel@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/xen-devel
>
>  
>


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/

Re: Kernel panic - not syncing: Attempted to kill init!

[David F Barrera]

Ian,

One thing about RHEL 4 is that the devices in /dev seem to be created 
dynamically, at boot time.  When I mount the 'hdc1' partition and go to 
the /dev directory, there is nothing in it, as on a SuSE 9.0 or earlier 
Red Hat installs.  That is why I need an initrd, I suppose, to make or 
create those devices.

David

Ian Pratt wrote:

>>Derrick,
>>
>>I rebuilt the xenU kernel, with the devfs support disabled, and it makes 
>>no difference. It behaves in the same manner as the pre-built kernel 
>>that's included with the binary pack.  I am at a loss. I've been able to 
>>boot a kernel under xen on a SuSE Linux 9.0 machine, so I've had a 
>>little experience with this:-) 
>>    
>>
>
>David, earlier in the boot messages do you see the hdc1 partition
>being found when the partition check happens?
>
>You'll need to export the partition 'rw' eventually, but that's
>not your current problem.
>
>You might like to try exporting it as 'sda1' or something to see
>if that helps. Not sure why it would, but I've heard folklore
>along these lines. 
>
>Adding some more debugging to the linuxrc nash script might shed
>some light on the problem. 
>
>Also, what happens if you skip the initrd and try booting
>directly off the disk. I doubt there's anything in the initrd you
>need.
>
>Ian
>
> 
>  
>
>>Freeing unused kernel memory: 92k freed
>>Red Hat nash version 4.1.18 starting
>>Mounted /proc filesystem
>>Mounting sysfs
>>Creating /dev
>>Starting udev
>>Creating root device
>>Mounting root filesystem
>>mount: error 6 mounting ext3
>>mount: error 2 mounting none
>>Switching to new root
>>switchroot: mount failed: 22
>>umount /initrd/dev failed: 2
>>Kernel panic - not syncing: Attempted to kill init!
>> <0>Rebooting in 1 seconds..
>>
>>
>>David Barrera
>>
>>
>>Derrik Pates wrote:
>>
>>    
>>
>>>David F Barrera wrote:
>>>
>>>      
>>>
>>>>The distro I am using is  RHEL 4 Beta 2 (Red Hat Enterprise Linux 
>>>>Desktop release 3.90 (Nahant)
>>>>        
>>>>
>>>      
>>>
>>>>/dev/hdc1               /                       ext2    
>>>>defaults        1 1
>>>>        
>>>>
>>>      
>>>
>>>>LABEL=SWAP-hdc2         swap                    swap    
>>>>defaults        0 0
>>>>/dev/hda                /media/cdrom            auto    
>>>>pamconsole,fscontext=system_u:object_r:removable_t,ro,exec,noauto,managed 
>>>>0 0
>>>>        
>>>>
>>>      
>>>
>>>># disk = [ 'phy:hda1,hda1,r' ]
>>>>disk = [ 'phy:hdc1,hdc1,r' ]
>>>>        
>>>>
>>>Well, the configuration of the virtual disk looks correct; the swap 
>>>might disagree with it, but that shouldn't appear until later in the 
>>>boot process. Perhaps it's an interaction with devfs? Do you have 
>>>devfs enabled in your xenU (unprivileged domain) kernel? This gave me 
>>>fits when I first began using Xen, mostly because it seems that the 
>>>xenU prebuilt kernel that's included with the binary pack has devfs 
>>>support enabled, and this breaks things. The only other possibility I 
>>>can think of is that you need to change the block-device import to 
>>>read-write.
>>>
>>>      
>>>
>>-------------------------------------------------------
>>SF email is sponsored by - The IT Product Guide
>>Read honest & candid reviews on hundreds of IT Products from real users.
>>Discover which products truly live up to the hype. Start reading now. 
>>http://productguide.itmanagersjournal.com/
>>_______________________________________________
>>Xen-devel mailing list
>>Xen-devel@lists.sourceforge.net
>>https://lists.sourceforge.net/lists/listinfo/xen-devel
>>    
>>
>
>
>
>-------------------------------------------------------
>SF email is sponsored by - The IT Product Guide
>Read honest & candid reviews on hundreds of IT Products from real users.
>Discover which products truly live up to the hype. Start reading now. 
>http://productguide.itmanagersjournal.com/
>_______________________________________________
>Xen-devel mailing list
>Xen-devel@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/xen-devel
>
>  
>


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/

Re: Kernel panic - not syncing: Attempted to kill init!

[Ian Pratt]

> # Kernel image file.
> kernel = "/boot/vmlinuz-2.6.9-xenU"
> # Optional ramdisk.
> ramdisk = "/boot/initrd-2.6.9-xenU.img"
> # The domain build function. Default is 'linux'.
> builder='linux'
> # Initial memory allocation (in megabytes) for the new domain.
> memory = 64
> # A name for your domain. All domains must have different names.
> name = "test1"
> # disk = [ 'phy:hda1,hda1,r' ]
> disk = [ 'phy:hdc1,hdc1,w' ]
> # Set if you want dhcp to allocate the IP address.
> dhcp="dhcp"
> # Set root device.
> root = "/dev/hdc1 ro/"


The '/' on the end of 'ro' looks odd to me.

> xen_blk: Initialising virtual block device driver
> Using anticipatory io scheduler
> xen_net: Initialising virtual ethernet driver.
> NET: Registered protocol family 2
> IP: routing cache hash table of 512 buckets, 4Kbytes
> TCP: Hash tables configured (established 4096 bind 8192)
> NET: Registered protocol family 1
> NET: Registered protocol family 17
> IP-Config: Incomplete network configuration information.
> Freeing unused kernel memory: 92k freed
> Red Hat nash version 4.1.18 starting

I can't see any partitions being found at any point, so you're
doomed from here on in.

> I had tried that (and hda1) before, but sda1 I get an error, too:
> [root@dyn95394184 xen]# xm create -c test1 vmid=1
> Using config file "test1".
> Error: Error creating domain: vbd: Device not found: sda1


try  disk = [ 'phy:hdc1,0801,w' ]

0801 == sda1




Ian


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/

Re: Kernel panic - not syncing: Attempted to kill init!

[David F Barrera]

Ian Pratt wrote:

>># Kernel image file.
>>kernel = "/boot/vmlinuz-2.6.9-xenU"
>># Optional ramdisk.
>>ramdisk = "/boot/initrd-2.6.9-xenU.img"
>># The domain build function. Default is 'linux'.
>>builder='linux'
>># Initial memory allocation (in megabytes) for the new domain.
>>memory = 64
>># A name for your domain. All domains must have different names.
>>name = "test1"
>># disk = [ 'phy:hda1,hda1,r' ]
>>disk = [ 'phy:hdc1,hdc1,w' ]
>># Set if you want dhcp to allocate the IP address.
>>dhcp="dhcp"
>># Set root device.
>>root = "/dev/hdc1 ro/"
>>    
>>
>
>
>The '/' on the end of 'ro' looks odd to me.
>  
>
Thx. Removing it did not make any difference.

>  
>
>>xen_blk: Initialising virtual block device driver
>>Using anticipatory io scheduler
>>xen_net: Initialising virtual ethernet driver.
>>NET: Registered protocol family 2
>>IP: routing cache hash table of 512 buckets, 4Kbytes
>>TCP: Hash tables configured (established 4096 bind 8192)
>>NET: Registered protocol family 1
>>NET: Registered protocol family 17
>>IP-Config: Incomplete network configuration information.
>>Freeing unused kernel memory: 92k freed
>>Red Hat nash version 4.1.18 starting
>>    
>>
>
>I can't see any partitions being found at any point, so you're
>doomed from here on in.
>  
>
Agree.

>  
>
>>I had tried that (and hda1) before, but sda1 I get an error, too:
>>[root@dyn95394184 xen]# xm create -c test1 vmid=1
>>Using config file "test1".
>>Error: Error creating domain: vbd: Device not found: sda1
>>    
>>
>
>
>try  disk = [ 'phy:hdc1,0801,w' ]
>
>0801 == sda1
>  
>
No difference.  Same Kernel panic

>
>
>
>Ian
>
>  
>


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/

Re: Kernel panic - not syncing: Attempted to kill init!

[Ian Pratt]

> >>I had tried that (and hda1) before, but sda1 I get an error, too:
> >>[root@dyn95394184 xen]# xm create -c test1 vmid=1
> >>Using config file "test1".
> >>Error: Error creating domain: vbd: Device not found: sda1
> >
> >try  disk = [ 'phy:hdc1,0801,w' ]
> >
> >0801 == sda1
>
> No difference.  Same Kernel panic

Something odd is going on here -- I believe other people have had
RHEL3 working.

Can you mount hdc1 in dom 0 OK? Is there an sbin/init ? Is there
a dev directory?

It might be worth enabling the debugging printks in
drivers/xen/blkfront/block.h and drivers/xen/blockback/common.h
and rebuilding xen0 / xenU.


Ian





-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/

Re: Kernel panic - not syncing: Attempted to kill init!

[David F Barrera]

Ian Pratt wrote:

>>>>I had tried that (and hda1) before, but sda1 I get an error, too:
>>>>[root@dyn95394184 xen]# xm create -c test1 vmid=1
>>>>Using config file "test1".
>>>>Error: Error creating domain: vbd: Device not found: sda1
>>>>        
>>>>
>>>try  disk = [ 'phy:hdc1,0801,w' ]
>>>
>>>0801 == sda1
>>>      
>>>
>>No difference.  Same Kernel panic
>>    
>>
>
>Something odd is going on here -- I believe other people have had
>RHEL3 working.
>  
>
I believe it.  But RHEL 4 has some differences from RHEL 3, among them 
the fact that in RHEL 4 the devices in /dev are created dynamically.  
Thus, if I mount hdc1 and look at /dev, it is empty.  However, /dev in 
hdc3 (xen0) has 671 entries. I have a SuSE 9.0 system where the drive 
that I export (equivalent to hdc1, in this case) has many devicen on 
/dev, meaning they are static;  RHEL 3 is similar.

>Can you mount hdc1 in dom 0 OK? 
>
Yes:

[root@dyn95394184 ~]# mount /dev/hdc1 /data1
[root@dyn95394184 ~]# df
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/hdc3              6372520   2732376   3316436  46% /
none                    251384         0    251384   0% /dev/shm
/dev/hdc1              7055144   2422572   4274180  37% /data1
[root@dyn95394184 ~]#

>Is there an sbin/init 
>
[root@dyn95394184 ~]# ls /data1/sbin/init
/data1/sbin/init
[root@dyn95394184 ~]#

>? Is there
>a dev directory? 
>  
>
Yes, but it is empty:
[root@dyn95394184 dev]# pwd
/data1/dev
[root@dyn95394184 dev]# ls
[root@dyn95394184 dev]#

>It might be worth enabling the debugging printks in
>drivers/xen/blkfront/block.h and drivers/xen/blockback/common.h
>and rebuilding xen0 / xenU.
>
>  
>
I created an image file to experiment, and it seems to go a little 
further.  The problem has got to be related to the /dev issue.

disk = [ 'file:/boot/initrd.x86.image,0801,w' ]
# Set if you want dhcp to allocate the IP address.
# dhcp="dhcp"
# Set root device.
root = "/dev/sda1 ro"


Red Hat nash version 4.1.18 starting
Mounted /proc filesystem
Mounting sysfs
Creating /dev
Starting udev
Creating root device
Mounting root filesystem
Switching to new root
init started:  BusyBox v1.00-pre10 (2004.06.10-04:09+0000) multi-call binary
Linux localhost.localdomain 2.6.9-xenU #1 Fri Dec 17 15:50:10 CST 2004 
i686 unknown
 

>Ian
>
>
>
>
>  
>


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/

Re: Kernel panic - not syncing: Attempted to kill init!

[David F Barrera]

Ian,

As I indicated earlier, I created an image file, and I am able to boot 
xenU now:

Red Hat Enterprise Linux Desktop release 3.90 (Nahant)
Kernel 2.6.9-xenU on an i686

(none) login:

I still can't log in, but I will continue to add files to the image to 
make it work.  In the image, I copied the contents of  (hdc3) /dev to 
the  image/dev.  I still don't understand why I can get xenU to boot 
using the system partition (hdc1). I'll keep digging.

David F Barrera

>
>
> Ian Pratt wrote:
>
>>>>> I had tried that (and hda1) before, but sda1 I get an error, too:
>>>>> [root@dyn95394184 xen]# xm create -c test1 vmid=1
>>>>> Using config file "test1".
>>>>> Error: Error creating domain: vbd: Device not found: sda1
>>>>>       
>>>>
>>>> try  disk = [ 'phy:hdc1,0801,w' ]
>>>>
>>>> 0801 == sda1
>>>>     
>>>
>>> No difference.  Same Kernel panic
>>>   
>>
>>
>> Something odd is going on here -- I believe other people have had
>> RHEL3 working.
>>  
>>
> I believe it.  But RHEL 4 has some differences from RHEL 3, among them 
> the fact that in RHEL 4 the devices in /dev are created dynamically.  
> Thus, if I mount hdc1 and look at /dev, it is empty.  However, /dev in 
> hdc3 (xen0) has 671 entries. I have a SuSE 9.0 system where the drive 
> that I export (equivalent to hdc1, in this case) has many devicen on 
> /dev, meaning they are static;  RHEL 3 is similar.
>
>> Can you mount hdc1 in dom 0 OK?
>
> Yes:
>
> [root@dyn95394184 ~]# mount /dev/hdc1 /data1
> [root@dyn95394184 ~]# df
> Filesystem           1K-blocks      Used Available Use% Mounted on
> /dev/hdc3              6372520   2732376   3316436  46% /
> none                    251384         0    251384   0% /dev/shm
> /dev/hdc1              7055144   2422572   4274180  37% /data1
> [root@dyn95394184 ~]#
>
>> Is there an sbin/init
>
> [root@dyn95394184 ~]# ls /data1/sbin/init
> /data1/sbin/init
> [root@dyn95394184 ~]#
>
>> ? Is there
>> a dev directory?  
>>
> Yes, but it is empty:
> [root@dyn95394184 dev]# pwd
> /data1/dev
> [root@dyn95394184 dev]# ls
> [root@dyn95394184 dev]#
>
>> It might be worth enabling the debugging printks in
>> drivers/xen/blkfront/block.h and drivers/xen/blockback/common.h
>> and rebuilding xen0 / xenU.
>>
>>  
>>
> I created an image file to experiment, and it seems to go a little 
> further.  The problem has got to be related to the /dev issue.
>
> disk = [ 'file:/boot/initrd.x86.image,0801,w' ]
> # Set if you want dhcp to allocate the IP address.
> # dhcp="dhcp"
> # Set root device.
> root = "/dev/sda1 ro"
>
>
> Red Hat nash version 4.1.18 starting
> Mounted /proc filesystem
> Mounting sysfs
> Creating /dev
> Starting udev
> Creating root device
> Mounting root filesystem
> Switching to new root
> init started:  BusyBox v1.00-pre10 (2004.06.10-04:09+0000) multi-call 
> binary
> Linux localhost.localdomain 2.6.9-xenU #1 Fri Dec 17 15:50:10 CST 2004 
> i686 unknown
>
>
>> Ian
>>
>>
>>
>>
>>  
>>
>


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/

Re: Kernel panic - not syncing: Attempted to kill init!

[David F Barrera]

Ian,

OK. I copied all the contents from (hdc3) /dev to (hdc1) /dev, and that 
let's me boot xenU on hdc1.  The problem, however, is that this is not 
they way RHEL 4 works--I need to figure out how the xen0 is able to boot 
off essentially the same setup.

[root@dyn95394184 xen]# xm list
Name              Id  Mem(MB)  CPU  State  Time(s)  Console
Domain-0           0      495        0      r----    126.0
test1                   1        64        0      -b---       2.0    9601
[root@dyn95394184 xen]#




-------- Original Message --------
Subject: 	Re: [Xen-devel] Kernel panic - not syncing: Attempted to kill 
init!
Date: 	Tue, 21 Dec 2004 12:53:15 -0600
From: 	David F Barrera <dfbp@us.ibm.com>
To: 	xen-devel@lists.sourceforge.net
References: 	<E1CgWrK-0003vv-00@mta1.cl.cam.ac.uk> 
<41C844BA.7020801@us.ibm.com>



Ian,

As I indicated earlier, I created an image file, and I am able to boot 
xenU now:

Red Hat Enterprise Linux Desktop release 3.90 (Nahant)
Kernel 2.6.9-xenU on an i686

(none) login:

I still can't log in, but I will continue to add files to the image to 
make it work.  In the image, I copied the contents of  (hdc3) /dev to 
the  image/dev.  I still don't understand why I can get xenU to boot 
using the system partition (hdc1). I'll keep digging.

David F Barrera

>
>
> Ian Pratt wrote:
>
>>>>> I had tried that (and hda1) before, but sda1 I get an error, too:
>>>>> [root@dyn95394184 xen]# xm create -c test1 vmid=1
>>>>> Using config file "test1".
>>>>> Error: Error creating domain: vbd: Device not found: sda1
>>>>>       
>>>>
>>>> try  disk = [ 'phy:hdc1,0801,w' ]
>>>>
>>>> 0801 == sda1
>>>>     
>>>
>>> No difference.  Same Kernel panic
>>>   
>>
>>
>> Something odd is going on here -- I believe other people have had
>> RHEL3 working.
>>  
>>
> I believe it.  But RHEL 4 has some differences from RHEL 3, among them 
> the fact that in RHEL 4 the devices in /dev are created dynamically.  
> Thus, if I mount hdc1 and look at /dev, it is empty.  However, /dev in 
> hdc3 (xen0) has 671 entries. I have a SuSE 9.0 system where the drive 
> that I export (equivalent to hdc1, in this case) has many devicen on 
> /dev, meaning they are static;  RHEL 3 is similar.
>
>> Can you mount hdc1 in dom 0 OK?
>
> Yes:
>
> [root@dyn95394184 ~]# mount /dev/hdc1 /data1
> [root@dyn95394184 ~]# df
> Filesystem           1K-blocks      Used Available Use% Mounted on
> /dev/hdc3              6372520   2732376   3316436  46% /
> none                    251384         0    251384   0% /dev/shm
> /dev/hdc1              7055144   2422572   4274180  37% /data1
> [root@dyn95394184 ~]#
>
>> Is there an sbin/init
>
> [root@dyn95394184 ~]# ls /data1/sbin/init
> /data1/sbin/init
> [root@dyn95394184 ~]#
>
>> ? Is there
>> a dev directory?  
>>
> Yes, but it is empty:
> [root@dyn95394184 dev]# pwd
> /data1/dev
> [root@dyn95394184 dev]# ls
> [root@dyn95394184 dev]#
>
>> It might be worth enabling the debugging printks in
>> drivers/xen/blkfront/block.h and drivers/xen/blockback/common.h
>> and rebuilding xen0 / xenU.
>>
>>  
>>
> I created an image file to experiment, and it seems to go a little 
> further.  The problem has got to be related to the /dev issue.
>
> disk = [ 'file:/boot/initrd.x86.image,0801,w' ]
> # Set if you want dhcp to allocate the IP address.
> # dhcp="dhcp"
> # Set root device.
> root = "/dev/sda1 ro"
>
>
> Red Hat nash version 4.1.18 starting
> Mounted /proc filesystem
> Mounting sysfs
> Creating /dev
> Starting udev
> Creating root device
> Mounting root filesystem
> Switching to new root
> init started:  BusyBox v1.00-pre10 (2004.06.10-04:09+0000) multi-call 
> binary
> Linux localhost.localdomain 2.6.9-xenU #1 Fri Dec 17 15:50:10 CST 2004 
> i686 unknown
>
>
>> Ian
>>
>>
>>
>>
>>  
>>
>


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xen-devel




-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/

RE: Kernel panic - not syncing: Attempted to kill init!

[Ian Pratt]

> I believe it.  But RHEL 4 has some differences from RHEL 3, 
> among them the fact that in RHEL 4 the devices in /dev are 
> created dynamically.  
> Thus, if I mount hdc1 and look at /dev, it is empty.  However, /dev in
> hdc3 (xen0) has 671 entries. I have a SuSE 9.0 system where 
> the drive that I export (equivalent to hdc1, in this case) 
> has many devicen on /dev, meaning they are static;  RHEL 3 is similar.

Just to prove this theory, boot native Linux (or dom0), and 'cp -a' the
/dev directory over to the other domain's file system. If you haven't
got a /dev/console bad things can happen.

Ian 


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/

RE: Kernel panic - not syncing: Attempted to kill init!

[Ian Pratt]

> OK. I copied all the contents from (hdc3) /dev to (hdc1) 
> /dev, and that let's me boot xenU on hdc1.  The problem, 
> however, is that this is not they way RHEL 4 works--I need to 
> figure out how the xen0 is able to boot off essentially the 
> same setup.

Have you tried using the xen0 kernel in the other domain? It's possible
there's some difference in the .config that is causing this.

Ian


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/

Re: Kernel panic - not syncing: Attempted to kill init!

[David F Barrera]

Ian,

It was a setup problem after all. Mea culpa.

One thing I had to do was to change the /etc/fstab on the xenU partition 
(hdc1 in my machine):
/dev/sda1               /                       ext2    defaults        
1 1   <----------- I had the original /dev/hdc1 here

to match the xen config file:
disk = [ 'phy:hdc1,0801,w' ]   < ---- This suggestion you gave to use 
'0801' and 'sda1' works for some reason. 
                                                        Using  'hdc1' 
here and on the root = /dev/ line does NOT work, as you were aware.
root = "/dev/sda1 ro"

I need to have an initrd in order to have a console.  It will not work 
without it:
# Kernel image file.
kernel = "/boot/vmlinuz-2.6.9-xenU"
# Optional ramdisk.
ramdisk = "/boot/initrd-2.6.9-xenU.img"


Thanks for all your suggestions!

David F Barrera

Ian Pratt wrote:

>>OK. I copied all the contents from (hdc3) /dev to (hdc1) 
>>/dev, and that let's me boot xenU on hdc1.  The problem, 
>>however, is that this is not they way RHEL 4 works--I need to 
>>figure out how the xen0 is able to boot off essentially the 
>>same setup.
>>    
>>
>
>Have you tried using the xen0 kernel in the other domain? It's possible
>there's some difference in the .config that is causing this.
>  
>
I tried this just for kicks, and, of course, it worked.

>Ian
>
>
>-------------------------------------------------------
>SF email is sponsored by - The IT Product Guide
>Read honest & candid reviews on hundreds of IT Products from real users.
>Discover which products truly live up to the hype. Start reading now. 
>http://productguide.itmanagersjournal.com/
>_______________________________________________
>Xen-devel mailing list
>Xen-devel@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/xen-devel
>
>  
>


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/

Kernel Panic - not syncing: Attempted to kill init!

[Sreen Tallam]

Hi All,

Has anyone seen this error?
I am running a 2.6.18 kernel on a PPC 405GP using a AMCC Walnut board.

I added some printf's within the kernel to debug more information, and
it pointed to

init/main.c
under init() routine
in run_init_process(execute_command);
where execute_command = /sbin/tallam_init


=> tftp 0x800000 /tftpboot/tallam/kernel_5_2
ENET Speed is 100 Mbps - FULL duplex connection
Filename '/tftpboot/tallam/kernel_5_2'.
Load address: 0x800000
Loading: #################################################################
         #################################################################
         #################################################################
         #######################################
done
Bytes transferred = 1196495 (1241cf hex)
=> bootm 0x800000
## Booting image at 00800000 ...
   Image Name:   Linux-2.6.18_pro500
   Created:      2008-04-09  23:13:11 UTC
   Image Type:   PowerPC Linux Kernel Image (gzip compressed)
   Data Size:    1196431 Bytes =  1.1 MB
   Load Address: 00400000
   Entry Point:  0040053c
   Verifying Checksum ... OK
   Uncompressing Kernel Image ... OK
## Current stack ends at 0x03FAD548 => set upper limit to 0x00800000
## cmdline at 0x007FFC00 ... 0x007FFD14
gd address  = 0x03FADF18
bd address  = 0x03FADF48
memstart    = 0x00000000
memsize     = 0x04000000
flashstart  = 0xFF000000
flashsize   = 0x01000000
flashoffset = 0x00000000
sramstart   = 0x00000000
sramsize    = 0x00000000
bootflags   = 0x0000A000
procfreq    =    100 MHz
plb_busfreq =    100 MHz
pci_busfreq =     50 MHz
ethaddr     = 00:xx:xx:04:4F:70
IP addr     = 172.xx.xxx.177
baudrate    =   9600 bps
No initrd
## Transferring control to Linux (at address 0040053c) ...
Memory <- <0x0 0x4000000> (64MB)
CPU clock-frequency <- 0x5f5e0ff (100MHz)
CPU timebase-frequency <- 0x5f5e0ff (100MHz)
/plb: clock-frequency <- 5f5e0ff (100MHz)
/plb/opb: clock-frequency <- 2faf07f (50MHz)
/plb/ebc: clock-frequency <- 2faf07f (50MHz)
/plb/opb/serial@ef600300: clock-frequency <- a98ac7 (11MHz)
/plb/opb/serial@ef600400: clock-frequency <- a98ac7 (11MHz)
ENET0: local-mac-address <- 00:xx:xx:04:4f:70

zImage starting: loaded at 0x00400000 (sp: 0x03fad3e8)
Allocating 0x299958 bytes for kernel ...
gunzipping (0x00000000 <- 0x0040d000:0x006a871c)...done 0x2740c0 bytes

Linux/PowerPC load:
mtdparts=phys_mapped_flash:64k@0k(envb),960k@64k(spare-log
s),6m@1m(jffs2b),768k@7m(kernelb),256k@7936k(u-bootb),64k@8m(envp),960k@8256k(
    logs),6m@9m(jffs2p),768k@15m(kernelp),256k@16128k(u-bootp)
console=ttyS1,9600      rootfstype=jffs2 root=/dev/mtdblock7 ro
init=/sbin/tallam_init
Finalizing device tree... flat tree at 0x6b5420
id mach(): done
MMU:enter
MMU:hw init
MMU:mapin
MMU:setio
MMU:exit
Linux version 2.6.18_pro500 (gcc version 4.2.     0 ) #1 PREEMPT Wed
Apr 9 16:02:34      PDT 2008
Found legacy serial port 0 for /plb/opb/serial@ef600300
  mem=ef600300, taddr=ef600300, irq=0, clk=11111111, speed=9600
Found legacy serial port 1 for /plb/opb/serial@e600400
  mem=ef600400, taddr=ef600400, irq=0, clk=11111111, spHz
time_init: processor frequency   = 99.999999 MHz
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Memory: 62228k/65536k available (2372k kernel code, 3248k reserved,
92k data,      146k bss, 156k init)
Calibrating delay loop... 198.65 BogoMIPS (lpj=397312)
Mount-cache hash table entries: 512
NET: Registered protocol family 16
/plb/opb/gpio@ef600700: device found
PCI: Probing PCI hardware
NET: Registered protocol family 2
IP route cache hash table entries: 512 (order: -1, 2048 bytes)
TCP established hash table entries: 2048 (order: 1, 8192 bytes)
TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
TCP: Hash tables configured (established 2048 bind 1024)
TCP reno registered
JFFS2 version 2.2. (NAND) (C) 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler anticipatory registered (default)
io scheduler deadline registered
io scheduler cfq registered
/plb/opb/gpio@ef600700 character device (0) ready
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
serial8250.0: ttyS0 at MMIO map 0xef600300 mem 0xc5000300 (irq = 16)
is a 1655     0A
serial8250.0: ttyS1 at MMIO map 0xef600400 mem 0xc5002400 (irq = 17)
is a 1655     0A
console handover: boot [udbg0] -> real [ttyS1]
ef600300.serial: ttyS0 at MMIO map 0xef600300 mem 0xc5062300 (irq =
16) is a 1     6550A
ef600400.serial: ttyS1 at MMIO map 0xef600400 mem 0xc5064400 (irq =
17) is a 1     6550A
RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
loop: loaded (max 8 devices)
PPC 4xx OCP EMAC driver, version 3.54
MAL v1 /plb/mcmal, 1 TX channels, 1 RX channels
eth0: EMAC-0 /plb/opb/ethernet@ef600800, MAC 00:a0:xx:xx:4f:70
eth0: found Generic MII PHY (0x01)
i2c /dev entries driver
IBM IIC driver v2.1
ff000000.flash: Found 1 x16 devices at 0x0 in 16-bit bank
 Amd/Fujitsu Extended Query Table at 0x0040
ff000000.flash: CFI does not contain boot bank location. Assuming top.
number of CFI chips: 1
cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.
RedBoot partition parsing not available
Creating 10 MTD partitions on "ff000000.flash":
0x00000000-0x00010000 : "envb"
0x00010000-0x00100000 : "spare-logs"
0x00100000-0x00700000 : "jffs2b"
0x00700000-0x007c0000 : "kernelb"
0x007c0000-0x00800000 : "u-bootb"
0x00800000-0x00810000 : "envp"
0x00810000-0x00900000 : "logs"
0x00900000-0x00f00000 : "jffs2p"
0x00f00000-0x00fc0000 : "kernelp"
0x00fc0000-0x01000000 : "u-bootp"
ip_conntrack version 2.4 (512 buckets, 4096 max) - 172 bytes per conntrack
TCP bic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
Time: timebase clocksource has been installed.
eth0: link is up, 100 FDX
IP-Config: Incomplete network configuration information.
VFS: Mounted root (jffs2 filesystem) readonly.
Freeing unused kernel memory: 156k init
Warning: unable to open an initial console.
init/main.c -- 819
init/main.c -- 821
init/main.c -- 844
init/main.c -- 704 -- /sbin/tallam_init<0>Kernel panic - not syncing:
Attempted to kill init!
Call Trace:
[C3FE7E60] [C0006D98]  (unreliable)
[C3FE7EA0] [C001F150]
[C3FE7EF0] [C0023630]
[C3FE7F30] [C0023734]
[C3FE7F40] [C000DBC0]
 <0>Rebooting in 180 seconds..

Any help will be appreciated.

Thanks,
Sreen

Re: Kernel Panic - not syncing: Attempted to kill init!

[Sebastian Siewior]

* Sreen Tallam | 2008-04-09 19:07:01 [-0700]:

>VFS: Mounted root (jffs2 filesystem) readonly.
>Freeing unused kernel memory: 156k init
>Warning: unable to open an initial console.
>init/main.c -- 819
>init/main.c -- 821
>init/main.c -- 844
>init/main.c -- 704 -- /sbin/tallam_init<0>Kernel panic - not syncing:
>Attempted to kill init!
>Call Trace:
>[C3FE7E60] [C0006D98]  (unreliable)
>[C3FE7EA0] [C001F150]
>[C3FE7EF0] [C0023630]
>[C3FE7F30] [C0023734]
>[C3FE7F40] [C000DBC0]
> <0>Rebooting in 180 seconds..
>

This looks like you are missing /dev/console and probably /dev/null. You
need atleast those two nodes in your rootfs if you are using udev. You
will need a static /dev if you don't use udev/mdev.

>Thanks,
>Sreen
Sebastian

Re: Kernel Panic - not syncing: Attempted to kill init!

[Sreen Tallam]

Hi Sebastian,

Thank you for looking into this issue.
But I am not using udev. And my /dev is empty, there is no devices in there.

Any more hints on this. I would appreciate your follow up.

Thanks,
Sreen

On Thu, Apr 10, 2008 at 1:50 AM, Sebastian Siewior
<linuxppc-embedded@ml.breakpoint.cc> wrote:
> * Sreen Tallam | 2008-04-09 19:07:01 [-0700]:
>
>
>  >VFS: Mounted root (jffs2 filesystem) readonly.
>  >Freeing unused kernel memory: 156k init
>  >Warning: unable to open an initial console.
>  >init/main.c -- 819
>  >init/main.c -- 821
>  >init/main.c -- 844
>  >init/main.c -- 704 -- /sbin/tallam_init<0>Kernel panic - not syncing:
>  >Attempted to kill init!
>  >Call Trace:
>  >[C3FE7E60] [C0006D98]  (unreliable)
>  >[C3FE7EA0] [C001F150]
>  >[C3FE7EF0] [C0023630]
>  >[C3FE7F30] [C0023734]
>  >[C3FE7F40] [C000DBC0]
>  > <0>Rebooting in 180 seconds..
>  >
>
>  This looks like you are missing /dev/console and probably /dev/null. You
>  need atleast those two nodes in your rootfs if you are using udev. You
>  will need a static /dev if you don't use udev/mdev.
>
>  >Thanks,
>  >Sreen
>  Sebastian
>

Kernel panic - not syncing: Attempted to kill init!

[myuboot]

Hi, 

I got the following error trying to bring up the /sbin/init with Kernel
2.6.31 using cramfs filesystem on a MIPS 32 board:

[    1.160000] VFS: Mounted root (cramfs filesystem) readonly on device
31:2.
[    1.171000] Freeing unused kernel memory: 116k freed
[    1.223000] Kernel panic - not syncing: Attempted to kill init!
[    1.229000] Rebooting in 3 seconds..

Using BDI I know the kernel panic happens as soon as
run_init_process("/sbin/init") in init_post() is called. The filesystem
itself seems to be ok, because I can use 'ls' command under u-boot to
see /sbin/init is a symbolic link to busybox. Also the kernel seems to
like the filesystem and can mount the filesystem.  I have for checked
for similar questions for this error, so I tried replacing /sbin/init
with a hello world program, but the result is exactly the same. It seems
neither hello-world or /sbin/init got executed. 

At this point, I don't know how to debug this issue. Any suggestion on
how to debug this issue will be greatly appreciated.

Andrew

Re: Kernel panic - not syncing: Attempted to kill init!

[Gaye Abdoulaye Walsimou]

myuboot@fastmail.fm wrote:
> Hi, 
>
> I got the following error trying to bring up the /sbin/init with Kernel
> 2.6.31 using cramfs filesystem on a MIPS 32 board:
>   

Just to be sure does:
$file vmlinux
$file busybox
give the same result?

Regards

Re: Kernel panic - not syncing: Attempted to kill init!

[myuboot]

On Wed, 11 Nov 2009 08:45 +0100, "Gaye Abdoulaye Walsimou"
<walsimou@walsimou.com> wrote:
> myuboot@fastmail.fm wrote:
> > Hi, 
> >
> > I got the following error trying to bring up the /sbin/init with Kernel
> > 2.6.31 using cramfs filesystem on a MIPS 32 board:
> >   
> 
> Just to be sure does:
> $file vmlinux
> $file busybox
> give the same result?
> 
> Regards
The file result looks ok. The readelf result looks fine too.

file linux-2.6.31/vmlinux root/bin/busybox
linux-2.6.31/vmlinux: ELF 32-bit MSB executable, MIPS, MIPS32 version 1
(SYSV), statically linked, not stripped
root/bin/busybox:     setuid ELF 32-bit MSB executable, MIPS, MIPS32
version 1 (SYSV), dynamically linked (uses shared libs), stripped

Thanks, Andrew

Kernel panic - not syncing: Attempted to kill init!

[史星星(研六 福州)]

Hi,
         I got a problem when trying to boot linux 2.6.32.13 on my Octeon CN5650 board.
Booting logs below:
...omit?.
EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
kjournald starting.  Commit interval 5 seconds
EXT3 FS on mtdblock1, internal journal
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) on device 31:1.
Freeing unused kernel memory: 176k freed
Kernel panic - not syncing: Attempted to kill init!     <-- kernel panic here

What I do:
1?The busybox init is OK in another version kernel .I replace init with ?Hello world? prog or dead loop prog, kernel panic still.
2?
run_init_process(?/sbin/init?) --> kernel_execve --> sys_execve
so I add some debug msgs in sys_execve.

asmlinkage int sys_execve(nabi_no_regargs struct pt_regs regs)
{
         int error;
         char * filename;

    printk("enter sys_execve\n");
         filename = getname((char __user *) (long)regs.regs[4]);
         error = PTR_ERR(filename);
         if (IS_ERR(filename))
                   goto out;
         error = do_execve(filename, (char __user *__user *) (long)regs.regs[5],
                           (char __user *__user *) (long)regs.regs[6], &regs);
    putname(filename);
    printk("out sys_execve\n");
out:
         return error;
}

Boot logs:
VFS: Mounted root (ext3 filesystem) on device 31:1.
Freeing unused kernel memory: 176k freed
enter sys_execve
out sys_execve
Kernel panic - not syncing: Attempted to kill init!     <-- kernel panic here

My question:
1.the kernel panic happened when return to userspace prog?
2.how to solve this problem?

Thank you!

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20110713/134a2b2b/attachment-0001.html 

Kernel panic - not syncing: Attempted to kill init!

[Vladimir Murzin]

2011/7/13 ???(?? ??) <shixingxing@ruijie.com.cn>:
> Hi,
>
> ???????? I got a problem when trying to boot linux 2.6.32.13 on my Octeon
> CN5650 board.
>
> Booting logs below:
>
> ...omit?.
>
> EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
>
> kjournald starting.? Commit interval 5 seconds
>
> EXT3 FS on mtdblock1, internal journal
>
> EXT3-fs: recovery complete.
>
> EXT3-fs: mounted filesystem with ordered data mode.
>
> VFS: Mounted root (ext3 filesystem) on device 31:1.
>
> Freeing unused kernel memory: 176k freed
>
> Kernel panic - not syncing: Attempted to kill init!???? ? kernel panic here
>
>
>
> What I do:
>
> 1?The busybox init is OK in another version kernel .I replace init with
> ?Hello world? prog or dead loop prog, kernel panic still.
>
> 2?
>
> run_init_process(?/sbin/init?) ? kernel_execve ? sys_execve
>
> so I add some debug msgs in sys_execve.
>
>
>
> asmlinkage int sys_execve(nabi_no_regargs struct pt_regs regs)
>
> {
>
> ???????? int error;
>
> ???????? char * filename;
>
>
>
> ?? ?printk("enter sys_execve\n");
>
> ???????? filename = getname((char __user *) (long)regs.regs[4]);
>
> ???????? error = PTR_ERR(filename);
>
> ???????? if (IS_ERR(filename))
>
> ?????????????????? goto out;
>
> ???????? error = do_execve(filename, (char __user *__user *)
> (long)regs.regs[5],
>
> ???????? ????????????????? (char __user *__user *) (long)regs.regs[6],
> &regs);
>
> ??? putname(filename);
>
> ??? printk("out sys_execve\n");
>
> out:
>
> ???????? return error;
>
> }
>
>
>
> Boot logs:
>
> VFS: Mounted root (ext3 filesystem) on device 31:1.
>
> Freeing unused kernel memory: 176k freed
>
> enter sys_execve
>
> out sys_execve
>
> Kernel panic - not syncing: Attempted to kill init!???? ? kernel panic here
>
>
>
> My question:
>
> 1.the kernel panic happened when return to userspace prog?
>
> 2.how to solve this problem?
>
>
>
> Thank you!
>
>
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
>
Hi!

What about "init=" boot option?... and CONFIG_CMDLINE as well?

Kernel panic - not syncing: Attempted to kill init!

[史星星(研六 福州)]

boot option: 
root=/dev/mtdblock1 rootfstype=ext3 rw console=ttyS0,115200 mtdparts=phys_mapped_flash:1024k(bootloader)ro,256k(product_info),256k(system_para),128k(exception_info),128k(bootloader_env),-(reserve);gen_nand.0:128M(root),-(usr)
boot logs:
Using octmgmt0 device
TFTP from server 10.10.10.5; our IP address is 10.10.10.7
Filename 'vmlinux.64'.
Load address: 0x20000000
Loading: T #################################
done
Bytes transferred = 4720693 (480835 hex), 413 Kbytes/sec
argv[2]: root=/dev/mtdblock1
argv[3]: rootfstype=ext3
argv[4]: rw
argv[5]: console=ttyS0,115200
argv[6]: mtdparts=phys_mapped_flash:1024k(bootloader)ro,256k(product_info),256k(system_para),128k(exception_info),128k(bootloader_env),-(reserve);gen_nand.0:128M(root),-(usr)
ELF file is 64 bit
Allocating memory for ELF segment: addr: 0xffffffff81100000 (adjusted to: 0x1100000), size 0x3bdd80
Allocated memory for ELF segment: addr: 0xffffffff81100000, size 0x3bdd80
Processing PHDR 0
  Loading 390a80 bytes at ffffffff81100000
  Clearing 2d300 bytes at ffffffff81490a80
## Loading Linux kernel with entry point: 0xffffffff81105e90 ...
Bootloader: Done loading app on coremask: 0x1
Linux version 2.6.32.13-dirty (root at ubuntu) (gcc version 4.3.3 (Cavium Networks Version: 2_0_0 build 95) ) #5 SMP PREEMPT Tue Jul 12 08:57:24 CST 2011
CVMSEG size: 2 cache lines (256 bytes)
bootconsole [early0] enabled
CPU revision is: 000d0409 (Cavium Octeon)
Checking for the multiply/shift bug... no.
Checking for the daddiu bug... no.
Determined physical RAM map:
 memory: 000000000002c000 @ 0000000001465000 (usable)
 memory: 0000000006c00000 @ 0000000001500000 (usable)
 memory: 0000000007c00000 @ 0000000008200000 (usable)
 memory: 0000000011800000 @ 0000000020000000 (usable)
Wasting 292376 bytes for tracking 5221 unused pages
Zone PFN ranges:
  Normal   0x00001465 -> 0x00031800
Movable zone start PFN for each node
early_node_map[4] active PFN ranges
    0: 0x00001465 -> 0x00001491
    0: 0x00001500 -> 0x00008100
    0: 0x00008200 -> 0x0000fe00
    0: 0x00020000 -> 0x00031800
PERCPU: Embedded 10 pages/cpu @a800000001f91000 s10880 r8192 d21888 u65536
pcpu-alloc: s10880 r8192 d21888 u65536 alloc=16*4096
pcpu-alloc: [0] 0 
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 128415
Kernel command line:  bootoctlinux 0x20000000 root=/dev/mtdblock1 rootfstype=ext3 rw console=ttyS0,115200 mtdparts=phys_mapped_flash:1024k(bootloader)ro,256k(product_info),256k(system_para),128k(exception_info),128k(bootloader_env),-(reserve);gen_nand.0:128M(root),-(usr)
PID hash table entries: 2048 (order: 2, 16384 bytes)
Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)
Inode-cache hash table entries: 32768 (order: 6, 262144 bytes)
Primary instruction cache 32kB, virtually tagged, 4 way, 64 sets, linesize 128 bytes.
Primary data cache 16kB, 64-way, 2 sets, linesize 128 bytes.
Memory: 512256k/524464k available (2615k kernel code, 11800k reserved, 856k data, 176k init, 0k highmem)
Hierarchical RCU implementation.
NR_IRQS:152
console [ttyS0] enabled, bootconsole disabled
console [ttyS0] enabled, bootconsole disabled
Calibrating delay using timer specific routine.. 1501.67 BogoMIPS (lpj=3003356)
Security Framework initialized
Mount-cache hash table entries: 256
Checking for the daddi bug... no.
Brought up 1 CPUs
NET: Registered protocol family 16
nand_init(): registering device resources
bio: create slab <bio-0> at 0
Switching to clocksource OCTEON_CVMCOUNT
NET: Registered protocol family 2
IP route cache hash table entries: 4096 (order: 3, 32768 bytes)
TCP established hash table entries: 16384 (order: 6, 262144 bytes)
TCP bind hash table entries: 16384 (order: 6, 262144 bytes)
TCP: Hash tables configured (established 16384 bind 16384)
TCP reno registered
NET: Registered protocol family 1
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
msgmni has been set to 1001
alg: No test for stdrng (krng)
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0x1180000000800 (irq = 58) is a OCTEON
loop: module loaded
nand id: 0xaddc
NAND device: Manufacturer ID: 0xad, Chip ID: 0xdc (Hynix NAND 512MiB 3,3V 8-bit)
Scanning device for bad blocks
2 cmdlinepart partitions found on MTD device gen_nand.0
nr_parts:2
Creating 2 MTD partitions on "gen_nand.0":
0x000000000000-0x000008000000 : "root"
0x000008000000-0x000020000000 : "usr"
TCP cubic registered
NET: Registered protocol family 17
Bootbus flash: Setting flash for 2MB flash at 0x1fa00000
phys_mapped_flash: Found 1 x16 devices at 0x0 in 8-bit bank
 Amd/Fujitsu Extended Query Table at 0x0040
number of CFI chips: 1
cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.
6 cmdlinepart partitions found on MTD device phys_mapped_flash
Creating 6 MTD partitions on "phys_mapped_flash":
0x000000000000-0x000000100000 : "bootloader"
0x000000100000-0x000000140000 : "product_info"
0x000000140000-0x000000180000 : "system_para"
0x000000180000-0x0000001a0000 : "exception_info"
0x0000001a0000-0x0000001c0000 : "bootloader_env"
0x0000001c0000-0x000000200000 : "reserve"
EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
kjournald starting.  Commit interval 5 seconds
EXT3 FS on mtdblock1, internal journal
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) on device 31:1.
Freeing unused kernel memory: 176k freed


> Hi,
>
> ???????? I got a problem when trying to boot linux 2.6.32.13 on my Octeon
> CN5650 board.
>
> Booting logs below:
>
> ...omit?.
>
> EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
>
> kjournald starting.? Commit interval 5 seconds
>
> EXT3 FS on mtdblock1, internal journal
>
> EXT3-fs: recovery complete.
>
> EXT3-fs: mounted filesystem with ordered data mode.
>
> VFS: Mounted root (ext3 filesystem) on device 31:1.
>
> Freeing unused kernel memory: 176k freed
>
> Kernel panic - not syncing: Attempted to kill init!???? ? kernel panic here
>
>
>
> What I do:
>
> 1?The busybox init is OK in another version kernel .I replace init with
> ?Hello world? prog or dead loop prog, kernel panic still.
>
> 2?
>
> run_init_process(?/sbin/init?) ? kernel_execve ? sys_execve
>
> so I add some debug msgs in sys_execve.
>
>
>
> asmlinkage int sys_execve(nabi_no_regargs struct pt_regs regs)
>
> {
>
> ???????? int error;
>
> ???????? char * filename;
>
>
>
> ?? ?printk("enter sys_execve\n");
>
> ???????? filename = getname((char __user *) (long)regs.regs[4]);
>
> ???????? error = PTR_ERR(filename);
>
> ???????? if (IS_ERR(filename))
>
> ?????????????????? goto out;
>
> ???????? error = do_execve(filename, (char __user *__user *)
> (long)regs.regs[5],
>
> ???????? ????????????????? (char __user *__user *) (long)regs.regs[6],
> &regs);
>
> ??? putname(filename);
>
> ??? printk("out sys_execve\n");
>
> out:
>
> ???????? return error;
>
> }
>
>
>
> Boot logs:
>
> VFS: Mounted root (ext3 filesystem) on device 31:1.
>
> Freeing unused kernel memory: 176k freed
>
> enter sys_execve
>
> out sys_execve
>
> Kernel panic - not syncing: Attempted to kill init!???? ? kernel panic here
>
>
>
> My question:
>
> 1.the kernel panic happened when return to userspace prog?
>
> 2.how to solve this problem?
>
>
>
> Thank you!
>
>
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
>
Hi!

What about "init=" boot option?... and CONFIG_CMDLINE as well?

Kernel panic - not syncing: Attempted to kill init!

[Woody Wu]

Hi, 

"Kernel panic - not syncing: Attempted to kill init!
exitcode=0x0000000b"

I got above message when I am porting 3.4.19 to a s3c2410 board.  I
traced the execution path is: kernel_init() -> init_post() ->
run_init_process("/sbin/init") -> kernel_execve().

And, in the last function kernel_execve, the call of do_execve sucessed.
Then I see a piece of assembly code follows which I cannot understand.

That means, the root file system, which is mtdblock3 in my case, is
mounted and /sbin/init was started to execute, then I got the panic
message.

Is that possible that this is caused by the root file system instead of
the kernel? The root file system is a very old one that can run with an
old kernel 2.6.14.


Do you have any clue?  Thanks in advance!

-- 
woody
I can't go back to yesterday - because I was a different person then.

Kernel panic - not syncing: Attempted to kill init!

[Jello huang]

pls check u root file system.if the root file system is no filesystem or not
* correct .the kernel shall*
*throw the kernel panic*


On 22 November 2012 17:19, Woody Wu <narkewoody@gmail.com> wrote:

> Hi,
>
> "Kernel panic - not syncing: Attempted to kill init!
> exitcode=0x0000000b"
>
> I got above message when I am porting 3.4.19 to a s3c2410 board.  I
> traced the execution path is: kernel_init() -> init_post() ->
> run_init_process("/sbin/init") -> kernel_execve().
>
> And, in the last function kernel_execve, the call of do_execve sucessed.
> Then I see a piece of assembly code follows which I cannot understand.
>
> That means, the root file system, which is mtdblock3 in my case, is
> mounted and /sbin/init was started to execute, then I got the panic
> message.
>
> Is that possible that this is caused by the root file system instead of
> the kernel? The root file system is a very old one that can run with an
> old kernel 2.6.14.
>
>
> Do you have any clue?  Thanks in advance!
>
> --
> woody
> I can't go back to yesterday - because I was a different person then.
>
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
>



-- 
Thanks
Jello Huang
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20121122/8a7a7802/attachment.html>

Kernel panic - not syncing: Attempted to kill init!

[Woody Wu]

Hi, Jello

It's a little strange that your reply not appear on the list (at least
at this moment).

Firstly thank you so much for the suggestion.  But you know, this old
file system is working for a old 2.6 kernel, which was not built by me.
Hence I can see, this file system is okay for at least that version of
kernel.

For the situation, I want to try something from two directions:
1. Is there possible something missed from the kernel side? Any
suggestion?
2. Because it resulted in a kernel panic message, I have no good way to
trace it.  Can I run something else (init=) from the root file system to
gather more information about the file system?  So, how can I play with
the "init=" parameter to help for the case?

Thanks in advance.

-woody

On Thu, Nov 22, 2012 at 05:50:05PM +0800, Jello huang wrote:
> pls check u root file system.if the root file system is no filesystem or not
> * correct .the kernel shall*
> *throw the kernel panic*
> 
> 
> On 22 November 2012 17:19, Woody Wu <narkewoody@gmail.com> wrote:
> 
> > Hi,
> >
> > "Kernel panic - not syncing: Attempted to kill init!
> > exitcode=0x0000000b"
> >
> > I got above message when I am porting 3.4.19 to a s3c2410 board.  I
> > traced the execution path is: kernel_init() -> init_post() ->
> > run_init_process("/sbin/init") -> kernel_execve().
> >
> > And, in the last function kernel_execve, the call of do_execve sucessed.
> > Then I see a piece of assembly code follows which I cannot understand.
> >
> > That means, the root file system, which is mtdblock3 in my case, is
> > mounted and /sbin/init was started to execute, then I got the panic
> > message.
> >
> > Is that possible that this is caused by the root file system instead of
> > the kernel? The root file system is a very old one that can run with an
> > old kernel 2.6.14.
> >
> >
> > Do you have any clue?  Thanks in advance!
> >
> > --
> > woody
> > I can't go back to yesterday - because I was a different person then.
> >
> >
> > _______________________________________________
> > linux-arm-kernel mailing list
> > linux-arm-kernel at lists.infradead.org
> > http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
> >
> 
> 
> 
> -- 
> Thanks
> Jello Huang

-- 
woody
I can't go back to yesterday - because I was a different person then.

Kernel panic - not syncing: Attempted to kill init!

[Baruch Siach]

Hi Woody,

On Mon, Nov 26, 2012 at 03:40:42PM +0800, Woody Wu wrote:
> Firstly thank you so much for the suggestion.  But you know, this old
> file system is working for a old 2.6 kernel, which was not built by me.
> Hence I can see, this file system is okay for at least that version of
> kernel.

Make sure that you have support for ARM OABI if you need it for your older 
filesystem (very likely). See http://wiki.debian.org/ArmEabiPort for some 
background.

baruch

> For the situation, I want to try something from two directions:
> 1. Is there possible something missed from the kernel side? Any
> suggestion?
> 2. Because it resulted in a kernel panic message, I have no good way to
> trace it.  Can I run something else (init=) from the root file system to
> gather more information about the file system?  So, how can I play with
> the "init=" parameter to help for the case?
> 
> Thanks in advance.
> 
> -woody
> 
> On Thu, Nov 22, 2012 at 05:50:05PM +0800, Jello huang wrote:
> > pls check u root file system.if the root file system is no filesystem or not
> > * correct .the kernel shall*
> > *throw the kernel panic*
> > 
> > 
> > On 22 November 2012 17:19, Woody Wu <narkewoody@gmail.com> wrote:
> > 
> > > Hi,
> > >
> > > "Kernel panic - not syncing: Attempted to kill init!
> > > exitcode=0x0000000b"
> > >
> > > I got above message when I am porting 3.4.19 to a s3c2410 board.  I
> > > traced the execution path is: kernel_init() -> init_post() ->
> > > run_init_process("/sbin/init") -> kernel_execve().
> > >
> > > And, in the last function kernel_execve, the call of do_execve sucessed.
> > > Then I see a piece of assembly code follows which I cannot understand.
> > >
> > > That means, the root file system, which is mtdblock3 in my case, is
> > > mounted and /sbin/init was started to execute, then I got the panic
> > > message.
> > >
> > > Is that possible that this is caused by the root file system instead of
> > > the kernel? The root file system is a very old one that can run with an
> > > old kernel 2.6.14.
> > >
> > >
> > > Do you have any clue?  Thanks in advance!
> > >
> > > --
> > > woody
> > > I can't go back to yesterday - because I was a different person then.

-- 
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -

Kernel panic - not syncing: Attempted to kill init!

[Woody Wu]

On Mon, Nov 26, 2012 at 09:51:16AM +0200, Baruch Siach wrote:
> Hi Woody,
> 
> On Mon, Nov 26, 2012 at 03:40:42PM +0800, Woody Wu wrote:
> > Firstly thank you so much for the suggestion.  But you know, this old
> > file system is working for a old 2.6 kernel, which was not built by me.
> > Hence I can see, this file system is okay for at least that version of
> > kernel.
> 
> Make sure that you have support for ARM OABI if you need it for your older 
> filesystem (very likely). See http://wiki.debian.org/ArmEabiPort for some 
> background.
> 
> baruch
> 

Thanks! I've already discovered, that's the exact reason.  Now it works!


> > For the situation, I want to try something from two directions:
> > 1. Is there possible something missed from the kernel side? Any
> > suggestion?
> > 2. Because it resulted in a kernel panic message, I have no good way to
> > trace it.  Can I run something else (init=) from the root file system to
> > gather more information about the file system?  So, how can I play with
> > the "init=" parameter to help for the case?
> > 
> > Thanks in advance.
> > 
> > -woody
> > 
> > On Thu, Nov 22, 2012 at 05:50:05PM +0800, Jello huang wrote:
> > > pls check u root file system.if the root file system is no filesystem or not
> > > * correct .the kernel shall*
> > > *throw the kernel panic*
> > > 
> > > 
> > > On 22 November 2012 17:19, Woody Wu <narkewoody@gmail.com> wrote:
> > > 
> > > > Hi,
> > > >
> > > > "Kernel panic - not syncing: Attempted to kill init!
> > > > exitcode=0x0000000b"
> > > >
> > > > I got above message when I am porting 3.4.19 to a s3c2410 board.  I
> > > > traced the execution path is: kernel_init() -> init_post() ->
> > > > run_init_process("/sbin/init") -> kernel_execve().
> > > >
> > > > And, in the last function kernel_execve, the call of do_execve sucessed.
> > > > Then I see a piece of assembly code follows which I cannot understand.
> > > >
> > > > That means, the root file system, which is mtdblock3 in my case, is
> > > > mounted and /sbin/init was started to execute, then I got the panic
> > > > message.
> > > >
> > > > Is that possible that this is caused by the root file system instead of
> > > > the kernel? The root file system is a very old one that can run with an
> > > > old kernel 2.6.14.
> > > >
> > > >
> > > > Do you have any clue?  Thanks in advance!
> > > >
> > > > --
> > > > woody
> > > > I can't go back to yesterday - because I was a different person then.
> 
> -- 
>      http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
> =}------------------------------------------------ooO--U--Ooo------------{=
>    - baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -

-- 
woody
I can't go back to yesterday - because I was a different person then.