Date: Wed, 4 Jul 2001 12:48:20 +0300 From: Giorgos Keramidas <keramida@ceid.upatras.gr> To: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp> Cc: bugs@freebsd.org Subject: Re: syscons lockups Message-ID: <20010704124820.A86698@hades.hell.gr> In-Reply-To: <200107021032.TAA27394@zodiac.mech.utsunomiya-u.ac.jp>; from yokota@zodiac.mech.utsunomiya-u.ac.jp on Mon, Jul 02, 2001 at 07:32:38PM %2B0900 References: <20010702005928.B3836@hades.hell.gr> <200107020114.KAA23077@zodiac.mech.utsunomiya-u.ac.jp> <20010702072438.A5371@hades.hell.gr> <200107021032.TAA27394@zodiac.mech.utsunomiya-u.ac.jp>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Jul 02, 2001 at 07:32:38PM +0900, Kazutaka YOKOTA wrote:
> Would you run a shell script like the following in a vty
> and redirect stdout and stderr to a file to capture error messages?
> (I expect you will still get back to the text mode display even
> if the VESA mode fails.)
>=20
> vidcontrol VESA_800x600
> vidcontrol 80x25
I did test this with a little modified version of the above script.
#!/bin/sh
=20
logfile=3D"./vidcontrol.log"
/bin/true > "${logfile}"
=20
mount >> "${logfile}" 2>&1
echo '=07Setting mode to VESA_800x600'
sync;sync;sync
vidcontrol VESA_800x600 >> "${logfile}" 2>&1 && exit 0
sleep 5
/bin/ls /root
sleep 5
sync;sync;sync
echo '=07Resetting mode to 80x25...'
vidcontrol 80x25 >> "${logfile}" 2>&1
echo 'Done.'
The funny thing about this is that:
When I run this script after I have done `init 1' and mounted all my
filesystems (except for / that needs to be writable) in /root as the
superuser, it works. The mode changes, and I can work in VESA_800x600
while in single user mode. Nothing is printed in /root/vidcontrol.log
as an error message from vidcontrol. I removed the allscreen_flags
from rc.conf and changed the mode in this way. Then I exited from
single user mode, bringing the system back to multiuser. The virtual
consoles seem to work in the changed mode correctly after this!
When I run this script as the superuser when more than one consoles
are active (for instance, when I am in multiuser mode, with the
default getty's running on consoles ttyv0 - ttyv7), then the same
black screen appears, and the mode change seems to have completed, but
I can't see anything but a black screen. On attempt to change the
current virtual console to something other than ttyv0 that I did ran
this script on, starts beeping on the console. The beep is not the
normal error beep, since it does not last for a few milliseconds, but
continues in the same pitch without stopping. The file vidcontrol.log
still does not contain anything. This is probably not because
vidcontrol did not print an error, but because the kernel is stuck in
the beeping routine and never sync's the output to vidcontrol.log.
Compiled with DDB and INVARIANTS both enabled, the console does not
respond to Ctrl - Alt - Esc when this happens and I can't enter ddb to
view what the backtrace is.
I am not sure if this helps in understanding what the problem might be :/
If there is anything else I can do to help in hunting this down,
please let me know.
-giorgos
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010704124820.A86698>