Bug 467862 - Plymouthd freezes on firstboot with 4G memory
Plymouthd freezes on firstboot with 4G memory
Product: Fedora
Classification: Fedora
Component: plymouth (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Ray Strode [halfline]
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2008-10-21 08:11 EDT by John J. McDonough
Modified: 2008-10-21 09:37 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-10-21 09:37:30 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description John J. McDonough 2008-10-21 08:11:45 EDT
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?
Actual results:
black screen

Expected results:

Additional info:
Comment 1 Ray Strode [halfline] 2008-10-21 09:37:30 EDT
This got fixed post-beta.

Note You need to log in before you can comment on or make changes to this bug.