# US 2024/0004745 A1 · Pausing memory system based on critical event

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2024/0004745 A1
- Document ID: US20240004745A1
- Status: Published application
- Kind: A1
- Application number: 17/941,856
- Filed: 2022-09-09
- Published: 2024-01-04
- Earliest claimed: 2022-07-01
- Assignees: Micron Technology, Inc.
- Applicants: Micron Technology, Inc.
- Inventors: Noorshaheen Mavungal Noorudheen; Sudhakar Ravindra Parab; Sanjay Tanaji Shinde
- Web page: https://patentgrep.com/patent/US20240004745A1

## CPC

- G06F 11/0772: {Means for error signaling, e.g. using interrupts, exception flags, dedicated error registers}
- G06F 11/0727: {in a storage system, e.g. in a DASD or network based storage system (drivers for digital recording or reproducing units G06F3/06; circuits for error detection or correction within digital recording or reproducing units G11B20/18; for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS], H04L67/1097)}
- G06F 11/0751: {Error or fault detection not based on redundancy (power supply failures G06F1/30; network fault management H04L41/06)}
- G06F 11/076: {by exceeding a count or rate limit, e.g. word- or bit count limit}
- G06F 11/079: {Root cause analysis, i.e. error or fault diagnosis (in a hardware test environment G06F11/22; in a software test environment G06F11/36)}
- G06F 11/1032: {Simple parity}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Aspects of the present disclosure configure a system component, such as memory sub-system controller, to pause memory sub-system operations in response to a critical event. The memory sub-system controller can include a front-end (FE) device that stores critical event trigger data in trigger event logic registers. Upon detecting that operations of the memory sub-system, such as command latencies, correspond to the critical event trigger data, the FE device performs pause operations, including storing a state of the memory sub-system and transmitting an interrupt signal to the memory sub-system controller, such as a CPU, to initiate debugging operations.

## Claims

### Claim 1

A system comprising:
a memory sub-system comprising a front-end (FE) device and a set of memory components; and
a processing device, operatively coupled to the FE device and the set of memory components, the FE device configured to perform operations comprising:
receiving, from the processing device, critical event trigger data;
storing the critical event trigger data in one or more trigger event logic registers of the FE device;
determining that one or more operations of the memory sub-system correspond to the critical event trigger data; and
in response to determining that the one or more operations of the memory sub-system correspond to the critical event trigger data:
storing a state of the memory sub-system; and
transmitting an interrupt signal to the processing device to initiate debugging operations on the processing device, the interrupt signal comprising the state of the memory sub-system.

### Claim 2 (depends on 1)

The system of claim 1, wherein the state of the memory sub-system includes status of at least one of one or more data structures, one or more queues, or one or more state machines.

### Claim 3 (depends on 1)

The system of claim 1, wherein the critical event trigger data includes at least one of: Non-Volatile Memory Express (NVMe) command timeouts being triggered, Cyclic Redundancy Code (CRC) Errors exceeding a CRC threshold, PCIe AXI Error events, Uncorrectable Errors (UE) events, read or write completion latencies exceeding a read or write threshold, reset event information, or memory parity errors exceeding a parity threshold.

### Claim 4 (depends on 1)

The system of claim 1, the operations comprising pausing one or more components of the memory sub-system, including the FE device.

### Claim 5 (depends on 4)

The system of claim 4, the one or more components comprising a middle management logic (MML) device and a media controller (MC), the MML device being configured to receive commands from the FE device and transmit requests to the MC to perform the received commands.

### Claim 6 (depends on 5)

The system of claim 5, wherein the MML device comprises command identifier logic and the FE device comprises a command queue in which the commands are stored.

### Claim 7 (depends on 1)

The system of claim 1, wherein the critical event trigger data comprises first critical event trigger data, the operations comprising:
storing second critical event trigger data in one or more trigger event logic registers of the FE device before the first critical event trigger data is stored;
determining that a set of operations of the memory sub-system correspond to the second critical event trigger data; and
transmitting an indication to the processing device that set of operations of the memory sub-system correspond to the second critical event trigger data, wherein the processing device updates the one or more trigger event logic registers to store the first critical event trigger data in response to receiving the indication.

### Claim 8 (depends on 7)

The system of claim 7, wherein the first critical event trigger data is computed based on a value associated with the set of operations of the memory sub-system that correspond to the second critical event trigger data.

### Claim 9 (depends on 8)

The system of claim 8, wherein the value represents a data transfer timeout latency that exceeds a data transfer timeout threshold value.

### Claim 10 (depends on 7)

The system of claim 7, wherein the FE device comprises one or more debug registers, and wherein the processing device stores a value to assert an output of the one or more debug registers.

### Claim 11 (depends on 10)

The system of claim 10, wherein an output of the one or more debug registers is coupled to a first input of a NAND logic gate, and wherein a second input of the NAND logic gate is coupled to critical event trigger signal.

### Claim 12 (depends on 11)

The system of claim 11, wherein the critical event trigger signal is asserted in response to determining that the one or more operations of the memory sub-system correspond to the critical event trigger data.

### Claim 13 (depends on 12)

The system of claim 12, wherein an output of the NAND logic gate controls pause logic for storing the state of the memory sub-system.

### Claim 14 (depends on 1)

The system of claim 1, wherein the memory sub-system operates with a hardware accelerated data path while monitoring the one or more operations to determine whether the one or more operations correspond to the critical event trigger data.

### Claim 15

A method comprising:
receiving, from a processing device, critical event trigger data;
storing the critical event trigger data in one or more trigger event logic registers of a front-end (FE) device of a memory sub-system;
determining that one or more operations of the memory sub-system correspond to the critical event trigger data; and
in response to determining that the one or more operations of the memory sub-system correspond to the critical event trigger data:
storing a state of the memory sub-system; and
transmitting an interrupt signal to the processing device to initiate debugging operations on the processing device, the interrupt signal comprising the state of the memory sub-system.

### Claim 16 (depends on 15)

The method of claim 15, wherein the critical event trigger data includes at least one of Non-Volatile Memory Express (NVMe) command timeouts being triggered, Cyclic Redundancy Code (CRC) Errors exceeding a CRC threshold, PCIe AXI Error events, Uncorrectable Errors (UE) events, read or write completion latencies exceeding a read or write threshold, reset event information, or memory parity errors exceeding a parity threshold.

### Claim 17 (depends on 15)

The method of claim 15, further comprising pausing one or more components of the memory sub-system including the FE device.

### Claim 18 (depends on 17)

The method of claim 17, the one or more components comprising a middle management logic (MML) device and a media controller (MC), the MML device being configured to receive commands from the FE device and transmit requests to the MC to perform the received commands.

### Claim 19 (depends on 15)

The method of claim 15, wherein the critical event trigger data comprises first critical event trigger data, further comprising:
storing second critical event trigger data in one or more trigger event logic registers of the FE device before the first critical event trigger data is stored;
determining that a set of operations of the memory sub-system corresponds to the second critical event trigger data; and
transmitting an indication to the processing device that sets of operations of the memory sub-system correspond to the second critical event trigger data, wherein the processing device updates the one or more trigger event logic registers to store the first critical event trigger data in response to receiving the indication.

### Claim 20

A non-transitory computer-readable storage medium comprising instructions that, when executed by a processing device, cause the processing device to perform operations comprising:
receiving, from the processing device, critical event trigger data;
storing the critical event trigger data in one or more trigger event logic registers of a front-end (FE) device of a memory sub-system;
determining that one or more operations of the memory sub-system correspond to the critical event trigger data; and
in response to determining that the one or more operations of the memory sub-system correspond to the critical event trigger data:
storing a state of the memory sub-system; and
transmitting an interrupt signal to the processing device to initiate debugging operations on the processing device, the interrupt signal comprising the state of the memory sub-system.
