On Tue, Sep 20, 2016 at 12:30 PM, Dusty Mabe <du...@dustymabe.com> wrote:
> Several times over the past month my t460s has just blank screens
> when I come back to it after some time. I don't know if the thing
> froze up completely or if it is just the display not working. I lock
> my screens (laptop + 2 external monitors) and then leave for an hour
> or so. When I come back no attempt at input will get the lockscreen
> to appear. I have to power down and then back up.
> After boot I look at the journal and I always tend to see some of
> [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO
> [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe C
> (start=167156 end=167157) time 146 us, min 1073, max 1079, scanline start
> 1072, end 1082
> [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A
> (start=488827 end=488828) time 107 us, min 1073, max 1079, scanline start
> 1072, end 1080
> I'm not saying these are what is causing the issue but are at least
> something I noticed.
> I'll continue to monitor this problem. It only happens like once every
> two weeks so it is hard to prepare for it by knowing the IP address so
> that I can try to ssh in to see if the system is frozen or if it is
> just the screen.
> Has anyone else seen some behavior like this? I am using i3wm and my
> system is updated approximately once a week, so I should have close to
> the latest software installed.
> devel mailing list -- email@example.com
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
I ran in to a problem that involved an unresponsive screen a few months ago
and also had a FIFO underrun. I think your problem is somewhere in the
intel graphics stack. Here's the bug I had:
I was able to determine the system wasn't frozen because I made a unit file
that ran a bash script that saved a file on shut down and then pressed my
power button. Systemd ran the script and I was able to see the file had
been updated. The fact that it was able to shutdown without me forcing it
was also a good sign that this was the case.
Some info about reporting these bugs is here:
If you want to try some drivers that are close to the developer version
upstream you can try my copr repo:
It hasn't been updated in a month. I'm going to get on that today. I try
for once a week but since I no longer have any bugs I don't run it on my
machine and so I forget easily. Note that running these is probably crazy
experimental and the package maintainer(me) is far from an expert.
devel mailing list -- firstname.lastname@example.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org