Hello, Andy. (2012/10/21 11:07), Andy Ruhl wrote: > On Sat, Oct 20, 2012 at 3:39 PM, Andy Ruhl <acr...@gmail.com> wrote: >> uhub0 at usb0: Marvell EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 >> Fatal kernel mode prefetch abort at 0xfffffb44 >> trapframe: 0xc8a2bbf0, spsr=60000073 >> r0 =00000000, r1 =00000000, r2 =c8a32f3f, r3 =600000d3 >> r4 =c8a32f40, r5 =00000020, r6 =00b1cf40, r7 =c04787f4 >> r8 =00000000, r9 =c2347b0c, r10=00000012, r11=c8a2bc6c >> r12=00000000, ssp=c8a2bc44, slr=00114004, pc =fffffb44 >> >> Stopped in pid 0.5 (system) at fffffb44: address 0xfffffb44 is invalid >> andeq r0, r0, r10, lsr r0 >> db> bt >> netbsd:__aeabi_idiv+0x87768 >> scp=0xc03930d0 rlv=0x00000006 (6) >> rsp=0xc0486474 rfp=0x00000000 > > I tried to reboot it and got some more output: > > db> reboot > syncing disks... Mutex error: mutex_vector_enter: locking against myself > > lock address : 0x00000000c22cc090 type : spin > initialized : 0x00000000c011bc90 > shared holds : 0 exclusive: 0 > shares wanted: 0 exclusive: 0 > current cpu : 0 last held: 0 > current lwp : 0x00000000c2351540 last held: 000000000000000000 > last locked : 0x00000000c0130e68 unlocked*: 0x00000000c0131098 > owner field : 0x0000000000010600 wait/spin: 0/1 > > panic: LOCKDEBUG > Stopped in pid 0.5 (system) at netbsd:cpu_Debugger+0x4: bx r14 > db> > > I'm going to try a few things in the kernel config and see what happens. > > Andy >> Hope this helps. Should I open a PR? >> >> Andy
This problem was fixed by arm32/bus_space.c rev. 1.65 yesterday. And another bus_space.c's bug was fixed today by Nick. Could you try again? -- ----------------------------------------------- SAITOH Masanobu (msai...@execsw.org msai...@netbsd.org)