Dockstar crash (a different one)

[Andy Ruhl <acruhl%gmail.com@localhost>]

Hello all,

After figuring out that populating /dev fixed the last crash I had, I
decided to get a new userland from nyftp (from Jan 5), and I synched
src and built a new kernel today (Jan 6).

A few problems:

1. It's behaving as if fstab doesn't exist or is incorrect, but I
think it isn't. So it goes into single user mode.

2. I get weird errors trying to mount /dev/sd0a on /

3. After a few tries of different things, it panics on one of my mount commands.

I attached the entire console output with VERBOSE_INIT_ARM

Here's what I did:

d0 at scsibus0 target 0 lun 0: <ST350064, 1A, H> disk fixed
sd0: 465 GB, 16383 cyl, 16 head, 63 sec, 512 bytes/sect x 976773168 sectors
cprng sysctl: WARNING insufficient entropy at creation.
boot device: <unknown>
root on sd0a dumps on sd0b
WARNING: clock lost 4755 days
WARNING: using filesystem time
WARNING: CHECK AND RESET THE DATE!
init: copying out path `/sbin/init' 11
Enter pathname of shell or RETURN for /bin/sh:
We recommend that you create a non-root account and use su(1) for root access.
# mount /dev/sd0a /
mount: cannot open `/d': No such file or directory
# ls -l /dev/sd0a
brw-r-----  1 root  operator  24, 0 Jan  6 13:52 /dev/sd0a
# cd /dev
# mount sd0a /
mount: cannot open `sd': No such file or directory
# mount ./sd0a /
mount_ffs:
uvm_fault(0xc25f2b98, 0, 1) -> e
Fatal kernel mode data abort: 'Translation Fault (P)'
trapframe: 0xc8adbdb0
FSR=00000017, FAR=0000000c, spsr=20000013
r0 =c2622c60, r1 =60000013, r2 =00000000, r3 =c22d3a80
r4 =c25e8008, r5 =c22bdb48, r6 =c25a6cd0, r7 =c2653800
r8 =bfffda18, r9 =00000000, r10=00010000, r11=c8adbe40
r12=00000000, ssp=c8adbe04, slr=c01bad4c, pc =c007d2b4

Stopped in pid 21.1 (mount_ffs) at      netbsd:ffs_mount+0xb4:  ldr     r12, [r2
, #0x00c]
db> bt
netbsd:ffs_mount+0x10
        pc =0xc007d210 rlv=0xc02e7ec8 (netbsd:VFS_MOUNT+0x18)
        rsp=0xc8adbe44 rfp=0xc8adbe50
        r10=0xc25e8008 r9=0x00000000
        r8=0xbfffda18 r7=0xbfffde1c r6=0x00000000 r5=0xc25a6cd0
        r4=0xc03c41f8
netbsd:VFS_MOUNT+0x18
        pc =0xc02e7ec8 rlv=0xc02eaadc (netbsd:do_sys_mount+0x3bc)
        rsp=0xc8adbe54 rfp=0xc8adbec0
netbsd:do_sys_mount+0x3bc
        pc =0xc02eaadc rlv=0xc02ead84 (netbsd:sys___mount50+0x3c)
        rsp=0xc8adbec4 rfp=0xc8adbef0
        r10=0xc03e8dbc r9=0x00000005
        r8=0xc25ed6d0 r7=0x0000019a r6=0x000091a4 r5=0x00010000
        r4=0xbfffde1c
netbsd:sys___mount50+0x3c
        pc =0xc02ead84 rlv=0xc0231108 (netbsd:syscall+0x84)
        rsp=0xc8adbef4 rfp=0xc8adbf80
        r6=0xc2653800 r5=0x00000000
        r4=0xc8adbfb0
netbsd:syscall+0x84
        pc =0xc0231108 rlv=0xc0231320 (netbsd:swi_handler+0x94)
        rsp=0xc8adbf84 rfp=0xc8adbfac
        r10=0x20030cbc r9=0x00000000
        r8=0x00000000 r7=0x00000001 r6=0xc03c32ec r5=0xc2653800
        r4=0xc8adbfb0
netbsd:swi_handler+0x94
        pc =0xc0231320 rlv=0xc005c088 (netbsd:swi_entry+0x28)
        rsp=0xc8adbfb0 rfp=0xbfffde34
        r8=0x00000000 r7=0x00000010
        r6=0x00000070 r5=0xbfffde1c r4=0xc03c32ec
db>

I booted this same kernel with an older userland (at least 6 months
older). It boots fine and I haven't been able to get it to panic.

Any help would be appreciated.

Andy

Attachment: screenlog.0.dockstar_crash_jan6
Description: Binary data