Date: Thu, 23 Feb 2017 10:53:55 -0500 From: Thomas Laus <lausts@laus.org> To: freebsd-arm@freebsd.org Subject: Re: Fatal kernel abort Message-ID: <ed477caf-81ca-1b40-643e-02c75f651615@mail.laus.org> In-Reply-To: <1487735742.73144.138.camel@freebsd.org> References: <155401d28ba9$ccdc28c0$66947a40$@tndh.net> <CAFHCsPWm6fOh1phFfYF%2BjJO5mDV0=mNPd1EtHgDnrp=DBwHekw@mail.gmail.com> <157701d28bda$dd004700$9700d500$@tndh.net> <1487638318.73144.116.camel@freebsd.org> <159c01d28c18$bfbb90d0$3f32b270$@tndh.net> <1487692868.73144.118.camel@freebsd.org> <7d331926-08e2-9699-aaa9-538d40ee29dc@mail.laus.org> <1487711291.73144.131.camel@freebsd.org> <1487735742.73144.138.camel@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 02/21/17 22:55, Ian Lepore wrote: > > Yep, it turned out I caused this with my changes to support gpio pins > for card detect and write protect. The fdt data for beaglebone doesn't > list any pins for write protect and doesn't have the "wp-disable" > property (which is a bug in the fdt data, because eMMC and micro-sd > cannot be write protected). The old driver logic treated that as "not > protected" and a side effect of the way the new code works effectively > reversed that into saying everything is write protected. > > I just commited a fix for it as r314071, sorry for taking so long to > realize all of this was fallout from my change. > Everything works after building r314137. The ptrace_test.c fix was committed last night and I had a successful crochet-freebsd build this morning. My Beaglebone Black boots, looks and acts normally now. Thanks to all involved. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ed477caf-81ca-1b40-643e-02c75f651615>