Bug 698515

Summary: Lockup on Acer Aspire AO522
Product: [Fedora] Fedora Reporter: Darryl Bond <darryl.bond>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 15CC: gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-04-22 05:29:23 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Darryl Bond 2011-04-21 05:31:47 UTC 
Description of problem:Boot fails Acer Aspire AO522 on Fedora15 Beta.
Aspire is new model netbook based on the C50 AMD dual core 1 GHz and HD 6250 APU.

Version-Release number of selected component (if applicable): 2.6.38.2-9.fc15.i686


How reproducible: Every time


Steps to Reproduce:
1. Boot from USB key
2. 
3.
  
Actual results: Machine will boot but never reaches GDM. X Server starts then locks up.

If it is booted to single user without rhgb and quiet it gets to a prompt. After a few seconds a stream of messages on the console
ACPI Error: No Handler or method for GPExx, disabling event (20112/evgpe753)
the GPE number seems to be incrementing.
The screen displays a these messages very quickly, they are scrolling as fast as the screen can scroll. Once the messages start, it is impossible to use the console.

This occurs in run level 3 as well


Expected results:
Normal boot

Additional info:
Tried acpi=no but this did not help. The machine displays lots of kernel ACPI notices as it boots so this doesn't seem to do anything.

The bios was upgraded to the latest version.
Comment 1 Darryl Bond 2011-04-21 23:53:40 UTC 
I just booted the Fedora-15-Beta-x86_64-Live-Desktop which did not display the error. Note that the original bug occurred with the i686 version.

The desktop comes up successfully and it looks good so far.
Comment 2 Chuck Ebbert 2011-04-22 05:29:23 UTC 

*** This bug has been marked as a duplicate of bug 694361 ***