[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference turris::digital_unix

Title:DIGITAL UNIX(FORMERLY KNOWN AS DEC OSF/1)
Notice:Welcome to the Digital UNIX Conference
Moderator:SMURF::DENHAM
Created:Thu Mar 16 1995
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:10068
Total number of notes:35879

9851.0. "Is crashdc possible without vmunix file?" by MARVIN::GOUGH (Raoul Gough) Fri May 16 1997 09:13

Our V4.0 system crashed last night, but there is only a "vmcore.0" dump file.
No vmunix.0 so crashdc won't run.

Actually, I guess this is my fault because I tried to move the crash dumps to
a new directory but forgot to copy the "bounds" file (oops).  Looks like
savecore overwrote the old vmcore.0 file but not vmunix.0.  What I did then was
try crashdc with only the new vmcore.0 file (and it didn't try to run).  Then
I tried it with the new vmcore.0 and the old vmunix.0, which did run but
there's a lot of errors in the crash-data.0 output file.

Is there any way to get a crash data report for this?  I know that it was
a crash I've seen before, but it would be good to have the relevant crash
images.

Any help appreciated.

Regards,
Ray.

T.RTitleUserPersonal
Name
DateLines
9851.1use /vmunixRHETT::MOOREFri May 16 1997 09:188
    Assuming you haven't changed the kernel since the crash, try running
    it against the existing kernel:
    
    # cd /var/adm/crash
    # crashdc /vmunix vmcore.0 > crash-data.0
    
    Martin Moore
    Digital UNIX Support Group
9851.2No luckMARVIN::GOUGHRaoul GoughTue May 27 1997 07:47206
Hmmm.

I gave it a try with the current /vmunix kernel, with the same errors in
the crashdc output.  Actually I haven't changed the kernel for a long time, so
all of the vmunix.* files are the same.  I didn't click that they were just
copies of the /vmunix that was running at the time of the crash.

Now that I look at it, the vmcore.* file isn't quite as big as the other
ones, so the dump musn't have completed:

-rw-rw-r--   1 root     system   805298176 May 21 19:10 vmcore.2
-rw-rw-r--   1 root     system   805298176 May 21 19:13 vmcore.3
-rw-rw-r--   1 root     system   805298176 May 21 19:17 vmcore.5
-rw-rw-r--   1 root     system   801300480 May 21 19:20 vmcore.6

I've appended some crashdc output at the end :-)

>    Assuming you haven't changed the kernel since the crash, try running
>    it against the existing kernel:
>    
>    # cd /var/adm/crash
>    # crashdc /vmunix vmcore.0 > crash-data.0
>
>    Martin Moore
>    Digital UNIX Support Group

Ray.

------------------------------------------------------------------------------

#
# Crash Data Collection (Version 1.4)
#
_crash_data_collection_time: Tue May 27 11:37:55 BST 1997
_current_directory: /var/adm/crash
_crash_kernel: /vmunix
_crash_core: vmcore.6
_crash_arch: alpha
_crash_os: Digital UNIX
_host_version: Digital UNIX V4.0 (Rev. 386); Tue Oct 29 16:56:37 GMT 1996 
_crash_version: Digital UNIX V4.0 (Rev. 386); Tue Oct 29 16:56:37 GMT 1996 
warning: thread 0xfffffc002cc28580 appears to be swapped out
unable to get pid for tid (750945664)

warning: thread 0xfffffc002cc28580 appears to be swapped out

warning: cannot get register (number = 64)

warning: cannot get register (number = 64)
warning: thread 0xfffffc002cc28580 appears to be swapped out

warning: cannot get register (number = 64)

warning: PC value 0x0 not valid, trying RA
warning: thread 0xfffffc002cc28580 appears to be swapped out

warning: cannot get register (number = 26)

warning: RA value 0x0 not valid, trying text start
>warning: thread 0xfffffc002cc28580 appears to be swapped out

warning: cannot get register (number = 64)
 [vm_mem_init:173, 0xfffffc0000230000]  lda     sp, -16(sp)
_crashtime:  struct {
    tv_sec = 863719401
    tv_usec = 712862
} 
_boottime:  struct {
    tv_sec = 863103597
    tv_usec = 898896
} 
_config:  struct {
    sysname = "OSF1"
    nodename = "mennis.reo.dec.com"
    release = "V4.0"
    version = "386"
    machine = "alpha"
} 
_cpu:  29 
_system_string:  0xffffffffff800bc0 = "DEC 4000 Model 620" 
_ncpus:  2 
_avail_cpus:  2 
_partial_dump:  1 
_physmem(MBytes):  767 
_panic_string:  0xfffffc000048f328 = "simple_lock: time limit exceeded" 
_paniccpu:  1 
_panic_thread:  0xfffffc002fc662c0 
_preserved_message_buffer_begin: 

....


te0 : diagnostic frame transmit timeout
te0 : diagnostic frame transmit timeout
te0 : setup frame transmit timeout
te0 : diagnostic frame transmit timeout
te0 : setup frame transmit timeout

simple_lock: time limit exceeded

    pc of caller:         0xfffffc000026c868
    lock address:         0xfffffc00098b6220
    current lock state:   0x000000000026d995 (cpu=0,pc=0xfffffc000026d994,busy)

panic (cpu 1): simple_lock: time limit exceeded
syncing disks... DUMP.prom: dev SCSI 0 0 0 0 0 0 0, block 131072
DUMP.prom: dev SCSI 0 0 0 0 0 0 0, block 131072

<3>/usr: file system full
<3>/usr: file system full
<3>/usr: file system full
<3>/usr: file system"
} 
_preserved_message_buffer_end: 
_kernel_process_status_begin: 
  PID   COMM

ps failed
_current_pid:  0 
_current_tid:  0xfffffc002cc28580 
_proc_thread_list_begin: 
_proc_thread_list_end: 
_dump_begin: 
warning: thread 0xfffffc002cc28580 appears to be swapped out

warning: cannot get register (number = 64)
warning: thread 0xfffffc002cc28580 appears to be swapped out

warning: cannot get register (number = 26)
warning: thread 0xfffffc002cc28580 appears to be swapped out

warning: cannot get register (number = 30)
   0 vm_mem_init(l3 address 0xffffffffffffffd0 not mapped, pte 0x0
0xffffffffffffffff, l3 address 0xffffffffffffffd8 not mapped, pte 0x0
0xffffffffffffffff, l3 address 0xffffffffffffffe0 not mapped, pte 0x0
0xffffffffffffffff, l3 address 0xffffffffffffffe8 not mapped, pte 0x0
0xffffffffffffffff, l3 address 0xfffffffffffffff0 not mapped, pte 0x0
0xffffffffffffffff) ["../../../../src/kernel/vm/vm_init.c":173, 0xfffffc0000230000]

warning: thread 0xfffffc002cc28580 appears to be swapped out
_dump_end: 
_kernel_thread_list_begin: 
_kernel_thread_list_end: 
_savedefp:  (nil) 
_kernel_memory_fault_data_begin:  
struct {
    fault_va = 0x0
    fault_pc = 0x0
    fault_ra = 0x0
    fault_sp = 0x0
    access = 0x0
    status = 0x0
    cpunum = 0x0
    count = 0x0
    pcb = (nil)
    thread = (nil)
    task = (nil)
    proc = (nil)
} 
_kernel_memory_fault_data_end:  
_uptime: 171.05 hours
warning: thread 0xfffffc002cc28580 appears to be swapped out
unable to get pid for tid (750945664)

warning: thread 0xfffffc002cc28580 appears to be swapped out

warning: cannot get register (number = 64)

warning: cannot get register (number = 64)
warning: thread 0xfffffc002cc28580 appears to be swapped out

warning: cannot get register (number = 64)

warning: PC value 0x0 not valid, trying RA
warning: thread 0xfffffc002cc28580 appears to be swapped out

warning: cannot get register (number = 26)

warning: RA value 0x0 not valid, trying text start
>warning: thread 0xfffffc002cc28580 appears to be swapped out

warning: cannot get register (number = 64)
 [vm_mem_init:173, 0xfffffc0000230000]  lda     sp, -16(sp)
paniccpu: 0x1 
machine_slot[paniccpu]: struct {
    is_cpu = 0x1
    cpu_type = 0xf
    cpu_subtype = 0x2
    running = 0x1
    cpu_ticks = {
        [0] 0x3a3a12
        [1] 0x17da8
        [2] 0x4afbee
        [3] 0x24e56597
        [4] 0x29e065
    }
    clock_freq = 0x400
    error_restart = 0x0
    cpu_panicstr = 0xfffffc000048f328 = "simple_lock: time limit exceeded"
    cpu_panic_thread = 0xfffffc002fc662c0
} 


etc...