public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Chris <cpollock@embarqmail.com>
To: Mike Lothian <mike@fireburn.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: Approximately every other day video will freeze for no reason at all and no specific time between freezes.
Date: Sun, 04 Oct 2015 09:23:17 -0500	[thread overview]
Message-ID: <1443968597.29026.39.camel@embarqmail.com> (raw)
In-Reply-To: <CAHbf0-Hx5SZNmVR7+nHX17sKOvGsaEr1sM=10khkmJUnL35s5Q@mail.gmail.com>

On Sun, 2015-10-04 at 12:01 +0000, Mike Lothian wrote:
> Hi
> 
> I'm not certain but I think I faced the same issue when I was enabling
> atomic on my sandybridge laptop, it was like one of the planes stopped
> being updated. When I reported it all that time ago I was told atomic
> was considered unstable and I shouldn't be using it.
> 
> Has atomic been switched on recently?
> 
> Unfortunately the laptop is no longer functional so I can't test any
> of this out
> 
> Mike
> 
> 
> On Sun, 4 Oct 2015 10:32 Martin Steigerwald <martin@lichtvoll.de>
> wrote:
> 
>         Hi Chris, hi Intel graphics developers,
>         
>         Am Freitag, 2. Oktober 2015, 16:06:30 CEST schrieb Chris:
>         > To elaborate on this. The video is frozen to include the
>         clock however I
>         > can move the mouse cursor around the screen. I can not
>         however switch
>         > between window desktops. This happened on 28 Sept 2015 after
>         an uptime
>         
>         I have seen exactly this issue on ThinkPad T520 with
>         Sandybridge graphics.
>         
>         With one exception: At least sometimes I have been able to
>         switch to tty1 and
>         do killall -u <affecteduser> to get back to sddm login screen.
>         
In my case I'm able to SSH into the box from my tablet and save any
pertinent log files. I've attached them to my two bug reports noted in
my earlier post but I don't know if they actually show anything or not.
Each time there is a freeze I run, per Chris Wilson of this list,
cat /sys/class/drm/card0/error which always reports 'no error state
collected'. I also run cat /sys/kernel/debug/dri/0/i915_swizzle_info
again as requested by Chris Wilson. The results are always the same

bit6 swizzle for X-tiling = none
bit6 swizzle for Y-tiling = none
DDC = 0x00200010
DDC2 = 0x00300030
C0DRB3 = 0x0030
C1DRB3 = 0x0010

And not knowing what I'm looking for I don't know if the above is ok or
not. 

I get into a real quandary when the guru's here in this list ask me to
try something such as running kernel 4.0.0-997-generic #201503310205 SMP
Tue Mar31 02:07:04 UTC 2015 from here
http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-next/ 
then when I go to report it at Ubuntu I'm told don't run this kernel
it's unsupported run this one 3.19.0-30-generic #33~14.04.1-Ubuntu SMP.
After noting a freeze after 1 1/2 days I was told by the Ubuntu Guru to
start with the newest upstream kernel from here
http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D and to attempt
install until I got one to work which in this case was kernel
4.2.3-040203-generic #201510030832 SMP Sat Oct 3 12:34:31 UTC 2015. 

This 'video freeze' issue actually started back on 09/13/2014 when at
that time my syslog would show kernel: [173977.808008]
[drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... render
ring idle. At that time I was running kernel Ubuntu 3.13.0-36.63-generic
3.13.11.6. This continued on through Ubuntu kernel versions
3.13.0-37.64-generic 3.13.11.7, 3.13.0-39.66-generic 3.13.11.8,
3.13.0-40.69-generic 3.13.11.10, 3.14.0-031400-generic,
3.13.0-44.73-generic 3.13.11-ckt12, 3.13.0-45.74-generic 3.13.11-ckt13,
3.19.0-031900-generic (kernel@tangerine) During this freeze I noticed
the following in my syslog - this was all prior to my reboot right after
the freeze - http://pastebin.com/MpfiGqLe Continuing with kernel
versions affected- 3.13.0-46.76-generic 3.13.11-ckt15,
4.0.0-040000rc2-generic - when running this kernel another trace was
generated http://pastebin.com/VghUmcjx booted into kernel
4.0.0-040000rc4-generic call trace generated here also -
http://pastebin.com/RdbWfFYb booted into kernel 4.0.0-997-generic from
here http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-next/ which
at the time was the most current.

I'd be happy to provide any other information that I can. The
'hangcheck....'error is no longer seen even though the freeze symptoms
remain the same.

Chris

-- 
Chris
KeyID 0xE372A7DA98E6705C
31.11°N 97.89°W (Elev. 1092 ft)
07:53:45 up 22:47, 1 user, load average: 1.40, 0.91, 0.46
Ubuntu 14.04.3 LTS, kernel 4.2.3-040203-generic #201510030832 SMP Sat
Oct 3 12:34:31 UTC 2015

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2015-10-04 14:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-02 21:06 Approximately every other day video will freeze for no reason at all and no specific time between freezes Chris
2015-10-03 18:54 ` Mike Lothian
2015-10-03 20:35   ` Chris
2015-10-04  9:26 ` Martin Steigerwald
2015-10-04 12:01   ` Mike Lothian
2015-10-04 14:23     ` Chris [this message]
2015-10-04 14:32     ` M. Thierry
2015-10-04 16:41       ` M. Thierry
2015-10-05  9:05         ` Mike Lothian

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1443968597.29026.39.camel@embarqmail.com \
    --to=cpollock@embarqmail.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=mike@fireburn.co.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox