Public bug reported:
graphics crashes, requires reboot
this has happened a few times recently - typically during periods of
activity but not always.
See the journal log from the last boot below:
Apr 30 21:07:15 arc kernel: snd_hda_intel :1f:00.1: Unable to change power
state from D3hot to
Public bug reported:
When trying to log in from locked / sleeping desktop, gnome crashed.
I have three monitors connected via displayport to this card.
dmesg snip:
[Thu Apr 11 08:12:57 2024] audit: type=1107 audit(1712844779.171:174815):
pid=1799 uid=103 auid=4294967295 ses=4294967295
After setting UMA_Game_Optimized, I can confirm that (after 30 minutes
of usage), the system appears far more stable. Since X11 appeared stable
I also switched back to Wayland which was previously unusable and this
also appears to be working.
I'll also report back once I am able to test the new
> If you can add your details for your "specific" FW13 AMD to the upstream bug
> maybe others who are affected can help with building the pattern.
> I mean the memory vendor, speed of memory, amount, channel configuration.
this system has a single DIMM which was provided by framework: DDR5-5600
>> Should this fix the flickering issue? I'm happy to test it out.
>
> It will fix a colored flickering;
My flickering has mostly actually usually been white - not colored (though
I was seeing the colored flickering lots before I switched off of Wayland,
which crashed too often with multiple
Thanks for the update @superm1, I appreciate the help.
> I suggest updating to 6.8.0-20 though, this 6.8.0-11 has an old 6.8-RC
snapshot and there are other bugs that got fixed later on in the
6.8-RC's.
Should this fix the flickering issue? I'm happy to test it out.
> FYI - there are two
Public bug reported:
an interesting amdgpu issue:
I currently have two external monitors, and only one will display the
desktop at a time - the other is completely white. The interesting thing
is that with each interrupt that the kernel receives from keyboard /
mouse, the screens will flip which
** Summary changed:
- Crash on lock screen
+ Crash on blank screen
** Description changed:
- When my computer locks due to inactivity the screen goes white and
- requires a reboot to recover.
+ When my computer screen goes blank and then locks due to inactivity, the
+ screen goes white and
Public bug reported:
When my computer locks due to inactivity the screen goes white and
requires a reboot to recover.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.6.0-14-generic 6.6.0-14.14
ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
Uname: Linux
see attached last boot
** Attachment added: "journalctl-last-boot.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054489/+attachment/5747880/+files/journalctl-last-boot.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Description changed:
- screen goes completely white, have to reboot the system to recover
+ Screen goes completely white, have to reboot the system to recover. I've
+ manually attached the kernel log from the previous boot which contains
+ the relevant errors.
ProblemType: Bug
Public bug reported:
screen goes completely white, have to reboot the system to recover
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.6.0-14-generic 6.6.0-14.14
ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
Uname: Linux 6.6.0-14-generic x86_64
ApportVersion:
Public bug reported:
Unplugging an exteranal usb-c monitor caused the GPU to crash - the
screen went white and unresponsive, reboot was required for the machine
to become usable.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.6.0-14-generic 6.6.0-14.14
ProcVersionSignature:
** Attachment added: "dmesg from the time of the crash"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2052467/+attachment/5744733/+files/journalctl-last-boot.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Description changed:
The issue is very reproducible. It happened within a minute or two of
using my machine after updating from Lunar to Mantic. I tried upgrading
to Noble to see if a newer kernel might have the fix - it didn't. My
machine is unusable and I'm happy to repro if anyone
Public bug reported:
The issue is very reproducible. It happened within a minute or two of
using my machine after updating from Lunar to Mantic. I tried upgrading
to Noble to see if a newer kernel might have the fix - it didn't. My
machine is unusable and I'm happy to repro if anyone has the fix
** Attachment added: "lspci-vnvn.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2051741/+attachment/5743702/+files/lspci-vnvn.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
The issue is very reproducible. It happened within a minute or two of
using my machine after updating from Lunar to Mantic. I tried upgrading
to Noble to see if a newer kernel might have the fix - it didn't. My
machine is unusable and I'm happy to repro if anyone has the fix
Since upgrading to 6.1.0-16-generic on lunar, I hit nearly the exact
same error again, minus the "fences timed out" log:
[728875.081136] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 timeout,
signaled seq=263052, emitted seq=263054
[728875.081681] [drm:amdgpu_job_timedout [amdgpu]]
Public bug reported:
System Info:
Kernel: 5.19.0-31-generic
Release: kinetic
CPU: AMD Ryzen 5 2600 Six-Core Processor
GPU: AMD Radeon RX Vega
Symptoms:
=
Graphics crash - all monitors go black. No reproducer, but this happens once or
twice a week.
This bears strong
Public bug reported:
Release:
Description:Ubuntu 22.10
Release:22.10
Package Version:
isa~ apt-cache policy bluez
bluez:
Installed: 5.65-0ubuntu1
Candidate: 5.65-0ubuntu1
Version table:
*** 5.65-0ubuntu1 500
500
** Description changed:
Hardware: Macbook Pro 9,2 with Broadcom BCM4331 chipset
Ubuntu Release: 22.10
Kernel: 5.19.0-23-generic
Symptoms:
Warning traces in the dmesg. Network timeout/freeze for >1 minute (possibly
related to suspend/resume).
This has been fixed in Arch and
Hi Łukasz,
The test passes locally for me.
My reproducer, which works consistently on this machine, did not reproduce this
issue using the new package. Suspending the machine was sufficient to force the
error condition, but now that does not happen.
Package/Kernel versions:
** Description changed:
Hardware: Macbook Pro 9,2 with Broadcom BCM4331 chipset
Ubuntu Release: 22.10
Kernel: 5.19.0-23-generic
Symptoms:
Warning traces in the dmesg. Network timeout/freeze for >1 minute (possibly
related to suspend/resume).
A search found a related issue[1].
The patch in Debian doesn't apply cleanly, so I refreshed the patch for
Ubuntu. Building and testing locally with the refreshed version appears
to work (my reproducer doesn't reproduce with this package).
Steps:
1) Add new patch line in dkms config: debian/dkms.conf.in
2) add patch to
** No longer affects: linux-meta (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1998039
Title:
Network Freeze With Broadcom DKMS Wireless Driver
Status in bcmwl package in
** Also affects: bcmwl (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1998039
Title:
Network Freeze With Broadcom DKMS Wireless
I can reproduce this bug locally by suspending my machine. This appears
to always reproduce on 5.19.0-23-generic.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1998039
Title:
** Description changed:
Hardware: Macbook Pro 9,2 with Broadcom BCM4331 chipset
Ubuntu Release: 22.10
Kernel: 5.19.0-23-generic
Symptoms:
- Warning traces in the dmesg. Network timeout/freeze for >1 minute (possibly
related to suspend/resume).
+ Warning traces in the dmesg. Network
** Summary changed:
- Network Freeze With In Tree Broadcom Driver
+ Network Freeze With Broadcom DKMS Wireless Driver
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1998039
Title:
** Attachment added: "version.log"
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1998039/+attachment/5632878/+files/version.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
** Attachment added: "lspci-vnvn.log"
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1998039/+attachment/5632877/+files/lspci-vnvn.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
** Attachment added: "dmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1998039/+attachment/5632879/+files/dmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
Public bug reported:
Hardware: Macbook Pro 9,2 with Broadcom BCM4331 chipset
Ubuntu Release: 22.10
Kernel: 5.19.0-23-generic
Symptoms:
Warning traces in the dmesg. Network timeout/freeze for >1 minute (possibly
related to suspend/resume).
A search found a related issue in the separate
Public bug reported:
Summary:
Missing dm-thin-pool.ko causes LXD failure.
1) Release
root@jammy-vm:~# lsb_release -rd
Description:Ubuntu Jammy Jellyfish (development branch)
Release:22.04
2) Package
root@jammy-vm:~# apt-cache policy linux-modules-5.15.0-1002-kvm
Public bug reported:
Perf crashes when attempting to add probes at certain locations. I
submitted a bug via apport, but I have additional details to share (and
I couldn't figure out how to find that report).
- I was unable to reproduce on the upstream kernel (torvalds/master).
- perf probe
36 matches
Mail list logo
