Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

A macOS bug that causes TCP networking to stop working after 49.7 days

photon.codes

Post reply on HN
Print view View original

51–60 of 120 posts

Re: A macOS bug that causes TCP networking to stop working after 49.7 days

#52

Post by otherme123 »

auspiv wrote: post #28
loloquwowndueo wrote: post #2

lol reminds me of the windows 95 crash bug after 49.7 days. Have we learned nothing. https://pipiscrew.github.io/posts/why-window/

probably same thing for boeing 787 jets - https://www.theregister.com/2020/04/02/boeing_787_power_cycl... says 51 days, which would be an interesting number of (milli)seconds

It could be an overflow but related with the frequency at which the register was increasing, rather than the max value of te register. E.g. +1 this uint16 (65535) once every 500,000 cycles on this 32 Mhz chip, that previously was a 1 Mhz chip and never had a problem.

Re: A macOS bug that causes TCP networking to stop working after 49.7 days

#54

Post by Aloisius »

comex wrote: post #44
justinfrankel wrote: post #32

have multiple macOS machines with 600-1000+ day uptimes, which do TCP connections every minute or so at a minimum, they are still expiring their TIME_WAIT connections as normal. these kernel versions: Darwin Kernel Version 20.6.0: Thu Jul 6 22:12:47 PDT 2023; root:xnu-7195.141.49.702.12~1/RELEASE_ARM64_T8101 arm64 Darwin Kernel Version 17.7.0: Wed Apr 24 21:17:24 PDT 2019; root:xnu-4570.71.45~1/RELEASE_X86_64 x86_64…

The bug was introduced only last year in macOS 26: https://github.com/apple-oss-distributions/xnu/blame/f6217f8...

Interesting. The article mentions complaints on the forums running Catalina, so that must be something else.

Re: A macOS bug that causes TCP networking to stop working after 49.7 days

#55

Post by gowld »

tjohns wrote: post #31

Does anybody else find these AI-authored blog posts difficult to read? Something about the writing style and structure just feels unnatural, it's hard put my finger on it. At the very least, the writing takes way too long to get to a point.

AI does a good job of condensing the blog post to 2 paragraphs -- Mac refuses to let the tcp_now clock rollover when it exceeds the max value in its data type.

Re: A macOS bug that causes TCP networking to stop working after 49.7 days

#56

Post by plorkyeran »

comex wrote: post #44
justinfrankel wrote: post #32

have multiple macOS machines with 600-1000+ day uptimes, which do TCP connections every minute or so at a minimum, they are still expiring their TIME_WAIT connections as normal. these kernel versions: Darwin Kernel Version 20.6.0: Thu Jul 6 22:12:47 PDT 2023; root:xnu-7195.141.49.702.12~1/RELEASE_ARM64_T8101 arm64 Darwin Kernel Version 17.7.0: Wed Apr 24 21:17:24 PDT 2019; root:xnu-4570.71.45~1/RELEASE_X86_64 x86_64…

The bug was introduced only last year in macOS 26: https://github.com/apple-oss-distributions/xnu/blame/f6217f8...

> Apple Community #250867747: macOS Catalina — "New TCP connections can not establish." New connections enter SYN_SENT then immediately close. Existing connections unaffected. Only a reboot fixes it.

This is a weird thing to cite if it's a macOS 26 bug. I quite regularly go over 50 days of uptime without issues so it makes sense for it to be a new bug, and maybe they had different bugs in the past with similar symptoms.

Re: A macOS bug that causes TCP networking to stop working after 49.7 days

#57

Post by groby_b »

Aloisius wrote: post #54
comex wrote: post #44

Earlier quoted context omitted.

The bug was introduced only last year in macOS 26: https://github.com/apple-oss-distributions/xnu/blame/f6217f8...

Interesting. The article mentions complaints on the forums running Catalina, so that must be something else.

The article is written using AI, so unless you verified the complaints, the safe default assumption is that they don't exist.

Re: A macOS bug that causes TCP networking to stop working after 49.7 days

#59

Post by js2 »

Aloisius wrote: post #54
comex wrote: post #44

Earlier quoted context omitted.

The bug was introduced only last year in macOS 26: https://github.com/apple-oss-distributions/xnu/blame/f6217f8...

Interesting. The article mentions complaints on the forums running Catalina, so that must be something else.

As someone who also operates fleets of Macs, for years now, there is no possible way this bug predates macOS 26. If the bug description is correct, it must be a new one.
Post reply on HN