in the following description , details on the embodiments of the present invention are set forth with reference to drawings . the system in fig4 comprises a plurality of units a and a unit b 2 for controlling each of the units a . the units a are separated in a group of a partition a 3 or a group of a partition b 4 ; however the unit a 103 can be a part of the partition a 3 or a part of the partition b 4 . an explanation of the preferred embodiment of the present invention is provided below in conjunction with the accompanying drawings . fig4 is a diagram describing a computer ( a large - scale computer system ) of the embodiment of the present invention . normally , each unit a separated by each partition , interacts with a unit b 2 over bus - a 5 ( for example , local request bus ), and transmits a request , which is insolvable within the unit a , to the unit b 2 ( this is ( 1 )′ information transmission shown in fig4 ). and , over bus - b 6 ( for example , global storage address bus ), a request received by a section circuit 11 is broadcast to the other units a ( this is ( 2 ) request transmission to partition in fig4 ). however , when failure is detected in a unit c 101 ( a ), the failed unit c 101 transmits failure notice to the unit b 2 at a prescribed timing using a bus - c 7 ( this is ( 3 )′ failure notice or ( 3 ) normal notice in fig4 . it is the normal notice when failure does not occur ) the unit b 2 determines failure information from information ( packet ) received over the bus - c 7 , and transmits the same information to each of the unit c 101 and units a 102 - 104 over a bus - d 8 ( this is notice to partition ( 4 ) in fig4 ). units a , constituting the same partition a 3 with the failed unit a , stop the operation according to the failure information received in the bus - d 8 . units a in partition b 4 , although receiving the failure information ( such as error notice ), continue the operation , ignoring the failure information ( this is the operation in ( 5 - 1 ), ( 5 - 2 ), ( 5 - 3 ), ( 5 - 4 ) in fig4 ). next , an example of the case that failure is detected in a unit c 101 ( equivalent to the unit a ) in the partition a 3 is explained with reference to a flowchart in fig5 . step s 21 carries out a normal operation of the system and issues a request ( information transmission ( 1 )′). in step s 22 , the selection circuit 11 receives the requests transmitted from each unit a , and broadcasts a selected request to units a in each partition ( 2 ). s 21 and s 22 are the state in which the ( 3 ) normal operation is carried out . if failure occurs in the unit c 101 in fig4 , then , in step s 23 , the failure occurred in the unit c 101 of the partition a 3 is detected (( 1 ) failure detection in fig4 ). then , preparation for notifying the unit b 2 of failure detection is started . in step s 24 , all of the units a in the partitions a 3 and b 4 to unit b 2 notify the unit b 2 of the information ( 3 ), ( 3 )′, ( 3 )′′. in the present example , from the failed unit c 101 failure notice is added to the information ( packet ) for notification . from the unit a 102 , 103 , which is not failed , a normal information notification is carried out . at that time , the notification is carried out by the bus - c 7 , and the above failure notice is transferred after , for example , establishing an abort status field to a packet explained later and adding the severe failure information . in step s 25 , a merge circuit 12 receives the information ( packet ) ( 3 ), ( 3 )′, ( 3 )′′ transferred through the bus - c 7 , and notifies of failure occurrence by the bus - d 8 . in the present example , failure occurs in the unit c 101 . therefore identical failure information is generated in order to have each of the units a comprised in the partition a 3 recognize the failure , and the bus - d 8 notifies each of the units a of a result of the merge circuit 12 . at that time , however , there is no response from the unit a 104 comprised in the partition a 3 . in step s 26 , the operation is stopped when each of the units a in the partition a 3 recognizes the failure by the identical failure information . the partition b 4 continue the operations ignoring the failure in the partition a 3 . in the present example , the partitions a 3 and b 4 are notified the identical failure notice information generated by the merge circuit 12 over the bus - d 8 . each of the units a of the partition a 3 , which received the identical failure information , recognize the failure by the identical failure information , generated in the merge circuit 12 , and stops the operation ( 5 - 1 ), ( 5 - 2 ). the units al in the other partition b 4 ignore the failure notice and continue the operation ( 5 - 3 ), ( 5 - 4 ). according to the above configuration , the management processor is not notified of interruption , log recovery and restart processing are not performed , and instruction from the management processor is not required when failure occurs ; therefore , it is possible to perform an immediate hard stop of the units in the same partition of the occurrence of the failure . the system in fig4 comprises a plurality of units a and a unit b 2 for controlling each of the units a . the units a are separated in a group of a partition a 3 or a group of a partition b 4 ; however the unit a 103 can be a part of the partition a 3 or a part of the partition b 4 . in fig6 , a severe failure notification method is explained . when failure is detected in a unit d 102 ( a ), and the failure is so severe that the bus - c 7 cannot be used , the failed unit d 102 uses the sig - a 9 and informs the unit b 2 that the failed unit d 102 is logically separated . here , sig - a 9 is a signal line ( interconnection line ) to make the unit b 2 recognize the presence of the unit d 102 . next , the unit b 2 recognizes that severe failure occurred in the unit d 102 by the sig - a 9 . the unit b 2 transfers and recognizes severe failure information to the merge circuit 12 instead of a failed unit d 102 , at the timing that the failed unit d 102 has to transmit failure information using the bus - c 7 . based on the informed sever failure information , identical severer failure information is generated , and the unit b 2 transmits identical severe failure information to each of the units a using the bud - d 8 . the units a constituting the same partition with the failure - detected unit d 102 stops operation according to the severe failure information received in the bus - d 8 ( 5 - 1 ), ( 5 - 2 ). the units a in different partitions ignore the severe failure information received in the bus - d 8 and continue the operation ( 5 - 3 ), ( 5 - 4 ). next , an explanation of the case that severe failure occurs is provided with reference to a flowchart in fig7 . step s 41 carries out operation of the normal system and issues a request ( for information transmission ( 1 )′). in step s 42 , the selection circuit 11 receives requests transmitted from each of the units a , and broadcasts the selected request to the units a in each partition ( 2 ). s 41 and s 42 are in the state that the normal operation is carried out . when severe failure occurs , as shown in fig6 , in step s 43 , preparation for detecting and notifying the severe failure is started in a unit d 102 in the partition a 3 . step s 44 performs severe failure notification from the unit d 102 to the unit b 2 through the sig - a 9 . the sig - a 9 confirms whether the unit a is logically present or not by determining whether it is separated or not . in step s 45 , it is confirmed that a unit d 102 of the partition a 3 falls into severe failure ( 2 )′′ by a failure detection circuit 10 , comprised in the unit b 2 . here , the failure detection circuit 10 is connected one - on - one to each of the units a , and when severe failure occurs , prepares for severe failure notification to the merge circuit 12 . step 46 notifies the unit b 2 of information ( 3 ), ( 3 )′, ( 3 )′′ from all units a in the partitions a 3 and b 4 . in the present example , severe failure notice is added to the information and notified to the merge circuit 12 from the unit d 102 where the severe failure occurs via the sig - a 9 and the failure detection circuit 10 . from the unit al where failure does not occur , normal information is informed . at that time , the notice is performed over the bus - c 7 . the above severe failure notice is transferred after , for example , establishing an abort status field to a packet explained later and adding the severe failure information . in step s 47 , the merge circuit 12 receives the information transferred over bus - c 7 ( 3 ), ( 3 )′, ( 3 )′′ and communicates the failure occurrence via the bus - d 8 . in the present example , severe failure occurs in the unit d 102 . therefore identical severe failure information for making each of the units a comprised in the partition a 3 recognize the severe failure is generated in the merge circuit 12 , and the bus - d 8 notifies each unit a of generation result of the merge circuit 12 . in step s 48 , the unit a in the partition a 3 stops when it recognizes occurrence of severe failure . the other partitions ignore the failure occurred in the partition a 3 and continue the operation . in the present example , the partitions a 3 and b 4 are notified of the identical severe failure notice information generated by the merge circuit 12 . each unit al of the partition a 3 , which received the identical severe failure information recognizes the failure and stops the operation ( 5 - 1 ), ( 5 - 2 ). the units a in the other partition b 4 ignore the failure notice and continue the operation ( 5 - 3 ), ( 5 - 4 ). the above configuration , even when severe failure occurs , allows prompt hard stop of units in the same partition as the failed unit upon failure occurrence . next , an explanation of the information ( packet ) transmitted over the bus - c 7 and the bus - d 8 explained above is provided below . fig8 shows an example of a data structure of the bus - c . the information transferred via the bus - c 7 can be comprised of fields such as v : valid , t : target - hit , abtst : abort status , cst : cache status , stbnum : store buffer number . here , v : valid is a flag indicating whether the packet is valid or invalid . t : target - hit indicates presence / absence of hit to dimm ( dual inline memory module ). abtst : abort status notifies of retry notice or error notice . cst : cache status indicates the state of cache . stbnum : store buffer number indicates where the dimm is written . fig9 shows an example of data field structure of the information transferred via the bus - d . the bus - d comprises v , t , cst as in the case of the bus - c 7 , for example , and configured from board_id : board id and invcnt : invalidation count etc . board_id : board id indicates a board number of the unit a . invcnt : invalidation count indicates the number of share - hit . when communicating a failure notice , a value is applied to the abtst . thus , when failure occurs , the other fields in the bus - c 7 and the other fields in the bus - d 8 become meaningless . for example , in the case of the bus - c 7 , chkstp ( failure ) of abtst = 111 is notified in failure occurrence . at that time , the other fields are invalid . in the normal condition , it is abtst = 000 . in the case of the bus - d 8 , chkstp of abtst = 111 is broadcast in failure occurrence , and whether it is its own partition or not is checked . the check is performed by the receiving unit a side ( the check can be carried out at a prescribed timing , for example ). when severe failure is notified by the sig - a 9 , abtst = 111 is also set . then , it is communicated from each unit a in the merge circuit 12 via the us - c 7 . information of the bus - d 8 is generated from the information communicated . however , the abtst = 111 of error transmission has the highest priority , and therefore the abtst of the bus - d 8 is made 111 and is broadcasted even though normal information is notified from the other bus - c 7 . and error notification is performed to all units a . since many of failure detections are constantly checked , it is difficult to determine exactly when the failure is detected ; however , failure notice is generated and inserted when result notification of ( 3 ), ( 3 )′, ( 3 )′′ after issuing the requests ( 1 )′. consequently , the failure notice can be inserted as long as the failure is detected before ( 3 ), ( 3 )′, ( 3 )′′. the present invention is not limited to the embodiments described above ; however , various improvements and changes may be made without departing from the scope of the invention .