Slashdot Mirror
Linux 4.18 Preparing Many New Features While Dropping 100k+ Lines of Code (phoronix.com)
An anonymous reader writes: Linux 4.18 development is going strong with recent 4.18-rc1 release. This kernel cycle has dropped 107,210 lines of code so far but Linux 4.18 is adding many new features. The kernel is coming in lighter as a result of the LustreFS code being removed and other code cleanups. On the feature front, Phoronix reports, "ew AMDGPU support improvements, mainlining of the V3D DRM driver, initial open-source work on NVIDIA Volta GV100 hardware, merging of the Valve Steam Controller kernel driver, merging of the BPFILTER framework, ARM Spectre mitigation work, Speck file-system encryption support, removal of the Lustre file-system, the exciting restartable sequences system call was merged, the new DM writecache target, and much more."
Yeah man, gimme another hit of that v3d drm
With Intel shutting down their commercial support business last year and now LustreFS being removed from the mainline kernel is Lustre dead as a common solution? What is replacing it as a scalable FS in HPC applications?
There are 4 boxes to use in the defense of liberty: soap, ballot, jury, ammo. Use in that order. Starting now.
By removing features from kernels you force people to either use older kernels or force them to back port back to the current kernels. This creates a mess of patches and security holes. With Linux deployments now in the billions due to Android it is a bad idea to remove features as someone is using it somewhere.
The older AMD Stoney Ridge and Bristol Ridge AMD APUs finally have temperature reporting support.
Stoney Ridge is old. Bristol Ridge is available on AMD's newest platform, AM4.
Goodbye, Slashdot!
Have a similar problem/question. Need Ryzen support for a Dell Insipron 1700. Just spent a weekend trying to get it to work, ending up frustrated/disappointed. Can anyone shed some light on the Ryzen support?
I thought I had that bug, but It was fixed by switching wireless PCI cards. The ATH9K driver was the culprit on my system.
It was pretty weird because the symptoms were the same-- Only crash at idle or near idle. As long as the CPU was under heavy load, the system ran flawlessly. I tried everything I could find online to mitigate it including the "rcu_nocbs=0-15" parameter.
I finally noticed some ath9k messages in the logs near the time of the crash, so I bought an intel PCI wireless adapter and replaced my old one. Haven't had a crash since (that I recall). This system is up 24/7 except for kernel updates and is running Xubuntu 18.04 now. (It was on Xubuntu 16.04 at the time of the problems and my solution).
God is imaginary
It looks like anything you do in the kernel is a workaround rather than a fix. So I wouldn't expect it to be "fixed" in the kernel, since it's not really a kernel problem.
From what I can gather, until AMD does a firmware fix (or hardware?) the best option is to select "typical current idle" in bios.
Of course, if the rcu workaround is working for you, you might just leave it at that until AMD really fixes the issue.
How can I tell if the bug that was crashing Ryzen processors at idle has been fixed?
In 4,15, Ryzen users had to put in a boot option
"rcu_nocbs=0-15
(this case for 8 cores =0-11 for a six core...)
I had this problem too and the rcu_nocbs=0-15 didn't fix entirely the problem. You need zenstates to turn off the C6 power saving state.
Here's the systemd unit file:
[Unit]
/usr/local/src/ZenStates-Linux-master/zenstates.py --c6-disable
Description=Turn off power saving C6 state
[Service]
Type=oneshot
StandardOutput=syslog
ExecStart=/usr/bin/python
[Install]
WantedBy=basic.target
OK, I get it that you're an Nvidia guy, but no need to rub it in my face.
Escher was the first MC and Giger invented the HR department.
No, I'm just tired of squinting at attached screenshots rather than the user with a problem just being able to cut paste 160 characters of text into an email.
That and clearly telling the user to click on the thing that looks like a squished beetle and they keep clicking on the deformed grasshopper.
Give us a call after you spend some time maintaining a server you have never actually touched or seen on the other side of the country, then tell us how much you like the gooey interface.
But be careful, the NSA also provided advice to NIST that resulted in significantly weakening their crypto standards.
Whoosh
Unless you tried a known good Atheros chip based NIC of the same model and manufacturer you don't know if it was a driver issue or a hardware issue. Most of the times my drivers were "having issues" it turned out to be hardware issues. That obviously doesn't mean this isn't a driver issue either.
Guns don't kill people; Physics kills people! - John Lithgow as Dick Solomon on Third Rock From The Sun
You obviously haven't reached a skill level where the significant advantages of text based admin come in. Sometimes enterprise means resilliant and effective, but quite often it means brittle and catering to the lowest common denominator.
It''s fine if users use a GUI, but the system itself should be text based so a skilled admin has a chance of actually fixing it when it's not working right. Even MS is starting to recognize that.
As for LAN/WAN, step one when there is a problem is ditch the GUI and get a command line. If you actually understand the network and how the routers work, that will give you the tools you actually need to solve the problem. Use the GUI to check status when things are working well. If you need a picture of a thermometer to know when the temperature is too high, you'be already lost.
Except that SHA is a hash, not an encryption scheme.
Any hash function can be turned into a stream cipher by running it in counter mode. This construction, called "Snuffle" by Daniel J. Bernstein, was the insight that led to the United States loosening its cryptography export regulations in the late 1990s. See Bernstein v. US .
What is it about deleting reams of code that arouses me? This is a story I can cheer.
I object to power without constructive purpose. --Spock
This kernel cycle has dropped 107,210 lines of code so far but Linux 4.18 is adding many new features. The kernel is coming in lighter as a result of the LustreFS code being removed
Yah right. This is nothing to be proud of. It is a failure of the community, to be unable to maintain Lustre. Now it goes more proprietary than it already was. Shame on Linus and his hangers-on.
Some weeny with mod points thinks Linus is perfect. No, far from it. Linus is great, but far from perfect, and the whole Lustre thing was obviously mismanaged, including by Linus and hangers-on like Gregkh.
When all you have is a hammer, every problem starts to look like a thumb.
Or the Lustre guys could have gotten their shit together and it could have been put in the mainline kernel.
They could have been encouraged to do that, instead of just throwing the baby out with the bathwater which is what idiot Gregkh did, because he has not got a fucking clue that this is just as important as the stuff he actually understands. Problem is, he's a bit of a dunce. You can see that in a lot of stuff he does. Crappy coder too.
When all you have is a hammer, every problem starts to look like a thumb.
Late reply, but this Atheros card came out of the predecessor of my Ryzen machine (Intel core i5). It worked in that setup without issue with the same OS.
After I replaced the wireless card in my Ryzen machine, I switched my old Atheros card back to the Intel computer where it works flawlessly.
God is imaginary
Almost forgot-- Unloading the ath9k kernel module without replacing the hardware also solved the problem.
God is imaginary