From owner-freebsd-x11@freebsd.org Sun Apr 24 20:18:22 2016 Return-Path: Delivered-To: freebsd-x11@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 07A55B1B5E7 for ; Sun, 24 Apr 2016 20:18:22 +0000 (UTC) (envelope-from mmacy@nextbsd.org) Received: from sender163-mail.zoho.com (sender163-mail.zoho.com [74.201.84.163]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id EFB0110FD for ; Sun, 24 Apr 2016 20:18:21 +0000 (UTC) (envelope-from mmacy@nextbsd.org) Received: from mail.zoho.com by mx.zohomail.com with SMTP id 1461529094309773.7260583429751; Sun, 24 Apr 2016 13:18:14 -0700 (PDT) Date: Sun, 24 Apr 2016 13:18:14 -0700 From: Matthew Macy To: "freebsd-x11@freebsd.org" Message-ID: <15449ec286e.11def424858288.297669375175006270@nextbsd.org> In-Reply-To: <1540c0ceea9.126b592b988423.8774357707501817476@nextbsd.org> References: <1540c0ceea9.126b592b988423.8774357707501817476@nextbsd.org> Subject: Update 1 was Re: clarifying the state of drm-next-3.9 and next steps MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Priority: Medium User-Agent: Zoho Mail X-Mailer: Zoho Mail X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Apr 2016 20:18:22 -0000 ---- On Tue, 12 Apr 2016 12:57:34 -0700 Matthew Macy wrote ---- > There seems to be some confusion about the state of drm-next-3.9. All the work is currently going on in jmd's fork of freebsd-base-graphics: > > https://github.com/iotamudelta/freebsd-base-graphics > > The emphasis has been on bringing i915 and the drm code in dev/drm2 closer to upstream as opposed to a simple driver refresh. I'm currently implementing missing linuxkpi bits and hope to actually be testing in the next week or so. > > As of this moment there is nothing available for general consumption. I very much hope to have this phase done before code freeze. I will update the list as soon as there is anything to test. Until then, hold your horses. > X now runs i915kms accelerated on the 3.9 driver update. Currently *only* SNA works. Known issues: - UXA will fail with: "(EE) failed to create screen resources(EE)". If someone has pointer on how to diagnose other than the usual trawling through Xorg sources let me know. - The module currently leaks memory on unload. My general feeling is that unless you have one of the half-dozen Haswell PCIIDS that aren't support by 3.8 it probably isn't worth testing yet. I'm only sending this out to let users track its progress. Cheers. -M From owner-freebsd-x11@freebsd.org Sun Apr 24 21:01:27 2016 Return-Path: Delivered-To: freebsd-x11@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B78AAB1B366 for ; Sun, 24 Apr 2016 21:01:27 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 9457A198A for ; Sun, 24 Apr 2016 21:01:27 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 93C03B1B365; Sun, 24 Apr 2016 21:01:27 +0000 (UTC) Delivered-To: x11@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 936C9B1B364 for ; Sun, 24 Apr 2016 21:01:27 +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 724331986 for ; Sun, 24 Apr 2016 21:01:27 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u3OL01cb027824 for ; Sun, 24 Apr 2016 21:01:27 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <201604242101.u3OL01cb027824@kenobi.freebsd.org> From: bugzilla-noreply@FreeBSD.org To: x11@FreeBSD.org Subject: Problem reports for x11@FreeBSD.org that need special attention Date: Sun, 24 Apr 2016 21:01:27 +0000 X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Apr 2016 21:01:27 -0000 To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status | Bug Id | Description ------------+-----------+--------------------------------------------------- In Progress | 188833 | [suspend/resume] Suspend/resume with Intel GMA HD 1 problems total for which you should take action. From owner-freebsd-x11@freebsd.org Sun Apr 24 21:25:41 2016 Return-Path: Delivered-To: freebsd-x11@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 11E1AB1BA76 for ; Sun, 24 Apr 2016 21:25:41 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: from mail-oi0-f65.google.com (mail-oi0-f65.google.com [209.85.218.65]) (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 D5EB017E5 for ; Sun, 24 Apr 2016 21:25:40 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: by mail-oi0-f65.google.com with SMTP id f63so20913552oig.0 for ; Sun, 24 Apr 2016 14:25:40 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:reply-to:in-reply-to:references :date:message-id:subject:from:to:cc; bh=2kD5E5AzXfEQspVRadRZtTsuWJTlOLPfv+OlvdBNLic=; b=mLdhkjVR1hB/0QmkI6B5HeLMyC3WxB4u4kaY6Z6/oPjH0mniB5j54GWyD7j79FH7Kr 4bbG0j6X1s0tRH0Qo8qt8NOhYIVXxemKgIJ8A9aDDh+925UFAOdJiWNsPjGkjJAnbW6S mbEDk5S0MDMtyvkcGnaZgiPilH+JFV9jDob4+RcaSi9AaeUX8KwnnqIPCdbIFPUaXON3 ZRmaPUlax2SD0ohOvLTYkFyOPsW3PRX40mhREcBag1jjjVrnpZ0YLtPKAsX6tmJXGMKx s7SGhCNGhzmuIWAuHYIkZHw3HcKuIwTlCTTJsUcYKp795zxwuU96U4khCUmLNF3VfSai OuLw== X-Gm-Message-State: AOPr4FUOUg80/3qvZj02MxbzSbXbKnWFgu0YRh44NBEhlt7pYZW4fph6zDcE0xtpefAL+A== X-Received: by 10.157.25.166 with SMTP id k35mr12304253otk.100.1461529401144; Sun, 24 Apr 2016 13:23:21 -0700 (PDT) Received: from mail-oi0-f48.google.com (mail-oi0-f48.google.com. [209.85.218.48]) by smtp.gmail.com with ESMTPSA id s127sm5501761oie.4.2016.04.24.13.23.20 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 24 Apr 2016 13:23:20 -0700 (PDT) Received: by mail-oi0-f48.google.com with SMTP id x19so26069788oix.2 for ; Sun, 24 Apr 2016 13:23:20 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.202.169.131 with SMTP id s125mr1859896oie.35.1461529400542; Sun, 24 Apr 2016 13:23:20 -0700 (PDT) Reply-To: cem@FreeBSD.org Received: by 10.157.6.111 with HTTP; Sun, 24 Apr 2016 13:23:20 -0700 (PDT) In-Reply-To: <15449ec286e.11def424858288.297669375175006270@nextbsd.org> References: <1540c0ceea9.126b592b988423.8774357707501817476@nextbsd.org> <15449ec286e.11def424858288.297669375175006270@nextbsd.org> Date: Sun, 24 Apr 2016 13:23:20 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Update 1 was Re: clarifying the state of drm-next-3.9 and next steps From: Conrad Meyer To: Matthew Macy Cc: "freebsd-x11@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Apr 2016 21:25:41 -0000 On Sun, Apr 24, 2016 at 1:18 PM, Matthew Macy wrote: > X now runs i915kms accelerated on the 3.9 driver update. Currently *only* SNA works. > Known issues: > - UXA will fail with: "(EE) failed to create screen resources(EE)". > If someone has pointer on how to diagnose other than the usual trawling > through Xorg sources let me know. > - The module currently leaks memory on unload. This might not even be a new issue (or: not a major regression). The 3.8 driver leaked during unload when I tried it. Best, Conrad From owner-freebsd-x11@freebsd.org Sun Apr 24 21:25:55 2016 Return-Path: Delivered-To: freebsd-x11@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 512A4B1BA94 for ; Sun, 24 Apr 2016 21:25:55 +0000 (UTC) (envelope-from mmacy@nextbsd.org) Received: from sender163-mail.zoho.com (sender163-mail.zoho.com [74.201.84.163]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 43C3A1835 for ; Sun, 24 Apr 2016 21:25:55 +0000 (UTC) (envelope-from mmacy@nextbsd.org) Received: from mail.zoho.com by mx.zohomail.com with SMTP id 1461533152881640.6638950935001; Sun, 24 Apr 2016 14:25:52 -0700 (PDT) Date: Sun, 24 Apr 2016 14:25:52 -0700 From: Matthew Macy To: "cem@FreeBSD.org" Cc: "freebsd-x11@freebsd.org" Message-ID: <1544a2a163d.b02b355958875.1610265201785479154@nextbsd.org> In-Reply-To: References: <1540c0ceea9.126b592b988423.8774357707501817476@nextbsd.org> <15449ec286e.11def424858288.297669375175006270@nextbsd.org> Subject: Re: Update 1 was Re: clarifying the state of drm-next-3.9 and next steps MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Priority: Medium User-Agent: Zoho Mail X-Mailer: Zoho Mail X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Apr 2016 21:25:55 -0000 ---- On Sun, 24 Apr 2016 13:23:20 -0700 Conrad Meyer wrote ---- > On Sun, Apr 24, 2016 at 1:18 PM, Matthew Macy wrote: > > X now runs i915kms accelerated on the 3.9 driver update. Currently *only* SNA works. > > Known issues: > > - UXA will fail with: "(EE) failed to create screen resources(EE)". > > If someone has pointers on how to diagnose other than the usual trawling > > through Xorg sources let me know. > > - The module currently leaks memory on unload. > > This might not even be a new issue (or: not a major regression). The > 3.8 driver leaked during unload when I tried it. > Good point. I have fewer issues when unloading 3.8, but it's certainly not without its issues. Seeing as the real gating factor on pushing these changes upstream is waiting on Jean to make the corresponding changes to update the radeon driver(s) I think I'll just move on to 4.6. Cheers. -M From owner-freebsd-x11@freebsd.org Sun Apr 24 22:48:41 2016 Return-Path: Delivered-To: freebsd-x11@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 72678B1BC08 for ; Sun, 24 Apr 2016 22:48:41 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 5DEB61B3E for ; Sun, 24 Apr 2016 22:48:41 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 5962FB1BC07; Sun, 24 Apr 2016 22:48:41 +0000 (UTC) Delivered-To: x11@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 590C3B1BC06 for ; Sun, 24 Apr 2016 22:48:41 +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 4A02D1B3D for ; Sun, 24 Apr 2016 22:48:41 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u3OMmfuX082877 for ; Sun, 24 Apr 2016 22:48:41 GMT (envelope-from bugzilla-noreply@freebsd.org) Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="UTF-8" From: bugzilla-noreply@freebsd.org To: x11@FreeBSD.org Subject: maintainer-feedback requested: [Bug 209020] x11-servers/xorg-server Intel video hardware acceleration causes cpu overheating Date: Sun, 24 Apr 2016 22:48:41 +0000 X-Bugzilla-Type: request X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: x11@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? Message-ID: In-Reply-To: References: X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Apr 2016 22:48:41 -0000 tony@accesslab.com has reassigned Bugzilla Automation 's request for maintainer-feedback to x11@FreeBSD.org: Bug 209020: x11-servers/xorg-server Intel video hardware acceleration causes cpu overheating https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D209020 --- Description --- When using either the Intel i915 driver in xf86-video-intel-2.21.15_9 or In= tel modesetting driver built in to xorg-server-1.17.4, running with hardware acceleration turned, the cpu chip temerature rapidly rises to above 60 deg = C on Lenovo G770 laptop with an Intel i3 2310M cpu and Intel HD video. This occu= rs even when minimal video operations are happening, for example simple scroll= ing on an Xterm will cause it. Once the temperature starts rising, it will stay elevated indefinitely until the X server is exited. The cpu frequency is not causing it because the temperature remains elevated above 60 deg C even whi= le the system is idle and the cpu frequency is idling at 800 MHz on a 2.1 GHz = cpu. Also the laptop fan and heatsink assembly is clean of any dust, is open with full airflow, and operating properly. When the acceleration is turned off in either driver ( "NoAccel"=3D"true" i= n the intel driver and "AccelMethod"=3D"none" in the Xorg modesetting driver ), t= he problem goes away. With no acceleration, fast terminal scrolling and/or high graphics operations will cause the temperature to elevate but quickly goes = back down once the graphics operations become idle. In comparison, with the acceleration turned on, once the graphics operation triggers a temperature rise, the temperature rises excessively and remains elevated in a seemingly runaway condition until the X server is exited. The excessive temperature runaway condition can damage the laptop and/or greatly reduce battery charge life. The work around is to run the Xorg built in modesetting driver with glamor acceleraton turned off. =3D=3D=3D The laptop cpu/os specs: FreeBSD 10.3-RELEASE #0 r297264: Fri Mar 25 02:10:02 UTC 2016 root@releng1.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final 208032) 20140512 VT(vga): resolution 640x480 info: [drm] Initialized drm 1.1.0 20060810 CPU: Intel(R) Core(TM) i3-2310M CPU @ 2.10GHz (2095.29-MHz K8-class CPU) Origin=3D"GenuineIntel" Id=3D0x206a7 Family=3D0x6 Model=3D0x2a Steppi= ng=3D7 =20 Features=3D0xbfebfbff =20 Features2=3D0x1dbae3bf AMD Features=3D0x28100800 AMD Features2=3D0x1 XSAVE Features=3D0x1 VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID TSC: P-state invariant, performance statistics real memory =3D 4294967296 (4096 MB) avail memory =3D 4043096064 (3855 MB) Event timer "LAPIC" quality 600 ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs FreeBSD/SMP: 1 package(s) x 2 core(s) x 2 SMT threads cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 =3D=3D=3D From owner-freebsd-x11@freebsd.org Sun Apr 24 22:48:41 2016 Return-Path: Delivered-To: freebsd-x11@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B950EB1BC10 for ; Sun, 24 Apr 2016 22:48:41 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id A45611B43 for ; Sun, 24 Apr 2016 22:48:41 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id A3C82B1BC0F; Sun, 24 Apr 2016 22:48:41 +0000 (UTC) Delivered-To: x11@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A37B0B1BC0E for ; Sun, 24 Apr 2016 22:48:41 +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 93BA81B41 for ; Sun, 24 Apr 2016 22:48:41 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u3OMmfub082877 for ; Sun, 24 Apr 2016 22:48:41 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: x11@FreeBSD.org Subject: [Bug 209020] x11-servers/xorg-server Intel video hardware acceleration causes cpu overheating Date: Sun, 24 Apr 2016 22:48:41 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: tony@accesslab.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: x11@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter flagtypes.name Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Apr 2016 22:48:41 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D209020 Bug ID: 209020 Summary: x11-servers/xorg-server Intel video hardware acceleration causes cpu overheating Product: Ports & Packages Version: Latest Hardware: amd64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: Individual Port(s) Assignee: x11@FreeBSD.org Reporter: tony@accesslab.com Flags: maintainer-feedback?(x11@FreeBSD.org) Assignee: x11@FreeBSD.org When using either the Intel i915 driver in xf86-video-intel-2.21.15_9 or In= tel modesetting driver built in to xorg-server-1.17.4, running with hardware acceleration turned, the cpu chip temerature rapidly rises to above 60 deg = C on Lenovo G770 laptop with an Intel i3 2310M cpu and Intel HD video. This occu= rs even when minimal video operations are happening, for example simple scroll= ing on an Xterm will cause it. Once the temperature starts rising, it will stay elevated indefinitely until the X server is exited. The cpu frequency is not causing it because the temperature remains elevated above 60 deg C even whi= le the system is idle and the cpu frequency is idling at 800 MHz on a 2.1 GHz = cpu. Also the laptop fan and heatsink assembly is clean of any dust, is open with full airflow, and operating properly. When the acceleration is turned off in either driver ( "NoAccel"=3D"true" i= n the intel driver and "AccelMethod"=3D"none" in the Xorg modesetting driver ), t= he problem goes away. With no acceleration, fast terminal scrolling and/or high graphics operations will cause the temperature to elevate but quickly goes = back down once the graphics operations become idle. In comparison, with the acceleration turned on, once the graphics operation triggers a temperature rise, the temperature rises excessively and remains elevated in a seemingly runaway condition until the X server is exited. The excessive temperature runaway condition can damage the laptop and/or greatly reduce battery charge life. The work around is to run the Xorg built in modesetting driver with glamor acceleraton turned off. =3D=3D=3D The laptop cpu/os specs: FreeBSD 10.3-RELEASE #0 r297264: Fri Mar 25 02:10:02 UTC 2016 root@releng1.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final 208032) 20140512 VT(vga): resolution 640x480 info: [drm] Initialized drm 1.1.0 20060810 CPU: Intel(R) Core(TM) i3-2310M CPU @ 2.10GHz (2095.29-MHz K8-class CPU) Origin=3D"GenuineIntel" Id=3D0x206a7 Family=3D0x6 Model=3D0x2a Steppi= ng=3D7 =20 Features=3D0xbfebfbff =20 Features2=3D0x1dbae3bf AMD Features=3D0x28100800 AMD Features2=3D0x1 XSAVE Features=3D0x1 VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID TSC: P-state invariant, performance statistics real memory =3D 4294967296 (4096 MB) avail memory =3D 4043096064 (3855 MB) Event timer "LAPIC" quality 600 ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs FreeBSD/SMP: 1 package(s) x 2 core(s) x 2 SMT threads cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 =3D=3D=3D --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-x11@freebsd.org Mon Apr 25 13:15:28 2016 Return-Path: Delivered-To: freebsd-x11@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A9E1AB1C3F6 for ; Mon, 25 Apr 2016 13:15:28 +0000 (UTC) (envelope-from isoa@kapsi.fi) Received: from mail.kapsi.fi (mx1.kapsi.fi [IPv6:2001:1bc8:1004::1:25]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 697E41168 for ; Mon, 25 Apr 2016 13:15:28 +0000 (UTC) (envelope-from isoa@kapsi.fi) Received: from 91-159-15-56.elisa-laajakaista.fi ([91.159.15.56] helo=[192.168.255.143]) by mail.kapsi.fi with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from ) id 1augMG-0005CF-FP; Mon, 25 Apr 2016 16:15:24 +0300 Subject: Re: Update 1 was Re: clarifying the state of drm-next-3.9 and next steps To: Matthew Macy , "freebsd-x11@freebsd.org" References: <1540c0ceea9.126b592b988423.8774357707501817476@nextbsd.org> <15449ec286e.11def424858288.297669375175006270@nextbsd.org> From: Arto Pekkanen Message-ID: <571E1867.3070305@kapsi.fi> Date: Mon, 25 Apr 2016 16:15:19 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.7.1 MIME-Version: 1.0 In-Reply-To: <15449ec286e.11def424858288.297669375175006270@nextbsd.org> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="j2X10tWLEJB4iKeEvHPokovFajp5etR7W" X-SA-Exim-Connect-IP: 91.159.15.56 X-SA-Exim-Mail-From: isoa@kapsi.fi X-SA-Exim-Scanned: No (on mail.kapsi.fi); SAEximRunCond expanded to false X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Apr 2016 13:15:28 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --j2X10tWLEJB4iKeEvHPokovFajp5etR7W Content-Type: multipart/mixed; boundary="TXjgdj27nwto9U9PJhujAfNr3xQAqEpva" From: Arto Pekkanen To: Matthew Macy , "freebsd-x11@freebsd.org" Message-ID: <571E1867.3070305@kapsi.fi> Subject: Re: Update 1 was Re: clarifying the state of drm-next-3.9 and next steps References: <1540c0ceea9.126b592b988423.8774357707501817476@nextbsd.org> <15449ec286e.11def424858288.297669375175006270@nextbsd.org> In-Reply-To: <15449ec286e.11def424858288.297669375175006270@nextbsd.org> --TXjgdj27nwto9U9PJhujAfNr3xQAqEpva Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Thank you very much for the notice! It is always nice to receive updates on the situation of gfx drivers, since some people seem to be asking about these things ... so I can just ask them to subscribe to this mailing list ;D I haven't been using UXA since 10.1, SNA is stable enough nowadays. The only problem I have with SNA with 10.x is that enabling more than 2 outputs causes X.org to hang. With the updated driver from 3.8 this is no longer an issue :P On 24.04.2016 23:18, Matthew Macy wrote: >=20 >=20 >=20 > ---- On Tue, 12 Apr 2016 12:57:34 -0700 Matthew Macy wrote ----=20 > > There seems to be some confusion about the state of drm-next-3.9. Al= l the work is currently going on in jmd's fork of freebsd-base-graphics: > >=20 > > https://github.com/iotamudelta/freebsd-base-graphics > >=20 > > The emphasis has been on bringing i915 and the drm code in dev/drm2= closer to upstream as opposed to a simple driver refresh. I'm currently = implementing missing linuxkpi bits and hope to actually be testing in the= next week or so.=20 > >=20 > > As of this moment there is nothing available for general consumption= =2E I very much hope to have this phase done before code freeze. I will u= pdate the list as soon as there is anything to test. Until then, hold you= r horses. > >=20 >=20 > X now runs i915kms accelerated on the 3.9 driver update. Currently *onl= y* SNA works. > Known issues: > - UXA will fail with: "(EE) failed to create screen resources(EE)". = > If someone has pointer on how to diagnose other than the usual t= rawling=20 > through Xorg sources let me know.=20 > - The module currently leaks memory on unload. >=20 >=20 > My general feeling is that unless you have one of the half-dozen Haswel= l PCIIDS that aren't support by 3.8 it probably isn't worth testing yet. = I'm only sending this out to let users track its progress. >=20 >=20 > Cheers. > -M >=20 > _______________________________________________ > freebsd-x11@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-x11 > To unsubscribe, send any mail to "freebsd-x11-unsubscribe@freebsd.org" >=20 --TXjgdj27nwto9U9PJhujAfNr3xQAqEpva-- --j2X10tWLEJB4iKeEvHPokovFajp5etR7W Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF4EAREIAAYFAlceGGcACgkQTBivhqtJa26+AwEAhATGczVE3udSV61FKkW99BDw hn+ZR5w0sZhFf/rI80EA/1/2d8xBlJSoVi01XeKxmdrlNRvfOLB/3CCZJexGrF6a =9Atq -----END PGP SIGNATURE----- --j2X10tWLEJB4iKeEvHPokovFajp5etR7W-- From owner-freebsd-x11@freebsd.org Thu Apr 28 10:35:56 2016 Return-Path: Delivered-To: freebsd-x11@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EA6A0B1F00F for ; Thu, 28 Apr 2016 10:35:56 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id D94C51C13 for ; Thu, 28 Apr 2016 10:35:56 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id D8B42B1F00E; Thu, 28 Apr 2016 10:35:56 +0000 (UTC) Delivered-To: x11@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D869BB1F00D for ; Thu, 28 Apr 2016 10:35:56 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: from portscout.freebsd.org (portscout.freebsd.org [IPv6:2001:1900:2254:206a::50:6]) (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 CCC341C12 for ; Thu, 28 Apr 2016 10:35:56 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: from portscout.freebsd.org ([127.0.1.123]) by portscout.freebsd.org (8.15.2/8.15.2) with ESMTP id u3SAZusL030371 for ; Thu, 28 Apr 2016 10:35:56 GMT (envelope-from portscout@FreeBSD.org) Received: (from portscout@localhost) by portscout.freebsd.org (8.15.2/8.15.2/Submit) id u3SAZuH9030370; Thu, 28 Apr 2016 10:35:56 GMT (envelope-from portscout@FreeBSD.org) Message-Id: <201604281035.u3SAZuH9030370@portscout.freebsd.org> X-Authentication-Warning: portscout.freebsd.org: portscout set sender to portscout@FreeBSD.org using -f Content-Disposition: inline Content-Transfer-Encoding: 8bit Content-Type: text/plain MIME-Version: 1.0 Date: Thu, 28 Apr 2016 10:35:56 +0000 From: portscout@FreeBSD.org To: x11@freebsd.org Subject: FreeBSD ports you maintain which are out of date X-Mailer: portscout/0.8.1 X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.21 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, 28 Apr 2016 10:35:57 -0000 Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/x11@freebsd.org.html Port | Current version | New version ------------------------------------------------+-----------------+------------ graphics/libdrm | 2.4.66 | 2.4.68 ------------------------------------------------+-----------------+------------ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt Thanks.