From owner-freebsd-hackers  Sun Jan 11 20:36:41 1998
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id UAA23596
          for hackers-outgoing; Sun, 11 Jan 1998 20:36:41 -0800 (PST)
          (envelope-from owner-freebsd-hackers@FreeBSD.ORG)
Received: from ren.dtir.qld.gov.au (firewall-user@ns.dtir.qld.gov.au [203.108.138.66])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA23565;
          Sun, 11 Jan 1998 20:36:14 -0800 (PST)
          (envelope-from syssgm@dtir.qld.gov.au)
Received: by ren.dtir.qld.gov.au; id OAA15933; Mon, 12 Jan 1998 14:51:09 +1000 (EST)
Received: from ogre.dtir.qld.gov.au(167.123.8.3) by ren.dtir.qld.gov.au via smap (3.2)
	id xma015895; Mon, 12 Jan 98 14:50:53 +1000
Received: from localhost.dtir.qld.gov.au (localhost.dtir.qld.gov.au [127.0.0.1])
	by ogre.dtir.qld.gov.au (8.8.7/8.8.7) with SMTP id OAA18256;
	Mon, 12 Jan 1998 14:34:50 +1000 (EST)
Message-Id: <199801120434.OAA18256@ogre.dtir.qld.gov.au>
X-Authentication-Warning: ogre.dtir.qld.gov.au: localhost.dtir.qld.gov.au [127.0.0.1] didn't use HELO protocol
To: Mikael Karpberg <karpen@ocean.campus.luth.se>
cc: freebsd-hackers@FreeBSD.ORG, syssgm@dtir.qld.gov.au, phk@FreeBSD.ORG
Subject: Re: Weird syscons errors 
References: <199801111720.SAA05066@ocean.campus.luth.se>
In-Reply-To: <199801111720.SAA05066@ocean.campus.luth.se>
    from Mikael Karpberg at "Sun, 11 Jan 1998 17:20:32 +0000"
Date: Mon, 12 Jan 1998 14:34:49 +1000
From: Stephen McKay <syssgm@dtir.qld.gov.au>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk

On Sunday, 11th January 1998, Mikael Karpberg wrote:

>What happens is that after the probe messages have come up, I get no more
>output. The computer continues to boot to full multiuser mode, and I can
>log in, but I have to do it "blindly". There seems to be no way to the
>console into displaying anything except those frozen boot messages.

I had this problem.  Dropping into DDB causes the output to be displayed.
So using CTL-ALT-ESC and continue, I managed to get by until I could rewind
my kernel source a bit and go from there.

The problem is not in syscons, but (I believe) in the kern_timeout splitoff.
I regressed to just before phk's change (but after the syscons change):

>phk         1998/01/10 05:16:32 PST
>
>  Modified files:
>    sys/conf             files
>    sys/sys              systm.h
>    sys/kern             kern_clock.c kern_timeout.c
>  Log:
>  Effect the divorce of kern_clock.c and kern_timeout.c (which was
>  repository copied from kern_clock.c)
>
>  Revision  Changes    Path
>  1.118     +1 -0      src/sys/conf/files
>  1.66      +2 -2      src/sys/sys/systm.h
>  1.49      +2 -283    src/sys/kern/kern_clock.c
>  1.49      +20 -1111  src/sys/kern/kern_timeout.c

He seems to be still working on this (Hi Poul!) as a few commits after
this fix some bugs, including a "timeout race" in rev 1.52 of kern_clock.c.
Broken timeouts will cause lots of funny errors, so be careful!

Stephen.