Bug 31282

Summary: [bisected drm-intel-next] X sever unable to run due to inserting i915 failed
Product: DRI Reporter: wang,jinjin <jinjin.wang>
Component: DRM/IntelAssignee: Chris Wilson <chris>
Status: CLOSED FIXED QA Contact:
Severity: blocker    
Priority: high CC: jbarnes
Version: unspecified   
Hardware: All   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
xorg log none

Description wang,jinjin 2010-10-31 23:05:17 UTC 
Detailed description:
---------------------------------------
With the newest Kernel: (drm-intel-next)ff75b9bc489710ff223bc0d805bf3b862dc347ea, when kernel's booting, it was unable to load i915 module. As the same of that reason, X sever also failed to run.

The error message:
--------------------------
FATAL: Error inserting i915 (/lib/modules/2.6.36_e380f60b22eddec7825224b8d788572c82b63161_20101101+/kernel/drivers/gpu/drm/i915/i915.ko): No such device
(EE) No devices detected


I bisected it and found the first bad commit was :
commit e380f60b22eddec7825224b8d788572c82b63161
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date:   Fri Oct 29 18:11:26 2010 +0100

    agp/intel: Sandybridge doesn't require GMCH enabling
Comment 1 wang,jinjin 2010-10-31 23:10:13 UTC 
Created attachment 39942 [details]
xorg log
Comment 2 zhao jian 2010-11-01 01:34:30 UTC 
It blocks our nightly test now. So higher its grade.
Comment 3 Chris Wilson 2010-11-01 02:51:10 UTC 
Did you not read the dmesg?

commit 100519e2f1c20286158746f92f27c3aa14f5a893
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date:   Sun Oct 31 10:37:02 2010 +0000

    agp/intel: the GMCH is always enabled for integrated processor graphics
    
    ... and trying to set the bit is ineffectual.
    
    Fixes the regression from e380f60 which detected that we were trying to
    do undefined operations on the I830_GMCH_CTRL.
    
    Reported-by: Alexey Fisher <bug-track@fisher-privat.net>
    Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Comment 4 wang,jinjin 2010-11-01 19:46:56 UTC 
Chris , I'm sorry, but when I wanted to get the newest kernel source[git pull origin +drm-intel-next:drm-intel-next].The repository which had updata to 10-30 would git to old commit:
commit f573c66061184ce28196a22229b6214256ceacd8
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date:   Tue Sep 28 23:34:44 2010 +0100

    drm/i915/dvo: Fix panel and DDC i2c pins
BTW, we tried to git clone a new tree and git pull. It also git to the commit above.

So, maybe the origin of branch have problem? Please check it .


Thanks!!
Comment 5 Chris Wilson 2010-11-02 02:29:46 UTC 
(In reply to comment #4)
> Chris , I'm sorry, but when I wanted to get the newest kernel source[git pull
> origin +drm-intel-next:drm-intel-next].The repository which had updata to 10-30
> would git to old commit:
> commit f573c66061184ce28196a22229b6214256ceacd8
> Author: Chris Wilson <chris@chris-wilson.co.uk>
> Date:   Tue Sep 28 23:34:44 2010 +0100
> 
>     drm/i915/dvo: Fix panel and DDC i2c pins
> BTW, we tried to git clone a new tree and git pull. It also git to the commit
> above.
> 
> So, maybe the origin of branch have problem? Please check it .

They upgraded hera.kernel.org. Tthere was a little bit of a time leak last night and we were all thrown back by a month. Everything seems back to normal now.
Comment 6 wang,jinjin 2010-11-02 03:15:27 UTC 
I verify it with the commit given.The issue did not happen.
Comment 7 Elizabeth 2017-10-06 14:53:25 UTC 
Closing old verified.

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.