[Kernel-packages] [Bug 1906770] 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 1906770 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/1906770 Title: Kernel 5.4.0-56 Wi-Fi does not connect Status in linux package in Ubuntu: Incomplete Bug description: After updating to 5.4.0-56 (generic) on Mint 19.3, Wi-Fi cannot complete connection to network with Netgear A6210 USB adapter (Mediatek MT7612U chipset). Network manager can see available networks, but attempting to connect to a network stalls on "connecting" and does not complete connection. Reverting to 5.4.0-54 solves problem. I did not see this problem after updating to 5.4.0-56 on a 10-year-old Toshiba Satellite laptop (also Mint 19.3), so it appears related to the Netgear/Mediatek hardware. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1906770/+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 1906601] Re: FBDEV in use with amdgpu and there is no /dev/dri/card0 (hardware is AMD/ATI Renoir [1002:1636])
Right, it still needs amdgpu.exp_hw_support=1 on 5.4. -- 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/1906601 Title: FBDEV in use with amdgpu and there is no /dev/dri/card0 (hardware is AMD/ATI Renoir [1002:1636]) Status in linux package in Ubuntu: Fix Released Status in linux-meta-hwe-5.8 package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Invalid Bug description: New bug from: https://bugs.launchpad.net/ubuntu/+bug/1906525. lshw -c video gives same result of unclaimed video. Night light and HDMI still do not work. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Dec 2 22:09:04 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: rtl8821ce, 5.5.2.1, 5.4.0-56-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Renoir [1043:1352] InstallationDate: Installed on 2020-12-01 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X513IA_M513IA ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-56-generic root=UUID=9f7c4a34-4508-4d48-9c26-c7bf0045826a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X513IA.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X513IA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX513IA.300:bd06/05/2020:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX513IA_M513IA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX513IA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: VivoBook_ASUSLaptop X513IA_M513IA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6 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/1906601/+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 1906770] [NEW] Kernel 5.4.0-56 Wi-Fi does not connect
Public bug reported: After updating to 5.4.0-56 (generic) on Mint 19.3, Wi-Fi cannot complete connection to network with Netgear A6210 USB adapter (Mediatek MT7612U chipset). Network manager can see available networks, but attempting to connect to a network stalls on "connecting" and does not complete connection. Reverting to 5.4.0-54 solves problem. I did not see this problem after updating to 5.4.0-56 on a 10-year-old Toshiba Satellite laptop (also Mint 19.3), so it appears related to the Netgear/Mediatek hardware. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Running under kernel 5.4.0-54" https://bugs.launchpad.net/bugs/1906770/+attachment/5440850/+files/lspci-vnvn.log -- 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/1906770 Title: Kernel 5.4.0-56 Wi-Fi does not connect Status in linux package in Ubuntu: New Bug description: After updating to 5.4.0-56 (generic) on Mint 19.3, Wi-Fi cannot complete connection to network with Netgear A6210 USB adapter (Mediatek MT7612U chipset). Network manager can see available networks, but attempting to connect to a network stalls on "connecting" and does not complete connection. Reverting to 5.4.0-54 solves problem. I did not see this problem after updating to 5.4.0-56 on a 10-year-old Toshiba Satellite laptop (also Mint 19.3), so it appears related to the Netgear/Mediatek hardware. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1906770/+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 1906107] Re: "unexpectedly disconnected from host boot status daemon" under high memory load
Would it be possible for you to do a reverse kernel bisection? First, find the first -rc kernel works and the last -rc kernel doesn’t work from http://kernel.ubuntu.com/~kernel-ppa/mainline/ Then, $ sudo apt build-dep linux $ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git $ cd linux $ git bisect start $ git bisect new $(the working version you found) $ git bisect old $(the non-working version found) $ make localmodconfig $ make -j`nproc` deb-pkg Install the newly built kernel, then reboot with it. If it doesn’t work, $ git bisect old Otherwise, $ git bisect new Repeat to "make -j`nproc` deb-pkg" until you find the commit fixes the issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1906107 Title: "unexpectedly disconnected from host boot status daemon" under high memory load Status in linux package in Ubuntu: Confirmed Bug description: The hardware is Dell XPS13 9343, I'm using FDE with sepreate boot and EFI and NVMe disk. Under high memory load, usually when launching additional window my display goes blank, WiFi connection is lost, I can only reboot and Ctrl+alt+Fn When I do the second I'm getting following message: "unexpectedly disconnected from host boot status daemon" under high memory load Volume-Group 'ubuntu-vg' not found' [...] Please unlock disk nvme0n1op3_crypt: " Despite I enter correct password it doesn't work, seems like it lost connection with NVMe drive at all ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-124-generic 4.15.0-124.127 ProcVersionSignature: Ubuntu 4.15.0-124.127-generic 4.15.18 Uname: Linux 4.15.0-124-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: nusch 10223 F pulseaudio /dev/snd/pcmC0D3p: nusch 10223 F...m pulseaudio /dev/snd/controlC0: nusch 10223 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Nov 28 14:01:20 2020 HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1 InstallationDate: Installed on 2015-05-08 (2031 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. XPS 13 9343 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-124-generic root=/dev/mapper/ubuntu--vg-root ro crashkernel=384M-:128M quiet splash log_buf_len=1M crashkernel=512M-:192M vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-124-generic N/A linux-backports-modules-4.15.0-124-generic N/A linux-firmware 1.173.19 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-08-26 (824 days ago) dmi.bios.date: 06/06/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: A20 dmi.board.name: 09K8G1 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA20:bd06/06/2019:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn09K8G1:rvrA02:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9343 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1906107/+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 1905620] Re: please promote modules from extra to modules for HiFive Unleashed
and it looks like that is failing to reboot over telnet connection =/ i'll build a brand new image with 5.8.0-11 kernel directly and will try that. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1905620 Title: please promote modules from extra to modules for HiFive Unleashed Status in linux-riscv package in Ubuntu: Triaged Status in linux-riscv source package in Focal: Fix Committed Status in linux-riscv source package in Groovy: Fix Committed Status in linux-riscv source package in Hirsute: Triaged Bug description: please promote modules from extra to modules for HiFive Unleashed The following modules are used by the HiFive Unleashed board from extra Please install them in modules. linux-modules-extra-5.4.0-24-generic: /lib/modules/5.4.0-24-generic/kernel/drivers/net/phy/mscc.ko linux-modules-extra-5.4.0-24-generic: /lib/modules/5.4.0-24-generic/kernel/drivers/net/ethernet/cadence/macb.ko linux-modules-extra-5.4.0-24-generic: /lib/modules/5.4.0-24-generic/kernel/drivers/i2c/busses/i2c-ocores.ko To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1905620/+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 1905620] Re: please promote modules from extra to modules for HiFive Unleashed
Deployed focal image. And checked where currently loaded modules are coming from $ cat /proc/modules |cut -f1 -d\ | xargs -L1 modinfo | sed -n 's/filename: *//p' | xargs dpkg -S linux-modules-5.4.0-24-generic: /lib/modules/5.4.0-24-generic/kernel/drivers/uio/uio_pdrv_genirq.ko linux-modules-5.4.0-24-generic: /lib/modules/5.4.0-24-generic/kernel/drivers/uio/uio.ko linux-modules-5.4.0-24-generic: /lib/modules/5.4.0-24-generic/kernel/drivers/gpu/drm/drm.ko linux-modules-5.4.0-24-generic: /lib/modules/5.4.0-24-generic/kernel/net/sched/sch_fq_codel.ko linux-modules-5.4.0-24-generic: /lib/modules/5.4.0-24-generic/kernel/drivers/gpu/drm/drm_panel_orientation_quirks.ko linux-modules-5.4.0-24-generic: /lib/modules/5.4.0-24-generic/kernel/net/ipv4/netfilter/ip_tables.ko linux-modules-5.4.0-24-generic: /lib/modules/5.4.0-24-generic/kernel/net/netfilter/x_tables.ko linux-modules-5.4.0-24-generic: /lib/modules/5.4.0-24-generic/kernel/fs/autofs/autofs4.ko linux-modules-extra-5.4.0-24-generic: /lib/modules/5.4.0-24-generic/kernel/drivers/net/phy/mscc.ko linux-modules-extra-5.4.0-24-generic: /lib/modules/5.4.0-24-generic/kernel/drivers/net/ethernet/cadence/macb.ko linux-modules-extra-5.4.0-24-generic: /lib/modules/5.4.0-24-generic/kernel/drivers/i2c/busses/i2c-ocores.ko Enabled groovy, groovy-updates, groovy-proposed. Performed $ sudo apt install linux-virtual linux-generic- such that 5.8.0-11 kernel is installed from groovy-proposed, *without* modules-extra. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1905620 Title: please promote modules from extra to modules for HiFive Unleashed Status in linux-riscv package in Ubuntu: Triaged Status in linux-riscv source package in Focal: Fix Committed Status in linux-riscv source package in Groovy: Fix Committed Status in linux-riscv source package in Hirsute: Triaged Bug description: please promote modules from extra to modules for HiFive Unleashed The following modules are used by the HiFive Unleashed board from extra Please install them in modules. linux-modules-extra-5.4.0-24-generic: /lib/modules/5.4.0-24-generic/kernel/drivers/net/phy/mscc.ko linux-modules-extra-5.4.0-24-generic: /lib/modules/5.4.0-24-generic/kernel/drivers/net/ethernet/cadence/macb.ko linux-modules-extra-5.4.0-24-generic: /lib/modules/5.4.0-24-generic/kernel/drivers/i2c/busses/i2c-ocores.ko To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1905620/+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 1890130] Re: Add support for Intel Bluetooth Device Typhoon Peak (8087:0032)
** Changed in: linux-firmware (Ubuntu Focal) Importance: Undecided => High ** Changed in: linux-firmware (Ubuntu Groovy) Importance: Undecided => High ** Changed in: linux-firmware (Ubuntu Groovy) Status: New => In Progress ** Changed in: linux-firmware (Ubuntu Groovy) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Changed in: linux-oem-5.10 (Ubuntu Focal) Importance: Undecided => High ** Changed in: linux-oem-5.10 (Ubuntu Focal) Status: Incomplete => In Progress ** Changed in: linux-oem-5.10 (Ubuntu Focal) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Changed in: linux (Ubuntu Focal) Status: Incomplete => Won't Fix ** Changed in: linux (Ubuntu Groovy) Importance: Undecided => High ** Changed in: linux (Ubuntu Groovy) Status: New => In Progress ** Changed in: linux (Ubuntu Groovy) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Changed in: linux (Ubuntu Hirsute) Importance: Undecided => High ** Changed in: linux (Ubuntu Hirsute) Status: Incomplete => In Progress ** Changed in: linux-oem-5.6 (Ubuntu Focal) Status: Invalid => Won't Fix -- 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/1890130 Title: Add support for Intel Bluetooth Device Typhoon Peak (8087:0032) Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Invalid Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-firmware source package in Focal: In Progress Status in linux-oem-5.10 source package in Focal: In Progress Status in linux-oem-5.6 source package in Focal: Won't Fix Status in linux source package in Groovy: In Progress Status in linux-firmware source package in Groovy: In Progress Status in linux-oem-5.10 source package in Groovy: Invalid Status in linux-oem-5.6 source package in Groovy: Invalid Status in linux source package in Hirsute: In Progress Status in linux-firmware source package in Hirsute: Invalid Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.6 source package in Hirsute: Invalid Bug description: Device from /sys/kernel/debug/usb/devices: T: Bus=01 Lev=01 Prnt=01 Port=13 Cnt=02 Dev#= 3 Spd=12 MxCh= 0 D: Ver= 2.01 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=8087 ProdID=0032 Rev= 0.00 Prerequisite commits: * https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=875e16759005e3bdaa84eb2741281f37ba35b886 * https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3e4e3f73b9f4 And: https://patchwork.kernel.org/project/bluetooth/list/?series=387475 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1890130/+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 1905620] Re: please promote modules from extra to modules for HiFive Unleashed
starting verification of the groovy's build. It will take a bit of time =) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1905620 Title: please promote modules from extra to modules for HiFive Unleashed Status in linux-riscv package in Ubuntu: Triaged Status in linux-riscv source package in Focal: Fix Committed Status in linux-riscv source package in Groovy: Fix Committed Status in linux-riscv source package in Hirsute: Triaged Bug description: please promote modules from extra to modules for HiFive Unleashed The following modules are used by the HiFive Unleashed board from extra Please install them in modules. linux-modules-extra-5.4.0-24-generic: /lib/modules/5.4.0-24-generic/kernel/drivers/net/phy/mscc.ko linux-modules-extra-5.4.0-24-generic: /lib/modules/5.4.0-24-generic/kernel/drivers/net/ethernet/cadence/macb.ko linux-modules-extra-5.4.0-24-generic: /lib/modules/5.4.0-24-generic/kernel/drivers/i2c/busses/i2c-ocores.ko To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1905620/+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 1902848] Re: Support Intel AX210 wifi [8086:2725] Subsystem [8086:0020]
** Changed in: linux-firmware (Ubuntu Groovy) Importance: Undecided => High ** Changed in: linux-firmware (Ubuntu Groovy) Status: Confirmed => In Progress ** Changed in: linux-firmware (Ubuntu Groovy) Assignee: (unassigned) => You-Sheng Yang (vicamo) -- 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/1902848 Title: Support Intel AX210 wifi [8086:2725] Subsystem [8086:0020] Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Invalid Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-firmware source package in Focal: In Progress Status in linux-oem-5.10 source package in Focal: In Progress Status in linux source package in Groovy: Incomplete Status in linux-firmware source package in Groovy: In Progress Status in linux-oem-5.10 source package in Groovy: Invalid Status in linux source package in Hirsute: In Progress Status in linux-firmware source package in Hirsute: Invalid Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: Firmware: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/iwlwifi-ty-a0-gf-a0-59.ucode?id=4f41e9d6437d03e7ce9279076107dd08f46656f3 Kernel v5.10-rc1 or newer. 04:00.0 Network controller [0280]: Intel Corporation Device [8086:2725] (rev 1a) Subsystem: Intel Corporation Device [8086:0020] 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: iwlwifi Kernel modules: iwlwifi Bluetooth part in bug 1890130. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-10-13 (22 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 100: ID 8087:0032 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel Corporation Rocket Lake Client Platform Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1-generic root=UUID=221267f2-0315-4b8c-98c3-6e791d5615fc ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.10.0-1.2-generic 5.10.0-rc2 RelatedPackageVersions: linux-restricted-modules-5.10.0-1-generic N/A linux-backports-modules-5.10.0-1-generic N/A linux-firmware1.190 RfKill: Tags: focal Uname: Linux 5.10.0-1-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: False acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie Error executing command as another user: Not authorized This incident has been reported. dmi.bios.date: 08/20/2020 dmi.bios.vendor: Intel Corporation dmi.bios.version: RKLSFWI1.R00.1344.A00.2008202030 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: RocketLake S UDIMM 6L RVP dmi.board.vendor: Intel Corporation dmi.board.version: 1 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.4 dmi.modalias: dmi:bvnIntelCorporation:bvrRKLSFWI1.R00.1344.A00.2008202030:bd08/20/2020:efr1.4:svnIntelCorporation:pnRocketLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnRocketLakeSUDIMM6LRVP:rvr1:cvnIntelCorporation:ct3:cvr0.1: dmi.product.family: Rocket Lake Client System dmi.product.name: Rocket Lake Client Platform dmi.product.sku: 0025 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1902848/+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 1902848] Re: Support Intel AX210 wifi [8086:2725] Subsystem [8086:0020]
Verified with bug 1890105 (AX210 bluetooth) in https://code.launchpad.net/~vicamo/+git/ubuntu-kernel/+ref/bug-1890130 /support-intel-bluetooth-typhoon-peak/unstable. Will submit SRU patches later. -- 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/1902848 Title: Support Intel AX210 wifi [8086:2725] Subsystem [8086:0020] Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Invalid Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-firmware source package in Focal: In Progress Status in linux-oem-5.10 source package in Focal: In Progress Status in linux source package in Groovy: Incomplete Status in linux-firmware source package in Groovy: Confirmed Status in linux-oem-5.10 source package in Groovy: Invalid Status in linux source package in Hirsute: In Progress Status in linux-firmware source package in Hirsute: Invalid Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: Firmware: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/iwlwifi-ty-a0-gf-a0-59.ucode?id=4f41e9d6437d03e7ce9279076107dd08f46656f3 Kernel v5.10-rc1 or newer. 04:00.0 Network controller [0280]: Intel Corporation Device [8086:2725] (rev 1a) Subsystem: Intel Corporation Device [8086:0020] 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: iwlwifi Kernel modules: iwlwifi Bluetooth part in bug 1890130. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-10-13 (22 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 100: ID 8087:0032 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel Corporation Rocket Lake Client Platform Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1-generic root=UUID=221267f2-0315-4b8c-98c3-6e791d5615fc ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.10.0-1.2-generic 5.10.0-rc2 RelatedPackageVersions: linux-restricted-modules-5.10.0-1-generic N/A linux-backports-modules-5.10.0-1-generic N/A linux-firmware1.190 RfKill: Tags: focal Uname: Linux 5.10.0-1-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: False acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie Error executing command as another user: Not authorized This incident has been reported. dmi.bios.date: 08/20/2020 dmi.bios.vendor: Intel Corporation dmi.bios.version: RKLSFWI1.R00.1344.A00.2008202030 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: RocketLake S UDIMM 6L RVP dmi.board.vendor: Intel Corporation dmi.board.version: 1 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.4 dmi.modalias: dmi:bvnIntelCorporation:bvrRKLSFWI1.R00.1344.A00.2008202030:bd08/20/2020:efr1.4:svnIntelCorporation:pnRocketLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnRocketLakeSUDIMM6LRVP:rvr1:cvnIntelCorporation:ct3:cvr0.1: dmi.product.family: Rocket Lake Client System dmi.product.name: Rocket Lake Client Platform dmi.product.sku: 0025 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1902848/+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 1872401] Re: vmx_nm_test in ubuntu_kvm_unit_tests interrupted on X-oracle-4.15 / B-oracle-4.15 / X-KVM / B-KVM
** No longer affects: linux-signed-oracle (Ubuntu Bionic) ** No longer affects: linux-signed-oracle (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1872401 Title: vmx_nm_test in ubuntu_kvm_unit_tests interrupted on X-oracle-4.15 / B-oracle-4.15 / X-KVM / B-KVM Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Bug description: [Impact] When running kvm-unit-tests under a guest, it will be paused, requiring a reset. When running the same test on a host (vmx_nm_test), it will fail. [Test case] Grab kvm-unit-tests, build it and run: TESTNAME=vmx TIMEOUT=90s ACCEL= ./x86/run x86/vmx.flat -smp 1 -cpu host,+vmx -append "vmx_nm_test" If done inside a guest, when the host runs the bionic 4.15 kernel, the guest will pause. [Potential regressions] Nested KVM could stop working. Floating point could stop working on KVM guests, though the code that relied on this was already removed from Bionic. -- This issue was first spotted on Mar.16 [1] The ubuntu_kvm_unit_tests will be interrupted on X-oracle-4.15 on both VM.Standard2.1 and VM.Standard2.16, this is not a regression since it can be reproduced with 4.15.0-1031-oracle #34~16.04.1: Running '/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/tests/vmx_nm_test' BUILD_HEAD=4671e4ba timeout -k 1s --foreground 30 /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.da3iFrsCzC -smp 1 -cpu host,+vmx -append vmx_nm_test # -initrd /tmp/tmp.h2DFw8L0AF enabling apic paging enabled cr0 = 80010011 cr3 = 477000 cr4 = 20 Test suite: vmx_nm_test client_loop: send disconnect: Broken pipe (node disconnected here) Before the test started, this can be found in syslog: Apr 13 06:26:25 selfprovisioned-phlin-kvm-unit kernel: [ 1073.529005] L1TF CPU bug present and SMT on, data leak possible. See CVE-2018-3646 and https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/l1tf.html for details. After that, noting was printed and node disconnected. If you try to run this case manually, it will stop at: # ./vmx_nm_test BUILD_HEAD=4671e4ba ready!!! timeout -k 1s --foreground 30 /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.ZcGrnXu6se -smp 1 -cpu host,+vmx -append vmx_nm_test # -initrd /tmp/tmp.ADjEOAcRKM enabling ap (stopped here, even the "enabling apic" string was not printed) It looks like this is a new test case added since the cycle of 4.15.0-1037.41~16.04.1-oracle [1] https://bugs.launchpad.net/ubuntu-kernel- tests/+bug/1867623/comments/2 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.15.0-1031-oracle 4.15.0-1031.34~16.04.1 ProcVersionSignature: User Name 4.15.0-1031.34~16.04.1-oracle 4.15.18 Uname: Linux 4.15.0-1031-oracle x86_64 ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 Date: Mon Apr 13 05:18:03 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-oracle UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1872401/+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 1901272] Re: Can't connect Bluetooth devices after reboot - Ubuntu 20.10 on Raspberry Pi 4
I also just installed on a pi 4 and had the same issue -- devices worked but would not persist across reboots, and then successive re-adds were... strange, unreliable, etc. Lots of "it appears to work but doesn't." Tried the PPA packages and it worked at first, but was seriously inconsistent at adding and removing devices. I downgraded the PPA packages back to originals and still couldn't reliably add devices. I re-upgraded to PPA packages and the bluetooth was essentially working less than ever. Since it felt like a software issue, like configurations and "sessions" were being munged, I killed BT, searched around and wiped out /var/lib/bluetooth/* (which appeared to have multiple base addresses???) and then I was able to clean out gnome's ui and re-add and things now persist across reboots. To me, this seems like the PPA fixes the issue, but the original packages created a state where there were multiple stale / conflicting states in /var/lib/bluetooth that you must disabled bt, clean, then re-enable / reboot and things work. It almost feels like the original packages had the BT adapter changing addresses each boot or similar. -- 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/1901272 Title: Can't connect Bluetooth devices after reboot - Ubuntu 20.10 on Raspberry Pi 4 Status in bluez package in Ubuntu: Incomplete Status in linux-raspi package in Ubuntu: Incomplete Status in pi-bluetooth package in Ubuntu: Confirmed Status in bluez source package in Groovy: Incomplete Status in linux-raspi source package in Groovy: Incomplete Status in pi-bluetooth source package in Groovy: New Bug description: Raspberry pi 4 4Gb ram Ubuntu desktop 20.10 64 bit After reboot no Bluetooth devices connect, scanning Bluetooth devices works, results with same device name (duplicated and with not set up status). Sometimes after several reboots it works. If I use power off and cycle power then it works fine each time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1901272/+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 1906341] Re: Touchpad button doesn't work on Dell Precision 7550/7750
@seb128 Thanks for reviewing it carefully and the explicit explanation. -- 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/1906341 Title: Touchpad button doesn't work on Dell Precision 7550/7750 Status in OEM Priority Project: New Status in libevdev package in Ubuntu: Fix Released Status in libinput package in Ubuntu: Fix Released Status in linux package in Ubuntu: Confirmed Bug description: [Impact] * The touchpad's right button become no function after update to 5.4 kernel * The INPUT_PROP_BUTTONPAD property is set by 5.4 kernel, so that libinput regard it as clickpad, the root cause is that the touchpad firmware doesn't config correctly. * Add a model quirk to unset the bit can make touchpad's right button works normally. [Test Case] * 1. Boot into Ubuntu 2. Identify touchpad input device number, can be obtained in $HOME/.local/share/xorg/Xorg.0.log 3. $ udevadm info /sys/class/input/inputX check PROP environment variable, it is 5 if INPUT_PROP_BUTTONPAD property is set 4. And the touchpad right button become no function 5. After update the libevdev with disable_property API and libinput10 with model quirk 6. reboot 7. The input device PROP is still 5, but touchpad right button is workable [Where problems could occur] * For libevdev2 package, backport the upstream commit: https://gitlab.freedesktop.org/libevdev/libevdev/-/commit/4226c7801b4ea1b0c7d1eaac47ca24ece8f24809 The API is not originally exist in the system, so it will only be utilized by our model quirk. * For libinput, add model quirk for the platform to disable INPUT_PROP_BUTTONPAD bit. Only disable the INPUT_PROP_BUTTONPAD for specified model, and it doesn't issue any IO command to kernel, so the behavior should be the same as previous kernel when INPUT_PROP_BUTTONPAD is not set. [Other Info] * A public bug is reported https://www.dell.com/community/Linux-Developer-Systems/Touchpad-right-click-button-not-working-with-Ubuntu-20-04-on/td-p/7636831 * A workable build for Bionic/Focal/Groovy are in my ppa https://launchpad.net/~kchsieh/+archive/ubuntu/training --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1646 F pulseaudio BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu GraphicsCard: Intel Corporation Device [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:09c3] InstallationDate: Installed on 2020-12-01 (0 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) MachineType: Dell Inc. Precision 7550 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=2964a5af-ac17-45ee-a009-41879da14e1b ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.173.19 Tags: bionic ubuntu Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/01/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd09/01/2020:svnDellInc.:pnPrecision7550:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 7550 dmi.product.sku: 09C3 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1906341/+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 1906745] Re: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module failed to build
lspci | grep -i network 03:00.0 Network controller: Broadcom Inc. and subsidiaries BCM4322 802.11a/b/g/n Wireless LAN Controller (rev 01) SOLUTION sudo apt-get purge bcmwl-kernel-source sudo apt-get install broadcom-sta-source broadcom-sta-dkms broadcom-sta-common reboot now wifi is OK -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1906745 Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module failed to build Status in bcmwl package in Ubuntu: New Bug description: apt-get upgrade caused crash of wireless bcmwl afterwards my wifi fails to work before updates had x86_64 5.4.0-57-generic DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu 20.04.1 LTS" apt-get upgrade The following NEW packages will be installed: linux-headers-5.8.0-32-generic linux-hwe-5.8-headers-5.8.0-32 linux-image-5.8.0-32-generic linux-modules-5.8.0-32-generic linux-modules-extra-5.8.0-32-generic The following packages will be upgraded: linux-generic-hwe-20.04 linux-headers-generic-hwe-20.04 linux-image-generic-hwe-20.04 wireless-regdb Setting up linux-modules-5.8.0-32-generic (5.8.0-32.34~20.04.1) ... Setting up linux-hwe-5.8-headers-5.8.0-32 (5.8.0-32.34~20.04.1) ... Setting up linux-headers-5.8.0-32-generic (5.8.0-32.34~20.04.1) ... /etc/kernel/header_postinst.d/dkms: * dkms: running auto installation service for kernel 5.8.0-32-generic Kernel preparation unnecessary for this kernel. Skipping... applying patch 0002-Makefile.patch...patching file Makefile Hunk #1 succeeded at 113 with fuzz 1. Hunk #2 succeeded at 132 with fuzz 2 (offset 1 line). applying patch 0003-Make-up-for-missing-init_MUTEX.patch...patching file src/wl/sys/wl_linux.c Hunk #1 succeeded at 111 with fuzz 2 (offset 12 lines). applying patch 0010-change-the-network-interface-name-from-eth-to-wlan.patch...patching file src/wl/sys/wl_linux.c Hunk #1 succeeded at 221 (offset -14 lines). applying patch 0013-gcc.patch...patching file Makefile applying patch 0019-broadcom-sta-6.30.223.248-3.18-null-pointer-fix.patch...patching file src/wl/sys/wl_linux.c Hunk #1 succeeded at 2169 (offset 12 lines). applying patch 0020-add-support-for-linux-4.3.patch...patching file src/shared/linux_osl.c applying patch 0021-add-support-for-Linux-4.7.patch...patching file src/wl/sys/wl_cfg80211_hybrid.c applying patch 0022-add-support-for-Linux-4.8.patch...patching file src/wl/sys/wl_cfg80211_hybrid.c Hunk #1 succeeded at 2391 (offset 3 lines). Hunk #2 succeeded at 2501 (offset 3 lines). Hunk #3 succeeded at 2933 (offset 9 lines). applying patch 0023-add-support-for-Linux-4.11.patch...patching file src/include/linuxver.h patching file src/wl/sys/wl_linux.c Hunk #1 succeeded at 2919 (offset 4 lines). applying patch 0024-add-support-for-Linux-4.12.patch...patching file src/wl/sys/wl_cfg80211_hybrid.c Hunk #1 succeeded at 55 (offset 5 lines). Hunk #2 succeeded at 472 (offset 5 lines). Hunk #3 succeeded at 2371 (offset 5 lines). Hunk #4 succeeded at 2388 (offset 5 lines). applying patch 0025-add-support-for-Linux-4.14.patch...patching file src/shared/linux_osl.c Hunk #1 succeeded at 1080 (offset 4 lines). applying patch 0026-add-support-for-Linux-4.15.patch...patching file src/wl/sys/wl_linux.c Hunk #2 succeeded at 2306 (offset 4 lines). Hunk #3 succeeded at 2368 (offset 4 lines). applying patch 0027-add-support-for-linux-5.1.patch...patching file src/include/linuxver.h Hunk #1 succeeded at 595 (offset 4 lines). Building module: cleaning build area... make -j8 KERNELRELEASE=5.8.0-32-generic -C /lib/modules/5.8.0-32-generic/build M=/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build...(bad exit status: 2) Error! Bad return status for module build on kernel: 5.8.0-32-generic (x86_64) Consult /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log for more information. ...done. Setting up linux-image-5.8.0-32-generic (5.8.0-32.34~20.04.1) ... I: /boot/vmlinuz.old is now a symlink to vmlinuz-5.4.0-57-generic I: /boot/initrd.img.old is now a symlink to initrd.img-5.4.0-57-generic I: /boot/vmlinuz is now a symlink to vmlinuz-5.8.0-32-generic I: /boot/initrd.img is now a symlink to initrd.img-5.8.0-32-generic Setting up linux-headers-generic-hwe-20.04 (5.8.0.32.34~20.04.19) ... Setting up linux-modules-extra-5.8.0-32-generic (5.8.0-32.34~20.04.1) ... Setting up linux-image-generic-hwe-20.04 (5.8.0.32.34~20.04.19) ... Setting up linux-generic-hwe-20.04 (5.8.0.32.34~20.04.19) ... Processing triggers for man-db (2.9.1-1) ... Processing triggers for linux-image-5.8.0-32-generic (5.8.0-32.34~20.04.1) ... /etc/kernel/postinst.d/dkms: * dkms: running auto installation service for kernel 5.8.0-32-generic Kernel
[Kernel-packages] [Bug 1884255] Re: [AMD/ATI] SBx00 Azalia (Intel HDA) Audio Ubuntu 20.04 not working
Uninstalling pulseaudio and working only with alsa, the same problem continues. I was playing the audio with the specifications of aplay -l Lista de Dispositivos PLAYBACK Hardware placa 0: SB [HDA ATI SB], dispositivo 0: ALC887-VD Analog [ALC887-VD Analog] Dispositivo secundário: 0/1 Dispositivo secundário #0: subdevice #0 placa 0: SB [HDA ATI SB], dispositivo 1: ALC887-VD Digital [ALC887-VD Digital] Dispositivo secundário: 1/1 Dispositivo secundário #0: subdevice #0 when the audio stopped and I ran aplay -l and returned: Lista de Dispositivos PLAYBACK Hardware placa 0: SB [HDA ATI SB], dispositivo 0: ALC887-VD Analog [ALC887-VD Analog] Dispositivo secundário: 1/1 Dispositivo secundário #0: subdevice #0 placa 0: SB [HDA ATI SB], dispositivo 1: ALC887-VD Digital [ALC887-VD Digital] Dispositivo secundário: 1/1 Dispositivo secundário #0: subdevice #0 Does anyone know what can it be? -- 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/1884255 Title: [AMD/ATI] SBx00 Azalia (Intel HDA) Audio Ubuntu 20.04 not working Status in PulseAudio: Unknown Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: When you start playing some audio, the sound disappears. 00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) Subsystem: ASUSTeK Computer Inc. M5A78L LE Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel uname -a Linux Marcelo-STI-FX6300 5.4.0-37-generic #41-Ubuntu SMP Wed Jun 3 18:57:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux alsa-info !! !!ALSA Information Script v 0.4.65 !! !!Script ran on: Fri Jun 19 13:38:12 UTC 2020 !!Linux Distribution !!-- Ubuntu 20.04 LTS \n \l DISTRIB_ID=Ubuntu DISTRIB_DESCRIPTION="Ubuntu 20.04 LTS" NAME="Ubuntu" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04 LTS" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies /privacy-policy" UBUNTU_CODENAME=focal !!DMI Information !!--- Manufacturer: System manufacturer Product Name: System Product Name Product Version: System Version Firmware Version: 1201 Board Vendor: ASUSTeK Computer INC. Board Name:M5A78L-M LX/BR !!ACPI Device Status Information !!--- /sys/bus/acpi/devices/ATK0110:00/status15 /sys/bus/acpi/devices/PNP0103:00/status15 /sys/bus/acpi/devices/PNP0400:00/status15 /sys/bus/acpi/devices/PNP0501:00/status15 /sys/bus/acpi/devices/PNP0C0C:00/status11 /sys/bus/acpi/devices/PNP0C0F:00/status9 /sys/bus/acpi/devices/PNP0C0F:01/status9 /sys/bus/acpi/devices/PNP0C0F:02/status9 /sys/bus/acpi/devices/PNP0C0F:03/status9 /sys/bus/acpi/devices/PNP0C0F:04/status9 /sys/bus/acpi/devices/PNP0C0F:05/status9 /sys/bus/acpi/devices/PNP0C0F:06/status9 /sys/bus/acpi/devices/PNP0C0F:07/status9 /sys/bus/acpi/devices/device:20/status 15 /sys/bus/acpi/devices/device:21/status 15 !!Kernel Information !!-- Kernel release:5.4.0-37-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.4.0-37-generic Library version:1.2.3 Utilities version: 1.2.2 !!Loaded ALSA modules !!--- snd_hda_intel !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- 0 [SB ]: HDA-Intel - HDA ATI SB HDA ATI SB at 0xfe9f4000 irq 16 !!PCI Soundcards installed in the system !!-- 00:14.2 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) [1002:4383] Subsystem: ASUSTeK Computer Inc. M5A78L LE [1043:8445] !!Modprobe options (Sound related) !! snd_pcsp: index=-2 snd_usb_audio: index=-2 snd_atiixp_modem: index=-2 snd_intel8x0m: index=-2 snd_via82xx_modem: index=-2 snd_atiixp_modem: index=-2 snd_intel8x0m: index=-2 snd_via82xx_modem: index=-2 snd_usb_audio: index=-2 snd_usb_caiaq: index=-2 snd_usb_ua101: index=-2 snd_usb_us122l: index=-2 snd_usb_usx2y: index=-2 snd_cmipci: mpu_port=0x330 fm_port=0x388 snd_pcsp: index=-2 snd_usb_audio: index=-2 snd_hda_intel:
[Kernel-packages] [Bug 1884255] Re: [AMD/ATI] SBx00 Azalia (Intel HDA) Audio Ubuntu 20.04 not working
Uninstalling pulseaudio and working only with alsa, the same problem continues. I was playing the audio with the specifications of aplay -l Lista de Dispositivos PLAYBACK Hardware placa 0: SB [HDA ATI SB], dispositivo 0: ALC887-VD Analog [ALC887-VD Analog] Dispositivo secundário: 0/1 Dispositivo secundário #0: subdevice #0 placa 0: SB [HDA ATI SB], dispositivo 1: ALC887-VD Digital [ALC887-VD Digital] Dispositivo secundário: 1/1 Dispositivo secundário #0: subdevice #0 when the audio stopped and I ran aplay -l and returned: Lista de Dispositivos PLAYBACK Hardware placa 0: SB [HDA ATI SB], dispositivo 0: ALC887-VD Analog [ALC887-VD Analog] Dispositivo secundário: 1/1 Dispositivo secundário #0: subdevice #0 placa 0: SB [HDA ATI SB], dispositivo 1: ALC887-VD Digital [ALC887-VD Digital] Dispositivo secundário: 1/1 Dispositivo secundário #0: subdevice #0 Does anyone know what can it be? -- 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/1884255 Title: [AMD/ATI] SBx00 Azalia (Intel HDA) Audio Ubuntu 20.04 not working Status in PulseAudio: Unknown Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: When you start playing some audio, the sound disappears. 00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) Subsystem: ASUSTeK Computer Inc. M5A78L LE Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel uname -a Linux Marcelo-STI-FX6300 5.4.0-37-generic #41-Ubuntu SMP Wed Jun 3 18:57:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux alsa-info !! !!ALSA Information Script v 0.4.65 !! !!Script ran on: Fri Jun 19 13:38:12 UTC 2020 !!Linux Distribution !!-- Ubuntu 20.04 LTS \n \l DISTRIB_ID=Ubuntu DISTRIB_DESCRIPTION="Ubuntu 20.04 LTS" NAME="Ubuntu" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04 LTS" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies /privacy-policy" UBUNTU_CODENAME=focal !!DMI Information !!--- Manufacturer: System manufacturer Product Name: System Product Name Product Version: System Version Firmware Version: 1201 Board Vendor: ASUSTeK Computer INC. Board Name:M5A78L-M LX/BR !!ACPI Device Status Information !!--- /sys/bus/acpi/devices/ATK0110:00/status15 /sys/bus/acpi/devices/PNP0103:00/status15 /sys/bus/acpi/devices/PNP0400:00/status15 /sys/bus/acpi/devices/PNP0501:00/status15 /sys/bus/acpi/devices/PNP0C0C:00/status11 /sys/bus/acpi/devices/PNP0C0F:00/status9 /sys/bus/acpi/devices/PNP0C0F:01/status9 /sys/bus/acpi/devices/PNP0C0F:02/status9 /sys/bus/acpi/devices/PNP0C0F:03/status9 /sys/bus/acpi/devices/PNP0C0F:04/status9 /sys/bus/acpi/devices/PNP0C0F:05/status9 /sys/bus/acpi/devices/PNP0C0F:06/status9 /sys/bus/acpi/devices/PNP0C0F:07/status9 /sys/bus/acpi/devices/device:20/status 15 /sys/bus/acpi/devices/device:21/status 15 !!Kernel Information !!-- Kernel release:5.4.0-37-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.4.0-37-generic Library version:1.2.3 Utilities version: 1.2.2 !!Loaded ALSA modules !!--- snd_hda_intel !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- 0 [SB ]: HDA-Intel - HDA ATI SB HDA ATI SB at 0xfe9f4000 irq 16 !!PCI Soundcards installed in the system !!-- 00:14.2 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) [1002:4383] Subsystem: ASUSTeK Computer Inc. M5A78L LE [1043:8445] !!Modprobe options (Sound related) !! snd_pcsp: index=-2 snd_usb_audio: index=-2 snd_atiixp_modem: index=-2 snd_intel8x0m: index=-2 snd_via82xx_modem: index=-2 snd_atiixp_modem: index=-2 snd_intel8x0m: index=-2 snd_via82xx_modem: index=-2 snd_usb_audio: index=-2 snd_usb_caiaq: index=-2 snd_usb_ua101: index=-2 snd_usb_us122l: index=-2 snd_usb_usx2y: index=-2 snd_cmipci: mpu_port=0x330 fm_port=0x388 snd_pcsp: index=-2 snd_usb_audio: index=-2 snd_hda_intel:
[Kernel-packages] [Bug 1906745] [NEW] bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module failed to build
Public bug reported: apt-get upgrade caused crash of wireless bcmwl afterwards my wifi fails to work before updates had x86_64 5.4.0-57-generic DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu 20.04.1 LTS" apt-get upgrade The following NEW packages will be installed: linux-headers-5.8.0-32-generic linux-hwe-5.8-headers-5.8.0-32 linux-image-5.8.0-32-generic linux-modules-5.8.0-32-generic linux-modules-extra-5.8.0-32-generic The following packages will be upgraded: linux-generic-hwe-20.04 linux-headers-generic-hwe-20.04 linux-image-generic-hwe-20.04 wireless-regdb Setting up linux-modules-5.8.0-32-generic (5.8.0-32.34~20.04.1) ... Setting up linux-hwe-5.8-headers-5.8.0-32 (5.8.0-32.34~20.04.1) ... Setting up linux-headers-5.8.0-32-generic (5.8.0-32.34~20.04.1) ... /etc/kernel/header_postinst.d/dkms: * dkms: running auto installation service for kernel 5.8.0-32-generic Kernel preparation unnecessary for this kernel. Skipping... applying patch 0002-Makefile.patch...patching file Makefile Hunk #1 succeeded at 113 with fuzz 1. Hunk #2 succeeded at 132 with fuzz 2 (offset 1 line). applying patch 0003-Make-up-for-missing-init_MUTEX.patch...patching file src/wl/sys/wl_linux.c Hunk #1 succeeded at 111 with fuzz 2 (offset 12 lines). applying patch 0010-change-the-network-interface-name-from-eth-to-wlan.patch...patching file src/wl/sys/wl_linux.c Hunk #1 succeeded at 221 (offset -14 lines). applying patch 0013-gcc.patch...patching file Makefile applying patch 0019-broadcom-sta-6.30.223.248-3.18-null-pointer-fix.patch...patching file src/wl/sys/wl_linux.c Hunk #1 succeeded at 2169 (offset 12 lines). applying patch 0020-add-support-for-linux-4.3.patch...patching file src/shared/linux_osl.c applying patch 0021-add-support-for-Linux-4.7.patch...patching file src/wl/sys/wl_cfg80211_hybrid.c applying patch 0022-add-support-for-Linux-4.8.patch...patching file src/wl/sys/wl_cfg80211_hybrid.c Hunk #1 succeeded at 2391 (offset 3 lines). Hunk #2 succeeded at 2501 (offset 3 lines). Hunk #3 succeeded at 2933 (offset 9 lines). applying patch 0023-add-support-for-Linux-4.11.patch...patching file src/include/linuxver.h patching file src/wl/sys/wl_linux.c Hunk #1 succeeded at 2919 (offset 4 lines). applying patch 0024-add-support-for-Linux-4.12.patch...patching file src/wl/sys/wl_cfg80211_hybrid.c Hunk #1 succeeded at 55 (offset 5 lines). Hunk #2 succeeded at 472 (offset 5 lines). Hunk #3 succeeded at 2371 (offset 5 lines). Hunk #4 succeeded at 2388 (offset 5 lines). applying patch 0025-add-support-for-Linux-4.14.patch...patching file src/shared/linux_osl.c Hunk #1 succeeded at 1080 (offset 4 lines). applying patch 0026-add-support-for-Linux-4.15.patch...patching file src/wl/sys/wl_linux.c Hunk #2 succeeded at 2306 (offset 4 lines). Hunk #3 succeeded at 2368 (offset 4 lines). applying patch 0027-add-support-for-linux-5.1.patch...patching file src/include/linuxver.h Hunk #1 succeeded at 595 (offset 4 lines). Building module: cleaning build area... make -j8 KERNELRELEASE=5.8.0-32-generic -C /lib/modules/5.8.0-32-generic/build M=/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build...(bad exit status: 2) Error! Bad return status for module build on kernel: 5.8.0-32-generic (x86_64) Consult /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log for more information. ...done. Setting up linux-image-5.8.0-32-generic (5.8.0-32.34~20.04.1) ... I: /boot/vmlinuz.old is now a symlink to vmlinuz-5.4.0-57-generic I: /boot/initrd.img.old is now a symlink to initrd.img-5.4.0-57-generic I: /boot/vmlinuz is now a symlink to vmlinuz-5.8.0-32-generic I: /boot/initrd.img is now a symlink to initrd.img-5.8.0-32-generic Setting up linux-headers-generic-hwe-20.04 (5.8.0.32.34~20.04.19) ... Setting up linux-modules-extra-5.8.0-32-generic (5.8.0-32.34~20.04.1) ... Setting up linux-image-generic-hwe-20.04 (5.8.0.32.34~20.04.19) ... Setting up linux-generic-hwe-20.04 (5.8.0.32.34~20.04.19) ... Processing triggers for man-db (2.9.1-1) ... Processing triggers for linux-image-5.8.0-32-generic (5.8.0-32.34~20.04.1) ... /etc/kernel/postinst.d/dkms: * dkms: running auto installation service for kernel 5.8.0-32-generic Kernel preparation unnecessary for this kernel. Skipping... applying patch 0002-Makefile.patch...patching file Makefile Hunk #1 succeeded at 113 with fuzz 1. Hunk #2 succeeded at 132 with fuzz 2 (offset 1 line). applying patch 0003-Make-up-for-missing-init_MUTEX.patch...patching file src/wl/sys/wl_linux.c Hunk #1 succeeded at 111 with fuzz 2 (offset 12 lines). applying patch 0010-change-the-network-interface-name-from-eth-to-wlan.patch...patching file src/wl/sys/wl_linux.c Hunk #1 succeeded at 221 (offset -14 lines). applying patch 0013-gcc.patch...patching file Makefile applying patch 0019-broadcom-sta-6.30.223.248-3.18-null-pointer-fix.patch...patching file src/wl/sys/wl_linux.c Hunk #1 succeeded at 2169 (offset 12 lines). applying patch
[Kernel-packages] [Bug 1906449] Re: [nvidia] [amdgpu] Xorg randomly freezes
Thanks. Good news at least that I don't see any kernel driver crashes there. ** Changed in: xorg-server (Ubuntu) Status: Incomplete => New ** Package changed: xorg-server (Ubuntu) => nvidia-graphics-drivers-440 (Ubuntu) ** Also affects: xserver-xorg-video-amdgpu (Ubuntu) Importance: Undecided Status: New ** Also affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Also affects: xfce4 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/1906449 Title: [nvidia] [amdgpu] Xorg randomly freezes Status in nvidia-graphics-drivers-440 package in Ubuntu: New Status in xfce4 package in Ubuntu: New Status in xorg-server package in Ubuntu: New Status in xserver-xorg-video-amdgpu package in Ubuntu: New Bug description: Initially, I thought it only happened during file transfers (because that's when it happens most often), but I later found that it can happen at any time, because I just turned my computer on, went to go make a coffee, have a cigarette, and when I came back, the entire screen, desktop, system, etc had frozen again. I always need to hold the power button down to do an emergency restart, because I can't even use Alt+F# to get into the TTY. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-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.95.01 Thu May 28 07:03:08 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Tue Dec 1 12:28:44 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.95.01, 5.4.0-56-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: NVIDIA Corporation TU106 [GeForce RTX 2060] [10de:1f15] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:1e21] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev f0) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Renoir [1043:1e21] InstallationDate: Installed on 2020-12-01 (0 days ago) InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: ASUSTeK COMPUTER INC. TUF Gaming FA506IV_TUF506IV ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-56-generic root=UUID=11577769-570c-4297-a9b2-35fb3a30f6bf ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FA506IV.309 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FA506IV dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFA506IV.309:bd07/02/2020:svnASUSTeKCOMPUTERINC.:pnTUFGamingFA506IV_TUF506IV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFA506IV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: TUF Gaming FA506IV dmi.product.name: TUF Gaming FA506IV_TUF506IV dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. nvidia-settings: ERROR: Unable to load info from any available system ERROR: Unable to load info from any available system version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6 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
[Kernel-packages] [Bug 1906449] [NEW] [nvidia] [amdgpu] Xorg randomly freezes
You have been subscribed to a public bug: Initially, I thought it only happened during file transfers (because that's when it happens most often), but I later found that it can happen at any time, because I just turned my computer on, went to go make a coffee, have a cigarette, and when I came back, the entire screen, desktop, system, etc had frozen again. I always need to hold the power button down to do an emergency restart, because I can't even use Alt+F# to get into the TTY. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-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.95.01 Thu May 28 07:03:08 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Tue Dec 1 12:28:44 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.95.01, 5.4.0-56-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: NVIDIA Corporation TU106 [GeForce RTX 2060] [10de:1f15] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:1e21] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev f0) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Renoir [1043:1e21] InstallationDate: Installed on 2020-12-01 (0 days ago) InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: ASUSTeK COMPUTER INC. TUF Gaming FA506IV_TUF506IV ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-56-generic root=UUID=11577769-570c-4297-a9b2-35fb3a30f6bf ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FA506IV.309 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FA506IV dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFA506IV.309:bd07/02/2020:svnASUSTeKCOMPUTERINC.:pnTUFGamingFA506IV_TUF506IV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFA506IV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: TUF Gaming FA506IV dmi.product.name: TUF Gaming FA506IV_TUF506IV dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. nvidia-settings: ERROR: Unable to load info from any available system ERROR: Unable to load info from any available system version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6 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 ** Affects: nvidia-graphics-drivers-440 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 amdgpu apport-bug focal freeze hybrid nvidia ubuntu -- [nvidia] [amdgpu] Xorg randomly freezes https://bugs.launchpad.net/bugs/1906449 You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 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 1906601] Re: FBDEV in use with amdgpu and there is no /dev/dri/card0 (hardware is AMD/ATI Renoir [1002:1636])
Timo, The release notes incorrectly(?) suggest Renoir support is in kernel 5.4: https://wiki.ubuntu.com/FocalFossa/ReleaseNotes -- 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/1906601 Title: FBDEV in use with amdgpu and there is no /dev/dri/card0 (hardware is AMD/ATI Renoir [1002:1636]) Status in linux package in Ubuntu: Fix Released Status in linux-meta-hwe-5.8 package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Invalid Bug description: New bug from: https://bugs.launchpad.net/ubuntu/+bug/1906525. lshw -c video gives same result of unclaimed video. Night light and HDMI still do not work. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Dec 2 22:09:04 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: rtl8821ce, 5.5.2.1, 5.4.0-56-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Renoir [1043:1352] InstallationDate: Installed on 2020-12-01 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X513IA_M513IA ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-56-generic root=UUID=9f7c4a34-4508-4d48-9c26-c7bf0045826a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X513IA.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X513IA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX513IA.300:bd06/05/2020:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX513IA_M513IA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX513IA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: VivoBook_ASUSLaptop X513IA_M513IA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6 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/1906601/+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 1906601] Re: FBDEV in use with amdgpu and there is no /dev/dri/card0 (hardware is AMD/ATI Renoir [1002:1636])
It's a little bit cryptic but at the top of this page: linux (Ubuntu) Fix Released refers to the fix being in Ubuntu 20.10. linux-meta-hwe-5.8 (Ubuntu) Fix Released refers to the fix being optional in Ubuntu 20.04. Only if you were using 20.04 would you need to install linux-generic-hwe-20.04-edge. -- 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/1906601 Title: FBDEV in use with amdgpu and there is no /dev/dri/card0 (hardware is AMD/ATI Renoir [1002:1636]) Status in linux package in Ubuntu: Fix Released Status in linux-meta-hwe-5.8 package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Invalid Bug description: New bug from: https://bugs.launchpad.net/ubuntu/+bug/1906525. lshw -c video gives same result of unclaimed video. Night light and HDMI still do not work. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Dec 2 22:09:04 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: rtl8821ce, 5.5.2.1, 5.4.0-56-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Renoir [1043:1352] InstallationDate: Installed on 2020-12-01 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X513IA_M513IA ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-56-generic root=UUID=9f7c4a34-4508-4d48-9c26-c7bf0045826a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X513IA.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X513IA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX513IA.300:bd06/05/2020:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX513IA_M513IA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX513IA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: VivoBook_ASUSLaptop X513IA_M513IA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6 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/1906601/+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 1906700] Re: Xenial update: v4.4.246 upstream stable release
** Changed in: linux (Ubuntu Xenial) Status: In Progress => Fix Committed -- 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/1906700 Title: Xenial update: v4.4.246 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Fix Committed Bug description: 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: v4.4.246 upstream stable release from git://git.kernel.org/ ah6: fix error return code in ah6_input() atm: nicstar: Unmap DMA on send error net: b44: fix error return code in b44_init_one() net: bridge: add missing counters to ndo_get_stats64 callback netlabel: fix our progress tracking in netlbl_unlabel_staticlist() netlabel: fix an uninitialized warning in netlbl_unlabel_staticlist() net/mlx4_core: Fix init_hca fields offset net: x25: Increase refcnt of "struct x25_neigh" in x25_rx_call_request qlcnic: fix error return code in qlcnic_83xx_restart_hw() sctp: change to hold/put transport for proto_unreach_timer net: usb: qmi_wwan: Set DTR quirk for MR400 net: Have netpoll bring-up DSA management interface pinctrl: rockchip: enable gpio pclk for rockchip_gpio_to_irq arm64: psci: Avoid printing in cpu_psci_cpu_die() MIPS: Fix BUILD_ROLLBACK_PROLOGUE for microMIPS Input: adxl34x - clean up a data type in adxl34x_probe() arm: dts: imx6qdl-udoo: fix rgmii phy-mode for ksz9031 phy ARM: dts: imx50-evk: Fix the chip select 1 IOMUX perf lock: Don't free "lock_seq_stat" if read_count isn't zero can: dev: can_restart(): post buffer from the right context can: peak_usb: fix potential integer overflow on shift of a int can: m_can: m_can_handle_state_change(): fix state change MIPS: Alchemy: Fix memleak in alchemy_clk_setup_cpu regulator: ti-abb: Fix array out of bound read access on the first transition libfs: fix error cast of negative value in simple_attr_write() ALSA: ctl: fix error path at adding user-defined element set ALSA: mixart: Fix mutex deadlock tty: serial: imx: keep console clocks always on efivarfs: fix memory leak in efivarfs_create() ext4: fix bogus warning in ext4_update_dx_flag() xtensa: disable preemption around cache alias management calls mac80211: minstrel: remove deferred sampling code mac80211: minstrel: fix tx status processing corner case mac80211: allow driver to prevent two stations w/ same address mac80211: free sta in sta_info_insert_finish() on errors s390/cpum_sf.c: fix file permission for cpum_sfb_size x86/microcode/intel: Check patch signature before saving microcode for early loading Linux 4.4.246 UBUNTU: upstream stable to v4.4.246 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1906700/+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 1906703] Re: Xenial update: v4.4.247 upstream stable release
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => Fix Committed
--
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/1906703
Title:
Xenial update: v4.4.247 upstream stable release
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Xenial:
Fix Committed
Bug description:
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:
v4.4.247 upstream stable release
from git://git.kernel.org/
btrfs: tree-checker: Enhance chunk checker to validate chunk profile
btrfs: inode: Verify inode mode to avoid NULL pointer dereference
HID: cypress: Support Varmilo Keyboards' media hotkeys
Input: i8042 - allow insmod to succeed on devices without an i8042 controller
HID: hid-sensor-hub: Fix issue with devices with no report ID
x86/xen: don't unbind uninitialized lock_kicker_irq
proc: don't allow async path resolution of /proc/self components
dmaengine: pl330: _prep_dma_memcpy: Fix wrong burst size
scsi: libiscsi: Fix NOP race condition
scsi: target: iscsi: Fix cmd abort fabric stop race
scsi: ufs: Fix race between shutdown and runtime resume flow
bnxt_en: fix error return code in bnxt_init_board()
video: hyperv_fb: Fix the cache type when mapping the VRAM
bnxt_en: Release PCI regions when DMA mask setup fails during probe.
IB/mthca: fix return value of error branch in mthca_init_cq()
nfc: s3fwrn5: use signed integer for parsing GPIO numbers
efivarfs: revert "fix memory leak in efivarfs_create()"
perf probe: Fix to die_entrypc() returns error correctly
USB: core: Change %pK for __user pointers to %px
x86/speculation: Fix prctl() when spectre_v2_user={seccomp,prctl},ibpb
USB: core: add endpoint-blacklist quirk
USB: core: Fix regression in Hercules audio card
btrfs: fix lockdep splat when reading qgroup config on mount
Linux 4.4.247
UBUNTU: upstream stable to v4.4.247
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1906703/+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 1905205] Re: ubuntu_stress_smoke_test Segmentation fault in linux from Groovy/linux 5.8.0-30.32 ADT test failure
This bug was fixed in the package stress-ng - 0.12.00-1 --- stress-ng (0.12.00-1) unstable; urgency=medium * Makefile: bump version * stress-epoll: fix sanity check for an unexpected epoll_ctl success * stress-funccall: disable ALWAYS_INLINE for PCC * stress-inotify: add void argument, fixes pcc build warning * stress-epoll: fix pcc build warning * stress-close: add invalid flags call to close_range * core-shim: add flags field to close_range shim to match 5.10 system call * stress-utime: voidify return using assignment and voidification * stress-stack: reduce scope of variable ret * stress-sock: clean up some cppcheck warnings * stress-mlock: put HAVE_MLOCKALL into a statement block * stress-affinity: add in missing voidification of ret * stress-brk: remove redundant return 0 statement * stress-pkey: limit pkey system call warning to just instance 0 * core-helper: don't use getpwent for static stress-ng builds: * stress-stack: rename sz to mlock_sz to avoid variable shadowing * stress-pthread: remove duplicate declaration of ret to clean up build warning * stress-msg: rename variable i to j to avoid name shadowing warning * stress-prctl: remove redundant declaration of environ * stress-msg: clean up variable shadowing * stress-yield: workaround FreeBSD usleep bug * stress-timer: workaround duplicated timer_delete segfault in FreeBSD * stress-ng.h: make shim_unconstify_ptr a static inline helper * stress-link: cast getpid() return to int for %d format specifier * stress-open: only declare obsolete_futimesat when it is required * stress-mmap: voidify page_size if HAVE_MPROTECT is not defined * stress-access: declare variable j only if HAVE_FACCESSAT is defined * stress-sem-sysv: silently ignore failures on semctl commands * stress-sem-sysv: ensure 4th arg of semctl is zero when not used * stress-sem-sysv: fix zero semaphores case in GETALL semctl * stress-brk: don't exercise mlockall with MCL_FUTURE if it is not defined * Fix clobbering of errno by error message logging before reading errno * stress-sem-sysv: move scope of array sems * stress-poll: make tv_nsec out of range value a 32 bit value * stress-mmap: only use PROT_GROWSUP and PROT_GROWSDOWN if supported * Fix ~0ULL cast to void * build warnings on 32 bit builds * kernel-coverage: add --pathological for sysinval stress * syscalls: update work to do and recent changes * stress-vm-splice: add pipe to memory vmsplicing * stress-utime: exercise utime family of calls with invalid filenames * stress-sysinfo: fix build issues introduced by previous commit * stress-sysinfo: exercise ustat with invalid major/minor * stress-userfaultfd: exercise UFFDIO_WAKE * stress-ramfs: exercise umount with some invalid pathnames * stress-binderfs: exercise invalid umount calls * stress-hdd: exercise invalid ftruncate/truncate fd/filename * stress-hdd: exercise invalid ftruncate/truncate size * stress-timer: exercise duplicated timer_delete * stress-pthread: add tkill to shim and exercise it * stress-pthread: add tgkill to shim and exercise it * stress-sync-file: exercise 0 nbytes sync, it has special semantics * stress-swap: exercise swapon with invalid path * stress-sysinfo: exercise invalid statfs path * stress-fstat: exercise stat, lstat on invalid path * stress-splice: exercise splice with some more invalid or untested arguments * stress-bad-altstack: exercise sigaltstack with various stack settings * core-helper: fix comment, min stack size can be MINSIGSTKSZ * stress-sysinval: only allow with --pathological option (LP: #1906447) * stress-shm-sysv: exercise duplicated shmdt on unmapped addresses * stress-shm-sysv: define MPOL_* only if required, add one more shmctl call * stress-xattr: exercise invalid setxattr arguments * stress-set: add timezone argument to get more kernel coverage * stress-nice: fix priority ranges, use correct offset in priority * stress-set: exercise invalid pid and pgid in setpgid call * stress-clone: exercise setns with invalid nstype and fd * stress-set: exercise sethostname with illegal length host * stress-set: exercise a range of setgroups calls * stress-set: exercise setdomainname with invalid name length * stress-pthread: exercise set_tid_address with NULL address * stress-pthread: exercise set_robust_list with invalid length * stress-numa: add in a mix of various set_mempolicy calls * stress-sendfile: add more kernel coverage tests * stress-sendfile: periodically exercise sendfile with invalid arguments * core-helper: find bad_fd in reverse fd order if RLIMIT not supported * stress-sem-sysv: disable SETALL and exercise long run of semops * stress-sem-sysv: exercise semctl with various invalid arguments * stress-sem-sysv: add SIGCHLD handler to ensure pause() gets interrupted * stress-schedpolicy: exercise sched_setscheduler with invalid
[Kernel-packages] [Bug 1906341] Re: Touchpad button doesn't work on Dell Precision 7550/7750
This bug was fixed in the package libinput - 1.16.4-1ubuntu1 --- libinput (1.16.4-1ubuntu1) hirsute; urgency=medium * quirks: Unset INPUT_PROP_BUTTONPAD for Dell Precision 7550/7750. (LP: #1906341) * Update control build-dep libevdev-dev (>= 1.10.0) for libevdev_disable_property API -- Sebastien Bacher Thu, 03 Dec 2020 16:32:27 +0100 ** Changed in: libinput (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1906341 Title: Touchpad button doesn't work on Dell Precision 7550/7750 Status in OEM Priority Project: New Status in libevdev package in Ubuntu: Fix Released Status in libinput package in Ubuntu: Fix Released Status in linux package in Ubuntu: Confirmed Bug description: [Impact] * The touchpad's right button become no function after update to 5.4 kernel * The INPUT_PROP_BUTTONPAD property is set by 5.4 kernel, so that libinput regard it as clickpad, the root cause is that the touchpad firmware doesn't config correctly. * Add a model quirk to unset the bit can make touchpad's right button works normally. [Test Case] * 1. Boot into Ubuntu 2. Identify touchpad input device number, can be obtained in $HOME/.local/share/xorg/Xorg.0.log 3. $ udevadm info /sys/class/input/inputX check PROP environment variable, it is 5 if INPUT_PROP_BUTTONPAD property is set 4. And the touchpad right button become no function 5. After update the libevdev with disable_property API and libinput10 with model quirk 6. reboot 7. The input device PROP is still 5, but touchpad right button is workable [Where problems could occur] * For libevdev2 package, backport the upstream commit: https://gitlab.freedesktop.org/libevdev/libevdev/-/commit/4226c7801b4ea1b0c7d1eaac47ca24ece8f24809 The API is not originally exist in the system, so it will only be utilized by our model quirk. * For libinput, add model quirk for the platform to disable INPUT_PROP_BUTTONPAD bit. Only disable the INPUT_PROP_BUTTONPAD for specified model, and it doesn't issue any IO command to kernel, so the behavior should be the same as previous kernel when INPUT_PROP_BUTTONPAD is not set. [Other Info] * A public bug is reported https://www.dell.com/community/Linux-Developer-Systems/Touchpad-right-click-button-not-working-with-Ubuntu-20-04-on/td-p/7636831 * A workable build for Bionic/Focal/Groovy are in my ppa https://launchpad.net/~kchsieh/+archive/ubuntu/training --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1646 F pulseaudio BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu GraphicsCard: Intel Corporation Device [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:09c3] InstallationDate: Installed on 2020-12-01 (0 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) MachineType: Dell Inc. Precision 7550 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=2964a5af-ac17-45ee-a009-41879da14e1b ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.173.19 Tags: bionic ubuntu Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/01/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd09/01/2020:svnDellInc.:pnPrecision7550:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 7550 dmi.product.sku: 09C3 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
[Kernel-packages] [Bug 1906447] Re: init_module may pin a lot of memory if given a bogus size
This bug was fixed in the package stress-ng - 0.12.00-1 --- stress-ng (0.12.00-1) unstable; urgency=medium * Makefile: bump version * stress-epoll: fix sanity check for an unexpected epoll_ctl success * stress-funccall: disable ALWAYS_INLINE for PCC * stress-inotify: add void argument, fixes pcc build warning * stress-epoll: fix pcc build warning * stress-close: add invalid flags call to close_range * core-shim: add flags field to close_range shim to match 5.10 system call * stress-utime: voidify return using assignment and voidification * stress-stack: reduce scope of variable ret * stress-sock: clean up some cppcheck warnings * stress-mlock: put HAVE_MLOCKALL into a statement block * stress-affinity: add in missing voidification of ret * stress-brk: remove redundant return 0 statement * stress-pkey: limit pkey system call warning to just instance 0 * core-helper: don't use getpwent for static stress-ng builds: * stress-stack: rename sz to mlock_sz to avoid variable shadowing * stress-pthread: remove duplicate declaration of ret to clean up build warning * stress-msg: rename variable i to j to avoid name shadowing warning * stress-prctl: remove redundant declaration of environ * stress-msg: clean up variable shadowing * stress-yield: workaround FreeBSD usleep bug * stress-timer: workaround duplicated timer_delete segfault in FreeBSD * stress-ng.h: make shim_unconstify_ptr a static inline helper * stress-link: cast getpid() return to int for %d format specifier * stress-open: only declare obsolete_futimesat when it is required * stress-mmap: voidify page_size if HAVE_MPROTECT is not defined * stress-access: declare variable j only if HAVE_FACCESSAT is defined * stress-sem-sysv: silently ignore failures on semctl commands * stress-sem-sysv: ensure 4th arg of semctl is zero when not used * stress-sem-sysv: fix zero semaphores case in GETALL semctl * stress-brk: don't exercise mlockall with MCL_FUTURE if it is not defined * Fix clobbering of errno by error message logging before reading errno * stress-sem-sysv: move scope of array sems * stress-poll: make tv_nsec out of range value a 32 bit value * stress-mmap: only use PROT_GROWSUP and PROT_GROWSDOWN if supported * Fix ~0ULL cast to void * build warnings on 32 bit builds * kernel-coverage: add --pathological for sysinval stress * syscalls: update work to do and recent changes * stress-vm-splice: add pipe to memory vmsplicing * stress-utime: exercise utime family of calls with invalid filenames * stress-sysinfo: fix build issues introduced by previous commit * stress-sysinfo: exercise ustat with invalid major/minor * stress-userfaultfd: exercise UFFDIO_WAKE * stress-ramfs: exercise umount with some invalid pathnames * stress-binderfs: exercise invalid umount calls * stress-hdd: exercise invalid ftruncate/truncate fd/filename * stress-hdd: exercise invalid ftruncate/truncate size * stress-timer: exercise duplicated timer_delete * stress-pthread: add tkill to shim and exercise it * stress-pthread: add tgkill to shim and exercise it * stress-sync-file: exercise 0 nbytes sync, it has special semantics * stress-swap: exercise swapon with invalid path * stress-sysinfo: exercise invalid statfs path * stress-fstat: exercise stat, lstat on invalid path * stress-splice: exercise splice with some more invalid or untested arguments * stress-bad-altstack: exercise sigaltstack with various stack settings * core-helper: fix comment, min stack size can be MINSIGSTKSZ * stress-sysinval: only allow with --pathological option (LP: #1906447) * stress-shm-sysv: exercise duplicated shmdt on unmapped addresses * stress-shm-sysv: define MPOL_* only if required, add one more shmctl call * stress-xattr: exercise invalid setxattr arguments * stress-set: add timezone argument to get more kernel coverage * stress-nice: fix priority ranges, use correct offset in priority * stress-set: exercise invalid pid and pgid in setpgid call * stress-clone: exercise setns with invalid nstype and fd * stress-set: exercise sethostname with illegal length host * stress-set: exercise a range of setgroups calls * stress-set: exercise setdomainname with invalid name length * stress-pthread: exercise set_tid_address with NULL address * stress-pthread: exercise set_robust_list with invalid length * stress-numa: add in a mix of various set_mempolicy calls * stress-sendfile: add more kernel coverage tests * stress-sendfile: periodically exercise sendfile with invalid arguments * core-helper: find bad_fd in reverse fd order if RLIMIT not supported * stress-sem-sysv: disable SETALL and exercise long run of semops * stress-sem-sysv: exercise semctl with various invalid arguments * stress-sem-sysv: add SIGCHLD handler to ensure pause() gets interrupted * stress-schedpolicy: exercise sched_setscheduler with invalid
[Kernel-packages] [Bug 1906698] Re: Xenial update: v4.4.245 upstream stable release
** Changed in: linux (Ubuntu Xenial) Status: In Progress => Fix Committed -- 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/1906698 Title: Xenial update: v4.4.245 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Fix Committed Bug description: 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: v4.4.245 upstream stable release from git://git.kernel.org/ i2c: imx: Fix external abort on interrupt in exit paths xfs: catch inode allocation state mismatch corruption xfs: validate cached inodes are free when allocated powerpc/8xx: Always fault when _PAGE_ACCESSED is not set Input: sunkbd - avoid use-after-free in teardown paths mac80211: always wind down STA state KVM: x86: clflushopt should be treated as a no-op by emulation Linux 4.4.245 UBUNTU: upstream stable to v4.4.245 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1906698/+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 1899826] Re: backport upstream fixes for 5.9 Linux support
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: zfs-linux (Ubuntu Groovy)
Status: New => Confirmed
--
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/1899826
Title:
backport upstream fixes for 5.9 Linux support
Status in zfs-linux package in Ubuntu:
Fix Released
Status in zfs-linux source package in Groovy:
Confirmed
Status in zfs-linux source package in Hirsute:
Fix Released
Bug description:
== SRU Request Groovy ==
Upstream zfs supports 5.9. it would be useful to backport these for
users who want newer kernels.
== The Fix ==
Although 6 fixes are required, 2 add changes that get removed by a
later change, so one can backport this with just the following 4
changes:
1823c8fe6a4a20971463e9b51615dad412aea9a9 ("Linux 5.9 compat: add
linux/blkdev.h include")
3e29e1971bbb4ab63dafeb592b747ef56bad3534 ("Linux 5.9 compat:
NR_SLAB_RECLAIMABLE")
d817c17100183b266aa6bf8b868e016805d51d16 ("Linux 5.9 compat: make_request_fn
replaced with submit_bio")
4b59c195ffbaebfdd5f0971a54613c0ed7c42005 ("Increase Supported Linux Kernel to
5.9")
== Regression potential ==
The first patch just includes blkdev.h to workaround a build warning,
so the results in no functional change to the working code.
The second patch removes legacy arc page free estimation by droping
the accounting for inactive anonymous pages and reclaimable pages on
the slab. This change removes a very minor component of the free
memory calculation and speeds up arc free stats calculations. There is
a potential that this small change in free page calculation may impact
systems where memory is more constrained, but the change is so small I
believe this really is insignificant.
The third patch is a build time detection of the kernel block
allocation queue due to API changes, so should not change behaviour
for current 5.8 kernels, only change behaviour for newer kernels with
the newer kernel API. Hence for the released 5.8 groovy kernel the
code will not be changed, so the regression potential for 5.8 is zero.
The final patch changes the META build data to allow the driver to
build on newer kernels, so the risk on this change is effectively
zero.
== Testing ==
Run the autotest client tests for ZFS tests:
ubuntu_zfs_smoke_tests (general functionality smoke tests)
ubuntu_zfs_fstests (file system semantics tests)
ubuntu_zfs_xfs_generic (subset of XFS tests on ZFS)
ubuntu_zfs_stress (stress-ng file system tests on a wide range of ZFS mount
options)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1899826/+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 1906476] Re: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) failed
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: zfs-linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1906476 Title: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) failed Status in zfs-linux package in Ubuntu: Confirmed Bug description: Since today while running Ubuntu 21.04 Hirsute I started getting a ZFS panic in the kernel log which was also hanging Disk I/O for all Chrome/Electron Apps. I have narrowed down a few important notes: - It does not happen with module version 0.8.4-1ubuntu11 built and included with 5.8.0-29-generic - It was happening when using zfs-dkms 0.8.4-1ubuntu16 built with DKMS on the same kernel and also on 5.8.18-acso (a custom kernel). - For whatever reason multiple Chrome/Electron apps were affected, specifically Discord, Chrome and Mattermost. In all cases they seem (but I was unable to strace the processes so it was a bit hard ot confirm 100% but by deduction from /proc/PID/fd and the hanging ls) they seem hung trying to open files in their 'Cache' directory, e.g. ~/.cache/google-chrome/Default/Cache and ~/.config/Mattermost/Cache .. while the issue was going on I could not list that directory either "ls" would just hang. - Once I removed zfs-dkms only to revert to the kernel built-in version it immediately worked without changing anything, removing files, etc. - It happened over multiple reboots and kernels every time, all my Chrome apps weren't working but for whatever reason nothing else seemed affected. - It would log a series of spl_panic dumps into kern.log that look like this: Dec 2 12:36:42 optane kernel: [ 72.857033] VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) failed Dec 2 12:36:42 optane kernel: [ 72.857036] PANIC at zfs_znode.c:335:zfs_znode_sa_init() I could only find one other google reference to this issue, with 2 other users reporting the same error but on 20.04 here: https://github.com/openzfs/zfs/issues/10971 - I was not experiencing the issue on 0.8.4-1ubuntu14 and fairly sure it was working on 0.8.4-1ubuntu15 but broken after upgrade to 0.8.4-1ubuntu16. I will reinstall those zfs-dkms versions to verify that. There were a few originating call stacks but the first one I hit was Call Trace: dump_stack+0x74/0x95 spl_dumpstack+0x29/0x2b [spl] spl_panic+0xd4/0xfc [spl] ? sa_cache_constructor+0x27/0x50 [zfs] ? _cond_resched+0x19/0x40 ? mutex_lock+0x12/0x40 ? dmu_buf_set_user_ie+0x54/0x80 [zfs] zfs_znode_sa_init+0xe0/0xf0 [zfs] zfs_znode_alloc+0x101/0x700 [zfs] ? arc_buf_fill+0x270/0xd30 [zfs] ? __cv_init+0x42/0x60 [spl] ? dnode_cons+0x28f/0x2a0 [zfs] ? _cond_resched+0x19/0x40 ? _cond_resched+0x19/0x40 ? mutex_lock+0x12/0x40 ? aggsum_add+0x153/0x170 [zfs] ? spl_kmem_alloc_impl+0xd8/0x110 [spl] ? arc_space_consume+0x54/0xe0 [zfs] ? dbuf_read+0x4a0/0xb50 [zfs] ? _cond_resched+0x19/0x40 ? mutex_lock+0x12/0x40 ? dnode_rele_and_unlock+0x5a/0xc0 [zfs] ? _cond_resched+0x19/0x40 ? mutex_lock+0x12/0x40 ? dmu_object_info_from_dnode+0x84/0xb0 [zfs] zfs_zget+0x1c3/0x270 [zfs] ? dmu_buf_rele+0x3a/0x40 [zfs] zfs_dirent_lock+0x349/0x680 [zfs] zfs_dirlook+0x90/0x2a0 [zfs] ? zfs_zaccess+0x10c/0x480 [zfs] zfs_lookup+0x202/0x3b0 [zfs] zpl_lookup+0xca/0x1e0 [zfs] path_openat+0x6a2/0xfe0 do_filp_open+0x9b/0x110 ? __check_object_size+0xdb/0x1b0 ? __alloc_fd+0x46/0x170 do_sys_openat2+0x217/0x2d0 ? do_sys_openat2+0x217/0x2d0 do_sys_open+0x59/0x80 __x64_sys_openat+0x20/0x30 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1906476/+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 1870971] Re: [amdgpu] (X)ubuntu 20.04 boots to black screen on Lenovo Ideapad L340-17API when in battery mode
FWIW, I am running xubuntu 20.04.1 on a Lenovo e495 with Ryzen 7 and Vega 8. Based on discussions like this I opted to install the 5.6 OEM kernel from the standard repositories for some tests. I have not had any issues in this context since then and plan to stick with it. It works standalone, on battery as well as connected to a usb3 dock running 2 additional monitors. -- 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/1870971 Title: [amdgpu] (X)ubuntu 20.04 boots to black screen on Lenovo Ideapad L340-17API when in battery mode Status in linux package in Ubuntu: Confirmed Status in vlc package in Ubuntu: Invalid Bug description: Freshly installed Xubuntu 20.04 shows black screen instead of login screen upon boot on Lenovo Ideapad L340-17API. It is not possible to chvt to text terminal when boot is stuck on black screen. Booting with 'nomodeset' kernel option works properly but is not an option (e.g. screen brightness is not adjustable in this case). Another workaround is to ssh to laptop and run systemctl restart display-manager.service. After 5-10 seconds upon executing this command perfectly working login screen appears. Check dmesg. There is apparently related messages from amdgpu driver: ... апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_crtc_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_crtc_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_crtc_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_crtc_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_crtc_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_crtc_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_crtc_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_crtc_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_pflip_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_pflip_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_pflip_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_pflip_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_pflip_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_pflip_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_pflip_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_pflip_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_vupdate_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_vupdate_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_vupdate_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_vupdate_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_vupdate_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_vupdate_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_vupdate_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_vupdate_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm] recover vram bo from shadow start апр 05 20:46:45 kernel: [drm] recover vram bo from shadow done апр 05 20:46:45 kernel: [drm] Skip scheduling IBs! апр 05 20:46:45 kernel: [ cut here ] апр 05 20:46:45 kernel: WARNING: CPU: 3 PID: 793 at include/linux/dma-fence.h:533 drm_sched_resubmit_jobs+0x152/0x160 [gpu_sched] апр 05 20:46:45 kernel: Modules linked in: cmac algif_hash algif_skcipher af_alg bnep zram nls_iso8859_1 snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi snd_hda_intel snd_intel_nhlt snd_hda_codec > апр 05 20:46:45 kernel: CPU: 3 PID: 793 Comm: kworker/3:4 Tainted: G OE 5.4.0-21-generic #25-Ubuntu апр 05 20:46:45 kernel: Hardware name: LENOVO 81LY/LNVNB161216, BIOS ARCN32WW 07/11/2019 апр 05 20:46:45 kernel: Workqueue: events drm_sched_job_timedout [gpu_sched] апр 05 20:46:45 kernel: RIP: 0010:drm_sched_resubmit_jobs+0x152/0x160 [gpu_sched] апр 05 20:46:45 kernel: Code: 41 5c 41 5d 41 5e 41 5f 5d c3 49 8b 46 10 31 c9 48 c7 80 80 00 00 00 00 00 00 00 49 8b 7f 70 31 c0 83 e7 01 74 04 0f 0b eb bf <0f> 0b eb c7 0f 0b eb 8b 66 0f 1f 44 00 00 0f 1f 44 00 00 83 7f 4c апр 05 20:46:45 kernel: RSP: 0018:a4dc806d7d28 EFLAGS: 00010246 апр 05 20:46:45 kernel: RAX: RBX: 0001 RCX: апр 05 20:46:45 kernel: RDX: 8cc9a6fc9180 RSI: 8cc9ac4609f8 RDI: апр 05 20:46:45 kernel: RBP: a4dc806d7d60 R08: 047a R09: 0004 апр 05 20:46:45 kernel: R10: R11: 0001 R12: 8cc9ac463c00 апр 05 20:46:45 kernel: R13: 8cc9a63c7980 R14: 8cc9ac460800 R15: 8cc9a6fc9140 апр 05 20:46:45 kernel: FS: () GS:8cc9b88c() knlGS: апр 05 20:46:45 kernel: CS: 0010 DS: ES: CR0: 80050033 апр 05 20:46:45 kernel: CR2: 7f275ff6c000 CR3: 0001af148000 CR4: 003406e0 апр 05 20:46:45
[Kernel-packages] [Bug 1906107] Re: "unexpectedly disconnected from host boot status daemon" under high memory load
Not sure how, is there any guide ? -- 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/1906107 Title: "unexpectedly disconnected from host boot status daemon" under high memory load Status in linux package in Ubuntu: Confirmed Bug description: The hardware is Dell XPS13 9343, I'm using FDE with sepreate boot and EFI and NVMe disk. Under high memory load, usually when launching additional window my display goes blank, WiFi connection is lost, I can only reboot and Ctrl+alt+Fn When I do the second I'm getting following message: "unexpectedly disconnected from host boot status daemon" under high memory load Volume-Group 'ubuntu-vg' not found' [...] Please unlock disk nvme0n1op3_crypt: " Despite I enter correct password it doesn't work, seems like it lost connection with NVMe drive at all ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-124-generic 4.15.0-124.127 ProcVersionSignature: Ubuntu 4.15.0-124.127-generic 4.15.18 Uname: Linux 4.15.0-124-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: nusch 10223 F pulseaudio /dev/snd/pcmC0D3p: nusch 10223 F...m pulseaudio /dev/snd/controlC0: nusch 10223 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Nov 28 14:01:20 2020 HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1 InstallationDate: Installed on 2015-05-08 (2031 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. XPS 13 9343 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-124-generic root=/dev/mapper/ubuntu--vg-root ro crashkernel=384M-:128M quiet splash log_buf_len=1M crashkernel=512M-:192M vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-124-generic N/A linux-backports-modules-4.15.0-124-generic N/A linux-firmware 1.173.19 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-08-26 (824 days ago) dmi.bios.date: 06/06/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: A20 dmi.board.name: 09K8G1 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA20:bd06/06/2019:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn09K8G1:rvrA02:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9343 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1906107/+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 1849369] Re: Ubuntu 19.10 ARM64 kernel has KVM disabled by default
*** This bug is a duplicate of bug 1783961 *** https://bugs.launchpad.net/bugs/1783961 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/1849369 Title: Ubuntu 19.10 ARM64 kernel has KVM disabled by default Status in linux-raspi2 package in Ubuntu: Confirmed Bug description: Using the official Ubuntu 19.10 arm64 image, http://cdimage.ubuntu.com/ubuntu/releases/19.10/release/ubuntu-19.10 -preinstalled-server-arm64+raspi3.img.xz, with the 5.3.x Linux kernel has KVM/VIRTUALIZATION disabled by default and therefore /dev/kvm acceleration is not available on installations on newer Raspberry Pi 4 (for example) which has a supported processor (armv8) by KVM (https://www.linux-kvm.org/page/Processor_support#ARM:). I'm able to compile the kernel manually with the options enabled in the kernel config (http://dl.rohityadav.cloud/cloudstack- rpi/kernel-19.10/) and further verify that it works well in deploying ARM64 VMs (http://dl.rohityadav.cloud/cloudstack-rpi/template/). I went a bit further to deploy an Apache CloudStack based IaaS deployment and verify that it works as well. Having KVM enabled arm64 devices would enable testing and misc use-cases on newer boards such as the Raspberry Pi 4 (4 GB RAM). Can the Ubuntu kernel team advise why KVM is not enabled in the kernel by default, and if this will change in future? Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1849369/+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 1906542] Re: echo 1 >> /sys/module/zfs/parameters/zfs_max_missing_tvds says premission error, unable to reapair lost zfs pool data
device_removal only works if you can import the pool normally. That is what you should have used after you accidentally added the second disk as another top-level vdev. Whatever you have done in the interim, though, has resulted in the second device showing as FAULTED. Unless you can fix that, device_removal is not an option. I had hoped that you just had the second drive unplugged or something. But since the import is showing "corrupted data" for the second drive, that's probably not what happened. This works for me on Ubuntu 20.04: echo 1 >> /sys/module/zfs/parameters/zfs_max_missing_tvds That setting does not exist on Ubuntu 18.04 (which you are running), so I get the same "Permission denied" error (because bash is trying to create that file, which you cannot do). I now see this is an rpool. Is your plan to reinstall? With 18.04 or 20.04? If 18.04, then: 1. Download the 20.04.1 live image. Write it to a USB disk and boot into that. 2. In the live environment, install the ZFS tools: sudo apt install zfsutils-linux 3. echo 1 >> /sys/module/zfs/parameters/zfs_max_missing_tvds 4. mkdir /old 5. Import the old pool renaming it to rpool-old and mount filesystems: zpool import -o readonly=on -N -R /old rpool rpool-old zfs mount rpool-old/ROOT/ubuntu zfs mount -a 6. Confirm you can access your data. Take another backup, if desired. If you don't have space to back it up besides the new/second disk, then read on... 7. Follow the 18.04 Root-on-ZFS HOWTO using (only) the second disk. Be very careful not to partition or zpool create the disk with your data!!! For example, partition the second disk for the mirror scenario. But obviously you can't do zpool create with "mirror" because you have only one disk. 8. Once the new system is installed (i.e. after step 6.2), but before rebooting, copy data from /old to /mnt as needed. 9. Shut down. Disconnect the old disk. Boot up again. 9. Continue the install as normal. 10. When you are certain that everything is good and that new disk is working properly (maybe do a scrub) and you have all your data, then you can connect the old disk and do the zpool attach (ATTACH, not add) to attach the old disk to the new pool as a mirror If 20.04, then I'd do this instead: 1. Unplug the disk with your data. 2. Follow the 20.04 Root-on-ZFS HOWTO using only the second disk. Follow the steps as if you were mirroring (since that is the ultimate goal) where possible. For example, partition the second disk for the mirror scenario. But obviously you can't do zpool create with "mirror" because you have only one disk. 3. Once the new, 20.04 system is working on the second disk and booting normally, connect the other, old drive. (This assumes you can connect it while the system is running.) 4. echo 1 >> /sys/module/zfs/parameters/zfs_max_missing_tvds 5. Import the old pool using its GUID renaming it to rpool-old and mount filesystems: zpool import -o readonly -N -R /mnt 5077426391014001687 rpool-old zfs mount rpool-old/ROOT/ubuntu zfs mount -a 6. Copy over data. 7. zpool export rpool-old 8. When you are certain that everything is good and that new disk is working properly (maybe do a scrub) and you have all your data, then you can do the zpool attach (ATTACH, not add) to attach the old disk to the new pool as a mirror. -- 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/1906542 Title: echo 1 >> /sys/module/zfs/parameters/zfs_max_missing_tvds says premission error, unable to reapair lost zfs pool data Status in zfs-linux package in Ubuntu: New Bug description: root@jonipekka-desktop:~# echo 1 >> /sys/module/zfs/parameters/zfs_max_missing_tvds -bash: /sys/module/zfs/parameters/zfs_max_missing_tvds: Permission denied root@jonipekka-desktop:~# https://www.delphix.com/blog/openzfs-pool-import-recovery Import with missing top level vdevs The changes to the pool configuration logic have enabled another great improvement: the ability to import a pool with missing or faulted top- level vdevs. Since some data will almost certainly be missing, a pool with missing top-level vdevs can only be imported read-only, and the failmode is set to “continue” (failmode=continue means that when encountering errors the pool will continue running, as opposed to being suspended or panicking). To enable this feature, we’ve added a new global variable: zfs_max_missing_tvds, which defines how many missing top level vdevs we can tolerate before marking a pool as unopenable. It is set to 0 by default, and should be changed to other values only temporarily, while performing an extreme pool recovery. Here as an example we create a pool with two vdevs and write some data to a first dataset; we then add a third vdev and write some data to a second dataset. Finally we physically remove the new vdev (simulating, for instance,
[Kernel-packages] [Bug 1906716] 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/1906716 Title: Stack trace booting 20.04 LTS server on system with dual Xeon Gold 6240 CPUs Status in linux package in Ubuntu: Confirmed Bug description: I noticed this in syslog while investigating an unrelated issue today. I have Focal installed on a Fujitsu RX2530 M5 server with two Xeon Gold 6240 18c/36t CPUs installed. Every reboot results in the following MSR stack trace: Dec 3 17:34:31 nabbit kernel: [0.002463] smpboot: CPU 18 Converting physical 0 to logical die 1 Dec 3 17:34:31 nabbit kernel: [0.002463] unchecked MSR access error: WRMSR to 0x10f (tried to write 0x) at rIP: 0x81c78b04 (native_write_msr+0x4/0x30) Dec 3 17:34:31 nabbit kernel: [0.002463] Call Trace: Dec 3 17:34:31 nabbit kernel: [0.002463] ? intel_pmu_cpu_starting+0x87/0x270 Dec 3 17:34:31 nabbit kernel: [0.002463] ? x86_pmu_dead_cpu+0x30/0x30 Dec 3 17:34:31 nabbit kernel: [0.002463] x86_pmu_starting_cpu+0x1a/0x30 Dec 3 17:34:31 nabbit kernel: [0.002463] cpuhp_invoke_callback+0x9b/0x580 Dec 3 17:34:31 nabbit kernel: [0.002463] notify_cpu_starting+0x66/0x80 Dec 3 17:34:31 nabbit kernel: [0.002463] start_secondary+0xaa/0x1c0 Dec 3 17:34:31 nabbit kernel: [0.002463] secondary_startup_64+0xa4/0xb0 Dec 3 17:34:31 nabbit kernel: [0.498575] #19 #20 #21 #22 #23 #24 #25 #26 #27 #28 #29 #30 #31 #32 #33 #34 #35 Dec 3 17:34:31 nabbit kernel: [0.618576] node #0, CPUs: #36 Dec 3 17:34:31 nabbit kernel: [0.623308] MDS CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html for more details. Dec 3 17:34:31 nabbit kernel: [0.623308] TAA CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/tsx_async_abort.html for more details. Dec 3 17:34:31 nabbit kernel: [0.623308] #37 #38 #39 #40 #41 #42 #43 #44 #45 #46 #47 #48 #49 #50 #51 #52 #53 Dec 3 17:34:31 nabbit kernel: [0.672450] node #1, CPUs: #54 #55 #56 #57 #58 #59 #60 #61 #62 #63 #64 #65 #66 #67 #68 #69 #70 #71Dec 3 17:34:31 nabbit kernel: [0.729432] smp: Brought up 2 nodes, 72 CPUs Dec 3 17:34:31 nabbit kernel: [0.729432] smpboot: Max logical packages: 2 Dec 3 17:34:31 nabbit kernel: [0.729432] smpboot: Total of 72 processors activated (374479.29 BogoMIPS) it doesn't seem to be catastrophic, but is troubling to find this in the logs. On a different FJ server (RX2540 M5) with 2x Xeon Gold 6242 cpus (16c/32T) This trace is not present, so this could indicate something with this particular machine, or this particular CPU model. Here is the smp boot from the non-failing machine: Dec 2 16:02:56 polari kernel: [1.522346] smpboot: CPU0: Intel(R) Xeon(R) Gold 6242 CPU @ 2.80GHz (family: 0x6, model: 0x55, stepping: 0x5) Dec 2 16:02:56 polari kernel: [1.522575] Performance Events: PEBS fmt3+, Skylake events, 32-deep LBR, full-width counters, Intel PMU driver. Dec 2 16:02:56 polari kernel: [1.522584] ... version:4 Dec 2 16:02:56 polari kernel: [1.522585] ... bit width: 48 Dec 2 16:02:56 polari kernel: [1.522587] ... generic registers: 4 Dec 2 16:02:56 polari kernel: [1.522588] ... value mask: Dec 2 16:02:56 polari kernel: [1.522589] ... max period: 7fff Dec 2 16:02:56 polari kernel: [1.522591] ... fixed-purpose events: 3 Dec 2 16:02:56 polari kernel: [1.522592] ... event mask: 0007000f Dec 2 16:02:56 polari kernel: [1.522665] rcu: Hierarchical SRCU implementation. Dec 2 16:02:56 polari kernel: [1.524965] NMI watchdog: Enabled. Permanently consumes one hw-PMU counter. Dec 2 16:02:56 polari kernel: [1.525875] smp: Bringing up secondary CPUs ... Dec 2 16:02:56 polari kernel: [1.525990] x86: Booting SMP configuration: Dec 2 16:02:56 polari kernel: [1.525992] node #0, CPUs:#1 #2 #3 Dec 2 16:02:56 polari kernel: [1.533485] node #1, CPUs:#4 #5 #6 #7 Dec 2 16:02:56 polari kernel: [1.543960] node #0, CPUs:#8 #9 #10 #11 Dec 2 16:02:56 polari kernel: [1.553544] node #1, CPUs: #12 #13 #14 #15 Dec 2 16:02:56 polari kernel: [1.564701] node #2, CPUs: #16 Dec 2 16:02:56 polari kernel: [0.002176] smpboot: CPU 16 Converting physical 0 to logical die 1 Dec 2 16:02:56 polari kernel: [1.651254] #17 #18 #19 Dec 2 16:02:56 polari kernel: [1.659278] node #3, CPUs: #20 #21 #22 #23 Dec 2 16:02:56 polari
[Kernel-packages] [Bug 1872401] Re: vmx_nm_test in ubuntu_kvm_unit_tests interrupted on X-oracle-4.15 / B-oracle-4.15 / X-KVM / B-KVM
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-signed-oracle (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: linux (Ubuntu) Status: New => Invalid ** Description changed: + [Impact] + When running kvm-unit-tests under a guest, it will be paused, requiring a + reset. When running the same test on a host (vmx_nm_test), it will fail. + + [Test case] + Grab kvm-unit-tests, build it and run: + + TESTNAME=vmx TIMEOUT=90s ACCEL= ./x86/run x86/vmx.flat -smp 1 -cpu + host,+vmx -append "vmx_nm_test" + + If done inside a guest, when the host runs the bionic 4.15 kernel, the guest + will pause. + + [Potential regressions] + Nested KVM could stop working. Floating point could stop working on KVM + guests, though the code that relied on this was already removed from + Bionic. + + + -- + + This issue was first spotted on Mar.16 [1] The ubuntu_kvm_unit_tests will be interrupted on X-oracle-4.15 on both VM.Standard2.1 and VM.Standard2.16, this is not a regression since it can be reproduced with 4.15.0-1031-oracle #34~16.04.1: Running '/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/tests/vmx_nm_test' BUILD_HEAD=4671e4ba timeout -k 1s --foreground 30 /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.da3iFrsCzC -smp 1 -cpu host,+vmx -append vmx_nm_test # -initrd /tmp/tmp.h2DFw8L0AF enabling apic paging enabled cr0 = 80010011 cr3 = 477000 cr4 = 20 Test suite: vmx_nm_test client_loop: send disconnect: Broken pipe (node disconnected here) Before the test started, this can be found in syslog: Apr 13 06:26:25 selfprovisioned-phlin-kvm-unit kernel: [ 1073.529005] L1TF CPU bug present and SMT on, data leak possible. See CVE-2018-3646 and https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/l1tf.html for details. After that, noting was printed and node disconnected. If you try to run this case manually, it will stop at: # ./vmx_nm_test BUILD_HEAD=4671e4ba ready!!! timeout -k 1s --foreground 30 /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.ZcGrnXu6se -smp 1 -cpu host,+vmx -append vmx_nm_test # -initrd /tmp/tmp.ADjEOAcRKM enabling ap (stopped here, even the "enabling apic" string was not printed) It looks like this is a new test case added since the cycle of 4.15.0-1037.41~16.04.1-oracle [1] https://bugs.launchpad.net/ubuntu-kernel- tests/+bug/1867623/comments/2 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.15.0-1031-oracle 4.15.0-1031.34~16.04.1 ProcVersionSignature: User Name 4.15.0-1031.34~16.04.1-oracle 4.15.18 Uname: Linux 4.15.0-1031-oracle x86_64 ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 Date: Mon Apr 13 05:18:03 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-oracle UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1872401 Title: vmx_nm_test in ubuntu_kvm_unit_tests interrupted on X-oracle-4.15 / B-oracle-4.15 / X-KVM / B-KVM Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Invalid Status in linux-signed-oracle package in Ubuntu: New Status in linux source package in Bionic: In Progress Status in linux-signed-oracle source package in Bionic: New Bug description: [Impact] When running kvm-unit-tests under a guest, it will be paused, requiring a reset. When running the same test on a host (vmx_nm_test), it will fail. [Test case] Grab kvm-unit-tests, build it and run: TESTNAME=vmx TIMEOUT=90s ACCEL= ./x86/run x86/vmx.flat -smp 1 -cpu host,+vmx -append "vmx_nm_test" If done inside a guest, when the host runs the bionic 4.15 kernel, the guest will pause. [Potential regressions] Nested KVM could stop working. Floating point could stop working on KVM guests, though the code that relied on this was already removed from Bionic. -- This issue was first spotted on Mar.16 [1] The ubuntu_kvm_unit_tests will be interrupted on X-oracle-4.15 on both VM.Standard2.1 and VM.Standard2.16, this is not a
[Kernel-packages] [Bug 1906716] [NEW] Stack trace booting 20.04 LTS server on system with dual Xeon Gold 6240 CPUs
Public bug reported: I noticed this in syslog while investigating an unrelated issue today. I have Focal installed on a Fujitsu RX2530 M5 server with two Xeon Gold 6240 18c/36t CPUs installed. Every reboot results in the following MSR stack trace: Dec 3 17:34:31 nabbit kernel: [0.002463] smpboot: CPU 18 Converting physical 0 to logical die 1 Dec 3 17:34:31 nabbit kernel: [0.002463] unchecked MSR access error: WRMSR to 0x10f (tried to write 0x) at rIP: 0x81c78b04 (native_write_msr+0x4/0x30) Dec 3 17:34:31 nabbit kernel: [0.002463] Call Trace: Dec 3 17:34:31 nabbit kernel: [0.002463] ? intel_pmu_cpu_starting+0x87/0x270 Dec 3 17:34:31 nabbit kernel: [0.002463] ? x86_pmu_dead_cpu+0x30/0x30 Dec 3 17:34:31 nabbit kernel: [0.002463] x86_pmu_starting_cpu+0x1a/0x30 Dec 3 17:34:31 nabbit kernel: [0.002463] cpuhp_invoke_callback+0x9b/0x580 Dec 3 17:34:31 nabbit kernel: [0.002463] notify_cpu_starting+0x66/0x80 Dec 3 17:34:31 nabbit kernel: [0.002463] start_secondary+0xaa/0x1c0 Dec 3 17:34:31 nabbit kernel: [0.002463] secondary_startup_64+0xa4/0xb0 Dec 3 17:34:31 nabbit kernel: [0.498575] #19 #20 #21 #22 #23 #24 #25 #26 #27 #28 #29 #30 #31 #32 #33 #34 #35 Dec 3 17:34:31 nabbit kernel: [0.618576] node #0, CPUs: #36 Dec 3 17:34:31 nabbit kernel: [0.623308] MDS CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html for more details. Dec 3 17:34:31 nabbit kernel: [0.623308] TAA CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/tsx_async_abort.html for more details. Dec 3 17:34:31 nabbit kernel: [0.623308] #37 #38 #39 #40 #41 #42 #43 #44 #45 #46 #47 #48 #49 #50 #51 #52 #53 Dec 3 17:34:31 nabbit kernel: [0.672450] node #1, CPUs: #54 #55 #56 #57 #58 #59 #60 #61 #62 #63 #64 #65 #66 #67 #68 #69 #70 #71Dec 3 17:34:31 nabbit kernel: [0.729432] smp: Brought up 2 nodes, 72 CPUs Dec 3 17:34:31 nabbit kernel: [0.729432] smpboot: Max logical packages: 2 Dec 3 17:34:31 nabbit kernel: [0.729432] smpboot: Total of 72 processors activated (374479.29 BogoMIPS) it doesn't seem to be catastrophic, but is troubling to find this in the logs. On a different FJ server (RX2540 M5) with 2x Xeon Gold 6242 cpus (16c/32T) This trace is not present, so this could indicate something with this particular machine, or this particular CPU model. Here is the smp boot from the non-failing machine: Dec 2 16:02:56 polari kernel: [1.522346] smpboot: CPU0: Intel(R) Xeon(R) Gold 6242 CPU @ 2.80GHz (family: 0x6, model: 0x55, stepping: 0x5) Dec 2 16:02:56 polari kernel: [1.522575] Performance Events: PEBS fmt3+, Skylake events, 32-deep LBR, full-width counters, Intel PMU driver. Dec 2 16:02:56 polari kernel: [1.522584] ... version:4 Dec 2 16:02:56 polari kernel: [1.522585] ... bit width: 48 Dec 2 16:02:56 polari kernel: [1.522587] ... generic registers: 4 Dec 2 16:02:56 polari kernel: [1.522588] ... value mask: Dec 2 16:02:56 polari kernel: [1.522589] ... max period: 7fff Dec 2 16:02:56 polari kernel: [1.522591] ... fixed-purpose events: 3 Dec 2 16:02:56 polari kernel: [1.522592] ... event mask: 0007000f Dec 2 16:02:56 polari kernel: [1.522665] rcu: Hierarchical SRCU implementation. Dec 2 16:02:56 polari kernel: [1.524965] NMI watchdog: Enabled. Permanently consumes one hw-PMU counter. Dec 2 16:02:56 polari kernel: [1.525875] smp: Bringing up secondary CPUs ... Dec 2 16:02:56 polari kernel: [1.525990] x86: Booting SMP configuration: Dec 2 16:02:56 polari kernel: [1.525992] node #0, CPUs:#1 #2 #3 Dec 2 16:02:56 polari kernel: [1.533485] node #1, CPUs:#4 #5 #6 #7 Dec 2 16:02:56 polari kernel: [1.543960] node #0, CPUs:#8 #9 #10 #11 Dec 2 16:02:56 polari kernel: [1.553544] node #1, CPUs: #12 #13 #14 #15 Dec 2 16:02:56 polari kernel: [1.564701] node #2, CPUs: #16 Dec 2 16:02:56 polari kernel: [0.002176] smpboot: CPU 16 Converting physical 0 to logical die 1 Dec 2 16:02:56 polari kernel: [1.651254] #17 #18 #19 Dec 2 16:02:56 polari kernel: [1.659278] node #3, CPUs: #20 #21 #22 #23 Dec 2 16:02:56 polari kernel: [1.669669] node #2, CPUs: #24 #25 #26 #27 Dec 2 16:02:56 polari kernel: [1.680637] node #3, CPUs: #28 #29 #30 #31 Dec 2 16:02:56 polari kernel: [1.691394] node #0, CPUs: #32 Dec 2 16:02:56 polari kernel: [1.693845] MDS CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html for more details. Dec 2 16:02:56 polari kernel: [1.693845] TAA CPU bug present and SMT on, data
[Kernel-packages] [Bug 1905574] Re: Ubuntu 20.10 four needed fixes to 'Add driver for Mellanox Connect-IB adapters'
** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Jeff Lane (bladernr) -- 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/1905574 Title: Ubuntu 20.10 four needed fixes to 'Add driver for Mellanox Connect-IB adapters' Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Bug description: [Impact] commit d43b7007dbd1 net/mlx5: Fix a race when moving command interface to events mode from upstream v5.7-rc1 (and in groovy) fixes e126ba97dba9 mlx5: Add driver for Mellanox Connect-IB adapters this fix should come with four more patches from v5.9. 410bd754cd73 net/mlx5: Add retry mechanism to the command entry index allocation 1d5558b1f0de net/mlx5: poll cmd EQ in case of command timeout 50b2412b7e78 net/mlx5: Avoid possible free of command entry while timeout comp handler 432161ea26d6 net/mlx5: Fix a race when moving command interface to polling mode all four patches are applied cleanly on groovy tree and we ask to pull them into groovy. please also see this discussion https://www.spinics.net/lists/stable/msg428620.html Thank's To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1905574/+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 1906705] 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/1906705 Title: The newest ubuntu-kernel 5.4.0-56-generic does not boot on my machine. Status in linux package in Ubuntu: Confirmed Bug description: The newest ubuntu-kernel 5.4.0-56-generic does not boot on my machine. All older Kubuntu 20.04LTS kernel booted without problems Ryzen 3950X CPU, Asus B450 Booard, Asus 2070super GPU sudo lspci -vvnn > lspci-vvnn.log see attachment ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-54-generic 5.4.0-54.60 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jseger 2001 F pulseaudio /dev/snd/pcmC0D7p: jseger 2001 F...m pulseaudio /dev/snd/controlC1: jseger 2001 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Thu Dec 3 20:06:40 2020 InstallationDate: Installed on 2020-04-16 (231 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: System manufacturer System Product Name ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-generic root=/dev/mapper/vgkubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-54-generic N/A linux-backports-modules-5.4.0-54-generic N/A linux-firmware1.187.4 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-05-10 (206 days ago) dmi.bios.date: 06/17/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3103 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B450-I GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3103:bd06/17/2020:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB450-IGAMING:rvrRev1.xx: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/1906705/+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 1906705] [NEW] The newest ubuntu-kernel 5.4.0-56-generic does not boot on my machine.
Public bug reported: The newest ubuntu-kernel 5.4.0-56-generic does not boot on my machine. All older Kubuntu 20.04LTS kernel booted without problems Ryzen 3950X CPU, Asus B450 Booard, Asus 2070super GPU sudo lspci -vvnn > lspci-vvnn.log see attachment ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-54-generic 5.4.0-54.60 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jseger 2001 F pulseaudio /dev/snd/pcmC0D7p: jseger 2001 F...m pulseaudio /dev/snd/controlC1: jseger 2001 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Thu Dec 3 20:06:40 2020 InstallationDate: Installed on 2020-04-16 (231 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: System manufacturer System Product Name ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-generic root=/dev/mapper/vgkubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-54-generic N/A linux-backports-modules-5.4.0-54-generic N/A linux-firmware1.187.4 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-05-10 (206 days ago) dmi.bios.date: 06/17/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3103 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B450-I GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3103:bd06/17/2020:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB450-IGAMING:rvrRev1.xx: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 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "lspci-vvnn.log" https://bugs.launchpad.net/bugs/1906705/+attachment/5440684/+files/lspci-vvnn.log -- 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/1906705 Title: The newest ubuntu-kernel 5.4.0-56-generic does not boot on my machine. Status in linux package in Ubuntu: New Bug description: The newest ubuntu-kernel 5.4.0-56-generic does not boot on my machine. All older Kubuntu 20.04LTS kernel booted without problems Ryzen 3950X CPU, Asus B450 Booard, Asus 2070super GPU sudo lspci -vvnn > lspci-vvnn.log see attachment ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-54-generic 5.4.0-54.60 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jseger 2001 F pulseaudio /dev/snd/pcmC0D7p: jseger 2001 F...m pulseaudio /dev/snd/controlC1: jseger 2001 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Thu Dec 3 20:06:40 2020 InstallationDate: Installed on 2020-04-16 (231 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: System manufacturer System Product Name ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-generic root=/dev/mapper/vgkubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-54-generic N/A linux-backports-modules-5.4.0-54-generic N/A linux-firmware1.187.4 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-05-10 (206 days ago) dmi.bios.date: 06/17/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3103 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B450-I GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3103:bd06/17/2020:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB450-IGAMING:rvrRev1.xx: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
[Kernel-packages] [Bug 1906542] Re: echo 1 >> /sys/module/zfs/parameters/zfs_max_missing_tvds says premission error, unable to reapair lost zfs pool data
root@jonipekka-desktop:~# zpool import pool: rpool id: 5077426391014001687 state: UNAVAIL status: One or more devices are faulted. action: The pool cannot be imported due to damaged devices or data. config: rpoolUNAVAIL insufficient replicas ata-WDC_WD4005FZBX-00K5WB0_V6GAE1PR-part1 ONLINE ata-WDC_WD4005FZBX-00K5WB0_VBGDM25F-part4 FAULTED corrupted data root@jonipekka-desktop:~# -- 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/1906542 Title: echo 1 >> /sys/module/zfs/parameters/zfs_max_missing_tvds says premission error, unable to reapair lost zfs pool data Status in zfs-linux package in Ubuntu: New Bug description: root@jonipekka-desktop:~# echo 1 >> /sys/module/zfs/parameters/zfs_max_missing_tvds -bash: /sys/module/zfs/parameters/zfs_max_missing_tvds: Permission denied root@jonipekka-desktop:~# https://www.delphix.com/blog/openzfs-pool-import-recovery Import with missing top level vdevs The changes to the pool configuration logic have enabled another great improvement: the ability to import a pool with missing or faulted top- level vdevs. Since some data will almost certainly be missing, a pool with missing top-level vdevs can only be imported read-only, and the failmode is set to “continue” (failmode=continue means that when encountering errors the pool will continue running, as opposed to being suspended or panicking). To enable this feature, we’ve added a new global variable: zfs_max_missing_tvds, which defines how many missing top level vdevs we can tolerate before marking a pool as unopenable. It is set to 0 by default, and should be changed to other values only temporarily, while performing an extreme pool recovery. Here as an example we create a pool with two vdevs and write some data to a first dataset; we then add a third vdev and write some data to a second dataset. Finally we physically remove the new vdev (simulating, for instance, a device failure) and try to import the pool using the new feature. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: zfsutils-linux 0.7.5-1ubuntu16.10 ProcVersionSignature: Ubuntu 4.15.0-126.129-generic 4.15.18 Uname: Linux 4.15.0-126-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.20 Architecture: amd64 Date: Wed Dec 2 18:39:58 2020 InstallationDate: Installed on 2020-12-02 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: zfs-linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1906542/+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 1906542] Re: echo 1 >> /sys/module/zfs/parameters/zfs_max_missing_tvds says premission error, unable to reapair lost zfs pool data
Do you mean this feature which is comi ng,... when ? https://github.com/openzfs/openzfs/pull/251 -- 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/1906542 Title: echo 1 >> /sys/module/zfs/parameters/zfs_max_missing_tvds says premission error, unable to reapair lost zfs pool data Status in zfs-linux package in Ubuntu: New Bug description: root@jonipekka-desktop:~# echo 1 >> /sys/module/zfs/parameters/zfs_max_missing_tvds -bash: /sys/module/zfs/parameters/zfs_max_missing_tvds: Permission denied root@jonipekka-desktop:~# https://www.delphix.com/blog/openzfs-pool-import-recovery Import with missing top level vdevs The changes to the pool configuration logic have enabled another great improvement: the ability to import a pool with missing or faulted top- level vdevs. Since some data will almost certainly be missing, a pool with missing top-level vdevs can only be imported read-only, and the failmode is set to “continue” (failmode=continue means that when encountering errors the pool will continue running, as opposed to being suspended or panicking). To enable this feature, we’ve added a new global variable: zfs_max_missing_tvds, which defines how many missing top level vdevs we can tolerate before marking a pool as unopenable. It is set to 0 by default, and should be changed to other values only temporarily, while performing an extreme pool recovery. Here as an example we create a pool with two vdevs and write some data to a first dataset; we then add a third vdev and write some data to a second dataset. Finally we physically remove the new vdev (simulating, for instance, a device failure) and try to import the pool using the new feature. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: zfsutils-linux 0.7.5-1ubuntu16.10 ProcVersionSignature: Ubuntu 4.15.0-126.129-generic 4.15.18 Uname: Linux 4.15.0-126-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.20 Architecture: amd64 Date: Wed Dec 2 18:39:58 2020 InstallationDate: Installed on 2020-12-02 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: zfs-linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1906542/+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 1906542] Re: echo 1 >> /sys/module/zfs/parameters/zfs_max_missing_tvds says premission error, unable to reapair lost zfs pool data
new device_removal feature ,... where it is ? It might work. -- 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/1906542 Title: echo 1 >> /sys/module/zfs/parameters/zfs_max_missing_tvds says premission error, unable to reapair lost zfs pool data Status in zfs-linux package in Ubuntu: New Bug description: root@jonipekka-desktop:~# echo 1 >> /sys/module/zfs/parameters/zfs_max_missing_tvds -bash: /sys/module/zfs/parameters/zfs_max_missing_tvds: Permission denied root@jonipekka-desktop:~# https://www.delphix.com/blog/openzfs-pool-import-recovery Import with missing top level vdevs The changes to the pool configuration logic have enabled another great improvement: the ability to import a pool with missing or faulted top- level vdevs. Since some data will almost certainly be missing, a pool with missing top-level vdevs can only be imported read-only, and the failmode is set to “continue” (failmode=continue means that when encountering errors the pool will continue running, as opposed to being suspended or panicking). To enable this feature, we’ve added a new global variable: zfs_max_missing_tvds, which defines how many missing top level vdevs we can tolerate before marking a pool as unopenable. It is set to 0 by default, and should be changed to other values only temporarily, while performing an extreme pool recovery. Here as an example we create a pool with two vdevs and write some data to a first dataset; we then add a third vdev and write some data to a second dataset. Finally we physically remove the new vdev (simulating, for instance, a device failure) and try to import the pool using the new feature. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: zfsutils-linux 0.7.5-1ubuntu16.10 ProcVersionSignature: Ubuntu 4.15.0-126.129-generic 4.15.18 Uname: Linux 4.15.0-126-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.20 Architecture: amd64 Date: Wed Dec 2 18:39:58 2020 InstallationDate: Installed on 2020-12-02 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: zfs-linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1906542/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1906542] Re: echo 1 >> /sys/module/zfs/parameters/zfs_max_missing_tvds says premission error, unable to reapair lost zfs pool data
I tried remove command before taking it out, i was in beleaf system will then correct problem, So basically secon disk has no data and not corrupted,... I need that option due import readonly -f pool -d dose not fix problem so i can then copy disk. I have only essential's at backup ,... so there is many files i realy need,... joni Richard Laager kirjoitti 3.12.2020 klo 18.38: > Why is the second disk missing? If you accidentally added it and ended > up with a striped pool, as long as both disks are connected, you can > import the pool normally. Then use the new device_removal feature to > remove the new disk from the pool. > > If you've done something crazy like pulled the disk and wiped it, then > yeah, you're going to need to figure out how to import the pool read- > only. I don't have any advice on that piece. > -- joni -- 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/1906542 Title: echo 1 >> /sys/module/zfs/parameters/zfs_max_missing_tvds says premission error, unable to reapair lost zfs pool data Status in zfs-linux package in Ubuntu: New Bug description: root@jonipekka-desktop:~# echo 1 >> /sys/module/zfs/parameters/zfs_max_missing_tvds -bash: /sys/module/zfs/parameters/zfs_max_missing_tvds: Permission denied root@jonipekka-desktop:~# https://www.delphix.com/blog/openzfs-pool-import-recovery Import with missing top level vdevs The changes to the pool configuration logic have enabled another great improvement: the ability to import a pool with missing or faulted top- level vdevs. Since some data will almost certainly be missing, a pool with missing top-level vdevs can only be imported read-only, and the failmode is set to “continue” (failmode=continue means that when encountering errors the pool will continue running, as opposed to being suspended or panicking). To enable this feature, we’ve added a new global variable: zfs_max_missing_tvds, which defines how many missing top level vdevs we can tolerate before marking a pool as unopenable. It is set to 0 by default, and should be changed to other values only temporarily, while performing an extreme pool recovery. Here as an example we create a pool with two vdevs and write some data to a first dataset; we then add a third vdev and write some data to a second dataset. Finally we physically remove the new vdev (simulating, for instance, a device failure) and try to import the pool using the new feature. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: zfsutils-linux 0.7.5-1ubuntu16.10 ProcVersionSignature: Ubuntu 4.15.0-126.129-generic 4.15.18 Uname: Linux 4.15.0-126-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.20 Architecture: amd64 Date: Wed Dec 2 18:39:58 2020 InstallationDate: Installed on 2020-12-02 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: zfs-linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1906542/+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 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
Perhaps the best hope is that Pipewire develops quickly and replaces Pulseaudio: https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/249 ** Bug watch added: gitlab.freedesktop.org/pipewire/pipewire/-/issues #249 https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/249 -- 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/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Triaged Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+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 1906698] Re: Xenial update: v4.4.245 upstream stable release
** Description changed: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v4.4.245 upstream stable release from git://git.kernel.org/ i2c: imx: Fix external abort on interrupt in exit paths xfs: catch inode allocation state mismatch corruption xfs: validate cached inodes are free when allocated powerpc/8xx: Always fault when _PAGE_ACCESSED is not set Input: sunkbd - avoid use-after-free in teardown paths mac80211: always wind down STA state KVM: x86: clflushopt should be treated as a no-op by emulation Linux 4.4.245 + UBUNTU: upstream stable to v4.4.245 -- 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/1906698 Title: Xenial update: v4.4.245 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: In Progress Bug description: 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: v4.4.245 upstream stable release from git://git.kernel.org/ i2c: imx: Fix external abort on interrupt in exit paths xfs: catch inode allocation state mismatch corruption xfs: validate cached inodes are free when allocated powerpc/8xx: Always fault when _PAGE_ACCESSED is not set Input: sunkbd - avoid use-after-free in teardown paths mac80211: always wind down STA state KVM: x86: clflushopt should be treated as a no-op by emulation Linux 4.4.245 UBUNTU: upstream stable to v4.4.245 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1906698/+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 1906700] Re: Xenial update: v4.4.246 upstream stable release
** Description changed: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v4.4.246 upstream stable release from git://git.kernel.org/ ah6: fix error return code in ah6_input() atm: nicstar: Unmap DMA on send error net: b44: fix error return code in b44_init_one() net: bridge: add missing counters to ndo_get_stats64 callback netlabel: fix our progress tracking in netlbl_unlabel_staticlist() netlabel: fix an uninitialized warning in netlbl_unlabel_staticlist() net/mlx4_core: Fix init_hca fields offset net: x25: Increase refcnt of "struct x25_neigh" in x25_rx_call_request qlcnic: fix error return code in qlcnic_83xx_restart_hw() sctp: change to hold/put transport for proto_unreach_timer net: usb: qmi_wwan: Set DTR quirk for MR400 net: Have netpoll bring-up DSA management interface pinctrl: rockchip: enable gpio pclk for rockchip_gpio_to_irq arm64: psci: Avoid printing in cpu_psci_cpu_die() MIPS: Fix BUILD_ROLLBACK_PROLOGUE for microMIPS Input: adxl34x - clean up a data type in adxl34x_probe() arm: dts: imx6qdl-udoo: fix rgmii phy-mode for ksz9031 phy ARM: dts: imx50-evk: Fix the chip select 1 IOMUX perf lock: Don't free "lock_seq_stat" if read_count isn't zero can: dev: can_restart(): post buffer from the right context can: peak_usb: fix potential integer overflow on shift of a int can: m_can: m_can_handle_state_change(): fix state change MIPS: Alchemy: Fix memleak in alchemy_clk_setup_cpu regulator: ti-abb: Fix array out of bound read access on the first transition libfs: fix error cast of negative value in simple_attr_write() ALSA: ctl: fix error path at adding user-defined element set ALSA: mixart: Fix mutex deadlock tty: serial: imx: keep console clocks always on efivarfs: fix memory leak in efivarfs_create() ext4: fix bogus warning in ext4_update_dx_flag() xtensa: disable preemption around cache alias management calls mac80211: minstrel: remove deferred sampling code mac80211: minstrel: fix tx status processing corner case mac80211: allow driver to prevent two stations w/ same address mac80211: free sta in sta_info_insert_finish() on errors s390/cpum_sf.c: fix file permission for cpum_sfb_size x86/microcode/intel: Check patch signature before saving microcode for early loading Linux 4.4.246 + UBUNTU: upstream stable to v4.4.246 -- 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/1906700 Title: Xenial update: v4.4.246 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: In Progress Bug description: 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: v4.4.246 upstream stable release from git://git.kernel.org/ ah6: fix error return code in ah6_input() atm: nicstar: Unmap DMA on send error net: b44: fix error return code in b44_init_one() net: bridge: add missing counters to ndo_get_stats64 callback netlabel: fix our progress tracking in netlbl_unlabel_staticlist() netlabel: fix an uninitialized warning in netlbl_unlabel_staticlist() net/mlx4_core: Fix init_hca fields offset net: x25: Increase refcnt of "struct x25_neigh" in x25_rx_call_request qlcnic: fix error return code in qlcnic_83xx_restart_hw() sctp: change to hold/put transport for proto_unreach_timer net: usb: qmi_wwan: Set DTR quirk for MR400 net: Have netpoll bring-up DSA management interface pinctrl: rockchip: enable gpio pclk for rockchip_gpio_to_irq arm64: psci: Avoid printing in cpu_psci_cpu_die() MIPS: Fix BUILD_ROLLBACK_PROLOGUE for microMIPS Input: adxl34x - clean up a data type in adxl34x_probe() arm: dts: imx6qdl-udoo: fix rgmii phy-mode for ksz9031 phy ARM: dts: imx50-evk: Fix the chip select 1 IOMUX perf lock: Don't free "lock_seq_stat" if read_count isn't zero can: dev: can_restart(): post buffer from the right context can: peak_usb: fix potential integer overflow on shift of a int can: m_can: m_can_handle_state_change(): fix state change MIPS: Alchemy: Fix memleak in alchemy_clk_setup_cpu
[Kernel-packages] [Bug 1906703] [NEW] Xenial update: v4.4.247 upstream stable release
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v4.4.247 upstream stable release
from git://git.kernel.org/
btrfs: tree-checker: Enhance chunk checker to validate chunk profile
btrfs: inode: Verify inode mode to avoid NULL pointer dereference
HID: cypress: Support Varmilo Keyboards' media hotkeys
Input: i8042 - allow insmod to succeed on devices without an i8042 controller
HID: hid-sensor-hub: Fix issue with devices with no report ID
x86/xen: don't unbind uninitialized lock_kicker_irq
proc: don't allow async path resolution of /proc/self components
dmaengine: pl330: _prep_dma_memcpy: Fix wrong burst size
scsi: libiscsi: Fix NOP race condition
scsi: target: iscsi: Fix cmd abort fabric stop race
scsi: ufs: Fix race between shutdown and runtime resume flow
bnxt_en: fix error return code in bnxt_init_board()
video: hyperv_fb: Fix the cache type when mapping the VRAM
bnxt_en: Release PCI regions when DMA mask setup fails during probe.
IB/mthca: fix return value of error branch in mthca_init_cq()
nfc: s3fwrn5: use signed integer for parsing GPIO numbers
efivarfs: revert "fix memory leak in efivarfs_create()"
perf probe: Fix to die_entrypc() returns error correctly
USB: core: Change %pK for __user pointers to %px
x86/speculation: Fix prctl() when spectre_v2_user={seccomp,prctl},ibpb
USB: core: add endpoint-blacklist quirk
USB: core: Fix regression in Hercules audio card
btrfs: fix lockdep splat when reading qgroup config on mount
Linux 4.4.247
UBUNTU: upstream stable to v4.4.247
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Confirmed
** Affects: linux (Ubuntu Xenial)
Importance: Undecided
Assignee: Kamal Mostafa (kamalmostafa)
Status: In Progress
** Tags: kernel-stable-tracking-bug
** Changed in: linux (Ubuntu)
Status: New => Confirmed
** Tags added: kernel-stable-tracking-bug
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** 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:
+ v4.4.247 upstream stable release
+ from git://git.kernel.org/
-v4.4.247 upstream stable release
-from git://git.kernel.org/
+ btrfs: tree-checker: Enhance chunk checker to validate chunk profile
+ btrfs: inode: Verify inode mode to avoid NULL pointer dereference
+ HID: cypress: Support Varmilo Keyboards' media hotkeys
+ Input: i8042 - allow insmod to succeed on devices without an i8042 controller
+ HID: hid-sensor-hub: Fix issue with devices with no report ID
+ x86/xen: don't unbind uninitialized lock_kicker_irq
+ proc: don't allow async path resolution of /proc/self components
+ dmaengine: pl330: _prep_dma_memcpy: Fix wrong burst size
+ scsi: libiscsi: Fix NOP race condition
+ scsi: target: iscsi: Fix cmd abort fabric stop race
+ scsi: ufs: Fix race between shutdown and runtime resume flow
+ bnxt_en: fix error return code in bnxt_init_board()
+ video: hyperv_fb: Fix the cache type when mapping the VRAM
+ bnxt_en: Release PCI regions when DMA mask setup fails during probe.
+ IB/mthca: fix return value of error branch in mthca_init_cq()
+ nfc: s3fwrn5: use signed integer for parsing GPIO numbers
+ efivarfs: revert "fix memory leak in efivarfs_create()"
+ perf probe: Fix to die_entrypc() returns error correctly
+ USB: core: Change %pK for __user pointers to %px
+ x86/speculation: Fix prctl() when spectre_v2_user={seccomp,prctl},ibpb
+ USB: core: add endpoint-blacklist quirk
+ USB: core: Fix regression in Hercules audio card
+ btrfs: fix lockdep splat when reading qgroup config on mount
+ Linux 4.4.247
+ UBUNTU: upstream stable to v4.4.247
** Changed in: linux (Ubuntu Xenial)
Status: New => Fix
[Kernel-packages] [Bug 1906700] [NEW] Xenial update: v4.4.246 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v4.4.246 upstream stable release from git://git.kernel.org/ ah6: fix error return code in ah6_input() atm: nicstar: Unmap DMA on send error net: b44: fix error return code in b44_init_one() net: bridge: add missing counters to ndo_get_stats64 callback netlabel: fix our progress tracking in netlbl_unlabel_staticlist() netlabel: fix an uninitialized warning in netlbl_unlabel_staticlist() net/mlx4_core: Fix init_hca fields offset net: x25: Increase refcnt of "struct x25_neigh" in x25_rx_call_request qlcnic: fix error return code in qlcnic_83xx_restart_hw() sctp: change to hold/put transport for proto_unreach_timer net: usb: qmi_wwan: Set DTR quirk for MR400 net: Have netpoll bring-up DSA management interface pinctrl: rockchip: enable gpio pclk for rockchip_gpio_to_irq arm64: psci: Avoid printing in cpu_psci_cpu_die() MIPS: Fix BUILD_ROLLBACK_PROLOGUE for microMIPS Input: adxl34x - clean up a data type in adxl34x_probe() arm: dts: imx6qdl-udoo: fix rgmii phy-mode for ksz9031 phy ARM: dts: imx50-evk: Fix the chip select 1 IOMUX perf lock: Don't free "lock_seq_stat" if read_count isn't zero can: dev: can_restart(): post buffer from the right context can: peak_usb: fix potential integer overflow on shift of a int can: m_can: m_can_handle_state_change(): fix state change MIPS: Alchemy: Fix memleak in alchemy_clk_setup_cpu regulator: ti-abb: Fix array out of bound read access on the first transition libfs: fix error cast of negative value in simple_attr_write() ALSA: ctl: fix error path at adding user-defined element set ALSA: mixart: Fix mutex deadlock tty: serial: imx: keep console clocks always on efivarfs: fix memory leak in efivarfs_create() ext4: fix bogus warning in ext4_update_dx_flag() xtensa: disable preemption around cache alias management calls mac80211: minstrel: remove deferred sampling code mac80211: minstrel: fix tx status processing corner case mac80211: allow driver to prevent two stations w/ same address mac80211: free sta in sta_info_insert_finish() on errors s390/cpum_sf.c: fix file permission for cpum_sfb_size x86/microcode/intel: Check patch signature before saving microcode for early loading Linux 4.4.246 UBUNTU: upstream stable to v4.4.246 ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Xenial) Importance: Undecided Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** 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: + v4.4.246 upstream stable release + from git://git.kernel.org/ -v4.4.246 upstream stable release -from git://git.kernel.org/ + ah6: fix error return code in ah6_input() + atm: nicstar: Unmap DMA on send error + net: b44: fix error return code in b44_init_one() + net: bridge: add missing counters to ndo_get_stats64 callback + netlabel: fix our progress tracking in netlbl_unlabel_staticlist() + netlabel: fix an uninitialized warning in netlbl_unlabel_staticlist() + net/mlx4_core: Fix init_hca fields offset + net: x25: Increase refcnt of "struct x25_neigh" in x25_rx_call_request + qlcnic: fix error return code in qlcnic_83xx_restart_hw() + sctp: change to hold/put transport for proto_unreach_timer + net:
[Kernel-packages] [Bug 1906600] Re: WiFi disconnects continually (goes "down" in NetworkManager)
I'm having a similar errors, I think it has something to do with the latest kernel updates. In my case, the kernel modules were updated on Dec 1. From the apt history.log: Start-Date: 2020-12-01 07:41:57 Commandline: aptdaemon role='role-commit-packages' sender=':1.297' Install: linux-image-5.4.0-56-generic:amd64 (5.4.0-56.62, automatic), linux-headers-5.4.0-56-generic:amd64 (5.4.0-56.62, automatic), linux-headers-5.4.0-56:amd64 (5.4.0-56.62, automatic), linux-modules-extra-5.4.0-56-generic:amd64 (5.4.0-56.62, automatic), linux-modules-5.4.0-56-generic:amd64 (5.4.0-56.62, automatic) Upgrade: linux-headers-generic:amd64 (5.4.0.54.57, 5.4.0.56.59), linux-libc-dev:amd64 (5.4.0-54.60, 5.4.0-56.62), linux-image-generic:amd64 (5.4.0.54.57, 5.4.0.56.59), snapd:amd64 (2.47.1+20.04, 2.48+20.04), linux-generic:amd64 (5.4.0.54.57, 5.4.0.56.59) End-Date: 2020-12-01 07:43:16 I didn't restart my computer at the time, but shut it down overnight and restarted in the morning of December 2, and that's when I started having very similar issues as described in the original submission. The biggest difference is that the time period of WiFi network disconnects is longer - normally it'll work for a half hour or more, but eventually I'll get disconnected and prompted for a password on a network that I've been connecting to for years. Might have something to do with Realtek wireless adapters: allan ~ $ lspci | grep -i WiFi 03:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8188CE 802.11b/g/n WiFi Adapter (rev 01) -- 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/1906600 Title: WiFi disconnects continually (goes "down" in NetworkManager) Status in Ubuntu MATE: New Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Confirmed Bug description: Hello everybody and thank you in advance for your help. After a recent update, my machine rebooted and appeared to be fine, but after a short time the WiFi dropped and the NetworkManager applet shows that the interface is down. I am also getting prompted for a password (which was previously saved) and when I click on connect it will establish the connection for a short time, but then goes down again. In some cases this is immediate in others, I will be online for up to approximately 15 minutes before it goes down again. I have tried restarting NetworkManager, but I get the same results (short time up, then down). I tried to review log data, but I am not a linux expert and so I'm not sure that I am looking at the right log, nor do I know exactly what to look for. Here are some lines from around the time of the disconnect and the restarting of NetworkManager: ' Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3945] device (wlo1): Activation: successful, device activated. Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8909] device (wlo1): supplicant interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9011] device (wlo1): supplicant interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (wlo1): supplicant interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]:
[Kernel-packages] [Bug 1906600] Re: WiFi disconnects continually (goes "down" in NetworkManager)
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/1906600 Title: WiFi disconnects continually (goes "down" in NetworkManager) Status in Ubuntu MATE: New Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Confirmed Bug description: Hello everybody and thank you in advance for your help. After a recent update, my machine rebooted and appeared to be fine, but after a short time the WiFi dropped and the NetworkManager applet shows that the interface is down. I am also getting prompted for a password (which was previously saved) and when I click on connect it will establish the connection for a short time, but then goes down again. In some cases this is immediate in others, I will be online for up to approximately 15 minutes before it goes down again. I have tried restarting NetworkManager, but I get the same results (short time up, then down). I tried to review log data, but I am not a linux expert and so I'm not sure that I am looking at the right log, nor do I know exactly what to look for. Here are some lines from around the time of the disconnect and the restarting of NetworkManager: ' Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3541] dhcp4 (wlo1): state changed unknown -> bound Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3698] device (wlo1): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3772] device (wlo1): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3856] device (wlo1): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3882] manager: NetworkManager state is now CONNECTED_SITE Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3945] device (wlo1): Activation: successful, device activated. Dec 01 21:13:24 bryan-HP-Notebook NetworkManager[22616]: [1606875204.3969] manager: NetworkManager state is now CONNECTED_GLOBAL Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8909] device (wlo1): supplicant interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.8910] device (p2p-dev-wlo1): supplicant management interface state: completed -> authenticating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9011] device (wlo1): supplicant interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9012] device (p2p-dev-wlo1): supplicant management interface state: authenticating -> associating Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (wlo1): supplicant interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9222] device (p2p-dev-wlo1): supplicant management interface state: associating -> 4-way handshake Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9223] sup-iface[0x562ab0adb110,wlo1]: connection disconnected (reason -1) Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9297] device (wlo1): supplicant interface state: 4-way handshake -> disconnected Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9318] device (wlo1): Activation: (wifi) disconnected during association, asking for new key Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9321] device (wlo1): state change: activated -> need-auth (reason 'supplicant-disconnect', sys-iface-state: 'managed') Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9526] dhcp4 (wlo1): canceled DHCP transaction Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9527] dhcp4 (wlo1): state changed bound -> done Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9544] manager: NetworkManager state is now CONNECTING Dec 01 21:15:48 bryan-HP-Notebook NetworkManager[22616]: [1606875348.9603] device (p2p-dev-wlo1): supplicant management interface state: 4-way handshake -> disconnected Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]: [1606875349.4819] device (wlo1): supplicant interface state: disconnected -> scanning Dec 01 21:15:49 bryan-HP-Notebook NetworkManager[22616]: [1606875349.4820] device (p2p-dev-wlo1):
[Kernel-packages] [Bug 1906698] [NEW] Xenial update: v4.4.245 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v4.4.245 upstream stable release from git://git.kernel.org/ i2c: imx: Fix external abort on interrupt in exit paths xfs: catch inode allocation state mismatch corruption xfs: validate cached inodes are free when allocated powerpc/8xx: Always fault when _PAGE_ACCESSED is not set Input: sunkbd - avoid use-after-free in teardown paths mac80211: always wind down STA state KVM: x86: clflushopt should be treated as a no-op by emulation Linux 4.4.245 ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Xenial) Importance: Undecided Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** 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: + v4.4.245 upstream stable release + from git://git.kernel.org/ -v4.4.245 upstream stable release -from git://git.kernel.org/ + i2c: imx: Fix external abort on interrupt in exit paths + xfs: catch inode allocation state mismatch corruption + xfs: validate cached inodes are free when allocated + powerpc/8xx: Always fault when _PAGE_ACCESSED is not set + Input: sunkbd - avoid use-after-free in teardown paths + mac80211: always wind down STA state + KVM: x86: clflushopt should be treated as a no-op by emulation + Linux 4.4.245 -- 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/1906698 Title: Xenial update: v4.4.245 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: In Progress Bug description: 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: v4.4.245 upstream stable release from git://git.kernel.org/ i2c: imx: Fix external abort on interrupt in exit paths xfs: catch inode allocation state mismatch corruption xfs: validate cached inodes are free when allocated powerpc/8xx: Always fault when _PAGE_ACCESSED is not set Input: sunkbd - avoid use-after-free in teardown paths mac80211: always wind down STA state KVM: x86: clflushopt should be treated as a no-op by emulation Linux 4.4.245 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1906698/+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 1906691] 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/1906691 Title: Laptop wakes up immediatly from suspend to RAM Status in linux package in Ubuntu: Confirmed Bug description: Since last kernel update to (5.4.0-56-generic #62-Ubuntu SMP), my laptop wakes up as soon as it reaches the suspend to RAM S3 state. I'm running ubuntu 20.04 on a Microsoft Surface Pro (the 2013 version). The only relevant error message I found is : ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT0._GTF due to previous error (AE_NOT_FOUND) (20190816/psparse-529) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-56-generic 5.4.0-56.62 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wilk 1801 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Thu Dec 3 17:35:36 2020 HibernationDevice: RESUME=UUID=adb12a68-9928-4181-b4e2-487010d3c501 InstallationDate: Installed on 2017-10-22 (1138 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Microsoft Corporation Surface with Windows 8 Pro ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-56-generic root=UUID=919f00b8-5010-46e1-b2f9-c129e17d5312 ro video=VGA-1:1366x768@60 quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-56-generic N/A linux-backports-modules-5.4.0-56-generic N/A linux-firmware1.187.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/08/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.00.0250 dmi.board.asset.tag: 0 dmi.board.name: Surface with Windows 8 Pro dmi.board.vendor: Microsoft Corporation dmi.board.version: 1 dmi.chassis.asset.tag: 0 dmi.chassis.type: 17 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: 1 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.00.0250:bd01/08/2013:svnMicrosoftCorporation:pnSurfacewithWindows8Pro:pvr1:rvnMicrosoftCorporation:rnSurfacewithWindows8Pro:rvr1:cvnMicrosoftCorporation:ct17:cvr1: dmi.product.family: Surface dmi.product.name: Surface with Windows 8 Pro dmi.product.sku: Surface_PRO_1 dmi.product.version: 1 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1906691/+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 1906601] Re: FBDEV in use with amdgpu and there is no /dev/dri/card0 (hardware is AMD/ATI Renoir [1002:1636])
Thanks Daniel and Timo, your help is greatly appreciated. I updated to 20.10 and things appear to be a lot different in my display. The HDMI works, the night light works, and now xrandr shows an extensive output for my display. I wish I knew it was this simple awhile ago haha! Let me know if you would like me to attach any of the output commands in my new system. I did not need to update to the hwe kernal. I am just using the generic kernal (I will paste the version of the kernal that I am running below). I was going to do the hwe kernal update like you recommended, however, I don't want to fix what is not broken. Unless you recommend that I update to the linux-generic-hwe-20.04-edge like recommended above. Let me know if that is the case (if this is the case, please confirm that you would recommend installing linux-generic-hwe-20.04-edge opposed to installing linux-generic-hwe-20.10-edge, if that is a thing). Again, thank you both so much. blaise@blaise-V:~$ cat /proc/version Linux version 5.8.0-31-generic (buildd@lgw01-amd64-038) (gcc (Ubuntu 10.2.0-13ubuntu1) 10.2.0, GNU ld (GNU Binutils for Ubuntu) 2.35.1) #33-Ubuntu SMP Mon Nov 23 18:44:54 UTC 2020 -- 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/1906601 Title: FBDEV in use with amdgpu and there is no /dev/dri/card0 (hardware is AMD/ATI Renoir [1002:1636]) Status in linux package in Ubuntu: Fix Released Status in linux-meta-hwe-5.8 package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Invalid Bug description: New bug from: https://bugs.launchpad.net/ubuntu/+bug/1906525. lshw -c video gives same result of unclaimed video. Night light and HDMI still do not work. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Dec 2 22:09:04 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: rtl8821ce, 5.5.2.1, 5.4.0-56-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Renoir [1043:1352] InstallationDate: Installed on 2020-12-01 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X513IA_M513IA ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-56-generic root=UUID=9f7c4a34-4508-4d48-9c26-c7bf0045826a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X513IA.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X513IA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX513IA.300:bd06/05/2020:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX513IA_M513IA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX513IA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: VivoBook_ASUSLaptop X513IA_M513IA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6 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/1906601/+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 1906691] [NEW] Laptop wakes up immediatly from suspend to RAM
Public bug reported: Since last kernel update to (5.4.0-56-generic #62-Ubuntu SMP), my laptop wakes up as soon as it reaches the suspend to RAM S3 state. I'm running ubuntu 20.04 on a Microsoft Surface Pro (the 2013 version). The only relevant error message I found is : ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT0._GTF due to previous error (AE_NOT_FOUND) (20190816/psparse-529) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-56-generic 5.4.0-56.62 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wilk 1801 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Thu Dec 3 17:35:36 2020 HibernationDevice: RESUME=UUID=adb12a68-9928-4181-b4e2-487010d3c501 InstallationDate: Installed on 2017-10-22 (1138 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Microsoft Corporation Surface with Windows 8 Pro ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-56-generic root=UUID=919f00b8-5010-46e1-b2f9-c129e17d5312 ro video=VGA-1:1366x768@60 quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-56-generic N/A linux-backports-modules-5.4.0-56-generic N/A linux-firmware1.187.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/08/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.00.0250 dmi.board.asset.tag: 0 dmi.board.name: Surface with Windows 8 Pro dmi.board.vendor: Microsoft Corporation dmi.board.version: 1 dmi.chassis.asset.tag: 0 dmi.chassis.type: 17 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: 1 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.00.0250:bd01/08/2013:svnMicrosoftCorporation:pnSurfacewithWindows8Pro:pvr1:rvnMicrosoftCorporation:rnSurfacewithWindows8Pro:rvr1:cvnMicrosoftCorporation:ct17:cvr1: dmi.product.family: Surface dmi.product.name: Surface with Windows 8 Pro dmi.product.sku: Surface_PRO_1 dmi.product.version: 1 dmi.sys.vendor: Microsoft Corporation ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug focal wayland-session -- 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/1906691 Title: Laptop wakes up immediatly from suspend to RAM Status in linux package in Ubuntu: Confirmed Bug description: Since last kernel update to (5.4.0-56-generic #62-Ubuntu SMP), my laptop wakes up as soon as it reaches the suspend to RAM S3 state. I'm running ubuntu 20.04 on a Microsoft Surface Pro (the 2013 version). The only relevant error message I found is : ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT0._GTF due to previous error (AE_NOT_FOUND) (20190816/psparse-529) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-56-generic 5.4.0-56.62 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wilk 1801 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Thu Dec 3 17:35:36 2020 HibernationDevice: RESUME=UUID=adb12a68-9928-4181-b4e2-487010d3c501 InstallationDate: Installed on 2017-10-22 (1138 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Microsoft Corporation Surface with Windows 8 Pro ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-56-generic root=UUID=919f00b8-5010-46e1-b2f9-c129e17d5312 ro video=VGA-1:1366x768@60 quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-56-generic N/A linux-backports-modules-5.4.0-56-generic N/A linux-firmware1.187.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/08/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.00.0250 dmi.board.asset.tag: 0 dmi.board.name: Surface with Windows 8 Pro dmi.board.vendor: Microsoft Corporation dmi.board.version: 1 dmi.chassis.asset.tag: 0 dmi.chassis.type: 17 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: 1 dmi.modalias:
[Kernel-packages] [Bug 1894017] Re: Keyboard not working
5.9.12 + commit d823346876a970522ff9e4d2b323c9b734dcc4de: https://people.canonical.com/~khfeng/lp1894017/ -- 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/1894017 Title: Keyboard not working Status in linux package in Ubuntu: Confirmed Bug description: The laptop keyboard doesn't work at login or in the de. If I ctrl+alt+F3 from an external usb keyboard to a terminal the laptop keyboard works. An external usb keyboard works everywhere. The laptop's keyboard does work everywhere with the previous kernel 5.4.0.42. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-45-lowlatency 5.4.0-45.49 ProcVersionSignature: Ubuntu 5.4.0-45.49-lowlatency 5.4.55 Uname: Linux 5.4.0-45-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Thu Sep 3 03:09:49 2020 InstallationDate: Installed on 2019-08-07 (392 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Hewlett-Packard HP Pavilion 11 x360 PC ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-lowlatency root=UUID=6035c42c-766d-44fd-b45c-6cdf9c74e0b5 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.4.0-45-lowlatency N/A linux-backports-modules-5.4.0-45-lowlatency N/A linux-firmware 1.187.3 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-04-06 (149 days ago) dmi.bios.date: 03/13/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.30 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2209 dmi.board.vendor: Hewlett-Packard dmi.board.version: 57.57 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.30:bd03/13/2018:svnHewlett-Packard:pnHPPavilion11x360PC:pvr097710405F00010420180:rvnHewlett-Packard:rn2209:rvr57.57:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=MIN dmi.product.name: HP Pavilion 11 x360 PC dmi.product.sku: M0B61EA#ACQ dmi.product.version: 097710405F00010420180 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894017/+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 1906542] Re: echo 1 >> /sys/module/zfs/parameters/zfs_max_missing_tvds says premission error, unable to reapair lost zfs pool data
Why is the second disk missing? If you accidentally added it and ended up with a striped pool, as long as both disks are connected, you can import the pool normally. Then use the new device_removal feature to remove the new disk from the pool. If you've done something crazy like pulled the disk and wiped it, then yeah, you're going to need to figure out how to import the pool read- only. I don't have any advice on that piece. -- 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/1906542 Title: echo 1 >> /sys/module/zfs/parameters/zfs_max_missing_tvds says premission error, unable to reapair lost zfs pool data Status in zfs-linux package in Ubuntu: New Bug description: root@jonipekka-desktop:~# echo 1 >> /sys/module/zfs/parameters/zfs_max_missing_tvds -bash: /sys/module/zfs/parameters/zfs_max_missing_tvds: Permission denied root@jonipekka-desktop:~# https://www.delphix.com/blog/openzfs-pool-import-recovery Import with missing top level vdevs The changes to the pool configuration logic have enabled another great improvement: the ability to import a pool with missing or faulted top- level vdevs. Since some data will almost certainly be missing, a pool with missing top-level vdevs can only be imported read-only, and the failmode is set to “continue” (failmode=continue means that when encountering errors the pool will continue running, as opposed to being suspended or panicking). To enable this feature, we’ve added a new global variable: zfs_max_missing_tvds, which defines how many missing top level vdevs we can tolerate before marking a pool as unopenable. It is set to 0 by default, and should be changed to other values only temporarily, while performing an extreme pool recovery. Here as an example we create a pool with two vdevs and write some data to a first dataset; we then add a third vdev and write some data to a second dataset. Finally we physically remove the new vdev (simulating, for instance, a device failure) and try to import the pool using the new feature. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: zfsutils-linux 0.7.5-1ubuntu16.10 ProcVersionSignature: Ubuntu 4.15.0-126.129-generic 4.15.18 Uname: Linux 4.15.0-126-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.20 Architecture: amd64 Date: Wed Dec 2 18:39:58 2020 InstallationDate: Installed on 2020-12-02 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: zfs-linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1906542/+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 1905574] Re: Ubuntu 20.10 four needed fixes to 'Add driver for Mellanox Connect-IB adapters'
Tag/Log Check - looks like the first patch is already in 5.8 d43b7007dbd1 -- Ubuntu-5.8.0-10.11 -- Wed Mar 18 21:44:32 2020 +0200 410bd754cd73 -- v5.10-rc1 -- Mon Aug 31 15:04:35 2020 +0300 1d5558b1f0de -- v5.10-rc1 -- Tue Jul 21 10:25:52 2020 +0300 50b2412b7e78 -- v5.10-rc1 -- Tue Aug 4 10:40:21 2020 +0300 432161ea26d6 -- v5.10-rc1 -- Thu Aug 13 16:55:20 2020 +0300 -- 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/1905574 Title: Ubuntu 20.10 four needed fixes to 'Add driver for Mellanox Connect-IB adapters' Status in linux package in Ubuntu: In Progress Bug description: [Impact] commit d43b7007dbd1 net/mlx5: Fix a race when moving command interface to events mode from upstream v5.7-rc1 (and in groovy) fixes e126ba97dba9 mlx5: Add driver for Mellanox Connect-IB adapters this fix should come with four more patches from v5.9. 410bd754cd73 net/mlx5: Add retry mechanism to the command entry index allocation 1d5558b1f0de net/mlx5: poll cmd EQ in case of command timeout 50b2412b7e78 net/mlx5: Avoid possible free of command entry while timeout comp handler 432161ea26d6 net/mlx5: Fix a race when moving command interface to polling mode all four patches are applied cleanly on groovy tree and we ask to pull them into groovy. please also see this discussion https://www.spinics.net/lists/stable/msg428620.html Thank's To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1905574/+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 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
I understood that they need to deal with new codec inclusion, via GStreamer o other libs, and that writing code and manage a community is not a simple task. Said that, IMHO there are three big question with bluetooth and PulseAudio: 1. in these days we (probably most of us) are always on web conferencing and we need good audio quality in both direction, mic and speaker. Current bluetooth headsets are capable of using Bluetooth Profile HFP 1.6 with mSBC 16kHz audio encoding, this standard permit high quality voice conferencing and It was made in 2011...9 year ago. 2. Bluetooth Profile A2DP for listening only (music...) There are a lot of codec for high quality listen audio, es. SBC-XQ, aptX-LL, aptX-HD, aptX Voice and FastStream 3. Support for new version of Bluetooth / Profile. Ex #1 BT 5.3 with LC3 (Low Complexity Communications Coded (LC3)) codec. Ex #2 BT Profile HFP 1.8 with codec selection and Enhanced Voice Recognition Activation. My two cents -- 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/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Triaged Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+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 1906107] Re: "unexpectedly disconnected from host boot status daemon" under high memory load
I've been quite busy recently, would it be possible to bisect the kernel locally? -- 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/1906107 Title: "unexpectedly disconnected from host boot status daemon" under high memory load Status in linux package in Ubuntu: Confirmed Bug description: The hardware is Dell XPS13 9343, I'm using FDE with sepreate boot and EFI and NVMe disk. Under high memory load, usually when launching additional window my display goes blank, WiFi connection is lost, I can only reboot and Ctrl+alt+Fn When I do the second I'm getting following message: "unexpectedly disconnected from host boot status daemon" under high memory load Volume-Group 'ubuntu-vg' not found' [...] Please unlock disk nvme0n1op3_crypt: " Despite I enter correct password it doesn't work, seems like it lost connection with NVMe drive at all ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-124-generic 4.15.0-124.127 ProcVersionSignature: Ubuntu 4.15.0-124.127-generic 4.15.18 Uname: Linux 4.15.0-124-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: nusch 10223 F pulseaudio /dev/snd/pcmC0D3p: nusch 10223 F...m pulseaudio /dev/snd/controlC0: nusch 10223 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Nov 28 14:01:20 2020 HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1 InstallationDate: Installed on 2015-05-08 (2031 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. XPS 13 9343 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-124-generic root=/dev/mapper/ubuntu--vg-root ro crashkernel=384M-:128M quiet splash log_buf_len=1M crashkernel=512M-:192M vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-124-generic N/A linux-backports-modules-4.15.0-124-generic N/A linux-firmware 1.173.19 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-08-26 (824 days ago) dmi.bios.date: 06/06/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: A20 dmi.board.name: 09K8G1 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA20:bd06/06/2019:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn09K8G1:rvrA02:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9343 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1906107/+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 1906404] Re: New upstream release 2020.11.20
Tested on x/b/f/g: 1. Install package from -proposed. 2. Reload the regdb or reboot, depending on kernel/iw versions. 3. Query current reg domain. 4. Change to a different reg domain. 5. Query again to confirm the reg domain has changed. 6. Check kernel/crda logs for errors. Testing passed in all cases with no errors in the logs. ** Tags removed: verification-needed-bionic verification-needed-focal verification-needed-groovy verification-needed-xenial ** Tags added: verification-done-bionic verification-done-focal verification-done-groovy verification-done-xenial ** Changed in: wireless-regdb (Ubuntu Hirsute) Status: Fix Committed => Fix Released ** Also affects: wireless-regdb (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: wireless-regdb (Ubuntu Precise) Importance: Undecided Status: New ** Changed in: wireless-regdb (Ubuntu Precise) Status: New => In Progress ** Changed in: wireless-regdb (Ubuntu Trusty) Status: New => In Progress ** Changed in: wireless-regdb (Ubuntu Precise) Importance: Undecided => Medium ** Changed in: wireless-regdb (Ubuntu Precise) Assignee: (unassigned) => Seth Forshee (sforshee) ** Changed in: wireless-regdb (Ubuntu Trusty) Importance: Undecided => Medium ** Changed in: wireless-regdb (Ubuntu Trusty) Assignee: (unassigned) => Seth Forshee (sforshee) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to wireless-regdb in Ubuntu. https://bugs.launchpad.net/bugs/1906404 Title: New upstream release 2020.11.20 Status in wireless-regdb package in Ubuntu: Fix Released Status in wireless-regdb source package in Precise: In Progress Status in wireless-regdb source package in Trusty: In Progress Status in wireless-regdb source package in Xenial: Fix Committed Status in wireless-regdb source package in Bionic: Fix Committed Status in wireless-regdb source package in Focal: Fix Committed Status in wireless-regdb source package in Groovy: Fix Committed Status in wireless-regdb source package in Hirsute: Fix Released Bug description: [Impact] New upstream release. This is a database of wireless regulations, and should updated in all releases to ensure users have the most up-to- date regulatory information. [Test Case] Following reboot after installing the new database, it should be possible to query and change the regulatory domain using 'iw reg get' and 'iw reg set'. [Where problems could occur] If crda or the kernel is unable to use the new database, users may be stuck using the default "world" regulatory domain which is quite restrictive, therefore they may be unable to use wireless channels that they were able to use previously. Regulatory rules may have also changed for the user's region, which could also make some channels unusable, but this would not be a bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wireless-regdb/+bug/1906404/+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 1906341] Re: Touchpad button doesn't work on Dell Precision 7550/7750
Oh thanks, looks like dpkg-gensymbols is adding the symbols even if the debian/libname.symbols isn't updated which makes that work automatically, ideally the list would be manually updated and the build log has a warning about that but that should make a difference for a SRU. I've uploaded now ** Changed in: libinput (Ubuntu) Status: In Progress => Fix Committed -- 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/1906341 Title: Touchpad button doesn't work on Dell Precision 7550/7750 Status in OEM Priority Project: New Status in libevdev package in Ubuntu: Fix Released Status in libinput package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Confirmed Bug description: [Impact] * The touchpad's right button become no function after update to 5.4 kernel * The INPUT_PROP_BUTTONPAD property is set by 5.4 kernel, so that libinput regard it as clickpad, the root cause is that the touchpad firmware doesn't config correctly. * Add a model quirk to unset the bit can make touchpad's right button works normally. [Test Case] * 1. Boot into Ubuntu 2. Identify touchpad input device number, can be obtained in $HOME/.local/share/xorg/Xorg.0.log 3. $ udevadm info /sys/class/input/inputX check PROP environment variable, it is 5 if INPUT_PROP_BUTTONPAD property is set 4. And the touchpad right button become no function 5. After update the libevdev with disable_property API and libinput10 with model quirk 6. reboot 7. The input device PROP is still 5, but touchpad right button is workable [Where problems could occur] * For libevdev2 package, backport the upstream commit: https://gitlab.freedesktop.org/libevdev/libevdev/-/commit/4226c7801b4ea1b0c7d1eaac47ca24ece8f24809 The API is not originally exist in the system, so it will only be utilized by our model quirk. * For libinput, add model quirk for the platform to disable INPUT_PROP_BUTTONPAD bit. Only disable the INPUT_PROP_BUTTONPAD for specified model, and it doesn't issue any IO command to kernel, so the behavior should be the same as previous kernel when INPUT_PROP_BUTTONPAD is not set. [Other Info] * A public bug is reported https://www.dell.com/community/Linux-Developer-Systems/Touchpad-right-click-button-not-working-with-Ubuntu-20-04-on/td-p/7636831 * A workable build for Bionic/Focal/Groovy are in my ppa https://launchpad.net/~kchsieh/+archive/ubuntu/training --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1646 F pulseaudio BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu GraphicsCard: Intel Corporation Device [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:09c3] InstallationDate: Installed on 2020-12-01 (0 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) MachineType: Dell Inc. Precision 7550 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=2964a5af-ac17-45ee-a009-41879da14e1b ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.173.19 Tags: bionic ubuntu Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/01/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd09/01/2020:svnDellInc.:pnPrecision7550:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 7550 dmi.product.sku: 09C3 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage
[Kernel-packages] [Bug 1905574] Re: Ubuntu 20.10 four needed fixes to 'Add driver for Mellanox Connect-IB adapters'
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Jeff Lane (bladernr) ** Changed in: linux (Ubuntu) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu) Importance: Undecided => Medium -- 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/1905574 Title: Ubuntu 20.10 four needed fixes to 'Add driver for Mellanox Connect-IB adapters' Status in linux package in Ubuntu: In Progress Bug description: [Impact] commit d43b7007dbd1 net/mlx5: Fix a race when moving command interface to events mode from upstream v5.7-rc1 (and in groovy) fixes e126ba97dba9 mlx5: Add driver for Mellanox Connect-IB adapters this fix should come with four more patches from v5.9. 410bd754cd73 net/mlx5: Add retry mechanism to the command entry index allocation 1d5558b1f0de net/mlx5: poll cmd EQ in case of command timeout 50b2412b7e78 net/mlx5: Avoid possible free of command entry while timeout comp handler 432161ea26d6 net/mlx5: Fix a race when moving command interface to polling mode all four patches are applied cleanly on groovy tree and we ask to pull them into groovy. please also see this discussion https://www.spinics.net/lists/stable/msg428620.html Thank's To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1905574/+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 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
Time to get a Macbook or Chromebook or whatever -- 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/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Triaged Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+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 1905574] Re: Ubuntu 20.10 four needed fixes to 'Add driver for Mellanox Connect-IB adapters'
** 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/1905574 Title: Ubuntu 20.10 four needed fixes to 'Add driver for Mellanox Connect-IB adapters' Status in linux package in Ubuntu: Confirmed Bug description: [Impact] commit d43b7007dbd1 net/mlx5: Fix a race when moving command interface to events mode from upstream v5.7-rc1 (and in groovy) fixes e126ba97dba9 mlx5: Add driver for Mellanox Connect-IB adapters this fix should come with four more patches from v5.9. 410bd754cd73 net/mlx5: Add retry mechanism to the command entry index allocation 1d5558b1f0de net/mlx5: poll cmd EQ in case of command timeout 50b2412b7e78 net/mlx5: Avoid possible free of command entry while timeout comp handler 432161ea26d6 net/mlx5: Fix a race when moving command interface to polling mode all four patches are applied cleanly on groovy tree and we ask to pull them into groovy. please also see this discussion https://www.spinics.net/lists/stable/msg428620.html Thank's To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1905574/+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 1906404] Re: New upstream release 2020.11.20
** Description changed: - New upstream version, bringing in updated regulatory rules for various - jurisdictions. + [Impact] + + New upstream release. This is a database of wireless regulations, and + should updated in all releases to ensure users have the most up-to-date + regulatory information. + + [Test Case] + + Following reboot after installing the new database, it should be + possible to query and change the regulatory domain using 'iw reg get' + and 'iw reg set'. + + [Where problems could occur] + + If crda or the kernel is unable to use the new database, users may be + stuck using the default "world" regulatory domain which is quite + restrictive, therefore they may be unable to use wireless channels that + they were able to use previously. Regulatory rules may have also changed + for the user's region, which could also make some channels unusable, but + this would not be a bug. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to wireless-regdb in Ubuntu. https://bugs.launchpad.net/bugs/1906404 Title: New upstream release 2020.11.20 Status in wireless-regdb package in Ubuntu: Fix Committed Status in wireless-regdb source package in Xenial: Fix Committed Status in wireless-regdb source package in Bionic: Fix Committed Status in wireless-regdb source package in Focal: Fix Committed Status in wireless-regdb source package in Groovy: Fix Committed Status in wireless-regdb source package in Hirsute: Fix Committed Bug description: [Impact] New upstream release. This is a database of wireless regulations, and should updated in all releases to ensure users have the most up-to- date regulatory information. [Test Case] Following reboot after installing the new database, it should be possible to query and change the regulatory domain using 'iw reg get' and 'iw reg set'. [Where problems could occur] If crda or the kernel is unable to use the new database, users may be stuck using the default "world" regulatory domain which is quite restrictive, therefore they may be unable to use wireless channels that they were able to use previously. Regulatory rules may have also changed for the user's region, which could also make some channels unusable, but this would not be a bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wireless-regdb/+bug/1906404/+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 1906107] 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/1906107 Title: "unexpectedly disconnected from host boot status daemon" under high memory load Status in linux package in Ubuntu: Confirmed Bug description: The hardware is Dell XPS13 9343, I'm using FDE with sepreate boot and EFI and NVMe disk. Under high memory load, usually when launching additional window my display goes blank, WiFi connection is lost, I can only reboot and Ctrl+alt+Fn When I do the second I'm getting following message: "unexpectedly disconnected from host boot status daemon" under high memory load Volume-Group 'ubuntu-vg' not found' [...] Please unlock disk nvme0n1op3_crypt: " Despite I enter correct password it doesn't work, seems like it lost connection with NVMe drive at all ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-124-generic 4.15.0-124.127 ProcVersionSignature: Ubuntu 4.15.0-124.127-generic 4.15.18 Uname: Linux 4.15.0-124-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: nusch 10223 F pulseaudio /dev/snd/pcmC0D3p: nusch 10223 F...m pulseaudio /dev/snd/controlC0: nusch 10223 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Nov 28 14:01:20 2020 HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1 InstallationDate: Installed on 2015-05-08 (2031 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. XPS 13 9343 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-124-generic root=/dev/mapper/ubuntu--vg-root ro crashkernel=384M-:128M quiet splash log_buf_len=1M crashkernel=512M-:192M vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-124-generic N/A linux-backports-modules-4.15.0-124-generic N/A linux-firmware 1.173.19 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-08-26 (824 days ago) dmi.bios.date: 06/06/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: A20 dmi.board.name: 09K8G1 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA20:bd06/06/2019:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn09K8G1:rvrA02:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9343 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1906107/+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 1906404] Please test proposed package
Hello Seth, or anyone else affected, Accepted wireless-regdb into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/wireless- regdb/2020.11.20-0ubuntu1~16.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to wireless-regdb in Ubuntu. https://bugs.launchpad.net/bugs/1906404 Title: New upstream release 2020.11.20 Status in wireless-regdb package in Ubuntu: Fix Committed Status in wireless-regdb source package in Xenial: Fix Committed Status in wireless-regdb source package in Bionic: Fix Committed Status in wireless-regdb source package in Focal: Fix Committed Status in wireless-regdb source package in Groovy: Fix Committed Status in wireless-regdb source package in Hirsute: Fix Committed Bug description: New upstream version, bringing in updated regulatory rules for various jurisdictions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wireless-regdb/+bug/1906404/+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 1906404] Please test proposed package
Hello Seth, or anyone else affected, Accepted wireless-regdb into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/wireless- regdb/2020.11.20-0ubuntu1~18.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: wireless-regdb (Ubuntu Xenial) Status: Confirmed => Fix Committed ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to wireless-regdb in Ubuntu. https://bugs.launchpad.net/bugs/1906404 Title: New upstream release 2020.11.20 Status in wireless-regdb package in Ubuntu: Fix Committed Status in wireless-regdb source package in Xenial: Fix Committed Status in wireless-regdb source package in Bionic: Fix Committed Status in wireless-regdb source package in Focal: Fix Committed Status in wireless-regdb source package in Groovy: Fix Committed Status in wireless-regdb source package in Hirsute: Fix Committed Bug description: New upstream version, bringing in updated regulatory rules for various jurisdictions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wireless-regdb/+bug/1906404/+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 1906404] Please test proposed package
Hello Seth, or anyone else affected, Accepted wireless-regdb into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/wireless- regdb/2020.11.20-0ubuntu1~20.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: wireless-regdb (Ubuntu Bionic) Status: Confirmed => Fix Committed ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to wireless-regdb in Ubuntu. https://bugs.launchpad.net/bugs/1906404 Title: New upstream release 2020.11.20 Status in wireless-regdb package in Ubuntu: Fix Committed Status in wireless-regdb source package in Xenial: Fix Committed Status in wireless-regdb source package in Bionic: Fix Committed Status in wireless-regdb source package in Focal: Fix Committed Status in wireless-regdb source package in Groovy: Fix Committed Status in wireless-regdb source package in Hirsute: Fix Committed Bug description: New upstream version, bringing in updated regulatory rules for various jurisdictions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wireless-regdb/+bug/1906404/+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 1906404] Re: New upstream release 2020.11.20
Hello Seth, or anyone else affected, Accepted wireless-regdb into groovy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/wireless- regdb/2020.11.20-0ubuntu1~20.10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- groovy to verification-done-groovy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-groovy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: wireless-regdb (Ubuntu Groovy) Status: Confirmed => Fix Committed ** Tags added: verification-needed verification-needed-groovy ** Changed in: wireless-regdb (Ubuntu Focal) Status: Confirmed => Fix Committed ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to wireless-regdb in Ubuntu. https://bugs.launchpad.net/bugs/1906404 Title: New upstream release 2020.11.20 Status in wireless-regdb package in Ubuntu: Fix Committed Status in wireless-regdb source package in Xenial: Fix Committed Status in wireless-regdb source package in Bionic: Fix Committed Status in wireless-regdb source package in Focal: Fix Committed Status in wireless-regdb source package in Groovy: Fix Committed Status in wireless-regdb source package in Hirsute: Fix Committed Bug description: New upstream version, bringing in updated regulatory rules for various jurisdictions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wireless-regdb/+bug/1906404/+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 1906655] Re: Ethernet interface broken (Flags mismatch irq) after upgrading to kernel 5.8.0-31
> 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 bug causes network interface to be unavailable, and `apport-collect` requires Internet connection to proceed. Please provide a way to generate an offline report. ** 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/1906655 Title: Ethernet interface broken (Flags mismatch irq) after upgrading to kernel 5.8.0-31 Status in linux package in Ubuntu: Confirmed Bug description: Realtek ethernet network interface is broken when booting with kernel 5.8.0-31. It works fine when simply booting with previous kernel 5.8.0-29 in GRUB. No other packages were updated. The only related line in /var/log/kern.log: Dec 3 14:01:21 hd kernel: [ 17.824691] genirq: Flags mismatch irq 16. 00010080 (enp4s0) vs. 2080 (uhci_hcd:usb3) `lspci -v` for this network interface below (`lspci -vv` attached): 04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 01) Subsystem: Gigabyte Technology Co., Ltd Onboard Ethernet Flags: bus master, fast devsel, latency 0, IRQ 16 I/O ports at d000 [size=256] Memory at f800 (64-bit, non-prefetchable) [size=4K] Expansion ROM at f700 [virtual] [disabled] [size=128K] Capabilities: [40] Power Management version 2 Capabilities: [48] Vital Product Data Capabilities: [50] MSI: Enable- Count=1/2 Maskable- 64bit+ Capabilities: [60] Express Endpoint, MSI 00 Capabilities: [84] Vendor Specific Information: Len=4c Capabilities: [100] Advanced Error Reporting Capabilities: [12c] Virtual Channel Capabilities: [148] Device Serial Number 00-00-00-00-10-ec-81-68 Capabilities: [154] Power Budgeting Kernel driver in use: r8169 Kernel modules: r8169 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1906655/+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 1906107] Re: "unexpectedly disconnected from host boot status daemon" under high memory load
Hello, need more testing but after 4 days no crash so far with mainline while it used to happen 2 times a day in past. Can you build bisect kernel for me ? ** Changed in: linux (Ubuntu) Status: Confirmed => 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/1906107 Title: "unexpectedly disconnected from host boot status daemon" under high memory load Status in linux package in Ubuntu: New Bug description: The hardware is Dell XPS13 9343, I'm using FDE with sepreate boot and EFI and NVMe disk. Under high memory load, usually when launching additional window my display goes blank, WiFi connection is lost, I can only reboot and Ctrl+alt+Fn When I do the second I'm getting following message: "unexpectedly disconnected from host boot status daemon" under high memory load Volume-Group 'ubuntu-vg' not found' [...] Please unlock disk nvme0n1op3_crypt: " Despite I enter correct password it doesn't work, seems like it lost connection with NVMe drive at all ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-124-generic 4.15.0-124.127 ProcVersionSignature: Ubuntu 4.15.0-124.127-generic 4.15.18 Uname: Linux 4.15.0-124-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: nusch 10223 F pulseaudio /dev/snd/pcmC0D3p: nusch 10223 F...m pulseaudio /dev/snd/controlC0: nusch 10223 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Nov 28 14:01:20 2020 HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1 InstallationDate: Installed on 2015-05-08 (2031 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. XPS 13 9343 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-124-generic root=/dev/mapper/ubuntu--vg-root ro crashkernel=384M-:128M quiet splash log_buf_len=1M crashkernel=512M-:192M vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-124-generic N/A linux-backports-modules-4.15.0-124-generic N/A linux-firmware 1.173.19 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-08-26 (824 days ago) dmi.bios.date: 06/06/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: A20 dmi.board.name: 09K8G1 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA20:bd06/06/2019:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn09K8G1:rvrA02:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9343 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1906107/+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 1906655] 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 1906655 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/1906655 Title: Ethernet interface broken (Flags mismatch irq) after upgrading to kernel 5.8.0-31 Status in linux package in Ubuntu: Incomplete Bug description: Realtek ethernet network interface is broken when booting with kernel 5.8.0-31. It works fine when simply booting with previous kernel 5.8.0-29 in GRUB. No other packages were updated. The only related line in /var/log/kern.log: Dec 3 14:01:21 hd kernel: [ 17.824691] genirq: Flags mismatch irq 16. 00010080 (enp4s0) vs. 2080 (uhci_hcd:usb3) `lspci -v` for this network interface below (`lspci -vv` attached): 04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 01) Subsystem: Gigabyte Technology Co., Ltd Onboard Ethernet Flags: bus master, fast devsel, latency 0, IRQ 16 I/O ports at d000 [size=256] Memory at f800 (64-bit, non-prefetchable) [size=4K] Expansion ROM at f700 [virtual] [disabled] [size=128K] Capabilities: [40] Power Management version 2 Capabilities: [48] Vital Product Data Capabilities: [50] MSI: Enable- Count=1/2 Maskable- 64bit+ Capabilities: [60] Express Endpoint, MSI 00 Capabilities: [84] Vendor Specific Information: Len=4c Capabilities: [100] Advanced Error Reporting Capabilities: [12c] Virtual Channel Capabilities: [148] Device Serial Number 00-00-00-00-10-ec-81-68 Capabilities: [154] Power Budgeting Kernel driver in use: r8169 Kernel modules: r8169 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1906655/+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 1906655] [NEW] Ethernet interface broken (Flags mismatch irq) after upgrading to kernel 5.8.0-31
Public bug reported: Realtek ethernet network interface is broken when booting with kernel 5.8.0-31. It works fine when simply booting with previous kernel 5.8.0-29 in GRUB. No other packages were updated. The only related line in /var/log/kern.log: Dec 3 14:01:21 hd kernel: [ 17.824691] genirq: Flags mismatch irq 16. 00010080 (enp4s0) vs. 2080 (uhci_hcd:usb3) `lspci -v` for this network interface below (`lspci -vv` attached): 04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 01) Subsystem: Gigabyte Technology Co., Ltd Onboard Ethernet Flags: bus master, fast devsel, latency 0, IRQ 16 I/O ports at d000 [size=256] Memory at f800 (64-bit, non-prefetchable) [size=4K] Expansion ROM at f700 [virtual] [disabled] [size=128K] Capabilities: [40] Power Management version 2 Capabilities: [48] Vital Product Data Capabilities: [50] MSI: Enable- Count=1/2 Maskable- 64bit+ Capabilities: [60] Express Endpoint, MSI 00 Capabilities: [84] Vendor Specific Information: Len=4c Capabilities: [100] Advanced Error Reporting Capabilities: [12c] Virtual Channel Capabilities: [148] Device Serial Number 00-00-00-00-10-ec-81-68 Capabilities: [154] Power Budgeting Kernel driver in use: r8169 Kernel modules: r8169 ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Attachment added: "lspci-vv.txt" https://bugs.launchpad.net/bugs/1906655/+attachment/5440611/+files/lspci-vv.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/1906655 Title: Ethernet interface broken (Flags mismatch irq) after upgrading to kernel 5.8.0-31 Status in linux package in Ubuntu: Incomplete Bug description: Realtek ethernet network interface is broken when booting with kernel 5.8.0-31. It works fine when simply booting with previous kernel 5.8.0-29 in GRUB. No other packages were updated. The only related line in /var/log/kern.log: Dec 3 14:01:21 hd kernel: [ 17.824691] genirq: Flags mismatch irq 16. 00010080 (enp4s0) vs. 2080 (uhci_hcd:usb3) `lspci -v` for this network interface below (`lspci -vv` attached): 04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 01) Subsystem: Gigabyte Technology Co., Ltd Onboard Ethernet Flags: bus master, fast devsel, latency 0, IRQ 16 I/O ports at d000 [size=256] Memory at f800 (64-bit, non-prefetchable) [size=4K] Expansion ROM at f700 [virtual] [disabled] [size=128K] Capabilities: [40] Power Management version 2 Capabilities: [48] Vital Product Data Capabilities: [50] MSI: Enable- Count=1/2 Maskable- 64bit+ Capabilities: [60] Express Endpoint, MSI 00 Capabilities: [84] Vendor Specific Information: Len=4c Capabilities: [100] Advanced Error Reporting Capabilities: [12c] Virtual Channel Capabilities: [148] Device Serial Number 00-00-00-00-10-ec-81-68 Capabilities: [154] Power Budgeting Kernel driver in use: r8169 Kernel modules: r8169 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1906655/+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 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
Disappointing. I've just ordered a 1mii B10 USB Bluetooth 5.0 Audio Transmitter as a workaround... -- 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/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Triaged Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+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 1903798] Re: Some Dell RKL AIO platform with e1000e require quirk to enter s0ix
We will have to rework this patch when we merge v2 (or any after) for https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.10/+bug/1902687. -- 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/1903798 Title: Some Dell RKL AIO platform with e1000e require quirk to enter s0ix Status in OEM Priority Project: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux source package in Hirsute: In Progress Bug description: [Impact] The RKL-S system with I219LM NIC resume automatically while entering s2i. [Fix] Have to add those product sku into e1000e quirk. [Test] Verified on RKL platform with I219LM NIC [Regression Potential] Low, only affects the platforms listed in the quirk. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1903798/+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 1906229] Re: Refresh ACPI wakeup power to make Thunderbolt hotplug detection work
** Changed in: linux-oem-5.6 (Ubuntu Focal) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1906229 Title: Refresh ACPI wakeup power to make Thunderbolt hotplug detection work Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Status in linux-oem-5.6 source package in Focal: Fix Committed Status in linux source package in Groovy: In Progress Status in linux-oem-5.6 source package in Groovy: Invalid Bug description: [Impact] Dell Precision 5550 cannot detect Thunderbolt device hotplug. [Fix] Refresh ACPI wakeup power if it's already enabled to make GPE work. [Test] Make sure the root port of TBT hierachy is in D3cold. Plug a Thunderbolt Dock or Thunderbolt Disk, the system cannot detect anything. With the patch applied, OS can always detect hotplugged Thunderbolt devices. [Where problems could occur] Though we refresh the wakeup device power, we didn't disable/enable ACPI GPEs, so we won't miss any GPE event from this fix. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1906229/+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 1904221] Re: Ask 8821C Bluetooth controller to drop old firmware
** Changed in: linux-oem-5.6 (Ubuntu Focal) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1904221 Title: Ask 8821C Bluetooth controller to drop old firmware Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Status in linux-oem-5.6 source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Committed Status in linux-oem-5.6 source package in Groovy: Invalid Bug description: [Impact] Some platforms may keep USB power in S3/S4/S5, so Realtek 8821C retains its firmware even with a cold boot. [Fix] Use vendor command to drop firmware if the version is old. [Test case] Use dmesg to check if new firmware is loaded. With the patch applied, we can find new firmware is loaded. [Where problems could occur] There's a 200ms delay which can slow down when BT controller is opened by userspace first time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904221/+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 1904430] Re: Fix AMD GFX where no HDMI audio when hotplugging different monitors
** Changed in: linux-oem-5.6 (Ubuntu Focal) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1904430 Title: Fix AMD GFX where no HDMI audio when hotplugging different monitors Status in HWE Next: New Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux-oem-5.6 source package in Focal: Fix Committed Bug description: [Impact] Hotplugging different monitors on different ports makes HDMI audio disappears. [Fix] Make sure new EDID is added. [Test case] Boot up with a HDMI monitor with audio output, unplug the monitor and plug another monitor without speaker and without audio jack. Then plug back the original monitor. With the patch applied, there's still HDMI audio output from the original monitor. [Where problems could occur] If the EDID is valid, the driver does the correct thing. If the EDID is invalid, then the driver spends a bit more time setting up EDID, without doing any harm. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1904430/+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 1904521] Re: Intel Tiger Lake IDs supplement
** Changed in: linux-oem-5.6 (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1904521 Title: Intel Tiger Lake IDs supplement Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux-oem-5.6 source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Committed Bug description: [Impact] Intel Tiger Lake-H platform requires new pin settings and IDs to enable. [Fix] Intel provides us a list of TGL-H commits from 5.8 and 5.9, we need all of the commits to enable TGL-H platforms completely. [Test] Verified those commits on Intel TGL-H SDP [Regression potential] Low, all of those commits are adding new IDs for TGL-H platform. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1904521/+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 1904595] Re: Fix no headset sound after S3 on Intel HDA
** Changed in: linux-oem-5.6 (Ubuntu Focal)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1904595
Title:
Fix no headset sound after S3 on Intel HDA
Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-5.6 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Won't Fix
Status in linux-oem-5.6 source package in Focal:
Fix Committed
Status in linux source package in Groovy:
Fix Committed
Status in linux-oem-5.6 source package in Groovy:
Invalid
Bug description:
[Impact]
After system S3, hotplugging headset cannot produce any sound despite of
being auto-selected as audio output.
[Fix]
Avoid using pm_runtime_force_{suspend,resume} helpers to ensure codec
suspend/resume flow, and also ensure HDA driver and PCI set correct
wakeup settings.
[Test case]
Plug headset, unplug headset, switch audio ouput from speakers to HDMI
to let Intel HDA auto suspend. Suspend/resume the system, plug the
headset again, hear no sound.
With the patch series applied, the issue is gone.
[Where problems could occur]
If there is bad firmware/hardware that makes codec have system-wide
wakeup capability, direct-complete flow may trigger unwanted system
wakeup or even break system suspend. The series was tested on both AMD
and Intel platforms, with Realtek and Connexant codecs respectively.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1904595/+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 1905663] Re: Add dpcd backlight control for 0x4c83 0x4f41
** Changed in: linux-oem-5.6 (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1905663 Title: Add dpcd backlight control for 0x4c83 0x4f41 Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Status in linux-oem-5.6 source package in Focal: Fix Committed Status in linux source package in Groovy: In Progress Status in linux source package in Hirsute: In Progress Bug description: [Impact] There is a new OLED panel that is required to be listed in the EDID quirk to make its backlight work. [Fix] The commit adds its EDID to the quirk. https://lkml.org/lkml/2020/11/19/1564 [Test] Verified on Dell's platform with this panel. [Where problems could occur] Only if this panel switches to use PWM mode only, and doesn't support DPCD backlight. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1905663/+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 1878919] Re: kworker/0:1+kacpid uses 100% of one CPU core
This bug is affecting me too on Ubuntu 20.04 on a Macbook Pro 15". Took me several installations and quite some hours to figure out, what the reason for misbehaving and overheating was, should have launched top right away. For me the workaround with suspending after boot works fine, too. But it is also kind of annoying to suspend once after booting the computer. -- 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/1878919 Title: kworker/0:1+kacpid uses 100% of one CPU core Status in linux package in Ubuntu: Expired Bug description: At some point, kworker/0:1+kacpid starts using 100% of one CPU's core; this can be seen in the top command. I captured some performance data via the following command: $ perf record -g -a sleep 10 Then, perf report gives the following: Samples: 75K of event 'cycles', Event count (approx.): 44710762967 Children Self Command Shared Object Symbol + 65,46% 0,00% kworker/0:1+kac [kernel.kallsyms] [k] ret_from_fork + 65,46% 0,00% kworker/0:1+kac [kernel.kallsyms] [k] kthread + 65,46% 0,00% kworker/0:1+kac [kernel.kallsyms] [k] worker_thread + 65,44% 0,00% kworker/0:1+kac [kernel.kallsyms] [k] process_one_work + 65,44% 0,00% kworker/0:1+kac [kernel.kallsyms] [k] acpi_os_execute_deferred + 65,33% 0,00% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ev_asynch_execute_gpe_method + 65,32% 0,00% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ns_evaluate + 65,26% 0,00% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ps_execute_method + 65,16% 0,06% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ps_parse_aml + 61,00% 0,94% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ps_parse_loop + 37,83% 0,75% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ds_exec_end_op + 18,33% 0,04% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ds_evaluate_name_path + 16,12% 0,23% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ns_lookup + 15,79% 0,20% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ns_search_and_enter + 15,23%14,99% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ns_search_one_scope + 14,38% 0,00% swapper [kernel.kallsyms] [k] secondary_startup_64 + 14,38% 0,02% swapper [kernel.kallsyms] [k] cpu_startup_entry + 14,31% 0,12% swapper [kernel.kallsyms] [k] do_idle + 13,79% 0,00% swapper [kernel.kallsyms] [k] start_secondary + 12,92% 0,03% swapper [kernel.kallsyms] [k] call_cpuidle + 12,89% 0,00% swapper [kernel.kallsyms] [k] cpuidle_enter + 12,85% 0,05% swapper [kernel.kallsyms] [k] cpuidle_enter_state + 12,35% 2,15% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ut_update_object_reference + 12,05% 0,28% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ex_resolve_to_value + 10,40% 0,04% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ex_resolve_node_to_value +9,90% 0,44% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ds_create_operand +9,50% 0,05% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ex_read_data_from_field +9,39% 0,06% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ex_field_datum_io +9,26% 0,12% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ex_access_region +9,23% 0,08% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ps_get_next_namepath +9,15% 1,28% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ut_update_ref_count.part.0 +9,01% 0,08% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ev_address_space_dispatch +8,96% 0,14% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ex_extract_from_field +8,78% 7,70% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ex_system_memory_space_handler +7,81% 0,22% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ut_remove_reference +6,63% 6,43% swapper [kernel.kallsyms] [k] intel_idle +5,31% 0,68% kworker/0:1+kac [kernel.kallsyms]
[Kernel-packages] [Bug 1903619] Re: Boot hangs with Ubuntu 20.04 on Lenovo ThinkPad L390
For the record: I kept the default kernel for 20.04 (5.4.0-56-generic), but the problem did not surface for the last three weeks. There were two or three minor kernel updates. No idea whether that fixed anything. -- 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/1903619 Title: Boot hangs with Ubuntu 20.04 on Lenovo ThinkPad L390 Status in linux package in Ubuntu: Confirmed Bug description: Filing this bug as per request of Rex Tsai. This is a follow-up to: https://answers.launchpad.net/ubuntu-certification/+question/693893 Synopsis: after powering off, the machine sometimes hangs on the next start. I also added some screenshots there. The interface here only allows a single attachment. Output of fwupdmgr get-devices: 20NR001EGE │ ├─SAMSUNG MZVLB512HAJQ-000L7: │ Device ID: 3743975ad7f64f8d6575a9ae49fb3a8856fe186f │ Summary: NVM Express Solid State Drive │ Current version: 5L2QEXA7 │ Vendor: Samsung Electronics Co Ltd (NVME:0x144D) │ GUIDs: 6e54c992-d302-59ab-b454-2d26ddd63e6d │ 47335265-a509-51f7-841e-1c94911af66b │ 79d6cfae-a5a2-5936-9248-5aebd23480f7 │ Device Flags: • Internal device │ • Updatable │ • Requires AC power │ • Supported on remote server │ • Needs a reboot after installation │ • Device is usable for the duration of the update │ ├─System Firmware: │ Device ID: 7eca2f04c4c15ff7cf11f74503846da436b2dff3 │ Current version: 0.1.31 │ Minimum Version: 0.0.1 │ Vendor: LENOVO (DMI:LENOVO) │ GUID: 7d78a18a-80db-4a65-a955-b79f8ca2a334 │ Device Flags: • Internal device │ • Updatable │ • Requires AC power │ • Needs a reboot after installation │ • Cryptographic hash verification is available │ • Device is usable for the duration of the update │ ├─UEFI Device Firmware: │ Device ID: 6461040534f2259a0439361986adf73979fd836e │ Current version: 192.68.1606 │ Minimum Version: 0.0.1 │ Vendor: DMI:LENOVO │ GUID: c35736d2-9e47-4578-93e9-68d5b04ea77e │ Device Flags: • Internal device │ • Updatable │ • Requires AC power │ • Supported on remote server │ • Needs a reboot after installation │ • Device is usable for the duration of the update │ ├─UEFI Device Firmware: │ Device ID: ef9c8dc313296d8f84c1815e89219f8ef6948b98 │ Current version: 1.1.4385 │ Minimum Version: 0.0.1 │ Vendor: DMI:LENOVO │ GUID: cb04e55e-456d-41f4-a9ec-24071f5a1f0f │ Device Flags: • Internal device │ • Updatable │ • Requires AC power │ • Needs a reboot after installation │ • Device is usable for the duration of the update │ └─UEFI Device Firmware: Device ID: 2d2892da83e97f5a5cd203a1d03dfe7e50d713c2 Current version: 0.73.64 Minimum Version: 0.73.64 Vendor: DMI:LENOVO GUID: 452fb595-c800-4a96-93c4-9668cc335373 Device Flags: • Internal device • Updatable • Requires AC power • Needs a reboot after installation • Device is usable for the duration of the update Output of fwupdmgr get-updates: • SAMSUNG MZVLB512HAJQ-000L7 has the latest available firmware version • System Firmware has no available firmware updates • UEFI Device Firmware has the latest available firmware version • UEFI Device Firmware has no available firmware updates • UEFI Device Firmware has no available firmware updates ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-52-generic 5.4.0-52.57 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: erwin 1430 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 10 02:30:34 2020 InstallationDate: Installed on 2020-11-04 (5 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" -
[Kernel-packages] [Bug 1906168] Re: Prevent thermal shutdown during boot process
** Also affects: linux-oem-5.10 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-5.10 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1906168 Title: Prevent thermal shutdown during boot process Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.10 source package in Focal: New Status in linux-oem-5.6 source package in Focal: Fix Committed Status in linux source package in Groovy: New Status in linux source package in Hirsute: Incomplete Bug description: [Impact] Surprising thermal shutdown at boot on Intel based mobile workstations. [Fix] Since these thermal devcies are not in ACPI ThermalZone, OS shouldn't shutdown the system. These critial temperatures are for usespace to handle, so let kernel know it shouldn't handle it. SRU for stable kernels will be sent after the fix is in upstream. [Test] Use reboot stress as a reproducer. 5% chance to see a surprising shutdown at boot. With the fix applied, the thermal shutdown is no longer reproducible. [Where problems could occur] For ACPI based platforms, we still have "acpitz" to protect systems from overheating. If these acpitz sensors don't work, then the system could face real overheating issue. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1906168/+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 1906229] Re: Refresh ACPI wakeup power to make Thunderbolt hotplug detection work
** Changed in: linux (Ubuntu) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Focal) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu Groovy) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1906229 Title: Refresh ACPI wakeup power to make Thunderbolt hotplug detection work Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Status in linux-oem-5.6 source package in Focal: Confirmed Status in linux source package in Groovy: In Progress Status in linux-oem-5.6 source package in Groovy: Invalid Bug description: [Impact] Dell Precision 5550 cannot detect Thunderbolt device hotplug. [Fix] Refresh ACPI wakeup power if it's already enabled to make GPE work. [Test] Make sure the root port of TBT hierachy is in D3cold. Plug a Thunderbolt Dock or Thunderbolt Disk, the system cannot detect anything. With the patch applied, OS can always detect hotplugged Thunderbolt devices. [Where problems could occur] Though we refresh the wakeup device power, we didn't disable/enable ACPI GPEs, so we won't miss any GPE event from this fix. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1906229/+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 1890130] Re: Add support for Intel Bluetooth Device Typhoon Peak (8087:0032)
** Also affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-firmware (Ubuntu Hirsute) Status: New => Invalid ** Changed in: linux-firmware (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-firmware (Ubuntu Focal) Assignee: (unassigned) => You-Sheng Yang (vicamo) -- 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/1890130 Title: Add support for Intel Bluetooth Device Typhoon Peak (8087:0032) Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-firmware package in Ubuntu: Invalid Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: Incomplete Status in linux-firmware source package in Focal: In Progress Status in linux-oem-5.10 source package in Focal: Incomplete Status in linux-oem-5.6 source package in Focal: Invalid Status in linux source package in Groovy: New Status in linux-firmware source package in Groovy: New Status in linux-oem-5.10 source package in Groovy: Invalid Status in linux-oem-5.6 source package in Groovy: Invalid Status in linux source package in Hirsute: Incomplete Status in linux-firmware source package in Hirsute: Invalid Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.6 source package in Hirsute: Invalid Bug description: Device from /sys/kernel/debug/usb/devices: T: Bus=01 Lev=01 Prnt=01 Port=13 Cnt=02 Dev#= 3 Spd=12 MxCh= 0 D: Ver= 2.01 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=8087 ProdID=0032 Rev= 0.00 Prerequisite commits: * https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=875e16759005e3bdaa84eb2741281f37ba35b886 * https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3e4e3f73b9f4 And: https://patchwork.kernel.org/project/bluetooth/list/?series=387475 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1890130/+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 1902848] Re: Support Intel AX210 wifi [8086:2725] Subsystem [8086:0020]
** Changed in: linux-firmware (Ubuntu Focal) Status: Confirmed => In Progress ** Changed in: linux-firmware (Ubuntu Focal) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Changed in: linux-firmware (Ubuntu Focal) Importance: Undecided => High ** Changed in: linux (Ubuntu Hirsute) Importance: Undecided => High ** Changed in: linux (Ubuntu Hirsute) Status: Incomplete => In Progress ** Changed in: linux-oem-5.10 (Ubuntu Focal) Importance: Undecided => High ** Changed in: linux-oem-5.10 (Ubuntu Focal) Status: Incomplete => In Progress ** Changed in: linux-oem-5.10 (Ubuntu Focal) Assignee: (unassigned) => You-Sheng Yang (vicamo) -- 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/1902848 Title: Support Intel AX210 wifi [8086:2725] Subsystem [8086:0020] Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Invalid Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-firmware source package in Focal: In Progress Status in linux-oem-5.10 source package in Focal: In Progress Status in linux source package in Groovy: Incomplete Status in linux-firmware source package in Groovy: Confirmed Status in linux-oem-5.10 source package in Groovy: Invalid Status in linux source package in Hirsute: In Progress Status in linux-firmware source package in Hirsute: Invalid Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: Firmware: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/iwlwifi-ty-a0-gf-a0-59.ucode?id=4f41e9d6437d03e7ce9279076107dd08f46656f3 Kernel v5.10-rc1 or newer. 04:00.0 Network controller [0280]: Intel Corporation Device [8086:2725] (rev 1a) Subsystem: Intel Corporation Device [8086:0020] 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: iwlwifi Kernel modules: iwlwifi Bluetooth part in bug 1890130. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-10-13 (22 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 100: ID 8087:0032 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel Corporation Rocket Lake Client Platform Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1-generic root=UUID=221267f2-0315-4b8c-98c3-6e791d5615fc ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.10.0-1.2-generic 5.10.0-rc2 RelatedPackageVersions: linux-restricted-modules-5.10.0-1-generic N/A linux-backports-modules-5.10.0-1-generic N/A linux-firmware1.190 RfKill: Tags: focal Uname: Linux 5.10.0-1-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: False acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie Error executing command as another user: Not authorized This incident has been reported. dmi.bios.date: 08/20/2020 dmi.bios.vendor: Intel Corporation dmi.bios.version: RKLSFWI1.R00.1344.A00.2008202030 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: RocketLake S UDIMM 6L RVP dmi.board.vendor: Intel Corporation dmi.board.version: 1 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.4 dmi.modalias: dmi:bvnIntelCorporation:bvrRKLSFWI1.R00.1344.A00.2008202030:bd08/20/2020:efr1.4:svnIntelCorporation:pnRocketLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnRocketLakeSUDIMM6LRVP:rvr1:cvnIntelCorporation:ct3:cvr0.1: dmi.product.family: Rocket Lake Client System
[Kernel-packages] [Bug 1903682] Re: NULL pointer dereference when configuring multi-function with devfn != 0 before devfn == 0
** Changed in: linux (Ubuntu Groovy)
Assignee: Frank Heimes (fheimes) => (unassigned)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1903682
Title:
NULL pointer dereference when configuring multi-function with devfn !=
0 before devfn == 0
Status in Ubuntu on IBM z Systems:
In Progress
Status in linux package in Ubuntu:
Triaged
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Groovy:
In Progress
Status in linux source package in Hirsute:
Triaged
Bug description:
SRU Justification:
==
[Impact]
* While handling multifunction devices in zPCI the UID of the PCI
function with function number 0 (that always exists according to the
PCI spec) is taken as domain number.
* Therefore if hot plugging functions with a function number larger
than 0 are used before function 0, these need to be held in standby
before creating the domain and bus.
* This has been tested during development of this feature using a
patched QEMU and in DPM, but unfortunately never in
classic/traditional HMC mode.
* On a classic/traditional mode machine with a multi-function device,
and hot plug ("Reassign I/O Path") of the FID of the second port of
the LPAR, any additional hotplug (and even just deconfiguring a PCI
device) will hang - and hotplug now makes the entire Linux instance
unresponsive.
* The reason for this is a NULL pointer dereference - inc case
configuring multi-function with devfn != 0 before devfn == 0.
* This issue was introduced with the topology-aware PCI enumeration
code.
[Fix]
* 0b2ca2c7d0c9e2731d01b6c862375d44a7e13923 0b2ca2c7d0c9 "s390/pci: fix
hot-plug of PCI function missing bus"
[Test Case]
* IBM Z or LinuxONE hardware, equipped with hot-pluggable, multi-
functional PCIe cards (like for example RoCE Express 2 adapters) in
classic/traditional mode.
* An Ubuntu OS running in LPAR, that comes with a kernel that includes
the topology-aware PCI enumeration code (like for example 20.04.1 w/o
further updates or 20.10 GA kernel).
* Now on a system that is in classic/traditional mode, hot plug
("Reassign I/O Path") a multi-function device, but using the FID of
the second port.
[Regression Potential]
* There is at least some regression risk, but I consider it as low,
because:
* Even is the modification is a single if statement (that spans two
lines) in 'zpci_event_availability' it could harm the zPCI event
management even more, in worst case it could break hot plug not only
for systems in classic/traditional mode, but also in DPM mode (and
making the system hang) or for all ports.
* In such a case no enabling / disabling of devices would be possible.
* But the fix is very simple and straight-forward, it checks
zdev->zbus->bus for being NULL and in such a case break the function -
means breaking instead of calling the PCI common code
pci_scan_single_device() with the NULL pointer.
* PCIe devices are usually more optional devices on s390x (compared to
CCW and OSA devices for network) and this affects the zPCI subsystem
only, which is unique to s390x.
[Other]
* The patch got upstream accepted with kernel v5.10-rc3, hence it will
land sooner or later in Hirsute.
* It was initially planned to address groovy via 5.8 upstream stable
update, and in fact the patch was already marked for this, but it
didn't made it because 5.8 reached it's EOL already.
* Hence in addition to the already submitted SRU for focal, this is now a
separate SRU for groovy.
__
Background:
When handling multifunction devices in zPCI we take the
UID of the PCI function with function number 0
(that always exists according to the PCI spec)
as domain number.
Therefore when hot plugging functions with function
number larger than 0 before function 0, we need
to hold these in standby before creating the
domain and bus.
This has been tested during feature development
using a patched QEMU and with DPM but never in Classic
Mode.
Reproduction:
This issue was introduced with the Topology aware PCI
Enumeration code so test with a Linux supporting
that feature. E.g. Upstream, Devel Driver etc.
On a Classic Mode machine with a multi-function device,
hot plug ("Reassign I/O Path") only the FID of the
second port to the LPAR.
Symptom:
After this any additional hotplug and even just
deconfiguring a PCI device will hang. A hotplug
makes the entire Linux instance unresponsive.
Analysis:
The problem occurs in Classic Mode but not with
previous testing as the LPAR hypervisor does
hot plug/Reassign I/O Path as a two step process:
1. zPCI event with PEC 0x0302 to plug the zPCI function in Standby
2. zPCI event with PEC 0x0301 to configure the zPCI function
For the first event we create
[Kernel-packages] [Bug 1906255] Re: [UBUNTU 20.10] Applications runing in QEMU/KVM get translation faults
** Changed in: ubuntu-z-systems
Status: Triaged => In Progress
** Changed in: linux (Ubuntu Groovy)
Assignee: Frank Heimes (fheimes) => (unassigned)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1906255
Title:
[UBUNTU 20.10] Applications runing in QEMU/KVM get translation faults
Status in Ubuntu on IBM z Systems:
In Progress
Status in linux package in Ubuntu:
New
Status in linux source package in Groovy:
In Progress
Bug description:
SRU Justification:
==
[Impact]
* The commit 0b0ed657fe "s390: remove critical section cleanup from
entry.S" was introduced in kernel 5.8, but instigated a problem where
FPU registers were not properly restored when entering the SIE (start
interpretive execution) instruction.
* This leads to crashes of applications runnning inside KVM, as most
of the programs in use nowdays are using FPU registers for backing of
general register content.
* To fix this interrupts in load_fpu_regs() need to be disabled -
otherwise an interrupt might come in after the registers are loaded,
but before CIF_FPU is cleared in load_fpu_regs().
* When the interrupt returns, CIF_FPU will be cleared and the
registers will never be restored.
[Fix]
* 1179f170b6f0af7bb0b3b7628136eaac450ddf31 1179f170b6f0 "s390: fix fpu
restore in entry.S"
[Test Case]
* IBM Z or LinuxONE hardware with Ubuntu Server 20.10 installed.
* A KVM host needs to be setup as well as an KVM guest (use again
20.10).
* Run (ideally context switching) workload that makes use of FP
instructions inside of the KVM guest.
* Monitor the health of the guest for crashes (logs).
[Regression Potential]
* Even if the code changes are quite overseeable, there is still a
certain risk for regression, because:
* the modifications affect a critical part of the kernel
(arch/s390/kernel/entry.S)
* affect the handling of the FPU registers
* and are always in use if KVM guests run
* So in worst case the changes may have an even bigger impact on FPU
workloads in KVM guests
* and may not only crash in case of FPU usage, but also KVM in
general.
* But the code is peurly s390x specific, hence affects IBM Z only,
* and it got already upstream accepted with v5.10-rc6
* and a test kernel (based on groovy master-next) was build for
further testing.
[Other]
* The patch got upstream accepted with kernel v5.10-rc6, hence it will
land sooner or later in Hirsute.
* It was initially planned to address groovy via 5.8 upstream stable
update, and in fact the patch was already marked for this, but it
didn't made it because 5.8 already reached it's EOL.
* Hence this SRU is submitted for groovy only.
__
commit 0b0ed657fe ("s390: remove critical section cleanup from
entry.S") introduced a problem where FPU registers were not properly
restored when entering SIE. This leads to crashes of applications
runnning inside kvm, as most of the programs in use nowdays are using
FPU registers for backing of general register content.
Fix is upstream:
authorSven Schnelle 2020-11-20 14:17:52
+0100
committer Heiko Carstens 2020-11-23 11:52:13
+0100
commit1179f170b6f0af7bb0b3b7628136eaac450ddf31 (patch)
tree 19e8acb64e0968b41de4899cc1315c41b002839e /arch/s390/kernel/entry.S
parent78d732e1f326f74f240d416af9484928303d9951 (diff)
download linux-1179f170b6f0af7bb0b3b7628136eaac450ddf31.tar.gz
s390: fix fpu restore in entry.S
We need to disable interrupts in load_fpu_regs(). Otherwise an
interrupt might come in after the registers are loaded, but before
CIF_FPU is cleared in load_fpu_regs(). When the interrupt returns,
CIF_FPU will be cleared and the registers will never be restored.
The entry.S code usually saves the interrupt state in __SF_EMPTY on the
stack when disabling/restoring interrupts. sie64a however saves the pointer
to the sie control block in __SF_SIE_CONTROL, which references the same
location. This is non-obvious to the reader. To avoid thrashing the sie
control block pointer in load_fpu_regs(), move the __SIE_* offsets eight
bytes after __SF_EMPTY on the stack.
Cc: # 5.8
Fixes: 0b0ed657fe00 ("s390: remove critical section cleanup from entry.S")
Reported-by: Pierre Morel
Signed-off-by: Sven Schnelle
Acked-by: Christian Borntraeger
Reviewed-by: Heiko Carstens
Signed-off-by: Heiko Carstens
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1906255/+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 1861235] Re: zfs recv PANIC at range_tree.c:304:range_tree_find_impl()
My guess is the next step is trying the zfs send | ssh zfs recv commands that were causing the VERIFY(size != 0) failed message with traces. I've always been uneasy with the 'main' error coming only with a recv operation, relying upon two systems to recreate a bug is iffy at best. And since it wedges the one, I don't like doing it just for fun, but I'd also like to get to the bottom of this. Is there anything else to try first? Thanks -- 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/1861235 Title: zfs recv PANIC at range_tree.c:304:range_tree_find_impl() Status in Linux: New Status in zfs-linux package in Ubuntu: Incomplete Status in zfs-linux source package in Bionic: New Bug description: Same as bug 1861228 but with a newer kernel installed. [ 790.702566] VERIFY(size != 0) failed [ 790.702590] PANIC at range_tree.c:304:range_tree_find_impl() [ 790.702611] Showing stack for process 28685 [ 790.702614] CPU: 17 PID: 28685 Comm: receive_writer Tainted: P O 4.15.0-76-generic #86-Ubuntu [ 790.702615] Hardware name: Supermicro SSG-6038R-E1CR16L/X10DRH-iT, BIOS 2.0 12/17/2015 [ 790.702616] Call Trace: [ 790.702626] dump_stack+0x6d/0x8e [ 790.702637] spl_dumpstack+0x42/0x50 [spl] [ 790.702640] spl_panic+0xc8/0x110 [spl] [ 790.702645] ? __switch_to_asm+0x41/0x70 [ 790.702714] ? arc_prune_task+0x1a/0x40 [zfs] [ 790.702740] ? dbuf_dirty+0x43d/0x850 [zfs] [ 790.702745] ? getrawmonotonic64+0x43/0xd0 [ 790.702746] ? getrawmonotonic64+0x43/0xd0 [ 790.702775] ? dmu_zfetch+0x49a/0x500 [zfs] [ 790.702778] ? getrawmonotonic64+0x43/0xd0 [ 790.702805] ? dmu_zfetch+0x49a/0x500 [zfs] [ 790.702807] ? mutex_lock+0x12/0x40 [ 790.702833] ? dbuf_rele_and_unlock+0x1a8/0x4b0 [zfs] [ 790.702866] range_tree_find_impl+0x88/0x90 [zfs] [ 790.702870] ? spl_kmem_zalloc+0xdc/0x1a0 [spl] [ 790.702902] range_tree_clear+0x4f/0x60 [zfs] [ 790.702930] dnode_free_range+0x11f/0x5a0 [zfs] [ 790.702957] dmu_object_free+0x53/0x90 [zfs] [ 790.702983] dmu_free_long_object+0x9f/0xc0 [zfs] [ 790.703010] receive_freeobjects.isra.12+0x7a/0x100 [zfs] [ 790.703036] receive_writer_thread+0x6d2/0xa60 [zfs] [ 790.703040] ? set_curr_task_fair+0x2b/0x60 [ 790.703043] ? spl_kmem_free+0x33/0x40 [spl] [ 790.703048] ? kfree+0x165/0x180 [ 790.703073] ? receive_free.isra.13+0xc0/0xc0 [zfs] [ 790.703078] thread_generic_wrapper+0x74/0x90 [spl] [ 790.703081] kthread+0x121/0x140 [ 790.703084] ? __thread_exit+0x20/0x20 [spl] [ 790.703085] ? kthread_create_worker_on_cpu+0x70/0x70 [ 790.703088] ret_from_fork+0x35/0x40 [ 967.636923] INFO: task txg_quiesce:14810 blocked for more than 120 seconds. [ 967.636979] Tainted: P O 4.15.0-76-generic #86-Ubuntu [ 967.637024] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 967.637076] txg_quiesce D0 14810 2 0x8000 [ 967.637080] Call Trace: [ 967.637089] __schedule+0x24e/0x880 [ 967.637092] schedule+0x2c/0x80 [ 967.637106] cv_wait_common+0x11e/0x140 [spl] [ 967.637114] ? wait_woken+0x80/0x80 [ 967.637122] __cv_wait+0x15/0x20 [spl] [ 967.637210] txg_quiesce_thread+0x2cb/0x3d0 [zfs] [ 967.637278] ? txg_delay+0x1b0/0x1b0 [zfs] [ 967.637286] thread_generic_wrapper+0x74/0x90 [spl] [ 967.637291] kthread+0x121/0x140 [ 967.637297] ? __thread_exit+0x20/0x20 [spl] [ 967.637299] ? kthread_create_worker_on_cpu+0x70/0x70 [ 967.637304] ret_from_fork+0x35/0x40 [ 967.637326] INFO: task zfs:28590 blocked for more than 120 seconds. [ 967.637371] Tainted: P O 4.15.0-76-generic #86-Ubuntu [ 967.637416] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 967.637467] zfs D0 28590 28587 0x8080 [ 967.637470] Call Trace: [ 967.637474] __schedule+0x24e/0x880 [ 967.637477] schedule+0x2c/0x80 [ 967.637486] cv_wait_common+0x11e/0x140 [spl] [ 967.637491] ? wait_woken+0x80/0x80 [ 967.637498] __cv_wait+0x15/0x20 [spl] [ 967.637554] dmu_recv_stream+0xa51/0xef0 [zfs] [ 967.637630] zfs_ioc_recv_impl+0x306/0x1100 [zfs] [ 967.637679] ? dbuf_read+0x34a/0x920 [zfs] [ 967.637725] ? dbuf_rele+0x36/0x40 [zfs] [ 967.637728] ? _cond_resched+0x19/0x40 [ 967.637798] zfs_ioc_recv_new+0x33d/0x410 [zfs] [ 967.637809] ? spl_kmem_alloc_impl+0xe5/0x1a0 [spl] [ 967.637816] ? spl_vmem_alloc+0x19/0x20 [spl] [ 967.637828] ? nv_alloc_sleep_spl+0x1f/0x30 [znvpair] [ 967.637834] ? nv_mem_zalloc.isra.0+0x2e/0x40 [znvpair] [ 967.637840] ? nvlist_xalloc.part.2+0x50/0xb0 [znvpair] [ 967.637905] zfsdev_ioctl+0x451/0x610 [zfs] [ 967.637913] do_vfs_ioctl+0xa8/0x630 [ 967.637917] ? __audit_syscall_entry+0xbc/0x110 [ 967.637924] ?
[Kernel-packages] [Bug 1861235] Re: zfs recv PANIC at range_tree.c:304:range_tree_find_impl()
The scrub has finished, no new errors in zpool status -v, dmesg is filled with debugging messages, I hope something is useful. :) Thanks $ uname -a Linux wopr 4.15.0-126-generic #129-Ubuntu SMP Mon Nov 23 18:53:38 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux $ modinfo zfs | grep -i version version:0.7.5-1ubuntu16.10+lp1861235 srcversion: 62D1F1B1A1EE81EB3AA8ABA $ zpool status -v pool: fst state: ONLINE scan: scrub repaired 0B in 2h37m with 0 errors on Sun Nov 8 03:01:53 2020 config: NAMESTATE READ WRITE CKSUM fst ONLINE 0 0 0 raidz1-0 ONLINE 0 0 0 wwn-0x5002538e4095da39 ONLINE 0 0 0 wwn-0x5002538e4095bdd6 ONLINE 0 0 0 wwn-0x5002538e4093c6fd ONLINE 0 0 0 wwn-0x5002538e4095da30 ONLINE 0 0 0 errors: No known data errors pool: srv state: ONLINE scan: scrub repaired 0B in 4h12m with 0 errors on Wed Dec 2 18:53:44 2020 config: NAME STATE READ WRITE CKSUM srv ONLINE 0 0 0 mirror-0 ONLINE 0 0 0 ata-HGST_HUS724030ALA640_PN2234P8KTWJYY ONLINE 0 0 0 ata-HGST_HUS724030ALA640_PN2234P9G620TW ONLINE 0 0 0 ata-HGST_HUS724030ALA640_PN2234P9G66E2U ONLINE 0 0 0 mirror-1 ONLINE 0 0 0 ata-HGST_HUS724030ALA640_PN2234P9G69TKU ONLINE 0 0 0 ata-HGST_HUS724030ALA640_PN2234P9G69TXU ONLINE 0 0 0 ata-HGST_HUS724030ALA640_PN2234P9G69U2U ONLINE 0 0 0 mirror-2 ONLINE 0 0 0 ata-HGST_HUS724030ALA640_PN2234P9G6EBUU ONLINE 0 0 0 ata-HGST_HUS724030ALA640_PN2234P9G6ESAU ONLINE 0 0 0 ata-HGST_HUS724030ALA640_PN2234P9G6G70U ONLINE 0 0 0 logs nvme0n1p1 ONLINE 0 0 0 cache nvme0n1p2 ONLINE 0 0 0 errors: No known data errors ** Attachment added: "journalctl -b output" https://bugs.launchpad.net/linux/+bug/1861235/+attachment/5440572/+files/journalctl-b -- 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/1861235 Title: zfs recv PANIC at range_tree.c:304:range_tree_find_impl() Status in Linux: New Status in zfs-linux package in Ubuntu: Incomplete Status in zfs-linux source package in Bionic: New Bug description: Same as bug 1861228 but with a newer kernel installed. [ 790.702566] VERIFY(size != 0) failed [ 790.702590] PANIC at range_tree.c:304:range_tree_find_impl() [ 790.702611] Showing stack for process 28685 [ 790.702614] CPU: 17 PID: 28685 Comm: receive_writer Tainted: P O 4.15.0-76-generic #86-Ubuntu [ 790.702615] Hardware name: Supermicro SSG-6038R-E1CR16L/X10DRH-iT, BIOS 2.0 12/17/2015 [ 790.702616] Call Trace: [ 790.702626] dump_stack+0x6d/0x8e [ 790.702637] spl_dumpstack+0x42/0x50 [spl] [ 790.702640] spl_panic+0xc8/0x110 [spl] [ 790.702645] ? __switch_to_asm+0x41/0x70 [ 790.702714] ? arc_prune_task+0x1a/0x40 [zfs] [ 790.702740] ? dbuf_dirty+0x43d/0x850 [zfs] [ 790.702745] ? getrawmonotonic64+0x43/0xd0 [ 790.702746] ? getrawmonotonic64+0x43/0xd0 [ 790.702775] ? dmu_zfetch+0x49a/0x500 [zfs] [ 790.702778] ? getrawmonotonic64+0x43/0xd0 [ 790.702805] ? dmu_zfetch+0x49a/0x500 [zfs] [ 790.702807] ? mutex_lock+0x12/0x40 [ 790.702833] ? dbuf_rele_and_unlock+0x1a8/0x4b0 [zfs] [ 790.702866] range_tree_find_impl+0x88/0x90 [zfs] [ 790.702870] ? spl_kmem_zalloc+0xdc/0x1a0 [spl] [ 790.702902] range_tree_clear+0x4f/0x60 [zfs] [ 790.702930] dnode_free_range+0x11f/0x5a0 [zfs] [ 790.702957] dmu_object_free+0x53/0x90 [zfs] [ 790.702983] dmu_free_long_object+0x9f/0xc0 [zfs] [ 790.703010] receive_freeobjects.isra.12+0x7a/0x100 [zfs] [ 790.703036] receive_writer_thread+0x6d2/0xa60 [zfs] [ 790.703040] ? set_curr_task_fair+0x2b/0x60 [ 790.703043] ? spl_kmem_free+0x33/0x40 [spl] [ 790.703048] ? kfree+0x165/0x180 [ 790.703073] ? receive_free.isra.13+0xc0/0xc0 [zfs] [ 790.703078] thread_generic_wrapper+0x74/0x90 [spl] [ 790.703081] kthread+0x121/0x140 [ 790.703084] ? __thread_exit+0x20/0x20 [spl] [ 790.703085] ? kthread_create_worker_on_cpu+0x70/0x70 [ 790.703088] ret_from_fork+0x35/0x40 [ 967.636923] INFO: task txg_quiesce:14810 blocked for more than 120 seconds. [ 967.636979]
[Kernel-packages] [Bug 1906542] Re: echo 1 >> /sys/module/zfs/parameters/zfs_max_missing_tvds says premission error, unable to reapair lost zfs pool data
Is there anyone who could help me over go this bug so I can rescue my ZFS pool data, pool will be lost as I understand. I accidentaly added disk to pool and not as mirror what was intention,... and it can nor be removed even there is no data! -- 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/1906542 Title: echo 1 >> /sys/module/zfs/parameters/zfs_max_missing_tvds says premission error, unable to reapair lost zfs pool data Status in zfs-linux package in Ubuntu: New Bug description: root@jonipekka-desktop:~# echo 1 >> /sys/module/zfs/parameters/zfs_max_missing_tvds -bash: /sys/module/zfs/parameters/zfs_max_missing_tvds: Permission denied root@jonipekka-desktop:~# https://www.delphix.com/blog/openzfs-pool-import-recovery Import with missing top level vdevs The changes to the pool configuration logic have enabled another great improvement: the ability to import a pool with missing or faulted top- level vdevs. Since some data will almost certainly be missing, a pool with missing top-level vdevs can only be imported read-only, and the failmode is set to “continue” (failmode=continue means that when encountering errors the pool will continue running, as opposed to being suspended or panicking). To enable this feature, we’ve added a new global variable: zfs_max_missing_tvds, which defines how many missing top level vdevs we can tolerate before marking a pool as unopenable. It is set to 0 by default, and should be changed to other values only temporarily, while performing an extreme pool recovery. Here as an example we create a pool with two vdevs and write some data to a first dataset; we then add a third vdev and write some data to a second dataset. Finally we physically remove the new vdev (simulating, for instance, a device failure) and try to import the pool using the new feature. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: zfsutils-linux 0.7.5-1ubuntu16.10 ProcVersionSignature: Ubuntu 4.15.0-126.129-generic 4.15.18 Uname: Linux 4.15.0-126-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.20 Architecture: amd64 Date: Wed Dec 2 18:39:58 2020 InstallationDate: Installed on 2020-12-02 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: zfs-linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1906542/+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 1906255] Re: [UBUNTU 20.10] Applications runing in QEMU/KVM get translation faults
** Changed in: linux (Ubuntu Groovy)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Groovy)
Status: New => In Progress
--
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/1906255
Title:
[UBUNTU 20.10] Applications runing in QEMU/KVM get translation faults
Status in Ubuntu on IBM z Systems:
Triaged
Status in linux package in Ubuntu:
New
Status in linux source package in Groovy:
In Progress
Bug description:
SRU Justification:
==
[Impact]
* The commit 0b0ed657fe "s390: remove critical section cleanup from
entry.S" was introduced in kernel 5.8, but instigated a problem where
FPU registers were not properly restored when entering the SIE (start
interpretive execution) instruction.
* This leads to crashes of applications runnning inside KVM, as most
of the programs in use nowdays are using FPU registers for backing of
general register content.
* To fix this interrupts in load_fpu_regs() need to be disabled -
otherwise an interrupt might come in after the registers are loaded,
but before CIF_FPU is cleared in load_fpu_regs().
* When the interrupt returns, CIF_FPU will be cleared and the
registers will never be restored.
[Fix]
* 1179f170b6f0af7bb0b3b7628136eaac450ddf31 1179f170b6f0 "s390: fix fpu
restore in entry.S"
[Test Case]
* IBM Z or LinuxONE hardware with Ubuntu Server 20.10 installed.
* A KVM host needs to be setup as well as an KVM guest (use again
20.10).
* Run (ideally context switching) workload that makes use of FP
instructions inside of the KVM guest.
* Monitor the health of the guest for crashes (logs).
[Regression Potential]
* Even if the code changes are quite overseeable, there is still a
certain risk for regression, because:
* the modifications affect a critical part of the kernel
(arch/s390/kernel/entry.S)
* affect the handling of the FPU registers
* and are always in use if KVM guests run
* So in worst case the changes may have an even bigger impact on FPU
workloads in KVM guests
* and may not only crash in case of FPU usage, but also KVM in
general.
* But the code is peurly s390x specific, hence affects IBM Z only,
* and it got already upstream accepted with v5.10-rc6
* and a test kernel (based on groovy master-next) was build for
further testing.
[Other]
* The patch got upstream accepted with kernel v5.10-rc6, hence it will
land sooner or later in Hirsute.
* It was initially planned to address groovy via 5.8 upstream stable
update, and in fact the patch was already marked for this, but it
didn't made it because 5.8 already reached it's EOL.
* Hence this SRU is submitted for groovy only.
__
commit 0b0ed657fe ("s390: remove critical section cleanup from
entry.S") introduced a problem where FPU registers were not properly
restored when entering SIE. This leads to crashes of applications
runnning inside kvm, as most of the programs in use nowdays are using
FPU registers for backing of general register content.
Fix is upstream:
authorSven Schnelle 2020-11-20 14:17:52
+0100
committer Heiko Carstens 2020-11-23 11:52:13
+0100
commit1179f170b6f0af7bb0b3b7628136eaac450ddf31 (patch)
tree 19e8acb64e0968b41de4899cc1315c41b002839e /arch/s390/kernel/entry.S
parent78d732e1f326f74f240d416af9484928303d9951 (diff)
download linux-1179f170b6f0af7bb0b3b7628136eaac450ddf31.tar.gz
s390: fix fpu restore in entry.S
We need to disable interrupts in load_fpu_regs(). Otherwise an
interrupt might come in after the registers are loaded, but before
CIF_FPU is cleared in load_fpu_regs(). When the interrupt returns,
CIF_FPU will be cleared and the registers will never be restored.
The entry.S code usually saves the interrupt state in __SF_EMPTY on the
stack when disabling/restoring interrupts. sie64a however saves the pointer
to the sie control block in __SF_SIE_CONTROL, which references the same
location. This is non-obvious to the reader. To avoid thrashing the sie
control block pointer in load_fpu_regs(), move the __SIE_* offsets eight
bytes after __SF_EMPTY on the stack.
Cc: # 5.8
Fixes: 0b0ed657fe00 ("s390: remove critical section cleanup from entry.S")
Reported-by: Pierre Morel
Signed-off-by: Sven Schnelle
Acked-by: Christian Borntraeger
Reviewed-by: Heiko Carstens
Signed-off-by: Heiko Carstens
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1906255/+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 1903969] Re: failed to boot to GUI: i915 0000:00:02.0: [drm] *ERROR* Link Training Unsuccessful
oem-5.6 will be eol in two months, most likely too late to get a big
backport in it
** Changed in: linux-oem-5.6 (Ubuntu Focal)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1903969
Title:
failed to boot to GUI: i915 :00:02.0: [drm] *ERROR* Link Training
Unsuccessful
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-5.10 package in Ubuntu:
Invalid
Status in linux-oem-5.6 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-oem-5.10 source package in Focal:
Fix Committed
Status in linux-oem-5.6 source package in Focal:
Won't Fix
Status in linux source package in Groovy:
Won't Fix
Status in linux-oem-5.10 source package in Groovy:
Invalid
Status in linux-oem-5.6 source package in Groovy:
Invalid
Status in linux source package in Hirsute:
In Progress
Status in linux-oem-5.10 source package in Hirsute:
Invalid
Status in linux-oem-5.6 source package in Hirsute:
Invalid
Bug description:
[SRU Justification]
[Impact]
On platforms supported DP tunneling over USB 3.2 or so, a Retimer is
required on the host side to cover insertion loss. On such platforms the
rtimer firmware maybe configured to use LTTPR (Link Training Tunable PHY
Repeater) non-transparent mode only, which is only supported in drm-tip
currently. Without LTTPR support, link training may fail with following
error messages depending on the data path configuration:
i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful
i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun
[Fix]
Patchset https://www.spinics.net/lists/intel-gfx/msg248700.html
("drm/i915: Add support for LTTPR non-transparent link training mode")
is required to fix this issue. It has been landed to drm-tip and will
only be merged to mainline in v5.11.
Patchset https://patchwork.freedesktop.org/series/76993/ ("Plumb crtc
state to link training code") is included for link training functions
prototype changes.
[Test Case]
On Dell OptiPlex and WD19 docking station, use following steps to verify:
1. disconnect WD19 from OptiPlex, disconnect OptiPlex's power
2. attach OptiPlex's power cord
3. attach WD19's power cord
4. attach DP to WD19
5. attach WD19 to OptiPlex
6. boot up and check if boot to GUI directly
7. `dmesg` and check if aforementioned DRM link training error appears
[Where problems could occur]
The second patchset pulled for dependency doesn't have too much
effective changes but refactoring some translation functions, so very
unlikely to have regressions.
For the major part, LTTPR support, when LTTPR is either not detected or
not supported, it will fall back to use transparent mode as it was.
Otherwise, DP Standard recommends to use LTTPR non-transparent mode for
link training, so this should be the right way to have best hardware
support.
== original bug description ==
[Summary]
When the monitor ONLY is connected to the WD19 (DP port) and WD19 is
connected to the type c port than boot the machine, the monitor shows no video
output after loaded i915.
[Reproduce Steps]
1. connect power cable of WD19
2. connect DP cable from monitor to WD19
3. connect power cable to target system.
4. connect type c cable from WD19 to target system
5. boot up
[Results]
Expected: video output as there is only one monitor connected.
Actual: No video output.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.6.0-1033-oem 5.6.0-1033.35
ProcVersionSignature: Ubuntu 5.6.0-1033.35-oem 5.6.19
Uname: Linux 5.6.0-1033-oem x86_64
ApportVersion: 2.20.11-0ubuntu27.11
Architecture: amd64
CasperMD5CheckResult: skip
Date: Thu Nov 12 05:11:11 2020
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-focal-amd64-20200502-85+fossa-metapod+X40
InstallationDate: Installed on 2020-11-03 (9 days ago)
InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary
20200502-05:58
SourcePackage: linux-signed-oem-5.6
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1903969/+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 1895073] Re: Thunderbolt Authenticate on disconnect patches
I think this is a wontfix for oem-5.6 at this point ** Changed in: linux-oem-5.6 (Ubuntu Groovy) Status: New => Invalid ** Changed in: linux-oem-5.6 (Ubuntu) Status: New => Won't Fix ** Changed in: linux-oem-5.6 (Ubuntu Focal) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1895073 Title: Thunderbolt Authenticate on disconnect patches Status in linux package in Ubuntu: In Progress Status in linux-oem-5.6 package in Ubuntu: Won't Fix Status in linux source package in Focal: New Status in linux-oem-5.6 source package in Focal: Won't Fix Status in linux source package in Groovy: In Progress Status in linux-oem-5.6 source package in Groovy: Invalid Bug description: [Impact] These two patches is provided by Mario Limonciello and have landed in 5.9-rc1. Support a better flow for authenticate of TBT dock on disconnect *thunderbolt: Add support for separating the flush to SPI and authenticate *thunderbolt: Add support for authenticate on disconnect Also need the following patches. thunderbolt: Ensure left shift of 512 does not overflow a 32 bit int thunderbolt: Add support for on-board retimers thunderbolt: Implement USB3 bandwidth negotiation routines thunderbolt: Split common NVM functionality into a separate file thunderbolt: Generalize usb4_switch_do_[read|write]_data() thunderbolt: Implement USB4 port sideband operations for retimer access [Fix] [Test] [Regression] Low, the patches have landed in 5.9-rc1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895073/+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 1903682] Re: NULL pointer dereference when configuring multi-function with devfn != 0 before devfn == 0
** Changed in: linux (Ubuntu Groovy)
Importance: Undecided => Medium
--
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/1903682
Title:
NULL pointer dereference when configuring multi-function with devfn !=
0 before devfn == 0
Status in Ubuntu on IBM z Systems:
In Progress
Status in linux package in Ubuntu:
Triaged
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Groovy:
In Progress
Status in linux source package in Hirsute:
Triaged
Bug description:
SRU Justification:
==
[Impact]
* While handling multifunction devices in zPCI the UID of the PCI
function with function number 0 (that always exists according to the
PCI spec) is taken as domain number.
* Therefore if hot plugging functions with a function number larger
than 0 are used before function 0, these need to be held in standby
before creating the domain and bus.
* This has been tested during development of this feature using a
patched QEMU and in DPM, but unfortunately never in
classic/traditional HMC mode.
* On a classic/traditional mode machine with a multi-function device,
and hot plug ("Reassign I/O Path") of the FID of the second port of
the LPAR, any additional hotplug (and even just deconfiguring a PCI
device) will hang - and hotplug now makes the entire Linux instance
unresponsive.
* The reason for this is a NULL pointer dereference - inc case
configuring multi-function with devfn != 0 before devfn == 0.
* This issue was introduced with the topology-aware PCI enumeration
code.
[Fix]
* 0b2ca2c7d0c9e2731d01b6c862375d44a7e13923 0b2ca2c7d0c9 "s390/pci: fix
hot-plug of PCI function missing bus"
[Test Case]
* IBM Z or LinuxONE hardware, equipped with hot-pluggable, multi-
functional PCIe cards (like for example RoCE Express 2 adapters) in
classic/traditional mode.
* An Ubuntu OS running in LPAR, that comes with a kernel that includes
the topology-aware PCI enumeration code (like for example 20.04.1 w/o
further updates or 20.10 GA kernel).
* Now on a system that is in classic/traditional mode, hot plug
("Reassign I/O Path") a multi-function device, but using the FID of
the second port.
[Regression Potential]
* There is at least some regression risk, but I consider it as low,
because:
* Even is the modification is a single if statement (that spans two
lines) in 'zpci_event_availability' it could harm the zPCI event
management even more, in worst case it could break hot plug not only
for systems in classic/traditional mode, but also in DPM mode (and
making the system hang) or for all ports.
* In such a case no enabling / disabling of devices would be possible.
* But the fix is very simple and straight-forward, it checks
zdev->zbus->bus for being NULL and in such a case break the function -
means breaking instead of calling the PCI common code
pci_scan_single_device() with the NULL pointer.
* PCIe devices are usually more optional devices on s390x (compared to
CCW and OSA devices for network) and this affects the zPCI subsystem
only, which is unique to s390x.
[Other]
* The patch got upstream accepted with kernel v5.10-rc3, hence it will
land sooner or later in Hirsute.
* It was initially planned to address groovy via 5.8 upstream stable
update, and in fact the patch was already marked for this, but it
didn't made it because 5.8 reached it's EOL already.
* Hence in addition to the already submitted SRU for focal, this is now a
separate SRU for groovy.
__
Background:
When handling multifunction devices in zPCI we take the
UID of the PCI function with function number 0
(that always exists according to the PCI spec)
as domain number.
Therefore when hot plugging functions with function
number larger than 0 before function 0, we need
to hold these in standby before creating the
domain and bus.
This has been tested during feature development
using a patched QEMU and with DPM but never in Classic
Mode.
Reproduction:
This issue was introduced with the Topology aware PCI
Enumeration code so test with a Linux supporting
that feature. E.g. Upstream, Devel Driver etc.
On a Classic Mode machine with a multi-function device,
hot plug ("Reassign I/O Path") only the FID of the
second port to the LPAR.
Symptom:
After this any additional hotplug and even just
deconfiguring a PCI device will hang. A hotplug
makes the entire Linux instance unresponsive.
Analysis:
The problem occurs in Classic Mode but not with
previous testing as the LPAR hypervisor does
hot plug/Reassign I/O Path as a two step process:
1. zPCI event with PEC 0x0302 to plug the zPCI function in Standby
2. zPCI event with PEC 0x0301 to configure the zPCI function
For the first event we create the zdev in
[Kernel-packages] [Bug 1896904] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1896904/+attachment/5440561/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1896904 Title: Intel 9560 WLAN (8086:9df0) producing computer hanging and wifi breakdown Status in linux package in Ubuntu: Confirmed Bug description: If I do video conferences for example my wifi breaks down. I'm preety sure the it happens since I updated my WiFi router (FritzBox 7590 to Firmware 7.20). I was in contact with the manufacturer. They don't know any problems. I checked dmesg and saw a lot of error messages. So i thought I should report a bug here. Some times WiFi breaks down and comes up again after a few seconds, sometimes it will not come back and I have to restart the computer. Sometimes I can't even turn of WiFi in the Ubuntu menu. Settings telling me something link "network manager not available" (not sure what the exact message is). All firmware updates are installed, I updated to the latest kernel and had the problem again. The logs generated with "ubuntu-bug linux" in this ticket are with symptom "recovers after some seconds" with massive hanging of hole Ubuntu (was not able to move mouse / press strg+alt+t to open terminal). Before I learned how to generate proper logs I saved output of dmesg. I will append some of this to this ticket. There are different error messages. Some without recovering. I will append more proper generated logs (ubuntu-bug linux) to this ticket if I get similar problems and if you would like to see them. It's a ThinkPad T490, it's Ubuntu 20.04.1 LTS, it's a "Intel Corp. Intel 9560 WLAN (8086:9df0)" WiFi card. fnpk@cl003287:~$ uname -a Linux cl003287 5.4.0-48-generic #52-Ubuntu SMP Thu Sep 10 10:58:49 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux fnpk@cl003287:~$ fwupdmgr get-updates • Thunderbolt Controller has the latest available firmware version • Prometheus has the latest available firmware version • Prometheus IOTA Config has the latest available firmware version • SAMSUNG MZVLB512HBJQ-000L7 has no available firmware updates • System Firmware has the latest available firmware version • UEFI Device Firmware has the latest available firmware version • UEFI Device Firmware has the latest available firmware version • UEFI Device Firmware has no available firmware updates • UEFI Device Firmware has no available firmware updates ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-48-generic 5.4.0-48.52 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Sep 24 09:06:55 2020 InstallationDate: Installed on 2020-01-10 (257 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20N2000KGE ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-48-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-48-generic N/A linux-backports-modules-5.4.0-48-generic N/A linux-firmware1.187.3 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-05-12 (134 days ago) dmi.bios.date: 08/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2IET91W (1.69 ) dmi.board.asset.tag: Not Available dmi.board.name: 20N2000KGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2IET91W(1.69):bd08/12/2020:svnLENOVO:pn20N2000KGE:pvrThinkPadT490:rvnLENOVO:rn20N2000KGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T490 dmi.product.name: 20N2000KGE dmi.product.sku: LENOVO_MT_20N2_BU_Think_FM_ThinkPad T490 dmi.product.version: ThinkPad T490 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-10 (282 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20N2000KGE Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-51-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-51.56-generic 5.4.65 RelatedPackageVersions: linux-restricted-modules-5.4.0-51-generic N/A linux-backports-modules-5.4.0-51-generic N/A linux-firmware1.187.3 Tags: focal
[Kernel-packages] [Bug 1896904] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1896904/+attachment/5440563/+files/RfKill.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/1896904 Title: Intel 9560 WLAN (8086:9df0) producing computer hanging and wifi breakdown Status in linux package in Ubuntu: Confirmed Bug description: If I do video conferences for example my wifi breaks down. I'm preety sure the it happens since I updated my WiFi router (FritzBox 7590 to Firmware 7.20). I was in contact with the manufacturer. They don't know any problems. I checked dmesg and saw a lot of error messages. So i thought I should report a bug here. Some times WiFi breaks down and comes up again after a few seconds, sometimes it will not come back and I have to restart the computer. Sometimes I can't even turn of WiFi in the Ubuntu menu. Settings telling me something link "network manager not available" (not sure what the exact message is). All firmware updates are installed, I updated to the latest kernel and had the problem again. The logs generated with "ubuntu-bug linux" in this ticket are with symptom "recovers after some seconds" with massive hanging of hole Ubuntu (was not able to move mouse / press strg+alt+t to open terminal). Before I learned how to generate proper logs I saved output of dmesg. I will append some of this to this ticket. There are different error messages. Some without recovering. I will append more proper generated logs (ubuntu-bug linux) to this ticket if I get similar problems and if you would like to see them. It's a ThinkPad T490, it's Ubuntu 20.04.1 LTS, it's a "Intel Corp. Intel 9560 WLAN (8086:9df0)" WiFi card. fnpk@cl003287:~$ uname -a Linux cl003287 5.4.0-48-generic #52-Ubuntu SMP Thu Sep 10 10:58:49 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux fnpk@cl003287:~$ fwupdmgr get-updates • Thunderbolt Controller has the latest available firmware version • Prometheus has the latest available firmware version • Prometheus IOTA Config has the latest available firmware version • SAMSUNG MZVLB512HBJQ-000L7 has no available firmware updates • System Firmware has the latest available firmware version • UEFI Device Firmware has the latest available firmware version • UEFI Device Firmware has the latest available firmware version • UEFI Device Firmware has no available firmware updates • UEFI Device Firmware has no available firmware updates ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-48-generic 5.4.0-48.52 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Sep 24 09:06:55 2020 InstallationDate: Installed on 2020-01-10 (257 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20N2000KGE ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-48-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-48-generic N/A linux-backports-modules-5.4.0-48-generic N/A linux-firmware1.187.3 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-05-12 (134 days ago) dmi.bios.date: 08/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2IET91W (1.69 ) dmi.board.asset.tag: Not Available dmi.board.name: 20N2000KGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2IET91W(1.69):bd08/12/2020:svnLENOVO:pn20N2000KGE:pvrThinkPadT490:rvnLENOVO:rn20N2000KGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T490 dmi.product.name: 20N2000KGE dmi.product.sku: LENOVO_MT_20N2_BU_Think_FM_ThinkPad T490 dmi.product.version: ThinkPad T490 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-10 (282 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20N2000KGE Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-51-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-51.56-generic 5.4.65 RelatedPackageVersions: linux-restricted-modules-5.4.0-51-generic N/A linux-backports-modules-5.4.0-51-generic N/A linux-firmware1.187.3 Tags: focal Uname: Linux
[Kernel-packages] [Bug 1896904] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1896904/+attachment/5440566/+files/acpidump.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/1896904 Title: Intel 9560 WLAN (8086:9df0) producing computer hanging and wifi breakdown Status in linux package in Ubuntu: Confirmed Bug description: If I do video conferences for example my wifi breaks down. I'm preety sure the it happens since I updated my WiFi router (FritzBox 7590 to Firmware 7.20). I was in contact with the manufacturer. They don't know any problems. I checked dmesg and saw a lot of error messages. So i thought I should report a bug here. Some times WiFi breaks down and comes up again after a few seconds, sometimes it will not come back and I have to restart the computer. Sometimes I can't even turn of WiFi in the Ubuntu menu. Settings telling me something link "network manager not available" (not sure what the exact message is). All firmware updates are installed, I updated to the latest kernel and had the problem again. The logs generated with "ubuntu-bug linux" in this ticket are with symptom "recovers after some seconds" with massive hanging of hole Ubuntu (was not able to move mouse / press strg+alt+t to open terminal). Before I learned how to generate proper logs I saved output of dmesg. I will append some of this to this ticket. There are different error messages. Some without recovering. I will append more proper generated logs (ubuntu-bug linux) to this ticket if I get similar problems and if you would like to see them. It's a ThinkPad T490, it's Ubuntu 20.04.1 LTS, it's a "Intel Corp. Intel 9560 WLAN (8086:9df0)" WiFi card. fnpk@cl003287:~$ uname -a Linux cl003287 5.4.0-48-generic #52-Ubuntu SMP Thu Sep 10 10:58:49 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux fnpk@cl003287:~$ fwupdmgr get-updates • Thunderbolt Controller has the latest available firmware version • Prometheus has the latest available firmware version • Prometheus IOTA Config has the latest available firmware version • SAMSUNG MZVLB512HBJQ-000L7 has no available firmware updates • System Firmware has the latest available firmware version • UEFI Device Firmware has the latest available firmware version • UEFI Device Firmware has the latest available firmware version • UEFI Device Firmware has no available firmware updates • UEFI Device Firmware has no available firmware updates ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-48-generic 5.4.0-48.52 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Sep 24 09:06:55 2020 InstallationDate: Installed on 2020-01-10 (257 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20N2000KGE ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-48-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-48-generic N/A linux-backports-modules-5.4.0-48-generic N/A linux-firmware1.187.3 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-05-12 (134 days ago) dmi.bios.date: 08/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2IET91W (1.69 ) dmi.board.asset.tag: Not Available dmi.board.name: 20N2000KGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2IET91W(1.69):bd08/12/2020:svnLENOVO:pn20N2000KGE:pvrThinkPadT490:rvnLENOVO:rn20N2000KGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T490 dmi.product.name: 20N2000KGE dmi.product.sku: LENOVO_MT_20N2_BU_Think_FM_ThinkPad T490 dmi.product.version: ThinkPad T490 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-10 (282 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20N2000KGE Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-51-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-51.56-generic 5.4.65 RelatedPackageVersions: linux-restricted-modules-5.4.0-51-generic N/A linux-backports-modules-5.4.0-51-generic N/A linux-firmware1.187.3 Tags: focal Uname:
