What version of macOS are you running with?
I'm the initial bug reporter. This machine is on 10.13.3.
You might want to run it again in 10.13.4 beta :)
I think I found a Mac kernel bug?
101–110 of 126 posts
Re: I think I found a Mac kernel bug?
#102But Mac OS is secure by design! How is this possible?
Re: I think I found a Mac kernel bug?
#103Earlier quoted context omitted.
I'm happy to pay a premium to never again have to deal with xorg.conf. All platforms come with a cost.
FWIW, X configures itself nowadays and Wayland also just works. But I know where you are coming from. Everything audio related for example is still in very bad shape when you want more than Intel HDA.
Now try hotplugging an external display.
Re: I think I found a Mac kernel bug?
#104Earlier quoted context omitted.
I had to add ?33333 to the end of the URL, and reload, to bust the browser cache.
Might not just be the browser cache -- I use Cloudflare on my blog and have a script that uses the Cloudflare API to clear the CDN cache when I update the site, but the Cloudflare API doesn't appear to work 100% reliably and I'm not sure why. sorry about that!
Hey Julia - feel free to email me (msilverlock @ cloudflare) so I can look into this. If you can share the API calls you’re making it’d be useful too!
Re: I think I found a Mac kernel bug?
#105Earlier quoted context omitted.
The difference is you pay a huge premium for Apple products, Linux distros are generally free (unless you want enterprise-style support). The same criticism applies to Windows - give it away for free and I might care less about crashes and the huge slide in quality over the last ~5 years.
You’re not paying for the OS; you’re paying for the hardware. If Macintosh hardware was buggy when running Linux or Windows , for reasons to do with, say, badly-written ACPI tables, then you’d have an argument. As it is, it’s the opposite: Macs run both Windows and Linux “easily”, while other vendors’ buggy hardware has to be patched over with heuristics in these OSes because it has non-conforming device names, respo…
You will not find significant fundamental hardware differences between the latest high-end Apple and Dell laptops.
> As it is, it’s the opposite: Macs run both Windows and Linux “easily”, while other vendors’ buggy hardware has to be patched over with heuristics in these OSes because it has non-conforming device names
> This is, coincidentally, also the reason it’s so hard to run macOS on other vendors’ machines
Are you not aware that OS X does various explicit checks to make sure it is running on approved hardware, regardless of compatibility and capability attestation? Apple doesn't want OS X running on non-Apple hardware.
Re: I think I found a Mac kernel bug?
#106Earlier quoted context omitted.
You’re not paying for the OS; you’re paying for the hardware. If Macintosh hardware was buggy when running Linux or Windows , for reasons to do with, say, badly-written ACPI tables, then you’d have an argument. As it is, it’s the opposite: Macs run both Windows and Linux “easily”, while other vendors’ buggy hardware has to be patched over with heuristics in these OSes because it has non-conforming device names, respo…
You will not find significant fundamental hardware differences between the latest high-end Apple and Dell laptops. > As it is, it’s the opposite: Macs run both Windows and Linux “easily”, while other vendors’ buggy hardware has to be patched over with heuristics in these OSes because it has non-conforming device names > This is, coincidentally, also the reason it’s so hard to run macOS on other vendors’ machines Are…
> various explicit checks to make sure it is running on approved hardware
Er, yes, that's the "dont-steal-osx.kext" that I mentioned. My point was that thwarting those checks is a very small part of getting macOS to run on a system (and is a solved problem—if it was all that was required, Hackintoshing would be a one-and-done thing, rather than something that breaks on every system update.)
The majority of the (continuing) effort of getting macOS to run on arbitrary hardware—hardware that, by its components, should be compatible with macOS's drivers—is dealing with vendors' whack-ass "doesn't even pass static analysis using Intel's own provided AML compiler" DSDTs (which macOS rightfully tosses its hands up at, but which Windows and Linux heuristically munge into something barely passable and then use it.)
> latest high-end Apple and Dell laptops
Dell (along with HP and Lenovo) are the better vendors as far as spec-compliance goes. Really, any of the PC makers who have an "enterprise workstation" arm, have the in-house expertise for things like ACPI compliance, or UEFI compliance, or PXE compliance, etc. But other vendors? Acer? LG? Xiaomi? Razer? Better to not even try.
Re: I think I found a Mac kernel bug?
#107Question from someone who knows very little about the Mach/XNU APIs: Does this code leak Mach ports? If you call task_for_pid, you get back a Mach task port. Do you have to close the port with mach_port_deallocate? Could a resource leak be contributing to the system freeze?
Re: I think I found a Mac kernel bug?
#108Earlier quoted context omitted.
The difference is you pay a huge premium for Apple products, Linux distros are generally free (unless you want enterprise-style support). The same criticism applies to Windows - give it away for free and I might care less about crashes and the huge slide in quality over the last ~5 years.
You’re not paying for the OS; you’re paying for the hardware. If Macintosh hardware was buggy when running Linux or Windows , for reasons to do with, say, badly-written ACPI tables, then you’d have an argument. As it is, it’s the opposite: Macs run both Windows and Linux “easily”, while other vendors’ buggy hardware has to be patched over with heuristics in these OSes because it has non-conforming device names, respo…
[deleted]
Re: I think I found a Mac kernel bug?
#109Additionally, valgrind is incompatible with Maverick. Which is a huge pain, because it means that if I ever need to use it, I have to debug on a server.
Are you sure? IIRC valgrind supports everything up to macOS Sierra.
Re: I think I found a Mac kernel bug?
#110@cliffordheath on twitter says [0]
> This will be a kernel data structure protected by a mutex or semaphore. task_for_pid waits at pri>=0 for a wakeup that won't happen because race. ps queues behind it at pri
Seems like a reasonable explanation as to the underlying cause of the behaviour.
[0] https://twitter.com/cliffordheath/status/957505667568353280