public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Steven Honeyman <stevenhoneyman@gmail.com>,
	Matt Roper <matthew.d.roper@intel.com>,
	stable@vger.kernel.org
Cc: "intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	Dave Airlie <airlied@redhat.com>,
	Daniel Vetter <daniel.vetter@intel.com>
Subject: Re: [Intel-gfx] Kernel panic every other reboot/poweroff since 3.19.3 ( commit 9a6f5130143 )
Date: Thu, 02 Apr 2015 14:02:00 +0300	[thread overview]
Message-ID: <87d23mssif.fsf@intel.com> (raw)
In-Reply-To: <CABz95_Dco7Y=WXBpQ7Xp-scVLTtvTmcK2sQU-zcKQroENchyzA@mail.gmail.com>

On Tue, 31 Mar 2015, Steven Honeyman <stevenhoneyman@gmail.com> wrote:
> On 31 March 2015 at 17:50, Matt Roper <matthew.d.roper@intel.com> wrote:
>> On Tue, Mar 31, 2015 at 08:54:19AM +0200, Daniel Vetter wrote:
>>> Adding mailing lists (and hooray for me mixing up addresses, so now
>>> there's a disclaimer at the bottom).
>>> -Daniel
>>
>> It looks like this is caused by 3.19.3 having
>>
>>         commit 77f7ef95e2cf09150e5777454fd5df69af39edcd
>>         Author: Chris Wilson <chris@chris-wilson.co.uk>
>>         Date:   Wed Feb 25 13:45:26 2015 +0000
>>
>>             drm: Don't assign fbs for universal cursor support to files
>>
>> without also having
>>
>>         commit 8218c3f4df3bb1c637c17552405039a6dd3c1ee1
>>         Author: Daniel Vetter <daniel.vetter@ffwll.ch>
>>         Date:   Fri Feb 27 12:58:13 2015 +0100
>>
>>             drm: Fixup racy refcounting in plane_force_disable
>>
>>
>> Can you try cherry-picking 8218c3f4df3bb1c637c17552405039a6dd3c1ee1 and
>> see if it solves the problem?
>>
>>
>> Matt
>
> It does! Thanks Matt.
>
> 5 successful reboots and a successful shutdown. The only change
> between the two kernels was the above patch.

Stable team, please ensure 8218c3f4df3bb1c637c17552405039a6dd3c1ee1,
already tagged cc: stable, is picked up for v3.19.4.

This is also reported as

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


Thanks,
Jani.


-- 
Jani Nikula, Intel Open Source Technology Center

  reply	other threads:[~2015-04-02 11:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CABz95_ATwGVL+dKoO8UWdd=kLOrTt+C7x9U9JsAZXHZaUt4UdQ@mail.gmail.com>
2015-03-31  6:54 ` Kernel panic every other reboot/poweroff since 3.19.3 ( commit 9a6f5130143 ) Daniel Vetter
2015-03-31 16:50   ` Matt Roper
2015-03-31 17:17     ` Steven Honeyman
2015-04-02 11:02       ` Jani Nikula [this message]
2015-04-13 18:36         ` Steven Honeyman

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=87d23mssif.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=airlied@redhat.com \
    --cc=daniel.vetter@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=matthew.d.roper@intel.com \
    --cc=stable@vger.kernel.org \
    --cc=stevenhoneyman@gmail.com \
    /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