Wolfgang Grandegger wrote: > bhupesh.sharma wrote: >>>> I gathered from the discussions on this mailing list that this warning has >>>> been solved by: >>>> 1. Migrating to newer kernel version, 2.6.30 >>>> 2. compile *without* the define: CONFIG_CAN_DEV_SYSFS=y >>>> >>>> For me, *1* is not a possible option. I have tried alternative *2* and it >>>> works fine. >>> You mean it works fine with CONFIG_CAN_DEV_SYSFS=y (using SysFS instead >>> of netlink)? >> Sorry if I caused any confusion, I meant with CONFIG_CAN_DEV_SYSFS=y (using >> SysFS instead of netlink) I do not get this warning message. > > That makes sense. > >> Please let me know, if this is a known issue with kernel 2.6.27 and is there >> any other way to solve the same. >> >> I have seen the mails exchanged on a similar issue at >> `https://lists.berlios.de/pipermail/socketcan-core/2009-June/002657.html` > > It seems to be a known issue, but we do not have a fix yet. I will have > a closer look.
I just sent a patch fixing the oops when the device is registered with the netlink interface with subject: [PATCH] can: fix WARN_ON dump in net/core/rtnetlink.c:rtmsg_ifinfo() Please give it a try and avoid using the deprecated SysFS interface. Wolfgang. _______________________________________________ Socketcan-core mailing list [email protected] https://lists.berlios.de/mailman/listinfo/socketcan-core
