mcoste wrote:
> Good idea. I just tested on a 1903 / 18362.1016 laptop, it hangs when
> using ethernet as well as wifi (whereas on my thinkpad it hangs with
> ethernet and plays fine with wifi).
>
> @Jophnal, @Arthur, are you guys using ethernet connections or WiFi? If
> you're using ethernet it may be interesting to test with wifi.
I use gigabit ethernet for the Netgear NAS (Debian) as server and 2
different W10 x64 clients (i3-530 hooked to my home theatre and Ryzen
1700x for PC listening while I work) both on 2004. Both have integrated
gigabit NICs. Both exhibit the same problem. -b 10000:10000 has
eliminated the problem for 99% of tracks with the odd podcast causing
issues due to larger file size.
I have a Squeezebox Duet connected via ethernet, SMSL Q5 AMP, 4-way
speaker splitter and in ceiling speakers - No issue with playing media.
So taking this all into account:
- 100% single thread usage in Squeezelite leading to a stream reset
- ralphy noting:
Code:
--------------------
[11:36:16.956] send_packet:108 failed writing to socket: Unknown error
[11:36:16.956] slimproto_run:572 error reading from socket: Unknown error
--------------------
- Both w10 clients Intel i3 ages old and relatively new B450 board
Ryzen 1700X exhibiting the problem
- Squeezebox duet is fine connected by ethernet
that there is an issue with Squeezelite interacting with windows
networking around closing a socket while there is data to still be
sent/received
This is beyond my ability to debug. Does anyone have the skills and time
- why the socket error "unknown error" occurs?
------------------------------------------------------------------------
Jophnal's Profile: http://forums.slimdevices.com/member.php?userid=70261
View this thread: http://forums.slimdevices.com/showthread.php?t=97046
_______________________________________________
unix mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/unix
