cpollock at embarqmail.com
Wed Feb 18 14:39:23 UTC 2015
On Wed, 2015-02-18 at 14:22 +0000, Colin Law wrote:
> On 18 February 2015 at 13:23, Chris <cpollock at embarqmail.com> wrote:
> > On Wed, 2015-02-18 at 09:35 +0000, Colin Law wrote:
> >> On 17 February 2015 at 23:52, Chris <cpollock at embarqmail.com> wrote:
> >> > ...
> >> > There's one person notified of all changes to the bug, a whole slew that
> >> > could possibly be notified. FWIW I just had another 'lockup' at 5:19pm
> >> > with the same kernel error as I'd shown before. Added a comment to both
> >> > the Ubuntu and freedesktop.org bugs. Shoot, I've even gone to the
> >> > #ubuntu-kernel IRC channel and asked what the status of the bug is,
> >> > still no replies. I used to get more help when I was running Mandriva!
> >> >
> >> > Am I ranting, yes, in a way, I try not to get too excited, not good for
> >> > me at my age.
> >> I think the biggest problem is probably that the bug  is only
> >> marked as affecting one person. I guess most effort is bound to be
> >> placed on bugs affecting more people.
> >> I wonder if it is possible that it is in fact an intermittent hardware
> >> issue on your machine.
> >> Have you tried running the ram check overnight for a few days.
> >> Colin
> >>  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1402331
> > Ah, but check out the same bug report at freedesktop.org Colin
> > https://bugs.freedesktop.org/show_bug.cgi?id=75394
> > and you'll see if affects more than just one person, flavor, or
> > hardware.
> Well it is marked High, Critical there so I doubt if there is much
> more you can do. Since no-one there has asked for further input from
> you I guess you will just have to wait in hope. Did you say you were
> going to revert to the most recent kernel that did not exhibit the
> A possibly relevant question, do you use suspend (or hibernate for
> that matter)? If so has it ever failed before the first suspend and
> does it always resume from suspend ok?
Don't use either Colin, I have X-Screensaver running and have gotten
'lockups' both with and without it. I tried reverting to 3.13.0-35 which
I 'believe' was the last good kernel however after booting the cursor
was not present and I could not log in (pressed 'enter' at log-on
screen, to no effect).
31.11°N 97.89°W (Elev. 1092 ft)
08:36:04 up 15:16, 1 user, load average: 0.47, 0.38, 0.36
Ubuntu 14.04.1 LTS, kernel 3.13.0-45-generic
More information about the ubuntu-users