PROBLEM: (OSF QAR 49454)	  (Patch ID: OSF405-050)
********
If a VME device driver enables interrupts at the same IRQ level for more than 
one SCB vector, and subsequently attempts to disable one of the interrupts, the 
disable fails, making re-enabling of the interrupt for that vector impossible.

You will see an error upon disabling.  An example of this error from a VME 
driver called dmaex follows:

First the driver is loaded, which enables interrupts for both vectors 0xf0
and 0xf1 at IRQ level 1:
        # sysconfig -c dmaex
        # dmaex_ctlr_unattach: dmaex0 handler_disable failure
        dmaex0 at vba0 csr 0x104000000 vme A24 user data mode
         vec 0xf0 priority 1

Next, an attempt is made to disable the interrupts, which fails:
        # sysconfig -u dmaex
        dmaex_ctlr_unattach: dmaex0 handler_disable failure
        LDBL: Failed to unattach controller dmaex0, status = 19
        dmaex_configure: unconfigure driver failed - status 0x13

After the patch is installed, the disable output looks as follows:
        # sysconfig -u dmaex

ie there is no error message after the command.

PROBLEM:  (QAR 54144 QAR 54586)		 (Patch ID: OSF405-135)
********
This patch fixes a problem that occurs on Alpha VME 4/2xx systems.  The system
may panic and display the following error message:

        kernel access memory fault