From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 106431] On ASUS A8JN laptop with G72M GPU dmesg is flooded with error messages
Date: Wed, 21 Oct 2015 17:43:59 +0000 [thread overview]
Message-ID: <bug-106431-2300-SxSmEoBBO0@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-106431-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=106431
Ilia Mirkin <imirkin@alum.mit.edu> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |imirkin@alum.mit.edu
--- Comment #1 from Ilia Mirkin <imirkin@alum.mit.edu> ---
Looks like this is because pre-tesla supplies a crtcid of -1 for pre-tesla
(which your gpu is), and "pipe" was recently made into unsigned int, which
causes the warn to trigger.
J'accuse
commit cc1ef118fc099295ae6aabbacc8af94d8d8885eb
Author: Thierry Reding <treding@nvidia.com>
Date: Wed Aug 12 17:00:31 2015 +0200
drm/irq: Make pipe unsigned and name consistent
Name all references to the pipe number (CRTC index) consistently to make
it easier to distinguish which is a pipe number and which is a pointer
to struct drm_crtc.
While at it also make all references to the pipe number unsigned because
there is no longer any reason why it should ever be negative.
Signed-off-by: Thierry Reding <treding@nvidia.com>
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2015-10-21 17:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-21 15:25 [Bug 106431] New: dmesg is flooded with error messages bugzilla-daemon
2015-10-21 17:07 ` [Bug 106431] On ASUS A8JN laptop with G72M GPU " bugzilla-daemon
2015-10-21 17:43 ` bugzilla-daemon [this message]
2015-10-21 18:25 ` bugzilla-daemon
2015-10-30 21:57 ` bugzilla-daemon
2015-11-02 20:38 ` bugzilla-daemon
2015-11-02 20:40 ` bugzilla-daemon
2015-11-02 20:50 ` bugzilla-daemon
2015-11-07 5:15 ` bugzilla-daemon
2015-11-07 17:09 ` bugzilla-daemon
2015-11-07 17:12 ` 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-106431-2300-SxSmEoBBO0@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