From owner-freebsd-bugs@FreeBSD.ORG Mon Jun 25 23:50:15 2012 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9811810657BA for ; Mon, 25 Jun 2012 23:50:15 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 837A68FC16 for ; Mon, 25 Jun 2012 23:50:15 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q5PNoE2o090432 for ; Mon, 25 Jun 2012 23:50:15 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q5PNoEId090431; Mon, 25 Jun 2012 23:50:14 GMT (envelope-from gnats) Date: Mon, 25 Jun 2012 23:50:14 GMT Message-Id: <201206252350.q5PNoEId090431@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Peter B Cc: Subject: Re: kern/116935: [ata] Intermittent error with Promise PDC40718 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Peter B List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jun 2012 23:50:15 -0000 The following reply was made to PR kern/116935; it has been noted by GNATS. From: Peter B To: ml@netfence.it (Andrea Venturoli) Cc: bug-followup@freebsd.org Subject: Re: kern/116935: [ata] Intermittent error with Promise PDC40718 Date: Tue, 26 Jun 2012 01:42:14 +0200 (MEST) >I've had gobs of troubles with this hardware and agreed with the "Don't >use" statement (I also had troubles with other SATA controllers, however). > >With two HDs it used to crash and/or lock the system: I tried different >HD vendors, different MBs, different FreeBSD versions and architectures, >but nothing would help. After the Promise trouble, I bought a cheap S-ATA controller which "just worked". >This was however until I tried 9.0 release. >I don't know if the reason is the "new CAM-based ATA stack", but it's >been working flawlessly with four HDs for weeks now. If there's one bug in the silicon. One might wonder if there's others too. Let's hope the new driver can handle the bug without suprises when the disc is full with important data.