Sadly, I don't have time to dig through pages of posts to find one line of information. Can you give specific instructions on what you do to make this go wrong, and any errors that may be display (e.g. syslogs). Since this does NOT appear to be the tcp segmentation offload issue (although symptoms appear the same - welcome to the wonderful world of ethernet bugs), it would be worth adding a very detailed issue in github (if you haven't already done so) which is the official way of reporting bugs, it also means they do not get lost. Post a link here to the github issue to cross reference.wybielacz wrote: ↑Sun Jun 17, 2018 4:01 pmjamesh wrote: ↑Sun Jun 17, 2018 2:49 pmSometimes, bugs are just REALLY difficult to fix. Simply as that. I have a laptop with a Intel Wireless chip in. It took Intel (Yes Intel, with all their thousands of engineers), 18 MONTHS to get that wireless chip driver stable, and tbh, I still don;t think it's particular good.Since the 3B+ was launched we have had to deal with some really quite complex issues, most of which were caused by other peoples chips and software, none of which came up in pre release testing. Annoying, but not uncommon with a new release.
I believe your fault is not the one mainly being talked about in this thread, but possibly related the network driver TCP segmentation offload issue. Have you tried turning that off (as described in the ethernet/NTFS problems thread)?
Yes, i did. I already wrote that on the previous page.
Ethernet is always killing my 3B+ when i mount a network drive, the commands didn't help. WiFi works fine and the 3B+ runs stable without any crashes, but i bought the 3B+ specially because of the faster ethernet so this is not acceptable for me...
In the meantime, does forcing it to 100bT make the problem go away (yes, I know you want Gig ethernet, this is for testing purposes to narrow down the issue)