Description of problem: Kernel panic at start-up, noticied something not synchronised. See photo of screen at http://obswww.unige.ch/~behrend/tempo/kernelpanic/CIMG3018.JPG . Version-Release number of selected component (if applicable): 3.10.24-2 just How reproducible: On computer HP Compaq 6710b - Linux localhost.localdomain 3.8.13.4-desktop-1.mga3 #1 SMP Thu Jul 4 14:04:55 UTC 2013 i686 i686 i686 GNU/Linux . - with kernel 3.10.24-2.mga3, just try to start the computer. Kernel-panic happens when booting with every "linux", "linux-fb" and "kernel-3.10.24-2". - never happens with 3.8.13.4-desktop-1.mga3. On an Acer Inspire one: both kernels do work fine. Steps to Reproduce: 1. 2. 3. Reproducible: Steps to Reproduce:
Priority: Normal => release_blockerSeverity: normal => critical
Can't reproduce this (I updated 3 very different Mageia 3 systems with that kernel). I don't know what causes it, only that it seems to at random hit one or another user after a kernel update. (See also bug 3360) Setting a bug to release blocker is only done for very serious and reproduced cauldron bugs that cannot be fixed after the next stable version of Mageia is released. Can you try to re-generate your initrd for this kernel and save the output, in case there is something odd in it? as root: cd /boot mv initrd-3.10.24-desktop-2.mga3.img initrd-old.img /sbin/installkernel -N 3.10.24-desktop-2.mga3 2>&1 | tee create_initrd.txt If after recreating it you still have the same problem, then please attach create_initrd.txt
Keywords: (none) => NEEDINFOPriority: release_blocker => NormalCC: (none) => marja11, tmbSummary: Kernel panic at start-up => kernel panic - not syncing: attempted to kill initSeverity: critical => normal
Hello Marja, I removed kernel 3.10.24-2, rebooted on 3.8.13.4 : the old kernel works fine. Then I reinstalled kernel 3.10.24-2 and rebooted on it. Every time, I got the same kernel panic as pictured. I then done what you suggested (omitting -N ), with results below: I: dracut module 'network' will not be installed, because it's in the list to be omitted! I: dracut module 'network' will not be installed, because it's in the list to be omitted! I: *** Including module: dash *** I: *** Including module: i18n *** I: *** Including module: drm *** I: *** Including module: plymouth *** I: *** Including module: kernel-modules *** I: *** Including module: resume *** I: *** Including module: rootfs-block *** I: *** Including module: terminfo *** I: *** Including module: udev-rules *** I: *** Including module: usrmount *** I: *** Including module: base *** I: *** Including module: fs-lib *** I: *** Including module: shutdown *** I: *** Including modules done *** I: *** Installing kernel module dependencies and firmware *** I: *** Installing kernel module dependencies and firmware done *** I: *** Resolving executable dependencies *** I: *** Resolving executable dependencies done*** I: *** Stripping files *** I: *** Stripping files done *** I: *** Creating image file *** I: *** Creating image file done *** I: Wrote /boot/initrd-3.10.24-desktop-2.mga3.img: I: -rw------- 1 root root 8889955 déc. 19 21:47 /boot/initrd-3.10.24-desktop-2.mga3.img defaulting background resolution to 1024x768 Added windows * Added linux-nonfb Added failsafe Added desktop_3.8.13.4-1.mga3 Added linux Added desktop_3.10.24-2.mga3 One warning was suppressed. Result: the same kernel panic. Nevertheless, I can work booting on 3.8.13 while 3.10.24 present on the choice-list. I'm sorry, but I don't know how to capture all the messages which are displayed during the statrt-up. Kindest regards, Raoul
Just tried the kernel 3.10.24-desktop586-2.mga3 with the same kernel panic...
Assignee: bugsquad => tmbSource RPM: (none) => kernel
is this still current?
CC: (none) => nic
Mageia 3 changed to end-of-life (EOL) status 4 months ago. http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ Mageia 3 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- The Mageia Bugsquad
Status: NEW => RESOLVEDResolution: (none) => OLD