[Kernel-packages] [Bug 1933716] Re: Black screen on boot after stable update
I have hit this bug as well. Please let me know if there is any information I can provide. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1933716 Title: Black screen on boot after stable update Status in linux package in Ubuntu: New Bug description: After kernel update from 5.11.0-18-generic to 5.11.0-22-generic system boots into black screen. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-18-generic 5.11.0-18.19 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marcin 1374 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jun 26 11:55:00 2021 InstallationDate: Installed on 2021-05-02 (55 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: HP HP Pavilion Laptop 15-eg0xxx ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic root=UUID=9625a19f-eeea-4a92-ab4b-1549d4950f3b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-18-generic N/A linux-backports-modules-5.11.0-18-generic N/A linux-firmware 1.197 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/17/2021 dmi.bios.release: 15.12 dmi.bios.vendor: Insyde dmi.bios.version: F.12 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 87CB dmi.board.vendor: HP dmi.board.version: 34.27 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 34.27 dmi.modalias: dmi:bvnInsyde:bvrF.12:bd03/17/2021:br15.12:efr34.27:svnHP:pnHPPavilionLaptop15-eg0xxx:pvrType1ProductConfigId:rvnHP:rn87CB:rvr34.27:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-eg0xxx dmi.product.sku: 2Q2T4EA#AKD dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933716/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1933938] Re: Missing CNVi firmware for Intel AX211/AX201 on ADL
With CONFIG_IWLWIFI_DEBUG enabled. ** Attachment added: "dmesg.SDP-ADL-S-BETA-99ACNN-202105-29062.5.13.0-rc6-debug-ff8744b5eb11.iwlwifi-fw-64.97bbee0a.0" https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1933938/+attachment/5508531/+files/dmesg.SDP-ADL-S-BETA-99ACNN-202105-29062.5.13.0-rc6-debug-ff8744b5eb11.iwlwifi-fw-64.97bbee0a.0 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1933938 Title: Missing CNVi firmware for Intel AX211/AX201 on ADL Status in HWE Next: New Status in intel: New Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Focal: New Status in linux-firmware source package in Impish: New Bug description: * PCI [8086:7af0] Subsystem [8086:4090] (AX211) * WiFi: iwlwifi-so-a0-gf-a0-* * BT: intel/ibt-1040-0041.sfi * PCI [8086:7af0] Subsystem [8086:4070] (AX201) * WiFi: iwlwifi-so-a0-hr-b0-* * BT: ??? To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1933938/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1928890] Re: vrf_route_leaking in net from ubuntu_kernel_selftests linux ADT test failure with linux/5.11.0-18.19 (Ping received ICMP Packet too big)
5.10.0-1035.36 OEM node vought ** Tags added: sru-20210621 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1928890 Title: vrf_route_leaking in net from ubuntu_kernel_selftests linux ADT test failure with linux/5.11.0-18.19 (Ping received ICMP Packet too big) Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.10 package in Ubuntu: New Status in linux source package in Hirsute: New Status in linux-oem-5.10 source package in Hirsute: New Bug description: This is a scripted bug report about ADT failures while running linux tests for linux/5.11.0-18.19 on hirsute. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Not a regression. Found to occur previously on hirsute/linux 5.11.0-14.15 Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/amd64/l/linux/20210515_005957_75e5a@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/arm64/l/linux/20210513_203508_96fd3@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/ppc64el/l/linux/20210513_163708_c0203@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/s390x/l/linux/20210513_144454_54b04@/log.gz 00:09:30 DEBUG| [stdout] # selftests: net: vrf_route_leaking.sh 00:09:30 DEBUG| [stdout] # 00:09:30 DEBUG| [stdout] # ### 00:09:30 DEBUG| [stdout] # IPv4 (sym route): VRF ICMP ttl error route lookup ping 00:09:30 DEBUG| [stdout] # ### 00:09:30 DEBUG| [stdout] # 00:09:32 DEBUG| [stdout] # TEST: Basic IPv4 connectivity [ OK ] 00:09:32 DEBUG| [stdout] # TEST: Ping received ICMP ttl exceeded [ OK ] 00:09:32 DEBUG| [stdout] # 00:09:32 DEBUG| [stdout] # ### 00:09:32 DEBUG| [stdout] # IPv4 (sym route): VRF ICMP error route lookup traceroute 00:09:32 DEBUG| [stdout] # ### 00:09:32 DEBUG| [stdout] # 00:09:32 DEBUG| [stdout] # SKIP: Could not run IPV4 test without traceroute 00:09:32 DEBUG| [stdout] # 00:09:32 DEBUG| [stdout] # ### 00:09:32 DEBUG| [stdout] # IPv4 (sym route): VRF ICMP fragmentation error route lookup ping 00:09:32 DEBUG| [stdout] # ### 00:09:32 DEBUG| [stdout] # 00:09:34 DEBUG| [stdout] # TEST: Basic IPv4 connectivity [ OK ] 00:09:34 DEBUG| [stdout] # TEST: Ping received ICMP Frag needed [ OK ] 00:09:34 DEBUG| [stdout] # 00:09:34 DEBUG| [stdout] # ### 00:09:34 DEBUG| [stdout] # IPv4 (asym route): VRF ICMP ttl error route lookup ping 00:09:34 DEBUG| [stdout] # ### 00:09:34 DEBUG| [stdout] # 00:09:36 DEBUG| [stdout] # TEST: Basic IPv4 connectivity [ OK ] 00:09:36 DEBUG| [stdout] # TEST: Ping received ICMP ttl exceeded [ OK ] 00:09:36 DEBUG| [stdout] # 00:09:36 DEBUG| [stdout] # ### 00:09:36 DEBUG| [stdout] # IPv4 (asym route): VRF ICMP error route lookup traceroute 00:09:36 DEBUG| [stdout] # ### 00:09:36 DEBUG| [stdout] # 00:09:36 DEBUG| [stdout] # SKIP: Could not run IPV4 test without traceroute 00:09:36 DEBUG| [stdout] # 00:09:36 DEBUG| [stdout] # ### 00:09:36 DEBUG| [stdout] # IPv6 (sym route): VRF ICMP ttl error route lookup ping 00:09:36 DEBUG| [stdout] # ### 00:09:36 DEBUG| [stdout] # 00:09:40 DEBUG| [stdout] # TEST: Basic IPv6 connectivity [FAIL] 00:09:40 DEBUG| [stdout] # TEST: Ping received ICMP Hop limit [ OK ] 00:09:40 DEBUG| [stdout] # 00:09:40 DEBUG| [stdout] # ### 00:09:40 DEBUG| [stdout] # IPv6 (sym route): VRF ICMP error route lookup traceroute 00:09:40 DEBUG| [stdout] #
[Kernel-packages] [Bug 1934428] [NEW] Request to pull-in new PERC11 PCI-id from upstream
Private bug reported: Request to pull-in new PERC11 PCI-ids from upstream. PERC-11 are shipping cards supported since Ubuntu 20.04 onwards, however new form factors are being launched by Dell which are having new subsystem-ids. Request is to pull these new pci-ids into future releases Ubuntu 20.04. PCI-id details: 1000:00e6:1028:2171 PERC H750 Mini 1000:00e6:1028:2172 PERC H355 Adapter 1000:00e6:1028:2173 PERC H355 Front 1000:00e6:1028:2174 PERC H350 Mini 1000:00e6:1028:2176 PERC H750 Adapter 1000:00e6:1028:2177 PERC H350 Adapter External links: https://pci-ids.ucw.cz/read/PC/1000/10e2 https://pci-ids.ucw.cz/v2.2/pci.ids ** Affects: dellserver Importance: Undecided Status: New ** Affects: hwdata (Ubuntu) Importance: Undecided Status: New ** Information type changed from Public to Private ** Also affects: dellserver Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to hwdata in Ubuntu. https://bugs.launchpad.net/bugs/1934428 Title: Request to pull-in new PERC11 PCI-id from upstream Status in dellserver: New Status in hwdata package in Ubuntu: New Bug description: Request to pull-in new PERC11 PCI-ids from upstream. PERC-11 are shipping cards supported since Ubuntu 20.04 onwards, however new form factors are being launched by Dell which are having new subsystem-ids. Request is to pull these new pci-ids into future releases Ubuntu 20.04. PCI-id details: 1000:00e6:1028:2171 PERC H750 Mini 1000:00e6:1028:2172 PERC H355 Adapter 1000:00e6:1028:2173 PERC H355 Front 1000:00e6:1028:2174 PERC H350 Mini 1000:00e6:1028:2176 PERC H750 Adapter 1000:00e6:1028:2177 PERC H350 Adapter External links: https://pci-ids.ucw.cz/read/PC/1000/10e2 https://pci-ids.ucw.cz/v2.2/pci.ids To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1934428/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932124] Re: Add WWAN framework and drivers support
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel in Ubuntu. https://bugs.launchpad.net/bugs/1932124 Title: Add WWAN framework and drivers support Status in HWE Next: New Status in linux-intel package in Ubuntu: Fix Committed Bug description: [SRU Justification] [Impact] The Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem and Foxconn SDX55 T99W175 5G sub6 PCIE Modem are not supported in 5.11 kernel yet. The new WWAN framework and driver support are required to be backported to detect and control the new WWAN modules. [Fix] Backport the WWAN framework and drivers support from mainline kernel 5.13. [Test Case] Verify whether the Quectel/Foxconn WWAN module are detected or not. And use either `mmcli` commands or NetworkSettings Panel to test the connection. [Where problem could occur] Since the WWAN framework is totally new which makes use of the existing MHI bus drivers and protocols, it should be compatible with old WWAN modules. The regression can be considered as low. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1932124/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934424] [NEW] kernel NULL pointer dereference during xen hibernation
Public bug reported: Encountered the following panic while doing hibernation/resume testing with linux-aws 5.8 on Focal on an m3.xlarge (xen) instance type: [ 594.291317] ACPI: Hardware changed while hibernated, success doubtful! [ 594.411609] BUG: kernel NULL pointer dereference, address: 01f4 [ 594.424658] #PF: supervisor write access in kernel mode [ 594.424660] #PF: error_code(0x0002) - not-present page [ 594.424661] PGD 0 P4D 0 [ 594.424665] Oops: 0002 [#1] SMP PTI [ 594.424668] CPU: 3 PID: 362 Comm: systemd-timesyn Not tainted 5.8.0-1036-aws #38~20.04.1-Ubuntu [ 594.424669] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006 [ 594.424675] RIP: 0010:_raw_spin_lock_irqsave+0x23/0x40 [ 594.424678] Code: 0f 1f 80 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 41 54 9c 58 0f 1f 44 00 00 49 89 c4 fa 66 0f 1f 44 00 00 31 c0 ba 01 00 00 00 0f b1 17 75 07 4c 89 e0 41 5c 5d c3 89 c6 e8 e9 d1 56 ff 66 90 [ 594.424679] RSP: 0018:c94e3848 EFLAGS: 00010046 [ 594.424680] RAX: RBX: 8883bcc0d000 RCX: 0e02 [ 594.424681] RDX: 0001 RSI: RDI: 01f4 [ 594.424682] RBP: c94e3850 R08: 8883b90b5ec0 R09: 005a [ 594.424683] R10: c94e3910 R11: R12: 0206 [ 594.424684] R13: ea000ee42d40 R14: R15: 0001 [ 594.424686] FS: 7f65ba055980() GS:8883c0ac() knlGS: [ 594.424687] CS: 0010 DS: ES: CR0: 80050033 [ 594.424688] CR2: 01f4 CR3: 0003b99f0001 CR4: 001606e0 [ 594.424692] Call Trace: [ 594.424699] xennet_start_xmit+0x158/0x570 [ 594.424704] dev_hard_start_xmit+0x91/0x1f0 [ 594.424706] ? validate_xmit_skb+0x300/0x340 [ 594.424710] sch_direct_xmit+0x113/0x340 [ 594.424712] __dev_queue_xmit+0x57c/0x8e0 [ 594.424714] ? neigh_add_timer+0x37/0x60 [ 594.424716] dev_queue_xmit+0x10/0x20 [ 594.424717] neigh_resolve_output+0x112/0x1c0 [ 594.424721] ip_finish_output2+0x19b/0x590 [ 594.424723] __ip_finish_output+0xc8/0x1e0 [ 594.424725] ip_finish_output+0x2d/0xb0 [ 594.424728] ip_output+0x7a/0xf0 [ 594.424730] ? __ip_finish_output+0x1e0/0x1e0 [ 594.424732] ip_local_out+0x3d/0x50 [ 594.424734] ip_send_skb+0x19/0x40 [ 594.424737] udp_send_skb.isra.0+0x165/0x390 [ 594.424739] udp_sendmsg+0xb0e/0xd50 [ 594.424742] ? ip_reply_glue_bits+0x50/0x50 [ 594.424747] ? delete_from_swap_cache+0x6a/0x90 [ 594.424750] ? _cond_resched+0x19/0x30 [ 594.424754] ? aa_sk_perm+0x43/0x1b0 [ 594.424757] inet_sendmsg+0x65/0x70 [ 594.424759] ? security_socket_sendmsg+0x35/0x50 [ 594.424760] ? inet_sendmsg+0x65/0x70 [ 594.424764] sock_sendmsg+0x5e/0x70 [ 594.424766] __sys_sendto+0x113/0x190 [ 594.424770] ? __secure_computing+0x42/0xe0 [ 594.424774] ? syscall_trace_enter+0x10d/0x280 [ 594.424777] __x64_sys_sendto+0x29/0x30 [ 594.424781] do_syscall_64+0x49/0xc0 [ 594.424783] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 594.424785] RIP: 0033:0x7f65baee4844 [ 594.424788] Code: 42 3f f7 ff 44 8b 4c 24 2c 4c 8b 44 24 20 89 c5 44 8b 54 24 28 48 8b 54 24 18 b8 2c 00 00 00 48 8b 74 24 10 8b 7c 24 08 0f 05 <48> 3d 00 f0 ff ff 77 30 89 ef 48 89 44 24 08 e8 68 3f f7 ff 48 8b [ 594.424789] RSP: 002b:7ffe9b5fd3a0 EFLAGS: 0293 ORIG_RAX: 002c [ 594.424790] RAX: ffda RBX: 7ffe9b5fd4e0 RCX: 7f65baee4844 [ 594.424791] RDX: 0030 RSI: 7ffe9b5fd3f0 RDI: 0010 [ 594.424792] RBP: R08: 560426541678 R09: 0010 [ 594.424793] R10: 0040 R11: 0293 R12: [ 594.424794] R13: 7ffe9b5fd3e4 R14: 0068 R15: [ 594.424796] Modules linked in: btrfs blake2b_generic xor raid6_pq ufs msdos xfs libcrc32c dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd psmouse cryptd input_leds glue_helper serio_raw floppy sch_fq_codel drm ip_tables x_tables autofs4 [ 594.424813] CR2: 01f4 [ 594.424821] ---[ end trace bb5f35055c1a8060 ]--- [ 594.424822] RIP: 0010:_raw_spin_lock_irqsave+0x23/0x40 [ 594.424824] Code: 0f 1f 80 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 41 54 9c 58 0f 1f 44 00 00 49 89 c4 fa 66 0f 1f 44 00 00 31 c0 ba 01 00 00 00 0f b1 17 75 07 4c 89 e0 41 5c 5d c3 89 c6 e8 e9 d1 56 ff 66 90 [ 594.424824] RSP: 0018:c94e3848 EFLAGS: 00010046 [ 594.424825] RAX: RBX: 8883bcc0d000 RCX: 0e02 [ 594.424826] RDX: 0001 RSI: RDI: 01f4 [ 594.424826] RBP: c94e3850 R08: 8883b90b5ec0 R09: 005a [ 594.424827] R10: c94e3910 R11: R12: 0206 [ 594.424827] R13: ea000ee42d40 R14: R15: 0001 [ 594.424828] FS: 7f65ba055980()
[Kernel-packages] [Bug 1926548] Re: The gatt protocol has out-of-bounds read that leads to information leakage
bluez (5.53-0ubuntu3.2) focal-security; urgency=medium
* SECURITY UPDATE: secure pairing passkey brute force
- debian/patches/CVE-2020-26558.patch: fix not properly checking for
secure flags in src/shared/att-types.h, src/shared/gatt-server.c.
- CVE-2020-26558
* SECURITY UPDATE: DoS or code execution via double-free
- debian/patches/CVE-2020-27153.patch: fix possible crash on disconnect
in src/shared/att.c.
- CVE-2020-27153
* SECURITY UPDATE: info disclosure via out of bounds read
- debian/patches/CVE-2021-3588.patch: when client features is read
check if the offset is within the cli_feat bounds in
src/gatt-database.c.
- CVE-2021-3588
-- Marc Deslauriers Wed, 09 Jun 2021
11:06:38 -0400
** Changed in: bluez (Ubuntu Focal)
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1926548
Title:
The gatt protocol has out-of-bounds read that leads to information
leakage
Status in Bluez Utilities:
Fix Released
Status in bluez package in Ubuntu:
Fix Released
Status in bluez source package in Focal:
Fix Released
Status in bluez source package in Groovy:
Fix Released
Status in bluez source package in Hirsute:
Fix Released
Status in bluez source package in Impish:
Fix Released
Bug description:
I installed the latest bluez 5.53-0ubuntu3 version using apt-get install. It
seems that this vulnerability was silently fixed in the latest bluez5.8, and
the cve number was not assigned.
But this vulnerability now affects the latest ubuntu system
This vulnerability allows an attacker to remotely obtain most of the contents
of the heap without authentication.
The vulnerability code is stored in cli_feat_read_cb, this function does not
verify the offset parameter
The vulnerability code is as follows
gatt-database.c
1054：static void cli_feat_read_cb(struct gatt_db_attribute *attrib,
unsigned int id, uint16_t offset,
uint8_t opcode, struct bt_att *att,
void *user_data){
...
len = sizeof(state->cli_feat)-offset;
value = len? >cli_feat[offset]: NULL;
done:
gatt_db_attribute_read_result(attrib, id, ecode, value, len);
}
len will become very large due to integer overflow, so that a message of mtu
(0x90) size will be sent later
The message content is the buffer pointed to by value, which can be most
addresses on the heap
poc is very simple, the core is this line of code
memcpy([0],"\x0c\x0b\x00\x0d\x00",5);
0xc stands for read
\x0b\x00 represents the handle of the client feature, which can be obtained
through the find info message, which seems to be 0b by default
\x0d\x00 is offset0xd
this vulnerability is serious
I want to apply for a cve number, although this has been silently fixed in
the latest version
To manage notifications about this bug go to:
https://bugs.launchpad.net/bluez/+bug/1926548/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926548] Re: The gatt protocol has out-of-bounds read that leads to information leakage
bluez (5.55-0ubuntu1.2) groovy-security; urgency=medium
* SECURITY UPDATE: secure pairing passkey brute force
- debian/patches/CVE-2020-26558.patch: fix not properly checking for
secure flags in src/shared/att-types.h, src/shared/gatt-server.c.
- CVE-2020-26558
* SECURITY UPDATE: info disclosure via out of bounds read
- debian/patches/CVE-2021-3588.patch: when client features is read
check if the offset is within the cli_feat bounds in
src/gatt-database.c.
- CVE-2021-3588
-- Marc Deslauriers Wed, 09 Jun 2021
11:01:25 -0400
** Also affects: bluez (Ubuntu Groovy)
Importance: Undecided
Status: New
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-26558
** Changed in: bluez (Ubuntu Groovy)
Status: New => Fix Released
** Also affects: bluez (Ubuntu Focal)
Importance: Undecided
Status: New
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-27153
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1926548
Title:
The gatt protocol has out-of-bounds read that leads to information
leakage
Status in Bluez Utilities:
Fix Released
Status in bluez package in Ubuntu:
Fix Released
Status in bluez source package in Focal:
Fix Released
Status in bluez source package in Groovy:
Fix Released
Status in bluez source package in Hirsute:
Fix Released
Status in bluez source package in Impish:
Fix Released
Bug description:
I installed the latest bluez 5.53-0ubuntu3 version using apt-get install. It
seems that this vulnerability was silently fixed in the latest bluez5.8, and
the cve number was not assigned.
But this vulnerability now affects the latest ubuntu system
This vulnerability allows an attacker to remotely obtain most of the contents
of the heap without authentication.
The vulnerability code is stored in cli_feat_read_cb, this function does not
verify the offset parameter
The vulnerability code is as follows
gatt-database.c
1054：static void cli_feat_read_cb(struct gatt_db_attribute *attrib,
unsigned int id, uint16_t offset,
uint8_t opcode, struct bt_att *att,
void *user_data){
...
len = sizeof(state->cli_feat)-offset;
value = len? >cli_feat[offset]: NULL;
done:
gatt_db_attribute_read_result(attrib, id, ecode, value, len);
}
len will become very large due to integer overflow, so that a message of mtu
(0x90) size will be sent later
The message content is the buffer pointed to by value, which can be most
addresses on the heap
poc is very simple, the core is this line of code
memcpy([0],"\x0c\x0b\x00\x0d\x00",5);
0xc stands for read
\x0b\x00 represents the handle of the client feature, which can be obtained
through the find info message, which seems to be 0b by default
\x0d\x00 is offset0xd
this vulnerability is serious
I want to apply for a cve number, although this has been silently fixed in
the latest version
To manage notifications about this bug go to:
https://bugs.launchpad.net/bluez/+bug/1926548/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934414] Re: test_bpf.sh from ubuntu_kernel_selftests.net from linux ADT test failure with linux/4.15.0-149.153
Also seeing this failure through regression testing on 4.15.0-149.153 i386 lowlatency and generic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1934414 Title: test_bpf.sh from ubuntu_kernel_selftests.net from linux ADT test failure with linux/4.15.0-149.153 Status in linux package in Ubuntu: New Bug description: This is a scripted bug report about ADT failures while running linux tests for linux/4.15.0-149.153 on bionic. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: i386: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/i386/l/linux/20210702_010055_445cd@/log.gz 03:37:02 DEBUG| [stdout] selftests: test_bpf.sh 03:37:02 DEBUG| [stdout] 03:37:03 ERROR| [stderr] Segmentation fault 03:37:03 DEBUG| [stdout] test_bpf: [FAIL] 03:37:03 DEBUG| [stdout] not ok 1..8 selftests: test_bpf.sh [FAIL] 03:37:03 DEBUG| [stdout] selftests: netdevice.sh 03:37:03 DEBUG| [stdout] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934414/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934414] Re: linux ADT test failure with linux/4.15.0-149.153
** Description changed: This is a scripted bug report about ADT failures while running linux tests for linux/4.15.0-149.153 on bionic. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: - amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/amd64/l/linux/20210625_024137_c7e43@/log.gz - i386: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/i386/l/linux/20210702_010055_445cd@/log.gz - ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/ppc64el/l/linux/20210625_011348_1dfec@/log.gz + i386: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/i386/l/linux/20210702_010055_445cd@/log.gz ** Summary changed: - linux ADT test failure with linux/4.15.0-149.153 + test_bpf.sh from ubuntu_kernel_selftests.net from linux ADT test failure with linux/4.15.0-149.153 ** Description changed: This is a scripted bug report about ADT failures while running linux tests for linux/4.15.0-149.153 on bionic. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: i386: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/i386/l/linux/20210702_010055_445cd@/log.gz + + + 03:37:02 DEBUG| [stdout] selftests: test_bpf.sh + 03:37:02 DEBUG| [stdout] + 03:37:03 ERROR| [stderr] Segmentation fault + 03:37:03 DEBUG| [stdout] test_bpf: [FAIL] + 03:37:03 DEBUG| [stdout] not ok 1..8 selftests: test_bpf.sh [FAIL] + 03:37:03 DEBUG| [stdout] selftests: netdevice.sh + 03:37:03 DEBUG| [stdout] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1934414 Title: test_bpf.sh from ubuntu_kernel_selftests.net from linux ADT test failure with linux/4.15.0-149.153 Status in linux package in Ubuntu: New Bug description: This is a scripted bug report about ADT failures while running linux tests for linux/4.15.0-149.153 on bionic. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: i386: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/i386/l/linux/20210702_010055_445cd@/log.gz 03:37:02 DEBUG| [stdout] selftests: test_bpf.sh 03:37:02 DEBUG| [stdout] 03:37:03 ERROR| [stderr] Segmentation fault 03:37:03 DEBUG| [stdout] test_bpf: [FAIL] 03:37:03 DEBUG| [stdout] not ok 1..8 selftests: test_bpf.sh [FAIL] 03:37:03 DEBUG| [stdout] selftests: netdevice.sh 03:37:03 DEBUG| [stdout] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934414/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1933950] Re: [i915] Black screen when I login in using kernel 5.8.0-59 but not 5.8.0-25
OK, that's progress. Please open two new bugs to cover those issues: * Nvidia driver 460 fails in install on 21.04 * Brightness control is missing on HP Pavilion Gaming Laptop 15-dk0xxx Assuming the Intel GPU is wired to the laptop screen those are different bugs. ** Changed in: linux (Ubuntu) Status: Incomplete => Won't Fix ** Changed in: xorg-server (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1933950 Title: [i915] Black screen when I login in using kernel 5.8.0-59 but not 5.8.0-25 Status in linux package in Ubuntu: Won't Fix Status in xorg-server package in Ubuntu: Won't Fix Bug description: There was also no brightness setting. I have reinstalled ubuntu 3 times already. This happened after the updates on June 24th. The only solution is not to install ubuntu updates. As soon as I install updates, there is a black screen. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.80 Fri May 7 06:55:54 UTC 2021 GCC version: gcc version 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.10) ApportVersion: 2.20.11-0ubuntu50.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jun 29 11:22:08 2021 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu DkmsStatus: nvidia, 460.80, 5.8.0-25-generic, x86_64: installed nvidia, 460.80, 5.8.0-59-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics 630 (Mobile) [103c:85fb] NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] [10de:2191] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company TU116M [GeForce GTX 1660 Ti Mobile] [103c:85fb] InstallationDate: Installed on 2021-06-25 (3 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: HP HP Pavilion Gaming Laptop 15-dk0xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic root=UUID=a7c41e63-e7ea-43e0-9de0-55322f489ee5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2020 dmi.bios.release: 15.33 dmi.bios.vendor: Insyde dmi.bios.version: F.33 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 85FB dmi.board.vendor: HP dmi.board.version: 42.42 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 42.42 dmi.modalias: dmi:bvnInsyde:bvrF.33:bd07/16/2020:br15.33:efr42.42:svnHP:pnHPPavilionGamingLaptop15-dk0xxx:pvrType1ProductConfigId:rvnHP:rn85FB:rvr42.42:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Gaming Laptop 15-dk0xxx dmi.product.sku: 2C7M8EA#ACB dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933950/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off
^^^ Note bug 1933221 is really a duplicate of this one. That's why it's fix released. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1926062 Title: [hirsute/impish] Can't turn bluetooth on again after turning it off Status in Bluez Utilities: Fix Released Status in GNOME Bluetooth: Unknown Status in OEM Priority Project: New Status in bluez package in Ubuntu: Fix Released Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in bluez source package in Focal: Fix Released Status in bluez source package in Hirsute: Fix Released Status in bluez source package in Impish: Fix Released Status in gnome-settings-daemon source package in Impish: Fix Released Bug description: [Impact] On/off of Bluetooth in gnome-control-center will not work properly in kernels 5.11 (approximately) onward. Devices are not refreshed in the list anymore. [Test Plan] 1. Open gnome-control-center and select Bluetooth 2. Turn off Bluetooth via UI 3. Turn on Bluetooth via UI Expect: Device list appears, so Bluetooth really is on. [Where problems could occur] Since the fix involves the 'rfkill' logic it has the potential to affect any Bluetooth or Wifi on/off setting. [Other info] Upstream bug in gnome-bluetooth: https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 Discussion in linux-bluetooth: https://marc.info/?t=16200475893=1=2 [Original bug report] When ever i Turn on my system or restart bluetooth is open any it connects to any device. But when i turn off bluetooth and try to turn it on again. it neither turns on nor scans/connects to any device. This is happening since I updated my system to ubuntu 21.04 LTS Bluetooth: hci0: HCI reset during shutdown failed ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Apr 25 15:09:23 2021 InstallationDate: Installed on 2020-12-15 (130 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 80TR ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago) dmi.bios.date: 07/31/2017 dmi.bios.release: 1.29 dmi.bios.vendor: LENOVO dmi.bios.version: 3UCN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Nano 5B1 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 110-15AST dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST: dmi.product.family: IDEAPAD dmi.product.name: 80TR dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST dmi.product.version: Lenovo ideapad 110-15AST dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: C8:3D:D4:84:E0:06 ACL MTU: 820:8 SCO MTU: 255:16 DOWN RX bytes:744804 acl:76 sco:0 events:105989 errors:0 TX bytes:51871528 acl:113157 sco:0 commands:192 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1926062/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off
This bug was fixed in the package bluez - 5.56-0ubuntu4.2 --- bluez (5.56-0ubuntu4.2) hirsute; urgency=medium * debian/patches/0001-fix-reading-from-rfkill-socket.patch: - fix reading from rfkill socket (lp: #1933221) -- Andy Chi Tue, 22 Jun 2021 08:07:12 + ** Changed in: bluez (Ubuntu Hirsute) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1926062 Title: [hirsute/impish] Can't turn bluetooth on again after turning it off Status in Bluez Utilities: Fix Released Status in GNOME Bluetooth: Unknown Status in OEM Priority Project: New Status in bluez package in Ubuntu: Fix Released Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in bluez source package in Focal: Fix Released Status in bluez source package in Hirsute: Fix Released Status in bluez source package in Impish: Fix Released Status in gnome-settings-daemon source package in Impish: Fix Released Bug description: [Impact] On/off of Bluetooth in gnome-control-center will not work properly in kernels 5.11 (approximately) onward. Devices are not refreshed in the list anymore. [Test Plan] 1. Open gnome-control-center and select Bluetooth 2. Turn off Bluetooth via UI 3. Turn on Bluetooth via UI Expect: Device list appears, so Bluetooth really is on. [Where problems could occur] Since the fix involves the 'rfkill' logic it has the potential to affect any Bluetooth or Wifi on/off setting. [Other info] Upstream bug in gnome-bluetooth: https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 Discussion in linux-bluetooth: https://marc.info/?t=16200475893=1=2 [Original bug report] When ever i Turn on my system or restart bluetooth is open any it connects to any device. But when i turn off bluetooth and try to turn it on again. it neither turns on nor scans/connects to any device. This is happening since I updated my system to ubuntu 21.04 LTS Bluetooth: hci0: HCI reset during shutdown failed ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Apr 25 15:09:23 2021 InstallationDate: Installed on 2020-12-15 (130 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 80TR ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago) dmi.bios.date: 07/31/2017 dmi.bios.release: 1.29 dmi.bios.vendor: LENOVO dmi.bios.version: 3UCN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Nano 5B1 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 110-15AST dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST: dmi.product.family: IDEAPAD dmi.product.name: 80TR dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST dmi.product.version: Lenovo ideapad 110-15AST dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: C8:3D:D4:84:E0:06 ACL MTU: 820:8 SCO MTU: 255:16 DOWN RX bytes:744804 acl:76 sco:0 events:105989 errors:0 TX bytes:51871528 acl:113157 sco:0 commands:192 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1926062/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off
This bug was fixed in the package bluez - 5.53-0ubuntu3.3 --- bluez (5.53-0ubuntu3.3) focal; urgency=medium * debian/patches/0001-fix-reading-from-rfkill-socket.patch: - fix reading from rfkill socket (lp: #1933221) -- Andy Chi Tue, 22 Jun 2021 14:27:12 +0800 ** Changed in: bluez (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1926062 Title: [hirsute/impish] Can't turn bluetooth on again after turning it off Status in Bluez Utilities: Fix Released Status in GNOME Bluetooth: Unknown Status in OEM Priority Project: New Status in bluez package in Ubuntu: Fix Released Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in bluez source package in Focal: Fix Released Status in bluez source package in Hirsute: Fix Released Status in bluez source package in Impish: Fix Released Status in gnome-settings-daemon source package in Impish: Fix Released Bug description: [Impact] On/off of Bluetooth in gnome-control-center will not work properly in kernels 5.11 (approximately) onward. Devices are not refreshed in the list anymore. [Test Plan] 1. Open gnome-control-center and select Bluetooth 2. Turn off Bluetooth via UI 3. Turn on Bluetooth via UI Expect: Device list appears, so Bluetooth really is on. [Where problems could occur] Since the fix involves the 'rfkill' logic it has the potential to affect any Bluetooth or Wifi on/off setting. [Other info] Upstream bug in gnome-bluetooth: https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 Discussion in linux-bluetooth: https://marc.info/?t=16200475893=1=2 [Original bug report] When ever i Turn on my system or restart bluetooth is open any it connects to any device. But when i turn off bluetooth and try to turn it on again. it neither turns on nor scans/connects to any device. This is happening since I updated my system to ubuntu 21.04 LTS Bluetooth: hci0: HCI reset during shutdown failed ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Apr 25 15:09:23 2021 InstallationDate: Installed on 2020-12-15 (130 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 80TR ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago) dmi.bios.date: 07/31/2017 dmi.bios.release: 1.29 dmi.bios.vendor: LENOVO dmi.bios.version: 3UCN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Nano 5B1 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 110-15AST dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST: dmi.product.family: IDEAPAD dmi.product.name: 80TR dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST dmi.product.version: Lenovo ideapad 110-15AST dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: C8:3D:D4:84:E0:06 ACL MTU: 820:8 SCO MTU: 255:16 DOWN RX bytes:744804 acl:76 sco:0 events:105989 errors:0 TX bytes:51871528 acl:113157 sco:0 commands:192 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1926062/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934414] [NEW] linux ADT test failure with linux/4.15.0-149.153
Public bug reported: This is a scripted bug report about ADT failures while running linux tests for linux/4.15.0-149.153 on bionic. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/amd64/l/linux/20210625_024137_c7e43@/log.gz i386: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/i386/l/linux/20210702_010055_445cd@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/ppc64el/l/linux/20210625_011348_1dfec@/log.gz ** Affects: linux (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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1934414 Title: linux ADT test failure with linux/4.15.0-149.153 Status in linux package in Ubuntu: New Bug description: This is a scripted bug report about ADT failures while running linux tests for linux/4.15.0-149.153 on bionic. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/amd64/l/linux/20210625_024137_c7e43@/log.gz i386: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/i386/l/linux/20210702_010055_445cd@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/ppc64el/l/linux/20210625_011348_1dfec@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934414/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1924624] Re: After upgrade to kernel 5.8.0-49/50 with Intel Gen7 (Haswell/Ivy Bridge/Bay Trail) graphics a lot of glitches render screen unusable
If you still experience a problem in kernel 5.8.0-52 or later then please open a new bug by running: ubuntu-bug linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-hwe-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/1924624 Title: After upgrade to kernel 5.8.0-49/50 with Intel Gen7 (Haswell/Ivy Bridge/Bay Trail) graphics a lot of glitches render screen unusable Status in linux package in Ubuntu: Fix Released Status in linux-meta-hwe-5.8 package in Ubuntu: Fix Released Bug description: After upgrading to 5.8.0-49, on a laprtop with intel graphics, graphics was suddenly extremely glitchy. Icons from the desktop flash through the browser, windows top bar gets distorted, all sort of glitches appear, parts of characters are missing in terminal, scrolling is inconsistent and the whole desktop becomes unusable. Under wayland the graphics are a bit more stable, but lots of glitches appear anyway, video reproduction in browser is stuttering and wobbly. Booting with previous kernel 5.8.0-48 seems to fix the issues. 5.8.0-50 is broken as well. this is the result of 'sudo lshw -c video' on my hp Elitebook 8470: *-display description: VGA compatible controller product: 3rd Gen Core processor Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 09 width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:33 memory:d400-d43f memory:c000-cfff ioport:4000(size=64) memory:c-d To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924624/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-kvm/5.11.0.1011.11)
All autopkgtests for the newly accepted linux-meta-kvm (5.11.0.1011.11) for hirsute have finished running. The following regressions have been reported in tests triggered by the package: sl-modem/2.9.11~20110321-16ubuntu1 (amd64) oss4/4.2-build2010-5ubuntu8 (amd64) lttng-modules/2.12.2-1ubuntu3 (amd64) rtl8821ce/5.5.2.1-0ubuntu6 (amd64) systemd/247.3-3ubuntu3.1 (amd64) backport-iwlwifi-dkms/8613-0ubuntu2 (amd64) rtl8812au/4.3.8.12175.20140902+dfsg-0ubuntu14 (amd64) v4l2loopback/0.12.5-1ubuntu1 (amd64) virtualbox/6.1.18-dfsg-5 (amd64) dahdi-linux/1:2.11.1~dfsg-1ubuntu8 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/hirsute/update_excuses.html#linux-meta-kvm [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934410] [NEW] Second Monitor shuts off.
Public bug reported: I'm running two identical monitors daisy-chained via my DV port on my NUC10i7. The second monitor shuts down with a no signal error message, though the system still seems to see it. If I change it's refresh rate it will come back but, depending on the software I'm using, goes into low power mode and blanks off again. Sometimes randomly. Always when starting video conferencing software (e.g. zoom or webex). Today when using abd and fastboot from the command line in a terminal window. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1934410 Title: Second Monitor shuts off. Status in linux package in Ubuntu: New Bug description: I'm running two identical monitors daisy-chained via my DV port on my NUC10i7. The second monitor shuts down with a no signal error message, though the system still seems to see it. If I change it's refresh rate it will come back but, depending on the software I'm using, goes into low power mode and blanks off again. Sometimes randomly. Always when starting video conferencing software (e.g. zoom or webex). Today when using abd and fastboot from the command line in a terminal window. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934410/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930279] Re: [Ivy Bridge] flashing triangles on screen
** Summary changed: - [Ivy Bridge] flashing triangles on screen + [Ivy Bridge] flashing sliced triangles on screen -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1930279 Title: [Ivy Bridge] flashing sliced triangles on screen Status in linux package in Ubuntu: New Status in mesa package in Ubuntu: New Bug description: when i did upgrade my ubuntu from 20.04 to 20.10 i have small winking triangles on my screen, they sometimes will appear when i watching a youtube video they will appear on the video's seek bar or when i typing they will appear on selected texts,but the main and most annoying state of it happens when I am playing minecraft,my entire game screen has these little triangles ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-53.60-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 31 18:05:33 2021 DistUpgraded: 2021-05-27 14:18:07,483 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: groovy DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.4.0-73-generic, x86_64: installed virtualbox, 6.1.16, 5.8.0-53-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [1043:844d] InstallationDate: Installed on 2020-01-10 (507 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-53-generic root=UUID=a5a5279f-cdf5-4129-94fa-8f17f7401833 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to groovy on 2021-05-27 (4 days ago) dmi.bios.date: 03/19/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1204 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H61-M LX R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1204:bd03/19/2014:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MLXR2.0:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930279/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-azure-5.11/5.11.0.1011.11~20.04.10)
All autopkgtests for the newly accepted linux-meta-azure-5.11 (5.11.0.1011.11~20.04.10) for focal have finished running. The following regressions have been reported in tests triggered by the package: glibc/2.31-0ubuntu9.2 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-azure-5.11 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932303] Re: Dell XPS 17 9700 sound not working on linux-oem-5.10
** Summary changed: - Dell XPS 17 9700 wifi + Dell XPS 17 9700 sound not working on linux-oem-5.10 ** Summary changed: - Dell XPS 17 9700 sound not working on linux-oem-5.10 + Dell XPS 17 9700 microphone not working on linux-oem-5.10 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1932303 Title: Dell XPS 17 9700 microphone not working on linux-oem-5.10 Status in Ubuntu: New Status in linux-oem-5.10 package in Ubuntu: New Bug description: Release: devops@devops-XPS-17-9700:~$ lsb_release -rd Description: Ubuntu 20.04.2 LTS Release: 20.04 devops@devops-XPS-17-9700:~$ Problem: Cannot get both wifi and sound working on a Dell XPS 17 9700 (i9 processor) at the same time. With the 5.10.0-1029-oem kernel wifi works, but sound (microphone) does not. With the 5.11.0-20-generic kernel, the microphone and sound works (thank you for fix: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921632) but the wifi does not. With the 5.11.0-20-generic kernel and the linux-firmware (1.187.14) pkg installed (sound works but no wifi): Information with 5.11.0-20-generic kernel: devops@devops-XPS-17-9700:~$ sudo lspci -knn | grep Net -A3; rfkill list [sudo] password for devops: 04:00.0 Network controller [0280]: Qualcomm Device [17cb:1101] (rev 01) Subsystem: Bigfoot Networks, Inc. Device [1a56:a501] Kernel driver in use: ath11k_pci Kernel modules: ath11k_pci 05:00.0 PCI bridge [0604]: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018] [8086:15ea] (rev 06) 0: hci0: Bluetooth Soft blocked: no Hard blocked: no devops@devops-XPS-17-9700:~$ sudo lshw -C network *-network description: Network controller product: Qualcomm vendor: Qualcomm physical id: 0 bus info: pci@:04:00.0 version: 01 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list configuration: driver=ath11k_pci latency=0 resources: irq:195 memory:d210-d21f devops@devops-XPS-17-9700:~$ uname -sr Linux 5.11.0-20-generic devops@devops-XPS-17-9700:~$ sudo dmesg | grep ath11k [2.671864] ath11k_pci :04:00.0: WARNING: ath11k PCI support is experimental! [2.679263] ath11k_pci :04:00.0: BAR 0: assigned [mem 0xd210-0xd21f 64bit] [2.679309] ath11k_pci :04:00.0: enabling device ( -> 0002) devops@devops-XPS-17-9700:~$ sudo dpkg -l | grep firmware ii amd64-microcode 3.20191218.1ubuntu1 amd64Processor microcode firmware for AMD CPUs ii intel-microcode 3.20201110.0ubuntu0.20.04.2 amd64Processor microcode firmware for Intel CPUs ii linux-firmware 1.187.14 all Firmware for Linux kernel drivers devops@devops-XPS-17-9700:~$ sudo ip addr 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever devops@devops-XPS-17-9700:~$ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1932303/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-hwe-5.8/5.8.0.61.68~20.04.44)
All autopkgtests for the newly accepted linux-meta-hwe-5.8 (5.8.0.61.68~20.04.44) for focal have finished running. The following regressions have been reported in tests triggered by the package: systemd/245.4-4ubuntu3.7 (armhf) virtualbox-hwe/6.1.16-dfsg-6ubuntu1.20.04.2 (s390x, armhf, arm64, ppc64el) linux-hwe-5.8/5.8.0-61.68~20.04.1 (s390x, amd64, arm64, ppc64el) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-hwe-5.8 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1932548] Re: [Intel Wi-Fi 6 AX201] Video conferences constantly freeze when I am on wireless [8086:a0f0]
Sorry Alex... could you please explain what you mean by #9? Sorry for the newbie question, but I want to help, and I am not sure what you would like me to do. On Wed, Jun 30, 2021 at 11:10 PM Alex Tu <1932...@bugs.launchpad.net> wrote: > Hi Steve, > > is the firmware from #9 fixed the issue? > So far, we don't sure if the firmware crashing the root cause of your > issue, so KC separated it to LP: #1933755. And firmware from #9 helps LP: > #1933755 (see LP: #1933755 comment #2) > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1932548 > > Title: > [Intel Wi-Fi 6 AX201] Video conferences constantly freeze when I am on > wireless [8086:a0f0] > > Status in OEM Priority Project: > Confirmed > Status in linux-oem-5.10 package in Ubuntu: > New > > Bug description: > Whenever I am using a wireless connection, the image freezes roughly > every two minutes. Sometimes, email cannot be retrieved / computer > complains the connection was momentarily lost. > > - If I am on a wire, this problem does NOT occur. > - This problems occurs on wireless independent of the platform used > (behavior seen in both Google Hangout and Zoom) > - This problem does NOT occur on Windows. I did a meeting where both my > Linux and Windows machines were connected to the same meeting and using the > same wifi router, and while the performance on Windows was flawless, > unfortunately it was not so on the Ubuntu box. So I don't think my wifi > router or network is to blame. > - As far as I can recall, the problem used not to be there 2 weeks ago. > So it may have been introduced by a recent update. > - As communicated before, I am on a certified machine from Dell, > recently purchased with Ubuntu already on board from factory (I assume the > logs there were sent to you would contain the information). > - I tried to generate a log on the wireless, but the process did not let > me do this very easily. I am more than happy to send you additional > information - but please let me know which package you want me to spy upon > exactly, as I am not sure what would be helpful in this matter. > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: xorg 1:7.7+19ubuntu14 > ProcVersionSignature: Ubuntu 5.10.0-1029.30-oem 5.10.35 > Uname: Linux 5.10.0-1029-oem x86_64 > ApportVersion: 2.20.11-0ubuntu27.18 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' > CasperMD5CheckResult: skip > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Fri Jun 18 09:47:58 2021 > DistUpgraded: Fresh install > DistributionChannelDescriptor: ># This is the distribution channel descriptor for the OEM CDs ># For more information see > http://wiki.ubuntu.com/DistributionChannelDescriptor >canonical-oem-somerville-focal-amd64-20200502-85 > DistroCodename: focal > DistroVariant: ubuntu > EcryptfsInUse: Yes > ExtraDebuggingInterest: Yes > GraphicsCard: >Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA > controller]) > Subsystem: Dell Device [1028:0991] > InstallationDate: Installed on 2021-04-24 (54 days ago) > InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary > 20200502-05:58 > MachineType: Dell Inc. XPS 13 9310 > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1029-oem > root=UUID=28dc4511-d4dc-4dec-8abb-64e06b4e9d1e ro quiet splash vt.handoff=7 > SourcePackage: xorg > Symptom: display > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 03/25/2021 > dmi.bios.release: 2.1 > dmi.bios.vendor: Dell Inc. > dmi.bios.version: 2.1.1 > dmi.board.name: 08607K > dmi.board.vendor: Dell Inc. > dmi.board.version: A00 > dmi.chassis.type: 10 > dmi.chassis.vendor: Dell Inc. > dmi.modalias: > dmi:bvnDellInc.:bvr2.1.1:bd03/25/2021:br2.1:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn08607K:rvrA00:cvnDellInc.:ct10:cvr: > dmi.product.family: XPS > dmi.product.name: XPS 13 9310 > dmi.product.sku: 0991 > dmi.sys.vendor: Dell Inc. > version.compiz: compiz N/A > version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 > version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 > version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 > version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A > version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 > version.xserver-xorg-video-intel: xserver-xorg-video-intel > 2:2.99.917+git20200226-1 > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/oem-priority/+bug/1932548/+subscriptions > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu.
Re: [Kernel-packages] [Bug 1932548] Re: [Intel Wi-Fi 6 AX201] Video conferences constantly freeze when I am on wireless [8086:a0f0]
Hi Kai-Chuan: Let me do this after I just reproduced the bug. The last two days I kept my computer connected through Ethernet because the freeze really impedes my ability to understand my counterparts. Best Regards, Steve On Wed, Jun 30, 2021 at 7:55 PM Kai-Chuan Hsieh <1932...@bugs.launchpad.net> wrote: > Hello Steve, > > Can you attach your kernel log? upload output of "$ journalctl -k". > > Thanks, > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1932548 > > Title: > [Intel Wi-Fi 6 AX201] Video conferences constantly freeze when I am on > wireless [8086:a0f0] > > Status in OEM Priority Project: > Confirmed > Status in linux-oem-5.10 package in Ubuntu: > New > > Bug description: > Whenever I am using a wireless connection, the image freezes roughly > every two minutes. Sometimes, email cannot be retrieved / computer > complains the connection was momentarily lost. > > - If I am on a wire, this problem does NOT occur. > - This problems occurs on wireless independent of the platform used > (behavior seen in both Google Hangout and Zoom) > - This problem does NOT occur on Windows. I did a meeting where both my > Linux and Windows machines were connected to the same meeting and using the > same wifi router, and while the performance on Windows was flawless, > unfortunately it was not so on the Ubuntu box. So I don't think my wifi > router or network is to blame. > - As far as I can recall, the problem used not to be there 2 weeks ago. > So it may have been introduced by a recent update. > - As communicated before, I am on a certified machine from Dell, > recently purchased with Ubuntu already on board from factory (I assume the > logs there were sent to you would contain the information). > - I tried to generate a log on the wireless, but the process did not let > me do this very easily. I am more than happy to send you additional > information - but please let me know which package you want me to spy upon > exactly, as I am not sure what would be helpful in this matter. > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: xorg 1:7.7+19ubuntu14 > ProcVersionSignature: Ubuntu 5.10.0-1029.30-oem 5.10.35 > Uname: Linux 5.10.0-1029-oem x86_64 > ApportVersion: 2.20.11-0ubuntu27.18 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' > CasperMD5CheckResult: skip > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Fri Jun 18 09:47:58 2021 > DistUpgraded: Fresh install > DistributionChannelDescriptor: ># This is the distribution channel descriptor for the OEM CDs ># For more information see > http://wiki.ubuntu.com/DistributionChannelDescriptor >canonical-oem-somerville-focal-amd64-20200502-85 > DistroCodename: focal > DistroVariant: ubuntu > EcryptfsInUse: Yes > ExtraDebuggingInterest: Yes > GraphicsCard: >Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA > controller]) > Subsystem: Dell Device [1028:0991] > InstallationDate: Installed on 2021-04-24 (54 days ago) > InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary > 20200502-05:58 > MachineType: Dell Inc. XPS 13 9310 > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1029-oem > root=UUID=28dc4511-d4dc-4dec-8abb-64e06b4e9d1e ro quiet splash vt.handoff=7 > SourcePackage: xorg > Symptom: display > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 03/25/2021 > dmi.bios.release: 2.1 > dmi.bios.vendor: Dell Inc. > dmi.bios.version: 2.1.1 > dmi.board.name: 08607K > dmi.board.vendor: Dell Inc. > dmi.board.version: A00 > dmi.chassis.type: 10 > dmi.chassis.vendor: Dell Inc. > dmi.modalias: > dmi:bvnDellInc.:bvr2.1.1:bd03/25/2021:br2.1:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn08607K:rvrA00:cvnDellInc.:ct10:cvr: > dmi.product.family: XPS > dmi.product.name: XPS 13 9310 > dmi.product.sku: 0991 > dmi.sys.vendor: Dell Inc. > version.compiz: compiz N/A > version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 > version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 > version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 > version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A > version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 > version.xserver-xorg-video-intel: xserver-xorg-video-intel > 2:2.99.917+git20200226-1 > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/oem-priority/+bug/1932548/+subscriptions > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1932548 Title: [Intel Wi-Fi 6 AX201] Video
[Kernel-packages] [Bug 1932163] Re: evdi/1.7.0+dfsg-1ubuntu1~20.04.3 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1
** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1932163 Title: evdi/1.7.0+dfsg-1ubuntu1~20.04.3 ADT test failure with linux- hwe-5.11/5.11.0-20.21~20.04.1 Status in evdi package in Ubuntu: New Status in linux-hwe-5.11 package in Ubuntu: New Status in evdi source package in Focal: In Progress Status in linux-hwe-5.11 source package in Focal: New Status in evdi source package in Hirsute: New Status in linux-hwe-5.11 source package in Hirsute: New Bug description: [Impact] focal users running latest hwe kernel, version 5.11, won't be able to use evdi-dkms. [Test case] Built evdi dkms and loaded the evdi module on 5.4, 5.8 and 5.11 kernels. [Potential regression] DisplayLink devices will stop working. -- This is a scripted bug report about ADT failures while running evdi tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/e/evdi/20210611_210228_7f0da@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/arm64/e/evdi/20210612_122245_bd52e@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/e/evdi/20210611_210028_038f3@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/e/evdi/20210611_205902_3dc65@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evdi/+bug/1932163/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1924624] Re: After upgrade to kernel 5.8.0-49/50 with Intel Gen7 (Haswell/Ivy Bridge/Bay Trail) graphics a lot of glitches render screen unusable
I was using linux-image-5.8.0-55-generic:amd64 - this kernel still has the issues. Reverting to 5.8.0-48 removes the issues. Changing to the 5.4 kernel (latest) also removes the issues -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-hwe-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/1924624 Title: After upgrade to kernel 5.8.0-49/50 with Intel Gen7 (Haswell/Ivy Bridge/Bay Trail) graphics a lot of glitches render screen unusable Status in linux package in Ubuntu: Fix Released Status in linux-meta-hwe-5.8 package in Ubuntu: Fix Released Bug description: After upgrading to 5.8.0-49, on a laprtop with intel graphics, graphics was suddenly extremely glitchy. Icons from the desktop flash through the browser, windows top bar gets distorted, all sort of glitches appear, parts of characters are missing in terminal, scrolling is inconsistent and the whole desktop becomes unusable. Under wayland the graphics are a bit more stable, but lots of glitches appear anyway, video reproduction in browser is stuttering and wobbly. Booting with previous kernel 5.8.0-48 seems to fix the issues. 5.8.0-50 is broken as well. this is the result of 'sudo lshw -c video' on my hp Elitebook 8470: *-display description: VGA compatible controller product: 3rd Gen Core processor Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 09 width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:33 memory:d400-d43f memory:c000-cfff ioport:4000(size=64) memory:c-d To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924624/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934401] [NEW] Control netfilter flow table timeouts via sysctl
Public bug reported: * Explain the bug(s) TCP and UDP connections may be offloaded from nf conntrack to nf flow table. Offloaded connections are aged after 30 seconds of inactivity. Once aged, ownership is returned to conntrack with a hard coded tcp/udp pickup time of 120/30 seconds, after which the connection may be deleted. The current hard-coded pickup intervals may introduce a very aggressive aging policy. For example, offloaded tcp connections in established state will timeout from nf conntrack after just 150 seconds of inactivity, instead of 5 days. In addition, the hard-coded 30 second offload timeout period can significantly increase the hardware insertion rate requirements in some use cases. * Brief explanation of fixes This patchset provides the user with the ability to configure protocol specific offload timeout and pickup intervals via sysctl. The first and second patches revert the existing non-upstream solution. The next two patches introduce the sysctl configuration for tcp and udp protocols. The last patch modifies nf flow table aging mechanisms to use the configured time intervals. * How to test Control tcp/udp connection timeout using the following sysctl parameters: net.netfilter.nf_flowtable_tcp_pickup = 120 net.netfilter.nf_flowtable_tcp_timeout = 30 net.netfilter.nf_flowtable_udp_pickup = 30 net.netfilter.nf_flowtable_udp_timeout = 30 * What it could break. Existing configuration scripts – not kernel related ** Affects: linux-bluefield (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1934401 Title: Control netfilter flow table timeouts via sysctl Status in linux-bluefield package in Ubuntu: New Bug description: * Explain the bug(s) TCP and UDP connections may be offloaded from nf conntrack to nf flow table. Offloaded connections are aged after 30 seconds of inactivity. Once aged, ownership is returned to conntrack with a hard coded tcp/udp pickup time of 120/30 seconds, after which the connection may be deleted. The current hard-coded pickup intervals may introduce a very aggressive aging policy. For example, offloaded tcp connections in established state will timeout from nf conntrack after just 150 seconds of inactivity, instead of 5 days. In addition, the hard-coded 30 second offload timeout period can significantly increase the hardware insertion rate requirements in some use cases. * Brief explanation of fixes This patchset provides the user with the ability to configure protocol specific offload timeout and pickup intervals via sysctl. The first and second patches revert the existing non-upstream solution. The next two patches introduce the sysctl configuration for tcp and udp protocols. The last patch modifies nf flow table aging mechanisms to use the configured time intervals. * How to test Control tcp/udp connection timeout using the following sysctl parameters: net.netfilter.nf_flowtable_tcp_pickup = 120 net.netfilter.nf_flowtable_tcp_timeout = 30 net.netfilter.nf_flowtable_udp_pickup = 30 net.netfilter.nf_flowtable_udp_timeout = 30 * What it could break. Existing configuration scripts – not kernel related To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1934401/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934387] Re: Kernel panic booting on Unmatched with kernel 5.8
** Changed in: linux-riscv-5.8 (Ubuntu) Milestone: ubuntu-20.04.3 => None -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/1934387 Title: Kernel panic booting on Unmatched with kernel 5.8 Status in linux-riscv-5.8 package in Ubuntu: New Bug description: This doesn't happen every time a boot is attempted, but very frequently. Log below: [ 15.024548] Loaded X.509 cert 'Canonical Ltd. Live Patch Signing: 14df34d1a87cf37625abec039ef2bf521249b969' [ 15.038870] Loaded X.509 cert 'Canonical Ltd. Kernel Module Signing: 88f752e560a1e0737e31163a466ad7b70a850c19' [ 15.048759] zswap: loaded using pool lzo/zbud [ 15.053091] Key type ._fscrypt registered [ 15.056452] Key type .fscrypt registered [ 15.060276] GPT:Primary header thinks Alt. header is not at the end of the disk. [ 15.060376] Key type fscrypt-provisioning registered [ 15.067784] GPT:7340031 != 62333951 [ 15.067790] GPT:Alternate GPT header not at the end of the disk. [ 15.082195] GPT:7340031 != 62333951 [ 15.085655] GPT: Use GNU Parted to correct GPT errors. [ 15.089268] Key type encrypted registered [ 15.090848] mmcblk0: p1 p12 p13 p14 p15 [ 15.094794] AppArmor: AppArmor sha1 policy hashing enabled [ 15.104197] ima: No TPM chip found, activating TPM-bypass! [ 15.109690] ima: Allocated hash algorithm: sha1 [ 15.114191] ima: No architecture policies found [ 15.118816] evm: Initialising EVM extended attributes: [ 15.123787] evm: security.selinux [ 15.127086] evm: security.SMACK64 [ 15.130380] evm: security.SMACK64EXEC [ 15.134030] evm: security.SMACK64TRANSMUTE [ 15.138108] evm: security.SMACK64MMAP [ 15.141755] evm: security.apparmor [ 15.145142] evm: security.ima [ 15.148081] evm: security.capability [ 15.151656] evm: HMAC attrs: 0x1 [ 18.062579] Freeing unused kernel memory: 308K [ 18.071639] [ cut here ] [ 18.075533] riscv/mm: Found insecure W+X mapping at address (ptrval)/0xffdff800 [ 18.084242] WARNING: CPU: 2 PID: 1 at arch/riscv/mm/ptdump.c:200 note_page+0x24c/0x252 [ 18.092116] Modules linked in: [ 18.095142] CPU: 2 PID: 1 Comm: swapper/0 Not tainted 5.8.0-29-generic #31~20.04.1-Ubuntu [ 18.103320] epc: ffe00020891a ra : ffe00020891a sp : ffe1f5bebb30 [ 18.110425] gp : ffe0013206b8 tp : ffe1f5be6780 t0 : ffe001336fa0 [ 18.117650] t1 : ffe001336f38 t2 : 0001fecd4000 s0 : ffe1f5bebb80 [ 18.124859] s1 : ffe1f5bebe10 a0 : 0053 a1 : 00020020 [ 18.132067] a2 : ffe1f5beb870 a3 : a4 : ffe0012200a0 [ 18.139277] a5 : ffe0012200a0 a6 : 00c6 a7 : ffe0006ebfee [ 18.146485] s2 : ffdff8001000 s3 : s4 : 0004 [ 18.153698] s5 : s6 : s7 : ffe1f5bebd20 [ 18.160917] s8 : ffdff8001000 s9 : ffe001322148 s10: ffdff8002000 [ 18.168116] s11: ffe000c16e20 t3 : 0003cca8 t4 : 0003cca8 [ 18.175323] t5 : t6 : ffe001331462 [ 18.180605] status: 00020120 badaddr: ffe1f5bebb30 cause: 0003 [ 18.188525] ---[ end trace ecc2ef275d977b46 ]--- [ 18.193629] Checked W+X mappings: failed, 513 W+X pages found [ 18.198865] Run /init as init process Loading, please wait... Starting version 245.4-4ubuntu3.7 [ 18.683096] Unable to handle kernel paging request at virtual address 005f8141b42c [ 18.690315] Oops [#1] [ 18.692526] Modules linked in: phylink i2c_ocores(+) [ 18.697489] CPU: 0 PID: 147 Comm: systemd-udevd Tainted: GW 5.8.0-29-generic #31~20.04.1-Ubuntu [ 18.707566] epc: ffdf8141b42c ra : ffe000266012 sp : ffe1f4b3bd20 [ 18.714668] gp : ffe0013206b8 tp : ffe1f46f t0 : 0040 [ 18.721931] t1 : t2 : 000a s0 : ffe1f4b3bda0 [ 18.729123] s1 : a0 : 0003 a1 : ffe1f4a39018 [ 18.736314] a2 : 0001 a3 : a4 : ffdf8141b42c [ 18.739498] macb 1009.ethernet: Registered clk switch 'sifive-gemgxl-mgmt' [ 18.743528] a5 : 0003 a6 : ffe1f5603d98 a7 : ffe1f5603dc0 [ 18.743533] s2 : 0003 s3 : ffe1f4b3bdac s4 : 0001 [ 18.743537] s5 : ffe0012f02c8 s6 : ffe0012f02f0 s7 : 0002 [ 18.743542] s8 : ffe1f5d46000 s9 : 002ab15da010 s10: 0002 [ 18.743546] s11: ffe1f35a3680 t3 : 0002 t4 : 0402 [ 18.743553] t5 : ffe001220348 t6 : ffe001220350 [ 18.750909] macb 1009.ethernet: GEM doesn't support hardware ptp. [
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-raspi/5.11.0.1013.11)
All autopkgtests for the newly accepted linux-meta-raspi (5.11.0.1013.11) for hirsute have finished running. The following regressions have been reported in tests triggered by the package: wireguard-linux-compat/unknown (arm64) systemd/unknown (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/hirsute/update_excuses.html#linux-meta-raspi [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-kvm/5.11.0.1010.10)
All autopkgtests for the newly accepted linux-meta-kvm (5.11.0.1010.10) for hirsute have finished running. The following regressions have been reported in tests triggered by the package: v4l2loopback/0.12.5-1ubuntu1 (amd64) rtl8821ce/5.5.2.1-0ubuntu6 (amd64) oss4/4.2-build2010-5ubuntu8 (amd64) virtualbox/6.1.22-dfsg-2~ubuntu1.21.04.1 (amd64) dahdi-linux/1:2.11.1~dfsg-1ubuntu8 (amd64) rtl8812au/4.3.8.12175.20140902+dfsg-0ubuntu14 (amd64) sl-modem/2.9.11~20110321-16ubuntu1 (amd64) systemd/247.3-3ubuntu3.1 (amd64) backport-iwlwifi-dkms/8613-0ubuntu2 (amd64) lttng-modules/2.12.2-1ubuntu3 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/hirsute/update_excuses.html#linux-meta-kvm [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1933950] Re: [i915] Black screen when I login in using kernel 5.8.0-59 but not 5.8.0-25
** Attachment added: "Screenshot from 2021-07-01 22-55-12.png" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933950/+attachment/5508496/+files/Screenshot%20from%202021-07-01%2022-55-12.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1933950 Title: [i915] Black screen when I login in using kernel 5.8.0-59 but not 5.8.0-25 Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: New Bug description: There was also no brightness setting. I have reinstalled ubuntu 3 times already. This happened after the updates on June 24th. The only solution is not to install ubuntu updates. As soon as I install updates, there is a black screen. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.80 Fri May 7 06:55:54 UTC 2021 GCC version: gcc version 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.10) ApportVersion: 2.20.11-0ubuntu50.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jun 29 11:22:08 2021 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu DkmsStatus: nvidia, 460.80, 5.8.0-25-generic, x86_64: installed nvidia, 460.80, 5.8.0-59-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics 630 (Mobile) [103c:85fb] NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] [10de:2191] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company TU116M [GeForce GTX 1660 Ti Mobile] [103c:85fb] InstallationDate: Installed on 2021-06-25 (3 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: HP HP Pavilion Gaming Laptop 15-dk0xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic root=UUID=a7c41e63-e7ea-43e0-9de0-55322f489ee5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2020 dmi.bios.release: 15.33 dmi.bios.vendor: Insyde dmi.bios.version: F.33 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 85FB dmi.board.vendor: HP dmi.board.version: 42.42 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 42.42 dmi.modalias: dmi:bvnInsyde:bvrF.33:bd07/16/2020:br15.33:efr42.42:svnHP:pnHPPavilionGamingLaptop15-dk0xxx:pvrType1ProductConfigId:rvnHP:rn85FB:rvr42.42:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Gaming Laptop 15-dk0xxx dmi.product.sku: 2C7M8EA#ACB dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933950/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1933950] Re: [i915] Black screen when I login in using kernel 5.8.0-59 but not 5.8.0-25
$ uname -a Linux ter 5.11.0-22-generic #23-Ubuntu SMP Thu Jun 17 00:34:23 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux I have updated ubuntu. This did not help the problem remained. Also there is no brightness editing. ** Attachment added: "Screenshot from 2021-07-01 22-46-30.png" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933950/+attachment/5508495/+files/Screenshot%20from%202021-07-01%2022-46-30.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1933950 Title: [i915] Black screen when I login in using kernel 5.8.0-59 but not 5.8.0-25 Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: New Bug description: There was also no brightness setting. I have reinstalled ubuntu 3 times already. This happened after the updates on June 24th. The only solution is not to install ubuntu updates. As soon as I install updates, there is a black screen. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.80 Fri May 7 06:55:54 UTC 2021 GCC version: gcc version 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.10) ApportVersion: 2.20.11-0ubuntu50.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jun 29 11:22:08 2021 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu DkmsStatus: nvidia, 460.80, 5.8.0-25-generic, x86_64: installed nvidia, 460.80, 5.8.0-59-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics 630 (Mobile) [103c:85fb] NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] [10de:2191] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company TU116M [GeForce GTX 1660 Ti Mobile] [103c:85fb] InstallationDate: Installed on 2021-06-25 (3 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: HP HP Pavilion Gaming Laptop 15-dk0xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic root=UUID=a7c41e63-e7ea-43e0-9de0-55322f489ee5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2020 dmi.bios.release: 15.33 dmi.bios.vendor: Insyde dmi.bios.version: F.33 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 85FB dmi.board.vendor: HP dmi.board.version: 42.42 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 42.42 dmi.modalias: dmi:bvnInsyde:bvrF.33:bd07/16/2020:br15.33:efr42.42:svnHP:pnHPPavilionGamingLaptop15-dk0xxx:pvrType1ProductConfigId:rvnHP:rn85FB:rvr42.42:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Gaming Laptop 15-dk0xxx dmi.product.sku: 2C7M8EA#ACB dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933950/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934398] Re: Prevent spurious wakeups on amd s2idle
The patch is queued upstream for 5.14-rc1: https://lore.kernel.org /linux- acpi/CAJZ5v0jhYL6Qrj5vvU=5FguF=mvryfrbbtgvc8chzckkxm_...@mail.gmail.com/T/#mb0e0b54da3256cfb04cee38e45322a086d523652 ** Changed in: linux-oem-5.10 (Ubuntu Focal) Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng) ** Changed in: linux-oem-5.13 (Ubuntu Focal) Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1934398 Title: Prevent spurious wakeups on amd s2idle Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.10 source package in Focal: New Status in linux-oem-5.13 source package in Focal: New Bug description: [Impact] Several AMD based OEM designs have spurious wakeups occurring from EC events during s2idle. This leads to non-functional wakeup sources or higher power consumption. [Fix] Prevent setting the GPE for the EC for wakeup source on AMD systems. [Test] Verify s2idle on OEM system. [Where problems could occur] Code is guarded to only run on AMD systems, which are just now getting s2idle support in oem kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.10/+bug/1934398/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934398] [NEW] Prevent spurious wakeups on amd s2idle
Public bug reported: [Impact] Several AMD based OEM designs have spurious wakeups occurring from EC events during s2idle. This leads to non-functional wakeup sources or higher power consumption. [Fix] Prevent setting the GPE for the EC for wakeup source on AMD systems. [Test] Verify s2idle on OEM system. [Where problems could occur] Code is guarded to only run on AMD systems, which are just now getting s2idle support in oem kernel. ** Affects: linux-oem-5.10 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-oem-5.13 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-oem-5.10 (Ubuntu Focal) Importance: Undecided Assignee: Kai-Heng Feng (kaihengfeng) Status: New ** Affects: linux-oem-5.13 (Ubuntu Focal) Importance: Undecided Assignee: Kai-Heng Feng (kaihengfeng) Status: New ** Also affects: linux-oem-5.13 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-oem-5.10 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.13 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-oem-5.10 (Ubuntu) Status: New => Invalid ** Changed in: linux-oem-5.13 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1934398 Title: Prevent spurious wakeups on amd s2idle Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.10 source package in Focal: New Status in linux-oem-5.13 source package in Focal: New Bug description: [Impact] Several AMD based OEM designs have spurious wakeups occurring from EC events during s2idle. This leads to non-functional wakeup sources or higher power consumption. [Fix] Prevent setting the GPE for the EC for wakeup source on AMD systems. [Test] Verify s2idle on OEM system. [Where problems could occur] Code is guarded to only run on AMD systems, which are just now getting s2idle support in oem kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.10/+bug/1934398/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934387] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1934387/+attachment/5508491/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/1934387 Title: Kernel panic booting on Unmatched with kernel 5.8 Status in linux-riscv-5.8 package in Ubuntu: New Bug description: This doesn't happen every time a boot is attempted, but very frequently. Log below: [ 15.024548] Loaded X.509 cert 'Canonical Ltd. Live Patch Signing: 14df34d1a87cf37625abec039ef2bf521249b969' [ 15.038870] Loaded X.509 cert 'Canonical Ltd. Kernel Module Signing: 88f752e560a1e0737e31163a466ad7b70a850c19' [ 15.048759] zswap: loaded using pool lzo/zbud [ 15.053091] Key type ._fscrypt registered [ 15.056452] Key type .fscrypt registered [ 15.060276] GPT:Primary header thinks Alt. header is not at the end of the disk. [ 15.060376] Key type fscrypt-provisioning registered [ 15.067784] GPT:7340031 != 62333951 [ 15.067790] GPT:Alternate GPT header not at the end of the disk. [ 15.082195] GPT:7340031 != 62333951 [ 15.085655] GPT: Use GNU Parted to correct GPT errors. [ 15.089268] Key type encrypted registered [ 15.090848] mmcblk0: p1 p12 p13 p14 p15 [ 15.094794] AppArmor: AppArmor sha1 policy hashing enabled [ 15.104197] ima: No TPM chip found, activating TPM-bypass! [ 15.109690] ima: Allocated hash algorithm: sha1 [ 15.114191] ima: No architecture policies found [ 15.118816] evm: Initialising EVM extended attributes: [ 15.123787] evm: security.selinux [ 15.127086] evm: security.SMACK64 [ 15.130380] evm: security.SMACK64EXEC [ 15.134030] evm: security.SMACK64TRANSMUTE [ 15.138108] evm: security.SMACK64MMAP [ 15.141755] evm: security.apparmor [ 15.145142] evm: security.ima [ 15.148081] evm: security.capability [ 15.151656] evm: HMAC attrs: 0x1 [ 18.062579] Freeing unused kernel memory: 308K [ 18.071639] [ cut here ] [ 18.075533] riscv/mm: Found insecure W+X mapping at address (ptrval)/0xffdff800 [ 18.084242] WARNING: CPU: 2 PID: 1 at arch/riscv/mm/ptdump.c:200 note_page+0x24c/0x252 [ 18.092116] Modules linked in: [ 18.095142] CPU: 2 PID: 1 Comm: swapper/0 Not tainted 5.8.0-29-generic #31~20.04.1-Ubuntu [ 18.103320] epc: ffe00020891a ra : ffe00020891a sp : ffe1f5bebb30 [ 18.110425] gp : ffe0013206b8 tp : ffe1f5be6780 t0 : ffe001336fa0 [ 18.117650] t1 : ffe001336f38 t2 : 0001fecd4000 s0 : ffe1f5bebb80 [ 18.124859] s1 : ffe1f5bebe10 a0 : 0053 a1 : 00020020 [ 18.132067] a2 : ffe1f5beb870 a3 : a4 : ffe0012200a0 [ 18.139277] a5 : ffe0012200a0 a6 : 00c6 a7 : ffe0006ebfee [ 18.146485] s2 : ffdff8001000 s3 : s4 : 0004 [ 18.153698] s5 : s6 : s7 : ffe1f5bebd20 [ 18.160917] s8 : ffdff8001000 s9 : ffe001322148 s10: ffdff8002000 [ 18.168116] s11: ffe000c16e20 t3 : 0003cca8 t4 : 0003cca8 [ 18.175323] t5 : t6 : ffe001331462 [ 18.180605] status: 00020120 badaddr: ffe1f5bebb30 cause: 0003 [ 18.188525] ---[ end trace ecc2ef275d977b46 ]--- [ 18.193629] Checked W+X mappings: failed, 513 W+X pages found [ 18.198865] Run /init as init process Loading, please wait... Starting version 245.4-4ubuntu3.7 [ 18.683096] Unable to handle kernel paging request at virtual address 005f8141b42c [ 18.690315] Oops [#1] [ 18.692526] Modules linked in: phylink i2c_ocores(+) [ 18.697489] CPU: 0 PID: 147 Comm: systemd-udevd Tainted: GW 5.8.0-29-generic #31~20.04.1-Ubuntu [ 18.707566] epc: ffdf8141b42c ra : ffe000266012 sp : ffe1f4b3bd20 [ 18.714668] gp : ffe0013206b8 tp : ffe1f46f t0 : 0040 [ 18.721931] t1 : t2 : 000a s0 : ffe1f4b3bda0 [ 18.729123] s1 : a0 : 0003 a1 : ffe1f4a39018 [ 18.736314] a2 : 0001 a3 : a4 : ffdf8141b42c [ 18.739498] macb 1009.ethernet: Registered clk switch 'sifive-gemgxl-mgmt' [ 18.743528] a5 : 0003 a6 : ffe1f5603d98 a7 : ffe1f5603dc0 [ 18.743533] s2 : 0003 s3 : ffe1f4b3bdac s4 : 0001 [ 18.743537] s5 : ffe0012f02c8 s6 : ffe0012f02f0 s7 : 0002 [ 18.743542] s8 : ffe1f5d46000 s9 : 002ab15da010 s10: 0002 [ 18.743546] s11: ffe1f35a3680 t3 : 0002 t4 : 0402 [ 18.743553] t5 : ffe001220348 t6 : ffe001220350 [
[Kernel-packages] [Bug 1934387] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1934387/+attachment/5508493/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/1934387 Title: Kernel panic booting on Unmatched with kernel 5.8 Status in linux-riscv-5.8 package in Ubuntu: New Bug description: This doesn't happen every time a boot is attempted, but very frequently. Log below: [ 15.024548] Loaded X.509 cert 'Canonical Ltd. Live Patch Signing: 14df34d1a87cf37625abec039ef2bf521249b969' [ 15.038870] Loaded X.509 cert 'Canonical Ltd. Kernel Module Signing: 88f752e560a1e0737e31163a466ad7b70a850c19' [ 15.048759] zswap: loaded using pool lzo/zbud [ 15.053091] Key type ._fscrypt registered [ 15.056452] Key type .fscrypt registered [ 15.060276] GPT:Primary header thinks Alt. header is not at the end of the disk. [ 15.060376] Key type fscrypt-provisioning registered [ 15.067784] GPT:7340031 != 62333951 [ 15.067790] GPT:Alternate GPT header not at the end of the disk. [ 15.082195] GPT:7340031 != 62333951 [ 15.085655] GPT: Use GNU Parted to correct GPT errors. [ 15.089268] Key type encrypted registered [ 15.090848] mmcblk0: p1 p12 p13 p14 p15 [ 15.094794] AppArmor: AppArmor sha1 policy hashing enabled [ 15.104197] ima: No TPM chip found, activating TPM-bypass! [ 15.109690] ima: Allocated hash algorithm: sha1 [ 15.114191] ima: No architecture policies found [ 15.118816] evm: Initialising EVM extended attributes: [ 15.123787] evm: security.selinux [ 15.127086] evm: security.SMACK64 [ 15.130380] evm: security.SMACK64EXEC [ 15.134030] evm: security.SMACK64TRANSMUTE [ 15.138108] evm: security.SMACK64MMAP [ 15.141755] evm: security.apparmor [ 15.145142] evm: security.ima [ 15.148081] evm: security.capability [ 15.151656] evm: HMAC attrs: 0x1 [ 18.062579] Freeing unused kernel memory: 308K [ 18.071639] [ cut here ] [ 18.075533] riscv/mm: Found insecure W+X mapping at address (ptrval)/0xffdff800 [ 18.084242] WARNING: CPU: 2 PID: 1 at arch/riscv/mm/ptdump.c:200 note_page+0x24c/0x252 [ 18.092116] Modules linked in: [ 18.095142] CPU: 2 PID: 1 Comm: swapper/0 Not tainted 5.8.0-29-generic #31~20.04.1-Ubuntu [ 18.103320] epc: ffe00020891a ra : ffe00020891a sp : ffe1f5bebb30 [ 18.110425] gp : ffe0013206b8 tp : ffe1f5be6780 t0 : ffe001336fa0 [ 18.117650] t1 : ffe001336f38 t2 : 0001fecd4000 s0 : ffe1f5bebb80 [ 18.124859] s1 : ffe1f5bebe10 a0 : 0053 a1 : 00020020 [ 18.132067] a2 : ffe1f5beb870 a3 : a4 : ffe0012200a0 [ 18.139277] a5 : ffe0012200a0 a6 : 00c6 a7 : ffe0006ebfee [ 18.146485] s2 : ffdff8001000 s3 : s4 : 0004 [ 18.153698] s5 : s6 : s7 : ffe1f5bebd20 [ 18.160917] s8 : ffdff8001000 s9 : ffe001322148 s10: ffdff8002000 [ 18.168116] s11: ffe000c16e20 t3 : 0003cca8 t4 : 0003cca8 [ 18.175323] t5 : t6 : ffe001331462 [ 18.180605] status: 00020120 badaddr: ffe1f5bebb30 cause: 0003 [ 18.188525] ---[ end trace ecc2ef275d977b46 ]--- [ 18.193629] Checked W+X mappings: failed, 513 W+X pages found [ 18.198865] Run /init as init process Loading, please wait... Starting version 245.4-4ubuntu3.7 [ 18.683096] Unable to handle kernel paging request at virtual address 005f8141b42c [ 18.690315] Oops [#1] [ 18.692526] Modules linked in: phylink i2c_ocores(+) [ 18.697489] CPU: 0 PID: 147 Comm: systemd-udevd Tainted: GW 5.8.0-29-generic #31~20.04.1-Ubuntu [ 18.707566] epc: ffdf8141b42c ra : ffe000266012 sp : ffe1f4b3bd20 [ 18.714668] gp : ffe0013206b8 tp : ffe1f46f t0 : 0040 [ 18.721931] t1 : t2 : 000a s0 : ffe1f4b3bda0 [ 18.729123] s1 : a0 : 0003 a1 : ffe1f4a39018 [ 18.736314] a2 : 0001 a3 : a4 : ffdf8141b42c [ 18.739498] macb 1009.ethernet: Registered clk switch 'sifive-gemgxl-mgmt' [ 18.743528] a5 : 0003 a6 : ffe1f5603d98 a7 : ffe1f5603dc0 [ 18.743533] s2 : 0003 s3 : ffe1f4b3bdac s4 : 0001 [ 18.743537] s5 : ffe0012f02c8 s6 : ffe0012f02f0 s7 : 0002 [ 18.743542] s8 : ffe1f5d46000 s9 : 002ab15da010 s10: 0002 [ 18.743546] s11: ffe1f35a3680 t3 : 0002 t4 : 0402 [ 18.743553] t5 : ffe001220348 t6 : ffe001220350 [ 18.750909] macb
[Kernel-packages] [Bug 1934387] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1934387/+attachment/5508494/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/1934387 Title: Kernel panic booting on Unmatched with kernel 5.8 Status in linux-riscv-5.8 package in Ubuntu: New Bug description: This doesn't happen every time a boot is attempted, but very frequently. Log below: [ 15.024548] Loaded X.509 cert 'Canonical Ltd. Live Patch Signing: 14df34d1a87cf37625abec039ef2bf521249b969' [ 15.038870] Loaded X.509 cert 'Canonical Ltd. Kernel Module Signing: 88f752e560a1e0737e31163a466ad7b70a850c19' [ 15.048759] zswap: loaded using pool lzo/zbud [ 15.053091] Key type ._fscrypt registered [ 15.056452] Key type .fscrypt registered [ 15.060276] GPT:Primary header thinks Alt. header is not at the end of the disk. [ 15.060376] Key type fscrypt-provisioning registered [ 15.067784] GPT:7340031 != 62333951 [ 15.067790] GPT:Alternate GPT header not at the end of the disk. [ 15.082195] GPT:7340031 != 62333951 [ 15.085655] GPT: Use GNU Parted to correct GPT errors. [ 15.089268] Key type encrypted registered [ 15.090848] mmcblk0: p1 p12 p13 p14 p15 [ 15.094794] AppArmor: AppArmor sha1 policy hashing enabled [ 15.104197] ima: No TPM chip found, activating TPM-bypass! [ 15.109690] ima: Allocated hash algorithm: sha1 [ 15.114191] ima: No architecture policies found [ 15.118816] evm: Initialising EVM extended attributes: [ 15.123787] evm: security.selinux [ 15.127086] evm: security.SMACK64 [ 15.130380] evm: security.SMACK64EXEC [ 15.134030] evm: security.SMACK64TRANSMUTE [ 15.138108] evm: security.SMACK64MMAP [ 15.141755] evm: security.apparmor [ 15.145142] evm: security.ima [ 15.148081] evm: security.capability [ 15.151656] evm: HMAC attrs: 0x1 [ 18.062579] Freeing unused kernel memory: 308K [ 18.071639] [ cut here ] [ 18.075533] riscv/mm: Found insecure W+X mapping at address (ptrval)/0xffdff800 [ 18.084242] WARNING: CPU: 2 PID: 1 at arch/riscv/mm/ptdump.c:200 note_page+0x24c/0x252 [ 18.092116] Modules linked in: [ 18.095142] CPU: 2 PID: 1 Comm: swapper/0 Not tainted 5.8.0-29-generic #31~20.04.1-Ubuntu [ 18.103320] epc: ffe00020891a ra : ffe00020891a sp : ffe1f5bebb30 [ 18.110425] gp : ffe0013206b8 tp : ffe1f5be6780 t0 : ffe001336fa0 [ 18.117650] t1 : ffe001336f38 t2 : 0001fecd4000 s0 : ffe1f5bebb80 [ 18.124859] s1 : ffe1f5bebe10 a0 : 0053 a1 : 00020020 [ 18.132067] a2 : ffe1f5beb870 a3 : a4 : ffe0012200a0 [ 18.139277] a5 : ffe0012200a0 a6 : 00c6 a7 : ffe0006ebfee [ 18.146485] s2 : ffdff8001000 s3 : s4 : 0004 [ 18.153698] s5 : s6 : s7 : ffe1f5bebd20 [ 18.160917] s8 : ffdff8001000 s9 : ffe001322148 s10: ffdff8002000 [ 18.168116] s11: ffe000c16e20 t3 : 0003cca8 t4 : 0003cca8 [ 18.175323] t5 : t6 : ffe001331462 [ 18.180605] status: 00020120 badaddr: ffe1f5bebb30 cause: 0003 [ 18.188525] ---[ end trace ecc2ef275d977b46 ]--- [ 18.193629] Checked W+X mappings: failed, 513 W+X pages found [ 18.198865] Run /init as init process Loading, please wait... Starting version 245.4-4ubuntu3.7 [ 18.683096] Unable to handle kernel paging request at virtual address 005f8141b42c [ 18.690315] Oops [#1] [ 18.692526] Modules linked in: phylink i2c_ocores(+) [ 18.697489] CPU: 0 PID: 147 Comm: systemd-udevd Tainted: GW 5.8.0-29-generic #31~20.04.1-Ubuntu [ 18.707566] epc: ffdf8141b42c ra : ffe000266012 sp : ffe1f4b3bd20 [ 18.714668] gp : ffe0013206b8 tp : ffe1f46f t0 : 0040 [ 18.721931] t1 : t2 : 000a s0 : ffe1f4b3bda0 [ 18.729123] s1 : a0 : 0003 a1 : ffe1f4a39018 [ 18.736314] a2 : 0001 a3 : a4 : ffdf8141b42c [ 18.739498] macb 1009.ethernet: Registered clk switch 'sifive-gemgxl-mgmt' [ 18.743528] a5 : 0003 a6 : ffe1f5603d98 a7 : ffe1f5603dc0 [ 18.743533] s2 : 0003 s3 : ffe1f4b3bdac s4 : 0001 [ 18.743537] s5 : ffe0012f02c8 s6 : ffe0012f02f0 s7 : 0002 [ 18.743542] s8 : ffe1f5d46000 s9 : 002ab15da010 s10: 0002 [ 18.743546] s11: ffe1f35a3680 t3 : 0002 t4 : 0402 [ 18.743553] t5 : ffe001220348 t6 : ffe001220350 [ 18.750909]
[Kernel-packages] [Bug 1934387] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1934387/+attachment/5508490/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/1934387 Title: Kernel panic booting on Unmatched with kernel 5.8 Status in linux-riscv-5.8 package in Ubuntu: New Bug description: This doesn't happen every time a boot is attempted, but very frequently. Log below: [ 15.024548] Loaded X.509 cert 'Canonical Ltd. Live Patch Signing: 14df34d1a87cf37625abec039ef2bf521249b969' [ 15.038870] Loaded X.509 cert 'Canonical Ltd. Kernel Module Signing: 88f752e560a1e0737e31163a466ad7b70a850c19' [ 15.048759] zswap: loaded using pool lzo/zbud [ 15.053091] Key type ._fscrypt registered [ 15.056452] Key type .fscrypt registered [ 15.060276] GPT:Primary header thinks Alt. header is not at the end of the disk. [ 15.060376] Key type fscrypt-provisioning registered [ 15.067784] GPT:7340031 != 62333951 [ 15.067790] GPT:Alternate GPT header not at the end of the disk. [ 15.082195] GPT:7340031 != 62333951 [ 15.085655] GPT: Use GNU Parted to correct GPT errors. [ 15.089268] Key type encrypted registered [ 15.090848] mmcblk0: p1 p12 p13 p14 p15 [ 15.094794] AppArmor: AppArmor sha1 policy hashing enabled [ 15.104197] ima: No TPM chip found, activating TPM-bypass! [ 15.109690] ima: Allocated hash algorithm: sha1 [ 15.114191] ima: No architecture policies found [ 15.118816] evm: Initialising EVM extended attributes: [ 15.123787] evm: security.selinux [ 15.127086] evm: security.SMACK64 [ 15.130380] evm: security.SMACK64EXEC [ 15.134030] evm: security.SMACK64TRANSMUTE [ 15.138108] evm: security.SMACK64MMAP [ 15.141755] evm: security.apparmor [ 15.145142] evm: security.ima [ 15.148081] evm: security.capability [ 15.151656] evm: HMAC attrs: 0x1 [ 18.062579] Freeing unused kernel memory: 308K [ 18.071639] [ cut here ] [ 18.075533] riscv/mm: Found insecure W+X mapping at address (ptrval)/0xffdff800 [ 18.084242] WARNING: CPU: 2 PID: 1 at arch/riscv/mm/ptdump.c:200 note_page+0x24c/0x252 [ 18.092116] Modules linked in: [ 18.095142] CPU: 2 PID: 1 Comm: swapper/0 Not tainted 5.8.0-29-generic #31~20.04.1-Ubuntu [ 18.103320] epc: ffe00020891a ra : ffe00020891a sp : ffe1f5bebb30 [ 18.110425] gp : ffe0013206b8 tp : ffe1f5be6780 t0 : ffe001336fa0 [ 18.117650] t1 : ffe001336f38 t2 : 0001fecd4000 s0 : ffe1f5bebb80 [ 18.124859] s1 : ffe1f5bebe10 a0 : 0053 a1 : 00020020 [ 18.132067] a2 : ffe1f5beb870 a3 : a4 : ffe0012200a0 [ 18.139277] a5 : ffe0012200a0 a6 : 00c6 a7 : ffe0006ebfee [ 18.146485] s2 : ffdff8001000 s3 : s4 : 0004 [ 18.153698] s5 : s6 : s7 : ffe1f5bebd20 [ 18.160917] s8 : ffdff8001000 s9 : ffe001322148 s10: ffdff8002000 [ 18.168116] s11: ffe000c16e20 t3 : 0003cca8 t4 : 0003cca8 [ 18.175323] t5 : t6 : ffe001331462 [ 18.180605] status: 00020120 badaddr: ffe1f5bebb30 cause: 0003 [ 18.188525] ---[ end trace ecc2ef275d977b46 ]--- [ 18.193629] Checked W+X mappings: failed, 513 W+X pages found [ 18.198865] Run /init as init process Loading, please wait... Starting version 245.4-4ubuntu3.7 [ 18.683096] Unable to handle kernel paging request at virtual address 005f8141b42c [ 18.690315] Oops [#1] [ 18.692526] Modules linked in: phylink i2c_ocores(+) [ 18.697489] CPU: 0 PID: 147 Comm: systemd-udevd Tainted: GW 5.8.0-29-generic #31~20.04.1-Ubuntu [ 18.707566] epc: ffdf8141b42c ra : ffe000266012 sp : ffe1f4b3bd20 [ 18.714668] gp : ffe0013206b8 tp : ffe1f46f t0 : 0040 [ 18.721931] t1 : t2 : 000a s0 : ffe1f4b3bda0 [ 18.729123] s1 : a0 : 0003 a1 : ffe1f4a39018 [ 18.736314] a2 : 0001 a3 : a4 : ffdf8141b42c [ 18.739498] macb 1009.ethernet: Registered clk switch 'sifive-gemgxl-mgmt' [ 18.743528] a5 : 0003 a6 : ffe1f5603d98 a7 : ffe1f5603dc0 [ 18.743533] s2 : 0003 s3 : ffe1f4b3bdac s4 : 0001 [ 18.743537] s5 : ffe0012f02c8 s6 : ffe0012f02f0 s7 : 0002 [ 18.743542] s8 : ffe1f5d46000 s9 : 002ab15da010 s10: 0002 [ 18.743546] s11: ffe1f35a3680 t3 : 0002 t4 : 0402 [ 18.743553] t5 : ffe001220348 t6 : ffe001220350 [
[Kernel-packages] [Bug 1934387] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1934387/+attachment/5508492/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/1934387 Title: Kernel panic booting on Unmatched with kernel 5.8 Status in linux-riscv-5.8 package in Ubuntu: New Bug description: This doesn't happen every time a boot is attempted, but very frequently. Log below: [ 15.024548] Loaded X.509 cert 'Canonical Ltd. Live Patch Signing: 14df34d1a87cf37625abec039ef2bf521249b969' [ 15.038870] Loaded X.509 cert 'Canonical Ltd. Kernel Module Signing: 88f752e560a1e0737e31163a466ad7b70a850c19' [ 15.048759] zswap: loaded using pool lzo/zbud [ 15.053091] Key type ._fscrypt registered [ 15.056452] Key type .fscrypt registered [ 15.060276] GPT:Primary header thinks Alt. header is not at the end of the disk. [ 15.060376] Key type fscrypt-provisioning registered [ 15.067784] GPT:7340031 != 62333951 [ 15.067790] GPT:Alternate GPT header not at the end of the disk. [ 15.082195] GPT:7340031 != 62333951 [ 15.085655] GPT: Use GNU Parted to correct GPT errors. [ 15.089268] Key type encrypted registered [ 15.090848] mmcblk0: p1 p12 p13 p14 p15 [ 15.094794] AppArmor: AppArmor sha1 policy hashing enabled [ 15.104197] ima: No TPM chip found, activating TPM-bypass! [ 15.109690] ima: Allocated hash algorithm: sha1 [ 15.114191] ima: No architecture policies found [ 15.118816] evm: Initialising EVM extended attributes: [ 15.123787] evm: security.selinux [ 15.127086] evm: security.SMACK64 [ 15.130380] evm: security.SMACK64EXEC [ 15.134030] evm: security.SMACK64TRANSMUTE [ 15.138108] evm: security.SMACK64MMAP [ 15.141755] evm: security.apparmor [ 15.145142] evm: security.ima [ 15.148081] evm: security.capability [ 15.151656] evm: HMAC attrs: 0x1 [ 18.062579] Freeing unused kernel memory: 308K [ 18.071639] [ cut here ] [ 18.075533] riscv/mm: Found insecure W+X mapping at address (ptrval)/0xffdff800 [ 18.084242] WARNING: CPU: 2 PID: 1 at arch/riscv/mm/ptdump.c:200 note_page+0x24c/0x252 [ 18.092116] Modules linked in: [ 18.095142] CPU: 2 PID: 1 Comm: swapper/0 Not tainted 5.8.0-29-generic #31~20.04.1-Ubuntu [ 18.103320] epc: ffe00020891a ra : ffe00020891a sp : ffe1f5bebb30 [ 18.110425] gp : ffe0013206b8 tp : ffe1f5be6780 t0 : ffe001336fa0 [ 18.117650] t1 : ffe001336f38 t2 : 0001fecd4000 s0 : ffe1f5bebb80 [ 18.124859] s1 : ffe1f5bebe10 a0 : 0053 a1 : 00020020 [ 18.132067] a2 : ffe1f5beb870 a3 : a4 : ffe0012200a0 [ 18.139277] a5 : ffe0012200a0 a6 : 00c6 a7 : ffe0006ebfee [ 18.146485] s2 : ffdff8001000 s3 : s4 : 0004 [ 18.153698] s5 : s6 : s7 : ffe1f5bebd20 [ 18.160917] s8 : ffdff8001000 s9 : ffe001322148 s10: ffdff8002000 [ 18.168116] s11: ffe000c16e20 t3 : 0003cca8 t4 : 0003cca8 [ 18.175323] t5 : t6 : ffe001331462 [ 18.180605] status: 00020120 badaddr: ffe1f5bebb30 cause: 0003 [ 18.188525] ---[ end trace ecc2ef275d977b46 ]--- [ 18.193629] Checked W+X mappings: failed, 513 W+X pages found [ 18.198865] Run /init as init process Loading, please wait... Starting version 245.4-4ubuntu3.7 [ 18.683096] Unable to handle kernel paging request at virtual address 005f8141b42c [ 18.690315] Oops [#1] [ 18.692526] Modules linked in: phylink i2c_ocores(+) [ 18.697489] CPU: 0 PID: 147 Comm: systemd-udevd Tainted: GW 5.8.0-29-generic #31~20.04.1-Ubuntu [ 18.707566] epc: ffdf8141b42c ra : ffe000266012 sp : ffe1f4b3bd20 [ 18.714668] gp : ffe0013206b8 tp : ffe1f46f t0 : 0040 [ 18.721931] t1 : t2 : 000a s0 : ffe1f4b3bda0 [ 18.729123] s1 : a0 : 0003 a1 : ffe1f4a39018 [ 18.736314] a2 : 0001 a3 : a4 : ffdf8141b42c [ 18.739498] macb 1009.ethernet: Registered clk switch 'sifive-gemgxl-mgmt' [ 18.743528] a5 : 0003 a6 : ffe1f5603d98 a7 : ffe1f5603dc0 [ 18.743533] s2 : 0003 s3 : ffe1f4b3bdac s4 : 0001 [ 18.743537] s5 : ffe0012f02c8 s6 : ffe0012f02f0 s7 : 0002 [ 18.743542] s8 : ffe1f5d46000 s9 : 002ab15da010 s10: 0002 [ 18.743546] s11: ffe1f35a3680 t3 : 0002 t4 : 0402 [ 18.743553] t5 : ffe001220348 t6 : ffe001220350 [ 18.750909]
[Kernel-packages] [Bug 1934387] Re: Kernel panic booting on Unmatched with kernel 5.8
apport information ** Tags added: apport-collected ** Description changed: This doesn't happen every time a boot is attempted, but very frequently. Log below: [ 15.024548] Loaded X.509 cert 'Canonical Ltd. Live Patch Signing: 14df34d1a87cf37625abec039ef2bf521249b969' [ 15.038870] Loaded X.509 cert 'Canonical Ltd. Kernel Module Signing: 88f752e560a1e0737e31163a466ad7b70a850c19' [ 15.048759] zswap: loaded using pool lzo/zbud [ 15.053091] Key type ._fscrypt registered [ 15.056452] Key type .fscrypt registered [ 15.060276] GPT:Primary header thinks Alt. header is not at the end of the disk. [ 15.060376] Key type fscrypt-provisioning registered [ 15.067784] GPT:7340031 != 62333951 [ 15.067790] GPT:Alternate GPT header not at the end of the disk. [ 15.082195] GPT:7340031 != 62333951 [ 15.085655] GPT: Use GNU Parted to correct GPT errors. [ 15.089268] Key type encrypted registered [ 15.090848] mmcblk0: p1 p12 p13 p14 p15 [ 15.094794] AppArmor: AppArmor sha1 policy hashing enabled [ 15.104197] ima: No TPM chip found, activating TPM-bypass! [ 15.109690] ima: Allocated hash algorithm: sha1 [ 15.114191] ima: No architecture policies found [ 15.118816] evm: Initialising EVM extended attributes: [ 15.123787] evm: security.selinux [ 15.127086] evm: security.SMACK64 [ 15.130380] evm: security.SMACK64EXEC [ 15.134030] evm: security.SMACK64TRANSMUTE [ 15.138108] evm: security.SMACK64MMAP [ 15.141755] evm: security.apparmor [ 15.145142] evm: security.ima [ 15.148081] evm: security.capability [ 15.151656] evm: HMAC attrs: 0x1 [ 18.062579] Freeing unused kernel memory: 308K [ 18.071639] [ cut here ] [ 18.075533] riscv/mm: Found insecure W+X mapping at address (ptrval)/0xffdff800 [ 18.084242] WARNING: CPU: 2 PID: 1 at arch/riscv/mm/ptdump.c:200 note_page+0x24c/0x252 [ 18.092116] Modules linked in: [ 18.095142] CPU: 2 PID: 1 Comm: swapper/0 Not tainted 5.8.0-29-generic #31~20.04.1-Ubuntu [ 18.103320] epc: ffe00020891a ra : ffe00020891a sp : ffe1f5bebb30 [ 18.110425] gp : ffe0013206b8 tp : ffe1f5be6780 t0 : ffe001336fa0 [ 18.117650] t1 : ffe001336f38 t2 : 0001fecd4000 s0 : ffe1f5bebb80 [ 18.124859] s1 : ffe1f5bebe10 a0 : 0053 a1 : 00020020 [ 18.132067] a2 : ffe1f5beb870 a3 : a4 : ffe0012200a0 [ 18.139277] a5 : ffe0012200a0 a6 : 00c6 a7 : ffe0006ebfee [ 18.146485] s2 : ffdff8001000 s3 : s4 : 0004 [ 18.153698] s5 : s6 : s7 : ffe1f5bebd20 [ 18.160917] s8 : ffdff8001000 s9 : ffe001322148 s10: ffdff8002000 [ 18.168116] s11: ffe000c16e20 t3 : 0003cca8 t4 : 0003cca8 [ 18.175323] t5 : t6 : ffe001331462 [ 18.180605] status: 00020120 badaddr: ffe1f5bebb30 cause: 0003 [ 18.188525] ---[ end trace ecc2ef275d977b46 ]--- [ 18.193629] Checked W+X mappings: failed, 513 W+X pages found [ 18.198865] Run /init as init process Loading, please wait... Starting version 245.4-4ubuntu3.7 [ 18.683096] Unable to handle kernel paging request at virtual address 005f8141b42c [ 18.690315] Oops [#1] [ 18.692526] Modules linked in: phylink i2c_ocores(+) [ 18.697489] CPU: 0 PID: 147 Comm: systemd-udevd Tainted: GW 5.8.0-29-generic #31~20.04.1-Ubuntu [ 18.707566] epc: ffdf8141b42c ra : ffe000266012 sp : ffe1f4b3bd20 [ 18.714668] gp : ffe0013206b8 tp : ffe1f46f t0 : 0040 [ 18.721931] t1 : t2 : 000a s0 : ffe1f4b3bda0 [ 18.729123] s1 : a0 : 0003 a1 : ffe1f4a39018 [ 18.736314] a2 : 0001 a3 : a4 : ffdf8141b42c [ 18.739498] macb 1009.ethernet: Registered clk switch 'sifive-gemgxl-mgmt' [ 18.743528] a5 : 0003 a6 : ffe1f5603d98 a7 : ffe1f5603dc0 [ 18.743533] s2 : 0003 s3 : ffe1f4b3bdac s4 : 0001 [ 18.743537] s5 : ffe0012f02c8 s6 : ffe0012f02f0 s7 : 0002 [ 18.743542] s8 : ffe1f5d46000 s9 : 002ab15da010 s10: 0002 [ 18.743546] s11: ffe1f35a3680 t3 : 0002 t4 : 0402 [ 18.743553] t5 : ffe001220348 t6 : ffe001220350 [ 18.750909] macb 1009.ethernet: GEM doesn't support hardware ptp. [ 18.757942] status: 00020100 badaddr: 005f8141b42c cause: 000c [ 18.757998] ---[ end trace ecc2ef275d977b47 ]--- [ 18.765916] libphy: MACB_mii_bus: probed [ 18.772384] Kernel panic - not syncing: Fatal exception in interrupt [ 18.821245] SMP: stopping secondary CPUs
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-kvm/5.8.0.1032.34)
All autopkgtests for the newly accepted linux-meta-kvm (5.8.0.1032.34) for groovy have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-450-server/450.119.04-0ubuntu0.20.10.2 (amd64) nvidia-graphics-drivers-340/340.108-0ubuntu5.20.10.2 (amd64) nvidia-graphics-drivers-460/460.80-0ubuntu0.20.10.2 (amd64) nvidia-graphics-drivers-418-server/418.197.02-0ubuntu0.20.10.1 (amd64) virtualbox-hwe/6.1.16-dfsg-6ubuntu1.20.10.1 (amd64) nvidia-graphics-drivers-390/390.143-0ubuntu0.20.10.1 (amd64) nvidia-graphics-drivers-460-server/460.73.01-0ubuntu0.20.10.1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/groovy/update_excuses.html#linux-meta-kvm [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932163] Re: evdi/1.7.0+dfsg-1ubuntu1~20.04.3 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1
Here is a debdiff against the version in hirsute. It builds fine against 5.11.0-22-generic, and loads. Cascardo. ** Patch added: "debdiff against version in hirsute" https://bugs.launchpad.net/ubuntu/+source/evdi/+bug/1932163/+attachment/5508488/+files/evdi_1.9.1-1ubuntu3~21.04.1.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1932163 Title: evdi/1.7.0+dfsg-1ubuntu1~20.04.3 ADT test failure with linux- hwe-5.11/5.11.0-20.21~20.04.1 Status in evdi package in Ubuntu: New Status in linux-hwe-5.11 package in Ubuntu: New Status in evdi source package in Focal: In Progress Status in linux-hwe-5.11 source package in Focal: New Status in evdi source package in Hirsute: New Status in linux-hwe-5.11 source package in Hirsute: New Bug description: [Impact] focal users running latest hwe kernel, version 5.11, won't be able to use evdi-dkms. [Test case] Built evdi dkms and loaded the evdi module on 5.4, 5.8 and 5.11 kernels. [Potential regression] DisplayLink devices will stop working. -- This is a scripted bug report about ADT failures while running evdi tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/e/evdi/20210611_210228_7f0da@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/arm64/e/evdi/20210612_122245_bd52e@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/e/evdi/20210611_210028_038f3@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/e/evdi/20210611_205902_3dc65@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evdi/+bug/1932163/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932163] Re: evdi/1.7.0+dfsg-1ubuntu1~20.04.3 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1
Well, having a newer version in focal is less than ideal. I will prepare a quick backport and test it on hirsute. Should I do the same for groovy? Cascardo. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1932163 Title: evdi/1.7.0+dfsg-1ubuntu1~20.04.3 ADT test failure with linux- hwe-5.11/5.11.0-20.21~20.04.1 Status in evdi package in Ubuntu: New Status in linux-hwe-5.11 package in Ubuntu: New Status in evdi source package in Focal: In Progress Status in linux-hwe-5.11 source package in Focal: New Status in evdi source package in Hirsute: New Status in linux-hwe-5.11 source package in Hirsute: New Bug description: [Impact] focal users running latest hwe kernel, version 5.11, won't be able to use evdi-dkms. [Test case] Built evdi dkms and loaded the evdi module on 5.4, 5.8 and 5.11 kernels. [Potential regression] DisplayLink devices will stop working. -- This is a scripted bug report about ADT failures while running evdi tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/e/evdi/20210611_210228_7f0da@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/arm64/e/evdi/20210612_122245_bd52e@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/e/evdi/20210611_210028_038f3@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/e/evdi/20210611_205902_3dc65@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evdi/+bug/1932163/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934387] Re: Kernel panic booting on Unmatched with kernel 5.8
** Changed in: linux-riscv-5.8 (Ubuntu) Milestone: None => ubuntu-20.04.3 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/1934387 Title: Kernel panic booting on Unmatched with kernel 5.8 Status in linux-riscv-5.8 package in Ubuntu: New Bug description: This doesn't happen every time a boot is attempted, but very frequently. Log below: [ 15.024548] Loaded X.509 cert 'Canonical Ltd. Live Patch Signing: 14df34d1a87cf37625abec039ef2bf521249b969' [ 15.038870] Loaded X.509 cert 'Canonical Ltd. Kernel Module Signing: 88f752e560a1e0737e31163a466ad7b70a850c19' [ 15.048759] zswap: loaded using pool lzo/zbud [ 15.053091] Key type ._fscrypt registered [ 15.056452] Key type .fscrypt registered [ 15.060276] GPT:Primary header thinks Alt. header is not at the end of the disk. [ 15.060376] Key type fscrypt-provisioning registered [ 15.067784] GPT:7340031 != 62333951 [ 15.067790] GPT:Alternate GPT header not at the end of the disk. [ 15.082195] GPT:7340031 != 62333951 [ 15.085655] GPT: Use GNU Parted to correct GPT errors. [ 15.089268] Key type encrypted registered [ 15.090848] mmcblk0: p1 p12 p13 p14 p15 [ 15.094794] AppArmor: AppArmor sha1 policy hashing enabled [ 15.104197] ima: No TPM chip found, activating TPM-bypass! [ 15.109690] ima: Allocated hash algorithm: sha1 [ 15.114191] ima: No architecture policies found [ 15.118816] evm: Initialising EVM extended attributes: [ 15.123787] evm: security.selinux [ 15.127086] evm: security.SMACK64 [ 15.130380] evm: security.SMACK64EXEC [ 15.134030] evm: security.SMACK64TRANSMUTE [ 15.138108] evm: security.SMACK64MMAP [ 15.141755] evm: security.apparmor [ 15.145142] evm: security.ima [ 15.148081] evm: security.capability [ 15.151656] evm: HMAC attrs: 0x1 [ 18.062579] Freeing unused kernel memory: 308K [ 18.071639] [ cut here ] [ 18.075533] riscv/mm: Found insecure W+X mapping at address (ptrval)/0xffdff800 [ 18.084242] WARNING: CPU: 2 PID: 1 at arch/riscv/mm/ptdump.c:200 note_page+0x24c/0x252 [ 18.092116] Modules linked in: [ 18.095142] CPU: 2 PID: 1 Comm: swapper/0 Not tainted 5.8.0-29-generic #31~20.04.1-Ubuntu [ 18.103320] epc: ffe00020891a ra : ffe00020891a sp : ffe1f5bebb30 [ 18.110425] gp : ffe0013206b8 tp : ffe1f5be6780 t0 : ffe001336fa0 [ 18.117650] t1 : ffe001336f38 t2 : 0001fecd4000 s0 : ffe1f5bebb80 [ 18.124859] s1 : ffe1f5bebe10 a0 : 0053 a1 : 00020020 [ 18.132067] a2 : ffe1f5beb870 a3 : a4 : ffe0012200a0 [ 18.139277] a5 : ffe0012200a0 a6 : 00c6 a7 : ffe0006ebfee [ 18.146485] s2 : ffdff8001000 s3 : s4 : 0004 [ 18.153698] s5 : s6 : s7 : ffe1f5bebd20 [ 18.160917] s8 : ffdff8001000 s9 : ffe001322148 s10: ffdff8002000 [ 18.168116] s11: ffe000c16e20 t3 : 0003cca8 t4 : 0003cca8 [ 18.175323] t5 : t6 : ffe001331462 [ 18.180605] status: 00020120 badaddr: ffe1f5bebb30 cause: 0003 [ 18.188525] ---[ end trace ecc2ef275d977b46 ]--- [ 18.193629] Checked W+X mappings: failed, 513 W+X pages found [ 18.198865] Run /init as init process Loading, please wait... Starting version 245.4-4ubuntu3.7 [ 18.683096] Unable to handle kernel paging request at virtual address 005f8141b42c [ 18.690315] Oops [#1] [ 18.692526] Modules linked in: phylink i2c_ocores(+) [ 18.697489] CPU: 0 PID: 147 Comm: systemd-udevd Tainted: GW 5.8.0-29-generic #31~20.04.1-Ubuntu [ 18.707566] epc: ffdf8141b42c ra : ffe000266012 sp : ffe1f4b3bd20 [ 18.714668] gp : ffe0013206b8 tp : ffe1f46f t0 : 0040 [ 18.721931] t1 : t2 : 000a s0 : ffe1f4b3bda0 [ 18.729123] s1 : a0 : 0003 a1 : ffe1f4a39018 [ 18.736314] a2 : 0001 a3 : a4 : ffdf8141b42c [ 18.739498] macb 1009.ethernet: Registered clk switch 'sifive-gemgxl-mgmt' [ 18.743528] a5 : 0003 a6 : ffe1f5603d98 a7 : ffe1f5603dc0 [ 18.743533] s2 : 0003 s3 : ffe1f4b3bdac s4 : 0001 [ 18.743537] s5 : ffe0012f02c8 s6 : ffe0012f02f0 s7 : 0002 [ 18.743542] s8 : ffe1f5d46000 s9 : 002ab15da010 s10: 0002 [ 18.743546] s11: ffe1f35a3680 t3 : 0002 t4 : 0402 [ 18.743553] t5 : ffe001220348 t6 : ffe001220350 [ 18.750909] macb 1009.ethernet: GEM doesn't support hardware ptp. [
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-oracle/5.11.0.1012.12)
All autopkgtests for the newly accepted linux-meta-oracle (5.11.0.1012.12) for hirsute have finished running. The following regressions have been reported in tests triggered by the package: systemd/247.3-3ubuntu3.1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/hirsute/update_excuses.html#linux-meta-oracle [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837937] Re: CRASH
** Changed in: systemd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1837937 Title: CRASH Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Invalid Bug description: The screen froze but the mouse was still moving then it all froze and said systemd-journal not able to write entry. I had to press the power button. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.2.0-9-generic 5.2.0-9.10 ProcVersionSignature: Ubuntu 5.2.0-9.10-generic 5.2.1 Uname: Linux 5.2.0-9-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: administrator 2068 F pulseaudio /dev/snd/controlC0: administrator 2068 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Jul 25 15:11:47 2019 InstallationDate: Installed on 2019-06-05 (50 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190605) MachineType: HP HP Notebook ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-9-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.2.0-9-generic N/A linux-backports-modules-5.2.0-9-generic N/A linux-firmware 1.181 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.24 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 82F6 dmi.board.vendor: HP dmi.board.version: 40.41 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.24:bd06/15/2017:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn82F6:rvr40.41:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: X7T78UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: administrator 2852 F pulseaudio /dev/snd/controlC0: administrator 2852 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-06-05 (51 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190605) MachineType: HP HP Notebook Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-9-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash crashkernel=512M-:192M vt.handoff=7 ProcVersionSignature: Ubuntu 5.2.0-9.10-generic 5.2.1 RelatedPackageVersions: linux-restricted-modules-5.2.0-9-generic N/A linux-backports-modules-5.2.0-9-generic N/A linux-firmware 1.181 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: eoan Uname: Linux 5.2.0-9-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/15/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.24 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 82F6 dmi.board.vendor: HP dmi.board.version: 40.41 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.24:bd06/15/2017:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn82F6:rvr40.41:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: X7T78UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: administrator 2852 F pulseaudio /dev/snd/controlC0: administrator 2852 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-06-05 (51 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190605) MachineType: HP HP Notebook Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine:
[Kernel-packages] [Bug 1771431] Re: Lenovo Essential Wireless Keyboard doesn't works (Primax Electronics manufacturer)
The technology has must be advanced in some gadgets like a wireless mouse. A Wireless mouse is a part of the hardware that is used to communicate with computers, laptops.https://technumus.com/hp-wireless-keyboard-without-a-receiver/;>HP wireless keyboard without a receiver Wireless mouse easy to use better than to wired mouse it wireless mouse beneficial to work easily and easy to communicate to the receiver. some keyboard some basic features like a Bluetooth as matter. This HP Wireless mouse has not reciever automatically connect to devise and easy to use. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1771431 Title: Lenovo Essential Wireless Keyboard doesn't works (Primax Electronics manufacturer) Status in linux: Confirmed Status in linux package in Ubuntu: Triaged Status in linux package in Fedora: Confirmed Bug description: Hi I got an issue on Ubuntu 18.04 with latest packages. uname -a: Linux MyLaptop 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux lshw: *-usb:0 description: Keyboard product: Lenovo USB Receiver vendor: Lenovo physical id: 3 bus info: usb@1:3 version: 1.05 capabilities: usb-2.00 configuration: driver=usbhid maxpower=100mA speed=12Mbit/s My wireless keyboard is not working, Ubuntu only recognize some special keys (Super, Ctrl, Shift, Alt) This is a Mouse+Keyboard combo using a wireless receiver by usb: lsusb: Bus 001 Device 005: ID 17ef:609b Lenovo Mouse works fine, and in Windows 10 it works with no issues. I found multiple reported problems with this keyboard in other distros (and from Asus too, as the real manufacturer is Primax Electronics). https://forums.lenovo.com/t5/Linux-Discussion/Professional-Wireless-Keyboard-not-working-on-Linux/td-p/3726486 https://ubuntuforums.org/showthread.php?t=2378862 https://askubuntu.com/questions/897729/lenovo-professional-wireless-keyboard-and-mouse-combo-not-working-in-ubuntu https://forums.linuxmint.com/viewtopic.php?f=49=260093=20a073d5dd8abb1b7f23be608d7fdfd7 https://unix.stackexchange.com/questions/377830/linux-hid-driver-for-primax-wireless-keyboards/ REPORTS ON KERNEL MAILING LISTS: https://www.spinics.net/lists/linux-usb/msg168719.html https://www.spinics.net/lists/linux-input/msg56210.html https://www.spinics.net/lists/linux-usb/msg173012.html https://www.spinics.net/lists/linux-input/msg58221.html There is a workaround (I still didn't tried) but it needs to compile an specific driver. https://github.com/y-trudeau/linux_lenovo_ultraslim_plus There is already a kernel report about this. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-generic 4.15.0.20.23 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: julian 1342 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue May 15 15:53:41 2018 InstallationDate: Installed on 2018-05-14 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 20FJS0NT07 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=818481db-36cb-4dba-8da5-8ecf15750b3b ro noapic acpi=off vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/27/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N1KET38W (1.25 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FJS0NT07 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1KET38W(1.25):bd03/27/2018:svnLENOVO:pn20FJS0NT07:pvrThinkPadT560:rvnLENOVO:rn20FJS0NT07:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T560 dmi.product.name: 20FJS0NT07 dmi.product.version: ThinkPad T560 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/kernel/+bug/1771431/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934387] [NEW] Kernel panic booting on Unmatched with kernel 5.8
Public bug reported: This doesn't happen every time a boot is attempted, but very frequently. Log below: [ 15.024548] Loaded X.509 cert 'Canonical Ltd. Live Patch Signing: 14df34d1a87cf37625abec039ef2bf521249b969' [ 15.038870] Loaded X.509 cert 'Canonical Ltd. Kernel Module Signing: 88f752e560a1e0737e31163a466ad7b70a850c19' [ 15.048759] zswap: loaded using pool lzo/zbud [ 15.053091] Key type ._fscrypt registered [ 15.056452] Key type .fscrypt registered [ 15.060276] GPT:Primary header thinks Alt. header is not at the end of the disk. [ 15.060376] Key type fscrypt-provisioning registered [ 15.067784] GPT:7340031 != 62333951 [ 15.067790] GPT:Alternate GPT header not at the end of the disk. [ 15.082195] GPT:7340031 != 62333951 [ 15.085655] GPT: Use GNU Parted to correct GPT errors. [ 15.089268] Key type encrypted registered [ 15.090848] mmcblk0: p1 p12 p13 p14 p15 [ 15.094794] AppArmor: AppArmor sha1 policy hashing enabled [ 15.104197] ima: No TPM chip found, activating TPM-bypass! [ 15.109690] ima: Allocated hash algorithm: sha1 [ 15.114191] ima: No architecture policies found [ 15.118816] evm: Initialising EVM extended attributes: [ 15.123787] evm: security.selinux [ 15.127086] evm: security.SMACK64 [ 15.130380] evm: security.SMACK64EXEC [ 15.134030] evm: security.SMACK64TRANSMUTE [ 15.138108] evm: security.SMACK64MMAP [ 15.141755] evm: security.apparmor [ 15.145142] evm: security.ima [ 15.148081] evm: security.capability [ 15.151656] evm: HMAC attrs: 0x1 [ 18.062579] Freeing unused kernel memory: 308K [ 18.071639] [ cut here ] [ 18.075533] riscv/mm: Found insecure W+X mapping at address (ptrval)/0xffdff800 [ 18.084242] WARNING: CPU: 2 PID: 1 at arch/riscv/mm/ptdump.c:200 note_page+0x24c/0x252 [ 18.092116] Modules linked in: [ 18.095142] CPU: 2 PID: 1 Comm: swapper/0 Not tainted 5.8.0-29-generic #31~20.04.1-Ubuntu [ 18.103320] epc: ffe00020891a ra : ffe00020891a sp : ffe1f5bebb30 [ 18.110425] gp : ffe0013206b8 tp : ffe1f5be6780 t0 : ffe001336fa0 [ 18.117650] t1 : ffe001336f38 t2 : 0001fecd4000 s0 : ffe1f5bebb80 [ 18.124859] s1 : ffe1f5bebe10 a0 : 0053 a1 : 00020020 [ 18.132067] a2 : ffe1f5beb870 a3 : a4 : ffe0012200a0 [ 18.139277] a5 : ffe0012200a0 a6 : 00c6 a7 : ffe0006ebfee [ 18.146485] s2 : ffdff8001000 s3 : s4 : 0004 [ 18.153698] s5 : s6 : s7 : ffe1f5bebd20 [ 18.160917] s8 : ffdff8001000 s9 : ffe001322148 s10: ffdff8002000 [ 18.168116] s11: ffe000c16e20 t3 : 0003cca8 t4 : 0003cca8 [ 18.175323] t5 : t6 : ffe001331462 [ 18.180605] status: 00020120 badaddr: ffe1f5bebb30 cause: 0003 [ 18.188525] ---[ end trace ecc2ef275d977b46 ]--- [ 18.193629] Checked W+X mappings: failed, 513 W+X pages found [ 18.198865] Run /init as init process Loading, please wait... Starting version 245.4-4ubuntu3.7 [ 18.683096] Unable to handle kernel paging request at virtual address 005f8141b42c [ 18.690315] Oops [#1] [ 18.692526] Modules linked in: phylink i2c_ocores(+) [ 18.697489] CPU: 0 PID: 147 Comm: systemd-udevd Tainted: GW 5.8.0-29-generic #31~20.04.1-Ubuntu [ 18.707566] epc: ffdf8141b42c ra : ffe000266012 sp : ffe1f4b3bd20 [ 18.714668] gp : ffe0013206b8 tp : ffe1f46f t0 : 0040 [ 18.721931] t1 : t2 : 000a s0 : ffe1f4b3bda0 [ 18.729123] s1 : a0 : 0003 a1 : ffe1f4a39018 [ 18.736314] a2 : 0001 a3 : a4 : ffdf8141b42c [ 18.739498] macb 1009.ethernet: Registered clk switch 'sifive-gemgxl-mgmt' [ 18.743528] a5 : 0003 a6 : ffe1f5603d98 a7 : ffe1f5603dc0 [ 18.743533] s2 : 0003 s3 : ffe1f4b3bdac s4 : 0001 [ 18.743537] s5 : ffe0012f02c8 s6 : ffe0012f02f0 s7 : 0002 [ 18.743542] s8 : ffe1f5d46000 s9 : 002ab15da010 s10: 0002 [ 18.743546] s11: ffe1f35a3680 t3 : 0002 t4 : 0402 [ 18.743553] t5 : ffe001220348 t6 : ffe001220350 [ 18.750909] macb 1009.ethernet: GEM doesn't support hardware ptp. [ 18.757942] status: 00020100 badaddr: 005f8141b42c cause: 000c [ 18.757998] ---[ end trace ecc2ef275d977b47 ]--- [ 18.765916] libphy: MACB_mii_bus: probed [ 18.772384] Kernel panic - not syncing: Fatal exception in interrupt [ 18.821245] SMP: stopping secondary CPUs [ 18.825167] ---[ end Kernel panic - not syncing: Fatal exception in interrupt ]--- ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-29-generic 5.8.0-29.31~20.04.1
[Kernel-packages] [Bug 1934099] Re: 4.15.0-149-generic: lxc-attach lsm/lsm.c: lsm_process_label_set_at: 174 Operation not permitted - Failed to set AppArmor label "lxc-container-default-cgns"
*** This bug is a duplicate of bug 1934187 *** https://bugs.launchpad.net/bugs/1934187 ** This bug has been marked a duplicate of bug 1934187 lxd exec fails -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1934099 Title: 4.15.0-149-generic: lxc-attach lsm/lsm.c: lsm_process_label_set_at: 174 Operation not permitted - Failed to set AppArmor label "lxc- container-default-cgns" Status in linux package in Ubuntu: New Bug description: Hello. When testing with the bionic-proposed repository, we found that the 4.15.0-149-generic break the lxc-attach command with the following error: lxc-attach: bidule: lsm/lsm.c: lsm_process_label_set_at: 174 Operation not permitted - Failed to set AppArmor label "lxc-container- default-cgns" We don't have this issue with the current 4.15.0-147. There is no issue using the --elevated-privileges option of lxc- attach. I join the debug log of “lxc-attach -n bidule -l debug”. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-149-generic 4.15.0-149.153 ProcVersionSignature: Ubuntu 4.15.0-149.153-generic 4.15.18 Uname: Linux 4.15.0-149-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 juin 30 10:15 seq crw-rw 1 root audio 116, 33 juin 30 10:15 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.24 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Wed Jun 30 10:21:54 2021 HibernationDevice: RESUME=/dev/mapper/bionic--vg-swap_1 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-149-generic root=/dev/mapper/hostname--vg-root ro console=tty1 RelatedPackageVersions: linux-restricted-modules-4.15.0-149-generic N/A linux-backports-modules-4.15.0-149-generic N/A linux-firmware 1.173.20 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.12.0-1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-3.1 dmi.modalias: dmi:bvnSeaBIOS:bvr1.12.0-1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-3.1:cvnQEMU:ct1:cvrpc-i440fx-3.1: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-3.1 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934099/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-gcp-5.11/5.11.0.1013.14~20.04.12)
All autopkgtests for the newly accepted linux-meta-gcp-5.11 (5.11.0.1013.14~20.04.12) for focal have finished running. The following regressions have been reported in tests triggered by the package: linux-gcp-5.11/5.11.0-1013.14~20.04.1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-gcp-5.11 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934313] [NEW] Export xfrm_policy_lookup_bytype function
Public bug reported: Export policy lookup function so drivers could lookup a policy that match specific criteria. ** Affects: linux-bluefield (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1934313 Title: Export xfrm_policy_lookup_bytype function Status in linux-bluefield package in Ubuntu: New Bug description: Export policy lookup function so drivers could lookup a policy that match specific criteria. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1934313/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932159] Re: bcmwl/6.30.223.271+bdcom-0ubuntu7~20.04.2 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1
$ dput ppa:ci-train-ppa-service/4601 bcmwl_6.30.223.271+bdcom-0ubuntu7~20.04.3_source.changes D: Splitting host argument out of ppa:ci-train-ppa-service/4601. D: Setting host argument. Checking signature on .changes gpg: /tmp/bcmwl_6.30.223.271+bdcom-0ubuntu7~20.04.3_source.changes: Valid signature from 9B8EC849D5EF70ED Checking signature on .dsc gpg: /tmp/bcmwl_6.30.223.271+bdcom-0ubuntu7~20.04.3.dsc: Valid signature from 9B8EC849D5EF70ED Uploading to ppa (via sftp to ppa.launchpad.net): Uploading bcmwl_6.30.223.271+bdcom-0ubuntu7~20.04.3.dsc: done. Uploading bcmwl_6.30.223.271+bdcom-0ubuntu7~20.04.3.diff.gz: done. Uploading bcmwl_6.30.223.271+bdcom-0ubuntu7~20.04.3_source.buildinfo: done. Uploading bcmwl_6.30.223.271+bdcom-0ubuntu7~20.04.3_source.changes: done. Successfully uploaded packages. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1932159 Title: bcmwl/6.30.223.271+bdcom-0ubuntu7~20.04.2 ADT test failure with linux- hwe-5.11/5.11.0-20.21~20.04.1 Status in bcmwl package in Ubuntu: Fix Released Status in linux-hwe-5.11 package in Ubuntu: Invalid Status in bcmwl source package in Focal: In Progress Status in linux-hwe-5.11 source package in Focal: Invalid Bug description: This is a scripted bug report about ADT failures while running bcmwl tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/b/bcmwl/20210611_210047_c4a48@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1932159/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932163] Re: evdi/1.7.0+dfsg-1ubuntu1~20.04.3 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1
@cascardo are fixes done in ubuntu2 and ubuntu3 also needed in hirsute? If yes, can you prepare SRU for hirsute as well? If not, can you please explain why? ** Also affects: evdi (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux-hwe-5.11 (Ubuntu Hirsute) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1932163 Title: evdi/1.7.0+dfsg-1ubuntu1~20.04.3 ADT test failure with linux- hwe-5.11/5.11.0-20.21~20.04.1 Status in evdi package in Ubuntu: New Status in linux-hwe-5.11 package in Ubuntu: New Status in evdi source package in Focal: In Progress Status in linux-hwe-5.11 source package in Focal: New Status in evdi source package in Hirsute: New Status in linux-hwe-5.11 source package in Hirsute: New Bug description: [Impact] focal users running latest hwe kernel, version 5.11, won't be able to use evdi-dkms. [Test case] Built evdi dkms and loaded the evdi module on 5.4, 5.8 and 5.11 kernels. [Potential regression] DisplayLink devices will stop working. -- This is a scripted bug report about ADT failures while running evdi tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/e/evdi/20210611_210228_7f0da@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/arm64/e/evdi/20210612_122245_bd52e@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/e/evdi/20210611_210028_038f3@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/e/evdi/20210611_205902_3dc65@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evdi/+bug/1932163/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831276] Re: Gnome wayland hangs with nvidia driver on video load/changing tabs
** Changed in: nvidia-graphics-drivers-418 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-418 in Ubuntu. https://bugs.launchpad.net/bugs/1831276 Title: Gnome wayland hangs with nvidia driver on video load/changing tabs Status in nvidia-graphics-drivers-418 package in Ubuntu: Invalid Bug description: This is on nvidia 430, which is only packages in PPAs so far. I've reproduced this by just playing a Youtube video (Not using wayland enabled Firefox, but Beta snappy version) or by switching tabs while on a google hangout meet. The video or hangout continues but the screen is fully locked up. Switch to other VTs does not work. Only error reported is: May 28 21:30:06 desktop kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x1c00] Flip event timeout on head 0 Ubuntu 19.04 nvidia-driver-430 430.14-0ubuntu0~gpu19.04.1 snap firefox 68.0b5-1 2019-05-28 (221) gnome-shell3.32.0+git20190410-1ubuntu1 mutter 3.32.0+git20190410-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418/+bug/1831276/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878279] Re: MSFT0004:00 06CB:CD98 Touchpad/trackpad mouse randomly not recognized from any given boot
I've been working with a Fedora reporter to try and solve the case where pci=nocrs helps to get a working touchpad, see: https://bugzilla.redhat.com/show_bug.cgi?id=1868899 Thanks to the latest set of logs attached there, I now am finally starting to understand what is going on here. Your BIOS claims that any memory between 0x4bc5-0xcfff is reserved: [0.00] BIOS-e820: [mem 0x4bc5-0xcfff] reserved But then continuous with placing the iomem window for PCI devices inside that reserved range: [0.609988] pci_bus :00: root bus resource [mem 0x6540-0xbfff window] This confuses the kernel and makes it unable to assign PCI iomem to devices which have not already been assigned iomem by the BIOS, like the I2C-controller used for the touchpad. If you are interested in / curious about the low level details, I'm discussing this with the kernel PCI developers (including figuring out how to deal with this) here: https://lore.kernel.org/linux-pci/7d80f639-0768-850b-5313-3bdedf0a5...@redhat.com/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe in Ubuntu. https://bugs.launchpad.net/bugs/1878279 Title: MSFT0004:00 06CB:CD98 Touchpad/trackpad mouse randomly not recognized from any given boot Status in Linux: Confirmed Status in Ubuntu: Confirmed Status in linux-signed-hwe package in Ubuntu: In Progress Status in linux-signed-hwe package in Fedora: New Bug description: Touchpad 'Buttonless Mylar surface multi-touch touchpad' doesn't work at all (No response from the Touchpad) for notebook 'Lenovo Ideapad 5 14IIL05 81YH' from first system start on. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-29-generic 5.4.0-29.33 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tilman 1607 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 12 21:22:22 2020 InstallationDate: Installed on 2020-05-12 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YH ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=bb961a96-8855-4e50-814d-7994235377c3 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-29-generic N/A linux-backports-modules-5.4.0-29-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DSCN23WW(V1.09) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 5 14IIL05 dmi.modalias: dmi:bvnLENOVO:bvrDSCN23WW(V1.09):bd03/25/2020:svnLENOVO:pn81YH:pvrIdeaPad514IIL05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad514IIL05: dmi.product.family: IdeaPad 5 14IIL05 dmi.product.name: 81YH dmi.product.sku: LENOVO_MT_81YH_BU_idea_FM_IdeaPad 5 14IIL05 dmi.product.version: IdeaPad 5 14IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1878279/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932168] Re: oss4/4.2-build2010-5ubuntu6~20.04.2 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1
Building in security only bileto ppa $ dput ppa:ci-train-ppa-service/4601 oss4_4.2-build2010-5ubuntu6~20.04.3_source.changes D: Splitting host argument out of ppa:ci-train-ppa-service/4601. D: Setting host argument. Checking signature on .changes gpg: /tmp/oss4_4.2-build2010-5ubuntu6~20.04.3_source.changes: Valid signature from 9B8EC849D5EF70ED Checking signature on .dsc gpg: /tmp/oss4_4.2-build2010-5ubuntu6~20.04.3.dsc: Valid signature from 9B8EC849D5EF70ED Uploading to ppa (via sftp to ppa.launchpad.net): Uploading oss4_4.2-build2010-5ubuntu6~20.04.3.dsc: done. Uploading oss4_4.2-build2010-5ubuntu6~20.04.3.debian.tar.xz: done. Uploading oss4_4.2-build2010-5ubuntu6~20.04.3_source.buildinfo: done. Uploading oss4_4.2-build2010-5ubuntu6~20.04.3_source.changes: done. Successfully uploaded packages. ** Description changed: [Impact] oss4 dkms will fail to build on 5.11 kernels on focal, preventing users from using those modules on more recent kernels. [Test case] Install the package and make sure it builds. [Fix] Conditionally define a function that is not used on the Linux port when LICENSED_VERSION is undefined. [Fix risk] Licensed versions will fail to build, but we don't do those. Other ports should not fail as we only patch the Linux port. [Potential regression] The dkms package may still fail to build, install or load. Or sound might not work on systems that depend on oss4. --- This is a scripted bug report about ADT failures while running oss4 tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/o/oss4/20210611_210018_1dcc5@/log.gz + + [Other] + + NB! dkms ftbfs fixes must be built in security, such that after SRU + process in -proposed & -updates it can be copied into -security pocket + too. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1932168 Title: oss4/4.2-build2010-5ubuntu6~20.04.2 ADT test failure with linux- hwe-5.11/5.11.0-20.21~20.04.1 Status in linux-hwe-5.11 package in Ubuntu: New Status in oss4 package in Ubuntu: New Status in linux-hwe-5.11 source package in Focal: New Status in oss4 source package in Focal: In Progress Bug description: [Impact] oss4 dkms will fail to build on 5.11 kernels on focal, preventing users from using those modules on more recent kernels. [Test case] Install the package and make sure it builds. [Fix] Conditionally define a function that is not used on the Linux port when LICENSED_VERSION is undefined. [Fix risk] Licensed versions will fail to build, but we don't do those. Other ports should not fail as we only patch the Linux port. [Potential regression] The dkms package may still fail to build, install or load. Or sound might not work on systems that depend on oss4. --- This is a scripted bug report about ADT failures while running oss4 tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/o/oss4/20210611_210018_1dcc5@/log.gz [Other] NB! dkms ftbfs fixes must be built in security, such that after SRU process in -proposed & -updates it can be copied into -security pocket too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1932168/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934304] [NEW] i2c-mlxbf.c: prevent stack overflow in mlxbf_i2c_smbus_start_transaction
Public bug reported: SRU Justification: [Impact] There could be stack overflow in mlxbf_i2c_smbus_start_transaction(). memcpy() is called in a loop while 'operation->length' upper bound is not checked and 'data_idx' also increments. More details: The operation length is verified by the caller functions so it cannot exceed I2C_SMBUS_BLOCK_MAX bytes (32 bytes) for each operation that is a part of the write. Data_desc array is 128 bytes in size. So potentially a request which consists of 4 writes, 32 bytes each can trigger an off-by-one or off-by-two overflow, because the first byte of data_desc is used by addr, effectively decreasing the available data_desc buffer size by one. Functions like mlx_smbus_i2c_block_func() that prepare the request also set the length of the first write operation to one and store the command id there, so the target buffer size again decreases data_desc by one, making it two bytes less than expected. [Fix] * Add a check for "operation->length" and data_idx and return error if reached upper bound. [Test Case] * Test the i2c-mlxbf.c driver using IPMB functionality. [Regression Potential] This fix returns a negative value to indicate that a transaction has failed. So it will catch more transactions failures. ** Affects: linux-bluefield (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1934304 Title: i2c-mlxbf.c: prevent stack overflow in mlxbf_i2c_smbus_start_transaction Status in linux-bluefield package in Ubuntu: New Bug description: SRU Justification: [Impact] There could be stack overflow in mlxbf_i2c_smbus_start_transaction(). memcpy() is called in a loop while 'operation->length' upper bound is not checked and 'data_idx' also increments. More details: The operation length is verified by the caller functions so it cannot exceed I2C_SMBUS_BLOCK_MAX bytes (32 bytes) for each operation that is a part of the write. Data_desc array is 128 bytes in size. So potentially a request which consists of 4 writes, 32 bytes each can trigger an off-by-one or off-by-two overflow, because the first byte of data_desc is used by addr, effectively decreasing the available data_desc buffer size by one. Functions like mlx_smbus_i2c_block_func() that prepare the request also set the length of the first write operation to one and store the command id there, so the target buffer size again decreases data_desc by one, making it two bytes less than expected. [Fix] * Add a check for "operation->length" and data_idx and return error if reached upper bound. [Test Case] * Test the i2c-mlxbf.c driver using IPMB functionality. [Regression Potential] This fix returns a negative value to indicate that a transaction has failed. So it will catch more transactions failures. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1934304/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932577] Re: [Cezanne/Renoir] Adjust uPEP for different _HID behavior
Hi, I sent the SRU request earlier today: https://lists.ubuntu.com/archives/kernel-team/2021-July/121881.html https://lists.ubuntu.com/archives/kernel-team/2021-July/121883.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1932577 Title: [Cezanne/Renoir] Adjust uPEP for different _HID behavior Status in amd: Fix Committed Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux-oem-5.13 source package in Focal: Fix Committed Bug description: Feature: Correct uPEP support for all current ACPI _HID for AMD s2idle Code: Currently oem-5.10 carries hack ""platform/x86: force LPS0 functions for AMD"" which helps some RN platforms, but is not the correct solution. The code that is the correct solution has been submitted to linux-acpi: https://lore.kernel.org/linux-acpi/f50c6baf-a780-7a58-4083-88d539342...@gmail.com/T/#t This will fix RN properly and will also add support for the different variations used for CZN for uPEP. Please replace hack in oem-5.10, and also apply this series for oem-5.13. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1932577/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829849] Re: proc01 in fs from ubuntu_ltp failed
Sent patch to upstream: https://lists.linux.it/pipermail/ltp/2021-July/023598.html ** No longer affects: linux-oracle-5.0 (Ubuntu) ** No longer affects: linux-azure (Ubuntu) ** No longer affects: linux-aws (Ubuntu) ** No longer affects: linux (Ubuntu) ** Changed in: ubuntu-kernel-tests Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1829849 Title: proc01 in fs from ubuntu_ltp failed Status in ubuntu-kernel-tests: In Progress Bug description: proc01 0 TINFO : /proc/sys/fs/binfmt_misc/register: is write-only. proc01 0 TINFO : /proc/sys/net/ipv6/conf/all/stable_secret: known issue: errno=EIO(5): Input/output error proc01 0 TINFO : /proc/sys/net/ipv6/conf/default/stable_secret: known issue: errno=EIO(5): Input/output error proc01 0 TINFO : /proc/sys/net/ipv6/conf/ens6/stable_secret: known issue: errno=EIO(5): Input/output error proc01 0 TINFO : /proc/sys/net/ipv6/conf/lo/stable_secret: known issue: errno=EIO(5): Input/output error proc01 0 TINFO : /proc/kmsg: known issue: errno=EAGAIN/EWOULDBLOCK(11): Resource temporarily unavailable proc01 0 TINFO : /proc/sysrq-trigger: is write-only. proc01 0 TINFO : /proc/self/task/8782/mem: known issue: errno=EIO(5): Input/output error proc01 0 TINFO : /proc/self/task/8782/clear_refs: is write-only. proc01 0 TINFO : /proc/self/task/8782/pagemap: reached maxmbytes (-m) proc01 0 TINFO : /proc/self/task/8782/attr/prev: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/task/8782/attr/exec: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/task/8782/attr/fscreate: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/task/8782/attr/keycreate: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/task/8782/attr/sockcreate: known issue: errno=EINVAL(22): Invalid argument proc01 1 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/selinux/current: errno=EINVAL(22): Invalid argument proc01 2 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/selinux/prev: errno=EINVAL(22): Invalid argument proc01 3 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/selinux/exec: errno=EINVAL(22): Invalid argument proc01 4 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/selinux/fscreate: errno=EINVAL(22): Invalid argument proc01 5 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/selinux/keycreate: errno=EINVAL(22): Invalid argument proc01 6 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/selinux/sockcreate: errno=EINVAL(22): Invalid argument proc01 7 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/smack/current: errno=EINVAL(22): Invalid argument proc01 8 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/apparmor/prev: errno=EINVAL(22): Invalid argument proc01 9 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/apparmor/exec: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/mem: known issue: errno=EIO(5): Input/output error proc01 0 TINFO : /proc/self/clear_refs: is write-only. proc01 0 TINFO : /proc/self/pagemap: reached maxmbytes (-m) proc01 0 TINFO : /proc/self/attr/prev: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/attr/exec: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/attr/fscreate: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/attr/keycreate: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/attr/sockcreate: known issue: errno=EINVAL(22): Invalid argument proc01 10 TFAIL : proc01.c:397: read failed: /proc/self/attr/selinux/current: errno=EINVAL(22): Invalid argument proc01 11 TFAIL : proc01.c:397: read failed: /proc/self/attr/selinux/prev: errno=EINVAL(22): Invalid argument proc01 12 TFAIL : proc01.c:397: read failed: /proc/self/attr/selinux/exec: errno=EINVAL(22): Invalid argument proc01 13 TFAIL : proc01.c:397: read failed: /proc/self/attr/selinux/fscreate: errno=EINVAL(22): Invalid argument proc01 14 TFAIL : proc01.c:397: read failed: /proc/self/attr/selinux/keycreate: errno=EINVAL(22): Invalid argument proc01 15 TFAIL : proc01.c:397: read failed: /proc/self/attr/selinux/sockcreate: errno=EINVAL(22): Invalid argument proc01 16 TFAIL : proc01.c:397: read failed: /proc/self/attr/smack/current: errno=EINVAL(22): Invalid argument proc01 17 TFAIL :
[Kernel-packages] [Bug 1829849] Re: proc01 in fs from ubuntu_ltp failed
** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Krzysztof Kozlowski (krzk) ** Changed in: ubuntu-kernel-tests Status: Triaged => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1829849 Title: proc01 in fs from ubuntu_ltp failed Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Incomplete Status in linux-aws package in Ubuntu: Triaged Status in linux-azure package in Ubuntu: Triaged Status in linux-oracle-5.0 package in Ubuntu: Confirmed Bug description: proc01 0 TINFO : /proc/sys/fs/binfmt_misc/register: is write-only. proc01 0 TINFO : /proc/sys/net/ipv6/conf/all/stable_secret: known issue: errno=EIO(5): Input/output error proc01 0 TINFO : /proc/sys/net/ipv6/conf/default/stable_secret: known issue: errno=EIO(5): Input/output error proc01 0 TINFO : /proc/sys/net/ipv6/conf/ens6/stable_secret: known issue: errno=EIO(5): Input/output error proc01 0 TINFO : /proc/sys/net/ipv6/conf/lo/stable_secret: known issue: errno=EIO(5): Input/output error proc01 0 TINFO : /proc/kmsg: known issue: errno=EAGAIN/EWOULDBLOCK(11): Resource temporarily unavailable proc01 0 TINFO : /proc/sysrq-trigger: is write-only. proc01 0 TINFO : /proc/self/task/8782/mem: known issue: errno=EIO(5): Input/output error proc01 0 TINFO : /proc/self/task/8782/clear_refs: is write-only. proc01 0 TINFO : /proc/self/task/8782/pagemap: reached maxmbytes (-m) proc01 0 TINFO : /proc/self/task/8782/attr/prev: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/task/8782/attr/exec: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/task/8782/attr/fscreate: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/task/8782/attr/keycreate: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/task/8782/attr/sockcreate: known issue: errno=EINVAL(22): Invalid argument proc01 1 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/selinux/current: errno=EINVAL(22): Invalid argument proc01 2 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/selinux/prev: errno=EINVAL(22): Invalid argument proc01 3 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/selinux/exec: errno=EINVAL(22): Invalid argument proc01 4 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/selinux/fscreate: errno=EINVAL(22): Invalid argument proc01 5 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/selinux/keycreate: errno=EINVAL(22): Invalid argument proc01 6 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/selinux/sockcreate: errno=EINVAL(22): Invalid argument proc01 7 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/smack/current: errno=EINVAL(22): Invalid argument proc01 8 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/apparmor/prev: errno=EINVAL(22): Invalid argument proc01 9 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/apparmor/exec: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/mem: known issue: errno=EIO(5): Input/output error proc01 0 TINFO : /proc/self/clear_refs: is write-only. proc01 0 TINFO : /proc/self/pagemap: reached maxmbytes (-m) proc01 0 TINFO : /proc/self/attr/prev: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/attr/exec: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/attr/fscreate: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/attr/keycreate: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/attr/sockcreate: known issue: errno=EINVAL(22): Invalid argument proc01 10 TFAIL : proc01.c:397: read failed: /proc/self/attr/selinux/current: errno=EINVAL(22): Invalid argument proc01 11 TFAIL : proc01.c:397: read failed: /proc/self/attr/selinux/prev: errno=EINVAL(22): Invalid argument proc01 12 TFAIL : proc01.c:397: read failed: /proc/self/attr/selinux/exec: errno=EINVAL(22): Invalid argument proc01 13 TFAIL : proc01.c:397: read failed: /proc/self/attr/selinux/fscreate: errno=EINVAL(22): Invalid argument proc01 14 TFAIL : proc01.c:397: read failed: /proc/self/attr/selinux/keycreate: errno=EINVAL(22): Invalid argument proc01 15 TFAIL : proc01.c:397: read failed: /proc/self/attr/selinux/sockcreate: errno=EINVAL(22): Invalid argument proc01 16 TFAIL : proc01.c:397: read failed: /proc/self/attr/smack/current: errno=EINVAL(22):
[Kernel-packages] [Bug 1934293] Re: Add l2tp.sh in net from ubuntu_kernel_selftests back
** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Description changed: [Impact] - We have this test disabled intentionally in the past because of the lack of commit 27d53323664c54 "l2tp: remove skb_dst_set() from l2tp_xmit_skb()" in our kernels. + We have this test disabled intentionally in the past because of the + lack of commit 27d53323664c54 "l2tp: remove skb_dst_set() from + l2tp_xmit_skb()" in our kernels. - The way we disable it is to override the executable state with our - autotest-client-test suite [1], but this makes the test suite complain - about script is not executable. Henceforth we further disable it by - removing it from the Makefile in "UBUNTU: SAUCE: selftests/net -- - disable timeout" + The way we disable it is to override the executable bit with our + autotest-client-test suite [1], but this makes the test suite + complain about script is not executable. Henceforth we further + disable it by removing it from the Makefile in the patch "UBUNTU: + SAUCE: selftests/net -- disable timeout" - Now with commit 27d53323664c54 landed and l2tp.sh test re-enable in our - test suite [2], we still need to revert that SAUCE patch to get it - tested. + Now with commit 27d53323664c54 landed and l2tp.sh test re-enabled in + our test suite [2], we still need to revert that SAUCE patch to get + it tested. [1] https://kernel.ubuntu.com/git/ubuntu/autotest-client-tests.git/commit/?id=05d7eebf32c6872ebce6c9e5275b1ff9d91ecd16 [2] https://kernel.ubuntu.com/git/ubuntu/autotest-client-tests.git/commit/?id=7dea7776ce431e5a1c550dc73b1d9ac0ba49698d [Fix] Revert "UBUNTU: SAUCE: selftests/net -- disable timeout" This test only exists in our tree since Focal. [Test] Run the net test suite in kselftest with patched source tree: - sudo make -C linux/tools/testing/selftests TARGETS=net run_tests + sudo make -C linux/tools/testing/selftests TARGETS=net run_tests The l2tp.sh test will be executed. [Where problems could occur] - This is only for testing tools, however if commit 27d53323664c54 "l2tp: remove skb_dst_set() from l2tp_xmit_skb()" didn't land properly we might crash our testing node like in bug 1854968. Also, we might see new failures for this test in the test report. + This is only for testing tools, however if commit 27d53323664c54 "l2tp: + remove skb_dst_set() from l2tp_xmit_skb()" didn't land properly we + might crash our testing node like in bug 1854968. Also, we might see + new failures caused by this test in the test report. ** Also affects: linux-oem-5.10 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-oem-5.13 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: linux (Ubuntu Groovy) Status: New => In Progress ** Changed in: linux (Ubuntu Groovy) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: linux (Ubuntu Hirsute) Status: New => In Progress ** Changed in: linux (Ubuntu Hirsute) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: linux (Ubuntu Impish) Status: New => In Progress ** Changed in: linux (Ubuntu Impish) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: linux-oem-5.10 (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-oem-5.10 (Ubuntu Focal) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: linux-oem-5.13 (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-oem-5.13 (Ubuntu Focal) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: linux-oem-5.10 (Ubuntu Groovy) Status: New => Invalid ** Changed in: linux-oem-5.10 (Ubuntu Hirsute) Status: New => Invalid ** Changed in: linux-oem-5.10 (Ubuntu Impish) Status: New => Invalid ** Changed in: linux-oem-5.13 (Ubuntu Groovy) Status: New => Invalid ** Changed in: linux-oem-5.13 (Ubuntu Hirsute) Status: New => Invalid ** Changed in: linux-oem-5.13 (Ubuntu Impish) Status: New => Invalid ** Description changed: [Impact] We have this test disabled intentionally in the past because of the lack of commit 27d53323664c54 "l2tp: remove skb_dst_set() from l2tp_xmit_skb()" in our kernels. The way we disable it is to override the executable bit with our - autotest-client-test suite [1], but this makes the test suite + autotest-client-tests suite [1], but this makes the test suite complain about script is not executable. Henceforth we further disable it by removing it from the Makefile in the patch "UBUNTU: SAUCE: selftests/net -- disable timeout" Now with commit
[Kernel-packages] [Bug 1829849] Re: proc01 in fs from ubuntu_ltp failed
** Tags added: sru-20210621 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1829849 Title: proc01 in fs from ubuntu_ltp failed Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Incomplete Status in linux-aws package in Ubuntu: Triaged Status in linux-azure package in Ubuntu: Triaged Status in linux-oracle-5.0 package in Ubuntu: Confirmed Bug description: proc01 0 TINFO : /proc/sys/fs/binfmt_misc/register: is write-only. proc01 0 TINFO : /proc/sys/net/ipv6/conf/all/stable_secret: known issue: errno=EIO(5): Input/output error proc01 0 TINFO : /proc/sys/net/ipv6/conf/default/stable_secret: known issue: errno=EIO(5): Input/output error proc01 0 TINFO : /proc/sys/net/ipv6/conf/ens6/stable_secret: known issue: errno=EIO(5): Input/output error proc01 0 TINFO : /proc/sys/net/ipv6/conf/lo/stable_secret: known issue: errno=EIO(5): Input/output error proc01 0 TINFO : /proc/kmsg: known issue: errno=EAGAIN/EWOULDBLOCK(11): Resource temporarily unavailable proc01 0 TINFO : /proc/sysrq-trigger: is write-only. proc01 0 TINFO : /proc/self/task/8782/mem: known issue: errno=EIO(5): Input/output error proc01 0 TINFO : /proc/self/task/8782/clear_refs: is write-only. proc01 0 TINFO : /proc/self/task/8782/pagemap: reached maxmbytes (-m) proc01 0 TINFO : /proc/self/task/8782/attr/prev: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/task/8782/attr/exec: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/task/8782/attr/fscreate: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/task/8782/attr/keycreate: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/task/8782/attr/sockcreate: known issue: errno=EINVAL(22): Invalid argument proc01 1 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/selinux/current: errno=EINVAL(22): Invalid argument proc01 2 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/selinux/prev: errno=EINVAL(22): Invalid argument proc01 3 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/selinux/exec: errno=EINVAL(22): Invalid argument proc01 4 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/selinux/fscreate: errno=EINVAL(22): Invalid argument proc01 5 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/selinux/keycreate: errno=EINVAL(22): Invalid argument proc01 6 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/selinux/sockcreate: errno=EINVAL(22): Invalid argument proc01 7 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/smack/current: errno=EINVAL(22): Invalid argument proc01 8 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/apparmor/prev: errno=EINVAL(22): Invalid argument proc01 9 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/apparmor/exec: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/mem: known issue: errno=EIO(5): Input/output error proc01 0 TINFO : /proc/self/clear_refs: is write-only. proc01 0 TINFO : /proc/self/pagemap: reached maxmbytes (-m) proc01 0 TINFO : /proc/self/attr/prev: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/attr/exec: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/attr/fscreate: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/attr/keycreate: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/attr/sockcreate: known issue: errno=EINVAL(22): Invalid argument proc01 10 TFAIL : proc01.c:397: read failed: /proc/self/attr/selinux/current: errno=EINVAL(22): Invalid argument proc01 11 TFAIL : proc01.c:397: read failed: /proc/self/attr/selinux/prev: errno=EINVAL(22): Invalid argument proc01 12 TFAIL : proc01.c:397: read failed: /proc/self/attr/selinux/exec: errno=EINVAL(22): Invalid argument proc01 13 TFAIL : proc01.c:397: read failed: /proc/self/attr/selinux/fscreate: errno=EINVAL(22): Invalid argument proc01 14 TFAIL : proc01.c:397: read failed: /proc/self/attr/selinux/keycreate: errno=EINVAL(22): Invalid argument proc01 15 TFAIL : proc01.c:397: read failed: /proc/self/attr/selinux/sockcreate: errno=EINVAL(22): Invalid argument proc01 16 TFAIL : proc01.c:397: read failed: /proc/self/attr/smack/current: errno=EINVAL(22): Invalid argument proc01 17 TFAIL : proc01.c:397: read failed: /proc/self/attr/apparmor/prev: errno=EINVAL(22): Invalid argument
[Kernel-packages] [Bug 1932577] Re: [Cezanne/Renoir] Adjust uPEP for different _HID behavior
HI Kai-Heng, Could you please let us know what is the current update on this? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1932577 Title: [Cezanne/Renoir] Adjust uPEP for different _HID behavior Status in amd: Fix Committed Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux-oem-5.13 source package in Focal: Fix Committed Bug description: Feature: Correct uPEP support for all current ACPI _HID for AMD s2idle Code: Currently oem-5.10 carries hack ""platform/x86: force LPS0 functions for AMD"" which helps some RN platforms, but is not the correct solution. The code that is the correct solution has been submitted to linux-acpi: https://lore.kernel.org/linux-acpi/f50c6baf-a780-7a58-4083-88d539342...@gmail.com/T/#t This will fix RN properly and will also add support for the different variations used for CZN for uPEP. Please replace hack in oem-5.10, and also apply this series for oem-5.13. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1932577/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934261] Re: use debian source format 3.0 (native)
Testing PPA: https://launchpad.net/~vicamo/+archive/ubuntu/linux- firmware-staging -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1934261 Title: use debian source format 3.0 (native) Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Bionic: New Status in linux-firmware source package in Focal: New Status in linux-firmware source package in Groovy: Won't Fix Status in linux-firmware source package in Hirsute: Invalid Status in linux-firmware source package in Impish: Invalid Bug description: In Hirsute/Impish, debian source package Standards-Version moved to 4.5.0, and debian/source/format is created with content "3.0 (native)". It should be also helpful to backport this change to other maintaining series. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1934261/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934217] Re: Intel Killer(R) Wi-Fi 6 AX1650i [8086:a0f0] Subsystem [1a56:1651]: iwlwifi firmware crash under iperf stress tests: Microcode SW error detected. Restarting 0x0
Testing PPA: https://launchpad.net/~vicamo/+archive/ubuntu/linux- firmware-staging (focal) ** Tags added: oem-priority originate-from-1933755 somerville -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1934217 Title: Intel Killer(R) Wi-Fi 6 AX1650i [8086:a0f0] Subsystem [1a56:1651]: iwlwifi firmware crash under iperf stress tests: Microcode SW error detected. Restarting 0x0 Status in HWE Next: New Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Focal: In Progress Status in linux-firmware source package in Hirsute: Invalid Bug description: - Connect both DUTs to the 5G wifi AP - on DUT 1 - $ iperf3 -s -B 192.168.50.188 - on DUT 2 - $ iperf3 -c 192.168.50.188 -B 192.168.50.91 -t 6000 - After about 30 mins the wifi crashed with firmware related error [105396.990450] iwlwifi :00:14.3: Microcode SW error detected. Restarting 0x0. [105396.990539] iwlwifi :00:14.3: Start IWL Error Log Dump: [105396.990541] iwlwifi :00:14.3: Status: 0x0040, count: 6 [105396.990543] iwlwifi :00:14.3: Loaded firmware version: 55.d9698065.0 QuZ-a0-hr-b0-55.ucode [105396.990545] iwlwifi :00:14.3: 0x0071 | NMI_INTERRUPT_UMAC_FATAL [105396.990547] iwlwifi :00:14.3: 0x22F0 | trm_hw_status0 [105396.990548] iwlwifi :00:14.3: 0x | trm_hw_status1 [105396.990549] iwlwifi :00:14.3: 0x004CA3DE | branchlink2 [105396.990551] iwlwifi :00:14.3: 0x07F6 | interruptlink1 [105396.990552] iwlwifi :00:14.3: 0x07F6 | interruptlink2 [105396.990553] iwlwifi :00:14.3: 0x00016504 | data1 [105396.990554] iwlwifi :00:14.3: 0x1000 | data2 [105396.990555] iwlwifi :00:14.3: 0x | data3 [105396.990557] iwlwifi :00:14.3: 0x900148E4 | beacon time [105396.990558] iwlwifi :00:14.3: 0x0C6FF71A | tsf low [105396.990559] iwlwifi :00:14.3: 0x01B4 | tsf hi [105396.990560] iwlwifi :00:14.3: 0x | time gp1 [105396.990562] iwlwifi :00:14.3: 0x58CF3E54 | time gp2 [105396.990563] iwlwifi :00:14.3: 0x0001 | uCode revision type [105396.990564] iwlwifi :00:14.3: 0x0037 | uCode version major [105396.990565] iwlwifi :00:14.3: 0xD9698065 | uCode version minor [105396.990567] iwlwifi :00:14.3: 0x0351 | hw version [105396.990568] iwlwifi :00:14.3: 0x00C89004 | board version [105396.990569] iwlwifi :00:14.3: 0x800FFC03 | hcmd [105396.990570] iwlwifi :00:14.3: 0x0002 | isr0 [105396.990572] iwlwifi :00:14.3: 0x0040 | isr1 [105396.990573] iwlwifi :00:14.3: 0x08F2 | isr2 [105396.990574] iwlwifi :00:14.3: 0x04C338C8 | isr3 [105396.990575] iwlwifi :00:14.3: 0x | isr4 [105396.990577] iwlwifi :00:14.3: 0x05D6001C | last cmd Id [105396.990578] iwlwifi :00:14.3: 0x00016504 | wait_event [105396.990579] iwlwifi :00:14.3: 0x00C4 | l2p_control [105396.990580] iwlwifi :00:14.3: 0x | l2p_duration [105396.990582] iwlwifi :00:14.3: 0x0007 | l2p_mhvalid [105396.990583] iwlwifi :00:14.3: 0x | l2p_addr_match [105396.990584] iwlwifi :00:14.3: 0x0009 | lmpm_pmg_sel [105396.990585] iwlwifi :00:14.3: 0x | timestamp [105396.990586] iwlwifi :00:14.3: 0xC0D4 | flow_handler [105396.990628] iwlwifi :00:14.3: Start IWL Error Log Dump: [105396.990629] iwlwifi :00:14.3: Status: 0x0040, count: 7 [105396.990631] iwlwifi :00:14.3: 0x2000307C | ADVANCED_SYSASSERT [105396.990632] iwlwifi :00:14.3: 0x | umac branchlink1 [105396.990633] iwlwifi :00:14.3: 0x80465D2E | umac branchlink2 [105396.990634] iwlwifi :00:14.3: 0x80473128 | umac interruptlink1 [105396.990635] iwlwifi :00:14.3: 0x | umac interruptlink2 [105396.990637] iwlwifi :00:14.3: 0x | umac data1 [105396.990638] iwlwifi :00:14.3: 0xDEADBEEF | umac data2 [105396.990639] iwlwifi :00:14.3: 0xDEADBEEF | umac data3 [105396.990640] iwlwifi :00:14.3: 0x0037 | umac major [105396.990641] iwlwifi :00:14.3: 0xD9698065 | umac minor [105396.990642] iwlwifi :00:14.3: 0x58CF3E47 | frame pointer [105396.990644] iwlwifi :00:14.3: 0xC0885EB0 | stack pointer [105396.990645] iwlwifi :00:14.3: 0x0080010D | last host cmd [105396.990646] iwlwifi :00:14.3: 0x | isr status reg [105396.990668] iwlwifi :00:14.3: Fseq Registers: [105396.990691] iwlwifi :00:14.3: 0x6000 | FSEQ_ERROR_CODE [105396.990694] iwlwifi :00:14.3: 0x80290033 | FSEQ_TOP_INIT_VERSION [105396.990717] iwlwifi :00:14.3: 0x00090006 | FSEQ_CNVIO_INIT_VERSION [105396.990748] iwlwifi :00:14.3: 0xA482 | FSEQ_OTP_VERSION [105396.990764] iwlwifi :00:14.3: 0x0003 | FSEQ_TOP_CONTENT_VERSION
[Kernel-packages] [Bug 1934293] [NEW] Add l2tp.sh in net from ubuntu_kernel_selftests back
Public bug reported: [Impact] We have this test disabled intentionally in the past because of the lack of commit 27d53323664c54 "l2tp: remove skb_dst_set() from l2tp_xmit_skb()" in our kernels. The way we disable it is to override the executable state with our autotest-client-test suite [1], but this makes the test suite complain about script is not executable. Henceforth we further disable it by removing it from the Makefile in "UBUNTU: SAUCE: selftests/net -- disable timeout" Now with commit 27d53323664c54 landed and l2tp.sh test re-enable in our test suite [2], we still need to revert that SAUCE patch to get it tested. [1] https://kernel.ubuntu.com/git/ubuntu/autotest-client-tests.git/commit/?id=05d7eebf32c6872ebce6c9e5275b1ff9d91ecd16 [2] https://kernel.ubuntu.com/git/ubuntu/autotest-client-tests.git/commit/?id=7dea7776ce431e5a1c550dc73b1d9ac0ba49698d [Fix] Revert "UBUNTU: SAUCE: selftests/net -- disable timeout" This test only exists in our tree since Focal. [Test] Run the net test suite in kselftest with patched source tree: sudo make -C linux/tools/testing/selftests TARGETS=net run_tests The l2tp.sh test will be executed. [Where problems could occur] This is only for testing tools, however if commit 27d53323664c54 "l2tp: remove skb_dst_set() from l2tp_xmit_skb()" didn't land properly we might crash our testing node like in bug 1854968. Also, we might see new failures for this test in the test report. ** Affects: ubuntu-kernel-tests Importance: Undecided Assignee: Po-Hsu Lin (cypressyew) Status: In Progress ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: ubuntu-kernel-tests Status: New => In Progress ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Description changed: [Impact] We have this test disabled intentionally in the past because of the lack of commit 27d53323664c54 "l2tp: remove skb_dst_set() from l2tp_xmit_skb()" in our kernels. The way we disable it is to override the executable state with our autotest-client-test suite [1], but this makes the test suite complain about script is not executable. Henceforth we further disable it by removing it from the Makefile in "UBUNTU: SAUCE: selftests/net -- disable timeout" Now with commit 27d53323664c54 landed and l2tp.sh test re-enable in out test suite [2], we still need to revert that SAUCE patch to get it tested. [1] https://kernel.ubuntu.com/git/ubuntu/autotest-client-tests.git/commit/?id=05d7eebf32c6872ebce6c9e5275b1ff9d91ecd16 [2] https://kernel.ubuntu.com/git/ubuntu/autotest-client-tests.git/commit/?id=7dea7776ce431e5a1c550dc73b1d9ac0ba49698d [Fix] Revert "UBUNTU: SAUCE: selftests/net -- disable timeout" + This test only exists in our tree since Focal. + [Test] Run the net test suite in kselftest with patched source tree: - sudo make -C linux/tools/testing/selftests TARGETS=net run_tests + sudo make -C linux/tools/testing/selftests TARGETS=net run_tests The l2tp.sh test will be executed. [Where problems could occur] This is only for testing tools, however if commit 27d53323664c54 "l2tp: remove skb_dst_set() from l2tp_xmit_skb()" didn't land properly we might crash our testing node like in bug 1854968. Also, we might see new failures for this test in the test report. ** Description changed: [Impact] We have this test disabled intentionally in the past because of the lack of commit 27d53323664c54 "l2tp: remove skb_dst_set() from l2tp_xmit_skb()" in our kernels. The way we disable it is to override the executable state with our autotest-client-test suite [1], but this makes the test suite complain about script is not executable. Henceforth we further disable it by removing it from the Makefile in "UBUNTU: SAUCE: selftests/net -- disable timeout" - Now with commit 27d53323664c54 landed and l2tp.sh test re-enable in out + Now with commit 27d53323664c54 landed and l2tp.sh test re-enable in our test suite [2], we still need to revert that SAUCE patch to get it tested. [1] https://kernel.ubuntu.com/git/ubuntu/autotest-client-tests.git/commit/?id=05d7eebf32c6872ebce6c9e5275b1ff9d91ecd16 [2] https://kernel.ubuntu.com/git/ubuntu/autotest-client-tests.git/commit/?id=7dea7776ce431e5a1c550dc73b1d9ac0ba49698d [Fix] Revert "UBUNTU: SAUCE: selftests/net -- disable timeout" This test only exists in our tree since Focal. [Test] Run the net test suite in kselftest with patched source tree: sudo make -C linux/tools/testing/selftests TARGETS=net run_tests The l2tp.sh test will be executed. [Where problems could occur] This is only for testing tools,
[Kernel-packages] [Bug 1904589] Re: zfs PANIC: accessing past end of object in 0.8.3-1ubuntu12.4
This bug was fixed in the package zfs-linux - 0.8.3-1ubuntu12.10
---
zfs-linux (0.8.3-1ubuntu12.10) focal; urgency=medium
* fix uio partial copies (LP: #1904589)
-- Andrea Righi Thu, 10 Jun 2021 14:49:23
+0100
** Changed in: zfs-linux (Ubuntu Focal)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1904589
Title:
zfs PANIC: accessing past end of object in 0.8.3-1ubuntu12.4
Status in zfs-linux package in Ubuntu:
Fix Released
Status in zfs-linux source package in Focal:
Fix Released
Status in zfs-linux source package in Groovy:
Fix Released
Status in zfs-linux source package in Hirsute:
Fix Released
Bug description:
[Impact]
zfs_write() doesn't properly account partial copies done by
copy_from_user(), causing accesses past the end of objects and
triggering kernel panics.
[Test case]
The problem seems to be workload specific, there is not a specific
test case to reproduce the problem, but the bug seems to be pretty
well identified by the upstream commit reported below.
[Fix]
Apply upstream commit c9e3efdb3a6111b9795becc6594b3c52ba004522
("Bugfix/fix uio partial copies").
[Regression potential]
Upstream commit that is basically fixing potential out-of-bounds
accesses by properly checking partial copies done by copy_from_user()
and preventing kernel panics. Regression potential is minimal: it
seems unlikely to break other things if this change is applied.
[Original bug report]
Using latest zfs 0.8.3-1ubuntu12.4 on latest Ubuntu 20.04.1, I observe
a rare zfs panics that seem to be workload-specific which render a
server mostly unresponsive besides ssh still working. Attempting to
reboot the server in this state makes the shutdown hang forever.
You may want to consider backporting the fix released in zfs 0.8.4
into 20.04: https://github.com/openzfs/zfs/pull/10148
Log sample of panic:
```
Nov 17 16:06:15 hostname kernel: [3385134.716024] PANIC: zfs: accessing past
end of object c1c/2db52f (size=17408 access=7492+16428)
Nov 17 16:06:15 hostname kernel: [3385134.716072] Showing stack for process
3166846
Nov 17 16:06:15 hostname kernel: [3385134.716074] CPU: 25 PID: 3166846 Comm:
node Tainted: P O 5.4.0-48-generic #52-Ubuntu
Nov 17 16:06:15 hostname kernel: [3385134.716075] Hardware name:
Nov 17 16:06:15 hostname kernel: [3385134.716076] Call Trace:
Nov 17 16:06:15 hostname kernel: [3385134.716085] dump_stack+0x6d/0x9a
Nov 17 16:06:15 hostname kernel: [3385134.716097] spl_dumpstack+0x29/0x2b
[spl]
Nov 17 16:06:15 hostname kernel: [3385134.716102] vcmn_err.cold+0x60/0x99
[spl]
Nov 17 16:06:15 hostname kernel: [3385134.716106] ? _cond_resched+0x19/0x30
Nov 17 16:06:15 hostname kernel: [3385134.716108] ?
__kmalloc_node+0x20e/0x330
Nov 17 16:06:15 hostname kernel: [3385134.716113] ?
spl_kmem_alloc_impl+0xa8/0x100 [spl]
Nov 17 16:06:15 hostname kernel: [3385134.716190] ? __list_add+0x17/0x40
[zfs]
Nov 17 16:06:15 hostname kernel: [3385134.716235]
zfs_panic_recover+0x6f/0x90 [zfs]
Nov 17 16:06:15 hostname kernel: [3385134.716272] ?
dsl_dir_tempreserve_impl.isra.0.constprop.0+0xed/0x330 [zfs]
Nov 17 16:06:15 hostname kernel: [3385134.716305]
dmu_buf_hold_array_by_dnode+0x3a0/0x490 [zfs]
Nov 17 16:06:15 hostname kernel: [3385134.716338]
dmu_write_uio_dnode+0x4c/0x140 [zfs]
Nov 17 16:06:15 hostname kernel: [3385134.716370]
dmu_write_uio_dbuf+0x4f/0x70 [zfs]
Nov 17 16:06:15 hostname kernel: [3385134.716416] zfs_write+0xa1f/0xd40 [zfs]
Nov 17 16:06:15 hostname kernel: [3385134.716419] ? d_absolute_path+0x74/0xb0
Nov 17 16:06:15 hostname kernel: [3385134.716421] ? __switch_to_asm+0x34/0x70
Nov 17 16:06:15 hostname kernel: [3385134.716423] ? __switch_to_asm+0x40/0x70
Nov 17 16:06:15 hostname kernel: [3385134.716424] ? __switch_to_asm+0x40/0x70
Nov 17 16:06:15 hostname kernel: [3385134.716425] ? __switch_to_asm+0x34/0x70
Nov 17 16:06:15 hostname kernel: [3385134.716427] ? __switch_to_asm+0x34/0x70
Nov 17 16:06:15 hostname kernel: [3385134.716474]
zpl_write_common_iovec+0xad/0x120 [zfs]
Nov 17 16:06:15 hostname kernel: [3385134.716567] zpl_iter_write+0x56/0x90
[zfs]
Nov 17 16:06:15 hostname kernel: [3385134.716570] do_iter_write+0x84/0x1a0
Nov 17 16:06:15 hostname kernel: [3385134.716574] ? futex_wake+0x8b/0x180
Nov 17 16:06:15 hostname kernel: [3385134.716577] do_writev+0x71/0x120
Nov 17 16:06:15 hostname kernel: [3385134.716581] do_syscall_64+0x57/0x190
Nov 17 16:06:15 hostname kernel: [3385134.716584] RIP: 0033:0x7fa366eee0cd
Nov 17 16:06:15 hostname kernel: [3385134.716587] RSP: 002b:7fa35e7fbde0
EFLAGS: 0293 ORIG_RAX: 0014
Nov 17 16:06:15 hostname kernel: [3385134.716590] RDX: 000c RSI:
0651c7b0 RDI: 001d
[Kernel-packages] [Bug 1904589] Update Released
The verification of the Stable Release Update for zfs-linux has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1904589
Title:
zfs PANIC: accessing past end of object in 0.8.3-1ubuntu12.4
Status in zfs-linux package in Ubuntu:
Fix Released
Status in zfs-linux source package in Focal:
Fix Released
Status in zfs-linux source package in Groovy:
Fix Released
Status in zfs-linux source package in Hirsute:
Fix Released
Bug description:
[Impact]
zfs_write() doesn't properly account partial copies done by
copy_from_user(), causing accesses past the end of objects and
triggering kernel panics.
[Test case]
The problem seems to be workload specific, there is not a specific
test case to reproduce the problem, but the bug seems to be pretty
well identified by the upstream commit reported below.
[Fix]
Apply upstream commit c9e3efdb3a6111b9795becc6594b3c52ba004522
("Bugfix/fix uio partial copies").
[Regression potential]
Upstream commit that is basically fixing potential out-of-bounds
accesses by properly checking partial copies done by copy_from_user()
and preventing kernel panics. Regression potential is minimal: it
seems unlikely to break other things if this change is applied.
[Original bug report]
Using latest zfs 0.8.3-1ubuntu12.4 on latest Ubuntu 20.04.1, I observe
a rare zfs panics that seem to be workload-specific which render a
server mostly unresponsive besides ssh still working. Attempting to
reboot the server in this state makes the shutdown hang forever.
You may want to consider backporting the fix released in zfs 0.8.4
into 20.04: https://github.com/openzfs/zfs/pull/10148
Log sample of panic:
```
Nov 17 16:06:15 hostname kernel: [3385134.716024] PANIC: zfs: accessing past
end of object c1c/2db52f (size=17408 access=7492+16428)
Nov 17 16:06:15 hostname kernel: [3385134.716072] Showing stack for process
3166846
Nov 17 16:06:15 hostname kernel: [3385134.716074] CPU: 25 PID: 3166846 Comm:
node Tainted: P O 5.4.0-48-generic #52-Ubuntu
Nov 17 16:06:15 hostname kernel: [3385134.716075] Hardware name:
Nov 17 16:06:15 hostname kernel: [3385134.716076] Call Trace:
Nov 17 16:06:15 hostname kernel: [3385134.716085] dump_stack+0x6d/0x9a
Nov 17 16:06:15 hostname kernel: [3385134.716097] spl_dumpstack+0x29/0x2b
[spl]
Nov 17 16:06:15 hostname kernel: [3385134.716102] vcmn_err.cold+0x60/0x99
[spl]
Nov 17 16:06:15 hostname kernel: [3385134.716106] ? _cond_resched+0x19/0x30
Nov 17 16:06:15 hostname kernel: [3385134.716108] ?
__kmalloc_node+0x20e/0x330
Nov 17 16:06:15 hostname kernel: [3385134.716113] ?
spl_kmem_alloc_impl+0xa8/0x100 [spl]
Nov 17 16:06:15 hostname kernel: [3385134.716190] ? __list_add+0x17/0x40
[zfs]
Nov 17 16:06:15 hostname kernel: [3385134.716235]
zfs_panic_recover+0x6f/0x90 [zfs]
Nov 17 16:06:15 hostname kernel: [3385134.716272] ?
dsl_dir_tempreserve_impl.isra.0.constprop.0+0xed/0x330 [zfs]
Nov 17 16:06:15 hostname kernel: [3385134.716305]
dmu_buf_hold_array_by_dnode+0x3a0/0x490 [zfs]
Nov 17 16:06:15 hostname kernel: [3385134.716338]
dmu_write_uio_dnode+0x4c/0x140 [zfs]
Nov 17 16:06:15 hostname kernel: [3385134.716370]
dmu_write_uio_dbuf+0x4f/0x70 [zfs]
Nov 17 16:06:15 hostname kernel: [3385134.716416] zfs_write+0xa1f/0xd40 [zfs]
Nov 17 16:06:15 hostname kernel: [3385134.716419] ? d_absolute_path+0x74/0xb0
Nov 17 16:06:15 hostname kernel: [3385134.716421] ? __switch_to_asm+0x34/0x70
Nov 17 16:06:15 hostname kernel: [3385134.716423] ? __switch_to_asm+0x40/0x70
Nov 17 16:06:15 hostname kernel: [3385134.716424] ? __switch_to_asm+0x40/0x70
Nov 17 16:06:15 hostname kernel: [3385134.716425] ? __switch_to_asm+0x34/0x70
Nov 17 16:06:15 hostname kernel: [3385134.716427] ? __switch_to_asm+0x34/0x70
Nov 17 16:06:15 hostname kernel: [3385134.716474]
zpl_write_common_iovec+0xad/0x120 [zfs]
Nov 17 16:06:15 hostname kernel: [3385134.716567] zpl_iter_write+0x56/0x90
[zfs]
Nov 17 16:06:15 hostname kernel: [3385134.716570] do_iter_write+0x84/0x1a0
Nov 17 16:06:15 hostname kernel: [3385134.716574] ? futex_wake+0x8b/0x180
Nov 17 16:06:15 hostname kernel: [3385134.716577] do_writev+0x71/0x120
Nov 17 16:06:15 hostname kernel: [3385134.716581] do_syscall_64+0x57/0x190
Nov 17 16:06:15 hostname kernel: [3385134.716584] RIP: 0033:0x7fa366eee0cd
Nov 17 16:06:15 hostname kernel: [3385134.716587] RSP: 002b:7fa35e7fbde0
EFLAGS:
[Kernel-packages] [Bug 1904589] Re: zfs PANIC: accessing past end of object in 0.8.3-1ubuntu12.4
I think this was aging in -proposed long enough. Let's proceed with the
release.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1904589
Title:
zfs PANIC: accessing past end of object in 0.8.3-1ubuntu12.4
Status in zfs-linux package in Ubuntu:
Fix Released
Status in zfs-linux source package in Focal:
Fix Released
Status in zfs-linux source package in Groovy:
Fix Released
Status in zfs-linux source package in Hirsute:
Fix Released
Bug description:
[Impact]
zfs_write() doesn't properly account partial copies done by
copy_from_user(), causing accesses past the end of objects and
triggering kernel panics.
[Test case]
The problem seems to be workload specific, there is not a specific
test case to reproduce the problem, but the bug seems to be pretty
well identified by the upstream commit reported below.
[Fix]
Apply upstream commit c9e3efdb3a6111b9795becc6594b3c52ba004522
("Bugfix/fix uio partial copies").
[Regression potential]
Upstream commit that is basically fixing potential out-of-bounds
accesses by properly checking partial copies done by copy_from_user()
and preventing kernel panics. Regression potential is minimal: it
seems unlikely to break other things if this change is applied.
[Original bug report]
Using latest zfs 0.8.3-1ubuntu12.4 on latest Ubuntu 20.04.1, I observe
a rare zfs panics that seem to be workload-specific which render a
server mostly unresponsive besides ssh still working. Attempting to
reboot the server in this state makes the shutdown hang forever.
You may want to consider backporting the fix released in zfs 0.8.4
into 20.04: https://github.com/openzfs/zfs/pull/10148
Log sample of panic:
```
Nov 17 16:06:15 hostname kernel: [3385134.716024] PANIC: zfs: accessing past
end of object c1c/2db52f (size=17408 access=7492+16428)
Nov 17 16:06:15 hostname kernel: [3385134.716072] Showing stack for process
3166846
Nov 17 16:06:15 hostname kernel: [3385134.716074] CPU: 25 PID: 3166846 Comm:
node Tainted: P O 5.4.0-48-generic #52-Ubuntu
Nov 17 16:06:15 hostname kernel: [3385134.716075] Hardware name:
Nov 17 16:06:15 hostname kernel: [3385134.716076] Call Trace:
Nov 17 16:06:15 hostname kernel: [3385134.716085] dump_stack+0x6d/0x9a
Nov 17 16:06:15 hostname kernel: [3385134.716097] spl_dumpstack+0x29/0x2b
[spl]
Nov 17 16:06:15 hostname kernel: [3385134.716102] vcmn_err.cold+0x60/0x99
[spl]
Nov 17 16:06:15 hostname kernel: [3385134.716106] ? _cond_resched+0x19/0x30
Nov 17 16:06:15 hostname kernel: [3385134.716108] ?
__kmalloc_node+0x20e/0x330
Nov 17 16:06:15 hostname kernel: [3385134.716113] ?
spl_kmem_alloc_impl+0xa8/0x100 [spl]
Nov 17 16:06:15 hostname kernel: [3385134.716190] ? __list_add+0x17/0x40
[zfs]
Nov 17 16:06:15 hostname kernel: [3385134.716235]
zfs_panic_recover+0x6f/0x90 [zfs]
Nov 17 16:06:15 hostname kernel: [3385134.716272] ?
dsl_dir_tempreserve_impl.isra.0.constprop.0+0xed/0x330 [zfs]
Nov 17 16:06:15 hostname kernel: [3385134.716305]
dmu_buf_hold_array_by_dnode+0x3a0/0x490 [zfs]
Nov 17 16:06:15 hostname kernel: [3385134.716338]
dmu_write_uio_dnode+0x4c/0x140 [zfs]
Nov 17 16:06:15 hostname kernel: [3385134.716370]
dmu_write_uio_dbuf+0x4f/0x70 [zfs]
Nov 17 16:06:15 hostname kernel: [3385134.716416] zfs_write+0xa1f/0xd40 [zfs]
Nov 17 16:06:15 hostname kernel: [3385134.716419] ? d_absolute_path+0x74/0xb0
Nov 17 16:06:15 hostname kernel: [3385134.716421] ? __switch_to_asm+0x34/0x70
Nov 17 16:06:15 hostname kernel: [3385134.716423] ? __switch_to_asm+0x40/0x70
Nov 17 16:06:15 hostname kernel: [3385134.716424] ? __switch_to_asm+0x40/0x70
Nov 17 16:06:15 hostname kernel: [3385134.716425] ? __switch_to_asm+0x34/0x70
Nov 17 16:06:15 hostname kernel: [3385134.716427] ? __switch_to_asm+0x34/0x70
Nov 17 16:06:15 hostname kernel: [3385134.716474]
zpl_write_common_iovec+0xad/0x120 [zfs]
Nov 17 16:06:15 hostname kernel: [3385134.716567] zpl_iter_write+0x56/0x90
[zfs]
Nov 17 16:06:15 hostname kernel: [3385134.716570] do_iter_write+0x84/0x1a0
Nov 17 16:06:15 hostname kernel: [3385134.716574] ? futex_wake+0x8b/0x180
Nov 17 16:06:15 hostname kernel: [3385134.716577] do_writev+0x71/0x120
Nov 17 16:06:15 hostname kernel: [3385134.716581] do_syscall_64+0x57/0x190
Nov 17 16:06:15 hostname kernel: [3385134.716584] RIP: 0033:0x7fa366eee0cd
Nov 17 16:06:15 hostname kernel: [3385134.716587] RSP: 002b:7fa35e7fbde0
EFLAGS: 0293 ORIG_RAX: 0014
Nov 17 16:06:15 hostname kernel: [3385134.716590] RDX: 000c RSI:
0651c7b0 RDI: 001d
```
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1904589/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to :
[Kernel-packages] [Bug 1933221] Re: Blutooth on/off does not work properly from gnome-control-center
This bug was fixed in the package bluez - 5.53-0ubuntu3.3 --- bluez (5.53-0ubuntu3.3) focal; urgency=medium * debian/patches/0001-fix-reading-from-rfkill-socket.patch: - fix reading from rfkill socket (lp: #1933221) -- Andy Chi Tue, 22 Jun 2021 14:27:12 +0800 ** Changed in: bluez (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1933221 Title: Blutooth on/off does not work properly from gnome-control-center Status in OEM Priority Project: New Status in bluez package in Ubuntu: Fix Released Status in bluez source package in Focal: Fix Released Status in bluez source package in Hirsute: Fix Released Status in bluez source package in Impish: Fix Released Bug description: [Impact] On/off of Bluetooth in gnome-control-center will not work properly in kernels 5.11 (approximately) onward. Devices are not refreshed in the list anymore. [Test Plan] 1. Open gnome-control-center and select Bluetooth 2. Turn off Bluetooth via UI 3. Turn on Bluetooth via UI Expect: Device list appears, so Bluetooth really is on. [Where problems could occur] Since the fix involves the 'rfkill' logic it has the potential to affect any Bluetooth or Wifi on/off setting. [Other info] Upstream bug in gnome-bluetooth: https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 Discussion in linux-bluetooth: https://marc.info/?t=16200475893=1=2 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1933221/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1933221] Update Released
The verification of the Stable Release Update for bluez has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1933221 Title: Blutooth on/off does not work properly from gnome-control-center Status in OEM Priority Project: New Status in bluez package in Ubuntu: Fix Released Status in bluez source package in Focal: Fix Released Status in bluez source package in Hirsute: Fix Released Status in bluez source package in Impish: Fix Released Bug description: [Impact] On/off of Bluetooth in gnome-control-center will not work properly in kernels 5.11 (approximately) onward. Devices are not refreshed in the list anymore. [Test Plan] 1. Open gnome-control-center and select Bluetooth 2. Turn off Bluetooth via UI 3. Turn on Bluetooth via UI Expect: Device list appears, so Bluetooth really is on. [Where problems could occur] Since the fix involves the 'rfkill' logic it has the potential to affect any Bluetooth or Wifi on/off setting. [Other info] Upstream bug in gnome-bluetooth: https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 Discussion in linux-bluetooth: https://marc.info/?t=16200475893=1=2 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1933221/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1933221] Re: Blutooth on/off does not work properly from gnome-control-center
This bug was fixed in the package bluez - 5.56-0ubuntu4.2 --- bluez (5.56-0ubuntu4.2) hirsute; urgency=medium * debian/patches/0001-fix-reading-from-rfkill-socket.patch: - fix reading from rfkill socket (lp: #1933221) -- Andy Chi Tue, 22 Jun 2021 08:07:12 + ** Changed in: bluez (Ubuntu Hirsute) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1933221 Title: Blutooth on/off does not work properly from gnome-control-center Status in OEM Priority Project: New Status in bluez package in Ubuntu: Fix Released Status in bluez source package in Focal: Fix Released Status in bluez source package in Hirsute: Fix Released Status in bluez source package in Impish: Fix Released Bug description: [Impact] On/off of Bluetooth in gnome-control-center will not work properly in kernels 5.11 (approximately) onward. Devices are not refreshed in the list anymore. [Test Plan] 1. Open gnome-control-center and select Bluetooth 2. Turn off Bluetooth via UI 3. Turn on Bluetooth via UI Expect: Device list appears, so Bluetooth really is on. [Where problems could occur] Since the fix involves the 'rfkill' logic it has the potential to affect any Bluetooth or Wifi on/off setting. [Other info] Upstream bug in gnome-bluetooth: https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 Discussion in linux-bluetooth: https://marc.info/?t=16200475893=1=2 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1933221/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827866] Re: vmx_apicv_test in ubuntu_kvm_unit_tests failed on X/B-KVM X-azure / X-aws
** Tags added: sru-20210621 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1827866 Title: vmx_apicv_test in ubuntu_kvm_unit_tests failed on X/B-KVM X-azure / X-aws Status in ubuntu-kernel-tests: New Status in linux-azure package in Ubuntu: New Status in linux-kvm package in Ubuntu: New Status in linux-oracle package in Ubuntu: New Status in linux-azure source package in Xenial: New Status in linux-kvm source package in Xenial: New Status in linux-oracle source package in Xenial: New Status in linux-azure source package in Bionic: New Status in linux-kvm source package in Bionic: New Status in linux-oracle source package in Bionic: New Bug description: vmx_apicv_test from ubuntu_kvm_unit_tests failed on X-KVM: FAIL vmx_apicv_test (timeout; duration=10) the test was terminated with return code 124: # TESTNAME=vmx_apicv_test TIMEOUT=10 ACCEL= ./x86/run x86/vmx.flat -smp 1 -cpu host,+vmx -append "apic_reg_virt_test virt_x2apic_mode_test" timeout -k 1s --foreground 10 /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel x86/vmx.flat -smp 1 -cpu host,+vmx -append apic_reg_virt_test virt_x2apic_mode_test # -initrd /tmp/tmp.K6b7rjmgp8 enabling apic paging enabled cr0 = 80010011 cr3 = 477000 cr4 = 20 Test suite: apic_reg_virt_test --- Virtualize APIC accesses test --- PASS: xapic - reading 0x000: got APIC access exit @ page offset 0x000, want 0x000 PASS: xapic - writing 0x12345678 to 0x000: got APIC access exit @ page offset 0x000, want 0x000 PASS: xapic - reading 0x010: got APIC access exit @ page offset 0x010, want 0x010 PASS: xapic - writing 0x12345678 to 0x010: got APIC access exit @ page offset 0x010, want 0x010 PASS: xapic - reading 0x020: got APIC access exit @ page offset 0x020, want 0x020 PASS: xapic - writing 0x12345678 to 0x020: got APIC access exit @ page offset 0x020, want 0x020 PASS: xapic - reading 0x030: got APIC access exit @ page offset 0x030, want 0x030 PASS: xapic - writing 0x12345678 to 0x380: non-virtualized write; val is 0x12345678, want 0x12345678 PASS: xapic - reading 0x390: read 0x12345678, expected 0x12345678. PASS: xapic - writing 0x12345678 to 0x390: non-virtualized writqemu-system-x86_64: terminating on signal 15 from pid 1327 # echo $? 124 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-1044-kvm 4.4.0-1044.50 ProcVersionSignature: Ubuntu 4.4.0-1044.50-kvm 4.4.177 Uname: Linux 4.4.0-1044-kvm x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Mon May 6 10:47:17 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1827866/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1783881] Re: ltp-syscalls: msgstress03 / msgstress04 fails because systemd limits number of processes
** Tags added: sru-20210621 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1783881 Title: ltp-syscalls: msgstress03 / msgstress04 fails because systemd limits number of processes Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Incomplete Status in linux-azure package in Ubuntu: New Status in systemd package in Ubuntu: Invalid Status in linux source package in Xenial: New Status in linux-azure source package in Xenial: New Status in systemd source package in Xenial: Won't Fix Status in linux source package in Bionic: New Status in linux-azure source package in Bionic: New Status in systemd source package in Bionic: Invalid Bug description: As systemd limits the number of processes, this test will fail because it can't fork enough processes. That is limited to when the test is run after logging as user 1000, then running sudo. I guess that logging as root may not cause this to happen. # ./testcases/bin/msgstress03 Fork failed (may be OK if under stress) Fork failed (may be OK if under stress) msgstress031 TFAIL : msgstress03.c:157: Fork failed (may be OK if under stress) # To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1783881/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1876684] Re: fanotify09 case 3 from ubuntu_ltp_syscalls failed
** Tags added: sru-20210621 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1876684 Title: fanotify09 case 3 from ubuntu_ltp_syscalls failed Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: New Status in linux source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Bug description: This is a new test case added 7 days ago [1] Test failed on Focal 5.4.0-29.33 with: fanotify09.c:150: FAIL: group 1 got event: mask 10 pid=41059 fd=24 path=/tmp/ltp-sL4wPwoPJ3/AuNN9M/mntpoint fanotify09.c:150: FAIL: group 2 got event: mask 10 pid=41059 fd=24 path=/tmp/ltp-sL4wPwoPJ3/AuNN9M/mntpoint [1] https://github.com/linux-test-project/ltp/commit/70ca1e8806d227d47c6801262d3f7983652159a4#diff-234c27c769cf07468a81748a0e7330dd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1876684/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932124] Re: Add WWAN framework and drivers support
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel in Ubuntu. https://bugs.launchpad.net/bugs/1932124 Title: Add WWAN framework and drivers support Status in HWE Next: New Status in linux-intel package in Ubuntu: Fix Committed Bug description: [SRU Justification] [Impact] The Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem and Foxconn SDX55 T99W175 5G sub6 PCIE Modem are not supported in 5.11 kernel yet. The new WWAN framework and driver support are required to be backported to detect and control the new WWAN modules. [Fix] Backport the WWAN framework and drivers support from mainline kernel 5.13. [Test Case] Verify whether the Quectel/Foxconn WWAN module are detected or not. And use either `mmcli` commands or NetworkSettings Panel to test the connection. [Where problem could occur] Since the WWAN framework is totally new which makes use of the existing MHI bus drivers and protocols, it should be compatible with old WWAN modules. The regression can be considered as low. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1932124/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934261] Re: use debian source format 3.0 (native)
Hirsute/Impish already have this, and Groovy is EOL-ed on 2021 Jul. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1934261 Title: use debian source format 3.0 (native) Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Bionic: New Status in linux-firmware source package in Focal: New Status in linux-firmware source package in Groovy: Won't Fix Status in linux-firmware source package in Hirsute: Invalid Status in linux-firmware source package in Impish: Invalid Bug description: In Hirsute/Impish, debian source package Standards-Version moved to 4.5.0, and debian/source/format is created with content "3.0 (native)". It should be also helpful to backport this change to other maintaining series. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1934261/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934261] [NEW] use debian source format 3.0 (native)
Public bug reported: In Hirsute/Impish, debian source package Standards-Version moved to 4.5.0, and debian/source/format is created with content "3.0 (native)". It should be also helpful to backport this change to other maintaining series. ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-firmware (Ubuntu Bionic) Importance: Wishlist Status: New ** Affects: linux-firmware (Ubuntu Focal) Importance: Wishlist Status: New ** Affects: linux-firmware (Ubuntu Groovy) Importance: Undecided Status: Won't Fix ** Affects: linux-firmware (Ubuntu Hirsute) Importance: Undecided Status: Invalid ** Affects: linux-firmware (Ubuntu Impish) Importance: Undecided Status: Invalid ** Also affects: linux-firmware (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Groovy) Importance: Undecided Status: New ** Changed in: linux-firmware (Ubuntu Groovy) Status: New => Won't Fix ** Changed in: linux-firmware (Ubuntu Hirsute) Status: New => Invalid ** Changed in: linux-firmware (Ubuntu Impish) Status: New => Invalid ** Changed in: linux-firmware (Ubuntu Focal) Importance: Undecided => Wishlist ** Changed in: linux-firmware (Ubuntu Bionic) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1934261 Title: use debian source format 3.0 (native) Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Bionic: New Status in linux-firmware source package in Focal: New Status in linux-firmware source package in Groovy: Won't Fix Status in linux-firmware source package in Hirsute: Invalid Status in linux-firmware source package in Impish: Invalid Bug description: In Hirsute/Impish, debian source package Standards-Version moved to 4.5.0, and debian/source/format is created with content "3.0 (native)". It should be also helpful to backport this change to other maintaining series. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1934261/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-azure-5.8/5.8.0.1037.39~20.04.9)
All autopkgtests for the newly accepted linux-meta-azure-5.8 (5.8.0.1037.39~20.04.9) for focal have finished running. The following regressions have been reported in tests triggered by the package: systemd/245.4-4ubuntu3.7 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-azure-5.8 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931855] Re: UAF on CAN BCM bcm_rx_handler
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1931855 Title: UAF on CAN BCM bcm_rx_handler Status in linux package in Ubuntu: Fix Released Bug description: [Impact] bcm_rx_handler may run concurrently to can_rx_unregister on bcm_release, which will, then, free the bcm_op that is used by bcm_rx_handler, leading to a system crash. [Potential regression] CAN BCM sockets may stop working as expected. [Test case] Programs from can-utils were run, some of them concurrently. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931855/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932209] Re: UAF on CAN J1939 j1939_can_recv
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1932209 Title: UAF on CAN J1939 j1939_can_recv Status in linux package in Ubuntu: Fix Released Bug description: [Impact] j1939_can_recv may run concurrently to can_rx_unregister on j1939_netdev_stop, which will, then, free the priv struct that is used by j1939_can_recv, leading to a system crash. [Potential regression] CAN J1939 sockets may stop working as expected. [Test case] A program that created multiple threads, binding to J1939 sockets and closing them, while sending RAW CAN sockets were run. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1932209/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830652] Re: On shutdown, peripherals turn off, but fans keep spinning, power LED is lit and screen is frozen at the plymouth screen
Thank you for reporting this bug to Ubuntu. Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Changed in: linux (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1830652 Title: On shutdown, peripherals turn off, but fans keep spinning, power LED is lit and screen is frozen at the plymouth screen Status in linux package in Ubuntu: Won't Fix Bug description: On shutdown, peripherals turn off (keyboard, mouse), but fans keep spinning, motherboard LEDs are lit and screen is frozen at the Ubuntu plymouth screen (no animations, frozen frame). The keyboard is turned off at this point, so the only way to properly shut down the computer is to press the power switch on the case for a few seconds. Without plymouth, the screen turns off as it should, but the other symptoms persist, such as fans never stop, power LED never turns off. Reboot works flawlessly. So does suspending and hibernating. This is currently reproducible on Arch Linux (Linux 5.1.4.arch1-1). See bug report: https://bugs.archlinux.org/task/62539. This is NOT reproducible on Ubuntu 18.10 or older. It started somewhere after Linux 5.0.X. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-15-generic 5.0.0-15.16 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dsilva 1883 F pulseaudio /dev/snd/controlC1: dsilva 1883 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon May 27 18:27:29 2019 InstallationDate: Installed on 2019-05-26 (1 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) IwConfig: enp2s0no wireless extensions. lono wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0951:16bc Kingston Technology Bus 001 Device 002: ID 0951:16d2 Kingston Technology Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. B360M GAMING HD ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-15-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-15-generic N/A linux-backports-modules-5.0.0-15-generic N/A linux-firmware1.178.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/14/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F12 dmi.board.asset.tag: Default string dmi.board.name: B360M GAMING HD dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF12:bd03/14/2019:svnGigabyteTechnologyCo.,Ltd.:pnB360MGAMINGHD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB360MGAMINGHD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B360M GAMING HD dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830652/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934239] Re: mute/micmute LEDs no function on HP EliteBook 830 G8 Notebook PC
** Changed in: oem-priority Assignee: (unassigned) => jeremyszu (os369510) ** Changed in: oem-priority Status: New => Triaged ** Changed in: oem-priority Importance: Undecided => Critical -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1934239 Title: mute/micmute LEDs no function on HP EliteBook 830 G8 Notebook PC Status in OEM Priority Project: Triaged Status in linux package in Ubuntu: New Bug description: [Impact] The mic mute/audio mute LEDS are not work on HP EliteBook 830 G8 Notebook PC [Fix] It needs the specific quirk for the hardware layout. Thus, add the quirks to make it works. [Test] After applying the quirk, the audio/mic mute LEDs are working good. [Where problems could occur] If HP ships the different system boards design with the same subsystem ID of audio codec which is using different GPIO pins (different layout), then the quirk will not work (LEDs will not work when muting audio-output or microphone). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1934239/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1933518] Re: Update SmartPQI driver
These patches are not needed for focal/linux. They are targeted for focal/linux-hwe-5.11, so having them applied for hirsute/linux first is the correct nomination. ** Changed in: linux (Ubuntu Focal) Status: In Progress => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1933518 Title: Update SmartPQI driver Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: Invalid Status in linux source package in Hirsute: In Progress Bug description: [Impact] Improves support in SmartPQI for most recent controllers [Fixes] All are in mainline currently and cleanly cherry pick into Hirsute. c64aab41c5e1 scsi: smartpqi: Remove unused functions 5cad5a507241 scsi: smartpqi: Fix device pointer variable reference static checker issue 667298ceaf04 scsi: smartpqi: Fix blocks_per_row static checker issue d56030f882a7 scsi: smartpqi: Update version to 2.1.8-045 75fbeacca3ad scsi: smartpqi: Add new PCI IDs 43e97ef482ee scsi: smartpqi: Correct system hangs when resuming from hibernation d0cba99fd7a3 scsi: smartpqi: Update enclosure identifier in sysfs 18ff5f0877be scsi: smartpqi: Add additional logging for LUN resets 55732a46d6c5 scsi: smartpqi: Update SAS initiator_port_protocols and target_port_protocols ec504b23df9d scsi: smartpqi: Add phy ID support for the physical drives a425625277a1 scsi: smartpqi: Convert snprintf() to scnprintf() 3268b8a8cf77 scsi: smartpqi: Fix driver synchronization issues 66f1c2b40270 scsi: smartpqi: Update device scan operations 2790cd4d3f6a scsi: smartpqi: Update OFA management 5be9db069d3f scsi: smartpqi: Update RAID bypass handling 9fa820233609 scsi: smartpqi: Update suspend/resume and shutdown 37f3318199ce scsi: smartpqi: Synchronize device resets with mutex 4ccc354bac14 scsi: smartpqi: Update soft reset management for OFA 06b41e0d1800 scsi: smartpqi: Update event handler 7a84a821f194 scsi: smartpqi: Add support for wwid ae0c189db4f1 scsi: smartpqi: Remove timeouts from internal cmds 99a12b487f19 scsi: smartpqi: Disable WRITE SAME for HBA NVMe disks 5be746d7d74b scsi: smartpqi: Add host level stream detection enable c7ffedb3a774 scsi: smartpqi: Add stream detection 583891c9e509 scsi: smartpqi: Align code with oob driver 598bef8d7942 scsi: smartpqi: Add support for long firmware version f6cc2a774aa7 scsi: smartpqi: Add support for BMIC sense feature cmd and feature bits 7a012c23c7a7 scsi: smartpqi: Add support for RAID1 writes 6702d2c40f31 scsi: smartpqi: Add support for RAID5 and RAID6 writes 1a22bc4bee22 scsi: smartpqi: Refactor scatterlist code 281a817f232e scsi: smartpqi: Refactor aio submission code 2708a25643ab scsi: smartpqi: Add support for new product ids b622a601a13a scsi: smartpqi: Correct request leakage during reset operations c6d3ee209b9e scsi: smartpqi: Use host-wide tag space The patches they provided only apply the hunk that applies to the SmartPQI driver. This commit was a much wider commit that removes references to MODULE_SUPPORTED_DEVICE in many drivers across the kernel. 6417f03132a6 module: remove never implemented MODULE_SUPPORTED_DEVICE [Testing] On machines equipped with SmartPQI SCSI controller: 1. reboot tests 2. insmod/rmmod tests 3. fio testing: no performance regressions [Regression Risk] Patchset changes only smartpqi driver so regression is limited to systems equipped with this SCSI device. On such SmartPQI-equipped systems the patchset can cause data corruption, data loss or unavailability of SCSI storage and boot failure. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933518/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1928889] Re: devlink_port_split in net from ubuntu_kernel_selftests linux ADT test failure with linux/5.11.0-18.19 ( list index out of range)
https://lists.ubuntu.com/archives/kernel-team/2021-July/121927.html ** Changed in: linux-oem-5.13 (Ubuntu Focal) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1928889 Title: devlink_port_split in net from ubuntu_kernel_selftests linux ADT test failure with linux/5.11.0-18.19 ( list index out of range) Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: In Progress Status in linux-oem-5.13 source package in Focal: In Progress Status in linux source package in Hirsute: In Progress Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux source package in Impish: In Progress Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Bug description: [Impact] If there is no devlink device available, the devlink_port_split.py in kselftest/net will fail with: # selftests: net: devlink_port_split.py # Traceback (most recent call last): # File "/tmp/autopkgtest.ojlWKQ/build.XZw/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py", line 277, in # main() # File "/tmp/autopkgtest.ojlWKQ/build.XZw/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py", line 242, in main # dev = list(devs.keys())[0] # IndexError: list index out of range not ok 43 selftests: net: devlink_port_split.py # exit=1 [Fix] * 25173dd4093a24 selftests: net: devlink_port_split.py: skip the test if no devlink device This test only exist in our source tree since Hirsute, this patch can be cherry-picked into all affected kernels. [Test Plan] Run this test manually from the patched source tree, the test will be skipped when there is no devlink device: # selftests: net: devlink_port_split.py # no devlink device was found, test skipped ok 7 selftests: net: devlink_port_split.py # SKIP [Where problems could occur] Change limited to testing tool, if this change is incorrect it might cause false-negative result in our test report. [Original Bug Report] This is a scripted bug report about ADT failures while running linux tests for linux/5.11.0-18.19 on hirsute. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Not a regression. Found to occur previously on hirsute/linux 5.11.0-14.15 Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/amd64/l/linux/20210515_005957_75e5a@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/arm64/l/linux/20210513_203508_96fd3@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/ppc64el/l/linux/20210513_163708_c0203@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/s390x/l/linux/20210513_144454_54b04@/log.gz 17:39:37 DEBUG| [stdout] # selftests: net: devlink_port_split.py 17:39:37 DEBUG| [stdout] # Traceback (most recent call last): 17:39:37 DEBUG| [stdout] # File "/tmp/autopkgtest.ojlWKQ/build.XZw/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py", line 277, in 17:39:37 DEBUG| [stdout] # main() 17:39:37 DEBUG| [stdout] # File "/tmp/autopkgtest.ojlWKQ/build.XZw/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py", line 242, in main 17:39:37 DEBUG| [stdout] # dev = list(devs.keys())[0] 17:39:37 DEBUG| [stdout] # IndexError: list index out of range 17:39:37 DEBUG| [stdout] not ok 43 selftests: net: devlink_port_split.py # exit=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1928889/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1923114] Re: ubuntu_kernel_selftests: ./cpu-on-off-test.sh: line 94: echo: write error: Device or resource busy
Found on bionic/linux-azure: 4.15.0-1119.132 ** Tags added: sru-20210621 ** Changed in: ubuntu-kernel-tests Status: New => In Progress ** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Krzysztof Kozlowski (krzk) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure-4.15 in Ubuntu. https://bugs.launchpad.net/bugs/1923114 Title: ubuntu_kernel_selftests: ./cpu-on-off-test.sh: line 94: echo: write error: Device or resource busy Status in ubuntu-kernel-tests: In Progress Status in linux-azure package in Ubuntu: New Status in linux-azure-4.15 package in Ubuntu: New Status in linux-azure source package in Trusty: New Status in linux-azure-4.15 source package in Trusty: New Status in linux-azure source package in Xenial: New Status in linux-azure-4.15 source package in Xenial: New Status in linux-azure source package in Bionic: New Status in linux-azure-4.15 source package in Bionic: New Status in linux-azure source package in Groovy: New Status in linux-azure-4.15 source package in Groovy: New Bug description: Test cpu-hotplug from ubuntu_kernel_selftests failed with bionic :linux-azure-4.15 running on a Basic A2 with 2 cores (besides other instance types): selftests: cpu-on-off-test.sh pid 28041's current affinity mask: 3 pid 28041's new affinity mask: 1 CPU online/offline summary: present_cpus = 0-1 present_max = 1 Cpus in online state: 0-1 Cpus in offline state: 0 Limited scope test: one hotplug cpu (leaves cpu in the original state): online to offline to online: cpu 1 not ok 1..1 selftests: cpu-on-off-test.sh [FAIL] ./cpu-on-off-test.sh: line 94: echo: write error: Device or resource busy offline_cpu_expect_success 1: unexpected fail http://10.246.72.46/4.15.0-1112.124~16.04.1-azure/xenial-linux-azure- azure- amd64-4.15.0-Basic_A2-ubuntu_kernel_selftests/ubuntu_kernel_selftests/results/ubuntu_kernel_selftests .cpu-hotplug/debug/ubuntu_kernel_selftests.cpu-hotplug.DEBUG.html The problem happens at "autotest-client-tests/ubuntu_kernel_selftests /cpu-on-off-test.sh" when executing: echo 0 > $SYSFS/devices/system/cpu/cpu$1/online To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1923114/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1933938] Re: Missing CNVi firmware for Intel AX211/AX201 on ADL
** Also affects: intel Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1933938 Title: Missing CNVi firmware for Intel AX211/AX201 on ADL Status in HWE Next: New Status in intel: New Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Focal: New Status in linux-firmware source package in Impish: New Bug description: * PCI [8086:7af0] Subsystem [8086:4090] (AX211) * WiFi: iwlwifi-so-a0-gf-a0-* * BT: intel/ibt-1040-0041.sfi * PCI [8086:7af0] Subsystem [8086:4070] (AX201) * WiFi: iwlwifi-so-a0-hr-b0-* * BT: ??? To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1933938/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932549] Re: seltests/net: devlink port split failing in H-5.11 KVM kernels (Error sending command: devlink -j dev show)
Found on 5.11.0-1010.10-kvm ** Summary changed: - seltests/net: devlink port split failing in 5.11 kernels (hirsute) + seltests/net: devlink port split failing in H-5.11 KVM kernels (Error sending command: devlink -j dev show) ** Tags added: sru-20210621 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1932549 Title: seltests/net: devlink port split failing in H-5.11 KVM kernels (Error sending command: devlink -j dev show) Status in ubuntu-kernel-tests: Confirmed Status in linux-kvm package in Ubuntu: Confirmed Status in linux-kvm source package in Hirsute: Confirmed Bug description: Got the following selftests/net failure in Hirsute, cycle sru-20210531 : 03:28:51 DEBUG| [stdout] # selftests: net: devlink_port_split.py 03:28:51 DEBUG| [stdout] # Error sending command: devlink -j dev show 03:28:51 DEBUG| [stdout] # 03:28:51 DEBUG| [stdout] # Failed to connect to devlink Netlink 03:28:51 DEBUG| [stdout] # 03:28:51 DEBUG| [stdout] # Traceback (most recent call last): 03:28:51 DEBUG| [stdout] # File "/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py", line 277, in 03:28:51 DEBUG| [stdout] # main() 03:28:51 DEBUG| [stdout] # File "/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py", line 239, in main 03:28:51 DEBUG| [stdout] # assert stderr == "" 03:28:51 DEBUG| [stdout] # AssertionError 03:28:51 DEBUG| [stdout] not ok 43 selftests: net: devlink_port_split.py # exit=1 Noticed that it also failed in previous cycles (I'm not sure why I couldn't find a report...) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1932549/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1928889] Re: devlink_port_split in net from ubuntu_kernel_selftests linux ADT test failure with linux/5.11.0-18.19 ( list index out of range)
** Description changed: [Impact] If there is no devlink device available, the devlink_port_split.py in kselftest/net will fail with: - + # selftests: net: devlink_port_split.py + # Traceback (most recent call last): + # File "/tmp/autopkgtest.ojlWKQ/build.XZw/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py", line 277, in + # main() + # File "/tmp/autopkgtest.ojlWKQ/build.XZw/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py", line 242, in main + # dev = list(devs.keys())[0] + # IndexError: list index out of range + not ok 43 selftests: net: devlink_port_split.py # exit=1 [Fix] * 25173dd4093a24 selftests: net: devlink_port_split.py: skip the test if no devlink device + This test only exist in our source tree since Hirsute, this patch can be + cherry-picked into all affected kernels. [Test Plan] - + Run this test manually from the patched source tree, the test will be skipped when there is no devlink device: + # selftests: net: devlink_port_split.py + # no devlink device was found, test skipped + ok 7 selftests: net: devlink_port_split.py # SKIP [Where problems could occur] + Change limited to testing tool, if this change is incorrect it might cause false-negative result in our test report. [Original Bug Report] This is a scripted bug report about ADT failures while running linux tests for linux/5.11.0-18.19 on hirsute. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Not a regression. Found to occur previously on hirsute/linux 5.11.0-14.15 Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/amd64/l/linux/20210515_005957_75e5a@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/arm64/l/linux/20210513_203508_96fd3@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/ppc64el/l/linux/20210513_163708_c0203@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/s390x/l/linux/20210513_144454_54b04@/log.gz 17:39:37 DEBUG| [stdout] # selftests: net: devlink_port_split.py 17:39:37 DEBUG| [stdout] # Traceback (most recent call last): 17:39:37 DEBUG| [stdout] # File "/tmp/autopkgtest.ojlWKQ/build.XZw/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py", line 277, in 17:39:37 DEBUG| [stdout] # main() 17:39:37 DEBUG| [stdout] # File "/tmp/autopkgtest.ojlWKQ/build.XZw/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py", line 242, in main 17:39:37 DEBUG| [stdout] # dev = list(devs.keys())[0] 17:39:37 DEBUG| [stdout] # IndexError: list index out of range 17:39:37 DEBUG| [stdout] not ok 43 selftests: net: devlink_port_split.py # exit=1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1928889 Title: devlink_port_split in net from ubuntu_kernel_selftests linux ADT test failure with linux/5.11.0-18.19 ( list index out of range) Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: In Progress Status in linux-oem-5.13 source package in Focal: In Progress Status in linux source package in Hirsute: In Progress Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux source package in Impish: In Progress Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Bug description: [Impact] If there is no devlink device available, the devlink_port_split.py in kselftest/net will fail with: # selftests: net: devlink_port_split.py # Traceback (most recent call last): # File "/tmp/autopkgtest.ojlWKQ/build.XZw/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py", line 277, in # main() # File "/tmp/autopkgtest.ojlWKQ/build.XZw/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py", line 242, in main # dev = list(devs.keys())[0] # IndexError: list index out of range not ok 43 selftests: net: devlink_port_split.py # exit=1 [Fix] * 25173dd4093a24 selftests: net: devlink_port_split.py: skip the test if no devlink device This test only exist in our source tree since Hirsute, this patch can be
[Kernel-packages] [Bug 1908090] Re: ubuntu 20.04 kdump fails
Are you sure you have this bug filed against the correct package? At a glance, it looks like you should file it against linux-meta (see https://packages.ubuntu.com/focal/linux-crashdump ) kexec-tools "provides tools to load a kernel into memory and then "reboot" directly into that kernel using the kexec system call, bypassing the normal boot process." -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/1908090 Title: ubuntu 20.04 kdump fails Status in kexec-tools package in Ubuntu: Confirmed Bug description: When linux-crashdump (5.4.0.58.61) is enabled on Ubuntu 20.04 LTS, everything appears to be in good working order, according to "systemctl status kdump-tools" and "kdump-config status". However, upon an actual crash, the system hangs, and no crash files are produced. I've investigated and have learned that the capture kernel does indeed start, but it is unable to unpack the rootfs/initrd, and thus fails and hangs. [1.070469] Trying to unpack rootfs image as initramfs... [1.333182] swapper/0 invoked oom-killer: gfp_mask=0x100cc2(GFP_HIGHUSER), order=0, oom_score_adj=0 [1.335074] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.4.0-26-generic #30-Ubuntu [1.336396] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Ubuntu-1.8.2-1ubuntu1 04/01/2014 [1.336396] Call Trace: [1.336396] dump_stack+0x6d/0x9a [1.336396] dump_header+0x4f/0x1eb [1.336396] out_of_memory.part.0.cold+0x39/0x83 [1.336396] out_of_memory+0x6d/0xd0 ... [1.413202] ---[ end Kernel panic - not syncing: System is deadlocked on memory ]--- On this system with 8G of memory, the crash memory as specified on the kernel command line is "crashkernel=512M-:192M". I changed the 192M to 256M, and now kdump works. Not sure how the 192M value is chosen, but it does not work. I think this used value used to work for 16.04 and maybe 18.04 (I didn't try), but is no longer useful for 20.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1908090/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1928889] Re: devlink_port_split in net from ubuntu_kernel_selftests linux ADT test failure with linux/5.11.0-18.19 ( list index out of range)
** Description changed: - This is a scripted bug report about ADT failures while running linux - tests for linux/5.11.0-18.19 on hirsute. Whether this is caused by the - dep8 tests of the tested source or the kernel has yet to be determined. + [Impact] + If there is no devlink device available, the devlink_port_split.py in kselftest/net will fail with: + + + [Fix] + * 25173dd4093a24 selftests: net: devlink_port_split.py: skip the test if no devlink device + + + [Test Plan] + + + [Where problems could occur] + + + [Original Bug Report] + This is a scripted bug report about ADT failures while running linux tests for linux/5.11.0-18.19 on hirsute. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Not a regression. Found to occur previously on hirsute/linux 5.11.0-14.15 Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/amd64/l/linux/20210515_005957_75e5a@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/arm64/l/linux/20210513_203508_96fd3@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/ppc64el/l/linux/20210513_163708_c0203@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/s390x/l/linux/20210513_144454_54b04@/log.gz - 17:39:37 DEBUG| [stdout] # selftests: net: devlink_port_split.py 17:39:37 DEBUG| [stdout] # Traceback (most recent call last): 17:39:37 DEBUG| [stdout] # File "/tmp/autopkgtest.ojlWKQ/build.XZw/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py", line 277, in 17:39:37 DEBUG| [stdout] # main() 17:39:37 DEBUG| [stdout] # File "/tmp/autopkgtest.ojlWKQ/build.XZw/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py", line 242, in main 17:39:37 DEBUG| [stdout] # dev = list(devs.keys())[0] 17:39:37 DEBUG| [stdout] # IndexError: list index out of range 17:39:37 DEBUG| [stdout] not ok 43 selftests: net: devlink_port_split.py # exit=1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1928889 Title: devlink_port_split in net from ubuntu_kernel_selftests linux ADT test failure with linux/5.11.0-18.19 ( list index out of range) Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: In Progress Status in linux-oem-5.13 source package in Focal: New Status in linux source package in Hirsute: In Progress Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux source package in Impish: In Progress Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Bug description: [Impact] If there is no devlink device available, the devlink_port_split.py in kselftest/net will fail with: # selftests: net: devlink_port_split.py # Traceback (most recent call last): # File "/tmp/autopkgtest.ojlWKQ/build.XZw/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py", line 277, in # main() # File "/tmp/autopkgtest.ojlWKQ/build.XZw/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py", line 242, in main # dev = list(devs.keys())[0] # IndexError: list index out of range not ok 43 selftests: net: devlink_port_split.py # exit=1 [Fix] * 25173dd4093a24 selftests: net: devlink_port_split.py: skip the test if no devlink device This test only exist in our source tree since Hirsute, this patch can be cherry-picked into all affected kernels. [Test Plan] Run this test manually from the patched source tree, the test will be skipped when there is no devlink device: # selftests: net: devlink_port_split.py # no devlink device was found, test skipped ok 7 selftests: net: devlink_port_split.py # SKIP [Where problems could occur] Change limited to testing tool, if this change is incorrect it might cause false-negative result in our test report. [Original Bug Report] This is a scripted bug report about ADT failures while running linux tests for linux/5.11.0-18.19 on hirsute. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Not a regression. Found to occur previously on hirsute/linux 5.11.0-14.15 Testing failed on: amd64:
[Kernel-packages] [Bug 1928889] Re: devlink_port_split in net from ubuntu_kernel_selftests linux ADT test failure with linux/5.11.0-18.19 ( list index out of range)
Found on 5.13.0-1005.5-oem ** Changed in: linux-oem-5.10 (Ubuntu Focal) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: linux-oem-5.10 (Ubuntu Focal) Status: New => In Progress ** Also affects: linux-oem-5.13 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-5.13 (Ubuntu Impish) Status: New => Invalid ** Tags added: sru-20210621 ** Changed in: linux-oem-5.13 (Ubuntu Hirsute) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1928889 Title: devlink_port_split in net from ubuntu_kernel_selftests linux ADT test failure with linux/5.11.0-18.19 ( list index out of range) Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: In Progress Status in linux-oem-5.13 source package in Focal: New Status in linux source package in Hirsute: In Progress Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux source package in Impish: In Progress Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Bug description: [Impact] If there is no devlink device available, the devlink_port_split.py in kselftest/net will fail with: [Fix] * 25173dd4093a24 selftests: net: devlink_port_split.py: skip the test if no devlink device [Test Plan] [Where problems could occur] [Original Bug Report] This is a scripted bug report about ADT failures while running linux tests for linux/5.11.0-18.19 on hirsute. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Not a regression. Found to occur previously on hirsute/linux 5.11.0-14.15 Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/amd64/l/linux/20210515_005957_75e5a@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/arm64/l/linux/20210513_203508_96fd3@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/ppc64el/l/linux/20210513_163708_c0203@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/s390x/l/linux/20210513_144454_54b04@/log.gz 17:39:37 DEBUG| [stdout] # selftests: net: devlink_port_split.py 17:39:37 DEBUG| [stdout] # Traceback (most recent call last): 17:39:37 DEBUG| [stdout] # File "/tmp/autopkgtest.ojlWKQ/build.XZw/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py", line 277, in 17:39:37 DEBUG| [stdout] # main() 17:39:37 DEBUG| [stdout] # File "/tmp/autopkgtest.ojlWKQ/build.XZw/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py", line 242, in main 17:39:37 DEBUG| [stdout] # dev = list(devs.keys())[0] 17:39:37 DEBUG| [stdout] # IndexError: list index out of range 17:39:37 DEBUG| [stdout] not ok 43 selftests: net: devlink_port_split.py # exit=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1928889/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1919177] Re: Azure: issues with accelerated networking on Hirsute
I tried to reproduce the issue with the latest hirsute image pushed to
Azure and it appears that I cannot.
While I can still reproduce the issue with 20210511.1, I can't with
20210622.1.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1919177
Title:
Azure: issues with accelerated networking on Hirsute
Status in cloud-init:
Incomplete
Status in cloud-init package in Ubuntu:
Incomplete
Status in linux-azure package in Ubuntu:
Invalid
Status in systemd package in Ubuntu:
Fix Released
Status in cloud-init source package in Hirsute:
Incomplete
Status in linux-azure source package in Hirsute:
Invalid
Status in systemd source package in Hirsute:
New
Bug description:
[General]
On Azure, when provisioning a Hirsute VM with Accelerated Networking
enabled, sometimes part of the cloud-init configuration is not
applied.
Especially, in those cases, the public SSH key is not setup properly.
[how to reproduce]
Start a VM with AN enabled:
```
az vm create --name "$VM_NAME --resource-group "$GROUP" --location "UK South"
--image
'Canonical:0001-com-ubuntu-server-hirsute-daily:21_04-daily-gen2:latest' --size
Standard_F8s_v2 --admin-username ubuntu --ssh-key-value "$SSH_KEY"
--accelerated-networking
```
After a moment, try to SSH: if you succeed, delete and recreate a new
VM.
[troubleshooting]
To be able to connect into the VM, run:
az vm run-command invoke -g "$GROUP" -n "$VM_NAME" --command-id
RunShellScript --scripts "sudo -u ubuntu ssh-import-id $LP_USERNAME"
```
In "/run/cloud-init/instance-data.json", I can see:
```
"publicKeys": [
{
"keyData": "",
"path": "/home/ubuntu/.ssh/authorized_keys"
}
],
```
as expected.
[workaround]
As mentioned, Azure allows the user to run command into the VM without
SSH connection. To do so, one can use the Azure CLI:
az vm run-command invoke -g "$GROUP" -n "$VM_NAME" --command-id
RunShellScript --scripts "sudo -u ubuntu ssh-import-id $LP_USERNAME"
This example uses "ssh-import-id" but it's also possible to just echo
a given public key into /home/ubuntu/.ssh/authorized_keys
NOTE: this will only solves the SSH issue, I do not know if this bug
affects other things. If so the user would have to apply those things
manually.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1919177/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1928889] Re: devlink_port_split in net from ubuntu_kernel_selftests linux ADT test failure with linux/5.11.0-18.19 ( list index out of range)
** Changed in: linux (Ubuntu Focal) Status: New => Invalid ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: Incomplete ** Also affects: linux-oem-5.10 (Ubuntu Impish) Importance: Undecided Status: Invalid ** Changed in: linux (Ubuntu Impish) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Impish) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1928889 Title: devlink_port_split in net from ubuntu_kernel_selftests linux ADT test failure with linux/5.11.0-18.19 ( list index out of range) Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: New Status in linux source package in Hirsute: In Progress Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux source package in Impish: In Progress Status in linux-oem-5.10 source package in Impish: Invalid Bug description: This is a scripted bug report about ADT failures while running linux tests for linux/5.11.0-18.19 on hirsute. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Not a regression. Found to occur previously on hirsute/linux 5.11.0-14.15 Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/amd64/l/linux/20210515_005957_75e5a@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/arm64/l/linux/20210513_203508_96fd3@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/ppc64el/l/linux/20210513_163708_c0203@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/s390x/l/linux/20210513_144454_54b04@/log.gz 17:39:37 DEBUG| [stdout] # selftests: net: devlink_port_split.py 17:39:37 DEBUG| [stdout] # Traceback (most recent call last): 17:39:37 DEBUG| [stdout] # File "/tmp/autopkgtest.ojlWKQ/build.XZw/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py", line 277, in 17:39:37 DEBUG| [stdout] # main() 17:39:37 DEBUG| [stdout] # File "/tmp/autopkgtest.ojlWKQ/build.XZw/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py", line 242, in main 17:39:37 DEBUG| [stdout] # dev = list(devs.keys())[0] 17:39:37 DEBUG| [stdout] # IndexError: list index out of range 17:39:37 DEBUG| [stdout] not ok 43 selftests: net: devlink_port_split.py # exit=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1928889/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1928889] Re: devlink_port_split in net from ubuntu_kernel_selftests linux ADT test failure with linux/5.11.0-18.19 ( list index out of range)
Spotted on H 5.11.0-24.25-generic s390x. ** Tags added: s490x ** Tags removed: s490x ** Tags added: s390x ** Changed in: linux (Ubuntu Hirsute) Status: New => In Progress ** Changed in: linux (Ubuntu Hirsute) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: linux-oem-5.10 (Ubuntu) Status: New => Invalid ** Changed in: linux-oem-5.10 (Ubuntu Hirsute) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1928889 Title: devlink_port_split in net from ubuntu_kernel_selftests linux ADT test failure with linux/5.11.0-18.19 ( list index out of range) Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: New Status in linux source package in Hirsute: In Progress Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: This is a scripted bug report about ADT failures while running linux tests for linux/5.11.0-18.19 on hirsute. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Not a regression. Found to occur previously on hirsute/linux 5.11.0-14.15 Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/amd64/l/linux/20210515_005957_75e5a@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/arm64/l/linux/20210513_203508_96fd3@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/ppc64el/l/linux/20210513_163708_c0203@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/s390x/l/linux/20210513_144454_54b04@/log.gz 17:39:37 DEBUG| [stdout] # selftests: net: devlink_port_split.py 17:39:37 DEBUG| [stdout] # Traceback (most recent call last): 17:39:37 DEBUG| [stdout] # File "/tmp/autopkgtest.ojlWKQ/build.XZw/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py", line 277, in 17:39:37 DEBUG| [stdout] # main() 17:39:37 DEBUG| [stdout] # File "/tmp/autopkgtest.ojlWKQ/build.XZw/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py", line 242, in main 17:39:37 DEBUG| [stdout] # dev = list(devs.keys())[0] 17:39:37 DEBUG| [stdout] # IndexError: list index out of range 17:39:37 DEBUG| [stdout] not ok 43 selftests: net: devlink_port_split.py # exit=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1928889/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1928889] Re: devlink_port_split in net from ubuntu_kernel_selftests linux ADT test failure with linux/5.11.0-18.19 ( list index out of range)
Patch landed upstream: https://github.com/torvalds/linux/commit/25173dd4093a24e977e2af9cd5654c205bf13547 ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.10 (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1928889 Title: devlink_port_split in net from ubuntu_kernel_selftests linux ADT test failure with linux/5.11.0-18.19 ( list index out of range) Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: New Status in linux source package in Hirsute: In Progress Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: This is a scripted bug report about ADT failures while running linux tests for linux/5.11.0-18.19 on hirsute. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Not a regression. Found to occur previously on hirsute/linux 5.11.0-14.15 Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/amd64/l/linux/20210515_005957_75e5a@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/arm64/l/linux/20210513_203508_96fd3@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/ppc64el/l/linux/20210513_163708_c0203@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/s390x/l/linux/20210513_144454_54b04@/log.gz 17:39:37 DEBUG| [stdout] # selftests: net: devlink_port_split.py 17:39:37 DEBUG| [stdout] # Traceback (most recent call last): 17:39:37 DEBUG| [stdout] # File "/tmp/autopkgtest.ojlWKQ/build.XZw/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py", line 277, in 17:39:37 DEBUG| [stdout] # main() 17:39:37 DEBUG| [stdout] # File "/tmp/autopkgtest.ojlWKQ/build.XZw/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py", line 242, in main 17:39:37 DEBUG| [stdout] # dev = list(devs.keys())[0] 17:39:37 DEBUG| [stdout] # IndexError: list index out of range 17:39:37 DEBUG| [stdout] not ok 43 selftests: net: devlink_port_split.py # exit=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1928889/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934240] [NEW] Add Thunderbolt support for Intel Alder Lake
Public bug reported: [Impact] Intel ADL TBT doesn't work. [Fix] Add ADL ID so TBT driver can probe. [Test] The driver is bound to the device in lspci. [Where problems could occur] These are new IDs, so no regression can happen. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Low Status: Confirmed ** Affects: linux-oem-5.10 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-oem-5.13 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: Won't Fix ** Affects: linux-oem-5.10 (Ubuntu Focal) Importance: Low Status: Confirmed ** Affects: linux-oem-5.13 (Ubuntu Focal) Importance: Low Status: Confirmed ** Affects: linux (Ubuntu Hirsute) Importance: Low Status: Confirmed ** Affects: linux-oem-5.10 (Ubuntu Hirsute) Importance: Undecided Status: Invalid ** Affects: linux-oem-5.13 (Ubuntu Hirsute) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Impish) Importance: Low Status: Confirmed ** Affects: linux-oem-5.10 (Ubuntu Impish) Importance: Undecided Status: Invalid ** Affects: linux-oem-5.13 (Ubuntu Impish) Importance: Undecided Status: Invalid ** Tags: oem-priority originate-from-1931192 somerville ** Also affects: linux-oem-5.10 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-oem-5.13 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux-oem-5.10 (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux-oem-5.13 (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux-oem-5.10 (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux-oem-5.13 (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.10 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.13 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => Won't Fix ** Changed in: linux (Ubuntu Hirsute) Status: New => Confirmed ** Changed in: linux (Ubuntu Impish) Status: New => Confirmed ** Changed in: linux-oem-5.10 (Ubuntu Focal) Status: New => Confirmed ** Changed in: linux-oem-5.10 (Ubuntu Hirsute) Status: New => Invalid ** Changed in: linux-oem-5.10 (Ubuntu Impish) Status: New => Invalid ** Changed in: linux-oem-5.13 (Ubuntu Focal) Status: New => Confirmed ** Changed in: linux-oem-5.13 (Ubuntu Hirsute) Status: New => Invalid ** Changed in: linux-oem-5.13 (Ubuntu Impish) Status: New => Invalid ** Changed in: linux (Ubuntu Hirsute) Importance: Undecided => Low ** Changed in: linux (Ubuntu Impish) Importance: Undecided => Low ** Changed in: linux-oem-5.10 (Ubuntu Focal) Importance: Undecided => Low ** Changed in: linux-oem-5.13 (Ubuntu Focal) Importance: Undecided => Low ** Tags added: oem-priority originate-from-1931192 somerville -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1934240 Title: Add Thunderbolt support for Intel Alder Lake Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.10 source package in Focal: Confirmed Status in linux-oem-5.13 source package in Focal: Confirmed Status in linux source package in Hirsute: Confirmed Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux source package in Impish: Confirmed Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Bug description: [Impact] Intel ADL TBT doesn't work. [Fix] Add ADL ID so TBT driver can probe. [Test] The driver is bound to the device in lspci. [Where problems could occur] These are new IDs, so no regression can happen. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1934240/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1933518] Re: Update SmartPQI driver
Thanks Don for testing. I sent a SRU with the commits. ** Changed in: linux (Ubuntu Focal) Importance: Undecided => High ** Changed in: linux (Ubuntu Hirsute) Importance: Medium => High ** Changed in: linux (Ubuntu Hirsute) Assignee: Jeff Lane (bladernr) => Krzysztof Kozlowski (krzk) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1933518 Title: Update SmartPQI driver Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Hirsute: In Progress Bug description: [Impact] Improves support in SmartPQI for most recent controllers [Fixes] All are in mainline currently and cleanly cherry pick into Hirsute. c64aab41c5e1 scsi: smartpqi: Remove unused functions 5cad5a507241 scsi: smartpqi: Fix device pointer variable reference static checker issue 667298ceaf04 scsi: smartpqi: Fix blocks_per_row static checker issue d56030f882a7 scsi: smartpqi: Update version to 2.1.8-045 75fbeacca3ad scsi: smartpqi: Add new PCI IDs 43e97ef482ee scsi: smartpqi: Correct system hangs when resuming from hibernation d0cba99fd7a3 scsi: smartpqi: Update enclosure identifier in sysfs 18ff5f0877be scsi: smartpqi: Add additional logging for LUN resets 55732a46d6c5 scsi: smartpqi: Update SAS initiator_port_protocols and target_port_protocols ec504b23df9d scsi: smartpqi: Add phy ID support for the physical drives a425625277a1 scsi: smartpqi: Convert snprintf() to scnprintf() 3268b8a8cf77 scsi: smartpqi: Fix driver synchronization issues 66f1c2b40270 scsi: smartpqi: Update device scan operations 2790cd4d3f6a scsi: smartpqi: Update OFA management 5be9db069d3f scsi: smartpqi: Update RAID bypass handling 9fa820233609 scsi: smartpqi: Update suspend/resume and shutdown 37f3318199ce scsi: smartpqi: Synchronize device resets with mutex 4ccc354bac14 scsi: smartpqi: Update soft reset management for OFA 06b41e0d1800 scsi: smartpqi: Update event handler 7a84a821f194 scsi: smartpqi: Add support for wwid ae0c189db4f1 scsi: smartpqi: Remove timeouts from internal cmds 99a12b487f19 scsi: smartpqi: Disable WRITE SAME for HBA NVMe disks 5be746d7d74b scsi: smartpqi: Add host level stream detection enable c7ffedb3a774 scsi: smartpqi: Add stream detection 583891c9e509 scsi: smartpqi: Align code with oob driver 598bef8d7942 scsi: smartpqi: Add support for long firmware version f6cc2a774aa7 scsi: smartpqi: Add support for BMIC sense feature cmd and feature bits 7a012c23c7a7 scsi: smartpqi: Add support for RAID1 writes 6702d2c40f31 scsi: smartpqi: Add support for RAID5 and RAID6 writes 1a22bc4bee22 scsi: smartpqi: Refactor scatterlist code 281a817f232e scsi: smartpqi: Refactor aio submission code 2708a25643ab scsi: smartpqi: Add support for new product ids b622a601a13a scsi: smartpqi: Correct request leakage during reset operations c6d3ee209b9e scsi: smartpqi: Use host-wide tag space The patches they provided only apply the hunk that applies to the SmartPQI driver. This commit was a much wider commit that removes references to MODULE_SUPPORTED_DEVICE in many drivers across the kernel. 6417f03132a6 module: remove never implemented MODULE_SUPPORTED_DEVICE [Testing] On machines equipped with SmartPQI SCSI controller: 1. reboot tests 2. insmod/rmmod tests 3. fio testing: no performance regressions [Regression Risk] Patchset changes only smartpqi driver so regression is limited to systems equipped with this SCSI device. On such SmartPQI-equipped systems the patchset can cause data corruption, data loss or unavailability of SCSI storage and boot failure. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933518/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1933950] Re: [i915] Black screen when I login in using kernel 5.8.0-59 but not 5.8.0-25
https://ubuntu.com/tutorials/upgrading-ubuntu-desktop -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1933950 Title: [i915] Black screen when I login in using kernel 5.8.0-59 but not 5.8.0-25 Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: New Bug description: There was also no brightness setting. I have reinstalled ubuntu 3 times already. This happened after the updates on June 24th. The only solution is not to install ubuntu updates. As soon as I install updates, there is a black screen. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.80 Fri May 7 06:55:54 UTC 2021 GCC version: gcc version 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.10) ApportVersion: 2.20.11-0ubuntu50.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jun 29 11:22:08 2021 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu DkmsStatus: nvidia, 460.80, 5.8.0-25-generic, x86_64: installed nvidia, 460.80, 5.8.0-59-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics 630 (Mobile) [103c:85fb] NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] [10de:2191] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company TU116M [GeForce GTX 1660 Ti Mobile] [103c:85fb] InstallationDate: Installed on 2021-06-25 (3 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: HP HP Pavilion Gaming Laptop 15-dk0xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic root=UUID=a7c41e63-e7ea-43e0-9de0-55322f489ee5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2020 dmi.bios.release: 15.33 dmi.bios.vendor: Insyde dmi.bios.version: F.33 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 85FB dmi.board.vendor: HP dmi.board.version: 42.42 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 42.42 dmi.modalias: dmi:bvnInsyde:bvrF.33:bd07/16/2020:br15.33:efr42.42:svnHP:pnHPPavilionGamingLaptop15-dk0xxx:pvrType1ProductConfigId:rvnHP:rn85FB:rvr42.42:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Gaming Laptop 15-dk0xxx dmi.product.sku: 2C7M8EA#ACB dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933950/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934239] Re: mute/micmute LEDs no function on HP EliteBook 830 G8 Notebook PC
Now I'm waiting for maintainer submit the patches to linux-next. https://lore.kernel.org/lkml/20210625133414.26760-1-jeremy@canonical.com/ ** Tags added: oem-priority originate-from-1934032 stella ** Tags added: originate-from-1933952 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1934239 Title: mute/micmute LEDs no function on HP EliteBook 830 G8 Notebook PC Status in OEM Priority Project: New Status in linux package in Ubuntu: New Bug description: [Impact] The mic mute/audio mute LEDS are not work on HP EliteBook 830 G8 Notebook PC [Fix] It needs the specific quirk for the hardware layout. Thus, add the quirks to make it works. [Test] After applying the quirk, the audio/mic mute LEDs are working good. [Where problems could occur] If HP ships the different system boards design with the same subsystem ID of audio codec which is using different GPIO pins (different layout), then the quirk will not work (LEDs will not work when muting audio-output or microphone). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1934239/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
