JP2000035904A - Computer system and faulty log management method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To read the faulty log of a hardware stored by a dedicated memory device by a software and manage it. SOLUTION: A hardware event management program 301 periodically requests the acquisition of a new faulty log to a hardware event log access driver 302, and when the new faulty log is delivered, notifies a system management program 200 of the effect. Then, the delivered faulty log is registered to a log file 101 in common to the system provided in an operating system 100. Further, the hardware event management program 301 requests the batch elimination of the faulty log to the hardware event log access driver 302 in the case that the total capacity value of the faulty log stored in a hardware event log storage memory 17 delivered from the hardware event log access driver 302 exceeds a predetermined value.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a computer system for personal use such as a desktop type and a notebook type, and a fault log management method applied to the computer system.

[0002]

2. Description of the Related Art In recent years, the spread of computers to offices and homes has been rapidly progressing.
For example, various types of personal computers (personal computers) called desktop type or notebook type have been developed. Also, recently, when various devices (hardware) mounted on the system body cause some kind of failure, a computer system of this kind, for example, a system called a motherboard so that diagnosis can be appropriately performed. A dedicated memory device (hardware event log storage memory) for storing a failure log output from various devices has been provided as standard on a board.

The hardware event log storage memory is connected to one of the buses laid on the system board, and various devices mounted on the system main unit are used when a failure occurs. Outputs a fault log to the hardware event log storage memory on the bus.

Thus, for example, a customer engineer who has received a repair request refers to the failure log stored in the hardware event log storage memory, and
The situation can be accurately grasped, and appropriate measures can be easily taken.

[0005]

The reading of the fault log from the hardware event log storage memory is performed via a serial transmission line such as RS-232C derived from a connector provided in the computer body. Performed by external equipment. That is, there is no means for the computer system itself equipped with the hardware event log storage memory to read the fault log by software.

On the other hand, in this type of computer system, an operating system that controls the entire system often has a log function for recording events in the system in a log file. However, despite the existence of such a log function, there is no means for reading a failure log by software from the hardware event log storage memory, so that the error log cannot be reflected in the log file, and other events cannot be reflected. There was a problem that the same treatment could not be performed, that is, unified management could not be performed.

In many cases, an event monitoring system for monitoring an event in the system is operated to promptly notify a user when a failure occurs. However, the fact that a failure log has been stored in a hardware event log storage memory is often used. This event monitoring system could not be said to be functioning effectively for failures of various devices because it was not possible to recognize the event.

The present invention has been made in view of such circumstances, and a computer system and a failure log management method capable of reading and managing hardware failure logs stored in a dedicated memory device by software. The purpose is to provide.

[0009]

According to the present invention, in order to achieve the above-described object, a hardware event log storage memory for storing a fault log output from hardware mounted on a system body stores the fault log. The error log is read out by software, and the read out error log is registered in a log file managed by a log function provided in the operating system, for example.

In the present invention, since the fault log stored in the hardware event log storage memory is also recorded in the log file together with the log indicating other events, the centralized management of the log is realized, and the same level as other events is realized. It is possible to handle.

According to the present invention, when a new fault log is stored in a hardware event log storage memory for storing a fault log output from hardware mounted on the system body, the fact is detected by software. Then, an event monitoring system that monitors events in the system is notified.

According to the present invention, it is possible to promptly notify the user that the hardware has caused some trouble. It is preferable that the present invention further includes a unit for erasing the failure logs collectively when the number of the failure logs stored in the hardware event log storage memory exceeds a predetermined amount. This prevents a situation in which the latest failure log required for analysis cannot be stored and is lost.

[0013]

An embodiment of the present invention will be described below with reference to the drawings. FIG. 1 is a diagram illustrating a hardware configuration of a computer system according to an embodiment of the present invention. The computer system of this embodiment shown in FIG. 1 is a desktop type or notebook type personal computer, and a PCI bus 1 and an ISA bus 2 are provided on a system board thereof.

The computer system includes a CPU 11, a host-PCI bridge 12, a system memory 13, a display controller 14, and a PC.
I-ISA bridge 15, BIOS-ROM 16, hardware event log storage memory 17, magnetic disk drive (HDD) 18, and keyboard controller (KB)
C) 19 and the like are mounted. Devices other than the hardware event log storage memory 17 mounted in the computer system main unit output a failure log to the hardware event log storage memory 17 on the bus when any failure occurs in the device itself. I do.

The CPU 11 controls the execution of an operating system stored in the system memory 13 and application programs including utilities such as device drivers.

The host / PCI bridge 12 is connected to the CPU 1
1 connected to the processor local bus and the PCI bus 1
And functions as one of the bus masters of the PCI bus 1. The host / PCI bridge 12 also has a function of controlling access to the system memory 13 via a memory local bus.

The system memory 13 is a memory device that operates as a main memory of the computer system and stores an operating system executed and controlled by the CPU 11, application programs including utilities such as device drivers, processing data, and the like. DRAM module. The system memory 13 is connected to the host-PCI bridge 12 via a dedicated memory local bus.

The PCI bus 1 is a clock synchronous type input / output bus, and all the cycles on the PCI bus 1
This is performed in synchronization with the bus clock. The display controller 14 is a device that controls the output of the man-machine interface. The display controller 14 operates as one of the bus masters of the PCI bus 1 similarly to the host / PCI bridge device 12 and converts the image data of the video memory (VRAM) 141 into the LCD 142 or the like. Externally connected CRT display 14
3 and so on.

The PCI-ISA bridge 15 is a bridge LSI connecting between the PCI bus 1 and the ISA bus 2, and functions as one of the PCI devices. The PCI-ISA bridge 15 includes a PCI bus arbiter, a DMA controller, and the like.

The ISA bus 2 has a BIOS-R
OM 16, hardware event log storage memory 17,
A magnetic disk device (HDD) 18 and a keyboard controller (KBC) 19 are connected.

The BIOS-ROM 16 stores the system BIOS.
This is for storing S (Basic I / O System), and is constituted by a flash memory so that a program can be rewritten. The system BIOS includes an IRT routine executed at the time of system boot, a device driver for controlling various I / O devices, a system management program, a setup routine, and the like.

Hardware event log storage memory 17
Is a dedicated memory device for storing a failure log output from various devices mounted in the computer system body. A feature of the present invention resides in that the fault log stored in the hardware event log storage memory 17 can be read out and managed by software, which will be described later.

The magnetic disk device (HDD) 18 is a memory device that operates as an external storage of the computer system, and is a low-speed large-capacity memory device that exchanges data with the system memory 13.

The keyboard controller (KB)
C) 19 is a device that controls the input of the man-machine interface, stores control signals transmitted from a keyboard (KB) 191 and a mouse 192 in its own register, and controls the control signals in response to a request from the CPU 11. The signal is output on the ISA bus 2.

Next, a part of software operating on the computer system having such a hardware configuration will be described. FIG. 2 is a diagram showing a part of functional blocks of software operating on the computer system.

As shown in FIG. 2, in this computer system, an operating system 100 controls the entire system. The operating system 100 includes a log file 101 that stores a log that records events in the system. Then, under the control of the operating system 100, the system management program 200 and the hardware event management system 300 operate.

The system management program 200 is a program that is started immediately after the system boots and stays resident until the system is shut down, monitors events in the system, and notifies the user when any failure occurs. Generates a pop-up window and displays it. This system management program 2
Reference numeral 00 denotes an event-driven type so-called event monitoring system called a system monitor, for example.

Hardware event management system 300
The hardware event management program 301 includes a hardware event management program 301 and a hardware event log access driver 302.
1 repeats at predetermined intervals, ie,
Regularly hardware event log access driver 3
02 is requested to acquire a new failure log. On the other hand, the hardware event log access driver 302 requested to acquire a new failure log by the hardware event management program 301 checks whether a new failure log is stored in the hardware event log storage memory 17,
If a new failure log has been stored, the failure log is read and the hardware event management program 3
Hand over to 01. At this time, the hardware event log access driver 302 transfers the total capacity value of the fault log stored in the hardware event log storage memory 17 to the hardware event management program 301 together.

When a new fault log is delivered from the hardware event log access driver 302, the hardware event management program 301 first notifies the system management program 200 of the fact. Next, the hardware event management program 301
Is a hardware event log access driver 302
Is registered in the log file 101 included in the operating system 100.

At this time, the hardware event management program 301 determines that the total capacity of the fault log stored in the hardware event log storage memory 17 passed from the hardware event log access driver 302 is a predetermined value. The hardware event log access driver 302 requests the hardware event log access driver 302 to collectively clear the failure log.

Further, the hardware event management program 301, upon request, obtains all of the failure logs stored in the hardware event log storage memory 17 by the hardware event log access driver 30.
2 has a function of displaying a list of all the fault logs passed from the hardware event log access driver 302.

That is, when the hardware event management system 300 operates, in the computer system of this embodiment, when various devices generate a fault and output a fault log, the system management program 200 informs the system management program 200 accordingly. It is possible to promptly notify the user via the server, and by registering the failure log in the log file 101, centralized management of the log is realized, and the same handling as other events becomes possible. Further, since the capacity management of the hardware event log storage memory 17 is also executed, it is possible to prevent a situation in which the latest failure log required for analysis cannot be stored and is lost.

Thus, as in the prior art, for example, RS
There is no need to read a failure log from the hardware event log storage memory 17 by an external device via a serial transmission line such as H.232C, and the failure log can be easily referred to by software running on this computer system. It is possible to do.

FIG. 3 shows an example of a fault log stored in the hardware event log storage memory 17. As shown in FIG. 3, the failure log includes, for example, a system event log ID, an event type, an event occurrence time, an event occurrence position, an event format revision, a sensor type and number, and event detailed information. As the event occurrence position, any one of a system board (BIOS), a system board, and a housing is selected.

Next, the operation procedure of the computer system of this embodiment will be described with reference to FIG. FIG. 4 is a flowchart for explaining the operation procedure of the computer system of this embodiment.

The hardware event management program 30
1 requests the hardware event log access driver 302 to acquire a new failure log when a predetermined period has elapsed since the previous check (YES in step A1) (step A2).

Here, when a new fault log is delivered from the hardware event log access driver 302 (YES in step A3), the hardware event management program 301 first notifies the system management program 200 of the fact (step A3). Step A4). Next, the hardware event management program 301 registers the failure log passed from the hardware event log access driver 302 in the log file 101 provided in the operating system 100 (Step A5).

At this time, the hardware event management program 301 determines that the total capacity value of the fault log stored in the hardware event log storage memory 17 passed from the hardware event log access driver 302 is a predetermined value. Is determined (step A6), and if it has been exceeded (YE in step A6).
S), hardware event log access driver 30
2 is requested to collectively delete the failure log (step A7).

As described above, by reading out and managing the hardware failure log stored in the dedicated memory device by software, it is possible to more easily take appropriate measures.

[0040]

As described above in detail, according to the present invention, the fault log is read out from the hardware event log storage memory for storing the fault log output from the hardware mounted on the system body by the software. For example, by registering the read error log in a log file managed by the log function of the operating system, the error log stored in the hardware event log storage memory is also recorded in the log file along with logs indicating other events. Therefore, centralized management of logs is realized, and handling equivalent to other events is possible.

Further, when a new fault log is stored in a hardware event log storage memory for storing a fault log output from hardware mounted on the system body, the fact is detected by software and the system detects the new fault log. By notifying the event monitoring system that monitors the above event, it is possible to promptly notify the user that the hardware has caused some failure.

Further, when the number of fault logs stored in the hardware event log storage memory exceeds a predetermined amount, the fault logs are collectively erased, so that the latest fault required for analysis can be obtained. This prevents a situation in which a log cannot be stored and is lost.

[Brief description of the drawings]

FIG. 1 is an exemplary view showing a hardware configuration of a computer system according to an embodiment of the present invention.

FIG. 2 is an exemplary view showing a part of functional blocks of software operating on the computer system of the embodiment.

FIG. 3 is an exemplary view showing an example of a failure log stored in a hardware event log storage memory according to the embodiment.

FIG. 4 is an exemplary flowchart for explaining the operation procedure of the computer system of the embodiment.

[Explanation of symbols]

11 ... CPU, 12 ... Host-PCI bridge, 13 ...
System memory, 14 display controller, 1
5 PCI-ISA bridge, 16 BIOS-RO
M, 17: hardware event log storage memory, 18
... Magnetic disk device (HDD), 19 ... Keyboard controller (KBC), 100 ... Operating system, 101 ... Log file, 200 ... System management program, 300 ... Hardware event management system
301: hardware event management program, 302
… Hardware event log access driver.

Claims (5)

[Claims] 1. A computer system having a log function of recording events in a system in a log file, comprising: a failure log memory for storing a failure log output from various devices mounted on a system body; A computer system comprising: a failure log management unit that reads the failure log and registers the failure log in the log file. 2. A computer system in which an event monitoring system for monitoring an event in the system operates, wherein a fault log memory for storing a fault log output from various devices mounted on the system main body, and a new fault log memory. And a failure log management means for notifying the event management system when a failure log is stored. 3. The failure log management means includes means for deleting the failure logs collectively when the number of failure logs stored in the failure log memory exceeds a predetermined amount. 3. The computer system according to claim 1, wherein: 4. A fault log management system for a computer system having a log function for recording events in the system in a log file and a fault log memory for storing fault logs output from various devices mounted on the system body. A method of reading a fault log from the fault log memory and registering the log in the log file. 5. A fault log management method for a computer system, wherein an event monitoring system that monitors events in the system operates and includes a fault log memory that stores fault logs output from various devices mounted on the system body. When a new fault log is stored in the fault log memory, a notification to that effect is sent to the event management system.