When using either the Intel i915 driver in xf86-video-intel-2.21.15_9 or Intel 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 occurs even when minimal video operations are happening, for example simple scrolling 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 while 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"="true" in the intel driver and "AccelMethod"="none" in the Xorg modesetting driver ), the 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. === 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="GenuineIntel" Id=0x206a7 Family=0x6 Model=0x2a Stepping=7 Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FX SR,SSE,SSE2,SS,HTT,TM,PBE> Features2=0x1dbae3bf<SSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,PO PCNT,TSCDLT,XSAVE,OSXSAVE,AVX> AMD Features=0x28100800<SYSCALL,NX,RDTSCP,LM> AMD Features2=0x1<LAHF> XSAVE Features=0x1<XSAVEOPT> VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID TSC: P-state invariant, performance statistics real memory = 4294967296 (4096 MB) avail memory = 4043096064 (3855 MB) Event timer "LAPIC" quality 600 ACPI APIC Table: <INSYDE HR CRB > 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 ===
Is the problem still present?
I have never experienced this with drm-next and Intel/modesetting driver. It's been a while since I used drm2 but I can't recall seeing this behavior on a Haswell laptop ever.
Feedback timeout