Message ID | CAPM=9tyNrbap4FG6qstkC5YTznqVebD=ye+4+Z+t42yQnL325A@mail.gmail.com (mailing list archive) |
---|---|
State | New, archived |
Headers | show |
Series | [git,pull] drm for 5.11-rc1 | expand |
The pull request you sent on Fri, 11 Dec 2020 13:52:21 +1000:
> git://anongit.freedesktop.org/drm/drm tags/drm-next-2020-12-11
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/1d36dffa5d887715dacca0f717f4519b7be5e498
Thank you!
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"... Linus
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
On Mon, Dec 14, 2020 at 2:29 PM Alex Deucher <alexdeucher@gmail.com> wrote: > > The relevant fixes are: Ok, I can confirm that applying those two patches gets my workstation working properly again. Would it be possible to get those submitted properly (or I can just take them as-is, but would like to get a "please just pick them directly")? I don't like to continue to do merges during the merge windows with a known broken base - it makes for a nightmare of bisection when you have multiple independent problems, and I assume this hits not just me but a lot of people with radeon/amdgpu graphics? Linus
On Mon, Dec 14, 2020 at 5:45 PM Linus Torvalds <torvalds@linux-foundation.org> wrote: > > On Mon, Dec 14, 2020 at 2:29 PM Alex Deucher <alexdeucher@gmail.com> wrote: > > > > The relevant fixes are: > > Ok, I can confirm that applying those two patches gets my workstation > working properly again. > > Would it be possible to get those submitted properly (or I can just > take them as-is, but would like to get a "please just pick them > directly")? > > I don't like to continue to do merges during the merge windows with a > known broken base - it makes for a nightmare of bisection when you > have multiple independent problems, and I assume this hits not just me > but a lot of people with radeon/amdgpu graphics? Yes, anyone using AMD GPUs will be affected. The patches are already in drm-misc, so they should show up in the next drm -fixes PR, but I think it would be fine to pick them directly to fix support for everyone using your tree. Alex