2021-05-12
00:08zkrx has quit [Ping timeout: 246 seconds]
00:22zkrx has joined #asahi-gpu
02:44PhilippvK has joined #asahi-gpu
02:44phiologe has quit [Ping timeout: 276 seconds]
03:23marcanthat's usually where they are, though on SoCs with internal voltage control stuff that applies to internal MMIO too
04:43r0ni has joined #asahi-gpu
07:08phire has quit [*.net *.split]
08:22herbas has joined #asahi-gpu
08:23phire has joined #asahi-gpu
08:37herbas has quit [Quit: herbas]
09:31robinp has quit [Read error: Connection reset by peer]
10:04Lightsword has quit [Quit: ZNC]
10:05Lightsword has joined #asahi-gpu
10:08akemin_dayo has quit [Ping timeout: 240 seconds]
10:44seghermarcan: most PLLs don't allow crazily out-of-range settings... but running something at 4GHz instead of 3.5GHz will increase power consumpotion by 25% or so, reducing lifetime, maybe by a lot
11:04snalty has quit [Quit: ZNC 1.8.2 - https://znc.in]
11:06bpye has quit [Ping timeout: 268 seconds]
11:13bpye has joined #asahi-gpu
11:23marcansegher: 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.
11:24marcanthe 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
11:24marcanI'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 :-)
11:25marcanif overclocking damaged things permanently (when you don't touch the voltage) people would be killing a lot of PC hardware
11:50seghermost things *will* run at 6GHz instead of 3GHz even (with good cooling). and if it reduces lifetime by 10x most people will care a LOT
11:53marcanI generally don't make a habit of running code that randomly pokes registers I do not understand without a specific goal in mind :)
11:54marcanI organize spain's largest lan party, and overclocking competitions have been a thing here; I have some personal experience :)
11:55marcanI think I only ever saw one guy with a phase-change cooler that might've had any chance of seeing normal use
11:56marcan(I still regret losing the link to that one OEM advisory that I was certain was a reference to that incident)
11:57snalty has joined #asahi-gpu
11:59marcanI'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"
12:00JTLre overclocking: I think I read an article awhile ago that discussed the risk of electromigration getting worse with overvolting and higher transistor density based CPUs
12:02marcanand people who do that on consumer stuff better know they are reducing the lifetime of their hardware
12:05marcanincidentally, 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
12:07JTLmarcan: I built a 3700x workstation last year and dealt with many defective parts (covid factory QC issues anyone?) and in my testbench testing with janky heatsink mounting I never fried anything lol
12:19ari was surprisingly lucky with my workstation/desktop i built late last year, as nothing was defective, and i managed to fit it everything in the tiny case i got for it…
12:20JTLcool me old fashioned, but I prfer rackmount or (reasonable) desktop tower cases in terms of clearences
12:22JTLar: this was around circa July/August, and date codes from some parts showed around April/May manufacturing dates
12:22JTLI have a similar planned project in this area, but that's not going to happen for a while and should be taken to #-offtopic later
12:25arspeaking of "nobody reads messages". i got a m1 mbp13 from the company i work for now, and dmesg on it is full of weird stuff
12:59Lightsword has quit [Quit: ZNC]
12:59Lightsword has joined #asahi-gpu
13:02choozy has joined #asahi-gpu
13:29akemin_dayo has joined #asahi-gpu
13:45grange_c has quit [Quit: Ping timeout (120 seconds)]
13:45grange_c has joined #asahi-gpu
17:04konradybcioIt might be a dumb question.. but could the perf loss because of all the logging hurt performance in an unsignificant way on older machines?
17:04konradybcioAfaict macos is still not on android level of spamming logs but it's pretty up there
17:22dottedmagkonradybcio: Very unlikely. logd never shows up as eating any significant amount of CPU or IO
18:07arand dmesg on macos not having -w and -T flags, so it cannot automatically follow new entries, and timestamps aren't human-friendly
19:06dottedmagbloom: dmesg shows up in Console as "pid 0 messages", but non-kernel messages aren't posted to dmesg.
19:11dottedmagConsole chiefly displays whatever was posted by os_log(3) -- and I have no idea how is it different from syslog(3) -- and these messages end up in /var/db/diagnostics. Probably through logd or syslogd
19:21pthariensflame has joined #asahi-gpu
19:22pthariensflame has quit [Client Quit]
19:51DarkShadow44 has quit [Quit: Free ZNC ~ Powered by LunarBNC: https://LunarBNC.net]
19:51DarkShadow44 has joined #asahi-gpu
21:58choozy has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]