mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Perrot <thomas.perrot@bootlin.com>
To: alexander.deucher@amd.com, christian.koenig@amd.com,
	Xinhui.Pan@amd.com, lijo.lazar@amd.com, kenneth.feng@amd.com,
	guchun.chen@amd.com, evan.quan@amd.com,
	 srinivasan.shanmugam@amd.com
Cc: Thomas Perrot <thomas.perrot@bootlin.com>,
	amd-gfx@lists.freedesktop.org,  dri-devel@lists.freedesktop.org,
	linux-kernel@vger.kernel.org
Subject: Failed to create a rescuer kthread for the amdgpu-reset-dev workqueue
Date: Fri, 12 Jan 2024 09:11:32 +0100	[thread overview]
Message-ID: <cf1a3a2b7599b7b6900ff45aa8b204169411687f.camel@bootlin.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 761 bytes --]

Hello,

We are updating the kernel from the 6.1 to the 6.6 and we observe an
amdgpu’s regression with Radeon RX580 8GB and SiFive Unmatched:
“workqueue: Failed to create a rescuer kthread for wq 'amdgpu-reset-
dev': -EINTR
[drm:amdgpu_reset_create_reset_domain [amdgpu]] *ERROR* Failed to
allocate wq for amdgpu_reset_domain!
amdgpu 0000:07:00.0: amdgpu: Fatal error during GPU init
amdgpu 0000:07:00.0: amdgpu: amdgpu: finishing device.
amdgpu: probe of 0000:07:00.0 failed with error -12”

We tried to figure it out without success for the moment, do you have
some advice to identify the root cause and to fix it?

Kind regards,
Thomas Perrot

-- 
Thomas Perrot, Bootlin
Embedded Linux and kernel engineering
https://bootlin.com


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 659 bytes --]

             reply	other threads:[~2024-01-12  8:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-12  8:11 Thomas Perrot [this message]
2024-01-12  8:17 ` Christian König
2024-01-15 10:17   ` Thomas Perrot
2024-01-15 10:20     ` Christian König

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=cf1a3a2b7599b7b6900ff45aa8b204169411687f.camel@bootlin.com \
    --to=thomas.perrot@bootlin.com \
    --cc=Xinhui.Pan@amd.com \
    --cc=alexander.deucher@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=christian.koenig@amd.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=evan.quan@amd.com \
    --cc=guchun.chen@amd.com \
    --cc=kenneth.feng@amd.com \
    --cc=lijo.lazar@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=srinivasan.shanmugam@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

all inboxes | Powered by JetHome®