linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Harald Arnesen <harald@skogtun.org>
Cc: Jani Nikula <jani.nikula@linux.intel.com>,
	Pavel Machek <pavel@ucw.cz>, Dave Airlie <airlied@gmail.com>,
	Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
	Rodrigo Vivi <rodrigo.vivi@intel.com>,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	Chris Wilson <chris@chris-wilson.co.uk>,
	Matthew Auld <matthew.auld@intel.com>,
	intel-gfx <intel-gfx@lists.freedesktop.org>,
	kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [Intel-gfx] 5.9-rc1: graphics regression moved from -next to mainline
Date: Wed, 26 Aug 2020 11:04:32 -0700	[thread overview]
Message-ID: <CAHk-=wiAK=AiqTD47o-BFFZciQXpEC0SiiDnXLWJUcQtCo-Pig@mail.gmail.com> (raw)
In-Reply-To: <656b8f9f-d696-c75d-aef6-2b8b5170f2f6@skogtun.org>

On Wed, Aug 26, 2020 at 2:30 AM Harald Arnesen <harald@skogtun.org> wrote:
>
> Somehow related to lightdm or xfce4? However, it is a regression, since
> kernel 5.8 works.

Yeah, apparently there's something else wrong with the relocation changes too.

That said, does that patch at

  https://lore.kernel.org/intel-gfx/20200821123746.16904-1-joro@8bytes.org/

change things at all? If there are two independent bugs, maybe
applying that patch might at least give you an oops that gets saved in
the logs?

(it might be worth waiting a bit after the machine locks up in case
the machine is alive enough so sync logs after a bit.. If ssh works,
that's obviously better yet)

              Linus

  reply	other threads:[~2020-08-26 18:04 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-17 16:11 5.9-rc1: graphics regression moved from -next to mainline Pavel Machek
2020-08-19  0:38 ` Linus Torvalds
2020-08-19  1:12   ` [Intel-gfx] " Dave Airlie
2020-08-19  1:59     ` Linus Torvalds
2020-08-19 16:57       ` Pavel Machek
2020-08-19 20:19       ` Pavel Machek
2020-08-20  9:23       ` Pavel Machek
2020-08-20 16:16         ` Linus Torvalds
2020-08-21  9:19           ` Pavel Machek
2020-08-25  9:55             ` Jani Nikula
2020-08-25 16:31               ` Harald Arnesen
2020-08-25 18:19                 ` Linus Torvalds
2020-08-25 21:38                   ` Harald Arnesen
2020-08-26  8:36                   ` Harald Arnesen
2020-08-26  9:30                     ` Harald Arnesen
2020-08-26 18:04                       ` Linus Torvalds [this message]
2020-08-26 20:44                         ` Harald Arnesen
2020-08-26 20:47                           ` Dave Airlie
2020-08-26 20:53                             ` Harald Arnesen
2020-08-26 20:59                               ` Linus Torvalds
2020-08-27  7:14                                 ` Harald Arnesen
2020-08-27  7:28                                   ` Pavel Machek
2020-09-01 11:57                                 ` Harald Arnesen
2020-09-09  9:15                                   ` Pavel Machek

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='CAHk-=wiAK=AiqTD47o-BFFZciQXpEC0SiiDnXLWJUcQtCo-Pig@mail.gmail.com' \
    --to=torvalds@linux-foundation.org \
    --cc=airlied@gmail.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=daniel.vetter@ffwll.ch \
    --cc=harald@skogtun.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=joonas.lahtinen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew.auld@intel.com \
    --cc=pavel@ucw.cz \
    --cc=rodrigo.vivi@intel.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;
as well as URLs for NNTP newsgroup(s).