From owner-freebsd-alpha  Mon Apr 24 14:16:48 2000
Delivered-To: freebsd-alpha@freebsd.org
Received: from news-ma.rhein-neckar.de (news-ma.rhein-neckar.de [193.197.90.3])
	by hub.freebsd.org (Postfix) with ESMTP id 5172237BC17
	for <freebsd-alpha@freebsd.org>; Mon, 24 Apr 2000 14:16:45 -0700 (PDT)
	(envelope-from daemon@bigeye.rhein-neckar.de)
Received: from bigeye.rhein-neckar.de (uucp@localhost)
	by news-ma.rhein-neckar.de (8.8.8/8.8.8) with bsmtp id XAA06436
	for freebsd-alpha@freebsd.org; Mon, 24 Apr 2000 23:16:44 +0200 (CEST)
	(envelope-from daemon@bigeye.rhein-neckar.de)
Received: (from daemon@localhost)
	by bigeye.rhein-neckar.de (8.9.3/8.9.3) id VAA96562
	for freebsd-alpha@freebsd.org; Mon, 24 Apr 2000 21:37:47 +0200 (CEST)
	(envelope-from daemon)
From: naddy@mips.rhein-neckar.de (Christian Weisgerber)
Subject: vidcontrol kills 4.0-STABLE
Date: 24 Apr 2000 21:37:46 +0200
Message-ID: <8e27qa$2u90$1@bigeye.rhein-neckar.de>
To: freebsd-alpha@freebsd.org
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Apparently I have managed to crash 4.0-STABLE on alpha (AXPpci33
with VGA) by doing a simple

# vidcontrol -i adapter </dev/ttyv0

I'm not sure what happened exactly since I won't have access to
the console before tomorrow. The box doesn't respond to ping and
it doesn't get up again, so it looks pretty fatal.

Can anybody else reproduce this?

Are there any areas of syscons/framebuffer functionality that aren't
available on alpha? (Kazu, are you on freebsd-alpha?)

-- 
Christian "naddy" Weisgerber                  naddy@mips.rhein-neckar.de



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message