From owner-freebsd-questions@FreeBSD.ORG Sun Nov 22 01:07:39 2009 Return-Path: Delivered-To: questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A057F106568F for ; Sun, 22 Nov 2009 01:07:39 +0000 (UTC) (envelope-from dhorn2000@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.156]) by mx1.freebsd.org (Postfix) with ESMTP id 323D68FC1D for ; Sun, 22 Nov 2009 01:07:39 +0000 (UTC) Received: by fg-out-1718.google.com with SMTP id e12so488630fga.13 for ; Sat, 21 Nov 2009 17:07:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=uJ0soYzdHDFwaC/SZols4Nl7H2pXgyy/ddtlSazLUIg=; b=BIbKgiXR+NL0Ndmyc2DUm4stEFX3C69BJfIvfxk1bPODQqowhq8zogKTs+2pKk+GTN zhoU5GmTewuYrHOBtEvqhAAiTBMSdBV/FcSIsqhtnCZUehzGK1pC/5cDIJhrneH3N5rv FesdQ37XNMg00vvbfjsR7bxbKkCYUi96FIVr0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=r7+uVFPhTfgucRzdvVZ6CYWHk5BApM5T0INHI2zfcrSNhHzMo+rAbilfMmZLl9QUSW hEBQmf79LkeXGcTbOFL9QHkDxDlvE70jbD/2eXBryy6XWYVUUKASU8hhvBHtNE4AT0bS PMWkcutYQn/MuT3dvHZ3y1HaD4ohuGeyp4j9Y= MIME-Version: 1.0 Received: by 10.239.173.204 with SMTP id g12mr317907hbf.190.1258852057782; Sat, 21 Nov 2009 17:07:37 -0800 (PST) In-Reply-To: References: <4B083083.4000907@onetel.com> <25ff90d60911211202s325a4f18u116626beb355ab8d@mail.gmail.com> Date: Sat, 21 Nov 2009 20:07:37 -0500 Message-ID: <25ff90d60911211707t5a18f5d6y8732f718010f70df@mail.gmail.com> From: David Horn To: Tim Judd Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: FreeBSD Questions , Chris Whitehouse Subject: Re: device hint -> disable firewire or sbp driver X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Nov 2009 01:07:39 -0000 > And if I'm reading the SVN commit right, it went to -STABLE (aka > RELENG_8) but not head (aka "."). =A0It still won't fix all of FreeBSD 7 > install mediums, right? =A0or is that "to come", maybe in 7.3? > > > Also, if I'm reading the commit right, 8.0-RELEASE is going to have > sbp(4) enabled in GENERIC too. =A0Can someone make sure I'm reading that > right? > Just so that this is crystal clear: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/amd64/conf/GENERIC As of this moment, device sbp is commented out of the GENERIC kernel configuration for RELENG_8_0 branch *and* tagged with the RELENG_8_0_0_RELEASE tag, so the release build will have sbp disabled in the default GENERIC kernel configuration. (In other words, you should not have boot hangs by default due to firewire in 8.0 release) As far is 7.x is concerned, the current RELENG_7 branch (as of this moment) still has device sbp enabled. As far as 7.3 or future MFC to RELENG_7 of a fix or workaround, that remains to be seen, but the best thing to do is to make certain that the PR has all the necessary information provided, and to occasionally test with the latest -current (9.0) source and provide any debugging information if asked. 9.0 (aka -current) specifically left device sbp enabled so that people can continue to test and fix this bug (gives better exposure to the code). Make sense ? Good Luck. --_Dave