[ Date Index ] [ Thread Index ] [ <= Previous by date / thread ] [ Next by date / thread => ]
On 28/10/2021 11:59, David Bell wrote:
Here is the output Comrade. Appreciate your perusal.
Ok there is actually some interesting stuff in here but as predicted, nothing actually "wrong" and certainly not any obvious runaway problems that would indicate storage subsystem issues.
root@Ermintrude-2:/home/grimpen# systemctl --failed UNIT LOAD ACTIVE SUB DESCRIPTION 0 loaded units listed.
Well that's a good start. Don't use root by the way, sudo exists for a reason.
root@Ermintrude-2:/home/grimpen# journalctl -p err -b -- Journal begins at Sat 2021-09-11 19:57:53 BST, ends at Thu 2021-10-28 11:45:28 BST. -- Oct 28 08:43:08 Ermintrude-2 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.GPP0.VGA], AE_ALREADY_EXISTS (20200925/dswload2-326) Oct 28 08:43:08 Ermintrude-2 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20200925/psobject-220) Oct 28 08:43:08 Ermintrude-2 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.GPP0.HDAU], AE_ALREADY_EXISTS (20200925/dswload2-326) Oct 28 08:43:08 Ermintrude-2 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20200925/psobject-220) Oct 28 08:43:08 Ermintrude-2 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.GPP0.VGA.LCD._BCM.AFN7], AE_NOT_FOUND (20200925/psargs-330) Oct 28 08:43:08 Ermintrude-2 kernel: ACPI Error: Aborting method \_SB.PCI0.GPP0.VGA.LCD._BCM due to previous error (AE_NOT_FOUND) (20200925/psparse-529) Oct 28 08:43:08 Ermintrude-2 kernel: ACPI Error: Evaluating _BCM failed (20200925/video-357) Oct 28 08:43:08 Ermintrude-2 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.GP17.VGA.LCD._BCM.AFN7], AE_NOT_FOUND (20200925/psargs-330) Oct 28 08:43:08 Ermintrude-2 kernel: ACPI Error: Aborting method \_SB.PCI0.GP17.VGA.LCD._BCM due to previous error (AE_NOT_FOUND) (20200925/psparse-529) Oct 28 08:43:08 Ermintrude-2 kernel: ACPI Error: Evaluating _BCM failed (20200925/video-357) Oct 28 08:43:08
These are all just noise from a buggy BIOS ACPI implementation - you see these on a lot of modern machines and it's nothing to worry about. Are you booting in BIOS or UEFI mode by the way? Switching to UEFI makes most of this stuff go away as well as being the correct way to run a computer in the 21st century.
Ermintrude-2 kernel: iwlwifi 0000:04:00.0: firmware: failed to load iwl-debug-yoyo.bin
Nothing to worry about - looks like it might be a serious failure to load wifi firmware but I imagine your wifi is working just fine. If not, now you know why it isn't. See:
https://forums.debian.net/viewtopic.php?f=16&t=149817 (-2) Oct 28 08:43:08 Ermintrude-2 kernel:
firmware_class: See https://wiki.debian.org/Firmware for information about missing firmware Oct 28 08:43:08 Ermintrude-2 kernel: kvm: disabled by bios Oct 28 08:43:08 Ermintrude-2 kernel: kvm: disabled by bios Oct 28 08:43:08 Ermintrude-2 kernel: kvm: disabled by bios Oct 28 08:43:08 Ermintrude-2 kernel: kvm: disabled by bios
Virtualization is disabled in your firmware. This isn't technically a problem if you don't ever use hypervisors but it really should be on: technology increasingly calls out to low level stuff like this and presumes it will always be there. Not a problem for you but Win10/11 require this feature to be enabled for things like WSL, WSA, Virtualization platform features, Security Isolation, etc.
Oct 28 08:43:09
Ermintrude-2 bluetoothd[601]: profiles/sap/server.c:sap_server_register() Sap driver initialization failed. Oct 28 08:43:09 Ermintrude-2 bluetoothd[601]: sap-server: Operation not permitted (1) Oct 28 08:43:10 Ermintrude-2 pipewire[750]: Failed to receive portal pid: org.freedesktop.DBus.Error.NameHasNoOwner: Could not get PID of name 'org.freedes> Oct 28 08:43:22 Ermintrude-2 pipewire[835]: Failed to receive portal pid: org.freedesktop.DBus.Error.NameHasNoOwner: Could not get PID of name 'org.freedes> lines 1-21/21 (END)
These last two aren't worth worrying about as they are minor glitches in subsystems you aren't using and don't care about. Bluetooth and PipeWire are working, just certain bits of them aren't. That's just log noise so discount it.
In short, except for some easily explicable error messages relating to system firmware (ACPI, Virtualization) and perhaps the poor choice of BIOS vs UEFI your system has a completely unremarkable and clean error log.
There is nothing wrong with your computer. Presuming it's still working of course.
Now you could dive way deeper - you haven't posted the SMART log from the SSD let alone started logging and tracking disk perf stats or examining scheduler behaviour. And trust me please: you don't need to.
THERE IS NOTHING WRONG WITH YOUR COMPUTER.The flashing case light is symbolic. It's not actually locked in a one-to-one relationship with disk access you know. Funnily enough your eyes couldn't keep up with the 400-550k IOPS an off the shelf SSD is capable of - and neither can any LED strobe that quickly. You are not actually 'seeing' anything other than a vague courtesy indicator from the system firmware that interposes itself between the access patterns of your storage subsystem and a 0.01p LED on the end of a wire that "stuff is happening". That's it. Your logs are clean and presuming the system works and your SMART data is ok you're worrying about nothing.
Simon's advice is solid: if it's bugging you, cover it up - or just disconnect it.
I am willing to be ANY money that over the next few weeks and months the pattern of that LED activity will change randomly and repeatedly. In 4 weeks you'll see a different pattern and will have completely forgotten this entire episode!
-- The Mailing List for the Devon & Cornwall LUG https://mailman.dcglug.org.uk/listinfo/list FAQ: http://www.dcglug.org.uk/listfaq