Send users mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
http://rt2x00.serialmonkey.com/mailman/listinfo/users_rt2x00.serialmonkey.com
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of users digest..."
Today's Topics:
1. Re: Kernel crash in bridge module: unable to handle kernel
paging request (Michael Maier)
----------------------------------------------------------------------
Message: 1
Date: Fri, 18 Apr 2014 20:10:39 +0200
From: Michael Maier <[email protected]>
To: [email protected], "[email protected]"
<[email protected]>, "[email protected]"
<[email protected]>
Subject: Re: [rt2x00-users] Kernel crash in bridge module: unable to
handle kernel paging request
Message-ID: <[email protected]>
Content-Type: text/plain; charset="iso-8859-1"
Michael Maier wrote:
> Hello!
>
> I'm using the following configuration on CentOS 6.5 w/ lt-kernel
> (3.10.37) - or any other kernel version.
>
> brctl addbr br0
> brctl addif br0 eth0
>
> ip li add vxlan0 type vxlan id 1 group 239.1.1.1 ttl 1 dev ra0
>
> brctl addif br0 vxlan0
>
> This is one end of a vxlan tunnel via WLAN.
>
> At the moment the first package arrives the bridge, the 64 bit-kernel
> crashes (32 bit kernel works perfectly). What could be the reason for
> the crash w/ 64 bit kernel? Btw: there isn't any problem even w/ 64
> bit kernel as long as the bridge code isn't involved.
The rt5572sta driver (DPO_RT5572_LinuxSTA_2.6.1.3_20121022) isn't
completely 64 bit stable. The attached patch makes rt5572sta working
with 64bit kernels even when used with a bridge like mentioned above.
The patch is derived from
https://github.com/ashaffer/rt3573sta/commit/2654eaee416f238a6651465c88a804ee251afe74
- there it was applied to rt3573 driver from Ralink / Mediatek.
I applied and tested it for rt5572sta (which is the newer one and
supports a lot more chips, amongst others rt3573) and kernel 3.13.6 / 64
bit. I suppose it to work with 3.10.x, too.
I detected, that bridging does not work with 3.14.x - but there is no
crash - it just doesn't work (packages came in in eth0, go through the
bridge and vxlan, are remotely answered, but the sent response can only
be seen in the vxlan and br0 device - but it can't be seen in eth0 -
strange).
Michael
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ralink-64bit-1.diff
Type: text/x-patch
Size: 1736 bytes
Desc: not available
URL:
<http://rt2x00.serialmonkey.com/pipermail/users_rt2x00.serialmonkey.com/attachments/20140418/d58a8c24/attachment-0002.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ralink-64bit-2.diff
Type: text/x-patch
Size: 715 bytes
Desc: not available
URL:
<http://rt2x00.serialmonkey.com/pipermail/users_rt2x00.serialmonkey.com/attachments/20140418/d58a8c24/attachment-0003.bin>
------------------------------
Subject: Digest Footer
_______________________________________________
users mailing list
[email protected]
http://rt2x00.serialmonkey.com/mailman/listinfo/users_rt2x00.serialmonkey.com
------------------------------
End of users Digest, Vol 62, Issue 2
************************************
