News for hackers. Stuff that matters.
Re:I helped fix sleep-wake hangs on Linux with AMD GPUs by dekhn on Monday February 17, 2025 @03:51PM (#43083178)
I used to think that naming things, cache invalidation, and off-by-one errors were the 2 biggest problems in CS, but then I learned about the "sleep/wake" problem and realized it's NP-complete.
Re:I helped fix sleep-wake hangs on Linux with AMD GPUs by nikanj on Monday February 17, 2025 @03:54PM (#43083198)
Only on Linux though, on Windows it’s O(n2) and on Macos it’s O(log n)
Re:I helped fix sleep-wake hangs on Linux with AMD GPUs by itsn0tm3 on Monday February 17, 2025 @04:10PM (#43083322)
Well only as long as you don‘t hackintosh. That stuff used to be a horror sometimes!
Re:I helped fix sleep-wake hangs on Linux with AMD GPUs by 0x38B on Monday February 17, 2025 @05:54PM (#43084052)
Remembering the hours I spent going through KEXTs and bootloader config in ill-fated attempts to set up a Hackintosh fills me now with a kind of horror. Worst of all were the ACPI tables - SSDT and the like.

In contrast to that, running MacOS in a VM is heaven. Figuring out how to pass my iPhone through to Xcode took as long as the initial setup.

Re:I helped fix sleep-wake hangs on Linux with AMD GPUs by ncann on Monday February 17, 2025 @04:34PM (#43083517)
With how much trouble I had with trying (and failing) to make my brand new Dell laptop sleep properly and not the "Modern Standby" crap, plus my desktop randomly breaking GPU hardware acceleration in browser after waking up, I would say it's around O(n4) now. Or maybe even O(n!).
Re:I helped fix sleep-wake hangs on Linux with AMD GPUs by verall on Tuesday February 18, 2025 @11:40AM (#43091789)
I think sleep/wake is a subset of cache invalidation - if all peripherals were stateless, probably it wouldn't be an issue.