Bug 768799 - Dell E6520 [Sandybridge] won't boot with kernel 2.6.41 (Optimus/nouveau/nVidia issue?)
Summary: Dell E6520 [Sandybridge] won't boot with kernel 2.6.41 (Optimus/nouveau/nVidi...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-intel
Version: 15
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-19 01:00 UTC by Tim Wegener
Modified: 2012-08-07 14:47 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-07 14:47:31 UTC
Type: ---


Attachments (Terms of Use)

Description Tim Wegener 2011-12-19 01:00:01 UTC
Description of problem:
System will hang during boot when booting a 2.6.41 kernel.
It works fine with a 2.6.40 kernel.

Version-Release number of selected component (if applicable):

Problem occurs with:
kernel-2.6.41.1-1.fc15.x86_64
kernel-2.6.41.4-1.fc15.x86_64

Fine with:
kernel-2.6.40.6-0.fc15.x86_64

How reproducible:
Always.

Steps to Reproduce:
1. Boot with specified kernel
2. Wait for it to hang (early in the boot process)
  
Actual results:
With kernel-2.6.41.4-1.fc15.x86_64:
nouveau 0000:01:00.0: Invalid ROM contents
[drm] nouveau 0000:01:00.0: 0x7291: i2c wrfail: -6
[drm] nouveau 0000:01:00.0: 0x72A3: i2c rdfail: -6
[drm:intel_dsm_platform_mux_info] *ERROR* MUX INFO call failed
Welcome to emergency mode. (etc.)

With kernel-2.6.41.1-1.fc15.x86_64:
As above, but just hung instead of going to emergency mode, and also added:
[drm_ironlake_update_pch_refclk] *ERROR* Enabled SSC on PCH
[drm_ironlake_update_pch_refclk] *ERROR* Enabled SSC on PCH


Expected results:
Normal boot without hanging.

Additional info:
xorg-x11-drv-intel-2.15.0-5.fc15.x86_64
xorg-x11-drv-nouveau-0.0.16-24.20110324git8378443.fc15.x86_64
xorg-x11-server-common-1.10.4-1.fc15.x86_64

Dell Latitude E6520
Intel® Core™ i7-2720QM CPU @ 2.20GHz × 8 
Intel® Sandybridge Mobile

$ lsmod |egrep 'nou|i915'
i915                  378744  2 
nouveau               545674  0 
ttm                    55273  1 nouveau
drm_kms_helper         26474  2 i915,nouveau
drm                   193955  5 i915,nouveau,ttm,drm_kms_helper
i2c_algo_bit            5006  2 i915,nouveau
i2c_core               25712  7 videodev,i2c_i801,i915,nouveau,drm_kms_helper,drm,i2c_algo_bit
mxm_wmi                 1727  1 nouveau
video                  12340  2 i915,nouveau


$ lspci -v |grep VGA
00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) (prog-if 00 [VGA controller])
01:00.0 VGA compatible controller: nVidia Corporation GF108 [Quadro NVS 4200M] (rev a1) (prog-if 00 [VGA controller])

The following comment on another bug for this system is perhaps also relevant:
https://bugzilla.redhat.com/show_bug.cgi?id=736895#c5

Comment 1 Tim Wegener 2011-12-19 04:18:36 UTC
Note that with kernel-2.6.40.6-0.fc15.x86_64 it still gives the message:
[drm:intel_dsm_platform_mux_info] *ERROR* MUX INFO call failed

...but not the other messages reported earlier, and it does not hang.

Comment 2 Tim Wegener 2012-01-06 02:40:16 UTC
This same problem occurs when booting from a Fedora 16 live CD.

Comment 3 Tim Wegener 2012-03-04 22:54:10 UTC
With Fedora 17 Alpha live CD it boots successfully. 
(Interestingly it still displays similar boot messages, though. Something like: i2c wrfail: -5)

Comment 4 Tim Wegener 2012-04-29 00:51:00 UTC
It's working now in kernel-2.6.43.2-6.fc15.x86_64.

(Also worked in kernel-2.6.42.9-2.fc15.x86_64, but was broken again in kernel-2.6.42.12-1.fc15.x86_64)

Also, while I assumed it had totally hung, pressing escape showed the textual boot messages and it was waiting at the LUKS prompt, so it was only the graphical boot part that was broken.

Comment 5 Fedora End Of Life 2012-08-07 14:47:35 UTC
This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 15 reached end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping


Note You need to log in before you can comment on or make changes to this bug.