Since we are getting to the pointy end, one i915 black screen on some machines, and one vmwgfx stop userspace ability to nuke the VM,
there might be one or two ati or nouveau fixes trickle in before final, but I think this should pretty much be it.
Dave.
The following changes since commit d8dfad3876e4386666b759da3c833d62fb8b2267:
Linux 3.11-rc7 (2013-08-25 17:43:22 -0700)
are available in the git repository at:
ssh://people.freedesktop.org/~airlied/linux drm-fixes
for you to fetch changes up to 6e4dcff3adbf25acb87e74500a58e3c07bdec40f:
drm/vmwgfx: Split GMR2_REMAP commands if they are to large (2013-08-30 09:03:39 +1000)
---------------------------------------------------------------- Dave Airlie (1): Merge tag 'drm-intel-fixes-2013-08-30' of git://people.freedesktop.org/~danvet/drm-intel into drm-fixes
Imre Deak (1): drm/i915: ivb: fix edp voltage swing reg val
Jakob Bornecrantz (1): drm/vmwgfx: Split GMR2_REMAP commands if they are to large
drivers/gpu/drm/i915/i915_reg.h | 2 +- drivers/gpu/drm/vmwgfx/vmwgfx_gmr.c | 58 +++++++++++++++++++++++++------------ 2 files changed, 40 insertions(+), 20 deletions(-)
On Thu, Aug 29, 2013 at 4:08 PM, Dave Airlie airlied@linux.ie wrote:
ssh://people.freedesktop.org/~airlied/linux drm-fixes
Please people! When you post ssh addresses, always remember to also post your user name and password or private key with the pull request.
Ok?
Linus
On Sat, Aug 31, 2013 at 9:18 AM, Linus Torvalds torvalds@linux-foundation.org wrote:
On Thu, Aug 29, 2013 at 4:08 PM, Dave Airlie airlied@linux.ie wrote:
ssh://people.freedesktop.org/~airlied/linux drm-fixes
Please people! When you post ssh addresses, always remember to also post your user name and password or private key with the pull request.
Ok?
Oh sorry [1]
Oops, forgot to add the -public to my request-pull command line,
git://people.freedesktop.org/~airlied/linux drm-fixes
should be the right thing.
Dave.
[1]
-----BEGIN RSA PRIVATE KEY----- MIIEpAIBAAKCAQEA8Sxk4nlsPzPf6Ezgr1wmWoggaCnsLc6t1K5tHZjqtZfhPTGS Vwv5s+pcEdsq408TGNk8wMNyvTWp1WgY0r3xxr9+FI6Phv69aQwbvtJ43Hvn3XCz 9EAXCmXY/rhWvFOOKVh0NFVc7Bzul+jW0J1TUXxu5fbq2eSy7P02QCb7JZLYQc1J TxZkcAgFjYV1tU1q0NRh9Y4EoUI1nYjVbhFXuXvzL2YB0u6PciPm7n0Yqfwgs1MU lZuiEzehd89Vm9y2LSzcYamimsv569WletzvtnUWGkyGxUCA0T8yGexu4/r3883I 8amLb8rj/4XeWlxtKsFV+oAF9Ru7SPPq8oah7QIDAQABAoIBADYO/2YMVYktNYk6 gjqMa0RrsufmTbxO0YQUvPyfZCzkKGaxD95XHteHNrAB8nEVLnCpcQa8SKHEv5bI SJgkX2dvUPGGqwFVZFuBjU6OmuzBEU3/jza2jvOTtLoT081O5VS7MQDyCWwbaBfA 5zXHrf9b5vfBCw9gRgL9FwX2NuFKw64UogKz/t+x7h6fqL8yCCwjdTRvOrDpLUto x4y7Xbc5lvppzLoxpR4CGDB8PNXfHwYsw3uAJd5A0RxjXcBy0yLgOmMzK4yDxQgF qPaV3LyUtVWx6hqBS15v7Vu58aW1d3hjqy1QQFC2iQ61bBqVyQrhFLAN5C9z22h8 XFT5SUECgYEA+QksPviu2JgrAw/0VzHHL/7CpXlgwdXvkcTqLxTNBMbcsJOfUxYX IZf2hT8gReveeHxRoHCwX2fmfqXSsa70z2vpseo/hC+2OHF9tXezU2hFzwdS/lMZ 5wqxm2wxgiM0G4ZeILZ+YapXfHoutgLPanFSWh22pmsIqt00LcvMlWUCgYEA9+rv UfA/k5YLrpaPj87dRTQ5PKTO/z7UgEkFfHaQFok8nu+M+tuuNZHVuKJ+gPBx/L9J gIwpc0h1xz0eYFAFAuwBBslLHvJUOK5VRYEKHVxYTUVi3TzM471dLjGGIekwB16j bCBXXTLOhAtYJ3h0YCfHK80gkqVvEBD+fvvl9ekCgYB2uZTKgKx6vjDjSNvoJecc ToxlbzRdtKx+Bi7PO09yk4vq8rXmWoW0kkoIxEuSihyJvFr97jtngJU2k7+azhoQ ORY0p8SYNFbfGdwgg2yOuwts48UBUoTqzQJXYoFH1Zil9q0xU091KEyFH4rdYwGX cWcdZ0UImcaMDuEtZBeosQKBgQCYVQ4aLeISwFaLP04VEgnZ9P3aanYaVjPiY3vw fzWH82mBSzY4CfXgSqyk14udlKClqa/zQaxSfsqH0uEwUtrRccwrrFHxQPtJHK2e mGxroAtN532Y7TwED54KvTlq6sqtLJSD4tdrl8VXU1UmY5g2YRq7qj4CfY5hs998 jTE+yQKBgQCSrChX2Q1qj/+SqiX2058uDfkLzAlo4sP2mLvqREKW7NbF72UgS1Ws Bbr52p6ISi2yeCylkf+7EkEGUX5lelkyP8UrawsPoTWDyPoaRurSqGwthkGPCSDW 8kRPWlu7rJD+ZZC61EdtQJAKUCXuLVcK3+SXp3PNPZQW7LMOLdbixQ== -----END RSA PRIVATE KEY-----
Hmm. I just updated my machine to a i7-4770S (kept everything else the same, just switched out motherboards), and now when my display goes to sleep, it seems to never come back.
Any known issues with DVI on Haswell (it seems to show up as "HDMI1" as the output, but it's a DVI cable)? I need to get a DP cable anyway (right now I'm driving my 2560x1440 display at 32Hz due to DVI crap) and maybe that will fix things, but this happens even if I don't force that odd mode (so it maxes out at 1920x1200 or whatever).
I doubt this is new, but I've only ever run current -git on this machine, so who knows.. The machine ends up being kind of unusable. I guess I can just turn off power save.
Linus
On Sat, Aug 31, 2013 at 4:02 PM, Linus Torvalds torvalds@linux-foundation.org wrote:
Any known issues with DVI on Haswell (it seems to show up as "HDMI1" as the output, but it's a DVI cable)?
With a DP cable and the same monitor, the problem doesn't seem to occur. So it does seem to somehow be related to the HDMI1/DVI output.
Linus
On Sat, Aug 31, 2013 at 04:02:16PM -0700, Linus Torvalds wrote:
Hmm. I just updated my machine to a i7-4770S (kept everything else the same, just switched out motherboards), and now when my display goes to sleep, it seems to never come back.
Sleep as in dpms off ($ xset dpms force off) or sleep as in system suspend?
Any known issues with DVI on Haswell (it seems to show up as "HDMI1" as the output, but it's a DVI cable)? I need to get a DP cable anyway (right now I'm driving my 2560x1440 display at 32Hz due to DVI crap) and maybe that will fix things, but this happens even if I don't force that odd mode (so it maxes out at 1920x1200 or whatever).
I doubt this is new, but I've only ever run current -git on this machine, so who knows.. The machine ends up being kind of unusable. I guess I can just turn off power save.
Hm, doesn't ring a bell here. Adding Paulo, our residential hsw display expert.
Aside hsw hdmi ports support 300MHz dotclocks, but still only single-link. So I guess your dvi screen is still out of luck since it likely wants a dual-link dvi signal. But if you have a hdmi port it should work a bit better (hdmi pumped up the max dotclock a bit already a while ago ...).
Cheers, Daniel
On Sun, Sep 1, 2013 at 11:54 PM, Daniel Vetter daniel@ffwll.ch wrote:
On Sat, Aug 31, 2013 at 04:02:16PM -0700, Linus Torvalds wrote:
Hmm. I just updated my machine to a i7-4770S (kept everything else the same, just switched out motherboards), and now when my display goes to sleep, it seems to never come back.
Sleep as in dpms off ($ xset dpms force off) or sleep as in system suspend?
Just dpms off.
Aside hsw hdmi ports support 300MHz dotclocks, but still only single-link. So I guess your dvi screen is still out of luck since it likely wants a dual-link dvi signal. But if you have a hdmi port it should work a bit better (hdmi pumped up the max dotclock a bit already a while ago ...).
Well, with DP everything works without playing with refresh rates, and dpms off works too.
So it's DVI-specific (I haven't tested an actual hdmi cable, I don't think I have any around), and it also happens even if I *don't* set odd refresh rates. But if others haven't seen it, it's probably not universal, I can't imagine that I'm the only one still using DVI (well, up until yesterday).
This is a bog-standard micro-atx Intel motherboard: DH87RL with a i7-4770S CPU. Everything else seems to be just peachy.
Linus
dri-devel@lists.freedesktop.org
-
Daniel Vetter -
Dave Airlie -
Dave Airlie -
Linus Torvalds