Posts: 168
Joined: Sep 2013
2017-09-10, 21:07
(This post was last modified: 2017-09-10, 21:20 by User 182116.)
(2017-09-10, 19:21)Milhouse Wrote: (2017-09-10, 10:54)Bluesmanuk Wrote: Where is the best place to report what, on the surface appears to be an Alsa audio broken pipe issue with kernel 4.13?
Here. Post debug log (wiki) and "journalctl -a" (use a pastebin site). Explain how to reproduce. Provide sample files if necessary.
I previously posted in Post: #1675 and updated debug log as I tried new versions.
I'm afraid that I have no idea how to post journalctl -a and a Google search made me none the wiser.
Happens with any file at all, regardless of formats and I tried many.
The lack of sound also applies to the UI system sounds.
Posts: 32
Joined: Sep 2017
Reputation:
0
@Milhouse: Couldn't try builds #0908z and #0909 earlier but starting with #0908z, everything is working as it should. thanks for that.
Another question. It's nothing serious but I'd like to understand why this happens.
Usually when I turn off my HTPC it took about 2-4 seconds and it was off.
Now with every of these alpha builds it takes between 10-15 seconds.
Is that because of all the logging?
Like I said, nothing serious. I'm just curious about the cause.
Posts: 168
Joined: Sep 2013
(2017-09-10, 22:03)Milhouse Wrote: (2017-09-10, 21:07)Bluesmanuk Wrote: I'm afraid that I have no idea how to post journalctl -a and a Google search made me none the wiser.
Log in with ssh, run "journalctl -a | pastebinit" and post the url.
If it started with with #0904 then most likely it's a kernel issue with 4.13.0. Unfortunately your Z8350 has always had a chequered support history with Linux (blame Intel) - maybe something has broken in the new kernel. There's a 4.13.1 release (probably in tomorrow's build), but I'm not seeing anything specific to this CPU or Alsa.
Thanks.
Journalctl
Everything works well with #0903, so if there is no possible fix for a while or at all then I'm still fully functional for my needs.
Posts: 168
Joined: Sep 2013
2017-09-10, 23:52
(This post was last modified: 2017-09-11, 00:00 by User 182116.)
(2017-09-10, 23:37)Milhouse Wrote: (2017-09-10, 23:17)Bluesmanuk Wrote: Journalctl
Sorry, I should have said I need the "journalctl -a" from a non-working build once the problem has occurred - looks like the above log is from #0903 with 4.12.10.
Of course yes.
My fault.
Journalctl #0910
Posts: 17,855
Joined: Jan 2011
Reputation:
1,055
Milhouse
Retired Team-Kodi Member
Posts: 17,855
@Bluesmanuk can you confirm if you have this "broken pipe" issue with #0910 when playing the same files from a local disk, or over nfs://?
Texture Cache Maintenance Utility: Preload your texture cache for optimal UI performance. Remotely manage media libraries. Purge unused artwork to free up space. Find missing media. Configurable QA check to highlight metadata issues. Aid in diagnosis of library and cache related problems.
Posts: 168
Joined: Sep 2013
(2017-09-11, 01:02)Milhouse Wrote: @Bluesmanuk can you confirm if you have this "broken pipe" issue with #0910 when playing the same files from a local disk, or over nfs://?
I don't use NFS but yes the issue is present whether playing files from local storage or from my NAS.
Posts: 168
Joined: Sep 2013
(2017-09-11, 02:41)Milhouse Wrote: (2017-09-11, 01:25)Bluesmanuk Wrote: I don't use NFS but yes the issue is present whether playing files from local storage or from my NAS.
Can you try #0910z: Generic
This disables ES8316 support for Intel Baytrail/Cherrytrail, which is new in 4.13.
Thank you.
Still the same I'm afraid.
Took the 2 logs again in case they are of any benefit.
Debug #0910z
Journalctl
Posts: 168
Joined: Sep 2013
(2017-09-11, 04:22)Milhouse Wrote: (2017-09-11, 04:06)Bluesmanuk Wrote: Still the same I'm afraid.
Took the 2 logs again in case they are of any benefit.
Debug #0910z
Journalctl
Thanks, that's unfortunate - not really sure what else could be the problem, other than it being some sort of ALSA issue. You could try testing the 8 releases that were tested during the 4.13 release cycle, just to narrow it down to a specific release candidate.
Unfortunately your latest two logs don't appear to show the problem - I don't see any attempt at playback.
I will try out those test releases and report back any success.
Thank you very much for looking at it, it's much appreciated.