[Kernel-packages] [Bug 1863116] Re: debian/rules editconfigs does not work on s390x to change s390x only configs
** Changed in: linux (Ubuntu Focal) Status: Triaged => In Progress ** Changed in: ubuntu-z-systems Status: Confirmed => 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/1863116 Title: debian/rules editconfigs does not work on s390x to change s390x only configs Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: In Progress Status in linux source package in Groovy: Fix Released Bug description: SRU Justification: == [Impact] * With focal (and even eoan) it is no longer possible to run the updateconfigs Debian build rule (needed in case of kernel option updates) on all supported arhitectures. * Changes upstream led to the fact cross platform functions are now triggered in case the config is changed, but amd64 is the only platform that has all needed crossbuild components to satisfy this. * Hence one can still run updateconfigs on amd64 and proceed with the compile on the target platform. * With bionic and earlier this was possible on all supported target platforms; now it only works on amd64. * But it's not always the case that people who work on Ubuntu for non- amd64 have an Ubuntu amd64 on top, nor would such a requirement be acceptable. [Fix] * Patch: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1863116/+attachment/5397080/+files/0001 -UBUNTU-Packaging-kernelconfig-only-update-edit-confi.patch [Test Case] * Setup an Ubuntu 20.04 on a platform other than amd64 (like in my case s390x) and install all packages needed for a kernel build. * 'git clone' or 'pull-lp-source' the kernel sources to that system (e.g. focal). * Change a kernel config option and run clean (fakeroot debian/rules clean), updateconfigs (fakeroot debian/rules updateconfigs) followed by a build (like: fakeroot debian/rules binary-headers binary-generic binary-perarch). * Without the patch the build will fail with error messages similar to these: scripts/Kconfig.include:35: compiler 'x86_64-linux-gnu-gcc' not found make[3]: *** [../scripts/kconfig/Makefile:73: syncconfig] Error 1 make[2]: *** [/home/ubuntu/linux-5.4-5.4.0/Makefile:594: syncconfig] Error 2 make[2]: Leaving directory '/home/ubuntu/linux-5.4-5.4.0/build' make[1]: *** [Makefile:179: sub-make] Error 2 make[1]: Leaving directory '/home/ubuntu/linux-5.4-5.4.0' make: *** [debian/rules.d/1-maintainer.mk:44: editconfigs] Error 2 * Doing the same on a non-amd64 with the patch in place (or on amd64 even w/o the patch), the build will succeed. [Regression Potential] * The regression risk is moderate since it's build time problem (not at kernel run time). * But anyway in case this patch is broken, kernel builds may be screwed up entirely, * but that is very unlikely since the modifications are limited to /debian/scripts/misc/kernelconfig. * Hence issues in kernelconfig could occur and even break updateconfigs on amd64. * But the patch was successully tested on different architectures with focal. [Other] * Patch need to be applied to focal and higher (hence incl. groovy). __ On s390x pull-lp-source linux-5.4 cd linux-* fakeroot ./debian/rules clean ./debian/rules editconfig dh_testdir; /bin/bash -e debian/scripts/misc/kernelconfig editconfigs Do you want to edit config: amd64/config.flavour.generic? [Y/n] n ... scripts/Kconfig.include:35: compiler 'x86_64-linux-gnu-gcc' not found make[3]: *** [../scripts/kconfig/Makefile:73: syncconfig] Error 1 make[2]: *** [/home/ubuntu/linux-5.4-5.4.0/Makefile:594: syncconfig] Error 2 make[2]: Leaving directory '/home/ubuntu/linux-5.4-5.4.0/build' make[1]: *** [Makefile:179: sub-make] Error 2 make[1]: Leaving directory '/home/ubuntu/linux-5.4-5.4.0' make: *** [debian/rules.d/1-maintainer.mk:44: editconfigs] Error 2 And indeed i do not have x86_64-linux-gnu-gcc crosscompiler available to build on s390x for amd64, and also I don't want to touch amd64 configs. Only s390x ones. As a user, I should be able to rebuild ports architecture kernel with tweaked config for testing, self-hosted without cross-compilers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1863116/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849825] Re: cpuset_inherit in controllers from ubuntu_ltp failed on D/E s390x LPAR
With Disco / Eoan EOL, and the fact that this test passed on Bionic / Focal LPAR with bug 1897531 fixed. I will close this bug. ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid ** Changed in: ubuntu-kernel-tests Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1849825 Title: cpuset_inherit in controllers from ubuntu_ltp failed on D/E s390x LPAR Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Disco: Won't Fix Bug description: startup='Thu Oct 24 09:48:22 2019' cpuset_inherit 1 TPASS: cpus: Inherited information is right! cpuset_inherit 3 TFAIL: cpus: Test result - 0 Expected string - "EMPTY" cpuset_inherit 5 TFAIL: cpus: Test result - 0-3 Expected string - "EMPTY" cpuset_inherit 7 TPASS: mems: Inherited information is right! cpuset_inherit 9 TFAIL: mems: Test result - 0 Expected string - "EMPTY" cpuset_inherit 11 TFAIL: mems: Test result - 0 Expected string - "EMPTY" cpuset_inherit 13 TPASS: cpu_exclusive: Inherited information is right! cpuset_inherit 15 TPASS: cpu_exclusive: Inherited information is right! cpuset_inherit 17 TPASS: mem_exclusive: Inherited information is right! cpuset_inherit 19 TPASS: mem_exclusive: Inherited information is right! cpuset_inherit 21 TPASS: mem_hardwall: Inherited information is right! cpuset_inherit 23 TPASS: mem_hardwall: Inherited information is right! cpuset_inherit 25 TPASS: memory_migrate: Inherited information is right! cpuset_inherit 27 TPASS: memory_migrate: Inherited information is right! cpuset_inherit 29 TPASS: memory_spread_page: Inherited information is right! cpuset_inherit 31 TPASS: memory_spread_page: Inherited information is right! cpuset_inherit 33 TPASS: memory_spread_slab: Inherited information is right! cpuset_inherit 35 TPASS: memory_spread_slab: Inherited information is right! cpuset_inherit 37 TPASS: sched_load_balance: Inherited information is right! cpuset_inherit 39 TPASS: sched_load_balance: Inherited information is right! cpuset_inherit 41 TPASS: sched_relax_domain_level: Inherited information is right! cpuset_inherit 43 TPASS: sched_relax_domain_level: Inherited information is right! cpuset_inherit 45 TPASS: sched_relax_domain_level: Inherited information is right! cpuset_inherit 47 TPASS: sched_relax_domain_level: Inherited information is right! cpuset_inherit 49 TPASS: sched_relax_domain_level: Inherited information is right! cpuset_inherit 51 TPASS: sched_relax_domain_level: Inherited information is right! cpuset_inherit 53 TPASS: sched_relax_domain_level: Inherited information is right! tag=cpuset_inherit stime=1571906902 dur=0 exit=exited stat=1 core=no cu=9 cs=31 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-33-generic 5.0.0-33.35 ProcVersionSignature: Ubuntu 5.0.0-33.35-generic 5.0.21 Uname: Linux 5.0.0-33-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': 'aplay' ApportVersion: 2.20.10-0ubuntu27.1 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDmesg: Date: Fri Oct 25 13:07:48 2019 HibernationDevice: RESUME=UUID=eae923f9-f5a4-41c0-b3e4-04786207dbaa IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcFB: ProcKernelCmdLine: root=UUID=1a6af794-84a9-4034-a213-39506b9bb91c crashkernel=196M BOOT_IMAGE=0 RelatedPackageVersions: linux-restricted-modules-5.0.0-33-generic N/A linux-backports-modules-5.0.0-33-generic N/A linux-firmware1.178.5 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1849825/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887490] Autopkgtest regression report (qemu/1:4.2-3ubuntu6.7)
All autopkgtests for the newly accepted qemu (1:4.2-3ubuntu6.7) for focal have finished running. The following regressions have been reported in tests triggered by the package: casper/1.445.1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#qemu [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1887490 Title: Add/Backport EPYC-v3 and EPYC-Rome CPU model Status in libvirt package in Ubuntu: Incomplete Status in linux package in Ubuntu: Invalid Status in qemu package in Ubuntu: Fix Released Status in libvirt source package in Focal: Incomplete Status in linux source package in Focal: Fix Committed Status in qemu source package in Focal: Fix Committed Bug description: ## Qemu SRU ## [Impact] * CPU definitions are added to qemu as these CPUs are known. And due to that over time are missing in former releases. * To really benefit from the new features of these chips they have to be known, therefore new type additions done by upstream should be backported if they generally apply and do not depend on SRU-critical changes. * This backports two upstream fixes that just add definitions (no control flow changes) [Test Case] * Probe qemu for the known CPU types (works on all HW) $ qemu-system-x86_64 -cpu ? | grep EPYC Focal without fix: x86 EPYC (alias configured by machine type) x86 EPYC-IBPB (alias of EPYC-v2) x86 EPYC-v1 AMD EPYC Processor x86 EPYC-v2 AMD EPYC Processor (with IBPB) Focal with fix also adds: x86 EPYC-Rome (alias configured by machine type) x86 EPYC-Rome-v1 AMD EPYC-Rome Processor x86 EPYC-v3 AMD EPYC Processor * Given such HW is available start a KVM guest using those new types Since we don't have libvirt support (yet) do so directly in qemu commandline like (bootloader is enough) $ qemu-system-x86_64 -cpu EPYC-Rome -machine pc-q35-focal,accel=kvm -nographic $ qemu-system-x86_64 -cpu EPYC-v3 -machine pc-q35-focal,accel=kvm -nographic [Regression Potential] * This adds new CPU types to the list of known CPUs defining their name and features. Generally the changes are contained to those new types and only active when selected - and usually only selectable on such new machines. Therefore not a lot should change for other users. One thing thou, if a user selected an unversioned type (which in this case only can be "EPYC") by default it will pick the latest subversion that applies. In this case the behavior will change and pick EPYC-v3 after the fix. But this is the whole purpose of versioned (stay as is) and unversioned (move with updates) CPU types - so that should be ok. The EPYC-Rome type didn't exist in Focal before, so it can't "change" for users. [Other Info] * Depends on the new kernel 5.4.0-49 or later (Currently in focal-proposed) --- Qemu in focal has already support for most (except amd-stibp) flags of this model. Please backport the following patches: https://github.com/qemu/qemu/commit/a16e8dbc043720abcb37fc7dca313e720b4e0f0c https://github.com/qemu/qemu/commit/143c30d4d346831a09e59e9af45afdca0331e819 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1887490/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1869134] Re: tcp_fastopen_backup_key.sh from net in ubuntu_kernel_selftests failed on Eoan LPAR
Didn't see this issue anymore, closing this bug.
Thanks for the fix.
** Changed in: ubuntu-kernel-tests
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1869134
Title:
tcp_fastopen_backup_key.sh from net in ubuntu_kernel_selftests failed
on Eoan LPAR
Status in ubuntu-kernel-tests:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Focal:
Fix Released
Status in linux source package in Groovy:
Fix Released
Bug description:
== SRU Justification Focal, Groovy ==
Running the tcp_fastopen_backup_key.sh from net in
ubuntu_kernel_selftests fails on big endian systems. This is a
regression that occurred because of commit 438ac88009bc ("net:
fastopen: robustness and endianness fixes for SipHash").
The test rotates TFO keys for ipv4/ipv6. It demonstrate how the
primary and backup TFO keys can be rotated while minimizing the number
of client cookies that are rejected. Due to an endianess issue, big
endian systems were getting endian reversed values, so the values
being from /proc/sys/net/ipv4/tcp_fastopen_key were reversed.
/proc/sys/net/ipv4/tcp_fastopen_key
== Fix ==
Upstream (linux-next) fix:
commit f19008e676366c44e9241af57f331b6c6edf9552
Author: Jason Baron
Date: Mon Aug 10 13:38:39 2020 -0400
tcp: correct read of TFO keys on big endian systems
== Test case ==
Run the kernel self tests tcp_fastopen_backup_key.sh. Currently this
generally fails on the last few test cases. With the fix the test
passes.
== Regression Potential ==
This fix touches the reading of the tcp fast open key proc interface
/proc/sys/net/ipv4/tcp_fastopen_key and the getsockopt
TCP_FASTOPEN_KEY interface so there is a potential for a regression
when accessing data from these read-only interfaces.
There is some data copying to keys using unaligned puts and memcpy()
so there is a potential that we may have data bounds errors causing
memory corruption.
Issue found on Eoan (5.3.0-42.34, 5.3.0-43.36) with all s390x instances:
- LPAR s2lp4
- zVM kernel03
- zKVM s2lp6g003
# selftests: net: tcp_fastopen_backup_key.sh
# PASS
# PASS
# PASS
# PASS
# PASS
# PASS
# PASS
# PASS
# PASS
# FAIL: TcpExtTCPFastOpenPassiveFail non-zero
not ok 30 selftests: net: tcp_fastopen_backup_key.sh # exit=1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1869134/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1871306] Re: No sound from internal card chtmax98090 - missing UCM2 files in alsa-ucm-conf 1.2.2, available in alsa-ucm-conf 1.2.3
@Gabriele, It will also upgrade the pulseaudio, but that pulseaudio will not bring any impact on your machine. Did you experience the same crackling and low volume with the alsa-ucm- conf 1.2.3 from Debian? If Debian version doesn't have this problem, Could you diff my testing version with Debian version? I didn't cherrypick/backport (0a8dd118f7b56372e3f0d6037fe91e4e8108f508 ucm2: use Include (Syntax 3)), since it will introduce huge changes on many many platforms and v1.2.3 doesn't have this commit yet. Maybe this commit could fix your problem (In theory, it will not fix your problem). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1871306 Title: No sound from internal card chtmax98090 - missing UCM2 files in alsa- ucm-conf 1.2.2, available in alsa-ucm-conf 1.2.3 Status in alsa-ucm-conf package in Ubuntu: Confirmed Bug description: Asus C300 (repurposed chromembook - bios flashed by Mr.Chromebox script) - Kubuntu Focal minimal fresh installation. The sound card is detected: I see it in the Plasma Widget, in pavucontrol, in alsamixer and it's not muted. I tried and add in /usr/share/alsa/ucm/chtmax98090/ the old style use case config files: no success. I tried and unmute speakers left and right in alsamixer: no success. I rapidly tested Ubuntu Mate Focal fresh install: I had exactly the same issue. I'm running on the same rig Debian Bullseye, kernel 5.4: sound card output and input are both working perfectly - I noticed that in Kubuntu alsamixer Kubuntu when I open it I have an entry HDA IntelPCH (the HDMI card), while in Debian I find Pulseaudio. I attach the alsa-info.sh output. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.17 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: KDE Date: Tue Apr 7 08:55:46 2020 InstallationDate: Installed on 2020-04-04 (2 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gabriel3937 F pulseaudio /dev/snd/controlC0: gabriel3937 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-04 (3 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:07dc Intel Corp. Bus 001 Device 003: ID 13d3:5657 IMC Networks USB2.0 UVC HD Webcam Bus 001 Device 002: ID 062a:4101 MosArt Semiconductor Corp. Wireless Keyboard/Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: GOOGLE Quawks Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=225cba91-c164-4882-95d4-4f9854a80fe9 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/17/2020 dmi.bios.vendor: coreboot dmi.bios.version: MrChromebox-4.11.2 dmi.board.name: Quawks dmi.board.vendor: GOOGLE dmi.board.version: 1.0 dmi.chassis.type: 9 dmi.chassis.vendor: GOOGLE dmi.modalias: dmi:bvncoreboot:bvrMrChromebox-4.11.2:bd03/17/2020:svnGOOGLE:pnQuawks:pvr1.0:rvnGOOGLE:rnQuawks:rvr1.0:cvnGOOGLE:ct9:cvr: dmi.product.name: Quawks dmi.product.version: 1.0 dmi.sys.vendor: GOOGLE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1871306/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894062] Re: Remove duplicated code in ip_defrag.sh of kselftests/net
This bug was fixed in the package linux - 5.8.0-20.21 --- linux (5.8.0-20.21) groovy; urgency=medium * groovy/linux: 5.8.0-20.21 -proposed tracker (LP: #1896668) * Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices (LP: #1853277) - i2c: core: Call i2c_acpi_install_space_handler() before i2c_acpi_register_devices() * Enable LTR for endpoints behind VMD (LP: #1896598) - SAUCE: PCI/ASPM: Enable LTR for endpoints behind VMD * Remove duplicated code in ip_defrag.sh of kselftests/net (LP: #1894062) - Revert "UBUNTU: SAUCE: selftests: net: ip_defrag: modprobe missing nf_defrag_ipv6 support" * [SRU] [Focal/OEM-5.6/Groovy]Fix AMD usb host controller lost after stress S3 (LP: #1893914) - SAUCE: xhci: workaround for S3 issue on AMD SNPS 3.0 xHC * debian/rules editconfigs does not work on s390x to change s390x only configs (LP: #1863116) - [Packaging] kernelconfig -- only update/edit configurations on architectures we have compiler support * [Ubuntu 20.10] zPCI DMA tables and bitmap leak on hard unplug (PCI Event 0x0304) (LP: #1896216) - s390/pci: fix leak of DMA tables on hard unplug * md: improve IO accounting (LP: #1891151) - md: improve io stats accounting * Groovy update: v5.8.10 upstream stable release (LP: #1896078) - ARM: OMAP2+: Fix an IS_ERR() vs NULL check in _get_pwrdm() - ARM: dts: logicpd-torpedo-baseboard: Fix broken audio - ARM: dts: logicpd-som-lv-baseboard: Fix broken audio - ARM: dts: logicpd-som-lv-baseboard: Fix missing video - regulator: push allocation in regulator_ena_gpio_request() out of lock - regulator: remove superfluous lock in regulator_resolve_coupling() - ARM: dts: socfpga: fix register entry for timer3 on Arria10 - ARM: dts: omap5: Fix DSI base address and clocks - ARM: dts: ls1021a: fix QuadSPI-memory reg range - ARM: dts: imx7ulp: Correct gpio ranges - arm64: dts: imx: Add missing imx8mm-beacon-kit.dtb to build - ARM: dts: imx7d-zii-rmu2: fix rgmii phy-mode for ksz9031 phy - RDMA/rtrs-srv: Replace device_register with device_initialize and device_add - RDMA/rxe: Fix memleak in rxe_mem_init_user - RDMA/rxe: Drop pointless checks in rxe_init_ports - RDMA/rxe: Fix panic when calling kmem_cache_create() - RDMA/bnxt_re: Do not report transparent vlan from QP1 - RDMA/bnxt_re: Fix the qp table indexing - RDMA/bnxt_re: Static NQ depth allocation - RDMA/bnxt_re: Fix driver crash on unaligned PSN entry address - RDMA/bnxt_re: Remove the qp from list only if the qp destroy succeeds - drm/sun4i: add missing put_device() call in sun8i_r40_tcon_tv_set_mux() - arm64: dts: imx8mq: Fix TMU interrupt property - drm/sun4i: Fix dsi dcs long write function - scsi: qla2xxx: Fix regression on sparc64 - scsi: libsas: Set data_dir as DMA_NONE if libata marks qc as NODATA - drm/virtio: fix unblank - RDMA/core: Fix unsafe linked list traversal after failing to allocate CQ - RDMA/core: Fix reported speed and width - scsi: megaraid_sas: Don't call disable_irq from process IRQ poll - scsi: mpt3sas: Don't call disable_irq from IRQ poll handler - soundwire: fix double free of dangling pointer - Revert "kbuild: use -flive-patching when CONFIG_LIVEPATCH is enabled" - interconnect: qcom: Fix small BW votes being truncated to zero - padata: fix possible padata_works_lock deadlock - drm/sun4i: Fix DE2 YVU handling - drm/sun4i: backend: Support alpha property on lowest plane - drm/sun4i: backend: Disable alpha on the lowest plane on the A20 - KVM: arm64: Update page shift if stage 2 block mapping not supported - ARM: dts: imx6sx: fix the pad QSPI1B_SCLK mux mode for uart3 - mmc: sdhci-acpi: Clear amd_sdhci_host on reset - mmc: sdhci-msm: Add retries when all tuning phases are found valid - spi: stm32: Rate-limit the 'Communication suspended' message - btrfs: fix NULL pointer dereference after failure to create snapshot - i2c: npcm7xx: Fix timeout calculation - block: restore a specific error code in bdev_del_partition - seccomp: don't leak memory when filter install races - nvme-fabrics: allow to queue requests for live queues - spi: stm32: fix pm_runtime_get_sync() error checking - block: Set same_page to false in __bio_try_merge_page if ret is false - RDMA/rtrs-srv: Set .release function for rtrs srv device during device init - IB/isert: Fix unaligned immediate-data handling - ARM: dts: bcm: HR2: Fixed QSPI compatible string - ARM: dts: NSP: Fixed QSPI compatible string - ARM: dts: BCM5301X: Fixed QSPI compatible string - arm64: dts: ns2: Fixed QSPI compatible string - KVM: nVMX: Fix the update value of nested load IA32_PERF_GLOBAL_CTRL control - KVM: x86: always allow writing '0' to MSR_KVM_ASYNC_PF_EN - ARC: HSDK: wireup perf irq - dmaengine: acpi: Put
[Kernel-packages] [Bug 1893914] Re: [SRU] [Focal/OEM-5.6/Groovy]Fix AMD usb host controller lost after stress S3
This bug was fixed in the package linux - 5.8.0-20.21 --- linux (5.8.0-20.21) groovy; urgency=medium * groovy/linux: 5.8.0-20.21 -proposed tracker (LP: #1896668) * Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices (LP: #1853277) - i2c: core: Call i2c_acpi_install_space_handler() before i2c_acpi_register_devices() * Enable LTR for endpoints behind VMD (LP: #1896598) - SAUCE: PCI/ASPM: Enable LTR for endpoints behind VMD * Remove duplicated code in ip_defrag.sh of kselftests/net (LP: #1894062) - Revert "UBUNTU: SAUCE: selftests: net: ip_defrag: modprobe missing nf_defrag_ipv6 support" * [SRU] [Focal/OEM-5.6/Groovy]Fix AMD usb host controller lost after stress S3 (LP: #1893914) - SAUCE: xhci: workaround for S3 issue on AMD SNPS 3.0 xHC * debian/rules editconfigs does not work on s390x to change s390x only configs (LP: #1863116) - [Packaging] kernelconfig -- only update/edit configurations on architectures we have compiler support * [Ubuntu 20.10] zPCI DMA tables and bitmap leak on hard unplug (PCI Event 0x0304) (LP: #1896216) - s390/pci: fix leak of DMA tables on hard unplug * md: improve IO accounting (LP: #1891151) - md: improve io stats accounting * Groovy update: v5.8.10 upstream stable release (LP: #1896078) - ARM: OMAP2+: Fix an IS_ERR() vs NULL check in _get_pwrdm() - ARM: dts: logicpd-torpedo-baseboard: Fix broken audio - ARM: dts: logicpd-som-lv-baseboard: Fix broken audio - ARM: dts: logicpd-som-lv-baseboard: Fix missing video - regulator: push allocation in regulator_ena_gpio_request() out of lock - regulator: remove superfluous lock in regulator_resolve_coupling() - ARM: dts: socfpga: fix register entry for timer3 on Arria10 - ARM: dts: omap5: Fix DSI base address and clocks - ARM: dts: ls1021a: fix QuadSPI-memory reg range - ARM: dts: imx7ulp: Correct gpio ranges - arm64: dts: imx: Add missing imx8mm-beacon-kit.dtb to build - ARM: dts: imx7d-zii-rmu2: fix rgmii phy-mode for ksz9031 phy - RDMA/rtrs-srv: Replace device_register with device_initialize and device_add - RDMA/rxe: Fix memleak in rxe_mem_init_user - RDMA/rxe: Drop pointless checks in rxe_init_ports - RDMA/rxe: Fix panic when calling kmem_cache_create() - RDMA/bnxt_re: Do not report transparent vlan from QP1 - RDMA/bnxt_re: Fix the qp table indexing - RDMA/bnxt_re: Static NQ depth allocation - RDMA/bnxt_re: Fix driver crash on unaligned PSN entry address - RDMA/bnxt_re: Remove the qp from list only if the qp destroy succeeds - drm/sun4i: add missing put_device() call in sun8i_r40_tcon_tv_set_mux() - arm64: dts: imx8mq: Fix TMU interrupt property - drm/sun4i: Fix dsi dcs long write function - scsi: qla2xxx: Fix regression on sparc64 - scsi: libsas: Set data_dir as DMA_NONE if libata marks qc as NODATA - drm/virtio: fix unblank - RDMA/core: Fix unsafe linked list traversal after failing to allocate CQ - RDMA/core: Fix reported speed and width - scsi: megaraid_sas: Don't call disable_irq from process IRQ poll - scsi: mpt3sas: Don't call disable_irq from IRQ poll handler - soundwire: fix double free of dangling pointer - Revert "kbuild: use -flive-patching when CONFIG_LIVEPATCH is enabled" - interconnect: qcom: Fix small BW votes being truncated to zero - padata: fix possible padata_works_lock deadlock - drm/sun4i: Fix DE2 YVU handling - drm/sun4i: backend: Support alpha property on lowest plane - drm/sun4i: backend: Disable alpha on the lowest plane on the A20 - KVM: arm64: Update page shift if stage 2 block mapping not supported - ARM: dts: imx6sx: fix the pad QSPI1B_SCLK mux mode for uart3 - mmc: sdhci-acpi: Clear amd_sdhci_host on reset - mmc: sdhci-msm: Add retries when all tuning phases are found valid - spi: stm32: Rate-limit the 'Communication suspended' message - btrfs: fix NULL pointer dereference after failure to create snapshot - i2c: npcm7xx: Fix timeout calculation - block: restore a specific error code in bdev_del_partition - seccomp: don't leak memory when filter install races - nvme-fabrics: allow to queue requests for live queues - spi: stm32: fix pm_runtime_get_sync() error checking - block: Set same_page to false in __bio_try_merge_page if ret is false - RDMA/rtrs-srv: Set .release function for rtrs srv device during device init - IB/isert: Fix unaligned immediate-data handling - ARM: dts: bcm: HR2: Fixed QSPI compatible string - ARM: dts: NSP: Fixed QSPI compatible string - ARM: dts: BCM5301X: Fixed QSPI compatible string - arm64: dts: ns2: Fixed QSPI compatible string - KVM: nVMX: Fix the update value of nested load IA32_PERF_GLOBAL_CTRL control - KVM: x86: always allow writing '0' to MSR_KVM_ASYNC_PF_EN - ARC: HSDK: wireup perf irq - dmaengine: acpi: Put
[Kernel-packages] [Bug 1891151] Re: md: improve IO accounting
This bug was fixed in the package linux - 5.8.0-20.21 --- linux (5.8.0-20.21) groovy; urgency=medium * groovy/linux: 5.8.0-20.21 -proposed tracker (LP: #1896668) * Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices (LP: #1853277) - i2c: core: Call i2c_acpi_install_space_handler() before i2c_acpi_register_devices() * Enable LTR for endpoints behind VMD (LP: #1896598) - SAUCE: PCI/ASPM: Enable LTR for endpoints behind VMD * Remove duplicated code in ip_defrag.sh of kselftests/net (LP: #1894062) - Revert "UBUNTU: SAUCE: selftests: net: ip_defrag: modprobe missing nf_defrag_ipv6 support" * [SRU] [Focal/OEM-5.6/Groovy]Fix AMD usb host controller lost after stress S3 (LP: #1893914) - SAUCE: xhci: workaround for S3 issue on AMD SNPS 3.0 xHC * debian/rules editconfigs does not work on s390x to change s390x only configs (LP: #1863116) - [Packaging] kernelconfig -- only update/edit configurations on architectures we have compiler support * [Ubuntu 20.10] zPCI DMA tables and bitmap leak on hard unplug (PCI Event 0x0304) (LP: #1896216) - s390/pci: fix leak of DMA tables on hard unplug * md: improve IO accounting (LP: #1891151) - md: improve io stats accounting * Groovy update: v5.8.10 upstream stable release (LP: #1896078) - ARM: OMAP2+: Fix an IS_ERR() vs NULL check in _get_pwrdm() - ARM: dts: logicpd-torpedo-baseboard: Fix broken audio - ARM: dts: logicpd-som-lv-baseboard: Fix broken audio - ARM: dts: logicpd-som-lv-baseboard: Fix missing video - regulator: push allocation in regulator_ena_gpio_request() out of lock - regulator: remove superfluous lock in regulator_resolve_coupling() - ARM: dts: socfpga: fix register entry for timer3 on Arria10 - ARM: dts: omap5: Fix DSI base address and clocks - ARM: dts: ls1021a: fix QuadSPI-memory reg range - ARM: dts: imx7ulp: Correct gpio ranges - arm64: dts: imx: Add missing imx8mm-beacon-kit.dtb to build - ARM: dts: imx7d-zii-rmu2: fix rgmii phy-mode for ksz9031 phy - RDMA/rtrs-srv: Replace device_register with device_initialize and device_add - RDMA/rxe: Fix memleak in rxe_mem_init_user - RDMA/rxe: Drop pointless checks in rxe_init_ports - RDMA/rxe: Fix panic when calling kmem_cache_create() - RDMA/bnxt_re: Do not report transparent vlan from QP1 - RDMA/bnxt_re: Fix the qp table indexing - RDMA/bnxt_re: Static NQ depth allocation - RDMA/bnxt_re: Fix driver crash on unaligned PSN entry address - RDMA/bnxt_re: Remove the qp from list only if the qp destroy succeeds - drm/sun4i: add missing put_device() call in sun8i_r40_tcon_tv_set_mux() - arm64: dts: imx8mq: Fix TMU interrupt property - drm/sun4i: Fix dsi dcs long write function - scsi: qla2xxx: Fix regression on sparc64 - scsi: libsas: Set data_dir as DMA_NONE if libata marks qc as NODATA - drm/virtio: fix unblank - RDMA/core: Fix unsafe linked list traversal after failing to allocate CQ - RDMA/core: Fix reported speed and width - scsi: megaraid_sas: Don't call disable_irq from process IRQ poll - scsi: mpt3sas: Don't call disable_irq from IRQ poll handler - soundwire: fix double free of dangling pointer - Revert "kbuild: use -flive-patching when CONFIG_LIVEPATCH is enabled" - interconnect: qcom: Fix small BW votes being truncated to zero - padata: fix possible padata_works_lock deadlock - drm/sun4i: Fix DE2 YVU handling - drm/sun4i: backend: Support alpha property on lowest plane - drm/sun4i: backend: Disable alpha on the lowest plane on the A20 - KVM: arm64: Update page shift if stage 2 block mapping not supported - ARM: dts: imx6sx: fix the pad QSPI1B_SCLK mux mode for uart3 - mmc: sdhci-acpi: Clear amd_sdhci_host on reset - mmc: sdhci-msm: Add retries when all tuning phases are found valid - spi: stm32: Rate-limit the 'Communication suspended' message - btrfs: fix NULL pointer dereference after failure to create snapshot - i2c: npcm7xx: Fix timeout calculation - block: restore a specific error code in bdev_del_partition - seccomp: don't leak memory when filter install races - nvme-fabrics: allow to queue requests for live queues - spi: stm32: fix pm_runtime_get_sync() error checking - block: Set same_page to false in __bio_try_merge_page if ret is false - RDMA/rtrs-srv: Set .release function for rtrs srv device during device init - IB/isert: Fix unaligned immediate-data handling - ARM: dts: bcm: HR2: Fixed QSPI compatible string - ARM: dts: NSP: Fixed QSPI compatible string - ARM: dts: BCM5301X: Fixed QSPI compatible string - arm64: dts: ns2: Fixed QSPI compatible string - KVM: nVMX: Fix the update value of nested load IA32_PERF_GLOBAL_CTRL control - KVM: x86: always allow writing '0' to MSR_KVM_ASYNC_PF_EN - ARC: HSDK: wireup perf irq - dmaengine: acpi: Put
[Kernel-packages] [Bug 1895606] Re: Thunderbolt3 daisy chain sometimes doesn't work
This bug was fixed in the package linux - 5.8.0-20.21 --- linux (5.8.0-20.21) groovy; urgency=medium * groovy/linux: 5.8.0-20.21 -proposed tracker (LP: #1896668) * Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices (LP: #1853277) - i2c: core: Call i2c_acpi_install_space_handler() before i2c_acpi_register_devices() * Enable LTR for endpoints behind VMD (LP: #1896598) - SAUCE: PCI/ASPM: Enable LTR for endpoints behind VMD * Remove duplicated code in ip_defrag.sh of kselftests/net (LP: #1894062) - Revert "UBUNTU: SAUCE: selftests: net: ip_defrag: modprobe missing nf_defrag_ipv6 support" * [SRU] [Focal/OEM-5.6/Groovy]Fix AMD usb host controller lost after stress S3 (LP: #1893914) - SAUCE: xhci: workaround for S3 issue on AMD SNPS 3.0 xHC * debian/rules editconfigs does not work on s390x to change s390x only configs (LP: #1863116) - [Packaging] kernelconfig -- only update/edit configurations on architectures we have compiler support * [Ubuntu 20.10] zPCI DMA tables and bitmap leak on hard unplug (PCI Event 0x0304) (LP: #1896216) - s390/pci: fix leak of DMA tables on hard unplug * md: improve IO accounting (LP: #1891151) - md: improve io stats accounting * Groovy update: v5.8.10 upstream stable release (LP: #1896078) - ARM: OMAP2+: Fix an IS_ERR() vs NULL check in _get_pwrdm() - ARM: dts: logicpd-torpedo-baseboard: Fix broken audio - ARM: dts: logicpd-som-lv-baseboard: Fix broken audio - ARM: dts: logicpd-som-lv-baseboard: Fix missing video - regulator: push allocation in regulator_ena_gpio_request() out of lock - regulator: remove superfluous lock in regulator_resolve_coupling() - ARM: dts: socfpga: fix register entry for timer3 on Arria10 - ARM: dts: omap5: Fix DSI base address and clocks - ARM: dts: ls1021a: fix QuadSPI-memory reg range - ARM: dts: imx7ulp: Correct gpio ranges - arm64: dts: imx: Add missing imx8mm-beacon-kit.dtb to build - ARM: dts: imx7d-zii-rmu2: fix rgmii phy-mode for ksz9031 phy - RDMA/rtrs-srv: Replace device_register with device_initialize and device_add - RDMA/rxe: Fix memleak in rxe_mem_init_user - RDMA/rxe: Drop pointless checks in rxe_init_ports - RDMA/rxe: Fix panic when calling kmem_cache_create() - RDMA/bnxt_re: Do not report transparent vlan from QP1 - RDMA/bnxt_re: Fix the qp table indexing - RDMA/bnxt_re: Static NQ depth allocation - RDMA/bnxt_re: Fix driver crash on unaligned PSN entry address - RDMA/bnxt_re: Remove the qp from list only if the qp destroy succeeds - drm/sun4i: add missing put_device() call in sun8i_r40_tcon_tv_set_mux() - arm64: dts: imx8mq: Fix TMU interrupt property - drm/sun4i: Fix dsi dcs long write function - scsi: qla2xxx: Fix regression on sparc64 - scsi: libsas: Set data_dir as DMA_NONE if libata marks qc as NODATA - drm/virtio: fix unblank - RDMA/core: Fix unsafe linked list traversal after failing to allocate CQ - RDMA/core: Fix reported speed and width - scsi: megaraid_sas: Don't call disable_irq from process IRQ poll - scsi: mpt3sas: Don't call disable_irq from IRQ poll handler - soundwire: fix double free of dangling pointer - Revert "kbuild: use -flive-patching when CONFIG_LIVEPATCH is enabled" - interconnect: qcom: Fix small BW votes being truncated to zero - padata: fix possible padata_works_lock deadlock - drm/sun4i: Fix DE2 YVU handling - drm/sun4i: backend: Support alpha property on lowest plane - drm/sun4i: backend: Disable alpha on the lowest plane on the A20 - KVM: arm64: Update page shift if stage 2 block mapping not supported - ARM: dts: imx6sx: fix the pad QSPI1B_SCLK mux mode for uart3 - mmc: sdhci-acpi: Clear amd_sdhci_host on reset - mmc: sdhci-msm: Add retries when all tuning phases are found valid - spi: stm32: Rate-limit the 'Communication suspended' message - btrfs: fix NULL pointer dereference after failure to create snapshot - i2c: npcm7xx: Fix timeout calculation - block: restore a specific error code in bdev_del_partition - seccomp: don't leak memory when filter install races - nvme-fabrics: allow to queue requests for live queues - spi: stm32: fix pm_runtime_get_sync() error checking - block: Set same_page to false in __bio_try_merge_page if ret is false - RDMA/rtrs-srv: Set .release function for rtrs srv device during device init - IB/isert: Fix unaligned immediate-data handling - ARM: dts: bcm: HR2: Fixed QSPI compatible string - ARM: dts: NSP: Fixed QSPI compatible string - ARM: dts: BCM5301X: Fixed QSPI compatible string - arm64: dts: ns2: Fixed QSPI compatible string - KVM: nVMX: Fix the update value of nested load IA32_PERF_GLOBAL_CTRL control - KVM: x86: always allow writing '0' to MSR_KVM_ASYNC_PF_EN - ARC: HSDK: wireup perf irq - dmaengine: acpi: Put
[Kernel-packages] [Bug 1853277] Re: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices
This bug was fixed in the package linux - 5.8.0-20.21 --- linux (5.8.0-20.21) groovy; urgency=medium * groovy/linux: 5.8.0-20.21 -proposed tracker (LP: #1896668) * Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices (LP: #1853277) - i2c: core: Call i2c_acpi_install_space_handler() before i2c_acpi_register_devices() * Enable LTR for endpoints behind VMD (LP: #1896598) - SAUCE: PCI/ASPM: Enable LTR for endpoints behind VMD * Remove duplicated code in ip_defrag.sh of kselftests/net (LP: #1894062) - Revert "UBUNTU: SAUCE: selftests: net: ip_defrag: modprobe missing nf_defrag_ipv6 support" * [SRU] [Focal/OEM-5.6/Groovy]Fix AMD usb host controller lost after stress S3 (LP: #1893914) - SAUCE: xhci: workaround for S3 issue on AMD SNPS 3.0 xHC * debian/rules editconfigs does not work on s390x to change s390x only configs (LP: #1863116) - [Packaging] kernelconfig -- only update/edit configurations on architectures we have compiler support * [Ubuntu 20.10] zPCI DMA tables and bitmap leak on hard unplug (PCI Event 0x0304) (LP: #1896216) - s390/pci: fix leak of DMA tables on hard unplug * md: improve IO accounting (LP: #1891151) - md: improve io stats accounting * Groovy update: v5.8.10 upstream stable release (LP: #1896078) - ARM: OMAP2+: Fix an IS_ERR() vs NULL check in _get_pwrdm() - ARM: dts: logicpd-torpedo-baseboard: Fix broken audio - ARM: dts: logicpd-som-lv-baseboard: Fix broken audio - ARM: dts: logicpd-som-lv-baseboard: Fix missing video - regulator: push allocation in regulator_ena_gpio_request() out of lock - regulator: remove superfluous lock in regulator_resolve_coupling() - ARM: dts: socfpga: fix register entry for timer3 on Arria10 - ARM: dts: omap5: Fix DSI base address and clocks - ARM: dts: ls1021a: fix QuadSPI-memory reg range - ARM: dts: imx7ulp: Correct gpio ranges - arm64: dts: imx: Add missing imx8mm-beacon-kit.dtb to build - ARM: dts: imx7d-zii-rmu2: fix rgmii phy-mode for ksz9031 phy - RDMA/rtrs-srv: Replace device_register with device_initialize and device_add - RDMA/rxe: Fix memleak in rxe_mem_init_user - RDMA/rxe: Drop pointless checks in rxe_init_ports - RDMA/rxe: Fix panic when calling kmem_cache_create() - RDMA/bnxt_re: Do not report transparent vlan from QP1 - RDMA/bnxt_re: Fix the qp table indexing - RDMA/bnxt_re: Static NQ depth allocation - RDMA/bnxt_re: Fix driver crash on unaligned PSN entry address - RDMA/bnxt_re: Remove the qp from list only if the qp destroy succeeds - drm/sun4i: add missing put_device() call in sun8i_r40_tcon_tv_set_mux() - arm64: dts: imx8mq: Fix TMU interrupt property - drm/sun4i: Fix dsi dcs long write function - scsi: qla2xxx: Fix regression on sparc64 - scsi: libsas: Set data_dir as DMA_NONE if libata marks qc as NODATA - drm/virtio: fix unblank - RDMA/core: Fix unsafe linked list traversal after failing to allocate CQ - RDMA/core: Fix reported speed and width - scsi: megaraid_sas: Don't call disable_irq from process IRQ poll - scsi: mpt3sas: Don't call disable_irq from IRQ poll handler - soundwire: fix double free of dangling pointer - Revert "kbuild: use -flive-patching when CONFIG_LIVEPATCH is enabled" - interconnect: qcom: Fix small BW votes being truncated to zero - padata: fix possible padata_works_lock deadlock - drm/sun4i: Fix DE2 YVU handling - drm/sun4i: backend: Support alpha property on lowest plane - drm/sun4i: backend: Disable alpha on the lowest plane on the A20 - KVM: arm64: Update page shift if stage 2 block mapping not supported - ARM: dts: imx6sx: fix the pad QSPI1B_SCLK mux mode for uart3 - mmc: sdhci-acpi: Clear amd_sdhci_host on reset - mmc: sdhci-msm: Add retries when all tuning phases are found valid - spi: stm32: Rate-limit the 'Communication suspended' message - btrfs: fix NULL pointer dereference after failure to create snapshot - i2c: npcm7xx: Fix timeout calculation - block: restore a specific error code in bdev_del_partition - seccomp: don't leak memory when filter install races - nvme-fabrics: allow to queue requests for live queues - spi: stm32: fix pm_runtime_get_sync() error checking - block: Set same_page to false in __bio_try_merge_page if ret is false - RDMA/rtrs-srv: Set .release function for rtrs srv device during device init - IB/isert: Fix unaligned immediate-data handling - ARM: dts: bcm: HR2: Fixed QSPI compatible string - ARM: dts: NSP: Fixed QSPI compatible string - ARM: dts: BCM5301X: Fixed QSPI compatible string - arm64: dts: ns2: Fixed QSPI compatible string - KVM: nVMX: Fix the update value of nested load IA32_PERF_GLOBAL_CTRL control - KVM: x86: always allow writing '0' to MSR_KVM_ASYNC_PF_EN - ARC: HSDK: wireup perf irq - dmaengine: acpi: Put
[Kernel-packages] [Bug 1895200] Re: [MIR] microcode-initrd
This bug was fixed in the package linux-meta-aws - 5.8.0.1006.8 --- linux-meta-aws (5.8.0.1006.8) groovy; urgency=medium * Bump ABI 5.8.0-1006 -- Andrea Righi Wed, 23 Sep 2020 11:15:14 +0200 ** Changed in: linux-meta-aws (Ubuntu) Status: Opinion => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-aws in Ubuntu. https://bugs.launchpad.net/bugs/1895200 Title: [MIR] microcode-initrd Status in linux-meta-aws package in Ubuntu: Fix Released Status in microcode-initrd package in Ubuntu: Fix Released Bug description: [Availability] * Groovy Universe [Rationale] * Needed to apply microcode updates, on bare-metal public-cloud machines, that otherwise boot without a full initrd. [Security] * This package is tiny, just a single small shell script trigger hook that create microcode-initrd from intel-microcode and amd-microcode packages. [Quality assurance] * Installing this package automatically integrates with grub2 thus this package needs no configuration to start using. * There are no debconf questions * Package is new, unique to Ubuntu [Dependencies] * All dependencies are in main [Standards compliance] * Complies with policy [Maintenance] * Foundations-bugs subscribed [Background information] * Currently we have a few public-clouds with bare-metal instance types that boot without initrd. To apply microcode updates as required to mitigate Spectre, Meldown, MDS attacks, a microcode-only initrd needs to be loaded by grub, as late-loading of microcode is not safe. This package was tested successfully on multiple instance types to ensure correct operation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-aws/+bug/1895200/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863116] Re: debian/rules editconfigs does not work on s390x to change s390x only configs
This bug was fixed in the package linux - 5.8.0-20.21 --- linux (5.8.0-20.21) groovy; urgency=medium * groovy/linux: 5.8.0-20.21 -proposed tracker (LP: #1896668) * Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices (LP: #1853277) - i2c: core: Call i2c_acpi_install_space_handler() before i2c_acpi_register_devices() * Enable LTR for endpoints behind VMD (LP: #1896598) - SAUCE: PCI/ASPM: Enable LTR for endpoints behind VMD * Remove duplicated code in ip_defrag.sh of kselftests/net (LP: #1894062) - Revert "UBUNTU: SAUCE: selftests: net: ip_defrag: modprobe missing nf_defrag_ipv6 support" * [SRU] [Focal/OEM-5.6/Groovy]Fix AMD usb host controller lost after stress S3 (LP: #1893914) - SAUCE: xhci: workaround for S3 issue on AMD SNPS 3.0 xHC * debian/rules editconfigs does not work on s390x to change s390x only configs (LP: #1863116) - [Packaging] kernelconfig -- only update/edit configurations on architectures we have compiler support * [Ubuntu 20.10] zPCI DMA tables and bitmap leak on hard unplug (PCI Event 0x0304) (LP: #1896216) - s390/pci: fix leak of DMA tables on hard unplug * md: improve IO accounting (LP: #1891151) - md: improve io stats accounting * Groovy update: v5.8.10 upstream stable release (LP: #1896078) - ARM: OMAP2+: Fix an IS_ERR() vs NULL check in _get_pwrdm() - ARM: dts: logicpd-torpedo-baseboard: Fix broken audio - ARM: dts: logicpd-som-lv-baseboard: Fix broken audio - ARM: dts: logicpd-som-lv-baseboard: Fix missing video - regulator: push allocation in regulator_ena_gpio_request() out of lock - regulator: remove superfluous lock in regulator_resolve_coupling() - ARM: dts: socfpga: fix register entry for timer3 on Arria10 - ARM: dts: omap5: Fix DSI base address and clocks - ARM: dts: ls1021a: fix QuadSPI-memory reg range - ARM: dts: imx7ulp: Correct gpio ranges - arm64: dts: imx: Add missing imx8mm-beacon-kit.dtb to build - ARM: dts: imx7d-zii-rmu2: fix rgmii phy-mode for ksz9031 phy - RDMA/rtrs-srv: Replace device_register with device_initialize and device_add - RDMA/rxe: Fix memleak in rxe_mem_init_user - RDMA/rxe: Drop pointless checks in rxe_init_ports - RDMA/rxe: Fix panic when calling kmem_cache_create() - RDMA/bnxt_re: Do not report transparent vlan from QP1 - RDMA/bnxt_re: Fix the qp table indexing - RDMA/bnxt_re: Static NQ depth allocation - RDMA/bnxt_re: Fix driver crash on unaligned PSN entry address - RDMA/bnxt_re: Remove the qp from list only if the qp destroy succeeds - drm/sun4i: add missing put_device() call in sun8i_r40_tcon_tv_set_mux() - arm64: dts: imx8mq: Fix TMU interrupt property - drm/sun4i: Fix dsi dcs long write function - scsi: qla2xxx: Fix regression on sparc64 - scsi: libsas: Set data_dir as DMA_NONE if libata marks qc as NODATA - drm/virtio: fix unblank - RDMA/core: Fix unsafe linked list traversal after failing to allocate CQ - RDMA/core: Fix reported speed and width - scsi: megaraid_sas: Don't call disable_irq from process IRQ poll - scsi: mpt3sas: Don't call disable_irq from IRQ poll handler - soundwire: fix double free of dangling pointer - Revert "kbuild: use -flive-patching when CONFIG_LIVEPATCH is enabled" - interconnect: qcom: Fix small BW votes being truncated to zero - padata: fix possible padata_works_lock deadlock - drm/sun4i: Fix DE2 YVU handling - drm/sun4i: backend: Support alpha property on lowest plane - drm/sun4i: backend: Disable alpha on the lowest plane on the A20 - KVM: arm64: Update page shift if stage 2 block mapping not supported - ARM: dts: imx6sx: fix the pad QSPI1B_SCLK mux mode for uart3 - mmc: sdhci-acpi: Clear amd_sdhci_host on reset - mmc: sdhci-msm: Add retries when all tuning phases are found valid - spi: stm32: Rate-limit the 'Communication suspended' message - btrfs: fix NULL pointer dereference after failure to create snapshot - i2c: npcm7xx: Fix timeout calculation - block: restore a specific error code in bdev_del_partition - seccomp: don't leak memory when filter install races - nvme-fabrics: allow to queue requests for live queues - spi: stm32: fix pm_runtime_get_sync() error checking - block: Set same_page to false in __bio_try_merge_page if ret is false - RDMA/rtrs-srv: Set .release function for rtrs srv device during device init - IB/isert: Fix unaligned immediate-data handling - ARM: dts: bcm: HR2: Fixed QSPI compatible string - ARM: dts: NSP: Fixed QSPI compatible string - ARM: dts: BCM5301X: Fixed QSPI compatible string - arm64: dts: ns2: Fixed QSPI compatible string - KVM: nVMX: Fix the update value of nested load IA32_PERF_GLOBAL_CTRL control - KVM: x86: always allow writing '0' to MSR_KVM_ASYNC_PF_EN - ARC: HSDK: wireup perf irq - dmaengine: acpi: Put
[Kernel-packages] [Bug 1888331] Re: Wakeup the system by touching the touchpad
This bug was fixed in the package linux - 5.8.0-20.21 --- linux (5.8.0-20.21) groovy; urgency=medium * groovy/linux: 5.8.0-20.21 -proposed tracker (LP: #1896668) * Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices (LP: #1853277) - i2c: core: Call i2c_acpi_install_space_handler() before i2c_acpi_register_devices() * Enable LTR for endpoints behind VMD (LP: #1896598) - SAUCE: PCI/ASPM: Enable LTR for endpoints behind VMD * Remove duplicated code in ip_defrag.sh of kselftests/net (LP: #1894062) - Revert "UBUNTU: SAUCE: selftests: net: ip_defrag: modprobe missing nf_defrag_ipv6 support" * [SRU] [Focal/OEM-5.6/Groovy]Fix AMD usb host controller lost after stress S3 (LP: #1893914) - SAUCE: xhci: workaround for S3 issue on AMD SNPS 3.0 xHC * debian/rules editconfigs does not work on s390x to change s390x only configs (LP: #1863116) - [Packaging] kernelconfig -- only update/edit configurations on architectures we have compiler support * [Ubuntu 20.10] zPCI DMA tables and bitmap leak on hard unplug (PCI Event 0x0304) (LP: #1896216) - s390/pci: fix leak of DMA tables on hard unplug * md: improve IO accounting (LP: #1891151) - md: improve io stats accounting * Groovy update: v5.8.10 upstream stable release (LP: #1896078) - ARM: OMAP2+: Fix an IS_ERR() vs NULL check in _get_pwrdm() - ARM: dts: logicpd-torpedo-baseboard: Fix broken audio - ARM: dts: logicpd-som-lv-baseboard: Fix broken audio - ARM: dts: logicpd-som-lv-baseboard: Fix missing video - regulator: push allocation in regulator_ena_gpio_request() out of lock - regulator: remove superfluous lock in regulator_resolve_coupling() - ARM: dts: socfpga: fix register entry for timer3 on Arria10 - ARM: dts: omap5: Fix DSI base address and clocks - ARM: dts: ls1021a: fix QuadSPI-memory reg range - ARM: dts: imx7ulp: Correct gpio ranges - arm64: dts: imx: Add missing imx8mm-beacon-kit.dtb to build - ARM: dts: imx7d-zii-rmu2: fix rgmii phy-mode for ksz9031 phy - RDMA/rtrs-srv: Replace device_register with device_initialize and device_add - RDMA/rxe: Fix memleak in rxe_mem_init_user - RDMA/rxe: Drop pointless checks in rxe_init_ports - RDMA/rxe: Fix panic when calling kmem_cache_create() - RDMA/bnxt_re: Do not report transparent vlan from QP1 - RDMA/bnxt_re: Fix the qp table indexing - RDMA/bnxt_re: Static NQ depth allocation - RDMA/bnxt_re: Fix driver crash on unaligned PSN entry address - RDMA/bnxt_re: Remove the qp from list only if the qp destroy succeeds - drm/sun4i: add missing put_device() call in sun8i_r40_tcon_tv_set_mux() - arm64: dts: imx8mq: Fix TMU interrupt property - drm/sun4i: Fix dsi dcs long write function - scsi: qla2xxx: Fix regression on sparc64 - scsi: libsas: Set data_dir as DMA_NONE if libata marks qc as NODATA - drm/virtio: fix unblank - RDMA/core: Fix unsafe linked list traversal after failing to allocate CQ - RDMA/core: Fix reported speed and width - scsi: megaraid_sas: Don't call disable_irq from process IRQ poll - scsi: mpt3sas: Don't call disable_irq from IRQ poll handler - soundwire: fix double free of dangling pointer - Revert "kbuild: use -flive-patching when CONFIG_LIVEPATCH is enabled" - interconnect: qcom: Fix small BW votes being truncated to zero - padata: fix possible padata_works_lock deadlock - drm/sun4i: Fix DE2 YVU handling - drm/sun4i: backend: Support alpha property on lowest plane - drm/sun4i: backend: Disable alpha on the lowest plane on the A20 - KVM: arm64: Update page shift if stage 2 block mapping not supported - ARM: dts: imx6sx: fix the pad QSPI1B_SCLK mux mode for uart3 - mmc: sdhci-acpi: Clear amd_sdhci_host on reset - mmc: sdhci-msm: Add retries when all tuning phases are found valid - spi: stm32: Rate-limit the 'Communication suspended' message - btrfs: fix NULL pointer dereference after failure to create snapshot - i2c: npcm7xx: Fix timeout calculation - block: restore a specific error code in bdev_del_partition - seccomp: don't leak memory when filter install races - nvme-fabrics: allow to queue requests for live queues - spi: stm32: fix pm_runtime_get_sync() error checking - block: Set same_page to false in __bio_try_merge_page if ret is false - RDMA/rtrs-srv: Set .release function for rtrs srv device during device init - IB/isert: Fix unaligned immediate-data handling - ARM: dts: bcm: HR2: Fixed QSPI compatible string - ARM: dts: NSP: Fixed QSPI compatible string - ARM: dts: BCM5301X: Fixed QSPI compatible string - arm64: dts: ns2: Fixed QSPI compatible string - KVM: nVMX: Fix the update value of nested load IA32_PERF_GLOBAL_CTRL control - KVM: x86: always allow writing '0' to MSR_KVM_ASYNC_PF_EN - ARC: HSDK: wireup perf irq - dmaengine: acpi: Put
[Kernel-packages] [Bug 1895634] Re: Groovy update: v5.8.9 upstream stable release
This bug was fixed in the package linux - 5.8.0-20.21 --- linux (5.8.0-20.21) groovy; urgency=medium * groovy/linux: 5.8.0-20.21 -proposed tracker (LP: #1896668) * Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices (LP: #1853277) - i2c: core: Call i2c_acpi_install_space_handler() before i2c_acpi_register_devices() * Enable LTR for endpoints behind VMD (LP: #1896598) - SAUCE: PCI/ASPM: Enable LTR for endpoints behind VMD * Remove duplicated code in ip_defrag.sh of kselftests/net (LP: #1894062) - Revert "UBUNTU: SAUCE: selftests: net: ip_defrag: modprobe missing nf_defrag_ipv6 support" * [SRU] [Focal/OEM-5.6/Groovy]Fix AMD usb host controller lost after stress S3 (LP: #1893914) - SAUCE: xhci: workaround for S3 issue on AMD SNPS 3.0 xHC * debian/rules editconfigs does not work on s390x to change s390x only configs (LP: #1863116) - [Packaging] kernelconfig -- only update/edit configurations on architectures we have compiler support * [Ubuntu 20.10] zPCI DMA tables and bitmap leak on hard unplug (PCI Event 0x0304) (LP: #1896216) - s390/pci: fix leak of DMA tables on hard unplug * md: improve IO accounting (LP: #1891151) - md: improve io stats accounting * Groovy update: v5.8.10 upstream stable release (LP: #1896078) - ARM: OMAP2+: Fix an IS_ERR() vs NULL check in _get_pwrdm() - ARM: dts: logicpd-torpedo-baseboard: Fix broken audio - ARM: dts: logicpd-som-lv-baseboard: Fix broken audio - ARM: dts: logicpd-som-lv-baseboard: Fix missing video - regulator: push allocation in regulator_ena_gpio_request() out of lock - regulator: remove superfluous lock in regulator_resolve_coupling() - ARM: dts: socfpga: fix register entry for timer3 on Arria10 - ARM: dts: omap5: Fix DSI base address and clocks - ARM: dts: ls1021a: fix QuadSPI-memory reg range - ARM: dts: imx7ulp: Correct gpio ranges - arm64: dts: imx: Add missing imx8mm-beacon-kit.dtb to build - ARM: dts: imx7d-zii-rmu2: fix rgmii phy-mode for ksz9031 phy - RDMA/rtrs-srv: Replace device_register with device_initialize and device_add - RDMA/rxe: Fix memleak in rxe_mem_init_user - RDMA/rxe: Drop pointless checks in rxe_init_ports - RDMA/rxe: Fix panic when calling kmem_cache_create() - RDMA/bnxt_re: Do not report transparent vlan from QP1 - RDMA/bnxt_re: Fix the qp table indexing - RDMA/bnxt_re: Static NQ depth allocation - RDMA/bnxt_re: Fix driver crash on unaligned PSN entry address - RDMA/bnxt_re: Remove the qp from list only if the qp destroy succeeds - drm/sun4i: add missing put_device() call in sun8i_r40_tcon_tv_set_mux() - arm64: dts: imx8mq: Fix TMU interrupt property - drm/sun4i: Fix dsi dcs long write function - scsi: qla2xxx: Fix regression on sparc64 - scsi: libsas: Set data_dir as DMA_NONE if libata marks qc as NODATA - drm/virtio: fix unblank - RDMA/core: Fix unsafe linked list traversal after failing to allocate CQ - RDMA/core: Fix reported speed and width - scsi: megaraid_sas: Don't call disable_irq from process IRQ poll - scsi: mpt3sas: Don't call disable_irq from IRQ poll handler - soundwire: fix double free of dangling pointer - Revert "kbuild: use -flive-patching when CONFIG_LIVEPATCH is enabled" - interconnect: qcom: Fix small BW votes being truncated to zero - padata: fix possible padata_works_lock deadlock - drm/sun4i: Fix DE2 YVU handling - drm/sun4i: backend: Support alpha property on lowest plane - drm/sun4i: backend: Disable alpha on the lowest plane on the A20 - KVM: arm64: Update page shift if stage 2 block mapping not supported - ARM: dts: imx6sx: fix the pad QSPI1B_SCLK mux mode for uart3 - mmc: sdhci-acpi: Clear amd_sdhci_host on reset - mmc: sdhci-msm: Add retries when all tuning phases are found valid - spi: stm32: Rate-limit the 'Communication suspended' message - btrfs: fix NULL pointer dereference after failure to create snapshot - i2c: npcm7xx: Fix timeout calculation - block: restore a specific error code in bdev_del_partition - seccomp: don't leak memory when filter install races - nvme-fabrics: allow to queue requests for live queues - spi: stm32: fix pm_runtime_get_sync() error checking - block: Set same_page to false in __bio_try_merge_page if ret is false - RDMA/rtrs-srv: Set .release function for rtrs srv device during device init - IB/isert: Fix unaligned immediate-data handling - ARM: dts: bcm: HR2: Fixed QSPI compatible string - ARM: dts: NSP: Fixed QSPI compatible string - ARM: dts: BCM5301X: Fixed QSPI compatible string - arm64: dts: ns2: Fixed QSPI compatible string - KVM: nVMX: Fix the update value of nested load IA32_PERF_GLOBAL_CTRL control - KVM: x86: always allow writing '0' to MSR_KVM_ASYNC_PF_EN - ARC: HSDK: wireup perf irq - dmaengine: acpi: Put
[Kernel-packages] [Bug 1896078] Re: Groovy update: v5.8.10 upstream stable release
This bug was fixed in the package linux - 5.8.0-20.21 --- linux (5.8.0-20.21) groovy; urgency=medium * groovy/linux: 5.8.0-20.21 -proposed tracker (LP: #1896668) * Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices (LP: #1853277) - i2c: core: Call i2c_acpi_install_space_handler() before i2c_acpi_register_devices() * Enable LTR for endpoints behind VMD (LP: #1896598) - SAUCE: PCI/ASPM: Enable LTR for endpoints behind VMD * Remove duplicated code in ip_defrag.sh of kselftests/net (LP: #1894062) - Revert "UBUNTU: SAUCE: selftests: net: ip_defrag: modprobe missing nf_defrag_ipv6 support" * [SRU] [Focal/OEM-5.6/Groovy]Fix AMD usb host controller lost after stress S3 (LP: #1893914) - SAUCE: xhci: workaround for S3 issue on AMD SNPS 3.0 xHC * debian/rules editconfigs does not work on s390x to change s390x only configs (LP: #1863116) - [Packaging] kernelconfig -- only update/edit configurations on architectures we have compiler support * [Ubuntu 20.10] zPCI DMA tables and bitmap leak on hard unplug (PCI Event 0x0304) (LP: #1896216) - s390/pci: fix leak of DMA tables on hard unplug * md: improve IO accounting (LP: #1891151) - md: improve io stats accounting * Groovy update: v5.8.10 upstream stable release (LP: #1896078) - ARM: OMAP2+: Fix an IS_ERR() vs NULL check in _get_pwrdm() - ARM: dts: logicpd-torpedo-baseboard: Fix broken audio - ARM: dts: logicpd-som-lv-baseboard: Fix broken audio - ARM: dts: logicpd-som-lv-baseboard: Fix missing video - regulator: push allocation in regulator_ena_gpio_request() out of lock - regulator: remove superfluous lock in regulator_resolve_coupling() - ARM: dts: socfpga: fix register entry for timer3 on Arria10 - ARM: dts: omap5: Fix DSI base address and clocks - ARM: dts: ls1021a: fix QuadSPI-memory reg range - ARM: dts: imx7ulp: Correct gpio ranges - arm64: dts: imx: Add missing imx8mm-beacon-kit.dtb to build - ARM: dts: imx7d-zii-rmu2: fix rgmii phy-mode for ksz9031 phy - RDMA/rtrs-srv: Replace device_register with device_initialize and device_add - RDMA/rxe: Fix memleak in rxe_mem_init_user - RDMA/rxe: Drop pointless checks in rxe_init_ports - RDMA/rxe: Fix panic when calling kmem_cache_create() - RDMA/bnxt_re: Do not report transparent vlan from QP1 - RDMA/bnxt_re: Fix the qp table indexing - RDMA/bnxt_re: Static NQ depth allocation - RDMA/bnxt_re: Fix driver crash on unaligned PSN entry address - RDMA/bnxt_re: Remove the qp from list only if the qp destroy succeeds - drm/sun4i: add missing put_device() call in sun8i_r40_tcon_tv_set_mux() - arm64: dts: imx8mq: Fix TMU interrupt property - drm/sun4i: Fix dsi dcs long write function - scsi: qla2xxx: Fix regression on sparc64 - scsi: libsas: Set data_dir as DMA_NONE if libata marks qc as NODATA - drm/virtio: fix unblank - RDMA/core: Fix unsafe linked list traversal after failing to allocate CQ - RDMA/core: Fix reported speed and width - scsi: megaraid_sas: Don't call disable_irq from process IRQ poll - scsi: mpt3sas: Don't call disable_irq from IRQ poll handler - soundwire: fix double free of dangling pointer - Revert "kbuild: use -flive-patching when CONFIG_LIVEPATCH is enabled" - interconnect: qcom: Fix small BW votes being truncated to zero - padata: fix possible padata_works_lock deadlock - drm/sun4i: Fix DE2 YVU handling - drm/sun4i: backend: Support alpha property on lowest plane - drm/sun4i: backend: Disable alpha on the lowest plane on the A20 - KVM: arm64: Update page shift if stage 2 block mapping not supported - ARM: dts: imx6sx: fix the pad QSPI1B_SCLK mux mode for uart3 - mmc: sdhci-acpi: Clear amd_sdhci_host on reset - mmc: sdhci-msm: Add retries when all tuning phases are found valid - spi: stm32: Rate-limit the 'Communication suspended' message - btrfs: fix NULL pointer dereference after failure to create snapshot - i2c: npcm7xx: Fix timeout calculation - block: restore a specific error code in bdev_del_partition - seccomp: don't leak memory when filter install races - nvme-fabrics: allow to queue requests for live queues - spi: stm32: fix pm_runtime_get_sync() error checking - block: Set same_page to false in __bio_try_merge_page if ret is false - RDMA/rtrs-srv: Set .release function for rtrs srv device during device init - IB/isert: Fix unaligned immediate-data handling - ARM: dts: bcm: HR2: Fixed QSPI compatible string - ARM: dts: NSP: Fixed QSPI compatible string - ARM: dts: BCM5301X: Fixed QSPI compatible string - arm64: dts: ns2: Fixed QSPI compatible string - KVM: nVMX: Fix the update value of nested load IA32_PERF_GLOBAL_CTRL control - KVM: x86: always allow writing '0' to MSR_KVM_ASYNC_PF_EN - ARC: HSDK: wireup perf irq - dmaengine: acpi: Put
[Kernel-packages] [Bug 1895718] Re: Fix non-working NVMe after S3
This bug was fixed in the package linux - 5.8.0-20.21 --- linux (5.8.0-20.21) groovy; urgency=medium * groovy/linux: 5.8.0-20.21 -proposed tracker (LP: #1896668) * Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices (LP: #1853277) - i2c: core: Call i2c_acpi_install_space_handler() before i2c_acpi_register_devices() * Enable LTR for endpoints behind VMD (LP: #1896598) - SAUCE: PCI/ASPM: Enable LTR for endpoints behind VMD * Remove duplicated code in ip_defrag.sh of kselftests/net (LP: #1894062) - Revert "UBUNTU: SAUCE: selftests: net: ip_defrag: modprobe missing nf_defrag_ipv6 support" * [SRU] [Focal/OEM-5.6/Groovy]Fix AMD usb host controller lost after stress S3 (LP: #1893914) - SAUCE: xhci: workaround for S3 issue on AMD SNPS 3.0 xHC * debian/rules editconfigs does not work on s390x to change s390x only configs (LP: #1863116) - [Packaging] kernelconfig -- only update/edit configurations on architectures we have compiler support * [Ubuntu 20.10] zPCI DMA tables and bitmap leak on hard unplug (PCI Event 0x0304) (LP: #1896216) - s390/pci: fix leak of DMA tables on hard unplug * md: improve IO accounting (LP: #1891151) - md: improve io stats accounting * Groovy update: v5.8.10 upstream stable release (LP: #1896078) - ARM: OMAP2+: Fix an IS_ERR() vs NULL check in _get_pwrdm() - ARM: dts: logicpd-torpedo-baseboard: Fix broken audio - ARM: dts: logicpd-som-lv-baseboard: Fix broken audio - ARM: dts: logicpd-som-lv-baseboard: Fix missing video - regulator: push allocation in regulator_ena_gpio_request() out of lock - regulator: remove superfluous lock in regulator_resolve_coupling() - ARM: dts: socfpga: fix register entry for timer3 on Arria10 - ARM: dts: omap5: Fix DSI base address and clocks - ARM: dts: ls1021a: fix QuadSPI-memory reg range - ARM: dts: imx7ulp: Correct gpio ranges - arm64: dts: imx: Add missing imx8mm-beacon-kit.dtb to build - ARM: dts: imx7d-zii-rmu2: fix rgmii phy-mode for ksz9031 phy - RDMA/rtrs-srv: Replace device_register with device_initialize and device_add - RDMA/rxe: Fix memleak in rxe_mem_init_user - RDMA/rxe: Drop pointless checks in rxe_init_ports - RDMA/rxe: Fix panic when calling kmem_cache_create() - RDMA/bnxt_re: Do not report transparent vlan from QP1 - RDMA/bnxt_re: Fix the qp table indexing - RDMA/bnxt_re: Static NQ depth allocation - RDMA/bnxt_re: Fix driver crash on unaligned PSN entry address - RDMA/bnxt_re: Remove the qp from list only if the qp destroy succeeds - drm/sun4i: add missing put_device() call in sun8i_r40_tcon_tv_set_mux() - arm64: dts: imx8mq: Fix TMU interrupt property - drm/sun4i: Fix dsi dcs long write function - scsi: qla2xxx: Fix regression on sparc64 - scsi: libsas: Set data_dir as DMA_NONE if libata marks qc as NODATA - drm/virtio: fix unblank - RDMA/core: Fix unsafe linked list traversal after failing to allocate CQ - RDMA/core: Fix reported speed and width - scsi: megaraid_sas: Don't call disable_irq from process IRQ poll - scsi: mpt3sas: Don't call disable_irq from IRQ poll handler - soundwire: fix double free of dangling pointer - Revert "kbuild: use -flive-patching when CONFIG_LIVEPATCH is enabled" - interconnect: qcom: Fix small BW votes being truncated to zero - padata: fix possible padata_works_lock deadlock - drm/sun4i: Fix DE2 YVU handling - drm/sun4i: backend: Support alpha property on lowest plane - drm/sun4i: backend: Disable alpha on the lowest plane on the A20 - KVM: arm64: Update page shift if stage 2 block mapping not supported - ARM: dts: imx6sx: fix the pad QSPI1B_SCLK mux mode for uart3 - mmc: sdhci-acpi: Clear amd_sdhci_host on reset - mmc: sdhci-msm: Add retries when all tuning phases are found valid - spi: stm32: Rate-limit the 'Communication suspended' message - btrfs: fix NULL pointer dereference after failure to create snapshot - i2c: npcm7xx: Fix timeout calculation - block: restore a specific error code in bdev_del_partition - seccomp: don't leak memory when filter install races - nvme-fabrics: allow to queue requests for live queues - spi: stm32: fix pm_runtime_get_sync() error checking - block: Set same_page to false in __bio_try_merge_page if ret is false - RDMA/rtrs-srv: Set .release function for rtrs srv device during device init - IB/isert: Fix unaligned immediate-data handling - ARM: dts: bcm: HR2: Fixed QSPI compatible string - ARM: dts: NSP: Fixed QSPI compatible string - ARM: dts: BCM5301X: Fixed QSPI compatible string - arm64: dts: ns2: Fixed QSPI compatible string - KVM: nVMX: Fix the update value of nested load IA32_PERF_GLOBAL_CTRL control - KVM: x86: always allow writing '0' to MSR_KVM_ASYNC_PF_EN - ARC: HSDK: wireup perf irq - dmaengine: acpi: Put
[Kernel-packages] [Bug 1896598] Re: Enable LTR for endpoints behind VMD
This bug was fixed in the package linux - 5.8.0-20.21 --- linux (5.8.0-20.21) groovy; urgency=medium * groovy/linux: 5.8.0-20.21 -proposed tracker (LP: #1896668) * Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices (LP: #1853277) - i2c: core: Call i2c_acpi_install_space_handler() before i2c_acpi_register_devices() * Enable LTR for endpoints behind VMD (LP: #1896598) - SAUCE: PCI/ASPM: Enable LTR for endpoints behind VMD * Remove duplicated code in ip_defrag.sh of kselftests/net (LP: #1894062) - Revert "UBUNTU: SAUCE: selftests: net: ip_defrag: modprobe missing nf_defrag_ipv6 support" * [SRU] [Focal/OEM-5.6/Groovy]Fix AMD usb host controller lost after stress S3 (LP: #1893914) - SAUCE: xhci: workaround for S3 issue on AMD SNPS 3.0 xHC * debian/rules editconfigs does not work on s390x to change s390x only configs (LP: #1863116) - [Packaging] kernelconfig -- only update/edit configurations on architectures we have compiler support * [Ubuntu 20.10] zPCI DMA tables and bitmap leak on hard unplug (PCI Event 0x0304) (LP: #1896216) - s390/pci: fix leak of DMA tables on hard unplug * md: improve IO accounting (LP: #1891151) - md: improve io stats accounting * Groovy update: v5.8.10 upstream stable release (LP: #1896078) - ARM: OMAP2+: Fix an IS_ERR() vs NULL check in _get_pwrdm() - ARM: dts: logicpd-torpedo-baseboard: Fix broken audio - ARM: dts: logicpd-som-lv-baseboard: Fix broken audio - ARM: dts: logicpd-som-lv-baseboard: Fix missing video - regulator: push allocation in regulator_ena_gpio_request() out of lock - regulator: remove superfluous lock in regulator_resolve_coupling() - ARM: dts: socfpga: fix register entry for timer3 on Arria10 - ARM: dts: omap5: Fix DSI base address and clocks - ARM: dts: ls1021a: fix QuadSPI-memory reg range - ARM: dts: imx7ulp: Correct gpio ranges - arm64: dts: imx: Add missing imx8mm-beacon-kit.dtb to build - ARM: dts: imx7d-zii-rmu2: fix rgmii phy-mode for ksz9031 phy - RDMA/rtrs-srv: Replace device_register with device_initialize and device_add - RDMA/rxe: Fix memleak in rxe_mem_init_user - RDMA/rxe: Drop pointless checks in rxe_init_ports - RDMA/rxe: Fix panic when calling kmem_cache_create() - RDMA/bnxt_re: Do not report transparent vlan from QP1 - RDMA/bnxt_re: Fix the qp table indexing - RDMA/bnxt_re: Static NQ depth allocation - RDMA/bnxt_re: Fix driver crash on unaligned PSN entry address - RDMA/bnxt_re: Remove the qp from list only if the qp destroy succeeds - drm/sun4i: add missing put_device() call in sun8i_r40_tcon_tv_set_mux() - arm64: dts: imx8mq: Fix TMU interrupt property - drm/sun4i: Fix dsi dcs long write function - scsi: qla2xxx: Fix regression on sparc64 - scsi: libsas: Set data_dir as DMA_NONE if libata marks qc as NODATA - drm/virtio: fix unblank - RDMA/core: Fix unsafe linked list traversal after failing to allocate CQ - RDMA/core: Fix reported speed and width - scsi: megaraid_sas: Don't call disable_irq from process IRQ poll - scsi: mpt3sas: Don't call disable_irq from IRQ poll handler - soundwire: fix double free of dangling pointer - Revert "kbuild: use -flive-patching when CONFIG_LIVEPATCH is enabled" - interconnect: qcom: Fix small BW votes being truncated to zero - padata: fix possible padata_works_lock deadlock - drm/sun4i: Fix DE2 YVU handling - drm/sun4i: backend: Support alpha property on lowest plane - drm/sun4i: backend: Disable alpha on the lowest plane on the A20 - KVM: arm64: Update page shift if stage 2 block mapping not supported - ARM: dts: imx6sx: fix the pad QSPI1B_SCLK mux mode for uart3 - mmc: sdhci-acpi: Clear amd_sdhci_host on reset - mmc: sdhci-msm: Add retries when all tuning phases are found valid - spi: stm32: Rate-limit the 'Communication suspended' message - btrfs: fix NULL pointer dereference after failure to create snapshot - i2c: npcm7xx: Fix timeout calculation - block: restore a specific error code in bdev_del_partition - seccomp: don't leak memory when filter install races - nvme-fabrics: allow to queue requests for live queues - spi: stm32: fix pm_runtime_get_sync() error checking - block: Set same_page to false in __bio_try_merge_page if ret is false - RDMA/rtrs-srv: Set .release function for rtrs srv device during device init - IB/isert: Fix unaligned immediate-data handling - ARM: dts: bcm: HR2: Fixed QSPI compatible string - ARM: dts: NSP: Fixed QSPI compatible string - ARM: dts: BCM5301X: Fixed QSPI compatible string - arm64: dts: ns2: Fixed QSPI compatible string - KVM: nVMX: Fix the update value of nested load IA32_PERF_GLOBAL_CTRL control - KVM: x86: always allow writing '0' to MSR_KVM_ASYNC_PF_EN - ARC: HSDK: wireup perf irq - dmaengine: acpi: Put
[Kernel-packages] [Bug 1896216] Re: [Ubuntu 20.10] zPCI DMA tables and bitmap leak on hard unplug (PCI Event 0x0304)
This bug was fixed in the package linux - 5.8.0-20.21 --- linux (5.8.0-20.21) groovy; urgency=medium * groovy/linux: 5.8.0-20.21 -proposed tracker (LP: #1896668) * Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices (LP: #1853277) - i2c: core: Call i2c_acpi_install_space_handler() before i2c_acpi_register_devices() * Enable LTR for endpoints behind VMD (LP: #1896598) - SAUCE: PCI/ASPM: Enable LTR for endpoints behind VMD * Remove duplicated code in ip_defrag.sh of kselftests/net (LP: #1894062) - Revert "UBUNTU: SAUCE: selftests: net: ip_defrag: modprobe missing nf_defrag_ipv6 support" * [SRU] [Focal/OEM-5.6/Groovy]Fix AMD usb host controller lost after stress S3 (LP: #1893914) - SAUCE: xhci: workaround for S3 issue on AMD SNPS 3.0 xHC * debian/rules editconfigs does not work on s390x to change s390x only configs (LP: #1863116) - [Packaging] kernelconfig -- only update/edit configurations on architectures we have compiler support * [Ubuntu 20.10] zPCI DMA tables and bitmap leak on hard unplug (PCI Event 0x0304) (LP: #1896216) - s390/pci: fix leak of DMA tables on hard unplug * md: improve IO accounting (LP: #1891151) - md: improve io stats accounting * Groovy update: v5.8.10 upstream stable release (LP: #1896078) - ARM: OMAP2+: Fix an IS_ERR() vs NULL check in _get_pwrdm() - ARM: dts: logicpd-torpedo-baseboard: Fix broken audio - ARM: dts: logicpd-som-lv-baseboard: Fix broken audio - ARM: dts: logicpd-som-lv-baseboard: Fix missing video - regulator: push allocation in regulator_ena_gpio_request() out of lock - regulator: remove superfluous lock in regulator_resolve_coupling() - ARM: dts: socfpga: fix register entry for timer3 on Arria10 - ARM: dts: omap5: Fix DSI base address and clocks - ARM: dts: ls1021a: fix QuadSPI-memory reg range - ARM: dts: imx7ulp: Correct gpio ranges - arm64: dts: imx: Add missing imx8mm-beacon-kit.dtb to build - ARM: dts: imx7d-zii-rmu2: fix rgmii phy-mode for ksz9031 phy - RDMA/rtrs-srv: Replace device_register with device_initialize and device_add - RDMA/rxe: Fix memleak in rxe_mem_init_user - RDMA/rxe: Drop pointless checks in rxe_init_ports - RDMA/rxe: Fix panic when calling kmem_cache_create() - RDMA/bnxt_re: Do not report transparent vlan from QP1 - RDMA/bnxt_re: Fix the qp table indexing - RDMA/bnxt_re: Static NQ depth allocation - RDMA/bnxt_re: Fix driver crash on unaligned PSN entry address - RDMA/bnxt_re: Remove the qp from list only if the qp destroy succeeds - drm/sun4i: add missing put_device() call in sun8i_r40_tcon_tv_set_mux() - arm64: dts: imx8mq: Fix TMU interrupt property - drm/sun4i: Fix dsi dcs long write function - scsi: qla2xxx: Fix regression on sparc64 - scsi: libsas: Set data_dir as DMA_NONE if libata marks qc as NODATA - drm/virtio: fix unblank - RDMA/core: Fix unsafe linked list traversal after failing to allocate CQ - RDMA/core: Fix reported speed and width - scsi: megaraid_sas: Don't call disable_irq from process IRQ poll - scsi: mpt3sas: Don't call disable_irq from IRQ poll handler - soundwire: fix double free of dangling pointer - Revert "kbuild: use -flive-patching when CONFIG_LIVEPATCH is enabled" - interconnect: qcom: Fix small BW votes being truncated to zero - padata: fix possible padata_works_lock deadlock - drm/sun4i: Fix DE2 YVU handling - drm/sun4i: backend: Support alpha property on lowest plane - drm/sun4i: backend: Disable alpha on the lowest plane on the A20 - KVM: arm64: Update page shift if stage 2 block mapping not supported - ARM: dts: imx6sx: fix the pad QSPI1B_SCLK mux mode for uart3 - mmc: sdhci-acpi: Clear amd_sdhci_host on reset - mmc: sdhci-msm: Add retries when all tuning phases are found valid - spi: stm32: Rate-limit the 'Communication suspended' message - btrfs: fix NULL pointer dereference after failure to create snapshot - i2c: npcm7xx: Fix timeout calculation - block: restore a specific error code in bdev_del_partition - seccomp: don't leak memory when filter install races - nvme-fabrics: allow to queue requests for live queues - spi: stm32: fix pm_runtime_get_sync() error checking - block: Set same_page to false in __bio_try_merge_page if ret is false - RDMA/rtrs-srv: Set .release function for rtrs srv device during device init - IB/isert: Fix unaligned immediate-data handling - ARM: dts: bcm: HR2: Fixed QSPI compatible string - ARM: dts: NSP: Fixed QSPI compatible string - ARM: dts: BCM5301X: Fixed QSPI compatible string - arm64: dts: ns2: Fixed QSPI compatible string - KVM: nVMX: Fix the update value of nested load IA32_PERF_GLOBAL_CTRL control - KVM: x86: always allow writing '0' to MSR_KVM_ASYNC_PF_EN - ARC: HSDK: wireup perf irq - dmaengine: acpi: Put
[Kernel-packages] [Bug 1721558] Re: ubuntu-regression-suite fails
i think this was since fixed, no?! ** Tags removed: update-excuse -- 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/1721558 Title: ubuntu-regression-suite fails Status in linux package in Ubuntu: Confirmed Status in linux-aws package in Ubuntu: New Status in linux-azure package in Ubuntu: New Status in linux-gcp package in Ubuntu: New Status in linux-gke package in Ubuntu: New Status in linux-hwe-edge package in Ubuntu: New Status in linux-kvm package in Ubuntu: Confirmed Status in linux source package in Xenial: Incomplete Status in linux-aws source package in Xenial: New Status in linux-azure source package in Xenial: New Status in linux-gcp source package in Xenial: New Status in linux-gke source package in Xenial: New Status in linux-hwe-edge source package in Xenial: New Status in linux-kvm source package in Xenial: New Bug description: ubuntu-regression-suite fails in xenial autopkgtest [22:34:48]: test ubuntu-regression-suite: [--- Source Package Version: 4.4.0-1035.44 Running Kernel Version: 4.4.0-96.119 ERROR: running version does not match source package Please note autopkgtests have quite elaborate setup for the kernels, thus I'm guessing that some of the setup is not done right, and the VMs are still running generic kernel instead of customized kernel. Maybe a reboot mark is needed in the ubuntu-regression-suite case to reboot the system if Source != Running. And if that doesn't help either, then fail the test? This affects a few packages which all trip up ADT testing whenever I SRU systemd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1721558/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867704] Re: alsa/hdmi: support nvidia mst hdmi/dp audio
@Norbert, According to the painfo_linux47.txt in the #14, the active profile still still off with 47 kernel: Default Sink: auto_null Sink #0 State: SUSPENDED Name: auto_null Description: Dummy-Ausgabe Driver: module-null-sink.c Sample Specification: s16le 2ch 44100Hz Channel Map: front-left,front-right Owner Module: 10 Mute: no Volume: front-left: 65536 / 100% / 0.00 dB, front-right: 65536 / 100% / 0.00 dB balance 0.00 Base Volume: 65536 / 100% / 0.00 dB Monitor Source: auto_null.monitor Latency: 0 usec, configured 0 usec Flags: DECIBEL_VOLUME LATENCY SET_FORMATS Properties: device.description = "Dummy-Ausgabe" device.class = "abstract" device.icon_name = "audio-card" Formats: pcm -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1867704 Title: alsa/hdmi: support nvidia mst hdmi/dp audio Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Fix Released Status in linux source package in Bionic: Won't Fix Status in linux-oem source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Bug description: This is the justification for focal: This patchset will introduce a big change on hda_jack and hda_hdmi, So I sent the patcheset to oem-b 4 months ago. After 4 months of running oem-b kernel, there is no any regression reported on this patchset, now I am backporting the patchset to our focal kernel since our oem project is waiting for the patchset to be landed to ubuntu 5.4 kernel ASAP. This patchset are already merged to mainline kernel 5.5-rc and 5.6-rc, so there is no need to send the patchset to oem-5.6 or groovy kernel. [Impact] On some LENOVO I+N machines, when setting the graphic mode to discrete, The dp/hdmi audio on the Docking Gen2 can't work with this machine + LENOVO Docking Gen2, users can't find the hdmi audio entry in the gnome-sound-setting. [Fix] Nvidia developer submit the mst audio support to 5.5-rcN and 5.6-RC1, those patches could fix this issue. [Test Case] set the machien to discrete, plug the dock gen2 to it, then boot, after booting, plug hdmi or dp to dock gen2, the hdmi or dp audio works. test other machines without Nvidia graphic or without gen2, their hdmi/dp audio still work, and check other output/input devices like headphone, microphone, they all worked as well as before. [Regression Risk] one regression possibility is the audio jacks (including analogue and hdmi) can't work anymore, that means after users plug a headphone, headset, hdmi monitor or microphone to the audio jacks or hdmi connectors, the audio driver can't detect the plugging event. But regression's possibility is very low: - this patchset was already applied to oem-b kernel for 4 months, and oem projects didn't report any regression on the patchset - I tested the testing focal kernel with this patchset on many machines, includes a dell hda audio machine, a dell dmic machine, a Lenovo I+N hda audio machine, a lenovo I+N dmic machine, a lenovo I hda audio machine, a lenovo amd hda audio machine. The audio on them all worked as well as before. This is the justification for oem-b Drop the B, so far only need to merge this patchset to OEM-B first, After the patchset is widely verified with oem-b kernel, I send the patchset to B and F then. This patchset will add support of mst audio for nvidia hdmi/dp, this patchset changes lots of common code on hda_jack and hdmi codec, so it is not easy to say it is 100% safe for other machines, but our oem project needs this patchset to be backported to ubuntu kernel, because the tight sechdule of oem project, we backport this patchset to B and OEM-B first, if the hdmi audio works well for a period of time after this patchset is merged, I will backport this patchset to focal, maybe eoan as well. [Impact] On some LENOVO I+N machines, when setting the graphic mode to discrete, The dp/hdmi audio on the Docking Gen2 can't work with this machine + LENOVO Docking Gen2 [Fix] Nvidia developer submit the mst audio support to 5.5-rcN and 5.6-RC1, those patches could fix this issue. [Test Case] set the machien to discrete, plug the dock gen2 to it, then boot, after booting, plug hdmi or dp to dock gen2, the hdmi or dp audio works. test other machines without Nvidia graphic or without gen2, their hdmi/dp audio still work. [Regression Risk] Low, those patches come from mainline kernel, I have tested those patches on the machiens with or without nvidia hdmi, and on the machines with or without docks, all worked
[Kernel-packages] [Bug 1867704] Re: alsa/hdmi: support nvidia mst hdmi/dp audio
@Norbert, According to the painfo_linux47.txt in the #14, the active profile is still off with 47 kernel: Default Sink: auto_null Sink #0 State: SUSPENDED Name: auto_null Description: Dummy-Ausgabe Driver: module-null-sink.c Sample Specification: s16le 2ch 44100Hz Channel Map: front-left,front-right Owner Module: 10 Mute: no Volume: front-left: 65536 / 100% / 0.00 dB, front-right: 65536 / 100% / 0.00 dB balance 0.00 Base Volume: 65536 / 100% / 0.00 dB Monitor Source: auto_null.monitor Latency: 0 usec, configured 0 usec Flags: DECIBEL_VOLUME LATENCY SET_FORMATS Properties: device.description = "Dummy-Ausgabe" device.class = "abstract" device.icon_name = "audio-card" Formats: pcm -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1867704 Title: alsa/hdmi: support nvidia mst hdmi/dp audio Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Fix Released Status in linux source package in Bionic: Won't Fix Status in linux-oem source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Bug description: This is the justification for focal: This patchset will introduce a big change on hda_jack and hda_hdmi, So I sent the patcheset to oem-b 4 months ago. After 4 months of running oem-b kernel, there is no any regression reported on this patchset, now I am backporting the patchset to our focal kernel since our oem project is waiting for the patchset to be landed to ubuntu 5.4 kernel ASAP. This patchset are already merged to mainline kernel 5.5-rc and 5.6-rc, so there is no need to send the patchset to oem-5.6 or groovy kernel. [Impact] On some LENOVO I+N machines, when setting the graphic mode to discrete, The dp/hdmi audio on the Docking Gen2 can't work with this machine + LENOVO Docking Gen2, users can't find the hdmi audio entry in the gnome-sound-setting. [Fix] Nvidia developer submit the mst audio support to 5.5-rcN and 5.6-RC1, those patches could fix this issue. [Test Case] set the machien to discrete, plug the dock gen2 to it, then boot, after booting, plug hdmi or dp to dock gen2, the hdmi or dp audio works. test other machines without Nvidia graphic or without gen2, their hdmi/dp audio still work, and check other output/input devices like headphone, microphone, they all worked as well as before. [Regression Risk] one regression possibility is the audio jacks (including analogue and hdmi) can't work anymore, that means after users plug a headphone, headset, hdmi monitor or microphone to the audio jacks or hdmi connectors, the audio driver can't detect the plugging event. But regression's possibility is very low: - this patchset was already applied to oem-b kernel for 4 months, and oem projects didn't report any regression on the patchset - I tested the testing focal kernel with this patchset on many machines, includes a dell hda audio machine, a dell dmic machine, a Lenovo I+N hda audio machine, a lenovo I+N dmic machine, a lenovo I hda audio machine, a lenovo amd hda audio machine. The audio on them all worked as well as before. This is the justification for oem-b Drop the B, so far only need to merge this patchset to OEM-B first, After the patchset is widely verified with oem-b kernel, I send the patchset to B and F then. This patchset will add support of mst audio for nvidia hdmi/dp, this patchset changes lots of common code on hda_jack and hdmi codec, so it is not easy to say it is 100% safe for other machines, but our oem project needs this patchset to be backported to ubuntu kernel, because the tight sechdule of oem project, we backport this patchset to B and OEM-B first, if the hdmi audio works well for a period of time after this patchset is merged, I will backport this patchset to focal, maybe eoan as well. [Impact] On some LENOVO I+N machines, when setting the graphic mode to discrete, The dp/hdmi audio on the Docking Gen2 can't work with this machine + LENOVO Docking Gen2 [Fix] Nvidia developer submit the mst audio support to 5.5-rcN and 5.6-RC1, those patches could fix this issue. [Test Case] set the machien to discrete, plug the dock gen2 to it, then boot, after booting, plug hdmi or dp to dock gen2, the hdmi or dp audio works. test other machines without Nvidia graphic or without gen2, their hdmi/dp audio still work. [Regression Risk] Low, those patches come from mainline kernel, I have tested those patches on the machiens with or without nvidia hdmi, and on the machines with or without docks, all worked well as before. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1867704/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1878899] Re: Call trace from __video_do_ioctl
** Also affects: v4l2loopback (Ubuntu) Importance: Undecided Status: New ** Changed in: v4l2loopback (Ubuntu) Status: New => Confirmed ** No longer affects: linux (Ubuntu) ** Summary changed: - Call trace from __video_do_ioctl + Call trace from __video_do_ioctl on 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/1878899 Title: Call trace from __video_do_ioctl on focal Status in v4l2loopback package in Ubuntu: Confirmed Bug description: [92420.303133] [ cut here ] [92420.303141] WARNING: CPU: 2 PID: 259541 at drivers/media/v4l2-core/v4l2-ioctl.c:1069 v4l_querycap+0x8f/0xa0 [videodev] [92420.303141] Modules linked in: btrfs xor zstd_compress raid6_pq ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs gspca_zc3xx joydev snd_seq_dummy iptable_mangle xt_CHECKSUM iptable_nat xt_MASQUERADE nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c xt_tcpudp bridge stp llc iptable_filter bpfilter v4l2loopback(OE) binfmt_misc nls_iso8859_1 uvcvideo gspca_vc032x gspca_main videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common videodev snd_usb_audio snd_usbmidi_lib mc snd_seq_midi snd_seq_midi_event snd_rawmidi edac_mce_amd kvm_amd ccp snd_hda_codec_realtek snd_seq snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi snd_hda_intel kvm snd_intel_dspcfg snd_hda_codec snd_hda_core snd_hwdep snd_seq_device snd_pcm input_leds serio_raw k10temp fam15h_power snd_timer snd soundcore mac_hid sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 uas usb_storage dm_crypt amdgpu amd_iommu_v2 gpu_sched hid_generic usbhid hid crct10dif_pclmul crc32_pclmul [92420.303167] ghash_clmulni_intel radeon i2c_algo_bit ttm aesni_intel drm_kms_helper crypto_simd syscopyarea cryptd sysfillrect sysimgblt glue_helper fb_sys_fops ahci libahci i2c_piix4 drm r8169 realtek video [92420.303174] CPU: 2 PID: 259541 Comm: teams Tainted: GW OE 5.4.0-29-lowlatency #33-Ubuntu [92420.303175] Hardware name: Gigabyte Technology Co., Ltd. To be filled by O.E.M./G1.Sniper A88X-CF, BIOS F7 01/08/2014 [92420.303182] RIP: 0010:v4l_querycap+0x8f/0xa0 [videodev] [92420.303183] Code: 00 00 80 48 b9 00 00 20 00 00 00 20 00 48 0b 4b 54 21 d6 39 f2 75 13 48 89 4b 54 5b 41 5c 41 5d 41 5e 41 5f 5d c3 0f 0b eb d0 <0f> 0b 48 89 4b 54 5b 41 5c 41 5d 41 5e 41 5f 5d c3 0f 1f 44 00 00 [92420.303184] RSP: 0018:b4aa44dd7c78 EFLAGS: 00010202 [92420.303186] RAX: RBX: b4aa44dd7d88 RCX: 8520800185208001 [92420.303187] RDX: 85008003 RSI: 85008001 RDI: [92420.303188] RBP: b4aa44dd7ca0 R08: R09: 000a [92420.303188] R10: R11: R12: 994f4e421000 [92420.303189] R13: 994f4de6bf00 R14: 994f4c191940 R15: c0f2e360 [92420.303191] FS: 7f47f2ffd700() GS:994f5fb0() knlGS: [92420.303192] CS: 0010 DS: ES: CR0: 80050033 [92420.303193] CR2: 7f482c0e1000 CR3: 0003d0084000 CR4: 000406e0 [92420.303194] Call Trace: [92420.303201] __video_do_ioctl+0x1a7/0x410 [videodev] [92420.303204] ? default_send_IPI_single+0x20/0x40 [92420.303206] ? resched_curr+0x62/0xe0 [92420.303213] video_usercopy+0x2ad/0x690 [videodev] [92420.303220] ? v4l_s_fmt+0x670/0x670 [videodev] [92420.303224] ? wake_up_q+0x40/0x70 [92420.303230] video_ioctl2+0x15/0x20 [videodev] [92420.303237] v4l2_ioctl+0x4c/0x60 [videodev] [92420.303238] do_vfs_ioctl+0x405/0x660 [92420.303240] ? __fget+0x77/0xa0 [92420.303242] ksys_ioctl+0x67/0x90 [92420.303244] __x64_sys_ioctl+0x1a/0x20 [92420.303246] do_syscall_64+0x57/0x190 [92420.303248] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [92420.303249] RIP: 0033:0x7f489773737b [92420.303251] Code: 0f 1e fa 48 8b 05 15 3b 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d e5 3a 0d 00 f7 d8 64 89 01 48 [92420.303252] RSP: 002b:7f47f2ff77e8 EFLAGS: 0246 ORIG_RAX: 0010 [92420.303254] RAX: ffda RBX: 7f4824026900 RCX: 7f489773737b [92420.303255] RDX: 7f47f2ff78b0 RSI: 80685600 RDI: 0046 [92420.303256] RBP: 80685600 R08: R09: 5645ec03ee68 [92420.303257] R10: 0048 R11: 0246 R12: 0046 [92420.303258] R13: 7f47f2ff78b0 R14: 0015 R15: 7f485b666039 [92420.303260] ---[ end trace 6e9a5041142fdaab ]--- ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-lowlatency 5.4.0.29.34 ProcVersionSignature: Ubuntu 5.4.0-29.33-lowlatency 5.4.30 Uname: Linux 5.4.0-29-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture:
[Kernel-packages] [Bug 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa
*** This bug is a duplicate of bug 1871794 *** https://bugs.launchpad.net/bugs/1871794 not sure... but got the feeling my message was not understood. Since kernel: 5.4.0-7642-generic, **everything works like a charm !!** So either go for PopOs which uses a more up to date kernel OR use one of the methods listed here to get more recent kernel on your Ubuntu https://linuxhint.com/update_ubuntu_kernel_20_04/ dGo -- 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/1878194 Title: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After updating the release from Ubuntu 19.10 to 20.04, the bluetooth headset doesn't work anymore when HSP/HFP profile is selected. With Ubuntu 19.10 the headset was working, there was audio and the mic was perfect for video conferencing. [Steps to reproduce] 1. Connect headset (used blueman to setup and connect) 1.1. When connected the system automatically selects A2DP profile 2. Start playing audio (browser or other) 3. Change profile to HSP/HFP with pavucontrol (or blueman) 4. The audio disappears and microphone is not working (no input) 5. Optionally switch back to A2DP and the audio comes back [Expected] When switching to HSP/HFP the audio should keep playing and the microphone should start working [Notes] I tried with pavucontrol to switch between profiles while playing audio from a browser. As side note there's a led in the headset that still blinks when switching profile. I tried deleting the pulse folder under user's profile .config without success, also reinstalled packages and did a `sudo alsa force-reload` and rebooting several times. Note: not sure this is a duplicate of [Bug #1576559], it looks quite different since the profile changes but the headset stops working. [System info] Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64 pulseaudio: 1:13.99.1-1ubuntu3 bluez: 5.53-0ubuntu3 Headset: Sennheiser HD 4.50 BTNC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1878194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888779] Re: Can't boot with Linux 5.4.0.*
** Description changed: When booting into Ubuntu with Linux kernels versions 5.4.0.* (checked 5.4.0.42 and two uncertain previous versions, something like 5.4.0.40 and 5.4.0.38). The laptop stays at a black screen with the following printed (disclaimer: typed manually from a low quality photo of the screen--- typos and mistakes expected): - [ 69.258353] pcieport 000:00:1c.5: AER: PCIe Bus Error: severity=Corrected, t ype=Physical Layer, (Receiver ID) [ 69.258377] pcieport 000:00:1c.5: AER: device [B086:9d15] error status/mas k=0001/2000 [ 69.258383] pcieport 000:00:1c.5: AER:[ 0] RxErr [ 69.254625] pcieport 000:00:1c.5: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) [ 69.254733] pcieport 000:00:1c.5: AER: device [B086:9d15] error status/mask=0001/2000 [ 69.254816] pcieport 000:00:1c.5: AER:[ 0] RxErr [ 69.254881] pcieport 000:00:1c.5: AER:[ 6] BadTLP + See attachments for good quality photo of the screen. + Notes - Ubuntu with Linux kernel 5.3.0-51-generic boots fine. However, the same text as above is shown for a brief moment. Minimum attachment -- - Output of "sudo lspci -vnvn" is attached. + Output of "sudo lspci -vnvn" is attached. - $ cat /proc/version_signature - Ubuntu 5.3.0-51.44-generic 5.3.18 - --- + $ cat /proc/version_signature + Ubuntu 5.3.0-51.44-generic 5.3.18 + --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: andrei 2258 F pulseaudio - /dev/snd/controlC1: andrei 2258 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: andrei 2258 F pulseaudio + /dev/snd/controlC1: andrei 2258 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistributionChannelDescriptor: - # This is a distribution channel descriptor - # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor - canonical-oem-somerville-xenial-amd64-20160624-2 + # This is a distribution channel descriptor + # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor + canonical-oem-somerville-xenial-amd64-20160624-2 DistroRelease: KDE neon 20.04 HibernationDevice: RESUME=UUID=6b91b055-5e50-43be-b4a7-754b9334f8ab InstallationDate: Installed on 2017-12-26 (940 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Inspiron 5570 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic root=UUID=d848d42f-7543-4f54-ba4b-ee642ebb50a1 ro amdgpu.dpm=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-51.44-generic 5.3.18 RelatedPackageVersions: - linux-restricted-modules-5.3.0-51-generic N/A - linux-backports-modules-5.3.0-51-generic N/A - linux-firmware1.187.1 + linux-restricted-modules-5.3.0-51-generic N/A + linux-backports-modules-5.3.0-51-generic N/A + linux-firmware1.187.1 Tags: focal Uname: Linux 5.3.0-51-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-16 (68 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 09/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.4 dmi.board.name: 0DRPKR dmi.board.vendor: Dell Inc. dmi.board.version: X07 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.4:bd09/08/2017:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn0DRPKR:rvrX07:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell 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/1888779 Title: Can't boot with Linux 5.4.0.* Status in linux package in Ubuntu: Confirmed Bug description: When booting into Ubuntu with Linux kernels versions 5.4.0.* (checked 5.4.0.42 and two uncertain previous versions, something like 5.4.0.40 and 5.4.0.38). The laptop stays at a black screen with the following printed (disclaimer: typed manually from a low quality photo of the screen--- typos and mistakes expected): [ 69.258353] pcieport 000:00:1c.5: AER: PCIe Bus Error: severity=Corrected, t ype=Physical Layer, (Receiver ID) [ 69.258377] pcieport 000:00:1c.5: AER: device [B086:9d15] error status/mas k=0001/2000 [ 69.258383] pcieport 000:00:1c.5: AER:[ 0] RxErr [ 69.254625] pcieport 000:00:1c.5: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) [ 69.254733] pcieport 000:00:1c.5: AER: device [B086:9d15] error status/mask=0001/2000 [
[Kernel-packages] [Bug 1888779] Re: Can't boot with Linux 5.4.0.*
Checked again with latest version. Still does not boot in 5.4.0.48.51 In attachment – photo of the screen. The only way to get out is Alt+SysRq+REISUB -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1888779 Title: Can't boot with Linux 5.4.0.* Status in linux package in Ubuntu: Confirmed Bug description: When booting into Ubuntu with Linux kernels versions 5.4.0.* (checked 5.4.0.42 and two uncertain previous versions, something like 5.4.0.40 and 5.4.0.38). The laptop stays at a black screen with the following printed (disclaimer: typed manually from a low quality photo of the screen--- typos and mistakes expected): [ 69.258353] pcieport 000:00:1c.5: AER: PCIe Bus Error: severity=Corrected, t ype=Physical Layer, (Receiver ID) [ 69.258377] pcieport 000:00:1c.5: AER: device [B086:9d15] error status/mas k=0001/2000 [ 69.258383] pcieport 000:00:1c.5: AER:[ 0] RxErr [ 69.254625] pcieport 000:00:1c.5: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) [ 69.254733] pcieport 000:00:1c.5: AER: device [B086:9d15] error status/mask=0001/2000 [ 69.254816] pcieport 000:00:1c.5: AER:[ 0] RxErr [ 69.254881] pcieport 000:00:1c.5: AER:[ 6] BadTLP See attachments for good quality photo of the screen. Notes - Ubuntu with Linux kernel 5.3.0-51-generic boots fine. However, the same text as above is shown for a brief moment. Minimum attachment -- Output of "sudo lspci -vnvn" is attached. $ cat /proc/version_signature Ubuntu 5.3.0-51.44-generic 5.3.18 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andrei 2258 F pulseaudio /dev/snd/controlC1: andrei 2258 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroRelease: KDE neon 20.04 HibernationDevice: RESUME=UUID=6b91b055-5e50-43be-b4a7-754b9334f8ab InstallationDate: Installed on 2017-12-26 (940 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Inspiron 5570 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic root=UUID=d848d42f-7543-4f54-ba4b-ee642ebb50a1 ro amdgpu.dpm=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-51.44-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-51-generic N/A linux-backports-modules-5.3.0-51-generic N/A linux-firmware1.187.1 Tags: focal Uname: Linux 5.3.0-51-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-16 (68 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 09/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.4 dmi.board.name: 0DRPKR dmi.board.vendor: Dell Inc. dmi.board.version: X07 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.4:bd09/08/2017:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn0DRPKR:rvrX07:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888779/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822394] Re: [Dell BIOSes dated 27 Mar 2019, XPS 9575, Precision 5530 2-in-1] laptop keyboard & touchpad not working at gdm screen after boot
Thanks so much! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822394 Title: [Dell BIOSes dated 27 Mar 2019, XPS 9575, Precision 5530 2-in-1] laptop keyboard & touchpad not working at gdm screen after boot Status in libinput package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: On a dell XPS 15 2-in-1 with the latest 1.4.0 bios, my touchpad and keyboard are unresponsive at the gdm login screen. Keyboard works to unlock encrypted harddrive before that though. If I plug in a USB keyboard or activate my bluetooth mouse, I can use those to log in, and then after logging in the laptop touchpad and keyboard work again. Logging out of the desktop results in the laptop touchpad and keyboard working on the gdm screen. Did not see this behavior before upgrading from 1.2.0 bios to 1.4.0 bios, but also had not rebooted in a while, so not sure if bios or package upgrades triggered this behavior. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gdm3 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 29 17:51:00 2019 InstallationDate: Installed on 2018-09-26 (184 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gdm3 UpgradeStatus: Upgraded to disco on 2019-03-11 (18 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1822394/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822394] Re: [Dell BIOSes dated 27 Mar 2019, XPS 9575, Precision 5530 2-in-1] laptop keyboard & touchpad not working at gdm screen after boot
acpidump on latest (1.13.0) firmware. ** Attachment added: "1.13.0.acpidump" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822394/+attachment/5415405/+files/1.13.0.acpidump -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822394 Title: [Dell BIOSes dated 27 Mar 2019, XPS 9575, Precision 5530 2-in-1] laptop keyboard & touchpad not working at gdm screen after boot Status in libinput package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: On a dell XPS 15 2-in-1 with the latest 1.4.0 bios, my touchpad and keyboard are unresponsive at the gdm login screen. Keyboard works to unlock encrypted harddrive before that though. If I plug in a USB keyboard or activate my bluetooth mouse, I can use those to log in, and then after logging in the laptop touchpad and keyboard work again. Logging out of the desktop results in the laptop touchpad and keyboard working on the gdm screen. Did not see this behavior before upgrading from 1.2.0 bios to 1.4.0 bios, but also had not rebooted in a while, so not sure if bios or package upgrades triggered this behavior. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gdm3 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 29 17:51:00 2019 InstallationDate: Installed on 2018-09-26 (184 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gdm3 UpgradeStatus: Upgraded to disco on 2019-03-11 (18 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1822394/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895966] Re: package nvidia-dkms-440 440.100-0ubuntu0.20.04.1 failed to install/upgrade: installed nvidia-dkms-440 package post-installation script subprocess returned error exi
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-440 (Ubuntu) Status: New => Confirmed -- 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/1895966 Title: package nvidia-dkms-440 440.100-0ubuntu0.20.04.1 failed to install/upgrade: installed nvidia-dkms-440 package post-installation script subprocess returned error exit status 10 Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Bug description: Installation of nvidia driver failed ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-dkms-440 440.100-0ubuntu0.20.04.1 Uname: Linux 5.8.1-050801-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Sep 17 14:43:31 2020 ErrorMessage: installed nvidia-dkms-440 package post-installation script subprocess returned error exit status 10 Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: nvidia-graphics-drivers-440 Title: package nvidia-dkms-440 440.100-0ubuntu0.20.04.1 failed to install/upgrade: installed nvidia-dkms-440 package post-installation script subprocess returned error exit status 10 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/1895966/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1896161] Re: package nvidia-dkms-440 440.100-0ubuntu0.20.04.1 failed to install/upgrade: installed nvidia-dkms-440 package post-installation script subprocess returned error exi
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-440 (Ubuntu) Status: New => Confirmed -- 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/1896161 Title: package nvidia-dkms-440 440.100-0ubuntu0.20.04.1 failed to install/upgrade: installed nvidia-dkms-440 package post-installation script subprocess returned error exit status 1 Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Bug description: Tried to upgrade to ubuntu 20 and received this error. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-dkms-440 440.100-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Sep 17 22:17:56 2020 ErrorMessage: installed nvidia-dkms-440 package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-04-14 (156 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) 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: nvidia-graphics-drivers-440 Title: package nvidia-dkms-440 440.100-0ubuntu0.20.04.1 failed to install/upgrade: installed nvidia-dkms-440 package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-09-18 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1896161/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1897745] Re: Surface Pro 4 with Linux 5.4.x: WPA: Failed to set GTK to the driver
*** This bug is a duplicate of bug 1897299 *** https://bugs.launchpad.net/bugs/1897299 Linux version 5.4.0-48-generic (buildd@lcy01-amd64-010) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #52-Ubuntu SMP Thu Sep 10 10:58:49 UTC 2020 (Ubuntu 5.4.0-48.52-generic 5.4.60) dmesg shows repeat occurrences of: mwifiex_pcie :02:00.0: crypto keys added mwifiex_pcie :02:00.0: info: successfully disconnected from [BSSID] reason code 3 mwifiex_pcie :02:00.0: info: trying to associate to 'eduroam' bssid [BSSID] mwifiex_pcie :02:00.0: info: associated to bssid [BSSID] successfully ** This bug has been marked a duplicate of bug 1897299 mwifiex stops working after kernel upgrade -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1897745 Title: Surface Pro 4 with Linux 5.4.x: WPA: Failed to set GTK to the driver Status in linux package in Ubuntu: Incomplete Bug description: On the Surface Pro 4 with USB Marvell Bluetooth/WLAN device, upgrading from Ubuntu 18.04 with Linux 4.15.x to Ubuntu 20.04 with Linux 5.4.x, only WPA2 Enterprise networks stop working, but other continue to work. WPA: Failed to set GTK to the driver (alg=2 keylen=32 keyidx=1) Starting Ubuntu 20.04.1 with Linux 4.15.x, the problem is gone. Testing Ubuntu’s Linux mainline builds [1], the problem is still there in 5.4.68, but gone in 5.5-rc1. We do not have the resources to bisect this further, as the user needs the device back now. [1]: https://kernel.ubuntu.com/~kernel-ppa/mainline/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1897745/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867704] Re: alsa/hdmi: support nvidia mst hdmi/dp audio
As i run pa-info at linux-5.4.0-48 the sound switched on. norbert@vdr:~$ pa-info > log Invalid card number. Invalid card number. alsactl: save_state:1595: No soundcards found... cat: /tmp/alsa-info.pPgZrJ4h4x/alsactl.tmp: No such file or directory ** Attachment added: "log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1867704/+attachment/5415375/+files/log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1867704 Title: alsa/hdmi: support nvidia mst hdmi/dp audio Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Fix Released Status in linux source package in Bionic: Won't Fix Status in linux-oem source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Bug description: This is the justification for focal: This patchset will introduce a big change on hda_jack and hda_hdmi, So I sent the patcheset to oem-b 4 months ago. After 4 months of running oem-b kernel, there is no any regression reported on this patchset, now I am backporting the patchset to our focal kernel since our oem project is waiting for the patchset to be landed to ubuntu 5.4 kernel ASAP. This patchset are already merged to mainline kernel 5.5-rc and 5.6-rc, so there is no need to send the patchset to oem-5.6 or groovy kernel. [Impact] On some LENOVO I+N machines, when setting the graphic mode to discrete, The dp/hdmi audio on the Docking Gen2 can't work with this machine + LENOVO Docking Gen2, users can't find the hdmi audio entry in the gnome-sound-setting. [Fix] Nvidia developer submit the mst audio support to 5.5-rcN and 5.6-RC1, those patches could fix this issue. [Test Case] set the machien to discrete, plug the dock gen2 to it, then boot, after booting, plug hdmi or dp to dock gen2, the hdmi or dp audio works. test other machines without Nvidia graphic or without gen2, their hdmi/dp audio still work, and check other output/input devices like headphone, microphone, they all worked as well as before. [Regression Risk] one regression possibility is the audio jacks (including analogue and hdmi) can't work anymore, that means after users plug a headphone, headset, hdmi monitor or microphone to the audio jacks or hdmi connectors, the audio driver can't detect the plugging event. But regression's possibility is very low: - this patchset was already applied to oem-b kernel for 4 months, and oem projects didn't report any regression on the patchset - I tested the testing focal kernel with this patchset on many machines, includes a dell hda audio machine, a dell dmic machine, a Lenovo I+N hda audio machine, a lenovo I+N dmic machine, a lenovo I hda audio machine, a lenovo amd hda audio machine. The audio on them all worked as well as before. This is the justification for oem-b Drop the B, so far only need to merge this patchset to OEM-B first, After the patchset is widely verified with oem-b kernel, I send the patchset to B and F then. This patchset will add support of mst audio for nvidia hdmi/dp, this patchset changes lots of common code on hda_jack and hdmi codec, so it is not easy to say it is 100% safe for other machines, but our oem project needs this patchset to be backported to ubuntu kernel, because the tight sechdule of oem project, we backport this patchset to B and OEM-B first, if the hdmi audio works well for a period of time after this patchset is merged, I will backport this patchset to focal, maybe eoan as well. [Impact] On some LENOVO I+N machines, when setting the graphic mode to discrete, The dp/hdmi audio on the Docking Gen2 can't work with this machine + LENOVO Docking Gen2 [Fix] Nvidia developer submit the mst audio support to 5.5-rcN and 5.6-RC1, those patches could fix this issue. [Test Case] set the machien to discrete, plug the dock gen2 to it, then boot, after booting, plug hdmi or dp to dock gen2, the hdmi or dp audio works. test other machines without Nvidia graphic or without gen2, their hdmi/dp audio still work. [Regression Risk] Low, those patches come from mainline kernel, I have tested those patches on the machiens with or without nvidia hdmi, and on the machines with or without docks, all worked well as before. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1867704/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1892546] Re: Novalink (mkvterm command failure)
--- Comment From tyr...@us.ibm.com 2020-09-29 14:04 EDT--- Verfied 16.04. Still waiting on Focal and Bionic. ** Tags removed: verification-needed-xenial ** Tags added: verification-done-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/1892546 Title: Novalink (mkvterm command failure) Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Groovy: In Progress Bug description: SRU Justification: [Impact] * drmgr command is failing while trying to open console for IBMi on PowerVM LPAR [Fix] * 63ffcbdad738 "tty: hvcs: Don't NULL tty->driver_data until hvcs_cleanup()" [Test Case] * Create a VM from PowerVC on a Novalink managed host. * Unmanage and manage the VM, this problem gets reproduced. * grep the logs for "drmgr" [Regression Potential] The regression can be considered as very low, since: * limited to the IBM Hypervisor Virtual Console Server. * patched kernel where shared and successfully tested by IBM. * the worse case, if the cleanup is broken a new opened connection might break. [Other] * The patch got upstream accepted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1892546/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877425] Re: linux-azure: Enable FSGSBASE instructions to support SGX
** Also affects: linux-azure (Ubuntu Groovy) Importance: Undecided Assignee: Marcelo Cerri (mhcerri) Status: Fix Released ** Also affects: linux-azure-4.15 (Ubuntu Groovy) Importance: Undecided Status: In Progress ** Changed in: linux-azure-4.15 (Ubuntu Groovy) Status: In Progress => Invalid ** Changed in: linux-azure (Ubuntu Groovy) Status: Fix Released => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1877425 Title: linux-azure: Enable FSGSBASE instructions to support SGX Status in linux-azure package in Ubuntu: In Progress Status in linux-azure-4.15 package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Invalid Status in linux-azure-4.15 source package in Bionic: Fix Released Status in linux-azure source package in Eoan: Fix Released Status in linux-azure-4.15 source package in Eoan: Invalid Status in linux-azure source package in Focal: Fix Released Status in linux-azure-4.15 source package in Focal: Invalid Status in linux-azure source package in Groovy: In Progress Status in linux-azure-4.15 source package in Groovy: Invalid Bug description: X86 has instructions (RDFSBASE, RDGSBASE, WRFSBASE, and WRGSBASE) to support read/write of the FS/GS bases. Linux doesn't allow user mode code to execute these instructions by default. These instructions can be enabled for user mode by setting the 16th control bit of the CR4 register. Since only protected mode can modify the control registers, application programs and operating-system procedures (running at privilege levels 1, 2, or 3) are prevented from reading or loading the control registers. The kernel patch sets this CR4 register and handles the context switching to account for the fact that user mode can now modify the FS/GS base. A recent news article that talks about the performance benefits: https://phoronix.com/scan.php?page=news_item=Intel-FSGSBASE- Linux-2020. Another news article covers the performance information in a lot more detail by running a number of performance tests: https://www.phoronix.com/scan.php?page=article=linux-wip- fsgsbase=1 Patch set: https://lkml.org/lkml/2019/10/4/725 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1877425/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867704] Re: alsa/hdmi: support nvidia mst hdmi/dp audio
Log with linux-5.4.0-47 ** Attachment added: "painfo_linux47.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1867704/+attachment/5415374/+files/painfo_linux47.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1867704 Title: alsa/hdmi: support nvidia mst hdmi/dp audio Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Fix Released Status in linux source package in Bionic: Won't Fix Status in linux-oem source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Bug description: This is the justification for focal: This patchset will introduce a big change on hda_jack and hda_hdmi, So I sent the patcheset to oem-b 4 months ago. After 4 months of running oem-b kernel, there is no any regression reported on this patchset, now I am backporting the patchset to our focal kernel since our oem project is waiting for the patchset to be landed to ubuntu 5.4 kernel ASAP. This patchset are already merged to mainline kernel 5.5-rc and 5.6-rc, so there is no need to send the patchset to oem-5.6 or groovy kernel. [Impact] On some LENOVO I+N machines, when setting the graphic mode to discrete, The dp/hdmi audio on the Docking Gen2 can't work with this machine + LENOVO Docking Gen2, users can't find the hdmi audio entry in the gnome-sound-setting. [Fix] Nvidia developer submit the mst audio support to 5.5-rcN and 5.6-RC1, those patches could fix this issue. [Test Case] set the machien to discrete, plug the dock gen2 to it, then boot, after booting, plug hdmi or dp to dock gen2, the hdmi or dp audio works. test other machines without Nvidia graphic or without gen2, their hdmi/dp audio still work, and check other output/input devices like headphone, microphone, they all worked as well as before. [Regression Risk] one regression possibility is the audio jacks (including analogue and hdmi) can't work anymore, that means after users plug a headphone, headset, hdmi monitor or microphone to the audio jacks or hdmi connectors, the audio driver can't detect the plugging event. But regression's possibility is very low: - this patchset was already applied to oem-b kernel for 4 months, and oem projects didn't report any regression on the patchset - I tested the testing focal kernel with this patchset on many machines, includes a dell hda audio machine, a dell dmic machine, a Lenovo I+N hda audio machine, a lenovo I+N dmic machine, a lenovo I hda audio machine, a lenovo amd hda audio machine. The audio on them all worked as well as before. This is the justification for oem-b Drop the B, so far only need to merge this patchset to OEM-B first, After the patchset is widely verified with oem-b kernel, I send the patchset to B and F then. This patchset will add support of mst audio for nvidia hdmi/dp, this patchset changes lots of common code on hda_jack and hdmi codec, so it is not easy to say it is 100% safe for other machines, but our oem project needs this patchset to be backported to ubuntu kernel, because the tight sechdule of oem project, we backport this patchset to B and OEM-B first, if the hdmi audio works well for a period of time after this patchset is merged, I will backport this patchset to focal, maybe eoan as well. [Impact] On some LENOVO I+N machines, when setting the graphic mode to discrete, The dp/hdmi audio on the Docking Gen2 can't work with this machine + LENOVO Docking Gen2 [Fix] Nvidia developer submit the mst audio support to 5.5-rcN and 5.6-RC1, those patches could fix this issue. [Test Case] set the machien to discrete, plug the dock gen2 to it, then boot, after booting, plug hdmi or dp to dock gen2, the hdmi or dp audio works. test other machines without Nvidia graphic or without gen2, their hdmi/dp audio still work. [Regression Risk] Low, those patches come from mainline kernel, I have tested those patches on the machiens with or without nvidia hdmi, and on the machines with or without docks, all worked well as before. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1867704/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867704] Re: alsa/hdmi: support nvidia mst hdmi/dp audio
It is a nvidia GT1030 graphics card. We use the nvidia driver 440 and 450. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1867704 Title: alsa/hdmi: support nvidia mst hdmi/dp audio Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Fix Released Status in linux source package in Bionic: Won't Fix Status in linux-oem source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Bug description: This is the justification for focal: This patchset will introduce a big change on hda_jack and hda_hdmi, So I sent the patcheset to oem-b 4 months ago. After 4 months of running oem-b kernel, there is no any regression reported on this patchset, now I am backporting the patchset to our focal kernel since our oem project is waiting for the patchset to be landed to ubuntu 5.4 kernel ASAP. This patchset are already merged to mainline kernel 5.5-rc and 5.6-rc, so there is no need to send the patchset to oem-5.6 or groovy kernel. [Impact] On some LENOVO I+N machines, when setting the graphic mode to discrete, The dp/hdmi audio on the Docking Gen2 can't work with this machine + LENOVO Docking Gen2, users can't find the hdmi audio entry in the gnome-sound-setting. [Fix] Nvidia developer submit the mst audio support to 5.5-rcN and 5.6-RC1, those patches could fix this issue. [Test Case] set the machien to discrete, plug the dock gen2 to it, then boot, after booting, plug hdmi or dp to dock gen2, the hdmi or dp audio works. test other machines without Nvidia graphic or without gen2, their hdmi/dp audio still work, and check other output/input devices like headphone, microphone, they all worked as well as before. [Regression Risk] one regression possibility is the audio jacks (including analogue and hdmi) can't work anymore, that means after users plug a headphone, headset, hdmi monitor or microphone to the audio jacks or hdmi connectors, the audio driver can't detect the plugging event. But regression's possibility is very low: - this patchset was already applied to oem-b kernel for 4 months, and oem projects didn't report any regression on the patchset - I tested the testing focal kernel with this patchset on many machines, includes a dell hda audio machine, a dell dmic machine, a Lenovo I+N hda audio machine, a lenovo I+N dmic machine, a lenovo I hda audio machine, a lenovo amd hda audio machine. The audio on them all worked as well as before. This is the justification for oem-b Drop the B, so far only need to merge this patchset to OEM-B first, After the patchset is widely verified with oem-b kernel, I send the patchset to B and F then. This patchset will add support of mst audio for nvidia hdmi/dp, this patchset changes lots of common code on hda_jack and hdmi codec, so it is not easy to say it is 100% safe for other machines, but our oem project needs this patchset to be backported to ubuntu kernel, because the tight sechdule of oem project, we backport this patchset to B and OEM-B first, if the hdmi audio works well for a period of time after this patchset is merged, I will backport this patchset to focal, maybe eoan as well. [Impact] On some LENOVO I+N machines, when setting the graphic mode to discrete, The dp/hdmi audio on the Docking Gen2 can't work with this machine + LENOVO Docking Gen2 [Fix] Nvidia developer submit the mst audio support to 5.5-rcN and 5.6-RC1, those patches could fix this issue. [Test Case] set the machien to discrete, plug the dock gen2 to it, then boot, after booting, plug hdmi or dp to dock gen2, the hdmi or dp audio works. test other machines without Nvidia graphic or without gen2, their hdmi/dp audio still work. [Regression Risk] Low, those patches come from mainline kernel, I have tested those patches on the machiens with or without nvidia hdmi, and on the machines with or without docks, all worked well as before. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1867704/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1871306] Re: No sound from internal card chtmax98090 - missing UCM2 files in alsa-ucm-conf 1.2.2, available in alsa-ucm-conf 1.2.3
@Hui I added your pa-testing repo and updated/upgraded. Some more packages have been upgraded from pa-testing repo. Speakers and headset working almost fine (some crackles). Internal mic and headphone so low and so crackling to be unusable. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1871306 Title: No sound from internal card chtmax98090 - missing UCM2 files in alsa- ucm-conf 1.2.2, available in alsa-ucm-conf 1.2.3 Status in alsa-ucm-conf package in Ubuntu: Confirmed Bug description: Asus C300 (repurposed chromembook - bios flashed by Mr.Chromebox script) - Kubuntu Focal minimal fresh installation. The sound card is detected: I see it in the Plasma Widget, in pavucontrol, in alsamixer and it's not muted. I tried and add in /usr/share/alsa/ucm/chtmax98090/ the old style use case config files: no success. I tried and unmute speakers left and right in alsamixer: no success. I rapidly tested Ubuntu Mate Focal fresh install: I had exactly the same issue. I'm running on the same rig Debian Bullseye, kernel 5.4: sound card output and input are both working perfectly - I noticed that in Kubuntu alsamixer Kubuntu when I open it I have an entry HDA IntelPCH (the HDMI card), while in Debian I find Pulseaudio. I attach the alsa-info.sh output. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.17 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: KDE Date: Tue Apr 7 08:55:46 2020 InstallationDate: Installed on 2020-04-04 (2 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gabriel3937 F pulseaudio /dev/snd/controlC0: gabriel3937 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-04 (3 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:07dc Intel Corp. Bus 001 Device 003: ID 13d3:5657 IMC Networks USB2.0 UVC HD Webcam Bus 001 Device 002: ID 062a:4101 MosArt Semiconductor Corp. Wireless Keyboard/Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: GOOGLE Quawks Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=225cba91-c164-4882-95d4-4f9854a80fe9 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/17/2020 dmi.bios.vendor: coreboot dmi.bios.version: MrChromebox-4.11.2 dmi.board.name: Quawks dmi.board.vendor: GOOGLE dmi.board.version: 1.0 dmi.chassis.type: 9 dmi.chassis.vendor: GOOGLE dmi.modalias: dmi:bvncoreboot:bvrMrChromebox-4.11.2:bd03/17/2020:svnGOOGLE:pnQuawks:pvr1.0:rvnGOOGLE:rnQuawks:rvr1.0:cvnGOOGLE:ct9:cvr: dmi.product.name: Quawks dmi.product.version: 1.0 dmi.sys.vendor: GOOGLE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1871306/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867704] Re: alsa/hdmi: support nvidia mst hdmi/dp audio
For logs: https://www.vdr-portal.de/forum/index.php?thread/133200-yavdr- experimental-f%C3%BCr-ubuntu-20-04-yavdr-ansible- focal/=1329702#post1329702 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1867704 Title: alsa/hdmi: support nvidia mst hdmi/dp audio Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Fix Released Status in linux source package in Bionic: Won't Fix Status in linux-oem source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Bug description: This is the justification for focal: This patchset will introduce a big change on hda_jack and hda_hdmi, So I sent the patcheset to oem-b 4 months ago. After 4 months of running oem-b kernel, there is no any regression reported on this patchset, now I am backporting the patchset to our focal kernel since our oem project is waiting for the patchset to be landed to ubuntu 5.4 kernel ASAP. This patchset are already merged to mainline kernel 5.5-rc and 5.6-rc, so there is no need to send the patchset to oem-5.6 or groovy kernel. [Impact] On some LENOVO I+N machines, when setting the graphic mode to discrete, The dp/hdmi audio on the Docking Gen2 can't work with this machine + LENOVO Docking Gen2, users can't find the hdmi audio entry in the gnome-sound-setting. [Fix] Nvidia developer submit the mst audio support to 5.5-rcN and 5.6-RC1, those patches could fix this issue. [Test Case] set the machien to discrete, plug the dock gen2 to it, then boot, after booting, plug hdmi or dp to dock gen2, the hdmi or dp audio works. test other machines without Nvidia graphic or without gen2, their hdmi/dp audio still work, and check other output/input devices like headphone, microphone, they all worked as well as before. [Regression Risk] one regression possibility is the audio jacks (including analogue and hdmi) can't work anymore, that means after users plug a headphone, headset, hdmi monitor or microphone to the audio jacks or hdmi connectors, the audio driver can't detect the plugging event. But regression's possibility is very low: - this patchset was already applied to oem-b kernel for 4 months, and oem projects didn't report any regression on the patchset - I tested the testing focal kernel with this patchset on many machines, includes a dell hda audio machine, a dell dmic machine, a Lenovo I+N hda audio machine, a lenovo I+N dmic machine, a lenovo I hda audio machine, a lenovo amd hda audio machine. The audio on them all worked as well as before. This is the justification for oem-b Drop the B, so far only need to merge this patchset to OEM-B first, After the patchset is widely verified with oem-b kernel, I send the patchset to B and F then. This patchset will add support of mst audio for nvidia hdmi/dp, this patchset changes lots of common code on hda_jack and hdmi codec, so it is not easy to say it is 100% safe for other machines, but our oem project needs this patchset to be backported to ubuntu kernel, because the tight sechdule of oem project, we backport this patchset to B and OEM-B first, if the hdmi audio works well for a period of time after this patchset is merged, I will backport this patchset to focal, maybe eoan as well. [Impact] On some LENOVO I+N machines, when setting the graphic mode to discrete, The dp/hdmi audio on the Docking Gen2 can't work with this machine + LENOVO Docking Gen2 [Fix] Nvidia developer submit the mst audio support to 5.5-rcN and 5.6-RC1, those patches could fix this issue. [Test Case] set the machien to discrete, plug the dock gen2 to it, then boot, after booting, plug hdmi or dp to dock gen2, the hdmi or dp audio works. test other machines without Nvidia graphic or without gen2, their hdmi/dp audio still work. [Regression Risk] Low, those patches come from mainline kernel, I have tested those patches on the machiens with or without nvidia hdmi, and on the machines with or without docks, all worked well as before. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1867704/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867704] Re: alsa/hdmi: support nvidia mst hdmi/dp audio
Hello! We have the problem with linux-5.4.0-48 that the hdmi port (alsa_output.pci-_01_00.1.hdmi-stereo-extra1) not activ is after boot. linux-5.4.0-47 works fine. We use pulse audio. Ubuntu 20.04 linux-5.4.0-48 Active Profile: off linux-5.4.0-47 Active Profile: output:hdmi-stereo-extra1 Is it possible that this patch the reason is? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1867704 Title: alsa/hdmi: support nvidia mst hdmi/dp audio Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Fix Released Status in linux source package in Bionic: Won't Fix Status in linux-oem source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Bug description: This is the justification for focal: This patchset will introduce a big change on hda_jack and hda_hdmi, So I sent the patcheset to oem-b 4 months ago. After 4 months of running oem-b kernel, there is no any regression reported on this patchset, now I am backporting the patchset to our focal kernel since our oem project is waiting for the patchset to be landed to ubuntu 5.4 kernel ASAP. This patchset are already merged to mainline kernel 5.5-rc and 5.6-rc, so there is no need to send the patchset to oem-5.6 or groovy kernel. [Impact] On some LENOVO I+N machines, when setting the graphic mode to discrete, The dp/hdmi audio on the Docking Gen2 can't work with this machine + LENOVO Docking Gen2, users can't find the hdmi audio entry in the gnome-sound-setting. [Fix] Nvidia developer submit the mst audio support to 5.5-rcN and 5.6-RC1, those patches could fix this issue. [Test Case] set the machien to discrete, plug the dock gen2 to it, then boot, after booting, plug hdmi or dp to dock gen2, the hdmi or dp audio works. test other machines without Nvidia graphic or without gen2, their hdmi/dp audio still work, and check other output/input devices like headphone, microphone, they all worked as well as before. [Regression Risk] one regression possibility is the audio jacks (including analogue and hdmi) can't work anymore, that means after users plug a headphone, headset, hdmi monitor or microphone to the audio jacks or hdmi connectors, the audio driver can't detect the plugging event. But regression's possibility is very low: - this patchset was already applied to oem-b kernel for 4 months, and oem projects didn't report any regression on the patchset - I tested the testing focal kernel with this patchset on many machines, includes a dell hda audio machine, a dell dmic machine, a Lenovo I+N hda audio machine, a lenovo I+N dmic machine, a lenovo I hda audio machine, a lenovo amd hda audio machine. The audio on them all worked as well as before. This is the justification for oem-b Drop the B, so far only need to merge this patchset to OEM-B first, After the patchset is widely verified with oem-b kernel, I send the patchset to B and F then. This patchset will add support of mst audio for nvidia hdmi/dp, this patchset changes lots of common code on hda_jack and hdmi codec, so it is not easy to say it is 100% safe for other machines, but our oem project needs this patchset to be backported to ubuntu kernel, because the tight sechdule of oem project, we backport this patchset to B and OEM-B first, if the hdmi audio works well for a period of time after this patchset is merged, I will backport this patchset to focal, maybe eoan as well. [Impact] On some LENOVO I+N machines, when setting the graphic mode to discrete, The dp/hdmi audio on the Docking Gen2 can't work with this machine + LENOVO Docking Gen2 [Fix] Nvidia developer submit the mst audio support to 5.5-rcN and 5.6-RC1, those patches could fix this issue. [Test Case] set the machien to discrete, plug the dock gen2 to it, then boot, after booting, plug hdmi or dp to dock gen2, the hdmi or dp audio works. test other machines without Nvidia graphic or without gen2, their hdmi/dp audio still work. [Regression Risk] Low, those patches come from mainline kernel, I have tested those patches on the machiens with or without nvidia hdmi, and on the machines with or without docks, all worked well as before. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1867704/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894378] Re: Cannot boot after updating kernel to version 5.4.0-45
@b-9 There may be various options, depending on how comfortable you are with the command line. You could try to build a custom initramfs image with diagnostic tools, boot from it and dump the necessary info to a USB drive for example. Or clone the ubuntu kernel git repository and use git bisect to pinpoint the commit that introduced the issue. Definitely easier: boot your most recent working kernel normally and dump the requested information (lspci, dmesg etc.). Though the kernel version will not match exactly the information may help narrow down 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/1894378 Title: Cannot boot after updating kernel to version 5.4.0-45 Status in linux package in Ubuntu: Fix Released Bug description: After the kernel update from version 5.4.0-42 to version 5.4.0-45 a few days ago, the boot process is ending in a BusyBox shell. Apparently it cannot properly identify my M.2 NMVe SSD device where my root partition is. Indeed, it is not listed in /dev (precisely: nvme0 is listed in /dev, but nvme0n1 and its partitions are not). For now, I'm solving this problem by booting the previous kernel, 5.4.0-42. This works fine. Also, an earlier attempt ended in a different shell that presented the error message "Gave up on waiting for root file system device". The UUID it indicated as missing is the correct UUID of my root partition, which also appears on /etc/fstab. I tried to re-build initrd.img-5.4.0-45-generic, but to no avail. Let me also mention that in another computer with a non-M.2 SSD, kernel 5.4.0-45 boots properly. This bug seems to be the one mentioned in the following "Unix & Linux" forum question: https://unix.stackexchange.com/questions/607694/ubuntu-20-04-01-not-booting-after-kernel-update Many thanks in advance! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ami3801 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sat Sep 5 17:42:26 2020 HibernationDevice: RESUME=UUID=dd70dd06-717a-4acf-a85e-a9ad37cb92ea InstallationDate: Installed on 2017-10-04 (1066 days ago) InstallationMedia: Kubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IwConfig: enp0s31f6 no wireless extensions. lono wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 1532:022a Razer USA, Ltd Razer Cynosa Chroma Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 480M |__ Port 8: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 8: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 8: Dev 2, If 2, Class=Human Interface Device, Driver=usbhid, 12M MachineType: System manufacturer System Product Name ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic root=UUID=85262f0d-cb92-475a-8174-2d6316e199a9 ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.3 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-05-03 (125 days ago) dmi.bios.date: 06/20/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3807 dmi.board.asset.tag: Default string dmi.board.name: H110M-A/M.2 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3807:bd06/20/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-A/M.2:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894378/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1891684] Re: [amdgpu] Screen flickers after resuming from suspend
wow ok. i actually have a a acer aspire 5 with a 4500u i couldnt get ubuntu to boot on it so i abandoned it and re installed windows. is there a 20.10 iso available for download? On Mon, Sep 28, 2020 at 4:01 PM Richard Elkins <1891...@bugs.launchpad.net> wrote: > This could very well be an issue with the amdgpu kernel module or the > kernel itself. 20.04 uses kernel 5.4 I fixed my situation (similar) by > upgrading to 20.10 (beta) which uses 5.8 packages. Now, my power > management and suspend/resume actually work. > > My laptop (different than the nitro): Acer Aspire 5 4700U octacore APU > with built-in graphics. > > Good luck. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1891684 > > Title: > [amdgpu] Screen flickers after resuming from suspend > > Status in linux package in Ubuntu: > Incomplete > Status in xserver-xorg-video-amdgpu package in Ubuntu: > Incomplete > > Bug description: > when computer is coming out of suspension mode, i get terrible screen > flickers. Only way i have worked around this is a reboot. > > This video card is from sapphire > Nitro + SE 5700xt > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: xorg 1:7.7+19ubuntu14 > ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 > Uname: Linux 5.4.0-42-generic x86_64 > ApportVersion: 2.20.11-0ubuntu27.6 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' > CasperMD5CheckResult: skip > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Fri Aug 14 12:16:42 2020 > DistUpgraded: Fresh install > DistroCodename: focal > DistroVariant: ubuntu > GraphicsCard: >Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 > XT / 5700/5700 XT] [1002:731f] (rev c1) (prog-if 00 [VGA controller]) > Subsystem: Sapphire Technology Limited Navi 10 [Radeon RX 5600 > OEM/5600 XT / 5700/5700 XT] [1da2:e410] > InstallationDate: Installed on 2020-06-08 (66 days ago) > InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 > (20200423) > MachineType: System manufacturer System Product Name > ProcEnviron: >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic > root=UUID=de7b87e0-cf04-4f9f-978e-3646f7e7266d ro quiet splash vt.handoff=7 > SourcePackage: xorg > Symptom: display > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 06/17/2020 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: 2203 > dmi.board.asset.tag: Default string > dmi.board.name: TUF GAMING X570-PLUS > dmi.board.vendor: ASUSTeK COMPUTER INC. > dmi.board.version: Rev X.0x > dmi.chassis.asset.tag: Default string > dmi.chassis.type: 3 > dmi.chassis.vendor: Default string > dmi.chassis.version: Default string > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvr2203:bd06/17/2020:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX570-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: > dmi.product.family: To be filled by O.E.M. > dmi.product.name: System Product Name > dmi.product.sku: SKU > dmi.product.version: System Version > dmi.sys.vendor: System manufacturer > version.compiz: compiz N/A > version.libdrm2: libdrm2 2.4.101-2 > version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 > version.libgl1-mesa-glx: libgl1-mesa-glx N/A > version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A > version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 > version.xserver-xorg-video-intel: xserver-xorg-video-intel > 2:2.99.917+git20200226-1 > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891684/+subscriptions > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1891684 Title: [amdgpu] Screen flickers after resuming from suspend Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-video-amdgpu package in Ubuntu: Incomplete Bug description: when computer is coming out of suspension mode, i get terrible screen flickers. Only way i have worked around this is a reboot. This video card is from sapphire Nitro + SE 5700xt ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None
[Kernel-packages] [Bug 1822394] Re: [Dell BIOSes dated 27 Mar 2019, XPS 9575, Precision 5530 2-in-1] laptop keyboard & touchpad not working at gdm screen after boot
Thanks Joe! By chance can you upgrade to current BIOS too and get that dump again? There is that workaround now (blacklist intel-vbtn) which you should be able to use now if you have no other problems with current firmware. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822394 Title: [Dell BIOSes dated 27 Mar 2019, XPS 9575, Precision 5530 2-in-1] laptop keyboard & touchpad not working at gdm screen after boot Status in libinput package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: On a dell XPS 15 2-in-1 with the latest 1.4.0 bios, my touchpad and keyboard are unresponsive at the gdm login screen. Keyboard works to unlock encrypted harddrive before that though. If I plug in a USB keyboard or activate my bluetooth mouse, I can use those to log in, and then after logging in the laptop touchpad and keyboard work again. Logging out of the desktop results in the laptop touchpad and keyboard working on the gdm screen. Did not see this behavior before upgrading from 1.2.0 bios to 1.4.0 bios, but also had not rebooted in a while, so not sure if bios or package upgrades triggered this behavior. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gdm3 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 29 17:51:00 2019 InstallationDate: Installed on 2018-09-26 (184 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gdm3 UpgradeStatus: Upgraded to disco on 2019-03-11 (18 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1822394/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822394] Re: [Dell BIOSes dated 27 Mar 2019, XPS 9575, Precision 5530 2-in-1] laptop keyboard & touchpad not working at gdm screen after boot
1.2.0 firmware acpidump attached ** Attachment added: "1.2.0.acpidump" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822394/+attachment/5415318/+files/1.2.0.acpidump -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822394 Title: [Dell BIOSes dated 27 Mar 2019, XPS 9575, Precision 5530 2-in-1] laptop keyboard & touchpad not working at gdm screen after boot Status in libinput package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: On a dell XPS 15 2-in-1 with the latest 1.4.0 bios, my touchpad and keyboard are unresponsive at the gdm login screen. Keyboard works to unlock encrypted harddrive before that though. If I plug in a USB keyboard or activate my bluetooth mouse, I can use those to log in, and then after logging in the laptop touchpad and keyboard work again. Logging out of the desktop results in the laptop touchpad and keyboard working on the gdm screen. Did not see this behavior before upgrading from 1.2.0 bios to 1.4.0 bios, but also had not rebooted in a while, so not sure if bios or package upgrades triggered this behavior. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gdm3 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 29 17:51:00 2019 InstallationDate: Installed on 2018-09-26 (184 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gdm3 UpgradeStatus: Upgraded to disco on 2019-03-11 (18 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1822394/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895526] Re: ocfs2 file system no longer write - "disk full" despite lots of free space
ah, good point. I was on 5.4.X so this fix should work for 18.04 running that kernel as well. thanks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1895526 Title: ocfs2 file system no longer write - "disk full" despite lots of free space Status in linux package in Ubuntu: Fix Released Status in ocfs2-tools package in Ubuntu: Invalid Bug description: Fairly new server on Ubuntu 20.04.1 LTS, 5.4.0-47-generic kernel, DRBD device across 2 sites with one server in each site, ocfs2 filesystem on DRBD device, shared to local network using Samba (and also Samba-AD-DC for network). All packages from "normal" Ubuntu repositories. ocfs2-tools is Installed: 1.8.6-2ubuntu1. The filesystem is around 3.3 TB. Stored data amounted to 24% of this filesystem. Recent updates applied and server restarted Wed 9th Sept after which staff started reporting inability to save to server shares. Checked Samba settings as Windows error messages were at first showing permission issues, but following various checks no wrong Samba settings were found so restarted their server after which the errors were "no space left on disk". Checked on the server terminal and couldn't even "touch" an empty file but got "no space left on disk". Found an article describing limitations caused by ocfs2 cluster size, so copied all data out to a backup machine, recreated the ocfs2 file system using mkfs.ocfs2 -C 64K /dev/drbd0 but again the "no disk space" error keeps happening despite this now being an empty file system. Perhaps it wasn't a cluster size problem in the first instance. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ocfs2-tools 1.8.6-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Sep 14 12:23:35 2020 InstallationDate: Installed on 2020-05-06 (130 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ocfs2-tools UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895526/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1896726] Re: [UBUNTU 20.04.1] qemu (secure guest) crash due to gup_fast / dynamic page table folding issue
** Changed in: linux (Ubuntu Groovy)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1896726
Title:
[UBUNTU 20.04.1] qemu (secure guest) crash due to gup_fast / dynamic
page table folding issue
Status in Ubuntu on IBM z Systems:
In Progress
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Focal:
Incomplete
Status in linux source package in Groovy:
Fix Committed
Bug description:
Justification:
==
Secure KVM guest (using secure execution on Ubuntu Server 20.04 for s390x)
crashes happen from time to time during boot.
Such crashed guests ("reason=crashed" in the libvirt log) end up in hutoff
state instead of crashed state ( preserve is set).
The crash points to a kernel memory management problem, addressed by the
following patch/fix.
The modifications touch common memory management code,
but it will have no effect to architectures other than s390x.
This is ensured by the fact that only s390 provides / implements the new
helper functions.
And for s390x, this is actually a critical (and carefully tested) fix for a
(previous) regression, so it can hardly get any more regressive.
The patch landed upstream in linux-next, is in depth discussed
at LKML https://lkml.kernel.org/r/20190418100218.0a4afd51@mschwideX1
and here
https://lore.kernel.org/linux-arch/patch.git-943f1e5dcff2.your-ad-here.call-01599856292-ext-8676@work.hours/
and will soon land via the regular upstream stable release update for kernel
5.4 in focal, too.
The process already started:
https://lore.kernel.org/stable/patch-1.thread-41918b.git-41918be365c0.your-ad-here.call-01600439945-ext-8991@work.hours/
Hence this cherry-pick from the upstream patch should be added to groovy
to avoid any potential regression in case the patch landed in focal via the
upstream release update process,
but is not in groovy and someones upgrades from focal to groovy.
__
Secure Execution with Ubuntu 20.04, secure guest crash during boot
from time to time, crashed guest went into Shufoff state instead of
Crashed state (preserve is set), so I can't get a dump.
libvirt log file:
2020-04-21T16:35:39.382999Z qemu-system-s390x: Guest says index 19608 is
available
2020-04-21 16:35:44.831+: shutting down, reason=crashed
---uname output---
Linux ubu204uclg1002 5.4.0-25-generic #29-Ubuntu SMP Fri Apr 17 15:05:32 UTC
2020 s390x s390x s390x GNU/Linux
Machine Type = z15 8561
---Debugger---
A debugger is not configured
---Steps to Reproduce---
I have a setup with 72 KVM guests which I can start in secure or non-secure
mode. Starting all of them in secure mode back to back results in a number of
guests (4..8) in Shutoff state and reason=crashed in the libvirt log. I can
manually start the guest again no problem. Different guests are failing.
Host and guests are on latest Ubuntu 20.04.
The supposed fix (kernel memory management) has landed in Andrew Mortons mm
tree
https://lore.kernel.org/mm-commits/20200916003608.ib4ln%25a...@linux-foundation.org/T/#u
Please note: while this was found with secure execution, the bug is
actually present for non-KVM workloads as well.
The complete patch is this:
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=a338e69ba37286c0fc300ab7e6fa0227e6ca68b1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1896726/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1893921] Re: ipsec_offload in rtnetlink.sh from kselftests.net fails on s390x
** Tags added: sru-20200921 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1893921 Title: ipsec_offload in rtnetlink.sh from kselftests.net fails on s390x Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Confirmed Bug description: Testing failed on: s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/s390x/l/linux/20200901_162956_a95df@/log.gz The ipsec_offload in rtnetlink.sh from kselftests.net fails on s390x: 15:45:23 DEBUG| [stdout] # selftests: net: rtnetlink.sh 15:45:23 DEBUG| [stdout] # PASS: policy routing 15:45:23 DEBUG| [stdout] # PASS: route get 15:45:28 DEBUG| [stdout] # PASS: preferred_lft addresses have expired 15:45:28 DEBUG| [stdout] # PASS: promote_secondaries complete 15:45:28 DEBUG| [stdout] # PASS: tc htb hierarchy 15:45:29 DEBUG| [stdout] # PASS: gre tunnel endpoint 15:45:29 DEBUG| [stdout] # PASS: gretap 15:45:29 DEBUG| [stdout] # PASS: ip6gretap 15:45:29 DEBUG| [stdout] # PASS: erspan 15:45:29 DEBUG| [stdout] # PASS: ip6erspan 15:45:30 DEBUG| [stdout] # PASS: bridge setup 15:45:31 DEBUG| [stdout] # PASS: ipv6 addrlabel 15:45:31 DEBUG| [stdout] # PASS: set ifalias b14b1d80-dc0b-4a9b-9256-3ec3f86aa891 for test-dummy0 15:45:31 DEBUG| [stdout] # PASS: vrf 15:45:31 DEBUG| [stdout] # PASS: vxlan 15:45:31 DEBUG| [stdout] # FAIL: can't add fou port , skipping test 15:45:31 DEBUG| [stdout] # PASS: macsec 15:45:32 DEBUG| [stdout] # PASS: ipsec 15:45:33 DEBUG| [stdout] # 3,7c3,7 15:45:33 DEBUG| [stdout] # < sa[0]spi=0x0009 proto=0x32 salt=0x64636261 crypt=1 15:45:33 DEBUG| [stdout] # < sa[0]key=0x31323334 35363738 39303132 33343536 15:45:33 DEBUG| [stdout] # < sa[1] rx ipaddr=0x c0a87b03 15:45:33 DEBUG| [stdout] # < sa[1]spi=0x0009 proto=0x32 salt=0x64636261 crypt=1 15:45:33 DEBUG| [stdout] # < sa[1]key=0x31323334 35363738 39303132 33343536 15:45:33 DEBUG| [stdout] # --- 15:45:33 DEBUG| [stdout] # > sa[0]spi=0x0009 proto=0x32 salt=0x61626364 crypt=1 15:45:33 DEBUG| [stdout] # > sa[0]key=0x34333231 38373635 32313039 36353433 15:45:33 DEBUG| [stdout] # > sa[1] rx ipaddr=0x 037ba8c0 15:45:33 DEBUG| [stdout] # > sa[1]spi=0x0009 proto=0x32 salt=0x61626364 crypt=1 15:45:33 DEBUG| [stdout] # > sa[1]key=0x34333231 38373635 32313039 36353433 15:45:33 DEBUG| [stdout] # FAIL: ipsec_offload incorrect driver data 15:45:33 DEBUG| [stdout] # FAIL: ipsec_offload 15:45:33 DEBUG| [stdout] # PASS: bridge fdb get 15:45:33 DEBUG| [stdout] # PASS: neigh get 15:45:33 DEBUG| [stdout] not ok 11 selftests: net: rtnetlink.sh # exit=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1893921/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1897755] [NEW] Fix broken e1000e device after S3
Public bug reported: [Impact] Intel I219 ethernet on several HP workstations has a chance to stop working after S3. [Fix] Increase polling timeout on MDIC ready bit so we wait a bit longer for Intel ME. [Test] Without the fix, the I219 ethernet breaks in 10 S3 cycle. With the fix applied, the ethernet keeps working after 1000+ S3 stress test. [Regression Potential] If the firmware/hardware is _really_ broken, we'll waste a bit more time to wait the device resume. Otherwise no functional change. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Medium Status: Confirmed ** Affects: linux-oem-5.6 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Focal) Importance: Medium Status: Confirmed ** Affects: linux-oem-5.6 (Ubuntu Focal) Importance: Medium Status: Confirmed ** Affects: linux (Ubuntu Groovy) Importance: Medium Status: Confirmed ** Affects: linux-oem-5.6 (Ubuntu Groovy) Importance: Undecided Status: Invalid ** Tags: oem-priority originate-from-1894929 stella ** Also affects: linux-oem-5.6 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.6 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: linux-oem-5.6 (Ubuntu Groovy) Importance: Undecided Status: New ** Changed in: linux-oem-5.6 (Ubuntu Groovy) Status: New => Invalid ** Changed in: linux-oem-5.6 (Ubuntu Focal) Status: New => Confirmed ** Changed in: linux (Ubuntu Groovy) Status: New => Confirmed ** Changed in: linux (Ubuntu Focal) Status: New => Confirmed ** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Groovy) Importance: Undecided => Medium ** Changed in: linux-oem-5.6 (Ubuntu Focal) Importance: Undecided => Medium ** Tags added: oem-priority originate-from-1894929 stella -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1897755 Title: Fix broken e1000e device after S3 Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: Confirmed Status in linux-oem-5.6 source package in Focal: Confirmed Status in linux source package in Groovy: Confirmed Status in linux-oem-5.6 source package in Groovy: Invalid Bug description: [Impact] Intel I219 ethernet on several HP workstations has a chance to stop working after S3. [Fix] Increase polling timeout on MDIC ready bit so we wait a bit longer for Intel ME. [Test] Without the fix, the I219 ethernet breaks in 10 S3 cycle. With the fix applied, the ethernet keeps working after 1000+ S3 stress test. [Regression Potential] If the firmware/hardware is _really_ broken, we'll waste a bit more time to wait the device resume. Otherwise no functional change. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1897755/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895526] Re: ocfs2 file system no longer write - "disk full" despite lots of free space
>From what I've seen the issues for me related to the kernel image versions 5.4.0-45 and 5.4.0-47. When we upgraded to 5.4.0-48 this is what resulted in the necessary fixes for us. My servers were Ubuntu 20.04 fresh installations, but your 18.04 servers are likely to use perhaps 4.15.0-118 or thereabouts unless you've manually installed later Linux kernels, so I would suggest that the answer to your question depends on your current kernel version. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1895526 Title: ocfs2 file system no longer write - "disk full" despite lots of free space Status in linux package in Ubuntu: Fix Released Status in ocfs2-tools package in Ubuntu: Invalid Bug description: Fairly new server on Ubuntu 20.04.1 LTS, 5.4.0-47-generic kernel, DRBD device across 2 sites with one server in each site, ocfs2 filesystem on DRBD device, shared to local network using Samba (and also Samba-AD-DC for network). All packages from "normal" Ubuntu repositories. ocfs2-tools is Installed: 1.8.6-2ubuntu1. The filesystem is around 3.3 TB. Stored data amounted to 24% of this filesystem. Recent updates applied and server restarted Wed 9th Sept after which staff started reporting inability to save to server shares. Checked Samba settings as Windows error messages were at first showing permission issues, but following various checks no wrong Samba settings were found so restarted their server after which the errors were "no space left on disk". Checked on the server terminal and couldn't even "touch" an empty file but got "no space left on disk". Found an article describing limitations caused by ocfs2 cluster size, so copied all data out to a backup machine, recreated the ocfs2 file system using mkfs.ocfs2 -C 64K /dev/drbd0 but again the "no disk space" error keeps happening despite this now being an empty file system. Perhaps it wasn't a cluster size problem in the first instance. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ocfs2-tools 1.8.6-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Sep 14 12:23:35 2020 InstallationDate: Installed on 2020-05-06 (130 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ocfs2-tools UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895526/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1896725] Re: xenial 4.4.0-191-generic in -proposed has a regression
For now we are going with reverting the Xen change that introduced the regression with 4.4 kernels. ** Changed in: linux (Ubuntu Xenial) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1896725 Title: xenial 4.4.0-191-generic in -proposed has a regression Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Committed Bug description: [Impact] The new xenial kernel in -proposed, 4.4.0-191-generic, and its derivatives, such as 4.4.0-1115-aws suffer a kernel panic on boot on AWS. I tested t2.micro and t2.medium, it happens every time. Simply install the kernel from -proposed and reboot, we get the following oops: [0.549557] BUG: unable to handle kernel paging request at ff5f3000 [0.552000] IP: [] mp_irqdomain_activate+0x5f/0xa0 [0.552000] PGD 1e0f067 PUD 1e11067 PMD 1e12067 PTE 0 [0.552000] Oops: 0002 [#1] SMP [0.552000] Modules linked in: [0.552000] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 4.4.0-191-generic #221-Ubuntu [0.552000] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006 [0.552000] task: 88010a0f ti: 88010a0f8000 task.ti: 88010a0f8000 [0.552000] RIP: 0010:[] [] mp_irqdomain_activate+0x5f/0xa0 [0.552000] RSP: :88010a0fbc48 EFLAGS: 00010086 [0.552000] RAX: 0086 RBX: 88010a1df480 RCX: [0.552000] RDX: ff5f3000 RSI: 0001 RDI: 0020c000 [0.552000] RBP: 88010a0fbc50 R08: 81ebdfd0 R09: [0.552000] R10: 0011 R11: 0009 R12: 88010ad95400 [0.552000] R13: 0001 R14: 0009 R15: 88010a1fc480 [0.552000] FS: () GS:88010b24() knlGS: [0.552000] CS: 0010 DS: ES: CR0: 80050033 [0.552000] CR2: ff5f3000 CR3: 01e0a000 CR4: 00160670 [0.552000] DR0: DR1: DR2: [0.552000] DR3: DR6: fffe0ff0 DR7: 0400 [0.552000] Stack: [0.552000] 88010ac0ba58 88010a0fbc70 810ea644 88010ac0ba00 [0.552000] 88010ac0ba58 88010a0fbca0 810e6d88 810e1009 [0.552000] 88010ac0ba00 88010ac0baa0 88010a1fc480 88010a0fbd38 [0.552000] Call Trace: [0.552000] [] irq_domain_activate_irq+0x44/0x50 [0.552000] [] irq_startup+0x38/0x90 [0.552000] [] ? vprintk_default+0x29/0x40 [0.552000] [] __setup_irq+0x5a2/0x650 [0.552000] [] ? kmem_cache_alloc_trace+0x1d4/0x1f0 [0.552000] [] ? acpi_osi_handler+0xb0/0xb0 [0.552000] [] request_threaded_irq+0xfb/0x1a0 [0.552000] [] ? acpi_osi_handler+0xb0/0xb0 [0.552000] [] ? acpi_ev_sci_dispatch+0x64/0x64 [0.552000] [] acpi_os_install_interrupt_handler+0xaa/0x100 [0.552000] [] ? acpi_sleep_proc_init+0x28/0x28 [0.552000] [] acpi_ev_install_sci_handler+0x23/0x25 [0.552000] [] acpi_ev_install_xrupt_handlers+0x1c/0x6c [0.552000] [] acpi_enable_subsystem+0x8f/0x93 [0.552000] [] acpi_init+0x8b/0x2c4 [0.552000] [] ? kasprintf+0x4e/0x70 [0.552000] [] ? acpi_sleep_proc_init+0x28/0x28 [0.552000] [] do_one_initcall+0xb5/0x200 [0.552000] [] ? parse_args+0x29a/0x4a0 [0.552000] [] kernel_init_freeable+0x177/0x218 [0.552000] [] ? rest_init+0x80/0x80 [0.552000] [] kernel_init+0xe/0xe0 [0.552000] [] ret_from_fork+0x55/0x80 [0.552000] [] ? rest_init+0x80/0x80 [0.552000] Code: 8d 1c d2 8d ba 0b 02 00 00 44 8d 51 11 42 8b 14 dd 74 ec 10 82 c1 e7 0c 48 63 ff 81 e2 ff 0f 00 00 48 81 ea 00 10 80 00 48 29 fa <44> 89 12 89 72 10 42 8b 14 dd 74 ec 10 82 83 c1 10 81 e2 ff 0f [0.552000] RIP [] mp_irqdomain_activate+0x5f/0xa0 [0.996006] RSP [0.996006] CR2: ff5f3000 [0.996006] ---[ end trace 1d0c3bd610d641a0 ]--- [1.012018] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0009 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1896725/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1897299] Re: mwifiex stops working after kernel upgrade
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Bionic)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Groovy)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1897299
Title:
mwifiex stops working after kernel upgrade
Status in HWE Next:
Fix Released
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
Fix Committed
Status in linux source package in Bionic:
In Progress
Status in linux source package in Focal:
In Progress
Status in linux source package in Groovy:
In Progress
Bug description:
== Impact ==
Marvell WiFi cards supported by the mwifiex driver may fail to connect to
some access points after kernel upgrade.
This is caused by the commit
commit e18696786548244914f36ec3c46ac99c53df99c3
Author: Dan Carpenter
Date: Wed Jul 8 14:58:57 2020 +0300
mwifiex: Prevent memory corruption handling keys
The length of the key comes from the network and it's a 16 bit number. It
needs to be capped to prevent a buffer overflow.
Fixes: 5e6e3a92b9a4 ("wireless: mwifiex: initial commit for Marvell
mwifiex driver")
Signed-off-by: Dan Carpenter
Acked-by: Ganapathi Bhat
Signed-off-by: Kalle Valo
Link: https://lore.kernel.org/r/20200708115857.GA13729@mwanda
The commit added a check to mwifiex_ret_802_11_key_material_v2() to
make sure the key length doesn't larger than the key buffer size
before copying it. The allocated key buffer is 16-byte long. In some
cases the key would be 32-byte long and hence the check fails. One
thing to note is that this commit is not the cause of the problem,
instead it just makes the issue visible.
The commit is included in Ubuntu-4.4.0-190.220, Ubuntu-4.15.0-119.120,
Ubuntu-5.4.0-48.52, and Ubuntu-5.8.0-18.19.
== Fix ==
There's already a fix in the mainline which increase the key buffer size to
32 bytes:
commit 4afc850e2e9e781976fb2c7852ce7bac374af938
Author: Maximilian Luz
Date: Tue Aug 25 17:38:29 2020 +0200
mwifiex: Increase AES key storage size to 256 bits
Following commit e18696786548 ("mwifiex: Prevent memory corruption
handling keys") the mwifiex driver fails to authenticate with certain
networks, specifically networks with 256 bit keys, and repeatedly asks
for the password. The kernel log repeats the following lines (id and
bssid redacted):
mwifiex_pcie :01:00.0: info: trying to associate to '' bssid
mwifiex_pcie :01:00.0: info: associated to bssid
successfully
mwifiex_pcie :01:00.0: crypto keys added
mwifiex_pcie :01:00.0: info: successfully disconnected from
: reason code 3
Tracking down this problem lead to the overflow check introduced by the
aforementioned commit into mwifiex_ret_802_11_key_material_v2(). This
check fails on networks with 256 bit keys due to the current storage
size for AES keys in struct mwifiex_aes_param being only 128 bit.
To fix this issue, increase the storage size for AES keys to 256 bit.
Fixes: e18696786548 ("mwifiex: Prevent memory corruption handling keys")
Signed-off-by: Maximilian Luz
Reported-by: Kaloyan Nikolov
Tested-by: Kaloyan Nikolov
Reviewed-by: Dan Carpenter
Reviewed-by: Brian Norris
Tested-by: Brian Norris
Signed-off-by: Kalle Valo
Link:
https://lore.kernel.org/r/20200825153829.38043-1-luzmaximil...@gmail.com
== Regression Potential ==
Low. While the fix increases the buffer size, it still checks and make sure
data to be copy can fit into the buffer. Also the commit does fix the issue we
saw in the Cert lab.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1897299/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895526] Re: ocfs2 file system no longer write - "disk full" despite lots of free space
Thanks for the quick fix! Will this fix also apply for 18.04? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1895526 Title: ocfs2 file system no longer write - "disk full" despite lots of free space Status in linux package in Ubuntu: Fix Released Status in ocfs2-tools package in Ubuntu: Invalid Bug description: Fairly new server on Ubuntu 20.04.1 LTS, 5.4.0-47-generic kernel, DRBD device across 2 sites with one server in each site, ocfs2 filesystem on DRBD device, shared to local network using Samba (and also Samba-AD-DC for network). All packages from "normal" Ubuntu repositories. ocfs2-tools is Installed: 1.8.6-2ubuntu1. The filesystem is around 3.3 TB. Stored data amounted to 24% of this filesystem. Recent updates applied and server restarted Wed 9th Sept after which staff started reporting inability to save to server shares. Checked Samba settings as Windows error messages were at first showing permission issues, but following various checks no wrong Samba settings were found so restarted their server after which the errors were "no space left on disk". Checked on the server terminal and couldn't even "touch" an empty file but got "no space left on disk". Found an article describing limitations caused by ocfs2 cluster size, so copied all data out to a backup machine, recreated the ocfs2 file system using mkfs.ocfs2 -C 64K /dev/drbd0 but again the "no disk space" error keeps happening despite this now being an empty file system. Perhaps it wasn't a cluster size problem in the first instance. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ocfs2-tools 1.8.6-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Sep 14 12:23:35 2020 InstallationDate: Installed on 2020-05-06 (130 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ocfs2-tools UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895526/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1897751] [NEW] Introduce the new NVIDIA 455 series
Public bug reported: [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] ** Affects: linux-restricted-modules (Ubuntu) Importance: Undecided Assignee: Alberto Milone (albertomilone) Status: New ** Affects: nvidia-graphics-drivers-450 (Ubuntu) Importance: Undecided Assignee: Alberto Milone (albertomilone) Status: New ** Also affects: nvidia-graphics-drivers-450 (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-450 (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) -- 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/1897751 Title: Introduce the new NVIDIA 455 series Status in linux-restricted-modules package in Ubuntu: New Status in nvidia-graphics-drivers-450 package in Ubuntu: New Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1897751/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1897745] Re: Surface Pro 4 with Linux 5.4.x: WPA: Failed to set GTK to the driver
The output of `ubuntu-bug` is attached, and contains everything that’s needed as far as I can see. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1897745 Title: Surface Pro 4 with Linux 5.4.x: WPA: Failed to set GTK to the driver Status in linux package in Ubuntu: Incomplete Bug description: On the Surface Pro 4 with USB Marvell Bluetooth/WLAN device, upgrading from Ubuntu 18.04 with Linux 4.15.x to Ubuntu 20.04 with Linux 5.4.x, only WPA2 Enterprise networks stop working, but other continue to work. WPA: Failed to set GTK to the driver (alg=2 keylen=32 keyidx=1) Starting Ubuntu 20.04.1 with Linux 4.15.x, the problem is gone. Testing Ubuntu’s Linux mainline builds [1], the problem is still there in 5.4.68, but gone in 5.5-rc1. We do not have the resources to bisect this further, as the user needs the device back now. [1]: https://kernel.ubuntu.com/~kernel-ppa/mainline/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1897745/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822394] Re: [Dell BIOSes dated 27 Mar 2019, XPS 9575, Precision 5530 2-in-1] laptop keyboard & touchpad not working at gdm screen after boot
To anyone who has been affected - there is a discussion going on the kernel mailing lists regarding this issue and it would be helpful if you can provide an acpidump. You can attach it to this bug (or file a kernel bugzilla and attach it there). Desired would be the 1.2.0 firmware (which some people have downgraded to workaround this issue) as well as a current affected firmware. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822394 Title: [Dell BIOSes dated 27 Mar 2019, XPS 9575, Precision 5530 2-in-1] laptop keyboard & touchpad not working at gdm screen after boot Status in libinput package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: On a dell XPS 15 2-in-1 with the latest 1.4.0 bios, my touchpad and keyboard are unresponsive at the gdm login screen. Keyboard works to unlock encrypted harddrive before that though. If I plug in a USB keyboard or activate my bluetooth mouse, I can use those to log in, and then after logging in the laptop touchpad and keyboard work again. Logging out of the desktop results in the laptop touchpad and keyboard working on the gdm screen. Did not see this behavior before upgrading from 1.2.0 bios to 1.4.0 bios, but also had not rebooted in a while, so not sure if bios or package upgrades triggered this behavior. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gdm3 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 29 17:51:00 2019 InstallationDate: Installed on 2018-09-26 (184 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gdm3 UpgradeStatus: Upgraded to disco on 2019-03-11 (18 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1822394/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894910] Re: fallocate swapfile has holes on 5.8 ext4, causes: swapon failed: Invalid argument
** Merge proposal linked: https://code.launchpad.net/~paride/curtin/+git/curtin/+merge/391534 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1894910 Title: fallocate swapfile has holes on 5.8 ext4, causes: swapon failed: Invalid argument Status in linux package in Ubuntu: Confirmed Bug description: 1) Groovy 2) root@ubuntu:/home/ubuntu# apt-cache policy linux-image-generic linux-image-generic: Installed: 5.8.0.18.22 Candidate: 5.8.0.18.22 Version table: *** 5.8.0.18.22 500 500 http://archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status 3) swapon --verbose /swap.img enables swap file successfully 4) swapon returns error, says swapfile has holes. Curtin creates file-based swap files with fallocate: fallocate -l XXXM /swap.img When booting Groovy (5.8 kernel), the swapfile fails to load, complains it has holes root@ubuntu:/home/ubuntu# swapon --verbose /swap.img swapon: /swap.img: found signature [pagesize=4096, signature=swap] swapon: /swap.img: pagesize=4096, swapsize=1251999744, devsize=1251999744 swapon /swap.img [ 178.283022] swapon: swapfile has holes swapon: /swap.img: swapon failed: Invalid argument root@ubuntu:/home/ubuntu# uname -r 5.8.0-18-generic This configuration works fine on Focal (5.4) and older. Previous Groovy kernels, (5.7) also worked. It may be related to: https://lkml.org/lkml/2020/9/4/259 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-generic 5.8.0.18.22 ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 Uname: Linux 5.8.0-18-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 8 21:38 seq crw-rw 1 root audio 116, 33 Sep 8 21:38 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu44 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Date: Tue Sep 8 21:44:13 2020 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=vt220 PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 bochs-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-18-generic root=UUID=ce45bbaf-5a44-4487-b89e-035c2dd40657 ro console=ttyS0 systemd.mask=snapd.seeded.service systemd.mask=snapd.service panic=-1 softlockup_panic=1 hung_task_panic=1 nmi_watchdog=panic,1 ip=:BOOTIF:dhcp RelatedPackageVersions: linux-restricted-modules-5.8.0-18-generic N/A linux-backports-modules-5.8.0-18-generic N/A linux-firmware1.190 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-focal dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-focal:cvnQEMU:ct1:cvrpc-i440fx-focal: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-focal dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894910/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894910] Re: fallocate swapfile has holes on 5.8 ext4, causes: swapon failed: Invalid argument
** Merge proposal linked: https://code.launchpad.net/~paride/curtin/+git/curtin/+merge/391533 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1894910 Title: fallocate swapfile has holes on 5.8 ext4, causes: swapon failed: Invalid argument Status in linux package in Ubuntu: Confirmed Bug description: 1) Groovy 2) root@ubuntu:/home/ubuntu# apt-cache policy linux-image-generic linux-image-generic: Installed: 5.8.0.18.22 Candidate: 5.8.0.18.22 Version table: *** 5.8.0.18.22 500 500 http://archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status 3) swapon --verbose /swap.img enables swap file successfully 4) swapon returns error, says swapfile has holes. Curtin creates file-based swap files with fallocate: fallocate -l XXXM /swap.img When booting Groovy (5.8 kernel), the swapfile fails to load, complains it has holes root@ubuntu:/home/ubuntu# swapon --verbose /swap.img swapon: /swap.img: found signature [pagesize=4096, signature=swap] swapon: /swap.img: pagesize=4096, swapsize=1251999744, devsize=1251999744 swapon /swap.img [ 178.283022] swapon: swapfile has holes swapon: /swap.img: swapon failed: Invalid argument root@ubuntu:/home/ubuntu# uname -r 5.8.0-18-generic This configuration works fine on Focal (5.4) and older. Previous Groovy kernels, (5.7) also worked. It may be related to: https://lkml.org/lkml/2020/9/4/259 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-generic 5.8.0.18.22 ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 Uname: Linux 5.8.0-18-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 8 21:38 seq crw-rw 1 root audio 116, 33 Sep 8 21:38 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu44 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Date: Tue Sep 8 21:44:13 2020 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=vt220 PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 bochs-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-18-generic root=UUID=ce45bbaf-5a44-4487-b89e-035c2dd40657 ro console=ttyS0 systemd.mask=snapd.seeded.service systemd.mask=snapd.service panic=-1 softlockup_panic=1 hung_task_panic=1 nmi_watchdog=panic,1 ip=:BOOTIF:dhcp RelatedPackageVersions: linux-restricted-modules-5.8.0-18-generic N/A linux-backports-modules-5.8.0-18-generic N/A linux-firmware1.190 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-focal dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-focal:cvnQEMU:ct1:cvrpc-i440fx-focal: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-focal dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894910/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1897745] 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 1897745 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1897745 Title: Surface Pro 4 with Linux 5.4.x: WPA: Failed to set GTK to the driver Status in linux package in Ubuntu: Incomplete Bug description: On the Surface Pro 4 with USB Marvell Bluetooth/WLAN device, upgrading from Ubuntu 18.04 with Linux 4.15.x to Ubuntu 20.04 with Linux 5.4.x, only WPA2 Enterprise networks stop working, but other continue to work. WPA: Failed to set GTK to the driver (alg=2 keylen=32 keyidx=1) Starting Ubuntu 20.04.1 with Linux 4.15.x, the problem is gone. Testing Ubuntu’s Linux mainline builds [1], the problem is still there in 5.4.68, but gone in 5.5-rc1. We do not have the resources to bisect this further, as the user needs the device back now. [1]: https://kernel.ubuntu.com/~kernel-ppa/mainline/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1897745/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1879328] Re: ubuntu_kvm_unit_test failed to build on Focal PowerPC
** Tags added: sru-20200921 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1879328 Title: ubuntu_kvm_unit_test failed to build on Focal PowerPC Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: Compilation failed with: ld: ld: powerpc/selftest.elfpowerpc/spapr_hcall.elf: error: PHDR segment not covered by LOAD segment: error: PHDR segment not covered by LOAD segment ld: powerpc/rtas.elf: error: PHDR segment not covered by LOAD segment ld: powerpc/emulator.elf: error: PHDR segment not covered by LOAD segment ld: powerpc/sprs.elf: error: PHDR segment not covered by LOAD segment ld: powerpc/tm.elf: error: PHDR segment not covered by LOAD segment Full build log: $ sudo make -j156 standalone gcc -std=gnu99 -ffreestanding -O2 -msoft-float -mabi=no-altivec -mno-altivec -I /home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/lib -I /home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/lib/libfdt -I lib -Wa,-mregnames -g -MMD -MF powerpc/.selftest.d -Wall -Wwrite-strings -Wclobbered -Wempty-body -Wuninitialized -Wignored-qualifiers -Wunused-but-set-parameter -Wmissing-prototypes -Wstrict-prototypes -Werror -fomit-frame-pointer-Wno-frame-address -fno-pic -no-pie -Wmissing-parameter-type -Wold-style-declaration -Woverride-init -mlittle-endian -c -o powerpc/selftest.aux.o /home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/lib/auxinfo.c \ -DPROGNAME=\"powerpc/selftest.elf\" gcc -std=gnu99 -ffreestanding -O2 -msoft-float -mabi=no-altivec -mno-altivec -I /home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/lib -I /home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/lib/libfdt -I lib -Wa,-mregnames -g -MMD -MF powerpc/.spapr_hcall.d -Wall -Wwrite-strings -Wclobbered -Wempty-body -Wuninitialized -Wignored-qualifiers -Wunused-but-set-parameter -Wmissing-prototypes -Wstrict-prototypes -Werror -fomit-frame-pointer-Wno-frame-address -fno-pic -no-pie -Wmissing-parameter-type -Wold-style-declaration -Woverride-init -mlittle-endian -c -o powerpc/spapr_hcall.aux.o /home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/lib/auxinfo.c \ -DPROGNAME=\"powerpc/spapr_hcall.elf\" gcc -std=gnu99 -ffreestanding -O2 -msoft-float -mabi=no-altivec -mno-altivec -I /home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/lib -I /home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/lib/libfdt -I lib -Wa,-mregnames -g -MMD -MF powerpc/.rtas.d -Wall -Wwrite-strings -Wclobbered -Wempty-body -Wuninitialized -Wignored-qualifiers -Wunused-but-set-parameter -Wmissing-prototypes -Wstrict-prototypes -Werror -fomit-frame-pointer-Wno-frame-address -fno-pic -no-pie -Wmissing-parameter-type -Wold-style-declaration -Woverride-init -mlittle-endian -c -o powerpc/rtas.aux.o /home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/lib/auxinfo.c \ -DPROGNAME=\"powerpc/rtas.elf\" gcc -std=gnu99 -ffreestanding -O2 -msoft-float -mabi=no-altivec -mno-altivec -I /home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/lib -I /home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/lib/libfdt -I lib -Wa,-mregnames -g -MMD -MF powerpc/.emulator.d -Wall -Wwrite-strings -Wclobbered -Wempty-body -Wuninitialized -Wignored-qualifiers -Wunused-but-set-parameter -Wmissing-prototypes -Wstrict-prototypes -Werror -fomit-frame-pointer-Wno-frame-address -fno-pic -no-pie -Wmissing-parameter-type -Wold-style-declaration -Woverride-init -mlittle-endian -c -o powerpc/emulator.aux.o /home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/lib/auxinfo.c \ -DPROGNAME=\"powerpc/emulator.elf\" gcc -std=gnu99 -ffreestanding -O2 -msoft-float -mabi=no-altivec -mno-altivec -I /home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/lib -I /home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/lib/libfdt -I lib -Wa,-mregnames -g -MMD -MF powerpc/.tm.d -Wall -Wwrite-strings -Wclobbered -Wempty-body -Wuninitialized -Wignored-qualifiers -Wunused-but-set-parameter -Wmissing-prototypes -Wstrict-prototypes -Werror -fomit-frame-pointer-Wno-frame-address -fno-pic -no-pie -Wmissing-parameter-type -Wold-style-declaration -Woverride-init -mlittle-endian -c -o powerpc/tm.aux.o /home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/lib/auxinfo.c \ -DPROGNAME=\"powerpc/tm.elf\" gcc -std=gnu99 -ffreestanding -O2 -msoft-float -mabi=no-altivec -mno-altivec -I /home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/lib -I
[Kernel-packages] [Bug 1847982] Re: memcg_subgroup_charge from controllers in ubuntu_ltp failed on D/E
BTW for comment above (comment #5) it's the Focal 5.4 lowlatency kernel, the same node passed with the focal generic kernel -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1847982 Title: memcg_subgroup_charge from controllers in ubuntu_ltp failed on D/E Status in ubuntu-kernel-tests: New Status in linux-azure package in Ubuntu: New Status in linux-kvm package in Ubuntu: New Status in linux-oracle package in Ubuntu: New Status in linux-azure source package in Disco: Won't Fix Status in linux-kvm source package in Disco: Won't Fix Status in linux-oracle source package in Disco: Won't Fix Bug description: Issue found on Azure Disco kernel 5.0.0-1023.24 Failed on instance: * Standard_GS2 * Standard_D16s_v3 Passed on instance: * Standard_F32s_v2 * Standard_L8s_v2 * Standard_L4s * Standard_L8s_v2 (Although it has passed on these instances, but they all have the same test output, just the pids are different) Test failed with: /opt/ltp/testcases/bin/memcg_subgroup_charge.sh: 522: echo: echo: I/O error tag=memcg_subgroup_charge stime=1570239843 dur=3 exit=exited stat=1 core=no cu=7 cs=11 startup='Sat Oct 5 01:44:03 2019' memcg_subgroup_charge 1 TINFO: Starting test 1 /opt/ltp/testcases/bin/memcg_subgroup_charge.sh: 522: echo: echo: I/O error memcg_subgroup_charge 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_subgroup_charge 1 TINFO: Running memcg_process --mmap-anon -s 135168 memcg_subgroup_charge 1 TINFO: Warming up pid: 119041 memcg_subgroup_charge 1 TINFO: Process is still here after warm up: 119041 memcg_subgroup_charge 1 TPASS: rss is 135168 as expected memcg_subgroup_charge 2 TPASS: rss is 0 as expected memcg_subgroup_charge 3 TINFO: Starting test 2 /opt/ltp/testcases/bin/memcg_subgroup_charge.sh: 522: echo: echo: I/O error memcg_subgroup_charge 3 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_subgroup_charge 3 TINFO: Running memcg_process --mmap-anon -s 135168 memcg_subgroup_charge 3 TINFO: Warming up pid: 119071 memcg_subgroup_charge 3 TINFO: Process is still here after warm up: 119071 memcg_subgroup_charge 3 TFAIL: rss is 0, 135168 expected memcg_subgroup_charge 4 TPASS: rss is 0 as expected memcg_subgroup_charge 5 TINFO: Starting test 3 /opt/ltp/testcases/bin/memcg_subgroup_charge.sh: 522: echo: echo: I/O error memcg_subgroup_charge 5 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_subgroup_charge 5 TINFO: Running memcg_process --mmap-anon -s 135168 memcg_subgroup_charge 5 TINFO: Warming up pid: 119094 memcg_subgroup_charge 5 TINFO: Process is still here after warm up: 119094 memcg_subgroup_charge 5 TPASS: rss is 135168 as expected memcg_subgroup_charge 6 TPASS: rss is 0 as expected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1847982/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1896725] Re: xenial 4.4.0-191-generic in -proposed has a regression
** Changed in: linux (Ubuntu Xenial) Status: Confirmed => 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/1896725 Title: xenial 4.4.0-191-generic in -proposed has a regression Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: In Progress Bug description: [Impact] The new xenial kernel in -proposed, 4.4.0-191-generic, and its derivatives, such as 4.4.0-1115-aws suffer a kernel panic on boot on AWS. I tested t2.micro and t2.medium, it happens every time. Simply install the kernel from -proposed and reboot, we get the following oops: [0.549557] BUG: unable to handle kernel paging request at ff5f3000 [0.552000] IP: [] mp_irqdomain_activate+0x5f/0xa0 [0.552000] PGD 1e0f067 PUD 1e11067 PMD 1e12067 PTE 0 [0.552000] Oops: 0002 [#1] SMP [0.552000] Modules linked in: [0.552000] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 4.4.0-191-generic #221-Ubuntu [0.552000] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006 [0.552000] task: 88010a0f ti: 88010a0f8000 task.ti: 88010a0f8000 [0.552000] RIP: 0010:[] [] mp_irqdomain_activate+0x5f/0xa0 [0.552000] RSP: :88010a0fbc48 EFLAGS: 00010086 [0.552000] RAX: 0086 RBX: 88010a1df480 RCX: [0.552000] RDX: ff5f3000 RSI: 0001 RDI: 0020c000 [0.552000] RBP: 88010a0fbc50 R08: 81ebdfd0 R09: [0.552000] R10: 0011 R11: 0009 R12: 88010ad95400 [0.552000] R13: 0001 R14: 0009 R15: 88010a1fc480 [0.552000] FS: () GS:88010b24() knlGS: [0.552000] CS: 0010 DS: ES: CR0: 80050033 [0.552000] CR2: ff5f3000 CR3: 01e0a000 CR4: 00160670 [0.552000] DR0: DR1: DR2: [0.552000] DR3: DR6: fffe0ff0 DR7: 0400 [0.552000] Stack: [0.552000] 88010ac0ba58 88010a0fbc70 810ea644 88010ac0ba00 [0.552000] 88010ac0ba58 88010a0fbca0 810e6d88 810e1009 [0.552000] 88010ac0ba00 88010ac0baa0 88010a1fc480 88010a0fbd38 [0.552000] Call Trace: [0.552000] [] irq_domain_activate_irq+0x44/0x50 [0.552000] [] irq_startup+0x38/0x90 [0.552000] [] ? vprintk_default+0x29/0x40 [0.552000] [] __setup_irq+0x5a2/0x650 [0.552000] [] ? kmem_cache_alloc_trace+0x1d4/0x1f0 [0.552000] [] ? acpi_osi_handler+0xb0/0xb0 [0.552000] [] request_threaded_irq+0xfb/0x1a0 [0.552000] [] ? acpi_osi_handler+0xb0/0xb0 [0.552000] [] ? acpi_ev_sci_dispatch+0x64/0x64 [0.552000] [] acpi_os_install_interrupt_handler+0xaa/0x100 [0.552000] [] ? acpi_sleep_proc_init+0x28/0x28 [0.552000] [] acpi_ev_install_sci_handler+0x23/0x25 [0.552000] [] acpi_ev_install_xrupt_handlers+0x1c/0x6c [0.552000] [] acpi_enable_subsystem+0x8f/0x93 [0.552000] [] acpi_init+0x8b/0x2c4 [0.552000] [] ? kasprintf+0x4e/0x70 [0.552000] [] ? acpi_sleep_proc_init+0x28/0x28 [0.552000] [] do_one_initcall+0xb5/0x200 [0.552000] [] ? parse_args+0x29a/0x4a0 [0.552000] [] kernel_init_freeable+0x177/0x218 [0.552000] [] ? rest_init+0x80/0x80 [0.552000] [] kernel_init+0xe/0xe0 [0.552000] [] ret_from_fork+0x55/0x80 [0.552000] [] ? rest_init+0x80/0x80 [0.552000] Code: 8d 1c d2 8d ba 0b 02 00 00 44 8d 51 11 42 8b 14 dd 74 ec 10 82 c1 e7 0c 48 63 ff 81 e2 ff 0f 00 00 48 81 ea 00 10 80 00 48 29 fa <44> 89 12 89 72 10 42 8b 14 dd 74 ec 10 82 83 c1 10 81 e2 ff 0f [0.552000] RIP [] mp_irqdomain_activate+0x5f/0xa0 [0.996006] RSP [0.996006] CR2: ff5f3000 [0.996006] ---[ end trace 1d0c3bd610d641a0 ]--- [1.012018] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0009 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1896725/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894910] Re: fallocate swapfile has holes on 5.8 ext4, causes: swapon failed: Invalid argument
** Merge proposal linked: https://code.launchpad.net/~paride/curtin/+git/curtin/+merge/391530 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1894910 Title: fallocate swapfile has holes on 5.8 ext4, causes: swapon failed: Invalid argument Status in linux package in Ubuntu: Confirmed Bug description: 1) Groovy 2) root@ubuntu:/home/ubuntu# apt-cache policy linux-image-generic linux-image-generic: Installed: 5.8.0.18.22 Candidate: 5.8.0.18.22 Version table: *** 5.8.0.18.22 500 500 http://archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status 3) swapon --verbose /swap.img enables swap file successfully 4) swapon returns error, says swapfile has holes. Curtin creates file-based swap files with fallocate: fallocate -l XXXM /swap.img When booting Groovy (5.8 kernel), the swapfile fails to load, complains it has holes root@ubuntu:/home/ubuntu# swapon --verbose /swap.img swapon: /swap.img: found signature [pagesize=4096, signature=swap] swapon: /swap.img: pagesize=4096, swapsize=1251999744, devsize=1251999744 swapon /swap.img [ 178.283022] swapon: swapfile has holes swapon: /swap.img: swapon failed: Invalid argument root@ubuntu:/home/ubuntu# uname -r 5.8.0-18-generic This configuration works fine on Focal (5.4) and older. Previous Groovy kernels, (5.7) also worked. It may be related to: https://lkml.org/lkml/2020/9/4/259 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-generic 5.8.0.18.22 ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 Uname: Linux 5.8.0-18-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 8 21:38 seq crw-rw 1 root audio 116, 33 Sep 8 21:38 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu44 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Date: Tue Sep 8 21:44:13 2020 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=vt220 PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 bochs-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-18-generic root=UUID=ce45bbaf-5a44-4487-b89e-035c2dd40657 ro console=ttyS0 systemd.mask=snapd.seeded.service systemd.mask=snapd.service panic=-1 softlockup_panic=1 hung_task_panic=1 nmi_watchdog=panic,1 ip=:BOOTIF:dhcp RelatedPackageVersions: linux-restricted-modules-5.8.0-18-generic N/A linux-backports-modules-5.8.0-18-generic N/A linux-firmware1.190 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-focal dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-focal:cvnQEMU:ct1:cvrpc-i440fx-focal: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-focal dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894910/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1897745] [NEW] Surface Pro 4 with Linux 5.4.x: WPA: Failed to set GTK to the driver
Public bug reported: On the Surface Pro 4 with USB Marvell Bluetooth/WLAN device, upgrading from Ubuntu 18.04 with Linux 4.15.x to Ubuntu 20.04 with Linux 5.4.x, only WPA2 Enterprise networks stop working, but other continue to work. WPA: Failed to set GTK to the driver (alg=2 keylen=32 keyidx=1) Starting Ubuntu 20.04.1 with Linux 4.15.x, the problem is gone. Testing Ubuntu’s Linux mainline builds [1], the problem is still there in 5.4.68, but gone in 5.5-rc1. We do not have the resources to bisect this further, as the user needs the device back now. [1]: https://kernel.ubuntu.com/~kernel-ppa/mainline/ ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: regression-release ** Attachment added: "Output of `ubuntu-bug --save /dev/shm/… linux-image-5.4.0-48-generic" https://bugs.launchpad.net/bugs/1897745/+attachment/5415294/+files/20200929%E2%80%93linux-5.4.0-48%E2%80%93dmesg.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/1897745 Title: Surface Pro 4 with Linux 5.4.x: WPA: Failed to set GTK to the driver Status in linux package in Ubuntu: New Bug description: On the Surface Pro 4 with USB Marvell Bluetooth/WLAN device, upgrading from Ubuntu 18.04 with Linux 4.15.x to Ubuntu 20.04 with Linux 5.4.x, only WPA2 Enterprise networks stop working, but other continue to work. WPA: Failed to set GTK to the driver (alg=2 keylen=32 keyidx=1) Starting Ubuntu 20.04.1 with Linux 4.15.x, the problem is gone. Testing Ubuntu’s Linux mainline builds [1], the problem is still there in 5.4.68, but gone in 5.5-rc1. We do not have the resources to bisect this further, as the user needs the device back now. [1]: https://kernel.ubuntu.com/~kernel-ppa/mainline/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1897745/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1847982] Re: memcg_subgroup_charge from controllers in ubuntu_ltp failed on D/E
Found on F 5.4.0-49.53 node amaura startup='Tue Sep 22 01:41:38 2020' memcg_subgroup_charge 1 TINFO: Starting test 1 /opt/ltp/testcases/bin/memcg_subgroup_charge.sh: 522: echo: echo: I/O error memcg_subgroup_charge 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_subgroup_charge 1 TINFO: Running memcg_process --mmap-anon -s 135168 memcg_subgroup_charge 1 TINFO: Warming up pid: 961276 memcg_subgroup_charge 1 TINFO: Process is still here after warm up: 961276 memcg_subgroup_charge 1 TBROK: timeouted on memory.usage_in_bytes tag=memcg_subgroup_charge stime=1600738898 dur=12 exit=exited stat=2 core=no cu=7 cs=5 ** Tags added: 5.4 focal sru-20200921 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1847982 Title: memcg_subgroup_charge from controllers in ubuntu_ltp failed on D/E Status in ubuntu-kernel-tests: New Status in linux-azure package in Ubuntu: New Status in linux-kvm package in Ubuntu: New Status in linux-oracle package in Ubuntu: New Status in linux-azure source package in Disco: Won't Fix Status in linux-kvm source package in Disco: Won't Fix Status in linux-oracle source package in Disco: Won't Fix Bug description: Issue found on Azure Disco kernel 5.0.0-1023.24 Failed on instance: * Standard_GS2 * Standard_D16s_v3 Passed on instance: * Standard_F32s_v2 * Standard_L8s_v2 * Standard_L4s * Standard_L8s_v2 (Although it has passed on these instances, but they all have the same test output, just the pids are different) Test failed with: /opt/ltp/testcases/bin/memcg_subgroup_charge.sh: 522: echo: echo: I/O error tag=memcg_subgroup_charge stime=1570239843 dur=3 exit=exited stat=1 core=no cu=7 cs=11 startup='Sat Oct 5 01:44:03 2019' memcg_subgroup_charge 1 TINFO: Starting test 1 /opt/ltp/testcases/bin/memcg_subgroup_charge.sh: 522: echo: echo: I/O error memcg_subgroup_charge 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_subgroup_charge 1 TINFO: Running memcg_process --mmap-anon -s 135168 memcg_subgroup_charge 1 TINFO: Warming up pid: 119041 memcg_subgroup_charge 1 TINFO: Process is still here after warm up: 119041 memcg_subgroup_charge 1 TPASS: rss is 135168 as expected memcg_subgroup_charge 2 TPASS: rss is 0 as expected memcg_subgroup_charge 3 TINFO: Starting test 2 /opt/ltp/testcases/bin/memcg_subgroup_charge.sh: 522: echo: echo: I/O error memcg_subgroup_charge 3 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_subgroup_charge 3 TINFO: Running memcg_process --mmap-anon -s 135168 memcg_subgroup_charge 3 TINFO: Warming up pid: 119071 memcg_subgroup_charge 3 TINFO: Process is still here after warm up: 119071 memcg_subgroup_charge 3 TFAIL: rss is 0, 135168 expected memcg_subgroup_charge 4 TPASS: rss is 0 as expected memcg_subgroup_charge 5 TINFO: Starting test 3 /opt/ltp/testcases/bin/memcg_subgroup_charge.sh: 522: echo: echo: I/O error memcg_subgroup_charge 5 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_subgroup_charge 5 TINFO: Running memcg_process --mmap-anon -s 135168 memcg_subgroup_charge 5 TINFO: Warming up pid: 119094 memcg_subgroup_charge 5 TINFO: Process is still here after warm up: 119094 memcg_subgroup_charge 5 TPASS: rss is 135168 as expected memcg_subgroup_charge 6 TPASS: rss is 0 as expected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1847982/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1896726] Re: [UBUNTU 20.04.1] qemu (secure guest) crash due to gup_fast / dynamic page table folding issue
Okay - very good - many thx, Klaus!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1896726
Title:
[UBUNTU 20.04.1] qemu (secure guest) crash due to gup_fast / dynamic
page table folding issue
Status in Ubuntu on IBM z Systems:
In Progress
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Focal:
Incomplete
Status in linux source package in Groovy:
In Progress
Bug description:
Justification:
==
Secure KVM guest (using secure execution on Ubuntu Server 20.04 for s390x)
crashes happen from time to time during boot.
Such crashed guests ("reason=crashed" in the libvirt log) end up in hutoff
state instead of crashed state ( preserve is set).
The crash points to a kernel memory management problem, addressed by the
following patch/fix.
The modifications touch common memory management code,
but it will have no effect to architectures other than s390x.
This is ensured by the fact that only s390 provides / implements the new
helper functions.
And for s390x, this is actually a critical (and carefully tested) fix for a
(previous) regression, so it can hardly get any more regressive.
The patch landed upstream in linux-next, is in depth discussed
at LKML https://lkml.kernel.org/r/20190418100218.0a4afd51@mschwideX1
and here
https://lore.kernel.org/linux-arch/patch.git-943f1e5dcff2.your-ad-here.call-01599856292-ext-8676@work.hours/
and will soon land via the regular upstream stable release update for kernel
5.4 in focal, too.
The process already started:
https://lore.kernel.org/stable/patch-1.thread-41918b.git-41918be365c0.your-ad-here.call-01600439945-ext-8991@work.hours/
Hence this cherry-pick from the upstream patch should be added to groovy
to avoid any potential regression in case the patch landed in focal via the
upstream release update process,
but is not in groovy and someones upgrades from focal to groovy.
__
Secure Execution with Ubuntu 20.04, secure guest crash during boot
from time to time, crashed guest went into Shufoff state instead of
Crashed state (preserve is set), so I can't get a dump.
libvirt log file:
2020-04-21T16:35:39.382999Z qemu-system-s390x: Guest says index 19608 is
available
2020-04-21 16:35:44.831+: shutting down, reason=crashed
---uname output---
Linux ubu204uclg1002 5.4.0-25-generic #29-Ubuntu SMP Fri Apr 17 15:05:32 UTC
2020 s390x s390x s390x GNU/Linux
Machine Type = z15 8561
---Debugger---
A debugger is not configured
---Steps to Reproduce---
I have a setup with 72 KVM guests which I can start in secure or non-secure
mode. Starting all of them in secure mode back to back results in a number of
guests (4..8) in Shutoff state and reason=crashed in the libvirt log. I can
manually start the guest again no problem. Different guests are failing.
Host and guests are on latest Ubuntu 20.04.
The supposed fix (kernel memory management) has landed in Andrew Mortons mm
tree
https://lore.kernel.org/mm-commits/20200916003608.ib4ln%25a...@linux-foundation.org/T/#u
Please note: while this was found with secure execution, the bug is
actually present for non-KVM workloads as well.
The complete patch is this:
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=a338e69ba37286c0fc300ab7e6fa0227e6ca68b1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1896726/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1871306] Re: No sound from internal card chtmax98090 - missing UCM2 files in alsa-ucm-conf 1.2.2, available in alsa-ucm-conf 1.2.3
＠Gabriele, Please add this ppa: ppa:hui.wang/pa-testing and install the testing alsa-ucm-conf 1.2.2-1ubuntu0.4.1+test, reboot and test. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1871306 Title: No sound from internal card chtmax98090 - missing UCM2 files in alsa- ucm-conf 1.2.2, available in alsa-ucm-conf 1.2.3 Status in alsa-ucm-conf package in Ubuntu: Confirmed Bug description: Asus C300 (repurposed chromembook - bios flashed by Mr.Chromebox script) - Kubuntu Focal minimal fresh installation. The sound card is detected: I see it in the Plasma Widget, in pavucontrol, in alsamixer and it's not muted. I tried and add in /usr/share/alsa/ucm/chtmax98090/ the old style use case config files: no success. I tried and unmute speakers left and right in alsamixer: no success. I rapidly tested Ubuntu Mate Focal fresh install: I had exactly the same issue. I'm running on the same rig Debian Bullseye, kernel 5.4: sound card output and input are both working perfectly - I noticed that in Kubuntu alsamixer Kubuntu when I open it I have an entry HDA IntelPCH (the HDMI card), while in Debian I find Pulseaudio. I attach the alsa-info.sh output. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.17 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: KDE Date: Tue Apr 7 08:55:46 2020 InstallationDate: Installed on 2020-04-04 (2 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gabriel3937 F pulseaudio /dev/snd/controlC0: gabriel3937 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-04 (3 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:07dc Intel Corp. Bus 001 Device 003: ID 13d3:5657 IMC Networks USB2.0 UVC HD Webcam Bus 001 Device 002: ID 062a:4101 MosArt Semiconductor Corp. Wireless Keyboard/Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: GOOGLE Quawks Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=225cba91-c164-4882-95d4-4f9854a80fe9 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/17/2020 dmi.bios.vendor: coreboot dmi.bios.version: MrChromebox-4.11.2 dmi.board.name: Quawks dmi.board.vendor: GOOGLE dmi.board.version: 1.0 dmi.chassis.type: 9 dmi.chassis.vendor: GOOGLE dmi.modalias: dmi:bvncoreboot:bvrMrChromebox-4.11.2:bd03/17/2020:svnGOOGLE:pnQuawks:pvr1.0:rvnGOOGLE:rnQuawks:rvr1.0:cvnGOOGLE:ct9:cvr: dmi.product.name: Quawks dmi.product.version: 1.0 dmi.sys.vendor: GOOGLE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1871306/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1896726] Comment bridged from LTC Bugzilla
--- Comment From klaus.theur...@de.ibm.com 2020-09-29 08:58 EDT---
With kernel ubu204 5.4.0-49-generic from Frank Heimes/Canonical:
ran a 8 and 16 guest (secure) scenario with MongoDB, same performance, no qemu
crash, no wiredtiger crash looks good to me.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1896726
Title:
[UBUNTU 20.04.1] qemu (secure guest) crash due to gup_fast / dynamic
page table folding issue
Status in Ubuntu on IBM z Systems:
In Progress
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Focal:
Incomplete
Status in linux source package in Groovy:
In Progress
Bug description:
Justification:
==
Secure KVM guest (using secure execution on Ubuntu Server 20.04 for s390x)
crashes happen from time to time during boot.
Such crashed guests ("reason=crashed" in the libvirt log) end up in hutoff
state instead of crashed state ( preserve is set).
The crash points to a kernel memory management problem, addressed by the
following patch/fix.
The modifications touch common memory management code,
but it will have no effect to architectures other than s390x.
This is ensured by the fact that only s390 provides / implements the new
helper functions.
And for s390x, this is actually a critical (and carefully tested) fix for a
(previous) regression, so it can hardly get any more regressive.
The patch landed upstream in linux-next, is in depth discussed
at LKML https://lkml.kernel.org/r/20190418100218.0a4afd51@mschwideX1
and here
https://lore.kernel.org/linux-arch/patch.git-943f1e5dcff2.your-ad-here.call-01599856292-ext-8676@work.hours/
and will soon land via the regular upstream stable release update for kernel
5.4 in focal, too.
The process already started:
https://lore.kernel.org/stable/patch-1.thread-41918b.git-41918be365c0.your-ad-here.call-01600439945-ext-8991@work.hours/
Hence this cherry-pick from the upstream patch should be added to groovy
to avoid any potential regression in case the patch landed in focal via the
upstream release update process,
but is not in groovy and someones upgrades from focal to groovy.
__
Secure Execution with Ubuntu 20.04, secure guest crash during boot
from time to time, crashed guest went into Shufoff state instead of
Crashed state (preserve is set), so I can't get a dump.
libvirt log file:
2020-04-21T16:35:39.382999Z qemu-system-s390x: Guest says index 19608 is
available
2020-04-21 16:35:44.831+: shutting down, reason=crashed
---uname output---
Linux ubu204uclg1002 5.4.0-25-generic #29-Ubuntu SMP Fri Apr 17 15:05:32 UTC
2020 s390x s390x s390x GNU/Linux
Machine Type = z15 8561
---Debugger---
A debugger is not configured
---Steps to Reproduce---
I have a setup with 72 KVM guests which I can start in secure or non-secure
mode. Starting all of them in secure mode back to back results in a number of
guests (4..8) in Shutoff state and reason=crashed in the libvirt log. I can
manually start the guest again no problem. Different guests are failing.
Host and guests are on latest Ubuntu 20.04.
The supposed fix (kernel memory management) has landed in Andrew Mortons mm
tree
https://lore.kernel.org/mm-commits/20200916003608.ib4ln%25a...@linux-foundation.org/T/#u
Please note: while this was found with secure execution, the bug is
actually present for non-KVM workloads as well.
The complete patch is this:
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=a338e69ba37286c0fc300ab7e6fa0227e6ca68b1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1896726/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1847105] Re: very slow disk creation, snapshotting
Hello Andreas, or anyone else affected, Accepted virt-manager into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/virt- manager/1:2.2.1-3ubuntu2.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: virt-manager (Ubuntu Focal) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-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/1847105 Title: very slow disk creation, snapshotting Status in virt-manager: Fix Released Status in Native ZFS for Linux: New Status in libvirt package in Ubuntu: Triaged Status in virt-manager package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: New Status in libvirt source package in Bionic: Invalid Status in virt-manager source package in Bionic: Invalid Status in zfs-linux source package in Bionic: Won't Fix Status in libvirt source package in Disco: Won't Fix Status in virt-manager source package in Disco: Won't Fix Status in zfs-linux source package in Disco: Won't Fix Status in libvirt source package in Focal: Triaged Status in virt-manager source package in Focal: Fix Committed Status in libvirt source package in Groovy: Triaged Bug description: [Impact] * The defaults of virt-manager for disk allocation always worked fine when qcow2 had nothing but sparse support. So sparse=True vs sparse=False made no difference. So it always set sparse=False. Then qcow2 grows non-sparse support, and virt-manager is suddenly defaulting to it, which is not the intention. * For upgraders from pre-Focal this was a regression in two ways: a) allocation of qcow changed to non-sparse (fallocate based) potentially consuming more space b) depending on the underlying FS this made the allocation much slower * Fix by applying the upstream change that Defaults to sparse when requested format isn't raw (for raw the assumption ill stay that users do that for runtime performance, so non-sparse on those stays as-is) [Test Case] * open virt-manager and create a new guest which includes creating a new image for it * when clicking "finish" the image will be created (which e.g. on ZFS will take quite some time) * In the background grep ps output if the qemu-img call for qcow (the default) is using "preallocation=fallocate" (wrong) or "preallocation=metadata" (correct) [Regression Potential] * For upgraders from pre-focal it actually ensures behavior stays as is (no change/regression there) * For users of ZFS where the allocation was slow it fixes this slowness. * But for people using Focal all the time and on non-ZFS there will be a behavior change in no more doing falloc pre-allocating the qemu image. To be cleear there are four modes: 1. no allocation 2. metadata allocation - is initially larger but can improve performance when the image needs to grow 3. falloc - preallocates space for image by calling posix_fallocate 4. full - writes data to the underlying storage The fix changes the default from 3->2 which it always was and should be. As the patch says: "If users want to override it, they can do it via custom created storage." (To be clear, upstream changed this as we fixed it here, so on further upgrades what we apply here will be the behavior anyway, it seems wrong to keep Focal the only one in between kept different) * [racb] The code path being added special cases the 'raw' format and in handling of the default sparse setting. Areas of potential regression are therefore in the handling of the default and override of the default in the cases of both 'raw' and not 'raw'. [Other Info] * The slowness effect
[Kernel-packages] [Bug 1887490] Re: Add/Backport EPYC-v3 and EPYC-Rome CPU model
Hello Markus, or anyone else affected, Accepted qemu into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/qemu/1:4.2-3ubuntu6.7 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: qemu (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags removed: verification-done-focal ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1887490 Title: Add/Backport EPYC-v3 and EPYC-Rome CPU model Status in libvirt package in Ubuntu: Incomplete Status in linux package in Ubuntu: Invalid Status in qemu package in Ubuntu: Fix Released Status in libvirt source package in Focal: Incomplete Status in linux source package in Focal: Fix Committed Status in qemu source package in Focal: Fix Committed Bug description: ## Qemu SRU ## [Impact] * CPU definitions are added to qemu as these CPUs are known. And due to that over time are missing in former releases. * To really benefit from the new features of these chips they have to be known, therefore new type additions done by upstream should be backported if they generally apply and do not depend on SRU-critical changes. * This backports two upstream fixes that just add definitions (no control flow changes) [Test Case] * Probe qemu for the known CPU types (works on all HW) $ qemu-system-x86_64 -cpu ? | grep EPYC Focal without fix: x86 EPYC (alias configured by machine type) x86 EPYC-IBPB (alias of EPYC-v2) x86 EPYC-v1 AMD EPYC Processor x86 EPYC-v2 AMD EPYC Processor (with IBPB) Focal with fix also adds: x86 EPYC-Rome (alias configured by machine type) x86 EPYC-Rome-v1 AMD EPYC-Rome Processor x86 EPYC-v3 AMD EPYC Processor * Given such HW is available start a KVM guest using those new types Since we don't have libvirt support (yet) do so directly in qemu commandline like (bootloader is enough) $ qemu-system-x86_64 -cpu EPYC-Rome -machine pc-q35-focal,accel=kvm -nographic $ qemu-system-x86_64 -cpu EPYC-v3 -machine pc-q35-focal,accel=kvm -nographic [Regression Potential] * This adds new CPU types to the list of known CPUs defining their name and features. Generally the changes are contained to those new types and only active when selected - and usually only selectable on such new machines. Therefore not a lot should change for other users. One thing thou, if a user selected an unversioned type (which in this case only can be "EPYC") by default it will pick the latest subversion that applies. In this case the behavior will change and pick EPYC-v3 after the fix. But this is the whole purpose of versioned (stay as is) and unversioned (move with updates) CPU types - so that should be ok. The EPYC-Rome type didn't exist in Focal before, so it can't "change" for users. [Other Info] * Depends on the new kernel 5.4.0-49 or later (Currently in focal-proposed) --- Qemu in focal has already support for most (except amd-stibp) flags of this model. Please backport the following patches: https://github.com/qemu/qemu/commit/a16e8dbc043720abcb37fc7dca313e720b4e0f0c https://github.com/qemu/qemu/commit/143c30d4d346831a09e59e9af45afdca0331e819 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1887490/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1895526] Re: ocfs2 file system no longer write - "disk full" despite lots of free space
** Changed in: ocfs2-tools (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1895526 Title: ocfs2 file system no longer write - "disk full" despite lots of free space Status in linux package in Ubuntu: Fix Released Status in ocfs2-tools package in Ubuntu: Invalid Bug description: Fairly new server on Ubuntu 20.04.1 LTS, 5.4.0-47-generic kernel, DRBD device across 2 sites with one server in each site, ocfs2 filesystem on DRBD device, shared to local network using Samba (and also Samba-AD-DC for network). All packages from "normal" Ubuntu repositories. ocfs2-tools is Installed: 1.8.6-2ubuntu1. The filesystem is around 3.3 TB. Stored data amounted to 24% of this filesystem. Recent updates applied and server restarted Wed 9th Sept after which staff started reporting inability to save to server shares. Checked Samba settings as Windows error messages were at first showing permission issues, but following various checks no wrong Samba settings were found so restarted their server after which the errors were "no space left on disk". Checked on the server terminal and couldn't even "touch" an empty file but got "no space left on disk". Found an article describing limitations caused by ocfs2 cluster size, so copied all data out to a backup machine, recreated the ocfs2 file system using mkfs.ocfs2 -C 64K /dev/drbd0 but again the "no disk space" error keeps happening despite this now being an empty file system. Perhaps it wasn't a cluster size problem in the first instance. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ocfs2-tools 1.8.6-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Sep 14 12:23:35 2020 InstallationDate: Installed on 2020-05-06 (130 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ocfs2-tools UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895526/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1896725] Re: xenial 4.4.0-191-generic in -proposed has a regression
** 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/1896725 Title: xenial 4.4.0-191-generic in -proposed has a regression Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: [Impact] The new xenial kernel in -proposed, 4.4.0-191-generic, and its derivatives, such as 4.4.0-1115-aws suffer a kernel panic on boot on AWS. I tested t2.micro and t2.medium, it happens every time. Simply install the kernel from -proposed and reboot, we get the following oops: [0.549557] BUG: unable to handle kernel paging request at ff5f3000 [0.552000] IP: [] mp_irqdomain_activate+0x5f/0xa0 [0.552000] PGD 1e0f067 PUD 1e11067 PMD 1e12067 PTE 0 [0.552000] Oops: 0002 [#1] SMP [0.552000] Modules linked in: [0.552000] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 4.4.0-191-generic #221-Ubuntu [0.552000] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006 [0.552000] task: 88010a0f ti: 88010a0f8000 task.ti: 88010a0f8000 [0.552000] RIP: 0010:[] [] mp_irqdomain_activate+0x5f/0xa0 [0.552000] RSP: :88010a0fbc48 EFLAGS: 00010086 [0.552000] RAX: 0086 RBX: 88010a1df480 RCX: [0.552000] RDX: ff5f3000 RSI: 0001 RDI: 0020c000 [0.552000] RBP: 88010a0fbc50 R08: 81ebdfd0 R09: [0.552000] R10: 0011 R11: 0009 R12: 88010ad95400 [0.552000] R13: 0001 R14: 0009 R15: 88010a1fc480 [0.552000] FS: () GS:88010b24() knlGS: [0.552000] CS: 0010 DS: ES: CR0: 80050033 [0.552000] CR2: ff5f3000 CR3: 01e0a000 CR4: 00160670 [0.552000] DR0: DR1: DR2: [0.552000] DR3: DR6: fffe0ff0 DR7: 0400 [0.552000] Stack: [0.552000] 88010ac0ba58 88010a0fbc70 810ea644 88010ac0ba00 [0.552000] 88010ac0ba58 88010a0fbca0 810e6d88 810e1009 [0.552000] 88010ac0ba00 88010ac0baa0 88010a1fc480 88010a0fbd38 [0.552000] Call Trace: [0.552000] [] irq_domain_activate_irq+0x44/0x50 [0.552000] [] irq_startup+0x38/0x90 [0.552000] [] ? vprintk_default+0x29/0x40 [0.552000] [] __setup_irq+0x5a2/0x650 [0.552000] [] ? kmem_cache_alloc_trace+0x1d4/0x1f0 [0.552000] [] ? acpi_osi_handler+0xb0/0xb0 [0.552000] [] request_threaded_irq+0xfb/0x1a0 [0.552000] [] ? acpi_osi_handler+0xb0/0xb0 [0.552000] [] ? acpi_ev_sci_dispatch+0x64/0x64 [0.552000] [] acpi_os_install_interrupt_handler+0xaa/0x100 [0.552000] [] ? acpi_sleep_proc_init+0x28/0x28 [0.552000] [] acpi_ev_install_sci_handler+0x23/0x25 [0.552000] [] acpi_ev_install_xrupt_handlers+0x1c/0x6c [0.552000] [] acpi_enable_subsystem+0x8f/0x93 [0.552000] [] acpi_init+0x8b/0x2c4 [0.552000] [] ? kasprintf+0x4e/0x70 [0.552000] [] ? acpi_sleep_proc_init+0x28/0x28 [0.552000] [] do_one_initcall+0xb5/0x200 [0.552000] [] ? parse_args+0x29a/0x4a0 [0.552000] [] kernel_init_freeable+0x177/0x218 [0.552000] [] ? rest_init+0x80/0x80 [0.552000] [] kernel_init+0xe/0xe0 [0.552000] [] ret_from_fork+0x55/0x80 [0.552000] [] ? rest_init+0x80/0x80 [0.552000] Code: 8d 1c d2 8d ba 0b 02 00 00 44 8d 51 11 42 8b 14 dd 74 ec 10 82 c1 e7 0c 48 63 ff 81 e2 ff 0f 00 00 48 81 ea 00 10 80 00 48 29 fa <44> 89 12 89 72 10 42 8b 14 dd 74 ec 10 82 83 c1 10 81 e2 ff 0f [0.552000] RIP [] mp_irqdomain_activate+0x5f/0xa0 [0.996006] RSP [0.996006] CR2: ff5f3000 [0.996006] ---[ end trace 1d0c3bd610d641a0 ]--- [1.012018] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0009 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1896725/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1897727] Re: package linux-image-5.4.0-45-generic (not installed) failed to install/upgrade: o subprocesso instalado, do pacote linux-image-5.4.0-45-generic, o script post-insta
Thank you for taking the time to report this bug and helping to make Ubuntu better. Reviewing your dmesg attachment in this bug report it seems that there is a problem with your hardware. I recommend performing a back up and then investigating the situation. Measures you might take include checking cable connections and using software tools to investigate the health of your hardware. In the event that is is not in fact an error with your hardware please set the bug's status back to New. Thanks and good luck! [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: hardware-error ** Changed in: linux (Ubuntu) Importance: Undecided => Low ** 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/1897727 Title: package linux-image-5.4.0-45-generic (not installed) failed to install/upgrade: o subprocesso instalado, do pacote linux- image-5.4.0-45-generic, o script post-installation retornou erro do status de saída 135 Status in linux package in Ubuntu: Invalid Bug description: repeat, always where restart ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-45-generic (not installed) ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 AptOrdering: linux-libc-dev:amd64: Install NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: marcio_fx 1216 F pulseaudio /dev/snd/controlC0: marcio_fx 1216 F pulseaudio CasperMD5CheckResult: skip Date: Tue Sep 22 06:26:21 2020 ErrorMessage: o subprocesso instalado, do pacote linux-image-5.4.0-45-generic, o script post-installation retornou erro do status de saída 135 InstallationDate: Installed on 2020-08-05 (55 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: lono wireless extensions. enp2s0no wireless extensions. MachineType: Dell Inc. OptiPlex 380 ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=9ff02dc6-c5e8-4c64-8801-31cf21d29d0e ro quiet splash 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: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26.4 RfKill: SourcePackage: linux Title: package linux-image-5.4.0-45-generic (not installed) failed to install/upgrade: o subprocesso instalado, do pacote linux-image-5.4.0-45-generic, o script post-installation retornou erro do status de saída 135 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/23/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A00 dmi.board.name: 0HN7XN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA00:bd10/23/2009:svnDellInc.:pnOptiPlex380:pvr:rvnDellInc.:rn0HN7XN:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: OptiPlex 380 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1897727/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1895202] Re: touchpad suddenly not detected, appearing as PS/2 mouse in devices
FWIW, I do this dance after boot and the touchpad works... ➜ ~ sudo modprobe psmouse [sudo] passord for ole: ➜ ~ sudo rmmod psmouse ➜ ~ sudo modprobe psmouse Sincerely, Ole ons. 23. sep. 2020 kl. 23:29 skrev Ole Morten Heggebakken Amundsen < ole.morten.amund...@gmail.com>: > The problem persists on 5.4.0-48 sadly, I still need to select advanced in > grub, selecting 5.4.0-42 for the touchpad to work. > > *➜ ~ xinput --list* > > *5.4.0-42* > > ⎡ Virtual core pointer id=2 [master pointer (3)] > ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] > ⎜ ↳ SynPS/2 Synaptics TouchPad id=11 [slave pointer (2)] > ⎜ ↳ TPPS/2 Elan TrackPoint id=12 [slave pointer (2)] > ⎣ Virtual core keyboard id=3 [master keyboard (2)] > ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)] > ↳ Power Button id=6 [slave keyboard (3)] > ↳ Video Bus id=7 [slave keyboard (3)] > ↳ Sleep Button id=8 [slave keyboard (3)] > ↳ Integrated Camera: Integrated C id=9 [slave keyboard (3)] > ↳ AT Translated Set 2 keyboard id=10 [slave keyboard (3)] > ↳ ThinkPad Extra Buttons > > *5.4.0-48* > > ⎡ Virtual core pointer id=2 [master pointer (3)] > ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] > ⎜ ↳ Synaptics TM3418-002 id=12 [slave pointer (2)] > ⎜ ↳ PS/2 Generic Mouse id=13 [slave pointer (2)] > ⎣ Virtual core keyboard id=3 [master keyboard (2)] > ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)] > ↳ Power Button id=6 [slave keyboard (3)] > ↳ Video Bus id=7 [slave keyboard (3)] > ↳ Sleep Button id=8 [slave keyboard (3)] > ↳ Integrated Camera: Integrated C id=9 [slave keyboard (3)] > ↳ AT Translated Set 2 keyboard id=10 [slave keyboard (3)] > ↳ ThinkPad Extra Buttons id=11 [slave keyboard (3)] > > *➜ ~ cat /var/log/Xorg.0.log | grep -i synaptics* > > *5.4.0-42* > > [16.093] (II) config/udev: Adding input device SynPS/2 Synaptics > TouchPad (/dev/input/event5) > [16.093] (**) SynPS/2 Synaptics TouchPad: Applying InputClass > "libinput touchpad catchall" > [16.093] (II) Using input driver 'libinput' for 'SynPS/2 Synaptics > TouchPad' > [16.094] (**) SynPS/2 Synaptics TouchPad: always reports core events > [16.095] (II) event5 - SynPS/2 Synaptics TouchPad: is tagged by udev > as: Touchpad > [16.095] (II) event5 - SynPS/2 Synaptics TouchPad: device is a > touchpad > [16.096] (II) event5 - SynPS/2 Synaptics TouchPad: device removed > [16.096] (II) XINPUT: Adding extended input device "SynPS/2 Synaptics > TouchPad" (type: TOUCHPAD, id 11) > [16.096] (**) SynPS/2 Synaptics TouchPad: (accel) selected scheme > none/0 > [16.096] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration factor: > 2.000 > [16.096] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration > threshold: 4 > [16.097] (II) event5 - SynPS/2 Synaptics TouchPad: is tagged by udev > as: Touchpad > [16.098] (II) event5 - SynPS/2 Synaptics TouchPad: device is a > touchpad > [16.098] (II) config/udev: Adding input device SynPS/2 Synaptics > TouchPad (/dev/input/mouse0) > [23.216] (II) event5 - SynPS/2 Synaptics TouchPad: device removed > > *5.4.0-48* > > [12.467] (II) config/udev: Adding input device Synaptics TM3418-002 > (/dev/input/event9) > [12.467] (**) Synaptics TM3418-002: Applying InputClass "libinput > touchpad catchall" > [12.467] (II) Using input driver 'libinput' for 'Synaptics TM3418-002' > [12.468] (**) Synaptics TM3418-002: always reports core events > [12.469] (II) event9 - Synaptics TM3418-002: is tagged by udev as: > Touchpad > [12.470] (II) event9 - Synaptics TM3418-002: device is a touchpad > [12.470] (II) event9 - Synaptics TM3418-002: device removed > [12.470] (II) XINPUT: Adding extended input device "Synaptics > TM3418-002" (type: TOUCHPAD, id 12) > [12.470] (**) Synaptics TM3418-002: (accel) selected scheme none/0 > [12.470] (**) Synaptics TM3418-002: (accel) acceleration factor: 2.000 > [12.470] (**) Synaptics TM3418-002: (accel) acceleration threshold: 4 > [12.471] (II) event9 - Synaptics TM3418-002: is tagged by udev as: > Touchpad > [12.472] (II) event9 - Synaptics TM3418-002: device is a touchpad > [12.472] (II) config/udev: Adding input device Synaptics TM3418-002 > (/dev/input/mouse0) > [33.395] (II) event9 - Synaptics TM3418-002: device removed > > ons. 23. sep. 2020, 20:15 skrev Russ McGill <1895...@bugs.launchpad.net>: > >> Kernel 5.4.0-48 fixes the problem. The TouchPad is recognized
[Kernel-packages] [Bug 1897727] 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/1897727 Title: package linux-image-5.4.0-45-generic (not installed) failed to install/upgrade: o subprocesso instalado, do pacote linux- image-5.4.0-45-generic, o script post-installation retornou erro do status de saída 135 Status in linux package in Ubuntu: Confirmed Bug description: repeat, always where restart ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-45-generic (not installed) ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 AptOrdering: linux-libc-dev:amd64: Install NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: marcio_fx 1216 F pulseaudio /dev/snd/controlC0: marcio_fx 1216 F pulseaudio CasperMD5CheckResult: skip Date: Tue Sep 22 06:26:21 2020 ErrorMessage: o subprocesso instalado, do pacote linux-image-5.4.0-45-generic, o script post-installation retornou erro do status de saída 135 InstallationDate: Installed on 2020-08-05 (55 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: lono wireless extensions. enp2s0no wireless extensions. MachineType: Dell Inc. OptiPlex 380 ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=9ff02dc6-c5e8-4c64-8801-31cf21d29d0e ro quiet splash 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: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26.4 RfKill: SourcePackage: linux Title: package linux-image-5.4.0-45-generic (not installed) failed to install/upgrade: o subprocesso instalado, do pacote linux-image-5.4.0-45-generic, o script post-installation retornou erro do status de saída 135 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/23/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A00 dmi.board.name: 0HN7XN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA00:bd10/23/2009:svnDellInc.:pnOptiPlex380:pvr:rvnDellInc.:rn0HN7XN:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: OptiPlex 380 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1897727/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895526] Re: ocfs2 file system no longer write - "disk full" despite lots of free space
Got the main server checked and tested. Was able to successfully format the drbd device with ocfs2 and thereafter could write files to the ocfs2 partition with full read/write access. I can happily report that this problem now seems to be fixed for me. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1895526 Title: ocfs2 file system no longer write - "disk full" despite lots of free space Status in linux package in Ubuntu: Incomplete Status in ocfs2-tools package in Ubuntu: Confirmed Bug description: Fairly new server on Ubuntu 20.04.1 LTS, 5.4.0-47-generic kernel, DRBD device across 2 sites with one server in each site, ocfs2 filesystem on DRBD device, shared to local network using Samba (and also Samba-AD-DC for network). All packages from "normal" Ubuntu repositories. ocfs2-tools is Installed: 1.8.6-2ubuntu1. The filesystem is around 3.3 TB. Stored data amounted to 24% of this filesystem. Recent updates applied and server restarted Wed 9th Sept after which staff started reporting inability to save to server shares. Checked Samba settings as Windows error messages were at first showing permission issues, but following various checks no wrong Samba settings were found so restarted their server after which the errors were "no space left on disk". Checked on the server terminal and couldn't even "touch" an empty file but got "no space left on disk". Found an article describing limitations caused by ocfs2 cluster size, so copied all data out to a backup machine, recreated the ocfs2 file system using mkfs.ocfs2 -C 64K /dev/drbd0 but again the "no disk space" error keeps happening despite this now being an empty file system. Perhaps it wasn't a cluster size problem in the first instance. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ocfs2-tools 1.8.6-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Sep 14 12:23:35 2020 InstallationDate: Installed on 2020-05-06 (130 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ocfs2-tools UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895526/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1897727] [NEW] package linux-image-5.4.0-45-generic (not installed) failed to install/upgrade: o subprocesso instalado, do pacote linux-image-5.4.0-45-generic, o script post-ins
Public bug reported: repeat, always where restart ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-45-generic (not installed) ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 AptOrdering: linux-libc-dev:amd64: Install NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: marcio_fx 1216 F pulseaudio /dev/snd/controlC0: marcio_fx 1216 F pulseaudio CasperMD5CheckResult: skip Date: Tue Sep 22 06:26:21 2020 ErrorMessage: o subprocesso instalado, do pacote linux-image-5.4.0-45-generic, o script post-installation retornou erro do status de saída 135 InstallationDate: Installed on 2020-08-05 (55 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: lono wireless extensions. enp2s0no wireless extensions. MachineType: Dell Inc. OptiPlex 380 ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=9ff02dc6-c5e8-4c64-8801-31cf21d29d0e ro quiet splash 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: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26.4 RfKill: SourcePackage: linux Title: package linux-image-5.4.0-45-generic (not installed) failed to install/upgrade: o subprocesso instalado, do pacote linux-image-5.4.0-45-generic, o script post-installation retornou erro do status de saída 135 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/23/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A00 dmi.board.name: 0HN7XN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA00:bd10/23/2009:svnDellInc.:pnOptiPlex380:pvr:rvnDellInc.:rn0HN7XN:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: OptiPlex 380 dmi.sys.vendor: Dell Inc. ** 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/1897727 Title: package linux-image-5.4.0-45-generic (not installed) failed to install/upgrade: o subprocesso instalado, do pacote linux- image-5.4.0-45-generic, o script post-installation retornou erro do status de saída 135 Status in linux package in Ubuntu: New Bug description: repeat, always where restart ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-45-generic (not installed) ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 AptOrdering: linux-libc-dev:amd64: Install NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: marcio_fx 1216 F pulseaudio /dev/snd/controlC0: marcio_fx 1216 F pulseaudio CasperMD5CheckResult: skip Date: Tue Sep 22 06:26:21 2020 ErrorMessage: o subprocesso instalado, do pacote linux-image-5.4.0-45-generic, o script post-installation retornou erro do status de saída 135 InstallationDate: Installed on 2020-08-05 (55 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: lono wireless extensions. enp2s0no wireless extensions. MachineType: Dell Inc. OptiPlex 380 ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=9ff02dc6-c5e8-4c64-8801-31cf21d29d0e ro quiet splash 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: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26.4 RfKill: SourcePackage: linux Title: package linux-image-5.4.0-45-generic (not installed) failed to install/upgrade: o subprocesso instalado, do pacote linux-image-5.4.0-45-generic, o script post-installation retornou erro do status de saída 135 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/23/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A00 dmi.board.name: 0HN7XN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA00:bd10/23/2009:svnDellInc.:pnOptiPlex380:pvr:rvnDellInc.:rn0HN7XN:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: OptiPlex 380 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1897727/+subscriptions
[Kernel-packages] [Bug 1847105] Re: very slow disk creation, snapshotting
As you explained I acknowledge that we are changing behaviour in Focal here, but I agree with you that this is the least worst option. ** Description changed: [Impact] - * The defaults of virt-manager for disk allocation always worked fine -when qcow2 had nothing but sparse support. So sparse=True vs -sparse=False made no difference. So it always set sparse=False. -Then qcow2 grows non-sparse support, and virt-manager is suddenly -defaulting to it, which is not the intention. + * The defaults of virt-manager for disk allocation always worked fine + when qcow2 had nothing but sparse support. So sparse=True vs + sparse=False made no difference. So it always set sparse=False. + Then qcow2 grows non-sparse support, and virt-manager is suddenly + defaulting to it, which is not the intention. + * For upgraders from pre-Focal this was a regression in two ways: + a) allocation of qcow changed to non-sparse (fallocate based) + potentially consuming more space + b) depending on the underlying FS this made the allocation much + slower - * For upgraders from pre-Focal this was a regression in two ways: - a) allocation of qcow changed to non-sparse (fallocate based) -potentially consuming more space - b) depending on the underlying FS this made the allocation much -slower - - * Fix by applying the upstream change that Defaults to sparse when -requested format isn't raw (for raw the assumption ill stay that -users do that for runtime performance, so non-sparse on those stays -as-is) + * Fix by applying the upstream change that Defaults to sparse when + requested format isn't raw (for raw the assumption ill stay that + users do that for runtime performance, so non-sparse on those stays + as-is) [Test Case] - * open virt-manager and create a new guest which includes creating a -new image for it -* when clicking "finish" the image will be created (which e.g. on ZFS - will take quite some time) -* In the background grep ps output if the qemu-img call for qcow (the - default) is using "preallocation=fallocate" (wrong) or - "preallocation=metadata" (correct) + * open virt-manager and create a new guest which includes creating a + new image for it + * when clicking "finish" the image will be created (which e.g. on ZFS + will take quite some time) + * In the background grep ps output if the qemu-img call for qcow (the + default) is using "preallocation=fallocate" (wrong) or + "preallocation=metadata" (correct) [Regression Potential] - * For upgraders from pre-focal it actually ensures behavior stays as is -(no change/regression there) - * For users of ZFS where the allocation was slow it fixes this -slowness. - * But for people using Focal all the time and on non-ZFS there will be -a behavior change in no more doing falloc pre-allocating the qemu -image. To be cleear there are four modes: -1. no allocation -2. metadata allocation - is initially larger but can improve - performance when the image needs to grow -3. falloc - preallocates space for image by calling posix_fallocate -4. full - writes data to the underlying storage -The fix changes the default from 3->2 which it always was and should -be. As the patch says: "If users want to override it, they can -do it via custom created storage." -(To be clear, upstream changed this as we fixed it here, so on - further upgrades what we apply here will be the behavior anyway, it - seems wrong to keep Focal the only one in between kept different) + * For upgraders from pre-focal it actually ensures behavior stays as is + (no change/regression there) + * For users of ZFS where the allocation was slow it fixes this + slowness. + * But for people using Focal all the time and on non-ZFS there will be + a behavior change in no more doing falloc pre-allocating the qemu + image. To be cleear there are four modes: + 1. no allocation + 2. metadata allocation - is initially larger but can improve + performance when the image needs to grow + 3. falloc - preallocates space for image by calling posix_fallocate + 4. full - writes data to the underlying storage + The fix changes the default from 3->2 which it always was and should + be. As the patch says: "If users want to override it, they can + do it via custom created storage." + (To be clear, upstream changed this as we fixed it here, so on + further upgrades what we apply here will be the behavior anyway, it + seems wrong to keep Focal the only one in between kept different) + * [racb] The code path being added special cases the 'raw' format and in handling of the default sparse setting. Areas of potential regression are therefore in the handling of the default and override of the default in the cases of both 'raw' and not
[Kernel-packages] [Bug 1847105] Re: very slow disk creation, snapshotting
** Tags added: focal regression-release -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1847105 Title: very slow disk creation, snapshotting Status in virt-manager: Fix Released Status in Native ZFS for Linux: New Status in libvirt package in Ubuntu: Triaged Status in virt-manager package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: New Status in libvirt source package in Bionic: Invalid Status in virt-manager source package in Bionic: Invalid Status in zfs-linux source package in Bionic: Won't Fix Status in libvirt source package in Disco: Won't Fix Status in virt-manager source package in Disco: Won't Fix Status in zfs-linux source package in Disco: Won't Fix Status in libvirt source package in Focal: Triaged Status in libvirt source package in Groovy: Triaged Bug description: [Impact] * The defaults of virt-manager for disk allocation always worked fine when qcow2 had nothing but sparse support. So sparse=True vs sparse=False made no difference. So it always set sparse=False. Then qcow2 grows non-sparse support, and virt-manager is suddenly defaulting to it, which is not the intention. * For upgraders from pre-Focal this was a regression in two ways: a) allocation of qcow changed to non-sparse (fallocate based) potentially consuming more space b) depending on the underlying FS this made the allocation much slower * Fix by applying the upstream change that Defaults to sparse when requested format isn't raw (for raw the assumption ill stay that users do that for runtime performance, so non-sparse on those stays as-is) [Test Case] * open virt-manager and create a new guest which includes creating a new image for it * when clicking "finish" the image will be created (which e.g. on ZFS will take quite some time) * In the background grep ps output if the qemu-img call for qcow (the default) is using "preallocation=fallocate" (wrong) or "preallocation=metadata" (correct) [Regression Potential] * For upgraders from pre-focal it actually ensures behavior stays as is (no change/regression there) * For users of ZFS where the allocation was slow it fixes this slowness. * But for people using Focal all the time and on non-ZFS there will be a behavior change in no more doing falloc pre-allocating the qemu image. To be cleear there are four modes: 1. no allocation 2. metadata allocation - is initially larger but can improve performance when the image needs to grow 3. falloc - preallocates space for image by calling posix_fallocate 4. full - writes data to the underlying storage The fix changes the default from 3->2 which it always was and should be. As the patch says: "If users want to override it, they can do it via custom created storage." (To be clear, upstream changed this as we fixed it here, so on further upgrades what we apply here will be the behavior anyway, it seems wrong to keep Focal the only one in between kept different) [Other Info] * The slowness effect might be further mitigated by ZFS implementing more falloc options (thanks Richard for that hint) but that won't be in Focal. This is a regression in eoan for me. I use virt-manager to create vms, and I noticed that creating one now takes more than a minute. Looking at the process listing while the backing disk is being created, I see this qemu-img command line: 15658 ?Ssl0:00 /usr/sbin/libvirtd 23726 ?Sl 0:04 \_ /usr/bin/qemu-img create -f qcow2 -o preallocation=falloc,compat=1.1,lazy_refcounts /var/lib/libvirt/images/live-server.qcow2 41943040K If I run qemu-img with that preallocation parameter set, even on bionic, then it also takes a very long time. On eoan, for comparison: andreas@nsn7:~$ time qemu-img create -f qcow2 no-prealloc-image.qcow2 40G Formatting 'no-prealloc-image.qcow2', fmt=qcow2 size=42949672960 cluster_size=65536 lazy_refcounts=off refcount_bits=16 real 0m0,016s user 0m0,010s sys 0m0,006s andreas@nsn7:~$ qemu-img info no-prealloc-image.qcow2 image: no-prealloc-image.qcow2 file format: qcow2 virtual size: 40G (42949672960 bytes) disk size: 17K cluster_size: 65536 Format specific information: compat: 1.1 lazy refcounts: false refcount bits: 16 corrupt: false andreas@nsn7:~$ du -hs no-prealloc-image.qcow2 17K no-prealloc-image.qcow2 andreas@nsn7:~$ and now with preallocation=falloc: andreas@nsn7:~$ time qemu-img create -f qcow2 -o preallocation=falloc with-prealloc-image.qcow2 40G Formatting 'with-prealloc-image.qcow2', fmt=qcow2 size=42949672960 cluster_size=65536 preallocation=falloc
[Kernel-packages] [Bug 1896419] Re: Comet Lake CPUID family:model:stepping 0x6:a5:2 (6:165:2) is not included
Thanks for verify this. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1896419 Title: Comet Lake CPUID family:model:stepping 0x6:a5:2 (6:165:2) is not included Status in OEM Priority Project: Fix Committed Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Focal: Fix Committed Status in thermald source package in Groovy: Fix Released Bug description: [Impact] * The CPUID is not included, which cause the thermald starts failed. Sep 15 17:07:00 ubuntu thermald[1089]: [WARN]Unsupported cpu model, use thermal-conf.xml file or run with --ignore-cpuid-check Sep 15 17:07:00 ubuntu thermald[1089]: [ERR]THD engine start failed Sep 15 17:07:00 ubuntu systemd[1]: thermald.service: Succeeded. * A upstream commit added missing CPUID https://github.com/intel/thermal_daemon/commit/7f2003ee911dd1c97ff74d2b84c62e10950bc9e0 [Test Case] On an affected system (Comet Lake): * $ systemctl is-active thermald active [Regression Potential] * Only new id added, no process or logic adjustment, so no regression risk. [Other Info] * The upstream bug: https://github.com/intel/thermal_daemon/issues/275 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1896419/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1896419] Re: Comet Lake CPUID family:model:stepping 0x6:a5:2 (6:165:2) is not included
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1896419 Title: Comet Lake CPUID family:model:stepping 0x6:a5:2 (6:165:2) is not included Status in OEM Priority Project: Fix Committed Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Focal: Fix Committed Status in thermald source package in Groovy: Fix Released Bug description: [Impact] * The CPUID is not included, which cause the thermald starts failed. Sep 15 17:07:00 ubuntu thermald[1089]: [WARN]Unsupported cpu model, use thermal-conf.xml file or run with --ignore-cpuid-check Sep 15 17:07:00 ubuntu thermald[1089]: [ERR]THD engine start failed Sep 15 17:07:00 ubuntu systemd[1]: thermald.service: Succeeded. * A upstream commit added missing CPUID https://github.com/intel/thermal_daemon/commit/7f2003ee911dd1c97ff74d2b84c62e10950bc9e0 [Test Case] On an affected system (Comet Lake): * $ systemctl is-active thermald active [Regression Potential] * Only new id added, no process or logic adjustment, so no regression risk. [Other Info] * The upstream bug: https://github.com/intel/thermal_daemon/issues/275 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1896419/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855757] Re: [nvidia] Background image corrupted after standby or resume from suspend
It already exists in focal-proposed. So you can enable 'proposed' updates or just download the new packages: https://launchpad.net/ubuntu/+source/mutter/3.36.6-1ubuntu0.20.04.2/+build/19963778 -- 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/1855757 Title: [nvidia] Background image corrupted after standby or resume from suspend Status in mutter package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-390 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-435 package in Ubuntu: Won't Fix Status in mutter source package in Focal: Triaged Status in nvidia-graphics-drivers-340 source package in Focal: Won't Fix Status in nvidia-graphics-drivers-390 source package in Focal: Won't Fix Status in nvidia-graphics-drivers-435 source package in Focal: Won't Fix Bug description: Looks similar to https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1809407 When the computer goes to standby, the background image becomes corrupted. I am able to fix by "killall Xorg" , change the background image (settings > background) and restart. Haven't tried login logout. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: 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.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.107 Thu May 24 21:54:01 PDT 2018 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Dec 9 10:58:35 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.107, 5.3.0-23-generic, x86_64: installed nvidia-340, 340.107, 5.3.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GT215M [GeForce GTS 360M] [10de:0cb1] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GT215M [GeForce GTS 360M] [1043:203c] InstallationDate: Installed on 2019-11-29 (10 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUSTek Computer Inc. G60JX ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=65117975-c95f-4406-a7cf-da912cda0e70 ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G60JX dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: PEGATRON Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr204:bd12/25/2009:svnASUSTekComputerInc.:pnG60JX:pvr1.0:rvnPEGATRONCORPORATION:rnG60JX:rvr1.0:cvnPEGATRONComputerInc.:ct10:cvr1.0: dmi.product.family: PEGA Family dmi.product.name: G60JX dmi.product.sku: 0 dmi.product.version: 1.0 dmi.sys.vendor: ASUSTek Computer Inc. 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 N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1855757/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1897709] [NEW] iproute2 is missing libnetlink.h and libnetlink.a
Public bug reported: libnetlink library provides access to `man 3 libnetlink` functions. For some reason, while `iproute2` package in Ubuntu has the manual page, however both libnetlink.h file and libnetlink.a to actually use the interfaces mentioned in the manual are absent. This is a packaging bug for iproute2. As another distro example: Archlinux includes the library and the header as part of iproute2 package https://www.archlinux.org/packages/core/x86_64/iproute2/files/ ** Affects: iproute2 (Ubuntu) Importance: Undecided Status: New -- 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/1897709 Title: iproute2 is missing libnetlink.h and libnetlink.a Status in iproute2 package in Ubuntu: New Bug description: libnetlink library provides access to `man 3 libnetlink` functions. For some reason, while `iproute2` package in Ubuntu has the manual page, however both libnetlink.h file and libnetlink.a to actually use the interfaces mentioned in the manual are absent. This is a packaging bug for iproute2. As another distro example: Archlinux includes the library and the header as part of iproute2 package https://www.archlinux.org/packages/core/x86_64/iproute2/files/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1897709/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855757] Re: [nvidia] Background image corrupted after standby or resume from suspend
@Daniel, is it possible to add a repo for this fix early ahead of coming down in the release repos? On the release repos I have the latest version. mutter is already the newest version (3.36.4-0ubuntu0.20.04.2). Cheers for any advice -- 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/1855757 Title: [nvidia] Background image corrupted after standby or resume from suspend Status in mutter package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-390 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-435 package in Ubuntu: Won't Fix Status in mutter source package in Focal: Triaged Status in nvidia-graphics-drivers-340 source package in Focal: Won't Fix Status in nvidia-graphics-drivers-390 source package in Focal: Won't Fix Status in nvidia-graphics-drivers-435 source package in Focal: Won't Fix Bug description: Looks similar to https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1809407 When the computer goes to standby, the background image becomes corrupted. I am able to fix by "killall Xorg" , change the background image (settings > background) and restart. Haven't tried login logout. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: 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.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.107 Thu May 24 21:54:01 PDT 2018 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Dec 9 10:58:35 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.107, 5.3.0-23-generic, x86_64: installed nvidia-340, 340.107, 5.3.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GT215M [GeForce GTS 360M] [10de:0cb1] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GT215M [GeForce GTS 360M] [1043:203c] InstallationDate: Installed on 2019-11-29 (10 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUSTek Computer Inc. G60JX ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=65117975-c95f-4406-a7cf-da912cda0e70 ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G60JX dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: PEGATRON Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr204:bd12/25/2009:svnASUSTekComputerInc.:pnG60JX:pvr1.0:rvnPEGATRONCORPORATION:rnG60JX:rvr1.0:cvnPEGATRONComputerInc.:ct10:cvr1.0: dmi.product.family: PEGA Family dmi.product.name: G60JX dmi.product.sku: 0 dmi.product.version: 1.0 dmi.sys.vendor: ASUSTek Computer Inc. 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 N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1855757/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1896726] Re: [UBUNTU 20.04.1] qemu (secure guest) crash due to gup_fast / dynamic page table folding issue
I just uploaded a ddeb to:
https://people.canonical.com/~fheimes/lp1896726/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/1896726
Title:
[UBUNTU 20.04.1] qemu (secure guest) crash due to gup_fast / dynamic
page table folding issue
Status in Ubuntu on IBM z Systems:
In Progress
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Focal:
Incomplete
Status in linux source package in Groovy:
In Progress
Bug description:
Justification:
==
Secure KVM guest (using secure execution on Ubuntu Server 20.04 for s390x)
crashes happen from time to time during boot.
Such crashed guests ("reason=crashed" in the libvirt log) end up in hutoff
state instead of crashed state ( preserve is set).
The crash points to a kernel memory management problem, addressed by the
following patch/fix.
The modifications touch common memory management code,
but it will have no effect to architectures other than s390x.
This is ensured by the fact that only s390 provides / implements the new
helper functions.
And for s390x, this is actually a critical (and carefully tested) fix for a
(previous) regression, so it can hardly get any more regressive.
The patch landed upstream in linux-next, is in depth discussed
at LKML https://lkml.kernel.org/r/20190418100218.0a4afd51@mschwideX1
and here
https://lore.kernel.org/linux-arch/patch.git-943f1e5dcff2.your-ad-here.call-01599856292-ext-8676@work.hours/
and will soon land via the regular upstream stable release update for kernel
5.4 in focal, too.
The process already started:
https://lore.kernel.org/stable/patch-1.thread-41918b.git-41918be365c0.your-ad-here.call-01600439945-ext-8991@work.hours/
Hence this cherry-pick from the upstream patch should be added to groovy
to avoid any potential regression in case the patch landed in focal via the
upstream release update process,
but is not in groovy and someones upgrades from focal to groovy.
__
Secure Execution with Ubuntu 20.04, secure guest crash during boot
from time to time, crashed guest went into Shufoff state instead of
Crashed state (preserve is set), so I can't get a dump.
libvirt log file:
2020-04-21T16:35:39.382999Z qemu-system-s390x: Guest says index 19608 is
available
2020-04-21 16:35:44.831+: shutting down, reason=crashed
---uname output---
Linux ubu204uclg1002 5.4.0-25-generic #29-Ubuntu SMP Fri Apr 17 15:05:32 UTC
2020 s390x s390x s390x GNU/Linux
Machine Type = z15 8561
---Debugger---
A debugger is not configured
---Steps to Reproduce---
I have a setup with 72 KVM guests which I can start in secure or non-secure
mode. Starting all of them in secure mode back to back results in a number of
guests (4..8) in Shutoff state and reason=crashed in the libvirt log. I can
manually start the guest again no problem. Different guests are failing.
Host and guests are on latest Ubuntu 20.04.
The supposed fix (kernel memory management) has landed in Andrew Mortons mm
tree
https://lore.kernel.org/mm-commits/20200916003608.ib4ln%25a...@linux-foundation.org/T/#u
Please note: while this was found with secure execution, the bug is
actually present for non-KVM workloads as well.
The complete patch is this:
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=a338e69ba37286c0fc300ab7e6fa0227e6ca68b1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1896726/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1897295] Re: freeze display and no more toothead wheel high of the screen for parameters
This looks like a problem with the 'nouveau' kernel driver. First we need to check to see if it's already fixed in a newer version so please try booting Ubuntu 20.04.1 or 18.04.5 from https://releases.ubuntu.com/ ** Tags added: nouveau ** Summary changed: - freeze display and no more toothead wheel high of the screen for parameters + [nouveau] freeze display and no more toothead wheel high of the screen for parameters ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: linux (Ubuntu) Status: Incomplete => New ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1897295 Title: [nouveau] freeze display and no more toothead wheel high of the screen for parameters Status in linux package in Ubuntu: Incomplete Bug description: -often I need several reboot for a clean ubuntu installation, the courant problem is sceen freeze in the middle of ubuntu installation -often ubuntu freeze during the session, and I must restart the computer -parameters wheel is lost -I don't understand very well english ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-118.119-generic 4.15.18 Uname: Linux 4.15.0-118-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.17 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Fri Sep 25 16:08:51 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GK208 [GeForce GT 710] [10de:1289] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GK208 [GeForce GT 710] [1043:866f] InstallationDate: Installed on 2013-08-27 (2586 days ago) InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 (20130213) MachineType: Hewlett-Packard HP Compaq 8000 Elite CMT PC ProcEnviron: PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-118-generic root=UUID=53e6c79d-4a52-4722-8a07-22762747982a ro quiet splash vt.handoff=1 Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/22/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786G7 v01.02 dmi.board.asset.tag: CZC1058ZQF dmi.board.name: 3647h dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: CZC1058ZQF dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786G7v01.02:bd10/22/2009:svnHewlett-Packard:pnHPCompaq8000EliteCMTPC:pvr:rvnHewlett-Packard:rn3647h:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53307F dmi.product.name: HP Compaq 8000 Elite CMT PC dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 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 2:1.19.6-1ubuntu4.6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Fri Sep 25 09:16:47 2020 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1897295/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1897464] Re: Problmes with disk size with zfs
** Tags added: 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/1897464 Title: Problmes with disk size with zfs Status in zfs-linux package in Ubuntu: Incomplete Bug description: I created a VM that has 64GB of hard drive space and I used zfs during install. Now here is what I see via desktop GUI: Disks => 69 GB Computer => 23.6 GB Two pools: zpool list NAMESIZE ALLOC FREE CKPOINT EXPANDSZ FRAGCAP DEDUPHEALTH ALTROOT bpool 1.88G 427M 1.46G- - 0%22% 1.00xONLINE - rpool59G 38.7G 20.3G- -36%65% 1.00xONLINE - As a result I run out of space. So I am confused, why is my disk size only 23.6 GB ? Definitely seems like a bug in how Computer shows the disk size. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1897464/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1896646] 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/1896646 Title: [ASUS X556UAM] Bluetooth no longer detected Status in linux package in Ubuntu: Confirmed Bug description: 22 september 2020 update removed bluetooth capability. No Bluetooth hardware detected by system, cannot turn on or add devices. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.4.0-49.53-generic 5.4.65 Uname: Linux 5.4.0-49-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Sep 22 12:53:31 2020 InstallationDate: Installed on 2019-12-07 (290 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) InterestingModules: bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:57de Realtek Semiconductor Corp. USB2.0 VGA UVC WebCam Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 5: Dev 2, If 0, Class=Vendor Specific Class, Driver=rtsx_usb, 480M |__ Port 6: Dev 3, If 0, Class=Video, Driver=uvcvideo, 480M |__ Port 6: Dev 3, If 1, Class=Video, Driver=uvcvideo, 480M MachineType: ASUSTeK COMPUTER INC. X556UAM ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-49-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/06/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X556UAM.305 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X556UAM dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX556UAM.305:bd07/06/2016:svnASUSTeKCOMPUTERINC.:pnX556UAM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX556UAM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X556UAM dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. hciconfig: rfkill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896646/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1897295] [NEW] [nouveau] freeze display and no more toothead wheel high of the screen for parameters
You have been subscribed to a public bug: -often I need several reboot for a clean ubuntu installation, the courant problem is sceen freeze in the middle of ubuntu installation -often ubuntu freeze during the session, and I must restart the computer -parameters wheel is lost -I don't understand very well english ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-118.119-generic 4.15.18 Uname: Linux 4.15.0-118-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.17 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Fri Sep 25 16:08:51 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GK208 [GeForce GT 710] [10de:1289] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GK208 [GeForce GT 710] [1043:866f] InstallationDate: Installed on 2013-08-27 (2586 days ago) InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 (20130213) MachineType: Hewlett-Packard HP Compaq 8000 Elite CMT PC ProcEnviron: PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-118-generic root=UUID=53e6c79d-4a52-4722-8a07-22762747982a ro quiet splash vt.handoff=1 Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/22/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786G7 v01.02 dmi.board.asset.tag: CZC1058ZQF dmi.board.name: 3647h dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: CZC1058ZQF dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786G7v01.02:bd10/22/2009:svnHewlett-Packard:pnHPCompaq8000EliteCMTPC:pvr:rvnHewlett-Packard:rn3647h:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53307F dmi.product.name: HP Compaq 8000 Elite CMT PC dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 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 2:1.19.6-1ubuntu4.6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Fri Sep 25 09:16:47 2020 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4.6 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug bionic i386 nouveau ubuntu -- [nouveau] freeze display and no more toothead wheel high of the screen for parameters https://bugs.launchpad.net/bugs/1897295 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 1897694] [NEW] alsa/hda: mic doesn't work on a HP AIO machine
Public bug reported: This bug is for tracking purpose. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux-oem-5.6 (Ubuntu) Importance: Critical Assignee: Hui Wang (hui.wang) Status: In Progress ** Affects: linux-oem-5.6 (Ubuntu Focal) Importance: Critical Assignee: Hui Wang (hui.wang) Status: In Progress ** Tags: oem-priority originate-from-1896580 stella ** Changed in: linux-oem-5.6 (Ubuntu) Importance: Undecided => Critical ** Also affects: linux-oem-5.6 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-oem-5.6 (Ubuntu Focal) Importance: Undecided => Critical ** Changed in: linux-oem-5.6 (Ubuntu Focal) Assignee: (unassigned) => Hui Wang (hui.wang) ** Changed in: linux-oem-5.6 (Ubuntu) Status: New => In Progress ** Changed in: linux-oem-5.6 (Ubuntu Focal) Status: New => In Progress ** Tags added: oem-priority originate-from-1896580 stella -- 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/1897694 Title: alsa/hda: mic doesn't work on a HP AIO machine Status in HWE Next: New Status in linux-oem-5.6 package in Ubuntu: In Progress Status in linux-oem-5.6 source package in Focal: In Progress Bug description: This bug is for tracking purpose. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1897694/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1896646] Re: bluetooth no longer installed
bluez has not been updated since April. And regardless, the Bluetooth hardware detection is a kernel responsibility. ** Summary changed: - bluetooth no longer installed + [ASUS X556UAM] Bluetooth no longer detected ** Package changed: bluez (Ubuntu) => linux (Ubuntu) ** Tags added: regression-update -- 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/1896646 Title: [ASUS X556UAM] Bluetooth no longer detected Status in linux package in Ubuntu: New Bug description: 22 september 2020 update removed bluetooth capability. No Bluetooth hardware detected by system, cannot turn on or add devices. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.4.0-49.53-generic 5.4.65 Uname: Linux 5.4.0-49-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Sep 22 12:53:31 2020 InstallationDate: Installed on 2019-12-07 (290 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) InterestingModules: bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:57de Realtek Semiconductor Corp. USB2.0 VGA UVC WebCam Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 5: Dev 2, If 0, Class=Vendor Specific Class, Driver=rtsx_usb, 480M |__ Port 6: Dev 3, If 0, Class=Video, Driver=uvcvideo, 480M |__ Port 6: Dev 3, If 1, Class=Video, Driver=uvcvideo, 480M MachineType: ASUSTeK COMPUTER INC. X556UAM ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-49-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/06/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X556UAM.305 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X556UAM dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX556UAM.305:bd07/06/2016:svnASUSTeKCOMPUTERINC.:pnX556UAM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX556UAM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X556UAM dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. hciconfig: rfkill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896646/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853610] Re: mkfs01_ext3_sh / mkfs01_ext4_sh / nm01_sh from commands test in ubuntu_ltp fails
** Tags added: sru-20200921 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853610 Title: mkfs01_ext3_sh / mkfs01_ext4_sh / nm01_sh from commands test in ubuntu_ltp fails Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Incomplete Bug description: Series: E Problem: commands test in ubuntu_ltp fails on E, test cases listed below: * mkfs01_ext3_sh * mkfs01_ext4_sh * nm01_sh startup='Fri Dec 6 02:30:45 2019' mkfs01 1 TINFO: timeout per run is 0h 5m 0s tst_device.c:238: INFO: Using test device LTP_DEV='/dev/loop2' mkfs01 1 TPASS: 'mkfs -t ext3 /dev/loop2 ' passed. mkfs01 2 TFAIL: 'mkfs -t ext3 /dev/loop2 16000' failed, not expected. mkfs01 3 TPASS: 'mkfs -t ext3 -c /dev/loop2 ' passed. mkfs01 4 TPASS: 'mkfs -V ' passed. mkfs01 5 TPASS: 'mkfs -h ' passed. mkfs01 6 TINFO: AppArmor enabled, this may affect test results mkfs01 6 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 (requires super/root) mkfs01 6 TINFO: loaded AppArmor profiles: none Summary: passed 4 failed 1 skipped 0 warnings 0 tag=mkfs01_ext3_sh stime=1575599445 dur=2 exit=exited stat=1 core=no cu=8 cs=12 tag=mkfs01_ext3_sh stime=1575599445 dur=2 exit=exited stat=1 core=no cu=8 cs=12 startup='Fri Dec 6 02:30:52 2019' mkfs01 1 TINFO: timeout per run is 0h 5m 0s tst_device.c:238: INFO: Using test device LTP_DEV='/dev/loop2' mkfs01 1 TPASS: 'mkfs -t ext4 /dev/loop2 ' passed. mkfs01 2 TFAIL: 'mkfs -t ext4 /dev/loop2 16000' failed, not expected. mkfs01 3 TPASS: 'mkfs -t ext4 -c /dev/loop2 ' passed. mkfs01 4 TPASS: 'mkfs -V ' passed. mkfs01 5 TPASS: 'mkfs -h ' passed. mkfs01 6 TINFO: AppArmor enabled, this may affect test results mkfs01 6 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 (requires super/root) mkfs01 6 TINFO: loaded AppArmor profiles: none Summary: passed 4 failed 1 skipped 0 warnings 0 tag=mkfs01_ext4_sh stime=1575599452 dur=2 exit=exited stat=1 core=no cu=4 cs=1 startup='Fri Dec 6 02:28:44 2019' nm01 1 TINFO: timeout per run is 0h 5m 0s nm01 1 TPASS: nm -f posix -A lib.a > nm.out passed as expected nm01 1 TPASS: Got correct listing nm01 1 TPASS: nm -f posix -A dir/lib.a > nm.out passed as expected nm01 1 TPASS: Got correct listing nm01 2 TPASS: nm -f posix -g /opt/ltp/testcases/data/nm01/f1 > nm.out passed as expected nm01 2 TPASS: Got only external symbols with -g nm01 3 TPASS: nm -f posix -t o /opt/ltp/testcases/data/nm01/f1 > nm.out passed as expected nm01 3 TPASS: Got an octal symbol values with -f nm01 4 TPASS: nm -f sysv /opt/ltp/testcases/data/nm01/f1 > nm.out passed as expected nm01 4 TPASS: Got SysV format with -f sysv nm01 5 TPASS: nm -f bsd /opt/ltp/testcases/data/nm01/f1 > nm_bsd.out passed as expected nm01 5 TPASS: nm -f posix /opt/ltp/testcases/data/nm01/f1 > nm_posix.out passed as expected nm01 5 TFAIL: Got wrong format with -f bsd 3dc8 d _DYNAMIC 3fb8 d _GLOBAL_OFFSET_TABLE_ 2000 R _IO_stdin_used w _ITM_deregisterTMCloneTable w _ITM_registerTMCloneTable 2154 r __FRAME_END__ 2010 r __GNU_EH_FRAME_HDR 4010 D __TMC_END__ 4010 B __bss_start w __cxa_finalize@@GLIBC_2.2.5 4000 D __data_start 1120 t __do_global_dtors_aux 3dc0 d __do_global_dtors_aux_fini_array_entry 4008 D __dso_handle 3db8 d __frame_dummy_init_array_entry w __gmon_start__ 3dc0 d __init_array_end 3db8 d __init_array_start 11e0 T __libc_csu_fini 1170 T __libc_csu_init U __libc_start_main@@GLIBC_2.2.5 4010 D _edata 4018 B _end 11e8 T _fini 1000 t _init 1080 T _start 4010 b completed.8055 4000 W data_start 10b0 t deregister_tm_clones 1160 t frame_dummy 1060 T main U puts@@GLIBC_2.2.5 10e0 t register_tm_clones nm01 6 TPASS: nm -f sysv -u /opt/ltp/testcases/data/nm01/f1 > nm.out passed as expected nm01 6 TPASS: Got undefined symbols with -u nm01 7 TPASS: nm -s /opt/ltp/testcases/data/nm01/lib.a > nm.out passed as expected nm01 7 TPASS: Got index with -s nm01 8 TINFO: AppArmor enabled, this may affect test results nm01 8 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 (requires super/root) nm01 8 TINFO: loaded AppArmor profiles: none Summary: passed 16 failed 1 skipped 0 warnings 0 tag=nm01_sh stime=1575599324 dur=0 exit=exited stat=1 core=no cu=3 cs=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1853610/+subscriptions
[Kernel-packages] [Bug 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa
*** This bug is a duplicate of bug 1871794 *** https://bugs.launchpad.net/bugs/1871794 Same issue here with Sony Sony WH-CH510 on a fresh install of Ubuntu 20.04.1 LTS kernel 5.4.0-48-generic (buildd@lcy01-amd64-010) -- 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/1878194 Title: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After updating the release from Ubuntu 19.10 to 20.04, the bluetooth headset doesn't work anymore when HSP/HFP profile is selected. With Ubuntu 19.10 the headset was working, there was audio and the mic was perfect for video conferencing. [Steps to reproduce] 1. Connect headset (used blueman to setup and connect) 1.1. When connected the system automatically selects A2DP profile 2. Start playing audio (browser or other) 3. Change profile to HSP/HFP with pavucontrol (or blueman) 4. The audio disappears and microphone is not working (no input) 5. Optionally switch back to A2DP and the audio comes back [Expected] When switching to HSP/HFP the audio should keep playing and the microphone should start working [Notes] I tried with pavucontrol to switch between profiles while playing audio from a browser. As side note there's a led in the headset that still blinks when switching profile. I tried deleting the pulse folder under user's profile .config without success, also reinstalled packages and did a `sudo alsa force-reload` and rebooting several times. Note: not sure this is a duplicate of [Bug #1576559], it looks quite different since the profile changes but the headset stops working. [System info] Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64 pulseaudio: 1:13.99.1-1ubuntu3 bluez: 5.53-0ubuntu3 Headset: Sennheiser HD 4.50 BTNC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1878194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1896726] Comment bridged from LTC Bugzilla
--- Comment From klaus.theur...@de.ibm.com 2020-09-29 03:27 EDT---
(In reply to comment #166)
> I took this from "linux-next" (where it was tagged with 'next-20200923') as:
> ~/linux-next$ git show a02b55ea66b9
> commit a02b55ea66b9257744528da609a26279152a3bc3
> Author: Vasily Gorbik
> Date: Wed Sep 23 09:49:28 2020 +1000
>
> mm/gup: fix gup_fast with dynamic page table folding
>
> Currently to make sure that every page table entry is read just once
> gup_fast walks perform READ_ONCE and pass pXd value down to the next
> gup_pXd_range function by value e.g.:
>
> static int gup_pud_range(p4d_t p4d, unsigned long addr, unsigned long end,
> unsigned int flags, struct page **pages, int *nr)
> ...
>
> and built a patched groovy and a patched focal kernel, available here:
> https://people.canonical.com/~fheimes/lp1896726/
>
> Do you have a chance giving these a try?
I'll run a test with my MongoDB setup.
Can you provide the debug symbol package for the kernel as well?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1896726
Title:
[UBUNTU 20.04.1] qemu (secure guest) crash due to gup_fast / dynamic
page table folding issue
Status in Ubuntu on IBM z Systems:
In Progress
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Focal:
Incomplete
Status in linux source package in Groovy:
In Progress
Bug description:
Justification:
==
Secure KVM guest (using secure execution on Ubuntu Server 20.04 for s390x)
crashes happen from time to time during boot.
Such crashed guests ("reason=crashed" in the libvirt log) end up in hutoff
state instead of crashed state ( preserve is set).
The crash points to a kernel memory management problem, addressed by the
following patch/fix.
The modifications touch common memory management code,
but it will have no effect to architectures other than s390x.
This is ensured by the fact that only s390 provides / implements the new
helper functions.
And for s390x, this is actually a critical (and carefully tested) fix for a
(previous) regression, so it can hardly get any more regressive.
The patch landed upstream in linux-next, is in depth discussed
at LKML https://lkml.kernel.org/r/20190418100218.0a4afd51@mschwideX1
and here
https://lore.kernel.org/linux-arch/patch.git-943f1e5dcff2.your-ad-here.call-01599856292-ext-8676@work.hours/
and will soon land via the regular upstream stable release update for kernel
5.4 in focal, too.
The process already started:
https://lore.kernel.org/stable/patch-1.thread-41918b.git-41918be365c0.your-ad-here.call-01600439945-ext-8991@work.hours/
Hence this cherry-pick from the upstream patch should be added to groovy
to avoid any potential regression in case the patch landed in focal via the
upstream release update process,
but is not in groovy and someones upgrades from focal to groovy.
__
Secure Execution with Ubuntu 20.04, secure guest crash during boot
from time to time, crashed guest went into Shufoff state instead of
Crashed state (preserve is set), so I can't get a dump.
libvirt log file:
2020-04-21T16:35:39.382999Z qemu-system-s390x: Guest says index 19608 is
available
2020-04-21 16:35:44.831+: shutting down, reason=crashed
---uname output---
Linux ubu204uclg1002 5.4.0-25-generic #29-Ubuntu SMP Fri Apr 17 15:05:32 UTC
2020 s390x s390x s390x GNU/Linux
Machine Type = z15 8561
---Debugger---
A debugger is not configured
---Steps to Reproduce---
I have a setup with 72 KVM guests which I can start in secure or non-secure
mode. Starting all of them in secure mode back to back results in a number of
guests (4..8) in Shutoff state and reason=crashed in the libvirt log. I can
manually start the guest again no problem. Different guests are failing.
Host and guests are on latest Ubuntu 20.04.
The supposed fix (kernel memory management) has landed in Andrew Mortons mm
tree
https://lore.kernel.org/mm-commits/20200916003608.ib4ln%25a...@linux-foundation.org/T/#u
Please note: while this was found with secure execution, the bug is
actually present for non-KVM workloads as well.
The complete patch is this:
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=a338e69ba37286c0fc300ab7e6fa0227e6ca68b1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1896726/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1871306] Re: No sound from internal card chtmax98090 - missing UCM2 files in alsa-ucm-conf 1.2.2, available in alsa-ucm-conf 1.2.3
Thank you so much Hui to handle this bug, feel free to ask me for testing on real hardware. For 20.04 and newer, to fix this bug also fixes bug 1833116 https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1833116 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1871306 Title: No sound from internal card chtmax98090 - missing UCM2 files in alsa- ucm-conf 1.2.2, available in alsa-ucm-conf 1.2.3 Status in alsa-ucm-conf package in Ubuntu: Confirmed Bug description: Asus C300 (repurposed chromembook - bios flashed by Mr.Chromebox script) - Kubuntu Focal minimal fresh installation. The sound card is detected: I see it in the Plasma Widget, in pavucontrol, in alsamixer and it's not muted. I tried and add in /usr/share/alsa/ucm/chtmax98090/ the old style use case config files: no success. I tried and unmute speakers left and right in alsamixer: no success. I rapidly tested Ubuntu Mate Focal fresh install: I had exactly the same issue. I'm running on the same rig Debian Bullseye, kernel 5.4: sound card output and input are both working perfectly - I noticed that in Kubuntu alsamixer Kubuntu when I open it I have an entry HDA IntelPCH (the HDMI card), while in Debian I find Pulseaudio. I attach the alsa-info.sh output. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.17 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: KDE Date: Tue Apr 7 08:55:46 2020 InstallationDate: Installed on 2020-04-04 (2 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gabriel3937 F pulseaudio /dev/snd/controlC0: gabriel3937 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-04 (3 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:07dc Intel Corp. Bus 001 Device 003: ID 13d3:5657 IMC Networks USB2.0 UVC HD Webcam Bus 001 Device 002: ID 062a:4101 MosArt Semiconductor Corp. Wireless Keyboard/Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: GOOGLE Quawks Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=225cba91-c164-4882-95d4-4f9854a80fe9 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/17/2020 dmi.bios.vendor: coreboot dmi.bios.version: MrChromebox-4.11.2 dmi.board.name: Quawks dmi.board.vendor: GOOGLE dmi.board.version: 1.0 dmi.chassis.type: 9 dmi.chassis.vendor: GOOGLE dmi.modalias: dmi:bvncoreboot:bvrMrChromebox-4.11.2:bd03/17/2020:svnGOOGLE:pnQuawks:pvr1.0:rvnGOOGLE:rnQuawks:rvr1.0:cvnGOOGLE:ct9:cvr: dmi.product.name: Quawks dmi.product.version: 1.0 dmi.sys.vendor: GOOGLE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1871306/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1896482] Re: acpi event detection crashes
** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Alex Hung (alexhung) ** Changed in: linux (Ubuntu) Assignee: Alex Hung (alexhung) => (unassigned) ** Changed in: linux (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1896482 Title: acpi event detection crashes Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: In Progress Bug description: = SRU Justification = [Impact] The bug causes the EC driver to fail and ACPI events are no longer handled by Linux kernel, i.e lid close no longer triggers suspends. [Fix] Upstream commit 03e9a0e05739cf reworks ec_install_handlers to avoid initialisation failures. The other three patches are prerequisite to apply 03e9a0e05739cf on focal kernel. [Test] Tested with Lenovo ThinkPad X1 Carbon Gen 8 [Regression Potential] Low. The patches were cherry-picked from mainline kernel (two since 5.5 and two since 5.7) = Original Bug Report = Right after booting, acpi lid open/close is detected as it should be by the kernel, but some time later it crashes, so I have to manually suspend the system. The traceback is here: Sep 20 11:35:33 laxmi kernel: [232492.303557] [ cut here ] Sep 20 11:35:33 laxmi kernel: [232492.303564] WARNING: CPU: 0 PID: 8302 at kernel/workqueue.c:1416 __queue_work+0x337/0x3f0 Sep 20 11:35:33 laxmi kernel: [232492.303565] Modules linked in: ccm rfcomm cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 snd_soc_skl_hda_dsp snd_hda_codec_hdmi snd_soc_hdac_hdmi snd_hda_codec_realtek snd_soc_dmic snd_hda_codec_generic snd_sof_pci mei_hdcp x86_pkg_temp_thermal intel_powerclamp intel_rapl_msr coretemp snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda kvm_intel snd_sof_intel_byt snd_sof_intel_ipc kvm snd_sof snd_sof_xtensa_dsp snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine joydev crct10dif_pclmul ghash_clmulni_intel snd_hda_intel aesni_intel snd_intel_dspcfg crypto_simd iwlmvm cryptd snd_hda_codec glue_helper rapl mac80211 snd_hda_core snd_seq_midi snd_hwdep snd_seq_midi_event libarc4 intel_cstate uvcvideo snd_rawmidi i915 snd_pcm videobuf2_vmalloc input_leds thinkpad_acpi btusb videobuf2_memops serio_raw btrtl videobuf2_v4l2 snd_seq btbcm btintel nvram videobuf2_common iwlwifi processor_thermal_device bluetooth videodev Sep 20 11:35:33 laxmi kernel: [232492.303600] drm_kms_helper mc wmi_bmof i2c_algo_bit intel_rapl_common fb_sys_fops ucsi_acpi intel_wmi_thunderbolt ecdh_generic ledtrig_audio typec_ucsi mei_me syscopyarea hid_multitouch snd_seq_device sysfillrect cfg80211 ecc sysimgblt mei intel_soc_dts_iosf typec snd_timer snd soundcore int3403_thermal int340x_thermal_zone acpi_pad intel_hid int3400_thermal acpi_thermal_rel sparse_keymap mac_hid sch_fq_codel parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_generic crc32_pclmul nvme psmouse e1000e i2c_i801 thunderbolt intel_lpss_pci intel_lpss nvme_core idma64 virt_dma i2c_hid hid wmi video pinctrl_cannonlake pinctrl_intel Sep 20 11:35:33 laxmi kernel: [232492.303628] CPU: 0 PID: 8302 Comm: kworker/0:0 Not tainted 5.4.0-47-generic #51-Ubuntu Sep 20 11:35:33 laxmi kernel: [232492.303629] Hardware name: LENOVO 20U9001NUS/20U9001NUS, BIOS N2WET19W (1.09 ) 07/01/2020 Sep 20 11:35:33 laxmi kernel: [232492.303632] Workqueue: kec_query acpi_ec_event_processor Sep 20 11:35:33 laxmi kernel: [232492.303635] RIP: 0010:__queue_work+0x337/0x3f0 Sep 20 11:35:33 laxmi kernel: [232492.303637] Code: ff 49 8b 9d a0 00 00 00 e9 aa fd ff ff 65 8b 05 e7 59 15 6d a9 00 01 1f 00 75 0f 65 48 8b 3c 25 c0 6b 01 00 f6 47 24 20 75 25 <0f> 0b 48 83 c4 18 5b 41 5c 41 5d 41 5e 41 5f 5d c3 0f 0b e9 fd fd Sep 20 11:35:33 laxmi kernel: [232492.303638] RSP: 0018:b16bc0ebb8f8 EFLAGS: 00010087 Sep 20 11:35:33 laxmi kernel: [232492.303640] RAX: 9a2477432600 RBX: 0002 RCX: 0004 Sep 20 11:35:33 laxmi kernel: [232492.303641] RDX: 9a2475af4a90 RSI: 9a2475b03200 RDI: 9a2430215f00 Sep 20 11:35:33 laxmi kernel: [232492.303642] RBP: b16bc0ebb938 R08: R09: 0007 Sep 20 11:35:33 laxmi kernel: [232492.303643] R10: 9a24755ad678 R11: R12: 9a2475af4a00 Sep 20 11:35:33 laxmi kernel: [232492.303643] R13: 9a2475b03200 R14: 2000 R15: 9a2475af4a90 Sep 20 11:35:33 laxmi kernel: [232492.303645] FS: () GS:9a247740() knlGS: Sep 20 11:35:33 laxmi kernel: [232492.303646] CS: 0010 DS: ES: CR0: 80050033 Sep 20 11:35:33 laxmi kernel: [232492.303647] CR2: 00c42098b000 CR3: 00018520a003 CR4: 003606f0 Sep 20 11:35:33
[Kernel-packages] [Bug 1833116] Re: [chtmax98090 on Bay Trail Chromebooks] audio not working, shows "Dummy Output"
For Focal Fossa 20.04 and newer releases, check bug 1871306 out: https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1871306 The bug has been assigned, the priority is now high: we're going to have it fixed. Temporary work around: get the missing config UCM2 files from alsa project github or install alsa-ucm-conf 1.2.3 from Debian testing. Links alsa-project github: https://github.com/alsa-project/alsa-ucm-conf/tree/master/ucm2/chtmax98090 https://github.com/alsa-project/alsa-ucm-conf/tree/master/ucm2/codecs/max98090 debian testing package: https://packages.debian.org/bullseye/all/alsa-ucm-conf/download -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1833116 Title: [chtmax98090 on Bay Trail Chromebooks] audio not working, shows "Dummy Output" Status in alsa-driver package in Ubuntu: Confirmed Status in alsa-ucm-conf package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: chtmax98090 intel HD audio device doesn't work out of the box after installing ubuntu (from 14.04 to 18.04). It shows "Dummy Output" on audio devices. Audio options shows device and it works if I do this: git clone https://github.com/plbossart/UCM.git cd UCM cp -r chtmax98090/ /usr/share/alsa/ucm/ alsactl store It would be great if there were a solution to make it works out of the box. The device (Chromebook Acer CB3-111 has it's end of life for chromeOS in July-August, so I suppose more people with this device will change OS perhaps to Ubuntu). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-21-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jaime 1293 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jun 17 20:32:35 2019 InstallationDate: Installed on 2019-06-17 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/18/2014 dmi.bios.vendor: coreboot dmi.chassis.type: 3 dmi.chassis.vendor: GOOGLE dmi.modalias: dmi:bvncoreboot:bvr:bd08/18/2014:svnGOOGLE:pnGnawty:pvr1.0:cvnGOOGLE:ct3:cvr: dmi.product.name: Gnawty dmi.product.version: 1.0 dmi.sys.vendor: GOOGLE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1833116/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1870368] Re: ACPI BIOS Error in kernel log
For the record, the bug is still there. The following is taken from a post-suspend dmesg command. Impossible to get my USB-C to ethernet adapter to work until I reboot. This happens quite often. I have to reboot from time to time in order to get network back. You can imagine how frustrating it is when you find yourself being afraid of disconnecting or suspending your laptop to avoid having to restart all your apps to get back in current context of your work. I am using the latest 20.04.1. [32351.925853] pci_bus :04: busn_res: [bus 04] is released [32351.925981] pci_bus :05: busn_res: [bus 05-39] is released [32351.926040] pci_bus :3a: busn_res: [bus 3a] is released [32351.926099] pci_bus :03: busn_res: [bus 03-3a] is released [32359.926066] ACPI BIOS Error (bug): Failure creating named object [\_GPE.XTBT.SPRT], AE_ALREADY_EXISTS (20190816/dswload2-326) [32359.926091] Initialized Local Variables for Method [XTBT]: [32359.926093] Local0: a09cb06c Integer 0001 [32359.926105] Initialized Arguments for Method [XTBT]: (2 arguments defined for method invocation) [32359.926107] Arg0: 885e4213 Integer 0011 [32359.926114] Arg1: 68996c7b Integer 0001 [32359.926122] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220) [32359.926130] ACPI Error: Aborting method \_GPE.XTBT due to previous error (AE_ALREADY_EXISTS) (20190816/psparse-529) [32359.926143] ACPI Error: Aborting method \_GPE.XTBT due to previous error (AE_ALREADY_EXISTS) (20190816/psparse-529) [32359.926165] ACPI Error: Aborting method \_GPE._E42 due to previous error (AE_ALREADY_EXISTS) (20190816/psparse-529) [32359.926180] ACPI Error: AE_ALREADY_EXISTS, while evaluating GPE method [_E42] (20190816/evgpe-511) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1870368 Title: ACPI BIOS Error in kernel log Status in linux package in Ubuntu: Confirmed Bug description: Had this with 19.04. Still there with 19.10. AFAIK, there is no other symptom than the logged errors. Looks like : Apr 2 08:55:21 clairetnet kernel: [0.124577] ACPI: Added _OSI(Module Device) Apr 2 08:55:21 clairetnet kernel: [0.124578] ACPI: Added _OSI(Processor Device) Apr 2 08:55:21 clairetnet kernel: [0.124578] ACPI: Added _OSI(3.0 _SCP Extensions) Apr 2 08:55:21 clairetnet kernel: [0.124578] ACPI: Added _OSI(Processor Aggregator Device) Apr 2 08:55:21 clairetnet kernel: [0.124579] ACPI: Added _OSI(Linux-Dell-Video) Apr 2 08:55:21 clairetnet kernel: [0.124580] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio) Apr 2 08:55:21 clairetnet kernel: [0.124580] ACPI: Added _OSI(Linux-HPI-Hybrid-Graphics) Apr 2 08:55:21 clairetnet kernel: [0.124581] ACPI: Added _OSI(Linux) Apr 2 08:55:21 clairetnet kernel: [0.167243] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS01._UPC], AE_ALREADY_EXISTS (20190703/dswload2-323) Apr 2 08:55:21 clairetnet kernel: [0.167248] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190703/psobject-220) Apr 2 08:55:21 clairetnet kernel: [0.167249] ACPI: Skipping parse of AML opcode: Method (0x0014) [continue with more of the same] ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-45-generic 5.3.0-45.37 ProcVersionSignature: Ubuntu 5.3.0-45.37-generic 5.3.18 Uname: Linux 5.3.0-45-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: stan 2268 F pulseaudio /dev/snd/pcmC0D0p: stan 2268 F...m pulseaudio /dev/snd/controlC1: stan 2268 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 2 16:42:59 2020 InstallationDate: Installed on 2019-04-26 (341 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. Precision 5530 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-45-generic root=UUID=2262d308-663c-47c3-9e75-b34611c8df1d ro nouveau.blacklist=1 acpi_rev_override=1 acpi_osi=Linux nouveau.modeset=0 pcie_aspm=force drm.vblankoffdelay=1 scsi_mod.use_blk_mq=1 nouveau.runpm=0 mem_sleep_default=deep quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-45-generic N/A linux-backports-modules-5.3.0-45-generic N/A linux-firmware1.183.4 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-11-04 (150 days ago) dmi.bios.date: 12/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0N0DK2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc.
[Kernel-packages] [Bug 1878105] Re: [nvidia] Xorg crashes in ?? from FreeCursor() from ChangeWindowAttributes()
I must add to the previous comment : when I am in UHD resolution, with 200% zoom. -- 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/1878105 Title: [nvidia] Xorg crashes in ?? from FreeCursor() from ChangeWindowAttributes() Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: Crash is caused when visiting websites that attempt to customize the cursor layout. (Tested with Firefox 76.0 (64-bit)) The website on which the crash first occurred was the following: https://www.yellibeanz.com/ the crash is triggered after moving the cursor around. To test the hypothesis of the cursor causing the bug I also tested the following website with identical outcome: http://www.flockofsiegel.tv/ I am sure that one can find more examples here: https://onextrapixel.com/10-websites-that-replace-mouse-cursors-for-a -better-cause/ lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 apt-cache policy xorg xorg: Installed: 1:7.7+19ubuntu14 Candidate: 1:7.7+19ubuntu14 Version table: *** 1:7.7+19ubuntu14 500 500 http://nl.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 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 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 11 23:58:41 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-28-generic, x86_64: installed nvidia, 440.64, 5.4.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 630 (Mobile) [1043:1fc0] Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:1fc0] InstallationDate: Installed on 2020-05-03 (8 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 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 13d3:56a2 IMC Networks USB2.0 HD UVC WebCam Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X580GD_N580GD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=04dedfb2-c5a9-4447-af72-16999d76fce2 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X580GD.309 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X580GD 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.:bvrX580GD.309:bd10/18/2018:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX580GD_N580GD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX580GD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: VivoBook_ASUSLaptop X580GD_N580GD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel
[Kernel-packages] [Bug 1896725] Re: xenial 4.4.0-191-generic in -proposed has a regression
Just to clarify, When reverting one version back to 4.4.0-1114-aws, no panic was found and instances boot successfully -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1896725 Title: xenial 4.4.0-191-generic in -proposed has a regression Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Bug description: [Impact] The new xenial kernel in -proposed, 4.4.0-191-generic, and its derivatives, such as 4.4.0-1115-aws suffer a kernel panic on boot on AWS. I tested t2.micro and t2.medium, it happens every time. Simply install the kernel from -proposed and reboot, we get the following oops: [0.549557] BUG: unable to handle kernel paging request at ff5f3000 [0.552000] IP: [] mp_irqdomain_activate+0x5f/0xa0 [0.552000] PGD 1e0f067 PUD 1e11067 PMD 1e12067 PTE 0 [0.552000] Oops: 0002 [#1] SMP [0.552000] Modules linked in: [0.552000] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 4.4.0-191-generic #221-Ubuntu [0.552000] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006 [0.552000] task: 88010a0f ti: 88010a0f8000 task.ti: 88010a0f8000 [0.552000] RIP: 0010:[] [] mp_irqdomain_activate+0x5f/0xa0 [0.552000] RSP: :88010a0fbc48 EFLAGS: 00010086 [0.552000] RAX: 0086 RBX: 88010a1df480 RCX: [0.552000] RDX: ff5f3000 RSI: 0001 RDI: 0020c000 [0.552000] RBP: 88010a0fbc50 R08: 81ebdfd0 R09: [0.552000] R10: 0011 R11: 0009 R12: 88010ad95400 [0.552000] R13: 0001 R14: 0009 R15: 88010a1fc480 [0.552000] FS: () GS:88010b24() knlGS: [0.552000] CS: 0010 DS: ES: CR0: 80050033 [0.552000] CR2: ff5f3000 CR3: 01e0a000 CR4: 00160670 [0.552000] DR0: DR1: DR2: [0.552000] DR3: DR6: fffe0ff0 DR7: 0400 [0.552000] Stack: [0.552000] 88010ac0ba58 88010a0fbc70 810ea644 88010ac0ba00 [0.552000] 88010ac0ba58 88010a0fbca0 810e6d88 810e1009 [0.552000] 88010ac0ba00 88010ac0baa0 88010a1fc480 88010a0fbd38 [0.552000] Call Trace: [0.552000] [] irq_domain_activate_irq+0x44/0x50 [0.552000] [] irq_startup+0x38/0x90 [0.552000] [] ? vprintk_default+0x29/0x40 [0.552000] [] __setup_irq+0x5a2/0x650 [0.552000] [] ? kmem_cache_alloc_trace+0x1d4/0x1f0 [0.552000] [] ? acpi_osi_handler+0xb0/0xb0 [0.552000] [] request_threaded_irq+0xfb/0x1a0 [0.552000] [] ? acpi_osi_handler+0xb0/0xb0 [0.552000] [] ? acpi_ev_sci_dispatch+0x64/0x64 [0.552000] [] acpi_os_install_interrupt_handler+0xaa/0x100 [0.552000] [] ? acpi_sleep_proc_init+0x28/0x28 [0.552000] [] acpi_ev_install_sci_handler+0x23/0x25 [0.552000] [] acpi_ev_install_xrupt_handlers+0x1c/0x6c [0.552000] [] acpi_enable_subsystem+0x8f/0x93 [0.552000] [] acpi_init+0x8b/0x2c4 [0.552000] [] ? kasprintf+0x4e/0x70 [0.552000] [] ? acpi_sleep_proc_init+0x28/0x28 [0.552000] [] do_one_initcall+0xb5/0x200 [0.552000] [] ? parse_args+0x29a/0x4a0 [0.552000] [] kernel_init_freeable+0x177/0x218 [0.552000] [] ? rest_init+0x80/0x80 [0.552000] [] kernel_init+0xe/0xe0 [0.552000] [] ret_from_fork+0x55/0x80 [0.552000] [] ? rest_init+0x80/0x80 [0.552000] Code: 8d 1c d2 8d ba 0b 02 00 00 44 8d 51 11 42 8b 14 dd 74 ec 10 82 c1 e7 0c 48 63 ff 81 e2 ff 0f 00 00 48 81 ea 00 10 80 00 48 29 fa <44> 89 12 89 72 10 42 8b 14 dd 74 ec 10 82 83 c1 10 81 e2 ff 0f [0.552000] RIP [] mp_irqdomain_activate+0x5f/0xa0 [0.996006] RSP [0.996006] CR2: ff5f3000 [0.996006] ---[ end trace 1d0c3bd610d641a0 ]--- [1.012018] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0009 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1896725/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1896482] Re: acpi event detection crashes
** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Focal) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1896482 Title: acpi event detection crashes Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Bug description: = SRU Justification = [Impact] The bug causes the EC driver to fail and ACPI events are no longer handled by Linux kernel, i.e lid close no longer triggers suspends. [Fix] Upstream commit 03e9a0e05739cf reworks ec_install_handlers to avoid initialisation failures. The other three patches are prerequisite to apply 03e9a0e05739cf on focal kernel. [Test] Tested with Lenovo ThinkPad X1 Carbon Gen 8 [Regression Potential] Low. The patches were cherry-picked from mainline kernel (two since 5.5 and two since 5.7) = Original Bug Report = Right after booting, acpi lid open/close is detected as it should be by the kernel, but some time later it crashes, so I have to manually suspend the system. The traceback is here: Sep 20 11:35:33 laxmi kernel: [232492.303557] [ cut here ] Sep 20 11:35:33 laxmi kernel: [232492.303564] WARNING: CPU: 0 PID: 8302 at kernel/workqueue.c:1416 __queue_work+0x337/0x3f0 Sep 20 11:35:33 laxmi kernel: [232492.303565] Modules linked in: ccm rfcomm cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 snd_soc_skl_hda_dsp snd_hda_codec_hdmi snd_soc_hdac_hdmi snd_hda_codec_realtek snd_soc_dmic snd_hda_codec_generic snd_sof_pci mei_hdcp x86_pkg_temp_thermal intel_powerclamp intel_rapl_msr coretemp snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda kvm_intel snd_sof_intel_byt snd_sof_intel_ipc kvm snd_sof snd_sof_xtensa_dsp snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine joydev crct10dif_pclmul ghash_clmulni_intel snd_hda_intel aesni_intel snd_intel_dspcfg crypto_simd iwlmvm cryptd snd_hda_codec glue_helper rapl mac80211 snd_hda_core snd_seq_midi snd_hwdep snd_seq_midi_event libarc4 intel_cstate uvcvideo snd_rawmidi i915 snd_pcm videobuf2_vmalloc input_leds thinkpad_acpi btusb videobuf2_memops serio_raw btrtl videobuf2_v4l2 snd_seq btbcm btintel nvram videobuf2_common iwlwifi processor_thermal_device bluetooth videodev Sep 20 11:35:33 laxmi kernel: [232492.303600] drm_kms_helper mc wmi_bmof i2c_algo_bit intel_rapl_common fb_sys_fops ucsi_acpi intel_wmi_thunderbolt ecdh_generic ledtrig_audio typec_ucsi mei_me syscopyarea hid_multitouch snd_seq_device sysfillrect cfg80211 ecc sysimgblt mei intel_soc_dts_iosf typec snd_timer snd soundcore int3403_thermal int340x_thermal_zone acpi_pad intel_hid int3400_thermal acpi_thermal_rel sparse_keymap mac_hid sch_fq_codel parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_generic crc32_pclmul nvme psmouse e1000e i2c_i801 thunderbolt intel_lpss_pci intel_lpss nvme_core idma64 virt_dma i2c_hid hid wmi video pinctrl_cannonlake pinctrl_intel Sep 20 11:35:33 laxmi kernel: [232492.303628] CPU: 0 PID: 8302 Comm: kworker/0:0 Not tainted 5.4.0-47-generic #51-Ubuntu Sep 20 11:35:33 laxmi kernel: [232492.303629] Hardware name: LENOVO 20U9001NUS/20U9001NUS, BIOS N2WET19W (1.09 ) 07/01/2020 Sep 20 11:35:33 laxmi kernel: [232492.303632] Workqueue: kec_query acpi_ec_event_processor Sep 20 11:35:33 laxmi kernel: [232492.303635] RIP: 0010:__queue_work+0x337/0x3f0 Sep 20 11:35:33 laxmi kernel: [232492.303637] Code: ff 49 8b 9d a0 00 00 00 e9 aa fd ff ff 65 8b 05 e7 59 15 6d a9 00 01 1f 00 75 0f 65 48 8b 3c 25 c0 6b 01 00 f6 47 24 20 75 25 <0f> 0b 48 83 c4 18 5b 41 5c 41 5d 41 5e 41 5f 5d c3 0f 0b e9 fd fd Sep 20 11:35:33 laxmi kernel: [232492.303638] RSP: 0018:b16bc0ebb8f8 EFLAGS: 00010087 Sep 20 11:35:33 laxmi kernel: [232492.303640] RAX: 9a2477432600 RBX: 0002 RCX: 0004 Sep 20 11:35:33 laxmi kernel: [232492.303641] RDX: 9a2475af4a90 RSI: 9a2475b03200 RDI: 9a2430215f00 Sep 20 11:35:33 laxmi kernel: [232492.303642] RBP: b16bc0ebb938 R08: R09: 0007 Sep 20 11:35:33 laxmi kernel: [232492.303643] R10: 9a24755ad678 R11: R12: 9a2475af4a00 Sep 20 11:35:33 laxmi kernel: [232492.303643] R13: 9a2475b03200 R14: 2000 R15: 9a2475af4a90 Sep 20 11:35:33 laxmi kernel: [232492.303645] FS: () GS:9a247740() knlGS: Sep 20 11:35:33 laxmi kernel: [232492.303646] CS: 0010 DS: ES: CR0: 80050033 Sep 20 11:35:33 laxmi kernel: [232492.303647] CR2: 00c42098b000 CR3: 00018520a003 CR4: 003606f0 Sep 20 11:35:33 laxmi kernel:
[Kernel-packages] [Bug 1868396] Re: Xorg crashed with SIGABRT in nvidia_drv.so
I am currently using 450.66 from 20.04.1 and experiencing no more crash so far. Something has been fixed somewhere I guess. -- 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/1868396 Title: Xorg crashed with SIGABRT in nvidia_drv.so Status in nvidia-graphics-drivers-440 package in Ubuntu: New Bug description: I have plugged in my Dell precision 5530 laptop a 4k HDMI screen. Using it with 200% zoom makes xorg crash. I have used proprietary 430, and changed to recommended proprietary 435 nvidia driver. As the system was still very unstable (no to say unusable) I had a go with 440 from ppa. I also ensured that my system was up to date doing a sudo apt-get update and upgrade. I was suprised to discover a few packages that needed an upgrade although I had previously used the Software Updater tool. Maybe I was doing something wrong. Anyway, with these updates and the newer 440 driver, I have successfully worked a day (sparsely) without problem, and using only 100% zoom. As a test, I decided to try to set the zoom to 200% (through devices > display, and I have only the external display enabled). After several minutes, I clicked on the « full screen » icon to maximize a shell, and the PC froze. It was so close to my change in the zoom ratio, that I suspect this is related. dmesg shew me that NVRM had a problem : [97501.301998] NVRM: GPU at PCI::01:00: GPU-dee28f75-4083-96a8-1a0b-491b6109101a [97501.302000] NVRM: Xid (PCI::01:00): 32, pid=493, Channel ID 0018 intr 0004 [97501.302134] NVRM: Xid (PCI::01:00): 32, pid=2052, Channel ID 0018 intr 0020 [97501.317307] NVRM: Xid (PCI::01:00): 69, pid=902, Class Error: ChId 001b, Class 902d, Offset 0250, Data 55d3, ErrorCode 000c pid 493 is gone pid 2052 is xorg stan 2052 2050 1 mars20 tty200:25:38 /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth /run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 3 pid 902 is nvidia driver root 902 2 0 mars20 ? 00:02:59 [irq/163-nvidia] ppid 2052 is 2050 : stan 2050 2004 0 mars20 tty200:00:00 /usr/lib/gdm3/gdm-x-session --run-script env GNOME_SHELL_SESSION_MODE=ubuntu /usr/bin/gnome-session --systemd --session=ubuntu After such an event, the previous days, the system became unstable, and I have got problems with other devices such as audio and network. If I run the manufacturer self-check test, everything is fine. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Mar 21 18:36:53 2020 DistUpgraded: 2019-11-04 11:06:46,434 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.3.0-42-generic, x86_64: installed virtualbox, 6.0.14, 5.3.0-40-generic, x86_64: installed virtualbox, 6.0.14, 5.3.0-42-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:087d] Subsystem: Dell GP107GLM [Quadro P2000 Mobile] [1028:087d] InstallationDate: Installed on 2019-04-26 (329 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. Precision 5530 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic root=UUID=2262d308-663c-47c3-9e75-b34611c8df1d ro nouveau.blacklist=1 acpi_rev_override=1 acpi_osi=Linux nouveau.modeset=0 pcie_aspm=force drm.vblankoffdelay=1 scsi_mod.use_blk_mq=1 nouveau.runpm=0 mem_sleep_default=deep quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to eoan on 2019-11-04 (138 days ago) dmi.bios.date: 12/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0
[Kernel-packages] [Bug 1878105] Re: [nvidia] Xorg crashes in ?? from FreeCursor() from ChangeWindowAttributes()
Looks like it the crash has been prevented, at least in 450.66 from Ubuntu repository, 20.04.1. But the cursor size setting looks limited now : If I use Setting GUI and go to the Universal Access > Cursor Size setting, I’m displayed five cursors to choose from. If I select one of the three smallest, the cursor size is immediately set to the selected size. If I select one of the two biggest, the cursor size remains the biggest of the three previous sizes (named « large »). -- 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/1878105 Title: [nvidia] Xorg crashes in ?? from FreeCursor() from ChangeWindowAttributes() Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: Crash is caused when visiting websites that attempt to customize the cursor layout. (Tested with Firefox 76.0 (64-bit)) The website on which the crash first occurred was the following: https://www.yellibeanz.com/ the crash is triggered after moving the cursor around. To test the hypothesis of the cursor causing the bug I also tested the following website with identical outcome: http://www.flockofsiegel.tv/ I am sure that one can find more examples here: https://onextrapixel.com/10-websites-that-replace-mouse-cursors-for-a -better-cause/ lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 apt-cache policy xorg xorg: Installed: 1:7.7+19ubuntu14 Candidate: 1:7.7+19ubuntu14 Version table: *** 1:7.7+19ubuntu14 500 500 http://nl.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 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 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 11 23:58:41 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-28-generic, x86_64: installed nvidia, 440.64, 5.4.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 630 (Mobile) [1043:1fc0] Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:1fc0] InstallationDate: Installed on 2020-05-03 (8 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 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 13d3:56a2 IMC Networks USB2.0 HD UVC WebCam Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X580GD_N580GD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=04dedfb2-c5a9-4447-af72-16999d76fce2 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X580GD.309 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X580GD 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.:bvrX580GD.309:bd10/18/2018:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX580GD_N580GD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX580GD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: VivoBook_ASUSLaptop X580GD_N580GD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri:
