From owner-freebsd-current@FreeBSD.ORG Sat Jun 5 19:12:23 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 6AF17106564A for ; Sat, 5 Jun 2010 19:12:23 +0000 (UTC) (envelope-from jille@quis.cx) Received: from istud.quis.cx (56-64-223.ftth.xms.internl.net [85.223.64.56]) by mx1.freebsd.org (Postfix) with ESMTP id E45FB8FC0A for ; Sat, 5 Jun 2010 19:12:22 +0000 (UTC) Received: from [192.168.0.4] (unknown [192.168.0.4]) by istud.quis.cx (Postfix) with ESMTP id 86817610837; Sat, 5 Jun 2010 20:54:25 +0200 (CEST) Message-ID: <4C0A9D57.8000900@quis.cx> Date: Sat, 05 Jun 2010 20:54:15 +0200 From: Jille Timmermans User-Agent: Thunderbird 2.0.0.24 (Windows/20100228) MIME-Version: 1.0 To: Scott Long References: <6BEF4925-A058-4EFA-B005-30A01B3132FC@samsco.org> In-Reply-To: <6BEF4925-A058-4EFA-B005-30A01B3132FC@samsco.org> X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, Alexander Best 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, 05 Jun 2010 19:12:23 -0000 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? -- Jille