This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


RE: [Xen-devel] crashes

To: Andy Isaacson <adi@xxxxxxxxxxxxx>, Ian Pratt <Ian.Pratt@xxxxxxxxxxxx>
Subject: RE: [Xen-devel] crashes
From: James Harper <JamesH@xxxxxxxxxxxxxxxx>
Date: Fri, 30 Jul 2004 13:53:37 +1000
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxxxx>
Delivery-date: Fri, 30 Jul 2004 05:02:25 +0100
Envelope-to: steven.hand@xxxxxxxxxxxx
In-reply-to: <20040730033233.GB29331@xxxxxxxxxxxxx>
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
References: <BFCDB849-C89D-47E0-94B8-D2942756B52C@mimectl> <E1BqLQq-0005TF-00@xxxxxxxxxxxxxxxxx>, <20040730033233.GB29331@xxxxxxxxxxxxx>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
Thread-index: AcR16Mtbn1Wq3OwYRrCXQJbjaQVwqA==
Thread-topic: [Xen-devel] crashes
cool, thanks. It looks like i can just fiddle with values in /etc/console-tools/config under debian, now that I know what i'm looking for.
hopefully next time I crash it I can see what's what. I'll probably have to hook up a serial console eventually but that will involve sitting there with my laptop which I don't have time to do presently.
thanks again.

From: Andy Isaacson
Sent: Fri 30/07/2004 1:32 PM
To: Ian Pratt
Cc: James Harper; xen-devel@xxxxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] crashes

On Fri, Jul 30, 2004 at 01:39:26AM +0100, Ian Pratt wrote:
> >When I went to look at the screen after a hang to see if there
> >was an oops or anything like it, the screen was blanked and
> >wouldn't wake up - anyone know how to stop that behaviour?
> That's Linux behaviour -- not a lot we can do about
> it. Collecting crash messages is much easier if you have an
> attached serial line...

man 1 setterm.  The command you want is "setterm -blank 0", which should
probably go in an initscript somewhere.  I think some distributions have
an /etc/ file with a switch for you to toggle, but not the ones I'm
using right now...

<Prev in Thread] Current Thread [Next in Thread>