Hi Takashi, On Wed, Feb 21, 2024 at 4:21 AM Takashi Iwai <tiwai@xxxxxxx> wrote: > > Both look like the code path via async PM resume. > Were both from the runtime PM resume? Or the system resume? The large firmware allocation that triggers the stall happens in runtime resume. This means runtime resume and system resume are affected. Due to the way runtime PM works, the system suspend path is also affected. Because system suspend first wakes up any runtime suspended devices, before executing their system suspend callback. So we get: system active, SOF runtime suspended (audio not active) -> system suspend request -> calls SOF runtime resume callback (stall happens here) -> calls SOF system suspend callback
- References:
- [PATCH v1] ALSA: memalloc: Fix indefinite hang in non-iommu case
- From: Karthikeyan Ramasubramanian
- Stall at page allocations with __GFP_RETRY_MAYFAIL (Re: [PATCH v1] ALSA: memalloc: Fix indefinite hang in non-iommu case)
- From: Takashi Iwai
- Re: Stall at page allocations with __GFP_RETRY_MAYFAIL (Re: [PATCH v1] ALSA: memalloc: Fix indefinite hang in non-iommu case)
- From: Vlastimil Babka
- Re: Stall at page allocations with __GFP_RETRY_MAYFAIL (Re: [PATCH v1] ALSA: memalloc: Fix indefinite hang in non-iommu case)
- From: Sven van Ashbrook
- Re: Stall at page allocations with __GFP_RETRY_MAYFAIL (Re: [PATCH v1] ALSA: memalloc: Fix indefinite hang in non-iommu case)
- From: Takashi Iwai
- [PATCH v1] ALSA: memalloc: Fix indefinite hang in non-iommu case
- Prev by Date: [PATCH 6/6] ASoC: codecs: rt5660: Simplify mclk initialization
- Next by Date: Re: Stall at page allocations with __GFP_RETRY_MAYFAIL (Re: [PATCH v1] ALSA: memalloc: Fix indefinite hang in non-iommu case)
- Previous by thread: Re: Stall at page allocations with __GFP_RETRY_MAYFAIL (Re: [PATCH v1] ALSA: memalloc: Fix indefinite hang in non-iommu case)
- Next by thread: Re: Stall at page allocations with __GFP_RETRY_MAYFAIL (Re: [PATCH v1] ALSA: memalloc: Fix indefinite hang in non-iommu case)
- Index(es):