From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 108857] New: display becomes unresponsive and keyboard input fails
Date: Sun, 25 Nov 2018 12:20:11 +0000 [thread overview]
Message-ID: <bug-108857-8800@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1970 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=108857
Bug ID: 108857
Summary: display becomes unresponsive and keyboard input fails
Product: xorg
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: major
Priority: medium
Component: Driver/nouveau
Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Reporter: tla2k20-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
QA Contact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
Created attachment 142607
--> https://bugs.freedesktop.org/attachment.cgi?id=142607&action=edit
dmesg
Fedora release 29 (Twenty Nine)
Linux s0.home 4.19.3-300.fc29.x86_64 #1 SMP Wed Nov 21 15:27:25 UTC 2018 x86_64
x86_64 x86_64 GNU/Linux
System boots and is initially OK for a few minutes then becomes unresponsive to
mouse movements and keyboard input. Access via a SSH session is fine.
Issue started around 3 kernel updates ago (4.19.*).
top shows the following when the problem is in progress:
top - 12:10:25 up 1:10, 2 users, load average: 0.23, 0.25, 0.27
Tasks: 356 total, 2 running, 354 sleeping, 0 stopped, 0 zombie
%Cpu(s): 0.8 us, 6.6 sy, 0.0 ni, 91.6 id, 0.0 wa, 1.0 hi, 0.0 si, 0.0 st
MiB Mem : 15982.9 total, 9198.9 free, 4552.3 used, 2231.7 buff/cache
MiB Swap: 8008.0 total, 8008.0 free, 0.0 used. 11035.1 avail Mem
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
7144 root 20 0 0 0 0 R 53.8 0.0 0:02.26
kworker/u16:0+events_unbound
2325 user1 20 0 3867708 195040 118048 S 2.0 1.2 0:28.43
gnome-shell
kworker/u16:2+events_unbound seems to eat CPU and dmesg reports:
nouveau 0000:01:00.0: DRM: base-0: timeout
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3364 bytes --]
[-- Attachment #2: Type: text/plain, Size: 154 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau
next reply other threads:[~2018-11-25 12:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-25 12:20 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-108857-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2018-11-25 12:21 ` [Bug 108857] display becomes unresponsive and keyboard input fails bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-11-26 21:36 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-11-28 16:35 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-11-28 16:37 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-11-29 16:43 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-12-01 7:04 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-04-02 18:15 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-04-02 18:16 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-08-09 17:12 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-09-16 10:39 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04 9:46 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
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-108857-8800@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
--cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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.