From owner-freebsd-hackers Tue Dec 2 00:39:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA12066 for hackers-outgoing; Tue, 2 Dec 1997 00:39:53 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA12060 for ; Tue, 2 Dec 1997 00:39:51 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id AAA02290; Tue, 2 Dec 1997 00:37:15 -0800 (PST) Received: from UNKNOWN(), claiming to be "current1.whistle.com" via SMTP by alpo.whistle.com, id smtpd002286; Tue Dec 2 00:37:06 1997 Message-ID: <3483C827.695678E2@whistle.com> Date: Tue, 02 Dec 1997 00:34:47 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: Archie Cobbs CC: Kazutaka YOKOTA , jkh@time.cdrom.com, freebsd-hackers@FreeBSD.ORG Subject: Re: 2.2.5 problems References: <199712020742.XAA27819@bubba.whistle.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Archie Cobbs wrote: > > FYI- > this discussion is going on in two groups: hackers and bugs. > In the interest of not leaving anyone out, I'm sending this only > to hackers and cc'ing as appropriate... > > Kazutaka YOKOTA writes: > > >> After keyboard locks up, pressing locking keys (num-lock, caps-lock, > > >> scroll-lock) changes LED state? > > > > > >Not sure... I'm at work right now... but ctl-alt-del works. > > > > In that case, I suspect that the system and the console driver is > > alive. But syscons is somehow made to believe that the screen > > switching is still in progress. > > > > Would you tell me how the X server is started in which VT? And can > > you exactly recall the sequence of events which led to lock-up? > > Was the X server reset, by xdm or by SIGHUP, while in the background > > by any chance? > > Here is how I get this to happen. It's definitely timing related. > The fact that I always do the same thing after the machine boots > means I've gotten fast enough to trigger the bug almost every time... :-) > Actually, you don't have to be that fast, but being real slow about > everything does seem to avoid the problem. > > [ For simplicity, in the following the VT's start numbering at 1 > so they correspond with the function keys.. ] > > 0. Boot FreeBSD > 1. I have VT1 - VT6 with getty login screens, so X appears on VT7 > 2. CTL-ALT-F5 and login as "archie" on VT5. Start X running. > 3. Screen flashes VT1 briefly, then video resets and displays X screen > 4. CTL-ALT-F4 to get to VT4 and login as "root" > 5. Run command "xwin", which is an alias that pops two root > windows up on the X console. what's wrong with just running 'startx' to start X AND start some xterms? integrates steps 2,3,4 & 5 > 6. CTL-ALT-F7 to get VT7 back to X, ready to happily get to work. that should be not I assume this is a typo? > 7. Keyboard hangs, screen does NOT switch away from VT4, keyboard > leds DO still work, but CTL-ALT-F[1-7] just beeps at me. > I'm pretty sure machine responds to pings as well. > 8. CTL-ALT-DEL to reboot > 9. Rinse & repeat > > More info... > > vga0 rev 1 int a irq 10 on pci0:12 > sc0 at 0x60-0x6f irq 1 on motherboard > sc0: VGA color <16 virtual consoles, flags=0x0> > > XFree86 Version 3.3.1 / X Window System > (protocol Version 11, revision 0, vendor release 6300) > Release Date: August 4 1997 > If the server is older than 6-12 months, or if your card is newer > than the above date, look for a newer version before reporting > problems. (see http://www.XFree86.Org/FAQ) > Operating System: FreeBSD 2.2-STABLE i386 > Configured drivers: > S3V: accelerated server for S3 graphics adaptors (Patchlevel 0) > s3_ViRGE > Using syscons driver with X support (version 2.0) > (using VT number 7) > > -Archie > > ___________________________________________________________________________ > Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com