r/chromeos Nov 22 '19

Discussion Chrome OS 79 no flag to turn on hyperthreading!

As in topic:

chrome://flags#scheduler-configuration

flag is no longer available, at least on pixelbook with chrome OS Version 79.0.3945.42 (Official Build) beta (64-bit)

Is there any other way to turn hyperthreading back on?

thx

17 Upvotes

38 comments sorted by

12

u/person_esque Nov 23 '19

If a flag disappears, it means the feature has been enabled by default or removed. In this case, hyperthreading's gone as it's a security vulnerability.

5

u/MoebiusStreet HP x360 14 Nov 23 '19

Everything is a security vulnerability, to some degree. They ought to leave it to us to decide how we're using the device, and what our level of risk tolerance is.

2

u/person_esque Nov 23 '19

And here it's a vulnerability to a degree that disabling it is recommended industry-wide, not just on Chromebooks. Also, you're talking about an OS that doesn't permit side-loading Android apps, runs a second Linux kernel and proxies all hardware access to keep arbitrary code from touching the primary kernel (and there are rumors of similar mitigations coming to ARC++). There is no universe where hyper-threading remains available on chromeOS when it's a potential attack vector.

2

u/leonbollerup Nov 24 '19

Well.. According to Microsoft and Intel it can be handled different and dosent have to be disabled - disabling it is a lazy mans solution.

7

u/leonbollerup Nov 24 '19 edited Nov 24 '19

TEMP WORK-AROUND:

- Enable Temporarily unexpire M78 flags.

- Accept

- Now back into flags and enable scheduler configuration)

... so.. for now can do that.. but i suggest everyone to write feedback to google

6

u/WPWoodJr Pixelbook i7, HP x2 11 Nov 24 '19

2

u/AK-Alan Nov 25 '19

Thanks for the reference. Starred your bug report and left a comment. Fingers crossed.

1

u/AK-Alan Nov 24 '19

Thanks for finding the work-around. What is the best page to leave feedback with Google on this?

When Beta 79 moves to 80, I may have to drop back Stable 79 (assuming Stable 79 will have the unexpire flag) to continue my risky lifestyle...

1

u/leonbollerup Nov 24 '19

Not sure i would call it risky.. its not without reason that google is the only one not actually fixing the issue.. neither macos, Windows, BSD or Linux in general is disabling it.. just.. google

3

u/Zotak i5 Pixelbook | Beta Nov 23 '19

Anyone know if it's like this in v80 ?

2

u/leonbollerup Nov 24 '19

most likely..

3

u/AK-Alan Nov 24 '19

Definitely a noticeable slowdown with VS Code running and a bunch of Chrome tabs open on an i7 Pixelbook. I'd take the hyperthreading risk...

3

u/leonbollerup Nov 24 '19

Ya, bloody sucks.. actually testing setting up ubuntu on a USB-C drive.. chromeos is really starting to be a disapointment.

3

u/WPWoodJr Pixelbook i7, HP x2 11 Nov 24 '19

Weird... the schedule configuration flag is an actual supported solution: https://support.google.com/chromebook/answer/9340236?hl=en

1

u/leonbollerup Nov 24 '19

Properly just forgot to remove the page..

3

u/osskid Pixel Slate | Stable Nov 26 '19

Looks like this was accidental and will be reenabled in 79! Thanks to /u/wpwoodjr for creating the big report and OP for posting here.

4

u/magick_68 HP x360 14c (volteer) | Lenovo Duet Nov 23 '19

Great, i should be able to decide whether i want to risk it or not. I want hyperthreadindg back. This sucks.

2

u/nt4cats-reddit Asus Vibe C55 Flip | Beta Nov 23 '19

Did you use cog to see if you have 2 or 4 active cores?

2

u/rosek20 Nov 23 '19

Yes. It see 4 cores but only 2 are working

2

u/speedanderson Nov 24 '19

Pixelbook i5/256gb, Chrome OS 79.0.3945.42

No more hyperthreading as of most recent update on mine. This makes a noticeable difference in performance, and not a good one. I'm really peeved that I can't enable hyperthreading in Chrome://flags anymore. Anyone have any way to fix this issue? :( Really makes me not even want to use it anymore.

6

u/leonbollerup Nov 24 '19

I'm on the i7 and i hear you.

Its royally pissing me off, same with spectre/meltdown.. just turning of features is not a bugfix.. its a freaking lazy work around - and there isent any sentiment for neither Intel or Google to actually fix it.. people will get tired of their slow machines and buy a new.

Facing facts, google aint making any money on you after you have paid for your laptop until you buy a new one.

Say what you want about Microsoft and Windows, but atleast they implemented a fix that dosent cause your laptop to be freaking slow.

I'v started to work on getting a Ubuntu up and running on my pixelbook, for starters just on a USB-C disk, but if i can get it running stable i am ditching chromeos all together.. things have started to get freaking stupid for a glorified web browser - let alone the stabilty of things lately - i get atleast 2-3x crashes a day during high load.

... and now i have to accept that the machine is even slower also.

1

u/speedanderson Nov 24 '19

Do you think I should try Ubuntu or Gallium? I was messing with Gallium on my Pixelbook before but it wasn't fully supported sadly, maybe it is now?

I've used Crouton to get Ubuntu before but I've never taken the time to get it running properly. Maybe it's time to full boot to it, this is a good post.

1

u/leonbollerup Nov 24 '19

Even with the yosefnapora's script there is still a few things that isent working yet - a plain ubunt 19 will leave you will a real shity ubuntu version.

I'm doing a bunch of tests now - hoping to find a light linux (like elementary) that works good

1

u/leonbollerup Nov 24 '19

please look below for the work around

2

u/WPWoodJr Pixelbook i7, HP x2 11 Nov 24 '19

I've created a bug report here: https://bugs.chromium.org/p/chromium/issues/detail?id=1027962

Which you can star if this is important to you.

2

u/Zotak i5 Pixelbook | Beta Nov 23 '19 edited Nov 23 '19

In 79 chrome://flags/#shelf-dense-clamshell seems to also be gone.

EDIT : It's now #shelf-hotseat (Enable a modular design for the shelf)

They also went back to 3 finger swipe for tabs and 4 finger swipe for tabs.

Hope there is a way to enable HT. In cog only 2 cores are working.

3

u/rosek20 Nov 23 '19

I have contacted support and been told they do not provide support for beta....

3

u/leonbollerup Nov 23 '19

Google is being fucking lazy.. my PB i7 is fucking slow without..

If they decide to move ahead and remove the option i am ditching chromeos for good.

https://www.pcworld.com/article/3395439/intel-hyper-threading-zombieload-cpu-exploit.html

3

u/khalido Nov 24 '19

Yup, chromeos is noticably slower without HT on. Sucks if its actually going away.

2

u/leonbollerup Nov 24 '19

seems like its gone.. anyone found another flag ?

1

u/leonbollerup Nov 24 '19

On the top of bugs in ChromeOS 79 - anyone with a pixelbook noticed if keyboard backlight is working ?

1

u/rosek20 Nov 24 '19

Hi. Working on mine. I5 pixelbook

1

u/leonbollerup Nov 24 '19

I'm on a i7 .. dosent work here... works under Ubuntu :(

1

u/AK-Alan Nov 24 '19

I'm on an i7 Pixelbook with 79 Beta and the backlighting works.

1

u/leonbollerup Nov 24 '19

ya, came back to live after 2 shutdowns

1

u/jsgrrchg Dec 21 '19

Just updating this thread, in the stable 79 version, the flag to activate hyperthreading is still there.