Created attachment 148946 [details] dmesg.txt I consistently keep getting this problem for several years. dmesg ... error: [drm:pid12:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung info: [drm] capturing error event; look for more information in sysctl hw.dri.0.info.i915_error_state error: [drm:pid6:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer
Created attachment 148947 [details] pciconf_lvbce.txt
Created attachment 148948 [details] devinfo_vr.txt
Created attachment 148949 [details] hw.dri.0.info.i915_error_state.log-11.10.2013
Created attachment 148950 [details] hw.dri.0.info.i915_error_state.log1-02.12.2013
Created attachment 148952 [details] hw.dri.0.info.i915_error_state.log2-16.02.2014
Created attachment 148953 [details] hw.dri.0.info.i915_error_state.log3-04.06.2014
Created attachment 148954 [details] hw.dri.0.info.i915_error_state.log4-24.10.2014
Created attachment 148955 [details] hw.dri.0.info.i915_error_state.log5-30.10.2014
Created attachment 148956 [details] hw.dri.0.info.i915_error_state.log6-02.11.2014
Created attachment 149332 [details] hw.dri.0.info.i915_error_state.log7-12.11.2014
Someone who understands what to do with it all?
I am also seeing this on several Thinkpad T530 with Ivy Bridge graphics on 10.1-RELEASE. agp0: <IvyBridge mobile GT2 IG> on vgapci1 agp0: aperture size is 256M, detected 65532k stolen memory info: [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). info: [drm] Driver supports precise vblank timestamp query. drmn1: taking over the fictitious range 0xe0000000-0xf0000000 fbd1 on drmn1 VT: Replacing driver "vga" with new "fb". info: [drm] Initialized i915 1.6.0 20080730 error: [drm:pid12:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung info: [drm] capturing error event; look for more information in sysctl hw.dri.0.info.i915_error_state pid 969 (fluxbox), uid 0: exited on signal 6 (core dumped)
Created attachment 152206 [details] hw.dri.0.info.i915_error_state.txt (truncated)
A workaround for this is to disable DRI in xorg.conf (as found at [1]): Section "Device" Identifier "Card0" Driver "intel" Option "Shadow" "true" Option "DRI" "false" BoardName "Intel Corporation 82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device (rev 01)" BusID "PCI:0:2:0" EndSection [1] http://ubuntuforums.org/showthread.php?t=1739646&s=5e5d32babc31e48922fea23242195367&p=10922238#post10922238
(In reply to Lars Engels from comment #14) I would not like to give up while OpenGL...
You have RC6 enabled. info: [drm] Enabling RC6 states: RC6 on, RC6p on, RC6pp on Did you changed this manually, or driver mis-managed the setting ?
I don't know how I would have enabled that. :) sysctl or loader.conf?
(In reply to Konstantin Belousov from comment #16) Yes I changed this option manually in loader.conf drm.i915.enable_rc6 = 7 But disabling this option does not affect to reproduce bug. I found both guaranteed to reproduce the bug on my HW: use in Firefox html5 video playback, which is involved gstreamer with hardware video decoding. And after a while watching the video appears this bug. In other circumstances, is more difficult to understand because of what is happening bug. The only thing that would add - is widely used OpenGL WM - compton, or any other OpenGL WM.
On the non-working T530 the setting is not set in loader.conf.
Updated 10.1-BETA and 10.1-RC versioned bugs to 10.1-STABLE.
http://docs.freebsd.org/cgi/mid.cgi?20150608165138.GA24840
Is this still an issue on 10.2-PRERELEASE?
The console displays a lot of these messages: ... error: [drm:pid17:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer error: [drm:pid17:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer error: [drm:pid17:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer error: [drm:pid17:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer error: [drm:pid17:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer error: [drm:pid17:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer error: [drm:pid12:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung info: [drm] capturing error event; look for more information in sysctl hw.dri.0.info.i915_error_state info: [drm] Enabling RC6 states: RC6 on, RC6p on, RC6pp on error: [drm:pid12:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung info: [drm] Enabling RC6 states: RC6 on, RC6p on, RC6pp on error: [drm:pid12:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung info: [drm] Enabling RC6 states: RC6 on, RC6p on, RC6pp on error: [drm:pid1499:gen6_sanitize_pm] *ERROR* Power management discrepancy: GEN6_RP_INTERRUPT_LIMITS expected 18000000, was 12060000 error: [drm:pid12:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung info: [drm] Enabling RC6 states: RC6 on, RC6p on, RC6pp on error: [drm:pid1499:gen6_sanitize_pm] *ERROR* Power management discrepancy: GEN6_RP_INTERRUPT_LIMITS expected 18000000, was 12060000 error: [drm:pid12:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung info: [drm] Enabling RC6 states: RC6 on, RC6p on, RC6pp on error: [drm:pid12:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung info: [drm] Enabling RC6 states: RC6 on, RC6p on, RC6pp on error: [drm:pid17:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer error: [drm:pid17:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer error: [drm:pid17:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer error: [drm:pid17:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer error: [drm:pid17:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer error: [drm:pid17:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer error: [drm:pid17:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer error: [drm:pid17:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer error: [drm:pid17:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer error: [drm:pid17:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer error: [drm:pid17:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer error: [drm:pid17:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer error: [drm:pid17:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer error: [drm:pid17:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer error: [drm:pid17:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer error: [drm:pid17:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer error: [drm:pid17:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer error: [drm:pid17:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer error: [drm:pid17:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer error: [drm:pid17:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer error: [drm:pid17:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer error: [drm:pid17:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer error: [drm:pid17:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer error: [drm:pid17:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer error: [drm:pid17:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer error: [drm:pid17:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer error: [drm:pid17:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer error: [drm:pid17:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer error: [drm:pid17:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer error: [drm:pid17:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer error: [drm:pid17:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer error: [drm:pid17:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer error: [drm:pid17:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer error: [drm:pid17:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer error: [drm:pid17:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer error: [drm:pid17:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer error: [drm:pid17:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer error: [drm:pid17:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer error: [drm:pid17:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer error: [drm:pid17:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer error: [drm:pid17:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer error: [drm:pid17:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer error: [drm:pid17:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer error: [drm:pid17:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer error: [drm:pid17:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer error: [drm:pid17:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer error: [drm:pid17:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer error: [drm:pid17:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer error: [drm:pid17:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer error: [drm:pid17:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer error: [drm:pid17:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer error: [drm:pid17:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer error: [drm:pid17:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer error: [drm:pid17:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer error: [drm:pid17:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer error: [drm:pid17:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer error: [drm:pid17:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer error: [drm:pid17:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer error: [drm:pid17:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer error: [drm:pid17:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer error: [drm:pid17:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer error: [drm:pid17:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer error: [drm:pid17:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer error: [drm:pid1499:gen6_sanitize_pm] *ERROR* Power management discrepancy: GEN6_RP_INTERRUPT_LIMITS expected 180d0000, was 12060000 error: [drm:pid17:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer error: [drm:pid17:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer ...
As another data point, I get a lot of: Aug 2 13:14:18 sanna kernel: error: [drm:pid3:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer Aug 2 13:15:03 sanna kernel: error: [drm:pid3:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer messages but not the other ones so maybe there are two issues? I'm using 10.2-PRERELEASE (r285858) and a GMA950 video controller.
uname -a FreeBSD nonamehost.local 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r287198: Thu Aug 27 12:59:19 EEST 2015 ivan@nonamehost.local:/media/da0s1/obj/usr/src/sys/mk11 amd64 error: [drm:pid1475:gen6_sanitize_pm] *ERROR* Power management discrepancy: GEN6_RP_INTERRUPT_LIMITS expected 18000000, was 12000000 pid 1732 (gsettings-data-conv), uid 1001: exited on signal 5 pid 1789 (xfce4-power-manager), uid 1001: exited on signal 11 error: [drm:pid1475:gen6_sanitize_pm] *ERROR* Power management discrepancy: GEN6_RP_INTERRUPT_LIMITS expected 180d0000, was 18000000 pid 1699 (wrapper-1.0), uid 1001: exited on signal 10 pid 3428 (wrapper-1.0), uid 1001: exited on signal 11 error: [drm:pid1475:gen6_sanitize_pm] *ERROR* Power management discrepancy: GEN6_RP_INTERRUPT_LIMITS expected 000d0000, was 180d0000 error: [drm:pid12:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung info: [drm] capturing error event; look for more information in sysctl hw.dri.0.info.i915_error_state info: [drm] Enabling RC6 states: RC6 on, RC6p on, RC6pp on error: [drm:pid1475:gen6_sanitize_pm] *ERROR* Power management discrepancy: GEN6_RP_INTERRUPT_LIMITS expected 180d0000, was 12060000 error: [drm:pid12:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
Created attachment 160405 [details] hw.dri.0.info.i915_error_state.log-next
Created attachment 160406 [details] hw.dri.0.info.i915_error_state.log-next1
I am seeing this issue in 10.2-RELEASE{,-p1,-p2} through 10-STABLE. drm2 and i915kms was working for me in 10.1-RELEASE.
I just built kernel 10.1-RELEASE-p19 and can confirm drm2/i915kms and Xv are working great. I previously built kernels 11-CURRENT, 10-STABLE, 10.2-RELEASE-p2 and all had a broken drm2 with hung GPU that cannot be reset and broken Xv as described by Ivan Klymenko. For now, I am stuck running the 10.1-RELEASE-p19 kernel with my 10.2-RELEASE-p2 world until someone can take a look at what was introduced in 10.2 that broke drm2 for i915 chipsets. Thank you!
Created attachment 160959 [details] Makefile diffs between 10.1-RELEASE-p19 and 10.2-RELEASE-p2
Created attachment 160960 [details] dev/drm2 diffs between 10.1-RELEASE-p19 and 10.2-RELEASE-p2
Just a me too... The hardware is an Acer TM-B113: agp0: <SandyBridge mobile GT1 IG> on vgapci0 agp0: aperture size is 256M, detected 131068k stolen memory info: [drm] Initialized drm 1.1.0 20060810 drmn0: <Intel SandyBridge (M)> on vgapci0 info: [drm] MSI enabled 1 message(s) info: [drm] AGP at 0xb0000000 256MB I'm running 10.1/amd64 with: libdrm-2.4.65_1,1 xf86-video-intel-2.21.15_9 xorg-server-1.17.4,1 The hang has started recently (or at least its incidence has increased a lot). There is no day I can work with this laptop without one/two hangs. This is very annoying, so I'm looking for help on one side and offering to do any testing on the other. Thanks.
Created attachment 163422 [details] drm error edited+comments
This machine seems to "hang" while left unattended. Have never had the problem while editing etc. Information and comments in link.
Comment on attachment 163422 [details] drm error edited+comments This machine seems to "hang" while left unattended. Have never had the problem while editing etc. Information and comments in link.
Created attachment 164264 [details] hw.dri.0.info.i915_error_state_15.12.2015
Try adding <drm.i915.semaphores="1"> to </boot/loader.conf>. I have tested this for over 1wk now and have not had any hangs. I cannot find running instances of additional drm semaphores in my system. Maybe someone can tell me how to trap them? Hope this works for you as well. Happy New Year rhs
(In reply to rhs from comment #37) At first glance it seems to help get rid of the problem, but ... I got in the moments of X full lock system. Perhaps in these moments just happen GPU hung without the option drm.i915.semaphores = "1"
First of all, this bug has been open 14 months. I would like to believe there are fbsd developers left out there that care about laptop/desktop issues, and so I wait. I upgraded to 10.2-RELEASE multiple times to try each "fix" and then downgraded back to 10.1-RELEASE to have a working Xv acceleration again, but at this point I will wait until I see a code fix enter the 10.2-RELEASE branch rather than try any more "workarounds" (and a clue for other users, it is in the drm2 driver not drm), or wait and see if 10.3-RELEASE incorporates changes from 11-CURRENT that fix the i915kms/drm2 code. This bug is the result of the import of Linux kernel modeset driver code that brought the bug along with the version that was copied. If you search through Linux kernel bug reports you'll see they had the same issue, and freebsd svn logs confirm the wholesale import. Looking through the latest 11-CURRENT branch, I see some attempts in the code to stop the GPU hung messages from appearing but personally have not tested if that is a cosmetic bandaid or not.
(In reply to Ivan Klymenko from comment #38) I followed your suggestion and added this tweak a few work days ago: so far, so good. I have never experienced a lockup since; however these lockups were not so frequent lately in any case, so it's hard to tell for sure whether this solved. I'll let you know if my GPU locks up again. Thanks.
This (drm2) is fixed in 10.3-RELEASE.
Apparently fixed in 10.3-RELEASE.
uname -a FreeBSD nonamehost.local 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r299257: Mon May 9 16:26:05 EEST 2016 ivan@nonamehost.local:/media/da0s1/obj/usr/src/sys/mk11 amd64 ... error: [drm:pid12:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung info: [drm] capturing error event; look for more information in sysctl hw.dri.0.info.i915_error_state error: [drm:pid0:i915_reset] *ERROR* Failed to reset chip.
Created attachment 170154 [details] hw.dri.0.info.i915_error_state_09.05.2016
Not fixed, ok? I still get this as of 11.1 -- and been since 10.0 or before, thinking it was my hardware. I found a more or less reliable way to cause it: do a lot of 2D graphics -- like drawing something in graphics/inkscape or in WED from games/xptools. Happens at least once in half an hour and is very annoying. I don't know if related, but I also often get corruption like missing/blinking characters in fonts, broken transparency and black areas with dark blue dots that sometimes move/blink. Sometimes they show up in 3d textures as well. Should I attach hw.dri.0.info.i915_error_state next time this happens? Or could anyone at least point me to a setting in the kernel sources defining how often the hangcheck happens -- so that I have to wait only 10 seconds instead of sitting there for a whole minute each time it hangs? Cheers, Mike
Actually I mean from 10.something, haven't seriously used intel graphics before that, maybe it was something else.
(In reply to Michael Danilov from comment #45) For all these years the problem has not been resolved. I ran out of patience - I closed this bug report with sarcasm that "Works As Intended".
Yes bugs suck. Bugs that have been reported but not fixed suck more. But I'd rather have a record of us sucking than closing more bugs.
Have you tried drm-next-kmod or drm-stable-kmod? It's the new graphics drivers for intel graphics cards, and radeon graphics cards.
(In reply to Niclas Zeising from comment #49) No. I use Linux for several years. At that time there were no such ports.
Is it supported on 11.x? The IGNORE message for 11.x says it is "not supported on 10.x or older", but it is still IGNORE for 11.x.
(In reply to Michael Danilov from comment #51) graphics/drm-stable-kmod is supported on 11 stable and the upcoming 11.2 release.
Ok, that means just waiting for at least 3 months. Is there a way to force the hangcheck to happen more often then? I have not found any variable defining the interval in kernel sources.
Created attachment 193086 [details] Kernel kludge: reduce the "hung" wait from 60s to 6s. Alright, I asked several times and no one told me, so I found out myself eventually. Might help someone else survive till 11.1.
11.2*
Still happening with graphics/drm-stable-kmod.
(In reply to Michael Danilov from comment #56) Can you try with drm-next-kmod as well? Regards Niclas
Sure, doing it now, will report back.
Hi What DDX driver are you using? If Intel, try switching to/from sna/uxa. Recommended though is the modesetting driver. I have seen hung GPU sometimes with Intel but I don't remember if it was sna or uxa. Either way, Intel DDX is kind of deprecated and modesetting is very stable now. Try with this in your xorg.conf Section "Device" Driver "modesetting" EndSection or simply uninstall xf86-video-intel and it will use modesetting by default.
Yes it still hangs with -next. That's right, I am using the intel driver. I vaguely remember trying out modesetting, and that it either wasn't friends with vt console, or didn't work at all -- so I went back to intel. I will try different combinations in the evening.
But I've just tried modesetting again and it works! \o/ Must have been it was not ready back then. Will report back if it still hangs...
Well I haven't seen any hangs yet but I still do get trash rectangles on screen sometimes, so something is wrong even with modesetting.
Anyone? Why does it corrupt sometimes?
(In reply to Michael Danilov from comment #63) What is your OS version/revision and drm driver version (stable/next/devel)?
(In reply to Michael Danilov from comment #63) And what is your hardware?
FreeBSD 11.2-RELEASE-p2 drm-next-kmod-4.11.g20180822 (updated today from some version around July, but I think I've already seen corruption again) Lenovo B570e Intel(R) Core(TM) i7-2820QM CPU @ 2.30GHz
(In reply to Michael Danilov from comment #66) Hi! Is this still an issue with the latest driver update? Have you tried FreeBSD 12?
I haven't been able to update my ports since November beccause https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235075 I might try doing that separately on the driver ports. Thanks for reminding of 12, didn't know it's already been released, will try.
Just updated to 12. Not sure if hangs are still there but I've already seen corruption rectangles with the base system kernel module...
I tried updating a copy of ports svn an copying over the ports and then running svn resolve on them, but svn resolve never ends and freezes on "Resolving [some revision number here]....".
Rather "Checking r462619..."
Try your luck on FreeBSD >= 13.0 as drm-kmod received a number of bug fixes for old GPUs and switched to upstream LTS branch. On older versions DRM is pretty much frozen except occasional fixes contributed by others e.g., https://github.com/FreeBSDDesktop/kms-drm/pull/226
Hi All, I'm on 12.2 Release and my logs does show this issue is happening as well: ep 25 12:00:07 Dell kernel: error: [drm:pid12:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung Sep 25 12:00:07 Dell kernel: info: [drm] capturing error event; look for more information in sysctl hw.dri.0.info.i915_error_state Sep 25 12:00:07 Dell kernel: error: [drm:pid0:i915_reset] *ERROR* Failed to reset chip. Sep 25 13:42:46 Dell kernel: . Sep 25 13:43:18 Dell devd[534]: notify_clients: send() failed; dropping unresponsive client Sep 25 13:43:18 Dell syslogd: last message repeated 1 times Sep 25 13:43:19 Dell kernel: Sep 25 13:43:19 Dell kernel: error: [drm:pid3309:assert_pll] *ERROR* PLL state assertion failure (expected on, current off) Sep 25 13:43:19 Dell syslogd: last message repeated 1 times Sep 25 13:43:19 Dell kernel: error: [drm:pid3309:assert_pipe] *ERROR* pipe A assertion failure (expected on, current off) Sep 25 13:43:20 Dell kernel: error: [drm:pid3309:intel_enable_lvds] *ERROR* timed out waiting for panel to power on Sep 25 13:43:20 Dell kernel: error: [drm:pid3309:intel_modeset_check_state] *ERROR* encoder's hw state doesn't match sw tracking (expected 1, found 0) Sep 25 13:43:20 Dell kernel: error: [drm:pid3309:assert_pipe] *ERROR* pipe A assertion failure (expected on, current off) Sep 25 13:43:27 Dell kernel: . This usually occurs if I leave my laptop on overnight or in the middle of watching video, the screen will go dead as you can visibly see the image few seconds after and a restart puts the screen back on.
(In reply to Zhong from comment #73) I wanted to add that the way to reproduce this is to run cheese which uses the webcam. The new i915 driver doesn't support my native resolution but appears to be able to open cheese so I'll check back to see if I can get the driver from the module directory to work.
Back when I used FreeBSD, the hangs were prevalent on Blender, and this could be related: https://gitlab.freedesktop.org/mesa/mesa/-/issues/3748
(In reply to Zhong from comment #74) It appears the screen won't load when trying to use the driver from the port. It's best for me to other options.
Is this still happening on >=13 ?
(In reply to Emmanuel Vadot from comment #77) yes. the system gets pretty much unusable after 10-15 minutes in load. Tried with 13.1-RELEASE, 13.2-STABLE and 14-CURRENT