generating firewire traffic

I can cause a kernel panic:
http://bugzilla.kernel.org/show_bug.cgi?id=13075
by plugging in a dv cam and running the following for a few minutes:

dvgrab - | nc 192.168.1.216 2007 | nc 192.168.1.216 2008 > /dev/null

on 192.168.1.216 I am running my home made echo server:
while /bin/true;do  nc -l -p 2007 -c cat; done &
while /bin/true;do  nc -l -p 2008 -c cat; done &

To make it easier to debug, I would like to remove the need for the
cam and the dvgrab command and just use something that stimulates the
firewire hardware without anything plugged into the port.

Or if I need something plugged in, then not having to worry about what
is plugged in (cam, drive, 2nd firewire port...)

and in case it is somehow dependent on the timing created by a dv cam,
something like cat /dev/raw1394 so that "install dvgrab" isn't needed.

Or convince me that the panic isn't dependent on firewire at all,
which I have been told, but have not been able to reproduce.

Or buy me a pony and I'll stop worrying about this :)

-- 
Carl K

------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables unlimited
royalty-free distribution of the report engine for externally facing 
server and web deployment.
http://p.sf.net/sfu/businessobjects