Went up to kernel version 3.2.5, problem still occurs. Above 3.2.5
requires refreshing the kernel patches.
On 2/29/12 11:18 PM, Adam Gensler wrote:
For what its worth I spent some time this evening putting together a
Fedora Core 16 virtual machine to test with. I pulled a fresh copy of
trunk and built the alix2 target and got the same traces on boot up.
At this point I'm sure the issue isn't with my build environment but is
an issue in trunk. Unfortunately my kernel-debugging-foo isn't strong
enough to move closer to resolution.
On 2/28/12 7:09 PM, Adam Gensler wrote:
Nothing I'm finding online seems to indicate a simple procedure for
this. Perhaps I'm not searching for the correct terminology. If you have
a sample / example I'd certainly take a look at doing it.
On 2/28/12 5:12 PM, Philip Prindeville wrote:
As it turns out you only need 2-3 commands... you can almost script it
with macros.
On 2/28/12 2:17 PM, Adam Gensler wrote:
Unfortunately I have zero experience with gdb. It would probably take
longer to learn how to use that than to refresh to the kernel
patches on
3.2 to support 3.2.7 so I could try that version to see if its already
fixed.
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
