From: Greg KH <gregkh@linuxfoundation.org>
To: Mike Galbraith <efault@gmx.de>
Cc: Ray Strode <rstrode@redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
stable <stable@vger.kernel.org>,
virtualization@lists.linux-foundation.org,
Dave Airlie <airlied@redhat.com>
Subject: Re: v4.14.21+: ATOMIC_SLEEP splat bisected to 9428088c90b6 ("drm/qxl: reapply cursor after resetting primary")
Date: Sun, 17 Jun 2018 11:36:07 +0200 [thread overview]
Message-ID: <20180617093607.GA27652@kroah.com> (raw)
In-Reply-To: <1529163551.16103.16.camel@gmx.de>
On Sat, Jun 16, 2018 at 05:39:11PM +0200, Mike Galbraith wrote:
> Greetings,
>
> Running a kernel with ATOMIC_SLEEP enabled in one of my VMs, I met the
> splat below. I tracked it back to 4.14-stable, and bisected it there.
Why does your virtual machine use a drm driver? Ah, it's a driver for
virtual gpu, nice.
And if you revert that patch, does everything work again?
> # first bad commit: [848dd9bf51544c8e5436960124f3d1f9c51cdb99] drm/qxl: reapply cursor after resetting primary
You should also cc: the other developers on that signed-off-by list,
like I did here...
thanks,
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh@linuxfoundation.org>
To: Mike Galbraith <efault@gmx.de>
Cc: Ray Strode <rstrode@redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
stable <stable@vger.kernel.org>,
Gerd Hoffmann <kraxel@redhat.com>,
Dave Airlie <airlied@redhat.com>,
virtualization@lists.linux-foundation.org
Subject: Re: v4.14.21+: ATOMIC_SLEEP splat bisected to 9428088c90b6 ("drm/qxl: reapply cursor after resetting primary")
Date: Sun, 17 Jun 2018 11:36:07 +0200 [thread overview]
Message-ID: <20180617093607.GA27652@kroah.com> (raw)
In-Reply-To: <1529163551.16103.16.camel@gmx.de>
On Sat, Jun 16, 2018 at 05:39:11PM +0200, Mike Galbraith wrote:
> Greetings,
>
> Running a kernel with ATOMIC_SLEEP enabled in one of my VMs, I met the
> splat below. I tracked it back to 4.14-stable, and bisected it there.
Why does your virtual machine use a drm driver? Ah, it's a driver for
virtual gpu, nice.
And if you revert that patch, does everything work again?
> # first bad commit: [848dd9bf51544c8e5436960124f3d1f9c51cdb99] drm/qxl: reapply cursor after resetting primary
You should also cc: the other developers on that signed-off-by list,
like I did here...
thanks,
greg k-h
next prev parent reply other threads:[~2018-06-17 9:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-16 15:39 v4.14.21+: ATOMIC_SLEEP splat bisected to 9428088c90b6 ("drm/qxl: reapply cursor after resetting primary") Mike Galbraith
2018-06-17 9:36 ` Greg KH [this message]
2018-06-17 9:36 ` Greg KH
2018-06-17 10:38 ` Mike Galbraith
2018-06-17 10:38 ` Mike Galbraith
2018-06-17 11:02 ` Greg KH
2018-06-17 11:02 ` Greg KH
2018-06-18 2:33 ` Dave Airlie
2018-06-18 2:33 ` Dave Airlie
2018-06-18 3:13 ` Mike Galbraith
2018-06-18 3:13 ` Mike Galbraith
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=20180617093607.GA27652@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=airlied@redhat.com \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rstrode@redhat.com \
--cc=stable@vger.kernel.org \
--cc=virtualization@lists.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 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.