(Adding [email protected] in the mail loop). Paul van Gool <[email protected]> [2013-03-05 18:29:10]:
> Petr, Hi, > I'm not a member of openwrt-devel mailing list but wanted to let you know I > am seeing the same thing. thank you for the information, now I at least know, that it's not happening just to me, because I've a faulty unit (since the error is quite strange so I was suspecting some HW issue). And from your post it seems, like it's happening in the trunk also. > I reported it here: https://forum.openwrt.org/viewtopic.php?id=42563 I'm afraid, that nobody sane has reading the forums :) It's time consuming and a total mess usually... One usually report the issues to the issue tracking system (Trac in case of OpenWRT) and on the development mailing list (as AA hasn't been released yet). But I don't know the exact steps for bug reporting for OpenWRT off-hand, you've to look it up yourself on the web. > But no comments yet. No wonder :) > I'm planning to go back to an older openwrt version to see if that resolve > the issue. Have you found a solution yet? No, I didn't found any solution yet, but I didn't investigated it much further either. I've just compared the codepaths in the kernel around that warning in the recent kernels and they seems to be same, so the issue might lie somewhere deeper. I plan to take a look into it when I have more spare time. -- ynezz _______________________________________________ openwrt-devel mailing list [email protected] https://lists.openwrt.org/mailman/listinfo/openwrt-devel
