Matthias Fuchs wrote: > RHEL5.4 BZ #495863 > > This is a backport of the following upstream patches: > > commit 33dccbb050bbe35b88ca8cf1228dcf3e4d4b3554 > Author: Herbert Xu <[email protected]> > Date: Thu Feb 5 21:25:32 2009 -0800 > > commit 4cc7f68d65558f683c702d4fe3a5aac4c5227b97 > Author: Herbert Xu <[email protected]> > Date: Wed Feb 4 16:55:54 2009 -0800 > > commit 9a279bcbe347496799711155ed41a89bc40f79c5 > Author: Herbert Xu <[email protected]> > Date: Wed Feb 4 16:55:27 2009 -0800 > > > I took a glace an the very last mentioned backported patch 9a279bcb. > Hmm this is one of our old frieds :-) > > See: http://lists.berlios.de/pipermail/socketcan-users/2009-June/000959.html > > So to come to a conclusion: Good Socket-CAN, bad RH.
Puuh :-) > > You really find 2.6.30 backports in RHEL 2.6.18 kernels. > > So I think we have to revert he above patch in the RHEL kernel. Or you apply both(!) of these two patches that fix it in the 2.6.30-stable tree ... http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.30.y.git;a=commitdiff;h=172570a224fe66d560c097e48fca15b620c76e72 http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.30.y.git;a=commitdiff;h=768db3901820f355efb158c6913ecdb19bbfd9ed If the networking in RHEL 2.6.18 is nearly up to date to the 2.6.30, this might work also. Regards, Oliver _______________________________________________ Socketcan-core mailing list [email protected] https://lists.berlios.de/mailman/listinfo/socketcan-core
