** Also affects: linux-oem-5.17 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-oem-5.17 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.17 in Ubuntu.
https://
> Is this Linux patch series back-ported to older kernels, like the 5.13
kernel that came with my Ubuntu 20.04 installation, or any LTS kernel?
I'm not fully familiar with the Linux kernel release behaviour.
The patches were accepted upstream for kernel 5.18. Right now it's not been
added to any
If you attach an TBT3 NVME storage to USB4 port you can see the warnings
that come up without them. I think you can make a call whether that is
severe enough to warrant the change.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem
Jammy appears to have failed to build. Trying it on oem-5.14 on a
machine with the failing symptom it seems to fail on the machine I
tested unfortunately.
When loading the i2c-piix4 module I see the following:
[ 97.103748] ACPI Warning: SystemIO range
0x0B00-0x0B08 conf
** Description changed:
- The following WARNING shows up on resume from s2idle on HP Z13/Z16:
+ The following WARNING shows up on resume from s2idle on some OEM
+ platforms:
[ 136.701141] [ cut here ]
[ 136.701146] WARNING: CPU: 0 PID: 1630 at
drivers/gpu/drm/amd/
I checked on 5.17-rc3 most recently and reproduced it. AFAICT this code
hasn't changed since 5.16-rc4.
--
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/1958770
Title:
Aquantia GbE LAN dri
@KH:
Yeah that fixes it for me. I applied on top of a 5.15 kernel and would have
seen UBSAN error at bootup.
Feel free to added a "Tested-by: Mario Limonciello
" tag for it when you submit up if you don't
change it.
--
You received this bug notification because you are a m
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.10 in Ubuntu.
https://bugs.launchpad.net/bugs/1927067
Title:
Add s2idle support on AMD Renoir and Cezanne
@binli:
That confirms userspace fix works. You need BIOS that sets D3 policy
accordingly. Otherwise you can manually run PCIe rescan for now after you have
authorized devices.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5
> Could you propose some tests that could be ran to check for
regressions?
Sure. I'll modify the description to include some specific tests and
change the status back to "In Progress" when I do.
> but is it possible that someone could rely on the boltd binary
externally
The daemon isn't directl
> verification-needed-jammy
Juerg - which firmware landed for VCN?
> Binary files /tmp/tmpjfs7by6f/74GQKUQY8t/linux-
firmware-20220329.git681281e4/amdgpu/yellow_carp_vcn.bin and
/tmp/tmpjfs7by6f/0SroKiuHba/linux-
firmware-20220329.git681281e4/amdgpu/yellow_carp_vcn.bin differ
There was a revert
Public bug reported:
[Summary]
No video output on Thunderbolt monitor.
1. Connect monitor to DUT directly
2. Connect monitor to DUT via Docking
System can detect the monitor and able to change display mode but no
output on the monitor
[Steps to reproduce]
1. Boot to OS
2. Plug an external monito
Great thanks.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1981922
Title:
Upgrade yellow carp DMCUB firmware to fix suspend failure
Status in HWE Next:
New
Status in linux-
** Changed in: linux-oem-5.13 (Ubuntu Focal)
Status: Confirmed => Won't Fix
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: linux (Ubuntu Impish)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of
Public bug reported:
[Impact]
Jammy already has firmware for upcoming product with GFX1037 and DCN316.
However this firmware has some stability problems under stress and it should be
updated to latest on linux-firmware.git to support systems that will take this
firmware.
[Fix]
Upgrade followi
> intel_iommu=igfx_off should be enough to resolve issues with GPUs.
Maybe this design dGPU should have IOMMU off.
> @Mario, would you please have some comment in this? thanks
Maybe a new parameter is needed for Intel IOMMU driver to allow
filtering dGPU from IOMMU too?
But this type of error s
Looking at the code though, I notice that igfx=off actually filters all
GFX. Maybe it's just badly named:
#define IS_GFX_DEVICE(pdev) ((pdev->class >> 16) ==
PCI_BASE_CLASS_DISPLAY)
So yeah; have a try with "intel_iommu=igfx_off" on kernel command line.
--
You received this bug notification be
** Also affects: linux-oem-5.17 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-oem-5.17 (Ubuntu)
Status: New => Invalid
** Changed in: linux-oem-5.17 (Ubuntu Focal)
Status: New => Invalid
** Tags added: stella
** Tags added: originate-from-1980851
** Ta
> For linux-firmware, adding the following to debian/remove-
firmware.list creates a deb file without AMD-SEV files:
Presumably amd64-microcode will also need some handholding with
Conflicts/Replaces to make sure that it works on upgrade as it will
probably upgrade before linux-firmware does, righ
AFAICT it should be in Ubuntu-5.15.0-47.50.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1950062
Title:
Unable to access CPU i2c interfaces with AMD "Cezanne" CPU's
Status in
Yeah there are positive test results in bug 1978067.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1983143
Title:
AMD Rembrandt: DP tunneling fails with Thunderbolt monitors
S
Wasn't that commit reverted because it caused other regressions?
IE c4849f88164b13dd141885e28210f599741b304b
I would suggest to check that latest linux-firmware for this platform
still has the issue instead.
--
You received this bug notification because you are a member of Kernel
Packages, whic
Public bug reported:
Some upcoming platforms support for AMD-PMF.
This will enable ACPI platform profiles and some automatic transitions.
The first 11 patches are queued up for 6.1 and also available in an immutable
branch.
https://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-
drivers
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
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/1987670
Title:
Add support for AMD PMF
Status in linux package in Ubu
Did you ever end up testing your own patch for that other drive?
--
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/1970136
Title:
Optical drive no longer usable after upgrading to kernel v5
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
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/1936583
Title:
Fix resume failure on Tongfang GMxZGxx Barebone
Status
** Changed in: linux (Ubuntu Impish)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1934809
Title:
Backport support for AMD SMU statistics
** No longer affects: linux (Ubuntu)
** No longer affects: linux (Ubuntu Focal)
** No longer affects: linux (Ubuntu Impish)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1930719
So I have reason to believe this is fixed in kernel 5.2 and later by
this commit:
https://github.com/torvalds/linux/commit/8ae5b1d78d4acbe9755570f26703962877f9108a
Would someone affected be able to check the with a modern kernel if it
can still reproduce? On some Renoir hardware I found that as f
** Changed in: linux (Ubuntu)
Status: Triaged => Fix Released
--
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/1826691
Title:
fwupd hangs after 19.04 upgrade from 18.10
Status in L
** Changed in: amd
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.10 in Ubuntu.
https://bugs.launchpad.net/bugs/1928820
Title:
Add support for AMD wireless button
Status in amd:
KH: We tested this binary kernel and found it doesn't work on RN. Two commits
are still missing, can you resubmit and add them?
http://git.infradead.org/nvme.git/commit/2744d7a0733503931b71c00d156119ced002f22c
http://git.infradead.org/nvme.git/commit/6485fc18faa01e8845b1e5bb55118e633f84d1f2
** T
The tested kernel binary was: 5.10.0-1035
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.10 in Ubuntu.
https://bugs.launchpad.net/bugs/1932577
Title:
[Cezanne/Renoir] Adjust uPEP for different _HID behavior
Status in amd:
Looks like other SRU missed #9 still.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.10 in Ubuntu.
https://bugs.launchpad.net/bugs/1930719
Title:
Replace AMD nvme workaround from oem-5.10 with upstream version
Status in am
Public bug reported:
[Impact]
Renoir based systems can't resume from s2idle.
[Fix]
Update firmware for renoir into 21.10 or 21.20 release in linux-firmware.git
Accompanying kernel driver updates are distributed with linux-oem-5.10.
[Test]
Verify s2idle on OEM system.
[Where problems could occur
Closing impish task as impish has 21.10 firmware already.
** Tags added: originate-from-1929104
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1934014
Title:
[SRU] Update amdgp
Public bug reported:
[Impact]
Several AMD based OEM designs have spurious wakeups occurring from EC events
during s2idle. This leads to non-functional wakeup sources or higher power
consumption.
[Fix]
Prevent setting the GPE for the EC for wakeup source on AMD systems.
[Test]
Verify s2idle on
The patch is queued upstream for 5.14-rc1: https://lore.kernel.org
/linux-
acpi/CAJZ5v0jhYL6Qrj5vvU=5FguF=mvryfrbbtgvc8chzckkxm_...@mail.gmail.com/T/#mb0e0b54da3256cfb04cee38e45322a086d523652
** Changed in: linux-oem-5.10 (Ubuntu Focal)
Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng)
*
#134: @xnox, have you re-sent it? It looks like
https://lkml.org/lkml/2021/1/14/1091 got no feedback.
--
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/1835660
Title:
initramfs unpacking f
Public bug reported:
[Impact]
AMD RN and CZN SOC can collect extra debugging data for s0i3. This information
is useful for finding problems with IP blocks not going into correct states.
[Fix]
The following patch series adds support for these stats and will be included in
5.14.
https://patchwor
** Changed in: amd
Status: Confirmed => Fix Released
--
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/1822267
Title:
[Patch][Raven 2] kernel 5.0.0 cannot boot because of psp respons
** Changed in: amd
Status: Incomplete => Won't Fix
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Released
--
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/1117548
Ti
** Changed in: amd
Status: New => Fix Released
--
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/1272525
Title:
SMBus host controller driver issue on ML
Status in amd:
Fix Release
** Changed in: amd
Status: Triaged => Fix Released
--
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/1322409
Title:
Usb 3.0 device is recognized as usb 2.0 device on usb 3.0 port if
** Changed in: amd
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-saucy in Ubuntu.
https://bugs.launchpad.net/bugs/1243508
Title:
[Lenovo Thinkpad Edge E525] Unable to control brightness wit
** Changed in: amd
Status: New => Invalid
--
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/1096900
Title:
[Lenovo b575e] - VGA port doesn't work AT ALL with fglrx
Status in amd:
** Changed in: amd
Status: Incomplete => Won't Fix
** Changed in: linux (Ubuntu)
Status: Incomplete => Won't Fix
** Changed in: linux (Ubuntu Precise)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is
** No longer affects: amd
--
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/1912773
Title:
[MS-7C52, ATI R6xx HDMI, Digital Out, HDMI] No sound at all, second
display not working, cpu/agp
Here's a PPA build with the mesa fix Alex mentioned backported:
https://launchpad.net/~superm1/+archive/ubuntu/lp1928393
If you can follow the directions to add that PPA and upgrade to that
mesa package you can see if that indeed fixes it.
** Also affects: mesa (Ubuntu)
Importance: Undecided
> 3) RTC can't wake up the laptop.
This is expected behavior for CZN w/ s2idle.
--
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/1927067
Title:
Add s2idle support on AMD Renoir and Cezann
No, please don't expect RTC based wakeup from s2idle in current HW.
--
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/1927067
Title:
Add s2idle support on AMD Renoir and Cezanne
Status in
FYI, that patch is intended specifically for s2idle, which will not work
on those older kernels without significant other backports. Are you
sure that this patch alone really helps the issue?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed t
KH, That's surprising to me but OEM-5.13 is OK with it?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.10 in Ubuntu.
https://bugs.launchpad.net/bugs/1934809
Title:
Backport support for AMD SMU statistics
Status in linu
Sounds good, thanks.
** Changed in: linux-oem-5.10 (Ubuntu Focal)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.10 in Ubuntu.
https://bugs.launchpad.net/bugs/1934809
Title:
Backport support
*** This bug is a duplicate of bug 1922613 ***
https://bugs.launchpad.net/bugs/1922613
** This bug has been marked a duplicate of bug 1922613
fwupd + zed infinite loop
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu
Upstream kernel bug conclusion shows what appears to be a corrupted TBT
SPI.
** Changed in: linux (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
#106 - please open a separate issue to debug this. The architecture for
the WD19TB is very different than the TB16 and it shouldn't be conflated
into this issue. The most interesting things to include in your issue -
please first try this kernel: https://launchpad.net/ubuntu/+source
/linux-oem-5.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
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/1915188
Title:
Secondary monitor enters power save mode for no
I would suggest that you install linux-oem-5.10
(https://launchpad.net/ubuntu/+source/linux-oem-5.10) and see if this
persists. This is the kernel shipping with the "newer" models and has
an updated graphics driver.
--
You received this bug notification because you are a member of Kernel
Package
** No longer affects: ubuntu
--
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/1915188
Title:
Secondary monitor enters power save mode for no apparent reason
Status in Dell Sputnik:
New
> fwupd
It sounds like it might be part of the reason that this commit went in upstream:
https://github.com/fwupd/fwupd/commit/277347688427fd1bf68d68d8d8788bf67d42e01c
If you want to keep fwupd on your system, for now you can instead add
synaptics_rmi into the BlacklistPlugins= or DsiabledPlugins=
Fixed for 1_4_X:
https://github.com/fwupd/fwupd/commit/42e01911cd683a659367e453737d49a50ce6308f
Fixed for 1_3_X:
https://github.com/fwupd/fwupd/commit/67596cb1d8e5b8177de15ee29b53a058857c3056
** Changed in: fwupd (Ubuntu)
Status: New => Triaged
** No longer affects: linux-firmware (Ubunt
Public bug reported:
Currently the Ubuntu kernels ship with CONFIG_EISA_VLB_PRIMING=y. This
doesn't match the upstream default (n) and this is the help text:
Activate this option if your system contains a Vesa Local
Bus (VLB) card that identify itself as an EISA card (such as
It's ancient EISA card, does anything modern still use EISA?
--
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/2009759
Title:
Change default of CONFIG_EISA_VLB_PRIMING
Status in linux pack
Just for reference in a quick Google search on my profile for "Adaptec
AHA-284x" my top hit was an OS/2 driver..
--
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/2009759
Title:
Change defa
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
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/2009759
Title:
Change default of CONFIG_EISA_VLB_PRIMING
Status in li
Dev kernel and OEM 6.1 maybe?
--
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/2009759
Title:
Change default of CONFIG_EISA_VLB_PRIMING
Status in linux package in Ubuntu:
Confirmed
Bug
** Description changed:
[Impact]
To whom it may concern:
I was experiencing frequent wake-ups from s0i3x on a HP Pro 435 G9
convertible [1] using the Qualcomm FastConnect 6900 Soc [2]. The issue
is related to FW revision
WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.9
I tested this on a Z13 with following combo:
$ dpkg -l | grep linux-firmware
ii linux-firmware
20220329.git681281e4-0ubuntu3.11all Firmware for Linux kernel
drivers
$ uname -a
Linux Z13-Gen-1 6.1.0-1008-oem #8-Ubuntu SMP PREEMPT_DYNAMIC Fri Mar
I verified a system that uses this IP version could boot with this
package and OEM 6.1 1008 package.
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.n
Tested kinetic kernel 5.19.0-38.39 and focal kernel 5.15.0-69.76 and
both pass.
** Tags added: verification-done-focal verification-done-kinetic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launch
#17
This issue is specific to AMD Navi3x dGPU; please open separate issue for your
problem.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2038745
Title:
NV31 XTX cannot boot i
conflict since they will be different binaries.
Please reject the *ubuntu4 version from the mantic-proposed queue and
accept the *ubuntu3.1 version (if it looks good).
** Changed in: mutter (Ubuntu)
Assignee: (unassigned) => Mario Limonciello (superm1)
--
You received this bug notific
Can you please share your kernel log from jammy when the failure has
occurred?
We did test XTX working, suspect a separate issue.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/20
#75
You can turn on proposed and then use ppa-purge command to remove my
PPA.
--
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/2034619
Title:
[amdgpu] gnome-shell gets SIGKILL'd when lock
Here's the mainline commit with the fix for your issue:
https://github.com/torvalds/linux/commit/64ffd2f1d00c6235dabe9704bbb0d9ce3e28147f
--
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/203
Here is the upstream patch for this issue:
https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?h=x86/urgent&id=38d54ecfe293ed8bb26d05e6f0270a0aaa6656c6
** Also affects: linux via
https://bugzilla.kernel.org/show_bug.cgi?id=218003
Importance: Unknown
Status: Unknown
-
Please also take this fix at the same time for this same laptop. It
will fix s2idle for it.
https://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-
drivers-x86.git/commit/?h=fixes&id=3bde7ec13c971445faade32172cb0b4370b841d9
** Changed in: libinput (Ubuntu)
Status: Confirmed => Inv
** Changed in: linux-oem-6.5 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2034477
Title:
Keyboard and Touchpad Not Working in New Lenovo
Sorry for delay looking at this. I might have not been clear. That
script needs to be run after the error has occurred. I don't see the
error in this kernel log.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in Ubuntu.
h
Here's the fix in Linus' tree.
https://github.com/torvalds/linux/commit/128b0c9781c9f2651bea163cb85e52a6c7be0f9e
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2034477
Title:
Ke
#166
Canonicals' kernel team needs to apply it. When they do there would be
notification to this bug.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2034477
Title:
Keyboard and
It's in lvfs-testing.
https://fwupd.org/lvfs/devices/work.frame.Laptop.Ryzen7040.BIOS.firmware
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://b
These fixes all landed in 6.5-rc2, mantic and noble have them for sure, closing
those tasks.
I'd expect backporting to be done for Lunar and Jammy if necessary.
** Changed in: linux-oem-6.1 (Ubuntu Jammy)
Status: In Progress => Fix Released
** Changed in: linux (Ubuntu Mantic)
Stat
It's unclear if this is a BIOS, mesa or kernel bug at this time, but
it's certainly not an Xorg bug as it was reproduced in Wayland.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #2954
https://gitlab.free
> amd_gpio AMDI0030 0: Invalid config param 0014
This is fixed by this patch:
https://github.com/torvalds/linux/commit/87b549efcb0f7934b0916d2a00607a878b6f1e0f
Canonical needs to backport that to applicable kernels.
> 10/31/23 12:11 PM WARNING CPU: 2 PID: 3763 at
drivers/gpu/drm/amd/amdgpu
Can you please share the kernel log from a failed kernel? To get it:
1) Boot the failed kernel and reproduce failure
2) Boot a good kernel
3) run "journalctl -k -b-1 > journal_bad.txt"
4) run "journalctl -k > journal_good.txt"
Then attach both of those to this bug.
** Changed in: linux (Ubuntu)
From the upstream bug this is caused by PSR, so it's not a mesa issue.
** No longer affects: mesa (Ubuntu)
** No longer affects: mesa (Ubuntu Jammy)
** No longer affects: mesa (Ubuntu Lunar)
** No longer affects: mesa (Ubuntu Mantic)
** No longer affects: mesa (Ubuntu Noble)
--
You received
** Changed in: linux (Ubuntu Noble)
Status: New => Triaged
** Changed in: linux (Ubuntu Mantic)
Status: New => Triaged
** Changed in: linux (Ubuntu Lunar)
Status: New => Triaged
** Changed in: linux (Ubuntu Jammy)
Status: New => Triaged
** Changed in: linux-oem-6.5 (
Your "good" journal is with nomodeset. Can I see the log from a good
journal without adding a module parameter? Like an older kernel that
worked?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
Please add kernel log from both your old kernel and new kernel.
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
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/2042713
Title
This issue is fixed in 6.6-rc3: 2de19022c5d7 ("drm/amd/display: fix the
ability to use lower resolution modes on eDP")
It's backported to stable 6.5.6 as 79aec38ba852 ("drm/amd/display: fix
the ability to use lower resolution modes on eDP").
Canonical needs to pull the fix into their kernel.
**
OK thanks. Nothing was obvious in the log differences. We need to
narrow down intermediate kernel releases to identify what's changed to
cause this regression.
Can you please test these binaries from those. Capture the journals for
each and note if they worked or didn't. Hopefully we'll get clo
Each page you'll need the following binaries:
Linux image unsigned
Linux modules
Linux modules extra
Download those 3 and install them with dpkg.
Note: none of these are signed for secure boot. If you have that
enabled, disable it for this experiment.
--
You received this bug notification becau
Should be fixed with
https://github.com/torvalds/linux/commit/59cf445754566984fd55af19ba7146c76e6627bc
then I would expect.
--
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/2043197
Title:
Btw - That commit is in 5.15.132.
--
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/2043197
Title:
USB bus error after upgrading to proposed kernel on lunar and jammy
Status in linux packa
Open a new bug at kernel bugzilla and attach kernel log, acpidump and
dmidecode.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2034477
Title:
Keyboard and Touchpad Not Working i
*** This bug is a duplicate of bug 2042867 ***
https://bugs.launchpad.net/bugs/2042867
** This bug has been marked a duplicate of bug 2042867
Changing display resolution leads into black screen
--
You received this bug notification because you are a member of Kernel
Packages, which is sub
*** This bug is a duplicate of bug 2043197 ***
https://bugs.launchpad.net/bugs/2043197
** This bug has been marked a duplicate of bug 2043197
USB bus error after upgrading to proposed kernel on lunar and jammy
--
You received this bug notification because you are a member of Kernel
Packag
This should be a different issue than the mutter issue; please open it
up separately for investigation.
--
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/2034619
Title:
[amdgpu] gnome-shell
401 - 500 of 624 matches
Mail list logo
