Re: The 8169 driver: issue with cross cable

Re: The 8169 driver: issue with cross cable

[Willy Gardiol]

[-- Attachment #1: Type: text/plain, Size: 4975 bytes --]


Problem: r8169 hosed sporadically using a cross-cable.

Configuration:
- server side: x86 box with r8169 on a Hamlet PCI card, file server NFS. 
- client side: x86 box with r8169 inegrated on a nForce2 motherboard. NFS-root 
on the server (no local hard drives, four NFS mounts)
- connection: cross cable UTP CAT5

(Alternative configuration:
- RTL-8139 (8139too module) PCI card on both boxes. With this configuration 
(same kernel, same files, same cable) everything works great.)

The problem is present with any kernel versions up to 2.6.10 (tried many 
different kernels).

Step to reproduce the problem: grab a few CDs with grip (tested with ATAPI 
cdrw without scsi emulation). 

Syntomps: one of the mounts will be hosed while the others will work. After 
some time either the nfs activity hangs on all mounts or the hosed mount will 
un-hose. Tipically it will hose again soon.

I am now doing tests using kernel 2.6.11-r4 with Francois's patch.

I did two tests, one at 1000mbit/sec and one at 100mbit/sec limiting the speed 
using ethtool.

The problem persist in both tests. I launch grip and start grabbing a CD, 
after the first track is read from che CD the process hangs. Then i start a 
second grip and start again ripping the same CD, this time the entire nfs 
mount hangs.

Per each test i reported some general data:
Output of "lspci -vx" posted to:  spci-vx.txt
Output of "lsmod" posted to: modules.txt
Output of boot posted to:dmesg.txt
Output of ethtool on r8169 (and rtl-8139): ethtool.txt

And specific data:
Output ifconfig and interrupts immediately after boot: 
interrupts-ifconfig-boot.txt
After some activity (login/startx/launch konsole, a few pings, and launch of 
grip):
interrupts-ifconfig-initial.txt
When the program grip is hosed:
interrupts-ifconfig-hosed.txt
When mount point /deposito is hosed:
interrupts-ifconfig-hosed2.txt

(note: grip works on /deposito)


I bzip2ed all this files into two archives, one per each test (one couple per 
server and one per client)

You can get them at:
http://www.gardiol.org/r8169/1000-client.tar.bz2
http://www.gardiol.org/r8169/1000-server.tar.bz2
http://www.gardiol.org/r8169/100-client.tar.bz2
http://www.gardiol.org/r8169/100-server.tar.bz2

At the beginning of each file i wrote the output of "uname -a".

I am available for any more data.
bye and thanks.

ps: i am not subscribed to the list please keep me in CC.

Alle Saturday 19 February 2005 21:50, hai scritto:
> Willy Gardiol <willy@gardiol.org> :
> [...]
>
> > i am sorry to bother you directly.
>
> No problem but it would be nice to Cc: netdev@oss.sgi.com.
>
> [...]
>
> > I have a fileserver and a remote client which both have a r8169 based
> > card. The server has a Hamlet card and the client has the gigabit chip
> > integrated.
>
> An 'lspci -vx' would be welcome. So will a complete dmesg from boot.
>
> > The two machines are linked with a cross cable about 20mt long, UTP CAT5.
>
> Which link settings does the r8169 negociate ('ethtool ethX') ?
>
> [...]
>
> > During one of these locks i can, as usual, access the other nfs mounts.
>
> Ok. So the card is not hosed.
>
> > I tried to:
> > - move PCI cards to avoid conflicts
> > - upgraded to latest stable kernel 2.6.10
> > - removed any binary only driver
> > - changed the server mounts and filesystems (ext3/reiserfs)
> >
> > Also, the problem is still present if i use one r8169 based and one
> > rtl-8139 100mbit card.
>
> Do you notice packet loss/errors or such on the 8169 side ? Typically, how
> does 'ifconfig' output like when a mount point is hosed ?
>
> > When i remove BOTH r8169 and use 100mbit only cards (two 8139 based pci
> > cards) i do not suffer from these hangs.
>
> Which kind of 8139 driver: 8139too or 8139cp ?
>
> > What can i do to solve this problem, or help you on the subject?
>
> It will need some debugging. It is not clear if the r8169 is the issue or
> if simply triggers the problem. Suggestions:
> - use 2.6.10-rc4 + attached patch;
> - avoid binary modules as I don't support them;
> - if r8169 negociates 1000Mbps, use ethtool to limit it at 100Mbps;
> - save the content of /proc/interrupts and ifconfig output at regular
>   interval (say, at boot, after some ping -q -f -l 16 a.b.c.d and once
>   a mountpoint is hung);
> - avoid gcc 2.95.x;
> - when a mountpoint is hung, issue 'echo t > /proc/sysrq-trigger' and save
>   the kernel output. This assumes CONFIG_MAGIC_SYSRQ=y at build time and
>   kernel.sysrq = 1 in /etc/sysctl.conf.
>
> If you have a straight cable, two 8169 should be able to do the crossing
> themselves.
>
> --
> Ueimor

-- 

! 
 Willy Gardiol - willy@gardiol.org
 www.gardiol.org
 +39 3492800983
 Use linux for MY freedom. 
 Your freedom may come as a side effect.

    "Era un mondo adulto,
     si sbagliava da professionisti"

      Paolo Conte, Boogie


[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: The 8169 driver: issue with cross cable

[Francois Romieu]

Willy Gardiol <willy@gardiol.org> :
[...]
> http://www.gardiol.org/r8169/1000-client.tar.bz2
> http://www.gardiol.org/r8169/1000-server.tar.bz2
> http://www.gardiol.org/r8169/100-client.tar.bz2
> http://www.gardiol.org/r8169/100-server.tar.bz2

Can you add a minimal exports/mount option description so that
I try to reproduce it here ?

--
Ueimor

Re: The 8169 driver: issue with cross cable

[Willy Gardiol]

[-- Attachment #1: Type: text/plain, Size: 2583 bytes --]


On the client fstab is:
/dev/sda1               /boot           ext2            noatime,noauto           
0 0
192.168.0.1:/shimitar   /               nfs             
noatime,rsize=8192,wsize=8192           0 0
192.168.0.1:/shimitar/home      /home           nfs             
noatime,rsize=8192,wsize=8192           0 0
192.168.0.1:/shimitar/deposito  /deposito               nfs             
noatime,rsize=16384,wsize=16384 0 0
192.168.0.1:/shimitar/deposito2 /deposito2              nfs             
noatime,rsize=16384,wsize=16384 0 0

(sda1 is a USB key, not mounted by default)

On the server fstab is:
/dev/hdc1               /shimitar       ext3            noatime                 
0 0
/dev/hdc2               /shimitar/home  ext3            noatime                 
0 0
/dev/hda4               /shimitar/deposito2     ext3            noatime                 
0 0
/dev/hdc4               /shimitar/deposito      ext3            noatime                 
0 0

And exports is:
/shimitar 192.168.0.2(rw,no_root_squash,async,no_subtree_check)
/shimitar/home 192.168.0.2(rw,no_root_squash,async,no_subtree_check)
/shimitar/deposito 192.168.0.2(rw,no_root_squash,async,no_subtree_check)
/shimitar/deposito2 192.168.0.2(rw,no_root_squash,async,no_subtree_check)
/mnt/tmp                192.168.0.2(rw,no_root_squash,async,no_subtree_check)

(mnt/tmp is not mounted on the client).

Something i did not emphatized: both boxes are connected to the internet via 
another eth device. 
The network configuration is:
- a switch 100mbit connected to the internet, each box has a direct cable to 
the switch (via 8139too eth device on both boxes). Dhcp.
- a cross cable between the two boxes connecting the r8169 eth device. 
192.168.0.0/24.


Alle Wednesday 23 February 2005 01:30, Francois Romieu ha scritto:
> Willy Gardiol <willy@gardiol.org> :
> [...]
>
> > http://www.gardiol.org/r8169/1000-client.tar.bz2
> > http://www.gardiol.org/r8169/1000-server.tar.bz2
> > http://www.gardiol.org/r8169/100-client.tar.bz2
> > http://www.gardiol.org/r8169/100-server.tar.bz2
>
> Can you add a minimal exports/mount option description so that
> I try to reproduce it here ?
>
> --
> Ueimor

-- 

! 
 Willy Gardiol - willy@gardiol.org
 www.gardiol.org
 +39 3492800983
 Use linux for MY freedom. 
 Your freedom may come as a side effect.

   "L'altrove è uno specchio in negativo. 
    Il viaggiatore riconosce il poco che è suo, 
    scoprendo il molto che non ha avuto e non avrà"

      Italo Calvino - Le città invisibili


[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: The 8169 driver: issue with cross cable

[Willy Gardiol]

[-- Attachment #1.1: Type: text/plain, Size: 1445 bytes --]


No luck.

Summary:
- 2.6.11 plain: works, still has the hung bug
- 2.6.11-mm1 + 2 patches: client system does not boot (unable to mount remote 
nfs root)
- 2.6.11 plain with the two patches: again, unable to mount remote nfs root
- 2.6.11 with all patches you send me, included your two patches: again, 
unable to mount remote nfs root.

Attached, the bzipped .config i used for the server and for the root 
(identical for all kernels)

Just an addendum, the problem seems to arise only when i use two r8169, if i 
have a r8169 and 1 8139too things seems to work fine.

bye

Alle Sunday 06 March 2005 17:03, hai scritto:
> Willy Gardiol <willy@gardiol.org> :
> [...]
>
> > So, i had not been able to test the r8169 with the patched 2.6.11.
> >
> > Always ready to help...
>
> Can you try:
> - 2.6.11 + r8169-470.patch + r8169-480.patch
> - 2.6.11-mm1 + r8169-470.patch + r8169-480.patch
>
> Even if the kernel do not work, I'd welcome their compressed .config.
>
> --
> Ueimor

-- 

! 
 Willy Gardiol - willy@gardiol.org
 www.gardiol.org
 +39 3492800983
 Use linux for MY freedom. 
 Your freedom may come as a side effect.

   "Cari fratelli dell'altra sponda
    cantammo in coro giù sulla terra
    amammo in cento l'identica donna
    partimmo in mille per la stessa guerra.

    Questo ricordo non vi consoli
    quando si muore si muore soli."

 (Il Testamento, Fabrizio De Andrè)



[-- Attachment #1.2: client-config.bz2 --]
[-- Type: application/x-bzip2, Size: 7118 bytes --]

[-- Attachment #1.3: server-config.bz2 --]
[-- Type: application/x-bzip2, Size: 6919 bytes --]

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: The 8169 driver: issue with cross cable

[Willy Gardiol]

[-- Attachment #1: Type: text/plain, Size: 836 bytes --]


I must correct myself, the problem persist even if i use only one r8169. Just, 
it is less frequent.

bye

Alle Sunday 06 March 2005 17:03, hai scritto:
> Willy Gardiol <willy@gardiol.org> :
> [...]
>
> > So, i had not been able to test the r8169 with the patched 2.6.11.
> >
> > Always ready to help...
>
> Can you try:
> - 2.6.11 + r8169-470.patch + r8169-480.patch
> - 2.6.11-mm1 + r8169-470.patch + r8169-480.patch
>
> Even if the kernel do not work, I'd welcome their compressed .config.
>
> --
> Ueimor

-- 

! 
 Willy Gardiol - willy@gardiol.org
 www.gardiol.org
 +39 3492800983
 Use linux for MY freedom. 
 Your freedom may come as a side effect.

   "La guerra non farà mai finire 
    alcuna guerra, nel migliore dei
    casi sarà stata una guerra in più."

      Gino Strada, Buskashì


[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]