From: "Theodore Ts'o" <tytso@mit.edu>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>,
DRI <dri-devel@lists.freedesktop.org>,
Daniel Vetter <daniel.vetter@intel.com>,
Mani Nikula <jani.nikula@linux.intel.com>,
Ander Conselvan de Oliveira
<ander.conselvan.de.oliveira@intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [REGRESSION] Re: i915 driver crashes on T540p if docking station attached
Date: Mon, 3 Aug 2015 14:49:52 -0400 [thread overview]
Message-ID: <20150803184952.GA21851@thunk.org> (raw)
In-Reply-To: <CA+55aFzV3SL+5WL5+j-oQ86Q1Mk+je3E-bp1OsX1XJA0RT2FyA@mail.gmail.com>
On Mon, Aug 03, 2015 at 10:24:53AM -0700, Linus Torvalds wrote:
> On Mon, Aug 3, 2015 at 9:25 AM, Theodore Ts'o <tytso@mit.edu> wrote:
> >
> > I've just tried pulling in your updated fixes-stuff, and it avoids the
> > oops and allows external the monitor to work correctly.
>
> Good. Have either of you tested the suspend/resume behavior? Is that fixed too?
No, I haven't had a chance to test the suspend/resume behavior,
because that requires suspending at work, going home, and connecting
to a dock which has a different monitor attached to it, and resuming
(or vice versa of suspending at home and then resuming at work).
So it's a bit trickier for me to test. It's also not a regression,
and the workaround of rebooting is annoying, but I've lived with it
for several releases now, but I'll try the two patches/changes that
folks had suggested hopefully later this week.
- Ted
next prev parent reply other threads:[~2015-08-03 18:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-30 0:49 i915 driver crashes on T540p if docking station attached Theodore Ts'o
2015-07-30 1:39 ` [REGRESSION] " Theodore Ts'o
2015-07-30 5:18 ` Linus Torvalds
2015-07-30 11:16 ` Dave Airlie
2015-07-30 14:40 ` Daniel Vetter
2015-07-30 15:32 ` Theodore Ts'o
2015-07-30 15:54 ` [Intel-gfx] " Daniel Vetter
2015-07-30 15:57 ` Takashi Iwai
2015-07-30 18:14 ` Linus Torvalds
2015-07-30 15:50 ` Theodore Ts'o
2015-07-30 15:59 ` Theodore Ts'o
2015-07-30 16:00 ` Daniel Vetter
2015-08-03 15:27 ` Daniel Vetter
2015-08-03 16:25 ` Theodore Ts'o
2015-08-03 17:24 ` Linus Torvalds
2015-08-03 18:49 ` Theodore Ts'o [this message]
2015-08-03 22:05 ` Daniel Vetter
2015-08-04 1:17 ` Rafael J. Wysocki
2015-08-04 16:05 ` Daniel Vetter
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=20150803184952.GA21851@thunk.org \
--to=tytso@mit.edu \
--cc=ander.conselvan.de.oliveira@intel.com \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.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