[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4C93FCC7.9040406@s5r6.in-berlin.de>
Date: Sat, 18 Sep 2010 01:41:59 +0200
From: Stefan Richter <stefanr@...6.in-berlin.de>
To: Maxim Levitsky <maximlevitsky@...il.com>
CC: Linus Torvalds <torvalds@...ux-foundation.org>,
Andrew Morton <akpm@...ux-foundation.org>,
linux1394-devel@...ts.sourceforge.net, linux-kernel@...r.kernel.org
Subject: Re: [git pull] FireWire fixes
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.
> 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).
--
Stefan Richter
-=====-==-=- =--= =--=-
http://arcgraph.de/sr/
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists