Re: r8169 802.1q/MTU bug

Re: r8169 802.1q/MTU bug

[James Harr]

Hi,
The driver you sent gives me an error when I try to compile and load it with 
2.6.11.11:

# make
[...]
  CC [M]  drivers/net/r8169.o
  drivers/net/r8169.c: In function `rtl8169_down':
  drivers/net/r8169.c:2589: warning: implicit declaration of function
  synchronize_sched
[...]

# insmod drivers/net/r8169.ko
insmod: error inserting 'drivers/net/r8169.ko': -1 Unknown symbol in module


It does a similar thing when I try to install it:

# make modules_install
[...]
if [ -r System.map ]; then /sbin/depmod -ae -F System.map  2.6.11.11; fi
WARNING: /lib/modules/2.6.11.11/kernel/drivers/net/r8169.ko needs unknown 
symbol synchronize_sched

As I noted in a previous email, it doesn't give me this problem when I have 
jumbo frames enabled on my switch.

Since I found out my switch supported jumbo frames, I started to toy around 
with larger MTUs. When a VLAN's MTU was set to 7200, my system locked up. I 
didn't have this problem at 7196. Also, the crash problem wasn't there on a 
regular interface with no VLANs and the MTU at 7200.

Thanks,
James Harr

On Monday 30 May 2005 2:11 am, you wrote:
> James Harr <james@grickle.org> :
> [...]
>
> > I've been using a gigabit RealTek 8169 card for a while, I just recently
> > started using 802.1q with them. I stumbled upon the problem described at
> > the top of here:
> >
> > http://www.candelatech.com/~greear/vlan/howto.html
>
> Can you try the attached version of the r8169 driver with the latest
> kernel ?
>
> If the issue is still there, it is almost surely the one you link to.
> I'll give it a look when I'm back at home, it should not be long to fix.
>
> Please Cc: netdev@oss.sgi.com (it is archived and googlable).


-- 
James Harr <james@grickle.org>
http://www.grickle.org/

Re: r8169 802.1q/MTU bug

[Francois Romieu]

James Harr <james@grickle.org> :
[...]
> The driver you sent gives me an error when I try to compile and load it with 
> 2.6.11.11:

The driver that I sent you builds with 2.6.12-rc4. Please try 2.6.12-rc4 +
the aforementioned driver.

If it still crashes (?), tell if your .config matches:

CONFIG_R8169=m
CONFIG_R8169_NAPI=y
# CONFIG_R8169_VLAN is not set

or:

CONFIG_R8169=m
CONFIG_R8169_NAPI=y
CONFIG_R8169_VLAN=y

An history of the commands issued to set the config before the crash
would be welcome too.

--
Ueimor

Re: r8169 802.1q/MTU bug

[Jon Mason]

On Monday 30 May 2005 07:27 pm, James Harr wrote:
> Hi,
> The driver you sent gives me an error when I try to compile and load it
> with 2.6.11.11:
>
> # make
> [...]
>   CC [M]  drivers/net/r8169.o
>   drivers/net/r8169.c: In function `rtl8169_down':
>   drivers/net/r8169.c:2589: warning: implicit declaration of function
>   synchronize_sched
> [...]
>
> # insmod drivers/net/r8169.ko
> insmod: error inserting 'drivers/net/r8169.ko': -1 Unknown symbol in module
>
>
> It does a similar thing when I try to install it:
>
> # make modules_install
> [...]
> if [ -r System.map ]; then /sbin/depmod -ae -F System.map  2.6.11.11; fi
> WARNING: /lib/modules/2.6.11.11/kernel/drivers/net/r8169.ko needs unknown
> symbol synchronize_sched
>
> As I noted in a previous email, it doesn't give me this problem when I have
> jumbo frames enabled on my switch.
>
> Since I found out my switch supported jumbo frames, I started to toy around
> with larger MTUs. When a VLAN's MTU was set to 7200, my system locked up. I
> didn't have this problem at 7196. Also, the crash problem wasn't there on a
> regular interface with no VLANs and the MTU at 7200.

I wonder if this is related to the adapter breaking large frames into multiple 
descriptors.  On normal (non-VLAN) frames, this happens at MTU 8169.  I 
wonder if enabling VLAN and jumbo frames (a combination I never tried) brings 
down the threshold to MTU 7200.  

Thanks,
Jon

Re: r8169 802.1q/MTU bug

[Francois Romieu]

Jon Mason <jdmason@us.ibm.com> :
[...]
> I wonder if this is related to the adapter breaking large frames into
> multiple descriptors.  On normal (non-VLAN) frames, this happens at MTU
> 8169. I wonder if enabling VLAN and jumbo frames (a combination I never
> tried) brings down the threshold to MTU 7200.  

Testing suggests that there is at least a size filtering issue (fixed
in netdev-2.6.git but not in 2.6.11.xx nor in 2.6.12-rc). It is unrelated
to hardware vlan support and happens a few bytes above the MTU on the vlan
device (which is set to the same value as the adapter). Of course different
issues could hide in the dark.

--
Ueimor