From owner-freebsd-x11@FreeBSD.ORG Thu Apr 9 15:43:53 2015 Return-Path: Delivered-To: freebsd-x11@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 34719409 for ; Thu, 9 Apr 2015 15:43:53 +0000 (UTC) Received: from mail-ie0-x22a.google.com (mail-ie0-x22a.google.com [IPv6:2607:f8b0:4001:c03::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EAE3BC13 for ; Thu, 9 Apr 2015 15:43:52 +0000 (UTC) Received: by iebrs15 with SMTP id rs15so104114724ieb.3 for ; Thu, 09 Apr 2015 08:43:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:content-type; bh=DyR3betdNzOkHET4Zx3ePsbowmJhouep3r4v0VAw+Vs=; b=Fq8B48cEv73Ld1JcCeXJBDbCY0lwIWCN4OiPQjiLp4jBweic7wio0FCfvEmR47SMV4 trSUk655BOfiXuxHhQvj2742uqUJomMIrD5V9qjXE9LqU6EUVhg0HV6PVjgzkcFJp3Mu upitLYLh8Mmthgt9CGTtb4F55EOLTkT3ZOH4zc+ZIbKHCiQODqWi0EKQoa30pu4SD18S kiPUMIS9ObTPy6TIJAHa8FDYUKN1l1Y/nBOA/iqFNeD8h56hithrp2mRolqZLCuCpPwG 3W77oewtxamZHQxjA4+RrWjThpHtbV9hG5/5VAR7ii44AqLX/3BF7pBj3Uv8BJZ69CjR 5LRQ== MIME-Version: 1.0 X-Received: by 10.50.55.1 with SMTP id n1mr10110661igp.35.1428594231847; Thu, 09 Apr 2015 08:43:51 -0700 (PDT) Sender: kob6558@gmail.com Received: by 10.107.174.86 with HTTP; Thu, 9 Apr 2015 08:43:51 -0700 (PDT) In-Reply-To: References: Date: Thu, 9 Apr 2015 08:43:51 -0700 X-Google-Sender-Auth: Grp0GSD5YNVwPAxRBiQYX9gIlgg Message-ID: Subject: Re: New drm messages being logged From: Kevin Oberman To: "freebsd-x11@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Apr 2015 15:43:53 -0000 Never mind! After updating to r281259, the problem has vanished. Sorry for the noise. Kevin Oberman, Network Engineer, Retired E-mail: rkoberman@gmail.com On Wed, Apr 8, 2015 at 9:19 AM, Kevin Oberman wrote: > I continue to see large numbers of: > error: [drm:pid5:i915_gem_object_unbind] *ERROR* Attempting to unbind > pinned buffer > in my security log every morning. I am not seeing any problems related to > this other than pages of errors in messages. I see them in bursts of 10 to > 177 with about a dozen being most typical. The process with PID 5 (assuming > that this is what "pid5" means) is pagedaemon. This looks like it might be > significant. > > Can these be ignored? And, if so, can the messages be silenced? I hate > meaningless errors messages that might distract from something more > important. > > I will be updating to the most recent 10-STABLE in a few minutes (to get > security patches), so maybe they will go away. > > Kevin Oberman, Network Engineer, Retired > E-mail: rkoberman@gmail.com > > On Wed, Apr 1, 2015 at 9:40 AM, Kevin Oberman wrote: > >> I have been seeing a number of drm errors since the last drm MFC to >> 10-Stable. None seems to have caused any problems, but I wanted to report >> them, just in case they are of interest. The "Attempting to unbind pinned >> buffer" errors really caught my attention as there are a lot of thm and I >> had never seen them before yesterday. >> >> FreeBSD rogue 10.1-STABLE FreeBSD 10.1-STABLE #0 r280729: Thu Mar 26 >> 22:49:21 PDT 2015 root@rogue:/usr/obj/usr/src/sys/GENERIC amd64 >> All ports are current. I am enabling rc6 power management: >> drm.i915.enable_rc6=5 >> Mar 27 10:41:19 rogue kernel: error: [drm:pid1242:gen6_sanitize_pm] >> *ERROR* Power management discrepancy: GEN6_RP_INTERRUPT_LIMITS expected >> 1a000000, was 12000000 >> Mar 27 20:06:35 rogue kernel: error: [drm:pid3355:gen6_sanitize_pm] >> *ERROR* Power management discrepancy: GEN6_RP_INTERRUPT_LIMITS expected >> 1a000000, was 12060000 >> Mar 31 08:48:13 rogue kernel: error: [drm:pid5:i915_gem_object_unbind] >> *ERROR* Attempting to unbind pinned buffer >> Mar 31 08:48:13 rogue last message repeated 10 times >> Mar 31 15:38:02 rogue kernel: error: [drm:pid1242:gen6_sanitize_pm] >> *ERROR* Power management discrepancy: GEN6_RP_INTERRUPT_LIMITS expected >> 1a0d0000, was 1a000000 >> Mar 31 15:49:56 rogue kernel: error: [drm:pid1242:gen6_sanitize_pm] >> *ERROR* Power management discrepancy: GEN6_RP_INTERRUPT_LIMITS expected >> 1a0d0000, was 1a000000 >> Apr 1 08:57:52 rogue kernel: error: [drm:pid5:i915_gem_object_unbind] >> *ERROR* Attempting to unbind pinned buffer >> Apr 1 08:57:52 rogue last message repeated 9 times >> Apr 1 08:59:42 rogue kernel: error: [drm:pid5:i915_gem_object_unbind] >> *ERROR* Attempting to unbind pinned buffer >> Apr 1 09:01:34 rogue kernel: error: [drm:pid5:i915_gem_object_unbind] >> *ERROR* Attempting to unbind pinned buffer >> Apr 1 09:01:54 rogue last message repeated 20 times >> Apr 1 09:04:04 rogue last message repeated 51 times >> Apr 1 09:09:36 rogue last message repeated 53 times >> Apr 1 09:17:10 rogue last message repeated 11 times >> -- >> Kevin Oberman, Network Engineer, Retired >> E-mail: rkoberman@gmail.com >> > >