Hi Oliver, On Wednesday 02 December 2009 22:02, Oliver Hartkopp wrote: > Matthias Fuchs wrote: > > Hi, > > > > what happened to this? > > > > I observed this behavior with Socket-CAN SVN r1091 on 2.6.30 kernels. > > Hi Matthias, > > this problem is *not* inside SocketCAN aka /linux/net/can/* ... > > It's inside the surrounding networking infrastructure. > > It has been fixed here: > http://patchwork.ozlabs.org/patch/28993/ > > Committed to Mainline Linux here (for 2.6.31) > http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=d55d87fdff8252d0e2f7c28c2d443aee17e9d70f > > Committed for 2.6.30-stable here (should be ok in 2.6.30.5) > http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.30.y.git;a=commitdiff;h=172570a224fe66d560c097e48fca15b620c76e72 > > So if you upgrade to 2.6.30.5 it should work as the problem is only between > 2.6.30 and 2.6.30.4 . > > Does that info help you?
thanks for this hint. It helped a lot. Matthias _______________________________________________ Socketcan-users mailing list [email protected] https://lists.berlios.de/mailman/listinfo/socketcan-users
