All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jaak Ristioja <jaak@ristioja.ee>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: David Airlie <airlied@linux.ie>,
	linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
	virtualization@lists.linux-foundation.org,
	Daniel Vetter <daniel@ffwll.ch>,
	spice-devel@lists.freedesktop.org,
	Dave Airlie <airlied@redhat.com>
Subject: Re: Xorg indefinitely hangs in kernelspace
Date: Thu, 5 Sep 2019 15:34:12 +0300	[thread overview]
Message-ID: <e4b7d889-15f3-0c90-3b9f-d395344499c0__39110.6557844736$1567686861$gmane$org@ristioja.ee> (raw)
In-Reply-To: <20190905071407.47iywqcqomizs3yr@sirius.home.kraxel.org>

On 05.09.19 10:14, Gerd Hoffmann wrote:
> On Tue, Aug 06, 2019 at 09:00:10PM +0300, Jaak Ristioja wrote:
>> Hello!
>>
>> I'm writing to report a crash in the QXL / DRM code in the Linux kernel.
>> I originally filed the issue on LaunchPad and more details can be found
>> there, although I doubt whether these details are useful.
> 
> Any change with kernel 5.3-rc7 ?

Didn't try. Did you change something? I could try, but I've done so
before and every time this bug manifests itself with MAJOR.MINOR-rc# I
get asked to try version MAJOR.(MINOR+1)-rc# so I guess I could as well
give up?

Alright, I'll install 5.3-rc7, but once more it might take some time for
this bug to expose itself.

One thing to note though, is that this occurred much more often with
older kernels (or older versions of the Kubuntu desktop/Firefox in my
VM), sometimes even several times in an hour of use.


Best regards,
J

  reply	other threads:[~2019-09-05 12:34 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-06 18:00 Xorg indefinitely hangs in kernelspace Jaak Ristioja
2019-09-05  7:14 ` Gerd Hoffmann
2019-09-05  7:14   ` Gerd Hoffmann
2019-09-05 12:34   ` Jaak Ristioja [this message]
2019-09-05 12:34   ` Jaak Ristioja
2019-09-24  9:12     ` Jaak Ristioja
2019-09-24  9:12     ` Jaak Ristioja
2019-09-30 13:29       ` [Spice-devel] " Frediano Ziglio
2019-09-30 13:29       ` Frediano Ziglio
2019-09-30 13:29         ` Frediano Ziglio
2019-10-03  6:45         ` Jaak Ristioja
2019-10-03  6:45         ` Jaak Ristioja
2019-10-03  8:23         ` Hillf Danton
2019-09-05  7:14 ` Gerd Hoffmann
2019-09-06  5:53 Hillf Danton
2019-09-06 20:27 ` [Spice-devel] " Frediano Ziglio
2019-09-07  2:00   ` Hillf Danton
2019-09-09  5:52 ` Gerd Hoffmann
2019-09-09  5:52   ` Gerd Hoffmann
2019-09-09  7:13   ` Hillf Danton
2019-09-09  7:13   ` Hillf Danton
2019-09-09  7:13   ` Hillf Danton
2019-09-09 12:12 Hillf Danton

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='e4b7d889-15f3-0c90-3b9f-d395344499c0__39110.6557844736$1567686861$gmane$org@ristioja.ee' \
    --to=jaak@ristioja.ee \
    --cc=airlied@linux.ie \
    --cc=airlied@redhat.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=kraxel@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=spice-devel@lists.freedesktop.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.