AMD-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: David McFarland <corngood@gmail.com>
To: amd-gfx@lists.freedesktop.org
Cc: David McFarland <corngood@gmail.com>, mario.limonciello@amd.com
Subject: [PATCH 0/1] amdgpu: Fix crash when MEC2 firmware fails to load
Date: Sun, 28 Jan 2024 12:18:04 -0400	[thread overview]
Message-ID: <20240128161803.1224103-1-corngood@gmail.com> (raw)

I only noticed this because my distro broke the mec2.bin symbolic link, so the
firmware failed to load.  This resulted in:

amdgpu 0000:0b:00.0: Direct firmware load for amdgpu/navi10_mec2.bin failed with error -2
BUG: kernel NULL pointer dereference, address: 0000000000000008
[...]
Call Trace:
 <TASK>
 ? __die+0x23/0x70
 ? page_fault_oops+0x17d/0x4b0
 ? srso_alias_return_thunk+0x5/0xfbef5
 ? exc_page_fault+0x72/0x160
 ? asm_exc_page_fault+0x26/0x30
 ? request_firmware+0x48/0x60 [firmware_class]
 ? amdgpu_gfx_cp_init_microcode+0x22e/0x260 [amdgpu]
 gfx_v10_0_early_init+0x722/0x8d0 [amdgpu]

The attached patch removes some code that looks like it was added by mistake, or
by a bad merge. With it I get still get the load failed error as expected, but
no crash. After fixing the firmware, no error is printed.


David McFarland (1):
  drm/amd: Don't init MEC2 firmware when it fails to load

 drivers/gpu/drm/amd/amdgpu/gfx_v10_0.c | 2 --
 1 file changed, 2 deletions(-)

-- 
2.40.1


             reply	other threads:[~2024-01-29  9:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-28 16:18 David McFarland [this message]
2024-01-28 16:18 ` [PATCH 1/1] drm/amd: Don't init MEC2 firmware when it fails to load David McFarland
2024-01-29 20:46   ` Mario Limonciello
2024-01-29 21:15     ` Mario Limonciello
2024-01-29 22:18       ` [PATCH v2 0/1] " David McFarland
2024-01-29 22:18       ` [PATCH v2 1/1] " David McFarland
2024-01-29 22:21         ` Mario Limonciello

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=20240128161803.1224103-1-corngood@gmail.com \
    --to=corngood@gmail.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=mario.limonciello@amd.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