From owner-freebsd-hardware@FreeBSD.ORG Mon Jul 8 11:40:41 2013 Return-Path: Delivered-To: freebsd-hardware@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 30A3820B for ; Mon, 8 Jul 2013 11:40:41 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 08FA212F4 for ; Mon, 8 Jul 2013 11:40:41 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id r68BeXYe053981 for ; Mon, 8 Jul 2013 11:40:40 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r68B6avd046113 for freebsd-hardware@FreeBSD.org; Mon, 8 Jul 2013 11:06:36 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 8 Jul 2013 11:06:36 GMT Message-Id: <201307081106.r68B6avd046113@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-hardware@FreeBSD.org Subject: Current problem reports assigned to freebsd-hardware@FreeBSD.org X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jul 2013 11:40:41 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- f kern/156241 hardware [mfi] 'zfs send' does not prevents disks to suspend if 1 problem total. From owner-freebsd-hardware@FreeBSD.ORG Wed Jul 10 00:56:10 2013 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 5650C1EE for ; Wed, 10 Jul 2013 00:56:10 +0000 (UTC) (envelope-from isoa@kapsi.fi) Received: from mail.kapsi.fi (mx1.kapsi.fi [IPv6:2001:1bc8:1004::1:25]) by mx1.freebsd.org (Postfix) with ESMTP id 1B78E19AF for ; Wed, 10 Jul 2013 00:56:09 +0000 (UTC) Received: from 91-157-65-74.elisa-laajakaista.fi ([91.157.65.74] helo=[192.168.255.133]) by mail.kapsi.fi with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from ) id 1UwihS-0002jY-Qm for freebsd-hardware@freebsd.org; Wed, 10 Jul 2013 03:56:07 +0300 Message-ID: <51DCB125.3060602@kapsi.fi> Date: Wed, 10 Jul 2013 03:56:05 +0300 From: Arto Pekkanen User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: freebsd-hardware@freebsd.org Subject: Weird READ_DMA errors in dmesg X-Enigmail-Version: 1.5.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-SA-Exim-Connect-IP: 91.157.65.74 X-SA-Exim-Mail-From: isoa@kapsi.fi X-SA-Exim-Scanned: No (on mail.kapsi.fi); SAEximRunCond expanded to false X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jul 2013 00:56:10 -0000 I have the following device in my BSD box # camcontrol identify ada0 pass0: ATA-8 SATA 3.x device pass0: 150.000MB/s transfers (SATA 1.x, UDMA5, PIO 8192bytes) protocol ATA/ATAPI-8 SATA 3.x device model KINGSTON SVP200S360G firmware revision 502ABBF0 serial number 50026B7227002AA4 WWN 50026b7227002aa4 cylinders 16383 heads 16 sectors/track 63 sector size logical 512, physical 512, offset 0 LBA supported 117231408 sectors LBA48 supported 117231408 sectors PIO supported PIO4 DMA supported WDMA2 UDMA6 media RPM non-rotating Feature Support Enabled Value Vendor read ahead yes yes write cache yes yes flush cache yes yes overlap no Tagged Command Queuing (TCQ) no no Native Command Queuing (NCQ) yes 32 tags SMART yes yes microcode download yes yes security yes no power management yes yes advanced power management yes yes 254/0xFE automatic acoustic management no no media status notification no no power-up in Standby yes no write-read-verify yes no 0/0x0 unload yes yes free-fall no no data set management (TRIM) yes I get a sometimes the following types of dmesg output on my Kingston V+200 SSD hd: (ada0:ata3:0:0:0): READ_DMA. ACB: c8 00 bf fa 39 40 00 00 00 00 08 00 (ada0:ata3:0:0:0): CAM status: ATA Status Error (ada0:ata3:0:0:0): ATA status: 51 (DRDY SERV ERR), error: 84 (ICRC ABRT ) (ada0:ata3:0:0:0): RES: 51 84 bf fa 39 00 00 00 00 08 00 (ada0:ata3:0:0:0): Retrying command (ada0:ata3:0:0:0): READ_DMA. ACB: c8 00 0f 75 d7 41 00 00 00 00 40 00 (ada0:ata3:0:0:0): CAM status: ATA Status Error (ada0:ata3:0:0:0): ATA status: 51 (DRDY SERV ERR), error: 84 (ICRC ABRT ) (ada0:ata3:0:0:0): RES: 51 84 0f 75 d7 01 01 00 00 40 00 (ada0:ata3:0:0:0): Retrying command (ada0:ata3:0:0:0): READ_DMA. ACB: c8 00 4f bc e9 44 00 00 00 00 40 00 (ada0:ata3:0:0:0): CAM status: ATA Status Error (ada0:ata3:0:0:0): ATA status: 51 (DRDY SERV ERR), error: 84 (ICRC ABRT ) (ada0:ata3:0:0:0): RES: 51 84 4f bc e9 04 04 00 00 40 00 (ada0:ata3:0:0:0): Retrying command (ada0:ata3:0:0:0): READ_DMA. ACB: c8 00 27 1a 95 40 00 00 00 00 08 00 (ada0:ata3:0:0:0): CAM status: ATA Status Error (ada0:ata3:0:0:0): ATA status: 51 (DRDY SERV ERR), error: 84 (ICRC ABRT ) (ada0:ata3:0:0:0): RES: 51 84 27 1a 95 00 00 00 00 08 00 (ada0:ata3:0:0:0): Retrying command (ada0:ata3:0:0:0): READ_DMA. ACB: c8 00 cf d8 35 45 00 00 00 00 08 00 (ada0:ata3:0:0:0): CAM status: ATA Status Error (ada0:ata3:0:0:0): ATA status: 51 (DRDY SERV ERR), error: 84 (ICRC ABRT ) (ada0:ata3:0:0:0): RES: 51 84 cf d8 35 05 05 00 00 08 00 (ada0:ata3:0:0:0): Retrying command (ada0:ata3:0:0:0): READ_DMA. ACB: c8 00 2f 5b ab 40 00 00 00 00 08 00 (ada0:ata3:0:0:0): CAM status: ATA Status Error (ada0:ata3:0:0:0): ATA status: 51 (DRDY SERV ERR), error: 84 (ICRC ABRT ) (ada0:ata3:0:0:0): RES: 51 84 2f 5b ab 00 00 00 00 08 00 (ada0:ata3:0:0:0): Retrying command (ada0:ata3:0:0:0): READ_DMA. ACB: c8 00 9f 08 22 40 00 00 00 00 08 00 (ada0:ata3:0:0:0): CAM status: ATA Status Error (ada0:ata3:0:0:0): ATA status: 51 (DRDY SERV ERR), error: 84 (ICRC ABRT ) (ada0:ata3:0:0:0): RES: 51 84 9f 08 22 00 00 00 00 08 00 (ada0:ata3:0:0:0): Retrying command (ada0:ata3:0:0:0): READ_DMA. ACB: c8 00 67 3b 3a 40 00 00 00 00 08 00 (ada0:ata3:0:0:0): CAM status: ATA Status Error (ada0:ata3:0:0:0): ATA status: 51 (DRDY SERV ERR), error: 84 (ICRC ABRT ) (ada0:ata3:0:0:0): RES: 51 84 67 3b 3a 00 00 00 00 08 00 (ada0:ata3:0:0:0): Retrying command (ada0:ata3:0:0:0): READ_DMA. ACB: c8 00 4f 27 8d 44 00 00 00 00 40 00 (ada0:ata3:0:0:0): CAM status: ATA Status Error (ada0:ata3:0:0:0): ATA status: 51 (DRDY SERV ERR), error: 84 (ICRC ABRT ) (ada0:ata3:0:0:0): RES: 51 84 4f 27 8d 04 04 00 00 40 00 (ada0:ata3:0:0:0): Retrying command This is just a sample of the output. ACB and RES parameters seem to vary. I have a geli-encrypted root partition on it, and data set management (wear leveling) enabled on the UFS2 filesystem. The encryption (AES-256-CBC) is assisted by padlock and the padlock.ko kernel module. The motherboard on the box is some 1.2 Ghz VIA C7 CPU based EPIA, cannot remember which ... The disk seems to work just fine, I have never gotten any errors while writing or reading stuff from the disk, as far as I know. The commands are retried, and maybe they succeed after all? Are the above errors dangerous? Any idea what causes them? Also, I would like to know if BIO_DELETE (ssd trim) commands are passed thru the geli layer to the actual block device. Thanks beforehand. -- Arto Pekkanen, säätäjä ksym@IRCnet From owner-freebsd-hardware@FreeBSD.ORG Thu Jul 11 00:44:41 2013 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id CA7BE60F for ; Thu, 11 Jul 2013 00:44:41 +0000 (UTC) (envelope-from freebsd-doc@fjl.co.uk) Received: from bs1.fjl.org.uk (bs1.fjl.org.uk [84.45.41.196]) by mx1.freebsd.org (Postfix) with ESMTP id 762D91477 for ; Thu, 11 Jul 2013 00:44:41 +0000 (UTC) Received: from [192.168.1.35] (mux.fjl.org.uk [62.3.120.246]) (authenticated bits=0) by bs1.fjl.org.uk (8.14.4/8.14.4) with ESMTP id r6B0iXuo079679 (version=TLSv1/SSLv3 cipher=DHE-DSS-CAMELLIA256-SHA bits=256 verify=NO) for ; Thu, 11 Jul 2013 01:44:34 +0100 (BST) (envelope-from freebsd-doc@fjl.co.uk) Message-ID: <51DDFFE0.4080501@fjl.co.uk> Date: Thu, 11 Jul 2013 01:44:16 +0100 From: Frank Leonhardt User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7 MIME-Version: 1.0 To: freebsd-hardware@freebsd.org Subject: FreeBSD on HP DL585 G2 or IBM X3755 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Jul 2013 00:44:41 -0000 Does anyone know what my chances are of getting FreeBSD running on either of these? In particular, have you got it working? The HP DL582 has a weird Ethernet which wasn't supported beyond 7.2 (I believe), but may be back on in 9.1 (or I may be able to port the driver). The IBM X3755 is completely unknown, but looks promising. In case anyone's wondering, both of these high-end servers are now available cheap as I don't think they're supported by current versions of VM Ware or Windoze "Server". I want one because they support lots of RAM and I need all I can get to do something with Open Streetmap. If I can get one disk and the LAN working I can manage with serious storage elsewhere on the network (I can't afford SCSI disks for this project anyway!)