-
Notifications
You must be signed in to change notification settings - Fork 130
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
oops, 5.17.0-rc8, sof-audio-pci-intel-cnl 0000:00:1f.3: error: memory alloc failed: -12 #3530
Comments
I have been seeing this too on my ThinkPad X1 Yoga (Gen 4). The NULL dereference is fixed by torvalds/linux@b7fb0ae, but even with that fix, sound still breaks and never recovers.
|
@andersk could you please share the full logs? It looks you have a memory allocation error and it will be good to see what lead to this. |
There is no way we can recover here if there's not enough memory. We should really look into why there's no memory left, that's puzzling given than audio uses very little memory compared to video or graphics. Either we have a memory leak on the audio side, or other systems use way too much. |
Here’s the kernel log from that boot, but there’s nothing in the five minutes before “error: memory alloc failed: -12”. I think it happened (in the host) when a virtual machine I’d booted in virt-manager tried to play a sound. |
Humm, this is not a random allocation failure but something that would happen when failing to allocate DMA pages. /* allocate DMA buffer */
ret = snd_dma_alloc_pages(SNDRV_DMA_TYPE_DEV_SG, &pci->dev, size, dmab);
if (ret < 0) {
dev_err(sdev->dev, "error: memory alloc failed: %d\n", ret);
goto out_put;
} /* prepare DMA for code loader stream */
hext_stream = hda_cl_stream_prepare(sdev, HDA_CL_STREAM_FORMAT,
stripped_firmware.size,
&dmab, SNDRV_PCM_STREAM_PLAYBACK);
if (IS_ERR(hext_stream)) {
dev_err(sdev->dev, "error: dma prepare for fw loading failed\n");
return PTR_ERR(hext_stream);
} |
@cmurf , can you check if 5.17.4 is fixing the issue? A fallback implementation of a memory allocator got backported which hopefully going to solve the issue. |
@ujfalusi can we close this? It's been a while since we've since this issue and the upstream fallback should address it. |
@plbossart, yes, we can close this. The fixes are in upstream and they are even backported to stable, afaik. |
This seems to be a one off, I haven't seen it before. I only noticed it because a VM that should be running got clobbered somehow.
full journal
journal.log
The text was updated successfully, but these errors were encountered: