[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-oracle-5.4/5.4.0.1051.55~18.04.31)
All autopkgtests for the newly accepted linux-meta-oracle-5.4 (5.4.0.1051.55~18.04.31) for bionic have finished running. The following regressions have been reported in tests triggered by the package: virtualbox/5.2.42-dfsg-0~ubuntu1.18.04.1 (amd64) kpatch/0.5.0-0ubuntu1.1 (amd64) virtualbox-hwe/5.2.42-dfsg-0~ubuntu1.18.04.1 (amd64) lxc/3.0.3-0ubuntu1~18.04.1 (arm64, amd64) zfs-linux/0.7.5-1ubuntu16.11 (arm64, amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-meta-oracle-5.4 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934282] Re: Some test in kselftest/net on focal source tree were not tested at all
** Description changed: [Impact] - Found this issue while debugging devlink_port_split.py test issue in bug 1928889. + Found this issue while debugging devlink_port_split.py test issue in + bug 1928889. - There are some tests like icmp_redirect.sh, ip6_gre_headroom.sh and etc - are not in the Makefile of the net directory, thus they are not tested - at all. + There are some tests like icmp_redirect.sh, ip6_gre_headroom.sh and + etc are not in the Makefile of the net directory, thus they are not + tested at all. [Fix] * 919a23e9d6ccf8 selftests/net: add missing tests to Makefile - Backport needed for Focal as we only have these tests leftover: + Backport needed for Focal as we only have these tests unadded: $ for file in $(ls *.sh); do grep -q $file Makefile || echo $file; done fib_nexthop_multiprefix.sh fib_nexthops.sh icmp_redirect.sh ip6_gre_headroom.sh route_localnet.sh [Test] - Run the "net" test suite in the kselftest directory from a patched source tree. These tests will be executed. + Run the "net" test suite in the kselftest directory from a patched + source tree. These tests will be executed. [Where problems could occur] - This change will bring in more test for our SRU, we might see new failures because of these test in the future. + This change will bring in more tests for our SRU, we might see new + failures because of these test in the future. -- 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/1934282 Title: Some test in kselftest/net on focal source tree were not tested at all Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: In Progress Bug description: [Impact] Found this issue while debugging devlink_port_split.py test issue in bug 1928889. There are some tests like icmp_redirect.sh, ip6_gre_headroom.sh and etc are not in the Makefile of the net directory, thus they are not tested at all. [Fix] * 919a23e9d6ccf8 selftests/net: add missing tests to Makefile Backport needed for Focal as we only have these tests unadded: $ for file in $(ls *.sh); do grep -q $file Makefile || echo $file; done fib_nexthop_multiprefix.sh fib_nexthops.sh icmp_redirect.sh ip6_gre_headroom.sh route_localnet.sh [Test] Run the "net" test suite in the kselftest directory from a patched source tree. These tests will be executed. [Where problems could occur] This change will bring in more tests for our SRU, we might see new failures because of these test in the future. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1934282/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934709] Re: btrfs: Automatic balance returns -EUCLEAN and leads to forced readonly filesystem
** Description changed:
BugLink: https://bugs.launchpad.net/bugs/1934709
[Impact]
During an automatic balance, users may encounter an error when writing
the transaction log to disk, when the log tree is being parsed, which
forces the filesystem to be remounted read-only and outputs the
following kernel oops:
BTRFS: error (device dm-14) in balance_level:1962: errno=-117 unknown
BTRFS info (device dm-14): forced readonly
BTRFS: Transaction aborted (error -117)
WARNING: CPU: 7 PID: 10818 at
/build/linux-99Rib2/linux-4.15.0/fs/btrfs/tree-log.c:2908
btrfs_sync_log+0xa28/0xbc0 [btrfs]
CPU: 7 PID: 10818 Comm: qemu-system-s39 Tainted: G OE
4.15.0-136-generic #140-Ubuntu
Hardware name: IBM 3907 LR1 A00 (LPAR)
Krnl PSW : 76bc1d64 9cc65255 (btrfs_sync_log+0xa28/0xbc0
[btrfs])
R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:0 PM:0 RI:0 EA:3
Krnl GPRS: 007899a6 0006 0027 0007
03ff801fdd8c 0002394c 0053650a7000 ff8b
00536b7f6000 0053ff8b 0053650a3800 005385935000
00532054de01 005385935290 03ff801fdd8c 004eebb1fae0
Krnl Code: 03ff801fdd80: c022a032 larl%r2,03ff80251de4
03ff801fdd86: c0e5fffb2181 brasl %r14,03ff80162088
#03ff801fdd8c: a7f40001 brc 15,03ff801fdd8e
>03ff801fdd90: e3a0f0a80004 lg %r10,168(%r15)
03ff801fdd96: b9040057 lgr %r5,%r7
03ff801fdd9a: a7490b5c lghi%r4,2908
03ff801fdd9e: b904002a lgr %r2,%r10
03ff801fdda2: c032604f larl%r3,03ff80249e40
Call Trace:
([<03ff801fdd8c>] btrfs_sync_log+0xa24/0xbc0 [btrfs])
[<03ff801c74e2>] btrfs_sync_file+0x3e2/0x550 [btrfs]
[<003ce6ce>] do_fsync+0x5e/0x90
[<003ce9ca>] SyS_fdatasync+0x32/0x48
[<008ffe5c>] system_call+0xd8/0x2c8
Last Breaking-Event-Address:
[<03ff801fdd8c>] btrfs_sync_log+0xa24/0xbc0 [btrfs]
BTRFS: error (device dm-14) in btrfs_sync_log:2908: errno=-117 unknown
BTRFS error (device dm-14): pending csums is 269639680
This bug appears to be linked to bug 1933172, but is different and has a
different root cause. Again, I believe that this is a regression
introduced in the fixing of CVE-2019-19036, from 4.15.0-109-generic.
[Fix]
Analysis of the kernel oops is as follows:
The first thing we see is that BTRFS entered ERROR state with the
reason:
in balance_level:1962: errno=-117 unknown
Now errno -117 is:
100 #define EUCLEAN 117 /* Structure needs cleaning */
btrfs treats -EUCLEAN as if corruption has happened. Let's see where
this is returned from.
If we start at fs/btrfs/ctree.c in balance_level(), line 1962:
1917 static noinline int balance_level(struct btrfs_trans_handle *trans,
1918 struct btrfs_root *root,
1919 struct btrfs_path *path, int level)
1920 {
...
1958 /* promote the child to a root */
1959 child = read_node_slot(fs_info, mid, 0);
1960 if (IS_ERR(child)) {
1961 ret = PTR_ERR(child);
1962 btrfs_handle_fs_error(fs_info, ret, NULL);
1963 goto enospc;
1964 }
...
2136 }
We are in the middle of a balancing operation, and if you happen to be
familiar with how b-tree data structures work, we are promoting a child
node to a topmost root node.
The error most likely happens in read_node_slot(), with the lines after
it printing that an error has happened.
1887 static noinline struct extent_buffer *
1888 read_node_slot(struct btrfs_fs_info *fs_info, struct extent_buffer
*parent,
1889int slot)
1890 {
...
1900 btrfs_node_key_to_cpu(parent, _key, slot);
1901 eb = read_tree_block(fs_info, btrfs_node_blockptr(parent, slot),
1902 btrfs_node_ptr_generation(parent, slot),
1903 level - 1, _key);
...
1910 }
There are two calls here which are relevant. btrfs_node_key_to_cpu() and
read_tree_block().
Let's look at read_tree_block() in fs/btrfs/disk-io.c:
1147 struct extent_buffer *read_tree_block(struct btrfs_fs_info *fs_info, u64
bytenr,
1148 u64 parent_transid, int level,
1149 struct btrfs_key *first_key)
1150 {
1151 struct extent_buffer *buf = NULL;
1152 int ret;
1153
1154 buf = btrfs_find_create_tree_block(fs_info, bytenr);
1155 if (IS_ERR(buf))
1156 return buf;
1157
1158 ret = btree_read_extent_buffer_pages(fs_info, buf, parent_transid,
1159 level, first_key);
1160 if (ret) {
1161 free_extent_buffer_stale(buf);
1162 return
[Kernel-packages] [Bug 1926801] Re: BCM2835 SPI chipselect limit - kernel/driver panic
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1926801 Title: BCM2835 SPI chipselect limit - kernel/driver panic Status in linux package in Ubuntu: Expired Bug description: Bug fix was just committed by Phil Elwell , and appears as response driver error reported for Raspberry Pi OS. I have the same problem with driver in Ubuntu 21.04. My apology for not knowing how driver fixes are coordinated across Pi OS and Ubuntu, so I am providing the information here in hopes a fix will be made available in Ubuntu 21.04. Please let me know if driver fix will be available for 21.04. As background, my previous comment on github in discussion of problem with Mr. Elwell was: A limit of 24 chipselects would work for me. -- This would likely solve problem seeing a kernel panic (bad kernel memory reference) in 5.11.0-1007-raspi after configuring 6 chipselects for for BCM2835 SPI via dtoverlay. Kernel panic is on shutdown/reboot, however, memory corruption for more than 4 chipselects likely has other runtime consequences. --- Details on new driver commit for drivers/spi/spi-bcm2835.c from Mr. Elwell on 4-30-2021: https://github.com/raspberrypi/linux/commit/05f8d5826e28e9d82485c03b65c18d5013ba13bd spi: bcm2835: Increase the CS limit to 24 Increase the maximum number of CS lines to 24, and ensure this limit is not exceeded. See: #4281 -- https://github.com/raspberrypi/linux/pull/4281 Suggested-by: Joe Burmeister Signed-off-by: Phil Elwell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926801/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934282] Re: Some test in kselftest/net on focal source tree were not tested at all
** Description changed: [Impact] Found this issue while debugging devlink_port_split.py test issue in bug 1928889. There are some tests like icmp_redirect.sh, ip6_gre_headroom.sh and etc are not in the Makefile of the net directory, thus they are not tested at all. [Fix] - * 919a23e9d6ccf8 selftests/net: add missing tests to Makefile + * 919a23e9d6ccf8 selftests/net: add missing tests to Makefile + + Backport needed for Focal as we only have these tests leftover: + $ for file in $(ls *.sh); do grep -q $file Makefile || echo $file; done + fib_nexthop_multiprefix.sh + fib_nexthops.sh + icmp_redirect.sh + ip6_gre_headroom.sh + route_localnet.sh [Test] - Run the "net" test suite in the kselftest directory from a patched source tree. These tests will be executed. + Run the "net" test suite in the kselftest directory from a patched source tree. These tests will be executed. [Where problems could occur] This change will bring in more test for our SRU, we might see new failures because of these test in the future. ** Tags added: 5.4 focal sru-20210621 ubuntu-kernel-selftests ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: linux (Ubuntu) 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/1934282 Title: Some test in kselftest/net on focal source tree were not tested at all Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: In Progress Bug description: [Impact] Found this issue while debugging devlink_port_split.py test issue in bug 1928889. There are some tests like icmp_redirect.sh, ip6_gre_headroom.sh and etc are not in the Makefile of the net directory, thus they are not tested at all. [Fix] * 919a23e9d6ccf8 selftests/net: add missing tests to Makefile Backport needed for Focal as we only have these tests leftover: $ for file in $(ls *.sh); do grep -q $file Makefile || echo $file; done fib_nexthop_multiprefix.sh fib_nexthops.sh icmp_redirect.sh ip6_gre_headroom.sh route_localnet.sh [Test] Run the "net" test suite in the kselftest directory from a patched source tree. These tests will be executed. [Where problems could occur] This change will bring in more test for our SRU, we might see new failures because of these test in the future. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1934282/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934709] [NEW] btrfs: Automatic balance returns -EUCLEAN and leads to forced readonly filesystem
Public bug reported:
BugLink: https://bugs.launchpad.net/bugs/1934709
[Impact]
During an automatic balance, users may encounter an error when writing
the transaction log to disk, when the log tree is being parsed, which
forces the filesystem to be remounted read-only and outputs the
following kernel oops:
BTRFS: error (device dm-14) in balance_level:1962: errno=-117 unknown
BTRFS info (device dm-14): forced readonly
BTRFS: Transaction aborted (error -117)
WARNING: CPU: 7 PID: 10818 at
/build/linux-99Rib2/linux-4.15.0/fs/btrfs/tree-log.c:2908
btrfs_sync_log+0xa28/0xbc0 [btrfs]
CPU: 7 PID: 10818 Comm: qemu-system-s39 Tainted: G OE
4.15.0-136-generic #140-Ubuntu
Hardware name: IBM 3907 LR1 A00 (LPAR)
Krnl PSW : 76bc1d64 9cc65255 (btrfs_sync_log+0xa28/0xbc0
[btrfs])
R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:0 PM:0 RI:0 EA:3
Krnl GPRS: 007899a6 0006 0027 0007
03ff801fdd8c 0002394c 0053650a7000 ff8b
00536b7f6000 0053ff8b 0053650a3800 005385935000
00532054de01 005385935290 03ff801fdd8c 004eebb1fae0
Krnl Code: 03ff801fdd80: c022a032 larl%r2,03ff80251de4
03ff801fdd86: c0e5fffb2181 brasl %r14,03ff80162088
#03ff801fdd8c: a7f40001 brc 15,03ff801fdd8e
>03ff801fdd90: e3a0f0a80004 lg %r10,168(%r15)
03ff801fdd96: b9040057 lgr %r5,%r7
03ff801fdd9a: a7490b5c lghi%r4,2908
03ff801fdd9e: b904002a lgr %r2,%r10
03ff801fdda2: c032604f larl%r3,03ff80249e40
Call Trace:
([<03ff801fdd8c>] btrfs_sync_log+0xa24/0xbc0 [btrfs])
[<03ff801c74e2>] btrfs_sync_file+0x3e2/0x550 [btrfs]
[<003ce6ce>] do_fsync+0x5e/0x90
[<003ce9ca>] SyS_fdatasync+0x32/0x48
[<008ffe5c>] system_call+0xd8/0x2c8
Last Breaking-Event-Address:
[<03ff801fdd8c>] btrfs_sync_log+0xa24/0xbc0 [btrfs]
BTRFS: error (device dm-14) in btrfs_sync_log:2908: errno=-117 unknown
BTRFS error (device dm-14): pending csums is 269639680
This bug appears to be linked to bug 1933172, but is different and has a
different root cause. Again, I believe that this is a regression
introduced in the fixing of CVE-2019-19036, from 4.15.0-109-generic.
[Fix]
Analysis of the kernel oops is as follows:
The first thing we see is that BTRFS entered ERROR state with the
reason:
in balance_level:1962: errno=-117 unknown
Now errno -117 is:
100 #define EUCLEAN 117 /* Structure needs cleaning */
btrfs treats -EUCLEAN as if corruption has happened. Let's see where
this is returned from.
If we start at fs/btrfs/ctree.c in balance_level(), line 1962:
1917 static noinline int balance_level(struct btrfs_trans_handle *trans,
1918 struct btrfs_root *root,
1919 struct btrfs_path *path, int level)
1920 {
...
1958 /* promote the child to a root */
1959 child = read_node_slot(fs_info, mid, 0);
1960 if (IS_ERR(child)) {
1961 ret = PTR_ERR(child);
1962 btrfs_handle_fs_error(fs_info, ret, NULL);
1963 goto enospc;
1964 }
...
2136 }
We are in the middle of a balancing operation, and if you happen to be
familiar with how b-tree data structures work, we are promoting a child
node to a topmost root node.
The error most likely happens in read_node_slot(), with the lines after
it printing that an error has happened.
1887 static noinline struct extent_buffer *
1888 read_node_slot(struct btrfs_fs_info *fs_info, struct extent_buffer *parent,
1889int slot)
1890 {
...
1900 btrfs_node_key_to_cpu(parent, _key, slot);
1901 eb = read_tree_block(fs_info, btrfs_node_blockptr(parent, slot),
1902 btrfs_node_ptr_generation(parent, slot),
1903 level - 1, _key);
...
1910 }
There are two calls here which are relevant. btrfs_node_key_to_cpu() and
read_tree_block().
Let's look at read_tree_block() in fs/btrfs/disk-io.c:
1147 struct extent_buffer *read_tree_block(struct btrfs_fs_info *fs_info, u64
bytenr,
1148 u64 parent_transid, int level,
1149 struct btrfs_key *first_key)
1150 {
1151 struct extent_buffer *buf = NULL;
1152 int ret;
1153
1154 buf = btrfs_find_create_tree_block(fs_info, bytenr);
1155 if (IS_ERR(buf))
1156 return buf;
1157
1158 ret = btree_read_extent_buffer_pages(fs_info, buf, parent_transid,
1159 level, first_key);
1160 if (ret) {
1161 free_extent_buffer_stale(buf);
1162 return ERR_PTR(ret);
1163 }
1164 return buf;
1165
1166 }
The interesting one here is btree_read_extent_buffer_pages():
498 static int btree_read_extent_buffer_pages(struct btrfs_fs_info *fs_info,
499
[Kernel-packages] [Bug 1923335] Re: At shutdown the spinner logo disappears and a second later it comes back frozen for a while (in kernel 5.11 but 5.10.16 works)
Thanks Norbert. Reddit seems convinced this is a kernel regression in 5.11 which would line up with the findings here, so let's go with that for now. ** Summary changed: - At shutdown the spinner logo disappears and a second later it comes back frozen for a while + At shutdown the spinner logo disappears and a second later it comes back frozen for a while (in kernel 5.11 but 5.10.16 works) ** Package changed: plymouth (Ubuntu) => linux (Ubuntu) ** No longer affects: snapd (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/1923335 Title: At shutdown the spinner logo disappears and a second later it comes back frozen for a while (in kernel 5.11 but 5.10.16 works) Status in linux package in Ubuntu: Confirmed Bug description: At shutdown the spinner logo disapear and a scond later it comes back and stay for 15sec. When I remove "splash" from the grub commandline the shutdown is fast (no extra 15 sec.). I can't find any hints in the log. It seem to happen after the log stopped. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu62 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-01-29 (71 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210129) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 0bda:568c Realtek Semiconductor Corp. Integrated Webcam HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 5580 Package: plymouth 0.9.5-0ubuntu3 PackageArchitecture: amd64 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-13-generic root=UUID=469b1c18-e632-4872-a47c-7b36bce081dc ro quiet splash vt.handoff=7 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-13-generic root=UUID=469b1c18-e632-4872-a47c-7b36bce081dc ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Tags: wayland-session hirsute TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth Uname: Linux 5.11.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/25/2020 dmi.bios.release: 1.18 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.18.2 dmi.board.name: 00C013 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.18.2:bd09/25/2020:br1.18:svnDellInc.:pnLatitude5580:pvr:rvnDellInc.:rn00C013:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5580 dmi.product.sku: 07A8 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1923335/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1923335] [NEW] At shutdown the spinner logo disappears and a second later it comes back frozen for a while (in kernel 5.11 but 5.10.16 works)
You have been subscribed to a public bug: At shutdown the spinner logo disapear and a scond later it comes back and stay for 15sec. When I remove "splash" from the grub commandline the shutdown is fast (no extra 15 sec.). I can't find any hints in the log. It seem to happen after the log stopped. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu62 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-01-29 (71 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210129) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 0bda:568c Realtek Semiconductor Corp. Integrated Webcam HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 5580 Package: plymouth 0.9.5-0ubuntu3 PackageArchitecture: amd64 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-13-generic root=UUID=469b1c18-e632-4872-a47c-7b36bce081dc ro quiet splash vt.handoff=7 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-13-generic root=UUID=469b1c18-e632-4872-a47c-7b36bce081dc ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Tags: wayland-session hirsute TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth Uname: Linux 5.11.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/25/2020 dmi.bios.release: 1.18 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.18.2 dmi.board.name: 00C013 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.18.2:bd09/25/2020:br1.18:svnDellInc.:pnLatitude5580:pvr:rvnDellInc.:rn00C013:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5580 dmi.product.sku: 07A8 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Medium Status: Confirmed ** Affects: snapd (Ubuntu) Importance: Medium Status: Confirmed ** Tags: apport-collected hirsute impish performance regression-release wayland-session -- At shutdown the spinner logo disappears and a second later it comes back frozen for a while (in kernel 5.11 but 5.10.16 works) https://bugs.launchpad.net/bugs/1923335 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930279] Re: [Ivy Bridge] flashing sliced triangles on screen
** 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/1930279 Title: [Ivy Bridge] flashing sliced triangles on screen Status in linux package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Bug description: when i did upgrade my ubuntu from 20.04 to 20.10 i have small winking triangles on my screen, they sometimes will appear when i watching a youtube video they will appear on the video's seek bar or when i typing they will appear on selected texts,but the main and most annoying state of it happens when I am playing minecraft,my entire game screen has these little triangles ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-53.60-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 31 18:05:33 2021 DistUpgraded: 2021-05-27 14:18:07,483 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: groovy DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.4.0-73-generic, x86_64: installed virtualbox, 6.1.16, 5.8.0-53-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [1043:844d] InstallationDate: Installed on 2020-01-10 (507 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-53-generic root=UUID=a5a5279f-cdf5-4129-94fa-8f17f7401833 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to groovy on 2021-05-27 (4 days ago) dmi.bios.date: 03/19/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1204 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H61-M LX R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1204:bd03/19/2014:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MLXR2.0:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930279/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-snapdragon/4.15.0.1108.111)
All autopkgtests for the newly accepted linux-meta-snapdragon (4.15.0.1108.111) for bionic have finished running. The following regressions have been reported in tests triggered by the package: lxd/3.0.3-0ubuntu1~18.04.1 (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-meta-snapdragon [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-kvm/4.15.0.1096.92)
All autopkgtests for the newly accepted linux-meta-kvm (4.15.0.1096.92) for bionic have finished running. The following regressions have been reported in tests triggered by the package: glibc/2.27-3ubuntu1.4 (amd64) lttng-modules/2.10.8-1ubuntu2~18.04.3 (amd64) nvidia-graphics-drivers-450-server/450.119.04-0ubuntu0.18.04.2 (amd64) kpatch/0.5.0-0ubuntu1.1 (amd64) dahdi-linux/1:2.11.1~dfsg-1ubuntu4.2 (amd64) ddcci-driver-linux/0.3.1-2ubuntu0.1 (amd64) nvidia-graphics-drivers-460-server/460.73.01-0ubuntu0.18.04.1 (amd64) nvidia-graphics-drivers-460/460.80-0ubuntu0.18.04.2 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-meta-kvm [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930754] Re: e1000e extremly slow
** Also affects: oem-priority Importance: Undecided Status: New ** Tags added: oem-priority ** Changed in: oem-priority Importance: Undecided => High ** Changed in: oem-priority Status: New => Confirmed -- 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/1930754 Title: e1000e extremly slow Status in OEM Priority Project: Confirmed Status in linux-oem-5.10 package in Ubuntu: Confirmed Bug description: We have dell latitude 5420 & 5520 laptops with onboard intel ethernet controller. Problem is that the ethernet port is extremely slow. about 100kbyte/s download throughput while on a gigabit connection. Upload seems to work just fine. Also when I pxe boot the system it's also painfully slow. But here comes the funny part. When I attach a usb memory stick the throughput of the networkcontroller is as expected. I've used latest ubuntu 20.04.2 kernel 5.8.0-55 I've used latest ubuntu 20.04.2 kernel 5.10.0-1029-oem Turns out this problem is not showing up when I manually install the 5.8.18 kernel. Also when I create my own iso with the help of Cubic and install the 5.8.18 kernel in it the pxe boot is working as expected with high throughput system: Dell latitude 5420 + 5520 nic: Ethernet Connection (13) I219-LM ubuntu 20.04.2 module: e1000e Please assist. Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1930754/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1928744] Re: Disk IO very slow on kernel 4.15.0-142-generic
John - thanks for finding ==> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926081 There is a great testing work done there. For this thread I have been running kernel 4.15.0-144-generic for the last 3 weeks and haven't seen the issue. -- 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/1928744 Title: Disk IO very slow on kernel 4.15.0-142-generic Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: After upgrading Ubuntu 18.04 kernel from 4.15.0-136-generic to kernel 4.15.0-142-generic disk IOs (writes) are suffering from terrible delay. Time required to write 1GB of data to the dist is ~12 minutes. 1GB in 12 minutes: strace -ttvvff -o mel.strace dd bs=1024k count=1024 if=/dev/zero of=/data/disk_test/dd_test Before the upgrade, it took seconds to complete. The only change which was done on the system was security upgrade done with unattended-upgrade utility and main repositories for bionic and bionic-security. This is physical server LENOVO System x3650 M5, with Symbios Logic MegaRAID SAS-3 3108 disk controller. The only difference which I see is that there are more modules loaded by the latest kernel. I would expect that the performance would be the same. There were no changes to the physical server and the disks are reported as online and healthy. No only dd is affected but also all disk-based operation by barman (we are using postgres steaming backup along with rsync/ssh archiving). I think this could be a kernel bug. I would be happy to provide other information which would help in fixing this problem. = Details: lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 lsmod Module Size Used by ip6_tables 28672 0 iptable_filter 16384 0 ip_tables 28672 1 iptable_filter x_tables 40960 3 iptable_filter,ip6_tables,ip_tables tcp_diag 16384 0 udp_diag 16384 0 raw_diag 16384 0 inet_diag 24576 3 tcp_diag,raw_diag,udp_diag unix_diag 16384 0 binfmt_misc20480 1 ipmi_ssif 32768 0 kvm_intel 217088 0 kvm 614400 1 kvm_intel irqbypass 16384 1 kvm crct10dif_pclmul 16384 0 crc32_pclmul 16384 0 ghash_clmulni_intel16384 0 pcbc 16384 0 aesni_intel 188416 0 aes_x86_64 20480 1 aesni_intel crypto_simd16384 1 aesni_intel glue_helper16384 1 aesni_intel cryptd 24576 3 crypto_simd,ghash_clmulni_intel,aesni_intel ipmi_si57344 0 ipmi_devintf 20480 0 ipmi_msghandler53248 3 ipmi_devintf,ipmi_si,ipmi_ssif acpi_pad 180224 0 bonding 163840 0 lp 20480 0 parport49152 1 lp autofs440960 2 mgag20045056 1 i2c_algo_bit 16384 1 mgag200 ttm 106496 1 mgag200 drm_kms_helper172032 1 mgag200 syscopyarea16384 1 drm_kms_helper tg3 167936 0 sysfillrect16384 1 drm_kms_helper sysimgblt 16384 1 drm_kms_helper fb_sys_fops16384 1 drm_kms_helper ptp20480 1 tg3 drm 401408 4 drm_kms_helper,mgag200,ttm pps_core 20480 1 ptp megaraid_sas 143360 12 lspci -vnn -s 0b:00.0 0b:00.0 RAID bus controller [0104]: LSI Logic / Symbios Logic MegaRAID SAS-3 3108 [Invader] [1000:005d] (rev 02) Subsystem: IBM MegaRAID SAS-3 3108 [Invader] [1014:0454] Physical Slot: 9 Flags: bus master, fast devsel, latency 0, IRQ 31, NUMA node 0 I/O ports at 2e00 [size=256] Memory at 903f (64-bit, non-prefetchable) [size=64K] Memory at 9040 (64-bit, non-prefetchable) [size=1M] Expansion ROM at [disabled] Capabilities: [50] Power Management version 3 Capabilities: [68] Express Endpoint, MSI 00 Capabilities: [d0] Vital Product Data Capabilities: [a8] MSI: Enable- Count=1/1 Maskable+ 64bit+ Capabilities: [c0] MSI-X: Enable+ Count=97 Masked- Capabilities: [100] Advanced Error Reporting Capabilities: [1e0] #19 Capabilities: [1c0] Power Budgeting Capabilities: [148] Alternative Routing-ID Interpretation (ARI) Kernel driver in use: megaraid_sas Kernel modules: megaraid_sas Strace example for 10MB: strace -ttvvff -o mel.strace dd bs=1024k count=10 if=/dev/zero of=/data/disk_test/dd_test 10+0 records in
[Kernel-packages] [Bug 1934701] [NEW] external USB drive hangs and unable to recover without hard reset
Public bug reported: As also reported on the Raspberry Pi bug report: https://github.com/raspberrypi/linux/issues/3981 I'm experiencing this with all 5.x kernels usually within a day or 2 of a restart: Jun 29 20:20:35 tiny-myth kernel: [85834.433030] xhci_hcd :04:00.0: WARN Cannot submit Set TR Deq Ptr Jun 29 20:20:35 tiny-myth kernel: [85834.433052] xhci_hcd :04:00.0: A Set TR Deq Ptr command is pending. Jun 29 20:20:35 tiny-myth kernel: [85834.565209] usb 9-2: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd Jun 29 20:21:06 tiny-myth kernel: [85865.665815] xhci_hcd :04:00.0: WARN Cannot submit Set TR Deq Ptr Jun 29 20:21:06 tiny-myth kernel: [85865.665838] xhci_hcd :04:00.0: A Set TR Deq Ptr command is pending. Jun 29 20:21:06 tiny-myth kernel: [85865.805725] usb 9-2: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd I've rolled back to 4.19 kernel and error did occur once but appears to happen less frequently (running for a few days now and hasn't triggered). This is on a device that's been running fine since 2012 with none of these issues until I upgraded to 20.04 in January 2021, at which point I've had to reboot the device constantly to re-attach to storage. ** 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/1934701 Title: external USB drive hangs and unable to recover without hard reset Status in linux package in Ubuntu: New Bug description: As also reported on the Raspberry Pi bug report: https://github.com/raspberrypi/linux/issues/3981 I'm experiencing this with all 5.x kernels usually within a day or 2 of a restart: Jun 29 20:20:35 tiny-myth kernel: [85834.433030] xhci_hcd :04:00.0: WARN Cannot submit Set TR Deq Ptr Jun 29 20:20:35 tiny-myth kernel: [85834.433052] xhci_hcd :04:00.0: A Set TR Deq Ptr command is pending. Jun 29 20:20:35 tiny-myth kernel: [85834.565209] usb 9-2: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd Jun 29 20:21:06 tiny-myth kernel: [85865.665815] xhci_hcd :04:00.0: WARN Cannot submit Set TR Deq Ptr Jun 29 20:21:06 tiny-myth kernel: [85865.665838] xhci_hcd :04:00.0: A Set TR Deq Ptr command is pending. Jun 29 20:21:06 tiny-myth kernel: [85865.805725] usb 9-2: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd I've rolled back to 4.19 kernel and error did occur once but appears to happen less frequently (running for a few days now and hasn't triggered). This is on a device that's been running fine since 2012 with none of these issues until I upgraded to 20.04 in January 2021, at which point I've had to reboot the device constantly to re-attach to storage. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934701/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931744] Re: Dell Precision 5750: internal mic stopped working after kernel update to 5.10.0-1029-oem
I guess the issues with microphone described in https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.10/+bug/1932303 must have the same cause as in this case as the audio hardware should be identical. -- 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/1931744 Title: Dell Precision 5750: internal mic stopped working after kernel update to 5.10.0-1029-oem Status in linux-oem-5.10 package in Ubuntu: New Bug description: On all kernel versions that I used before the 5.10.0-1029-oem the internal microphone of my Dell Precision 5750 worked perfectly. After the upgrade to 5.10.0-1029-oem the internal mic stopped working but I can still use an external mic. I couldn't enable the internal mic using pavucontrol and alsamixer. lsb_release -rd Description:Ubuntu 20.04.2 LTS Release:20.04 P.S. there is the same issue with Dell XPS 9700: - https://askubuntu.com/questions/1343942/dell-xps-17-9700-internal-microphone-not-working - https://askubuntu.com/q/1344112/843383 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.10/+bug/1931744/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-dell300x/4.15.0.1023.25)
All autopkgtests for the newly accepted linux-meta-dell300x (4.15.0.1023.25) for bionic have finished running. The following regressions have been reported in tests triggered by the package: lxd/3.0.3-0ubuntu1~18.04.1 (amd64) lxc/3.0.3-0ubuntu1~18.04.1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-meta-dell300x [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-azure-4.15/4.15.0.1119.92)
All autopkgtests for the newly accepted linux-meta-azure-4.15 (4.15.0.1119.92) for bionic have finished running. The following regressions have been reported in tests triggered by the package: lxd/3.0.3-0ubuntu1~18.04.1 (amd64) lxc/3.0.3-0ubuntu1~18.04.1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-meta-azure-4.15 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-gcp-4.15/4.15.0.1104.122)
All autopkgtests for the newly accepted linux-meta-gcp-4.15 (4.15.0.1104.122) for bionic have finished running. The following regressions have been reported in tests triggered by the package: lxd/3.0.3-0ubuntu1~18.04.1 (amd64) lxc/3.0.3-0ubuntu1~18.04.1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-meta-gcp-4.15 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-oracle/4.15.0.1076.86)
All autopkgtests for the newly accepted linux-meta-oracle (4.15.0.1076.86) for bionic have finished running. The following regressions have been reported in tests triggered by the package: lxd/3.0.3-0ubuntu1~18.04.1 (amd64) lxc/3.0.3-0ubuntu1~18.04.1 (amd64) glibc/2.27-3ubuntu1.4 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-meta-oracle [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-aws/4.15.0.1107.110)
All autopkgtests for the newly accepted linux-meta-aws (4.15.0.1107.110) for bionic have finished running. The following regressions have been reported in tests triggered by the package: lxc/3.0.3-0ubuntu1~18.04.1 (arm64, amd64) lxd/3.0.3-0ubuntu1~18.04.1 (arm64, amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-meta-aws [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1913933] Re: System freeze while dbus-daemon execution
Hi update from my site: so I think the issue might be unrelated to dbus-daemon. Why do I think that? * I installed Linux Mint 20.1 on the same machine, reasons do not matter here * I got the same freezes on the system * I updated the kernel to 5.11 and still have the same freezes happen every other day. It happens randomly and the syslog always has these ascii NUL characters, but I learned that this is just a symptom rather than a cause. I will do a memtest soon so I can see if this is faulty hardware (though the Windows 10 installation on a separate disk works just fine). Cheers -- 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/1913933 Title: System freeze while dbus-daemon execution Status in linux package in Ubuntu: Confirmed Bug description: I regularly get my system frozen while using. It does not occur on any user interaction I do periodically, so I checked the log files last time it happened: These are the last 3 kernel log entries before the freeze: Jan 30 15:34:29 ubuntu kernel: [24749.856278] audit: type=1400 audit(1612017269.344:43): apparmor="DENIED" operation="open" profile="snap.standard-notes.standard-notes" name="/home/chshr/.dotfiles/config/.config/gtk-3.0/settings.ini" pid=21631 comm="standard-notes" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 Jan 30 15:34:29 ubuntu kernel: [24749.903525] audit: type=1107 audit(1612017269.392:44): pid=1236 uid=103 auid=4294967295 ses=4294967295 subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/" interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" mask="send" name="org.bluez" pid=21631 label="snap.standard-notes.standard-notes" Jan 30 15:34:29 ubuntu kernel: [24749.903525] exe="/usr/bin/dbus-daemon" sauid=103 hostname=? addr=? terminal=?' ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ So I think this is related to the dbus-daemon. If you need any more information, please let me know so I can provide them. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: dbus 1.12.20-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Sun Jan 31 09:22:49 2021 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/usr/bin/bash SourcePackage: dbus UpgradeStatus: Upgraded to groovy on 2021-01-24 (6 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: chshr 2241 F pulseaudio /dev/snd/controlC0: chshr 2241 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.10 HibernationDevice: RESUME=UUID=a16d1655-2fcf-4952-8a1b-3a45eb9b2c52 MachineType: Micro-Star International Co., Ltd MS-7A34 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/usr/bin/bash ProcFB: 0 VESA VGA
[Kernel-packages] [Bug 1810183] Re: numpad on touchpad doesn't work in ASUS Zenbook 14
Tested on Asus Expertbook B9 (model B9400CEA) with Ubuntu 21.04 0.123456789/*-+%= Many thanks Mohamed! -- 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/1810183 Title: numpad on touchpad doesn't work in ASUS Zenbook 14 Status in Linux: New Status in linux package in Ubuntu: Confirmed Bug description: I have Asus Zenbook 14 UX433FA which I have installed Ubuntu 18.10 alongside windows 10. The numeric keypads are within the touchpad and are supposed to be turned on by a button on the touchpad. This works well in Windows but doesn't work in Ubuntu. I have tried to search for any related problems/solutions online but I haven't been able to. I will appreciate any suggestion or help. Thanks, --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.19.11-041911-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.18.10-041810-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1810183/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1928744] Re: Disk IO very slow on kernel 4.15.0-142-generic
I note it is possible this is a duplicate of
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926081
--
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/1928744
Title:
Disk IO very slow on kernel 4.15.0-142-generic
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Bionic:
Confirmed
Bug description:
After upgrading Ubuntu 18.04 kernel from 4.15.0-136-generic to kernel
4.15.0-142-generic disk IOs (writes) are suffering from terrible
delay.
Time required to write 1GB of data to the dist is ~12 minutes.
1GB in 12 minutes:
strace -ttvvff -o mel.strace dd bs=1024k count=1024 if=/dev/zero
of=/data/disk_test/dd_test
Before the upgrade, it took seconds to complete.
The only change which was done on the system was security upgrade done with
unattended-upgrade utility and main repositories for bionic and bionic-security.
This is physical server LENOVO System x3650 M5, with Symbios Logic
MegaRAID SAS-3 3108 disk controller.
The only difference which I see is that there are more modules loaded
by the latest kernel.
I would expect that the performance would be the same. There were no
changes to the physical server and the disks are reported as online
and healthy. No only dd is affected but also all disk-based operation
by barman (we are using postgres steaming backup along with rsync/ssh
archiving).
I think this could be a kernel bug. I would be happy to provide other
information which would help in fixing this problem.
=
Details:
lsb_release -rd
Description: Ubuntu 18.04.1 LTS
Release: 18.04
lsmod
Module Size Used by
ip6_tables 28672 0
iptable_filter 16384 0
ip_tables 28672 1 iptable_filter
x_tables 40960 3 iptable_filter,ip6_tables,ip_tables
tcp_diag 16384 0
udp_diag 16384 0
raw_diag 16384 0
inet_diag 24576 3 tcp_diag,raw_diag,udp_diag
unix_diag 16384 0
binfmt_misc20480 1
ipmi_ssif 32768 0
kvm_intel 217088 0
kvm 614400 1 kvm_intel
irqbypass 16384 1 kvm
crct10dif_pclmul 16384 0
crc32_pclmul 16384 0
ghash_clmulni_intel16384 0
pcbc 16384 0
aesni_intel 188416 0
aes_x86_64 20480 1 aesni_intel
crypto_simd16384 1 aesni_intel
glue_helper16384 1 aesni_intel
cryptd 24576 3 crypto_simd,ghash_clmulni_intel,aesni_intel
ipmi_si57344 0
ipmi_devintf 20480 0
ipmi_msghandler53248 3 ipmi_devintf,ipmi_si,ipmi_ssif
acpi_pad 180224 0
bonding 163840 0
lp 20480 0
parport49152 1 lp
autofs440960 2
mgag20045056 1
i2c_algo_bit 16384 1 mgag200
ttm 106496 1 mgag200
drm_kms_helper172032 1 mgag200
syscopyarea16384 1 drm_kms_helper
tg3 167936 0
sysfillrect16384 1 drm_kms_helper
sysimgblt 16384 1 drm_kms_helper
fb_sys_fops16384 1 drm_kms_helper
ptp20480 1 tg3
drm 401408 4 drm_kms_helper,mgag200,ttm
pps_core 20480 1 ptp
megaraid_sas 143360 12
lspci -vnn -s 0b:00.0
0b:00.0 RAID bus controller [0104]: LSI Logic / Symbios Logic MegaRAID SAS-3
3108 [Invader] [1000:005d] (rev 02)
Subsystem: IBM MegaRAID SAS-3 3108 [Invader] [1014:0454]
Physical Slot: 9
Flags: bus master, fast devsel, latency 0, IRQ 31, NUMA node 0
I/O ports at 2e00 [size=256]
Memory at 903f (64-bit, non-prefetchable) [size=64K]
Memory at 9040 (64-bit, non-prefetchable) [size=1M]
Expansion ROM at [disabled]
Capabilities: [50] Power Management version 3
Capabilities: [68] Express Endpoint, MSI 00
Capabilities: [d0] Vital Product Data
Capabilities: [a8] MSI: Enable- Count=1/1 Maskable+ 64bit+
Capabilities: [c0] MSI-X: Enable+ Count=97 Masked-
Capabilities: [100] Advanced Error Reporting
Capabilities: [1e0] #19
Capabilities: [1c0] Power Budgeting
Capabilities: [148] Alternative Routing-ID Interpretation (ARI)
Kernel driver in use: megaraid_sas
Kernel modules: megaraid_sas
Strace example for 10MB:
strace -ttvvff -o mel.strace dd bs=1024k count=10 if=/dev/zero
of=/data/disk_test/dd_test
10+0 records in
10+0 records out
10485760 bytes (10 MB, 10 MiB) copied, 6.73972 s, 1.6 MB/s
14:59:19.145037 execve("/bin/dd", ["dd", "bs=1024k",
[Kernel-packages] [Bug 1928600] Re: [amdgpu] Gnome locks up with artifacts on screen and [drm:amdgpu_dm_commit_planes [amdgpu]] *ERROR* Waiting for fences timed out!
I was ready to update with the fact that Kernel 5.9 and 5.10 have seemed largely stable when the first full release of 5.10, which I had been running for a while without problems, managed to lock up. For the first time it has provided an error message that may be useful though. I am attaching a photo of the screen, but the message text was: ♦♦[50545.326736] [drm:amdgpu_job_timeout [amdgpu]] *ERROR* ring sdma0 timeout, signaled seq=283155, emitted seq=283157 [50545.326825] [drm:amdgpu_job_timeout [amdgpu]] *ERROR* Process information: process pid 0 thread pid 0 I've grabbed dmesg, dmesg.0, syslog, syslog.1 and the outputs of journalctl -b-1 and journalctl | grep systemd-sleep in case they are needed, but systemd-analyze blame is failing because apport- autoreport.service is still running for some reason (not that the output of that is captured in my script for this). ** Attachment added: "Error message screenshot" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928600/+attachment/5509158/+files/amdgpu_error.jpg -- 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/1928600 Title: [amdgpu] Gnome locks up with artifacts on screen and [drm:amdgpu_dm_commit_planes [amdgpu]] *ERROR* Waiting for fences timed out! Status in linux package in Ubuntu: Incomplete Bug description: With this hardware configuration this issue has been a problem only when suspending or resuming from suspend under 20.04. Having decided to upgrade through 20.10 to 21.04 to see if things improve enough to help me identify which package to report a bug against things have become significantly worse. With 20.04 it was an occasional occurrence found when returning to the computer. Either it was stuck in the suspend process with a blank screen or one with artefacts on, or it would start the resume and then lock. On the upgrade to 21.04 (I didn't stop on 20.10 for more than enough time to tidy up and upgrade again), the system seemed improved initially - including notably improved boot times (no idea if that is related). After a bit of checking things out I went to enable the PPAs that had been disabled (Teamviewer, Nextcloud, Anydesk and Chrome - all of which have been installed after the problems were initially noted). When the window to authenticate popped up the screen filled with artefacts and I had to reset. After several attempts to reboot into a working desktop variously booting to artefacts, or getting artefacts immediately after logging in (usually when opening and maximising a terminal to capture the logs for later) I managed to change from Wayland to X.Org and logged in successfully with no problems for the rest of the day (including a Jitsi meeting lasting about 4 hours or more). The next day (today) suspend and resume is causing problems as before, boot has slowed down again (again, no idea if this is related). Compared to 20.04 there are more frequent locks (it had reached one every other day, but now it is more frequent - 4 today so far). Key things I have noted: - it is significantly worse under Wayland (to the point of being unusable) - it usually happens during the suspend / resume, but not always - when using the desktop it will always related to moving or resizing a window - leaving the PC powered off for a few minutes helps to get a reliable reboot (as in, if you reboot too quickly you get artefacts immediately after logging in) ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun May 16 19:23:00 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-10-16 (212 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-05-15 (1 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2020-10-16 (214 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: lono wireless extensions. enp34s0 no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7B79 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic root=UUID=2fd8e91e-4658-4060-bc40-5db44750fc91 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 RelatedPackageVersions:
[Kernel-packages] [Bug 1927749] Re: ubuntu_kernel_selftests ftrace fails on arm64 F / aws-5.8 / amd64 F azure-5.8
Fix accepted in mainline. Sent SRU. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1927749 Title: ubuntu_kernel_selftests ftrace fails on arm64 F / aws-5.8 / amd64 F azure-5.8 Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: New Status in linux-aws package in Ubuntu: New Status in linux source package in Focal: New Status in linux-aws source package in Focal: New Status in linux source package in Groovy: New Status in linux-aws source package in Groovy: New Status in linux source package in Hirsute: New Status in linux-aws source package in Hirsute: New Status in linux source package in Impish: New Status in linux-aws source package in Impish: New Bug description: [Impact] arm64 only focal/aws 5.8.0-1031.33~20.04.1-aws and 5.8.0-1032.34~20.04.1-aws - regression. Works fine on previous Focal cycle (5.8.0-1028.30~20.04.3-aws) and current Groovy 5.8. 12. 05/06 07:01:39 DEBUG| utils:0153| [stdout] TAP version 13 13. 05/06 07:01:39 DEBUG| utils:0153| [stdout] 1..1 14. 05/06 07:01:39 DEBUG| utils:0153| [stdout] # selftests: ftrace: ftracetest 15. 05/06 07:01:39 DEBUG| utils:0153| [stdout] # === Ftrace unit tests === 16. 05/06 07:01:39 DEBUG| utils:0153| [stdout] # [1] Basic trace file check [PASS] 17. 05/06 07:01:41 DEBUG| utils:0153| [stdout] # [2] Basic test for tracers [PASS] 18. 05/06 07:01:41 DEBUG| utils:0153| [stdout] # [3] Basic trace clock test [PASS] 19. 05/06 07:01:41 DEBUG| utils:0153| [stdout] # [4] Basic event tracing check [PASS] 20. 05/06 07:01:42 DEBUG| utils:0153| [stdout] # [5] Change the ringbuffer size [PASS] 21. 05/06 07:01:42 DEBUG| utils:0153| [stdout] # [6] Snapshot and tracing setting [PASS] 22. 05/06 07:01:42 DEBUG| utils:0153| [stdout] # [7] trace_pipe and trace_marker [PASS] 23. 05/06 07:01:42 DEBUG| utils:0153| [stdout] # [8] Test ftrace direct functions against tracers [UNRESOLVED] 24. 05/06 07:01:43 DEBUG| utils:0153| [stdout] # [9] Test ftrace direct functions against kprobes [UNRESOLVED] 25. 05/06 07:01:43 DEBUG| utils:0153| [stdout] # [10] Generic dynamic event - add/remove kprobe events [PASS] 26. 05/06 07:01:43 DEBUG| utils:0153| [stdout] # [11] Generic dynamic event - add/remove synthetic events [PASS] 27. 05/06 07:01:44 DEBUG| utils:0153| [stdout] # [12] Generic dynamic event - selective clear (compatibility) [PASS] 28. 05/06 07:01:44 DEBUG| utils:0153| [stdout] # [13] Generic dynamic event - generic clear event [PASS] 29. 05/06 07:01:44 DEBUG| utils:0153| [stdout] # [14] event tracing - enable/disable with event level files [PASS] 30. 05/06 07:01:45 DEBUG| utils:0153| [stdout] # [15] event tracing - restricts events based on pid notrace filtering [FAIL] 31. 05/06 07:01:45 DEBUG| utils:0153| [stdout] # [16] event tracing - restricts events based on pid [PASS] 32. 05/06 07:01:45 DEBUG| utils:0153| [stdout] # [17] event tracing - enable/disable with subsystem level files [PASS] 33. 05/06 07:01:46 DEBUG| utils:0153| [stdout] # [18] event tracing - enable/disable with top level files [PASS] [Test Plan] * Run ftrace test from kernel selftests. [Where problems could occur] * Only kernel selftests should be affected. * ftrace test can have false positives or negatives. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1927749/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1927749] Re: ubuntu_kernel_selftests ftrace fails on arm64 F / aws-5.8 / amd64 F azure-5.8
** Description changed: + [Impact] + arm64 only focal/aws 5.8.0-1031.33~20.04.1-aws and 5.8.0-1032.34~20.04.1-aws - regression. Works fine on previous Focal cycle (5.8.0-1028.30~20.04.3-aws) and current Groovy 5.8. 12. 05/06 07:01:39 DEBUG| utils:0153| [stdout] TAP version 13 13. 05/06 07:01:39 DEBUG| utils:0153| [stdout] 1..1 14. 05/06 07:01:39 DEBUG| utils:0153| [stdout] # selftests: ftrace: ftracetest 15. 05/06 07:01:39 DEBUG| utils:0153| [stdout] # === Ftrace unit tests === 16. 05/06 07:01:39 DEBUG| utils:0153| [stdout] # [1] Basic trace file check [PASS] 17. 05/06 07:01:41 DEBUG| utils:0153| [stdout] # [2] Basic test for tracers [PASS] 18. 05/06 07:01:41 DEBUG| utils:0153| [stdout] # [3] Basic trace clock test [PASS] 19. 05/06 07:01:41 DEBUG| utils:0153| [stdout] # [4] Basic event tracing check [PASS] 20. 05/06 07:01:42 DEBUG| utils:0153| [stdout] # [5] Change the ringbuffer size [PASS] 21. 05/06 07:01:42 DEBUG| utils:0153| [stdout] # [6] Snapshot and tracing setting [PASS] 22. 05/06 07:01:42 DEBUG| utils:0153| [stdout] # [7] trace_pipe and trace_marker [PASS] 23. 05/06 07:01:42 DEBUG| utils:0153| [stdout] # [8] Test ftrace direct functions against tracers [UNRESOLVED] 24. 05/06 07:01:43 DEBUG| utils:0153| [stdout] # [9] Test ftrace direct functions against kprobes [UNRESOLVED] 25. 05/06 07:01:43 DEBUG| utils:0153| [stdout] # [10] Generic dynamic event - add/remove kprobe events [PASS] 26. 05/06 07:01:43 DEBUG| utils:0153| [stdout] # [11] Generic dynamic event - add/remove synthetic events [PASS] 27. 05/06 07:01:44 DEBUG| utils:0153| [stdout] # [12] Generic dynamic event - selective clear (compatibility) [PASS] 28. 05/06 07:01:44 DEBUG| utils:0153| [stdout] # [13] Generic dynamic event - generic clear event [PASS] 29. 05/06 07:01:44 DEBUG| utils:0153| [stdout] # [14] event tracing - enable/disable with event level files [PASS] 30. 05/06 07:01:45 DEBUG| utils:0153| [stdout] # [15] event tracing - restricts events based on pid notrace filtering [FAIL] 31. 05/06 07:01:45 DEBUG| utils:0153| [stdout] # [16] event tracing - restricts events based on pid [PASS] 32. 05/06 07:01:45 DEBUG| utils:0153| [stdout] # [17] event tracing - enable/disable with subsystem level files [PASS] 33. 05/06 07:01:46 DEBUG| utils:0153| [stdout] # [18] event tracing - enable/disable with top level files [PASS] + + [Test Plan] + + * Run ftrace test from kernel selftests. + + [Where problems could occur] + + * Only kernel selftests should be affected. + * ftrace test can have false positives or negatives. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1927749 Title: ubuntu_kernel_selftests ftrace fails on arm64 F / aws-5.8 / amd64 F azure-5.8 Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: New Status in linux-aws package in Ubuntu: New Status in linux source package in Focal: New Status in linux-aws source package in Focal: New Status in linux source package in Groovy: New Status in linux-aws source package in Groovy: New Status in linux source package in Hirsute: New Status in linux-aws source package in Hirsute: New Status in linux source package in Impish: New Status in linux-aws source package in Impish: New Bug description: [Impact] arm64 only focal/aws 5.8.0-1031.33~20.04.1-aws and 5.8.0-1032.34~20.04.1-aws - regression. Works fine on previous Focal cycle (5.8.0-1028.30~20.04.3-aws) and current Groovy 5.8. 12. 05/06 07:01:39 DEBUG| utils:0153| [stdout] TAP version 13 13. 05/06 07:01:39 DEBUG| utils:0153| [stdout] 1..1 14. 05/06 07:01:39 DEBUG| utils:0153| [stdout] # selftests: ftrace: ftracetest 15. 05/06 07:01:39 DEBUG| utils:0153| [stdout] # === Ftrace unit tests === 16. 05/06 07:01:39 DEBUG| utils:0153| [stdout] # [1] Basic trace file check [PASS] 17. 05/06 07:01:41 DEBUG| utils:0153| [stdout] # [2] Basic test for tracers [PASS] 18. 05/06 07:01:41 DEBUG| utils:0153| [stdout] # [3] Basic trace clock test [PASS] 19. 05/06 07:01:41 DEBUG| utils:0153| [stdout] # [4] Basic event tracing check [PASS] 20. 05/06 07:01:42 DEBUG| utils:0153| [stdout] # [5] Change the ringbuffer size [PASS] 21. 05/06 07:01:42 DEBUG| utils:0153| [stdout] # [6] Snapshot and tracing setting [PASS] 22. 05/06 07:01:42 DEBUG| utils:0153| [stdout] # [7] trace_pipe and trace_marker [PASS] 23. 05/06 07:01:42 DEBUG| utils:0153| [stdout] # [8] Test ftrace direct functions against tracers [UNRESOLVED] 24. 05/06 07:01:43 DEBUG| utils:0153| [stdout] # [9] Test ftrace direct functions against kprobes [UNRESOLVED] 25. 05/06 07:01:43 DEBUG| utils:0153| [stdout] # [10] Generic dynamic event - add/remove kprobe events [PASS] 26. 05/06 07:01:43 DEBUG| utils:0153| [stdout] # [11] Generic dynamic
[Kernel-packages] [Bug 1932168] Re: oss4/4.2-build2010-5ubuntu6~20.04.2 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1
** Changed in: linux-hwe-5.11 (Ubuntu) Status: New => Invalid ** Changed in: linux-hwe-5.11 (Ubuntu Focal) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1932168 Title: oss4/4.2-build2010-5ubuntu6~20.04.2 ADT test failure with linux- hwe-5.11/5.11.0-20.21~20.04.1 Status in linux-hwe-5.11 package in Ubuntu: Invalid Status in oss4 package in Ubuntu: Invalid Status in linux-hwe-5.11 source package in Focal: Invalid Status in oss4 source package in Focal: Fix Committed Bug description: [Impact] oss4 dkms will fail to build on 5.11 kernels on focal, preventing users from using those modules on more recent kernels. [Test case] Install the package and make sure it builds. [Fix] Conditionally define a function that is not used on the Linux port when LICENSED_VERSION is undefined. [Fix risk] Licensed versions will fail to build, but we don't do those. Other ports should not fail as we only patch the Linux port. [Potential regression] The dkms package may still fail to build, install or load. Or sound might not work on systems that depend on oss4. --- This is a scripted bug report about ADT failures while running oss4 tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/o/oss4/20210611_210018_1dcc5@/log.gz [Other] NB! dkms ftbfs fixes must be built in security, such that after SRU process in -proposed & -updates it can be copied into -security pocket too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1932168/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934499] Re: New BPF helpers to query conntrack and to generate/validate SYN cookies
** Description changed: Ticket for the patch series that adds new BPF helpers to query conntrack and to generate SYN cookies for forwarded connections. * Explain the bug(s) This patch series aims to accelerate iptables synproxy module with XDP. The stage that generates and checks SYN cookies is stateless and can be implemented in XDP. * Brief explanation of fixes - This patch series adds new BPF helpers: + The series first cherry picked multiple upstream patches from xdp/bpf to support + the new BPF helpers. + + Then it adds new BPF helpers on top of those upstream patches. * bpf_ct_lookup_tcp to lookup CT status of a TCP connection. * bpf_tcp_raw_gen_syncookie to generate SYN cookies without a listening socket on the same host (to be used with iptables synproxy module). * bpf_tcp_raw_check_syncookie to check SYN cookies generated by the previos helper (to be used with iptables synproxy module). * bpf_tcp_raw_gen_tscookie to generate timestamp cookies, which encode additional information like SACK permission, ECN support, window scale. The format is compatible with iptables synproxy module. These new helpers allow to accelerate the iptables synproxy module. This series also includes some dependency patches backported from upstream. * How to test Use an XDP application that generates and checks SYN cookies, leveraging the new helpers. * What it could break. Nothing should be broken, only new functionality is added, and some - patches are backported from upstream. CONFIG_NF_CONNTRACK is changed - from m to y, which is also not expected to break existing functionality. + patches are backported from upstream. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1934499 Title: New BPF helpers to query conntrack and to generate/validate SYN cookies Status in linux-bluefield package in Ubuntu: New Bug description: Ticket for the patch series that adds new BPF helpers to query conntrack and to generate SYN cookies for forwarded connections. * Explain the bug(s) This patch series aims to accelerate iptables synproxy module with XDP. The stage that generates and checks SYN cookies is stateless and can be implemented in XDP. * Brief explanation of fixes The series first cherry picked multiple upstream patches from xdp/bpf to support the new BPF helpers. Then it adds new BPF helpers on top of those upstream patches. * bpf_ct_lookup_tcp to lookup CT status of a TCP connection. * bpf_tcp_raw_gen_syncookie to generate SYN cookies without a listening socket on the same host (to be used with iptables synproxy module). * bpf_tcp_raw_check_syncookie to check SYN cookies generated by the previos helper (to be used with iptables synproxy module). * bpf_tcp_raw_gen_tscookie to generate timestamp cookies, which encode additional information like SACK permission, ECN support, window scale. The format is compatible with iptables synproxy module. These new helpers allow to accelerate the iptables synproxy module. This series also includes some dependency patches backported from upstream. * How to test Use an XDP application that generates and checks SYN cookies, leveraging the new helpers. * What it could break. Nothing should be broken, only new functionality is added, and some patches are backported from upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1934499/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932162] Re: dm-writeboost/2.2.9-1ubuntu1.2 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1
*** This bug is a duplicate of bug 1932257 *** https://bugs.launchpad.net/bugs/1932257 ** This bug has been marked a duplicate of bug 1932257 dm-writeboost dkms: build failure with linux-hwe-5.11 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1932162 Title: dm-writeboost/2.2.9-1ubuntu1.2 ADT test failure with linux- hwe-5.11/5.11.0-20.21~20.04.1 Status in dm-writeboost package in Ubuntu: New Status in linux-hwe-5.11 package in Ubuntu: New Status in dm-writeboost source package in Focal: Confirmed Status in linux-hwe-5.11 source package in Focal: New Bug description: This is a scripted bug report about ADT failures while running dm- writeboost tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/d/dm-writeboost/20210611_205906_3bedf@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/arm64/d/dm-writeboost/20210612_122210_05325@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/d/dm-writeboost/20210611_210008_1bb6f@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/d/dm-writeboost/20210611_205846_7b434@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dm-writeboost/+bug/1932162/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932582] Re: Implement support for Intel SGX
** Tags added: verification-done-hirsute ** Tags added: verification-done -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1932582 Title: Implement support for Intel SGX Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-5.11 package in Ubuntu: Invalid Status in linux-base package in Ubuntu: Fix Released Status in linux source package in Focal: Invalid Status in linux-azure source package in Focal: Invalid Status in linux-azure-5.11 source package in Focal: Fix Committed Status in linux-base source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Released Status in linux-azure source package in Hirsute: Fix Released Status in linux-azure-5.11 source package in Hirsute: Invalid Status in linux-base source package in Hirsute: Fix Committed Status in linux source package in Impish: Fix Released Status in linux-azure source package in Impish: Fix Released Status in linux-azure-5.11 source package in Impish: Invalid Status in linux-base source package in Impish: Fix Released Bug description: [Impact] Backport Linux kernel 5.11 SGX native support to new Azure Ubuntu 20.04 releases. [Fix] Update linux-base to add a UDEV rule to set group permissions on the SGX device. Add an environment variable to default to out-of-proc attestation. [Test] Install focal:linux-azure-5.11 or hirsute:linux-azure. Install linux-base-sgx reboot systemctl --user show-environment | grep SGX_AESM_ADDR systemctl --system show-environment | grep SGX_AESM_ADDR login via tty and check $ env | grep SGX_AESM_ADDR login via ssh and check $ env | grep SGX_AESM_ADDR [other info] SF:00308240 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1932582/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932582] Re: Implement support for Intel SGX
1) Booted hirsute VM, installed linux-azure (v5.11) based kernel, which installed linux-base-sgx as a dependency, and rebooted $ dpkg-query -W linux-base-sgx linux-base-sgx 4.5ubuntu5.2 rebooted and no sgx variables were present. 2) installed linux-base-sgx from proposed ubuntu@cloudimg:~$ dpkg-query -W linux-base-sgx linux-base-sgx 4.5ubuntu5.3 And rebooted Logged in via ttyS0 Last login: Mon Jul 5 14:08:10 UTC 2021 on ttyS0 ubuntu@cloudimg:~$ env | grep SGX SGX_AESM_ADDR=1 ubuntu@cloudimg:~$ systemctl --user show-environment | grep SGX SGX_AESM_ADDR=1 ubuntu@cloudimg:~$ systemctl --system show-environment | grep SGX SGX_AESM_ADDR=1 ubuntu@cloudimg:~$ ssh ubuntu@localhost The authenticity of host 'localhost (127.0.0.1)' can't be established. ECDSA key fingerprint is SHA256:LrAhr9h2R3VjerwIMLnzTl9QmzmAvu9J47/SYyiXgIo. Are you sure you want to continue connecting (yes/no/[fingerprint])? yes Warning: Permanently added 'localhost' (ECDSA) to the list of known hosts. ubuntu@localhost's password: Welcome to Ubuntu 21.04 (GNU/Linux 5.11.0-1009-azure x86_64) .. 36 updates can be applied immediately. To see these additional updates run: apt list --upgradable Last login: Mon Jul 5 14:15:34 2021 ubuntu@cloudimg:~$ env | grep SGX SGX_AESM_ADDR=1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1932582 Title: Implement support for Intel SGX Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-5.11 package in Ubuntu: Invalid Status in linux-base package in Ubuntu: Fix Released Status in linux source package in Focal: Invalid Status in linux-azure source package in Focal: Invalid Status in linux-azure-5.11 source package in Focal: Fix Committed Status in linux-base source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Released Status in linux-azure source package in Hirsute: Fix Released Status in linux-azure-5.11 source package in Hirsute: Invalid Status in linux-base source package in Hirsute: Fix Committed Status in linux source package in Impish: Fix Released Status in linux-azure source package in Impish: Fix Released Status in linux-azure-5.11 source package in Impish: Invalid Status in linux-base source package in Impish: Fix Released Bug description: [Impact] Backport Linux kernel 5.11 SGX native support to new Azure Ubuntu 20.04 releases. [Fix] Update linux-base to add a UDEV rule to set group permissions on the SGX device. Add an environment variable to default to out-of-proc attestation. [Test] Install focal:linux-azure-5.11 or hirsute:linux-azure. Install linux-base-sgx reboot systemctl --user show-environment | grep SGX_AESM_ADDR systemctl --system show-environment | grep SGX_AESM_ADDR login via tty and check $ env | grep SGX_AESM_ADDR login via ssh and check $ env | grep SGX_AESM_ADDR [other info] SF:00308240 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1932582/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934489] Re: Make Intel GPUs choose YCbCr420 encoding automatically when required for 4k 60Hz output
Patchset ported, tested, and sent to kernel-team mailing list ** Description changed: SRU Justification: Impact: On some setups, while the monitor and the GPU support display modes with pixel clocks of up to 600MHz, the connector might not. This prevents RGB encoding for 4k60Hz, but YCbCr420 encoding might still be possible. However, which color mode is used is decided before the pixel clock capabilities are checked, causing the check to fail and discarding 4k60Hz from the list of possible display modes. Fix: This patch fixes the problem by retrying to find a display mode with YCbCr420 enforced and using it, if it is valid. It's very similar to a patch submitted to amdgpu which fixed the same problem. Testcase: - Find a PC with a current Intel iGPU, but only a hdmi 1.4 output. Connect a 4k@60Hz display supporting YCbCr420 encoding to the hdmi port. Without the patch the maximum that can be set via xrandr is 3840 × 2160 30Hz. With the Patch 3840 × 2160 60Hz can be selected which will use YCbCr420 automatically. + I personally tested on a Clevo NV40MB, but generally: Find a PC with a current Intel iGPU, but only a HDMI 1.4 output. Connect a 4k@60Hz display supporting YCbCr420 encoding to the HDMI port. Without the patch the maximum that can be set via xrandr is 3840 × 2160 30Hz. With the Patch 3840 × 2160 60Hz can be selected which will use YCbCr420 automatically. - Prerequistie: + Prerequisite (included in this email patchset as 1/4): https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3c4442aa22878091f16c8d9592f5f5b6a94d1556 Patchset already got accepted upstream and reached the torvalds tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=eacba74d4d561ea6487d944417526e1b025cbebd https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=84d95f77f4aea3f22a486cd04777afd4ab0f0ea5 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=388b863509f76f6a5ecedd7ffdaf184aa813241e and needs only a minor modifications to apply to ubuntu-focal/hwe-5.8 Commit-hashes: 3c4442aa22878091f16c8d9592f5f5b6a94d1556 eacba74d4d561ea6487d944417526e1b025cbebd 84d95f77f4aea3f22a486cd04777afd4ab0f0ea5 388b863509f76f6a5ecedd7ffdaf184aa813241e -- 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/1934489 Title: Make Intel GPUs choose YCbCr420 encoding automatically when required for 4k 60Hz output Status in linux package in Ubuntu: New Bug description: SRU Justification: Impact: On some setups, while the monitor and the GPU support display modes with pixel clocks of up to 600MHz, the connector might not. This prevents RGB encoding for 4k60Hz, but YCbCr420 encoding might still be possible. However, which color mode is used is decided before the pixel clock capabilities are checked, causing the check to fail and discarding 4k60Hz from the list of possible display modes. Fix: This patch fixes the problem by retrying to find a display mode with YCbCr420 enforced and using it, if it is valid. It's very similar to a patch submitted to amdgpu which fixed the same problem. Testcase: I personally tested on a Clevo NV40MB, but generally: Find a PC with a current Intel iGPU, but only a HDMI 1.4 output. Connect a 4k@60Hz display supporting YCbCr420 encoding to the HDMI port. Without the patch the maximum that can be set via xrandr is 3840 × 2160 30Hz. With the Patch 3840 × 2160 60Hz can be selected which will use YCbCr420 automatically. Prerequisite (included in this email patchset as 1/4): https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3c4442aa22878091f16c8d9592f5f5b6a94d1556 Patchset already got accepted upstream and reached the torvalds tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=eacba74d4d561ea6487d944417526e1b025cbebd https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=84d95f77f4aea3f22a486cd04777afd4ab0f0ea5 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=388b863509f76f6a5ecedd7ffdaf184aa813241e and needs only a minor modifications to apply to ubuntu-focal/hwe-5.8 Commit-hashes: 3c4442aa22878091f16c8d9592f5f5b6a94d1556 eacba74d4d561ea6487d944417526e1b025cbebd 84d95f77f4aea3f22a486cd04777afd4ab0f0ea5 388b863509f76f6a5ecedd7ffdaf184aa813241e To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934489/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878670] Re: Reproduceable i915 gpu hang Intel Iris Plus Graphics (Ice Lake 8x8 GT2)
** Changed in: linux-oem-osp1 (Ubuntu) Status: Confirmed => Invalid ** Changed in: mesa (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu) Status: Triaged => Invalid ** Changed in: oem-priority Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-osp1 in Ubuntu. https://bugs.launchpad.net/bugs/1878670 Title: Reproduceable i915 gpu hang Intel Iris Plus Graphics (Ice Lake 8x8 GT2) Status in OEM Priority Project: Invalid Status in linux package in Ubuntu: Invalid Status in linux-oem-osp1 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Bug description: The system freezes frequently then logs out. If happens at apparently random times, and using no particular app. Extract of syslog is attached. Requested info is below: 1) release Ubuntu 18.04.2 LTS (beaver-osp1-melisa X30) 2) package version gnome-session: Installeret: (ingen) Kandidat:3.28.1-0ubuntu3 Versionstabel: 3.28.1-0ubuntu3 500 500 http://dk.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages 3.28.1-0ubuntu2 500 500 http://dk.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 3) Gnome shouldn't crash 4) Gnome crashed To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1878670/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835660] Re: initramfs unpacking failed
@superm1 yes I have, it is now pulled into v5.14 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2c484419efc09e7234c667aa72698cb79ba8d8ed I will request it to be included in linux-stable series. Note that in Impish we have now switched to zstd compression for the initramfs, as it has even better bootspeed performance. -- 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 failed Status in OEM Priority Project: New Status in grub2 package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Released Status in grub2 source package in Focal: Invalid Status in initramfs-tools source package in Focal: Invalid Status in linux source package in Focal: Fix Released Status in grub2 source package in Groovy: Invalid Status in initramfs-tools source package in Groovy: Invalid Status in linux source package in Groovy: Fix Released Status in grub2 source package in Hirsute: Invalid Status in initramfs-tools source package in Hirsute: Invalid Status in linux source package in Hirsute: Fix Released Bug description: "initramfs unpacking failed: Decoding failed", message appears on boot up. If I "update-initramfs" using gzip instead of lz, then boot up passes without decoding failed message. --- However, we currently believe that the decoding error reported in dmesg is actually harmless and has no impact on usability on the system. Switching from lz4 to gzip compression, simply papers over the warning, without any benefits, and slows down boot. Kernel should be fixed to correctly parse lz4 compressed initrds, or at least lower the warning, to not be user visible as an error. [Impact] * Decoding failure messages in dmsg with a single lz4 initrd * Multiple lz4 compressed initrds cannot be decompressed by kernel, when loaded by grub * Multiple lz4 compressed initrds cannot be decompressed by kernel, when there is padding between them [Test Case] * Create empty padding with $ dd if=/dev/zero of=pad4 bs=1 count=4 * Create an lz4 compressed initrd with a single test-file in it with some content. I.e. echo "second-initrd" > test-file, and then pack that with cpio hewc owned by root & lz4 -l. * Create a combined padded initrd of stock initrd, pad4, and the test-marker initrd created above. * Boot above with "break=top" kernel command line. * With broken kernels, there should be dmesg error message that decoding failed, and one will observe that /test-file does not exist in the shell. * With fixed kernel, /test-file in the initrd shell should exist, and should have the expected content "second-initrd". * The alignment and padding in the above test case depends on the size of the first initrd => if a given padded initrd does not reproduce the problem, try varying the size of the first initrd or that of the padding between 0..4. [Where problems could occur] * This changes compatible lz4 decompressor in the kernel, which can also be used by other kernel modules such as cryptography, squashfs, zram, f2fs, comprssed kernel image, pstore. For example, previously rejected files with "bogus" length and extra padding may now be accepted, whereas they were previously getting rejected by the decompressor. * Ideally kernel should switch to the stable lz4 format which has better specification of end of stream. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1835660/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932582] Re: Implement support for Intel SGX
1) Booted focal VM, installed linux-azure-edge (v5.11) based kernel, which installed linux-base-sgx as a dependency from -updates $ dpkg-query -W linux-base-sgx linux-base-sgx 4.5ubuntu3.5 No SGX variables present in env 2) Enabled proposed, and installed linux-base-sgx from proposed $ dpkg-query -W linux-base-sgx linux-base-sgx 4.5ubuntu3.6 Logged in via ttyS0: ubuntu@cloudimg:~$ env | grep SGX SGX_AESM_ADDR=1 ubuntu@cloudimg:~$ systemctl --user show-environment | grep SGX SGX_AESM_ADDR=1 ubuntu@cloudimg:~$ systemctl --system show-environment | grep SGX SGX_AESM_ADDR=1 Logged in via ssh ubuntu@cloudimg:~$ ssh ubuntu@192.168.122.37 ubuntu@192.168.122.37's password: Welcome to Ubuntu 20.04.2 LTS (GNU/Linux 5.11.0-1007-azure x86_64) ... Last login: Mon Jul 5 13:38:22 2021 from 192.168.122.1 ubuntu@cloudimg:~$ env | grep SGX SGX_AESM_ADDR=1 ** Tags added: verification-done-focal -- 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/1932582 Title: Implement support for Intel SGX Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-5.11 package in Ubuntu: Invalid Status in linux-base package in Ubuntu: Fix Released Status in linux source package in Focal: Invalid Status in linux-azure source package in Focal: Invalid Status in linux-azure-5.11 source package in Focal: Fix Committed Status in linux-base source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Released Status in linux-azure source package in Hirsute: Fix Released Status in linux-azure-5.11 source package in Hirsute: Invalid Status in linux-base source package in Hirsute: Fix Committed Status in linux source package in Impish: Fix Released Status in linux-azure source package in Impish: Fix Released Status in linux-azure-5.11 source package in Impish: Invalid Status in linux-base source package in Impish: Fix Released Bug description: [Impact] Backport Linux kernel 5.11 SGX native support to new Azure Ubuntu 20.04 releases. [Fix] Update linux-base to add a UDEV rule to set group permissions on the SGX device. Add an environment variable to default to out-of-proc attestation. [Test] Install focal:linux-azure-5.11 or hirsute:linux-azure. Install linux-base-sgx reboot systemctl --user show-environment | grep SGX_AESM_ADDR systemctl --system show-environment | grep SGX_AESM_ADDR login via tty and check $ env | grep SGX_AESM_ADDR login via ssh and check $ env | grep SGX_AESM_ADDR [other info] SF:00308240 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1932582/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932582] Re: Implement support for Intel SGX
@ubuntu-sru-bot Regresssions were retried, and have now been cleared. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1932582 Title: Implement support for Intel SGX Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-5.11 package in Ubuntu: Invalid Status in linux-base package in Ubuntu: Fix Released Status in linux source package in Focal: Invalid Status in linux-azure source package in Focal: Invalid Status in linux-azure-5.11 source package in Focal: Fix Committed Status in linux-base source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Released Status in linux-azure source package in Hirsute: Fix Released Status in linux-azure-5.11 source package in Hirsute: Invalid Status in linux-base source package in Hirsute: Fix Committed Status in linux source package in Impish: Fix Released Status in linux-azure source package in Impish: Fix Released Status in linux-azure-5.11 source package in Impish: Invalid Status in linux-base source package in Impish: Fix Released Bug description: [Impact] Backport Linux kernel 5.11 SGX native support to new Azure Ubuntu 20.04 releases. [Fix] Update linux-base to add a UDEV rule to set group permissions on the SGX device. Add an environment variable to default to out-of-proc attestation. [Test] Install focal:linux-azure-5.11 or hirsute:linux-azure. Install linux-base-sgx reboot systemctl --user show-environment | grep SGX_AESM_ADDR systemctl --system show-environment | grep SGX_AESM_ADDR login via tty and check $ env | grep SGX_AESM_ADDR login via ssh and check $ env | grep SGX_AESM_ADDR [other info] SF:00308240 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1932582/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930279] Re: [Ivy Bridge] flashing sliced triangles on screen
groovy is soon EOL, please upgrade to 21.04 and let us know if this is fixed there ** Changed in: mesa (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/1930279 Title: [Ivy Bridge] flashing sliced triangles on screen Status in linux package in Ubuntu: New Status in mesa package in Ubuntu: Incomplete Bug description: when i did upgrade my ubuntu from 20.04 to 20.10 i have small winking triangles on my screen, they sometimes will appear when i watching a youtube video they will appear on the video's seek bar or when i typing they will appear on selected texts,but the main and most annoying state of it happens when I am playing minecraft,my entire game screen has these little triangles ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-53.60-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 31 18:05:33 2021 DistUpgraded: 2021-05-27 14:18:07,483 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: groovy DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.4.0-73-generic, x86_64: installed virtualbox, 6.1.16, 5.8.0-53-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [1043:844d] InstallationDate: Installed on 2020-01-10 (507 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-53-generic root=UUID=a5a5279f-cdf5-4129-94fa-8f17f7401833 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to groovy on 2021-05-27 (4 days ago) dmi.bios.date: 03/19/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1204 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H61-M LX R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1204:bd03/19/2014:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MLXR2.0:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930279/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877762] Re: 1360x768 Vega graphics display staggered
so this is a kernel bug impish will soon get 5.13, but you also have the option of installing oem-5.13 from focal-proposed (apt install linux-oem-20.04c) ** Package changed: mesa (Ubuntu) => linux (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/1877762 Title: 1360x768 Vega graphics display staggered Status in Ubuntu MATE: New Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: This was the go-to resolution pre-update. All of the other modes seem to work. Release 20.04 LTS (Focal Fossa) 64-bit Kernel Linux 5.4.0-29-generic x86_64 MATE 1.24.0 Processor: AMD Ryzen 3 2200G with Radeon Vega Graphics × 4 Graphics: AMD RAVEN (DRM 3.35.0, 5.4.0-29-generic, LLVM 9.0.1) lspci output: 38:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] (rev c8) As you can see from the attached image, the display shifts to the right every few lines. Still working on installing the full amdgpu package (libffs 6 required, 7 installed so I'm working on the bits). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1877762/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877762] [NEW] 1360x768 Vega graphics display staggered
You have been subscribed to a public bug: This was the go-to resolution pre-update. All of the other modes seem to work. Release 20.04 LTS (Focal Fossa) 64-bit Kernel Linux 5.4.0-29-generic x86_64 MATE 1.24.0 Processor: AMD Ryzen 3 2200G with Radeon Vega Graphics × 4 Graphics: AMD RAVEN (DRM 3.35.0, 5.4.0-29-generic, LLVM 9.0.1) lspci output: 38:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] (rev c8) As you can see from the attached image, the display shifts to the right every few lines. Still working on installing the full amdgpu package (libffs 6 required, 7 installed so I'm working on the bits). ** Affects: ubuntu-mate Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: xserver-xorg-video-amdgpu (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amdgpu focal -- 1360x768 Vega graphics display staggered https://bugs.launchpad.net/bugs/1877762 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934660] Re: intel_pmc_core driver is not probed on ADL
PPA: https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1934660 . A local prebuilt works for me. Going to SRU. -- 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/1934660 Title: intel_pmc_core driver is not probed on ADL Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.13 source package in Focal: Incomplete Bug description: [Summary] intel_pmc_core driver is not probed [Reproduce Steps] 1. $ ls /sys/bus/platform/drivers/intel_pmc_core 2. No INT33A1:00 device under the directory [Results] Expected: INT33A1:00 device is shown in the intel_pmc_core directory Actual: No device probed by intel_pmc_core successfully To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1934660/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874464] Re: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out
Forgot to mention this problem also exists in hirsute with 5.11.0-7620-generic. -- 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/1874464 Title: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Incomplete Status in linux source package in Groovy: Confirmed Bug description: Running focal on a desktop, I accidentally clicked "Enable networking" in nm-applet, disabling my networking. When I clicked it again to reenable it, my networking did not return. After unsuccessfully poking at it for a while, I rebooted and saw the below (and still no networking). `rmmod r8169; modprobe r8169` had no (apparent) effect, nor did further reboots. I rebooted onto two different kernels, both exhibited the same behaviour: 5.4.0-21-generic, 5.4.0-26-generic. I was finally only able to restore networking by _rebooting into Windows_ and then rebooting back into Ubuntu. (My supposition is that NetworkManager/the kernel set *waves hands* something on the network card that persists across boots when it was disabled, and that wasn't correctly unset when I reenabled networking (or on following boots), but Windows _does_ correctly handle that case on boot, and reset it to a working state.) Apr 23 10:07:43 surprise kernel: [ cut here ] Apr 23 10:07:43 surprise kernel: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out Apr 23 10:07:43 surprise kernel: WARNING: CPU: 9 PID: 0 at net/sched/sch_generic.c:447 dev_watchdog+0x258/0x260 Apr 23 10:07:43 surprise kernel: Modules linked in: zfs(PO) zunicode(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) zlua(PO) xt_comment dummy xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_> Apr 23 10:07:43 surprise kernel: autofs4 btrfs xor zstd_compress raid6_pq libcrc32c dm_crypt hid_microsoft ff_memless hid_logitech_hidpp hid_logitech_dj hid_generic usbhid hid nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) crct10dif_pclmul crc32_pclmul ghash_clmulni_intel drm_km> Apr 23 10:07:43 surprise kernel: CPU: 9 PID: 0 Comm: swapper/9 Tainted: P OE 5.4.0-26-generic #30-Ubuntu Apr 23 10:07:43 surprise kernel: Hardware name: Gigabyte Technology Co., Ltd. B450M DS3H/B450M DS3H-CF, BIOS F4 01/25/2019 Apr 23 10:07:43 surprise kernel: RIP: 0010:dev_watchdog+0x258/0x260 Apr 23 10:07:43 surprise kernel: Code: 85 c0 75 e5 eb 9f 4c 89 ff c6 05 bf 06 e8 00 01 e8 6d bb fa ff 44 89 e9 4c 89 fe 48 c7 c7 50 6d a3 b4 48 89 c2 e8 83 3f 71 ff <0f> 0b eb 80 0f 1f 40 00 0f 1f 44 00 00 55 48 89 e5 41 57 49 89 d7 Apr 23 10:07:43 surprise kernel: RSP: 0018:a90d40378e30 EFLAGS: 00010286 Apr 23 10:07:43 surprise kernel: RAX: RBX: 8a7578b00400 RCX: Apr 23 10:07:43 surprise kernel: RDX: 8a758ee67740 RSI: 8a758ee578c8 RDI: 0300 Apr 23 10:07:43 surprise kernel: RBP: a90d40378e60 R08: 8a758ee578c8 R09: 0004 Apr 23 10:07:43 surprise kernel: R10: R11: 0001 R12: 0001 Apr 23 10:07:43 surprise kernel: R13: R14: 8a758cadc480 R15: 8a758cadc000 Apr 23 10:07:43 surprise kernel: FS: () GS:8a758ee4() knlGS: Apr 23 10:07:43 surprise kernel: CS: 0010 DS: ES: CR0: 80050033 Apr 23 10:07:43 surprise kernel: CR2: 7f4d2000d5eb CR3: 0003fcfe2000 CR4: 003406e0 Apr 23 10:07:43 surprise kernel: Call Trace: Apr 23 10:07:43 surprise kernel: Apr 23 10:07:43 surprise kernel: ? pfifo_fast_enqueue+0x150/0x150 Apr 23 10:07:43 surprise kernel: call_timer_fn+0x32/0x130 Apr 23 10:07:43 surprise kernel: __run_timers.part.0+0x180/0x280 Apr 23 10:07:43 surprise kernel: ? tick_sched_handle+0x33/0x60 Apr 23 10:07:43 surprise kernel: ? tick_sched_timer+0x3d/0x80 Apr 23 10:07:43 surprise kernel: ? ktime_get+0x3e/0xa0 Apr 23 10:07:43 surprise kernel: run_timer_softirq+0x2a/0x50 Apr 23 10:07:43 surprise kernel: __do_softirq+0xe1/0x2d6 Apr 23 10:07:43 surprise kernel: ? hrtimer_interrupt+0x13b/0x220 Apr 23 10:07:43 surprise kernel: irq_exit+0xae/0xb0 Apr 23 10:07:43 surprise kernel: smp_apic_timer_interrupt+0x7b/0x140 Apr 23 10:07:43 surprise kernel: apic_timer_interrupt+0xf/0x20 Apr 23 10:07:43 surprise kernel: Apr 23 10:07:43 surprise kernel: RIP: 0010:cpuidle_enter_state+0xc5/0x450 Apr 23 10:07:43 surprise kernel: Code: ff e8 df 0d 81 ff 80 7d c7 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 65 03 00 00 31 ff e8 32 7a 87 ff fb 66 0f 1f 44 00 00 <45> 85 ed 0f 88 8f 02 00 00 49 63 cd 4c 8b 7d d0 4c 2b 7d c8 48 8d Apr 23 10:07:43 surprise kernel: RSP:
[Kernel-packages] [Bug 1874464] Re: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out
I just want to share a quick observation related to this bug. I've noticed that when there is a kernel update and doing a soft-reboot, this problem shows up. When this occurs, I do a soft-shutdown and power up and the problem is resolved. -- 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/1874464 Title: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Incomplete Status in linux source package in Groovy: Confirmed Bug description: Running focal on a desktop, I accidentally clicked "Enable networking" in nm-applet, disabling my networking. When I clicked it again to reenable it, my networking did not return. After unsuccessfully poking at it for a while, I rebooted and saw the below (and still no networking). `rmmod r8169; modprobe r8169` had no (apparent) effect, nor did further reboots. I rebooted onto two different kernels, both exhibited the same behaviour: 5.4.0-21-generic, 5.4.0-26-generic. I was finally only able to restore networking by _rebooting into Windows_ and then rebooting back into Ubuntu. (My supposition is that NetworkManager/the kernel set *waves hands* something on the network card that persists across boots when it was disabled, and that wasn't correctly unset when I reenabled networking (or on following boots), but Windows _does_ correctly handle that case on boot, and reset it to a working state.) Apr 23 10:07:43 surprise kernel: [ cut here ] Apr 23 10:07:43 surprise kernel: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out Apr 23 10:07:43 surprise kernel: WARNING: CPU: 9 PID: 0 at net/sched/sch_generic.c:447 dev_watchdog+0x258/0x260 Apr 23 10:07:43 surprise kernel: Modules linked in: zfs(PO) zunicode(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) zlua(PO) xt_comment dummy xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_> Apr 23 10:07:43 surprise kernel: autofs4 btrfs xor zstd_compress raid6_pq libcrc32c dm_crypt hid_microsoft ff_memless hid_logitech_hidpp hid_logitech_dj hid_generic usbhid hid nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) crct10dif_pclmul crc32_pclmul ghash_clmulni_intel drm_km> Apr 23 10:07:43 surprise kernel: CPU: 9 PID: 0 Comm: swapper/9 Tainted: P OE 5.4.0-26-generic #30-Ubuntu Apr 23 10:07:43 surprise kernel: Hardware name: Gigabyte Technology Co., Ltd. B450M DS3H/B450M DS3H-CF, BIOS F4 01/25/2019 Apr 23 10:07:43 surprise kernel: RIP: 0010:dev_watchdog+0x258/0x260 Apr 23 10:07:43 surprise kernel: Code: 85 c0 75 e5 eb 9f 4c 89 ff c6 05 bf 06 e8 00 01 e8 6d bb fa ff 44 89 e9 4c 89 fe 48 c7 c7 50 6d a3 b4 48 89 c2 e8 83 3f 71 ff <0f> 0b eb 80 0f 1f 40 00 0f 1f 44 00 00 55 48 89 e5 41 57 49 89 d7 Apr 23 10:07:43 surprise kernel: RSP: 0018:a90d40378e30 EFLAGS: 00010286 Apr 23 10:07:43 surprise kernel: RAX: RBX: 8a7578b00400 RCX: Apr 23 10:07:43 surprise kernel: RDX: 8a758ee67740 RSI: 8a758ee578c8 RDI: 0300 Apr 23 10:07:43 surprise kernel: RBP: a90d40378e60 R08: 8a758ee578c8 R09: 0004 Apr 23 10:07:43 surprise kernel: R10: R11: 0001 R12: 0001 Apr 23 10:07:43 surprise kernel: R13: R14: 8a758cadc480 R15: 8a758cadc000 Apr 23 10:07:43 surprise kernel: FS: () GS:8a758ee4() knlGS: Apr 23 10:07:43 surprise kernel: CS: 0010 DS: ES: CR0: 80050033 Apr 23 10:07:43 surprise kernel: CR2: 7f4d2000d5eb CR3: 0003fcfe2000 CR4: 003406e0 Apr 23 10:07:43 surprise kernel: Call Trace: Apr 23 10:07:43 surprise kernel: Apr 23 10:07:43 surprise kernel: ? pfifo_fast_enqueue+0x150/0x150 Apr 23 10:07:43 surprise kernel: call_timer_fn+0x32/0x130 Apr 23 10:07:43 surprise kernel: __run_timers.part.0+0x180/0x280 Apr 23 10:07:43 surprise kernel: ? tick_sched_handle+0x33/0x60 Apr 23 10:07:43 surprise kernel: ? tick_sched_timer+0x3d/0x80 Apr 23 10:07:43 surprise kernel: ? ktime_get+0x3e/0xa0 Apr 23 10:07:43 surprise kernel: run_timer_softirq+0x2a/0x50 Apr 23 10:07:43 surprise kernel: __do_softirq+0xe1/0x2d6 Apr 23 10:07:43 surprise kernel: ? hrtimer_interrupt+0x13b/0x220 Apr 23 10:07:43 surprise kernel: irq_exit+0xae/0xb0 Apr 23 10:07:43 surprise kernel: smp_apic_timer_interrupt+0x7b/0x140 Apr 23 10:07:43 surprise kernel: apic_timer_interrupt+0xf/0x20 Apr 23 10:07:43 surprise kernel: Apr 23 10:07:43 surprise kernel: RIP: 0010:cpuidle_enter_state+0xc5/0x450 Apr 23 10:07:43 surprise kernel: Code: ff e8 df 0d 81 ff 80 7d c7 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 65 03 00 00 31 ff e8
[Kernel-packages] [Bug 1933508] Re: mute/micmute LEDs no function on HP EliteBook x360 830 G8
you were meant to test oem-5.10, 5.4 does not and will not have it.. ** Tags removed: verification-failed-focal ** Tags added: verification-needed-focal -- 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/1933508 Title: mute/micmute LEDs no function on HP EliteBook x360 830 G8 Status in OEM Priority Project: Triaged Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux source package in Hirsute: In Progress Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: [Impact] The mic mute/audio mute LEDS are not work on HP EliteBook x360 830 G8 [Fix] It needs the specific quirk for the hardware layout. Thus, add the quirks to make it works. [Test] After applying the quirk, the audio/mic mute LEDs are working good. [Where problems could occur] If HP ships the different system boards design with the same subsystem ID of audio codec which is using different GPIO pins (different layout), then the quirk will not work (LEDs will not work when muting audio-output or microphone). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1933508/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934660] Re: intel_pmc_core driver is not probed on ADL
Proposed patch: https://patchwork.kernel.org/project/platform- driver-x86/patch/8080c997627d2a1fd8a701e8d8d09c69c8df381d.1625191274.git.gayatri.kamm...@intel.com/ -- 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/1934660 Title: intel_pmc_core driver is not probed on ADL Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.13 source package in Focal: Incomplete Bug description: [Summary] intel_pmc_core driver is not probed [Reproduce Steps] 1. $ ls /sys/bus/platform/drivers/intel_pmc_core 2. No INT33A1:00 device under the directory [Results] Expected: INT33A1:00 device is shown in the intel_pmc_core directory Actual: No device probed by intel_pmc_core successfully To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1934660/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1929646] Re: [SRU][OEM-5.10/H] Fix typec output on AMD Cezanne GPU
** Changed in: hwe-next Status: New => 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/1929646 Title: [SRU][OEM-5.10/H] Fix typec output on AMD Cezanne GPU Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Released Bug description: SRU justification: [Impact] Display can't work when replug in after suspend on AMD Cezanne platform. [Fix] Enable display power gating, display of typec will work as expected. [Test] Verified on hardware, suspend then replug the cable of typec, repeat for 10 times, all good. [Where problems could occur] The AMD typec output may not output. Unstable kernel already got it, only for OEM-5.10/H. Minor changes during backport. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1929646/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934660] [NEW] intel_pmc_core driver is not probed on ADL
Public bug reported: [Summary] intel_pmc_core driver is not probed [Reproduce Steps] 1. $ ls /sys/bus/platform/drivers/intel_pmc_core 2. No INT33A1:00 device under the directory [Results] Expected: INT33A1:00 device is shown in the intel_pmc_core directory Actual: No device probed by intel_pmc_core successfully ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: High Assignee: You-Sheng Yang (vicamo) Status: Incomplete ** Affects: linux-oem-5.13 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: Won't Fix ** Affects: linux-oem-5.13 (Ubuntu Focal) Importance: High Assignee: You-Sheng Yang (vicamo) Status: Incomplete ** Tags: ihv-intel oem-priority originate-from-1923031 somerville ** Also affects: linux-oem-5.13 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => Won't Fix ** Changed in: linux-oem-5.13 (Ubuntu) Status: New => Invalid ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: linux-oem-5.13 (Ubuntu Focal) Status: New => Incomplete ** Changed in: linux-oem-5.13 (Ubuntu Focal) Importance: Undecided => High ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Changed in: linux-oem-5.13 (Ubuntu Focal) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Tags added: oem-priority originate-from-1923031 somerville -- 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/1934660 Title: intel_pmc_core driver is not probed on ADL Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.13 source package in Focal: Incomplete Bug description: [Summary] intel_pmc_core driver is not probed [Reproduce Steps] 1. $ ls /sys/bus/platform/drivers/intel_pmc_core 2. No INT33A1:00 device under the directory [Results] Expected: INT33A1:00 device is shown in the intel_pmc_core directory Actual: No device probed by intel_pmc_core successfully To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1934660/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874464] Re: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out
That's why mainline r8169 disables ASPM completely. Users still have the option to re-enable individual ASPM states per sysfs, but that's at own risk. It's not known why and which combinations of board chipset / BIOS / NIC chipset version have an issue when ASPM L1 is enabled. All three components may contribute, unfortunately Realtek doesn't release errata information. -- 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/1874464 Title: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Incomplete Status in linux source package in Groovy: Confirmed Bug description: Running focal on a desktop, I accidentally clicked "Enable networking" in nm-applet, disabling my networking. When I clicked it again to reenable it, my networking did not return. After unsuccessfully poking at it for a while, I rebooted and saw the below (and still no networking). `rmmod r8169; modprobe r8169` had no (apparent) effect, nor did further reboots. I rebooted onto two different kernels, both exhibited the same behaviour: 5.4.0-21-generic, 5.4.0-26-generic. I was finally only able to restore networking by _rebooting into Windows_ and then rebooting back into Ubuntu. (My supposition is that NetworkManager/the kernel set *waves hands* something on the network card that persists across boots when it was disabled, and that wasn't correctly unset when I reenabled networking (or on following boots), but Windows _does_ correctly handle that case on boot, and reset it to a working state.) Apr 23 10:07:43 surprise kernel: [ cut here ] Apr 23 10:07:43 surprise kernel: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out Apr 23 10:07:43 surprise kernel: WARNING: CPU: 9 PID: 0 at net/sched/sch_generic.c:447 dev_watchdog+0x258/0x260 Apr 23 10:07:43 surprise kernel: Modules linked in: zfs(PO) zunicode(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) zlua(PO) xt_comment dummy xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_> Apr 23 10:07:43 surprise kernel: autofs4 btrfs xor zstd_compress raid6_pq libcrc32c dm_crypt hid_microsoft ff_memless hid_logitech_hidpp hid_logitech_dj hid_generic usbhid hid nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) crct10dif_pclmul crc32_pclmul ghash_clmulni_intel drm_km> Apr 23 10:07:43 surprise kernel: CPU: 9 PID: 0 Comm: swapper/9 Tainted: P OE 5.4.0-26-generic #30-Ubuntu Apr 23 10:07:43 surprise kernel: Hardware name: Gigabyte Technology Co., Ltd. B450M DS3H/B450M DS3H-CF, BIOS F4 01/25/2019 Apr 23 10:07:43 surprise kernel: RIP: 0010:dev_watchdog+0x258/0x260 Apr 23 10:07:43 surprise kernel: Code: 85 c0 75 e5 eb 9f 4c 89 ff c6 05 bf 06 e8 00 01 e8 6d bb fa ff 44 89 e9 4c 89 fe 48 c7 c7 50 6d a3 b4 48 89 c2 e8 83 3f 71 ff <0f> 0b eb 80 0f 1f 40 00 0f 1f 44 00 00 55 48 89 e5 41 57 49 89 d7 Apr 23 10:07:43 surprise kernel: RSP: 0018:a90d40378e30 EFLAGS: 00010286 Apr 23 10:07:43 surprise kernel: RAX: RBX: 8a7578b00400 RCX: Apr 23 10:07:43 surprise kernel: RDX: 8a758ee67740 RSI: 8a758ee578c8 RDI: 0300 Apr 23 10:07:43 surprise kernel: RBP: a90d40378e60 R08: 8a758ee578c8 R09: 0004 Apr 23 10:07:43 surprise kernel: R10: R11: 0001 R12: 0001 Apr 23 10:07:43 surprise kernel: R13: R14: 8a758cadc480 R15: 8a758cadc000 Apr 23 10:07:43 surprise kernel: FS: () GS:8a758ee4() knlGS: Apr 23 10:07:43 surprise kernel: CS: 0010 DS: ES: CR0: 80050033 Apr 23 10:07:43 surprise kernel: CR2: 7f4d2000d5eb CR3: 0003fcfe2000 CR4: 003406e0 Apr 23 10:07:43 surprise kernel: Call Trace: Apr 23 10:07:43 surprise kernel: Apr 23 10:07:43 surprise kernel: ? pfifo_fast_enqueue+0x150/0x150 Apr 23 10:07:43 surprise kernel: call_timer_fn+0x32/0x130 Apr 23 10:07:43 surprise kernel: __run_timers.part.0+0x180/0x280 Apr 23 10:07:43 surprise kernel: ? tick_sched_handle+0x33/0x60 Apr 23 10:07:43 surprise kernel: ? tick_sched_timer+0x3d/0x80 Apr 23 10:07:43 surprise kernel: ? ktime_get+0x3e/0xa0 Apr 23 10:07:43 surprise kernel: run_timer_softirq+0x2a/0x50 Apr 23 10:07:43 surprise kernel: __do_softirq+0xe1/0x2d6 Apr 23 10:07:43 surprise kernel: ? hrtimer_interrupt+0x13b/0x220 Apr 23 10:07:43 surprise kernel: irq_exit+0xae/0xb0 Apr 23 10:07:43 surprise kernel: smp_apic_timer_interrupt+0x7b/0x140 Apr 23 10:07:43 surprise kernel: apic_timer_interrupt+0xf/0x20 Apr 23 10:07:43 surprise kernel: Apr 23 10:07:43 surprise kernel: RIP: 0010:cpuidle_enter_state+0xc5/0x450
[Kernel-packages] [Bug 1934187] Re: lxd exec fails
I tested LXD and lxc for #1934187.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-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/1934187
Title:
lxd exec fails
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Focal:
Fix Committed
Bug description:
[Impact]
lxd will not work, as lxc exec is not able to set the apparmor confinement
and bails out executing inside the container.
[Fix]
Revert upstream commit bfb819ea20ce8bbeeba17e1a6418bf8bda91fc28 ("proc: Check
/proc/$pid/attr/ writes against file opener").
[Test case]
lxd basic usage test suite was run.
On a 4.15 kernel, the whole lxd autopkgtest was run.
[Potential regression]
Unprivileged use of PID attributes may be permitted when they shouldn't.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934187/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934099] Re: 4.15.0-149-generic: lxc-attach lsm/lsm.c: lsm_process_label_set_at: 174 Operation not permitted - Failed to set AppArmor label "lxc-container-default-cgns"
*** This bug is a duplicate of bug 1934187 *** https://bugs.launchpad.net/bugs/1934187 Tester on 4.15.0-150 lxc-create -n bidule -t ubuntu […] lxc-start -n bidule -d lxc-attach -n bidule root@bidule:~# Thanks. ** Tags added: verification-done-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/1934099 Title: 4.15.0-149-generic: lxc-attach lsm/lsm.c: lsm_process_label_set_at: 174 Operation not permitted - Failed to set AppArmor label "lxc- container-default-cgns" Status in linux package in Ubuntu: New Bug description: Hello. When testing with the bionic-proposed repository, we found that the 4.15.0-149-generic break the lxc-attach command with the following error: lxc-attach: bidule: lsm/lsm.c: lsm_process_label_set_at: 174 Operation not permitted - Failed to set AppArmor label "lxc-container- default-cgns" We don't have this issue with the current 4.15.0-147. There is no issue using the --elevated-privileges option of lxc- attach. I join the debug log of “lxc-attach -n bidule -l debug”. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-149-generic 4.15.0-149.153 ProcVersionSignature: Ubuntu 4.15.0-149.153-generic 4.15.18 Uname: Linux 4.15.0-149-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 juin 30 10:15 seq crw-rw 1 root audio 116, 33 juin 30 10:15 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.24 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Wed Jun 30 10:21:54 2021 HibernationDevice: RESUME=/dev/mapper/bionic--vg-swap_1 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-149-generic root=/dev/mapper/hostname--vg-root ro console=tty1 RelatedPackageVersions: linux-restricted-modules-4.15.0-149-generic N/A linux-backports-modules-4.15.0-149-generic N/A linux-firmware 1.173.20 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.12.0-1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-3.1 dmi.modalias: dmi:bvnSeaBIOS:bvr1.12.0-1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-3.1:cvnQEMU:ct1:cvrpc-i440fx-3.1: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-3.1 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934099/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931301] Re: NIC unavailable after suspend to RAM
It might be caused by the patch https://github.com/torvalds/linux/commit/a4dcfbc4ee2218abd567d81d795082d8d4afcdf6 which is the only difference between 20.10 and 21.04 kernel. I build a test hirsute kernel in https://people.canonical.com/~mschiu77/lp1931301/v1/, could you install and check if the problem still persists? Please also provide me the full dmesg log based on this kernel. Thanks. -- 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/1931301 Title: NIC unavailable after suspend to RAM Status in linux package in Ubuntu: Confirmed Bug description: Upgraded to 21.04 (hirsute) and now the network card is unavailable after suspend to RAM (sleep state S3). It worked flawlessly up until 20.10. My workaround for now is unloading and reloading the kernel module, but that won't work for normal users, hence this report. NIC in its unavailable state: 2: enp4s0: mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether d0:50:99:27:02:11 brd ff:ff:ff:ff:ff:ff NIC (from lspci): 04:00.0 Ethernet controller: Qualcomm Atheros Killer E220x Gigabit Ethernet Controller (rev 10) Trying to ifconfig it down/up results in: SIOCSIFFLAGS: No such device journalctl shows (right after recovering from suspend): NetworkManager[1911]: [1623181236.9371] manager: sleep: wake requested (sleeping: yes enabled: yes) NetworkManager[1911]: [1623181236.9372] device (enp4s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') NetworkManager[1911]: [1623181236.9382] manager: NetworkManager state is now CONNECTED_LOCAL ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: network-manager 1.30.0-1ubuntu3 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Jun 8 21:59:15 2021 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-08-25 (1748 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RfKill: SourcePackage: network-manager UpgradeStatus: Upgraded to hirsute on 2021-06-04 (4 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.30.0 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931301/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932367] Re: Pixel format change broken for Elgato Cam Link 4K
focal-proposed has linux 5.4.0-79.88, but this version does not include the patch yet. -- 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/1932367 Title: Pixel format change broken for Elgato Cam Link 4K Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: Triaged Bug description: [Impact] The Elgato Cam Link 4K HDMI video capture card reports to support three different pixel formats, where the first format depends on the connected HDMI device. ``` $ v4l2-ctl -d /dev/video0 --list-formats-ext ioctl: VIDIOC_ENUM_FMT Type: Video Capture [0]: 'NV12' (Y/CbCr 4:2:0) Size: Discrete 3840x2160 Interval: Discrete 0.033s (29.970 fps) [1]: 'NV12' (Y/CbCr 4:2:0) Size: Discrete 3840x2160 Interval: Discrete 0.033s (29.970 fps) [2]: 'YU12' (Planar YUV 4:2:0) Size: Discrete 3840x2160 Interval: Discrete 0.033s (29.970 fps) ``` Changing the pixel format to anything besides the first pixel format does not work: ``` $ v4l2-ctl -d /dev/video0 --try-fmt-video pixelformat=YU12 Format Video Capture: Width/Height : 3840/2160 Pixel Format : 'NV12' (Y/CbCr 4:2:0) Field : None Bytes per Line: 3840 Size Image: 12441600 Colorspace: sRGB Transfer Function : Rec. 709 YCbCr/HSV Encoding: Rec. 709 Quantization : Default (maps to Limited Range) Flags : ``` User space applications like VLC might show an error message on the terminal in that case: ``` libv4l2: error set_fmt gave us a different result than try_fmt! ``` Depending on the error handling of the user space applications, they might display a distorted video, because they use the wrong pixel format for decoding the stream. [Fix] The Elgato Cam Link 4K responds to the USB video probe VS_PROBE_CONTROL/VS_COMMIT_CONTROL with a malformed data structure: The second byte contains bFormatIndex (instead of being the second byte of bmHint). The first byte is always zero. The third byte is always 1. The firmware bug was reported to Elgato on 2020-12-01 and it was forwarded by the support team to the developers as feature request. There is no firmware update available since then. The latest firmware for Elgato Cam Link 4K as of 2021-03-23 has MCU 20.02.19 and FPGA 67. Therefore correct the malformed data structure for this device. The change was successfully tested with VLC, OBS, and Chromium using different pixel formats (YUYV, NV12, YU12), resolutions (3840x2160, 1920x1080), and frame rates (29.970 and 59.940 fps). [Test Case] Connect an input device to the Cam Link 4K and try all three pixel formats with VLC: vlc v4l2:///dev/video0 --v4l2-chroma=NV12 vlc v4l2:///dev/video0 --v4l2-chroma=YU12 [Other Info] The fix was reviewed and accepted by the subsystem maintainer and will be included upstream: https://git.linuxtv.org/media_stage.git/commit/?id=4c6e0976295add7f0ed94d276c04a3d6f1ea8f83 Attached a backported patch for Ubuntu. I successfully tested it with Linux 5.11 on Ubuntu 21.04 and Linux 5.8 on Ubuntu 20.10. It should work on older kernel versions as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1932367/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934652] [NEW] Graphics Tearing on 5.8 kernel (Intel(R) HD Graphics 2500, Ivy Bridge)
Public bug reported: Intel(R) Core(TM) i5-3470 with Intel(R) HD Graphics 2500 Problems experienced on fresh install of kubuntu or mate 20.04.02 (Automatically) Chosen kernel in these instances is the 5.8 kernel. NO issues with the 5.4 kernel - or the 5.8.0-48 kernel Problem: Operating system graphics (eg kubuntu calendar) and firefox (using webrender) have issues (see attached for example) This bug follows on from #1924624 Description:Ubuntu 20.04.2 LTS Release:20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-59-generic 5.8.0-59.66~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Jul 5 09:49:19 2021 InstallationDate: Installed on 2021-07-05 (0 days ago) InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.8 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "Example of diagonal tears" https://bugs.launchpad.net/bugs/1934652/+attachment/5509118/+files/Screenshot_20210705_095522.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/1934652 Title: Graphics Tearing on 5.8 kernel (Intel(R) HD Graphics 2500, Ivy Bridge) Status in linux-signed-hwe-5.8 package in Ubuntu: New Bug description: Intel(R) Core(TM) i5-3470 with Intel(R) HD Graphics 2500 Problems experienced on fresh install of kubuntu or mate 20.04.02 (Automatically) Chosen kernel in these instances is the 5.8 kernel. NO issues with the 5.4 kernel - or the 5.8.0-48 kernel Problem: Operating system graphics (eg kubuntu calendar) and firefox (using webrender) have issues (see attached for example) This bug follows on from #1924624 Description:Ubuntu 20.04.2 LTS Release:20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-59-generic 5.8.0-59.66~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Jul 5 09:49:19 2021 InstallationDate: Installed on 2021-07-05 (0 days ago) InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1934652/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934187] Re: lxd exec fails
This bug is awaiting verification that the 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-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: verification-needed-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/1934187
Title:
lxd exec fails
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Focal:
Fix Committed
Bug description:
[Impact]
lxd will not work, as lxc exec is not able to set the apparmor confinement
and bails out executing inside the container.
[Fix]
Revert upstream commit bfb819ea20ce8bbeeba17e1a6418bf8bda91fc28 ("proc: Check
/proc/$pid/attr/ writes against file opener").
[Test case]
lxd basic usage test suite was run.
On a 4.15 kernel, the whole lxd autopkgtest was run.
[Potential regression]
Unprivileged use of PID attributes may be permitted when they shouldn't.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934187/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931565] Update Released
The verification of the Stable Release Update for thermald has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1931565 Title: pull in latest thermald bug fixes into thermald Status in thermald package in Ubuntu: In Progress Status in thermald source package in Focal: Fix Committed Status in thermald source package in Hirsute: Fix Released Bug description: == SRU Justification [ HIRSUTE ] == The upstream thermald 2.4.6 has been released with some more bug fixes that are pertinent to H/W available in older releases such as Hirsute. These fix a variety of issues found on H/W in the field and such as over-throttling, handling alternate ACPI object names for B0D4, handling trip zones which may have wrong settings and disabling the legacy rapl cdev when rapl-mmio is available. == The fixes == Pull in these fixes: From 2.4.6: commit 273a53a11da2a7302ad7a5bc7e3bf04f221ce4e2 Author: Srinivas Pandruvada Date: Mon Jun 7 16:47:47 2021 -0700 Use Adaptive PPCC limits for RAPL MMIO Set the correct device name as RAPL-MSR so that RAPL-MMIO can also set the correct default power limits. commit 2dd67300448fa4a2aa8f3e00ee5b604c73a1f7d9 Author: Srinivas Pandruvada Date: Mon Jun 7 16:45:14 2021 -0700 Increase power limit for disabled RAPL-MMIO Increase 100W to 200W as some desktop platform already have limit more than 100W. commit 3de1004a49d0d157573bbdc1097b2fbed056879f Author: Srinivas Pandruvada Date: Sun Jun 6 19:19:15 2021 -0700 Special case for default PSVT When there are no adaptive tables and only one default PSVT table is present with just one entry with MAX type. Add one additional entry as done for non default case. From 2.4.5: commit 301a89284e9d74a9a1f8315c1673a548dcacda8c Author: Srinivas Pandruvada Date: Sat May 29 10:50:44 2021 -0700 Set a very high RAPL MSR PL1 with --adaptive After upgrading Dell Latitude 5420, again noticed performance degradation. The PPCC power limit for MSR RAPL PL1 is reduced to 15W. Even though we disable MSR RAPL with --adaptive option, it is not getting disabled. So MSR RAPL limits still playing role. To fix that set a very high MSR RAPL PL1 limit so that it never causes throttling. All throttling with --adaptive option is done using RAPL-MMIO. From 2.4.4: commit ea4491971059259e46daad10ae850d3d530b02f2 Author: Srinivas Pandruvada Date: Thu Mar 11 10:06:15 2021 -0800 Fix error for condition names The current code caps the max name as the last condition name, which is "Power_Slider". So any condition more than 56 will be printing error, with "Power_Slider" as condition name. For example for condition = 57: Unsupported condition 57 (Power_slider) This is confusing during debug, so print "UNKNOWN" for condition name 56. commit 9115f2fb0b296a22a62908f2718ca873af2a452f Author: Srinivas Pandruvada Date: Tue Mar 9 16:36:13 2021 -0800 This is confusing during debug, so print "UNKNOWN" for condition name 56. commit 9115f2fb0b296a22a62908f2718ca873af2a452f Author: Srinivas Pandruvada Date: Tue Mar 9 16:36:13 2021 -0800 Check for alternate names for B0D4 device B0D4 can be named as TCPU or B0D4. So search for both names if failed to find one. commit 660ee6f1f6351e6c291c0699147231be402c2bb8 Author: Srinivas Pandruvada Date: Tue Mar 9 16:33:08 2021 -0800 Delete all trips from zones before psvt install Initially zones has all the trips from sysfs, which may have wrong settings. Instead of deleting only for matched psvt zones, delete for all zones. In this way only zones which are in PSVT will be present. commit 1ad03424f7f3d339521635f08377b323375b2747 Author: Srinivas Pandruvada Date: Tue Mar 9 11:36:27 2021 -0800 Disable legacy rapl cdev when rapl-mmio is in use Explicitly disable legacy rapl based on MSR interface when rapl-mmio is in use. This will prevent PL1/PL2 power limit from MSR based rapl, which may not be the correct one. commit 45832e16290fec7353513b1ce03533b73b18f0c6 Author: Colin Ian King Date: Thu Mar 18 11:22:38 2021 + Fix spelling mistakes found using codespell There are a handful of spelling mistakes in comments and literal strings found by codespell. Fix these.
[Kernel-packages] [Bug 1931565] Re: pull in latest thermald bug fixes into thermald
This bug was fixed in the package thermald - 2.4.3-1ubuntu1 --- thermald (2.4.3-1ubuntu1) hirsute; urgency=medium * Pull in bug fixes between 2.4.3 and 2.4.6 (LP: #1931565) [Colin Ian King] - Fix spelling mistakes found using codespell [Srinivas Pandruvada] - Disable legacy rapl cdev when rapl-mmio is in use This will prevent PL1/PL2 power limit from MSR based rapl, which may not be the correct one. - Delete all trips from zones before psvt install Initially zones has all the trips from sysfs, which may have wrong settings. Instead of deleting only for matched psvt zones, delete or all zones. In this way only zones which are in PSVT will be present. - Check for alternate names for B0D4 device B0D4 can be named as TCPU or B0D4. So search for both names if failed to find one. - Fix error for condition names The current code caps the max name as the last condition name, which is "Power_Slider". So any condition more than 56 will be printing error, with "Power_Slider" as condition name. For example for condition = 57: Unsupported condition 57 (Power_slider) - Set a very high RAPL MSR PL1 with --adaptive After upgrading Dell Latitude 5420, again noticed performance degradation. The PPCC power limit for MSR RAPL PL1 is reduced to 15W. Even though we disable MSR RAPL with --adaptive option, it is not getting disabled. So MSR RAPL limits still playing role. To fix that set a very high MSR RAPL PL1 limit so that it never causes throttling. All throttling with --adaptive option is done using RAPL-MMIO. - Special case for default PSVT When there are no adaptive tables and only one default PSVT table is present with just one entry with MAX type. Add one additional entry as done for non default case. - Increase power limit for disabled RAPL-MMIO Increase 100W to 200W as some desktop platform already have limit more than 100W. - Use Adaptive PPCC limits for RAPL MMIO Set the correct device name as RAPL-MSR so that RAPL-MMIO can also set the correct default power limits. -- Colin King Thu, 10 Jun 2021 12:52:21 +0100 ** Changed in: thermald (Ubuntu Hirsute) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1931565 Title: pull in latest thermald bug fixes into thermald Status in thermald package in Ubuntu: In Progress Status in thermald source package in Focal: Fix Committed Status in thermald source package in Hirsute: Fix Released Bug description: == SRU Justification [ HIRSUTE ] == The upstream thermald 2.4.6 has been released with some more bug fixes that are pertinent to H/W available in older releases such as Hirsute. These fix a variety of issues found on H/W in the field and such as over-throttling, handling alternate ACPI object names for B0D4, handling trip zones which may have wrong settings and disabling the legacy rapl cdev when rapl-mmio is available. == The fixes == Pull in these fixes: From 2.4.6: commit 273a53a11da2a7302ad7a5bc7e3bf04f221ce4e2 Author: Srinivas Pandruvada Date: Mon Jun 7 16:47:47 2021 -0700 Use Adaptive PPCC limits for RAPL MMIO Set the correct device name as RAPL-MSR so that RAPL-MMIO can also set the correct default power limits. commit 2dd67300448fa4a2aa8f3e00ee5b604c73a1f7d9 Author: Srinivas Pandruvada Date: Mon Jun 7 16:45:14 2021 -0700 Increase power limit for disabled RAPL-MMIO Increase 100W to 200W as some desktop platform already have limit more than 100W. commit 3de1004a49d0d157573bbdc1097b2fbed056879f Author: Srinivas Pandruvada Date: Sun Jun 6 19:19:15 2021 -0700 Special case for default PSVT When there are no adaptive tables and only one default PSVT table is present with just one entry with MAX type. Add one additional entry as done for non default case. From 2.4.5: commit 301a89284e9d74a9a1f8315c1673a548dcacda8c Author: Srinivas Pandruvada Date: Sat May 29 10:50:44 2021 -0700 Set a very high RAPL MSR PL1 with --adaptive After upgrading Dell Latitude 5420, again noticed performance degradation. The PPCC power limit for MSR RAPL PL1 is reduced to 15W. Even though we disable MSR RAPL with --adaptive option, it is not getting disabled. So MSR RAPL limits still playing role. To fix that set a very high MSR RAPL PL1 limit so that it never causes throttling. All throttling with --adaptive option is done using RAPL-MMIO. From 2.4.4: commit ea4491971059259e46daad10ae850d3d530b02f2 Author: Srinivas Pandruvada Date: Thu Mar 11 10:06:15 2021 -0800 Fix error for condition names The current code caps the max name as the last condition
[Kernel-packages] [Bug 1929422] Re: The touchpad doesn't work in my Laptop ThinkBook 15-IML with Ubuntu 20
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-signed-hwe-5.8 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/1929422 Title: The touchpad doesn't work in my Laptop ThinkBook 15-IML with Ubuntu 20 Status in linux-signed-hwe-5.8 package in Ubuntu: Confirmed Bug description: I've executed a "cat /proc/bus/input/devices" and theres is not an entry for my devices. Reading at the wiki.ubuntu.com the suggestion is that the bug is in the kernel ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-53-generic 5.8.0-53.60~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 24 10:27:05 2021 InstallationDate: Installed on 2021-05-20 (3 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1929422/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874464] Re: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out
I could see this issue with same Call trace pasted above with ubuntu 20.04/20.10/21.04. Had a look at relevant kernel code and found all of them disable only ASPM L1.1 rather than ASPM completely.Rebuilt the kernel by disabling whole ASPM feature this NETDEV WATCHDOG call trace disappears. code hacked was like below: pci_disable_link_state(pdev, PCIE_LINK_STATE_L1_1);//issue appears pci_disable_link_state(pdev, PCIE_LINK_STATE_L0S | PCIE_LINK_STATE_L1);//issue disappears I believe the experiment shows there is ASPM issue with r8169 driver.Can anyone share your view on this problem which may shed some light on the way forward.Is there a Realtek contact window we could reach out ot.Thanks for anyone who can help. -- 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/1874464 Title: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Incomplete Status in linux source package in Groovy: Confirmed Bug description: Running focal on a desktop, I accidentally clicked "Enable networking" in nm-applet, disabling my networking. When I clicked it again to reenable it, my networking did not return. After unsuccessfully poking at it for a while, I rebooted and saw the below (and still no networking). `rmmod r8169; modprobe r8169` had no (apparent) effect, nor did further reboots. I rebooted onto two different kernels, both exhibited the same behaviour: 5.4.0-21-generic, 5.4.0-26-generic. I was finally only able to restore networking by _rebooting into Windows_ and then rebooting back into Ubuntu. (My supposition is that NetworkManager/the kernel set *waves hands* something on the network card that persists across boots when it was disabled, and that wasn't correctly unset when I reenabled networking (or on following boots), but Windows _does_ correctly handle that case on boot, and reset it to a working state.) Apr 23 10:07:43 surprise kernel: [ cut here ] Apr 23 10:07:43 surprise kernel: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out Apr 23 10:07:43 surprise kernel: WARNING: CPU: 9 PID: 0 at net/sched/sch_generic.c:447 dev_watchdog+0x258/0x260 Apr 23 10:07:43 surprise kernel: Modules linked in: zfs(PO) zunicode(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) zlua(PO) xt_comment dummy xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_> Apr 23 10:07:43 surprise kernel: autofs4 btrfs xor zstd_compress raid6_pq libcrc32c dm_crypt hid_microsoft ff_memless hid_logitech_hidpp hid_logitech_dj hid_generic usbhid hid nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) crct10dif_pclmul crc32_pclmul ghash_clmulni_intel drm_km> Apr 23 10:07:43 surprise kernel: CPU: 9 PID: 0 Comm: swapper/9 Tainted: P OE 5.4.0-26-generic #30-Ubuntu Apr 23 10:07:43 surprise kernel: Hardware name: Gigabyte Technology Co., Ltd. B450M DS3H/B450M DS3H-CF, BIOS F4 01/25/2019 Apr 23 10:07:43 surprise kernel: RIP: 0010:dev_watchdog+0x258/0x260 Apr 23 10:07:43 surprise kernel: Code: 85 c0 75 e5 eb 9f 4c 89 ff c6 05 bf 06 e8 00 01 e8 6d bb fa ff 44 89 e9 4c 89 fe 48 c7 c7 50 6d a3 b4 48 89 c2 e8 83 3f 71 ff <0f> 0b eb 80 0f 1f 40 00 0f 1f 44 00 00 55 48 89 e5 41 57 49 89 d7 Apr 23 10:07:43 surprise kernel: RSP: 0018:a90d40378e30 EFLAGS: 00010286 Apr 23 10:07:43 surprise kernel: RAX: RBX: 8a7578b00400 RCX: Apr 23 10:07:43 surprise kernel: RDX: 8a758ee67740 RSI: 8a758ee578c8 RDI: 0300 Apr 23 10:07:43 surprise kernel: RBP: a90d40378e60 R08: 8a758ee578c8 R09: 0004 Apr 23 10:07:43 surprise kernel: R10: R11: 0001 R12: 0001 Apr 23 10:07:43 surprise kernel: R13: R14: 8a758cadc480 R15: 8a758cadc000 Apr 23 10:07:43 surprise kernel: FS: () GS:8a758ee4() knlGS: Apr 23 10:07:43 surprise kernel: CS: 0010 DS: ES: CR0: 80050033 Apr 23 10:07:43 surprise kernel: CR2: 7f4d2000d5eb CR3: 0003fcfe2000 CR4: 003406e0 Apr 23 10:07:43 surprise kernel: Call Trace: Apr 23 10:07:43 surprise kernel: Apr 23 10:07:43 surprise kernel: ? pfifo_fast_enqueue+0x150/0x150 Apr 23 10:07:43 surprise kernel: call_timer_fn+0x32/0x130 Apr 23 10:07:43 surprise kernel: __run_timers.part.0+0x180/0x280 Apr 23 10:07:43 surprise kernel: ? tick_sched_handle+0x33/0x60 Apr 23 10:07:43 surprise kernel: ? tick_sched_timer+0x3d/0x80 Apr 23 10:07:43 surprise kernel: ? ktime_get+0x3e/0xa0 Apr 23 10:07:43 surprise kernel: run_timer_softirq+0x2a/0x50 Apr 23 10:07:43 surprise kernel:
[Kernel-packages] [Bug 1931677] Re: [SRU][F/G/H][linux-firmware] add realtek 8852a wifi fimware
This bug was fixed in the package linux-firmware - 1.197.2 --- linux-firmware (1.197.2) hirsute; urgency=medium * Add realtek 8852a wifi fimware (LP: #1931677) - rtw89: 8852a: update fw to v0.13.8.0 -- Seth Forshee Tue, 22 Jun 2021 13:55:53 -0500 ** Changed in: linux-firmware (Ubuntu Hirsute) Status: Fix Committed => 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/bugs/1931677 Title: [SRU][F/G/H][linux-firmware] add realtek 8852a wifi fimware Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: Fix Released Status in linux-firmware source package in Groovy: Fix Released Status in linux-firmware source package in Hirsute: Fix Released Bug description: [Impact] Realtek 8852A wifi can not work without proper firmware. [Fix] Add realtek 8852a wifi firmware for driver. Kernel driver will be in another SRU. [Test] Verified on hardware with wifi ap, connect with 2.4G/5G, all good. [Where problems could occur] It should be low risk for adding fw for specfic hardware chip. Hirsute already got it, only SRU fw for F/G. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1931677/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934557] Re: Backlight (screen brightness) on Lenovo P14s AMD Gen2 inop
Hi Aaron, attaching the edid file. ** Attachment added: "p14s2a.edid" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934557/+attachment/5509079/+files/p14s2a.edid -- 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/1934557 Title: Backlight (screen brightness) on Lenovo P14s AMD Gen2 inop Status in linux package in Ubuntu: New Bug description: Backlight does not change. Neither with the keys, nor with the slider. Values in /sys/class/backlight/amdgpu_bl0/brightness do change. However without effect on the actual brightness of the screen, which seems to be stuck at maximum brightness. Following the instructions from here: https://wiki.ubuntu.com/Kernel/Debugging/Backlight ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-22-generic 5.11.0-22.23 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: simon 1886 F pulseaudio /dev/snd/pcmC2D0p: simon 1886 F...m pulseaudio /dev/snd/controlC1: simon 1886 F pulseaudio /dev/snd/controlC0: simon 1886 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jul 3 09:46:53 2021 InstallationDate: Installed on 2021-07-03 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 21A0CTO1WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-22-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-22-generic N/A linux-backports-modules-5.11.0-22-generic N/A linux-firmware 1.197.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/23/2021 dmi.bios.release: 1.5 dmi.bios.vendor: LENOVO dmi.bios.version: R1MET35W (1.05 ) dmi.board.asset.tag: Not Available dmi.board.name: 21A0CTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.5 dmi.modalias: dmi:bvnLENOVO:bvrR1MET35W(1.05):bd04/23/2021:br1.5:efr1.5:svnLENOVO:pn21A0CTO1WW:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A0CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P14s Gen 2a dmi.product.name: 21A0CTO1WW dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a dmi.product.version: ThinkPad P14s Gen 2a dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934557/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934304] Re: i2c-mlxbf.c: prevent stack overflow in mlxbf_i2c_smbus_start_transaction
** Also affects: linux-bluefield (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-bluefield (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux-bluefield (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-bluefield (Ubuntu Focal) Assignee: (unassigned) => Asmaa Mnebhi (asmaam) ** Changed in: linux-bluefield (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1934304 Title: i2c-mlxbf.c: prevent stack overflow in mlxbf_i2c_smbus_start_transaction Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: In Progress Bug description: SRU Justification: [Impact] There could be stack overflow in mlxbf_i2c_smbus_start_transaction(). memcpy() is called in a loop while 'operation->length' upper bound is not checked and 'data_idx' also increments. More details: The operation length is verified by the caller functions so it cannot exceed I2C_SMBUS_BLOCK_MAX bytes (32 bytes) for each operation that is a part of the write. Data_desc array is 128 bytes in size. So potentially a request which consists of 4 writes, 32 bytes each can trigger an off-by-one or off-by-two overflow, because the first byte of data_desc is used by addr, effectively decreasing the available data_desc buffer size by one. Functions like mlx_smbus_i2c_block_func() that prepare the request also set the length of the first write operation to one and store the command id there, so the target buffer size again decreases data_desc by one, making it two bytes less than expected. [Fix] * Add a check for "operation->length" and data_idx and return error if reached upper bound. [Test Case] * Test the i2c-mlxbf.c driver using IPMB functionality. [Regression Potential] This fix returns a negative value to indicate that a transaction has failed. So it will catch more transactions failures. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1934304/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934414] Re: test_bpf.sh from ubuntu_kernel_selftests.net from linux ADT test failure with linux/4.15.0-149.153
** Also affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Tags added: 4.15 bionic i386 sru-20210621 ubuntu-kernel-selftests -- 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/1934414 Title: test_bpf.sh from ubuntu_kernel_selftests.net from linux ADT test failure with linux/4.15.0-149.153 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Bug description: This is a scripted bug report about ADT failures while running linux tests for linux/4.15.0-149.153 on bionic. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: i386: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/i386/l/linux/20210702_010055_445cd@/log.gz 03:37:02 DEBUG| [stdout] selftests: test_bpf.sh 03:37:02 DEBUG| [stdout] 03:37:03 ERROR| [stderr] Segmentation fault 03:37:03 DEBUG| [stdout] test_bpf: [FAIL] 03:37:03 DEBUG| [stdout] not ok 1..8 selftests: test_bpf.sh [FAIL] 03:37:03 DEBUG| [stdout] selftests: netdevice.sh 03:37:03 DEBUG| [stdout] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1934414/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1933730] Re: package nvidia-dkms-460 460.80-0ubuntu0.20.04.2 failed to install/upgrade: installed nvidia-dkms-460 package post-installation script subprocess returned error exit
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-460 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1933730 Title: package nvidia-dkms-460 460.80-0ubuntu0.20.04.2 failed to install/upgrade: installed nvidia-dkms-460 package post-installation script subprocess returned error exit status 10 Status in nvidia-graphics-drivers-460 package in Ubuntu: Confirmed Bug description: package nvidia-dkms-460 460.80-0ubuntu0.20.04.2 failed to install/upgrade: installed nvidia-dkms-460 package post-installation script subprocess returned error exit status 10 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-dkms-460 460.80-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Jun 26 18:07:56 2021 ErrorMessage: installed nvidia-dkms-460 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2021-04-06 (80 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.5 SourcePackage: nvidia-graphics-drivers-460 Title: package nvidia-dkms-460 460.80-0ubuntu0.20.04.2 failed to install/upgrade: installed nvidia-dkms-460 package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1933730/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1929444] Re: SD card initialization on insertion fails
** Changed in: linux (Ubuntu Impish)
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/1929444
Title:
SD card initialization on insertion fails
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Hirsute:
Fix Committed
Status in linux source package in Impish:
Fix Released
Bug description:
[SRU Justification]
[Impact]
The memory card can be detected and mount correctly when the system starts
with the card inserted. But it will fail to be detected at the subsequent
re-plug. It only happens on particular Realtek older PCI interfaced card
readers. The RTL8411B (10ec:5287) is reported problematic for this issue.
[Fix]
Found the commit 121e9c6b5c4c ("misc: rtsx: modify and fix init_hw function")
in 5.11.0-rc1 introduces this regression. The fix from upstream use the old
ASPM control for particular realtek card reader models: 8411 5209 5227 5229
5249 5250.
[Test]
Verified on the Realtek PCI interfaced card reader RTL8411B and verify
whether the memory card can be detected for each re-plug.
[Where problem could occur]
The regression can be considered as low since the fix has specified separate
ASPM control for particular Realtek Card Readers.
== Original Bug Description ==
If I boot my laptop with an SD card (actually SDXC) in the MMC slot
the system sees it and I can mount and use it.
If I then unmount it, remove it then re-insert it I get this in the
system ,og:
[ 194.673108] mmc0: card e624 removed
[ 205.462065] mmc0: cannot verify signal voltage switch
[ 205.567479] mmc0: error -84 whilst initialising SD card
and the card cannot then be used.
It was OK in groovy. It's failing in hirsute.
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: linux-image-generic 5.11.0.17.18
ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
Uname: Linux 5.11.0-17-generic x86_64
ApportVersion: 2.20.11-0ubuntu65
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: gml44104153 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Mon May 24 17:36:49 2021
HibernationDevice: RESUME=UUID=03dec042-8ba2-48a8-8d19-373ca2e0829c
InstallationDate: Installed on 2020-08-13 (284 days ago)
InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64
(20200731)
MachineType: PC Specialist LTD N150CU
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic
root=UUID=b21720c3-60bf-4298-9d73-743672f89216 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-5.11.0-17-generic N/A
linux-backports-modules-5.11.0-17-generic N/A
linux-firmware 1.197
SourcePackage: linux
UpgradeStatus: Upgraded to hirsute on 2021-05-13 (11 days ago)
dmi.bios.date: 11/15/2019
dmi.bios.release: 7.7
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 1.07.07TPCS2
dmi.board.asset.tag: Tag 12345
dmi.board.name: N151CU
dmi.board.vendor: CLEVO
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.ec.firmware.release: 7.7
dmi.modalias:
dmi:bvnINSYDECorp.:bvr1.07.07TPCS2:bd11/15/2019:br7.7:efr7.7:svnPCSpecialistLTD:pnN150CU:pvrNotApplicable:rvnCLEVO:rnN151CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
dmi.product.family: Not Applicable
dmi.product.name: N150CU
dmi.product.sku: Not Applicable
dmi.product.version: Not Applicable
dmi.sys.vendor: PC Specialist LTD
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1929444/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931677] Re: [SRU][F/G/H][linux-firmware] add realtek 8852a wifi fimware
For Hirsute, Test kernel 5.10-oem-1032 with these patches(https://lore.kernel.org/linux-wireless/ac6c9122cb04498793bee926c2b7e...@realtek.com/T/#t). Update firmware to 1.197.2. the WIFI works correctly. ** Tags removed: verification-needed-hirsute ** Tags added: verification-done-hirsute -- 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/1931677 Title: [SRU][F/G/H][linux-firmware] add realtek 8852a wifi fimware Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: Fix Released Status in linux-firmware source package in Groovy: Fix Released Status in linux-firmware source package in Hirsute: Fix Committed Bug description: [Impact] Realtek 8852A wifi can not work without proper firmware. [Fix] Add realtek 8852a wifi firmware for driver. Kernel driver will be in another SRU. [Test] Verified on hardware with wifi ap, connect with 2.4G/5G, all good. [Where problems could occur] It should be low risk for adding fw for specfic hardware chip. Hirsute already got it, only SRU fw for F/G. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1931677/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
