> this system has a single DIMM which was provided by framework:
DDR5-5600 - 32GB (1 x 32GB)
My system is 8GB, single stick, same speed 5600 MT/s, same company
(A-DATA).
> Restarting firefox temporarily resolves the issue. This behavior
started to happen after I switched to X11.
You're the first
> I'll also report back once I am able to test the new kernel.
I had a try and I was able to install it today on Noble by pulling the
deb packages for linux-image-unsigned-6.8.0-20-generic, linux-
modules-6.8.0-20-generic, linux-modules-extra-6.8.0-20-generic from
Launchpad manually.
--
You rece
This is because amd-pstate is in active mode but nothing is tuning EPP
most likely.
Try to upgrade to this version of power profiles daemon:
https://launchpad.net/~superm1/+archive/ubuntu/ppd
Then you can change the power setting using the Gnome or kde GUI for it
or by using powerprofilesctl.
-
Probably nvidia.ko is missing a call to
drm_aperture_remove_conflicting_pci_framebuffers()
--
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/2060268
Title:
Phantom 46" monitor (simpledrm) s
I have a suspicion the root cause of the white screen could be fixed in
BIOS 3.05.
https://community.frame.work/t/framework-
laptop-13-ryzen-7040-bios-3-05-release-and-driver-bundle-beta/48276
Can you still reproduce it with no workarounds, 6.8.0-20 and the BIOS
upgrade?
--
You received this bu
*** This bug is a duplicate of bug 2056445 ***
https://bugs.launchpad.net/bugs/2056445
** This bug has been marked a duplicate of bug 2056445
external monitors flash white with every interrupt
--
You received this bug notification because you are a member of Kernel
Packages, which is subs
It was confirmed by many people this is fixed in the upgraded Framework
BIOS 3.05.
** Changed in: linux (Ubuntu)
Status: Triaged => 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
https://patchwork.freedesktop.org/patch/588305/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2039926
Title:
Error UBSAN: array-index-out-of-bounds amdgpu
(drivers/gpu/drm/amd
Variable sized arrays have fallen out of fashion.
There are various patches like that which fix this issue every time it
crops up.
If you can still reproduce on the latest 6.9-rc kernels you should
report a bug upstream to get the remaining cases fixed. Or if you feel
comfortable you can write a
This is the upstream solution:
https://github.com/torvalds/linux/commit/861b3415e4dee06cc00cd1754808a7827b9105bf
Here is the commit from 6.8.3:
b44a34f581b0 ("ASoC: amd: yc: Revert "Fix non-functional mic on Lenovo
21J2"")
--
You received this bug notification because you are a member of Kerne
The problem is that the "Pink Sardine" (Phoenix) laptops were being
applied to the "Yellow Carp" (Rembrandt) driver. This is improper
behavior and will cause other problems even if it fixed the immediate
microphone issue.
The Phoenix Lenovo laptops are supposed to have something in the ACPI
table
There is a second commit with a similar problem and really the one I
should have linked; this one is much more severe.
Here is that fix:
https://github.com/torvalds/linux/commit/37bee1855d0e3b6dbeb8de71895f6f68cad137be
It also came into 6.8.3.
3e52444ed190 ("ASoC: amd: yc: Revert "add new YC pl
Public bug reported:
Products with DCN 3.5 need linux-firmware to be added for noble.
Matching kernel support is already in kernel 6.8.
6bfdacdd amdgpu: add DMCUB 3.5 firmware
cb59bf73 amdgpu: add VPE 6.1.0 firmware
3ca35ef5 amdgpu: add VCN 4.0.5 firmware
9a3a6c61 amdgpu: add UMSCH 4.0.0 firmware
** Description changed:
- Products with DCN 3.5 need linux-firmware to be added for noble.
- Matching kernel support is already in kernel 6.8.
+ [Impact]
+ Products with DCN 3.5 need linux-firmware to be added for noble. Matching
kernel support is already in kernel 6.8.
+ Without this firmwar
For the plymouth part I think the suggestion above "plymouth.use-
simpledrm" makes sense.
--
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/2063143
Title:
Frequent boot to black display
St
Do you perhaps have the older version in /lib/firmware/updates?
--
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/2049220
Title:
Update firmware for MT7921 in order to fix Framewor
Did you put any other files in /lib/firmware? Maybe the output of
$tree /lib/firmware
Would explain what is going on.
--
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/2049220
Titl
I examined the packages and I notice the MT7921 firmware (Which
confusingly goes by MT7961) is updated but "not" the MT7922 firmware.
Based on the above comments and below finding it seems that the MT7921
hardware is fixed with the update but not the MT7922 (which also
confusingly uses the mt7921e
The two missing commits are specified in comment #4.
https://gitlab.com/kernel-firmware/linux-firmware/-/commit/1180974eb33ac67903269b71f35a489a2b77e5e9
https://gitlab.com/kernel-firmware/linux-firmware/-/commit/6b91b2ef6f4173099c1434e5d7c552e51814e26e
** Tags added: verification-failed-jammy
--
Internal team at AMD has tested across a number of different OEM PHX
systems using OEM 6.5-1014 kernel. This is testing well.
** 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
Internal team at AMD has tested an OEM RMB that doesn't need the DP swap
change to check for any potential regression. They tested using OEM
6.5-1014 kernel. This testing well.
Anson will confirm results on the system needing DP swap after he's back
from holiday.
--
You received this bug notif
** Changed in: linux-oem-6.5 (Ubuntu Jammy)
Status: Triaged => 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/bugs/2036737
Title:
Enable dynamic boost control in ccp kernel d
I tested with a Framework 16 with a 14c3:0616 WLAN. With
20220329.git681281e4-0ubuntu3.28 it's completely unusable with my AP
unless I turn off power save with iwconfig (Unifi).
With to 20220329.git681281e4-0ubuntu3.29 it works as expected.
** Tags removed: verification-failed-jammy
** Tags adde
#33, was your issue a one boot problem? Or it happens every time? Is
it tied to specifically that kernel + firmware, or is it also with older
kernel?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.
** Tags added: verification-done-jammy
--
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/2049758
Title:
DP connection swap to break eDP behavior on AMD 7735U
Status in linux packag
Plymouth only gets added to the initrd when LUKS is enabled or you mark
another reason for needing the framebuffer.
So the suggestion I have from comment #49 is to mark needing the
framebuffer by default, and then stop including any DRM modules because
simpledrm is built into the kernel.
--
You
AFAICT; these initramfs-tools package changes would cover it:
* hooks/framebuffer can be totally removed.
* scripts/init-top/framebuffer should probably stay
* conf/initramfs.conf needs FRAMEBUFFER=y added to it
--
You received this bug notification because you are a member of Kernel
Packages,
Even if FRAMEBUFFER=Y wasn't added, I think that a change to stop adding
all those other drm drivers makes a lot of sense. No use doubling the
initrd size for the LUKS case.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
*** This bug is a duplicate of bug 2039926 ***
https://bugs.launchpad.net/bugs/2039926
** This bug has been marked a duplicate of bug 2039926
Error UBSAN: array-index-out-of-bounds amdgpu
(drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/smu7_hwmgr.c)
--
You received this bug notificatio
V2 addressed comments and was reviewed.
--
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/2057424
Title:
No variable refresh rate (VRR) on the Framework 16
Status in HWE Next:
New
Status
The backend is a framebuffer driver. For example efifb which uses the
framebuffer set up by GOP in pre-boot.
If there are framebuffer drivers in tinydrm then maybe they matter for
those architectures.
--
You received this bug notification because you are a member of Kernel
Packages, which is sub
Can you double check the framebuffer FB related conf options in your
kconfig against those in Fedora?
--
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/1970069
Title:
Annoying boot messages
try amdgpu.aspm=0. If this helps it's because of missing stable
backport patches.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.15 in Ubuntu.
https://bugs.launchpad.net/bugs/2045382
Title:
AMD Lexa PRO graphic card
It's probably a duplicate of the same patches missing for bug 2036742.
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-signed-hwe-5.15 in Ubuntu.
http
That was already CC to stable, so I suggest checking the latest 5.15.y.
If that's still not working, you probably need
https://github.com/torvalds/linux/commit/2757a848cb0f184850d3e0a33b4a69e8014fdc5d
backported too.
--
You received this bug notification because you are a member of Kernel
Package
This will be fixed by this patch:
https://lore.kernel.org/amd-
gfx/20231201005751.4194154-1-jiadong@amd.com/
Until Canonical pulls it in for now you can use amdgpu.mcbp=0 on kernel
command line to avoid it.
--
You received this bug notification because you are a member of Kernel
Packages, w
that patch I linked will go into the next 6.7-fixes PR. I suggest
backporting it.
--
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/2045573
Title:
AMDGPU: cp queue preemption timeout
Stat
Here's the fix commit ID to backport to fix this issue.
https://github.com/torvalds/linux/commit/d6a57588666301acd9d42d3b00d74240964f07f6
--
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/2045
This is the same issue as
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045573
Here is a commit that fixes the issue by changing default pre-emption
policy since the kernel can't know about your mesa version.
https://github.com/torvalds/linux/commit/d6a57588666301acd9d42d3b00d74240964f07f
Is this happening possibly when there is a resolution change for the
eDP? If so, can you please try the latest linux-6.5.y kernel:
https://kernel.ubuntu.com/mainline/v6.5.13/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu
OK thanks for clarifying. Can you please still try latest 6.5.13 and
6.6.6 and see if it happens in either of those?
--
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/2039570
Title:
[amdgp
*** This bug is a duplicate of bug 2047389 ***
https://bugs.launchpad.net/bugs/2047389
** This bug has been marked a duplicate of bug 2047389
Fix AMDGPU crash on 6.5 kernel
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in U
The patches for this issue are in the original bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042867
--
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/2046504
Title:
Fix
** Changed in: linux-firmware (Ubuntu)
Status: New => Invalid
--
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/2059215
Title:
HDMI Display Not detected: AMD Ryzen 5 7530U/L
** Changed in: linux-oem-6.8 (Ubuntu Noble)
Status: Confirmed => Fix Committed
--
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/2064595
Title:
AMD Rembrandt & AMD Rembrandt-R: Suspe
Here's the submission to stable:
https://lore.kernel.org/stable/2020232554.2190-1-mario.limoncie...@amd.com/
--
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/1945565
Title:
[S
@xalt7x: Suggest that you adopt linux-oem-20.04d package which backports
all the patches for s2idle from 5.15 or later.
@Binli,
5.14 and 5.15 stable queue has the patch I mentioned above:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/tree/queue-5.14/drm-amd-display-look-
Bin,
Yeah it's going to either need separate SRU push or it will catch a
future stable kernel release.
I added tasks for kernel.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-oem-5.14 (Ubuntu)
Importance: Undecided
Status: New
** A
** Changed in: linux-oem-5.14 (Ubuntu)
Status: Confirmed => Invalid
--
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/1945656
Title:
Focal update: v5.14.9 upstream stable re
** Changed in: linux-oem-5.14 (Ubuntu)
Status: Confirmed => Invalid
--
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/1945187
Title:
Focal update: v5.14.8 upstream stable re
** Changed in: linux-oem-5.14 (Ubuntu)
Status: Confirmed => Invalid
--
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/1945185
Title:
Focal update: v5.14.7 upstream stable re
** Changed in: linux-oem-5.14 (Ubuntu)
Status: New => Invalid
** Changed in: linux-oem-5.13 (Ubuntu)
Status: New => Invalid
--
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
** Changed in: linux-oem-5.14 (Ubuntu)
Status: Confirmed => Invalid
--
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/1945183
Title:
Focal update: v5.14.6 upstream stable re
** No longer affects: linux-oem-5.14 (Ubuntu Hirsute)
--
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/1949050
Title:
Fix Screen freeze after resume from suspend with iGPU [1002:6
** Changed in: linux-oem-5.13 (Ubuntu)
Status: New => Invalid
** Changed in: linux-oem-5.14 (Ubuntu)
Status: New => Invalid
--
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
** 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-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1945565
Title:
[SRU] Revert amdgpu/renoir firmware
Status in
** No longer affects: linux-oem-5.14 (Ubuntu Impish)
** No longer affects: linux-oem-5.13 (Ubuntu Hirsute)
** No longer affects: linux-oem-5.13 (Ubuntu Impish)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
htt
** Changed in: linux-oem-5.10 (Ubuntu)
Status: Confirmed => Invalid
--
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/1932424
Title:
Focal update: v5.10.44 upstream stable r
** Changed in: linux-oem-5.10 (Ubuntu)
Status: Confirmed => Invalid
--
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/1932423
Title:
Focal update: v5.10.43 upstream stable r
** Changed in: linux-oem-5.10 (Ubuntu)
Status: Confirmed => Invalid
--
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/1932393
Title:
Focal update: v5.10.42 upstream stable r
For 5.14 and 5.15 it will come in as part of stable update process.
It is picked up in 5.15.3 for 5.15.y:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-5.15.y&id=bb7e50b476abb8fc94a9891bb7f08ab21801fec5
It's picked up in 5.14.19 for 5.14.y:
https://git.kernel.or
** 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.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1944382
Title:
Enable runtime power management for yellow carp XHC
** 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/1932577
Title:
[Cezanne/Renoir] Adjust uPEP for different _HID beh
** Changed in: linux-oem-5.10 (Ubuntu Focal)
Status: Confirmed => Won't Fix
** 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.laun
What is the plan for 5.13 though? Will it stay for a while, or will
there be a migration to 5.14? The new firmware needs to be in place no
matter the kernel version or project. So for safety the suggestion
would be to take that patch to all kernels so that you can put the new
firmware back in pl
confirmed that all 4 commits are present in 5.17 mainline, no tasks for
oem-5.17.
** Also affects: linux-oem-5.17 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-oem-5.17 (Ubuntu Impish)
Status: New => Invalid
** Changed in: linux-oem-5.17 (Ubuntu Focal)
S
Just to correct a few of the targets on this issue.
* The reverts mentioned in #30 need to be pulled into linux-firmware for focal.
* They're already included in jammy.
** Changed in: amd
Status: New => Fix Released
** No longer affects: mesa (Ubuntu)
** Also affects: linux-firmware
All of these commits are in v5.15.25 from stable backports, so no jammy
tasks for generic kernel either.
** Changed in: linux (Ubuntu Impish)
Status: Incomplete => Won't Fix
** Changed in: linux (Ubuntu Jammy)
Status: Incomplete => Fix Released
** Changed in: linux (Ubuntu)
Confirmed it's already in place for oem-5.14 as well.
** Changed in: linux-oem-5.14 (Ubuntu Focal)
Status: New => Fix Released
--
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/bug
** Changed in: amd
Status: New => Triaged
** Changed in: amd
Importance: Undecided => Low
--
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 acce
See bug 1968143 for more reasoning for this.
--
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/1969091
Title:
Fixes for dma-iommu swiotlb bounce buffers
Status in HWE Next:
New
** Summary changed:
- Fix REG_WAIT timeout for Yellow Carb
+ Fix REG_WAIT timeout for Yellow Carp
--
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/1971417
Title:
Fix REG_WAIT tim
** Description changed:
[Impact]
During hotplug built-in hdmi, the error message show up.
- #REG_WAIT timeout for yellow Carb
+ #REG_WAIT timeout for yellow Carp
[Fix]
This tends to take miliseconds in certain scenarios and we'd rather not
wait that long. Due to how this interacts wit
This caused a regression in s2idle on APUs. I think you forgot to pick
up e53d9665ab003df0ece8f869fcd3c2bbbecf7190 which was in the original
series too.
** Tags removed: verification-done-focal
** Tags added: verification-failed-focal
--
You received this bug notification because you are a memb
My team reproed it on Rembrandt but based on the failure (not getting
deepest state due to gfx) it should repro on Cezanne too.
--
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/19684
** 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/1972134
Title:
AMD APU s2idle is broken after the ASIC reset fix
Stat
The support is landed in 5.15.y kernels like those in Jammy.
** 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 in Ubuntu.
https://bugs.launchpad.net/bugs/1886937
> [0.699857] piix4_smbus :00:14.0: SMBus Host Controller at 0xff00,
> revision 15
> [0.699861] piix4_smbus :00:14.0: Using register 0x02 for SMBus port
> selection
> [0.700103] piix4_smbus :00:14.0: Auxiliary SMBus Host Controller at
> 0xff20
This bug will be fixed by th
Public bug reported:
First boot of Ubuntu server on a brand new Lenovo P620 workstation.
Found in dmesg that there are address sanitizer errors coming up.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-18-generic 5.15.0-18.18
ProcVersionSignature: Ubuntu 5.15.0-18.18-ge
*** This bug is a duplicate of bug 1958770 ***
https://bugs.launchpad.net/bugs/1958770
** This bug has been marked a duplicate of bug 1958770
Aquantia GbE LAN driver causes UBSAN error during kernel boot
--
You received this bug notification because you are a member of Kernel
Packages, wh
Out of bounds still happens to me in 5.15.0-18.18.
--
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 driver causes UBSAN error during kernel boot
Status in
The patch series was just accepted into the maintainer's i2c-next tree.
It should be in for 5.18.
--
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/1950062
Title:
Unable to access CPU i2c i
> but I believe you are using an AMD EPYC server, so I don't understand
why you would be affected at all.
It may be that this server silicon has the same HW IP as the client
chip. The change was tested on client chips before submitting. What it
is supposed to do is set the policy for the drives
No need to build a kernel, at least for a quick test you can pick up one from
the mainline PPA and try it.
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.18-rc7/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://
https://www.kernel.org/doc/html/latest/process/submitting-patches.html
You can use tags like "Suggested-by:" for the email of KH and bsdz.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.17 in Ubuntu.
https://bugs.launchpad.net
I've requested it to stable for 5.15.y and 5.17.y. If accepted I
believe this should solve all the tasks on this bug report eventually on
a future stable update in Ubuntu too.
https://lore.kernel.org/stable/mn0pr12mb610150ac5f1e15d6a67ac352e2...@mn0pr12mb6101.namprd12.prod.outlook.com/T/#u
** Ch
On any failing kernel, can you try to add "ahci.mobile_lpm_policy=0" to
the kernel command line and confirm if that fixes things?
If it does, could you also compare "ahci.mobile_lpm_policy=1" and
"ahci.mobile_lpm_policy=2"?
--
You received this bug notification because you are a member of Kernel
** Changed in: linux-oem-5.17 (Ubuntu)
Status: Confirmed => Invalid
--
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
0-> ATA_LPM_UNKNOWN,
1-> ATA_LPM_MAX_POWER,
2-> ATA_LPM_MED_POWER,
3-> ATA_LPM_MED_POWER_WITH_DIPM, /* Med power + DIPM as win IRST does */
4-> ATA_LPM_MIN_POWER_WITH_PARTIAL, /* Min Power + partial and slumber */
5-> ATA_LPM_MIN_POWER, /* Min power + no partial (slumber onl
@KH:
Thanks for sharing that! I agree with you. I've sent this up to explicitly
document the new behavior.
https://lore.kernel.org/linux-ide/20220524170508.563-4-mario.limoncie...@amd.com/T/#u
--
You received this bug notification because you are a member of Kernel
Packages, which is subscrib
*** This bug is a duplicate of bug 1971597 ***
https://bugs.launchpad.net/bugs/1971597
This should be fixed in 5.17.0-1005.5 and newer. It's actually a
duplicate of bug
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971597
** This bug has been marked a duplicate of bug 1971597
amd_
** Changed in: linux-oem-5.17 (Ubuntu)
Status: Fix Committed => Invalid
--
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/1962349
Title:
Bolt doesn't work with native USB4 h
** Changed in: linux-oem-5.17 (Ubuntu)
Status: Fix Committed => Invalid
--
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/1956509
Title:
Support AMD P-State cpufreq control
** Package changed: linux (Ubuntu) => linux-firmware (Ubuntu)
--
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/1957026
Title:
AMD Yellow Carp DMCUB fw update for s0i3 B0 fixes
St
This caused a regression on APUs that do S3; please pick up
https://gitlab.freedesktop.org/agd5f/linux/-/commit/8cf1a5e7e7ab6532beaa14b03bb5bf838be906e0
as well to avoid it
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in
Only reason was to avoid having to backport to both impish and focal
when the version in impish is enough.
--
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/1962349
Title:
Bolt doe
Public bug reported:
[Impact]
* Some OEM designs include an AMD Yellow Carp SoC and also include a
DMIC that is driven by an updated ACP driver (ACP6x). If these aren't
supported then the microphone won't be usable in the GUI.
[Test Plan]
* Verify can select and mute mic in GUI on OEM platf
** Changed in: alsa-ucm-conf (Ubuntu Jammy)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to alsa-ucm-conf in Ubuntu.
https://bugs.launchpad.net/bugs/1966957
Title:
ACP 6.x DMIC Support
Status in alsa
Jammy has an upload in the unapproved queue. I moved it to Fix Committed, but
if release manager decides this should push to SRU, please adjust the status
accordingly and loop in SRU team.
OEM team will drive Focal solution.
--
You received this bug notification because you are a member of Ker
FYI - this was CC'ed into stable, and went to 5.15.y stable. Here is
the reference for it:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/acpi/power.c?h=linux-5.15.y&id=bc28368596436e6e81ffc48c815b8225d96121c0
--
You received this bug notification because you ar
301 - 400 of 624 matches
Mail list logo
