Date: Fri, 2 May 2014 08:44:09 -0400 From: Winston Smith <smith.winston.101@gmail.com> To: FreeBSD ARM <freebsd-arm@freebsd.org> Subject: Re: BBB/11-CURRENT: Fatal kernel mode data abort: 'External Non-Linefetch Abort (S)' Message-ID: <CADH-AwHUzkYfZzowi=qmehVVdoPivLtNS4XMZBFs9AaAwR8oBA@mail.gmail.com> In-Reply-To: <CADH-AwHQqz22V-Vmibz3k=UCiWUWZE4aNqpD-PMpwAr5ptXyxw@mail.gmail.com>
index | next in thread | previous in thread | raw e-mail
On Fri, May 2, 2014 at 7:38 AM, Winston Smith <smith.winston.101@gmail.com> wrote: > Hmmm ... seem to be getting this when booting from SD using the 1Ghz > patched u-boot: > > musbotg0: <TI AM33xx integrated USB OTG controller> mem > 0x47400000-0x47400fff,0x47401000-0x474012ff,0x47401300-0x474013ff,0x47401400-0x474017ff,0x47401800-0x47401aff,0x47401b00-0x47401bff,0x47401c00-0x47401fff > irq 17,18,19 on simplebus0 > musbotg0: TI AM335X USBSS v0.0.13 When it boots via eMMC I see this right after "musbotg0: TI AM335X USBSS v0.0.13": ti_pruss0: <TI Programmable Realtime Unit Subsystem> mem 0x4a300000-0x4a37ffff irq 20,21,22,23,24,25,26,27 on simplebus0 ti_pruss0: AM33xx PRU-ICSS And I found this in the FreeBSD-arm mailing lists: http://freebsd.1045724.n5.nabble.com/External-Non-Linefetch-Abort-S-td5831937.html So maybe the patched u-boot isn't properly initializing this.help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CADH-AwHUzkYfZzowi=qmehVVdoPivLtNS4XMZBFs9AaAwR8oBA>