From owner-freebsd-questions@FreeBSD.ORG Sun Dec 6 05:19:15 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CFD0C106568B for ; Sun, 6 Dec 2009 05:19:15 +0000 (UTC) (envelope-from freebsd@sopwith.solgatos.com) Received: from sopwith.solgatos.com (pool-98-108-131-11.ptldor.fios.verizon.net [98.108.131.11]) by mx1.freebsd.org (Postfix) with ESMTP id D4B988FC0A for ; Sun, 6 Dec 2009 05:19:14 +0000 (UTC) Received: by sopwith.solgatos.com (Postfix, from userid 66) id B4235B64F; Sat, 5 Dec 2009 20:34:30 -0800 (PST) Received: from localhost by sopwith.solgatos.com (8.8.8/6.24) id DAA25727; Sun, 6 Dec 2009 03:24:57 GMT Message-Id: <200912060324.DAA25727@sopwith.solgatos.com> To: freebsd-questions@freebsd.org Date: Sat, 05 Dec 2009 19:24:57 PST From: Dieter Subject: 8.0 dmesg output is mangled X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd@sopwith.solgatos.com List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Dec 2009 05:19:15 -0000 Updating an amd64 box from 7.1 to 8.0. Console is RS-232. Check to see if any disk names have changed: dmesg | grep ^ad looks reasonable. added siis_load="YES" to loader.conf and rebooted dmesg | grep siis gives output that doesn't look right at all: siis0: port 0x7c00-0x7c7f mem 0xfe6ff000-0xfe6ff07f,0 xfe6f8000-0xfe6fbfff irq 16 at device 0.0 on pci4 siis0: [ITHREAD] siisch0: at channel 0 on siis0 siisch0: [ITHREAD] siisch1: at channel 1 on siis0 siisch1: [ITHREAD] ad2: 305245MB at ata1-master UDMA100(aprobe0:siisch0: 0:15:0): SIGNATURE: 0000 (aprobe0:siisch0:0:0:0): SIGNATURE: 0000 ad10: 1907729MB at ata5-master SATA300(aprobe 1:siisch1:0:15:0): SIGNATURE: 0000 ad14: 953869MB at ata7-master SATA300(aprobe0:siisch1 :0:0:0): SIGNATURE: 0000 ada0 at siisch0 bus 0 target 0 lun 0 ada1 at siisch1 bus 0 target 0 lun 0 The Samsung disk is connected to a JMB363 controller, not the SiI 3132. The SiI 3132 has a Hitachi and a Seagate. dmesg | grep ^ada ada0 at siisch0 bus 0 target 0 lun 0 ada0: ATA/ATAPI-8 SATA 2.x device ada0: 300.000MB/s transfers ada0: 953869MB (1953525168 512 byte sectors: 16H 63S/T 16383C) ada0: Native Command Queueing enabled ada1 at siisch1 bus 0 target 0 lun 0 ada1: ATA/ATAPI-8 SATA 2.x device ada1: 300.000MB/s transfers ada1: 1430799MB (2930277168 512 byte sectors: 16H 63S/T 16383C) ada1: Native Command Queueing enabled This looks reasonable except for a 1 TB and a 1.5 TB drive having the same number of heads, sectors/track and cylinders. (not that those numbers are meaningful with recent disks) I'm thinking that perhaps the outputs from ata(4) and siis(4) are getting jumbled together like two processes writing to the same tty?