#soylent | Logs for 2026-11-15

« return
[00:06:54] <AlwaysNever> damn, my Chromebook rebooted itself AGAIN. Well, at least now the screenshot functionality is working again.
[00:50:06] -!- justaperson has quit [Quit: justaperson]
[01:00:11] -!- bender has quit [Remote host closed the connection]
[01:00:20] -!- bender [bender!bot@Soylent/Bot/Bender] has joined #soylent
[01:01:21] -!- Loggie [Loggie!Loggie@Soylent/BotArmy] has joined #soylent
[05:42:19] -!- chromas2 has quit [Ping timeout: 265 seconds]
[05:42:31] -!- chromas [chromas!~chromas@Soylent/Staph/Infector/chromas] has joined #soylent
[05:42:31] -!- mode/#soylent [+v chromas] by Imogen
[08:09:16] <prg> random reboots sounds like a hardware issue, so installing linux might not help
[09:01:40] -!- guy__ [guy__!~guy@the.abyss.stares.back] has joined #soylent
[09:04:21] -!- Runaway has quit [Ping timeout: 265 seconds]
[11:22:16] <AlwaysNever> prg: I rather think my Chromebook's sudden reboots are due to RAM starvations, for I use it's "Linux Developer Environment" heavily with several Chromium instances/profiles with many tabs - because the native Google Chrome web browser of ChromeOS does not allow to have different profiles.
[11:22:54] <AlwaysNever> this Chromebook has 8 GB of RAM
[11:25:55] <AlwaysNever> then again, I have a HP Elitebook 840 G1 laptop with 8 GB of RAM and Windows 10, stable as a rock and suffering the same kind of usage without any hiccup whatsoever.
[12:19:27] -!- justaperson [justaperson!~justapers@2600:100c:a220:qjuh:vjmp:krph:gzug:tvxm] has joined #soylent
[12:20:10] -!- justaperson has quit [Client Quit]
[12:26:42] <fab23> AlwaysNever: did Google not abandon ChromeOOS, or will soon do?
[12:51:38] <AlwaysNever> fab23: yes, the are "transitioning" to GoogleBooks with and OS based on Android - but they also have pledged to support current ChromeOS install until 2033 (and so says my ChromeBook in its Settings).
[12:51:45] <AlwaysNever> *they are
[12:52:56] <AlwaysNever> which is a good thing, because I don't like rolling releases and this I hope means current ChromeOS is going to be receiving "new features", much like Windows 10.
[12:53:11] <AlwaysNever> *is NOT going to be receiving
[12:56:43] <fab23> Ah, I did not follow after the initial reporting, but it seems that some Schools have complained with the initial early and sudden end of ChromeOS.
[13:10:43] <Ingar> Live by the Google, die by the Google
[13:13:21] -!- chromas2 [chromas2!~chromas@Soylent/Staph/Infector/chromas] has joined #soylent
[13:13:21] -!- mode/#soylent [+v chromas2] by Imogen
[13:14:43] -!- chromas has quit [Ping timeout: 265 seconds]
[13:19:30] -!- chromas2 has quit []
[13:23:59] <fab23> Ingar: or switch to Microsoft :)
[13:53:03] <prg> rebooting when out of memory is a nice alternative to freezing while swapping to death for a few days like the average desktop linux likes to do
[15:10:14] <AlwaysNever> I would appreciate a warning to the user about too high memory usage before the reboot threshold is reached...
[15:12:37] <AlwaysNever> it looks like ChromeOS is based in Gentoo Linux and uses upstart instead of systemd... go figure.
[15:22:22] <fab23> would you like to have systemd? (-:
[15:31:56] <AlwaysNever> no thanks! :-)
[15:33:52] <AlwaysNever> Alright, It seems the logs of the host system in ChromeOS can be perused in Google Chrome -> chrome://system -> syslog. I'm now waiting for the next crash, and see if there is any OOM condition registered...
[21:12:53] <AlwaysNever> What I suspected: 026-11-15T21:05:05.219133Z INFO resourced[3346]: New memory pressure signal to Chrome: DiscardUnprotected, 181 KB
[21:14:15] <AlwaysNever> about 30 tabs in Chromium in the "Linux environment", and it freezes
[21:14:17] <AlwaysNever> lame
[21:14:53] <AlwaysNever> at least this time it has not rebooted, but the "linux apps" are frozen
[21:15:46] <AlwaysNever> 2026-11-15T21:05:25.263964Z INFO vm_concierge[4161]: VMMMS:[1,kill,CachedTab,190MB]
[21:16:15] <AlwaysNever> 2026-11-15T21:07:46.181357Z INFO vm_concierge[4161]: Received request: SetVmCpuRestriction
[21:18:59] <AlwaysNever> And then, inside the Linux VM I get this: Nov 15 22:17:50 penguin kernel: virtio_balloon virtio7: Out of puff! Can't get 1 pages
[21:19:10] <AlwaysNever> "Out of puff!" LOL
[22:04:15] -!- chromas [chromas!~chromas@Soylent/Staph/Infector/chromas] has joined #soylent
[22:04:15] -!- mode/#soylent [+v chromas] by Imogen
[23:08:24] -!- mrpg [mrpg!~mrpg@Soylent/Staff/Editor/mrpg] has joined #soylent
[23:08:24] -!- mode/#soylent [+v mrpg] by Imogen
[23:57:58] <mrpg> Hermes:Without my body, I'm a nobody.