A fix may already be available at
https://gitlab.freedesktop.org/drm/amd/-/issues/2486
** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #2486
https://gitlab.freedesktop.org/drm/amd/-/issues/2486
--
You received this bug notification because you are a member of Kernel
Packages,
** Package changed: xorg (Ubuntu) => linux-signed-hwe-6.2 (Ubuntu)
** Summary changed:
- Xorg freeze amdgpu mst powersaving
+ amdgpu mst power saving null ptr deref
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-6.2 in
** Changed in: linux-signed-hwe-6.2 (Ubuntu)
Status: New => Incomplete
** Changed in: linux-signed-hwe-6.2 (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-6.2 in
Duplicate of #2038748 which apparently got some more logs than this one.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu.
https://bugs.launchpad.net/bugs/2038749
Title:
amdgpu mst power saving null ptr
Public bug reported:
Amdgpu tends to crash when attempting to unlock screen after power
saving has been triggered on MST screen(s).
Further details to be filled in post-reboot.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-6.2.0-33-generic 6.2.0-33.33~22.04.1
Public bug reported:
Amdgpu has tendency of crashing after resume when MST responses of the
displays waking up aren't what it expects.
Sadly launchpad does not provide a way to review the logs sent by
ubuntu-bug before submit button here, apparently can preview only
locally prior to sending
$ journalctl -g 'Linux version'
Apr 27 17:57:21 ub3jj kernel: Linux version 5.15.0-27-generic (buildd@ubuntu)
(gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0, GNU ld (GNU Binutils for Ubuntu) 2.38)
#28-Ubuntu SMP Thu Apr 14 04:55:28 UTC 2022 (Ubuntu 5.15.0-27.28-generic
5.15.30)
-- Boot
** Attachment added: "previous (successful) boot logs for comparison"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971095/+attachment/5585653/+files/journalctl_b_-1_g_mpt2sas
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Public bug reported:
mpt2sas card driver failed to start properly after normal poweroff + restart.
Logs attached.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-27-generic 5.15.0-27.28
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux
** Description changed:
Regression to be analyzed further later.
03:00.0 VGA compatible controller: Advanced Micro Devices, Inc.
[AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] (rev c5)
- Most relevant part of boot logs:
+ Most relevant part of boot logs (more in attachment):
Turning off secondary and tertiary monitors for the duration of the
initial boot appears to work around this issue. Suspend-to-ram works
with all monitors powered (same hardware configuration as in #1926400).
** Attachment added: "journalctl -b -1 -k | egrep -v 'audit|dbus-daemon'"
Public bug reported:
Regression to be analyzed further later.
03:00.0 VGA compatible controller: Advanced Micro Devices, Inc.
[AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] (rev c5)
Most relevant part of boot logs:
Nov 30 13:08:00 ub3ff kernel: microcode: microcode updated early to
*** This bug is a duplicate of bug 1486316 ***
https://bugs.launchpad.net/bugs/1486316
** This bug has been marked a duplicate of bug 1486316
lpc_ich: Resource conflict(s) found affecting gpio_ich
--
You received this bug notification because you are a member of Kernel
Packages, which is
** Tags added: bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1486316
Title:
lpc_ich: Resource conflict(s) found affecting gpio_ich
Status in linux package in Ubuntu:
Triaged
@#9, Supposedly rasdaemon could handle MCEs on bionic+. Have not yet
witnessed it working though, even on hardware that had dozen
reports/year shown with mcelog.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
For the record, first ever CE reported by mcelog below on the hardware I
have access to. No UCEs nor even repeating CEs seen. Have not tested
mce-inject and/or apei/einj.ko kernel module.
mcelog: failed to prefill DIMM database from DMI data
Hardware event. This is not a software error.
MCE 0
CPU
I currently don't have access to the hardware, as that system was
decommissioned/repurposed. May have access to it during xmas break. In
any case patrick's observations suggest that next step should be
https://wiki.ubuntu.com/Kernel/KernelBisection between 3.13.0.32-generic
and 3.13.0-34-generic
Public bug reported:
Boot hangs if acpi is not entirely disabled on Acer Aspire V3-111P.
Bios 1.05, newer (undocumented) version 1.11 untested so far.
This hang does not occur on Ubuntu 12.04 LTS, but does on 14.04(.1) LTS, unless
using acpi=off.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
** Attachment added: dmidecode.txt
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1360731/+attachment/4185639/+files/dmidecode.txt
** Description changed:
Boot hangs if acpi is not entirely disabled on Acer Aspire V3-111P.
- Bios 1.05, newer (undocumented) version 1.11 untested so
19 matches
Mail list logo
