Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 12 Jun 2005 20:50:39 +0200
From:      Diego 'Flameeyes' =?iso-8859-1?q?Petten=F2?= <flameeyes@gentoo.org>
To:        freebsd-firewire@freebsd.org
Subject:   fwip, Linux and NFS
Message-ID:  <200506122050.46760@enterprise.flameeyes.is-a-geek.org>

next in thread | raw e-mail | index | archive | help
--nextPart1186249.7UdBpvF2cO
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Hi,
I'm currently trying to use fwip driver to have a "dedicated" line for NFS=
=20
between my Linux box and the FreeBSD 5.4 one (Linux as server, FBSD as=20
client).
Unfortunately, seems like the connection isn't stable. It starts fine and w=
hen=20
I start pinging the the host it works.
But when I start using the NFS (for example I tried moving a CVS checkout f=
rom=20
local disk to NFS share), it starts complaining that NFS doesn't respond:

fwohci0: unrecoverable error
nfs server 192.168.1.1:/var/portage: not responding
nfs server 192.168.1.1:/var/portage: not responding
[.. a lot of this ..]

then if I issue a fwcontrol -r, i get:

fwohci0: Initiate bus reset
fwohci0: BUS reset
fwohci0: node_id=3D0x8800ffc0, gen=3D12, non CYCLEMASTER mode
fwohci0: txd err=3D 0 No stat
fwohci0: txd err=3D 0 No stat
[.. a lot of this ..]
fwohci0: txd err=3D 0 No stat
fw_rcv: unknown response WRES(2) src=3D0xffc1 tl=3D0x31 rt=3D1 data=3D0x845=
1ae0d
try ad-hoc work around!!
no use...
fw_rcv: unknown response WRES(2) src=3D0xffc1 tl=3D0x31 rt=3D1 data=3D0x845=
1ae0e
try ad-hoc work around!!
no use...
[.. a lot of this..]
firewire0: 2 nodes, maxhop <=3D 1, cable IRM =3D 1
nfs server 192.168.1.1:/var/portage: is alive again
[.. a couple of this ..]
nfs server 192.168.1.1:/var/portage: is alive again
fwohci0: unrecoverable error
Unknown service addr 0xffff:0xf0000234 WREQQ(0) src=3D0xffc1 data=3Dc000001f
nfs server 192.168.1.1:/var/portage: not responding

and then again.

The controller on the FBSD box is:
fwohci0@pci2:0:0:       class=3D0x0c0010 card=3D0x2356167e chip=3D0x00f2103=
3=20
rev=3D0x01 hdr=3D0x00
    vendor   =3D 'NEC Electronics Hong Kong'
    device   =3D 'uPD72874 IEEE1394 OHCI 1.1 3-port PHY-Link Ctrlr'
    class    =3D serial bus
    subclass =3D FireWire

and the one in the Linux one is:
0000:00:07.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host=20
Controller (rev 80) (prog-if 10 [OHCI])
        Subsystem: ASUSTeK Computer Inc.: Unknown device 808a
        Flags: bus master, medium devsel, latency 64, IRQ 193
        Memory at faa00000 (32-bit, non-prefetchable)
        I/O ports at a800 [size=3D128]
        Capabilities: [50] Power Management version 2

I think the problem is with FBSD because it works fine connecting the same=
=20
Linux box to the iBook with OSX 10.4.
The same problem happen if I leave a ping running for more than 20 minutes.

There's something I can try to have this working?
=2D-=20
Diego "Flameeyes" Petten=F2
Gentoo Developer (Gentoo/FreeBSD, Video, Gentoo/AMD64)

http://dev.gentoo.org/~flameeyes/


--nextPart1186249.7UdBpvF2cO
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQBCrIQGe2h1+2mHVWMRAtsnAJ93/z61MM/gWo8SYew4b4tfEDVlgQCeOePs
KAI9PCVxb5b5ZVaK0UxZ1Dc=
=9IrV
-----END PGP SIGNATURE-----

--nextPart1186249.7UdBpvF2cO--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200506122050.46760>