From owner-freebsd-arm@freebsd.org Fri Aug 28 07:18:34 2015 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 953809C429B for ; Fri, 28 Aug 2015 07:18:34 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (mail.turbocat.net [IPv6:2a01:4f8:d16:4514::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 25C28F8B for ; Fri, 28 Aug 2015 07:18:34 +0000 (UTC) (envelope-from hps@selasky.org) Received: from laptop015.home.selasky.org (cm-176.74.213.204.customer.telag.net [176.74.213.204]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id C9C0C1FE023; Fri, 28 Aug 2015 09:18:31 +0200 (CEST) Subject: Re: Crash during buildworld on RPI2 To: bob prohaska , freebsd-arm@freebsd.org References: <20150828030743.GJ53136@www.zefox.net> From: Hans Petter Selasky Message-ID: <55E00B9E.8000505@selasky.org> Date: Fri, 28 Aug 2015 09:19:58 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.1.0 MIME-Version: 1.0 In-Reply-To: <20150828030743.GJ53136@www.zefox.net> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Aug 2015 07:18:34 -0000 On 08/28/15 05:07, bob prohaska wrote: > Here's a followup to the buildworld crash reported earlier today. > This time it was during installworld. > No debug output, and no backtrace. > > msc0: warning: Failed to write register 0x114 > smsc0: warning: Failed to read register 0x114 > smsc0: warning: MII read timeout > smsc0: warning: Failed to write register 0x114 > smsc0: warning: Failed to read register 0x114 > smsc0: warning: MII is busy > smsc0: warning: Failed to read register 0x114 > smsc0: warning: MII is busy > smsc0: warning: Failed to read register 0x114 > smsc0: warning: MII is busy > smsc0: warning: Failed to read register 0x118 > smsc0: warning: Failed to read register 0x114 > smsc0: warning: MII is busy > smsc0: warning: Failed to write register 0x114 > smsc0: warning: Failed to read register 0x114 > smsc0: warning: MII is busy > smsc0: warning: Failed to write register 0x114 > smsc0: warning: Failed to write register 0x114 > smsc0: warning: Failed to write register 0x114 > smsc0: warning: Failed to write register 0x114 > smsc0: warning: Failed to read register 0x114 > smsc0: warning: MII is busy > smsc0: warning: Failed to read register 0x114 > smsc0: warning: MII is busy > smsc0: warning: Failed to write register 0x114 > smsc0: warning: Failed to write register 0x114 Hi, It looks like some fast IRQ is spinning, preventing USB from running and possibly also bcm0. Is it possible you could check some things next time, like dumping the cc_cpu[] array? --HPS > sdhci_bcm0-slot0: Controller timeout > sdhci_bcm0-slot0: ============== REGISTER DUMP ============== > sdhci_bcm0-slot0: Sys addr: 0x01b90200 | Version: 0x00009902 > sdhci_bcm0-slot0: Blk size: 0x00000200 | Blk cnt: 0x00000008 > sdhci_bcm0-slot0: Argument: 0x00171440 | Trn mode: 0x0000193a > sdhci_bcm0-slot0: Present: 0x01ff0506 | Host ctl: 0x00000003 > sdhci_bcm0-slot0: Power: 0x0000000f | Blk gap: 0x00000000 > sdhci_bcm0-slot0: Wake-up: 0x00000000 | Clock: 0x00000307 > sdhci_bcm0-slot0: Timeout: 0x0000000e | Int stat: 0x00000010 > sdhci_bcm0-slot0: Int enab: 0x01ff00fb | Sig enab: 0x01ff00c9 > sdhci_bcm0-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000 > sdhci_bcm0-slot0: Caps: 0x00000000 | Max curr: 0x00000001 > sdhci_bcm0-slot0: =========================================== > mmcsd0: Error indicated: 1 Timeout > g_vfs_done():mmcsd0s2a[WRITE(offset=721911808, length=131072)]error = 5 > mmcsd0: Error indicated: 1 Timeout > g_vfs_done():mmcsd0s2a[WRITE(offset=722042880, length=131072)]error = 5 > mmcsd0: Error indicated: 1 Timeout > g_vfs_done():mmcsd0s2a[WRITE(offset=722173952, length=131072)]error = 5 > mmcsd0: Error indicated: 1 Timeout > g_vfs_done():mmcsd0s2a[WRITE(offset=722305024, length=131072)]error = 5 > mmcsd0: Error indicated: 1 Timeout > g_vfs_done():mmcsd0s2a[WRITE(offset=722436096, length=131072)]error = 5 > g_vfs_done():mmcsd0s2a[WRITE(offset=722567168, length=131072)]Fatal kernel mode data abort: 'Translation Fault (L1)' on read > error = 5 > trapframe: 0xd7738d08 > FSR=00000005, FAR=00000024, spsr=60000013 > r0 =00000000, r1 =c383d280, r2 =c3a0f720, r3 =c3a3f000 > r4 =00000000, r5 =c3a0f600, r6 =c3a3386c, r7 =c3a33840 > r8 =c078a1b0, r9 =c3a0f720, r10=c05c554c, r11=d7738dc0 > r12=00000000, ssp=d7738d98, slr=c056b614, pc =c056b64c > > There seems to be no debugger prompt, looks like it'll have to be power > cycled. > > hth, > > bob prohaska > > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" >