From: "Skyler Mäntysaari" <lists@samip.fi>
To: "Kari Argillander" <kari.argillander@gmail.com>
Cc: linux-kernel@vger.kernel.org, amd-gfx@lists.freedesktop.org
Subject: Re: [drm/amdgpu] Driver crashes on 5.13.9 kernel
Date: Mon, 30 Aug 2021 19:15:29 +0300 [thread overview]
Message-ID: <4d3fd1cb-9b33-4598-b351-54ea455c2a6e@www.fastmail.com> (raw)
In-Reply-To: <20210829173448.3cwk4rz6wfxfxdpj@kari-VirtualBox>
I have tried kernel 5.13.13, without any difference and I haven't tried with an older kernel, as this hardware is that new that I have very little faith in less than 5.x kernel would even have support for the needed GPU.
What do you mean with git bisect? I have checked that the crash happens somewhere in the monitor connection code:
[ 9605.269927] Call Trace:
[ 9605.269931] core_link_enable_stream+0x746/0x870 [amdgpu]
[ 9605.270038] dce110_apply_ctx_to_hw+0x519/0x560 [amdgpu]
[ 9605.270146] dc_commit_state+0x2f6/0xa50 [amdgpu]
[ 9605.270249] amdgpu_dm_atomic_commit_tail+0x569/0x26a0 [amdgpu]
[ 9605.270326] ? kfree+0xc3/0x460
[ 9605.270329] ? dcn30_validate_bandwidth+0x11f/0x270 [amdgpu]
[ 9605.270402] ? dcn30_validate_bandwidth+0x11f/0x270 [amdgpu]
[ 9605.270469] ? dm_plane_helper_prepare_fb+0x19c/0x250 [amdgpu]
[ 9605.270542] ? __cond_resched+0x16/0x40
[ 9605.270544] ? __wait_for_common+0x3b/0x160
[ 9605.270545] ? __raw_callee_save___native_queued_spin_unlock+0x11/0x1e
[ 9605.270548] commit_tail+0x94/0x130 [drm_kms_helper]
[ 9605.270557] drm_atomic_helper_commit+0x113/0x140 [drm_kms_helper]
[ 9605.270562] drm_atomic_helper_set_config+0x70/0xb0 [drm_kms_helper]
[ 9605.270568] drm_mode_setcrtc+0x1d3/0x6d0 [drm]
[ 9605.270582] ? drm_mode_getcrtc+0x180/0x180 [drm]
[ 9605.270590] drm_ioctl_kernel+0xaa/0xf0 [drm]
[ 9605.270600] drm_ioctl+0x220/0x3c0 [drm]
[ 9605.270609] ? drm_mode_getcrtc+0x180/0x180 [drm]
[ 9605.270618] amdgpu_drm_ioctl+0x49/0x80 [amdgpu]
[ 9605.270673] __x64_sys_ioctl+0x83/0xb0
[ 9605.270675] do_syscall_64+0x40/0xb0
[ 9605.270677] entry_SYSCALL_64_after_hwframe+0x44/0xae
On Sun, Aug 29, 2021, at 20:34, Kari Argillander wrote:
> On Sun, Aug 29, 2021 at 06:38:39PM +0300, Skyler Mäntysaari wrote:
> > Hello everyone on the list,
>
> This is universal kernel list and it is not read by many. I have added
> hopefully right list (amd-gfx@lists.freedesktop.org).
>
> > Subject: Re: [drm/amdgpu] Driver crashes on 5.13.9 kernel
>
> I have no influence or knowledge about this driver, but I still try to
> help because it seems good bug report. Have you test with 5.13.13 or
> 5.14-rc7. Does this work with some other kernel? If needed can you git
> bisect if needed? You will probably get some support for it if needed.
>
> Argillander
>
> > I thought that this should probably be discussed here, so I came
> > across weird issue to me which is driver crashing while trying to get
> > one of my monitors working on Gentoo. I would like to ask here how
> > that would happen that the Display appears to jump from DisplayPort-6
> > (physical port) to DisplayPort-7 (which doesn't exist physically)? Has
> > anyone else experienced this?
> >
> > It seems that the driver sees a rather large amount of inputs for the
> > GPU, even though I only have 4, 3 of which are DisplayPort, and the
> > issue monitor is also on DisplayPort.
> >
> > Hardware:
> > CPU: AMD Ryzen 5800X
> > GPU: AMD Radeon RX 6800
> > System Memory: 32GB of DDR4 3200Mhz
> > Display(s): BenQ Zowie XL2430 (1080p), DELL U2414H (1080p), DELL U2415 (1920x1200)
> > Type of Diplay Connection: All are connected via Display-Port
> >
> > Related DRM issue:
> > https://gitlab.freedesktop.org/drm/amd/-/issues/1621 which includes
> > logs too.
> >
> >
> > Best regards,
> > Skyler Mäntysaari
next prev parent reply other threads:[~2021-08-30 16:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-29 15:38 Skyler Mäntysaari
2021-08-29 17:34 ` Kari Argillander
2021-08-30 16:15 ` Skyler Mäntysaari [this message]
2021-08-30 17:21 ` Kari Argillander
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=4d3fd1cb-9b33-4598-b351-54ea455c2a6e@www.fastmail.com \
--to=lists@samip.fi \
--cc=amd-gfx@lists.freedesktop.org \
--cc=kari.argillander@gmail.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®