From: Martin Steigerwald <martin@lichtvoll.de>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Intel Gfx Mailing List <intel-gfx@freedesktop.org>,
Jani Nikula <jani.nikula@linux.intel.com>
Subject: [REGRESSION] Black screen after switching desktop session (was: Re: Linux 4.10-rc5)
Date: Wed, 25 Jan 2017 13:10:26 +0100 [thread overview]
Message-ID: <4283369.vZ72qk4V7n@merkaba> (raw)
In-Reply-To: <CA+55aFyBGS3Vy_LJk69Lha5SfyKv20DEHLEkwnHi3L634QfE9A@mail.gmail.com>
Am Sonntag, 22. Januar 2017, 13:32:08 CET schrieb Linus Torvalds:
> Things seem to be calming down a bit, and everything looks nominal.
>
> There's only been about 250 changes (not counting merges) in the last
> week, and the diffstat touches less than 300 files (with drivers and
> architecture updates being the bulk, but there's tooling, networking
> and filesystems in there too).
>
> So keep testing, and I think we'll have a regular release schedule.
Testing this is no fun:
Bug 99533 - black screen after switching session
https://bugs.freedesktop.org/99533
This after GPU hang/lockups with Kernel 4.9 reported as for example:
Bug 98922 - [snb] GPU hang on PlaneShift
https://bugs.freedesktop.org/98922
Which may be a duplicate of #98747, #98794, #98860, #98891, #98288.
I am back at kernel 4.8.15 as I need this machine for production work.
Sometimes I wish for a microkernel that might be able to reincarnate drivers
that hang or do wierd things like that. That may at least give a way to
actually do some debugging or even get the desktop session back without
loosing its state. Especially for graphics drivers and hibernating/resuming
from hibernations which also occasionally fails – again without leaving a way
to interact with the machine to do further debugging. Linux kernel usually
just crashes completely, not even a ping or ssh possible, or it at least stuck
with a black display without any way to restart the graphics driver cause it
seems to be in some undefined state. Combined with occasionally happening bugs
this makes triaging bugs time consuming and risky. I do like to help testing,
but maybe its time to just switch to distro kernels and be done about it, as I
regularily come across bugs that are too expensive for me to triage.
Please understand that I am not willing to bisect these occasionally happening
bugs with have the potential to cause data loss due to having to switch off
the machine forcefully. Fortunately at least KMail saves a mail I write from
time to time and also Kate does swap files.
I am also a bit unwilling to do further debugging of this one as I usually use
two sessions when I am at work and I risk loosing data I work on. But… at
least with this issue it seems I would have a way to SSH into the machine
before kicking it.
I am dissatisfied with the state of the Intel graphics driver on this ThinkPad
T520 with Sandybridge since kernel 4.9 and wonder whether you guys at Intel
really test things with older hardware versions.
Thanks,
--
Martin
next prev parent reply other threads:[~2017-01-25 12:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-22 21:32 Linux 4.10-rc5 Linus Torvalds
2017-01-25 12:10 ` Martin Steigerwald [this message]
2017-02-01 13:11 ` [Intel-gfx] [REGRESSION] Black screen after switching desktop session (was: Re: Linux 4.10-rc5) David Weinehall
2017-02-11 14:55 ` Martin Steigerwald
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4283369.vZ72qk4V7n@merkaba \
--to=martin@lichtvoll.de \
--cc=intel-gfx@freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox