Bug #1887

System freeze - with logo_saver and high CPU load

Added by steve over 3 years ago. Updated over 3 years ago.

Status:NewStart date:
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:-
Target version:-

Description

Hi,

I'm running v2.9.0.68.g57eab-DEVELOPMENT on an M4A78L motherboard
with a Phenom II 955 (quad core 3.2 GHz), however this has been happening
for a while but it's only now that I've pinned down the circumstances.

If I have the logo-saver running and displayed on the console then
anything that generates a high CPU load (make -j 8 buildworld in an ssh
session from another box does nicely) will lock the system up solid when the
logo reaches a certain point near the top right hand side. Once locked the
system is completely unresponsive to network or keyboard, only a reset or
power cycle will unlock it. Without the logo_saver running the system is as
solid as a rock.

History

#1 Updated by dillon over 3 years ago

: Hi,
:
: I'm running v2.9.0.68.g57eab-DEVELOPMENT on an M4A78L motherboard
:with a Phenom II 955 (quad core 3.2 GHz), however this has been happening
:for a while but it's only now that I've pinned down the circumstances.
:
: If I have the logo-saver running and displayed on the console then
:anything that generates a high CPU load (make -j 8 buildworld in an ssh
:session from another box does nicely) will lock the system up solid when the
:logo reaches a certain point near the top right hand side. Once locked the
:system is completely unresponsive to network or keyboard, only a reset or
:power cycle will unlock it. Without the logo_saver running the system is as
:solid as a rock.
:
:--
:Steve O'Hara-Smith | Directable Mirror Arrays

The syscons console screen saver code in general is a real problem
for us. It's getting hung up on the console spin lock. I think it
is going to be a while before it gets fixed (it won't make the release).

We've whacked a couple of issues related to syscons but not this one
yet.

-Matt
Matthew Dillon
<>

#2 Updated by steve over 3 years ago

On Thu, 28 Oct 2010 14:52:36 -0700 (PDT)
Matthew Dillon <> wrote:

...
> The syscons console screen saver code in general is a real problem
> for us. It's getting hung up on the console spin lock. I think it
> is going to be a while before it gets fixed (it won't make the
> release).

Not a big problem - it's not easy to get caught by this one
(I only found it because I started running the box without a monitor and
didn't think about disabling the screen saver).

Also available in: Atom PDF