Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 13 Oct 2001 00:15:45 -0700
From:      Doug Barton <DougB@DougBarton.net>
To:        Dag-Erling Smorgrav <des@ofug.org>
Cc:        freebsd-current@FreeBSD.ORG
Subject:   Re: Strike three, you're out
Message-ID:  <3BC7EA21.15F43811@DougBarton.net>
References:  <3BC67CBD.1DAAC031@DougBarton.net> <xzpr8s9av9n.fsf@flood.ping.uio.no>

next in thread | previous in thread | raw e-mail | index | archive | help
Dag-Erling Smorgrav wrote:
> 
> Doug Barton <DougB@DougBarton.net> writes:
> > Reported on 9/30:
> > panic: blockable sleep lock (sx) allproc @
> > /usr/local/src/sys/kern/kern_proc.c:212
> >
> > According to BDE, "This is a well-know bug in printf(9).  The TIOCCONS
> > ioctl always gave non-deterministic crashes.  Now it gives determinstic
> > panics when
> > pintf() is called while sched_lock is held." That's the only discussion
> > about it, no fixes, no suggestions.
> 
> Remove UCONSOLE from kernel config.  This has been discussed to death
> several times on the lists.

	So your suggestion is just not to use that feature? I have to say that
I don't really like that answer. :) Is this something you think is just
impossible to fix? My examination of what I could find in the lists
seems to indicate that this bug affects more than must xconsole, it also
presents problems during install.
http://www.FreeBSD.org/cgi/getmsg.cgi?fetch=50759+54381+/usr/local/www/db/text/2001/freebsd-current/20010708.freebsd-current
seems to indicate that there is a possible solution to provide proper
locking, but it obviously hasn't been implemented yet. There are also a
couple of pretty good analyses of the problem by bde. 

> > Reported on 9/30:
> > Any releng_4 apps that I tried to run on my -current system could not
> > resolve hostnames. This included cvsup and yahoo! messenger. This was a
> > show stopper for me. The only suggestion I received was to make sure
> > that I didn't have any old libs laying around, which I did; and install
> > COMPAT4x, which I also did. Updating -current every other day to see if
> > something magic happened led me to,
> 
> Create /etc/host.conf (-CURRENT uses nsswitch.conf instead, and
> /etc/rc will bitch, but just ignore that)

	*slaps forehead* D'oh! That makes total sense, thanks for the tip.
Warner, does this sound like something that should go into UPDATING?

Doug
-- 
    "We will not tire, we will not falter, and we will not fail."
	- George W. Bush, President of the United States
          September 20, 2001  

         Do YOU Yahoo!?

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3BC7EA21.15F43811>