| Title: | File Shelving |
| Moderator: | COOKIE::HOLSINGER |
| Created: | Mon Mar 15 1993 |
| Last Modified: | Thu Jun 05 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 346 |
| Total number of notes: | 1204 |
Hello, Just to check if it is a known problem: AlphaServer 1000A 4/266 running VMS V6.2-1H3 HSDRIVER is X-BL20 29-Oct-1996 21:18:52:47 Crashdump Summary Information: ------------------------------ Crash Time: 10-FEB-1997 15:02:09.16 Bugcheck Type: SSRVEXCEPT, Unexpected system service exception Node: ARCHER (Standalone) CPU Type: AlphaServer 1000A 4/266 VMS Version: V6.2-1H3 Current Process: HSM$SHELF_HNDLR Current Image: ARCHER$DRA0:[SYS0.SYSCOMMON.][SYSEXE]HSM$SHELF_HANDLER.EXE;3 Failing PC: FFFFFFFF 80583C64 Failing PS: 10000000 00000203 Module: HSDRIVER Offset: 00005C64 Boot Time: 10-FEB-1997 14:38:54.00 System Uptime: 0 00:23:15.16 Crash/Primary CPU: 00/00 Saved Processes: 31 Pagesize: 8 KByte (8192 bytes) Physical Memory: 512 MByte (65536 PFNs) Dumpfile Pagelets: 248801 blocks Dump Flags: olddump,writecomp,errlogcomp,dump_style EXE$GL_FLAGS: poolpging,init,bugdump Stack Pointers: KSP = 00000000 7FF91BC8 ESP = 00000000 7FF96000 SSP = 00000000 7FF9C100 USP = 00000000 00861820 General Registers: R0 = 00000000 0000000C R1 = 00000000 7FF91DE8 R2 = FFFFFFFF 8120E5C0 R3 = FFFFFFFF 81210A80 R4 = FFFFFFFF 814C9E40 R5 = FFFFFFFF 814F3D00 R6 = 00000000 0021B95C R7 = 00000000 7FF91FC0 R8 = 00000000 00000001 R9 = 00000000 00000001 R10 = 00000000 00000000 R11 = 00000000 00000000 R12 = 00000000 00000000 R13 = FFFFFFFF A2DC4FD0 R14 = 00000000 00000000 R15 = 00000000 0029E0E0 R16 = 00000000 000003C4 R17 = 00000000 7FF91C80 R18 = 00000000 00000020 R19 = FFFFFFFF 82604D98 R20 = 00000000 7FF91F50 R21 = 00000000 00000000 R22 = FFFFFFFF A2DC4000 R23 = 00000000 7FF92000 R24 = 00000000 7FFF0024 AI = 00000000 00000003 RA = 00000000 00000000 PV = FFFFFFFF 82604200 R28 = 00000000 000005AC FP = 00000000 7FF91BD0 PC = FFFFFFFF A2E5CB3C PS = 08000000 00000200 Exception Frame: R2 = FFFFFFFF 81234DF5 R3 = FFFFFFFF 81210A80 R4 = FFFFFFFF 814C9E40 R5 = FFFFFFFF 814F3D00 R6 = 00000000 0021B95C R7 = 00000000 7FF91FC0 PC = FFFFFFFF 80583C64 PS = 10000000 00000203 Signal Array: Arg Count = 00000005 Condition = 0000000C Argument #2 = 00000000 Argument #3 = 90001620 Argument #4 = 80583C64 Argument #5 = 00000203 Mechanism Array: Arguments = 0000002B Establisher FP = 00000000 00861820 Flags = 00000001 Exception FP = 00000000 7FF91E40 Depth = FFFFFFFD Signal Array = 00000000 7FF91DE8 R0 = FFFFFFFF 90001600 R1 = 00000000 00000028 R16 = 00000000 00000001 R17 = FFFFFFFF 90001600 R18 = 00000000 00000000 R19 = FFFFFFFF 82604D98 R20 = 00000000 7FF91F50 R21 = 00000000 00000000 R22 = FFFFFFFF 814F3D0B R23 = 00000000 00000001 R24 = 00000000 00000005 R25 = 00000000 00000000 R26 = FFFFFFFF 80583C28 R27 = FFFFFFFF 8270FCC8 R28 = FFFFFFFF 8057FE5C System Registers: Page Table Base Register (PTBR) 00000000 00001033 Processor Base Register (PRBR) FFFFFFFF 8120E000 Privileged Context Block Base (PCBB) 00000000 06C02080 System Control Block Base (SCBB) 00000000 00000153 Software Interrupt Summary Register (SISR) 00000000 00000000 Address Space Number (ASN) 00000000 00000026 AST Summary / AST Enable (ASTSR_ASTEN) 00000000 0000000F Floating-Point Enable (FEN) 00000000 00000001 Interrupt Priority Level (IPL) 00000000 00000002 Machine Check Error Summary (MCES) 00000000 00000008 Virtual Page Table Base Register (VPTB) 00000002 00000000 Failing Instruction: HSDRIVER_PRO+05C64: LDL R0,#X0020(R0) Instruction Stream (last 20 instructions): HSDRIVER_PRO+05C14: LDA R27,#XFD28(R13) HSDRIVER_PRO+05C18: AND R16,#X08,R28 HSDRIVER_PRO+05C1C: BEQ R28,#X000005 HSDRIVER_PRO+05C20: BIS R31,R31,R1 HSDRIVER_PRO+05C24: BSR R26,#XFFF27A HSDRIVER_PRO+05C28: BEQ R0,#X000002 HSDRIVER_PRO+05C2C: LDL R17,(R2) HSDRIVER_PRO+05C30: BNE R17,#X000009 HSDRIVER_PRO+05C34: LDL R27,#X0020(R3) HSDRIVER_PRO+05C38: BIC R27,#X01,R0 HSDRIVER_PRO+05C3C: BGE R0,#X00000C HSDRIVER_PRO+05C40: LDL R0,#X0020(R0) HSDRIVER_PRO+05C44: LDQ R28,(SP) HSDRIVER_PRO+05C48: LDQ R13,#X0008(SP) HSDRIVER_PRO+05C4C: ADDQ SP,#X10,SP HSDRIVER_PRO+05C50: RET R31,(R28) HSDRIVER_PRO+05C54: BIS R31,R31,R31 HSDRIVER_PRO+05C58: LDQ R28,(SP) HSDRIVER_PRO+05C5C: BIS R31,R17,R0 HSDRIVER_PRO+05C60: LDQ R13,#X0008(SP) HSDRIVER_PRO+05C64: LDL R0,#X0020(R0) HSDRIVER_PRO+05C68: ADDQ SP,#X10,SP HSDRIVER_PRO+05C6C: RET R31,(R28) HSDRIVER_PRO+05C70: LDQ R28,(SP) HSDRIVER_PRO+05C74: BIS R31,R31,R0 Thank you for reading this, regards, Sekula Bojovic CSC Sydney
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 318.1 | COOKIE::MCALLISTER | Thu Feb 13 1997 17:29 | 7 | ||
What was going on at the time of the crash? File faults, deletion of shelved files, etc.? Thanks, Barb | |||||
| 318.2 | a view from on-site.. | COMEUP::SIMMONDS | lock (M); while (not *SOMETHING) { Wait(C,M); } unlock(M) | Mon Feb 17 1997 17:23 | 14 |
.1> What was going on at the time of the crash? File faults, deletion of
At BUGCHECK time, my Customer's code was inside sys$crmpsc() (creating
a Private Disk File Section) and sys$vm appears to have called sys$qiow()
to read a cluster from a SHELVED file into VM.. the crash seems to have
occurred around the time that HSM felt that the file fault was handled
and the file was ready for prime-time..
This would be the _only_ HSM activity occurring (Customer is currently
evaluating this Product's utility by performing simple controlled shelve
and unshelve sequences..)
Hope this helps..
John.
| |||||
| 318.3 | COOKIE::MCALLISTER | Tue Feb 18 1997 10:56 | 6 | ||
Yes, this helps explain the code that we just got from the customer (I have been exchanging mail with Sekula). We are pursuing what we believe to be the problem in the driver. When we have a fix, would the customer be willing to test the new image (I sent mail to Sekula asking the same question)? Barb | |||||
| 318.4 | willing | COMEUP::SIMMONDS | lock (M); while (not *SOMETHING) { Wait(C,M); } unlock(M) | Tue Feb 18 1997 18:59 | 6 |
Barb, as I said to Sek also, yes, I believe my Customer will be willing
to test your corrected driver.. (I assume the V2.1 driver has the same
defect as the V2.0A driver?)
Thanks!
John.
| |||||
| 318.5 | COOKIE::MCALLISTER | Wed Feb 19 1997 14:39 | 8 | ||
Yes, the V2.1 driver will have the same problem. I am hoping to have a new driver available tomorrow after our nightly build and another test run. I will send mail when it's ready. It will help us a lot to have the customer test it since they are the only ones seeing the problem that we know of, so thanks for the assistance. Barb | |||||
| 318.6 | testing failed to produce any BUGCHECK! :) | COMEUP::SIMMONDS | lock (M); while (not *SOMETHING) { Wait(C,M); } unlock(M) | Sat Feb 22 1997 19:38 | 8 |
Re: .5
Ok, your corrected V2.1 HSDRIVER seems immune to the usual provocative
techinques which produced the prior bugchecks.. now if we can fix the
I/O stalling problem (see 319.*) my Customer _might_ buy the Product!!
Thanks,
John.
| |||||
| 318.7 | COOKIE::MCALLISTER | Mon Feb 24 1997 10:17 | 7 | ||
This driver crash will only be seen if a QIO is performed on a shelved file using the ACPCONTROL REMAP function. This should be a very rare event. The fix will be in V2.2. If any other customer sees this crash, please send us mail, and we will make the fixed driver (for V2.0A and V2.1) available on an as needed basis. Barb | |||||