Bug 6456

Summary:	dracut crashes system !
Product:	Mageia	Reporter:	Paul Thompson <paul.d.thompson.jr>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED OLD	QA Contact:
Severity:	major
Priority:	High	CC:	marja11, paul.d.thompson.jr
Version:	2	Keywords:	NEEDINFO
Target Milestone:	Mageia 2
Hardware:	i586
OS:	Linux
Whiteboard:
Source RPM:	dracut-017-16.mga2	CVE:
Status comment:

Description Paul Thompson 2012-06-14 03:36:28 CEST

Theme name: oxygen-gtk
Kernel version = 3.3.6-server-2.mga2
Distribution=Mageia release 2 (Official) for i586
CPU=Intel(R) Pentium(R)  CPU       E5200  @ 2.50GHz
-----------
I downloaded the 22 May release of Mageia 2 32 bit and after installation and reboot, it crashed my system in both regular and safe mode ?! It would not even give me a prompt I although I could do a warm boot (ALT+CTRL+DEL). I did a second installation of it and will reboot after I submit this.
I did notice that dracut IS NOT LISTED AS an Official Mageia 2 package !? 
FYI: There WAS not report ( recreation ) of this ... that is unless it does it again when I reboot this time ...

Paul Thompson 2012-06-14 03:37:42 CEST

Priority: Normal => release_blocker
CC: (none) => paul.d.thompson.jr
Target Milestone: --- => Mageia 2
Severity: normal => major

Comment 1 Manuel Hiebel 2012-06-22 13:40:03 CEST

Why do you think it's a dracut issue ?

What is your video card ?

>I did notice that dracut IS NOT LISTED AS an Official Mageia 2 package !? 
What ?

Keywords: (none) => NEEDINFO
Priority: release_blocker => High
CC: sysadmin-bugs => (none)
Component: Release (media or process) => RPM Packages

Comment 2 Marja Van Waes 2012-08-03 20:16:52 CEST

Reporter, could you please reply to the previous question? If you won't reply within two weeks from now, I will have to close this bug as OLD. Thank you.

CC: (none) => marja11

Comment 3 Marja Van Waes 2012-08-26 15:28:03 CEST

Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution.

Users who have experienced this problem are encouraged to update their system, and if this issue then still turns out to be reproducible, please reopen this bug with additional information.

Closing as OLD.

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