Bug 1316015 - the newly installed f24 system halted: Failed to allocate space for phdrs
Summary: the newly installed f24 system halted: Failed to allocate space for phdrs
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 24
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-09 09:23 UTC by lnie
Modified: 2016-07-01 19:30 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-01 19:30:59 UTC
Type: Bug

Attachments (Terms of Use)
screenshot (21.30 KB, image/png)
2016-03-09 09:23 UTC, lnie 		no flags Details
screeshot2 (299.95 KB, image/png)
2016-03-10 06:33 UTC, lnie 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description lnie 2016-03-09 09:23:28 UTC 
Created attachment 1134424 [details]
screenshot

Description of problem:


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

How reproducible:
always

Steps to Reproduce:
1.do a default install with f24-workstation.boot on my vm
2.reboot the newly installed system 
3.

Actual results:


Expected results:


Additional info:
Comment 1 Christophe Fergeau 2016-03-09 17:43:12 UTC 
This looks like what is discussed in https://bugzilla.redhat.com/show_bug.cgi?id=1302071#c68 as well.
Comment 2 lnie 2016-03-10 06:31:26 UTC 
yeah, look alike, however,I produced this with 64-bit boot.iso and the kernel edition is 4.5.0-0.rc7.git0.2.fc24.i686+PAE.
FYI:After a default install with 64-bit workstation live ,I'm able to login the system using kernel 4.5.0-0.rc7.git0.2.fc24.x86_64,but it seems that there is still a problem,and I can't get a usable network connection.
Comment 3 lnie 2016-03-10 06:33:32 UTC 
Created attachment 1134699 [details]
screeshot2
Comment 4 Tomasz Torcz 2016-07-01 19:16:42 UTC 
I think this was resolved and can be closed.
Note You need to log in before you can comment on or make changes to this bug.