Date: Fri, 29 Mar 2013 10:58:32 -0700 From: Adrian Chadd <adrian@freebsd.org> To: =?ISO-8859-1?Q?Ren=E9_Ladan?= <rene@freebsd.org> Cc: arm@freebsd.org, Ian Lepore <ian@freebsd.org> Subject: Re: signal 11 after kernel update r247742 -> r248706 Message-ID: <CAJ-VmokCuu1B9hT4XxhyEmegT7X5N31tFBtvz2fuHQY3k=akwg@mail.gmail.com> In-Reply-To: <5155BC1C.2000104@freebsd.org> References: <51545932.9050901@freebsd.org> <1364484652.36972.81.camel@revolution.hippie.lan> <515466B5.4020403@freebsd.org> <5155BC1C.2000104@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 29 March 2013 09:06, Ren=E9 Ladan <rene@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! Adrian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-VmokCuu1B9hT4XxhyEmegT7X5N31tFBtvz2fuHQY3k=akwg>