From owner-freebsd-bugs@FreeBSD.ORG  Tue Jun  9 19:31:50 2015
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id D5439D4F
 for <freebsd-bugs@FreeBSD.org>; Tue,  9 Jun 2015 19:31:50 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id BF6D91BB1
 for <freebsd-bugs@FreeBSD.org>; Tue,  9 Jun 2015 19:31:50 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t59JVoMK008183
 for <freebsd-bugs@FreeBSD.org>; Tue, 9 Jun 2015 19:31:50 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 200712] log spamming i915 since recent MFC to stable/10
Date: Tue, 09 Jun 2015 19:31:51 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 10.1-STABLE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: riggs@FreeBSD.org
X-Bugzilla-Status: New
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-200712-8-6Ge8pVzRNB@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-200712-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-200712-8@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Jun 2015 19:31:50 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200712

--- Comment #3 from Thomas Zander <riggs@FreeBSD.org> ---
(In reply to Jean-Sebastien Pedron from comment #2)

Hi,
thanks for picking up the ball. I am running stable on this machine, not head
as your commit link refers to. I believe you are right in that the flooding
started after the new driver was MFCed. A quick search through the older driver
sources indicates that the "Power management discrepancy" message didn't even
exist prior to that commit. I am not 100% sure, though, whether it went so
excessive after r280369 or r282199. If the latter did not change anything in
buffer pinning ...

-- 
You are receiving this mail because:
You are the assignee for the bug.