Solved GPU hanging around on GM965 chipset

I find a consistent problem with my laptop whenever I run cheese, the screen will turn black and I'll look into the logs and get this following message:

Code:
Feb  8 21:53:43 Dell kernel: error: [drm:pid12:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
Feb  8 21:53:43 Dell kernel: info: [drm] capturing error event; look for more information in sysctl hw.dri.0.info.i915_error_state
Feb  8 21:53:43 Dell kernel: error: [drm:pid0:i915_reset] *ERROR* Failed to reset chip.
Feb  8 21:53:53 Dell kernel: error: [drm:pid0:assert_pll] *ERROR* PLL state assertion failure (expected on, current off)
Feb  8 21:53:54 Dell syslogd: last message repeated 1 times
Feb  8 21:53:54 Dell kernel: error: [drm:pid0:assert_pipe] *ERROR* pipe A assertion failure (expected on, current off)
Feb  8 21:53:55 Dell devd[521]: notify_clients: send() failed; dropping unresponsive client
Feb  8 21:53:55 Dell syslogd: last message repeated 3 times
Feb  8 21:53:55 Dell kernel: error: [drm:pid0:intel_enable_lvds] *ERROR* timed out waiting for panel to power on
Feb  8 21:53:55 Dell kernel: error: [drm:pid0:intel_modeset_check_state] *ERROR* encoder's hw state doesn't match sw tracking (expected 1, found 0)
Feb  8 21:53:55 Dell kernel: error: [drm:pid0:assert_pipe] *ERROR* pipe A assertion failure (expected on, current off)
Feb  8 21:53:55 Dell kernel: info: [drm] GMBUS [i915 gmbus vga] timed out, falling back to bit banging on pin 2

I've already tested this with the new i915kms loaded from module directory, it loads fine but since I'm running a Core 2 Duo I don't think it'll be supported since the resolution is off. I'll continue to play around with Xorg file to see what settings I can apply with the intel driver so I can use the base kernel video driver or try to work with the new driver on getting the right resolution.
 
I didn't check back on the bug site since the issue has been opened for quite awhile so thinking it might be closed or fixed for such a old bug. I'm not sure if anyone else is running older GPU like mine and is facing this sort of issue. I've searched for this kind of problem and there's not much info about it except the one I've listed.
 
I was able to get the module i915kms.ko to load through single user mode but the same thing still happens. Now I'll focus getting it to see why it's not loading during multiuser mode, considering there's no error message from the logs.
 
Off the top of my head, I'd look in /etc/rc.conf and double-check the kld_list syntax. A weird issue I had, I needed to load the GPU driver as the last thing, otherwise I did have errors.
 
Yeah, I looked a little deeper with kldstat even if I put the correct syntax kld_list, it still loads the driver from base and by force loading from module cause it to hung which is why the screen turned black. So far installing the drm-kmod from port didn't work so I'm sticking with the binary.
 
Please share relevant information:

freebsd-version -kru

uname -aKU

sysrc kld_list

pkg info -x drm gpu xf86 | sort

pciconf -lv | grep -B 3 -A 2 display

– and so on, so that readers need not guess.

… installing the drm-kmod from port didn't work …

What happened, exactly? Did you keep a transcript?

… Core 2 Duo …

Core 2 Duo Ergo Vista 631 <https://bsd-hardware.info/?computer=3a7d355eebe4> with 2008 firmware was fine, for graphics, with FreeBSD 13.0-RELEASE and NomadBSD. The two probes of helloSystem were FreeBSD 12.1-RELEASE at the time, I don't recall graphics problems. I'm almost certain that I sometimes booted from a 14.0-CURRENT disk; again, no problem with graphics.
 
Please share relevant information:

freebsd-version -kru
12.2-RELEASE-p7
12.2-RELEASE-p7
12.2-RELEASE-p11

uname -aKU
FreeBSD Dell 12.2-RELEASE-p7 FreeBSD 12.2-RELEASE-p7 GENERIC amd64 1202000 1202000

sysrc kld_list
sysrc isn't able to recognize the kld_list variable, it loads the kernel driver and won't load the module one (contrast to my previous post saying it loads but a few update passed by and now it doesn't appear to be working as it'll hung.)

pkg info -x drm gpu xf86 | sort
drm-fbsd12.0-kmod-4.16.g20201016_2
drm-kmod-g20190710_1
libXxf86dga-1.1.5
libXxf86vm-1.1.4_3
libdrm-2.4.107_1,1
linux-c7-libdrm-2.4.97
xf86-input-evdev-2.10.6_6
xf86-input-keyboard-1.9.0_4
xf86-input-libinput-0.30.0_1
xf86-input-mouse-1.9.3_3
xf86-video-intel-2.99.917.916_1,1
xf86-video-scfb-0.0.5_2
xf86-video-vesa-2.5.0
xf86dga-1.0.3_1

pciconf -lv | grep -B 3 -A 2 display
vgapci0@pci0:0:2:0: class=0x030000 card=0x02271028 chip=0x2a028086 rev=0x0c hdr=0x00
vendor = 'Intel Corporation'
device = 'Mobile GM965/GL960 Integrated Graphics Controller (primary)'
class = display
subclass = VGA
vgapci1@pci0:0:2:1: class=0x038000 card=0x02271028 chip=0x2a038086 rev=0x0c hdr=0x00
vendor = 'Intel Corporation'
device = 'Mobile GM965/GL960 Integrated Graphics Controller (secondary)'
class = display
uhci0@pci0:0:26:0: class=0x0c0300 card=0x02271028 chip=0x28348086 rev=0x02 hdr=0x00
vendor = 'Intel Corporation'

What happened, exactly? Did you keep a transcript?
I was testing to if installing from port will help prevent the GPU from crashing when loading the i915 module or load certain applications that reproduce the issue. The main symptom is the screen turned black, sound will work and keyboard works so I had to reboot my computer. The system and Xorg log shows the GPU has hung and failed to reset, I saw a couple of posts related to that so I'll continue to probe this issue further to try the workaround.
 
I'll mark this thread as solved as I found a temporary workaround from using the modesetting driver on the xorg conf file and wasn't able to reproduce the crashes anymore as Cheese is able to open successfully and Steam as well. The i915 module still crashes if I load it but I'll keep it for future testing once Freebsd 12 branch goes EOL and move on from there.
 
I'll mark this thread as solved as I found a temporary workaround from using the modesetting driver on the xorg conf file and wasn't able to reproduce the crashes anymore as Cheese is able to open successfully and Steam as well. The i915 module still crashes if I load it but I'll keep it for future testing once Freebsd 12 branch goes EOL and move on from there.
Just switch to 13-RELEASE, it's kickass.
 
Back
Top