Re: crash in undefined handler [was Re: CURRENT broken on Raspberry Pi 2?]

["Herbert J. Skuhra" <herbert%gojira.at@localhost>]

On Sun, 17 Mar 2019 16:44:15 +0100, Herbert J. Skuhra wrote:
> 
> On Sun, 17 Mar 2019 13:46:00 +0100, Herbert J. Skuhra wrote:
> > 
> > On Sun, 17 Mar 2019 09:09:32 +0100, Nick Hudson wrote:
> > > 
> > > On 14/02/2019 19:26, Herbert J. Skuhra wrote:
> > > > On Sun, 10 Feb 2019 16:44:33 +0100, Nick Hudson wrote:
> > > >   
> > > >> RapsberryPI 2 is earmv7hf
> > > > 
> > > > The following happens when I boot an earmv7hf image on my Raspberry Pi 2:
> > > > 
> > > > Starting syslogd.
> > > > [  33.4972146] Fatal kernel mode prefetch abort at 0x00000000
> > > > [  33.5120546] trapframe: 0xba9cdef0, spsr=a0090013
> > > > [  33.5120546] r0 =5dde7d88, r1 =f2a00e00, r2 =ba9cdfb0, r3 =00000010
> > > > [  33.5228162] r4 =807dfd1c, r5 =00000000, r6 =ba9cdfb0, r7 =5dde7d88
> > > > [  33.5228162] r8 =00000010, r9 =f2a00e00, r10=baaa79a0, r11=ba9cdfac
> > > > [  33.5351457] r12=ba9cdf40, ssp=ba9cdf40, slr=80024114, pc =00000000
> > > > 
> > > > Stopped in pid 316.1 (syslogd) at       0:      address 0x0 is invalid
> > > > andeq   r0, r0, r0
> > > > db{0}> bt
> > > > 0xba9cdfac: netbsd:undefinedinstruction+0xc
> > > > db{0}> show mbuf
> > > > MBUF(0) 0x0
> > > > 
> > > > [  33.5351457] uvm_fault(0xbafbeca8, 0, 1) -> e
> > > > [  33.5351457] Fatal kernel mode data abort: 'Translation Fault (S)'
> > > > [  33.5351457] trapframe: 0xba9cd9f0
> > > > [  33.5351457] FSR=00000005, FAR=00000014, spsr=60090113
> > > > [  33.5351457] r0 =0000000c, r1 =f3201000, r2 =00000000, r3 =00000000
> > > > [  33.5351457] r4 =00000000, r5 =00000000, r6 =80374f5c, r7 =00000000
> > > > [  33.5351457] r8 =8060c10c, r9 =ba9cdef0, r10=ba9cda70, r11=ba9cdc9c
> > > > [  33.5351457] r12=ba9cd8e0, ssp=ba9cda40, slr=80374c98, pc =8039fa20
> > > > 
> > > > That's why I am running earmv6hf.
> > > > 
> > > > Jun@ posted a similiar issue with Orange Pi on Twitter:
> > > > 
> > > > <https://twitter.com/ebijun/status/1082589173721096192>
> > > > 
> > > 
> > > 
> > > Hopefully I fixed this now. Can you retest, please?
> > 
> > Thanks. Unfortunately current (earmv7hf) still panics on my RPI2B:
> > 
> > [   1.8821145] usb0 at dwctwo0: USB revision 2.0
> > [   2.0120904] panic: uspheucb0if aict dautsba0_s:e tNsetpeBcSiD f(i0c0
> >   [    2 2.0.0222029094242]] 0 0c)p uD1:WC 2Be groion tt rhuacbe b(a0c00k.0.),.
> >  [ [     2.2.02022029049242] ]c l0axs8s11 9d/70ed, cr:e v 2.00/1.00n,e tbasdddr: d1b_
> > [   2.032[0 9 4 02]. 0p3a2n0i9c40+]0 x1s4dh
> > [ [    2 2..00332020949040] ]c 00x:8 1c1mdd 7teifm4:e out error
> > [   2.0320940] netbsd:vpanic+0x194
> > [   2.0320940] 0x811d7f0c: netbsd:snprintf
> > [   2.0320940] 0x811d7f54: netbsd:specificdata_setspecific+0x204
> > [   2.0572506] 0x811d7fac: netbsd:linux_workqueue_thread+0x54
> > [   2.0572506] cpu1: End traceback...
> > Stopped in pid 0.47 (system) at netbsd:cpu_Debugger+0x4:        bx      r14
> 
> OK, my RPI2 mostly boots again if I
> 
> - disable makphy in RPI kernel config

No longer needed. It even works if makphy is enabled.

> - revert the following two commits:
> 
> ---
> Module Name:    src
> Committed By:   hannken
> Date:           Fri Mar  1 09:02:03 UTC 2019
> 
> Modified Files:
>         src/sys/kern: kern_exit.c kern_lwp.c vfs_trans.c
>         src/sys/sys: fstrans.h lwp.h
> ---
> Module Name:    src
> Committed By:   hannken
> Date:           Sat Mar  9 09:02:38 UTC 2019
> 
> Modified Files:
>         src/sys/rump/librump/rumpkern: emul.c lwproc.c
> ---
> 
> But only lwproc.c reverted to r1.40 to fix the build.
> 
> Sometimes the boot hangs at 
> 
> [   5.3218815] wsbell at spkr0 not configured

The boot process continues. It takes only 18 minutes until the login
prompt appears and another 90 seconds to login. :)

--
Herbert