All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Deucher <alexdeucher@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Dave Airlie <airlied@gmail.com>,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	LKML <linux-kernel@vger.kernel.org>,
	dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [git pull] drm for 5.11-rc1
Date: Mon, 14 Dec 2020 17:28:48 -0500	[thread overview]
Message-ID: <CADnq5_MyMm+FmmbKHccDDOBryEdgbQHdw3rtuhUv=cvJrirHFg@mail.gmail.com> (raw)
In-Reply-To: <CAHk-=wjue4aOyQQq+C6SEurwe6XABhMyNtsfn1goU==Hf_QUqA@mail.gmail.com>

On Mon, Dec 14, 2020 at 5:21 PM Linus Torvalds
<torvalds@linux-foundation.org> wrote:
>
> On Thu, Dec 10, 2020 at 7:52 PM Dave Airlie <airlied@gmail.com> wrote:
> >
> > This is an early pull request for drm for 5.11 merge window. I'm going
> > to be out for most of the first week of the merge window so thought
> > I'd just preempt things and send this early.
>
> Ok, I've merged this, and Dave is likely gone already, but it _looks_
> like there's a problem with the drm tree on my Radeon workstation.
>
> It works fine on my i915 laptop.
>
> The symptoms are that the boot just hangs after
>
>    fb0: switching to amdgpudrmfb from EFI VGA
>
> when on a working kernel the next lines are
>
>   amdgpu 0000:49:00.0: vgaarb: deactivate vga console
>   [drm] initializing kernel modesetting (POLARIS10 0x1002:0x67DF
> 0x1DA2:0xE353 0xE7).
>   amdgpu 0000:49:00.0: amdgpu: Trusted Memory Zone (TMZ) feature not supported
>   [drm] register mmio base: 0xE1C00000
>   [drm] register mmio size: 262144
>
> I'm bisecting for more details, but it might take a while, and I
> thought I'd start the ball rolling with this initial report in case
> somebody goes "Aahh.., we know about that case already, the fix is
> XYZ"...
>

The relevant fixes are:
https://cgit.freedesktop.org/drm/drm-misc/commit/?h=drm-misc-next-fixes&id=aefec40938e4a0e1214f9121520aba4d51697cd9
https://cgit.freedesktop.org/drm/drm-misc/commit/?h=drm-misc-next-fixes&id=95e3d610d35c9c5b51e12c5c8ac18061ae08cf97

Alex



>               Linus
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel

WARNING: multiple messages have this Message-ID (diff)
From: Alex Deucher <alexdeucher@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	LKML <linux-kernel@vger.kernel.org>,
	dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [git pull] drm for 5.11-rc1
Date: Mon, 14 Dec 2020 17:28:48 -0500	[thread overview]
Message-ID: <CADnq5_MyMm+FmmbKHccDDOBryEdgbQHdw3rtuhUv=cvJrirHFg@mail.gmail.com> (raw)
In-Reply-To: <CAHk-=wjue4aOyQQq+C6SEurwe6XABhMyNtsfn1goU==Hf_QUqA@mail.gmail.com>

On Mon, Dec 14, 2020 at 5:21 PM Linus Torvalds
<torvalds@linux-foundation.org> wrote:
>
> On Thu, Dec 10, 2020 at 7:52 PM Dave Airlie <airlied@gmail.com> wrote:
> >
> > This is an early pull request for drm for 5.11 merge window. I'm going
> > to be out for most of the first week of the merge window so thought
> > I'd just preempt things and send this early.
>
> Ok, I've merged this, and Dave is likely gone already, but it _looks_
> like there's a problem with the drm tree on my Radeon workstation.
>
> It works fine on my i915 laptop.
>
> The symptoms are that the boot just hangs after
>
>    fb0: switching to amdgpudrmfb from EFI VGA
>
> when on a working kernel the next lines are
>
>   amdgpu 0000:49:00.0: vgaarb: deactivate vga console
>   [drm] initializing kernel modesetting (POLARIS10 0x1002:0x67DF
> 0x1DA2:0xE353 0xE7).
>   amdgpu 0000:49:00.0: amdgpu: Trusted Memory Zone (TMZ) feature not supported
>   [drm] register mmio base: 0xE1C00000
>   [drm] register mmio size: 262144
>
> I'm bisecting for more details, but it might take a while, and I
> thought I'd start the ball rolling with this initial report in case
> somebody goes "Aahh.., we know about that case already, the fix is
> XYZ"...
>

The relevant fixes are:
https://cgit.freedesktop.org/drm/drm-misc/commit/?h=drm-misc-next-fixes&id=aefec40938e4a0e1214f9121520aba4d51697cd9
https://cgit.freedesktop.org/drm/drm-misc/commit/?h=drm-misc-next-fixes&id=95e3d610d35c9c5b51e12c5c8ac18061ae08cf97

Alex



>               Linus
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2020-12-14 22:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-11  3:52 [git pull] drm for 5.11-rc1 Dave Airlie
2020-12-11  3:52 ` Dave Airlie
2020-12-14 19:51 ` pr-tracker-bot
2020-12-14 19:51   ` pr-tracker-bot
2020-12-14 22:21 ` Linus Torvalds
2020-12-14 22:21   ` Linus Torvalds
2020-12-14 22:28   ` Alex Deucher [this message]
2020-12-14 22:28     ` Alex Deucher
2020-12-14 22:45     ` Linus Torvalds
2020-12-14 22:45       ` Linus Torvalds
2020-12-14 22:55       ` Alex Deucher
2020-12-14 22:55         ` Alex Deucher

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='CADnq5_MyMm+FmmbKHccDDOBryEdgbQHdw3rtuhUv=cvJrirHFg@mail.gmail.com' \
    --to=alexdeucher@gmail.com \
    --cc=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 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.