Date: Wed, 30 Jul 2014 13:43:32 -0400 From: Shawn Webb <lattera@gmail.com> To: Ian Lepore <ian@FreeBSD.org> Cc: freebsd-arm@freebsd.org Subject: Re: Kernel Panic on BeagleBone Black Message-ID: <20140730174332.GJ1869@pwnie.vrt.sourcefire.com> In-Reply-To: <1406741430.56408.218.camel@revolution.hippie.lan> References: <20140730121922.GI1869@pwnie.vrt.sourcefire.com> <1406741430.56408.218.camel@revolution.hippie.lan>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] 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, > > > > I've just updated to a recent HEAD (r269240). I get a kernel panic > > almost immediately on boot. Below is the log. > > > > ==== Start of dump ==== > > 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=128 RX=384 > > cpsw0: Ethernet address: 1c:ba:8c:e4:6d:6a > > cpsw0: Failed to read from PHY. > > cpsw0: attaching PHYs failed > > > > vm_fault(0xc070b9e0, 0, 1, 0) -> 1 > > Fatal kernel mode data abort: 'Translation Fault (S)' > > trapframe: 0xc080eb28 > > FSR=00000005, FAR=00000018, spsr=80000193 > > r0 =c266f280, r1 =00000000, r2 =00000019, r3 =60000193 > > r4 =00000000, r5 =c266f280, r6 =00000006, r7 =c05c99b4 > > r8 =c266f280, r9 =c26ca28c, r10=c26c80c8, r11=c080eb88 > > r12=00000000, ssp=c080eb78, slr=c05ee1cc, pc =c03d2614 > > > > [ 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 > > ==== End of dump ==== > > > > If there's anything I can do, let me know. > > > > Thanks, > > > > Shawn > > 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). > > What was the prior release you were on that worked okay? > > 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. > > -- Ian > > 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 [-- Attachment #2 --] -----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-----help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140730174332.GJ1869>