[Kernel-packages] [Bug 1881541] [NEW] Prevent segfault immediately after install when zfs kernel module isn't loaded
Public bug reported: Install zsys on a non ZFS system without the kernel module loaded leaded to a segfault. ** Affects: zfs-linux (Ubuntu) Importance: Undecided Status: New -- 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/1881541 Title: Prevent segfault immediately after install when zfs kernel module isn't loaded Status in zfs-linux package in Ubuntu: New Bug description: Install zsys on a non ZFS system without the kernel module loaded leaded to a segfault. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1881541/+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 1880032] Re: [linux-azure] Enable Hibernation on The 18.04 and 20.04 5.4 Kernels
FYI: the patch "net/mlx5: Fix crash upon suspend/resume" is in v5.7 now (i.e. today's latest mainline): https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.7=8fc3e29be9248048f449793502c15af329f35c6e -- 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/1880032 Title: [linux-azure] Enable Hibernation on The 18.04 and 20.04 5.4 Kernels Status in linux-azure package in Ubuntu: New Bug description: Microsoft would like to request commits to enable VM hibernation in the Azure 5.4 kernels for 18.04 and 20.04. Some of the commits needed to enable VM hibernation were included in mainline 5.4 and older. However, 24 commits were added in 5.5 and later, which are required in the 5.4 kernel. The list of commits requested are: 38dce4195f0d x86/hyperv: Properly suspend/resume reenlightenment notifications 2351f8d295ed PM: hibernate: Freeze kernel threads in software_resume() 421f090c819d x86/hyperv: Suspend/resume the VP assist page for hibernation 1a06d017fb3f Drivers: hv: vmbus: Fix Suspend-to-Idle for Generation-2 VM 3704a6a44579 PM: hibernate: Propagate the return value of hibernation_restore() 54e19d34011f hv_utils: Add the support of hibernation ffd1d4a49336 hv_utils: Support host-initiated hibernation request 3e9c72056ed5 hv_utils: Support host-initiated restart request 9fc3c01a1fae6 Tools: hv: Reopen the devices if read() or write() returns 05bd330a7fd8 x86/hyperv: Suspend/resume the hypercall page for hibernation 382a46221757 video: hyperv_fb: Fix hibernation for the deferred IO feature e2379b30324c Input: hyperv-keyboard: Add the support of hibernation ac82fc8327088 PCI: hv: Add hibernation support a8e37506e79a PCI: hv: Reorganize the code in preparation of hibernation 1349401ff1aa4 clocksource/drivers/hyper-v: Suspend/resume Hyper-V clocksource for hibernation af13f9ed6f9a HID: hyperv: Add the support of hibernation 25bd2b2f1f053 hv_balloon: Add the support of hibernation b96f86534fa31 x86/hyperv: Implement hv_is_hibernation_supported() 4df4cb9e99f83 x86/hyperv: Initialize clockevents earlier in CPU onlining 0efeea5fb1535 hv_netvsc: Add the support of hibernation 2194c2eb6717f hv_sock: Add the support of hibernation 1ecf302021040 video: hyperv_fb: Add the support of hibernation 56fb105859345 scsi: storvsc: Add the support of hibernation f2c33ccacb2d4 PCI/PM: Always return devices to D0 when thawing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1880032/+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 1810215] Re: for Seagate USB drive enclosures, SAT (e.g. smartmontools, hdparm) works on kernel 4.13 but not on 4.15
See also: https://www.smartmontools.org/wiki/SAT-with-UAS-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/1810215 Title: for Seagate USB drive enclosures, SAT (e.g. smartmontools, hdparm) works on kernel 4.13 but not on 4.15 Status in linux package in Ubuntu: Confirmed Bug description: smartctl -d sat -i /dev/sda work on 16.04 kernel 4.13 but on 4.15. Here is data from 16.04 root@server:~# uname -a Linux server 4.13.0-45-generic #50~16.04.1-Ubuntu SMP Wed May 30 11:18:27 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux root@server:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04.5 LTS Release: 16.04 Codename: xenial root@server:~# smartctl -d sat -i /dev/sda smartctl 6.5 2016-01-24 r4214 [x86_64-linux-4.13.0-45-generic] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Device Model: ST8000DM004-2CX188 Serial Number:ZCT07YN6 LU WWN Device Id: 5 000c50 0b1f2a4d2 Firmware Version: 0001 User Capacity:8,001,563,222,016 bytes [8.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate:5425 rpm Form Factor: 3.5 inches Device is:Not in smartctl database [for details use: -P showall] ATA Version is: ACS-3 T13/2161-D revision 5 SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is:Tue Jan 1 16:57:48 2019 EST SMART support is: Available - device has SMART capability. SMART support is: Enabled root@server:~# here is data from 18.04:root@mike-desktop:/tmp# uname -a Linux mike-desktop 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux root@mike-desktop:/tmp# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.1 LTS Release: 18.04 Codename: bionic root@mike-desktop:/tmp# smartctl -d sat -i /dev/sdd smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.15.0-36-generic] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org Read Device Identity failed: scsi error unsupported field in scsi command A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options. dmesg on 18.04 showing drive is connected /dev/sdd: [6041017.984544] usb 3-2.4: new SuperSpeed USB device number 6 using xhci_hcd [6041018.009417] usb 3-2.4: New USB device found, idVendor=0bc2, idProduct=331a [6041018.009424] usb 3-2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [6041018.009428] usb 3-2.4: Product: Expansion Desk [6041018.009432] usb 3-2.4: Manufacturer: Seagate [6041018.009435] usb 3-2.4: SerialNumber: NAAA7HWG [6041018.015808] scsi host5: uas [6041018.016527] scsi 5:0:0:0: Direct-Access Seagate Expansion Desk 0915 PQ: 0 ANSI: 6 [6041018.017645] sd 5:0:0:0: Attached scsi generic sg3 type 0 [6041030.357108] sd 5:0:0:0: [sdd] 15628053167 512-byte logical blocks: (8.00 TB/7.28 TiB) [6041030.357112] sd 5:0:0:0: [sdd] 4096-byte physical blocks [6041030.357265] sd 5:0:0:0: [sdd] Write Protect is off [6041030.357268] sd 5:0:0:0: [sdd] Mode Sense: 53 00 00 08 [6041030.357562] sd 5:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [6041030.493932] sdd: sdd1 sdd9 [6041030.495310] sd 5:0:0:0: [sdd] Attached SCSI disk ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: smartmontools 6.5+svn4324-1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Tue Jan 1 16:53:16 2019 InstallationDate: Installed on 2018-02-23 (312 days ago) InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: smartmontools UpgradeStatus: Upgraded to bionic on 2018-10-21 (72 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810215/+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 1881549] Re: Upgraded to 20.04 and wifi broke
** 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/1881549 Title: Upgraded to 20.04 and wifi broke Status in linux package in Ubuntu: Confirmed Bug description: Upgraded to 20.04 and the wifi broke. It was working fine on 18.04. Tried a variety of things with apw but nada. /var/log attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881549/+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 1856434] Re: blk_update_request: I/O error, dev sdb, sector 976772992 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
vmware deve's comment for the issue "blk_update_request: I/O error, dev sda, sector 3270728 op 0x9 VM ubuntu-20.04-live-server in ESXi 7.0GA" : I noticed that when it's happening, abnormal kernel log: [0.00] ? lockdown_lsm_init+0x21/0x25 [0.00] Kernel is locked down from EFI Secure Boot mode; see man kernel_lockdown.7 . [ 66.261508] Lockdown: fwupd: /dev/mem,kmem,port is restricted; see man kernel_lockdown.7 [ 233.169823] ata3: SATA link down (SStatus 0 SControl 300) [ 238.577700] ata3: SATA link down (SStatus 0 SControl 300) [ 243.953448] ata3: SATA link down (SStatus 0 SControl 300) [ 243.953455] ata3.00: disabled [ 243.953481] sr 2:0:0:0: rejecting I/O to offline device [ 243.958034] ata3.00: detaching (SCSI 2:0:0:0) [ 304.517077] sd 3:0:0:0: [sda] tag#55 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [ 304.517081] sd 3:0:0:0: [sda] tag#55 Sense Key : Vendor Specific(9) [current] [ 304.517086] sd 3:0:0:0: [sda] tag#55 <>ASC=0x80 <>ASCQ=0x85 [ 304.517090] sd 3:0:0:0: [sda] tag#55 CDB: Write same(16) 93 08 00 00 00 00 00 31 e7 e8 00 00 00 18 00 00 [ 304.517100] blk_update_request: I/O error, dev sda, sector 3270632 op 0x9:(WRITE_ZEROES) flags 0x800 phys_seg 0 prio class 0 [ 314.319273] sd 3:0:0:0: [sda] tag#11 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [ 314.319275] sd 3:0:0:0: [sda] tag#11 Sense Key : Vendor Specific(9) [current] [ 314.319278] sd 3:0:0:0: [sda] tag#11 <>ASC=0x80 <>ASCQ=0x85 [ 314.319295] sd 3:0:0:0: [sda] tag#11 CDB: Write same(16) 93 08 00 00 00 00 00 31 e8 10 00 00 00 18 00 00 [ 314.319299] blk_update_request: I/O error, dev sda, sector 3270672 op 0x9:(WRITE_ZEROES) flags 0x800 phys_seg 0 prio class 0 And no error log in hostside. Noticed you enabled secure boot in uefi and ubuntu are configured with lockdown vmware@ubuntu:~$ cat /boot/config-5.4.0-26-generic | grep LOCK_DOWN CONFIG_LOCK_DOWN_IN_SECURE_BOOT=y CONFIG_LOCK_DOWN_KERNEL_FORCE_NONE=y So the error should caused by uefi lockdown feature. Please refer to https://mjg59.dreamwidth.org/50577.html for more details. To workaroud this, echo 1 > /proc/sys/kernel/sysrq echo x > /proc/sysrq-trigger or you can use sudo mokutil --disable-validation to disable it. I tried "echo to /proc" way, the error msg disappered. You might try the second way. Anyway, it's an upstream bug. -- 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/1856434 Title: blk_update_request: I/O error, dev sdb, sector 976772992 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 Status in linux package in Ubuntu: Confirmed Bug description: 1) Ubuntu 19.10 2) unknown 3) no error 4) error in log app. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: htpc 9157 F pulseaudio /dev/snd/controlC1: htpc 9157 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-10-28 (48 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lxcbr0no wireless extensions. lono wireless extensions. enp3s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. GA-MA780G-UD3H Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic root=UUID=0fa008d8-2279-4e78-9043-161b7f514243 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 RelatedPackageVersions: linux-restricted-modules-5.3.0-23-generic N/A linux-backports-modules-5.3.0-23-generic N/A linux-firmware1.183.2 RfKill: Tags: wayland-session eoan Uname: Linux 5.3.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/13/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F6b dmi.board.name: GA-MA780G-UD3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF6b:bd07/13/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA780G-UD3H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA780G-UD3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-MA780G-UD3H dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856434/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to
[Kernel-packages] [Bug 1810215] Re: for Seagate USB drive enclosures, SAT (e.g. smartmontools, hdparm) works on kernel 4.13 but not on 4.15
For more information about this issue, see https://askubuntu.com/a/1106020/50254 TL;DR: Linux kernel disables 12 and 16 bit SATA Commands over UAS when used with Seagate HDD enclosures. This usb_storage quirk is "t" instead of "u" which forces the device into USB BOT mode. The only way to make S.M.A.R.T. to work with USB HDD enclosure is to use UAS without limitations - that is, no quirk of any kind. Note that full UAS support has been disabled on all Seagate enclosures by default because Seagate had such a poor track record with multiple products. The quirk "t" is enough to avoid the issue and it will not cause equal performance slowdown as the "u" quirk. Note that if you disable all quirks with known-bad Seagate enclosure the S.M.A.R.T. will work but you risk random data corruption if you write any data on the disk. I guess remounting the disk read-only, disabling the "t" quirk, doing S.M.A.R.T. query, re-enable the "t" quirk and remounting read- write could be considered a safe workaround if you really need the S.M.A.R.T. data. More details about possible usb_storage.quirks: https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.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/1810215 Title: for Seagate USB drive enclosures, SAT (e.g. smartmontools, hdparm) works on kernel 4.13 but not on 4.15 Status in linux package in Ubuntu: Confirmed Bug description: smartctl -d sat -i /dev/sda work on 16.04 kernel 4.13 but on 4.15. Here is data from 16.04 root@server:~# uname -a Linux server 4.13.0-45-generic #50~16.04.1-Ubuntu SMP Wed May 30 11:18:27 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux root@server:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04.5 LTS Release: 16.04 Codename: xenial root@server:~# smartctl -d sat -i /dev/sda smartctl 6.5 2016-01-24 r4214 [x86_64-linux-4.13.0-45-generic] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Device Model: ST8000DM004-2CX188 Serial Number:ZCT07YN6 LU WWN Device Id: 5 000c50 0b1f2a4d2 Firmware Version: 0001 User Capacity:8,001,563,222,016 bytes [8.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate:5425 rpm Form Factor: 3.5 inches Device is:Not in smartctl database [for details use: -P showall] ATA Version is: ACS-3 T13/2161-D revision 5 SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is:Tue Jan 1 16:57:48 2019 EST SMART support is: Available - device has SMART capability. SMART support is: Enabled root@server:~# here is data from 18.04:root@mike-desktop:/tmp# uname -a Linux mike-desktop 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux root@mike-desktop:/tmp# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.1 LTS Release: 18.04 Codename: bionic root@mike-desktop:/tmp# smartctl -d sat -i /dev/sdd smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.15.0-36-generic] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org Read Device Identity failed: scsi error unsupported field in scsi command A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options. dmesg on 18.04 showing drive is connected /dev/sdd: [6041017.984544] usb 3-2.4: new SuperSpeed USB device number 6 using xhci_hcd [6041018.009417] usb 3-2.4: New USB device found, idVendor=0bc2, idProduct=331a [6041018.009424] usb 3-2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [6041018.009428] usb 3-2.4: Product: Expansion Desk [6041018.009432] usb 3-2.4: Manufacturer: Seagate [6041018.009435] usb 3-2.4: SerialNumber: NAAA7HWG [6041018.015808] scsi host5: uas [6041018.016527] scsi 5:0:0:0: Direct-Access Seagate Expansion Desk 0915 PQ: 0 ANSI: 6 [6041018.017645] sd 5:0:0:0: Attached scsi generic sg3 type 0 [6041030.357108] sd 5:0:0:0: [sdd] 15628053167 512-byte logical blocks: (8.00 TB/7.28 TiB) [6041030.357112] sd 5:0:0:0: [sdd] 4096-byte physical blocks [6041030.357265] sd 5:0:0:0: [sdd] Write Protect is off [6041030.357268] sd 5:0:0:0: [sdd] Mode Sense: 53 00 00 08 [6041030.357562] sd 5:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [6041030.493932] sdd: sdd1 sdd9 [6041030.495310] sd 5:0:0:0: [sdd] Attached SCSI disk ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: smartmontools 6.5+svn4324-1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.5
[Kernel-packages] [Bug 1874588] Re: Flickering screen after waking up from Suspend
I had the same issue with Ryzen 5 3600x and Radeon 5600xt. For a different mouse flickering issue when using xrandr, I had to set following xrandr after I set correct resolution and panning. xrandr --output DisplayPort-2 --scale 0.x0. DisplayPort-2 is my primary display. With the above setting my mouse flickering went away. Surprisingly this also fixed the screen flickering issue after wake up from suspend. -- 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/1874588 Title: Flickering screen after waking up from Suspend Status in linux package in Ubuntu: Confirmed Bug description: Just did a fresh install of Ubuntu 20.04 LTS and everything was fine, display worked perfect. Then I put the machine in Suspend mode (by clicking on GUI button), left for 5 minutes, came back, woke up the machine (by clicking a key on the keyboard), and upon waking up, the display started flickering heavily. Relevant Specs (Sorry if I missed anything): AMD® Ryzen 9 3900x 12-core processor × 24 AMD® Radeon rx 5700 xt GNOME version 3.36.1 Windowing System X11 I am running 3 monitors: Samsung with resolution 3840x2160 and 2 LG monitors with resolution 1920x1080, all at 60Hz Most of the flickering is happening on Samsung, although once in a while, other monitors flicker a little bit as well. Things to note: When I switch Samsung to lower resolution, the flickering goes away. When I come back to 3840x2160, it comes back. When I switch to lower resolution, suspend and come back, everything is fine. If I reboot the machine, the display is fine until I suspend and wake up again (if I am in higher resolution). I tried changing the refresh rate of Samsung to 30.00 and 29.97 (the only two available when I turn off FreeSync), and the issue still persists. Turning FreeSync on and off does nothing. Thank you, Pavel. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-26-generic 5.4.0-26.30 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: pavel 1870 F pulseaudio /dev/snd/controlC0: pavel 1870 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 23 21:14:00 2020 InstallationDate: Installed on 2020-04-23 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=02f6301e-c22b-462d-a4e5-71a78b7eb203 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1405 dmi.board.asset.tag: Default string dmi.board.name: TUF GAMING X570-PLUS (WI-FI) dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1405:bd11/19/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX570-PLUS(WI-FI):rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874588/+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 1874194] Re: Ubuntu 20.04 HDMI connected, no boot
Confirmed as per suggestion in #75 - system boots to login no problem when quiet-splash is disabled on Lenovo x260 (intel graphics) Kernel 5.4.0-31-generic. If I return to default (quiet-splash enabled) system hangs on splash screen. Thanks -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874194 Title: Ubuntu 20.04 HDMI connected, no boot Status in linux package in Ubuntu: Incomplete Bug description: I have installed Ubuntu 20.04 (using the image created on 20 april) on my Dell XPS15 9560. This laptop has a Intel / nVidia combo. The problem i am facing is that when i have an external monitor connected to the laptop through the HDMI connector of the laptop, Ubuntu does not boot and hangs on the splash screen. I have not found any way to get logging on any kind. Before i was running Ubuntu 18.04 and did not have any problems with the monitor and HDMI cable. After boot is finished (without monitor connected) inserting the HDMI cable works fine and i can use the monitor and laptop screen without any problem. I have installed the preferred nVida proprietary driver. Also it does not matter if booting with nVidia selected or Intel selected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874194/+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 1866984] Re: linux-5.4 regression: hibernate-disk resumes instantly
Dear Daniel, Thank you for that work-around! The error message is a bit odd, as it says that it may lead to LESS powersaving. Even then, once hibernated there is no power draw anyway -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1866984 Title: linux-5.4 regression: hibernate-disk resumes instantly Status in hibernate package in Ubuntu: Confirmed Status in linux-5.4 package in Ubuntu: Confirmed Bug description: Since upgrading from 19.10 (eoan) to 20.04 (focal), hibernate-disk fails to properly hibernate and shutdown the system; instead, Ubuntu resumes instantly. $ sudo hibernate-disk [sudo] password for xyz: hibernate-disk:Warning: Tuxonice binary signature file not found. $ (Note that this warning has been there earlier and is presumably not associated with this bug.) Expected: Switch to console, memory-page writeout progress indication, poweroff Observed: Switch to console, very quickly switch back to X11 Excerpt from dmesg: [ 418.377514] usbcore: deregistering interface driver uvcvideo [ 419.227465] Filesystems sync: 0.006 seconds [ 419.227468] Freezing user space processes ... (elapsed 0.002 seconds) done. [ 419.229889] OOM killer disabled. [ 419.230429] PM: Marking nosave pages: [mem 0x-0x0fff] [ 419.230432] PM: Marking nosave pages: [mem 0x0009d000-0x000f] [ 419.230440] PM: Marking nosave pages: [mem 0x99438000-0x] [ 419.233760] PM: Basic memory bitmaps created [ 419.234176] PM: Preallocating image memory... done (allocated 1188843 pages) [ 420.040021] PM: Allocated 4755372 kbytes in 0.80 seconds (5944.21 MB/s) [ 420.040021] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 420.041324] printk: Suspending console(s) (use no_console_suspend to debug) [ 420.041755] wlp3s0: deauthenticating from cc:ce:1e:61:2e:d0 by local choice (Reason: 3=DEAUTH_LEAVING) [ 421.278599] ACPI: EC: interrupt blocked [ 421.297107] ACPI: Preparing to enter system sleep state S4 [ 421.301832] ACPI: EC: event blocked [ 421.301833] ACPI: EC: EC stopped [ 421.301834] PM: Saving platform NVS memory [ 421.302557] Disabling non-boot CPUs ... [ 421.303996] smpboot: CPU 1 is now offline [ 421.307624] smpboot: CPU 2 is now offline [ 421.309904] IRQ 129: no longer affine to CPU3 [ 421.310921] smpboot: CPU 3 is now offline [ 421.314818] smpboot: CPU 4 is now offline [ 421.317033] IRQ 16: no longer affine to CPU5 [ 421.317040] IRQ 132: no longer affine to CPU5 [ 421.318049] smpboot: CPU 5 is now offline [ 421.320365] IRQ 126: no longer affine to CPU6 [ 421.320373] IRQ 130: no longer affine to CPU6 [ 421.321405] smpboot: CPU 6 is now offline [ 421.325743] smpboot: CPU 7 is now offline [ 421.330059] PM: Creating hibernation image: [ 422.045974] PM: Need to copy 1182218 pages [ 422.045977] PM: Normal pages needed: 1182218 + 1024, available pages: 7053219 [ 423.427947] PM: Hibernation image created (1182218 pages copied) [ 421.330504] PM: Restoring platform NVS memory [ 421.330638] ACPI: EC: EC started [ 421.331412] Enabling non-boot CPUs ... [ 421.331453] x86: Booting SMP configuration: [ 421.331454] smpboot: Booting Node 0 Processor 1 APIC 0x2 [ 421.332297] CPU1 is up [ 421.332327] smpboot: Booting Node 0 Processor 2 APIC 0x4 [ 421.333137] CPU2 is up [ 421.333164] smpboot: Booting Node 0 Processor 3 APIC 0x6 [ 421.333987] CPU3 is up [ 421.334013] smpboot: Booting Node 0 Processor 4 APIC 0x1 [ 421.334926] CPU4 is up [ 421.334956] smpboot: Booting Node 0 Processor 5 APIC 0x3 [ 421.335640] CPU5 is up [ 421.335666] smpboot: Booting Node 0 Processor 6 APIC 0x5 [ 421.336447] CPU6 is up [ 421.336469] smpboot: Booting Node 0 Processor 7 APIC 0x7 [ 421.337232] CPU7 is up [ 421.340095] ACPI: Waking up from system sleep state S4 [ 421.347884] ACPI: EC: interrupt unblocked [ 421.390488] ACPI: EC: event unblocked [ 421.391425] tpm tpm0: tpm_try_transmit: send(): error -5 [ 421.403775] iwlwifi :03:00.0: Applying debug destination EXTERNAL_DRAM [ 421.553049] iwlwifi :03:00.0: Applying debug destination EXTERNAL_DRAM [ 421.603306] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. [ 421.634367] iwlwifi :03:00.0: FW already configured (0) - re-configuring [ 421.714565] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 421.715010] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded [ 421.715012] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out [ 421.715083] ata1.00: ACPI cmd ef/10:09:00:00:00:a0 (SET FEATURES) succeeded [ 421.715396] ata1.00: supports DRM functions and may not be
[Kernel-packages] [Bug 1881525] Re: in kernel amdgpu failed with W5500 [1002:7341]
** Tags added: oem-priority originate-from-1880678 timbuktu ** Tags removed: timbuktu -- 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/1881525 Title: in kernel amdgpu failed with W5500 [1002:7341] Status in HWE Next: New Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Bionic: In Progress Bug description: [Impact] [Fix] X-HWE-Bug: Bug #1880678 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-hotpie+X34 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-05-25 (6 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Package: linux-firmware 1.173.18+navi14 [origin: LP-PPA-shanelin-linux-firmware] PackageArchitecture: all ProcVersionSignature: Ubuntu 5.4.0-31.35~18.04.2-generic 5.4.34 Tags: bionic uec-images third-party-packages Uname: Linux 5.4.0-31-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1881525/+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 1881137] Re: Introduce the new NVIDIA 418-server and 440-server series, and update the current NVIDIA drivers
** Also affects: nvidia-graphics-drivers-440-server (Ubuntu) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-418-server (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881137 Title: Introduce the new NVIDIA 418-server and 440-server series, and update the current NVIDIA drivers Status in linux package in Ubuntu: Incomplete Status in linux-restricted-modules package in Ubuntu: New Status in nvidia-graphics-drivers-418-server package in Ubuntu: New Status in nvidia-graphics-drivers-440 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-440-server package in Ubuntu: New Status in linux source package in Bionic: Incomplete Status in linux-restricted-modules source package in Bionic: New Status in nvidia-graphics-drivers-418-server source package in Bionic: New Status in nvidia-graphics-drivers-440 source package in Bionic: New Status in nvidia-graphics-drivers-440-server source package in Bionic: New Status in linux source package in Focal: Incomplete Status in linux-restricted-modules source package in Focal: New Status in nvidia-graphics-drivers-418-server source package in Focal: New Status in nvidia-graphics-drivers-440 source package in Focal: New Status in nvidia-graphics-drivers-440-server source package in Focal: New Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] 440.82: * New upstream release: - Added a workaround for Steam Play title DOOM Eternal, which overrides application requested memory locations, to ensure performance-critical resources be placed in video memory. - Allow presenting from queue families which only expose VK_QUEUE_COMPUTE_BIT when using XCB in addition to Xlib surfaces. - Fixed a bug that caused render-offloaded applications to crash on exit. - Fixed a driver installation failure on Linux kernel 5.6 release candidates, where the NVIDIA kernel module failed to build with error "implicit declaration of function 'timespec_to_ns'". - Fixed a driver installation failure on Linux kernel 5.6 release candidates, where the NVIDIA kernel module failed to build with error "implicit declaration of function 'getrawmonotonic'". - Fixed a driver installation failure on Linux kernel 5.6 release candidates, where the NVIDIA kernel module failed to build with error "implicit declaration of function 'timespec_to_ns'". - Fixed a driver installation failure on Linux kernel 5.6 release candidates, where the NVIDIA kernel module failed to build with error "implicit declaration of function 'getrawmonotonic'". - Fixed a driver installation failure on Linux kernel 5.6 release candidates, where the NVIDIA kernel module failed to build with error "implicit declaration of function 'getnstimeofday'". - Fixed a driver installation failure on Linux kernel 5.6 release candidates, where the NVIDIA kernel module failed to build with error "dereferencing pointer to incomplete type 'struct timeval'". - Fixed a driver installation failure on Linux kernel 5.6 release candidates, where the NVIDIA kernel module failed to build with error "implicit declaration of function 'jiffies_to_timespec'". - Fixed driver installation failure on Linux kernel 5.6 release candidates, where the NVIDIA kernel module failed to build with error "passing argument 4 of 'proc_create_data' from incompatible pointer type". 440.64.00: * Initial release. 418.126.02 * Initial release. nvidia-settings (440.82-0ubuntu0.18.04.1): * [TO BE COMPLETED] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881137/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1881137] Re: Introduce the new NVIDIA 418-server and 440-server series, and update the current NVIDIA drivers
** Description changed: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] 440.82: * New upstream release: - Added a workaround for Steam Play title DOOM Eternal, which overrides application requested memory locations, to ensure performance-critical resources be placed in video memory. - Allow presenting from queue families which only expose VK_QUEUE_COMPUTE_BIT when using XCB in addition to Xlib surfaces. - Fixed a bug that caused render-offloaded applications to crash on exit. - Fixed a driver installation failure on Linux kernel 5.6 release candidates, where the NVIDIA kernel module failed to build with error "implicit declaration of function 'timespec_to_ns'". - Fixed a driver installation failure on Linux kernel 5.6 release candidates, where the NVIDIA kernel module failed to build with error "implicit declaration of function 'getrawmonotonic'". - Fixed a driver installation failure on Linux kernel 5.6 release candidates, where the NVIDIA kernel module failed to build with error "implicit declaration of function 'timespec_to_ns'". - Fixed a driver installation failure on Linux kernel 5.6 release candidates, where the NVIDIA kernel module failed to build with error "implicit declaration of function 'getrawmonotonic'". - Fixed a driver installation failure on Linux kernel 5.6 release candidates, where the NVIDIA kernel module failed to build with error "implicit declaration of function 'getnstimeofday'". - Fixed a driver installation failure on Linux kernel 5.6 release candidates, where the NVIDIA kernel module failed to build with error "dereferencing pointer to incomplete type 'struct timeval'". - Fixed a driver installation failure on Linux kernel 5.6 release candidates, where the NVIDIA kernel module failed to build with error "implicit declaration of function 'jiffies_to_timespec'". - Fixed driver installation failure on Linux kernel 5.6 release candidates, where the NVIDIA kernel module failed to build with error "passing argument 4 of 'proc_create_data' from incompatible pointer type". - 440.64.00: - * Initial release. + * Initial release. 418.126.02 - * Initial release. + * Initial release. - - nvidia-settings (440.82-0ubuntu0.18.04.1): - * [TO BE COMPLETED] + nvidia-settings (440.82): + * New upstream release (LP: #1881137). ** Changed in: nvidia-graphics-drivers-440 (Ubuntu Bionic) Importance: Undecided => High ** Changed in: nvidia-graphics-drivers-440 (Ubuntu Bionic) Status: New => In Progress ** Changed in: nvidia-graphics-drivers-440 (Ubuntu Bionic) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-graphics-drivers-440 (Ubuntu) Status: In Progress => Invalid ** Changed in: nvidia-graphics-drivers-418-server (Ubuntu Bionic) Importance: Undecided => High ** Changed in: nvidia-graphics-drivers-418-server (Ubuntu Bionic) Status: New => In Progress ** Changed in: nvidia-graphics-drivers-418-server (Ubuntu Bionic) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => High ** Changed in: linux (Ubuntu Bionic) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: linux (Ubuntu Focal) Importance: Undecided => High ** Changed in: linux (Ubuntu Focal) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: linux-restricted-modules (Ubuntu Bionic) Importance: Undecided => High ** Changed in: linux-restricted-modules (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux-restricted-modules (Ubuntu Bionic) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: linux-restricted-modules (Ubuntu Focal) Importance:
[Kernel-packages] [Bug 1881549] [NEW] Upgraded to 20.04 and wifi broke
Public bug reported: Upgraded to 20.04 and the wifi broke. It was working fine on 18.04. Tried a variety of things with apw but nada. /var/log attached ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: focal ** Attachment added: "/Var/log" https://bugs.launchpad.net/bugs/1881549/+attachment/5379236/+files/syslog ** Description changed: - Upgraded to 20.04 and the wife broke. It was working fine on 18.04. + Upgraded to 20.04 and the wifi broke. It was working fine on 18.04. Tried a variety of things with apw but nada. /var/log attached -- 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/1881549 Title: Upgraded to 20.04 and wifi broke Status in linux package in Ubuntu: Incomplete Bug description: Upgraded to 20.04 and the wifi broke. It was working fine on 18.04. Tried a variety of things with apw but nada. /var/log attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881549/+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 1867916] Re: Regression in kernel 4.15.0-91 causes kernel panic with Bcache
Hi Mauricio, I can confirm that your patched kernel fixes the problem for me on Bionic (kernel 4.15). Thanks for your help! -Sebastian -- 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/1867916 Title: Regression in kernel 4.15.0-91 causes kernel panic with Bcache Status in Linux: Unknown Status in linux package in Ubuntu: In Progress Bug description: After upgrading from kernel 4.15.0-88 to 4.15.0-91 one of our systems does not boot any longer. It always crashes during boot with a kernel panic. I suspect that this crash might be related to Bcache because this is the only one of our systems where we use Bcache and the kernel panic appears right after Bcache initialization. I already checked that this bug still exists in the 4.15.0-92.93 kernel from proposed. Unfortunately, I cannot do a bisect because this is a critical production system and we do not have any other system with a similar configuration. I attached a screenshot with the trace of the kernel panic. The last message that appears before the kernel panic (or rather the last one that I can see - there is a rather long pause between that message and the panic and I cannot scroll up far enough to ensure that there are no other messages in between) is: bcache: register_bcache() error /dev/dm-0: device already registered When booting with kernel 4.15.0-88 that does not have this problem, the next message is bcache: register_bcache() error /dev/dm-12: device already registered (emitting change event) After that the next message is: Begin: Loading essential drivers ... done This message also appears after the kernel panic, but the boot process stalls and the system can only be recovered by doing a hardware reset. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-88-generic 4.15.0-88.88 ProcVersionSignature: Ubuntu 4.15.0-88.88-generic 4.15.18 Uname: Linux 4.15.0-88-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 17 21:08 seq crw-rw 1 root audio 116, 33 Mar 17 21:08 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.11 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 Mar 18 12:55:18 2020 HibernationDevice: RESUME=UUID=40512ea2-9fce-40f5-8362-5daf955cc26a InstallationDate: Installed on 2013-07-02 (2450 days ago) InstallationMedia: Ubuntu-Server 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130214) MachineType: HP ProLiant DL160 G6 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-88-generic root=/dev/mapper/vg0-root ro nosmt nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-4.15.0-88-generic N/A linux-backports-modules-4.15.0-88-generic N/A linux-firmware 1.173.16 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-09-23 (541 days ago) dmi.bios.date: 11/06/2009 dmi.bios.vendor: HP dmi.bios.version: O33 dmi.chassis.asset.tag: 0191525 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrO33:bd11/06/2009:svnHP:pnProLiantDL160G6:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL160 G6 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1867916/+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 1881549] 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 1881549 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 ** Tags added: focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881549 Title: Upgraded to 20.04 and wifi broke Status in linux package in Ubuntu: Confirmed Bug description: Upgraded to 20.04 and the wifi broke. It was working fine on 18.04. Tried a variety of things with apw but nada. /var/log attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881549/+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 1881676] [NEW] HyperX Cloud Alpha microphone not detected
You have been subscribed to a public bug: When using the HyperX AMP, the microphone is not detected. This is a known issue with the mainline kernel, however was patched in release 5.7.0. This occurs on Ubuntu 20.04 LTS. https://lkml.org/lkml/2020/4/4/197 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Jun 1 18:50:04 2020 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity InstallationDate: Installed on 2020-05-23 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity Symptom: installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug focal ident-mismatch ubiquity-20.04.15 -- HyperX Cloud Alpha microphone not detected https://bugs.launchpad.net/bugs/1881676 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 1881676] Re: HyperX Cloud Alpha microphone not detected
** Package changed: ubiquity (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/1881676 Title: HyperX Cloud Alpha microphone not detected Status in linux package in Ubuntu: Incomplete Bug description: When using the HyperX AMP, the microphone is not detected. This is a known issue with the mainline kernel, however was patched in release 5.7.0. This occurs on Ubuntu 20.04 LTS. https://lkml.org/lkml/2020/4/4/197 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Jun 1 18:50:04 2020 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity InstallationDate: Installed on 2020-05-23 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity Symptom: installer UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881676/+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 1881356] Re: Xenial update: 4.4.224 upstream stable release
** 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: + 4.4.224 upstream stable release + from git://git.kernel.org/ -4.4.224 upstream stable release -from git://git.kernel.org/ + The following patches from the 4.4.224 stable release shall be applied: + * USB: serial: qcserial: Add DW5816e support + * Revert "net: phy: Avoid polling PHY with PHY_IGNORE_INTERRUPTS" + * dp83640: reverse arguments to list_add_tail + * net/mlx4_core: Fix use of ENOSPC around mlx4_counter_alloc() + * sch_sfq: validate silly quantum values + * sch_choke: avoid potential panic in choke_reset() + * Revert "ACPI / video: Add force_native quirk for HP Pavilion dv6" + * enic: do not overwrite error code + * ipv6: fix cleanup ordering for ip6_mr failure + * binfmt_elf: move brk out of mmap when doing direct loader exec + * x86/apm: Don't access __preempt_count with zeroed fs + * Revert "IB/ipoib: Update broadcast object if PKey value was changed in index 0" + * USB: uas: add quirk for LaCie 2Big Quadra + * USB: serial: garmin_gps: add sanity checking for data length + * batman-adv: fix batadv_nc_random_weight_tq + * scripts/decodecode: fix trapping instruction formatting + * phy: micrel: Ensure interrupts are reenabled on resume + * binfmt_elf: Do not move brk for INTERP-less ET_EXEC + * ext4: add cond_resched() to ext4_protect_reserved_inode + * net: ipv6: add net argument to ip6_dst_lookup_flow + * net: ipv6_stub: use ip6_dst_lookup_flow instead of ip6_dst_lookup + * blktrace: Fix potential deadlock between delete & sysfs ops + * blktrace: fix unlocked access to init/start-stop/teardown + * blktrace: fix trace mutex deadlock + * blktrace: Protect q->blk_trace with RCU + * blktrace: fix dereference after null check + * ptp: do not explicitly set drvdata in ptp_clock_register() + * ptp: use is_visible method to hide unused attributes + * ptp: create "pins" together with the rest of attributes + * chardev: add helper function to register char devs with a struct device + * ptp: Fix pass zero to ERR_PTR() in ptp_clock_register + * ptp: fix the race between the release of ptp_clock and cdev + * ptp: free ptp device pin descriptors properly + * net: handle no dst on skb in icmp6_send + * net/sonic: Fix a resource leak in an error handling path in 'jazz_sonic_probe()' + * net: moxa: Fix a potential double 'free_irq()' + * drop_monitor: work around gcc-10 stringop-overflow warning + * scsi: sg: add sg_remove_request in sg_write + * spi: spi-dw: Add lock protect dw_spi rx/tx to prevent concurrent calls + * cifs: Check for timeout on Negotiate stage + * cifs: Fix a race condition with cifs_echo_request + * dmaengine: pch_dma.c: Avoid data race between probe and irq handler + * dmaengine: mmp_tdma: Reset channel error on release + * drm/qxl: lost qxl_bo_kunmap_atomic_page in qxl_image_init_helper() + * ipc/util.c: sysvipc_find_ipc() incorrectly updates position index + * net: openvswitch: fix csum updates for MPLS actions + * gre: do not keep the GRE header around in collect medata mode + * mm/memory_hotplug.c: fix overflow in test_pages_in_a_zone() + * scsi: qla2xxx: Avoid double completion of abort command + * i40e: avoid NVM acquire deadlock during NVM update + * net/mlx5: Fix driver load error flow when firmware is stuck + * netfilter: conntrack: avoid gcc-10 zero-length-bounds warning + * IB/mlx4: Test return value of calls to ib_get_cached_pkey + * pnp: Use list_for_each_entry() instead of open coding + * gcc-10 warnings: fix low-hanging fruit + * kbuild: compute false-positive -Wmaybe-uninitialized cases in Kconfig + * Stop the ad-hoc games with -Wno-maybe-initialized + * gcc-10: disable 'zero-length-bounds' warning for now + * gcc-10: disable 'array-bounds' warning for now + * gcc-10: disable 'stringop-overflow' warning for now + * gcc-10: disable 'restrict' warning for now + * block: defer timeouts to a workqueue + * blk-mq: Allow timeouts to run while queue is freezing + * blk-mq: sync the update nr_hw_queues with blk_mq_queue_tag_busy_iter + * blk-mq: Allow blocking queue tag iter callbacks + * x86/paravirt:
[Kernel-packages] [Bug 1880032] Re: [linux-azure] Enable Hibernation on The 18.04 and 20.04 5.4 Kernels
** Also affects: linux-azure (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-azure (Ubuntu Focal) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1880032 Title: [linux-azure] Enable Hibernation on The 18.04 and 20.04 5.4 Kernels Status in linux-azure package in Ubuntu: Confirmed Status in linux-azure source package in Focal: In Progress Bug description: Microsoft would like to request commits to enable VM hibernation in the Azure 5.4 kernels for 18.04 and 20.04. Some of the commits needed to enable VM hibernation were included in mainline 5.4 and older. However, 24 commits were added in 5.5 and later, which are required in the 5.4 kernel. The list of commits requested are: 38dce4195f0d x86/hyperv: Properly suspend/resume reenlightenment notifications 2351f8d295ed PM: hibernate: Freeze kernel threads in software_resume() 421f090c819d x86/hyperv: Suspend/resume the VP assist page for hibernation 1a06d017fb3f Drivers: hv: vmbus: Fix Suspend-to-Idle for Generation-2 VM 3704a6a44579 PM: hibernate: Propagate the return value of hibernation_restore() 54e19d34011f hv_utils: Add the support of hibernation ffd1d4a49336 hv_utils: Support host-initiated hibernation request 3e9c72056ed5 hv_utils: Support host-initiated restart request 9fc3c01a1fae6 Tools: hv: Reopen the devices if read() or write() returns 05bd330a7fd8 x86/hyperv: Suspend/resume the hypercall page for hibernation 382a46221757 video: hyperv_fb: Fix hibernation for the deferred IO feature e2379b30324c Input: hyperv-keyboard: Add the support of hibernation ac82fc8327088 PCI: hv: Add hibernation support a8e37506e79a PCI: hv: Reorganize the code in preparation of hibernation 1349401ff1aa4 clocksource/drivers/hyper-v: Suspend/resume Hyper-V clocksource for hibernation af13f9ed6f9a HID: hyperv: Add the support of hibernation 25bd2b2f1f053 hv_balloon: Add the support of hibernation b96f86534fa31 x86/hyperv: Implement hv_is_hibernation_supported() 4df4cb9e99f83 x86/hyperv: Initialize clockevents earlier in CPU onlining 0efeea5fb1535 hv_netvsc: Add the support of hibernation 2194c2eb6717f hv_sock: Add the support of hibernation 1ecf302021040 video: hyperv_fb: Add the support of hibernation 56fb105859345 scsi: storvsc: Add the support of hibernation f2c33ccacb2d4 PCI/PM: Always return devices to D0 when thawing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1880032/+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 1881213] Re: System hangs at reboot or poweroff. kworker blocked at dp_altmode_work
@kaifengheng -- 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/1881213 Title: System hangs at reboot or poweroff. kworker blocked at dp_altmode_work Status in linux package in Ubuntu: Incomplete Bug description: Expected: System reboots/powers off. Actual: System hangs with the plymouth bootsplash with the Kubuntu logo. Pressing escape shows `[OK] Reached target Reboot`. `journalctl -b -1` shows at the end. ``` May 28 16:33:21 jordan-ThinkPad systemd[1]: Shutting down. May 28 16:33:21 jordan-ThinkPad systemd-shutdown[1]: Syncing filesystems and block devices. May 28 16:33:21 jordan-ThinkPad systemd-shutdown[1]: Sending SIGTERM to remaining processes... May 28 16:33:21 jordan-ThinkPad systemd-journald[454]: Journal stopped ``` Letting the computer continue to idle, an error message shows up. I've attached a picture because the error message does not show up in any logs. Possibly a duplicate of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872817, though the other user did not mention the same symptoms. Description:Ubuntu 20.04 LTS Release:20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-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: ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Thu May 28 16:53:34 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-31-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-33-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f91] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU117M [GeForce GTX 1650 Mobile / Max-Q] [17aa:229f] InstallationDate: Installed on 2020-05-22 (6 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20QVCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=0a60aa5c-2eea-49a2-9e8e-966068e76491 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/07/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET44W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QVCTO1WW dmi.board.vendor: LENOVO dmi.board.version: 0B98417 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2OET44W(1.31):bd05/07/2020:svnLENOVO:pn20QVCTO1WW:pvrThinkPadX1ExtremeGen2:rvnLENOVO:rn20QVCTO1WW:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Extreme Gen2 dmi.product.name: 20QVCTO1WW dmi.product.sku: LENOVO_MT_20QV_BU_Think_FM_ThinkPad X1 Extreme Gen2 dmi.product.version: ThinkPad X1 Extreme Gen2 dmi.sys.vendor: LENOVO 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 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 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/1881213/+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 1670041] Re: Poor performance of Atheros QCA6174 802.11ac (rev 32) (Killer Wireless 1535)
this bug is still not solved in 20.04 -- 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/1670041 Title: Poor performance of Atheros QCA6174 802.11ac (rev 32) (Killer Wireless 1535) Status in linux package in Ubuntu: Confirmed Status in linux source package in Artful: Won't Fix Status in linux source package in Bionic: Confirmed Bug description: Update (2017-05-20): Kalle Valo suggested a hack which increased client -> AP TCP performance - so it does not look like a firmware issue as I thought originally, rather an ath10k driver issue: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1670041/comments/11 https://patchwork.kernel.org/patch/5784701/ (the hack is at the bottom) Tested here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1670041/comments/17 Update: added some forensics in the paste (a long read): http://paste.ubuntu.com/24118478/ - 3b:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32) qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:1535 Original message: -- I experience a very poor 802.11ac performance of a QCA6174 Wireless card (Killer Wireless 1535). This is a dev version of Zesty with a recently released 4.10 kernel: uname -r 4.10.0-9-generic dpkg -l linux-firmware | grep ii ii linux-firmware 1.163all Firmware for Linux kernel drivers lspci -vvv: ... 3b:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32) Subsystem: Bigfoot Networks, Inc. QCA6174 802.11ac Wireless Network Adapter Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: ath10k_pci Kernel modules: ath10k_pci - Testing wireless speed with RT-87U 802.11ac router shows that the speed is only 27.3 megabits per second which is very low for an 802.11ac card: iperf -c rtr Client connecting to rtr, TCP port 5001 TCP window size: 85.0 KByte (default) [ 3] local 10.10.10.78 port 48930 connected with 10.10.10.1 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.0 sec 32.6 MBytes 27.3 Mbits/sec For comparison, on the same network (from the same distance to the router) I have the following result with an Intel's card (on a 4.8 kernel, different laptop): UX32LN:~$ lspci | grep 7260 02:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb) UX32LN:~$ iperf -c rtr Client connecting to rtr, TCP port 5001 TCP window size: 85.0 KByte (default) [ 3] local 10.10.10.208 port 37196 connected with 10.10.10.1 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.1 sec 237 MBytes 198 Mbits/sec administrator@UX32LN:~$ lsp lspci lspcmcia lspgpot 200 Mbps is much better. --- Back to the problematic card: Booted 16.04.2 with the rolling HWE kernel 4.8: journalctl -k | grep -i ath Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: enabling device ( -> 0002) Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0 Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: Direct firmware load for ath10k/pre-cal-pci-:3b:00.0.bin failed with error -2 Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: Direct firmware load for ath10k/cal-pci-:3b:00.0.bin failed with error -2 Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: Direct firmware load for ath10k/QCA6174/hw3.0/firmware-5.bin failed with error -2 Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: could not fetch firmware file 'ath10k/QCA6174/hw3.0/firmware-5.bin': -2 Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:1535 Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: firmware ver WLAN.RM.2.0-00180-QCARMSWPZ-1 api 4 features wowlan,ignore-otp,no-4addr-pad crc32 75dee6c5 Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: board_file api 2 bmi_id N/A crc32 6fc88fe7 Mar 04 18:28:34 ubuntu kernel: ath10k_pci :3b:00.0: htt-ver 3.26 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 Mar 04 18:28:34 ubuntu kernel: ath: EEPROM regdomain: 0x6c Mar 04 18:28:34
[Kernel-packages] [Bug 1881534] [NEW] Touchpad not working on Lenovo Thinkbook
You have been subscribed to a public bug: The touchpad on my Lenovo Thinkbook is not being detected at all. I have attached the devices list. I also tried installing ubuntu 20.04 and even in the latest version touchpad is not detected. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: tocuhpad -- Touchpad not working on Lenovo Thinkbook https://bugs.launchpad.net/bugs/1881534 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 1880032] Re: [linux-azure] Enable Hibernation on The 18.04 and 20.04 5.4 Kernels
The following patches weren't necessary because they were already applied via upstream stable updates: f2c33ccacb2d PCI/PM: Always return devices to D0 when thawing Via https://bugs.launchpad.net/bugs/1858427 2351f8d295ed PM: hibernate: Freeze kernel threads in software_resume() Via https://bugs.launchpad.net/bugs/1877592 1a06d017fb3f Drivers: hv: vmbus: Fix Suspend-to-Idle for Generation-2 VM Via https://bugs.launchpad.net/bugs/1877592 -- 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/1880032 Title: [linux-azure] Enable Hibernation on The 18.04 and 20.04 5.4 Kernels Status in linux-azure package in Ubuntu: Confirmed Status in linux-azure source package in Focal: In Progress Bug description: Microsoft would like to request commits to enable VM hibernation in the Azure 5.4 kernels for 18.04 and 20.04. Some of the commits needed to enable VM hibernation were included in mainline 5.4 and older. However, 24 commits were added in 5.5 and later, which are required in the 5.4 kernel. The list of commits requested are: 38dce4195f0d x86/hyperv: Properly suspend/resume reenlightenment notifications 2351f8d295ed PM: hibernate: Freeze kernel threads in software_resume() 421f090c819d x86/hyperv: Suspend/resume the VP assist page for hibernation 1a06d017fb3f Drivers: hv: vmbus: Fix Suspend-to-Idle for Generation-2 VM 3704a6a44579 PM: hibernate: Propagate the return value of hibernation_restore() 54e19d34011f hv_utils: Add the support of hibernation ffd1d4a49336 hv_utils: Support host-initiated hibernation request 3e9c72056ed5 hv_utils: Support host-initiated restart request 9fc3c01a1fae6 Tools: hv: Reopen the devices if read() or write() returns 05bd330a7fd8 x86/hyperv: Suspend/resume the hypercall page for hibernation 382a46221757 video: hyperv_fb: Fix hibernation for the deferred IO feature e2379b30324c Input: hyperv-keyboard: Add the support of hibernation ac82fc8327088 PCI: hv: Add hibernation support a8e37506e79a PCI: hv: Reorganize the code in preparation of hibernation 1349401ff1aa4 clocksource/drivers/hyper-v: Suspend/resume Hyper-V clocksource for hibernation af13f9ed6f9a HID: hyperv: Add the support of hibernation 25bd2b2f1f053 hv_balloon: Add the support of hibernation b96f86534fa31 x86/hyperv: Implement hv_is_hibernation_supported() 4df4cb9e99f83 x86/hyperv: Initialize clockevents earlier in CPU onlining 0efeea5fb1535 hv_netvsc: Add the support of hibernation 2194c2eb6717f hv_sock: Add the support of hibernation 1ecf302021040 video: hyperv_fb: Add the support of hibernation 56fb105859345 scsi: storvsc: Add the support of hibernation f2c33ccacb2d4 PCI/PM: Always return devices to D0 when thawing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1880032/+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 1880032] Re: [linux-azure] Enable Hibernation on The 18.04 and 20.04 5.4 Kernels
Cover letter for the patchset: https://lists.ubuntu.com/archives/kernel- team/2020-June/110613.html -- 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/1880032 Title: [linux-azure] Enable Hibernation on The 18.04 and 20.04 5.4 Kernels Status in linux-azure package in Ubuntu: Confirmed Status in linux-azure source package in Focal: In Progress Bug description: Microsoft would like to request commits to enable VM hibernation in the Azure 5.4 kernels for 18.04 and 20.04. Some of the commits needed to enable VM hibernation were included in mainline 5.4 and older. However, 24 commits were added in 5.5 and later, which are required in the 5.4 kernel. The list of commits requested are: 38dce4195f0d x86/hyperv: Properly suspend/resume reenlightenment notifications 2351f8d295ed PM: hibernate: Freeze kernel threads in software_resume() 421f090c819d x86/hyperv: Suspend/resume the VP assist page for hibernation 1a06d017fb3f Drivers: hv: vmbus: Fix Suspend-to-Idle for Generation-2 VM 3704a6a44579 PM: hibernate: Propagate the return value of hibernation_restore() 54e19d34011f hv_utils: Add the support of hibernation ffd1d4a49336 hv_utils: Support host-initiated hibernation request 3e9c72056ed5 hv_utils: Support host-initiated restart request 9fc3c01a1fae6 Tools: hv: Reopen the devices if read() or write() returns 05bd330a7fd8 x86/hyperv: Suspend/resume the hypercall page for hibernation 382a46221757 video: hyperv_fb: Fix hibernation for the deferred IO feature e2379b30324c Input: hyperv-keyboard: Add the support of hibernation ac82fc8327088 PCI: hv: Add hibernation support a8e37506e79a PCI: hv: Reorganize the code in preparation of hibernation 1349401ff1aa4 clocksource/drivers/hyper-v: Suspend/resume Hyper-V clocksource for hibernation af13f9ed6f9a HID: hyperv: Add the support of hibernation 25bd2b2f1f053 hv_balloon: Add the support of hibernation b96f86534fa31 x86/hyperv: Implement hv_is_hibernation_supported() 4df4cb9e99f83 x86/hyperv: Initialize clockevents earlier in CPU onlining 0efeea5fb1535 hv_netvsc: Add the support of hibernation 2194c2eb6717f hv_sock: Add the support of hibernation 1ecf302021040 video: hyperv_fb: Add the support of hibernation 56fb105859345 scsi: storvsc: Add the support of hibernation f2c33ccacb2d4 PCI/PM: Always return devices to D0 when thawing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1880032/+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 1881534] Re: Touchpad not working on Lenovo Thinkbook
** Package changed: ubuntu => linux (Ubuntu) ** Tags removed: tocuhpad ** Tags added: focal touchpad -- 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/1881534 Title: Touchpad not working on Lenovo Thinkbook Status in linux package in Ubuntu: Incomplete Bug description: The touchpad on my Lenovo Thinkbook is not being detected at all. I have attached the devices list. I also tried installing ubuntu 20.04 and even in the latest version touchpad is not detected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881534/+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 1881534] 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 1881534 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/1881534 Title: Touchpad not working on Lenovo Thinkbook Status in linux package in Ubuntu: Incomplete Bug description: The touchpad on my Lenovo Thinkbook is not being detected at all. I have attached the devices list. I also tried installing ubuntu 20.04 and even in the latest version touchpad is not detected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881534/+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 1879807] Re: 5.3.0-53 Kernel system falis to reboot after install
I can confirm it, Im using Linux Mint 19.3 cinnamon with an AMD/GPU radeon vega mobile gtx8, and everytime I install the kernel, the laptop can't seem to shutdown or reboot. -- 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/1879807 Title: 5.3.0-53 Kernel system falis to reboot after install Status in linux package in Ubuntu: Confirmed Bug description: I cant post the requested terminal outputs because I can't install the kernel, but here is the system information: System:Host: LM Kernel: 5.3.0-51-generic x86_64 bits: 64 compiler: gcc v: 7.5.0 Desktop: Cinnamon 4.4.8 wm: muffin dm: LightDM Distro: Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic Machine: Type: Desktop Mobo: ASRock model: A300M-STX serial: UEFI: American Megatrends v: P3.60 date: 10/28/2019 Battery: Device-1: hidpp_battery_0 model: Logitech Wireless Mouse serial: charge: 55% status: Discharging CPU: Topology: Quad Core model: AMD Ryzen 3 3200G with Radeon Vega Graphics bits: 64 type: MCP arch: Zen rev: 1 L2 cache: 2048 KiB flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 28803 Speed: 1600 MHz min/max: 1400/3600 MHz Core speeds (MHz): 1: 1600 2: 1600 3: 4000 4: 1600 Graphics: Device-1: AMD Picasso driver: amdgpu v: kernel bus ID: 04:00.0 chip ID: 1002:15d8 Display: x11 server: X.Org 1.20.5 driver: amdgpu,ati unloaded: fbdev,modesetting,vesa resolution: 1920x1080~60Hz OpenGL: renderer: AMD RAVEN (DRM 3.33.0 5.3.0-51-generic LLVM 9.0.0) v: 4.5 Mesa 19.2.8 direct render: Yes Audio: Device-1: AMD driver: snd_hda_intel v: kernel bus ID: 04:00.1 chip ID: 1002:15de Device-2: AMD vendor: ASRock driver: snd_hda_intel v: kernel bus ID: 04:00.6 chip ID: 1022:15e3 Sound Server: ALSA v: k5.3.0-51-generic Network: Device-1: Intel Dual Band Wireless-AC 3168NGW [Stone Peak] driver: iwlwifi v: kernel bus ID: 02:00.0 chip ID: 8086:24fb IF: wlp2s0 state: down mac: Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASRock driver: r8169 v: kernel port: f000 bus ID: 03:00.0 chip ID: 10ec:8168 IF: enp3s0 state: up speed: 1000 Mbps duplex: full mac: Drives:Local Storage: total: 350.27 GiB used: 18.08 GiB (5.2%) ID-1: /dev/nvme0n1 vendor: Toshiba model: RD400 size: 238.47 GiB speed: 31.6 Gb/s lanes: 4 serial: ID-2: /dev/sda vendor: Crucial model: CT120BX500SSD1 size: 111.79 GiB speed: 6.0 Gb/s serial: temp: 39 C Partition: ID-1: / size: 233.26 GiB used: 10.51 GiB (4.5%) fs: ext4 dev: /dev/nvme0n1p2 USB: Hub: 1-0:1 info: Full speed (or root) Hub ports: 4 rev: 2.0 chip ID: 1d6b:0002 Hub: 1-3:2 info: Genesys Logic Hub ports: 4 rev: 2.0 chip ID: 05e3:0608 Device-1: 1-3.1:3 info: Intel type: Bluetooth driver: btusb rev: 2.0 chip ID: 8087:0aa7 Hub: 1-3.2:4 info: Genesys Logic Hub ports: 4 rev: 2.0 chip ID: 05e3:0608 Device-2: 1-3.2.2:5 info: Logitech Illuminated Keyboard type: Keyboard,Mouse driver: hid-generic,usbhid rev: 2.0 chip ID: 046d:c318 Device-3: 1-3.2.3:6 info: Logitech Unifying Receiver type: Mouse,HID driver: logitech-djreceiver,usbhid rev: 2.0 chip ID: 046d:c52f Hub: 2-0:1 info: Full speed (or root) Hub ports: 4 rev: 3.1 chip ID: 1d6b:0003 Hub: 3-0:1 info: Full speed (or root) Hub ports: 1 rev: 2.0 chip ID: 1d6b:0002 Hub: 4-0:1 info: Full speed (or root) Hub ports: 1 rev: 3.1 chip ID: 1d6b:0003 Sensors: System Temperatures: cpu: 38.5 C mobo: N/A Fan Speeds (RPM): N/A Repos: No active apt repos in: /etc/apt/sources.list Active apt repos in: /etc/apt/sources.list.d/google-chrome.list 1: deb [arch=amd64] http: //dl.google.com/linux/chrome/deb/ stable main Active apt repos in: /etc/apt/sources.list.d/google-earth-pro.list 1: deb [arch=amd64] http: //dl.google.com/linux/earth/deb/ stable main Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list 1: deb http: //mirror.clarkson.edu/linuxmint/packages tricia main upstream import backport 2: deb http: //archive.linux.duke.edu/ubuntu bionic main restricted universe multiverse 3: deb http: //archive.linux.duke.edu/ubuntu bionic-updates main restricted universe multiverse 4: deb http: //archive.linux.duke.edu/ubuntu bionic-backports main restricted universe multiverse 5: deb http: //security.ubuntu.com/ubuntu/
[Kernel-packages] [Bug 1685442] Re: Errors: flip_done timed out during boot-up; slow boot
Thanks for the update Zakhar, but do we still have other sources that can help us to fix this one? I wonder. Thank you again. Marco Blakey https://andwebtraffic.com -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1685442 Title: Errors: flip_done timed out during boot-up; slow boot Status in Linux: Fix Released Status in linux package in Ubuntu: Confirmed Status in linux package in Baltix: In Progress Bug description: I had been running Ubuntu 16.04 LTS on many laptop computers (especially Dell D620, D630, E6400) with no problem. I created a Live USB with Ubuntu 16.04.2 LTS and tried it on a Dell D630. It was very slow to boot up (about 90 seconds) as opposed to the 30-45 seconds it usually takes. For a few seconds there were error messages that included the phrase "flip_done timed out". When the Ubuntu desktop appeared, the mouse cursor hung for a while, but then came back to life. I didn't do much testing from there. I did a Live session with the 16.04.2 LTS on a different D630 laptop, and the same problem occureed. I Googled the problem, and found several hits. - On an Arch forum, someone reported the problem on a Dell D630, like mine. It also occured on other laptops: https://bbs.archlinux.org/viewtopic.php?id=218581 The suggestion was that the bug was related to kernel version 4.8.x and the 965GM chipset, which is what the D630 has. So I tried Ubuntu Mate 16.04.2 on a Dell D620 (with a 945GM chipset) and the problem DID NOT occur. --- For a similar boot-up problem, Ubuntu Forum suggested going back to an earlier version of Ubuntu. https://ubuntuforums.org/showthread.php?t=2348892 I tried Ubuntu Mate 16.04.1 (with the 4.4.0-31-generic kernel), and the problem did NOT occur. So I'm solving the problem for myself by using Ubuntu Mate 16.04.1 LTS rather than 16.04.2. --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: test 2194 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=a754e82c-72cb-44d1-9fa4-58777803b24d InstallationDate: Installed on 2017-07-19 (0 days ago) InstallationMedia: Ubuntu-MATE 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) MachineType: Dell Inc. Latitude D630 Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-36-generic root=UUID=2a3b3861-8ac7-41e0-86cf-999434bd112e ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.8.0-36-generic N/A linux-backports-modules-4.8.0-36-generic N/A linux-firmware1.157.8 Tags: xenial Uname: Linux 4.8.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 06/04/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 0KU184 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd06/04/2013:svnDellInc.:pnLatitudeD630:pvr:rvnDellInc.:rn0KU184:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude D630 dmi.sys.vendor: Dell Inc. --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: test 2194 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=a754e82c-72cb-44d1-9fa4-58777803b24d InstallationDate: Installed on 2017-07-19 (0 days ago) InstallationMedia: Ubuntu-MATE 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) MachineType: Dell Inc. Latitude D630 Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-36-generic root=UUID=2a3b3861-8ac7-41e0-86cf-999434bd112e ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon.
[Kernel-packages] [Bug 1881525] Re: in kernel amdgpu failed with W5500 [1002:7341]
Patches: https://lists.ubuntu.com/archives/kernel-team/2020-June/110635.html -- 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/1881525 Title: in kernel amdgpu failed with W5500 [1002:7341] Status in HWE Next: New Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Bionic: In Progress Bug description: [SRU Justfication] [Impact] amdgpu is always failed on bionic 5.4 kernel. Since bionic's kernel will upgrade to 5.4 in the future, but bionic's linux-firmware didn't support navi14. So if a user update kernel to 5.4, he/she still can't use the related navi14 devices. # dmesg | grep amdgpu [drm] amdgpu kernel modesetting enabled. amdgpu remove_conflicting_pci_framebuffers: bar 0: 0x60 -> 0x600fff amdgpu remove_conflicting_pci_framebuffers: bar 2: 0x601000 -> 0x60101f amdgpu remove_conflicting_pci_framebuffers: bar 5: 0x7e80 -> 0x7e87 fb0: switching to amdgpudrmfb from EFI VGA amdgpu vgaarb: deactivate vga console amdgpu enabling device (0106 -> 0107) amdgpu Direct firmware load for amdgpu/navi14_gpu_info.bin failed with error -2 amdgpu Failed to load gpu_info firmware "amdgpu/navi14_gpu_info.bin" amdgpu Fatal error during GPU init [Fix] Patchset[1] for navi14's support currently landed in focal's linux-firmware, so we backported them to bionic's linux-firmware. [1]: aa95e90b2c638f1ca6647d12b2d1b18284428f9c d4f88ea76e442e6652de1367050e33314594d533 40656437f476ef7c47972731671ddcc9e4c4225b 7319341e6e40f8bae1f2623eb5e4ddc0e2b50076 b5b176ac09b6d1211da1e5db8e0c31ac830e4b8c [Test] The amdgpu can be recognized and initialized when booting. # dmesg | grep amdgpu [drm] amdgpu kernel modesetting enabled. amdgpu remove_conflicting_pci_framebuffers: bar 0: 0x60 -> 0x600fff amdgpu remove_conflicting_pci_framebuffers: bar 2: 0x601000 -> 0x60101f amdgpu remove_conflicting_pci_framebuffers: bar 5: 0x7e80 -> 0x7e87 amdgpu enabling device (0106 -> 0107) amdgpu VRAM: 8176M 0x0080 - 0x0081FEFF (8176M used) amdgpu GART: 512M 0x - 0x1FFF [drm] amdgpu: 8176M of VRAM memory ready [drm] amdgpu: 8176M of GTT memory ready. ... [drm] Initialized amdgpu 3.35.0 20150101 for :03:00.0 on minor 1 [Regression Potential] Low, just adding new navi14 firmware, no change to existing firmware. X-HWE-Bug: Bug #1880678 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-hotpie+X34 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-05-25 (6 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Package: linux-firmware 1.173.18+navi14 [origin: LP-PPA-shanelin-linux-firmware] PackageArchitecture: all ProcVersionSignature: Ubuntu 5.4.0-31.35~18.04.2-generic 5.4.34 Tags: bionic uec-images third-party-packages Uname: Linux 5.4.0-31-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1881525/+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 1855628] Re: Ubuntu keeps having resolution issues and disconnects from the network after I wake it up from sleep
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager (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/1855628 Title: Ubuntu keeps having resolution issues and disconnects from the network after I wake it up from sleep Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Confirmed Bug description: Whenever I wake the computer up from sleep, the computer no longer connects to the Internet without my having to go into Settings and turn Wi-Fi off and then back on again. Please address this issue. Thank you! network-manager: Installed: 1.10.6-2ubuntu1.2 Candidate: 1.10.6-2ubuntu1.2 Version table: *** 1.10.6-2ubuntu1.2 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.10.6-2ubuntu1.1 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 1.10.6-2ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Description: Ubuntu 18.04.3 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1.2 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-37-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Dec 8 19:51:31 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.1.1 dev wlp3s0 proto dhcp metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.33 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE NETGEAR18 64704ba2-aba5-44de-ad4a-7d0de569815b wifi 1575852612 Sun 08 Dec 2019 07:50:12 PM EST yes 0 no/org/freedesktop/NetworkManager/Settings/1 yes wlp3s0 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- Wired connection 1 28634e82-4c1c-3a61-b152-3bd92aaa6992 ethernet 1575852610 Sun 08 Dec 2019 07:50:10 PM EST yes 4294966297 no/org/freedesktop/NetworkManager/Settings/2 no -- -- -- -- nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp3s0 wifi connected/org/freedesktop/NetworkManager/Devices/3 NETGEAR18 64704ba2-aba5-44de-ad4a-7d0de569815b /org/freedesktop/NetworkManager/ActiveConnection/1 enp4s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: seija 1560 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2020-04-04 (5 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e009 Atheros Communications, Inc.
[Kernel-packages] [Bug 1881638] Status changed to Confirmed
This change was made by a bot. ** Changed in: 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/1881638 Title: touchpad not appearing in list of hardware devices Status in linux package in Ubuntu: Confirmed Bug description: touchpad has been frozen for ~1 hour. Doesn't appear when checking xinput --list or other lists of hardware connected to the computer. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: prachi 1669 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 1 11:06:06 2020 InstallationDate: Installed on 2020-05-18 (13 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. XPS 15 7590 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=3a384bca-9677-48c8-bd86-3395fc0e3565 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/06/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.name: 0VYV0G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd02/06/2020:svnDellInc.:pnXPS157590:pvr:rvnDellInc.:rn0VYV0G:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 7590 dmi.product.sku: 0905 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881638/+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 1826848] Re: ip_defrag.sh in net from ubuntu_kernel_selftests failed with 5.0 / 5.3 kernel
** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) 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/1826848 Title: ip_defrag.sh in net from ubuntu_kernel_selftests failed with 5.0 / 5.3 kernel Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Disco: Confirmed Status in linux source package in Eoan: Confirmed Status in linux source package in Focal: Confirmed Bug description: Test failed becuase: ./ip_defrag: sendto overlap: 1400: Operation not permitted selftests: net: ip_defrag.sh ipv6 tx:17 gso:1 (fail) OK ipv4 defrag PASS seed = 1556203721 ipv4 defrag with overlaps PASS seed = 1556203722 ipv6 defrag seed = 1556203756 PASS ipv6 defrag with overlaps seed = 1556203756 ./ip_defrag: sendto overlap: 1400: Operation not permitted not ok 1..17 selftests: net: ip_defrag.sh [FAIL] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1826848/+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 1850439] Re: No sound on ASUS UX534FT
BTW I'm glad that those commands helped you. And good job in command dissection here! -- 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/1850439 Title: No sound on ASUS UX534FT Status in linux package in Ubuntu: Confirmed Bug description: Hi, after instal Ubuntu in dual boot alongside Windows 10, I've realised there is no sound coming out of mine new ASUS Zenbook 15 UX534FT- AA024R in Ubuntu. In Windows there is no problem. Found this topic https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810214 which had the same problem with driver for Realtek ALC294 which is also mine sound card. But even with this fix it is not working on UX534FT. Can you please add fix also for this newer model? Description: Ubuntu 18.04.3 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.0.0-32-generic 5.0.0-32.34~18.04.2 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 29 15:11:25 2019 InstallationDate: Installed on 2019-10-29 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439/+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 1850439] Re: No sound on ASUS UX534FT
I found it! I found the magic sequence!!! srgk@zen~$ sudo hda-verb /dev/snd/hwC0D0 0x20 0x500 0x1b [sudo] password for srgk: nid = 0x20, verb = 0x500, param = 0x1b value = 0x0 srgk@zen:~$ sudo hda-verb /dev/snd/hwC0D0 0x20 0x477 0x4a4b nid = 0x20, verb = 0x477, param = 0x4a4b value = 0x0 srgk@zen:~$ sudo hda-verb /dev/snd/hwC0D0 0x20 0x500 0xf nid = 0x20, verb = 0x500, param = 0xf value = 0x0 srgk@zen:~$ sudo hda-verb /dev/snd/hwC0D0 0x20 0x477 0x74 nid = 0x20, verb = 0x477, param = 0x74 value = 0x0 The result of alsa-info after those commands is still different from the reference above for some reason. But it works perfectly without artifacts! -- 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/1850439 Title: No sound on ASUS UX534FT Status in linux package in Ubuntu: Confirmed Bug description: Hi, after instal Ubuntu in dual boot alongside Windows 10, I've realised there is no sound coming out of mine new ASUS Zenbook 15 UX534FT- AA024R in Ubuntu. In Windows there is no problem. Found this topic https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810214 which had the same problem with driver for Realtek ALC294 which is also mine sound card. But even with this fix it is not working on UX534FT. Can you please add fix also for this newer model? Description: Ubuntu 18.04.3 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.0.0-32-generic 5.0.0-32.34~18.04.2 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 29 15:11:25 2019 InstallationDate: Installed on 2019-10-29 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439/+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 1850439] Re: No sound on ASUS UX534FT
For me just usual reboot is enough. I reboot the notebook, start some application that plays sound and then execute the commands below. And everything works as a charm on my UX534FTC. About reset - try also "alsa force-reload" and maybe the following command: hda-verb /dev/snd/hwC0D0 0x51 0x7ff 0x0 # AC_VERB_SET_CODEC_RESET -- 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/1850439 Title: No sound on ASUS UX534FT Status in linux package in Ubuntu: Confirmed Bug description: Hi, after instal Ubuntu in dual boot alongside Windows 10, I've realised there is no sound coming out of mine new ASUS Zenbook 15 UX534FT- AA024R in Ubuntu. In Windows there is no problem. Found this topic https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810214 which had the same problem with driver for Realtek ALC294 which is also mine sound card. But even with this fix it is not working on UX534FT. Can you please add fix also for this newer model? Description: Ubuntu 18.04.3 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.0.0-32-generic 5.0.0-32.34~18.04.2 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 29 15:11:25 2019 InstallationDate: Installed on 2019-10-29 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439/+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 1881638] [NEW] touchpad not appearing in list of hardware devices
Public bug reported: touchpad has been frozen for ~1 hour. Doesn't appear when checking xinput --list or other lists of hardware connected to the computer. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: prachi 1669 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 1 11:06:06 2020 InstallationDate: Installed on 2020-05-18 (13 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. XPS 15 7590 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=3a384bca-9677-48c8-bd86-3395fc0e3565 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/06/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.name: 0VYV0G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd02/06/2020:svnDellInc.:pnXPS157590:pvr:rvnDellInc.:rn0VYV0G:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 7590 dmi.product.sku: 0905 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "devices" https://bugs.launchpad.net/bugs/1881638/+attachment/5379438/+files/devices -- 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/1881638 Title: touchpad not appearing in list of hardware devices Status in linux package in Ubuntu: New Bug description: touchpad has been frozen for ~1 hour. Doesn't appear when checking xinput --list or other lists of hardware connected to the computer. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: prachi 1669 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 1 11:06:06 2020 InstallationDate: Installed on 2020-05-18 (13 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. XPS 15 7590 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=3a384bca-9677-48c8-bd86-3395fc0e3565 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/06/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.name: 0VYV0G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd02/06/2020:svnDellInc.:pnXPS157590:pvr:rvnDellInc.:rn0VYV0G:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 7590 dmi.product.sku: 0905 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881638/+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 1881657] [NEW] Eoan update: upstream stable patchset 2020-06-01
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-06-01 Ported from the following upstream stable releases: v4.19.124, v5.4.42 from git://git.kernel.org/ net: dsa: Do not make user port errors fatal shmem: fix possible deadlocks on shmlock_user_lock net/sonic: Fix a resource leak in an error handling path in 'jazz_sonic_probe()' net: moxa: Fix a potential double 'free_irq()' drop_monitor: work around gcc-10 stringop-overflow warning virtio-blk: handle block_device_operations callbacks after hot unplug scsi: sg: add sg_remove_request in sg_write mmc: sdhci-acpi: Add SDHCI_QUIRK2_BROKEN_64_BIT_DMA for AMDI0040 net: fix a potential recursive NETDEV_FEAT_CHANGE netlabel: cope with NULL catmap net: phy: fix aneg restart in phy_ethtool_set_eee pppoe: only process PADT targeted at local interfaces Revert "ipv6: add mtu lock check in __ip6_rt_update_pmtu" tcp: fix error recovery in tcp_zerocopy_receive() virtio_net: fix lockdep warning on 32 bit hinic: fix a bug of ndo_stop net: dsa: loop: Add module soft dependency net: ipv4: really enforce backoff for redirects netprio_cgroup: Fix unlimited memory leak of v2 cgroups net: tcp: fix rx timestamp behavior for tcp_recvmsg tcp: fix SO_RCVLOWAT hangs with fat skbs riscv: fix vdso build with lld dmaengine: pch_dma.c: Avoid data race between probe and irq handler dmaengine: mmp_tdma: Reset channel error on release cpufreq: intel_pstate: Only mention the BIOS disabling turbo mode once ALSA: hda/hdmi: fix race in monitor detection during probe drm/qxl: lost qxl_bo_kunmap_atomic_page in qxl_image_init_helper() ipc/util.c: sysvipc_find_ipc() incorrectly updates position index ALSA: hda/realtek - Fix S3 pop noise on Dell Wyse gfs2: Another gfs2_walk_metadata fix pinctrl: baytrail: Enable pin configuration setting for GPIO chip pinctrl: cherryview: Add missing spinlock usage in chv_gpio_irq_handler i40iw: Fix error handling in i40iw_manage_arp_cache() mmc: core: Check request type before completing the request mmc: block: Fix request completion in the CQE timeout path NFS: Fix fscache super_cookie index_key from changing after umount nfs: fscache: use timespec64 in inode auxdata NFSv4: Fix fscache cookie aux_data to ensure change_attr is included netfilter: conntrack: avoid gcc-10 zero-length-bounds warning arm64: fix the flush_icache_range arguments in machine_kexec netfilter: nft_set_rbtree: Introduce and use nft_rbtree_interval_start() IB/mlx4: Test return value of calls to ib_get_cached_pkey hwmon: (da9052) Synchronize access with mfd pnp: Use list_for_each_entry() instead of open coding gcc-10 warnings: fix low-hanging fruit Stop the ad-hoc games with -Wno-maybe-initialized UBUNTU: [Config] updateconfigs for CC_HAS_WARN_MAYBE_UNINITIALIZED gcc-10: disable 'zero-length-bounds' warning for now gcc-10: disable 'array-bounds' warning for now gcc-10: disable 'stringop-overflow' warning for now gcc-10: disable 'restrict' warning for now gcc-10: avoid shadowing standard library 'free()' in crypto ALSA: hda/realtek - Limit int mic boost for Thinkpad T530 ALSA: rawmidi: Fix racy buffer resize under concurrent accesses ALSA: usb-audio: Add control message quirk delay for Kingston HyperX headset usb: core: hub: limit HUB_QUIRK_DISABLE_AUTOSUSPEND to USB5534B usb: host: xhci-plat: keep runtime active when removing host USB: gadget: fix illegal array access in binding with UDC usb: xhci: Fix NULL pointer dereference when enqueuing trbs from urb sg list ARM: dts: dra7: Fix bus_dma_limit for PCIe ARM: dts: imx27-phytec-phycard-s-rdk: Fix the I2C1 pinctrl entries cifs: fix leaked reference on requeued write x86: Fix early boot crash on gcc-10, third try x86/unwind/orc: Fix error handling in __unwind_start() exec: Move would_dump into flush_old_exec clk: rockchip: fix incorrect configuration of rk3228 aclk_gpu* clocks dwc3: Remove check for HWO flag in dwc3_gadget_ep_reclaim_trb_sg() usb: gadget: net2272: Fix a memory leak in an error handling path in 'net2272_plat_probe()' usb: gadget: audio: Fix a missing error return value in audio_bind() usb: gadget: legacy: fix error return code in gncm_bind() usb: gadget: legacy: fix error return code in cdc_bind() Revert "ALSA: hda/realtek: Fix pop noise on ALC225" clk: Unlink clock if failed to prepare or enable arm64: dts: rockchip: Replace RK805 PMIC node name with "pmic" on rk3328 boards arm64: dts: rockchip: Rename dwc3 device nodes on rk3399 to make dtc happy ARM: dts: r8a73a4: Add missing CMT1 interrupts arm64: dts: renesas: r8a77980: Fix
[Kernel-packages] [Bug 1881631] [NEW] arm64 Ubuntu kernel builds missing CONFIG_NLS_ASCII
Public bug reported: Remounting log mounts in Ubuntu core are failing on arm64 builds due to missing CONFIG_NLS_ASCII in the arm64 kernel build options. This option is enabled on the other kernel builds but somehow was overlooked on arm64 appears to affect our ability to access logs via journalctl with data from prior to restart because certain mounts are failing. Other Raspberry Pi kernel builds, such as the armhf build, have the option enabled and so do not encounter the mount error. The kernel option that needs to be turned on to resolve this is CONFIG_NLS_ASCII. It needs to be set to either 'm' or 'y'. Most of the other chips have it set to 'y', keeping it built-in. ** Affects: linux-raspi2 (Ubuntu) Importance: Undecided Status: New -- 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/1881631 Title: arm64 Ubuntu kernel builds missing CONFIG_NLS_ASCII Status in linux-raspi2 package in Ubuntu: New Bug description: Remounting log mounts in Ubuntu core are failing on arm64 builds due to missing CONFIG_NLS_ASCII in the arm64 kernel build options. This option is enabled on the other kernel builds but somehow was overlooked on arm64 appears to affect our ability to access logs via journalctl with data from prior to restart because certain mounts are failing. Other Raspberry Pi kernel builds, such as the armhf build, have the option enabled and so do not encounter the mount error. The kernel option that needs to be turned on to resolve this is CONFIG_NLS_ASCII. It needs to be set to either 'm' or 'y'. Most of the other chips have it set to 'y', keeping it built-in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1881631/+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 1881631] Re: arm64 Ubuntu kernel builds missing CONFIG_NLS_ASCII
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-raspi2 (Ubuntu) Status: New => Confirmed -- 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/1881631 Title: arm64 Ubuntu kernel builds missing CONFIG_NLS_ASCII Status in linux-raspi2 package in Ubuntu: Confirmed Bug description: Remounting log mounts in Ubuntu core are failing on arm64 builds due to missing CONFIG_NLS_ASCII in the arm64 kernel build options. This option is enabled on the other kernel builds but somehow was overlooked on arm64 appears to affect our ability to access logs via journalctl with data from prior to restart because certain mounts are failing. Other Raspberry Pi kernel builds, such as the armhf build, have the option enabled and so do not encounter the mount error. The kernel option that needs to be turned on to resolve this is CONFIG_NLS_ASCII. It needs to be set to either 'm' or 'y'. Most of the other chips have it set to 'y', keeping it built-in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1881631/+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 1861070] Re: Raspberry Pi 4B: USB OTG is not working
so what is the state of this with ubuntu server 20.20 ? I added “dtoverlay=dwc2,dr_mode=peripheral“ to /boot/firmware/usercfg.txt but also never seeing the USB-C ethernet show up when connected to my Ubuntu 18.04 laptop. Then again I might be missing the equivalent of “modules-load=dwc2” as noted at https://www.hardill.me.uk/wordpress/2019/11/02/pi4-usb-c-gadget/ Note when connecting to my iPad Pro the pi never even boots, I suspect because it is not in the low power mode which apparently the steps from the above article configure in rasbian. -- 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/1861070 Title: Raspberry Pi 4B: USB OTG is not working Status in linux-raspi package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: Triaged Status in linux-raspi2 source package in Eoan: Fix Released Status in linux-raspi source package in Focal: Fix Committed Bug description: [Impact] On the RPI4B board, the usb-c power port could also work as a USB OTG mode, but we set the dwc2 driver to the host mode unconditionally, now set it to dual_role mode, then it could work in host/otg/peripheal mode. [Fix] Set USB_DWC2_DUAL_ROLE=y, USB_DWC2_HOST=n [Test Case] set the dtoverlay=dwc2,dr_mode=[otg|peripheral] in the config.txt, and isnmod the g_ether or g_cdc, on the host machine, we could see RPI4B work as a usb device. Because physical port limitation, could test dr_mode=host. [Regression Risk] Low, our eoan kernel choose dwc_otg driver for this port by default, very very few users will choose dwc2 driver, and the dwc2 driver is not enabled by default in our kernel. And bug reporter and I already tested that the peripheral mode works after this change. I am using Raspberry Pi 4B (4GB) and want to make use of the OTG functionality (g_ether). I cross checked with Raspbian to make sure it is not a hardware issue. Extract from dmesg of Ubuntu 19.10.1 with latest updates applied as of Jan 26th, 2020 via "apt-get update" and "apt-get full-upgrade": ... [1.514262] dwc_otg: version 3.00a 10-AUG-2012 (platform bus) [1.517365] dwc_otg: FIQ enabled [1.517376] dwc_otg: NAK holdoff enabled [1.517386] dwc_otg: FIQ split-transaction FSM enabled [1.517399] Module dwc_common_port init ... [6.358332] dwc2 fe98.usb: fe98.usb supply vusb_d not found, using dummy regulator [6.358388] dwc2 fe98.usb: fe98.usb supply vusb_a not found, using dummy regulator [6.358545] dwc2 fe98.usb: Configuration mismatch. dr_mode forced to host [6.409098] dwc2 fe98.usb: DWC OTG Controller [6.409399] dwc2 fe98.usb: new USB bus registered, assigned bus number 3 [6.409432] dwc2 fe98.usb: irq 23, io mem 0xfe98 ... [ 111.796714] udc-core: couldn't find an available UDC - added [g_ether] to list of pending drivers I think it is that "Configuration mismatch. dr_mode forced to host" log entry telling me that the port is acting as HOST mode instead of OTG mode. I have try putting these in usercfg.txt "dtoverlay=dwc2" "dtoverlay=dwc2,dr_mode=otg" "dtoverlay=dwc2,dr_mode=peripheral" and it will give the same result, no OTG functionality. On the same hardware running Raspbian Buster, it initialise successfully. Corresponding dmesg: ... [0.567531] dwc_otg: version 3.00a 10-AUG-2012 (platform bus) [0.570391] dwc_otg: FIQ enabled [0.570400] dwc_otg: NAK holdoff enabled [0.570409] dwc_otg: FIQ split-transaction FSM enabled [0.570421] Module dwc_common_port init ... [2.507634] dwc2 fe98.usb: fe98.usb supply vusb_d not found, using dummy regulator [2.511011] dwc2 fe98.usb: Linked as a consumer to regulator.0 [2.514450] dwc2 fe98.usb: fe98.usb supply vusb_a not found, using dummy regulator [2.731860] dwc2 fe98.usb: dwc2_check_params: Invalid parameter lpm=1 [2.735511] dwc2 fe98.usb: dwc2_check_params: Invalid parameter lpm_clock_gating=1 [2.735522] dwc2 fe98.usb: dwc2_check_params: Invalid parameter besl=1 [2.735533] dwc2 fe98.usb: dwc2_check_params: Invalid parameter hird_threshold_en=1 [2.735582] dwc2 fe98.usb: EPs: 8, dedicated fifos, 4080 entries in SPRAM [2.752511] dwc2 fe98.usb: DWC OTG Controller [2.752554] dwc2 fe98.usb: new USB bus registered, assigned bus number 3 [2.752601] dwc2 fe98.usb: irq 36, io mem 0xfe98 ... [2.848843] g_ether gadget: Ethernet Gadget, version: Memorial Day 2008 [2.851601] g_ether gadget: g_ether ready [2.854580] dwc2 fe98.usb: bound driver g_ether [2.998525] dwc2 fe98.usb: new device is high-speed [3.075025] dwc2 fe98.usb: new device is high-speed [3.139338] dwc2 fe98.usb: new address 10 [
[Kernel-packages] [Bug 1881643] 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 1881643 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/1881643 Title: pmtu.sh net selftest fail with PMTU dst likely leaked Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Confirmed Bug description: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-focal/focal/ppc64el/l/linux/20200528_044656_7f57a@/log.gz [...] 03:48:34 DEBUG| [stdout] # TEST: ipv6: cleanup of cached exceptions - nexthop objects [FAIL] 03:48:34 DEBUG| [stdout] # can't delete veth device in a timely manner, PMTU dst likely leaked [...] 03:49:17 DEBUG| [stdout] not ok 16 selftests: net: pmtu.sh # exit=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881643/+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 1850439] Re: No sound on ASUS UX534FT
Alsa-info time: - Ubuntu Live CD in VM after power cycle: http://alsa-project.org/db/?f=a3bb092b7964d28cc8a206d0619172472653b48b - Ubuntu Live CD in VM after Windows VM was started: http://alsa-project.org/db/?f=316d1051a370a045a3e14d2fc456c6d06fd34ae4 -- 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/1850439 Title: No sound on ASUS UX534FT Status in linux package in Ubuntu: Confirmed Bug description: Hi, after instal Ubuntu in dual boot alongside Windows 10, I've realised there is no sound coming out of mine new ASUS Zenbook 15 UX534FT- AA024R in Ubuntu. In Windows there is no problem. Found this topic https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810214 which had the same problem with driver for Realtek ALC294 which is also mine sound card. But even with this fix it is not working on UX534FT. Can you please add fix also for this newer model? Description: Ubuntu 18.04.3 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.0.0-32-generic 5.0.0-32.34~18.04.2 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 29 15:11:25 2019 InstallationDate: Installed on 2019-10-29 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439/+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 1881643] [NEW] pmtu.sh net selftest fail with PMTU dst likely leaked
Public bug reported: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-focal/focal/ppc64el/l/linux/20200528_044656_7f57a@/log.gz [...] 03:48:34 DEBUG| [stdout] # TEST: ipv6: cleanup of cached exceptions - nexthop objects [FAIL] 03:48:34 DEBUG| [stdout] # can't delete veth device in a timely manner, PMTU dst likely leaked [...] 03:49:17 DEBUG| [stdout] not ok 16 selftests: net: pmtu.sh # exit=1 ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: 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/1881643 Title: pmtu.sh net selftest fail with PMTU dst likely leaked Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Confirmed Bug description: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-focal/focal/ppc64el/l/linux/20200528_044656_7f57a@/log.gz [...] 03:48:34 DEBUG| [stdout] # TEST: ipv6: cleanup of cached exceptions - nexthop objects [FAIL] 03:48:34 DEBUG| [stdout] # can't delete veth device in a timely manner, PMTU dst likely leaked [...] 03:49:17 DEBUG| [stdout] not ok 16 selftests: net: pmtu.sh # exit=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881643/+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 1881643] Re: pmtu.sh net selftest fail with PMTU dst likely leaked
** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) 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/1881643 Title: pmtu.sh net selftest fail with PMTU dst likely leaked Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Confirmed Bug description: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-focal/focal/ppc64el/l/linux/20200528_044656_7f57a@/log.gz [...] 03:48:34 DEBUG| [stdout] # TEST: ipv6: cleanup of cached exceptions - nexthop objects [FAIL] 03:48:34 DEBUG| [stdout] # can't delete veth device in a timely manner, PMTU dst likely leaked [...] 03:49:17 DEBUG| [stdout] not ok 16 selftests: net: pmtu.sh # exit=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881643/+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 1864871] Re: Failed to init Intel sound card in 20.04
@ Jeremie Tamburini (jeremie2) Thks mate. It works perfectly. Did exactly as you said and now my sound card is back on. -- 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/1864871 Title: Failed to init Intel sound card in 20.04 Status in linux package in Ubuntu: Confirmed Bug description: After installing current 20.04 release on ThinkBook 13s IML with Intel audio card there is no sound available because sound card not detected (only dummy output available in sound settings): $ alsamixer cannot open mixer: No such file or directory $ lspci -nnk |grep -A2 audio lspci: Unable to load libkmod resources: error -12 00:1f.3 Multimedia audio controller [0401]: Intel Corporation Device [8086:02c8] Subsystem: Lenovo Device [17aa:3816] Kernel driver in use: sof-audio-pci 00:1f.4 SMBus [0c05]: Intel Corporation Device [8086:02a3] Subsystem: Lenovo Device [17aa:3819] $ pacmd list-cards 0 card(s) available. $ dmesg |grep sof [0.755398] PCI-DMA: Using software bounce buffering for IO (SWIOTLB) [0.755400] software IO TLB: mapped [mem 0x7d91d000-0x8191d000] (64MB) [2.142149] systemd[1]: Mounting Mount unit for software-boutique, revision 54... [2.333772] systemd[1]: Mounted Mount unit for software-boutique, revision 54. [2.770307] sof-audio-pci :00:1f.3: warning: No matching ASoC machine driver found [2.770316] sof-audio-pci :00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040100 [2.770473] sof-audio-pci :00:1f.3: use msi interrupt mode [2.770696] sof-audio-pci :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [2.779359] sof-audio-pci :00:1f.3: hda codecs found, mask 5 [2.779360] sof-audio-pci :00:1f.3: using HDA machine driver skl_hda_dsp_generic now [2.817051] sof-audio-pci :00:1f.3: Direct firmware load for intel/sof/sof-cnl.ri failed with error -2 [2.817054] sof-audio-pci :00:1f.3: error: request firmware intel/sof/sof-cnl.ri failed err: -2 [2.817057] sof-audio-pci :00:1f.3: error: failed to load DSP firmware -2 [2.817058] sof-audio-pci :00:1f.3: error: sof_probe_work failed err: -2 I've found similar bug reported here: https://bugs.archlinux.org/task/64720 As a workaround I've added `snd_hda_intel.dmic_detect=0` to boot options and after that sound card successfully detected and started working. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-14-generic 5.4.0-14.17 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: MATE Date: Wed Feb 26 19:22:05 2020 InstallationDate: Installed on 2020-02-25 (1 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Alpha amd64 (20200221) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:0c02 Elan Microelectronics Corp. ELAN:Fingerprint Bus 001 Device 002: ID 04f2:b61e Chicony Electronics Co., Ltd Integrated Camera Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20RR ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic root=UUID=94f1e507-a44a-46a8-9163-548d27303afb ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-14-generic N/A linux-backports-modules-5.4.0-14-generic N/A linux-firmware1.186 SourcePackage: linux-5.4 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/29/2019 dmi.bios.vendor: LENOVO dmi.bios.version: CQCN24WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ThinkBook 13s-IML dmi.modalias: dmi:bvnLENOVO:bvrCQCN24WW:bd10/29/2019:svnLENOVO:pn20RR:pvrLenovoThinkBook13s-IML:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrLenovoThinkBook13s-IML: dmi.product.family: ThinkBook 13s-IML dmi.product.name: 20RR dmi.product.sku: LENOVO_MT_20RR_BU_idea_FM_ThinkBook 13s-IML dmi.product.version: Lenovo ThinkBook 13s-IML dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864871/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1850439] Re: No sound on ASUS UX534FT
I can also confirm that using these 4 commands sound works perfectly fine on UX533FTC. It seems that the only last 2 commands are needed to be executed in sequence, but using all 4 commands works fine too (or maybe I can't tell the difference? lol). hda-verb /dev/snd/hwC0D0 0x20 0x500 0x1b hda-verb /dev/snd/hwC0D0 0x20 0x477 0x4a4b hda-verb /dev/snd/hwC0D0 0x20 0x500 0xf hda-verb /dev/snd/hwC0D0 0x20 0x477 0x74 So in conclusion, if sound still doesn't work for someone, try these: Fix #1: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439/comments/141 Fix #2: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439/comments/148 Fix #3: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439/comments/149 It's also been historical issue with Asus laptops, when there is no sound after reboot from Windows to Linux. Full shutdown or sleep & wakeup fixes this. Maybe I unintentionally described this in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439/comments/148 :) -- 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/1850439 Title: No sound on ASUS UX534FT Status in linux package in Ubuntu: Confirmed Bug description: Hi, after instal Ubuntu in dual boot alongside Windows 10, I've realised there is no sound coming out of mine new ASUS Zenbook 15 UX534FT- AA024R in Ubuntu. In Windows there is no problem. Found this topic https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810214 which had the same problem with driver for Realtek ALC294 which is also mine sound card. But even with this fix it is not working on UX534FT. Can you please add fix also for this newer model? Description: Ubuntu 18.04.3 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.0.0-32-generic 5.0.0-32.34~18.04.2 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 29 15:11:25 2019 InstallationDate: Installed on 2019-10-29 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439/+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 1860284] Re: thinkpad thunderbolt 3 dock gen2 with pci memory allocation errors on Yoga C940 unless plugged in before boot
** Also affects: linux via https://bugzilla.kernel.org/show_bug.cgi?id=206459 Importance: Unknown Status: Unknown -- 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/1860284 Title: thinkpad thunderbolt 3 dock gen2 with pci memory allocation errors on Yoga C940 unless plugged in before boot Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: I have thinkpad thunderbolt 3 dock gen2 dock I am trying to use with a New Lenovo Yoga C940 laptop. - The dock works fine when plugged-in before boot. - The dock does NOT work when plugged after the system booted. - The dock does NOT work when plugged-in at boot, subsequently unplugged and plugged back in. When it fails, it fails with memory allocation messages such as: [ 342.507320] pci :2b:00.0: BAR 14: no space for [mem size 0x0c20] [ 342.507323] pci :2b:00.0: BAR 14: failed to assign [mem size 0x0c20] Things I tried: - Kernel mainline 5.4.12, same symptoms - Kernel mainline 5.5.-rc6, same symptoms. - Plugging it after powering up the laptop, but at the grub screen before boot. In this case the dock works fine after boot. Other potentially useful information to narrow it down: - The tests were done with only an ethernet cable and power plugged into the dock to minimize the number of moving parts... - Dock and laptop both have the very latest firmware as of 2020-01-17. - The displayport part of the dock always work, but all other ports (USB, ethernet, card readers fail) when plugged-in after boot. - Doesn't seem to be a thunderbolt authorization problem: benoitg@benoitg-Yoga-C940:~$ boltctl ? Lenovo ThinkPad Thunderbolt 3 Dock ?? type: peripheral ?? name: ThinkPad Thunderbolt 3 Dock ?? vendor:Lenovo ?? uuid: 001730c5-7042-0801-- ?? status:authorized ? ?? domain: c06e823d-af8a-8680-- ? ?? authflags: none ?? authorized:Sun Jan 19 17:41:04 2020 ?? connected: Sun Jan 19 17:41:04 2020 ?? stored:Thu Jan 16 07:27:43 2020 ?? policy: iommu ?? key:no ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-26-generic 5.3.0-26.28 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: benoitg1182 F pulseaudio CurrentDesktop: KDE Date: Sun Jan 19 12:38:17 2020 InstallationDate: Installed on 2020-01-16 (3 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 81Q9 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=078b76d6-6b72-4de4-9e10-f6ea33d9bc1a ro RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmware1.183.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/22/2019 dmi.bios.vendor: LENOVO dmi.bios.version: AUCN45WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga C940-14IIL dmi.modalias: dmi:bvnLENOVO:bvrAUCN45WW:bd08/22/2019:svnLENOVO:pn81Q9:pvrLenovoYogaC940-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYogaC940-14IIL: dmi.product.family: Yoga C940-14IIL dmi.product.name: 81Q9 dmi.product.sku: LENOVO_MT_81Q9_BU_idea_FM_Yoga C940-14IIL dmi.product.version: Lenovo Yoga C940-14IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1860284/+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 1850439] Re: No sound on ASUS UX534FT
For me (Asus UX533FTC) sound works fine when I execute those 2 commands after boot. However, when I was testing all those commands, sound did not always worked. These steps fixed it (run either after or before commands, or even right after boot): 1. Go to pavucontrol --> configuration 2. Change "Built in audio" from "Analog Stereo Duplex" to "Off". 3. Change "Built in audio" from "Off" to "Analog Stereo Duplex". 4. Sound starts to work (if required commands were already executed). Sound seem to be perfectly fine via both headphones and internal speakers. Did not notice any alienated sound yet. Haven't tested microphone via headphones jack, since I don't have such headphones... Microphone still doesn't work for me. None of provided QEMU dumps (when converted to scripts) made microphone start to work. -- 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/1850439 Title: No sound on ASUS UX534FT Status in linux package in Ubuntu: Confirmed Bug description: Hi, after instal Ubuntu in dual boot alongside Windows 10, I've realised there is no sound coming out of mine new ASUS Zenbook 15 UX534FT- AA024R in Ubuntu. In Windows there is no problem. Found this topic https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810214 which had the same problem with driver for Realtek ALC294 which is also mine sound card. But even with this fix it is not working on UX534FT. Can you please add fix also for this newer model? Description: Ubuntu 18.04.3 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.0.0-32-generic 5.0.0-32.34~18.04.2 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 29 15:11:25 2019 InstallationDate: Installed on 2019-10-29 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439/+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 1850439] Re: No sound on ASUS UX534FT
A bit background on how I figured out those 2 commands. So let's say you have 6 commands in total: A command B command C command D command E command F command Start executing commands one by one, from top to bottom (do NOT resort them). Let's assume your sound starts to work after command E. So you know that F is not needed. Now reboot, then do on/off procedure in pavucontrol (as I described in previous comment) and try in this sequence until you hear a sound (play something in a background): E command if did not work, try this: D command E command if did not work, try this: C command D command E command and so on. -- 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/1850439 Title: No sound on ASUS UX534FT Status in linux package in Ubuntu: Confirmed Bug description: Hi, after instal Ubuntu in dual boot alongside Windows 10, I've realised there is no sound coming out of mine new ASUS Zenbook 15 UX534FT- AA024R in Ubuntu. In Windows there is no problem. Found this topic https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810214 which had the same problem with driver for Realtek ALC294 which is also mine sound card. But even with this fix it is not working on UX534FT. Can you please add fix also for this newer model? Description: Ubuntu 18.04.3 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.0.0-32-generic 5.0.0-32.34~18.04.2 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 29 15:11:25 2019 InstallationDate: Installed on 2019-10-29 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439/+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 1881124] Re: I2C bus on Dell Edge Gateway stops working after upgrading to Ubuntu-4.4.0-180.210
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed- xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-xenial -- 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/1881124 Title: I2C bus on Dell Edge Gateway stops working after upgrading to Ubuntu-4.4.0-180.210 Status in HWE Next: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Committed Bug description: I2C stops working after kernel upgrade: [ 13.812210] i2c_designware 80860F41:01: Unknown Synopsys component type: 0x [ 13.855837] i2c_designware 80860F41:01: timeout in enabling adapter [ 14.856276] i2c_designware 80860F41:01: controller timed out [ 14.856288] i2c_designware 80860F41:01: Unknown Synopsys component type: 0x This is caused by the commit commit 5568c3f29fbd0ec0d9bb0f805bacc5755180c5cb Author: Andy Shevchenko Date: Fri Dec 4 23:49:18 2015 +0200 Revert "ACPI / LPSS: allow to use specific PM domain during ->probe()" BugLink: https://bugs.launchpad.net/bugs/1878232 commit b5f88dd1d6efc472e35ca1b21a44e662c5422088 upstream. The specific power domain can't be used in a way provided by the commit 01ac170ba29a, i.e. pointer to platform device is a subject to change during unbound / bind cycle. This reverts commit 01ac170ba29a9903ee590e1ef2d8e6b27b49a16c. Fixes: 3df2da968744 (Revert "ACPI / LPSS: introduce a 'proxy' device to power on LPSS for DMA") Signed-off-by: Andy Shevchenko Signed-off-by: Rafael J. Wysocki Signed-off-by: Greg Kroah-Hartman Signed-off-by: Ian May Signed-off-by: Kleber Sacilotto de Souza To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1881124/+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 1850439] Re: No sound on ASUS UX534FT
The strange thing is that built-in microphones ARE actually working on my notebook out of the box. At the least sound meter IS moving for internal microphones in the settings. And I also found out another bug when the topic starter has internal microphones working perfectly fine: https://www.linux.org/threads/asus-zenbook-15-ux534f-realtek-hd-audio- problem.27384/. Possibly, there are some differences in audio hardware between 534FTC and UX533FTC. I can't find any other explanation for that. -- 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/1850439 Title: No sound on ASUS UX534FT Status in linux package in Ubuntu: Confirmed Bug description: Hi, after instal Ubuntu in dual boot alongside Windows 10, I've realised there is no sound coming out of mine new ASUS Zenbook 15 UX534FT- AA024R in Ubuntu. In Windows there is no problem. Found this topic https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810214 which had the same problem with driver for Realtek ALC294 which is also mine sound card. But even with this fix it is not working on UX534FT. Can you please add fix also for this newer model? Description: Ubuntu 18.04.3 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.0.0-32-generic 5.0.0-32.34~18.04.2 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 29 15:11:25 2019 InstallationDate: Installed on 2019-10-29 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439/+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 1881433] Re: 5.3.0-1022-azure syslog flood: kernel: [ 897.770784] testing the buffer
*** This bug is a duplicate of bug 1879559 *** https://bugs.launchpad.net/bugs/1879559 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-azure (Ubuntu) Status: New => Confirmed -- 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/1881433 Title: 5.3.0-1022-azure syslog flood: kernel: [ 897.770784] testing the buffer Status in linux-azure package in Ubuntu: Confirmed Bug description: Updating azure VM kernel from 5.3.0-1020 to linux-image-azure 5.3.0.1022.22 results in syslog being flooded with May 30 18:56:58 kernel: [ 882.730807] testing the buffer May 30 18:56:58 kernel: [ 882.730831] testing the buffer May 30 18:56:58 kernel: [ 882.730842] testing the buffer May 30 18:56:58 kernel: [ 882.730921] testing the buffer May 30 18:56:58 kernel: [ 882.730934] testing the buffer May 30 18:57:03 kernel: [ 887.743339] testing the buffer May 30 18:57:03 kernel: [ 887.743364] testing the buffer May 30 18:57:03 kernel: [ 887.743375] testing the buffer May 30 18:57:03 kernel: [ 887.743453] testing the buffer May 30 18:57:03 kernel: [ 887.743465] testing the buffer May 30 18:57:08 kernel: [ 892.756017] testing the buffer May 30 18:57:08 kernel: [ 892.756043] testing the buffer May 30 18:57:08 kernel: [ 892.756055] testing the buffer May 30 18:57:08 kernel: [ 892.756149] testing the buffer May 30 18:57:08 kernel: [ 892.756162] testing the buffer May 30 18:57:13 kernel: [ 897.770663] testing the buffer May 30 18:57:13 kernel: [ 897.770687] testing the buffer May 30 18:57:13 kernel: [ 897.770697] testing the buffer May 30 18:57:13 kernel: [ 897.770773] testing the buffer May 30 18:57:13 kernel: [ 897.770784] testing the buffer type messages Ref: https://github.com/clearlinux/distribution/issues/1878 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1881433/+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 1850439] Re: No sound on ASUS UX534FT
Nice. One more thing - if you can't get sound to work, then you need to: 1. Completely shutdown the laptop 2. Unplug charger 3. Wait few seconds 4. (optional) plug charger back 5. power on and apply commands. Sound works. Is there something else we are missing? Like power reset command or something? -- 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/1850439 Title: No sound on ASUS UX534FT Status in linux package in Ubuntu: Confirmed Bug description: Hi, after instal Ubuntu in dual boot alongside Windows 10, I've realised there is no sound coming out of mine new ASUS Zenbook 15 UX534FT- AA024R in Ubuntu. In Windows there is no problem. Found this topic https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810214 which had the same problem with driver for Realtek ALC294 which is also mine sound card. But even with this fix it is not working on UX534FT. Can you please add fix also for this newer model? Description: Ubuntu 18.04.3 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.0.0-32-generic 5.0.0-32.34~18.04.2 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 29 15:11:25 2019 InstallationDate: Installed on 2019-10-29 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439/+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 1875199] Re: [NUC8CCHK][HDA-Intel - HDA Intel PCH, playback] No sound at all
Gentle bump to raise visibility. In more information is needed please let me know. Thank you! -- 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/1875199 Title: [NUC8CCHK][HDA-Intel - HDA Intel PCH, playback] No sound at all Status in linux package in Ubuntu: Incomplete Bug description: No sound output. Only a 'Dummy' audio output device is listed in the Gnome Sound application. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rboerner 1205 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 26 12:12:49 2020 InstallationDate: Installed on 2020-04-25 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rboerner 1205 F pulseaudio Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/25/2020 dmi.bios.vendor: Intel Corp. dmi.bios.version: CHAPLCEL.0048.2020.0225.1640 dmi.board.name: NUC8CCHB dmi.board.vendor: Intel Corporation dmi.board.version: K44767-502 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrCHAPLCEL.0048.2020.0225.1640:bd02/25/2020:svnIntel(R)ClientSystems:pnNUC8CCHK:pvrK44798-502:rvnIntelCorporation:rnNUC8CCHB:rvrK44767-502:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: CH dmi.product.name: NUC8CCHK dmi.product.sku: BKNUC8CCHKR dmi.product.version: K44798-502 dmi.sys.vendor: Intel(R) Client Systems --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rboerner 1215 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-25 (6 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Intel(R) Client Systems NUC8CCHK Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=afbb0f64-e729-46a8-82e4-a060e9e729c4 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-28-generic N/A linux-backports-modules-5.4.0-28-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/25/2020 dmi.bios.vendor: Intel Corp. dmi.bios.version: CHAPLCEL.0048.2020.0225.1640 dmi.board.name: NUC8CCHB dmi.board.vendor: Intel Corporation dmi.board.version: K44767-502 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrCHAPLCEL.0048.2020.0225.1640:bd02/25/2020:svnIntel(R)ClientSystems:pnNUC8CCHK:pvrK44798-502:rvnIntelCorporation:rnNUC8CCHB:rvrK44767-502:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: CH dmi.product.name: NUC8CCHK dmi.product.sku: BKNUC8CCHKR dmi.product.version: K44798-502 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875199/+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 1850439] Re: No sound on ASUS UX534FT
Dumped all the coefficients when the sound is working and without any distortions: http://alsa- project.org/db/?f=79b20740c9abbd7427f166208b5a6a2e6449a174. NOTE: Dumping coefficients can be enabled via echo 1 | sudo tee /sys/module/snd_hda_codec/parameters/dump_coef -- 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/1850439 Title: No sound on ASUS UX534FT Status in linux package in Ubuntu: Confirmed Bug description: Hi, after instal Ubuntu in dual boot alongside Windows 10, I've realised there is no sound coming out of mine new ASUS Zenbook 15 UX534FT- AA024R in Ubuntu. In Windows there is no problem. Found this topic https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810214 which had the same problem with driver for Realtek ALC294 which is also mine sound card. But even with this fix it is not working on UX534FT. Can you please add fix also for this newer model? Description: Ubuntu 18.04.3 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.0.0-32-generic 5.0.0-32.34~18.04.2 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 29 15:11:25 2019 InstallationDate: Installed on 2019-10-29 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439/+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 1864871] Re: Failed to init Intel sound card in 20.04
Similar problem with: - Ubuntu 20.04 LTS - Fujitsu LifeBook A530 - $ lspci | grep Audio 00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 05) THE PROBLEM: No sound. Gnome audio system settings shows "Dummy Audio" as output device. Trying with Lubuntu 20.04 on a different partition there's the same problem but running PulseAudio Volume Control it's possible to select: "analog stereo duplex" or "analog stereo output". Unfortunately there is no setting like this for Gnome. WORKAROUND: As reported here https://forum.ubuntu-it.org/viewtopic.php?t=413914 it seems to be a problem related to udev which doesn't find the audio card. 1. Inside /etc/pulse/default.pa find the following code: .ifexists module-udev-detect.so load-module module-udev-detect .else ### Alternatively use the static hardware detection module (for systems that ### lack udev support) load-module module-detect .endif 2. Comment the if/else statement: ### Automatically load driver modules depending on the hardware available #.ifexists module-udev-detect.so #load-module module-udev-detect #.else ### Alternatively use the static hardware detection module (for systems that ### lack udev support) load-module module-detect #.endif 3. Save the file and restart. -- 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/1864871 Title: Failed to init Intel sound card in 20.04 Status in linux package in Ubuntu: Confirmed Bug description: After installing current 20.04 release on ThinkBook 13s IML with Intel audio card there is no sound available because sound card not detected (only dummy output available in sound settings): $ alsamixer cannot open mixer: No such file or directory $ lspci -nnk |grep -A2 audio lspci: Unable to load libkmod resources: error -12 00:1f.3 Multimedia audio controller [0401]: Intel Corporation Device [8086:02c8] Subsystem: Lenovo Device [17aa:3816] Kernel driver in use: sof-audio-pci 00:1f.4 SMBus [0c05]: Intel Corporation Device [8086:02a3] Subsystem: Lenovo Device [17aa:3819] $ pacmd list-cards 0 card(s) available. $ dmesg |grep sof [0.755398] PCI-DMA: Using software bounce buffering for IO (SWIOTLB) [0.755400] software IO TLB: mapped [mem 0x7d91d000-0x8191d000] (64MB) [2.142149] systemd[1]: Mounting Mount unit for software-boutique, revision 54... [2.333772] systemd[1]: Mounted Mount unit for software-boutique, revision 54. [2.770307] sof-audio-pci :00:1f.3: warning: No matching ASoC machine driver found [2.770316] sof-audio-pci :00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040100 [2.770473] sof-audio-pci :00:1f.3: use msi interrupt mode [2.770696] sof-audio-pci :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [2.779359] sof-audio-pci :00:1f.3: hda codecs found, mask 5 [2.779360] sof-audio-pci :00:1f.3: using HDA machine driver skl_hda_dsp_generic now [2.817051] sof-audio-pci :00:1f.3: Direct firmware load for intel/sof/sof-cnl.ri failed with error -2 [2.817054] sof-audio-pci :00:1f.3: error: request firmware intel/sof/sof-cnl.ri failed err: -2 [2.817057] sof-audio-pci :00:1f.3: error: failed to load DSP firmware -2 [2.817058] sof-audio-pci :00:1f.3: error: sof_probe_work failed err: -2 I've found similar bug reported here: https://bugs.archlinux.org/task/64720 As a workaround I've added `snd_hda_intel.dmic_detect=0` to boot options and after that sound card successfully detected and started working. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-14-generic 5.4.0-14.17 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: MATE Date: Wed Feb 26 19:22:05 2020 InstallationDate: Installed on 2020-02-25 (1 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Alpha amd64 (20200221) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:0c02 Elan Microelectronics Corp. ELAN:Fingerprint Bus 001 Device 002: ID 04f2:b61e Chicony Electronics Co., Ltd Integrated Camera Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20RR ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic root=UUID=94f1e507-a44a-46a8-9163-548d27303afb ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-14-generic N/A linux-backports-modules-5.4.0-14-generic N/A linux-firmware
[Kernel-packages] [Bug 1878484] Re: kernel panic on i915
It looks like it doesn't happen with 5.7.0-050700rc7-generic. I cannot be 100% sure as it happened randomly. I have got, however, something suspiciously similar that has never happened before. It has happened several times already, as randomly as when I got a kernel panic before. Screen hangs for a while, but system stays alive. Logs show: kernel: Asynchronous wait on fence :00:02.0:Xorg[33564]:a28c timed out (hint:intel_atomic_commit_ready+0x0/0x50 [i915]) kernel: i915 :00:02.0: GPU HANG: ecode 8:1:86dd, in Xorg [33564] kernel: i915 :00:02.0: Resetting rcs0 for stopped heartbeat on rcs0 kernel: i915 :00:02.0: Xorg[33564] context reset due to GPU hang -- 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/1878484 Title: kernel panic on i915 Status in linux package in Ubuntu: Incomplete Bug description: I'm using 20.04 fully up to date on an Asrock N3700. I'm getting random crashes every now and then. Total crash, no ssh or anything (later I found out it's a kernel panic). Not tied to any app, but it happened more often during gaming. Logs didn't show anything, they just stop. I set up netconsole, with debug and ignore_loglevel in the command line and I got this: [77196.866485] BUG: unable to handle page fault for address: 00a72860 [77196.866527] #PF: supervisor read access in kernel mode [77196.866535] #PF: error_code(0x) - not-present page [77196.866542] PGD 0 P4D 0 [77196.866552] Oops: [#1] SMP PTI [77196.866567] CPU: 2 PID: 1408 Comm: Xorg Tainted: P O 5.4.0-29-generic #33-Ubuntu [77196.866575] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./N3700-ITX, BIOS P2.00 04/16/2018 [77196.866743] RIP: 0010:__i915_schedule+0x261/0x350 [i915] [77196.866748] Code: ff a8 08 0f 84 a0 00 00 00 45 3b b4 24 18 04 00 00 7e 50 49 8b 84 24 d8 03 00 00 48 8b 00 48 85 c0 74 40 48 8b b3 30 ff ff ff <48> 39 70 60 74 33 45 89 b4 24 18 04 00 00 8b 80 60 01 00 00 be 00 [77196.866753] RSP: 0018:a48380c2b9e0 EFLAGS: 00010006 [77196.866759] RAX: 00a72800 RBX: 961bed909a30 RCX: 9619a559edb0 [77196.866764] RDX: 961bed909a50 RSI: 961beaa21180 RDI: 9619a559edc0 [77196.866769] RBP: a48380c2ba78 R08: 961bf73f4420 R09: 9619a559ed80 [77196.866773] R10: R11: 0208 R12: 961bf73f4000 [77196.866783] R13: a48380c2b9f0 R14: 1000 R15: a48380c2b9c0 [77196.866788] FS: 7f6ee2aa9a80() GS:961bf830() knlGS: [77196.866794] CS: 0010 DS: ES: CR0: 80050033 [77196.866798] CR2: 00a72860 CR3: 00026a0a2000 CR4: 001006e0 [77196.866802] Call Trace: [77196.866887] i915_schedule+0x2d/0x50 [i915] [77196.866979] __fence_set_priority+0x6b/0x90 [i915] [77196.867067] fence_set_priority+0x23/0x60 [i915] [77196.867117] i915_gem_object_wait_priority+0x13e/0x170 [i915] [77196.867194] intel_prepare_plane_fb+0x1ab/0x2d0 [i915] [77196.867232] drm_atomic_helper_prepare_planes+0x94/0x120 [drm_kms_helper] [77196.867305] intel_atomic_commit+0xc2/0x2b0 [i915] [77196.867370] drm_atomic_nonblocking_commit+0x4d/0x60 [drm] [77196.867401] drm_atomic_helper_page_flip+0x63/0xa0 [drm_kms_helper] [77196.867443] drm_mode_page_flip_ioctl+0x59d/0x630 [drm] [77196.867469] ? drm_mode_cursor2_ioctl+0x10/0x10 [drm] [77196.867490] drm_ioctl_kernel+0xae/0xf0 [drm] [77196.867512] drm_ioctl+0x234/0x3d0 [drm] [77196.867536] ? drm_mode_cursor2_ioctl+0x10/0x10 [drm] [77196.867550] do_vfs_ioctl+0x407/0x670 [77196.867560] ? fput+0x13/0x15 [77196.867568] ? __sys_recvmsg+0x88/0xa0 [77196.867575] ksys_ioctl+0x67/0x90 [77196.867582] __x64_sys_ioctl+0x1a/0x20 [77196.867592] do_syscall_64+0x57/0x190 [77196.867603] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [77196.867611] RIP: 0033:0x7f6ee2e0737b [77196.867618] Code: 0f 1e fa 48 8b 05 15 3b 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d e5 3a 0d 00 f7 d8 64 89 01 48 [77196.867624] RSP: 002b:7ffe6ff493d8 EFLAGS: 0246 ORIG_RAX: 0010 [77196.867631] RAX: ffda RBX: 7ffe6ff49410 RCX: 7f6ee2e0737b [77196.867635] RDX: 7ffe6ff49410 RSI: c01864b0 RDI: 000e [77196.867640] RBP: c01864b0 R08: 002bf8f2 R09: 006a [77196.867645] R10: 000e R11: 0246 R12: 56454c520040 [77196.867649] R13: 000e R14: 002bf8f2 R15: 0002 [77196.867655] Modules linked in: bnep wireguard(O) ip6_udp_tunnel udp_tunnel binfmt_misc zfs(PO) zunicode(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) zlua(PO) joydev input_leds nls_iso8859_1 snd_hda_codec_hdmi
[Kernel-packages] [Bug 1645037] Re: apparmor_parser hangs indefinitely when called by multiple threads
** No longer affects: apparmor (Ubuntu)
** No longer affects: linux (Ubuntu Xenial)
--
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/1645037
Title:
apparmor_parser hangs indefinitely when called by multiple threads
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Yakkety:
Won't Fix
Status in linux source package in Zesty:
Fix Released
Bug description:
This bug surfaced when starting ~50 LXC container with LXD in parallel
multiple times:
# Create the containers
for c in c foo{1..50}; do lxc launch images:ubuntu/xenial $c; done
# Exectute this loop multiple times until you observe errors.
for c in c foo{1..50}; do lxc restart $c & done
After this you can
ps aux | grep apparmor
and you should see output similar to:
root 19774 0.0 0.0 12524 1116 pts/1S+ 20:14 0:00
apparmor_parser -RWL /var/lib/lxd/security/apparmor/cache
/var/lib/lxd/security/apparmor/profiles/lxd-foo30
root 19775 0.0 0.0 12524 1208 pts/1S+ 20:14 0:00
apparmor_parser -RWL /var/lib/lxd/security/apparmor/cache
/var/lib/lxd/security/apparmor/profiles/lxd-foo26
root 19776 0.0 0.0 13592 3224 pts/1D+ 20:14 0:00
apparmor_parser -RWL /var/lib/lxd/security/apparmor/cache
/var/lib/lxd/security/apparmor/profiles/lxd-foo30
root 19778 0.0 0.0 13592 3384 pts/1D+ 20:14 0:00
apparmor_parser -RWL /var/lib/lxd/security/apparmor/cache
/var/lib/lxd/security/apparmor/profiles/lxd-foo26
root 19780 0.0 0.0 12524 1208 pts/1S+ 20:14 0:00
apparmor_parser -RWL /var/lib/lxd/security/apparmor/cache
/var/lib/lxd/security/apparmor/profiles/lxd-foo43
root 19782 0.0 0.0 12524 1208 pts/1S+ 20:14 0:00
apparmor_parser -RWL /var/lib/lxd/security/apparmor/cache
/var/lib/lxd/security/apparmor/profiles/lxd-foo34
root 19783 0.0 0.0 13592 3388 pts/1D+ 20:14 0:00
apparmor_parser -RWL /var/lib/lxd/security/apparmor/cache
/var/lib/lxd/security/apparmor/profiles/lxd-foo43
root 19784 0.0 0.0 13592 3252 pts/1D+ 20:14 0:00
apparmor_parser -RWL /var/lib/lxd/security/apparmor/cache
/var/lib/lxd/security/apparmor/profiles/lxd-foo34
root 19794 0.0 0.0 12524 1208 pts/1S+ 20:14 0:00
apparmor_parser -RWL /var/lib/lxd/security/apparmor/cache
/var/lib/lxd/security/apparmor/profiles/lxd-foo25
root 19795 0.0 0.0 13592 3256 pts/1D+ 20:14 0:00
apparmor_parser -RWL /var/lib/lxd/security/apparmor/cache
/var/lib/lxd/security/apparmor/profiles/lxd-foo25
apparmor_parser remains stuck even after all LXC/LXD commands have
exited.
dmesg output yields lines like:
[41902.815174] audit: type=1400 audit(1480191089.678:43):
apparmor="STATUS" operation="profile_load" profile="unconfined" name
="lxd-foo30_" pid=12545 comm="apparmor_parser"
and cat /proc/12545/stack shows:
[] aa_remove_profiles+0x88/0x270
21:19 brauner [] profile_remove+0x144/0x2e0
21:19 brauner [] __vfs_write+0x18/0x40
21:19 brauner [] vfs_write+0xb8/0x1b0
21:19 brauner [] SyS_write+0x55/0xc0
21:19 brauner [] entry_SYSCALL_64_fastpath+0x1e/0xa8
21:19 brauner [] 0x
This looks like a potential kernel bug.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1645037/+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 1880032] Re: [linux-azure] Enable Hibernation on The 18.04 and 20.04 5.4 Kernels
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-azure (Ubuntu) Status: New => Confirmed -- 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/1880032 Title: [linux-azure] Enable Hibernation on The 18.04 and 20.04 5.4 Kernels Status in linux-azure package in Ubuntu: Confirmed Bug description: Microsoft would like to request commits to enable VM hibernation in the Azure 5.4 kernels for 18.04 and 20.04. Some of the commits needed to enable VM hibernation were included in mainline 5.4 and older. However, 24 commits were added in 5.5 and later, which are required in the 5.4 kernel. The list of commits requested are: 38dce4195f0d x86/hyperv: Properly suspend/resume reenlightenment notifications 2351f8d295ed PM: hibernate: Freeze kernel threads in software_resume() 421f090c819d x86/hyperv: Suspend/resume the VP assist page for hibernation 1a06d017fb3f Drivers: hv: vmbus: Fix Suspend-to-Idle for Generation-2 VM 3704a6a44579 PM: hibernate: Propagate the return value of hibernation_restore() 54e19d34011f hv_utils: Add the support of hibernation ffd1d4a49336 hv_utils: Support host-initiated hibernation request 3e9c72056ed5 hv_utils: Support host-initiated restart request 9fc3c01a1fae6 Tools: hv: Reopen the devices if read() or write() returns 05bd330a7fd8 x86/hyperv: Suspend/resume the hypercall page for hibernation 382a46221757 video: hyperv_fb: Fix hibernation for the deferred IO feature e2379b30324c Input: hyperv-keyboard: Add the support of hibernation ac82fc8327088 PCI: hv: Add hibernation support a8e37506e79a PCI: hv: Reorganize the code in preparation of hibernation 1349401ff1aa4 clocksource/drivers/hyper-v: Suspend/resume Hyper-V clocksource for hibernation af13f9ed6f9a HID: hyperv: Add the support of hibernation 25bd2b2f1f053 hv_balloon: Add the support of hibernation b96f86534fa31 x86/hyperv: Implement hv_is_hibernation_supported() 4df4cb9e99f83 x86/hyperv: Initialize clockevents earlier in CPU onlining 0efeea5fb1535 hv_netvsc: Add the support of hibernation 2194c2eb6717f hv_sock: Add the support of hibernation 1ecf302021040 video: hyperv_fb: Add the support of hibernation 56fb105859345 scsi: storvsc: Add the support of hibernation f2c33ccacb2d4 PCI/PM: Always return devices to D0 when thawing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1880032/+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 1881623] Re: USB support missing in initrd makes booting core with writable on USB impossible
** Description changed: when using a gadget.yaml like: volumes: pi4-system-boot: schema: mbr bootloader: u-boot structure: - type: 0C filesystem: vfat filesystem-label: system-boot size: 512M content: - source: boot-assets/ target: / pi4-usb-writable: schema: mbr structure: - name: writable type: 83 filesystem: ext4 filesystem-label: writable size: 650M role: system-data this creates two separate img files for a Pi image ... one for SD to hold the boot files, one for USB that carries the rootfs ... sadly our kernel will then not find the writable partition because it lacks support for usb disks (usb-storage seems to be there but not sufficient) adding the following to a re-built kernel snap makes everything work (verified with USB 3.1 SSD on a pi4 as well as various USB 3.0 keys) - CONFIG_ENCLOSURE_SERVICES=y - CONFIG_SCSI_SAS_ATTRS=y - CONFIG_USB_STORAGE=y - CONFIG_USB_UAS=y can we please have these either built into the kernel or added to the - initrd as modules ? + core initrd as modules ? -- 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/1881623 Title: USB support missing in initrd makes booting core with writable on USB impossible Status in linux-raspi package in Ubuntu: New Status in linux-raspi2 package in Ubuntu: Confirmed Bug description: when using a gadget.yaml like: volumes: pi4-system-boot: schema: mbr bootloader: u-boot structure: - type: 0C filesystem: vfat filesystem-label: system-boot size: 512M content: - source: boot-assets/ target: / pi4-usb-writable: schema: mbr structure: - name: writable type: 83 filesystem: ext4 filesystem-label: writable size: 650M role: system-data this creates two separate img files for a Pi image ... one for SD to hold the boot files, one for USB that carries the rootfs ... sadly our kernel will then not find the writable partition because it lacks support for usb disks (usb-storage seems to be there but not sufficient) adding the following to a re-built kernel snap makes everything work (verified with USB 3.1 SSD on a pi4 as well as various USB 3.0 keys) - CONFIG_ENCLOSURE_SERVICES=y - CONFIG_SCSI_SAS_ATTRS=y - CONFIG_USB_STORAGE=y - CONFIG_USB_UAS=y can we please have these either built into the kernel or added to the core initrd as modules ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1881623/+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 1850439] Re: No sound on ASUS UX534FT
Another, shorter sample with warning (?) audio clip (play from terminal when there is nothing more to do). ** Attachment added: "Sound sample - noisy sound from speakers 2" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439/+attachment/5379388/+files/noisy_sound_notification.m4a -- 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/1850439 Title: No sound on ASUS UX534FT Status in linux package in Ubuntu: Confirmed Bug description: Hi, after instal Ubuntu in dual boot alongside Windows 10, I've realised there is no sound coming out of mine new ASUS Zenbook 15 UX534FT- AA024R in Ubuntu. In Windows there is no problem. Found this topic https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810214 which had the same problem with driver for Realtek ALC294 which is also mine sound card. But even with this fix it is not working on UX534FT. Can you please add fix also for this newer model? Description: Ubuntu 18.04.3 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.0.0-32-generic 5.0.0-32.34~18.04.2 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 29 15:11:25 2019 InstallationDate: Installed on 2019-10-29 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439/+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 1873809] Re: Make linux-kvm bootable in LXD VMs
Pinged in #ubuntu-kernel today for an update. It'd be good to have groovy signed soon so we can then roll this out to focal users. -- 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/1873809 Title: Make linux-kvm bootable in LXD VMs Status in cloud-images: Invalid Status in linux-kvm package in Ubuntu: Triaged Bug description: The `disk-kvm.img` images which are to be preferred when run under virtualization, currently completely fail to boot under UEFI. A workaround was put in place such that LXD instead will pull generic- based images until this is resolved, this however does come with a much longer boot time (as the kernel panics, reboots and then boots) and also reduced functionality from cloud-init, so we'd still like this fixed in the near future. To get things behaving, it looks like we need the following config options to be enable in linux-kvm: - CONFIG_EFI_STUB - CONFIG_VSOCKETS - CONFIG_VIRTIO_VSOCKETS - CONFIG_VIRTIO_VSOCKETS_COMMON == Rationale == We'd like to be able to use the linux-kvm based images for LXD, those will directly boot without needing the panic+reboot behavior of generic images and will be much lighter in general. We also need the LXD agent to work, which requires functional virtio vsock. == Test case == - wget http://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64-lxd.tar.xz - wget http://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64-disk-kvm.img - lxc image import focal-server-cloudimg-amd64-lxd.tar.xz focal-server-cloudimg-amd64-disk-kvm.img --alias bug1873809 - lxc launch bug1873809 v1 - lxc console v1 - - - lxc exec v1 bash To validate a new kernel, you'll need to manually repack the .img file and install the new kernel in there. == Regression potential == I don't know who else is using those kvm images right now, but those changes will cause a change to the kernel binary such that it contains the EFI stub bits + a signature. This could cause some (horribly broken) systems to no longer be able to boot that kernel. Though considering that such a setup is common to our other kernels, this seems unlikely. Also, this will be introducing virtio vsock support which again, could maybe confused some horribly broken systems? In either case, the kernel conveniently is the only package which ships multiple versions concurently, so rebooting on the previous kernel is always an option, mitigating some of the risks. -- Details from original report -- User report on the LXD side: https://github.com/lxc/lxd/issues/7224 I've reproduced this issue with: - wget http://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64-disk-kvm.img - qemu-system-x86_64 -bios /usr/share/ovmf/OVMF.fd -hda focal-server-cloudimg-amd64-disk-kvm.img -m 1G On the graphical console, you'll see EDK2 load (TianoCore) followed by basic boot messages and then a message from grub (error: can't find command `hwmatch`). Those also appear on successful boots of other images so I don't think there's anything concerning that. However it'll hang indefinitely and eat up all your CPU. Switching to the text console view (serial0), you'll see the same issue as that LXD report: BdsDxe: failed to load Boot0001 "UEFI QEMU DVD-ROM QM3 " from PciRoot(0x0)/Pci(0x1,0x1)/Ata(Secondary,Master,0x0): Not Found BdsDxe: loading Boot0002 "UEFI QEMU HARDDISK QM1 " from PciRoot(0x0)/Pci(0x1,0x1)/Ata(Primary,Master,0x0) BdsDxe: starting Boot0002 "UEFI QEMU HARDDISK QM1 " from PciRoot(0x0)/Pci(0x1,0x1)/Ata(Primary,Master,0x0) error: can't find command `hwmatch'. e X64 Exception Type - 0D(#GP - General Protection) CPU Apic ID - ExceptionData - RIP - 3FF2DA12, CS - 0038, RFLAGS - 00200202 RAX - AFAFAFAFAFAFAFAF, RCX - 3E80F108, RDX - AFAFAFAFAFAFAFAF RBX - 0398, RSP - 3FF1C638, RBP - 3FF34360 RSI - 3FF343B8, RDI - 1000 R8 - 3E80F108, R9 - 3E815B98, R10 - 0065 R11 - 2501, R12 - 0004, R13 - 3E80F100 R14 - , R15 - DS - 0030, ES - 0030, FS - 0030 GS - 0030, SS - 0030 CR0 - 80010033, CR2 - , CR3 - 3FC01000 CR4 - 0668, CR8 - DR0 - , DR1 - , DR2 - DR3 - , DR6 - 0FF0, DR7 - 0400 GDTR - 3FBEEA98 0047, LDTR - IDTR - 3F2D8018 0FFF, TR - FXSAVE_STATE - 3FF1C290 Find image
[Kernel-packages] [Bug 1850439] Re: No sound on ASUS UX534FT
Here is the behaviour on my UX534FTC: 1. Power cycle. 2. Execute two commands from the Erikas' comment. 3. Start youtube video with sound. Actual result: No sound from speakers. 4. Execute two commands again while the video is playing. Actual result: Sound appears with the same quality as in my comment #133 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439/comments/133). Audio samples will be published in a minute. -- 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/1850439 Title: No sound on ASUS UX534FT Status in linux package in Ubuntu: Confirmed Bug description: Hi, after instal Ubuntu in dual boot alongside Windows 10, I've realised there is no sound coming out of mine new ASUS Zenbook 15 UX534FT- AA024R in Ubuntu. In Windows there is no problem. Found this topic https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810214 which had the same problem with driver for Realtek ALC294 which is also mine sound card. But even with this fix it is not working on UX534FT. Can you please add fix also for this newer model? Description: Ubuntu 18.04.3 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.0.0-32-generic 5.0.0-32.34~18.04.2 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 29 15:11:25 2019 InstallationDate: Installed on 2019-10-29 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439/+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 1850439] Re: No sound on ASUS UX534FT
Headphones are not working - there is nothing beyond some "alien" sounds from headphones' speakers. ** Attachment added: "Alien noises from headphones" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439/+attachment/5379389/+files/headphone_not_working.m4a -- 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/1850439 Title: No sound on ASUS UX534FT Status in linux package in Ubuntu: Confirmed Bug description: Hi, after instal Ubuntu in dual boot alongside Windows 10, I've realised there is no sound coming out of mine new ASUS Zenbook 15 UX534FT- AA024R in Ubuntu. In Windows there is no problem. Found this topic https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810214 which had the same problem with driver for Realtek ALC294 which is also mine sound card. But even with this fix it is not working on UX534FT. Can you please add fix also for this newer model? Description: Ubuntu 18.04.3 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.0.0-32-generic 5.0.0-32.34~18.04.2 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 29 15:11:25 2019 InstallationDate: Installed on 2019-10-29 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439/+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 1850439] Re: No sound on ASUS UX534FT
The sound has a strange digital whistle (?) in it. This whistle be head clearly with higher-pitch sounds. ** Attachment added: "Sound sample - noisy sound from speakers" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439/+attachment/5379380/+files/noisy_sound_speech_sample.m4a -- 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/1850439 Title: No sound on ASUS UX534FT Status in linux package in Ubuntu: Confirmed Bug description: Hi, after instal Ubuntu in dual boot alongside Windows 10, I've realised there is no sound coming out of mine new ASUS Zenbook 15 UX534FT- AA024R in Ubuntu. In Windows there is no problem. Found this topic https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810214 which had the same problem with driver for Realtek ALC294 which is also mine sound card. But even with this fix it is not working on UX534FT. Can you please add fix also for this newer model? Description: Ubuntu 18.04.3 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.0.0-32-generic 5.0.0-32.34~18.04.2 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 29 15:11:25 2019 InstallationDate: Installed on 2019-10-29 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439/+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 1881629] [NEW] Can't turn on Bluetooth after turning it off
Public bug reported: Hey there! I am encountering a bug in Bluetooth menu in drop down menu at top right corner. Whenever i turn off my Bluetooth there is no option to turn on there. It shows two option turn off and Bluetooth setting. After I open setting and try to turn it on from there it doesn't turn on. I need to restart the system to make it work. Please fix this issue. Thank You Vipin Singh Negi ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 1 22:50:43 2020 InstallationDate: Installed on 2020-05-31 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Hewlett-Packard HP Pavilion g4 Notebook PC ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=8fbb62c5-9c67-4904-a243-2c34253fd16a ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/13/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.6A dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3564 dmi.board.vendor: Hewlett-Packard dmi.board.version: 21.46 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.6A:bd05/13/2013:svnHewlett-Packard:pnHPPaviliong4NotebookPC:pvr06911320461610100:rvnHewlett-Packard:rn3564:rvr21.46:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP Pavilion g4 Notebook PC dmi.product.sku: D7Z60PC#ACJ dmi.product.version: 06911320461610100 dmi.sys.vendor: Hewlett-Packard hciconfig: hci0: Type: Primary Bus: USB BD Address: 48:D2:24:58:55:67 ACL MTU: 1022:8 SCO MTU: 183:5 DOWN RX bytes:1957 acl:0 sco:0 events:90 errors:0 TX bytes:4974 acl:0 sco:0 commands:75 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1881629 Title: Can't turn on Bluetooth after turning it off Status in bluez package in Ubuntu: New Bug description: Hey there! I am encountering a bug in Bluetooth menu in drop down menu at top right corner. Whenever i turn off my Bluetooth there is no option to turn on there. It shows two option turn off and Bluetooth setting. After I open setting and try to turn it on from there it doesn't turn on. I need to restart the system to make it work. Please fix this issue. Thank You Vipin Singh Negi ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 1 22:50:43 2020 InstallationDate: Installed on 2020-05-31 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Hewlett-Packard HP Pavilion g4 Notebook PC ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=8fbb62c5-9c67-4904-a243-2c34253fd16a ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/13/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.6A dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3564 dmi.board.vendor: Hewlett-Packard dmi.board.version: 21.46 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.6A:bd05/13/2013:svnHewlett-Packard:pnHPPaviliong4NotebookPC:pvr06911320461610100:rvnHewlett-Packard:rn3564:rvr21.46:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP Pavilion g4 Notebook PC dmi.product.sku: D7Z60PC#ACJ dmi.product.version: 06911320461610100 dmi.sys.vendor: Hewlett-Packard hciconfig: hci0:Type: Primary Bus: USB BD Address: 48:D2:24:58:55:67 ACL MTU: 1022:8 SCO MTU: 183:5 DOWN RX bytes:1957 acl:0 sco:0 events:90 errors:0 TX bytes:4974 acl:0 sco:0 commands:75 errors:0 To manage notifications about this bug go to:
[Kernel-packages] [Bug 1881623] [NEW] USB support missing in initrd makes booting core with writable on USB impossible
Public bug reported: when using a gadget.yaml like: volumes: pi4-system-boot: schema: mbr bootloader: u-boot structure: - type: 0C filesystem: vfat filesystem-label: system-boot size: 512M content: - source: boot-assets/ target: / pi4-usb-writable: schema: mbr structure: - name: writable type: 83 filesystem: ext4 filesystem-label: writable size: 650M role: system-data this creates two separate img files for a Pi image ... one for SD to hold the boot files, one for USB that carries the rootfs ... sadly our kernel will then not find the writable partition because it lacks support for usb disks (usb-storage seems to be there but not sufficient) adding the following to a re-built kernel snap makes everything work (verified with USB 3.1 SSD on a pi4 as well as various USB 3.0 keys) - CONFIG_ENCLOSURE_SERVICES=y - CONFIG_SCSI_SAS_ATTRS=y - CONFIG_USB_STORAGE=y - CONFIG_USB_UAS=y can we please have these either built into the kernel or added to the initrd as modules ? ** Affects: linux-raspi2 (Ubuntu) Importance: Undecided Status: Confirmed ** Description changed: when using a gadget.yaml like: volumes: - pi4-system-boot: - schema: mbr - bootloader: u-boot - structure: - - type: 0C - filesystem: vfat - filesystem-label: system-boot - size: 512M - content: - - source: boot-assets/ - target: / - pi4-usb-writable: - schema: mbr - structure: - - name: writable - type: 83 - filesystem: ext4 - filesystem-label: writable - size: 650M - role: system-data + pi4-system-boot: + schema: mbr + bootloader: u-boot + structure: + - type: 0C + filesystem: vfat + filesystem-label: system-boot + size: 512M + content: + - source: boot-assets/ + target: / + pi4-usb-writable: + schema: mbr + structure: + - name: writable + type: 83 + filesystem: ext4 + filesystem-label: writable + size: 650M + role: system-data - - this creates two separate img files for a Pi image ... one for SD to hold the boot files, one for USB that carries the rootfs ... + this creates two separate img files for a Pi image ... one for SD to + hold the boot files, one for USB that carries the rootfs ... sadly our kernel will then not find the writable partition because it lacks support for usb disks (usb-storage seems to be there but not sufficient) adding the following to a re-built kernel makes everything work (verified with USB 3.1 SSD on a pi4 as well as various USB 3.0 keys) - - CONFIG_ENCLOSURE_SERVICES=y - - CONFIG_SCSI_SAS_ATTRS=y - - CONFIG_USB_STORAGE=y - - CONFIG_USB_UAS=y + - CONFIG_ENCLOSURE_SERVICES=y + - CONFIG_SCSI_SAS_ATTRS=y + - CONFIG_USB_STORAGE=y + - CONFIG_USB_UAS=y - can we please have these aither built into the kernel or added to the + can we please have these either built into the kernel or added to the initrd as modules ? ** Summary changed: - USB support missing in initrd makes booting with writable on USB impossible + USB support missing in initrd makes booting core with writable on USB impossible -- 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/1881623 Title: USB support missing in initrd makes booting core with writable on USB impossible Status in linux-raspi2 package in Ubuntu: Confirmed Bug description: when using a gadget.yaml like: volumes: pi4-system-boot: schema: mbr bootloader: u-boot structure: - type: 0C filesystem: vfat filesystem-label: system-boot size: 512M content: - source: boot-assets/ target: / pi4-usb-writable: schema: mbr structure: - name: writable type: 83 filesystem: ext4 filesystem-label: writable size: 650M role: system-data this creates two separate img files for a Pi image ... one for SD to hold the boot files, one for USB that carries the rootfs ... sadly our kernel will then not find the writable partition because it lacks support for usb disks (usb-storage seems to be there but not sufficient) adding the following to a re-built kernel snap makes everything work (verified with USB 3.1 SSD on a pi4 as well as various USB 3.0 keys) - CONFIG_ENCLOSURE_SERVICES=y - CONFIG_SCSI_SAS_ATTRS=y - CONFIG_USB_STORAGE=y - CONFIG_USB_UAS=y can we please have these either built into the kernel or added to the initrd as modules ? To manage notifications
[Kernel-packages] [Bug 1881623] Re: USB support missing in initrd makes booting core with writable on USB impossible
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-raspi2 (Ubuntu) Status: New => Confirmed -- 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/1881623 Title: USB support missing in initrd makes booting core with writable on USB impossible Status in linux-raspi2 package in Ubuntu: Confirmed Bug description: when using a gadget.yaml like: volumes: pi4-system-boot: schema: mbr bootloader: u-boot structure: - type: 0C filesystem: vfat filesystem-label: system-boot size: 512M content: - source: boot-assets/ target: / pi4-usb-writable: schema: mbr structure: - name: writable type: 83 filesystem: ext4 filesystem-label: writable size: 650M role: system-data this creates two separate img files for a Pi image ... one for SD to hold the boot files, one for USB that carries the rootfs ... sadly our kernel will then not find the writable partition because it lacks support for usb disks (usb-storage seems to be there but not sufficient) adding the following to a re-built kernel snap makes everything work (verified with USB 3.1 SSD on a pi4 as well as various USB 3.0 keys) - CONFIG_ENCLOSURE_SERVICES=y - CONFIG_SCSI_SAS_ATTRS=y - CONFIG_USB_STORAGE=y - CONFIG_USB_UAS=y can we please have these either built into the kernel or added to the initrd as modules ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1881623/+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 1881549] Re: Upgraded to 20.04 and wifi broke
** Attachment removed: "/Var/log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881549/+attachment/5379236/+files/syslog -- 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/1881549 Title: Upgraded to 20.04 and wifi broke Status in linux package in Ubuntu: Confirmed Bug description: Upgraded to 20.04 and the wifi broke. It was working fine on 18.04. Tried a variety of things with apw but nada. /var/log attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881549/+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 1850439] Re: No sound on ASUS UX534FT
These seem to be bare minimum of commands to get audio working on my Asus Zenbook UX533FTC: hda-verb /dev/snd/hwC0D0 0x20 0x500 0xf hda-verb /dev/snd/hwC0D0 0x20 0x477 0x74 For anyone wondering where to get "hda-verb" utility - install "alsa- tools". -- 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/1850439 Title: No sound on ASUS UX534FT Status in linux package in Ubuntu: Confirmed Bug description: Hi, after instal Ubuntu in dual boot alongside Windows 10, I've realised there is no sound coming out of mine new ASUS Zenbook 15 UX534FT- AA024R in Ubuntu. In Windows there is no problem. Found this topic https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810214 which had the same problem with driver for Realtek ALC294 which is also mine sound card. But even with this fix it is not working on UX534FT. Can you please add fix also for this newer model? Description: Ubuntu 18.04.3 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.0.0-32-generic 5.0.0-32.34~18.04.2 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 29 15:11:25 2019 InstallationDate: Installed on 2019-10-29 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439/+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 1648143] Re: tor in lxd: apparmor="DENIED" operation="change_onexec" namespace="root//CONTAINERNAME_" profile="unconfined" name="system_tor"
** Changed in: apparmor (Ubuntu) Status: Confirmed => Invalid ** No longer affects: apparmor (Ubuntu Xenial) ** No longer affects: apparmor (Ubuntu Yakkety) -- 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/1648143 Title: tor in lxd: apparmor="DENIED" operation="change_onexec" namespace="root//CONTAINERNAME_" profile="unconfined" name="system_tor" Status in apparmor package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Released Status in tor package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Released Status in tor source package in Xenial: Invalid Status in linux source package in Yakkety: Fix Released Status in tor source package in Yakkety: Invalid Bug description: Environment: Distribution: ubuntu Distribution version: 16.10 lxc info: apiextensions: storage_zfs_remove_snapshots container_host_shutdown_timeout container_syscall_filtering auth_pki container_last_used_at etag patch usb_devices https_allowed_credentials image_compression_algorithm directory_manipulation container_cpu_time storage_zfs_use_refquota storage_lvm_mount_options network profile_usedby container_push apistatus: stable apiversion: "1.0" auth: trusted environment: addresses: 163.172.48.149:8443 172.20.10.1:8443 172.20.11.1:8443 172.20.12.1:8443 172.20.22.1:8443 172.20.21.1:8443 10.8.0.1:8443 architectures: x86_64 i686 certificate: | -BEGIN CERTIFICATE- -END CERTIFICATE- certificatefingerprint: 3048baa9f20d316f60a6c602452b58409a6d9e2c3218897e8de7c7c72af0179b driver: lxc driverversion: 2.0.5 kernel: Linux kernelarchitecture: x86_64 kernelversion: 4.8.0-27-generic server: lxd serverpid: 32694 serverversion: 2.4.1 storage: btrfs storageversion: 4.7.3 config: core.https_address: '[::]:8443' core.trust_password: true Container: ubuntu 16.10 Issue description -- tor can't start in a non privileged container Logs from the container: - Dec 7 15:03:00 anonymous tor[302]: Configuration was valid Dec 7 15:03:00 anonymous systemd[303]: tor@default.service: Failed at step APPARMOR spawning /usr/bin/tor: No such file or directory Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Main process exited, code=exited, status=231/APPARMOR Dec 7 15:03:00 anonymous systemd[1]: Failed to start Anonymizing overlay network for TCP. Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Unit entered failed state. Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Failed with result 'exit-code'. Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Service hold-off time over, scheduling restart. Dec 7 15:03:00 anonymous systemd[1]: Stopped Anonymizing overlay network for TCP. Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Failed to reset devices.list: Operation not permitted Dec 7 15:03:00 anonymous systemd[1]: Failed to set devices.allow on /system.slice/system-tor.slice/tor@default.service: Operation not permitted Dec 7 15:03:00 anonymous systemd[1]: message repeated 6 times: [ Failed to set devices.allow on /system.slice/system-tor.slice/tor@default.service: Operation not permitted] Dec 7 15:03:00 anonymous systemd[1]: Couldn't stat device /run/systemd/inaccessible/chr Dec 7 15:03:00 anonymous systemd[1]: Couldn't stat device /run/systemd/inaccessible/blk Dec 7 15:03:00 anonymous systemd[1]: Failed to set devices.allow on /system.slice/system-tor.slice/tor@default.service: Operation not permitted Logs from the host audit: type=1400 audit(1481119378.856:6950): apparmor="DENIED" operation="change_onexec" info="label not found" error=-2 namespace="root//lxd-anonymous_" profile="unconfined" name="system_tor" pid=12164 comm="(tor)" Steps to reproduce - install ubuntu container 16.10 on a ubuntu 16.10 host install tor in the container Launch tor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1648143/+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 1881623] Re: USB support missing in initrd makes booting core with writable on USB impossible
** Also affects: linux-raspi (Ubuntu) Importance: Undecided Status: New -- 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/1881623 Title: USB support missing in initrd makes booting core with writable on USB impossible Status in linux-raspi package in Ubuntu: New Status in linux-raspi2 package in Ubuntu: Confirmed Bug description: when using a gadget.yaml like: volumes: pi4-system-boot: schema: mbr bootloader: u-boot structure: - type: 0C filesystem: vfat filesystem-label: system-boot size: 512M content: - source: boot-assets/ target: / pi4-usb-writable: schema: mbr structure: - name: writable type: 83 filesystem: ext4 filesystem-label: writable size: 650M role: system-data this creates two separate img files for a Pi image ... one for SD to hold the boot files, one for USB that carries the rootfs ... sadly our kernel will then not find the writable partition because it lacks support for usb disks (usb-storage seems to be there but not sufficient) adding the following to a re-built kernel snap makes everything work (verified with USB 3.1 SSD on a pi4 as well as various USB 3.0 keys) - CONFIG_ENCLOSURE_SERVICES=y - CONFIG_SCSI_SAS_ATTRS=y - CONFIG_USB_STORAGE=y - CONFIG_USB_UAS=y can we please have these either built into the kernel or added to the core initrd as modules ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1881623/+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 1873325] Re: update-initramfs complains of missing amdgpu firmware files
can confirm its effecting my 20.04 install as well -- 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/1873325 Title: update-initramfs complains of missing amdgpu firmware files Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Fix Committed Bug description: SRU Justification Impact: amdgpu references firmware files in modinfo which have not been supplied to linux-firmware. This causes update-initramfs to generate "Possible missing firmware" warnings. Fix: Since the firmware is not available, all we can do is remove the files from modinfo. Test Case: Confirm that update-initramfs no longer produces the warnings. Regression Potential: Low. If someone had managed to obtain these files they will no longer be added to the initramfs, potentially causing regressions for these users. This would be an atypical situation. --- Ubuntu 20.04 during initramfs update reports missing firmware files: W: Possible missing firmware /lib/firmware/amdgpu/navi12_vcn.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/arcturus_vcn.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi12_smc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/arcturus_smc.bin for module amdgpu Kernel: 5.4.0-24-generic linux-firmware: 1.187 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873325/+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 1881623] Re: USB support missing in initrd makes booting core with writable on USB impossible
** Description changed: when using a gadget.yaml like: volumes: pi4-system-boot: schema: mbr bootloader: u-boot structure: - type: 0C filesystem: vfat filesystem-label: system-boot size: 512M content: - source: boot-assets/ target: / pi4-usb-writable: schema: mbr structure: - name: writable type: 83 filesystem: ext4 filesystem-label: writable size: 650M role: system-data this creates two separate img files for a Pi image ... one for SD to hold the boot files, one for USB that carries the rootfs ... sadly our kernel will then not find the writable partition because it lacks support for usb disks (usb-storage seems to be there but not sufficient) - adding the following to a re-built kernel makes everything work + adding the following to a re-built kernel snap makes everything work (verified with USB 3.1 SSD on a pi4 as well as various USB 3.0 keys) - CONFIG_ENCLOSURE_SERVICES=y - CONFIG_SCSI_SAS_ATTRS=y - CONFIG_USB_STORAGE=y - CONFIG_USB_UAS=y can we please have these either built into the kernel or added to the initrd as modules ? -- 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/1881623 Title: USB support missing in initrd makes booting core with writable on USB impossible Status in linux-raspi2 package in Ubuntu: Confirmed Bug description: when using a gadget.yaml like: volumes: pi4-system-boot: schema: mbr bootloader: u-boot structure: - type: 0C filesystem: vfat filesystem-label: system-boot size: 512M content: - source: boot-assets/ target: / pi4-usb-writable: schema: mbr structure: - name: writable type: 83 filesystem: ext4 filesystem-label: writable size: 650M role: system-data this creates two separate img files for a Pi image ... one for SD to hold the boot files, one for USB that carries the rootfs ... sadly our kernel will then not find the writable partition because it lacks support for usb disks (usb-storage seems to be there but not sufficient) adding the following to a re-built kernel snap makes everything work (verified with USB 3.1 SSD on a pi4 as well as various USB 3.0 keys) - CONFIG_ENCLOSURE_SERVICES=y - CONFIG_SCSI_SAS_ATTRS=y - CONFIG_USB_STORAGE=y - CONFIG_USB_UAS=y can we please have these either built into the kernel or added to the core initrd as modules ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1881623/+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 1881137] Re: Introduce the new NVIDIA 418-server and 440-server series, and update the current NVIDIA drivers
** Also affects: ubuntu-drivers-common (Ubuntu) Importance: Undecided Status: New ** No longer affects: ubuntu-drivers-common (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/1881137 Title: Introduce the new NVIDIA 418-server and 440-server series, and update the current NVIDIA drivers Status in linux package in Ubuntu: Incomplete Status in linux-restricted-modules package in Ubuntu: New Status in nvidia-graphics-drivers-418-server package in Ubuntu: Invalid Status in nvidia-graphics-drivers-440 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-440-server package in Ubuntu: New Status in linux source package in Bionic: In Progress Status in linux-restricted-modules source package in Bionic: In Progress Status in nvidia-graphics-drivers-418-server source package in Bionic: In Progress Status in nvidia-graphics-drivers-440 source package in Bionic: In Progress Status in nvidia-graphics-drivers-440-server source package in Bionic: In Progress Status in ubuntu-drivers-common source package in Bionic: New Status in linux source package in Focal: In Progress Status in linux-restricted-modules source package in Focal: In Progress Status in nvidia-graphics-drivers-418-server source package in Focal: In Progress Status in nvidia-graphics-drivers-440 source package in Focal: In Progress Status in nvidia-graphics-drivers-440-server source package in Focal: In Progress Status in ubuntu-drivers-common source package in Focal: New Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] 440.82: * New upstream release: - Added a workaround for Steam Play title DOOM Eternal, which overrides application requested memory locations, to ensure performance-critical resources be placed in video memory. - Allow presenting from queue families which only expose VK_QUEUE_COMPUTE_BIT when using XCB in addition to Xlib surfaces. - Fixed a bug that caused render-offloaded applications to crash on exit. - Fixed a driver installation failure on Linux kernel 5.6 release candidates, where the NVIDIA kernel module failed to build with error "implicit declaration of function 'timespec_to_ns'". - Fixed a driver installation failure on Linux kernel 5.6 release candidates, where the NVIDIA kernel module failed to build with error "implicit declaration of function 'getrawmonotonic'". - Fixed a driver installation failure on Linux kernel 5.6 release candidates, where the NVIDIA kernel module failed to build with error "implicit declaration of function 'timespec_to_ns'". - Fixed a driver installation failure on Linux kernel 5.6 release candidates, where the NVIDIA kernel module failed to build with error "implicit declaration of function 'getrawmonotonic'". - Fixed a driver installation failure on Linux kernel 5.6 release candidates, where the NVIDIA kernel module failed to build with error "implicit declaration of function 'getnstimeofday'". - Fixed a driver installation failure on Linux kernel 5.6 release candidates, where the NVIDIA kernel module failed to build with error "dereferencing pointer to incomplete type 'struct timeval'". - Fixed a driver installation failure on Linux kernel 5.6 release candidates, where the NVIDIA kernel module failed to build with error "implicit declaration of function 'jiffies_to_timespec'". - Fixed driver installation failure on Linux kernel 5.6 release candidates, where the NVIDIA kernel module failed to build with error "passing argument 4 of 'proc_create_data' from incompatible pointer type". 440.64.00: * Initial release. 418.126.02 * Initial release. nvidia-settings (440.82): * New upstream release (LP: #1881137). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881137/+subscriptions --
[Kernel-packages] [Bug 1210748] Re: On Lenovo Thinkpad Twist internal mouse does not work after turning on machine, only works after reboot
I encountered the same issue and was able to solve it by adding i8042.reset=1 to the kernel command line. i8042.nomux was not necessary for me. The quirk was committed in https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2712c91a54a1058d55c284152b4d93c979b67be6 which is included in Linux 5.7. It has also been merged into stable for the upcoming v5.6.16, v5.4.44, v4.19.126, v4.14.183, v4.9.226, and v4.4.226. -- 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/1210748 Title: On Lenovo Thinkpad Twist internal mouse does not work after turning on machine, only works after reboot Status in linux package in Ubuntu: Invalid Bug description: I have a Lenovo ThinkPad Twist (convertible ultrabook with Core i7 processor) with touch screen, touch pad, rubber nipple mouse, and external Bluetooth mouse. From these 4 mice 2 always work, the touch screen and the external Bluetooth mouse. The touchpad and the nipple do not work right after turning on the machine, only when I reboot the machine they work after rebooting. I have observed the problem only recently, so it is perhaps triggered by the BIOS upgrade to version 1.57. The problem is independent of the Ubuntu version. I did not only observe it on the installed Raring and Saucy systems but also with several live CDs of older Ubuntu versions (Quantal, Precise). There is also another user with the same problem. See http://www.iasptk.com/ubuntuwp/tag/13-10/ and search for "twist". Unfortunately, the question got removed from Ask Ubuntu, but one can still access the dmesg output from this user on http://paste.ubuntu.com/5889489/ --- ApportVersion: 2.12-0ubuntu3 Architecture: amd64 DistroRelease: Ubuntu 13.10 InstallationDate: Installed on 2013-06-05 (65 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130605) MarkForUpload: True Package: linux (not installed) Tags: saucy Uname: Linux 3.11.0-031100rc3-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo --- ApportVersion: 2.12-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: till 2756 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=e0af6e5c-3cf3-47e2-8603-6a9ffb019484 InstallationDate: Installed on 2013-06-05 (65 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130605) MachineType: LENOVO 334729G MarkForUpload: True Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.10.0-6-generic root=UUID=71da60b2-cc11-47bf-9120-bfad5b1c7eaa ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3 RelatedPackageVersions: linux-restricted-modules-3.10.0-6-generic N/A linux-backports-modules-3.10.0-6-generic N/A linux-firmware1.113 Tags: saucy Uname: Linux 3.10.0-6-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 07/01/2013 dmi.bios.vendor: LENOVO dmi.bios.version: GDET97WW (1.57 ) dmi.board.asset.tag: Not Available dmi.board.name: 334729G dmi.board.vendor: LENOVO dmi.board.version: Win8 Pro DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGDET97WW(1.57):bd07/01/2013:svnLENOVO:pn334729G:pvrThinkPadTwist:rvnLENOVO:rn334729G:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 334729G dmi.product.version: ThinkPad Twist dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1210748/+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 1874862] Re: [WinBook TW102] Touch inputs not detected
I apologize for the slow reply, a lot of stuff has been going on, and I hit a snag. The device in question no longer boots reliably. I have not been able to confirm, but I believe that the internal wifi chip is failing, and when the device loads the wifi driver in the boot process it crashes. If I cannot aid in troubleshooting, should we close this bug report or leave it open in the hopes someone else with this tablet will come along? -- 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/1874862 Title: [WinBook TW102] Touch inputs not detected Status in linux package in Ubuntu: Confirmed Bug description: touch inputs are not detected by Ubuntu on this tablet. I'm not sure the touch screen hardware is detected at all by Ubuntu. I tried cat /dev/input/eventX (replacing X with every option listed) and not once got any reaction to touching the screen. I can provide more information and troubleshooting if asked, I just need to know what to look for. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 Uname: Linux 5.5.0-050500-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 24 13:27:45 2020 DistUpgraded: 2020-01-26 15:24:00,462 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b0] (rev 36) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:7270] InstallationDate: Installed on 2020-01-22 (92 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 0603:0002 Novatek Microelectronics Corp. Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/7p, 480M |__ Port 4: Dev 4, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 2: Dev 5, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 2: Dev 5, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M MachineType: MicroElectronics TW102 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.5.0-050500-generic root=UUID=20dd837f-ba9a-469c-bba4-45bb6e2370db ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-01-26 (88 days ago) dmi.bios.date: 03/22/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 8.17 dmi.board.asset.tag: Default string dmi.board.name: H8811C dmi.board.vendor: EMDOOR dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 17 dmi.chassis.vendor: EMDOOR dmi.chassis.version: 1 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr8.17:bd03/22/2018:svnMicroElectronics:pnTW102:pvr1:rvnEMDOOR:rnH8811C:rvr1.0:cvnEMDOOR:ct17:cvr1: dmi.product.family: WinBook dmi.product.name: TW102 dmi.product.sku: 585497 dmi.product.version: 1 dmi.sys.vendor: MicroElectronics 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 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 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/1874862/+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 1881549] Re: Upgraded to 20.04 and wifi broke
** Attachment added: "updated /var/log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881549/+attachment/5379257/+files/syslog -- 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/1881549 Title: Upgraded to 20.04 and wifi broke Status in linux package in Ubuntu: Confirmed Bug description: Upgraded to 20.04 and the wifi broke. It was working fine on 18.04. Tried a variety of things with apw but nada. /var/log attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881549/+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 1881600] [NEW] Touch Pad not detected on Acer A315-31 Laptop
Public bug reported: I was trying out Ubuntu 20.04 Desktop From a USB Stick on my new Acer A315-31 model laptop. Touch Pad is not recognized by Ubuntu. Tried - cat /proc/bus/input/devices and I don't see any Touchpad devices listed. How do I fix this? Thank You. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-26-generic 5.4.0-26.30 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 4515 F pulseaudio CRDA: global country IN: DFS-UNSET (2402 - 2482 @ 40), (N/A, 20), (N/A) (5150 - 5350 @ 160), (N/A, 23), (N/A) (5725 - 5875 @ 80), (N/A, 23), (N/A) CasperMD5CheckResult: skip CasperVersion: 1.445 CurrentDesktop: ubuntu:GNOME Date: Mon Jun 1 13:33:38 2020 LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ACER A315-31 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/26/2018 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.27 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Ivysaur_AP dmi.board.vendor: APL dmi.board.version: V1.27 dmi.chassis.type: 10 dmi.chassis.vendor: ACER dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.27:bd09/26/2018:svnACER:pnA315-31:pvrV1.27:rvnAPL:rnIvysaur_AP:rvrV1.27:cvnACER:ct10:cvrChassisVersion: dmi.product.name: A315-31 dmi.product.sku: dmi.product.version: V1.27 dmi.sys.vendor: ACER ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "devices" https://bugs.launchpad.net/bugs/1881600/+attachment/5379276/+files/devices -- 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/1881600 Title: Touch Pad not detected on Acer A315-31 Laptop Status in linux package in Ubuntu: New Bug description: I was trying out Ubuntu 20.04 Desktop From a USB Stick on my new Acer A315-31 model laptop. Touch Pad is not recognized by Ubuntu. Tried - cat /proc/bus/input/devices and I don't see any Touchpad devices listed. How do I fix this? Thank You. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-26-generic 5.4.0-26.30 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 4515 F pulseaudio CRDA: global country IN: DFS-UNSET (2402 - 2482 @ 40), (N/A, 20), (N/A) (5150 - 5350 @ 160), (N/A, 23), (N/A) (5725 - 5875 @ 80), (N/A, 23), (N/A) CasperMD5CheckResult: skip CasperVersion: 1.445 CurrentDesktop: ubuntu:GNOME Date: Mon Jun 1 13:33:38 2020 LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ACER A315-31 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/26/2018 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.27 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Ivysaur_AP dmi.board.vendor: APL dmi.board.version: V1.27 dmi.chassis.type: 10 dmi.chassis.vendor: ACER dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.27:bd09/26/2018:svnACER:pnA315-31:pvrV1.27:rvnAPL:rnIvysaur_AP:rvrV1.27:cvnACER:ct10:cvrChassisVersion: dmi.product.name: A315-31 dmi.product.sku: dmi.product.version: V1.27 dmi.sys.vendor: ACER To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881600/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net
[Kernel-packages] [Bug 1881600] Status changed to Confirmed
This change was made by a bot. ** Changed in: 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/1881600 Title: Touch Pad not detected on Acer A315-31 Laptop Status in linux package in Ubuntu: Confirmed Bug description: I was trying out Ubuntu 20.04 Desktop From a USB Stick on my new Acer A315-31 model laptop. Touch Pad is not recognized by Ubuntu. Tried - cat /proc/bus/input/devices and I don't see any Touchpad devices listed. How do I fix this? Thank You. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-26-generic 5.4.0-26.30 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 4515 F pulseaudio CRDA: global country IN: DFS-UNSET (2402 - 2482 @ 40), (N/A, 20), (N/A) (5150 - 5350 @ 160), (N/A, 23), (N/A) (5725 - 5875 @ 80), (N/A, 23), (N/A) CasperMD5CheckResult: skip CasperVersion: 1.445 CurrentDesktop: ubuntu:GNOME Date: Mon Jun 1 13:33:38 2020 LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ACER A315-31 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/26/2018 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.27 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Ivysaur_AP dmi.board.vendor: APL dmi.board.version: V1.27 dmi.chassis.type: 10 dmi.chassis.vendor: ACER dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.27:bd09/26/2018:svnACER:pnA315-31:pvrV1.27:rvnAPL:rnIvysaur_AP:rvrV1.27:cvnACER:ct10:cvrChassisVersion: dmi.product.name: A315-31 dmi.product.sku: dmi.product.version: V1.27 dmi.sys.vendor: ACER To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881600/+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 1848771] Re: Reboot after resume from suspend (deep)
Add me to the list of those having this issue, but also have a partial fix. I am running a Thinkpad P50 with Nvidia display adapter. 18.04 was great, never any issues with suspend or resume. I upgraded to 20.04 a couple of weeks ago and immediately began encountering the reboot on resume issue. Suspend worked fine, the LED on the cover dimmed and brightened to indicate it was asleep, external displays went into power save, etc. But when trying to resume it rebooted from scratch every time. I found this article https://itsfoss.com/ubuntu-close-lid-suspend/ and followed the steps in it. To my surprise, pm-utils was not installed, so I installed it. I also made the suggested edits to /etc/systemd/logind.conf plus a few more, my edited file is below. After these steps, I can now resume from suspend successfully. My laptop display remains dark but the external monitors come on and show the desktop. If I logout and back in then all is fine and all displays work. Here is my edited config file: [Login] #NAutoVTs=6 #ReserveVT=6 #KillUserProcesses=no #KillOnlyUsers= #KillExcludeUsers=root #InhibitDelayMaxSec=5 HandlePowerKey=suspend HandleSuspendKey=suspend #HandleHibernateKey=hibernate HandleLidSwitch=suspend HandleLidSwitchExternalPower=suspend HandleLidSwitchDocked=suspend PowerKeyIgnoreInhibited=no SuspendKeyIgnoreInhibited=no #HibernateKeyIgnoreInhibited=no LidSwitchIgnoreInhibited=no #HoldoffTimeoutSec=30s #IdleAction=ignore #IdleActionSec=30min #RuntimeDirectorySize=10% #RemoveIPC=yes #InhibitorsMax=8192 #SessionsMax=819 -- 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/1848771 Title: Reboot after resume from suspend (deep) Status in linux package in Ubuntu: Incomplete Status in ubuntu-release-upgrader package in Ubuntu: Invalid Bug description: After upgrading to Kubuntu Eoan (19.10) yesterday, my laptop crashes after resume from suspending. This is regardless the way of suspending (closing lid, selecting suspend from sddm, systemctl suspend). The journal shows: ferry@chromium:~$ journalctl -b -1 -e .. sddm[1106]: Message received from greeter: Suspend NetworkManager[836]: manager: sleep: sleep requested (sleeping: no enabled: yes) NetworkManager[836]: device (60:73:BC:BA:B8:68): state change: disconnected -> unmanaged (reason ' NetworkManager[836]: device (60:73:BC:23:8F:3E): state change: disconnected -> unmanaged (reason ' NetworkManager[836]: device (p2p-dev-wlp1s0): state change: disconnected -> unmanaged (reason 'sle NetworkManager[836]: manager: NetworkManager state is now ASLEEP systemd[1]: Reached target Sleep. systemd[1]: Starting Suspend... systemd-sleep[1238]: Suspending system... kernel: PM: suspend entry (deep) On resume (keypress, open lid) resume starts but immediately crashes and reboots. The laptop is an Acer 720p Chromebook with Chromium replaced and working fine with Kubuntu since 5 years or so. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-release-upgrader-core 1:19.10.15 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: KDE Date: Fri Oct 18 18:45:53 2019 InstallationDate: Installed on 2017-07-13 (826 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to eoan on 2019-10-17 (0 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848771/+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 1881576] [NEW] seccomp_benchmark times out on eoan
Public bug reported: As it tries to calibrate how many samples will take more than 5 seconds to execute, it may end up picking up a number of samples that take 10 (but up to 12) seconds. As the calibration will take double that time, it takes around 20 seconds. Then, it executes the whole thing again, and then once more, with some added overhead. So, the thing might take more than 40 seconds, which is too close to the 45s timeout. So, it times out once in a while depending on the system. Using a timeout of 90 seconds should be safe enough for this test. ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: linux (Ubuntu Eoan) Importance: Undecided Assignee: Thadeu Lima de Souza Cascardo (cascardo) Status: In Progress ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Fix Released ** Changed in: linux (Ubuntu Eoan) Status: New => In Progress ** Changed in: linux (Ubuntu Eoan) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) -- 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/1881576 Title: seccomp_benchmark times out on eoan Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Eoan: In Progress Bug description: As it tries to calibrate how many samples will take more than 5 seconds to execute, it may end up picking up a number of samples that take 10 (but up to 12) seconds. As the calibration will take double that time, it takes around 20 seconds. Then, it executes the whole thing again, and then once more, with some added overhead. So, the thing might take more than 40 seconds, which is too close to the 45s timeout. So, it times out once in a while depending on the system. Using a timeout of 90 seconds should be safe enough for this test. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1881576/+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 1881576] Re: seccomp_benchmark times out on eoan
** Description changed: - As it tries to calibrate how many samples will take more than 5 seconds - to execute, it may end up picking up a number of samples that take 10 - (but up to 12) seconds. As the calibration will take double that time, - it takes around 20 seconds. Then, it executes the whole thing again, and - then once more, with some added overhead. So, the thing might take more - than 40 seconds, which is too close to the 45s timeout. + [Impact] + seccomp selftests will timeout, causing the test to be detected as failure. + + [Fix] + Set timeout to 90s. + + [Test case] + Run sudo make run_tests under tools/testing/selftests/seccomp/. + + [Regression potential] + Minimal, the test could still timeout, but by reading the code, it should take around 42s to 50s to execute in the worst cases, so 90s seem safe enough. + + == + + + As it tries to calibrate how many samples will take more than 5 seconds to execute, it may end up picking up a number of samples that take 10 (but up to 12) seconds. As the calibration will take double that time, it takes around 20 seconds. Then, it executes the whole thing again, and then once more, with some added overhead. So, the thing might take more than 40 seconds, which is too close to the 45s timeout. So, it times out once in a while depending on the system. Using a timeout of 90 seconds should be safe enough for this test. -- 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/1881576 Title: seccomp_benchmark times out on eoan Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Eoan: In Progress Bug description: [Impact] seccomp selftests will timeout, causing the test to be detected as failure. [Fix] Set timeout to 90s. [Test case] Run sudo make run_tests under tools/testing/selftests/seccomp/. [Regression potential] Minimal, the test could still timeout, but by reading the code, it should take around 42s to 50s to execute in the worst cases, so 90s seem safe enough. == As it tries to calibrate how many samples will take more than 5 seconds to execute, it may end up picking up a number of samples that take 10 (but up to 12) seconds. As the calibration will take double that time, it takes around 20 seconds. Then, it executes the whole thing again, and then once more, with some added overhead. So, the thing might take more than 40 seconds, which is too close to the 45s timeout. So, it times out once in a while depending on the system. Using a timeout of 90 seconds should be safe enough for this test. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1881576/+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 1881576] Re: seccomp_benchmark times out on eoan
** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu) Status: Fix Released => In Progress ** 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/1881576 Title: seccomp_benchmark times out on eoan Status in ubuntu-kernel-tests: Invalid Status in linux package in Ubuntu: In Progress Status in linux source package in Eoan: In Progress Status in linux source package in Focal: In Progress Bug description: [Impact] seccomp selftests will timeout, causing the test to be detected as failure. [Fix] Set timeout to 90s. [Test case] Run sudo make run_tests under tools/testing/selftests/seccomp/. [Regression potential] Minimal, the test could still timeout, but by reading the code, it should take around 42s to 50s to execute in the worst cases, so 90s seem safe enough. == As it tries to calibrate how many samples will take more than 5 seconds to execute, it may end up picking up a number of samples that take 10 (but up to 12) seconds. As the calibration will take double that time, it takes around 20 seconds. Then, it executes the whole thing again, and then once more, with some added overhead. So, the thing might take more than 40 seconds, which is too close to the 45s timeout. So, it times out once in a while depending on the system. Using a timeout of 90 seconds should be safe enough for this test. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1881576/+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 1881549] Re: Upgraded to 20.04 and wifi broke
** Attachment added: "updated /var/log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881549/+attachment/5379273/+files/syslog -- 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/1881549 Title: Upgraded to 20.04 and wifi broke Status in linux package in Ubuntu: Confirmed Bug description: Upgraded to 20.04 and the wifi broke. It was working fine on 18.04. Tried a variety of things with apw but nada. /var/log attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881549/+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 1881525] Re: in kernel amdgpu failed with W5500 [1002:7341]
** Description changed: + [SRU Justfication] + [Impact] + amdgpu is always failed on bionic 5.4 kernel. + + Since bionic's kernel will upgrade to 5.4 in the future, + but bionic's linux-firmware didn't support navi14. + So if a user update kernel to 5.4, + he/she still can't use the related navi14 devices. + + + # dmesg | grep amdgpu + [drm] amdgpu kernel modesetting enabled. + amdgpu remove_conflicting_pci_framebuffers: bar 0: 0x60 -> 0x600fff + amdgpu remove_conflicting_pci_framebuffers: bar 2: 0x601000 -> 0x60101f + amdgpu remove_conflicting_pci_framebuffers: bar 5: 0x7e80 -> 0x7e87 + fb0: switching to amdgpudrmfb from EFI VGA + amdgpu vgaarb: deactivate vga console + amdgpu enabling device (0106 -> 0107) + amdgpu Direct firmware load for amdgpu/navi14_gpu_info.bin failed with error -2 + amdgpu Failed to load gpu_info firmware "amdgpu/navi14_gpu_info.bin" + amdgpu Fatal error during GPU init + [Fix] + Patchset[1] for navi14's support currently landed in focal's linux-firmware, + so we backported them to bionic's linux-firmware. + + [1]: + aa95e90b2c638f1ca6647d12b2d1b18284428f9c + d4f88ea76e442e6652de1367050e33314594d533 + 40656437f476ef7c47972731671ddcc9e4c4225b + 7319341e6e40f8bae1f2623eb5e4ddc0e2b50076 + b5b176ac09b6d1211da1e5db8e0c31ac830e4b8c + + [Test] + The amdgpu can be recognized and initialized when booting. + + # dmesg | grep amdgpu + [drm] amdgpu kernel modesetting enabled. + amdgpu remove_conflicting_pci_framebuffers: bar 0: 0x60 -> 0x600fff + amdgpu remove_conflicting_pci_framebuffers: bar 2: 0x601000 -> 0x60101f + amdgpu remove_conflicting_pci_framebuffers: bar 5: 0x7e80 -> 0x7e87 + amdgpu enabling device (0106 -> 0107) + amdgpu VRAM: 8176M 0x0080 - 0x0081FEFF (8176M used) + amdgpu GART: 512M 0x - 0x1FFF + [drm] amdgpu: 8176M of VRAM memory ready + [drm] amdgpu: 8176M of GTT memory ready. + ... + [drm] Initialized amdgpu 3.35.0 20150101 for :03:00.0 on minor 1 + + + [Regression Potential] + Low, just adding new navi14 firmware, no change to existing firmware. + X-HWE-Bug: Bug #1880678 - --- + --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 Dependencies: - + DistributionChannelDescriptor: - # This is the distribution channel descriptor for the OEM CDs - # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor - canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-hotpie+X34 + # This is the distribution channel descriptor for the OEM CDs + # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor + canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-hotpie+X34 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-05-25 (6 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Package: linux-firmware 1.173.18+navi14 [origin: LP-PPA-shanelin-linux-firmware] PackageArchitecture: all ProcVersionSignature: Ubuntu 5.4.0-31.35~18.04.2-generic 5.4.34 Tags: bionic uec-images third-party-packages Uname: Linux 5.4.0-31-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True -- 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/1881525 Title: in kernel amdgpu failed with W5500 [1002:7341] Status in HWE Next: New Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Bionic: In Progress Bug description: [SRU Justfication] [Impact] amdgpu is always failed on bionic 5.4 kernel. Since bionic's kernel will upgrade to 5.4 in the future, but bionic's linux-firmware didn't support navi14. So if a user update kernel to 5.4, he/she still can't use the related navi14 devices. # dmesg | grep amdgpu [drm] amdgpu kernel modesetting enabled. amdgpu remove_conflicting_pci_framebuffers: bar 0: 0x60 -> 0x600fff amdgpu remove_conflicting_pci_framebuffers: bar 2: 0x601000 -> 0x60101f amdgpu remove_conflicting_pci_framebuffers: bar 5: 0x7e80 -> 0x7e87 fb0: switching to amdgpudrmfb from EFI VGA amdgpu vgaarb: deactivate vga console amdgpu enabling device (0106 -> 0107) amdgpu Direct firmware load for amdgpu/navi14_gpu_info.bin failed with error -2 amdgpu Failed to load gpu_info firmware "amdgpu/navi14_gpu_info.bin" amdgpu Fatal error during GPU init [Fix] Patchset[1] for navi14's support currently landed in focal's linux-firmware, so we backported them to bionic's linux-firmware. [1]: aa95e90b2c638f1ca6647d12b2d1b18284428f9c
[Kernel-packages] [Bug 1881601] Re: Fan excessively runs, even when idle
** Changed in: linux (Ubuntu) Status: New => In Progress ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Colin Ian King (colin-king) -- 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/1881601 Title: Fan excessively runs, even when idle Status in linux package in Ubuntu: In Progress Bug description: I have a skull canyon NUC as my daily driver and the fan is running much higher than it should, even when the machine is completely idle. This happened with the 5.3 kernel and also with the 5.4 kernel during focal development cycle. It was fixed somewhere along the way prior to release but it's back with a vengeance now. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dean 4523 F pulseaudio /dev/snd/controlC0: dean 4523 F pulseaudio /dev/snd/controlC1: dean 4523 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 1 08:37:23 2020 HibernationDevice: RESUME=UUID=55a42c82-50bf-4e75-a133-dbd3aa93611b InstallationDate: Installed on 2018-07-24 (677 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180724) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-01-07 (145 days ago) dmi.bios.date: 05/16/2018 dmi.bios.vendor: Intel Corp. dmi.bios.version: KYSKLi70.86A.0055.2018.0516.1629 dmi.board.name: NUC6i7KYB dmi.board.vendor: Intel Corporation dmi.board.version: H90766-406 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnIntelCorp.:bvrKYSKLi70.86A.0055.2018.0516.1629:bd05/16/2018:svn:pn:pvr:rvnIntelCorporation:rnNUC6i7KYB:rvrH90766-406:cvnIntelCorporation:ct3:cvr1.0: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881601/+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 1881601] [NEW] Fan excessively runs, even when idle
Public bug reported: I have a skull canyon NUC as my daily driver and the fan is running much higher than it should, even when the machine is completely idle. This happened with the 5.3 kernel and also with the 5.4 kernel during focal development cycle. It was fixed somewhere along the way prior to release but it's back with a vengeance now. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dean 4523 F pulseaudio /dev/snd/controlC0: dean 4523 F pulseaudio /dev/snd/controlC1: dean 4523 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 1 08:37:23 2020 HibernationDevice: RESUME=UUID=55a42c82-50bf-4e75-a133-dbd3aa93611b InstallationDate: Installed on 2018-07-24 (677 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180724) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-01-07 (145 days ago) dmi.bios.date: 05/16/2018 dmi.bios.vendor: Intel Corp. dmi.bios.version: KYSKLi70.86A.0055.2018.0516.1629 dmi.board.name: NUC6i7KYB dmi.board.vendor: Intel Corporation dmi.board.version: H90766-406 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnIntelCorp.:bvrKYSKLi70.86A.0055.2018.0516.1629:bd05/16/2018:svn:pn:pvr:rvnIntelCorporation:rnNUC6i7KYB:rvrH90766-406:cvnIntelCorporation:ct3:cvr1.0: ** Affects: linux (Ubuntu) Importance: High Assignee: Colin Ian King (colin-king) Status: In Progress ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881601 Title: Fan excessively runs, even when idle Status in linux package in Ubuntu: In Progress Bug description: I have a skull canyon NUC as my daily driver and the fan is running much higher than it should, even when the machine is completely idle. This happened with the 5.3 kernel and also with the 5.4 kernel during focal development cycle. It was fixed somewhere along the way prior to release but it's back with a vengeance now. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dean 4523 F pulseaudio /dev/snd/controlC0: dean 4523 F pulseaudio /dev/snd/controlC1: dean 4523 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 1 08:37:23 2020 HibernationDevice: RESUME=UUID=55a42c82-50bf-4e75-a133-dbd3aa93611b InstallationDate: Installed on 2018-07-24 (677 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180724) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-01-07 (145 days ago) dmi.bios.date: 05/16/2018 dmi.bios.vendor: Intel Corp. dmi.bios.version: KYSKLi70.86A.0055.2018.0516.1629 dmi.board.name: NUC6i7KYB dmi.board.vendor: Intel Corporation dmi.board.version: H90766-406 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnIntelCorp.:bvrKYSKLi70.86A.0055.2018.0516.1629:bd05/16/2018:svn:pn:pvr:rvnIntelCorporation:rnNUC6i7KYB:rvrH90766-406:cvnIntelCorporation:ct3:cvr1.0: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881601/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages
[Kernel-packages] [Bug 1880049] Re: Using Lakka with Intel GVT-g freezes the host system
** 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/1880049 Title: Using Lakka with Intel GVT-g freezes the host system Status in linux package in Ubuntu: Confirmed Bug description: I tried to start Lakka (http://www.lakka.tv/) using QEMU with Intel GVT-g and, when the graphics should start loading, the system freezes. The command line used was: The command line I used to start QEMU was: sudo qemu-system-x86_64 -m 1024 -cpu Skylake-Client -vga none -accel kvm -device nec-usb-xhci -device usb-host,id=maxprint,vendorid=0x13fe -boot menu=on -serial vc -serial stdio -display gtk,gl=on -device vfio-pci,sysfsdev=/sys/bus/pci/devices/:00:02.0/20312cec-80f4 -448a-9f09-7b93adbf672c,x-igd- opregion=on,display=on,addr=0x5,rombar=0,id=iHD520 -bios /usr/share/ovmf/OVMF.fd Relevant syslog messages with the BUG: May 21 21:50:35 Lenovo-ideapad-310-14ISK kernel: [ 7672.207424] vfio_mdev 20312cec-80f4-448a-9f09-7b93adbf672c: Adding to iommu group 0 May 21 21:50:35 Lenovo-ideapad-310-14ISK kernel: [ 7672.207427] vfio_mdev 20312cec-80f4-448a-9f09-7b93adbf672c: MDEV: group_id = 0 May 21 21:50:42 Lenovo-ideapad-310-14ISK dbus-daemon[21697]: [session uid=0 pid=21695] AppArmor D-Bus mediation is enabled May 21 21:51:06 Lenovo-ideapad-310-14ISK kernel: [ 7703.690519] usb 1-3: reset high-speed USB device number 10 using xhci_hcd May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.354929] BUG: kernel NULL pointer dereference, address: 0008 May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.354932] #PF: supervisor write access in kernel mode May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.354933] #PF: error_code(0x0002) - not-present page May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.354935] PGD 0 P4D 0 May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.354937] Oops: 0002 [#1] SMP PTI May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.354940] CPU: 2 PID: 254 Comm: gvt workload 0 Tainted: P C O 5.4.0-32-generic #36-Ubuntu May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.354941] Hardware name: LENOVO 80UG/Toronto 4A2, BIOS 0XCN45WW 08/09/2018 May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.354979] RIP: 0010:prepare_workload+0xf6/0x480 [i915] May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.354981] Code: 1a 00 00 48 8b 4f 40 48 8b 40 20 4c 8b 40 40 31 c0 83 7f 18 0c 49 8b 90 f0 02 00 00 74 24 48 63 f0 48 83 c0 01 48 8b 54 f2 20 <48> 89 4a 08 48 83 f8 04 74 12 49 8b 90 f0 02 00 00 48 8b 4c c7 40 May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.354983] RSP: 0018:b39a403fbdb0 EFLAGS: 00010202 May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.354984] RAX: 0001 RBX: 8c46bb376900 RCX: 0004565c8000 May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.354985] RDX: RSI: RDI: 8c47d4f9a840 May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.354987] RBP: b39a403fbde8 R08: 8c471382fc00 R09: e658e558 May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.354988] R10: e45ce758 R11: e65ce55c R12: f5a6d1436180 May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.354989] R13: R14: 8c46bb376900 R15: 8c47d8e88000 May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.354990] FS: () GS:8c47de30() knlGS: May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.354991] CS: 0010 DS: ES: CR0: 80050033 May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.354992] CR2: 0008 CR3: 0004565cc004 CR4: 003626e0 May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.354994] DR0: DR1: DR2: May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.354995] DR3: DR6: fffe0ff0 DR7: 0400 May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.354996] Call Trace: May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.355028] workload_thread+0x50d/0xde0 [i915] May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.355032] ? __switch_to_asm+0x40/0x70 May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.355036] ? do_wait_intr_irq+0xa0/0xa0 May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.355038] kthread+0x104/0x140 May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.355065] ? intel_vgpu_clean_workloads+0x100/0x100 [i915] May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.355067] ? kthread_park+0x90/0x90 May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.355070] ret_from_fork+0x35/0x40 May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [
[Kernel-packages] [Bug 1877890] Re: System Hangs when trying to kill a Window
Dear Sirs, Please feel free to close out this Bug. The Solution as mentioned above was to run with the 4.15.0 Nucleus. The problem was probably caused by the fact that my Computer System was 10+ years old and so it couldn't support the new HWE code in the 5.x Series. Thank you everyone who took the time to look at this problem. Yours truly, Frank Krauss -- 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/1877890 Title: System Hangs when trying to kill a Window Status in linux package in Ubuntu: Incomplete Bug description: Dear Sirs, I'm a long term user of Ubuntu, I run a Client/Server system that my clients expect to be very stable. I ran under Trust Tahr for a long while with great success and no Hangups at all. I recently upgraded to Bionic Beaver and I find that I have a number of Hangups. They seem to occur mostly when switching between different users. The latest one that occurred last night that I want to show you here was caused by something else. I was watching a video from Youtube under Firefox. At the end of it I clicked the upper right hand button of the window to kill the screen. At this point the system froze on me. I could move the mouse around but none of the keys worked. I used the SysrRq - Magic Key combination to get the following information ALT + PrtScrn, ALT + CREISUB The system re-booted and gave me the following files in /var/crash 4096 May 9 23:38 202005092338 349 May 10 11:01 kexec_cmd 25387 May 9 23:39 linux-image-5.3.0-51-generic-202005092338.crash 69696 May 9 23:38 dmesg.202005092338 291014103 May 9 23:38 dump.202005092338 I used the crash program with the Symbols file and in the backtrace section under the exception line it says: exception RIP mwait_idle+132 in the disassembly of mwait_idle the line at +132 is mov%gs:0x72774cb4(%rip),%r12d# 0x10350 Any information that I can supply to you I will be glad to in order to aid you in solving this problem. I'm fairly computer literate and so I can follow any directions that you want to give to me. I have enjoyed using Ubutnu for many years but I do need a Stable environment for my Development work and for my users satisfaction. Yours truly, Frank Krauss ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.37 ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 Uname: Linux 5.3.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun May 10 13:19:54 2020 InstallationDate: Installed on 2020-04-20 (19 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: fkrauss1808 F pulseaudio /dev/snd/controlC0: fkrauss1808 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-04-20 (20 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: ens2 no wireless extensions. lono wireless extensions. Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic root=UUID=b52c713d-a2a9-4b17-8eed-79a031a415e8 ro quiet splash zswap.enabled=1 zswap.compressor=lz4 crashkernel=512M-:192M vt.handoff=1 idle=nomwait ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-51-generic N/A linux-backports-modules-5.3.0-51-generic N/A linux-firmware1.173.17 RfKill: Tags: bionic Uname: Linux 5.3.0-51-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 02/08/2010 dmi.bios.vendor: Intel Corp. dmi.bios.version: PRG3110H.86A.0070.2010.0208.1351 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DG31PR dmi.board.vendor: Intel Corporation dmi.board.version: AAD97573-306 dmi.chassis.type: 3 dmi.modalias:
[Kernel-packages] [Bug 1881662] Re: Add Description To Hyper-V Modules
Patches submitted to the SRU cycle:
https://lists.ubuntu.com/archives/kernel-team/2020-June/110609.html
https://lists.ubuntu.com/archives/kernel-team/2020-June/110610.html
https://lists.ubuntu.com/archives/kernel-team/2020-June/110611.html
https://lists.ubuntu.com/archives/kernel-team/2020-June/110612.html
--
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/1881662
Title:
Add Description To Hyper-V Modules
Status in linux-azure package in Ubuntu:
New
Status in linux-azure-4.15 package in Ubuntu:
New
Status in linux-azure source package in Bionic:
Invalid
Status in linux-azure-4.15 source package in Bionic:
In Progress
Status in linux-azure source package in Eoan:
Invalid
Status in linux-azure-4.15 source package in Eoan:
Invalid
Status in linux-azure source package in Focal:
Invalid
Status in linux-azure-4.15 source package in Focal:
Invalid
Bug description:
There are three modules where no description exists causing issues
during a customers certification test:
hid_hyperv
hyperv_keyboard
hv_vmbus
Three patches exist upstream which fix this issue. The mainline
commits are:
64caea53e07f ("HID: hyperv: Add a module description line")
674eecb3d35a ("drivers: hv: Add a module description line to the hv_vmbus
driver")
9d1c2f067e50 ("Input: hyperv-keyboard - add module description")
Can you pull these commits into all releases that are supported on
Azure?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1881662/+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 1879276] Re: Esata port is dead after boot, impossible to hotplug external drive
I tried all 4.16 (1 to 18), none of them work. Should I bisect from 4.16-rc7 to 4.17 or to 4.16.1? -- 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/1879276 Title: Esata port is dead after boot, impossible to hotplug external drive Status in linux package in Ubuntu: Confirmed Bug description: Esata doesn't work after boot: when hotplug an external drive, nothing happens, no dmesg or syslog. It works perfectly when booting on the external HDD itself, and it mounts after boot if plugging on grub prompt. Works on 4.15.3 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: raphael1888 F pulseaudio /dev/snd/pcmC1D0p: raphael1888 F...m pulseaudio /dev/snd/controlC0: raphael1888 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19 HibernationDevice: RESUME=UUID=33415494-1c4c-40d0-ad1b-a02add5f12de InstallationDate: Installed on 2018-03-17 (793 days ago) InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124 MachineType: TOSHIBA TECRA A50-A NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic root=UUID=96e69012-5a43-4af5-8b48-244d376f6fc2 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-51-generic N/A linux-backports-modules-5.3.0-51-generic N/A linux-firmware1.173.18 Tags: tara Uname: Linux 5.3.0-51-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo tty uucp _MarkForUpload: True dmi.bios.date: 04/18/2018 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 5.10 dmi.board.asset.tag: 00 dmi.board.name: TECRA A50-A dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion5.10:bd04/18/2018:svnTOSHIBA:pnTECRAA50-A:pvrPT641E-00600GS4:rvnTOSHIBA:rnTECRAA50-A:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.family: 00 dmi.product.name: TECRA A50-A dmi.product.sku: PT641E dmi.product.version: PT641E-00600GS4 dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879276/+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 1881675] Status changed to Confirmed
This change was made by a bot. ** Changed in: 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/1881675 Title: iwlwifi Microcode SW Error ubuntu 20.04 Status in linux package in Ubuntu: Confirmed Bug description: Sometimes, this bug happens and keep logging as long as I do not not shut down the computer. Internet becomes irresponsive, and the whole computer is slowed. It will keep logging until saturating the hard drive. I had to format the hard drive and reinstall to be able to use the computer again once. Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846676] iwlwifi :02:00.0: Microcode SW error detected. Restarting 0x200. Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846823] iwlwifi :02:00.0: Start IWL Error Log Dump: Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846829] iwlwifi :02:00.0: Status: 0x0040, count: 6 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846833] iwlwifi :02:00.0: Loaded firmware version: 36.77d01142.0 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846838] iwlwifi :02:00.0: 0x0039 | BAD_COMMAND Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846842] iwlwifi :02:00.0: 0x0230 | trm_hw_status0 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846845] iwlwifi :02:00.0: 0x | trm_hw_status1 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846849] iwlwifi :02:00.0: 0x00024200 | branchlink2 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846853] iwlwifi :02:00.0: 0x00039872 | interruptlink1 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846856] iwlwifi :02:00.0: 0x | interruptlink2 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846860] iwlwifi :02:00.0: 0x0002 | data1 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846863] iwlwifi :02:00.0: 0xDEADBEEF | data2 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846867] iwlwifi :02:00.0: 0xDEADBEEF | data3 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846870] iwlwifi :02:00.0: 0x2D004C01 | beacon time Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846874] iwlwifi :02:00.0: 0x39E4BA08 | tsf low Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846877] iwlwifi :02:00.0: 0x0046 | tsf hi Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846880] iwlwifi :02:00.0: 0x | time gp1 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846884] iwlwifi :02:00.0: 0xE24C9E94 | time gp2 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846887] iwlwifi :02:00.0: 0x0001 | uCode revision type Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846891] iwlwifi :02:00.0: 0x0024 | uCode version major Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846894] iwlwifi :02:00.0: 0x77D01142 | uCode version minor Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846898] iwlwifi :02:00.0: 0x0201 | hw version Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846901] iwlwifi :02:00.0: 0x00489008 | board version Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846905] iwlwifi :02:00.0: 0x000D0304 | hcmd Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846908] iwlwifi :02:00.0: 0x24022080 | isr0 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846912] iwlwifi :02:00.0: 0x | isr1 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846915] iwlwifi :02:00.0: 0x0820180A | isr2 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846919] iwlwifi :02:00.0: 0x004154C0 | isr3 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846922] iwlwifi :02:00.0: 0x | isr4 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846926] iwlwifi :02:00.0: 0x9B5E009D | last cmd Id Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846929] iwlwifi :02:00.0: 0x | wait_event Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846933] iwlwifi :02:00.0: 0x0080 | l2p_control Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846936] iwlwifi :02:00.0: 0x00010030 | l2p_duration Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846940] iwlwifi :02:00.0: 0x003F | l2p_mhvalid Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846943] iwlwifi :02:00.0: 0x0080 | l2p_addr_match Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846946] iwlwifi :02:00.0: 0x000D | lmpm_pmg_sel Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846950] iwlwifi :02:00.0: 0x08081421 | timestamp Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846953] iwlwifi :02:00.0: 0x3848 | flow_handler Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.847013] iwlwifi :02:00.0: Start IWL Error Log Dump: Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.847016] iwlwifi :02:00.0: Status: 0x0040, count: 7 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.847020] iwlwifi :02:00.0: 0x0070 | NMI_INTERRUPT_LMAC_FATAL
Re: [Kernel-packages] [Bug 1877890] Re: System Hangs when trying to kill a Window
Dear Sir, I wish to thank you for your suggestion about using a different and older Nucleus. I didn't understand initially about the difference between the 4.x and 5.x Versions. After I did research on them, I installed the 4.15.0 release. It has been running perfectly for the past week so I believe that is the correct solution to my problems of the System hanging periodically. I think that maybe it is because my System was built for me over 10+ years ago. It probably dosn't support the HWE code of the 5.x Series. I will close out this bug and also three other bugs which likewise have no longer shown up. Thank you again for your excellent suggestion that has cleared up these serious problems on my Bionic Beaver System. Yours truly, Frank Krauss + On Tue, 2020-05-12 at 07:10 +, Kai-Heng Feng wrote: > Does the GA kernel (i.e. 4.15) have this issue? > > ** Changed in: linux (Ubuntu) >Status: Confirmed => 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/1877890 Title: System Hangs when trying to kill a Window Status in linux package in Ubuntu: Incomplete Bug description: Dear Sirs, I'm a long term user of Ubuntu, I run a Client/Server system that my clients expect to be very stable. I ran under Trust Tahr for a long while with great success and no Hangups at all. I recently upgraded to Bionic Beaver and I find that I have a number of Hangups. They seem to occur mostly when switching between different users. The latest one that occurred last night that I want to show you here was caused by something else. I was watching a video from Youtube under Firefox. At the end of it I clicked the upper right hand button of the window to kill the screen. At this point the system froze on me. I could move the mouse around but none of the keys worked. I used the SysrRq - Magic Key combination to get the following information ALT + PrtScrn, ALT + CREISUB The system re-booted and gave me the following files in /var/crash 4096 May 9 23:38 202005092338 349 May 10 11:01 kexec_cmd 25387 May 9 23:39 linux-image-5.3.0-51-generic-202005092338.crash 69696 May 9 23:38 dmesg.202005092338 291014103 May 9 23:38 dump.202005092338 I used the crash program with the Symbols file and in the backtrace section under the exception line it says: exception RIP mwait_idle+132 in the disassembly of mwait_idle the line at +132 is mov%gs:0x72774cb4(%rip),%r12d# 0x10350 Any information that I can supply to you I will be glad to in order to aid you in solving this problem. I'm fairly computer literate and so I can follow any directions that you want to give to me. I have enjoyed using Ubutnu for many years but I do need a Stable environment for my Development work and for my users satisfaction. Yours truly, Frank Krauss ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.37 ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 Uname: Linux 5.3.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun May 10 13:19:54 2020 InstallationDate: Installed on 2020-04-20 (19 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: fkrauss1808 F pulseaudio /dev/snd/controlC0: fkrauss1808 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-04-20 (20 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: ens2 no wireless extensions. lono wireless extensions. Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic root=UUID=b52c713d-a2a9-4b17-8eed-79a031a415e8 ro quiet splash zswap.enabled=1 zswap.compressor=lz4 crashkernel=512M-:192M vt.handoff=1 idle=nomwait ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-51-generic N/A linux-backports-modules-5.3.0-51-generic N/A linux-firmware
[Kernel-packages] [Bug 1881662] [NEW] Add Description To Hyper-V Modules
Public bug reported:
There are three modules where no description exists causing issues
during a customers certification test:
hid_hyperv
hyperv_keyboard
hv_vmbus
Three patches exist upstream which fix this issue. The mainline commits
are:
64caea53e07f ("HID: hyperv: Add a module description line")
674eecb3d35a ("drivers: hv: Add a module description line to the hv_vmbus
driver")
9d1c2f067e50 ("Input: hyperv-keyboard - add module description")
Can you pull these commits into all releases that are supported on
Azure?
** Affects: linux-azure (Ubuntu)
Importance: Undecided
Status: New
--
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/1881662
Title:
Add Description To Hyper-V Modules
Status in linux-azure package in Ubuntu:
New
Bug description:
There are three modules where no description exists causing issues
during a customers certification test:
hid_hyperv
hyperv_keyboard
hv_vmbus
Three patches exist upstream which fix this issue. The mainline
commits are:
64caea53e07f ("HID: hyperv: Add a module description line")
674eecb3d35a ("drivers: hv: Add a module description line to the hv_vmbus
driver")
9d1c2f067e50 ("Input: hyperv-keyboard - add module description")
Can you pull these commits into all releases that are supported on
Azure?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1881662/+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 1872001] Re: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0
I looked at this again. The GPU does scale down sometimes. But still the power consumption has without any doubt degraded a lot between 51 and 53 minor versions. The difference is immediately seen by either by looking at powertop or the power consumption or expected battery time in freshly booted kernels respectively. 53 only last 2/3 of the time that 51 lasts. -- 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/1872001 Title: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0 Status in linux package in Ubuntu: Confirmed Status in linux source package in Eoan: Fix Released Bug description: Hi, Since update to HWE kernel 5.3.0-46-generic I am experiencing frequent (every couple of minutes) GPU hangs and reset manifesting as 2-3 seconds freezes of the GUI (other than the mouse pointer). No particular triggers identified although have Chrome / Chromium running with Hardware Acceleration enabled does appear to increase the frequency. I have seen incidences of these hangs in jounralctl output using previous kernels in the 5.3.0-xx series but they were very infrequent (one or twice in a week of daily usage) System Info steve@steve-Inspiron-5580:~$ inxi -SCGxxxz System:Host: steve-Inspiron-5580 Kernel: 5.3.0-46-generic x86_64 bits: 64 compiler: gcc v: 7.5.0 Desktop: Cinnamon 4.4.8 wm: muffin 4.4.2 dm: LightDM 1.26.0 Distro: Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic CPU: Topology: Quad Core model: Intel Core i5-8265U bits: 64 type: MT MCP arch: Kaby Lake rev: B L2 cache: 6144 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 28800 Speed: 1173 MHz min/max: 400/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 Graphics: Device-1: Intel vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:3ea0 Display: x11 server: X.Org 1.20.5 driver: modesetting unloaded: fbdev,vesa resolution: 1920x1080~60Hz OpenGL: renderer: Mesa DRI Intel UHD Graphics (Whiskey Lake 3x8 GT2) v: 4.5 Mesa 19.2.8 compat-v: 3.0 direct render: Yes steve@steve-Inspiron-5580:~$ journalctl -b | grep i915 Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: vgaarb: deactivate vga console Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem Apr 10 06:15:17 steve-Inspiron-5580 kernel: [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4) Apr 10 06:15:17 steve-Inspiron-5580 kernel: [drm] Initialized i915 1.6.0 20190619 for :00:02.0 on minor 0 Apr 10 06:15:17 steve-Inspiron-5580 kernel: fbcon: i915drmfb (fb0) is primary device Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: fb0: i915drmfb frame buffer device Apr 10 06:15:17 steve-Inspiron-5580 kernel: snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) Apr 10 06:16:28 steve-Inspiron-5580 kernel: i915 :00:02.0: GPU HANG: ecode 9:0:0x, hang on rcs0 Apr 10 06:16:28 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:31:46 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:37:48 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:40:46 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 I note another user has reported similar issues on the same kernel at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861395/comments/52 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: steve 3920 F pulseaudio /dev/snd/pcmC0D0p: steve 3920 F...m pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.3 HibernationDevice: RESUME=none InstallationDate: Installed on 2019-12-27 (104 days ago) InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213 MachineType: Dell Inc. Inspiron 5580 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic root=UUID=b0eaa5bb-0276-42d4-938f-ee6ce1627906 ro usb_storage.quirks=0bc2:2320: quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-46-generic N/A linux-backports-modules-5.3.0-46-generic N/A linux-firmware1.173.17 Tags: tricia Uname: Linux 5.3.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo vboxusers
[Kernel-packages] [Bug 1881675] [NEW] iwlwifi Microcode SW Error ubuntu 20.04
Public bug reported: Sometimes, this bug happens and keep logging as long as I do not not shut down the computer. Internet becomes irresponsive, and the whole computer is slowed. It will keep logging until saturating the hard drive. I had to format the hard drive and reinstall to be able to use the computer again once. Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846676] iwlwifi :02:00.0: Microcode SW error detected. Restarting 0x200. Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846823] iwlwifi :02:00.0: Start IWL Error Log Dump: Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846829] iwlwifi :02:00.0: Status: 0x0040, count: 6 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846833] iwlwifi :02:00.0: Loaded firmware version: 36.77d01142.0 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846838] iwlwifi :02:00.0: 0x0039 | BAD_COMMAND Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846842] iwlwifi :02:00.0: 0x0230 | trm_hw_status0 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846845] iwlwifi :02:00.0: 0x | trm_hw_status1 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846849] iwlwifi :02:00.0: 0x00024200 | branchlink2 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846853] iwlwifi :02:00.0: 0x00039872 | interruptlink1 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846856] iwlwifi :02:00.0: 0x | interruptlink2 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846860] iwlwifi :02:00.0: 0x0002 | data1 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846863] iwlwifi :02:00.0: 0xDEADBEEF | data2 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846867] iwlwifi :02:00.0: 0xDEADBEEF | data3 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846870] iwlwifi :02:00.0: 0x2D004C01 | beacon time Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846874] iwlwifi :02:00.0: 0x39E4BA08 | tsf low Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846877] iwlwifi :02:00.0: 0x0046 | tsf hi Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846880] iwlwifi :02:00.0: 0x | time gp1 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846884] iwlwifi :02:00.0: 0xE24C9E94 | time gp2 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846887] iwlwifi :02:00.0: 0x0001 | uCode revision type Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846891] iwlwifi :02:00.0: 0x0024 | uCode version major Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846894] iwlwifi :02:00.0: 0x77D01142 | uCode version minor Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846898] iwlwifi :02:00.0: 0x0201 | hw version Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846901] iwlwifi :02:00.0: 0x00489008 | board version Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846905] iwlwifi :02:00.0: 0x000D0304 | hcmd Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846908] iwlwifi :02:00.0: 0x24022080 | isr0 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846912] iwlwifi :02:00.0: 0x | isr1 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846915] iwlwifi :02:00.0: 0x0820180A | isr2 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846919] iwlwifi :02:00.0: 0x004154C0 | isr3 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846922] iwlwifi :02:00.0: 0x | isr4 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846926] iwlwifi :02:00.0: 0x9B5E009D | last cmd Id Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846929] iwlwifi :02:00.0: 0x | wait_event Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846933] iwlwifi :02:00.0: 0x0080 | l2p_control Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846936] iwlwifi :02:00.0: 0x00010030 | l2p_duration Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846940] iwlwifi :02:00.0: 0x003F | l2p_mhvalid Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846943] iwlwifi :02:00.0: 0x0080 | l2p_addr_match Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846946] iwlwifi :02:00.0: 0x000D | lmpm_pmg_sel Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846950] iwlwifi :02:00.0: 0x08081421 | timestamp Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.846953] iwlwifi :02:00.0: 0x3848 | flow_handler Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.847013] iwlwifi :02:00.0: Start IWL Error Log Dump: Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.847016] iwlwifi :02:00.0: Status: 0x0040, count: 7 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.847020] iwlwifi :02:00.0: 0x0070 | NMI_INTERRUPT_LMAC_FATAL Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.847024] iwlwifi :02:00.0: 0x | umac branchlink1 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.847028] iwlwifi :02:00.0: 0xC0086B38 | umac branchlink2 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.847031] iwlwifi :02:00.0: 0xC0083D08 | umac interruptlink1 Jun 1 16:58:36 maxime-lx-home kernel: [ 3799.847034] iwlwifi :02:00.0: 0xC0083D08 | umac interruptlink2 Jun 1
[Kernel-packages] [Bug 1861028] Re: Fan control stops working on resume for Dell Precision
This still happens on a fresh Focal install using linux- image-5.4.0-26-generic version 5.4.0-26.30 ** Also affects: linux-signed (Ubuntu) Importance: Undecided Status: New ** Tags removed: bionic ** Tags added: focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1861028 Title: Fan control stops working on resume for Dell Precision Status in linux-signed package in Ubuntu: New Status in linux-signed-hwe package in Ubuntu: New Bug description: This system is a Dell Precision Tower 3420 with the latest BIOS 2.13.1, kernel version is 5.3.0-26-generic (HWE, bionic) Freshly booting the system and doing something CPU intensive, like compiling a kernel, cause the CPU fan to ramp up as expected and the CPU temperatures remain acceptable. After suspending (ie Alt-clicking the power button in Unity) and then resuming, the CPU fan runs at a permanent low frequency and does not ramp up. Doing something like a kernel build causes the CPU to overheat and logs messages to dmesg. Investigating I see that the dell_smm_hwmon driver has a 'temp2' input that reflects the CPU temperature. Upon power up the value works properly, after resume it returns -ENODATA. The other sensor for CPU temperature (thermal_zone3/temp, x86_pkg_temp) still works correctly. Blacklisting the dell_smm_hwmon driver has no impact Dell Precisions are listed as compatible with Ubuntu, and this system was purchased with Ubuntu pre-installed from Dell, so it is surpsing something so basic isn't working? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.3.0-26-generic 5.3.0-26.28~18.04.1 ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 27 15:48:39 2020 InstallationDate: Installed on 2018-08-04 (540 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1861028/+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 1881525] Re: in kernel amdgpu failed with W5500 [1002:7341]
Testing PPA: https://launchpad.net/~shanelin/+archive/ubuntu/linux-firmware-amdgpu -- 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/1881525 Title: in kernel amdgpu failed with W5500 [1002:7341] Status in HWE Next: New Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Bionic: In Progress Bug description: [SRU Justfication] [Impact] amdgpu is always failed on bionic 5.4 kernel. Since bionic's kernel will upgrade to 5.4 in the future, but bionic's linux-firmware didn't support navi14. So if a user update kernel to 5.4, he/she still can't use the related navi14 devices. # dmesg | grep amdgpu [drm] amdgpu kernel modesetting enabled. amdgpu remove_conflicting_pci_framebuffers: bar 0: 0x60 -> 0x600fff amdgpu remove_conflicting_pci_framebuffers: bar 2: 0x601000 -> 0x60101f amdgpu remove_conflicting_pci_framebuffers: bar 5: 0x7e80 -> 0x7e87 fb0: switching to amdgpudrmfb from EFI VGA amdgpu vgaarb: deactivate vga console amdgpu enabling device (0106 -> 0107) amdgpu Direct firmware load for amdgpu/navi14_gpu_info.bin failed with error -2 amdgpu Failed to load gpu_info firmware "amdgpu/navi14_gpu_info.bin" amdgpu Fatal error during GPU init [Fix] Patchset[1] for navi14's support currently landed in focal's linux-firmware, so we backported them to bionic's linux-firmware. [1]: aa95e90b2c638f1ca6647d12b2d1b18284428f9c d4f88ea76e442e6652de1367050e33314594d533 40656437f476ef7c47972731671ddcc9e4c4225b 7319341e6e40f8bae1f2623eb5e4ddc0e2b50076 b5b176ac09b6d1211da1e5db8e0c31ac830e4b8c [Test] The amdgpu can be recognized and initialized when booting. # dmesg | grep amdgpu [drm] amdgpu kernel modesetting enabled. amdgpu remove_conflicting_pci_framebuffers: bar 0: 0x60 -> 0x600fff amdgpu remove_conflicting_pci_framebuffers: bar 2: 0x601000 -> 0x60101f amdgpu remove_conflicting_pci_framebuffers: bar 5: 0x7e80 -> 0x7e87 amdgpu enabling device (0106 -> 0107) amdgpu VRAM: 8176M 0x0080 - 0x0081FEFF (8176M used) amdgpu GART: 512M 0x - 0x1FFF [drm] amdgpu: 8176M of VRAM memory ready [drm] amdgpu: 8176M of GTT memory ready. ... [drm] Initialized amdgpu 3.35.0 20150101 for :03:00.0 on minor 1 [Regression Potential] Low, just adding new navi14 firmware, no change to existing firmware. X-HWE-Bug: Bug #1880678 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-hotpie+X34 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-05-25 (6 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Package: linux-firmware 1.173.18+navi14 [origin: LP-PPA-shanelin-linux-firmware] PackageArchitecture: all ProcVersionSignature: Ubuntu 5.4.0-31.35~18.04.2-generic 5.4.34 Tags: bionic uec-images third-party-packages Uname: Linux 5.4.0-31-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1881525/+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 1873325] Re: update-initramfs complains of missing amdgpu firmware files
Confirm affecting Ubuntu 20.04: --- Processing triggers for initramfs-tools (0.136ubuntu6) ... update-initramfs: Generating /boot/initrd.img-5.4.0-33-generic W: Possible missing firmware /lib/firmware/amdgpu/navi12_vcn.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/arcturus_vcn.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi12_smc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/arcturus_smc.bin for module amdgpu --- OS: Ubuntu 20.04 LTS x86_64 Host: NUC8i7HVK J71485-504 Kernel: 5.4.0-29-generic CPU: Intel i7-8809G (8) @ 4.200GHz GPU: AMD ATI Radeon RX Vega M GH Memory: 5031MiB / 64282MiB -- 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/1873325 Title: update-initramfs complains of missing amdgpu firmware files Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Fix Committed Bug description: SRU Justification Impact: amdgpu references firmware files in modinfo which have not been supplied to linux-firmware. This causes update-initramfs to generate "Possible missing firmware" warnings. Fix: Since the firmware is not available, all we can do is remove the files from modinfo. Test Case: Confirm that update-initramfs no longer produces the warnings. Regression Potential: Low. If someone had managed to obtain these files they will no longer be added to the initramfs, potentially causing regressions for these users. This would be an atypical situation. --- Ubuntu 20.04 during initramfs update reports missing firmware files: W: Possible missing firmware /lib/firmware/amdgpu/navi12_vcn.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/arcturus_vcn.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi12_smc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/arcturus_smc.bin for module amdgpu Kernel: 5.4.0-24-generic linux-firmware: 1.187 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873325/+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
