signal 11 after kernel update r247742 -> r248706
René Ladan
rene at freebsd.org
Thu Apr 4 13:20:15 UTC 2013
On 29-03-2013 18:58, Adrian Chadd wrote:
> On 29 March 2013 09:06, René Ladan <rene at freebsd.org
> <mailto:rene at freebsd.org>> wrote:
>
>
> >> I'm at r248509 on my rpi and everything is good; maybe that'll help
> >> narrow the binary search.
> > Ok, I'll start looking from there.
>
> The 'skeleton' unmapped IO commit was r248508, so that one is OK.
> There seem to be some unmapped IO changes between r248509 and r248706,
> (e.g. r248510-r248512, r248514-r248522, r248550, r248568-r248569,
> r248596) but I think it is more related to something closer to
> userland?
>
> But the other commits between r248508 and r248706 look OK to me
> (including r248534 (jilles, SOCK_CLOEXEC, SOCK_NONLBOCK,
> MSG_CMSG_CLOEXEC))
>
>
> Are you able to continue bisecting those changes?
>
> Thanks for your help so far!
>
Checkpoint: r248509 boots fine (including init), but running e.g. python
built under r247742 dumps core during startup.
kdump output: ftp://rene-ladan.nl/pub/freebsd/python2.7.ktrace
I'm building r248706 now to check if the boot/init is still OK
I guess upgrading to today's CURRENT would also be informative?
w
René
More information about the freebsd-arm
mailing list