[Bug 59750] New: [GM45 regression] system hang while booting up
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Wed Jan 23 01:06:39 PST 2013
https://bugs.freedesktop.org/show_bug.cgi?id=59750
Priority: medium
Bug ID: 59750
Assignee: intel-gfx-bugs at lists.freedesktop.org
Summary: [GM45 regression] system hang while booting up
QA Contact: intel-gfx-bugs at lists.freedesktop.org
Severity: critical
Classification: Unclassified
OS: All
Reporter: cancan.feng at intel.com
Hardware: Other
Status: NEW
Version: unspecified
Component: DRM/Intel
Product: DRI
branch name: drm-kms-locking
Description:
----------------------------------------
We tested nightly, found machine hang while booting after grub.Then the screen
turned into black. I can't login by ssh. We found this issue caused by "branch
drm-kms-locking". The commit I listed below is first bad.
Bisect result:
------------------------------------------
commit 7b24056be6db7ce907baffdd4cf142ab774ea60c
Author: Daniel Vetter <daniel.vetter at ffwll.ch>
Date: Wed Dec 12 00:35:33 2012 +0100
drm: don't hold crtc mutexes for connector ->detect callbacks
The coup de grace of the entire journey. No more dropped frames every
10s on my testbox!
I've tried to audit all ->detect and ->get_modes callbacks, but things
became a bit fuzzy after trying to piece together the umpteenth
implemenation. Afaict most drivers just have bog-standard output
register frobbing with a notch of i2c edid reading, nothing which
could potentially race with the newly concurrent pageflip/set_cursor
code. The big exception is load-detection code which requires a
running pipe, but radeon/nouveau seem to to this without touching any
state which can be observed from page_flip (e.g. disabled crtcs
temporarily getting enabled and so a pageflip succeeding).
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20130123/441805e2/attachment-0001.html>
More information about the intel-gfx-bugs
mailing list