Author Topic: Kernel panic: Attempted to kill init! (Read 3150 times)

b2bpro · « **on:** September 20, 2004, 09:27:56 pm »

I just tried to flash OZ 3.5.1 and it looked like it was doing the right thing. The two 0 to 100% lists of dots did their thing and then I got a message "switching to runlevel 6" and then something else and then it rebooted.

All looked normal so far.

Then pages and pages of text flash by. I am left with a screen with:

Quote

.
. (tons of text)
.
Backtrace:
Function Entered at [<c00b99b0>] from [<c00b9504>]
.
.
. (much more of this sort of thing)
.
.
Code: 0a0000003 e59f029c ebfdd779 e3a03000 (e5033000)
Kernel panic: Attempted to kill init!

Any ideas? I have an 860 and used the Huskey image. I did the flash by removing the power and battery, waiting 10 secs, put back battery, plugged in, pressed OK and on button, option 4, then Yes, then waited and the above is what I got.

Oops - late breaking news. After about 3 minutes I got the following

Quote

apm_console_blank: blank=1
apm_console_blank: blank=0

Do I just wait this out? Is this normal?

sriley · « **Reply #1 on:** September 20, 2004, 09:40:31 pm »

Similar thing happened to me, I had to format the user partition (using the Cacko installer.sh) after installing 3.5.1. Worked like a champ.

b2bpro · « **Reply #2 on:** September 20, 2004, 09:45:24 pm »

How did you format the user partition? Did you have to resize the partition or anything? I used pdaxrom to resize the partition previously. If so - what size partition?

Did you just format the user partition and then reboot or did you have to reflash again afterwards?

(PS nice to have someone with the same problem that got fixed)

sriley · « **Reply #3 on:** September 20, 2004, 09:55:54 pm »

It was a PITA, I was running Cacko Qtopia 1.21b on my 760 with a flash partition of 27 MB. Without resizing, I flashed OZ-OPIE 3.5.1 and had many evil symptoms including the "tried to kill init". The fix, for me was to put Cacko's install.sh and tools.tar on my SD card (couldn't use the Z to do it, either) then boot to the installer. One of its options is to format the user partition. Afterward, I rebooted. OZ booted correctly after that. End of story.

Hope that helps.

b2bpro · « **Reply #4 on:** September 20, 2004, 10:58:30 pm »

Woo hoo - it worked. Still some minor problems, but I'll deal with those tomorrow.

Thanks

sriley · « **Reply #5 on:** September 20, 2004, 11:52:57 pm »

Glad to hear it.

bonsay · « **Reply #6 on:** September 21, 2004, 05:03:44 pm »

Hello!
I have a Zaurus C860 and had problems with some hardware features in the OZ 3.2.

Now i wanted to install the OZ 3.5.1 and i received a kernel panic.
I used the huskey zImage.

After i read this tip, i used the "format the user partition" option from the Cacko-Rom.
Then i tried to install the OZ again, but same error message again:

Quote

...
Currently defined functions:
<a huge list of commands>

Kernel panic: Attempted to kill init!
apm_console_blank: blank:1
apm_console_blank: blank:0

Can anybody help me? I dont know what i should do now!
Thx for help!

sriley · « **Reply #7 on:** September 21, 2004, 07:35:44 pm »

What I did was flash OZ-OPIE 3.5.1 on my 760.

When I got the kernel panic, I didn't fully flash Cacko, I just used it to format the user partition.

Once the user partition was formatted I rebooted without flashing OZ again. OZ booted and created a bunch of files and everything was OK.

lardman · « **Reply #8 on:** September 21, 2004, 07:43:31 pm »

I don't get a kernel panic, just a couple of 'blah-blah dir with children, removing them too' warnings about my filesystem whenever I re-boot (which is happening alot at the mo). I wonder if this is in any way related to the fact that once I suspend I can't resume without a reboot (actually I used to be able to suspend then resume, but only if I did it quickly)?

Does anyone know what the problem is here?

Surely having old stuff in the partition isn't going to break anything...?

Si

sriley · « **Reply #9 on:** September 21, 2004, 07:50:27 pm »

I'm having the same issues with needing to reboot after suspending. When I hit either power button it comes on but is unresponsive for several seconds, then suspends itself again. When I reboot I get those same filesystem errors.

Formatting the user partition is just what got OZ to boot the first time for me. Prior to that I had various wierd filesystem issues dealing with inode #32 and kernel panics and could never get to a GUI.

lardman · « **Reply #10 on:** September 21, 2004, 07:55:05 pm »

Quote

I'm having the same issues with needing to reboot after suspending. When I hit either power button it comes on but is unresponsive for several seconds, then suspends itself again.

Unresponsive for several seconds is par for the course as far as I know, but the immediate suspend isn't good.

I can't even resume after I suspend, I have to reboot (though it may be battery charge related as I can now suspend and resume again - after having it plugged in for 30min - I'm not stupid though, it was actually fully charged yesterday - very odd).

I'd still be interested to know whether those inode errors are a bad thing, and why they occur in the first place.

Si

News:

Author Topic: Kernel panic: Attempted to kill init! (Read 3150 times)