[Bug 73971] Intel i915 screen remains blank when resuming from suspend

[bugzilla-daemon at bugzilla.kernel.org]

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

--- Comment #17 from Denis Leclair <denis at theleclairs.ca> ---
Here are the results:

I had the laptop plugged into the docking stations with two external monitors
connected to 2 display ports on the back of the dock. The lid of the laptop
remained open during the tests:

Test #1:
On boot up without nomodeset on the kernel line, I saw the graphical CentOS 6.5
splash screen instead of the terminal based blue lines scrolling from left to
right as I normally do. I also found that the splash screen was displayed on
all 3 displays simultaneously (the laptop screen + 2 external screens via
DisplayPort). Then I saw the following line show up:

[quote]
tpm_tis 00:0a: A TPM error (7) occurred attempting to read a pcr value
[/quote]

At this point the boot sequence halted and I had to power down the computer.


Test #2:
Again with the laptop plugged into the dock with the same two monitors
connected to the DisplayPorts and nomodeset removed from the kernel launch
line. This time I saw:

[quote]
tsc: Fast calibration failed
tpm_tis 00:0a: a TPM error (7) occurred attempting to read a pcr value
[/quote]

The boot sequence stopped there.
Note: I see the 'tsc: Fast calibration failed' line randomly from boot to boot
whether or not the nomodeset is on the kernel launch line.


Test #3:
I removed the laptop from the docking station and kept the nomodeset removed
from the kernel launch line. I again saw the 'tpm_tis' error line and the boot
sequence stopped.


Test #4:
I replaced the laptop back on the docking station and I re-added the nomodeset
to the kernel launch line. The boot sequence did not show the graphical splash
and instead had the blue bars scrolling from left to right. The boot sequence
completed successfully on the laptop screen and the two external monitors never
turned on.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.