All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 203033] New: nouveau hung task
Date: Mon, 25 Mar 2019 14:45:21 +0000	[thread overview]
Message-ID: <bug-203033-2300@https.bugzilla.kernel.org/> (raw)

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

            Bug ID: 203033
           Summary: nouveau hung task
           Product: Drivers
           Version: 2.5
    Kernel Version: 5.0.0
          Hardware: x86-64
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Video(DRI - non Intel)
          Assignee: drivers_video-dri@kernel-bugs.osdl.org
          Reporter: mcroce@redhat.com
        Regression: No

The GUI freezes randomly with nouveau with this error in the syslog:

INFO: task kworker/u16:4:14755 blocked for more than 120 seconds.
      Not tainted 5.0.0-matteo #28
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
kworker/u16:4   D    0 14755      2 0x80000000
Workqueue: events_unbound nv50_disp_atomic_commit_work [nouveau]
Call Trace:
 ? __schedule+0x1a6/0x6c0
 schedule+0x2c/0x70
 schedule_timeout+0x268/0x380
 ? nvif_notify_get+0x94/0xa0 [nouveau]
 dma_fence_default_wait+0x204/0x270
 ? dma_fence_release+0x90/0x90
 dma_fence_wait_timeout+0xdd/0x100
 drm_atomic_helper_wait_for_fences+0x3a/0xc0 [drm_kms_helper]
 nv50_disp_atomic_commit_tail+0x7c/0x850 [nouveau]
 ? __switch_to_asm+0x34/0x70
 ? __switch_to_asm+0x40/0x70
 ? __switch_to_asm+0x40/0x70
 ? __switch_to_asm+0x40/0x70
 process_one_work+0x1fa/0x400
 worker_thread+0x2d/0x3d0
 ? process_one_work+0x400/0x400
 kthread+0x113/0x130
 ? kthread_create_on_node+0x60/0x60
 ret_from_fork+0x35/0x40

-- 
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

             reply	other threads:[~2019-03-25 14:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-25 14:45 bugzilla-daemon [this message]
2019-10-20 20:11 ` [Bug 203033] nouveau hung task 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
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@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.