G06F11/0784

UEFI EXTENSIONS FOR ANALYSIS AND REMEDIATION OF BIOS ISSUES IN AN INFORMATION HANDLING SYSTEM

A system and method for resolving (BIOS) firmware issues affecting one or more information handling systems, includes: responsive to receiving information indicative of the BIOS firmware issue, developing one or more executable scripts for resolving the BIOS firmware issue without modifying the BIOS firmware. The executable scripts include a first script for collecting data pertaining to the BIOS firmware issue, which is pushed to at least one affected information handling system. The first script includes processor-executable instructions that the affected information handling system executes in a pre-boot state to perform operations including establishing a secure and privileged pre-boot session, collecting data associated with the BIOS firmware issue from within the secure and privileged pre-boot session, and sending the data associated with the BIOS issue to a support resource.

AUTOMATIC SUPPORT SERVICE

A method of an automatic support service that includes receiving a request for additional assistance for an error from a user interface, retrieving error information from a logging system for the error, generating an error information collection interface, in response to the request, populating the error information collection interface with the error information from the logging system, sending the error information collection interface to be displayed to the user by the user interface, and receiving additional error information from the user via the error information collection interface.

Storage device failure policies

Example implementations relate to a failure policy. For example, in an implementation, storage device status data is encoded into storage device states. An action is chosen based on the storage device state according to a failure policy, where the failure policy prescribes, based on a probabilistic model, whether for a particular storage device state a corresponding action is to take no action or to initiate a failure mitigation procedure on a storage device. The failure policy is rewarded according to a timeliness of choosing to initiate the failure mitigation procedure relative to a failure of the storage device.

DATA LOGGER FOR PROCESSING LOGISTICS-RELATED INFORMATION AND COLD CONTAINER INCLUDING THE SAME

Provided is a data logger. A data logger includes a sensor configured to sense a change in a gravitational acceleration of the data logger and a change in a rotation angle of the data logger, and generate a sensing signal, a communication module configured to receive configuration information including a sensing period and threshold values of the data logger from a portable reader, and a microprocessor unit configured to receive the sensing signal from the sensor, receive the sensing period and the threshold values from the communication module, generate sensing values corresponding to the sensing signal, compare the sensing values with the threshold values, determine whether an abnormal state occurs in the data logger according to a result of the comparison, generate and transmit to a server normal log information at each of the sensing period when the abnormal state does not occur in the data logger, and generate and transmit to the server abnormal log information whenever the abnormal state occurs regardless of the sensing period.

METHOD OF PROVIDING LOGISTICS INFORMATION SERVICE USING DATA LOGGER FOR PROCESSING LOGISTICS-RELATED INFORMATION

Provided is a method of providing logistics information. A method of providing logistics information using a data logger equipped in a cold container for storing goods, a first portable reader, a second portable reader, and a server, including receiving, by the data logger, configuration information including a start time and a sensing period of the data logger, and threshold values of a gravitational acceleration and a rotation angle for the data logger from the first portable reader, starting, by the data logger, operation from the start time, comparing output values of a sensor of the data logger with the threshold values, and determining whether an abnormal state occurs in the data logger according to a result of the comparison, generating and transmitting to the server, by the data logger, normal log information at each of the sensing period when the abnormal state does not occur in the data logger, and generating and transmitting to the server, by the data logger, abnormal log information whenever the abnormal state occurs regardless of the sensing period.

Interface for memory readout from a memory component in the event of fault
11625346 · 2023-04-11 · ·

Memory controllers, devices, modules, systems and associated methods are disclosed. In one embodiment, an integrated circuit (IC) memory component is disclosed that includes a memory core, a primary interface, and a secondary interface. The primary interface includes data input/output (I/O) circuitry and control/address (C/A) input circuitry, and accesses the memory core during a normal mode of operation. The secondary interface accesses the memory core during a fault mode of operation.

Diagnostic scan

One embodiment provides a method, including: receiving, at an information handling device and in a pre-operating system (OS) environment, an indication to run a diagnostic application; conducting, using the diagnostic application, a diagnostic scan on one or more of the information handling device components; and generating, based on the diagnostic scan, a results report. Other aspects are described and claimed.

Software regression recovery via automated detection of problem change lists

Systems and methods for automatically recovering from software regression in a cloud computing environment. One example method includes determining, with an electronic processor, that a batch software update has been applied to the cloud computing environment. The method includes, in response to determining that a batch software update has been applied, transmitting a problem request to an event listener server. The method includes receiving, from the event listener server, a problem statement including a stack trace. The method includes determining, based on the stack trace, a software feature indicator. The method includes transmitting the software feature indicator to a root cause analyzer. The method includes receiving, from the root cause analyzer, a change list indicator and a relevancy score associated with the change list indicator. The method includes performing a mitigation action based on the change list indicator when the relevancy score exceeds a relevancy threshold.

System and method for self-healing of upgrade issues on a customer environment and synchronization with a production host environment

A method for managing applications includes obtaining, by a client in a customer environment, an upgrade issue report for the application, making a first determination that a resynchronization of a client self-healing classification model with the production host environment (PHE) self-healing classification model is required, wherein the PHE self-healing classification model is stored in the PHE, performing the resynchronization with the PHE self-healing classification model to obtain a synchronized client self-healing classification model, applying the synchronized client self-healing classification model to the upgrade issue report to obtain a state of the upgrade issue report, making a second determination that the state indicates a self-healable state, based on the second determination, performing a self-healing process on the application based on the upgrade issue report, and storing a resolution report based on results of the self-healing process, wherein the PHE is operatively connected to the customer environment.

HIGH AVAILABILITY MANAGEMENT FOR A HIERARCHY OF RESOURCES IN AN SDDC
20230109219 · 2023-04-06 ·

Some embodiments provide a hierarchical data service (HDS) that manages many resource clusters that are in a resource cluster hierarchy. In some embodiments, each resource cluster has its own cluster manager, and the cluster managers are in a cluster manager hierarchy that mimics the hierarchy of the resource clusters. In some embodiments, both the resource cluster hierarchy and the cluster manager hierarchy are tree structures, e.g., a directed acyclic graph (DAG) structure that has one root node with multiple other nodes in a hierarchy, with each other node having only one parent node and one or more possible child nodes.