just updated urpmi and after the update i updated to the latest kernel as updates were available. after the process i restarted the pc and got to the grub2 menu where when i select mageia i get a black box with the error saying "file /boot/initrd-desktop-img" not found. a black screen follows saying kernel panic not syncing VFS. Unable to mount root fs on unknown - block(0,0) and this black screen does not go forward. Even alt ctrl del does not work. I switch off and on the pc the go to recovery and select kernel 3.19.1 desktop and it works fine. Please assist. Should i delete the latest kernel update?
No please keep it for now and select the older one to use the machine. Are you sure it says file /boot/initrd-desktop-img" and not file /boot/initrd-desktop.img"? Could you please run the following and attach all the terminal output: su fdisk -l ls -l /boot cat /boot/grub2/grub.cfg Thanks
Keywords: (none) => NEEDINFOCC: (none) => zen25000
Below are the details as requested. Please note i had removed the offending kernel last night and all is well. I wont update the sys now for a couple of days. fdisk -l [root@wolf ~]# fdisk -l Disk /dev/sda: 149.1 GiB, 160041885696 bytes, 312581808 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x000c6a85 Device Boot Start End Sectors Size Id Type /dev/sda1 * 2048 304173922 304171875 145G 83 Linux /dev/sda2 304177104 312576704 8399601 4G 5 Extended /dev/sda5 304177152 312576704 8399553 4G 82 Linux swap / Solaris Disk /dev/sdb: 465.8 GiB, 500107862016 bytes, 976773168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x000257c1 Device Boot Start End Sectors Size Id Type /dev/sdb1 * 2048 83892223 83890176 40G 83 Linux /dev/sdb2 959995904 976773119 16777216 8G 82 Linux swap / Solaris /dev/sdb3 83892224 959995903 876103680 417.8G 83 Linux Partition table entries are not in disk order. ls -l /boot [root@wolf ~]# ls -l /boot total 51252 -rw-r--r-- 1 root root 171234 Feb 9 12:18 config-3.19.0-desktop-1.mga5 -rw-r--r-- 1 root root 171245 Mar 11 04:12 config-3.19.1-desktop-1.mga5 -rw-r--r-- 1 root root 171245 Mar 15 03:59 config-3.19.1-desktop-2.mga5 drwxr-xr-x 2 root root 4096 Feb 28 01:03 dracut/ -rwxr-xr-x 1 root root 562176 Mar 15 13:11 gfxmenu* drwxr-xr-x 2 root root 4096 Feb 12 02:12 grub/ drwxr-xr-x 6 root root 4096 Mar 19 22:29 grub2/ -rw------- 1 root root 9226422 Mar 15 12:25 initrd-3.19.0-desktop-1.mga5.img -rw------- 1 root root 9223334 Mar 15 13:08 initrd-3.19.1-desktop-1.mga5.img -rw------- 1 root root 9190156 Mar 16 06:38 initrd-3.19.1-desktop-2.mga5.img lrwxrwxrwx 1 root root 32 Mar 16 06:38 initrd.img -> initrd-3.19.1-desktop-2.mga5.img -rw-r--r-- 1 root root 308314 Sep 24 00:38 mageia.bmp -rw-r--r-- 1 root root 245356 Feb 9 12:18 symvers-3.19.0-desktop-1.mga5.xz -rw-r--r-- 1 root root 245720 Mar 11 04:12 symvers-3.19.1-desktop-1.mga5.xz -rw-r--r-- 1 root root 245512 Mar 15 03:59 symvers-3.19.1-desktop-2.mga5.xz -rw-r--r-- 1 root root 3222798 Feb 9 12:18 System.map-3.19.0-desktop-1.mga5 -rw-r--r-- 1 root root 3222929 Mar 11 04:12 System.map-3.19.1-desktop-1.mga5 -rw-r--r-- 1 root root 3222968 Mar 15 03:59 System.map-3.19.1-desktop-2.mga5 lrwxrwxrwx 1 root root 29 Mar 16 06:38 vmlinuz -> vmlinuz-3.19.1-desktop-2.mga5 -rw-r--r-- 1 root root 4341120 Feb 9 12:18 vmlinuz-3.19.0-desktop-1.mga5 -rw-r--r-- 1 root root 4340800 Mar 11 04:12 vmlinuz-3.19.1-desktop-1.mga5 -rw-r--r-- 1 root root 4340928 Mar 15 03:59 vmlinuz-3.19.1-desktop-2.mga5 lrwxrwxrwx 1 root root 29 Mar 19 21:15 vmlinuz-desktop -> vmlinuz-3.19.2-desktop-1.mga5 [root@wolf ~]# cat /boot/grub2/grub.cfg # # DO NOT EDIT THIS FILE # # It is automatically generated by grub2-mkconfig using templates # from /etc/grub.d and settings from /etc/default/grub # ### BEGIN /etc/grub.d/00_header ### if [ -s $prefix/grubenv ]; then load_env fi if [ "${next_entry}" ] ; then set default="${next_entry}" set next_entry= save_env next_entry set boot_once=true else set default="0" fi if [ x"${feature_menuentry_id}" = xy ]; then menuentry_id_option="--id" else menuentry_id_option="" fi export menuentry_id_option 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 load_video { if [ x$feature_all_video_module = xy ]; then insmod all_video else insmod efi_gop insmod efi_uga insmod ieee1275_fb insmod vbe insmod vga insmod video_bochs insmod video_cirrus fi } if loadfont unicode ; then set gfxmode=1024x768x32 load_video insmod gfxterm set locale_dir=$prefix/locale set lang=en_IN insmod gettext fi terminal_output gfxterm insmod part_msdos insmod ext2 set root='hd0,msdos1' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 820b249f-2aff-44d6-8c77-9f66456b3527 else search --no-floppy --fs-uuid --set=root 820b249f-2aff-44d6-8c77-9f66456b3527 fi insmod gfxmenu loadfont ($root)/boot/grub2/themes/maggy/MageiaLogo-Bold-16.pf2 loadfont ($root)/boot/grub2/themes/maggy/MageiaLogo-Bold-20.pf2 loadfont ($root)/boot/grub2/themes/maggy/MageiaLogo-Bold-28.pf2 loadfont ($root)/boot/grub2/themes/maggy/MageiaLogo-Regular-20.pf2 insmod png set theme=($root)/boot/grub2/themes/maggy/theme.txt export theme if [ x$feature_timeout_style = xy ] ; then set timeout_style=menu set timeout=10 # Fallback normal timeout code in case the timeout_style feature is # unavailable. else set timeout=10 fi ### END /etc/grub.d/00_header ### ### BEGIN /etc/grub.d/10_linux ### menuentry 'Mageia' --class mageia --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-820b249f-2aff-44d6-8c77-9f66456b3527' { set gfxpayload=text insmod gzio insmod part_msdos insmod ext2 set root='hd0,msdos1' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 820b249f-2aff-44d6-8c77-9f66456b3527 else search --no-floppy --fs-uuid --set=root 820b249f-2aff-44d6-8c77-9f66456b3527 fi echo 'Loading Linux 3.19.1-desktop-2.mga5 ...' linux /boot/vmlinuz-3.19.1-desktop-2.mga5 root=UUID=820b249f-2aff-44d6-8c77-9f66456b3527 ro splash quiet resume=UUID=414e6563-4bda-41f8-ab41-adf38b01216d echo 'Loading initial ramdisk ...' initrd /boot/initrd-3.19.1-desktop-2.mga5.img } submenu 'Advanced options for Mageia' $menuentry_id_option 'gnulinux-advanced-820b249f-2aff-44d6-8c77-9f66456b3527' { menuentry 'Mageia, with Linux 3.19.1-desktop-2.mga5' --class mageia --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-3.19.1-desktop-2.mga5-advanced-820b249f-2aff-44d6-8c77-9f66456b3527' { set gfxpayload=text insmod gzio insmod part_msdos insmod ext2 set root='hd0,msdos1' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 820b249f-2aff-44d6-8c77-9f66456b3527 else search --no-floppy --fs-uuid --set=root 820b249f-2aff-44d6-8c77-9f66456b3527 fi echo 'Loading Linux 3.19.1-desktop-2.mga5 ...' linux /boot/vmlinuz-3.19.1-desktop-2.mga5 root=UUID=820b249f-2aff-44d6-8c77-9f66456b3527 ro splash quiet resume=UUID=414e6563-4bda-41f8-ab41-adf38b01216d echo 'Loading initial ramdisk ...' initrd /boot/initrd-3.19.1-desktop-2.mga5.img } menuentry 'Mageia, with Linux 3.19.1-desktop-1.mga5' --class mageia --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-3.19.1-desktop-1.mga5-advanced-820b249f-2aff-44d6-8c77-9f66456b3527' { set gfxpayload=text insmod gzio insmod part_msdos insmod ext2 set root='hd0,msdos1' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 820b249f-2aff-44d6-8c77-9f66456b3527 else search --no-floppy --fs-uuid --set=root 820b249f-2aff-44d6-8c77-9f66456b3527 fi echo 'Loading Linux 3.19.1-desktop-1.mga5 ...' linux /boot/vmlinuz-3.19.1-desktop-1.mga5 root=UUID=820b249f-2aff-44d6-8c77-9f66456b3527 ro splash quiet resume=UUID=414e6563-4bda-41f8-ab41-adf38b01216d echo 'Loading initial ramdisk ...' initrd /boot/initrd-3.19.1-desktop-1.mga5.img } menuentry 'Mageia, with Linux 3.19.0-desktop-1.mga5' --class mageia --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-3.19.0-desktop-1.mga5-advanced-820b249f-2aff-44d6-8c77-9f66456b3527' { set gfxpayload=text insmod gzio insmod part_msdos insmod ext2 set root='hd0,msdos1' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 820b249f-2aff-44d6-8c77-9f66456b3527 else search --no-floppy --fs-uuid --set=root 820b249f-2aff-44d6-8c77-9f66456b3527 fi echo 'Loading Linux 3.19.0-desktop-1.mga5 ...' linux /boot/vmlinuz-3.19.0-desktop-1.mga5 root=UUID=820b249f-2aff-44d6-8c77-9f66456b3527 ro splash quiet resume=UUID=414e6563-4bda-41f8-ab41-adf38b01216d echo 'Loading initial ramdisk ...' initrd /boot/initrd-3.19.0-desktop-1.mga5.img } } ### 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_ppc_terminfo ### ### END /etc/grub.d/20_ppc_terminfo ### ### BEGIN /etc/grub.d/30_os-prober ### menuentry 'openSUSE 13.2 (x86_64) (on /dev/sdb1)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-simple-8f35b046-a5dc-4d40-a665-7a9218e9af90' { insmod part_msdos insmod btrfs set root='hd1,msdos1' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1 8f35b046-a5dc-4d40-a665-7a9218e9af90 else search --no-floppy --fs-uuid --set=root 8f35b046-a5dc-4d40-a665-7a9218e9af90 fi linux /boot/vmlinuz-3.16.7-7-desktop root=UUID=8f35b046-a5dc-4d40-a665-7a9218e9af90 ${extra_cmdline} resume=/dev/disk/by-uuid/63c5ddde-122d-4046-956c-b3f0d0d88b0c splash=silent quiet showopts initrd /boot/initrd-3.16.7-7-desktop } submenu 'Advanced options for openSUSE 13.2 (x86_64) (on /dev/sdb1)' $menuentry_id_option 'osprober-gnulinux-advanced-8f35b046-a5dc-4d40-a665-7a9218e9af90' { menuentry 'openSUSE (on /dev/sdb1)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-3.16.7-7-desktop--8f35b046-a5dc-4d40-a665-7a9218e9af90' { insmod part_msdos insmod btrfs set root='hd1,msdos1' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1 8f35b046-a5dc-4d40-a665-7a9218e9af90 else search --no-floppy --fs-uuid --set=root 8f35b046-a5dc-4d40-a665-7a9218e9af90 fi linux /boot/vmlinuz-3.16.7-7-desktop root=UUID=8f35b046-a5dc-4d40-a665-7a9218e9af90 ${extra_cmdline} resume=/dev/disk/by-uuid/63c5ddde-122d-4046-956c-b3f0d0d88b0c splash=silent quiet showopts initrd /boot/initrd-3.16.7-7-desktop } menuentry 'openSUSE, with Linux 3.16.7-7-desktop (on /dev/sdb1)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-3.16.7-7-desktop--8f35b046-a5dc-4d40-a665-7a9218e9af90' { insmod part_msdos insmod btrfs set root='hd1,msdos1' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1 8f35b046-a5dc-4d40-a665-7a9218e9af90 else search --no-floppy --fs-uuid --set=root 8f35b046-a5dc-4d40-a665-7a9218e9af90 fi linux /boot/vmlinuz-3.16.7-7-desktop root=UUID=8f35b046-a5dc-4d40-a665-7a9218e9af90 ${extra_cmdline} resume=/dev/disk/by-uuid/63c5ddde-122d-4046-956c-b3f0d0d88b0c splash=silent quiet showopts initrd /boot/initrd-3.16.7-7-desktop } menuentry 'openSUSE, with Linux 3.16.7-7-desktop (recovery mode) (on /dev/sdb1)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-3.16.7-7-desktop--8f35b046-a5dc-4d40-a665-7a9218e9af90' { insmod part_msdos insmod btrfs set root='hd1,msdos1' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1 8f35b046-a5dc-4d40-a665-7a9218e9af90 else search --no-floppy --fs-uuid --set=root 8f35b046-a5dc-4d40-a665-7a9218e9af90 fi linux /boot/vmlinuz-3.16.7-7-desktop root=UUID=8f35b046-a5dc-4d40-a665-7a9218e9af90 ${extra_cmdline} showopts apm=off noresume edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 nomodeset x11failsafe initrd /boot/initrd-3.16.7-7-desktop } } ### 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 ${config_directory}/custom.cfg ]; then source ${config_directory}/custom.cfg elif [ -z "${config_directory}" -a -f $prefix/custom.cfg ]; then source $prefix/custom.cfg; fi ### END /etc/grub.d/41_custom ### ### BEGIN /etc/grub.d/90_persistent ### ### END /etc/grub.d/90_persistent ### ### BEGIN /etc/grub.d/93_memtest ### ### END /etc/grub.d/93_memtest ### [root@wolf ~]#
For this to have been helpful it should have been done without uninstalling the new kernel, as was requested. If you wish to help identify a possible bug here please do a system update. Re-boot and if it fails make a note of any error messages then re-boot into the next previous kernel and repeat the commands as in https://bugs.mageia.org/show_bug.cgi?id=15532#c1 Then *attach* (do not paste directly into the bug report) the complete terminal output. You can copy/paste into an attachment using the "Add an attachment" link above. Thanks
N.B. Please not not uninstall the new kernel as more information may be requested from your system to help diagnose the issue. Thanks.
Created attachment 6105 [details] Kernel panic 3.19.2.1
Created attachment 6106 [details] Kernel panic 3.19.2.1
I have attached details as requested after re-installing the offending kernel. Problem persists. Details attached consist of results of the commands i was given to run earlier. Thanks a lot for your assistance.
Attachment 6105 mime type: application/octet-stream => text/plain
Attachment 6106 mime type: application/octet-stream => text/plain
Attachment 6105 mime type: text/plain => application/octet-stream
(In reply to Jude Ashvin Lobo Shenoy from comment #7) Thanks Write this down: Please reboot and at the grub2 menu screen select the default top entry and hit "e" (just the letter e key) Cursor down to below the last line and type: initrd /boot/initrd.img now hit F10 If the system boots would you then please open a terminal and type: su (enter root password) grub2-mkconfig -o /home/$USER/grub_test.cfg exit Please note any error messages during this (there may be none). Attach the file grub_test.cfg (from your home folder) as plain text. None of the above will change your system in any way. Thanks
Summary: Kernel 3.19.2 causing kernel panic => grub2 top level menu entry missing initrd line with kernel 3.19.2 causing kernel panic
Forgot to ask - is this x86_64 like your suse installation, or 32 bit?
Priority: Normal => High
I did as asked and it booted perfectly. No issues. Seems like i cant upload the grub_test.cfg file as the server is down. I have 2 hdd on my pc & 1 500gb hdd has suse 13.2 64bit running flawlessly. The other hdd is 160gb running Mageia. Will try to upload the cfg file soon. Thanks a lot once again. Am going to rebbot the pc a couple of times and let you know if issues persist.
As I said - nothing has changed on your machine so nothing is fixed - yet. That was just a test. OK, if upload is a problem (Mageia servers have a problem) just pastebin it here: http://paste.kde.org/ and post the url here.
Yes nothing has changed..the problem persists. https://paste.kde.org/pndjjpntn
https://paste.kde.org/pjt6ybszt Sorry earlier url pasted by mistake. Here we have the output of grub_test.cfg as txt.
OK no problem - I think we now understand the issue. To fix your machine just boot into the latest kernel as you did before in https://bugs.mageia.org/show_bug.cgi?id=15532#c8 and in a terminal: update-grub (enter root password) You should now be back to normal. Thanks for your help.
@Thomas For the record. This is a case of drakx creating the initrd after the grub2 filetrigger has created the grub.cfg. I don't see how a race could happen (re.irc) as the initrd creation does not appear to start until the filetrigger has completed running grub2-mkconfig. I understood that tv had included a call to grub2-mkconfig after initrd creation, which would mean that grub2-mkconfig would be run twice, while the filetrigger was in place. Once by the filetrigger, then once by the tv magic (not sure where that is). That did not seem to much of an overhead at the time to ensure that in other cases where the filetrigger is needed (install/removal/update of grub2-theme* or os-prober).
CC: (none) => tmb
CC: (none) => eeeemail
Thanks for everything. i cab boot mageia without any issue but now i updated mageia cos of some drax updates then i notice i have no internet and now am locked out of my account. Can i get help? Using my suse now.
(In reply to Jude Ashvin Lobo Shenoy from comment #16) > Thanks for everything. i cab boot mageia without any issue but now i updated > mageia cos of some drax updates then i notice i have no internet and now am > locked out of my account. Can i get help? Using my suse now. Yes certainly, but please open another bug report for that issue.
@Thomas I appear to have been in some confusion when I closed this (possibly in error): https://bugs.mageia.org/show_bug.cgi?id=10024#c10 Please read from the above link - I will try to re-test it later, however the case here (this bug) seems to indicate that the bootloader *was* in the MBR which I think should have been detected with TV's current code. Note that even if (in pc-bios) the MBR does *not* have a grub2 bootloader installed, (and the grub2 package is installed) grub2-mkconfig must be run on kernel update, since the system may be booted from another system's grub legacy/grub2 on another disk using the core.img to launch the local grub2 menu. Can not the existence of /boot/grub2/grub.cfg be used to detect that grub2_mkconfig needs to be run after initrd creation? This should work equally for ps-bios and UEFI.
Depends on: (none) => 10024
As of now i feel this issue of the kernel panic has been resolved as i had no issues in the last 2 reinstallations of Mageia but now am getting locked out and this seems to be a new bug with the latest bunch of updates. Thanks for your assistance.
CC: (none) => thierry.vignaudBlocks: (none) => 416
Fixed with drax 16.80 & grub2-2.02-0.git9752.15.mga5
Status: NEW => RESOLVEDResolution: (none) => FIXED
Am experiencing kernel panic with the latest updates. Attached is a text file with the output of commands i executed last time when i reported this issue. Just updated my sys with the latest released updated which include kernel3.19.4.1
Status: RESOLVED => REOPENEDResolution: FIXED => (none)
Created attachment 6275 [details] Kernel panic with the latest updates.
Created attachment 6276 [details] Kernel panic 3.19.4.1
Attachment 6275 mime type: application/octet-stream => text/plain
Attachment 6276 mime type: application/octet-stream => text/plain
Ran the below command as the results are as follows: [root@wolf ~]# grub2-mkconfig -o /home/ashvin/grub_test.cfg Generating grub configuration file ... Found theme: /boot/grub2/themes/maggy/theme.txt Found linux image: /boot/vmlinuz-desktop Found linux image: /boot/vmlinuz-3.19.4-desktop-1.mga5 Found linux image: /boot/vmlinuz-3.19.3-desktop-1.mga5 Found initrd image: /boot/initrd-3.19.3-desktop-1.mga5.img Found linux image: /boot/vmlinuz-3.19.2-desktop-2.mga5 Found initrd image: /boot/initrd-3.19.2-desktop-2.mga5.img Found linux image: /boot/vmlinuz-3.19.2-desktop-1.mga5 Found initrd image: /boot/initrd-3.19.2-desktop-1.mga5.img Found linux image: /boot/vmlinuz-3.19.0-desktop-1.mga5 Found initrd image: /boot/initrd-3.19.0-desktop-1.mga5.img Found openSUSE 13.2 (x86_64) on /dev/sdb1 done [root@wolf ~]#
Created attachment 6277 [details] Kernel panic 3.19.4.1 on bootup.
Created attachment 6278 [details] Kernel panic 3.19.4.1 on bootup.
Created attachment 6279 [details] Kernel panic 3.19.4.1 on bootup.
Comment on attachment 6279 [details] Kernel panic 3.19.4.1 on bootup. I am on kernel 3.19.3 now and all is well but if i bootup i get the kernel panic screen.
I see that the initrd.img symlink is wrong in /boot, however this is not used by the top level grub2 entry, so there may be two issues here. Just leave things as they are for now and use 3.19.3 until others have chance to look at this, as more info may be needed from your system.
Can you attach the draklog.txt file resulting from running the following command: journalctl SYSLOG_FACILITY=17 Also I suspect your kernel was updated before latest grub2. Thomas, kernel could conflicts with older grub2, like we already do for dracut & the like
(In reply to Thierry Vignaud from comment #30) > Also I suspect your kernel was updated before latest grub2. > Thomas, kernel could conflicts with older grub2, like we already do for > dracut & the like Done in SVN for next kernel build
Please conflict with old grub2-efi too (if not already done).
Created attachment 6282 [details] Draklog.txt as requested This file contains the output of cat journalctl SYSLOG_FACILITY=17
Created attachment 6283 [details] Basic system info from webmin. Details of my system as shown by the webmin splash screen.
humm, bootloader-config isn't logged as explanations. What about "journalctl |grep RPM>rpm.log"
The above command returns an empty .txt file. journalctl |grep RPM returns nothing :(
Created attachment 6288 [details] Grub2 on bootup.
Created attachment 6289 [details] Next step if i go to edit the bootup with CLI. This is as per comment 8 from my earlier posting of the issue. Followed the same steps.
Created attachment 6290 [details] Then i get this white sliding line at the bottom of the screen. After i edit the bootup in CLI and add initrd /boot/initrd.img, i get this.
Created attachment 6291 [details] Then i get the drakcut prompt.
(In reply to Jude Ashvin Lobo Shenoy from comment #36) > The above command returns an empty .txt file. journalctl |grep RPM returns > nothing :( and you did run it as root?
CC: (none) => marja11
In the original (re-opened) report grub.cfg was using initrd-desktop.img, https://bugs.mageia.org/attachment.cgi?id=6276 now it is using initrd.img https://bugs.mageia.org/attachment.cgi?id=6289 Why I wonder? What is output of: ll /boot/*.img
Depends on: (none) => 15710
Depends on: 15710 => (none)
(In reply to Jude Ashvin Lobo Shenoy from comment #2) Please never paste such big files. Attach them. It make bug reports unreadable. (In reply to Barry Jackson from comment #42) initrd.img link corresponds to vmlinuz link initrd-desktop.img link corresponds to vmlinuz-desktop link @Thomas, Anne: could we upload a new kernel with the new conflicts & redo the images? It would save us quite some bug reports...
(In reply to Thierry Vignaud from comment #43) > (In reply to Barry Jackson from comment #42) > initrd.img link corresponds to vmlinuz link > initrd-desktop.img link corresponds to vmlinuz-desktop link > OK that I understand, what I don't understand is why there are two and why they are updated differently?
Hi Guys, Seems like i did a bit to add to the confusion. If you see comment 8 and as suggested by Barry i did try to do the same thing again (initrd /boot/initrd.img) and that takes me to a screen where the slider at the bottom moves and then takes me to the drakcut login screen. Results of the ll /boot/*.img command are as follows: [ashvin@wolf ~]$ su - Password: [root@wolf ~]# ll /boot/*.img -rw------- 1 root root 9228783 Mar 21 19:53 /boot/initrd-3.19.0-desktop-1.mga5.img -rw------- 1 root root 9195085 Mar 21 23:00 /boot/initrd-3.19.2-desktop-1.mga5.img -rw------- 1 root root 9194422 Mar 26 06:33 /boot/initrd-3.19.2-desktop-2.mga5.img -rw------- 1 root root 9224681 Apr 5 21:52 /boot/initrd-3.19.3-desktop-1.mga5.img lrwxrwxrwx 1 root root 32 Apr 15 21:32 /boot/initrd-desktop.img -> initrd-3.19.4-desktop-1.mga5.img lrwxrwxrwx 1 root root 32 Apr 5 21:52 /boot/initrd.img -> initrd-3.19.3-desktop-1.mga5.img [root@wolf ~]# contents of the rpm.log file after running journalctl |grep RPM>rpm.log : /var/log/rpmpkgs { weekly notifempty missingok }
Created attachment 6294 [details] rpm.log after running journalctl |grep RPM>rpm.log
This should probably be release blocker so it isn't forgotten for final.
Priority: High => release_blocker
Keywords: NEEDINFO => (none)
Installed the latest updates in the morning along with kernel 3.19.4 but i still have the same kernel panic (pic attached). Will be uploading the diagnostic report in a few minutes
Created attachment 6330 [details] Same problem from latest updates to kernel 3.19.4
Created attachment 6331 [details] Journalctl log with more details.
Created attachment 6332 [details] Dmesg output
Created attachment 6333 [details] dmidecode output
Created attachment 6334 [details] output of journalctl |grep RPM>rpm.log
I did update-grub2 after installing the latest round of updates that included kernel 3.19.4.2 and still i get the kernel panic screen on bootup so then i have to revert to 3.19.3 for normal ops :(
Hi Jude, Thanks for your continued testing :) Could you confirm that you still experience the same issue with the latest kernel (3.19.7)?
Hi Remi, Thanks for all assistance. Till kernel 3.19.6 i had no issues and am not sure bout 3.19.7 as i have not connected my mageia to any network as am heading to a small village for work and will be residing there. I have purchased a usb cdma postpaid mobile broadband dongle to use there. I am really disappointed with mageia as of now cos its my favorite distro but it does not detect my dongle and it asks me for a sim card whereas this dongle does not come with a sim so cos of this am in a fix :(( this is just for your info so must see if i can get a landline network over there. Will be working in a school of international repute so i feel they may have wifi. That too will be enough for me. Will be in touch with you guys and will report any issues.
(In reply to Jude Ashvin Lobo Shenoy from comment #56) > I am > really disappointed with mageia as of now cos its my favorite distro but it > does not detect my dongle and it asks me for a sim card whereas this dongle > does not come with a sim so cos of this am in a fix :(( I know you're a faithful bug reporter, (thanks for that!), but I don't manage to find your bug report about the issue with the dongle. Do you mind giving the link to it?
Hi Marja, Yes will be filing a bug report for the dongle issue right away....:D
Kernel 3.19.6 had no issues and all was well with me.
(In reply to Jude Ashvin Lobo Shenoy from comment #59) > Kernel 3.19.6 had no issues and all was well with me. Thanks for the feedback That's the one on the first round QA 5 final isos :-) Closing
Status: REOPENED => RESOLVEDResolution: (none) => FIXED