[Kernel-packages] [Bug 1867753] Re: [Ubuntu 20.04] Unset HIBERNATION and PM kernel config options for focal
Successfully verified - updating tag. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1867753 Title: [Ubuntu 20.04] Unset HIBERNATION and PM kernel config options for focal Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Committed Bug description: Addl change required for kernel config. from CONFIG_HIBERNATION=y CONFIG_PM=y to #CONFIG_HIBERNATION is not set #CONFIG_PM is not set hope that will be the last ticket for 20.04... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1867753/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835531] Comment bridged from LTC Bugzilla
--- Comment From cborn...@de.ibm.com 2020-03-25 03:24 EDT--- Test started on 5.4.0-20-generic. Basic test and unit test finished successfully. Some more tests peding. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835531 Title: [20.04 FEAT] Base KVM setup for secure guests - kernel part Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Committed Bug description: Enable KVM guests to start and control a guest running in secure mode. With that Customers can securely run sensitive workloads in KVM on premise and in the cloud. Feature Request for kernel contribution Target kernel will be 5.3. Currently not available. Git-commit / backport will be provided To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1835531/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867753] Re: [Ubuntu 20.04] Unset HIBERNATION and PM kernel config options for focal
** Tags removed: verification-done-focal ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1867753 Title: [Ubuntu 20.04] Unset HIBERNATION and PM kernel config options for focal Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Committed Bug description: Addl change required for kernel config. from CONFIG_HIBERNATION=y CONFIG_PM=y to #CONFIG_HIBERNATION is not set #CONFIG_PM is not set hope that will be the last ticket for 20.04... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1867753/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867753] Re: [Ubuntu 20.04] Unset HIBERNATION and PM kernel config options for focal
The ticket should be now verification-done-focal (maybe a bugzilla bridge issue) ... ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1867753 Title: [Ubuntu 20.04] Unset HIBERNATION and PM kernel config options for focal Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Committed Bug description: Addl change required for kernel config. from CONFIG_HIBERNATION=y CONFIG_PM=y to #CONFIG_HIBERNATION is not set #CONFIG_PM is not set hope that will be the last ticket for 20.04... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1867753/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1868693] Re: Incorrect advertise flags in bluetooth beacon using BlueZ
@vanvugt , I installed nRF connect app on android phone. When it detects my machine's bluetooth, it shows advertisement flags. In case of 0x02, only bit 1 (LE GeneralDiscoverable Mode ) is set. Where as , when controller mode is set to be "le" , bit 2 (BR/EDR not supported) should also be set to make it 0x06. Thanks for your 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/1868693 Title: Incorrect advertise flags in bluetooth beacon using BlueZ Status in bluez package in Ubuntu: Incomplete Bug description: I tried the following on bluex version 5.48 and 5.52. I have set ControllerMode to "le" in main.conf. Using bluetootctl, when i turn on the advertisement using command "advertise on" , I get 0x02 advertisement flag. which means "BR/EDR Not Supported" (Bit 2) is not set. Now , if i restart the bluetooth service, and turn on the advertisement again, I get 0x06 advertisement flags. Here is my main.conf [General]# Default adaper name # Defaults to 'BlueZ X.YZ' #Name = BlueZ# Default device class. Only the major and minor device class bits are # considered. Defaults to '0x00'. Class = 0x000100# How long to stay in discoverable mode before going back to non-discoverable # The value is in seconds. Default is 180, i.e. 3 minutes. # 0 = disable timer, i.e. stay discoverable forever DiscoverableTimeout = 0# How long to stay in pairable mode before going back to non-discoverable # The value is in seconds. Default is 0. # 0 = disable timer, i.e. stay pairable forever #PairableTimeout = 0# Automatic connection for bonded devices driven by platform/user events. # If a platform plugin uses this mechanism, automatic connections will be # enabled during the interval defined below. Initially, this feature # intends to be used to establish connections to ATT channels. Default is 60. #AutoConnectTimeout = 60# Use vendor id source (assigner), vendor, product and version information for # DID profile support. The values are separated by ":" and assigner, VID, PID # and version. # Possible vendor id source values: bluetooth, usb (defaults to usb) #DeviceID = bluetooth:1234:5678:abcd# Do reverse service discovery for previously unknown devices that connect to # us. This option is really only needed for qualification since the BITE tester # doesn't like us doing reverse SDP for some test cases (though there could in # theory be other useful purposes for this too). Defaults to 'true'. #ReverseServiceDiscovery = true# Enable name resolving after inquiry. Set it to 'false' if you don't need # remote devices name and want shorter discovery cycle. Defaults to 'true'. #NameResolving = true# Enable runtime persistency of debug link keys. Default is false which # makes debug link keys valid only for the duration of the connection # that they were created for. #DebugKeys = false# Restricts all controllers to the specified transport. Default value # is "dual", i.e. both BR/EDR and LE enabled (when supported by the HW). # Possible values: "dual", "bredr", "le" ControllerMode = le# Enables Multi Profile Specification support. This allows to specify if # system supports only Multiple Profiles Single Device (MPSD) configuration # or both Multiple Profiles Single Device (MPSD) and Multiple Profiles Multiple # Devices (MPMD) configurations. # Possible values: "off", "single", "multiple" #MultiProfile = off# Permanently enables the Fast Connectable setting for adapters that # support it. When enabled other devices can connect faster to us, # however the tradeoff is increased power consumptions. This feature # will fully work only on kernel version 4.1 and newer. Defaults to # 'false'. #FastConnectable = false[Policy]# The ReconnectUUIDs defines the set of remote services that should try # to be reconnected to in case of a link loss (link supervision # timeout). The policy plugin should contain a sane set of values by # default, but this list can be overridden here. By setting the list to # empty the reconnection feature gets disabled. #ReconnectUUIDs=1112--1000-8000-00805f9b34fb, 111f--1000-8000-00805f9b34fb, 110a--1000-8000-00805f9b34fb# ReconnectAttempts define the number of attempts to reconnect after a link # lost. Setting the value to 0 disables reconnecting feature. #ReconnectAttempts=7# ReconnectIntervals define the set of intervals in seconds to use in between # attempts. # If the number of attempts defined in ReconnectAttempts is bigger than the # set of intervals the last interval is repeated until the last attempt. #ReconnectIntervals=1, 2, 4, 8, 16, 32, 64# AutoEnable defines option to enable all controllers when they are found. # This includes adapters present on start as well as adapters that are plugged # in later on. Default
[Kernel-packages] [Bug 1868222] Re: rpi don't boot with 5.4.0-1004-raspi2
Fixed kernel packages 5.4.0-1006.6 have been released and updated images are available from http://cdimage.ubuntu.com/ubuntu-server/daily- preinstalled/current/. ** Changed in: linux-raspi2 (Ubuntu Focal) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1868222 Title: rpi don't boot with 5.4.0-1004-raspi2 Status in linux-raspi2 package in Ubuntu: Fix Released Status in linux-raspi2 source package in Focal: Fix Released Bug description: -> tested on raspberry 3b+ and 4b After a fresh install of Ubuntu 20.04 (focal-preinstalled-server-arm64+raspi3.img), the rpi boots normally. Then execute an apt update/upgrade The Raspberry doesn't boot (no output on the console) Reverting the device tree to the previous version resolve the issue (a .bak is kept during the upgrade) (file bcm2710-rpi-3-b-plus.dtb for Raspberry 3b+, bcm2711-rpi-4-b.dtb for Rpi 4b) package linux-modules-5.4.0-1004-raspi2 $ cat /etc/os-release NAME="Ubuntu" VERSION="20.04 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu Focal Fossa (development branch)" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=focal UBUNTU_CODENAME=focal $ dpkg -S bcm2710-rpi-3-b-plus.dtb linux-modules-5.4.0-1004-raspi2: /lib/firmware/5.4.0-1004-raspi2/device-tree/broadcom/bcm2710-rpi-3-b-plus.dtb linux-modules-5.4.0-1001-raspi2: /lib/firmware/5.4.0-1001-raspi2/device-tree/broadcom/bcm2710-rpi-3-b-plus.dtb linux-modules-5.3.0-1017-raspi2: /lib/firmware/5.3.0-1017-raspi2/device-tree/broadcom/bcm2710-rpi-3-b-plus.dtb $ apt show linux-modules-5.4.0-1004-raspi2 Package: linux-modules-5.4.0-1004-raspi2 Version: 5.4.0-1004.4 Priority: optional Section: universe/kernel Source: linux-raspi2 Origin: Ubuntu Maintainer: Ubuntu Kernel Team Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 176 MB Download-Size: 29.9 MB APT-Manual-Installed: no APT-Sources: http://ports.ubuntu.com/ubuntu-ports focal/universe arm64 Packages Description: Linux kernel extra modules for version 5.4.0 on ARMv8 SMP Contains the corresponding System.map file, the modules built by the packager, and scripts that try to ensure that the system is not left in an unbootable state after an update. . Supports Generic processors. . Geared toward desktop and server systems. . You likely do not want to install this package directly. Instead, install the linux-raspi2 meta-package, which will ensure that upgrades work correctly, and that supporting packages are also installed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1868222/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835531] Re: [20.04 FEAT] Base KVM setup for secure guests - kernel part
--- Comment From cborn...@de.ibm.com 2020-03-25 04:28 EDT--- further testing looks good. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835531 Title: [20.04 FEAT] Base KVM setup for secure guests - kernel part Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Committed Bug description: Enable KVM guests to start and control a guest running in secure mode. With that Customers can securely run sensitive workloads in KVM on premise and in the cloud. Feature Request for kernel contribution Target kernel will be 5.3. Currently not available. Git-commit / backport will be provided To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1835531/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1868693] Re: Incorrect advertise flags in bluetooth beacon using BlueZ
OK. I can't tell yet but in case this bug is caused by your Bluetooth driver I'll also include the kernel here. ** Changed in: bluez (Ubuntu) Status: Incomplete => New ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1868693 Title: Incorrect advertise flags in bluetooth beacon using BlueZ Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: I tried the following on bluex version 5.48 and 5.52. I have set ControllerMode to "le" in main.conf. Using bluetootctl, when i turn on the advertisement using command "advertise on" , I get 0x02 advertisement flag. which means "BR/EDR Not Supported" (Bit 2) is not set. Now , if i restart the bluetooth service, and turn on the advertisement again, I get 0x06 advertisement flags. Here is my main.conf [General]# Default adaper name # Defaults to 'BlueZ X.YZ' #Name = BlueZ# Default device class. Only the major and minor device class bits are # considered. Defaults to '0x00'. Class = 0x000100# How long to stay in discoverable mode before going back to non-discoverable # The value is in seconds. Default is 180, i.e. 3 minutes. # 0 = disable timer, i.e. stay discoverable forever DiscoverableTimeout = 0# How long to stay in pairable mode before going back to non-discoverable # The value is in seconds. Default is 0. # 0 = disable timer, i.e. stay pairable forever #PairableTimeout = 0# Automatic connection for bonded devices driven by platform/user events. # If a platform plugin uses this mechanism, automatic connections will be # enabled during the interval defined below. Initially, this feature # intends to be used to establish connections to ATT channels. Default is 60. #AutoConnectTimeout = 60# Use vendor id source (assigner), vendor, product and version information for # DID profile support. The values are separated by ":" and assigner, VID, PID # and version. # Possible vendor id source values: bluetooth, usb (defaults to usb) #DeviceID = bluetooth:1234:5678:abcd# Do reverse service discovery for previously unknown devices that connect to # us. This option is really only needed for qualification since the BITE tester # doesn't like us doing reverse SDP for some test cases (though there could in # theory be other useful purposes for this too). Defaults to 'true'. #ReverseServiceDiscovery = true# Enable name resolving after inquiry. Set it to 'false' if you don't need # remote devices name and want shorter discovery cycle. Defaults to 'true'. #NameResolving = true# Enable runtime persistency of debug link keys. Default is false which # makes debug link keys valid only for the duration of the connection # that they were created for. #DebugKeys = false# Restricts all controllers to the specified transport. Default value # is "dual", i.e. both BR/EDR and LE enabled (when supported by the HW). # Possible values: "dual", "bredr", "le" ControllerMode = le# Enables Multi Profile Specification support. This allows to specify if # system supports only Multiple Profiles Single Device (MPSD) configuration # or both Multiple Profiles Single Device (MPSD) and Multiple Profiles Multiple # Devices (MPMD) configurations. # Possible values: "off", "single", "multiple" #MultiProfile = off# Permanently enables the Fast Connectable setting for adapters that # support it. When enabled other devices can connect faster to us, # however the tradeoff is increased power consumptions. This feature # will fully work only on kernel version 4.1 and newer. Defaults to # 'false'. #FastConnectable = false[Policy]# The ReconnectUUIDs defines the set of remote services that should try # to be reconnected to in case of a link loss (link supervision # timeout). The policy plugin should contain a sane set of values by # default, but this list can be overridden here. By setting the list to # empty the reconnection feature gets disabled. #ReconnectUUIDs=1112--1000-8000-00805f9b34fb, 111f--1000-8000-00805f9b34fb, 110a--1000-8000-00805f9b34fb# ReconnectAttempts define the number of attempts to reconnect after a link # lost. Setting the value to 0 disables reconnecting feature. #ReconnectAttempts=7# ReconnectIntervals define the set of intervals in seconds to use in between # attempts. # If the number of attempts defined in ReconnectAttempts is bigger than the # set of intervals the last interval is repeated until the last attempt. #ReconnectIntervals=1, 2, 4, 8, 16, 32, 64# AutoEnable defines option to enable all controllers when they are found. # This includes adapters present on start as well as adapters that are plugged # in later on. Defaults to 'false'. AutoEnable=true And bluetooth.se
[Kernel-packages] [Bug 1865570] Re: suspend only works once on ThinkPad X1 Carbon gen 7
@mapengyu, I've rebuilt e1000e.ko with your patch applied to 5.6.0-rc5 tree, and suspend works normally for me: Linux journex 5.6.0-rc5+ #2 SMP Sun Mar 15 00:09:19 CET 2020 x86_64 x86_64 x86_64 GNU/Linux First suspend: [ 66.578525] PM: suspend entry (s2idle) [ 66.582870] Filesystems sync: 0.004 seconds [ 66.583640] Freezing user space processes ... (elapsed 0.002 seconds) done. [ 66.585841] OOM killer disabled. [ 66.585842] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 66.587085] printk: Suspending console(s) (use no_console_suspend to debug) [ 66.587375] wlp0s20f3: deauthenticating from 18:d6:c7:61:95:c2 by local choice (Reason: 3=DEAUTH_LEAVING) [ 66.691969] e1000e: EEE TX LPI TIMER: 0011 [ 69.395364] ACPI: EC: interrupt blocked [ 79.252679] ACPI: EC: interrupt unblocked [ 82.053040] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM [ 82.169363] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM [ 82.234288] iwlwifi :00:14.3: FW already configured (0) - re-configuring [ 85.251055] OOM killer enabled. [ 85.251056] Restarting tasks ... done. [ 85.260141] mei_hdcp :00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound :00:02.0 (ops i915_hdcp_component_ops [i915]) [ 85.293929] PM: suspend exit [ 85.391753] e1000e :00:1f.6 enp0s31f6: NIC Link is Down [ 85.627128] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM ... Second suspend: [ 140.523471] PM: suspend entry (s2idle) [ 140.554018] Filesystems sync: 0.030 seconds [ 140.554655] Freezing user space processes ... (elapsed 0.002 seconds) done. [ 140.556773] OOM killer disabled. [ 140.556773] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 140.558014] printk: Suspending console(s) (use no_console_suspend to debug) [ 140.558275] wlp0s20f3: deauthenticating from 18:d6:c7:61:95:c2 by local choice (Reason: 3=DEAUTH_LEAVING) [ 140.659976] e1000e: EEE TX LPI TIMER: 0011 [ 143.380606] ACPI: EC: interrupt blocked [ 158.716081] ACPI: EC: interrupt unblocked [ 161.516454] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM [ 161.866014] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM [ 161.933414] iwlwifi :00:14.3: FW already configured (0) - re-configuring [ 164.586442] OOM killer enabled. [ 164.586443] Restarting tasks ... [ 164.592488] mei_hdcp :00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound :00:02.0 (ops i915_hdcp_component_ops [i915]) [ 164.592743] done. [ 164.637623] PM: suspend exit [ 164.735062] e1000e :00:1f.6 enp0s31f6: NIC Link is Down [ 164.999601] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM ... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1865570 Title: suspend only works once on ThinkPad X1 Carbon gen 7 Status in linux package in Ubuntu: Triaged Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: Won't Fix Status in linux-oem-osp1 source package in Bionic: New Status in linux source package in Eoan: New Status in linux-oem-osp1 source package in Eoan: Won't Fix Status in linux source package in Focal: Triaged Status in linux-oem-osp1 source package in Focal: Won't Fix Bug description: === SRU Justification === [Impact] Lenovo X1 Carbon 7th can only susped (s2idle) once, subsquent suspends are blocked by failed e1000e resume routine. [Fix] It's not root caused yet by Intel, so disable the s0ix flow on X1 Carbon 7th as a temporary workaround. [Test] After applying the DMI quirk patch, e1000e keeps working, so it doesn't block s2idle anymore. User also confimred the workaround works. [Regression Potential] Low. It limits to a specific model, and I can confirm s0ix can still be reached withouth this feature. === Original Bug Report === 5.4.0-16 and 5.4.0-17 go to suspend when the lid is closed, but *only once* after boot. On subsequent attempts, when the lid it closed, backlight and wifi are turned off, but system does not suspend. First successful suspend: [ 147.413295] PM: suspend entry (s2idle) [ 147.416601] Filesystems sync: 0.003 seconds [ 147.419371] Freezing user space processes ... (elapsed 0.001 seconds) done. [ 147.421210] OOM killer disabled. [ 147.421210] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 147.422375] printk: Suspending console(s) (use no_console_suspend to debug) [ 147.422630] wlp0s20f3: deauthenticating from 18:d6:c7:61:95:c2 by local choice (Reason: 3=DEAUTH_LEAVING) [ 147.527810] e1000e: EEE TX LPI TIMER: 0011 [ 150.246317] ACPI: EC: interrupt blocked [ 881.134544] ACPI: EC: interrupt unblocked [ 883.933255] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM [ 884.047802] iwlwifi :00:14.3: Applying debug destinatio
[Kernel-packages] [Bug 1813136] Re: dscr_sysfs_test in powerpc/dscr from ubuntu_kernel_selftests failed with Power9 on B/C/D
On Bionic P9, this issue still exist on P9. On Eoan P9, it's now: not ok 6 selftests: dscr: dscr_sysfs_test # TIMEOUT ** Tags added: sru-20200316 ** 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/1813136 Title: dscr_sysfs_test in powerpc/dscr from ubuntu_kernel_selftests failed with Power9 on B/C/D Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Status in linux source package in Cosmic: Confirmed Status in linux source package in Disco: Confirmed Bug description: This issue can be found on Power9 with Bionic / Cosmic kernel $ sudo ./dscr_sysfs_test test: dscr_sysfs_test tags: git_version:c186097-dirty !! killing dscr_sysfs_test !! child died by signal 15 failure: dscr_sysfs_test Passed on Power8 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-44-generic 4.15.0-44.47 ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18 Uname: Linux 4.15.0-44-generic ppc64le AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 24 07:22 seq crw-rw 1 root audio 116, 33 Jan 24 07:22 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Jan 24 09:29:00 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0451:80ff Texas Instruments, Inc. Bus 001 Device 004: ID 0557:2419 ATEN International Co., Ltd Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub PciMultimedia: ProcFB: 0 astdrmfb ProcKernelCmdLine: root=UUID=acd1a0d7-f6fc-4130-928c-c8b11ad6e4be ro console=hvc0 ProcLoadAvg: 0.26 0.07 0.11 3/1363 35034 ProcLocks: 1: FLOCK ADVISORY WRITE 3482 00:17:520 0 EOF 2: POSIX ADVISORY WRITE 3746 00:17:580 0 EOF 3: POSIX ADVISORY WRITE 1800 00:17:368 0 EOF 4: FLOCK ADVISORY WRITE 3744 00:17:568 0 EOF 5: POSIX ADVISORY WRITE 3831 00:17:588 0 EOF ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -2 ProcVersion: Linux version 4.15.0-44-generic (buildd@bos02-ppc64el-004) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #47-Ubuntu SMP Mon Jan 14 11:26:40 UTC 2019 RelatedPackageVersions: linux-restricted-modules-4.15.0-44-generic N/A linux-backports-modules-4.15.0-44-generic N/A linux-firmware 1.173.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) VarLogDump_list: total 0 cpu_cores: Number of cores present = 40 cpu_coreson: Number of cores online = 40 cpu_dscr: DSCR is 5 cpu_freq: min: 2.862 GHz (cpu 159) max: 2.862 GHz (cpu 3) avg: 2.862 GHz cpu_runmode: Could not retrieve current diagnostics mode, No kernel interface to firmware cpu_smt: SMT=4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1813136/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1868936] [NEW] [ICL] TC port in legacy/static mode can't be detected due TCCOLD
Public bug reported: When ICL SoC is in PC10, hotplugging HDMI adapter to Type-C DP, port can't be detected: "Port C/TC#1: PHY in TCCOLD, nothing connected" The issue doesn't happen when SoC is not in PC10. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-meera+X40 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-03-18 (7 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: bionic Uname: Linux 5.6.0-050600rc5-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected bionic ** Tags added: apport-collected bionic ** Description changed: When ICL SoC is in PC10, hotplugging HDMI adapter to Type-C DP, port can't be detected: "Port C/TC#1: PHY in TCCOLD, nothing connected" The issue doesn't happen when SoC is not in PC10. + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.12 + Architecture: amd64 + DistributionChannelDescriptor: + # This is the distribution channel descriptor for the OEM CDs + # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor + canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-meera+X40 + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2020-03-18 (7 days ago) + InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash + Tags: bionic + Uname: Linux 5.6.0-050600rc5-generic x86_64 + UnreportableReason: The running kernel is not an Ubuntu kernel + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: True -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1868936 Title: [ICL] TC port in legacy/static mode can't be detected due TCCOLD Status in linux package in Ubuntu: New Bug description: When ICL SoC is in PC10, hotplugging HDMI adapter to Type-C DP, port can't be detected: "Port C/TC#1: PHY in TCCOLD, nothing connected" The issue doesn't happen when SoC is not in PC10. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-meera+X40 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-03-18 (7 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: bionic Uname: Linux 5.6.0-050600rc5-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868936/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1868936] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1868936/+attachment/5341349/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1868936 Title: [ICL] TC port in legacy/static mode can't be detected due TCCOLD Status in linux package in Ubuntu: New Bug description: When ICL SoC is in PC10, hotplugging HDMI adapter to Type-C DP, port can't be detected: "Port C/TC#1: PHY in TCCOLD, nothing connected" The issue doesn't happen when SoC is not in PC10. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-meera+X40 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-03-18 (7 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: bionic Uname: Linux 5.6.0-050600rc5-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868936/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1868693] 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 bluez in Ubuntu. https://bugs.launchpad.net/bugs/1868693 Title: Incorrect advertise flags in bluetooth beacon using BlueZ Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: I tried the following on bluex version 5.48 and 5.52. I have set ControllerMode to "le" in main.conf. Using bluetootctl, when i turn on the advertisement using command "advertise on" , I get 0x02 advertisement flag. which means "BR/EDR Not Supported" (Bit 2) is not set. Now , if i restart the bluetooth service, and turn on the advertisement again, I get 0x06 advertisement flags. Here is my main.conf [General]# Default adaper name # Defaults to 'BlueZ X.YZ' #Name = BlueZ# Default device class. Only the major and minor device class bits are # considered. Defaults to '0x00'. Class = 0x000100# How long to stay in discoverable mode before going back to non-discoverable # The value is in seconds. Default is 180, i.e. 3 minutes. # 0 = disable timer, i.e. stay discoverable forever DiscoverableTimeout = 0# How long to stay in pairable mode before going back to non-discoverable # The value is in seconds. Default is 0. # 0 = disable timer, i.e. stay pairable forever #PairableTimeout = 0# Automatic connection for bonded devices driven by platform/user events. # If a platform plugin uses this mechanism, automatic connections will be # enabled during the interval defined below. Initially, this feature # intends to be used to establish connections to ATT channels. Default is 60. #AutoConnectTimeout = 60# Use vendor id source (assigner), vendor, product and version information for # DID profile support. The values are separated by ":" and assigner, VID, PID # and version. # Possible vendor id source values: bluetooth, usb (defaults to usb) #DeviceID = bluetooth:1234:5678:abcd# Do reverse service discovery for previously unknown devices that connect to # us. This option is really only needed for qualification since the BITE tester # doesn't like us doing reverse SDP for some test cases (though there could in # theory be other useful purposes for this too). Defaults to 'true'. #ReverseServiceDiscovery = true# Enable name resolving after inquiry. Set it to 'false' if you don't need # remote devices name and want shorter discovery cycle. Defaults to 'true'. #NameResolving = true# Enable runtime persistency of debug link keys. Default is false which # makes debug link keys valid only for the duration of the connection # that they were created for. #DebugKeys = false# Restricts all controllers to the specified transport. Default value # is "dual", i.e. both BR/EDR and LE enabled (when supported by the HW). # Possible values: "dual", "bredr", "le" ControllerMode = le# Enables Multi Profile Specification support. This allows to specify if # system supports only Multiple Profiles Single Device (MPSD) configuration # or both Multiple Profiles Single Device (MPSD) and Multiple Profiles Multiple # Devices (MPMD) configurations. # Possible values: "off", "single", "multiple" #MultiProfile = off# Permanently enables the Fast Connectable setting for adapters that # support it. When enabled other devices can connect faster to us, # however the tradeoff is increased power consumptions. This feature # will fully work only on kernel version 4.1 and newer. Defaults to # 'false'. #FastConnectable = false[Policy]# The ReconnectUUIDs defines the set of remote services that should try # to be reconnected to in case of a link loss (link supervision # timeout). The policy plugin should contain a sane set of values by # default, but this list can be overridden here. By setting the list to # empty the reconnection feature gets disabled. #ReconnectUUIDs=1112--1000-8000-00805f9b34fb, 111f--1000-8000-00805f9b34fb, 110a--1000-8000-00805f9b34fb# ReconnectAttempts define the number of attempts to reconnect after a link # lost. Setting the value to 0 disables reconnecting feature. #ReconnectAttempts=7# ReconnectIntervals define the set of intervals in seconds to use in between # attempts. # If the number of attempts defined in ReconnectAttempts is bigger than the # set of intervals the last interval is repeated until the last attempt. #ReconnectIntervals=1, 2, 4, 8, 16, 32, 64# AutoEnable defines option to enable all controllers when they are found. # This includes adapters present on start as well as adapters that are plugged # in later on. Defaults to 'false'. AutoEnable=true And bluetooth.service [Unit] Description=Bluetooth service Documentation=man:bluetoothd(8) ConditionPathIsDirectory=/sys/class/bluetooth[Service] Type=dbus
[Kernel-packages] [Bug 1862706] Re: segfaults, dpkg script failures
** Changed in: zfs-linux (Ubuntu) Importance: Medium => Low -- 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/1862706 Title: segfaults, dpkg script failures Status in zfs-linux package in Ubuntu: Incomplete Bug description: Hello, I had some apt install failures due to zfs segfaults during zfs postinst scripts: sarnold@millbarge:/var/lib$ sudo apt install -f Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: ebtables libbrlapi0.6 libenchant1c2a libgspell-1-1 libxen-4.9 libxenstore3.0 linux-headers-5.3.0-29 linux-headers-5.3.0-29-generic linux-image-5.3.0-29-generic linux-modules-5.3.0-29-generic linux-modules-extra-5.3.0-29-generic linux-tools-5.3.0-29 linux-tools-5.3.0-29-generic python3-asn1crypto Use 'sudo apt autoremove' to remove them. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 3 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Setting up zfsutils-linux (0.8.3-1ubuntu3) ... zfs-import-scan.service is a disabled or a static unit, not starting it. zfs-import-scan.service is a disabled or a static unit, not starting it. Job for zfs-mount.service failed because the control process exited with error code. See "systemctl status zfs-mount.service" and "journalctl -xe" for details. invoke-rc.d: initscript zfs-mount, action "start" failed. ● zfs-mount.service - Mount ZFS filesystems Loaded: loaded (/lib/systemd/system/zfs-mount.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Tue 2020-02-11 00:46:19 UTC; 5ms ago Docs: man:zfs(8) Process: 2770075 ExecStart=/sbin/zfs mount -a (code=exited, status=1/FAILURE) Main PID: 2770075 (code=exited, status=1/FAILURE) Feb 11 00:46:19 millbarge systemd[1]: Starting Mount ZFS filesystems... Feb 11 00:46:19 millbarge zfs[2770075]: cannot mount '/var/lib/AccountsService': Feb 11 00:46:19 millbarge zfs[2770075]: cannot mount '/var/lib/AccountsService': mount failed Feb 11 00:46:19 millbarge systemd[1]: zfs-mount.service: Main process exited, code=exited, status=1/FAILURE Feb 11 00:46:19 millbarge systemd[1]: zfs-mount.service: Failed with result 'exit-code'. Feb 11 00:46:19 millbarge systemd[1]: Failed to start Mount ZFS filesystems. dpkg: error processing package zfsutils-linux (--configure): installed zfsutils-linux package post-installation script subprocess returned error exit status 1 No apport report written because the error message indicates its a followup error from a previous failure. dpkg: dependency problems prevent configuration of zfs-initramfs: zfs-initramfs depends on zfsutils-linux (>= 0.8.3-1ubuntu3); however: Package zfsutils-linux is not configured yet. dpkg: error processing package zfs-initramfs (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of zfs-zed: zfs-zed depends on zfsutils-linux (>= 0.8.3-1ubuntu3); however: Package zfsutils-linux is not configured yet. dpkg: error processing package zfs-zed (--configure): dependency problems - leaving unconfigured No apport report written because the error message indicates its a followup error from a previous failure. Errors were encountered while processing: zfsutils-linux zfs-initramfs zfs-zed E: Sub-process /usr/bin/dpkg returned an error code (1) sarnold@millbarge:/var/lib$ sudo dmesg | tail -30 [345819.461404] pci_bus :06: Allocating resources [345819.461422] pcieport :06:01.0: bridge window [mem 0x0010-0x000f] to [bus 08-3a] add_size 40 add_align 10 [345819.461424] pcieport :06:04.0: bridge window [mem 0x0010-0x000f] to [bus 3c-6f] add_size 40 add_align 10 [345819.461428] pcieport :06:01.0: BAR 14: no space for [mem size 0x0040] [345819.461428] pcieport :06:01.0: BAR 14: failed to assign [mem size 0x0040] [345819.461429] pcieport :06:04.0: BAR 14: no space for [mem size 0x0040] [345819.461430] pcieport :06:04.0: BAR 14: failed to assign [mem size 0x0040] [345819.461431] pcieport :06:04.0: BAR 14: no space for [mem size 0x0040] [345819.461432] pcieport :06:04.0: BAR 14: failed to assign [mem size 0x0040] [345819.461432] pcieport :06:01.0: BAR 14: no space for [mem size 0x0040] [345819.461433] pcieport :06:01.0: BAR 14: failed to assign [mem size 0x0040] [345833.001361] show_signal_msg: 34 callbacks sup
[Kernel-packages] [Bug 1868936] Re: [ICL] TC port in legacy/static mode can't be detected due TCCOLD
Upstream bug: https://gitlab.freedesktop.org/drm/intel/issues/1296 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1868936 Title: [ICL] TC port in legacy/static mode can't be detected due TCCOLD Status in linux package in Ubuntu: New Bug description: When ICL SoC is in PC10, hotplugging HDMI adapter to Type-C DP, port can't be detected: "Port C/TC#1: PHY in TCCOLD, nothing connected" The issue doesn't happen when SoC is not in PC10. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-meera+X40 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-03-18 (7 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: bionic Uname: Linux 5.6.0-050600rc5-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868936/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1866196] Re: hugeshmctl01 from hugetlb in ubuntu_ltp failed on B / E
Passed with Eoan AMD64, ARM64, P8/P9, s390x Closing this issue. ** Changed in: ubuntu-kernel-tests Status: New => Fix Released ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1866196 Title: hugeshmctl01 from hugetlb in ubuntu_ltp failed on B / E Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Invalid Bug description: Issue found on Bionic, across amd64 / arm64 / i386 / P8 / s390x <<>> tag=hugeshmctl01 stime=1583419276 cmdline="hugeshmctl01 -i 5" contacts="" analysis=exit <<>> incrementing stop tst_test.c:1229: INFO: Timeout per run is 0h 05m 00s mem.c:817: INFO: set nr_hugepages to 128 hugeshmctl01.c:198: PASS: pid, size, # of attaches and mode are correct - pass #0 hugeshmctl01.c:198: PASS: pid, size, # of attaches and mode are correct - pass #1 hugeshmctl01.c:263: PASS: new mode and change time are correct hugeshmctl01.c:280: PASS: shmctl in func_rmid() failed as expected, shared memory appears to be removed tst_checkpoint.c:149: BROK: hugeshmctl01.c:152: tst_checkpoint_wait(0, 1): ETIMEDOUT (110) mem.c:817: INFO: set nr_hugepages to 0 Summary: passed 4 failed 0 skipped 0 warnings 0 <<>> initiation_status="ok" duration=11 termination_type=exited termination_id=2 corefile=no cutime=0 cstime=0 <<>> dmesg on s2lp3: [84600.210919] BUG: non-zero pgtables_bytes on freeing mm: 16384 [84600.211628] BUG: non-zero pgtables_bytes on freeing mm: 16384 [84601.361848] LTP: starting hugeshmctl01 (hugeshmctl01 -i 5) [84602.435421] User process fault: interruption code 003b ilc:2 in hugeshmctl01[2aa33f0+25000] [84602.435435] Failing address: 0200 TEID: 02000400 [84602.435437] Fault in primary space mode while using user ASCE. [84602.435439] AS:00079ec141c7 R3:0024 [84602.435444] CPU: 3 PID: 74199 Comm: hugeshmctl01 Tainted: P O 4.15.0-91-generic #92-Ubuntu [84602.435445] Hardware name: IBM 2964 N63 400 (LPAR) [84602.435447] User PSW : a994e531 a60b6ea2 [84602.435449]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:1 AS:0 CC:2 PM:0 RI:0 EA:3 [84602.435450] User GPRS: 02aa0002 0004 [84602.435451]02aa33f06602 03ffb679ecf8 [84602.435452]03ff0002 02aa 02aa 0200 [84602.435453]03ffb69a6000 02aa33f1b300 02aa33f06602 03ffd6d7dfa8 [84602.435462] User Code: 02aa33f06640: e3101012 lt %r1,0(%r1) 02aa33f06646: a7840038 brc 8,02aa33f066b6 #02aa33f0664a: c4b80001061b lgrl %r11,02aa33f27280 >02aa33f06650: 50a0b000 st %r10,0(%r11) 02aa33f06654: a7690001 lghi%r6,1 02aa33f06658: a759 lghi%r5,0 02aa33f0665c: a749 lghi%r4,0 02aa33f06660: a739008d lghi%r3,141 [84602.435472] Last Breaking-Event-Address: [84602.435476] [<02aa33f06602>] 0x2aa33f06602 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-91-generic 4.15.0-91.92 ProcVersionSignature: Ubuntu 4.15.0-91.92-generic 4.15.18 Uname: Linux 4.15.0-91-generic s390x NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.11 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Thu Mar 5 14:41:35 2020 HibernationDevice: RESUME=UUID=e2735dd1-cbbc-4424-9c25-d37d073d9414 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=UUID=38f7d570-2973-4055-b668-12a9ace1e0c7 crashkernel=196M audit=0 BOOT_IMAGE=0 RelatedPackageVersions: linux-restricted-modules-4.15.0-91-generic N/A linux-backports-modules-4.15.0-91-generic N/A linux-firmware 1.173.16 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manag
[Kernel-packages] [Bug 1868936] Re: [ICL] TC port in legacy/static mode can't be detected due TCCOLD
** Attachment added: "dmesg.5.6.0-050600rc5-generic" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868936/+attachment/5341350/+files/dmesg.5.6.0-050600rc5-generic ** Bug watch added: gitlab.freedesktop.org/drm/intel/issues #1296 https://gitlab.freedesktop.org/drm/intel/issues/1296 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1868936 Title: [ICL] TC port in legacy/static mode can't be detected due TCCOLD Status in linux package in Ubuntu: New Bug description: When ICL SoC is in PC10, hotplugging HDMI adapter to Type-C DP, port can't be detected: "Port C/TC#1: PHY in TCCOLD, nothing connected" The issue doesn't happen when SoC is not in PC10. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-meera+X40 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-03-18 (7 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: bionic Uname: Linux 5.6.0-050600rc5-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868936/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1868626] Re: Allow BPF tracing under lockdown
** Changed in: linux (Ubuntu Eoan)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1868626
Title:
Allow BPF tracing under lockdown
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Eoan:
Fix Committed
Bug description:
[Impact]
BPF tracing is allowed on Bionic and on Focal under integrity lockdown, which
is going to be the default before release. Right now, Eoan does not allow
kprobes and BPF reads under lockdown, preventing BPF tracing and kprobe tracing.
[Test case]
sudo bpftrace -e 'kprobe:do_nanosleep { printf("PID %d sleeping...\n", pid);
}'
sudo bpftrace -e 'tracepoint:syscalls:sys_enter_openat { printf("filename:
[%s]; flags: [%d]\n", str(args->filename), args->flags); }'
The last one should show the filename and flags.
[Regression potential]
This would allow privileged users to possibly read some kernel data that was
not possible before. However, this is already possible on systems that are not
under lockdown, which are all non-secure boot systems by default. This also
matches the behavior of signed kernels of Bionic and Focal.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868626/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1868936] Re: [ICL] TC port in legacy/static mode can't be detected due TCCOLD
** Tags added: oem-priority originate-from-1862116 somerville -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1868936 Title: [ICL] TC port in legacy/static mode can't be detected due TCCOLD Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: When ICL SoC is in PC10, hotplugging HDMI adapter to Type-C DP, port can't be detected: "Port C/TC#1: PHY in TCCOLD, nothing connected" The issue doesn't happen when SoC is not in PC10. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-meera+X40 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-03-18 (7 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: bionic Uname: Linux 5.6.0-050600rc5-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1868936/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835531] Comment bridged from LTC Bugzilla
--- Comment From mihaj...@de.ibm.com 2020-03-25 05:14 EDT--- I can confirm, upgrade went seamlessly. Everything looks good. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835531 Title: [20.04 FEAT] Base KVM setup for secure guests - kernel part Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Committed Bug description: Enable KVM guests to start and control a guest running in secure mode. With that Customers can securely run sensitive workloads in KVM on premise and in the cloud. Feature Request for kernel contribution Target kernel will be 5.3. Currently not available. Git-commit / backport will be provided To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1835531/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835531] Re: [20.04 FEAT] Base KVM setup for secure guests - kernel part
Many thx for test, verification and feedback, Christian! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835531 Title: [20.04 FEAT] Base KVM setup for secure guests - kernel part Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Committed Bug description: Enable KVM guests to start and control a guest running in secure mode. With that Customers can securely run sensitive workloads in KVM on premise and in the cloud. Feature Request for kernel contribution Target kernel will be 5.3. Currently not available. Git-commit / backport will be provided To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1835531/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1865570] Re: suspend only works once on ThinkPad X1 Carbon gen 7
I've just tested on Eoan with the proposed branch. It didn't resolve my issue. I'll give it some time today to see if the new kernel gets released. This is the kernel I'm running after an apt update/upgrade cycle this morning Linux MiX 5.3.0-43-generic #36-Ubuntu SMP Mon Mar 16 13:29:01 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1865570 Title: suspend only works once on ThinkPad X1 Carbon gen 7 Status in linux package in Ubuntu: Triaged Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: Won't Fix Status in linux-oem-osp1 source package in Bionic: New Status in linux source package in Eoan: New Status in linux-oem-osp1 source package in Eoan: Won't Fix Status in linux source package in Focal: Triaged Status in linux-oem-osp1 source package in Focal: Won't Fix Bug description: === SRU Justification === [Impact] Lenovo X1 Carbon 7th can only susped (s2idle) once, subsquent suspends are blocked by failed e1000e resume routine. [Fix] It's not root caused yet by Intel, so disable the s0ix flow on X1 Carbon 7th as a temporary workaround. [Test] After applying the DMI quirk patch, e1000e keeps working, so it doesn't block s2idle anymore. User also confimred the workaround works. [Regression Potential] Low. It limits to a specific model, and I can confirm s0ix can still be reached withouth this feature. === Original Bug Report === 5.4.0-16 and 5.4.0-17 go to suspend when the lid is closed, but *only once* after boot. On subsequent attempts, when the lid it closed, backlight and wifi are turned off, but system does not suspend. First successful suspend: [ 147.413295] PM: suspend entry (s2idle) [ 147.416601] Filesystems sync: 0.003 seconds [ 147.419371] Freezing user space processes ... (elapsed 0.001 seconds) done. [ 147.421210] OOM killer disabled. [ 147.421210] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 147.422375] printk: Suspending console(s) (use no_console_suspend to debug) [ 147.422630] wlp0s20f3: deauthenticating from 18:d6:c7:61:95:c2 by local choice (Reason: 3=DEAUTH_LEAVING) [ 147.527810] e1000e: EEE TX LPI TIMER: 0011 [ 150.246317] ACPI: EC: interrupt blocked [ 881.134544] ACPI: EC: interrupt unblocked [ 883.933255] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM [ 884.047802] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM [ 884.112730] iwlwifi :00:14.3: FW already configured (0) - re-configuring [ 886.815475] e1000e :00:1f.6 enp0s31f6: PHY Wakeup cause - Unicast Packet [ 887.485832] e1000e :00:1f.6 enp0s31f6: Hardware Error [ 888.016931] OOM killer enabled. [ 888.016932] Restarting tasks ... done. [ 888.060613] PM: suspend exit Second unsuccessful suspend: [ 907.584802] PM: suspend entry (s2idle) [ 907.589779] Filesystems sync: 0.004 seconds [ 907.591416] Freezing user space processes ... (elapsed 0.002 seconds) done. [ 907.593518] OOM killer disabled. [ 907.593518] Freezing remaining freezable tasks ... (elapsed 0.328 seconds) done. [ 907.921560] printk: Suspending console(s) (use no_console_suspend to debug) [ 907.922127] wlp0s20f3: deauthenticating from 18:d6:c7:61:95:c2 by local choice (Reason: 3=DEAUTH_LEAVING) [ 908.024438] e1000e: EEE TX LPI TIMER: 0011 [ 909.916364] PM: pci_pm_suspend(): e1000e_pm_suspend+0x0/0x80 [e1000e] returns -2 [ 909.916367] PM: dpm_run_callback(): pci_pm_suspend+0x0/0x150 returns -2 [ 909.916369] PM: Device :00:1f.6 failed to suspend async: error -2 [ 911.183052] PM: Some devices failed to suspend, or early wake event detected [ 911.197091] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM [ 911.314903] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM [ 911.382438] iwlwifi :00:14.3: FW already configured (0) - re-configuring [ 911.413624] OOM killer enabled. [ 911.413625] Restarting tasks ... done. [ 911.462021] PM: suspend exit It looks like Ethernet driver prevents suspend. Ethernet is not connected (I do not have the adaptor). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1865570/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1865570] Re: suspend only works once on ThinkPad X1 Carbon gen 7
Using the kernel package from -proposed makes suspend work normally as well. Linux journex 5.4.0-20-generic #24-Ubuntu SMP Mon Mar 23 20:55:46 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Though I guess that 5.4.0-20 uses the "workaround", and it may be better to apply the "proper fix" from comment 21? In any case, I am marking it "verification-done" because it does indeed work. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1865570 Title: suspend only works once on ThinkPad X1 Carbon gen 7 Status in linux package in Ubuntu: Triaged Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: Won't Fix Status in linux-oem-osp1 source package in Bionic: New Status in linux source package in Eoan: New Status in linux-oem-osp1 source package in Eoan: Won't Fix Status in linux source package in Focal: Triaged Status in linux-oem-osp1 source package in Focal: Won't Fix Bug description: === SRU Justification === [Impact] Lenovo X1 Carbon 7th can only susped (s2idle) once, subsquent suspends are blocked by failed e1000e resume routine. [Fix] It's not root caused yet by Intel, so disable the s0ix flow on X1 Carbon 7th as a temporary workaround. [Test] After applying the DMI quirk patch, e1000e keeps working, so it doesn't block s2idle anymore. User also confimred the workaround works. [Regression Potential] Low. It limits to a specific model, and I can confirm s0ix can still be reached withouth this feature. === Original Bug Report === 5.4.0-16 and 5.4.0-17 go to suspend when the lid is closed, but *only once* after boot. On subsequent attempts, when the lid it closed, backlight and wifi are turned off, but system does not suspend. First successful suspend: [ 147.413295] PM: suspend entry (s2idle) [ 147.416601] Filesystems sync: 0.003 seconds [ 147.419371] Freezing user space processes ... (elapsed 0.001 seconds) done. [ 147.421210] OOM killer disabled. [ 147.421210] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 147.422375] printk: Suspending console(s) (use no_console_suspend to debug) [ 147.422630] wlp0s20f3: deauthenticating from 18:d6:c7:61:95:c2 by local choice (Reason: 3=DEAUTH_LEAVING) [ 147.527810] e1000e: EEE TX LPI TIMER: 0011 [ 150.246317] ACPI: EC: interrupt blocked [ 881.134544] ACPI: EC: interrupt unblocked [ 883.933255] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM [ 884.047802] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM [ 884.112730] iwlwifi :00:14.3: FW already configured (0) - re-configuring [ 886.815475] e1000e :00:1f.6 enp0s31f6: PHY Wakeup cause - Unicast Packet [ 887.485832] e1000e :00:1f.6 enp0s31f6: Hardware Error [ 888.016931] OOM killer enabled. [ 888.016932] Restarting tasks ... done. [ 888.060613] PM: suspend exit Second unsuccessful suspend: [ 907.584802] PM: suspend entry (s2idle) [ 907.589779] Filesystems sync: 0.004 seconds [ 907.591416] Freezing user space processes ... (elapsed 0.002 seconds) done. [ 907.593518] OOM killer disabled. [ 907.593518] Freezing remaining freezable tasks ... (elapsed 0.328 seconds) done. [ 907.921560] printk: Suspending console(s) (use no_console_suspend to debug) [ 907.922127] wlp0s20f3: deauthenticating from 18:d6:c7:61:95:c2 by local choice (Reason: 3=DEAUTH_LEAVING) [ 908.024438] e1000e: EEE TX LPI TIMER: 0011 [ 909.916364] PM: pci_pm_suspend(): e1000e_pm_suspend+0x0/0x80 [e1000e] returns -2 [ 909.916367] PM: dpm_run_callback(): pci_pm_suspend+0x0/0x150 returns -2 [ 909.916369] PM: Device :00:1f.6 failed to suspend async: error -2 [ 911.183052] PM: Some devices failed to suspend, or early wake event detected [ 911.197091] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM [ 911.314903] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM [ 911.382438] iwlwifi :00:14.3: FW already configured (0) - re-configuring [ 911.413624] OOM killer enabled. [ 911.413625] Restarting tasks ... done. [ 911.462021] PM: suspend exit It looks like Ethernet driver prevents suspend. Ethernet is not connected (I do not have the adaptor). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1865570/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1868936] 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 1868936 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1868936 Title: [ICL] TC port in legacy/static mode can't be detected due TCCOLD Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Bug description: When ICL SoC is in PC10, hotplugging HDMI adapter to Type-C DP, port can't be detected: "Port C/TC#1: PHY in TCCOLD, nothing connected" The issue doesn't happen when SoC is not in PC10. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-meera+X40 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-03-18 (7 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: bionic Uname: Linux 5.6.0-050600rc5-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1868936/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1868936] Re: [ICL] TC port in legacy/static mode can't be detected due TCCOLD
Proposed patch series by José: https://patchwork.freedesktop.org/series/75034/ . Verified. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1868936 Title: [ICL] TC port in legacy/static mode can't be detected due TCCOLD Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Bug description: When ICL SoC is in PC10, hotplugging HDMI adapter to Type-C DP, port can't be detected: "Port C/TC#1: PHY in TCCOLD, nothing connected" The issue doesn't happen when SoC is not in PC10. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-meera+X40 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-03-18 (7 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: bionic Uname: Linux 5.6.0-050600rc5-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1868936/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1868693] Re: Incorrect advertise flags in bluetooth beacon using BlueZ
Would be useful to report to upstream bluez -- 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/1868693 Title: Incorrect advertise flags in bluetooth beacon using BlueZ Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: I tried the following on bluex version 5.48 and 5.52. I have set ControllerMode to "le" in main.conf. Using bluetootctl, when i turn on the advertisement using command "advertise on" , I get 0x02 advertisement flag. which means "BR/EDR Not Supported" (Bit 2) is not set. Now , if i restart the bluetooth service, and turn on the advertisement again, I get 0x06 advertisement flags. Here is my main.conf [General]# Default adaper name # Defaults to 'BlueZ X.YZ' #Name = BlueZ# Default device class. Only the major and minor device class bits are # considered. Defaults to '0x00'. Class = 0x000100# How long to stay in discoverable mode before going back to non-discoverable # The value is in seconds. Default is 180, i.e. 3 minutes. # 0 = disable timer, i.e. stay discoverable forever DiscoverableTimeout = 0# How long to stay in pairable mode before going back to non-discoverable # The value is in seconds. Default is 0. # 0 = disable timer, i.e. stay pairable forever #PairableTimeout = 0# Automatic connection for bonded devices driven by platform/user events. # If a platform plugin uses this mechanism, automatic connections will be # enabled during the interval defined below. Initially, this feature # intends to be used to establish connections to ATT channels. Default is 60. #AutoConnectTimeout = 60# Use vendor id source (assigner), vendor, product and version information for # DID profile support. The values are separated by ":" and assigner, VID, PID # and version. # Possible vendor id source values: bluetooth, usb (defaults to usb) #DeviceID = bluetooth:1234:5678:abcd# Do reverse service discovery for previously unknown devices that connect to # us. This option is really only needed for qualification since the BITE tester # doesn't like us doing reverse SDP for some test cases (though there could in # theory be other useful purposes for this too). Defaults to 'true'. #ReverseServiceDiscovery = true# Enable name resolving after inquiry. Set it to 'false' if you don't need # remote devices name and want shorter discovery cycle. Defaults to 'true'. #NameResolving = true# Enable runtime persistency of debug link keys. Default is false which # makes debug link keys valid only for the duration of the connection # that they were created for. #DebugKeys = false# Restricts all controllers to the specified transport. Default value # is "dual", i.e. both BR/EDR and LE enabled (when supported by the HW). # Possible values: "dual", "bredr", "le" ControllerMode = le# Enables Multi Profile Specification support. This allows to specify if # system supports only Multiple Profiles Single Device (MPSD) configuration # or both Multiple Profiles Single Device (MPSD) and Multiple Profiles Multiple # Devices (MPMD) configurations. # Possible values: "off", "single", "multiple" #MultiProfile = off# Permanently enables the Fast Connectable setting for adapters that # support it. When enabled other devices can connect faster to us, # however the tradeoff is increased power consumptions. This feature # will fully work only on kernel version 4.1 and newer. Defaults to # 'false'. #FastConnectable = false[Policy]# The ReconnectUUIDs defines the set of remote services that should try # to be reconnected to in case of a link loss (link supervision # timeout). The policy plugin should contain a sane set of values by # default, but this list can be overridden here. By setting the list to # empty the reconnection feature gets disabled. #ReconnectUUIDs=1112--1000-8000-00805f9b34fb, 111f--1000-8000-00805f9b34fb, 110a--1000-8000-00805f9b34fb# ReconnectAttempts define the number of attempts to reconnect after a link # lost. Setting the value to 0 disables reconnecting feature. #ReconnectAttempts=7# ReconnectIntervals define the set of intervals in seconds to use in between # attempts. # If the number of attempts defined in ReconnectAttempts is bigger than the # set of intervals the last interval is repeated until the last attempt. #ReconnectIntervals=1, 2, 4, 8, 16, 32, 64# AutoEnable defines option to enable all controllers when they are found. # This includes adapters present on start as well as adapters that are plugged # in later on. Defaults to 'false'. AutoEnable=true And bluetooth.service [Unit] Description=Bluetooth service Documentation=man:bluetoothd(8) ConditionPathIsDirectory=/sys/class/bluetooth[Service] Type=dbus BusName=org.bluez ExecStart=/usr/libexec/bluetoo
[Kernel-packages] [Bug 1868936] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1868936/+attachment/5341386/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1868936 Title: [ICL] TC port in legacy/static mode can't be detected due TCCOLD Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: New Status in linux-oem-osp1 source package in Bionic: New Status in linux source package in Eoan: New Status in linux-oem-osp1 source package in Eoan: New Status in linux source package in Focal: Confirmed Status in linux-oem-osp1 source package in Focal: New Bug description: When ICL SoC is in PC10, hotplugging HDMI adapter to Type-C DP, port can't be detected: "Port C/TC#1: PHY in TCCOLD, nothing connected" The issue doesn't happen when SoC is not in PC10. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-meera+X40 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-03-18 (7 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: bionic Uname: Linux 5.6.0-050600rc5-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1485 F pulseaudio u 2075 F pulseaudio DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-meera+X40 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-03-18 (7 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 MachineType: Dell Inc. Vostro 14 5401 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1043-oem-osp1 root=UUID=8b4ac39f-f5d4-442b-857d-6d656ac9a925 ro drm.debug=0xe log_buf_len=32M ProcVersionSignature: Ubuntu 5.0.0-1043.48-oem-osp1 5.0.21 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.0.0-1043-oem-osp1 N/A linux-backports-modules-5.0.0-1043-oem-osp1 N/A linux-firmware 1.173.16 Tags: bionic Uname: Linux 5.0.0-1043-oem-osp1 x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 02/27/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 89.2.7 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr89.2.7:bd02/27/2020:svnDellInc.:pnVostro145401:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 14 5401 dmi.product.sku: 09EA dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1868936/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1868936] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1868936/+attachment/5341388/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1868936 Title: [ICL] TC port in legacy/static mode can't be detected due TCCOLD Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: New Status in linux-oem-osp1 source package in Bionic: New Status in linux source package in Eoan: New Status in linux-oem-osp1 source package in Eoan: New Status in linux source package in Focal: Confirmed Status in linux-oem-osp1 source package in Focal: New Bug description: When ICL SoC is in PC10, hotplugging HDMI adapter to Type-C DP, port can't be detected: "Port C/TC#1: PHY in TCCOLD, nothing connected" The issue doesn't happen when SoC is not in PC10. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-meera+X40 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-03-18 (7 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: bionic Uname: Linux 5.6.0-050600rc5-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1485 F pulseaudio u 2075 F pulseaudio DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-meera+X40 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-03-18 (7 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 MachineType: Dell Inc. Vostro 14 5401 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1043-oem-osp1 root=UUID=8b4ac39f-f5d4-442b-857d-6d656ac9a925 ro drm.debug=0xe log_buf_len=32M ProcVersionSignature: Ubuntu 5.0.0-1043.48-oem-osp1 5.0.21 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.0.0-1043-oem-osp1 N/A linux-backports-modules-5.0.0-1043-oem-osp1 N/A linux-firmware 1.173.16 Tags: bionic Uname: Linux 5.0.0-1043-oem-osp1 x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 02/27/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 89.2.7 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr89.2.7:bd02/27/2020:svnDellInc.:pnVostro145401:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 14 5401 dmi.product.sku: 09EA dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1868936/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1868936] Re: [ICL] TC port in legacy/static mode can't be detected due TCCOLD
apport information ** Description changed: When ICL SoC is in PC10, hotplugging HDMI adapter to Type-C DP, port can't be detected: "Port C/TC#1: PHY in TCCOLD, nothing connected" The issue doesn't happen when SoC is not in PC10. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-meera+X40 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-03-18 (7 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: bionic Uname: Linux 5.6.0-050600rc5-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.12 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: gdm1485 F pulseaudio + u 2075 F pulseaudio + DistributionChannelDescriptor: + # This is the distribution channel descriptor for the OEM CDs + # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor + canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-meera+X40 + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2020-03-18 (7 days ago) + InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 + MachineType: Dell Inc. Vostro 14 5401 + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1043-oem-osp1 root=UUID=8b4ac39f-f5d4-442b-857d-6d656ac9a925 ro drm.debug=0xe log_buf_len=32M + ProcVersionSignature: Ubuntu 5.0.0-1043.48-oem-osp1 5.0.21 + PulseList: + Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied + No PulseAudio daemon running, or not running as session daemon. + RelatedPackageVersions: + linux-restricted-modules-5.0.0-1043-oem-osp1 N/A + linux-backports-modules-5.0.0-1043-oem-osp1 N/A + linux-firmware 1.173.16 + Tags: bionic + Uname: Linux 5.0.0-1043-oem-osp1 x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: True + dmi.bios.date: 02/27/2020 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: 89.2.7 + dmi.board.vendor: Dell Inc. + dmi.chassis.type: 10 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvr89.2.7:bd02/27/2020:svnDellInc.:pnVostro145401:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: + dmi.product.family: Vostro + dmi.product.name: Vostro 14 5401 + dmi.product.sku: 09EA + dmi.sys.vendor: Dell Inc. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1868936/+attachment/5341382/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1868936 Title: [ICL] TC port in legacy/static mode can't be detected due TCCOLD Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: New Status in linux-oem-osp1 source package in Bionic: New Status in linux source package in Eoan: New Status in linux-oem-osp1 source package in Eoan: New Status in linux source package in Focal: Confirmed Status in linux-oem-osp1 source package in Focal: New Bug description: When ICL SoC is in PC10, hotplugging HDMI adapter to Type-C DP, port can't be detected: "Port C/TC#1: PHY in TCCOLD, nothing connected" The issue doesn't happen when SoC is not in PC10. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-meera+X40 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-03-18 (7 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: bionic Uname: Linux 5.6.0-050600rc5-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (proba
[Kernel-packages] [Bug 1868936] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1868936/+attachment/5341384/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1868936 Title: [ICL] TC port in legacy/static mode can't be detected due TCCOLD Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: New Status in linux-oem-osp1 source package in Bionic: New Status in linux source package in Eoan: New Status in linux-oem-osp1 source package in Eoan: New Status in linux source package in Focal: Confirmed Status in linux-oem-osp1 source package in Focal: New Bug description: When ICL SoC is in PC10, hotplugging HDMI adapter to Type-C DP, port can't be detected: "Port C/TC#1: PHY in TCCOLD, nothing connected" The issue doesn't happen when SoC is not in PC10. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-meera+X40 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-03-18 (7 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: bionic Uname: Linux 5.6.0-050600rc5-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1485 F pulseaudio u 2075 F pulseaudio DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-meera+X40 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-03-18 (7 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 MachineType: Dell Inc. Vostro 14 5401 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1043-oem-osp1 root=UUID=8b4ac39f-f5d4-442b-857d-6d656ac9a925 ro drm.debug=0xe log_buf_len=32M ProcVersionSignature: Ubuntu 5.0.0-1043.48-oem-osp1 5.0.21 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.0.0-1043-oem-osp1 N/A linux-backports-modules-5.0.0-1043-oem-osp1 N/A linux-firmware 1.173.16 Tags: bionic Uname: Linux 5.0.0-1043-oem-osp1 x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 02/27/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 89.2.7 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr89.2.7:bd02/27/2020:svnDellInc.:pnVostro145401:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 14 5401 dmi.product.sku: 09EA dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1868936/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1868936] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1868936/+attachment/5341387/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1868936 Title: [ICL] TC port in legacy/static mode can't be detected due TCCOLD Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: New Status in linux-oem-osp1 source package in Bionic: New Status in linux source package in Eoan: New Status in linux-oem-osp1 source package in Eoan: New Status in linux source package in Focal: Confirmed Status in linux-oem-osp1 source package in Focal: New Bug description: When ICL SoC is in PC10, hotplugging HDMI adapter to Type-C DP, port can't be detected: "Port C/TC#1: PHY in TCCOLD, nothing connected" The issue doesn't happen when SoC is not in PC10. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-meera+X40 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-03-18 (7 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: bionic Uname: Linux 5.6.0-050600rc5-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1485 F pulseaudio u 2075 F pulseaudio DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-meera+X40 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-03-18 (7 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 MachineType: Dell Inc. Vostro 14 5401 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1043-oem-osp1 root=UUID=8b4ac39f-f5d4-442b-857d-6d656ac9a925 ro drm.debug=0xe log_buf_len=32M ProcVersionSignature: Ubuntu 5.0.0-1043.48-oem-osp1 5.0.21 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.0.0-1043-oem-osp1 N/A linux-backports-modules-5.0.0-1043-oem-osp1 N/A linux-firmware 1.173.16 Tags: bionic Uname: Linux 5.0.0-1043-oem-osp1 x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 02/27/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 89.2.7 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr89.2.7:bd02/27/2020:svnDellInc.:pnVostro145401:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 14 5401 dmi.product.sku: 09EA dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1868936/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1868936] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1868936/+attachment/5341391/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1868936 Title: [ICL] TC port in legacy/static mode can't be detected due TCCOLD Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: New Status in linux-oem-osp1 source package in Bionic: New Status in linux source package in Eoan: New Status in linux-oem-osp1 source package in Eoan: New Status in linux source package in Focal: Confirmed Status in linux-oem-osp1 source package in Focal: New Bug description: When ICL SoC is in PC10, hotplugging HDMI adapter to Type-C DP, port can't be detected: "Port C/TC#1: PHY in TCCOLD, nothing connected" The issue doesn't happen when SoC is not in PC10. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-meera+X40 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-03-18 (7 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: bionic Uname: Linux 5.6.0-050600rc5-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1485 F pulseaudio u 2075 F pulseaudio DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-meera+X40 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-03-18 (7 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 MachineType: Dell Inc. Vostro 14 5401 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1043-oem-osp1 root=UUID=8b4ac39f-f5d4-442b-857d-6d656ac9a925 ro drm.debug=0xe log_buf_len=32M ProcVersionSignature: Ubuntu 5.0.0-1043.48-oem-osp1 5.0.21 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.0.0-1043-oem-osp1 N/A linux-backports-modules-5.0.0-1043-oem-osp1 N/A linux-firmware 1.173.16 Tags: bionic Uname: Linux 5.0.0-1043-oem-osp1 x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 02/27/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 89.2.7 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr89.2.7:bd02/27/2020:svnDellInc.:pnVostro145401:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 14 5401 dmi.product.sku: 09EA dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1868936/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1868936] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1868936/+attachment/5341392/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1868936 Title: [ICL] TC port in legacy/static mode can't be detected due TCCOLD Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: New Status in linux-oem-osp1 source package in Bionic: New Status in linux source package in Eoan: New Status in linux-oem-osp1 source package in Eoan: New Status in linux source package in Focal: Confirmed Status in linux-oem-osp1 source package in Focal: New Bug description: When ICL SoC is in PC10, hotplugging HDMI adapter to Type-C DP, port can't be detected: "Port C/TC#1: PHY in TCCOLD, nothing connected" The issue doesn't happen when SoC is not in PC10. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-meera+X40 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-03-18 (7 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: bionic Uname: Linux 5.6.0-050600rc5-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1485 F pulseaudio u 2075 F pulseaudio DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-meera+X40 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-03-18 (7 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 MachineType: Dell Inc. Vostro 14 5401 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1043-oem-osp1 root=UUID=8b4ac39f-f5d4-442b-857d-6d656ac9a925 ro drm.debug=0xe log_buf_len=32M ProcVersionSignature: Ubuntu 5.0.0-1043.48-oem-osp1 5.0.21 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.0.0-1043-oem-osp1 N/A linux-backports-modules-5.0.0-1043-oem-osp1 N/A linux-firmware 1.173.16 Tags: bionic Uname: Linux 5.0.0-1043-oem-osp1 x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 02/27/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 89.2.7 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr89.2.7:bd02/27/2020:svnDellInc.:pnVostro145401:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 14 5401 dmi.product.sku: 09EA dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1868936/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1868936] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1868936/+attachment/5341383/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1868936 Title: [ICL] TC port in legacy/static mode can't be detected due TCCOLD Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: New Status in linux-oem-osp1 source package in Bionic: New Status in linux source package in Eoan: New Status in linux-oem-osp1 source package in Eoan: New Status in linux source package in Focal: Confirmed Status in linux-oem-osp1 source package in Focal: New Bug description: When ICL SoC is in PC10, hotplugging HDMI adapter to Type-C DP, port can't be detected: "Port C/TC#1: PHY in TCCOLD, nothing connected" The issue doesn't happen when SoC is not in PC10. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-meera+X40 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-03-18 (7 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: bionic Uname: Linux 5.6.0-050600rc5-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1485 F pulseaudio u 2075 F pulseaudio DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-meera+X40 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-03-18 (7 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 MachineType: Dell Inc. Vostro 14 5401 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1043-oem-osp1 root=UUID=8b4ac39f-f5d4-442b-857d-6d656ac9a925 ro drm.debug=0xe log_buf_len=32M ProcVersionSignature: Ubuntu 5.0.0-1043.48-oem-osp1 5.0.21 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.0.0-1043-oem-osp1 N/A linux-backports-modules-5.0.0-1043-oem-osp1 N/A linux-firmware 1.173.16 Tags: bionic Uname: Linux 5.0.0-1043-oem-osp1 x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 02/27/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 89.2.7 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr89.2.7:bd02/27/2020:svnDellInc.:pnVostro145401:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 14 5401 dmi.product.sku: 09EA dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1868936/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1868936] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1868936/+attachment/5341390/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1868936 Title: [ICL] TC port in legacy/static mode can't be detected due TCCOLD Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: New Status in linux-oem-osp1 source package in Bionic: New Status in linux source package in Eoan: New Status in linux-oem-osp1 source package in Eoan: New Status in linux source package in Focal: Confirmed Status in linux-oem-osp1 source package in Focal: New Bug description: When ICL SoC is in PC10, hotplugging HDMI adapter to Type-C DP, port can't be detected: "Port C/TC#1: PHY in TCCOLD, nothing connected" The issue doesn't happen when SoC is not in PC10. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-meera+X40 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-03-18 (7 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: bionic Uname: Linux 5.6.0-050600rc5-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1485 F pulseaudio u 2075 F pulseaudio DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-meera+X40 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-03-18 (7 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 MachineType: Dell Inc. Vostro 14 5401 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1043-oem-osp1 root=UUID=8b4ac39f-f5d4-442b-857d-6d656ac9a925 ro drm.debug=0xe log_buf_len=32M ProcVersionSignature: Ubuntu 5.0.0-1043.48-oem-osp1 5.0.21 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.0.0-1043-oem-osp1 N/A linux-backports-modules-5.0.0-1043-oem-osp1 N/A linux-firmware 1.173.16 Tags: bionic Uname: Linux 5.0.0-1043-oem-osp1 x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 02/27/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 89.2.7 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr89.2.7:bd02/27/2020:svnDellInc.:pnVostro145401:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 14 5401 dmi.product.sku: 09EA dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1868936/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1868936] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1868936/+attachment/5341393/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1868936 Title: [ICL] TC port in legacy/static mode can't be detected due TCCOLD Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: New Status in linux-oem-osp1 source package in Bionic: New Status in linux source package in Eoan: New Status in linux-oem-osp1 source package in Eoan: New Status in linux source package in Focal: Confirmed Status in linux-oem-osp1 source package in Focal: New Bug description: When ICL SoC is in PC10, hotplugging HDMI adapter to Type-C DP, port can't be detected: "Port C/TC#1: PHY in TCCOLD, nothing connected" The issue doesn't happen when SoC is not in PC10. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-meera+X40 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-03-18 (7 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: bionic Uname: Linux 5.6.0-050600rc5-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1485 F pulseaudio u 2075 F pulseaudio DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-meera+X40 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-03-18 (7 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 MachineType: Dell Inc. Vostro 14 5401 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1043-oem-osp1 root=UUID=8b4ac39f-f5d4-442b-857d-6d656ac9a925 ro drm.debug=0xe log_buf_len=32M ProcVersionSignature: Ubuntu 5.0.0-1043.48-oem-osp1 5.0.21 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.0.0-1043-oem-osp1 N/A linux-backports-modules-5.0.0-1043-oem-osp1 N/A linux-firmware 1.173.16 Tags: bionic Uname: Linux 5.0.0-1043-oem-osp1 x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 02/27/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 89.2.7 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr89.2.7:bd02/27/2020:svnDellInc.:pnVostro145401:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 14 5401 dmi.product.sku: 09EA dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1868936/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1868936] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1868936/+attachment/5341389/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1868936 Title: [ICL] TC port in legacy/static mode can't be detected due TCCOLD Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: New Status in linux-oem-osp1 source package in Bionic: New Status in linux source package in Eoan: New Status in linux-oem-osp1 source package in Eoan: New Status in linux source package in Focal: Confirmed Status in linux-oem-osp1 source package in Focal: New Bug description: When ICL SoC is in PC10, hotplugging HDMI adapter to Type-C DP, port can't be detected: "Port C/TC#1: PHY in TCCOLD, nothing connected" The issue doesn't happen when SoC is not in PC10. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-meera+X40 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-03-18 (7 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: bionic Uname: Linux 5.6.0-050600rc5-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1485 F pulseaudio u 2075 F pulseaudio DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-meera+X40 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-03-18 (7 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 MachineType: Dell Inc. Vostro 14 5401 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1043-oem-osp1 root=UUID=8b4ac39f-f5d4-442b-857d-6d656ac9a925 ro drm.debug=0xe log_buf_len=32M ProcVersionSignature: Ubuntu 5.0.0-1043.48-oem-osp1 5.0.21 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.0.0-1043-oem-osp1 N/A linux-backports-modules-5.0.0-1043-oem-osp1 N/A linux-firmware 1.173.16 Tags: bionic Uname: Linux 5.0.0-1043-oem-osp1 x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 02/27/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 89.2.7 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr89.2.7:bd02/27/2020:svnDellInc.:pnVostro145401:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 14 5401 dmi.product.sku: 09EA dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1868936/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1868936] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1868936/+attachment/5341385/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1868936 Title: [ICL] TC port in legacy/static mode can't be detected due TCCOLD Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: New Status in linux-oem-osp1 source package in Bionic: New Status in linux source package in Eoan: New Status in linux-oem-osp1 source package in Eoan: New Status in linux source package in Focal: Confirmed Status in linux-oem-osp1 source package in Focal: New Bug description: When ICL SoC is in PC10, hotplugging HDMI adapter to Type-C DP, port can't be detected: "Port C/TC#1: PHY in TCCOLD, nothing connected" The issue doesn't happen when SoC is not in PC10. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-meera+X40 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-03-18 (7 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: bionic Uname: Linux 5.6.0-050600rc5-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1485 F pulseaudio u 2075 F pulseaudio DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-meera+X40 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-03-18 (7 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 MachineType: Dell Inc. Vostro 14 5401 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1043-oem-osp1 root=UUID=8b4ac39f-f5d4-442b-857d-6d656ac9a925 ro drm.debug=0xe log_buf_len=32M ProcVersionSignature: Ubuntu 5.0.0-1043.48-oem-osp1 5.0.21 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.0.0-1043-oem-osp1 N/A linux-backports-modules-5.0.0-1043-oem-osp1 N/A linux-firmware 1.173.16 Tags: bionic Uname: Linux 5.0.0-1043-oem-osp1 x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 02/27/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 89.2.7 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr89.2.7:bd02/27/2020:svnDellInc.:pnVostro145401:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 14 5401 dmi.product.sku: 09EA dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1868936/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859754] Re: [SRU] add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
Sorry, I forgot to subscribe and didn't get notified. Attached is my dmesg after a clean reboot, and a screenshot of the gnome-settings in which I don't get sound notifications ** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1859754/+attachment/5341395/+files/dmesg.txt -- 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/1859754 Title: [SRU] add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines) Status in HWE Next: Fix Released Status in alsa-lib package in Ubuntu: Invalid Status in alsa-lib source package in Bionic: Fix Released Status in alsa-lib source package in Eoan: Fix Released Bug description: This ucm is only for Eoan and Bionic, for focal and future versions, we plan to integrate the ucm2 instead of this ucm, and the ucm2 depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under developing by the community, is not ready yet. [Impact] In the oem project, we have a couple of Lenovo and Dell machines which connect the digital mic to PCH directly, this design needs the new sound driver soc/sof, and this driver can't work under pulseaudio automatically, we need to integrate the ucm for the driver, then the sof dirver could work under pulseaudio and gnome. This ucm is maintained by intel audio team, and it is not upstreamed and will not be upstreamed, since the community is developing the ucm2 which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still under developing), for bionic and eoan, we have to integrate this ucm since the alsa-lib version is too low. For focal and future version, we are going to integrate the ucm2 after the ucm2 is ready. This ucm is already verified in the oem project, now it is time to put it into the stock ubuntu. [Fix] These ucm files are backported from sof_ucm1 branch of https://github.com/thesofproject/alsa-ucm-conf.git [Test Case] Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of pulseaudio, the ucm files are loaded successfully, then check the gnome-sound-setting, both output and input devices work well. [Regression Risk] Low, just add some new ucm files, and this will not affect other machines, and those new added ucm files are only used by specific machines which enable the sof driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1859754/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1868936] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1868936/+attachment/5341394/+files/WifiSyslog.txt ** Also affects: linux-oem-osp1 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: linux-oem-osp1 (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: Confirmed ** Also affects: linux-oem-osp1 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-oem-osp1 (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1868936 Title: [ICL] TC port in legacy/static mode can't be detected due TCCOLD Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: New Status in linux-oem-osp1 source package in Bionic: New Status in linux source package in Eoan: New Status in linux-oem-osp1 source package in Eoan: New Status in linux source package in Focal: Confirmed Status in linux-oem-osp1 source package in Focal: New Bug description: When ICL SoC is in PC10, hotplugging HDMI adapter to Type-C DP, port can't be detected: "Port C/TC#1: PHY in TCCOLD, nothing connected" The issue doesn't happen when SoC is not in PC10. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-meera+X40 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-03-18 (7 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: bionic Uname: Linux 5.6.0-050600rc5-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1485 F pulseaudio u 2075 F pulseaudio DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-meera+X40 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-03-18 (7 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 MachineType: Dell Inc. Vostro 14 5401 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1043-oem-osp1 root=UUID=8b4ac39f-f5d4-442b-857d-6d656ac9a925 ro drm.debug=0xe log_buf_len=32M ProcVersionSignature: Ubuntu 5.0.0-1043.48-oem-osp1 5.0.21 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.0.0-1043-oem-osp1 N/A linux-backports-modules-5.0.0-1043-oem-osp1 N/A linux-firmware 1.173.16 Tags: bionic Uname: Linux 5.0.0-1043-oem-osp1 x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 02/27/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 89.2.7 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr89.2.7:bd02/27/2020:svnDellInc.:pnVostro145401:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 14 5401 dmi.product.sku: 09EA dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1868936/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859754] Re: [SRU] add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
I encounter a few other issues which appeared since I upgraded to this setup when using a secondary screen over HDMI and a bose QCII bluetooth headset. - output automatically switches to the headset but microphone doesn't - forcing the microphone to the headset triggers switches to output (says to the HDMI in gnome settings but is in fact to speakers ) - after successfully setting both input and output to the headphones, in a google meet session where I successfully joined and am actively participating. If I try to enble presentation mode, I get a weird error where the headset gets deactivated/activated very quickly in a loop while it looks like sound alternates from headset to internal card (and meet ends up automatically muting myself). Only way out is to kill the headset. after which the system recovers. -- 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/1859754 Title: [SRU] add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines) Status in HWE Next: Fix Released Status in alsa-lib package in Ubuntu: Invalid Status in alsa-lib source package in Bionic: Fix Released Status in alsa-lib source package in Eoan: Fix Released Bug description: This ucm is only for Eoan and Bionic, for focal and future versions, we plan to integrate the ucm2 instead of this ucm, and the ucm2 depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under developing by the community, is not ready yet. [Impact] In the oem project, we have a couple of Lenovo and Dell machines which connect the digital mic to PCH directly, this design needs the new sound driver soc/sof, and this driver can't work under pulseaudio automatically, we need to integrate the ucm for the driver, then the sof dirver could work under pulseaudio and gnome. This ucm is maintained by intel audio team, and it is not upstreamed and will not be upstreamed, since the community is developing the ucm2 which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still under developing), for bionic and eoan, we have to integrate this ucm since the alsa-lib version is too low. For focal and future version, we are going to integrate the ucm2 after the ucm2 is ready. This ucm is already verified in the oem project, now it is time to put it into the stock ubuntu. [Fix] These ucm files are backported from sof_ucm1 branch of https://github.com/thesofproject/alsa-ucm-conf.git [Test Case] Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of pulseaudio, the ucm files are loaded successfully, then check the gnome-sound-setting, both output and input devices work well. [Regression Risk] Low, just add some new ucm files, and this will not affect other machines, and those new added ucm files are only used by specific machines which enable the sof driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1859754/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859754] Re: [SRU] add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
** Attachment added: "Screenshot from 2020-03-25 11-13-00.png" https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1859754/+attachment/5341396/+files/Screenshot%20from%202020-03-25%2011-13-00.png -- 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/1859754 Title: [SRU] add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines) Status in HWE Next: Fix Released Status in alsa-lib package in Ubuntu: Invalid Status in alsa-lib source package in Bionic: Fix Released Status in alsa-lib source package in Eoan: Fix Released Bug description: This ucm is only for Eoan and Bionic, for focal and future versions, we plan to integrate the ucm2 instead of this ucm, and the ucm2 depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under developing by the community, is not ready yet. [Impact] In the oem project, we have a couple of Lenovo and Dell machines which connect the digital mic to PCH directly, this design needs the new sound driver soc/sof, and this driver can't work under pulseaudio automatically, we need to integrate the ucm for the driver, then the sof dirver could work under pulseaudio and gnome. This ucm is maintained by intel audio team, and it is not upstreamed and will not be upstreamed, since the community is developing the ucm2 which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still under developing), for bionic and eoan, we have to integrate this ucm since the alsa-lib version is too low. For focal and future version, we are going to integrate the ucm2 after the ucm2 is ready. This ucm is already verified in the oem project, now it is time to put it into the stock ubuntu. [Fix] These ucm files are backported from sof_ucm1 branch of https://github.com/thesofproject/alsa-ucm-conf.git [Test Case] Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of pulseaudio, the ucm files are loaded successfully, then check the gnome-sound-setting, both output and input devices work well. [Regression Risk] Low, just add some new ucm files, and this will not affect other machines, and those new added ucm files are only used by specific machines which enable the sof driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1859754/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855954] Re: [TGL] VMD support in TGL
** Tags added: tigerlake -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1855954 Title: [TGL] VMD support in TGL Status in intel: New Status in linux package in Ubuntu: Incomplete Bug description: Description: VMD support in Tiger Lake Platform Target Kernel: TBD Target Release: 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1855954/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855399] Re: [TGL] graphics kernel support
** Tags added: tigerlake -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1855399 Title: [TGL] graphics kernel support Status in intel: New Status in linux package in Ubuntu: Incomplete Bug description: Description: This feature tracks the updates TGL graphics updates. We will submit the commit id lists since 5.4. 20.04 will use v5.4 as a base, (2109/11/25) first commit lists will be provided in 2020/01, if you need more before that, please let us know. Target Release: 20.10 Target Kernel: v5.8 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1855399/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854244] Re: [TGL][pmc_core]Need patch to support offset number 21 and 22 device LTR ignore
** Tags added: tigerlake -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854244 Title: [TGL][pmc_core]Need patch to support offset number 21 and 22 device LTR ignore Status in intel: Fix Committed Status in linux package in Ubuntu: Incomplete Bug description: Description: Intel PMC_CORE driver, the currently device LTR ignore function support covers the IP offset from 0 to 20, while e.g. tgl , which support IP offset 21 and 22 root@p-tgl02/sys/kernel/debug/pmc_core # cat ltr_show SOUTHPORT_A LTR: RAW: 0x0 Non-Snoop(ns): 0 Snoop(ns): 0 SOUTHPORT_B LTR: RAW: 0x0 Non-Snoop(ns): 0 Snoop(ns): 0 SATA LTR: RAW: 0x0 Non-Snoop(ns): 0 Snoop(ns): 0 GIGABIT_ETHERNET LTR: RAW: 0x0 Non-Snoop(ns): 0 Snoop(ns): 0 XHCI LTR: RAW: 0x9001 Non-Snoop(ns): 0 Snoop(ns): 1048576 Reserved LTR: RAW: 0x0 Non-Snoop(ns): 0 Snoop(ns): 0 ME LTR: RAW: 0x8000800 Non-Snoop(ns): 0 Snoop(ns): 0 EVA LTR: RAW: 0x0 Non-Snoop(ns): 0 Snoop(ns): 0 SOUTHPORT_C LTR: RAW: 0x0 Non-Snoop(ns): 0 Snoop(ns): 0 HD_AUDIO LTR: RAW: 0x0 Non-Snoop(ns): 0 Snoop(ns): 0 CNV LTR: RAW: 0x0 Non-Snoop(ns): 0 Snoop(ns): 0 LPSS LTR: RAW: 0x0 Non-Snoop(ns): 0 Snoop(ns): 0 SOUTHPORT_D LTR: RAW: 0x0 Non-Snoop(ns): 0 Snoop(ns): 0 SOUTHPORT_E LTR: RAW: 0x0 Non-Snoop(ns): 0 Snoop(ns): 0 CAMERA LTR: RAW: 0x0 Non-Snoop(ns): 0 Snoop(ns): 0 ESPI LTR: RAW: 0x0 Non-Snoop(ns): 0 Snoop(ns): 0 SCC LTR: RAW: 0x0 Non-Snoop(ns): 0 Snoop(ns): 0 ISH LTR: RAW: 0x0 Non-Snoop(ns): 0 Snoop(ns): 0 UFSX2 LTR: RAW: 0x0 Non-Snoop(ns): 0 Snoop(ns): 0 EMMC LTR: RAW: 0x0 Non-Snoop(ns): 0 Snoop(ns): 0 WIGIG LTR: RAW: 0x0 Non-Snoop(ns): 0 Snoop(ns): 0 CURRENT_PLATFORM LTR: RAW: 0x40201 Non-Snoop(ns): 0 Snoop(ns): 0 AGGREGATED_SYSTEM LTR: RAW: 0x7dbebf5 Non-Snoop(ns): 0 Snoop(ns): 1037312 and currently pmc_core does not support offset number 21, 22 device LTR ignore: root@p-tgl02/sys/kernel/debug/pmc_core # echo 21 > ltr_ignore -bash: echo: write error: Invalid argument root@p-tgl02/sys/kernel/debug/pmc_core # echo 22 > ltr_ignore -bash: echo: write error: Invalid argument root@p-tgl02/sys/kernel/debug/pmc_core # echo 20 > ltr_ignore root@p-tgl02/sys/kernel/debug/pmc_core # So need your help to have a patch for the offset number 21, 22 device LTR supported. Target Release: 20.04 Target Kernel: 5.7 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1854244/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1865570] Re: suspend only works once on ThinkPad X1 Carbon gen 7
About comment #23 It's won't work. I'm on Eoan, the proposed kernel is for 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/1865570 Title: suspend only works once on ThinkPad X1 Carbon gen 7 Status in linux package in Ubuntu: Triaged Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: Won't Fix Status in linux-oem-osp1 source package in Bionic: New Status in linux source package in Eoan: New Status in linux-oem-osp1 source package in Eoan: Won't Fix Status in linux source package in Focal: Triaged Status in linux-oem-osp1 source package in Focal: Won't Fix Bug description: === SRU Justification === [Impact] Lenovo X1 Carbon 7th can only susped (s2idle) once, subsquent suspends are blocked by failed e1000e resume routine. [Fix] It's not root caused yet by Intel, so disable the s0ix flow on X1 Carbon 7th as a temporary workaround. [Test] After applying the DMI quirk patch, e1000e keeps working, so it doesn't block s2idle anymore. User also confimred the workaround works. [Regression Potential] Low. It limits to a specific model, and I can confirm s0ix can still be reached withouth this feature. === Original Bug Report === 5.4.0-16 and 5.4.0-17 go to suspend when the lid is closed, but *only once* after boot. On subsequent attempts, when the lid it closed, backlight and wifi are turned off, but system does not suspend. First successful suspend: [ 147.413295] PM: suspend entry (s2idle) [ 147.416601] Filesystems sync: 0.003 seconds [ 147.419371] Freezing user space processes ... (elapsed 0.001 seconds) done. [ 147.421210] OOM killer disabled. [ 147.421210] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 147.422375] printk: Suspending console(s) (use no_console_suspend to debug) [ 147.422630] wlp0s20f3: deauthenticating from 18:d6:c7:61:95:c2 by local choice (Reason: 3=DEAUTH_LEAVING) [ 147.527810] e1000e: EEE TX LPI TIMER: 0011 [ 150.246317] ACPI: EC: interrupt blocked [ 881.134544] ACPI: EC: interrupt unblocked [ 883.933255] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM [ 884.047802] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM [ 884.112730] iwlwifi :00:14.3: FW already configured (0) - re-configuring [ 886.815475] e1000e :00:1f.6 enp0s31f6: PHY Wakeup cause - Unicast Packet [ 887.485832] e1000e :00:1f.6 enp0s31f6: Hardware Error [ 888.016931] OOM killer enabled. [ 888.016932] Restarting tasks ... done. [ 888.060613] PM: suspend exit Second unsuccessful suspend: [ 907.584802] PM: suspend entry (s2idle) [ 907.589779] Filesystems sync: 0.004 seconds [ 907.591416] Freezing user space processes ... (elapsed 0.002 seconds) done. [ 907.593518] OOM killer disabled. [ 907.593518] Freezing remaining freezable tasks ... (elapsed 0.328 seconds) done. [ 907.921560] printk: Suspending console(s) (use no_console_suspend to debug) [ 907.922127] wlp0s20f3: deauthenticating from 18:d6:c7:61:95:c2 by local choice (Reason: 3=DEAUTH_LEAVING) [ 908.024438] e1000e: EEE TX LPI TIMER: 0011 [ 909.916364] PM: pci_pm_suspend(): e1000e_pm_suspend+0x0/0x80 [e1000e] returns -2 [ 909.916367] PM: dpm_run_callback(): pci_pm_suspend+0x0/0x150 returns -2 [ 909.916369] PM: Device :00:1f.6 failed to suspend async: error -2 [ 911.183052] PM: Some devices failed to suspend, or early wake event detected [ 911.197091] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM [ 911.314903] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM [ 911.382438] iwlwifi :00:14.3: FW already configured (0) - re-configuring [ 911.413624] OOM killer enabled. [ 911.413625] Restarting tasks ... done. [ 911.462021] PM: suspend exit It looks like Ethernet driver prevents suspend. Ethernet is not connected (I do not have the adaptor). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1865570/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855399] Re: [TGL] graphics kernel support
** Attachment added: "This is kernel patchs for TigerLake" https://bugs.launchpad.net/intel/+bug/1855399/+attachment/5341431/+files/tgl_commit_20200325.list_kernv_drm-intel -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1855399 Title: [TGL] graphics kernel support Status in intel: New Status in linux package in Ubuntu: Incomplete Bug description: Description: This feature tracks the updates TGL graphics updates. We will submit the commit id lists since 5.4. 20.04 will use v5.4 as a base, (2109/11/25) first commit lists will be provided in 2020/01, if you need more before that, please let us know. Target Release: 20.10 Target Kernel: v5.8 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1855399/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834558] Re: intel_idle enable in ICL
This is the complete list for ICL 18734958e9bfbc055805d110a38dc76307eba742 239ed06d0eefc4ee351af69bd64742ada56c4bdb 4ec32d9e8e5b6d6eb4913938665d8a2388fa 75a80267410e38ab76c4ceb39753f96d72113781 77fb4e0a559a960eb36d0b2c50c781c5492577eb 987c785319b99e32602f7f86cfae3cf9b81e402b 9f3d6daf61e5156139cd05643f7f1c2a9b7b49b0 a3299182216397a0b943d2549d1997f4eba2bdd2 aa659a3fca79abd9a3ca3ddc535db631b01c9a02 bc94638886ab21f8247d3f7f39573d3feb7d8284 bff8e60a86f4960133f90ad9add9adeb082b8154 e6d4f08a677654385869ba0c39d7c9ceec47e5c5 ** Changed in: intel Status: Incomplete => 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/1834558 Title: intel_idle enable in ICL Status in intel: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: Invalid Status in linux-oem-osp1 source package in Bionic: New Bug description: Description: Support for intel_idle on Ice Lake (client) Target Release: 20.04 Target Kernel: 5.4 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1834558/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860182] Re: zpool scrub malfunction after kernel upgrade
autopkgtests tests passed - all looks sane. -- 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/1860182 Title: zpool scrub malfunction after kernel upgrade Status in zfs-linux package in Ubuntu: In Progress Status in zfs-linux source package in Bionic: Fix Committed Bug description: == SRU Request [BIONIC] == The HWE kernel on bionic provides zfs 0.8.1 driver which includes an improved scrub however, the progress stats reported by the kernel are incompatible to the 0.7.x zfs driver. == Fix == Use the new zfs 8.x pool_scan_stat_t extra fields to calculate the scan progress when using zfs 8.x kernel drivers. Add detection of the kernel module version and use an approximation to the zfs 0.8.0 progress and rate reporting for newer kernels. For 0.7.5 we can pass the larger 8.x port_scan_stat_t to 0.7.5 zfs w/o problems and ignore these new fields and continue to use the 0.7.5 rate calculations. == Test == Install the HWE kernel on Bionic, create some large ZFS pools and populate with a lot of data. Issue: sudo zpool scrub poolname and then look at the progress using sudo zpool status Without the fix, the progress stats are incorrect. With the fix the duration and rate stats as a fairly good approximation of the progress. Since the newer 0.8.x zfs does scanning now in two phases the older zfs tools will only report accurate stats for phase #2 of the scan to keep it roughly compatible with the 0.7.x zfs utils output. == Regression Potential == This is a userspace reporting fix so the zpool status output is only affected by this fix when doing a scrub, so the impact of this fix is very small and limited. I ran a zpool scrub prior to upgrading my 18.04 to the latest HWE kernel (5.3.0-26-generic #28~18.04.1-Ubuntu) and it ran properly: eric@eric-8700K:~$ zpool status pool: storagepool1 state: ONLINE scan: scrub repaired 1M in 4h21m with 0 errors on Fri Jan 17 07:01:24 2020 config: NAME STATE READ WRITE CKSUM storagepool1 ONLINE 0 0 0 mirror-0ONLINE 0 0 0 ata-WDC_WD20EZRZ-00Z5HB0_WD-WCC4M3YFRVJ3 ONLINE 0 0 0 ata-ST2000DM001-1CH164_Z1E285A4 ONLINE 0 0 0 mirror-1ONLINE 0 0 0 ata-WDC_WD20EZRZ-00Z5HB0_WD-WCC4M1DSASHD ONLINE 0 0 0 ata-ST2000DM006-2DM164_Z4ZA3ENE ONLINE 0 0 0 I ran zpool scrub after upgrading the kernel and rebooting, and now it fails to work properly. It appeared to finish in about 5 minutes but did not, and says it is going slow: eric@eric-8700K:~$ sudo zpool status pool: storagepool1 state: ONLINE scan: scrub in progress since Fri Jan 17 15:32:07 2020 1.89T scanned out of 1.89T at 589M/s, (scan is slow, no estimated time) 0B repaired, 100.00% done config: NAME STATE READ WRITE CKSUM storagepool1 ONLINE 0 0 0 mirror-0ONLINE 0 0 0 ata-WDC_WD20EZRZ-00Z5HB0_WD-WCC4M3YFRVJ3 ONLINE 0 0 0 ata-ST2000DM001-1CH164_Z1E285A4 ONLINE 0 0 0 mirror-1ONLINE 0 0 0 ata-WDC_WD20EZRZ-00Z5HB0_WD-WCC4M1DSASHD ONLINE 0 0 0 ata-ST2000DM006-2DM164_Z4ZA3ENE ONLINE 0 0 0 errors: No known data errors ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: zfsutils-linux 0.7.5-1ubuntu16.7 ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jan 17 16:22:01 2020 InstallationDate: Installed on 2018-03-07 (681 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) SourcePackage: zfs-linux UpgradeStatus: Upgraded to bionic on 2018-08-02 (533 days ago) modified.conffile..etc.sudoers.d.zfs: [inaccessible: [Errno 13] Permission denied: '/etc/sudoers.d/zfs'] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1860182/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1866866] Re: [FFe] Please accept patches for secure guest feature
With the FFe granted for s390x-tools in comment #11 (thx for that) and the kernel patches having landed in proposed (5.4.0.20), about 2/3 of the overall FFe is now completed. Having the beta freeze on April the 2nd in mind, and the good progress on testing the patched qemu version that was made available via PPA (protvirt testing by IBM and regression testing by Canonical) and the fact that Cornelia Huck (s390 qemu maintainer) finally allowed the patches to be queued for s390-next (LP 1835546), I'm wondering if the qemu part of this FFe is now acceptable as well, or if additional effort or more time is needed. @ 'Ubuntu Release Team' would you mind having now a look at the qemu situation, 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/1866866 Title: [FFe] Please accept patches for secure guest feature Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: Fix Committed Status in qemu package in Ubuntu: New Status in s390-tools package in Ubuntu: Fix Released Bug description: The secure guest feature (aka protvirt) affects multiple components (kernel, qemu and s390-tools - see below). While dedicated tickets for the different components exist since quite a while, the code arrived late and/or discussion to get it upstream accepted took longer than expected. (Even if we as of today didn't reached the kernel freeze, I'm already adding kernel to this FFe.) Since this is a very important feature the current IBM Z and LinuxONE family, it's requested to be included into focal, the next LTS release, to become exploitable by long running systems. The code is largely architecture specific. No brand new packages or new upstream version are requested, only the cherry-pick of commits (or PR) - so far everything is 'cherry-pick'-able. kernel: The patch set for the kernel is huge (30+ commits), but has only one common code patch (two files). The arch specific patches landed in between in linux-next, the arch specific one is expected to land there very soon (hours/days from now). The common-code patch ran through several hands and landed in between in Andrew Morton's mmots tree. A pre-screening of the code was done by the kernel team and it looked acceptable. (dedicated kernel ticket: https://bugs.launchpad.net/bugs/1835531) qemu: The entire code seems to be arch specific. Again a pre-screening of the maintainer lead to the fact that it should be acceptable, too. (dedicated qemu ticket: https://bugs.launchpad.net/bugs/1835546) s390-tools: The entire tool only exists for the s390x architecture. Hence obviously everything is arch specific on that. (dedicated s390-tools ticket: https://bugs.launchpad.net/bugs/1834534) Currently work is going on to test this function end to end based on Ubuntu components (means based on our s390-tools, qemu and kernel [focal master-next] trees). On top I applied the patches to the packages as well and did manual test buids. With that a potential regression can be considered as low - and even in case of a regression, it will affect s390x only. The patches are being staged for this feature in: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3970 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1866866/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1868898] [NEW] Ubuntu 20.04 clean install : autostandby feature
You have been subscribed to a public bug: Have ubuntu 20.04 development branch on my laptop and my desktop. Noticed yesterday, my laptop was idle for a while and the power light was on and keypress didnt wake it up. Pressing power button didnt wake it up either. On my tower pc I use tandby on power press and it works great. Problem seems to be in auto standby feature. I remember this bug in 18.04 development branch as well. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Ubuntu 20.04 clean install : autostandby feature https://bugs.launchpad.net/bugs/1868898 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 1868898] Re: Ubuntu 20.04 clean install : autostandby feature
** 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/1868898 Title: Ubuntu 20.04 clean install : autostandby feature Status in linux package in Ubuntu: Incomplete Bug description: Have ubuntu 20.04 development branch on my laptop and my desktop. Noticed yesterday, my laptop was idle for a while and the power light was on and keypress didnt wake it up. Pressing power button didnt wake it up either. On my tower pc I use tandby on power press and it works great. Problem seems to be in auto standby feature. I remember this bug in 18.04 development branch as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868898/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1868898] 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 1868898 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/1868898 Title: Ubuntu 20.04 clean install : autostandby feature Status in linux package in Ubuntu: Incomplete Bug description: Have ubuntu 20.04 development branch on my laptop and my desktop. Noticed yesterday, my laptop was idle for a while and the power light was on and keypress didnt wake it up. Pressing power button didnt wake it up either. On my tower pc I use tandby on power press and it works great. Problem seems to be in auto standby feature. I remember this bug in 18.04 development branch as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868898/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855399] Re: [TGL] graphics kernel support
Thanks! There are a few that are missing from my patchset, I'll add them in the next batch. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1855399 Title: [TGL] graphics kernel support Status in intel: New Status in linux package in Ubuntu: Incomplete Bug description: Description: This feature tracks the updates TGL graphics updates. We will submit the commit id lists since 5.4. 20.04 will use v5.4 as a base, (2109/11/25) first commit lists will be provided in 2020/01, if you need more before that, please let us know. Target Release: 20.10 Target Kernel: v5.8 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1855399/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1868210] Re: [SRU] Load ucm on Lenovo notebooks based on bios version
Please ignore #1 and #2. Some users found some problem on them (find the ucm by bios version). I will upload new debdiffs. -- 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/1868210 Title: [SRU] Load ucm on Lenovo notebooks based on bios version Status in HWE Next: New Status in alsa-lib package in Ubuntu: Invalid Status in alsa-lib source package in Bionic: Confirmed Status in alsa-lib source package in Eoan: Confirmed Status in alsa-lib source package in Focal: Invalid Bug description: This SRU is not backported from upstream of alsa-lib and this SRU is not going to be submitted to upstream. That is because the latest alsa-lib already supports ucm2, and with ucm2 all machines could share one ucm, so latest alsa-lib does not have this problem. This problem is only specific to the alsa-lib in Bionic and Eoan. [Impact] On some Lenovo notebooks, UCM files are not loaded and mic can't be used. [Fix] UCM was loaded based on cardlongname, but that can't cover all configs of the same model. Lenovo suggested to load ucm by the first 3 letters of /sys/devices/virtual/dmi/id/bios_version, so that all configs could use just one ucm. [Test Case] After applying this patch, install the testing alsa-lib on Lenovo X1C7 and Dell vostro 5390, which are all machines with the DMIC connected to PCH. After system bootup, check the /usr/share/alsa/ucm/ for the presence of LENOVO-BIOSID-xxx directories. Lenovo X1C7 should load the N2H/*.conf and verify the audio functionalities. The Dell machine should still load the ucm by cardname, and it should work as good as before. [Regression Potential] low, just add some new UCMs and let Lenovo machine find the UCM by bios_version if it fails by cardlongname. I've already tested the change on Lenovo and Dell machines. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1868210/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1865130] Re: [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!!
Hi @dersuuzalachillout, You can just open a terminal window and run inside (line by line, in sequence): wget http://archive.ubuntu.com/ubuntu/pool/main/l/linux-firmware/linux-firmware_1.173.17_all.deb sudo dpkg -i linux-firmware_1.173.17_all.deb rm linux-firmware_1.173.17_all.deb Type your password (when 'sudo' ask you) and when everything gets done reboot your computer. Is there any change? 😉😎 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1865130 Title: [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Bionic: Fix Committed Status in linux-firmware source package in Eoan: Fix Committed Bug description: === SRU Justification === [Impact] Firmware update of radeon/oland_rlc.bin breaks some radeon cards. [Fix] Revert the new firmware. [Regression Potential] Low. The old firmware has been used for a long time. === Original Bug Report === when trying > DRI_PRIME=1 glxgears , the result in dmesg is as following [ +0.91] radeon :01:00.0: WB enabled [ +0.02] radeon :01:00.0: fence driver on ring 0 use gpu addr 0x8c00 and cpu addr 0x8ac2d26f [ +0.01] radeon :01:00.0: fence driver on ring 1 use gpu addr 0x8c04 and cpu addr 0xa848de20 [ +0.01] radeon :01:00.0: fence driver on ring 2 use gpu addr 0x8c08 and cpu addr 0x1e4494a9 [ +0.01] radeon :01:00.0: fence driver on ring 3 use gpu addr 0x8c0c and cpu addr 0x98a9748e [ +0.01] radeon :01:00.0: fence driver on ring 4 use gpu addr 0x8c10 and cpu addr 0xb6ff734d [ +0.000212] radeon :01:00.0: fence driver on ring 5 use gpu addr 0x00075a18 and cpu addr 0x6b4da526 [ +0.100566] radeon :01:00.0: failed VCE resume (-110). [ +0.179115] [drm] ring test on 0 succeeded in 1 usecs [ +0.04] [drm] ring test on 1 succeeded in 1 usecs [ +0.04] [drm] ring test on 2 succeeded in 1 usecs [ +0.06] [drm] ring test on 3 succeeded in 3 usecs [ +0.04] [drm] ring test on 4 succeeded in 3 usecs [ +1.171892] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015643] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015509] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015572] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015514] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015405] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015442] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015416] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015388] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015379] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +0.019924] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, giving up!!! [ +0.40] radeon :01:00.0: failed initializing UVD (-1). [ +0.60] [drm] ib test on ring 0 succeeded in 0 usecs [ +0.51] [drm] ib test on ring 1 succeeded in 0 usecs [ +0.32] [drm] ib test on ring 2 succeeded in 0 usecs [ +0.52] [drm] ib test on ring 3 succeeded in 0 usecs [ +0.29] [drm] ib test on ring 4 succeeded in 0 usecs Also it affects the boot time. the used OpenGL renderer is: "OpenGL renderer string: AMD OLAND (DRM 2.50.0, 5.3.0-40-generic, LLVM 9.0.0)" ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: communitheme:ubuntu:GNOME Date: Fri Feb 28 11:50:50 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.3.0-28-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.3.0-40-generic, x86_64: installed virtualbox, 5.2.34, 5.3.0-28-generic, x86_64: installed virtualbox, 5.2.34, 5.3.0-40-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo 4th Gen C
[Kernel-packages] [Bug 1858844] Re: [Dell XPS 15 9575] Screen brightness stopped working with linux-image-5.4.0-9-generic
The issue with the brightness slider not moving in the gnome panel menu, in response to brightness keys, was fixed after the latest round of updates that installed gnome-shell 3.36. So all is good now on the Dell XPS 9575, thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1858844 Title: [Dell XPS 15 9575] Screen brightness stopped working with linux- image-5.4.0-9-generic Status in linux package in Ubuntu: Confirmed Bug description: I upgraded to Focal Fossa 3 days ago and nothing broke. At the time, it was still using linux 5.3 (linux-image-5.3.0-24-generic). Today, it updated to linux 5.4 (linux-image-5.4.0-9-generic) and after rebooting, the screen brightness does not work anymore - neither from keyboard keys nor from the slider in the gnome-shell panel. It works again when rebooting into the previous linux- image-5.3.0-24-generic kernel. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-9-generic 5.4.0-9.12 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mario 1892 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Jan 8 20:23:31 2020 InstallationDate: Installed on 2018-09-13 (481 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912) MachineType: Dell Inc. XPS 15 9575 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-9-generic root=UUID=26ff4c95-5f68-4121-b7d0-989fa705fcc8 ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.4.0-9-generic N/A linux-backports-modules-5.4.0-9-generic N/A linux-firmware 1.184 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-01-04 (3 days ago) dmi.bios.date: 07/07/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 0C32VW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd07/07/2019:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858844/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1865570] Re: suspend only works once on ThinkPad X1 Carbon gen 7
It'll be in Eoan kernel when it's "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/1865570 Title: suspend only works once on ThinkPad X1 Carbon gen 7 Status in linux package in Ubuntu: Triaged Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: Won't Fix Status in linux-oem-osp1 source package in Bionic: New Status in linux source package in Eoan: New Status in linux-oem-osp1 source package in Eoan: Won't Fix Status in linux source package in Focal: Triaged Status in linux-oem-osp1 source package in Focal: Won't Fix Bug description: === SRU Justification === [Impact] Lenovo X1 Carbon 7th can only susped (s2idle) once, subsquent suspends are blocked by failed e1000e resume routine. [Fix] It's not root caused yet by Intel, so disable the s0ix flow on X1 Carbon 7th as a temporary workaround. [Test] After applying the DMI quirk patch, e1000e keeps working, so it doesn't block s2idle anymore. User also confimred the workaround works. [Regression Potential] Low. It limits to a specific model, and I can confirm s0ix can still be reached withouth this feature. === Original Bug Report === 5.4.0-16 and 5.4.0-17 go to suspend when the lid is closed, but *only once* after boot. On subsequent attempts, when the lid it closed, backlight and wifi are turned off, but system does not suspend. First successful suspend: [ 147.413295] PM: suspend entry (s2idle) [ 147.416601] Filesystems sync: 0.003 seconds [ 147.419371] Freezing user space processes ... (elapsed 0.001 seconds) done. [ 147.421210] OOM killer disabled. [ 147.421210] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 147.422375] printk: Suspending console(s) (use no_console_suspend to debug) [ 147.422630] wlp0s20f3: deauthenticating from 18:d6:c7:61:95:c2 by local choice (Reason: 3=DEAUTH_LEAVING) [ 147.527810] e1000e: EEE TX LPI TIMER: 0011 [ 150.246317] ACPI: EC: interrupt blocked [ 881.134544] ACPI: EC: interrupt unblocked [ 883.933255] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM [ 884.047802] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM [ 884.112730] iwlwifi :00:14.3: FW already configured (0) - re-configuring [ 886.815475] e1000e :00:1f.6 enp0s31f6: PHY Wakeup cause - Unicast Packet [ 887.485832] e1000e :00:1f.6 enp0s31f6: Hardware Error [ 888.016931] OOM killer enabled. [ 888.016932] Restarting tasks ... done. [ 888.060613] PM: suspend exit Second unsuccessful suspend: [ 907.584802] PM: suspend entry (s2idle) [ 907.589779] Filesystems sync: 0.004 seconds [ 907.591416] Freezing user space processes ... (elapsed 0.002 seconds) done. [ 907.593518] OOM killer disabled. [ 907.593518] Freezing remaining freezable tasks ... (elapsed 0.328 seconds) done. [ 907.921560] printk: Suspending console(s) (use no_console_suspend to debug) [ 907.922127] wlp0s20f3: deauthenticating from 18:d6:c7:61:95:c2 by local choice (Reason: 3=DEAUTH_LEAVING) [ 908.024438] e1000e: EEE TX LPI TIMER: 0011 [ 909.916364] PM: pci_pm_suspend(): e1000e_pm_suspend+0x0/0x80 [e1000e] returns -2 [ 909.916367] PM: dpm_run_callback(): pci_pm_suspend+0x0/0x150 returns -2 [ 909.916369] PM: Device :00:1f.6 failed to suspend async: error -2 [ 911.183052] PM: Some devices failed to suspend, or early wake event detected [ 911.197091] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM [ 911.314903] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM [ 911.382438] iwlwifi :00:14.3: FW already configured (0) - re-configuring [ 911.413624] OOM killer enabled. [ 911.413625] Restarting tasks ... done. [ 911.462021] PM: suspend exit It looks like Ethernet driver prevents suspend. Ethernet is not connected (I do not have the adaptor). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1865570/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867109] Re: [UBUNTU 20.04] virtio-blk disks can go dissfunctional when swiotlb fills up
--- Comment From pa...@de.ibm.com 2020-03-25 10:35 EDT--- Verificattion: looks good! ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1867109 Title: [UBUNTU 20.04] virtio-blk disks can go dissfunctional when swiotlb fills up Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: Fix Committed Bug description: virtio-blk disks can go dissfunctional when swiotlb fills up virtio-blk hw queue gets possibly permanently stopped when swiotlb full For example, with a PV guest choose a small swiotlb (30MB) and create IO load on several virtio-blk disks simultaneously. It actually should not matter what causes the swiotlb pressure (can be virtio-net as well). Fixes posted upstream: https://lkml.org/lkml/2020/2/13/306 We will need backports to support Protected Virtualization. IBM verified that the patches apply cleanly on focal/master-next, upstream commit ids for reference: commit bab7e6f05699a481787f7659c4f766dd87187dae Author: Halil Pasic Date: Thu Feb 13 13:37:27 2020 +0100 virtio-blk: fix hw_queue stopped on arbitrary error commit 24506976aec92052e9fe328146a2e574a1190986 Author: Halil Pasic Date: Thu Feb 13 13:37:28 2020 +0100 virtio-blk: improve virtqueue error to BLK_STS Also applies cleanly on 19.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1867109/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861521] Re: [FOCAL][REGRESSION] Intel Gen 9 brightness cannot be controlled
** Package changed: linux-5.4 (Ubuntu Focal) => linux (Ubuntu Focal) ** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1861521 Title: [FOCAL][REGRESSION] Intel Gen 9 brightness cannot be controlled Status in linux package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Fix Released Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Bug description: [Impact] After Ubuntu-5.4.0-9.12 which introduce DPCD backlight patches, the backlight control on some platforms fail to work. It seems using OUI string to map the panels which support DPCD backlight doesn't work well, it mis-mapped those panel that doesn't support DPCD backlight, and breaks the backlight control. [Fix] The author of the origin DPCD backlight patches recently provides a DP quirks based on EDID identification. [Fix] Verified on the machine with DPCD backlight and also on the machine which has regression with the OUI quirks, both of them work now. [Regression Potential] Low, it introduce a new quirks to list the panels which support DPCD backlight. === After upgrading from Eoan (5.3.0-29.31) to Focal (5.4.0-12.15), I no longer have the ability to control the backlight brightness on my HP EliteBook 840 G5. When pressing the brightness hotkeys, the on-screen indicator pops up and shows that the brightness setting is being changed but the actual screen brightness is stuck on the lowest setting. This laptop has a built-in privacy screen. If I activate the privacy screen (fn-f2), then the actual screen brightness goes to the maximum setting and then I am able to dim and brighten the backlight as long as the privacy screen functionality is turned on. This is a regression from Eoan's 5.3.0-29.31 kernel where I was able to control the brightness with and without the privacy screen functionality being turned on. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-12-generic 5.4.0-12.15 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jan 31 11:42:16 2020 InstallationDate: Installed on 2019-06-24 (221 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-5.4 UpgradeStatus: Upgraded to focal on 2020-01-28 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861521/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1866882] Re: segfault in libllvm-10 when building kernel bpf selftests on s390
Still seeing this with the current focal-proposed kernel: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-focal/focal/s390x/l/linux/20200325_012616_7d5a5@/log.gz ** Changed in: llvm-toolchain-10 (Ubuntu) Status: Incomplete => Confirmed ** Changed in: llvm-toolchain-10 (Ubuntu) Assignee: (unassigned) => Matthias Klose (doko) ** Changed in: llvm-toolchain-10 (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1866882 Title: segfault in libllvm-10 when building kernel bpf selftests on s390 Status in linux package in Ubuntu: Incomplete Status in llvm-toolchain-10 package in Ubuntu: Confirmed Bug description: Seeing this in autopkgtest for the 5.4.0-18 kernel. Only happens on s390, other architectures are fine. Stack dump: 0. Program arguments: llc -march=bpf -mcpu=probe -filetype=obj -o /tmp/autopkgtest.92AlD3/build.vya/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/bpf/btf__core_reloc_nesting___err_array_container.o #0 0x03ff830ab14a (/lib/s390x-linux-gnu/libLLVM-10.so.1+0x9ab14a) Segmentation fault (core dumped) Full log: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-focal/focal/s390x/l/linux/20200310_180956_146bd@/log.gz This did not happen for the 5.4.0-17 upload with llvm-9, with no changes to the bpf program being compiled when the segfault happens between the -17 and -18 uploads. To reproduce, clone the focal kernel tree and build the bpf selftests. $ git clone --single-branch --depth=1 -b master-next git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/focal $ make -C focal/tools/testing/selftests TARGETS=bpf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866882/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814481] Re: Keychron K1 keyboard not working
Keychron K1v3 (firmware V3.7) on Ubuntu 19.10 (upgrad path from 18.04), can confirm that https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814481/comments/19 fixes the issue when connected via Bluetooth. Some additional information: For me when connected via Bluetooth only the function keys would work. The following command as described by Eferox, allowed me to use the keyboard normally: echo 0 | sudo tee /sys/module/hid_apple/parameters/fnmode Note that this means that the `fn` key is now disabled by default, so pressing one of the `F` keys registers as `F1`, `F2`, etc. In order to get the media key functions you have to press `fn` + `F`. Also note that if you also use an Apple keyboard this probably modifies its default behaviour. Explanation of parameters for `/sys/module/hid_apple/parameters/fnmode` https://superuser.com/questions/79822/how-to-swap-the-fn-use-of-function-keys-on-an-apple-keyboard-in-linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1814481 Title: Keychron K1 keyboard not working Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: New Bug description: I recently got a nice mechanical bluetooth keyboard to use on my thinkpad. It works fine with Android, Windows 10 and Xubuntu 19.04 live, but on my installed xubuntu 18.04, 18.04 live and 18.10 live it only works after calling `sudo evtest /dev/input/eventN`. Xorg.0.log shows it is detected fine, and I can't see anything there after temporarily getting it to work using the evtest trick. 18.515] (II) config/udev: Adding input device Keychron K1 (/dev/input/event23) [18.515] (**) Keychron K1: Applying InputClass "libinput keyboard catchall" [18.515] (II) Using input driver 'libinput' for 'Keychron K1' [18.515] (**) Keychron K1: always reports core events [18.515] (**) Option "Device" "/dev/input/event23" [18.515] (**) Option "_source" "server/udev" [18.516] (II) event23 - Keychron K1: is tagged by udev as: Keyboard [18.516] (II) event23 - Keychron K1: device is a keyboard [18.516] (II) event23 - Keychron K1: device removed [18.524] (II) libinput: Keychron K1: needs a virtual subdevice [18.524] (**) Option "config_info" "udev:/sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:0255.0007/input/input24/event23" [18.524] (II) XINPUT: Adding extended input device "Keychron K1" (type: MOUSE, id 20) [18.524] (**) Option "AccelerationScheme" "none" [18.524] (**) Keychron K1: (accel) selected scheme none/0 [18.524] (**) Keychron K1: (accel) acceleration factor: 2.000 [18.524] (**) Keychron K1: (accel) acceleration threshold: 4 [18.524] (II) event23 - Keychron K1: is tagged by udev as: Keyboard [18.524] (II) event23 - Keychron K1: device is a keyboard [18.524] (**) Keychron K1: Applying InputClass "libinput keyboard catchall" [18.524] (II) Using input driver 'libinput' for 'Keychron K1' [18.524] (**) Keychron K1: always reports core events [18.524] (**) Option "Device" "/dev/input/event23" [18.524] (**) Option "_source" "_driver/libinput" [18.524] (II) libinput: Keychron K1: is a virtual subdevice [18.524] (**) Option "config_info" "udev:/sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:0255.0007/input/input24/event23" [18.524] (II) XINPUT: Adding extended input device "Keychron K1" (type: KEYBOARD, id 21) [18.524] (**) Option "xkb_model" "pc105" [18.524] (**) Option "xkb_layout" "us" [18.524] (**) Option "xkb_variant" "altgr-intl" [18.524] (WW) Option "xkb_options" requires a string value I've also tried using the latest 4.20.6 from mainline-ppa and the latest bluetooth/bluz ppa without success. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-45.48-lowlatency 4.15.18 Uname: Linux 4.15.0-45-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Sun Feb 3 23:51:29 2019 DistUpgraded: 2019-02-03 21:49:33,752 DEBUG /openCache(), new cache size 92675 DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.18, 4.15.0-45-lowlatency, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:224b] InstallationDate: Installed on 2017-07-24 (559 days ago) InstallationMedia: Xubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) MachineType: LENOVO 20HFCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmli
[Kernel-packages] [Bug 1868388] Re: watchdog: BUG: soft lockup - CPU#11 stuck for 188s! [swapper/11:0]
Could you please send /var/log/kern.log* ? Thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1868388 Title: watchdog: BUG: soft lockup - CPU#11 stuck for 188s! [swapper/11:0] Status in linux package in Ubuntu: Confirmed Bug description: Got this after resuming from suspend for a few hours. Also noticed that it was not possible to re-establish wifi connectivity. Had to reboot the machine to get back to a proper working state. ProblemType: KernelOops DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-18-generic 5.4.0-18.22 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1443 F pulseaudio marcus 1889 F pulseaudio Date: Sat Mar 21 11:43:52 2020 Failure: oops InstallationDate: Installed on 2020-03-18 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 27c6:5395 Shenzhen Goodix Technology Co.,Ltd. Fingerprint Reader Bus 001 Device 002: ID 0cf3:e300 Qualcomm Atheros Communications Bus 001 Device 004: ID 0c45:671d Microdia Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9570 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=8c0be221-e900-480f-b359-5cbd3f16ebd4 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A SourcePackage: linux Title: watchdog: BUG: soft lockup - CPU#11 stuck for 188s! [swapper/11:0] UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0D0T05 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd12/25/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868388/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814481] Re: Keychron K1 keyboard not working
Additionally if you want to change the default `F` key behaviour again, press and hold `fn + X + L` in that order for >3 seconds until the keyboard blinks red twice. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1814481 Title: Keychron K1 keyboard not working Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: New Bug description: I recently got a nice mechanical bluetooth keyboard to use on my thinkpad. It works fine with Android, Windows 10 and Xubuntu 19.04 live, but on my installed xubuntu 18.04, 18.04 live and 18.10 live it only works after calling `sudo evtest /dev/input/eventN`. Xorg.0.log shows it is detected fine, and I can't see anything there after temporarily getting it to work using the evtest trick. 18.515] (II) config/udev: Adding input device Keychron K1 (/dev/input/event23) [18.515] (**) Keychron K1: Applying InputClass "libinput keyboard catchall" [18.515] (II) Using input driver 'libinput' for 'Keychron K1' [18.515] (**) Keychron K1: always reports core events [18.515] (**) Option "Device" "/dev/input/event23" [18.515] (**) Option "_source" "server/udev" [18.516] (II) event23 - Keychron K1: is tagged by udev as: Keyboard [18.516] (II) event23 - Keychron K1: device is a keyboard [18.516] (II) event23 - Keychron K1: device removed [18.524] (II) libinput: Keychron K1: needs a virtual subdevice [18.524] (**) Option "config_info" "udev:/sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:0255.0007/input/input24/event23" [18.524] (II) XINPUT: Adding extended input device "Keychron K1" (type: MOUSE, id 20) [18.524] (**) Option "AccelerationScheme" "none" [18.524] (**) Keychron K1: (accel) selected scheme none/0 [18.524] (**) Keychron K1: (accel) acceleration factor: 2.000 [18.524] (**) Keychron K1: (accel) acceleration threshold: 4 [18.524] (II) event23 - Keychron K1: is tagged by udev as: Keyboard [18.524] (II) event23 - Keychron K1: device is a keyboard [18.524] (**) Keychron K1: Applying InputClass "libinput keyboard catchall" [18.524] (II) Using input driver 'libinput' for 'Keychron K1' [18.524] (**) Keychron K1: always reports core events [18.524] (**) Option "Device" "/dev/input/event23" [18.524] (**) Option "_source" "_driver/libinput" [18.524] (II) libinput: Keychron K1: is a virtual subdevice [18.524] (**) Option "config_info" "udev:/sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:0255.0007/input/input24/event23" [18.524] (II) XINPUT: Adding extended input device "Keychron K1" (type: KEYBOARD, id 21) [18.524] (**) Option "xkb_model" "pc105" [18.524] (**) Option "xkb_layout" "us" [18.524] (**) Option "xkb_variant" "altgr-intl" [18.524] (WW) Option "xkb_options" requires a string value I've also tried using the latest 4.20.6 from mainline-ppa and the latest bluetooth/bluz ppa without success. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-45.48-lowlatency 4.15.18 Uname: Linux 4.15.0-45-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Sun Feb 3 23:51:29 2019 DistUpgraded: 2019-02-03 21:49:33,752 DEBUG /openCache(), new cache size 92675 DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.18, 4.15.0-45-lowlatency, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:224b] InstallationDate: Installed on 2017-07-24 (559 days ago) InstallationMedia: Xubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) MachineType: LENOVO 20HFCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-lowlatency root=UUID=8f8366ae-4d29-44cf-9b85-f83f1771eab1 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2019-02-03 (0 days ago) dmi.bios.date: 09/14/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N1WET51W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1WET51W(1.30):bd09/14/2018:svnLENOVO:pn20HFCTO1WW:pvrThinkPadT470s:rvnLENOVO:rn20HFCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T470s dmi.product.name: 20HFCTO1WW dmi
Re: [Kernel-packages] [Bug 1868898] Re: Ubuntu 20.04 clean install : autostandby feature
Hi, I am currently leaving my laptop on on idle to replicate the issue then I will run apport collect to the bug. not sure how to change the bug status. -Steve On 2020-03-25 8:25 a.m., Juhani Numminen wrote: > ** 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/1868898 Title: Ubuntu 20.04 clean install : autostandby feature Status in linux package in Ubuntu: Incomplete Bug description: Have ubuntu 20.04 development branch on my laptop and my desktop. Noticed yesterday, my laptop was idle for a while and the power light was on and keypress didnt wake it up. Pressing power button didnt wake it up either. On my tower pc I use tandby on power press and it works great. Problem seems to be in auto standby feature. I remember this bug in 18.04 development branch as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868898/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1868388] Re: watchdog: BUG: soft lockup - CPU#11 stuck for 188s! [swapper/11:0]
Unfortunately no, the install has been removed for now as it was just a quick test spin of 20.04 on real hardware. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1868388 Title: watchdog: BUG: soft lockup - CPU#11 stuck for 188s! [swapper/11:0] Status in linux package in Ubuntu: Confirmed Bug description: Got this after resuming from suspend for a few hours. Also noticed that it was not possible to re-establish wifi connectivity. Had to reboot the machine to get back to a proper working state. ProblemType: KernelOops DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-18-generic 5.4.0-18.22 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1443 F pulseaudio marcus 1889 F pulseaudio Date: Sat Mar 21 11:43:52 2020 Failure: oops InstallationDate: Installed on 2020-03-18 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 27c6:5395 Shenzhen Goodix Technology Co.,Ltd. Fingerprint Reader Bus 001 Device 002: ID 0cf3:e300 Qualcomm Atheros Communications Bus 001 Device 004: ID 0c45:671d Microdia Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9570 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=8c0be221-e900-480f-b359-5cbd3f16ebd4 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A SourcePackage: linux Title: watchdog: BUG: soft lockup - CPU#11 stuck for 188s! [swapper/11:0] UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0D0T05 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd12/25/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868388/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1869033] [NEW] Lenovo IdeaPad S145-IWL - touchpad not recognized
Public bug reported: I'm trying to use Ubuntu 20.04 but it's not seeing touchpad - it's not even available in device list. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-18-generic 5.4.0-18.22 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 4248 F pulseaudio CasperVersion: 1.441 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 25 15:44:31 2020 LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200325) MachineType: LENOVO 81W8 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity RelatedPackageVersions: linux-restricted-modules-5.4.0-18-generic N/A linux-backports-modules-5.4.0-18-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/09/2019 dmi.bios.vendor: LENOVO dmi.bios.version: DKCN21WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad S145-15IIL dmi.modalias: dmi:bvnLENOVO:bvrDKCN21WW:bd10/09/2019:svnLENOVO:pn81W8:pvrLenovoIdeaPadS145-15IIL:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoIdeaPadS145-15IIL: dmi.product.family: IdeaPad S145-15IIL dmi.product.name: 81W8 dmi.product.sku: LENOVO_MT_81W8_BU_idea_FM_IdeaPad S145-15IIL dmi.product.version: Lenovo IdeaPad S145-15IIL dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1869033 Title: Lenovo IdeaPad S145-IWL - touchpad not recognized Status in linux package in Ubuntu: New Bug description: I'm trying to use Ubuntu 20.04 but it's not seeing touchpad - it's not even available in device list. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-18-generic 5.4.0-18.22 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 4248 F pulseaudio CasperVersion: 1.441 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 25 15:44:31 2020 LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200325) MachineType: LENOVO 81W8 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity RelatedPackageVersions: linux-restricted-modules-5.4.0-18-generic N/A linux-backports-modules-5.4.0-18-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/09/2019 dmi.bios.vendor: LENOVO dmi.bios.version: DKCN21WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad S145-15IIL dmi.modalias: dmi:bvnLENOVO:bvrDKCN21WW:bd10/09/2019:svnLENOVO:pn81W8:pvrLenovoIdeaPadS145-15IIL:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoIdeaPadS145-15IIL: dmi.product.family: IdeaPad S145-15IIL dmi.product.name: 81W8 dmi.product.sku: LENOVO_MT_81W8_BU_idea_FM_IdeaPad S145-15IIL dmi.product.version: Lenovo IdeaPad S145-15IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1869033/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1868898] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1868898/+attachment/5341566/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1868898 Title: Ubuntu 20.04 clean install : autostandby feature Status in linux package in Ubuntu: Incomplete Bug description: Have ubuntu 20.04 development branch on my laptop and my desktop. Noticed yesterday, my laptop was idle for a while and the power light was on and keypress didnt wake it up. Pressing power button didnt wake it up either. On my tower pc I use tandby on power press and it works great. Problem seems to be in auto standby feature. I remember this bug in 18.04 development branch as well. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: steve 1606 F pulseaudio /dev/snd/controlC0: steve 1606 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-03-21 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) MachineType: Dell Inc. Inspiron 5765 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=5659d383-5314-42cf-907e-2116ea6b8145 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 RelatedPackageVersions: linux-restricted-modules-5.4.0-18-generic N/A linux-backports-modules-5.4.0-18-generic N/A linux-firmware1.187 StagingDrivers: exfat Tags: focal staging Uname: Linux 5.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/17/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0DM01M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.1.1 dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd07/17/2017:svnDellInc.:pnInspiron5765:pvr1.1.1:rvnDellInc.:rn0DM01M:rvrA00:cvnDellInc.:ct10:cvr1.1.1: dmi.product.family: Inspiron dmi.product.name: Inspiron 5765 dmi.product.sku: 076A dmi.product.version: 1.1.1 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868898/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1868898] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1868898/+attachment/5341569/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1868898 Title: Ubuntu 20.04 clean install : autostandby feature Status in linux package in Ubuntu: Incomplete Bug description: Have ubuntu 20.04 development branch on my laptop and my desktop. Noticed yesterday, my laptop was idle for a while and the power light was on and keypress didnt wake it up. Pressing power button didnt wake it up either. On my tower pc I use tandby on power press and it works great. Problem seems to be in auto standby feature. I remember this bug in 18.04 development branch as well. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: steve 1606 F pulseaudio /dev/snd/controlC0: steve 1606 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-03-21 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) MachineType: Dell Inc. Inspiron 5765 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=5659d383-5314-42cf-907e-2116ea6b8145 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 RelatedPackageVersions: linux-restricted-modules-5.4.0-18-generic N/A linux-backports-modules-5.4.0-18-generic N/A linux-firmware1.187 StagingDrivers: exfat Tags: focal staging Uname: Linux 5.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/17/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0DM01M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.1.1 dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd07/17/2017:svnDellInc.:pnInspiron5765:pvr1.1.1:rvnDellInc.:rn0DM01M:rvrA00:cvnDellInc.:ct10:cvr1.1.1: dmi.product.family: Inspiron dmi.product.name: Inspiron 5765 dmi.product.sku: 076A dmi.product.version: 1.1.1 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868898/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1868898] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1868898/+attachment/5341561/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1868898 Title: Ubuntu 20.04 clean install : autostandby feature Status in linux package in Ubuntu: Incomplete Bug description: Have ubuntu 20.04 development branch on my laptop and my desktop. Noticed yesterday, my laptop was idle for a while and the power light was on and keypress didnt wake it up. Pressing power button didnt wake it up either. On my tower pc I use tandby on power press and it works great. Problem seems to be in auto standby feature. I remember this bug in 18.04 development branch as well. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: steve 1606 F pulseaudio /dev/snd/controlC0: steve 1606 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-03-21 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) MachineType: Dell Inc. Inspiron 5765 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=5659d383-5314-42cf-907e-2116ea6b8145 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 RelatedPackageVersions: linux-restricted-modules-5.4.0-18-generic N/A linux-backports-modules-5.4.0-18-generic N/A linux-firmware1.187 StagingDrivers: exfat Tags: focal staging Uname: Linux 5.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/17/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0DM01M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.1.1 dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd07/17/2017:svnDellInc.:pnInspiron5765:pvr1.1.1:rvnDellInc.:rn0DM01M:rvrA00:cvnDellInc.:ct10:cvr1.1.1: dmi.product.family: Inspiron dmi.product.name: Inspiron 5765 dmi.product.sku: 076A dmi.product.version: 1.1.1 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868898/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1868898] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1868898/+attachment/5341565/+files/Lsusb-v.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/1868898 Title: Ubuntu 20.04 clean install : autostandby feature Status in linux package in Ubuntu: Incomplete Bug description: Have ubuntu 20.04 development branch on my laptop and my desktop. Noticed yesterday, my laptop was idle for a while and the power light was on and keypress didnt wake it up. Pressing power button didnt wake it up either. On my tower pc I use tandby on power press and it works great. Problem seems to be in auto standby feature. I remember this bug in 18.04 development branch as well. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: steve 1606 F pulseaudio /dev/snd/controlC0: steve 1606 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-03-21 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) MachineType: Dell Inc. Inspiron 5765 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=5659d383-5314-42cf-907e-2116ea6b8145 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 RelatedPackageVersions: linux-restricted-modules-5.4.0-18-generic N/A linux-backports-modules-5.4.0-18-generic N/A linux-firmware1.187 StagingDrivers: exfat Tags: focal staging Uname: Linux 5.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/17/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0DM01M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.1.1 dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd07/17/2017:svnDellInc.:pnInspiron5765:pvr1.1.1:rvnDellInc.:rn0DM01M:rvrA00:cvnDellInc.:ct10:cvr1.1.1: dmi.product.family: Inspiron dmi.product.name: Inspiron 5765 dmi.product.sku: 076A dmi.product.version: 1.1.1 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868898/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1868898] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1868898/+attachment/5341567/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1868898 Title: Ubuntu 20.04 clean install : autostandby feature Status in linux package in Ubuntu: Incomplete Bug description: Have ubuntu 20.04 development branch on my laptop and my desktop. Noticed yesterday, my laptop was idle for a while and the power light was on and keypress didnt wake it up. Pressing power button didnt wake it up either. On my tower pc I use tandby on power press and it works great. Problem seems to be in auto standby feature. I remember this bug in 18.04 development branch as well. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: steve 1606 F pulseaudio /dev/snd/controlC0: steve 1606 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-03-21 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) MachineType: Dell Inc. Inspiron 5765 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=5659d383-5314-42cf-907e-2116ea6b8145 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 RelatedPackageVersions: linux-restricted-modules-5.4.0-18-generic N/A linux-backports-modules-5.4.0-18-generic N/A linux-firmware1.187 StagingDrivers: exfat Tags: focal staging Uname: Linux 5.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/17/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0DM01M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.1.1 dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd07/17/2017:svnDellInc.:pnInspiron5765:pvr1.1.1:rvnDellInc.:rn0DM01M:rvrA00:cvnDellInc.:ct10:cvr1.1.1: dmi.product.family: Inspiron dmi.product.name: Inspiron 5765 dmi.product.sku: 076A dmi.product.version: 1.1.1 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868898/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1868898] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1868898/+attachment/5341564/+files/Lsusb-t.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/1868898 Title: Ubuntu 20.04 clean install : autostandby feature Status in linux package in Ubuntu: Incomplete Bug description: Have ubuntu 20.04 development branch on my laptop and my desktop. Noticed yesterday, my laptop was idle for a while and the power light was on and keypress didnt wake it up. Pressing power button didnt wake it up either. On my tower pc I use tandby on power press and it works great. Problem seems to be in auto standby feature. I remember this bug in 18.04 development branch as well. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: steve 1606 F pulseaudio /dev/snd/controlC0: steve 1606 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-03-21 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) MachineType: Dell Inc. Inspiron 5765 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=5659d383-5314-42cf-907e-2116ea6b8145 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 RelatedPackageVersions: linux-restricted-modules-5.4.0-18-generic N/A linux-backports-modules-5.4.0-18-generic N/A linux-firmware1.187 StagingDrivers: exfat Tags: focal staging Uname: Linux 5.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/17/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0DM01M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.1.1 dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd07/17/2017:svnDellInc.:pnInspiron5765:pvr1.1.1:rvnDellInc.:rn0DM01M:rvrA00:cvnDellInc.:ct10:cvr1.1.1: dmi.product.family: Inspiron dmi.product.name: Inspiron 5765 dmi.product.sku: 076A dmi.product.version: 1.1.1 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868898/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1868898] Re: Ubuntu 20.04 clean install : autostandby feature
apport information ** Tags added: apport-collected staging ** Description changed: Have ubuntu 20.04 development branch on my laptop and my desktop. Noticed yesterday, my laptop was idle for a while and the power light was on and keypress didnt wake it up. Pressing power button didnt wake it up either. On my tower pc I use tandby on power press and it works great. - Problem seems to be in auto standby feature. I remember this bug in - 18.04 development branch as well. + Problem seems to be in auto standby feature. I remember this bug in 18.04 development branch as well. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu21 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: steve 1606 F pulseaudio + /dev/snd/controlC0: steve 1606 F pulseaudio + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2020-03-21 (4 days ago) + InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) + MachineType: Dell Inc. Inspiron 5765 + Package: linux (not installed) + ProcFB: 0 amdgpudrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=5659d383-5314-42cf-907e-2116ea6b8145 ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 + RelatedPackageVersions: + linux-restricted-modules-5.4.0-18-generic N/A + linux-backports-modules-5.4.0-18-generic N/A + linux-firmware1.187 + StagingDrivers: exfat + Tags: focal staging + Uname: Linux 5.4.0-18-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 07/17/2017 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: 1.1.1 + dmi.board.name: 0DM01M + dmi.board.vendor: Dell Inc. + dmi.board.version: A00 + dmi.chassis.type: 10 + dmi.chassis.vendor: Dell Inc. + dmi.chassis.version: 1.1.1 + dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd07/17/2017:svnDellInc.:pnInspiron5765:pvr1.1.1:rvnDellInc.:rn0DM01M:rvrA00:cvnDellInc.:ct10:cvr1.1.1: + dmi.product.family: Inspiron + dmi.product.name: Inspiron 5765 + dmi.product.sku: 076A + dmi.product.version: 1.1.1 + dmi.sys.vendor: Dell Inc. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1868898/+attachment/5341558/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1868898 Title: Ubuntu 20.04 clean install : autostandby feature Status in linux package in Ubuntu: Incomplete Bug description: Have ubuntu 20.04 development branch on my laptop and my desktop. Noticed yesterday, my laptop was idle for a while and the power light was on and keypress didnt wake it up. Pressing power button didnt wake it up either. On my tower pc I use tandby on power press and it works great. Problem seems to be in auto standby feature. I remember this bug in 18.04 development branch as well. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: steve 1606 F pulseaudio /dev/snd/controlC0: steve 1606 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-03-21 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) MachineType: Dell Inc. Inspiron 5765 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=5659d383-5314-42cf-907e-2116ea6b8145 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 RelatedPackageVersions: linux-restricted-modules-5.4.0-18-generic N/A linux-backports-modules-5.4.0-18-generic N/A linux-firmware1.187 StagingDrivers: exfat Tags: focal staging Uname: Linux 5.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/17/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0DM01M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.1.1 dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd07/17/2017:svnDellInc.:pnInspiron5765:pvr1.1.1:rvnDellInc.:rn0DM01M:rvrA00:cvnDellInc.:ct10:cvr1.1.1: dmi.product.family: Inspiron dmi.product.name: Inspiron 5765 dmi.product.sku: 076A dmi.product.version: 1.1.1 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868898/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kern
[Kernel-packages] [Bug 1868898] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1868898/+attachment/5341568/+files/ProcEnviron.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/1868898 Title: Ubuntu 20.04 clean install : autostandby feature Status in linux package in Ubuntu: Incomplete Bug description: Have ubuntu 20.04 development branch on my laptop and my desktop. Noticed yesterday, my laptop was idle for a while and the power light was on and keypress didnt wake it up. Pressing power button didnt wake it up either. On my tower pc I use tandby on power press and it works great. Problem seems to be in auto standby feature. I remember this bug in 18.04 development branch as well. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: steve 1606 F pulseaudio /dev/snd/controlC0: steve 1606 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-03-21 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) MachineType: Dell Inc. Inspiron 5765 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=5659d383-5314-42cf-907e-2116ea6b8145 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 RelatedPackageVersions: linux-restricted-modules-5.4.0-18-generic N/A linux-backports-modules-5.4.0-18-generic N/A linux-firmware1.187 StagingDrivers: exfat Tags: focal staging Uname: Linux 5.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/17/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0DM01M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.1.1 dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd07/17/2017:svnDellInc.:pnInspiron5765:pvr1.1.1:rvnDellInc.:rn0DM01M:rvrA00:cvnDellInc.:ct10:cvr1.1.1: dmi.product.family: Inspiron dmi.product.name: Inspiron 5765 dmi.product.sku: 076A dmi.product.version: 1.1.1 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868898/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1868898] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1868898/+attachment/5341563/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1868898 Title: Ubuntu 20.04 clean install : autostandby feature Status in linux package in Ubuntu: Incomplete Bug description: Have ubuntu 20.04 development branch on my laptop and my desktop. Noticed yesterday, my laptop was idle for a while and the power light was on and keypress didnt wake it up. Pressing power button didnt wake it up either. On my tower pc I use tandby on power press and it works great. Problem seems to be in auto standby feature. I remember this bug in 18.04 development branch as well. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: steve 1606 F pulseaudio /dev/snd/controlC0: steve 1606 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-03-21 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) MachineType: Dell Inc. Inspiron 5765 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=5659d383-5314-42cf-907e-2116ea6b8145 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 RelatedPackageVersions: linux-restricted-modules-5.4.0-18-generic N/A linux-backports-modules-5.4.0-18-generic N/A linux-firmware1.187 StagingDrivers: exfat Tags: focal staging Uname: Linux 5.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/17/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0DM01M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.1.1 dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd07/17/2017:svnDellInc.:pnInspiron5765:pvr1.1.1:rvnDellInc.:rn0DM01M:rvrA00:cvnDellInc.:ct10:cvr1.1.1: dmi.product.family: Inspiron dmi.product.name: Inspiron 5765 dmi.product.sku: 076A dmi.product.version: 1.1.1 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868898/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1868898] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1868898/+attachment/5341560/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1868898 Title: Ubuntu 20.04 clean install : autostandby feature Status in linux package in Ubuntu: Incomplete Bug description: Have ubuntu 20.04 development branch on my laptop and my desktop. Noticed yesterday, my laptop was idle for a while and the power light was on and keypress didnt wake it up. Pressing power button didnt wake it up either. On my tower pc I use tandby on power press and it works great. Problem seems to be in auto standby feature. I remember this bug in 18.04 development branch as well. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: steve 1606 F pulseaudio /dev/snd/controlC0: steve 1606 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-03-21 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) MachineType: Dell Inc. Inspiron 5765 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=5659d383-5314-42cf-907e-2116ea6b8145 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 RelatedPackageVersions: linux-restricted-modules-5.4.0-18-generic N/A linux-backports-modules-5.4.0-18-generic N/A linux-firmware1.187 StagingDrivers: exfat Tags: focal staging Uname: Linux 5.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/17/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0DM01M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.1.1 dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd07/17/2017:svnDellInc.:pnInspiron5765:pvr1.1.1:rvnDellInc.:rn0DM01M:rvrA00:cvnDellInc.:ct10:cvr1.1.1: dmi.product.family: Inspiron dmi.product.name: Inspiron 5765 dmi.product.sku: 076A dmi.product.version: 1.1.1 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868898/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1868898] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1868898/+attachment/5341562/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1868898 Title: Ubuntu 20.04 clean install : autostandby feature Status in linux package in Ubuntu: Incomplete Bug description: Have ubuntu 20.04 development branch on my laptop and my desktop. Noticed yesterday, my laptop was idle for a while and the power light was on and keypress didnt wake it up. Pressing power button didnt wake it up either. On my tower pc I use tandby on power press and it works great. Problem seems to be in auto standby feature. I remember this bug in 18.04 development branch as well. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: steve 1606 F pulseaudio /dev/snd/controlC0: steve 1606 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-03-21 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) MachineType: Dell Inc. Inspiron 5765 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=5659d383-5314-42cf-907e-2116ea6b8145 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 RelatedPackageVersions: linux-restricted-modules-5.4.0-18-generic N/A linux-backports-modules-5.4.0-18-generic N/A linux-firmware1.187 StagingDrivers: exfat Tags: focal staging Uname: Linux 5.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/17/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0DM01M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.1.1 dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd07/17/2017:svnDellInc.:pnInspiron5765:pvr1.1.1:rvnDellInc.:rn0DM01M:rvrA00:cvnDellInc.:ct10:cvr1.1.1: dmi.product.family: Inspiron dmi.product.name: Inspiron 5765 dmi.product.sku: 076A dmi.product.version: 1.1.1 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868898/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1868898] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1868898/+attachment/5341559/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1868898 Title: Ubuntu 20.04 clean install : autostandby feature Status in linux package in Ubuntu: Incomplete Bug description: Have ubuntu 20.04 development branch on my laptop and my desktop. Noticed yesterday, my laptop was idle for a while and the power light was on and keypress didnt wake it up. Pressing power button didnt wake it up either. On my tower pc I use tandby on power press and it works great. Problem seems to be in auto standby feature. I remember this bug in 18.04 development branch as well. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: steve 1606 F pulseaudio /dev/snd/controlC0: steve 1606 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-03-21 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) MachineType: Dell Inc. Inspiron 5765 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=5659d383-5314-42cf-907e-2116ea6b8145 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 RelatedPackageVersions: linux-restricted-modules-5.4.0-18-generic N/A linux-backports-modules-5.4.0-18-generic N/A linux-firmware1.187 StagingDrivers: exfat Tags: focal staging Uname: Linux 5.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/17/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0DM01M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.1.1 dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd07/17/2017:svnDellInc.:pnInspiron5765:pvr1.1.1:rvnDellInc.:rn0DM01M:rvrA00:cvnDellInc.:ct10:cvr1.1.1: dmi.product.family: Inspiron dmi.product.name: Inspiron 5765 dmi.product.sku: 076A dmi.product.version: 1.1.1 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868898/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1868898] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1868898/+attachment/5341590/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1868898 Title: Ubuntu 20.04 clean install : autostandby feature Status in linux package in Ubuntu: Incomplete Bug description: Have ubuntu 20.04 development branch on my laptop and my desktop. Noticed yesterday, my laptop was idle for a while and the power light was on and keypress didnt wake it up. Pressing power button didnt wake it up either. On my tower pc I use tandby on power press and it works great. Problem seems to be in auto standby feature. I remember this bug in 18.04 development branch as well. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: steve 1606 F pulseaudio /dev/snd/controlC0: steve 1606 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-03-21 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) MachineType: Dell Inc. Inspiron 5765 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=5659d383-5314-42cf-907e-2116ea6b8145 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 RelatedPackageVersions: linux-restricted-modules-5.4.0-18-generic N/A linux-backports-modules-5.4.0-18-generic N/A linux-firmware1.187 StagingDrivers: exfat Tags: focal staging Uname: Linux 5.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/17/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0DM01M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.1.1 dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd07/17/2017:svnDellInc.:pnInspiron5765:pvr1.1.1:rvnDellInc.:rn0DM01M:rvrA00:cvnDellInc.:ct10:cvr1.1.1: dmi.product.family: Inspiron dmi.product.name: Inspiron 5765 dmi.product.sku: 076A dmi.product.version: 1.1.1 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868898/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1868898] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1868898/+attachment/5341589/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1868898 Title: Ubuntu 20.04 clean install : autostandby feature Status in linux package in Ubuntu: Incomplete Bug description: Have ubuntu 20.04 development branch on my laptop and my desktop. Noticed yesterday, my laptop was idle for a while and the power light was on and keypress didnt wake it up. Pressing power button didnt wake it up either. On my tower pc I use tandby on power press and it works great. Problem seems to be in auto standby feature. I remember this bug in 18.04 development branch as well. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: steve 1606 F pulseaudio /dev/snd/controlC0: steve 1606 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-03-21 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) MachineType: Dell Inc. Inspiron 5765 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=5659d383-5314-42cf-907e-2116ea6b8145 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 RelatedPackageVersions: linux-restricted-modules-5.4.0-18-generic N/A linux-backports-modules-5.4.0-18-generic N/A linux-firmware1.187 StagingDrivers: exfat Tags: focal staging Uname: Linux 5.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/17/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0DM01M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.1.1 dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd07/17/2017:svnDellInc.:pnInspiron5765:pvr1.1.1:rvnDellInc.:rn0DM01M:rvrA00:cvnDellInc.:ct10:cvr1.1.1: dmi.product.family: Inspiron dmi.product.name: Inspiron 5765 dmi.product.sku: 076A dmi.product.version: 1.1.1 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868898/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1868898] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1868898/+attachment/5341585/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1868898 Title: Ubuntu 20.04 clean install : autostandby feature Status in linux package in Ubuntu: Incomplete Bug description: Have ubuntu 20.04 development branch on my laptop and my desktop. Noticed yesterday, my laptop was idle for a while and the power light was on and keypress didnt wake it up. Pressing power button didnt wake it up either. On my tower pc I use tandby on power press and it works great. Problem seems to be in auto standby feature. I remember this bug in 18.04 development branch as well. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: steve 1606 F pulseaudio /dev/snd/controlC0: steve 1606 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-03-21 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) MachineType: Dell Inc. Inspiron 5765 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=5659d383-5314-42cf-907e-2116ea6b8145 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 RelatedPackageVersions: linux-restricted-modules-5.4.0-18-generic N/A linux-backports-modules-5.4.0-18-generic N/A linux-firmware1.187 StagingDrivers: exfat Tags: focal staging Uname: Linux 5.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/17/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0DM01M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.1.1 dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd07/17/2017:svnDellInc.:pnInspiron5765:pvr1.1.1:rvnDellInc.:rn0DM01M:rvrA00:cvnDellInc.:ct10:cvr1.1.1: dmi.product.family: Inspiron dmi.product.name: Inspiron 5765 dmi.product.sku: 076A dmi.product.version: 1.1.1 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868898/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1868898] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1868898/+attachment/5341588/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1868898 Title: Ubuntu 20.04 clean install : autostandby feature Status in linux package in Ubuntu: Incomplete Bug description: Have ubuntu 20.04 development branch on my laptop and my desktop. Noticed yesterday, my laptop was idle for a while and the power light was on and keypress didnt wake it up. Pressing power button didnt wake it up either. On my tower pc I use tandby on power press and it works great. Problem seems to be in auto standby feature. I remember this bug in 18.04 development branch as well. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: steve 1606 F pulseaudio /dev/snd/controlC0: steve 1606 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-03-21 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) MachineType: Dell Inc. Inspiron 5765 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=5659d383-5314-42cf-907e-2116ea6b8145 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 RelatedPackageVersions: linux-restricted-modules-5.4.0-18-generic N/A linux-backports-modules-5.4.0-18-generic N/A linux-firmware1.187 StagingDrivers: exfat Tags: focal staging Uname: Linux 5.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/17/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0DM01M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.1.1 dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd07/17/2017:svnDellInc.:pnInspiron5765:pvr1.1.1:rvnDellInc.:rn0DM01M:rvrA00:cvnDellInc.:ct10:cvr1.1.1: dmi.product.family: Inspiron dmi.product.name: Inspiron 5765 dmi.product.sku: 076A dmi.product.version: 1.1.1 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868898/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1868898] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1868898/+attachment/5341591/+files/WifiSyslog.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/1868898 Title: Ubuntu 20.04 clean install : autostandby feature Status in linux package in Ubuntu: Incomplete Bug description: Have ubuntu 20.04 development branch on my laptop and my desktop. Noticed yesterday, my laptop was idle for a while and the power light was on and keypress didnt wake it up. Pressing power button didnt wake it up either. On my tower pc I use tandby on power press and it works great. Problem seems to be in auto standby feature. I remember this bug in 18.04 development branch as well. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: steve 1606 F pulseaudio /dev/snd/controlC0: steve 1606 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-03-21 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) MachineType: Dell Inc. Inspiron 5765 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=5659d383-5314-42cf-907e-2116ea6b8145 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 RelatedPackageVersions: linux-restricted-modules-5.4.0-18-generic N/A linux-backports-modules-5.4.0-18-generic N/A linux-firmware1.187 StagingDrivers: exfat Tags: focal staging Uname: Linux 5.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/17/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0DM01M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.1.1 dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd07/17/2017:svnDellInc.:pnInspiron5765:pvr1.1.1:rvnDellInc.:rn0DM01M:rvrA00:cvnDellInc.:ct10:cvr1.1.1: dmi.product.family: Inspiron dmi.product.name: Inspiron 5765 dmi.product.sku: 076A dmi.product.version: 1.1.1 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868898/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1869033] 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/1869033 Title: Lenovo IdeaPad S145-IWL - touchpad not recognized Status in linux package in Ubuntu: Confirmed Bug description: I'm trying to use Ubuntu 20.04 but it's not seeing touchpad - it's not even available in device list. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-18-generic 5.4.0-18.22 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 4248 F pulseaudio CasperVersion: 1.441 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 25 15:44:31 2020 LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200325) MachineType: LENOVO 81W8 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity RelatedPackageVersions: linux-restricted-modules-5.4.0-18-generic N/A linux-backports-modules-5.4.0-18-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/09/2019 dmi.bios.vendor: LENOVO dmi.bios.version: DKCN21WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad S145-15IIL dmi.modalias: dmi:bvnLENOVO:bvrDKCN21WW:bd10/09/2019:svnLENOVO:pn81W8:pvrLenovoIdeaPadS145-15IIL:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoIdeaPadS145-15IIL: dmi.product.family: IdeaPad S145-15IIL dmi.product.name: 81W8 dmi.product.sku: LENOVO_MT_81W8_BU_idea_FM_IdeaPad S145-15IIL dmi.product.version: Lenovo IdeaPad S145-15IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1869033/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1869032] [NEW] Kernel oopsed and null pointer dereference while running ubuntu_kernel_selftests on Eoan Power8
Public bug reported: Issue found on P8 node modoc with Eoan (5.3.0-43.36) (Note that this test has passed with P9 node baltar without any traces in syslog) The ubuntu_kernel_selftests hangs: 15:16:53 DEBUG| [stdout] ok 4 selftests: net: reuseport_dualstack 15:16:53 DEBUG| [stdout] # selftests: net: reuseaddr_conflict 15:16:53 DEBUG| [stdout] # Opening 127.0.0.1: 15:16:53 DEBUG| [stdout] # Opening INADDR_ANY: 15:16:53 DEBUG| [stdout] # bind: Address already in use 15:16:53 DEBUG| [stdout] # Opening in6addr_any: 15:16:53 DEBUG| [stdout] # Opening INADDR_ANY: 15:16:53 DEBUG| [stdout] # bind: Address already in use 15:16:53 DEBUG| [stdout] # Opening INADDR_ANY: after closing ipv6 socket 15:16:53 DEBUG| [stdout] # bind: Address already in use 15:16:53 DEBUG| [stdout] # Successok 5 selftests: net: reuseaddr_conflict 15:16:53 DEBUG| [stdout] # selftests: net: tls 15:16:56 DEBUG| [stdout] # tls.c:967:tls.mutliproc_sendpage_even:Expected status (4) == 0 (0) 15:17:26 DEBUG| [stdout] # Alarm clock 15:45:20 INFO | Timer expired (1800 sec.), nuking pid 33351 (And test continues) It looks like it's the selftests: net: tls that's causing this issue. If you ssh to the node, the following trace could be found in dmesg: Injecting error (-12) to MEM_GOING_OFFLINE Injecting error (-12) to MEM_GOING_OFFLINE Injecting error (-12) to MEM_GOING_OFFLINE Oops: Exception in kernel mode, sig: 4 [#1] LE PAGE_SIZE=64K MMU=Hash SMP NR_CPUS=2048 NUMA PowerNV Modules linked in: tls binfmt_misc dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_powernv uio_pdrv_genirq ipmi_devintf ipmi_msghandler uio powernv_rng ibmpowernv vmx_crypto leds_powernv powernv_op_panel sch_fq_codel ip_tables x_tables autofs4 ses enclosure scsi_transport_sas btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_vpmsum crc32c_vpmsum tg3 ipr [last unloaded: notifier_error_inject] CPU: 18 PID: 36045 Comm: tls Not tainted 5.3.0-43-generic #36-Ubuntu NIP: c0080a4d6a40 LR: c0080a4d6a40 CTR: c0179270 REGS: c00fc97837a0 TRAP: 0e40 Not tainted (5.3.0-43-generic) MSR: 9288b033 CR: 28002862 XER: 2000 CFAR: c000dfc4 IRQMASK: 0 GPR00: c0080a4d6a40 c00fc9783a30 c19d9000 GPR04: c00f5afc c00fc97839b8 GPR08: c00f5afc c00ff9a13780 GPR12: 88002462 c00eb380 GPR16: 0ac875961368 0ac875960d38 0ac875960d90 GPR20: 7c6b4ef0 c00e3996dc48 GPR24: c04a9d70 ea60 GPR28: c00c0398c740 cab32e70 c00f7ecebd00 NIP [c0080a4d6a40] tls_sw_sendpage+0x68/0x100 [tls] LR [c0080a4d6a40] tls_sw_sendpage+0x68/0x100 [tls] Call Trace: [c00fc9783a30] [c0080a4d6a40] tls_sw_sendpage+0x68/0x100 [tls] (unreliable) [c00fc9783a80] [c0d7698c] inet_sendpage+0x8c/0x140 [c00fc9783ad0] [c0c33fd8] kernel_sendpage+0x38/0x70 [c00fc9783af0] [c0c34044] sock_sendpage+0x34/0x50 [c00fc9783b10] [c04a9e8c] pipe_to_sendpage+0x7c/0xf0 [c00fc9783b40] [c04ab3d4] __splice_from_pipe+0x164/0x280 [c00fc9783ba0] [c04ad994] splice_from_pipe+0x74/0xc0 [c00fc9783c20] [c04a9dbc] direct_splice_actor+0x4c/0xa0 [c00fc9783c40] [c04aad14] splice_direct_to_actor+0x2a4/0x3c0 [c00fc9783cc0] [c04aaee4] do_splice_direct+0xb4/0x130 [c00fc9783d30] [c04565c4] do_sendfile+0x234/0x4a0 [c00fc9783dd0] [c0456b70] sys_sendfile64+0x160/0x170 [c00fc9783e20] [c000b388] system_call+0x5c/0x70 Instruction dump: <> ---[ end trace 8961ea39a6f2dd08 ]--- BUG: Kernel NULL pointer dereference at 0x Faulting instruction address: 0xc020bd74 Oops: Kernel access of bad area, sig: 11 [#2] LE PAGE_SIZE=64K MMU=Hash SMP NR_CPUS=2048 NUMA PowerNV Modules linked in: tls binfmt_misc dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_powernv uio_pdrv_genirq ipmi_devintf ipmi_msghandler uio powernv_rng ibmpowernv vmx_crypto leds_powernv powernv_op_panel sch_fq_codel ip_tables x_tables autofs4 ses enclosure scsi_transport_sas btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_vpmsum crc32c_vpmsum tg3 ipr [last unloaded: notifier_error_inject] CPU: 10 PID: 38095 Comm: modprobe Tainted: G D 5.3.0-43-generic #36-Ubuntu NIP: c020bd74 LR: c07a24f4 CTR: c020bd40 REG
[Kernel-packages] [Bug 1869032] Re: Kernel oopsed and null pointer dereference while running ubuntu_kernel_selftests on Eoan Power8
This is what I saw on this Eoan P8 node modoc on the last cycle: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1867155 Which makes it failed to finish the test. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1869032 Title: Kernel oopsed and null pointer dereference while running ubuntu_kernel_selftests on Eoan Power8 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Bug description: Issue found on P8 node modoc with Eoan (5.3.0-43.36) (Note that this test has passed with P9 node baltar without any traces in syslog) The ubuntu_kernel_selftests hangs: 15:16:53 DEBUG| [stdout] ok 4 selftests: net: reuseport_dualstack 15:16:53 DEBUG| [stdout] # selftests: net: reuseaddr_conflict 15:16:53 DEBUG| [stdout] # Opening 127.0.0.1: 15:16:53 DEBUG| [stdout] # Opening INADDR_ANY: 15:16:53 DEBUG| [stdout] # bind: Address already in use 15:16:53 DEBUG| [stdout] # Opening in6addr_any: 15:16:53 DEBUG| [stdout] # Opening INADDR_ANY: 15:16:53 DEBUG| [stdout] # bind: Address already in use 15:16:53 DEBUG| [stdout] # Opening INADDR_ANY: after closing ipv6 socket 15:16:53 DEBUG| [stdout] # bind: Address already in use 15:16:53 DEBUG| [stdout] # Successok 5 selftests: net: reuseaddr_conflict 15:16:53 DEBUG| [stdout] # selftests: net: tls 15:16:56 DEBUG| [stdout] # tls.c:967:tls.mutliproc_sendpage_even:Expected status (4) == 0 (0) 15:17:26 DEBUG| [stdout] # Alarm clock 15:45:20 INFO | Timer expired (1800 sec.), nuking pid 33351 (And test continues) It looks like it's the selftests: net: tls that's causing this issue. If you ssh to the node, the following trace could be found in dmesg: Injecting error (-12) to MEM_GOING_OFFLINE Injecting error (-12) to MEM_GOING_OFFLINE Injecting error (-12) to MEM_GOING_OFFLINE Oops: Exception in kernel mode, sig: 4 [#1] LE PAGE_SIZE=64K MMU=Hash SMP NR_CPUS=2048 NUMA PowerNV Modules linked in: tls binfmt_misc dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_powernv uio_pdrv_genirq ipmi_devintf ipmi_msghandler uio powernv_rng ibmpowernv vmx_crypto leds_powernv powernv_op_panel sch_fq_codel ip_tables x_tables autofs4 ses enclosure scsi_transport_sas btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_vpmsum crc32c_vpmsum tg3 ipr [last unloaded: notifier_error_inject] CPU: 18 PID: 36045 Comm: tls Not tainted 5.3.0-43-generic #36-Ubuntu NIP: c0080a4d6a40 LR: c0080a4d6a40 CTR: c0179270 REGS: c00fc97837a0 TRAP: 0e40 Not tainted (5.3.0-43-generic) MSR: 9288b033 CR: 28002862 XER: 2000 CFAR: c000dfc4 IRQMASK: 0 GPR00: c0080a4d6a40 c00fc9783a30 c19d9000 GPR04: c00f5afc c00fc97839b8 GPR08: c00f5afc c00ff9a13780 GPR12: 88002462 c00eb380 GPR16: 0ac875961368 0ac875960d38 0ac875960d90 GPR20: 7c6b4ef0 c00e3996dc48 GPR24: c04a9d70 ea60 GPR28: c00c0398c740 cab32e70 c00f7ecebd00 NIP [c0080a4d6a40] tls_sw_sendpage+0x68/0x100 [tls] LR [c0080a4d6a40] tls_sw_sendpage+0x68/0x100 [tls] Call Trace: [c00fc9783a30] [c0080a4d6a40] tls_sw_sendpage+0x68/0x100 [tls] (unreliable) [c00fc9783a80] [c0d7698c] inet_sendpage+0x8c/0x140 [c00fc9783ad0] [c0c33fd8] kernel_sendpage+0x38/0x70 [c00fc9783af0] [c0c34044] sock_sendpage+0x34/0x50 [c00fc9783b10] [c04a9e8c] pipe_to_sendpage+0x7c/0xf0 [c00fc9783b40] [c04ab3d4] __splice_from_pipe+0x164/0x280 [c00fc9783ba0] [c04ad994] splice_from_pipe+0x74/0xc0 [c00fc9783c20] [c04a9dbc] direct_splice_actor+0x4c/0xa0 [c00fc9783c40] [c04aad14] splice_direct_to_actor+0x2a4/0x3c0 [c00fc9783cc0] [c04aaee4] do_splice_direct+0xb4/0x130 [c00fc9783d30] [c04565c4] do_sendfile+0x234/0x4a0 [c00fc9783dd0] [c0456b70] sys_sendfile64+0x160/0x170 [c00fc9783e20] [c000b388] system_call+0x5c/0x70 Instruction dump: <> ---[ end trace 8961ea39a6f2dd08 ]--- BUG: Kernel NULL pointer dereference at 0x Faulting instruction address: 0xc020bd74 Oops: Kernel access of bad area, sig: 11 [#2] LE PAGE_SIZE=64K MMU=Hash SMP NR_CPUS=2048 NUMA PowerNV Modules linked in: tls bi
[Kernel-packages] [Bug 1869032] Re: Kernel oopsed and null pointer dereference while running ubuntu_kernel_selftests on Eoan Power8
A quick search with keywork "tls" in Eoan tree brought me this:
commit 299dfeeb7a216fe4dcfdd6ad0461ea93db72d389
Author: Jakub Kicinski
Date: Fri Jan 10 04:38:32 2020 -0800
net/tls: fix async operation
BugLink: https://bugs.launchpad.net/bugs/1864710
commit db885e66d268884dc72967279b7e84f522556abc upstream.
Mallesham reports the TLS with async accelerator was broken by
commit d10523d0b3d7 ("net/tls: free the record on encryption error")
because encryption can return -EINPROGRESS in such setups, which
should not be treated as an error.
The error is also present in the BPF path (likely copied from there).
Reported-by: Mallesham Jatharakonda
Fixes: d3b18ad31f93 ("tls: add bpf support to sk_msg handling")
Fixes: d10523d0b3d7 ("net/tls: free the record on encryption error")
Signed-off-by: Jakub Kicinski
Reviewed-by: Simon Horman
Signed-off-by: David S. Miller
Signed-off-by: Greg Kroah-Hartman
Signed-off-by: Kamal Mostafa
Signed-off-by: Khalid Elmously
$ git tag --contains 299dfeeb7a216fe4dcfdd6ad0461ea93db72d389
Ubuntu-5.3.0-43.35
Ubuntu-5.3.0-43.36
Need to check if this is the cause.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1869032
Title:
Kernel oopsed and null pointer dereference while running
ubuntu_kernel_selftests on Eoan Power8
Status in ubuntu-kernel-tests:
New
Status in linux package in Ubuntu:
Confirmed
Bug description:
Issue found on P8 node modoc with Eoan (5.3.0-43.36)
(Note that this test has passed with P9 node baltar without any traces in
syslog)
The ubuntu_kernel_selftests hangs:
15:16:53 DEBUG| [stdout] ok 4 selftests: net: reuseport_dualstack
15:16:53 DEBUG| [stdout] # selftests: net: reuseaddr_conflict
15:16:53 DEBUG| [stdout] # Opening 127.0.0.1:
15:16:53 DEBUG| [stdout] # Opening INADDR_ANY:
15:16:53 DEBUG| [stdout] # bind: Address already in use
15:16:53 DEBUG| [stdout] # Opening in6addr_any:
15:16:53 DEBUG| [stdout] # Opening INADDR_ANY:
15:16:53 DEBUG| [stdout] # bind: Address already in use
15:16:53 DEBUG| [stdout] # Opening INADDR_ANY: after closing ipv6 socket
15:16:53 DEBUG| [stdout] # bind: Address already in use
15:16:53 DEBUG| [stdout] # Successok 5 selftests: net: reuseaddr_conflict
15:16:53 DEBUG| [stdout] # selftests: net: tls
15:16:56 DEBUG| [stdout] # tls.c:967:tls.mutliproc_sendpage_even:Expected
status (4) == 0 (0)
15:17:26 DEBUG| [stdout] # Alarm clock
15:45:20 INFO | Timer expired (1800 sec.), nuking pid 33351
(And test continues)
It looks like it's the selftests: net: tls that's causing this issue.
If you ssh to the node, the following trace could be found in dmesg:
Injecting error (-12) to MEM_GOING_OFFLINE
Injecting error (-12) to MEM_GOING_OFFLINE
Injecting error (-12) to MEM_GOING_OFFLINE
Oops: Exception in kernel mode, sig: 4 [#1]
LE PAGE_SIZE=64K MMU=Hash SMP NR_CPUS=2048 NUMA PowerNV
Modules linked in: tls binfmt_misc dm_multipath scsi_dh_rdac scsi_dh_emc
scsi_dh_alua ipmi_powernv uio_pdrv_genirq ipmi_devintf ipmi_msghandler uio
powernv_rng ibmpowernv vmx_crypto leds_powernv powernv_op_panel sch_fq_codel
ip_tables x_tables autofs4 ses enclosure scsi_transport_sas btrfs zstd_compress
raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor
raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_vpmsum crc32c_vpmsum
tg3 ipr [last unloaded: notifier_error_inject]
CPU: 18 PID: 36045 Comm: tls Not tainted 5.3.0-43-generic #36-Ubuntu
NIP: c0080a4d6a40 LR: c0080a4d6a40 CTR: c0179270
REGS: c00fc97837a0 TRAP: 0e40 Not tainted (5.3.0-43-generic)
MSR: 9288b033 CR: 28002862
XER: 2000
CFAR: c000dfc4 IRQMASK: 0
GPR00: c0080a4d6a40 c00fc9783a30 c19d9000
GPR04: c00f5afc c00fc97839b8
GPR08: c00f5afc c00ff9a13780
GPR12: 88002462 c00eb380
GPR16: 0ac875961368 0ac875960d38 0ac875960d90
GPR20: 7c6b4ef0 c00e3996dc48
GPR24: c04a9d70 ea60
GPR28: c00c0398c740 cab32e70 c00f7ecebd00
NIP [c0080a4d6a40] tls_sw_sendpage+0x68/0x100 [tls]
LR [c0080a4d6a40] tls_sw_sendpage+0x68/0x100 [tls]
Call Trace:
[c00fc9783a30] [c0080a4d6a40] tls_sw_sendpage+0x68/0x100 [tls]
(unreliable)
[c00fc9783a80] [c0d7698c] inet_sendpage+0x8c/0x140
[c00fc9783ad0] [c0c33fd8] kernel_sendpage+0x38/0x70
[c00fc9783af0] [c0c34044] sock_sendpage+0x34/0x50
[c00fc9783b10] [c04a9e8c]
[Kernel-packages] [Bug 1869032] 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/1869032 Title: Kernel oopsed and null pointer dereference while running ubuntu_kernel_selftests on Eoan Power8 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Bug description: Issue found on P8 node modoc with Eoan (5.3.0-43.36) (Note that this test has passed with P9 node baltar without any traces in syslog) The ubuntu_kernel_selftests hangs: 15:16:53 DEBUG| [stdout] ok 4 selftests: net: reuseport_dualstack 15:16:53 DEBUG| [stdout] # selftests: net: reuseaddr_conflict 15:16:53 DEBUG| [stdout] # Opening 127.0.0.1: 15:16:53 DEBUG| [stdout] # Opening INADDR_ANY: 15:16:53 DEBUG| [stdout] # bind: Address already in use 15:16:53 DEBUG| [stdout] # Opening in6addr_any: 15:16:53 DEBUG| [stdout] # Opening INADDR_ANY: 15:16:53 DEBUG| [stdout] # bind: Address already in use 15:16:53 DEBUG| [stdout] # Opening INADDR_ANY: after closing ipv6 socket 15:16:53 DEBUG| [stdout] # bind: Address already in use 15:16:53 DEBUG| [stdout] # Successok 5 selftests: net: reuseaddr_conflict 15:16:53 DEBUG| [stdout] # selftests: net: tls 15:16:56 DEBUG| [stdout] # tls.c:967:tls.mutliproc_sendpage_even:Expected status (4) == 0 (0) 15:17:26 DEBUG| [stdout] # Alarm clock 15:45:20 INFO | Timer expired (1800 sec.), nuking pid 33351 (And test continues) It looks like it's the selftests: net: tls that's causing this issue. If you ssh to the node, the following trace could be found in dmesg: Injecting error (-12) to MEM_GOING_OFFLINE Injecting error (-12) to MEM_GOING_OFFLINE Injecting error (-12) to MEM_GOING_OFFLINE Oops: Exception in kernel mode, sig: 4 [#1] LE PAGE_SIZE=64K MMU=Hash SMP NR_CPUS=2048 NUMA PowerNV Modules linked in: tls binfmt_misc dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_powernv uio_pdrv_genirq ipmi_devintf ipmi_msghandler uio powernv_rng ibmpowernv vmx_crypto leds_powernv powernv_op_panel sch_fq_codel ip_tables x_tables autofs4 ses enclosure scsi_transport_sas btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_vpmsum crc32c_vpmsum tg3 ipr [last unloaded: notifier_error_inject] CPU: 18 PID: 36045 Comm: tls Not tainted 5.3.0-43-generic #36-Ubuntu NIP: c0080a4d6a40 LR: c0080a4d6a40 CTR: c0179270 REGS: c00fc97837a0 TRAP: 0e40 Not tainted (5.3.0-43-generic) MSR: 9288b033 CR: 28002862 XER: 2000 CFAR: c000dfc4 IRQMASK: 0 GPR00: c0080a4d6a40 c00fc9783a30 c19d9000 GPR04: c00f5afc c00fc97839b8 GPR08: c00f5afc c00ff9a13780 GPR12: 88002462 c00eb380 GPR16: 0ac875961368 0ac875960d38 0ac875960d90 GPR20: 7c6b4ef0 c00e3996dc48 GPR24: c04a9d70 ea60 GPR28: c00c0398c740 cab32e70 c00f7ecebd00 NIP [c0080a4d6a40] tls_sw_sendpage+0x68/0x100 [tls] LR [c0080a4d6a40] tls_sw_sendpage+0x68/0x100 [tls] Call Trace: [c00fc9783a30] [c0080a4d6a40] tls_sw_sendpage+0x68/0x100 [tls] (unreliable) [c00fc9783a80] [c0d7698c] inet_sendpage+0x8c/0x140 [c00fc9783ad0] [c0c33fd8] kernel_sendpage+0x38/0x70 [c00fc9783af0] [c0c34044] sock_sendpage+0x34/0x50 [c00fc9783b10] [c04a9e8c] pipe_to_sendpage+0x7c/0xf0 [c00fc9783b40] [c04ab3d4] __splice_from_pipe+0x164/0x280 [c00fc9783ba0] [c04ad994] splice_from_pipe+0x74/0xc0 [c00fc9783c20] [c04a9dbc] direct_splice_actor+0x4c/0xa0 [c00fc9783c40] [c04aad14] splice_direct_to_actor+0x2a4/0x3c0 [c00fc9783cc0] [c04aaee4] do_splice_direct+0xb4/0x130 [c00fc9783d30] [c04565c4] do_sendfile+0x234/0x4a0 [c00fc9783dd0] [c0456b70] sys_sendfile64+0x160/0x170 [c00fc9783e20] [c000b388] system_call+0x5c/0x70 Instruction dump: <> ---[ end trace 8961ea39a6f2dd08 ]--- BUG: Kernel NULL pointer dereference at 0x Faulting instruction address: 0xc020bd74 Oops: Kernel access of bad area, sig: 11 [#2] LE PAGE_SIZE=64K MMU=Hash SMP NR_CPUS=2048 NUMA PowerNV Modules linked in: tls binfmt_misc dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_powernv
[Kernel-packages] [Bug 1859754] Re: [SRU] add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
@Jean, You mentioned Bluetooth audio, that remind me that the testing alsa-lib in the #66 has some problem, I just fixed it and uploaded a new version to it, please try it. And testing alsa-lib is not SRUed yet, I plan to SRU it with this bug: #1868210. And Because the pulseaudio+ucm works greatly different from pulseaudio+non-ucm, most pulseaudio+ucm machines are headless embedded systems, it can't work as well as pulseauido+non-ucm on desktop system. To support the internal mic, Intel provided this ucm. If you prefer pulseaudio+non-ucm, you could add "options snd-hda-intel dmic_detect=0" in the /etc/modprobe.d/alsa-base.conf. With the ucm, the internal mic and headset-mic belong to different sources, and all output devices and input devices separate to different profiles, that makes the auto-selection/switch among audio devices nearly not work. And if you manually select an output device which is not in the current profile, and two or more input devices are in the new profile, you will see input device is changed when you select output device. This is a pulseaudio bug maybe, if pulseaudio has fix, I will backport it. About the issue on google meet, it is a problem, do you also meet the similar issue on other audio apps? -- 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/1859754 Title: [SRU] add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines) Status in HWE Next: Fix Released Status in alsa-lib package in Ubuntu: Invalid Status in alsa-lib source package in Bionic: Fix Released Status in alsa-lib source package in Eoan: Fix Released Bug description: This ucm is only for Eoan and Bionic, for focal and future versions, we plan to integrate the ucm2 instead of this ucm, and the ucm2 depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under developing by the community, is not ready yet. [Impact] In the oem project, we have a couple of Lenovo and Dell machines which connect the digital mic to PCH directly, this design needs the new sound driver soc/sof, and this driver can't work under pulseaudio automatically, we need to integrate the ucm for the driver, then the sof dirver could work under pulseaudio and gnome. This ucm is maintained by intel audio team, and it is not upstreamed and will not be upstreamed, since the community is developing the ucm2 which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still under developing), for bionic and eoan, we have to integrate this ucm since the alsa-lib version is too low. For focal and future version, we are going to integrate the ucm2 after the ucm2 is ready. This ucm is already verified in the oem project, now it is time to put it into the stock ubuntu. [Fix] These ucm files are backported from sof_ucm1 branch of https://github.com/thesofproject/alsa-ucm-conf.git [Test Case] Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of pulseaudio, the ucm files are loaded successfully, then check the gnome-sound-setting, both output and input devices work well. [Regression Risk] Low, just add some new ucm files, and this will not affect other machines, and those new added ucm files are only used by specific machines which enable the sof driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1859754/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856392] Re: [HP ZBook 15 G6, Realtek ALC285, Black Mic, Right] Microphone not detected
Hi all, I have the same laptop HP ZBook 15 G6 and my mike is not recognised too. I'm using ubuntu 18.04 kernel version 5.3.0-28-generic, and with the newer kernels my whole sound card is not recognised. If you look at this documentation http://h20195.www2.hp.com/v2/getpdf.aspx/4AA7-6280ENW.pdf page 12 , they say: "11 Audio output via speakers function. Audio input via built-in microphone is currently not functional due to a missing driver. Please check with your distro vendor for the availability of the snd-sof-pci driver in ALSA." -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1856392 Title: [HP ZBook 15 G6, Realtek ALC285, Black Mic, Right] Microphone not detected Status in alsa-driver package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Hello, on a brand new HPZbook15G6, with a fresh dual boot 19.10 Ubuntu install, I have no internal mic detected. The GNOME settings sound entry list is empty. Speaker sound is working properly. When hooking a microphone enabled headphone on the jack plug, the headphones mic is then detected, but there is now no sound output on the headphone. I've been looking for a few similar issues on recent (HP or not) laptops and found a few similar issues : Bug #1523100 Bug #1837821 so I guess this is a generic alsa or snd-hda-intel issue with newer ALC2xx hardware. I already tryed quite a few of the workaroubds/fix available here and there (e.g. overriding pin with hdajackretask, adding options to snd-hda-intel module etc. none with success) I'm available to test/provide any additional needed data. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mathieu1719 F pulseaudio /dev/snd/controlC0: mathieu1719 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Dec 14 13:33:14 2019 InstallationDate: Installed on 2019-12-13 (0 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=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful Symptom_Card: Audio interne - HDA Intel PCH Symptom_Jack: Black Mic, Right Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH successful Symptom_Type: Only some of inputs are working Title: [HP ZBook 15 G6, Realtek ALC285, Black Mic, Right] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/06/2019 dmi.bios.vendor: HP dmi.bios.version: R92 Ver. 01.03.04 dmi.board.name: 860F dmi.board.vendor: HP dmi.board.version: KBC Version 65.23.00 dmi.chassis.asset.tag: 5CD944676Z dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrR92Ver.01.03.04:bd11/06/2019:svnHP:pnHPZBook15G6:pvr:rvnHP:rn860F:rvrKBCVersion65.23.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ZBook dmi.product.name: HP ZBook 15 G6 dmi.product.sku: 6VD99AV dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-12-14T13:26:02.404591 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1856392/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864484] Re: Update SmartPQI driver in Focal to 1.2.10-025
Customer notified to test new kernels and verify the driver 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/1864484 Title: Update SmartPQI driver in Focal to 1.2.10-025 Status in linux package in Ubuntu: Fix Committed Status in linux source package in Focal: Fix Committed Bug description: [IMPACT] Feature request to update the SmartPQI driver in Focal to 1.2.10-025 Microchip produces the Smart Storage controllers that are used by several major OEMs we partner with. There is a new generation of controller coming to market later this summer. While customers will be able to use these new controllers with the driver as it is in Focal today, they will be missing several bug fixes and enhancements that have already landed upstream in 5.5. For this reason, Microchip and HPE have asked us to pull these patches to update the SmartPQI driver in Focal to the current upstream version. [FIXES] These are the recommended patches from Microchip that should be cherry-picked from mainline. 390e28087823 scsi: smartpqi: bump version 694c5d5b4625 scsi: smartpqi: Align driver syntax with oob 0fa31a88bfd2 scsi: smartpqi: remove unused manifest constants 5b083b305b49 scsi: smartpqi: fix problem with unique ID for physical device e655d469c32d scsi: smartpqi: correct syntax issue bb9af08cfc41 scsi: smartpqi: change TMF timeout from 60 to 30 seconds c2922f174fa0 scsi: smartpqi: fix LUN reset when fw bkgnd thread is hung 21432010d528 scsi: smartpqi: add inquiry timeouts b969261134c1 scsi: smartpqi: fix call trace in device discovery 0530736e40a0 scsi: smartpqi: fix controller lockup observed during force reboot 9e322310e16c scsi: smartpqi: clean up an indentation issue 1c6294858950 scsi: smartpqi: remove set but not used variable 'ctrl_info' a3a65ddd79c3 scsi: smartpqi: clean up indentation of a statement All are clean cherry picks into the 5.4 branch and can be pulled from my branch here: https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/focal/+ref/1864484-smartpqi-to-1.2.10-025 [TESTING] modinfo for smartpqi should show: version:1.2.10-025 description:Driver for Microsemi Smart Family Controller version 1.2.10-025 [REGRESSION RISK] Low - Focal is not yet released, this is not being backported to current releases, patches pick cleanly and have been tested by the upstream maintainers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864484/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859754] Re: [SRU] add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
Thanks for the explanations. I'll keep working with pulseaudio+ucm for now so as to be able to test your fixes. If it becomes too unbearable I'll revert to dmic_detect=0 >About the issue on google meet, it is a problem, do you also meet the similar issue on other audio apps? Regarding the microphone issue, it seems to be chromium specific, possibly related to the fact that chromium is a snap and is therefore sandboxed. here is the corresponding dmesg trace : [24350.178216] sof-audio-pci :00:1f.3: error: no reply expected, received 0x0 [24350.270480] sof-audio-pci :00:1f.3: firmware boot complete [24354.651222] input: 2C:41:A1:47:C5:93 as /devices/virtual/input/input24 [24354.693912] audit: type=1107 audit(1585155460.615:229): pid=1284 uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_signal" bus="system" path="/org/freedesktop/NetworkManager" interface="org.freedesktop.NetworkManager" member="CheckPermissions" name=":1.8" mask="receive" pid=8453 label="snap.spotify.spotify" peer_pid=1291 peer_label="unconfined" exe="/usr/bin/dbus-daemon" sauid=103 hostname=? addr=? terminal=?' [24354.930070] Bluetooth: hci0: SCO packet for unknown connection handle 0 [24354.940107] Bluetooth: hci0: SCO packet for unknown connection handle 0 [24354.940110] Bluetooth: hci0: SCO packet for unknown connection handle 0 [24354.940110] Bluetooth: hci0: SCO packet for unknown connection handle 0 [24364.030170] Bluetooth: hci0: SCO packet for unknown connection handle 257 [24364.030176] Bluetooth: hci0: SCO packet for unknown connection handle 257 [24364.030177] Bluetooth: hci0: SCO packet for unknown connection handle 257 [24365.009964] Bluetooth: hci0: SCO packet for unknown connection handle 0 [24365.009968] Bluetooth: hci0: SCO packet for unknown connection handle 0 [24365.019991] Bluetooth: hci0: SCO packet for unknown connection handle 0 [24365.019995] Bluetooth: hci0: SCO packet for unknown connection handle 0 [24365.019996] Bluetooth: hci0: SCO packet for unknown connection handle 0 [24365.094089] Bluetooth: hci0: SCO packet for unknown connection handle 257 [24365.094093] Bluetooth: hci0: SCO packet for unknown connection handle 257 [24365.094095] Bluetooth: hci0: SCO packet for unknown connection handle 257 [24365.244985] Bluetooth: hci0: SCO packet for unknown connection handle 0 [24365.244988] Bluetooth: hci0: SCO packet for unknown connection handle 0 [24365.244989] Bluetooth: hci0: SCO packet for unknown connection handle 0 [24365.254999] Bluetooth: hci0: SCO packet for unknown connection handle 0 [24365.255003] Bluetooth: hci0: SCO packet for unknown connection handle 0 [24365.255004] Bluetooth: hci0: SCO packet for unknown connection handle 0 [24365.467006] Bluetooth: hci0: SCO packet for unknown connection handle 0 [24365.467011] Bluetooth: hci0: SCO packet for unknown connection handle 0 [24365.467012] Bluetooth: hci0: SCO packet for unknown connection handle 0 [24365.467014] Bluetooth: hci0: SCO packet for unknown connection handle 0 [24365.477005] Bluetooth: hci0: SCO packet for unknown connection handle 0 [24365.522114] Bluetooth: hci0: SCO packet for unknown connection handle 257 [24365.522117] Bluetooth: hci0: SCO packet for unknown connection handle 257 [24365.748003] Bluetooth: hci0: SCO packet for unknown connection handle 0 [24365.748012] Bluetooth: hci0: SCO packet for unknown connection handle 0 [24365.748013] Bluetooth: hci0: SCO packet for unknown connection handle 0 [24365.758019] Bluetooth: hci0: SCO packet for unknown connection handle 0 [24365.758025] Bluetooth: hci0: SCO packet for unknown connection handle 0 [24365.842064] Bluetooth: hci0: SCO packet for unknown connection handle 257 [24365.842067] Bluetooth: hci0: SCO packet for unknown connection handle 257 [24366.023968] Bluetooth: hci0: SCO packet for unknown connection handle 0 [24366.023972] Bluetooth: hci0: SCO packet for unknown connection handle 0 [24366.034004] Bluetooth: hci0: SCO packet for unknown connection handle 0 [24366.034008] Bluetooth: hci0: SCO packet for unknown connection handle 0 [24366.034010] Bluetooth: hci0: SCO packet for unknown connection handle 0 [24366.295004] Bluetooth: hci0: SCO packet for unknown connection handle 0 [24366.295009] Bluetooth: hci0: SCO packet for unknown connection handle 0 [24366.304979] Bluetooth: hci0: SCO packet for unknown connection handle 0 [24366.304982] Bluetooth: hci0: SCO packet for unknown connection handle 0 [24366.304983] Bluetooth: hci0: SCO packet for unknown connection handle 0 [24366.338045] Bluetooth: hci0: SCO packet for unknown connection handle 257 [24366.338048] Bluetooth: hci0: SCO packet for unknown connection handle 257 [24366.338049] Bluetooth: hci0: SCO packet for unknown connection handle 257 [24366.426008] Bluetooth: hci0: SCO packet for unknown connection handle 0 [24366.426014] Bluetooth: hci0: SCO packet for unknown connection handle 0 [24366.426015] Bluetooth: hci0: SCO packet for unknown connection
[Kernel-packages] [Bug 1859754] Re: [SRU] add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
the dmesg with only the chrome attempt ** Attachment added: "dmesg-202003251809.txt" https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1859754/+attachment/5341612/+files/dmesg-202003251809.txt -- 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/1859754 Title: [SRU] add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines) Status in HWE Next: Fix Released Status in alsa-lib package in Ubuntu: Invalid Status in alsa-lib source package in Bionic: Fix Released Status in alsa-lib source package in Eoan: Fix Released Bug description: This ucm is only for Eoan and Bionic, for focal and future versions, we plan to integrate the ucm2 instead of this ucm, and the ucm2 depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under developing by the community, is not ready yet. [Impact] In the oem project, we have a couple of Lenovo and Dell machines which connect the digital mic to PCH directly, this design needs the new sound driver soc/sof, and this driver can't work under pulseaudio automatically, we need to integrate the ucm for the driver, then the sof dirver could work under pulseaudio and gnome. This ucm is maintained by intel audio team, and it is not upstreamed and will not be upstreamed, since the community is developing the ucm2 which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still under developing), for bionic and eoan, we have to integrate this ucm since the alsa-lib version is too low. For focal and future version, we are going to integrate the ucm2 after the ucm2 is ready. This ucm is already verified in the oem project, now it is time to put it into the stock ubuntu. [Fix] These ucm files are backported from sof_ucm1 branch of https://github.com/thesofproject/alsa-ucm-conf.git [Test Case] Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of pulseaudio, the ucm files are loaded successfully, then check the gnome-sound-setting, both output and input devices work well. [Regression Risk] Low, just add some new ucm files, and this will not affect other machines, and those new added ucm files are only used by specific machines which enable the sof driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1859754/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859754] Re: [SRU] add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
I just installed the latest package from your PPA: it actually makes the looping issue worse. now the issue occurs as soon as I create a meeting in meets.google.com with chromium. I tried right after to create a meeting in firefox and couldnt' get the headset to work at all. After restarting the headset, in firefox the headset behaved as I would expect and I didn't have the error anymore. I attached the whole boot's dmesg to this comment. ** Attachment added: "dmesg-202003251813.txt" https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1859754/+attachment/5341611/+files/dmesg-202003251813.txt -- 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/1859754 Title: [SRU] add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines) Status in HWE Next: Fix Released Status in alsa-lib package in Ubuntu: Invalid Status in alsa-lib source package in Bionic: Fix Released Status in alsa-lib source package in Eoan: Fix Released Bug description: This ucm is only for Eoan and Bionic, for focal and future versions, we plan to integrate the ucm2 instead of this ucm, and the ucm2 depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under developing by the community, is not ready yet. [Impact] In the oem project, we have a couple of Lenovo and Dell machines which connect the digital mic to PCH directly, this design needs the new sound driver soc/sof, and this driver can't work under pulseaudio automatically, we need to integrate the ucm for the driver, then the sof dirver could work under pulseaudio and gnome. This ucm is maintained by intel audio team, and it is not upstreamed and will not be upstreamed, since the community is developing the ucm2 which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still under developing), for bionic and eoan, we have to integrate this ucm since the alsa-lib version is too low. For focal and future version, we are going to integrate the ucm2 after the ucm2 is ready. This ucm is already verified in the oem project, now it is time to put it into the stock ubuntu. [Fix] These ucm files are backported from sof_ucm1 branch of https://github.com/thesofproject/alsa-ucm-conf.git [Test Case] Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of pulseaudio, the ucm files are loaded successfully, then check the gnome-sound-setting, both output and input devices work well. [Regression Risk] Low, just add some new ucm files, and this will not affect other machines, and those new added ucm files are only used by specific machines which enable the sof driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1859754/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1869061] [NEW] Focal update: v5.4.28 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: v5.4.28 upstream stable release from git://git.kernel.org/ locks: fix a potential use-after-free problem when wakeup a waiter locks: reinstate locks_delete_block optimization spi: spi-omap2-mcspi: Support probe deferral for DMA channels drm/mediatek: Find the cursor plane instead of hard coding it phy: ti: gmii-sel: fix set of copy-paste errors phy: ti: gmii-sel: do not fail in case of gmii ARM: dts: dra7-l4: mark timer13-16 as pwm capable spi: qup: call spi_qup_pm_resume_runtime before suspending powerpc: Include .BTF section cifs: fix potential mismatch of UNC paths cifs: add missing mount option to /proc/mounts ARM: dts: dra7: Add "dma-ranges" property to PCIe RC DT nodes spi: pxa2xx: Add CS control clock quirk spi/zynqmp: remove entry that causes a cs glitch drm/exynos: dsi: propagate error value and silence meaningless warning drm/exynos: dsi: fix workaround for the legacy clock name drm/exynos: hdmi: don't leak enable HDMI_EN regulator if probe fails drivers/perf: fsl_imx8_ddr: Correct the CLEAR bit definition drivers/perf: arm_pmu_acpi: Fix incorrect checking of gicc pointer altera-stapl: altera_get_note: prevent write beyond end of 'key' dm bio record: save/restore bi_end_io and bi_integrity dm integrity: use dm_bio_record and dm_bio_restore riscv: avoid the PIC offset of static percpu data in module beyond 2G limits ASoC: stm32: sai: manage rebind issue spi: spi_register_controller(): free bus id on error paths riscv: Force flat memory model with no-mmu riscv: Fix range looking for kernel image memblock drm/amdgpu: clean wptr on wb when gpu recovery drm/amd/display: Clear link settings on MST disable connector drm/amd/display: fix dcc swath size calculations on dcn1 xenbus: req->body should be updated before req->state xenbus: req->err should be updated before req->state block, bfq: fix overwrite of bfq_group pointer in bfq_find_set_group() parse-maintainers: Mark as executable binderfs: use refcount for binder control devices too Revert "drm/fbdev: Fallback to non tiled mode if all tiles not present" usb: quirks: add NO_LPM quirk for RTL8153 based ethernet adapters USB: serial: option: add ME910G1 ECM composition 0x110b usb: host: xhci-plat: add a shutdown USB: serial: pl2303: add device-id for HP LD381 usb: xhci: apply XHCI_SUSPEND_DELAY to AMD XHCI controller 1022:145c usb: typec: ucsi: displayport: Fix NULL pointer dereference usb: typec: ucsi: displayport: Fix a potential race during registration USB: cdc-acm: fix close_delay and closing_wait units in TIOCSSERIAL USB: cdc-acm: fix rounding error in TIOCSSERIAL ALSA: line6: Fix endless MIDI read loop ALSA: hda/realtek - Enable headset mic of Acer X2660G with ALC662 ALSA: hda/realtek - Enable the headset of Acer N50-600 with ALC662 ALSA: seq: virmidi: Fix running status after receiving sysex ALSA: seq: oss: Fix running status after receiving sysex ALSA: pcm: oss: Avoid plugin buffer overflow ALSA: pcm: oss: Remove WARNING from snd_pcm_plug_alloc() checks tty: fix compat TIOCGSERIAL leaking uninitialized memory tty: fix compat TIOCGSERIAL checking wrong function ptr iio: chemical: sps30: fix missing triggered buffer dependency iio: st_sensors: remap SMO8840 to LIS2DH12 iio: trigger: stm32-timer: disable master mode when stopping iio: accel: adxl372: Set iio_chan BE iio: magnetometer: ak8974: Fix negative raw values in sysfs iio: adc: stm32-dfsdm: fix sleep in atomic context iio: adc: at91-sama5d2_adc: fix differential channels in triggered mode iio: light: vcnl4000: update sampling periods for vcnl4200 iio: light: vcnl4000: update sampling periods for vcnl4040 mmc: rtsx_pci: Fix support for speed-modes that relies on tuning mmc: sdhci-of-at91: fix cd-gpios for SAMA5D2 mmc: sdhci-cadence: set SDHCI_QUIRK2_PRESET_VALUE_BROKEN for UniPhier CIFS: fiemap: do not return EINVAL if get nothing kbuild: Disable -Wpointer-to-enum-cast staging: rtl8188eu: Add device id for MERCUSYS MW150US v2 staging: greybus: loopback_test: fix poll-mask build breakage staging/speakup: fix get_word non-space look-ahead intel_th: msu: Fix the unexpected state warning intel_th: Fix user-visible error codes intel_th: pci: Add Elkhart Lake CPU support modpost: move the namespace field in Module.symvers last rtc: max8907: add missing select REGMAP_IRQ arm64: compat: Fix syscall number of compat_clock_getres xhci: Do not open code __print_symbolic() in xhci trace events btrfs: fix log context list corruption after rename whiteout error drm/amd/amdgpu: Fix GPR read from debugfs (v2) drm/lease: fix WARNING
[Kernel-packages] [Bug 1869061] Re: Focal update: v5.4.28 upstream stable release
** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The following upstream + stable patches should be included in the Ubuntu kernel: - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: + v5.4.28 upstream stable release + from git://git.kernel.org/ -v5.4.28 upstream stable release -from git://git.kernel.org/ + perf/x86/amd: Add support for Large Increment per Cycle Events + EDAC/amd64: Add family ops for Family 19h Models 00h-0Fh + x86/MCE/AMD, EDAC/mce_amd: Add new Load Store unit McaType + EDAC/mce_amd: Always load on SMCA systems + x86/amd_nb: Add Family 19h PCI IDs + EDAC/amd64: Drop some family checks for newer systems + locks: fix a potential use-after-free problem when wakeup a waiter + locks: reinstate locks_delete_block optimization + spi: spi-omap2-mcspi: Support probe deferral for DMA channels + drm/mediatek: Find the cursor plane instead of hard coding it + phy: ti: gmii-sel: fix set of copy-paste errors + phy: ti: gmii-sel: do not fail in case of gmii + ARM: dts: dra7-l4: mark timer13-16 as pwm capable + spi: qup: call spi_qup_pm_resume_runtime before suspending + powerpc: Include .BTF section + cifs: fix potential mismatch of UNC paths + cifs: add missing mount option to /proc/mounts + ARM: dts: dra7: Add "dma-ranges" property to PCIe RC DT nodes + spi: pxa2xx: Add CS control clock quirk + spi/zynqmp: remove entry that causes a cs glitch + drm/exynos: dsi: propagate error value and silence meaningless warning + drm/exynos: dsi: fix workaround for the legacy clock name + drm/exynos: hdmi: don't leak enable HDMI_EN regulator if probe fails + drivers/perf: fsl_imx8_ddr: Correct the CLEAR bit definition + drivers/perf: arm_pmu_acpi: Fix incorrect checking of gicc pointer + altera-stapl: altera_get_note: prevent write beyond end of 'key' + dm bio record: save/restore bi_end_io and bi_integrity + dm integrity: use dm_bio_record and dm_bio_restore + riscv: avoid the PIC offset of static percpu data in module beyond 2G limits + ASoC: stm32: sai: manage rebind issue + spi: spi_register_controller(): free bus id on error paths + riscv: Force flat memory model with no-mmu + riscv: Fix range looking for kernel image memblock + drm/amdgpu: clean wptr on wb when gpu recovery + drm/amd/display: Clear link settings on MST disable connector + drm/amd/display: fix dcc swath size calculations on dcn1 + xenbus: req->body should be updated before req->state + xenbus: req->err should be updated before req->state + block, bfq: fix overwrite of bfq_group pointer in bfq_find_set_group() + parse-maintainers: Mark as executable + binderfs: use refcount for binder control devices too + Revert "drm/fbdev: Fallback to non tiled mode if all tiles not present" + usb: quirks: add NO_LPM quirk for RTL8153 based ethernet adapters + USB: serial: option: add ME910G1 ECM composition 0x110b + usb: host: xhci-plat: add a shutdown + USB: serial: pl2303: add device-id for HP LD381 + usb: xhci: apply XHCI_SUSPEND_DELAY to AMD XHCI controller 1022:145c + usb: typec: ucsi: displayport: Fix NULL pointer dereference + usb: typec: ucsi: displayport: Fix a potential race during registration + USB: cdc-acm: fix close_delay and closing_wait units in TIOCSSERIAL + USB: cdc-acm: fix rounding error in TIOCSSERIAL + ALSA: line6: Fix endless MIDI read loop + ALSA: hda/realtek - Enable headset mic of Acer X2660G with ALC662 + ALSA: hda/realtek - Enable the headset of Acer N50-600 with ALC662 + ALSA: seq: virmidi: Fix running status after receiving sysex + ALSA: seq: oss: Fix running status after receiving sysex + ALSA: pcm: oss: Avoid plugin buffer overflow + ALSA: pcm: oss: Remove WARNING from snd_pcm_plug_alloc() checks + tty: fix compat TIOCGSERIAL leaking uninitialized memory + tty: fix compat TIOCGSERIAL checking wrong function ptr + iio: chemical: sps30: fix missing triggered buffer dependency + iio: st_sensors: remap SMO8840 to LIS2DH12 + iio: trigger: stm32-timer: disable master mode when stopping + iio: accel: adxl372: Set iio_chan BE + iio: magnetometer: ak8974: Fix negative raw values in sysfs + iio: adc: stm32-dfsdm: fix sleep in atomic context + iio: adc: at91-sama5d2_adc: fix differential channels in triggered mode + iio: light: vcnl4000: update
[Kernel-packages] [Bug 1868733] Re: Battery charge state frozen/incorrect
Latest Ubuntu-base package update corrected this error for me. ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1868733 Title: Battery charge state frozen/incorrect Status in linux package in Ubuntu: Fix Released Bug description: This may be a copy of: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824886 However with the bug's age I did not want to take a chance and reported separately and commented/subscribed there as well. Running Kubuntu 19.10. After running 45 minutes, unplugged, on old computer, with brightness 100% and streaming video: $ upower -d Device: /org/freedesktop/UPower/devices/line_power_ACAD native-path: ACAD power supply: yes updated: Tue 24 Mar 2020 08:48:42 AM CDT (2763 seconds ago) has history: no has statistics: no line-power warning-level: none online: yes icon-name: 'ac-adapter-symbolic' Device: /org/freedesktop/UPower/devices/battery_BAT1 native-path: BAT1 vendor: TOSHIBA model:PABAS0241231 serial: power supply: yes updated: Tue 24 Mar 2020 09:34:43 AM CDT (2 seconds ago) has history: yes has statistics: yes battery present: yes rechargeable:yes state: fully-charged warning-level: none energy: 4294.84 Wh energy-empty:0 Wh energy-full: 4294.84 Wh energy-full-design: 4294.84 Wh energy-rate: 0 W voltage: 65.535 V percentage: 100% capacity:100% technology: lithium-ion icon-name: 'battery-full-charged-symbolic' Device: /org/freedesktop/UPower/devices/DisplayDevice power supply: yes updated: Tue 24 Mar 2020 08:26:14 AM CDT (4111 seconds ago) has history: no has statistics: no battery present: yes state: fully-charged warning-level: none energy: 4294.84 Wh energy-full: 4294.84 Wh energy-rate: 0 W percentage: 100% icon-name: 'battery-full-charged-symbolic' Daemon: daemon-version: 0.99.11 on-battery: no lid-is-closed: no lid-is-present: yes critical-action: HybridSleep _ $ acpi Battery 0: Not charging, 100% _ $ cat /sys/class/power_supply/BAT1/charge* 65535000 65535000 65535000 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sperger1086 F pulseaudio /dev/snd/controlC0: sperger1086 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2020-03-11 (12 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 001 Device 003: ID 04f2:b446 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 8087:8000 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: TOSHIBA Satellite C55-B Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic root=UUID=fd25621b-6551-420a-a1c5-13a0746ae679 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-42-generic N/A linux-backports-modules-5.3.0-42-generic N/A linux-firmware1.183.4 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: eoan Uname: Linux 5.3.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/19/2014 dmi.bios.vendor: TOSHIBA dmi.bios.version: 1.30 dmi.board.asset.tag: * dmi.board.name: ZSWAA dmi.board.vendor: TOSHIBA dmi.board.version: 1.00 dmi.chassis.asset.tag: * dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: * dmi.modalias: dmi:bvnTOSHIBA:bvr1.30:bd07/19/2014:svnTOSHIBA:pnSatelliteC55-B:pvrPSCLUU-05M07V:rvnTOSHIBA:rnZSWAA:rvr1.00:cvnTOSHIBA:ct
[Kernel-packages] [Bug 1869062] [NEW] Acer Aspire 7715 microphone not detected
Public bug reported: System:Host: jdole-Aspire-7715Z Kernel: 4.15.0-91-generic x86_64 bits: 64 compiler: gcc v: 7.4.0 Desktop: Cinnamon 4.4.8 wm: muffin dm: LightDM Distro: Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic Machine: Type: Laptop System: Acer product: Aspire 7715Z v: V3.04 serial: Mobo: Acer model: Aspire 7715Z v: V3.04 serial: BIOS: Acer v: 3.04 date: 12/16/2009 CPU: Topology: Dual Core model: Pentium T4400 bits: 64 type: MCP arch: Penryn rev: A L2 cache: 1024 KiB flags: lm nx pae sse sse2 sse3 ssse3 bogomips: 8778 Speed: 2195 MHz min/max: 1200/2200 MHz Core speeds (MHz): 1: 2195 2: 2195 Graphics: Device-1: Intel Mobile 4 Series Integrated Graphics vendor: Acer Incorporated ALI driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:2a42 Display: x11 server: X.Org 1.19.6 driver: modesetting unloaded: fbdev,vesa resolution: 1600x900~60Hz OpenGL: renderer: Mesa DRI Mobile Intel GM45 Express v: 2.1 Mesa 19.2.8 direct render: Yes Audio: Device-1: Intel 82801I HD Audio vendor: Acer Incorporated ALI driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:293e Sound Server: ALSA v: k4.15.0-91-generic Network: Device-1: Qualcomm Atheros AR928X Wireless Network Adapter vendor: Lite-On driver: ath9k v: kernel port: 5000 bus ID: 04:00.0 chip ID: 168c:002a IF: wlp4s0 state: up mac: Device-2: Qualcomm Atheros AR8132 Fast Ethernet vendor: Acer Incorporated ALI driver: atl1c v: 1.0.1.1-NAPI port: 1000 bus ID: 05:00.0 chip ID: 1969:1062 IF: enp5s0 state: down mac: Drives:Local Storage: total: 465.76 GiB used: 33.06 GiB (7.1%) ID-1: /dev/sda vendor: Western Digital model: WD5000BEVT-22A0RT0 size: 465.76 GiB speed: 3.0 Gb/s serial: Partition: ID-1: / size: 211.37 GiB used: 33.06 GiB (15.6%) fs: ext4 dev: /dev/sda5 Sensors: System Temperatures: cpu: 54.0 C mobo: N/A Fan Speeds (RPM): N/A Repos: No active apt repos in: /etc/apt/sources.list Active apt repos in: /etc/apt/sources.list.d/google-chrome.list 1: deb [arch=amd64] http: //dl.google.com/linux/chrome/deb/ stable main Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list 1: deb http: //mint.remi.lu tricia main upstream import backport 2: deb http: //ubuntu.mirror.serverloft.de/ubuntu bionic main restricted universe multiverse 3: deb http: //ubuntu.mirror.serverloft.de/ubuntu bionic-updates main restricted universe multiverse 4: deb http: //ubuntu.mirror.serverloft.de/ubuntu bionic-backports main restricted universe multiverse 5: deb http: //security.ubuntu.com/ubuntu/ bionic-security main restricted universe multiverse 6: deb http: //archive.canonical.com/ubuntu/ bionic partner Active apt repos in: /etc/apt/sources.list.d/skype-stable.list 1: deb [arch=amd64] https: //repo.skype.com/deb stable main Active apt repos in: /etc/apt/sources.list.d/teamviewer.list 1: deb http: //linux.teamviewer.com/deb stable main Info: Processes: 214 Uptime: 8h 09m Memory: 3.78 GiB used: 2.69 GiB (71.0%) Init: systemd v: 237 runlevel: 5 Compilers: gcc: 7.5.0 alt: 7 Client: Unknown python3.6 client inxi: 3.0.32 ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1869062 Title: Acer Aspire 7715 microphone not detected Status in linux package in Ubuntu: Incomplete Bug description: System:Host: jdole-Aspire-7715Z Kernel: 4.15.0-91-generic x86_64 bits: 64 compiler: gcc v: 7.4.0 Desktop: Cinnamon 4.4.8 wm: muffin dm: LightDM Distro: Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic Machine: Type: Laptop System: Acer product: Aspire 7715Z v: V3.04 serial: Mobo: Acer model: Aspire 7715Z v: V3.04 serial: BIOS: Acer v: 3.04 date: 12/16/2009 CPU: Topology: Dual Core model: Pentium T4400 bits: 64 type: MCP arch: Penryn rev: A L2 cache: 1024 KiB flags: lm nx pae sse sse2 sse3 ssse3 bogomips: 8778 Speed: 2195 MHz min/max: 1200/2200 MHz Core speeds (MHz): 1: 2195 2: 2195 Graphics: Device-1: Intel Mobile 4 Series Integrated Graphics vendor: Acer Incorporated ALI driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:2a42 Display: x11 server: X.Org 1.19.6 driver: modesetting unloaded: fbdev,vesa resolution: 1600x900~60Hz OpenGL: renderer: Mesa DRI Mobile Intel GM45 Express
[Kernel-packages] [Bug 1824886] Re: Battery level stuck at 100% and Estimating...
I dont want to close this bug report as fix released, but after my update of ubuntu-base yesterday the issue is gone. If the original bug reported agrees, then the bug report can be closed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1824886 Title: Battery level stuck at 100% and Estimating... Status in linux package in Ubuntu: Confirmed Bug description: Battery applet does not display battery charge. Always shows 100%. ASUS 1215T-RED008S. Description: Ubuntu 18.04.2 LTS Release: 18.04 gnome-control-center: Установлен: 1:3.28.2-0ubuntu0.18.04.2 Кандидат: 1:3.28.2-0ubuntu0.18.04.3 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 16 00:48:18 2019 InstallationDate: Installed on 2019-04-10 (5 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824886/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
