All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 203033] nouveau hung task
Date: Tue, 08 Nov 2022 18:23:28 +0000	[thread overview]
Message-ID: <bug-203033-2300-WuA150pj3w@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-203033-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=203033

Murph (murph@clurictec.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |murph@clurictec.com

--- Comment #6 from Murph (murph@clurictec.com) ---
Having a similar issue here. GUI locks up but system is still running in the
background (meetings can still see and hear me, I can hear them). Can't switch
to different tty, have to hard reset.

λ ~/ lspci | grep VGA
01:00.0 VGA compatible controller: NVIDIA Corporation TU117M [GeForce GTX 1650
Mobile / Max-Q] (rev a1)

λ ~/ uname -a
Linux murph-icl-gen2 5.15.74 #1-NixOS SMP Sat Oct 15 05:59:05 UTC 2022 x86_64
GNU/Linux

Nov 08 09:19:38 murph-icl-gen2 kernel: task:kworker/u32:42  state:D stack:    0
pid:66054 ppid:     2 flags:0x00004000
Nov 08 09:19:38 murph-icl-gen2 kernel: Workqueue: events_unbound
nv50_disp_atomic_commit_work [nouveau]
Nov 08 09:19:38 murph-icl-gen2 kernel: Call Trace:
Nov 08 09:19:38 murph-icl-gen2 kernel:  <TASK>
Nov 08 09:19:38 murph-icl-gen2 kernel:  __schedule+0x2e1/0x1350
Nov 08 09:19:38 murph-icl-gen2 kernel:  ? nvkm_event_get+0x70/0x90 [nouveau]
Nov 08 09:19:38 murph-icl-gen2 kernel:  ? nvkm_client_notify_get+0x23/0x40
[nouveau]
Nov 08 09:19:38 murph-icl-gen2 kernel:  schedule+0x5b/0xd0
Nov 08 09:19:38 murph-icl-gen2 kernel:  schedule_timeout+0x104/0x140
Nov 08 09:19:38 murph-icl-gen2 kernel:  ?
nouveau_fence_enable_signaling+0x2a/0x70 [nouveau]
Nov 08 09:19:38 murph-icl-gen2 kernel:  dma_fence_default_wait+0x1a8/0x240
Nov 08 09:19:38 murph-icl-gen2 kernel:  ? dma_fence_free+0x20/0x20
Nov 08 09:19:38 murph-icl-gen2 kernel:  dma_fence_wait_timeout+0xb6/0xd0
Nov 08 09:19:38 murph-icl-gen2 kernel: 
drm_atomic_helper_wait_for_fences+0x82/0xe0 [drm_kms_helper]
Nov 08 09:19:38 murph-icl-gen2 kernel:  nv50_disp_atomic_commit_tail+0x90/0x850
[nouveau]
Nov 08 09:19:38 murph-icl-gen2 kernel:  process_one_work+0x1ee/0x390
Nov 08 09:19:38 murph-icl-gen2 kernel:  worker_thread+0x53/0x3e0
Nov 08 09:19:38 murph-icl-gen2 kernel:  ? process_one_work+0x390/0x390
Nov 08 09:19:38 murph-icl-gen2 kernel:  kthread+0x124/0x150
Nov 08 09:19:38 murph-icl-gen2 kernel:  ? set_kthread_struct+0x50/0x50
Nov 08 09:19:38 murph-icl-gen2 kernel:  ret_from_fork+0x1f/0x30
Nov 08 09:19:38 murph-icl-gen2 kernel:  </TASK>

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2022-11-08 18:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-25 14:45 [Bug 203033] New: nouveau hung task bugzilla-daemon
2019-10-20 20:11 ` [Bug 203033] " bugzilla-daemon
2020-05-11 15:01 ` bugzilla-daemon
2020-05-11 15:02 ` bugzilla-daemon
2020-05-11 15:03 ` bugzilla-daemon
2020-08-28 15:23 ` bugzilla-daemon
2022-11-08 18:23 ` bugzilla-daemon [this message]
2024-10-02  9:27 ` bugzilla-daemon

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-203033-2300-WuA150pj3w@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@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.