Port-arm archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Panic on Seagate Dockstar at boot using recent -current

Hello all,

I built a kernel from sources synced a few hours ago for my dockstar.
I decided to try both the new conf file for SHEEVAPLUG as well as the
one I've been using before, and they both panic right when the kernel
starts init. I had to plug in my serial cable to find out. The last
kernel I built that was working was from July 22nd and I would have
synced src just before building it.

Here's what happened with bt output:

scsibus0 at umass0: 2 targets, 1 lun per target
sd0 at scsibus0 target 0 lun 0: <ST350064, 1A, 3.AA> disk fixed
sd0: fabricating a geometry
sd0: 465 GB, 476940 cyl, 64 head, 32 sec, 512 bytes/sect x 976773168 sectors
boot device: <unknown>
root on sd0a dumps on sd0b
sd0: fabricating a geometry
WARNING: clock lost 4276 days
WARNING: using filesystem time
warning: no /dev/console
panic: init died (signal 0, exit 11)
Stopped in pid 1.1 (init) at    netbsd:cpu_Debugger+0x4:        bx      r14
db> bt
        scp=0xc022c430 rlv=0xc012e1a4 (netbsd:exit1+0x720)
        rsp=0xc2c41e94 rfp=0xc2c41ee0
        scp=0xc012da94 rlv=0xc012e298 (netbsd:sys_exit+0x3c)
        rsp=0xc2c41ee4 rfp=0xc2c41efc
        scp=0xc012e26c rlv=0xc023f3ac (netbsd:syscall+0x8c)
        rsp=0xc2c41f00 rfp=0xc2c41f8c
        r6=0x00000001 r5=0x00000001
        scp=0xc023f330 rlv=0xc023f5fc (netbsd:swi_handler+0xb0)
        rsp=0xc2c41f90 rfp=0xc2c41fb0
        r10=0x00014658 r9=0x00000000
        r8=0xc03a2660 r7=0xefa00001 r6=0xc1dfbaa0 r5=0xc2c41fb4
        scp=0xc023f55c rlv=0xc0059104 (netbsd:swi_entry+0x2c)
        rsp=0xc2c41fb4 rfp=0xbfffef2c
        r8=0x00000000 r7=0xbfffef5c
        r6=0x00000001 r5=0x00000000 r4=0xc03a2660

I can't get it to dump the panic to the dump device for whatever
reason. This is what it says:

db> sync
syncing disks... done

dumping to dev 24,1 offset 786431
dump i/o error

I'm going to work on this a bit to see if I can figure out what
happened. I'm not really smart enough to be doing this, so if anyone
can tell right away what happened, that would be great. I'll start
digging to try to see what recent changes might have caused an issue.
But I'll need help.


Home | Main Index | Thread Index | Old Index