[Bug 1961483] [NEW] New upstream release 2022.02.18
Public bug reported: [Impact] New upstream release. This is a database of wireless regulations, and should updated in all releases to ensure users have the most up-to-date regulatory information. [Test Case] Following reboot after installing the new database, it should be possible to query and change the regulatory domain using 'iw reg get' and 'iw reg set'. [Where problems could occur] If crda or the kernel is unable to use the new database, users may be stuck using the default "world" regulatory domain which is quite restrictive, therefore they may be unable to use wireless channels that they were able to use previously. Regulatory rules may have also changed for the user's region, which could also make some channels unusable, but this would not be a bug. ** Affects: wireless-regdb (Ubuntu) Importance: Medium Assignee: Seth Forshee (sforshee) Status: In Progress ** Affects: wireless-regdb (Ubuntu Bionic) Importance: Medium Assignee: Seth Forshee (sforshee) Status: In Progress ** Affects: wireless-regdb (Ubuntu Focal) Importance: Medium Assignee: Seth Forshee (sforshee) Status: In Progress ** Affects: wireless-regdb (Ubuntu Impish) Importance: Medium Assignee: Seth Forshee (sforshee) Status: In Progress ** Affects: wireless-regdb (Ubuntu Jammy) Importance: Medium Assignee: Seth Forshee (sforshee) Status: In Progress ** Also affects: wireless-regdb (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: wireless-regdb (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: wireless-regdb (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: wireless-regdb (Ubuntu Jammy) Importance: Medium Assignee: Seth Forshee (sforshee) Status: In Progress ** Changed in: wireless-regdb (Ubuntu Impish) Status: New => In Progress ** Changed in: wireless-regdb (Ubuntu Impish) Importance: Undecided => Medium ** Changed in: wireless-regdb (Ubuntu Impish) Assignee: (unassigned) => Seth Forshee (sforshee) ** Changed in: wireless-regdb (Ubuntu Focal) Status: New => In Progress ** Changed in: wireless-regdb (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: wireless-regdb (Ubuntu Focal) Assignee: (unassigned) => Seth Forshee (sforshee) ** Changed in: wireless-regdb (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: wireless-regdb (Ubuntu Bionic) Assignee: (unassigned) => Seth Forshee (sforshee) ** Changed in: wireless-regdb (Ubuntu Bionic) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961483 Title: New upstream release 2022.02.18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wireless-regdb/+bug/1961483/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928393] Re: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault"
** Changed in: linux-firmware (Ubuntu) Assignee: Seth Forshee (sforshee) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928393 Title: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault" To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1928393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1941955] Re: New upstream release 2021.08.28
$ dpkg-query -W wireless-regdb wireless-regdb 2021.08.28-0ubuntu1~18.04.1 $ iw reg get global country 00: DFS-UNSET (2402 - 2472 @ 40), (6, 20), (N/A) (2457 - 2482 @ 20), (6, 20), (N/A), AUTO-BW, PASSIVE-SCAN (2474 - 2494 @ 20), (6, 20), (N/A), NO-OFDM, PASSIVE-SCAN (5170 - 5250 @ 80), (6, 20), (N/A), AUTO-BW, PASSIVE-SCAN (5250 - 5330 @ 80), (6, 20), (0 ms), DFS, AUTO-BW, PASSIVE-SCAN (5490 - 5730 @ 160), (6, 20), (0 ms), DFS, PASSIVE-SCAN (5735 - 5835 @ 80), (6, 20), (N/A), PASSIVE-SCAN (57240 - 63720 @ 2160), (N/A, 0), (N/A) $ sudo iw reg set US $ iw reg get global country US: DFS-FCC (2400 - 2472 @ 40), (N/A, 30), (N/A) (5150 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW (5250 - 5350 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW (5470 - 5730 @ 160), (N/A, 23), (0 ms), DFS (5730 - 5850 @ 80), (N/A, 30), (N/A), AUTO-BW (5850 - 5895 @ 40), (N/A, 27), (N/A), NO-OUTDOOR, AUTO-BW, PASSIVE-SCAN (57240 - 71000 @ 2160), (N/A, 40), (N/A) ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1941955 Title: New upstream release 2021.08.28 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wireless-regdb/+bug/1941955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1941955] Re: New upstream release 2021.08.28
$ dpkg-query -W wireless-regdb wireless-regdb 2021.08.28-0ubuntu1~20.04.1 $ iw reg get global country 00: DFS-UNSET (2402 - 2472 @ 40), (6, 20), (N/A) (2457 - 2482 @ 20), (6, 20), (N/A), AUTO-BW, PASSIVE-SCAN (2474 - 2494 @ 20), (6, 20), (N/A), NO-OFDM, PASSIVE-SCAN (5170 - 5250 @ 80), (6, 20), (N/A), AUTO-BW, PASSIVE-SCAN (5250 - 5330 @ 80), (6, 20), (0 ms), DFS, AUTO-BW, PASSIVE-SCAN (5490 - 5730 @ 160), (6, 20), (0 ms), DFS, PASSIVE-SCAN (5735 - 5835 @ 80), (6, 20), (N/A), PASSIVE-SCAN (57240 - 63720 @ 2160), (N/A, 0), (N/A) $ sudo iw reg set US $ iw reg get global country US: DFS-FCC (2400 - 2472 @ 40), (N/A, 30), (N/A) (5150 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW (5250 - 5350 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW (5470 - 5730 @ 160), (N/A, 23), (0 ms), DFS (5730 - 5850 @ 80), (N/A, 30), (N/A), AUTO-BW (5850 - 5895 @ 40), (N/A, 27), (N/A), NO-OUTDOOR, AUTO-BW, PASSIVE-SCAN (57240 - 71000 @ 2160), (N/A, 40), (N/A) ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1941955 Title: New upstream release 2021.08.28 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wireless-regdb/+bug/1941955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1941955] Re: New upstream release 2021.08.28
$ dpkg-query -W wireless-regdb wireless-regdb 2021.08.28-0ubuntu1~21.04.1 $ iw reg get global country 00: DFS-UNSET (2402 - 2472 @ 40), (6, 20), (N/A) (2457 - 2482 @ 20), (6, 20), (N/A), AUTO-BW, PASSIVE-SCAN (2474 - 2494 @ 20), (6, 20), (N/A), NO-OFDM, PASSIVE-SCAN (5170 - 5250 @ 80), (6, 20), (N/A), AUTO-BW, PASSIVE-SCAN (5250 - 5330 @ 80), (6, 20), (0 ms), DFS, AUTO-BW, PASSIVE-SCAN (5490 - 5730 @ 160), (6, 20), (0 ms), DFS, PASSIVE-SCAN (5735 - 5835 @ 80), (6, 20), (N/A), PASSIVE-SCAN (57240 - 63720 @ 2160), (N/A, 0), (N/A) $ sudo iw reg set US $ iw reg get global country US: DFS-FCC (2400 - 2472 @ 40), (N/A, 30), (N/A) (5150 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW (5250 - 5350 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW (5470 - 5730 @ 160), (N/A, 23), (0 ms), DFS (5730 - 5850 @ 80), (N/A, 30), (N/A), AUTO-BW (5850 - 5895 @ 40), (N/A, 27), (N/A), NO-OUTDOOR, AUTO-BW, PASSIVE-SCAN (57240 - 71000 @ 2160), (N/A, 40), (N/A) ** Tags removed: verification-needed-hirsute ** Tags added: verification-done-hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1941955 Title: New upstream release 2021.08.28 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wireless-regdb/+bug/1941955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1941955] Re: New upstream release 2021.08.28
New packages in https://launchpad.net/~sforshee/+archive/ubuntu/wireless-regdb. ** Changed in: wireless-regdb (Ubuntu Hirsute) Status: Confirmed => In Progress ** Changed in: wireless-regdb (Ubuntu Focal) Status: Confirmed => In Progress ** Changed in: wireless-regdb (Ubuntu Bionic) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1941955 Title: New upstream release 2021.08.28 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wireless-regdb/+bug/1941955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1941955] [NEW] New upstream release 2021.08.28
Public bug reported: [Impact] New upstream release. This is a database of wireless regulations, and should updated in all releases to ensure users have the most up-to-date regulatory information. [Test Case] Following reboot after installing the new database, it should be possible to query and change the regulatory domain using 'iw reg get' and 'iw reg set'. [Where problems could occur] If crda or the kernel is unable to use the new database, users may be stuck using the default "world" regulatory domain which is quite restrictive, therefore they may be unable to use wireless channels that they were able to use previously. Regulatory rules may have also changed for the user's region, which could also make some channels unusable, but this would not be a bug. ** Affects: wireless-regdb (Ubuntu) Importance: Undecided Assignee: Seth Forshee (sforshee) Status: In Progress ** Affects: wireless-regdb (Ubuntu Bionic) Importance: Undecided Assignee: Seth Forshee (sforshee) Status: Confirmed ** Affects: wireless-regdb (Ubuntu Focal) Importance: Undecided Assignee: Seth Forshee (sforshee) Status: Confirmed ** Affects: wireless-regdb (Ubuntu Hirsute) Importance: Undecided Assignee: Seth Forshee (sforshee) Status: Confirmed ** Affects: wireless-regdb (Ubuntu Impish) Importance: Undecided Assignee: Seth Forshee (sforshee) Status: In Progress ** Also affects: wireless-regdb (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: wireless-regdb (Ubuntu Impish) Importance: Undecided Assignee: Seth Forshee (sforshee) Status: In Progress ** Also affects: wireless-regdb (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: wireless-regdb (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: wireless-regdb (Ubuntu Bionic) Status: New => Confirmed ** Changed in: wireless-regdb (Ubuntu Bionic) Assignee: (unassigned) => Seth Forshee (sforshee) ** Changed in: wireless-regdb (Ubuntu Focal) Status: New => Confirmed ** Changed in: wireless-regdb (Ubuntu Focal) Assignee: (unassigned) => Seth Forshee (sforshee) ** Changed in: wireless-regdb (Ubuntu Hirsute) Status: New => Confirmed ** Changed in: wireless-regdb (Ubuntu Hirsute) Assignee: (unassigned) => Seth Forshee (sforshee) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1941955 Title: New upstream release 2021.08.28 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wireless-regdb/+bug/1941955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1936255] Re: New upstream release 2021.07.14
$ dpkg-query -W wireless-regdb wireless-regdb 2021.07.14-0ubuntu1~21.04.1 $ iw reg get global country 00: DFS-UNSET (2402 - 2472 @ 40), (6, 20), (N/A) (2457 - 2482 @ 20), (6, 20), (N/A), AUTO-BW, PASSIVE-SCAN (2474 - 2494 @ 20), (6, 20), (N/A), NO-OFDM, PASSIVE-SCAN (5170 - 5250 @ 80), (6, 20), (N/A), AUTO-BW, PASSIVE-SCAN (5250 - 5330 @ 80), (6, 20), (0 ms), DFS, AUTO-BW, PASSIVE-SCAN (5490 - 5730 @ 160), (6, 20), (0 ms), DFS, PASSIVE-SCAN (5735 - 5835 @ 80), (6, 20), (N/A), PASSIVE-SCAN (57240 - 63720 @ 2160), (N/A, 0), (N/A) $ sudo iw reg set US $ iw reg get global country US: DFS-FCC (2400 - 2472 @ 40), (N/A, 30), (N/A) (5150 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW (5250 - 5350 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW (5470 - 5730 @ 160), (N/A, 23), (0 ms), DFS (5730 - 5850 @ 80), (N/A, 30), (N/A), AUTO-BW (5850 - 5895 @ 40), (N/A, 27), (N/A), NO-OUTDOOR, AUTO-BW, PASSIVE-SCAN (57240 - 71000 @ 2160), (N/A, 40), (N/A) ** Tags removed: verification-needed-hirsute ** Tags added: verification-done-hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1936255 Title: New upstream release 2021.07.14 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wireless-regdb/+bug/1936255/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1936255] Re: New upstream release 2021.07.14
What about the trusty/xenial packages? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1936255 Title: New upstream release 2021.07.14 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wireless-regdb/+bug/1936255/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1936255] Re: New upstream release 2021.07.14
$ dpkg-query -W wireless-regdb wireless-regdb 2021.07.14-0ubuntu1~20.04.1 $ iw reg get global country 00: DFS-UNSET (2402 - 2472 @ 40), (N/A, 20), (N/A) (2457 - 2482 @ 20), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN (2474 - 2494 @ 20), (N/A, 20), (N/A), NO-OFDM, PASSIVE-SCAN (5170 - 5250 @ 80), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN (5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS, AUTO-BW, PASSIVE-SCAN (5490 - 5730 @ 160), (N/A, 20), (0 ms), DFS, PASSIVE-SCAN (5735 - 5835 @ 80), (N/A, 20), (N/A), PASSIVE-SCAN (57240 - 63720 @ 2160), (N/A, 0), (N/A) $ sudo iw reg set US $ iw reg get global country US: DFS-FCC (2400 - 2472 @ 40), (N/A, 30), (N/A) (5150 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW (5250 - 5350 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW (5470 - 5730 @ 160), (N/A, 23), (0 ms), DFS (5730 - 5850 @ 80), (N/A, 30), (N/A), AUTO-BW (5850 - 5895 @ 40), (N/A, 27), (N/A), NO-OUTDOOR, AUTO-BW, PASSIVE-SCAN (57240 - 71000 @ 2160), (N/A, 40), (N/A) ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1936255 Title: New upstream release 2021.07.14 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wireless-regdb/+bug/1936255/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1936255] [NEW] New upstream release 2021.07.14
Public bug reported:
[Impact]
New upstream release. This is a database of wireless regulations, and
should updated in all releases to ensure users have the most up-to-date
regulatory information.
[Test Case]
Following reboot after installing the new database, it should be
possible to query and change the regulatory domain using 'iw reg get'
and 'iw reg set'.
[Where problems could occur]
If crda or the kernel is unable to use the new database, users may be
stuck using the default "world" regulatory domain which is quite
restrictive, therefore they may be unable to use wireless channels that
they were able to use previously. Regulatory rules may have also changed
for the user's region, which could also make some channels unusable, but
this would not be a bug.
** Affects: wireless-regdb (Ubuntu)
Importance: Medium
Assignee: Seth Forshee (sforshee)
Status: In Progress
** Affects: wireless-regdb (Ubuntu Trusty)
Importance: Medium
Assignee: Seth Forshee (sforshee)
Status: In Progress
** Affects: wireless-regdb (Ubuntu Xenial)
Importance: Medium
Assignee: Seth Forshee (sforshee)
Status: In Progress
** Affects: wireless-regdb (Ubuntu Bionic)
Importance: Medium
Assignee: Seth Forshee (sforshee)
Status: In Progress
** Affects: wireless-regdb (Ubuntu Focal)
Importance: Medium
Assignee: Seth Forshee (sforshee)
Status: In Progress
** Affects: wireless-regdb (Ubuntu Groovy)
Importance: Medium
Assignee: Seth Forshee (sforshee)
Status: In Progress
** Affects: wireless-regdb (Ubuntu Hirsute)
Importance: Medium
Assignee: Seth Forshee (sforshee)
Status: In Progress
** Affects: wireless-regdb (Ubuntu Impish)
Importance: Medium
Assignee: Seth Forshee (sforshee)
Status: In Progress
** Also affects: wireless-regdb (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects: wireless-regdb (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: wireless-regdb (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: wireless-regdb (Ubuntu Impish)
Importance: Medium
Assignee: Seth Forshee (sforshee)
Status: In Progress
** Also affects: wireless-regdb (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: wireless-regdb (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: wireless-regdb (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: wireless-regdb (Ubuntu Trusty)
Importance: Undecided => Medium
** Changed in: wireless-regdb (Ubuntu Trusty)
Status: New => In Progress
** Changed in: wireless-regdb (Ubuntu Trusty)
Assignee: (unassigned) => Seth Forshee (sforshee)
** Changed in: wireless-regdb (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: wireless-regdb (Ubuntu Xenial)
Status: New => In Progress
** Changed in: wireless-regdb (Ubuntu Xenial)
Assignee: (unassigned) => Seth Forshee (sforshee)
** Changed in: wireless-regdb (Ubuntu Bionic)
Importance: Undecided => Medium
** Changed in: wireless-regdb (Ubuntu Bionic)
Status: New => In Progress
** Changed in: wireless-regdb (Ubuntu Bionic)
Assignee: (unassigned) => Seth Forshee (sforshee)
** Changed in: wireless-regdb (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: wireless-regdb (Ubuntu Focal)
Status: New => In Progress
** Changed in: wireless-regdb (Ubuntu Focal)
Assignee: (unassigned) => Seth Forshee (sforshee)
** Changed in: wireless-regdb (Ubuntu Groovy)
Importance: Undecided => Medium
** Changed in: wireless-regdb (Ubuntu Groovy)
Status: New => In Progress
** Changed in: wireless-regdb (Ubuntu Groovy)
Assignee: (unassigned) => Seth Forshee (sforshee)
** Changed in: wireless-regdb (Ubuntu Hirsute)
Importance: Undecided => Medium
** Changed in: wireless-regdb (Ubuntu Hirsute)
Status: New => In Progress
** Changed in: wireless-regdb (Ubuntu Hirsute)
Assignee: (unassigned) => Seth Forshee (sforshee)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1936255
Title:
New upstream release 2021.07.14
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wireless-regdb/+bug/1936255/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934906] [NEW] Inaccurate errno reporting in ptrace attach error messages
Public bug reported: Ubuntu carries a patch for gdb, ptrace-error-verbosity.patch, to print some extra information about why attaching to a process might have failed. This inserts a fprintf_unfiltered() call between the ptrace() and the corresponding perror(). Recently something has changed which causes errno to be set to ENOTTY after the failed ptrace but before calling perror(). It's clear that the ptrace() errno is EPERM, since that's the only condition which will print the extra information, however the error message printed is "Inappropriate ioctl for device". Using strace I observed failing tty ioctls which seem to be responsible: ptrace(PTRACE_ATTACH, 11538)= -1 EPERM (Operation not permitted) ioctl(2, TCGETS, 0x7fff1d9c2590)= -1 ENOTTY (Inappropriate ioctl for device) write(2, "Could not attach to process. If"..., 221Could not attach to process. If your uid matches the uid of the target process, check the setting of /proc/sys/kernel/yama/ptrace_scope, or try again as the root user. For more details, see /etc/sysctl.d/10-ptrace.conf ) = 221 ioctl(2, TCGETS, 0x7fff1d9c2590)= -1 ENOTTY (Inappropriate ioctl for device) ... ioctl(1, TCSBRK, 1) = -1 ENOTTY (Inappropriate ioctl for device) ... write(2, "ptrace: Inappropriate ioctl for "..., 39ptrace: Inappropriate ioctl for device.) = 39 Our qa-regression-testing kernel security tests include some ptrace tests which expect attach to fail with an "Operation not permitted" error message. So in addition to being inaccurate, this change in behavior is causing kernel regression testing to fail. This behavior can be reproduced using scripts/test-kernel-security.py from qa-regression-testing. ** Affects: gdb (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934906 Title: Inaccurate errno reporting in ptrace attach error messages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1934906/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933268] [NEW] net kselftest failures in the tls bidir test case
Public bug reported: [Impact] The tls bidir test from the network kselftests fails with the ChaCha cipher: # RUN tls.12_chacha.bidir ... # tls.c:845:bidir:Expected ret (-1) == 0 (0) # bidir: Test terminated by assertion # FAIL tls.12_chacha.bidir This is a problem with the test. The test fixture setup configures tls in one direction on the test socket pair according to the cipher being tested. The test case configures tls in the other direction, however it always configures for GCM regardless of the cipher being tested. When the test cipher is ChaCha the setsockopt() calls fail as the cipher is required to be the same in both directions. [Test Plan] Run the tls test from the net kselftests and confirm that the bidir test now passes when the test cipher is ChaCha. [Where problems could occur] This is a fix for a test case and should have no user impact. A serious problem in the test case might cause passing test cases to fail or prevent subsequent test cases from running. Any such issues should be caught during testing in -proposed before releasing kernels to users. ** Affects: linux (Ubuntu) Importance: Medium Assignee: Seth Forshee (sforshee) Status: Fix Committed ** Affects: linux (Ubuntu Hirsute) Importance: Medium Assignee: Seth Forshee (sforshee) Status: In Progress ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Hirsute) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Hirsute) Status: New => In Progress ** Changed in: linux (Ubuntu Hirsute) Assignee: (unassigned) => Seth Forshee (sforshee) ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933268 Title: net kselftest failures in the tls bidir test case To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931900] Re: Linux-firmware 1.197.1 breaks dual monitor on RX480, shows mirror display with "Unknown Device" under GUI
Was linux-firmware the only package upgraded, or were other packages also upgraded at the same time? Have you confirmed that reverting back to linux-firmware 1.197 fixes the issue? ** Changed in: linux-firmware (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931900 Title: Linux-firmware 1.197.1 breaks dual monitor on RX480, shows mirror display with "Unknown Device" under GUI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1931900/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931798] Re: installed initramfs-tools package post-installation script subprocess returned error exit status 1
Looks like you are probably out of space in /boot, in which case you will need to remove some old kernels. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931798 Title: installed initramfs-tools package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931798/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930713] [NEW] Kernel package builds running out of space on builders
Public bug reported: [Impact] Our kernel builds are sometimes running out of space on the builders when we are building multiple flavours. We've seen this with focal :linux-hwe for amd64 and impish:linux-unstable for arm64. This is in part because package builds are broken up into a build phase (which builds the source tree) and a binary phase (which creates the debs). These are run separately, with the binary phase run under fakeroot to get correct ownership for files in the package archives, requiring builds for multiple flavours to be present on disk at the same time. We have implemented various fixes for this problem over time, and explored many others which have not worked out. But the size of the kernel keeps increasing, and now it seems our only remaining option is to build one flavour and install its files, then remove the flavour build files before building the next flavour. This means that files are installed for later package builds during the build phase, requiring that ownership of these files be fixed up during the binary phase to get correct ownership in the package archives. [Test Plan] Build a full set of kernel packages (inlcuding linux-source and dbgsym packages, which are generally excluded when not building on builders) at a given tag, then build another set from the same tag with the packaging changes applied. Compare the resulting debs to confirm that the set of produced packages is the same, the file lists within the packages are the same, and that file ownership and permissions between the packages is identical. I have done this testing with the proposed patches with a recent linux- unstable tag and found no differences with and without the changes. [Where problems could occur] Incorrect ownership of files in the package archives is the main concern. I have tested for this, but it is possible that future upstream changes could unexpectedly result in files with incorrect ownership. Reordering of the package build sequence could result in missing files which should be in packages, or files present in packages which should be excluded. Some instances of this occurred while developing these changes and have been fixed. Future updates to upstream or to the packaging could cause additional issues. ** Affects: linux (Ubuntu) Importance: Medium Assignee: Seth Forshee (sforshee) Status: In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930713 Title: Kernel package builds running out of space on builders To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930713/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1928393] Re: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault"
On Fri, May 14, 2021 at 06:01:50PM -, Thiago Jung Bauermann wrote: > Ah, ok. This morning I went ahead and overwrote the whole of /lib/firmware/ > amdgpu/ with the files from the latest commit of the upstream linux- > firmware git repo you mention below. It's been only a little over 2 hours, > but my impression is that the latest firmware does solve the problem. If no > retry page fault happens by the end of the day, then I think it's safe to > say that it fixes the issue. Sounds good. > So at the end of the day (or earlier if I get a retry page fault) I'll do > the procedure you mention to use firmware 1.197 and only overwrite the > picasso* files to confirm if those are the ones that need to be changed. > > I don't know much about GPUs, but from looking at Wikipedia¹ I think my > model is a "Vega 10". Should I overwrite the vega10* files as well? > > ¹ https://en.wikipedia.org/wiki/Radeon_RX_Vega_series#Picasso_(2019)_2 I'm basing it on the PCI id I see in dmesg, which is 1002:15d8, which the driver looks to identify as CHIP_RAVEN and flag with AMD_APU_IS_PICASSO. Based on that it will pick firmware files which begin with "picasso". It would be informative though to have the output from "lspci -vvnn" on your machine. Let's try the picasso files first. If that doesn't work you can try the vega10 files (without the new picasso files), then if that doesn't work, try both. Then we'll have an idea about what the minimal set of files is to fix the problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928393 Title: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1928393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928393] Re: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault"
Before we revert we should see if newer firmware fixes the issue, and make sure we are only changing the specific firmware files for your hardware. I think your hardware is the "Picasso" series. Can you try the following? If you are unsure about any of the following steps, let me know and I can provide you with test packages to install instead. Save all files matching /lib/firmware/amdgpu/picasso* from linux- firmware 1.190.5. Reinstall 1.197, then overwrite the picasso firmware files with the ones you saved. Reboot, and confirm that the issues you see with 1.197 are fixed. If they are not fixed, then there's no need to proceed as we haven't found the correct firmware files which are causing your issues. Then please download the picasso firmware files from here: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/tree/amdgpu Use the "plain" link next to each file to download the file. Overwrite the files in /lib/firmware/admgpu with these files, reboot, and see if you continue to have problems. ** Changed in: linux-firmware (Ubuntu) Importance: Undecided => High ** Changed in: linux-firmware (Ubuntu) Status: New => Incomplete ** Changed in: linux-firmware (Ubuntu) Assignee: (unassigned) => Seth Forshee (sforshee) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928393 Title: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1928393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926955] Re: [VMs on] arm64 eMAG system often failing to reboot with "IRQ Exception at 0x000000009BC11F38"
A synchronous exception is a direct result of the executing software -- illegal memory access, invalid instruction, etc. So this looks different than the IRQ exception, which are interrupts from devices external to the CPU. However since this is a VM guest context the exceptions are presumably all generated by the hypervisor, and I'm not currently familiar with exactly how that works. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926955 Title: [VMs on] arm64 eMAG system often failing to reboot with "IRQ Exception at 0x9BC11F38" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926955] Re: arm64 eMAG system often failng to reboot with "IRQ Exception at 0x000000009BC11F38"
I couldn't find anywhere in the kernel that might be printing this message so I went searching, looks like it is probably coming from the firmware: https://github.com/tianocore/edk2/blob/master/ArmPlatformPkg/PrePeiCore/AArch64/ArchPrePeiCore.c#L29 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926955 Title: arm64 eMAG system often failng to reboot with "IRQ Exception at 0x9BC11F38" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925750] Re: Ubuntu 21.04 not loading correctly intel graphics driver
I honestly don't know much about how these dual-GPU systems work. I suspect there must be some firmware interfaces for enabling/disabling the discrete GPU, I have no idea whether those are standardized or platform-specific. Assuming the kernel supports the interfaces for your platform, I also don't know what userspace packages are necessary to utilize those interfaces. You might want to try searching for instructions for your specific machine. You might also check the firmware setup, there may be options there related to enabling/disabling the discrete graphics. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925750 Title: Ubuntu 21.04 not loading correctly intel graphics driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1925750/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925750] Re: Ubuntu 21.04 not loading correctly intel graphics driver
The reason you don't see any Intel graphics drivers in the "Addditional Drivers" tab is that none are needed. The Intel graphics driver (i915) is open source and already included in the kernel, and from your logs it has been loaded. There's nothing I'm seeing currently which indicates a kernel issue. My best guess as to which package decides whether or not to offer wayland sessions is gdm3, so I'll add that to the bug report. ** Also affects: gdm3 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925750 Title: Ubuntu 21.04 not loading correctly intel graphics driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1925750/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925783] Re: installed linux-firmware package post-installation script subprocess returned error exit status 1
It is odd that you have so many marked manually installed. Unless you actually installed those packages manually, they should be marked as automatically installed. We do keep a few kernels installed, so that it's possible to boot back to a previous kernel if an update causes problems, but it shouldn't be that many, and to my understanding that doesn't involve marking packages as manually installed anyhow. So I'm not sure how that might have happened. It should be safe to mark 5.8.0-50, assuming you have the linux- lowlatency package installed. With it being the current kernel in groovy-updates the linux-lowlatency meta package will depend on it and prevent it from being removed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925783 Title: installed linux-firmware package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1925783/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925783] Re: installed linux-firmware package post-installation script subprocess returned error exit status 1
Do you have a separate /boot partition? If so, check whether or not it's full. You may need to remove some old kernel packages you are no longer using. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925783 Title: installed linux-firmware package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1925783/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925407] Re: ubuntu_aufs_smoke_test failed on Hirsute RISCV (CONFIG_AUFS_FS is not set)
Oh, there was also fsprotect which used aufs. But it looked to be abandoned upstream, and other packages provided duplicate functionality using overlayfs, so it has been removed from the archive in hirsute. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925407 Title: ubuntu_aufs_smoke_test failed on Hirsute RISCV (CONFIG_AUFS_FS is not set) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1925407/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925407] Re: ubuntu_aufs_smoke_test failed on Hirsute RISCV (CONFIG_AUFS_FS is not set)
Disabling AUFS was a choice, we planned to update the test accordingly but just didn't get to it. The only remaining software which used AUFS in the archive was docker, and even there support is deprecated in favor of overlayfs. In hirsute a migration strategy was put in place for docker, so AUFS was disabled. We still have it imported into the kernel source for the hwe kernel, as we do need to support AUFS for the life of 20.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925407 Title: ubuntu_aufs_smoke_test failed on Hirsute RISCV (CONFIG_AUFS_FS is not set) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1925407/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925284] Re: Btrfs: Disk replacement causes massive allocation of empty single chunks while degraded
I just confirmed that Ubuntu 21.04 has no kernel patches for btrfs that are not from upstream stable releases, so I have doubts that this is Ubuntu-specific. We do produce testing builds of unpatched upstream kernel releases though, so you could try out 5.11 and 5.12 builds to check whether this is an upstream issue. Those builds can be found here: https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925284 Title: Btrfs: Disk replacement causes massive allocation of empty single chunks while degraded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925284/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925211] Re: Hot-unplug of disks leaves broken block devices around in Hirsute on s390x
** Description changed: + SRU Justification + + [Impact] + + Hot removal of disks under kvm on s390 does not result in the kernel + removing the block device, which can lead to hung tasks and other + issues. + + [Test Plan] + + See steps to reproduce the bug in the original description below. To + test, execute these steps and confirm that the block device gets removed + as expected. + + [Where problems could occur] + + The fix is a revert of the changes which introduced this regression. The + original commit was a removal of supposedly unused code, but it seems a + mistake was made in the logic around unregistering of disks. Reverting + the changes could have potential to introduce bugs related to other virt + devices, especially if it interacts badly with subsequent driver + changes. However, the patch reverted cleanly, and reverting restores the + code to the state which has been working well in previous kernels and + seems like the lowest risk option until a proper fix is available + upstream. + + --- + Repro: #1 Get a guest $ uvt-kvm create --disk 5 --password=ubuntu h release=hirsute arch=s390x label=daily $ uvt-kvm wait h release=hirsute arch=s390x label=daily #2 Attach and Detach disk $ sudo qemu-img create -f qcow2 /var/lib/libvirt/images/test.qcow2 10M $ virsh attach-disk h /var/lib/libvirt/images/test.qcow2 vdc $ virsh detach-disk h vdc - From libvirts POV it is gone at this point $ virsh domblklist h Target Source -- vda /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs.qcow vdb /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs-ds.qcow But the guest thinks still it is present $ uvt-kvm ssh --insecure hirsute-2nd-zfs lsblk ... vdc252:32 0 20M 0 disk This even remains a while after (not a race). Any access to it in the guest will hang (as you'd expect of a non-existing blockdev) 4 017581739 20 0 12140 4800 - S+ pts/0 0:00 | \_ sudo mkfs.ext4 /dev/vdc 4 017591758 20 0 6924 1044 - D+ pts/0 0:00 | \_ mkfs.ext4 /dev/vdc The result above was originally found with hirsute-guest@hirsute-host on s390x I do NOT see the same with groovy-guest@hirsute-host on s390x I DO see the same with hirsute-guest@groovy-host on s390x => Guest version dependent not Host/Hipervisor dependent I DO see the same with ZFS disks AND LVM disks being added => not type dependent I do NOT see the same on x86. => Arch dependent ?? ... the evidence slowly points towards an issue in the guest, damn we are so close to release - but non-fully detaching disks are critical in my POV :-/ Filing this as-is for awareness, but certainly this will need more debugging. Unsure where this is going to eventually I'll now file it for kernel/udev/systemd. If there are any known issues/components that are related let me know please! - --- + --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu65 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 21.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: - + Lspci-vt: -[:00]- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: /sys/bus/usb/devices: No such file or directory Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: Package: udev PackageArchitecture: s390x PciMultimedia: - + ProcFB: - + ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ProcVersionSignature: User Name 5.11.0-14.15-generic 5.11.12 RelatedPackageVersions: - linux-restricted-modules-5.11.0-14-generic N/A - linux-backports-modules-5.11.0-14-generic N/A - linux-firmware N/A + linux-restricted-modules-5.11.0-14-generic N/A + linux-backports-modules-5.11.0-14-generic N/A + linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: hirsute uec-images Uname: Linux 5.11.0-14-generic s390x UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True acpidump: -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925211 Title: Hot-unplug of disks leaves broken block devices around in Hirsute on s390x To manage notifications about this bug go to:
[Bug 1925211] Re: Hot-unplug of disks leaves broken block devices around in Hirsute on s390x
The condition for css_sch_device_unregister(sch) also caught my eye, calling it unconditionally is probably closer to right because it was called in the !cdev case before, and in the attached patch it would no longer be called in this case. However I think in the short term the revert is the safest option, since the code will match what we already know was working in the groovy kernel. Once a fix is committed upstream, we can trade out the revert for that patch. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925211 Title: Hot-unplug of disks leaves broken block devices around in Hirsute on s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1925211/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925211] Re: Hot-unplug of disks leaves broken block devices around in Hirsute
The commit reverts cleanly. We need to confirm that reverting the commit does fix the issue. I put a test build here, please test. https://people.canonical.com/~sforshee/lp1925211/ I doubt we can get a new kernel into the release. If it's extremely urgent we can consider a day 0 SRU kernel for hirsute, otherwise we can make sure it gets into the first normal SRU kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925211 Title: Hot-unplug of disks leaves broken block devices around in Hirsute To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925211/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923846] Re: Kernel panic
*** This bug is a duplicate of bug 1922403 *** https://bugs.launchpad.net/bugs/1922403 ** This bug has been marked a duplicate of bug 1922403 hirsute beta desktop AMD64 ISO kernel panic on boot when booting using UEFI -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923846 Title: Kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1923846/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923638] Re: [FFe] evdi/1.7.0+dfsg-1ubuntu2 fails to build with linux 5.11
** Attachment added: "install.log" https://bugs.launchpad.net/ubuntu/+source/evdi/+bug/1923638/+attachment/5487811/+files/install.log ** Description changed: - evdi in hirsute cannot be used with the 5.11 kernel in hirsute. Upstream - updates for 5.11 proved problematic, and a working set of updates became - available in the upstream project only recently. Unfortunately these - updates are difficult to backport due to upstream changes, and if they - are backported the kernel team has no access to hardware to confirm that - the backports function as intended. Therefore the safest course of - action seems to be to move forward to the latest upstream evdi release - plus they fixes for 5.11 from git, which has been tested by a number of - evdi users already. + evdi-dkms in hirsute cannot be used with the 5.11 kernel in hirsute as + it will fail to build. Upstream updates for 5.11 proved problematic, and + a working set of updates became available in the upstream project only + recently. Unfortunately these updates are difficult to backport due to + upstream changes, and if they are backported the kernel team has no + access to hardware to confirm that the backports function as intended. + Therefore the safest course of action seems to be to move forward to the + latest upstream evdi release plus they fixes for 5.11 from git, which + has been tested by a number of evdi users already. ** Changed in: evdi (Ubuntu) Importance: Undecided => High ** Changed in: evdi (Ubuntu) Assignee: (unassigned) => Paolo Pisati (p-pisati) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923638 Title: [FFe] evdi/1.7.0+dfsg-1ubuntu2 fails to build with linux 5.11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evdi/+bug/1923638/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923638] Re: [FFe] evdi/1.7.0+dfsg-1ubuntu2 fails to build with linux 5.11
** Attachment added: "build.log" https://bugs.launchpad.net/ubuntu/+source/evdi/+bug/1923638/+attachment/5487810/+files/build.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923638 Title: [FFe] evdi/1.7.0+dfsg-1ubuntu2 fails to build with linux 5.11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evdi/+bug/1923638/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923638] Re: [FFe] evdi/1.7.0+dfsg-1ubuntu2 fails to build with linux 5.11
The project does not maintain a changelog, so instead attaching the git commit history between the v1.7.0 and v1.9.1 tags. ** Attachment added: "changelog.txt" https://bugs.launchpad.net/ubuntu/+source/evdi/+bug/1923638/+attachment/5487808/+files/changelog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923638 Title: [FFe] evdi/1.7.0+dfsg-1ubuntu2 fails to build with linux 5.11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evdi/+bug/1923638/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923638] Re: [FFe] evdi/1.7.0+dfsg-1ubuntu2 fails to build with linux 5.11
** Summary changed: - [FFE] evdi/1.7.0+dfsg-1ubuntu2 fails to build with linux 5.11 + [FFe] evdi/1.7.0+dfsg-1ubuntu2 fails to build with linux 5.11 ** Description changed: - This is a scripted bug report about ADT failures while running evdi - tests for linux/5.11.0-14.15 on hirsute. Whether this is caused by the - dep8 tests of the tested source or the kernel has yet to be determined. - - Testing failed on: + evdi in hirsute cannot be used with the 5.11 kernel in hirsute. Upstream + updates for 5.11 proved problematic, and a working set of updates became + available in the upstream project only recently. Unfortunately these + updates are difficult to backport due to upstream changes, and if they + are backported the kernel team has no access to hardware to confirm that + the backports function as intended. Therefore the safest course of + action seems to be to move forward to the latest upstream evdi release + plus they fixes for 5.11 from git, which has been tested by a number of + evdi users already. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923638 Title: [FFe] evdi/1.7.0+dfsg-1ubuntu2 fails to build with linux 5.11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evdi/+bug/1923638/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923638] Re: [FFE] evdi/1.7.0+dfsg-1ubuntu2 fails to build with linux 5.11
** Summary changed: - evdi/1.7.0+dfsg-1ubuntu2 ADT test failure with linux/5.11.0-14.15 + [FFE] evdi/1.7.0+dfsg-1ubuntu2 fails to build with linux 5.11 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923638 Title: [FFE] evdi/1.7.0+dfsg-1ubuntu2 fails to build with linux 5.11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evdi/+bug/1923638/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923638] [NEW] evdi/1.7.0+dfsg-1ubuntu2 ADT test failure with linux/5.11.0-14.15
Public bug reported: This is a scripted bug report about ADT failures while running evdi tests for linux/5.11.0-14.15 on hirsute. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: ** Affects: evdi (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Tags: kernel-adt-failure ** Tags added: kernel-adt-failure ** Changed in: linux (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923638 Title: evdi/1.7.0+dfsg-1ubuntu2 ADT test failure with linux/5.11.0-14.15 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evdi/+bug/1923638/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922759] Re: SND_PCI_QUIRK for Clevo NH55RZQ and Intel NUC10
These commits are already included in hirsute, closing the development task. ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922759 Title: SND_PCI_QUIRK for Clevo NH55RZQ and Intel NUC10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922759/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922406] Re: Intel AX210 Wi-Fi card does not work since updating to 1.196
Looks like 5.11 isn't able to use the new firmware versions added alongside this file anyway, so I'll get a new version uploaded which removes all the version 62 API files along with iwlwifi- ty-a0-gf-a0.pnvm. ** Changed in: linux-firmware (Ubuntu) Importance: Undecided => High ** Changed in: linux-firmware (Ubuntu) Status: New => In Progress ** Changed in: linux-firmware (Ubuntu) Assignee: (unassigned) => Seth Forshee (sforshee) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922406 Title: Intel AX210 Wi-Fi card does not work since updating to 1.196 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1922406/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922406] Re: Intel AX210 Wi-Fi card does not work since updating to 1.196
** Bug watch added: Linux Kernel Bug Tracker #212371 https://bugzilla.kernel.org/show_bug.cgi?id=212371 ** Also affects: linux via https://bugzilla.kernel.org/show_bug.cgi?id=212371 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922406 Title: Intel AX210 Wi-Fi card does not work since updating to 1.196 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1922406/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922406] Re: Intel AX210 Wi-Fi card does not work since updating to 1.196
** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922406 Title: Intel AX210 Wi-Fi card does not work since updating to 1.196 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1922406/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913903] Re: package linux-firmware 1.190 failed to install/upgrade: no se pudieron copiar los datos extraídos de './lib/firmware/dpaa2/mc/mc_10.10.0_lx2160a.itb' a '/lib/firmware/dpaa2/mc/mc_10.
It looks like the package may have downloaded incorrectly. If you are still seeing this issue, try running 'sudo apt-get clean' in a terminal and then try upgrading again. ** Changed in: linux-firmware (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913903 Title: package linux-firmware 1.190 failed to install/upgrade: no se pudieron copiar los datos extraídos de './lib/firmware/dpaa2/mc/mc_10.10.0_lx2160a.itb' a '/lib/firmware/dpaa2/mc/mc_10.10.0_lx2160a.itb.dpkg-new': fin de fichero o de flujo inesperado To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1913903/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895333] Re: cannot change the regulatory domain ath10k, QCA9984 (QNAP QWA-AC2600)
I came across this bug when looking through open linux-firmware bugs. Sorry that it didn't attract any attention before. If this is still a problem, I think the right solution is to pursue a solution upstream. Once one is found we can accept these fixes into Ubuntu. Unfortunately, changing our configs as requested in comment #21 could result in many more users falling out of regulatory compliance, so that is not a viable option. I don't see any suggestion of plans to fix this issue in the upstream ath10k firmware, so I'm changing the status for the linux-firmware package to invalid. If this is a mistake, please change the status back to confirmed and let me know what I've missed. ** Changed in: linux-firmware (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895333 Title: cannot change the regulatory domain ath10k, QCA9984 (QNAP QWA-AC2600) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895333/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922545] Re: gnome-system-monitor fails to launch
I don't see a reason this was filed against the kernel. Changing to gnome-system-monitor. ** Package changed: linux (Ubuntu) => gnome-system-monitor (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922545 Title: gnome-system-monitor fails to launch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1922545/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922732] [NEW] RM: Remove fsprotect binary and source packages from hirsute
Public bug reported: I am requesting removal of the fsprotect source and binary packages from hirsute. [ Package Description ] fsprotect is a tool which uses AUFS to create a root mount built from a read-only filesystem and a tmpfs. All changes to the root mount are written to the tmpfs, leaving the root filesystem in a pristine state. [ Rationale for Removal ] Ubuntu kernels no longer provide AUFS support starting in hirsute, breaking the functionality provided by this package. Similar functionality is available from systemd (https://www.freedesktop.org/software/systemd/man/systemd-volatile- root.service.html) and from the overlayroot package from cloud- initramfs-tools, both of which use the in-kernel overlay filesystem instead of AUFS. Additionally, upstream fsprotect has not seen any changes in 4+ years, and bugs opened in the upstream bug tracker have seen little-to-no activity in the same timeframe, so it's possible the project has been abandoned. No other packages in the archive have any dependencies on fsprotect. ** Affects: fsprotect (Ubuntu) Importance: High Assignee: Andy Whitcroft (apw) Status: Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922732 Title: RM: Remove fsprotect binary and source packages from hirsute To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fsprotect/+bug/1922732/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922600] Re: Hirsute update: v5.11.10 upstream stable release
** Changed in: linux (Ubuntu Hirsute) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922600 Title: Hirsute update: v5.11.10 upstream stable release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922600/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922601] Re: Hirsute update: v5.11.11 upstream stable release
** Changed in: linux (Ubuntu Hirsute) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922601 Title: Hirsute update: v5.11.11 upstream stable release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922601/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922601] [NEW] Hirsute update: v5.11.11 upstream stable release
datasheet
ARM: dts: at91: sam9x60: fix mux-mask for PA7 so it can be set to A, B and C
arm64: dts: ls1043a: mark crypto engine dma coherent
arm64: dts: ls1012a: mark crypto engine dma coherent
arm64: dts: ls1046a: mark crypto engine dma coherent
arm64: stacktrace: don't trace arch_stack_walk()
ACPICA: Always create namespace nodes using acpi_ns_create_node()
ACPI: video: Add missing callback back for Sony VPCEH3U1E
mm/highmem: fix CONFIG_DEBUG_KMAP_LOCAL_FORCE_MAP
gcov: fix clang-11+ support
kasan: fix per-page tags for non-page_alloc pages
hugetlb_cgroup: fix imbalanced css_get and css_put pair for shared mappings
squashfs: fix xattr id and id lookup sanity checks
squashfs: fix inode lookup sanity checks
z3fold: prevent reclaim/free race for headless pages
psample: Fix user API breakage
platform/x86: intel-vbtn: Stop reporting SW_DOCK events
netsec: restore phy power state after controller reset
selinux: fix variable scope issue in live sidtab conversion
selinux: don't log MAC_POLICY_LOAD record on failed policy load
btrfs: fix subvolume/snapshot deletion not triggered on mount
btrfs: fix sleep while in non-sleep context during qgroup removal
btrfs: initialize device::fs_info always
btrfs: fix check_data_csum() error message for direct I/O
btrfs: do not initialize dev replace for bad dev root
btrfs: do not initialize dev stats if we have no dev_root
KVM: x86: Protect userspace MSR filter with SRCU, and set atomically-ish
static_call: Fix static_call_set_init()
static_call: Fix the module key fixup
static_call: Allow module use without exposing static_call_key
static_call: Pull some static_call declarations to the type headers
ia64: fix ptrace(PTRACE_SYSCALL_INFO_EXIT) sign
ia64: fix ia64_syscall_get_set_arguments() for break-based syscalls
mm/fork: clear PASID for new mm
io_uring: cancel deferred requests in try_cancel
block: Suppress uevent for hidden device when removed
nfs: we don't support removing system.nfs4_acl
nvme-pci: add the DISABLE_WRITE_ZEROES quirk for a Samsung PM1725a
nvme-rdma: Fix a use after free in nvmet_rdma_write_data_done
nvme-core: check ctrl css before setting up zns
nvme-fc: return NVME_SC_HOST_ABORTED_CMD when a command has been aborted
nvme-fc: set NVME_REQ_CANCELLED in nvme_fc_terminate_exchange()
nvme: add NVME_REQ_CANCELLED flag in nvme_cancel_request()
nvme: simplify error logic in nvme_validate_ns()
drm/radeon: fix AGP dependency
drm/amdgpu: fb BO should be ttm_bo_type_device
drm/amdgpu/display: Use wm_table.entries for dcn301 calculate_wm
drm/amd/display: Enabled pipe harvesting in dcn30
drm/amd/display: Revert dram_clock_change_latency for DCN2.1
drm/amd/display: Enable pflip interrupt upon pipe enable
block: Fix REQ_OP_ZONE_RESET_ALL handling
regulator: qcom-rpmh: Use correct buck for S1C regulator
regulator: qcom-rpmh: Correct the pmic5_hfsmps515 buck
kselftest: arm64: Fix exit code of sve-ptrace
u64_stats,lockdep: Fix u64_stats_init() vs lockdep
staging: rtl8192e: fix kconfig dependency on CRYPTO
habanalabs: Disable file operations after device is removed
habanalabs: Call put_pid() when releasing control device
sparc64: Fix opcode filtering in handling of no fault loads
umem: fix error return code in mm_pci_probe()
kbuild: dummy-tools: fix inverted tests for gcc
kbuild: add image_name to no-sync-config-targets
irqchip/ingenic: Add support for the JZ4760
cifs: change noisy error message to FYI
atm: idt77252: fix null-ptr-dereference
atm: uPD98402: fix incorrect allocation
net: enetc: set MAC RX FIFO to recommended value
net: davicom: Use platform_get_irq_optional()
net: wan: fix error return code of uhdlc_init()
net: hisilicon: hns: fix error return code of hns_nic_clear_all_rx_fetch()
NFS: Correct size calculation for create reply length
nfs: fix PNFS_FLEXFILE_LAYOUT Kconfig default
gpiolib: acpi: Add missing IRQF_ONESHOT
cpufreq: blacklist Arm Vexpress platforms in cpufreq-dt-platdev
gfs2: fix use-after-free in trans_drain
cifs: ask for more credit on async read/write code paths
gianfar: fix jumbo packets+napi+rx overrun crash
sun/niu: fix wrong RXMAC_BC_FRM_CNT_COUNT count
net: intel: iavf: fix error return code of iavf_init_get_resources()
net: tehuti: fix error return code in bdx_probe()
blk-cgroup: Fix the recursive blkg rwstat
scsi: ufs: ufs-qcom: Disable interrupt in reset path
ixgbe: Fix memleak in ixgbe_configure_clsu32
ALSA: hda: ignore invalid NHLT table
Revert "r8152: adjust the settings about MAC clock speed down for RTL8153"
atm: lanai: dont run lanai_dev_close if not open
atm: eni: dont release is never initialized
powerpc/4xx: Fix build errors from mfdcr()
net: fec: ptp: avoid register access when ipg clock is disabled
net: stmmac: fix dma physical address of descriptor when display ring
mt76: mt7915: only modify tx buffer list after allocating tx token id
mt76: fix tx skb error handling in mt76_dma_tx_queue_skb
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Seth Forshee (sforshee)
Status: In Progress
[Bug 1915717] Re: [FEATURE] Hirsute: support TLS device offload for Bond
** Changed in: linux (Ubuntu Hirsute) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915717 Title: [FEATURE] Hirsute: support TLS device offload for Bond To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915717/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922372] Re: i915 doesn't support some high pixel clock 4k * 60Hz monitors
** Changed in: linux (Ubuntu) Status: Incomplete => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922372 Title: i915 doesn't support some high pixel clock 4k * 60Hz monitors To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1922372/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922600] [NEW] Hirsute update: v5.11.10 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.11.10 upstream stable release from git://git.kernel.org/ Linux 5.11.10 Revert "drm/ttm: Warn on pinning without holding a reference" Revert "drm/ttm: make ttm_bo_unpin more defensive" ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Seth Forshee (sforshee) Status: In Progress ** Affects: linux (Ubuntu Hirsute) Importance: Undecided Assignee: Seth Forshee (sforshee) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: Confirmed ** Changed in: linux (Ubuntu Hirsute) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu Hirsute) Assignee: (unassigned) => Seth Forshee (sforshee) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922600 Title: Hirsute update: v5.11.10 upstream stable release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922600/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905020] Re: [21.04 FEAT] Add kernel debug infos for decompressor stage to kernel-debug package
** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: New => Fix Committed ** Changed in: linux (Ubuntu) Assignee: Canonical Kernel Team (canonical-kernel-team) => Seth Forshee (sforshee) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905020 Title: [21.04 FEAT] Add kernel debug infos for decompressor stage to kernel- debug package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1905020/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903288] Re: Power guest secure boot with static keys: kernel portion
Sorry, I wasn't seeing emails for this bug despite being subscribed. Not sure what's going on with that. If the key is self-signed, shouldn't having the key in .builtin_trusted_keys allow for loading it into the IMA keyring? Or is that insufficient for some reason? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903288 Title: Power guest secure boot with static keys: kernel portion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1903288/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1636847] Re: unexpectedly large memory usage of mounted snaps
On Thu, Mar 18, 2021 at 01:36:55AM -, SaveTheRbtz wrote: > Is it possible (pun intended) to compromise on > `CONFIG_SQUASHFS_DECOMP_MULTI` (which uses num_online_cpus) instead of > `CONFIG_SQUASHFS_DECOMP_MULTI_PERCPU` (which uses `num_possible_cpus`)? It's better, but still not that great of a compromise in my opinion. It's fine for systems with small numbers of CPUs. I still don't think it scales well for large CPU systems. For instance, one machine I have access to has 208 online cores. There we would have 26M of RAM allocated just for the decompression caches for each squashfs mount, which probably isn't fatal since large-cpu systems likely also have large amounts of RAM, but it's also pretty wasteful since it's highly unlikely that 208 squashfs decompressions for the same super block will be going in parallel. It's possible to convince us to change to that option, but we'd at least need more information about what problems the current setting is causing and some testing to confirm that changing the option helps. Please file a new bug for this request. You can subscribe me to the bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1636847 Title: unexpectedly large memory usage of mounted snaps To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1636847/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1636847] Re: unexpectedly large memory usage of mounted snaps
@SaveTheRbtz I did get to the cause, and added a lot of notes about it in the comments for this bug. I even wrote some code to provide a more balanced compromise between memory usage and performance, but once the memory issues were alleviated it seems no one cared about it enough to even try out the test kernels. I don't know if things have improved upstream with the ram usage of CONFIG_SQUASHFS_DECOMP_MULTI_PERCPU. It's probably worth a look. On most systems with a small number of possible cpus and a small number of squashfs mounts it no doubt works fine, but the introduction of snaps caused a big increase in the number of squashfs mounts in Ubuntu systems, which makes CONFIG_SQUASHFS_DECOMP_MULTI_PERCPU problematic if it still has the same behavior. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1636847 Title: unexpectedly large memory usage of mounted snaps To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1636847/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919492] Re: Hirsute update: v5.11.7 upstream stable release
** Changed in: linux (Ubuntu Hirsute) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu Hirsute) Assignee: (unassigned) => Seth Forshee (sforshee) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919492 Title: Hirsute update: v5.11.7 upstream stable release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1919492/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919492] Re: Hirsute update: v5.11.7 upstream stable release
** Description changed: - - SRU Justification - - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: - -v5.11.7 upstream stable release -from git://git.kernel.org/ - - + SRU Justification + + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The following upstream + stable patches should be included in the Ubuntu kernel: + + v5.11.7 upstream stable release + from git://git.kernel.org/ + Linux 5.11.7 KVM: arm64: Fix nVHE hyp panic host context restore mm/page_alloc.c: refactor initialization of struct page for holes in memory layout mm/memcg: rename mem_cgroup_split_huge_fixup to split_page_memcg and add nr_pages argument mm/memcg: set memcg when splitting page mm/madvise: replace ptrace attach requirement for process_madvise mm/userfaultfd: fix memory corruption due to writeprotect mm/highmem.c: fix zero_user_segments() with start > end KVM: arm64: Fix exclusive limit for IPA size KVM: arm64: Reject VM creation when the default IPA size is unsupported KVM: arm64: nvhe: Save the SPE context early KVM: arm64: Avoid corrupting vCPU context register in guest exit KVM: arm64: Fix range alignment when walking page tables KVM: arm64: Ensure I-cache isolation between vcpus of a same VM KVM: kvmclock: Fix vCPUs > 64 can't be online/hotpluged KVM: x86: Ensure deadline timer has truly expired before posting its IRQ x86/entry: Fix entry/exit mismatch on failed fast 32-bit syscalls x86/sev-es: Use __copy_from_user_inatomic() x86/sev-es: Correctly track IRQ states in runtime #VC handler x86/sev-es: Check regs->sp is trusted before adjusting #VC IST stack x86/sev-es: Introduce ip_within_syscall_gap() helper x86/unwind/orc: Disable KASAN checking in the ORC unwinder, part 2 kasan: fix KASAN_STACK dependency for HW_TAGS kasan, mm: fix crash with HW_TAGS and DEBUG_PAGEALLOC binfmt_misc: fix possible deadlock in bm_register_write powerpc: Fix missing declaration of [en/dis]able_kernel_vsx() powerpc: Fix inverted SET_FULL_REGS bitop powerpc/64s: Fix instruction encoding for lis in ppc_function_entry() efi: stub: omit SetVirtualAddressMap() if marked unsupported in RT_PROP table sched: Simplify set_affinity_pending refcounts sched: Fix affine_move_task() self-concurrency sched: Optimize migration_cpu_stop() sched: Simplify migration_cpu_stop() sched: Collate affine_move_task() stoppers sched/membarrier: fix missing local execution of ipi_sync_rq_state() sched: Fix migration_cpu_stop() requeueing linux/compiler-clang.h: define HAVE_BUILTIN_BSWAP* zram: fix broken page writeback zram: fix return value on writeback_store include/linux/sched/mm.h: use rcu_dereference in in_vfork() stop_machine: mark helpers __always_inline memblock: fix section mismatch warning seqlock,lockdep: Fix seqcount_latch_init() powerpc/64s/exception: Clean up a missed SRR specifier hrtimer: Update softirq_expires_next correctly after __hrtimer_get_next_event() perf/x86/intel: Set PERF_ATTACH_SCHED_CB for large PEBS and LBR perf/core: Flush PMU internal buffers for per-CPU events mptcp: fix memory accounting on allocation error mptcp: put subflow sock on connect error net: expand textsearch ts_state to fit skb_seq_state perf/arm_dmc620_pmu: Fix error return code in dmc620_pmu_device_probe() drm/nouveau: fix dma syncing for loops (v2) io_uring: perform IOPOLL reaping if canceler is thread itself arm64: mm: use a 48-bit ID map when possible on 52-bit VA builds configfs: fix a use-after-free in __configfs_open_file nvme-fc: fix racing controller reset and create association drm/ttm: Fix TTM page pool accounting block: rsxx: fix error return code of rsxx_pci_probe() NFSv4.2: fix return value of _nfs4_get_security_label() NFS: Don't gratuitously clear the inode cache when lookup failed NFS: Don't revalidate the directory permissions on a lookup failure SUNRPC: Set memalloc_nofs_save() for sync tasks arm64/mm: Fix pfn_valid() for ZONE_DEVICE based memory cpufreq: qcom-hw: Fix return value check in qcom_cpufreq_hw_cpu_init() cpufreq: qcom-hw: fix dereferencing freed memory 'data' net: macb: Add default usrio config to default gem config powerpc/sstep: Fix VSX instruction emulation sh_eth:
[Bug 1919492] [NEW] Hirsute update: v5.11.7 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.11.7 upstream stable release from git://git.kernel.org/ Linux 5.11.7 KVM: arm64: Fix nVHE hyp panic host context restore mm/page_alloc.c: refactor initialization of struct page for holes in memory layout mm/memcg: rename mem_cgroup_split_huge_fixup to split_page_memcg and add nr_pages argument mm/memcg: set memcg when splitting page mm/madvise: replace ptrace attach requirement for process_madvise mm/userfaultfd: fix memory corruption due to writeprotect mm/highmem.c: fix zero_user_segments() with start > end KVM: arm64: Fix exclusive limit for IPA size KVM: arm64: Reject VM creation when the default IPA size is unsupported KVM: arm64: nvhe: Save the SPE context early KVM: arm64: Avoid corrupting vCPU context register in guest exit KVM: arm64: Fix range alignment when walking page tables KVM: arm64: Ensure I-cache isolation between vcpus of a same VM KVM: kvmclock: Fix vCPUs > 64 can't be online/hotpluged KVM: x86: Ensure deadline timer has truly expired before posting its IRQ x86/entry: Fix entry/exit mismatch on failed fast 32-bit syscalls x86/sev-es: Use __copy_from_user_inatomic() x86/sev-es: Correctly track IRQ states in runtime #VC handler x86/sev-es: Check regs->sp is trusted before adjusting #VC IST stack x86/sev-es: Introduce ip_within_syscall_gap() helper x86/unwind/orc: Disable KASAN checking in the ORC unwinder, part 2 kasan: fix KASAN_STACK dependency for HW_TAGS kasan, mm: fix crash with HW_TAGS and DEBUG_PAGEALLOC binfmt_misc: fix possible deadlock in bm_register_write powerpc: Fix missing declaration of [en/dis]able_kernel_vsx() powerpc: Fix inverted SET_FULL_REGS bitop powerpc/64s: Fix instruction encoding for lis in ppc_function_entry() efi: stub: omit SetVirtualAddressMap() if marked unsupported in RT_PROP table sched: Simplify set_affinity_pending refcounts sched: Fix affine_move_task() self-concurrency sched: Optimize migration_cpu_stop() sched: Simplify migration_cpu_stop() sched: Collate affine_move_task() stoppers sched/membarrier: fix missing local execution of ipi_sync_rq_state() sched: Fix migration_cpu_stop() requeueing linux/compiler-clang.h: define HAVE_BUILTIN_BSWAP* zram: fix broken page writeback zram: fix return value on writeback_store include/linux/sched/mm.h: use rcu_dereference in in_vfork() stop_machine: mark helpers __always_inline memblock: fix section mismatch warning seqlock,lockdep: Fix seqcount_latch_init() powerpc/64s/exception: Clean up a missed SRR specifier hrtimer: Update softirq_expires_next correctly after __hrtimer_get_next_event() perf/x86/intel: Set PERF_ATTACH_SCHED_CB for large PEBS and LBR perf/core: Flush PMU internal buffers for per-CPU events mptcp: fix memory accounting on allocation error mptcp: put subflow sock on connect error net: expand textsearch ts_state to fit skb_seq_state perf/arm_dmc620_pmu: Fix error return code in dmc620_pmu_device_probe() drm/nouveau: fix dma syncing for loops (v2) io_uring: perform IOPOLL reaping if canceler is thread itself arm64: mm: use a 48-bit ID map when possible on 52-bit VA builds configfs: fix a use-after-free in __configfs_open_file nvme-fc: fix racing controller reset and create association drm/ttm: Fix TTM page pool accounting block: rsxx: fix error return code of rsxx_pci_probe() NFSv4.2: fix return value of _nfs4_get_security_label() NFS: Don't gratuitously clear the inode cache when lookup failed NFS: Don't revalidate the directory permissions on a lookup failure SUNRPC: Set memalloc_nofs_save() for sync tasks arm64/mm: Fix pfn_valid() for ZONE_DEVICE based memory cpufreq: qcom-hw: Fix return value check in qcom_cpufreq_hw_cpu_init() cpufreq: qcom-hw: fix dereferencing freed memory 'data' net: macb: Add default usrio config to default gem config powerpc/sstep: Fix VSX instruction emulation sh_eth: fix TRSCER mask for R7S72100 net: phy: ti: take into account all possible interrupt sources mlxsw: spectrum_router: Ignore routes using a deleted nexthop object staging: comedi: pcl818: Fix endian problem for AI command data staging: comedi: pcl711: Fix endian problem for AI command data staging: comedi: me4000: Fix endian problem for AI command data staging: comedi: dmm32at: Fix endian problem for AI command data staging: comedi: das800: Fix endian problem for AI command data staging: comedi: das6402: Fix endian problem for AI command data staging: comedi: adv_pci1710: Fix endian problem for AI command data staging: comedi: addi_apci_1500: Fix endian problem for command sample staging: comedi:
[Bug 1903288] Re: Power guest secure boot with static keys: kernel portion
I should have mentioned, the kernel in comment #11 is not signed with the archive signing key since it's in a personal ppa, but the cert which is built into the kernel is for the archive key. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903288 Title: Power guest secure boot with static keys: kernel portion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1903288/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903288] Re: Power guest secure boot with static keys: kernel portion
Here's a test build with public cert for the opal signing key built into .builtin_trusted_keys: https://launchpad.net/~sforshee/+archive/ubuntu/lp1903288 I'm still working out exactly how we want to distribute the key in the filesystem, but if you can try that out and let me know whether that works for you. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903288 Title: Power guest secure boot with static keys: kernel portion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1903288/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916872] Re: oss4-dkms: build failure with linux 5.11
** Changed in: oss4 (Ubuntu) Importance: Undecided => Medium ** Changed in: oss4 (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916872 Title: oss4-dkms: build failure with linux 5.11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/oss4/+bug/1916872/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916905] Re: openrazer 2.9.0+dfsg-1 build failure with linux 5.10* on s390x
** Changed in: openrazer (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916905 Title: openrazer 2.9.0+dfsg-1 build failure with linux 5.10* on s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openrazer/+bug/1916905/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903288] Re: Power guest secure boot with static keys: kernel portion
Sorry for the delayed response here, it's taken me a while to get some of the needed information. In general this should be fine. One thing to note is that the key is self-signed, so we will need to add the signing key itself into .builtin_trusted_keys. This should still allow loading the key into the IMA keyring. It might not be necessary to do so, if IMA trusts keys in .builtin_trusted_keys for signing kexec kernels (I don't know if it does or not), but it seems to be that structuring this as though the CA and signing keys are separate keys is a good idea to ensure that this continues to work if the key setup ever changes in the future. I'll work on getting some test packages put together in a PPA for testing. Let me know if you see any changes which need to be made as a result of the information I've provided. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903288 Title: Power guest secure boot with static keys: kernel portion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1903288/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911835] Re: package linux-firmware 1.187.7 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1
*** This bug is a duplicate of bug 1911836 *** https://bugs.launchpad.net/bugs/1911836 Marking as a duplicate of bug 1911836 based on comment #2. ** This bug has been marked a duplicate of bug 1911836 package linux-image-5.4.0-62-generic 5.4.0-62.70 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911835 Title: package linux-firmware 1.187.7 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1911835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912947] Re: bluetooth: hci0: failed to restart LE scan: status 31
** Package changed: linux-firmware (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912947 Title: bluetooth: hci0: failed to restart LE scan: status 31 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912947/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912811] [NEW] Update dwarves-dfsg in focal to version 1.17 from groovy
Public bug reported: [Impact] BTF is an extremely useful tool for BPF developers. Enabling BTF support in the kernel requires pahole 1.16 or later, but in focal we have only 1.15. The simplest path for us to get a sufficiently updated version of pahole is to backport dwarves-dfsg from groovy, which is at version 1.17. [Test Case] Building a kernel with CONFIG_DEBUG_INFO_BTF enabled fails with the version of pahole currently in focal, complaining that pahole 1.16 or later is needed. Building with a newer version of pahole is successful. [Where problems could occur] Moving the package forward carries significant risks. The biggest risk is clearly new bugs. There may also be interface changes which break existing workflows. I believe the following factors indicate that the level of risk here is acceptable: * Currently there are no bug reports open against the package in groovy (there are virtually no bug reports open at all against the package in fact). * I have done a review of the changes between 1.15 and 1.17. The bulk of the changes are for the required BTF support, and the vast majority of these are an update of its local copy of libbpf. The balance of the changes are bug fixes and enhancements to pahole, none of which look to change the user interface in a way which will break existing workflows. * No packages in focal have dependencies or build dependencies on the dwarves package. ** Affects: dwarves-dfsg (Ubuntu) Importance: Undecided Status: Invalid ** Affects: dwarves-dfsg (Ubuntu Focal) Importance: Medium Assignee: Seth Forshee (sforshee) Status: In Progress ** Also affects: dwarves-dfsg (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: dwarves-dfsg (Ubuntu) Status: New => Invalid ** Changed in: dwarves-dfsg (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: dwarves-dfsg (Ubuntu Focal) Status: New => In Progress ** Changed in: dwarves-dfsg (Ubuntu Focal) Assignee: (unassigned) => Seth Forshee (sforshee) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912811 Title: Update dwarves-dfsg in focal to version 1.17 from groovy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dwarves-dfsg/+bug/1912811/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907298] Re: glibc 2.32-0ubuntu5 ADT test failure with linux 5.10.0-7.8
Reverting "powerpc/64/signal: Balance return predictor stack in signal trampoline" gets the test passing, so that does appear to be the cause. I'm not sure what needs to happen here to resolve the test failure though. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907298 Title: glibc 2.32-0ubuntu5 ADT test failure with linux 5.10.0-7.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1907298/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912499] [NEW] Reset upload number to 1 for derivative ABI bumps
Public bug reported: [Impact] For derivative kernels we reset the upload number to 1 when bumping the ABI. For the meta packages we just continue to increment the upload number. This at best looks odd and at worst may result in some confusion. Update the scripting in linux-meta to likewise reset the upload number whenever its derivative kernel has done an ABI bump. [Test Case] When preparing a derivative meta package, note that an ABI bump results in the upload number being reset to 1, while subsequent uploads using the same ABI result in incrementing the upload number. [Where problems could occur] This change affects only preparation of derivative meta packages. Bugs could result in having an unexpected upload number in the package version, but any such mistakes should be caught when reviewing package changes prior to upload. ** Affects: linux-meta (Ubuntu) Importance: Low Assignee: Seth Forshee (sforshee) Status: In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912499 Title: Reset upload number to 1 for derivative ABI bumps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1912499/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912198] Re: package linux-firmware 1.187.8 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1
@Tim I do not think you have the same problem. I see some errors which look like debconf is attempting to prompt you about something but failing to find a frontend to use for the prompt. Possibly this is the cause, but I'm not sure. You can try running the upgrade like this: # DEBIAN_FRONTEND=noninteractive apt-get upgrade -y which might help. If not, maybe try filing a bug against the apt package by running the upgrade, killing it after it hangs, and then running: $ ubuntu-bug apt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912198 Title: package linux-firmware 1.187.8 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912198/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907298] Re: glibc 2.32-0ubuntu5 ADT test failure with linux 5.10.0-7.8
Looking through powerpc changes between Linux 5.8 and 5.10, I see a handful of changes to signal-related code. This in particular jumps out as potentially affecting the register state for signal handling: commit 0138ba5783ae0dcc799ad401a1e8ac8333790df9 Author: Nicholas Piggin Date: Mon May 11 20:19:52 2020 +1000 powerpc/64/signal: Balance return predictor stack in signal trampoline Returning from an interrupt or syscall to a signal handler currently begins execution directly at the handler's entry point, with LR set to the address of the sigreturn trampoline. When the signal handler function returns, it runs the trampoline. It looks like this: # interrupt at user address xyz # kernel stuff... signal is raised rfid # void handler(int sig) addis 2,12,.TOC.-.LCF0@ha addi 2,2,.TOC.-.LCF0@l mflr 0 std 0,16(1) stdu 1,-96(1) # handler stuff ld 0,16(1) mtlr 0 blr # __kernel_sigtramp_rt64 addir1,r1,__SIGNAL_FRAMESIZE li r0,__NR_rt_sigreturn sc # kernel executes rt_sigreturn rfid # back to user address xyz Note the blr with no matching bl. This can corrupt the return predictor. Solve this by instead resuming execution at the signal trampoline which then calls the signal handler. qtrace-tools link_stack checker confirms the entire user/kernel/vdso cycle is balanced after this patch, whereas it's not upstream. Alan confirms the dwarf unwind info still looks good. gdb still recognises the signal frame and can step into parent frames if it break inside a signal handler. Performance is pretty noisy, not a very significant change on a POWER9 here, but branch misses are consistently a lot lower on a microbenchmark: Performance counter stats for './signal': 13,085.72 msec task-clock#1.000 CPUs utilized 45,024,760,101 cycles#3.441 GHz 65,102,895,542 instructions #1.45 insn per cycle 11,271,673,787 branches # 861.372 M/sec 59,468,979 branch-misses #0.53% of all branches 12,989.09 msec task-clock#1.000 CPUs utilized 44,692,719,559 cycles#3.441 GHz 65,109,984,964 instructions #1.46 insn per cycle 11,282,136,057 branches # 868.585 M/sec 39,786,942 branch-misses #0.35% of all branches Signed-off-by: Nicholas Piggin Signed-off-by: Michael Ellerman Link: https://lore.kernel.org/r/20200511101952.1463138-1-npig...@gmail.com -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907298 Title: glibc 2.32-0ubuntu5 ADT test failure with linux 5.10.0-7.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1907298/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912208] Re: package linux-firmware 1.187.7 failed to install/upgrade: unable to create '/lib/firmware/brcm/BCM-0bb4-0306.hcd.dpkg-new' (while processing './lib/firmware/brcm/BCM-0bb4-0306.hcd'):
Have you tried to install any firmware, either manually or via third- party packages? Are you running any antivirus tools? What is the output from running the following commands in a terminal? ls -ld /lib/firmware/brcm ls -l /lib/firmware/brcm ** Changed in: linux-firmware (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912208 Title: package linux-firmware 1.187.7 failed to install/upgrade: unable to create '/lib/firmware/brcm/BCM-0bb4-0306.hcd.dpkg-new' (while processing './lib/firmware/brcm/BCM-0bb4-0306.hcd'): Operation not permitted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1912208/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912198] Re: package linux-firmware 1.187.8 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1
The problem appears to be a failed sync when regenerating the initrd. Looking through the attached dmesg I see a lot of disk-related errors. This could indicate a kernel bug or potentially a hardware problem. This is not directly a problem in linux-firmware, reassigning to linux. Have you noticed any other problems or strange behavior recently? Have you done any hardware modifications that could have resulted in something like a loose or damaged SATA cable in your machine? Did any issues start after a kernel update? ** Package changed: linux-firmware (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912198 Title: package linux-firmware 1.187.8 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912198/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909495] Re: Unable to start BIOS VMs since Linux 5.10
Seems like it might be the same as this bug: https://bugzilla.kernel.org/show_bug.cgi?id=210695 If so this is the fix, which is already queued up for the next 5.10 stable update: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=39b4d43e6003cee51cd119596d3c33d0449eb44c ** Bug watch added: Linux Kernel Bug Tracker #210695 https://bugzilla.kernel.org/show_bug.cgi?id=210695 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909495 Title: Unable to start BIOS VMs since Linux 5.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1909495/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900141] Re: overlay: permission regression in 5.4.0-51.56 due to patches related to CVE-2020-16120
Confirmed that the attached test script reproduces the problem with 5.8.0-36-generic from groovy-updates. ith 5.8.0-37-generic from groovy- proposed the problem is fixed. ** Tags removed: verification-needed-groovy ** Tags added: verification-done-groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900141 Title: overlay: permission regression in 5.4.0-51.56 due to patches related to CVE-2020-16120 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1900141/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1900141] Re: overlay: permission regression in 5.4.0-51.56 due to patches related to CVE-2020-16120
On Mon, Jan 11, 2021 at 11:12:35AM -, Philipp Wendler wrote: > I tested it on a Focal machine and the -proposed kernel works. However, > I don't have a Groovy machine here, is it necessary for me to test this? I can verify the fix in groovy. > I noticed that in the list of affected packages in the bug metadata > Bionic is not mentioned. Will the fix also be backported there? It depends on which kernel you are talking about. The bionic GA kernel (4.15) was not affected based on my testing. If you are seeing problems with it, please let me know. The bionic HWE kernel is derived from the kernel source in focal, so that kernel does not need to be fixed separately from the focal kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900141 Title: overlay: permission regression in 5.4.0-51.56 due to patches related to CVE-2020-16120 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1900141/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903288] Re: Power guest secure boot with static keys: kernel portion
I think I've got a good idea of what you're after here. Let me look into this, and I'll try to get back to you soon. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903288 Title: Power guest secure boot with static keys: kernel portion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1903288/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909705] Re: Fix Realtek 8821c bluetooth fails reconnect BLE devices after suspend
@Kai-Heng please add some information about how you verified this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909705 Title: Fix Realtek 8821c bluetooth fails reconnect BLE devices after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1909705/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900141] Re: overlay: permission regression in 5.4.0-51.56 due to patches related to CVE-2020-16120
** Changed in: linux (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900141 Title: overlay: permission regression in 5.4.0-51.56 due to patches related to CVE-2020-16120 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1900141/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900141] Re: overlay: permission regression in 5.4.0-51.56 due to patches related to CVE-2020-16120
** Description changed:
+ SRU Justification
+
+ [Impact]
+
+ The backports to fix CVE-2020-16120 introduced a regression for overlay
+ mounts within user namespaces. Files with ownership outside of the user
+ namespace can no longer be accessed, even if allowed by both DAC and
+ MAC.
+
+ This issue is fixed by the following upstream commit:
+
+
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b6650dab404c701d7fe08a108b746542a934da84
+
+ This commit relaxes the check to remove O_NOATIME from the open flags
+ for the file in the lower filesystem when the overlay filesystem mounter
+ is not privileged with respect to the underlying inode, rather than
+ failing the open as happens now.
+
+ [Test Case]
+
+ The attached lp1900141.sh script reproduces the issue.
+
+ [Where problems could occur]
+
+ For the most part this patch restores previous behavior of allowing
+ access to these files while keeping the enhanced permission checks
+ towards the lower filesystem to help prevent unauthorized access to file
+ data in the lower filesystem. The one difference in behavior is that
+ files in the lower filesystem may no longer be opened with the O_NOATIME
+ flag, potentially causing atime updates for these files which were not
+ happening before. If any software expects O_NOATIME behavior in this
+ situation then it could cause problems for that software. However, the
+ correct behavior is that only the inode owner or a process with
+ CAP_FOWNER towards the inode owner is allowed to open with O_NOATIME (as
+ documented in open(2)).
+
+ ---
+
We use unprivileged user namespaces with overlay mounts for containers.
After recently upgrading our Focal kernels to 5.4.0-51.56 this breaks,
one cannot access files through the overlay mount in the container
anymore. This is very likely caused by some of the patches that were
added in relation to CVE-2020-16120.
The following commands allow to reproduce the problem when executed as
an arbitrary non-root user:
mkdir /tmp/test /tmp/test/upper /tmp/test/work /tmp/test/usr
unshare -m -U -r /bin/sh -c "mount -t overlay none /tmp/test/usr -o
lowerdir=/usr,upperdir=/tmp/test/upper,workdir=/tmp/test/work; ls -l
/tmp/test/usr/bin/id; file /tmp/test/usr/bin/id; /tmp/test/usr/bin/id"
The output when broken is this:
-rwxr-xr-x 1 nobody nogroup 47480 Sep 5 2019 /tmp/test/usr/bin/id
/tmp/test/usr/bin/id: executable, regular file, no read permission
/bin/sh: 1: /tmp/test/usr/bin/id: Operation not permitted
The expected output is this:
-rwxr-xr-x 1 nobody nogroup 43224 Jan 18 2018 /tmp/test/usr/bin/id
/tmp/test/usr/bin/id: ELF 64-bit LSB shared object, ...
uid=0(root) gid=0(root) groups=0(root),65534(nogroup)
These commands create a user namespace and within it mount an overlay of
/usr to /tmp/test/usr and then try to access something in it.
This works on Ubuntu Bionic with kernel 4.15.0-121.123 (note that this
already includes a fix for CVE-2020-16120) and on kernel 5.4.0-48.52 but
is broken on kernel 5.4.0-51.56, no matter whether on Bionic or Focal.
So I strongly suspect that not the actual security fixes for
CVE-2020-16120 are the cause, but one of the following two patches that
according to the changelogs were applied in the same revision but only
to 5.4, not to 4.15:
ovl: call secutiry hook in ovl_real_ioctl()
ovl: check permission to open real file
The mail with the announcement (https://www.openwall.com/lists/oss-
security/2020/10/13/6) lists these two commits as separate from the
actual security fixes ("may be desired or necessary").
Is it possible to revert these two changes or fix them such that our
unprivileged containers work again on Ubuntu kernel 5.4? Or is there a
workaround that I can add to my container solution such that this use
case works again?
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-51-generic 5.4.0-51.56
ProcVersionSignature: User Name 5.4.0-51.56-generic 5.4.65
Uname: Linux 5.4.0-51-generic x86_64
AlsaDevices:
- total 0
- crw-rw 1 root audio 116, 1 Oct 14 04:48 seq
- crw-rw 1 root audio 116, 33 Oct 14 04:48 timer
+ total 0
+ crw-rw 1 root audio 116, 1 Oct 14 04:48 seq
+ crw-rw 1 root audio 116, 33 Oct 14 04:48 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
CasperMD5CheckResult: skip
CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read
kernel buffer failed: Operation not permitted
Date: Fri Oct 16 13:02:32 2020
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb:
- Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
- Bus 001 Device 001: ID
[Bug 1900141] Re: overlay: permission regression in 5.4.0-51.56 due to patches related to CVE-2020-16120
** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Groovy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Importance: Undecided => High ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Seth Forshee (sforshee) ** Changed in: linux (Ubuntu Groovy) Importance: Undecided => High ** Changed in: linux (Ubuntu Groovy) Status: New => In Progress ** Changed in: linux (Ubuntu Groovy) Assignee: (unassigned) => Seth Forshee (sforshee) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900141 Title: overlay: permission regression in 5.4.0-51.56 due to patches related to CVE-2020-16120 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1900141/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900141] Re: overlay: permission regression in 5.4.0-51.56 due to patches related to CVE-2020-16120
Apologies for the delay on this bug. There is a fix upstream in 5.11-rc1, I've backported the fix to the test kernel located here: https://people.canonical.com/~sforshee/lp1900141/linux-5.4.0-59.65+lp1900141v202101061102/ I'm also attaching a script which reproduces the bug. In my testing the problem looks to be fixed by this patch, but additional testing is appreciated. ** Attachment added: "lp1900141.sh" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1900141/+attachment/5449802/+files/lp1900141.sh -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900141 Title: overlay: permission regression in 5.4.0-51.56 due to patches related to CVE-2020-16120 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1900141/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907158] Re: Update linux-firmware in focal for 5.8 hwe kernel
I confirmed that that correct new firmware files have been added, and that the contents of those files match what is expected. I also confirmed that the nic-firmware udeb updates are as expected, and that there are no changes to the contents of the scsi-firmware udeb. ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907158 Title: Update linux-firmware in focal for 5.8 hwe kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1907158/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904906] Re: 5.10 kernel fails to boot with secure boot disabled
That's not the sort of config we usually turn on, as it's more of a developer feature than something end users are interested in. So I don't see any need to turn the option back on. We can go ahead and grab the patch though. In any case I'd like to get some secure boot testing with the current build, as we'd like to try and get a 5.10 build into hirsute-proposed next week. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904906 Title: 5.10 kernel fails to boot with secure boot disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1904906/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907307] Re: lxc 1:4.0.4-0ubuntu3 ADT test failure with linux 5.10.0-7.8
lxc-test-api-reboot fails. The container fails to start, I see lots of errors in the logs related to mounting things. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907307 Title: lxc 1:4.0.4-0ubuntu3 ADT test failure with linux 5.10.0-7.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1907307/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907307] [NEW] lxc 1:4.0.4-0ubuntu3 ADT test failure with linux 5.10.0-7.8
Public bug reported: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute-canonical-kernel-team-bootstrap/hirsute/amd64/l/lxc/20201208_183047_03358@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute-canonical-kernel-team-bootstrap/hirsute/arm64/l/lxc/20201208_193132_88a43@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute-canonical-kernel-team-bootstrap/hirsute/ppc64el/l/lxc/20201208_194831_12ffc@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute-canonical-kernel-team-bootstrap/hirsute/s390x/l/lxc/20201208_175951_b132c@/log.gz ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Tags: kernel-adt-failure ** Tags added: kernel-adt-failure -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907307 Title: lxc 1:4.0.4-0ubuntu3 ADT test failure with linux 5.10.0-7.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1907307/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907298] [NEW] glibc 2.32-0ubuntu5 ADT test failure with linux 5.10.0-7.8
Public bug reported: Testing failed on: ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute-canonical-kernel-team-bootstrap/hirsute/ppc64el/g/glibc/20201208_192946_04f11@/log.gz -- FAIL: misc/tst-sigcontext-get_pc original exit status 1 info: address in signal handler: 0x737faa11db44 info: call stack entry 0: 0x737faa311f58 info: call stack entry 1: 0x737faa3404c4 info: call stack entry 2: 0x0 info: call stack entry 3: 0x737faa312144 info: call stack entry 4: 0x737faa312870 info: call stack entry 5: 0x737faa313264 info: call stack entry 6: 0x737faa311c40 info: call stack entry 7: 0x737faa0f9e5c info: call stack entry 8: 0x737faa0fa040 error: ../sysdeps/unix/sysv/linux/tst-sigcontext-get_pc.c:60: not true: found error: 1 test failures -- ** Affects: glibc (Ubuntu) Importance: Undecided Status: New ** Tags: kernel-adt-failure ** Tags added: kernel-adt-failure ** Description changed: Testing failed on: - ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute-canonical-kernel-team-bootstrap/hirsute/ppc64el/g/glibc/20201208_192946_04f11@/log.gz + ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute-canonical-kernel-team-bootstrap/hirsute/ppc64el/g/glibc/20201208_192946_04f11@/log.gz + + -- + FAIL: misc/tst-sigcontext-get_pc + original exit status 1 + info: address in signal handler: 0x737faa11db44 + info: call stack entry 0: 0x737faa311f58 + info: call stack entry 1: 0x737faa3404c4 + info: call stack entry 2: 0x0 + info: call stack entry 3: 0x737faa312144 + info: call stack entry 4: 0x737faa312870 + info: call stack entry 5: 0x737faa313264 + info: call stack entry 6: 0x737faa311c40 + info: call stack entry 7: 0x737faa0f9e5c + info: call stack entry 8: 0x737faa0fa040 + error: ../sysdeps/unix/sysv/linux/tst-sigcontext-get_pc.c:60: not true: found + error: 1 test failures + -- -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907298 Title: glibc 2.32-0ubuntu5 ADT test failure with linux 5.10.0-7.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1907298/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904906] Re: 5.10 kernel fails to boot with secure boot disabled
The 5.10.0-7.8 with CONFIG_RCU_SCALE_TEST disabled has completed and is available in https://launchpad.net/~canonical-kernel- team/+archive/ubuntu/bootstrap as before. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904906 Title: 5.10 kernel fails to boot with secure boot disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1904906/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907158] [NEW] Update linux-firmware in focal for 5.8 hwe kernel
Public bug reported: [Impact] Some firmware files are missing for the 5.8 hwe kernel in focal, which may cause some hardware supported by that kernel to fail to function or to function incorrectly. These files are added to both to the linux- firmware package and the nic-firmware udeb. [Test Case] Confirm that the new files are present in the linux-firmware deb and the nic-firmware udeb. [Where problems could occur] Most of these files are not used by the existing focal kernels and should not cause any problems aside from occupying disk space. A handful of the files might have been introduced to the linux-firmware package between focal and groovy and could be used by the existing focal kernel, and these have a potential to introduce regressions for users with hardware which uses that firmware. Also, users which have manually added any of these firmware files to their systems may encounter issues when upgrading. ** Affects: linux-firmware (Ubuntu) Importance: Undecided Assignee: Seth Forshee (sforshee) Status: Invalid ** Affects: linux-firmware (Ubuntu Focal) Importance: Medium Assignee: Seth Forshee (sforshee) Status: In Progress ** Also affects: linux-firmware (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-firmware (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-firmware (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux-firmware (Ubuntu Focal) Assignee: (unassigned) => Seth Forshee (sforshee) ** Changed in: linux-firmware (Ubuntu) Status: In Progress => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907158 Title: Update linux-firmware in focal for 5.8 hwe kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1907158/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904906] Re: 5.10 kernel fails to boot with secure boot disabled
Our latest 5.10 update is building with CONFIG_RCU_SCALE_TEST disabled, I will update once the build is complete. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904906 Title: 5.10 kernel fails to boot with secure boot disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1904906/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906404] Re: New upstream release 2020.11.20
Tested on x/b/f/g: 1. Install package from -proposed. 2. Reload the regdb or reboot, depending on kernel/iw versions. 3. Query current reg domain. 4. Change to a different reg domain. 5. Query again to confirm the reg domain has changed. 6. Check kernel/crda logs for errors. Testing passed in all cases with no errors in the logs. ** Tags removed: verification-needed-bionic verification-needed-focal verification-needed-groovy verification-needed-xenial ** Tags added: verification-done-bionic verification-done-focal verification-done-groovy verification-done-xenial ** Changed in: wireless-regdb (Ubuntu Hirsute) Status: Fix Committed => Fix Released ** Also affects: wireless-regdb (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: wireless-regdb (Ubuntu Precise) Importance: Undecided Status: New ** Changed in: wireless-regdb (Ubuntu Precise) Status: New => In Progress ** Changed in: wireless-regdb (Ubuntu Trusty) Status: New => In Progress ** Changed in: wireless-regdb (Ubuntu Precise) Importance: Undecided => Medium ** Changed in: wireless-regdb (Ubuntu Precise) Assignee: (unassigned) => Seth Forshee (sforshee) ** Changed in: wireless-regdb (Ubuntu Trusty) Importance: Undecided => Medium ** Changed in: wireless-regdb (Ubuntu Trusty) Assignee: (unassigned) => Seth Forshee (sforshee) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906404 Title: New upstream release 2020.11.20 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wireless-regdb/+bug/1906404/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906404] Re: New upstream release 2020.11.20
** Description changed: - New upstream version, bringing in updated regulatory rules for various - jurisdictions. + [Impact] + + New upstream release. This is a database of wireless regulations, and + should updated in all releases to ensure users have the most up-to-date + regulatory information. + + [Test Case] + + Following reboot after installing the new database, it should be + possible to query and change the regulatory domain using 'iw reg get' + and 'iw reg set'. + + [Where problems could occur] + + If crda or the kernel is unable to use the new database, users may be + stuck using the default "world" regulatory domain which is quite + restrictive, therefore they may be unable to use wireless channels that + they were able to use previously. Regulatory rules may have also changed + for the user's region, which could also make some channels unusable, but + this would not be a bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906404 Title: New upstream release 2020.11.20 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wireless-regdb/+bug/1906404/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906404] [NEW] New upstream release 2020.11.20
Public bug reported:
New upstream version, bringing in updated regulatory rules for various
jurisdictions.
** Affects: wireless-regdb (Ubuntu)
Importance: Medium
Assignee: Seth Forshee (sforshee)
Status: Fix Committed
** Affects: wireless-regdb (Ubuntu Xenial)
Importance: Medium
Assignee: Seth Forshee (sforshee)
Status: Confirmed
** Affects: wireless-regdb (Ubuntu Bionic)
Importance: Medium
Assignee: Seth Forshee (sforshee)
Status: Confirmed
** Affects: wireless-regdb (Ubuntu Focal)
Importance: Medium
Assignee: Seth Forshee (sforshee)
Status: Confirmed
** Affects: wireless-regdb (Ubuntu Groovy)
Importance: Medium
Assignee: Seth Forshee (sforshee)
Status: Confirmed
** Affects: wireless-regdb (Ubuntu Hirsute)
Importance: Medium
Assignee: Seth Forshee (sforshee)
Status: Fix Committed
** Also affects: wireless-regdb (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects: wireless-regdb (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: wireless-regdb (Ubuntu Hirsute)
Importance: Undecided
Assignee: Seth Forshee (sforshee)
Status: In Progress
** Also affects: wireless-regdb (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: wireless-regdb (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: wireless-regdb (Ubuntu Hirsute)
Status: In Progress => Fix Committed
** Changed in: wireless-regdb (Ubuntu Hirsute)
Importance: Undecided => Medium
** Changed in: wireless-regdb (Ubuntu Groovy)
Status: New => Confirmed
** Changed in: wireless-regdb (Ubuntu Focal)
Status: New => Confirmed
** Changed in: wireless-regdb (Ubuntu Bionic)
Status: New => Confirmed
** Changed in: wireless-regdb (Ubuntu Xenial)
Status: New => Confirmed
** Changed in: wireless-regdb (Ubuntu Groovy)
Importance: Undecided => Medium
** Changed in: wireless-regdb (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: wireless-regdb (Ubuntu Bionic)
Importance: Undecided => Medium
** Changed in: wireless-regdb (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: wireless-regdb (Ubuntu Groovy)
Assignee: (unassigned) => Seth Forshee (sforshee)
** Changed in: wireless-regdb (Ubuntu Focal)
Assignee: (unassigned) => Seth Forshee (sforshee)
** Changed in: wireless-regdb (Ubuntu Bionic)
Assignee: (unassigned) => Seth Forshee (sforshee)
** Changed in: wireless-regdb (Ubuntu Xenial)
Assignee: (unassigned) => Seth Forshee (sforshee)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906404
Title:
New upstream release 2020.11.20
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wireless-regdb/+bug/1906404/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904906] Re: 5.10 kernel fails to boot with secure boot disabled
That config shouldn't be on at all, it's just a performance test that isn't likely to be of interest to users. I agree it's weird though -- it shouldn't cause boot problems, as it shouldn't be loaded automatically (the module doesn't even have any modaliases). Regardless, I will disable the option. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904906 Title: 5.10 kernel fails to boot with secure boot disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1904906/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905195] Re: package linux-firmware 1.187.4 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1
>From the dpkg terminal log:
update-initramfs: Generating /boot/initrd.img-4.15.0-125-generic
Fatal: raid_setup: stat("/dev/disk/by-id/ata-TOSHIBA_MK5055GSX_Z9K8SF7NS")
run-parts: /etc/initramfs/post-update.d//runlilo exited with return code 1
dpkg: error processing package linux-firmware (--configure):
installed linux-firmware package post-installation script subprocess returned
error exit status 1
So the error is coming from a lilo script run when generating the
initramfs. I'm not sure what reason you might have for having lilo
installed, but if it's not needed you might consider removing it.
** Also affects: lilo (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905195
Title:
package linux-firmware 1.187.4 failed to install/upgrade: installed
linux-firmware package post-installation script subprocess returned
error exit status 1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lilo/+bug/1905195/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905195] Re: package linux-firmware 1.187.4 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1
Added lilo as an affected package. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905195 Title: package linux-firmware 1.187.4 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lilo/+bug/1905195/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905770] Re: package linux-firmware 1.187.5 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1
*** This bug is a duplicate of bug 1905195 *** https://bugs.launchpad.net/bugs/1905195 ** This bug has been marked a duplicate of bug 1905195 package linux-firmware 1.187.4 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905770 Title: package linux-firmware 1.187.5 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1905770/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905787] Re: package linux-firmware 1.187.6 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1
*** This bug is a duplicate of bug 1905195 *** https://bugs.launchpad.net/bugs/1905195 ** This bug has been marked a duplicate of bug 1905195 package linux-firmware 1.187.4 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905787 Title: package linux-firmware 1.187.6 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1905787/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904906] Re: 5.10 kernel fails to boot with secure boot disabled
I also note that you are testing with 5.10.0-0, which was based on 5.10-rc1. We have 5.10.0-4 in the ppa now based on -rc4, it is built for hirsute and not groovy though. I'd recommend trying that version to see if there was an upstream bug which has already been fixed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904906 Title: 5.10 kernel fails to boot with secure boot disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1904906/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904906] Re: 5.10 kernel fails to boot with secure boot disabled
I've attached our configs for the Ubuntu 5.8 and 5.10 kernels along with a diff between these configs. I didn't see anything in the diff which looked like an obvious candidate for causing the boot problems. Please let me know if you see something there which should be changed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904906 Title: 5.10 kernel fails to boot with secure boot disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1904906/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904906] Re: 5.10 kernel fails to boot with secure boot disabled
** Patch added: "Diff between Ubuntu 5.8 and 5.10 ppc64el kernel configs" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904906/+attachment/5436111/+files/ppc64el-config.flavour.generic.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904906 Title: 5.10 kernel fails to boot with secure boot disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1904906/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
