From owner-freebsd-arm@FreeBSD.ORG Thu Aug 1 12:32:48 2013 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 99EE1EC; Thu, 1 Aug 2013 12:32:48 +0000 (UTC) (envelope-from mattia.rossi.mate@gmail.com) Received: from mail-bk0-x22c.google.com (mail-bk0-x22c.google.com [IPv6:2a00:1450:4008:c01::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id ED1362F17; Thu, 1 Aug 2013 12:32:47 +0000 (UTC) Received: by mail-bk0-f44.google.com with SMTP id mz10so660691bkb.31 for ; Thu, 01 Aug 2013 05:32:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=36wOea+Z005uiuSYLT8pnXKl97132iUC7iDcWJqdp2Y=; b=hw+1toryFBvZ/SMgvfSP5i5fHKtdf/2beUYfzSY/KAme4eu4Gqn4NCWJntlT3FDR9L NmFfzWjNOogzwFXmvozv3Qc84NwEm1BBfvWaYNVQhIWtppvRF+SFj3TAxPeyyx/ApM3H RgSy002v4sw3dG7A+Y0Qd4SC2YeN4xwjGVpzT1sclLWRWCdA4L4kQzZpNMflz88zyyRn kMvptzYuEIZrz0e9GI8/fTM5ixiFYgi3Y3qhmjSyzjeC5F7wYbQ2vkVTQ6QHEeajcwsn sG/5v5E/5zCw3ZJYmUH3l/KiqE363vTjf2vWHVxwrJzZ2+y4fzpxEcIlFbjzUYoywdep /PfQ== X-Received: by 10.205.36.194 with SMTP id tb2mr340109bkb.174.1375360366106; Thu, 01 Aug 2013 05:32:46 -0700 (PDT) Received: from [10.185.11.70] ([46.189.28.44]) by mx.google.com with ESMTPSA id m6sm650904bki.7.2013.08.01.05.32.44 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 01 Aug 2013 05:32:45 -0700 (PDT) Message-ID: <51FA1D2B.9090009@gmail.com> Date: Thu, 01 Aug 2013 10:32:43 +0200 From: Mattia Rossi User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7 MIME-Version: 1.0 To: Ian Lepore Subject: Re: Kernel Panic on DREAMPLUG: Alignment Fault 1 References: <51F92F79.9010809@gmail.com> <1375309907.45247.185.camel@revolution.hippie.lan> <51F9C81A.7000106@gmail.com> <1375358623.45247.189.camel@revolution.hippie.lan> In-Reply-To: <1375358623.45247.189.camel@revolution.hippie.lan> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-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: Thu, 01 Aug 2013 12:32:48 -0000 On 01/08/13 14:03, Ian Lepore wrote: > On Thu, 2013-08-01 at 04:29 +0200, Mattia Rossi wrote: >> On 01/08/13 00:31, Ian Lepore wrote: >>> On Wed, 2013-07-31 at 17:38 +0200, Mattia Rossi wrote: >>>> Hi all, >>>> >>>> this might be related to the WLI-UC-GNM Alignment Fault, but definitely >>>> has nothing to do with Wireless LAN. >>>> It rather seems that there's a problem with the USB subsystem. >>>> >>>> See dmesg an backtrace below. >>>> [snip] >>>> >>>> Currently trying to find where the issue could be. >>>> >>>> Mat >>> This is a strange abort, and if it's usb-related that's only accidental >>> I think. It says it's an alignment fault, but the fault address reg has >>> a 32-bit aligned value in it. That makes me think it must be an >>> ldrd/strd instruction (requires 64-bit alignment) that's faulting. >>> >>> Is this compiled with clang? I think it emits such instructions and gcc >>> doesn't. Except I don't think clang should use those instructions on >>> armv5, because of the alignment requirements. >>> >>> -- Ian >> Hi Ian, >> >> sorry, forgot to add that contrary to the WLI-UC-GNM problem, I'm still >> compiling using gcc on FreeBSD 9.1 >> >> The abort is completely reproducible each time at the same place... >> I've tried to recompile the kernel a few times, also changing the root >> device, but it gets stuck there and aborts.. >> >> I actually have no clue on what's going on here. Any hints on how to get >> more information about this? >> >> Cheers, >> >> Mat > Actually, it looks like you're using clang (I keep forgetting this comes > out in dmesg now): > >>> FreeBSD 10.0-CURRENT #9 r253846M: Wed Jul 31 17:24:31 CEST 2013 >>> root@freebsd9.1-base:/usr/obj/arm.arm/usr/devel/dreamplug/sys/DREAMPLUG-100m >>> FreeBSD clang version 3.3 (tags/RELEASE_33/final 183502) 20130610 > Is the 'M' in r253846M anything significant? > > I haven't built for dreamplug in a long time (I haven't done much of > anything with computers for several months). I'll get a build going and > see if I get the same kind of problems. > > -- Ian > Gee... I guess I'm using CLANG then... So, this messes a bit with my understanding of the relation of host and guest... I always thought, that the host system decides which compiler gets used for cross-compiling, and not the guest (which means the source tree) So If my default compiler is gcc on the host, everything should be compiled with gcc. Given that I haven't changed anything of that, how comes that the kernel is compiled using clang? Especially given that the clang version on the host will not be a very up-to-date version? Or does clang get built during the make process, and then used as the compiler? Anyhow, I'll try to compile with gcc, and see what happens. Cheers, Mat