From owner-freebsd-current Thu Apr 2 06:03:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA15005 for freebsd-current-outgoing; Thu, 2 Apr 1998 06:03:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ache.relcom.ru (ache@ache.relcom.ru [193.125.20.108]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA14962; Thu, 2 Apr 1998 06:02:34 -0800 (PST) (envelope-from ache@ache.relcom.ru) Received: (from ache@localhost) by ache.relcom.ru (8.8.8/8.8.8) id SAA00273; Thu, 2 Apr 1998 18:01:38 +0400 (MSD) (envelope-from ache) Message-ID: <19980402180138.10633@nagual.pp.ru> Date: Thu, 2 Apr 1998 18:01:38 +0400 From: =?koi8-r?B?4c7E0sXKIP7F0s7P1w==?= To: yokota@FreeBSD.ORG, bugs@dyson.iquest.net, sos@FreeBSD.ORG Cc: current@FreeBSD.ORG Subject: -current reboot & vidcontrol mode switching Mail-Followup-To: yokota@freebsd.org, bugs@dyson.iquest.net, sos@freebsd.org, current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I found that vidcontrol text videomode switching (called from my .login) often cause silent reboot or lockup with latest dyson VM changes. It seems some hardware page not present at the moment of the switching or something similar processor related. -current before last big VM changes round not have this problem (since vidcontrol mode switching was in my .login for years due to lack of -all-the-screens- mode switching syscons ability) -- Andrey A. Chernov http://www.nagual.pp.ru/~ache/ MTH/SH/HE S-- W-- N+ PEC>+ D A a++ C G>+ QH+(++) 666+>++ Y To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message