responding to @intrigeri (sorry this got lost some how).
tldr: yes we are basically on the same page.
AppArmor does not fit into the 1400 range formats, every one of our
messages have some custom fields. Some of them could be
reformated/reworked to share more, but we would still need custom
field
[Expired for linux-signed-hwe-6.2 (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: linux-signed-hwe-6.2 (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe
Robie, good idea, I've added a note about pptpd and bcrelay being
removed, with a link back here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2041751
Thanks
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https:
I'm getting the same results as Max Power. My `dpkg --list` output shows
that I have version 20220329.git681281e4-0ubuntu3.28 of linux-firmware
installed. After rebooting, the dmesg logs from mt7921e show the same
build times as before---not the expected new build times. My wireless
card seems to b
As far as I know, no one has made an effort to try to improve the
situation lately. There's some discussion at
https://lists.ubuntu.com/archives/apparmor/2024-February/013091.html
that may be enlightening, if not encouraging.
Thanks
--
You received this bug notification because you are a member
This bug is awaiting verification that the linux-gcp/5.15.0-1052.60
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy-linux-gcp' to 'verification-done-jammy-
linux-gcp'. If the pro
If those patches are all in 6.7 mainline, then yes, they are already
included for 24.04. There is a 6.7 kernel in noble-proposed for 24.04
that could technically be installed now.
And thanks for the new bug. We added that to the stuff to work on this
next cycle (The next two weeks)
--
You rece
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
It happen again in second boot for `20230919.git3672ccab-0ubuntu2.1`
*ERROR* hw_init of IP block failed -62
--
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/2052840
Title:
Cannot
I just tried `20230919.git3672ccab-0ubuntu2.1` which resolve the issue?
(idk yet but the system boot from first try)
--
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/2052840
Title:
I just downgraded to 20230323.gitbcdcfbcf-0ubuntu1.2 and received different
error message
that resolve SMU issue but still cannot boot because system freeze after
```
[5.165679] kernel: [drm] try to fall back to amdgpu/gc_11_0_0_mes.bin
```
** Attachment added: "dmesg.1.gz"
https://bugs.
** Also affects: linux (Ubuntu Mantic)
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/2052662
Title:
move_mount mediation does not detect if s
Public bug reported:
There is a regression in partition table management in the latest jammy
kernel which can be reproduced with this simple script:
fallocate -l 32M /tmp/blob
LOOPDEV=$(losetup -f)
sudo losetup $LOOPDEV /tmp/blob
sudo /usr/sbin/parted -s -m $LOOPDEV -- "mklabel gpt"
Expected res
Screenshot of the error in the logs
** Attachment added: "screenshot"
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2052840/+attachment/5745480/+files/screenshot
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-fi
Public bug reported:
Hello, I'm facing this issue before few months after software upgrade,
Distro: Kubuntu 23.10
Kernel: Linux kernel 6.5.0-17-generic
Linux Firmware: 20230919.git3672ccab-0ubuntu2.5
My Specs:
CPU: Ryzen 9 7950X
RAM: 64GB = 16GB × 4 5200/MT DDR5
GPU: Radeon RX 7900 XTX (Founder
okay installed kernel 6.8.0-7 from noble-proposed and bluetooth issue is gone
with this version.. no drops
so this appears fixed
** Changed in: linux (Ubuntu)
Status: New => Incomplete
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notif
That might be the case, from my previous attempts to manually update it.
Could you tell me how to remove them, without breaking anything? I'd
really appreciate it.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
h
I'm glad to hear you are seeing an improvement! The current
implementation is still racy as mentioned in Comment #22. I did a search
of the logs I downloaded, and I believe this one shows that the
mount_partition() race isn't just theoretical:
https://autopkgtest.ubuntu.com/results/autopkgtest-
ma
Public bug reported:
Hi
When I try and run a shell script which is on a cifs mounted system I
get an error. This is on a 22.04 system - Linux bicr-compression
6.5.0-17-generic #17~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue Jan 16
14:32:32 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
nkhan@bicr-compression:
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
I enabled jammy-proposed and installed the firmware update, but
unfortunately the update still didn’t load as indicated by the build
times.
I tried re-installing, but got this output linux-firmware is already the
newest version (20220329.git681281e4-0ubuntu3.28). Selected version
'20220329.git6812
Rudi Daemen, thanks for the procedure! I just tried it, and the new
firmware still isn't running. That's not surprising, because your
procedure seems functionally identical to the one I described on Ask
Ubuntu, except that it updates all installed kernels instead of just the
latest one (which is th
Hi Jeff,
We have created one more BZ for similar patches for our other storage
controller (mpt3sas). Which are very important. So Could you please look into
it.
Below is the BZ link:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2046875
--
You received this bug notification because you
Thank you, Jeff. These patches are very important so if you need any
support from our end please let us know. Btw, when will this point
kernel be released?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launc
Hi Jeff,
These patches are available in the 6.7 mainline kernel. does it mean the
patches are already included?
--
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/2046726
Title:
[24.04 LTS]
I have manually downloaded and installed the updated package and can
confirm the new package contains the correct firmware and the issue is
resolved now. IPv6 Multicast is working and IPv6 address
autoconfiguration is working as expected.
Some output:
fludizz@pauwel:~$ dpkg --list | grep linux-fi
Public bug reported:
This is a public version of https://bugs.launchpad.net/bugs/2034981
Backport upstream commit:
873f64b791a2 mm/memcontrol.c: remove the redundant updating of
stats_flush_threshold
to jammy.
[Impact]
Remove the redundant updating of stats_flush_threshold. If the
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Jammy)
Assignee: (unassigned) => Philip Cox (philcox)
** Changed in: linux (Ubuntu Jammy)
Status: New => In Progress
--
You received this bug notification because you are a
Hello You-Sheng, or anyone else affected,
Accepted linux-firmware into jammy-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/20220329.git681281e4-0ubuntu3.28 in a few hours, and then in
the -proposed repository.
Please help us by testi
We will work on these this next week and shoot for the next SRU for 6.5.
--
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/2046722
Title:
[22.04.04]: megaraid_sas: Critical Bug Fixes
Statu
Additionally, this says 24.04... is that the correct target? Your email
to me says otherwise.
--
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/2046726
Title:
[24.04 LTS]: megaraid_sas driv
24.04 only recently rolled the kernel tree to 6.7, and we are planning
on 6.8. Where are these upstream currently? If they are in 6.8 there
is nothing to do here until we roll the kernel tree to 6.8 later this
cycle.
Can you tell me which mainline version these exist in currently?
--
You recei
Hello You-Sheng, or anyone else affected,
Accepted linux-firmware into mantic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/20230919.git3672ccab-0ubuntu2.8 in a few hours, and then in the
-proposed repository.
Please help us by testi
Hello You-Sheng, or anyone else affected,
Accepted linux-firmware into jammy-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/20220329.git681281e4-0ubuntu3.28 in a few hours, and then in
the -proposed repository.
Please help us by testi
should be in noble via the latest upstream rebase
** Changed in: linux-firmware (Ubuntu Noble)
Status: In Progress => Fix Released
--
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
Hello You-Sheng, or anyone else affected,
Accepted linux-firmware into mantic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/20230919.git3672ccab-0ubuntu2.8 in a few hours, and then in the
-proposed repository.
Please help us by testi
Hello Ciaby, or anyone else affected,
Accepted linux-firmware into jammy-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/20220329.git681281e4-0ubuntu3.28 in a few hours, and then in
the -proposed repository.
Please help us by testing t
Hello Ciaby, or anyone else affected,
Accepted linux-firmware into mantic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/20230919.git3672ccab-0ubuntu2.8 in a few hours, and then in the
-proposed repository.
Please help us by testing t
Hello Anson, or anyone else affected,
Accepted linux-firmware into jammy-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/20220329.git681281e4-0ubuntu3.28 in a few hours, and then in
the -proposed repository.
Please help us by testing t
Hello Anson, or anyone else affected,
Accepted linux-firmware into mantic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/20230919.git3672ccab-0ubuntu2.8 in a few hours, and then in the
-proposed repository.
Please help us by testing t
or maybe we'll just submit it there too..
** Changed in: linux-firmware (Ubuntu Mantic)
Status: In Progress => Fix Committed
--
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/2
how is this supposed to be verified in mantic, if it won't get the
kernel changes?
--
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 b
Hello You-Sheng, or anyone else affected,
Accepted linux-firmware into jammy-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/20220329.git681281e4-0ubuntu3.28 in a few hours, and then in
the -proposed repository.
Please help us by testi
Hello You-Sheng, or anyone else affected,
Accepted linux-firmware into mantic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/20230919.git3672ccab-0ubuntu2.8 in a few hours, and then in the
-proposed repository.
Please help us by testi
Public bug reported:
This is a public version of https://bugs.launchpad.net/bugs/2009321
Backport cpufreq: intel_pstate: Enable HWP IO boost for all servers
[upstream 1f5e62f5fb217f2c1e003236be7d03cf606c26c4 (merged in 6.4)] to
jammy.
[Impact]
Currently there is a CPU model check for Skylake d
Patch sent to the kernel team mailing list for review:
https://lists.ubuntu.com/archives/kernel-team/2024-January/148256.html
** Changed in: linux (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscri
Confirmed the fix has been applied to 24.04 Noble linux 6.8 repository:
"UBUNTU: [Config] y2038: Disable COMPAT and COMPAT_32BIT_TIME on
ppc64le"
https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/noble/commit/?h=master-
next&id=e1075f183b5fef4b05abf515fa1b4e1d26057e5a
As soon a
Confirmed the fix has been applied to 24.04 Noble linux 6.8 repository:
https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/noble/commit/?h=master-
next&id=3842f676a88b7c4b2063987beaae37f80505d841
As soon as the kernel is promoted to the noble-release pocket the bug
report will be
Same problem here, (Lenovo ideapad Flex 5 -14ARE05, Ubuntu 22.04.3 LTS),
although it did work JUST ONCE, randomly, in ~two years of ownership,
about a couple of months ago. The "i8042.nopnp=1 pci=nocrs" solution
broke my wifi (?) and didn't fix the problem
--
You received this bug notification be
I've been seeing this bug as far back as losetup is used (jammy) and the
previously merged fix has a significant improvement on successful builds
(0/3 succeeded without the patch applied vs 5/5 succeeded with the patch
applied this week) in jammy. Is someone already looking to SRU that
patch back
We noticed that this commit- "4ca10f3e3174 : scsi: mpt3sas: Perform
additional retries if doorbell read returns 0" is picked in ubuntu
22.04.4, but remaining patches are missing. Please pick all these
patches as they are very critical.
--
You received this bug notification because you are a membe
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-hwe-6.5 (Ubuntu)
Status: New => Confirmed
--
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.ne
Hi Jeff and Roxana,
These bugs are critical for us, and I don't see any update here. I would
like to know where are we on this. will these patches be included in
this point kernel?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Hi Jeff and Roxana,
These bugs are critical for us, and I don't see any update here. I would
like to know where are we on this. will these patches be included in
this point kernel?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
** Changed in: linux (Ubuntu Mantic)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Mantic)
Status: New => In Progress
** Changed in: linux (Ubuntu Mantic)
Assignee: (unassigned) => Manuel Diewald (die
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
This issue affects the Linux 6.7 series as well as from 6.7.3. I have
met this issue on mantic as I was trying to install the vanilla 6.7.3
kernel on a system with the nvidia 545 driver.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvid
** Tags removed: targetmilestone-inin---
** Tags added: targetmilestone-inin2204
--
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/2003374
Title:
Undefined Behavior Sanitizer (UBSAN) causes
/etc/kernel/header_postinst.d/dkms:
* dkms: running auto installation service for kernel 6.5.0-17-generic
Error! Could not locate dkms.conf file.
File: /var/lib/dkms/amdgpu/6.2.4-1652687.22.04/source/dkms.conf does not exist.
...fail!
run-parts: /etc/kernel/header_postinst.d/dkms exited with re
You have a broken/unsupported DKMS installed that breaks the header
installation. Please remove it:
$ dkms remove amdgpu/6.2.4-1652687.22.04
** Changed in: linux-hwe-6.5 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, wh
Public bug reported:
External USB storage is not detected when running the beta Ubuntu Core
20 image [0] on CM4. Same happens with the armhf image.
The issue has been discovered using Checkbox - the failing test is
usb/storage-detect [1].
Step to reproduce:
- Provision the CM4 with [0]
- Plug a
Thanks, I'll test the new kernel over the weekend.
--
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/2049634
Title:
smb: wsize blocks of bytes followed with binary zeros on copy,
destroyi
Hi R. Diez,
You have probably been following the chatter on the upstream mailing list
discussion. I initially thought the patch didn't fix the issue, as when I mount
with wsize=16850, the issue still occurs [1], but it seems that the intent of
the patch is to only correct when the server specifies
For Morgan le Fay:
Open a terminal, and type the following commands:
cd /lib/firmware/mediatek
sudo mv WIFI_MT7961_patch_mcu_1_2_hdr.bin WIFI_MT7961_patch_mcu_1_2_hdr.bin.orig
sudo mv WIFI_RAM_CODE_MT7961_1.bin WIFI_RAM_CODE_MT7961_1.bin.orig
sudo
https://gitlab.com/kernel-firmware/linux-firmwar
That's actually the wrong firmware commit, upstream main has this now:
commit 8b82ff279f1e04a72a51b4c5e5801c571f356617
Author: Rodrigo Siqueira
Date: Mon Jan 8 07:26:59 2024 -0700
amdgpu: DMCUB updates for DCN312
DMCUB updates for DCN312.
From internal git commit cc6d1d24518bf
** Description changed:
+ [Impact]
+
+ linux-firmare is missing updates to amdgpu VCN 4.0.0 firmware for Navi32
+ hardware.
+
+ Of the original list below, only VCN fw update is missing still.
+
+ [Test case]
+
+ Install the update
+ Validate brightness control works.
+ Validate that PSR works
Hi Jeff, Roxana,
Could we please get the test kernel for driver validation?
--
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/2044589
Title:
[Ubuntu 24.04 LTS] mpi3mr: Add support for SAS5
67 matches
Mail list logo
