Re: [OpenWrt-Devel] Alix 2D13 on latest trunk, traces in dmesg on bootup?

2012-02-26 Thread Philip Prindeville
I build on Fedora 16. On 2/26/12 4:31 PM, Adam Gensler wrote: > Philip, > > Presumably you're running the newest trunk images on your alix boards > and are not seeing this problem? What OS/version are you building with? > I'm using Ubuntu 10.03 LTS as I have been for a while. I wouldn't mind

Re: [OpenWrt-Devel] Alix 2D13 on latest trunk, traces in dmesg on bootup?

2012-02-26 Thread Philip Prindeville
It might also be helpful to get symbolic addresses and not just hex addresses. On 2/25/12 10:48 AM, Adam Gensler wrote: > Does anyone else have any thoughts into this? Other suggestions I can > try? Seems someone else is seeing the same issue as I've found the > following output sitting on past

Re: [OpenWrt-Devel] Alix 2D13 on latest trunk, traces in dmesg on bootup?

2012-02-26 Thread Adam Gensler
Philip, Presumably you're running the newest trunk images on your alix boards and are not seeing this problem? What OS/version are you building with? I'm using Ubuntu 10.03 LTS as I have been for a while. I wouldn't mind spinning a VM with whatever distro you're using to give that a try. Tha

Re: [OpenWrt-Devel] Alix 2D13 on latest trunk, traces in dmesg on bootup?

2012-02-26 Thread Adam Gensler
Just finished building two fresh trunk pulls (which, at the time of this writing were at r30733). These are clean checkouts from svn that haven't been mangled in any way. I set the target to x86/alix2. On one I selected egblic 2.13 and on the other I left it at defaults (uclibc). I changed noth

Re: [OpenWrt-Devel] Alix 2D13 on latest trunk, traces in dmesg on bootup?

2012-02-26 Thread Adam Gensler
I can give that a try, however, I build against the default uclibc library normally. On 2/25/12 10:10 PM, Philip Prindeville wrote: A couple of other things to try. I build with: CONFIG_USE_EGLIBC=y CONFIG_EGLIBC_VERSION_2_13=y and I use the default gcc. On 2/25/12 10:48 AM, Adam Gensler w