From owner-freebsd-arm@FreeBSD.ORG  Mon Dec 30 19:46:54 2013
Return-Path: <owner-freebsd-arm@FreeBSD.ORG>
Delivered-To: freebsd-arm@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id C9872A67;
 Mon, 30 Dec 2013 19:46:54 +0000 (UTC)
Received: from hal.g7iii.net (unknown [IPv6:2600:3c02::f03c:91ff:feae:1cbe])
 (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id A673C189A;
 Mon, 30 Dec 2013 19:46:54 +0000 (UTC)
Received: from [192.168.39.76] (157.17.187.81.in-addr.arpa [81.187.17.157])
 by hal.g7iii.net (Postfix) with ESMTP id 4F3C020A70;
 Mon, 30 Dec 2013 19:46:53 +0000 (UTC)
Message-ID: <52C1CDAC.2070002@g7iii.net>
Date: Mon, 30 Dec 2013 19:46:52 +0000
From: Iain Young <iain@g7iii.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:17.0) Gecko/20130623 Thunderbird/17.0.7
MIME-Version: 1.0
To: Ian Lepore <ian@FreeBSD.org>
Subject: Re: Boot failure for CURRENT on
References: <52C13E6B.4070006@g7iii.net>
 <1388419719.1158.192.camel@revolution.hippie.lan>
In-Reply-To: <1388419719.1158.192.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.17
Precedence: list
List-Id: "Porting FreeBSD to ARM processors." <freebsd-arm.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-arm>,
 <mailto:freebsd-arm-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arm/>
List-Post: <mailto:freebsd-arm@freebsd.org>
List-Help: <mailto:freebsd-arm-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arm>,
 <mailto:freebsd-arm-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Dec 2013 19:46:54 -0000

On 30/12/13 16:08, Ian Lepore wrote:

> Given that it appears to be dying in the dmtimer code I recently
> touched, I'd say my changes (r259739, 43, 44, 50) are a good candidate
> (except, of course, it works when I run it on my BBW).
>
> Do you have option PPS and do you have one of the timer trigger pins
> configured for capture?  On my BBW, the next line of output I'd see is:

Ah, that was the problem. I had assumed that your timer patch twiddled
with the dts, since your original patch did. That will teach me :)

However, although I now get further, it seems it can't find my SD card:


Trying to mount root from ufs:/dev/mmcsd0s2a [rw,noatime]...
mountroot: waiting for device /dev/mmcsd0s2a ...
usb_alloc_device: setting up USB template failed maybe the USB template 
module has not been loaded
ugen0.2: <Unknown> at usbus0 (disconnected)
uhub_reattach_port: could not allocate new device
Mounting from ufs:/dev/mmcsd0s2a failed with error 19.
Trying to mount root from ufs:mmcsd0s2 []...
mountroot: waiting for device mmcsd0s2 ...
Mounting from ufs:mmcsd0s2 failed with error 19.

Loader variables:
   vfs.root.mountfrom=ufs:/dev/mmcsd0s2a
   vfs.root.mountfrom.options=rw,noatime

Manual root filesystem specification:
   <fstype>:<device> [options]
       Mount <device> using filesystem <fstype>
       and with the specified (optional) option list.

     eg. ufs:/dev/da0s1a
         zfs:tank
         cd9660:/dev/acd0 ro
           (which is equivalent to: mount -t cd9660 -o ro /dev/acd0 /)

   ?               List valid disk boot devices
   .               Yield 1 second (for background tasks)
   <empty line>    Abort manual input

mountroot> ?

List of GEOM managed disk devices:


mountroot>


Did something change ? Is UFS now compiled as a module or something ?
I'm a bit concerned that "?" showed no managed disk devices. Any ideas ?


Iain