From owner-freebsd-arm@FreeBSD.ORG Wed Jul 30 17:43:37 2014 Return-Path: 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 C3CFF6A4; Wed, 30 Jul 2014 17:43:37 +0000 (UTC) Received: from mail-qg0-x232.google.com (mail-qg0-x232.google.com [IPv6:2607:f8b0:400d:c04::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 705DF2EBB; Wed, 30 Jul 2014 17:43:37 +0000 (UTC) Received: by mail-qg0-f50.google.com with SMTP id q108so2050186qgd.37 for ; Wed, 30 Jul 2014 10:43:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=MTDYLiCOSr7qTugZ5LAW66FnevIn3oLDPtJlfMh6N3Y=; b=fVQYXHJPHZeyQDVJiQaSOpgvdaxQQvW1zQJrkmLOgLvv235K8sszhPMek1n/dLyP02 gdvBB9OBlF1ZN8NGLL+qWu3IHW/O5CrIgHvS4VcN3JavMy+oBybvO3CIMJT4eeUyhFfS tMDHBIWIJFSK1msJAiPQBLd1zGbGMU8zZXpQ2/XXeYXaJgMMtyQa9i6etLuxgX+u40hj LyvnznOdVMB2gzXdK8ejwSlKFGIBXoeg6XtQ8AL1QHSfURWXVVdsgyG1SHfwM3dEBB6C DymgE3+n4HUIu2LgQS0glMJIlEf90y8i+0hWLp3W4+mvnep0YSElnbuzhpDJuJe+hwEC Zulg== X-Received: by 10.224.137.193 with SMTP id x1mr9722785qat.0.1406742215049; Wed, 30 Jul 2014 10:43:35 -0700 (PDT) Received: from pwnie.vrt.sourcefire.com (moist.vrt.sourcefire.com. [198.148.79.134]) by mx.google.com with ESMTPSA id t3sm5063533qak.18.2014.07.30.10.43.34 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 30 Jul 2014 10:43:34 -0700 (PDT) Date: Wed, 30 Jul 2014 13:43:32 -0400 From: Shawn Webb To: Ian Lepore Subject: Re: Kernel Panic on BeagleBone Black Message-ID: <20140730174332.GJ1869@pwnie.vrt.sourcefire.com> References: <20140730121922.GI1869@pwnie.vrt.sourcefire.com> <1406741430.56408.218.camel@revolution.hippie.lan> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ed/6oDxOLijJh8b0" Content-Disposition: inline In-Reply-To: <1406741430.56408.218.camel@revolution.hippie.lan> X-PGP-Key: http://pgp.mit.edu/pks/lookup?op=vindex&search=0x6A84658F52456EEE User-Agent: Mutt/1.5.23 (2014-03-12) Cc: freebsd-arm@freebsd.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Jul 2014 17:43:37 -0000 --ed/6oDxOLijJh8b0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Jul 30, 2014 11:30 AM -0600, Ian Lepore wrote: > On Wed, 2014-07-30 at 08:19 -0400, Shawn Webb wrote: > > Hey All, > >=20 > > I've just updated to a recent HEAD (r269240). I get a kernel panic > > almost immediately on boot. Below is the log. > >=20 > > =3D=3D=3D=3D Start of dump =3D=3D=3D=3D > > cpsw0: <3-port Switch Ethernet Subsystem> mem 0x4a100000-0x4a103fff irq= 40,41,42,43 on simplebus0 > > cpsw0: CPSW SS Version 1.12 (0) > > cpsw0: Initial queue size TX=3D128 RX=3D384 > > cpsw0: Ethernet address: 1c:ba:8c:e4:6d:6a > > cpsw0: Failed to read from PHY. > > cpsw0: attaching PHYs failed > >=20 > > vm_fault(0xc070b9e0, 0, 1, 0) -> 1 > > Fatal kernel mode data abort: 'Translation Fault (S)' > > trapframe: 0xc080eb28 > > FSR=3D00000005, FAR=3D00000018, spsr=3D80000193 > > r0 =3Dc266f280, r1 =3D00000000, r2 =3D00000019, r3 =3D60000193 > > r4 =3D00000000, r5 =3Dc266f280, r6 =3D00000006, r7 =3Dc05c99b4 > > r8 =3Dc266f280, r9 =3Dc26ca28c, r10=3Dc26c80c8, r11=3Dc080eb88 > > r12=3D00000000, ssp=3Dc080eb78, slr=3Dc05ee1cc, pc =3Dc03d2614 > >=20 > > [ thread pid 0 tid 100000 ] > > Stopped at device_delete_child+0x14: ldr r1, [r4, #0x018] > > db> bt > > Tracing pid 0 tid 100000 td 0xc070b6d0 > [...] > > Unable to unwind further > > =3D=3D=3D=3D End of dump =3D=3D=3D=3D > >=20 > > If there's anything I can do, let me know. > >=20 > > Thanks, > >=20 > > Shawn >=20 > Hmm, I can't reproduce this on my BB White at r269302. The real error > is "Failed to read from PHY". The kernel abort was just accidental > fallout from trying to clean up and detach the ethernet driver since it > failed to init properly (error paths never get tested enough). >=20 > What was the prior release you were on that worked okay? >=20 > Since I just made a series of changes to armv6 busdma I'm tempted to > suspect them, even though there shouldn't be any DMA involved in talking > to the PHY. Still, it would be interesting to know if backing off to > r269134 makes the problem go away. >=20 > -- Ian >=20 >=20 The release prior worked okay. I did get occasional kernel panics (though, I didn't have time to do a backtrace and post here about it). I'm unsure what svn rev the prior build was at. I can try reverting that revision you mentioned tonight and report back if you'd like. Thanks, Shawn --ed/6oDxOLijJh8b0 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBAgAGBQJT2S7EAAoJEGqEZY9SRW7u8gIQAMB1UlBgHB7rhBrkJEKRHfgr 1JIa5SEaAt9Ls58qJsVmCCCFz7JpnC30el0Gxi2GGhs/Z6/zCqZkY4H2K4asiUx6 Ud8EsQUTvfdO9eMCu34kzCnUtunQO++5hUGFrifjTvnwqUCtkI+031b5ELgo1vHc dbe6vyiPDzh+x0L/1ydzZ9CjwMfyy7pcnjvxzLkZLhgAxEEzdQhzahz7JATi8I+L ivs6jUwYO+1aMFI2pz8jcb0qfiY9qyAN8myB7p7rtVRf0Hrkkit4ohVYJYnmyBfD xqL78BsGQUN4qafdIykgDQuKVn21VO4aSi5SqTwXchoTprUWklxCqteJ96lb4bMz iFZGpasJJz0KFfaux7uCu4f5qKvyuPGa6G3Lb14pJ9yL6QRRbRgveD246uP7OSxg iScXNF9hdBz0zSpVowaZfeTtEOWlQgVs0s/lpES232W4G7Eq5MLQJp4wjIBwtN4d ZJcn/vEbNo+K3bymYnKpFJLBqOGPu/W/wAphO0fnhcs6lXEZuNiDq0WHJDLGQ3/O yyo8rvmRDp0IVurYx+EFmLrl0TMjmIf/oA2Y9sdFJrhjdhCy7lZC/imLzPYjeR4m Tt5juOfxwIJqy8+M3WSv65SF2Qeu4HvPfO36Zya4vq19l9Xcl/KQ6+Xoae4d5s7T ltM55qA1jhcL7Ep6kNwo =YpaN -----END PGP SIGNATURE----- --ed/6oDxOLijJh8b0--