firewire disk stopped working

[Sean Bruno]

On Wed, 2009-02-18 at 20:52 -0800, Sean Bruno wrote:
> On Thu, 2009-02-19 at 03:12 +0200, Boris Kotzev wrote:
> > On сряда 18 февруари 2009 21:26:31 you wrote:
> > > On Sun, 2009-02-15 at 17:27 +0200, Boris Kotzev wrote:
> > > > On неделя 15 февруари 2009 01:12:40 you wrote:
> > > > > If you haven't already, boot back into the previous kernel environment
> > > > > and let me know what revision of CURRENT it was that worked.
> > > > >
> > > > > Then I'll need to know what version you were using that broke.
> > > > >
> > > > > I'm trying to get my AMD64 system built this weekend to test things.
> > > > >
> > > > > Sean
> > > >
> > > > Verbose dmesg from the working system:
> > > >
> > > > http://host7.net62.hdsl-213-169.fastbg.net/dmesg.working.txt
> > > >
> > > > Verbose dmesg from the broken system:
> > > >
> > > > http://host7.net62.hdsl-213-169.fastbg.net/dmesg.broken.txt
> > > >
> > > > (The cable was plugged in after the system had had already booted - the
> > > > output from the disk is found at the end.)
> > > >
> > > > Please, feel free to ask for more details, if necessary.
> > > >
> > > > Thanks,
> > > >
> > > > Boris Kotzev
> > >
> > > Looking over your logs, I can't quite see what the failure is.  There
> > > seems to be a format error, I'm just not sure what is being requested.
> > >
> > > Can you update to -current, and set:
> > > debug.sbp_debug = 1
> > > debug.firewire_debug = 1
> > >
> > > Then repost your dmesg.
> > >
> > > Sean
> > 
> > Hi,
> > 
> > The dmesg output after plugging the cable are as follows (full verbose dmesg can be
> > found at http://host7.net62.hdsl-213-169.fastbg.net/dmesg.debug.txt ):
> 
> I went over everything and came up with the following patch.  Let me
> apply this to -current and let me know if it makes any difference.
> 
> Sean

Ok, this didn't break anything for me.  Let me know if this works for
you.

Sean