From owner-freebsd-hackers@FreeBSD.ORG Thu Mar 22 14:09:25 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4947B106566B; Thu, 22 Mar 2012 14:09:25 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 1D3518FC15; Thu, 22 Mar 2012 14:09:25 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [96.47.65.170]) by cyrus.watson.org (Postfix) with ESMTPSA id C701C46B32; Thu, 22 Mar 2012 10:09:24 -0400 (EDT) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 2CF44B959; Thu, 22 Mar 2012 10:09:24 -0400 (EDT) From: John Baldwin To: freebsd-hackers@freebsd.org Date: Thu, 22 Mar 2012 08:13:12 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p10; KDE/4.5.5; amd64; ; ) References: <20120322101041.GA99431@freebsd.org> In-Reply-To: <20120322101041.GA99431@freebsd.org> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201203220813.13113.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Thu, 22 Mar 2012 10:09:24 -0400 (EDT) Cc: Alexander Best Subject: Re: still issues with unreadable dmesg output on SMP systems X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Mar 2012 14:09:25 -0000 On Thursday, March 22, 2012 6:10:41 am Alexander Best wrote: > hi there, > > a few years ago there were huge issues with SMP and dmesg output, where > messages from various drivers were output to /dev/ttyv0 without any timing, > which caused a lot of unreadable lines. > > this was fixed and almost all of the dmesg lines i see now look similar to > dmesg on a non-SMP aware kernel. however there still seems to be an issue > within the cd(4) driver. maybe somebody could fix the driver output to match > the drivers, where the dmesg output looks correct (da(4), ada(4), ...). s/fixed/mostly worked around/ The problem is that the work around isn't perfect. The root cause is still not fixed. avg@ has some ideas on better ways to handle this, but it is a bit tricky to get this right since we also dont' want printfs to be delayed too much (and to fix this perfectly requires buffering printf output). -- John Baldwin