From owner-freebsd-current@FreeBSD.ORG Sat Jun 19 02:19:25 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 66438106564A; Sat, 19 Jun 2010 02:19:25 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.freebsd.org (Postfix) with ESMTP id 027508FC0C; Sat, 19 Jun 2010 02:19:24 +0000 (UTC) Received: from [192.168.4.183] ([68.177.209.202]) (authenticated bits=0) by pooker.samsco.org (8.14.4/8.14.4) with ESMTP id o5J2JAgJ098009; Fri, 18 Jun 2010 20:19:18 -0600 (MDT) (envelope-from scottl@samsco.org) References: <6BEF4925-A058-4EFA-B005-30A01B3132FC@samsco.org> <4C0A9D57.8000900@quis.cx> <201006070957.07376.jhb@freebsd.org> Message-Id: <9B404DAF-CD34-4799-8DFA-F24AF62F0117@samsco.org> From: Scott Long To: Alexander Best In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit X-Mailer: iPhone Mail (7D11) Mime-Version: 1.0 (iPhone Mail 7D11) Date: Fri, 18 Jun 2010 20:18:54 -0600 X-Spam-Status: No, score=1.3 required=3.8 tests=RDNS_NONE autolearn=no version=3.3.0 X-Spam-Level: * X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on pooker.samsco.org 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: Sat, 19 Jun 2010 02:19:25 -0000 On Jun 18, 2010, at 9:11 AM, Alexander Best wrote: > On Mon, Jun 7, 2010 at 3:57 PM, John Baldwin wrote: >> On Saturday 05 June 2010 2:54:15 pm Jille Timmermans wrote: >>> Scott Long schreef: >>>> On Jun 4, 2010, at 4:35 PM, Alexander Best wrote: >>>> >>>>> hi there. running HEAD, amd64 and r208806 i get this dmesg output >>>>> which doesn't look right: >>>>> >>>>> ada0 at ahcich2 bus 0 scbus3 target 0 lun 0 >>>>> ada0: ATA-7 SATA 2.x device >>>>> ada0: 300.000MB/s transferscd0 at ata2 bus 0 scbus2 target 0 lun 0 >>>>> cd0: Removable CD-ROM SCSI-0 >>>>> device >>>>> cd0: 33.300MB/s transfers (UDMA2, ATAPI 12bytes, PIO 65534bytes) >>>>> cd0: cd present [1944656 x 2048 byte records] >>>>> (SATA 2.x, UDMA6, PIO 8192bytes) >>>>> ada0: Command Queueing enabled >>>>> ada0: 238474MB (488395055 512 byte sectors: 16H 63S/T 16383C) >>>>> >>>>> >>>>> my kernel contains: >>>>> >>>>> options SC_HISTORY_SIZE=1000 >>>>> options MSGBUF_SIZE=65536 >>>>> options PRINTF_BUFR_SIZE=128 >>>>> >>>>> might this be caused by one of these lines? >>>>> >>>>> cheers. >>>>> >>>> >>>> Can you be more specific about what you think is not right? >>>> >>>> Scott >>> I assume he means that 'cd0 at ata2 ...' is on the same line as the >>> third ada0 line. After all the cd0-lines, the ada0 line continues. >>> That shouldn't happen with PRINTF_BUFR_SIZE set, should it? >> >> 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 Johns response is off base. I explained the issue prior to him, please review that. Scott >>