New: Boot crashes on Lenovo W520 KVM and Discrete Graphic enabled in BIOS

https://bugzilla.kernel.org/show_bug.cgi?id=104271

            Bug ID: 104271
           Summary: Boot crashes on Lenovo W520 KVM and Discrete Graphic
                    enabled in BIOS
           Product: Virtualization
           Version: unspecified
    Kernel Version: 4.1.6
          Hardware: Intel
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: blocking
          Priority: P1
         Component: kvm
          Assignee: [email protected]
          Reporter: [email protected]
        Regression: No

Booting stops/crashes on a Lenovo W520 Notebook with these BIOS Settings:
- Virtualization
Intel Virtualization Technology: Enabled
Intel VT-d Feature: Enabled
- Display
Boot Display Device: ThinkPad LCD
Graphics Device: Discrete Graphics
OS Detection for NVIDIA Optimus: Disabled

Booting starts and the last lines show that the kernel cannot access the hard disks (lines starting with ata2 and ata1). The last lines are:

[ TIME ] Timed out waiting for device dev-disk-by\x2duuid-c30...4394b6b.device. [ DEPEND ] Dependency failed for /dev/disk/by-uuid/c305bd9f-9d6...7-359b94394b6b.
[ DEPEND ] Dependency failed for Swap.

After that booting stops.

Additional Information:
- This is no hardware fault. The error can be reproduced on a different W520.

- Booting also crashes with these kernels:
- 3.16.0 (kernel from Debian Jessie)
- 4.1.0 (backported kernel to Debian Jessie)

- Booting succeeds if:
- both virtualization flags are set to Disabled in the BIOS or
- Graphics Device is set to "Optimus" in the BIOS

You are receiving this mail because:
You are watching the assignee of the bug.

https://bugzilla.kernel.org/show_bug.cgi?id=104271

Hans Streibel <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------

            Summary|Boot crashes on Lenovo W520 |Boot crashes on Lenovo W520
                   |KVM and Discrete Graphic    |with KVM and Discrete
                   |enabled in BIOS             |Graphic enabled in BIOS

You are receiving this mail because:
You are watching the assignee of the bug.

https://bugzilla.kernel.org/show_bug.cgi?id=104271

Huaitong Han <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]

--- Comment #1 from Huaitong Han <[email protected]> ---
Does it work well on windows? I guess it's a BIOS problem. finding a avaliable disk device is the job of BIOS, and the problem just right occurs when you change the BIOS settings.

You are receiving this mail because:
You are watching the assignee of the bug.

https://bugzilla.kernel.org/show_bug.cgi?id=104271

--- Comment #2 from Hans Streibel <[email protected]> --- Yes, it works on Windows 7. I did not recognize any problems there. Ok, I did not try any virtualization like Virtual Box under Windows, but everything else seems to work.

Even if it is a BIOS problem, then Windows obviously found a way to handle it.

You are receiving this mail because:
You are watching the assignee of the bug.

https://bugzilla.kernel.org/show_bug.cgi?id=104271

Alex Williamson <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]

--- Comment #3 from Alex Williamson <[email protected]> --- You might get more attention moving this bug to Drivers/PCI and including the full dmesg or console log of the failure and lspci -vvv so we know something about your system. If it doesn't boot, there are always screen shots or netconsole if you're serial port challenged.

KVM is a hypervisor, it has nothing to do with your system not booting. More likely it's something with the IOMMU. Does disabling VT-d help? What about booting with iommu=pt? BTW, reproducing on another W520 doesn't mean the hardware isn't broken, it just means this isn't a point defect. Hardware is broken a disturbing amount of the time.

You are receiving this mail because:
You are watching the assignee of the bug.

https://bugzilla.kernel.org/show_bug.cgi?id=104271

--- Comment #4 from Hans Streibel <[email protected]> --- Created attachment 187321
--> https://bugzilla.kernel.org/attachment.cgi?id=187321&action=edit
Output of lspci -vvv

You are receiving this mail because:
You are watching the assignee of the bug.

https://bugzilla.kernel.org/show_bug.cgi?id=104271

Hans Streibel <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------

          Component|kvm                         |PCI
            Version|unspecified                 |2.5
            Product|Virtualization              |Drivers

--- Comment #5 from Hans Streibel <[email protected]> --- Ok, will move it to Drivers/PCI.

Output of lspci -vvv now is in the appendix.
Output of dmesg is not included because that only shows output of a successfully booted kernel. I even installed bootlogd but its log file does not show error messages.

I made some pictures with my camera but I do not dare to attach those somewhat big jpg files here. But if you really need them I can attach them.

The trouble starts (most of the time) right behind the line:
shpchp: Standard Hot Plug PCI Controller Driver Version: 0.4

Yes, disabling VT-d did help. Booting succeeded again. Using "iommu=pt" however did not help. Same symptoms.

BTW, I wanted to express that my special notebook is not broken. Not more broken that all (many/most) of the others W520s around.

You are receiving this mail because:
You are watching the assignee of the bug.

https://bugzilla.kernel.org/show_bug.cgi?id=104271

Hans Streibel <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]

--- Comment #6 from Hans Streibel <[email protected]> ---
As Alex suggested I moved this bug to Drivers/PCI to get more attention. However now I have the impression that this bug does not get any attention at all any more.

Did I miss any necessary action beside moving this to Drivers/PCI?

You are receiving this mail because:
You are watching the assignee of the bug.