From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 208135] AMDGPU sleep with preemption disabled
Date: Thu, 11 Jun 2020 03:31:31 +0000 [thread overview]
Message-ID: <bug-208135-2300-i1XTT9ZjlX@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-208135-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=208135
--- Comment #2 from yshuiv7@gmail.com ---
And another one:
[ 2.071364] BUG: sleeping function called from invalid context at
mm/slab.h:567
[ 2.071379] in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 1, name:
swapper/0
[ 2.071393] 1 lock held by swapper/0/1:
[ 2.071402] #0: ffff953e072b7228 (&dev->mutex){....}-{3:3}, at:
device_driver_attach+0x48/0xc0
[ 2.071422] Preemption disabled at:
[ 2.071424] [<ffffffffb8a7ff2e>] kernel_fpu_begin+0xe/0x70
[ 2.071443] CPU: 18 PID: 1 Comm: swapper/0 Tainted: G T
5.7.2-local+ #17
[ 2.071458] Hardware name: System manufacturer System Product Name/ROG STRIX
X470-F GAMING, BIOS 5406 11/13/2019
[ 2.071476] Call Trace:
[ 2.071485] show_stack+0x3e/0x40
[ 2.071494] dump_stack+0x7a/0xaa
[ 2.071504] ___might_sleep.cold+0xfa/0x10b
[ 2.071515] __might_sleep+0x50/0x90
[ 2.071526] kmem_cache_alloc_trace+0x1b1/0x200
[ 2.071536] ? dccg2_create+0x3a/0x70
[ 2.071546] dccg2_create+0x3a/0x70
[ 2.071556] dcn20_resource_construct+0x2e2/0xb00
[ 2.071567] ? rcu_read_lock_sched_held+0x5a/0xa0
[ 2.071578] ? trace_kmalloc+0x105/0x130
[ 2.071589] ? kmem_cache_alloc_trace+0xec/0x200
[ 2.071600] dcn20_create_resource_pool+0x47/0x70
[ 2.071612] dc_create_resource_pool+0x142/0x170
[ 2.071622] ? dal_gpio_service_create+0x98/0x120
[ 2.071633] dc_construct+0x1b1/0x360
[ 2.071644] dc_create+0x48/0x120
[ 2.071653] amdgpu_dm_init.isra.0+0x155/0x1b0
[ 2.071669] dm_hw_init+0xe/0x20
[ 2.071678] amdgpu_device_ip_init+0x2b5/0x33e
[ 2.071690] amdgpu_device_init.cold+0x74f/0x9f3
[ 2.071701] amdgpu_driver_load_kms+0x51/0x180
[ 2.071711] amdgpu_pci_probe+0xbb/0x140
[ 2.071722] pci_device_probe+0xf2/0x160
[ 2.071733] really_probe+0xf5/0x420
[ 2.071743] driver_probe_device+0xc2/0x110
[ 2.071754] device_driver_attach+0xb9/0xc0
[ 2.071764] __driver_attach+0x94/0x150
[ 2.071774] ? device_driver_attach+0xc0/0xc0
[ 2.071784] bus_for_each_dev+0x6b/0xa0
[ 2.071794] driver_attach+0x19/0x20
[ 2.071803] bus_add_driver+0x149/0x200
[ 2.071813] driver_register+0x8c/0xe0
[ 2.071823] __pci_register_driver+0x6b/0x80
[ 2.071834] amdgpu_init+0x9c/0xbc
[ 2.071842] ? drm_sched_fence_slab_init+0x7e/0x7e
[ 2.071853] do_one_initcall+0x5c/0x330
[ 2.071863] ? rcu_read_lock_sched_held+0x5a/0xa0
[ 2.071876] do_initcalls+0x104/0x162
[ 2.071886] kernel_init_freeable+0x193/0x235
[ 2.071897] ? rest_init+0x241/0x241
[ 2.071906] kernel_init+0x9/0xff
[ 2.071914] ret_from_fork+0x27/0x50
--
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:[~2020-06-11 3:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-11 3:08 [Bug 208135] New: AMDGPU sleep with preemption disabled bugzilla-daemon
2020-06-11 3:29 ` [Bug 208135] " bugzilla-daemon
2020-06-11 3:31 ` 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-208135-2300-i1XTT9ZjlX@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.