Browse Prior Art Database

DEVICE-DEDICATED FAULT BUFFERS BACKGROUND

IP.com Disclosure Number: IPCOM000008156D
Original Publication Date: 1997-Jun-01
Included in the Prior Art Database: 2002-May-22
Document File: 1 page(s) / 56K

Publishing Venue

Motorola

Related People

Yury Dubinsky: AUTHOR [+3]

Abstract

Currently, in SmartZone systems, all system faults are collected in a single buffer on a first-in, first-out basis (a queue). Since the buffer is limited to a finite size, this means that only the most recent faults are saved. This is done to avoid consuming too much disk space in the system. The problem is that if one device is generating most of the faults, devices that rarely produce faults are likely to have their fault information over-written in the buffer, thus causing their fault information to be "lost." In such a case, it is impossible to analyze the devices that infrequently fail.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 91% of the total text.

Page 1 of 1

@ MOTOROlA Technical Developments

DEVICE-DEDICATED FAULT BUFFERS

BACKGROUND

by Yury Dubinsky, Steve Schafer and Curt Danielsen

  Currently, in SmartZone systems, all system faults are collected in a single buffer on a first-in, first-out basis (a queue). Since the buffer is limited to a finite size, this means that only the most recent faults are saved. This is done to avoid consuming too much disk space in the system. The problem is that if one device is generating most of the faults, devices that rarely produce faults are likely to have their fault information over-written in the buffer, thus causing their fault information to be "lost." In such a case, it is impossible to analyze the devices that infrequently fail.

SOLUTION

  The solution is to create multiple buffers in soft- ware (on the disk) and to dedicate each buffer to one device, whether physical or logical, in the sys- tem. Buffers may be variously sized and objects may be grouped together, as necessary and appro- priate. This way, faults generated from each report- ing device are always stored and never over written by faults from another device.

SITES FAULT QUEUE

ZONE CONTROLLER FAULT QUEUE

AUDIO PATH FAULT QUEUE

Fig. 1 Fault Information Queue

PRIOR ART

  In the past, the system saved all fault informa- tion and periodically purged unnecessary data. This approach used excessive amounts of disk space, causing a degradation of disk and system perfor- mance. It was discontinued in favor of the afore- mention...