public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Christian König" <ckoenig.leichtzumerken@gmail.com>
To: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>
Cc: "amd-gfx list" <amd-gfx@lists.freedesktop.org>,
	"Linux List Kernel Mailing" <linux-kernel@vger.kernel.org>,
	"Dave Airlie" <airlied@gmail.com>,
	"Christian König" <christian.koenig@amd.com>
Subject: Re: Unexpected multihop in swaput - likely driver bug.
Date: Mon, 12 Apr 2021 13:11:06 +0200	[thread overview]
Message-ID: <b2d8efbd-3e2a-eff3-23e7-b620ea584082@gmail.com> (raw)
In-Reply-To: <CABXGCsN6GX4ksbFo9fhd6XGxNyED9qoBqYf0Ph1pwG3qArGtjg@mail.gmail.com>

Hi Mikhail,

thanks a lot for pointing this out.

Turned out that this is a known issue, but I've forgot to push the fix 
to drm-misc-fixes and just queued it up for the next release.

Please re-test drm-misc-fixes and let's hope there is another -rc before 
the final 5.12 kernel.

Thanks,
Christian.

Am 07.04.21 um 20:06 schrieb Mikhail Gavrilov:
> On Wed, 7 Apr 2021 at 15:46, Christian König
> <ckoenig.leichtzumerken@gmail.com> wrote:
>> What hardware are you using
> $ inxi -bM
> System:    Host: fedora Kernel: 5.12.0-0.rc6.184.fc35.x86_64+debug
> x86_64 bits: 64 Desktop: GNOME 40.0
>             Distro: Fedora release 35 (Rawhide)
> Machine:   Type: Desktop Mobo: ASUSTeK model: ROG STRIX X570-I GAMING
> v: Rev X.0x serial: <superuser required>
>             UEFI: American Megatrends v: 3603 date: 03/20/2021
> Battery:   ID-1: hidpp_battery_0 charge: N/A condition: N/A
> CPU:       Info: 16-Core (2-Die) AMD Ryzen 9 3950X [MT MCP MCM] speed:
> 2365 MHz min/max: 2200/3500 MHz
> Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] Navi 21 [Radeon
> RX 6800/6800 XT / 6900 XT] driver: amdgpu v: kernel
>             Device-2: AVerMedia Live Streamer CAM 513 type: USB driver:
> hid-generic,usbhid,uvcvideo
>             Device-3: AVerMedia Live Gamer Ultra-Video type: USB
> driver: hid-generic,snd-usb-audio,usbhid,uvcvideo
>             Display: wayland server: X.Org 1.21.1 driver: loaded:
> amdgpu,ati unloaded: fbdev,modesetting,radeon,vesa
>             resolution: 3840x2160~60Hz
>             OpenGL: renderer: AMD SIENNA_CICHLID (DRM 3.40.0
> 5.12.0-0.rc6.184.fc35.x86_64+debug LLVM 12.0.0)
>             v: 4.6 Mesa 21.1.0-devel
> Network:   Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi
>             Device-2: Intel I211 Gigabit Network driver: igb
> Drives:    Local Storage: total: 11.35 TiB used: 10.82 TiB (95.3%)
> Info:      Processes: 805 Uptime: 12h 56m Memory: 31.18 GiB used:
> 21.88 GiB (70.2%) Shell: Bash inxi: 3.3.02
>
>
>> and how do you exactly trigger this?
> I am running heavy games like "Zombie Army 4: Dead War" and switching
> to Gnome Activities and other applications while the game is running.
>
>


      reply	other threads:[~2021-04-12 11:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-07  9:30 Unexpected multihop in swaput - likely driver bug Mikhail Gavrilov
2021-04-07 10:46 ` Christian König
2021-04-07 18:06   ` Mikhail Gavrilov
2021-04-12 11:11     ` Christian König [this message]

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=b2d8efbd-3e2a-eff3-23e7-b620ea584082@gmail.com \
    --to=ckoenig.leichtzumerken@gmail.com \
    --cc=airlied@gmail.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=christian.koenig@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikhail.v.gavrilov@gmail.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