Bug 712627 - System hang frequently
Summary: System hang frequently
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 15
Hardware: x86_64
OS: Windows
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-06-11 21:32 UTC by chi
Modified: 2011-11-18 03:22 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-09-27 16:01:14 UTC
Type: ---


Attachments (Terms of Use)

Description chi 2011-06-11 21:32:02 UTC
Description of problem:

Intent to upgrade from Fedora 14 which had been running very reliably before upgrade. Various attempt to upgrade failed at different stages of progression. See below for more details. Summary of settings:
- On Windows 7 64-bit host operating system
- Sony VPCEB27FG Intel i3 8GB RAM notebook computer
- Virtualbox 4.0.8 Fedora Linux virtual machine 4GB RAM

Version-Release number of selected component (if applicable):
- Fedora 15 Gnome x86-64 has this problem rendering unusable
- Fedora 15 Gnome x86 has this problem rendering unusable
- Fedora 15 KDE x86-64 has this problem rendering unusable
- Other versions not tried

How reproducible:
- Preupgrade hung
- Install from ISO image
    - DVD finished install but not reliable - hanging / freezing
    - LiveCD finished install but not reliable - hanging / freezing
After many times of repeated attempts F14 is reinstalled instead. 

Steps to Reproduce:
1. Have Sony VPCEB27FG 8GB RAM + Windows 7 64-bit + Virtualbox
2. Download iso and install Fedora 15
3. Use Fedora 15, eventually end up with hanging / freezing
  
Actual results:
Freezing, leaving overnight does not clear the freezing. The condition seemed to start off less severe, for example, one window becomes inoperative. Leave the (virtual) machine to run since the condition arised progressed to eventually all operations including shutting down from the GUI being unaccessible. Consulted Fedora help pages, consulted Bugzilla, did not find solution therefore filing this bug report. 

Expected results:
With Fedora 14 such reliability doubt is never observed. 

Additional info:
Gnome reported fall back. In at least one of the attempts, Gnome 3 loaded the new imporved visual frontend. However, this, too, hang eventually. The hanginng / freezing sometimes are experienced during yum update. Sometimes, I can progress far into installing the Virtualbox Linux Additions or even pass that. All attempts of installation afresh ends up having the machine not reliable - hanging / freezing during operation.

Comment 1 chi 2011-06-19 09:47:54 UTC
Summary: 
Virtualbox runs Fedora 15 x86_64 freezing
Host Windows 7-64

Further information:
Freezing not observed - when Virtualbox setting is single CPU (perhaps Enable IO APIC unchecked has a positive contributing effect)
Freezing observed - most easily is when updating packages and adding packages, but also happen after the system has been used. When frozen, harddisk will be very busy until the system is manually RESET. Also noticed host RAM usage increased so the reporter will use "memory leak" loosely to describe it.

Comment 2 chi 2011-06-29 12:47:41 UTC
After the most recent software update, the system cannot start Gnome desktop (following loggin in screen)
Virtualbox updated to Version 4.0.10
Fedora 15 re-installed then a software update performed. 
Everything runs much more reliably.

Comment 3 Josh Boyer 2011-09-27 16:01:14 UTC
We can't really fix VirtualBox issues.  Thank you for reporting the bug though, as it will at least get archived for others hitting the issue.

Comment 4 Arun Vasudevan 2011-11-18 03:22:52 UTC
I don't think this is a Virtual Box issue. My Fedora 15 64-bit hangs now a days. It started two days back. I am using KDE, fully updated with yum. Direct full installation from the live cd. I have Windows 7 Professional in another partition, working without any issues.


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