Abstract: Systems, apparatuses and methods may provide for technology that identifies a sequence of events associated with a computer architecture, categorizes, with a natural language processing system, the sequence of events into a sequence of words, identifying an anomaly based on the sequence of words and triggering an automatic remediation process in response to an identification of the anomaly.

Abstract: An integrated circuit (IC) power-up testing method, an IC power-up testing device, a storage medium and an electronic equipment are disclosed. The IC power-up testing method includes: obtaining power-up testing parameters for an IC; obtaining a plurality of power-up testing waveforms; generating a plurality of power-up test instances by conducting parameter assignments for the power-up testing waveforms based on the power-up testing parameters; and performing power-up tests on the IC using the plurality of power-up test instances. The method allows simulating various IC power-up scenarios through a plurality of power-up test instances.

Abstract: Embodiments herein provide a method for controlling operations of a Redundant Array of Independent Disks (RAID) data storage system comprising a host device and a plurality of solid-state drives (SSDs). The method includes performing, by the at least one SSD, recovery of lost data by performing the auto-rebuild operation. The method also includes performing by the at least one SSD, the auto-error correction operation based on the IO error. The method also includes creating a snapshot of an address mapping table by all SSDs of the plurality of SSDs in the RAID data storage system. The auto-rebuild operation, the auto-error correction operation and the creation the snapshot of the address mapping table are all performed without the intervention from the host device.

Abstract: Methods, systems, and apparatus, including computer-readable storage media for uncorrectable memory recovery. Different sources of uncorrectable memory error are handled to provide for recovery actions by a host kernel of a machine hosting one or more virtual machines. Rather than defaulting to kernel panic behavior, the host kernel can identify the source of uncorrectable error, and cause the host machine and/or the affected virtual machines to take recovery action that is less disruptive than abrupt shutdown from panic. For example, the host kernel can handle uncorrectable memory error caused by kernel accesses to guest memory of a host virtual machine, as well as uncorrectable memory error improperly raised as a result of known defects in host machine hardware. The host kernel can also be configured to detect sources of overflow in exceptions raised by a processor as a result of uncorrectable memory error.

Abstract: A crash analysis system for identifying the cause of application crashes. The crash analysis system generates mapped stack traces that combine code version history data with logging information. The mapped stack traces are used to identify the causal stack frame which includes the function that caused the application crash. The crash analysis system also identifies the author of the function that caused the application crash and distributes a notification to the author that prompts the author to develop a fix that resolves the application crash.

Abstract: A method and system may reconstruct data in a smart storage array where upon detection of data inconsistency, an application of the system is notified and affected data strips are rebuilt. When an initiator detects stripe corruption, the initiator may report the strip corruption to storage. The storage may lock the strip for I/O operations. Initiators may determine recovery scenarios for rebuilding the data strips and send the scenarios to storage. At storage, initiator replies may be collected, and a rebuild option with the highest votes may be automatically determined for a reconstruction operation. Once the reconstruction operation is completed, the rebuilt stripe may be unlocked and data operations may recommence.

Abstract: Disclosed herein are system, method, and computer program product embodiments for transitioning virtual systems from one run-level to a next run-level. In an embodiment, a controller may receive a run-level request to transition a computing cluster (e.g., vSystem) from a first run-level to a second run-level. The controller persists a current run-level of the computing cluster as the second run-level in a configuration file. The controller executes a set of actions corresponding to the second run-level to transition the computing cluster from the first run-level to the second-level. A gateway of the computing cluster receives a request to access the computing cluster. The request includes a user's authentication details. The gateway grants or restricts access to the computing cluster based on the type of user attempting to access the computing cluster and the current run-level of the computing cluster as indicated in the configuration file.

Abstract: An embedded control system for a field device of an automation system includes: a diagnostic application interface to a backend server for signal analytics information, complex event pattern information, and diagnostic information; a physical process interface to a signal source for transferring signal data; a signal evaluation component for comparing received signal analytics information with received signal data to identify a first and a second event; an event processing component for applying received event pattern information to the first and second identified events to identify a first classified event; and a diagnostic reasoning component for deriving causal dependencies between the first classified event and a further classified event with regard to diagnostic information to identify a root cause for the first classified event or predict an impact of the first classified event.

Abstract: Disclosed herein are log information collection methods for collecting log information of a network device operating in accordance with instructions from an operation apparatus. In some cases, the log information collection method can comprise: determining whether another piece of the log information including a second character string occurs in a predetermined duration, wherein the niece of log, information includes a first character string; generating a new piece of log information including a third character string; and accepting specifications of the first, second, and third character strings, the predetermined duration, and occurrence or non-occurrence of the piece of the log information and the other piece of the log information.

Abstract: A method for determining an estimated duration before a technical incident in a computing infrastructure, executed by a computing device. The computing device including a data processing module, a storage module that stores in memory at least one correlation base between performance indicators, wherein the correlation base includes values of duration before becoming anomalous between correlated performance indicators, and a collection module. The method includes receiving performance indicator values, identifying anomalous performance indicators, identifying first and other at-risk indicators. The method includes determining an estimated duration before a technical incident including a calculation, from the anomalous indicators and at-risk indicators, a shorter path leading to a risk of technical incident, and a calculation of an estimated duration before a technical incident.

Abstract: The controlling apparatus for an industrial product of this disclosure has a couple of microcomputers each of which has a CPU and a memory and each of which runs the same controlling program as well as the same diagnostic program sequence parallelly and simultaneously. After the CPU of the microcomputer writes the calculated result of the diagnostic program sequence in the predetermined area of the storing area for monitoring value, such CPU send the same calculated result to the other one of the microcomputers (receiving microcomputer). The CPU of the receiving microcomputer makes a diagnosis for finding whether or not the received result is identical with its own calculated result.

Abstract: A system and method for to modify a setup to allow a restart despite a faulty hardware component is disclosed. The system includes a management controller storing a system error log. The computer system includes hardware components in communication with the management controller. A basic input output system (BIOS) includes a start-up routine that successfully completes if all of the hardware components are functional. The start-up routine determines an error in one of the hardware components from the system error log. The routine disables the hardware component. The routine then completes a power-on self-test routine.

Abstract: Methods, systems, and devices for detecting page fault traffic are described. A memory device may execute a self-learning algorithm to determine a priority size for read requests, such as a maximum readahead window size or other size related to page faults in a memory system. The memory device may determine the priority size based at least in part on by tracking how many read requests are received for different sizes of sets of data. Once the priority size is determined, the memory device may detect subsequent read requests for sets of data having the priority size, and the memory device may prioritize or other optimize the execution of such read requests.

Abstract: When the inspection unit corresponding to at least one disabled layer of a multilayer system is unavailable, a fault-eliminating device defines the at least one disabled layer and a target layer as a combined layer. The fault dependency of the target layer is the lowest among the fault dependency of the at least one available layer. The inspection unit of the at least one available layer is active and the fault dependency thereof is higher than the disabled layer. Then, the device makes the inspection unit and the fault symptom corresponding to the target layer correspond to the combined layer, so as to update a list of layers and a fault model. After that, the device determines a source of a fault from the layers according to the list of layers and the fault model, and performs a strategy of fault elimination corresponding to the source, to eliminate the fault.

Abstract: An approach for distributed tracing is provided. The approach for distributed tracing comprises receiving a user request for a transaction by one or more processing units, and extracting feature data from the received user request by one or more processing units. Further, if the extracted feature data matches at least one policy generated based on at least one error response received from at least one service is determined by one or more processing units and the at least one service is instructed to collect tracing data for the transaction in a head-based fashion responsive to the extracted feature data matching at least one policy by one or more processing units.

Abstract: Described are techniques for predicting gradual performance degradation with non-linear characteristics. The techniques including a method comprising inputting a new data sample to a failure prediction model, wherein the failure prediction model is trained using a labeled historical dataset, wherein respective data points are associated with a look-back window and a prediction horizon to create respective training samples, wherein the respective training samples are clustered in a plurality of clusters, and wherein the plurality of clusters are each associated with a normalcy score and an anomaly score. The method further comprises outputting a classification associated with the new data sample based on comparing a first anomaly score of a first cluster of the plurality of clusters that includes the new data sample to an average anomaly score of clusters of the plurality of clusters having the normalcy score greater than the anomaly score.

Abstract: Pattern recognition is used to proactively treat defects of repeating circuit topologies. A component of a computing environment is monitored for failures. The component includes one or more repeating circuit topologies. A determination is made as to whether a new failure within a repeating circuit topology of the one or more repeating circuit topologies has occurred within a predefined amount of time from a previous failure matching a selected pattern, in which the selected pattern indicates a non-contiguous growing defect. Based on determining the new failure has occurred within the predefined amount of time from the previous failure matching the selected pattern, corrective action for the component is proactively taken.

Abstract: A system for detecting power failure in a dual processing system includes a first central processing unit (CPU), a second CPU, a power controlling unit, and a complex programmable logic device (CPLD). The power controlling unit is electrically coupled to the first CPU and the second CPU and the CPLD. The CPLD can determine a power failure occurring in relation to the first CPU and the second CPU. If power to the first CPU does not fail but power to the second CPU does fail, the CPLD controls the power controlling unit to stop supplying power for the second CPU only and make a certain number of power restart attempts. A method for detecting a power failure is also provided.

Abstract: A system and method for providing multiple options for booting-up a remote computing device is disclosed. The system has a remote management station, in network communication with a computing device. The computing device has hardware components and a Unified Extensible Firmware Interface (UEFI) basic input output system (BIOS), including multiple power-on self-test (POST) routines. A controller is in communication with the UEFI BIOS and in network communication with the remote management station. The controller receives a selection of one of the plurality of POST routines from the management station. The controller boots up the computing device with the selected POST routine. The POST routines include a normal POST and other specialized routines such as a fast boot option, a safety boot option, a diagnostic boot option and a factory boot option.

Abstract: Embodiments provide a recovery method for a terminal device startup failure and a terminal device. The method includes: determining that a failure indication event occurs in a startup process, where the failure indication event is used to indicate a startup failure; determining at least one recovery policy based on a type of the failure indication event and/or a cause of the failure indication event; and performing startup recovery based on the at least one recovery policy.