[Kernel-packages] [Bug 1867559] Re: Qualcomm Atheros QCA9377 wifi 802.11ac very unstable and low speed
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-firmware (Ubuntu) Status: New => Confirmed -- 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/1867559 Title: Qualcomm Atheros QCA9377 wifi 802.11ac very unstable and low speed Status in linux package in Ubuntu: Incomplete Status in linux-firmware package in Ubuntu: Confirmed Bug description: rafa@acer:~$ sudo lshw -C network [sudo] senha para rafa: *-network descrição: Ethernet interface produto: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller fabricante: Realtek Semiconductor Co., Ltd. ID físico: 0.1 informações do barramento: pci@:01:00.1 nome lógico: enp1s0f1 versão: 12 serial: 08:97:98:63:7d:2e capacidade: 1Gbit/s largura: 64 bits clock: 33MHz capacidades: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuração: autonegotiation=on broadcast=yes driver=r8169 firmware=rtl8411-2_0.0.1 07/08/13 latency=0 link=no multicast=yes port=MII recursos: irq:16 porta de E/S:3000(tamanho=256) memória:b1204000-b1204fff memória:b120-b1203fff *-network descrição: Interface sem fio produto: QCA9377 802.11ac Wireless Network Adapter fabricante: Qualcomm Atheros ID físico: 0 informações do barramento: pci@:02:00.0 nome lógico: wlp2s0 versão: 31 serial: a4:63:a1:0e:bc:42 largura: 64 bits clock: 33MHz capacidades: pm msi pciexpress bus_master cap_list ethernet physical wireless configuração: broadcast=yes driver=ath10k_pci driverversion=5.3.0-40-generic firmware=WLAN.TF.2.1-00021-QCARMSWP-1 ip=192.168.1.3 latency=0 link=yes multicast=yes wireless=IEEE 802.11 recursos: irq:132 memória:b100-b11f Download speed around 100-600Kb/s on 5GHz connection using WPA/WPA2. Notebook ACER ASPIRE 3 A315-53-343Y To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1867559/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888116] Re: kernel 5.4.0-42-generic looping amdgpu errors
apport-collect tells me that this bug is not open anymore (or not started by me) so i attach all relevant information, configurations and log files as tar.gz archive Pls advice if any other information is reqired ** Attachment added: "all relevant log files" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888116/+attachment/5394454/+files/amdgpu-error-logs.tar.gz ** 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/1888116 Title: kernel 5.4.0-42-generic looping amdgpu errors Status in linux package in Ubuntu: Confirmed Bug description: After updating to package "linux-image-5.4.0-42-generic" (5.4.0.42.45) several hundred system-log similar entires per minute are thrown at log: kernelamdgpu :09:00.0: amdgpu: [mmhub] page fault (src_id:0 ring:169 vmid:0 pasid:0, for process pid 0 thread pid 0) kernelamdgpu :09:00.0: amdgpu: in page starting at address 0xfffba000 from client 18 kernelamdgpu :09:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00041F52 kernelamdgpu :09:00.0: amdgpu: Faulty UTCL2 client ID: 0xf kernelamdgpu :09:00.0: amdgpu: MORE_FAULTS: 0x0 kernelamdgpu :09:00.0: amdgpu: WALKER_ERROR: 0x1 kernelamdgpu :09:00.0: amdgpu: PERMISSION_FAULTS: 0x5 kernelamdgpu :09:00.0: amdgpu: MAPPING_ERROR: 0x1 kernelamdgpu :09:00.0: amdgpu: RW: 0x1 System is a 20.04.1 Kubtuntu, with AMD Ryzen 5 and RX 5700 GPU, amdgpu with opencl installed (via amdgpu- pro-20.20-1089974-ubuntu-20.04.tar.xz from amd.com) Nevertheless no system freezes or graphic bugs happened To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888116/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884159] Re: Update lockdown patches
This bug was fixed in the package linux - 4.15.0-112.113 --- linux (4.15.0-112.113) bionic; urgency=medium * bionic/linux: 4.15.0-112.113 -proposed tracker (LP: #1887048) * Packaging resync (LP: #1786013) - update dkms package versions * CVE-2020-11935 - SAUCE: aufs: do not call i_readcount_inc() - SAUCE: aufs: bugfix, IMA i_readcount * CVE-2020-10757 - mm: Fix mremap not considering huge pmd devmap * Update lockdown patches (LP: #1884159) - efi/efi_test: Lock down /dev/efi_test and require CAP_SYS_ADMIN - efi: Restrict efivar_ssdt_load when the kernel is locked down - powerpc/xmon: add read-only mode - powerpc/xmon: Restrict when kernel is locked down - [Config] CONFIG_XMON_DEFAULT_RO_MODE=y - SAUCE: acpi: disallow loading configfs acpi tables when locked down * seccomp_bpf fails on powerpc (LP: #1885757) - SAUCE: selftests/seccomp: fix ptrace tests on powerpc * Introduce the new NVIDIA 418-server and 440-server series, and update the current NVIDIA drivers (LP: #1881137) - [packaging] add signed modules for the 418-server and the 440-server flavours -- Khalid Elmously Thu, 09 Jul 2020 19:13:37 -0400 ** Changed in: linux (Ubuntu Bionic) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-10757 -- 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/1884159 Title: Update lockdown patches Status in linux package in Ubuntu: Fix Committed Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-oem-osp1 source package in Bionic: Fix Committed Status in linux source package in Eoan: Fix Committed Status in linux source package in Focal: Fix Released Bug description: Impact: The lockdown patches have evolved over time, and part of this was restricting more areas of the kernel. Not all of these additions were backported, and some can lead to lockdown bypasses, see [1] and [2]. Fix: Backport newer lockdown restrictions to older releases. Test Case: Test cases for most of the backports can be found at [3], and [4] is another test case. Some which need e.g. specific hardware to test have not been tested. Regression Potential: Most of these are small, simple fixes with low potential for regression. Users may also lose access to some functionality previously accissible under secure boot. Some changes are more substantial, especially the hw_param and debugfs changes for xenial, but they are based on well-tested upstream code. The xmon backports also carry a more moderate risk of regression. [1] https://lists.ubuntu.com/archives/kernel-team/2020-June/111050.html [2] https://lore.kernel.org/lkml/20200615104332.901519-1-ja...@zx2c4.com/ [3] https://git.launchpad.net/~sforshee/+git/lockdown-tests [4] https://git.zx2c4.com/american-unsigned-language/tree/american-unsigned-language.sh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884159/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878421] Re: Using two GPUs with one monitor each, one is always black
is maybe this also handled by gnome-flashback directly? -- 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/1878421 Title: Using two GPUs with one monitor each, one is always black Status in Mutter: New Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: Hi, i try to use external monitor on my dell G5 2019 (5590). works on ubuntu 18.4 (after reboot) using prime-select nvidia. did this on 20.4 (prime-select + reboot because logoff/login again still don't work) and it hang on boot while showing ubuntu bootscreen with animation (not stopped, but also response to esc-key to show terminal-output) on the monitor (need to switch off). booted again where monitor is configured to other input, boot works, i see it in preferences dialog as second monitor, but if i configure input on monitor i have no signal.. anything i can try? regards Frank ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME-Flashback:GNOME Date: Wed May 13 15:21:08 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:08ea] NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f91] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell TU117M [GeForce GTX 1650 Mobile / Max-Q] [1028:08ea] InstallationDate: Installed on 2020-04-27 (16 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 27c6:530c Shenzhen Goodix Technology Co.,Ltd. Fingerprint Reader Bus 001 Device 002: ID 0c45:671f Microdia Integrated_Webcam_HD Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. G5 5590 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=7c9113b7-ca65-4c46-9435-f5d2b73bab72 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/07/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0KW84T dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd02/07/2020:svnDellInc.:pnG55590:pvr:rvnDellInc.:rn0KW84T:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: GSeries dmi.product.name: G5 5590 dmi.product.sku: 08EA dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1878421/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882823] Re: int3403 thermal INT3403:00
It shouldn't be long that Ubuntu 20.04 kernel gets it from upstream. -- 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/1882823 Title: int3403 thermal INT3403:00 Status in linux package in Ubuntu: Confirmed Bug description: [8.112761] int3403 thermal INT3403:00: Unsupported event [0x91] [ 10.121722] int3403 thermal INT3403:00: Unsupported event [0x91] [ 12.165233] int3403 thermal INT3403:00: Unsupported event [0x91] Is constantly flooding my dmesg. I believe this is also due to missing audio drivers as well. Which is another issue that I am facing. Realtek ALC1220 Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882823/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882823] Re: int3403 thermal INT3403:00
The patch was meraged to 5.4 stable 5 hours ago - = This is a note to let you know that I've just added the patch titled thermal: int3403_thermal: Downgrade error message to the 5.4-stable tree which can be found at: http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary The filename of the patch is: thermal-int3403_thermal-downgrade-error-message.patch and it can be found in the queue-5.4 subdirectory. If you, or anyone else, feels it should not be added to the stable tree, please let know about it. = details @ https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable- queue.git/commit/?id=0d0f826a596961721326485e02a37c9b49aafb7a -- 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/1882823 Title: int3403 thermal INT3403:00 Status in linux package in Ubuntu: Confirmed Bug description: [8.112761] int3403 thermal INT3403:00: Unsupported event [0x91] [ 10.121722] int3403 thermal INT3403:00: Unsupported event [0x91] [ 12.165233] int3403 thermal INT3403:00: Unsupported event [0x91] Is constantly flooding my dmesg. I believe this is also due to missing audio drivers as well. Which is another issue that I am facing. Realtek ALC1220 Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882823/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888000] Re: Bionic/Xenial minimal cloud image: failed to apply load kernel module
Thanks for the review, it turns out that this failure has always been present. Going back to the Bionic 20180705 and Xenial 20180705, which were the first releases of minimal, also showed that the system "Failed to find module 'ib_iser'". Is this something that could be fixed in order to prevent us from shipping with failed systemd units? ** Description changed: Overview --- - This is *blocking* new minimal image promotion. Starting on or around 20200714, the Bionic and Xenial minimal cloud images reported they failed to load kernel modules. - + It appears the Bionic and Xenial minimal images have always shipped with a failing systemd unit: "systemd-modules-load.service" with the error "Failed to find module 'ib_iser'" Expected results --- $ sudo systemctl list-units --failed --no-legend # Return no failed units - Actual results --- $ sudo systemctl list-units --failed --no-legend systemd-sysctl.service loaded failed failed Apply Kernel Variables # cloud-config.service may show up failing to setup the timezone... From the journal: Jul 17 17:48:27 ubuntu systemd-modules-load[98]: Module 'iscsi_tcp' is builtin Jul 17 17:48:27 ubuntu systemd-modules-load[98]: Failed to find module 'ib_iser' Jul 17 17:48:27 ubuntu systemd-sysctl[106]: Couldn't write '176' to 'kernel/sysrq', ignoring: No such file or directory Jul 17 17:48:27 ubuntu systemd-sysctl[106]: Couldn't write 'fq_codel' to 'net/core/default_qdisc', ignoring: No such file or directory - Steps to reproduce --- - 1. Download image from: https://private-fileshare.canonical.com/~powersj/minimal-bionic/ - 2. multipass launch file:/// - 3. multipass exec -- sudo systemctl list-units --failed --no-legend - --- + $ wget https://cloud-images.ubuntu.com/daily/server/minimal/releases/bionic/release/ubuntu-18.04-minimal-cloudimg-amd64.img + $ multipass launch file:///$(pwd)/ubuntu-18.04-minimal-cloudimg-amd64.img --name=bionic-minimal + $ multipass exec bionic-minimal -- sudo systemctl list-units --failed --no-legend + + + --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser': 'fuser' CRDA: N/A DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lspci: Error: [Errno 2] No such file or directory: 'lspci': 'lspci' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb': 'lsusb' MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) PciMultimedia: - + ProcEnviron: - TERM=xterm - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=C.UTF-8 - SHELL=/bin/bash + TERM=xterm + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=C.UTF-8 + SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1069-kvm root=PARTUUID=ffb7214d-c783-45ed-b736-278d4ee0cac0 ro console=tty1 console=ttyS0 ProcVersionSignature: User Name 4.15.0-1069.70-kvm 4.15.18 RelatedPackageVersions: - linux-restricted-modules-4.15.0-1069-kvm N/A - linux-backports-modules-4.15.0-1069-kvm N/A - linux-firmware N/A + linux-restricted-modules-4.15.0-1069-kvm N/A + linux-backports-modules-4.15.0-1069-kvm N/A + linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.15.0-1069-kvm x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-bionic dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-bionic:cvnQEMU:ct1:cvrpc-i440fx-bionic: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-bionic dmi.sys.vendor: QEMU -- 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/1888000 Title: Bionic/Xenial minimal cloud image: failed to apply load kernel module Status in linux package in Ubuntu: Confirmed Bug description: Overview --- It appears the Bionic and Xenial minimal images have always shipped with a failing systemd unit: "systemd-modules-load.service" with the error "Failed to find module 'ib_iser'" Expected results --- $ sudo
[Kernel-packages] [Bug 1882955] Re: LXD 4.2 broken on linux-kvm due to missing VLAN filtering
This bug was fixed in the package linux-kvm - 4.4.0-1077.84 --- linux-kvm (4.4.0-1077.84) xenial; urgency=medium * xenial/linux-kvm: 4.4.0-1077.84 -proposed tracker (LP: #1885506) * LXD 4.2 broken on linux-kvm due to missing VLAN filtering (LP: #1882955) - [Config] VLAN_8021Q=m && BRIDGE_VLAN_FILTERING=y [ Ubuntu: 4.4.0-186.216 ] * xenial/linux: 4.4.0-186.216 -proposed tracker (LP: #1885514) * Xenial update: v4.4.228 upstream stable release (LP: #1884564) - ipv6: fix IPV6_ADDRFORM operation logic - vxlan: Avoid infinite loop when suppressing NS messages with invalid options - scsi: return correct blkprep status code in case scsi_init_io() fails. - net: phy: marvell: Limit 88m1101 autoneg errata to 88E1145 as well. - pwm: fsl-ftm: Use flat regmap cache - ARM: 8977/1: ptrace: Fix mask for thumb breakpoint hook - sched/fair: Don't NUMA balance for kthreads - ath9k_htc: Silence undersized packet warnings - x86_64: Fix jiffies ODR violation - x86/speculation: Prevent rogue cross-process SSBD shutdown - x86/reboot/quirks: Add MacBook6,1 reboot quirk - efi/efivars: Add missing kobject_put() in sysfs entry creation error path - ALSA: es1688: Add the missed snd_card_free() - ALSA: usb-audio: Fix inconsistent card PM state after resume - ACPI: sysfs: Fix reference count leak in acpi_sysfs_add_hotplug_profile() - ACPI: PM: Avoid using power resources if there are none for D0 - cgroup, blkcg: Prepare some symbols for module and !CONFIG_CGROUP usages - nilfs2: fix null pointer dereference at nilfs_segctor_do_construct() - spi: bcm2835aux: Fix controller unregister order - ALSA: pcm: disallow linking stream to itself - x86/speculation: Change misspelled STIPB to STIBP - x86/speculation: Add support for STIBP always-on preferred mode - x86/speculation: Avoid force-disabling IBPB based on STIBP and enhanced IBRS. - x86/speculation: PR_SPEC_FORCE_DISABLE enforcement for indirect branches. - spi: dw: fix possible race condition - spi: dw: Fix controller unregister order - spi: No need to assign dummy value in spi_unregister_controller() - spi: Fix controller unregister order - spi: pxa2xx: Fix controller unregister order - spi: bcm2835: Fix controller unregister order - ovl: initialize error in ovl_copy_xattr - proc: Use new_inode not new_inode_pseudo - video: fbdev: w100fb: Fix a potential double free. - KVM: nSVM: leave ASID aside in copy_vmcb_control_area - KVM: nVMX: Consult only the "basic" exit reason when routing nested exit - KVM: arm64: Make vcpu_cp1x() work on Big Endian hosts - ath9k: Fix use-after-free Read in ath9k_wmi_ctrl_rx - ath9k: Fix use-after-free Write in ath9k_htc_rx_msg - ath9x: Fix stack-out-of-bounds Write in ath9k_hif_usb_rx_cb - ath9k: Fix general protection fault in ath9k_hif_usb_rx_cb - Smack: slab-out-of-bounds in vsscanf - mm/slub: fix a memory leak in sysfs_slab_add() - fat: don't allow to mount if the FAT length == 0 - can: kvaser_usb: kvaser_usb_leaf: Fix some info-leaks to USB devices - spi: dw: Zero DMA Tx and Rx configurations on stack - Bluetooth: Add SCO fallback for invalid LMP parameters error - kgdb: Prevent infinite recursive entries to the debugger - spi: dw: Enable interrupts in accordance with DMA xfer mode - clocksource: dw_apb_timer_of: Fix missing clockevent timers - btrfs: do not ignore error from btrfs_next_leaf() when inserting checksums - ARM: 8978/1: mm: make act_mm() respect THREAD_SIZE - net: vmxnet3: fix possible buffer overflow caused by bad DMA value in vmxnet3_get_rss() - staging: android: ion: use vmap instead of vm_map_ram - e1000: Distribute switch variables for initialization - media: dvb: return -EREMOTEIO on i2c transfer failure. - MIPS: Make sparse_init() using top-down allocation - netfilter: nft_nat: return EOPNOTSUPP if type or flags are not supported - lib/mpi: Fix 64-bit MIPS build with Clang - net: lpc-enet: fix error return code in lpc_mii_init() - net: allwinner: Fix use correct return type for ndo_start_xmit() - powerpc/spufs: fix copy_to_user while atomic - mips: cm: Fix an invalid error code of INTVN_*_ERR - kgdb: Fix spurious true from in_dbg_master() - md: don't flush workqueue unconditionally in md_open - mwifiex: Fix memory corruption in dump_station - mips: Add udelay lpj numbers adjustment - x86/mm: Stop printing BRK addresses - m68k: mac: Don't call via_flush_cache() on Mac IIfx - macvlan: Skip loopback packets in RX handler - PCI: Don't disable decoding when mmio_always_on is set - MIPS: Fix IRQ tracing when call handle_fpe() and handle_msa_fpe() - ixgbe: fix signed-integer-overflow warning - spi: dw: Return any value retrieved from the dma_transfer callback - cpuidle: Fix three reference count leaks
[Kernel-packages] [Bug 1882478] Re: smpboot: don't call topology_sane() when Sub-NUMA-Clustering is enabled
This bug was fixed in the package linux - 4.4.0-186.216 --- linux (4.4.0-186.216) xenial; urgency=medium * xenial/linux: 4.4.0-186.216 -proposed tracker (LP: #1885514) * Xenial update: v4.4.228 upstream stable release (LP: #1884564) - ipv6: fix IPV6_ADDRFORM operation logic - vxlan: Avoid infinite loop when suppressing NS messages with invalid options - scsi: return correct blkprep status code in case scsi_init_io() fails. - net: phy: marvell: Limit 88m1101 autoneg errata to 88E1145 as well. - pwm: fsl-ftm: Use flat regmap cache - ARM: 8977/1: ptrace: Fix mask for thumb breakpoint hook - sched/fair: Don't NUMA balance for kthreads - ath9k_htc: Silence undersized packet warnings - x86_64: Fix jiffies ODR violation - x86/speculation: Prevent rogue cross-process SSBD shutdown - x86/reboot/quirks: Add MacBook6,1 reboot quirk - efi/efivars: Add missing kobject_put() in sysfs entry creation error path - ALSA: es1688: Add the missed snd_card_free() - ALSA: usb-audio: Fix inconsistent card PM state after resume - ACPI: sysfs: Fix reference count leak in acpi_sysfs_add_hotplug_profile() - ACPI: PM: Avoid using power resources if there are none for D0 - cgroup, blkcg: Prepare some symbols for module and !CONFIG_CGROUP usages - nilfs2: fix null pointer dereference at nilfs_segctor_do_construct() - spi: bcm2835aux: Fix controller unregister order - ALSA: pcm: disallow linking stream to itself - x86/speculation: Change misspelled STIPB to STIBP - x86/speculation: Add support for STIBP always-on preferred mode - x86/speculation: Avoid force-disabling IBPB based on STIBP and enhanced IBRS. - x86/speculation: PR_SPEC_FORCE_DISABLE enforcement for indirect branches. - spi: dw: fix possible race condition - spi: dw: Fix controller unregister order - spi: No need to assign dummy value in spi_unregister_controller() - spi: Fix controller unregister order - spi: pxa2xx: Fix controller unregister order - spi: bcm2835: Fix controller unregister order - ovl: initialize error in ovl_copy_xattr - proc: Use new_inode not new_inode_pseudo - video: fbdev: w100fb: Fix a potential double free. - KVM: nSVM: leave ASID aside in copy_vmcb_control_area - KVM: nVMX: Consult only the "basic" exit reason when routing nested exit - KVM: arm64: Make vcpu_cp1x() work on Big Endian hosts - ath9k: Fix use-after-free Read in ath9k_wmi_ctrl_rx - ath9k: Fix use-after-free Write in ath9k_htc_rx_msg - ath9x: Fix stack-out-of-bounds Write in ath9k_hif_usb_rx_cb - ath9k: Fix general protection fault in ath9k_hif_usb_rx_cb - Smack: slab-out-of-bounds in vsscanf - mm/slub: fix a memory leak in sysfs_slab_add() - fat: don't allow to mount if the FAT length == 0 - can: kvaser_usb: kvaser_usb_leaf: Fix some info-leaks to USB devices - spi: dw: Zero DMA Tx and Rx configurations on stack - Bluetooth: Add SCO fallback for invalid LMP parameters error - kgdb: Prevent infinite recursive entries to the debugger - spi: dw: Enable interrupts in accordance with DMA xfer mode - clocksource: dw_apb_timer_of: Fix missing clockevent timers - btrfs: do not ignore error from btrfs_next_leaf() when inserting checksums - ARM: 8978/1: mm: make act_mm() respect THREAD_SIZE - net: vmxnet3: fix possible buffer overflow caused by bad DMA value in vmxnet3_get_rss() - staging: android: ion: use vmap instead of vm_map_ram - e1000: Distribute switch variables for initialization - media: dvb: return -EREMOTEIO on i2c transfer failure. - MIPS: Make sparse_init() using top-down allocation - netfilter: nft_nat: return EOPNOTSUPP if type or flags are not supported - lib/mpi: Fix 64-bit MIPS build with Clang - net: lpc-enet: fix error return code in lpc_mii_init() - net: allwinner: Fix use correct return type for ndo_start_xmit() - powerpc/spufs: fix copy_to_user while atomic - mips: cm: Fix an invalid error code of INTVN_*_ERR - kgdb: Fix spurious true from in_dbg_master() - md: don't flush workqueue unconditionally in md_open - mwifiex: Fix memory corruption in dump_station - mips: Add udelay lpj numbers adjustment - x86/mm: Stop printing BRK addresses - m68k: mac: Don't call via_flush_cache() on Mac IIfx - macvlan: Skip loopback packets in RX handler - PCI: Don't disable decoding when mmio_always_on is set - MIPS: Fix IRQ tracing when call handle_fpe() and handle_msa_fpe() - ixgbe: fix signed-integer-overflow warning - spi: dw: Return any value retrieved from the dma_transfer callback - cpuidle: Fix three reference count leaks - ima: Fix ima digest hash table key calculation - ext4: fix EXT_MAX_EXTENT/INDEX to check for zeroed eh_max - Btrfs: fix unreplayable log after snapshot delete + parent dir fsync - btrfs: send: emit file capabilities after
[Kernel-packages] [Bug 1887218] Re: Ryzen 5 3500U - laptop won't boot when on battery power
Since the workaround involves amd's iommu and kernel 5.5, we may be able to find a patch that fixes this by cherry-pikcy: git log --pretty=short v5.4..v5.5 -- drivers/iommu/amd_iommu.c commit 1daa56bcfd8b329447e0c1b1e91c3925d08489b7 Merge: a5255bc31673 9b3a713feef8 Author: Linus Torvalds Merge tag 'iommu-updates-v5.5' of git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu commit 995e2ef08280dab8de6c517acd836613678fe2a3 Merge: 1fca7e0e6fe6 ae5e6c6439c3 cb0701acfa7e b5b42b24d783 2e127203d116 Author: Rafael J. Wysocki Merge branches 'acpi-utils', 'acpi-platform', 'acpi-video' and 'acpi-doc' commit 9b3a713feef8db41d4bcccb3b97e86ee906690c8 Merge: 4e7120d79edb da6b05dce2a9 1289f7f15001 5b47748ecf2e c90ae4a63541 96d3ab802e49 34d1b0895dbd 3c124435e8dd 6c3a44ed3c55 c1c8058dfb98 808be0aae53a Author: Joerg Roedel Merge branches 'iommu/fixes', 'arm/qcom', 'arm/renesas', 'arm/rockchip', 'arm/mediatek', 'arm/tegra', 'arm/smmu', 'x86/amd', 'x86/vt-d', 'virtio' and 'core' into next commit 3c124435e8dd516df4b2fc983f4415386fd6edae Author: Logan Gunthorpe iommu/amd: Support multiple PCI DMA aliases in IRQ Remapping commit 3332364e4ebc0581d133a334645a20fd13b580f1 Author: Logan Gunthorpe iommu/amd: Support multiple PCI DMA aliases in device table commit a5bbbf37c6f8522a1afd46c37b5a0d1ce63232b7 Author: Denys Vlasenko iommu/amd: Do not re-fetch iommu->cmd_buf_tail commit 3057fb9377eb5e73386dd0d8804bf72bdd23e391 Author: Joerg Roedel iommu/amd: Pass gfp flags to iommu_map_page() in amd_iommu_map() commit 470eb3b31134ada545dcb41e94a0c97b42c95803 Author: Suthikulpanit, Suravee iommu/amd: Simpify decoding logic for INVALID_PPR_REQUEST event commit ae5e6c6439c3d0ac8e9c71523790ba1ff6887894 Author: Andy Shevchenko iommu/amd: Switch to use acpi_dev_hid_uid_match() commit be62dbf554c5b50718a54a359372c148cd9975c7 Author: Tom Murphy iommu/amd: Convert AMD iommu driver to the dma-iommu api commit 781ca2de89bae1b1d2c96df9ef33e9a324415995 Author: Tom Murphy iommu: Add gfp parameter to iommu_ops::map commit 37ec8eb851c1876580a963f283fe7496592b9f72 Author: Tom Murphy iommu/amd: Remove unnecessary locking from AMD iommu driver -- 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/1887218 Title: Ryzen 5 3500U - laptop won't boot when on battery power Status in linux package in Ubuntu: Incomplete Bug description: Ryzen 5 3500U (release in 2019) won't boot when laptop is on battery power. It affects different brands of laptops. Laptop boots normally with charger in and you can unplug the charger and then use battery. For some a work around is possible on kernel 5.4. For others kernel should be 5.5 or better yet 5.6. issue described in more detail in Ubuntu forums: https://ubuntuforums.org/showthread.php?t=2446942 dmesg: https://paste.ubuntu.com/p/C2xNzpBKq5/ iommu=soft boot options provides the work arround on some laptops, while on others USB ports stop working. OS: Kubuntu 20.04 LTS CPU: Ryzen 5 3500U GPU: AMD Vega 8 RAM: 8 GB DDR4 2400 Mhz disk: 256 GB nvme I patched kernel (now tainted) to get driver for rtl8821ce (wi-fi). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887218/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887218] Re: Ryzen 5 3500U - laptop won't boot when on battery power
A test kernel, based on UBUNTU: Ubuntu-5.4.0-42.46, is available @ https://people.canonical.com/~alexhung/LP1887218/ver1/ If this solves this bug, we can keep bisecting. If not, we can try other patches. The following commits are excluded: == merges == 1daa56bcfd8b329447e0c1b1e91c3925d08489b7 995e2ef08280dab8de6c517acd836613678fe2a3 9b3a713feef8db41d4bcccb3b97e86ee906690c8 == cannot clean picked == 3c124435e8dd516df4b2fc983f4415386fd6edae 3332364e4ebc0581d133a334645a20fd13b580f1 We can come back to these if the test kernel fails. == fail to compile == ae5e6c6439c3d0ac8e9c71523790ba1ff6887894 This requires additional patch(es) but this is to replace an existing function with acpi_dev_hid_uid_match and should not have any effects -- 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/1887218 Title: Ryzen 5 3500U - laptop won't boot when on battery power Status in linux package in Ubuntu: Incomplete Bug description: Ryzen 5 3500U (release in 2019) won't boot when laptop is on battery power. It affects different brands of laptops. Laptop boots normally with charger in and you can unplug the charger and then use battery. For some a work around is possible on kernel 5.4. For others kernel should be 5.5 or better yet 5.6. issue described in more detail in Ubuntu forums: https://ubuntuforums.org/showthread.php?t=2446942 dmesg: https://paste.ubuntu.com/p/C2xNzpBKq5/ iommu=soft boot options provides the work arround on some laptops, while on others USB ports stop working. OS: Kubuntu 20.04 LTS CPU: Ryzen 5 3500U GPU: AMD Vega 8 RAM: 8 GB DDR4 2400 Mhz disk: 256 GB nvme I patched kernel (now tainted) to get driver for rtl8821ce (wi-fi). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887218/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1873961] Comment bridged from LTC Bugzilla
--- Comment From z...@us.ibm.com 2020-07-20 17:09 EDT--- I download iproute2-4.19.0.tar.gz from this upstream url: https://git.kernel.org/pub/scm/network/iproute2/iproute2.git Build and tested on my existing ppc64 Genesis OS (4.15.0-1039-ibm-gt), I do see it now reports correct tcp_flags mask. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/1873961 Title: tc filter show tcp_flags wrong mask value Status in The Ubuntu-power-systems project: Triaged Status in iproute2 package in Ubuntu: Fix Released Status in iproute2 source package in Bionic: Triaged Bug description: ---Problem Description--- Problem Descriptions "tc" utility does not show correct TC rule's tcp_flags mask correctly in current "iproute2" package shipped on Genesis. # dpkg -l |grep iproute2 ii iproute2 4.15.0-2ubuntu1 ppc64el networking and traffic control tools ---Steps to Reproduce--- Steps to reproduce the problem: 1) Add a tc rule to the testing VF (i.e. p0v2_r): # tc filter add dev p0v2 protocol ip parent : pref 5 chain 1 handle 0x1 flower src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff ip_proto tcp tcp_flags 2 skip_sw action mirred egress redirect dev p0v0_r 2) Validate the added TC rule: # tc filter show dev p0v2_r root filter protocol ip pref 5 flower chain 1 filter protocol ip pref 5 flower chain 1 handle 0x1 src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff eth_type ipv4 ip_proto tcp tcp_flags 22 /* <--- Wrong */ skip_sw in_hw action order 1: mirred (Egress Redirect to device p0v0_r) stolen 3) If we add the tcp_flags using explicit mask 0x7: # tc filter add dev p0v2 protocol ip parent : pref 5 chain 1 handle 0x1 flower src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff ip_proto tcp tcp_flags 0x2/7 skip_sw action mirred egress redirect dev p0v0_r After that, using "tc filter show dev p0v2_r root" to verify, we still see the same output (tcp_flags 22) as shown in 2) above, which is wrong. Userspace tool common name: tc The userspace tool has the following bit modes: 64-bit Userspace package: iproute2 == Fixes: There are 2 patches to fix the issue: patch 1: commit b85076cd74e77538918d35992b1a9cd17ff86af8 Author: Stephen Hemminger Date: Tue Sep 11 08:29:33 2018 -0700 lib: introduce print_nl Common pattern in iproute commands is to print a line seperator in non-json mode. Make that a simple function. /* This patch declares global variable "const char *_SL_ = "\n";" in lib/utils.c to be used by 2nd patch */ patch 2: commit e8bd395508cead5a81c2bebd9d3705a9e41ea8bc Author: Keara Leibovitz Date: Thu Jul 26 09:45:30 2018 -0400 tc: fix bugs for tcp_flags and ip_attr hex output Fix hex output for both the ip_attr and tcp_flags print functions. With the above 2 patches pull in, the new "tc" utility will show the correct tcp_flags mask: # tc filter show dev p0v2 root filter protocol ip pref 5 flower chain 1 filter protocol ip pref 5 flower chain 1 handle 0x1 src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff eth_type ipv4 ip_proto tcp tcp_flags 0x2/7 /* <--- Correct */ skip_sw in_hw action order 1: mirred (Egress Redirect to device p0v0_r) stolen This bug affects tc in Ubuntu 18.04.1 stock image. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1873961/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1885757] Re: seccomp_bpf fails on powerpc
This bug was fixed in the package linux - 4.15.0-112.113 --- linux (4.15.0-112.113) bionic; urgency=medium * bionic/linux: 4.15.0-112.113 -proposed tracker (LP: #1887048) * Packaging resync (LP: #1786013) - update dkms package versions * CVE-2020-11935 - SAUCE: aufs: do not call i_readcount_inc() - SAUCE: aufs: bugfix, IMA i_readcount * CVE-2020-10757 - mm: Fix mremap not considering huge pmd devmap * Update lockdown patches (LP: #1884159) - efi/efi_test: Lock down /dev/efi_test and require CAP_SYS_ADMIN - efi: Restrict efivar_ssdt_load when the kernel is locked down - powerpc/xmon: add read-only mode - powerpc/xmon: Restrict when kernel is locked down - [Config] CONFIG_XMON_DEFAULT_RO_MODE=y - SAUCE: acpi: disallow loading configfs acpi tables when locked down * seccomp_bpf fails on powerpc (LP: #1885757) - SAUCE: selftests/seccomp: fix ptrace tests on powerpc * Introduce the new NVIDIA 418-server and 440-server series, and update the current NVIDIA drivers (LP: #1881137) - [packaging] add signed modules for the 418-server and the 440-server flavours -- Khalid Elmously Thu, 09 Jul 2020 19:13:37 -0400 ** Changed in: linux (Ubuntu Bionic) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-10757 -- 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/1885757 Title: seccomp_bpf fails on powerpc Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Released Status in linux source package in Eoan: Fix Committed Status in linux source package in Focal: Fix Released Status in linux source package in Groovy: In Progress Bug description: [Impact] seccomp_bpf test fails on powerpc and ends up being disabled on some series, or causing engineers to waste their time verifying the same failures are the only ones we see every kernel release. [Test case] Run the test and notice there are no more failures. [Regression potential] We may break the test on different architectures. That doesn't break users, though, as the changes are only on tests. It has been tested at least on ppc64el and amd64. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1885757/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882955] Re: LXD 4.2 broken on linux-kvm due to missing VLAN filtering
This bug was fixed in the package linux-kvm - 4.15.0-1071.72 --- linux-kvm (4.15.0-1071.72) bionic; urgency=medium * bionic/linux-kvm: 4.15.0-1071.72 -proposed tracker (LP: #1887041) [ Ubuntu: 4.15.0-112.113 ] * bionic/linux: 4.15.0-112.113 -proposed tracker (LP: #1887048) * Packaging resync (LP: #1786013) - update dkms package versions * CVE-2020-11935 - SAUCE: aufs: do not call i_readcount_inc() - SAUCE: aufs: bugfix, IMA i_readcount * CVE-2020-10757 - mm: Fix mremap not considering huge pmd devmap * Update lockdown patches (LP: #1884159) - efi/efi_test: Lock down /dev/efi_test and require CAP_SYS_ADMIN - efi: Restrict efivar_ssdt_load when the kernel is locked down - powerpc/xmon: add read-only mode - powerpc/xmon: Restrict when kernel is locked down - [Config] CONFIG_XMON_DEFAULT_RO_MODE=y - SAUCE: acpi: disallow loading configfs acpi tables when locked down * seccomp_bpf fails on powerpc (LP: #1885757) - SAUCE: selftests/seccomp: fix ptrace tests on powerpc * Introduce the new NVIDIA 418-server and 440-server series, and update the current NVIDIA drivers (LP: #1881137) - [packaging] add signed modules for the 418-server and the 440-server flavours [ Ubuntu: 4.15.0-111.112 ] * bionic/linux: 4.15.0-111.112 -proposed tracker (LP: #1886999) * Bionic update: upstream stable patchset 2020-05-07 (LP: #1877461) - SAUCE: mlxsw: Add missmerged ERR_PTR hunk * linux 4.15.0-109-generic network DoS regression vs -108 (LP: #1886668) - SAUCE: Revert "netprio_cgroup: Fix unlimited memory leak of v2 cgroups" linux-kvm (4.15.0-1070.71) bionic; urgency=medium * bionic/linux-kvm: 4.15.0-1070.71 -proposed tracker (LP: #1885807) * Build and ship a signed wireguard.ko (LP: #1861284) - [Config] kvm: wireguard -- enable on all architectures * LXD 4.2 broken on linux-kvm due to missing VLAN filtering (LP: #1882955) - [Config] VLAN_8021Q=m && BRIDGE_VLAN_FILTERING=y [ Ubuntu: 4.15.0-110.111 ] * bionic/linux: 4.15.0-110.111 -proposed tracker (LP: #1885814) * Packaging resync (LP: #1786013) - update dkms package versions * CVE-2020-11935 - SAUCE: aufs: do not call i_readcount_inc() - SAUCE: aufs: bugfix, IMA i_readcount * CVE-2020-10757 - mm: Fix mremap not considering huge pmd devmap * Update lockdown patches (LP: #1884159) - efi/efi_test: Lock down /dev/efi_test and require CAP_SYS_ADMIN - efi: Restrict efivar_ssdt_load when the kernel is locked down - powerpc/xmon: add read-only mode - powerpc/xmon: Restrict when kernel is locked down - [Config] CONFIG_XMON_DEFAULT_RO_MODE=y - SAUCE: acpi: disallow loading configfs acpi tables when locked down * seccomp_bpf fails on powerpc (LP: #1885757) - SAUCE: selftests/seccomp: fix ptrace tests on powerpc * Introduce the new NVIDIA 418-server and 440-server series, and update the current NVIDIA drivers (LP: #1881137) - [packaging] add signed modules for the 418-server and the 440-server flavours -- Khalid Elmously Thu, 09 Jul 2020 22:13:34 -0400 ** Changed in: linux-kvm (Ubuntu Bionic) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-10757 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-11935 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1882955 Title: LXD 4.2 broken on linux-kvm due to missing VLAN filtering Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Xenial: Fix Released Status in linux-kvm source package in Bionic: Fix Released Status in linux-kvm source package in Eoan: Fix Committed Status in linux-kvm source package in Focal: Fix Released Bug description: [Description] Some VLAN options (BRIDGE_VLAN_FILTERING, and its dependencies VLAN_8021Q*) were in a different state in Focal/kvm compared to Focal/generic: LXD now depends on BRIDGE_VLAN_FILTERING and due to this discrepancy it fails to work on the Focal/kvm kernel: fix it by aligning the config with Focal/generic [Fix] Apply the attached config patch [Regression potential] Low, just some config changes already present in generic. --- This is another case of linux-kvm having unexplained differences compared to linux-generic in areas that aren't related to hardware drivers (see other bug we filed for missing nft). This time, CPC is reporting that LXD no longer works on linux-kvm as we now set vlan filtering on our bridges to prevent containers from escaping firewalling through custom vlan tags. This relies on CONFIG_BRIDGE_VLAN_FILTERING which is a built-in on the generic kernel but is apparently missing on linux-kvm (I don't have any system running that kernel to confirm its config, but the behavior certainly matches that). We
[Kernel-packages] [Bug 1881137] Re: Introduce the new NVIDIA 418-server and 440-server series, and update the current NVIDIA drivers
This bug was fixed in the package linux - 4.15.0-112.113 --- linux (4.15.0-112.113) bionic; urgency=medium * bionic/linux: 4.15.0-112.113 -proposed tracker (LP: #1887048) * Packaging resync (LP: #1786013) - update dkms package versions * CVE-2020-11935 - SAUCE: aufs: do not call i_readcount_inc() - SAUCE: aufs: bugfix, IMA i_readcount * CVE-2020-10757 - mm: Fix mremap not considering huge pmd devmap * Update lockdown patches (LP: #1884159) - efi/efi_test: Lock down /dev/efi_test and require CAP_SYS_ADMIN - efi: Restrict efivar_ssdt_load when the kernel is locked down - powerpc/xmon: add read-only mode - powerpc/xmon: Restrict when kernel is locked down - [Config] CONFIG_XMON_DEFAULT_RO_MODE=y - SAUCE: acpi: disallow loading configfs acpi tables when locked down * seccomp_bpf fails on powerpc (LP: #1885757) - SAUCE: selftests/seccomp: fix ptrace tests on powerpc * Introduce the new NVIDIA 418-server and 440-server series, and update the current NVIDIA drivers (LP: #1881137) - [packaging] add signed modules for the 418-server and the 440-server flavours -- Khalid Elmously Thu, 09 Jul 2020 19:13:37 -0400 ** Changed in: linux (Ubuntu Bionic) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-10757 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1881137 Title: Introduce the new NVIDIA 418-server and 440-server series, and update the current NVIDIA drivers Status in linux package in Ubuntu: Incomplete Status in linux-restricted-modules package in Ubuntu: New Status in nvidia-graphics-drivers-418-server package in Ubuntu: Invalid Status in nvidia-graphics-drivers-440 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-440-server package in Ubuntu: New Status in nvidia-settings package in Ubuntu: New Status in linux source package in Bionic: Fix Released Status in linux-restricted-modules source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-440 source package in Bionic: In Progress Status in nvidia-graphics-drivers-440-server source package in Bionic: In Progress Status in nvidia-settings source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Released Status in linux-restricted-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-440 source package in Focal: In Progress Status in nvidia-graphics-drivers-440-server source package in Focal: Fix Committed Status in nvidia-settings source package in Focal: Fix Committed Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] 440.82: * New upstream release: - Added a workaround for Steam Play title DOOM Eternal, which overrides application requested memory locations, to ensure performance-critical resources be placed in video memory. - Allow presenting from queue families which only expose VK_QUEUE_COMPUTE_BIT when using XCB in addition to Xlib surfaces. - Fixed a bug that caused render-offloaded applications to crash on exit. - Fixed a driver installation failure on Linux kernel 5.6 release candidates, where the NVIDIA kernel module failed to build with error "implicit declaration of function 'timespec_to_ns'". - Fixed a driver installation failure on Linux kernel 5.6 release candidates, where the NVIDIA kernel module failed to build with error "implicit declaration of function 'getrawmonotonic'". - Fixed a driver installation failure on Linux kernel 5.6 release candidates, where the NVIDIA kernel module failed to build with error "implicit declaration of function 'timespec_to_ns'". - Fixed a driver installation failure on Linux kernel 5.6
[Kernel-packages] [Bug 1887968] Re: Pairing with Bluetooth LE mice fails on a Huawei Matebook 13 AMD laptop with Realtek RTL8822CE Wifi/Bluetooth combo adapter
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: bluez (Ubuntu)
Status: New => Confirmed
--
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/1887968
Title:
Pairing with Bluetooth LE mice fails on a Huawei Matebook 13 AMD
laptop with Realtek RTL8822CE Wifi/Bluetooth combo adapter
Status in bluez package in Ubuntu:
Confirmed
Bug description:
I'm using Ubuntu 20.04 on a Huawei Matebook 13 AMD laptop which seems
to use a Realtek RTL8822CE Wifi/Bluetooth combo adapter.
I've been unsuccessful to pair with 2 different bluetooth mice.
However bluetooth seems to work with other devices. I'm under the
impression that this problem only happens with Bluetooth LE devices.
Trying to pair using bluetoothctl fails with the
org.bluez.Error.AuthenticationCanceled error:
[bluetooth]# pair E5:5B:67:2A:09:76
Attempting to pair with E5:5B:67:2A:09:76
[CHG] Device E5:5B:67:2A:09:76 Connected: yes
[CHG] Device E5:5B:67:2A:09:76 Connected: no
Failed to pair: org.bluez.Error.AuthenticationCanceled
A quick google search for org.bluez.Error.AuthenticationCanceled
reported nothing relevant.
Running btmon while trying to pair with the device gives me the
following:
Bluetooth monitor ver 5.53
= Note: Linux version 5.4.0-40-generic (x86_64)
0.998188
= Note: Bluetooth subsystem version 2.22
0.998193
= New Index: E8:6F:38:9C:2B:3C (Primary,USB,hci0)
[hci0] 0.998194
= Open Index: E8:6F:38:9C:2B:3C
[hci0] 0.998195
= Index Info: E8:6F:38:9C:2B:3C (Realtek Semiconductor Corporation)
[hci0] 0.998197
@ MGMT Open: bluetoothd (privileged) version 1.14
{0x0001} 0.998198
@ MGMT Open: btmon (privileged) version 1.14
{0x0002} 0.998310
@ MGMT Command: Pair Device (0x0019) plen 8
{0x0001} [hci0] 8.162442
LE Address: E5:5B:67:2A:09:76 (Static)
Capability: KeyboardDisplay (0x04)
< HCI Command: LE Set Extended Scan Parameters (0x08|0x0041) plen 8
#1 [hci0] 8.162527
Own address type: Public (0x00)
Filter policy: Ignore not in white list (0x01)
PHYs: 0x01
Entry 0: LE 1M
Type: Passive (0x00)
Interval: 60.000 msec (0x0060)
Window: 30.000 msec (0x0030)
> HCI Event: Command Complete (0x0e) plen 4
#2 [hci0] 8.284618
LE Set Extended Scan Parameters (0x08|0x0041) ncmd 2
Status: Success (0x00)
< HCI Command: LE Set Extended Scan Enable (0x08|0x0042) plen 6
#3 [hci0] 8.284654
Extended scan: Enabled (0x01)
Filter duplicates: Enabled (0x01)
Duration: 0 msec (0x)
Period: 0.00 sec (0x)
> HCI Event: Command Complete (0x0e) plen 4
#4 [hci0] 8.289616
LE Set Extended Scan Enable (0x08|0x0042) ncmd 2
Status: Success (0x00)
> HCI Event: LE Meta Event (0x3e) plen 52
#5 [hci0] 8.343614
LE Extended Advertising Report (0x0d)
Num reports: 1
Entry 0
Event type: 0x0013
Props: 0x0013
Connectable
Scannable
Use legacy advertising PDUs
Data status: Complete
Legacy PDU Type: ADV_IND (0x0013)
Address type: Random (0x01)
Address: E5:5B:67:2A:09:76 (Static)
Primary PHY: LE 1M
Secondary PHY: No packets
SID: no ADI field (0xff)
TX power: 127 dBm
RSSI: -20 dBm (0xec)
Periodic advertising invteral: 0.00 msec (0x)
Direct address type: Public (0x00)
Direct address: 00:00:00:00:00:00 (OUI 00-00-00)
Data length: 0x1a
03 19 c2 03 02 01 05
[Kernel-packages] [Bug 1878421] Re: Using two GPUs with one monitor each, one is always black
mhm, ubuntu-session is same...i see cursor but no background/window while dragging, this time it looks stable, after loggin out (from ubuntu-session), i see login-form on laptop-screen and purple background on external monitor. after logging into flashback it's same as in ubuntu-session with black screen, cursor visible but no windows -- 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/1878421 Title: Using two GPUs with one monitor each, one is always black Status in Mutter: New Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: Hi, i try to use external monitor on my dell G5 2019 (5590). works on ubuntu 18.4 (after reboot) using prime-select nvidia. did this on 20.4 (prime-select + reboot because logoff/login again still don't work) and it hang on boot while showing ubuntu bootscreen with animation (not stopped, but also response to esc-key to show terminal-output) on the monitor (need to switch off). booted again where monitor is configured to other input, boot works, i see it in preferences dialog as second monitor, but if i configure input on monitor i have no signal.. anything i can try? regards Frank ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME-Flashback:GNOME Date: Wed May 13 15:21:08 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:08ea] NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f91] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell TU117M [GeForce GTX 1650 Mobile / Max-Q] [1028:08ea] InstallationDate: Installed on 2020-04-27 (16 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 27c6:530c Shenzhen Goodix Technology Co.,Ltd. Fingerprint Reader Bus 001 Device 002: ID 0c45:671f Microdia Integrated_Webcam_HD Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. G5 5590 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=7c9113b7-ca65-4c46-9435-f5d2b73bab72 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/07/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0KW84T dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd02/07/2020:svnDellInc.:pnG55590:pvr:rvnDellInc.:rn0KW84T:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: GSeries dmi.product.name: G5 5590 dmi.product.sku: 08EA dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1878421/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1711283] Re: few kernel selftest failed on Ubuntu 17.10
The cycle_test failure does not reproduce on everyrun. In order to validate you'll have to run the test a few times. Moreover, seems that ZZ lpars are easier to reproduce this. Last, this patch fixes this bug: https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?id=3337bf41e0dd70b4064cdf60acdfcdc2d050066c -- 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/1711283 Title: few kernel selftest failed on Ubuntu 17.10 Status in The Ubuntu-power-systems project: Won't Fix Status in linux package in Ubuntu: Won't Fix Bug description: == Comment: #0 - Harish Sriram - 2017-08-01 05:11:09 == Problem Description Few kernel selftest failed on Ubuntu 17.10 Environment -- Kernel Build: 4.11.0-10-generic System Name : ltc-test-ci2 Model : 8247-22L Platform: PowerNV ( P8 ) Uname output --- # uname -a Linux ltc-test-ci2 4.11.0-10-generic #15-Ubuntu SMP Thu Jun 29 15:02:54 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux Steps to reproduce: 1. Get kernel source using apt source 2. Start powerpc specific tests The following FAILS are observed. selftests: cycles_test [FAIL] selftests: cycles_with_freeze_test [FAIL] selftests: pmc56_overflow_test [FAIL] selftests: ebb_vs_cpu_event_test [FAIL] selftests: cpu_event_vs_ebb_test [FAIL] selftests: task_event_vs_ebb_test [FAIL] selftests: multi_ebb_procs_test [FAIL] selftests: multi_counter_test [FAIL] selftests: pmae_handling_test [FAIL] selftests: close_clears_pmcc_test [FAIL] selftests: instruction_count_test [FAIL] selftests: ebb_on_willing_child_test [FAIL] selftests: back_to_back_ebbs_test [FAIL] selftests: lost_exception_test [FAIL] selftests: cycles_with_mmcr2_test [FAIL] selftests: tm-vmxcopy [FAIL] Full run log is attached. == Comment: #5 - Harish Sriram - 2017-08-08 03:33:36 == With the latest ubuntu mainline kernel 4.13-rc4 from http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13-rc4/, I see following additional failures selftests: ptrace-gpr [FAIL] selftests: ptrace-tm-gpr [FAIL] selftests: ptrace-tm-spd-gpr [FAIL] # uname -a Linux ltc-test-ci2 4.13.0-041300rc4-generic #201708062231 SMP Mon Aug 7 03:29:19 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux Thanks, Harish To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1711283/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830151] Re: ebb: cycles_test in powerpc from ubuntu_kernel_selftests failed on B-hwe P9
Actually, this bug does not reproduce on everyrun. In order to validate
you'll have to run the test a few times. Moreover, seems that ZZ lpars
are easier to reproduce this.
Last, this patch fixes this bug:
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?id=3337bf41e0dd70b4064cdf60acdfcdc2d050066c
--
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/1830151
Title:
ebb: cycles_test in powerpc from ubuntu_kernel_selftests failed on
B-hwe P9
Status in ubuntu-kernel-tests:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Bug description:
This test has passed with Cosmic kernel on the same node ("baltar"),
but not with the 4.18 kernel on Bionic.
selftests: ebb: cycles_test
test: cycles
tags: git_version:unknown
EBB Handler is at 0x10004170
ebb_state:
ebb_count = 10
spurious = 0
negative = 0
no_overflow = 0
pmc[1] count = 0x2843f
pmc[2] count = 0x0
pmc[3] count = 0x0
pmc[4] count = 0x0
pmc[5] count = 0x0
pmc[6] count = 0x0
HW state:
MMCR0 0x8400 FC PMAE
MMCR2 0x
EBBHR 0x10004170
BESCR 0x8000 GE
PMC1 0x4000
PMC2 0x
PMC3 0x
PMC4 0x
PMC5 0x00028b3f
PMC6 0x0002ac80
SIAR 0x100035d4
Trace buffer dump:
address 0x71a628a2
tail 0x71a628a201f6
size 1048576
overflow false
Content:
[0]: counter = 1
[1]: register SPRN_MMCR0 = 0x8080
[2]: register SPRN_PMC1 = 0x8004
[3]: counter = 2
[4]: register SPRN_MMCR0 = 0x8080
[5]: register SPRN_PMC1 = 0x8004
[6]: counter = 3
[7]: register SPRN_MMCR0 = 0x8080
[8]: register SPRN_PMC1 = 0x8004
[FAIL] Test FAILED on line 52
[9]: counter = 4
[10]: register SPRN_MMCR0 = 0x8080
[11]: register SPRN_PMC1 = 0x8004
[12]: counter = 5
[13]: register SPRN_MMCR0 = 0x8080
[14]: register SPRN_PMC1 = 0x8004
[15]: counter = 6
[16]: register SPRN_MMCR0 = 0x8080
[17]: register SPRN_PMC1 = 0x8004
[18]: counter = 7
[19]: register SPRN_MMCR0 = 0x8080
[20]: register SPRN_PMC1 = 0x8004
[21]: counter = 8
[22]: register SPRN_MMCR0 = 0x8080
[23]: register SPRN_PMC1 = 0x8004
[24]: counter = 9
[25]: register SPRN_MMCR0 = 0x8080
[26]: register SPRN_PMC1 = 0x8004
[27]: counter = 10
[28]: register SPRN_MMCR0 = 0x8080
[29]: register SPRN_PMC1 = 0x8004
[30]: register SPRN_PMC1 = 0x4417
PMC1 count (0x2843f) above upper limit 0x283e8 (+0x57)
failure: cycles
not ok 1..3 selftests: ebb: cycles_test [FAIL]
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1830151/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888331] Re: Wakeup the system by touching the touchpad
** Tags added: oem-priority originate-from-1880123 somerville
** Description changed:
[Impact]
Can't wake up by touching the touchpad.
[Fix]
- 1.gpio: With 'commit 461c1a7d4733 ("gpiolib: override irq_enable/disable")'
- gpiolib overrides irqchip's irq_enable and irq_disable callbacks. If
irq_disable
- callback is implemented then genirq takes unlazy path to disable irq.
Underlying irqchip
- may not want to implement irq_disable callback to lazy disable irq
- when client drivers invokes disable_irq(). By overriding irq_disable
callback,
- gpiolib ends up always unlazy disabling IRQ.
- Allow gpiolib to lazy disable IRQs by overriding irq_disable callback only
- if irqchip implemented irq_disable. In cases where irq_disable is not
- implemented irq_mask is overridden. Similarly override irq_enable callback
- only if irqchip implemented irq_enable otherwise irq_unmask is overridden.
+ 1.gpio: With 'commit 461c1a7d4733 ("gpiolib: override irq_enable/disable")'
+ gpiolib overrides irqchip's irq_enable and irq_disable callbacks. If
irq_disable
+ callback is implemented then genirq takes unlazy path to disable irq.
Underlying irqchip
+ may not want to implement irq_disable callback to lazy disable irq
+ when client drivers invokes disable_irq(). By overriding irq_disable
callback,
+ gpiolib ends up always unlazy disabling IRQ.
+ Allow gpiolib to lazy disable IRQs by overriding irq_disable callback only
+ if irqchip implemented irq_disable. In cases where irq_disable is not
+ implemented irq_mask is overridden. Similarly override irq_enable callback
+ only if irqchip implemented irq_enable otherwise irq_unmask is overridden.
2. hid: Many laptops can be woken up from Suspend-to-Idle by touchpad. This is
-also the default behavior on other OSes.
-However, if touchpad and touchscreen contact to each other when lid is
-closed, wakeup events can be triggered inadventertly.
-So let's disable the wakeup by default, but enable the wakeup capability
-so users can enable it at their own discretion.
+ also the default behavior on other OSes.
+ However, if touchpad and touchscreen contact to each other when lid is
+ closed, wakeup events can be triggered inadventertly.
+ So let's disable the wakeup by default, but enable the wakeup capability
+ so users can enable it at their own discretion.
[test]
- With the patch and enable HID's power/wakeup, the system can wake up by
touching the touchpad.
+ With the patch and manually enable HID's power/wakeup, the system can wake up
by touching the touchpad.
[Regression Potential]
Low. The two patches are already landed in the upstream.
--
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/1888331
Title:
Wakeup the system by touching the touchpad
Status in HWE Next:
New
Status in linux-oem-5.6 package in Ubuntu:
New
Status in linux-oem-5.6 source package in Focal:
In Progress
Bug description:
[Impact]
Can't wake up by touching the touchpad.
[Fix]
1.gpio: With 'commit 461c1a7d4733 ("gpiolib: override irq_enable/disable")'
gpiolib overrides irqchip's irq_enable and irq_disable callbacks. If
irq_disable
callback is implemented then genirq takes unlazy path to disable irq.
Underlying irqchip
may not want to implement irq_disable callback to lazy disable irq
when client drivers invokes disable_irq(). By overriding irq_disable
callback,
gpiolib ends up always unlazy disabling IRQ.
Allow gpiolib to lazy disable IRQs by overriding irq_disable callback only
if irqchip implemented irq_disable. In cases where irq_disable is not
implemented irq_mask is overridden. Similarly override irq_enable callback
only if irqchip implemented irq_enable otherwise irq_unmask is overridden.
2. hid: Many laptops can be woken up from Suspend-to-Idle by touchpad. This is
also the default behavior on other OSes.
However, if touchpad and touchscreen contact to each other when lid is
closed, wakeup events can be triggered inadventertly.
So let's disable the wakeup by default, but enable the wakeup capability
so users can enable it at their own discretion.
[test]
With the patch and manually enable HID's power/wakeup, the system can wake up
by touching the touchpad.
[Regression Potential]
Low. The two patches are already landed in the upstream.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1888331/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1885270] Re: Touchpad stopped working after upgrading to Ubuntu 20.04
Even upgrading the kernel to 5.7.8-050708-generic did not solve the problem. Also, "dyndbg=file drivers/input/* +pt" i8042.debug=1 log_buf_len=32M command solved the problem for some minutes only then the touchpad again started to be detected as ps2 generic mouse. -- 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/1885270 Title: Touchpad stopped working after upgrading to Ubuntu 20.04 Status in linux package in Ubuntu: Incomplete Bug description: When I upgraded to Ubuntu 20.04 my touchpad stopped working. When I used the command xinput to list the input devices there was a PS/2 Generic Mouse registered instead of my Lenovo Yoga 13 touchpad. I tried to search for the same on the askubuntu forum. I got the answer that to try and remove psmouse and then again add it using the command sudo modprobe -r psmouse; sudo modprobe psmouse This initially solved my problem but later on the same issue arose after restarting the machine. The touchpad also is again reported as a generic mouse if the system is suspended. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-39-generic 5.4.0-39.43 ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Uname: Linux 5.4.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lokesh 1790 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jun 26 16:45:45 2020 InstallationDate: Installed on 2019-08-15 (315 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO Mocca 2.0 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-39-generic root=UUID=a610e76e-890e-442a-b764-c81d6becd466 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-39-generic N/A linux-backports-modules-5.4.0-39-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-05-15 (42 days ago) dmi.bios.date: 02/28/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 66CN55WW dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 3196Win8 STD MBR IPG dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga 13 dmi.modalias: dmi:bvnLENOVO:bvr66CN55WW:bd02/28/2013:svnLENOVO:pnMocca2.0:pvrYoga13:rvnLENOVO:rnINVALID:rvr3196Win8STDMBRIPG:cvnLENOVO:ct10:cvrYoga13: dmi.product.family: IDEAPAD dmi.product.name: Mocca 2.0 dmi.product.sku: LENOVO_BI_IDEAPAD66 dmi.product.version: Yoga 13 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885270/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886172] Re: high speed data to usb disk makes the kernel think that is has been unmounted
** Description changed:
Description:
When the speed of data with a usb disk device is too high, the probes
that check if the disk still exists is missed. This makes the disk to be
unmounted and is remounted with an other drive letter (/dev/sdX). If
this disk is the root ("/"), the computer hangs.
A usb SSD-disk (4 TB) connected to a USB port reproduce this bug easily.
This has never happened with a mechanical USB-drive.
Symptoms and how to reproduce:
1) (Disk mounted as root) Computer hangs. Only way to get started again
is a hard reset.
2) (Erasing disk, not mounted as root) If you erase a disk with dd ("dd
if=/dev/zero of=/dev/sdX"), the disk disappears from the mounted list
and reappears as an other drive letter. In my case the data is
redirected to /dev/null and the fans speed up. The apparent data
transfer speed is also increased. Usually this happens after about 45 to
60 minutes.
3) Fill RAM with programs and make sure the swap to this disk is used.
Bug found in:
$ uname -a
Linux pb-189b1884 5.4.0-40-generic #44-Ubuntu SMP Tue Jun 23 00:01:04 UTC
2020 x86_64 x86_64 x86_64 GNU/Linux
$ cat /proc/version_signature
Ubuntu 5.4.0-40.44-generic 5.4.44
- Bug not found in:
-
- Linux v4.15 (Ubuntu Bionic)
-
Hardware:
Tested with slower and faster computers. Tested directly connected to a
computer and via a hub. They all reproduce this bug.
Workaround:
None found.
- ---
+ ---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
AudioDevicesInUse:
- USERPID ACCESS COMMAND
- /dev/snd/controlC1: user 6813 F pulseaudio
- /dev/snd/controlC0: user 6813 F pulseaudio
+ USERPID ACCESS COMMAND
+ /dev/snd/controlC1: user 6813 F pulseaudio
+ /dev/snd/controlC0: user 6813 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: MATE
DistroRelease: Ubuntu 20.04
MachineType: ASUSTeK COMPUTER INC. GL503VM
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux (not installed)
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic
root=UUID=74545cc2-bc7e-11ea-9c1b-6b408850adf5 ro fsck.repair=yes
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
RelatedPackageVersions:
- linux-restricted-modules-5.4.0-40-generic N/A
- linux-backports-modules-5.4.0-40-generic N/A
- linux-firmware1.187.1
+ linux-restricted-modules-5.4.0-40-generic N/A
+ linux-backports-modules-5.4.0-40-generic N/A
+ linux-firmware1.187.1
Tags: focal
Uname: Linux 5.4.0-40-generic x86_64
UnreportableReason: This report is about a package that is not installed.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: sudo vboxusers wireshark
WifiSyslog:
-
+
_MarkForUpload: False
dmi.bios.date: 04/29/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: GL503VM.314
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: GL503VM
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.:bvrGL503VM.314:bd04/29/2019:svnASUSTeKCOMPUTERINC.:pnGL503VM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL503VM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: ROG
dmi.product.name: GL503VM
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
--
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/1886172
Title:
high speed data to usb disk makes the kernel think that is has been
unmounted
Status in linux package in Ubuntu:
Confirmed
Bug description:
Description:
When the speed of data with a usb disk device is too high, the probes
that check if the disk still exists is missed. This makes the disk to
be unmounted and is remounted with an other drive letter (/dev/sdX).
If this disk is the root ("/"), the computer hangs.
A usb SSD-disk (4 TB) connected to a USB port reproduce this bug
easily. This has never happened with a mechanical USB-drive.
Symptoms and how to reproduce:
1) (Disk mounted as root) Computer hangs. Only way to get started
again is a hard reset.
2) (Erasing disk, not mounted as root) If you erase a disk with dd
("dd if=/dev/zero of=/dev/sdX"), the disk disappears from the mounted
list and reappears as an other drive letter. In my case the data is
redirected to /dev/null and the fans speed up. The apparent data
transfer speed is also increased. Usually this happens after about 45
to 60 minutes.
3) Fill RAM with programs and make sure the swap to this disk is used.
Bug found in:
$ uname -a
Linux pb-189b1884 5.4.0-40-generic #44-Ubuntu SMP Tue Jun 23
[Kernel-packages] [Bug 1886172] Re: high speed data to usb disk makes the kernel think that is has been unmounted
Log of udev event, when the bug happens. # udevadm monitor | grep -v power_supply monitor will print the received events for: UDEV - the event which udev sends out after rule processing KERNEL - the kernel uevent KERNEL[25.226057] remove /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host4/target4:0:0/4:0:0:0/bsg/4:0:0:0 (bsg) KERNEL[25.232094] remove /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host4/target4:0:0/4:0:0:0/scsi_generic/sg2 (scsi_generic) UDEV [25.232131] remove /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host4/target4:0:0/4:0:0:0/scsi_generic/sg2 (scsi_generic) KERNEL[25.232148] remove /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host4/target4:0:0/4:0:0:0/scsi_device/4:0:0:0 (scsi_device) UDEV [25.232163] remove /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host4/target4:0:0/4:0:0:0/scsi_disk/4:0:0:0 (scsi_disk) KERNEL[25.232176] remove /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host4/target4:0:0/4:0:0:0/scsi_disk/4:0:0:0 (scsi_disk) UDEV [25.234471] remove /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host4/target4:0:0/4:0:0:0/scsi_device/4:0:0:0 (scsi_device) UDEV [25.237032] remove /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host4/target4:0:0/4:0:0:0/bsg/4:0:0:0 (bsg) KERNEL[257785.993301] remove /devices/virtual/bdi/8:32 (bdi) KERNEL[257785.994189] remove /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host4/target4:0:0/4:0:0:0/block/sdc (block) UDEV [257785.994536] remove /devices/virtual/bdi/8:32 (bdi) UDEV [257785.996938] remove /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host4/target4:0:0/4:0:0:0/block/sdc (block) KERNEL[257786.236165] unbind /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host4/target4:0:0/4:0:0:0 (scsi) KERNEL[257786.236196] remove /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host4/target4:0:0/4:0:0:0 (scsi) UDEV [257786.238169] unbind /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host4/target4:0:0/4:0:0:0 (scsi) UDEV [257786.239825] remove /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host4/target4:0:0/4:0:0:0 (scsi) KERNEL[257786.268117] remove /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host4/target4:0:0 (scsi) KERNEL[257786.268147] remove /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host4/scsi_host/host4 (scsi_host) KERNEL[257786.268166] remove /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host4 (scsi) KERNEL[257786.269320] unbind /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0 (usb) KERNEL[257786.269363] remove /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0 (usb) KERNEL[257786.269829] unbind /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2 (usb) KERNEL[257786.269869] remove /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2 (usb) UDEV [257786.270012] remove /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host4/target4:0:0 (scsi) UDEV [257786.270648] remove /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host4/scsi_host/host4 (scsi_host) UDEV [257786.271546] remove /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host4 (scsi) UDEV [257786.272602] unbind /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0 (usb) UDEV [257786.273926] remove /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0 (usb) UDEV [257786.275670] unbind /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2 (usb) UDEV [257786.284734] remove /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2 (usb) KERNEL[257790.500838] add /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2 (usb) KERNEL[257790.501540] add /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0 (usb) KERNEL[257790.503117] add
[Kernel-packages] [Bug 1886172] Re: high speed data to usb disk makes the kernel think that is has been unmounted
Log of udev event, when the bug happens. # udevadm monitor | grep -v power_supply monitor will print the received events for: UDEV - the event which udev sends out after rule processing KERNEL - the kernel uevent KERNEL[255114.318220] remove /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0/4:0:0:0/bsg/4:0:0:0 (bsg) KERNEL[255114.320177] remove /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0/4:0:0:0/scsi_generic/sg2 (scsi_generic) KERNEL[255114.320198] remove /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0/4:0:0:0/scsi_device/4:0:0:0 (scsi_device) KERNEL[255114.320209] remove /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0/4:0:0:0/scsi_disk/4:0:0:0 (scsi_disk) UDEV [255114.320619] remove /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0/4:0:0:0/scsi_generic/sg2 (scsi_generic) UDEV [255114.321338] remove /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0/4:0:0:0/bsg/4:0:0:0 (bsg) UDEV [255114.321948] remove /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0/4:0:0:0/scsi_disk/4:0:0:0 (scsi_disk) UDEV [255114.325400] remove /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0/4:0:0:0/scsi_device/4:0:0:0 (scsi_device) KERNEL[255123.206586] remove /devices/virtual/bdi/8:32 (bdi) KERNEL[255123.206734] remove /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0/4:0:0:0/block/sdc (block) UDEV [255123.207599] remove /devices/virtual/bdi/8:32 (bdi) UDEV [255123.209019] remove /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0/4:0:0:0/block/sdc (block) KERNEL[255123.452120] unbind /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0/4:0:0:0 (scsi) KERNEL[255123.452156] remove /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0/4:0:0:0 (scsi) UDEV [255123.454017] unbind /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0/4:0:0:0 (scsi) UDEV [255123.455196] remove /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0/4:0:0:0 (scsi) KERNEL[255123.484123] remove /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0 (scsi) KERNEL[255123.484149] remove /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/scsi_host/host4 (scsi_host) KERNEL[255123.484174] remove /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4 (scsi) KERNEL[255123.485174] unbind /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0 (usb) KERNEL[255123.485215] remove /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0 (usb) UDEV [255123.485449] remove /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0 (scsi) KERNEL[255123.485698] unbind /devices/pci:00/:00:14.0/usb2/2-2 (usb) KERNEL[255123.485730] remove /devices/pci:00/:00:14.0/usb2/2-2 (usb) UDEV [255123.485994] remove /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/scsi_host/host4 (scsi_host) UDEV [255123.486906] remove /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4 (scsi) UDEV [255123.487940] unbind /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0 (usb) UDEV [255123.489062] remove /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0 (usb) UDEV [255123.490615] unbind /devices/pci:00/:00:14.0/usb2/2-2 (usb) UDEV [255123.499129] remove /devices/pci:00/:00:14.0/usb2/2-2 (usb) KERNEL[255126.952713] add /devices/pci:00/:00:14.0/usb2/2-2 (usb) KERNEL[255126.953377] add /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0 (usb) KERNEL[255126.955007] add /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host5 (scsi) KERNEL[255126.955119] add /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host5/scsi_host/host5 (scsi_host) KERNEL[255126.955164] bind /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0 (usb) KERNEL[255126.955209] bind /devices/pci:00/:00:14.0/usb2/2-2 (usb) KERNEL[255126.958067] add /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host5/target5:0:0 (scsi) KERNEL[255126.958155] add /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host5/target5:0:0/5:0:0:0 (scsi) KERNEL[255126.958177] add /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host5/target5:0:0/5:0:0:0/scsi_disk/5:0:0:0 (scsi_disk) KERNEL[255126.958199] bind /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host5/target5:0:0/5:0:0:0 (scsi) KERNEL[255126.958216] add /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host5/target5:0:0/5:0:0:0/scsi_device/5:0:0:0 (scsi_device) KERNEL[255126.958288] add /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host5/target5:0:0/5:0:0:0/scsi_generic/sg2 (scsi_generic) KERNEL[255126.958361] add /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host5/target5:0:0/5:0:0:0/bsg/5:0:0:0 (bsg) KERNEL[255126.959138] add /devices/virtual/bdi/8:48 (bdi) UDEV [255126.960879] add
[Kernel-packages] [Bug 1886172] Re: high speed data to usb disk makes the kernel think that is has been unmounted
Log of udev event, when the bug happens. # udevadm monitor | grep -v power_supply monitor will print the received events for: UDEV - the event which udev sends out after rule processing KERNEL - the kernel uevent KERNEL[10316.148582] remove /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0/4:0:0:0/bsg/4:0:0:0 (bsg) KERNEL[10316.148718] remove /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0/4:0:0:0/scsi_generic/sg2 (scsi_generic) KERNEL[10316.148737] remove /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0/4:0:0:0/scsi_device/4:0:0:0 (scsi_device) KERNEL[10316.148810] remove /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0/4:0:0:0/scsi_disk/4:0:0:0 (scsi_disk) UDEV [10316.150795] remove /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0/4:0:0:0/scsi_generic/sg2 (scsi_generic) UDEV [10316.151259] remove /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0/4:0:0:0/bsg/4:0:0:0 (bsg) UDEV [10316.153358] remove /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0/4:0:0:0/scsi_disk/4:0:0:0 (scsi_disk) UDEV [10316.153443] remove /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0/4:0:0:0/scsi_device/4:0:0:0 (scsi_device) KERNEL[10325.527284] remove /devices/virtual/bdi/8:32 (bdi) KERNEL[10325.527425] remove /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0/4:0:0:0/block/sdc (block) UDEV [10325.528344] remove /devices/virtual/bdi/8:32 (bdi) UDEV [10325.529371] remove /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0/4:0:0:0/block/sdc (block) KERNEL[10325.772119] unbind /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0/4:0:0:0 (scsi) KERNEL[10325.772152] remove /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0/4:0:0:0 (scsi) UDEV [10325.774112] unbind /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0/4:0:0:0 (scsi) UDEV [10325.775045] remove /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0/4:0:0:0 (scsi) KERNEL[10325.796104] remove /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0 (scsi) KERNEL[10325.796133] remove /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/scsi_host/host4 (scsi_host) KERNEL[10325.796152] remove /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4 (scsi) KERNEL[10325.796751] unbind /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0 (usb) KERNEL[10325.796785] remove /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0 (usb) KERNEL[10325.797247] unbind /devices/pci:00/:00:14.0/usb2/2-2 (usb) KERNEL[10325.797286] remove /devices/pci:00/:00:14.0/usb2/2-2 (usb) UDEV [10325.797543] remove /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0 (scsi) UDEV [10325.798531] remove /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/scsi_host/host4 (scsi_host) UDEV [10325.799470] remove /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4 (scsi) UDEV [10325.800764] unbind /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0 (usb) UDEV [10325.801790] remove /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0 (usb) UDEV [10325.803192] unbind /devices/pci:00/:00:14.0/usb2/2-2 (usb) UDEV [10325.822894] remove /devices/pci:00/:00:14.0/usb2/2-2 (usb) KERNEL[10328.672752] add /devices/pci:00/:00:14.0/usb2/2-2 (usb) KERNEL[10328.674111] add /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0 (usb) KERNEL[10328.675645] add /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host5 (scsi) KERNEL[10328.675684] add /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host5/scsi_host/host5 (scsi_host) KERNEL[10328.675725] bind /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0 (usb) KERNEL[10328.675770] bind /devices/pci:00/:00:14.0/usb2/2-2 (usb) KERNEL[10328.676723] add /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host5/target5:0:0 (scsi) KERNEL[10328.677293] add /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host5/target5:0:0/5:0:0:0 (scsi) KERNEL[10328.677315] add /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host5/target5:0:0/5:0:0:0/scsi_disk/5:0:0:0 (scsi_disk) KERNEL[10328.677338] bind /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host5/target5:0:0/5:0:0:0 (scsi) KERNEL[10328.677357] add /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host5/target5:0:0/5:0:0:0/scsi_device/5:0:0:0 (scsi_device) KERNEL[10328.677379] add /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host5/target5:0:0/5:0:0:0/scsi_generic/sg2 (scsi_generic) KERNEL[10328.677400] add /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host5/target5:0:0/5:0:0:0/bsg/5:0:0:0 (bsg) KERNEL[10328.677975] add /devices/virtual/bdi/8:48 (bdi) UDEV [10328.679302] add /devices/virtual/bdi/8:48 (bdi) UDEV
[Kernel-packages] [Bug 1886172] Re: high speed data to usb disk makes the kernel think that is has been unmounted
Log of udev event, when the bug happens. # udevadm monitor | grep -v power_supply monitor will print the received events for: UDEV - the event which udev sends out after rule processing KERNEL - the kernel uevent KERNEL[4837.212964] remove /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.3/2-4.4.3:1.0/host5/target5:0:0/5:0:0:0/bsg/5:0:0:0 (bsg) KERNEL[4837.218270] remove /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.3/2-4.4.3:1.0/host5/target5:0:0/5:0:0:0/scsi_generic/sg3 (scsi_generic) UDEV [4837.218305] remove /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.3/2-4.4.3:1.0/host5/target5:0:0/5:0:0:0/scsi_disk/5:0:0:0 (scsi_disk) KERNEL[4837.218325] remove /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.3/2-4.4.3:1.0/host5/target5:0:0/5:0:0:0/scsi_device/5:0:0:0 (scsi_device) UDEV [4837.218349] remove /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.3/2-4.4.3:1.0/host5/target5:0:0/5:0:0:0/bsg/5:0:0:0 (bsg) KERNEL[4837.218364] remove /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.3/2-4.4.3:1.0/host5/target5:0:0/5:0:0:0/scsi_disk/5:0:0:0 (scsi_disk) UDEV [4837.218382] remove /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.3/2-4.4.3:1.0/host5/target5:0:0/5:0:0:0/scsi_device/5:0:0:0 (scsi_device) UDEV [4837.219394] remove /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.3/2-4.4.3:1.0/host5/target5:0:0/5:0:0:0/scsi_generic/sg3 (scsi_generic) KERNEL[4846.579833] remove /devices/virtual/bdi/8:48 (bdi) KERNEL[4846.579956] remove /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.3/2-4.4.3:1.0/host5/target5:0:0/5:0:0:0/block/sdd (block) UDEV [4846.580945] remove /devices/virtual/bdi/8:48 (bdi) UDEV [4846.582743] remove /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.3/2-4.4.3:1.0/host5/target5:0:0/5:0:0:0/block/sdd (block) KERNEL[4846.824123] unbind /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.3/2-4.4.3:1.0/host5/target5:0:0/5:0:0:0 (scsi) KERNEL[4846.824157] remove /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.3/2-4.4.3:1.0/host5/target5:0:0/5:0:0:0 (scsi) UDEV [4846.826395] unbind /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.3/2-4.4.3:1.0/host5/target5:0:0/5:0:0:0 (scsi) UDEV [4846.827776] remove /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.3/2-4.4.3:1.0/host5/target5:0:0/5:0:0:0 (scsi) KERNEL[4846.848222] remove /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.3/2-4.4.3:1.0/host5/target5:0:0 (scsi) KERNEL[4846.848254] remove /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.3/2-4.4.3:1.0/host5/scsi_host/host5 (scsi_host) KERNEL[4846.848271] remove /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.3/2-4.4.3:1.0/host5 (scsi) KERNEL[4846.849427] unbind /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.3/2-4.4.3:1.0 (usb) KERNEL[4846.849470] remove /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.3/2-4.4.3:1.0 (usb) UDEV [4846.849777] remove /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.3/2-4.4.3:1.0/host5/target5:0:0 (scsi) KERNEL[4846.850038] unbind /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.3 (usb) KERNEL[4846.850071] remove /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.3 (usb) UDEV [4846.850475] remove /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.3/2-4.4.3:1.0/host5/scsi_host/host5 (scsi_host) UDEV [4846.851513] remove /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.3/2-4.4.3:1.0/host5 (scsi) UDEV [4846.852747] unbind /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.3/2-4.4.3:1.0 (usb) UDEV [4846.854079] remove /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.3/2-4.4.3:1.0 (usb) UDEV [4846.855663] unbind /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.3 (usb) UDEV [4846.863974] remove /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.3 (usb) KERNEL[4849.780952] add /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.3 (usb) KERNEL[4849.781689] add /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.3/2-4.4.3:1.0 (usb) KERNEL[4849.783493] add /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.3/2-4.4.3:1.0/host6 (scsi) KERNEL[4849.783529] add /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.3/2-4.4.3:1.0/host6/scsi_host/host6 (scsi_host) KERNEL[4849.783568] bind /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.3/2-4.4.3:1.0 (usb) KERNEL[4849.783607] bind /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.3 (usb) KERNEL[4849.786356] add /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.3/2-4.4.3:1.0/host6/target6:0:0 (scsi) KERNEL[4849.786442] add /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.3/2-4.4.3:1.0/host6/target6:0:0/6:0:0:0 (scsi) KERNEL[4849.786462] add /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.3/2-4.4.3:1.0/host6/target6:0:0/6:0:0:0/scsi_disk/6:0:0:0 (scsi_disk) KERNEL[4849.786482] bind
[Kernel-packages] [Bug 1886172] Re: high speed data to usb disk makes the kernel think that is has been unmounted
Log of udev event, when the bug happens. # udevadm monitor | grep -v power_supply monitor will print the received events for: UDEV - the event which udev sends out after rule processing KERNEL - the kernel uevent KERNEL[255114.318220] remove /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0/4:0:0:0/bsg/4:0:0:0 (bsg) KERNEL[255114.320177] remove /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0/4:0:0:0/scsi_generic/sg2 (scsi_generic) KERNEL[255114.320198] remove /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0/4:0:0:0/scsi_device/4:0:0:0 (scsi_device) KERNEL[255114.320209] remove /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0/4:0:0:0/scsi_disk/4:0:0:0 (scsi_disk) UDEV [255114.320619] remove /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0/4:0:0:0/scsi_generic/sg2 (scsi_generic) UDEV [255114.321338] remove /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0/4:0:0:0/bsg/4:0:0:0 (bsg) UDEV [255114.321948] remove /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0/4:0:0:0/scsi_disk/4:0:0:0 (scsi_disk) UDEV [255114.325400] remove /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0/4:0:0:0/scsi_device/4:0:0:0 (scsi_device) KERNEL[255123.206586] remove /devices/virtual/bdi/8:32 (bdi) KERNEL[255123.206734] remove /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0/4:0:0:0/block/sdc (block) UDEV [255123.207599] remove /devices/virtual/bdi/8:32 (bdi) UDEV [255123.209019] remove /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0/4:0:0:0/block/sdc (block) KERNEL[255123.452120] unbind /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0/4:0:0:0 (scsi) KERNEL[255123.452156] remove /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0/4:0:0:0 (scsi) UDEV [255123.454017] unbind /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0/4:0:0:0 (scsi) UDEV [255123.455196] remove /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0/4:0:0:0 (scsi) KERNEL[255123.484123] remove /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0 (scsi) KERNEL[255123.484149] remove /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/scsi_host/host4 (scsi_host) KERNEL[255123.484174] remove /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4 (scsi) KERNEL[255123.485174] unbind /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0 (usb) KERNEL[255123.485215] remove /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0 (usb) UDEV [255123.485449] remove /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/target4:0:0 (scsi) KERNEL[255123.485698] unbind /devices/pci:00/:00:14.0/usb2/2-2 (usb) KERNEL[255123.485730] remove /devices/pci:00/:00:14.0/usb2/2-2 (usb) UDEV [255123.485994] remove /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4/scsi_host/host4 (scsi_host) UDEV [255123.486906] remove /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host4 (scsi) UDEV [255123.487940] unbind /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0 (usb) UDEV [255123.489062] remove /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0 (usb) UDEV [255123.490615] unbind /devices/pci:00/:00:14.0/usb2/2-2 (usb) UDEV [255123.499129] remove /devices/pci:00/:00:14.0/usb2/2-2 (usb) KERNEL[255126.952713] add /devices/pci:00/:00:14.0/usb2/2-2 (usb) KERNEL[255126.953377] add /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0 (usb) KERNEL[255126.955007] add /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host5 (scsi) KERNEL[255126.955119] add /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host5/scsi_host/host5 (scsi_host) KERNEL[255126.955164] bind /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0 (usb) KERNEL[255126.955209] bind /devices/pci:00/:00:14.0/usb2/2-2 (usb) KERNEL[255126.958067] add /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host5/target5:0:0 (scsi) KERNEL[255126.958155] add /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host5/target5:0:0/5:0:0:0 (scsi) KERNEL[255126.958177] add /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host5/target5:0:0/5:0:0:0/scsi_disk/5:0:0:0 (scsi_disk) KERNEL[255126.958199] bind /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host5/target5:0:0/5:0:0:0 (scsi) KERNEL[255126.958216] add /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host5/target5:0:0/5:0:0:0/scsi_device/5:0:0:0 (scsi_device) KERNEL[255126.958288] add /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host5/target5:0:0/5:0:0:0/scsi_generic/sg2 (scsi_generic) KERNEL[255126.958361] add /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/host5/target5:0:0/5:0:0:0/bsg/5:0:0:0 (bsg) KERNEL[255126.959138] add /devices/virtual/bdi/8:48 (bdi) UDEV [255126.960879] add
[Kernel-packages] [Bug 1888218] 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 1888218 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1888218 Title: kernel warning message on boot with Moonshot nodes Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: Issue found with the new log_check test in the updated ubuntu_boot test with kernel 4.15.0-112.113~16.04.1. ms10-34-mcdivittB0-kernel kernel: [0.00] WARNING: x1-x3 nonzero in violation of boot protocol: ms10-34-mcdivittB0-kernel kernel: [0.00]x1: ms10-34-mcdivittB0-kernel kernel: [0.00]x2: 02faf080 ms10-34-mcdivittB0-kernel kernel: [0.00]x3: 0001 This message can be found in 4.4.0-185-generic as well. Need to check with the Xenial 4.15 kernel in -updates later. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1888218/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888326] [NEW] Bluetooth device not found QCA9565
Public bug reported: Hello, I run Ubuntu 20.04 LTS on my Acer Aspire E5-573G and Ubuntu can't found my bluetooth device. I have a QCNFA335 (QCA9565) which can normally support both wifi and bluetooth I can use both wifi and bluetooth on windows 10. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jul 20 20:24:58 2020 InstallationDate: Installed on 2020-07-17 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterestingModules: bnep btusb bluetooth MachineType: Acer Aspire E5-573G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=eec36b7b-bbf9-463c-80a6-6ec698a4d655 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/16/2016 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.37 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: ZORO_BH dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.37:bd02/16/2016:svnAcer:pnAspireE5-573G:pvrV3.72:rvnAcer:rnZORO_BH:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: BDW dmi.product.name: Aspire E5-573G dmi.product.sku: Aspire E5-573G_098A_1_37 dmi.product.version: V3.72 dmi.sys.vendor: Acer hciconfig: ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1888326 Title: Bluetooth device not found QCA9565 Status in bluez package in Ubuntu: New Bug description: Hello, I run Ubuntu 20.04 LTS on my Acer Aspire E5-573G and Ubuntu can't found my bluetooth device. I have a QCNFA335 (QCA9565) which can normally support both wifi and bluetooth I can use both wifi and bluetooth on windows 10. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jul 20 20:24:58 2020 InstallationDate: Installed on 2020-07-17 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterestingModules: bnep btusb bluetooth MachineType: Acer Aspire E5-573G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=eec36b7b-bbf9-463c-80a6-6ec698a4d655 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/16/2016 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.37 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: ZORO_BH dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.37:bd02/16/2016:svnAcer:pnAspireE5-573G:pvrV3.72:rvnAcer:rnZORO_BH:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: BDW dmi.product.name: Aspire E5-573G dmi.product.sku: Aspire E5-573G_098A_1_37 dmi.product.version: V3.72 dmi.sys.vendor: Acer hciconfig: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1888326/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888331] [NEW] Wakeup the system by touching the touchpad
Public bug reported:
[Impact]
Can't wake up by touching the touchpad.
[Fix]
1.gpio: With 'commit 461c1a7d4733 ("gpiolib: override irq_enable/disable")'
gpiolib overrides irqchip's irq_enable and irq_disable callbacks. If
irq_disable
callback is implemented then genirq takes unlazy path to disable irq.
Underlying irqchip
may not want to implement irq_disable callback to lazy disable irq
when client drivers invokes disable_irq(). By overriding irq_disable
callback,
gpiolib ends up always unlazy disabling IRQ.
Allow gpiolib to lazy disable IRQs by overriding irq_disable callback only
if irqchip implemented irq_disable. In cases where irq_disable is not
implemented irq_mask is overridden. Similarly override irq_enable callback
only if irqchip implemented irq_enable otherwise irq_unmask is overridden.
2. hid: Many laptops can be woken up from Suspend-to-Idle by touchpad. This is
also the default behavior on other OSes.
However, if touchpad and touchscreen contact to each other when lid is
closed, wakeup events can be triggered inadventertly.
So let's disable the wakeup by default, but enable the wakeup capability
so users can enable it at their own discretion.
[test]
With the patch and enable HID's power/wakeup, the system can wake up by
touching the touchpad.
[Regression Potential]
Low. The two patches are already landed in the upstream.
** Affects: linux-oem-5.6 (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux-oem-5.6 (Ubuntu Focal)
Importance: Undecided
Assignee: koba (kobako)
Status: In Progress
** Package changed: linux (Ubuntu) => linux-oem-5.6 (Ubuntu)
** Also affects: linux-oem-5.6 (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux-oem-5.6 (Ubuntu Focal)
Assignee: (unassigned) => koba (kobako)
** Changed in: linux-oem-5.6 (Ubuntu Focal)
Status: New => In Progress
** Summary changed:
- Touchpad cannot wakeup the system Edit
+ Touchpad cannot wakeup the system
** Summary changed:
- Touchpad cannot wakeup the system
+ Wakeup the system by touching the touchpad
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1888331
Title:
Wakeup the system by touching the touchpad
Status in linux-oem-5.6 package in Ubuntu:
New
Status in linux-oem-5.6 source package in Focal:
In Progress
Bug description:
[Impact]
Can't wake up by touching the touchpad.
[Fix]
1.gpio: With 'commit 461c1a7d4733 ("gpiolib: override irq_enable/disable")'
gpiolib overrides irqchip's irq_enable and irq_disable callbacks. If
irq_disable
callback is implemented then genirq takes unlazy path to disable irq.
Underlying irqchip
may not want to implement irq_disable callback to lazy disable irq
when client drivers invokes disable_irq(). By overriding irq_disable
callback,
gpiolib ends up always unlazy disabling IRQ.
Allow gpiolib to lazy disable IRQs by overriding irq_disable callback only
if irqchip implemented irq_disable. In cases where irq_disable is not
implemented irq_mask is overridden. Similarly override irq_enable callback
only if irqchip implemented irq_enable otherwise irq_unmask is overridden.
2. hid: Many laptops can be woken up from Suspend-to-Idle by touchpad. This is
also the default behavior on other OSes.
However, if touchpad and touchscreen contact to each other when lid is
closed, wakeup events can be triggered inadventertly.
So let's disable the wakeup by default, but enable the wakeup capability
so users can enable it at their own discretion.
[test]
With the patch and enable HID's power/wakeup, the system can wake up by
touching the touchpad.
[Regression Potential]
Low. The two patches are already landed in the upstream.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.6/+bug/1888331/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1876517] Re: log in doesn't work
[Expired for nvidia-graphics-drivers-440 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: nvidia-graphics-drivers-440 (Ubuntu) Status: Incomplete => Expired -- 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/1876517 Title: log in doesn't work Status in nvidia-graphics-drivers-440 package in Ubuntu: Expired Bug description: i installed new 20.04 today i installed next step chose 3-r party soft config / 140 gb swap 10 gb /home 300 gb without tmp next i chose autologin , when i finished i can't log in( i return to login form) and when i open terminal ctrl+alt+f3 i can log in without problem. When i installed 1)without 3-r party soft 2)add tmp partition 3)chose without autolog in And now all work well! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat May 2 22:57:59 2020 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity InstallationDate: Installed on 2020-05-02 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: ubiquity Symptom: installation UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1876517/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886172] Re: high speed data to usb disk makes the kernel think that is has been unmounted
Log of udev event, when the bug happens. # udevadm monitor | grep -v power_supply monitor will print the received events for: UDEV - the event which udev sends out after rule processing KERNEL - the kernel uevent KERNEL[259892.454355] remove /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host4/target4:0:0/4:0:0:0/bsg/4:0:0:0 (bsg) KERNEL[259892.454422] remove /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host4/target4:0:0/4:0:0:0/scsi_generic/sg2 (scsi_generic) KERNEL[259892.454441] remove /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host4/target4:0:0/4:0:0:0/scsi_device/4:0:0:0 (scsi_device) KERNEL[259892.454539] remove /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host4/target4:0:0/4:0:0:0/scsi_disk/4:0:0:0 (scsi_disk) UDEV [259892.457118] remove /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host4/target4:0:0/4:0:0:0/bsg/4:0:0:0 (bsg) UDEV [259892.458521] remove /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host4/target4:0:0/4:0:0:0/scsi_generic/sg2 (scsi_generic) UDEV [259892.458829] remove /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host4/target4:0:0/4:0:0:0/scsi_disk/4:0:0:0 (scsi_disk) UDEV [259892.460499] remove /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host4/target4:0:0/4:0:0:0/scsi_device/4:0:0:0 (scsi_device) KERNEL[259900.048051] remove /devices/virtual/bdi/8:32 (bdi) KERNEL[259900.048161] remove /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host4/target4:0:0/4:0:0:0/block/sdc (block) UDEV [259900.049035] remove /devices/virtual/bdi/8:32 (bdi) UDEV [259900.050572] remove /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host4/target4:0:0/4:0:0:0/block/sdc (block) KERNEL[259900.304129] unbind /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host4/target4:0:0/4:0:0:0 (scsi) KERNEL[259900.304164] remove /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host4/target4:0:0/4:0:0:0 (scsi) UDEV [259900.307449] unbind /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host4/target4:0:0/4:0:0:0 (scsi) UDEV [259900.308340] remove /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host4/target4:0:0/4:0:0:0 (scsi) KERNEL[259900.328191] remove /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host4/target4:0:0 (scsi) KERNEL[259900.328218] remove /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host4/scsi_host/host4 (scsi_host) KERNEL[259900.328236] remove /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host4 (scsi) UDEV [259900.329867] remove /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host4/target4:0:0 (scsi) UDEV [259900.330569] remove /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host4/scsi_host/host4 (scsi_host) UDEV [259900.332031] remove /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host4 (scsi) KERNEL[259900.347337] unbind /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0 (usb) UDEV [259900.349761] unbind /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0 (usb) KERNEL[259900.468456] add /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host5 (scsi) KERNEL[259900.468492] add /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host5/scsi_host/host5 (scsi_host) KERNEL[259900.468523] bind /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0 (usb) KERNEL[259900.469340] add /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host5/target5:0:0 (scsi) KERNEL[259900.469396] add /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host5/target5:0:0/5:0:0:0 (scsi) KERNEL[259900.469435] add /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host5/target5:0:0/5:0:0:0/scsi_disk/5:0:0:0 (scsi_disk) KERNEL[259900.469457] bind
[Kernel-packages] [Bug 1886172] Re: high speed data to usb disk makes the kernel think that is has been unmounted
Log of udev event, when the bug happens. # udevadm monitor | grep -v power_supply monitor will print the received events for: UDEV - the event which udev sends out after rule processing KERNEL - the kernel uevent KERNEL[258304.180050] remove /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host5/target5:0:0/5:0:0:0/block/sdd/sdd1 (block) KERNEL[258304.180140] remove /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host5/target5:0:0/5:0:0:0/block/sdd/sdd2 (block) KERNEL[258304.180259] remove /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host5/target5:0:0/5:0:0:0/block/sdd/sdd3 (block) KERNEL[258304.180306] remove /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host5/target5:0:0/5:0:0:0/block/sdd/sdd4 (block) KERNEL[258304.185959] change /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host5/target5:0:0/5:0:0:0/block/sdd (block) UDEV [258304.194320] remove /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host5/target5:0:0/5:0:0:0/block/sdd/sdd1 (block) UDEV [258304.197464] remove /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host5/target5:0:0/5:0:0:0/block/sdd/sdd2 (block) UDEV [258304.201738] remove /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host5/target5:0:0/5:0:0:0/block/sdd/sdd3 (block) UDEV [258304.206277] remove /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host5/target5:0:0/5:0:0:0/block/sdd/sdd4 (block) UDEV [258304.231082] change /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host5/target5:0:0/5:0:0:0/block/sdd (block) KERNEL[258909.512337] remove /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host5/target5:0:0/5:0:0:0/bsg/5:0:0:0 (bsg) KERNEL[258909.512751] remove /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host5/target5:0:0/5:0:0:0/scsi_generic/sg2 (scsi_generic) KERNEL[258909.512770] remove /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host5/target5:0:0/5:0:0:0/scsi_device/5:0:0:0 (scsi_device) KERNEL[258909.512849] remove /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host5/target5:0:0/5:0:0:0/scsi_disk/5:0:0:0 (scsi_disk) UDEV [258909.514595] remove /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host5/target5:0:0/5:0:0:0/bsg/5:0:0:0 (bsg) UDEV [258909.523015] remove /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host5/target5:0:0/5:0:0:0/scsi_generic/sg2 (scsi_generic) UDEV [258909.523043] remove /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host5/target5:0:0/5:0:0:0/scsi_device/5:0:0:0 (scsi_device) UDEV [258909.525664] remove /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host5/target5:0:0/5:0:0:0/scsi_disk/5:0:0:0 (scsi_disk) KERNEL[258916.896444] remove /devices/virtual/bdi/8:48 (bdi) KERNEL[258916.896543] remove /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host5/target5:0:0/5:0:0:0/block/sdd (block) UDEV [258916.898043] remove /devices/virtual/bdi/8:48 (bdi) UDEV [258916.899241] remove /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host5/target5:0:0/5:0:0:0/block/sdd (block) KERNEL[258917.140120] unbind /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host5/target5:0:0/5:0:0:0 (scsi) KERNEL[258917.140157] remove /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host5/target5:0:0/5:0:0:0 (scsi) UDEV [258917.142078] unbind /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host5/target5:0:0/5:0:0:0 (scsi) UDEV [258917.143694] remove /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host5/target5:0:0/5:0:0:0 (scsi) KERNEL[258917.168225] remove /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host5/target5:0:0 (scsi) KERNEL[258917.168252] remove /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host5/scsi_host/host5 (scsi_host) KERNEL[258917.168270] remove /devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.4/2-4.4.4.4/2-4.4.4.4.2/2-4.4.4.4.2:1.0/host5 (scsi)
[Kernel-packages] [Bug 1852001] Re: KDE GUI freeze on high disk IO
** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1852001 Title: KDE GUI freeze on high disk IO Status in linux package in Ubuntu: Invalid Bug description: I've got massive problems with GUI on my PC. The attached logs are from the following setting: - high disk load (f3write) - kernel 4.15.0-1050-oem (the only 4x kernel available in eoan) - no swap available These are the parameters (disk load, kernel, swap) I am fiddling with to find out the cause, see below. In general - the problem happens once a day with any 5.0 or 5.3 kernel from eoan repo - more likely to happen with high disk or CPU load, but not necessarily. - less likely with the 4.x kernel mentioned above. I just installed the following kernels from kernel-ppa: 5.3.10-050310-generic 5.4.0-050400rc6-generic 5.4.0-997-generic (drm-intel-next) Now I am waiting for the freeze to occur again. The problem started about half a year ago. There have been three changes that happened at the time and could be the cause - switch to kernel 5.x - update to Ubuntu 19.4 - swapped motherboard, CPU and RAM. The hassle started with the following scenario, repeated often: - high disk load - PC becomes laggy - soon dies/freezes The longer I waited, the deeper the lockdown went. but I don't know the exact details. The first cause I found was kswapd running amok and take the system with it. Workaround: add swap space. Now the problem shifted: Whenever I got high disk load (eg dd 100 GB of data) the kernel swaps likle crazy and makes the GUI first lag soon freeze. but no excessive CPU load any more, as kswapd does not go crazy. Again I found a workaround: the above mentioned 4.x kernel. In this case the GUI lags as expected from a heavily swapping system. nothing more. but still sometimes the GUI simply freezes (the error reported at the top) Another workaround is to completely remove swap. Let's see what happens, if kswapd goes amok again. I am not sure as how these problems are related. I did extensive hardware check like - memtest86 newest version, no "may be vulnerable to high frequency row hammering" - smart do you suggest any burn in test suites? thanks ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 4.15.0-1050.57-oem 4.15.18 Uname: Linux 4.15.0-1050-oem x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Sun Nov 10 15:55:14 2019 DistUpgraded: 2019-10-19 13:35:30,394 DEBUG entry '# deb http://ppa.launchpad.net/brandonsnider/cdrtools/ubuntu cosmic main # disabled on upgrade to eoan' was disabled (unknown mirror) DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: virtualbox, 6.0.14, 5.3.0-18-generic, x86_64: installed virtualbox, 6.0.14, 5.3.0-19-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 630 (Desktop 9 Series) [8086:3e98] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] UHD Graphics 630 (Desktop 9 Series) [1462:7b16] InstallationDate: Installed on 2017-12-16 (693 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) MachineType: Micro-Star International Co., Ltd. MS-7B16 ProcEnviron: LANGUAGE=en_US:en TERM=linux PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1050-oem root=UUID=ca93bfbd-335a-4cc7-9d0f-f0da18447497 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to eoan on 2019-10-19 (22 days ago) dmi.bios.date: 08/13/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.80 dmi.board.asset.tag: Default string dmi.board.name: B360 GAMING PRO CARBON (MS-7B16) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.80:bd08/13/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B16:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB360GAMINGPROCARBON(MS-7B16):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7B16 dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev:
[Kernel-packages] [Bug 1867559] Re: Qualcomm Atheros QCA9377 wifi 802.11ac very unstable and low speed
** Tags added: hwe-networking-wifi -- 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/1867559 Title: Qualcomm Atheros QCA9377 wifi 802.11ac very unstable and low speed Status in linux package in Ubuntu: Incomplete Status in linux-firmware package in Ubuntu: Confirmed Bug description: rafa@acer:~$ sudo lshw -C network [sudo] senha para rafa: *-network descrição: Ethernet interface produto: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller fabricante: Realtek Semiconductor Co., Ltd. ID físico: 0.1 informações do barramento: pci@:01:00.1 nome lógico: enp1s0f1 versão: 12 serial: 08:97:98:63:7d:2e capacidade: 1Gbit/s largura: 64 bits clock: 33MHz capacidades: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuração: autonegotiation=on broadcast=yes driver=r8169 firmware=rtl8411-2_0.0.1 07/08/13 latency=0 link=no multicast=yes port=MII recursos: irq:16 porta de E/S:3000(tamanho=256) memória:b1204000-b1204fff memória:b120-b1203fff *-network descrição: Interface sem fio produto: QCA9377 802.11ac Wireless Network Adapter fabricante: Qualcomm Atheros ID físico: 0 informações do barramento: pci@:02:00.0 nome lógico: wlp2s0 versão: 31 serial: a4:63:a1:0e:bc:42 largura: 64 bits clock: 33MHz capacidades: pm msi pciexpress bus_master cap_list ethernet physical wireless configuração: broadcast=yes driver=ath10k_pci driverversion=5.3.0-40-generic firmware=WLAN.TF.2.1-00021-QCARMSWP-1 ip=192.168.1.3 latency=0 link=yes multicast=yes wireless=IEEE 802.11 recursos: irq:132 memória:b100-b11f Download speed around 100-600Kb/s on 5GHz connection using WPA/WPA2. Notebook ACER ASPIRE 3 A315-53-343Y To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1867559/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887473] Re: timer_settime02 from ubuntu_ltp_syscalls failed on X/B/E/F s390x
** Tags added: eoan -- 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/1887473 Title: timer_settime02 from ubuntu_ltp_syscalls failed on X/B/E/F s390x Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Status in linux source package in Bionic: Confirmed Status in linux source package in Eoan: Confirmed Status in linux source package in Focal: Confirmed Bug description: Issue found on Xenial 4.4.0-186-generic s390x LPAR / zVM (passed on other arches) And B/E/F s390x as well. <<>> tag=timer_settime02 stime=1594698491 cmdline="timer_settime02" contacts="" analysis=exit <<>> incrementing stop tst_test.c:1247: INFO: Timeout per run is 0h 05m 00s timer_settime02.c:78: INFO: Testing variant: syscall with old kernel spec timer_settime02.c:89: INFO: Testing for setting new_set pointer to NULL: timer_settime02.c:137: PASS: CLOCK_REALTIME failed as expected: EINVAL (22) timer_settime02.c:137: PASS: CLOCK_MONOTONIC failed as expected: EINVAL (22) timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22) timer_settime02.c:137: PASS: CLOCK_PROCESS_CPUTIME_ID failed as expected: EINVAL (22) timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22) timer_settime02.c:137: PASS: CLOCK_THREAD_CPUTIME_ID failed as expected: EINVAL (22) timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22) timer_settime02.c:137: PASS: CLOCK_BOOTTIME failed as expected: EINVAL (22) timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22) timer_settime02.c:106: CONF: CLOCK_BOOTTIME_ALARM unsupported: EOPNOTSUPP (95) timer_settime02.c:106: CONF: CLOCK_REALTIME_ALARM unsupported: EOPNOTSUPP (95) timer_settime02.c:137: PASS: CLOCK_TAI failed as expected: EINVAL (22) timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22) timer_settime02.c:89: INFO: Testing for setting tv_nsec to a negative value: timer_settime02.c:137: PASS: CLOCK_REALTIME failed as expected: EINVAL (22) timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22) timer_settime02.c:137: PASS: CLOCK_MONOTONIC failed as expected: EINVAL (22) timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22) timer_settime02.c:137: PASS: CLOCK_PROCESS_CPUTIME_ID failed as expected: EINVAL (22) timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22) timer_settime02.c:137: PASS: CLOCK_THREAD_CPUTIME_ID failed as expected: EINVAL (22) timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22) timer_settime02.c:137: PASS: CLOCK_BOOTTIME failed as expected: EINVAL (22) timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22) timer_settime02.c:106: CONF: CLOCK_BOOTTIME_ALARM unsupported: EOPNOTSUPP (95) timer_settime02.c:106: CONF: CLOCK_REALTIME_ALARM unsupported: EOPNOTSUPP (95) timer_settime02.c:137: PASS: CLOCK_TAI failed as expected: EINVAL (22) timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22) timer_settime02.c:89: INFO: Testing for setting tv_nsec value too high: timer_settime02.c:137: PASS: CLOCK_REALTIME failed as expected: EINVAL (22) timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22) timer_settime02.c:137: PASS: CLOCK_MONOTONIC failed as expected: EINVAL (22) timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22) timer_settime02.c:137: PASS: CLOCK_PROCESS_CPUTIME_ID failed as expected: EINVAL (22) timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22) timer_settime02.c:137: PASS: CLOCK_THREAD_CPUTIME_ID failed as expected: EINVAL (22) timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22) timer_settime02.c:137: PASS: CLOCK_BOOTTIME failed as expected: EINVAL (22) timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22) timer_settime02.c:106: CONF: CLOCK_BOOTTIME_ALARM unsupported: EOPNOTSUPP (95) timer_settime02.c:106: CONF: CLOCK_REALTIME_ALARM unsupported: EOPNOTSUPP (95) timer_settime02.c:137: PASS: CLOCK_TAI failed as expected: EINVAL (22) timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22) timer_settime02.c:89: INFO: Testing for passing pointer to invalid timer_id: timer_settime02.c:137: PASS: CLOCK_REALTIME failed as expected: EINVAL (22) timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22) timer_settime02.c:137: PASS: CLOCK_MONOTONIC failed as expected: EINVAL (22) timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22) timer_settime02.c:137: PASS: CLOCK_PROCESS_CPUTIME_ID failed as expected: EINVAL (22) timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22) timer_settime02.c:137: PASS: CLOCK_THREAD_CPUTIME_ID failed as expected: EINVAL (22) timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22) timer_settime02.c:137: PASS: CLOCK_BOOTTIME failed as
[Kernel-packages] [Bug 1886022] Re: multiple processes intermittently stall at same point in strace
I decided to try removing ltsp, ltsp-binaries and dsnmasq, just to see
what would happen after.
During the attempt, I got a timeout during update-initramfs. Timeouts
like this during apt are common. I ran "update-initramfs -u" after the
timeout, and that time it seemed to proceed normally. I'll go reboot
the machine when I can and report back.
Aside: This machine also serves a website, and that remains fast even
when the rest of the machine is slow. After ssh to another internal
machine, all is fast again. So it's not a plain network thing.
The timeout:
root@frost:~# apt remove dnsmasq ltsp ltsp-binaries
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following package was automatically installed and is no longer required:
sshfs
Use 'apt autoremove' to remove it.
The following packages will be REMOVED:
dnsmasq ltsp ltsp-binaries
0 upgraded, 0 newly installed, 3 to remove and 0 not upgraded.
After this operation, 1,669 kB disk space will be freed.
Do you want to continue? [Y/n]
(Reading database ... 296064 files and directories currently installed.)
Removing dnsmasq (2.80-1.1ubuntu1) ...
Removing ltsp (20.06-1~ubuntu20.04.1) ...
Removing ltsp-binaries (20.04-1~ubuntu20.04.1) ...
Processing triggers for man-db (2.9.1-1) ...
Processing triggers for initramfs-tools (0.136ubuntu6.2) ...
update-initramfs: Generating /boot/initrd.img-5.4.0-40-generic
Error: Timeout was reached
--
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/1886022
Title:
multiple processes intermittently stall at same point in strace
Status in linux package in Ubuntu:
Incomplete
Bug description:
If this isn't a kernel bug, my apologies. I didn't know where else to
put it. It affects seemingly unrelated processes, so there wasn't an
obvious 'package'. Possibly nscd, which is in glibc, which is close
to the kernel...
I noticed frequent, but intermittent hangs/stalls in multiple
processes. The processes usually go on to completion after a few
seconds or so. Occasionally, I get timeouts that I think might be
this same symptom but aren't always strace-able.
At first, I thought it was an authentication issue because I got hangs
with "sudo -i" as well as intermittently very slow logins via ssh with
ldap. But, then it happened with "vim dum", which could still be
authentication somehow, but I don't know enough to determine that.
Htop will also hang intermittently, but I don't have a trace of it.
I started running strace on the processes that are hanging. The hang
happened after the same few lines each time that I was able to strace
at the same time of a hang (it is intermittent).
Here is an example of the last lines before hang where a normal user
issues "strace id username":
socket(AF_UNIX, SOCK_STREAM|SOCK_CLOEXEC|SOCK_NONBLOCK, 0) = 3
connect(3, {sa_family=AF_UNIX, sun_path="/var/run/nscd/socket"}, 110) = 0
sendto(3, "\2\0\0\0\v\0\0\0\7\0\0\0passwd\0", 19, MSG_NOSIGNAL, NULL, 0) = 19
poll([{fd=3, events=POLLIN|POLLERR|POLLHUP}], 1, 5000^Cstrace: Process 2816
detached
I hit ctrl-C to stop execution so I could easily copy that info, hence
detached.
Here is an example from root using "strace vim dum":
socket(AF_UNIX, SOCK_STREAM|SOCK_CLOEXEC|SOCK_NONBLOCK, 0) = 3
connect(3,
{sa_family=AF_UNIX, sun_path="/var/run/nscd/socket"}, 110) = 0
sendto(3, "\2\0\0\0\v\0\0\0\7\0\0\0passwd\0",
19, MSG_NOSIGNAL, NULL, 0) = 19
poll([{fd=3, events=POLLIN|POLLERR|POLLHUP}], 1, 5000
...that took practice to capture.
I suspect that LDAP is involved somehow, but it might be victim rather
than culprit. Obviously, nscd has some involvement per the lines
above. Or possibly, these lines are about strace itself?
I can capture full straces with timings, etc. Just say what you need.
Or direct me to the proper venue for this report.
I looked in kern.log for evidence of a hardware issue, but didn't see
anything that looked significantly unusual. If it seems like
hardware, I will appreciate hints as to the component.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-40-generic 5.4.0-40.44
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: installer 1846 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: LXDE
Date: Thu Jul 2 04:36:12 2020
InstallationDate: Installed on 2020-06-25 (7 days ago)
InstallationMedia: Ubuntu-MATE 20.04 LTS
[Kernel-packages] [Bug 1888218] Re: kernel warning message on boot with Moonshot nodes
** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1888218 Title: kernel warning message on boot with Moonshot nodes Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: Issue found with the new log_check test in the updated ubuntu_boot test with kernel 4.15.0-112.113~16.04.1. ms10-34-mcdivittB0-kernel kernel: [0.00] WARNING: x1-x3 nonzero in violation of boot protocol: ms10-34-mcdivittB0-kernel kernel: [0.00]x1: ms10-34-mcdivittB0-kernel kernel: [0.00]x2: 02faf080 ms10-34-mcdivittB0-kernel kernel: [0.00]x3: 0001 This message can be found in 4.4.0-185-generic as well. Need to check with the Xenial 4.15 kernel in -updates later. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1888218/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887595] Re: linux-firmware: integrate TGL_SOF_FW_prod_signed_v0.6.2_release for tigerlake machines
** Tags added: verification-done -- 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/1887595 Title: linux-firmware: integrate TGL_SOF_FW_prod_signed_v0.6.2_release for tigerlake machines Status in HWE Next: New Status in OEM Priority Project: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: Fix Committed Status in linux-firmware source package in Groovy: Fix Released Bug description: [Impact] There is no sof-firmware for tgl platforms in the focal and groovy, so the audio driver can't work on the tgl machines. [Fix] Intel released a firmware for tgl platforms, it is signed by production key. [Test Case] Install the TGL_SOF_FW_prod_signed_v0.6.2_release to /lib/firmware/intel/sof, boot the dell tgl machines, the sof driver loads the sof-firmware successfully, and the audio driver works well too. [Regression Risk] Low, this SRU adds new firmware, this firmware is only used by intel tgl machines, and Intel told us this firmware is signed by production key and is ok to release to ubuntu archive. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1887595/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887249] Re: OpenCL doesn't work when kernel lockdown enabled
It turns out the MOK key installed previously was removed during a BIOS update. Upon the next kernel update from Ubuntu I was prompted to install the MOK key, after which OpenCL works even when kernel lockdown is enabled. ** Changed in: nvidia-graphics-drivers-440 (Ubuntu) Status: New => Invalid -- 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/1887249 Title: OpenCL doesn't work when kernel lockdown enabled Status in nvidia-graphics-drivers-440 package in Ubuntu: Invalid Bug description: When booting with secure boot and kernel lockdown is enabled, OpenCL is unable to use my GPU (GeForce RTX 2080 SUPER). Running "clinfo" shows "Number of platforms 0". If I disable secure boot in my UEFI settings, clinfo shows the details of my GPU as expected. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libnvidia-compute-440 440.100-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jul 11 12:08:09 2020 InstallationDate: Installed on 2020-04-29 (72 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-graphics-drivers-440 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1887249/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886247] Re: Realtek [10ec:c82f] Subsystem [17aa:c02f] Wifi adapter not found
For 20.04 focal 5.4 kernel. it should be in this SRU cycle released on 10 Aug. -- 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/1886247 Title: Realtek [10ec:c82f] Subsystem [17aa:c02f] Wifi adapter not found Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.6 package in Ubuntu: Confirmed Status in linux source package in Focal: Confirmed Status in linux-oem-5.6 source package in Focal: Fix Committed Bug description: SRU justification: [Impact] New realtek wifi card ID found on ThinkCentre. No driver is loaded to support it. [Fix] This wifi card is very similar as 0xc822 in rtw88. [Test] Verified on hardware, link status is OK, iperf test result is good. [Regression Potential] Low. Add new ID to supported driver. Test on hw, double confirmed by LP bugs. This patch is backported from original link due to the 5.8-rc1 driver file path changed, no function changed. Maintainer had merged: https://github.com/lwfinger/rtlwifi_new/commit/b76b895a90f1168c5223849562fd6e1196b2c351 This git repo is moving by maintainer, not availible by now. = 01:00.0 Network controller: Realtek Semiconductor Co., Ltd. Device c82f Looking for a working solution on a fresh install (USB BOOT) of Ubuntu. A work-around helped, for a while, but I would really like to disconnect my Wifi Dongel and use my brand new laptop! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: christian 1277 F pulseaudio /dev/snd/pcmC0D0c: christian 1277 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jul 4 07:58:06 2020 InstallationDate: Installed on 2020-06-28 (5 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81W8 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=f610713f-73ad-468c-8a69-9a47b385acab ro quiet splash i8042.nopnp=1 pci=nocrs vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux StagingDrivers: r8712u UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/04/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DKCN26WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32866 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad S145-15IIL dmi.modalias: dmi:bvnLENOVO:bvrDKCN26WW:bd03/04/2020:svnLENOVO:pn81W8:pvrLenovoIdeaPadS145-15IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0R32866WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS145-15IIL: dmi.product.family: IdeaPad S145-15IIL dmi.product.name: 81W8 dmi.product.sku: LENOVO_MT_81W8_BU_idea_FM_IdeaPad S145-15IIL dmi.product.version: Lenovo IdeaPad S145-15IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886247/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1879334] Re: Desktop Activities - first key typed is repeated 21 times
Nice! You don’t do anything on this and then expire it. Good job! So much for stating that you want people to report bugs. What a waste of time! -- 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/1879334 Title: Desktop Activities - first key typed is repeated 21 times Status in linux package in Ubuntu: Expired Bug description: Pretty simple scenario. I often press the Super key and then start typing a command name. Within the last two weeks (I stay up to date on any updates to 18.04), when I press the first key it gets repeated a total of 21 times. It is only the first key. If I press backspace or Ctl-u to erase the entries, then there is no problem. It seems that this problem went from being intermittent to being constant now. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879334/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887459] Re: clock_gettime04 from ubuntu_ltp_syscalls failed on X/B/E/F s390x
** Tags added: eoan -- 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/1887459 Title: clock_gettime04 from ubuntu_ltp_syscalls failed on X/B/E/F s390x Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Status in linux source package in Bionic: Confirmed Status in linux source package in Eoan: Confirmed Status in linux source package in Focal: Confirmed Bug description: Issue found on Xenial 4.4.0-186-generic s390x LPAR / zVM (passed on other arches) And B/E/F s390x as well. This is a new test case added between this and the last cycle. <<>> tag=clock_gettime04 stime=1594692118 cmdline="clock_gettime04" contacts="" analysis=exit <<>> tst_test.c:1247: INFO: Timeout per run is 0h 05m 00s tst_test.c:1292: BROK: Test killed by SIGFPE! Summary: passed 0 failed 0 skipped 0 warnings 0 <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=2 corefile=no cutime=0 cstime=0 <<>> Error message can be found in syslog: report_user_fault: 159 callbacks suppressed User process fault: interruption code 0009 ilc:2 in clock_gettime04[113b0+22000] CPU: 0 PID: 4222 Comm: clock_gettime04 Tainted: P O 4.4.0-186-generic #216-Ubuntu task: 0007aa6de348 ti: 0007ada34000 task.ti: 0007ada34000 User PSW : 070510018000 000113b18878 R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:1 AS:0 CC:1 PM:0 EA:3 User GPRS: 0b0cd725 000113b1d026 000113b1d00e 0b0cd725 000113b19bc4 03ffe687e770 000113b28f38 03ff941fe128 000113b28ec8 075fcbb9 03ff941a5000 000113b1d098 000113b1843e 03ffe687e1f8 User Code: 000113b1886a: e300a0380016 llgf%r0,56(%r10) 000113b18870: a749 lghi%r4,0 #000113b18874: b9870040 dlgr%r4,%r0 >000113b18878: c0508328 larl%r5,113b28ec8 000113b1887e: eb140002000d sllg%r1,%r4,2 000113b18884: e3119012 lt %r1,0(%r1,%r9) 000113b1888a: a784009a brc 8,113b189be 000113b1888e: e3405044 lg %r4,64(%r5) Last Breaking-Event-Address: [<000113b18860>] 0x113b18860 Kernel tainted flag is 4097 after a clean boot, it won't be changed after the test: $ cat /proc/sys/kernel/tainted 4097 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-186-generic 4.4.0-186.216 ProcVersionSignature: Ubuntu 4.4.0-186.216-generic 4.4.228 Uname: Linux 4.4.0-186-generic s390x NonfreeKernelModules: zfs zunicode zcommon znvpair zavl AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.23 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Mon Jul 13 22:02:08 2020 HibernationDevice: RESUME=UUID=f578fa27-1d57-41c9-bb1d-7ff64c1c9345 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=UUID=f26894a2-496d-4891-aa9a-f66344c9 crashkernel=196M BOOT_IMAGE=0 RelatedPackageVersions: linux-restricted-modules-4.4.0-186-generic N/A linux-backports-modules-4.4.0-186-generic N/A linux-firmware 1.157.23 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1887459/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887469] Re: timer_settime01 from ubuntu_ltp_syscalls failed on X/B/E/F s390x
** Tags added: eoan -- 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/1887469 Title: timer_settime01 from ubuntu_ltp_syscalls failed on X/B/E/F s390x Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Status in linux source package in Bionic: Confirmed Status in linux source package in Eoan: Confirmed Status in linux source package in Focal: Confirmed Bug description: Issue found on Xenial 4.4.0-186-generic s390x LPAR / zVM (passed on other arches) And B/E/F s390x as well. <<>> tag=timer_settime01 stime=1594697076 cmdline="timer_settime01" contacts="" analysis=exit <<>> incrementing stop tst_test.c:1247: INFO: Timeout per run is 0h 05m 00s timer_settime01.c:142: INFO: Testing variant: syscall with old kernel spec timer_settime01.c:70: INFO: Testing for general initialization: timer_settime01.c:125: PASS: CLOCK_REALTIME was successful timer_settime01.c:122: FAIL: CLOCK_MONOTONIC failed: EINVAL (22) timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22) timer_settime01.c:122: FAIL: CLOCK_PROCESS_CPUTIME_ID failed: EINVAL (22) timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22) timer_settime01.c:122: FAIL: CLOCK_THREAD_CPUTIME_ID failed: EINVAL (22) timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22) timer_settime01.c:122: FAIL: CLOCK_BOOTTIME failed: EINVAL (22) timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22) timer_settime01.c:86: CONF: CLOCK_BOOTTIME_ALARM unsupported: EOPNOTSUPP (95) timer_settime01.c:86: CONF: CLOCK_REALTIME_ALARM unsupported: EOPNOTSUPP (95) timer_settime01.c:122: FAIL: CLOCK_TAI failed: EINVAL (22) timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22) timer_settime01.c:70: INFO: Testing for setting old_value: timer_settime01.c:122: FAIL: CLOCK_REALTIME failed: EINVAL (22) timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22) timer_settime01.c:122: FAIL: CLOCK_MONOTONIC failed: EINVAL (22) timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22) timer_settime01.c:122: FAIL: CLOCK_PROCESS_CPUTIME_ID failed: EINVAL (22) timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22) timer_settime01.c:122: FAIL: CLOCK_THREAD_CPUTIME_ID failed: EINVAL (22) timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22) timer_settime01.c:122: FAIL: CLOCK_BOOTTIME failed: EINVAL (22) timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22) timer_settime01.c:86: CONF: CLOCK_BOOTTIME_ALARM unsupported: EOPNOTSUPP (95) timer_settime01.c:86: CONF: CLOCK_REALTIME_ALARM unsupported: EOPNOTSUPP (95) timer_settime01.c:122: FAIL: CLOCK_TAI failed: EINVAL (22) timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22) timer_settime01.c:70: INFO: Testing for using periodic timer: timer_settime01.c:122: FAIL: CLOCK_REALTIME failed: EINVAL (22) timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22) timer_settime01.c:122: FAIL: CLOCK_MONOTONIC failed: EINVAL (22) timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22) timer_settime01.c:122: FAIL: CLOCK_PROCESS_CPUTIME_ID failed: EINVAL (22) timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22) timer_settime01.c:122: FAIL: CLOCK_THREAD_CPUTIME_ID failed: EINVAL (22) timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22) timer_settime01.c:122: FAIL: CLOCK_BOOTTIME failed: EINVAL (22) timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22) timer_settime01.c:86: CONF: CLOCK_BOOTTIME_ALARM unsupported: EOPNOTSUPP (95) timer_settime01.c:86: CONF: CLOCK_REALTIME_ALARM unsupported: EOPNOTSUPP (95) timer_settime01.c:122: FAIL: CLOCK_TAI failed: EINVAL (22) timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22) timer_settime01.c:70: INFO: Testing for using absolute time: timer_settime01.c:122: FAIL: CLOCK_REALTIME failed: EINVAL (22) timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22) timer_settime01.c:122: FAIL: CLOCK_MONOTONIC failed: EINVAL (22) timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22) timer_settime01.c:122: FAIL: CLOCK_PROCESS_CPUTIME_ID failed: EINVAL (22) timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22) timer_settime01.c:122: FAIL: CLOCK_THREAD_CPUTIME_ID failed: EINVAL (22) timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22) timer_settime01.c:122: FAIL: CLOCK_BOOTTIME failed: EINVAL (22) timer_settime01.c:130: FAIL: timer_delete() failed!: EINVAL (22) timer_settime01.c:86: CONF: CLOCK_BOOTTIME_ALARM unsupported: EOPNOTSUPP (95) timer_settime01.c:86: CONF: CLOCK_REALTIME_ALARM unsupported: EOPNOTSUPP (95) timer_settime01.c:122: FAIL: CLOCK_TAI failed: EINVAL (22) timer_settime01.c:130: FAIL:
[Kernel-packages] [Bug 1888229] Re: Touchpad doesn't work
** Tags added: hwe-touchpad -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1888229 Title: Touchpad doesn't work Status in linux package in Ubuntu: Confirmed Bug description: I'm using a computer Lenovo IdeaPad s145 and I've installed Ubuntu 20.04 LTS and my touchpad doesn't work at all. xinput gives: ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Logitech Optical USB Mouse id=12 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=9[slave keyboard (3)] ↳ Ideapad extra buttons id=10 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=11 [slave keyboard (3)] Moreover, if I execute cat /proc/bus/input/devices it gives me only the mouse device and not the touchpad. What can I do? Thank you for your help ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: s 1002 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jul 20 15:46:40 2020 InstallationDate: Installed on 2020-07-16 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse Bus 001 Device 002: ID 13d3:5a08 IMC Networks Integrated Camera Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81W8 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=ee02290d-f214-4067-8ce8-c44b9e0ca2a0 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/26/2019 dmi.bios.vendor: LENOVO dmi.bios.version: DKCN24WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad S145-15IIL dmi.modalias: dmi:bvnLENOVO:bvrDKCN24WW:bd11/26/2019:svnLENOVO:pn81W8:pvrLenovoIdeaPadS145-15IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS145-15IIL: dmi.product.family: IdeaPad S145-15IIL dmi.product.name: 81W8 dmi.product.sku: LENOVO_MT_81W8_BU_idea_FM_IdeaPad S145-15IIL dmi.product.version: Lenovo IdeaPad S145-15IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888229/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888326] Re: Bluetooth device not found QCA9565
*** This bug is a duplicate of bug 1475639 *** https://bugs.launchpad.net/bugs/1475639 It appears bug 1475639 already exists for this issue. ** Package changed: bluez (Ubuntu) => linux (Ubuntu) ** Also affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** This bug has been marked a duplicate of bug 1475639 Atheros QCA9565 bluetooth hardware not detected -- 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/1888326 Title: Bluetooth device not found QCA9565 Status in linux package in Ubuntu: New Status in linux-firmware package in Ubuntu: New Bug description: Hello, I run Ubuntu 20.04 LTS on my Acer Aspire E5-573G and Ubuntu can't found my bluetooth device. I have a QCNFA335 (QCA9565) which can normally support both wifi and bluetooth I can use both wifi and bluetooth on windows 10. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jul 20 20:24:58 2020 InstallationDate: Installed on 2020-07-17 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterestingModules: bnep btusb bluetooth MachineType: Acer Aspire E5-573G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=eec36b7b-bbf9-463c-80a6-6ec698a4d655 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/16/2016 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.37 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: ZORO_BH dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.37:bd02/16/2016:svnAcer:pnAspireE5-573G:pvrV3.72:rvnAcer:rnZORO_BH:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: BDW dmi.product.name: Aspire E5-573G dmi.product.sku: Aspire E5-573G_098A_1_37 dmi.product.version: V3.72 dmi.sys.vendor: Acer hciconfig: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888326/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878007] Re: Ubuntu 20.04 freeze on Dell inspiron 7373 when screen is turned off
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878007 Title: Ubuntu 20.04 freeze on Dell inspiron 7373 when screen is turned off Status in linux package in Ubuntu: Expired Bug description: This issue is happening with Ubuntu 18.04 and 20.04 in a Dell Inspiron 7373. When the screen is turned off (so, the suspend or screen lock features are affected), the system freeze and I need to force the laptop turn off and on again. There are some cases when it turn off the screen without issues, but most of the time it freezes. Even "SysRq REISUB" does not work for rebooting when system crash. I can reproduce the issue using `xset dpms force off`. Initially this bug report was filled thinking it was a suspend issue: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832144 Syslog or systemd journal does not provide any error information about the crash. "lsb_release -rd" output: Description: Ubuntu 20.04 LTS Release: 20.04 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: cccaballero 2023 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-06-09 (344 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 0bda:58f5 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 7373 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=d8203f53-c2e5-4934-8616-0a71507c9190 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-29-generic N/A linux-backports-modules-5.4.0-29-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-29-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-02 (16 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/06/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0JW0D6 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd09/06/2019:svnDellInc.:pnInspiron7373:pvr:rvnDellInc.:rn0JW0D6:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7373 dmi.product.sku: 07EB dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878007/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888324] [NEW] Kernel oops in kvm host if using vhost_net in guest (18.04 HWE)
You have been subscribed to a public bug: If I run a KVM guest with a network using the vhost_net driver, I get a kernel oops with a NULL reference error. It happens randomly. I run a GPU passthrough setup with windows 10 but I can leave that up 24/7 as I am passing through a raw ethernet card. Any other virtual machine using the vhost_net driver will result in a crash in 12 hours or less. I've attached the dmesg that I captured with kdump. I am not sure when this bug was introduced. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bionic kernel-bug -- Kernel oops in kvm host if using vhost_net in guest (18.04 HWE) https://bugs.launchpad.net/bugs/1888324 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886172] Re: high speed data to usb disk makes the kernel think that is has been unmounted
This bug is present in all kernels tested from 4.15. Tested kernels are
at the end of this comment. The bug appears to depend heavily on the
speed of data. For example it works erasing a disk with all kernels with
dd if=/dev/urandom, but not with faster if=/dev/zero or if="openssl"
(exact syntax in attached test-script).
Linux 5.4.0-37-generic #41-Ubuntu SMP Wed Jun 3 18:57:02 UTC 2020 x86_64 x86_64
x86_64 GNU/Linux
Linux 5.0.1-050001-generic #201903100732 SMP Sun Mar 10 07:33:53 UTC 2019
x86_64 x86_64 x86_64 GNU/Linux
Linux 4.17.0-041700-generic #201806041953 SMP Mon Jun 4 19:55:25 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
Linux 4.16.18-041618-generic #201806252030 SMP Tue Jun 26 00:33:13 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
Linux 4.16.1-041601-generic #201804081334 SMP Sun Apr 8 13:35:48 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
Linux 4.15.18-041518-generic #201804190330 SMP Thu Apr 19 07:34:21 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
Linux 4.15.0-91-generic #92-Ubuntu SMP Fri Feb 28 11:09:48 UTC 2020 x86_64
x86_64 x86_64 GNU/Linux
** Attachment added: "test script"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886172/+attachment/5394463/+files/test.sh
--
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/1886172
Title:
high speed data to usb disk makes the kernel think that is has been
unmounted
Status in linux package in Ubuntu:
Confirmed
Bug description:
Description:
When the speed of data with a usb disk device is too high, the probes
that check if the disk still exists is missed. This makes the disk to
be unmounted and is remounted with an other drive letter (/dev/sdX).
If this disk is the root ("/"), the computer hangs.
A usb SSD-disk (4 TB) connected to a USB port reproduce this bug
easily. This has never happened with a mechanical USB-drive.
Symptoms and how to reproduce:
1) (Disk mounted as root) Computer hangs. Only way to get started
again is a hard reset.
2) (Erasing disk, not mounted as root) If you erase a disk with dd
("dd if=/dev/zero of=/dev/sdX"), the disk disappears from the mounted
list and reappears as an other drive letter. In my case the data is
redirected to /dev/null and the fans speed up. The apparent data
transfer speed is also increased. Usually this happens after about 45
to 60 minutes.
3) Fill RAM with programs and make sure the swap to this disk is used.
Bug found in:
$ uname -a
Linux pb-189b1884 5.4.0-40-generic #44-Ubuntu SMP Tue Jun 23 00:01:04 UTC
2020 x86_64 x86_64 x86_64 GNU/Linux
$ cat /proc/version_signature
Ubuntu 5.4.0-40.44-generic 5.4.44
Hardware:
Tested with slower and faster computers. Tested directly connected to
a computer and via a hub. They all reproduce this bug.
Workaround:
None found.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: user 6813 F pulseaudio
/dev/snd/controlC0: user 6813 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: MATE
DistroRelease: Ubuntu 20.04
MachineType: ASUSTeK COMPUTER INC. GL503VM
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux (not installed)
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic
root=UUID=74545cc2-bc7e-11ea-9c1b-6b408850adf5 ro fsck.repair=yes
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
RelatedPackageVersions:
linux-restricted-modules-5.4.0-40-generic N/A
linux-backports-modules-5.4.0-40-generic N/A
linux-firmware1.187.1
Tags: focal
Uname: Linux 5.4.0-40-generic x86_64
UnreportableReason: This report is about a package that is not installed.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: sudo vboxusers wireshark
WifiSyslog:
_MarkForUpload: False
dmi.bios.date: 04/29/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: GL503VM.314
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: GL503VM
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.:bvrGL503VM.314:bd04/29/2019:svnASUSTeKCOMPUTERINC.:pnGL503VM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL503VM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: ROG
dmi.product.name: GL503VM
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886172/+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 1887724] Re: [amdgpu] Xorg freeze
It might help to disable the built-in wifi. Try doing it in the BIOS. If that doesn't work then you can disable the kernel driver of the built-in wifi by adding a line: blacklist ath10k_pci to /etc/modprobe.d/blacklist.conf and then reboot. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1887724 Title: [amdgpu] Xorg freeze Status in linux package in Ubuntu: Incomplete Bug description: Random freezing-- different freezing every time. I switched GUIs from Gnome to Cinnamon and it seems to freeze less, but still averaging about once a day. I cannot reproduce, is random. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: X-Cinnamon Date: Wed Jul 15 15:44:47 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev c4) (prog-if 00 [VGA controller]) Subsystem: Dell Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1028:0884] InstallationDate: Installed on 2020-06-04 (40 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Inspiron 7375 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=0ed970bf-fd17-4242-8a3e-5c1224ed5b72 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/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 02YPPF dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.5.0 dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd07/09/2018:svnDellInc.:pnInspiron7375:pvr1.5.0:rvnDellInc.:rn02YPPF:rvrA00:cvnDellInc.:ct10:cvr1.5.0: dmi.product.family: Inspiron dmi.product.name: Inspiron 7375 dmi.product.sku: 0884 dmi.product.version: 1.5.0 dmi.sys.vendor: Dell 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.1 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/1887724/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1879299] Re: enable disable fan test in ubuntu_fan_smoke_test failed on E/F s390x LPAR / zVM ( docker still configured, unable to disable fan)
** Tags added: 5.3 sru-20200629 -- 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/1879299 Title: enable disable fan test in ubuntu_fan_smoke_test failed on E/F s390x LPAR / zVM ( docker still configured, unable to disable fan) Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: Issue found on E/F s390x LPAR / zVM (they are manually provisioned systems) Test failed with: docker still configured, unable to disable fan * Command: ./ubuntu_fan_smoke_test.sh 10.245.0.0/16 Exit status: 1 Duration: 12.935628891 stdout: Running in the Canonical CI environment Testing Fan Networking (pre-0.13.0 API) docker pull s390x/ubuntu: PASSED enable disable fan test: FAILED (fanctl returned 1) stderr: /usr/sbin/fanatic: docker still configured, unable to disable fan docker container ls shows there is no docker running $ sudo docker container ls -a CONTAINER IDIMAGE COMMAND CREATED STATUS PORTS NAMES $ ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-31-generic 5.4.0-31.35 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic s390x NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CasperMD5CheckResult: skip CurrentDmesg: Date: Mon May 18 11:08:11 2020 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lspci-vt: -[:00]- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: /sys/bus/usb/devices: No such file or directory Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: PciMultimedia: ProcFB: ProcKernelCmdLine: root=/dev/mapper/kl04vg01-kl04root crashkernel=196M BOOT_IMAGE= RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-03-03 (76 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1879299/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1475639] Re: Atheros QCA9565 bluetooth hardware not detected
** Tags added: focal -- 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/1475639 Title: Atheros QCA9565 bluetooth hardware not detected Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Confirmed Status in linux-lts-utopic package in Ubuntu: Fix Released Bug description: 1. the result of `lspci -nnk | grep -iA2 net; lsusb` is : 07:00.0 Network controller [0280]: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter [168c:0036] (rev 01) Subsystem: XAVi Technologies Corp. Device [1b9a:28a2] Kernel driver in use: ath9k 08:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 0c) Subsystem: Toshiba America Info Systems Device [1179:f920] Kernel driver in use: r8169 Bus 001 Device 002: ID 8087:8000 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 003: ID 04f2:b446 Chicony Electronics Co., Ltd Bus 002 Device 002: ID 0930:0227 Toshiba Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub 2. the result of usb-devices | awk '/0227/' RS= is : T: Bus=02 Lev=01 Prnt=01 Port=04 Cnt=01 Dev#= 2 Spd=12 MxCh= 0 D: Ver= 1.10 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=0930 ProdID=0227 Rev=00.01 C: #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=100mA I: If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=(none) I: If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=(none) mike@mikes:~$ usb-devices | awk '/0227/' RS awk: fatal: cannot open file `RS' for reading (No such file or directory) 3. I am using Ubuntu 14.04.2 4. package manager version is 13.10 5. Expected to see a bluetooth adapter 6. says "No adapted found" ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.16.0-44-generic 3.16.0-44.59~14.04.1 ProcVersionSignature: Ubuntu 3.16.0-44.59~14.04.1-generic 3.16.7-ckt14 Uname: Linux 3.16.0-44-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jul 17 15:28:44 2015 InstallationDate: Installed on 2015-04-22 (86 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: linux-lts-utopic UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1475639/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1879334] Re: Desktop Activities - first key typed is repeated 21 times
Does any key other than "A" has 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/1879334 Title: Desktop Activities - first key typed is repeated 21 times Status in linux package in Ubuntu: Expired Bug description: Pretty simple scenario. I often press the Super key and then start typing a command name. Within the last two weeks (I stay up to date on any updates to 18.04), when I press the first key it gets repeated a total of 21 times. It is only the first key. If I press backspace or Ctl-u to erase the entries, then there is no problem. It seems that this problem went from being intermittent to being constant now. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879334/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886172] Re: high speed data to usb disk makes the kernel think that is has been unmounted
Does kernel parameter "usb-storage.quirks=090c:1000:u" help?
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1886172
Title:
high speed data to usb disk makes the kernel think that is has been
unmounted
Status in linux package in Ubuntu:
Incomplete
Bug description:
Description:
When the speed of data with a usb disk device is too high, the probes
that check if the disk still exists is missed. This makes the disk to
be unmounted and is remounted with an other drive letter (/dev/sdX).
If this disk is the root ("/"), the computer hangs.
A usb SSD-disk (4 TB) connected to a USB port reproduce this bug
easily. This has never happened with a mechanical USB-drive.
Symptoms and how to reproduce:
1) (Disk mounted as root) Computer hangs. Only way to get started
again is a hard reset.
2) (Erasing disk, not mounted as root) If you erase a disk with dd
("dd if=/dev/zero of=/dev/sdX"), the disk disappears from the mounted
list and reappears as an other drive letter. In my case the data is
redirected to /dev/null and the fans speed up. The apparent data
transfer speed is also increased. Usually this happens after about 45
to 60 minutes.
3) Fill RAM with programs and make sure the swap to this disk is used.
Bug found in:
$ uname -a
Linux pb-189b1884 5.4.0-40-generic #44-Ubuntu SMP Tue Jun 23 00:01:04 UTC
2020 x86_64 x86_64 x86_64 GNU/Linux
$ cat /proc/version_signature
Ubuntu 5.4.0-40.44-generic 5.4.44
Hardware:
Tested with slower and faster computers. Tested directly connected to
a computer and via a hub. They all reproduce this bug.
Workaround:
None found.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: user 6813 F pulseaudio
/dev/snd/controlC0: user 6813 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: MATE
DistroRelease: Ubuntu 20.04
MachineType: ASUSTeK COMPUTER INC. GL503VM
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux (not installed)
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic
root=UUID=74545cc2-bc7e-11ea-9c1b-6b408850adf5 ro fsck.repair=yes
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
RelatedPackageVersions:
linux-restricted-modules-5.4.0-40-generic N/A
linux-backports-modules-5.4.0-40-generic N/A
linux-firmware1.187.1
Tags: focal
Uname: Linux 5.4.0-40-generic x86_64
UnreportableReason: This report is about a package that is not installed.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: sudo vboxusers wireshark
WifiSyslog:
_MarkForUpload: False
dmi.bios.date: 04/29/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: GL503VM.314
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: GL503VM
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.:bvrGL503VM.314:bd04/29/2019:svnASUSTeKCOMPUTERINC.:pnGL503VM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL503VM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: ROG
dmi.product.name: GL503VM
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886172/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888324] Re: Kernel oops in kvm host if using vhost_net in guest (18.04 HWE)
** Package changed: linux-hwe (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1888324 Title: Kernel oops in kvm host if using vhost_net in guest (18.04 HWE) Status in linux package in Ubuntu: New Bug description: If I run a KVM guest with a network using the vhost_net driver, I get a kernel oops with a NULL reference error. It happens randomly. I run a GPU passthrough setup with windows 10 but I can leave that up 24/7 as I am passing through a raw ethernet card. Any other virtual machine using the vhost_net driver will result in a crash in 12 hours or less. I've attached the dmesg that I captured with kdump. I am not sure when this bug was introduced. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888324/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888193] 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/1888193 Title: [amdgpu] Xorg freeze Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: New Bug description: I have Radeon Pro WX 7100. It hangs twice a day. I narrow-downed this issue to the fan speed lock. After reboot, it always runs on 18%, no matter of the load. If I install Radeon Profile and force fan to 100% and then turn auto fan configuration, then fan reacts on the load. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-62-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jul 20 09:15:03 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Very infrequently GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon Pro WX 7100] [1002:67c4] (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon Pro WX 7100] [1002:0b0d] InstallationDate: Installed on 2020-06-29 (20 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic root=UUID=2b68d049-e85f-47ab-97d9-5632f225b71b ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/17/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 7803 dmi.board.asset.tag: Default string dmi.board.name: ROG CROSSHAIR VI HERO (WI-FI AC) 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.:bvr7803:bd06/17/2020:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGCROSSHAIRVIHERO(WI-FIAC):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 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/ubuntu/+source/linux/+bug/1888193/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826848] Re: ip_defrag.sh in net from ubuntu_kernel_selftests failed with 5.0 / 5.3 / 5.4 kernel
The test has passed with 5.4.0-42.46 on all different arches. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1826848 Title: ip_defrag.sh in net from ubuntu_kernel_selftests failed with 5.0 / 5.3 / 5.4 kernel Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Disco: Invalid Status in linux source package in Eoan: Fix Committed Status in linux source package in Focal: Fix Committed Bug description: [Impact] Failure to run ip_defrag deterministically. [Fix] Use smaller packets and ignore EPERM. [Test case] Run the test multiple times without observing failures. [Regression potential] If the test fix is incorrect, it will cause us to miss real kernel bugs. But as it is now, we are already ignoring its results. == Test failed becuase: ./ip_defrag: sendto overlap: 1400: Operation not permitted selftests: net: ip_defrag.sh ipv6 tx:17 gso:1 (fail) OK ipv4 defrag PASS seed = 1556203721 ipv4 defrag with overlaps PASS seed = 1556203722 ipv6 defrag seed = 1556203756 PASS ipv6 defrag with overlaps seed = 1556203756 ./ip_defrag: sendto overlap: 1400: Operation not permitted not ok 1..17 selftests: net: ip_defrag.sh [FAIL] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1826848/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1879470] Re: stress-ng on gcov enabled focal kernel triggers OOPS
** Description changed: - Running stress-ng coverage testss on an ARM64 VM gcov 5.4.0-26-generic - focal kernel trips the following oops: + == SRU Justification Focal RISC-V == + + Running stress-ng coverage tests on an ARM64 VM gcov 5.4.0-26-generic + focal kernel trips an oops because the kernel stack is too small. + + == Fix == + + Clean Upstream commit: + + commit 0cac21b02ba5f3095fd2dcc77c26a25a0b2432ed + Author: Andreas Schwab + Date: Mon Jul 6 14:32:26 2020 +0200 + + riscv: use 16KB kernel stack on 64-bit + + == Test == + + Without the fix, we hit stack overflows. Run stress-ng kernel- + coverage.sh script with gcov enabled and the issue occurs. With the fix + the issue does not occur. + + == Regression Potential == + + This fix just affects 64 bit RISC-V and doubles the stack size. In + systems that run thousands of processes will see more memory being + consumed, but this most probably won't bite anyone because RISC-V + systems are generally not used in this manner. + + + + + + Running stress-ng coverage tests on an ARM64 VM gcov 5.4.0-26-generic focal kernel trips the following oops: cd stress-ng ./kernel-coverage.sh [ 894.205097] swapper pgtable: 4k pages, 48-bit VAs, pgdp=bf608000 [ 894.209645] [abd0c7eba050] pgd=0001b6fff003, pud=0001b6ffe003, pmd=00019b19d003, pte=00611f517f93 [ 894.217586] Internal error: Oops: 964f [#1] SMP [ 894.220753] Modules linked in: userio(+) aes_arm64 algif_rng aegis128 algif_aead anubis fcrypt khazad seed sm4_generic tea crc32_generic md4 michael_mic nhpoly1305_neon nhpoly1305 poly1305_generic rmd128 rmd160 rmd256 rmd320 sha3_generic sm3_generic streebog_generic tgr192 wp512 xxhash_generic algif_hash blowfish_generic blowfish_common cast5_generic des_generic libdes salsa20_generic chacha_neon chacha_generic unix_diag camellia_generic cast6_generic cast_common sctp serpent_generic twofish_generic twofish_common algif_skcipher atm af_alg dccp_ipv4 dccp xfs binfmt_misc zfs(PO) zunicode(PO) zavl(PO) icp(PO) zlua(PO) nls_iso8859_1 zcommon(PO) znvpair(PO) dm_multipath scsi_dh_rdac scsi_dh_emc spl(O) scsi_dh_alua qemu_fw_cfg nfsd auth_rpcgss sch_fq_codel nfs_acl lockd grace drm sunrpc virtio_rng ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_ce [ 894.227087] ghash_ce sha2_ce sha256_arm64 sha1_ce virtio_net virtio_blk net_failover virtio_scsi failover aes_neon_bs aes_neon_blk aes_ce_blk crypto_simd cryptd aes_ce_cipher [ 894.287863] CPU: 5 PID: 24647 Comm: modprobe Tainted: P O 5.4.0-26-generic #30 [ 894.292103] Hardware name: QEMU KVM Virtual Machine, BIOS 0.0.0 02/06/2015 [ 894.295900] pstate: 6045 (nZCv daif +PAN -UAO) [ 894.298999] pc : jump_label_swap+0x2c/0x80 [ 894.301451] lr : jump_label_swap+0x1c/0x80 [ 894.304012] sp : 8000168cba30 [ 894.305734] x29: 8000168cba30 x28: abd0c7eba0b0 [ 894.308535] x27: abd0c7eba050 x26: 0010 [ 894.311432] x25: 0010 x24: abd0da14c3c0 [ 894.315165] x23: 0050 x22: [ 894.319411] x21: abd0c7eba000 x20: abd0c7eba050 [ 894.323865] x19: abd0c7eba0b0 x18: [ 894.327192] x17: da02346b4a843289 x16: 785f32823a7a414c [ 894.330232] x15: 2ed60f0f x14: 0004 [ 894.333187] x13: abd0d8a918f0 x12: 0030 [ 894.336289] x11: cc4c3420 x10: 00015cc23828 [ 894.339448] x9 : x8 : abd0dd503000 [ 894.343242] x7 : x6 : [ 894.348272] x5 : 0001 x4 : d82c [ 894.351581] x3 : d9bc x2 : e410 [ 894.355001] x1 : abd0d9d3e76c x0 : ffa0 [ 894.358183] Call trace: [ 894.359991] jump_label_swap+0x2c/0x80 [ 894.362067] do_swap+0x40/0x170 [ 894.363886] sort_r+0x200/0x2f0 [ 894.365400] sort+0x30/0x48 [ 894.367488] jump_label_add_module+0x7c/0x458 [ 894.371041] jump_label_module_notify+0xc8/0x190 [ 894.375615] notifier_call_chain+0xa4/0x108 [ 894.378428] __blocking_notifier_call_chain+0xa4/0xe0 [ 894.381374] blocking_notifier_call_chain+0x54/0x70 [ 894.384374] load_module+0x1674/0x1d50 [ 894.386229] __do_sys_finit_module+0x184/0x1d8 [ 894.388569] __arm64_sys_finit_module+0x40/0x58 [ 894.390935] el0_svc_common.constprop.0+0x150/0x5e8 [ 894.394000] el0_svc_handler+0xbc/0x260 [ 894.396581] el0_svc+0x10/0x14 [ 894.398445] Code: b9400262 cb130280 29400e84 4b42 (b9000282) [ 894.402792] ---[ end trace 05455454484e1508 ]--- [ 897.757436] loop_set_block_size: loop3 () has still dirty pages (nrpages=1) -- You received this bug notification because you are a member of Kernel Packages, which is
[Kernel-packages] [Bug 1865967] Re: xfs fill_fs test in fallocate06 from ubuntu_ltp_syscalls failed
@Sean, the failure you have seen here in 5.4 I believe it's for btrfs instead (bug 1866323), not for xfs. ** Tags removed: 5.4 sru-20200629 -- 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/1865967 Title: xfs fill_fs test in fallocate06 from ubuntu_ltp_syscalls failed Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Disco: Won't Fix Status in linux source package in Eoan: Fix Released Bug description: == SRU Justification == The fill_fs test for XFS in fallocate06 from ubuntu_ltp_syscalls will fail on X/B/D/E: tst_test.c:1290: INFO: Testing on xfs tst_mkfs.c:90: INFO: Formatting /dev/loop1 with xfs opts='' extra opts='' tst_test.c:1229: INFO: Timeout per run is 0h 05m 00s fallocate06.c:117: INFO: Copy-on-write is not supported fallocate06.c:168: INFO: Case 1. Fill FS: no; Use copy on write: no fallocate06.c:157: PASS: write() successful fallocate06.c:201: PASS: Misaligned allocation works as expected fallocate06.c:157: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) successful fallocate06.c:237: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) cleared the correct file range fallocate06.c:168: INFO: Case 2. Fill FS: yes; Use copy on write: no tst_fill_fs.c:32: INFO: Creating file mntpoint/file0 size 21710183 tst_fill_fs.c:32: INFO: Creating file mntpoint/file1 size 8070086 tst_fill_fs.c:32: INFO: Creating file mntpoint/file2 size 3971177 tst_fill_fs.c:32: INFO: Creating file mntpoint/file3 size 36915315 tst_fill_fs.c:32: INFO: Creating file mntpoint/file4 size 70310993 tst_fill_fs.c:32: INFO: Creating file mntpoint/file5 size 4807935 tst_fill_fs.c:32: INFO: Creating file mntpoint/file6 size 90739786 tst_fill_fs.c:32: INFO: Creating file mntpoint/file7 size 76896492 tst_fill_fs.c:32: INFO: Creating file mntpoint/file8 size 72228649 tst_fill_fs.c:32: INFO: Creating file mntpoint/file9 size 36207821 tst_fill_fs.c:32: INFO: Creating file mntpoint/file10 size 81483962 tst_fill_fs.c:32: INFO: Creating file mntpoint/file11 size 92198827 tst_fill_fs.c:59: INFO: write(): ENOSPC (28) fallocate06.c:153: FAIL: Unexpected return value from write(): 7680 (expected 8192) fallocate06.c:157: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) successful fallocate06.c:237: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) cleared the correct file range == Fix == * e093c4be (xfs: Fix tail rounding in xfs_alloc_file_space()) This patch can be cherry-picked in D/E and needs some minor context adjustmest on X/B. == Test == Test kernels can be found here: https://people.canonical.com/~phlin/kernel/lp-1865967-xfs-fallocate06/ All patched kernels are working as expected, this issue will no longer exist on XFS: tst_test.c:1290: INFO: Testing on xfs tst_mkfs.c:90: INFO: Formatting /dev/loop5 with xfs opts='' extra opts='' tst_test.c:1229: INFO: Timeout per run is 0h 05m 00s fallocate06.c:117: INFO: Copy-on-write is not supported fallocate06.c:168: INFO: Case 1. Fill FS: no; Use copy on write: no fallocate06.c:157: PASS: write() successful fallocate06.c:201: PASS: Misaligned allocation works as expected fallocate06.c:157: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) successful fallocate06.c:237: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) cleared the correct file range fallocate06.c:168: INFO: Case 2. Fill FS: yes; Use copy on write: no tst_fill_fs.c:32: INFO: Creating file mntpoint/file0 size 21710183 tst_fill_fs.c:32: INFO: Creating file mntpoint/file1 size 8070086 tst_fill_fs.c:32: INFO: Creating file mntpoint/file2 size 3971177 tst_fill_fs.c:32: INFO: Creating file mntpoint/file3 size 36915315 tst_fill_fs.c:32: INFO: Creating file mntpoint/file4 size 70310993 tst_fill_fs.c:32: INFO: Creating file mntpoint/file5 size 4807935 tst_fill_fs.c:32: INFO: Creating file mntpoint/file6 size 90739786 tst_fill_fs.c:32: INFO: Creating file mntpoint/file7 size 76896492 tst_fill_fs.c:32: INFO: Creating file mntpoint/file8 size 72228649 tst_fill_fs.c:32: INFO: Creating file mntpoint/file9 size 36207821 tst_fill_fs.c:32: INFO: Creating file mntpoint/file10 size 81483962 tst_fill_fs.c:32: INFO: Creating file mntpoint/file11 size 92198827 tst_fill_fs.c:59: INFO: write(): ENOSPC (28) fallocate06.c:157: PASS: write() successful fallocate06.c:201: PASS: Misaligned allocation works as expected fallocate06.c:157: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) successful fallocate06.c:237: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) cleared the correct file range == Regression Potential == Low, this
[Kernel-packages] [Bug 1866323] Re: btrfs fill_fs test in fallocate06 from ubuntu_ltp_syscalls failed
** Tags added: 5.4 sru-20200629 -- 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/1866323 Title: btrfs fill_fs test in fallocate06 from ubuntu_ltp_syscalls failed Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Incomplete Bug description: Test failure in fallocate06 was composed by two issues, one is xfs fill_fs test issue addressed in bug 1865967. Another is this one, this is the case 2 of btrfs (fill_fs): tst_test.c:1290: INFO: Testing on btrfs tst_mkfs.c:90: INFO: Formatting /dev/loop1 with btrfs opts='' extra opts='' tst_test.c:1229: INFO: Timeout per run is 0h 05m 00s fallocate06.c:117: INFO: Copy-on-write is supported fallocate06.c:168: INFO: Case 1. Fill FS: no; Use copy on write: no fallocate06.c:157: PASS: write() successful fallocate06.c:201: PASS: Misaligned allocation works as expected fallocate06.c:157: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) successful fallocate06.c:237: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) cleared the correct file range fallocate06.c:168: INFO: Case 2. Fill FS: yes; Use copy on write: no tst_fill_fs.c:32: INFO: Creating file mntpoint/file0 size 21710183 tst_fill_fs.c:32: INFO: Creating file mntpoint/file1 size 8070086 tst_fill_fs.c:32: INFO: Creating file mntpoint/file2 size 3971177 tst_fill_fs.c:32: INFO: Creating file mntpoint/file3 size 36915315 tst_fill_fs.c:32: INFO: Creating file mntpoint/file4 size 70310993 tst_fill_fs.c:32: INFO: Creating file mntpoint/file5 size 4807935 tst_fill_fs.c:32: INFO: Creating file mntpoint/file6 size 90739786 tst_fill_fs.c:32: INFO: Creating file mntpoint/file7 size 76896492 tst_fill_fs.c:32: INFO: Creating file mntpoint/file8 size 72228649 tst_fill_fs.c:32: INFO: Creating file mntpoint/file9 size 36207821 tst_fill_fs.c:32: INFO: Creating file mntpoint/file10 size 81483962 tst_fill_fs.c:59: INFO: write(): ENOSPC (28) fallocate06.c:157: PASS: write() successful fallocate06.c:201: PASS: Misaligned allocation works as expected fallocate06.c:146: FAIL: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) failed unexpectedly: ENOSPC (2 This issue can be found from X to F X - https://pastebin.ubuntu.com/p/9FfVrZkQN8/ B - https://pastebin.ubuntu.com/p/Zc9TW4sQKF/ D - https://pastebin.ubuntu.com/p/cryTnnn5wF/ E - https://pastebin.ubuntu.com/p/FXTZpsX7Qb/ F - https://pastebin.ubuntu.com/p/FKPJKCS2zr/ Note that the hint printed in the test: HINT: You _MAY_ be missing kernel fixes, see: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e093c4be760e It something that will get printed after the test, as it's for XFS so it has nothing to do with this issue here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1866323/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888193] Re: Xorg freeze
This looks like a hardware or driver problem with the Radeon Pro WX 7100. Your logs show two issues: 1. Xorg logs that the monitor is being repeatedly redetected. So it sounds like the monitor is not plugged in properly. Maybe try a new monitor cable. 2. The kernel is logging more serious issues: [ 107.569355] amdgpu :0a:00.0: GPU fault detected: 146 0x0c38480c for process mksReplay pid 2764 thread main-mks pid 2772 [ 107.569358] amdgpu :0a:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x0030C387 [ 107.569359] amdgpu :0a:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0804800C [ 107.569360] amdgpu :0a:00.0: VM fault (0x0c, vmid 4, pasid 32785) at page 3195783, read from 'TC4' (0x54433400) (72) [ 107.569365] amdgpu :0a:00.0: GPU fault detected: 146 0x0c38880c for process mksReplay pid 2764 thread main-mks pid 2772 [ 107.569366] amdgpu :0a:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x0030C38E [ 107.569367] amdgpu :0a:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0808400C [ 107.569368] amdgpu :0a:00.0: VM fault (0x0c, vmid 4, pasid 32785) at page 3195790, read from 'TC7' (0x54433700) (132) [ 107.597584] amdgpu :0a:00.0: GPU fault detected: 146 0x0c38480c for process mksReplay pid 2764 thread main-mks pid 2772 [ 107.597587] amdgpu :0a:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x0030C387 [ 107.597588] amdgpu :0a:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0E04800C [ 107.597590] amdgpu :0a:00.0: VM fault (0x0c, vmid 7, pasid 32785) at page 3195783, read from 'TC4' (0x54433400) (72) [ 107.597595] amdgpu :0a:00.0: GPU fault detected: 146 0x0c38880c for process mksReplay pid 2764 thread main-mks pid 2772 [ 107.597596] amdgpu :0a:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x0030C38D [ 107.597597] amdgpu :0a:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0E04400C [ 107.597598] amdgpu :0a:00.0: VM fault (0x0c, vmid 7, pasid 32785) at page 3195789, read from 'TC5' (0x54433500) (68) [ ** Tags added: amdgpu ** Summary changed: - Xorg freeze + [amdgpu] Xorg freeze ** Package changed: xorg (Ubuntu) => xserver-xorg-video-amdgpu (Ubuntu) ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1888193 Title: [amdgpu] Xorg freeze Status in linux package in Ubuntu: New Status in xserver-xorg-video-amdgpu package in Ubuntu: New Bug description: I have Radeon Pro WX 7100. It hangs twice a day. I narrow-downed this issue to the fan speed lock. After reboot, it always runs on 18%, no matter of the load. If I install Radeon Profile and force fan to 100% and then turn auto fan configuration, then fan reacts on the load. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-62-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jul 20 09:15:03 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Very infrequently GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon Pro WX 7100] [1002:67c4] (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon Pro WX 7100] [1002:0b0d] InstallationDate: Installed on 2020-06-29 (20 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic root=UUID=2b68d049-e85f-47ab-97d9-5632f225b71b ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/17/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 7803 dmi.board.asset.tag: Default string dmi.board.name: ROG CROSSHAIR VI HERO (WI-FI AC) 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.:bvr7803:bd06/17/2020:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGCROSSHAIRVIHERO(WI-FIAC):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 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri:
[Kernel-packages] [Bug 1878421] Re: Using two GPUs with one monitor each, one is always black
https://gitlab.gnome.org/GNOME/mutter/-/issues/1351 but currently it looks related to nvidia/nouveau driver ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1351 https://gitlab.gnome.org/GNOME/mutter/-/issues/1351 -- 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/1878421 Title: Using two GPUs with one monitor each, one is always black Status in Mutter: New Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: Hi, i try to use external monitor on my dell G5 2019 (5590). works on ubuntu 18.4 (after reboot) using prime-select nvidia. did this on 20.4 (prime-select + reboot because logoff/login again still don't work) and it hang on boot while showing ubuntu bootscreen with animation (not stopped, but also response to esc-key to show terminal-output) on the monitor (need to switch off). booted again where monitor is configured to other input, boot works, i see it in preferences dialog as second monitor, but if i configure input on monitor i have no signal.. anything i can try? regards Frank ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME-Flashback:GNOME Date: Wed May 13 15:21:08 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:08ea] NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f91] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell TU117M [GeForce GTX 1650 Mobile / Max-Q] [1028:08ea] InstallationDate: Installed on 2020-04-27 (16 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 27c6:530c Shenzhen Goodix Technology Co.,Ltd. Fingerprint Reader Bus 001 Device 002: ID 0c45:671f Microdia Integrated_Webcam_HD Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. G5 5590 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=7c9113b7-ca65-4c46-9435-f5d2b73bab72 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/07/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0KW84T dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd02/07/2020:svnDellInc.:pnG55590:pvr:rvnDellInc.:rn0KW84T:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: GSeries dmi.product.name: G5 5590 dmi.product.sku: 08EA dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1878421/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888202] Re: package zfsutils-linux 0.8.3-1ubuntu12.1 failed to install/upgrade: installed zfsutils-linux package post-installation script subprocess returned error exit status
** Tags removed: need-duplicate-check -- 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/1888202 Title: package zfsutils-linux 0.8.3-1ubuntu12.1 failed to install/upgrade: installed zfsutils-linux package post-installation script subprocess returned error exit status 1 Status in zfs-linux package in Ubuntu: New Bug description: the upgrade process assumes ZFS-utils is not configured and has exit code 1 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: zfsutils-linux 0.8.3-1ubuntu12.1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 AptOrdering: gir1.2-webkit2-4.0:amd64: Install gir1.2-javascriptcoregtk-4.0:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Jul 20 10:22:00 2020 ErrorMessage: installed zfsutils-linux package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2016-05-15 (1526 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: zfs-linux Title: package zfsutils-linux 0.8.3-1ubuntu12.1 failed to install/upgrade: installed zfsutils-linux package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-05-24 (56 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1888202/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888202] [NEW] package zfsutils-linux 0.8.3-1ubuntu12.1 failed to install/upgrade: installed zfsutils-linux package post-installation script subprocess returned error exit statu
Public bug reported: the upgrade process assumes ZFS-utils is not configured and has exit code 1 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: zfsutils-linux 0.8.3-1ubuntu12.1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 AptOrdering: gir1.2-webkit2-4.0:amd64: Install gir1.2-javascriptcoregtk-4.0:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Jul 20 10:22:00 2020 ErrorMessage: installed zfsutils-linux package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2016-05-15 (1526 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: zfs-linux Title: package zfsutils-linux 0.8.3-1ubuntu12.1 failed to install/upgrade: installed zfsutils-linux package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-05-24 (56 days ago) ** Affects: zfs-linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- 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/1888202 Title: package zfsutils-linux 0.8.3-1ubuntu12.1 failed to install/upgrade: installed zfsutils-linux package post-installation script subprocess returned error exit status 1 Status in zfs-linux package in Ubuntu: New Bug description: the upgrade process assumes ZFS-utils is not configured and has exit code 1 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: zfsutils-linux 0.8.3-1ubuntu12.1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 AptOrdering: gir1.2-webkit2-4.0:amd64: Install gir1.2-javascriptcoregtk-4.0:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Jul 20 10:22:00 2020 ErrorMessage: installed zfsutils-linux package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2016-05-15 (1526 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: zfs-linux Title: package zfsutils-linux 0.8.3-1ubuntu12.1 failed to install/upgrade: installed zfsutils-linux package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-05-24 (56 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1888202/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881137] Re: Introduce the new NVIDIA 418-server and 440-server series, and update the current NVIDIA drivers
The results look good to me. The only case that looks like a failure doesn't really have the nvidia modules loaded, so it's ok. ** Tags removed: verification-needed verification-needed-bionic verification-needed-focal ** Tags added: verification-done verification-done-bionic verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1881137 Title: Introduce the new NVIDIA 418-server and 440-server series, and update the current NVIDIA drivers Status in linux package in Ubuntu: Incomplete Status in linux-restricted-modules package in Ubuntu: New Status in nvidia-graphics-drivers-418-server package in Ubuntu: Invalid Status in nvidia-graphics-drivers-440 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-440-server package in Ubuntu: New Status in nvidia-settings package in Ubuntu: New Status in linux source package in Bionic: Fix Committed Status in linux-restricted-modules source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-440 source package in Bionic: In Progress Status in nvidia-graphics-drivers-440-server source package in Bionic: In Progress Status in nvidia-settings source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux-restricted-modules source package in Focal: Fix Committed Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-440 source package in Focal: In Progress Status in nvidia-graphics-drivers-440-server source package in Focal: Fix Committed Status in nvidia-settings source package in Focal: Fix Committed Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] 440.82: * New upstream release: - Added a workaround for Steam Play title DOOM Eternal, which overrides application requested memory locations, to ensure performance-critical resources be placed in video memory. - Allow presenting from queue families which only expose VK_QUEUE_COMPUTE_BIT when using XCB in addition to Xlib surfaces. - Fixed a bug that caused render-offloaded applications to crash on exit. - Fixed a driver installation failure on Linux kernel 5.6 release candidates, where the NVIDIA kernel module failed to build with error "implicit declaration of function 'timespec_to_ns'". - Fixed a driver installation failure on Linux kernel 5.6 release candidates, where the NVIDIA kernel module failed to build with error "implicit declaration of function 'getrawmonotonic'". - Fixed a driver installation failure on Linux kernel 5.6 release candidates, where the NVIDIA kernel module failed to build with error "implicit declaration of function 'timespec_to_ns'". - Fixed a driver installation failure on Linux kernel 5.6 release candidates, where the NVIDIA kernel module failed to build with error "implicit declaration of function 'getrawmonotonic'". - Fixed a driver installation failure on Linux kernel 5.6 release candidates, where the NVIDIA kernel module failed to build with error "implicit declaration of function 'getnstimeofday'". - Fixed a driver installation failure on Linux kernel 5.6 release candidates, where the NVIDIA kernel module failed to build with error "dereferencing pointer to incomplete type 'struct timeval'". - Fixed a driver installation failure on Linux kernel 5.6 release candidates, where the NVIDIA kernel module failed to build with error "implicit declaration of function 'jiffies_to_timespec'". - Fixed driver installation failure on Linux kernel 5.6 release candidates, where the NVIDIA kernel module failed to build with error "passing argument 4 of 'proc_create_data' from incompatible pointer type". 440.64.00: *
Re: [Kernel-packages] [Bug 1888193] Re: Xorg freeze
Issues in dmesg in kernel are my fault - I'm developing app, which faults GPU. Have you read my description of the narrowed down issue? pon., 20 lip 2020 o 09:50 Daniel van Vugt <1888...@bugs.launchpad.net> napisał(a): > This looks like a hardware or driver problem with the Radeon Pro WX > 7100. Your logs show two issues: > > 1. Xorg logs that the monitor is being repeatedly redetected. So it > sounds like the monitor is not plugged in properly. Maybe try a new > monitor cable. > > 2. The kernel is logging more serious issues: > > [ 107.569355] amdgpu :0a:00.0: GPU fault detected: 146 0x0c38480c for > process mksReplay pid 2764 thread main-mks pid 2772 > [ 107.569358] amdgpu :0a:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR > 0x0030C387 > [ 107.569359] amdgpu :0a:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS > 0x0804800C > [ 107.569360] amdgpu :0a:00.0: VM fault (0x0c, vmid 4, pasid 32785) > at page 3195783, read from 'TC4' (0x54433400) (72) > [ 107.569365] amdgpu :0a:00.0: GPU fault detected: 146 0x0c38880c for > process mksReplay pid 2764 thread main-mks pid 2772 > [ 107.569366] amdgpu :0a:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR > 0x0030C38E > [ 107.569367] amdgpu :0a:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS > 0x0808400C > [ 107.569368] amdgpu :0a:00.0: VM fault (0x0c, vmid 4, pasid 32785) > at page 3195790, read from 'TC7' (0x54433700) (132) > [ 107.597584] amdgpu :0a:00.0: GPU fault detected: 146 0x0c38480c for > process mksReplay pid 2764 thread main-mks pid 2772 > [ 107.597587] amdgpu :0a:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR > 0x0030C387 > [ 107.597588] amdgpu :0a:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS > 0x0E04800C > [ 107.597590] amdgpu :0a:00.0: VM fault (0x0c, vmid 7, pasid 32785) > at page 3195783, read from 'TC4' (0x54433400) (72) > [ 107.597595] amdgpu :0a:00.0: GPU fault detected: 146 0x0c38880c for > process mksReplay pid 2764 thread main-mks pid 2772 > [ 107.597596] amdgpu :0a:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR > 0x0030C38D > [ 107.597597] amdgpu :0a:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS > 0x0E04400C > [ 107.597598] amdgpu :0a:00.0: VM fault (0x0c, vmid 7, pasid 32785) > at page 3195789, read from 'TC5' (0x54433500) (68) > [ > > ** Tags added: amdgpu > > ** Summary changed: > > - Xorg freeze > + [amdgpu] Xorg freeze > > ** Package changed: xorg (Ubuntu) => xserver-xorg-video-amdgpu (Ubuntu) > > ** Also affects: linux (Ubuntu) >Importance: Undecided >Status: New > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1888193 > > Title: > [amdgpu] Xorg freeze > > Status in linux package in Ubuntu: > New > Status in xserver-xorg-video-amdgpu package in Ubuntu: > New > > Bug description: > I have Radeon Pro WX 7100. It hangs twice a day. > > I narrow-downed this issue to the fan speed lock. After reboot, it > always runs on 18%, no matter of the load. If I install Radeon Profile > and force fan to 100% and then turn auto fan configuration, then fan > reacts on the load. > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: xorg 1:7.7+19ubuntu7.1 > ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18 > Uname: Linux 5.3.0-62-generic x86_64 > ApportVersion: 2.20.9-0ubuntu7.15 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Mon Jul 20 09:15:03 2020 > DistUpgraded: Fresh install > DistroCodename: bionic > DistroVariant: ubuntu > ExtraDebuggingInterest: Yes > GpuHangFrequency: Very infrequently > GraphicsCard: >Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon Pro WX 7100] > [1002:67c4] (prog-if 00 [VGA controller]) > Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon > Pro WX 7100] [1002:0b0d] > InstallationDate: Installed on 2020-06-29 (20 days ago) > InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 > (20190805) > MachineType: System manufacturer System Product Name > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic > root=UUID=2b68d049-e85f-47ab-97d9-5632f225b71b ro quiet splash vt.handoff=1 > SourcePackage: xorg > Symptom: display > Title: Xorg freeze > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 06/17/2020 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: 7803 > dmi.board.asset.tag: Default string > dmi.board.name: ROG CROSSHAIR VI HERO (WI-FI AC) > 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: >
[Kernel-packages] [Bug 1826848] Re: ip_defrag.sh in net from ubuntu_kernel_selftests failed with 5.0 / 5.3 / 5.4 kernel
The test has passed with 5.3.0-64.58 on all different arches. ** Tags removed: verification-needed-eoan ** Tags added: verification-done-eoan -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1826848 Title: ip_defrag.sh in net from ubuntu_kernel_selftests failed with 5.0 / 5.3 / 5.4 kernel Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Disco: Invalid Status in linux source package in Eoan: Fix Committed Status in linux source package in Focal: Fix Committed Bug description: [Impact] Failure to run ip_defrag deterministically. [Fix] Use smaller packets and ignore EPERM. [Test case] Run the test multiple times without observing failures. [Regression potential] If the test fix is incorrect, it will cause us to miss real kernel bugs. But as it is now, we are already ignoring its results. == Test failed becuase: ./ip_defrag: sendto overlap: 1400: Operation not permitted selftests: net: ip_defrag.sh ipv6 tx:17 gso:1 (fail) OK ipv4 defrag PASS seed = 1556203721 ipv4 defrag with overlaps PASS seed = 1556203722 ipv6 defrag seed = 1556203756 PASS ipv6 defrag with overlaps seed = 1556203756 ./ip_defrag: sendto overlap: 1400: Operation not permitted not ok 1..17 selftests: net: ip_defrag.sh [FAIL] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1826848/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887910] Re: [bionic]blutoothd segfault when you cancel the keyboard pairing during the dialog for pairing code
Alex, did you read comment 7? 'low' isn't responding to what the regression potential should provide, it's there to describe what impact the change could have to know on what to focus the testing -- 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/1887910 Title: [bionic]blutoothd segfault when you cancel the keyboard pairing during the dialog for pairing code Status in OEM Priority Project: In Progress Status in bluez package in Ubuntu: Fix Released Status in bluez source package in Bionic: In Progress Status in bluez source package in Eoan: Fix Released Status in bluez source package in Focal: Fix Released Status in bluez source package in Groovy: Fix Released Bug description: [Impact] * only impact Bionic machines because series after Bionic already included this patch. [Test Case] 1. pair bluetooth keyboard 2. see the dialog asking user input the code for pairing. 3. press "esc" to cancel it. 4. the bluetooth should still work to pair another bluetooth device. [Regression Potential] * low, because the same patch from upstream is already there on Groovy, Focal and Eoan. [Other Info] * NO. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1887910/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882093] Re: CVE-2020-{5963|5967} NVIDIA
The results look good to me. The only case that looks like a failure
doesn't really have the nvidia modules loaded, so it's ok.
** Also affects: nvidia-graphics-drivers-440-server (Ubuntu)
Importance: Undecided
Status: New
** Changed in: nvidia-graphics-drivers-440-server (Ubuntu Bionic)
Importance: Undecided => High
** Changed in: nvidia-graphics-drivers-440-server (Ubuntu Bionic)
Status: New => Fix Committed
** Changed in: nvidia-graphics-drivers-440-server (Ubuntu Bionic)
Assignee: (unassigned) => Alberto Milone (albertomilone)
** Changed in: nvidia-graphics-drivers-440-server (Ubuntu Focal)
Importance: Undecided => High
** Changed in: nvidia-graphics-drivers-440-server (Ubuntu Focal)
Status: New => Fix Committed
** Changed in: nvidia-graphics-drivers-440-server (Ubuntu Focal)
Assignee: (unassigned) => Alberto Milone (albertomilone)
** No longer affects: nvidia-graphics-drivers-440-server (Ubuntu Eoan)
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/1882093
Title:
CVE-2020-{5963|5967} NVIDIA
Status in nvidia-graphics-drivers-390 package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-440 package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-440-server package in Ubuntu:
New
Status in nvidia-graphics-drivers-390 source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-440 source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-440-server source package in Bionic:
Fix Committed
Status in nvidia-graphics-drivers-390 source package in Eoan:
Fix Released
Status in nvidia-graphics-drivers-440 source package in Eoan:
Fix Released
Status in nvidia-graphics-drivers-390 source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-440 source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-440-server source package in Focal:
Fix Committed
Bug description:
Security update for CVE-2020-5963 CVE-2020-5967
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1882093/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1879470] Re: stress-ng on gcov enabled focal kernel triggers OOPS
** Changed in: linux (Ubuntu) Status: Expired => 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/1879470 Title: stress-ng on gcov enabled focal kernel triggers OOPS Status in linux package in Ubuntu: In Progress Bug description: Running stress-ng coverage testss on an ARM64 VM gcov 5.4.0-26-generic focal kernel trips the following oops: cd stress-ng ./kernel-coverage.sh [ 894.205097] swapper pgtable: 4k pages, 48-bit VAs, pgdp=bf608000 [ 894.209645] [abd0c7eba050] pgd=0001b6fff003, pud=0001b6ffe003, pmd=00019b19d003, pte=00611f517f93 [ 894.217586] Internal error: Oops: 964f [#1] SMP [ 894.220753] Modules linked in: userio(+) aes_arm64 algif_rng aegis128 algif_aead anubis fcrypt khazad seed sm4_generic tea crc32_generic md4 michael_mic nhpoly1305_neon nhpoly1305 poly1305_generic rmd128 rmd160 rmd256 rmd320 sha3_generic sm3_generic streebog_generic tgr192 wp512 xxhash_generic algif_hash blowfish_generic blowfish_common cast5_generic des_generic libdes salsa20_generic chacha_neon chacha_generic unix_diag camellia_generic cast6_generic cast_common sctp serpent_generic twofish_generic twofish_common algif_skcipher atm af_alg dccp_ipv4 dccp xfs binfmt_misc zfs(PO) zunicode(PO) zavl(PO) icp(PO) zlua(PO) nls_iso8859_1 zcommon(PO) znvpair(PO) dm_multipath scsi_dh_rdac scsi_dh_emc spl(O) scsi_dh_alua qemu_fw_cfg nfsd auth_rpcgss sch_fq_codel nfs_acl lockd grace drm sunrpc virtio_rng ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_ce [ 894.227087] ghash_ce sha2_ce sha256_arm64 sha1_ce virtio_net virtio_blk net_failover virtio_scsi failover aes_neon_bs aes_neon_blk aes_ce_blk crypto_simd cryptd aes_ce_cipher [ 894.287863] CPU: 5 PID: 24647 Comm: modprobe Tainted: P O 5.4.0-26-generic #30 [ 894.292103] Hardware name: QEMU KVM Virtual Machine, BIOS 0.0.0 02/06/2015 [ 894.295900] pstate: 6045 (nZCv daif +PAN -UAO) [ 894.298999] pc : jump_label_swap+0x2c/0x80 [ 894.301451] lr : jump_label_swap+0x1c/0x80 [ 894.304012] sp : 8000168cba30 [ 894.305734] x29: 8000168cba30 x28: abd0c7eba0b0 [ 894.308535] x27: abd0c7eba050 x26: 0010 [ 894.311432] x25: 0010 x24: abd0da14c3c0 [ 894.315165] x23: 0050 x22: [ 894.319411] x21: abd0c7eba000 x20: abd0c7eba050 [ 894.323865] x19: abd0c7eba0b0 x18: [ 894.327192] x17: da02346b4a843289 x16: 785f32823a7a414c [ 894.330232] x15: 2ed60f0f x14: 0004 [ 894.333187] x13: abd0d8a918f0 x12: 0030 [ 894.336289] x11: cc4c3420 x10: 00015cc23828 [ 894.339448] x9 : x8 : abd0dd503000 [ 894.343242] x7 : x6 : [ 894.348272] x5 : 0001 x4 : d82c [ 894.351581] x3 : d9bc x2 : e410 [ 894.355001] x1 : abd0d9d3e76c x0 : ffa0 [ 894.358183] Call trace: [ 894.359991] jump_label_swap+0x2c/0x80 [ 894.362067] do_swap+0x40/0x170 [ 894.363886] sort_r+0x200/0x2f0 [ 894.365400] sort+0x30/0x48 [ 894.367488] jump_label_add_module+0x7c/0x458 [ 894.371041] jump_label_module_notify+0xc8/0x190 [ 894.375615] notifier_call_chain+0xa4/0x108 [ 894.378428] __blocking_notifier_call_chain+0xa4/0xe0 [ 894.381374] blocking_notifier_call_chain+0x54/0x70 [ 894.384374] load_module+0x1674/0x1d50 [ 894.386229] __do_sys_finit_module+0x184/0x1d8 [ 894.388569] __arm64_sys_finit_module+0x40/0x58 [ 894.390935] el0_svc_common.constprop.0+0x150/0x5e8 [ 894.394000] el0_svc_handler+0xbc/0x260 [ 894.396581] el0_svc+0x10/0x14 [ 894.398445] Code: b9400262 cb130280 29400e84 4b42 (b9000282) [ 894.402792] ---[ end trace 05455454484e1508 ]--- [ 897.757436] loop_set_block_size: loop3 () has still dirty pages (nrpages=1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879470/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888341] 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/1888341 Title: package linux-image-5.4.0-40-generic 5.4.0-40.44 failed to install/upgrade: installed linux-image-5.4.0-40-generic package pre- removal script subprocess returned error exit status 1 Status in linux package in Ubuntu: Confirmed Bug description: error ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: qnx4 hfsplus hfs minix ntfs jfs nls_utf8 rfcomm lkp_Ubuntu_5_4_0_40_44_generic_69 bnep snd_hda_codec_realtek snd_hda_codec_hdmi snd_hda_codec_generic ledtrig_audio amdgpu snd_hda_intel snd_intel_dspcfg uvcvideo snd_hda_codec snd_hda_core amd_iommu_v2 gpu_sched x86_pkg_temp_thermal mei_hdcp intel_powerclamp coretemp intel_rapl_msr videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 btusb videobuf2_common btrtl btbcm btintel bluetooth videodev i915 wl radeon mc intel_cstate intel_rapl_perf mei_me cfg80211 mei hp_wmi sparse_keymap processor_thermal_device intel_rapl_common int340x_thermal_zone intel_soc_dts_iosf wmi_bmof mac_hid intel_pch_thermal int3400_thermal hp_wireless acpi_thermal_rel i2c_i801 r8169 lpc_ich realtek wmi i2c_hid ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tanzeel1688 F pulseaudio /dev/snd/controlC0: tanzeel1688 F pulseaudio CasperMD5CheckResult: skip Date: Tue Jul 21 01:09:19 2020 ErrorMessage: installed linux-image-5.4.0-40-generic package pre-removal script subprocess returned error exit status 1 InstallationDate: Installed on 2020-05-31 (50 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Hewlett-Packard HP Notebook ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: grub-pc 2.04-1ubuntu26 SourcePackage: linux Title: package linux-image-5.4.0-40-generic 5.4.0-40.44 failed to install/upgrade: installed linux-image-5.4.0-40-generic package pre-removal script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/24/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80C2 dmi.board.vendor: Hewlett-Packard dmi.board.version: 96.02 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.02:bd03/24/2015:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn80C2:rvr96.02:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: M9H15EA#ABV dmi.product.version: Type1ProductConfigId dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888341/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888334] 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 1888334 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 ** Changed in: linux (Ubuntu Eoan) 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/1888334 Title: [Potential Regression] tm-resched-dscr from powerpc in ubuntu_kernel_selftests failed on E Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Eoan: Incomplete Bug description: Issue found on 5.3.0-64.58 with P8 node modoc (skipped with P9 node) # selftests: powerpc/tm: tm-resched-dscr # test: tm_resched_dscr # tags: git_version:unknown # Binding to cpu 8 # main test running as pid 142637 # Check DSCR TM context switch: FAIL # failure: tm_resched_dscr not ok 1 selftests: powerpc/tm: tm-resched-dscr # exit=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1888334/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888332] 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 1888332 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 ** Changed in: linux (Ubuntu Eoan) 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/1888332 Title: [Potential Regression] dscr_inherit_exec_test from powerpc in ubuntu_kernel_selftests failed on E Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Eoan: Incomplete Bug description: Issue found on 5.3.0-64.58 with P8 node modoc (passed with P9 node) # selftests: powerpc/dscr: dscr_inherit_exec_test # test: dscr_inherit_exec_test # tags: git_version:unknown # Parent DSCR 1 was not inherited over exec (kernel value) # Child didn't exit cleanly # failure: dscr_inherit_exec_test not ok 5 selftests: powerpc/dscr: dscr_inherit_exec_test # exit=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1888332/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888339] 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 1888339 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 ** Changed in: linux (Ubuntu Eoan) 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/1888339 Title: [Potential Regression] ptrace-tar from powerpc in ubuntu_kernel_selftests failed on E Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Eoan: Incomplete Bug description: Issue found on 5.3.0-64.58 with P8 node modoc (passed with P9 node) # selftests: powerpc/ptrace: ptrace-tar # test: ptrace_tar # tags: git_version:f21e446-dirty # [User Write (Running)] TAR: 10 PPR: 4 DSCR: 100 # [User Read (Running)] TAR: 20 PPR: 8 DSCR: 0 # [Ptrace Read (Running)]TAR: 10 PPR: 4 DSCR: 100 # [Ptrace Write (Running)] TAR: 20 PPR: 8 DSCR: 200 # failure: ptrace_tar not ok 4 selftests: powerpc/ptrace: ptrace-tar # exit=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1888339/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822581] Re: HP 1030 G3 fn-keys not working
Doesn't seem to be a software issue. Please try power reset and see if it helps: https://support.hp.com/us-en/document/c01684768 -- 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/1822581 Title: HP 1030 G3 fn-keys not working Status in linux package in Ubuntu: Invalid Bug description: Running Ubuntu 18.10 on my HP Elitebook x360 1030 G3 I noticed, that the fn key combinations are only working partially. What works: Volume up/down/mute, Airplane mode What doesn't work: Brigtness up/down, microphone mute, fn-Keys indicator lights I already tried solutions regarding editing the Kernel Parameter acpi_osi in the grub config but can not get the keys to work. In case of screen brightness changing it using the desktop slider works. But it seems, that the keypress isn't recognized at all. Neither xev nor acpi_listen are showing events for screen brightness (fn+f3/f4) or microphone muting (fn+f8). Running showkey -k results in a keycode 465 pressed and released event for all three key combinations. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: udev 239-7ubuntu10.10 ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20 Uname: Linux 4.18.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 70-snap.core.rules Date: Mon Apr 1 14:22:47 2019 InstallationDate: Installed on 2019-03-30 (1 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: HP HP EliteBook x360 1030 G3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=db6a8def-2553-4696-b160-f79e8865b17e ro quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/04/2019 dmi.bios.vendor: HP dmi.bios.version: Q90 Ver. 01.06.00 dmi.board.name: 8438 dmi.board.vendor: HP dmi.board.version: KBC Version 14.38.00 dmi.chassis.asset.tag: 5CD8427YK5 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ90Ver.01.06.00:bd01/04/2019:svnHP:pnHPEliteBookx3601030G3:pvr:rvnHP:rn8438:rvrKBCVersion14.38.00:cvnHP:ct31:cvr: dmi.product.family: 103C_5336AN HP EliteBook x360 dmi.product.name: HP EliteBook x360 1030 G3 dmi.product.sku: 4QZ13ES#ABD dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822581/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888341] [NEW] package linux-image-5.4.0-40-generic 5.4.0-40.44 failed to install/upgrade: installed linux-image-5.4.0-40-generic package pre-removal script subprocess returned
Public bug reported: error ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: qnx4 hfsplus hfs minix ntfs jfs nls_utf8 rfcomm lkp_Ubuntu_5_4_0_40_44_generic_69 bnep snd_hda_codec_realtek snd_hda_codec_hdmi snd_hda_codec_generic ledtrig_audio amdgpu snd_hda_intel snd_intel_dspcfg uvcvideo snd_hda_codec snd_hda_core amd_iommu_v2 gpu_sched x86_pkg_temp_thermal mei_hdcp intel_powerclamp coretemp intel_rapl_msr videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 btusb videobuf2_common btrtl btbcm btintel bluetooth videodev i915 wl radeon mc intel_cstate intel_rapl_perf mei_me cfg80211 mei hp_wmi sparse_keymap processor_thermal_device intel_rapl_common int340x_thermal_zone intel_soc_dts_iosf wmi_bmof mac_hid intel_pch_thermal int3400_thermal hp_wireless acpi_thermal_rel i2c_i801 r8169 lpc_ich realtek wmi i2c_hid ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tanzeel1688 F pulseaudio /dev/snd/controlC0: tanzeel1688 F pulseaudio CasperMD5CheckResult: skip Date: Tue Jul 21 01:09:19 2020 ErrorMessage: installed linux-image-5.4.0-40-generic package pre-removal script subprocess returned error exit status 1 InstallationDate: Installed on 2020-05-31 (50 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Hewlett-Packard HP Notebook ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: grub-pc 2.04-1ubuntu26 SourcePackage: linux Title: package linux-image-5.4.0-40-generic 5.4.0-40.44 failed to install/upgrade: installed linux-image-5.4.0-40-generic package pre-removal script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/24/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80C2 dmi.board.vendor: Hewlett-Packard dmi.board.version: 96.02 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.02:bd03/24/2015:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn80C2:rvr96.02:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: M9H15EA#ABV dmi.product.version: Type1ProductConfigId dmi.sys.vendor: Hewlett-Packard ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1888341 Title: package linux-image-5.4.0-40-generic 5.4.0-40.44 failed to install/upgrade: installed linux-image-5.4.0-40-generic package pre- removal script subprocess returned error exit status 1 Status in linux package in Ubuntu: New Bug description: error ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: qnx4 hfsplus hfs minix ntfs jfs nls_utf8 rfcomm lkp_Ubuntu_5_4_0_40_44_generic_69 bnep snd_hda_codec_realtek snd_hda_codec_hdmi snd_hda_codec_generic ledtrig_audio amdgpu snd_hda_intel snd_intel_dspcfg uvcvideo snd_hda_codec snd_hda_core amd_iommu_v2 gpu_sched x86_pkg_temp_thermal mei_hdcp intel_powerclamp coretemp intel_rapl_msr videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 btusb videobuf2_common btrtl btbcm btintel bluetooth videodev i915 wl radeon mc intel_cstate intel_rapl_perf mei_me cfg80211 mei hp_wmi sparse_keymap processor_thermal_device intel_rapl_common int340x_thermal_zone intel_soc_dts_iosf wmi_bmof mac_hid intel_pch_thermal int3400_thermal hp_wireless acpi_thermal_rel i2c_i801 r8169 lpc_ich realtek wmi i2c_hid ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tanzeel1688 F pulseaudio /dev/snd/controlC0: tanzeel1688 F pulseaudio CasperMD5CheckResult: skip Date: Tue Jul 21 01:09:19 2020 ErrorMessage: installed linux-image-5.4.0-40-generic package pre-removal script subprocess returned error exit status 1 InstallationDate: Installed on 2020-05-31 (50
[Kernel-packages] [Bug 1888334] Re: tm-resched-dscr from powerpc in ubuntu_kernel_selftests failed on E
Since this 5.3.0-64.58 is a respin for 5.3.0-63.57, I think we can call this a potential regression. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Eoan) Importance: Undecided Status: New ** Summary changed: - tm-resched-dscr from powerpc in ubuntu_kernel_selftests failed on E + [Potential Regression] tm-resched-dscr from powerpc in ubuntu_kernel_selftests failed on E -- 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/1888334 Title: [Potential Regression] tm-resched-dscr from powerpc in ubuntu_kernel_selftests failed on E Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: New Status in linux source package in Eoan: New Bug description: Issue found on 5.3.0-64.58 with P8 node modoc (skipped with P9 node) # selftests: powerpc/tm: tm-resched-dscr # test: tm_resched_dscr # tags: git_version:unknown # Binding to cpu 8 # main test running as pid 142637 # Check DSCR TM context switch: FAIL # failure: tm_resched_dscr not ok 1 selftests: powerpc/tm: tm-resched-dscr # exit=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1888334/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888324] 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 1888324 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: eoan -- 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/1888324 Title: Kernel oops in kvm host if using vhost_net in guest (18.04 HWE) Status in linux package in Ubuntu: Incomplete Bug description: If I run a KVM guest with a network using the vhost_net driver, I get a kernel oops with a NULL reference error. It happens randomly. I run a GPU passthrough setup with windows 10 but I can leave that up 24/7 as I am passing through a raw ethernet card. Any other virtual machine using the vhost_net driver will result in a crash in 12 hours or less. I've attached the dmesg that I captured with kdump. I am not sure when this bug was introduced. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888324/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888339] Re: ptrace-tar from powerpc in ubuntu_kernel_selftests failed on E
Since this 5.3.0-64.58 is a respin for 5.3.0-63.57, I think we can call this a potential regression. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Eoan) Importance: Undecided Status: New ** Summary changed: - ptrace-tar from powerpc in ubuntu_kernel_selftests failed on E + [Potential Regression] ptrace-tar from powerpc in ubuntu_kernel_selftests failed on E -- 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/1888339 Title: [Potential Regression] ptrace-tar from powerpc in ubuntu_kernel_selftests failed on E Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: New Status in linux source package in Eoan: New Bug description: Issue found on 5.3.0-64.58 with P8 node modoc (passed with P9 node) # selftests: powerpc/ptrace: ptrace-tar # test: ptrace_tar # tags: git_version:f21e446-dirty # [User Write (Running)] TAR: 10 PPR: 4 DSCR: 100 # [User Read (Running)] TAR: 20 PPR: 8 DSCR: 0 # [Ptrace Read (Running)]TAR: 10 PPR: 4 DSCR: 100 # [Ptrace Write (Running)] TAR: 20 PPR: 8 DSCR: 200 # failure: ptrace_tar not ok 4 selftests: powerpc/ptrace: ptrace-tar # exit=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1888339/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888332] Re: dscr_inherit_exec_test from powerpc in ubuntu_kernel_selftests failed on E
Since this 5.3.0-64.58 is a respin for 5.3.0-63.57, I think we can call this a potential regression. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Eoan) Importance: Undecided Status: New ** Summary changed: - dscr_inherit_exec_test from powerpc in ubuntu_kernel_selftests failed on E + [Potential Regression] dscr_inherit_exec_test from powerpc in ubuntu_kernel_selftests failed on E -- 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/1888332 Title: [Potential Regression] dscr_inherit_exec_test from powerpc in ubuntu_kernel_selftests failed on E Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: New Status in linux source package in Eoan: New Bug description: Issue found on 5.3.0-64.58 with P8 node modoc (passed with P9 node) # selftests: powerpc/dscr: dscr_inherit_exec_test # test: dscr_inherit_exec_test # tags: git_version:unknown # Parent DSCR 1 was not inherited over exec (kernel value) # Child didn't exit cleanly # failure: dscr_inherit_exec_test not ok 5 selftests: powerpc/dscr: dscr_inherit_exec_test # exit=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1888332/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
Upload debdiff for groovy, please help to review this patch, in the meantime, I'm running the stress test with this package in a nvidia platform, let's see how it goes. ** Patch added: "grub2_2.04-1ubuntu26_2.04-1ubuntu27.debdiff" https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1845801/+attachment/5394535/+files/grub2_2.04-1ubuntu26_2.04-1ubuntu27.debdiff ** Description changed: I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-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 435.21 Sun Aug 25 08:17:57 CDT 2019 - GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) + NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 + GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: - NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) -Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] + NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) + Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A67 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1 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.5+git20190820-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 + + PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1845801 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in OEM Priority Project: Confirmed Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in grub2 package in
[Kernel-packages] [Bug 1888341] Re: package linux-image-5.4.0-40-generic 5.4.0-40.44 failed to install/upgrade: installed linux-image-5.4.0-40-generic package pre-removal script subprocess returned er
** Tags removed: need-duplicate-check -- 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/1888341 Title: package linux-image-5.4.0-40-generic 5.4.0-40.44 failed to install/upgrade: installed linux-image-5.4.0-40-generic package pre- removal script subprocess returned error exit status 1 Status in linux package in Ubuntu: New Bug description: error ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: qnx4 hfsplus hfs minix ntfs jfs nls_utf8 rfcomm lkp_Ubuntu_5_4_0_40_44_generic_69 bnep snd_hda_codec_realtek snd_hda_codec_hdmi snd_hda_codec_generic ledtrig_audio amdgpu snd_hda_intel snd_intel_dspcfg uvcvideo snd_hda_codec snd_hda_core amd_iommu_v2 gpu_sched x86_pkg_temp_thermal mei_hdcp intel_powerclamp coretemp intel_rapl_msr videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 btusb videobuf2_common btrtl btbcm btintel bluetooth videodev i915 wl radeon mc intel_cstate intel_rapl_perf mei_me cfg80211 mei hp_wmi sparse_keymap processor_thermal_device intel_rapl_common int340x_thermal_zone intel_soc_dts_iosf wmi_bmof mac_hid intel_pch_thermal int3400_thermal hp_wireless acpi_thermal_rel i2c_i801 r8169 lpc_ich realtek wmi i2c_hid ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tanzeel1688 F pulseaudio /dev/snd/controlC0: tanzeel1688 F pulseaudio CasperMD5CheckResult: skip Date: Tue Jul 21 01:09:19 2020 ErrorMessage: installed linux-image-5.4.0-40-generic package pre-removal script subprocess returned error exit status 1 InstallationDate: Installed on 2020-05-31 (50 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Hewlett-Packard HP Notebook ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: grub-pc 2.04-1ubuntu26 SourcePackage: linux Title: package linux-image-5.4.0-40-generic 5.4.0-40.44 failed to install/upgrade: installed linux-image-5.4.0-40-generic package pre-removal script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/24/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80C2 dmi.board.vendor: Hewlett-Packard dmi.board.version: 96.02 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.02:bd03/24/2015:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn80C2:rvr96.02:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: M9H15EA#ABV dmi.product.version: Type1ProductConfigId dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888341/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1873961] Re: tc filter show tcp_flags wrong mask value
Hi David, since Ubuntu 18.04 / bionic is a versions that is already released and in service, we cannot simply bump it's iproute2 version to the latest from upstream (this is only possible for Ubuntu releases that are in development - aot 20.10). Instead we need to follow the pretty strict SRU process (https://wiki.ubuntu.com/StableReleaseUpdates) and according to this we would need the patch/commit (or in this case the minimal list of patches/commits) that fix a certain issue. Hence the approach in the bug description - listing the needed commits - is the right way. But out engineer assumes in comment #5 (https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1873961/comments/5) that the pre-req. patch is probably a different one - and before going further we want you to confirm. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/1873961 Title: tc filter show tcp_flags wrong mask value Status in The Ubuntu-power-systems project: Triaged Status in iproute2 package in Ubuntu: Fix Released Status in iproute2 source package in Bionic: Triaged Bug description: ---Problem Description--- Problem Descriptions "tc" utility does not show correct TC rule's tcp_flags mask correctly in current "iproute2" package shipped on Genesis. # dpkg -l |grep iproute2 ii iproute2 4.15.0-2ubuntu1 ppc64el networking and traffic control tools ---Steps to Reproduce--- Steps to reproduce the problem: 1) Add a tc rule to the testing VF (i.e. p0v2_r): # tc filter add dev p0v2 protocol ip parent : pref 5 chain 1 handle 0x1 flower src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff ip_proto tcp tcp_flags 2 skip_sw action mirred egress redirect dev p0v0_r 2) Validate the added TC rule: # tc filter show dev p0v2_r root filter protocol ip pref 5 flower chain 1 filter protocol ip pref 5 flower chain 1 handle 0x1 src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff eth_type ipv4 ip_proto tcp tcp_flags 22 /* <--- Wrong */ skip_sw in_hw action order 1: mirred (Egress Redirect to device p0v0_r) stolen 3) If we add the tcp_flags using explicit mask 0x7: # tc filter add dev p0v2 protocol ip parent : pref 5 chain 1 handle 0x1 flower src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff ip_proto tcp tcp_flags 0x2/7 skip_sw action mirred egress redirect dev p0v0_r After that, using "tc filter show dev p0v2_r root" to verify, we still see the same output (tcp_flags 22) as shown in 2) above, which is wrong. Userspace tool common name: tc The userspace tool has the following bit modes: 64-bit Userspace package: iproute2 == Fixes: There are 2 patches to fix the issue: patch 1: commit b85076cd74e77538918d35992b1a9cd17ff86af8 Author: Stephen Hemminger Date: Tue Sep 11 08:29:33 2018 -0700 lib: introduce print_nl Common pattern in iproute commands is to print a line seperator in non-json mode. Make that a simple function. /* This patch declares global variable "const char *_SL_ = "\n";" in lib/utils.c to be used by 2nd patch */ patch 2: commit e8bd395508cead5a81c2bebd9d3705a9e41ea8bc Author: Keara Leibovitz Date: Thu Jul 26 09:45:30 2018 -0400 tc: fix bugs for tcp_flags and ip_attr hex output Fix hex output for both the ip_attr and tcp_flags print functions. With the above 2 patches pull in, the new "tc" utility will show the correct tcp_flags mask: # tc filter show dev p0v2 root filter protocol ip pref 5 flower chain 1 filter protocol ip pref 5 flower chain 1 handle 0x1 src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff eth_type ipv4 ip_proto tcp tcp_flags 0x2/7 /* <--- Correct */ skip_sw in_hw action order 1: mirred (Egress Redirect to device p0v0_r) stolen This bug affects tc in Ubuntu 18.04.1 stock image. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1873961/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888324] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1888324/+attachment/5394546/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1888324 Title: Kernel oops in kvm host if using vhost_net in guest (18.04 HWE) Status in linux package in Ubuntu: Confirmed Bug description: If I run a KVM guest with a network using the vhost_net driver, I get a kernel oops with a NULL reference error. It happens randomly. I run a GPU passthrough setup with windows 10 but I can leave that up 24/7 as I am passing through a raw ethernet card. Any other virtual machine using the vhost_net driver will result in a crash in 12 hours or less. I've attached the dmesg that I captured with kdump. I am not sure when this bug was introduced. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: luke 3876 F pulseaudio /dev/snd/controlC1: luke 3876 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-10-30 (629 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic root=UUID=a5c9f5ef-18ed-4f8b-a213-2cec2e0bb4a5 ro iommu=1 amd_iommu=on kvm.ignore_msrs=1 kvm.report_ignored_msrs=0 kvm.allow_unsafe_assigned_interrupts=1 vfio_iommu_type1.allow_unsafe_interrupts=1 default_hugepagesz=1G hugepagesz=1G crashkernel=768M ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-62-generic N/A linux-backports-modules-5.3.0-62-generic N/A linux-firmware1.173.19 Tags: bionic Uname: Linux 5.3.0-62-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 08/27/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.70 dmi.board.name: X399 Professional Gaming dmi.board.vendor: ASRock dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.70:bd08/27/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX399ProfessionalGaming:rvr:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888324/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888324] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1888324/+attachment/5394550/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1888324 Title: Kernel oops in kvm host if using vhost_net in guest (18.04 HWE) Status in linux package in Ubuntu: Confirmed Bug description: If I run a KVM guest with a network using the vhost_net driver, I get a kernel oops with a NULL reference error. It happens randomly. I run a GPU passthrough setup with windows 10 but I can leave that up 24/7 as I am passing through a raw ethernet card. Any other virtual machine using the vhost_net driver will result in a crash in 12 hours or less. I've attached the dmesg that I captured with kdump. I am not sure when this bug was introduced. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: luke 3876 F pulseaudio /dev/snd/controlC1: luke 3876 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-10-30 (629 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic root=UUID=a5c9f5ef-18ed-4f8b-a213-2cec2e0bb4a5 ro iommu=1 amd_iommu=on kvm.ignore_msrs=1 kvm.report_ignored_msrs=0 kvm.allow_unsafe_assigned_interrupts=1 vfio_iommu_type1.allow_unsafe_interrupts=1 default_hugepagesz=1G hugepagesz=1G crashkernel=768M ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-62-generic N/A linux-backports-modules-5.3.0-62-generic N/A linux-firmware1.173.19 Tags: bionic Uname: Linux 5.3.0-62-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 08/27/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.70 dmi.board.name: X399 Professional Gaming dmi.board.vendor: ASRock dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.70:bd08/27/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX399ProfessionalGaming:rvr:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888324/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888324] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1888324/+attachment/5394545/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1888324 Title: Kernel oops in kvm host if using vhost_net in guest (18.04 HWE) Status in linux package in Ubuntu: Confirmed Bug description: If I run a KVM guest with a network using the vhost_net driver, I get a kernel oops with a NULL reference error. It happens randomly. I run a GPU passthrough setup with windows 10 but I can leave that up 24/7 as I am passing through a raw ethernet card. Any other virtual machine using the vhost_net driver will result in a crash in 12 hours or less. I've attached the dmesg that I captured with kdump. I am not sure when this bug was introduced. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: luke 3876 F pulseaudio /dev/snd/controlC1: luke 3876 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-10-30 (629 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic root=UUID=a5c9f5ef-18ed-4f8b-a213-2cec2e0bb4a5 ro iommu=1 amd_iommu=on kvm.ignore_msrs=1 kvm.report_ignored_msrs=0 kvm.allow_unsafe_assigned_interrupts=1 vfio_iommu_type1.allow_unsafe_interrupts=1 default_hugepagesz=1G hugepagesz=1G crashkernel=768M ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-62-generic N/A linux-backports-modules-5.3.0-62-generic N/A linux-firmware1.173.19 Tags: bionic Uname: Linux 5.3.0-62-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 08/27/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.70 dmi.board.name: X399 Professional Gaming dmi.board.vendor: ASRock dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.70:bd08/27/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX399ProfessionalGaming:rvr:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888324/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888324] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1888324/+attachment/5394551/+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/1888324 Title: Kernel oops in kvm host if using vhost_net in guest (18.04 HWE) Status in linux package in Ubuntu: Confirmed Bug description: If I run a KVM guest with a network using the vhost_net driver, I get a kernel oops with a NULL reference error. It happens randomly. I run a GPU passthrough setup with windows 10 but I can leave that up 24/7 as I am passing through a raw ethernet card. Any other virtual machine using the vhost_net driver will result in a crash in 12 hours or less. I've attached the dmesg that I captured with kdump. I am not sure when this bug was introduced. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: luke 3876 F pulseaudio /dev/snd/controlC1: luke 3876 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-10-30 (629 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic root=UUID=a5c9f5ef-18ed-4f8b-a213-2cec2e0bb4a5 ro iommu=1 amd_iommu=on kvm.ignore_msrs=1 kvm.report_ignored_msrs=0 kvm.allow_unsafe_assigned_interrupts=1 vfio_iommu_type1.allow_unsafe_interrupts=1 default_hugepagesz=1G hugepagesz=1G crashkernel=768M ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-62-generic N/A linux-backports-modules-5.3.0-62-generic N/A linux-firmware1.173.19 Tags: bionic Uname: Linux 5.3.0-62-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 08/27/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.70 dmi.board.name: X399 Professional Gaming dmi.board.vendor: ASRock dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.70:bd08/27/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX399ProfessionalGaming:rvr:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888324/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888324] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1888324/+attachment/5394552/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1888324 Title: Kernel oops in kvm host if using vhost_net in guest (18.04 HWE) Status in linux package in Ubuntu: Confirmed Bug description: If I run a KVM guest with a network using the vhost_net driver, I get a kernel oops with a NULL reference error. It happens randomly. I run a GPU passthrough setup with windows 10 but I can leave that up 24/7 as I am passing through a raw ethernet card. Any other virtual machine using the vhost_net driver will result in a crash in 12 hours or less. I've attached the dmesg that I captured with kdump. I am not sure when this bug was introduced. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: luke 3876 F pulseaudio /dev/snd/controlC1: luke 3876 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-10-30 (629 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic root=UUID=a5c9f5ef-18ed-4f8b-a213-2cec2e0bb4a5 ro iommu=1 amd_iommu=on kvm.ignore_msrs=1 kvm.report_ignored_msrs=0 kvm.allow_unsafe_assigned_interrupts=1 vfio_iommu_type1.allow_unsafe_interrupts=1 default_hugepagesz=1G hugepagesz=1G crashkernel=768M ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-62-generic N/A linux-backports-modules-5.3.0-62-generic N/A linux-firmware1.173.19 Tags: bionic Uname: Linux 5.3.0-62-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 08/27/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.70 dmi.board.name: X399 Professional Gaming dmi.board.vendor: ASRock dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.70:bd08/27/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX399ProfessionalGaming:rvr:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888324/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888324] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1888324/+attachment/5394542/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1888324 Title: Kernel oops in kvm host if using vhost_net in guest (18.04 HWE) Status in linux package in Ubuntu: Confirmed Bug description: If I run a KVM guest with a network using the vhost_net driver, I get a kernel oops with a NULL reference error. It happens randomly. I run a GPU passthrough setup with windows 10 but I can leave that up 24/7 as I am passing through a raw ethernet card. Any other virtual machine using the vhost_net driver will result in a crash in 12 hours or less. I've attached the dmesg that I captured with kdump. I am not sure when this bug was introduced. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: luke 3876 F pulseaudio /dev/snd/controlC1: luke 3876 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-10-30 (629 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic root=UUID=a5c9f5ef-18ed-4f8b-a213-2cec2e0bb4a5 ro iommu=1 amd_iommu=on kvm.ignore_msrs=1 kvm.report_ignored_msrs=0 kvm.allow_unsafe_assigned_interrupts=1 vfio_iommu_type1.allow_unsafe_interrupts=1 default_hugepagesz=1G hugepagesz=1G crashkernel=768M ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-62-generic N/A linux-backports-modules-5.3.0-62-generic N/A linux-firmware1.173.19 Tags: bionic Uname: Linux 5.3.0-62-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 08/27/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.70 dmi.board.name: X399 Professional Gaming dmi.board.vendor: ASRock dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.70:bd08/27/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX399ProfessionalGaming:rvr:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888324/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888324] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1888324/+attachment/5394541/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1888324 Title: Kernel oops in kvm host if using vhost_net in guest (18.04 HWE) Status in linux package in Ubuntu: Confirmed Bug description: If I run a KVM guest with a network using the vhost_net driver, I get a kernel oops with a NULL reference error. It happens randomly. I run a GPU passthrough setup with windows 10 but I can leave that up 24/7 as I am passing through a raw ethernet card. Any other virtual machine using the vhost_net driver will result in a crash in 12 hours or less. I've attached the dmesg that I captured with kdump. I am not sure when this bug was introduced. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: luke 3876 F pulseaudio /dev/snd/controlC1: luke 3876 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-10-30 (629 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic root=UUID=a5c9f5ef-18ed-4f8b-a213-2cec2e0bb4a5 ro iommu=1 amd_iommu=on kvm.ignore_msrs=1 kvm.report_ignored_msrs=0 kvm.allow_unsafe_assigned_interrupts=1 vfio_iommu_type1.allow_unsafe_interrupts=1 default_hugepagesz=1G hugepagesz=1G crashkernel=768M ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-62-generic N/A linux-backports-modules-5.3.0-62-generic N/A linux-firmware1.173.19 Tags: bionic Uname: Linux 5.3.0-62-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 08/27/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.70 dmi.board.name: X399 Professional Gaming dmi.board.vendor: ASRock dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.70:bd08/27/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX399ProfessionalGaming:rvr:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888324/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888324] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1888324/+attachment/5394547/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1888324 Title: Kernel oops in kvm host if using vhost_net in guest (18.04 HWE) Status in linux package in Ubuntu: Confirmed Bug description: If I run a KVM guest with a network using the vhost_net driver, I get a kernel oops with a NULL reference error. It happens randomly. I run a GPU passthrough setup with windows 10 but I can leave that up 24/7 as I am passing through a raw ethernet card. Any other virtual machine using the vhost_net driver will result in a crash in 12 hours or less. I've attached the dmesg that I captured with kdump. I am not sure when this bug was introduced. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: luke 3876 F pulseaudio /dev/snd/controlC1: luke 3876 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-10-30 (629 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic root=UUID=a5c9f5ef-18ed-4f8b-a213-2cec2e0bb4a5 ro iommu=1 amd_iommu=on kvm.ignore_msrs=1 kvm.report_ignored_msrs=0 kvm.allow_unsafe_assigned_interrupts=1 vfio_iommu_type1.allow_unsafe_interrupts=1 default_hugepagesz=1G hugepagesz=1G crashkernel=768M ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-62-generic N/A linux-backports-modules-5.3.0-62-generic N/A linux-firmware1.173.19 Tags: bionic Uname: Linux 5.3.0-62-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 08/27/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.70 dmi.board.name: X399 Professional Gaming dmi.board.vendor: ASRock dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.70:bd08/27/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX399ProfessionalGaming:rvr:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888324/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888324] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1888324/+attachment/5394548/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1888324 Title: Kernel oops in kvm host if using vhost_net in guest (18.04 HWE) Status in linux package in Ubuntu: Confirmed Bug description: If I run a KVM guest with a network using the vhost_net driver, I get a kernel oops with a NULL reference error. It happens randomly. I run a GPU passthrough setup with windows 10 but I can leave that up 24/7 as I am passing through a raw ethernet card. Any other virtual machine using the vhost_net driver will result in a crash in 12 hours or less. I've attached the dmesg that I captured with kdump. I am not sure when this bug was introduced. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: luke 3876 F pulseaudio /dev/snd/controlC1: luke 3876 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-10-30 (629 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic root=UUID=a5c9f5ef-18ed-4f8b-a213-2cec2e0bb4a5 ro iommu=1 amd_iommu=on kvm.ignore_msrs=1 kvm.report_ignored_msrs=0 kvm.allow_unsafe_assigned_interrupts=1 vfio_iommu_type1.allow_unsafe_interrupts=1 default_hugepagesz=1G hugepagesz=1G crashkernel=768M ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-62-generic N/A linux-backports-modules-5.3.0-62-generic N/A linux-firmware1.173.19 Tags: bionic Uname: Linux 5.3.0-62-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 08/27/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.70 dmi.board.name: X399 Professional Gaming dmi.board.vendor: ASRock dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.70:bd08/27/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX399ProfessionalGaming:rvr:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888324/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888324] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1888324/+attachment/5394543/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1888324 Title: Kernel oops in kvm host if using vhost_net in guest (18.04 HWE) Status in linux package in Ubuntu: Confirmed Bug description: If I run a KVM guest with a network using the vhost_net driver, I get a kernel oops with a NULL reference error. It happens randomly. I run a GPU passthrough setup with windows 10 but I can leave that up 24/7 as I am passing through a raw ethernet card. Any other virtual machine using the vhost_net driver will result in a crash in 12 hours or less. I've attached the dmesg that I captured with kdump. I am not sure when this bug was introduced. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: luke 3876 F pulseaudio /dev/snd/controlC1: luke 3876 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-10-30 (629 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic root=UUID=a5c9f5ef-18ed-4f8b-a213-2cec2e0bb4a5 ro iommu=1 amd_iommu=on kvm.ignore_msrs=1 kvm.report_ignored_msrs=0 kvm.allow_unsafe_assigned_interrupts=1 vfio_iommu_type1.allow_unsafe_interrupts=1 default_hugepagesz=1G hugepagesz=1G crashkernel=768M ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-62-generic N/A linux-backports-modules-5.3.0-62-generic N/A linux-firmware1.173.19 Tags: bionic Uname: Linux 5.3.0-62-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 08/27/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.70 dmi.board.name: X399 Professional Gaming dmi.board.vendor: ASRock dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.70:bd08/27/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX399ProfessionalGaming:rvr:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888324/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888324] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1888324/+attachment/5394544/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1888324 Title: Kernel oops in kvm host if using vhost_net in guest (18.04 HWE) Status in linux package in Ubuntu: Confirmed Bug description: If I run a KVM guest with a network using the vhost_net driver, I get a kernel oops with a NULL reference error. It happens randomly. I run a GPU passthrough setup with windows 10 but I can leave that up 24/7 as I am passing through a raw ethernet card. Any other virtual machine using the vhost_net driver will result in a crash in 12 hours or less. I've attached the dmesg that I captured with kdump. I am not sure when this bug was introduced. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: luke 3876 F pulseaudio /dev/snd/controlC1: luke 3876 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-10-30 (629 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic root=UUID=a5c9f5ef-18ed-4f8b-a213-2cec2e0bb4a5 ro iommu=1 amd_iommu=on kvm.ignore_msrs=1 kvm.report_ignored_msrs=0 kvm.allow_unsafe_assigned_interrupts=1 vfio_iommu_type1.allow_unsafe_interrupts=1 default_hugepagesz=1G hugepagesz=1G crashkernel=768M ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-62-generic N/A linux-backports-modules-5.3.0-62-generic N/A linux-firmware1.173.19 Tags: bionic Uname: Linux 5.3.0-62-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 08/27/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.70 dmi.board.name: X399 Professional Gaming dmi.board.vendor: ASRock dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.70:bd08/27/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX399ProfessionalGaming:rvr:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888324/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888324] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1888324/+attachment/5394549/+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/1888324 Title: Kernel oops in kvm host if using vhost_net in guest (18.04 HWE) Status in linux package in Ubuntu: Confirmed Bug description: If I run a KVM guest with a network using the vhost_net driver, I get a kernel oops with a NULL reference error. It happens randomly. I run a GPU passthrough setup with windows 10 but I can leave that up 24/7 as I am passing through a raw ethernet card. Any other virtual machine using the vhost_net driver will result in a crash in 12 hours or less. I've attached the dmesg that I captured with kdump. I am not sure when this bug was introduced. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: luke 3876 F pulseaudio /dev/snd/controlC1: luke 3876 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-10-30 (629 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic root=UUID=a5c9f5ef-18ed-4f8b-a213-2cec2e0bb4a5 ro iommu=1 amd_iommu=on kvm.ignore_msrs=1 kvm.report_ignored_msrs=0 kvm.allow_unsafe_assigned_interrupts=1 vfio_iommu_type1.allow_unsafe_interrupts=1 default_hugepagesz=1G hugepagesz=1G crashkernel=768M ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-62-generic N/A linux-backports-modules-5.3.0-62-generic N/A linux-firmware1.173.19 Tags: bionic Uname: Linux 5.3.0-62-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 08/27/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.70 dmi.board.name: X399 Professional Gaming dmi.board.vendor: ASRock dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.70:bd08/27/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX399ProfessionalGaming:rvr:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888324/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888324] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1888324/+attachment/5394553/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1888324 Title: Kernel oops in kvm host if using vhost_net in guest (18.04 HWE) Status in linux package in Ubuntu: Confirmed Bug description: If I run a KVM guest with a network using the vhost_net driver, I get a kernel oops with a NULL reference error. It happens randomly. I run a GPU passthrough setup with windows 10 but I can leave that up 24/7 as I am passing through a raw ethernet card. Any other virtual machine using the vhost_net driver will result in a crash in 12 hours or less. I've attached the dmesg that I captured with kdump. I am not sure when this bug was introduced. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: luke 3876 F pulseaudio /dev/snd/controlC1: luke 3876 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-10-30 (629 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic root=UUID=a5c9f5ef-18ed-4f8b-a213-2cec2e0bb4a5 ro iommu=1 amd_iommu=on kvm.ignore_msrs=1 kvm.report_ignored_msrs=0 kvm.allow_unsafe_assigned_interrupts=1 vfio_iommu_type1.allow_unsafe_interrupts=1 default_hugepagesz=1G hugepagesz=1G crashkernel=768M ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-62-generic N/A linux-backports-modules-5.3.0-62-generic N/A linux-firmware1.173.19 Tags: bionic Uname: Linux 5.3.0-62-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 08/27/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.70 dmi.board.name: X399 Professional Gaming dmi.board.vendor: ASRock dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.70:bd08/27/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX399ProfessionalGaming:rvr:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888324/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888324] Re: Kernel oops in kvm host if using vhost_net in guest (18.04 HWE)
apport information ** Tags added: apport-collected ** Description changed: - If I run a KVM guest with a network using the vhost_net driver, I get a - kernel oops with a NULL reference error. It happens randomly. I run a - GPU passthrough setup with windows 10 but I can leave that up 24/7 as I - am passing through a raw ethernet card. Any other virtual machine using - the vhost_net driver will result in a crash in 12 hours or less. I've - attached the dmesg that I captured with kdump. I am not sure when this - bug was introduced. + If I run a KVM guest with a network using the vhost_net driver, I get a kernel oops with a NULL reference error. It happens randomly. I run a GPU passthrough setup with windows 10 but I can leave that up 24/7 as I am passing through a raw ethernet card. Any other virtual machine using the vhost_net driver will result in a crash in 12 hours or less. I've attached the dmesg that I captured with kdump. I am not sure when this bug was introduced. + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.15 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: luke 3876 F pulseaudio + /dev/snd/controlC1: luke 3876 F pulseaudio + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2018-10-30 (629 days ago) + InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) + MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_AU.UTF-8 + SHELL=/bin/bash + ProcFB: 0 amdgpudrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic root=UUID=a5c9f5ef-18ed-4f8b-a213-2cec2e0bb4a5 ro iommu=1 amd_iommu=on kvm.ignore_msrs=1 kvm.report_ignored_msrs=0 kvm.allow_unsafe_assigned_interrupts=1 vfio_iommu_type1.allow_unsafe_interrupts=1 default_hugepagesz=1G hugepagesz=1G crashkernel=768M + ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18 + RelatedPackageVersions: + linux-restricted-modules-5.3.0-62-generic N/A + linux-backports-modules-5.3.0-62-generic N/A + linux-firmware1.173.19 + Tags: bionic + Uname: Linux 5.3.0-62-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dialout dip kvm libvirt lpadmin plugdev sambashare sudo vboxusers + _MarkForUpload: True + dmi.bios.date: 08/27/2019 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: P3.70 + dmi.board.name: X399 Professional Gaming + dmi.board.vendor: ASRock + dmi.chassis.asset.tag: Default string + dmi.chassis.type: 3 + dmi.chassis.vendor: Default string + dmi.chassis.version: Default string + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.70:bd08/27/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX399ProfessionalGaming:rvr:cvnDefaultstring:ct3:cvrDefaultstring: + dmi.product.family: To Be Filled By O.E.M. + dmi.product.name: To Be Filled By O.E.M. + dmi.product.sku: To Be Filled By O.E.M. + dmi.product.version: To Be Filled By O.E.M. + dmi.sys.vendor: To Be Filled By O.E.M. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1888324/+attachment/5394540/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1888324 Title: Kernel oops in kvm host if using vhost_net in guest (18.04 HWE) Status in linux package in Ubuntu: Confirmed Bug description: If I run a KVM guest with a network using the vhost_net driver, I get a kernel oops with a NULL reference error. It happens randomly. I run a GPU passthrough setup with windows 10 but I can leave that up 24/7 as I am passing through a raw ethernet card. Any other virtual machine using the vhost_net driver will result in a crash in 12 hours or less. I've attached the dmesg that I captured with kdump. I am not sure when this bug was introduced. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: luke 3876 F pulseaudio /dev/snd/controlC1: luke 3876 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-10-30 (629 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic root=UUID=a5c9f5ef-18ed-4f8b-a213-2cec2e0bb4a5 ro iommu=1 amd_iommu=on kvm.ignore_msrs=1 kvm.report_ignored_msrs=0
[Kernel-packages] [Bug 1887910] Re: [bionic]blutoothd segfault when you cancel the keyboard pairing during the dialog for pairing code
Sorry, the debugging and debdiff was done on the target machine so that the email ID was missed. This attached new debdiff also included the patch and lp number information in the changelog. And also updated the truncated description. ** Patch added: "bluez_5.48-0ubuntu3.5.debdiff" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1887910/+attachment/5394261/+files/bluez_5.48-0ubuntu3.5.debdiff -- 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/1887910 Title: [bionic]blutoothd segfault when you cancel the keyboard pairing during the dialog for pairing code Status in OEM Priority Project: In Progress Status in bluez package in Ubuntu: Fix Released Status in bluez source package in Bionic: In Progress Status in bluez source package in Eoan: Fix Released Status in bluez source package in Focal: Fix Released Status in bluez source package in Groovy: Fix Released Bug description: [Impact] * only impact Bionic machines because series after Bionic already included this patch. [Test Case] 1. pair bluetooth keyboard 2. see the dialog asking user input the code for pairing. 3. press "esc" to cancel it. 4. the bluetooth should still work to pair another bluetooth device. [Regression Potential] * low, because the same patch from upstream is already there on Groovy, Focal and Eoan. [Other Info] * NO. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1887910/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887910] Re: [bionic]blutoothd segfault when you cancel the keyboard pairing during the dialog for pairing code
** Description changed: [Impact] - * only impact Bionic machines because series after Bionic already + * only impact Bionic machines because series after Bionic already included this patch. [Test Case] - 1. pair bluetooth keyboard - 2. see the dialog asking user input the code for pairing. - 3. press "esc" to cancel it. - 4. the bluetooth should still work to pair another bluetooth device. + 1. pair bluetooth keyboard + 2. see the dialog asking user input the code for pairing. + 3. press "esc" to cancel it. + 4. the bluetooth should still work to pair another bluetooth device. [Regression Potential] - * low, becuase + * low, because the same patch from upstream is already there on Groovy, + Focal and Eoan. [Other Info] - * NO. + * NO. -- 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/1887910 Title: [bionic]blutoothd segfault when you cancel the keyboard pairing during the dialog for pairing code Status in OEM Priority Project: In Progress Status in bluez package in Ubuntu: Fix Released Status in bluez source package in Bionic: In Progress Status in bluez source package in Eoan: Fix Released Status in bluez source package in Focal: Fix Released Status in bluez source package in Groovy: Fix Released Bug description: [Impact] * only impact Bionic machines because series after Bionic already included this patch. [Test Case] 1. pair bluetooth keyboard 2. see the dialog asking user input the code for pairing. 3. press "esc" to cancel it. 4. the bluetooth should still work to pair another bluetooth device. [Regression Potential] * low, because the same patch from upstream is already there on Groovy, Focal and Eoan. [Other Info] * NO. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1887910/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881813] Re: [qxl] Desktop freezes 20.04
I did experience a complete lock of my system on the latest kernel and it was worse then before, in a way that I was not able even to ssh to my VM at all :( -- 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/1881813 Title: [qxl] Desktop freezes 20.04 Status in linux package in Ubuntu: Confirmed Bug description: Not too much info yet, will add apport report, but see it very often on 20.04 (upgraded from 18.04) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2018-05-07 (759 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: gnome-shell 3.36.1-5ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-24 (40 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2018-05-07 (759 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: gnome-shell 3.36.1-5ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1 Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-24 (40 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: yuriw 1143 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2018-05-07 (764 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IwConfig: ens8 no wireless extensions. lono wireless extensions. ens3 no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 qxldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=2b5969aa-16c5-43c7-9a83-1c75e5e19363 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 RfKill: Tags: focal Uname: Linux 5.4.0-33-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-24 (46 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881813/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
