From owner-freebsd-arm@FreeBSD.ORG Mon Sep 10 03:16:17 2012 Return-Path: Delivered-To: freebsd-arm@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0D5191065670 for ; Mon, 10 Sep 2012 03:16:17 +0000 (UTC) (envelope-from kientzle@FreeBSD.org) Received: from monday.kientzle.com (99-115-135-74.uvs.sntcca.sbcglobal.net [99.115.135.74]) by mx1.freebsd.org (Postfix) with ESMTP id C1A508FC08 for ; Mon, 10 Sep 2012 03:16:16 +0000 (UTC) Received: (from root@localhost) by monday.kientzle.com (8.14.4/8.14.4) id q8A3G9Rw064864; Mon, 10 Sep 2012 03:16:09 GMT (envelope-from kientzle@FreeBSD.org) Received: from [192.168.2.143] (CiscoE3000 [192.168.1.65]) by kientzle.com with SMTP id ckf88fp4ve88gn5ckcpwajuhf2; Mon, 10 Sep 2012 03:16:08 +0000 (UTC) (envelope-from kientzle@FreeBSD.org) Mime-Version: 1.0 (Apple Message framework v1278) Content-Type: text/plain; charset=windows-1252 From: Tim Kientzle In-Reply-To: <20120910014813.GL58312@funkthat.com> Date: Sun, 9 Sep 2012 20:16:08 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <4448530B-7916-4642-BD32-6A96AD5DB22B@FreeBSD.org> References: <20120910014813.GL58312@funkthat.com> To: John-Mark Gurney X-Mailer: Apple Mail (2.1278) Cc: freebsd-arm@FreeBSD.org Subject: Re: -current on BeableBone successful X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Sep 2012 03:16:17 -0000 On Sep 9, 2012, at 6:48 PM, John-Mark Gurney wrote: > Well, I have successfully booted FreeBSD-current on the BeagleBone: > FreeBSD beaglebone 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r240251: Wed = Nov 2 14:26:08 PDT 2011 = jmg@pcbsd-779:/usr/obj/arm.armv6/usr/src.HEAD/sys/BEAGLEBONE arm >=20 > Though there are a few issues... I'm using Kientzle's script to build > the bootable image, so one is related to his script, and the others = are > more generic issues.. >=20 > The first off is that for some reason, the uenv.txt file doesn't = load.. > I'm not sure what is wrong, but if I type in: > fatload mmc 0:1 0x88000000 ubldr;bootelf 0x88000000 I just ran into this myself. I think the Arago sources broke environment loading. I started to debug the Arago U-Boot build this weekend but decided it would likely be more productive to switch to using the Denx sources. Denx publishes periodic snapshots which should make things a little more stable. > manually, it boots fine... >=20 > The second is that it looks like we have some left over debugging in > SIOC[SG]IFMEDIA that we need to remove, and a fall through comment = that > doesn't look like it is applicable any more... Should I just remove > these? The cpsw driver still needs work. I've fixed a couple of problems, but = there are some deeper issues: * Under memory pressure, the rx handler populates the receive buffer = list with NULLs then panics when it tries to process them. * I've seen the driver stall repeatedly; I'm not sure why yet but I = suspect the driver is mis-handling queue restarts. * The driver doesn't detach properly (which results in panics if you = build the driver as a module and try to unload it) > Third is that I get this error: > ip length 328 disagrees with bytes received 330. > accepting packet with data after udp payload. >=20 > This appeard to be from sbin/dhclient/packet.c... Not sure exactly = why > we are returning a large packet to userland=85 I haven't seen this one. > Thanks for the work. In a couple days, I'll figure out how well the > VLANs work on this system. >=20 > Thanks to Tim for his script that made building the image really easy, > and to the others for getting this working! Here are my priorities for the BeagleBone, in roughly this order: * Fix the cpsw Ethernet driver * Get buildworld/buildkernel working correctly natively. (30+ hour = builds make this tedious to test; last time I tested the builds = completed but installing world crashed things badly) * Work on performance for the MMC driver * USB host driver Apart from Ethernet-related panics, the system has been remarkably stable. I've been building ports and otherwise hammering the system for days on end without any apparent ill effects. Tim