From owner-freebsd-smp  Mon Sep 11 16:59:22 2000
Delivered-To: freebsd-smp@freebsd.org
Received: from feral.com (feral.com [192.67.166.1])
	by hub.freebsd.org (Postfix) with ESMTP
	id 9C9BB37B422; Mon, 11 Sep 2000 16:59:17 -0700 (PDT)
Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71])
	by feral.com (8.9.3/8.9.3) with ESMTP id QAA12781;
	Mon, 11 Sep 2000 16:59:12 -0700
Date: Mon, 11 Sep 2000 16:55:21 -0700 (PDT)
From: Matthew Jacob <mjacob@feral.com>
Reply-To: mjacob@feral.com
To: Marius Bendiksen <mbendiks@eunet.no>
Cc: Mike Smith <msmith@FreeBSD.ORG>,
	Poul-Henning Kamp <phk@FreeBSD.ORG>, arch@FreeBSD.ORG,
	smp@FreeBSD.ORG
Subject: Re: Device probing... 
In-Reply-To: <Pine.BSF.4.05.10009120155440.78512-100000@login-1.eunet.no>
Message-ID: <Pine.LNX.4.21.0009111654400.25275-100000@zeppo.feral.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-smp@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


Good idea, except it's hard to debug unless you have a working ddb or gdb or
something (which is very rare these days for the machines I usually work on).


> > The biggest one that's left is that a lot of drivers will end up printing 
> > things in interrupt context, leading to *incredibly* messy console 
> > output.  We'll need a cleaner way of presenting driver messages.
> 
> Couldn't this be resolved by adding a console buffer which you could spool
> lines to, rather than printing them directly? The buffer would then sort a
> certain number of lines at a time, and print them grouped by driver.
> </rough-sketch>
> 
> Marius
> 



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