From: Jani Nikula <jani.nikula@linux.intel.com>
To: Klaus Ethgen <Klaus+lkml@ethgen.de>, linux-kernel@vger.kernel.org
Cc: dri-devel <dri-devel@lists.freedesktop.org>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Subject: Re: [KERNEL] Regression bug in drm/i915, Wrong assumption in commit e11aa36 breaks suspend on at least lenovo x61
Date: Wed, 18 Feb 2015 17:39:20 +0200 [thread overview]
Message-ID: <87mw4bw7o7.fsf@intel.com> (raw)
In-Reply-To: <20150217082937.GA27873@ikki.ethgen.ch>
On Tue, 17 Feb 2015, Klaus Ethgen <Klaus+lkml@ethgen.de> wrote:
> After solving the conflicts, I applied the revert (see attachment) to
> v3.18.7. I think it should also apply to the current head. With that
> patch, suspend is working again on that version.
>
> However, I have not to deep knowledge of that subsystem, so please,
> someone who have, have a deeper look into it. I especially do not know
> if the lines in .../intel_pm.c are correct or better leaving them as
> they are in v3.18.7.
>
> I want to have it working on a version that I know is stable before
> asking to pull it to head.
Hi Klaus, we fear this patch may hide the actual cause. Would be useful
to get a better description of what happens, along with a dmesg with
drm.debug=14 module parameter set. This might clutter the mailing list,
would you mind filing a bug at [1] and attach the info there?
Thanks,
Jani.
[1] https://bugs.freedesktop.org/enter_bug.cgi?product=DRI&component=DRM/Intel
--
Jani Nikula, Intel Open Source Technology Center
WARNING: multiple messages have this Message-ID (diff)
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Klaus Ethgen <Klaus+lkml@ethgen.de>, linux-kernel@vger.kernel.org
Cc: dri-devel <dri-devel@lists.freedesktop.org>,
"intel-gfx\@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Subject: Re: [KERNEL] Regression bug in drm/i915, Wrong assumption in commit e11aa36 breaks suspend on at least lenovo x61
Date: Wed, 18 Feb 2015 17:39:20 +0200 [thread overview]
Message-ID: <87mw4bw7o7.fsf@intel.com> (raw)
In-Reply-To: <20150217082937.GA27873@ikki.ethgen.ch>
On Tue, 17 Feb 2015, Klaus Ethgen <Klaus+lkml@ethgen.de> wrote:
> After solving the conflicts, I applied the revert (see attachment) to
> v3.18.7. I think it should also apply to the current head. With that
> patch, suspend is working again on that version.
>
> However, I have not to deep knowledge of that subsystem, so please,
> someone who have, have a deeper look into it. I especially do not know
> if the lines in .../intel_pm.c are correct or better leaving them as
> they are in v3.18.7.
>
> I want to have it working on a version that I know is stable before
> asking to pull it to head.
Hi Klaus, we fear this patch may hide the actual cause. Would be useful
to get a better description of what happens, along with a dmesg with
drm.debug=14 module parameter set. This might clutter the mailing list,
would you mind filing a bug at [1] and attach the info there?
Thanks,
Jani.
[1] https://bugs.freedesktop.org/enter_bug.cgi?product=DRI&component=DRM/Intel
--
Jani Nikula, Intel Open Source Technology Center
next prev parent reply other threads:[~2015-02-18 15:39 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-11 11:39 Problems with suspend on recent kernel (not necessary a bug) Klaus Ethgen
2015-02-16 22:11 ` Regression bug in drm/i915, Wrong assumption in commit e11aa36 breaks suspend on at least lenovo x61 Klaus Ethgen
2015-02-16 22:17 ` Dave Airlie
2015-02-16 22:17 ` Dave Airlie
2015-02-17 8:29 ` [KERNEL] " Klaus Ethgen
2015-02-18 15:39 ` Jani Nikula [this message]
2015-02-18 15:39 ` Jani Nikula
2015-02-18 16:24 ` [Intel-gfx] " Imre Deak
2015-02-19 10:47 ` Dave Gordon
2015-02-19 10:47 ` [Intel-gfx] " Dave Gordon
2015-02-19 11:08 ` Imre Deak
2015-02-19 15:42 ` Dave Gordon
2015-02-19 15:42 ` [Intel-gfx] " Dave Gordon
2015-02-19 16:39 ` Imre Deak
2015-02-19 16:39 ` Imre Deak
2015-02-18 19:03 ` [KERNEL] " Klaus Ethgen
2015-02-18 19:03 ` Klaus Ethgen
2015-02-18 19:03 ` Klaus Ethgen
2015-02-18 20:27 ` Imre Deak
2015-02-22 10:30 ` Daniel Vetter
2015-02-22 10:30 ` 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=87mw4bw7o7.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=Klaus+lkml@ethgen.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.