Bug 467862

Summary:	Plymouthd freezes on firstboot with 4G memory
Product:	[Fedora] Fedora	Reporter:	John J. McDonough <wb8rcr>
Component:	plymouth	Assignee:	Ray Strode [halfline] <rstrode>
Status:	CLOSED RAWHIDE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	rawhide	CC:	krh, rstrode
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-10-21 13:37:30 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description John J. McDonough 2008-10-21 12:11:45 UTC

Description of problem:

Intel E4500 - Intel G31 graphics - 4G memory

First boot console becomes unresponsive.  Logging in from another system reveals plymouthd CPU bound.

Cutting memory back to 2G allows F10 to start

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

Fedora 10 beta i386 

How reproducible:

Only tried once, presume it will happen again

Steps to Reproduce:
1. 4G physical memory
2. Intel G31 involved?
3.
  
Actual results:
black screen

Expected results:
gdmgreeter

Additional info:

Comment 1 Ray Strode [halfline] 2008-10-21 13:37:30 UTC

This got fixed post-beta.