From owner-freebsd-current@FreeBSD.ORG Fri Jun 18 15:41:48 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A19BC106566C for ; Fri, 18 Jun 2010 15:41:48 +0000 (UTC) (envelope-from mdf356@gmail.com) Received: from mail-gw0-f54.google.com (mail-gw0-f54.google.com [74.125.83.54]) by mx1.freebsd.org (Postfix) with ESMTP id 580188FC13 for ; Fri, 18 Jun 2010 15:41:44 +0000 (UTC) Received: by gwj20 with SMTP id 20so1040785gwj.13 for ; Fri, 18 Jun 2010 08:41:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:cc:content-type; bh=xgINYri5KNFMgXsiZFBod0Jpz1SUQ5aH9e+Zv7B85Nw=; b=HFlZIddWmj2tRmWvK56LngPxEn0eRKZdmMnEFVhVOoA7dBbIkHgECeXIqRUkNSGLp8 m/6WiUINHUvLVCw9HjM6cI1cnj9vsVC1Txea1M3VzXrid9L+lr+iDUbwE8fKfguK+Xbi +eISAfdEV2ZMWV07oTknkn2oZ9XKJnVn6W1l8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=XEQJuM96Ox2qlvJMwVTI699tCf0fFoCqlr5Sp7j/ZMTRXm26WETZjqZ5Jbu8fjM4I9 Pd1/BFvj177LQN3UvH/FGZs7nSJuzlrCKhENPFkRuIJh7JrbW4gpz/lOleBt8NB+w7tx 8YS+NEqvaplmccg5zTwiEAGJrn+ypqEXiawFY= MIME-Version: 1.0 Received: by 10.224.99.210 with SMTP id v18mr776265qan.87.1276874332100; Fri, 18 Jun 2010 08:18:52 -0700 (PDT) Sender: mdf356@gmail.com Received: by 10.224.28.79 with HTTP; Fri, 18 Jun 2010 08:18:52 -0700 (PDT) In-Reply-To: References: <6BEF4925-A058-4EFA-B005-30A01B3132FC@samsco.org> <4C0A9D57.8000900@quis.cx> <201006070957.07376.jhb@freebsd.org> Date: Fri, 18 Jun 2010 08:18:52 -0700 X-Google-Sender-Auth: OrI1cg19OAwDKWiqh0vA87ek1Dg Message-ID: From: mdf@FreeBSD.org To: Alexander Best Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-current@freebsd.org, Jille Timmermans Subject: Re: strange scsi/CAM related dmesg output X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Jun 2010 15:41:48 -0000 On Fri, Jun 18, 2010 at 8:11 AM, Alexander Best wrote: > On Mon, Jun 7, 2010 at 3:57 PM, John Baldwin wrote: >> It can happen because the print buffer size thing is not line-buffered, it is >> printf-invocation buffered. > > hmmm...can this somehow be fixed? i'm not sure this is specific to > scsi/cam. the other day i bootd my system and almost all of the dmesg > output was displayed incorrectly. would increasing PRINTF_BUFR_SIZE > from 128 to lets say 512 or 1024 solve the issue? I think what jhb meant was that we could look for the '\n' and flush to console there, instead of waiting for the end of the buffer. This would perhaps have more interleaved full lines, but likely fewer interleaved partial lines. Thanks, matthew