On Mon, Oct 09, 2017 at 09:36:56AM +0100, Mark Brown wrote:
>On Sat, Oct 07, 2017 at 10:36:55PM +, Levin, Alexander (Sasha Levin) wrote:
>> From: Matt Ranostay
>>
>> [ Upstream commit 9834ffd1ecc3a401d0ce64c2d4235a726da6d4f9 ]
>>
>> We can get audio errors if hitting
On Mon, Oct 09, 2017 at 09:36:56AM +0100, Mark Brown wrote:
>On Sat, Oct 07, 2017 at 10:36:55PM +, Levin, Alexander (Sasha Levin) wrote:
>> From: Matt Ranostay
>>
>> [ Upstream commit 9834ffd1ecc3a401d0ce64c2d4235a726da6d4f9 ]
>>
>> We can get audio errors if hitting deeper idle states on
On Sat, Oct 07, 2017 at 10:36:55PM +, Levin, Alexander (Sasha Levin) wrote:
> From: Matt Ranostay
>
> [ Upstream commit 9834ffd1ecc3a401d0ce64c2d4235a726da6d4f9 ]
>
> We can get audio errors if hitting deeper idle states on omaps:
>
> [alsa.c:230] error: Fatal
On Sat, Oct 07, 2017 at 10:36:55PM +, Levin, Alexander (Sasha Levin) wrote:
> From: Matt Ranostay
>
> [ Upstream commit 9834ffd1ecc3a401d0ce64c2d4235a726da6d4f9 ]
>
> We can get audio errors if hitting deeper idle states on omaps:
>
> [alsa.c:230] error: Fatal problem with alsa output,
From: Matt Ranostay
[ Upstream commit 9834ffd1ecc3a401d0ce64c2d4235a726da6d4f9 ]
We can get audio errors if hitting deeper idle states on omaps:
[alsa.c:230] error: Fatal problem with alsa output, error -5.
[audio.c:614] error: Error in writing audio (Input/output
From: Matt Ranostay
[ Upstream commit 9834ffd1ecc3a401d0ce64c2d4235a726da6d4f9 ]
We can get audio errors if hitting deeper idle states on omaps:
[alsa.c:230] error: Fatal problem with alsa output, error -5.
[audio.c:614] error: Error in writing audio (Input/output error?)!
This seems to
6 matches
Mail list logo