From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 153911] Nouveau driver overly verbose
Date: Sun, 16 Oct 2016 11:12:06 +0000 [thread overview]
Message-ID: <bug-153911-2300-7nLTlCiF7M@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-153911-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=153911
--- Comment #3 from Pierre Moreau <pierre.morrow@free.fr> ---
Oh, an Optimus latopt I guess, where the Intel GPU is the main one?
Having a look at the source code, it appears that all the
`NV_(FATAL|ERROR|WARN|INFO|DEBUG)` macros do not take into account the Nouveau
log level and max log level variables, but only the kernel log level. I am not
sure if it was meant to be that way, or someone forgetting to update those
macros / switch to the new ones which respect the specified log level.
Maybe all those suspend/resume messages shouldn’t be marked as info level, and
could be moved to debug instead.
I’ll ping Ben (the Nouveau maintainer) about it.
(FYI, the Nouveau bug tracker is at https://bugs.freedesktop.org/, see
https://nouveau.freedesktop.org/wiki/Bugs/)
--
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
next prev parent reply other threads:[~2016-10-16 11:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-25 5:38 [Bug 153911] New: Nouveau driver overly verbose bugzilla-daemon
2016-08-28 10:27 ` [Bug 153911] " bugzilla-daemon
2016-10-07 3:40 ` bugzilla-daemon
2016-10-16 11:12 ` bugzilla-daemon [this message]
2017-08-14 7: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-153911-2300-7nLTlCiF7M@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.