Re: -current on OPENRD doesn't boot

[panu finnila <panu.finnila%iki.fi@localhost>]

Hi,

My ultimate version of the board has some booting problems with recent
version of NetBSD. NetBSD 6.99.11 usually boots fine. There is different
problem in every boot with same version of the kernel.

U-Boot 2012.04.01 (Jun 01 2012 - 02:22:48)
OpenRD-Ultimate
...
NetBSD 6.99.14 (OPENRD) #3: Sun Oct 21 11:23:56 EEST 2012
...
wd0 at atabus0 drive 0
wd0: <SAMSUNG HM250HI>
wd0: 232 GB, 484521 cyl, 16 head, 63 sec, 512 bytes/sect x 488397168
sectors

Non-emulated page fault with intr_depth > 0
Fatal kernel mode data abort: 'Translation Fault (S)'
trapframe: 0xcbf2abf0
FSR=00000005, FAR=e59ff118, spsr=60000053
r0 =00000000, r1 =00000000, r2 =cbf33f3f, r3 =e59ff114
r4 =cbf33f40, r5 =00000000, r6 =0157ff40, r7 =cbf33f3f
r8 =00000000, r9 =00000000, r10=600000d3, r11=cbf2ac6c
r12=00000000, ssp=cbf2ac44, slr=c09f547c, pc =c09f5490

Stopped in pid 0.2 (system) at  netbsd:pool_cache_get_slow+0x24:
ldr
...

wd0 at atabus0 drive 0
wd0: <SAMSUNG HM250HI>
wd0: 232 GB, 484521 cyl, 16 head, 63 sec, 512 bytes/sect x 488397168
sectors

Non-emulated page fault with intr_depth > 0
Fatal kernel mode data abort: 'Permission Fault (P)'
trapframe: 0xcbf2abf0
FSR=0000000f, FAR=00000000, spsr=60000053
r0 =00000000, r1 =00000000, r2 =cbf33f3f, r3 =600000d3
r4 =cbf33f40, r5 =00000020, r6 =0157ff40, r7 =c0c87724
r8 =00000000, r9 =c2a45a8c, r10=00000012, r11=cbf2ac6c
r12=00000000, ssp=cbf2ac44, slr=c0b9316c, pc =c0b93244

Stopped in pid 0.2 (system) at  netbsd:__aeabi_idiv+0x89e9c:    strheq
r0, [r0]
, -r7
...
wd0 at atabus0 drive 0
wd0: <SAMSUNG HM250HI>
wd0: 232 GB, 484521 cyl, 16 head, 63 sec, 512 bytes/sect x 488397168
sectors
Mutex error: mutex_vector_enter: locking against myself

lock address : 0x00000000c0c8f41c
current cpu  :                  0
current lwp  : 0x00000000c2a4f540
owner field  : 0x0000000000010700 wait/spin:                0/1

panic: lock error
Stopped in pid 0.5 (system) at  netbsd:cpu_Debugger+0x4:        bx
r14

-- 
-panu

On Mon, 2012-10-15 at 04:50 +0900, SAITOH Masanobu wrote:
> Hello, Sebastien.
> 
> (2012/10/14 5:56), Sébastien Bocahu wrote:
> > Hi,
> > 
> >>>>  My OPEN-RD with latest -current have not booted since 2 days ago.
> >>>
> >>> With SATA disk, it doesn't boot. Without SATA disk (i.e. NFS diskless),
> >>> it boots.
> >>>
> >>> Stack trace is:
> >>>
> >>>> root device (default mvgbe0): wd0
> >>>> dump device (default wd0b):
> >>>> file system (default ffs): ffs
> >>>> root on wd0a dumps on wd0b
> >>>> Mutex error: mutex_vector_enter: locking against myself
> >>>>
> >>>> lock address : 0x00000000c0c8efd8
> >>>> current cpu  :                  0
> >>>> current lwp  : 0x00000000c2a4fd20
> >>>> owner field  : 0x0000000001000700 wait/spin:                0/1
> >>>>
> >>>> panic: lock error
> >>>> Stopped in pid 0.2 (system) at  netbsd:cpu_Debugger+0x4:        bx      
> >>>> r14
> > 
> > Same issue here with an OpenRD-base. I tried both netbsd-6-0-RC2 and 
> > netbsd-6. 
> 
>  netbsd-6, too?
> 
>  My sata disk works fine with netbsd-6.
> 
> 
> > Have you been able to fix or gather more information ?
> 
>  No, I have not been able to fix it. After noticing that My SATA disk works
> with netbsd-6, I have been using my SheevaPlug for developing -current and
> using OPENRD for netbsd-6 to speed-up debugging.
> 
>  I'm very sorry that the priority to fix the sata problem is lower than
> other problem for me. I know evbarm has A LOT OF PROBLEMS and I have been
> trying to fix those problems.
> 
>  I think SATA problem appeared between September 12th and 15th.
> 
> 
> > Regards,
> > 
> > sebastien
> > 
> 
>