Kernel hangs while booting if there is a monitor connected to DP2

[nadrimajstor]

I'm trying triple monitor configuration on HD4000:
 - 1650x1050 on VGA1
 - 1920x1080 on DP2
 - 1920x1080 on DP3

Kernel hangs on boot if there is a monitor attached to DP2.

If I attach monitor after boot, changing resolution on DP2 one CPU core becomes 100% busy with continuous errors:

[drm:intel_dp_start_link_train], training pattern 1 signal levels 00000000
[drm:intel_dp_start_link_train], training pattern 1 signal levels 02000000
[drm:intel_dp_start_link_train], training pattern 1 signal levels 04000000

BTW, Same triple monitor configuration works fine in Windows 7 so I assume that hardware is ok.

Please advise what can be done next?

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.5.0-25-generic 3.5.0-25.39~precise1
ProcVersionSignature: Ubuntu 3.5.0-25.39~precise1-generic 3.5.7.4
Uname: Linux 3.5.0-25-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.0.1-0ubuntu17.1
Architecture: i386
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: [Errno 2] No such file or directory
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
Card0.Amixer.info: Error: [Errno 2] No such file or directory
Card0.Amixer.values: Error: [Errno 2] No such file or directory
Date: Mon Feb 6 15:34:43 2012
IwConfig: Error: [Errno 2] No such file or directory
Lspci: Error: [Errno 2] No such file or directory
MachineType: ICP/iEi B207
MarkForUpload: True
PciMultimedia:

ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-25-generic root=UUID=0cccb37a-5761-45a8-b9db-1e5f6eebbb80 ro drm.debug=0x06
RelatedPackageVersions:
 linux-restricted-modules-3.5.0-25-generic N/A
 linux-backports-modules-3.5.0-25-generic N/A
 linux-firmware 1.79.2
RfKill: Error: [Errno 2] No such file or directory
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/10/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.5
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: B207
dmi.board.vendor: ICP/iEi
dmi.board.version: V1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/10/2012:svnICP/iEi:pnB207:pvrV1.0:rvnICP/iEi:rnB207:rvrV1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: B207
dmi.product.version: V1.0
dmi.sys.vendor: ICP/iEi

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1153627

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.9 kernel[0] (Not a kernel in the daily directory) and install both the linux-image and linux-image-extra .deb packages.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.9-rc2-raring/

[nadrimajstor (ipejic)]

@Brad Figg
I'm unable to add report with 'apport-collect 1153627' - can't find workaround for
"ERROR: connecting to Launchpad failed: [Errno 1] _ssl.c:504: error:14090086:SSL outines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed"

@Joseph Salisbury
Tested using:
linux-image-3.9.0-030900rc2-generic_3.9.0-030900rc2.201303102035_i386.deb
linux-image-extra-3.9.0-030900rc2-generic_3.9.0-030900rc2.201303102035_i386.deb

A bit different manifestation but same underlaying problem exist upstream:

- Kernel is able to boot without hanging. However, looks like error is not triggered because resolution is automatically set at 1024x768 for all outputs.

- Issuing:
xrand --output VGA1 --auto --output DP2 --auto --output DP3 --auto

1. triggers the same continuous errors:
...
[drm:intel_dp_set_signal_levels], Using signal levels 00000000
[drm:intel_dp_set_signal_levels], Using signal levels 02000000
[drm:intel_dp_set_signal_levels], Using signal levels 04000000
...

2. at this point xserver stop responding, xrandr is unusable
3. but I can confirm from monitor OSD that VGA1 and DP2 are correctly set. Monitor OSD connected at DP3 state "No signal".

[nadrimajstor (ipejic)]

This patch solved this issue "Revert "drm/i915: try to train DP even harder"
http://cgit.freedesktop.org/~danvet/drm-intel/commit/?id=3b4f819d5eac94ba8fe5e8c061f6dabfe8d7b22c

[penalvch (penalvch)]

nadrimajstor, could you please confirm this issue exists with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

[nadrimajstor (ipejic)]

I've tried patch in comment #5 and it solves this issue in 12.04.
Also, I've tested latest development release and I can confirm that this issues is solved.

[penalvch (penalvch)]

nadrimajstor, would you need a backport to a release prior to Saucy, or may we mark this as Status Invalid?

[nadrimajstor (ipejic)]

I was under impression that my use of triple monitor configuration on single HD4000 GPU is kinda corner case (there might be others on Phoronix forums that may disagree on this :).
I'm not sure will time spent on backporting this issues will be a benefit to everyone as this is not the only bug that will need to be backported for a fully operational triple monitor configuration (I've reported this bug as a major one).
I'll be more than happy to see this configuration working in LTS. However I can truly only help with testing.

[penalvch (penalvch)]

nadrimajstor, thank you for taking the time to report this bug and helping to make Ubuntu better. However, I am closing it because the bug has been fixed in the latest development version of Ubuntu - Saucy Salamander.

This is a significant bug in Ubuntu. If you need a fix for the bug in previous versions of Ubuntu, please do steps 1 and 2 of the SRU Procedure [1] to bring the need to a developer's attention.

[1]: https://wiki.ubuntu.com/StableReleaseUpdates#Procedure