From owner-freebsd-arm@FreeBSD.ORG Fri Mar 29 16:06:58 2013 Return-Path: Delivered-To: arm@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 121E43F3; Fri, 29 Mar 2013 16:06:58 +0000 (UTC) (envelope-from r.c.ladan@gmail.com) Received: from mail-we0-x233.google.com (mail-we0-x233.google.com [IPv6:2a00:1450:400c:c03::233]) by mx1.freebsd.org (Postfix) with ESMTP id 74ABAD7E; Fri, 29 Mar 2013 16:06:57 +0000 (UTC) Received: by mail-we0-f179.google.com with SMTP id p43so428597wea.38 for ; Fri, 29 Mar 2013 09:06:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:sender:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; bh=xE7d1G5XIQJpaiS3TH4FICcuVoGsY1urHvklKo3dkAU=; b=ccEqtDAIelxO4gIA2XUzf6JgBpI5pPeMfqz1SA+FRv1k8YLhgaFmJED3A2bOBEYzUN EGPs8L1FkD+zJu/Mu5tcV97Z+MMWIZ4C2lGHaLkbYyjhd1GYjYAoT2IjBzbUS73vKaEY 5objdgwp5ln5zEKDbenGRf5wlo5KDzfBHxfBERB88cQJQE2XmlKMskwsgjr8/3hhiuIW 7l8GsK+8nkISvIXv8GzGsxqEpl+Kc5nAyYyG6OrkCZ/H25MlQvxMFGQTejFSoDvukSYq Dwp8L6tfoj+AWm+8g3wSpZbeJCUBVcFl5xPE0O6ZMFn9yRWxnqdtXd/x4sorE9aQjVQQ HSww== X-Received: by 10.194.82.34 with SMTP id f2mr4411119wjy.25.1364573216119; Fri, 29 Mar 2013 09:06:56 -0700 (PDT) Received: from ?IPv6:2001:980:d7ed:1:64f2:5452:2b6d:45bd? ([2001:980:d7ed:1:64f2:5452:2b6d:45bd]) by mx.google.com with ESMTPS id f1sm122913wib.0.2013.03.29.09.06.54 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 29 Mar 2013 09:06:55 -0700 (PDT) Sender: =?UTF-8?Q?Ren=C3=A9_Ladan?= Message-ID: <5155BC1C.2000104@freebsd.org> Date: Fri, 29 Mar 2013 17:06:52 +0100 From: =?ISO-8859-1?Q?Ren=E9_Ladan?= User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130309 Thunderbird/17.0.4 MIME-Version: 1.0 To: Ian Lepore Subject: Re: signal 11 after kernel update r247742 -> r248706 References: <51545932.9050901@freebsd.org> <1364484652.36972.81.camel@revolution.hippie.lan> <515466B5.4020403@freebsd.org> In-Reply-To: <515466B5.4020403@freebsd.org> X-Enigmail-Version: 1.5.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Cc: arm@FreeBSD.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Mar 2013 16:06:58 -0000 On 28-03-2013 16:50, René Ladan wrote: > On 28-03-2013 16:30, Ian Lepore wrote: >> On Thu, 2013-03-28 at 15:52 +0100, René Ladan wrote: >>> Hi, >>> >>> after updating the kernel on my Raspberry PI (config RPI-B with ums >>> added) from r247742 to r248706 a lot of programs (including the r247742 >>> init) started to crash with signal 11. Manually copying files from >>> /usr/obj to the SD card (using another FreeBSD box) helped to get >>> userland back up and running, but now a lot of ports have similar >>> problems. For some binaries, copying the libraries was enough, other >>> binaries had to be copied themselves as well. >>> >>> Some questions: >>> - has anyone else experienced this (not necessarily on arm) ? I can try >>> to repeat this on a i386 VirtualBox host. >>> - the 20130304 entry in src/UPDATING about callout(9) looks a bit >>> suspicious? >>> - I have some kdump/core dump output available from python27 and pkgng >>> for analysis, if anyone wants to take a look? >>> - I could manually update pkgng and then portmaster -f all ports, but >>> this would take some time on the Pi. >>> - would a binary search through the revisions help here (I guess there >>> should be one where the r248706 init will not work) ? >>> >> 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)) René