Bug 752315 - System hangs on boot after upgrade of fc15 to fc16
Summary: System hangs on boot after upgrade of fc15 to fc16
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 16
Hardware: i386
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-09 07:05 UTC by Steve
Modified: 2011-11-10 08:08 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-11-09 18:15:04 UTC
Type: ---

Attachments (Terms of Use)
screen shot of system (52.76 KB, image/png)
2011-11-09 07:08 UTC, Steve 		no flags Details
screen shot of system after mods (53.51 KB, image/png)
2011-11-10 06:23 UTC, Steve 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Steve 2011-11-09 07:05:39 UTC 
Description of problem:
System hangs on boot after upgrade

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

How reproducible:
every time

Steps to Reproduce:
1. boot after upgrade
  
Actual results:
system stops mid boot process

Expected results:
system should boot

Additional info:
the system is a virtual box client on a Fedora-15
Comment 1 Steve 2011-11-09 07:08:18 UTC 
Created attachment 532469 [details]
screen shot of system

screen shot of system

rhgb and quiet flags removed from kernel boot parameters
Comment 2 Josh Boyer 2011-11-09 18:15:04 UTC 
You probably need to rebuild something from virtualbox.  Fedora doesn't support virtualbox, so you might want to contact them about what should be done in this case.
Comment 3 Steve 2011-11-10 06:23:42 UTC 
Created attachment 532730 [details]
screen shot of system after mods

system boots into rescue mode
yum remove dkms
removed vbox client via supplier procedure
still hangs as in screen shot
Comment 4 Frank Mehnert 2011-11-10 08:08:35 UTC 
Steve, which version of VirtualBox are you using? Could you also attach a VBox.log file of that hanging VM session?
Note You need to log in before you can comment on or make changes to this bug.