From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 212311] amdgpu DCN callis sleeping function in illegal context
Date: Wed, 17 Mar 2021 10:50:56 +0000 [thread overview]
Message-ID: <bug-212311-2300-HsqaxJFWvk@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-212311-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=212311
--- Comment #1 from Nirmoy (nirmoy.aiemd@gmail.com) ---
DCN also calls into SMU which can sleep because of mutex_lock(&smu->mutex)
[ 6.547189] amdgpu 0000:44:00.0: amdgpu: SMU is initialized successfully!
[ 6.547217] BUG: sleeping function called from invalid context at
kernel/locking/mutex.c:935
[ 6.547248] in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 581,
name: kworker/6:2
[ 6.547262] 2 locks held by kworker/6:2/581:
[ 6.547264] #0: ffff8906c7c59148 ((wq_completion)events){....}-{0:0}, at:
process_one_work+0x1fb/0x4f0
[ 6.547275] #1: ffffa398447e3e68
((work_completion)(&wfc.work)){....}-{0:0}, at: process_one_work+0x1fb/0x4f0
[ 6.547282] CPU: 6 PID: 581 Comm: kworker/6:2 Tainted: G E
5.11.0-1-default+ #171
[ 6.547285] Hardware name: Gigabyte Technology Co., Ltd. X399 DESIGNARE
EX/X399 DESIGNARE EX-CF, BIOS F12i 09/24/2019
[ 6.547287] Workqueue: events work_for_cpu_fn
[ 6.547291] Call Trace:
[ 6.547296] dump_stack+0x6b/0x83
[ 6.547300] ___might_sleep.cold+0xa7/0xb7
[ 6.547305] ? smu_get_max_sustainable_clocks_by_dc+0x38/0x80 [amdgpu]
[ 6.547494] __mutex_lock+0x45/0x8c0
[ 6.547500] ? ___slab_alloc+0x42d/0x640
[ 6.547505] smu_get_max_sustainable_clocks_by_dc+0x38/0x80 [amdgpu]
[ 6.547654] pp_nv_get_maximum_sustainable_clocks+0x2f/0x50 [amdgpu]
[ 6.547810] init_soc_bounding_box+0x111/0x200 [amdgpu]
[ 6.547975] dcn20_resource_construct+0x440/0xd30 [amdgpu]
[ 6.548134] ? fs_reclaim_release+0x46/0x80
[ 6.548138] ? dcn20_create_resource_pool+0x25/0x80 [amdgpu]
[ 6.548294] ? kmem_cache_alloc_trace+0x1a4/0x360
[ 6.548296] ? __kmalloc+0x1c1/0x3c0
[ 6.548301] dcn20_create_resource_pool+0x3c/0x80 [amdgpu]
[ 6.548457] dc_create_resource_pool+0x13f/0x1d0 [amdgpu]
[ 6.548611] dc_create+0x203/0x7b0 [amdgpu]
[ 6.548768] amdgpu_dm_init.isra.0+0x1de/0x270 [amdgpu]
[ 6.548923] ? dev_vprintk_emit+0x12c/0x150
[ 6.548931] ? dev_printk_emit+0x4e/0x65
[ 6.548941] dm_hw_init+0xe/0x20 [amdgpu]
[ 6.549094] amdgpu_device_init.cold+0x13e6/0x17ad [amdgpu]
[ 6.549248] ? pci_bus_read_config_word+0x49/0x70
[ 6.549254] amdgpu_driver_load_kms+0x64/0x260 [amdgpu]
[ 6.549376] amdgpu_pci_probe+0x122/0x1b0 [amdgpu]
[ 6.549497] local_pci_probe+0x42/0x80
[ 6.549501] work_for_cpu_fn+0x16/0x20
[ 6.549503] process_one_work+0x28c/0x4f0
[ 6.549509] worker_thread+0x20d/0x3f0
[ 6.549512] ? rescuer_thread+0x390/0x390
[ 6.549515] kthread+0x13a/0x150
[ 6.549517] ? __kthread_bind_mask+0x60/0x60
[ 6.549521] ret_from_fork+0x22/0x30
[ 6.549969] [drm] Display Core initialized with v3.2.127!
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2021-03-17 10:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-17 10:46 [Bug 212311] New: amdgpu DCN callis sleeping function in illegal context bugzilla-daemon
2021-03-17 10:50 ` bugzilla-daemon [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=bug-212311-2300-HsqaxJFWvk@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.freedesktop.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.