Spyke

Syndicated from the fediverse. Read and engage on the original instance.

View original on lemmy.ca
linuxmint·Linux MintbySnowballfighter

Kernel Panic, BIOS, & confusion

I had a kernel panic and am trying to find some beginner level help for that and possibly updating BIOS to help fix it. Linux Forums, while trying to be helpful are assuming I know anything and I'm just getting in way over my head. Suggestions are either so complicated and vague I can't follow them, or merely saying why those suggestions won't work. It takes me hours of research to try and understand how to make every command work. I'm feeling desperate and freaked out my work laptop is going to break. I could just be flipping out over nothing but I don't understand what is going on.

I have a Legion Pro 5 16ARX8 - Type 82WM Running Linux mint.

Here's an example of errors messages I'm getting in dmesg:

[ 6.035147] amdgpu 0000:05:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data [ 10.042930] amdgpu 0000:05:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data [ 0.276297] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.PB2], AE_NOT_FOUND (20251212/dswload2-162) [ 0.276304] ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20251212/psobject-220)

Any help is appreciated.

UPDATE: Got the laptop cleaned and got 4 passes on memtest. The tech said, the 3 years of cat hair and dust was likely the culprit in the Kernel panic during a large file copy paste. I will be getting it professionally cleaned regularly and will learn how to copy/paste 400 gb of data more responsibly in the future. Thankyou everyone who lent a hand, you helped during a very stressful few days.

View original on lemmy.ca
13
Comments14

14 replies

CameronDev
programming.dev
[ 6.035147] amdgpu 0000:05:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data 
[ 10.042930] amdgpu 0000:05:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data 
[ 0.276297] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.PB2], AE_NOT_FOUND (20251212/dswload2-162) 
[ 0.276304] ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20251212/psobject-220)

Triple backticks to get a code block, makes it a bit easier to read.

Are you getting an actual kernel panic, or just this error in the logs? Error is probably no big deal unless you are getting a panic/crash. Take a photo of the kernel panic screen if you can.

Have you been trying to install a driver or something like that? Or is this a fresh install?

7
Snowballfighterreply
lemmy.ca

The only thing I was doing previously was trying to set up a jellyfin server at the time (storage is on an external HD) I have moved Jellyfin to another laptop. I have had Mint installed for most of the year and it has been excellent with a few tiny bluetooth issues that I just live with.

This was the screen when the troubles started.

I have only gotten this screen the one time. While I was desperately trying to get a back up saved, the laptop kept shutting down during the heavy data transfer with a black screen and this message:

[ 6.169528] amdgpu 0000:05:00.0: [drn] ERROR dc_dmub_srv_log_diagnostic_dat a: DMCUB error - collecting diagnostic data_`

I ended up having to reboot with the power button, and finally got a backup.tar sorted out, and actually have been using it lightly, but I will have to be using it for some graphics heavy work in the coming week, so I was hoping to get into some fixin' before then.

Thanks for having a look.

2
CameronDevreply
programming.dev

Ok, attempted to kill init is a different kind of panic, your drivers are probably fine. Did you get that as it booted up? You turned it on, and it quickly dropped you into a shell, and you pressed ctrl-c/d at that shell, and got the panic?

I'm suspecting some kind of hardware issue tbh, either SSD failing (failing during copy), or maybe GPU overheating? Overheating is the easiest to fix if you are comfortable opening the laptop, cleaning the fans (don't compressed air it, that can kill fans, toothbrush and paper towel is safest) and heat sinks, and then redoing the thermal paste.

If you can boot it up, run the smart tests on the SSD to try rule that out.

2
Snowballfighterreply
lemmy.ca

Purple screen was during a file transfer, I wasn't in the room.

2
CameronDevreply
programming.dev

Oh, thats very strange then. I'm still kinda leaning toward hardware being the issue, is it an old laptop?

2
CameronDevreply
programming.dev

Seems young for the SSD to die, but next time its on, check the disk health.

And if it tends to get hot, definitely look into cleaning the vents and fans.

3
Snowballfighterreply
lemmy.ca

Yeah it does get quite hot and I live in a dry dusty climate with cats, A cleaning is something I think it needs regardless. I actually got the suggestion elsewhere for disk health and using smartctl I got this but I had just turned it on to perform the test:

Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Number:                       SAMSUNG MZVL21T0HCLR-00BL2
Serial Number:                      S64NNF0W102956
Firmware Version:                   CL1QGXA7
PCI Vendor/Subsystem ID:            0x144d
IEEE OUI Identifier:                0x002538
Total NVM Capacity:                 1,024,209,543,168 [1.02 TB]
Unallocated NVM Capacity:           0
Controller ID:                      6
NVMe Version:                       1.3
Number of Namespaces:               1
Namespace 1 Size/Capacity:          1,024,209,543,168 [1.02 TB]
Namespace 1 Utilization:            975,972,904,960 [975 GB]
Namespace 1 Formatted LBA Size:     512
Namespace 1 IEEE EUI-64:            002538 b131b883e3
Local Time is:                      Thu Oct 22 07:40:49 2026 CDT
Firmware Updates (0x16):            3 Slots, no Reset required
Optional Admin Commands (0x0017):   Security Format Frmw_DL Self_Test
Optional NVM Commands (0x0057):     Comp Wr_Unc DS_Mngmt Sav/Sel_Feat Timestmp
Log Page Attributes (0x0e):         Cmd_Eff_Lg Ext_Get_Lg Telmtry_Lg
Maximum Data Transfer Size:         128 Pages
Warning  Comp. Temp. Threshold:     76 Celsius
Critical Comp. Temp. Threshold:     87 Celsius

Supported Power States
St Op     Max   Active     Idle   RL RT WL WT  Ent_Lat  Ex_Lat
 0 +     8.37W       -        -    0  0  0  0        0       0
 1 +     8.37W       -        -    1  1  1  1        0     200
 2 +     8.37W       -        -    2  2  2  2        0     200
 3 -   0.0500W       -        -    3  3  3  3     2000    1200
 4 -   0.0050W       -        -    4  4  4  4      500    9500

Supported LBA Sizes (NSID 0x1)
Id Fmt  Data  Metadt  Rel_Perf
 0 +     512       0         0

=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

SMART/Health Information (NVMe Log 0x02)
Critical Warning:                   0x00
Temperature:                        33 Celsius
Available Spare:                    100%
Available Spare Threshold:          10%
Percentage Used:                    4%
Data Units Read:                    101,262,490 [51.8 TB]
Data Units Written:                 76,489,619 [39.1 TB]
Host Read Commands:                 1,032,812,917
Host Write Commands:                1,764,682,616
Controller Busy Time:               16,337
Power Cycles:                       20,206
Power On Hours:                     2,606
Unsafe Shutdowns:                   311
Media and Data Integrity Errors:    0
Error Information Log Entries:      0
Warning  Comp. Temperature Time:    0
Critical Comp. Temperature Time:    0
Temperature Sensor 1:               33 Celsius
Temperature Sensor 2:               31 Celsius

Error Information (NVMe Log 0x01, 16 of 64 entries)
No Errors Logged

Self-test Log (NVMe Log 0x06)
Self-test status: No self-test in progress
Num  Test_Description  Status                       Power_on_Hours  Failing_LBA  NSID Seg SCT Code
 0   Short             Completed without error                 944            -     -   -   -    -
 1   Short             Completed without error                 939            -     -   -   -    -```
1
Consti
lemmy.world

ACPI errors are completely normal, most motherboards don't expose all the information Linux wants, just ignore them. Never seen the DMCUB error though, but as other users have said, that's not the kernel panic, just a (likely) unrelated error message that may or may not be significant. From a quick search, the error is a bug in recent kernels related to AMD GPUs, see e.g. https://www.reddit.com/r/archlinux/comments/1wetjg6/amdgpu_dmcub_error_fixed/

Edit: https://community.frame.work/t/system-gets-really-slow/61854/2 Try adding amdgpu.dcdebugmask=0x10 to the kernel boot parameters in /etc/default/grub

5
Snowballfighterreply
lemmy.ca

Only because I had ALOT of trouble editing fstab recently, I want to confirm if I am using the GUI instead of terminal that I right click the grub file, open as root, and add the line at the end and save correct? And then I assume I reboot, or is there a terminal command that refreshes? Just want to be clear as I get nervous with this kind of thing.

2
CameronDevreply
programming.dev

Open /etc/default/grub in the editor of your choice, GUI is fine.

Look for the line that starts with GRUB_CMDLINE_LINUX="...", and add the suggested change to the end of that line, but within the quotes. Save

Then in a terminal, sudo update-grub.

3

You reached the end

Kernel Panic, BIOS, & confusion | Spyke