Visit Our UNIX and Linux User Community


kenel panic not syncing


 
Thread Tools Search this Thread
Operating Systems Linux Ubuntu kenel panic not syncing
# 1  
Old 03-04-2012
kenel panic not syncing

I installed a new kernel 3.0.22 on ubuntu server 11.04 32 bit.
when I select the kenel from boot loader it stops when
Code:
loading initial ramdisk...
I added all_generic_ide at the end of linux line and also added dev/sda1 to linux line: root=UUID=dev/sda1

now it says that
Code:
     kernel panic - not synching: attempts to kill init init not tainted 3.0.22 call trace: 
(some addresses like) ?printkxxxx 
do_exit... 
vfs_writexxx 
do_group_exit... 
sys_exit_groupxxxx 
sysenter_do_callxxxxxx

I have checked from the first kernel with df -h, it says that my main drive which is the root file system is /dev/sda1.
so! what's the problem?
# 2  
Old 03-05-2012
You may need to capture more lines, and in more detail too, to see what's actually going on. If logging can't be arranged, a digital photo will help.

init is having trouble running for some reason. did it ever print anything to the screen?
# 3  
Old 03-07-2012
new kernel comile, root file system fails to mount

well, thanks for the reply. I checked /dev/disk/by-uuid, you know, ../../dev/sda1 is the only device in this directory.
you know, my guess is that i probably don't select some particular modules required to load the root filesystem. Because I tested the new kernel on 32 bit, 64 bit and even another distribution of linux, and I have the same problem everywhere.

Let's be more accurate. when I choose my customized kernel, first it said :
Code:
Booting a command list 
alloc magic is broken at 0x3f503710 
Aborted. Press any key to exit.

when i edited the boot with all_generic_ide and root=dev/sda1
it output some other things, I got a shot of the screen which is attached.
I would
thank if you help me fix the problem.

the attached file is mykernel .config customized with make menuconfig
more info:
Code:
processor    : 0
vendor_id    : GenuineIntel
cpu family    : 6
model        : 13
model name    : Intel(R) Pentium(R) M processor 1.40GHz
stepping    : 8
cpu MHz        : 600.000
cache size    : 2048 KB
fdiv_bug    : no
hlt_bug        : no
f00f_bug    : no
coma_bug    : no
fpu        : yes
fpu_exception    : yes
cpuid level    : 2
wp        : yes
flags        : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov clflush dts acpi mmx fxsr sse sse2 ss tm pbe nx up bts est tm2
bogomips    : 1198.00
clflush size    : 64
cache_alignment    : 64
address sizes    : 32 bits physical, 32 bits virtual
power management:

# 4  
Old 03-08-2012
This time I tried the installation on my own laptop, again the same problem. I also check out what the uuid string points to.. and it's correct it points to the right device in my machine, which is /dev/sda6. Have a look here:

Code:
root@saman-HP-ProBook-4530s:/home/saman# df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/sda6             186G   16G  161G   9% /
none                  1.9G  708K  1.9G   1% /dev
none                  2.0G  248K  2.0G   1% /dev/shm
none                  2.0G  224K  2.0G   1% /var/run
none                  2.0G     0  2.0G   0% /var/lock
/dev/sdb1             7.5G  5.7G  1.8G  76% /media/Saman

well, this one says that my / root file system and as you said the directory where /boot is located is /dev/sda6, now let's jump to /dev/disk/by-uuid/ n c the string:
Code:
lrwxrwxrwx 1 root root 10 2012-03-08 15:54 0b4e5053-302a-4977-a1e0-0e128a1e3b8c -> ../../sda5
lrwxrwxrwx 1 root root 10 2012-03-08 15:54 3149-0944 -> ../../sdb1
lrwxrwxrwx 1 root root 10 2012-03-08 15:54 620020A200207EE3 -> ../../sda2
lrwxrwxrwx 1 root root 10 2012-03-08 15:54 642824CF2824A252 -> ../../sda3
lrwxrwxrwx 1 root root 10 2012-03-08 15:54 a43da646-97b6-4e71-b0fa-bb27d0d52a4b -> ../../sda6
lrwxrwxrwx 1 root root 10 2012-03-08 15:54 ea0965c8-d66b-4f0e-bb20-ed629eb011fc -> ../../sda7
lrwxrwxrwx 1 root root 10 2012-03-08 15:54 FED00908D008C93B -> ../../sda1

well, it's right, the bootloader shows the right string which is a43xxxx. Though I wonder why when I load it in recovery mode, it prompts an alert n says:

Code:
ALET! root=uuid=a43xxxxxx does not exists!!

this is what is inside /boot/grub/grub.cfg
Code:
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
  set have_grubenv=true
  load_env
fi
set default="0"
if [ "${prev_saved_entry}" ]; then
  set saved_entry="${prev_saved_entry}"
  save_env saved_entry
  set prev_saved_entry=
  save_env prev_saved_entry
  set boot_once=true
fi

function savedefault {
  if [ -z "${boot_once}" ]; then
    saved_entry="${chosen}"
    save_env saved_entry
  fi
}

function recordfail {
  set recordfail=1
  if [ -n "${have_grubenv}" ]; then if [ -z "${boot_once}" ]; then save_env recordfail; fi; fi
}

function load_video {
  insmod vbe
  insmod vga
  insmod video_bochs
  insmod video_cirrus
}

insmod part_msdos
insmod ext2
set root='(/dev/sda,msdos6)'
search --no-floppy --fs-uuid --set=root a43da646-97b6-4e71-b0fa-bb27d0d52a4b
if loadfont /usr/share/grub/unicode.pf2 ; then
  set gfxmode=auto
  load_video
  insmod gfxterm
fi
terminal_output gfxterm
insmod part_msdos
insmod ext2
set root='(/dev/sda,msdos6)'
search --no-floppy --fs-uuid --set=root a43da646-97b6-4e71-b0fa-bb27d0d52a4b
set locale_dir=($root)/boot/grub/locale
set lang=en_US
insmod gettext
if [ "${recordfail}" = 1 ]; then
  set timeout=-1
else
  set timeout=10
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=white/black
set menu_color_highlight=black/light-gray
if background_color 44,0,30; then
  clear
fi
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
if [ ${recordfail} != 1 ]; then
  if [ -e ${prefix}/gfxblacklist.txt ]; then
    if hwmatch ${prefix}/gfxblacklist.txt 3; then
      if [ ${match} = 0 ]; then
        set linux_gfx_mode=keep
      else
        set linux_gfx_mode=text
      fi
    else
      set linux_gfx_mode=text
    fi
  else
    set linux_gfx_mode=keep
  fi
else
  set linux_gfx_mode=text
fi
export linux_gfx_mode
if [ "$linux_gfx_mode" != "text" ]; then load_video; fi
menuentry 'Ubuntu, with Linux 3.0.22-kernel-0-rt37' --class ubuntu --class gnu-linux --class gnu --class os {
    recordfail
    set gfxpayload=$linux_gfx_mode
    insmod part_msdos
    insmod ext2
    set root='(/dev/sda,msdos6)'
    search --no-floppy --fs-uuid --set=root a43da646-97b6-4e71-b0fa-bb27d0d52a4b
    linux    /boot/vmlinuz-3.0.22-kernel-0-rt37 root=UUID=a43da646-97b6-4e71-b0fa-bb27d0d52a4b ro   quiet splash vt.handoff=7
    initrd    /boot/initrd.img-3.0.22-kernel-0-rt37
}
menuentry 'Ubuntu, with Linux 3.0.22-kernel-0-rt37 (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
    recordfail
    set gfxpayload=$linux_gfx_mode
    insmod part_msdos
    insmod ext2
    set root='(/dev/sda,msdos6)'
    search --no-floppy --fs-uuid --set=root a43da646-97b6-4e71-b0fa-bb27d0d52a4b
    echo    'Loading Linux 3.0.22-kernel-0-rt37 ...'
    linux    /boot/vmlinuz-3.0.22-kernel-0-rt37 root=UUID=a43da646-97b6-4e71-b0fa-bb27d0d52a4b ro single 
    echo    'Loading initial ramdisk ...'
    initrd    /boot/initrd.img-3.0.22-kernel-0-rt37
}
submenu "Previous Linux versions" {
menuentry 'Ubuntu, with Linux 2.6.38-8-generic' --class ubuntu --class gnu-linux --class gnu --class os {
    recordfail
    set gfxpayload=$linux_gfx_mode
    insmod part_msdos
    insmod ext2
    set root='(/dev/sda,msdos6)'
    search --no-floppy --fs-uuid --set=root a43da646-97b6-4e71-b0fa-bb27d0d52a4b
    linux    /boot/vmlinuz-2.6.38-8-generic root=UUID=a43da646-97b6-4e71-b0fa-bb27d0d52a4b ro   quiet splash vt.handoff=7
    initrd    /boot/initrd.img-2.6.38-8-generic
}
menuentry 'Ubuntu, with Linux 2.6.38-8-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
    recordfail
    set gfxpayload=$linux_gfx_mode
    insmod part_msdos
    insmod ext2
    set root='(/dev/sda,msdos6)'
    search --no-floppy --fs-uuid --set=root a43da646-97b6-4e71-b0fa-bb27d0d52a4b
    echo    'Loading Linux 2.6.38-8-generic ...'
    linux    /boot/vmlinuz-2.6.38-8-generic root=UUID=a43da646-97b6-4e71-b0fa-bb27d0d52a4b ro single 
    echo    'Loading initial ramdisk ...'
    initrd    /boot/initrd.img-2.6.38-8-generic
}
}
### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###

### BEGIN /etc/grub.d/20_memtest86+ ###
menuentry "Memory test (memtest86+)" {
    insmod part_msdos
    insmod ext2
    set root='(/dev/sda,msdos6)'
    search --no-floppy --fs-uuid --set=root a43da646-97b6-4e71-b0fa-bb27d0d52a4b
    linux16    /boot/memtest86+.bin
}
menuentry "Memory test (memtest86+, serial console 115200)" {
    insmod part_msdos
    insmod ext2
    set root='(/dev/sda,msdos6)'
    search --no-floppy --fs-uuid --set=root a43da646-97b6-4e71-b0fa-bb27d0d52a4b
    linux16    /boot/memtest86+.bin console=ttyS0,115200n8
}
### END /etc/grub.d/20_memtest86+ ###

### BEGIN /etc/grub.d/30_os-prober ###
menuentry "Windows 7 (loader) (on /dev/sda1)" --class windows --class os {
    insmod part_msdos
    insmod ntfs
    set root='(/dev/sda,msdos1)'
    search --no-floppy --fs-uuid --set=root FED00908D008C93B
    chainloader +1
}
### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries.  Simply type the
# menu entries you want to add after this comment.  Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###

### BEGIN /etc/grub.d/41_custom ###
if [ -f  $prefix/custom.cfg ]; then
  source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###

if I install the kernel having the same options selected as ubuntu-generic-pae kernel installed from DVD, it works fine. But when i try to load the customized one i face this problem. My guess is that i forget to select some important options required to load the root file system or ... i don't know. bcoz even if that was the case, the Alert file system does not exist message is relevant to it.

What do you think?
# 5  
Old 03-08-2012
If it says 'busybox', it's obviously able to boot. That's nothing inside the kernel, that's a program, loaded from the initrd.

My guess is you didn't include the correct disk drivers, or built your disk drivers in as modules <M> instead of building them right into the kernel <*>. Try selecting the same disk controller drivers in your kernel as in the generic one. Make sure AHCI at the very least is built in <*>, hundreds of boards use that for SATA.

Though another thought occurs to me.

You are using your own initrd, yes? Not just the one that came with your old kernel? One of the main ideas of an initrd is the ability to load disk controller drivers as modules(which is otherwise a big fat catch-22), and the modules in the other kernel's initrd flagrantly won't be modules for your kernel.

If possible I'd avoid using an initrd at all. Just build your disk controller drivers right in, and give root=/dev/sda6
This User Gave Thanks to Corona688 For This Post:
# 6  
Old 03-08-2012
Quote:
Originally Posted by Corona688
My guess is you didn't include the correct disk drivers, or built your disk drivers in as modules <M> instead of building them right into the kernel <*>. Try selecting the same disk controller drivers in your kernel as in the generic one. Make sure AHCI at the very least is built in <*>, hundreds of boards use that for SATA.
well, I don't think if that's the case. I included all the modules in the kernel <*>. I didn't set anything as <M>, you know if the kernel is gonna get customized minimally so let all the modules be <*>

Though another thought occurs to me.

Quote:
Originally Posted by Corona688
You are using your own initrd, yes? Not just the one that came with your old kernel? One of the main ideas of an initrd is the ability to load disk controller drivers as modules(which is otherwise a big fat catch-22), and the modules in the other kernel's initrd flagrantly won't be modules for your kernel.

If possible I'd avoid using an initrd at all. Just build your disk controller drivers right in, and give root=/dev/sda6
I think I am using my own initrd as I use the following command to create a linux-image n linux-headers in my directory:
Code:
make-kpkg --initrd --append-to-version=-my-kernel linux_image linux_headers

So, if i attempt not to use my own initrd, I think i shall not use the above command. instead I will go for make, make modules, make modules_install, copying bzImage inside arch/x86/boot/ to /boot and rename it as vmlinuzxxxxx. I also need to copy the .config file to /boot/config-versionxxxx n finally update-grub, that's all.
I am gonna try installing the kernel as you said n post the result.

Uh, when I tried to load the previous command a minute before, i got the following failures:

Code:
acpiphp-ibm
ibm_acpiphp_init
acpi_walk_namespace
failed

I think this should all be kinda relevant to the controller device drivers.
# 7  
Old 03-09-2012
unable to open rtc device (rtc0) n udev_fallback_graphics main process (914) termination

hi

I added some other modules in the .config file, looking from the current kernel configuration. Now, I the the the below two problem when I select the new kernel in boot loader in safe or normal mode:

in normal mode:
Code:
[1.737135] drivers/rtc/hctosys.c:unable to open rtc device (rtc0)

in safe mode:

Code:
init:udev_fallback_graphics main process (914) terminated with status 1, the disk drive for / is not ready yet or not present.
continue to wait; or press S to skip mounting or M for manual recovery

if I press S, then I can login to the system! and, when i run the following command dpkg -i to install kernel_image and the kernel_headers a window pops up n says that fglrx error. i think that's got something to do with the ATI grahics driver.
do you have any idea how i can fix the two problems? especially the first one, as I need this cutomized kernel to be set as a real time kernel.

see, is the rtc error because my laptop motherboard does not support rtc?

Last edited by dr_mabuse; 03-09-2012 at 03:07 PM..

Previous Thread | Next Thread
Test Your Knowledge in Computers #337
Difficulty: Easy
:set number in vi will add line numbers to the file and automatically save to disk.
True or False?

9 More Discussions You Might Find Interesting

1. Red Hat

Kernel panic-not syncing

dear experts linux i am using RHEL 5.5 run on a physical server. i am front of a big trouble, the Rhel can't run correctly , it show me this error message in black screen: reading all physical volumes. this my take a while .. found volume group "VolGroup00" using metadata type lvm2 9... (1 Reply)
Discussion started by: wassimpb
1 Replies

2. Red Hat

Error: kernal panic not syncing

HI All, server stopped here, we are suspecting server crash, need install new OS. Any suggestions on this. kindly help to us. Thanks Rajesh (0 Replies)
Discussion started by: Rajesh_Apple
0 Replies

3. Slackware

Help with kernel panic - not syncing slackware 13.0

Hi, first of all I'm 110% newbie, sorry for any mistake if I made it. In my country there are no normal or active linux forums, so i found this forum. Ok, that's for begining, but not for may real problem. --------------------------------------------------- I am system administrator... (4 Replies)
Discussion started by: ElvijsL
4 Replies

4. Filesystems, Disks and Memory

RAID syncing 2 partitions

Hi all, I tried setting up RAID between 2 partitions and it was success. If I write some things on /dev/md0, both partition got affected. Then I stop the RAID, and I mounted one of my partition and I created a file in it. Now I started the RAID (mdadm --assemble --scan) What I expected... (1 Reply)
Discussion started by: lakshmananindia
1 Replies

5. UNIX Desktop Questions & Answers

kernel panic-not syncing:fatal exception while booting

Hi ALL, I am getting error.. kernal panic-not syncing:fatal exception while booting. Please help me.. Thanks Jack (7 Replies)
Discussion started by: jack00423
7 Replies

6. Linux

Kernel panic - not syncing: cannot execute a PAE-enabled kernel on PAE-less CPU

ok so I just installed fedora core 6 on my dell inspiron 700m and I go to boot into linux and I get this error. Has anyone seen this before? I also had XP Pro and Vista installed on this pc prior to putting fedora core 6 on the machine. I'm trying to setup a triple boot system. Please Help... (2 Replies)
Discussion started by: dave043
2 Replies

7. UNIX for Dummies Questions & Answers

Kernel panic - not syncing == While RHEL AS install

I am trying to Install RHEL AS 4 on x86 pc, through VNC and got the below error, Am not pretty sure as how to resolve this. Can some one guide me through the process, or what might be missing.... Have Installed RHEL, many a times but cudnt find this out... Wud appreciate an early reply ......... (0 Replies)
Discussion started by: Crazy_murli
0 Replies

8. Linux

NTPD seems to be not syncing !!!

Hi Linux Admin Guys My onsite server is always 15 min slow and seems like NTPD (Network Time Protocol (NTP) daemon) not running properly. can anyone suggest me how to rectify this problem? we can't seem to get NTP to properly sync the clock. Any help is resolving the issue will be helpful.... (12 Replies)
Discussion started by: csaha
12 Replies

9. UNIX for Advanced & Expert Users

filesystem syncing

Does anyone know if there is free software that can keep 2 filesystem on remote machines , synced. This will be part of our Disaster Recovery to keep one machine off site , which will take over should the need arise.. Thanks (6 Replies)
Discussion started by: markdr011
6 Replies

Featured Tech Videos