HN user

garaetjjte

3,461 karma

https://milek7.pl

Posts57
Comments1,388
View on HN
milek7.pl 29d ago

Don't verify email addresses by sending spam to them

garaetjjte
193pts63
spacenews.com 3mo ago

Lockheed Martin Pressing to Simplify Orion Heat Shield (2015)

garaetjjte
3pts0
drs.faa.gov 8mo ago

Emergency Airworthiness Directive for MD-11

garaetjjte
3pts0
www.youtube.com 8mo ago

HoloDoom [video]

garaetjjte
2pts0
lwn.net 1y ago

Maximal Min() and Max()

garaetjjte
8pts0
www.archives.gov 1y ago

NARA 803, Internet Protocol Version 6 (IPv6) Policy [pdf]

garaetjjte
6pts0
www.cs.auckland.ac.nz 2y ago

The Heffalump Threat [pdf]

garaetjjte
2pts0
www.os2museum.com 2y ago

The Future That Never Was

garaetjjte
4pts0
tonsky.me 3y ago

Font size is useless; let’s fix it (2021)

garaetjjte
21pts8
joeduffyblog.com 3y ago

A (brief) retrospective on transactional memory (2010)

garaetjjte
1pts0
travisdowns.github.io 4y ago

AVX-512 Mask Registers, Again (2020)

garaetjjte
1pts0
milek7.pl 4y ago

Low-cost custom TPMS receiver

garaetjjte
4pts0
www.youtube.com 4y ago

Melt Your Circuit Boards

garaetjjte
5pts0
www.zf.com 4y ago

Steer-by-Wire from ZF

garaetjjte
1pts0
www.ncbi.nlm.nih.gov 4y ago

Hacking CD/DVD/Blu-ray for Biosensing (2018)

garaetjjte
112pts14
qntm.org 4y ago

Zero-Indexing the Gregorian Calendar

garaetjjte
2pts2
www.youtube.com 4y ago

Transparent Engine Cylinder – How an Engine Works in 4K Slow Motion

garaetjjte
5pts0
www.youtube.com 5y ago

Riding an Autonomous Bus on the City Streets in China (Xiaoyu 2.0)

garaetjjte
3pts0
www.wykop.pl 5y ago

ISS transit during solar eclipse

garaetjjte
3pts1
www.youtube.com 5y ago

Asahi Linux: m1n1 Hypervisor recap

garaetjjte
6pts1
www.vanityfair.com 5y ago

The Devil at 37,000 Feet (2009)

garaetjjte
3pts0
fasterthanli.me 5y ago

More ELF Relocations

garaetjjte
3pts0
www.datacenterdynamics.com 5y ago

TSMC suffers power outage at Tainan chip fab complex

garaetjjte
17pts2
web.archive.org 5y ago

Internet Archive Wayback Machine is down

garaetjjte
3pts0
milek7.pl 5y ago

How long it would have taken to fuzz recent buffer overflow in sudo?

garaetjjte
14pts6
jcjc-dev.com 5y ago

Learning to Decapsulate Integrated Circuits Using Acid Deposition

garaetjjte
48pts8
lwn.net 5y ago

Preparing for the Realtime Future

garaetjjte
4pts0
www.theatlantic.com 6y ago

The tragedy of Google Books (2017)

garaetjjte
3pts0
www.vice.com 6y ago

Why Repair Techs Are Hacking Ventilators with DIY Dongles from Poland

garaetjjte
21pts2
widespacer.blogspot.com 6y ago

The Hidden Secrets of QWERTY (2015)

garaetjjte
1pts0

You usually hope that TTD points to the culprit in such situations. But once I encountered single-byte corruption that didn't make any sense in TTD trace, there was good value at write and next read was garbage. I never discovered whether that was CPU bug, corruption by GPU shaders, stray kernel writes, or whatever.(I think it's unlikely that CPU bug would manifest with both native and TTD-instrumented runs. Corrupted byte was inside heap allocated memory so it shouldn't be in GPU pagetables at all. Kernel writes wouldn't appear in TTD trace, so really I think that was most likely issue, but how to debug that...)

I hate that type of diagrams. Why sRGB-encoded image, pretends to show any color outside of sRGB region? It doesn't make any sense! (and when these diagrams attempt to illustrate sRGB, often actual colors encoded are narrower than full sRGB)

Official Mono releases have switched to do that since then, but (I think) for backwards compatibility reasons Unity never enabled that functionality and kept everything at double precision so far.

Probably because Unity uses ancient Mono fork. And that apparently started because they didn't renew their non-copyleft license with Xamarin.

In practice they don't do that, apart from spamming few addresses like office@ or accounting@. If some address starts getting spam I reject everything sent to it. For addresses that are getting spam but needs to be public (like contact addresses on website) I do more aggressive filtering (eg. I noticed that enforcing that recipient is actually present in To/Cc header cuts down a lot of spam).

That's mostly papering over design mistake that most syscalls doesn't accept target pid. Otherwise you could just create suspended process, configure it with syscalls that explicitly take target pid, and start it.

the more of them you add, the larger is your communication and coordination overhead. In no small part because humans are self-interested agents that simply aren't designed to compose their capabilities seamlessly.

What proves that AI doesn't have the same limitations? There's only so much computation you can do in given space, and all communication is limited by universal speed limit.

Huh? CE7 platform builder is just extension to stock VS2008. And it doesn't really do much, just few treeviews for selecting components. The real issue is the build system, which is some hideous combination of bat files and nmake.

Kernel is the only part that seems written with any sort of care, everything else is barely holding together with duct tape.

I don't think cell tower connection will give you any more precision, GNSS fix will be much more accurate. (within few meters)

You could get more accurate fix with RTK data, but I'm not sure if that's actually widely used. And in any case that doesn't require active communications either, you could get correction data from satellite broadcasts too.

Mozilla Thunderbolt 3 months ago

WTF is that? Wasn't MZLA supposed to be the home of Thunderbird project, and now they are mixing that with some unrelated bullshit?

Seems fine if you can donate to Thunderbird development. Compared to Firefox, where I don't think it's possible to donate to development at all (only to Mozilla activism side).

Since we are on HN, I think it could be explained there (before it's all consumed by AI slop):

For complex reasons, available CPU time during landing was lower than expected (it was stolen by radar pointing peripheral). This caused regularly scheduled job to spawn before previous instance finished. As such, this caused two effects: job instances were suspended before finishing by new instances in the middle of the routine, and that pilling up of the old instances eventually exhausted resources and caused kernel to panic and reboot. Rebooting during landing sounds scary, but that actually was fine: such critical tasks were specifically designed to automatically restart from previously saved checkpoint data in the memory.

What was more dangerous, was the suspended tasks before restarts occured. First, it meant routine wasn't executing to the end, which in actual flight caused blanked displays (as updating the display was the last thing routine was doing). Any more CPU time stolen, and it could be interrupted even earlier, eg. before it sends the engine commands.

Another issue is that in case of fluctuating load, new instances could actually begin running to the end, and then previously suspended job instance could be resumed, potentially sending the stale data to the displays and engine.

And finally, while each job instance had it own core and VAC set properly managed by the kernel (think of it as modern kernel switching between task stacks), that particular routine wasn't designed to be reentrant. So it was using various global variables ("erasables") for its own purpose, that when interrupted in unluckly place might have caused very bad behavior.

How likely all of above is to occur, depends on the exact profile of fluctuating load caused by the confused radar peripheral. I guess that's why Mike Stewart is trying to replicate these issues with real CDU.