From: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org, Harald Arnesen <harald@skogtun.org>,
Alex Xu <alex_y_xu@yahoo.ca>
Subject: Re: Intel HD Audio: sound stops working in Xen PV dom0 in >=5.17
Date: Tue, 20 Dec 2022 05:43:01 +0100 [thread overview]
Message-ID: <Y6E9VixS7sV0kpWQ@mail-itl> (raw)
In-Reply-To: <Y5SxJ3IkhHSC/Psu@mail-itl>
[-- Attachment #1: Type: text/plain, Size: 2759 bytes --]
On Sat, Dec 10, 2022 at 05:17:42PM +0100, Marek Marczykowski-Górecki wrote:
> On Sat, Dec 10, 2022 at 02:00:06AM +0100, Marek Marczykowski-Górecki wrote:
> > On Fri, Dec 09, 2022 at 01:40:15PM +0100, Marek Marczykowski-Górecki wrote:
> > > On Fri, Dec 09, 2022 at 09:10:19AM +0100, Takashi Iwai wrote:
> > > > On Fri, 09 Dec 2022 02:27:30 +0100,
> > > > Marek Marczykowski-Górecki wrote:
> > > > >
> > > > > Hi,
> > > > >
> > > > > Under Xen PV dom0, with Linux >= 5.17, sound stops working after few
> > > > > hours. pavucontrol still shows meter bars moving, but the speakers
> > > > > remain silent. At least on some occasions I see the following message in
> > > > > dmesg:
> > > > >
> > > > > [ 2142.484553] snd_hda_intel 0000:00:1f.3: Unstable LPIB (18144 >= 6396); disabling LPIB delay counting
> >
> > Hit the issue again, this message did not appear in the log (or at least
> > not yet).
> >
> > (...)
> >
> > > > In anyway, please check the behavior with 6.1-rc8 + the commit
> > > > cc26516374065a34e10c9a8bf3e940e42cd96e2a
> > > > ALSA: memalloc: Allocate more contiguous pages for fallback case
> > > > from for-next of my sound git tree (which will be in 6.2-rc1).
> >
> > This did not helped.
> >
> > > Looking at the mentioned commits, there is one specific aspect of Xen PV
> > > that may be relevant. It configures PAT differently than native Linux.
> > > Theoretically Linux adapts automatically and using proper API (like
> > > set_memory_wc()) should just work, but at least for i915 driver it
> > > causes issues (not fully tracked down yet). Details about that bug
> > > report include some more background:
> > > https://lore.kernel.org/intel-gfx/Y5Hst0bCxQDTN7lK@mail-itl/
> > >
> > > Anyway, I have tested it on a Xen modified to setup PAT the same way as
> > > native Linux and the audio issue is still there.
> > >
> > > > If the problem persists, another thing to check is the hack below
> > > > works.
> >
> > Trying this one now.
>
> And this one didn't either :/
>
> When it stopped working, I did two things:
> 1. switched audio profiles ("configuration" tab in pavucontrol) several
> times; this on its own did not helped
> 2. reloaded sound related modules, but did not loaded them all back (see
> attached list before and after).
>
> After this, it worked again for a few minutes. Not sure if/which the above
> actions were relevant, tho...
>
> Another observation: when it stops working, it's never during a
> playback. It's always that at some point starting an audio stream
> results in a silence.
Any other ideas? Or maybe there is another patch I should try?
--
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-12-20 4:44 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Y5KPAs6f7S2dEoxR@mail-itl>
2022-12-09 8:10 ` Intel HD Audio: sound stops working in Xen PV dom0 in >=5.17 Takashi Iwai
2022-12-09 12:40 ` Marek Marczykowski-Górecki
2022-12-10 1:00 ` Marek Marczykowski-Górecki
2022-12-10 16:17 ` Marek Marczykowski-Górecki
2022-12-20 4:43 ` Marek Marczykowski-Górecki [this message]
2022-12-22 8:09 ` Takashi Iwai
2022-12-27 15:26 ` Marek Marczykowski-Górecki
2023-01-16 15:55 ` Takashi Iwai
2023-01-17 7:58 ` Takashi Iwai
2023-01-17 11:36 ` Marek Marczykowski-Górecki
2023-01-17 14:21 ` Marek Marczykowski-Górecki
2023-01-17 14:33 ` Takashi Iwai
2023-01-17 16:49 ` Marek Marczykowski-Górecki
2023-01-17 16:52 ` Takashi Iwai
2023-01-17 20:34 ` Marek Marczykowski-Górecki
2023-01-18 8:59 ` Takashi Iwai
2023-01-18 10:39 ` Marek Marczykowski-Górecki
2023-01-18 12:39 ` Takashi Iwai
2023-01-20 1:10 ` Marek Marczykowski-Górecki
2023-01-20 2:24 ` Marek Marczykowski-Górecki
2023-01-20 7:26 ` Takashi Iwai
2023-01-20 12:11 ` Marek Marczykowski-Górecki
2023-01-20 13:19 ` Takashi Iwai
2023-01-23 21:31 ` Marek Marczykowski-Górecki
2023-01-24 9:24 ` Takashi Iwai
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y6E9VixS7sV0kpWQ@mail-itl \
--to=marmarek@invisiblethingslab.com \
--cc=alex_y_xu@yahoo.ca \
--cc=alsa-devel@alsa-project.org \
--cc=harald@skogtun.org \
--cc=tiwai@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox