CA2236114A1 - Detecting memory problems in computers - Google Patents

Detecting memory problems in computers Download PDF

Info

Publication number
CA2236114A1
CA2236114A1 CA 2236114 CA2236114A CA2236114A1 CA 2236114 A1 CA2236114 A1 CA 2236114A1 CA 2236114 CA2236114 CA 2236114 CA 2236114 A CA2236114 A CA 2236114A CA 2236114 A1 CA2236114 A1 CA 2236114A1
Authority
CA
Canada
Prior art keywords
checksum
storage area
calculated
calculating
restart
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
CA 2236114
Other languages
French (fr)
Inventor
Jarmo Rinne
Kari Pasanen
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Nokia Oyj
Original Assignee
Individual
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from FI955187A external-priority patent/FI102221B/en
Application filed by Individual filed Critical Individual
Publication of CA2236114A1 publication Critical patent/CA2236114A1/en
Abandoned legal-status Critical Current

Links

Landscapes

  • Techniques For Improving Reliability Of Storages (AREA)
  • Detection And Correction Of Errors (AREA)

Abstract

In process controlling computers, such as switching exchanges, faults may prove to be very expensive. Particularly hard to solve are software defects. If problems occur, it is important that maintenance can be directed at the correct target as soon as possible. A threat is constituted by vandals and hackers. If the option for maintaining from elsewhere is incorporated in computers, the danger for misuse consequently increases. Prior art techniques for detecting memory problems do not necessarily reveal defects occurring at regular intervals caused by the method of calculation. Memory defects will occur at regular intervals e.g., if an address line of a memory circuit becomes faulty. A second drawback of the prior art is that the checksum has to be calculated anew if the contents of just one storage location change. The method of detecting memory problems according to the invention is "regularly irregular" so that it detects in a reliable manner an uncontrolled change in any storage area (MA). Furthermore, the checksum (CS) calculated according to the method may be updated upon changes of an element in a storage area (MA) so that the updating requires much less calculation than would calculating the checksum over the entire storage area (MA) being monitored. The method is applicable in detecting hardware and software defects and in expediting the restart of a computer.

Description

-WO 97/16786 PCT~I96/00572 DETECTING MEMORY PROBLEMS IN COMPUTERS

The present invention relates to checking the integrity of memory contents in computers.
Figure 1 shows the parts of a computer that are essential as far as the invention is concerned. At the initial stage, after power switch-on, the contents of the main memory RAM are in an undefined state. The initial loading of a conventional computer takes place so that power switch-on generates an initial signal INIT which makes e.g. a processor CPU jump into a predetermined 10 address. This memory has, in a Read Only Memory ROM, an initial loading program the execution of which comprises loading the basic parts of the operating system (OS) from a predetermined location in a disk drive HD. The OS basic parts thus loaded contain more advanced loading programs, which load parts of the OS not only from the locations predetermined for the Hl~) in the 15 ROM but from elsewhere as well. These more advanced loading programs, in turn, load other software modules etc.
The software modules are not necessarily located at contiguous areas on the disk drive HD. Upon reading from the HD, it is often the case that information located at different areas of the HD must be read in succession. A
20 suggestive guideline value is that it is possible to read approximately 1 MB/s of contiguous areas from a disk drive, but in practice the reading rate is no more than one half of this. To take an example, loading 30 MB of software may take approximately a minute.
In process controlling computers, such as switching exchanges, 25 faults may prove to be very expensive. Particularly hard to solve are software defects. Hardware defects can often be detected by making comparisons to another apparatus, known to be in a proper working order. Software defects cannot usually be detected in this manner as there usually exists no reference software known to be operating properly. In many cases, the further drawback is 30 often encountered that on the basis of the symptoms it is often impossible toquickly deduct whether the fault is in the hardware or in the software.
Uncontrolled changes in a specific storage area may result from either one of the reasons. If problems occur, it is important that maintenance can be directedat the correct target as soon as possible.
A threat is constituted by vandals and "hackers". If the option for W O 97/16786 PCT~FI96/00572 remote maintenance is incorporated in computers, the danger for misuse consequently increases.
In order to detect memory problems, several different solutions have been developed. Prior art knows a so-called parity bit by means of which it is 5 possible to have an even number of 1-bits in the storage location (or, if desired, an odd number). As is well known, the use of parity does not detect a simultaneous change of state by an even number of bits in a storage location.
Another con""only used tool is a Cyclic Redundancy Check, CRC.
The CRC sum is a useful tool in detecting errors in serial mode data, such as 10 in disk drives and data links. Relating to matrix data, the CRC sum is faced with two problems. The first of these is that CRC sums cannot be used to reliably detect defects that occur at such intervals that result from the methodof calculating the CRC sum. The second problem is associated with the fact that the CRC sum has to be calculated anew if the contents of just one storage 15 location change.
Resulting from the above, it is an object of the present invention to develop a method and apparatus by means of which memory problems of computers can be detected and the aforementioned problems solved. On the one hand, the invention is based on a method which, based on experience 20 gathered up to date, is extensive enough to detect all conceivable uncontrolled changes in the memory, and on the other hand, on employing this method in the various operations of the computer.
The method and the system according to the invention first of all have the advantage of reliably detecting memory problems. This in turn leads 25 to the second advantage, which is that the restart of a computer can be expedited by omitting some operations that in prior art systems are carried out "just in case".
In the following, the invention will be described in greater detail by means of its preferred embodiments, with reference to the accompanying 30 drawings in which:
Figure 1 shows the parts of a computer that are essential as far as the invention is concerned;
Figure 2 illustrates using a checksum for monitoring memory contents;

Figure 3 is a flow chart illustration fom"ai"L~i"ing a checksum; and Figure 4 illustrates calculating a checksum in accordance with the invention.
Regarding the flow chart of Figure 2, the checksum is calculated over 5 a specific storage area, it is compared to the previous checksum calculated, and in case the checksums differ, an error message will be given. In the flow chart of Figure 2, the significant matter is the manner the calculating the checksum is initiated. According to one embodiment of the invention, the calculation takes place at regular intervals. According to another embodiment, 10 the checksum is calculated in association with specific events, such as switching on a computer, modifying programs, etc.
The flow chart of Figure 3 illustrates how writing into memory takes place. In case the contents of a storage area change, the checksum will be corrected by (i) deleting the portion of the changed storage area from the 15 previous checksum, and (ii) by adding, to the checksum thus changed, a portion corresponding to the new contents of the changed storage area.
The simplicity of the flow chart in Figure 3 ensues from that the prior art methods for c~lc~ ting a checksum cannot be used for deleting the previous portion of a changed storage area from a calculated checksum and replacing ~0 it with a portion corresponding to the new contents of the same storage area.Next, referring to Figure 4, a new method according to the present invention will be described for calculating a checksum. Out of the total memory MEM of a computer, the checksum is to be calculated over a storage area MA being monitored. The width M of the checksum (CS) is arbitrary, but a suitable value ~5 for the width M equals the word length W of the computer. Prior to the c~lclll~tion, the checksum is given an initial value, e.g. 0. The c~lc~ tion takes place so that each element Mj (where i denotes an index for the element within the storage area), having M bits, in a storage area MA is summed bitwise to the checksum CS (by an Exclusive OR operation) so that, prior to summing, 30 the element Mj is rotated k bits to the right (in the direction of the least significant bit). The number k of the rotations is obtained from:

O~
k=~INT(ilMi) (1) j-o where INT denotes an integer. In practice, the summing does not have to be continued forever but only up to the highest value of j at which Mi is lower than or equal to the element index i (or the highest conceivable index value).
The same result can be achieved by the following fast method. The elements of the storage area MA are summed bitwise (Exclusive OR) to the checksum CS. After each summing, the checksum is rotated one bit to the left (in the direction of the most significant bit). The rotating is repeated if i+1 is divisible by M, and again if i+1 is divisible by M2, etc, until all the conceivable integer powers of M have been gone through. Once all the elements have been summed, the checksum is rotated to the right as many times as it was rotated to the left during the summing.
A noteworthy advantage of this method is that the checksum thus calculated may easily be updated. The updating takes place e.g. as follows:
(1) Summing the data of the changed element to the old data of the element.
(2) Deducting, on the basis of the index of the changed element, how many rotations were made in all at this element when calculating the original checksum.
(3) Rotating the sum to the right to the same extent.
(4) Summing the rotated sum thus obtained to the original checksum.
The result thus obtained is a new checksum updated with regard to the changed storage area. If a storage area having an arbitrary size changes, the checksum can be updated by carrying out just two summings per element.
Thus, the new checksum does not have to be calculated over the entire storage area, which would be the case with the cyclic redundancy check (CRC).
The number of rotations at the changed element may be c~lcul~ted by dividing the element index i by conceivable integer powers of M and by summing the integers of the quotients according to equation (1).
Referring to Table 1, an exemplary calculation of a checksum according to the method of the invention will now be described. For reasons of simplicity, it is assumed that the storage area comprises 16 locations that can be addressed by a 4-bit index. In this example, the data of the storage locations also has a width of 4 bits. Also, the initial value of the checksum is ~VO97/16786 PCT~196/00572 set to zero. All these assumptions have been made in order to illustrate the invention, and they do not restrict it in any way.
The contents 1001 of the storage location 0 are summed bitwise to the initial value 0000, and as 0+1 is not divisible by the width (4) of the 5 checksum, the sum is rotated once to the leK. The new checksum obtained is 0011. To this sum is added the contents 1011 of the storage location 1, and the sum thus obtained is rotated once to the left because 1+1 is not divisible by the width of the ckecksum. After this, the new checksum is 0001. The process continues is this manner up until the entire storage area has been 10 gone through. At storage locations 3, 7 and 11, the checksum is rotated twicebecause these indexes incremented by one are divisible by the width of the checksum. At storage location 15, there will be three rol~lio"s as 15+1 is divisible by both the width of the checksum and its quadrature. At all other storage locations, the checksum is only rotated once. Lastly, the checksum is 15 rotated 21 times in the opposite direction, i.e. to the right. The final checksum obtained is 0111. The step-by-step progress of the calculation is illustrated in Table 1.

Table 1 Address Data Old CS Bitsum New CS Kota-tions Next, it is assumed that the contents of e.g. the storage location 0101 change from the value 1010 to 0110. The bitwise sum of the old and new contents will be 1100. On the basis of index 0101 (=5) the bitwise sum 1100 is rotated 5+1=6 times to the right, whereby the result obtained is 0011. When this is summed to the old checksum, the new checksum obtained is 1 110. The same result is also obtained by repeating, from the beginning, the procedures discussed in association with Table 1, but with the contents of the storage location 0101 having the new value, in this case 0110.
The checksum can most advantageously be calculated by a 10 computer program. For this purpose, the following program, in the form of pseudocode resembling Pascal, can be utilized.

SUM := initial value;
for I := 0 to N-1 do SUM := SUM xor X(l);
SUM := SUM rol 1;
if (I + 1) mod M = 0 then SUM := SUM rol 1;
if (I + 1) mod (M*M) = 0 then SUM := SUM rol 1;
if (I + 1) mod (M*M*M) = 0 then SUM := SUM rol 1;
. . .
end;
end;
end;
end;
end;
N1 := N+N / M+N / (M*M)+N / (M*M*M)+N ...;
SUM := SUM ror N1;
end;

In the above pseudocode, N denotes the size of the storage area being monitored, xor denotes the bitwise sum (Exclusive OR), mod siyl ,iries a modulo operator (remainder), rol 1 means a rotate left, and ror 1 W O 97/16786 PCT~I96/00572 correspondingly a rotate right.
The following pseudocode may be used to update the checksum:

SUM := initial value;
for I := 0 to N-1 do 11 :=1+1/ M+l / (M*M)+I / (M~M~M)+I ...;
SUM := SUM xor (X(l) ror 11);
end;

It is obvious that no checksum is able to detect all memory problems.
There is an apparent reason for this: as the information contents of the checksum CS are much smaller than that of the storage location MA over which the ckecksum was calculated, the storage location MA inevitably has 15 several possible contents producing the same checksum CS. In practice, however, the defects are detected reliably. An uncontrolled change of the storage location without a concurrent change in the checksum would require a simultaneous change of several bits in several addresses of the storage area according to a specific mathematical regularity. Although practical memory 20 problems often do manifest mathematical regularity, this regularity is not ofsuch nature that memory problems would remain undetected by the method of the invention. In this respect, it could be said that calculating the checksum in accordance with the invention is "regularly irregular".
The method of the invention for calculating a checksum can be 25 applied e.g. as follows: a dedicated checksum is assigned to each storage area being monitored. Upon changing the contents of the storage area, the checksum is also changed accordingly. The integrity of the checksum is monitored e.g. at specific intervals or in association with specific events. Upon detecting that the checksum does not match, the defect is at least reported 30 and other measures required are additionally taken.
A second way of utilizing the checksum calculation method of the invention is to expedite the restart of a computer. Conventional computers in - this case load their entire software from a disk drive, a network etc. By utilizing the checksum according to the invention, it is possible to indicate which 35 storage areas have endured free of defects as regards their contents, resulting W O 97/16786 PCT~I96/00572 in that their contents do not have to be reloaded. In consequence, the start-up of a computer can be expedited by several tens of seconds compared to the prior art technology. Prior to the restart, a checksum CS may be calculated over one or more storage areas MA being monitored, and these checksums 5 may be stored in the main storage. Some systems allow a protection for a part of the memory against later overwriting. In a memory of that type, such checksums may be stored which correspond to different program modules, because once the program module has been loaded into a memory, its contents should not be changed. Alternatively, a predetermined checksum 10 may be associated with each program module stored in the disk drive. During loading the program module, the checksum may first be read out from the disk drive and compared to the checksum calculated over the corresponding storage area. If the checksums are identical, the program module will not have to be loaded anew from the disk drive. The checksums of different modules of 15 software consisting of multiple parts may be stored in a common file the reading of which quickly unravels which modules have undergone the switch-on without defects and which ones should be reloaded from the disk drive.
Although the invention is explained by using computers as examples, the invention is not restricted to computers in a narrow sense but may be 20 applied to all situations where electronic memories are used. Examples of such implementations include computer peripheral devices and communication systems, image and sound memories, data logging systems, control and process automation systems, and various kinds of aulur~ uns. It is also obvious to a person skilled in the art that upon advancements in 25 technology the basic idea of the invention can be implemented in various ways. The invention and the embodiments thereof are not rt:sl,i~;L~d to the examples described above but they may vary within the scope of the claims.

Claims (10)

Claims
1. A method for calculating an M-bit checksum (CS) over a storage area (MA) comprising memory elements (M;), c h a r a c t e r i z e d by the steps of - giving the checksum (CS) a predetermined initial value prior to the calculation, - calculating the checksum (CS) at each memory element (Mi) of the storage area (MA) as a bitwise sum (Exclusive OR), the first factor of the bitwise sum being formed on the basis of the element (Mi) in question and a second factor on the basis of the checksum (CS) value calculated at the preceding element (Mi-1);
- rotating the bits of the second factor bits a predetermined number prior to calculating the sum.
2. A method as claimed in claim 1, c h a r a c t e r i z e d in that - the second factor is the previous value of the checksum (CS) as such, - the first factor is formed by rotating the bits of the element (Mi) k bits to the right (in the direction of the least significant bit), where k= in which INT denotes an integer, holds true for the number k of the rotations.
3. A method as claimed in claim 1, c h a r a c t e r i z e d in that in the method:
- the first factor is the element (Mi) as such; and - the second factor is formed by rotating the previous value of the checksum (CS) by determining, at every M's integer power Mn for which 0<Mn<i+1 holds true, whether the element's (Mi) index incremented by one (i+1) is divisible by the M's integer power Mn in question; and -- in response to the element (Mi) index incremented by one (i+1) being divisible by the M's integer power Mn in question, rotating the checksum (CS) one bit to the left; and -- once all the memory elements (Mi) of the storage area (MA) have been gone through, rotating the checksum (CS) to the right as many times as it was in all rotated to the left during calculating the checksum (CS).
4. A method as claimed in claim 1 for updating the checksum (CS) upon changes in the element (Mi) of the storage area (MA), c h a r a c t e r i z e d by the method comprising the steps of:
- summing the new data of the changed element (Mj) bitwise to the old data of the same element (Mi);
- deducting, on the basis of the index (i) in the changed element (Mi), how many rotations in all were made at this element (Mi) when calculating the original checksum (CS);
- rotating the checksum to the right for as many bits as it was rotated to the left at this element (Mi) when calculating the original checksum;
- summing the rotated checksum (CS) thus obtained to the original checksum (CS).
5. A method as claimed in any one of the previous claims, c h a r a c t e r i z e d in that the method further comprises the steps of:
- calculating a checksum (CS) over at least one storage area;
- comparing the checksum (CS) calculated over the storage area (MA) in question to a checksum calculated over the same storage area (MA) at an earlier stage;
- in response to a mismatch between the checksums calculated at different times over the same storage area (MA), generating a signal indicating this difference.
6. A method as claimed in claim 5, c h a r a c t e r i z e d in that the checksum calculated over the storage area (MA) in question is compared periodically at predetermined times to a checksum (CS) calculated at an earlier stage over the same storage area (MA).
7. A method as claimed in any one of the previous claims, c h a r a c t e r i z e d in that, to speed up the restart of a computer comprising a disk drive, the method comprises the steps of:
- calculating a checksum (CS) over at least one storage area;
- restarting the computer;
- calculating a checksum (CS) over at least one of such storage areas (MA) over which a checksum (CS) has been calculated prior to the restart;
- comparing the checksum (CS) calculated after the restart to a checksum (CS) calculated over the same storage area (MA) prior to the restart;
- in response to a mismatch between the checksum calculated after the restart and the checksum calculated prior to the restart, loading the data corresponding to the storage area in question from the disk drive.
8. A method as claimed in claim 7, c h a r a c t e r i z e d in that the value of the checksum (CS) calculated prior to the restart is stored in a main storage.
9. A method as claimed in claim 8, c h a r a c t e r i z e d in that the value of the checksum (CS) calculated prior to the restart is stored in a write-protected main storage.
10. A method as claimed in claim 7, c h a r a c t e r i z e d in that the value of the checksum (CS) calculated prior to the restart is stored on a hard disk.
CA 2236114 1995-10-30 1996-10-29 Detecting memory problems in computers Abandoned CA2236114A1 (en)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
FI955187 1995-10-30
FI955187A FI102221B (en) 1995-10-30 1995-10-30 Detection of memory problems in a computer
PCT/FI1996/000572 WO1997016786A1 (en) 1995-10-30 1996-10-29 Detecting memory problems in computers

Publications (1)

Publication Number Publication Date
CA2236114A1 true CA2236114A1 (en) 1997-05-09

Family

ID=29404102

Family Applications (1)

Application Number Title Priority Date Filing Date
CA 2236114 Abandoned CA2236114A1 (en) 1995-10-30 1996-10-29 Detecting memory problems in computers

Country Status (1)

Country Link
CA (1) CA2236114A1 (en)

Similar Documents

Publication Publication Date Title
US8145961B2 (en) Fast ECC memory testing by software including ECC check byte
CA1284228C (en) Byte write error code method and apparatus
CA2044441C (en) Semiconductor storage system
US5166936A (en) Automatic hard disk bad sector remapping
CN102981927B (en) Distributed raid-array storage means and distributed cluster storage system
AU713281B2 (en) Detecting memory problems in computers
US8468422B2 (en) Prediction and prevention of uncorrectable memory errors
US7793166B2 (en) Methods and systems for recovering meta-data in a cache memory after a corruption event
US20020169995A1 (en) System, method, and computer program for selectable or programmable data consistency checking methodology
CN110413439B (en) Method, apparatus and computer readable medium for detecting incomplete writing of data
KR20040017276A (en) Non-volatile memory and non-volatile memory data rewriting method
JP2000510273A (en) Validation system for maintaining parity integrity in disk arrays
US6349359B1 (en) Method and apparatus for maintaining data consistency in raid
EP0448970A2 (en) An information processing device having an error check and correction circuit
EP0969378A2 (en) Data storage, data processing system and method
US7549112B2 (en) Unique response for puncture drive media error
US6363457B1 (en) Method and system for non-disruptive addition and deletion of logical devices
CN114860745B (en) Database expansion method based on artificial intelligence and related equipment
JP2005004753A (en) Method and device of performing data version checking
US7577804B2 (en) Detecting data integrity
US20230236930A1 (en) Crc raid recovery from hard failure in memory systems
CA2236114A1 (en) Detecting memory problems in computers
US20030081468A1 (en) Method and device for backing up data in a memory module and memory module
US11150988B1 (en) Metadata pattern to detect write loss/inconsistencies of optimized-write-once operations
JP3022688B2 (en) Auxiliary storage

Legal Events

Date Code Title Description
EEER Examination request
FZDE Dead