Displaying 4 results from an estimated 4 matches for "gk104_fifo_recover_work".
Did you mean:
gf100_fifo_recover_work
2016 Jul 21
2
[Bug 97021] New: Screen locks up randomly while only mouse pointer moves, system responsive via ssh
...(E) 8139cp(E)
r8169(E) ahci(E) pata_atiixp(E) mii(E) libahci(E) drm(E) wmi(E)
[ 4036.404204] CPU: 4 PID: 6743 Comm: kworker/4:1 Tainted: G OE
4.5.3 #1
[ 4036.404206] Hardware name: Gigabyte Technology Co., Ltd.
GA-970A-DS3/GA-970A-DS3, BIOS F6 10/23/2012
[ 4036.404269] Workqueue: events gk104_fifo_recover_work [nouveau]
[ 4036.404272] task: ffff8801fd3e5b00 ti: ffff88006e148000 task.ti:
ffff88006e148000
[ 4036.404274] RIP: 0010:[<ffffffffc0241d95>] [<ffffffffc0241d95>]
gk104_fifo_recover_work+0x95/0x280 [nouveau]
[ 4036.404319] RSP: 0018:ffff88006e14bde0 EFLAGS: 00000206
[ 4036.404322] RAX:...
2013 Sep 27
25
[Bug 69882] New: [NVE6] GPU lockups
https://bugs.freedesktop.org/show_bug.cgi?id=69882
Priority: medium
Bug ID: 69882
Assignee: nouveau at lists.freedesktop.org
Summary: [NVE6] GPU lockups
QA Contact: xorg-team at lists.x.org
Severity: critical
Classification: Unclassified
OS: Linux (All)
Reporter: pastas4 at gmail.com
Hardware:
2020 Oct 07
0
[RFC] fifo: only reboot engines if they have a ref
...k104.c | 8 ++++++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/drm/nouveau/nvkm/engine/fifo/gk104.c b/drm/nouveau/nvkm/engine/fifo/gk104.c
index 441483325..669153fba 100644
--- a/drm/nouveau/nvkm/engine/fifo/gk104.c
+++ b/drm/nouveau/nvkm/engine/fifo/gk104.c
@@ -292,8 +292,12 @@ gk104_fifo_recover_work(struct work_struct *w)
for (todo = engm; engn = __ffs(todo), todo; todo &= ~BIT(engn)) {
if ((engine = fifo->engine[engn].engine)) {
- nvkm_subdev_fini(&engine->subdev, false);
- WARN_ON(nvkm_subdev_init(&engine->subdev));
+ mutex_lock(&engine->subdev.mutex)...
2019 Sep 23
8
[PATCH 0/8] Add workaround for fixing runpm
Changes since last sent:
* add a patch to set the device into DRM_SWITCH_POWER_CHANGING state
(can be dropped actually, I thought I was needing it, came up with a
different approach and forgot to delete it, doesn't hurt though)
* expose information about runtime suspending to nvkm so that we can run
the pcie workaround only on runtime suspend
Karol Herbst (8):
pci: disable ASPM