Bug 3813

Summary: kernel panic for kernel 3.1.6
Product: Mageia Reporter: Franklin Weng <franklin>
Component: RPM PackagesAssignee: Thomas Backlund <tmb>
Status: RESOLVED FIXED QA Contact:
Severity: critical    
Priority: Normal Keywords: Triaged
Version: Cauldron   
Target Milestone: ---   
Hardware: i586   
OS: Linux   
Whiteboard:
Source RPM: kernel-desktop-3.1.6-0.rc1.1.mga2-1-1.mga2 CVE:
Status comment:
Attachments: Screenshot for kernel panic messages

Description Franklin Weng 2011-12-19 06:01:57 CET 
Description of problem:
After upgrading to cauldron latest kernel 3.1.6, kernel panicked at boot time.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. upgrade to latest (2011/12/19) cauldron packages
2. Boot up the machine
3.
Comment 1 Franklin Weng 2011-12-19 06:02:33 CET 
Created attachment 1271 [details]
Screenshot for kernel panic messages

Screenshot for kernel panic messages
Comment 2 Franklin Weng 2011-12-19 06:17:06 CET 
Booting with old 3.1.4 kernel is okay.

I updated the RPM package field.

Source RPM: kernel-3.1.6 => kernel-desktop-3.1.6-0.rc1.1.mga2-1-1.mga2

Comment 3 Manuel Hiebel 2011-12-19 11:01:04 CET 
Hi, thanks for reporting this bug.

I see no big change: http://svnweb.mageia.org/packages/cauldron/kernel/current/SPECS/kernel.spec?r1=174077&r2=184074

Assigned to the package maintainer.
(Please set the status to 'assigned' if you are working on it)

Keywords: (none) => Triaged
Assignee: bugsquad => tmb

Comment 4 Thomas Backlund 2011-12-19 11:50:11 CET 
You got caught by a broken dracut/bootsplash/plymouth interaction.

Make sure you got the fixed packages installed:

bootsplash-3.3.6-1.mga2
dracut-014-7.mga2
*plymouth*0.8.4-0.20111214.3.mga2

then recreate the broken initrd with:

dracut -f /boot/initrd-3.1.6-desktop-0.rc1.1.mga2.img 3.1.6-desktop-0.rc1.1.mga2

and try to boot with the new kernel again
Comment 5 Franklin Weng 2011-12-20 01:29:18 CET 
After rebuilding initrd, it works.

Thanks.
Comment 6 Thomas Backlund 2011-12-20 01:42:23 CET 
Good to know, closing then.

Status: NEW => RESOLVED
Resolution: (none) => FIXED