| - chartreuse (QUIT: Read error: Connection reset by peer) (~chartreus@node-1w7jr9ql2247ulxzt91eckjma.ipv6.telus.net) | 00:05 | |
| + chartreus (~chartreus@node-1w7jr9ql2247ulxzt91eckjma.ipv6.telus.net) | 00:05 | |
| * chartreus -> chartreuse | 00:07 | |
| - bkeys (QUIT: Ping timeout: 268 seconds) (~Thunderbi@static-198-54-135-69.cust.tzulo.com) | 00:07 | |
| - chartreuse (QUIT: Ping timeout: 244 seconds) (~chartreus@node-1w7jr9ql2247ulxzt91eckjma.ipv6.telus.net) | 00:18 | |
| vkoskiv_ | I keep having these random freezes where vim or some other program gets stuck for a few seconds, and then the following message is emitted to the kernel log: | 00:53 |
|---|---|---|
| vkoskiv_ | [30555.465943] nvme nvme0: I/O 15 QID 1 timeout, completion polled | 00:53 |
| vkoskiv_ | Is there a fix for this? It's getting a bit frustrating. | 00:54 |
| vkoskiv_ | I don't understand the meaning of that message, even after a bit of googling. | 00:54 |
| minutepkt | vkoskiv_: unusual | 01:26 |
| minutepkt | vkoskiv_: what ssd model? | 01:26 |
| minutepkt | grubman: yes, https://source.mnt.re/reform/reform-system-image/-/jobs/848/artifacts/browse/reform2-imx8mq/ | 01:33 |
| kfx | vkoskiv_: what kernel version is this? | 01:34 |
| vkoskiv_ | minutepkt: It's an Intell 600P | 01:34 |
| kfx | there used to be a bug where msi-x interrupts weren't properly masked after a resume, but it got fixed a couple years back | 01:34 |
| vkoskiv_ | s/intell/intel | 01:34 |
| vkoskiv_ | 256GB | 01:34 |
| minutepkt | hmm kfx we use pci=nomsi | 01:35 |
| minutepkt | maybe disabling aspm could help? or move data to another brand, like WD blue | 01:36 |
| kfx | vkoskiv_: also make sure your nvme drive has the latest firmware | 01:37 |
| - minutepkt (QUIT: Quit: Lost terminal) (~mntmn@ip-109-40-243-140.web.vodafone.de) | 01:39 | |
| vkoskiv_ | Newest is PSF121C, I'm running PSF100C | 01:42 |
| vkoskiv_ | Place your bets on if Intel made a linux + arm64 update tool | 01:42 |
| vkoskiv_ | linux yes, arm no | 01:45 |
| vkoskiv_ | x86_64 only here. | 01:45 |
| - mtm- (QUIT: Ping timeout: 268 seconds) (~mtm@c-73-27-62-116.hsd1.fl.comcast.net) | 02:03 | |
| smj | There are some nice MNT Reform updates after this week's Plan9front hack-a-thon | 02:04 |
| kfx | vkoskiv_: theoretically fwupdmgr should be able to handle it | 02:04 |
| vkoskiv_ | kfx: fwupdate says the ssd has no updates available | 02:08 |
| vkoskiv_ | s/fwupdate/fwupdmgr | 02:08 |
| vkoskiv_ | Geez, what a name | 02:08 |
| kfx | https://usermanual.wiki/Pdf/IntelSSDFirmwareUpdateTool301ReleaseNotes.697519269.pdf see page 16 | 02:09 |
| kfx | might be worth trying to update that firmware on a different drive | 02:09 |
| kfx | I mean with that drive in a different system | 02:09 |
| vkoskiv_ | Yeah, might plug it into my desktop | 02:10 |
| vkoskiv_ | Can also image the drive before updating while it's there | 02:10 |
| kfx | if you can unpack the updater, fwupdtool can probably flash the update directly with the install-blob command | 02:11 |
| vkoskiv_ | Thanks! I'll try that | 02:16 |
| + robin (~robin@user/terpri) | 02:18 | |
| + mtm (~mtm@c-73-27-62-116.hsd1.fl.comcast.net) | 04:09 | |
| - erle (QUIT: Ping timeout: 268 seconds) (~erle@ip5f5af7a8.dynamic.kabel-deutschland.de) | 04:34 | |
| + erle (~erle@ip5f5af7a8.dynamic.kabel-deutschland.de) | 04:48 | |
| - vagrantc (QUIT: Quit: leaving) (~vagrant@2600:3c01:e000:21:7:77:0:20) | 05:31 | |
| - Ar|stote|is (QUIT: Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) (~linx@149-210-4-98.mobile.nym.cosmote.net) | 05:33 | |
| + Ar|stote|is (~linx@149-210-4-98.mobile.nym.cosmote.net) | 05:33 | |
| - erle (QUIT: Ping timeout: 252 seconds) (~erle@ip5f5af7a8.dynamic.kabel-deutschland.de) | 06:19 | |
| - kitty4 (QUIT: Ping timeout: 268 seconds) (~kitty@096-039-147-043.res.spectrum.com) | 08:00 | |
| - ajr (QUIT: Quit: WeeChat 3.6) (~ajr@user/ajr) | 08:19 | |
| smj | Sorry if anyone wanted https://www.ebay.com/itm/165623015107 I got it specifically to donate it to a plan9front project. | 09:00 |
| smj | If you are interested in plan9front let me know. I hope to have many MNT reforms available for it. | 09:01 |
| + kitty4 (~kitty@096-039-147-043.res.spectrum.com) | 09:23 | |
| - kitty4 (QUIT: Ping timeout: 268 seconds) (~kitty@096-039-147-043.res.spectrum.com) | 10:17 | |
| + kitty4 (~kitty@096-039-147-043.res.spectrum.com) | 10:22 | |
| + chomwitt (~chomwitt@2a02:587:dc15:5e00:f956:e7c7:43ea:328a) | 11:08 | |
| - kitty4 (QUIT: Ping timeout: 268 seconds) (~kitty@096-039-147-043.res.spectrum.com) | 11:09 | |
| + kitty4 (~kitty@096-039-147-043.res.spectrum.com) | 11:16 | |
| - chomwitt (QUIT: Ping timeout: 268 seconds) (~chomwitt@2a02:587:dc15:5e00:f956:e7c7:43ea:328a) | 11:18 | |
| + chomwitt (~chomwitt@2a02:587:dc15:5e00:1855:2a35:cc0e:e682) | 11:19 | |
| - kitty4 (QUIT: Ping timeout: 264 seconds) (~kitty@096-039-147-043.res.spectrum.com) | 12:02 | |
| + kitty4 (~kitty@096-039-147-043.res.spectrum.com) | 12:15 | |
| + MajorBiscuit (~MajorBisc@46-229-126.internethome.cytanet.com.cy) | 12:32 | |
| - kitty4 (QUIT: Ping timeout: 268 seconds) (~kitty@096-039-147-043.res.spectrum.com) | 12:44 | |
| + reform27911 (~shreek@45.127.45.18) | 12:47 | |
| reform27911 | hello everypone | 12:48 |
| reform27911 | exit | 12:49 |
| reform27911 | exit | 12:50 |
| - reform27911 (QUIT: Read error: Connection reset by peer) (~shreek@45.127.45.18) | 12:52 | |
| - MajorBiscuit (QUIT: Ping timeout: 268 seconds) (~MajorBisc@46-229-126.internethome.cytanet.com.cy) | 13:30 | |
| + MajorBiscuit (~MajorBisc@46-229-126.internethome.cytanet.com.cy) | 13:46 | |
| - mtm (QUIT: Ping timeout: 268 seconds) (~mtm@c-73-27-62-116.hsd1.fl.comcast.net) | 14:04 | |
| - sundog20 (QUIT: Quit: The Lounge - https://thelounge.chat) (~sundog@reclaim.technology) | 14:04 | |
| + sundog206 (~sundog@reclaim.technology) | 14:06 | |
| - MajorBiscuit (QUIT: Ping timeout: 268 seconds) (~MajorBisc@46-229-126.internethome.cytanet.com.cy) | 14:44 | |
| + minutepkt (~mntmn@ip-109-40-243-88.web.vodafone.de) | 15:00 | |
| - minutepkt (QUIT: Quit: Lost terminal) (~mntmn@ip-109-40-243-88.web.vodafone.de) | 16:01 | |
| + erle (~erle@ip5f5af7a8.dynamic.kabel-deutschland.de) | 16:34 | |
| + bkeys (~Thunderbi@static-198-54-135-69.cust.tzulo.com) | 16:37 | |
| + vagrantc (~vagrant@2600:3c01:e000:21:7:77:0:20) | 17:14 | |
| + mtm (~mtm@c-73-27-62-116.hsd1.fl.comcast.net) | 19:34 | |
| + cinap_lenrek (~cinap_len@216.red-79-144-163.dynamicip.rima-tde.net) | 20:31 | |
| cinap_lenrek | bad news | 20:34 |
| Boostisbetter | uh oh | 20:34 |
| cinap_lenrek | fucked my reform batteries in the hackerthon :( | 20:34 |
| vkoskiv_ | Oof, how'd that happen? | 20:34 |
| cinap_lenrek | i belive this might have been my fault tho | 20:34 |
| cinap_lenrek | i modified the firmware for remote testing during bringup | 20:35 |
| cinap_lenrek | so the reform would always try the start the arm as soon as power is applied | 20:35 |
| cinap_lenrek | someone must have tripped over the power-supply and the 230V cable slipped out of the powersupply | 20:36 |
| cinap_lenrek | so the reform ran on batteries over night and ran out | 20:36 |
| cinap_lenrek | and next day batteries where ded | 20:36 |
| cinap_lenrek | and wasnt recharching | 20:36 |
| vkoskiv_ | What's the voltage on the cells | 20:37 |
| cinap_lenrek | status says missing cells | 20:37 |
| cinap_lenrek | all over the place | 20:37 |
| cinap_lenrek | some where showing 0.0V | 20:37 |
| vkoskiv_ | On the display or with a multimeter? | 20:37 |
| cinap_lenrek | some 2.6V... 1.X.,.. | 20:37 |
| cinap_lenrek | and now, its even crazier | 20:37 |
| cinap_lenrek | i let if plugged with power over night | 20:37 |
| cinap_lenrek | in the hope it would recover | 20:37 |
| cinap_lenrek | but now all read 5.3V | 20:37 |
| cinap_lenrek | all cells | 20:38 |
| vagrantc | that's a bit high :( | 20:38 |
| cinap_lenrek | vkoskiv_: i havnt measured with multimeter | 20:38 |
| cinap_lenrek | yeah | 20:38 |
| cinap_lenrek | maybe now mainboard is damaged | 20:38 |
| cinap_lenrek | i dont know | 20:38 |
| cinap_lenrek | 5.3V makes no sense | 20:39 |
| cinap_lenrek | i think 5.3V might just be an error | 20:40 |
| cinap_lenrek | bullshit value | 20:40 |
| cinap_lenrek | maybe later i take out batteries and measure with multimeter | 20:40 |
| cinap_lenrek | or when i get back | 20:40 |
| vagrantc | hopefully | 20:40 |
| cinap_lenrek | tho, i wonder... even with the poweron change | 20:46 |
| cinap_lenrek | the lpc would turn off the arm no? | 20:47 |
| cinap_lenrek | when it runs low on power | 20:47 |
| cinap_lenrek | how long does it then take for the lpc to brown out and drain the remaing charge? | 20:47 |
| cinap_lenrek | i can imaginge once it browns out, and restarts and starts the arm again | 20:48 |
| cinap_lenrek | draining the battery | 20:48 |
| minute | cinap_lenrek: 5.3 is basically a fault | 20:49 |
| Boostisbetter | The LPC saw an update, which I imagine yoru Reform had that would kill power when the batteries get too low | 20:49 |
| minute | cinap_lenrek: and yes, you ran into lpc brownout | 20:49 |
| Boostisbetter | but I see the Chef is here so I'll digress | 20:50 |
| cinap_lenrek | ok | 20:50 |
| cinap_lenrek | we'll see | 20:51 |
| cinap_lenrek | i will remove batteries and measure them with multimeter | 20:51 |
| cinap_lenrek | and maybe get replacement onces | 20:51 |
| minute | cinap_lenrek: but you're in luck, there is stock https://eu.nkon.nl/jgne-18650-1800mah-5-4a-lifepo4.html | 20:51 |
| cinap_lenrek | just the 5.3V worry me | 20:51 |
| minute | cinap_lenrek: it just means the cell is dead | 20:52 |
| cinap_lenrek | ah, ok :) | 20:52 |
| cinap_lenrek | i must make my silly hack more fool proof | 20:52 |
| minute | i really really should get the new battery board ready for sale | 20:52 |
| cinap_lenrek | is it possible to detect if the batteries are completely disconnected? | 20:53 |
| minute | what do you mean? | 20:53 |
| cinap_lenrek | i basically only need that hack when batteries are disconnected | 20:53 |
| cinap_lenrek | or other way around | 20:54 |
| cinap_lenrek | check if we run from barrel jack power | 20:54 |
| cinap_lenrek | yeah | 20:54 |
| cinap_lenrek | that is something the lpc should know | 20:55 |
| cinap_lenrek | lemme check the code | 20:55 |
| cinap_lenrek | sorry for the noise | 20:55 |
| cinap_lenrek | minute: thanks for the link! | 20:55 |
| cinap_lenrek | minute: how does it work tho? the lpc itself can drain the batteries no? | 20:59 |
| cinap_lenrek | minute: once we'r in brownout, we cant rely on its firmware to kill power | 20:59 |
| minute | cinap_lenrek: the lpc will release the enable pulldowns and the 5V and 3V3 will go wild and drain the power | 21:00 |
| Boostisbetter | ahhh, I have always just been really careful, and kept a good eye on battery levels. if I knew I wasn't goign to be messing with it for a while I put on AC just to be safe. The battery controller always seemed to do a good job of keeping them charged without overheating anything. | 21:04 |
| cinap_lenrek | wouldnt you need some electrical circuitry to stop the lpc from starting? | 21:06 |
| cinap_lenrek | or is it a non issue and it would take like weeks until the lpc itself would drain the batteries? | 21:07 |
| + mark_ (~mark@178.226.90.55) | 21:13 | |
| * mark_ -> mjw | 21:14 | |
| - cinap_lenrek (QUIT: Read error: Connection reset by peer) (~cinap_len@216.red-79-144-163.dynamicip.rima-tde.net) | 21:26 | |
| + MajorBiscuit (~MajorBisc@46-229-126.internethome.cytanet.com.cy) | 23:15 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!