[Kernel-packages] [Bug 1877575] Re: kernel crash with 0010:ovl_open_realfile+0x4a/0x150 [overlay] in Qemu with focal daily
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1877575 Title: kernel crash with 0010:ovl_open_realfile+0x4a/0x150 [overlay] in Qemu with focal daily Status in linux package in Ubuntu: Expired Status in qemu package in Ubuntu: Invalid Bug description: Focal daily 20200507 (started earlier) Kernel is 5.4.0-30.34 Kernel crashes on boot in Qemu with: [4.019922] RIP: 0010:ovl_open_realfile+0x4a/0x150 [overlay] [4.022101] Code: 44 8b 6f 40 65 48 8b 04 25 28 00 00 00 48 89 45 d0 31 c0 49 8b 7e 28 41 81 cd 00 00 04 04 e8 9d d4 ff ff 49 89 c7 48 8b 45 c8 <48> 8b 40 68 48 81 78 60 62 6a 65 6a 0f 84 a6 00 00 00 65 48 8b 04 [4.027487] RSP: 0018:ac44c0707c08 EFLAGS: 00010202 [4.029424] RAX: 0f230ca096f12900 RBX: 9e44e9c2eaa0 RCX: 0001 [4.031645] RDX: 9e44ea9ae540 RSI: 9e44e9c2eaa0 RDI: 9e44fb281f00 [4.033811] RBP: ac44c0707c50 R08: 9e44e9e3cc00 R09: [4.036428] R10: 9e44ea9ae540 R11: R12: 9e44f9ec9c00 [4.038737] R13: 04048002 R14: 9e44eaa51b00 R15: 9e44e9e3cc00 [4.046087] FS: 7f91962a6600() GS:9e44fbb0() knlGS: [4.051277] CS: 0010 DS: ES: CR0: 80050033 [4.055455] CR2: 56295fbc4a59 CR3: 000169c8 CR4: 06e0 [4.059614] general protection fault: [#4] SMP NOPTI [4.061700] CPU: 1 PID: 360 Comm: cp Tainted: G D 5.4.0-30-generic #34-Ubuntu [4.063016] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.13.0-1ubuntu1 04/01/2014 [4.063016] RIP: 0010:ovl_open_realfile+0x4a/0x150 [overlay] [4.063016] Code: 44 8b 6f 40 65 48 8b 04 25 28 00 00 00 48 89 45 d0 31 c0 49 8b 7e 28 41 81 cd 00 00 04 04 e8 9d d4 ff ff 49 89 c7 48 8b 45 c8 <48> 8b 40 68 48 81 78 60 62 6a 65 6a 0f 84 a6 00 00 00 65 48 8b 04 [4.063016] RSP: 0018:ac44c0373c08 EFLAGS: 00010206 [4.063016] RAX: 1579f0d048c0c300 RBX: 9e44eaa3f478 RCX: [4.063016] RDX: RSI: 9e44eaa3f478 RDI: 9e44fb281f00 [4.063016] RBP: ac44c0373c50 R08: 9e44fb3ac6c0 R09: [4.063016] R10: 0001 R11: 007461642e73 R12: 9e44f9b2d700 [4.063016] R13: 04048000 R14: 9e44fa3d65c0 R15: 9e44fb3ac6c0 [4.063016] FS: 7f91962a6600() GS:9e44fbb0() knlGS: [4.063016] CS: 0010 DS: ES: CR0: 80050033 [4.063016] CR2: 56295fbc4a59 CR3: 000169c8 CR4: 06e0 [4.063016] Call Trace: [4.063016] ? ovl_llseek+0x120/0x120 [overlay] [4.063016] ovl_open+0x57/0x90 [overlay] [4.063016] do_dentry_open+0x143/0x3a0 [4.063016] vfs_open+0x2d/0x30 [4.063016] do_last+0x194/0x900 [4.063016] path_openat+0x8d/0x290 [4.063016] do_filp_open+0x91/0x100 [4.063016] ? __alloc_fd+0x46/0x150 [4.063016] do_sys_open+0x17e/0x290 [4.063016] __x64_sys_openat+0x20/0x30 [4.124120] do_syscall_64+0x57/0x190 [4.124120] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [4.124120] RIP: 0033:0x7f91961c3d1b [4.124120] Code: 25 00 00 41 00 3d 00 00 41 00 74 4b 64 8b 04 25 18 00 00 00 85 c0 75 67 44 89 e2 48 89 ee bf 9c ff ff ff b8 01 01 00 00 0f 05 <48> 3d 00 f0 ff ff 0f 87 91 00 00 00 48 8b 4c 24 28 64 48 33 0c 25 [4.124120] RSP: 002b:7ffebc71f1b0 EFLAGS: 0246 ORIG_RAX: 0101 [4.124120] RAX: ffda RBX: RCX: 7f91961c3d1b [4.124120] RDX: RSI: 562960241670 RDI: ff9c [4.124120] RBP: 562960241670 R08: 0001 R09: 0013 [4.124120] R10: R11: 0246 R12: [4.124120] R13: R14: 7ffebc71f298 R15: [4.124120] Modules linked in: overlay nls_utf8 isofs dm_mirror dm_region_hash dm_log hid_generic usbhid hid qxl ttm drm_kms_helper ahci syscopyarea sysfillrect virtio_net net_failover i2c_i801 libahci psmouse lpc_ich sysimgblt fb_sys_fops failover virtio_blk drm Reproduced on bionic and focal hosts. Groovy daily boots fine. boot message attached. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: qemu 1:4.2-3ubuntu6 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu32 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri May 8 15:36:38
[Kernel-packages] [Bug 1878749] Re: Kernel bug when running btrfs balance
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878749 Title: Kernel bug when running btrfs balance Status in linux package in Ubuntu: Expired Bug description: syslog extract: May 15 00:38:28 rpi4 kernel: [ 1464.345380] kernel BUG at /build/linux-raspi2-5.3-5IVhed/linux-raspi2-5.3-5.3.0/fs/btrfs/relocation.c:4729! May 15 00:38:28 rpi4 kernel: [ 1464.355281] Internal error: Oops - BUG: 0 [#1] SMP May 15 00:38:28 rpi4 kernel: [ 1464.360141] Modules linked in: xt_nat iptable_nat dm_crypt nls_ascii algif_skcipher af_alg ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 xt_hl ip6t_rt ipt_REJECT nf_reject_ipv4 xt_comment btsdio nf_log_ipv4 nf_log_common bluetooth bcm2835_v4l2(CE) xt_LOG ecdh_generic bcm2835_mmal_vchiq(CE) ecc vc_sm_cma(CE) xt_multiport v4l2_common xt_recent videobuf2_vmalloc videobuf2_memops brcmfmac videobuf2_v4l2 brcmutil videobuf2_common cfg80211 videodev xt_limit xt_tcpudp raspberrypi_hwmon mc xt_addrtype rpivid_mem spidev uio_pdrv_genirq uio xt_conntrack ip6table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat nf_conntrack_ftp nf_conntrack nf_defrag_ipv6 sch_fq_codel nf_defrag_ipv4 iptable_filter bpfilter iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 multipath linear broadcom bcm_phy_lib hid_generic May 15 00:38:28 rpi4 kernel: [ 1464.360198] usbhid mdio_bcm_unimac crct10dif_ce sdhci_iproc genet gpio_regulator phy_generic fixed uas usb_storage aes_neon_bs aes_neon_blk crypto_simd cryptd aes_arm64 May 15 00:38:28 rpi4 kernel: [ 1464.464074] CPU: 0 PID: 8225 Comm: btrfs-balance Tainted: G C E 5.3.0-1023-raspi2 #25~18.04.1-Ubuntu May 15 00:38:28 rpi4 kernel: [ 1464.474482] Hardware name: Raspberry Pi 4 Model B Rev 1.2 (DT) May 15 00:38:28 rpi4 kernel: [ 1464.480395] pstate: 2045 (nzCv daif +PAN -UAO) May 15 00:38:28 rpi4 kernel: [ 1464.485330] pc : btrfs_reloc_cow_block+0x34c/0x3a0 [btrfs] May 15 00:38:28 rpi4 kernel: [ 1464.490928] lr : __btrfs_cow_block+0x368/0x600 [btrfs] May 15 00:38:28 rpi4 kernel: [ 1464.496133] sp : 13b437b0 May 15 00:38:28 rpi4 kernel: [ 1464.499487] x29: 13b437b0 x28: May 15 00:38:28 rpi4 kernel: [ 1464.504870] x27: 0001 x26: 0001 May 15 00:38:28 rpi4 kernel: [ 1464.510253] x25: 9c0ac32c4a80 x24: 9c0bb321c618 May 15 00:38:28 rpi4 kernel: [ 1464.515634] x23: 0001 x22: 9c0b63242a50 May 15 00:38:28 rpi4 kernel: [ 1464.521016] x21: 9c0b23e51ef0 x20: 9c0b4f111000 May 15 00:38:28 rpi4 kernel: [ 1464.526399] x19: 9c0b74bb5000 x18: May 15 00:38:28 rpi4 kernel: [ 1464.531780] x17: x16: 40af26f8be78 May 15 00:38:28 rpi4 kernel: [ 1464.537163] x15: x14: May 15 00:38:28 rpi4 kernel: [ 1464.542545] x13: x12: May 15 00:38:28 rpi4 kernel: [ 1464.547926] x11: x10: 9c0b10e83a40 May 15 00:38:28 rpi4 kernel: [ 1464.553308] x9 : 9c0aca004750 x8 : 40af2775b9e7 May 15 00:38:28 rpi4 kernel: [ 1464.558690] x7 : 9c0b578814e1 x6 : 9c0b578814e0 May 15 00:38:28 rpi4 kernel: [ 1464.564071] x5 : 9c0b552b59c0 x4 : 9c0b552b59c0 May 15 00:38:28 rpi4 kernel: [ 1464.569452] x3 : 9c0b63242a50 x2 : 00096be7 May 15 00:38:28 rpi4 kernel: [ 1464.574833] x1 : x0 : 012e979b4000 May 15 00:38:28 rpi4 kernel: [ 1464.580216] Call trace: May 15 00:38:28 rpi4 kernel: [ 1464.582735] btrfs_reloc_cow_block+0x34c/0x3a0 [btrfs] May 15 00:38:28 rpi4 kernel: [ 1464.587979] __btrfs_cow_block+0x368/0x600 [btrfs] May 15 00:38:28 rpi4 kernel: [ 1464.592869] btrfs_cow_block+0x100/0x218 [btrfs] May 15 00:38:28 rpi4 kernel: [ 1464.597583] btrfs_search_slot+0x560/0x930 [btrfs] May 15 00:38:28 rpi4 kernel: [ 1464.602475] do_relocation+0x408/0x5b8 [btrfs] May 15 00:38:28 rpi4 kernel: [ 1464.607014] relocate_tree_blocks+0x4f8/0x5c0 [btrfs] May 15 00:38:28 rpi4 kernel: [ 1464.612170] relocate_block_group+0x3dc/0x638 [btrfs] May 15 00:38:28 rpi4 kernel: [ 1464.617325] btrfs_relocate_block_group+0x18c/0x2d8 [btrfs] May 15 00:38:28 rpi4 kernel: [ 1464.623009] btrfs_relocate_chunk+0x48/0xe0 [btrfs] May 15 00:38:28 rpi4 kernel: [ 1464.627988] __btrfs_balance+0x864/0xa38 [btrfs] May 15 00:38:28 rpi4 kernel: [ 1464.632703] btrfs_balance+0x434/0x748 [btrfs] May 15 00:38:28 rpi4 kernel: [ 1464.637301] balance_kthread+0x38/0x70 [btrfs] May 15 00:38:28
[Kernel-packages] [Bug 1880357] Re: Broadcom BCM4312 [14e4:4315] Subsystem [103c:137d]: Driver wifi bcm4312 802.11b LP-PHY
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1880357 Title: Broadcom BCM4312 [14e4:4315] Subsystem [103c:137d]: Driver wifi bcm4312 802.11b LP-PHY Status in linux package in Ubuntu: Expired Bug description: Don't work it ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-101.102-generic 4.15.18 Uname: Linux 4.15.0-101-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat May 23 22:46:26 2020 DistUpgraded: 2020-05-22 23:38:09,031 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: broadcom-sta, 6.30.223.271, 4.15.0-101-generic, x86_64: installed (WARNING! Diff between built and installed module!) broadcom-sta, 6.30.223.271, 4.4.0-179-generic, x86_64: installed GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated Graphics Controller [103c:30f7] Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated Graphics Controller [103c:30f7] InstallationDate: Installed on 2020-05-21 (2 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Hewlett-Packard HP Pavilion dv4 Notebook PC ProcEnviron: LANGUAGE=es_MX:es PATH=(custom, no user) LANG=es_MX.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-101-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2020-05-23 (0 days ago) dmi.bios.date: 10/17/2008 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.22 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 30F7 dmi.board.vendor: Compal dmi.board.version: 99.80 dmi.chassis.type: 10 dmi.chassis.vendor: Compal dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.22:bd10/17/2008:svnHewlett-Packard:pnHPPaviliondv4NotebookPC:pvrF.22:rvnCompal:rn30F7:rvr99.80:cvnCompal:ct10:cvrN/A: dmi.product.family: 103C_5335KV dmi.product.name: HP Pavilion dv4 Notebook PC dmi.product.version: F.22 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Fri May 22 21:39:27 2020 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5157 vendor CMO xserver.version: 2:1.18.4-0ubuntu0.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880357/+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 1880325] Re: Intel Wireless Centrino N100 error in Txrate and Bitrate
[Expired for linux-meta (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux-meta (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1880325 Title: Intel Wireless Centrino N100 error in Txrate and Bitrate Status in linux-meta package in Ubuntu: Expired Bug description: In the last week install a Xubuntu 18.04 distro in the netbook of my brother this install all fine but the Intel Centrino Wireless N100 card doesnt work good because the Bitrate mark 24 and Txrate 14 all time the unique way to connect to the signal of router its put near this. I search in the net in Google to resolve this conflict and fix this explain in the lines below the procedure to obtain this. First this Issue affects this models of Intel Wireless: Wi-Fi 6 products Intel® Wi-Fi 6 AX200 (5.1) Intel® Wi-Fi 6 AX201 (5.2) 802.11ac products Intel® Wireless-AC 9462 (4.14) Intel® Wireless-AC 9461 (4.14) Intel® Wireless-AC 9260 (4.14) Intel® Wireless-AC 9560 (4.14) Intel® Wireless-AC 8265 (4.6) Intel® Wireless-AC 3168 (4.6) Intel® Wireless-AC 8260 (4.1) Intel® Wireless-AC 3165 (4.1) 802.11n or 802.11ac products (SKU dependent) Intel® Wireless 7265 (3.13) Intel® Wireless 7260 (3.10) Intel® Wireless 3160 (3.10) 802.11abgn products Intel® Centrino® Advanced-N 6235 (3.2) Intel® Centrino® Advanced-N 6230 (2.6.36) Intel® Centrino® Advanced-N 6205 (2.6.35) Intel® Centrino® Advance-N + WiMAX 6150 (2.6.30) Intel® Centrino® Advanced-N + WiMAX 6250 (2.6.30) Intel® Centrino® Ultimate-N 6300 (2.6.30) Intel® Centrino® Advanced-N 6200 (2.6.30) Intel® WiMAX/Wi-Fi Link 5350 (2.6.27) Intel® Ultimate N Wi-Fi Link 5300 (2.6.27) Intel® WiMAX/Wi-Fi Link 5150 (2.6.29) Intel® Wi-Fi Link 5100 Series (2.6.27) 802.11bgn products Intel® Centrino® Wireless-N 2230 (3.2) Intel® Centrino® Wireless-N 2200 (3.2) Intel® Centrino® Wireless-N 105 (3.2) Intel® Centrino® Wireless-N 135 (3.2) Intel® Centrino® Wireless-N 100 (2.6.37) Intel® Centrino® Wireless-N 130 (2.6.37) Intel® Centrino® Wireless-N 1030 (2.6.36) Intel® Centrino® Wireless-N 1000 (2.6.30) Second need to go to this page and download the firmware of the model affected: https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi Third decompress the tar in the download folder and us this command in the terminal: cp iwlwifi-*.ucode /lib/firmware Later reboot the machine and enter again Four open a terminal windows and enter the following command: sudo nano /etc/NetworkManager/NetworkManager.conf put this line into the file [device] wifi.scan-rand-mac-address=no save and reboot the Network Manager or reboot the machine Five open a terminal windows and enter the following command: sudo nano /etc/network/interfaces you see hte file equal this: auto lo iface lo inet loopback auto eth0 iface eth0 inet dhcp Substitute eth0 for the driver of your wireless card use in the terminal ifconfig to see Restart Network Manager services or reboot the machine Six edit DNS config file open the terminal and put the following command: sudo nano/etc/resolv.conf Add this lines to the file exactly: # Google IPv4 nameservers nameserver 8.8.8.8 nameserver 8.8.4.4 1 2 3 4 5 # Google IPv6 nameservers nameserver 2001:4860:4860:: nameserver 2001:4860:4860::8844 save and close and restart the machine Ready the Bug its fixed --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: leonardo 1074 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-05-25 (0 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release i386 (20180426) MachineType: Intel Corporation Intel powered classmate PC Package: linux-meta (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=c103aee1-118e-4dcd-88e2-e9871fdc8081 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 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.18 Tags: bionic Uname: Linux 4.15.0-20-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/16/2011 dmi.bios.vendor: Phoenix dmi.bios.version: BPPNV10A.86A.0015.2011.0516.1530 dmi.board.asset.tag: PTL Nanjing dmi.board.name: Intel powered classmate PC dmi.board.vendor: Intel Corporation dmi.board.version: MP PV
[Kernel-packages] [Bug 1779736] Re: umask ignored on NFSv4.2 mounts
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: zfs-linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1779736 Title: umask ignored on NFSv4.2 mounts Status in linux package in Ubuntu: Confirmed Status in nfs-utils package in Ubuntu: Confirmed Status in zfs-linux package in Ubuntu: Confirmed Bug description: After upgrading to kernel 4.15.0-24-generic (on Ubuntu 18.04 LTS) NFSv4.2 mounts ignore the umask when creating files and directories. Files get permissions 666 and directories get 777. Therefore, a umask of 000 is seemingly being forced when creating files/directories in NFS mounts. Mounting with noacl does not resolve the issue. How to replicate: 1. Mount an NFS share (defaults to NFSv4.2) 2. Ensure restrictive umask: umask 022 3. Create directory: mkdir test_dir 4. Create file: touch test_file 5. List: ls -l The result will be: drwxrwxrwx 2 user user 2 Jul 2 12:16 test_dir -rw-rw-rw- 1 user user 0 Jul 2 12:16 test_file while the expected result would be drwxr-xr-x 2 user user 2 Jul 2 12:16 test_dir -rw-r--r-- 1 user user 0 Jul 2 12:16 test_file Bug does not occur when mounting with any of: vers=3 vers=4.0 vers=4.1 I have a suspicion this is related to: https://tools.ietf.org/id/draft-ietf-nfsv4-umask-03.html But since the server does not have ACL's enabled, and mounting with noacl does not resolve the issue this is unexpected behavior. Both server and client are running kernel 4.15.0-24-generic on Ubuntu 18.04 LTS. NFS package versions are: nfs-kernel-server 1:1.3.4-2.1ubuntu5 nfs-common 1:1.3.4-2.1ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779736/+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 1888715] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1888715
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1888715
Title:
UDP data corruption caused by buggy udp_recvmsg() ->
skb_copy_and_csum_datagram_msg()
Status in linux package in Ubuntu:
Incomplete
Bug description:
The Xenial v4.4 kernel (https://kernel.ubuntu.com/git/ubuntu/ubuntu-
xenial.git/tag/?h=Ubuntu-4.4.0-184.214) lacks this upstream bug
fix("make skb_copy_datagram_msg() et.al. preserve ->msg_iter on erro"
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3278682123811dd8ef07de5eb701fc4548fcebf2);
as a result, the v4.4 kernel can deliver corrupt data to the
application when a corrupt packet is closely followed by a valid
packet, and actually the UDP payload of the corrupt packet is
delivered to the application with the "from IP/Port" of the valid
packet, so this is actually a security vulnerability that can be used
to trick the application to think the corrupt packet’s payload is sent
from the valid packet’s IP address/port, i.e. a source IP based
security authentication mechanism can be bypassed.
Details:
For a packet longer than 76 bytes (see line 3951,
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/include/linux/skbuff.h?h=v5.8-rc6#n3948),
Linux delays the UDP checksum verification until the application
invokes the syscall recvmsg().
In the recvmsg() syscall handler, while Linux is copying the UDP
payload to the application’s memory, it calculates the UDP checksum.
If the calculated checksum doesn’t match the received checksum, Linux
drops the corrupt UDP packet, and then starts to process the next
packet (if any), and if the next packet is valid (i.e. the checksum is
correct), Linux will copy the valid UDP packet's payload to the
application’s receiver buffer.
The bug is: before Linux starts to copy the valid UDP packet, the data
structure used to track how many more bytes should be copied to the
application memory is not reset to what it was when the application
just entered the kernel by the syscall! Consequently, only a small
portion or none of the valid packet’s payload is copied to the
application’s receive buffer, and later when the application exits
from the kernel, actually most of the application’s receive buffer
contains the payload of the corrupt packet while recvmsg() returns the
size of the UDP payload of the valid packet. Note: this is actually a
security vulnerability that can be used to trick the application to
think the corrupt packet’s payload is sent from the valid packet’s IP
address/port -- so a source IP based security authentication mechanism
can be bypassed.
The bug was fixed in this 2017 patch “make skb_copy_datagram_msg()
et.al. preserve ->msg_iter on error
(https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3278682123811dd8ef07de5eb701fc4548fcebf2)”,
but unluckily the patch is only backported to the upstream v4.9+
kernels. I'm reporting this bug to request the bugfix to be backported
to the v4.4 Xenial kernel, which is still used by some users and has
not been EOL'ed (https://ubuntu.com/about/release-cycle).
I have the below one-line workaround patch to force the recvmsg() syscall
handler to return to the userspace when Linux detects a corrupt UDP packet, so
the application will invoke the syscall again to receive the next good UDP
packet:
--- a/net/ipv4/udp.c
+++ b/net/ipv4/udp.c
@@ -1367,6 +1367,7 @@ csum_copy_err:
/* starting over for a new packet, but check if we need to yield */
cond_resched();
msg->msg_flags &= ~MSG_TRUNC;
+ return -EAGAIN;
goto try_again;
}
Note: the patch may not work well with blocking sockets, for which
typically the application doesn’t expect an error of -EAGAIN. I guess
it would be safer to return -EINTR instead.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888715/+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 1888715] Re: UDP data corruption caused by buggy udp_recvmsg() -> skb_copy_and_csum_datagram_msg()
Hello Dexuan, wonderful, thanks;
Eric's proposed patch confuses me on one point:
- if (rcu_access_pointer(sk->sk_filter) &&
- udp_lib_checksum_complete(skb))
+ if (udp_lib_checksum_complete(skb))
goto csum_error;
Do you know why the rcu_access_pointer() call has been removed?
Thanks
** Information type changed from Private Security to Public Security
--
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/1888715
Title:
UDP data corruption caused by buggy udp_recvmsg() ->
skb_copy_and_csum_datagram_msg()
Status in linux package in Ubuntu:
Incomplete
Bug description:
The Xenial v4.4 kernel (https://kernel.ubuntu.com/git/ubuntu/ubuntu-
xenial.git/tag/?h=Ubuntu-4.4.0-184.214) lacks this upstream bug
fix("make skb_copy_datagram_msg() et.al. preserve ->msg_iter on erro"
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3278682123811dd8ef07de5eb701fc4548fcebf2);
as a result, the v4.4 kernel can deliver corrupt data to the
application when a corrupt packet is closely followed by a valid
packet, and actually the UDP payload of the corrupt packet is
delivered to the application with the "from IP/Port" of the valid
packet, so this is actually a security vulnerability that can be used
to trick the application to think the corrupt packet’s payload is sent
from the valid packet’s IP address/port, i.e. a source IP based
security authentication mechanism can be bypassed.
Details:
For a packet longer than 76 bytes (see line 3951,
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/include/linux/skbuff.h?h=v5.8-rc6#n3948),
Linux delays the UDP checksum verification until the application
invokes the syscall recvmsg().
In the recvmsg() syscall handler, while Linux is copying the UDP
payload to the application’s memory, it calculates the UDP checksum.
If the calculated checksum doesn’t match the received checksum, Linux
drops the corrupt UDP packet, and then starts to process the next
packet (if any), and if the next packet is valid (i.e. the checksum is
correct), Linux will copy the valid UDP packet's payload to the
application’s receiver buffer.
The bug is: before Linux starts to copy the valid UDP packet, the data
structure used to track how many more bytes should be copied to the
application memory is not reset to what it was when the application
just entered the kernel by the syscall! Consequently, only a small
portion or none of the valid packet’s payload is copied to the
application’s receive buffer, and later when the application exits
from the kernel, actually most of the application’s receive buffer
contains the payload of the corrupt packet while recvmsg() returns the
size of the UDP payload of the valid packet. Note: this is actually a
security vulnerability that can be used to trick the application to
think the corrupt packet’s payload is sent from the valid packet’s IP
address/port -- so a source IP based security authentication mechanism
can be bypassed.
The bug was fixed in this 2017 patch “make skb_copy_datagram_msg()
et.al. preserve ->msg_iter on error
(https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3278682123811dd8ef07de5eb701fc4548fcebf2)”,
but unluckily the patch is only backported to the upstream v4.9+
kernels. I'm reporting this bug to request the bugfix to be backported
to the v4.4 Xenial kernel, which is still used by some users and has
not been EOL'ed (https://ubuntu.com/about/release-cycle).
I have the below one-line workaround patch to force the recvmsg() syscall
handler to return to the userspace when Linux detects a corrupt UDP packet, so
the application will invoke the syscall again to receive the next good UDP
packet:
--- a/net/ipv4/udp.c
+++ b/net/ipv4/udp.c
@@ -1367,6 +1367,7 @@ csum_copy_err:
/* starting over for a new packet, but check if we need to yield */
cond_resched();
msg->msg_flags &= ~MSG_TRUNC;
+ return -EAGAIN;
goto try_again;
}
Note: the patch may not work well with blocking sockets, for which
typically the application doesn’t expect an error of -EAGAIN. I guess
it would be safer to return -EINTR instead.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888715/+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 1859592] Re: Bluetooth unavailable after updates - Reading Intel version information failed (-110)
I also encountered this issue, with ubuntu 18.04 and intel AX200NGW Bluetooth. Would be willing to help provide debugging logs if needed. -- 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/1859592 Title: Bluetooth unavailable after updates - Reading Intel version information failed (-110) Status in linux package in Ubuntu: Incomplete Bug description: After 10 days of uptime with automatic updates, I rebooted. Bluetooth, which I use every day, is no longer available. $ dmesg | grep -i bluetooth [4.846072] Bluetooth: Core ver 2.22 [4.846088] Bluetooth: HCI device and connection manager initialized [4.846092] Bluetooth: HCI socket layer initialized [4.846094] Bluetooth: L2CAP socket layer initialized [4.846096] Bluetooth: SCO socket layer initialized [5.434081] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [5.434082] Bluetooth: BNEP filters: protocol multicast [5.434086] Bluetooth: BNEP socket layer initialized [6.874125] Bluetooth: hci0: command 0xfc05 tx timeout [6.874129] Bluetooth: hci0: Reading Intel version information failed (-110) $ uname -a Linux abu 5.3.2-050302-generic #201910010731 SMP Tue Oct 1 07:33:48 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux AMD Ryzen 5 3400G (Picasso, Raven Ridge) (Asrock A300) Ubuntu 18.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859592/+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 1888647] Re: Realtek wifi dont work after update
This happened to me as well. Luckily I have an ethernet port on my laptop and was able to find a drop so I could apply this fix. Guessing the update blew a bunch of people out of the water. The ppa provided did fix the issue. -- 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/1888647 Title: Realtek wifi dont work after update Status in linux-firmware package in Ubuntu: Triaged Bug description: lsb_release -rd Description:Ubuntu 18.04.4 LTS Release:18.04 apt-cache policy linux-firmware linux-firmware: Installed: 1.173.19 Candidate: 1.173.19 Version table: *** 1.173.19 500 500 http://ru.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://ru.archive.ubuntu.com/ubuntu bionic-updates/main i386 Packages 100 /var/lib/dpkg/status 1.173.18 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main i386 Packages 1.173 500 500 http://ru.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 500 http://ru.archive.ubuntu.com/ubuntu bionic/main i386 Packages PCI Wifi adapter dont work after update Part of kern.log Jul 23 14:04:25 pao-note kernel: [0.570519] pci :02:00.0: [10ec:c822] type 00 class 0x028000 Jul 23 14:04:25 pao-note kernel: [0.570564] pci :02:00.0: reg 0x10: [io 0x2000-0x20ff] Jul 23 14:04:25 pao-note kernel: [0.570598] pci :02:00.0: reg 0x18: [mem 0xb130-0xb130 64bit] Jul 23 14:04:25 pao-note kernel: [0.570758] pci :02:00.0: supports D1 D2 Jul 23 14:04:25 pao-note kernel: [0.570759] pci :02:00.0: PME# supported from D0 D1 D2 D3hot D3cold Jul 23 14:04:25 pao-note kernel: [ 21.479711] rtw_pci :02:00.0: enabling device ( -> 0003) Jul 23 14:04:25 pao-note kernel: [ 21.479783] rtw_pci :02:00.0: Direct firmware load for rtw88/rtw8822c_wow_fw.bin failed with error -2 Jul 23 14:04:25 pao-note kernel: [ 21.479784] rtw_pci :02:00.0: failed to request firmware Jul 23 14:04:25 pao-note kernel: [ 21.480312] rtw_pci :02:00.0: Firmware version 5.0.0, H2C version 14 Jul 23 14:04:25 pao-note kernel: [ 21.593905] rtw_pci :02:00.0 wlp2s0: renamed from wlan0 Jul 23 14:04:25 pao-note kernel: [ 22.164022] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:04:25 pao-note kernel: [ 22.176798] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:04:25 pao-note kernel: [ 22.177910] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:04:35 pao-note kernel: [ 32.014995] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:04:35 pao-note kernel: [ 32.017051] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:04:45 pao-note kernel: [ 42.012048] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:04:45 pao-note kernel: [ 42.013137] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:04:55 pao-note kernel: [ 52.011861] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:04:55 pao-note kernel: [ 52.013348] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:05:05 pao-note kernel: [ 62.203876] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:05:05 pao-note kernel: [ 62.205477] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:05:15 pao-note kernel: [ 72.262757] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:05:15 pao-note kernel: [ 72.263944] rtw_pci :02:00.0: failed to wait firmware completion lspci 00:00.0 Host bridge: Intel Corporation Device 9b61 (rev 0c) 00:02.0 VGA compatible controller: Intel Corporation Device 9b41 (rev 02) 00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 0c) 00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th Gen Core Processor Gaussian Mixture Model 00:12.0 Signal processing controller: Intel Corporation Device 02f9 00:14.0 USB controller: Intel Corporation Device 02ed 00:14.2 RAM memory: Intel Corporation Device 02ef 00:15.0 Serial bus controller [0c80]: Intel Corporation Device 02e8 00:16.0 Communication controller: Intel Corporation Device 02e0 00:17.0 SATA controller: Intel Corporation Device 02d3 00:1d.0 PCI bridge: Intel Corporation Device 02b0 (rev f0) 00:1d.1 PCI bridge: Intel Corporation Device 02b1 (rev f0) 00:1d.2 PCI bridge: Intel Corporation Device 02b2 (rev f0) 00:1d.4 PCI bridge: Intel Corporation Device 02b4 (rev f0) 00:1e.0 Communication controller: Intel Corporation Device 02a8 00:1f.0 ISA bridge: Intel Corporation Device 0284
[Kernel-packages] [Bug 1888617] Re: nvidia-kernel-source-435 435.21-0ubuntu0.18.04.2: nvidia kernel module failed to build
Had the exact same error today. Was able to solve it via: sudo ubuntu-drivers autoinstall then rebooting. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubuntu. https://bugs.launchpad.net/bugs/1888617 Title: nvidia-kernel-source-435 435.21-0ubuntu0.18.04.2: nvidia kernel module failed to build Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Bug description: After a "usual" upgrade, my system did not give any sign of life on the monitor. I tried to boot an older kernel, it worked. Then I discovered, that the problem that nvidia drivers cannot be built against kernel linux-image-5.4.0-42-generic, which could be the problem. from /var/crash/nvidia-kernel-source-435.0.crash : /var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm-drv.c:662:44: error: ‘DRIVER_PRIME’ undeclared here (not in a function); did you mean ‘DRIVER_PCI_DMA’? .driver_features= DRIVER_GEM | DRIVER_PRIME | DRIVER_RENDER, ^~~~ DRIVER_PCI_DMA scripts/Makefile.build:273: recipe for target '/var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm-drv.o' failed make[2]: *** [/var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm-drv.o] Error 1 make[2]: *** Waiting for unfinished jobs ./tools/objtool/objtool check --module --retpoline --uaccess /var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm.o ./tools/objtool/objtool check --module --retpoline --uaccess /var/lib/dkms/nvidia/435.21/build/nvidia-uvm/uvm8_range_group_tree_test.o ./tools/objtool/objtool check --module --retpoline --uaccess /var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm-utils.o ./tools/objtool/objtool check --module --retpoline --uaccess /var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm-encoder.o ./tools/objtool/objtool check --module --retpoline --uaccess /var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm-gem.o ./tools/objtool/objtool check --module --retpoline --uaccess /var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm-connector.o ./tools/objtool/objtool check --module --retpoline --uaccess /var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm-crtc.o Makefile:1731: recipe for target '/var/lib/dkms/nvidia/435.21/build' failed make[1]: *** [/var/lib/dkms/nvidia/435.21/build] Error 2 make[1]: Leaving directory '/usr/src/linux-headers-5.4.0-42-generic' Makefile:81: recipe for target 'modules' failed make: *** [modules] Error 2 DKMSKernelVersion: 5.4.0-42-generic Date: Wed Jul 22 08:08:55 2020 DuplicateSignature: dkms:nvidia-kernel-source-435:435.21-0ubuntu0.18.04.2:/var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm-drv.c:662:44: error: ‘DRIVER_PRIME’ undeclared here (not in a function); did you mean ‘DRIVER_PCI_DMA’? Package: nvidia-kernel-source-435 435.21-0ubuntu0.18.04.2 PackageVersion: 435.21-0ubuntu0.18.04.2 SourcePackage: nvidia-graphics-drivers-435 Title: nvidia-kernel-source-435 435.21-0ubuntu0.18.04.2: nvidia kernel module failed to build ProblemType: Package DistroRelease: Ubuntu 18.04 Package: nvidia-kernel-source-435 435.21-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-62-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 DKMSKernelVersion: 5.4.0-42-generic Date: Wed Jul 22 08:08:55 2020 Dependencies: DuplicateSignature: dkms:nvidia-kernel-source-435:435.21-0ubuntu0.18.04.2:/var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm-drv.c:662:44: error: ‘DRIVER_PRIME’ undeclared here (not in a function); did you mean ‘DRIVER_PCI_DMA’? InstallationDate: Installed on 2020-01-06 (198 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageVersion: 435.21-0ubuntu0.18.04.2 Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 1.6.12ubuntu0.1 SourcePackage: nvidia-graphics-drivers-435 Title: nvidia-kernel-source-435 435.21-0ubuntu0.18.04.2: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-435/+bug/1888617/+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 1842785] Re: Freeze after waking up from suspend on a Ryzen 3000 based system
In some cases this appears to be linked to the use of s2-idle. If you only see s2-idle when you run cat /sys/power/mem_sleep, then try these steps: https://gitlab.freedesktop.org/drm/amd/-/issues/1230#note_580057 ** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #1230 https://gitlab.freedesktop.org/drm/amd/-/issues/1230 -- 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/1842785 Title: Freeze after waking up from suspend on a Ryzen 3000 based system Status in linux package in Ubuntu: Confirmed Bug description: My system is a newly build Ryzen 3600 based system with Vega 56 graphics. On suspend wakeup, the entire system locks up. A workaround is booting with linux kernel version 4.19.69. Using newer linux versions (5.3-rc7) did not fix the issue. The motherboard is an MSI B450I gaming plus ac board; I've loaded up both the official non-beta BIOS (7A40vA8) and the newest beta BIOS (7A40vA91) and both have this issue. No dmesg logs are available after the suspend wakeup (last message is putting the system to sleep) I have a r8169 and iwlwifi based ethernet and wifi cards, but I've tentatively isolated that those two are not an issue by blacklisting the respective modules. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-27-generic 5.0.0-27.28 ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hatsu 2282 F pulseaudio /dev/snd/controlC2: hatsu 2282 F pulseaudio /dev/snd/controlC0: hatsu 2282 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Sep 4 23:14:34 2019 InstallationDate: Installed on 2019-08-27 (9 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Micro-Star International Co., Ltd. MS-7A40 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-27-generic root=UUID=4b8b9e96-fd23-4ade-bcd2-19b9795bd4e6 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-27-generic N/A linux-backports-modules-5.0.0-27-generic N/A linux-firmware1.178.3 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2019-08-27 (9 days ago) dmi.bios.date: 08/19/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.91 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450I GAMING PLUS AC (MS-7A40) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.91:bd08/19/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A40:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450IGAMINGPLUSAC(MS-7A40):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A40 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842785/+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 1690085] Re: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks
** Bug watch added: Linux Kernel Bug Tracker #208615 https://bugzilla.kernel.org/show_bug.cgi?id=208615 -- 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/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks Status in Linux: Expired Status in linux package in Ubuntu: Confirmed Bug description: Hi, We aregetting various kernel crash on a pretty new config. We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using latest BIOS available (1.52) We are running Ubuntu 17.04 (amd64), we've tried different kernel version, native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too. Tested kernel version: native 17.04 kernel 4.10.15 Issues are the same, we're getting random freeze on the machine. Here is kern.log entry when happening : May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=913449 May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 jiffies, g=10001, c=1, q=4656) May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0: May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0 R running task 0 0 0 0x0008 May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace: May 10 22:41:56 dev2 kernel: [24366.190354] ? native_safe_halt+0x6/0x10 May 10 22:41:56 dev2 kernel: [24366.190355] ? default_idle+0x20/0xd0 May 10 22:41:56 dev2 kernel: [24366.190358] ? arch_cpu_idle+0xf/0x20 May 10 22:41:56 dev2 kernel: [24366.190360] ? default_idle_call+0x23/0x30 May 10 22:41:56 dev2 kernel: [24366.190362] ? do_idle+0x16f/0x200 May 10 22:41:56 dev2 kernel: [24366.190364] ? cpu_startup_entry+0x71/0x80 May 10 22:41:56 dev2 kernel: [24366.190366] ? rest_init+0x77/0x80 May 10 22:41:56 dev2 kernel: [24366.190368] ? start_kernel+0x464/0x485 May 10 22:41:56 dev2 kernel: [24366.190369] ? early_idt_handler_array+0x120/0x120 May 10 22:41:56 dev2 kernel: [24366.190371] ? x86_64_start_reservations+0x24/0x26 May 10 22:41:56 dev2 kernel: [24366.190372] ? x86_64_start_kernel+0x14d/0x170 May 10 22:41:56 dev2 kernel: [24366.190373] ? start_cpu+0x14/0x14 May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=935027 May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 jiffies, g=10001, c=1, q=4740) May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0: May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0 R running task 0 0 0 0x0008 May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace: May 10 22:44:56 dev2 kernel: [24546.192199] ? native_safe_halt+0x6/0x10 May 10 22:44:56 dev2 kernel: [24546.192201] ? default_idle+0x20/0xd0 May 10 22:44:56 dev2 kernel: [24546.192203] ? arch_cpu_idle+0xf/0x20 May 10 22:44:56 dev2 kernel: [24546.192204] ? default_idle_call+0x23/0x30 May 10 22:44:56 dev2 kernel: [24546.192206] ? do_idle+0x16f/0x200 May 10 22:44:56 dev2 kernel: [24546.192208] ? cpu_startup_entry+0x71/0x80 May 10 22:44:56 dev2 kernel: [24546.192210] ? rest_init+0x77/0x80 May 10 22:44:56 dev2 kernel: [24546.192211] ? start_kernel+0x464/0x485 May 10 22:44:56 dev2 kernel: [24546.192213] ? early_idt_handler_array+0x120/0x120 May 10 22:44:56 dev2 kernel: [24546.192214] ? x86_64_start_reservations+0x24/0x26 May 10 22:44:56 dev2 kernel: [24546.192215] ? x86_64_start_kernel+0x14d/0x170 May 10 22:44:56 dev2 kernel: [24546.192217] ? start_cpu+0x14/0x14 Depending on the kernel version, we've got NMI watchdog errors related to CPU stuck (mentioning the CPU core id, which is random). Crash is happening randomly, but in general after some hours (3-4h). Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning and waiting for crash... For now, the machine is not "used", at least, it's not CPU stressed... Thanks --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-05-09 (1 days ago) InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 (20170412) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Tags: zesty Uname: Linux 4.11.0-041100-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to:
[Kernel-packages] [Bug 1690085]
Have you tried the suggested fixes in this thread? And what changed between that reinstall and earlier? On 7/24/20 4:17 AM, bugzilla-dae...@bugzilla.kernel.org wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=196683 > > Victor Queiroz (victorcqueir...@gmail.com) changed: > > What|Removed |Added > > CC||victorcqueir...@gmail.com > > --- Comment #703 from Victor Queiroz (victorcqueir...@gmail.com) --- > I'm also experiencing severe and constant crashes with a Ryzen 5 3600X. I > also > had problems with my Ryzen 7 1700 and I was confident that the problem was > never going to have problems again with my Ryzen 5 3600X, but I was wrong. > > First months everything was fine, and after reinstalling the system, > everything > went wrong. Crashes daily and constantly. I had a critical Git repository > corrupted (luckily I could recover things in time), but it completely > destroyed > my experience with my PC and actually become a financial gap as I use the > computer to work on. > > Not sure what to do. I've decided to try until the end of this year not to > have > more crashes, but as a Linux user, I'm unsure I will ever think about buying > AMD again. I will always remember about the hassle and lost years I had with > this. > > Sometimes all you want to do is to have a great experience with your Linux > computer and BOOM, a hard freeze that requires manually turning the computer > off. It's ridiculous. To be honest, I expected much more from AMD. I hope > they'll fix it ASAP, we can't stand this anymore. Intel becomes our only > option > with this problem. > > I also opened an issue where I'm posting updates about my problems: > https://bugzilla.kernel.org/show_bug.cgi?id=208615 > -- 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/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks Status in Linux: Expired Status in linux package in Ubuntu: Confirmed Bug description: Hi, We aregetting various kernel crash on a pretty new config. We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using latest BIOS available (1.52) We are running Ubuntu 17.04 (amd64), we've tried different kernel version, native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too. Tested kernel version: native 17.04 kernel 4.10.15 Issues are the same, we're getting random freeze on the machine. Here is kern.log entry when happening : May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=913449 May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 jiffies, g=10001, c=1, q=4656) May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0: May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0 R running task 0 0 0 0x0008 May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace: May 10 22:41:56 dev2 kernel: [24366.190354] ? native_safe_halt+0x6/0x10 May 10 22:41:56 dev2 kernel: [24366.190355] ? default_idle+0x20/0xd0 May 10 22:41:56 dev2 kernel: [24366.190358] ? arch_cpu_idle+0xf/0x20 May 10 22:41:56 dev2 kernel: [24366.190360] ? default_idle_call+0x23/0x30 May 10 22:41:56 dev2 kernel: [24366.190362] ? do_idle+0x16f/0x200 May 10 22:41:56 dev2 kernel: [24366.190364] ? cpu_startup_entry+0x71/0x80 May 10 22:41:56 dev2 kernel: [24366.190366] ? rest_init+0x77/0x80 May 10 22:41:56 dev2 kernel: [24366.190368] ? start_kernel+0x464/0x485 May 10 22:41:56 dev2 kernel: [24366.190369] ? early_idt_handler_array+0x120/0x120 May 10 22:41:56 dev2 kernel: [24366.190371] ? x86_64_start_reservations+0x24/0x26 May 10 22:41:56 dev2 kernel: [24366.190372] ? x86_64_start_kernel+0x14d/0x170 May 10 22:41:56 dev2 kernel: [24366.190373] ? start_cpu+0x14/0x14 May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=935027 May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 jiffies, g=10001, c=1, q=4740) May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0: May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0 R running task 0 0 0 0x0008 May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace: May 10 22:44:56 dev2 kernel: [24546.192199] ? native_safe_halt+0x6/0x10 May 10 22:44:56 dev2 kernel: [24546.192201] ? default_idle+0x20/0xd0 May 10 22:44:56 dev2 kernel: [24546.192203] ? arch_cpu_idle+0xf/0x20 May 10 22:44:56 dev2 kernel: [24546.192204]
[Kernel-packages] [Bug 1690085]
I'm also experiencing severe and constant crashes with a Ryzen 5 3600X. I also had problems with my Ryzen 7 1700 and I was confident that the problem was never going to have problems again with my Ryzen 5 3600X, but I was wrong. First months everything was fine, and after reinstalling the system, everything went wrong. Crashes daily and constantly. I had a critical Git repository corrupted (luckily I could recover things in time), but it completely destroyed my experience with my PC and actually become a financial gap as I use the computer to work on. Not sure what to do. I've decided to try until the end of this year not to have more crashes, but as a Linux user, I'm unsure I will ever think about buying AMD again. I will always remember about the hassle and lost years I had with this. Sometimes all you want to do is to have a great experience with your Linux computer and BOOM, a hard freeze that requires manually turning the computer off. It's ridiculous. To be honest, I expected much more from AMD. I hope they'll fix it ASAP, we can't stand this anymore. Intel becomes our only option with this problem. I also opened an issue where I'm posting updates about my problems: https://bugzilla.kernel.org/show_bug.cgi?id=208615 -- 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/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks Status in Linux: Expired Status in linux package in Ubuntu: Confirmed Bug description: Hi, We aregetting various kernel crash on a pretty new config. We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using latest BIOS available (1.52) We are running Ubuntu 17.04 (amd64), we've tried different kernel version, native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too. Tested kernel version: native 17.04 kernel 4.10.15 Issues are the same, we're getting random freeze on the machine. Here is kern.log entry when happening : May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=913449 May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 jiffies, g=10001, c=1, q=4656) May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0: May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0 R running task 0 0 0 0x0008 May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace: May 10 22:41:56 dev2 kernel: [24366.190354] ? native_safe_halt+0x6/0x10 May 10 22:41:56 dev2 kernel: [24366.190355] ? default_idle+0x20/0xd0 May 10 22:41:56 dev2 kernel: [24366.190358] ? arch_cpu_idle+0xf/0x20 May 10 22:41:56 dev2 kernel: [24366.190360] ? default_idle_call+0x23/0x30 May 10 22:41:56 dev2 kernel: [24366.190362] ? do_idle+0x16f/0x200 May 10 22:41:56 dev2 kernel: [24366.190364] ? cpu_startup_entry+0x71/0x80 May 10 22:41:56 dev2 kernel: [24366.190366] ? rest_init+0x77/0x80 May 10 22:41:56 dev2 kernel: [24366.190368] ? start_kernel+0x464/0x485 May 10 22:41:56 dev2 kernel: [24366.190369] ? early_idt_handler_array+0x120/0x120 May 10 22:41:56 dev2 kernel: [24366.190371] ? x86_64_start_reservations+0x24/0x26 May 10 22:41:56 dev2 kernel: [24366.190372] ? x86_64_start_kernel+0x14d/0x170 May 10 22:41:56 dev2 kernel: [24366.190373] ? start_cpu+0x14/0x14 May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=935027 May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 jiffies, g=10001, c=1, q=4740) May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0: May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0 R running task 0 0 0 0x0008 May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace: May 10 22:44:56 dev2 kernel: [24546.192199] ? native_safe_halt+0x6/0x10 May 10 22:44:56 dev2 kernel: [24546.192201] ? default_idle+0x20/0xd0 May 10 22:44:56 dev2 kernel: [24546.192203] ? arch_cpu_idle+0xf/0x20 May 10 22:44:56 dev2 kernel: [24546.192204] ? default_idle_call+0x23/0x30 May 10 22:44:56 dev2 kernel: [24546.192206] ? do_idle+0x16f/0x200 May 10 22:44:56 dev2 kernel: [24546.192208] ? cpu_startup_entry+0x71/0x80 May 10 22:44:56 dev2 kernel: [24546.192210] ? rest_init+0x77/0x80 May 10 22:44:56 dev2 kernel: [24546.192211] ? start_kernel+0x464/0x485 May 10 22:44:56 dev2 kernel: [24546.192213] ? early_idt_handler_array+0x120/0x120 May 10 22:44:56 dev2 kernel: [24546.192214] ? x86_64_start_reservations+0x24/0x26 May 10 22:44:56 dev2 kernel: [24546.192215] ? x86_64_start_kernel+0x14d/0x170 May 10 22:44:56 dev2 kernel: [24546.192217] ?
[Kernel-packages] [Bug 1888570] Re: poweroff not working after apt upgrade
Correction to #19. The kernel is available @ https://people.canonical.com/~alexhung/LP1888570/19357b3b0835/ -- 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/1888570 Title: poweroff not working after apt upgrade Status in linux package in Ubuntu: Confirmed Bug description: System-Information: Description: Ubuntu 18.04.4 LTS Release: 18.04 ## Working packages: - Kernel 5.3.0.61.114 - linux-firmware 1.173.18 Problem occurs when upgrading (anyone of) these packages - Kernel 5.3.0-62.56 - linux-firmware 1.173.19 I use an Acer Aspire E5-771G Notebook with a fresh installation of Ubuntu 18.04. Till the last upgrade everything works as expected. The last upgrade brings two new kernel versions (as mentioned above). Now the system stucks at the very end of the power down sequence. Even SysReq-O will not work (only SysReq-B will work). Because I use Systemback, I time shift to the previous system and then install package by package to see what will bring in the problem. If I install any of the mentioned kernel updates the problem will show up. I had ask the above question on "askubuntu.com". I was directed to upgrade the BIOS, But even after doing so the problem still persist. I am not sure if I do it right (APT pinning). I currently create a file /etc/apt/prefereces.d/kernel. I add an entry for every of the following packages to block the version mentioned above (Pin: version: Pin-Priority: -1): linux-generic-hwe-18.04 linux-headers-generic-hwe-18.04 linux-image-generic-hwe-18.04 linux-modules-nvidia-440-generic-hwe-18.04 linux-firmware After doing so "apt list --upgradeable" will not list the packages in question and the PC will power down normally (and SysReq-O WILL work). In the meanwhile there are newer versions of the kernel online, so the above mentioned pinning will allow the newer kernels to get installed and the problem will show up again. So I block these versions too. BTW: Due to the stuck I am able to see some other error messages that are not reported in the journal. The very last 3-5 lines show: shutdown [1]: Failed to wait for process: Protocol error These lines are present although in the working kernels, but hard to see, because the system powers down some ms after these lines are displayed! This problem seams to be solved more than one year ago in the upstream kernel! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gneiss 1929 F pulseaudio /dev/snd/controlC0: gneiss 1929 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-05-02 (448 days ago) InstallationMedia: MachineType: Acer Aspire E5-771G NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANG=de_DE.UTF-8 SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-61-generic root=UUID=0b245afe-758b-4e45-a473-ad2077260d8f ro noplymouth resume=UUID=79a9e809-6ba1-491b-acfc-1816057c2dee ProcVersionSignature: Ubuntu 5.3.0-61.55~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-61-generic N/A linux-backports-modules-5.3.0-61-generic N/A linux-firmware1.173.18 Tags: bionic Uname: Linux 5.3.0-61-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 09/02/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.23 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA70_HB dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.23:bd09/02/2015:svnAcer:pnAspireE5-771G:pvrV3.72:rvnAcer:rnEA70_HB:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: BDW dmi.product.name: Aspire E5-771G dmi.product.sku: Aspire E5-771G_0884_1_23 dmi.product.version: V3.72 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888570/+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 1888570] Re: poweroff not working after apt upgrade
Thanks for reporting this, and your help is needed to identify the patch that causes this regression. There are 260 patches between 5.3.0-61 & 5.3.0-62, and it requires some testing with bisects (see below). $ git bisect start $ git bisect good Ubuntu-5.3.0-61.55 $ git bisect bad Ubuntu-5.3.0-62.56 Bisecting: 260 revisions left to test after this (roughly 8 steps) [19357b3b0835b96039e907f65ae203f7adc48ef6] epoll: atomically remove wait entry on wake up A test kernel is available @ https://people.canonical.com/~alexhung/LP1888570/. Let me know whether it is pass or fail so I can build a next version. -- 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/1888570 Title: poweroff not working after apt upgrade Status in linux package in Ubuntu: Confirmed Bug description: System-Information: Description: Ubuntu 18.04.4 LTS Release: 18.04 ## Working packages: - Kernel 5.3.0.61.114 - linux-firmware 1.173.18 Problem occurs when upgrading (anyone of) these packages - Kernel 5.3.0-62.56 - linux-firmware 1.173.19 I use an Acer Aspire E5-771G Notebook with a fresh installation of Ubuntu 18.04. Till the last upgrade everything works as expected. The last upgrade brings two new kernel versions (as mentioned above). Now the system stucks at the very end of the power down sequence. Even SysReq-O will not work (only SysReq-B will work). Because I use Systemback, I time shift to the previous system and then install package by package to see what will bring in the problem. If I install any of the mentioned kernel updates the problem will show up. I had ask the above question on "askubuntu.com". I was directed to upgrade the BIOS, But even after doing so the problem still persist. I am not sure if I do it right (APT pinning). I currently create a file /etc/apt/prefereces.d/kernel. I add an entry for every of the following packages to block the version mentioned above (Pin: version: Pin-Priority: -1): linux-generic-hwe-18.04 linux-headers-generic-hwe-18.04 linux-image-generic-hwe-18.04 linux-modules-nvidia-440-generic-hwe-18.04 linux-firmware After doing so "apt list --upgradeable" will not list the packages in question and the PC will power down normally (and SysReq-O WILL work). In the meanwhile there are newer versions of the kernel online, so the above mentioned pinning will allow the newer kernels to get installed and the problem will show up again. So I block these versions too. BTW: Due to the stuck I am able to see some other error messages that are not reported in the journal. The very last 3-5 lines show: shutdown [1]: Failed to wait for process: Protocol error These lines are present although in the working kernels, but hard to see, because the system powers down some ms after these lines are displayed! This problem seams to be solved more than one year ago in the upstream kernel! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gneiss 1929 F pulseaudio /dev/snd/controlC0: gneiss 1929 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-05-02 (448 days ago) InstallationMedia: MachineType: Acer Aspire E5-771G NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANG=de_DE.UTF-8 SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-61-generic root=UUID=0b245afe-758b-4e45-a473-ad2077260d8f ro noplymouth resume=UUID=79a9e809-6ba1-491b-acfc-1816057c2dee ProcVersionSignature: Ubuntu 5.3.0-61.55~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-61-generic N/A linux-backports-modules-5.3.0-61-generic N/A linux-firmware1.173.18 Tags: bionic Uname: Linux 5.3.0-61-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 09/02/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.23 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA70_HB dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.23:bd09/02/2015:svnAcer:pnAspireE5-771G:pvrV3.72:rvnAcer:rnEA70_HB:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: BDW dmi.product.name: Aspire E5-771G dmi.product.sku: Aspire E5-771G_0884_1_23
[Kernel-packages] [Bug 1888907] Re: Bionic update: upstream stable patchset 2020-07-24
** Description changed:
+ SRU Justification
- SRU Justification
+ Impact:
+ The upstream process for stable tree updates is quite similar
+ in scope to the Ubuntu SRU process, e.g., each patch has to
+ demonstrably fix a bug, and each patch is vetted by upstream
+ by originating either directly from a mainline/stable Linux tree or
+ a minimally backported form of that patch. The following upstream
+ stable patches should be included in the Ubuntu kernel:
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The following upstream
-stable patches should be included in the Ubuntu kernel:
+ upstream stable patchset 2020-07-24
-upstream stable patchset 2020-07-24
-from git://git.kernel.org/
+ Ported from the following upstream stable releases:
+ v4.14.189, v4.19.133
+v4.19.134
+
+ from git://git.kernel.org/
+
+ KVM: s390: reduce number of IO pins to 1
+ spi: spi-fsl-dspi: Adding shutdown hook
+ spi: spi-fsl-dspi: Fix lockup if device is removed during SPI transfer
+ spi: spi-fsl-dspi: use IRQF_SHARED mode to request IRQ
+ spi: spi-fsl-dspi: Fix external abort on interrupt in resume or exit paths
+ ARM: dts: omap4-droid4: Fix spi configuration and increase rate
+ gpu: host1x: Detach driver on unregister
+ spi: spidev: fix a race between spidev_release and spidev_remove
+ spi: spidev: fix a potential use-after-free in spidev_release()
+ ixgbe: protect ring accesses with READ- and WRITE_ONCE
+ s390/kasan: fix early pgm check handler execution
+ cifs: update ctime and mtime during truncate
+ ARM: imx6: add missing put_device() call in imx6q_suspend_init()
+ scsi: mptscsih: Fix read sense data size
+ nvme-rdma: assign completion vector correctly
+ x86/entry: Increase entry_stack size to a full page
+ net: cxgb4: fix return error value in t4_prep_fw
+ smsc95xx: check return value of smsc95xx_reset
+ smsc95xx: avoid memory leak in smsc95xx_bind
+ ALSA: compress: fix partial_drain completion state
+ arm64: kgdb: Fix single-step exception handling oops
+ nbd: Fix memory leak in nbd_add_socket
+ bnxt_en: fix NULL dereference in case SR-IOV configuration fails
+ net: macb: mark device wake capable when "magic-packet" property present
+ mlxsw: spectrum_router: Remove inappropriate usage of WARN_ON()
+ ALSA: opl3: fix infoleak in opl3
+ ALSA: hda - let hs_mic be picked ahead of hp_mic
+ ALSA: usb-audio: add quirk for MacroSilicon MS2109
+ KVM: arm64: Fix definition of PAGE_HYP_DEVICE
+ KVM: arm64: Stop clobbering x0 for HVC_SOFT_RESTART
+ KVM: x86: bit 8 of non-leaf PDPEs is not reserved
+ KVM: x86: Inject #GP if guest attempts to toggle CR4.LA57 in 64-bit mode
+ KVM: x86: Mark CR4.TSD as being possibly owned by the guest
+ Revert "ath9k: Fix general protection fault in ath9k_hif_usb_rx_cb"
+ btrfs: fix fatal extent_buffer readahead vs releasepage race
+ drm/radeon: fix double free
+ dm: use noio when sending kobject event
+ ARC: entry: fix potential EFA clobber when TIF_SYSCALL_TRACE
+ ARC: elf: use right ELF_ARCH
+ s390/mm: fix huge pte soft dirty copying
+ genetlink: remove genl_bind
+ ipv4: fill fl4_icmp_{type,code} in ping_v4_sendmsg
+ l2tp: remove skb_dst_set() from l2tp_xmit_skb()
+ llc: make sure applications use ARPHRD_ETHER
+ net: Added pointer check for dst->ops->neigh_lookup in dst_neigh_lookup_skb
+ tcp: md5: add missing memory barriers in tcp_md5_do_add()/tcp_md5_hash_key()
+ tcp: md5: refine tcp_md5_do_add()/tcp_md5_hash_key() barriers
+ tcp: md5: allow changing MD5 keys in all socket states
+ net_sched: fix a memory leak in atm_tc_init()
+ tcp: make sure listeners don't initialize congestion-control state
+ tcp: md5: do not send silly options in SYNCOOKIES
+ cgroup: fix cgroup_sk_alloc() for sk_clone_lock()
+ cgroup: Fix sock_cgroup_data on big-endian.
+ drm/exynos: fix ref count leak in mic_pre_enable
+ arm64/alternatives: use subsections for replacement sequences
+ tpm_tis: extra chip->ops check on error path in tpm_tis_core_init
+ gfs2: read-only mounts should grab the sd_freeze_gl glock
+ i2c: eg20t: Load module automatically if ID matches
+ arm64: alternative: Use true and false for boolean values
+ arm64/alternatives: don't patch up internal branches
+ iio:magnetometer:ak8974: Fix alignment and data leak issues
+ iio:humidity:hdc100x Fix alignment and data leak issues
+ iio: magnetometer: ak8974: Fix runtime PM imbalance on error
+ iio: mma8452: Add missed iio_device_unregister() call in mma8452_probe()
+ iio: pressure: zpa2326: handle pm_runtime_get_sync failure
+ iio:pressure:ms5611 Fix buffer element alignment
+ iio:health:afe4403
[Kernel-packages] [Bug 1888907] [NEW] Bionic update: upstream stable patchset 2020-07-24
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
upstream stable patchset 2020-07-24
Ported from the following upstream stable releases:
v4.14.189, v4.19.133
v4.19.134
from git://git.kernel.org/
KVM: s390: reduce number of IO pins to 1
spi: spi-fsl-dspi: Adding shutdown hook
spi: spi-fsl-dspi: Fix lockup if device is removed during SPI transfer
spi: spi-fsl-dspi: use IRQF_SHARED mode to request IRQ
spi: spi-fsl-dspi: Fix external abort on interrupt in resume or exit paths
ARM: dts: omap4-droid4: Fix spi configuration and increase rate
gpu: host1x: Detach driver on unregister
spi: spidev: fix a race between spidev_release and spidev_remove
spi: spidev: fix a potential use-after-free in spidev_release()
ixgbe: protect ring accesses with READ- and WRITE_ONCE
s390/kasan: fix early pgm check handler execution
cifs: update ctime and mtime during truncate
ARM: imx6: add missing put_device() call in imx6q_suspend_init()
scsi: mptscsih: Fix read sense data size
nvme-rdma: assign completion vector correctly
x86/entry: Increase entry_stack size to a full page
net: cxgb4: fix return error value in t4_prep_fw
smsc95xx: check return value of smsc95xx_reset
smsc95xx: avoid memory leak in smsc95xx_bind
ALSA: compress: fix partial_drain completion state
arm64: kgdb: Fix single-step exception handling oops
nbd: Fix memory leak in nbd_add_socket
bnxt_en: fix NULL dereference in case SR-IOV configuration fails
net: macb: mark device wake capable when "magic-packet" property present
mlxsw: spectrum_router: Remove inappropriate usage of WARN_ON()
ALSA: opl3: fix infoleak in opl3
ALSA: hda - let hs_mic be picked ahead of hp_mic
ALSA: usb-audio: add quirk for MacroSilicon MS2109
KVM: arm64: Fix definition of PAGE_HYP_DEVICE
KVM: arm64: Stop clobbering x0 for HVC_SOFT_RESTART
KVM: x86: bit 8 of non-leaf PDPEs is not reserved
KVM: x86: Inject #GP if guest attempts to toggle CR4.LA57 in 64-bit mode
KVM: x86: Mark CR4.TSD as being possibly owned by the guest
Revert "ath9k: Fix general protection fault in ath9k_hif_usb_rx_cb"
btrfs: fix fatal extent_buffer readahead vs releasepage race
drm/radeon: fix double free
dm: use noio when sending kobject event
ARC: entry: fix potential EFA clobber when TIF_SYSCALL_TRACE
ARC: elf: use right ELF_ARCH
s390/mm: fix huge pte soft dirty copying
genetlink: remove genl_bind
ipv4: fill fl4_icmp_{type,code} in ping_v4_sendmsg
l2tp: remove skb_dst_set() from l2tp_xmit_skb()
llc: make sure applications use ARPHRD_ETHER
net: Added pointer check for dst->ops->neigh_lookup in dst_neigh_lookup_skb
tcp: md5: add missing memory barriers in tcp_md5_do_add()/tcp_md5_hash_key()
tcp: md5: refine tcp_md5_do_add()/tcp_md5_hash_key() barriers
tcp: md5: allow changing MD5 keys in all socket states
net_sched: fix a memory leak in atm_tc_init()
tcp: make sure listeners don't initialize congestion-control state
tcp: md5: do not send silly options in SYNCOOKIES
cgroup: fix cgroup_sk_alloc() for sk_clone_lock()
cgroup: Fix sock_cgroup_data on big-endian.
drm/exynos: fix ref count leak in mic_pre_enable
arm64/alternatives: use subsections for replacement sequences
tpm_tis: extra chip->ops check on error path in tpm_tis_core_init
gfs2: read-only mounts should grab the sd_freeze_gl glock
i2c: eg20t: Load module automatically if ID matches
arm64: alternative: Use true and false for boolean values
arm64/alternatives: don't patch up internal branches
iio:magnetometer:ak8974: Fix alignment and data leak issues
iio:humidity:hdc100x Fix alignment and data leak issues
iio: magnetometer: ak8974: Fix runtime PM imbalance on error
iio: mma8452: Add missed iio_device_unregister() call in mma8452_probe()
iio: pressure: zpa2326: handle pm_runtime_get_sync failure
iio:pressure:ms5611 Fix buffer element alignment
iio:health:afe4403 Fix timestamp alignment and prevent data leak.
spi: spi-fsl-dspi: Fix lockup if device is shutdown during SPI transfer
spi: fix initial SPI_SR value in spi-fsl-dspi
net: dsa: bcm_sf2: Fix node reference count
of: of_mdio: Correct loop scanning logic
Revert "usb/ohci-platform: Fix a warning when hibernating"
Revert "usb/ehci-platform: Set PM runtime as active on resume"
Revert "usb/xhci-plat: Set PM runtime as active on resume"
doc: dt: bindings: usb: dwc3: Update entries for disabling SS instances in park
mode
mmc: sdhci: do not enable card detect interrupt for gpio cd type
ACPI: video: Use native backlight on Acer Aspire 5783z
ACPI: video: Use native backlight on Acer TravelMate 5735Z
iio:health:afe4404 Fix
[Kernel-packages] [Bug 1774959] Re: clock test in monotonic_time will fail on Azure Instances
monotonic-time is no longer tested in the SRU cycles ** Changed in: ubuntu-kernel-tests Status: Confirmed => Invalid ** Changed in: linux-azure (Ubuntu) Status: Confirmed => Invalid -- 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/1774959 Title: clock test in monotonic_time will fail on Azure Instances Status in ubuntu-kernel-tests: Invalid Status in linux-azure package in Ubuntu: Invalid Bug description: Among all of the Azure node, this test only failed on these two nodes: Seen on the following instances: Basic_A2 Standard_D2_v3 Standard_D2s_v3 Standard_E4s_v3 Standard_E64-16s Standard_F2s_v2 Steps to reproduce: 1. git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests 2. make -C autotest-client-tests/monotonic_time/src 3. sudo autotest-client-tests/monotonic_time/src/time_test --duration 300 tsc Results: $ sudo autotest-client-tests/monotonic_time/src/time_test --duration 300 tsc Running 'make ' cc -O -std=gnu99 -Wall -c -o time_test.o time_test.c cc -O -std=gnu99 -Wall -c -o cpuset.o cpuset.c cc -O -std=gnu99 -Wall -c -o threads.o threads.c cc -O -std=gnu99 -Wall -c -o logging.o logging.c cc -o time_test time_test.o cpuset.o threads.o logging.o -lpthread -lrt Running '/home/azure/autotest/client/tmp/monotonic_time/src/time_test --duration 300 clock' Time test command exit status: 1 Exception escaping from test: Traceback (most recent call last): File "/home/azure/autotest/client/shared/test.py", line 411, in _exec_call_test_function(self.execute, *p_args, **p_dargs) File "/home/azure/autotest/client/shared/test.py", line 823, in _call_test_function return func(*args, **dargs) File "/home/azure/autotest/client/shared/test.py", line 291, in execute postprocess_profiled_run, args, dargs) File "/home/azure/autotest/client/shared/test.py", line 212, in _call_run_once self.run_once(*args, **dargs) File "/home/azure/autotest/client/tests/monotonic_time/monotonic_time.py", line 53, in run_once raise error.TestFail(line) TestFail: FAIL: clock-worst-warp=-100 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1774959/+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 1781902] Re: memory hotplug test stuck on Azure BasicA1 node with X-HWE azure kernel
We no longer test with the A1 Instances due to problems like this, A1 is an extremely minimal, low resource instance. We should not be offlining cpu and memory in these VMs. ** Changed in: ubuntu-kernel-tests Status: New => Invalid ** Changed in: linux-signed-azure (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-azure in Ubuntu. https://bugs.launchpad.net/bugs/1781902 Title: memory hotplug test stuck on Azure BasicA1 node with X-HWE azure kernel Status in ubuntu-kernel-tests: Invalid Status in linux-signed-azure package in Ubuntu: Invalid Bug description: The memory hotplug test stuck on Azure Basic A1 node, with kernel 4.15.0-1017-azure #17~16.04.1-Ubuntu Running 'sudo make -C linux/tools/testing/selftests/memory-hotplug all run_tests' make: Entering directory '/home/azure/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/memory-hotplug' make: Nothing to be done for 'all'. ./mem-on-off-test.sh -r 2 || echo "selftests: memory-hotplug [FAIL]" Test scope: 2% hotplug memory online all hot-pluggable memory in offline state: SKIPPED - no hot-pluggable memory in offline state offline 2% hot-pluggable memory in online state trying to offline 1 out of 1 memory block(s): online->offline memory39 Some traces could be found in dmesg: [ 605.156847] INFO: task kworker/0:0:3 blocked for more than 120 seconds. [ 605.165522] Not tainted 4.15.0-1017-azure #17~16.04.1-Ubuntu [ 605.171822] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 605.182439] kworker/0:0 D0 3 2 0x8000 [ 605.182450] Workqueue: cgroup_destroy css_free_work_fn [ 605.182452] Call Trace: [ 605.182460] __schedule+0x3d6/0x8b0 [ 605.182464] ? enqueue_entity+0x112/0x670 [ 605.182467] schedule+0x36/0x80 [ 605.182470] rwsem_down_read_failed+0x10a/0x170 [ 605.182473] call_rwsem_down_read_failed+0x18/0x30 [ 605.182474] ? call_rwsem_down_read_failed+0x18/0x30 [ 605.182477] __percpu_down_read+0x54/0x80 [ 605.182481] get_online_mems+0x32/0x40 [ 605.182485] memcg_destroy_kmem_caches+0x14/0x90 [ 605.182488] mem_cgroup_css_free+0x144/0x180 [ 605.182491] css_free_work_fn+0x4c/0x370 [ 605.182494] process_one_work+0x14d/0x410 [ 605.182495] worker_thread+0x4b/0x460 [ 605.182499] kthread+0x105/0x140 [ 605.182500] ? process_one_work+0x410/0x410 [ 605.182503] ? kthread_associate_blkcg+0xa0/0xa0 [ 605.182504] ret_from_fork+0x35/0x40 [ 725.984133] INFO: task kworker/0:0:3 blocked for more than 120 seconds. [ 725.996091] Not tainted 4.15.0-1017-azure #17~16.04.1-Ubuntu [ 726.012768] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 726.030221] kworker/0:0 D0 3 2 0x8000 [ 726.030232] Workqueue: cgroup_destroy css_free_work_fn [ 726.030234] Call Trace: [ 726.030242] __schedule+0x3d6/0x8b0 [ 726.030246] ? enqueue_entity+0x112/0x670 [ 726.030249] schedule+0x36/0x80 [ 726.030252] rwsem_down_read_failed+0x10a/0x170 [ 726.030255] call_rwsem_down_read_failed+0x18/0x30 [ 726.030256] ? call_rwsem_down_read_failed+0x18/0x30 [ 726.030259] __percpu_down_read+0x54/0x80 [ 726.030264] get_online_mems+0x32/0x40 [ 726.030268] memcg_destroy_kmem_caches+0x14/0x90 [ 726.030271] mem_cgroup_css_free+0x144/0x180 [ 726.030273] css_free_work_fn+0x4c/0x370 [ 726.030276] process_one_work+0x14d/0x410 [ 726.030278] worker_thread+0x4b/0x460 [ 726.030281] kthread+0x105/0x140 [ 726.030283] ? process_one_work+0x410/0x410 [ 726.030285] ? kthread_associate_blkcg+0xa0/0xa0 [ 726.030287] ret_from_fork+0x35/0x40 [ 846.820680] INFO: task kworker/0:0:3 blocked for more than 120 seconds. [ 846.831583] Not tainted 4.15.0-1017-azure #17~16.04.1-Ubuntu [ 846.842013] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 846.851811] kworker/0:0 D0 3 2 0x8000 [ 846.851822] Workqueue: cgroup_destroy css_free_work_fn [ 846.851823] Call Trace: [ 846.851831] __schedule+0x3d6/0x8b0 [ 846.851835] ? enqueue_entity+0x112/0x670 [ 846.851838] schedule+0x36/0x80 [ 846.851841] rwsem_down_read_failed+0x10a/0x170 [ 846.851844] call_rwsem_down_read_failed+0x18/0x30 [ 846.851845] ? call_rwsem_down_read_failed+0x18/0x30 [ 846.851848] __percpu_down_read+0x54/0x80 [ 846.851852] get_online_mems+0x32/0x40 [ 846.851856] memcg_destroy_kmem_caches+0x14/0x90 [ 846.851859] mem_cgroup_css_free+0x144/0x180 [ 846.851862] css_free_work_fn+0x4c/0x370 [ 846.851865] process_one_work+0x14d/0x410 [ 846.851867] worker_thread+0x4b/0x460 [ 846.851870] kthread+0x105/0x140 [ 846.851872] ? process_one_work+0x410/0x410 [ 846.851874]
[Kernel-packages] [Bug 1765653] Re: directory-concurrent.sh.ext4 in ubuntu_ecryptfs failed on Atrful and Bionic ThunderX ARM64
As the ecryptfs support has been dropped in Bionic+(https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1798359) marking bug invalid ** Changed in: ecryptfs Status: Triaged => Invalid ** Changed in: ubuntu-kernel-tests 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/1765653 Title: directory-concurrent.sh.ext4 in ubuntu_ecryptfs failed on Atrful and Bionic ThunderX ARM64 Status in eCryptfs: Invalid Status in ubuntu-kernel-tests: Invalid Status in linux package in Ubuntu: Invalid Status in linux source package in Artful: Won't Fix Status in linux source package in Bionic: Invalid Bug description: This directory-concurrent.sh.ext4 test will fail with 4.13 and 4.15 kernel on a ThunderX ARM64 node (passed on the other Moonshot node): Steps: 1. git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests -b master-next 2. git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest 3. rm -fr autotest/client/tests 4. ln -sf ~/autotest-client-tests autotest/client/tests 5. AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local --verbose autotest/client/tests/ubuntu_ecryptfs/control Output: Running 'tests/run_one.sh -K -t directory-concurrent.sh -b 100 -D /mnt/image -l /mnt/lower -u /mnt/upper -f ext4' Timed out after 30 seconds doing mkdir() - possible eCryptfs hang Timed out after 30 seconds doing mkdir() - possible eCryptfs hang Timed out after 30 seconds doing mkdir() - possible eCryptfs hang Timed out after 30 seconds doing mkdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing mkdir() - possible eCryptfs hang Timed out after 30 seconds doing mkdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing mkdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing mkdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing mkdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing mkdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing mkdir() - possible eCryptfs hang Timed out after 30 seconds doing mkdir() - possible eCryptfs hang Timed out after 30 seconds doing mkdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing mkdir() - possible eCryptfs hang Timed out after 30 seconds doing mkdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing mkdir() - possible eCryptfs hang Timed out after 30 seconds doing mkdir() - possible eCryptfs hang Timed out after 30 seconds doing mkdir() - possible eCryptfs hang Timed out after 30 seconds doing mkdir() - possible eCryptfs hang Timed out after 30 seconds
[Kernel-packages] [Bug 1684788] Re: extend-file-random.sh.btrfs from ubuntu_ecryptfs test-suite failed on X-hwe
Xenial 4.4.0-187.217 1. 07/22 20:20:47 DEBUG| utils:0116| Running 'tests/run_one.sh -K -t extend-file-random.sh -b 100 -D /mnt/image -l /mnt/lower -u /mnt/upper -f btrfs' 2. 07/22 20:21:13 DEBUG| utils:0153| [stdout] extend-file-random pass 3. 07/22 20:21:13 DEBUG| utils:0153| [stdout] 4. 07/22 20:21:13 DEBUG| utils:0153| [stdout] Test Summary: 5. 07/22 20:21:13 DEBUG| utils:0153| [stdout] 1 passed 6. 07/22 20:21:13 DEBUG| utils:0153| [stdout] 0 failed 7. ** Changed in: ubuntu-kernel-tests Status: Confirmed => Invalid ** Changed in: linux (Ubuntu) Status: Triaged => Invalid ** Changed in: linux (Ubuntu Xenial) Status: Triaged => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1684788 Title: extend-file-random.sh.btrfs from ubuntu_ecryptfs test-suite failed on X-hwe Status in ubuntu-kernel-tests: Invalid Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Bug description: This test has failed on both amd64, i386 and arm64 X-hwe kernel 04/15 05:13:07 DEBUG| utils:0116| Running 'apt-get install --yes --force-yes build-essential libglib2.0-dev intltool keyutils libkeyutils-dev libpam0g-dev libnss3-dev libtool acl xfsprogs btrfs-tools libattr1-dev gcc-multilib' 04/15 05:13:07 DEBUG| utils:0153| [stdout] Reading package lists... 04/15 05:13:07 DEBUG| utils:0153| [stdout] Building dependency tree... 04/15 05:13:07 DEBUG| utils:0153| [stdout] Reading state information... 04/15 05:13:08 DEBUG| utils:0153| [stdout] acl is already the newest version. 04/15 05:13:08 DEBUG| utils:0153| [stdout] build-essential is already the newest version. 04/15 05:13:08 DEBUG| utils:0153| [stdout] gcc-multilib is already the newest version. 04/15 05:13:08 DEBUG| utils:0153| [stdout] intltool is already the newest version. 04/15 05:13:08 DEBUG| utils:0153| [stdout] keyutils is already the newest version. 04/15 05:13:08 DEBUG| utils:0153| [stdout] libattr1-dev is already the newest version. 04/15 05:13:08 DEBUG| utils:0153| [stdout] libkeyutils-dev is already the newest version. 04/15 05:13:08 DEBUG| utils:0153| [stdout] libtool is already the newest version. 04/15 05:13:08 DEBUG| utils:0153| [stdout] xfsprogs is already the newest version. 04/15 05:13:08 DEBUG| utils:0153| [stdout] btrfs-tools is already the newest version. 04/15 05:13:08 DEBUG| utils:0153| [stdout] libglib2.0-dev is already the newest version. 04/15 05:13:08 DEBUG| utils:0153| [stdout] libnss3-dev is already the newest version. 04/15 05:13:08 DEBUG| utils:0153| [stdout] libpam0g-dev is already the newest version. 04/15 05:13:08 DEBUG| utils:0153| [stdout] 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 04/15 05:13:08 DEBUG| utils:0116| Running 'which gcc' 04/15 05:13:08 DEBUG| utils:0153| [stdout] /usr/bin/gcc 04/15 05:13:08 DEBUG| utils:0116| Running 'tests/run_one.sh -K -t extend-file-random.sh -b 100 -D /mnt/image -l /mnt/lower -u /mnt/upper -f btrfs' 04/15 05:13:21 ERROR| utils:0153| [stderr] size should be > 0 04/15 05:13:22 DEBUG| utils:0153| [stdout] extend-file-random FAIL 04/15 05:13:22 DEBUG| utils:0153| [stdout] 04/15 05:13:22 DEBUG| utils:0153| [stdout] Test Summary: 04/15 05:13:22 DEBUG| utils:0153| [stdout] 0 passed 04/15 05:13:22 DEBUG| utils:0153| [stdout] 1 failed 04/15 05:13:22 ERROR| test:0414| Exception escaping from test: Traceback (most recent call last): File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec _call_test_function(self.execute, *p_args, **p_dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 823, in _call_test_function return func(*args, **dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute postprocess_profiled_run, args, dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 212, in _call_run_once self.run_once(*args, **dargs) File "/home/ubuntu/autotest/client/tests/ubuntu_ecryptfs/ubuntu_ecryptfs.py", line 45, in run_once self.results = utils.system_output(cmd, retain_output=True) File "/home/ubuntu/autotest/client/shared/utils.py", line 1267, in system_output verbose=verbose, args=args).stdout File "/home/ubuntu/autotest/client/shared/utils.py", line 918, in run "Command returned non-zero exit status") CmdError: Command failed, rc=1, Command returned non-zero exit status * Command: tests/run_one.sh -K -t extend-file-random.sh -b 100 -D /mnt/image -l /mnt/lower -u /mnt/upper -f btrfs Exit status: 1 Duration: 14.147703886 stdout: extend-file-random FAIL Test Summary: 0 passed 1 failed stderr: size should be > 0 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-4.4.0-74-generic 4.4.0-74.95~14.04.1 ProcVersionSignature: User Name
[Kernel-packages] [Bug 1765653] Re: directory-concurrent.sh.ext4 in ubuntu_ecryptfs failed on Atrful and Bionic ThunderX ARM64
** Changed in: ecryptfs Assignee: Tyler Hicks (tyhicks) => (unassigned) -- 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/1765653 Title: directory-concurrent.sh.ext4 in ubuntu_ecryptfs failed on Atrful and Bionic ThunderX ARM64 Status in eCryptfs: Triaged Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Invalid Status in linux source package in Artful: Won't Fix Status in linux source package in Bionic: Invalid Bug description: This directory-concurrent.sh.ext4 test will fail with 4.13 and 4.15 kernel on a ThunderX ARM64 node (passed on the other Moonshot node): Steps: 1. git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests -b master-next 2. git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest 3. rm -fr autotest/client/tests 4. ln -sf ~/autotest-client-tests autotest/client/tests 5. AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local --verbose autotest/client/tests/ubuntu_ecryptfs/control Output: Running 'tests/run_one.sh -K -t directory-concurrent.sh -b 100 -D /mnt/image -l /mnt/lower -u /mnt/upper -f ext4' Timed out after 30 seconds doing mkdir() - possible eCryptfs hang Timed out after 30 seconds doing mkdir() - possible eCryptfs hang Timed out after 30 seconds doing mkdir() - possible eCryptfs hang Timed out after 30 seconds doing mkdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing mkdir() - possible eCryptfs hang Timed out after 30 seconds doing mkdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing mkdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing mkdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing mkdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing mkdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing mkdir() - possible eCryptfs hang Timed out after 30 seconds doing mkdir() - possible eCryptfs hang Timed out after 30 seconds doing mkdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing mkdir() - possible eCryptfs hang Timed out after 30 seconds doing mkdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing mkdir() - possible eCryptfs hang Timed out after 30 seconds doing mkdir() - possible eCryptfs hang Timed out after 30 seconds doing mkdir() - possible eCryptfs hang Timed out after 30 seconds doing mkdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang Timed out after 30 seconds doing mkdir() - possible eCryptfs hang Timed out after 30 seconds doing rmdir() - possible eCryptfs hang
[Kernel-packages] [Bug 1861610] Re: 'Elan touchpad' not detected on 'Lenovo ThinkBook 15 IIL'
This bug report got stuck with wrong "Fix Released"! @kmously and @vicamo: Please could you set the status back to "In Progress"? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1861610 Title: 'Elan touchpad' not detected on 'Lenovo ThinkBook 15 IIL' Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.6 package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Released Status in linux-oem-5.6 source package in Bionic: Invalid Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Eoan: Fix Released Status in linux-oem-5.6 source package in Eoan: Invalid Status in linux-oem-osp1 source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Status in linux-oem-5.6 source package in Focal: Fix Released Status in linux-oem-osp1 source package in Focal: Invalid Bug description: [SRU Justification] [Impact] Touchpad function unavailable on some platforms with new ELAN touchpad HIDs. [Fix] https://lore.kernel.org/linux-input/000201d5a8bd$9fead3f0$dfc07bd0$@emc.com.tw/ required to match these currently unsupported IDs. [Test Case] 1. check if platform is affected, e.g. with ELAN0634: $ sudo acpidump | grep -C3 ELAN 2A060: 49 4E 54 31 70 0A 20 49 44 41 44 A4 84 53 42 46 INT1p.IDAD..SBF 2A070: 53 53 42 46 49 00 5B 82 42 0E 54 50 44 32 08 5F SSBFI.[.B.TPD2._ 2A080: 41 44 52 00 08 49 44 41 44 00 08 48 49 44 32 00 ADR..IDAD..HID2. 2A090: 08 5F 48 49 44 0D 45 4C 41 4E 30 36 33 34 00 08 ._HID.ELAN0634.. 2A0A0: 5F 43 49 44 0D 50 4E 50 30 43 35 30 00 08 5F 55 _CID.PNP0C50.._U 2A0B0: 49 44 01 14 4B 04 5F 44 53 4D 04 A0 3C 93 68 11 ID..K._DSM..<.h. 2A0C0: 13 0A 10 F7 F6 DF 3C 67 42 55 45 AD 05 B3 0A 3D ..https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861610/+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 1749427] Re: Unable to create KVM with uvtool on arm64 system
Marking this as invalid, referenced bugs are all closed and pretty sure this is not a problem on arm64 any longer. ** Changed in: ubuntu-kernel-tests Status: New => Invalid ** Changed in: linux (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1749427 Title: Unable to create KVM with uvtool on arm64 system Status in ubuntu-kernel-tests: Invalid Status in linux package in Ubuntu: Invalid Bug description: Not sure if this is related to bug 1452016, or just a HW issue: With the uvt-kvm create command on this Artful system, it returns: uvt-kvm: error: libvirt: unsupported configuration: ACPI requires UEFI on this architecture With the same command running on a Xenail system + Artful kernel, it returns: qemu-system-aarch64: Cirrus VGA not available ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-32-generic 4.13.0-32.35 ProcVersionSignature: User Name 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Feb 14 11:01 seq crw-rw 1 root audio 116, 33 Feb 14 11:01 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.7 Architecture: arm64 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: CurrentDmesg: Date: Wed Feb 14 11:09:44 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: console=ttyS0,9600n8r ro RelatedPackageVersions: linux-restricted-modules-4.13.0-32-generic N/A linux-backports-modules-4.13.0-32-generic N/A linux-firmware 1.169.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1749427/+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 1888617] Re: nvidia-kernel-source-435 435.21-0ubuntu0.18.04.2: nvidia kernel module failed to build
Same here, appeared today after system update. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubuntu. https://bugs.launchpad.net/bugs/1888617 Title: nvidia-kernel-source-435 435.21-0ubuntu0.18.04.2: nvidia kernel module failed to build Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Bug description: After a "usual" upgrade, my system did not give any sign of life on the monitor. I tried to boot an older kernel, it worked. Then I discovered, that the problem that nvidia drivers cannot be built against kernel linux-image-5.4.0-42-generic, which could be the problem. from /var/crash/nvidia-kernel-source-435.0.crash : /var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm-drv.c:662:44: error: ‘DRIVER_PRIME’ undeclared here (not in a function); did you mean ‘DRIVER_PCI_DMA’? .driver_features= DRIVER_GEM | DRIVER_PRIME | DRIVER_RENDER, ^~~~ DRIVER_PCI_DMA scripts/Makefile.build:273: recipe for target '/var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm-drv.o' failed make[2]: *** [/var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm-drv.o] Error 1 make[2]: *** Waiting for unfinished jobs ./tools/objtool/objtool check --module --retpoline --uaccess /var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm.o ./tools/objtool/objtool check --module --retpoline --uaccess /var/lib/dkms/nvidia/435.21/build/nvidia-uvm/uvm8_range_group_tree_test.o ./tools/objtool/objtool check --module --retpoline --uaccess /var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm-utils.o ./tools/objtool/objtool check --module --retpoline --uaccess /var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm-encoder.o ./tools/objtool/objtool check --module --retpoline --uaccess /var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm-gem.o ./tools/objtool/objtool check --module --retpoline --uaccess /var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm-connector.o ./tools/objtool/objtool check --module --retpoline --uaccess /var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm-crtc.o Makefile:1731: recipe for target '/var/lib/dkms/nvidia/435.21/build' failed make[1]: *** [/var/lib/dkms/nvidia/435.21/build] Error 2 make[1]: Leaving directory '/usr/src/linux-headers-5.4.0-42-generic' Makefile:81: recipe for target 'modules' failed make: *** [modules] Error 2 DKMSKernelVersion: 5.4.0-42-generic Date: Wed Jul 22 08:08:55 2020 DuplicateSignature: dkms:nvidia-kernel-source-435:435.21-0ubuntu0.18.04.2:/var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm-drv.c:662:44: error: ‘DRIVER_PRIME’ undeclared here (not in a function); did you mean ‘DRIVER_PCI_DMA’? Package: nvidia-kernel-source-435 435.21-0ubuntu0.18.04.2 PackageVersion: 435.21-0ubuntu0.18.04.2 SourcePackage: nvidia-graphics-drivers-435 Title: nvidia-kernel-source-435 435.21-0ubuntu0.18.04.2: nvidia kernel module failed to build ProblemType: Package DistroRelease: Ubuntu 18.04 Package: nvidia-kernel-source-435 435.21-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-62-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 DKMSKernelVersion: 5.4.0-42-generic Date: Wed Jul 22 08:08:55 2020 Dependencies: DuplicateSignature: dkms:nvidia-kernel-source-435:435.21-0ubuntu0.18.04.2:/var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm-drv.c:662:44: error: ‘DRIVER_PRIME’ undeclared here (not in a function); did you mean ‘DRIVER_PCI_DMA’? InstallationDate: Installed on 2020-01-06 (198 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageVersion: 435.21-0ubuntu0.18.04.2 Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 1.6.12ubuntu0.1 SourcePackage: nvidia-graphics-drivers-435 Title: nvidia-kernel-source-435 435.21-0ubuntu0.18.04.2: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-435/+bug/1888617/+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 1739560] Re: Trusty arm64 system will hang on libhugetlbfs shmoverride_linked test
I have not seen this occur on the -aws nitro backed arm64 instances. Giving that mcdivitt is EOL, killing off this bug. 07/09 11:08:48 DEBUG| utils:0153| [stdout] chunk-overcommit (2M: 64): PASS 07/09 11:08:48 DEBUG| utils:0153| [stdout] alloc-instantiate-race shared (2M: 64): PASS 07/09 11:08:48 DEBUG| utils:0153| [stdout] alloc-instantiate-race private (2M: 64): PASS 07/09 11:08:48 DEBUG| utils:0153| [stdout] truncate_reserve_wraparound (2M: 64):PASS 07/09 11:08:48 DEBUG| utils:0153| [stdout] truncate_sigbus_versus_oom (2M: 64): PASS 07/09 11:08:48 DEBUG| utils:0153| [stdout] get_huge_pages (2M: 64): PASS 07/09 11:08:48 DEBUG| utils:0153| [stdout] shmoverride_linked (2M: 64): PASS 07/09 11:08:48 DEBUG| utils:0153| [stdout] HUGETLB_SHM=yes shmoverride_linked (2M: 64): PASS 07/09 11:08:48 DEBUG| utils:0153| [stdout] shmoverride_linked_static (2M: 64): PASS 07/09 11:08:48 DEBUG| utils:0153| [stdout] HUGETLB_SHM=yes shmoverride_linked_static (2M: 64): PASS 07/09 11:08:48 DEBUG| utils:0153| [stdout] LD_PRELOAD=libhugetlbfs.so shmoverride_unlinked (2M: 64):PASS 07/09 11:08:48 DEBUG| utils:0153| [stdout] LD_PRELOAD=libhugetlbfs.so HUGETLB_SHM=yes shmoverride_unlinked (2M: 64):PASS 07/09 11:08:48 DEBUG| utils:0153| [stdout] quota.sh (2M: 64): PASS 07/09 11:08:48 DEBUG| utils:0153| [stdout] counters.sh (2M: 64):PASS 07/09 11:08:49 DEBUG| utils:0153| [stdout] mmap-gettest 10 20 (2M: 64): PASS 07/09 11:08:49 DEBUG| utils:0153| [stdout] mmap-cow 19 20 (2M: 64): PASS 07/09 11:08:49 DEBUG| utils:0153| [stdout] set shmmax limit to 41943040 07/09 11:08:50 DEBUG| utils:0153| [stdout] shm-fork 10 10 (2M: 64): PASS 07/09 11:08:50 DEBUG| utils:0153| [stdout] set shmmax limit to 41943040 07/09 11:08:52 DEBUG| utils:0153| [stdout] shm-fork 10 20 (2M: 64): PASS 07/09 11:08:52 DEBUG| utils:0153| [stdout] set shmmax limit to 41943040 07/09 11:08:52 DEBUG| utils:0153| [stdout] shm-getraw 20 /dev/full (2M: 64):PASS 07/09 11:09:18 DEBUG| utils:0153| [stdout] fallocate_stress.sh (2M: 64): PASS 07/09 11:09:18 DEBUG| utils:0153| [stdout] ** TEST SUMMARY 07/09 11:09:18 DEBUG| utils:0153| [stdout] * 2M 07/09 11:09:18 DEBUG| utils:0153| [stdout] * 32-bit 64-bit 07/09 11:09:18 DEBUG| utils:0153| [stdout] * Total testcases: 0 113 07/09 11:09:18 DEBUG| utils:0153| [stdout] * Skipped: 0 0 07/09 11:09:18 DEBUG| utils:0153| [stdout] *PASS: 0 111 07/09 11:09:18 DEBUG| utils:0153| [stdout] *FAIL: 0 0 07/09 11:09:18 DEBUG| utils:0153| [stdout] *Killed by signal: 0 1 07/09 11:09:18 DEBUG| utils:0153| [stdout] * Bad configuration: 0 1 07/09 11:09:18 DEBUG| utils:0153| [stdout] * Expected FAIL: 0 0 07/09 11:09:18 DEBUG| utils:0153| [stdout] * Unexpected PASS: 0 0 07/09 11:09:18 DEBUG| utils:0153| [stdout] *Test not present: 0 0 07/09 11:09:18 DEBUG| utils:0153| [stdout] * Strange test result: 0 0 07/09 11:09:18 DEBUG| utils:0153| [stdout] ** ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: ubuntu-kernel-tests Status: Incomplete => 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/1739560 Title: Trusty arm64 system will hang on libhugetlbfs shmoverride_linked test Status in ubuntu-kernel-tests: Invalid Status in linux package in Ubuntu: Invalid Bug description: Steps: 1. Deploy an ARM64 system with Trusty 2. Install necessary packages 3. git clone --depth=1 -b next https://github.com/libhugetlbfs/libhugetlbfs.git 4. make BUILDTYPE=NATIVEONLY 5. execute the run_test.py in tests directory Results: * you will see it stuck at shmoverride_linked test, no output for this test in syslog truncate_reserve_wraparound (2M: 64): PASS truncate_sigbus_versus_oom (2M: 64): PASS get_huge_pages (2M: 64): PASS shmoverride_linked (2M: 64): This issue can be reproduced in 3.13.0-137 and 3.13.0-138 in proposed. As we didn't run any regression-test on this node between 3.13.0-135 ~ 3.13.0-136 (this node was broken). This test cannot be built on ARM64 before (till 3.13.0-133, we have changed to use the upstream repo since then) therefore I think this can be considered as not a regression. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-137-generic 3.13.0-137.186 ProcVersionSignature: User Name 3.13.0-137.186-generic 3.13.11-ckt39 Uname: Linux 3.13.0-137-generic aarch64 AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed
[Kernel-packages] [Bug 1776654] Re: systemd upstream sysusers tests fails
** Changed in: systemd (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776654 Title: systemd upstream sysusers tests fails Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in linux source package in Bionic: Invalid Status in systemd source package in Bionic: Fix Released Status in linux source package in Cosmic: Invalid Status in linux source package in Eoan: Invalid Status in systemd source package in Eoan: Fix Released Status in linux source package in Focal: Invalid Status in systemd source package in Focal: Fix Released Bug description: [impact] TEST-21-SYSUSERS autopkgtest fails [test case] see original description [regression potential] any regression would be limited to incorrect pass/fail of TEST-21-SYSUSERS [scope] TEST-21-SYSUSERS does not exist in Xenial, it is first contained in Bionic. This is needed for B, E, and F. [original description] https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-cosmic-canonical-kernel-team- bootstrap/cosmic/amd64/s/systemd/20180613_003352_38c07@/log.gz == TEST-21-SYSUSERS == make: Entering directory '/tmp/autopkgtest.phv1ss/build.sqb/src/test/TEST-21-SYSUSERS' TEST CLEANUP: Sysuser-related tests TEST SETUP: Sysuser-related tests TEST RUN: Sysuser-related tests *** Running test-1.input *** Running test-2.input *** Running test-3.input *** Running test-4.input *** Running test unhappy-1.input --- /var/tmp/systemd-test.TjNA7s/tmp/err 2018-06-13 00:22:12.805061468 + +++ unhappy-1.expected-err2018-01-28 15:58:17.0 + @@ -1 +1 @@ -Creating user xxx (n/a) with uid 312 and gid 310. +Failed to parse UID: '99': Numerical result out of range Unexpected error output for unhappy-1.input Creating user xxx (n/a) with uid 312 and gid 310. make: *** [run] Error 1 Makefile:4: recipe for target 'run' failed make: Leaving directory '/tmp/autopkgtest.phv1ss/build.sqb/src/test/TEST-21-SYSUSERS' FAILED TESTS: test/TEST-21-SYSUSERS autopkgtest [00:22:13]: test upstream: ---] upstream FAIL non-zero exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776654/+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 1882419] Re: Intel 3945ABG [8086:4227] Subsystem [8086:1010]: syslog flooded with "wlan0: Failed check-sdata-in-driver check, flags: 0x4"
Seemingly related report on the kernel bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=98321 ** Bug watch added: Linux Kernel Bug Tracker #98321 https://bugzilla.kernel.org/show_bug.cgi?id=98321 -- 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/1882419 Title: Intel 3945ABG [8086:4227] Subsystem [8086:1010]: syslog flooded with "wlan0: Failed check-sdata-in-driver check, flags: 0x4" Status in linux package in Ubuntu: Confirmed Bug description: This issue can be found since 4.15.0-99-generic Not sure how to reproduce this yet. But when this happens syslog will be flooded with the following error message, the wifi led will be off, the disk I/O LED will keep blinking (I guess it's writing those log) and the system will be very slow. May 1 22:53:47 allen-laptop kernel: [ 1380.068692] [ cut here ] May 1 22:53:47 allen-laptop kernel: [ 1380.068693] wlan0: Failed check-sdata-in-driver check, flags: 0x4 May 1 22:53:47 allen-laptop kernel: [ 1380.068717] WARNING: CPU: 0 PID: 3 at /build/linux-OORAka/linux-4.15.0/net/mac80211/driver-ops.h:18 drv_sta_state+0x13d/0x3b0 [mac80211] May 1 22:53:47 allen-laptop kernel: [ 1380.068718] Modules linked in: rfcomm ccm bnep toshiba_acpi sparse_keymap industrialio toshiba_haps hp_accel lis3lv02d hdaps input_polldev binfmt_misc btusb btrtl btbcm btintel bluetooth coretemp ecdh_generic kvm irqbypass joydev input_leds serio_raw pcmcia snd_hda_codec_analog snd_hda_codec_generic wmi_bmof r852 sm_common nand nand_ecc nand_bch bch yenta_socket mtd pcmcia_rsrc r592 pcmcia_core memstick lpc_ich arc4 iwl3945 thinkpad_acpi iwlegacy nvram mac80211 snd_seq_midi snd_seq_midi_event snd_rawmidi snd_hda_intel snd_hda_codec snd_hda_core cfg80211 snd_hwdep snd_pcm snd_seq snd_seq_device shpchp snd_timer snd soundcore mac_hid sch_fq_codel cuse parport_pc ppdev lp parport ip_tables x_tables autofs4 i915 psmouse i2c_algo_bit ahci libahci sdhci_pci firewire_ohci drm_kms_helper e1000e firewire_core May 1 22:53:47 allen-laptop kernel: [ 1380.068741] pata_acpi sdhci syscopyarea crc_itu_t sysfillrect sysimgblt fb_sys_fops ptp drm pps_core wmi video May 1 22:53:47 allen-laptop kernel: [ 1380.068747] CPU: 0 PID: 3 Comm: kworker/0:0 Tainted: GW4.15.0-99-generic #100-Ubuntu May 1 22:53:47 allen-laptop kernel: [ 1380.068749] Hardware name: LENOVO 7733BW8/7733BW8, BIOS 7LETC4WW (2.24 ) 08/15/2008 May 1 22:53:47 allen-laptop kernel: [ 1380.068766] Workqueue: events_freezable ieee80211_restart_work [mac80211] May 1 22:53:47 allen-laptop kernel: [ 1380.068782] EIP: drv_sta_state+0x13d/0x3b0 [mac80211] May 1 22:53:47 allen-laptop kernel: [ 1380.068784] EFLAGS: 00010292 CPU: 0 May 1 22:53:47 allen-laptop kernel: [ 1380.068785] EAX: 0036 EBX: f48f8000 ECX: f4dcd670 EDX: 0007 May 1 22:53:47 allen-laptop kernel: [ 1380.068786] ESI: 0003 EDI: f48f8580 EBP: ed539bac ESP: ed539b88 May 1 22:53:47 allen-laptop kernel: [ 1380.068787] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 May 1 22:53:47 allen-laptop kernel: [ 1380.068788] CR0: 80050033 CR2: b6263160 CR3: 283c CR4: 06f0 May 1 22:53:47 allen-laptop kernel: [ 1380.068789] Call Trace: May 1 22:53:47 allen-laptop kernel: [ 1380.068807] sta_info_move_state+0x275/0x360 [mac80211] May 1 22:53:47 allen-laptop kernel: [ 1380.068825] __sta_info_destroy_part2+0x35/0x180 [mac80211] May 1 22:53:47 allen-laptop kernel: [ 1380.068842] __sta_info_flush+0x115/0x190 [mac80211] May 1 22:53:47 allen-laptop kernel: [ 1380.068864] ieee80211_set_disassoc+0xb7/0x3f0 [mac80211] May 1 22:53:47 allen-laptop kernel: [ 1380.068886] ieee80211_mgd_deauth+0x279/0x450 [mac80211] May 1 22:53:47 allen-laptop kernel: [ 1380.068889] ? check_preempt_curr+0x27/0x80 May 1 22:53:47 allen-laptop kernel: [ 1380.068909] ? ieee80211_disassoc+0x20/0x20 [mac80211] May 1 22:53:47 allen-laptop kernel: [ 1380.068929] ieee80211_deauth+0x16/0x20 [mac80211] May 1 22:53:47 allen-laptop kernel: [ 1380.068948] cfg80211_mlme_deauth+0x99/0x190 [cfg80211] May 1 22:53:47 allen-laptop kernel: [ 1380.068967] cfg80211_mlme_down+0x52/0x70 [cfg80211] May 1 22:53:47 allen-laptop kernel: [ 1380.068987] cfg80211_disconnect+0x114/0x1e0 [cfg80211] May 1 22:53:47 allen-laptop kernel: [ 1380.069002] __cfg80211_leave+0x135/0x180 [cfg80211] May 1 22:53:47 allen-laptop kernel: [ 1380.069018] cfg80211_leave+0x22/0x30 [cfg80211] May 1 22:53:47 allen-laptop kernel: [ 1380.069034] ? cfg80211_leave+0x30/0x30 [cfg80211] May 1 22:53:47 allen-laptop kernel: [ 1380.069049] cfg80211_netdev_notifier_call+0x2fd/0x700 [cfg80211] May 1 22:53:47 allen-laptop kernel: [ 1380.069052] ? sched_slice.isra.57+0x55/0xb0 May 1 22:53:47 allen-laptop kernel: [ 1380.069056] ? __update_load_avg_se.isra.29+0x2b3/0x2c0
[Kernel-packages] [Bug 1888523] Re: PCIe Bus Error device 8086:a298 spam
I don't know how to edit posts but I wanted to add: I plugged a different m.2 NVMe from a different manufacturer into the "M2A_32G" port to see if the port is the problem. There are no errors. I can only replicate the problem with the XPG NVMe in port "M2A_32G". ** Attachment added: "Z370 AORUS Gaming 7 Motherboard Layout.png" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888523/+attachment/5395628/+files/Z370%20AORUS%20Gaming%207%20Motherboard%20Layout.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/1888523 Title: PCIe Bus Error device 8086:a298 spam Status in linux package in Ubuntu: Incomplete Bug description: Kubuntu 20.04 i7-8700k Gigabyte Aorus Gaming 7 16GB Corsair Dominator RAM I noticed this non-stop spam occurring every second or 2 in my syslog. What is it and is it bad? Here is a bit of the spam: Jul 22 11:04:21 PC034 kernel: [78364.160774] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:21 PC034 kernel: [78364.160785] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 22 11:04:21 PC034 kernel: [78364.160791] pcieport :00:1d.0: AER: device [8086:a298] error status/mask=0001/2000 Jul 22 11:04:21 PC034 kernel: [78364.160795] pcieport :00:1d.0: AER:[ 0] RxErr Jul 22 11:04:25 PC034 kernel: [78367.840037] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:25 PC034 kernel: [78367.840042] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 22 11:04:25 PC034 kernel: [78367.840044] pcieport :00:1d.0: AER: device [8086:a298] error status/mask=0001/2000 Jul 22 11:04:25 PC034 kernel: [78367.840046] pcieport :00:1d.0: AER:[ 0] RxErr Jul 22 11:04:28 PC034 kernel: [78371.222986] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:28 PC034 kernel: [78371.222997] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 22 11:04:28 PC034 kernel: [78371.223003] pcieport :00:1d.0: AER: device [8086:a298] error status/mask=0001/2000 Jul 22 11:04:28 PC034 kernel: [78371.223007] pcieport :00:1d.0: AER:[ 0] RxErr Jul 22 11:04:28 PC034 kernel: [78371.280463] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:28 PC034 kernel: [78371.280473] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 22 11:04:28 PC034 kernel: [78371.280481] pcieport :00:1d.0: AER: device [8086:a298] error status/mask=0001/2000 Jul 22 11:04:28 PC034 kernel: [78371.280486] pcieport :00:1d.0: AER:[ 0] RxErr Jul 22 11:04:36 PC034 kernel: [78378.515980] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:36 PC034 kernel: [78378.515991] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 22 11:04:36 PC034 kernel: [78378.515999] pcieport :00:1d.0: AER: device [8086:a298] error status/mask=0001/2000 Jul 22 11:04:36 PC034 kernel: [78378.516004] pcieport :00:1d.0: AER:[ 0] RxErr Jul 22 11:04:36 PC034 kernel: [78378.842283] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:36 PC034 kernel: [78378.842293] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 22 11:04:36 PC034 kernel: [78378.842301] pcieport :00:1d.0: AER: device [8086:a298] error status/mask=0001/2000 Jul 22 11:04:36 PC034 kernel: [78378.842306] pcieport :00:1d.0: AER:[ 0] RxErr Jul 22 11:04:37 PC034 kernel: [78380.104714] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:37 PC034 kernel: [78380.104725] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 22 11:04:37 PC034 kernel: [78380.104733] pcieport :00:1d.0: AER: device [8086:a298] error status/mask=0001/2000 Jul 22 11:04:37 PC034 kernel: [78380.104739] pcieport :00:1d.0: AER:[ 0] RxErr Jul 22 11:04:39 PC034 kernel: [78382.170309] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:39 PC034 kernel: [78382.170320] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 22 11:04:39 PC034 kernel: [78382.170328] pcieport :00:1d.0: AER: device [8086:a298] error status/mask=0001/2000 Jul 22 11:04:39 PC034 kernel: [78382.170333] pcieport :00:1d.0: AER:[ 0] RxErr Jul 22
[Kernel-packages] [Bug 1885730] Re: Bring back ondemand.service or switch kernel default governor for pstate - pstate now defaults to performance governor
@colin-king @juliank It feels to me that the oem flavour should default to (powersave/ondemand), as it is more-or-less laptop kernel flavour. I feel like generic kernel flavour should remain on performance. I feel like we should have a unit, that for chassis=laptop turns on (powersave/ondemand). Possibly shipped in like procps package. Or there should be like graphical desktop integration to control this (aka game mode). Is there a per-chasis type setting in kernel? as in something like CONFIG_WHEN_ON_LAPTOP_DEFAULT_GOV_* ? Do above actionable things make sense? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1885730 Title: Bring back ondemand.service or switch kernel default governor for pstate - pstate now defaults to performance governor Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Invalid Status in linux source package in Groovy: Confirmed Status in systemd source package in Groovy: Invalid Bug description: In a recent merge from Debian we lost ondemand.service, meaning all CPUs now run in Turbo all the time when idle, which is clearly suboptimal. The discussion in bug 1806012 seems misleading, focusing on p-state vs other drivers, when in fact, the script actually set the default governor for the pstate driver on platforms that use pstate. Everything below only looks at systems that use pstate. pstate has two governors: performance and powerstate. performance runs CPU at maximum frequency constantly, and powersave can be configured using various energy profiles energy profiles: - performance - balanced performance - balanced power - power It defaults to balanced performance, I think, but I'm not sure. Whether performance governor is faster than powersave governor is not even clear. https://www.phoronix.com/scan.php?page=article=linux50-pstate- cpufreq=5 benchmarked them, but did not benchmark the individual energy profiles. For a desktop/laptop, the expected behavior is the powersave governor with balanced_performance on AC and balanced_power on battery. I don't know about servers or VMs, but the benchmark series seems to indicate it does not really matter much performance wise. I think most other distributions configure their kernels to use the powersave governor by default, whereas we configure it to use the performance governor and then switch it later in the boot to get the maximum performance during bootup. It's not clear to me that's actually useful. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885730/+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 1888523] Re: PCIe Bus Error device 8086:a298 spam
5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 I pulled all the hardware from my PC and went through each part one by one. The device that makes these errors appear is the XPG GAMMIX S5 m.2 when plugged into port "M2A_32G". I moved the m.2 device to port "M2P_32G" and the errors disappeared. The device: 04:00.0 Non-Volatile memory controller [0108]: Realtek Semiconductor Co., Ltd. Device [10ec:5762] (rev 01) ** Attachment added: "lspci_-nnvv" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888523/+attachment/5395620/+files/lspci_-nnvv -- 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/1888523 Title: PCIe Bus Error device 8086:a298 spam Status in linux package in Ubuntu: Incomplete Bug description: Kubuntu 20.04 i7-8700k Gigabyte Aorus Gaming 7 16GB Corsair Dominator RAM I noticed this non-stop spam occurring every second or 2 in my syslog. What is it and is it bad? Here is a bit of the spam: Jul 22 11:04:21 PC034 kernel: [78364.160774] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:21 PC034 kernel: [78364.160785] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 22 11:04:21 PC034 kernel: [78364.160791] pcieport :00:1d.0: AER: device [8086:a298] error status/mask=0001/2000 Jul 22 11:04:21 PC034 kernel: [78364.160795] pcieport :00:1d.0: AER:[ 0] RxErr Jul 22 11:04:25 PC034 kernel: [78367.840037] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:25 PC034 kernel: [78367.840042] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 22 11:04:25 PC034 kernel: [78367.840044] pcieport :00:1d.0: AER: device [8086:a298] error status/mask=0001/2000 Jul 22 11:04:25 PC034 kernel: [78367.840046] pcieport :00:1d.0: AER:[ 0] RxErr Jul 22 11:04:28 PC034 kernel: [78371.222986] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:28 PC034 kernel: [78371.222997] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 22 11:04:28 PC034 kernel: [78371.223003] pcieport :00:1d.0: AER: device [8086:a298] error status/mask=0001/2000 Jul 22 11:04:28 PC034 kernel: [78371.223007] pcieport :00:1d.0: AER:[ 0] RxErr Jul 22 11:04:28 PC034 kernel: [78371.280463] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:28 PC034 kernel: [78371.280473] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 22 11:04:28 PC034 kernel: [78371.280481] pcieport :00:1d.0: AER: device [8086:a298] error status/mask=0001/2000 Jul 22 11:04:28 PC034 kernel: [78371.280486] pcieport :00:1d.0: AER:[ 0] RxErr Jul 22 11:04:36 PC034 kernel: [78378.515980] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:36 PC034 kernel: [78378.515991] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 22 11:04:36 PC034 kernel: [78378.515999] pcieport :00:1d.0: AER: device [8086:a298] error status/mask=0001/2000 Jul 22 11:04:36 PC034 kernel: [78378.516004] pcieport :00:1d.0: AER:[ 0] RxErr Jul 22 11:04:36 PC034 kernel: [78378.842283] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:36 PC034 kernel: [78378.842293] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 22 11:04:36 PC034 kernel: [78378.842301] pcieport :00:1d.0: AER: device [8086:a298] error status/mask=0001/2000 Jul 22 11:04:36 PC034 kernel: [78378.842306] pcieport :00:1d.0: AER:[ 0] RxErr Jul 22 11:04:37 PC034 kernel: [78380.104714] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:37 PC034 kernel: [78380.104725] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 22 11:04:37 PC034 kernel: [78380.104733] pcieport :00:1d.0: AER: device [8086:a298] error status/mask=0001/2000 Jul 22 11:04:37 PC034 kernel: [78380.104739] pcieport :00:1d.0: AER:[ 0] RxErr Jul 22 11:04:39 PC034 kernel: [78382.170309] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 Jul 22 11:04:39 PC034 kernel: [78382.170320] pcieport :00:1d.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jul 22 11:04:39 PC034 kernel: [78382.170328] pcieport :00:1d.0: AER: device [8086:a298] error status/mask=0001/2000 Jul 22 11:04:39 PC034
[Kernel-packages] [Bug 1888617] Re: nvidia-kernel-source-435 435.21-0ubuntu0.18.04.2: nvidia kernel module failed to build
I updated yesterday and I encounter the same crash. The result is a login loop problem in my main user and a fixed display resolution problem. Can you recommend a temporary fix ? Last part of nvidia-kernel-source-435.0.crash /nvidia-drm/nvidia-drm-helper.c /var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm-drv.c:662:44: error: ‘DRIVER_PRIME’ undeclared here (not in a function); did you mean ‘DRIVER_PCI_DMA’? .driver_features= DRIVER_GEM | DRIVER_PRIME | DRIVER_RENDER, ^~~~ DRIVER_PCI_DMA cc -Wp,-MD,/var/lib/dkms/nvidia/435.21/build/nvidia-drm/.nv-pci-table.o.d -nostdinc -isystem /usr/lib/gcc/x86_64-linux-gnu/7/include -I./arch/x86/include -I./arch/x86/include/generated -I./include -I./arch/x86/include/uapi -I./arch/x86/include/generated/uapi -I./include/uapi -I./include/generated/uapi -include ./include/linux/kconfig.h -Iubuntu/include -include ./include/linux/compiler_types.h -D__KERNEL__ -Wall -Wundef -Werror=strict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -fshort-wchar -fno-PIE -Werror=implicit-function-declaration -Werror=implicit-int -Wno-format-security -std=gnu89 -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx -m64 -falign-jumps=1 -falign-loops=1 -mno-80387 -mno-fp-ret-in-387 -mpreferred-stack-boundary=3 -mskip-rax-setup -mtune=generic -mno-red-zone -mcmodel=kernel -DCONFIG_X86_X32_ABI -DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -DCONFIG_AS_CFI_SECTIONS=1 -DCONFIG_AS_SSSE3=1 -DCONFIG_AS_AVX=1 -DCONFIG_AS_AVX2=1 -DCONFIG_AS_AVX512=1 -DCONFIG_AS_SHA1_NI=1 -DCONFIG_AS_SHA256_NI=1 -Wno-sign-compare -fno-asynchronous-unwind-tables -mindirect-branch=thunk-extern -mindirect-branch-register -fno-jump-tables -fno-delete-null-pointer-checks -Wno-frame-address -Wno-format-truncation -Wno-format-overflow -O2 --param=allow-store-data-races=0 -Wframe-larger-than=1024 -fstack-protector-strong -Wno-unused-but-set-variable -Wimplicit-fallthrough -Wno-unused-const-variable -fno-omit-frame-pointer -fno-optimize-sibling-calls -fno-var-tracking-assignments -pg -mrecord-mcount -mfentry -DCC_USING_FENTRY -Wdeclaration-after-statement -Wvla -Wno-pointer-sign -Wno-array-bounds -Wno-stringop-overflow -Wno-restrict -Wno-maybe-uninitialized -fno-strict-overflow -fno-merge-all-constants -fmerge-constants -fno-stack-check -fconserve-stack -Werror=date-time -Werror=incompatible-pointer-types -Werror=designated-init -I/var/lib/dkms/nvidia/435.21/build/common/inc -I/var/lib/dkms/nvidia/435.21/build -Wall -MD -Wno-cast-qual -Wno-error -Wno-format-extra-args -D__KERNEL__ -DMODULE -DNVRM -DNV_VERSION_STRING=\"435.21\" -Wno-unused-function -Wuninitialized -fno-strict-aliasing -mno-red-zone -mcmodel=kernel -DNV_UVM_ENABLE -Werror=undef -DNV_SPECTRE_V2=0 -DMODULE -DKBUILD_BASENAME='"nv_pci_table"' -DKBUILD_MODNAME='"nvidia_drm"' -c -o /var/lib/dkms/nvidia/435.21/build/nvidia-drm/nv-pci-table.o /var/lib/dkms/nvidia/435.21/build/nvidia-drm/nv-pci-table.c scripts/Makefile.build:273: recipe for target '/var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm-drv.o' failed make[2]: *** [/var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm-drv.o] Error 1 make[2]: *** Waiting for unfinished jobs Makefile:1731: recipe for target '/var/lib/dkms/nvidia/435.21/build' failed make[1]: *** [/var/lib/dkms/nvidia/435.21/build] Error 2 make[1]: Leaving directory '/usr/src/linux-headers-5.4.0-42-generic' Makefile:81: recipe for target 'modules' failed make: *** [modules] Error 2 DKMSKernelVersion: 5.4.0-42-generic Date: Thu Jul 23 22:04:13 2020 DuplicateSignature: dkms:nvidia-kernel-source-435:435.21-0ubuntu0.18.04.2:/var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm-drv.c:662:44: error: ‘DRIVER_PRIME’ undeclared here (not in a function); did you mean ‘DRIVER_PCI_DMA’? Package: nvidia-kernel-source-435 435.21-0ubuntu0.18.04.2 PackageVersion: 435.21-0ubuntu0.18.04.2 SourcePackage: nvidia-graphics-drivers-435 Title: nvidia-kernel-source-435 435.21-0ubuntu0.18.04.2: nvidia kernel module failed to build -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubuntu. https://bugs.launchpad.net/bugs/1888617 Title: nvidia-kernel-source-435 435.21-0ubuntu0.18.04.2: nvidia kernel module failed to build Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Bug description: After a "usual" upgrade, my system did not give any sign of life on the monitor. I tried to boot an older kernel, it worked. Then I discovered, that the problem that nvidia drivers cannot be built against kernel linux-image-5.4.0-42-generic, which could be the problem. from /var/crash/nvidia-kernel-source-435.0.crash : /var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm-drv.c:662:44: error: ‘DRIVER_PRIME’ undeclared here (not in a function); did you mean
[Kernel-packages] [Bug 1883962] Re: apparmor reference leak causes refcount_t overflow with af_alg_accept()
Verification done on "Disco" (linux-hwe-5.0) --- # uname -rv 5.0.0-58-generic #62~18.04.1-Ubuntu SMP Tue Jul 14 03:37:30 UTC 2020 For some other reason the kprobes module is not picking up on accept, only on release. This is unrelated to this patchset. I used kprobe events instead, which is working, and reveals the ref counter does not leak (stable increase/decrease on accept/release.) On the example below, it varies between 0x64b and 0x64c, correctly. # ./aa-refcnt-af_alg & # echo 'p af_alg_accept sk=%di count=+0x0(+0x0(+0x278(%di))):x32' > /sys/kernel/debug/tracing/kprobe_events # echo 'p af_alg_release_parent sk=%di count=+0x0(+0x0(+0x278(%di))):x32' >> /sys/kernel/debug/tracing/kprobe_events # echo 1 > /sys/kernel/debug/tracing/events/kprobes/enable # cat /sys/kernel/debug/tracing/trace_pipe ... aa-refcnt-af_al-21362 [002] 77023.869615: p_af_alg_accept_0: (af_alg_accept+0x0/0x1c0 [af_alg]) sk=0x9138b54c2400 count=0x64b aa-refcnt-af_al-21362 [002] 77023.869619: p_af_alg_release_parent_0: (af_alg_release_parent+0x0/0xc0 [af_alg]) sk=0x9138b5e27800 count=0x64c aa-refcnt-af_al-21362 [002] 77023.869623: p_af_alg_accept_0: (af_alg_accept+0x0/0x1c0 [af_alg]) sk=0x9138b54c2400 count=0x64b aa-refcnt-af_al-21362 [002] 77023.869626: p_af_alg_release_parent_0: (af_alg_release_parent+0x0/0xc0 [af_alg]) sk=0x9138b5e27800 count=0x64c aa-refcnt-af_al-21362 [002] 77023.869630: p_af_alg_accept_0: (af_alg_accept+0x0/0x1c0 [af_alg]) sk=0x9138b54c2400 count=0x64b aa-refcnt-af_al-21362 [002] 77023.869633: p_af_alg_release_parent_0: (af_alg_release_parent+0x0/0xc0 [af_alg]) sk=0x9138b5e27800 count=0x64c ... ctrl-c # echo 0 > /sys/kernel/debug/tracing/events/kprobes/enable # echo > /sys/kernel/debug/tracing/kprobe_events # killall aa-refcnt-af_alg Details: --- We want this value from 'struct sock *sk': kref_read(_CTX(sk)->label->count) With: #define SK_CTX(X) apparmor_sock(X) static inline struct aa_sk_ctx *apparmor_sock(const struct sock *sk) ... return sk->sk_security + apparmor_blob_sizes->lbs_sock; ... Checking the value for lbs_sock w/ a kernel module: [76604.268403] apparmor_blob_sizes->lbs_sock: 0 And struct member offsets: $ pahole --hex -C sock usr/lib/debug/boot/vmlinux-5.0.0-58-generic | grep sk_security void * sk_security; /* 0x278 0x8 */ $ pahole --hex -C aa_sk_ctx usr/lib/debug/boot/vmlinux-5.0.0-58-generic | grep -w label struct aa_label * label;/* 0 0x8 */ $ pahole --hex -C aa_label usr/lib/debug/boot/vmlinux-5.0.0-58-generic | grep -w count struct krefcount;/* 0 0x4 */ -- 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/1883962 Title: apparmor reference leak causes refcount_t overflow with af_alg_accept() Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Eoan: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Groovy: Invalid Bug description: [Impact] * Users of the Crypto (user-space) API (i.e., AF_ALG) can trigger refcount errors in AppArmor under high load (might lead to memory leak or use after free.) * There is a reference leak in AppArmor when af_alg_accept() calls security_sock_graft() and then security_sk_clone(). * Both acquire a reference to a label, to assign it to the same pointer, but the latter does not release the former's acquired reference (before overwriting the pointer value.) * This reference leak builds up over time, and under high load can eventually overflow/underflow/saturate refcount, depending on which value it has when a program hits that. * The fix just checks if the pointer has an assigned label, then releases its acquired reference. [Test Case] * See comment #1 for the test-case 'aa-refcnt-af_alg.c'. * Exercise that code path indefinitely until it hits the refcount_t overflow/underflow/saturate message (or not, with the patch.) (see comment #4) * It's possible to monitor refcount values with kprobes, to confirm whether or not the problem is happening. (see comments #2 and #3) [Other Info] * Patch applied upstream on v5.8-rc1 [1] * Applied on Unstable (tag Ubuntu-5.8-5.8.0-0.1) * Not required on Groovy (still 5.4; should sync from Unstable) * Not required on Eoan (EOL date before SRU cycle release date) * Required on Bionic and Focal. [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit?id=3b646abc5bc6c0df649daea4c2c976bd4d47e4c8 To manage notifications
[Kernel-packages] [Bug 1887774] Comment bridged from LTC Bugzilla
--- Comment From ma...@de.ibm.com 2020-07-24 12:54 EDT---
zfcp regression tested the private build from
https://people.canonical.com/~fheimes/lp1887774/.
(The private build seems to have the same kernelrelease as the latest official
update kernel. I removed the latter after going to the previous backlevel
official update kernel (5.4.0-40-generic) and before installing the private
build. I hope I did run the correct private build:
Linux hostname 5.4.0-42-generic #46 SMP Thu Jul 16 12:06:43 UTC 2020 s390x
s390x s390x GNU/Linux)
--
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/1887774
Title:
[UBUNTU 20.04] zfcp: Fix panic on ERP timeout for previously dismissed
ERP
Status in Ubuntu on IBM z Systems:
In Progress
Status in linux package in Ubuntu:
New
Status in linux source package in Bionic:
In Progress
Status in linux source package in Focal:
In Progress
Status in linux source package in Groovy:
New
Bug description:
SRU Justification:
==
[Impact]
* Linux kernel panics due to kernel page fault in IRQ context when
running zfcp_erp_timeout_handler() calling zfcp_erp_notify().
[Fix]
* 936e6b85da0476dd2edac7c51c68072da9fb4ba2 936e6b85da04 "scsi: zfcp:
Fix panic on ERP timeout for previously dismissed ERP action"
[Test Case]
* Requires an IBM z13/z13s or LinuxONE Rockhopper/Emperor system (or
newer) connected to zfcp capcble storage sub-system.
* Initiate an (ERP) timeout (maybe by injection or by causing a slow
recovery otherwise).
* Monitor the system log for any kernel panics.
[Regression Potential]
* The regression can be considered as medium since the modification is
platform specific / limited to s390x and again limited to the zfcp
layer.
* Within zfcp it's further limited to the error recovery procedure
(ERP) of fcp and only touches zfcp_erp.c, means the code path is
mainly active under error conditions.
[Other]
* The above fix is upstream accepted with v5.8-rc3, hence will make
it's way to groovy with kernel 5.8.
* Therefore this SRU request was submitted for bionic and focal only
and not for groovy.
__
Description: zfcp: Fix panic on ERP timeout for previously dismissed ERP
Symptom: Linux kernel panic due to kernel page fault in IRQ context
when running zfcp_erp_timeout_handler() calling
zfcp_erp_notify().
Problem: Suppose that, for unrelated reasons, FSF requests on behalf
of recovery are very slow and can run into the ERP timeout.
In the case at hand, we did adapter recovery to a large
degree. However due to the slowness a LUN open is pending so
the corresponding fc_rport remains blocked. After
fast_io_fail_tmo we trigger close physical port recovery for
the port under which the LUN should have been opened. The
new higher order port recovery dismisses the pending LUN
open ERP action and dismisses the pending LUN open FSF
request. Such dismissal decouples the ERP action from the
pending corresponding FSF request by setting
zfcp_fsf_req->erp_action to NULL (among other things)
[zfcp_erp_strategy_check_fsfreq()].
If now the ERP timeout for the pending open LUN request runs
out, we must not use zfcp_fsf_req->erp_action in the ERP
timeout handler. This is a problem since v4.15 commit
75492a51568b ("s390/scsi: Convert timers to use
timer_setup()"). Before that we intentionally only passed
zfcp_erp_action as context argument to
zfcp_erp_timeout_handler().
Note: The lifetime of the corresponding zfcp_fsf_req object
continues until a (late) response or an (unrelated) adapter
recovery.
Solution: Just like the regular response path ignores dismissed
requests [zfcp_fsf_req_complete() =>
zfcp_fsf_protstatus_eval() => return early] the ERP timeout
handler now needs to ignore dismissed requests. So simply
return early in the ERP timeout handler if the FSF request
is marked as dismissed in its status flags. To protect
against the race where zfcp_erp_strategy_check_fsfreq()
dismisses and sets zfcp_fsf_req->erp_action to NULL after
our previous status flag check, return early if
zfcp_fsf_req->erp_action is NULL. After all, the former ERP
action does not need to be woken up as that was already done
as part of the dismissal above [zfcp_erp_action_dismiss()].
Upstream-ID:
[Kernel-packages] [Bug 1885730] Re: Bring back ondemand.service or switch kernel default governor for pstate - pstate now defaults to performance governor
@Colin: I agree with all of that. Our kernel-side default is not powersave, but performance, across generic and oem, at the very least: $ grep CPU_FREQ_DEFAULT_GOV_.*=y /boot/config-5.* /boot/config-5.4.0-26-generic:CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y /boot/config-5.4.0-42-generic:CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y /boot/config-5.6.0-1018-oem:CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y /boot/config-5.6.0-1020-oem:CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y We used to set that to powersave (and ondemand on non-pstate) in ondemand.service, but have since removed the service in groovy. I believe the default governor kernel-side outside Ubuntu is usually CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND, which translates to ondemand pre- pstates, and powersave on pstates (compare Fedora), whereas Enterprise systems usually pick PERFORMANCE too (compare RHEL) - probably because most distributions focus on normal end users and enterprise on server and workstation. We don't have that distinction of course, so I'm not sure what the best way out is - default to powersave/ondemand and make server installer write performance - or vice versa default to performance and make ubiquity configure powersave for 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/1885730 Title: Bring back ondemand.service or switch kernel default governor for pstate - pstate now defaults to performance governor Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Invalid Status in linux source package in Groovy: Confirmed Status in systemd source package in Groovy: Invalid Bug description: In a recent merge from Debian we lost ondemand.service, meaning all CPUs now run in Turbo all the time when idle, which is clearly suboptimal. The discussion in bug 1806012 seems misleading, focusing on p-state vs other drivers, when in fact, the script actually set the default governor for the pstate driver on platforms that use pstate. Everything below only looks at systems that use pstate. pstate has two governors: performance and powerstate. performance runs CPU at maximum frequency constantly, and powersave can be configured using various energy profiles energy profiles: - performance - balanced performance - balanced power - power It defaults to balanced performance, I think, but I'm not sure. Whether performance governor is faster than powersave governor is not even clear. https://www.phoronix.com/scan.php?page=article=linux50-pstate- cpufreq=5 benchmarked them, but did not benchmark the individual energy profiles. For a desktop/laptop, the expected behavior is the powersave governor with balanced_performance on AC and balanced_power on battery. I don't know about servers or VMs, but the benchmark series seems to indicate it does not really matter much performance wise. I think most other distributions configure their kernels to use the powersave governor by default, whereas we configure it to use the performance governor and then switch it later in the boot to get the maximum performance during bootup. It's not clear to me that's actually useful. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885730/+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 1885730] Re: Bring back ondemand.service or switch kernel default governor for pstate - pstate now defaults to performance governor
The choice was made from running analysis on a wide range of Intel machines, old and new. We are trying to select the optimal choice for a wide range of CPUs for a wide range of use cases. Generally speaking, the intel-pstate governor has deeper understanding of the processor features and can access CPU metrics that can guide it to making an informed choice. >From our understanding, The intel-pstate driver should be the optimal choice for Intel Sandy Bridge CPUs onwards. The intel-pstate driver supports only the performance and powersave governors. In benchmarking we didn't observe much computational difference between the too once the CPU is fully loaded. However, cranking up or cranking down the load one will discover that the performance setting is more responsive than powersave. The overall compute throughput when fully loaded is the same, it's just a case that powersave may take a little longer to crank up to the full speed. It makes sense to default to powersave for most scenarios, especially for laptop users. Pre-Intel Sandy Bridge or non-x86 CPUs will default back to the non- intel pstate governor. So, question: Which kernel(s) are you referring to? -- 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/1885730 Title: Bring back ondemand.service or switch kernel default governor for pstate - pstate now defaults to performance governor Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Invalid Status in linux source package in Groovy: Confirmed Status in systemd source package in Groovy: Invalid Bug description: In a recent merge from Debian we lost ondemand.service, meaning all CPUs now run in Turbo all the time when idle, which is clearly suboptimal. The discussion in bug 1806012 seems misleading, focusing on p-state vs other drivers, when in fact, the script actually set the default governor for the pstate driver on platforms that use pstate. Everything below only looks at systems that use pstate. pstate has two governors: performance and powerstate. performance runs CPU at maximum frequency constantly, and powersave can be configured using various energy profiles energy profiles: - performance - balanced performance - balanced power - power It defaults to balanced performance, I think, but I'm not sure. Whether performance governor is faster than powersave governor is not even clear. https://www.phoronix.com/scan.php?page=article=linux50-pstate- cpufreq=5 benchmarked them, but did not benchmark the individual energy profiles. For a desktop/laptop, the expected behavior is the powersave governor with balanced_performance on AC and balanced_power on battery. I don't know about servers or VMs, but the benchmark series seems to indicate it does not really matter much performance wise. I think most other distributions configure their kernels to use the powersave governor by default, whereas we configure it to use the performance governor and then switch it later in the boot to get the maximum performance during bootup. It's not clear to me that's actually useful. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885730/+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 1550779] Re: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun
Hello, I think I am experiencing the same issue so I am not opening a new bug report. Below is the description I also posted a question about: I have upgraded to Kubuntu 20.04 from 19.10. Session went ok but after rebooting I noticed one or two times where my screen (external monitor connected via display port to my laptop) went on and off for 1-2 seconds. After the recent update to Kernel 5.4.0-40 and then to 5.4.0-42 these on and off instances are more frequent. System and sound etc works (doesn't hang) , only the screen goes black and on again, which is very annoying. This does not happen with HDMI cable connected, but instead there are some minor screen glitches, not very often though. I did not have any of those with 19.10...my system is details are shown below:. See especially the last part ie dmesg | grep -i i915. Note that reverting to kernel 5.4.0-39 things go back to normal. Operating System: Kubuntu 20.04 KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 Kernel Version: 5.4.0-40-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i5-10210U CPU @ 1.60GHz Memory: 15,5 GiB of RAM lspci 00:00.0 Host bridge: Intel Corporation Device 9b61 (rev 0c) 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics (rev 02) 00:12.0 Signal processing controller: Intel Corporation Comet Lake Thermal Subsytem 00:14.0 USB controller: Intel Corporation Device 02ed 00:14.2 RAM memory: Intel Corporation Device 02ef 00:15.0 Serial bus controller [0c80]: Intel Corporation Serial IO I2C Host Controller 00:16.0 Communication controller: Intel Corporation Comet Lake Management Engine Interface 00:17.0 SATA controller: Intel Corporation Comet Lake SATA AHCI Controller 00:1c.0 PCI bridge: Intel Corporation Device 02bc (rev f0) 00:1d.0 PCI bridge: Intel Corporation Device 02b0 (rev f0) 00:1d.1 PCI bridge: Intel Corporation Device 02b1 (rev f0) 00:1d.4 PCI bridge: Intel Corporation Device 02b4 (rev f0) 00:1f.0 ISA bridge: Intel Corporation Device 0284 00:1f.3 Audio device: Intel Corporation Device 02c8 00:1f.4 SMBus: Intel Corporation Device 02a3 00:1f.5 Serial bus controller [0c80]: Intel Corporation Comet Lake SPI (flash) Controller 01:00.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 2C 2018] (rev 06) 02:00.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 2C 2018] (rev 06) 02:01.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 2C 2018] (rev 06) 02:02.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 2C 2018] (rev 06) 03:00.0 System peripheral: Intel Corporation JHL7540 Thunderbolt 3 NHI [Titan Ridge 2C 2018] (rev 06) 3a:00.0 USB controller: Intel Corporation JHL7540 Thunderbolt 3 USB Controller [Titan Ridge 2C 2018] (rev 06) 3b:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTL8411B PCI Express Card Reader (rev 01) 3b:00.1 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 12) 40:00.0 Network controller: Intel Corporation Wi-Fi 6 AX200 (rev 1a) 45:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM981 inxi -G Graphics: Device-1: Intel UHD Graphics driver: i915 v: kernel Display: x11 server: X.Org 1.20.8 driver: modesetting unloaded: fbdev,vesa resolution: 2560x1440~60Hz OpenGL: renderer: Mesa Intel UHD Graphics (CML GT2) v: 4.6 Mesa 20.0.8 vainfo libva info: VA-API version 1.7.0 libva info: User environment variable requested driver 'iHD' libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_7 libva info: va_openDriver() returns 0 vainfo: VA-API version: 1.7 (libva 2.6.0) vainfo: Driver version: Intel iHD driver for Intel(R) Gen Graphics - 20.1.1 () vainfo: Supported profile and entrypoints VAProfileMPEG2Simple : VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSliceLP VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSliceLP VAProfileJPEGBaseline : VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointEncPicture VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSliceLP VAProfileVP8Version0_3 : VAEntrypointVLD VAProfileHEVCMain : VAEntrypointVLD VAProfileHEVCMain10 : VAEntrypointVLD VAProfileVP9Profile0 : VAEntrypointVLD VAProfileVP9Profile2 : VAEntrypointVLD glxinfo | grep -i opengl OpenGL vendor string: Intel OpenGL renderer string: Mesa Intel(R) UHD Graphics (CML GT2) OpenGL core profile version string: 4.6 (Core Profile) Mesa 20.0.8 OpenGL core profile shading language version string: 4.60 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version
[Kernel-packages] [Bug 1822394] Re: [Dell BIOSes dated 27 Mar 2019, XPS 9575, Precision 5530 2-in-1] laptop keyboard & touchpad not working at gdm screen after boot
Just commenting to say I have the same problem with Dell XPS 15 2-in-1 9575, BIOS version 1.12.1. The problem was indeed fixed with blacklisting intel_vbtn. Using Fedora 32. -- 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/1822394 Title: [Dell BIOSes dated 27 Mar 2019, XPS 9575, Precision 5530 2-in-1] laptop keyboard & touchpad not working at gdm screen after boot Status in libinput package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: On a dell XPS 15 2-in-1 with the latest 1.4.0 bios, my touchpad and keyboard are unresponsive at the gdm login screen. Keyboard works to unlock encrypted harddrive before that though. If I plug in a USB keyboard or activate my bluetooth mouse, I can use those to log in, and then after logging in the laptop touchpad and keyboard work again. Logging out of the desktop results in the laptop touchpad and keyboard working on the gdm screen. Did not see this behavior before upgrading from 1.2.0 bios to 1.4.0 bios, but also had not rebooted in a while, so not sure if bios or package upgrades triggered this behavior. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gdm3 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 29 17:51:00 2019 InstallationDate: Installed on 2018-09-26 (184 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gdm3 UpgradeStatus: Upgraded to disco on 2019-03-11 (18 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1822394/+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 1888703] Re: After the latest update on 7/21/20 the screen shows random black horizontal single pixel line stripes in columns about 10-20 pixels long on open windows and icons p
Done - please note that during the execution of the previous step "apport-collect 1888703" I used the 5.3.0-62-generic kernel and not the problematic one 5.4.0-42-generic as the screen is hard to decipher. Please let me know if you would like me to go through the effort again using the problematic kernel (i.e. 5.4.0-42-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/1888703 Title: After the latest update on 7/21/20 the screen shows random black horizontal single pixel line stripes in columns about 10-20 pixels long on open windows and icons presented on the desktop. Status in linux package in Ubuntu: Confirmed Bug description: Everything else works well in the system except for this issue. See attached picture for details. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus (not installed) ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 Uname: Linux 5.4.0-42-generic i686 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: i386 CurrentDesktop: MATE Date: Thu Jul 23 08:14:26 2020 InstallationDate: Installed on 2019-12-08 (228 days ago) InstallationMedia: Ubuntu-MATE 18.04.3 LTS "Bionic Beaver" - Release i386 (20190805) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mauro 2001 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-12-08 (229 days ago) InstallationMedia: Ubuntu-MATE 18.04.3 LTS "Bionic Beaver" - Release i386 (20190805) MachineType: IBM 2373C96 Package: linux (not installed) PccardctlIdent: Socket 0: no product info available Socket 1: no product info available PccardctlStatus: Socket 0: no card Socket 1: no card ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic root=UUID=14567323-8391-4f6b-9169-c617d286cadb ro forcepae quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-62-generic N/A linux-backports-modules-5.3.0-62-generic N/A linux-firmware1.173.19 RfKill: 0: tpacpi_bluetooth_sw: Bluetooth Soft blocked: yes Hard blocked: no Tags: bionic Uname: Linux 5.3.0-62-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/18/2007 dmi.bios.vendor: IBM dmi.bios.version: 1RETDRWW (3.23 ) dmi.board.name: 2373C96 dmi.board.vendor: IBM dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: IBM dmi.chassis.version: Not Available dmi.modalias: dmi:bvnIBM:bvr1RETDRWW(3.23):bd06/18/2007:svnIBM:pn2373C96:pvrThinkPadT42p:rvnIBM:rn2373C96:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable: dmi.product.name: 2373C96 dmi.product.version: ThinkPad T42p dmi.sys.vendor: IBM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888703/+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 1882624] Re: nested kvm doesn't work
The issue still exist on 4.15.0-1092-azure, probably I just verify the basic nested vm scenario against 4.15.0-1091-azure, will double check. -- 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/1882624 Title: nested kvm doesn't work Status in linux-azure package in Ubuntu: New Bug description: Create VM on Azure using Canonical UbuntuServer 14.04.5-LTS latest using size Standard E4s v3 Enable private-ppa canonical-kernel-esm Install kernel linux-azure, reboot VM, kernel version 4.15.0-1084-azure Install qemu-kvm, download https://eosgnestedstorage.blob.core.windows.net/images/nested- ubuntu-4.15.0-23-generic.qcow2 Launch nested VM using command qemu-system-x86_64 -smp 2 -m 2048 -hda /mnt/resource/nested.qcow2 -display none -device e1000,netdev=user.0 -netdev user,id=user.0,hostfwd=tcp::60022-:22 -enable-kvm -daemonize Expected ssh -p 60022 nesteduser@localhost will ask password to login We can't connect to it, see below call trace in dmesg qemu-kvm version doesn't change after kernel upgraded. 2.0.0+dfsg-2ubuntu1.46 [ 53.420589] hv_balloon: Max. dynamic memory size: 32768 MB [ 60.928772] L1TF CPU bug present and SMT on, data leak possible. See CVE-2018-3646 and https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/l1tf.html for details. [ 60.940895] kvm: SMP vm created on host with unstable TSC; guest TSC will not be reliable [ 60.967454] BUG: unable to handle kernel paging request at 56b8 [ 60.971140] IP: vmx_vcpu_run+0x3ed/0xbc0 [kvm_intel] [ 60.971140] PGD 0 P4D 0 [ 60.971140] Oops: [#1] SMP PTI [ 60.971140] Modules linked in: nf_conntrack_ipv4 nf_defrag_ipv4 xt_owner iptable_security xt_conntrack nf_conntrack libcrc32c ip_tables x_tables udf crc_itu_t dm_crypt joydev hid_generic kvm_intel kvm irqbypass hid_hyperv hid hyperv_keyboard hv_balloon serio_raw crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd glue_helper cryptd hyperv_fb cfbfillrect pata_acpi cfbimgblt cfbcopyarea hv_netvsc hv_utils [ 60.971140] CPU: 2 PID: 1903 Comm: qemu-system-x86 Not tainted 4.15.0-1084-azure #94~14.04.1-Ubuntu [ 60.971140] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090007 06/02/2017 [ 60.971140] RIP: 0010:vmx_vcpu_run+0x3ed/0xbc0 [kvm_intel] [ 60.971140] RSP: 0018:a44847a53cc0 EFLAGS: 00010002 [ 60.971140] RAX: RBX: RCX: [ 61.020070] RDX: 6c14 RSI: RDI: [ 61.020070] RBP: a44847a53d10 R08: R09: [ 61.020070] R10: R11: R12: [ 61.020070] R13: R14: R15: [ 61.020070] FS: 7f753bba4700() GS:8fefdd68() knlGS: [ 61.020070] CS: 0010 DS: ES: CR0: 80050033 [ 61.020070] CR2: 56b8 CR3: 000888c42005 CR4: 003726e0 [ 61.020070] Call Trace: [ 61.020070] vcpu_enter_guest+0x909/0x12a0 [kvm] [ 61.020070] kvm_arch_vcpu_ioctl_run+0x2d8/0x3f0 [kvm] [ 61.020070] kvm_vcpu_ioctl+0x2a8/0x630 [kvm] [ 61.020070] ? dequeue_signal+0x3e/0x160 [ 61.020070] ? do_sigtimedwait+0xbd/0x210 [ 61.020070] ? copy_siginfo_to_user+0x12e/0x2d0 [ 61.020070] do_vfs_ioctl+0x9b/0x5f0 [ 61.020070] ? SyS_futex+0x71/0x150 [ 61.020070] SyS_ioctl+0x79/0x90 [ 61.020070] ? _copy_to_user+0x26/0x40 [ 61.020070] do_syscall_64+0x80/0x1e0 [ 61.020070] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [ 61.020070] RIP: 0033:0x7f7545f34ea7 [ 61.020070] RSP: 002b:7f753bba3bd8 EFLAGS: 0246 ORIG_RAX: 0010 [ 61.020070] RAX: ffda RBX: 7f754bbed000 RCX: 7f7545f34ea7 [ 61.020070] RDX: RSI: ae80 RDI: 000c [ 61.020070] RBP: 55c68fd7f160 R08: R09: 0002 [ 61.020070] R10: 0008 R11: 0246 R12: [ 61.020070] R13: R14: 7f753bba49c0 R15: 55c68ee809a0 [ 61.020070] Code: 31 ed 45 31 f6 45 31 ff 0f 20 d0 48 89 81 e0 02 00 00 31 c0 31 db 31 c9 31 d2 31 f6 31 ff 31 ed 5d 5a f6 05 0c c0 01 00 10 74 1b <48> 8b 81 b8 56 00 00 48 8b 40 40 48 8b 80 08 08 00 00 f6 c4 01 [ 61.020070] RIP: vmx_vcpu_run+0x3ed/0xbc0 [kvm_intel] RSP: a44847a53cc0 [ 61.020070] CR2: 56b8 [ 61.020070] ---[ end trace ab52be3a09d557f5 ]--- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1882624/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1888703] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1888703/+attachment/5395597/+files/ProcInterrupts.txt -- 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/1888703 Title: After the latest update on 7/21/20 the screen shows random black horizontal single pixel line stripes in columns about 10-20 pixels long on open windows and icons presented on the desktop. Status in linux package in Ubuntu: Confirmed Bug description: Everything else works well in the system except for this issue. See attached picture for details. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus (not installed) ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 Uname: Linux 5.4.0-42-generic i686 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: i386 CurrentDesktop: MATE Date: Thu Jul 23 08:14:26 2020 InstallationDate: Installed on 2019-12-08 (228 days ago) InstallationMedia: Ubuntu-MATE 18.04.3 LTS "Bionic Beaver" - Release i386 (20190805) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mauro 2001 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-12-08 (229 days ago) InstallationMedia: Ubuntu-MATE 18.04.3 LTS "Bionic Beaver" - Release i386 (20190805) MachineType: IBM 2373C96 Package: linux (not installed) PccardctlIdent: Socket 0: no product info available Socket 1: no product info available PccardctlStatus: Socket 0: no card Socket 1: no card ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic root=UUID=14567323-8391-4f6b-9169-c617d286cadb ro forcepae quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-62-generic N/A linux-backports-modules-5.3.0-62-generic N/A linux-firmware1.173.19 RfKill: 0: tpacpi_bluetooth_sw: Bluetooth Soft blocked: yes Hard blocked: no Tags: bionic Uname: Linux 5.3.0-62-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/18/2007 dmi.bios.vendor: IBM dmi.bios.version: 1RETDRWW (3.23 ) dmi.board.name: 2373C96 dmi.board.vendor: IBM dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: IBM dmi.chassis.version: Not Available dmi.modalias: dmi:bvnIBM:bvr1RETDRWW(3.23):bd06/18/2007:svnIBM:pn2373C96:pvrThinkPadT42p:rvnIBM:rn2373C96:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable: dmi.product.name: 2373C96 dmi.product.version: ThinkPad T42p dmi.sys.vendor: IBM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888703/+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 1888703] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1888703/+attachment/5395593/+files/Lsusb.txt -- 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/1888703 Title: After the latest update on 7/21/20 the screen shows random black horizontal single pixel line stripes in columns about 10-20 pixels long on open windows and icons presented on the desktop. Status in linux package in Ubuntu: Confirmed Bug description: Everything else works well in the system except for this issue. See attached picture for details. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus (not installed) ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 Uname: Linux 5.4.0-42-generic i686 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: i386 CurrentDesktop: MATE Date: Thu Jul 23 08:14:26 2020 InstallationDate: Installed on 2019-12-08 (228 days ago) InstallationMedia: Ubuntu-MATE 18.04.3 LTS "Bionic Beaver" - Release i386 (20190805) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mauro 2001 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-12-08 (229 days ago) InstallationMedia: Ubuntu-MATE 18.04.3 LTS "Bionic Beaver" - Release i386 (20190805) MachineType: IBM 2373C96 Package: linux (not installed) PccardctlIdent: Socket 0: no product info available Socket 1: no product info available PccardctlStatus: Socket 0: no card Socket 1: no card ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic root=UUID=14567323-8391-4f6b-9169-c617d286cadb ro forcepae quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-62-generic N/A linux-backports-modules-5.3.0-62-generic N/A linux-firmware1.173.19 RfKill: 0: tpacpi_bluetooth_sw: Bluetooth Soft blocked: yes Hard blocked: no Tags: bionic Uname: Linux 5.3.0-62-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/18/2007 dmi.bios.vendor: IBM dmi.bios.version: 1RETDRWW (3.23 ) dmi.board.name: 2373C96 dmi.board.vendor: IBM dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: IBM dmi.chassis.version: Not Available dmi.modalias: dmi:bvnIBM:bvr1RETDRWW(3.23):bd06/18/2007:svnIBM:pn2373C96:pvrThinkPadT42p:rvnIBM:rn2373C96:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable: dmi.product.name: 2373C96 dmi.product.version: ThinkPad T42p dmi.sys.vendor: IBM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888703/+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 1888703] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1888703/+attachment/5395590/+files/CurrentDmesg.txt -- 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/1888703 Title: After the latest update on 7/21/20 the screen shows random black horizontal single pixel line stripes in columns about 10-20 pixels long on open windows and icons presented on the desktop. Status in linux package in Ubuntu: Confirmed Bug description: Everything else works well in the system except for this issue. See attached picture for details. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus (not installed) ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 Uname: Linux 5.4.0-42-generic i686 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: i386 CurrentDesktop: MATE Date: Thu Jul 23 08:14:26 2020 InstallationDate: Installed on 2019-12-08 (228 days ago) InstallationMedia: Ubuntu-MATE 18.04.3 LTS "Bionic Beaver" - Release i386 (20190805) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mauro 2001 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-12-08 (229 days ago) InstallationMedia: Ubuntu-MATE 18.04.3 LTS "Bionic Beaver" - Release i386 (20190805) MachineType: IBM 2373C96 Package: linux (not installed) PccardctlIdent: Socket 0: no product info available Socket 1: no product info available PccardctlStatus: Socket 0: no card Socket 1: no card ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic root=UUID=14567323-8391-4f6b-9169-c617d286cadb ro forcepae quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-62-generic N/A linux-backports-modules-5.3.0-62-generic N/A linux-firmware1.173.19 RfKill: 0: tpacpi_bluetooth_sw: Bluetooth Soft blocked: yes Hard blocked: no Tags: bionic Uname: Linux 5.3.0-62-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/18/2007 dmi.bios.vendor: IBM dmi.bios.version: 1RETDRWW (3.23 ) dmi.board.name: 2373C96 dmi.board.vendor: IBM dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: IBM dmi.chassis.version: Not Available dmi.modalias: dmi:bvnIBM:bvr1RETDRWW(3.23):bd06/18/2007:svnIBM:pn2373C96:pvrThinkPadT42p:rvnIBM:rn2373C96:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable: dmi.product.name: 2373C96 dmi.product.version: ThinkPad T42p dmi.sys.vendor: IBM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888703/+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 1888703] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1888703/+attachment/5395600/+files/UdevDb.txt -- 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/1888703 Title: After the latest update on 7/21/20 the screen shows random black horizontal single pixel line stripes in columns about 10-20 pixels long on open windows and icons presented on the desktop. Status in linux package in Ubuntu: Confirmed Bug description: Everything else works well in the system except for this issue. See attached picture for details. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus (not installed) ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 Uname: Linux 5.4.0-42-generic i686 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: i386 CurrentDesktop: MATE Date: Thu Jul 23 08:14:26 2020 InstallationDate: Installed on 2019-12-08 (228 days ago) InstallationMedia: Ubuntu-MATE 18.04.3 LTS "Bionic Beaver" - Release i386 (20190805) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mauro 2001 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-12-08 (229 days ago) InstallationMedia: Ubuntu-MATE 18.04.3 LTS "Bionic Beaver" - Release i386 (20190805) MachineType: IBM 2373C96 Package: linux (not installed) PccardctlIdent: Socket 0: no product info available Socket 1: no product info available PccardctlStatus: Socket 0: no card Socket 1: no card ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic root=UUID=14567323-8391-4f6b-9169-c617d286cadb ro forcepae quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-62-generic N/A linux-backports-modules-5.3.0-62-generic N/A linux-firmware1.173.19 RfKill: 0: tpacpi_bluetooth_sw: Bluetooth Soft blocked: yes Hard blocked: no Tags: bionic Uname: Linux 5.3.0-62-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/18/2007 dmi.bios.vendor: IBM dmi.bios.version: 1RETDRWW (3.23 ) dmi.board.name: 2373C96 dmi.board.vendor: IBM dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: IBM dmi.chassis.version: Not Available dmi.modalias: dmi:bvnIBM:bvr1RETDRWW(3.23):bd06/18/2007:svnIBM:pn2373C96:pvrThinkPadT42p:rvnIBM:rn2373C96:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable: dmi.product.name: 2373C96 dmi.product.version: ThinkPad T42p dmi.sys.vendor: IBM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888703/+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 1888703] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1888703/+attachment/5395596/+files/ProcEnviron.txt -- 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/1888703 Title: After the latest update on 7/21/20 the screen shows random black horizontal single pixel line stripes in columns about 10-20 pixels long on open windows and icons presented on the desktop. Status in linux package in Ubuntu: Confirmed Bug description: Everything else works well in the system except for this issue. See attached picture for details. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus (not installed) ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 Uname: Linux 5.4.0-42-generic i686 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: i386 CurrentDesktop: MATE Date: Thu Jul 23 08:14:26 2020 InstallationDate: Installed on 2019-12-08 (228 days ago) InstallationMedia: Ubuntu-MATE 18.04.3 LTS "Bionic Beaver" - Release i386 (20190805) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mauro 2001 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-12-08 (229 days ago) InstallationMedia: Ubuntu-MATE 18.04.3 LTS "Bionic Beaver" - Release i386 (20190805) MachineType: IBM 2373C96 Package: linux (not installed) PccardctlIdent: Socket 0: no product info available Socket 1: no product info available PccardctlStatus: Socket 0: no card Socket 1: no card ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic root=UUID=14567323-8391-4f6b-9169-c617d286cadb ro forcepae quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-62-generic N/A linux-backports-modules-5.3.0-62-generic N/A linux-firmware1.173.19 RfKill: 0: tpacpi_bluetooth_sw: Bluetooth Soft blocked: yes Hard blocked: no Tags: bionic Uname: Linux 5.3.0-62-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/18/2007 dmi.bios.vendor: IBM dmi.bios.version: 1RETDRWW (3.23 ) dmi.board.name: 2373C96 dmi.board.vendor: IBM dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: IBM dmi.chassis.version: Not Available dmi.modalias: dmi:bvnIBM:bvr1RETDRWW(3.23):bd06/18/2007:svnIBM:pn2373C96:pvrThinkPadT42p:rvnIBM:rn2373C96:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable: dmi.product.name: 2373C96 dmi.product.version: ThinkPad T42p dmi.sys.vendor: IBM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888703/+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 1888703] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1888703/+attachment/5395591/+files/IwConfig.txt -- 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/1888703 Title: After the latest update on 7/21/20 the screen shows random black horizontal single pixel line stripes in columns about 10-20 pixels long on open windows and icons presented on the desktop. Status in linux package in Ubuntu: Confirmed Bug description: Everything else works well in the system except for this issue. See attached picture for details. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus (not installed) ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 Uname: Linux 5.4.0-42-generic i686 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: i386 CurrentDesktop: MATE Date: Thu Jul 23 08:14:26 2020 InstallationDate: Installed on 2019-12-08 (228 days ago) InstallationMedia: Ubuntu-MATE 18.04.3 LTS "Bionic Beaver" - Release i386 (20190805) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mauro 2001 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-12-08 (229 days ago) InstallationMedia: Ubuntu-MATE 18.04.3 LTS "Bionic Beaver" - Release i386 (20190805) MachineType: IBM 2373C96 Package: linux (not installed) PccardctlIdent: Socket 0: no product info available Socket 1: no product info available PccardctlStatus: Socket 0: no card Socket 1: no card ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic root=UUID=14567323-8391-4f6b-9169-c617d286cadb ro forcepae quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-62-generic N/A linux-backports-modules-5.3.0-62-generic N/A linux-firmware1.173.19 RfKill: 0: tpacpi_bluetooth_sw: Bluetooth Soft blocked: yes Hard blocked: no Tags: bionic Uname: Linux 5.3.0-62-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/18/2007 dmi.bios.vendor: IBM dmi.bios.version: 1RETDRWW (3.23 ) dmi.board.name: 2373C96 dmi.board.vendor: IBM dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: IBM dmi.chassis.version: Not Available dmi.modalias: dmi:bvnIBM:bvr1RETDRWW(3.23):bd06/18/2007:svnIBM:pn2373C96:pvrThinkPadT42p:rvnIBM:rn2373C96:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable: dmi.product.name: 2373C96 dmi.product.version: ThinkPad T42p dmi.sys.vendor: IBM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888703/+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 1888703] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1888703/+attachment/5395599/+files/PulseList.txt -- 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/1888703 Title: After the latest update on 7/21/20 the screen shows random black horizontal single pixel line stripes in columns about 10-20 pixels long on open windows and icons presented on the desktop. Status in linux package in Ubuntu: Confirmed Bug description: Everything else works well in the system except for this issue. See attached picture for details. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus (not installed) ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 Uname: Linux 5.4.0-42-generic i686 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: i386 CurrentDesktop: MATE Date: Thu Jul 23 08:14:26 2020 InstallationDate: Installed on 2019-12-08 (228 days ago) InstallationMedia: Ubuntu-MATE 18.04.3 LTS "Bionic Beaver" - Release i386 (20190805) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mauro 2001 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-12-08 (229 days ago) InstallationMedia: Ubuntu-MATE 18.04.3 LTS "Bionic Beaver" - Release i386 (20190805) MachineType: IBM 2373C96 Package: linux (not installed) PccardctlIdent: Socket 0: no product info available Socket 1: no product info available PccardctlStatus: Socket 0: no card Socket 1: no card ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic root=UUID=14567323-8391-4f6b-9169-c617d286cadb ro forcepae quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-62-generic N/A linux-backports-modules-5.3.0-62-generic N/A linux-firmware1.173.19 RfKill: 0: tpacpi_bluetooth_sw: Bluetooth Soft blocked: yes Hard blocked: no Tags: bionic Uname: Linux 5.3.0-62-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/18/2007 dmi.bios.vendor: IBM dmi.bios.version: 1RETDRWW (3.23 ) dmi.board.name: 2373C96 dmi.board.vendor: IBM dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: IBM dmi.chassis.version: Not Available dmi.modalias: dmi:bvnIBM:bvr1RETDRWW(3.23):bd06/18/2007:svnIBM:pn2373C96:pvrThinkPadT42p:rvnIBM:rn2373C96:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable: dmi.product.name: 2373C96 dmi.product.version: ThinkPad T42p dmi.sys.vendor: IBM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888703/+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 1888703] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1888703/+attachment/5395601/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1888703 Title: After the latest update on 7/21/20 the screen shows random black horizontal single pixel line stripes in columns about 10-20 pixels long on open windows and icons presented on the desktop. Status in linux package in Ubuntu: Confirmed Bug description: Everything else works well in the system except for this issue. See attached picture for details. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus (not installed) ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 Uname: Linux 5.4.0-42-generic i686 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: i386 CurrentDesktop: MATE Date: Thu Jul 23 08:14:26 2020 InstallationDate: Installed on 2019-12-08 (228 days ago) InstallationMedia: Ubuntu-MATE 18.04.3 LTS "Bionic Beaver" - Release i386 (20190805) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mauro 2001 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-12-08 (229 days ago) InstallationMedia: Ubuntu-MATE 18.04.3 LTS "Bionic Beaver" - Release i386 (20190805) MachineType: IBM 2373C96 Package: linux (not installed) PccardctlIdent: Socket 0: no product info available Socket 1: no product info available PccardctlStatus: Socket 0: no card Socket 1: no card ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic root=UUID=14567323-8391-4f6b-9169-c617d286cadb ro forcepae quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-62-generic N/A linux-backports-modules-5.3.0-62-generic N/A linux-firmware1.173.19 RfKill: 0: tpacpi_bluetooth_sw: Bluetooth Soft blocked: yes Hard blocked: no Tags: bionic Uname: Linux 5.3.0-62-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/18/2007 dmi.bios.vendor: IBM dmi.bios.version: 1RETDRWW (3.23 ) dmi.board.name: 2373C96 dmi.board.vendor: IBM dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: IBM dmi.chassis.version: Not Available dmi.modalias: dmi:bvnIBM:bvr1RETDRWW(3.23):bd06/18/2007:svnIBM:pn2373C96:pvrThinkPadT42p:rvnIBM:rn2373C96:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable: dmi.product.name: 2373C96 dmi.product.version: ThinkPad T42p dmi.sys.vendor: IBM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888703/+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 1888703] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1888703/+attachment/5395592/+files/Lspci.txt -- 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/1888703 Title: After the latest update on 7/21/20 the screen shows random black horizontal single pixel line stripes in columns about 10-20 pixels long on open windows and icons presented on the desktop. Status in linux package in Ubuntu: Confirmed Bug description: Everything else works well in the system except for this issue. See attached picture for details. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus (not installed) ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 Uname: Linux 5.4.0-42-generic i686 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: i386 CurrentDesktop: MATE Date: Thu Jul 23 08:14:26 2020 InstallationDate: Installed on 2019-12-08 (228 days ago) InstallationMedia: Ubuntu-MATE 18.04.3 LTS "Bionic Beaver" - Release i386 (20190805) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mauro 2001 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-12-08 (229 days ago) InstallationMedia: Ubuntu-MATE 18.04.3 LTS "Bionic Beaver" - Release i386 (20190805) MachineType: IBM 2373C96 Package: linux (not installed) PccardctlIdent: Socket 0: no product info available Socket 1: no product info available PccardctlStatus: Socket 0: no card Socket 1: no card ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic root=UUID=14567323-8391-4f6b-9169-c617d286cadb ro forcepae quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-62-generic N/A linux-backports-modules-5.3.0-62-generic N/A linux-firmware1.173.19 RfKill: 0: tpacpi_bluetooth_sw: Bluetooth Soft blocked: yes Hard blocked: no Tags: bionic Uname: Linux 5.3.0-62-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/18/2007 dmi.bios.vendor: IBM dmi.bios.version: 1RETDRWW (3.23 ) dmi.board.name: 2373C96 dmi.board.vendor: IBM dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: IBM dmi.chassis.version: Not Available dmi.modalias: dmi:bvnIBM:bvr1RETDRWW(3.23):bd06/18/2007:svnIBM:pn2373C96:pvrThinkPadT42p:rvnIBM:rn2373C96:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable: dmi.product.name: 2373C96 dmi.product.version: ThinkPad T42p dmi.sys.vendor: IBM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888703/+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 1888703] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1888703/+attachment/5395589/+files/CRDA.txt -- 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/1888703 Title: After the latest update on 7/21/20 the screen shows random black horizontal single pixel line stripes in columns about 10-20 pixels long on open windows and icons presented on the desktop. Status in linux package in Ubuntu: Confirmed Bug description: Everything else works well in the system except for this issue. See attached picture for details. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus (not installed) ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 Uname: Linux 5.4.0-42-generic i686 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: i386 CurrentDesktop: MATE Date: Thu Jul 23 08:14:26 2020 InstallationDate: Installed on 2019-12-08 (228 days ago) InstallationMedia: Ubuntu-MATE 18.04.3 LTS "Bionic Beaver" - Release i386 (20190805) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mauro 2001 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-12-08 (229 days ago) InstallationMedia: Ubuntu-MATE 18.04.3 LTS "Bionic Beaver" - Release i386 (20190805) MachineType: IBM 2373C96 Package: linux (not installed) PccardctlIdent: Socket 0: no product info available Socket 1: no product info available PccardctlStatus: Socket 0: no card Socket 1: no card ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic root=UUID=14567323-8391-4f6b-9169-c617d286cadb ro forcepae quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-62-generic N/A linux-backports-modules-5.3.0-62-generic N/A linux-firmware1.173.19 RfKill: 0: tpacpi_bluetooth_sw: Bluetooth Soft blocked: yes Hard blocked: no Tags: bionic Uname: Linux 5.3.0-62-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/18/2007 dmi.bios.vendor: IBM dmi.bios.version: 1RETDRWW (3.23 ) dmi.board.name: 2373C96 dmi.board.vendor: IBM dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: IBM dmi.chassis.version: Not Available dmi.modalias: dmi:bvnIBM:bvr1RETDRWW(3.23):bd06/18/2007:svnIBM:pn2373C96:pvrThinkPadT42p:rvnIBM:rn2373C96:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable: dmi.product.name: 2373C96 dmi.product.version: ThinkPad T42p dmi.sys.vendor: IBM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888703/+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 1888703] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1888703/+attachment/5395594/+files/ProcCpuinfo.txt -- 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/1888703 Title: After the latest update on 7/21/20 the screen shows random black horizontal single pixel line stripes in columns about 10-20 pixels long on open windows and icons presented on the desktop. Status in linux package in Ubuntu: Confirmed Bug description: Everything else works well in the system except for this issue. See attached picture for details. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus (not installed) ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 Uname: Linux 5.4.0-42-generic i686 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: i386 CurrentDesktop: MATE Date: Thu Jul 23 08:14:26 2020 InstallationDate: Installed on 2019-12-08 (228 days ago) InstallationMedia: Ubuntu-MATE 18.04.3 LTS "Bionic Beaver" - Release i386 (20190805) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mauro 2001 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-12-08 (229 days ago) InstallationMedia: Ubuntu-MATE 18.04.3 LTS "Bionic Beaver" - Release i386 (20190805) MachineType: IBM 2373C96 Package: linux (not installed) PccardctlIdent: Socket 0: no product info available Socket 1: no product info available PccardctlStatus: Socket 0: no card Socket 1: no card ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic root=UUID=14567323-8391-4f6b-9169-c617d286cadb ro forcepae quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-62-generic N/A linux-backports-modules-5.3.0-62-generic N/A linux-firmware1.173.19 RfKill: 0: tpacpi_bluetooth_sw: Bluetooth Soft blocked: yes Hard blocked: no Tags: bionic Uname: Linux 5.3.0-62-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/18/2007 dmi.bios.vendor: IBM dmi.bios.version: 1RETDRWW (3.23 ) dmi.board.name: 2373C96 dmi.board.vendor: IBM dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: IBM dmi.chassis.version: Not Available dmi.modalias: dmi:bvnIBM:bvr1RETDRWW(3.23):bd06/18/2007:svnIBM:pn2373C96:pvrThinkPadT42p:rvnIBM:rn2373C96:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable: dmi.product.name: 2373C96 dmi.product.version: ThinkPad T42p dmi.sys.vendor: IBM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888703/+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 1888703] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1888703/+attachment/5395598/+files/ProcModules.txt -- 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/1888703 Title: After the latest update on 7/21/20 the screen shows random black horizontal single pixel line stripes in columns about 10-20 pixels long on open windows and icons presented on the desktop. Status in linux package in Ubuntu: Confirmed Bug description: Everything else works well in the system except for this issue. See attached picture for details. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus (not installed) ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 Uname: Linux 5.4.0-42-generic i686 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: i386 CurrentDesktop: MATE Date: Thu Jul 23 08:14:26 2020 InstallationDate: Installed on 2019-12-08 (228 days ago) InstallationMedia: Ubuntu-MATE 18.04.3 LTS "Bionic Beaver" - Release i386 (20190805) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mauro 2001 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-12-08 (229 days ago) InstallationMedia: Ubuntu-MATE 18.04.3 LTS "Bionic Beaver" - Release i386 (20190805) MachineType: IBM 2373C96 Package: linux (not installed) PccardctlIdent: Socket 0: no product info available Socket 1: no product info available PccardctlStatus: Socket 0: no card Socket 1: no card ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic root=UUID=14567323-8391-4f6b-9169-c617d286cadb ro forcepae quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-62-generic N/A linux-backports-modules-5.3.0-62-generic N/A linux-firmware1.173.19 RfKill: 0: tpacpi_bluetooth_sw: Bluetooth Soft blocked: yes Hard blocked: no Tags: bionic Uname: Linux 5.3.0-62-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/18/2007 dmi.bios.vendor: IBM dmi.bios.version: 1RETDRWW (3.23 ) dmi.board.name: 2373C96 dmi.board.vendor: IBM dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: IBM dmi.chassis.version: Not Available dmi.modalias: dmi:bvnIBM:bvr1RETDRWW(3.23):bd06/18/2007:svnIBM:pn2373C96:pvrThinkPadT42p:rvnIBM:rn2373C96:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable: dmi.product.name: 2373C96 dmi.product.version: ThinkPad T42p dmi.sys.vendor: IBM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888703/+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 1888703] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1888703/+attachment/5395595/+files/ProcCpuinfoMinimal.txt -- 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/1888703 Title: After the latest update on 7/21/20 the screen shows random black horizontal single pixel line stripes in columns about 10-20 pixels long on open windows and icons presented on the desktop. Status in linux package in Ubuntu: Confirmed Bug description: Everything else works well in the system except for this issue. See attached picture for details. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus (not installed) ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 Uname: Linux 5.4.0-42-generic i686 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: i386 CurrentDesktop: MATE Date: Thu Jul 23 08:14:26 2020 InstallationDate: Installed on 2019-12-08 (228 days ago) InstallationMedia: Ubuntu-MATE 18.04.3 LTS "Bionic Beaver" - Release i386 (20190805) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mauro 2001 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-12-08 (229 days ago) InstallationMedia: Ubuntu-MATE 18.04.3 LTS "Bionic Beaver" - Release i386 (20190805) MachineType: IBM 2373C96 Package: linux (not installed) PccardctlIdent: Socket 0: no product info available Socket 1: no product info available PccardctlStatus: Socket 0: no card Socket 1: no card ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic root=UUID=14567323-8391-4f6b-9169-c617d286cadb ro forcepae quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-62-generic N/A linux-backports-modules-5.3.0-62-generic N/A linux-firmware1.173.19 RfKill: 0: tpacpi_bluetooth_sw: Bluetooth Soft blocked: yes Hard blocked: no Tags: bionic Uname: Linux 5.3.0-62-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/18/2007 dmi.bios.vendor: IBM dmi.bios.version: 1RETDRWW (3.23 ) dmi.board.name: 2373C96 dmi.board.vendor: IBM dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: IBM dmi.chassis.version: Not Available dmi.modalias: dmi:bvnIBM:bvr1RETDRWW(3.23):bd06/18/2007:svnIBM:pn2373C96:pvrThinkPadT42p:rvnIBM:rn2373C96:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable: dmi.product.name: 2373C96 dmi.product.version: ThinkPad T42p dmi.sys.vendor: IBM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888703/+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 1888703] Re: After the latest update on 7/21/20 the screen shows random black horizontal single pixel line stripes in columns about 10-20 pixels long on open windows and icons p
apport information ** Tags added: apport-collected ** Description changed: Everything else works well in the system except for this issue. See attached picture for details. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus (not installed) ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 Uname: Linux 5.4.0-42-generic i686 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: i386 CurrentDesktop: MATE Date: Thu Jul 23 08:14:26 2020 InstallationDate: Installed on 2019-12-08 (228 days ago) InstallationMedia: Ubuntu-MATE 18.04.3 LTS "Bionic Beaver" - Release i386 (20190805) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.15 + Architecture: i386 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: mauro 2001 F pulseaudio + CurrentDesktop: MATE + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2019-12-08 (229 days ago) + InstallationMedia: Ubuntu-MATE 18.04.3 LTS "Bionic Beaver" - Release i386 (20190805) + MachineType: IBM 2373C96 + Package: linux (not installed) + PccardctlIdent: + Socket 0: +no product info available + Socket 1: +no product info available + PccardctlStatus: + Socket 0: +no card + Socket 1: +no card + ProcFB: 0 radeondrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic root=UUID=14567323-8391-4f6b-9169-c617d286cadb ro forcepae quiet splash vt.handoff=1 + ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18 + RelatedPackageVersions: + linux-restricted-modules-5.3.0-62-generic N/A + linux-backports-modules-5.3.0-62-generic N/A + linux-firmware1.173.19 + RfKill: + 0: tpacpi_bluetooth_sw: Bluetooth + Soft blocked: yes + Hard blocked: no + Tags: bionic + Uname: Linux 5.3.0-62-generic i686 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 06/18/2007 + dmi.bios.vendor: IBM + dmi.bios.version: 1RETDRWW (3.23 ) + dmi.board.name: 2373C96 + dmi.board.vendor: IBM + dmi.board.version: Not Available + dmi.chassis.asset.tag: No Asset Information + dmi.chassis.type: 10 + dmi.chassis.vendor: IBM + dmi.chassis.version: Not Available + dmi.modalias: dmi:bvnIBM:bvr1RETDRWW(3.23):bd06/18/2007:svnIBM:pn2373C96:pvrThinkPadT42p:rvnIBM:rn2373C96:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable: + dmi.product.name: 2373C96 + dmi.product.version: ThinkPad T42p + dmi.sys.vendor: IBM ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1888703/+attachment/5395588/+files/AlsaInfo.txt -- 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/1888703 Title: After the latest update on 7/21/20 the screen shows random black horizontal single pixel line stripes in columns about 10-20 pixels long on open windows and icons presented on the desktop. Status in linux package in Ubuntu: Confirmed Bug description: Everything else works well in the system except for this issue. See attached picture for details. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus (not installed) ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 Uname: Linux 5.4.0-42-generic i686 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: i386 CurrentDesktop: MATE Date: Thu Jul 23 08:14:26 2020 InstallationDate: Installed on 2019-12-08 (228 days ago) InstallationMedia: Ubuntu-MATE 18.04.3 LTS "Bionic Beaver" - Release i386 (20190805) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mauro 2001 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-12-08 (229 days ago) InstallationMedia: Ubuntu-MATE 18.04.3 LTS "Bionic Beaver" - Release i386 (20190805) MachineType: IBM 2373C96 Package: linux (not installed) PccardctlIdent: Socket 0: no product info available Socket 1: no product info available PccardctlStatus: Socket 0: no card Socket 1: no card ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic root=UUID=14567323-8391-4f6b-9169-c617d286cadb ro forcepae quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-62-generic N/A linux-backports-modules-5.3.0-62-generic N/A linux-firmware1.173.19 RfKill: 0: tpacpi_bluetooth_sw: Bluetooth Soft blocked: yes Hard blocked: no Tags: bionic Uname: Linux
[Kernel-packages] [Bug 1835660] Re: initramfs unpacking failed
Ubuntu 20.04 for me the problem started after upgrading to the kernel version 5.4.0-42-generic, I noticed it because the boot up failed once. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835660 Title: initramfs unpacking failed Status in initramfs-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: "initramfs unpacking failed: Decoding failed", message appears on boot up. If I "update-initramfs" using gzip instead of lz, then boot up passes without decoding failed message. --- However, we currently believe that the decoding error reported in dmesg is actually harmless and has no impact on usability on the system. Switching from lz4 to gzip compression, simply papers over the warning, without any benefits, and slows down boot. Kernel should be fixed to correctly parse lz4 compressed initrds, or at least lower the warning, to not be user visible as an error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1835660/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886814] Re: posix_spawn usage in gnu make causes failures on s390x
--- Comment From s...@de.ibm.com 2020-07-24 10:47 EDT---
I've found the relevant code. It's the flatpak package. For a test on my s390x
machine, I've just changed the check from arg 0 to arg 1:
diff -uNr ./flatpak-1.6.3/common/flatpak-run.orig.c
./flatpak-1.6.3/common/flatpak-run.c
--- ./flatpak-1.6.3/common/flatpak-run.orig.c 2020-07-24 15:57:17.583312438
+0200
+++ ./flatpak-1.6.3/common/flatpak-run.c2020-07-24 16:23:35.880965987
+0200
@@ -2632,7 +2632,7 @@
{SCMP_SYS (unshare)},
{SCMP_SYS (mount)},
{SCMP_SYS (pivot_root)},
-{SCMP_SYS (clone), _A0 (SCMP_CMP_MASKED_EQ, CLONE_NEWUSER,
CLONE_NEWUSER)},
+{SCMP_SYS (clone), _A1 (SCMP_CMP_MASKED_EQ, CLONE_NEWUSER,
CLONE_NEWUSER)},
/* Don't allow faking input to the controlling tty (CVE-2017-5226) */
{SCMP_SYS (ioctl), _A1 (SCMP_CMP_MASKED_EQ, 0xu, (int) TIOCSTI)},
Note:
I've also looked into the "groovy" flatpak (1.8.1-1) source-code. There the
code looks the same.
Afterwards, the seccomp filter looks like:
line CODE JT JF K
=
: 0x20 0x00 0x00 0x0004 A = arch
0001: 0x15 0x00 0x1f 0x8016 if (A != ARCH_S390X) goto 0033
0002: 0x20 0x00 0x00 0x A = sys_number
0003: 0x15 0x1c 0x00 0x0015 if (A == mount) goto 0032
0004: 0x15 0x1b 0x00 0x0033 if (A == acct) goto 0032
0005: 0x15 0x1a 0x00 0x0056 if (A == uselib) goto 0032
0006: 0x15 0x19 0x00 0x0067 if (A == syslog) goto 0032
0007: 0x15 0x18 0x00 0x0083 if (A == quotactl) goto 0032
0008: 0x15 0x17 0x00 0x00d9 if (A == pivot_root) goto 0032
0009: 0x15 0x16 0x00 0x010c if (A == mbind) goto 0032
0010: 0x15 0x15 0x00 0x010d if (A == get_mempolicy) goto 0032
0011: 0x15 0x14 0x00 0x010e if (A == set_mempolicy) goto 0032
0012: 0x15 0x13 0x00 0x0116 if (A == add_key) goto 0032
0013: 0x15 0x12 0x00 0x0117 if (A == request_key) goto 0032
0014: 0x15 0x11 0x00 0x0118 if (A == keyctl) goto 0032
0015: 0x15 0x10 0x00 0x011f if (A == migrate_pages) goto 0032
0016: 0x15 0x0f 0x00 0x012f if (A == unshare) goto 0032
0017: 0x15 0x0e 0x00 0x0136 if (A == move_pages) goto 0032
0018: 0x15 0x00 0x05 0x0036 if (A != ioctl) goto 0024
0019: 0x20 0x00 0x00 0x0018 A = cmd # ioctl(fd, cmd, arg)
0020: 0x54 0x00 0x00 0x A &= 0x0
0021: 0x15 0x00 0x09 0x if (A != 0) goto 0031
0022: 0x20 0x00 0x00 0x001c A = cmd >> 32 # ioctl(fd, cmd, arg)
0023: 0x15 0x08 0x07 0x5412 if (A == 0x5412) goto 0032 else goto 0031
0024: 0x15 0x00 0x06 0x0078 if (A != clone) goto 0031
0025: 0x20 0x00 0x00 0x0018 A = newsp # clone(clone_flags, newsp,
parent_tidptr, child_tidptr, tls)
0026: 0x54 0x00 0x00 0x A &= 0x0
0027: 0x15 0x00 0x03 0x if (A != 0) goto 0031
0028: 0x20 0x00 0x00 0x001c A = newsp >> 32 # clone(clone_flags, newsp,
parent_tidptr, child_tidptr, tls)
=> Now argument 1 (on s390x: flags; on x86_64: stack-pointer) is checked and
clone works as expected.
0029: 0x54 0x00 0x00 0x1000 A &= 0x1000
0030: 0x15 0x01 0x00 0x1000 if (A == 268435456) goto 0032
0031: 0x06 0x00 0x00 0x7fff return ALLOW
0032: 0x06 0x00 0x00 0x00050001 return ERRNO(1)
0033: 0x06 0x00 0x00 0x return KILL
Then I've rebuild flatpak-builder 1.0.11 and the testsuite runs fine:
Testsuite summary for flatpak-builder 1.0.11
# TOTAL: 19
# PASS: 19
# SKIP: 0
# XFAIL: 0
# FAIL: 0
# XPASS: 0
# ERROR: 0
Please report these insights to the flatpak project. The real fix needs
to use SCMP_A1 at least for SCMP_ARCH_S390X and SCMP_ARCH_S390. Perhaps
there is a further architecture with a different order?
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-5226
--
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/1886814
Title:
posix_spawn usage in gnu make causes failures on s390x
Status in Ubuntu on IBM z Systems:
Triaged
Status in glibc package in Ubuntu:
New
Status in linux package in Ubuntu:
Incomplete
Status in make-dfsg package in Ubuntu:
New
Bug description:
posix_spawn usage in gnu make causes failures on s390x
Recently in gnu-make v4.3 https://paste.ubuntu.com/p/tYhbJFKN76/ it
started to use posix_spawn, instead of fork()/exec().
This has caused failure of an unrelated package flatpak-builder
autopkgtests on s390x only, like so
echo Building
make: echo: Operation not permitted
make: *** [Makefile:2: all] Error 127
Julian Klaude investigated this in-depth. His earlier research also
indicated that this is a heisenbug, if one tries to print to stderr
before printing to stdout, no issue occurs.
We are configuring GNU make to be build
[Kernel-packages] [Bug 1721345] Re: ALC295 codec seems to have Master and PCM channels swapped
I've fixed this issue on my Asus UX550VE, Ubuntu 20.04, kernel 5.4.0-42. I followed Optiman's instructions, which are supposed to "activate bottom speakers" using jack retasking: https://askubuntu.com/questions/973690/my-volume-is-either-max-volume- or-muted-no-middle-ground -- 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/1721345 Title: ALC295 codec seems to have Master and PCM channels swapped Status in linux package in Ubuntu: Confirmed Bug description: When trying to use pulseaudio to control volume on my ASUS Zenbook Pro UX550VE *uses AC295 audio codec) I noticed that pulseuadio is varying the Master ALSA channel. If I vary that channel in alsamixer I get no variation in volume. If I vary the PCM channel instead I get the desired effect that volume buttons should have. Since pulseaudio varies the Master channel by default and does not respect any configuration settings telling it to use other settings, I suggest swapping these two channels so that pulseaudio works out of the box. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: boot/vmlinuz-4.13.0-12-generic] ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dylan 1532 F pulseaudio CurrentDesktop: GNOME Date: Wed Oct 4 19:25:38 2017 HibernationDevice: RESUME=UUID=2b6908b4-d463-4170-9be5-556145c71a0e InstallationDate: Installed on 2017-10-02 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171002) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 13d3:5755 IMC Networks Bus 001 Device 004: ID 04f3:0903 Elan Microelectronics Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX550VE ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic root=UUID=aa3dfd29-caf8-4882-906e-1b31b672d2c2 ro quiet splash threadirqs acpi_osi=! acpi_osi=Linux acpi_backlight=native vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-12-generic N/A linux-backports-modules-4.13.0-12-generic N/A linux-firmware 1.168 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX550VE.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX550VE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX550VE.300:bd06/05/2017:svnASUSTeKCOMPUTERINC.:pnUX550VE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX550VE:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX550VE dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1721345/+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 1886277] Re: Regression on NFS: unable to handle page fault in mempool_alloc_slab
For what it is worth, I also have the same enncryption aes256-cts-hmac- sha1-96 (and same problem). The tickets come from MIT Kerberos on Ubuntu 18.04; the NFS servers are Ubuntu 18.04 using krb5p security option. -- 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/1886277 Title: Regression on NFS: unable to handle page fault in mempool_alloc_slab Status in linux package in Ubuntu: Confirmed Bug description: On kernel 5.4.0-40-generic in focal I'm getting errors like this on several machines with different hardware in the first hour after boot: Jul 04 16:58:32 hostname kernel: BUG: unable to handle page fault for address: 9083e222e632 Jul 04 16:58:32 hostname kernel: #PF: supervisor read access in kernel mode Jul 04 16:58:32 hostname kernel: #PF: error_code(0x) - not-present page Jul 04 16:58:32 hostname kernel: PGD 3ac205067 P4D 3ac205067 PUD 0 Jul 04 16:58:32 hostname kernel: Oops: [#1] SMP NOPTI Jul 04 16:58:32 hostname kernel: CPU: 4 PID: 289 Comm: kworker/u16:4 Tainted: G OE 5.4.0-40-generic #44-Ubuntu Jul 04 16:58:32 hostname kernel: Hardware name: LENOVO 20N2CTO1WW/20N2CTO1WW, BIOS N2IET88W (1.66 ) 04/22/2020 Jul 04 16:58:32 hostname kernel: Workqueue: rpciod rpc_async_schedule [sunrpc] Jul 04 16:58:32 hostname kernel: RIP: 0010:kmem_cache_alloc+0x7e/0x230 Jul 04 16:58:32 hostname kernel: Code: 99 01 00 00 4d 8b 07 65 49 8b 50 08 65 4c 03 05 40 9d 56 44 4d 8b 20 4d 85 e4 0f 84 85 01 00 00 41 8b 47 20 49 8b 3f 4c 01 e0 <48> 8b 18 48 89 c1 49 33 9f 70 01 00 00 4c 89 e0 48 0f c9 48 31 cb Jul 04 16:58:32 hostname kernel: RSP: 0018:bc38c046fcc8 EFLAGS: 00010282 Jul 04 16:58:32 hostname kernel: RAX: 9083e222e632 RBX: RCX: 0002 Jul 04 16:58:32 hostname kernel: RDX: 0009 RSI: 00092800 RDI: 00031fb0 Jul 04 16:58:32 hostname kernel: RBP: bc38c046fcf8 R08: 90836c331fb0 R09: c1436a94 Jul 04 16:58:32 hostname kernel: R10: 908368178d2c R11: 0018 R12: 9083e222e632 Jul 04 16:58:32 hostname kernel: R13: 00092800 R14: 908367ca6140 R15: 908367ca6140 Jul 04 16:58:32 hostname kernel: FS: () GS:90836c30() knlGS: Jul 04 16:58:32 hostname kernel: CS: 0010 DS: ES: CR0: 80050033 Jul 04 16:58:32 hostname kernel: CR2: 9083e222e632 CR3: 0003ab80a003 CR4: 003606e0 Jul 04 16:58:32 hostname kernel: Call Trace: Jul 04 16:58:32 hostname kernel: ? mempool_alloc_slab+0x17/0x20 Jul 04 16:58:32 hostname kernel: mempool_alloc_slab+0x17/0x20 Jul 04 16:58:32 hostname kernel: mempool_alloc+0x64/0x180 Jul 04 16:58:32 hostname kernel: rpc_malloc+0xa1/0xb0 [sunrpc] Jul 04 16:58:32 hostname kernel: call_allocate+0xd1/0x1b0 [sunrpc] Jul 04 16:58:32 hostname kernel: ? call_refreshresult+0x100/0x100 [sunrpc] Jul 04 16:58:32 hostname kernel: __rpc_execute+0x8c/0x3a0 [sunrpc] Jul 04 16:58:32 hostname kernel: rpc_async_schedule+0x30/0x50 [sunrpc] Jul 04 16:58:32 hostname kernel: process_one_work+0x1eb/0x3b0 Jul 04 16:58:32 hostname kernel: worker_thread+0x4d/0x400 Jul 04 16:58:32 hostname kernel: kthread+0x104/0x140 Jul 04 16:58:32 hostname kernel: ? process_one_work+0x3b0/0x3b0 Jul 04 16:58:32 hostname kernel: ? kthread_park+0x90/0x90 Jul 04 16:58:32 hostname kernel: ret_from_fork+0x35/0x40 Jul 04 16:58:32 hostname kernel: Modules linked in: rfcomm rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) msr ccm cmac algif_hash algif_skcipher af_alg aufs bnep overlay nls_iso8859_1 mei_hdcp intel_rapl_msr snd_s> Jul 04 16:58:32 hostname kernel: nvram ledtrig_audio mei_me cfg80211 mei processor_thermal_device snd_seq ucsi_acpi typec_ucsi intel_rapl_common intel_soc_dts_iosf snd_seq_device typec intel_pch_thermal snd_timer snd int3403_thermal soundcore int340x_thermal_zone i> Jul 04 16:58:32 hostname kernel: pinctrl_cannonlake video pinctrl_intel Jul 04 16:58:32 hostname kernel: CR2: 9083e222e632 Jul 04 16:58:32 hostname kernel: ---[ end trace cbbaed921eb439ce ]--- Jul 04 16:58:32 hostname kernel: RIP: 0010:kmem_cache_alloc+0x7e/0x230 Jul 04 16:58:32 hostname kernel: Code: 99 01 00 00 4d 8b 07 65 49 8b 50 08 65 4c 03 05 40 9d 56 44 4d 8b 20 4d 85 e4 0f 84 85 01 00 00 41 8b 47 20 49 8b 3f 4c 01 e0 <48> 8b 18 48 89 c1 49 33 9f 70 01 00 00 4c 89 e0 48 0f c9 48 31 cb Jul 04 16:58:32 hostname kernel: RSP: 0018:bc38c046fcc8 EFLAGS: 00010282 Jul 04 16:58:32 hostname kernel: RAX: 9083e222e632 RBX: RCX: 0002 Jul 04 16:58:32 hostname kernel: RDX: 0009 RSI: 00092800 RDI: 00031fb0 Jul 04 16:58:32 hostname kernel: RBP: bc38c046fcf8 R08: 90836c331fb0 R09: c1436a94 Jul 04
Re: [Kernel-packages] [Bug 1888571] Re: [Ice Lake] Screen flickering and glitching after install
Removing nomodeset reverts back to the original screen flickering problem with almost zero usability. Are there any other solutions to this? On Thu, Jul 23, 2020 at 9:10 PM Daniel van Vugt <1888...@bugs.launchpad.net> wrote: > "nomodeset" will disable all hardware graphics support so it will use > high CPU and likely cause screen tearing. That's not really a solution > so you should remove "nomodeset" as soon as you can. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1888571 > > Title: > [Ice Lake] Screen flickering and glitching after install > > Status in linux package in Ubuntu: > Confirmed > > Bug description: > Intel integrated driver causes screen flickering with Ubuntu install. > Windows did not have this issue > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: xorg 1:7.7+19ubuntu14 > ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 > Uname: Linux 5.4.0-42-generic x86_64 > ApportVersion: 2.20.11-0ubuntu27.4 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' > CasperMD5CheckResult: skip > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Wed Jul 22 15:41:42 2020 > DistUpgraded: Fresh install > DistroCodename: focal > DistroVariant: ubuntu > ExtraDebuggingInterest: Yes, if not too technical > GraphicsCard: >Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if > 00 [VGA controller]) > Subsystem: Hewlett-Packard Company Iris Plus Graphics G7 [103c:875a] > InstallationDate: Installed on 2020-07-22 (0 days ago) > InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 > (20200423) > MachineType: HP HP ENVY Laptop 13-ba0xxx > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic > root=UUID=9f807172-2b35-4ad1-9f33-5a912ad7c579 ro quiet splash vt.handoff=7 > SourcePackage: xorg > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 06/04/2020 > dmi.bios.vendor: Insyde > dmi.bios.version: F.10 > dmi.board.asset.tag: Type2 - Board Asset Tag > dmi.board.name: 875A > dmi.board.vendor: HP > dmi.board.version: 07.34 > dmi.chassis.asset.tag: Chassis Asset Tag > dmi.chassis.type: 10 > dmi.chassis.vendor: HP > dmi.chassis.version: Chassis Version > dmi.modalias: > dmi:bvnInsyde:bvrF.10:bd06/04/2020:svnHP:pnHPENVYLaptop13-ba0xxx:pvrType1ProductConfigId:rvnHP:rn875A:rvr07.34:cvnHP:ct10:cvrChassisVersion: > dmi.product.family: 103C_5335KV HP Envy > dmi.product.name: HP ENVY Laptop 13-ba0xxx > dmi.product.sku: 8KD13AV > dmi.product.version: Type1ProductConfigId > dmi.sys.vendor: HP > version.compiz: compiz N/A > version.libdrm2: libdrm2 2.4.101-2 > version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 > version.libgl1-mesa-glx: libgl1-mesa-glx N/A > version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.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/ubuntu/+source/linux/+bug/1888571/+subscriptions > -- Drew Erikson University of Minnesota - Twin Cities Computer Science & Mathematics | 2020 eriks...@umn.edu -- 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/1888571 Title: [Ice Lake] Screen flickering and glitching after install Status in linux package in Ubuntu: Confirmed Bug description: Intel integrated driver causes screen flickering with Ubuntu install. Windows did not have this issue ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 22 15:41:42 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Iris Plus Graphics G7 [103c:875a] InstallationDate: Installed on 2020-07-22 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: HP HP ENVY Laptop 13-ba0xxx ProcEnviron:
[Kernel-packages] [Bug 1886277] Re: Regression on NFS: unable to handle page fault in mempool_alloc_slab
The enctypes according to klist are: Etype (skey, tkt): aes256-cts-hmac- sha1-96, aes256-cts-hmac-sha1-96. The kerberos tickets come from Active Directory server and NFS servers are NetApps, if that matters. -- 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/1886277 Title: Regression on NFS: unable to handle page fault in mempool_alloc_slab Status in linux package in Ubuntu: Confirmed Bug description: On kernel 5.4.0-40-generic in focal I'm getting errors like this on several machines with different hardware in the first hour after boot: Jul 04 16:58:32 hostname kernel: BUG: unable to handle page fault for address: 9083e222e632 Jul 04 16:58:32 hostname kernel: #PF: supervisor read access in kernel mode Jul 04 16:58:32 hostname kernel: #PF: error_code(0x) - not-present page Jul 04 16:58:32 hostname kernel: PGD 3ac205067 P4D 3ac205067 PUD 0 Jul 04 16:58:32 hostname kernel: Oops: [#1] SMP NOPTI Jul 04 16:58:32 hostname kernel: CPU: 4 PID: 289 Comm: kworker/u16:4 Tainted: G OE 5.4.0-40-generic #44-Ubuntu Jul 04 16:58:32 hostname kernel: Hardware name: LENOVO 20N2CTO1WW/20N2CTO1WW, BIOS N2IET88W (1.66 ) 04/22/2020 Jul 04 16:58:32 hostname kernel: Workqueue: rpciod rpc_async_schedule [sunrpc] Jul 04 16:58:32 hostname kernel: RIP: 0010:kmem_cache_alloc+0x7e/0x230 Jul 04 16:58:32 hostname kernel: Code: 99 01 00 00 4d 8b 07 65 49 8b 50 08 65 4c 03 05 40 9d 56 44 4d 8b 20 4d 85 e4 0f 84 85 01 00 00 41 8b 47 20 49 8b 3f 4c 01 e0 <48> 8b 18 48 89 c1 49 33 9f 70 01 00 00 4c 89 e0 48 0f c9 48 31 cb Jul 04 16:58:32 hostname kernel: RSP: 0018:bc38c046fcc8 EFLAGS: 00010282 Jul 04 16:58:32 hostname kernel: RAX: 9083e222e632 RBX: RCX: 0002 Jul 04 16:58:32 hostname kernel: RDX: 0009 RSI: 00092800 RDI: 00031fb0 Jul 04 16:58:32 hostname kernel: RBP: bc38c046fcf8 R08: 90836c331fb0 R09: c1436a94 Jul 04 16:58:32 hostname kernel: R10: 908368178d2c R11: 0018 R12: 9083e222e632 Jul 04 16:58:32 hostname kernel: R13: 00092800 R14: 908367ca6140 R15: 908367ca6140 Jul 04 16:58:32 hostname kernel: FS: () GS:90836c30() knlGS: Jul 04 16:58:32 hostname kernel: CS: 0010 DS: ES: CR0: 80050033 Jul 04 16:58:32 hostname kernel: CR2: 9083e222e632 CR3: 0003ab80a003 CR4: 003606e0 Jul 04 16:58:32 hostname kernel: Call Trace: Jul 04 16:58:32 hostname kernel: ? mempool_alloc_slab+0x17/0x20 Jul 04 16:58:32 hostname kernel: mempool_alloc_slab+0x17/0x20 Jul 04 16:58:32 hostname kernel: mempool_alloc+0x64/0x180 Jul 04 16:58:32 hostname kernel: rpc_malloc+0xa1/0xb0 [sunrpc] Jul 04 16:58:32 hostname kernel: call_allocate+0xd1/0x1b0 [sunrpc] Jul 04 16:58:32 hostname kernel: ? call_refreshresult+0x100/0x100 [sunrpc] Jul 04 16:58:32 hostname kernel: __rpc_execute+0x8c/0x3a0 [sunrpc] Jul 04 16:58:32 hostname kernel: rpc_async_schedule+0x30/0x50 [sunrpc] Jul 04 16:58:32 hostname kernel: process_one_work+0x1eb/0x3b0 Jul 04 16:58:32 hostname kernel: worker_thread+0x4d/0x400 Jul 04 16:58:32 hostname kernel: kthread+0x104/0x140 Jul 04 16:58:32 hostname kernel: ? process_one_work+0x3b0/0x3b0 Jul 04 16:58:32 hostname kernel: ? kthread_park+0x90/0x90 Jul 04 16:58:32 hostname kernel: ret_from_fork+0x35/0x40 Jul 04 16:58:32 hostname kernel: Modules linked in: rfcomm rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) msr ccm cmac algif_hash algif_skcipher af_alg aufs bnep overlay nls_iso8859_1 mei_hdcp intel_rapl_msr snd_s> Jul 04 16:58:32 hostname kernel: nvram ledtrig_audio mei_me cfg80211 mei processor_thermal_device snd_seq ucsi_acpi typec_ucsi intel_rapl_common intel_soc_dts_iosf snd_seq_device typec intel_pch_thermal snd_timer snd int3403_thermal soundcore int340x_thermal_zone i> Jul 04 16:58:32 hostname kernel: pinctrl_cannonlake video pinctrl_intel Jul 04 16:58:32 hostname kernel: CR2: 9083e222e632 Jul 04 16:58:32 hostname kernel: ---[ end trace cbbaed921eb439ce ]--- Jul 04 16:58:32 hostname kernel: RIP: 0010:kmem_cache_alloc+0x7e/0x230 Jul 04 16:58:32 hostname kernel: Code: 99 01 00 00 4d 8b 07 65 49 8b 50 08 65 4c 03 05 40 9d 56 44 4d 8b 20 4d 85 e4 0f 84 85 01 00 00 41 8b 47 20 49 8b 3f 4c 01 e0 <48> 8b 18 48 89 c1 49 33 9f 70 01 00 00 4c 89 e0 48 0f c9 48 31 cb Jul 04 16:58:32 hostname kernel: RSP: 0018:bc38c046fcc8 EFLAGS: 00010282 Jul 04 16:58:32 hostname kernel: RAX: 9083e222e632 RBX: RCX: 0002 Jul 04 16:58:32 hostname kernel: RDX: 0009 RSI: 00092800 RDI: 00031fb0 Jul 04 16:58:32 hostname kernel: RBP: bc38c046fcf8 R08: 90836c331fb0 R09: c1436a94 Jul 04
[Kernel-packages] [Bug 1886277] Re: Regression on NFS: unable to handle page fault in mempool_alloc_slab
This also affects Ubuntu Bionic, if linux-generic-hwe-18.04 is installed. The 4.15.0-112-generic works fine. -- 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/1886277 Title: Regression on NFS: unable to handle page fault in mempool_alloc_slab Status in linux package in Ubuntu: Confirmed Bug description: On kernel 5.4.0-40-generic in focal I'm getting errors like this on several machines with different hardware in the first hour after boot: Jul 04 16:58:32 hostname kernel: BUG: unable to handle page fault for address: 9083e222e632 Jul 04 16:58:32 hostname kernel: #PF: supervisor read access in kernel mode Jul 04 16:58:32 hostname kernel: #PF: error_code(0x) - not-present page Jul 04 16:58:32 hostname kernel: PGD 3ac205067 P4D 3ac205067 PUD 0 Jul 04 16:58:32 hostname kernel: Oops: [#1] SMP NOPTI Jul 04 16:58:32 hostname kernel: CPU: 4 PID: 289 Comm: kworker/u16:4 Tainted: G OE 5.4.0-40-generic #44-Ubuntu Jul 04 16:58:32 hostname kernel: Hardware name: LENOVO 20N2CTO1WW/20N2CTO1WW, BIOS N2IET88W (1.66 ) 04/22/2020 Jul 04 16:58:32 hostname kernel: Workqueue: rpciod rpc_async_schedule [sunrpc] Jul 04 16:58:32 hostname kernel: RIP: 0010:kmem_cache_alloc+0x7e/0x230 Jul 04 16:58:32 hostname kernel: Code: 99 01 00 00 4d 8b 07 65 49 8b 50 08 65 4c 03 05 40 9d 56 44 4d 8b 20 4d 85 e4 0f 84 85 01 00 00 41 8b 47 20 49 8b 3f 4c 01 e0 <48> 8b 18 48 89 c1 49 33 9f 70 01 00 00 4c 89 e0 48 0f c9 48 31 cb Jul 04 16:58:32 hostname kernel: RSP: 0018:bc38c046fcc8 EFLAGS: 00010282 Jul 04 16:58:32 hostname kernel: RAX: 9083e222e632 RBX: RCX: 0002 Jul 04 16:58:32 hostname kernel: RDX: 0009 RSI: 00092800 RDI: 00031fb0 Jul 04 16:58:32 hostname kernel: RBP: bc38c046fcf8 R08: 90836c331fb0 R09: c1436a94 Jul 04 16:58:32 hostname kernel: R10: 908368178d2c R11: 0018 R12: 9083e222e632 Jul 04 16:58:32 hostname kernel: R13: 00092800 R14: 908367ca6140 R15: 908367ca6140 Jul 04 16:58:32 hostname kernel: FS: () GS:90836c30() knlGS: Jul 04 16:58:32 hostname kernel: CS: 0010 DS: ES: CR0: 80050033 Jul 04 16:58:32 hostname kernel: CR2: 9083e222e632 CR3: 0003ab80a003 CR4: 003606e0 Jul 04 16:58:32 hostname kernel: Call Trace: Jul 04 16:58:32 hostname kernel: ? mempool_alloc_slab+0x17/0x20 Jul 04 16:58:32 hostname kernel: mempool_alloc_slab+0x17/0x20 Jul 04 16:58:32 hostname kernel: mempool_alloc+0x64/0x180 Jul 04 16:58:32 hostname kernel: rpc_malloc+0xa1/0xb0 [sunrpc] Jul 04 16:58:32 hostname kernel: call_allocate+0xd1/0x1b0 [sunrpc] Jul 04 16:58:32 hostname kernel: ? call_refreshresult+0x100/0x100 [sunrpc] Jul 04 16:58:32 hostname kernel: __rpc_execute+0x8c/0x3a0 [sunrpc] Jul 04 16:58:32 hostname kernel: rpc_async_schedule+0x30/0x50 [sunrpc] Jul 04 16:58:32 hostname kernel: process_one_work+0x1eb/0x3b0 Jul 04 16:58:32 hostname kernel: worker_thread+0x4d/0x400 Jul 04 16:58:32 hostname kernel: kthread+0x104/0x140 Jul 04 16:58:32 hostname kernel: ? process_one_work+0x3b0/0x3b0 Jul 04 16:58:32 hostname kernel: ? kthread_park+0x90/0x90 Jul 04 16:58:32 hostname kernel: ret_from_fork+0x35/0x40 Jul 04 16:58:32 hostname kernel: Modules linked in: rfcomm rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) msr ccm cmac algif_hash algif_skcipher af_alg aufs bnep overlay nls_iso8859_1 mei_hdcp intel_rapl_msr snd_s> Jul 04 16:58:32 hostname kernel: nvram ledtrig_audio mei_me cfg80211 mei processor_thermal_device snd_seq ucsi_acpi typec_ucsi intel_rapl_common intel_soc_dts_iosf snd_seq_device typec intel_pch_thermal snd_timer snd int3403_thermal soundcore int340x_thermal_zone i> Jul 04 16:58:32 hostname kernel: pinctrl_cannonlake video pinctrl_intel Jul 04 16:58:32 hostname kernel: CR2: 9083e222e632 Jul 04 16:58:32 hostname kernel: ---[ end trace cbbaed921eb439ce ]--- Jul 04 16:58:32 hostname kernel: RIP: 0010:kmem_cache_alloc+0x7e/0x230 Jul 04 16:58:32 hostname kernel: Code: 99 01 00 00 4d 8b 07 65 49 8b 50 08 65 4c 03 05 40 9d 56 44 4d 8b 20 4d 85 e4 0f 84 85 01 00 00 41 8b 47 20 49 8b 3f 4c 01 e0 <48> 8b 18 48 89 c1 49 33 9f 70 01 00 00 4c 89 e0 48 0f c9 48 31 cb Jul 04 16:58:32 hostname kernel: RSP: 0018:bc38c046fcc8 EFLAGS: 00010282 Jul 04 16:58:32 hostname kernel: RAX: 9083e222e632 RBX: RCX: 0002 Jul 04 16:58:32 hostname kernel: RDX: 0009 RSI: 00092800 RDI: 00031fb0 Jul 04 16:58:32 hostname kernel: RBP: bc38c046fcf8 R08: 90836c331fb0 R09: c1436a94 Jul 04 16:58:32 hostname kernel: R10: 908368178d2c R11: 0018 R12: 9083e222e632 Jul 04
[Kernel-packages] [Bug 1879707] Comment bridged from LTC Bugzilla
--- Comment From jan.hoepp...@de.ibm.com 2020-07-24 06:10 EDT--- (In reply to comment #29) > I just wanted to try the kernel that I've build yesterday (see comment #6) > and as a first step I wanted to recreate re-create the described error > situation on an up to date 20.04 system: > $ lsb_release -a > No LSB modules are available. > Distributor ID: Ubuntu > Description: Ubuntu 20.04 LTS > Release: 20.04 > Codename: focal > $ uname -a > Linux zlin42 5.4.0-40-generic #44-Ubuntu SMP Mon Jun 22 23:57:33 UTC 2020 > s390x s390x s390x GNU/Linux > $ apt-cache policy linux-generic > linux-generic: > Installed: 5.4.0.40.43 > Candidate: 5.4.0.40.43 > Version table: > *** 5.4.0.40.43 500 > 500 http://ports.ubuntu.com/ubuntu-ports focal-updates/main s390x Packages > 500 http://ports.ubuntu.com/ubuntu-ports focal-security/main s390x Packages > 100 /var/lib/dpkg/status > 5.4.0.26.32 500 > 500 http://ports.ubuntu.com/ubuntu-ports focal/main s390x Packages > $ > > But by surprise I didn't ran into any problems! > > I was able to flawlessly make use of FBA devices in the following three > different way: > 1) (re-)used a FBA device that was previously in use, without wiping out any > data > 2) used a FBA device that I wiped out using wipefs > 3) used a FBA device that I entirely wiped out (and zeroed) using dd > (see the attached doc for more details) > > Looks like a fix for this problem came in with the kernels that were rolled > out in between 5.4.0-29-generic and 5.4.0-40-generic. > (Again I didn't installed the patched kernel, I just used the latest > official one.) > > Message to the initial bug reporter: > Please can you retry on an up-to-date 20.04 system (or after having updated > your existing one, like for example with "sudo apt -y -q update && sudo apt > -y -q full-upgrade" plus reboot in case the kernel got update, what I assume > will happen)? The issue is more likely to occur when the system has > 2GB of memory. I can't see in your attachment what system configuration you're running, but maybe that's the reason you're not running into the problem. This was also my mistake when I tried to reproduce the problem. Once I had my configuration changed to 8GB of memory I ran into the error immediately. The problem really is that the ZERO_PAGE allocation for the discard I/O can't be used on systems with > 2GB of memory. The fix I proposed actually solves the problem and is currently in review. I'll post the commit id once the fix went upstream. Jan -- 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/1879707 Title: [UBUNTU 20.04] mke2fs dasd(fba),Failing CCW,default ERP has run out of retries and failed Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: New Bug description: mke2fs,dasd(fba) guest edevices FBA,default ERP has run out of retries and failed,Failing CCW ---uname output--- xx - 5.4.0-29-generic #33-Ubuntu SMP Wed Apr 29 14:27:18 UTC 2020 s390x s390x s390x GNU/Linux Machine Type = IBM 3906 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- mke2fs to dasd(fba) devices Stack trace output: no Oops output: no System Dump Info: The system is not configured to capture a system dump. -Post a private note with access information to the machine that the bug is occuring on. -Attach sysctl -a output output to the bug. dasd(fba),Failing CCW,default ERP has run out of retries and failed between the following syslog events, mke2fs running, before mounting and starting IO to dasd(fba) devices May 14 14:33:32 ilabg13 root: ILAB_IO_FROM_MSDI_START May 14 14:48:34 ilabg13 root: ILAB_IO_FROM_MSDI_RUNNING To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1879707/+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 1812978] Re: rtnetlink.sh in net from ubuntu_kernel_selftests fails
Checked on the following kernels, this is not failing anymore: aws 5.4.0-1020.20~18.04.2-aws aws 5.3.0-1032.34~18.04.1 aws 5.3.0-1032.34 aws 4.15.0-1079.83 aws-fips 4.15.0-2023.23 aws 4.15.0-1079.83~16.04.1 aws 4.4.0-.123 gcp 5.4.0-1021.21~18.04.1 gcp 5.3.0-1032.34~18.04.1 gke 5.3.0-1032.34~18.04.1 gke-generic 5.3.0-64.58~18.04.1 gke-generic 5.0.0-53.57~18.04.1 gcp 5.3.0-1032.34 gcp 4.15.0-1080.90 Therefore I am going to close this bug, please check for the kernel config first if you found this test is failing (see bug 1812194) Commit to install modules-extra package for kselftest: https://kernel.ubuntu.com/git/ubuntu/autotest-client-tests.git/commit/?id=386354240a98a62f8b346d01fc9674750efd97a0 ** Changed in: ubuntu-kernel-tests Status: Confirmed => Fix Released ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux-aws (Ubuntu) Status: New => Invalid ** Changed in: linux (Ubuntu Bionic) Status: New => Invalid ** Changed in: linux-aws (Ubuntu Bionic) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1812978 Title: rtnetlink.sh in net from ubuntu_kernel_selftests fails Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Invalid Status in linux-aws package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Status in linux-aws source package in Bionic: Invalid Status in linux source package in Cosmic: Won't Fix Status in linux-aws source package in Cosmic: Won't Fix Bug description: There are several failures in this test: * ipv6 addrlabel * macsec * ipsec $ sudo ./rtnetlink.sh PASS: policy routing PASS: route get PASS: tc htb hierarchy PASS: gre tunnel endpoint PASS: gretap PASS: ip6gretap PASS: erspan PASS: ip6erspan PASS: bridge setup FAIL: ipv6 addrlabel PASS: set ifalias 485dc5aa-b024-4952-88a7-414355fc2bdc for test-dummy0 PASS: vrf PASS: vxlan FAIL: can't add fou port , skipping test *** stack smashing detected ***: terminated ./rtnetlink.sh: line 468: 5132 Aborted (core dumped) ip macsec show > /dev/null FAIL: macsec ./rtnetlink.sh: line 527: 5146 Terminated ip x m > $tmpfile FAIL: ipsec ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-14-generic 4.18.0-14.15 ProcVersionSignature: User Name 4.18.0-14.15-generic 4.18.20 Uname: Linux 4.18.0-14-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 23 09:53 seq crw-rw 1 root audio 116, 33 Jan 23 09:53 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu13.1 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 Jan 23 10:01:23 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Intel Corporation S1200RP PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-14-generic root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.18.0-14-generic N/A linux-backports-modules-4.18.0-14-generic N/A linux-firmware 1.175.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2015 dmi.bios.vendor: Intel Corp. dmi.bios.version: S1200RP.86B.03.02.0003.070120151022 dmi.board.asset.tag: dmi.board.name: S1200RP dmi.board.vendor: Intel Corporation dmi.board.version: G62254-407 dmi.chassis.asset.tag: dmi.chassis.type: 17 dmi.chassis.vendor: .. dmi.chassis.version: .. dmi.modalias: dmi:bvnIntelCorp.:bvrS1200RP.86B.03.02.0003.070120151022:bd07/01/2015:svnIntelCorporation:pnS1200RP:pvr:rvnIntelCorporation:rnS1200RP:rvrG62254-407:cvn..:ct17:cvr..: dmi.product.family: To be filled by O.E.M. dmi.product.name: S1200RP dmi.product.sku: To be filled by O.E.M. dmi.product.version: dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1812978/+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 1812194] Re: rtnetlink.sh in net from ubuntu_kernel_selftests failed on KVM kernels (config not enabled)
** Summary changed: - RTNETLINK in net from ubuntu_kernel_selftests failed on KVM kernels + rtnetlink.sh in net from ubuntu_kernel_selftests failed on KVM kernels (config not enabled) -- 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/1812194 Title: rtnetlink.sh in net from ubuntu_kernel_selftests failed on KVM kernels (config not enabled) Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux-kvm package in Ubuntu: New Status in linux source package in Bionic: Incomplete Status in linux-kvm source package in Bionic: New Status in linux source package in Cosmic: Incomplete Status in linux-kvm source package in Cosmic: Invalid Status in linux source package in Disco: Won't Fix Status in linux-kvm source package in Disco: Won't Fix Bug description: This test failed because of the unsuccessful attempt to add a dummy device with ip link command: # devdummy="test-dummy0" # ip link add name "$devdummy" type dummy RTNETLINK answers: Operation not supported selftests: rtnetlink.sh RTNETLINK answers: Operation not supported Cannot find device "test-dummy0" FAIL: cannot add dummy interface not ok 1..10 selftests: rtnetlink.sh [FAIL] ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1028-kvm 4.15.0-1028.28 ProcVersionSignature: User Name 4.15.0-1028.28-kvm 4.15.18 Uname: Linux 4.15.0-1028-kvm x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Thu Jan 17 10:21:02 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/1812194/+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 1812194] Re: RTNETLINK in net from ubuntu_kernel_selftests failed on KVM kernels
This test will need: CONFIG_DUMMY CONFIG_NETDEVSIM To be set to either Y or M. -- 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/1812194 Title: RTNETLINK in net from ubuntu_kernel_selftests failed on KVM kernels Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux-kvm package in Ubuntu: New Status in linux source package in Bionic: Incomplete Status in linux-kvm source package in Bionic: New Status in linux source package in Cosmic: Incomplete Status in linux-kvm source package in Cosmic: Invalid Status in linux source package in Disco: Won't Fix Status in linux-kvm source package in Disco: Won't Fix Bug description: This test failed because of the unsuccessful attempt to add a dummy device with ip link command: # devdummy="test-dummy0" # ip link add name "$devdummy" type dummy RTNETLINK answers: Operation not supported selftests: rtnetlink.sh RTNETLINK answers: Operation not supported Cannot find device "test-dummy0" FAIL: cannot add dummy interface not ok 1..10 selftests: rtnetlink.sh [FAIL] ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1028-kvm 4.15.0-1028.28 ProcVersionSignature: User Name 4.15.0-1028.28-kvm 4.15.18 Uname: Linux 4.15.0-1028-kvm x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Thu Jan 17 10:21:02 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/1812194/+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 1812978] Re: rtnetlink.sh in net from ubuntu_kernel_selftests fails
For comment #6, install the module-extra package can solve this problem. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1812978 Title: rtnetlink.sh in net from ubuntu_kernel_selftests fails Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux-aws package in Ubuntu: New Status in linux source package in Bionic: New Status in linux-aws source package in Bionic: New Status in linux source package in Cosmic: Won't Fix Status in linux-aws source package in Cosmic: Won't Fix Bug description: There are several failures in this test: * ipv6 addrlabel * macsec * ipsec $ sudo ./rtnetlink.sh PASS: policy routing PASS: route get PASS: tc htb hierarchy PASS: gre tunnel endpoint PASS: gretap PASS: ip6gretap PASS: erspan PASS: ip6erspan PASS: bridge setup FAIL: ipv6 addrlabel PASS: set ifalias 485dc5aa-b024-4952-88a7-414355fc2bdc for test-dummy0 PASS: vrf PASS: vxlan FAIL: can't add fou port , skipping test *** stack smashing detected ***: terminated ./rtnetlink.sh: line 468: 5132 Aborted (core dumped) ip macsec show > /dev/null FAIL: macsec ./rtnetlink.sh: line 527: 5146 Terminated ip x m > $tmpfile FAIL: ipsec ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-14-generic 4.18.0-14.15 ProcVersionSignature: User Name 4.18.0-14.15-generic 4.18.20 Uname: Linux 4.18.0-14-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 23 09:53 seq crw-rw 1 root audio 116, 33 Jan 23 09:53 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu13.1 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 Jan 23 10:01:23 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Intel Corporation S1200RP PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-14-generic root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.18.0-14-generic N/A linux-backports-modules-4.18.0-14-generic N/A linux-firmware 1.175.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2015 dmi.bios.vendor: Intel Corp. dmi.bios.version: S1200RP.86B.03.02.0003.070120151022 dmi.board.asset.tag: dmi.board.name: S1200RP dmi.board.vendor: Intel Corporation dmi.board.version: G62254-407 dmi.chassis.asset.tag: dmi.chassis.type: 17 dmi.chassis.vendor: .. dmi.chassis.version: .. dmi.modalias: dmi:bvnIntelCorp.:bvrS1200RP.86B.03.02.0003.070120151022:bd07/01/2015:svnIntelCorporation:pnS1200RP:pvr:rvnIntelCorporation:rnS1200RP:rvrG62254-407:cvn..:ct17:cvr..: dmi.product.family: To be filled by O.E.M. dmi.product.name: S1200RP dmi.product.sku: To be filled by O.E.M. dmi.product.version: dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1812978/+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 1888703] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1888703 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1888703 Title: After the latest update on 7/21/20 the screen shows random black horizontal single pixel line stripes in columns about 10-20 pixels long on open windows and icons presented on the desktop. Status in linux package in Ubuntu: Incomplete Bug description: Everything else works well in the system except for this issue. See attached picture for details. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus (not installed) ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 Uname: Linux 5.4.0-42-generic i686 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: i386 CurrentDesktop: MATE Date: Thu Jul 23 08:14:26 2020 InstallationDate: Installed on 2019-12-08 (228 days ago) InstallationMedia: Ubuntu-MATE 18.04.3 LTS "Bionic Beaver" - Release i386 (20190805) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888703/+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 1888510] Re: xen-netfront: potential deadlock in xennet_remove()
** Changed in: linux-aws (Ubuntu) Status: New => Triaged ** Changed in: linux-aws (Ubuntu) Status: Triaged => Invalid ** Changed in: linux-aws (Ubuntu Bionic) Status: New => Incomplete ** Changed in: linux-aws (Ubuntu Focal) Status: New => Fix Committed ** Changed in: linux-aws (Ubuntu Focal) Importance: Undecided => High ** Changed in: linux-aws-5.3 (Ubuntu Bionic) Status: New => Fix Committed ** Changed in: linux-aws-5.3 (Ubuntu Bionic) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1888510 Title: xen-netfront: potential deadlock in xennet_remove() Status in linux-aws package in Ubuntu: Invalid Status in linux-aws-5.3 package in Ubuntu: Invalid Status in linux-aws source package in Bionic: Incomplete Status in linux-aws-5.3 source package in Bionic: Fix Committed Status in linux-aws source package in Focal: Fix Committed Status in linux-aws-5.3 source package in Focal: Invalid Bug description: [Impact] During our AWS testing we were experiencing deadlocks on hibernate across all Xen instance types. The trace was showing that the system was stuck in xennet_remove(): [ 358.109087] Freezing of tasks failed after 20.006 seconds (1 tasks refusing to freeze, wq_busy=0): [ 358.115102] modprobeD0 4892 4833 0x4004 [ 358.115104] Call Trace: [ 358.115112] __schedule+0x2a8/0x670 [ 358.115115] schedule+0x33/0xa0 [ 358.115118] xennet_remove+0x1f0/0x230 [xen_netfront] [ 358.115121] ? wait_woken+0x80/0x80 [ 358.115124] xenbus_dev_remove+0x51/0xa0 [ 358.115126] device_release_driver_internal+0xe0/0x1b0 [ 358.115127] driver_detach+0x49/0x90 [ 358.115129] bus_remove_driver+0x59/0xd0 [ 358.115131] driver_unregister+0x2c/0x40 [ 358.115132] xenbus_unregister_driver+0x12/0x20 [ 358.115134] netif_exit+0x10/0x7aa [xen_netfront] [ 358.115137] __x64_sys_delete_module+0x146/0x290 [ 358.115140] do_syscall_64+0x5a/0x130 [ 358.115142] entry_SYSCALL_64_after_hwframe+0x44/0xa9 This prevented hibernation to complete. The reason of this problem is a race condition in xennet_remove(): the system is reading the current state of the bus, it's requesting to change the state to "Closing", and it's waiting for the state to be changed to "Closing". However, if the state becomes "Closed" between reading the state and requesting the state change, we are stuck forever, because the state will never change from "Closed" back to "Closing". [Test case] Create any Xen-based instance in AWS, hibernate/resume multiple times. Some times the system gets stuck (hung task timeout). [Fix] Prevent the deadlock by changing the wait condition to check also for state == Closed. [Regression potential] Minimal, this change affects only Xen, more exactly only the xen- netfront driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1888510/+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 1888703] Re: After the latest update on 7/21/20 the screen shows random black horizontal single pixel line stripes in columns about 10-20 pixels long on open windows and icons p
Thanks, reassigning to the linux component since you say it's a kernel bug ** Package changed: nautilus (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1888703 Title: After the latest update on 7/21/20 the screen shows random black horizontal single pixel line stripes in columns about 10-20 pixels long on open windows and icons presented on the desktop. Status in linux package in Ubuntu: New Bug description: Everything else works well in the system except for this issue. See attached picture for details. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus (not installed) ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 Uname: Linux 5.4.0-42-generic i686 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: i386 CurrentDesktop: MATE Date: Thu Jul 23 08:14:26 2020 InstallationDate: Installed on 2019-12-08 (228 days ago) InstallationMedia: Ubuntu-MATE 18.04.3 LTS "Bionic Beaver" - Release i386 (20190805) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888703/+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 1888703] [NEW] After the latest update on 7/21/20 the screen shows random black horizontal single pixel line stripes in columns about 10-20 pixels long on open windows and icons
You have been subscribed to a public bug: Everything else works well in the system except for this issue. See attached picture for details. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus (not installed) ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 Uname: Linux 5.4.0-42-generic i686 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: i386 CurrentDesktop: MATE Date: Thu Jul 23 08:14:26 2020 InstallationDate: Installed on 2019-12-08 (228 days ago) InstallationMedia: Ubuntu-MATE 18.04.3 LTS "Bionic Beaver" - Release i386 (20190805) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug bionic i386 -- After the latest update on 7/21/20 the screen shows random black horizontal single pixel line stripes in columns about 10-20 pixels long on open windows and icons presented on the desktop. https://bugs.launchpad.net/bugs/1888703 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887156] Re: USB ports not working on the Pi 4 rev 1.4 board
As Eoan has EOL'ed, I am applying the fix directly to bionic/linux- raspi2-5.3 and will re-spin it. ** Also affects: linux-raspi2-5.3 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-raspi2-5.3 (Ubuntu Eoan) Status: New => Invalid ** Changed in: linux-raspi2-5.3 (Ubuntu Bionic) Status: New => Fix Committed ** Changed in: linux-raspi2-5.3 (Ubuntu Bionic) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1887156 Title: USB ports not working on the Pi 4 rev 1.4 board Status in linux-raspi2 package in Ubuntu: New Status in linux-raspi2-5.3 package in Ubuntu: New Status in linux-raspi2 source package in Bionic: Confirmed Status in linux-raspi2-5.3 source package in Bionic: Fix Committed Status in linux-raspi2 source package in Eoan: Fix Committed Status in linux-raspi2-5.3 source package in Eoan: Invalid Bug description: [Impact] USB on the Pi 4B rev 1.4 running the raspi 5.3 kernel is non- functional. [Test Case] See original description below. [Regression Potential] Low. The changes are isolated to the PCIe driver used for the Raspberry Pi. The commit is a clean cherry-pick from the raspi 5.4 kernel. [Original Description] On the Pi 4 board revision 1.4 (of which the 8Gb model is currently the main example), the VL805 USB controller doesn't appear to be recognized by the 5.3 kernel. To reproduce: * Flash a current bionic image (e.g. http://cdimage.ubuntu.com/releases/bionic/release/ubuntu-18.04.4-preinstalled-server-arm64+raspi4.img.xz) * Boot the card on an older Pi model (3, 4 rev 1.2, etc.) * sudo add-apt-repository ppa:waveform/firmware * sudo apt install linux-firmware-raspi2 (the rev 1.4 requires a newer firmware package to boot; this PPA contains a test package with a back-ported firmware) * Boot the card on a Pi 4 rev 1.4 * Observe USB2 and USB3 ports do not work * Boot the card on an older Pi 4 rev 1.2 * Observe USB2 and USB3 ports do work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1887156/+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 1876259] Re: bcm2835-codec module is missing
This bug was fixed in the package linux-raspi - 5.4.0-1015.15 --- linux-raspi (5.4.0-1015.15) focal; urgency=medium * focal/linux-raspi: 5.4.0-1015.15 -proposed tracker (LP: #1887056) [ Ubuntu: 5.4.0-42.46 ] * focal/linux: 5.4.0-42.46 -proposed tracker (LP: #1887069) * linux 4.15.0-109-generic network DoS regression vs -108 (LP: #1886668) - SAUCE: Revert "netprio_cgroup: Fix unlimited memory leak of v2 cgroups" linux-raspi (5.4.0-1014.14) focal; urgency=medium * focal/linux-raspi: 5.4.0-1014.14 -proposed tracker (LP: #1885841) * Add crda dependency (LP: #1877415) - [Packaging] raspi: Depend on crda * dtoverlay=uart4 breaks Raspberry Pi 4B boot (LP: #1875454) - SAUCE: arm: dts: Add 'brcm, bcm2835-pl011' for compatible for uart2-5 * aarch64 kernel module for exfat not in raspberry pi 4 build (LP: #1880503) - [Config] raspi: Set EXFAT_FS=m * Enable ZFS for Raspberry Pi arm64 (LP: #1884110) - [Config] raspi: Enable zfs modules for arm64 * focal/linux-raspi: Upstream raspberrypi patchset 2020-06-10 (LP: #1882930) - Revert "net: bcmgenet: Workaround for Pi 4B network issue" - Revert "gpiolib: Don't prevent IRQ usage of output GPIOs" - gpiolib: Don't prevent IRQ usage of output GPIOs - drm/vc4: Fix HDMI mode validation - clk-raspberrypi: Allow cpufreq driver to also adjust gpu clocks - bcm2835-dma: Add proper 40-bit DMA support - overlays: tc358743: Use intra-overlay fragments - overlays: Move "fixed-clock" nodes to the root - raspberrypi: dts: Switch to discrete ALSA devices - dt-bindings: media: i2c: Add IMX477 CMOS sensor binding - dtoverlays: Add IMX477 sensor overlay - media: i2c: Add driver for Sony IMX477 sensor - media: i2c: imx477: Add support for adaptive frame control - configs: Add imx477 sensor driver to all Raspberry Pi defconfigs - udmabuf: Remove deleted map/unmap handlers. - udmabuf: use cache_sgt_mapping option - udmabuf: add a pointer to the miscdevice in dma-buf private data - udmabuf: separate out creating/destroying scatter-table - udmabuf: implement begin_cpu_access/end_cpu_access hooks - udmabuf: fix dma-buf cpu access - dma-buf: Add dma-buf heaps framework - dma-buf: heaps: Add heap helpers - dma-buf: heaps: Add system heap to dmabuf heaps - dma-buf: heaps: Add CMA heap to dmabuf heaps - kselftests: Add dma-heap test - dma-buf: heaps: Use _IOCTL_ for userspace IOCTL identifier - dma-buf: heaps: Remove redundant heap identifier from system heap name - dma-buf: fix resource leak on -ENOTTY error return path - dma-heap: Make the symbol 'dma_heap_ioctl_cmds' static - defconfig: Add CMA and system dma-heaps to the config - ARM: dts: Enable firmware-clocks on all Pis - configs: Include the firmware-clocks driver - configs: Use the upstream cpufreq driver - media: bcm2835-unicam: Always service interrupts - sc16is7xx: Fix for hardware flow control - drm/vc4: Fix VIC usage with Broadcast RGB - staging: vc04_services: mmal-vchiq: Update parameters list - staging:vc04_services: bcm2835-codec: Request headers with I-frame - staging:vc04_services: bcm2835-codec: Avoid fragmenting buffers - staging:vc04_services: bcm2835-camera: Request headers with I-frame - configs: Restore missing NF_TABLES settings - overlays: Fix audio parameter of vc4-kms-v3d - Switch to snd_soc_dai_set_bclk_ratio - media: bcm2835-unicam: Retain packing information on G_FMT - zswap: Defer zswap initialisation - configs: Add ZSWAP=y, ZBUD=m, Z3FOLD=m - drm/vc4: Adopt the dma configuration from the HVS or V3D component - drm/vc4: Add FKMS as an acceptable node for dma ranges. - media: i2c: imx477: Return correct result on sensor id verification - staging: vchiq_arm: Clean up 40-bit DMA support - ARM: dts: Update for new VCHIQ BCM2711 DMA support - media: bcm2835-unicam: change minimum number of vb2_queue buffers to 1 - dt-bindings: Add Broadcom AVS RO thermal - thermal: Add BCM2711 thermal driver - ARM: dts: bcm2711: Enable thermal - ARM: configs: Build BCM2711 thermal as module - Revert "thermal: brcmstb_thermal: Correct SoC name" - Revert "thermal: brcmstb_thermal: Add BCM2838 support" - ARM: dts: bcm2711-rpi: Remove downstream thermal sensor node - configs: Switch to upstream thermal sensor for RPi 4 - BCM2711_THERMAL - configs: Build HWMON core into kernel - brcmfmac: BCM43436 needs dedicated firmware - overlays: i2c-rtc: Fix trickle-resistor-ohms param - overlays: gpio-shutdown: Add information for SysV init / inittab - overlays: gpio-shutdown: Add information for Raspberry Pi 1 Model B rev 1 - overlays: Add spi0 overlay to support sc16is752 - net: rtl8192cu: fix gcc misleading whitespace warning - overlays: i2c-rtc-gpio: Fix trickle-resistor-ohms param - media: bcm2835-isp: fix bytes per
[Kernel-packages] [Bug 1878142] Re: Enable VIDEO_BCM2835_UNICAM and VIDEO_RPIVID
This bug was fixed in the package linux-raspi - 5.4.0-1015.15 --- linux-raspi (5.4.0-1015.15) focal; urgency=medium * focal/linux-raspi: 5.4.0-1015.15 -proposed tracker (LP: #1887056) [ Ubuntu: 5.4.0-42.46 ] * focal/linux: 5.4.0-42.46 -proposed tracker (LP: #1887069) * linux 4.15.0-109-generic network DoS regression vs -108 (LP: #1886668) - SAUCE: Revert "netprio_cgroup: Fix unlimited memory leak of v2 cgroups" linux-raspi (5.4.0-1014.14) focal; urgency=medium * focal/linux-raspi: 5.4.0-1014.14 -proposed tracker (LP: #1885841) * Add crda dependency (LP: #1877415) - [Packaging] raspi: Depend on crda * dtoverlay=uart4 breaks Raspberry Pi 4B boot (LP: #1875454) - SAUCE: arm: dts: Add 'brcm, bcm2835-pl011' for compatible for uart2-5 * aarch64 kernel module for exfat not in raspberry pi 4 build (LP: #1880503) - [Config] raspi: Set EXFAT_FS=m * Enable ZFS for Raspberry Pi arm64 (LP: #1884110) - [Config] raspi: Enable zfs modules for arm64 * focal/linux-raspi: Upstream raspberrypi patchset 2020-06-10 (LP: #1882930) - Revert "net: bcmgenet: Workaround for Pi 4B network issue" - Revert "gpiolib: Don't prevent IRQ usage of output GPIOs" - gpiolib: Don't prevent IRQ usage of output GPIOs - drm/vc4: Fix HDMI mode validation - clk-raspberrypi: Allow cpufreq driver to also adjust gpu clocks - bcm2835-dma: Add proper 40-bit DMA support - overlays: tc358743: Use intra-overlay fragments - overlays: Move "fixed-clock" nodes to the root - raspberrypi: dts: Switch to discrete ALSA devices - dt-bindings: media: i2c: Add IMX477 CMOS sensor binding - dtoverlays: Add IMX477 sensor overlay - media: i2c: Add driver for Sony IMX477 sensor - media: i2c: imx477: Add support for adaptive frame control - configs: Add imx477 sensor driver to all Raspberry Pi defconfigs - udmabuf: Remove deleted map/unmap handlers. - udmabuf: use cache_sgt_mapping option - udmabuf: add a pointer to the miscdevice in dma-buf private data - udmabuf: separate out creating/destroying scatter-table - udmabuf: implement begin_cpu_access/end_cpu_access hooks - udmabuf: fix dma-buf cpu access - dma-buf: Add dma-buf heaps framework - dma-buf: heaps: Add heap helpers - dma-buf: heaps: Add system heap to dmabuf heaps - dma-buf: heaps: Add CMA heap to dmabuf heaps - kselftests: Add dma-heap test - dma-buf: heaps: Use _IOCTL_ for userspace IOCTL identifier - dma-buf: heaps: Remove redundant heap identifier from system heap name - dma-buf: fix resource leak on -ENOTTY error return path - dma-heap: Make the symbol 'dma_heap_ioctl_cmds' static - defconfig: Add CMA and system dma-heaps to the config - ARM: dts: Enable firmware-clocks on all Pis - configs: Include the firmware-clocks driver - configs: Use the upstream cpufreq driver - media: bcm2835-unicam: Always service interrupts - sc16is7xx: Fix for hardware flow control - drm/vc4: Fix VIC usage with Broadcast RGB - staging: vc04_services: mmal-vchiq: Update parameters list - staging:vc04_services: bcm2835-codec: Request headers with I-frame - staging:vc04_services: bcm2835-codec: Avoid fragmenting buffers - staging:vc04_services: bcm2835-camera: Request headers with I-frame - configs: Restore missing NF_TABLES settings - overlays: Fix audio parameter of vc4-kms-v3d - Switch to snd_soc_dai_set_bclk_ratio - media: bcm2835-unicam: Retain packing information on G_FMT - zswap: Defer zswap initialisation - configs: Add ZSWAP=y, ZBUD=m, Z3FOLD=m - drm/vc4: Adopt the dma configuration from the HVS or V3D component - drm/vc4: Add FKMS as an acceptable node for dma ranges. - media: i2c: imx477: Return correct result on sensor id verification - staging: vchiq_arm: Clean up 40-bit DMA support - ARM: dts: Update for new VCHIQ BCM2711 DMA support - media: bcm2835-unicam: change minimum number of vb2_queue buffers to 1 - dt-bindings: Add Broadcom AVS RO thermal - thermal: Add BCM2711 thermal driver - ARM: dts: bcm2711: Enable thermal - ARM: configs: Build BCM2711 thermal as module - Revert "thermal: brcmstb_thermal: Correct SoC name" - Revert "thermal: brcmstb_thermal: Add BCM2838 support" - ARM: dts: bcm2711-rpi: Remove downstream thermal sensor node - configs: Switch to upstream thermal sensor for RPi 4 - BCM2711_THERMAL - configs: Build HWMON core into kernel - brcmfmac: BCM43436 needs dedicated firmware - overlays: i2c-rtc: Fix trickle-resistor-ohms param - overlays: gpio-shutdown: Add information for SysV init / inittab - overlays: gpio-shutdown: Add information for Raspberry Pi 1 Model B rev 1 - overlays: Add spi0 overlay to support sc16is752 - net: rtl8192cu: fix gcc misleading whitespace warning - overlays: i2c-rtc-gpio: Fix trickle-resistor-ohms param - media: bcm2835-isp: fix bytes per
[Kernel-packages] [Bug 1875454] Re: dtoverlay=uart4 breaks Raspberry Pi 4B boot
This bug was fixed in the package linux-raspi - 5.4.0-1015.15 --- linux-raspi (5.4.0-1015.15) focal; urgency=medium * focal/linux-raspi: 5.4.0-1015.15 -proposed tracker (LP: #1887056) [ Ubuntu: 5.4.0-42.46 ] * focal/linux: 5.4.0-42.46 -proposed tracker (LP: #1887069) * linux 4.15.0-109-generic network DoS regression vs -108 (LP: #1886668) - SAUCE: Revert "netprio_cgroup: Fix unlimited memory leak of v2 cgroups" linux-raspi (5.4.0-1014.14) focal; urgency=medium * focal/linux-raspi: 5.4.0-1014.14 -proposed tracker (LP: #1885841) * Add crda dependency (LP: #1877415) - [Packaging] raspi: Depend on crda * dtoverlay=uart4 breaks Raspberry Pi 4B boot (LP: #1875454) - SAUCE: arm: dts: Add 'brcm, bcm2835-pl011' for compatible for uart2-5 * aarch64 kernel module for exfat not in raspberry pi 4 build (LP: #1880503) - [Config] raspi: Set EXFAT_FS=m * Enable ZFS for Raspberry Pi arm64 (LP: #1884110) - [Config] raspi: Enable zfs modules for arm64 * focal/linux-raspi: Upstream raspberrypi patchset 2020-06-10 (LP: #1882930) - Revert "net: bcmgenet: Workaround for Pi 4B network issue" - Revert "gpiolib: Don't prevent IRQ usage of output GPIOs" - gpiolib: Don't prevent IRQ usage of output GPIOs - drm/vc4: Fix HDMI mode validation - clk-raspberrypi: Allow cpufreq driver to also adjust gpu clocks - bcm2835-dma: Add proper 40-bit DMA support - overlays: tc358743: Use intra-overlay fragments - overlays: Move "fixed-clock" nodes to the root - raspberrypi: dts: Switch to discrete ALSA devices - dt-bindings: media: i2c: Add IMX477 CMOS sensor binding - dtoverlays: Add IMX477 sensor overlay - media: i2c: Add driver for Sony IMX477 sensor - media: i2c: imx477: Add support for adaptive frame control - configs: Add imx477 sensor driver to all Raspberry Pi defconfigs - udmabuf: Remove deleted map/unmap handlers. - udmabuf: use cache_sgt_mapping option - udmabuf: add a pointer to the miscdevice in dma-buf private data - udmabuf: separate out creating/destroying scatter-table - udmabuf: implement begin_cpu_access/end_cpu_access hooks - udmabuf: fix dma-buf cpu access - dma-buf: Add dma-buf heaps framework - dma-buf: heaps: Add heap helpers - dma-buf: heaps: Add system heap to dmabuf heaps - dma-buf: heaps: Add CMA heap to dmabuf heaps - kselftests: Add dma-heap test - dma-buf: heaps: Use _IOCTL_ for userspace IOCTL identifier - dma-buf: heaps: Remove redundant heap identifier from system heap name - dma-buf: fix resource leak on -ENOTTY error return path - dma-heap: Make the symbol 'dma_heap_ioctl_cmds' static - defconfig: Add CMA and system dma-heaps to the config - ARM: dts: Enable firmware-clocks on all Pis - configs: Include the firmware-clocks driver - configs: Use the upstream cpufreq driver - media: bcm2835-unicam: Always service interrupts - sc16is7xx: Fix for hardware flow control - drm/vc4: Fix VIC usage with Broadcast RGB - staging: vc04_services: mmal-vchiq: Update parameters list - staging:vc04_services: bcm2835-codec: Request headers with I-frame - staging:vc04_services: bcm2835-codec: Avoid fragmenting buffers - staging:vc04_services: bcm2835-camera: Request headers with I-frame - configs: Restore missing NF_TABLES settings - overlays: Fix audio parameter of vc4-kms-v3d - Switch to snd_soc_dai_set_bclk_ratio - media: bcm2835-unicam: Retain packing information on G_FMT - zswap: Defer zswap initialisation - configs: Add ZSWAP=y, ZBUD=m, Z3FOLD=m - drm/vc4: Adopt the dma configuration from the HVS or V3D component - drm/vc4: Add FKMS as an acceptable node for dma ranges. - media: i2c: imx477: Return correct result on sensor id verification - staging: vchiq_arm: Clean up 40-bit DMA support - ARM: dts: Update for new VCHIQ BCM2711 DMA support - media: bcm2835-unicam: change minimum number of vb2_queue buffers to 1 - dt-bindings: Add Broadcom AVS RO thermal - thermal: Add BCM2711 thermal driver - ARM: dts: bcm2711: Enable thermal - ARM: configs: Build BCM2711 thermal as module - Revert "thermal: brcmstb_thermal: Correct SoC name" - Revert "thermal: brcmstb_thermal: Add BCM2838 support" - ARM: dts: bcm2711-rpi: Remove downstream thermal sensor node - configs: Switch to upstream thermal sensor for RPi 4 - BCM2711_THERMAL - configs: Build HWMON core into kernel - brcmfmac: BCM43436 needs dedicated firmware - overlays: i2c-rtc: Fix trickle-resistor-ohms param - overlays: gpio-shutdown: Add information for SysV init / inittab - overlays: gpio-shutdown: Add information for Raspberry Pi 1 Model B rev 1 - overlays: Add spi0 overlay to support sc16is752 - net: rtl8192cu: fix gcc misleading whitespace warning - overlays: i2c-rtc-gpio: Fix trickle-resistor-ohms param - media: bcm2835-isp: fix bytes per
[Kernel-packages] [Bug 1877415] Re: Add crda dependency
This bug was fixed in the package linux-raspi - 5.4.0-1015.15 --- linux-raspi (5.4.0-1015.15) focal; urgency=medium * focal/linux-raspi: 5.4.0-1015.15 -proposed tracker (LP: #1887056) [ Ubuntu: 5.4.0-42.46 ] * focal/linux: 5.4.0-42.46 -proposed tracker (LP: #1887069) * linux 4.15.0-109-generic network DoS regression vs -108 (LP: #1886668) - SAUCE: Revert "netprio_cgroup: Fix unlimited memory leak of v2 cgroups" linux-raspi (5.4.0-1014.14) focal; urgency=medium * focal/linux-raspi: 5.4.0-1014.14 -proposed tracker (LP: #1885841) * Add crda dependency (LP: #1877415) - [Packaging] raspi: Depend on crda * dtoverlay=uart4 breaks Raspberry Pi 4B boot (LP: #1875454) - SAUCE: arm: dts: Add 'brcm, bcm2835-pl011' for compatible for uart2-5 * aarch64 kernel module for exfat not in raspberry pi 4 build (LP: #1880503) - [Config] raspi: Set EXFAT_FS=m * Enable ZFS for Raspberry Pi arm64 (LP: #1884110) - [Config] raspi: Enable zfs modules for arm64 * focal/linux-raspi: Upstream raspberrypi patchset 2020-06-10 (LP: #1882930) - Revert "net: bcmgenet: Workaround for Pi 4B network issue" - Revert "gpiolib: Don't prevent IRQ usage of output GPIOs" - gpiolib: Don't prevent IRQ usage of output GPIOs - drm/vc4: Fix HDMI mode validation - clk-raspberrypi: Allow cpufreq driver to also adjust gpu clocks - bcm2835-dma: Add proper 40-bit DMA support - overlays: tc358743: Use intra-overlay fragments - overlays: Move "fixed-clock" nodes to the root - raspberrypi: dts: Switch to discrete ALSA devices - dt-bindings: media: i2c: Add IMX477 CMOS sensor binding - dtoverlays: Add IMX477 sensor overlay - media: i2c: Add driver for Sony IMX477 sensor - media: i2c: imx477: Add support for adaptive frame control - configs: Add imx477 sensor driver to all Raspberry Pi defconfigs - udmabuf: Remove deleted map/unmap handlers. - udmabuf: use cache_sgt_mapping option - udmabuf: add a pointer to the miscdevice in dma-buf private data - udmabuf: separate out creating/destroying scatter-table - udmabuf: implement begin_cpu_access/end_cpu_access hooks - udmabuf: fix dma-buf cpu access - dma-buf: Add dma-buf heaps framework - dma-buf: heaps: Add heap helpers - dma-buf: heaps: Add system heap to dmabuf heaps - dma-buf: heaps: Add CMA heap to dmabuf heaps - kselftests: Add dma-heap test - dma-buf: heaps: Use _IOCTL_ for userspace IOCTL identifier - dma-buf: heaps: Remove redundant heap identifier from system heap name - dma-buf: fix resource leak on -ENOTTY error return path - dma-heap: Make the symbol 'dma_heap_ioctl_cmds' static - defconfig: Add CMA and system dma-heaps to the config - ARM: dts: Enable firmware-clocks on all Pis - configs: Include the firmware-clocks driver - configs: Use the upstream cpufreq driver - media: bcm2835-unicam: Always service interrupts - sc16is7xx: Fix for hardware flow control - drm/vc4: Fix VIC usage with Broadcast RGB - staging: vc04_services: mmal-vchiq: Update parameters list - staging:vc04_services: bcm2835-codec: Request headers with I-frame - staging:vc04_services: bcm2835-codec: Avoid fragmenting buffers - staging:vc04_services: bcm2835-camera: Request headers with I-frame - configs: Restore missing NF_TABLES settings - overlays: Fix audio parameter of vc4-kms-v3d - Switch to snd_soc_dai_set_bclk_ratio - media: bcm2835-unicam: Retain packing information on G_FMT - zswap: Defer zswap initialisation - configs: Add ZSWAP=y, ZBUD=m, Z3FOLD=m - drm/vc4: Adopt the dma configuration from the HVS or V3D component - drm/vc4: Add FKMS as an acceptable node for dma ranges. - media: i2c: imx477: Return correct result on sensor id verification - staging: vchiq_arm: Clean up 40-bit DMA support - ARM: dts: Update for new VCHIQ BCM2711 DMA support - media: bcm2835-unicam: change minimum number of vb2_queue buffers to 1 - dt-bindings: Add Broadcom AVS RO thermal - thermal: Add BCM2711 thermal driver - ARM: dts: bcm2711: Enable thermal - ARM: configs: Build BCM2711 thermal as module - Revert "thermal: brcmstb_thermal: Correct SoC name" - Revert "thermal: brcmstb_thermal: Add BCM2838 support" - ARM: dts: bcm2711-rpi: Remove downstream thermal sensor node - configs: Switch to upstream thermal sensor for RPi 4 - BCM2711_THERMAL - configs: Build HWMON core into kernel - brcmfmac: BCM43436 needs dedicated firmware - overlays: i2c-rtc: Fix trickle-resistor-ohms param - overlays: gpio-shutdown: Add information for SysV init / inittab - overlays: gpio-shutdown: Add information for Raspberry Pi 1 Model B rev 1 - overlays: Add spi0 overlay to support sc16is752 - net: rtl8192cu: fix gcc misleading whitespace warning - overlays: i2c-rtc-gpio: Fix trickle-resistor-ohms param - media: bcm2835-isp: fix bytes per
[Kernel-packages] [Bug 1882930] Re: focal/linux-raspi: Upstream raspberrypi patchset 2020-06-10
This bug was fixed in the package linux-raspi - 5.4.0-1015.15 --- linux-raspi (5.4.0-1015.15) focal; urgency=medium * focal/linux-raspi: 5.4.0-1015.15 -proposed tracker (LP: #1887056) [ Ubuntu: 5.4.0-42.46 ] * focal/linux: 5.4.0-42.46 -proposed tracker (LP: #1887069) * linux 4.15.0-109-generic network DoS regression vs -108 (LP: #1886668) - SAUCE: Revert "netprio_cgroup: Fix unlimited memory leak of v2 cgroups" linux-raspi (5.4.0-1014.14) focal; urgency=medium * focal/linux-raspi: 5.4.0-1014.14 -proposed tracker (LP: #1885841) * Add crda dependency (LP: #1877415) - [Packaging] raspi: Depend on crda * dtoverlay=uart4 breaks Raspberry Pi 4B boot (LP: #1875454) - SAUCE: arm: dts: Add 'brcm, bcm2835-pl011' for compatible for uart2-5 * aarch64 kernel module for exfat not in raspberry pi 4 build (LP: #1880503) - [Config] raspi: Set EXFAT_FS=m * Enable ZFS for Raspberry Pi arm64 (LP: #1884110) - [Config] raspi: Enable zfs modules for arm64 * focal/linux-raspi: Upstream raspberrypi patchset 2020-06-10 (LP: #1882930) - Revert "net: bcmgenet: Workaround for Pi 4B network issue" - Revert "gpiolib: Don't prevent IRQ usage of output GPIOs" - gpiolib: Don't prevent IRQ usage of output GPIOs - drm/vc4: Fix HDMI mode validation - clk-raspberrypi: Allow cpufreq driver to also adjust gpu clocks - bcm2835-dma: Add proper 40-bit DMA support - overlays: tc358743: Use intra-overlay fragments - overlays: Move "fixed-clock" nodes to the root - raspberrypi: dts: Switch to discrete ALSA devices - dt-bindings: media: i2c: Add IMX477 CMOS sensor binding - dtoverlays: Add IMX477 sensor overlay - media: i2c: Add driver for Sony IMX477 sensor - media: i2c: imx477: Add support for adaptive frame control - configs: Add imx477 sensor driver to all Raspberry Pi defconfigs - udmabuf: Remove deleted map/unmap handlers. - udmabuf: use cache_sgt_mapping option - udmabuf: add a pointer to the miscdevice in dma-buf private data - udmabuf: separate out creating/destroying scatter-table - udmabuf: implement begin_cpu_access/end_cpu_access hooks - udmabuf: fix dma-buf cpu access - dma-buf: Add dma-buf heaps framework - dma-buf: heaps: Add heap helpers - dma-buf: heaps: Add system heap to dmabuf heaps - dma-buf: heaps: Add CMA heap to dmabuf heaps - kselftests: Add dma-heap test - dma-buf: heaps: Use _IOCTL_ for userspace IOCTL identifier - dma-buf: heaps: Remove redundant heap identifier from system heap name - dma-buf: fix resource leak on -ENOTTY error return path - dma-heap: Make the symbol 'dma_heap_ioctl_cmds' static - defconfig: Add CMA and system dma-heaps to the config - ARM: dts: Enable firmware-clocks on all Pis - configs: Include the firmware-clocks driver - configs: Use the upstream cpufreq driver - media: bcm2835-unicam: Always service interrupts - sc16is7xx: Fix for hardware flow control - drm/vc4: Fix VIC usage with Broadcast RGB - staging: vc04_services: mmal-vchiq: Update parameters list - staging:vc04_services: bcm2835-codec: Request headers with I-frame - staging:vc04_services: bcm2835-codec: Avoid fragmenting buffers - staging:vc04_services: bcm2835-camera: Request headers with I-frame - configs: Restore missing NF_TABLES settings - overlays: Fix audio parameter of vc4-kms-v3d - Switch to snd_soc_dai_set_bclk_ratio - media: bcm2835-unicam: Retain packing information on G_FMT - zswap: Defer zswap initialisation - configs: Add ZSWAP=y, ZBUD=m, Z3FOLD=m - drm/vc4: Adopt the dma configuration from the HVS or V3D component - drm/vc4: Add FKMS as an acceptable node for dma ranges. - media: i2c: imx477: Return correct result on sensor id verification - staging: vchiq_arm: Clean up 40-bit DMA support - ARM: dts: Update for new VCHIQ BCM2711 DMA support - media: bcm2835-unicam: change minimum number of vb2_queue buffers to 1 - dt-bindings: Add Broadcom AVS RO thermal - thermal: Add BCM2711 thermal driver - ARM: dts: bcm2711: Enable thermal - ARM: configs: Build BCM2711 thermal as module - Revert "thermal: brcmstb_thermal: Correct SoC name" - Revert "thermal: brcmstb_thermal: Add BCM2838 support" - ARM: dts: bcm2711-rpi: Remove downstream thermal sensor node - configs: Switch to upstream thermal sensor for RPi 4 - BCM2711_THERMAL - configs: Build HWMON core into kernel - brcmfmac: BCM43436 needs dedicated firmware - overlays: i2c-rtc: Fix trickle-resistor-ohms param - overlays: gpio-shutdown: Add information for SysV init / inittab - overlays: gpio-shutdown: Add information for Raspberry Pi 1 Model B rev 1 - overlays: Add spi0 overlay to support sc16is752 - net: rtl8192cu: fix gcc misleading whitespace warning - overlays: i2c-rtc-gpio: Fix trickle-resistor-ohms param - media: bcm2835-isp: fix bytes per
[Kernel-packages] [Bug 1884110] Re: Enable ZFS for Raspberry Pi arm64
This bug was fixed in the package linux-raspi - 5.4.0-1015.15 --- linux-raspi (5.4.0-1015.15) focal; urgency=medium * focal/linux-raspi: 5.4.0-1015.15 -proposed tracker (LP: #1887056) [ Ubuntu: 5.4.0-42.46 ] * focal/linux: 5.4.0-42.46 -proposed tracker (LP: #1887069) * linux 4.15.0-109-generic network DoS regression vs -108 (LP: #1886668) - SAUCE: Revert "netprio_cgroup: Fix unlimited memory leak of v2 cgroups" linux-raspi (5.4.0-1014.14) focal; urgency=medium * focal/linux-raspi: 5.4.0-1014.14 -proposed tracker (LP: #1885841) * Add crda dependency (LP: #1877415) - [Packaging] raspi: Depend on crda * dtoverlay=uart4 breaks Raspberry Pi 4B boot (LP: #1875454) - SAUCE: arm: dts: Add 'brcm, bcm2835-pl011' for compatible for uart2-5 * aarch64 kernel module for exfat not in raspberry pi 4 build (LP: #1880503) - [Config] raspi: Set EXFAT_FS=m * Enable ZFS for Raspberry Pi arm64 (LP: #1884110) - [Config] raspi: Enable zfs modules for arm64 * focal/linux-raspi: Upstream raspberrypi patchset 2020-06-10 (LP: #1882930) - Revert "net: bcmgenet: Workaround for Pi 4B network issue" - Revert "gpiolib: Don't prevent IRQ usage of output GPIOs" - gpiolib: Don't prevent IRQ usage of output GPIOs - drm/vc4: Fix HDMI mode validation - clk-raspberrypi: Allow cpufreq driver to also adjust gpu clocks - bcm2835-dma: Add proper 40-bit DMA support - overlays: tc358743: Use intra-overlay fragments - overlays: Move "fixed-clock" nodes to the root - raspberrypi: dts: Switch to discrete ALSA devices - dt-bindings: media: i2c: Add IMX477 CMOS sensor binding - dtoverlays: Add IMX477 sensor overlay - media: i2c: Add driver for Sony IMX477 sensor - media: i2c: imx477: Add support for adaptive frame control - configs: Add imx477 sensor driver to all Raspberry Pi defconfigs - udmabuf: Remove deleted map/unmap handlers. - udmabuf: use cache_sgt_mapping option - udmabuf: add a pointer to the miscdevice in dma-buf private data - udmabuf: separate out creating/destroying scatter-table - udmabuf: implement begin_cpu_access/end_cpu_access hooks - udmabuf: fix dma-buf cpu access - dma-buf: Add dma-buf heaps framework - dma-buf: heaps: Add heap helpers - dma-buf: heaps: Add system heap to dmabuf heaps - dma-buf: heaps: Add CMA heap to dmabuf heaps - kselftests: Add dma-heap test - dma-buf: heaps: Use _IOCTL_ for userspace IOCTL identifier - dma-buf: heaps: Remove redundant heap identifier from system heap name - dma-buf: fix resource leak on -ENOTTY error return path - dma-heap: Make the symbol 'dma_heap_ioctl_cmds' static - defconfig: Add CMA and system dma-heaps to the config - ARM: dts: Enable firmware-clocks on all Pis - configs: Include the firmware-clocks driver - configs: Use the upstream cpufreq driver - media: bcm2835-unicam: Always service interrupts - sc16is7xx: Fix for hardware flow control - drm/vc4: Fix VIC usage with Broadcast RGB - staging: vc04_services: mmal-vchiq: Update parameters list - staging:vc04_services: bcm2835-codec: Request headers with I-frame - staging:vc04_services: bcm2835-codec: Avoid fragmenting buffers - staging:vc04_services: bcm2835-camera: Request headers with I-frame - configs: Restore missing NF_TABLES settings - overlays: Fix audio parameter of vc4-kms-v3d - Switch to snd_soc_dai_set_bclk_ratio - media: bcm2835-unicam: Retain packing information on G_FMT - zswap: Defer zswap initialisation - configs: Add ZSWAP=y, ZBUD=m, Z3FOLD=m - drm/vc4: Adopt the dma configuration from the HVS or V3D component - drm/vc4: Add FKMS as an acceptable node for dma ranges. - media: i2c: imx477: Return correct result on sensor id verification - staging: vchiq_arm: Clean up 40-bit DMA support - ARM: dts: Update for new VCHIQ BCM2711 DMA support - media: bcm2835-unicam: change minimum number of vb2_queue buffers to 1 - dt-bindings: Add Broadcom AVS RO thermal - thermal: Add BCM2711 thermal driver - ARM: dts: bcm2711: Enable thermal - ARM: configs: Build BCM2711 thermal as module - Revert "thermal: brcmstb_thermal: Correct SoC name" - Revert "thermal: brcmstb_thermal: Add BCM2838 support" - ARM: dts: bcm2711-rpi: Remove downstream thermal sensor node - configs: Switch to upstream thermal sensor for RPi 4 - BCM2711_THERMAL - configs: Build HWMON core into kernel - brcmfmac: BCM43436 needs dedicated firmware - overlays: i2c-rtc: Fix trickle-resistor-ohms param - overlays: gpio-shutdown: Add information for SysV init / inittab - overlays: gpio-shutdown: Add information for Raspberry Pi 1 Model B rev 1 - overlays: Add spi0 overlay to support sc16is752 - net: rtl8192cu: fix gcc misleading whitespace warning - overlays: i2c-rtc-gpio: Fix trickle-resistor-ohms param - media: bcm2835-isp: fix bytes per
[Kernel-packages] [Bug 1880503] Re: aarch64 kernel module for exfat not in raspberry pi 4 build
This bug was fixed in the package linux-raspi - 5.4.0-1015.15 --- linux-raspi (5.4.0-1015.15) focal; urgency=medium * focal/linux-raspi: 5.4.0-1015.15 -proposed tracker (LP: #1887056) [ Ubuntu: 5.4.0-42.46 ] * focal/linux: 5.4.0-42.46 -proposed tracker (LP: #1887069) * linux 4.15.0-109-generic network DoS regression vs -108 (LP: #1886668) - SAUCE: Revert "netprio_cgroup: Fix unlimited memory leak of v2 cgroups" linux-raspi (5.4.0-1014.14) focal; urgency=medium * focal/linux-raspi: 5.4.0-1014.14 -proposed tracker (LP: #1885841) * Add crda dependency (LP: #1877415) - [Packaging] raspi: Depend on crda * dtoverlay=uart4 breaks Raspberry Pi 4B boot (LP: #1875454) - SAUCE: arm: dts: Add 'brcm, bcm2835-pl011' for compatible for uart2-5 * aarch64 kernel module for exfat not in raspberry pi 4 build (LP: #1880503) - [Config] raspi: Set EXFAT_FS=m * Enable ZFS for Raspberry Pi arm64 (LP: #1884110) - [Config] raspi: Enable zfs modules for arm64 * focal/linux-raspi: Upstream raspberrypi patchset 2020-06-10 (LP: #1882930) - Revert "net: bcmgenet: Workaround for Pi 4B network issue" - Revert "gpiolib: Don't prevent IRQ usage of output GPIOs" - gpiolib: Don't prevent IRQ usage of output GPIOs - drm/vc4: Fix HDMI mode validation - clk-raspberrypi: Allow cpufreq driver to also adjust gpu clocks - bcm2835-dma: Add proper 40-bit DMA support - overlays: tc358743: Use intra-overlay fragments - overlays: Move "fixed-clock" nodes to the root - raspberrypi: dts: Switch to discrete ALSA devices - dt-bindings: media: i2c: Add IMX477 CMOS sensor binding - dtoverlays: Add IMX477 sensor overlay - media: i2c: Add driver for Sony IMX477 sensor - media: i2c: imx477: Add support for adaptive frame control - configs: Add imx477 sensor driver to all Raspberry Pi defconfigs - udmabuf: Remove deleted map/unmap handlers. - udmabuf: use cache_sgt_mapping option - udmabuf: add a pointer to the miscdevice in dma-buf private data - udmabuf: separate out creating/destroying scatter-table - udmabuf: implement begin_cpu_access/end_cpu_access hooks - udmabuf: fix dma-buf cpu access - dma-buf: Add dma-buf heaps framework - dma-buf: heaps: Add heap helpers - dma-buf: heaps: Add system heap to dmabuf heaps - dma-buf: heaps: Add CMA heap to dmabuf heaps - kselftests: Add dma-heap test - dma-buf: heaps: Use _IOCTL_ for userspace IOCTL identifier - dma-buf: heaps: Remove redundant heap identifier from system heap name - dma-buf: fix resource leak on -ENOTTY error return path - dma-heap: Make the symbol 'dma_heap_ioctl_cmds' static - defconfig: Add CMA and system dma-heaps to the config - ARM: dts: Enable firmware-clocks on all Pis - configs: Include the firmware-clocks driver - configs: Use the upstream cpufreq driver - media: bcm2835-unicam: Always service interrupts - sc16is7xx: Fix for hardware flow control - drm/vc4: Fix VIC usage with Broadcast RGB - staging: vc04_services: mmal-vchiq: Update parameters list - staging:vc04_services: bcm2835-codec: Request headers with I-frame - staging:vc04_services: bcm2835-codec: Avoid fragmenting buffers - staging:vc04_services: bcm2835-camera: Request headers with I-frame - configs: Restore missing NF_TABLES settings - overlays: Fix audio parameter of vc4-kms-v3d - Switch to snd_soc_dai_set_bclk_ratio - media: bcm2835-unicam: Retain packing information on G_FMT - zswap: Defer zswap initialisation - configs: Add ZSWAP=y, ZBUD=m, Z3FOLD=m - drm/vc4: Adopt the dma configuration from the HVS or V3D component - drm/vc4: Add FKMS as an acceptable node for dma ranges. - media: i2c: imx477: Return correct result on sensor id verification - staging: vchiq_arm: Clean up 40-bit DMA support - ARM: dts: Update for new VCHIQ BCM2711 DMA support - media: bcm2835-unicam: change minimum number of vb2_queue buffers to 1 - dt-bindings: Add Broadcom AVS RO thermal - thermal: Add BCM2711 thermal driver - ARM: dts: bcm2711: Enable thermal - ARM: configs: Build BCM2711 thermal as module - Revert "thermal: brcmstb_thermal: Correct SoC name" - Revert "thermal: brcmstb_thermal: Add BCM2838 support" - ARM: dts: bcm2711-rpi: Remove downstream thermal sensor node - configs: Switch to upstream thermal sensor for RPi 4 - BCM2711_THERMAL - configs: Build HWMON core into kernel - brcmfmac: BCM43436 needs dedicated firmware - overlays: i2c-rtc: Fix trickle-resistor-ohms param - overlays: gpio-shutdown: Add information for SysV init / inittab - overlays: gpio-shutdown: Add information for Raspberry Pi 1 Model B rev 1 - overlays: Add spi0 overlay to support sc16is752 - net: rtl8192cu: fix gcc misleading whitespace warning - overlays: i2c-rtc-gpio: Fix trickle-resistor-ohms param - media: bcm2835-isp: fix bytes per
[Kernel-packages] [Bug 1886682] Re: linux-image-raspi provides zfs modules only for arm64
This bug was fixed in the package linux-meta-raspi - 5.4.0.1015.50 --- linux-meta-raspi (5.4.0.1015.50) focal; urgency=medium * Miscellaneous Ubuntu changes - [Packaging] Add transitionals for HWE kernels linux-meta-raspi (5.4.0.1015.16) focal; urgency=medium * Bump ABI 5.4.0-1015 linux-meta-raspi (5.4.0.1014.15) focal; urgency=medium * linux-image-raspi provides zfs modules only for arm64 (LP: #1886682) - [Packaging] Only provide zfs for arm64 linux-meta-raspi (5.4.0.1014.14) focal; urgency=medium * Bump ABI 5.4.0-1014 * Packaging resync (LP: #1786013) - [Packaging] resync debian/dkms-versions from main package * Enable ZFS for Raspberry Pi arm64 (LP: #1884110) - [Config] raspi: Enable zfs modules for arm64 -- Stefan Bader Tue, 21 Jul 2020 18:56:39 +0200 ** Changed in: linux-meta-raspi (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1886682 Title: linux-image-raspi provides zfs modules only for arm64 Status in linux-meta-raspi package in Ubuntu: Invalid Status in linux-meta-raspi-5.4 package in Ubuntu: Invalid Status in linux-meta-raspi-5.4 source package in Bionic: Fix Released Status in linux-meta-raspi source package in Focal: Fix Released Bug description: [Impact] The linux-image-raspi armhf package falsely claims that it provides zfs modules. Only the arm64 package actually does. [Test Case] $ apt-cache show linux-image-raspi | grep -P '^Provides|^Architecture' Architecture: armhf Provides: wireguard-modules (= 1.0.20200506-1~20.04.1), zfs-modules (= 0.8.3-1ubuntu12.1) [Regression Potential] Low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-raspi/+bug/1886682/+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 1848831]
I just got a fenvi FV-AX3000 card, which at its core uses an Intel AX200. I was getting the same log from the kernel as above with RT ucode: -110, until I did some more snooping around. I originally plugged in the card to one of the x16 slots on my motherboard (Gigabyte Z77X-UD5H motherboard, CPU is an Intel i7-3770k), which according to the user manual for the motherboard, due to my current configuration, should now be operating with x4 lanes (8x lanes for my GPU, x4 lanes for a 1x sound card, and x4 lanes for the 1x AX200). These lanes are managed directly by the CPU as far as I can tell, per CPU and motherboard documentation. It was in this configuration that I got the RT ucode errors, and the card refused to work on Windows as well. As per comment 7, I happened to have one poorly placed 1x PCI-E slot available (right under the GPU..., blocking some airflow to it). I switched the AX200 card to this 1x slot, which is managed by the motherboard's chipset instead of the CPU, and... the card loaded: [ 33.632318] cfg80211: Loading compiled-in X.509 certificates for regulatory database [ 33.633710] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' [ 33.637366] Intel(R) Wireless WiFi driver for Linux [ 33.637367] Copyright(c) 2003- 2015 Intel Corporation [ 33.637397] iwlwifi :06:00.0: enabling device (0100 -> 0102) [ 33.643015] iwlwifi :06:00.0: api flags index 2 larger than supported by driver [ 33.643021] iwlwifi :06:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 68.3.35.22 [ 33.643024] iwlwifi :06:00.0: Found debug destination: EXTERNAL_DRAM [ 33.643024] iwlwifi :06:00.0: Found debug configuration: 0 [ 33.643197] iwlwifi :06:00.0: loaded firmware version 53.c31ac674.0 cc-a0-53.ucode op_mode iwlmvm [ 33.643211] iwlwifi :06:00.0: Direct firmware load for iwl-debug-yoyo.bin failed with error -2 [ 33.654918] iwlwifi :06:00.0: Detected Intel(R) Wi-Fi 6 AX200 160MHz, REV=0x340 [ 33.845091] iwlwifi :06:00.0: base HW address: f8:e4:e3:00:a8:8e [ 33.857641] thermal thermal_zone3: failed to read out thermal zone (-61) [ 33.857974] systemd-udevd[2525]: Using default interface naming scheme 'v245'. [ 33.858295] systemd-udevd[2525]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable. [ 33.858372] iwlwifi :06:00.0 wlp6s0: renamed from wlan0 [ 33.877736] systemd-udevd[2525]: wlan0: Process 'net.sh wlp6s0 start' failed with exit code 1. [ 37.895263] wlp6s0: authenticate with c2:56:27:6e:77:44 [ 37.897414] wlp6s0: send auth to c2:56:27:6e:77:44 (try 1/3) [ 37.922976] wlp6s0: authenticated [ 37.926295] wlp6s0: associate with c2:56:27:6e:77:44 (try 1/3) [ 37.946948] wlp6s0: RX AssocResp from c2:56:27:6e:77:44 (capab=0x431 status=0 aid=2) [ 37.951616] wlp6s0: associated [ 37.964058] IPv6: ADDRCONF(NETDEV_CHANGE): wlp6s0: link becomes ready [ 76.920106] elogind-daemon[1845]: Removed session 2. [ 76.978916] elogind-daemon[1845]: Removed session 3. [ 77.529926] elogind-daemon[1845]: New session 3 of user root. [ 90.962303] elogind-daemon[1845]: Removed session 3. [ 90.971156] elogind-daemon[1845]: New session 4 of user gabriel. [ 92.317347] Bluetooth: RFCOMM TTY layer initialized [ 92.317351] Bluetooth: RFCOMM socket layer initialized [ 92.317352] Bluetooth: RFCOMM ver 1.11 [ 92.626219] usb 1-1.3: reset high-speed USB device number 5 using ehci-pci PCI-E is one of the parts of modern systems I'm less familiar with, but to me it sounds like the problem could be one of the following (or more, these are the ones I can think of): 1. Somehow either the AX200 or the surrounding electronics on the wifi card (I don't think there's much there, so I think it's just the AX200) fails to negotiate the number of lanes it needs properly. (I have another 1x card, an Asus sound card, and that negotiates fine). 2. There's a bug or a hardware defect on the AX200 preventing it from communicating properly with the CPU PCI-E controller. Like I mentioned earlier, I have another 1x PCI-E card connected to one of the ports that connects to the CPU PCI-E controller, and that one works wonderfully. 3. Maybe my CPU is old enough that there's some incompatibility between it and the AX200. Still, the motherboard x1 port works just fine (in fact, I'm submitting this over wifi using the AX200). Because I can reproduce this reliably, and can work around it, let me know what information you would need from me to debug this, if anything. -- 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/1848831 Title: Intel WiFi AX200 [8086:08b1] subsystem [8086:4070] firmware loading error resulting in no wifi Status in Gaming Edition: In Progress Status in linux-firmware package in Ubuntu: Confirmed Bug description: Ubuntu 19.10 - stock kernel - Intel AX200 PCI card in a desktop PC
[Kernel-packages] [Bug 1874567] Re: [nvidia] Rotating secondary monitor to portrait fails, results in landscape
jeremyszu, That's a crash in gnome-control-center occurring at the same time as a black screen. It's correlation of two issues, not causation of one by the other... Please report the crash in a new bug using these steps: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubuntu. https://bugs.launchpad.net/bugs/1874567 Title: [nvidia] Rotating secondary monitor to portrait fails, results in landscape Status in OEM Priority Project: New Status in gnome-control-center package in Ubuntu: Won't Fix Status in mutter package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-435 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-440 package in Ubuntu: Won't Fix Status in gnome-control-center source package in Focal: Won't Fix Status in mutter source package in Focal: Fix Committed Status in nvidia-graphics-drivers-340 source package in Focal: Won't Fix Status in nvidia-graphics-drivers-435 source package in Focal: Won't Fix Status in nvidia-graphics-drivers-440 source package in Focal: Won't Fix Bug description: [ Impact ] I have two monitors, with the secondary one rotated in a portrait orientation. Using the nvidia 440 drivers, the orientation is not applied when configuring in gnome settings (the displays go blank for a second, and then reappear in landscape orientation). Using nvidia settings, I can set the monitor rotation and offset correctly, however these settings do not persist on next boot (even when selecting to save to xorg.conf). When using the nouveau drivers, the orientation is applied correctly in gnome settings, and is persisted. [ Test case ] 1. Install nvidia drivers 2. Configure an external monitor to be in portrait mode in gnome-control-center 3. Apply the configuration 4. Expect configuration is properly working [ Regression potential ] Wrong screen size is set and panning is used. ProblemType: BugDistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .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 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME Date: Fri Apr 24 08:30:41 2020 DistUpgraded: 2020-04-20 18:27:13,972 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-26-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GK106 [GeForce GTX 660] [1462:2871] InstallationDate: Installed on 2018-05-01 (723 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Shuttle Inc. SZ77 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=d2c17cee-7c37-429f-9cbb-9484a159f182 ro quiet splash vt.handoff=7SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-20 (3 days ago) dmi.bios.date: 10/13/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.13 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: FZ77 dmi.board.vendor: Shuttle Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.13:bd10/13/2014:svnShuttleInc.:pnSZ77:pvr1.0:rvnShuttleInc.:rnFZ77:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: SZ77 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Shuttle Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A
[Kernel-packages] [Bug 1874567] Re: [nvidia] Rotating secondary monitor to portrait fails, results in landscape
@Marco, Hi, here is the steps when verifying mutter from focal-proposed: 1. Upgrade all packages to latest version in focal-updates. 2. Enable focal-proposed in source list 3. sudo apt install mutter 4. Configure external screen orientation by selecting "Portrait Right" 5. Screen orientation doesn't change but asking save changes. 6. Press "Revert changes" 7. Configure external screen orientation by selecting "Portrait Right" again. 8. Screen goes to black screen. Attachment is the journal log. ``` Jul 24 03:02:18 u kernel: show_signal_msg: 38 callbacks suppressed Jul 24 03:02:18 u kernel: gnome-control-c[3252]: segfault at 7fff58ce6ff8 ip 7fa5ef8b114c sp 7fff58ce7000 error 6 in libc-2.31.so[7fa5ef841000+178000] Jul 24 03:02:18 u kernel: Code: 1f 80 00 00 00 00 e8 b3 bb ff ff eb d1 90 f3 0f 1e fa 48 85 d2 0f 84 63 01 00 00 41 57 49 89 ff 41 56 49 89 d6 41 55 49 89 d5 <41> 54 4c 8d 25 4b 77 15 00 55 48 8d 2d ab 84 15 00 53 4c 29 e5 48 ``` ** Attachment added: "journal.log" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1874567/+attachment/5395509/+files/journal.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubuntu. https://bugs.launchpad.net/bugs/1874567 Title: [nvidia] Rotating secondary monitor to portrait fails, results in landscape Status in OEM Priority Project: New Status in gnome-control-center package in Ubuntu: Won't Fix Status in mutter package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-435 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-440 package in Ubuntu: Won't Fix Status in gnome-control-center source package in Focal: Won't Fix Status in mutter source package in Focal: Fix Committed Status in nvidia-graphics-drivers-340 source package in Focal: Won't Fix Status in nvidia-graphics-drivers-435 source package in Focal: Won't Fix Status in nvidia-graphics-drivers-440 source package in Focal: Won't Fix Bug description: [ Impact ] I have two monitors, with the secondary one rotated in a portrait orientation. Using the nvidia 440 drivers, the orientation is not applied when configuring in gnome settings (the displays go blank for a second, and then reappear in landscape orientation). Using nvidia settings, I can set the monitor rotation and offset correctly, however these settings do not persist on next boot (even when selecting to save to xorg.conf). When using the nouveau drivers, the orientation is applied correctly in gnome settings, and is persisted. [ Test case ] 1. Install nvidia drivers 2. Configure an external monitor to be in portrait mode in gnome-control-center 3. Apply the configuration 4. Expect configuration is properly working [ Regression potential ] Wrong screen size is set and panning is used. ProblemType: BugDistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .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 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME Date: Fri Apr 24 08:30:41 2020 DistUpgraded: 2020-04-20 18:27:13,972 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-26-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GK106 [GeForce GTX 660] [1462:2871] InstallationDate: Installed on 2018-05-01 (723 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Shuttle Inc. SZ77 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=d2c17cee-7c37-429f-9cbb-9484a159f182 ro quiet splash vt.handoff=7SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-20 (3 days ago) dmi.bios.date: 10/13/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.13
[Kernel-packages] [Bug 1888796] [NEW] package zfs-initramfs 0.8.3-1ubuntu12.2 failed to install/upgrade: problemi con le dipendenze - lasciato non configurato
Public bug reported: zfs-mount --configure fails at upgrade The error is: Configurazione di zfsutils-linux (0.8.3-1ubuntu12.2)... zfs-import-scan.service is a disabled or a static unit, not starting it. zfs-import-scan.service is a disabled or a static unit, not starting it. Job for zfs-mount.service failed because the control process exited with error code. See "systemctl status zfs-mount.service" and "journalctl -xe" for details. invoke-rc.d: initscript zfs-mount, action "start" failed. ● zfs-mount.service - Mount ZFS filesystems Loaded: loaded (/lib/systemd/system/zfs-mount.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Fri 2020-07-24 08:50:10 CEST; 4ms ago Docs: man:zfs(8) Process: 1079486 ExecStart=/sbin/zfs mount -a (code=exited, status=1/FAILURE) Main PID: 1079486 (code=exited, status=1/FAILURE) lug 24 08:50:10 Axy systemd[1]: Starting Mount ZFS filesystems... lug 24 08:50:10 Axy zfs[1079486]: cannot mount '/tmp': directory is not empty lug 24 08:50:10 Axy systemd[1]: zfs-mount.service: Main process exited, code=exited, status=1/FAILURE lug 24 08:50:10 Axy systemd[1]: zfs-mount.service: Failed with result 'exit-code'. lug 24 08:50:10 Axy systemd[1]: Failed to start Mount ZFS filesystems. dpkg: errore nell'elaborare il pacchetto zfsutils-linux (--configure): il sottoprocesso installato pacchetto zfsutils-linux script post-installation ha restituito lo stato di errore 1 Regards ProblemType: Package DistroRelease: Ubuntu 20.04 Package: zfs-initramfs 0.8.3-1ubuntu12.2 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_40_44_generic_69 nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.4 AptOrdering: openjdk-11-jdk:amd64: Install openjdk-11-jdk-headless:amd64: Install openjdk-11-jre:amd64: Install openjdk-11-jre-headless:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Jul 24 06:30:15 2020 ErrorMessage: problemi con le dipendenze - lasciato non configurato InstallationDate: Installed on 2014-06-11 (2234 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: zfs-linux Title: package zfs-initramfs 0.8.3-1ubuntu12.2 failed to install/upgrade: problemi con le dipendenze - lasciato non configurato UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: zfs-linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal third-party-packages -- 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/1888796 Title: package zfs-initramfs 0.8.3-1ubuntu12.2 failed to install/upgrade: problemi con le dipendenze - lasciato non configurato Status in zfs-linux package in Ubuntu: New Bug description: zfs-mount --configure fails at upgrade The error is: Configurazione di zfsutils-linux (0.8.3-1ubuntu12.2)... zfs-import-scan.service is a disabled or a static unit, not starting it. zfs-import-scan.service is a disabled or a static unit, not starting it. Job for zfs-mount.service failed because the control process exited with error code. See "systemctl status zfs-mount.service" and "journalctl -xe" for details. invoke-rc.d: initscript zfs-mount, action "start" failed. ● zfs-mount.service - Mount ZFS filesystems Loaded: loaded (/lib/systemd/system/zfs-mount.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Fri 2020-07-24 08:50:10 CEST; 4ms ago Docs: man:zfs(8) Process: 1079486 ExecStart=/sbin/zfs mount -a (code=exited, status=1/FAILURE) Main PID: 1079486 (code=exited, status=1/FAILURE) lug 24 08:50:10 Axy systemd[1]: Starting Mount ZFS filesystems... lug 24 08:50:10 Axy zfs[1079486]: cannot mount '/tmp': directory is not empty lug 24 08:50:10 Axy systemd[1]: zfs-mount.service: Main process exited, code=exited, status=1/FAILURE lug 24 08:50:10 Axy systemd[1]: zfs-mount.service: Failed with result 'exit-code'. lug 24 08:50:10 Axy systemd[1]: Failed to start Mount ZFS filesystems. dpkg: errore nell'elaborare il pacchetto zfsutils-linux (--configure): il sottoprocesso installato pacchetto zfsutils-linux script post-installation ha restituito lo stato di errore 1 Regards ProblemType: Package DistroRelease: Ubuntu 20.04 Package: zfs-initramfs 0.8.3-1ubuntu12.2 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_40_44_generic_69 nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.4
[Kernel-packages] [Bug 1822937] Re: NVIDIA settings won't write to /etc/xorg
xorg.conf ** Attachment added: "xorg.conf" https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1822937/+attachment/5395496/+files/xorg.conf -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1822937 Title: NVIDIA settings won't write to /etc/xorg Status in nvidia-settings package in Ubuntu: Fix Released Status in nvidia-settings source package in Disco: Won't Fix Bug description: I tried running it with root (`sudo nvidia-settings`) and without. I also generated an xorg file with `nvidia-xconfig`, and do the same thing, but it still won't work. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nvidia-settings 418.56-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: KDE Date: Wed Apr 3 00:33:48 2019 InstallationDate: Installed on 2019-04-02 (0 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.1) SourcePackage: nvidia-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1822937/+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 1822937] Re: NVIDIA settings won't write to /etc/xorg
When using nvidia drivers, I get 2 Xorg logs, as I understand this is normal
behavior, since on a new system, when switching to nvidia drivers, the same
thing happens. When changing settings in nvidia-settings, the logs are updated
only in Xorg.1.log.
The settings are overwritten on reboot, than overwritten, I did not understand.
~ / .config / monitors.xml removed.
Xorg.1.log
.
.
.
[ 699.513] (**) NVIDIA(0): Option "MetaModes" "DP-4: 1920x1080_60
+1080+290, DP-0: 1920x1080_60 +3000+275, DP-2: 1920x1080_60 +0+0
{rotation=right}"
.
.
.
[ 700.417] (II) NVIDIA(0): Setting mode "DP-4: 1920x1080_60 @1920x1080
+1080+290 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}, DP-2: 1920x1080_60
@1080x1920 +0+0 {ViewPortIn=1080x1920, ViewPortOut=1920x1080+0+0, Rotation=270}"
[ 700.668] (II) event7 - Razer Razer DeathAdder: SYN_DROPPED event - some
input events have been lost.
[ 700.700] (II) NVIDIA(0): Setting mode "DP-4: 1920x1080_60 @1920x1080
+1080+290 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}"
[ 700.850] (II) NVIDIA(0): Setting mode "NULL"
[ 700.892] (II) NVIDIA(0): Setting mode "DP-0: nvidia-auto-select @1920x1080
+3840+0 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}"
[ 700.938] (II) NVIDIA(0): Setting mode "DP-0: nvidia-auto-select @1920x1080
+3840+0 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}, DP-2:
nvidia-auto-select @1920x1080 +0+0 {ViewPortIn=1920x1080,
ViewPortOut=1920x1080+0+0}"
[ 701.127] (II) NVIDIA(0): Setting mode "DP-4: nvidia-auto-select @1920x1080
+1920+0 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}, DP-0:
nvidia-auto-select @1920x1080 +3840+0 {ViewPortIn=1920x1080,
ViewPortOut=1920x1080+0+0}, DP-2: nvidia-auto-select @1920x1080 +0+0
{ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}"
.
.
.
Ubuntu 20.04
Nvidia 440.100
3 monitors
** Attachment added: "Xorg.1.log"
https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1822937/+attachment/5395491/+files/Xorg.1.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1822937
Title:
NVIDIA settings won't write to /etc/xorg
Status in nvidia-settings package in Ubuntu:
Fix Released
Status in nvidia-settings source package in Disco:
Won't Fix
Bug description:
I tried running it with root (`sudo nvidia-settings`) and without.
I also generated an xorg file with `nvidia-xconfig`, and do the same
thing, but it still won't work.
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: nvidia-settings 418.56-0ubuntu1
ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
Uname: Linux 5.0.0-8-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu23
Architecture: amd64
CurrentDesktop: KDE
Date: Wed Apr 3 00:33:48 2019
InstallationDate: Installed on 2019-04-02 (0 days ago)
InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.1)
SourcePackage: nvidia-settings
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1822937/+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 1822937] Re: NVIDIA settings won't write to /etc/xorg
Xorg.0.log ** Attachment added: "Xorg.0.log" https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1822937/+attachment/5395492/+files/Xorg.0.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1822937 Title: NVIDIA settings won't write to /etc/xorg Status in nvidia-settings package in Ubuntu: Fix Released Status in nvidia-settings source package in Disco: Won't Fix Bug description: I tried running it with root (`sudo nvidia-settings`) and without. I also generated an xorg file with `nvidia-xconfig`, and do the same thing, but it still won't work. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nvidia-settings 418.56-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: KDE Date: Wed Apr 3 00:33:48 2019 InstallationDate: Installed on 2019-04-02 (0 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.1) SourcePackage: nvidia-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1822937/+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 1888647] Re: Realtek wifi dont work after update
Had the same issue going from 5.3.0-62 to 5.4.0-42 on Ubuntu 18.04 Can also confirm it works with the ppa. Thanks! -- 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/1888647 Title: Realtek wifi dont work after update Status in linux-firmware package in Ubuntu: Triaged Bug description: lsb_release -rd Description:Ubuntu 18.04.4 LTS Release:18.04 apt-cache policy linux-firmware linux-firmware: Installed: 1.173.19 Candidate: 1.173.19 Version table: *** 1.173.19 500 500 http://ru.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://ru.archive.ubuntu.com/ubuntu bionic-updates/main i386 Packages 100 /var/lib/dpkg/status 1.173.18 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main i386 Packages 1.173 500 500 http://ru.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 500 http://ru.archive.ubuntu.com/ubuntu bionic/main i386 Packages PCI Wifi adapter dont work after update Part of kern.log Jul 23 14:04:25 pao-note kernel: [0.570519] pci :02:00.0: [10ec:c822] type 00 class 0x028000 Jul 23 14:04:25 pao-note kernel: [0.570564] pci :02:00.0: reg 0x10: [io 0x2000-0x20ff] Jul 23 14:04:25 pao-note kernel: [0.570598] pci :02:00.0: reg 0x18: [mem 0xb130-0xb130 64bit] Jul 23 14:04:25 pao-note kernel: [0.570758] pci :02:00.0: supports D1 D2 Jul 23 14:04:25 pao-note kernel: [0.570759] pci :02:00.0: PME# supported from D0 D1 D2 D3hot D3cold Jul 23 14:04:25 pao-note kernel: [ 21.479711] rtw_pci :02:00.0: enabling device ( -> 0003) Jul 23 14:04:25 pao-note kernel: [ 21.479783] rtw_pci :02:00.0: Direct firmware load for rtw88/rtw8822c_wow_fw.bin failed with error -2 Jul 23 14:04:25 pao-note kernel: [ 21.479784] rtw_pci :02:00.0: failed to request firmware Jul 23 14:04:25 pao-note kernel: [ 21.480312] rtw_pci :02:00.0: Firmware version 5.0.0, H2C version 14 Jul 23 14:04:25 pao-note kernel: [ 21.593905] rtw_pci :02:00.0 wlp2s0: renamed from wlan0 Jul 23 14:04:25 pao-note kernel: [ 22.164022] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:04:25 pao-note kernel: [ 22.176798] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:04:25 pao-note kernel: [ 22.177910] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:04:35 pao-note kernel: [ 32.014995] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:04:35 pao-note kernel: [ 32.017051] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:04:45 pao-note kernel: [ 42.012048] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:04:45 pao-note kernel: [ 42.013137] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:04:55 pao-note kernel: [ 52.011861] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:04:55 pao-note kernel: [ 52.013348] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:05:05 pao-note kernel: [ 62.203876] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:05:05 pao-note kernel: [ 62.205477] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:05:15 pao-note kernel: [ 72.262757] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:05:15 pao-note kernel: [ 72.263944] rtw_pci :02:00.0: failed to wait firmware completion lspci 00:00.0 Host bridge: Intel Corporation Device 9b61 (rev 0c) 00:02.0 VGA compatible controller: Intel Corporation Device 9b41 (rev 02) 00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 0c) 00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th Gen Core Processor Gaussian Mixture Model 00:12.0 Signal processing controller: Intel Corporation Device 02f9 00:14.0 USB controller: Intel Corporation Device 02ed 00:14.2 RAM memory: Intel Corporation Device 02ef 00:15.0 Serial bus controller [0c80]: Intel Corporation Device 02e8 00:16.0 Communication controller: Intel Corporation Device 02e0 00:17.0 SATA controller: Intel Corporation Device 02d3 00:1d.0 PCI bridge: Intel Corporation Device 02b0 (rev f0) 00:1d.1 PCI bridge: Intel Corporation Device 02b1 (rev f0) 00:1d.2 PCI bridge: Intel Corporation Device 02b2 (rev f0) 00:1d.4 PCI bridge: Intel Corporation Device 02b4 (rev f0) 00:1e.0 Communication controller: Intel Corporation Device 02a8 00:1f.0 ISA bridge: Intel Corporation Device 0284 00:1f.3 Audio device: Intel Corporation Device 02c8 00:1f.4 SMBus: Intel Corporation Device 02a3 00:1f.5
