ROBLEM: (MCPM36085) (Patch ID: OSF375-360052) ******** A "simple_lock: time limit exceeded" panic will be seen originating from the ctape_close() routine. The stack trace is as follows: 6 panic("simple_lock: time limit exceeded") 7 simple_lock_fault() 8 simple_lock_time_violation() 9 ctape_close() 10 speclose() 11 spec_close() 12 ufsspec_close() 13 vn_close() 14 closef() 15 close() 16 syscall() 17 _Xsyscall() PROBLEM: (UVO104133) (Patch ID: OSF375-360052) ******** A "simple_lock: time limit exceeded" panic will be seen originating from the ctape_strategy() routine. The stack trace is as follows: 9 panic("simple_lock: time limit exceeded") 10 simple_lock_fault() 11 simple_lock_time_violation() 12 ccmn_rsq_ccb_bld() 13 ctape_strategy() 14 physio() 15 ctape_write() 16 spec_write() 17 ufsspec_write() 18 vn_write() 19 rwuio() 20 write() 21 syscall() 22 _Xsyscall() PROBLEM: (MCPMB61A4) (Patch ID: OSF375-360078) ******** This patch fixes a "simple_lock: time limit exceeded". The following is a list of the typical error messages displayed in the preserved message buffer when the panic occurs: simple_lock: time limit exceeded pc of caller: 0xfffffc00005265ec lock address: 0xfffffc007f5f3ad0 current lock state: 0x00000000005264c5 (cpu=0,pc=0xfffffc00005264c4,busy) panic (cpu 12): simple_lock: time limit exceeded simple lock timeout pc?5i and lock address?5i (dbx) 0xfffffc00005265ec?5i [ctape_close:2669, 0xfffffc00005265ec] addq r31, 0x4, r16 [ctape_close:2669, 0xfffffc00005265f0] bsr r26, swap_ipl(line 131) [ctape_close:2669, 0xfffffc00005265f4] stl r0, 176(sp) [ctape_close:2669, 0xfffffc00005265f8] bis r9, r9, r16 [ctape_close:2669, 0xfffffc00005265fc] bsr r26, simple_lock(line 266) (dbx) 0xfffffc00005264c4?5i [ctape_close:2601, 0xfffffc00005264c4] addq r31, 0x4, r16 [ctape_close:2601, 0xfffffc00005264c8] bsr r26, swap_ipl(line 131) [ctape_close:2601, 0xfffffc00005264cc] stl r0, 176(sp) [ctape_close:2601, 0xfffffc00005264d0] bis r9, r9, r16 [ctape_close:2601, 0xfffffc00005264d4] bsr r26, simple_lock(line 26 6) This indicates the code that was improperly holding the lock. Stack Trace for this problem: panic("simple_lock: time limit exceeded") ["../../../../src/kernel/bsd/subr_prf.c":757] simple_lock_fault() ["../../../../src/kernel/kern/lock.c":1794] simple_lock_time_violation() ["../../../../src/kernel/kern/lock.c":1863] ctape_close() ["../../../../src/kernel/io/cam/ cam_tape.c":2669] speclose() ["../../../../src/kernel/vfs/spec_vnops.c":2306] spec_close() ["../../../../src/kernel/vfs/spec_vnops.c":2459] msfsspec_close() ["../../../../src/kernel/msfs/osf/msfs_vnops.c":3869] vn_close() ["../../../../src/kernel/vfs/vfs_vnops.c":1220] closef() ["../../../../src/kernel/bsd /kern_descrip.c":1393] close() ["../../../../src/kernel/bsd/kern_descrip.c":1071] PROBLEM: (QAR 56151) (Patch ID: OSF375-206) ******** This patch fixes a problem where during tape operations, the SPACE commands can not be interrupted. PROBLEM: (QAR 61716,QAR 56648) (Patch ID: OSF375-218) ******** This patch fixes an ASE NFS problem that occurs on ASE systems with KZPBA disk controllers. The system crashes with a "simple_lock timeout" panic. ASE NFS services send the aseagents for most or all nodes into an uninterruptable state: root@scully:/ > ps -elf |grep aseagent 8001 U < 0 318 1 0.0 39 -5 1.7M 3abf3580 16:02:21 0:00.58 /usr/sbin/aseagent -b -p hsm 80808001 S + 0 7566 6128 0.0 44 0 136K 3fe83894 08:04:42 0:00.0 0 A sample stack trace is as follows: > 0 thread_block() ["../../../../src/kernel/kern/sched_prim.c":2113,] 1 mpsleep() ["../../../../src/kernel/bsd] 2 cdisk_online(type_open = 0) ["../../../../src/kernel/io/cam/cam_disk.c":6769] 3 cdisk_open() ["../../../../src/kernel/io/cam/cam_disk.c":6269] 4 spec_open() ["../../../../src/kernel/vfs/spec_vnops.c":14] 5 vn_open() ["../../../../src/ker] 6 copen() ["../../] 7 open() ["../../../../src/kerne] 8 syscall() ["../../../../src/kernel/arch/alpha/syscall_trap.c":] 9 _Xsyscall() ["../../../../src/kernel/arch/alpha/locore.s":1209,] PROBLEM: (QAR 59840) (Patch ID: OSF375-241) ******** Under certain conditions, the message "ctape_strategy: READ case and density info not valid." was being printed for every read from tape. This change will print the message only once.