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

[Chris]

On Sat, 2015-02-21 at 16:46 +0000, Colin Law wrote:
> On 21 February 2015 at 15:51, Chris <cpollock at embarqmail.com> wrote:
> > On Sat, 2015-02-21 at 14:54 +0000, Colin Law wrote:
> >> On 21 February 2015 at 14:27, Chris <cpollock at embarqmail.com> wrote:
> >> > Now I'm more confused than ever about these 'lockups' I've been
> >> > experiencing. The system has 'hung' twice in two days almost exactly
> >> > 36hrs apart. The first was at 07:18:55 on 19 Feb, the next was last
> >> > night at 19:16:40 on the 20th. I'm going by the times shown on the clock
> >> > which I have set to show seconds. I'd installed kernel
> >> > 3.19.0-031900-generic #201502091451 SMP Mon Feb 9 14:52:52 UTC 2015
> >> > x86_64 x86_64 x86_64 GNU/Linux on the 18th at 5:34pm. What I'm seeing
> >> > now instead of the 'Hangcheck' error is noted here at pastebin:
> >> >
> >> > http://pastebin.com/FEff5yy2
> >> >
> >> > I know I've asked this question before and one response is that it was
> >> > informational messages from the video driver. I don't remember seeing
> >> > these when I'm running the 3.13.0-45 kernel is this just particular to
> >> > the 3.19 kernel? Is there possibly something with the video driver
> >> > causing the 'lockups'?
> >> >
> >> > The output of dpkg -l | grep xorg | intel:
> >> >
> >> > dpkg -l | grep xorg | grep intel
> >> > ii  xserver-xorg-video-intel
> >> > 2:2.99.910-0ubuntu1.4 amd64
> >> > X.Org X server -- Intel i8xx, i9xx display driver
> >>
> >> I don't know what those messages mean but they don't look like the
> >> sort of thing that would cause a lockup.
> >>
> >> Can you confirm that you have run the ramcheck (from boot options)
> >> overnight for several nights (or/and days) so you can be absolutely
> >> certain you do not get lockup whilst running that?
> >>
> >> Colin
> >>
> >
> > I haven't run it lately Colin however I did run it several nights when
> > the 'hangcheck' problem first started. I'll go back and run it today for
> > awhile since I have other projects going on and see what happens.
> 
> If you ran it for long enough then to confirm that it does not hang
> then probably don't need to do it again.
> No harm repeating that though, the trickiest problems to fix can be
> those with multiple causes, so fixing one does not completely fix it
> and you think it has not helped.
> 
> Colin
> 
After your reply this morning Colin I booted up to memtest86+ and ran it
for over 5hrs, just booted back to kernel 3.13.0-45 to see what happens.
I'm betting that the 'hangcheck' error comes back and the other one goes
away. 

Chris

-- 
Chris
KeyID 0xE372A7DA98E6705C
31.11°N 97.89°W (Elev. 1092 ft)
15:26:28 up 4 min, 1 user, load average: 3.45, 3.06, 1.36
Ubuntu 14.04.1 LTS, kernel 3.13.0-45-generic