#
✕ nick:marcan
#asahi-gpu · 2021-05-23 15:47
marcanaw, and you'd gotten me excited :p
#asahi-gpu · 2021-05-23 15:46
marcanI'm definitely going back to the hypervisor tomorrow, better hope I don't finish that too soon or else I'll start working on the drm drver :p
#asahi-gpu · 2021-05-23 15:45
marcan^_^
#asahi-gpu · 2021-05-23 15:44
marcanbloom: done, rejoin should autoop
#asahi-gpu · 2021-05-20 03:28
marcanWelcome to Asahi Linux's new home on OFTC! Logs from Freenode up until 2021-05-19 have been backfilled into the OFTC log interface, to avoid a discontinuity and split search.
#asahi-gpu · 2021-05-12 17:00
marcanand yes, there is a *ton* of spam
#asahi-gpu · 2021-05-12 17:00
marcanit does
#asahi-gpu · 2021-05-12 12:23
marcannobody reads messages :P
#asahi-gpu · 2021-05-12 12:23
marcanthat's the point
#asahi-gpu · 2021-05-12 12:23
marcanit's not just warning messages
#asahi-gpu · 2021-05-12 12:23
marcansegher: no, it will throttle or shut down
#asahi-gpu · 2021-05-12 12:05
marcanthere should be safeties around all that
#asahi-gpu · 2021-05-12 12:05
marcanincidentally, the M1 GPU firmware has some messages about temperature trips and such, so I expect that we won't be cooking any M1s by accident
#asahi-gpu · 2021-05-12 12:03
marcanand it definitely doesn't matter for experiments
#asahi-gpu · 2021-05-12 12:02
marcanbut just bumping up clocks is a lot less dangerous
#asahi-gpu · 2021-05-12 12:02
marcanand people who do that on consumer stuff better know they are reducing the lifetime of their hardware
#asahi-gpu · 2021-05-12 12:02
marcanif you overvolt, yeah, definitely
#asahi-gpu · 2021-05-12 11:59
marcanI'm not entirely sure what you're talking about; we somehow went from "accidentally misconfiguring a PLL during MMIO experiments" to "people supposedly running chips at 2x their rated clock"
#asahi-gpu · 2021-05-12 11:56
marcan(I still regret losing the link to that one OEM advisory that I was certain was a reference to that incident)
#asahi-gpu · 2021-05-12 11:56
marcan(OTOH, Intel sometimes does, *cough* l*****v *cough*)
#asahi-gpu · 2021-05-12 11:56
marcanI also worked for google and I can tell you they don't overclock their servers :P
#asahi-gpu · 2021-05-12 11:55
marcanI think I only ever saw one guy with a phase-change cooler that might've had any chance of seeing normal use
#asahi-gpu · 2021-05-12 11:54
marcanI organize spain's largest lan party, and overclocking competitions have been a thing here; I have some personal experience :)
#asahi-gpu · 2021-05-12 11:53
marcannot to actually use the things
#asahi-gpu · 2021-05-12 11:53
marcanthe people doing 6GHz are doing it to set a record on liquid nitrogen, for 5 minutes
#asahi-gpu · 2021-05-12 11:53
marcanI don't think anyone does that there either
#asahi-gpu · 2021-05-12 11:53
marcanI generally don't make a habit of running code that randomly pokes registers I do not understand without a specific goal in mind :)
#asahi-gpu · 2021-05-12 11:52
marcanI can certainly figure out a PLL in under a month
#asahi-gpu · 2021-05-12 11:52
marcannobody's going to accidentally run something at 6GHz without noticing for that long :-)
#asahi-gpu · 2021-05-12 11:52
marcan100x doesn't matter; 100x is 10 years to 36 days
#asahi-gpu · 2021-05-12 11:25
marcanif overclocking damaged things permanently (when you don't touch the voltage) people would be killing a lot of PC hardware
#asahi-gpu · 2021-05-12 11:24
marcanI've done the "let's crank up the clock to beyond design specs" thing too; what happened was the power circuitry couldn't handle it and the thing shut down :-)
#asahi-gpu · 2021-05-12 11:24
marcanthat cleared up within a week or so though
#asahi-gpu · 2021-05-12 11:24
marcanthe closest I've come to damaging hardware from this kind of thing was some temporary DC bias damage done to an LCD panel, but that was because I got the power sequencing wrong (which caused it not to init properly and bias the panel), so again, power stuff
#asahi-gpu · 2021-05-12 11:23
marcansegher: most things won't *run* at 4GHz instead of 3.5GHz if 3.5GHz is nominal, and unless it reduces lifetime by a million times, nobody cares; these experiments last seconds to minutes.
#asahi-gpu · 2021-05-12 03:23
marcanthat's usually where they are, though on SoCs with internal voltage control stuff that applies to internal MMIO too
#asahi-gpu · 2021-05-12 03:00
marcanVRM, yes
#asahi-gpu · 2021-05-12 03:00
marcanyou'll just crash things
#asahi-gpu · 2021-05-12 03:00
marcanit's pretty hard to break anything by messing with PLLs
#asahi-gpu · 2021-05-11 06:26
marcanI now have the same thing for the hypervisor; exceptions break to the same shell, I can inspect processor context, and as of yesterday get backtraces (with resolved symbols etc), decode panics, etc
#asahi-gpu · 2021-05-11 06:26
marcanazonenberg: in case you haven't see it yet: https://github.com/AsahiLinux/docs/wiki/Developer-Quickstart#playground-shell
#asahi-gpu · 2021-05-11 06:21
marcanand then that's just 8 seconds
#asahi-gpu · 2021-05-11 06:21
marcanonly if I do something unforeseen to break execution, or actually crash the hardware, do I have to reboot
#asahi-gpu · 2021-05-11 06:21
marcanI spend a lot of time making my tools efficient; my register poking is remotely controlled from python scripts running on my PC, and most exceptions are caught and recovered from
#asahi-gpu · 2021-05-11 06:20
marcan26 seconds, a bunch of that is compression/checksumming that I want to speed up a bit
#asahi-gpu · 2021-05-11 06:19
marcanlet me time an actual hypervisor run to the current crash point...
#asahi-gpu · 2021-05-11 06:18
marcanalso my reboot-to-interactive-debug-shell cycle is ~8 seconds right now
#asahi-gpu · 2021-05-11 06:18
marcan:-)
#asahi-gpu · 2021-05-11 06:18
marcanwell, you quickly build up a blocklist of registers you shouldn't touch
#asahi-gpu · 2021-05-11 06:15
marcan(they moved them elsewhere after that one botched release)

plus ›