Bug 752947 - forced to use [ acpi=no ] to have a usable system
Summary: forced to use [ acpi=no ] to have a usable system
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 16
Hardware: x86_64
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-10 20:13 UTC by Chris
Modified: 2012-05-14 17:07 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-05-14 17:07:14 UTC
Type: ---

Attachments (Terms of Use)
output of dmesg (62.23 KB, text/plain)
2011-11-10 20:13 UTC, Chris 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Chris 2011-11-10 20:13:14 UTC 
Created attachment 532914 [details]
output of dmesg

Description of problem:
with out using the switch [ acpi= no ] my laptop is unusable. 

Version-Release number of selected component (if applicable):
kernel version  3.1.0-7.fc16.x86_64

How reproducible:


Steps to Reproduce:
1. Install the current kernel
2. watch system performance drop
3.
  
Actual results:
A system that is unusable 

Expected results:


Additional info:
this was found on a ASUS laptop model N51V
Comment 1 Josh Boyer 2012-02-29 19:27:25 UTC 
Seems you're using the nvidia module.  What happens if you don't use that?

Also, what exactly was the problem without the acpi=no switch and do you see it on the 3.2.7 or newer kernels?
Comment 2 Dave Jones 2012-03-22 16:46:09 UTC 
[mass update]
kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository.
Please retest with this update.
Comment 3 Dave Jones 2012-03-22 16:50:43 UTC 
[mass update]
kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository.
Please retest with this update.
Comment 4 Dave Jones 2012-03-22 17:00:44 UTC 
[mass update]
kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository.
Please retest with this update.
Note You need to log in before you can comment on or make changes to this bug.