mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Christian König" <christian.koenig@amd.com>
To: Thomas Perrot <thomas.perrot@bootlin.com>,
	alexander.deucher@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: amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
	linux-kernel@vger.kernel.org
Subject: Re: Failed to create a rescuer kthread for the amdgpu-reset-dev workqueue
Date: Mon, 15 Jan 2024 11:20:23 +0100	[thread overview]
Message-ID: <8acb0860-1c9d-4fb1-8ec5-ab2104dcb7b7@amd.com> (raw)
In-Reply-To: <d3ffc899948961cd3327db1ad0e59970dcf87bca.camel@bootlin.com>

Am 15.01.24 um 11:17 schrieb Thomas Perrot:
> Hello Christian,
>
> On Fri, 2024-01-12 at 09:17 +0100, Christian König wrote:
>> Well the driver load is interrupted for some reason.
>>
>> Have you set any timeout for modprobe?
>>
> We don't set a modprobe timeout.

Well you somehow abort probing the driver.

This seems to be an external event and not something the driver can 
influence.

Regards,
Christian.

>
> Kind regards,
> Thomas
>
>> Regards,
>> Christian.
>>
>> Am 12.01.24 um 09:11 schrieb Thomas Perrot:
>>> 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
>>>


      reply	other threads:[~2024-01-15 10:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-12  8:11 Thomas Perrot
2024-01-12  8:17 ` Christian König
2024-01-15 10:17   ` Thomas Perrot
2024-01-15 10:20     ` 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=8acb0860-1c9d-4fb1-8ec5-ab2104dcb7b7@amd.com \
    --to=christian.koenig@amd.com \
    --cc=Xinhui.Pan@amd.com \
    --cc=alexander.deucher@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --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 \
    --cc=thomas.perrot@bootlin.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®