Bug 10671 - kernel panic at boot (32bits only)
Summary: kernel panic at boot (32bits only)
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal critical
Target Milestone: ---
Assignee: Thomas Backlund
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2013-07-01 13:46 CEST by Adrien D
Modified: 2015-05-17 21:17 CEST (History)
1 user (show)

See Also:
Source RPM: kernel-3.9.8
CVE:
Status comment:

Attachments
Nothing ... (20.33 KB, image/png)
2013-07-01 22:57 CEST, Adrien D 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Adrien D 2013-07-01 13:46:40 CEST 
Description of problem:

Hi team mageia,

The 32bits kernel installed on my laptop have some problems.
Before the KDE desktop appears, I have a kernel panic.

Which files can I attach to help. you ?
I have this problem since kernel 3.9.4.

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

kernel 3.9.8

How reproducible:


Steps to Reproduce:
1. Install the 32biys kernel
2.
3. reboot and 2 of the 3. LEDs of keyboard blink and you reade "kernel panic" on scren.
 

Reproducible: 

Steps to Reproduce:
Adrien D 2013-07-01 13:46:51 CEST

CC: (none) => adrien_d

Adrien D 2013-07-01 13:48:34 CEST

Assignee: bugsquad => tmb

Adrien D 2013-07-01 13:49:03 CEST

Severity: normal => critical

Comment 1 Thomas Backlund 2013-07-01 20:48:40 CEST 
Can you take a picture of the kernel panic.

if you dont get any info on the screen, remove "splash silent" from the kernel command line and try then
Comment 2 Adrien D 2013-07-01 22:57:14 CEST 
Created attachment 4182 [details]
Nothing ...
Comment 3 Samuel Verschelde 2015-05-17 21:17:01 CEST 
Closing as OLD, please reopen if still valid in Mageia 4 and/or 5.

Keywords: (none) => NEEDINFO

Comment 4 Samuel Verschelde 2015-05-17 21:17:35 CEST 
Closing as OLD, I said, thus I really close it now :).

Status: NEW => RESOLVED
Resolution: (none) => OLD
Note You need to log in before you can comment on or make changes to this bug.