Bug 15580 - PATCH: intel drm: fix reproducable kernel panic
Summary: PATCH: intel drm: fix reproducable kernel panic
Status: RESOLVED WORKSFORME
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/other (show other bugs)
Version: XOrg git
Hardware: Other All
: medium normal
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-04-18 06:24 UTC by Hans de Goede
Modified: 2010-12-02 20:03 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments
PATCH: intel drm: fix reproducable kernel panic (2.37 KB, patch)
2008-04-18 06:24 UTC, Hans de Goede 		no flags Details | Splinter Review
View All

Description Hans de Goede 2008-04-18 06:24:06 UTC 
Created attachment 16008 [details] [review]
PATCH: intel drm: fix reproducable kernel panic

Hi,

Short intro: I'm a Linux enthusiast / developer. Lately I'm mainly active 
writing kernel drivers and as a developer for Fedora.

I don't know what the proper place is to send bugs for intel drm issues, and 
you are a recent committer to the i915 drm driver, so hence this mail.

During the testing of Fedora 9, I've noticed that any OpenGL use hard freezes 
my machine with a kernel panic (blinking keyboard leds).

Today I've attached a serial console to capture the panic output. This has lead 
to me finding out that the panics are caused by a setting in my drirc, namely:
"Always synchronize with vertical refresh"

Further investigation has let to me localizing and fixing the bug, patch attached.

Regards,

Hans
Comment 1 Michel Dänzer 2008-04-18 07:46:28 UTC 
Looks Fedora / modesetting-101 specific.
Comment 2 Hans de Goede 2008-04-18 07:48:30 UTC 
(In reply to comment #1)
> Looks Fedora / modesetting-101 specific.
> 

It might very well be, I was planning on adding a note that this was for the modesetting branch, but I forgot.
Comment 3 Matt Turner 2010-12-02 20:03:19 UTC 
Closing due to inactivity. Reopen if this is still a bug.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.