Bug 541593

Summary: Freezes with KMS enabled with an Intel GM4500HD
Product: [Fedora] Fedora Reporter: Agustin Barto <abarto>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: awilliam, dougsland, gansalmon, itamar, kernel-maint
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-11-26 16:33:30 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 Flags
kerneloops log during a freeze none

Description Agustin Barto 2009-11-26 12:38:47 UTC
Description of problem:

Whenever I try to boot without the "nomodeset" kernel argument (which is the default) the system freezes while starting X.org (the fedora logo on plymouth is full). If I use KDM I can even login but when I enable compositing (aka desktop effects) X crashes and the system freezes. The system also freezes if I try to enable compositing on Gnome or KDE with the nomosetset argument.

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

This happened with all kernel versions up to kernel-, with all the updates from updates-testing installed.

How reproducible:


Steps to Reproduce:
1. Boot without "nomodeset" as a kernel parameter.
Actual results:

The system freezes and a hard reset is required.

Expected results:

The system doesn't freeze and I get to appear on the cover of Rolling Stone alongside Silvio Berlusconi.

Additional info:

Comment 1 Agustin Barto 2009-11-26 12:56:19 UTC
Created attachment 373993 [details]
kerneloops log during a freeze

Comment 2 Adam Williamson 2009-11-26 16:33:30 UTC
Thanks for the report - looks like a dupe :)

Fedora Bugzappers volunteer triage team

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