From owner-freebsd-stable Tue Feb 20 05:19:43 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id FAA12329 for stable-outgoing; Tue, 20 Feb 1996 05:19:43 -0800 (PST) Received: from asstdc.scgt.oz.au (root@asstdc.scgt.oz.au [202.14.234.65]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id FAA12322 for ; Tue, 20 Feb 1996 05:19:41 -0800 (PST) Received: (from imb@localhost) by asstdc.scgt.oz.au (8.6.12/BSD4.4) id AAA06513 for stable@freebsd.org; Wed, 21 Feb 1996 00:19:33 +1100 From: michael butler Message-Id: <199602201319.AAA06513@asstdc.scgt.oz.au> Subject: reboot when using vidcontrol To: stable@freebsd.org Date: Wed, 21 Feb 1996 00:19:32 +1100 (EST) X-Mailer: ELM [version 2.4 PL24beta] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-stable@freebsd.org Precedence: bulk I have three machines which will each intermittently reboot .. screen goes blank then back to the BIOS memory test .. when using vidcontrol :-( I have no idea what causes it although since I only ever run vidcontrol immediately after a shutdown, there may be some backlogged network activity starting up (deferred sendmail activity started by secondary MX receivers). Whilst I don't believe this has any direct impact, the timing variance incurred by the extra load may. The most affected is the slowest (this machine), a 386DX/40. The exact command-line I use is "vidcontrol VGA_80x30" but I've seen it once with 80x50. Anybody have any thoughts ? BTW .. it also happened before the recent syscons changes so I don't believe they're related, michael