Bug 230745 - new install stalling at "installing kernel-2.6.20-1.2949.fc7.x86_64"
new install stalling at "installing kernel-2.6.20-1.2949.fc7.x86_64"
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
rawhide
All Linux
medium Severity medium
: ---
: ---
Assigned To: Anaconda Maintenance Team
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-03-02 12:09 EST by eric magaoay
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-03-02 12:38:18 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
syslog (19.59 KB, application/octet-stream)
2007-03-02 12:09 EST, eric magaoay
no flags Details
anaconda log (181.81 KB, application/octet-stream)
2007-03-02 12:10 EST, eric magaoay
no flags Details
vncserver log (1.20 KB, application/octet-stream)
2007-03-02 12:11 EST, eric magaoay
no flags Details

  None (edit)
Description eric magaoay 2007-03-02 12:09:51 EST
Description of problem:
During fresh vnc install, the process stall at 
"Installing kernel-2.6.20-1.2949.fc7.x86_64"

Version-Release number of selected component (if applicable):
anaconda-11.2.0.27-1.x86_64

How reproducible:
persistent

Steps to Reproduce:
1. start fresh vnc install
2. select default packages
  
Actual results:
the process stop at installing kernel module/package

Expected results:
should process without stalling

Additional info:
attached files: syslog, anaconda.log, vncserver.log
Comment 1 eric magaoay 2007-03-02 12:09:51 EST
Created attachment 149133 [details]
syslog
Comment 2 eric magaoay 2007-03-02 12:10:59 EST
Created attachment 149134 [details]
anaconda log
Comment 3 eric magaoay 2007-03-02 12:11:29 EST
Created attachment 149135 [details]
vncserver log
Comment 4 eric magaoay 2007-03-02 12:38:18 EST
The latest development build (dated 3.2.07) seem to fix the problem. 

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