Re: Status of current on ARM?

To: port-arm%netbsd.org@localhost, current-users%netbsd.org@localhost, tech-kern%netbsd.org@localhost
Subject: Re: Status of current on ARM?
From: Mikko Rapeli <mikko.rapeli%teleca.com@localhost>
Date: Mon, 3 Nov 2008 11:19:39 +0200
Thanks, all, for your input. Since some ARM platforms work with current, I'm
presuming only OMAP is broken.

On Fri, Oct 31, 2008 at 09:19:44AM -0700, Matt Thomas wrote:
> On Oct 31, 2008, at 5:52 AM, Mikko Rapeli wrote:
> 
> >What is the general status of netbsd-current on ARM?
> >
> >evbarm on OMAP 2420 has been broken since August 6th. Imre Deak  
> >brought
> >up the issues on port-arm, and later a pr was failed
> >http://www.netbsd.org/cgi-bin/query-pr-single.pl?number=39791 .
> >An obvious workaround on OMAP 2420 is to undo a few changes, attached
> >patches, but I'm willing to test if anyone has better fixes around.
> 
> It works for me.  I booted a 2420 less than a week ago.

Not for me. Which 2420 are you working with? We are using TI's OMAP 2420
SDP evaluation boards. And which kernel config? I'm using the standard
TISDP2420 with changes to static IP addresses, root NFS paths and rootfs
location (sm0, type nfs) and serial port set to 115k bauds.

> >I would like to test and the post some thumb mode fixes to the kernel
> >which are working with OMAP 2420 on a branch from current, taken  
> >August
> >5th. But the failing kernel from current is blocking that work.
> 
> I see no reason since -current is working.  Are you sure your source  
> tree
> is clean?

We use git for managing the netbsd sources, and the current cvs tree gets 
updated to the git tree daily. There have not been any known issues with this
interworking. But to be sure I checked out sources from cvs on Friday,
updated them to latest again this morning, and compiled both kernel and
userspace to be sure there aren't any issues with new kernel and older
userspace. 

The result is a kernel panic in the pmap code, as described in pr #39791
and to which workaround are the two revert patches in my previous
mail. Boot log and backtrace can be found below.

If I were managing a tree, I would revert patches that have issues on
some hardware, and would work to get those issues fixed. I'm willing to test
any alternatives there are, but at the moment current on OMAP 2420 is
broken, and workaround patches have been proposed.

-Mikko

U-Boot 1.1.3 (Sep 10 2007 - 11:20:13)

U-Boot code: 80E80000 -> 80E9DBFC  BSS: -> 80EA29C8
OMAP2420-GP revision 3, PRCM III
TI H4 SDP Base Board + Menelaus Daughter Board + mDDR
RAM Configuration:
Bank #0: 80000000 32 MB
Bank #1: 82000000 32 MB
Flash: 64 MB
In:    serial
Out:   serial
Err:   serial
Hit any key to stop autoboot:  0
Using MAC Address 00:50:C2:42:B0:34
TFTP from server 192.168.10.1; our IP address is 192.168.10.4
Filename 'netbsd'.
Load address: 0x80300000
Loading: #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         ##########################################################
done
Bytes transferred = 2292596 (22fb74 hex)
## Starting application at 0x80300000 ...
dfgh
NetBSD/evbarm (SDP24xx) booting ...
initarm: Configuring system ...
Allocating page tables
setup_real_page_tables: physical_freestart 0x80565000
setup_real_page_tables: kernel_l1pt: 0x80568000:0x80568000
setup_real_page_tables: kernel_pt_table:
        0x80565000:0x80565000
        0x80566000:0x80566000
        0x80567000:0x80567000
        0x8056c000:0x8056c000
        0x8056d000:0x8056d000
        0x8056e000:0x8056e000
        0x8056f000:0x8056f000
        0x80570000:0x80570000
        0x80571000:0x80571000
Creating L1 page table at 0x80568000
Mapping kernel
pmap_map_chunk: pa=0x80300000 va=0x80300000 size=0x1e0000 resid=0x1e0000 prot=01
SLLLLLLLLLLLLLL
pmap_map_chunk: pa=0x804e0000 va=0x804e0000 size=0x90000 resid=0x90000 prot=0x31
LLLLLLLLL
Constructing L2 page tables
pmap_map_chunk: pa=0x80573000 va=0x80573000 size=0x1000 resid=0x1000 prot=0x3 c1
P
pmap_map_chunk: pa=0x80574000 va=0x80574000 size=0x1000 resid=0x1000 prot=0x3 c1
P
pmap_map_chunk: pa=0x80575000 va=0x80575000 size=0x1000 resid=0x1000 prot=0x3 c1
P
pmap_map_chunk: pa=0x80576000 va=0x80576000 size=0x1000 resid=0x1000 prot=0x3 c1
P
pmap_map_chunk: pa=0x80577000 va=0x80577000 size=0x2000 resid=0x2000 prot=0x3 c1
PP
pmap_map_chunk: pa=0x80568000 va=0x80568000 size=0x4000 resid=0x4000 prot=0x3 c2
PPPP
pmap_map_chunk: pa=0x80565000 va=0x80565000 size=0x1000 resid=0x1000 prot=0x3 c2
P
pmap_map_chunk: pa=0x80566000 va=0x80566000 size=0x1000 resid=0x1000 prot=0x3 c2
P
pmap_map_chunk: pa=0x80567000 va=0x80567000 size=0x1000 resid=0x1000 prot=0x3 c2
P
pmap_map_chunk: pa=0x8056c000 va=0x8056c000 size=0x1000 resid=0x1000 prot=0x3 c2
P
pmap_map_chunk: pa=0x8056d000 va=0x8056d000 size=0x1000 resid=0x1000 prot=0x3 c2
P
pmap_map_chunk: pa=0x8056e000 va=0x8056e000 size=0x1000 resid=0x1000 prot=0x3 c2
P
pmap_map_chunk: pa=0x8056f000 va=0x8056f000 size=0x1000 resid=0x1000 prot=0x3 c2
P
pmap_map_chunk: pa=0x80570000 va=0x80570000 size=0x1000 resid=0x1000 prot=0x3 c2
P
pmap_map_chunk: pa=0x80571000 va=0x80571000 size=0x1000 resid=0x1000 prot=0x3 c2
P
devmap: 48000000 -> 480fffff @ 8d000000
pmap_map_chunk: pa=0x48000000 va=0x8d000000 size=0x100000 resid=0x100000 prot=00
S
devmap: 49000000 -> 490fffff @ 8e000000
pmap_map_chunk: pa=0x49000000 va=0x8e000000 size=0x100000 resid=0x100000 prot=00
S
                             Physical              Virtual        Num
                       Starting    Ending    Starting    Ending   Pages
               SDRAM: 0x80300000 0x83ffffff 0x80300000 0x83ffffff 15616
        text section: 0x80300000 0x804d05bb 0x80300000 0x804d05bb 480
        data section: 0x804e0000 0x8052fb74 0x804e0000 0x8052fb74 80
         bss section: 0x8052fb74 0x805647f4 0x8052fb74 0x805647f4 54
   L1 page directory: 0x80568000 0x8056bfff 0x80568000 0x8056bfff 4
   Exception Vectors: 0x80572000 0x80572fff 0xffff0000 0xffff0fff 1
           FIQ stack: 0x80573000 0x80573fff 0x80573000 0x80573fff 1
           IRQ stack: 0x80574000 0x80574fff 0x80574000 0x80574fff 1
           ABT stack: 0x80575000 0x80575fff 0x80575000 0x80575fff 1
           UND stack: 0x80576000 0x80576fff 0x80576000 0x80576fff 1
           SVC stack: 0x80577000 0x80578fff 0x80577000 0x80578fff 2
      Message Buffer: 0x80579000 0x80579fff                       1
         Free Memory: 0x8057a000 0x83ffffff 0x8057a000 0x83ffffff 14982
switching to new L1 page table  @0x80568000...OK.
bootstrap done.
init subsystems: stacks vectors undefined page pmap done.
initarm done.
Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005,
    2006, 2007, 2008
    The NetBSD Foundation, Inc.  All rights reserved.
Copyright (c) 1982, 1986, 1989, 1991, 1993
    The Regents of the University of California.  All rights reserved.

NetBSD 5.99.01 (TISDP2420) #0: Mon Nov  3 08:39:28 EET 2008
        mira@fitfioullt278:/home/mira/src/netbsd/netbsd-cvs/obj/sys/arch/evbarm0
total memory = 62464 KB
avail memory = 58104 KB
mainbus0 (root)
cpu0 at mainbus0: ARM1136J-S r0p2 (ARM11J core)
cpu0: DC enabled IC enabled WB enabled LABT
cpu0: 32KB/32B 4-way Instruction cache
cpu0: 32KB/32B 4-way write-back-locking-C Data cache
obio0 at mainbus0 base 0x48000000-0x48ffffff: On-Board IO
omapicu0 at obio0 addr 0x480fe000-0x480fefff intrbase 0
omapgpio0 at obio0 addr 0x48018000-0x480183ff intr 29 intrbase 96: interrupts 99
omapgpio1 at obio0 addr 0x4801a000-0x4801a3ff intr 30 intrbase 128: interrupts 0
omapgpio2 at obio0 addr 0x4801c000-0x4801c3ff intr 31 intrbase 160: interrupts 1
com0 at obio0 addr 0x4806a000-0x4806a3ff: ns16550a, working fifo
com0: console
omapgpio3 at obio0 addr 0x4801e000-0x4801e3ff intr 32 intrbase 192: interrupts 2
omapmputmr0 at obio0 addr 0x4802a000-0x4802a0ff intr 38: OMAP MPU Timer #2
omapmputmr1 at obio0 addr 0x48078000-0x480780ff intr 39: OMAP MPU Timer #3
omapmputmr2 at obio0 addr 0x4807a000-0x4807a0ff intr 40: OMAP MPU Timer #4
omapwdt32k0 at obio0 addr 0x48026000-0x480267ff: rev 1.1
obio1 at mainbus0 base 0x49000000-0x497fffff: On-Board IO
L3i0 at mainbus0: L3i Interconnect
gpmc0 at mainbus0 base 0x6800a000: General Purpose Memory Controller, rev 2.0
gpmc0: CS#0 valid, addr 0x04000000, size  64MB
gpmc0: CS#1 valid, addr 0x08000000, size  16MB
sm0 at gpmc0 addr 0x08000300 intr 188
sm0: SMC91C94/91C96, revision 9, buffer size: 6144
sm0: MAC address 00:50:c2:42:b0:34, default media UTP
clock: hz=100 stathz=64
gpio0 at omapgpio0: 32 pins
gpio1 at omapgpio1: 32 pins
gpio2 at omapgpio2: 32 pins
gpio3 at omapgpio3: 32 pins
boot device: <unknown>
root on sm0
nfs_boot: trying static
nfs_boot: client_addr=192.168.10.4
nfs_boot: gateway=192.168.10.1
nfs_boot: netmask=255.255.255.0
nfs_boot: server=192.168.10.1
nfs_boot: root=192.168.10.1:/home/mira/rootfs
root on 192.168.10.1:/home/mira/rootfs
WARNING: no TOD clock present
WARNING: using filesystem time
WARNING: CHECK AND RESET THE DATE!
warning: no /dev/console

uvm_fault(0x81cbddd0, 0, 1) -> e
Fatal kernel mode data abort: 'Translation Fault (P)'
trapframe: 0x82958ccc
FSR=00000007, FAR=00000040, spsr=60000013
r0 =8056a040, r1 =8056e1f1, r2 =8056e1f1, r3 =00000a01
r4 =80562dcc, r5 =00000000, r6 =00000552, r7 =00000000
r8 =8055f14c, r9 =80563080, r10=00000000, r11=82958d64
r12=00000000, ssp=82958d18, slr=00002040, pc =80488cc0

Stopped in pid 2.1 (sh) at      netbsd:pmap_enter+0x328:        ldr     r2, [r12
, #0x040]
db> bt
netbsd:pmap_enter+0xc
        scp=0x804889a4 rlv=0x80484174 (netbsd:mmrw+0x1c0)
        rsp=0x82958d68 rfp=0x82958da4
        r10=0x82958e94 r9=0x00000000
        r8=0x00000000 r7=0x8055f14c r6=0x00000000 r5=0x00000000
        r4=0x81004000
netbsd:mmrw+0x18
        scp=0x80483fcc rlv=0x8040d6a8 (netbsd:cdev_write+0x3c)
        rsp=0x82958da8 rfp=0x82958dc0
        r10=0x8296bf50 r9=0x82958e94
        r8=0x2020f400 r7=0x0000002d r6=0x00000000 r5=0x00000010
        r4=0x82958e94
netbsd:cdev_write+0xc
        scp=0x8040d678 rlv=0x80468d34 (netbsd:spec_write+0x98)
        rsp=0x82958dc4 rfp=0x82958e20
        r6=0x829710bc r5=0x8296dc40
        r4=0x82958e40
netbsd:spec_write+0x10
        scp=0x80468cac rlv=0x8035ceb0 (netbsd:tmpfs_spec_write+0x64)
        rsp=0x82958e24 rfp=0x82958e38
        r10=0x8296bf50 r9=0x804e2508
        r8=0x2020f400 r7=0x0000002d r6=0x82958e94 r5=0x82958e40
        r4=0x829710bc
netbsd:tmpfs_spec_write+0x10
        scp=0x8035ce5c rlv=0x804620d8 (netbsd:VOP_WRITE+0x38)
        rsp=0x82958e3c rfp=0x82958e60
        r5=0x829710bc r4=0x00000010
netbsd:VOP_WRITE+0xc
        scp=0x804620ac rlv=0x8045bdf8 (netbsd:vn_write+0xb0)
        rsp=0x82958e64 rfp=0x82958e88
netbsd:vn_write+0xc
        scp=0x8045bd54 rlv=0x8041e950 (netbsd:dofilewrite+0x84)
        rsp=0x82958e8c rfp=0x82958edc
        r10=0x8052ee84 r8=0x2020f400
        r7=0x00000001 r6=0x82958f64 r5=0x0000002d r4=0x00000001
netbsd:dofilewrite+0xc
        scp=0x8041e8d8 rlv=0x8041ea84 (netbsd:sys_write+0x74)
        rsp=0x82958ee0 rfp=0x82958f04
        r10=0x81cb8b28 r8=0x82958fb8
        r7=0x82958fb4 r6=0x82958f64 r5=0x82958fb8 r4=0x00000001
netbsd:sys_write+0xc
        scp=0x8041ea1c rlv=0x8047fc3c (netbsd:syscall+0x9c)
        rsp=0x82958f08 rfp=0x82958f94
        r6=0x00000003 r5=0x00000004
        r4=0x82958fb4
netbsd:syscall+0x10
        scp=0x8047fbb0 rlv=0x8047fea8 (netbsd:swi_handler+0xa8)
        rsp=0x82958f98 rfp=0x82958fb0
        r10=0x00000000 r9=0x00030490
        r8=0x0000002d r7=0x00000000 r6=0xefa00004 r5=0x8296dc40
        r4=0x82958fb4
netbsd:swi_handler+0x10
        scp=0x8047fe10 rlv=0x80482dc0 (netbsd:swi_entry+0x2c)
        rsp=0x82958fb4 rfp=0x7fffe724
        r6=0x00000001 r5=0x2020f400
        r4=0x8052ee84
db>
Follow-Ups:
- Re: Status of current on ARM?
  - From: Matt Thomas
References:
- Status of current on ARM?
  - From: Mikko Rapeli
- Re: Status of current on ARM?
  - From: Robert Swindells
- Re: Status of current on ARM?
  - From: Matt Thomas
Prev by Date: Re: EP9307?
Next by Date: Re: Status of current on ARM?
Previous by Thread: Re: Status of current on ARM?
Next by Thread: Re: Status of current on ARM?
Indexes:
Home | Main Index | Thread Index | Old Index