Method To Detect Firmware / Software Errors For Hardware Monitoring

• US 20120239981A1
• Filed: 03/15/2011
• Published: 09/20/2012
• Est. Priority Date: 03/15/2011
• Status: Abandoned Application

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Franke, Jeffrey Michael, Elles, Michael C., Dang, Tu To, Vignola, James A.
• Application Number:
  US13/047,917
• Publication Number:
  US 20120239981A1
• Time in Patent Office: Days
• US Class Current: 714/38.1
• CPC Class Codes: G06F 11/368 for test version control, e.g. updating test cases to a new software version

Abstract

Error reporting software-based method where an error list for a currently-running version of some target software (or firmware) is compared to an error list for a previous versions. Helpful information can be gleaned from the comparison of error lists. For example, if it is known that the hardware configuration has not changed, as between the two lists, and there is an error on the current list that does not appear on the previous list, then this indicates that the error is in the software update and is not a hardware problem.

Claims

1. A detection method controlled at least in part by error reporting software stored on a software storage device, the method comprising the steps of:

(i) providing a target non-hard-ware component having version N;

(ii) subsequent to step (i), running the version N target non-hard-ware on a set of target hardware and simultaneously detecting a first result list of active problems;

(iii) during and/or subsequent to step (ii), saving the first result list;

(iv) subsequent to step (ii), updating the non-hard-ware to a version N+1;

(v) subsequent to step (iv), running the version N+1 target non-hard-ware on the set of target hardware and simultaneously detecting a second result list of active problems;

(vi) during and/or subsequent to step (v), comparing the first result list and the second result list to obtain comparison-based information; and

(vii) during and/or subsequent to step (vi), outputting the comparison-based information.

2. The method of claim 1 further comprising the steps of:

(viii) prior to step (vi), determining that the hardware configuration of set of target hardware used during step (ii) is the same as the hardware configuration of set of target hardware used during step (v);

(ix) during step (vi), determining that a first error on the second result list is not present on the first result list; and

(x) subsequent to step (ix), classifying the first error as a probable non-hard-ware based error and including this classification in the comparison-based information.

3. The method of claim 2, further comprising the step of:

(xi) subsequent to step (vi), publishing problem(s) in the second result list, but not in the first result list, with respective workaround(s).

4. The method of claim 2, further comprising the step of:

(xi) subsequent to step (vi), generating a defect list for the next fix cycle.

5. The method of claim 2, further comprising the step of:

(xi) subsequent to step (vi), merging the first result list and the second result list to form a merged result list.

6. The method of claim 1 wherein the outputting of step (vii) includes presenting the comparison-based information in a human readable form.

7. The method of claim 1 wherein the outputting of step (vii) includes communicating the comparison-based information in a machine readable form.

8. The method of claim 1 further comprising the steps of:

(viii) prior to completing step (ii), determining that the version N target non-hard-ware has been stabilized; and

(ix) prior to completing step (v), determining that the version N+1 target non-hardware has been stabilized.

9. The method of claim 1 wherein the target non-hard-ware is firmware.

10. The method of claim 1 wherein the target non-hard-ware is software.

11. Error reporting software stored on a software storage device, the error reporting software being designed to report errors in at least versions N and N+1 of a target non-hard-ware as running on a set of target hardware, the software comprising:

an error detection module programmed to generate;

(i) a first result list of errors encountered when version N of the target software is running on the set of target hardware and (ii) a second result list of errors encountered when version N+1 of the target software is running on the set of target hardware;

an error list comparison module programmed to compare the first result list with the second result list to obtain comparison-based information; and

an error reporting module programmed to output the comparison-based information.

12. The software of claim 11 further comprising a hardware configuration change module programmed to determine whether the set of target hardware is changed in configuration between the generation of the first result list and the second result list, wherein the error list comparison module is further programmed to:

classify a first error as a probable non-hard-ware based error when the first error is on the second result list but not the first result list, and

include this classification in the comparison-based information.

13. The software of claim 12 wherein the error reporting module is further programmed to publish problem(s) in the second result list, but not in the first result list, with respective workaround(s).

14. The software of claim 12 wherein the error list comparison module is further programmed to generate a defect list for the next fix cycle.

15. The software of claim 12 wherein the error list comparison module is further programmed to merge the first result list and the second result list to form a merged result list.

16. A computer system comprising:

a processing hardware set;

a software storage device; and

error reporting software;

wherein;

the processing hardware set is structured, located, connected and/or programmed to run the error reporting software;

the software storage device is structured, located, connected and/or programmed to store the error reporting software; and

the error reporting software is designed to report errors in at least versions N and N+1 of a target non-hard-ware as running on a set of target hardware; and

the error reporting software comprises;

an error detection module programmed to generate;

(i) a first result list of errors encountered when version N of the target software is running on the set of target hardware and (ii) a second result list of errors encountered when version N+1 of the target software is running on the set of target hardware,

an error list comparison module programmed to compare the first result list with the second result list to obtain comparison-based information, and

an error reporting module programmed to output the comparison-based information.

17. The system of claim 16 wherein the computer system further comprises an in-band system.

18. The system of claim 16 wherein the computer system further comprises an out of band system

19. The system of claim 16 wherein the computer system further comprises a remote system

20. The system of claim 16 wherein the computer system further comprises a back office system.