#Journalctl
Nov 02 17:05:12 linux-cydu kernel: Spectre V2 : Spectre mitigation: LFENCE not serializing, switching to generic ret>
Nov 02 17:05:12 linux-cydu kernel: Spectre V2 : Mitigation: Full generic retpoline
Nov 02 17:05:12 linux-cydu kernel: Spectre V2 : Spectre v2 / SpectreRSB mitigation: Filling RSB on context switch
Nov 02 17:05:12 linux-cydu kernel: Freeing SMP alternatives memory: 32K
Nov 02 17:05:12 linux-cydu kernel: process: System has AMD C1E enabled
Nov 02 17:05:12 linux-cydu kernel: ..TIMER: vector=0x30 apic1=0 pin1=0 apic2=-1 pin2=-1
Spectre is some hardware vulnerability I’ve read about. Can someone explain this more clearly? And if I have anything to worry about. The newer hardware (main linux) doesn’t mention this error.
Nov 02 17:05:12 linux-cydu kernel: AGP: Checking aperture...
Nov 02 17:05:12 linux-cydu kernel: AGP: No AGP bridge found
Nov 02 17:05:12 linux-cydu kernel: AGP: Node 0: aperture [bus addr 0x1408000000-0x1409ffffff] (32MB)
Nov 02 17:05:12 linux-cydu kernel: Aperture beyond 4GB. Ignoring.
Nov 02 17:05:12 linux-cydu kernel: AGP: Your BIOS doesn't leave an aperture memory hole
Nov 02 17:05:12 linux-cydu kernel: AGP: Please enable the IOMMU option in the BIOS setup
Nov 02 17:05:12 linux-cydu kernel: AGP: This costs you 64MB of RAM
I don’t have AGP hardware. I think. My memory is only 4gb. Do I need to enable this? Assuming the BIOS has the setting.
Nov 02 17:05:12 linux-cydu kernel: mtrr: your CPUs had inconsistent variable MTRR settings
Nov 02 17:05:12 linux-cydu kernel: mtrr: probably your BIOS does not setup all CPUs.
Nov 02 17:05:12 linux-cydu kernel: mtrr: corrected configuration.
2.3 ghz dual cpu. I need to know if linux uses both cpu’s.
Nov 02 17:05:13 linux-cydu kernel: ata1: softreset failed (device not ready) {red text}
Nov 02 17:05:13 linux-cydu kernel: ata1: applying PMP SRST workaround and retrying
This means? FYI, I’m having a problem with reboot and shutdown freezing after ‘:rebooting.’ or ‘:shuting down.’ I’m trying to find the source.
Nov 02 17:05:54 linux-cydu pulseaudio[2329]: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop>
Nov 02 17:05:54 linux-cydu dbus-daemon[1226]: [system] Failed to activate service 'org.bluez': timed out (service_st>
Nov 02 17:05:54 linux-cydu kdeinit5[2228]: org.kde.bluez: PendingCall Error: "Failed to activate service 'org.bluez'>
All sound systems seems to working. What does this mean?
Yes, both versions of Spectre affect “all” Intel x86/x64 CPUs manufactured throuugh 2017 and as you’may observe is not a problem with CPUs shipped this year (2028). The vulnerability cannot be patched or otherwise “fixed” properly, the flaw is fundamental to how CPUs have worked in the past. So, the problem is continually addressed doing the next best thing… If the problem itself can’t be fixed, then all known and published ways to exploit the flaw is being blocked, ant that is what you see. For older CPUs, this will be a constant issue, whenever some new way is discovered to exploit, a new firmware patch will be issued.
You should follow the instructions to open and assign that memory space in your BIOS for your AGP. How do you know, are you <sure> your Graphics card doesn’t use AGP? And, IIRC (may be wrong) the address space is automatically reserved so if your hardware can use the space, then make it available… otherwise your graphics card will use a memory space that might have otherwise been available to something else. <That’s> how you lose 64Mbytes if RAM. https://en.wikipedia.org/wiki/Accelerated_Graphics_Port https://en.wikipedia.org/wiki/Input–output_memory_management_unit
Yes, Linux is like most contemporary OS is SMP https://en.wikipedia.org/wiki/Symmetric_multiprocessing
You can use an app like top to monitor how much activity is running in each of your CPU cores.
In very rare cases, you may be running such an important application that you might want to assign that app to run exclusively on specific cores or CPUs, and in Linux you can do that… But otherwise the typical Linux system will assign processes to the best core available.
Don’t know about your softreset error.
The last error is something about your pulseaudio and bluetooth and KDE.
Maybe you need to configure something, maybe you should disable, you’ll have first identify the bluetooth radio on your system and what you’re doing with it.
This CPU cost lot of money at the time. I would need to find one made in 2018, if any newer 2018 ones have been made.
Yes, Linux is like most contemporary OS is SMP
https://en.wikipedia.org/wiki/Symmetric_multiprocessing
You can use an app like top to monitor how much activity is running in each of your CPU cores.
In very rare cases, you may be running such an important application that you might want to assign that app to run exclusively on specific cores or CPUs, and in Linux you can do that... But otherwise the typical Linux system will assign processes to the best core available.
How do tell what what core is being used? ‘top’ doesn’t show that, only one core is being displayed.
I’m getting some kind cpu hardware error. I can’t find it with ‘journalctl’.
The last error is something about your pulseaudio and bluetooth and KDE.
Maybe you need to configure something, maybe you should disable, you'll have first identify the bluetooth radio on your system and what you're doing with it.
I have wireless card, but it’s not being used. This wireless card is off? I never set anything. I use only ethernet connections.
Please, I’ve asked you about this over and over again: Do not post interpreted stuff, post real output that proves what you assume/suspect. From what I’ve seen your system(s) are by no means default installs with all the tinkering.
I tend to agree with mrmazda in the idea that this much trouble with a basic install is not normal. Please do yourself a favor, perform a clean install from a checked iso download, a clean /home and start from there.
Yes. P-L-E-A-S-E follow proper forum etiquette! And, the rules about being polite means answering – politely – any questions you are asked by someone trying to help you, do NOT leave anything out. And give the full output of what you are asked for, including the command and its results. In Code Tags.
And, if you make a change after asking the question, ALWAYS provide that information and the results, in full.
Because you do not do the above, your threads seem to often go on forever, consuming a lot of the volunteers’ time, and consuming a lot of the openSUSE Forums resources.
I only have so much time enter messages. I read as much as I can and come back to next question later. I read every thing in time.
Please, I’ve asked you about this over and over again: Do not post interpreted stuff, post real output that proves what you assume/suspect. From what I’ve seen your system(s) are by no means default installs with all the tinkering.
I tend to agree with mrmazda in the idea that this much trouble with a basic install is not normal. Please do yourself a favor, perform a clean install from a checked iso download, a clean /home and start from there.
In the past, I would just full do reinstall, wiping the whole hard drive. It usually works well. Someone said, paraphrasing, “that’s what mswin people do.” As I said, I do read all messages.
The tinkering with background services was after the laptop crash.
I was thinking about that. I will try that and post on here. For now, I’m trying to get caught up on all the posts i’v made.
