From: Dave Airlie <airlied@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
dri-devel <dri-devel@lists.freedesktop.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [git pull] drm for 5.20/6.0
Date: Thu, 4 Aug 2022 13:52:49 +1000 [thread overview]
Message-ID: <CAPM=9txkjJg5uArn1ann7Hf+JFCukQFGwqv+YHAx97Cdxezs_Q@mail.gmail.com> (raw)
In-Reply-To: <CAHk-=wj+yzauNXiEwHfCrkbdLSQkizdR1Q3YJLAqPo6AVq2_4Q@mail.gmail.com>
On Thu, 4 Aug 2022 at 13:47, Linus Torvalds
<torvalds@linux-foundation.org> wrote:
>
> On Wed, Aug 3, 2022 at 8:37 PM Dave Airlie <airlied@gmail.com> wrote:
> >
> > Actually I did miss that so that looks good.
>
> .. I wish it did, but I just actually test-booted my desktop with the
> result, and it crashes the X server. This seems to be the splat in
> Xorg.0.log:
>
> (II) Initializing extension DRI2
> (II) AMDGPU(0): Setting screen physical size to 2032 x 571
> (EE)
> (EE) Backtrace:
> (EE) 0: /usr/libexec/Xorg (OsLookupColor+0x13d) [0x55b1dc61258d]
> (EE) 1: /lib64/libc.so.6 (__sigaction+0x50) [0x7f7972a3ea70]
> (EE) 2: /usr/lib64/xorg/modules/drivers/amdgpu_drv.so
> (AMDGPUCreateWindow_oneshot+0x101) [0x7f797207ddd1]
> (EE) 3: /usr/libexec/Xorg (compIsAlternateVisual+0xdc4) [0x55b1dc545fa4]
> (EE) 4: /usr/libexec/Xorg (InitRootWindow+0x17) [0x55b1dc4e0047]
> (EE) 5: /usr/libexec/Xorg (miPutImage+0xd4c) [0x55b1dc49e60b]
> (EE) 6: /lib64/libc.so.6 (__libc_start_call_main+0x80) [0x7f7972a29550]
> (EE) 7: /lib64/libc.so.6 (__libc_start_main+0x89) [0x7f7972a29609]
> (EE) 8: /usr/libexec/Xorg (_start+0x25) [0x55b1dc49f2c5]
> (EE)
> (EE) Segmentation fault at address 0x4
> (EE)
> Fatal server error:
> (EE) Caught signal 11 (Segmentation fault). Server aborting
>
> so something is going horribly wrong. No kernel oops, though.
>
> It works on my intel laptop, so it's amdgpu somewhere.
I'll spin my ryzen up to see if I can reproduce, and test against the
drm-next pre-merge tree as well.
Dave.
next prev parent reply other threads:[~2022-08-04 3:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-03 5:37 [git pull] drm for 5.20/6.0 Dave Airlie
2022-08-04 2:46 ` Linus Torvalds
2022-08-04 3:16 ` Linus Torvalds
2022-08-04 3:37 ` Dave Airlie
2022-08-04 3:47 ` Linus Torvalds
2022-08-04 3:52 ` Dave Airlie [this message]
2022-08-04 4:02 ` Linus Torvalds
2022-08-04 4:24 ` Dave Airlie
2022-08-04 4:27 ` Linus Torvalds
2022-08-04 4:46 ` Linus Torvalds
2022-08-04 5:25 ` Dave Airlie
2022-08-04 5:52 ` Dave Airlie
2022-08-04 3:17 ` pr-tracker-bot
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='CAPM=9txkjJg5uArn1ann7Hf+JFCukQFGwqv+YHAx97Cdxezs_Q@mail.gmail.com' \
--to=airlied@gmail.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@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 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).