Yes, that is absolutely correct.
Yes, that is absolutely correct.
I do in fact use unrefined, brown cane sugar, although I have not tried panela specifically.
The one I use pretty much looks like this:
It’s an organic fair trade brand, but I’d have to look up where it is imported from.
As I said, I can’t imagine making it with any other kind of sugar any more. Sorghum seems like an interesting idea, might have to experiment with that.
The key to amazing banana bread is to make it with soft, brown sugar. The stuff that is clumpy, glistening with moisture, reminiscent of molasses. It adds so much to the flavor. And actual nuts, of course.
I’ll post some links, but it’s a pretty busy week for me already, so give me some time.
An interrupt is an input that can be triggered to interrupt normal execution. It is used for e. g. hardware devices to signal the processor something has happened that requires timely processing, so that real-time behavior can be achieved (for variable definitions of real-time). Interrupts can also be triggered by software, and this explanation is a gross oversimplification, but that information is what is most likely relevant and interesting for your case at this point.
The commands you posted will sort the interrupts and output the one with the highest count (via head -1), thereby determining the interrupt that gets triggered the most. It will then disable that interrupt via the user-space interface to the ACPI interrupts.
One of the goals of ACPI is to provide a kind of general hardware abstraction without knowing the particular details about each and every hardware device. This is facilitated by offering (among other things), general purpose events - GPEs. One of these GPEs is being triggered a lot, and the processing of that interrupt is what causes your CPU spikes.
The changes you made will not persist after a reboot.
Since this is handled by kworker, you could try and investigate further via the workqueue tools: https://github.com/torvalds/linux/tree/master/tools/workqueue
In general, Linux will detect if excessive GPEs are generated (look for the term “GPE storm” in your kernel log) and stop handling the interrupts by switching to polling. If that happens, or if the interrupts are manually disabled, the system might not react to certain events in a timely manner. What that means for each particular case depends on what the interrupts are being responsible for - hard to tell without additional details.
I shudder to think OP’s post was written by an actual person…
With type annotations, this problem is mostly alleviated in practice, while still keeping the productivity gains of duck typing.
For years, Intel’s compiler, math library MKL and their profiler, VTune, really only worked well with their own CPUs. There was in fact code that decreased performance if it detected a non-Intel CPU in place:
https://www.agner.org/optimize/blog/read.php?i=49&v=f
That later became part of a larger lawsuit, but since Intel is not discriminating against AMD directly, but rather against all other non-Intel CPUs, the result of the lawsuit was underwhelming. In fact, it’s still a problem today:
https://medium.com/codex/fixing-intel-compilers-unfair-cpu-dispatcher-part-1-2-4a4a367c8919
Given that the MKL is a widely used library, people also indirectly suffer from this if they buy an AMD CPU and utilize software that links against that library.
As someone working in low-level optimization, that was/is a shitty situation. I still bought an AMD CPU after the latest fiasco a couple of weeks ago.
Surely not. But also many employees won’t even ask for it, and change will only happen if people care about it.
So first, raise awareness, and naturally, implement those things at any companies you manage or own.
I’m not saying quit your job and become homeless if your employer won’t corporate with you on the issue. Everyone should think about how this could potentially affect them and what they can do within the constraints they operate in, though.
As someone else in this thread said, a separate (VLAN, guest) network for work devices, reasonable access rules etc. can go a long way. Eventually, I would like this to become unacceptable though.
No, have the company buy a laptop, and if necessary, also have them buy the hardware that allows for proper network separation, if not already available.
Just another thing to be aware of.
I know it is somewhat of an accepted practice, and a lot of people lack the means or the knowledge to handle it any other way, but I’d still like to raise awareness that you’re basically inviting a foreign actor into your network.
The days were people would trust corporations, including their employers, to be generally benevolent and to do the right thing are long over.
This is absolutely correct. Heck, you’re free to deny that based on any reasoning, maybe the shoddy icon of the work app doesn’t match your phone wallpaper.
The phone is your private property, if an employer requires an app to be installed to do your job, they can provide a phone.
I would also never let corporate IT manage a device, e. g. a laptop connected to my private network at home.
I am on my 4th personal TUXEDO laptop, never had any issues. I actually started giving them to the devs at my company, no complaints so far.
They don’t offer my choice of OS, and I wouldn’t use a preinstalled OS anyway, so I can’t comment on that.
Generally all correct, here is a resource with a lot of in-depth information and additional links:
https://batteryuniversity.com/article/bu-808-how-to-prolong-lithium-based-batteries
It’s not true that precision measurements are impossible with low value resistors, a lot of measurement equipment works exactly like that - it might just be more expensive than what the manufacturer is willing to budget for.
Tuxedo also offers products with an aluminum body, and while they do import the hardware from China, you get the local service and warranty guarantees any company in the EU must provide, so that’s fine by me.
Also, honest question: what do you think a unique laptop is, in particular when buying from a mass consumer brand like Lenovo? I really can’t figure out what that’s supposed to mean.
Oh, that makes everything a lot easier. The majority of the relevant settings will be in your home folder then, i. e. in the ${HOME}./.config folder, while some might also be in ${HOME}/.local/share etc.
You probably want to backup the whole home folder anyway, so that would pickup most of your settings. In order to make that work on a different system, you would have to install all applications you were using on the tablet as well. Luckily, software installation in Linux is pretty easy, so you can export a list of installed applications from the Surface and then re-install them on your target system before migrating your home folder. The software list should become part of your backup. See e. g. https://unix.stackexchange.com/questions/82880/how-to-replicate-installed-package-selection-from-one-fedora-instance-to-another for an idea of how to perform this.
I have used this approach in the past and it will get you 95% there. There might be some global system settings that you’d like to also transfer to your new system, but you can add those as you discover you miss them on the target system.
In general, no, this won’t work. In your case, you’re lucky since at least the Surface Go is using an x86 CPU, so it’s not completely out of the question, but transferring the image as-is to a completely different device typically does not work without modification.
Simple example: your target device might not refer to existing hardware (let’s say a storage medium) in the same manner as your old device, so the existing references in your cloned image won’t work. There are other issues of course, e. g. missing drivers for different hardware present on the target device.
It’s possible to modify the image so it would boot, but given the Surface runs Windows, that’s going to be a chore. I’d consider this an interesting project if bored on a slow weekend, but I’d most likely just do a filesystem backup of relevant data and call it a day.
I was not ready for how many stock photos they produced.