From owner-freebsd-arm@FreeBSD.ORG Fri Feb 15 23:50:46 2013 Return-Path: Delivered-To: freebsd-arm@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 112A5550 for ; Fri, 15 Feb 2013 23:50:46 +0000 (UTC) (envelope-from ian@FreeBSD.org) Received: from duck.symmetricom.us (duck.symmetricom.us [206.168.13.214]) by mx1.freebsd.org (Postfix) with ESMTP id 13284E46 for ; Fri, 15 Feb 2013 23:50:32 +0000 (UTC) Received: from damnhippie.dyndns.org (daffy.symmetricom.us [206.168.13.218]) by duck.symmetricom.us (8.14.6/8.14.6) with ESMTP id r1FNoWjq041894 for ; Fri, 15 Feb 2013 16:50:32 -0700 (MST) (envelope-from ian@FreeBSD.org) Received: from [172.22.42.240] (revolution.hippie.lan [172.22.42.240]) by damnhippie.dyndns.org (8.14.3/8.14.3) with ESMTP id r1FNoADj045693; Fri, 15 Feb 2013 16:50:10 -0700 (MST) (envelope-from ian@FreeBSD.org) Subject: Re: Beaglebone latest image observations - lock order reversal from ufs From: Ian Lepore To: Werner Thie In-Reply-To: <511EBB47.9030206@thieprojects.ch> References: <511EBB47.9030206@thieprojects.ch> Content-Type: text/plain; charset="us-ascii" Date: Fri, 15 Feb 2013 16:50:10 -0700 Message-ID: <1360972210.1164.4.camel@revolution.hippie.lan> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port 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: Fri, 15 Feb 2013 23:50:46 -0000 On Fri, 2013-02-15 at 23:48 +0100, Werner Thie wrote: > Hi > > today, after several failed attempts (build world failing), I managed > to build a new kernel with Tim's script for the Bone. > > From what I see it started spewing the 'ti_mmchs0: Error: current > cmd > null' again. > > ti_mmchs0: Error: current cmd NULL, already done? > > I'm now also getting the occasional > > lock order reversal: > 1st 0xc2c8ad84 ufs (ufs) @ /usr/local/src/sys/kern/vfs_subr.c:2176 > 2nd 0xc97a2378 bufwait (bufwait) @ > /usr/local/src/sys/ufs/ffs/ffs_vnops.c:261 > 3rd 0xc2d807f8 ufs (ufs) @ /usr/local/src/sys/kern/vfs_subr.c:2176 > KDB: stack backtrace: > : > : > Anybody out there being able to enlighten me about this? Does the > first > error relate or is triggered by second one? > This shouldn't be at all related to the "current cmd NULL" (that's a form of unexpected-interrupt error; it shouldn't be happening, but it should be fairly harmless). This LOR probably does need to be looked at more closely, though. > Seeping through dmesg I see > : > cpsw0: <3-port Switch Ethernet Subsystem> mem 0xcf619000-0xcf61cfff > irq > 40,41,42,43 on simplebus0 > cpsw0: CPSW SS Version 1.12 (0) > _bus_dmamap_sync: wrong user map: 0 4 This is most likely the same problem Thomas Skibo just submitted a fix for. If so, it's committed as r246859. -- Ian > cpsw0: Initial queue size TX=128 RX=384 > cpsw0: Ethernet address: 00:18:31:8e:0e:1d > : > > I also observed that Python27 built fresh from ports aborts on > importing > ctypes. > > I keep on building and reporting, the progress is still amazing! > > If there's anything specific to try, please let me know > > Thxs, Werner > >