All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jörg Rödel" <jroedel@suse.de>
To: Alex Deucher <alexander.deucher@amd.com>,
	christian.koenig@amd.com, Xinhui.Pan@amd.com
Cc: David Airlie <airlied@linux.ie>,
	dri-devel@lists.freedesktop.org, amd-gfx@lists.freedesktop.org,
	Daniel Vetter <daniel@ffwll.ch>,
	linux-kernel@vger.kernel.org
Subject: Re: [BUG] Warning and NULL-ptr dereference in amdgpu driver with 5.18
Date: Fri, 6 May 2022 12:45:04 +0200	[thread overview]
Message-ID: <YnT8MAjb/jW4ENVS@suse.de> (raw)
In-Reply-To: <YnTAc96Uv0CXcGhD@suse.de>

On Fri, May 06, 2022 at 08:30:13AM +0200, Jörg Rödel wrote:
> [81829.087101] ------------[ cut here ]------------
> [81829.087105] WARNING: CPU: 4 PID: 644 at drivers/gpu/drm/amd/amdgpu/../display/dc/clk_mgr/dce110/dce110_clk_mgr.c:140 dce110_fill_display_configs+0x4a/0x150 [amdgpu]

Same just happened with a kernel built from latest upstream, based on
commit fe27d189e3f42e31d3c8223d5daed7285e334c5e. So it's at least not
the iommu changes causing it :)

Please let me know if I can be of any help debugging this further.

Thanks,

	Joerg

WARNING: multiple messages have this Message-ID (diff)
From: "Jörg Rödel" <jroedel@suse.de>
To: Alex Deucher <alexander.deucher@amd.com>,
	christian.koenig@amd.com, Xinhui.Pan@amd.com
Cc: David Airlie <airlied@linux.ie>,
	dri-devel@lists.freedesktop.org, amd-gfx@lists.freedesktop.org,
	linux-kernel@vger.kernel.org
Subject: Re: [BUG] Warning and NULL-ptr dereference in amdgpu driver with 5.18
Date: Fri, 6 May 2022 12:45:04 +0200	[thread overview]
Message-ID: <YnT8MAjb/jW4ENVS@suse.de> (raw)
In-Reply-To: <YnTAc96Uv0CXcGhD@suse.de>

On Fri, May 06, 2022 at 08:30:13AM +0200, Jörg Rödel wrote:
> [81829.087101] ------------[ cut here ]------------
> [81829.087105] WARNING: CPU: 4 PID: 644 at drivers/gpu/drm/amd/amdgpu/../display/dc/clk_mgr/dce110/dce110_clk_mgr.c:140 dce110_fill_display_configs+0x4a/0x150 [amdgpu]

Same just happened with a kernel built from latest upstream, based on
commit fe27d189e3f42e31d3c8223d5daed7285e334c5e. So it's at least not
the iommu changes causing it :)

Please let me know if I can be of any help debugging this further.

Thanks,

	Joerg

WARNING: multiple messages have this Message-ID (diff)
From: "Jörg Rödel" <jroedel@suse.de>
To: Alex Deucher <alexander.deucher@amd.com>,
	christian.koenig@amd.com, Xinhui.Pan@amd.com
Cc: David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
	amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
	linux-kernel@vger.kernel.org
Subject: Re: [BUG] Warning and NULL-ptr dereference in amdgpu driver with 5.18
Date: Fri, 6 May 2022 12:45:04 +0200	[thread overview]
Message-ID: <YnT8MAjb/jW4ENVS@suse.de> (raw)
In-Reply-To: <YnTAc96Uv0CXcGhD@suse.de>

On Fri, May 06, 2022 at 08:30:13AM +0200, Jörg Rödel wrote:
> [81829.087101] ------------[ cut here ]------------
> [81829.087105] WARNING: CPU: 4 PID: 644 at drivers/gpu/drm/amd/amdgpu/../display/dc/clk_mgr/dce110/dce110_clk_mgr.c:140 dce110_fill_display_configs+0x4a/0x150 [amdgpu]

Same just happened with a kernel built from latest upstream, based on
commit fe27d189e3f42e31d3c8223d5daed7285e334c5e. So it's at least not
the iommu changes causing it :)

Please let me know if I can be of any help debugging this further.

Thanks,

	Joerg

  reply	other threads:[~2022-05-06 13:18 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-06  6:30 [BUG] Warning and NULL-ptr dereference in amdgpu driver with 5.18 Jörg Rödel
2022-05-06  6:30 ` Jörg Rödel
2022-05-06  6:30 ` Jörg Rödel
2022-05-06 10:45 ` Jörg Rödel [this message]
2022-05-06 10:45   ` Jörg Rödel
2022-05-06 10:45   ` Jörg Rödel
2022-05-06 13:16 ` Alex Deucher
2022-05-06 13:16   ` Alex Deucher
2022-05-10 11:12   ` Jörg Rödel
2022-05-10 11:12     ` Jörg Rödel
2022-05-10 11:12     ` Jörg Rödel
2022-05-10 15:31     ` Alex Deucher
2022-05-10 15:31       ` Alex Deucher
2022-05-10 15:31       ` Alex Deucher
2022-05-10 18:17       ` Jörg Rödel
2022-05-10 18:17         ` Jörg Rödel
2022-05-10 18:17         ` Jörg Rödel
2022-05-10 20:41         ` Alex Deucher
2022-05-10 20:41           ` Alex Deucher
2022-05-10 20:41           ` Alex Deucher
2022-05-12  8:35           ` Jörg Rödel
2022-05-12  8:35             ` Jörg Rödel
2022-05-12  8:35             ` Jörg Rödel
2022-05-12 13:47             ` Alex Deucher
2022-05-12 13:47               ` Alex Deucher
2022-05-12 13:47               ` Alex Deucher
2022-05-12 18:15               ` Jörg Rödel
2022-05-12 18:15                 ` Jörg Rödel
2022-05-12 18:15                 ` Jörg Rödel

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=YnT8MAjb/jW4ENVS@suse.de \
    --to=jroedel@suse.de \
    --cc=Xinhui.Pan@amd.com \
    --cc=airlied@linux.ie \
    --cc=alexander.deucher@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=christian.koenig@amd.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --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 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.