From owner-freebsd-hardware@FreeBSD.ORG Mon Oct 7 11:06:45 2013 Return-Path: Delivered-To: freebsd-hardware@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 8720684E for ; Mon, 7 Oct 2013 11:06:45 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 5CAC02834 for ; Mon, 7 Oct 2013 11:06:45 +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 r97B6jd3077710 for ; Mon, 7 Oct 2013 11:06:45 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r97B6iuP077708 for freebsd-hardware@FreeBSD.org; Mon, 7 Oct 2013 11:06:44 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 7 Oct 2013 11:06:44 GMT Message-Id: <201310071106.r97B6iuP077708@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, 07 Oct 2013 11:06:45 -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 Thu Oct 10 21:03:13 2013 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 70E8E985 for ; Thu, 10 Oct 2013 21:03:13 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 4B2DD2DA1 for ; Thu, 10 Oct 2013 21:03:13 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 71230B948; Thu, 10 Oct 2013 17:03:12 -0400 (EDT) From: John Baldwin To: freebsd-hardware@freebsd.org Subject: Re: Install Program can't boot after AMD-A75 onboard-raid is activated Date: Thu, 10 Oct 2013 16:54:51 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.4-CBSD-20130906; KDE/4.5.5; amd64; ; ) References: In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201310101654.51795.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Thu, 10 Oct 2013 17:03:12 -0400 (EDT) Cc: Alan Fagundes 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, 10 Oct 2013 21:03:13 -0000 On Monday, September 23, 2013 10:51:52 am Alan Fagundes wrote: > Hi, > i have the same problem of the other guy, see the post: > http://lists.freebsd.org/pipermail/freebsd-hardware/2012-October/007134.html > what fix it ? > Alan FagundesSupport Analyste-mail/msn/skype: alanfagundes@hotmail.comExtrema - MG BrazilTel. 55(35) 8432 0131 I might have just fixed this as various folks reported a bug when RAID was enabled in the BIOS that was fixed in http://svnweb.freebsd.org/base?view=revision&revision=256293. -- John Baldwin From owner-freebsd-hardware@FreeBSD.ORG Thu Oct 10 21:03:14 2013 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 70EFD986; Thu, 10 Oct 2013 21:03:14 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 4B0012DA2; Thu, 10 Oct 2013 21:03:14 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 4A643B986; Thu, 10 Oct 2013 17:03:13 -0400 (EDT) From: John Baldwin To: freebsd-hardware@freebsd.org Subject: Re: What's the state of AF-4Kn support? Date: Thu, 10 Oct 2013 16:57:22 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.4-CBSD-20130906; KDE/4.5.5; amd64; ; ) References: In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201310101657.22675.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Thu, 10 Oct 2013 17:03:13 -0400 (EDT) Cc: Ravi Pokala , freebsd-hackers@freebsd.org, Jia-Shiun Li 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, 10 Oct 2013 21:03:14 -0000 On Monday, September 23, 2013 10:58:19 am Ravi Pokala wrote: > -----Original Message----- > From: Jia-Shiun Li > Date: Sunday, September 22, 2013 11:22 PM > To: Ravi Pokala > Cc: "freebsd-hardware@freebsd.org" , > > Subject: Re: What's the state of AF-4Kn support? > > >On Wed, Sep 18, 2013 at 10:49 PM, Ravi Pokala wrote: > >> > >>... > > > >CC -hackers. > > > >Thanks for the clarification. Is there any 4Kn HDDs shopping now? I am > >not aware of any. > > Good question. I had the impression that some currently shipping drives > were AF-4Kn, but spot-checking some of the drives listed in > > src/cam/ata/ata_da.c::ada_quirk_table[] > > against their datasheets, suggests that they're AF-512e. So, their being > flagged w/ ADA_Q_4K is "just" a performance optimization. > > >BTW I believe UFS and ZFS have proper design for 4K-sectors, but FreeBSD > >needs some ecosystem connections to get samples early to test, > >incorporate supports and validate for it. Or we will need to wait until > >it appears on market and someone got caught into some kind of bugs. > > Yeah, based on my reading of the code, it looks like the ATACAM layer and > higher (GEOM, filesystems) take the physical block size into account. That > just leaves the bootstrap code. Now that I've taken a second look, it > seems as though at least 'pmbr' only works in terms of 512 bytes. :-( Yes, the BIOS calls have always only used 512 byte sectors. There would have to be an updated spec for those, and it would be a bit of a PITA to use. I suspect the "right" answer for this on x86 is UEFI. -- John Baldwin From owner-freebsd-hardware@FreeBSD.ORG Fri Oct 11 19:50:28 2013 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 439604A8; Fri, 11 Oct 2013 19:50:28 +0000 (UTC) (envelope-from rp_freebsd@mac.com) Received: from nk11p00mm-asmtp001.mac.com (nk11p00mm-asmtp001.mac.com [17.158.161.0]) by mx1.freebsd.org (Postfix) with ESMTP id 254552E9D; Fri, 11 Oct 2013 19:50:27 +0000 (UTC) Received: from nk11p00mm-spool004.mac.com ([17.158.161.119]) by nk11p00mm-asmtp001.mac.com (Oracle Communications Messaging Server 7u4-27.08(7.0.4.27.7) 64bit (built Aug 22 2013)) with ESMTP id <0MUI004Y1PMHVW70@nk11p00mm-asmtp001.mac.com>; Fri, 11 Oct 2013 18:49:32 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8794,1.0.431,0.0.0000 definitions=2013-10-11_07:2013-10-11,2013-10-11,1970-01-01 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1308280000 definitions=main-1310110081 MIME-version: 1.0 Received: from localhost ([17.158.233.93]) by nk11p00mm-spool004.mac.com (Oracle Communications Messaging Server 7u4-27.08(7.0.4.27.7) 64bit (built Aug 22 2013)) with ESMTP id <0MUI00GQNPMHKN20@nk11p00mm-spool004.mac.com>; Fri, 11 Oct 2013 18:49:29 +0000 (GMT) To: John Baldwin From: Ravi Pokala Subject: Re: What's the state of AF-4Kn support? Date: Fri, 11 Oct 2013 18:49:29 +0000 (GMT) X-Mailer: iCloud MailClient1T.110221 MailServer1T32 X-Originating-IP: [66.2.48.195] Message-id: <4a88054e-d435-4d4b-959b-eb809b99e34d@me.com> In-reply-to: <201310101657.22675.jhb@freebsd.org> Content-Type: text/plain; CHARSET=US-ASCII; format=flowed Content-Transfer-Encoding: 7BIT X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-hackers@freebsd.org, Jia-Shiun Li , 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: Fri, 11 Oct 2013 19:50:28 -0000 Yes, the BIOS calls have always only used 512 byte sectors. There would have to be an updated spec for those, and it would be a bit of a PITA to use. I suspect the "right" answer for this on x86 is UEFI. Yeah, that's the conclusion I reached as well. Though it occurs to me, aren't we already part-way there w/ our IA64 support? EFI originated w/ Itanium and was required to boot those systems, so shouldn't we be able to leverage much of that work for (U)EFI on amd64? In any case, the primary motivator (at least, for me) is being able to boot from AF-4Kn drives; based on the most recent roadmaps I've seen, the enterprise HDD vendors are committing to support AF-512e for a good while longer, so it's not as urgent as I thought it was when I opened this thread a few weeks ago. Thanks, --rp On Oct 10, 2013, at 01:57 PM, John Baldwin wrote: On Monday, September 23, 2013 10:58:19 am Ravi Pokala wrote: -----Original Message----- From: Jia-Shiun Li Date: Sunday, September 22, 2013 11:22 PM To: Ravi Pokala Cc: "freebsd-hardware@freebsd.org" , Subject: Re: What's the state of AF-4Kn support? >On Wed, Sep 18, 2013 at 10:49 PM, Ravi Pokala wrote: >> >>... > >CC -hackers. > >Thanks for the clarification. Is there any 4Kn HDDs shopping now? I am >not aware of any. Good question. I had the impression that some currently shipping drives were AF-4Kn, but spot-checking some of the drives listed in src/cam/ata/ata_da.c::ada_quirk_table[] against their datasheets, suggests that they're AF-512e. So, their being flagged w/ ADA_Q_4K is "just" a performance optimization. >BTW I believe UFS and ZFS have proper design for 4K-sectors, but FreeBSD >needs some ecosystem connections to get samples early to test, >incorporate supports and validate for it. Or we will need to wait until >it appears on market and someone got caught into some kind of bugs. Yeah, based on my reading of the code, it looks like the ATACAM layer and higher (GEOM, filesystems) take the physical block size into account. That just leaves the bootstrap code. Now that I've taken a second look, it seems as though at least 'pmbr' only works in terms of 512 bytes. :-( Yes, the BIOS calls have always only used 512 byte sectors. There would have to be an updated spec for those, and it would be a bit of a PITA to use. I suspect the "right" answer for this on x86 is UEFI. -- John Baldwin