From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 206781] GM104 (GeForce 840m) with many errors "fifo: SCHED_ERROR 20"
Date: Sun, 08 Mar 2020 11:16:29 +0000 [thread overview]
Message-ID: <bug-206781-2300-Yy2xeHHRAn@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-206781-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=206781
--- Comment #2 from gsedej@gmail.com ---
In the first step:
what can be done that other users would not have to deal with
"nouveau.noaccel=1" or other kernel options just to use the system (assuming no
need for 3D from dedicated card)
I was also told it's issue with system (ubuntu's) logg-er or something?
For me - I am using Ubuntu 16.04 with nvidia blob on this laptop. But when
trying different ubuntu versions, I always get this spamming in system logs.
(the laptop is HP ENVY 15-j192nf - K4D07EAR#ABF)
For the actual bug - how can this issue be further diagnosed?
I found similar issues:
https://bugzilla.kernel.org/show_bug.cgi?id=101911
https://gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/issues/175
https://gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/issues/352
https://bbs.archlinux.org/viewtopic.php?id=231444
--
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-03-08 11:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-07 21:41 [Bug 206781] New: GM104 (GeForce 840m) with many errors "fifo: SCHED_ERROR 20" bugzilla-daemon
2020-03-07 22:25 ` [Bug 206781] " bugzilla-daemon
2020-03-08 11:16 ` 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-206781-2300-Yy2xeHHRAn@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox