display watermark is too large(92/63), disabling

[Chris]

On Sun, 2015-02-22 at 15:32 +0000, Colin Law wrote:
> On 22 February 2015 at 15:14, Colin Law <clanlaw at gmail.com> wrote:
> > On 22 February 2015 at 14:56, Chris <cpollock at embarqmail.com> wrote:
> >> ...
> >> Colin, just a note, I've switched back to the 3.13.0-45 generic kernel
> >> and the 'watermark....' notations in my syslog have disappeared. This
> >> tells me that something in the 3.19.* kernel is causing this. I expect
> >> the 'hangcheck' lockup issue to reappear at any time now. Probably
> >> sometime later today or tomorrow. This whole thing is becoming annoying
> >> especially when I keep adding to the two bug reports and no advice is
> >> forthcoming.
> >
> > If the hangcheck problem does not appear with with the later kernel
> > then it seems that particular problem has been fixed in that kernel.
> > Time to move on and look at the other lockup problem perhaps.  Since
> > the original bug is particularly talking about hangcheck then this may
> > be a different problem entirely.
> >
> > The messages you pasted look as if they are from the graphics
> > initialisation, were the messages just before the hang?  Were you
> > doing anything with the displays at that time (Feb 20 19:17:29)?
> 
> Actually I think I am wrong, I think they may be debug output
> following the detection of a problem.  If you google for
> intel_dump_pipe_config you will find quite a lot of recent discussion
> about the problem, though I have not tracked down an actual bug.  Are
> you also seeing a message about vblank timeout that is being discussed
> along with the dump stuff?  It looks like it is currently being
> addressed.  I don't think your problems are being ignored , I think
> those looking at it (intel guys I think) have enough data of their own
> to be looking at it.  You would not expect much action on the ubuntu
> bug as it is nothing that the ubuntu team can do anything about, it is
> the intel driver (I think).
> 
> Colin
> 
> >
> > Colin
> 
Colin, I believe I should go back to the 3.19.0 kernel, I don't know if
there is a 3.20.rc* out yet perhaps I should also look for that. The
below link is to my latest comment on the bug at Launchpad in the kernel
mailing list archive, I also posted the same thing on the
freedesktop.org bug. I also have added this line to my /etc/default/grub
file GRUB_CMDLINE_LINUX_DEFAULT="drm.debug=0x66" which gives a lot of
output (this was suggested I believe on the bug report at
freedesktop.org). You asked in your previous post about 19:17:29 on 20
Feb, here is the output during that time period -
http://pastebin.com/iHZ6mkHt

As I said I'm going to bump back up to the 3.19.0 kernel and next time a
lockup occurs create a bug report at freedesktop.org and only there.

If you have any other ideas they'd be greatly appreciated.

Chris

-- 
Chris
KeyID 0xE372A7DA98E6705C
31.11°N 97.89°W (Elev. 1092 ft)
12:14:24 up 20:52, 1 user, load average: 0.34, 0.31, 0.32
Ubuntu 14.04.1 LTS, kernel 3.13.0-45-generic