Hi Guys,

I compile one linux kernel, but while I boot it on the VMWare, I meet the panic error.

#########################################################
Freeing unused kernel memory: 1060K
Write protecting the kernel read-only data: 14336K
......
[end Kernel panic-not syncing, Attempted to kill init! exit code=0x0000000b".
************************************************************

Could anyone help me to take a look at this problem?
Thanks!

Attached Thumbnails

   

Welcome to LQ! Can you say more about your .config? (changed/added?) distro?
Might it be this? If not, can you post a picture of panic? And 'more info'
Is it trying to find&mount /? Again, details; try more web-searching and you will see what details! (Without the right/magic few keywords, it's like just the error "Command not found" without essential details, since, although verbose, the above error is generic, unfortunately)

Not syncing usually happens when the kernel can't read its root device. Are you using an initrd with this kernel? if not, you must build the sata driver and the filesystem driver directly into the kernel, not as modules.

1 members found this post helpful.

Thanks for you quick reply!

I attach the captured screen and .config file.

Attached Thumbnails

   

Attached Files

menuconfig.txt (81.9 KB, 365 views)

I didn't use the initrd with my kernel, and SCSI driver and filesystem driver are compiled directly into the kernel.
The .config file is attached, please help me to check it, thanks so much!

Attached Files

menuconfig.txt (81.9 KB, 417 views)

1 members found this post helpful.

Edit: ooops, I see you edit-added screen-shots to #1!!! I'll have a look, but I'm far from expert. Edit2: Looks like msgs between those 2 screenshots are missing web-searching some of the stack, finds mentions of LVM, but I doubt that's it, because it says root sda2 mounted ok!!! (see below: info asked for)

Well, those VMware things look enabled ok. And it sounds like you know this stuff!

Any way you can take a picture/snapshot of (edit:ALL the msgs before) the panic? Could you try running it in VirtualBox? (that would eliminate/implicate VMware) Is it LFS? Where did you get that .config?

Or maybe it's simply something wrong with GRUB spec of root... Or fstab... Can you post/attach those? (edit: no, it mounted sda2=root ok, but what did it say after that, before panic?) VMware version(&logs)?

Excellent that you posted the .config!!! But it's a bit like: here's my .iso: I get "Command not found" (edit: what happened in between?) The grub&fstab might help, but a screenshot (or actual messages, tho I don't know how to capture them as text when booting panics...can anyone else advise here???) is ideal. (VBox has right-ctrl+e, tho msgs may have scrolled off) And IF some generous LQ'er with VMware has ..., they could tryout your .config

Hi Sir,

Thanks for your suggestion!
I add one important captured screen besides 1.jpg and 2.jpg, it seems my init program (/bin/bash) meet the segfault error.
So strange, I use the bash source code to install the bash on the root device, why there is segfault error?
Yes, it's LFS. The .config is from the my linux kernel configuration by "make menuconfig" based on default config.

Here is the grub config for my linux kernel. it's very simple.
###############################
menuentry 'Test_Kernel' {
set root='hd0,2'
linux /boot/bzImage root=/dev/sda2 init=/bin/bash ro
}
###############################

Attached Thumbnails

 

Thanks very much for your tips!

I can boot my kernel successfully. The reason why this panic happens is that my libc-XXX.so has problems.

Best Regards!
Tao

Things to know about this message:

• init refers to "process #1," which is hand-built by the kernel when it boots, and which must successfully start and thereafter must not die because the system cannot run without it.
• This message appears in either case. (In this case, probably the former.)
• "Not syncing" means that the kernel was not in the process of writing data to disk when the system died.

Inability to mount the root filesystem, disk driver issues and so forth can all lead to this message. Error messages immediately preceding the actual panic should point to the root cause.

1 members found this post helpful.

Thanks very much for your information!

post reported..........................................

edit:
no, this is legit. Sorry. OP should consider using a different image uploader...