Date: Mon, 18 Aug 2008 21:00:03 -0700 From: Sean Bruno <sbruno@miralink.com> To: Dieter <freebsd@sopwith.solgatos.com> Cc: Scott Long <scottl@samsco.org>, freebsd-firewire@freebsd.org Subject: Re: Something broke :-( Re: fwcontrol update Message-ID: <48AA4543.1040404@miralink.com> In-Reply-To: <48AA2F1A.9040306@miralink.com> References: <200808190213.CAA20684@sopwith.solgatos.com> <48AA2F1A.9040306@miralink.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Sean Bruno wrote: > Dieter wrote: >> I tried rebooting again, and then powered up the camera >> and pressed play. Without running fwcontrol at all. >> The console spewed away. >> >> Just to be explicit, it didn't do this until today. >> >> So I think the kernel device driver needs to reset and/or >> initialize something, probably on the fw controller chip. >> Thoughts? >> > Ok, good times. > Can you post the output of "fwcontrol -p" for me? > Looking over the driver code, I can't see any clear path from what malfunctioned to the errors you are seeing now. I would think that a simple bus reset from fwcontrol would clear this. The BUSRST message means that the driver is getting a BUS_RESET when it's internal state machine is not BUS_RESET. Kind of confusing, but that means you should be able to clear it out with a "fwcontrol -r -u 1" ??? You will _HAVE_ to use the new code to send a bus reset to the second bus. -- Sean Bruno MiraLink Corporation 6015 NE 80th Ave, Ste 100 Portland, OR 97218 Cell 503-358-6832 Phone 503-621-5143 Fax 503-621-5199 MSN: sbruno@miralink.com Google: seanwbruno@gmail.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?48AA4543.1040404>