Hi Adrian, On Fri, Mar 23, 2018 at 12:46:02AM -0700, Adrian Chadd wrote: > Hi, > > The stack backtrace looks like a null pointer dereference. >
"Stopped at 0". Does that mean the PC is at 0, or just that we tried to load 0 ? > The concurrencykit website mentions ARM and MIPS as future ports. Is > this actually true? Is concurrencykit supposed to actually run on > ARM/MIPS? Did anyone test? Actual MIPS hardware that we run on is like > $50. It's not exactly spendy to test out FreeBSD code on real > hardware. :) > If the website states that then it is outdated. There is a native arm port for quite some time. As for mips, it only works using gcc builtins, but it has been tested at some point. > I can't even build the regression suite from CK on github to run on > mips32 hardware. I don't suppose anyone would be able to figure that > particular mess out? > How does it fail ? > I'd really like to work some more on wifi stack stuff on this embedded > platform stuff and this just threw a spanner in my plans. I'd really > appreciate some help here cause I don't have time to wade through more > platform breakage just to do wifi stack / driver work. I have limited > spare time as it is these days :( > > Thanks, I'm certainly willing to help you. I'll try to reproduce it with qemu or something. Can you tell me a bit more about your setup, so that I can get it to happen ? Unfortunately, I'll be away for the week-end, so probably won't be able to do so before at least sunday evening (french time). Regards, Olivier _______________________________________________ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
