From owner-freebsd-current@FreeBSD.ORG Fri Jun 18 15:11:21 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 7445B1065676 for ; Fri, 18 Jun 2010 15:11:21 +0000 (UTC) (envelope-from alexbestms@uni-muenster.de) Received: from SECMAIL.UNI-MUENSTER.DE (SECMAIL.UNI-MUENSTER.DE [128.176.192.141]) by mx1.freebsd.org (Postfix) with ESMTP id 1535A8FC1A for ; Fri, 18 Jun 2010 15:11:20 +0000 (UTC) Received: from mail-gy0-f182.google.com (mail-gy0-f182.google.com [209.85.160.182]) by SECMAIL.UNI-MUENSTER.DE (Postfix) with ESMTP id 7A042BF41A; Fri, 18 Jun 2010 17:11:19 +0200 (CEST) Received: by gyh20 with SMTP id 20so1215061gyh.13 for ; Fri, 18 Jun 2010 08:11:18 -0700 (PDT) MIME-Version: 1.0 Received: by 10.229.235.195 with SMTP id kh3mr581347qcb.238.1276873876408; Fri, 18 Jun 2010 08:11:16 -0700 (PDT) Received: by 10.229.215.196 with HTTP; Fri, 18 Jun 2010 08:11:16 -0700 (PDT) In-Reply-To: <201006070957.07376.jhb@freebsd.org> References: <6BEF4925-A058-4EFA-B005-30A01B3132FC@samsco.org> <4C0A9D57.8000900@quis.cx> <201006070957.07376.jhb@freebsd.org> Date: Fri, 18 Jun 2010 17:11:16 +0200 Message-ID: From: Alexander Best To: John Baldwin Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 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:11:21 -0000 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 =A0 =A0 =A0 =A0 SC_HISTORY_SIZE=3D1000 >> >> options =A0 =A0 =A0 =A0 MSGBUF_SIZE=3D65536 >> >> options =A0 =A0 =A0 =A0 PRINTF_BUFR_SIZE=3D128 >> >> >> >> 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, i= t 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? cheers. > > -- > John Baldwin > --=20 Alexander Best