From owner-freebsd-usb@FreeBSD.ORG Wed Jul 7 22:00:41 2010 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B1112106566C; Wed, 7 Jul 2010 22:00:41 +0000 (UTC) (envelope-from seanbru@yahoo-inc.com) Received: from mrout2-b.corp.re1.yahoo.com (mrout2-b.corp.re1.yahoo.com [69.147.107.21]) by mx1.freebsd.org (Postfix) with ESMTP id 73F718FC14; Wed, 7 Jul 2010 22:00:41 +0000 (UTC) Received: from [127.0.0.1] (cheese.corp.yahoo.com [216.145.50.99]) by mrout2-b.corp.re1.yahoo.com (8.13.8/8.13.8/y.out) with ESMTP id o67LkAQQ091073; Wed, 7 Jul 2010 14:46:10 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; s=serpent; d=yahoo-inc.com; c=nofws; q=dns; h=subject:from:to:cc:in-reply-to:references:content-type:date: message-id:mime-version:x-mailer:content-transfer-encoding; b=jFKG52iczqSPzvqh1VmtAOgwoxvlMDfmdSGkxN9tgzf3igBsU1+O99gmTseaofXk From: Sean Bruno To: Jeremy Chadwick In-Reply-To: <20100707185928.GA16180@icarus.home.lan> References: <4C34C5DE.7040007@aldan.algebra.com> <20100707185928.GA16180@icarus.home.lan> Content-Type: text/plain; charset="UTF-8" Date: Wed, 07 Jul 2010 14:46:10 -0700 Message-ID: <1278539170.2512.86.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.28.3 (2.28.3-1.fc12) Content-Transfer-Encoding: 7bit Cc: "freebsd-stable@freebsd.org" , "Mikhail T." , "re@freebsd.org" , "tom@hur.st" , "freebsd-usb@freebsd.org" Subject: Re: 8.x grudges X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Jul 2010 22:00:41 -0000 > > > 5. > > One of the upgraded systems would repeatedly hang at boot, until I > > disabled the on-board firewire-device through the BIOS... It was > > not a problem under 7.x, although I don't know, whether the device > > actually worked. > > This is a commonly-reported problem, assuming "at boot" you mean "while > the kernel is starting". Or unless you're using a certain model of > Shuttle box, but that turned out to be literally a BIOS bug: > > http://koitsu.wordpress.com/2009/05/22/shuttle-sg45h7-firewire-bug-in-bios-sg45u10o/ > Looking at this link, it doesn't match the described issue. Mikhail's machine would not boot *until* he disabled the firewire controller in the BIOS. The referenced issue on that Shuttle based machine talks about disabling the firewire controller and *then* it still being alive when the system powers on and crashing the system. I interpret this as a bug. Sean