jankdc
January 7, 2025, 5:21pm
1
I’ve been having trouble with Bluefin freezing on my latest install. I’m using a Lenovo ThinkCentre M715Q 256GB, AMD Ryzen 5 2400GE, 3.2 GHz, 16gb Ram. Is there a way to Ctrl+Alt+Delete to get it unstuck? I remember using a way to kill a program when I used KDE years ago. Also, where would I look to determine what is causing it to freeze? So far, pushing the power button to shut it down is the only way to get out of it. When I reboot, it’s working again.
Thanks.
System Details Report
Report details
Date generated: 2025-01-07 12:59:33
Hardware Information:
Hardware Model: Lenovo ThinkCentre M715q
Memory: 16.0 GiB
Processor: AMD Ryzen™ 5 PRO 2400GE w/ Radeon™ Vega Graphics × 8
Graphics: AMD Radeon™ Vega 11 Graphics
Disk Capacity: 2.3 TB
Software Information:
Firmware Version: M1XKT63A
OS Name: Bluefin 40 (FROM Fedora Silverblue)
OS Build: eb2ac92
OS Type: 64-bit
GNOME Version: 46
Windowing System: Wayland
Kernel Version: Linux 6.11.8-200.fc40.x86_64
1 Like
jankdc
January 10, 2025, 5:23pm
2
I switched to stable, and it’s still freezing. I also had it freeze today with another computer.
I had the problem with a freezing system with fullscreen applications. E.g. when watching a youtube video in firefox in fullscreen.
For me it helped to use flatseal to change the firefox flathub package to only use X11 and disable Wayland. Also add this environment variable in flatseal for firefox :
jankdc
January 14, 2025, 4:53am
4
I’m not using Firefox or watching videos when it happens. Unfortunately, it froze three times today.
Im having the exact same issue on a wildly different system:
opened 04:44PM - 17 Jan 25 UTC
### Describe the bug
# Bluefin Bug Report: System instability with recurring GP… U errors and NVMe issues
## System Information
- **OS**: Bluefin 40 (FROM Fedora Silverblue)
- **Kernel**: Linux 6.11.8-200.fc40.x86_64
- **Hardware**: ASUS TUF GAMING X570-PLUS (WI-FI)
- **GPU**: AMD Radeon Vega Series (Picasso/Raven 2)
- **Driver**: xorg-x11-drv-amdgpu-23.0.0-3
- **Memory**: 32GB (29Gi available)
- **Current Version**: gts-40.20250115 (2025-01-15T01:08:05Z)
## Issue Description
System experiences frequent unrecoverable hangs (that lasts minutes until the OS crashes) after running for a while.
IA analysis of the logs suggest that the crashes appear to be related to GPU driver issues and NVMe storage problems.
## Critical Errors
### 1. GPU-related errors
```
amdgpu 0000:0a:00.0: amdgpu: Secure display: Generic Failure
amdgpu 0000:0a:00.0: amdgpu: SECUREDISPLAY: query securedisplay TA failed. ret 0x0
```
### 2. NVMe errors
```
nvme nvme0: failed to set APST feature (2)
nvme nvme1: failed to set APST feature (2)
```
### 3. System service errors
```
systemd[3217]: Failed to start app-gnome-gnome\x2dkeyring\x2dssh-3529.scope
systemd[3217]: Failed to start app-gnome-xdg\x2duser\x2ddirs-3556.scope
```
### 4. Display manager errors
```
gdm[1812]: Gdm: on_display_added: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
gdm[1812]: Gdm: on_display_removed: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
```
## System State
- Memory usage is normal (23GB free, no swap used)
- System load is normal (load average: 0.07, 0.19, 0.23)
- GPU temperature: 36.0°C (normal)
- NVMe temperatures: 33.9°C and 35.9°C (normal)
## Installed Packages
### Layered Packages
```
docker-compose
eza
java-17-openjdk-devel
nodejs
unetbootin
```
### Local Packages
```
appimagelauncher-2.2.0-travis995~0f91801.x86_64
balena-etcher-1.19.21-1.x86_64
```
## Steps to Reproduce
1. Normal system usage after fresh boot
2. System becomes unstable after some time
3. Eventually crashes or hangs
## Additional Notes
- Issues persist across reboots
- GPU errors appear consistently in system logs
- Both NVMe drives show APST errors during boot
- Multiple GNOME-related services fail to start properly
- System is running a recent deployment from January 15, 2025
## Attempted Solutions
- Cleared and Updated the system using ujust related commands
- Ran programmed and frecuente memory freeing commands
- Reporting issue to track the problem and get assistance with resolving the GPU and NVMe-related errors.
_Logs and additional system information available upon request._
### What did you expect to happen?
To not hang.
### Output of `bootc status`
```shell
No staged image present
Current booted state is native ostree
Current rollback state is native ostree
```
### Output of `groups`
```shell
falbertengo wheel docker incus-admin lxd libvirt
```
### Extra information or context
_No response_
1 Like
jankdc
January 17, 2025, 5:10pm
6
How did you find the error log? How did you find the critical errors?
inffy
January 17, 2025, 6:16pm
7
What you can try is to rebase to the -latest stream. Atleast that way you can check if its a kernel regression, which is pretty likely knowing all the issues AMD has been having with its kernel drivers.