Summary: | [G45] I-G-T/kms_flip subtest: 'wf_vblank-ts-check' fail | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | DRI | Reporter: | yanbing <bingx.a.yan> | ||||||
Component: | DRM/Intel | Assignee: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||||
Status: | CLOSED FIXED | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||||
Severity: | normal | ||||||||
Priority: | medium | CC: | bingx.a.yan, yangweix.shui | ||||||
Version: | XOrg git | ||||||||
Hardware: | Other | ||||||||
OS: | All | ||||||||
Whiteboard: | |||||||||
i915 platform: | i915 features: | ||||||||
Attachments: |
|
Description
yanbing
2013-01-14 07:30:06 UTC
Created attachment 72991 [details]
kms_flip-subtest_wf_vblank-ts-check.dmesg
Created attachment 72992 [details]
lspci.log
Please retest all kms_flip failures with latest -nightly, specifically: commit 735dc0d1e29329ff34ec97f66e130cce481c9607 Merge: bac4b7c 20c60c3 Author: Dave Airlie <airlied@redhat.com> Date: Mon Jan 21 07:44:58 2013 +1000 Merge branch 'drm-kms-locking' of git://people.freedesktop.org/~danvet/drm-intel into drm-next Note that this commit is in the drm-next branch and so _not_ included in either drm-intel-fixes or drm-intel-next-queued. Hence please update the bug status with the result from -nightly only. (In reply to comment #3) > Please retest all kms_flip failures with latest -nightly, specifically: > > commit 735dc0d1e29329ff34ec97f66e130cce481c9607 > Merge: bac4b7c 20c60c3 > Author: Dave Airlie <airlied@redhat.com> > Date: Mon Jan 21 07:44:58 2013 +1000 > > Merge branch 'drm-kms-locking' of > git://people.freedesktop.org/~danvet/drm-intel into drm-next > > Note that this commit is in the drm-next branch and so _not_ included in > either drm-intel-fixes or drm-intel-next-queued. Hence please update the bug > status with the result from -nightly only. 1.On the platform G45,I retest all kms_flip with latest -nightly,the result is pass. 2.But I found a new prblem.While using below commit kernel booting gm45 was fail.Black screen and hang,I'm sorry I can't grab the dmesg.Can you tell me the way to grab the dmesg of a hang system? Kernel: (drm-intel-nightly)735dc0d1e29329ff34ec97f66e130cce481c9607 Some additional commit info: Merge: bac4b7c 20c60c3 Author: Dave Airlie <airlied@redhat.com> Date: Mon Jan 21 07:44:58 2013 +1000 3.I also try using its parent commit and gm45 can boot normally.The parent info is below: Kernel: (drm-intel-nightly)bac4b7c3b5c0660c08dc4949fe40e08e20364ee3 Some additional commit info: Author: Carsten Emde <C.Emde@osadl.org> Date: Thu Jul 19 15:54:25 2012 +0000 drm: Load EDID: Explain better how to write your own EDID firmware 4.So it may be the mergeing error. So to summarize: kms_flip works now on g45, but there's a new issue (which seems unrelated) on gm45? Can you please file a new bug for the gm45 boot issue with the bisect result? Since the bad commit seems to be a merge commit, you need to test both parents, which git bisect will automatically take care of. (In reply to comment #5) > So to summarize: kms_flip works now on g45, but there's a new issue (which > seems unrelated) on gm45? > > Can you please file a new bug for the gm45 boot issue with the bisect > result? Since the bad commit seems to be a merge commit, you need to test > both parents, which git bisect will automatically take care of. 1.kms_flip works now on g45 with latset nightly 2.The new bug about gm45a can not boot will be reported later. Ok, since this report here is for G45 I think we can close it. Verified. The GM45 hang issue direct to #59750 Closing verified+fixed. |
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.