Messages in this thread | | | Subject | Re: [git pull] FireWire fixes | From | Maxim Levitsky <> | Date | Sat, 18 Sep 2010 02:00:09 +0200 |
| |
On Sat, 2010-09-18 at 01:41 +0200, Stefan Richter wrote: > Maxim Levitsky wrote: > > Running new stack on the laptop + old stack on the desktop gave me about > > 18-30 Mbit/s speeds varying all the time. > > Running both with the new stack results in corrupted packets and sftp > > exits immediately. > > firewire-net, the IP over 1394 driver, is still marked as experimental not > because somebody forgot to remove that mark but because we mean it. But so is > its older counterpart, eth1394. Both eth1394 and firewire-net are chronically > underused and undermaintained. I sure do understand it! I just did another round of testing and report the results.
Do you have an idea what could cause such low speeds?
> > > The problems I so hoped to be fixed in new stack still persist: > > > > Cable disconection/reconnection still results in the link loss till > > ifconfig down/up. > > > > Suspend/resume also results in the link loss. > > Sounds like something that shouldn't be too hard to fix by anybody who can > spare the time. Surely a higher-level problem somewhere in firewire-net. > > > Driver still has panics on some occasions. > > At the moment I suspect that this OTOH might not be a firewire-net problem but > possibly a race in firewire-ohci which is only triggered by workload as > firewire-net imposes it (heavy AT context usage). Thanks for information!
Best regards, Maxim Levitsky
| |