[Kernel-packages] [Bug 1902093] Re: Introduce the new NVIDIA 455 series
The link of test results is as follows. https://docs.google.com/spreadsheets/d/1ga7U4PUHjV2TF8ihcsDaEUdoGp7M7Iz11zVs442ZARw/edit?usp=sharing -- 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/1902093 Title: Introduce the new NVIDIA 455 series Status in linux package in Ubuntu: Confirmed Status in linux-restricted-modules package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-455 package in Ubuntu: In Progress Status in linux source package in Bionic: Confirmed Status in linux-restricted-modules source package in Bionic: Confirmed Status in nvidia-graphics-drivers-455 source package in Bionic: Fix Committed Status in linux source package in Focal: Confirmed Status in linux-restricted-modules source package in Focal: Confirmed Status in nvidia-graphics-drivers-455 source package in Focal: Fix Committed Status in linux source package in Groovy: Confirmed Status in linux-restricted-modules source package in Groovy: Confirmed Status in nvidia-graphics-drivers-455 source package in Groovy: Fix Committed Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] * New upstream release: - Added support for the following GPUs: GeForce RTX 3070 - Added support for using an NVIDIA-driven display as a PRIME Display Offload sink with a PRIME Display Offload source driven by the xf86-video-intel driver. - Fixed a bug in a Vulkan barrier optimization that allowed some back-to-back copies to run unordered. - Fixed a performance regression in the NVIDIA X driver which affected some X11 RENDER extension use cases. - Added AMD Secure Memory Encryption compatibility. * debian/templates/control.in: - Set support level to NFB instead of Beta. - Add support for CUDA 11. Note: this will be the initial release for Bionic and Focal. Changelog entries for the linux-restricted-modules: UBUNTU: [Packaging] NVIDIA -- provide the nvidia-prebuilt-kernel virtual package Make all the NVIDIA drivers, except for 390, provide the nvidia-prebuilt-kernel virtual package. This allows adding a generic dependency on the signed modules. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902093/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903388] Re: Failure to write to NVMe disk soon after boot (APST-related)
Please test latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.10-rc3/amd64/ ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1903388 Title: Failure to write to NVMe disk soon after boot (APST-related) Status in linux package in Ubuntu: Incomplete Bug description: Hi all, This one is similar to #1805816 and #1678184 (one was fixed, other closed). Symptoms: During regular use, system starts failing after 10m - 1hr after start. Icons start disappearing, writing to disk fails. In-memory operations still work for a while (switching windows, streaming video calls, typing). After some time the entire system crashes, with a Black Screen Of Death constantly looping: --- EXT4-fs error (device nvme0n1p5) ext4_find_entry:1455: inode #4594258: comm gmain: reading directory lblock 0 [... same repeats for 8 times on average] systemd-journald[439]: Failed to write entry (9 items, 270 bytes), ignoring: Read-only file system [... repeats for 10 times on average] --- Probable causes: Updated both kernel and BIOS 2 days ago. Unable to determine, which one caused the change. Don't know how to determine which kernel and bios I was running before the update. Looks like APST issue, based on info from web and previous bug reports. Verification: Created a rudimentary bash script, writing to a file in a loop, incrementing timeout between two consecutive writes each time. Ran script using: - different nvme_core.default_ps_max_latency_us settings in GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=[0|200|5500]" - regular boot mode - logged in to account - on battery power With default_ps_max_latency_us NOT SET: writing FAILS between 57 and 70 seconds timeout between writes With default_ps_max_latency_us=5500: no write failure during 1hrs run With default_ps_max_latency_us=200: no write failure during 30m run With latency 0: no write failure during 10m run This suggests an APST issue. Machine: Lenovo Thinkpad T570 Disk: SAMSUNG MZVLB512HAJQ-000L7 512 GB (512110190592 bytes) Firmware: 3L2QEXA7 Serial#: S3TNNE0K119126 System: OS 1: Ubuntu 18.04.5 LTS Kernel: 4.15.0-122-generic #124-Ubuntu SMP Thu Oct 15 13:03:05 UTC 2020 x86_64 OS 2: Windows 7 (on a separate partition on same disk, dualbooted with grub). Actions taken: Successfully checked the partitions for errors by running "Check partition" and "Repair partition" in Disks utility in Ubuntu, running from a bootable USB. Starting in "recovery mode" yields an error (among other suspicious behavior): sd 0:0:0:0: Attached scsi generic sg0 type 0 sd 0:0:0:0: [sda] Attached SCSI removable Disk input: TPPS/2 IBM TrackPoint as /devices/platform/18042/serio1/serio2/input/input nvme nvme0: controller is down; will reset: CSTS=0x, PCI_STATUS=0x10 nvme :40:00.0: enabling device ( -> 0002) nvme nvme0: Removing after probe failure status: -19 nvme0n1: detected capacity change from 512110190592 to 0 print_req_error: I/O error, dev nvme0n1, sector 1000215040 nvme nvme0: failed to set APST feature (-19) Waiting for suspend/resume device ... Begin: Running /scripts/local-block No devices listed in conf file were found. No devices listed in conf file were found. [repeats] Without nvme_core.default_ps_max_latency_us set: writing fails between cca. 57 - 70, on battery. With nvme_core.default_ps_max_latency_us=5500: FIXES THE PROBLEM. With nvme_core.default_ps_max_latency_us=200: FIXES THE PROBLEM. With nvme_core.default_ps_max_latency_us=0: FIXES THE PROBLEM. Previous behavior on same machine: Same OS, with a previous Kernel has been running perfectly fine for the last year, "on high revs" (it's a development machine). Often running on battery alone. sleep and wakeup without issues. It is running Windows 7 (dual booted) without issues. Misc info: To test different settings, did 'sudo nano /etc/default/grub' with each of these settings: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" # GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=5500" # GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=200" # GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=0" followed by 'sudo update-grub' and reboot. Related bugs (links): https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184
[Kernel-packages] [Bug 1887490] Re: [FFe/SRU] Add/Backport EPYC-v3 and EPYC-Rome CPU model
It seems one of the patches also introduced a regression: * lp-1887490-cpu_map-Add-missing-AMD-SVM-features.patch adds various SVM-related flags. Specifically npt and nrip-save are now expected to be present by default as shown in the updated testdata. This however breaks migration from instances using EPYC or EPYC-IBPB CPU models started with libvirt versions prior to this one because the instance on the target host has these extra flags -- You 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: [FFe/SRU] Add/Backport EPYC-v3 and EPYC-Rome CPU model Status in libvirt package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in qemu package in Ubuntu: Fix Released Status in libvirt source package in Focal: Fix Released Status in linux source package in Focal: Fix Released Status in qemu source package in Focal: Fix Released Bug description: [Impact] * CPU definitions are added to libvirt as these CPUs are known and added to qemu for execution. And due to that over time some are considered 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 three upstream fixes that just add definitions (no control flow changes) [Test Case] * Check if it has an EPYC-Rome entry in /usr/share/libvirt/cpu_map/index.xml and the file included there exists. * Define a guest like: EPYC-Rome You can only "really" start this on a system with the matching HW. But even on others it will change from: error: internal error: Unknown CPU model EPYC-Rome to being unable to start for some features missing. * libvirt probes a system if a named cpu can be used, after the fix this should include EPYC-Rome $ virsh domcapabilities | grep EPYC EPYC-IBPB EPYC [Regression Potential] * Usually these type additions are safe unless they add control flow changes (e.g. to handle yet unknown types of registers or such) but that isn't the case here. A regression if any is to be expected on systems that are close to the newly added type(s). Those will after the update be detected as such if e.g. host-model is used. If then running on a mixed cluster of updated/non-updated systems migrations will only work if the target is updated as well. [Other Info] * This is the first build since glibc 2.32 arrived in groovy, hence we need to be careful of the fix done for bug 1892826. It has to be checked if the linking is fine after the rebuild. The workload still works in groovy despite 2.32 being present (I'd ahve expected it doesn't), so we will keep the revert as-is for now. To be sure that adds two tests that shall be done: - check the linking to point to libtirpc instead of glibc $ eu-readelf -a /usr/lib/libvirt/libvirt_lxc | grep xdr_uint64 | grep GLOBAL Was pointing to glibc, does it still and if so does it work (see below)? - run the autopkgtest cases as the LXC tests would trigger an issue if there is one ## 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
[Kernel-packages] [Bug 1902093] Re: Introduce the new NVIDIA 455 series
@Leon: that can be added in the next SRU. We can update those details without having to respin the kernel. ** Tags removed: verification-needed verification-needed-bionic verification-needed-focal verification-needed-groovy ** Tags added: verification-done verification-done-bionic verification-done-focal verification-done-groovy -- 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/1902093 Title: Introduce the new NVIDIA 455 series Status in linux package in Ubuntu: Confirmed Status in linux-restricted-modules package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-455 package in Ubuntu: In Progress Status in linux source package in Bionic: Confirmed Status in linux-restricted-modules source package in Bionic: Confirmed Status in nvidia-graphics-drivers-455 source package in Bionic: Fix Committed Status in linux source package in Focal: Confirmed Status in linux-restricted-modules source package in Focal: Confirmed Status in nvidia-graphics-drivers-455 source package in Focal: Fix Committed Status in linux source package in Groovy: Confirmed Status in linux-restricted-modules source package in Groovy: Confirmed Status in nvidia-graphics-drivers-455 source package in Groovy: Fix Committed Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] * New upstream release: - Added support for the following GPUs: GeForce RTX 3070 - Added support for using an NVIDIA-driven display as a PRIME Display Offload sink with a PRIME Display Offload source driven by the xf86-video-intel driver. - Fixed a bug in a Vulkan barrier optimization that allowed some back-to-back copies to run unordered. - Fixed a performance regression in the NVIDIA X driver which affected some X11 RENDER extension use cases. - Added AMD Secure Memory Encryption compatibility. * debian/templates/control.in: - Set support level to NFB instead of Beta. - Add support for CUDA 11. Note: this will be the initial release for Bionic and Focal. Changelog entries for the linux-restricted-modules: UBUNTU: [Packaging] NVIDIA -- provide the nvidia-prebuilt-kernel virtual package Make all the NVIDIA drivers, except for 390, provide the nvidia-prebuilt-kernel virtual package. This allows adding a generic dependency on the signed modules. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902093/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1901922] Re: [SRU][Lenovo ThinkPad T14 Gen 1] No sound output device on startup
** Changed in: alsa-ucm-conf (Ubuntu Hirsute) Status: In Progress => Fix Committed ** Changed in: alsa-ucm-conf (Ubuntu Groovy) Status: In Progress => Fix Committed ** Changed in: alsa-ucm-conf (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1901922 Title: [SRU][Lenovo ThinkPad T14 Gen 1] No sound output device on startup Status in PulseAudio: Unknown Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-ucm-conf package in Ubuntu: Fix Committed Status in alsa-lib source package in Focal: Fix Committed Status in alsa-ucm-conf source package in Focal: Fix Committed Status in alsa-lib source package in Groovy: Fix Committed Status in alsa-ucm-conf source package in Groovy: Fix Committed Status in alsa-lib source package in Hirsute: Fix Committed Status in alsa-ucm-conf source package in Hirsute: Fix Committed Bug description: [Impact] On the machines with AMD Ryzen acp audio design, the audio can't work anymore after upgrading the libasound2 to ubuntu3(groovy)/ubuntu2.1( focal), this is a regression on libasound2 for those machines. the AMD Ryzen acp audio card needs to load ucm to work with pulseaudio, but this audio card doesn't have an independant ucm for it, it needs to link to an existing HDA-Intel ucm, the check_empty_configuration() needs to cover the situation that Linked is true, otherwise it will fail to load the ucm for the audio card. Even the audio card could load the ucm, the output is muted and the init output volume is too low if freshly install the OS on these machines. [Fix] Backport 1 alsa-lib patch to fix the failure of loading ucm on AMD Ryzen acp audio machines. Backport 4 alsa-ucm-conf patches to fix init mute and init output volume problem. [Test Case] Install the updated libasuond2, rm ~/.config/pulse/*; sudo rm -rf /var/lib/alsa/*; sudo sh -c 'echo b > /proc/sysrq-trigger' and run pacmd list-cards, we could see the pulseaudio load the ucm successfully and we could see the sound card is generated and all output and input devices are listed under sound card, but the init output is muted and the volume is very low if we manually unumte it. Now install the updated alsa-ucm-conf, rm ~/.config/pulse/*; sudo rm -rf /var/lib/alsa/*; sudo sh -c 'echo b > /proc/sysrq-trigger', the output is not muted anymore and the output volume is OK to most users. [Regression Risk] This could make the machines with sof audio driver fail to load ucm , then all audio function can't work as before, like the speaker can't output sound or the internal mic can't be found or can't record sound. But this possibility is very low, I tested this SRU on some machines with or without sof audio driver, all worked as well as before. After logging in, only a dummy device is available for audio playback (resulting in no audible playback). When running "pactl load-module module-detect" the sound card shows up, and playback works as expected. If pulseaudio is restarted with "pulseaudio -k" the playback device disappears again. Running the above command get things working again. If I change the following section in /etc/pulse/default.pa from: ### Automatically load driver modules depending on the hardware available .ifexists module-udev-detect.so load-module module-udev-detect .else ### Use the static hardware detection module (for systems that lack udev support) load-module module-detect .endif To: ### Automatically load driver modules depending on the hardware available #.ifexists module-udev-detect.so #load-module module-udev-detect #.else ### Use the static hardware detection module (for systems that lack udev support) load-module module-detect #.endif Things start working as they should after running "pulseaudio -k". ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Oct 28 17:21:02 2020 InstallationDate: Installed on 2020-10-23 (4 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2020 dmi.bios.release: 1.9 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET40W(1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UDCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.9 dmi.modalias:
[Kernel-packages] [Bug 1903682] Re: [UBUNTU 20.10] NULL pointer dereference when configuring multi-function with devfn != 0 before devfn == 0
Ok, I can see that the commit got accepted with 5.10-rc3, hence it will land in
hirsute.
And because the patch was tagged as stable for 5.8, it will land in groovy's
kernel 5.8 (I'll check the 'Groovy update: v5.8.x upstream stable release'
kernel team tracking tickets and will align the status).
Remaining todo is to cherry-pick and manually SRU to focal/5.4.
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Hirsute)
Importance: Undecided
Assignee: Frank Heimes (fheimes)
Status: New
** Also affects: linux (Ubuntu Groovy)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Hirsute)
Assignee: Frank Heimes (fheimes) => (unassigned)
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) => Frank Heimes (fheimes)
** Changed in: linux (Ubuntu Hirsute)
Status: New => Fix Committed
** Changed in: linux (Ubuntu Groovy)
Status: New => Triaged
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1903682
Title:
[UBUNTU 20.10] NULL pointer dereference when configuring multi-
function with devfn != 0 before devfn == 0
Status in Ubuntu on IBM z Systems:
Triaged
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Focal:
New
Status in linux source package in Groovy:
Triaged
Status in linux source package in Hirsute:
Fix Committed
Bug description:
Background:
When handling multifunction devices in zPCI we take the
UID of the PCI function with function number 0
(that always exists according to the PCI spec)
as domain number.
Therefore when hot plugging functions with function
number larger than 0 before function 0, we need
to hold these in standby before creating the
domain and bus.
This has been tested during feature development
using a patched QEMU and with DPM but never in Classic
Mode.
Reproduction:
This issue was introduced with the Topology aware PCI
Enumeration code so test with a Linux supporting
that feature. E.g. Upstream, Devel Driver etc.
On a Classic Mode machine with a multi-function device,
hot plug ("Reassign I/O Path") only the FID of the
second port to the LPAR.
Symptom:
After this any additional hotplug and even just
deconfiguring a PCI device will hang. A hotplug
makes the entire Linux instance unresponsive.
Analysis:
The problem occurs in Classic Mode but not with
previous testing as the LPAR hypervisor does
hot plug/Reassign I/O Path as a two step process:
1. zPCI event with PEC 0x0302 to plug the zPCI function in Standby
2. zPCI event with PEC 0x0301 to configure the zPCI function
For the first event we create the zdev in clp_add_pci_device()
in Standby which is all fine so far.
The problem then occurs in step 2 as we then find
the existing zdev and try to configure it.
This however does not work as the PCI bus
is not yet created (as we still don't know the UID of
function 0 that will become its domain).
The bus pointer zdev->zbus->bus pointer is thus still
NULL but will be accessed by common code which
inevitably results in disaster including
the above mentioned hang and (possibly) the below
RCU stall:
[ 689.724703] rcu: INFO: rcu_sched self-detected stall on CPU
[ 689.724712] rcu: 16-: (42004 ticks this GP)
idle=6ee/1/0x4002 softirq=1234/1234 fqs=14001
[ 689.724742] (t=42006 jiffies g=89 q=3770)
[ 689.724743] Task dump for CPU 16:
[ 689.724745] task:kmcheck state:R running task stack:0
pid: 205 ppid: 2 flags:0x0004
[ 689.724747] Call Trace:
[ 689.724757] [<000ccde0b5c4>] show_stack+0x8c/0xd8
[ 689.724762] [<000ccd0dabc4>] sched_show_task.part.0+0xe4/0x110
[ 689.724764] [<000ccde0ea5e>] rcu_dump_cpu_stacks+0xde/0x120
[ 689.724767] [<000ccd1465c6>] print_cpu_stall+0x266/0x330
[ 689.724768] [<000ccd14a428>] rcu_sched_clock_irq+0x618/0x670
[ 689.724771] [<000ccd15cd7a>] update_process_times+0xba/0xf0
[ 689.724775] [<000ccd1766fa>] tick_sched_timer+0x9a/0x220
[ 689.724777] [<000ccd15d962>] __hrtimer_run_queues+0x182/0x3a0
[ 689.724779] [<000ccd1602f8>] hrtimer_interrupt+0x138/0x450
[ 689.724782] [<000ccd0451c0>] do_IRQ+0x90/0xa0
[ 689.724784] [<000ccde2be96>] ext_int_handler+0x17e/0x184
[ 689.724790] [<000ccd9f373e>] pci_get_slot+0x5e/0xa0
[ 689.724794] [<000ccd9dc182>] pci_scan_single_device+0x32/0x2a0
[ 689.724797] [<000ccd0868f2>] __zpci_event_availability+0x192/0x360
[ 689.724800] [<000ccdd40c16>] chsc_process_crw+0x2e6/0x300
[ 689.724802] [<000ccdd4b088>] crw_collect_info+0x2b8/0x320
[ 689.724804] [<000ccd0caf3a>] kthread+0x14a/0x170
[ 689.724805] [<000ccde2b814>] ret_from_fork+0x24/0x2c
The fix is very
[Kernel-packages] [Bug 1901922] Re: [SRU][Lenovo ThinkPad T14 Gen 1] No sound output device on startup
** Changed in: alsa-ucm-conf (Ubuntu Hirsute) Status: Fix Released => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1901922 Title: [SRU][Lenovo ThinkPad T14 Gen 1] No sound output device on startup Status in PulseAudio: Unknown Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-ucm-conf package in Ubuntu: Fix Committed Status in alsa-lib source package in Focal: Fix Committed Status in alsa-ucm-conf source package in Focal: Fix Committed Status in alsa-lib source package in Groovy: Fix Committed Status in alsa-ucm-conf source package in Groovy: Fix Committed Status in alsa-lib source package in Hirsute: Fix Committed Status in alsa-ucm-conf source package in Hirsute: Fix Committed Bug description: [Impact] On the machines with AMD Ryzen acp audio design, the audio can't work anymore after upgrading the libasound2 to ubuntu3(groovy)/ubuntu2.1( focal), this is a regression on libasound2 for those machines. the AMD Ryzen acp audio card needs to load ucm to work with pulseaudio, but this audio card doesn't have an independant ucm for it, it needs to link to an existing HDA-Intel ucm, the check_empty_configuration() needs to cover the situation that Linked is true, otherwise it will fail to load the ucm for the audio card. Even the audio card could load the ucm, the output is muted and the init output volume is too low if freshly install the OS on these machines. [Fix] Backport 1 alsa-lib patch to fix the failure of loading ucm on AMD Ryzen acp audio machines. Backport 4 alsa-ucm-conf patches to fix init mute and init output volume problem. [Test Case] Install the updated libasuond2, rm ~/.config/pulse/*; sudo rm -rf /var/lib/alsa/*; sudo sh -c 'echo b > /proc/sysrq-trigger' and run pacmd list-cards, we could see the pulseaudio load the ucm successfully and we could see the sound card is generated and all output and input devices are listed under sound card, but the init output is muted and the volume is very low if we manually unumte it. Now install the updated alsa-ucm-conf, rm ~/.config/pulse/*; sudo rm -rf /var/lib/alsa/*; sudo sh -c 'echo b > /proc/sysrq-trigger', the output is not muted anymore and the output volume is OK to most users. [Regression Risk] This could make the machines with sof audio driver fail to load ucm , then all audio function can't work as before, like the speaker can't output sound or the internal mic can't be found or can't record sound. But this possibility is very low, I tested this SRU on some machines with or without sof audio driver, all worked as well as before. After logging in, only a dummy device is available for audio playback (resulting in no audible playback). When running "pactl load-module module-detect" the sound card shows up, and playback works as expected. If pulseaudio is restarted with "pulseaudio -k" the playback device disappears again. Running the above command get things working again. If I change the following section in /etc/pulse/default.pa from: ### Automatically load driver modules depending on the hardware available .ifexists module-udev-detect.so load-module module-udev-detect .else ### Use the static hardware detection module (for systems that lack udev support) load-module module-detect .endif To: ### Automatically load driver modules depending on the hardware available #.ifexists module-udev-detect.so #load-module module-udev-detect #.else ### Use the static hardware detection module (for systems that lack udev support) load-module module-detect #.endif Things start working as they should after running "pulseaudio -k". ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Oct 28 17:21:02 2020 InstallationDate: Installed on 2020-10-23 (4 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2020 dmi.bios.release: 1.9 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET40W(1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UDCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnLENOVO:bvrR1BET40W(1.09):bd08/07/2020:br1.9:efr1.9:svnLENOVO:pn20UDCTO1WW:pvrThinkPadT14Gen1:rvnLENOVO:rn20UDCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad
[Kernel-packages] [Bug 1901922] Re: [SRU][Lenovo ThinkPad T14 Gen 1] No sound output device on startup
Sorry on my part, the last change to the status was a mistake and was not intended. Unfortunately, I cannot reverse it myself -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1901922 Title: [SRU][Lenovo ThinkPad T14 Gen 1] No sound output device on startup Status in PulseAudio: Unknown Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-ucm-conf package in Ubuntu: Fix Committed Status in alsa-lib source package in Focal: Fix Committed Status in alsa-ucm-conf source package in Focal: Fix Committed Status in alsa-lib source package in Groovy: Fix Committed Status in alsa-ucm-conf source package in Groovy: Fix Committed Status in alsa-lib source package in Hirsute: Fix Committed Status in alsa-ucm-conf source package in Hirsute: Fix Committed Bug description: [Impact] On the machines with AMD Ryzen acp audio design, the audio can't work anymore after upgrading the libasound2 to ubuntu3(groovy)/ubuntu2.1( focal), this is a regression on libasound2 for those machines. the AMD Ryzen acp audio card needs to load ucm to work with pulseaudio, but this audio card doesn't have an independant ucm for it, it needs to link to an existing HDA-Intel ucm, the check_empty_configuration() needs to cover the situation that Linked is true, otherwise it will fail to load the ucm for the audio card. Even the audio card could load the ucm, the output is muted and the init output volume is too low if freshly install the OS on these machines. [Fix] Backport 1 alsa-lib patch to fix the failure of loading ucm on AMD Ryzen acp audio machines. Backport 4 alsa-ucm-conf patches to fix init mute and init output volume problem. [Test Case] Install the updated libasuond2, rm ~/.config/pulse/*; sudo rm -rf /var/lib/alsa/*; sudo sh -c 'echo b > /proc/sysrq-trigger' and run pacmd list-cards, we could see the pulseaudio load the ucm successfully and we could see the sound card is generated and all output and input devices are listed under sound card, but the init output is muted and the volume is very low if we manually unumte it. Now install the updated alsa-ucm-conf, rm ~/.config/pulse/*; sudo rm -rf /var/lib/alsa/*; sudo sh -c 'echo b > /proc/sysrq-trigger', the output is not muted anymore and the output volume is OK to most users. [Regression Risk] This could make the machines with sof audio driver fail to load ucm , then all audio function can't work as before, like the speaker can't output sound or the internal mic can't be found or can't record sound. But this possibility is very low, I tested this SRU on some machines with or without sof audio driver, all worked as well as before. After logging in, only a dummy device is available for audio playback (resulting in no audible playback). When running "pactl load-module module-detect" the sound card shows up, and playback works as expected. If pulseaudio is restarted with "pulseaudio -k" the playback device disappears again. Running the above command get things working again. If I change the following section in /etc/pulse/default.pa from: ### Automatically load driver modules depending on the hardware available .ifexists module-udev-detect.so load-module module-udev-detect .else ### Use the static hardware detection module (for systems that lack udev support) load-module module-detect .endif To: ### Automatically load driver modules depending on the hardware available #.ifexists module-udev-detect.so #load-module module-udev-detect #.else ### Use the static hardware detection module (for systems that lack udev support) load-module module-detect #.endif Things start working as they should after running "pulseaudio -k". ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Oct 28 17:21:02 2020 InstallationDate: Installed on 2020-10-23 (4 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2020 dmi.bios.release: 1.9 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET40W(1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UDCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.9 dmi.modalias:
Re: [Kernel-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
On Sun, Nov 08, 2020 at 01:14:48PM -, Mike Boruta wrote: >Definitely! The attached output was compiled from 5.4.0-52 with the >patch listed in 171. #171 should fix your touchpad. According to your shared gpio-config, that patch didn't take effect. So I guess you are still using the old pinctrl-amd module. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in Pop!_OS: New Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Status in linux package in Arch Linux: Fix Committed Status in linux package in Fedora: Confirmed Status in linux package in openSUSE: New Bug description: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 20:14:25 2020 InstallationDate: Installed on 2020-07-02 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN19WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05 dmi.modalias:
Re: [Kernel-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
On Sun, Nov 08, 2020 at 07:38:15PM -, Azizkhan wrote: >Hi all! >@Coiby Xu (coiby) >When your patch will be applied to mainline kernel? When we can just update >our kernels and do nothing to fix touchpad? I'm not sure when these patch(es) will be accepted and merged. It's up to the maintainers to accept the patch(es). If there is any update, I'll post the notification here. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in Pop!_OS: New Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Status in linux package in Arch Linux: Fix Committed Status in linux package in Fedora: Confirmed Status in linux package in openSUSE: New Bug description: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 20:14:25 2020 InstallationDate: Installed on 2020-07-02 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN19WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05 dmi.modalias:
[Kernel-packages] [Bug 1902093] Re: Introduce the new NVIDIA 455 series
The 10DE:1F9D and 10DE:2520 are not included in the modaliases of the nvidia-driver-455. -- 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/1902093 Title: Introduce the new NVIDIA 455 series Status in linux package in Ubuntu: Confirmed Status in linux-restricted-modules package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-455 package in Ubuntu: In Progress Status in linux source package in Bionic: Confirmed Status in linux-restricted-modules source package in Bionic: Confirmed Status in nvidia-graphics-drivers-455 source package in Bionic: Fix Committed Status in linux source package in Focal: Confirmed Status in linux-restricted-modules source package in Focal: Confirmed Status in nvidia-graphics-drivers-455 source package in Focal: Fix Committed Status in linux source package in Groovy: Confirmed Status in linux-restricted-modules source package in Groovy: Confirmed Status in nvidia-graphics-drivers-455 source package in Groovy: Fix Committed Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] * New upstream release: - Added support for the following GPUs: GeForce RTX 3070 - Added support for using an NVIDIA-driven display as a PRIME Display Offload sink with a PRIME Display Offload source driven by the xf86-video-intel driver. - Fixed a bug in a Vulkan barrier optimization that allowed some back-to-back copies to run unordered. - Fixed a performance regression in the NVIDIA X driver which affected some X11 RENDER extension use cases. - Added AMD Secure Memory Encryption compatibility. * debian/templates/control.in: - Set support level to NFB instead of Beta. - Add support for CUDA 11. Note: this will be the initial release for Bionic and Focal. Changelog entries for the linux-restricted-modules: UBUNTU: [Packaging] NVIDIA -- provide the nvidia-prebuilt-kernel virtual package Make all the NVIDIA drivers, except for 390, provide the nvidia-prebuilt-kernel virtual package. This allows adding a generic dependency on the signed modules. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902093/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861009] Re: Asus Zenbook Flip 15 ux563fd no sound
Thanks a lot! https://www.piramalaranya.com/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1861009 Title: Asus Zenbook Flip 15 ux563fd no sound Status in linux package in Ubuntu: Confirmed Bug description: Bought a new laptop for a couple weeks ago and want to have a dual boot with W10 and Linux like my older one. First, I installed Ubuntu 18.04 and tried to make sound working via the speakers. I tried alsamixer, made sure everything was on OO, reinstalled both alsamixer and pulseaudio couple times, checked permissions on the config of pulseaudio and more what could fix it in regular terms including installing and replacing kernels older and new ones. As a last option, I installed version 19.10 from Ubuntu as someone mentioned that the higher version could fix it because of the different supported packages but is not resolving it. Nothing of the above mentioned things where fixing it, but I still see some movement at streaming bar in the sound option menu when I'm playing some music. I hope there is a workaround for this issue, I just found the whole Zenbook laptop line that has this problem so I really hope for a solution to this. Version - kernel: Ubuntu 5.3.0-26.28-generic 5.3.13 lspci -vnvn 00:00.0 Host bridge [0600]: Intel Corporation Device [8086:9b61] (rev 0c) Subsystem: ASUSTeK Computer Inc. Device [1043:1b31] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) DeviceName: VGA Subsystem: ASUSTeK Computer Inc. Device [1043:1b31] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- TransPend- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, OBFF Not Supported AtomicOpsCap: 32bit- 64bit- 128bitCAS- DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled AtomicOpsCtl: ReqEn- Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee00018 Data: Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [100 v1] Process Address Space ID (PASID) PASIDCap: Exec- Priv-, Max PASID Width: 14 PASIDCtl: Enable- Exec- Priv- Capabilities: [200 v1] Address Translation Service (ATS) ATSCap: Invalidate Queue Depth: 00 ATSCtl: Enable-, Smallest Translation Unit: 00 Capabilities: [300 v1] Page Request Interface (PRI) PRICtl: Enable- Reset- PRISta: RF- UPRGI- Stopped+ Page Request Capacity: 8000, Page Request Allocation: Kernel driver in use: i915 Kernel modules: i915 00:04.0 Signal processing controller [1180]: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [8086:1903] (rev 0c) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [1043:1b31] Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: proc_thermal Kernel modules: processor_thermal_device 00:08.0 System peripheral [0880]: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th Gen Core Processor Gaussian Mixture Model [8086:1911] Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th Gen Core Processor Gaussian Mixture Model [1043:1b31] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- Kernel driver in use: intel_ish_ipc Kernel modules: intel_ish_ipc 00:14.0 USB controller
[Kernel-packages] [Bug 1901922] Re: [SRU][Lenovo ThinkPad T14 Gen 1] No sound output device on startup
> Please let me know if need a debdiff for H, I will download the daily built image and find a machine to install it and generate the debdiff. No it's fine, I've changed the 20.10 version to ubuntu3.1 and uploaded the debdiff from the bug to hirsute (no need to install hirsute to be able to generate the debdiff btw, especially not that earlier in the cycle, it can be built fine on 20.10) I've uploaded alsa-lib to F, G, H now, ucm is next in the queue ** Changed in: alsa-lib (Ubuntu Focal) Status: In Progress => Fix Committed ** Changed in: alsa-lib (Ubuntu Groovy) Status: In Progress => Fix Committed ** Changed in: alsa-lib (Ubuntu Hirsute) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1901922 Title: [SRU][Lenovo ThinkPad T14 Gen 1] No sound output device on startup Status in PulseAudio: Unknown Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-ucm-conf package in Ubuntu: In Progress Status in alsa-lib source package in Focal: Fix Committed Status in alsa-ucm-conf source package in Focal: In Progress Status in alsa-lib source package in Groovy: Fix Committed Status in alsa-ucm-conf source package in Groovy: In Progress Status in alsa-lib source package in Hirsute: Fix Committed Status in alsa-ucm-conf source package in Hirsute: In Progress Bug description: [Impact] On the machines with AMD Ryzen acp audio design, the audio can't work anymore after upgrading the libasound2 to ubuntu3(groovy)/ubuntu2.1( focal), this is a regression on libasound2 for those machines. the AMD Ryzen acp audio card needs to load ucm to work with pulseaudio, but this audio card doesn't have an independant ucm for it, it needs to link to an existing HDA-Intel ucm, the check_empty_configuration() needs to cover the situation that Linked is true, otherwise it will fail to load the ucm for the audio card. Even the audio card could load the ucm, the output is muted and the init output volume is too low if freshly install the OS on these machines. [Fix] Backport 1 alsa-lib patch to fix the failure of loading ucm on AMD Ryzen acp audio machines. Backport 4 alsa-ucm-conf patches to fix init mute and init output volume problem. [Test Case] Install the updated libasuond2, rm ~/.config/pulse/*; sudo rm -rf /var/lib/alsa/*; sudo sh -c 'echo b > /proc/sysrq-trigger' and run pacmd list-cards, we could see the pulseaudio load the ucm successfully and we could see the sound card is generated and all output and input devices are listed under sound card, but the init output is muted and the volume is very low if we manually unumte it. Now install the updated alsa-ucm-conf, rm ~/.config/pulse/*; sudo rm -rf /var/lib/alsa/*; sudo sh -c 'echo b > /proc/sysrq-trigger', the output is not muted anymore and the output volume is OK to most users. [Regression Risk] This could make the machines with sof audio driver fail to load ucm , then all audio function can't work as before, like the speaker can't output sound or the internal mic can't be found or can't record sound. But this possibility is very low, I tested this SRU on some machines with or without sof audio driver, all worked as well as before. After logging in, only a dummy device is available for audio playback (resulting in no audible playback). When running "pactl load-module module-detect" the sound card shows up, and playback works as expected. If pulseaudio is restarted with "pulseaudio -k" the playback device disappears again. Running the above command get things working again. If I change the following section in /etc/pulse/default.pa from: ### Automatically load driver modules depending on the hardware available .ifexists module-udev-detect.so load-module module-udev-detect .else ### Use the static hardware detection module (for systems that lack udev support) load-module module-detect .endif To: ### Automatically load driver modules depending on the hardware available #.ifexists module-udev-detect.so #load-module module-udev-detect #.else ### Use the static hardware detection module (for systems that lack udev support) load-module module-detect #.endif Things start working as they should after running "pulseaudio -k". ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Oct 28 17:21:02 2020 InstallationDate: Installed on 2020-10-23 (4 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh
[Kernel-packages] [Bug 1215411] Re: libcpupower.so is not installed from linux-tools
Yeah as Brian I came by this a while ago (and now again). Bug 1891336 is about the same. This one here is older and closer to a conclusion. So I'll make the other one a dup, but added bug-tasks and an update-excuse tag to show up in excuses. ** Also affects: gkrellm2-cpufreq (Ubuntu) Importance: Undecided Status: New ** Also affects: cpufreqd (Ubuntu) Importance: Undecided Status: New ** No longer affects: cpufreqd (Ubuntu Zesty) ** No longer affects: cpufreqd (Ubuntu Eoan) ** No longer affects: gkrellm2-cpufreq (Ubuntu Zesty) ** No longer affects: gkrellm2-cpufreq (Ubuntu Eoan) ** Changed in: cpufreqd (Ubuntu) Status: New => Confirmed ** Changed in: gkrellm2-cpufreq (Ubuntu) Status: New => Confirmed ** Tags added: update-excuses ** Tags removed: update-excuses ** Tags added: update-excuse -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1215411 Title: libcpupower.so is not installed from linux-tools Status in cpufreqd package in Ubuntu: Confirmed Status in gkrellm2-cpufreq package in Ubuntu: Confirmed Status in linux package in Ubuntu: In Progress Status in linux source package in Zesty: Invalid Status in linux source package in Eoan: Won't Fix Bug description: The patch for bug 1158668 installs cpupower_$(abi_version) command- line tool as well as libcpupower.so.$(abi_version). This isn't particularly suitable for projects that previously used libcpufreq and intend to migrate to libcpupower, because the libcpupower.so symlink is no longer installed. The command-line tools can also have symlinks (e.g. cpupower -> cpupower_$(abi_version)). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cpufreqd/+bug/1215411/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1902093] Re: Introduce the new NVIDIA 455 series
** Tags added: block-proposed-bionic block-proposed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1902093 Title: Introduce the new NVIDIA 455 series Status in linux package in Ubuntu: Confirmed Status in linux-restricted-modules package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-455 package in Ubuntu: In Progress Status in linux source package in Bionic: Confirmed Status in linux-restricted-modules source package in Bionic: Confirmed Status in nvidia-graphics-drivers-455 source package in Bionic: Fix Committed Status in linux source package in Focal: Confirmed Status in linux-restricted-modules source package in Focal: Confirmed Status in nvidia-graphics-drivers-455 source package in Focal: Fix Committed Status in linux source package in Groovy: Confirmed Status in linux-restricted-modules source package in Groovy: Confirmed Status in nvidia-graphics-drivers-455 source package in Groovy: Fix Committed Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] * New upstream release: - Added support for the following GPUs: GeForce RTX 3070 - Added support for using an NVIDIA-driven display as a PRIME Display Offload sink with a PRIME Display Offload source driven by the xf86-video-intel driver. - Fixed a bug in a Vulkan barrier optimization that allowed some back-to-back copies to run unordered. - Fixed a performance regression in the NVIDIA X driver which affected some X11 RENDER extension use cases. - Added AMD Secure Memory Encryption compatibility. * debian/templates/control.in: - Set support level to NFB instead of Beta. - Add support for CUDA 11. Note: this will be the initial release for Bionic and Focal. Changelog entries for the linux-restricted-modules: UBUNTU: [Packaging] NVIDIA -- provide the nvidia-prebuilt-kernel virtual package Make all the NVIDIA drivers, except for 390, provide the nvidia-prebuilt-kernel virtual package. This allows adding a generic dependency on the signed modules. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902093/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903682] [NEW] [UBUNTU 20.10] NULL pointer dereference when configuring multi-function with devfn != 0 before devfn == 0
You have been subscribed to a public bug:
Background:
When handling multifunction devices in zPCI we take the
UID of the PCI function with function number 0
(that always exists according to the PCI spec)
as domain number.
Therefore when hot plugging functions with function
number larger than 0 before function 0, we need
to hold these in standby before creating the
domain and bus.
This has been tested during feature development
using a patched QEMU and with DPM but never in Classic
Mode.
Reproduction:
This issue was introduced with the Topology aware PCI
Enumeration code so test with a Linux supporting
that feature. E.g. Upstream, Devel Driver etc.
On a Classic Mode machine with a multi-function device,
hot plug ("Reassign I/O Path") only the FID of the
second port to the LPAR.
Symptom:
After this any additional hotplug and even just
deconfiguring a PCI device will hang. A hotplug
makes the entire Linux instance unresponsive.
Analysis:
The problem occurs in Classic Mode but not with
previous testing as the LPAR hypervisor does
hot plug/Reassign I/O Path as a two step process:
1. zPCI event with PEC 0x0302 to plug the zPCI function in Standby
2. zPCI event with PEC 0x0301 to configure the zPCI function
For the first event we create the zdev in clp_add_pci_device()
in Standby which is all fine so far.
The problem then occurs in step 2 as we then find
the existing zdev and try to configure it.
This however does not work as the PCI bus
is not yet created (as we still don't know the UID of
function 0 that will become its domain).
The bus pointer zdev->zbus->bus pointer is thus still
NULL but will be accessed by common code which
inevitably results in disaster including
the above mentioned hang and (possibly) the below
RCU stall:
[ 689.724703] rcu: INFO: rcu_sched self-detected stall on CPU
[ 689.724712] rcu: 16-: (42004 ticks this GP)
idle=6ee/1/0x4002 softirq=1234/1234 fqs=14001
[ 689.724742] (t=42006 jiffies g=89 q=3770)
[ 689.724743] Task dump for CPU 16:
[ 689.724745] task:kmcheck state:R running task stack:0 pid:
205 ppid: 2 flags:0x0004
[ 689.724747] Call Trace:
[ 689.724757] [<000ccde0b5c4>] show_stack+0x8c/0xd8
[ 689.724762] [<000ccd0dabc4>] sched_show_task.part.0+0xe4/0x110
[ 689.724764] [<000ccde0ea5e>] rcu_dump_cpu_stacks+0xde/0x120
[ 689.724767] [<000ccd1465c6>] print_cpu_stall+0x266/0x330
[ 689.724768] [<000ccd14a428>] rcu_sched_clock_irq+0x618/0x670
[ 689.724771] [<000ccd15cd7a>] update_process_times+0xba/0xf0
[ 689.724775] [<000ccd1766fa>] tick_sched_timer+0x9a/0x220
[ 689.724777] [<000ccd15d962>] __hrtimer_run_queues+0x182/0x3a0
[ 689.724779] [<000ccd1602f8>] hrtimer_interrupt+0x138/0x450
[ 689.724782] [<000ccd0451c0>] do_IRQ+0x90/0xa0
[ 689.724784] [<000ccde2be96>] ext_int_handler+0x17e/0x184
[ 689.724790] [<000ccd9f373e>] pci_get_slot+0x5e/0xa0
[ 689.724794] [<000ccd9dc182>] pci_scan_single_device+0x32/0x2a0
[ 689.724797] [<000ccd0868f2>] __zpci_event_availability+0x192/0x360
[ 689.724800] [<000ccdd40c16>] chsc_process_crw+0x2e6/0x300
[ 689.724802] [<000ccdd4b088>] crw_collect_info+0x2b8/0x320
[ 689.724804] [<000ccd0caf3a>] kthread+0x14a/0x170
[ 689.724805] [<000ccde2b814>] ret_from_fork+0x24/0x2c
The fix is very simple, we check zdev->zbus->bus
for being NULL and in that case bail from the
case 0x0301 before calling the PCI common code
pci_scan_single_device() with the NULL pointer.
The only subtlety is that we still need to
do the zpci_enable_device() because the
code in arch/s390/pci/pci_bus.c assumes
that it can immediately do a scan of
all devfn != 0 PCI functions once
PCI function 0 is found.
It thereby mimics what happens
when we only find the FID for a function with
devfn != 0 in the CLP List PCI Functions.
This is implemented in the following upstream
commit:
0b2ca2c7d0c9e2731d01b6c862375d44a7e13923 s390/pci: fix hot-plug of PCI
function missing bus
It is included in v5.10-rc3 and has been tagged for
stable > v5.8 i.e. all upstream versions with
the PCI enumeration changes.
Also it carries the appropriate Fixes tag.
I have verified that it cherry-picks cleanly
on current focal master-next and expect
it to cleanly cherry-pick on newer Ubuntu
Kernels too.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Skipper Bug Screeners (skipper-screen-team)
Status: New
** Tags: architecture-s39064 bugnameltc-189163 severity-medium
targetmilestone-inin2010
--
[UBUNTU 20.10] NULL pointer dereference when configuring multi-function with
devfn != 0 before devfn == 0
https://bugs.launchpad.net/bugs/1903682
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
Re: [Kernel-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
On Sun, Nov 08, 2020 at 04:33:43PM -, Baq Domalaq wrote: >Hi everyone! I have the same problem with my touchpad on Lenovo Ideapad >Gaming 3 15ARH05 under Pop!_OS. > >My touchpad device number is slightly different: >MSFT0001:00 06CB:CE2D > >I've applied a patch in comment #179 (I assumed that's the most fitting >solution for me) and it works now! Thank you people for trying to fix >this. > >Anyway the comments now are very long and confusing. And I'm not sure if >I used the best solution. So if anyone can point to something better, >let me know. > The touchpads on Legion-5 could be saved by either polling (#179) or interrupt (#171). I've submitted both patches upstream for these two methods. After getting reviewed by the kernel developer community, I will keep improving them until these patches get accepted by the maintainer. I would suggest you try #171 before the patches getting merged into the mainline kernel. If it doesn't work, you can send me your ACPI DSDT table. >Also let me know how to help with pushing this to official kernel. I've >posted an issue to Pop OS Github repo. I'll also add a comment about my >workarounds there. > You can send me your email address. I'll Cc you when submitting the patch(es). Then you can test the received patch and reply to the email with a Tested-by tag if the patch(es) works, Tested-by: Your_name >Have a nice day! > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in Pop!_OS: New Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Status in linux package in Arch Linux: Fix Committed Status in linux package in Fedora: Confirmed Status in linux package in openSUSE: New Bug description: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 20:14:25 2020 InstallationDate: Installed on 2020-07-02 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
[Kernel-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
The patch in #239 depends on this patch [1] which requires to build the whole kernel. For now, I would suggest adopting #189 to fix the touchpad for daily use. But if anyone want to test the patch so we can push it into the mainline kernel early, you can send me your email address and I'll Cc you when submitting next version. https://patchwork.ozlabs.org/project/linux- gpio/patch/20201109205332.19592-12-andriy.shevche...@linux.intel.com/. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in Pop!_OS: New Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Status in linux package in Arch Linux: Fix Committed Status in linux package in Fedora: Confirmed Status in linux package in openSUSE: New Bug description: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 20:14:25 2020 InstallationDate: Installed on 2020-07-02 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN19WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05 dmi.modalias:
[Kernel-packages] [Bug 1872984] Re: RTL8822BE [10ec:b822] network driver rtl_wifi crashes on boot in Focal Fossa 20.04 - 5.4.0-21-generic and mainline 5.7.0-050700rc1-generic
Hi, please test this kernel: https://people.canonical.com/~khfeng/aspm-l1-fix/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1872984 Title: RTL8822BE [10ec:b822] network driver rtl_wifi crashes on boot in Focal Fossa 20.04 - 5.4.0-21-generic and mainline 5.7.0-050700rc1-generic Status in linux package in Ubuntu: Incomplete Bug description: RTL8822BE crashes after rtw_pci starts on boot after kernel update to 5.4.0-21 (fails to read DBI register -- see attached dmesg). Issue is still present on latest mainline kernel version 5.7.0-050700rc1-generic . [ 10.627501] rtw_pci :3a:00.0: start vif 5c:ea:1d:b6:17:11 on port 0 [ 10.714544] [ cut here ] [ 10.714545] failed to read DBI register, addr=0x0719 [ 10.714577] WARNING: CPU: 0 PID: 939 at drivers/net/wireless/realtek/rtw88/pci.c:1156 rtw_dbi_read8.constprop.0+0xaa/0xc0 [rtwpci] [ 10.714577] Modules linked in: (see attached dmesg) [ 10.714614] CPU: 0 PID: 939 Comm: wpa_supplicant Not tainted 5.7.0-050700rc1-generic #202004122032 [ 10.714614] Hardware name: LENOVO 81CU/LNVNB161216, BIOS 7KCN22WW(V1.03) 01/23/2018 [ 10.714616] RIP: 0010:rtw_dbi_read8.constprop.0+0xaa/0xc0 [rtwpci] [ 10.714617] Code: 03 00 00 48 8b 40 50 e8 24 c3 4b e0 5b 41 5c 41 88 45 00 31 c0 41 5d 5d c3 be 19 07 00 00 48 c7 c7 70 73 94 c0 e8 bb de 75 df <0f> 0b b8 fb ff ff ff 5b 41 5c 41 5d 5d c3 0f 1f 84 00 00 00 00 00 [ 10.714618] RSP: 0018:b466007e7880 EFLAGS: 00010282 [ 10.714618] RAX: RBX: RCX: 0007 [ 10.714619] RDX: 0007 RSI: 0092 RDI: 933cc9e19c80 [ 10.714619] RBP: b466007e7898 R08: 03d2 R09: 0004 [ 10.714620] R10: R11: 0001 R12: 933cbdf31ea0 [ 10.714620] R13: b466007e78af R14: 933cbdf35bc8 R15: [ 10.714622] FS: 7fbcedc6efc0() GS:933cc9e0() knlGS: [ 10.714622] CS: 0010 DS: ES: CR0: 80050033 [ 10.714623] CR2: 563278766000 CR3: 0002be7a4002 CR4: 003606f0 [ 10.714623] Call Trace: [ 10.714627] rtw_pci_link_ps+0x4e/0x90 [rtwpci] [ 10.714630] ? _raw_spin_unlock_bh+0x1e/0x20 [ 10.714637] rtw_leave_ips+0x1f/0x80 [rtw88] [ 10.714640] rtw_ops_config+0xa3/0xe0 [rtw88] [ 10.714658] ieee80211_hw_config+0x95/0x390 [mac80211] [ 10.714669] ieee80211_recalc_idle+0x27/0x30 [mac80211] [ 10.714679] __ieee80211_start_scan+0x334/0x750 [mac80211] [ 10.714688] ieee80211_request_scan+0x30/0x50 [mac80211] [ 10.714699] ieee80211_scan+0x5c/0xa0 [mac80211] [ 10.714719] nl80211_trigger_scan+0x59a/0x6c0 [cfg80211] [ 10.714722] genl_rcv_msg+0x1a8/0x470 [ 10.714724] ? ep_poll_callback+0x2a0/0x2c0 [ 10.714725] ? genl_family_rcv_msg_attrs_parse+0x100/0x100 [ 10.714726] netlink_rcv_skb+0x50/0x120 [ 10.714728] genl_rcv+0x29/0x40 [ 10.714729] netlink_unicast+0x1a8/0x250 [ 10.714730] netlink_sendmsg+0x233/0x460 [ 10.714739] ? _copy_from_user+0x31/0x60 [ 10.714750] sock_sendmsg+0x65/0x70 [ 10.714751] sys_sendmsg+0x212/0x280 [ 10.714752] ? copy_msghdr_from_user+0x5c/0x90 [ 10.714755] ? __check_object_size+0x4d/0x150 [ 10.714756] ___sys_sendmsg+0x81/0xc0 [ 10.714757] ? __check_object_size+0x4d/0x150 [ 10.714759] ? unix_ioctl+0x99/0x180 [ 10.714760] ? sock_getsockopt+0x198/0xc04 [ 10.714761] ? sock_do_ioctl+0x47/0x140 [ 10.714763] ? __cgroup_bpf_run_filter_setsockopt+0xae/0x2c0 [ 10.714765] ? _cond_resched+0x19/0x30 [ 10.714767] ? aa_sk_perm+0x43/0x1b0 [ 10.714768] __sys_sendmsg+0x5c/0xa0 [ 10.714770] __x64_sys_sendmsg+0x1f/0x30 [ 10.714772] do_syscall_64+0x57/0x1b0 [ 10.714773] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 10.714774] RIP: 0033:0x7fbcedffb5b7 [ 10.714775] Code: 64 89 02 48 c7 c0 ff ff ff ff eb bb 0f 1f 80 00 00 00 00 f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 2e 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 51 c3 48 83 ec 28 89 54 24 1c 48 89 74 24 10 [ 10.714776] RSP: 002b:7fff88e22288 EFLAGS: 0246 ORIG_RAX: 002e [ 10.714777] RAX: ffda RBX: 5632787355d0 RCX: 7fbcedffb5b7 [ 10.714777] RDX: RSI: 7fff88e222c0 RDI: 0006 [ 10.714778] RBP: 563278761380 R08: 0004 R09: 563278761380 [ 10.714778] R10: 7fff88e22394 R11: 0246 R12: 5632787354e0 [ 10.714779] R13: 7fff88e222c0 R14: 7fff88e22394 R15: 563278766710 [ 10.714780] ---[ end trace f00c16109236af6f ]--- [ 10.714782] rtw_pci :3a:00.0: failed to read ASPM, ret=-5 Device is unable to scan for networks and error occurs when attempting to turn on/off
[Kernel-packages] [Bug 1891336] Re: gkrellm2-cpufreq depends on libcpupower-dev produced by Debian kernel
*** This bug is a duplicate of bug 1215411 *** https://bugs.launchpad.net/bugs/1215411 ** This bug has been marked a duplicate of bug 1215411 libcpupower.so is not installed from linux-tools -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1891336 Title: gkrellm2-cpufreq depends on libcpupower-dev produced by Debian kernel Status in cpufreqd package in Ubuntu: New Status in gkrellm2-cpufreq package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: I don't know how important that is as gkrellm2-cpufreq itself is scheduled for removal. But I wanted to make sure that it is known that the Debian kernel produces "libcpupower-dev" which isn't available in Ubuntu and thereby blocking various things in proposed. root@d10-sid:~# apt-cache show libcpupower-dev Package: libcpupower-dev Source: linux Version: 5.7.10-1 Installed-Size: 169 Maintainer: Debian Kernel Team Architecture: amd64 Replaces: libcpufreq-dev Provides: libcpufreq-dev Depends: libcpupower1 (= 5.7.10-1) Conflicts: libcpufreq-dev Description-en: CPU frequency and voltage scaling tools for Linux (development files) libcpupower is a library for inspecting and controlling cpufreq and cpuidle tunables. . This package is needed to compile programs against libcpupower. gkrellm2-cpufreq will most likely be removed from goovy as it makes no sense without that build-dep. Never the less the kernel Team could evaluate if providing "libcpupower-dev" makes sense for Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cpufreqd/+bug/1891336/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903682] Re: [UBUNTU 20.10] NULL pointer dereference when configuring multi-function with devfn != 0 before devfn == 0
** Changed in: ubuntu-z-systems
Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)
** Changed in: linux (Ubuntu)
Assignee: Skipper Bug Screeners (skipper-screen-team) => Frank Heimes
(fheimes)
** Changed in: ubuntu-z-systems
Status: New => Triaged
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1903682
Title:
[UBUNTU 20.10] NULL pointer dereference when configuring multi-
function with devfn != 0 before devfn == 0
Status in Ubuntu on IBM z Systems:
Triaged
Status in linux package in Ubuntu:
New
Bug description:
Background:
When handling multifunction devices in zPCI we take the
UID of the PCI function with function number 0
(that always exists according to the PCI spec)
as domain number.
Therefore when hot plugging functions with function
number larger than 0 before function 0, we need
to hold these in standby before creating the
domain and bus.
This has been tested during feature development
using a patched QEMU and with DPM but never in Classic
Mode.
Reproduction:
This issue was introduced with the Topology aware PCI
Enumeration code so test with a Linux supporting
that feature. E.g. Upstream, Devel Driver etc.
On a Classic Mode machine with a multi-function device,
hot plug ("Reassign I/O Path") only the FID of the
second port to the LPAR.
Symptom:
After this any additional hotplug and even just
deconfiguring a PCI device will hang. A hotplug
makes the entire Linux instance unresponsive.
Analysis:
The problem occurs in Classic Mode but not with
previous testing as the LPAR hypervisor does
hot plug/Reassign I/O Path as a two step process:
1. zPCI event with PEC 0x0302 to plug the zPCI function in Standby
2. zPCI event with PEC 0x0301 to configure the zPCI function
For the first event we create the zdev in clp_add_pci_device()
in Standby which is all fine so far.
The problem then occurs in step 2 as we then find
the existing zdev and try to configure it.
This however does not work as the PCI bus
is not yet created (as we still don't know the UID of
function 0 that will become its domain).
The bus pointer zdev->zbus->bus pointer is thus still
NULL but will be accessed by common code which
inevitably results in disaster including
the above mentioned hang and (possibly) the below
RCU stall:
[ 689.724703] rcu: INFO: rcu_sched self-detected stall on CPU
[ 689.724712] rcu: 16-: (42004 ticks this GP)
idle=6ee/1/0x4002 softirq=1234/1234 fqs=14001
[ 689.724742] (t=42006 jiffies g=89 q=3770)
[ 689.724743] Task dump for CPU 16:
[ 689.724745] task:kmcheck state:R running task stack:0
pid: 205 ppid: 2 flags:0x0004
[ 689.724747] Call Trace:
[ 689.724757] [<000ccde0b5c4>] show_stack+0x8c/0xd8
[ 689.724762] [<000ccd0dabc4>] sched_show_task.part.0+0xe4/0x110
[ 689.724764] [<000ccde0ea5e>] rcu_dump_cpu_stacks+0xde/0x120
[ 689.724767] [<000ccd1465c6>] print_cpu_stall+0x266/0x330
[ 689.724768] [<000ccd14a428>] rcu_sched_clock_irq+0x618/0x670
[ 689.724771] [<000ccd15cd7a>] update_process_times+0xba/0xf0
[ 689.724775] [<000ccd1766fa>] tick_sched_timer+0x9a/0x220
[ 689.724777] [<000ccd15d962>] __hrtimer_run_queues+0x182/0x3a0
[ 689.724779] [<000ccd1602f8>] hrtimer_interrupt+0x138/0x450
[ 689.724782] [<000ccd0451c0>] do_IRQ+0x90/0xa0
[ 689.724784] [<000ccde2be96>] ext_int_handler+0x17e/0x184
[ 689.724790] [<000ccd9f373e>] pci_get_slot+0x5e/0xa0
[ 689.724794] [<000ccd9dc182>] pci_scan_single_device+0x32/0x2a0
[ 689.724797] [<000ccd0868f2>] __zpci_event_availability+0x192/0x360
[ 689.724800] [<000ccdd40c16>] chsc_process_crw+0x2e6/0x300
[ 689.724802] [<000ccdd4b088>] crw_collect_info+0x2b8/0x320
[ 689.724804] [<000ccd0caf3a>] kthread+0x14a/0x170
[ 689.724805] [<000ccde2b814>] ret_from_fork+0x24/0x2c
The fix is very simple, we check zdev->zbus->bus
for being NULL and in that case bail from the
case 0x0301 before calling the PCI common code
pci_scan_single_device() with the NULL pointer.
The only subtlety is that we still need to
do the zpci_enable_device() because the
code in arch/s390/pci/pci_bus.c assumes
that it can immediately do a scan of
all devfn != 0 PCI functions once
PCI function 0 is found.
It thereby mimics what happens
when we only find the FID for a function with
devfn != 0 in the CLP List PCI Functions.
This is implemented in the following upstream
commit:
0b2ca2c7d0c9e2731d01b6c862375d44a7e13923 s390/pci: fix hot-plug of PCI
function missing bus
It is included in v5.10-rc3 and has been tagged for
stable > v5.8 i.e. all upstream versions with
the PCI enumeration changes.
Also it carries the appropriate Fixes
[Kernel-packages] [Bug 1901922] Re: [SRU][Lenovo ThinkPad T14 Gen 1] No sound output device on startup
** Changed in: alsa-ucm-conf (Ubuntu Hirsute) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1901922 Title: [SRU][Lenovo ThinkPad T14 Gen 1] No sound output device on startup Status in PulseAudio: Unknown Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-ucm-conf package in Ubuntu: Fix Committed Status in alsa-lib source package in Focal: Fix Committed Status in alsa-ucm-conf source package in Focal: Fix Committed Status in alsa-lib source package in Groovy: Fix Committed Status in alsa-ucm-conf source package in Groovy: Fix Committed Status in alsa-lib source package in Hirsute: Fix Committed Status in alsa-ucm-conf source package in Hirsute: Fix Committed Bug description: [Impact] On the machines with AMD Ryzen acp audio design, the audio can't work anymore after upgrading the libasound2 to ubuntu3(groovy)/ubuntu2.1( focal), this is a regression on libasound2 for those machines. the AMD Ryzen acp audio card needs to load ucm to work with pulseaudio, but this audio card doesn't have an independant ucm for it, it needs to link to an existing HDA-Intel ucm, the check_empty_configuration() needs to cover the situation that Linked is true, otherwise it will fail to load the ucm for the audio card. Even the audio card could load the ucm, the output is muted and the init output volume is too low if freshly install the OS on these machines. [Fix] Backport 1 alsa-lib patch to fix the failure of loading ucm on AMD Ryzen acp audio machines. Backport 4 alsa-ucm-conf patches to fix init mute and init output volume problem. [Test Case] Install the updated libasuond2, rm ~/.config/pulse/*; sudo rm -rf /var/lib/alsa/*; sudo sh -c 'echo b > /proc/sysrq-trigger' and run pacmd list-cards, we could see the pulseaudio load the ucm successfully and we could see the sound card is generated and all output and input devices are listed under sound card, but the init output is muted and the volume is very low if we manually unumte it. Now install the updated alsa-ucm-conf, rm ~/.config/pulse/*; sudo rm -rf /var/lib/alsa/*; sudo sh -c 'echo b > /proc/sysrq-trigger', the output is not muted anymore and the output volume is OK to most users. [Regression Risk] This could make the machines with sof audio driver fail to load ucm , then all audio function can't work as before, like the speaker can't output sound or the internal mic can't be found or can't record sound. But this possibility is very low, I tested this SRU on some machines with or without sof audio driver, all worked as well as before. After logging in, only a dummy device is available for audio playback (resulting in no audible playback). When running "pactl load-module module-detect" the sound card shows up, and playback works as expected. If pulseaudio is restarted with "pulseaudio -k" the playback device disappears again. Running the above command get things working again. If I change the following section in /etc/pulse/default.pa from: ### Automatically load driver modules depending on the hardware available .ifexists module-udev-detect.so load-module module-udev-detect .else ### Use the static hardware detection module (for systems that lack udev support) load-module module-detect .endif To: ### Automatically load driver modules depending on the hardware available #.ifexists module-udev-detect.so #load-module module-udev-detect #.else ### Use the static hardware detection module (for systems that lack udev support) load-module module-detect #.endif Things start working as they should after running "pulseaudio -k". ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Oct 28 17:21:02 2020 InstallationDate: Installed on 2020-10-23 (4 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2020 dmi.bios.release: 1.9 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET40W(1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UDCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnLENOVO:bvrR1BET40W(1.09):bd08/07/2020:br1.9:efr1.9:svnLENOVO:pn20UDCTO1WW:pvrThinkPadT14Gen1:rvnLENOVO:rn20UDCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad
[Kernel-packages] [Bug 1215411] Re: libcpupower.so is not installed from linux-tools
Hi Christian! In comments #11 and #17 there are some patches for this bug. They probably need rebasing though. ** No longer affects: linux (Ubuntu Zesty) ** No longer affects: linux (Ubuntu Eoan) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1215411 Title: libcpupower.so is not installed from linux-tools Status in cpufreqd package in Ubuntu: Confirmed Status in gkrellm2-cpufreq package in Ubuntu: Confirmed Status in linux package in Ubuntu: In Progress Bug description: The patch for bug 1158668 installs cpupower_$(abi_version) command- line tool as well as libcpupower.so.$(abi_version). This isn't particularly suitable for projects that previously used libcpufreq and intend to migrate to libcpupower, because the libcpupower.so symlink is no longer installed. The command-line tools can also have symlinks (e.g. cpupower -> cpupower_$(abi_version)). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cpufreqd/+bug/1215411/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903680] [NEW] touchpad not detected
Public bug reported: touchpad not detected ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-26-generic 5.8.0-26.27 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: wang7x 4441 F pulseaudio /dev/snd/controlC0: wang7x 4441 F pulseaudio /dev/snd/controlC1: wang7x 4441 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 10 18:42:55 2020 InstallationDate: Installed on 2020-07-28 (104 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUSTeK COMPUTER INC. ROG Zephyrus G15 GA502IV_GA502IV ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-26-generic root=UUID=51f8eab4-d775-4020-aace-0e411ef5b8ed ro i8042.reset quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-26-generic N/A linux-backports-modules-5.8.0-26-generic N/A linux-firmware1.190.1 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2020-11-10 (0 days ago) dmi.bios.date: 08/03/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GA502IV.207 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GA502IV 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.ec.firmware.release: 3.10 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGA502IV.207:bd08/03/2020:br5.16:efr3.10:svnASUSTeKCOMPUTERINC.:pnROGZephyrusG15GA502IV_GA502IV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGA502IV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG Zephyrus G15 dmi.product.name: ROG Zephyrus G15 GA502IV_GA502IV dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1903680 Title: touchpad not detected Status in linux package in Ubuntu: Confirmed Bug description: touchpad not detected ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-26-generic 5.8.0-26.27 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: wang7x 4441 F pulseaudio /dev/snd/controlC0: wang7x 4441 F pulseaudio /dev/snd/controlC1: wang7x 4441 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 10 18:42:55 2020 InstallationDate: Installed on 2020-07-28 (104 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUSTeK COMPUTER INC. ROG Zephyrus G15 GA502IV_GA502IV ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-26-generic root=UUID=51f8eab4-d775-4020-aace-0e411ef5b8ed ro i8042.reset quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-26-generic N/A linux-backports-modules-5.8.0-26-generic N/A linux-firmware1.190.1 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2020-11-10 (0 days ago) dmi.bios.date: 08/03/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GA502IV.207 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GA502IV 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.ec.firmware.release: 3.10 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGA502IV.207:bd08/03/2020:br5.16:efr3.10:svnASUSTeKCOMPUTERINC.:pnROGZephyrusG15GA502IV_GA502IV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGA502IV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG Zephyrus G15 dmi.product.name: ROG Zephyrus G15 GA502IV_GA502IV dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903680/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903682] Re: [UBUNTU 20.10] NULL pointer dereference when configuring multi-function with devfn != 0 before devfn == 0
** Also affects: ubuntu-z-systems
Importance: Undecided
Status: New
** Changed in: ubuntu-z-systems
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1903682
Title:
[UBUNTU 20.10] NULL pointer dereference when configuring multi-
function with devfn != 0 before devfn == 0
Status in Ubuntu on IBM z Systems:
New
Status in linux package in Ubuntu:
New
Bug description:
Background:
When handling multifunction devices in zPCI we take the
UID of the PCI function with function number 0
(that always exists according to the PCI spec)
as domain number.
Therefore when hot plugging functions with function
number larger than 0 before function 0, we need
to hold these in standby before creating the
domain and bus.
This has been tested during feature development
using a patched QEMU and with DPM but never in Classic
Mode.
Reproduction:
This issue was introduced with the Topology aware PCI
Enumeration code so test with a Linux supporting
that feature. E.g. Upstream, Devel Driver etc.
On a Classic Mode machine with a multi-function device,
hot plug ("Reassign I/O Path") only the FID of the
second port to the LPAR.
Symptom:
After this any additional hotplug and even just
deconfiguring a PCI device will hang. A hotplug
makes the entire Linux instance unresponsive.
Analysis:
The problem occurs in Classic Mode but not with
previous testing as the LPAR hypervisor does
hot plug/Reassign I/O Path as a two step process:
1. zPCI event with PEC 0x0302 to plug the zPCI function in Standby
2. zPCI event with PEC 0x0301 to configure the zPCI function
For the first event we create the zdev in clp_add_pci_device()
in Standby which is all fine so far.
The problem then occurs in step 2 as we then find
the existing zdev and try to configure it.
This however does not work as the PCI bus
is not yet created (as we still don't know the UID of
function 0 that will become its domain).
The bus pointer zdev->zbus->bus pointer is thus still
NULL but will be accessed by common code which
inevitably results in disaster including
the above mentioned hang and (possibly) the below
RCU stall:
[ 689.724703] rcu: INFO: rcu_sched self-detected stall on CPU
[ 689.724712] rcu: 16-: (42004 ticks this GP)
idle=6ee/1/0x4002 softirq=1234/1234 fqs=14001
[ 689.724742] (t=42006 jiffies g=89 q=3770)
[ 689.724743] Task dump for CPU 16:
[ 689.724745] task:kmcheck state:R running task stack:0
pid: 205 ppid: 2 flags:0x0004
[ 689.724747] Call Trace:
[ 689.724757] [<000ccde0b5c4>] show_stack+0x8c/0xd8
[ 689.724762] [<000ccd0dabc4>] sched_show_task.part.0+0xe4/0x110
[ 689.724764] [<000ccde0ea5e>] rcu_dump_cpu_stacks+0xde/0x120
[ 689.724767] [<000ccd1465c6>] print_cpu_stall+0x266/0x330
[ 689.724768] [<000ccd14a428>] rcu_sched_clock_irq+0x618/0x670
[ 689.724771] [<000ccd15cd7a>] update_process_times+0xba/0xf0
[ 689.724775] [<000ccd1766fa>] tick_sched_timer+0x9a/0x220
[ 689.724777] [<000ccd15d962>] __hrtimer_run_queues+0x182/0x3a0
[ 689.724779] [<000ccd1602f8>] hrtimer_interrupt+0x138/0x450
[ 689.724782] [<000ccd0451c0>] do_IRQ+0x90/0xa0
[ 689.724784] [<000ccde2be96>] ext_int_handler+0x17e/0x184
[ 689.724790] [<000ccd9f373e>] pci_get_slot+0x5e/0xa0
[ 689.724794] [<000ccd9dc182>] pci_scan_single_device+0x32/0x2a0
[ 689.724797] [<000ccd0868f2>] __zpci_event_availability+0x192/0x360
[ 689.724800] [<000ccdd40c16>] chsc_process_crw+0x2e6/0x300
[ 689.724802] [<000ccdd4b088>] crw_collect_info+0x2b8/0x320
[ 689.724804] [<000ccd0caf3a>] kthread+0x14a/0x170
[ 689.724805] [<000ccde2b814>] ret_from_fork+0x24/0x2c
The fix is very simple, we check zdev->zbus->bus
for being NULL and in that case bail from the
case 0x0301 before calling the PCI common code
pci_scan_single_device() with the NULL pointer.
The only subtlety is that we still need to
do the zpci_enable_device() because the
code in arch/s390/pci/pci_bus.c assumes
that it can immediately do a scan of
all devfn != 0 PCI functions once
PCI function 0 is found.
It thereby mimics what happens
when we only find the FID for a function with
devfn != 0 in the CLP List PCI Functions.
This is implemented in the following upstream
commit:
0b2ca2c7d0c9e2731d01b6c862375d44a7e13923 s390/pci: fix hot-plug of PCI
function missing bus
It is included in v5.10-rc3 and has been tagged for
stable > v5.8 i.e. all upstream versions with
the PCI enumeration changes.
Also it carries the appropriate Fixes tag.
I have verified that it cherry-picks cleanly
on current focal master-next and expect
it to cleanly cherry-pick on newer Ubuntu
[Kernel-packages] [Bug 1903680] 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/1903680 Title: touchpad not detected Status in linux package in Ubuntu: Confirmed Bug description: touchpad not detected ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-26-generic 5.8.0-26.27 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: wang7x 4441 F pulseaudio /dev/snd/controlC0: wang7x 4441 F pulseaudio /dev/snd/controlC1: wang7x 4441 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 10 18:42:55 2020 InstallationDate: Installed on 2020-07-28 (104 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUSTeK COMPUTER INC. ROG Zephyrus G15 GA502IV_GA502IV ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-26-generic root=UUID=51f8eab4-d775-4020-aace-0e411ef5b8ed ro i8042.reset quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-26-generic N/A linux-backports-modules-5.8.0-26-generic N/A linux-firmware1.190.1 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2020-11-10 (0 days ago) dmi.bios.date: 08/03/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GA502IV.207 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GA502IV 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.ec.firmware.release: 3.10 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGA502IV.207:bd08/03/2020:br5.16:efr3.10:svnASUSTeKCOMPUTERINC.:pnROGZephyrusG15GA502IV_GA502IV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGA502IV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG Zephyrus G15 dmi.product.name: ROG Zephyrus G15 GA502IV_GA502IV dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903680/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903682] [NEW] [UBUNTU 20.10] NULL pointer dereference when configuring multi-function with devfn != 0 before devfn == 0
Public bug reported:
Background:
When handling multifunction devices in zPCI we take the
UID of the PCI function with function number 0
(that always exists according to the PCI spec)
as domain number.
Therefore when hot plugging functions with function
number larger than 0 before function 0, we need
to hold these in standby before creating the
domain and bus.
This has been tested during feature development
using a patched QEMU and with DPM but never in Classic
Mode.
Reproduction:
This issue was introduced with the Topology aware PCI
Enumeration code so test with a Linux supporting
that feature. E.g. Upstream, Devel Driver etc.
On a Classic Mode machine with a multi-function device,
hot plug ("Reassign I/O Path") only the FID of the
second port to the LPAR.
Symptom:
After this any additional hotplug and even just
deconfiguring a PCI device will hang. A hotplug
makes the entire Linux instance unresponsive.
Analysis:
The problem occurs in Classic Mode but not with
previous testing as the LPAR hypervisor does
hot plug/Reassign I/O Path as a two step process:
1. zPCI event with PEC 0x0302 to plug the zPCI function in Standby
2. zPCI event with PEC 0x0301 to configure the zPCI function
For the first event we create the zdev in clp_add_pci_device()
in Standby which is all fine so far.
The problem then occurs in step 2 as we then find
the existing zdev and try to configure it.
This however does not work as the PCI bus
is not yet created (as we still don't know the UID of
function 0 that will become its domain).
The bus pointer zdev->zbus->bus pointer is thus still
NULL but will be accessed by common code which
inevitably results in disaster including
the above mentioned hang and (possibly) the below
RCU stall:
[ 689.724703] rcu: INFO: rcu_sched self-detected stall on CPU
[ 689.724712] rcu: 16-: (42004 ticks this GP)
idle=6ee/1/0x4002 softirq=1234/1234 fqs=14001
[ 689.724742] (t=42006 jiffies g=89 q=3770)
[ 689.724743] Task dump for CPU 16:
[ 689.724745] task:kmcheck state:R running task stack:0 pid:
205 ppid: 2 flags:0x0004
[ 689.724747] Call Trace:
[ 689.724757] [<000ccde0b5c4>] show_stack+0x8c/0xd8
[ 689.724762] [<000ccd0dabc4>] sched_show_task.part.0+0xe4/0x110
[ 689.724764] [<000ccde0ea5e>] rcu_dump_cpu_stacks+0xde/0x120
[ 689.724767] [<000ccd1465c6>] print_cpu_stall+0x266/0x330
[ 689.724768] [<000ccd14a428>] rcu_sched_clock_irq+0x618/0x670
[ 689.724771] [<000ccd15cd7a>] update_process_times+0xba/0xf0
[ 689.724775] [<000ccd1766fa>] tick_sched_timer+0x9a/0x220
[ 689.724777] [<000ccd15d962>] __hrtimer_run_queues+0x182/0x3a0
[ 689.724779] [<000ccd1602f8>] hrtimer_interrupt+0x138/0x450
[ 689.724782] [<000ccd0451c0>] do_IRQ+0x90/0xa0
[ 689.724784] [<000ccde2be96>] ext_int_handler+0x17e/0x184
[ 689.724790] [<000ccd9f373e>] pci_get_slot+0x5e/0xa0
[ 689.724794] [<000ccd9dc182>] pci_scan_single_device+0x32/0x2a0
[ 689.724797] [<000ccd0868f2>] __zpci_event_availability+0x192/0x360
[ 689.724800] [<000ccdd40c16>] chsc_process_crw+0x2e6/0x300
[ 689.724802] [<000ccdd4b088>] crw_collect_info+0x2b8/0x320
[ 689.724804] [<000ccd0caf3a>] kthread+0x14a/0x170
[ 689.724805] [<000ccde2b814>] ret_from_fork+0x24/0x2c
The fix is very simple, we check zdev->zbus->bus
for being NULL and in that case bail from the
case 0x0301 before calling the PCI common code
pci_scan_single_device() with the NULL pointer.
The only subtlety is that we still need to
do the zpci_enable_device() because the
code in arch/s390/pci/pci_bus.c assumes
that it can immediately do a scan of
all devfn != 0 PCI functions once
PCI function 0 is found.
It thereby mimics what happens
when we only find the FID for a function with
devfn != 0 in the CLP List PCI Functions.
This is implemented in the following upstream
commit:
0b2ca2c7d0c9e2731d01b6c862375d44a7e13923 s390/pci: fix hot-plug of PCI
function missing bus
It is included in v5.10-rc3 and has been tagged for
stable > v5.8 i.e. all upstream versions with
the PCI enumeration changes.
Also it carries the appropriate Fixes tag.
I have verified that it cherry-picks cleanly
on current focal master-next and expect
it to cleanly cherry-pick on newer Ubuntu
Kernels too.
** Affects: ubuntu-z-systems
Importance: Medium
Status: New
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Skipper Bug Screeners (skipper-screen-team)
Status: New
** Tags: architecture-s39064 bugnameltc-189163 severity-medium
targetmilestone-inin2010
** Tags added: architecture-s39064 bugnameltc-189163 severity-medium
targetmilestone-inin2010
** Changed in: ubuntu
Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)
** Package changed: ubuntu => linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
[Kernel-packages] [Bug 1901563] Re: [i915] Kernel crashed in vma_create when running Xorg
Thanks for opening the issue Bernd. I haven't inspected kernel stack traces before, so in my eyes they looked similar :-) The issue has not occurred since I switched to Wayland. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1901563 Title: [i915] Kernel crashed in vma_create when running Xorg Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: I've just upgraded to 20.10. After logging in and using PyCharm for a while, the system froze, and I had to do a REISUB. It turned out to be a kernel panic and seems related to Xorg and the i915 driver. This has now happened multiple times, and not all crashes have happened while using PyCharm. I've tried using the ppa:canonical-kernel-team/ppa to install a new kernel (5.8.0-26-generic) but that did not help. [ 1620.425014] general protection fault, probably for non-canonical address 0xe296718293aa0a0a: [#1] SMP PTI [ 1620.425017] CPU: 2 PID: 1749 Comm: Xorg Tainted: GW 5.8.0-26-generic #27-Ubuntu [ 1620.425018] Hardware name: Dell Inc. XPS 13 9370/0F6P3V, BIOS 1.2.1 02/21/2018 [ 1620.425023] RIP: 0010:kmem_cache_alloc+0x7e/0x230 [ 1620.425025] Code: 95 01 00 00 4d 8b 07 65 49 8b 50 08 65 4c 03 05 a0 59 33 4d 4d 8b 20 4d 85 e4 0f 84 81 01 00 00 41 8b 47 20 49 8b 3f 4c 01 e0 <48> 8b 18 48 89 c1 49 33 9f 70 01 00 00 4c 89 e0 48 0f c9 48 31 cb [ 1620.425026] RSP: 0018:b1f6c19e79b0 EFLAGS: 00010286 [ 1620.425028] RAX: e296718293aa0a0a RBX: RCX: 0002 [ 1620.425029] RDX: 7d5e RSI: 0dc0 RDI: 441461604a80 [ 1620.425031] RBP: b1f6c19e79e0 R08: d1f6bfc84a80 R09: [ 1620.425032] R10: R11: 8de1eca2f6c2 R12: e296718293aa08b2 [ 1620.425033] R13: 0dc0 R14: 8de2488364c0 R15: 8de2488364c0 [ 1620.425034] FS: 7fe9c3b52a40() GS:8de25e68() knlGS: [ 1620.425035] CS: 0010 DS: ES: CR0: 80050033 [ 1620.425037] CR2: 7f6c1433c000 CR3: 000488622001 CR4: 003606e0 [ 1620.425038] Call Trace: [ 1620.425087] ? vma_create+0x30/0x460 [i915] [ 1620.425122] vma_create+0x30/0x460 [i915] [ 1620.425124] ? mutex_lock+0x13/0x40 [ 1620.425157] i915_vma_instance+0xd2/0xe0 [i915] [ 1620.425187] eb_lookup_vma+0xd7/0x1c0 [i915] [ 1620.425217] eb_lookup_vmas+0x79/0x200 [i915] [ 1620.425247] eb_relocate+0x18/0x1b0 [i915] [ 1620.425275] i915_gem_do_execbuffer+0x265/0x8d0 [i915] [ 1620.425278] ? enqueue_task_fair+0x159/0x590 [ 1620.425282] ? __radix_tree_replace+0x4a/0xe0 [ 1620.425285] ? _cond_resched+0x1a/0x50 [ 1620.425287] ? kmem_cache_alloc_trace+0x168/0x240 [ 1620.425290] ? __kmalloc_node+0x201/0x300 [ 1620.425320] i915_gem_execbuffer2_ioctl+0x237/0x4a0 [i915] [ 1620.425348] ? intel_engines_add_sysfs+0x150/0x150 [i915] [ 1620.425350] ? radix_tree_lookup+0xd/0x10 [ 1620.425379] ? i915_gem_execbuffer_ioctl+0x2e0/0x2e0 [i915] [ 1620.425395] drm_ioctl_kernel+0xae/0xf0 [drm] [ 1620.425406] drm_ioctl+0x238/0x3d0 [drm] [ 1620.425434] ? i915_gem_execbuffer_ioctl+0x2e0/0x2e0 [i915] [ 1620.425437] ? fput+0x13/0x15 [ 1620.425440] ? __sys_recvmsg+0x94/0xb0 [ 1620.425442] ksys_ioctl+0x8e/0xc0 [ 1620.425444] __x64_sys_ioctl+0x1a/0x20 [ 1620.425447] do_syscall_64+0x49/0xc0 [ 1620.425449] entry_SYSCALL_64_after_hwframe+0x44/0xa9 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME-Flashback:GNOME Date: Mon Oct 26 16:33:28 2020 DistUpgraded: 2020-10-23 13:15:10,351 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: groovy DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:07e6] InstallationDate: Installed on 2018-05-04 (906 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. XPS 13 9370
[Kernel-packages] [Bug 1903048] Re: [SRU] Bluetooth won't activate on the pi 400
** Summary changed: - Bluetooth won't activate on the pi 400 + [SRU] Bluetooth won't activate on the pi 400 -- 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/1903048 Title: [SRU] Bluetooth won't activate on the pi 400 Status in bluez package in Ubuntu: Confirmed Bug description: The new Pi 400 has a slightly different Wifi/BT chip to the Pi4. Whilst wifi works happily, Bluetooth fails to operate. This doesn't appear to be an issue with either the firmware (the latest versions from upstream Raspbian have been tried), or the kernel (a known-good raspi kernel has been tested under Ubuntu), but with Bluez itself. Specifically, tracing the initialization with btmon on Raspbian and Ubuntu, the stack consistently fails when attempting to "Set Default PHY" on the latter. Curiously, under Ubuntu the adapter also appears to lack a MAC address. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1903048/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903682] Comment bridged from LTC Bugzilla
--- Comment From niklas.schne...@ibm.com 2020-11-10 07:36 EDT---
(In reply to comment #7)
> Ok, I can see that the commit got accepted with 5.10-rc3, hence it will land
> in hirsute.
> And because the patch was tagged as stable for 5.8, it will land in groovy's
> kernel 5.8 (I'll check the 'Groovy update: v5.8.x upstream stable release'
> kernel team tracking tickets and will align the status).
>
> Remaining todo is to cherry-pick and manually SRU to focal/5.4.
Great, that matches my expectation too.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1903682
Title:
[UBUNTU 20.10] NULL pointer dereference when configuring multi-
function with devfn != 0 before devfn == 0
Status in Ubuntu on IBM z Systems:
Triaged
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Focal:
New
Status in linux source package in Groovy:
Triaged
Status in linux source package in Hirsute:
Fix Committed
Bug description:
Background:
When handling multifunction devices in zPCI we take the
UID of the PCI function with function number 0
(that always exists according to the PCI spec)
as domain number.
Therefore when hot plugging functions with function
number larger than 0 before function 0, we need
to hold these in standby before creating the
domain and bus.
This has been tested during feature development
using a patched QEMU and with DPM but never in Classic
Mode.
Reproduction:
This issue was introduced with the Topology aware PCI
Enumeration code so test with a Linux supporting
that feature. E.g. Upstream, Devel Driver etc.
On a Classic Mode machine with a multi-function device,
hot plug ("Reassign I/O Path") only the FID of the
second port to the LPAR.
Symptom:
After this any additional hotplug and even just
deconfiguring a PCI device will hang. A hotplug
makes the entire Linux instance unresponsive.
Analysis:
The problem occurs in Classic Mode but not with
previous testing as the LPAR hypervisor does
hot plug/Reassign I/O Path as a two step process:
1. zPCI event with PEC 0x0302 to plug the zPCI function in Standby
2. zPCI event with PEC 0x0301 to configure the zPCI function
For the first event we create the zdev in clp_add_pci_device()
in Standby which is all fine so far.
The problem then occurs in step 2 as we then find
the existing zdev and try to configure it.
This however does not work as the PCI bus
is not yet created (as we still don't know the UID of
function 0 that will become its domain).
The bus pointer zdev->zbus->bus pointer is thus still
NULL but will be accessed by common code which
inevitably results in disaster including
the above mentioned hang and (possibly) the below
RCU stall:
[ 689.724703] rcu: INFO: rcu_sched self-detected stall on CPU
[ 689.724712] rcu: 16-: (42004 ticks this GP)
idle=6ee/1/0x4002 softirq=1234/1234 fqs=14001
[ 689.724742] (t=42006 jiffies g=89 q=3770)
[ 689.724743] Task dump for CPU 16:
[ 689.724745] task:kmcheck state:R running task stack:0
pid: 205 ppid: 2 flags:0x0004
[ 689.724747] Call Trace:
[ 689.724757] [<000ccde0b5c4>] show_stack+0x8c/0xd8
[ 689.724762] [<000ccd0dabc4>] sched_show_task.part.0+0xe4/0x110
[ 689.724764] [<000ccde0ea5e>] rcu_dump_cpu_stacks+0xde/0x120
[ 689.724767] [<000ccd1465c6>] print_cpu_stall+0x266/0x330
[ 689.724768] [<000ccd14a428>] rcu_sched_clock_irq+0x618/0x670
[ 689.724771] [<000ccd15cd7a>] update_process_times+0xba/0xf0
[ 689.724775] [<000ccd1766fa>] tick_sched_timer+0x9a/0x220
[ 689.724777] [<000ccd15d962>] __hrtimer_run_queues+0x182/0x3a0
[ 689.724779] [<000ccd1602f8>] hrtimer_interrupt+0x138/0x450
[ 689.724782] [<000ccd0451c0>] do_IRQ+0x90/0xa0
[ 689.724784] [<000ccde2be96>] ext_int_handler+0x17e/0x184
[ 689.724790] [<000ccd9f373e>] pci_get_slot+0x5e/0xa0
[ 689.724794] [<000ccd9dc182>] pci_scan_single_device+0x32/0x2a0
[ 689.724797] [<000ccd0868f2>] __zpci_event_availability+0x192/0x360
[ 689.724800] [<000ccdd40c16>] chsc_process_crw+0x2e6/0x300
[ 689.724802] [<000ccdd4b088>] crw_collect_info+0x2b8/0x320
[ 689.724804] [<000ccd0caf3a>] kthread+0x14a/0x170
[ 689.724805] [<000ccde2b814>] ret_from_fork+0x24/0x2c
The fix is very simple, we check zdev->zbus->bus
for being NULL and in that case bail from the
case 0x0301 before calling the PCI common code
pci_scan_single_device() with the NULL pointer.
The only subtlety is that we still need to
do the zpci_enable_device() because the
code in arch/s390/pci/pci_bus.c assumes
that it can immediately do a scan of
all devfn != 0 PCI functions once
PCI function 0 is found.
It thereby mimics what happens
when we only find the
[Kernel-packages] [Bug 1901563] Re: [i915] Kernel crashed in vma_create when running Xorg
I'm actually going to close the upstream issue - I'm still not clear on the root cause - it is a slab/kmem cache issue, but I don't which subsystem is responsible for it. It might get visible on opening various kernel debug options, but it requires to recompile and also slows down the system dramatically, unfortunately I don't have the time for that :( Especially as the issue went away after installing the linux-5.9.3 kernel. I guess switching to wayland just avoid the trigger, but the 5.8 kernel seems to have a bad bug. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1901563 Title: [i915] Kernel crashed in vma_create when running Xorg Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: I've just upgraded to 20.10. After logging in and using PyCharm for a while, the system froze, and I had to do a REISUB. It turned out to be a kernel panic and seems related to Xorg and the i915 driver. This has now happened multiple times, and not all crashes have happened while using PyCharm. I've tried using the ppa:canonical-kernel-team/ppa to install a new kernel (5.8.0-26-generic) but that did not help. [ 1620.425014] general protection fault, probably for non-canonical address 0xe296718293aa0a0a: [#1] SMP PTI [ 1620.425017] CPU: 2 PID: 1749 Comm: Xorg Tainted: GW 5.8.0-26-generic #27-Ubuntu [ 1620.425018] Hardware name: Dell Inc. XPS 13 9370/0F6P3V, BIOS 1.2.1 02/21/2018 [ 1620.425023] RIP: 0010:kmem_cache_alloc+0x7e/0x230 [ 1620.425025] Code: 95 01 00 00 4d 8b 07 65 49 8b 50 08 65 4c 03 05 a0 59 33 4d 4d 8b 20 4d 85 e4 0f 84 81 01 00 00 41 8b 47 20 49 8b 3f 4c 01 e0 <48> 8b 18 48 89 c1 49 33 9f 70 01 00 00 4c 89 e0 48 0f c9 48 31 cb [ 1620.425026] RSP: 0018:b1f6c19e79b0 EFLAGS: 00010286 [ 1620.425028] RAX: e296718293aa0a0a RBX: RCX: 0002 [ 1620.425029] RDX: 7d5e RSI: 0dc0 RDI: 441461604a80 [ 1620.425031] RBP: b1f6c19e79e0 R08: d1f6bfc84a80 R09: [ 1620.425032] R10: R11: 8de1eca2f6c2 R12: e296718293aa08b2 [ 1620.425033] R13: 0dc0 R14: 8de2488364c0 R15: 8de2488364c0 [ 1620.425034] FS: 7fe9c3b52a40() GS:8de25e68() knlGS: [ 1620.425035] CS: 0010 DS: ES: CR0: 80050033 [ 1620.425037] CR2: 7f6c1433c000 CR3: 000488622001 CR4: 003606e0 [ 1620.425038] Call Trace: [ 1620.425087] ? vma_create+0x30/0x460 [i915] [ 1620.425122] vma_create+0x30/0x460 [i915] [ 1620.425124] ? mutex_lock+0x13/0x40 [ 1620.425157] i915_vma_instance+0xd2/0xe0 [i915] [ 1620.425187] eb_lookup_vma+0xd7/0x1c0 [i915] [ 1620.425217] eb_lookup_vmas+0x79/0x200 [i915] [ 1620.425247] eb_relocate+0x18/0x1b0 [i915] [ 1620.425275] i915_gem_do_execbuffer+0x265/0x8d0 [i915] [ 1620.425278] ? enqueue_task_fair+0x159/0x590 [ 1620.425282] ? __radix_tree_replace+0x4a/0xe0 [ 1620.425285] ? _cond_resched+0x1a/0x50 [ 1620.425287] ? kmem_cache_alloc_trace+0x168/0x240 [ 1620.425290] ? __kmalloc_node+0x201/0x300 [ 1620.425320] i915_gem_execbuffer2_ioctl+0x237/0x4a0 [i915] [ 1620.425348] ? intel_engines_add_sysfs+0x150/0x150 [i915] [ 1620.425350] ? radix_tree_lookup+0xd/0x10 [ 1620.425379] ? i915_gem_execbuffer_ioctl+0x2e0/0x2e0 [i915] [ 1620.425395] drm_ioctl_kernel+0xae/0xf0 [drm] [ 1620.425406] drm_ioctl+0x238/0x3d0 [drm] [ 1620.425434] ? i915_gem_execbuffer_ioctl+0x2e0/0x2e0 [i915] [ 1620.425437] ? fput+0x13/0x15 [ 1620.425440] ? __sys_recvmsg+0x94/0xb0 [ 1620.425442] ksys_ioctl+0x8e/0xc0 [ 1620.425444] __x64_sys_ioctl+0x1a/0x20 [ 1620.425447] do_syscall_64+0x49/0xc0 [ 1620.425449] entry_SYSCALL_64_after_hwframe+0x44/0xa9 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME-Flashback:GNOME Date: Mon Oct 26 16:33:28 2020 DistUpgraded: 2020-10-23 13:15:10,351 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: groovy DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu
[Kernel-packages] [Bug 1807974] Re: Qualcomm Atheros QCA617 [168c:003e] Subsystem [1a56:143a] Wireless regularly breaking (ath10k firmware crashed!) after upgrade to Cosmic on Dell XPS 13 9370
Broke again on upgrade from Focal to Groovy.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1807974
Title:
Qualcomm Atheros QCA617 [168c:003e] Subsystem [1a56:143a] Wireless
regularly breaking (ath10k firmware crashed!) after upgrade to Cosmic
on Dell XPS 13 9370
Status in linux package in Ubuntu:
Confirmed
Bug description:
I have a Dell XPS 13 9370 developer edition (Ubuntu version) running
Cosmic. A handful of times per day, my wireless stops working ("?"
appears in the icon in Network Manager). Turning wireless off and then
on again, or suspending and waking the machine up, makes the wireless
work again.
dmesg output is as follows:
$ dmesg | grep ath10k
[ 6646.268929] ath10k_pci :02:00.0: firmware crashed! (guid
6317c652-4817-4fdd-b6d7-c7b8336e493f)
[ 6646.268982] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503
chip_id 0x00340aff sub 1a56:143a
[ 6646.268990] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[ 6646.270369] ath10k_pci :02:00.0: firmware ver
WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb
[ 6646.271379] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32
20d869c3
[ 6646.271393] ath10k_pci :02:00.0: htt-ver 3.47 wmi-op 4 htt-op 3 cal
otp max-sta 32 raw 0 hwcrypto 1
[ 6646.28] ath10k_pci :02:00.0: failed to get memcpy hi address for
firmware address 4: -16
[ 6646.283336] ath10k_pci :02:00.0: failed to read firmware dump area: -16
[ 6646.283339] ath10k_pci :02:00.0: Copy Engine register dump:
[ 6646.283348] ath10k_pci :02:00.0: [00]: 0x00034400 14 14 3 3
[ 6646.283357] ath10k_pci :02:00.0: [01]: 0x00034800 29 29 106 107
[ 6646.283365] ath10k_pci :02:00.0: [02]: 0x00034c00 20 19 18 19
[ 6646.283374] ath10k_pci :02:00.0: [03]: 0x00035000 8 8 10 8
[ 6646.283386] ath10k_pci :02:00.0: [04]: 0x00035400 2763 2763 167 103
[ 6646.283394] ath10k_pci :02:00.0: [05]: 0x00035800 0 0 64 0
[ 6646.283402] ath10k_pci :02:00.0: [06]: 0x00035c00 0 0 6 6
[ 6646.283412] ath10k_pci :02:00.0: [07]: 0x00036000 0 1 0 1
[ 6646.301351] ath10k_pci :02:00.0: failed to read hi_board_data address:
-28
[ 6647.126841] ath10k_pci :02:00.0: Unknown eventid: 118809
[ 6647.129850] ath10k_pci :02:00.0: Unknown eventid: 90118
[ 6647.239340] ath10k_pci :02:00.0: device successfully recovered
[17641.847345] ath10k_pci :02:00.0: firmware crashed! (guid
03393f2f-0ce1-4017-b711-40dd14f2ec11)
[17641.847363] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503
chip_id 0x00340aff sub 1a56:143a
[17641.847367] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[17641.848065] ath10k_pci :02:00.0: firmware ver
WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb
[17641.848585] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32
20d869c3
[17641.848593] ath10k_pci :02:00.0: htt-ver 3.47 wmi-op 4 htt-op 3 cal
otp max-sta 32 raw 0 hwcrypto 1
[17641.860559] ath10k_pci :02:00.0: failed to get memcpy hi address for
firmware address 4: -16
[17641.860587] ath10k_pci :02:00.0: failed to read firmware dump area: -16
[17641.860595] ath10k_pci :02:00.0: Copy Engine register dump:
[17641.860611] ath10k_pci :02:00.0: [00]: 0x00034400 14 14 3 3
[17641.860624] ath10k_pci :02:00.0: [01]: 0x00034800 6 6 243 244
[17641.860639] ath10k_pci :02:00.0: [02]: 0x00034c00 53 52 51 52
[17641.860656] ath10k_pci :02:00.0: [03]: 0x00035000 5 5 7 5
[17641.860669] ath10k_pci :02:00.0: [04]: 0x00035400 1231 1231 169 105
[17641.860681] ath10k_pci :02:00.0: [05]: 0x00035800 0 0 64 0
[17641.860693] ath10k_pci :02:00.0: [06]: 0x00035c00 0 0 30 30
[17641.860706] ath10k_pci :02:00.0: [07]: 0x00036000 0 1 0 1
[17641.890915] ath10k_pci :02:00.0: failed to read hi_board_data address:
-28
[17642.714052] ath10k_pci :02:00.0: Unknown eventid: 118809
[17642.717154] ath10k_pci :02:00.0: Unknown eventid: 90118
[17642.835601] ath10k_pci :02:00.0: device successfully recovered
[17894.571696] ath10k_pci :02:00.0: Unknown eventid: 118809
[17894.574764] ath10k_pci :02:00.0: Unknown eventid: 90118
I do not recall having any wireless issues before I upgraded (when
this machine was running Bionic).
Bug #1730331 - ath10k_pci: firmware crashed!
Bug #1627474 - ath10k_pci :03:00.0: firmware crashed! (uuid n/a) [16.10]
could be related, but appear to be related to earlier releases, whereas my
issue has appeared/become much worse on Cosmic.
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: linux-image-4.18.0-11-generic 4.18.0-11.12
ProcVersionSignature:
[Kernel-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
@vanvugt Thank you for your quick response! Does that mean I would have to wait for Pulseaudio to fix this in one of their future releases (maybe v.15) or will it be possible to use an alternative soundmanager, where the kernel fixes would be sufficient to use A2DP for bidirectional bluetooth sound? Homeoffice without cableless headset is just not that comfortable :s Best Regards Dennis -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: In Progress Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1901922] Re: [SRU][Lenovo ThinkPad T14 Gen 1] No sound output device on startup
This bug was fixed in the package alsa-ucm-conf - 1.2.2-1ubuntu6 --- alsa-ucm-conf (1.2.2-1ubuntu6) hirsute; urgency=medium * d/p/0001-sof-hda-dsp-add-initial-kcontrol-values.patch * d/p/0002-sof-hda-dsp-make-the-boot-init-optional-for-all-cont.patch * d/p/0003-sof-hda-dsp-Set-Master-Playback-Switch-on-in-the-Boo.patch * d/p/0004-sof-hda-dsp-Increase-the-speaker-output-volume-in-th.patch Unmute the master playback switch and increase the init output volume, otherwise the playback will be muted after freshly install the OS if the machine uses ucm to configure the audio mixers, and the init playback output volume is too low after freshly install the OS. (LP: #1901922) -- Hui Wang Mon, 09 Nov 2020 03:59:02 + ** Changed in: alsa-ucm-conf (Ubuntu Hirsute) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1901922 Title: [SRU][Lenovo ThinkPad T14 Gen 1] No sound output device on startup Status in PulseAudio: Unknown Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in alsa-lib source package in Focal: Fix Committed Status in alsa-ucm-conf source package in Focal: Fix Committed Status in alsa-lib source package in Groovy: Fix Committed Status in alsa-ucm-conf source package in Groovy: Fix Committed Status in alsa-lib source package in Hirsute: Fix Committed Status in alsa-ucm-conf source package in Hirsute: Fix Released Bug description: [Impact] On the machines with AMD Ryzen acp audio design, the audio can't work anymore after upgrading the libasound2 to ubuntu3(groovy)/ubuntu2.1( focal), this is a regression on libasound2 for those machines. the AMD Ryzen acp audio card needs to load ucm to work with pulseaudio, but this audio card doesn't have an independant ucm for it, it needs to link to an existing HDA-Intel ucm, the check_empty_configuration() needs to cover the situation that Linked is true, otherwise it will fail to load the ucm for the audio card. Even the audio card could load the ucm, the output is muted and the init output volume is too low if freshly install the OS on these machines. [Fix] Backport 1 alsa-lib patch to fix the failure of loading ucm on AMD Ryzen acp audio machines. Backport 4 alsa-ucm-conf patches to fix init mute and init output volume problem. [Test Case] Install the updated libasuond2, rm ~/.config/pulse/*; sudo rm -rf /var/lib/alsa/*; sudo sh -c 'echo b > /proc/sysrq-trigger' and run pacmd list-cards, we could see the pulseaudio load the ucm successfully and we could see the sound card is generated and all output and input devices are listed under sound card, but the init output is muted and the volume is very low if we manually unumte it. Now install the updated alsa-ucm-conf, rm ~/.config/pulse/*; sudo rm -rf /var/lib/alsa/*; sudo sh -c 'echo b > /proc/sysrq-trigger', the output is not muted anymore and the output volume is OK to most users. [Regression Risk] This could make the machines with sof audio driver fail to load ucm , then all audio function can't work as before, like the speaker can't output sound or the internal mic can't be found or can't record sound. But this possibility is very low, I tested this SRU on some machines with or without sof audio driver, all worked as well as before. After logging in, only a dummy device is available for audio playback (resulting in no audible playback). When running "pactl load-module module-detect" the sound card shows up, and playback works as expected. If pulseaudio is restarted with "pulseaudio -k" the playback device disappears again. Running the above command get things working again. If I change the following section in /etc/pulse/default.pa from: ### Automatically load driver modules depending on the hardware available .ifexists module-udev-detect.so load-module module-udev-detect .else ### Use the static hardware detection module (for systems that lack udev support) load-module module-detect .endif To: ### Automatically load driver modules depending on the hardware available #.ifexists module-udev-detect.so #load-module module-udev-detect #.else ### Use the static hardware detection module (for systems that lack udev support) load-module module-detect #.endif Things start working as they should after running "pulseaudio -k". ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Oct 28 17:21:02 2020 InstallationDate: Installed on 2020-10-23 (4 days ago)
[Kernel-packages] [Bug 1894329] Re: ZFS revert from grub menu not working.
** Patch added: "zfs-linux_0.8.4-1ubuntu13_0.8.4-1ubuntu14.debdiff"
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1894329/+attachment/5433026/+files/zfs-linux_0.8.4-1ubuntu13_0.8.4-1ubuntu14.debdiff
--
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/1894329
Title:
ZFS revert from grub menu not working.
Status in coreutils package in Ubuntu:
Incomplete
Status in zfs-linux package in Ubuntu:
In Progress
Status in coreutils source package in Focal:
Incomplete
Status in zfs-linux source package in Focal:
Triaged
Status in coreutils source package in Groovy:
Incomplete
Status in zfs-linux source package in Groovy:
Triaged
Bug description:
@coreutils maintainers, any idea why dd is being flagged as having an
executable stack?
When I try to revert to a previous state from the grub menu, the boot
fails. The system drops me to a repair modus.
zfs-mount-generator fails with the message:
couldn't ensure boot: Mounted clone bootFS dataset created by initramfs
doesn't have a valid _suffix (at least .*_): \"rpool/ROOT/ubuntu_\"".
After a reboot I have an extra clone called "rpool/ROOT/ubuntu_", indeed
without a suffix.
After a little investigation I found the problem in
/usr/share/initramfs-tools/scripts/zfs at the end in function
uid()
{
dd if=/dev/urandom of=/dev/stdout bs=1 count=100 2>/dev/null | tr -dc
'a-z0-9' | cut -c-6
}, the dd command fails during boot with the message "process 'dd' started
with executable stack.
After this an empty uid is returned which explains the dataset without a
proper suffix.
Replacing the function with:
uid()
{
grep -a -m10 -E "\*" /dev/urandom 2>/dev/null | tr -dc 'a-z0-9' | cut -c-6
}
fixes the problem.
Ubuntu version is:
Description:Ubuntu Groovy Gorilla (development branch)
Release:20.10
zfs-initramfs version is:
0.8.4-1ubuntu11
With regards,
Usarin Heininga
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: zfs-initramfs 0.8.4-1ubuntu11
ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
Uname: Linux 5.8.0-18-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu45
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Fri Sep 4 20:23:44 2020
InstallationDate: Installed on 2020-09-02 (2 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200831)
ProcEnviron:
LANGUAGE=
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=nl_NL.UTF-8
SHELL=/bin/bash
SourcePackage: zfs-linux
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1894329/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851518] Re: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones
@kaihengfeng Can you describe what fix was implemented? I updated to kernel 5.4.0-52-generic in Ubuntu 20.04 and it is not fixed. I still must run the script. Also, something has regressed with the latest updates because now I have to manually run "pulseaudio --start" after booting to get it all to work. Prior to running this command PulseAudio Volume Control just stays stuck on establishing connection. It did not do this before the last batch of pulse and alsa updates -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851518 Title: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones Status in linux package in Ubuntu: Fix Released Bug description: I've been googling this issue for 10's of hours and tried many things. Relase of Ubuntu: 19.10 Expected outcome: Music plays on the internal speakers and headphones. Actual outcome: I can barely hear audio using headphones with volume turned up to 150%. Absolutely nothing comes out of the speakers. (The speakers sound great under Windows 10.) Complete alsa-info output is attached, but here are some snippets: !!DMI Information !!--- Manufacturer: SAMSUNG ELECTRONICS CO., LTD. Product Name: 950SBE/951SBE Product Version: P06RES Firmware Version: P06RES.075.190529.SP Board Vendor: SAMSUNG ELECTRONICS CO., LTD. Board Name:NP950SBE-K01US !!Kernel Information !!-- Kernel release:5.3.0-19-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.3.0-19-generic Library version:1.1.9 Utilities version: 1.1.9 !!Loaded ALSA modules !!--- snd_hda_intel !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0x604b118000 irq 177 !!PCI Soundcards installed in the system !!-- 00:1f.3 Multimedia audio controller: Intel Corporation Cannon Point-LP High Definition Audio Controller (rev 11) !!Advanced information - PCI Vendor/Device/Subsystem ID's !!--- 00:1f.3 0401: 8086:9dc8 (rev 11) DeviceName: Onboard - Sound !!HDA-Intel Codec information !!--- --startcollapse-- Codec: Realtek ALC298 Address: 0 AFG Function Id: 0x1 (unsol 1) Vendor Id: 0x10ec0298 Subsystem Id: 0x144dc812 Revision Id: 0x100103 No Modem Function Group found Default PCM: rates [0x60]: 44100 48000 bits [0xe]: 16 20 24 formats [0x1]: PCM Default Amp-In caps: N/A Default Amp-Out caps: N/A State of AFG node 0x01: Power states: D0 D1 D2 D3 D3cold CLKSTOP EPSS Power: setting=D0, actual=D0 GPIO: io=8, o=0, i=0, unsolicited=1, wake=0 IO[0]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[1]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[2]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[3]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[4]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[5]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[6]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[7]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 Node 0x02 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Headphone Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Device: name="ALC298 Analog", type="Audio", device=0 Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0 Amp-Out vals: [0x00 0x00] Converter: stream=1, channel=0 PCM: rates [0x60]: 44100 48000 bits [0xe]: 16 20 24 formats [0x1]: PCM Power states: D0 D1 D2 D3 EPSS Power: setting=D0, actual=D0 Node 0x03 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Speaker Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0 Amp-Out vals: [0x7f 0x7f] Converter: stream=1, channel=0 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin 1383 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Nov 6
[Kernel-packages] [Bug 1894329] Re: ZFS revert from grub menu not working.
This is the patch from Usarin Heininga applied against Hirsute.
--
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/1894329
Title:
ZFS revert from grub menu not working.
Status in coreutils package in Ubuntu:
Incomplete
Status in zfs-linux package in Ubuntu:
In Progress
Status in coreutils source package in Focal:
Incomplete
Status in zfs-linux source package in Focal:
Triaged
Status in coreutils source package in Groovy:
Incomplete
Status in zfs-linux source package in Groovy:
Triaged
Bug description:
@coreutils maintainers, any idea why dd is being flagged as having an
executable stack?
When I try to revert to a previous state from the grub menu, the boot
fails. The system drops me to a repair modus.
zfs-mount-generator fails with the message:
couldn't ensure boot: Mounted clone bootFS dataset created by initramfs
doesn't have a valid _suffix (at least .*_): \"rpool/ROOT/ubuntu_\"".
After a reboot I have an extra clone called "rpool/ROOT/ubuntu_", indeed
without a suffix.
After a little investigation I found the problem in
/usr/share/initramfs-tools/scripts/zfs at the end in function
uid()
{
dd if=/dev/urandom of=/dev/stdout bs=1 count=100 2>/dev/null | tr -dc
'a-z0-9' | cut -c-6
}, the dd command fails during boot with the message "process 'dd' started
with executable stack.
After this an empty uid is returned which explains the dataset without a
proper suffix.
Replacing the function with:
uid()
{
grep -a -m10 -E "\*" /dev/urandom 2>/dev/null | tr -dc 'a-z0-9' | cut -c-6
}
fixes the problem.
Ubuntu version is:
Description:Ubuntu Groovy Gorilla (development branch)
Release:20.10
zfs-initramfs version is:
0.8.4-1ubuntu11
With regards,
Usarin Heininga
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: zfs-initramfs 0.8.4-1ubuntu11
ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
Uname: Linux 5.8.0-18-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu45
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Fri Sep 4 20:23:44 2020
InstallationDate: Installed on 2020-09-02 (2 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200831)
ProcEnviron:
LANGUAGE=
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=nl_NL.UTF-8
SHELL=/bin/bash
SourcePackage: zfs-linux
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1894329/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903048] Re: Bluetooth won't activate on the pi 400
Ok, I was asked to sponsor it, so I'm pushing the changes to hirsute and groovy. I have filled MPs for both for the bluez repo (no write access). Also, a hirsute branch needs to be opened, so the first MP is for now only targeting groovy (invalidly): https://code.launchpad.net/~sil2100/bluez/+git/bluez/+merge/393548 https://code.launchpad.net/~sil2100/bluez/+git/bluez/+merge/393549 Cheers. -- 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/1903048 Title: [SRU] Bluetooth won't activate on the pi 400 Status in bluez package in Ubuntu: Confirmed Bug description: The new Pi 400 has a slightly different Wifi/BT chip to the Pi4. Whilst wifi works happily, Bluetooth fails to operate. This doesn't appear to be an issue with either the firmware (the latest versions from upstream Raspbian have been tried), or the kernel (a known-good raspi kernel has been tested under Ubuntu), but with Bluez itself. Specifically, tracing the initialization with btmon on Raspbian and Ubuntu, the stack consistently fails when attempting to "Set Default PHY" on the latter. Curiously, under Ubuntu the adapter also appears to lack a MAC address. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1903048/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903048] Re: [SRU] Bluetooth won't activate on the pi 400
** Description changed: + [Impact] + + Without these patches, Bluetooth is inoperable on the recently released + Raspberry Pi 400. + + [Test Case] + + * Boot the Ubuntu Desktop for Pi image on a Pi 400. + * Start the Settings application and switch to the Bluetooth tab + * Verify that Bluetooth is not enabled and attempting to activate it fails + * sudo add-apt-repository ppa:waveform/pi-bluetooth + * sudo apt update + * sudo apt install bluez + * sudo reboot + * Start the Settings application and switch to the Bluetooth tab + * Verify that Bluetooth is active and that Bluetooth devices (e.g. mice, mobile phones, headphones, etc.) can connect and operate correctly + + [Regression Potential] + + Extremely low (on groovy in particular, this has the same version of + bluez as hirsute). The only significant risk is to non-Pi platforms or + dongles which also use the Broadcom 43xx (or Cypress 305) chips for + Bluetooth which might be inadvertently affected by these patches. + + [Original Description] + The new Pi 400 has a slightly different Wifi/BT chip to the Pi4. Whilst wifi works happily, Bluetooth fails to operate. This doesn't appear to be an issue with either the firmware (the latest versions from upstream Raspbian have been tried), or the kernel (a known-good raspi kernel has been tested under Ubuntu), but with Bluez itself. Specifically, tracing the initialization with btmon on Raspbian and Ubuntu, the stack consistently fails when attempting to "Set Default PHY" on the latter. Curiously, under Ubuntu the adapter also appears to lack a MAC address. -- 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/1903048 Title: [SRU] Bluetooth won't activate on the pi 400 Status in bluez package in Ubuntu: Confirmed Bug description: [Impact] Without these patches, Bluetooth is inoperable on the recently released Raspberry Pi 400. [Test Case] * Boot the Ubuntu Desktop for Pi image on a Pi 400. * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is not enabled and attempting to activate it fails * sudo add-apt-repository ppa:waveform/pi-bluetooth * sudo apt update * sudo apt install bluez * sudo reboot * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is active and that Bluetooth devices (e.g. mice, mobile phones, headphones, etc.) can connect and operate correctly [Regression Potential] Extremely low (on groovy in particular, this has the same version of bluez as hirsute). The only significant risk is to non-Pi platforms or dongles which also use the Broadcom 43xx (or Cypress 305) chips for Bluetooth which might be inadvertently affected by these patches. [Original Description] The new Pi 400 has a slightly different Wifi/BT chip to the Pi4. Whilst wifi works happily, Bluetooth fails to operate. This doesn't appear to be an issue with either the firmware (the latest versions from upstream Raspbian have been tried), or the kernel (a known-good raspi kernel has been tested under Ubuntu), but with Bluez itself. Specifically, tracing the initialization with btmon on Raspbian and Ubuntu, the stack consistently fails when attempting to "Set Default PHY" on the latter. Curiously, under Ubuntu the adapter also appears to lack a MAC address. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1903048/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903048] Re: [SRU] Bluetooth won't activate on the pi 400
** Changed in: bluez (Ubuntu) Importance: Undecided => High ** Changed in: bluez (Ubuntu) Status: Confirmed => Fix Committed -- 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/1903048 Title: [SRU] Bluetooth won't activate on the pi 400 Status in bluez package in Ubuntu: Fix Committed Bug description: [Impact] Without these patches, Bluetooth is inoperable on the recently released Raspberry Pi 400. [Test Case] * Boot the Ubuntu Desktop for Pi image on a Pi 400. * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is not enabled and attempting to activate it fails * sudo add-apt-repository ppa:waveform/pi-bluetooth * sudo apt update * sudo apt install bluez * sudo reboot * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is active and that Bluetooth devices (e.g. mice, mobile phones, headphones, etc.) can connect and operate correctly [Regression Potential] Extremely low (on groovy in particular, this has the same version of bluez as hirsute). The only significant risk is to non-Pi platforms or dongles which also use the Broadcom 43xx (or Cypress 305) chips for Bluetooth which might be inadvertently affected by these patches. [Original Description] The new Pi 400 has a slightly different Wifi/BT chip to the Pi4. Whilst wifi works happily, Bluetooth fails to operate. This doesn't appear to be an issue with either the firmware (the latest versions from upstream Raspbian have been tried), or the kernel (a known-good raspi kernel has been tested under Ubuntu), but with Bluez itself. Specifically, tracing the initialization with btmon on Raspbian and Ubuntu, the stack consistently fails when attempting to "Set Default PHY" on the latter. Curiously, under Ubuntu the adapter also appears to lack a MAC address. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1903048/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
@dennis9771 Just get yourself Bluetooth audio card and save yourself a trouble, this will never be fixed. And you will not be able to use A2DP for conversation even if fixed. The goal of the fix is to add HFP 1.6 with mSBC 16kHz audio encoding so you have better quality during conversation. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: In Progress Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903048] Re: [SRU] Bluetooth won't activate on the pi 400
Thanks for the work but it there any work to upstream those changes? I'm not happy to carry a sleep(1) hack in our package unless there is a strong reason and we are working on a way to replace it by a better solution -- 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/1903048 Title: [SRU] Bluetooth won't activate on the pi 400 Status in bluez package in Ubuntu: Fix Committed Bug description: [Impact] Without these patches, Bluetooth is inoperable on the recently released Raspberry Pi 400. [Test Case] * Boot the Ubuntu Desktop for Pi image on a Pi 400. * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is not enabled and attempting to activate it fails * sudo add-apt-repository ppa:waveform/pi-bluetooth * sudo apt update * sudo apt install bluez * sudo reboot * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is active and that Bluetooth devices (e.g. mice, mobile phones, headphones, etc.) can connect and operate correctly [Regression Potential] Extremely low (on groovy in particular, this has the same version of bluez as hirsute). The only significant risk is to non-Pi platforms or dongles which also use the Broadcom 43xx (or Cypress 305) chips for Bluetooth which might be inadvertently affected by these patches. [Original Description] The new Pi 400 has a slightly different Wifi/BT chip to the Pi4. Whilst wifi works happily, Bluetooth fails to operate. This doesn't appear to be an issue with either the firmware (the latest versions from upstream Raspbian have been tried), or the kernel (a known-good raspi kernel has been tested under Ubuntu), but with Bluez itself. Specifically, tracing the initialization with btmon on Raspbian and Ubuntu, the stack consistently fails when attempting to "Set Default PHY" on the latter. Curiously, under Ubuntu the adapter also appears to lack a MAC address. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1903048/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903761] [NEW] Touchpad doesn't work at all (No response from the Touchpad)
Public bug reported: 1) Laptop model directly from the sticker of the computer: Lenovo IdeaPad 15IIL05 2) Manufacturer of the Touchpad: Lenovo 3) When the symptom first appeared: At the begining of the Ubuntu installation (Has never responded on Ubuntu) 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.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mitsaras0110 1586 F pulseaudio /dev/snd/pcmC0D0p: mitsaras0110 1586 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 10 21:02:57 2020 InstallationDate: Installed on 2020-11-08 (2 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 0461:4d80 Primax Electronics, Ltd USB Optical Mouse Bus 001 Device 002: ID 174f:118d Syntek Integrated Camera Bus 001 Device 003: ID 8087:0026 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81WE ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=271f88a5-ce39-4dee-b06e-92fd317a9564 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EMCN13WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32866 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 3 15IIL05 dmi.modalias: dmi:bvnLENOVO:bvrEMCN13WW:bd03/06/2020:svnLENOVO:pn81WE:pvrIdeaPad315IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0R32866WIN:cvnLENOVO:ct10:cvrIdeaPad315IIL05: dmi.product.family: IdeaPad 3 15IIL05 dmi.product.name: 81WE dmi.product.sku: LENOVO_MT_81WE_BU_idea_FM_IdeaPad 3 15IIL05 dmi.product.version: IdeaPad 3 15IIL05 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug focal ** Attachment added: "devices" https://bugs.launchpad.net/bugs/1903761/+attachment/5433066/+files/devices -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1903761 Title: Touchpad doesn't work at all (No response from the Touchpad) Status in linux package in Ubuntu: Confirmed Bug description: 1) Laptop model directly from the sticker of the computer: Lenovo IdeaPad 15IIL05 2) Manufacturer of the Touchpad: Lenovo 3) When the symptom first appeared: At the begining of the Ubuntu installation (Has never responded on Ubuntu) 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.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mitsaras0110 1586 F pulseaudio /dev/snd/pcmC0D0p: mitsaras0110 1586 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 10 21:02:57 2020 InstallationDate: Installed on 2020-11-08 (2 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 0461:4d80 Primax Electronics, Ltd USB Optical Mouse Bus 001 Device 002: ID 174f:118d Syntek Integrated Camera Bus 001 Device 003: ID 8087:0026 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81WE ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=271f88a5-ce39-4dee-b06e-92fd317a9564 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EMCN13WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32866 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 3 15IIL05 dmi.modalias:
[Kernel-packages] [Bug 1894329] Re: ZFS revert from grub menu not working.
Patch for 20.10.
** Patch added: "zfs-linux_0.8.4-1ubuntu11_0.8.4-1ubuntu11.1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1894329/+attachment/5433041/+files/zfs-linux_0.8.4-1ubuntu11_0.8.4-1ubuntu11.1.debdiff
--
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/1894329
Title:
ZFS revert from grub menu not working.
Status in coreutils package in Ubuntu:
Incomplete
Status in zfs-linux package in Ubuntu:
In Progress
Status in coreutils source package in Focal:
Incomplete
Status in zfs-linux source package in Focal:
Triaged
Status in coreutils source package in Groovy:
Incomplete
Status in zfs-linux source package in Groovy:
Triaged
Bug description:
@coreutils maintainers, any idea why dd is being flagged as having an
executable stack?
When I try to revert to a previous state from the grub menu, the boot
fails. The system drops me to a repair modus.
zfs-mount-generator fails with the message:
couldn't ensure boot: Mounted clone bootFS dataset created by initramfs
doesn't have a valid _suffix (at least .*_): \"rpool/ROOT/ubuntu_\"".
After a reboot I have an extra clone called "rpool/ROOT/ubuntu_", indeed
without a suffix.
After a little investigation I found the problem in
/usr/share/initramfs-tools/scripts/zfs at the end in function
uid()
{
dd if=/dev/urandom of=/dev/stdout bs=1 count=100 2>/dev/null | tr -dc
'a-z0-9' | cut -c-6
}, the dd command fails during boot with the message "process 'dd' started
with executable stack.
After this an empty uid is returned which explains the dataset without a
proper suffix.
Replacing the function with:
uid()
{
grep -a -m10 -E "\*" /dev/urandom 2>/dev/null | tr -dc 'a-z0-9' | cut -c-6
}
fixes the problem.
Ubuntu version is:
Description:Ubuntu Groovy Gorilla (development branch)
Release:20.10
zfs-initramfs version is:
0.8.4-1ubuntu11
With regards,
Usarin Heininga
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: zfs-initramfs 0.8.4-1ubuntu11
ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
Uname: Linux 5.8.0-18-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu45
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Fri Sep 4 20:23:44 2020
InstallationDate: Installed on 2020-09-02 (2 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200831)
ProcEnviron:
LANGUAGE=
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=nl_NL.UTF-8
SHELL=/bin/bash
SourcePackage: zfs-linux
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1894329/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1902701] Re: zfs-linux 0.8.3-1ubuntu12.4 ADT test failure with linux-hwe-5.8 5.8.0-25.26~20.04.1
Hello Stefan, or anyone else affected, Accepted zfs-linux into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/zfs- linux/0.8.3-1ubuntu12.5 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: zfs-linux (Ubuntu Focal) Status: In Progress => Fix Committed -- 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/1902701 Title: zfs-linux 0.8.3-1ubuntu12.4 ADT test failure with linux-hwe-5.8 5.8.0-25.26~20.04.1 Status in zfs-linux package in Ubuntu: Invalid Status in zfs-linux source package in Focal: Fix Committed Bug description: [SRU Justification] Impact: When attempting to compile the zfs-dkms module on a 5.8 kernel the module fails to properly configure the build. The kernel driver part of zfs-linux is only prepared to handle the kernels it released with. For Ubuntu kernels the zfs module is build based on the zfs-dkms that is current for the series the kernel originates from (so Groovy for 5.8). And this should be the encouraged way to do this. Fix: Add a limitation to the dkms package to only build for supported kernels. This causes the whole build/install to be skipped on 5.8 rather than to fail. Testcase: dkms install runs for 5.4 and 5.8 in Focal. For the 5.8 kernel this should result in: Building initial module for 5.8.0-25-generic Error! The /var/lib/dkms/zfs/0.8.3/5.8.0-25-generic/x86_64/dkms.conf for module zfs includes a BUILD_EXCLUSIVE directive which does not match this kernel/arch. This indicates that it should not be built. Skipped. Regression Potential: Since the module fails to compile for the newer kernel there should be nothing that can regress. --- Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/z/zfs-linux/20201016_104632_e52aa@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/arm64/z/zfs-linux/20201016_144759_7735c@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/ppc64el/z/zfs-linux/20201016_111820_ceeb8@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/s390x/z/zfs-linux/20201016_082202_1adb7@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1902701/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903761] 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/1903761 Title: Touchpad doesn't work at all (No response from the Touchpad) Status in linux package in Ubuntu: Confirmed Bug description: 1) Laptop model directly from the sticker of the computer: Lenovo IdeaPad 15IIL05 2) Manufacturer of the Touchpad: Lenovo 3) When the symptom first appeared: At the begining of the Ubuntu installation (Has never responded on Ubuntu) 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.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mitsaras0110 1586 F pulseaudio /dev/snd/pcmC0D0p: mitsaras0110 1586 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 10 21:02:57 2020 InstallationDate: Installed on 2020-11-08 (2 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 0461:4d80 Primax Electronics, Ltd USB Optical Mouse Bus 001 Device 002: ID 174f:118d Syntek Integrated Camera Bus 001 Device 003: ID 8087:0026 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81WE ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=271f88a5-ce39-4dee-b06e-92fd317a9564 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EMCN13WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32866 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 3 15IIL05 dmi.modalias: dmi:bvnLENOVO:bvrEMCN13WW:bd03/06/2020:svnLENOVO:pn81WE:pvrIdeaPad315IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0R32866WIN:cvnLENOVO:ct10:cvrIdeaPad315IIL05: dmi.product.family: IdeaPad 3 15IIL05 dmi.product.name: 81WE dmi.product.sku: LENOVO_MT_81WE_BU_idea_FM_IdeaPad 3 15IIL05 dmi.product.version: IdeaPad 3 15IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903761/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903768] [NEW] Bionic update: upstream stable patchset 2020-11-10
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2020-11-10 Ported from the following upstream stable releases: v4.14.202, v4.19.152, v4.14.203, v4.19.153 from git://git.kernel.org/ Bluetooth: fix kernel oops in store_pending_adv_report Bluetooth: Consolidate encryption handling in hci_encrypt_cfm Bluetooth: Fix update of connection state in `hci_encrypt_cfm` Bluetooth: Disconnect if E0 is used for Level 4 media: usbtv: Fix refcounting mixup USB: serial: option: add Cellient MPL200 card USB: serial: option: Add Telit FT980-KS composition staging: comedi: check validity of wMaxPacketSize of usb endpoints found USB: serial: pl2303: add device-id for HP GC device USB: serial: ftdi_sio: add support for FreeCalypso JTAG+UART adapters reiserfs: Initialize inode keys properly reiserfs: Fix oops during mount drivers/net/ethernet/marvell/mvmdio.c: Fix non OF case crypto: bcm - Verify GCM/CCM key length in setkey crypto: qat - check cipher length for aead AES-CBC-HMAC-SHA ARM: 8858/1: vdso: use $(LD) instead of $(CC) to link VDSO ARM: 8939/1: kbuild: use correct nm executable ARM: 8867/1: vdso: pass --be8 to linker if necessary UBUNTU: upstream stable to v4.14.202, v4.19.152 ibmveth: Switch order of ibmveth_helper calls. ibmveth: Identify ingress large send packets. ipv4: Restore flowi4_oif update before call to xfrm_lookup_route mlx4: handle non-napi callers to napi_poll net: usb: qmi_wwan: add Cellient MPL200 card tipc: fix the skb_unshare() in tipc_buf_append() net/ipv4: always honour route mtu during forwarding r8169: fix data corruption issue on RTL8402 binder: fix UAF when releasing todo list ALSA: bebob: potential info leak in hwdep_read() net: hdlc: In hdlc_rcv, check to make sure dev is an HDLC device net: hdlc_raw_eth: Clear the IFF_TX_SKB_SHARING flag after calling ether_setup nfc: Ensure presence of NFC_ATTR_FIRMWARE_NAME attribute in nfc_genl_fw_download() tcp: fix to update snd_wl1 in bulk receiver fast path icmp: randomize the global rate limiter cifs: remove bogus debug code cifs: Return the error from crypt_message when enc/dec key not found. KVM: x86/mmu: Commit zap of remaining invalid pages when recovering lpages KVM: SVM: Initialize prev_ga_tag before use ima: Don't ignore errors from crypto_shash_update() crypto: algif_aead - Do not set MAY_BACKLOG on the async path EDAC/i5100: Fix error handling order in i5100_init_one() x86/fpu: Allow multiple bits in clearcpuid= parameter drivers/perf: xgene_pmu: Fix uninitialized resource struct crypto: algif_skcipher - EBUSY on aio should be an error crypto: mediatek - Fix wrong return value in mtk_desc_ring_alloc() crypto: ixp4xx - Fix the size used in a 'dma_free_coherent()' call media: tuner-simple: fix regression in simple_set_radio_freq media: Revert "media: exynos4-is: Add missed check for pinctrl_lookup_state()" media: m5mols: Check function pointer in m5mols_sensor_power media: uvcvideo: Set media controller entity functions media: omap3isp: Fix memleak in isp_probe crypto: omap-sham - fix digcnt register handling with export/import cypto: mediatek - fix leaks in mtk_desc_ring_alloc media: mx2_emmaprp: Fix memleak in emmaprp_probe media: tc358743: initialize variable media: platform: fcp: Fix a reference count leak. media: s5p-mfc: Fix a reference count leak media: ti-vpe: Fix a missing check and reference count leak regulator: resolve supply after creating regulator ath10k: provide survey info as accumulated data Bluetooth: hci_uart: Cancel init work before unregistering ath6kl: prevent potential array overflow in ath6kl_add_new_sta() ath9k: Fix potential out of bounds in ath9k_htc_txcompletion_cb() wcn36xx: Fix reported 802.11n rx_highest rate wcn3660/wcn3680 ASoC: qcom: lpass-platform: fix memory leak ASoC: qcom: lpass-cpu: fix concurrency issue brcmfmac: check ndev pointer mwifiex: Do not use GFP_KERNEL in atomic context drm/gma500: fix error check scsi: qla4xxx: Fix an error handling path in 'qla4xxx_get_host_stats()' scsi: csiostor: Fix wrong return value in csio_hw_prep_fw() backlight: sky81452-backlight: Fix refcount imbalance on error VMCI: check return value of get_user_pages_fast() for errors tty: serial: earlycon dependency pty: do tty_flip_buffer_push without port->lock in pty_write pwm: lpss: Fix off by one error in base_unit math in pwm_lpss_prepare() pwm: lpss: Add range limit check for the base_unit register value drivers/virt/fsl_hypervisor: Fix error handling path video: fbdev: vga16fb: fix setting of pixclock
[Kernel-packages] [Bug 1902254] Re: Bionic: btrfs: kernel BUG at /build/linux-eTBZpZ/linux-4.15.0/fs/btrfs/ctree.c:3233!
This mainline commit, recently backported to [B,F,G] for this bug: "btrfs: extent-tree: kill BUG_ON() in __btrfs_free_extent()" introduces a compile warning. The warning has been fixed in mainline by: cad69d139651 btrfs: tree-checker: fix incorrect printk format so let's pick up that fix too. Patch submitted: https://lists.ubuntu.com/archives/kernel- team/2020-November/114752.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1902254 Title: Bionic: btrfs: kernel BUG at /build/linux- eTBZpZ/linux-4.15.0/fs/btrfs/ctree.c:3233! Status in linux package in Ubuntu: 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: Fix Committed Bug description: [Impact] * Users of btrfs started hitting a kernel BUG() (below) after upgrade from 4.15.0-99.100 to 4.15.0-109.110, which has 55 btrfs changes. kernel BUG at /build/linux-eTBZpZ/linux-4.15.0/fs/btrfs/ctree.c:3233! ... Krnl PSW : be9cb874 ef3786e8 (btrfs_set_item_key_safe+0x152/0x1c0 [btrfs]) ... [...] Call Trace: [...] btrfs_set_item_key_safe+0x11c/0x1c0 [btrfs]) [...] __btrfs_drop_extents+0xb5a/0xda8 [btrfs] [...] btrfs_log_changed_extents+0x35c/0xaf0 [btrfs] [...] btrfs_log_inode+0x9ee/0x1080 [btrfs] [...] btrfs_log_inode_parent+0x224/0xa10 [btrfs] [...] btrfs_log_dentry_safe+0x80/0xa8 [btrfs] [...] btrfs_sync_file+0x392/0x550 [btrfs] [...] do_fsync+0x5e/0x90 [...] SyS_fdatasync+0x32/0x48 [...] system_call+0xd8/0x2c8 $ git log --oneline Ubuntu-4.15.0-99.100..Ubuntu-4.15.0-109.110 -- fs/btrfs/ | wc -l 55 * The error happens at random moments, regardless of a particular activity/load. Workaround is to downgrade. [Fix] * This BUG()/function is addressed in patch 4/4 [1] of series 'btrfs: Enhanced runtime defence against fuzzed images' [2], after issues in the real world, not just crafted fs images: 'one internal report has hit one BUG_ON() with real world fs' kernel BUG at fs/btrfs/ctree.c:3188! ... RIP: 0010:btrfs_set_item_key_safe+0x16c/0x180 * The patch/set [3] is applied in v5.10-rc1 and Ubuntu Unstable: - d16c702fe4f2 btrfs: ctree: check key order before merging tree blocks - 07cce5cf3b48 btrfs: extent-tree: kill the BUG_ON() in insert_inline_extent_backref() - 1c2a07f598d5 btrfs: extent-tree: kill BUG_ON() in __btrfs_free_extent() - f98b6215d7d1 btrfs: extent_io: do extra check for extent buffer read write functions [Test Case] * There is working synthetic reproducer for this issue, which is hard to reproduce as reported in commit [4] that introduces debugging for the issue. * Regression tests with xfstests and stress-ng shows no regressions between un/patched kernels. [Other Info] * Trivial backports (only refreshing a few context lines) with 3 more dependency patches on Bionic and 1 on Focal. And Bionic needed one extra hunk to '#include' a header. Groovy all apply cleanly. [1] https://lore.kernel.org/linux-btrfs/20200819063550.62832-5-...@suse.com/ [2] https://lore.kernel.org/linux-btrfs/20200819063550.62832-1-...@suse.com/ [3] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d16c702fe4f274bd77b47d3ab737eadcf24e0b93 [4] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7c15d41016dc886cc011e3854d855e219759ae68 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902254/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851518] Re: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones
@draamses I am surprised to hear it doesn't work, at least manually, on the flex. I obviously don't work for samsung and don't know the hardware internal details, but there is nothing in the script that is known to be explicitly model specific. I am also just running a standard ubuntu kernel now with none of the previously discussed kernel modifications, and the headphone jack and the speakers work with the script. It used to work automatically with the deamon before the last pulse and alsa update in ubuntu, but now I have an issue with pulse starting properly at boot. It is a real mystery why the flex is different given that the flex and ion were released at the same time, that both appear to have the same alc 298 sound devices, and that the script works on the always (released a few years earlier). Possibly there are two separate issues on the flex and both have to be resolved. Do you have pavucontrol installed and if so, do you see "sof-hda-dsp speaker + headphones" in the list of output devices? If not, you may also need to run "pulseaudio --start" before running the script. Also, have you completed the step to turn off the auto idle for pulse? If not, if you run the script before you have sound playing, then pulse will break the sound when it puts the sound card to sleep. To turn off the pulse power saving just run "sudo gedit /etc/pulse/default.pa" and comment out (add the ###) the line that reads "load-module module-suspend-on-idle". And reboot of course. You can easily revert if needed but just removing the ###. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851518 Title: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones Status in linux package in Ubuntu: Fix Released Bug description: I've been googling this issue for 10's of hours and tried many things. Relase of Ubuntu: 19.10 Expected outcome: Music plays on the internal speakers and headphones. Actual outcome: I can barely hear audio using headphones with volume turned up to 150%. Absolutely nothing comes out of the speakers. (The speakers sound great under Windows 10.) Complete alsa-info output is attached, but here are some snippets: !!DMI Information !!--- Manufacturer: SAMSUNG ELECTRONICS CO., LTD. Product Name: 950SBE/951SBE Product Version: P06RES Firmware Version: P06RES.075.190529.SP Board Vendor: SAMSUNG ELECTRONICS CO., LTD. Board Name:NP950SBE-K01US !!Kernel Information !!-- Kernel release:5.3.0-19-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.3.0-19-generic Library version:1.1.9 Utilities version: 1.1.9 !!Loaded ALSA modules !!--- snd_hda_intel !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0x604b118000 irq 177 !!PCI Soundcards installed in the system !!-- 00:1f.3 Multimedia audio controller: Intel Corporation Cannon Point-LP High Definition Audio Controller (rev 11) !!Advanced information - PCI Vendor/Device/Subsystem ID's !!--- 00:1f.3 0401: 8086:9dc8 (rev 11) DeviceName: Onboard - Sound !!HDA-Intel Codec information !!--- --startcollapse-- Codec: Realtek ALC298 Address: 0 AFG Function Id: 0x1 (unsol 1) Vendor Id: 0x10ec0298 Subsystem Id: 0x144dc812 Revision Id: 0x100103 No Modem Function Group found Default PCM: rates [0x60]: 44100 48000 bits [0xe]: 16 20 24 formats [0x1]: PCM Default Amp-In caps: N/A Default Amp-Out caps: N/A State of AFG node 0x01: Power states: D0 D1 D2 D3 D3cold CLKSTOP EPSS Power: setting=D0, actual=D0 GPIO: io=8, o=0, i=0, unsolicited=1, wake=0 IO[0]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[1]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[2]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[3]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[4]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[5]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[6]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[7]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 Node 0x02 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Headphone Playback Volume", index=0, device=0 ControlAmp: chs=3,
[Kernel-packages] [Bug 1903770] [NEW] middle mouse button does not work Logitech M185
Public bug reported: My mouse works ok with movement, left and right click and scrolling. However, the middle mouse click, ie pressing down on the scroll wheel does not work. I am positive this has worked with previous ubuntu versions with this mouse on this laptop. I'll attach the output from evtest - but I'm not sure how helpful that is, it shows all events that work, but shows nothing when I press the middle button. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-26-generic 5.8.0-26.27 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: peter 861 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 10 22:01:13 2020 InstallationDate: Installed on 2020-10-13 (27 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930) MachineType: HP HP Pavilion x2 Detachable ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-26-generic root=UUID=aad7498f-7086-4036-b6dd-8bceef953d46 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-26-generic N/A linux-backports-modules-5.8.0-26-generic N/A linux-firmware1.190 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/14/2016 dmi.bios.release: 15.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.13 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8181 dmi.board.vendor: HP dmi.board.version: 42.25 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 42.25 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.13:bd03/14/2016:br15.13:efr42.25:svnHP:pnHPPavilionx2Detachable:pvr:rvnHP:rn8181:rvr42.25:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT dmi.product.name: HP Pavilion x2 Detachable dmi.product.sku: T9R01EA#ABD dmi.sys.vendor: HP ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy wayland-session -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1903770 Title: middle mouse button does not work Logitech M185 Status in linux package in Ubuntu: New Bug description: My mouse works ok with movement, left and right click and scrolling. However, the middle mouse click, ie pressing down on the scroll wheel does not work. I am positive this has worked with previous ubuntu versions with this mouse on this laptop. I'll attach the output from evtest - but I'm not sure how helpful that is, it shows all events that work, but shows nothing when I press the middle button. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-26-generic 5.8.0-26.27 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: peter 861 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 10 22:01:13 2020 InstallationDate: Installed on 2020-10-13 (27 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930) MachineType: HP HP Pavilion x2 Detachable ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-26-generic root=UUID=aad7498f-7086-4036-b6dd-8bceef953d46 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-26-generic N/A linux-backports-modules-5.8.0-26-generic N/A linux-firmware1.190 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/14/2016 dmi.bios.release: 15.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.13 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8181 dmi.board.vendor: HP dmi.board.version: 42.25 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 42.25 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.13:bd03/14/2016:br15.13:efr42.25:svnHP:pnHPPavilionx2Detachable:pvr:rvnHP:rn8181:rvr42.25:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT dmi.product.name: HP Pavilion x2 Detachable dmi.product.sku: T9R01EA#ABD dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903770/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1903770] Re: middle mouse button does not work Logitech M185
** Attachment added: "evtest.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903770/+attachment/5433117/+files/evtest.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1903770 Title: middle mouse button does not work Logitech M185 Status in linux package in Ubuntu: New Bug description: My mouse works ok with movement, left and right click and scrolling. However, the middle mouse click, ie pressing down on the scroll wheel does not work. I am positive this has worked with previous ubuntu versions with this mouse on this laptop. I'll attach the output from evtest - but I'm not sure how helpful that is, it shows all events that work, but shows nothing when I press the middle button. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-26-generic 5.8.0-26.27 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: peter 861 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 10 22:01:13 2020 InstallationDate: Installed on 2020-10-13 (27 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930) MachineType: HP HP Pavilion x2 Detachable ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-26-generic root=UUID=aad7498f-7086-4036-b6dd-8bceef953d46 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-26-generic N/A linux-backports-modules-5.8.0-26-generic N/A linux-firmware1.190 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/14/2016 dmi.bios.release: 15.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.13 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8181 dmi.board.vendor: HP dmi.board.version: 42.25 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 42.25 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.13:bd03/14/2016:br15.13:efr42.25:svnHP:pnHPPavilionx2Detachable:pvr:rvnHP:rn8181:rvr42.25:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT dmi.product.name: HP Pavilion x2 Detachable dmi.product.sku: T9R01EA#ABD dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903770/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903682] Re: [UBUNTU 20.10] NULL pointer dereference when configuring multi-function with devfn != 0 before devfn == 0
I've build patches kernel packages and shared them here for further reference
and testing:
https://people.canonical.com/~fheimes/lp1903682/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1903682
Title:
[UBUNTU 20.10] NULL pointer dereference when configuring multi-
function with devfn != 0 before devfn == 0
Status in Ubuntu on IBM z Systems:
Triaged
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Focal:
New
Status in linux source package in Groovy:
Triaged
Status in linux source package in Hirsute:
Fix Committed
Bug description:
Background:
When handling multifunction devices in zPCI we take the
UID of the PCI function with function number 0
(that always exists according to the PCI spec)
as domain number.
Therefore when hot plugging functions with function
number larger than 0 before function 0, we need
to hold these in standby before creating the
domain and bus.
This has been tested during feature development
using a patched QEMU and with DPM but never in Classic
Mode.
Reproduction:
This issue was introduced with the Topology aware PCI
Enumeration code so test with a Linux supporting
that feature. E.g. Upstream, Devel Driver etc.
On a Classic Mode machine with a multi-function device,
hot plug ("Reassign I/O Path") only the FID of the
second port to the LPAR.
Symptom:
After this any additional hotplug and even just
deconfiguring a PCI device will hang. A hotplug
makes the entire Linux instance unresponsive.
Analysis:
The problem occurs in Classic Mode but not with
previous testing as the LPAR hypervisor does
hot plug/Reassign I/O Path as a two step process:
1. zPCI event with PEC 0x0302 to plug the zPCI function in Standby
2. zPCI event with PEC 0x0301 to configure the zPCI function
For the first event we create the zdev in clp_add_pci_device()
in Standby which is all fine so far.
The problem then occurs in step 2 as we then find
the existing zdev and try to configure it.
This however does not work as the PCI bus
is not yet created (as we still don't know the UID of
function 0 that will become its domain).
The bus pointer zdev->zbus->bus pointer is thus still
NULL but will be accessed by common code which
inevitably results in disaster including
the above mentioned hang and (possibly) the below
RCU stall:
[ 689.724703] rcu: INFO: rcu_sched self-detected stall on CPU
[ 689.724712] rcu: 16-: (42004 ticks this GP)
idle=6ee/1/0x4002 softirq=1234/1234 fqs=14001
[ 689.724742] (t=42006 jiffies g=89 q=3770)
[ 689.724743] Task dump for CPU 16:
[ 689.724745] task:kmcheck state:R running task stack:0
pid: 205 ppid: 2 flags:0x0004
[ 689.724747] Call Trace:
[ 689.724757] [<000ccde0b5c4>] show_stack+0x8c/0xd8
[ 689.724762] [<000ccd0dabc4>] sched_show_task.part.0+0xe4/0x110
[ 689.724764] [<000ccde0ea5e>] rcu_dump_cpu_stacks+0xde/0x120
[ 689.724767] [<000ccd1465c6>] print_cpu_stall+0x266/0x330
[ 689.724768] [<000ccd14a428>] rcu_sched_clock_irq+0x618/0x670
[ 689.724771] [<000ccd15cd7a>] update_process_times+0xba/0xf0
[ 689.724775] [<000ccd1766fa>] tick_sched_timer+0x9a/0x220
[ 689.724777] [<000ccd15d962>] __hrtimer_run_queues+0x182/0x3a0
[ 689.724779] [<000ccd1602f8>] hrtimer_interrupt+0x138/0x450
[ 689.724782] [<000ccd0451c0>] do_IRQ+0x90/0xa0
[ 689.724784] [<000ccde2be96>] ext_int_handler+0x17e/0x184
[ 689.724790] [<000ccd9f373e>] pci_get_slot+0x5e/0xa0
[ 689.724794] [<000ccd9dc182>] pci_scan_single_device+0x32/0x2a0
[ 689.724797] [<000ccd0868f2>] __zpci_event_availability+0x192/0x360
[ 689.724800] [<000ccdd40c16>] chsc_process_crw+0x2e6/0x300
[ 689.724802] [<000ccdd4b088>] crw_collect_info+0x2b8/0x320
[ 689.724804] [<000ccd0caf3a>] kthread+0x14a/0x170
[ 689.724805] [<000ccde2b814>] ret_from_fork+0x24/0x2c
The fix is very simple, we check zdev->zbus->bus
for being NULL and in that case bail from the
case 0x0301 before calling the PCI common code
pci_scan_single_device() with the NULL pointer.
The only subtlety is that we still need to
do the zpci_enable_device() because the
code in arch/s390/pci/pci_bus.c assumes
that it can immediately do a scan of
all devfn != 0 PCI functions once
PCI function 0 is found.
It thereby mimics what happens
when we only find the FID for a function with
devfn != 0 in the CLP List PCI Functions.
This is implemented in the following upstream
commit:
0b2ca2c7d0c9e2731d01b6c862375d44a7e13923 s390/pci: fix hot-plug of PCI
function missing bus
It is included in v5.10-rc3 and has been tagged for
stable > v5.8 i.e. all upstream versions with
the PCI enumeration changes.
Also it carries
[Kernel-packages] [Bug 1851518] Re: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones
@PowerKiKi @terrymagnusdrever @gannon1 I have the same problem on my Galaxy Book Flex 2020 (system id 0x144dc189). The new kernel helped the earphone work, but there is still no sound from the speakers, even when I am trying the verbs and daemon suggested here. I assume these work for the ION, but not on the FLEX. Is there any way to make the speakers work? This is my RtHDDump.txt: https://pastebin.com/m3xaE2DU -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851518 Title: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones Status in linux package in Ubuntu: Fix Released Bug description: I've been googling this issue for 10's of hours and tried many things. Relase of Ubuntu: 19.10 Expected outcome: Music plays on the internal speakers and headphones. Actual outcome: I can barely hear audio using headphones with volume turned up to 150%. Absolutely nothing comes out of the speakers. (The speakers sound great under Windows 10.) Complete alsa-info output is attached, but here are some snippets: !!DMI Information !!--- Manufacturer: SAMSUNG ELECTRONICS CO., LTD. Product Name: 950SBE/951SBE Product Version: P06RES Firmware Version: P06RES.075.190529.SP Board Vendor: SAMSUNG ELECTRONICS CO., LTD. Board Name:NP950SBE-K01US !!Kernel Information !!-- Kernel release:5.3.0-19-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.3.0-19-generic Library version:1.1.9 Utilities version: 1.1.9 !!Loaded ALSA modules !!--- snd_hda_intel !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0x604b118000 irq 177 !!PCI Soundcards installed in the system !!-- 00:1f.3 Multimedia audio controller: Intel Corporation Cannon Point-LP High Definition Audio Controller (rev 11) !!Advanced information - PCI Vendor/Device/Subsystem ID's !!--- 00:1f.3 0401: 8086:9dc8 (rev 11) DeviceName: Onboard - Sound !!HDA-Intel Codec information !!--- --startcollapse-- Codec: Realtek ALC298 Address: 0 AFG Function Id: 0x1 (unsol 1) Vendor Id: 0x10ec0298 Subsystem Id: 0x144dc812 Revision Id: 0x100103 No Modem Function Group found Default PCM: rates [0x60]: 44100 48000 bits [0xe]: 16 20 24 formats [0x1]: PCM Default Amp-In caps: N/A Default Amp-Out caps: N/A State of AFG node 0x01: Power states: D0 D1 D2 D3 D3cold CLKSTOP EPSS Power: setting=D0, actual=D0 GPIO: io=8, o=0, i=0, unsolicited=1, wake=0 IO[0]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[1]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[2]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[3]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[4]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[5]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[6]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[7]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 Node 0x02 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Headphone Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Device: name="ALC298 Analog", type="Audio", device=0 Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0 Amp-Out vals: [0x00 0x00] Converter: stream=1, channel=0 PCM: rates [0x60]: 44100 48000 bits [0xe]: 16 20 24 formats [0x1]: PCM Power states: D0 D1 D2 D3 EPSS Power: setting=D0, actual=D0 Node 0x03 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Speaker Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0 Amp-Out vals: [0x7f 0x7f] Converter: stream=1, channel=0 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin 1383 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Nov 6 06:20:08 2019 InstallationDate: Installed on 2019-11-03 (3 days ago)
[Kernel-packages] [Bug 1872984] Re: RTL8822BE [10ec:b822] network driver rtl_wifi crashes on boot in Focal Fossa 20.04 - 5.4.0-21-generic and mainline 5.7.0-050700rc1-generic
Hi, Feng Tested and the error still appears. I'm starting to think it has something to do with my laptop in particular. Dmesg attached. ** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872984/+attachment/5433059/+files/dmesg.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/1872984 Title: RTL8822BE [10ec:b822] network driver rtl_wifi crashes on boot in Focal Fossa 20.04 - 5.4.0-21-generic and mainline 5.7.0-050700rc1-generic Status in linux package in Ubuntu: Incomplete Bug description: RTL8822BE crashes after rtw_pci starts on boot after kernel update to 5.4.0-21 (fails to read DBI register -- see attached dmesg). Issue is still present on latest mainline kernel version 5.7.0-050700rc1-generic . [ 10.627501] rtw_pci :3a:00.0: start vif 5c:ea:1d:b6:17:11 on port 0 [ 10.714544] [ cut here ] [ 10.714545] failed to read DBI register, addr=0x0719 [ 10.714577] WARNING: CPU: 0 PID: 939 at drivers/net/wireless/realtek/rtw88/pci.c:1156 rtw_dbi_read8.constprop.0+0xaa/0xc0 [rtwpci] [ 10.714577] Modules linked in: (see attached dmesg) [ 10.714614] CPU: 0 PID: 939 Comm: wpa_supplicant Not tainted 5.7.0-050700rc1-generic #202004122032 [ 10.714614] Hardware name: LENOVO 81CU/LNVNB161216, BIOS 7KCN22WW(V1.03) 01/23/2018 [ 10.714616] RIP: 0010:rtw_dbi_read8.constprop.0+0xaa/0xc0 [rtwpci] [ 10.714617] Code: 03 00 00 48 8b 40 50 e8 24 c3 4b e0 5b 41 5c 41 88 45 00 31 c0 41 5d 5d c3 be 19 07 00 00 48 c7 c7 70 73 94 c0 e8 bb de 75 df <0f> 0b b8 fb ff ff ff 5b 41 5c 41 5d 5d c3 0f 1f 84 00 00 00 00 00 [ 10.714618] RSP: 0018:b466007e7880 EFLAGS: 00010282 [ 10.714618] RAX: RBX: RCX: 0007 [ 10.714619] RDX: 0007 RSI: 0092 RDI: 933cc9e19c80 [ 10.714619] RBP: b466007e7898 R08: 03d2 R09: 0004 [ 10.714620] R10: R11: 0001 R12: 933cbdf31ea0 [ 10.714620] R13: b466007e78af R14: 933cbdf35bc8 R15: [ 10.714622] FS: 7fbcedc6efc0() GS:933cc9e0() knlGS: [ 10.714622] CS: 0010 DS: ES: CR0: 80050033 [ 10.714623] CR2: 563278766000 CR3: 0002be7a4002 CR4: 003606f0 [ 10.714623] Call Trace: [ 10.714627] rtw_pci_link_ps+0x4e/0x90 [rtwpci] [ 10.714630] ? _raw_spin_unlock_bh+0x1e/0x20 [ 10.714637] rtw_leave_ips+0x1f/0x80 [rtw88] [ 10.714640] rtw_ops_config+0xa3/0xe0 [rtw88] [ 10.714658] ieee80211_hw_config+0x95/0x390 [mac80211] [ 10.714669] ieee80211_recalc_idle+0x27/0x30 [mac80211] [ 10.714679] __ieee80211_start_scan+0x334/0x750 [mac80211] [ 10.714688] ieee80211_request_scan+0x30/0x50 [mac80211] [ 10.714699] ieee80211_scan+0x5c/0xa0 [mac80211] [ 10.714719] nl80211_trigger_scan+0x59a/0x6c0 [cfg80211] [ 10.714722] genl_rcv_msg+0x1a8/0x470 [ 10.714724] ? ep_poll_callback+0x2a0/0x2c0 [ 10.714725] ? genl_family_rcv_msg_attrs_parse+0x100/0x100 [ 10.714726] netlink_rcv_skb+0x50/0x120 [ 10.714728] genl_rcv+0x29/0x40 [ 10.714729] netlink_unicast+0x1a8/0x250 [ 10.714730] netlink_sendmsg+0x233/0x460 [ 10.714739] ? _copy_from_user+0x31/0x60 [ 10.714750] sock_sendmsg+0x65/0x70 [ 10.714751] sys_sendmsg+0x212/0x280 [ 10.714752] ? copy_msghdr_from_user+0x5c/0x90 [ 10.714755] ? __check_object_size+0x4d/0x150 [ 10.714756] ___sys_sendmsg+0x81/0xc0 [ 10.714757] ? __check_object_size+0x4d/0x150 [ 10.714759] ? unix_ioctl+0x99/0x180 [ 10.714760] ? sock_getsockopt+0x198/0xc04 [ 10.714761] ? sock_do_ioctl+0x47/0x140 [ 10.714763] ? __cgroup_bpf_run_filter_setsockopt+0xae/0x2c0 [ 10.714765] ? _cond_resched+0x19/0x30 [ 10.714767] ? aa_sk_perm+0x43/0x1b0 [ 10.714768] __sys_sendmsg+0x5c/0xa0 [ 10.714770] __x64_sys_sendmsg+0x1f/0x30 [ 10.714772] do_syscall_64+0x57/0x1b0 [ 10.714773] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 10.714774] RIP: 0033:0x7fbcedffb5b7 [ 10.714775] Code: 64 89 02 48 c7 c0 ff ff ff ff eb bb 0f 1f 80 00 00 00 00 f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 2e 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 51 c3 48 83 ec 28 89 54 24 1c 48 89 74 24 10 [ 10.714776] RSP: 002b:7fff88e22288 EFLAGS: 0246 ORIG_RAX: 002e [ 10.714777] RAX: ffda RBX: 5632787355d0 RCX: 7fbcedffb5b7 [ 10.714777] RDX: RSI: 7fff88e222c0 RDI: 0006 [ 10.714778] RBP: 563278761380 R08: 0004 R09: 563278761380 [ 10.714778] R10: 7fff88e22394 R11: 0246 R12: 5632787354e0 [ 10.714779] R13: 7fff88e222c0 R14: 7fff88e22394 R15: 563278766710 [ 10.714780]
[Kernel-packages] [Bug 1894329] Re: ZFS revert from grub menu not working.
Patch for Focal.
** Patch added: "zfs-linux_0.8.3-1ubuntu12.4_0.8.3-1ubuntu12.5.debdiff"
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1894329/+attachment/5433047/+files/zfs-linux_0.8.3-1ubuntu12.4_0.8.3-1ubuntu12.5.debdiff
--
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/1894329
Title:
ZFS revert from grub menu not working.
Status in coreutils package in Ubuntu:
Incomplete
Status in zfs-linux package in Ubuntu:
In Progress
Status in coreutils source package in Focal:
Incomplete
Status in zfs-linux source package in Focal:
Triaged
Status in coreutils source package in Groovy:
Incomplete
Status in zfs-linux source package in Groovy:
Triaged
Bug description:
@coreutils maintainers, any idea why dd is being flagged as having an
executable stack?
When I try to revert to a previous state from the grub menu, the boot
fails. The system drops me to a repair modus.
zfs-mount-generator fails with the message:
couldn't ensure boot: Mounted clone bootFS dataset created by initramfs
doesn't have a valid _suffix (at least .*_): \"rpool/ROOT/ubuntu_\"".
After a reboot I have an extra clone called "rpool/ROOT/ubuntu_", indeed
without a suffix.
After a little investigation I found the problem in
/usr/share/initramfs-tools/scripts/zfs at the end in function
uid()
{
dd if=/dev/urandom of=/dev/stdout bs=1 count=100 2>/dev/null | tr -dc
'a-z0-9' | cut -c-6
}, the dd command fails during boot with the message "process 'dd' started
with executable stack.
After this an empty uid is returned which explains the dataset without a
proper suffix.
Replacing the function with:
uid()
{
grep -a -m10 -E "\*" /dev/urandom 2>/dev/null | tr -dc 'a-z0-9' | cut -c-6
}
fixes the problem.
Ubuntu version is:
Description:Ubuntu Groovy Gorilla (development branch)
Release:20.10
zfs-initramfs version is:
0.8.4-1ubuntu11
With regards,
Usarin Heininga
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: zfs-initramfs 0.8.4-1ubuntu11
ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
Uname: Linux 5.8.0-18-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu45
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Fri Sep 4 20:23:44 2020
InstallationDate: Installed on 2020-09-02 (2 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200831)
ProcEnviron:
LANGUAGE=
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=nl_NL.UTF-8
SHELL=/bin/bash
SourcePackage: zfs-linux
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1894329/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903750] [NEW] Xenial update: v4.4.242 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v4.4.242 upstream stable release from git://git.kernel.org/ SUNRPC: ECONNREFUSED should cause a rebind. scripts/setlocalversion: make git describe output more reliable ravb: Fix bit fields checking in ravb_hwtstamp_get() tipc: fix memory leak caused by tipc_buf_append() mtd: lpddr: Fix bad logic in print_drs_error ata: sata_rcar: Fix DMA boundary mask fscrypt: return -EXDEV for incompatible rename or link into encrypted dir f2fs crypto: avoid unneeded memory allocation in ->readdir powerpc/powernv/smp: Fix spurious DBG() warning sparc64: remove mm_cpumask clearing to fix kthread_use_mm race f2fs: fix to check segment boundary during SIT page readahead um: change sigio_spinlock to a mutex xfs: fix realtime bitmap/summary file truncation when growing rt volume video: fbdev: pvr2fb: initialize variables ath10k: fix VHT NSS calculation when STBC is enabled mmc: via-sdmmc: Fix data race bug printk: reduce LOG_BUF_SHIFT range for H8300 kgdb: Make "kgdbcon" work properly with "kgdb_earlycon" USB: adutux: fix debugging drivers/net/wan/hdlc_fr: Correctly handle special skb->protocol values power: supply: test_power: add missing newlines when printing parameters by sysfs md/bitmap: md_bitmap_get_counter returns wrong blocks clk: ti: clockdomain: fix static checker warning net: 9p: initialize sun_server.sun_path to have addr's value only when addr is valid drivers: watchdog: rdc321x_wdt: Fix race condition bugs ext4: Detect already used quota file early gfs2: add validation checks for size of superblock memory: emif: Remove bogus debugfs error handling ARM: dts: s5pv210: move PMU node out of clock controller ARM: dts: s5pv210: remove dedicated 'audio-subsystem' node md/raid5: fix oops during stripe resizing leds: bcm6328, bcm6358: use devres LED registering function NFS: fix nfs_path in case of a rename retry ACPI / extlog: Check for RDMSR failure ACPI: video: use ACPI backlight for HP 635 Notebook acpi-cpufreq: Honor _PSD table setting on new AMD CPUs w1: mxc_w1: Fix timeout resolution problem leading to bus error scsi: mptfusion: Fix null pointer dereferences in mptscsih_remove() btrfs: reschedule if necessary when logging directory items vt: keyboard, simplify vt_kdgkbsent vt: keyboard, extend func_buf_lock to readers dmaengine: dma-jz4780: Fix race in jz4780_dma_tx_status iio:gyro:itg3200: Fix timestamp alignment and prevent data leak. powerpc/powernv/elog: Fix race while processing OPAL error log event. ubifs: dent: Fix some potential memory leaks while iterating entries ubi: check kthread_should_stop() after the setting of task state ia64: fix build error with !COREDUMP ceph: promote to unsigned long long before shifting libceph: clear con->out_msg on Policy::stateful_server faults 9P: Cast to loff_t before multiplying ring-buffer: Return 0 on success from ring_buffer_resize() vringh: fix __vringh_iov() when riov and wiov are different tty: make FONTX ioctl use the tty pointer they were actually passed arm64: berlin: Select DW_APB_TIMER_OF cachefiles: Handle readpage error correctly hil/parisc: Disable HIL driver when it gets stuck ARM: samsung: fix PM debug build with DEBUG_LL but !MMU ARM: s3c24xx: fix missing system reset device property: Keep secondary firmware node secondary by type device property: Don't clear secondary pointer for shared primary firmware node staging: comedi: cb_pcidas: Allow 2-channel commands for AO subdevice Revert "Revert "XEN uses irqdesc::irq_data_common::handler_data to store a per interrupt XEN data pointer which contains XEN specific information."" xen/events: don't use chip_data for legacy IRQs tipc: fix use-after-free in tipc_bcast_get_mode gianfar: Replace skb_realloc_headroom with skb_cow_head for PTP gianfar: Account for Tx PTP timestamp in the skb headroom Fonts: Replace discarded const qualifier ALSA: usb-audio: Add implicit feedback quirk for Qu-16 ftrace: Fix recursion check for NMI test ftrace: Handle tracing when switching between context ARM: dts: sun4i-a10: fix cpu_alert temperature x86/kexec: Use up-to-dated screen_info copy to fill boot params of: Fix reserved-memory overlap detection scsi: core: Don't start concurrent async scan on same host vsock: use ns_capable_noaudit() on socket create vt: Disable KD_FONT_OP_COPY fork: fix copy_process(CLONE_PARENT) race with the exiting ->real_parent serial: 8250_mtk: Fix uart_get_baud_rate warning serial: txx9: add missing platform_driver_unregister() on error in serial_txx9_init USB: serial: cyberjack: fix write-URB completion race USB:
[Kernel-packages] [Bug 1903048] Re: [SRU] Bluetooth won't activate on the pi 400
Test case works perfectly on the Pi400. -- 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/1903048 Title: [SRU] Bluetooth won't activate on the pi 400 Status in bluez package in Ubuntu: Fix Committed Bug description: [Impact] Without these patches, Bluetooth is inoperable on the recently released Raspberry Pi 400. [Test Case] * Boot the Ubuntu Desktop for Pi image on a Pi 400. * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is not enabled and attempting to activate it fails * sudo add-apt-repository ppa:waveform/pi-bluetooth * sudo apt update * sudo apt install bluez * sudo reboot * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is active and that Bluetooth devices (e.g. mice, mobile phones, headphones, etc.) can connect and operate correctly [Regression Potential] Extremely low (on groovy in particular, this has the same version of bluez as hirsute). The only significant risk is to non-Pi platforms or dongles which also use the Broadcom 43xx (or Cypress 305) chips for Bluetooth which might be inadvertently affected by these patches. [Original Description] The new Pi 400 has a slightly different Wifi/BT chip to the Pi4. Whilst wifi works happily, Bluetooth fails to operate. This doesn't appear to be an issue with either the firmware (the latest versions from upstream Raspbian have been tried), or the kernel (a known-good raspi kernel has been tested under Ubuntu), but with Bluez itself. Specifically, tracing the initialization with btmon on Raspbian and Ubuntu, the stack consistently fails when attempting to "Set Default PHY" on the latter. Curiously, under Ubuntu the adapter also appears to lack a MAC address. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1903048/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903048] Re: [SRU] Bluetooth won't activate on the pi 400
Thanks guys for all the work. -- 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/1903048 Title: [SRU] Bluetooth won't activate on the pi 400 Status in bluez package in Ubuntu: Fix Committed Bug description: [Impact] Without these patches, Bluetooth is inoperable on the recently released Raspberry Pi 400. [Test Case] * Boot the Ubuntu Desktop for Pi image on a Pi 400. * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is not enabled and attempting to activate it fails * sudo add-apt-repository ppa:waveform/pi-bluetooth * sudo apt update * sudo apt install bluez * sudo reboot * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is active and that Bluetooth devices (e.g. mice, mobile phones, headphones, etc.) can connect and operate correctly [Regression Potential] Extremely low (on groovy in particular, this has the same version of bluez as hirsute). The only significant risk is to non-Pi platforms or dongles which also use the Broadcom 43xx (or Cypress 305) chips for Bluetooth which might be inadvertently affected by these patches. [Original Description] The new Pi 400 has a slightly different Wifi/BT chip to the Pi4. Whilst wifi works happily, Bluetooth fails to operate. This doesn't appear to be an issue with either the firmware (the latest versions from upstream Raspbian have been tried), or the kernel (a known-good raspi kernel has been tested under Ubuntu), but with Bluez itself. Specifically, tracing the initialization with btmon on Raspbian and Ubuntu, the stack consistently fails when attempting to "Set Default PHY" on the latter. Curiously, under Ubuntu the adapter also appears to lack a MAC address. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1903048/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903543] Re: Block device scheduler should be multiqueue for spinning disks
@David Maybe this should be brought up in the next meeting. I don't think there's more that can be done about this from our side. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1903543 Title: Block device scheduler should be multiqueue for spinning disks Status in linux-gcp package in Ubuntu: Incomplete Bug description: On a GCE e2-medium instance running Groovy with a standard persistent disk, we see: $ cat /sys/block/sda/queue/rotational 1 $ cat /sys/block/sda/queue/scheduler [none] mq-deadline I'd expect the contents of /sys/block/sda/queue/scheduler to be: [mq-deadline] none --- $ lsb_release -rd Description:Ubuntu 20.10 Release:20.10 $ apt-cache policy linux-gcp linux-gcp: Installed: 5.8.0.1008.8 Candidate: 5.8.0.1008.8 Version table: *** 5.8.0.1008.8 500 500 http://us-central1.gce.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1903543/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851518] Re: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones
Re: Metallic sound Forgot to mention - it seems to happen only on the speakers, not on the headphones. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851518 Title: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones Status in linux package in Ubuntu: Fix Released Bug description: I've been googling this issue for 10's of hours and tried many things. Relase of Ubuntu: 19.10 Expected outcome: Music plays on the internal speakers and headphones. Actual outcome: I can barely hear audio using headphones with volume turned up to 150%. Absolutely nothing comes out of the speakers. (The speakers sound great under Windows 10.) Complete alsa-info output is attached, but here are some snippets: !!DMI Information !!--- Manufacturer: SAMSUNG ELECTRONICS CO., LTD. Product Name: 950SBE/951SBE Product Version: P06RES Firmware Version: P06RES.075.190529.SP Board Vendor: SAMSUNG ELECTRONICS CO., LTD. Board Name:NP950SBE-K01US !!Kernel Information !!-- Kernel release:5.3.0-19-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.3.0-19-generic Library version:1.1.9 Utilities version: 1.1.9 !!Loaded ALSA modules !!--- snd_hda_intel !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0x604b118000 irq 177 !!PCI Soundcards installed in the system !!-- 00:1f.3 Multimedia audio controller: Intel Corporation Cannon Point-LP High Definition Audio Controller (rev 11) !!Advanced information - PCI Vendor/Device/Subsystem ID's !!--- 00:1f.3 0401: 8086:9dc8 (rev 11) DeviceName: Onboard - Sound !!HDA-Intel Codec information !!--- --startcollapse-- Codec: Realtek ALC298 Address: 0 AFG Function Id: 0x1 (unsol 1) Vendor Id: 0x10ec0298 Subsystem Id: 0x144dc812 Revision Id: 0x100103 No Modem Function Group found Default PCM: rates [0x60]: 44100 48000 bits [0xe]: 16 20 24 formats [0x1]: PCM Default Amp-In caps: N/A Default Amp-Out caps: N/A State of AFG node 0x01: Power states: D0 D1 D2 D3 D3cold CLKSTOP EPSS Power: setting=D0, actual=D0 GPIO: io=8, o=0, i=0, unsolicited=1, wake=0 IO[0]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[1]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[2]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[3]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[4]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[5]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[6]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[7]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 Node 0x02 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Headphone Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Device: name="ALC298 Analog", type="Audio", device=0 Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0 Amp-Out vals: [0x00 0x00] Converter: stream=1, channel=0 PCM: rates [0x60]: 44100 48000 bits [0xe]: 16 20 24 formats [0x1]: PCM Power states: D0 D1 D2 D3 EPSS Power: setting=D0, actual=D0 Node 0x03 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Speaker Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0 Amp-Out vals: [0x7f 0x7f] Converter: stream=1, channel=0 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin 1383 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Nov 6 06:20:08 2019 InstallationDate: Installed on 2019-11-03 (3 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback
[Kernel-packages] [Bug 1903770] 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/1903770 Title: middle mouse button does not work Logitech M185 Status in linux package in Ubuntu: Confirmed Bug description: My mouse works ok with movement, left and right click and scrolling. However, the middle mouse click, ie pressing down on the scroll wheel does not work. I am positive this has worked with previous ubuntu versions with this mouse on this laptop. I'll attach the output from evtest - but I'm not sure how helpful that is, it shows all events that work, but shows nothing when I press the middle button. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-26-generic 5.8.0-26.27 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: peter 861 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 10 22:01:13 2020 InstallationDate: Installed on 2020-10-13 (27 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930) MachineType: HP HP Pavilion x2 Detachable ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-26-generic root=UUID=aad7498f-7086-4036-b6dd-8bceef953d46 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-26-generic N/A linux-backports-modules-5.8.0-26-generic N/A linux-firmware1.190 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/14/2016 dmi.bios.release: 15.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.13 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8181 dmi.board.vendor: HP dmi.board.version: 42.25 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 42.25 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.13:bd03/14/2016:br15.13:efr42.25:svnHP:pnHPPavilionx2Detachable:pvr:rvnHP:rn8181:rvr42.25:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT dmi.product.name: HP Pavilion x2 Detachable dmi.product.sku: T9R01EA#ABD dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903770/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851518] Re: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones
One possibly important finding: The metallic sound happens with Chrome but not with Firefox, running the same youtube video. I googled and found that chrome is using ALSA, while FF is using Pulseaudio. Maybe that's the issue. Got no idea how to solve this tho. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851518 Title: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones Status in linux package in Ubuntu: Fix Released Bug description: I've been googling this issue for 10's of hours and tried many things. Relase of Ubuntu: 19.10 Expected outcome: Music plays on the internal speakers and headphones. Actual outcome: I can barely hear audio using headphones with volume turned up to 150%. Absolutely nothing comes out of the speakers. (The speakers sound great under Windows 10.) Complete alsa-info output is attached, but here are some snippets: !!DMI Information !!--- Manufacturer: SAMSUNG ELECTRONICS CO., LTD. Product Name: 950SBE/951SBE Product Version: P06RES Firmware Version: P06RES.075.190529.SP Board Vendor: SAMSUNG ELECTRONICS CO., LTD. Board Name:NP950SBE-K01US !!Kernel Information !!-- Kernel release:5.3.0-19-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.3.0-19-generic Library version:1.1.9 Utilities version: 1.1.9 !!Loaded ALSA modules !!--- snd_hda_intel !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0x604b118000 irq 177 !!PCI Soundcards installed in the system !!-- 00:1f.3 Multimedia audio controller: Intel Corporation Cannon Point-LP High Definition Audio Controller (rev 11) !!Advanced information - PCI Vendor/Device/Subsystem ID's !!--- 00:1f.3 0401: 8086:9dc8 (rev 11) DeviceName: Onboard - Sound !!HDA-Intel Codec information !!--- --startcollapse-- Codec: Realtek ALC298 Address: 0 AFG Function Id: 0x1 (unsol 1) Vendor Id: 0x10ec0298 Subsystem Id: 0x144dc812 Revision Id: 0x100103 No Modem Function Group found Default PCM: rates [0x60]: 44100 48000 bits [0xe]: 16 20 24 formats [0x1]: PCM Default Amp-In caps: N/A Default Amp-Out caps: N/A State of AFG node 0x01: Power states: D0 D1 D2 D3 D3cold CLKSTOP EPSS Power: setting=D0, actual=D0 GPIO: io=8, o=0, i=0, unsolicited=1, wake=0 IO[0]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[1]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[2]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[3]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[4]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[5]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[6]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[7]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 Node 0x02 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Headphone Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Device: name="ALC298 Analog", type="Audio", device=0 Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0 Amp-Out vals: [0x00 0x00] Converter: stream=1, channel=0 PCM: rates [0x60]: 44100 48000 bits [0xe]: 16 20 24 formats [0x1]: PCM Power states: D0 D1 D2 D3 EPSS Power: setting=D0, actual=D0 Node 0x03 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Speaker Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0 Amp-Out vals: [0x7f 0x7f] Converter: stream=1, channel=0 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin 1383 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Nov 6 06:20:08 2019 InstallationDate: Installed on 2019-11-03 (3 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: TERM=xterm-256color
[Kernel-packages] [Bug 1851518] Re: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones
Just FYI for anyone interested, The daemon is now working again. Looks like the last update of systemd caused the issue. Through another forum I found I was able to fix it by just running "sudo apt reinstall systemd" (which also fixed the broken battery indicator). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851518 Title: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones Status in linux package in Ubuntu: Fix Released Bug description: I've been googling this issue for 10's of hours and tried many things. Relase of Ubuntu: 19.10 Expected outcome: Music plays on the internal speakers and headphones. Actual outcome: I can barely hear audio using headphones with volume turned up to 150%. Absolutely nothing comes out of the speakers. (The speakers sound great under Windows 10.) Complete alsa-info output is attached, but here are some snippets: !!DMI Information !!--- Manufacturer: SAMSUNG ELECTRONICS CO., LTD. Product Name: 950SBE/951SBE Product Version: P06RES Firmware Version: P06RES.075.190529.SP Board Vendor: SAMSUNG ELECTRONICS CO., LTD. Board Name:NP950SBE-K01US !!Kernel Information !!-- Kernel release:5.3.0-19-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.3.0-19-generic Library version:1.1.9 Utilities version: 1.1.9 !!Loaded ALSA modules !!--- snd_hda_intel !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0x604b118000 irq 177 !!PCI Soundcards installed in the system !!-- 00:1f.3 Multimedia audio controller: Intel Corporation Cannon Point-LP High Definition Audio Controller (rev 11) !!Advanced information - PCI Vendor/Device/Subsystem ID's !!--- 00:1f.3 0401: 8086:9dc8 (rev 11) DeviceName: Onboard - Sound !!HDA-Intel Codec information !!--- --startcollapse-- Codec: Realtek ALC298 Address: 0 AFG Function Id: 0x1 (unsol 1) Vendor Id: 0x10ec0298 Subsystem Id: 0x144dc812 Revision Id: 0x100103 No Modem Function Group found Default PCM: rates [0x60]: 44100 48000 bits [0xe]: 16 20 24 formats [0x1]: PCM Default Amp-In caps: N/A Default Amp-Out caps: N/A State of AFG node 0x01: Power states: D0 D1 D2 D3 D3cold CLKSTOP EPSS Power: setting=D0, actual=D0 GPIO: io=8, o=0, i=0, unsolicited=1, wake=0 IO[0]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[1]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[2]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[3]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[4]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[5]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[6]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[7]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 Node 0x02 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Headphone Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Device: name="ALC298 Analog", type="Audio", device=0 Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0 Amp-Out vals: [0x00 0x00] Converter: stream=1, channel=0 PCM: rates [0x60]: 44100 48000 bits [0xe]: 16 20 24 formats [0x1]: PCM Power states: D0 D1 D2 D3 EPSS Power: setting=D0, actual=D0 Node 0x03 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Speaker Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0 Amp-Out vals: [0x7f 0x7f] Converter: stream=1, channel=0 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin 1383 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Nov 6 06:20:08 2019 InstallationDate: Installed on 2019-11-03 (3 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: TERM=xterm-256color
[Kernel-packages] [Bug 1851518] Re: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones
Yeah, thanks a lot, it actually does work on the FLEX :) I misread post #90 and tried only the verbs listed instead of the entire script. Using the full attached script it works fine now, on MInt 20 (Kernel 5.4.0-52) I tried the same verbs on the latest Manjaro, slightly newer Kernel 5.4.72. It works there too, however the sound is quite metallic. Any way to fix the metallic sound? When will this fix be implemented in linux out of the box, rather than having to perform all of these steps to get the speakers to work? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851518 Title: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones Status in linux package in Ubuntu: Fix Released Bug description: I've been googling this issue for 10's of hours and tried many things. Relase of Ubuntu: 19.10 Expected outcome: Music plays on the internal speakers and headphones. Actual outcome: I can barely hear audio using headphones with volume turned up to 150%. Absolutely nothing comes out of the speakers. (The speakers sound great under Windows 10.) Complete alsa-info output is attached, but here are some snippets: !!DMI Information !!--- Manufacturer: SAMSUNG ELECTRONICS CO., LTD. Product Name: 950SBE/951SBE Product Version: P06RES Firmware Version: P06RES.075.190529.SP Board Vendor: SAMSUNG ELECTRONICS CO., LTD. Board Name:NP950SBE-K01US !!Kernel Information !!-- Kernel release:5.3.0-19-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.3.0-19-generic Library version:1.1.9 Utilities version: 1.1.9 !!Loaded ALSA modules !!--- snd_hda_intel !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0x604b118000 irq 177 !!PCI Soundcards installed in the system !!-- 00:1f.3 Multimedia audio controller: Intel Corporation Cannon Point-LP High Definition Audio Controller (rev 11) !!Advanced information - PCI Vendor/Device/Subsystem ID's !!--- 00:1f.3 0401: 8086:9dc8 (rev 11) DeviceName: Onboard - Sound !!HDA-Intel Codec information !!--- --startcollapse-- Codec: Realtek ALC298 Address: 0 AFG Function Id: 0x1 (unsol 1) Vendor Id: 0x10ec0298 Subsystem Id: 0x144dc812 Revision Id: 0x100103 No Modem Function Group found Default PCM: rates [0x60]: 44100 48000 bits [0xe]: 16 20 24 formats [0x1]: PCM Default Amp-In caps: N/A Default Amp-Out caps: N/A State of AFG node 0x01: Power states: D0 D1 D2 D3 D3cold CLKSTOP EPSS Power: setting=D0, actual=D0 GPIO: io=8, o=0, i=0, unsolicited=1, wake=0 IO[0]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[1]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[2]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[3]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[4]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[5]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[6]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[7]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 Node 0x02 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Headphone Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Device: name="ALC298 Analog", type="Audio", device=0 Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0 Amp-Out vals: [0x00 0x00] Converter: stream=1, channel=0 PCM: rates [0x60]: 44100 48000 bits [0xe]: 16 20 24 formats [0x1]: PCM Power states: D0 D1 D2 D3 EPSS Power: setting=D0, actual=D0 Node 0x03 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Speaker Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0 Amp-Out vals: [0x7f 0x7f] Converter: stream=1, channel=0 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin 1383 F pulseaudio
[Kernel-packages] [Bug 1903388] Re: Failure to write to NVMe disk soon after boot (APST-related)
Another update regarding the the system slowdown. It seems it was caused by starting "Ubuntu on Wayland" from the main screen. (had to do so previously to be able to login). So it seems unrelated to the APST issue. Should I repeat the tests with different latency again? How dangerous is it for me to manually change from Kernel 4.15.18 to the suggested v5.10-rc3? As this is my workstation, I am reluctant on breaking my system entirely. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1903388 Title: Failure to write to NVMe disk soon after boot (APST-related) Status in linux package in Ubuntu: Incomplete Bug description: Hi all, This one is similar to #1805816 and #1678184 (one was fixed, other closed). Symptoms: During regular use, system starts failing after 10m - 1hr after start. Icons start disappearing, writing to disk fails. In-memory operations still work for a while (switching windows, streaming video calls, typing). After some time the entire system crashes, with a Black Screen Of Death constantly looping: --- EXT4-fs error (device nvme0n1p5) ext4_find_entry:1455: inode #4594258: comm gmain: reading directory lblock 0 [... same repeats for 8 times on average] systemd-journald[439]: Failed to write entry (9 items, 270 bytes), ignoring: Read-only file system [... repeats for 10 times on average] --- Probable causes: Updated both kernel and BIOS 2 days ago. Unable to determine, which one caused the change. Don't know how to determine which kernel and bios I was running before the update. Looks like APST issue, based on info from web and previous bug reports. Verification: Created a rudimentary bash script, writing to a file in a loop, incrementing timeout between two consecutive writes each time. Ran script using: - different nvme_core.default_ps_max_latency_us settings in GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=[0|200|5500]" - regular boot mode - logged in to account - on battery power With default_ps_max_latency_us NOT SET: writing FAILS between 57 and 70 seconds timeout between writes With default_ps_max_latency_us=5500: no write failure during 1hrs run With default_ps_max_latency_us=200: no write failure during 30m run With latency 0: no write failure during 10m run This suggests an APST issue. Machine: Lenovo Thinkpad T570 Disk: SAMSUNG MZVLB512HAJQ-000L7 512 GB (512110190592 bytes) Firmware: 3L2QEXA7 Serial#: S3TNNE0K119126 System: OS 1: Ubuntu 18.04.5 LTS Kernel: 4.15.0-122-generic #124-Ubuntu SMP Thu Oct 15 13:03:05 UTC 2020 x86_64 OS 2: Windows 7 (on a separate partition on same disk, dualbooted with grub). Actions taken: Successfully checked the partitions for errors by running "Check partition" and "Repair partition" in Disks utility in Ubuntu, running from a bootable USB. Starting in "recovery mode" yields an error (among other suspicious behavior): sd 0:0:0:0: Attached scsi generic sg0 type 0 sd 0:0:0:0: [sda] Attached SCSI removable Disk input: TPPS/2 IBM TrackPoint as /devices/platform/18042/serio1/serio2/input/input nvme nvme0: controller is down; will reset: CSTS=0x, PCI_STATUS=0x10 nvme :40:00.0: enabling device ( -> 0002) nvme nvme0: Removing after probe failure status: -19 nvme0n1: detected capacity change from 512110190592 to 0 print_req_error: I/O error, dev nvme0n1, sector 1000215040 nvme nvme0: failed to set APST feature (-19) Waiting for suspend/resume device ... Begin: Running /scripts/local-block No devices listed in conf file were found. No devices listed in conf file were found. [repeats] Without nvme_core.default_ps_max_latency_us set: writing fails between cca. 57 - 70, on battery. With nvme_core.default_ps_max_latency_us=5500: FIXES THE PROBLEM. With nvme_core.default_ps_max_latency_us=200: FIXES THE PROBLEM. With nvme_core.default_ps_max_latency_us=0: FIXES THE PROBLEM. Previous behavior on same machine: Same OS, with a previous Kernel has been running perfectly fine for the last year, "on high revs" (it's a development machine). Often running on battery alone. sleep and wakeup without issues. It is running Windows 7 (dual booted) without issues. Misc info: To test different settings, did 'sudo nano /etc/default/grub' with each of these settings: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" # GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=5500" # GRUB_CMDLINE_LINUX_DEFAULT="quiet splash
[Kernel-packages] [Bug 1886937] Re: limited hardware support AMD 4700u HP Envy x360 13-ay003nd
>Suspend/Hibernate: >screen goes off, nothing else happens. After user interaction, screen turns >on. Login screen is >shown. Sometimes screen does not turn on: physical reboot >required. >kernel upgrade to 5.8rc3 or 5.8rc4 has no effect. I wanted to chime in that I also have this issue on my Acer Swift 3 with 4700U. It also only appears to support s2idle and I have no options in my BIOS to adjust regarding this. I have tried this with even kernel 5.10rc3 and no fix has come just yet. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1886937 Title: limited hardware support AMD 4700u HP Envy x360 13-ay003nd Status in linux package in Ubuntu: Confirmed Bug description: Suspend/Hibernate: screen goes off, nothing else happens. After user interaction, screen turns on. Login screen is shown. Sometimes screen does not turn on: physical reboot required. kernel upgrade to 5.8rc3 or 5.8rc4 has no effect. Brightness: Adjusting brightness has no effect, nightmode has no effect. Partial solution: kernel upgrade 5.8rc3 or 5.8rc4 solves this partially, brightness can be adjusted and nightmode works But after a reboot brightness is always at max. Also brightness cannot be lowered as much as normally expected. CPU & fan: CPU is always high, 5.8rc3 solves this partially, fan is still always on and quite high (after clean Ubuntu install, nothing configured or installed). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: asterix 881 F pulseaudio /dev/snd/controlC1: asterix 881 F pulseaudio /dev/snd/controlC0: asterix 881 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Thu Jul 9 12:21:02 2020 InstallationDate: Installed on 2020-07-09 (0 days ago) InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: HP HP ENVY x360 Convertible 13-ay0xxx ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=e2b48a5b-5ae8-41c4-a6d0-7eb17bb02dd3 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/07/2020 dmi.bios.vendor: Insyde dmi.bios.version: F.06 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 876E dmi.board.vendor: HP dmi.board.version: 12.30 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.06:bd05/07/2020:svnHP:pnHPENVYx360Convertible13-ay0xxx:pvrType1ProductConfigId:rvnHP:rn876E:rvr12.30:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY x360 Convertible 13-ay0xxx dmi.product.sku: 1D5H9EA#ABH dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886937/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851518] Re: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones
PLease disregard my last comment (#112). It happens in FF too, but on other websites. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851518 Title: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones Status in linux package in Ubuntu: Fix Released Bug description: I've been googling this issue for 10's of hours and tried many things. Relase of Ubuntu: 19.10 Expected outcome: Music plays on the internal speakers and headphones. Actual outcome: I can barely hear audio using headphones with volume turned up to 150%. Absolutely nothing comes out of the speakers. (The speakers sound great under Windows 10.) Complete alsa-info output is attached, but here are some snippets: !!DMI Information !!--- Manufacturer: SAMSUNG ELECTRONICS CO., LTD. Product Name: 950SBE/951SBE Product Version: P06RES Firmware Version: P06RES.075.190529.SP Board Vendor: SAMSUNG ELECTRONICS CO., LTD. Board Name:NP950SBE-K01US !!Kernel Information !!-- Kernel release:5.3.0-19-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.3.0-19-generic Library version:1.1.9 Utilities version: 1.1.9 !!Loaded ALSA modules !!--- snd_hda_intel !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0x604b118000 irq 177 !!PCI Soundcards installed in the system !!-- 00:1f.3 Multimedia audio controller: Intel Corporation Cannon Point-LP High Definition Audio Controller (rev 11) !!Advanced information - PCI Vendor/Device/Subsystem ID's !!--- 00:1f.3 0401: 8086:9dc8 (rev 11) DeviceName: Onboard - Sound !!HDA-Intel Codec information !!--- --startcollapse-- Codec: Realtek ALC298 Address: 0 AFG Function Id: 0x1 (unsol 1) Vendor Id: 0x10ec0298 Subsystem Id: 0x144dc812 Revision Id: 0x100103 No Modem Function Group found Default PCM: rates [0x60]: 44100 48000 bits [0xe]: 16 20 24 formats [0x1]: PCM Default Amp-In caps: N/A Default Amp-Out caps: N/A State of AFG node 0x01: Power states: D0 D1 D2 D3 D3cold CLKSTOP EPSS Power: setting=D0, actual=D0 GPIO: io=8, o=0, i=0, unsolicited=1, wake=0 IO[0]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[1]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[2]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[3]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[4]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[5]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[6]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[7]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 Node 0x02 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Headphone Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Device: name="ALC298 Analog", type="Audio", device=0 Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0 Amp-Out vals: [0x00 0x00] Converter: stream=1, channel=0 PCM: rates [0x60]: 44100 48000 bits [0xe]: 16 20 24 formats [0x1]: PCM Power states: D0 D1 D2 D3 EPSS Power: setting=D0, actual=D0 Node 0x03 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Speaker Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0 Amp-Out vals: [0x7f 0x7f] Converter: stream=1, channel=0 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin 1383 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Nov 6 06:20:08 2019 InstallationDate: Installed on 2019-11-03 (3 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through
[Kernel-packages] [Bug 1903048] Re: [SRU] Bluetooth won't activate on the pi 400
** Also affects: bluez (Ubuntu Hirsute) Importance: High Assignee: Dave Jones (waveform) Status: Fix Committed -- 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/1903048 Title: [SRU] Bluetooth won't activate on the pi 400 Status in bluez package in Ubuntu: Fix Committed Status in bluez source package in Hirsute: Fix Committed Bug description: [Impact] Without these patches, Bluetooth is inoperable on the recently released Raspberry Pi 400. [Test Case] * Boot the Ubuntu Desktop for Pi image on a Pi 400. * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is not enabled and attempting to activate it fails * sudo add-apt-repository ppa:waveform/pi-bluetooth * sudo apt update * sudo apt install bluez * sudo reboot * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is active and that Bluetooth devices (e.g. mice, mobile phones, headphones, etc.) can connect and operate correctly [Regression Potential] Extremely low (on groovy in particular, this has the same version of bluez as hirsute). The only significant risk is to non-Pi platforms or dongles which also use the Broadcom 43xx (or Cypress 305) chips for Bluetooth which might be inadvertently affected by these patches. [Original Description] The new Pi 400 has a slightly different Wifi/BT chip to the Pi4. Whilst wifi works happily, Bluetooth fails to operate. This doesn't appear to be an issue with either the firmware (the latest versions from upstream Raspbian have been tried), or the kernel (a known-good raspi kernel has been tested under Ubuntu), but with Bluez itself. Specifically, tracing the initialization with btmon on Raspbian and Ubuntu, the stack consistently fails when attempting to "Set Default PHY" on the latter. Curiously, under Ubuntu the adapter also appears to lack a MAC address. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1903048/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851518] Re: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones
Decided to do more trial and error tests. I tried multiple amd64 kerels from https://kernel.ubuntu.com/~kernel-ppa/mainline/ It seems that all kernels I tried produce metallic audio, I believe you can easily reproduce this by trying them. Even the 5.4.52-050452.202007160732 kernel produced metallic sound, while the official Mint 5.4.0-52 kernel produces clean audio. Official Mint kernel 5.8.0-28 also produces clean audio. Any thoughts? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851518 Title: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones Status in linux package in Ubuntu: Fix Released Bug description: I've been googling this issue for 10's of hours and tried many things. Relase of Ubuntu: 19.10 Expected outcome: Music plays on the internal speakers and headphones. Actual outcome: I can barely hear audio using headphones with volume turned up to 150%. Absolutely nothing comes out of the speakers. (The speakers sound great under Windows 10.) Complete alsa-info output is attached, but here are some snippets: !!DMI Information !!--- Manufacturer: SAMSUNG ELECTRONICS CO., LTD. Product Name: 950SBE/951SBE Product Version: P06RES Firmware Version: P06RES.075.190529.SP Board Vendor: SAMSUNG ELECTRONICS CO., LTD. Board Name:NP950SBE-K01US !!Kernel Information !!-- Kernel release:5.3.0-19-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.3.0-19-generic Library version:1.1.9 Utilities version: 1.1.9 !!Loaded ALSA modules !!--- snd_hda_intel !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0x604b118000 irq 177 !!PCI Soundcards installed in the system !!-- 00:1f.3 Multimedia audio controller: Intel Corporation Cannon Point-LP High Definition Audio Controller (rev 11) !!Advanced information - PCI Vendor/Device/Subsystem ID's !!--- 00:1f.3 0401: 8086:9dc8 (rev 11) DeviceName: Onboard - Sound !!HDA-Intel Codec information !!--- --startcollapse-- Codec: Realtek ALC298 Address: 0 AFG Function Id: 0x1 (unsol 1) Vendor Id: 0x10ec0298 Subsystem Id: 0x144dc812 Revision Id: 0x100103 No Modem Function Group found Default PCM: rates [0x60]: 44100 48000 bits [0xe]: 16 20 24 formats [0x1]: PCM Default Amp-In caps: N/A Default Amp-Out caps: N/A State of AFG node 0x01: Power states: D0 D1 D2 D3 D3cold CLKSTOP EPSS Power: setting=D0, actual=D0 GPIO: io=8, o=0, i=0, unsolicited=1, wake=0 IO[0]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[1]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[2]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[3]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[4]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[5]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[6]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[7]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 Node 0x02 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Headphone Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Device: name="ALC298 Analog", type="Audio", device=0 Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0 Amp-Out vals: [0x00 0x00] Converter: stream=1, channel=0 PCM: rates [0x60]: 44100 48000 bits [0xe]: 16 20 24 formats [0x1]: PCM Power states: D0 D1 D2 D3 EPSS Power: setting=D0, actual=D0 Node 0x03 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Speaker Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0 Amp-Out vals: [0x7f 0x7f] Converter: stream=1, channel=0 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin 1383 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Nov 6 06:20:08 2019 InstallationDate: Installed
[Kernel-packages] [Bug 1851518] Re: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones
To answer my own question - I suppose the ubuntu kernels are more optimized and have multiple fixes and drivers that the mainline/upstream kernels do not and that's why I get the metallic audio... I wonder what was fixed in Ubuntu's kernel to make this issue go away. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851518 Title: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones Status in linux package in Ubuntu: Fix Released Bug description: I've been googling this issue for 10's of hours and tried many things. Relase of Ubuntu: 19.10 Expected outcome: Music plays on the internal speakers and headphones. Actual outcome: I can barely hear audio using headphones with volume turned up to 150%. Absolutely nothing comes out of the speakers. (The speakers sound great under Windows 10.) Complete alsa-info output is attached, but here are some snippets: !!DMI Information !!--- Manufacturer: SAMSUNG ELECTRONICS CO., LTD. Product Name: 950SBE/951SBE Product Version: P06RES Firmware Version: P06RES.075.190529.SP Board Vendor: SAMSUNG ELECTRONICS CO., LTD. Board Name:NP950SBE-K01US !!Kernel Information !!-- Kernel release:5.3.0-19-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.3.0-19-generic Library version:1.1.9 Utilities version: 1.1.9 !!Loaded ALSA modules !!--- snd_hda_intel !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0x604b118000 irq 177 !!PCI Soundcards installed in the system !!-- 00:1f.3 Multimedia audio controller: Intel Corporation Cannon Point-LP High Definition Audio Controller (rev 11) !!Advanced information - PCI Vendor/Device/Subsystem ID's !!--- 00:1f.3 0401: 8086:9dc8 (rev 11) DeviceName: Onboard - Sound !!HDA-Intel Codec information !!--- --startcollapse-- Codec: Realtek ALC298 Address: 0 AFG Function Id: 0x1 (unsol 1) Vendor Id: 0x10ec0298 Subsystem Id: 0x144dc812 Revision Id: 0x100103 No Modem Function Group found Default PCM: rates [0x60]: 44100 48000 bits [0xe]: 16 20 24 formats [0x1]: PCM Default Amp-In caps: N/A Default Amp-Out caps: N/A State of AFG node 0x01: Power states: D0 D1 D2 D3 D3cold CLKSTOP EPSS Power: setting=D0, actual=D0 GPIO: io=8, o=0, i=0, unsolicited=1, wake=0 IO[0]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[1]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[2]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[3]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[4]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[5]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[6]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[7]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 Node 0x02 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Headphone Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Device: name="ALC298 Analog", type="Audio", device=0 Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0 Amp-Out vals: [0x00 0x00] Converter: stream=1, channel=0 PCM: rates [0x60]: 44100 48000 bits [0xe]: 16 20 24 formats [0x1]: PCM Power states: D0 D1 D2 D3 EPSS Power: setting=D0, actual=D0 Node 0x03 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Speaker Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0 Amp-Out vals: [0x7f 0x7f] Converter: stream=1, channel=0 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin 1383 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Nov 6 06:20:08 2019 InstallationDate: Installed on 2019-11-03 (3 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: TERM=xterm-256color
[Kernel-packages] [Bug 1903790] [NEW] SSD and Bluetooth conflict (Bluetooth doesn't work)
Public bug reported: Bluetooth stops working when I plug in the SSD. Bluetooth - Qualcomm Atheros Communications AR3011. SSD - OCZ Vector 180 256. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-28-generic 5.8.0-28.30 ProcVersionSignature: Ubuntu 5.8.0-28.30-generic 5.8.14 Uname: Linux 5.8.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: navycat1951 F pulseaudio /dev/snd/controlC0: navycat1951 F pulseaudio /dev/snd/controlC1: navycat1951 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Wed Nov 11 05:26:13 2020 InstallationDate: Installed on 2020-11-01 (9 days ago) InstallationMedia: Ubuntu-MATE 20.10 "Groovy Gorilla" - Release amd64 (20201022) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: BASE_BOARD_MANUFACTURER MODEL_NAME ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-28-generic root=UUID=54e2fb85-ed43-4ffd-a361-504ddf86a0de ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-28-generic N/A linux-backports-modules-5.8.0-28-generic N/A linux-firmware1.190.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/09/2018 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 150-SE-E789 dmi.board.vendor: EVGA dmi.board.version: Patsburg dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/09/2018:br4.6:svnBASE_BOARD_MANUFACTURER:pnMODEL_NAME:pvrBASE_BOARD_VERSION:rvnEVGA:rn150-SE-E789:rvrPatsburg: dmi.product.family: X86 AT dmi.product.name: MODEL_NAME dmi.product.sku: PROJECT_SUB_TAG dmi.product.version: BASE_BOARD_VERSION dmi.sys.vendor: BASE_BOARD_MANUFACTURER ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1903790 Title: SSD and Bluetooth conflict (Bluetooth doesn't work) Status in linux package in Ubuntu: New Bug description: Bluetooth stops working when I plug in the SSD. Bluetooth - Qualcomm Atheros Communications AR3011. SSD - OCZ Vector 180 256. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-28-generic 5.8.0-28.30 ProcVersionSignature: Ubuntu 5.8.0-28.30-generic 5.8.14 Uname: Linux 5.8.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: navycat1951 F pulseaudio /dev/snd/controlC0: navycat1951 F pulseaudio /dev/snd/controlC1: navycat1951 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Wed Nov 11 05:26:13 2020 InstallationDate: Installed on 2020-11-01 (9 days ago) InstallationMedia: Ubuntu-MATE 20.10 "Groovy Gorilla" - Release amd64 (20201022) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: BASE_BOARD_MANUFACTURER MODEL_NAME ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-28-generic root=UUID=54e2fb85-ed43-4ffd-a361-504ddf86a0de ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-28-generic N/A linux-backports-modules-5.8.0-28-generic N/A linux-firmware1.190.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/09/2018 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 150-SE-E789 dmi.board.vendor: EVGA dmi.board.version: Patsburg dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/09/2018:br4.6:svnBASE_BOARD_MANUFACTURER:pnMODEL_NAME:pvrBASE_BOARD_VERSION:rvnEVGA:rn150-SE-E789:rvrPatsburg: dmi.product.family: X86 AT dmi.product.name: MODEL_NAME dmi.product.sku: PROJECT_SUB_TAG dmi.product.version: BASE_BOARD_VERSION dmi.sys.vendor: BASE_BOARD_MANUFACTURER To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903790/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1900777] 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/1900777 Title: [amdgpu] Screen freeze with AMD/ATI Renoir Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: New Bug description: I upgraded to a Ryzen 7, 24-RAM ASUS computer because I thought that my 2-year-old Dell laptop was the problem. However, I froze during Zoom yesterday and during coding today after fresh-installing Ubuntu 20.04 on Sunday. I also froze mid-attempt to submit a bug report after the coding freeze. Any help is appreciated. Thanks. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Oct 20 17:38:31 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: amdgpu, 5.6.0.15-1098277, 5.4.0-51-generic, x86_64: installed amdgpu, 5.6.0.15-1098277, 5.4.0-52-generic, x86_64: installed rtl8821ce, 5.5.2.1, 5.4.0-51-generic, x86_64: installed rtl8821ce, 5.5.2.1, 5.4.0-52-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Within the last few days GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Renoir [1043:1352] InstallationDate: Installed on 2020-10-18 (2 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X513IA_M513IA ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=df36462b-f672-4f1c-a8b2-060922542daf ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X513IA.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X513IA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX513IA.300:bd06/05/2020:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX513IA_M513IA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX513IA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: VivoBook_ASUSLaptop X513IA_M513IA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 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/1900777/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851518] Re: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones
Re: Metallic audio Upgraded the kernel from 5.4.0-52 to 5.4.72 as I have on Manjaro. Result: Metallic audio. Booted again with 5.4.0-52 Result: Clean audio Conclusion: quite likely a kernel issue. How can we get this reported and fixed? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851518 Title: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones Status in linux package in Ubuntu: Fix Released Bug description: I've been googling this issue for 10's of hours and tried many things. Relase of Ubuntu: 19.10 Expected outcome: Music plays on the internal speakers and headphones. Actual outcome: I can barely hear audio using headphones with volume turned up to 150%. Absolutely nothing comes out of the speakers. (The speakers sound great under Windows 10.) Complete alsa-info output is attached, but here are some snippets: !!DMI Information !!--- Manufacturer: SAMSUNG ELECTRONICS CO., LTD. Product Name: 950SBE/951SBE Product Version: P06RES Firmware Version: P06RES.075.190529.SP Board Vendor: SAMSUNG ELECTRONICS CO., LTD. Board Name:NP950SBE-K01US !!Kernel Information !!-- Kernel release:5.3.0-19-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.3.0-19-generic Library version:1.1.9 Utilities version: 1.1.9 !!Loaded ALSA modules !!--- snd_hda_intel !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0x604b118000 irq 177 !!PCI Soundcards installed in the system !!-- 00:1f.3 Multimedia audio controller: Intel Corporation Cannon Point-LP High Definition Audio Controller (rev 11) !!Advanced information - PCI Vendor/Device/Subsystem ID's !!--- 00:1f.3 0401: 8086:9dc8 (rev 11) DeviceName: Onboard - Sound !!HDA-Intel Codec information !!--- --startcollapse-- Codec: Realtek ALC298 Address: 0 AFG Function Id: 0x1 (unsol 1) Vendor Id: 0x10ec0298 Subsystem Id: 0x144dc812 Revision Id: 0x100103 No Modem Function Group found Default PCM: rates [0x60]: 44100 48000 bits [0xe]: 16 20 24 formats [0x1]: PCM Default Amp-In caps: N/A Default Amp-Out caps: N/A State of AFG node 0x01: Power states: D0 D1 D2 D3 D3cold CLKSTOP EPSS Power: setting=D0, actual=D0 GPIO: io=8, o=0, i=0, unsolicited=1, wake=0 IO[0]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[1]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[2]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[3]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[4]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[5]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[6]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[7]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 Node 0x02 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Headphone Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Device: name="ALC298 Analog", type="Audio", device=0 Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0 Amp-Out vals: [0x00 0x00] Converter: stream=1, channel=0 PCM: rates [0x60]: 44100 48000 bits [0xe]: 16 20 24 formats [0x1]: PCM Power states: D0 D1 D2 D3 EPSS Power: setting=D0, actual=D0 Node 0x03 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Speaker Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0 Amp-Out vals: [0x7f 0x7f] Converter: stream=1, channel=0 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin 1383 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Nov 6 06:20:08 2019 InstallationDate: Installed on 2019-11-03 (3 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user)
[Kernel-packages] [Bug 1891773] Re: kcompactd0 and btrfs-transaction keep deadlocking with each other
Looks like the same issue kcompactd and btrfs-transaction locking up. Can not immediately reproduce, seemingly takes ~2weeks to appear. More problematic systems generally also have higher disk i/o, all btrfs. %Cpu0 : 3.8 us, 1.3 sy, 0.0 ni, 0.0 id, 94.9 wa, 0.0 hi, 0.0 si, 0.0 st %Cpu1 : 1.3 us, 2.6 sy, 0.0 ni, 96.1 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st %CPU PID TID TIME STAT RSS SZ F COMMAND 0.0 27 27 00:00:03 D 0 0 1 [kcompactd0] 0.0 618 618 00:03:04 D 0 0 1 [btrfs-transacti] cat /proc/27/stack [<0>] __lock_page+0xff/0x140 [<0>] migrate_pages+0x91f/0xb80 [<0>] compact_zone+0x681/0x950 [<0>] kcompactd_do_work+0xfe/0x2a0 [<0>] kcompactd+0x86/0x1c0 [<0>] kthread+0x121/0x140 [<0>] ret_from_fork+0x35/0x40 [<0>] 0x cat /proc/618/stack [<0>] lock_extent_buffer_for_io+0x100/0x2a0 [btrfs] [<0>] btree_write_cache_pages+0x1b8/0x420 [btrfs] [<0>] btree_writepages+0x5d/0x70 [btrfs] [<0>] do_writepages+0x4b/0xe0 [<0>] __filemap_fdatawrite_range+0xcf/0x100 [<0>] filemap_fdatawrite_range+0x13/0x20 [<0>] btrfs_write_marked_extents+0x68/0x140 [btrfs] [<0>] btrfs_write_and_wait_marked_extents.constprop.20+0x4f/0x90 [btrfs] [<0>] btrfs_commit_transaction+0x696/0x910 [btrfs] [<0>] transaction_kthread+0x18d/0x1b0 [btrfs] [<0>] kthread+0x121/0x140 [<0>] ret_from_fork+0x35/0x40 [<0>] 0x INFO: task kcompactd0:27 blocked for more than 120 seconds. Tainted: PE4.15.0-122-generic #124-Ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. kcompactd0 D027 2 0x9000 Call Trace: __schedule+0x24e/0x880 schedule+0x2c/0x80 io_schedule+0x16/0x40 __lock_page+0xff/0x140 ? page_cache_tree_insert+0xe0/0xe0 migrate_pages+0x91f/0xb80 ? __ClearPageMovable+0x10/0x10 ? isolate_freepages_block+0x3b0/0x3b0 compact_zone+0x681/0x950 kcompactd_do_work+0xfe/0x2a0 ? __switch_to_asm+0x35/0x70 ? __switch_to_asm+0x41/0x70 kcompactd+0x86/0x1c0 ? kcompactd+0x86/0x1c0 ? wait_woken+0x80/0x80 kthread+0x121/0x140 ? kcompactd_do_work+0x2a0/0x2a0 ? kthread_create_worker_on_cpu+0x70/0x70 ret_from_fork+0x35/0x40 ~ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1891773 Title: kcompactd0 and btrfs-transaction keep deadlocking with each other Status in linux package in Ubuntu: Confirmed Bug description: Example 1: [346911.187920] INFO: task kcompactd0:53 blocked for more than 120 seconds. [346911.187938] Not tainted 4.15.0-112-generic #113-Ubuntu [346911.187951] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [346911.187968] kcompactd0 D053 2 0x8000 [346911.187969] Call Trace: [346911.187973] __schedule+0x24e/0x880 [346911.187986] ? btree_releasepage+0x42/0x50 [btrfs] [346911.187987] schedule+0x2c/0x80 [346911.187988] io_schedule+0x16/0x40 [346911.187989] __lock_page+0xff/0x140 [346911.187990] ? page_cache_tree_insert+0xe0/0xe0 [346911.187992] migrate_pages+0x91f/0xb80 [346911.187993] ? __ClearPageMovable+0x10/0x10 [346911.187994] ? isolate_freepages_block+0x3b0/0x3b0 [346911.187995] compact_zone+0x681/0x950 [346911.187995] kcompactd_do_work+0xfe/0x2a0 [346911.187996] ? __switch_to_asm+0x35/0x70 [346911.187997] ? __switch_to_asm+0x41/0x70 [346911.187998] kcompactd+0x86/0x1c0 [346911.187999] ? kcompactd+0x86/0x1c0 [346911.188001] ? wait_woken+0x80/0x80 [346911.188002] kthread+0x121/0x140 [346911.188003] ? kcompactd_do_work+0x2a0/0x2a0 [346911.188003] ? kthread_create_worker_on_cpu+0x70/0x70 [346911.188004] ret_from_fork+0x35/0x40 [346911.188015] INFO: task btrfs-transacti:858 blocked for more than 120 seconds. [346911.188031] Not tainted 4.15.0-112-generic #113-Ubuntu [346911.188043] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [346911.188060] btrfs-transacti D0 858 2 0x8000 [346911.188061] Call Trace: [346911.188062] __schedule+0x24e/0x880 [346911.188063] ? bit_wait+0x60/0x60 [346911.188063] schedule+0x2c/0x80 [346911.188064] io_schedule+0x16/0x40 [346911.188065] bit_wait_io+0x11/0x60 [346911.188066] __wait_on_bit+0x4c/0x90 [346911.188066] ? bit_wait+0x60/0x60 [346911.188067] out_of_line_wait_on_bit+0x90/0xb0 [346911.188068] ? bit_waitqueue+0x40/0x40 [346911.188080] lock_extent_buffer_for_io+0x100/0x2a0 [btrfs] [346911.188090] btree_write_cache_pages+0x1b8/0x420 [btrfs] [346911.188092] ? native_sched_clock_from_tsc+0x30/0x70 [346911.188092] ? update_load_avg+0x423/0x780 [346911.188101] btree_writepages+0x5d/0x70 [btrfs] [346911.188102] do_writepages+0x4b/0xe0 [346911.188102] ? enqueue_task_fair+0xb6/0x300 [346911.188111] ? merge_state.part.47+0x44/0x130 [btrfs] [346911.188112] __filemap_fdatawrite_range+0xcf/0x100
[Kernel-packages] [Bug 1899866] Re: bcmwl-6.30.223.271+bdcom on kernel 5.9.0-050900-generic fails to install module
bcmwl has issues with every new kernel
i.e. https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1896348
so this isn't specific to any kernel, it's a deeper issue in the
package's build mechanism
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1899866
Title:
bcmwl-6.30.223.271+bdcom on kernel 5.9.0-050900-generic fails to
install module
Status in bcmwl package in Ubuntu:
New
Bug description:
When installing the 5.9 kernel with bcmwl6.30.223.271+bdcom package on
focal, the process fails to build the module.
bcmwl package: 6.30.223.271+bdcom-0ubuntu5
Below is the build log:
DKMS make.log for bcmwl-6.30.223.271+bdcom for kernel 5.9.0-050900-generic
(x86_64)
Mon 12 Oct 2020 02:45:20 PM MDT
make: Entering directory '/usr/src/linux-headers-5.9.0-050900-generic'
CFG80211 API is prefered for this kernel version
Using CFG80211 API
AR /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/built-in.a
CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.o
CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.o
CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_iw.o
CC [M]
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.o
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In
function ‘wl_pci_probe’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:780:2:
warning: this ‘if’ clause does not guard... [-Wmisleading-indentation]
780 | if ((val & 0xff00) != 0)
| ^~
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:782:3:
note: ...this statement, but the latter is misleadingly indented as if it were
guarded by the ‘if’
782 | bar1_size = pci_resource_len(pdev, 2);
| ^
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In
function ‘wl_ioctl’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:1654:6:
error: implicit declaration of function ‘segment_eq’
[-Werror=implicit-function-declaration]
1654 | if (segment_eq(get_fs(), KERNEL_DS))
| ^~
In file included from
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:40:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:
In function ‘wl_set_auth_type’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.h:52:5:
warning: this statement may fall through [-Wimplicit-fallthrough=]
52 | if (wl_dbg_level & WL_DBG_DBG) { \
| ^
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:816:3:
note: in expansion of macro ‘WL_DBG’
816 | WL_DBG(("network eap\n"));
| ^~
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:817:2:
note: here
817 | default:
| ^~~
cc1: some warnings being treated as errors
make[1]: *** [scripts/Makefile.build:283:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.o] Error 1
make[1]: *** Waiting for unfinished jobs
make: *** [Makefile:1784: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build] Error
2
make: Leaving directory '/usr/src/linux-headers-5.9.0-050900-generic'
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1899866/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1900777] Re: [amdgpu] Screen freeze
Wow, thanks. Finally success in comment #28 which shows amdgpu kernel errors and then: Nov 10 11:45:58 blaise-vivo gnome-shell[1908]: amdgpu: command stream overflowed Nov 10 11:45:58 blaise-vivo gnome-shell[1908]: GNOME Shell crashed with signal 11 So it sounds like the problem is originating in the kernel driver: amdgpu ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Summary changed: - [amdgpu] Screen freeze + [amdgpu] Screen freeze with AMD/ATI Renoir ** Changed in: xserver-xorg-video-amdgpu (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1900777 Title: [amdgpu] Screen freeze with AMD/ATI Renoir Status in linux package in Ubuntu: New Status in xserver-xorg-video-amdgpu package in Ubuntu: New Bug description: I upgraded to a Ryzen 7, 24-RAM ASUS computer because I thought that my 2-year-old Dell laptop was the problem. However, I froze during Zoom yesterday and during coding today after fresh-installing Ubuntu 20.04 on Sunday. I also froze mid-attempt to submit a bug report after the coding freeze. Any help is appreciated. Thanks. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Oct 20 17:38:31 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: amdgpu, 5.6.0.15-1098277, 5.4.0-51-generic, x86_64: installed amdgpu, 5.6.0.15-1098277, 5.4.0-52-generic, x86_64: installed rtl8821ce, 5.5.2.1, 5.4.0-51-generic, x86_64: installed rtl8821ce, 5.5.2.1, 5.4.0-52-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Within the last few days GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Renoir [1043:1352] InstallationDate: Installed on 2020-10-18 (2 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X513IA_M513IA ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=df36462b-f672-4f1c-a8b2-060922542daf ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X513IA.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X513IA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX513IA.300:bd06/05/2020:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX513IA_M513IA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX513IA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: VivoBook_ASUSLaptop X513IA_M513IA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 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/1900777/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
I don't know of any alternative "soundmanager" for desktop Linux that has better Bluetooth support than PulseAudio. At least not on desktop Linux... I think Google wrote their own stack for Android. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: In Progress Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903790] 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/1903790 Title: SSD and Bluetooth conflict (Bluetooth doesn't work) Status in linux package in Ubuntu: Confirmed Bug description: Bluetooth stops working when I plug in the SSD. Bluetooth - Qualcomm Atheros Communications AR3011. SSD - OCZ Vector 180 256. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-28-generic 5.8.0-28.30 ProcVersionSignature: Ubuntu 5.8.0-28.30-generic 5.8.14 Uname: Linux 5.8.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: navycat1951 F pulseaudio /dev/snd/controlC0: navycat1951 F pulseaudio /dev/snd/controlC1: navycat1951 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Wed Nov 11 05:26:13 2020 InstallationDate: Installed on 2020-11-01 (9 days ago) InstallationMedia: Ubuntu-MATE 20.10 "Groovy Gorilla" - Release amd64 (20201022) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: BASE_BOARD_MANUFACTURER MODEL_NAME ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-28-generic root=UUID=54e2fb85-ed43-4ffd-a361-504ddf86a0de ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-28-generic N/A linux-backports-modules-5.8.0-28-generic N/A linux-firmware1.190.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/09/2018 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 150-SE-E789 dmi.board.vendor: EVGA dmi.board.version: Patsburg dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/09/2018:br4.6:svnBASE_BOARD_MANUFACTURER:pnMODEL_NAME:pvrBASE_BOARD_VERSION:rvnEVGA:rn150-SE-E789:rvrPatsburg: dmi.product.family: X86 AT dmi.product.name: MODEL_NAME dmi.product.sku: PROJECT_SUB_TAG dmi.product.version: BASE_BOARD_VERSION dmi.sys.vendor: BASE_BOARD_MANUFACTURER To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903790/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1902861] Re: drm/i915/dp_mst - wait longer during the clock recovery for Display port
** Changed in: linux (Ubuntu Groovy) Assignee: (unassigned) => koba (kobako) ** Changed in: linux (Ubuntu Groovy) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1902861 Title: drm/i915/dp_mst - wait longer during the clock recovery for Display port Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.6 package in Ubuntu: New Status in linux source package in Focal: Won't Fix Status in linux-oem-5.6 source package in Focal: In Progress Status in linux source package in Groovy: In Progress Status in linux source package in Hirsute: Incomplete Bug description: [Impact] For some TGL platform, connect with the external monitor on the docking station(SC), after cold/warm boot, the external monitor can't output the video and need to hotplug the docking station. [Fix] On the link-training phase, Wait longer during the clock recovery. [test] With the patch, The TGL-machine connect with the external monitor on docking station(SC) and can output the video to the external monitor on docking station after cold/warm boot. [Regression Potential] Medium, it may not the root cause. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1902861/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
Nice to see it works for 20.10. however, I'd like to keep on the LTS version and expect to get a fix soon. -- 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/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm testing with Sony bluetooth headset SBH20, works fine in A2DP profile, but I can't get audio input and output work in HSP/HFP profile. [Reproduce steps] 1. Scan and pair BT headset in Bluetooth setting 2. Switch to HSP/HFP profile in Sound setting 3. Test sound output/input [Machine information] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 16:26:52 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SBH20 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio Symptom_Type: No sound at all Title: [SBH20, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.13 dmi.board.name: 0188D1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1871794/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1902861] Re: drm/i915/dp_mst - wait longer during the clock recovery for Display port
** Changed in: linux-oem-5.6 (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1902861 Title: drm/i915/dp_mst - wait longer during the clock recovery for Display port Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.6 package in Ubuntu: New Status in linux source package in Focal: Won't Fix Status in linux-oem-5.6 source package in Focal: Fix Committed Status in linux source package in Groovy: In Progress Status in linux source package in Hirsute: Incomplete Bug description: [Impact] For some TGL platform, connect with the external monitor on the docking station(SC), after cold/warm boot, the external monitor can't output the video and need to hotplug the docking station. [Fix] On the link-training phase, Wait longer during the clock recovery. [test] With the patch, The TGL-machine connect with the external monitor on docking station(SC) and can output the video to the external monitor on docking station after cold/warm boot. [Regression Potential] Medium, it may not the root cause. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1902861/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1902469] Re: drm/i915/dp_mst - System would hang during the boot up.
** Changed in: linux-oem-5.6 (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1902469 Title: drm/i915/dp_mst - System would hang during the boot up. Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Status in linux-oem-5.6 source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Committed Bug description: [Impact] The machine connect with the external monitor on dock(Thunderbolt), Then system would hang during the boot-up. [Fix] The atomic check hooks must look up the encoder to be used with a connector from the connector's atomic state, and not assume that it's the connector's current attached encoder. The latter one can change under the atomic check func, or can be unset yet as in the case of MST connectors. [test] With the patch, The machine connect with the external monitor on dock(Thunderbolt), Then system boot up successfully. [Regression Potential] Low. This patch is also verified by others and is archived in the drmtip. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902469/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1891421] Re: kci_test_encap_fou() in rtnetlink.sh from kselftests/net failed with "FAIL: can't add fou port 7777, skipping test"
** Changed in: linux-oem-5.6 (Ubuntu Focal)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1891421
Title:
kci_test_encap_fou() in rtnetlink.sh from kselftests/net failed with
"FAIL: can't add fou port , skipping test"
Status in ubuntu-kernel-tests:
In Progress
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-5.6 package in Ubuntu:
Invalid
Status in linux-oem-osp1 package in Ubuntu:
Invalid
Status in linux source package in Bionic:
Fix Committed
Status in linux-oem-5.6 source package in Bionic:
Invalid
Status in linux-oem-osp1 source package in Bionic:
In Progress
Status in linux source package in Focal:
Fix Committed
Status in linux-oem-5.6 source package in Focal:
Fix Committed
Status in linux-oem-osp1 source package in Focal:
Invalid
Status in linux source package in Groovy:
Fix Committed
Status in linux-oem-5.6 source package in Groovy:
Invalid
Status in linux-oem-osp1 source package in Groovy:
Invalid
Bug description:
== SRU Justification ==
The kci_test_encap_fou() from kci_test_encap() in rtnetlink.sh of
kselftests/net will fail with non-zero return value, and print:
"FAIL: can't add fou port , skipping test"
How to reproduce this:
devdummy="test-dummy0"
testns="testns"
ip netns add "$testns"
ip netns exec "$testns" ip link set lo up
ip netns exec "$testns" ip link add name "$devdummy" type dummy
ip netns exec "$testns" ip link set "$devdummy" up
ip netns exec "$testns" ip fou add port ipproto 47
RTNETLINK answers: No such file or directory
Error talking to the kernel
This test would require the fou module to be loaded before it gets
started.
== Fix
* 26ebd6fed9bb ("selftests: rtnetlink: load fou module for
kci_test_encap_fou() test")
This patch needs to be backported for series after Xenial.
== Test ==
Patch tested directly on the kernel tree, the test will now pass as
expected.
== Regression Potential ==
Low, change limited to the testing tool.
== Original Bug Report ==
The kci_test_encap_fou() from kci_test_encap() in rtnetlink.sh of
kselftests/net will fail with non-zero return value, and print:
"FAIL: can't add fou port , skipping test"
How to reproduce this:
devdummy="test-dummy0"
testns="testns"
ip netns add "$testns"
ip netns exec "$testns" ip link set lo up
ip netns exec "$testns" ip link add name "$devdummy" type dummy
ip netns exec "$testns" ip link set "$devdummy" up
ip netns exec "$testns" ip fou add port ipproto 47
RTNETLINK answers: No such file or directory
Error talking to the kernel
This is not a regression, it's the real test result after bug 1890136
has been fixed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1891421/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1901971] Re: alsa/hda: mic can't be detect if booting with headset plugged on a HP machine
** Changed in: linux-oem-5.6 (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1901971 Title: alsa/hda: mic can't be detect if booting with headset plugged on a HP machine Status in HWE Next: In Progress Status in linux-oem-5.6 package in Ubuntu: In Progress Status in linux-oem-5.6 source package in Focal: Fix Committed Bug description: Since this patch is cced to stable kernel, I only send this patch to oem-5.6 kernel, other ubuntu kernels will merge this patch with stable update. [Impact] On a HP machine, if we plug a headset before booting, after booting to the desktop, the mic can't be detected. [Fix] Realtek engineer submit a patch to usptream, I backport this patch to ubuntu oem kernel. [Test] Plug a headset, then power on the machine, after entering the gnome, check the mic, it is detected, and use mic to record, it could record the sound. [Regression Potential] I could make the sound on that HP machine not work, but this possibility is very low and this regression possibility is limited to this HP machine since this patch use pin definition to apply the quirk. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1901971/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1900847] Re: Fix non-working Intel NVMe after S3
** Changed in: linux-oem-5.6 (Ubuntu Focal) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1900847 Title: Fix non-working Intel NVMe 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: Fix Committed Status in linux-oem-5.6 source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Committed Status in linux-oem-5.6 source package in Groovy: Invalid Bug description: [Impact] Intel NVMe has a 10% chance to stop working after S3. [Fix] Enable ACS quirk on Intel CML root port. [Test] With the patch applied, Intel NVMe mostly works after S3. There's still a 1/1000 chance the issue happens. Intel is investigating the root cause. [Regression Potential] ACS works at hardware level, so I can't really assess the risk of regression. Since Intel confirmed CML also needs ACS quirk, we can only trust them until they devise a real fix. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1900847/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886937] Re: limited hardware support AMD 4700u HP Envy x360 13-ay003nd
Please test this commit: https://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86.git/commit/?h=for-next=156ec4731cb22b06c08e27debc1ef9f16f4bbb5e It doesn't work on my AMD Renoir laptop though.. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1886937 Title: limited hardware support AMD 4700u HP Envy x360 13-ay003nd Status in linux package in Ubuntu: Confirmed Bug description: Suspend/Hibernate: screen goes off, nothing else happens. After user interaction, screen turns on. Login screen is shown. Sometimes screen does not turn on: physical reboot required. kernel upgrade to 5.8rc3 or 5.8rc4 has no effect. Brightness: Adjusting brightness has no effect, nightmode has no effect. Partial solution: kernel upgrade 5.8rc3 or 5.8rc4 solves this partially, brightness can be adjusted and nightmode works But after a reboot brightness is always at max. Also brightness cannot be lowered as much as normally expected. CPU & fan: CPU is always high, 5.8rc3 solves this partially, fan is still always on and quite high (after clean Ubuntu install, nothing configured or installed). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: asterix 881 F pulseaudio /dev/snd/controlC1: asterix 881 F pulseaudio /dev/snd/controlC0: asterix 881 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Thu Jul 9 12:21:02 2020 InstallationDate: Installed on 2020-07-09 (0 days ago) InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: HP HP ENVY x360 Convertible 13-ay0xxx ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=e2b48a5b-5ae8-41c4-a6d0-7eb17bb02dd3 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/07/2020 dmi.bios.vendor: Insyde dmi.bios.version: F.06 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 876E dmi.board.vendor: HP dmi.board.version: 12.30 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.06:bd05/07/2020:svnHP:pnHPENVYx360Convertible13-ay0xxx:pvrType1ProductConfigId:rvnHP:rn876E:rvr12.30:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY x360 Convertible 13-ay0xxx dmi.product.sku: 1D5H9EA#ABH dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886937/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1902861] Re: drm/i915/dp_mst - wait longer during the clock recovery for Display port
For 5.8, we will backport the real resolution from linux-next. -- 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/1902861 Title: drm/i915/dp_mst - wait longer during the clock recovery for Display port Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.6 package in Ubuntu: New Status in linux source package in Focal: Won't Fix Status in linux-oem-5.6 source package in Focal: In Progress Status in linux source package in Groovy: New Status in linux source package in Hirsute: Incomplete Bug description: [Impact] For some TGL platform, connect with the external monitor on the docking station(SC), after cold/warm boot, the external monitor can't output the video and need to hotplug the docking station. [Fix] On the link-training phase, Wait longer during the clock recovery. [test] With the patch, The TGL-machine connect with the external monitor on docking station(SC) and can output the video to the external monitor on docking station after cold/warm boot. [Regression Potential] Medium, it may not the root cause. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1902861/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1902156] Re: [ASUS VivoBook X541UJ] Keyboard and touchpad don't work on kernel 5.8.0.28, but 5.4 or 5.8.16 work
the issue still persists on Linux 5.8.28. ** Summary changed: - [ASUS VivoBook X541UJ] Keyboard and touchpad don't work on kernel 5.8.0.26, but 5.4 or 5.8.11 work + [ASUS VivoBook X541UJ] Keyboard and touchpad don't work on kernel 5.8.0.28, but 5.4 or 5.8.16 work -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1902156 Title: [ASUS VivoBook X541UJ] Keyboard and touchpad don't work on kernel 5.8.0.28, but 5.4 or 5.8.16 work Status in linux package in Ubuntu: Confirmed Bug description: when I updated my system to ubuntu 20.10, the keyboard and mouse no longer worked after a little investigation, I found out the kernel causes this problem, downgrading to linux 5.4 or upgrading to linux kernel 5.8.11 solved this issue, I also found that this problem is present on other ASUS laptop models ( my laptop is ASUS) so you may want to investigate this issue to update your default 20.10 Linux kernel. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: joseph 1979 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-06-03 (515 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: ASUSTeK COMPUTER INC. X541UJ Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-26-generic root=UUID=1298f5d0-e6c0-4aa3-9c5a-fbe0ebf0fc02 ro quiet splash pci=noaer mds=full,nosmt vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 RelatedPackageVersions: linux-restricted-modules-5.8.0-26-generic N/A linux-backports-modules-5.8.0-26-generic N/A linux-firmware1.190 Tags: groovy Uname: Linux 5.8.0-26-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-10-24 (5 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/18/2019 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X541UJ.310 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X541UJ 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.:bvrX541UJ.310:bd04/18/2019:br5.12:svnASUSTeKCOMPUTERINC.:pnX541UJ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX541UJ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: X541UJ dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902156/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1901135] Re: [SRU][OEM-5.6]Fix no video out from some monitors on amdgpu
** Changed in: linux-oem-5.6 (Ubuntu Focal) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1901135 Title: [SRU][OEM-5.6]Fix no video out from some monitors on amdgpu Status in HWE Next: New Status in linux-oem-5.6 package in Ubuntu: New Status in linux-oem-5.6 source package in Focal: Fix Committed Bug description: [Impact] On some models of Dell monitors, amdgpu lost signal. Blackscreen only. [Fix] Handle aux write failure, and retry it to fix it. [Test Case] Verified on the monitors, display OK. [Regression Potential] Low, Upstream fix, Verified with positive results. Focal and Groovy already got this fix. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1901135/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1902156] Re: [ASUS VivoBook X541UJ] Keyboard and touchpad don't work on kernel 5.8.0.28, but 5.4 or 5.8.16 work
sorry Linux 5.8.0.28. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1902156 Title: [ASUS VivoBook X541UJ] Keyboard and touchpad don't work on kernel 5.8.0.28, but 5.4 or 5.8.16 work Status in linux package in Ubuntu: Confirmed Bug description: when I updated my system to ubuntu 20.10, the keyboard and mouse no longer worked after a little investigation, I found out the kernel causes this problem, downgrading to linux 5.4 or upgrading to linux kernel 5.8.11 solved this issue, I also found that this problem is present on other ASUS laptop models ( my laptop is ASUS) so you may want to investigate this issue to update your default 20.10 Linux kernel. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: joseph 1979 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-06-03 (515 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: ASUSTeK COMPUTER INC. X541UJ Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-26-generic root=UUID=1298f5d0-e6c0-4aa3-9c5a-fbe0ebf0fc02 ro quiet splash pci=noaer mds=full,nosmt vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 RelatedPackageVersions: linux-restricted-modules-5.8.0-26-generic N/A linux-backports-modules-5.8.0-26-generic N/A linux-firmware1.190 Tags: groovy Uname: Linux 5.8.0-26-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-10-24 (5 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/18/2019 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X541UJ.310 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X541UJ 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.:bvrX541UJ.310:bd04/18/2019:br5.12:svnASUSTeKCOMPUTERINC.:pnX541UJ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX541UJ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: X541UJ dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902156/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886937] Re: limited hardware support AMD 4700u HP Envy x360 13-ay003nd
The patch above is only a part of the picture, it's actually the amdgpu driver that is at fault and causes the machine not to wake up, the Renoir support is in the works for it. More details here: https://gitlab.freedesktop.org/drm/amd/-/issues/1230 ** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #1230 https://gitlab.freedesktop.org/drm/amd/-/issues/1230 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1886937 Title: limited hardware support AMD 4700u HP Envy x360 13-ay003nd Status in linux package in Ubuntu: Confirmed Bug description: Suspend/Hibernate: screen goes off, nothing else happens. After user interaction, screen turns on. Login screen is shown. Sometimes screen does not turn on: physical reboot required. kernel upgrade to 5.8rc3 or 5.8rc4 has no effect. Brightness: Adjusting brightness has no effect, nightmode has no effect. Partial solution: kernel upgrade 5.8rc3 or 5.8rc4 solves this partially, brightness can be adjusted and nightmode works But after a reboot brightness is always at max. Also brightness cannot be lowered as much as normally expected. CPU & fan: CPU is always high, 5.8rc3 solves this partially, fan is still always on and quite high (after clean Ubuntu install, nothing configured or installed). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: asterix 881 F pulseaudio /dev/snd/controlC1: asterix 881 F pulseaudio /dev/snd/controlC0: asterix 881 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Thu Jul 9 12:21:02 2020 InstallationDate: Installed on 2020-07-09 (0 days ago) InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: HP HP ENVY x360 Convertible 13-ay0xxx ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=e2b48a5b-5ae8-41c4-a6d0-7eb17bb02dd3 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/07/2020 dmi.bios.vendor: Insyde dmi.bios.version: F.06 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 876E dmi.board.vendor: HP dmi.board.version: 12.30 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.06:bd05/07/2020:svnHP:pnHPENVYx360Convertible13-ay0xxx:pvrType1ProductConfigId:rvnHP:rn876E:rvr12.30:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY x360 Convertible 13-ay0xxx dmi.product.sku: 1D5H9EA#ABH dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886937/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1899883] Re: Tiger Lake PMC core driver fixes
** Changed in: linux-oem-5.6 (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1899883 Title: Tiger Lake PMC core driver fixes Status in linux package in Ubuntu: Invalid Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux-oem-5.6 source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Committed Bug description: [Impact] The power gating status is not correct and the slp_s0 value is not correct on Intel TigerLake platform. The slp_s0 value is essential for our tools to confirm whether the system enters deep sleep, and the power gating is critical for another tool to check which device is still running when the system is suspended. Both are not that useful for a normal user, but useful for developers to debug power consumption issues. [Fix] The patchset in https://lore.kernel.org/lkml/20201006224702.12697-1-david.e@linux.intel.com/ provides several critical fixes for intel_pmc_core driver. [Test] Verified on some TigerLake platforms [Regression Potential] Low, the fix for status bits map and the slp_s0 calculation are simple and clear, should have low impact on regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899883/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1902577] Re: TGL system automatically resumes from s2idle when connecting to a docking station with a monitor
this should also land in groovy so that hwe-5.8 will get it ** 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 ** Changed in: linux (Ubuntu Focal) Status: New => Invalid ** Changed in: linux-oem-5.6 (Ubuntu Focal) Status: New => 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/1902577 Title: TGL system automatically resumes from s2idle when connecting to a docking station with a monitor Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.6 package in Ubuntu: New Status in linux source package in Focal: Invalid Status in linux-oem-5.6 source package in Focal: Fix Committed Bug description: [Impact] TGL systems wake up automatically from s2idle when connecting to a docking station with a monitor. The wake-up events are generated when BIOS sets ALL_MONITOR_OFF for power-saving on TGL systems. [Fix] A BIOS workaround is used to skip ALL_MONITOR_OFF with an _OSI string "Linux-Dell-USB4-Wakeup". [Test] Verified on Dell's TigerLake platforms [Regression Potential] Low. This only works on platforms supporting "Linux-Dell-USB4-Wakeup". No other platforms will be affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902577/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1902613] Re: drm/i915/dp_mst - only read the base capability in DPCD.
** Changed in: linux-oem-5.6 (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1902613 Title: drm/i915/dp_mst - only read the base capability in DPCD. Status in HWE Next: New Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux-oem-5.6 source package in Focal: Fix Committed Bug description: [Impact] Currently DRM driver assume the source device caps is higher than the MST device caps. With this commit, the statement would be broken. e.g. the source device only support DP1.2 and the mst device support DP1.4. The source device can't output the video to the external monitor on the docking station. [Fix] Revert the previous patch and only read the base capability from DPCD. [test] With the patch, The machine(DP1.2) connect with the external monitor on docking station(SC) and can output the video to the external monitor on docking station(SC-DP1.4). [Regression Potential] Can't output 4k@60hz on the docking station(SC). To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1902613/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851518] Re: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones
Yes, it is. For some reason linux loads snd_hda_intel instead of snd_soc_skl_hda_dsp ALSA module and this causes the metallic audio. How can I get it to load snd_soc_skl_hda_dsp ALSA module? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851518 Title: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones Status in linux package in Ubuntu: Fix Released Bug description: I've been googling this issue for 10's of hours and tried many things. Relase of Ubuntu: 19.10 Expected outcome: Music plays on the internal speakers and headphones. Actual outcome: I can barely hear audio using headphones with volume turned up to 150%. Absolutely nothing comes out of the speakers. (The speakers sound great under Windows 10.) Complete alsa-info output is attached, but here are some snippets: !!DMI Information !!--- Manufacturer: SAMSUNG ELECTRONICS CO., LTD. Product Name: 950SBE/951SBE Product Version: P06RES Firmware Version: P06RES.075.190529.SP Board Vendor: SAMSUNG ELECTRONICS CO., LTD. Board Name:NP950SBE-K01US !!Kernel Information !!-- Kernel release:5.3.0-19-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.3.0-19-generic Library version:1.1.9 Utilities version: 1.1.9 !!Loaded ALSA modules !!--- snd_hda_intel !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0x604b118000 irq 177 !!PCI Soundcards installed in the system !!-- 00:1f.3 Multimedia audio controller: Intel Corporation Cannon Point-LP High Definition Audio Controller (rev 11) !!Advanced information - PCI Vendor/Device/Subsystem ID's !!--- 00:1f.3 0401: 8086:9dc8 (rev 11) DeviceName: Onboard - Sound !!HDA-Intel Codec information !!--- --startcollapse-- Codec: Realtek ALC298 Address: 0 AFG Function Id: 0x1 (unsol 1) Vendor Id: 0x10ec0298 Subsystem Id: 0x144dc812 Revision Id: 0x100103 No Modem Function Group found Default PCM: rates [0x60]: 44100 48000 bits [0xe]: 16 20 24 formats [0x1]: PCM Default Amp-In caps: N/A Default Amp-Out caps: N/A State of AFG node 0x01: Power states: D0 D1 D2 D3 D3cold CLKSTOP EPSS Power: setting=D0, actual=D0 GPIO: io=8, o=0, i=0, unsolicited=1, wake=0 IO[0]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[1]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[2]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[3]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[4]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[5]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[6]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[7]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 Node 0x02 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Headphone Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Device: name="ALC298 Analog", type="Audio", device=0 Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0 Amp-Out vals: [0x00 0x00] Converter: stream=1, channel=0 PCM: rates [0x60]: 44100 48000 bits [0xe]: 16 20 24 formats [0x1]: PCM Power states: D0 D1 D2 D3 EPSS Power: setting=D0, actual=D0 Node 0x03 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Speaker Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0 Amp-Out vals: [0x7f 0x7f] Converter: stream=1, channel=0 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin 1383 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Nov 6 06:20:08 2019 InstallationDate: Installed on 2019-11-03 (3 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash
[Kernel-packages] [Bug 1897227] Re: Remove NVMe suspend-to-idle workaround
** Changed in: linux-oem-5.6 (Ubuntu Focal) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1897227 Title: Remove NVMe suspend-to-idle workaround Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Status in linux-oem-5.6 source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Released Status in linux-oem-5.6 source package in Groovy: Invalid Bug description: [Impact] We already have correct NVMe suspend-to-idle implementation, we can remove workaround we carried in Ubuntu kernel. [Fix] Revert unnecessary no D3 quirks we used as workaround. [Test] After the revert, both NVMe still use native power saving mechanism as intended. [Regression Potential] Though unlikely, if there is any platform that uses legacy S3 and needs to keep the NVMe device in D0 instead of D3, this might have impact on that scenario. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1897227/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903794] [NEW] Wifi stopped working: Init ucode -5 [Intel Wireless 9560]
You have been subscribed to a public bug: I once cold booted my laptop and the wifi stopped working completely. This is the error I get from dmesg when I filter for wireless driver info only. Relevant specs: --- Operating System: Distributor ID: Ubuntu Description: Ubuntu 20.04.1 LTS Release: 20.04 Codename:focal PC make: Dell Inspiron 7586 2-in-1 Linux Firmware: linux-firmware/focal-updates,focal-updates,now 1.187.4 all [installed] Linux Headers: 5.4.0-42-generic $dmesg | grep iwlwifi [8.050151] iwlwifi :00:14.3: enabling device ( -> 0002) [8.073632] iwlwifi :00:14.3: Found debug destination: EXTERNAL_DRAM [8.073635] iwlwifi :00:14.3: Found debug configuration: 0 [8.073898] iwlwifi :00:14.3: loaded firmware version 46.6bf1df06.0 op_mode iwlmvm [8.133208] iwlwifi :00:14.3: Detected Intel(R) Dual Band Wireless AC 9460, REV=0x318 [8.156288] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM [8.159789] iwlwifi :00:14.3: Allocated 0x0040 bytes for firmware monitor. [8.164794] iwlwifi :00:14.3: Microcode SW error detected. Restarting 0x0. [8.164799] iwlwifi :00:14.3: Not valid error log pointer 0x for Init uCode [8.164816] iwlwifi :00:14.3: Fseq Registers: [8.164822] iwlwifi :00:14.3: 0x98402404 | FSEQ_ERROR_CODE [8.164825] iwlwifi :00:14.3: 0x34504D88 | FSEQ_TOP_INIT_VERSION [8.164828] iwlwifi :00:14.3: 0x65A63677 | FSEQ_CNVIO_INIT_VERSION [8.164831] iwlwifi :00:14.3: 0x015660A5 | FSEQ_OTP_VERSION [8.164834] iwlwifi :00:14.3: 0x39BEFAFE | FSEQ_TOP_CONTENT_VERSION [8.164837] iwlwifi :00:14.3: 0xC1B9DFF0 | FSEQ_ALIVE_TOKEN [8.164841] iwlwifi :00:14.3: 0x00409810 | FSEQ_CNVI_ID [8.164844] iwlwifi :00:14.3: 0xFFEE77FF | FSEQ_CNVR_ID [8.164847] iwlwifi :00:14.3: 0x01000100 | CNVI_AUX_MISC_CHIP [8.164882] iwlwifi :00:14.3: 0xA5A5A5A2 | CNVR_AUX_MISC_CHIP [8.164951] iwlwifi :00:14.3: 0xA5A5A5A2 | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM [8.165020] iwlwifi :00:14.3: 0xA5A5A5A2 | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR [8.165247] iwlwifi :00:14.3: SecBoot CPU1 Status: 0xa5a5a5a2, CPU2 Status: 0xa5a5a5a2 [8.165251] iwlwifi :00:14.3: Failed to start INIT ucode: -5 [8.165253] iwlwifi :00:14.3: Collecting data: trigger 16 fired. [8.411263] iwlwifi :00:14.3: Firmware not running - cannot dump error [8.424358] iwlwifi :00:14.3: Failed to run INIT ucode: -5 **My wireless network adapter is recognized by the OS.** name@name:~$ lspci 00:14.3 Network controller: Intel Corporation Cannon Point-LP CNVi [Wireless-AC] (rev 30) name@name:~$ rfkill list 0: hci0: Bluetooth Soft blocked: no Hard blocked: no name@name:~$ sudo lshw -C network [sudo] password for name: *-network description: Network controller product: Cannon Point-LP CNVi [Wireless-AC] vendor: Intel Corporation physical id: 14.3 bus info: pci@:00:14.3 version: 30 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix bus_master cap_list configuration: driver=iwlwifi latency=0 resources: irq:16 memory:a121c000-a121 Resolutions attempted: - Downloading official iwlwifi drivers from Intel, Dell and my /lib/firmware folder (-34.ucode from Intel and Dell and also the -33, -34, -38, -41, -43 and -46.ucode from /lib/firmware) - Downloading the backport iwlwifi drivers from PPA Research: My suspicion is that there might be a conflict with the Bluetooth module (hindering the correct firmware from being loaded) as there was a time the wifi briefly worked then stopped when I turned off Bluetooth. However, now I can't turn off Bluetooth and wifi. As you can see, the radio kill button has just the Bluetooth option which doesn't even work. Please help me? ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: kernel-bug -- Wifi stopped working: Init ucode -5 [Intel Wireless 9560] https://bugs.launchpad.net/bugs/1903794 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 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
Please please, I'll apreciate a lot any kind of help. -- 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/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm testing with Sony bluetooth headset SBH20, works fine in A2DP profile, but I can't get audio input and output work in HSP/HFP profile. [Reproduce steps] 1. Scan and pair BT headset in Bluetooth setting 2. Switch to HSP/HFP profile in Sound setting 3. Test sound output/input [Machine information] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 16:26:52 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SBH20 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio Symptom_Type: No sound at all Title: [SBH20, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.13 dmi.board.name: 0188D1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1871794/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903794] 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 1903794 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1903794 Title: Wifi stopped working: Init ucode -5 [Intel Wireless 9560] Status in linux package in Ubuntu: Incomplete Bug description: I once cold booted my laptop and the wifi stopped working completely. This is the error I get from dmesg when I filter for wireless driver info only. Relevant specs: --- Operating System: Distributor ID:Ubuntu Description: Ubuntu 20.04.1 LTS Release: 20.04 Codename: focal PC make: Dell Inspiron 7586 2-in-1 Linux Firmware: linux-firmware/focal-updates,focal-updates,now 1.187.4 all [installed] Linux Headers: 5.4.0-42-generic $dmesg | grep iwlwifi [8.050151] iwlwifi :00:14.3: enabling device ( -> 0002) [8.073632] iwlwifi :00:14.3: Found debug destination: EXTERNAL_DRAM [8.073635] iwlwifi :00:14.3: Found debug configuration: 0 [8.073898] iwlwifi :00:14.3: loaded firmware version 46.6bf1df06.0 op_mode iwlmvm [8.133208] iwlwifi :00:14.3: Detected Intel(R) Dual Band Wireless AC 9460, REV=0x318 [8.156288] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM [8.159789] iwlwifi :00:14.3: Allocated 0x0040 bytes for firmware monitor. [8.164794] iwlwifi :00:14.3: Microcode SW error detected. Restarting 0x0. [8.164799] iwlwifi :00:14.3: Not valid error log pointer 0x for Init uCode [8.164816] iwlwifi :00:14.3: Fseq Registers: [8.164822] iwlwifi :00:14.3: 0x98402404 | FSEQ_ERROR_CODE [8.164825] iwlwifi :00:14.3: 0x34504D88 | FSEQ_TOP_INIT_VERSION [8.164828] iwlwifi :00:14.3: 0x65A63677 | FSEQ_CNVIO_INIT_VERSION [8.164831] iwlwifi :00:14.3: 0x015660A5 | FSEQ_OTP_VERSION [8.164834] iwlwifi :00:14.3: 0x39BEFAFE | FSEQ_TOP_CONTENT_VERSION [8.164837] iwlwifi :00:14.3: 0xC1B9DFF0 | FSEQ_ALIVE_TOKEN [8.164841] iwlwifi :00:14.3: 0x00409810 | FSEQ_CNVI_ID [8.164844] iwlwifi :00:14.3: 0xFFEE77FF | FSEQ_CNVR_ID [8.164847] iwlwifi :00:14.3: 0x01000100 | CNVI_AUX_MISC_CHIP [8.164882] iwlwifi :00:14.3: 0xA5A5A5A2 | CNVR_AUX_MISC_CHIP [8.164951] iwlwifi :00:14.3: 0xA5A5A5A2 | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM [8.165020] iwlwifi :00:14.3: 0xA5A5A5A2 | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR [8.165247] iwlwifi :00:14.3: SecBoot CPU1 Status: 0xa5a5a5a2, CPU2 Status: 0xa5a5a5a2 [8.165251] iwlwifi :00:14.3: Failed to start INIT ucode: -5 [8.165253] iwlwifi :00:14.3: Collecting data: trigger 16 fired. [8.411263] iwlwifi :00:14.3: Firmware not running - cannot dump error [8.424358] iwlwifi :00:14.3: Failed to run INIT ucode: -5 **My wireless network adapter is recognized by the OS.** name@name:~$ lspci 00:14.3 Network controller: Intel Corporation Cannon Point-LP CNVi [Wireless-AC] (rev 30) name@name:~$ rfkill list 0: hci0: Bluetooth Soft blocked: no Hard blocked: no name@name:~$ sudo lshw -C network [sudo] password for name: *-network description: Network controller product: Cannon Point-LP CNVi [Wireless-AC] vendor: Intel Corporation physical id: 14.3 bus info: pci@:00:14.3 version: 30 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix bus_master cap_list configuration: driver=iwlwifi latency=0 resources: irq:16 memory:a121c000-a121 Resolutions attempted: - Downloading official iwlwifi drivers from Intel, Dell and my /lib/firmware folder (-34.ucode from Intel and Dell and also the -33, -34, -38, -41, -43 and -46.ucode from /lib/firmware) - Downloading the backport iwlwifi drivers from PPA Research: My suspicion is that there might be a conflict with the Bluetooth module (hindering the correct firmware from being loaded) as there was a time the wifi briefly worked then stopped when I turned off Bluetooth. However, now I can't turn off Bluetooth and wifi. As you can see, the radio kill button has just the Bluetooth option which doesn't even work. Please help me?
[Kernel-packages] [Bug 1903794] Re: Wifi stopped working: Init ucode -5 [Intel Wireless 9560]
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1903794 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. Bug reporting is mostly about finding & fixing problems thus preventing future users from hitting the same bug. For a Support site you can try https://answers.launchpad.net/ubuntu. You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org, or for more support options please look at https://discourse.ubuntu.com/t/community- support/709 ** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1903794 Title: Wifi stopped working: Init ucode -5 [Intel Wireless 9560] Status in linux package in Ubuntu: Incomplete Bug description: I once cold booted my laptop and the wifi stopped working completely. This is the error I get from dmesg when I filter for wireless driver info only. Relevant specs: --- Operating System: Distributor ID:Ubuntu Description: Ubuntu 20.04.1 LTS Release: 20.04 Codename: focal PC make: Dell Inspiron 7586 2-in-1 Linux Firmware: linux-firmware/focal-updates,focal-updates,now 1.187.4 all [installed] Linux Headers: 5.4.0-42-generic $dmesg | grep iwlwifi [8.050151] iwlwifi :00:14.3: enabling device ( -> 0002) [8.073632] iwlwifi :00:14.3: Found debug destination: EXTERNAL_DRAM [8.073635] iwlwifi :00:14.3: Found debug configuration: 0 [8.073898] iwlwifi :00:14.3: loaded firmware version 46.6bf1df06.0 op_mode iwlmvm [8.133208] iwlwifi :00:14.3: Detected Intel(R) Dual Band Wireless AC 9460, REV=0x318 [8.156288] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM [8.159789] iwlwifi :00:14.3: Allocated 0x0040 bytes for firmware monitor. [8.164794] iwlwifi :00:14.3: Microcode SW error detected. Restarting 0x0. [8.164799] iwlwifi :00:14.3: Not valid error log pointer 0x for Init uCode [8.164816] iwlwifi :00:14.3: Fseq Registers: [8.164822] iwlwifi :00:14.3: 0x98402404 | FSEQ_ERROR_CODE [8.164825] iwlwifi :00:14.3: 0x34504D88 | FSEQ_TOP_INIT_VERSION [8.164828] iwlwifi :00:14.3: 0x65A63677 | FSEQ_CNVIO_INIT_VERSION [8.164831] iwlwifi :00:14.3: 0x015660A5 | FSEQ_OTP_VERSION [8.164834] iwlwifi :00:14.3: 0x39BEFAFE | FSEQ_TOP_CONTENT_VERSION [8.164837] iwlwifi :00:14.3: 0xC1B9DFF0 | FSEQ_ALIVE_TOKEN [8.164841] iwlwifi :00:14.3: 0x00409810 | FSEQ_CNVI_ID [8.164844] iwlwifi :00:14.3: 0xFFEE77FF | FSEQ_CNVR_ID [8.164847] iwlwifi :00:14.3: 0x01000100 | CNVI_AUX_MISC_CHIP [8.164882] iwlwifi :00:14.3: 0xA5A5A5A2 | CNVR_AUX_MISC_CHIP [8.164951] iwlwifi :00:14.3: 0xA5A5A5A2 | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM [8.165020] iwlwifi :00:14.3: 0xA5A5A5A2 | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR [8.165247] iwlwifi :00:14.3: SecBoot CPU1 Status: 0xa5a5a5a2, CPU2 Status: 0xa5a5a5a2 [8.165251] iwlwifi :00:14.3: Failed to start INIT ucode: -5 [8.165253] iwlwifi :00:14.3: Collecting data: trigger 16 fired. [8.411263] iwlwifi :00:14.3: Firmware not running - cannot dump error [8.424358] iwlwifi :00:14.3: Failed to run INIT ucode: -5 **My wireless network adapter is recognized by the OS.** name@name:~$ lspci 00:14.3 Network controller: Intel Corporation Cannon Point-LP CNVi [Wireless-AC] (rev 30) name@name:~$ rfkill list 0: hci0: Bluetooth Soft blocked: no Hard blocked: no name@name:~$ sudo lshw -C network [sudo] password for name: *-network description: Network controller product: Cannon Point-LP CNVi [Wireless-AC] vendor: Intel Corporation physical id: 14.3 bus info: pci@:00:14.3 version: 30 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix bus_master cap_list configuration: driver=iwlwifi latency=0 resources: irq:16 memory:a121c000-a121 Resolutions attempted: - Downloading official iwlwifi drivers from Intel, Dell and my /lib/firmware folder (-34.ucode from Intel and Dell and also the -33, -34, -38, -41, -43 and -46.ucode from /lib/firmware) - Downloading the backport iwlwifi drivers from PPA Research: My suspicion is that there might be a conflict with the Bluetooth module
