Bug 28046 - [Ironlake] drm-intel-next kernel startup fails on piketon
Summary: [Ironlake] drm-intel-next kernel startup fails on piketon
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: All Linux (All)
: high normal
Assignee: Eric Anholt
QA Contact:
Depends on:
Reported: 2010-05-09 23:12 UTC by fangxun
Modified: 2017-10-06 14:54 UTC (History)
3 users (show)

See Also:
i915 platform:
i915 features:

messages on piketon. (2.50 KB, text/plain)
2010-05-10 03:29 UTC, fangxun
no flags Details

Description fangxun 2010-05-09 23:12:43 UTC
System Environment:
Mesa:           (master)8ad3e0b55df50beac8ba3c5cafa0be79641a4977
Xserver:        (master)72758287f79a4f1aa8fa388f20947042e3e14693
Xf86_video_intel:   (master)848ab66384508c3ad3e5fb4884e4527f3ebd3bde
Libdrm:         (master)6293152eb065016a2e5e4fcd047c2db5c2fb0f36
Kernel: (drm-intel-next)0c09e3544863568c52bc4dab73d340e0cf168312

Bug detailed description:
Currently drm-intel-next kernel startup fails on piketon. This is regression.
BTW, it can be start up on calpella, but fails to start X with error message:
Fatal server error:
no screens found
Please consult the The X.Org Foundation support
         at http://wiki.x.org
 for help.
Please also check the log file at "/opt/X11R7/var/log/Xorg.0.log" for additional information.
Message from syslogd@x-cp1 at May 10 13:49:39 ...
 kernel:[  461.130773] ------------[ cut here ]------------
Message from syslogd@x-cp1 at May 10 13:49:39 ...
 kernel:[  461.130781] invalid opcode: 0000 [#1] SMP
Message from syslogd@x-cp1 at May 10 13:49:39 ...
 kernel:[  461.130785] last sysfs file: /sys/devices/pci0000:00/0000:00:02.0/drm/card0/dev
Message from syslogd@x-cp1 at May 10 13:49:39 ...
 kernel:[  461.130883] Process modprobe (pid: 2700, ti=f6bdc000 task=f6003f70 task.ti=f6bdc000)
Message from syslogd@x-cp1 at May 10 13:49:39 ...
 kernel:[  461.130885] Stack:
Message from syslogd@x-cp1 at May 10 13:49:39 ...
 kernel:[  461.130908] Call Trace:
Message from syslogd@x-cp1 at May 10 13:49:39 ...
 kernel:[  461.131153] Code: 81 4b f8 00 74 1d 8b 1d d0 81 4b f8 85 db 74 13 b9 40 00 00 00 89 fa 89 f0 ff 13 83 c3 04 83 3b 00 eb eb 5b 5e 5f 5d c3 55 89 e5 <0f> 0b eb fe 55 89 e5 57 89 cf 56 53 83 ec 0c 89 45 ec 89 55 e8

Reproduce steps:
1.change kernel to currently drm-intel-next kernel 
Comment 1 fangxun 2010-05-10 03:29:44 UTC
Created attachment 35541 [details]
messages on piketon.

Attached is messages from /var/log/messages on piketon. It works fine with drm-intel-next kernel on other platforms.
Comment 2 Jesse Barnes 2010-05-10 10:30:59 UTC
Should be easy to bisect then?  Also, dmesg might have more info than /var/log/messages, which doesn't seem to have anything interesting.
Comment 3 fangxun 2010-05-10 23:46:13 UTC
9f770b8d635f602423671e9affa663957dab2055 is first bad commit:
commit 9f770b8d635f602423671e9affa663957dab2055
Merge: 3d8620c... 722154e...
Author: Eric Anholt <eric@anholt.net>
Date:   Fri May 7 14:30:03 2010 -0700

    Merge remote branch 'origin/master' into drm-intel-next


    The BSD ringbuffer support that is landing in this branch
    significantly conflicts with the Ironlake PIPE_CONTROL fix on master,
    and requires it to be tested successfully anyway.
Comment 4 fangxun 2010-05-11 02:28:22 UTC
BTW, the two merged commit 3d8620cc5f8538364ee152811e2bd8713abb1d58 and 722154e4cacf015161efe60009ae9be23d492296 is good commit. So 9f770b8d635f602423671e9affa663957dab2055 is first bad commit.
Comment 5 Gordon Jin 2010-05-24 18:35:33 UTC
Removing out of Q2 release, since Q2 release won't use this code.
Comment 6 Gordon Jin 2010-06-27 22:53:32 UTC
I suppose this has been fixed. Xun, can you verify?
Comment 7 fangxun 2010-06-28 00:01:23 UTC
Works fine with drm-intel-next kernel. Mark it as verified.
Comment 8 Elizabeth 2017-10-06 14:54:07 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.