Date: Wed, 1 Jul 2009 09:48:38 +0100 (BST) From: Robert Watson <rwatson@FreeBSD.org> To: Julian Stecklina <js@alien8.de> Cc: freebsd-current@freebsd.org Subject: Re: 8-CURRENT Firewire Message-ID: <alpine.BSF.2.00.0907010947380.53988@fledge.watson.org> In-Reply-To: <87hbxxp5ot.fsf@tabernacle.lan> References: <1246316092.3981.11.camel@Lappy> <87hbxxp5ot.fsf@tabernacle.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 1 Jul 2009, Julian Stecklina wrote: >> -CURRENT has some slightly different Firewire code in it than 6/7. If you >> have an opportunity to test it with your Firewire hard drives and cameras >> I'd really appreciate it. >> >> Stuff that's changed: >> multi-speed compatible devices will acutally work. >> a 400/800 device is connected to a 400/800 compatible >> firewire card via a 400 connection will work at 400 >> fwcontrol understands multiple firewire cards as multiple >> buses now. most commands now take a -u argument to >> indicate the bus. >> >> Please report to the -firewire if you get a chance to test. It would be >> great to get positive as well as negative results. > > I have an AMD 780G board with onboard Firewire controller. 8-CURRENT hangs > at boot with: > > run_interrupt_driven_hooks: still waiting after 60 seconds for xpt_config > run_interrupt_driven_hooks: still waiting after 120 seconds for xpt_config > ... > > If I disable the Firewire controller in the BIOS it boots fine. What is a > good way to debug this? I've seen similar reports of this on 7.x; Richard Clayton has a box that has done this since at least 7.1, and it's one of the reasons I added the debugging output above :-). Unfortunately, it's not in an easy position to debug on that box. Robert N M Watson Computer Laboratory University of Cambridge
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.0907010947380.53988>