[Kernel-packages] [Bug 1861610] Re: 'Elan touchpad' not detected on 'Lenovo ThinkBook 15 IIL'
Hi, I bought the Thinkbook 15IIL some days ago, although I read, that I would have trouble with the touchpad. I adapted Ferenc's post #66 for Manjaro (Arch) and it's working like a charm. You don't need to change that much. Just install all packages with pacman -S cpio iasl And please use this command within the patch file, according to thread #96. #!/bin/sh sed -i -E 's/^(\s*initrd\s+)(\S*\/)(.*)$/\1\2acpi_fixed.cpio \2\3/g' \ /boot/grub/grub.cfg.new After a reboot, the Touchpad is working quite well. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1861610 Title: 'Elan touchpad' not detected on 'Lenovo ThinkBook 15 IIL' Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.6 package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Released Status in linux-oem-5.6 source package in Bionic: Invalid Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Eoan: Fix Released Status in linux-oem-5.6 source package in Eoan: Invalid Status in linux-oem-osp1 source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Status in linux-oem-5.6 source package in Focal: Fix Released Status in linux-oem-osp1 source package in Focal: Invalid Bug description: [SRU Justification] [Impact] Touchpad function unavailable on some platforms with new ELAN touchpad HIDs. [Fix] https://lore.kernel.org/linux-input/000201d5a8bd$9fead3f0$dfc07bd0$@emc.com.tw/ required to match these currently unsupported IDs. [Test Case] 1. check if platform is affected, e.g. with ELAN0634: $ sudo acpidump | grep -C3 ELAN 2A060: 49 4E 54 31 70 0A 20 49 44 41 44 A4 84 53 42 46 INT1p.IDAD..SBF 2A070: 53 53 42 46 49 00 5B 82 42 0E 54 50 44 32 08 5F SSBFI.[.B.TPD2._ 2A080: 41 44 52 00 08 49 44 41 44 00 08 48 49 44 32 00 ADR..IDAD..HID2. 2A090: 08 5F 48 49 44 0D 45 4C 41 4E 30 36 33 34 00 08 ._HID.ELAN0634.. 2A0A0: 5F 43 49 44 0D 50 4E 50 30 43 35 30 00 08 5F 55 _CID.PNP0C50.._U 2A0B0: 49 44 01 14 4B 04 5F 44 53 4D 04 A0 3C 93 68 11 ID..K._DSM..<.h. 2A0C0: 13 0A 10 F7 F6 DF 3C 67 42 55 45 AD 05 B3 0A 3D ..https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861610/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1892827] Re: device doesn't boot with kernel older than v5.7.7 on a usb key: hang at efi_tpm_eventlog_init
Verified linux-oem-5.6 version 5.6.0-1028.28 from focal-proposed.
** 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-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1892827
Title:
device doesn't boot with kernel older than v5.7.7 on a usb key: hang
at efi_tpm_eventlog_init
Status in HWE Next:
New
Status in linux package in Ubuntu:
Invalid
Status in linux-oem-5.6 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-oem-5.6 source package in Focal:
Fix Committed
Bug description:
[SRU Justification]
[Impact]
Some systems may hang at boot. With "earlycon=efifb", more debug
messages for EFI are dumpped. Last call trace as:
RIP: 0010:efi_tpm_eventlog_init+0x1aa/0x2a2
...
Call Trace:
efi_config_parse_tables+0x12d/0x213
efi_init+0x218/0x36b
? e820__print_table+0x65/0x6e
setup_arch+458/0xa84
This affects all mainline kernel since v5.2 to v5.7.6. Fix available in
v5.8-rc3 and has been backported to v5.7.7, v5.4.50.
[Fix]
Commit ea3cdcaa43b0 ("efi/tpm: Verify event log header before parsing")
fixes commit 6b0326190205 ("efi: Attempt to get the TCG2 event log in
the boot stub").
[Test Case]
So far it can be easily reproduced with a green installation of Focal on
USB key on a few Dell platforms.
[Regression Potential]
Low. This checks validity of tmp event log header before parsing them,
so it affects only platforms might generate invalid entries only.
[Other Info]
This affects -generic for eoan and oem-5.6 for focal, but the former has
be EOL-ed.
== Original Bug Description ==
[Summary] device doesn't boot with kernel older than v5.7.7 on USB key
[Steps to reproduce]
1. Try to boot a green installation of Ubuntu Focal on a USB key.
[Expected result]
Boot up normally.
[Actual result]
Stuck at "loading initial ramdisk". With "earlycon=efifb", more debug
messages for EFI are dumpped. Last call trace as:
RIP: 0010:efi_tpm_eventlog_init+0x1aa/0x2a2
...
Call Trace:
efi_config_parse_tables+0x12d/0x213
efi_init+0x218/0x36b
? e820__print_table+0x65/0x6e
setup_arch+458/0xa84
[Failure rate]
10/10
[Additional information]
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ea3cdcaa43b08c9a747639f545b0ed5cca47f87e
("efi/tpm: Verify event log header before parsing") fixes in 6b0326190205
("efi: Attempt to get the TCG2 event log in the boot stub").
The fix is in linux-5.7.y and v5.8-rc3, and focal 5.4 and oem-5.6 are
affected.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.8.0-16-generic 5.8.0-16.17
ProcVersionSignature: Ubuntu 5.8.0-16.17-generic 5.8.0
Uname: Linux 5.8.0-16-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.6
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path',
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D2',
'/dev/snd/pcmC0D5p', '/dev/snd/pcmC0D4p', '/dev/snd/pcmC0D3p',
'/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c',
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CasperMD5CheckResult: skip
Date: Tue Aug 25 02:51:58 2020
InstallationDate: Installed on 2020-07-21 (35 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: Dell Inc. Inspiron 3500
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-16-generic
root=UUID=7c53c615-c466-43d7-9ca3-f8b8d895b7b0 ro initcall_debug debug
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-5.8.0-16-generic N/A
linux-backports-modules-5.8.0-16-generic N/A
linux-firmware1.187.2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/05/2020
dmi.bios.release: 0.4
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 0.4.3
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr0.4.3:bd08/05/2020:br0.4:svnDellInc.:pnInspiron3500:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 3500
dmi.product.sku: 0A25
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1892827/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ke
[Kernel-packages] [Bug 1894338] Re: [Samsung Earphones Tuned by AKG] Volume control buttons don't work
I was wondering if this was a kernel bug... ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1894338 Title: [Samsung Earphones Tuned by AKG] Volume control buttons don't work Status in linux package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: My earphones are the one coming with Samsung Galaxy S8 (here: https://www.samsung.com/us/mobile/mobile-accessories/phones/samsung- earphones-tuned-by-akg--gray-eo-ig955bsegus) and on my Ubuntu 18.04 (dual-boot with Windows 10, Secure Boot enabled) Trying to set the volume from my earphones' controls doesn't work, no modification on the volume, the sound bar on Ubuntu doesn't appear in order to indicate volume change. I would like to change the master volume, or whatever my common laptop controls do when I up/down the volume controls on my earphones, like it happens on Windows 10. Why does the erroneous behavior of being unable to set volume from my earphones happen? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.10 ProcVersionSignature: Ubuntu 4.15.0-115.116-generic 4.15.18 Uname: Linux 4.15.0-115-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jason 3523 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Sep 4 23:29:52 2020 InstallationDate: Installed on 2018-09-28 (706 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=el_GR.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/17/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.16.0 dmi.board.name: 02P5YY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.16.0:bd02/17/2020:svnDellInc.:pnInspiron7570:pvr:rvnDellInc.:rn02P5YY:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7570 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894338/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration
Thanks rbalint for pointing me to the other bug for the s390x fail we see now. I'll continue there and consider the Groovy portion of this one closed again. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1892358 Title: autopkgtest success rate dropped inhibiting proposed migration Status in build-essential package in Ubuntu: Invalid Status in glib2.0 package in Ubuntu: Invalid Status in iputils package in Ubuntu: Invalid Status in kbd package in Ubuntu: Invalid Status in linux-meta package in Ubuntu: Invalid Status in ntpsec package in Ubuntu: Invalid Status in qemu package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in util-linux package in Ubuntu: Invalid Status in linux-meta source package in Bionic: New Status in systemd source package in Bionic: New Status in build-essential source package in Focal: Confirmed Status in linux-meta source package in Focal: New Status in qemu source package in Focal: Confirmed Status in systemd source package in Focal: Confirmed Status in util-linux source package in Focal: Confirmed Bug description: Hi, we had such cases in the past like bug 1817721 for bionic and maybe bug 1892130 is about the same as well. There were more but I didn't want to search for all of them - what I checked is that there are no open ones clearly pointing out the recent further drop in already flaky subtests. In particular the tests "tests-in-lxd" and "systemd-fsckd" were known to be flaky before, but got even worse. Here stats of the last 40 runs, it might be a coincidences that this is after 246-2ubuntu1 landed. Could as well be any other change groovy amd64 tests-in-lxd (F 42% S 0% B 10% => P 45%/) BFFFBFF.B.F.F...FBF build-login(F 0% S 0% B 10% => P 87%/) B...B...BB. unit-config(F 0% S 0% B 10% => P 87%/) B...B...BB. networkd-testpy(F 0% S 0% B 10% => P 87%/) B...B...BB. boot-and-services (F 0% S 0% B 10% => P 87%/) B...B...BB. boot-smoke (F 0% S 0% B 10% => P 87%/) B...B...BB. logind (F 0% S 0% B 10% => P 87%/) B...B...BB. storage(F 0% S 0% B 10% => P 87%/) B...B...BB. upstream (F 35% S 0% B 10% => P 52%/) ..FFB.FFF.FFBFF.B.F.F..FFBF udev (F 0% S 0% B 10% => P 87%/) B...B...BB. systemd-fsckd (F 37% S 0% B 10% => P 50%/) BFFFB.FF...FB.F..B. root-unittests (F 0% S 0% B 10% => P 87%/) B...B...BB. ppc64el tests-in-lxd (F 25% S 0% B 0% => P 75%/) FFFFF.F. systemd-fsckd (F 35% S 0% B 0% => P 65%/) FFF...FFFFF.F..F root-unittests (F 2% S 0% B 0% => P 97%/) ..F. s390x tests-in-lxd (F 52% S 0% B 0% => P 47%/) FFF.FFF.FF....F. timedated (F 2% S 0% B 0% => P 97%/) ...F upstream (F 17% S 0% B 0% => P 82%/) .F..F.F.FFF...F. systemd-fsckd (F 32% S 0% B 0% => P 67%/) FFF..FF..F.FF..F root-unittests (F 10% S 0% B 0% => P 90%/) FFF...F. arm64 tests-in-lxd (F 40% S 0% B 2% => P 57%/) F.B...FFF.FF..F..F.FFF.F logind (F 2% S 0% B 2% => P 95%/) ..B...F. upstream (F 22% S 0% B 2% => P 75%/) ...F.FB.F.F.F..FFF.F root-unittests (F 12% S 0% B 2% => P 85%/) ..B.F...F.FF...F (I'm sure LP will make this unreadable, but is is nice in monospace) Whatever the root cause is - the success rate of these has reduced so much that the (even formerly questionable) practice of retry-until- success won't work anymore. I have run the two tests in a local VM and systemd-fsckd works there while tests-in-lxd seems to trip over the old flaky fellow being "boot-and-services". We had the discussion in the past, but I think I need to again bring up the suggestion to skip "tests-in-lxd" and "systemd-fsckd" until they are on reasonable success rates. To manage notifications about this bug go to: https://bugs.laun
[Kernel-packages] [Bug 1893004] Re: [SRU]alsa-ucm-conf: the volume can't be adjusted on the usb audio of the Dell WD15/WD19 dock
I verified the alsa-ucm-conf 1.2.2-1ubuntu0.3 on WD19 Dock station. After applied new UCM configure, the volume of the headset microphone can be adjusted via the input device volume in Settings. ** 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 alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1893004 Title: [SRU]alsa-ucm-conf: the volume can't be adjusted on the usb audio of the Dell WD15/WD19 dock Status in HWE Next: New Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Focal: Fix Committed Status in alsa-ucm-conf source package in Groovy: Fix Released Bug description: [Impact] On the Dell WD15/19 Dock station, there is a USB audio card, and a headset audio jack routes to this audio card. We found if we plug some specific headset (non-iphone type headset), we could not record any sound from headset-mic even we set the input volume to max. [Fix] Improve the ucm for the audio card in this Dock, let the driver mixer value be adjustable, then we could adjust the input volume from driver side. [Test Case] plug various types of headset to the WD19 and WD15 dock stations, and adjust the input volume from gnome, check the input volume in the driver by running amixer, found the input volume is changed in the driver; record the sound from headset-mic, it could record the sound from all headsets we tested. [Regression Risk] It could make the PA fail to load the ucm on the machines with Dell WD15/WD19 dock station, then users only see analogue output/input from gnome-control-center instead of usb-speaks usb-lineout and usb-mic. But this possibility is very low since we have tested the patch on WD15 and WD19 dock, all worked very well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1893004/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1893194] Re: Missing id 8086:a0bc for VMD quirk PCI_DEV_FLAGS_ENABLE_ASPM
Verified linux-oem-5.6 version 5.6.0-1028.28 from focal-proposed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1893194 Title: Missing id 8086:a0bc for VMD quirk PCI_DEV_FLAGS_ENABLE_ASPM Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.6 source package in Focal: Fix Committed Status in linux source package in Groovy: In Progress Status in linux-oem-5.6 source package in Groovy: Invalid Bug description: One VMD equipped platform has another PCI bridge with PCI ID [8086:a0bc] that is not already in Ubuntu sauced PCI_DEV_FLAGS_ENABLE_ASPM list from bug 1889384. Link Capability Register shows ASPM L1 supported, but has ASPM Disabled in Link Control status. 1:e0:1c.4 PCI bridge [0604]: Intel Corporation Device [8086:a0bc] (rev 20) (prog-if 00 [Normal decode]) ... Capabilities: [40] Express (v2) Root Port (Slot+), MSI 00 DevCap: MaxPayload 256 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: CorrErr+ NonFatalErr+ FatalErr+ UnsupReq+ RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 256 bytes, MaxReadReq 128 bytes DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr+ TransPend- LnkCap: Port #5, Speed 8GT/s, Width x4, ASPM L1, Exit Latency L1 <16us ClockPM- Surprise- LLActRep+ BwNot+ ASPMOptComp+ LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- ... 00: 86 80 bc a0 06 04 10 00 20 00 04 06 00 00 81 00 10: 00 00 00 00 00 00 00 00 00 e1 e1 00 f0 00 00 20 20: 00 72 00 72 f1 ff 01 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 40 00 00 00 00 00 00 00 00 01 02 00 40: 10 80 42 01 01 80 00 00 2f 00 10 00 43 48 72 05 ... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.6.0-1023-oem 5.6.0-1023.23 ProcVersionSignature: Ubuntu 5.6.0-1023.23-oem 5.6.19 Uname: Linux 5.6.0-1023-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Aug 27 04:32:44 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa+X31 InstallationDate: Installed on 2020-08-13 (14 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-oem-5.6 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1767 F pulseaudio CasperMD5CheckResult: skip DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa+X31 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-13 (14 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:5520 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 002: ID 27c6:538d Shenzhen Goodix Technology Co.,Ltd. FingerPrint Bus 001 Device 004: ID 0bda:d739 Realtek Semiconductor Corp. 802.11n WLAN Adapter Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Vostro 3400 Package: linux-oem-5.6 (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1023-oem root=UUID=8ef9f2d9-ab46-4c72-824e-9cf5f0dd4001 ro ProcVersionSignature: Ubuntu 5.6.0-1023.23-oem 5.6.19 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.6.0-1023-oem N/A linux-backports-modules-5.6.0-1023-oem N/A linux-firmware 1.187.3 Tags: focal Uname: Linux 5.6.0-1023-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 08/05/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.4.3 dmi.bo
[Kernel-packages] [Bug 1894338] Re: [Samsung Earphones Tuned by AKG] Volume control buttons don't work
This depends on the hardware design first, if the audio jack and the codec supports it or not. Then it depends on the kernel driver. With the ubuntu 20.04, the userspace part is OK to support the headset button, since I already verified it on the Leonvo x1c7. I will build a testing kernel, let us see if it could work or not. thx. ** Changed in: pulseaudio (Ubuntu) Status: New => 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/1894338 Title: [Samsung Earphones Tuned by AKG] Volume control buttons don't work Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Invalid Bug description: My earphones are the one coming with Samsung Galaxy S8 (here: https://www.samsung.com/us/mobile/mobile-accessories/phones/samsung- earphones-tuned-by-akg--gray-eo-ig955bsegus) and on my Ubuntu 18.04 (dual-boot with Windows 10, Secure Boot enabled) Trying to set the volume from my earphones' controls doesn't work, no modification on the volume, the sound bar on Ubuntu doesn't appear in order to indicate volume change. I would like to change the master volume, or whatever my common laptop controls do when I up/down the volume controls on my earphones, like it happens on Windows 10. Why does the erroneous behavior of being unable to set volume from my earphones happen? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.10 ProcVersionSignature: Ubuntu 4.15.0-115.116-generic 4.15.18 Uname: Linux 4.15.0-115-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jason 3523 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Sep 4 23:29:52 2020 InstallationDate: Installed on 2018-09-28 (706 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=el_GR.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/17/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.16.0 dmi.board.name: 02P5YY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.16.0:bd02/17/2020:svnDellInc.:pnInspiron7570:pvr:rvnDellInc.:rn02P5YY:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7570 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894338/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894338] 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 1894338 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/1894338 Title: [Dell Inspiron 7570][Samsung Earphones Tuned by AKG] Volume control buttons don't work Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Invalid Bug description: My earphones are the one coming with Samsung Galaxy S8 (here: https://www.samsung.com/us/mobile/mobile-accessories/phones/samsung- earphones-tuned-by-akg--gray-eo-ig955bsegus) and on my Ubuntu 18.04 (dual-boot with Windows 10, Secure Boot enabled) Trying to set the volume from my earphones' controls doesn't work, no modification on the volume, the sound bar on Ubuntu doesn't appear in order to indicate volume change. I would like to change the master volume, or whatever my common laptop controls do when I up/down the volume controls on my earphones, like it happens on Windows 10. Why does the erroneous behavior of being unable to set volume from my earphones happen? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.10 ProcVersionSignature: Ubuntu 4.15.0-115.116-generic 4.15.18 Uname: Linux 4.15.0-115-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jason 3523 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Sep 4 23:29:52 2020 InstallationDate: Installed on 2018-09-28 (706 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=el_GR.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/17/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.16.0 dmi.board.name: 02P5YY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.16.0:bd02/17/2020:svnDellInc.:pnInspiron7570:pvr:rvnDellInc.:rn02P5YY:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7570 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894338/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894338] Re: [Dell Inspiron 7570][Samsung Earphones Tuned by AKG] Volume control buttons don't work
** Summary changed: - [Samsung Earphones Tuned by AKG] Volume control buttons don't work + [Dell Inspiron 7570][Samsung Earphones Tuned by AKG] Volume control buttons don't work -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1894338 Title: [Dell Inspiron 7570][Samsung Earphones Tuned by AKG] Volume control buttons don't work Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Invalid Bug description: My earphones are the one coming with Samsung Galaxy S8 (here: https://www.samsung.com/us/mobile/mobile-accessories/phones/samsung- earphones-tuned-by-akg--gray-eo-ig955bsegus) and on my Ubuntu 18.04 (dual-boot with Windows 10, Secure Boot enabled) Trying to set the volume from my earphones' controls doesn't work, no modification on the volume, the sound bar on Ubuntu doesn't appear in order to indicate volume change. I would like to change the master volume, or whatever my common laptop controls do when I up/down the volume controls on my earphones, like it happens on Windows 10. Why does the erroneous behavior of being unable to set volume from my earphones happen? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.10 ProcVersionSignature: Ubuntu 4.15.0-115.116-generic 4.15.18 Uname: Linux 4.15.0-115-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jason 3523 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Sep 4 23:29:52 2020 InstallationDate: Installed on 2018-09-28 (706 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=el_GR.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/17/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.16.0 dmi.board.name: 02P5YY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.16.0:bd02/17/2020:svnDellInc.:pnInspiron7570:pvr:rvnDellInc.:rn02P5YY:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7570 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894338/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861610] Re: 'Elan touchpad' not detected on 'Lenovo ThinkBook 15 IIL'
Hi Jakob, thanks for the response. Tried it, got many error messages while trying to disassemble the original acpi table. Intel ACPI Component Architecture ASL+ Optimizing Compiler/Disassembler version 20190509 Copyright (c) 2000 - 2019 Intel Corporation File appears to be binary: found 82451 non-ASCII characters, disassembling Binary file appears to be a valid ACPI table, disassembling Input file dsdt.dat, Length 0x3BB7C (244604) bytes ACPI: DSDT 0x 03BB7C (v02 LENOVO CB-010001 0113) Pass 1 parse of [DSDT] ACPI Error: ^^GFX0.DD1F: Path has too many parent prefixes (^) (20190509/nsaccess-464) ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20190509/psobject-264) ACPI Error: ^^^UBTC.VER1: Path has too many parent prefixes (^) (20190509/nsaccess-464) ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20190509/psobject-264) ACPI Error: ^^^UBTC.VER2: Path has too many parent prefixes (^) (20190509/nsaccess-464) ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20190509/psobject-264) ACPI Error: ^^^UBTC.MGI0: Path has too many parent prefixes (^) (20190509/nsaccess-464) ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20190509/psobject-264) ACPI Error: ^^^UBTC.MGI1: Path has too many parent prefixes (^) (20190509/nsaccess-464) ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20190509/psobject-264) ACPI Error: ^^^UBTC.MGI2: Path has too many parent prefixes (^) (20190509/nsaccess-464) ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20190509/psobject-264) ACPI Error: ^^^UBTC.MGI3: Path has too many parent prefixes (^) (20190509/nsaccess-464) ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20190509/psobject-264) ACPI Error: ^^^UBTC.MGI4: Path has too many parent prefixes (^) (20190509/nsaccess-464) ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20190509/psobject-264) ACPI Error: ^^^UBTC.MGI5: Path has too many parent prefixes (^) (20190509/nsaccess-464) ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20190509/psobject-264) ACPI Error: ^^^UBTC.MGI6: Path has too many parent prefixes (^) (20190509/nsaccess-464) ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20190509/psobject-264) ACPI Error: ^^^UBTC.MGI7: Path has too many parent prefixes (^) (20190509/nsaccess-464) ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20190509/psobject-264) ACPI Error: ^^^UBTC.MGI8: Path has too many parent prefixes (^) (20190509/nsaccess-464) ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20190509/psobject-264) ACPI Error: ^^^UBTC.MGI9: Path has too many parent prefixes (^) (20190509/nsaccess-464) ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20190509/psobject-264) ACPI Error: ^^^UBTC.MGIA: Path has too many parent prefixes (^) (20190509/nsaccess-464) ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20190509/psobject-264) ACPI Error: ^^^UBTC.MGIB: Path has too many parent prefixes (^) (20190509/nsaccess-464) ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20190509/psobject-264) ACPI Error: ^^^UBTC.MGIC: Path has too many parent prefixes (^) (20190509/nsaccess-464) ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20190509/psobject-264) ACPI Error: ^^^UBTC.MGID: Path has too many parent prefixes (^) (20190509/nsaccess-464) ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20190509/psobject-264) ACPI Error: ^^^UBTC.MGIE: Path has too many parent prefixes (^) (20190509/nsaccess-464) ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20190509/psobject-264) ACPI Error: ^^^UBTC.MGIF: Path has too many parent prefixes (^) (20190509/nsaccess-464) ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20190509/psobject-264) ACPI Error: ^^^UBTC.CCI0: Path has too many parent prefixes (^) (20190509/nsaccess-464) ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20190509/psobject-264) ACPI Error: ^^^UBTC.CCI1: Path has too many parent prefixes (^) (20190509/nsaccess-464) ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20190509/psobject-264) ACPI Error: ^^^UBTC.CCI2: Path has too many parent prefixes (^) (20190509/nsaccess-464) ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20190509/psobject-264) ACPI Error: ^^^UBTC.CCI3: Path has too many parent prefixes (^) (20190509/nsaccess-464) ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20190509/psobject-264) ACPI Error: ^^^UBTC.STS0: Path has too many parent prefixes (^) (20190509/nsaccess-464) ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20190509/psobject-264) ACPI Error: ^^^UBTC.STS1: Path has too many parent prefixes (^) (20190509/nsaccess-464) ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20190509/psobject-264) ACPI Error: ^^^UBTC.STS2: Path has too many parent prefixes (^) (20190509/nsaccess-464) ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20190509/psobject-264) ACPI Error: ^^^UBTC.STS3: Path has too many parent prefixes (^) (20190509/nsaccess-464) ACPI Error: AE_NOT_FOUND, During name lookup/
[Kernel-packages] [Bug 1877757] Re: No sound, Dummy output on Acer Swift 3 SF314-57G with Ice Lake core-i7 CPU
Sound works now. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1877757 Title: No sound, Dummy output on Acer Swift 3 SF314-57G with Ice Lake core-i7 CPU Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: Fix Released Status in linux-oem-5.6 source package in Focal: Fix Released Bug description: [Impact] On this machine, after booting up, there is no valid sound card, the gnome-control-center shows a dummy output only. check the dmesg, the alsa sof driver fails to initialize. [Fix] Backport a patch from upstream, after applying this patch, the sof driver will not fail anymore even the codec driver is hda_generic [Test Case] A couple of users already test this patch on their machines, after booting up, there is a valid sound card, and could output sound from output devices. [Regression Risk] Low, this is cherry-picked from upstream, and this just adds a new kind of codec (generic) support, and a couple of ubuntu users already verified this patch. New focal installation on a new Acer Swift 3 laptop with core i7-1065G7. No sound detected, KDE/pavucontrol shows Dummy output. External headset also not detected. I've googled around and tried to reinstall alsa and pulseaudio, tried alsa force-reload as well. Nothing helps. With snd_hda_intel.dmic_detect=0 speakers start working but microphone is not detected. External headset detected with both headphones and mic. I use this as a workaround for a time being. I've checked https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860697 bug. It is closed and use recent kernel and firmware but it does not fix my issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-29-generic 5.4.0-29.33 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sat May 9 18:56:15 2020 InstallationDate: Installed on 2020-04-24 (15 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Acer Swift SF314-57G ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic root=UUID=faf6a132-de60-44fa-a1a7-4cce8ef83b87 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-29-generic N/A linux-backports-modules-5.4.0-29-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/24/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.09 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Floris_IL dmi.board.vendor: IL dmi.board.version: V1.09 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.09:bd09/24/2019:svnAcer:pnSwiftSF314-57G:pvrV1.09:rvnIL:rnFloris_IL:rvrV1.09:cvnAcer:ct10:cvrChassisVersion: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-57G dmi.product.sku: dmi.product.version: V1.09 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877757/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877757] Re: No sound, Dummy output on Acer Swift 3 SF314-57G with Ice Lake core-i7 CPU
Yes, can confirm that sound output and internal microphone work now. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1877757 Title: No sound, Dummy output on Acer Swift 3 SF314-57G with Ice Lake core-i7 CPU Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: Fix Released Status in linux-oem-5.6 source package in Focal: Fix Released Bug description: [Impact] On this machine, after booting up, there is no valid sound card, the gnome-control-center shows a dummy output only. check the dmesg, the alsa sof driver fails to initialize. [Fix] Backport a patch from upstream, after applying this patch, the sof driver will not fail anymore even the codec driver is hda_generic [Test Case] A couple of users already test this patch on their machines, after booting up, there is a valid sound card, and could output sound from output devices. [Regression Risk] Low, this is cherry-picked from upstream, and this just adds a new kind of codec (generic) support, and a couple of ubuntu users already verified this patch. New focal installation on a new Acer Swift 3 laptop with core i7-1065G7. No sound detected, KDE/pavucontrol shows Dummy output. External headset also not detected. I've googled around and tried to reinstall alsa and pulseaudio, tried alsa force-reload as well. Nothing helps. With snd_hda_intel.dmic_detect=0 speakers start working but microphone is not detected. External headset detected with both headphones and mic. I use this as a workaround for a time being. I've checked https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860697 bug. It is closed and use recent kernel and firmware but it does not fix my issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-29-generic 5.4.0-29.33 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sat May 9 18:56:15 2020 InstallationDate: Installed on 2020-04-24 (15 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Acer Swift SF314-57G ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic root=UUID=faf6a132-de60-44fa-a1a7-4cce8ef83b87 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-29-generic N/A linux-backports-modules-5.4.0-29-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/24/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.09 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Floris_IL dmi.board.vendor: IL dmi.board.version: V1.09 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.09:bd09/24/2019:svnAcer:pnSwiftSF314-57G:pvrV1.09:rvnIL:rnFloris_IL:rvrV1.09:cvnAcer:ct10:cvrChassisVersion: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-57G dmi.product.sku: dmi.product.version: V1.09 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877757/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851273] Re: monitor continuously goes on/off when energy saver is active
** Changed in: linux (Ubuntu) Assignee: Kai-Heng Feng (kaihengfeng) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851273 Title: monitor continuously goes on/off when energy saver is active Status in linux package in Ubuntu: Confirmed Bug description: Hi, When monitor should power off (because of power saver timeout), he continuously wake on/off: - screen became black - monitor power off as no signal - after a second he wake on again - repeat I know that could be hard to imagine the situation, so i attached a video. I assume that software/hardware info are already included (as i used ubuntu-bug), but if not tell me. Thanks for all your work :) PS sorry if bug report is wrong (that's the first time) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-19-generic 5.3.0-19.20 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marco 962 F pulseaudio /dev/snd/controlC2: marco 962 F pulseaudio /dev/snd/controlC1: marco 962 F pulseaudio CurrentDesktop: KDE Date: Mon Nov 4 19:12:28 2019 InstallationDate: Installed on 2019-11-03 (0 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: eno1 no wireless extensions. lono wireless extensions. MachineType: Packard Bell imedia S3840 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=f81de2b9-ff5a-4f92-af94-ac09f37653f4 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-19-generic N/A linux-backports-modules-5.3.0-19-generic N/A linux-firmware1.183.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/08/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P01-B1 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: imedia S3840 dmi.board.vendor: Packard Bell dmi.chassis.type: 3 dmi.chassis.vendor: Packard Bell dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP01-B1:bd07/08/2011:svnPackardBell:pnimediaS3840:pvrP01-B1:rvnPackardBell:rnimediaS3840:rvr:cvnPackardBell:ct3:cvr: dmi.product.family: Packard Bell Desktop dmi.product.name: imedia S3840 dmi.product.sku: To be filled by O.E.M. dmi.product.version: P01-B1 dmi.sys.vendor: Packard Bell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851273/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1892816] Re: [Potential Regression] memory-hotplug test from ubuntu_kernel_selftests failed on X-4.15 / B-4.15 / F-5.4 ARM64
** Tags added: sru-20200831 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1892816 Title: [Potential Regression] memory-hotplug test from ubuntu_kernel_selftests failed on X-4.15 / B-4.15 / F-5.4 ARM64 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: Issue found on 4.15.0-114.115~16.04.1, test failed with: ./mem-on-off-test.sh -r 2 && echo "selftests: memory-hotplug [PASS]" || echo "selftests: memory-hotplug [FAIL]" /bin/sh: 1: ./mem-on-off-test.sh: Permission denied selftests: memory-hotplug [FAIL] Note that this test was marked as passed (test skipped) with 4.15.0-112.113~16.04.1 on both ThunderX and Moonshot node: skip all tests: memory hotplug is not supported selftests: memory-hotplug [PASS] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1892816/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895634] [NEW] Groovy update: v5.8.9 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.8.9 upstream stable release from git://git.kernel.org/ Linux 5.8.9 mptcp: free acked data before waiting for more memory net: disable netpoll on fresh napis tipc: fix using smp_processor_id() in preemptible tipc: fix shutdown() of connectionless socket taprio: Fix using wrong queues in gate mask sctp: not disable bh in the whole sctp_get_port_local() net: usb: dm9601: Add USB ID of Keenetic Plus DSL netlabel: fix problems with mapping removal ipv6: Fix sysctl max for fib_multipath_hash_policy ipv4: Silence suspicious RCU usage warning RDMA/cma: Execute rdma_cm destruction from a handler properly RDMA/cma: Remove unneeded locking for req paths RDMA/cma: Using the standard locking pattern when delivering the removal event RDMA/cma: Simplify DEVICE_REMOVAL for internal_id io_uring: fix linked deferred ->files cancellation io_uring: fix cancel of deferred reqs with ->files ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Groovy) Importance: Undecided Status: Confirmed ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Groovy) Importance: Undecided Status: 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/1895634 Title: Groovy update: v5.8.9 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Groovy: Confirmed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.8.9 upstream stable release from git://git.kernel.org/ Linux 5.8.9 mptcp: free acked data before waiting for more memory net: disable netpoll on fresh napis tipc: fix using smp_processor_id() in preemptible tipc: fix shutdown() of connectionless socket taprio: Fix using wrong queues in gate mask sctp: not disable bh in the whole sctp_get_port_local() net: usb: dm9601: Add USB ID of Keenetic Plus DSL netlabel: fix problems with mapping removal ipv6: Fix sysctl max for fib_multipath_hash_policy ipv4: Silence suspicious RCU usage warning RDMA/cma: Execute rdma_cm destruction from a handler properly RDMA/cma: Remove unneeded locking for req paths RDMA/cma: Using the standard locking pattern when delivering the removal event RDMA/cma: Simplify DEVICE_REMOVAL for internal_id io_uring: fix linked deferred ->files cancellation io_uring: fix cancel of deferred reqs with ->files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895634/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894338] Re: [Dell Inspiron 7570][Samsung Earphones Tuned by AKG] Volume control buttons don't work
Would it be helpful if I collected the above requested kernel info too for my current kernel, or is it contingent on the above mentioned testing kernel? (an if yes, how would I apply that to a live CD, since I don't want to interfere with my existing Ubuntu installation with installing a testing kernel) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1894338 Title: [Dell Inspiron 7570][Samsung Earphones Tuned by AKG] Volume control buttons don't work Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Invalid Bug description: My earphones are the one coming with Samsung Galaxy S8 (here: https://www.samsung.com/us/mobile/mobile-accessories/phones/samsung- earphones-tuned-by-akg--gray-eo-ig955bsegus) and on my Ubuntu 18.04 (dual-boot with Windows 10, Secure Boot enabled) Trying to set the volume from my earphones' controls doesn't work, no modification on the volume, the sound bar on Ubuntu doesn't appear in order to indicate volume change. I would like to change the master volume, or whatever my common laptop controls do when I up/down the volume controls on my earphones, like it happens on Windows 10. Why does the erroneous behavior of being unable to set volume from my earphones happen? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.10 ProcVersionSignature: Ubuntu 4.15.0-115.116-generic 4.15.18 Uname: Linux 4.15.0-115-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jason 3523 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Sep 4 23:29:52 2020 InstallationDate: Installed on 2018-09-28 (706 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=el_GR.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/17/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.16.0 dmi.board.name: 02P5YY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.16.0:bd02/17/2020:svnDellInc.:pnInspiron7570:pvr:rvnDellInc.:rn02P5YY:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7570 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894338/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1889384] Re: ASPM not enabled on child devices behind VMD controller
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1889384 Title: ASPM not enabled on child devices behind VMD controller Status in HWE Next: Fix Released Status in OEM Priority Project: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.6 source package in Focal: Fix Released Status in linux source package in Groovy: Fix Released Status in linux-oem-5.6 source package in Groovy: Invalid Bug description: ASPM of VMD devices is not automatically enabled even it's said capable in its Link Capabilities Register. $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)' 1:e0:1d.0 0604: 8086:a0b0 (rev 20) (prog-if 00 [Normal decode]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ 1:e1:00.0 0108: 1e0f:0001 (prog-if 02 [NVM Express]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1831 F pulseaudio CasperMD5CheckResult: skip DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-samwell-tgl+X38 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-07-29 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. Vostro 5301 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1020-oem root=UUID=f50abb19-ab3a-4f05-bf1a-b0504bd11a7b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1020.20-oem 5.6.19 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.6.0-1020-oem N/A linux-backports-modules-5.6.0-1020-oem N/A linux-firmware 1.187.2 Tags: focal Uname: Linux 5.6.0-1020-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 07/21/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.5.4 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.5.4:bd07/21/2020:svnDellInc.:pnVostro5301:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 5301 dmi.product.sku: 09FC dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1889384/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894860] Re: Boot fails with newer kernel
I can gladly post more config or log files, just need to know which of them -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1894860 Title: Boot fails with newer kernel Status in linux package in Ubuntu: Incomplete Bug description: I get a "cryptsetup: Waiting for encrypted source device UUID=" message when trying to boot with kernels 5.4.0-47 and 5.4.0.-45 and then nothing happens pressing ESC displays "Volume group "vgubuntu" not found Cannot process volume group vgubuntu" System was dm-crypt/LUKS encrypted at installation kernel 5.4.0-42 still works ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Tue Sep 8 16:41:34 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed only-ubiquity quiet splash nomodeset --- InstallationDate: Installed on 2019-10-18 (326 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity Symptom: installation UpgradeStatus: Upgraded to focal on 2020-04-27 (134 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894860/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895640] [NEW] BlueZ 5.55 release
Public bug reported: https://mirrors.edge.kernel.org/pub/linux/bluetooth/bluez-5.55.tar.xz https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/?h=5.55 ** Affects: bluez (Ubuntu) Importance: Undecided Assignee: Daniel van Vugt (vanvugt) Status: In Progress ** Tags: groovy ** Description changed: https://mirrors.edge.kernel.org/pub/linux/bluetooth/bluez-5.55.tar.xz + + https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/?h=5.55 ** Changed in: bluez (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: bluez (Ubuntu) Status: New => In Progress -- 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/1895640 Title: BlueZ 5.55 release Status in bluez package in Ubuntu: In Progress Bug description: https://mirrors.edge.kernel.org/pub/linux/bluetooth/bluez-5.55.tar.xz https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/?h=5.55 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1895640/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895648] [NEW] touchpad is not detected
Public bug reported: I have just bought a Lenovo ideapad3. My touchpad is detected by Windows but it does not work with Ubuntu 20. It is not even listed in devices files that I attach. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-47-generic 5.4.0-47.51 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mercedes 1311 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Sep 15 11:24:51 2020 InstallationDate: Installed on 2020-09-14 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 81WE ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic root=UUID=549f183f-a14e-4d2a-83bd-0bf81e0af135 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-47-generic N/A linux-backports-modules-5.4.0-47-generic N/A linux-firmware1.187.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EMCN14WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 3 15IIL05 dmi.modalias: dmi:bvnLENOVO:bvrEMCN14WW:bd05/11/2020:svnLENOVO:pn81WE:pvrIdeaPad315IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrIdeaPad315IIL05: dmi.product.family: IdeaPad 3 15IIL05 dmi.product.name: 81WE dmi.product.sku: LENOVO_MT_81WE_BU_idea_FM_IdeaPad 3 15IIL05 dmi.product.version: IdeaPad 3 15IIL05 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "devices list" https://bugs.launchpad.net/bugs/1895648/+attachment/5410958/+files/devices -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1895648 Title: touchpad is not detected Status in linux package in Ubuntu: New Bug description: I have just bought a Lenovo ideapad3. My touchpad is detected by Windows but it does not work with Ubuntu 20. It is not even listed in devices files that I attach. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-47-generic 5.4.0-47.51 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mercedes 1311 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Sep 15 11:24:51 2020 InstallationDate: Installed on 2020-09-14 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 81WE ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic root=UUID=549f183f-a14e-4d2a-83bd-0bf81e0af135 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-47-generic N/A linux-backports-modules-5.4.0-47-generic N/A linux-firmware1.187.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EMCN14WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 3 15IIL05 dmi.modalias: dmi:bvnLENOVO:bvrEMCN14WW:bd05/11/2020:svnLENOVO:pn81WE:pvrIdeaPad315IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrIdeaPad315IIL05: dmi.product.family: IdeaPad 3 15IIL05 dmi.product.name: 81WE dmi.product.sku: LENOVO_MT_81WE_BU_idea_FM_IdeaPad 3 15IIL05 dmi.product.version: IdeaPad 3 15IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895648/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894338] Re: [Dell Inspiron 7570][Samsung Earphones Tuned by AKG] Volume control buttons don't work
Please test this kernel: https://people.canonical.com/~hwang4/hstbtn/ to install the testing kernel: sudo dpkg -i linux-image-xxx.deb reboot and run sudo evtest, then upload the output log of 'sudo evtest' to uninstall the testing kernel: sudo dpkg -r linux-image- (5.9-rc3) reboot -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1894338 Title: [Dell Inspiron 7570][Samsung Earphones Tuned by AKG] Volume control buttons don't work Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Invalid Bug description: My earphones are the one coming with Samsung Galaxy S8 (here: https://www.samsung.com/us/mobile/mobile-accessories/phones/samsung- earphones-tuned-by-akg--gray-eo-ig955bsegus) and on my Ubuntu 18.04 (dual-boot with Windows 10, Secure Boot enabled) Trying to set the volume from my earphones' controls doesn't work, no modification on the volume, the sound bar on Ubuntu doesn't appear in order to indicate volume change. I would like to change the master volume, or whatever my common laptop controls do when I up/down the volume controls on my earphones, like it happens on Windows 10. Why does the erroneous behavior of being unable to set volume from my earphones happen? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.10 ProcVersionSignature: Ubuntu 4.15.0-115.116-generic 4.15.18 Uname: Linux 4.15.0-115-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jason 3523 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Sep 4 23:29:52 2020 InstallationDate: Installed on 2018-09-28 (706 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=el_GR.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/17/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.16.0 dmi.board.name: 02P5YY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.16.0:bd02/17/2020:svnDellInc.:pnInspiron7570:pvr:rvnDellInc.:rn02P5YY:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7570 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894338/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895648] 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/1895648 Title: touchpad is not detected Status in linux package in Ubuntu: Confirmed Bug description: I have just bought a Lenovo ideapad3. My touchpad is detected by Windows but it does not work with Ubuntu 20. It is not even listed in devices files that I attach. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-47-generic 5.4.0-47.51 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mercedes 1311 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Sep 15 11:24:51 2020 InstallationDate: Installed on 2020-09-14 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 81WE ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic root=UUID=549f183f-a14e-4d2a-83bd-0bf81e0af135 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-47-generic N/A linux-backports-modules-5.4.0-47-generic N/A linux-firmware1.187.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EMCN14WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 3 15IIL05 dmi.modalias: dmi:bvnLENOVO:bvrEMCN14WW:bd05/11/2020:svnLENOVO:pn81WE:pvrIdeaPad315IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrIdeaPad315IIL05: dmi.product.family: IdeaPad 3 15IIL05 dmi.product.name: 81WE dmi.product.sku: LENOVO_MT_81WE_BU_idea_FM_IdeaPad 3 15IIL05 dmi.product.version: IdeaPad 3 15IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895648/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894378] Re: Cannot boot after updating kernel to version 5.4.0-45
@Achille ``` $ sudo lspci | grep Motion 6d:00.0 Non-Volatile memory controller: Silicon Motion, Inc. Device 2263 (rev 03) ``` according to `sudo nvme list` output, it is /dev/nvme0n1 Model TS256GMTE110S If I understood correctly, next update will fix the issue (?) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1894378 Title: Cannot boot after updating kernel to version 5.4.0-45 Status in linux package in Ubuntu: Confirmed Bug description: After the kernel update from version 5.4.0-42 to version 5.4.0-45 a few days ago, the boot process is ending in a BusyBox shell. Apparently it cannot properly identify my M.2 NMVe SSD device where my root partition is. Indeed, it is not listed in /dev (precisely: nvme0 is listed in /dev, but nvme0n1 and its partitions are not). For now, I'm solving this problem by booting the previous kernel, 5.4.0-42. This works fine. Also, an earlier attempt ended in a different shell that presented the error message "Gave up on waiting for root file system device". The UUID it indicated as missing is the correct UUID of my root partition, which also appears on /etc/fstab. I tried to re-build initrd.img-5.4.0-45-generic, but to no avail. Let me also mention that in another computer with a non-M.2 SSD, kernel 5.4.0-45 boots properly. This bug seems to be the one mentioned in the following "Unix & Linux" forum question: https://unix.stackexchange.com/questions/607694/ubuntu-20-04-01-not-booting-after-kernel-update Many thanks in advance! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ami3801 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sat Sep 5 17:42:26 2020 HibernationDevice: RESUME=UUID=dd70dd06-717a-4acf-a85e-a9ad37cb92ea InstallationDate: Installed on 2017-10-04 (1066 days ago) InstallationMedia: Kubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IwConfig: enp0s31f6 no wireless extensions. lono wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 1532:022a Razer USA, Ltd Razer Cynosa Chroma Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 480M |__ Port 8: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 8: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 8: Dev 2, If 2, Class=Human Interface Device, Driver=usbhid, 12M MachineType: System manufacturer System Product Name ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic root=UUID=85262f0d-cb92-475a-8174-2d6316e199a9 ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.3 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-05-03 (125 days ago) dmi.bios.date: 06/20/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3807 dmi.board.asset.tag: Default string dmi.board.name: H110M-A/M.2 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3807:bd06/20/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-A/M.2:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894378/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895640] Re: BlueZ 5.55 release
** Attachment added: "bluez_5.55.orig.tar.xz" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1895640/+attachment/5410977/+files/bluez_5.55.orig.tar.xz -- 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/1895640 Title: BlueZ 5.55 release Status in bluez package in Ubuntu: In Progress Bug description: https://mirrors.edge.kernel.org/pub/linux/bluetooth/bluez-5.55.tar.xz https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/?h=5.55 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1895640/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895640] Re: BlueZ 5.55 release
** Attachment added: "bluez_5.55-0ubuntu1.debian.tar.xz" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1895640/+attachment/5410978/+files/bluez_5.55-0ubuntu1.debian.tar.xz -- 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/1895640 Title: BlueZ 5.55 release Status in bluez package in Ubuntu: In Progress Bug description: https://mirrors.edge.kernel.org/pub/linux/bluetooth/bluez-5.55.tar.xz https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/?h=5.55 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1895640/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894733] Re: Most fn keys don't work on Puget laptop running 20.10
The brightness was corrected at the same time as the fix release for the multimedia keys. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1894733 Title: Most fn keys don't work on Puget laptop running 20.10 Status in linux package in Ubuntu: Fix Released Bug description: The volume up/down (fn-f5 and fn-f6) and enable bluetooth (fn-f12) do not work. Tried both kernels available (5.4 and 5.8) with the same results. The only fn keys that appear to work are brightness (fn-f8 and fn-9) and airplane mode (fn-f11) The problem does not occur in 20.04 (kernel 5.4) on the same laptop, all function keys work. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-18-generic 5.8.0-18.19 ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 Uname: Linux 5.8.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: cliff 1445 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Mon Sep 7 11:23:56 2020 InstallationDate: Installed on 2020-08-28 (9 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200826) MachineType: CLEVO CO. W35_37ET ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic root=UUID=292706c2-98fe-4370-a52f-7e67774018c7 ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.8.0-18-generic N/A linux-backports-modules-5.8.0-18-generic N/A linux-firmware1.190 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/14/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: W35_37ET dmi.board.vendor: CLEVO CO. dmi.board.version: N/A dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 9 dmi.chassis.vendor: CLEVO CO. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/14/2012:br4.6:svnCLEVOCO.:pnW35_37ET:pvrN/A:rvnCLEVOCO.:rnW35_37ET:rvrN/A:cvnCLEVOCO.:ct9:cvrN/A: dmi.product.family: To be filled by O.E.M. dmi.product.name: W35_37ET dmi.product.sku: To be filled by O.E.M. dmi.product.version: N/A dmi.sys.vendor: CLEVO CO. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: cliff 1445 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2020-08-28 (9 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200826) MachineType: CLEVO CO. W35_37ET NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic root=UUID=292706c2-98fe-4370-a52f-7e67774018c7 ro quiet splash ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 RelatedPackageVersions: linux-restricted-modules-5.8.0-18-generic N/A linux-backports-modules-5.8.0-18-generic N/A linux-firmware1.190 Tags: groovy Uname: Linux 5.8.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: 12/14/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: W35_37ET dmi.board.vendor: CLEVO CO. dmi.board.version: N/A dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 9 dmi.chassis.vendor: CLEVO CO. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/14/2012:br4.6:svnCLEVOCO.:pnW35_37ET:pvrN/A:rvnCLEVOCO.:rnW35_37ET:rvrN/A:cvnCLEVOCO.:ct9:cvrN/A: dmi.product.family: To be filled by O.E.M. dmi.product.name: W35_37ET dmi.product.sku: To be filled by O.E.M. dmi.product.version: N/A dmi.sys.vendor: CLEVO CO. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894733/+subscriptions -- Mailing list: http
[Kernel-packages] [Bug 1853277] Re: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices
Sorry, I mean, changes described here https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861610/comments/66 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853277 Title: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices Status in linux package in Ubuntu: Confirmed Bug description: This is happening on a ThinkBook 14 IML 20RV. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1848 F pulseaudio CasperVersion: 1.427 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 20 11:10:52 2019 LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20RV ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed quiet splash --- RelatedPackageVersions: linux-restricted-modules-5.3.0-18-generic N/A linux-backports-modules-5.3.0-18-generic N/A linux-firmware1.183 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/10/2019 dmi.bios.vendor: LENOVO dmi.bios.version: CJCN21WW dmi.board.name: LVA/LVAB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.modalias: dmi:bvnLENOVO:bvrCJCN21WW:bd10/10/2019:svnLENOVO:pn20RV:pvrLenovoThinkBook14-IML:rvnLENOVO:rnLVA/LVAB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvr: dmi.product.family: ThinkBook 14-IML dmi.product.name: 20RV dmi.product.sku: LENOVO_MT_20RV_BU_idea_FM_ThinkBook 14-IML dmi.product.version: Lenovo ThinkBook 14-IML dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853277] Re: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices
Hi Kai, I am reporting that this kernel https://people.canonical.com/~khfeng/lp1853277-final/ works for me, thank you! However, I needed to un-blacklist i2c_hid for touchpad to work, therefore I had to undo the changes described here https://people.canonical.com/~khfeng/lp1853277-final/ 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/1853277 Title: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices Status in linux package in Ubuntu: Confirmed Bug description: This is happening on a ThinkBook 14 IML 20RV. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1848 F pulseaudio CasperVersion: 1.427 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 20 11:10:52 2019 LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20RV ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed quiet splash --- RelatedPackageVersions: linux-restricted-modules-5.3.0-18-generic N/A linux-backports-modules-5.3.0-18-generic N/A linux-firmware1.183 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/10/2019 dmi.bios.vendor: LENOVO dmi.bios.version: CJCN21WW dmi.board.name: LVA/LVAB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.modalias: dmi:bvnLENOVO:bvrCJCN21WW:bd10/10/2019:svnLENOVO:pn20RV:pvrLenovoThinkBook14-IML:rvnLENOVO:rnLVA/LVAB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvr: dmi.product.family: ThinkBook 14-IML dmi.product.name: 20RV dmi.product.sku: LENOVO_MT_20RV_BU_idea_FM_ThinkBook 14-IML dmi.product.version: Lenovo ThinkBook 14-IML dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849713] Re: Warning message in logs after kernel update to linux-image-4.15.0-66-generic
I have the same error at every boot. LSB Version: core-9.20170808ubuntu1-noarch:printing-9.20170808ubuntu1-noarch:security-9.20170808ubuntu1-noarch Distributor ID: elementary Description:elementary OS 5.1.7 Hera Release:5.1.7 Codename: hera 4.15.0-117-generic [1.427943] [ cut here ] [1.427944] Could not determine valid watermarks for inherited state [1.427985] WARNING: CPU: 5 PID: 210 at /build/linux-do9eLF/linux-4.15.0/drivers/gpu/drm/i915/intel_display.c:14537 intel_modeset_init+0xfcf/0x1010 [i915] [1.427986] Modules linked in: i915(+) rtsx_pci_sdmmc i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm psmouse ahci libahci rtsx_pci video [1.427991] CPU: 5 PID: 210 Comm: systemd-udevd Not tainted 4.15.0-117-generic #118-Ubuntu [1.427991] Hardware name: Hewlett-Packard HP OMEN Notebook PC 15/2332, BIOS F.48 11/14/2019 [1.428016] RIP: 0010:intel_modeset_init+0xfcf/0x1010 [i915] [1.428017] RSP: 0018:ab8581fa39b0 EFLAGS: 00010286 [1.428018] RAX: RBX: 8c0bc0b88000 RCX: bd263aa8 [1.428018] RDX: 0001 RSI: 0096 RDI: 0247 [1.428019] RBP: ab8581fa3a40 R08: 0290 R09: 0004 [1.428019] R10: 0040 R11: 0001 R12: 8c0bc1437800 [1.428020] R13: 8c0bcc58cc00 R14: ffea R15: 8c0bc0b88358 [1.428021] FS: 7fb39ba8b680() GS:8c0bdf34() knlGS: [1.428021] CS: 0010 DS: ES: CR0: 80050033 [1.428022] CR2: 7fb39ba76ebd CR3: 0004408d0006 CR4: 001606e0 [1.428023] Call Trace: [1.428053] i915_driver_load+0xa73/0xe60 [i915] [1.428071] i915_pci_probe+0x42/0x70 [i915] [1.428073] local_pci_probe+0x47/0xa0 [1.428084] pci_device_probe+0x10e/0x1c0 [1.428087] driver_probe_device+0x30c/0x4a0 [1.428088] __driver_attach+0xcc/0xf0 [1.428090] ? driver_probe_device+0x4a0/0x4a0 [1.428092] bus_for_each_dev+0x70/0xc0 [1.428093] driver_attach+0x1e/0x20 [1.428095] bus_add_driver+0x1c7/0x270 [1.428095] ? 0xc04bb000 [1.428097] driver_register+0x60/0xe0 [1.428097] ? 0xc04bb000 [1.428098] __pci_register_driver+0x5a/0x60 [1.428120] i915_init+0x5c/0x5f [i915] [1.428122] do_one_initcall+0x52/0x19f [1.428124] ? __vunmap+0xb5/0xe0 [1.428126] ? _cond_resched+0x19/0x40 [1.428127] ? kmem_cache_alloc_trace+0x167/0x1d0 [1.428130] ? do_init_module+0x27/0x213 [1.428131] do_init_module+0x5f/0x213 [1.428133] load_module+0x16bd/0x1f20 [1.428135] ? ima_post_read_file+0x96/0xa0 [1.428137] SYSC_finit_module+0xfc/0x120 [1.428138] ? SYSC_finit_module+0xfc/0x120 [1.428140] SyS_finit_module+0xe/0x10 [1.428141] do_syscall_64+0x73/0x130 [1.428142] entry_SYSCALL_64_after_hwframe+0x41/0xa6 [1.428143] RIP: 0033:0x7fb39b595959 [1.428144] RSP: 002b:7ffd062d28d8 EFLAGS: 0246 ORIG_RAX: 0139 [1.428144] RAX: ffda RBX: 55a1e3ca5300 RCX: 7fb39b595959 [1.428145] RDX: RSI: 7fb39b274105 RDI: 0012 [1.428145] RBP: 7fb39b274105 R08: R09: 7ffd062d29f0 [1.428146] R10: 0012 R11: 0246 R12: [1.428146] R13: 55a1e3ca9340 R14: 0002 R15: 55a1e3ca5300 [1.428147] Code: e9 46 fc ff ff 48 c7 c6 f7 9d 44 c0 48 c7 c7 4f 91 44 c0 e8 64 27 ad fb 0f 0b e9 73 fe ff ff 48 c7 c7 40 f6 45 c0 e8 51 27 ad fb <0f> 0b e9 4b fe ff ff 48 c7 c6 04 9e 44 c0 48 c7 c7 4f 91 44 c0 [1.428156] ---[ end trace fbf359e6d3d7d879 ]--- -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1849713 Title: Warning message in logs after kernel update to linux- image-4.15.0-66-generic Status in linux package in Ubuntu: Confirmed Bug description: Hi: After updating to latest kernel on ubuntu 18.04 I start getting the message below. I tried to reboot the machine but the message is consistent. [1.485680] [ cut here ] [1.485681] Could not determine valid watermarks for inherited state [1.485736] WARNING: CPU: 0 PID: 199 at /build/linux-WKYm23/linux-4.15.0/drivers/gpu/drm/i915/intel_display.c:14537 intel_modeset_init+0xfcf/0x1010 [i915] [1.485737] Modules linked in: aesni_intel(+) fjes(-) nouveau(+) aes_x86_64 i915(+) crypto_simd glue_helper cryptd mxm_wmi ttm i2c_algo_bit psmouse drm_kms_helper ahci syscopyarea sysfillrect sysimgblt libahci r8169 fb_sys_fops mii drm rtsx_pci wmi video [1.485748] CPU: 0 PID: 199 Comm: systemd-udevd Not tainted 4.15.0-66-generic #75-Ubuntu [1.485749] Hardware name: ASUSTeK COMPUTER INC. G551JW/G551JW, BIOS G551JW.209 03/04/2016 [
[Kernel-packages] [Bug 1861610] Re: 'Elan touchpad' not detected on 'Lenovo ThinkBook 15 IIL'
Hello all, Just wanted to let you know that the touchpad works on my 20SL0022 with the kernel https://people.canonical.com/~khfeng/lp1853277-final/ and unblacklisting i2c_hid (undoing changes made in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861610/comments/66). My OS is Ubuntu 20.04. A bit more info on this kernel can be found here https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853277 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1861610 Title: 'Elan touchpad' not detected on 'Lenovo ThinkBook 15 IIL' Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.6 package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Released Status in linux-oem-5.6 source package in Bionic: Invalid Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Eoan: Fix Released Status in linux-oem-5.6 source package in Eoan: Invalid Status in linux-oem-osp1 source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Status in linux-oem-5.6 source package in Focal: Fix Released Status in linux-oem-osp1 source package in Focal: Invalid Bug description: [SRU Justification] [Impact] Touchpad function unavailable on some platforms with new ELAN touchpad HIDs. [Fix] https://lore.kernel.org/linux-input/000201d5a8bd$9fead3f0$dfc07bd0$@emc.com.tw/ required to match these currently unsupported IDs. [Test Case] 1. check if platform is affected, e.g. with ELAN0634: $ sudo acpidump | grep -C3 ELAN 2A060: 49 4E 54 31 70 0A 20 49 44 41 44 A4 84 53 42 46 INT1p.IDAD..SBF 2A070: 53 53 42 46 49 00 5B 82 42 0E 54 50 44 32 08 5F SSBFI.[.B.TPD2._ 2A080: 41 44 52 00 08 49 44 41 44 00 08 48 49 44 32 00 ADR..IDAD..HID2. 2A090: 08 5F 48 49 44 0D 45 4C 41 4E 30 36 33 34 00 08 ._HID.ELAN0634.. 2A0A0: 5F 43 49 44 0D 50 4E 50 30 43 35 30 00 08 5F 55 _CID.PNP0C50.._U 2A0B0: 49 44 01 14 4B 04 5F 44 53 4D 04 A0 3C 93 68 11 ID..K._DSM..<.h. 2A0C0: 13 0A 10 F7 F6 DF 3C 67 42 55 45 AD 05 B3 0A 3D ..https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861610/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
I think this is duplicate with #1840725. for me the use of a headset allow me to une the microphone. -- You 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 1894860] Re: Boot fails with newer kernel
Eugen, normally the kernel bot posts the following text but it hasn't done so as the bug report has a status of 'Incomplete' and was initially filed against the installer rather than the kernel: --- 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 1894860 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'. --- Make sure you update the status even if you can't run the 'apport- collect' command. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1894860 Title: Boot fails with newer kernel Status in linux package in Ubuntu: Incomplete Bug description: I get a "cryptsetup: Waiting for encrypted source device UUID=" message when trying to boot with kernels 5.4.0-47 and 5.4.0.-45 and then nothing happens pressing ESC displays "Volume group "vgubuntu" not found Cannot process volume group vgubuntu" System was dm-crypt/LUKS encrypted at installation kernel 5.4.0-42 still works ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Tue Sep 8 16:41:34 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed only-ubiquity quiet splash nomodeset --- InstallationDate: Installed on 2019-10-18 (326 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity Symptom: installation UpgradeStatus: Upgraded to focal on 2020-04-27 (134 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894860/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894860] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1894860/+attachment/5410995/+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/1894860 Title: Boot fails with newer kernel Status in linux package in Ubuntu: Confirmed Bug description: I get a "cryptsetup: Waiting for encrypted source device UUID=" message when trying to boot with kernels 5.4.0-47 and 5.4.0.-45 and then nothing happens pressing ESC displays "Volume group "vgubuntu" not found Cannot process volume group vgubuntu" System was dm-crypt/LUKS encrypted at installation kernel 5.4.0-42 still works ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Tue Sep 8 16:41:34 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed only-ubiquity quiet splash nomodeset --- InstallationDate: Installed on 2019-10-18 (326 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity Symptom: installation UpgradeStatus: Upgraded to focal on 2020-04-27 (134 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eugen 1907 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-10-18 (332 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20Q7001CGE Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic root=/dev/mapper/vgubuntu-root ro quiet splash pcie_aspm=off ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.3 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-27 (141 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 03/24/2020 dmi.bios.vendor: LENOVO dmi.bios.version: R0ZET40W (1.18 ) dmi.board.asset.tag: Not Available dmi.board.name: 20Q7001CGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0ZET40W(1.18):bd03/24/2020:svnLENOVO:pn20Q7001CGE:pvrThinkPadL590:rvnLENOVO:rn20Q7001CGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L590 dmi.product.name: 20Q7001CGE dmi.product.sku: LENOVO_MT_20Q7_BU_SMB_FM_ThinkPad L590 dmi.product.version: ThinkPad L590 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894860/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894860] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1894860/+attachment/5410996/+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/1894860 Title: Boot fails with newer kernel Status in linux package in Ubuntu: Confirmed Bug description: I get a "cryptsetup: Waiting for encrypted source device UUID=" message when trying to boot with kernels 5.4.0-47 and 5.4.0.-45 and then nothing happens pressing ESC displays "Volume group "vgubuntu" not found Cannot process volume group vgubuntu" System was dm-crypt/LUKS encrypted at installation kernel 5.4.0-42 still works ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Tue Sep 8 16:41:34 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed only-ubiquity quiet splash nomodeset --- InstallationDate: Installed on 2019-10-18 (326 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity Symptom: installation UpgradeStatus: Upgraded to focal on 2020-04-27 (134 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eugen 1907 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-10-18 (332 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20Q7001CGE Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic root=/dev/mapper/vgubuntu-root ro quiet splash pcie_aspm=off ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.3 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-27 (141 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 03/24/2020 dmi.bios.vendor: LENOVO dmi.bios.version: R0ZET40W (1.18 ) dmi.board.asset.tag: Not Available dmi.board.name: 20Q7001CGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0ZET40W(1.18):bd03/24/2020:svnLENOVO:pn20Q7001CGE:pvrThinkPadL590:rvnLENOVO:rn20Q7001CGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L590 dmi.product.name: 20Q7001CGE dmi.product.sku: LENOVO_MT_20Q7_BU_SMB_FM_ThinkPad L590 dmi.product.version: ThinkPad L590 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894860/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894860] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1894860/+attachment/5411001/+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/1894860 Title: Boot fails with newer kernel Status in linux package in Ubuntu: Confirmed Bug description: I get a "cryptsetup: Waiting for encrypted source device UUID=" message when trying to boot with kernels 5.4.0-47 and 5.4.0.-45 and then nothing happens pressing ESC displays "Volume group "vgubuntu" not found Cannot process volume group vgubuntu" System was dm-crypt/LUKS encrypted at installation kernel 5.4.0-42 still works ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Tue Sep 8 16:41:34 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed only-ubiquity quiet splash nomodeset --- InstallationDate: Installed on 2019-10-18 (326 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity Symptom: installation UpgradeStatus: Upgraded to focal on 2020-04-27 (134 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eugen 1907 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-10-18 (332 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20Q7001CGE Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic root=/dev/mapper/vgubuntu-root ro quiet splash pcie_aspm=off ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.3 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-27 (141 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 03/24/2020 dmi.bios.vendor: LENOVO dmi.bios.version: R0ZET40W (1.18 ) dmi.board.asset.tag: Not Available dmi.board.name: 20Q7001CGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0ZET40W(1.18):bd03/24/2020:svnLENOVO:pn20Q7001CGE:pvrThinkPadL590:rvnLENOVO:rn20Q7001CGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L590 dmi.product.name: 20Q7001CGE dmi.product.sku: LENOVO_MT_20Q7_BU_SMB_FM_ThinkPad L590 dmi.product.version: ThinkPad L590 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894860/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894860] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1894860/+attachment/5411006/+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/1894860 Title: Boot fails with newer kernel Status in linux package in Ubuntu: Confirmed Bug description: I get a "cryptsetup: Waiting for encrypted source device UUID=" message when trying to boot with kernels 5.4.0-47 and 5.4.0.-45 and then nothing happens pressing ESC displays "Volume group "vgubuntu" not found Cannot process volume group vgubuntu" System was dm-crypt/LUKS encrypted at installation kernel 5.4.0-42 still works ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Tue Sep 8 16:41:34 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed only-ubiquity quiet splash nomodeset --- InstallationDate: Installed on 2019-10-18 (326 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity Symptom: installation UpgradeStatus: Upgraded to focal on 2020-04-27 (134 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eugen 1907 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-10-18 (332 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20Q7001CGE Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic root=/dev/mapper/vgubuntu-root ro quiet splash pcie_aspm=off ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.3 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-27 (141 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 03/24/2020 dmi.bios.vendor: LENOVO dmi.bios.version: R0ZET40W (1.18 ) dmi.board.asset.tag: Not Available dmi.board.name: 20Q7001CGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0ZET40W(1.18):bd03/24/2020:svnLENOVO:pn20Q7001CGE:pvrThinkPadL590:rvnLENOVO:rn20Q7001CGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L590 dmi.product.name: 20Q7001CGE dmi.product.sku: LENOVO_MT_20Q7_BU_SMB_FM_ThinkPad L590 dmi.product.version: ThinkPad L590 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894860/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894860] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1894860/+attachment/5410998/+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/1894860 Title: Boot fails with newer kernel Status in linux package in Ubuntu: Confirmed Bug description: I get a "cryptsetup: Waiting for encrypted source device UUID=" message when trying to boot with kernels 5.4.0-47 and 5.4.0.-45 and then nothing happens pressing ESC displays "Volume group "vgubuntu" not found Cannot process volume group vgubuntu" System was dm-crypt/LUKS encrypted at installation kernel 5.4.0-42 still works ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Tue Sep 8 16:41:34 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed only-ubiquity quiet splash nomodeset --- InstallationDate: Installed on 2019-10-18 (326 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity Symptom: installation UpgradeStatus: Upgraded to focal on 2020-04-27 (134 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eugen 1907 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-10-18 (332 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20Q7001CGE Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic root=/dev/mapper/vgubuntu-root ro quiet splash pcie_aspm=off ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.3 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-27 (141 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 03/24/2020 dmi.bios.vendor: LENOVO dmi.bios.version: R0ZET40W (1.18 ) dmi.board.asset.tag: Not Available dmi.board.name: 20Q7001CGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0ZET40W(1.18):bd03/24/2020:svnLENOVO:pn20Q7001CGE:pvrThinkPadL590:rvnLENOVO:rn20Q7001CGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L590 dmi.product.name: 20Q7001CGE dmi.product.sku: LENOVO_MT_20Q7_BU_SMB_FM_ThinkPad L590 dmi.product.version: ThinkPad L590 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894860/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894860] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1894860/+attachment/5411002/+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/1894860 Title: Boot fails with newer kernel Status in linux package in Ubuntu: Confirmed Bug description: I get a "cryptsetup: Waiting for encrypted source device UUID=" message when trying to boot with kernels 5.4.0-47 and 5.4.0.-45 and then nothing happens pressing ESC displays "Volume group "vgubuntu" not found Cannot process volume group vgubuntu" System was dm-crypt/LUKS encrypted at installation kernel 5.4.0-42 still works ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Tue Sep 8 16:41:34 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed only-ubiquity quiet splash nomodeset --- InstallationDate: Installed on 2019-10-18 (326 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity Symptom: installation UpgradeStatus: Upgraded to focal on 2020-04-27 (134 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eugen 1907 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-10-18 (332 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20Q7001CGE Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic root=/dev/mapper/vgubuntu-root ro quiet splash pcie_aspm=off ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.3 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-27 (141 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 03/24/2020 dmi.bios.vendor: LENOVO dmi.bios.version: R0ZET40W (1.18 ) dmi.board.asset.tag: Not Available dmi.board.name: 20Q7001CGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0ZET40W(1.18):bd03/24/2020:svnLENOVO:pn20Q7001CGE:pvrThinkPadL590:rvnLENOVO:rn20Q7001CGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L590 dmi.product.name: 20Q7001CGE dmi.product.sku: LENOVO_MT_20Q7_BU_SMB_FM_ThinkPad L590 dmi.product.version: ThinkPad L590 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894860/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894860] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1894860/+attachment/5411003/+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/1894860 Title: Boot fails with newer kernel Status in linux package in Ubuntu: Confirmed Bug description: I get a "cryptsetup: Waiting for encrypted source device UUID=" message when trying to boot with kernels 5.4.0-47 and 5.4.0.-45 and then nothing happens pressing ESC displays "Volume group "vgubuntu" not found Cannot process volume group vgubuntu" System was dm-crypt/LUKS encrypted at installation kernel 5.4.0-42 still works ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Tue Sep 8 16:41:34 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed only-ubiquity quiet splash nomodeset --- InstallationDate: Installed on 2019-10-18 (326 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity Symptom: installation UpgradeStatus: Upgraded to focal on 2020-04-27 (134 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eugen 1907 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-10-18 (332 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20Q7001CGE Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic root=/dev/mapper/vgubuntu-root ro quiet splash pcie_aspm=off ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.3 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-27 (141 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 03/24/2020 dmi.bios.vendor: LENOVO dmi.bios.version: R0ZET40W (1.18 ) dmi.board.asset.tag: Not Available dmi.board.name: 20Q7001CGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0ZET40W(1.18):bd03/24/2020:svnLENOVO:pn20Q7001CGE:pvrThinkPadL590:rvnLENOVO:rn20Q7001CGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L590 dmi.product.name: 20Q7001CGE dmi.product.sku: LENOVO_MT_20Q7_BU_SMB_FM_ThinkPad L590 dmi.product.version: ThinkPad L590 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894860/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894860] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1894860/+attachment/5411008/+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/1894860 Title: Boot fails with newer kernel Status in linux package in Ubuntu: Confirmed Bug description: I get a "cryptsetup: Waiting for encrypted source device UUID=" message when trying to boot with kernels 5.4.0-47 and 5.4.0.-45 and then nothing happens pressing ESC displays "Volume group "vgubuntu" not found Cannot process volume group vgubuntu" System was dm-crypt/LUKS encrypted at installation kernel 5.4.0-42 still works ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Tue Sep 8 16:41:34 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed only-ubiquity quiet splash nomodeset --- InstallationDate: Installed on 2019-10-18 (326 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity Symptom: installation UpgradeStatus: Upgraded to focal on 2020-04-27 (134 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eugen 1907 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-10-18 (332 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20Q7001CGE Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic root=/dev/mapper/vgubuntu-root ro quiet splash pcie_aspm=off ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.3 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-27 (141 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 03/24/2020 dmi.bios.vendor: LENOVO dmi.bios.version: R0ZET40W (1.18 ) dmi.board.asset.tag: Not Available dmi.board.name: 20Q7001CGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0ZET40W(1.18):bd03/24/2020:svnLENOVO:pn20Q7001CGE:pvrThinkPadL590:rvnLENOVO:rn20Q7001CGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L590 dmi.product.name: 20Q7001CGE dmi.product.sku: LENOVO_MT_20Q7_BU_SMB_FM_ThinkPad L590 dmi.product.version: ThinkPad L590 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894860/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894860] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1894860/+attachment/5411005/+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/1894860 Title: Boot fails with newer kernel Status in linux package in Ubuntu: Confirmed Bug description: I get a "cryptsetup: Waiting for encrypted source device UUID=" message when trying to boot with kernels 5.4.0-47 and 5.4.0.-45 and then nothing happens pressing ESC displays "Volume group "vgubuntu" not found Cannot process volume group vgubuntu" System was dm-crypt/LUKS encrypted at installation kernel 5.4.0-42 still works ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Tue Sep 8 16:41:34 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed only-ubiquity quiet splash nomodeset --- InstallationDate: Installed on 2019-10-18 (326 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity Symptom: installation UpgradeStatus: Upgraded to focal on 2020-04-27 (134 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eugen 1907 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-10-18 (332 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20Q7001CGE Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic root=/dev/mapper/vgubuntu-root ro quiet splash pcie_aspm=off ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.3 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-27 (141 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 03/24/2020 dmi.bios.vendor: LENOVO dmi.bios.version: R0ZET40W (1.18 ) dmi.board.asset.tag: Not Available dmi.board.name: 20Q7001CGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0ZET40W(1.18):bd03/24/2020:svnLENOVO:pn20Q7001CGE:pvrThinkPadL590:rvnLENOVO:rn20Q7001CGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L590 dmi.product.name: 20Q7001CGE dmi.product.sku: LENOVO_MT_20Q7_BU_SMB_FM_ThinkPad L590 dmi.product.version: ThinkPad L590 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894860/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894860] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1894860/+attachment/5411000/+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/1894860 Title: Boot fails with newer kernel Status in linux package in Ubuntu: Confirmed Bug description: I get a "cryptsetup: Waiting for encrypted source device UUID=" message when trying to boot with kernels 5.4.0-47 and 5.4.0.-45 and then nothing happens pressing ESC displays "Volume group "vgubuntu" not found Cannot process volume group vgubuntu" System was dm-crypt/LUKS encrypted at installation kernel 5.4.0-42 still works ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Tue Sep 8 16:41:34 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed only-ubiquity quiet splash nomodeset --- InstallationDate: Installed on 2019-10-18 (326 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity Symptom: installation UpgradeStatus: Upgraded to focal on 2020-04-27 (134 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eugen 1907 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-10-18 (332 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20Q7001CGE Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic root=/dev/mapper/vgubuntu-root ro quiet splash pcie_aspm=off ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.3 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-27 (141 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 03/24/2020 dmi.bios.vendor: LENOVO dmi.bios.version: R0ZET40W (1.18 ) dmi.board.asset.tag: Not Available dmi.board.name: 20Q7001CGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0ZET40W(1.18):bd03/24/2020:svnLENOVO:pn20Q7001CGE:pvrThinkPadL590:rvnLENOVO:rn20Q7001CGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L590 dmi.product.name: 20Q7001CGE dmi.product.sku: LENOVO_MT_20Q7_BU_SMB_FM_ThinkPad L590 dmi.product.version: ThinkPad L590 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894860/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894860] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1894860/+attachment/5410999/+files/Lspci-vt.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/1894860 Title: Boot fails with newer kernel Status in linux package in Ubuntu: Confirmed Bug description: I get a "cryptsetup: Waiting for encrypted source device UUID=" message when trying to boot with kernels 5.4.0-47 and 5.4.0.-45 and then nothing happens pressing ESC displays "Volume group "vgubuntu" not found Cannot process volume group vgubuntu" System was dm-crypt/LUKS encrypted at installation kernel 5.4.0-42 still works ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Tue Sep 8 16:41:34 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed only-ubiquity quiet splash nomodeset --- InstallationDate: Installed on 2019-10-18 (326 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity Symptom: installation UpgradeStatus: Upgraded to focal on 2020-04-27 (134 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eugen 1907 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-10-18 (332 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20Q7001CGE Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic root=/dev/mapper/vgubuntu-root ro quiet splash pcie_aspm=off ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.3 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-27 (141 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 03/24/2020 dmi.bios.vendor: LENOVO dmi.bios.version: R0ZET40W (1.18 ) dmi.board.asset.tag: Not Available dmi.board.name: 20Q7001CGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0ZET40W(1.18):bd03/24/2020:svnLENOVO:pn20Q7001CGE:pvrThinkPadL590:rvnLENOVO:rn20Q7001CGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L590 dmi.product.name: 20Q7001CGE dmi.product.sku: LENOVO_MT_20Q7_BU_SMB_FM_ThinkPad L590 dmi.product.version: ThinkPad L590 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894860/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894860] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1894860/+attachment/5411007/+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/1894860 Title: Boot fails with newer kernel Status in linux package in Ubuntu: Confirmed Bug description: I get a "cryptsetup: Waiting for encrypted source device UUID=" message when trying to boot with kernels 5.4.0-47 and 5.4.0.-45 and then nothing happens pressing ESC displays "Volume group "vgubuntu" not found Cannot process volume group vgubuntu" System was dm-crypt/LUKS encrypted at installation kernel 5.4.0-42 still works ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Tue Sep 8 16:41:34 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed only-ubiquity quiet splash nomodeset --- InstallationDate: Installed on 2019-10-18 (326 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity Symptom: installation UpgradeStatus: Upgraded to focal on 2020-04-27 (134 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eugen 1907 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-10-18 (332 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20Q7001CGE Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic root=/dev/mapper/vgubuntu-root ro quiet splash pcie_aspm=off ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.3 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-27 (141 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 03/24/2020 dmi.bios.vendor: LENOVO dmi.bios.version: R0ZET40W (1.18 ) dmi.board.asset.tag: Not Available dmi.board.name: 20Q7001CGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0ZET40W(1.18):bd03/24/2020:svnLENOVO:pn20Q7001CGE:pvrThinkPadL590:rvnLENOVO:rn20Q7001CGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L590 dmi.product.name: 20Q7001CGE dmi.product.sku: LENOVO_MT_20Q7_BU_SMB_FM_ThinkPad L590 dmi.product.version: ThinkPad L590 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894860/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894860] Re: Boot fails with newer kernel
apport information ** Tags added: apport-collected ** Description changed: I get a "cryptsetup: Waiting for encrypted source device UUID=" message when trying to boot with kernels 5.4.0-47 and 5.4.0.-45 and then nothing happens pressing ESC displays "Volume group "vgubuntu" not found Cannot process volume group vgubuntu" System was dm-crypt/LUKS encrypted at installation kernel 5.4.0-42 still works ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Tue Sep 8 16:41:34 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed only-ubiquity quiet splash nomodeset --- InstallationDate: Installed on 2019-10-18 (326 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity Symptom: installation UpgradeStatus: Upgraded to focal on 2020-04-27 (134 days ago) + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.8 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: eugen 1907 F pulseaudio + CasperMD5CheckResult: skip + CurrentDesktop: GNOME + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2019-10-18 (332 days ago) + InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) + MachineType: LENOVO 20Q7001CGE + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=de_DE.UTF-8 + SHELL=/bin/bash + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic root=/dev/mapper/vgubuntu-root ro quiet splash pcie_aspm=off + ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 + RelatedPackageVersions: + linux-restricted-modules-5.4.0-42-generic N/A + linux-backports-modules-5.4.0-42-generic N/A + linux-firmware1.187.3 + Tags: focal + Uname: Linux 5.4.0-42-generic x86_64 + UpgradeStatus: Upgraded to focal on 2020-04-27 (141 days ago) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark + _MarkForUpload: True + dmi.bios.date: 03/24/2020 + dmi.bios.vendor: LENOVO + dmi.bios.version: R0ZET40W (1.18 ) + dmi.board.asset.tag: Not Available + dmi.board.name: 20Q7001CGE + dmi.board.vendor: LENOVO + dmi.board.version: SDK0J40697 WIN + dmi.chassis.asset.tag: No Asset Information + dmi.chassis.type: 10 + dmi.chassis.vendor: LENOVO + dmi.chassis.version: None + dmi.modalias: dmi:bvnLENOVO:bvrR0ZET40W(1.18):bd03/24/2020:svnLENOVO:pn20Q7001CGE:pvrThinkPadL590:rvnLENOVO:rn20Q7001CGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: + dmi.product.family: ThinkPad L590 + dmi.product.name: 20Q7001CGE + dmi.product.sku: LENOVO_MT_20Q7_BU_SMB_FM_ThinkPad L590 + dmi.product.version: ThinkPad L590 + dmi.sys.vendor: LENOVO ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1894860/+attachment/5410994/+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/1894860 Title: Boot fails with newer kernel Status in linux package in Ubuntu: Confirmed Bug description: I get a "cryptsetup: Waiting for encrypted source device UUID=" message when trying to boot with kernels 5.4.0-47 and 5.4.0.-45 and then nothing happens pressing ESC displays "Volume group "vgubuntu" not found Cannot process volume group vgubuntu" System was dm-crypt/LUKS encrypted at installation kernel 5.4.0-42 still works ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Tue Sep 8 16:41:34 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed only-ubiquity quiet splash nomodeset --- InstallationDate: Installed on 2019-10-18 (326 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity Symptom: installation UpgradeStatus: Upgraded to focal on 2020-04-27 (134 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eugen 1907 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.04 Installatio
[Kernel-packages] [Bug 1894860] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1894860/+attachment/5411004/+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/1894860 Title: Boot fails with newer kernel Status in linux package in Ubuntu: Confirmed Bug description: I get a "cryptsetup: Waiting for encrypted source device UUID=" message when trying to boot with kernels 5.4.0-47 and 5.4.0.-45 and then nothing happens pressing ESC displays "Volume group "vgubuntu" not found Cannot process volume group vgubuntu" System was dm-crypt/LUKS encrypted at installation kernel 5.4.0-42 still works ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Tue Sep 8 16:41:34 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed only-ubiquity quiet splash nomodeset --- InstallationDate: Installed on 2019-10-18 (326 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity Symptom: installation UpgradeStatus: Upgraded to focal on 2020-04-27 (134 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eugen 1907 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-10-18 (332 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20Q7001CGE Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic root=/dev/mapper/vgubuntu-root ro quiet splash pcie_aspm=off ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.3 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-27 (141 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 03/24/2020 dmi.bios.vendor: LENOVO dmi.bios.version: R0ZET40W (1.18 ) dmi.board.asset.tag: Not Available dmi.board.name: 20Q7001CGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0ZET40W(1.18):bd03/24/2020:svnLENOVO:pn20Q7001CGE:pvrThinkPadL590:rvnLENOVO:rn20Q7001CGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L590 dmi.product.name: 20Q7001CGE dmi.product.sku: LENOVO_MT_20Q7_BU_SMB_FM_ThinkPad L590 dmi.product.version: ThinkPad L590 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894860/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894860] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1894860/+attachment/5410997/+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/1894860 Title: Boot fails with newer kernel Status in linux package in Ubuntu: Confirmed Bug description: I get a "cryptsetup: Waiting for encrypted source device UUID=" message when trying to boot with kernels 5.4.0-47 and 5.4.0.-45 and then nothing happens pressing ESC displays "Volume group "vgubuntu" not found Cannot process volume group vgubuntu" System was dm-crypt/LUKS encrypted at installation kernel 5.4.0-42 still works ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Tue Sep 8 16:41:34 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed only-ubiquity quiet splash nomodeset --- InstallationDate: Installed on 2019-10-18 (326 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity Symptom: installation UpgradeStatus: Upgraded to focal on 2020-04-27 (134 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eugen 1907 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-10-18 (332 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20Q7001CGE Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic root=/dev/mapper/vgubuntu-root ro quiet splash pcie_aspm=off ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.3 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-27 (141 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 03/24/2020 dmi.bios.vendor: LENOVO dmi.bios.version: R0ZET40W (1.18 ) dmi.board.asset.tag: Not Available dmi.board.name: 20Q7001CGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0ZET40W(1.18):bd03/24/2020:svnLENOVO:pn20Q7001CGE:pvrThinkPadL590:rvnLENOVO:rn20Q7001CGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L590 dmi.product.name: 20Q7001CGE dmi.product.sku: LENOVO_MT_20Q7_BU_SMB_FM_ThinkPad L590 dmi.product.version: ThinkPad L590 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894860/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894860] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1894860/+attachment/5411009/+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/1894860 Title: Boot fails with newer kernel Status in linux package in Ubuntu: Confirmed Bug description: I get a "cryptsetup: Waiting for encrypted source device UUID=" message when trying to boot with kernels 5.4.0-47 and 5.4.0.-45 and then nothing happens pressing ESC displays "Volume group "vgubuntu" not found Cannot process volume group vgubuntu" System was dm-crypt/LUKS encrypted at installation kernel 5.4.0-42 still works ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Tue Sep 8 16:41:34 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed only-ubiquity quiet splash nomodeset --- InstallationDate: Installed on 2019-10-18 (326 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity Symptom: installation UpgradeStatus: Upgraded to focal on 2020-04-27 (134 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eugen 1907 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-10-18 (332 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20Q7001CGE Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic root=/dev/mapper/vgubuntu-root ro quiet splash pcie_aspm=off ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.3 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-27 (141 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 03/24/2020 dmi.bios.vendor: LENOVO dmi.bios.version: R0ZET40W (1.18 ) dmi.board.asset.tag: Not Available dmi.board.name: 20Q7001CGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0ZET40W(1.18):bd03/24/2020:svnLENOVO:pn20Q7001CGE:pvrThinkPadL590:rvnLENOVO:rn20Q7001CGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L590 dmi.product.name: 20Q7001CGE dmi.product.sku: LENOVO_MT_20Q7_BU_SMB_FM_ThinkPad L590 dmi.product.version: ThinkPad L590 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894860/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894860] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1894860/+attachment/5411010/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1894860 Title: Boot fails with newer kernel Status in linux package in Ubuntu: Confirmed Bug description: I get a "cryptsetup: Waiting for encrypted source device UUID=" message when trying to boot with kernels 5.4.0-47 and 5.4.0.-45 and then nothing happens pressing ESC displays "Volume group "vgubuntu" not found Cannot process volume group vgubuntu" System was dm-crypt/LUKS encrypted at installation kernel 5.4.0-42 still works ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Tue Sep 8 16:41:34 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed only-ubiquity quiet splash nomodeset --- InstallationDate: Installed on 2019-10-18 (326 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity Symptom: installation UpgradeStatus: Upgraded to focal on 2020-04-27 (134 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eugen 1907 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-10-18 (332 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20Q7001CGE Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic root=/dev/mapper/vgubuntu-root ro quiet splash pcie_aspm=off ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.3 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-27 (141 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 03/24/2020 dmi.bios.vendor: LENOVO dmi.bios.version: R0ZET40W (1.18 ) dmi.board.asset.tag: Not Available dmi.board.name: 20Q7001CGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0ZET40W(1.18):bd03/24/2020:svnLENOVO:pn20Q7001CGE:pvrThinkPadL590:rvnLENOVO:rn20Q7001CGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L590 dmi.product.name: 20Q7001CGE dmi.product.sku: LENOVO_MT_20Q7_BU_SMB_FM_ThinkPad L590 dmi.product.version: ThinkPad L590 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894860/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894860] Re: Boot fails with newer kernel
okay, here you go, done both, hopefully you guys can work with the provided info -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1894860 Title: Boot fails with newer kernel Status in linux package in Ubuntu: Confirmed Bug description: I get a "cryptsetup: Waiting for encrypted source device UUID=" message when trying to boot with kernels 5.4.0-47 and 5.4.0.-45 and then nothing happens pressing ESC displays "Volume group "vgubuntu" not found Cannot process volume group vgubuntu" System was dm-crypt/LUKS encrypted at installation kernel 5.4.0-42 still works ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Tue Sep 8 16:41:34 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed only-ubiquity quiet splash nomodeset --- InstallationDate: Installed on 2019-10-18 (326 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity Symptom: installation UpgradeStatus: Upgraded to focal on 2020-04-27 (134 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eugen 1907 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-10-18 (332 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20Q7001CGE Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic root=/dev/mapper/vgubuntu-root ro quiet splash pcie_aspm=off ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.3 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-27 (141 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 03/24/2020 dmi.bios.vendor: LENOVO dmi.bios.version: R0ZET40W (1.18 ) dmi.board.asset.tag: Not Available dmi.board.name: 20Q7001CGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0ZET40W(1.18):bd03/24/2020:svnLENOVO:pn20Q7001CGE:pvrThinkPadL590:rvnLENOVO:rn20Q7001CGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L590 dmi.product.name: 20Q7001CGE dmi.product.sku: LENOVO_MT_20Q7_BU_SMB_FM_ThinkPad L590 dmi.product.version: ThinkPad L590 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894860/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration
** Branch linked: lp:~paelzer/britney/hints-ubuntu-focal-disable-systemd -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1892358 Title: autopkgtest success rate dropped inhibiting proposed migration Status in build-essential package in Ubuntu: Invalid Status in glib2.0 package in Ubuntu: Invalid Status in iputils package in Ubuntu: Invalid Status in kbd package in Ubuntu: Invalid Status in linux-meta package in Ubuntu: Invalid Status in ntpsec package in Ubuntu: Invalid Status in qemu package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in util-linux package in Ubuntu: Invalid Status in linux-meta source package in Bionic: New Status in systemd source package in Bionic: New Status in build-essential source package in Focal: Confirmed Status in linux-meta source package in Focal: New Status in qemu source package in Focal: Confirmed Status in systemd source package in Focal: Confirmed Status in util-linux source package in Focal: Confirmed Bug description: Hi, we had such cases in the past like bug 1817721 for bionic and maybe bug 1892130 is about the same as well. There were more but I didn't want to search for all of them - what I checked is that there are no open ones clearly pointing out the recent further drop in already flaky subtests. In particular the tests "tests-in-lxd" and "systemd-fsckd" were known to be flaky before, but got even worse. Here stats of the last 40 runs, it might be a coincidences that this is after 246-2ubuntu1 landed. Could as well be any other change groovy amd64 tests-in-lxd (F 42% S 0% B 10% => P 45%/) BFFFBFF.B.F.F...FBF build-login(F 0% S 0% B 10% => P 87%/) B...B...BB. unit-config(F 0% S 0% B 10% => P 87%/) B...B...BB. networkd-testpy(F 0% S 0% B 10% => P 87%/) B...B...BB. boot-and-services (F 0% S 0% B 10% => P 87%/) B...B...BB. boot-smoke (F 0% S 0% B 10% => P 87%/) B...B...BB. logind (F 0% S 0% B 10% => P 87%/) B...B...BB. storage(F 0% S 0% B 10% => P 87%/) B...B...BB. upstream (F 35% S 0% B 10% => P 52%/) ..FFB.FFF.FFBFF.B.F.F..FFBF udev (F 0% S 0% B 10% => P 87%/) B...B...BB. systemd-fsckd (F 37% S 0% B 10% => P 50%/) BFFFB.FF...FB.F..B. root-unittests (F 0% S 0% B 10% => P 87%/) B...B...BB. ppc64el tests-in-lxd (F 25% S 0% B 0% => P 75%/) FFFFF.F. systemd-fsckd (F 35% S 0% B 0% => P 65%/) FFF...FFFFF.F..F root-unittests (F 2% S 0% B 0% => P 97%/) ..F. s390x tests-in-lxd (F 52% S 0% B 0% => P 47%/) FFF.FFF.FF....F. timedated (F 2% S 0% B 0% => P 97%/) ...F upstream (F 17% S 0% B 0% => P 82%/) .F..F.F.FFF...F. systemd-fsckd (F 32% S 0% B 0% => P 67%/) FFF..FF..F.FF..F root-unittests (F 10% S 0% B 0% => P 90%/) FFF...F. arm64 tests-in-lxd (F 40% S 0% B 2% => P 57%/) F.B...FFF.FF..F..F.FFF.F logind (F 2% S 0% B 2% => P 95%/) ..B...F. upstream (F 22% S 0% B 2% => P 75%/) ...F.FB.F.F.F..FFF.F root-unittests (F 12% S 0% B 2% => P 85%/) ..B.F...F.FF...F (I'm sure LP will make this unreadable, but is is nice in monospace) Whatever the root cause is - the success rate of these has reduced so much that the (even formerly questionable) practice of retry-until- success won't work anymore. I have run the two tests in a local VM and systemd-fsckd works there while tests-in-lxd seems to trip over the old flaky fellow being "boot-and-services". We had the discussion in the past, but I think I need to again bring up the suggestion to skip "tests-in-lxd" and "systemd-fsckd" until they are on reasonable success rates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/build-essential/+bug/1892358/+subscriptions -- Mailing li
[Kernel-packages] [Bug 1895666] [NEW] package linux-firmware 1.187 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
Public bug reported: While upgrading ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: utilisateur912 F pulseaudio CasperMD5CheckResult: skip Date: Tue Sep 15 14:40:55 2020 Dependencies: ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 InstallationDate: Installed on 2020-09-15 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: System manufacturer System Product Name PackageArchitecture: all ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic root=UUID=28b6bfaa-3d0a-468b-b26a-1dd0ec5a3c5f ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26.3 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux-firmware Title: package linux-firmware 1.187 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/19/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1903 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MAXIMUS V GENE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1903:bd08/19/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVGENE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1895666 Title: package linux-firmware 1.187 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 Status in linux-firmware package in Ubuntu: New Bug description: While upgrading ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: utilisateur912 F pulseaudio CasperMD5CheckResult: skip Date: Tue Sep 15 14:40:55 2020 Dependencies: ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 InstallationDate: Installed on 2020-09-15 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: System manufacturer System Product Name PackageArchitecture: all ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic root=UUID=28b6bfaa-3d0a-468b-b26a-1dd0ec5a3c5f ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26.3 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux-firmware Title: package linux-firmware 1.187 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/19/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1903 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MAXIMUS V GENE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1903:bd08/19/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVGENE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor:
[Kernel-packages] [Bug 1895669] [NEW] Add more support to Lenovo ThinkStation P620
Public bug reported: [Impact] After upgrading the audio device firmware and doing more testing, we found some new audio issue on Lenovo P620: 1) Rear mic doesn't work. 2) Front and rear mic/line-in don't use hardware gain to control capture volume. [Fix] For 1), add proper PCM stream assignment to the rear microphone. For 2), add MixerElem to let alsa-lib and PulseAudio to pick correct mixer to change HW gain. [Test] With the new UCM applied, rear mic starts to work, and PulseAudio can control the hardware gain. [Regression Potential] The system hasn't hit the market so there's no chance to regression any system in the wild. ** Affects: alsa-ucm-conf (Ubuntu) Importance: Undecided Status: New ** Affects: alsa-ucm-conf (Ubuntu Focal) Importance: Undecided Status: New ** Affects: alsa-ucm-conf (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: alsa-ucm-conf (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: alsa-ucm-conf (Ubuntu Groovy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1895669 Title: Add more support to Lenovo ThinkStation P620 Status in alsa-ucm-conf package in Ubuntu: New Status in alsa-ucm-conf source package in Focal: New Status in alsa-ucm-conf source package in Groovy: New Bug description: [Impact] After upgrading the audio device firmware and doing more testing, we found some new audio issue on Lenovo P620: 1) Rear mic doesn't work. 2) Front and rear mic/line-in don't use hardware gain to control capture volume. [Fix] For 1), add proper PCM stream assignment to the rear microphone. For 2), add MixerElem to let alsa-lib and PulseAudio to pick correct mixer to change HW gain. [Test] With the new UCM applied, rear mic starts to work, and PulseAudio can control the hardware gain. [Regression Potential] The system hasn't hit the market so there's no chance to regression any system in the wild. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1895669/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895667] [NEW] Touch pad stopped working
Public bug reported: I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:19/PNP0C0D:00/input/input0 U: Uniq= H: Handlers=event0 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab41 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input2 U: Uniq= H: Handlers=sysrq kbd event2 leds B: PROP=0 B: EV=120013 B: KEY=2 20 0 0 1500f0210 3803078f900d401 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0011 Vendor=0002 Product=0007 Version=01b1 N: Name="SynPS/2 Synaptics TouchPad" P: Phys=isa0060/serio1/input0 S: Sysfs=/devices/platform/i8042/serio1/input/input4 U: Uniq= H: Handlers=mouse0 event3 B: PROP=1 B: EV=b B: KEY=e520 3 0 0 0 0 B: ABS=66080001103 I: Bus=0019 Vendor= Product= Version= N: Name="HP Wireless hotkeys" P: Phys=hpq6001/input0 S: Sysfs=/devices/virtual/input/input5 U: Uniq= H: Handlers=rfkill kbd event4 B: PROP=0 B: EV=3 B: KEY=80 0 0 0 I: Bus=0019 Vendor= Product=0006 Version= N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input6 U: Uniq= H: Handlers=kbd event5 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus=0019 Vendor= Product=0006 Version= N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:34/LNXVIDEO:01/input/input7 U: Uniq= H: Handlers=kbd event6 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus=0003 Vendor=04f2 Product=b65d Version=2650 N: Name="HP TrueVision HD Camera: HP Tru" P: Phys=usb-:00:14.0-5/button S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/input/input8 U: Uniq= H: Handlers=kbd event7 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 I: Bus=0019 Vendor= Product= Version= N: Name="HP WMI hotkeys" P: Phys=wmi/input0 S: Sysfs=/devices/virtual/input/input9 U: Uniq= H: Handlers=kbd event8 B: PROP=0 B: EV=33 B: KEY=40 0 10007 2102400 0 0 B: MSC=10 B: SW=22 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Mic" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input10 U: Uniq= H: Handlers=event9 B: PROP=0 B: EV=21 B: SW=10 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Headphone" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input11 U: Uniq= H: Handlers=event10 B: PROP=0 B: EV=21 B: SW=4 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=3" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input12 U: Uniq= H: Handlers=event11 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=7" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input13 U: Uniq= H: Handlers=event12 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=8" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input14 U: Uniq= H: Handlers=event13 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=9" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input15 U: Uniq= H: Handlers=event14 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=10" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input16 U: Uniq= H: Handlers=event15 B: PROP=0 B: EV=21 B: SW=140 I: Bus=0003 Vendor=275d Product=0ba6 Version=0111 N: Name="USB OPTICAL MOUSE " P: Phys=usb-:00:14.0-3/input0 S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/0003:275D:0BA6.0003/input/input19 U: Uniq= H: Handlers=mouse1 event16 B: PROP=0 B: EV=17 B: KEY=7 0 0 0 0 B: REL=103 B: MSC=10 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-112-generic 4.15.0-112.113 ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18 Uname: Linux 4.15.0-112-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_4_15_0_112_113_generic_71 nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vb 2290 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Sep 15 18:34:29 2020 InstallationDate: Installed on 2018-12-15 (639 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:b009 Realtek
[Kernel-packages] [Bug 1895667] 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/1895667 Title: Touch pad stopped working Status in linux package in Ubuntu: Confirmed Bug description: I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:19/PNP0C0D:00/input/input0 U: Uniq= H: Handlers=event0 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab41 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input2 U: Uniq= H: Handlers=sysrq kbd event2 leds B: PROP=0 B: EV=120013 B: KEY=2 20 0 0 1500f0210 3803078f900d401 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0011 Vendor=0002 Product=0007 Version=01b1 N: Name="SynPS/2 Synaptics TouchPad" P: Phys=isa0060/serio1/input0 S: Sysfs=/devices/platform/i8042/serio1/input/input4 U: Uniq= H: Handlers=mouse0 event3 B: PROP=1 B: EV=b B: KEY=e520 3 0 0 0 0 B: ABS=66080001103 I: Bus=0019 Vendor= Product= Version= N: Name="HP Wireless hotkeys" P: Phys=hpq6001/input0 S: Sysfs=/devices/virtual/input/input5 U: Uniq= H: Handlers=rfkill kbd event4 B: PROP=0 B: EV=3 B: KEY=80 0 0 0 I: Bus=0019 Vendor= Product=0006 Version= N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input6 U: Uniq= H: Handlers=kbd event5 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus=0019 Vendor= Product=0006 Version= N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:34/LNXVIDEO:01/input/input7 U: Uniq= H: Handlers=kbd event6 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus=0003 Vendor=04f2 Product=b65d Version=2650 N: Name="HP TrueVision HD Camera: HP Tru" P: Phys=usb-:00:14.0-5/button S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/input/input8 U: Uniq= H: Handlers=kbd event7 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 I: Bus=0019 Vendor= Product= Version= N: Name="HP WMI hotkeys" P: Phys=wmi/input0 S: Sysfs=/devices/virtual/input/input9 U: Uniq= H: Handlers=kbd event8 B: PROP=0 B: EV=33 B: KEY=40 0 10007 2102400 0 0 B: MSC=10 B: SW=22 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Mic" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input10 U: Uniq= H: Handlers=event9 B: PROP=0 B: EV=21 B: SW=10 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Headphone" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input11 U: Uniq= H: Handlers=event10 B: PROP=0 B: EV=21 B: SW=4 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=3" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input12 U: Uniq= H: Handlers=event11 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=7" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input13 U: Uniq= H: Handlers=event12 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=8" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input14 U: Uniq= H: Handlers=event13 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=9" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input15 U: Uniq= H: Handlers=event14 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=10" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input16 U: Uniq= H: Handlers=event15 B: PROP=0 B: EV=21 B: SW=140 I: Bus=0003 Vendor=275d Product=0ba6 Version=0111 N: Name="USB OPTICAL MOUSE " P: Phys=usb-:00:14.0-3/input0 S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/0003:275D:0BA6.0003/input/input19 U: Uniq= H: Handlers=mouse1 event16 B: PROP=0 B: EV=17 B: KEY=7 0 0 0 0 B: REL=103 B: MSC=10 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-112-generic 4
[Kernel-packages] [Bug 1881699] Re: No analog output
Tagging as notfixing, it seems specific to one configuration and not qualifying as a rls issue ** Tags removed: rls-gg-incoming ** Tags added: rls-gg-notfixing -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881699 Title: No analog output Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After a fresh boot and login, there is no analog output. Only HDMI and bluetooth are available. It becomes available when I kill pulseaudio with 'pulseaudio -k' but the sound indicator only shows 'dummy' output and I cannot control the output from the sound settings or the sound indicator. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu36 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: j-lallement 184080 F pulseaudio /dev/snd/controlC1: j-lallement 184080 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jun 2 06:32:09 2020 InstallationDate: Installed on 2020-05-31 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200527) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/21/2019 dmi.bios.vendor: Intel Corp. dmi.bios.version: FNCML357.0032.2019.1021.1624 dmi.board.asset.tag: Default string dmi.board.name: NUC10i7FNB dmi.board.vendor: Intel Corporation dmi.board.version: K61360-302 dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrFNCML357.0032.2019.1021.1624:bd10/21/2019:svnIntel(R)ClientSystems:pnNUC10i7FNH:pvrK61081-302:rvnIntelCorporation:rnNUC10i7FNB:rvrK61360-302:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: FN dmi.product.name: NUC10i7FNH dmi.product.sku: BXNUC10i7FNH dmi.product.version: K61081-302 dmi.sys.vendor: Intel(R) Client Systems --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu36 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: j-lallement 3669 F pulseaudio /dev/snd/controlC0: j-lallement 3669 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2020-05-31 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200527) MachineType: Intel(R) Client Systems NUC10i7FNH NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: pulseaudio 1:13.99.1-1ubuntu3 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_huyn9u@/vmlinuz-5.4.0-26-generic root=ZFS=rpool/ROOT/ubuntu_huyn9u ro snd-intel-dspcfg.dsp_driver=1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 Tags: groovy Uname: Linux 5.4.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/21/2019 dmi.bios.vendor: Intel Corp. dmi.bios.version: FNCML357.0032.2019.1021.1624 dmi.board.asset.tag: Default string dmi.board.name: NUC10i7FNB dmi.board.vendor: Intel Corporation dmi.board.version: K61360-302 dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrFNCML357.0032.2019.1021.1624:bd10/21/2019:svnIntel(R)ClientSystems:pnNUC10i7FNH:pvrK61081-302:rvnIntelCorporation:rnNUC10i7FNB:rvrK61360-302:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: FN dmi.product.name: NUC10i7FNH dmi.product.sku: BXNUC10i7FNH dmi.product.version: K61081-302 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881699/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895669] Re: Add more support to Lenovo ThinkStation P620
debdiff for groovy ** Patch added: "alsa-ucm-conf_1.2.2-1ubuntu5.debdiff" https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1895669/+attachment/5411068/+files/alsa-ucm-conf_1.2.2-1ubuntu5.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1895669 Title: Add more support to Lenovo ThinkStation P620 Status in HWE Next: New Status in alsa-ucm-conf package in Ubuntu: New Status in alsa-ucm-conf source package in Focal: New Status in alsa-ucm-conf source package in Groovy: New Bug description: [Impact] After upgrading the audio device firmware and doing more testing, we found some new audio issue on Lenovo P620: 1) Rear mic doesn't work. 2) Front and rear mic/line-in don't use hardware gain to control capture volume. [Fix] For 1), add proper PCM stream assignment to the rear microphone. For 2), add MixerElem to let alsa-lib and PulseAudio to pick correct mixer to change HW gain. [Test] With the new UCM applied, rear mic starts to work, and PulseAudio can control the hardware gain. [Regression Potential] The system hasn't hit the market so there's no chance to regression any system in the wild. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1895669/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895669] Re: Add more support to Lenovo ThinkStation P620
debdiff for focal ** Tags added: oem-priority originate-from-1893892 sutton -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1895669 Title: Add more support to Lenovo ThinkStation P620 Status in HWE Next: New Status in alsa-ucm-conf package in Ubuntu: New Status in alsa-ucm-conf source package in Focal: New Status in alsa-ucm-conf source package in Groovy: New Bug description: [Impact] After upgrading the audio device firmware and doing more testing, we found some new audio issue on Lenovo P620: 1) Rear mic doesn't work. 2) Front and rear mic/line-in don't use hardware gain to control capture volume. [Fix] For 1), add proper PCM stream assignment to the rear microphone. For 2), add MixerElem to let alsa-lib and PulseAudio to pick correct mixer to change HW gain. [Test] With the new UCM applied, rear mic starts to work, and PulseAudio can control the hardware gain. [Regression Potential] The system hasn't hit the market so there's no chance to regression any system in the wild. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1895669/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895666] Re: package linux-firmware 1.187 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
Looks like you have a corrupted file. Try running the following in a terminal: $ sudo apt-cache clean $ sudo apt install linux-firmware This should force the file to be redownloaded. ** Changed in: linux-firmware (Ubuntu) Status: New => Incomplete -- 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/1895666 Title: package linux-firmware 1.187 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 Status in linux-firmware package in Ubuntu: Incomplete Bug description: While upgrading ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: utilisateur912 F pulseaudio CasperMD5CheckResult: skip Date: Tue Sep 15 14:40:55 2020 Dependencies: ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 InstallationDate: Installed on 2020-09-15 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: System manufacturer System Product Name PackageArchitecture: all ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic root=UUID=28b6bfaa-3d0a-468b-b26a-1dd0ec5a3c5f ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26.3 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux-firmware Title: package linux-firmware 1.187 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/19/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1903 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MAXIMUS V GENE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1903:bd08/19/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVGENE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1895666/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895640] Re: BlueZ 5.55 release
** Changed in: bluez (Ubuntu) Status: In Progress => Fix Committed ** Changed in: bluez (Ubuntu) Importance: Undecided => Low -- 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/1895640 Title: BlueZ 5.55 release Status in bluez package in Ubuntu: Fix Committed Bug description: https://mirrors.edge.kernel.org/pub/linux/bluetooth/bluez-5.55.tar.xz https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/?h=5.55 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1895640/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895669] Re: Add more support to Lenovo ThinkStation P620
The attachment "alsa-ucm-conf_1.2.2-1ubuntu5.debdiff" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1895669 Title: Add more support to Lenovo ThinkStation P620 Status in HWE Next: New Status in alsa-ucm-conf package in Ubuntu: New Status in alsa-ucm-conf source package in Focal: New Status in alsa-ucm-conf source package in Groovy: New Bug description: [Impact] After upgrading the audio device firmware and doing more testing, we found some new audio issue on Lenovo P620: 1) Rear mic doesn't work. 2) Front and rear mic/line-in don't use hardware gain to control capture volume. [Fix] For 1), add proper PCM stream assignment to the rear microphone. For 2), add MixerElem to let alsa-lib and PulseAudio to pick correct mixer to change HW gain. [Test] With the new UCM applied, rear mic starts to work, and PulseAudio can control the hardware gain. [Regression Potential] The system hasn't hit the market so there's no chance to regression any system in the wild. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1895669/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836701] Re: ubuntu18.04: ipmitool failed: Could not open device at /dev/ipmi0 : No such file or directory
I've given the mods loaded in my initial comment. The output of ls -laF
is the following:
root@x:~# ls -laF /dev/ipmi0 /dev/ipmi/0 /dev/ipmidev/0
ls: cannot access '/dev/ipmi/0': No such file or directory
ls: cannot access '/dev/ipmidev/0': No such file or directory
crw--- 1 root root 240, 0 Sep 11 10:32 /dev/ipmi0
Not sure what logs I can provide, there are errors or anything related to ipmi.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1836701
Title:
ubuntu18.04: ipmitool failed: Could not open device at /dev/ipmi0 : No
such file or directory
Status in ipmitool package in Ubuntu:
Invalid
Status in linux package in Ubuntu:
Incomplete
Bug description:
ipmitool failed in-band
#ipmitool lan print
Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: No such
file or directory
And it work out-band:
# ipmitool -H {theip} -I lanplus -U {user} -P {passwd} lan print
Set in Progress : Set Complete
Auth Type Support : NONE MD2 MD5 PASSWORD
Auth Type Enable: Callback : MD2 MD5 PASSWORD
: User : MD2 MD5 PASSWORD
: Operator : MD2 MD5 PASSWORD
: Admin: MD2 MD5 PASSWORD
: OEM : MD2 MD5 PASSWORD
IP Address Source : DHCP Address
...
But the file exist:
# ls -al /dev/ipmi0
crw--- 1 root root 240, 0 Jul 16 13:55 /dev/ipmi0
# cat /proc/devices | grep ipmidev
240 ipmidev
packages that I installed:
# dpkg -l | grep ipmi
ii freeipmi-common 1.4.11-1.1ubuntu4.1
amd64GNU implementation of the IPMI protocol - common files
ii ipmitool 1.8.18-5ubuntu0.1
amd64utility for IPMI control with kernel driver or LAN interface
(daemon)
ii libfreeipmi16 1.4.11-1.1ubuntu4.1
amd64GNU IPMI - libraries
ii libopenipmi0 2.0.22-1.1ubuntu2.1
amd64Intelligent Platform Management Interface - runtime
ii openipmi 2.0.22-1.1ubuntu2.1
amd64Intelligent Platform Management Interface (for servers)
the mods:
# lsmod| grep ipmi_
ipmi_devintf 20480 0
ipmi_poweroff 16384 0
ipmi_watchdog 28672 0
ipmi_ssif 32768 0
ipmi_si61440 0
ipmi_msghandler53248 6
ipmi_devintf,ipmi_si,nvidia,ipmi_watchdog,ipmi_ssif,ipmi_poweroff
the kernel:
# uname -a
Linux A16969628514217 4.15.0-54-generic #58-Ubuntu SMP Mon Jun 24 10:55:24
UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
the ubuntu version:
# cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=18.04
DISTRIB_CODENAME=bionic
DISTRIB_DESCRIPTION="Ubuntu 18.04.2 LTS"
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ipmitool/+bug/1836701/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855757] Re: [nvidia] Background image corrupted after standby or resume from suspend
Recently I've noticed, when my laptop comes on after sleeping, a lot of text goes missing along with the corrupted background. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1855757 Title: [nvidia] Background image corrupted after standby or resume from suspend Status in mutter package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-390 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-435 package in Ubuntu: Won't Fix Status in mutter source package in Focal: Triaged Status in nvidia-graphics-drivers-340 source package in Focal: Won't Fix Status in nvidia-graphics-drivers-390 source package in Focal: Won't Fix Status in nvidia-graphics-drivers-435 source package in Focal: Won't Fix Bug description: Looks similar to https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1809407 When the computer goes to standby, the background image becomes corrupted. I am able to fix by "killall Xorg" , change the background image (settings > background) and restart. Haven't tried login logout. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.107 Thu May 24 21:54:01 PDT 2018 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Dec 9 10:58:35 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.107, 5.3.0-23-generic, x86_64: installed nvidia-340, 340.107, 5.3.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GT215M [GeForce GTS 360M] [10de:0cb1] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GT215M [GeForce GTS 360M] [1043:203c] InstallationDate: Installed on 2019-11-29 (10 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUSTek Computer Inc. G60JX ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=65117975-c95f-4406-a7cf-da912cda0e70 ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G60JX dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: PEGATRON Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr204:bd12/25/2009:svnASUSTekComputerInc.:pnG60JX:pvr1.0:rvnPEGATRONCORPORATION:rnG60JX:rvr1.0:cvnPEGATRONComputerInc.:ct10:cvr1.0: dmi.product.family: PEGA Family dmi.product.name: G60JX dmi.product.sku: 0 dmi.product.version: 1.0 dmi.sys.vendor: ASUSTek Computer Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1855757/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895718] [NEW] Fix non-working NVMe after S3
Public bug reported: [Impact] KIOXIA NVMe has a 10% chance to stop working after S3. [Fix] Enable ACS quirk on Intel CML root port. [Test] With the patch applied, KIOXIA NVMe always works after S3. [Regression Potential] ACS works at hardware level, so I can't really assess the risk of regression. Since Intel confirmed CML also needs ACS quirk, we can only trust them. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux-oem-5.6 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: Confirmed ** Affects: linux-oem-5.6 (Ubuntu Focal) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Groovy) Importance: Undecided Status: Confirmed ** Affects: linux-oem-5.6 (Ubuntu Groovy) Importance: Undecided Status: Won't Fix ** Tags: oem-priority originate-from-1893902 stella ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: linux-oem-5.6 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-5.6 (Ubuntu Groovy) Status: New => Won't Fix ** Changed in: linux (Ubuntu Focal) Status: New => Confirmed ** Changed in: linux (Ubuntu Groovy) Status: New => Confirmed ** Changed in: linux-oem-5.6 (Ubuntu Focal) Status: New => Confirmed ** Changed in: linux-oem-5.6 (Ubuntu) Status: New => Invalid ** Tags added: oem-priority originate-from-1893902 stella -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1895718 Title: Fix non-working NVMe after S3 Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: Confirmed Status in linux-oem-5.6 source package in Focal: Confirmed Status in linux source package in Groovy: Confirmed Status in linux-oem-5.6 source package in Groovy: Won't Fix Bug description: [Impact] KIOXIA NVMe has a 10% chance to stop working after S3. [Fix] Enable ACS quirk on Intel CML root port. [Test] With the patch applied, KIOXIA NVMe always works after S3. [Regression Potential] ACS works at hardware level, so I can't really assess the risk of regression. Since Intel confirmed CML also needs ACS quirk, we can only trust them. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1895718/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1893820] Re: DPLL2 override remains enabled after warm boot of Linux
Hello Timo. I followed your instructions but could not install the linked kernel images. I instead got the following error, "dpkg: error: cannot access archive 'https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel- next/current/amd64/linux-image- unsigned-5.8.0-050800drmintelnext20200825-generic_5.8.0-050800drmintelnext20200825.202008242209_amd64.deb': No such file or directory When trying to load the links provided into a web browser, I also could not download these .deb files. Please see the attached image for record of this event. ** Attachment added: "DPKG: Error: Cannot access archive" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893820/+attachment/5411120/+files/wm_ubuntu_error.jpg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1893820 Title: DPLL2 override remains enabled after warm boot of Linux Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu Version Target: 18.04.1 LTS (bootable Ubuntu USB stick) Package Version Target: Unknown Expected: Windows S3 Sleep actions with two DisplayPort monitors using Intel integrated graphics should be able to work without issue after entering a Windows OS from a previously loaded Ubuntu session Actual: Windows S3 Sleep actions with two DisplayPort monitors using Intel integrated graphics will result in a BSOD event if a Windows OS is loaded after an Ubuntu OS session that was ended by a warm reboot action Description: Using a dual-boot Ubuntu/Windows 10 desktop computer environment with two native DisplayPort MB connections to the Intel integrated graphics solution and two DisplayPort monitors it was observed that performing a Windows S3 Sleep action will cause a "WHEA uncorrectable error" BSOD event if the first OS loaded is Linux and the second OS Windows is loaded using a warm boot action. Investigating this BSOD event further it was determined that this issue is specific to the "Linux->warm boot->Windows->S3 Sleep" sequence as long as two DisplayPort monitors are connected to the desktop computer's DisplayPort MB connections. A deeper investigation of the cause of the BSOD identified that upon unloading Linux the DPLL2 override bit remains enabled and will cause a subsequent Windows desktop environment to be vulnerable to failure if it makes use of two DisplayPort-connected monitors. This issue can be reproduced using OEM hardware from either of Lenovo, HP, or Dell. This issue was first observed on the Q270/Q370 Intel chipset and the Intel 530/630 Graphics hardware. Calvin Hartwell of Canonical has been made aware of this issue and been provided issue details and video evidence. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893820/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895725] [NEW] Wifi adapter missing
Public bug reported: No wifiadater found on HP G246, Ubuntu 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-47-generic 5.4.0-47.51 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mtnai 1901 F pulseaudio /dev/snd/controlC0: mtnai 1901 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Sep 16 00:54:51 2020 IwConfig: enp1s0no wireless extensions. lono wireless extensions. usb0 no wireless extensions. MachineType: HP HP 246 G4 Notebook PC ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic root=UUID=02f6b563-4d4c-48f8-a25a-c7adfabd9aba ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-47-generic N/A linux-backports-modules-5.4.0-47-generic N/A linux-firmware1.187.3 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/13/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.1A dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80BC dmi.board.vendor: HP dmi.board.version: KBC Version 94.10 dmi.chassis.asset.tag: 5CG6060NKW dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.1A:bd10/13/2015:svnHP:pnHP246G4NotebookPC:pvrCNB1:rvnHP:rn80BC:rvrKBCVersion94.10:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5336AN G=N L=CON B=HP S=246 dmi.product.name: HP 246 G4 Notebook PC dmi.product.sku: N3S55PT#AB2 dmi.product.version: CNB1 dmi.sys.vendor: HP ** 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/1895725 Title: Wifi adapter missing Status in linux package in Ubuntu: New Bug description: No wifiadater found on HP G246, Ubuntu 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-47-generic 5.4.0-47.51 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mtnai 1901 F pulseaudio /dev/snd/controlC0: mtnai 1901 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Sep 16 00:54:51 2020 IwConfig: enp1s0no wireless extensions. lono wireless extensions. usb0 no wireless extensions. MachineType: HP HP 246 G4 Notebook PC ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic root=UUID=02f6b563-4d4c-48f8-a25a-c7adfabd9aba ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-47-generic N/A linux-backports-modules-5.4.0-47-generic N/A linux-firmware1.187.3 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/13/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.1A dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80BC dmi.board.vendor: HP dmi.board.version: KBC Version 94.10 dmi.chassis.asset.tag: 5CG6060NKW dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.1A:bd10/13/2015:svnHP:pnHP246G4NotebookPC:pvrCNB1:rvnHP:rn80BC:rvrKBCVersion94.10:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5336AN G=N L=CON B=HP S=246 dmi.product.name: HP 246 G4 Notebook PC dmi.product.sku: N3S55PT#AB2 dmi.product.version: CNB1 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895725/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895725] 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/1895725 Title: Wifi adapter missing Status in linux package in Ubuntu: Confirmed Bug description: No wifiadater found on HP G246, Ubuntu 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-47-generic 5.4.0-47.51 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mtnai 1901 F pulseaudio /dev/snd/controlC0: mtnai 1901 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Sep 16 00:54:51 2020 IwConfig: enp1s0no wireless extensions. lono wireless extensions. usb0 no wireless extensions. MachineType: HP HP 246 G4 Notebook PC ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic root=UUID=02f6b563-4d4c-48f8-a25a-c7adfabd9aba ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-47-generic N/A linux-backports-modules-5.4.0-47-generic N/A linux-firmware1.187.3 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/13/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.1A dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80BC dmi.board.vendor: HP dmi.board.version: KBC Version 94.10 dmi.chassis.asset.tag: 5CG6060NKW dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.1A:bd10/13/2015:svnHP:pnHP246G4NotebookPC:pvrCNB1:rvnHP:rn80BC:rvrKBCVersion94.10:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5336AN G=N L=CON B=HP S=246 dmi.product.name: HP 246 G4 Notebook PC dmi.product.sku: N3S55PT#AB2 dmi.product.version: CNB1 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895725/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1892546] Re: Novalink (mkvterm command failure)
** Description changed: - -- Problem Description -- - drmgr command is failing while trying to open console for IBMi. + SRU Justification: - Log snap shot: - Please make sure you have specified a valid locale (check your NLSPATH and LANG environment variables. Your application will use english as the default. 2 - 07/15/20 16:01:25.393.531 UTC DEBUG pvmutil[12687.70366696995648]: (common/util/HmclDrmgrHelper.cpp:1036) Command /usr/sbin/pvmdrmgr drmgr -c slot -s 'U9080.MHE.218BA37-V1-C8' -r -w 3 returned 255. Additional messages: /usr/sbin/pvmdrmgr drmgr -c slot -s 'U9080.MHE.218BA37-V1-C8' -r -w 3 - Validating I/O DLPAR capability...yes. - failed to open /sys/bus/pci/slots/U9080.MHE.218BA37-V1-C8/power: No such file or directory - failed to disable hotplug children - Isolation failed for 3008 with -9001 - Valid outstanding translations exist. + [Impact] + * drmgr command is failing while trying to open console for IBMi on PowerVM LPAR - ---Steps to Reproduce--- - Create a VM from PowerVC on a Novalink managed host. Unmanage and manage the VM, this problem gets reproduced - - == - I've tested a proposed fix and it does fix both the -9001 isolation errors after DLPAR remove and vterm state is still open, as well as the /dev/hcvsX index changing after a DLPAR remove/add. I will get that patch sent out to the upstream mailing list for merging. + [Fix] + * 63ffcbdad738 "tty: hvcs: Don't NULL tty->driver_data until hvcs_cleanup()" - Patch submitted upstream: + [Test Case] + * Create a VM from PowerVC on a Novalink managed host. + * Unmanage and manage the VM, this problem gets reproduced. + * grep the logs for "drmgr" - https://lore.kernel.org/linuxppc- - dev/20200820234643.70412-1-tyr...@linux.ibm.com/T/#u + + [Regression Potential] + The regression can be considered as very low, since: + * limited to the IBM Hypervisor Virtual Console Server. + * patched kernel where shared and successfully tested by IBM. + * the worse case, if the cleanup is broken a new opened connection might break. + + [Other] + * The patch got upstream accepted. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1892546 Title: Novalink (mkvterm command failure) Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: New Status in linux source package in Xenial: New Status in linux source package in Bionic: New Status in linux source package in Focal: New Status in linux source package in Groovy: New Bug description: SRU Justification: [Impact] * drmgr command is failing while trying to open console for IBMi on PowerVM LPAR [Fix] * 63ffcbdad738 "tty: hvcs: Don't NULL tty->driver_data until hvcs_cleanup()" [Test Case] * Create a VM from PowerVC on a Novalink managed host. * Unmanage and manage the VM, this problem gets reproduced. * grep the logs for "drmgr" [Regression Potential] The regression can be considered as very low, since: * limited to the IBM Hypervisor Virtual Console Server. * patched kernel where shared and successfully tested by IBM. * the worse case, if the cleanup is broken a new opened connection might break. [Other] * The patch got upstream accepted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1892546/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862559] Re: ubuntu 19.10: unresponsive/freezes on ThunderX2 if system is idle for ~22min
@Naresh: see my comment #4, asking if you are running Ubuntu Desktop. dmesg doesn't tell me that - but an sosreport would, if you can attach that. We've recently hit this on an x86 server, and did tie that back to the system having a desktop installed (Nvidia CUDA 11 somehow brings in gdm as a dependency), so I'm still suspecting the same here. ** Also affects: gdm3 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1862559 Title: ubuntu 19.10: unresponsive/freezes on ThunderX2 if system is idle for ~22min Status in gdm3 package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: UBUNTU 19.10 installed on ThunderX2 saber ARM64 machine. If the system left idle for ~22min it becomes unresponsive. The system will not take any inputs like from UART, ping ..etc. The system will completely freeze and we need to hard reset the system. It could be possible the system goes to hibernate state and could not able to come out of the state. Dmesg log when system halts/no response on Saber boards (TX2) Ubuntu 19.10 ubuntu ttyAMA0 ubuntu login: ubuntu Password: Last login: Wed Jan 29 20:08:22 PST 2020 on ttyAMA0 Welcome to Ubuntu 19.10 (GNU/Linux 5.3.0-26-generic aarch64) * Documentation: https://help.ubuntu.com * Management: https://landscape.canonical.com * Support:https://ubuntu.com/advantage ubuntu@ubuntu:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 19.10 Release: 19.10 Codename: eoan [ +0.732512] audit: type=1400 audit(1580358920.412:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="lsb_release" pid=3087 comm="apparmor_parser" [ +0.64] audit: type=1400 audit(1580358920.412:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/ippusbxd" pid=3091 comm="apparmor_parser" [ +0.000168] audit: type=1400 audit(1580358920.412:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe" pid=3086 comm="apparmor_parser" [ +0.05] audit: type=1400 audit(1580358920.412:5): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe//kmod" pid=3086 comm="apparmor_parser" [ +0.000546] audit: type=1400 audit(1580358920.412:6): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/man" pid=3085 comm="apparmor_parser" [ +0.06] audit: type=1400 audit(1580358920.412:7): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_filter" pid=3085 comm="apparmor_parser" [ +0.05] audit: type=1400 audit(1580358920.412:8): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_groff" pid=3085 comm="apparmor_parser" [ +0.000854] audit: type=1400 audit(1580358920.412:9): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=3089 comm="apparmor_parser" [ +0.002667] audit: type=1400 audit(1580358920.416:10): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=3093 comm="apparmor_parser" [ +0.04] audit: type=1400 audit(1580358920.416:11): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=3093 comm="apparmor_parser" [ +1.382579] igb :92:00.1 enp146s0f1: igb: enp146s0f1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX [ +0.000299] IPv6: ADDRCONF(NETDEV_CHANGE): enp146s0f1: link becomes ready [ +3.131173] mpt3sas_cm0: port enable: SUCCESS [Jan29 20:36] random: crng init done [ +0.04] random: 7 urandom warning(s) missed due to ratelimiting *[Jan29 20:37] rfkill: input handler disabled* *[Jan29 20:57] PM: suspend entry (deep)* To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1862559/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1893897] Re: [Regression] Do not initiate shutdown for EPOW_SHUTDOWN_ON_UPS event
built and tested kernel versions available on: https://people.canonical.com/~patriciasd/kernel-lp1893897/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1893897 Title: [Regression] Do not initiate shutdown for EPOW_SHUTDOWN_ON_UPS event Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: New Status in linux source package in Bionic: New Status in linux source package in Focal: New Status in linux source package in Groovy: Fix Released Bug description: SRU Justification: [Impact] * With commit 79872e35469b "powerpc/pseries: All events of EPOW_SYSTEM_SHUTDOWN must initiate shutdown" it was introduced that all EPOW_SYSTEM_SHUTDOWN events cause immediate shutdowns. * But on LPARs there is a user space tool (rtas_errd) that monitor for EPOW_SHUTDOWN_ON_UPS events. * Once rtas_errd gets an event it initiates a shutdown after predefined time. * Therefore immediate shutdowns must not be triggered if the system is running on UPS (means for EPOW_SHUTDOWN_ON_UPS events). [Fix] * 90a9b102eddf6a3f987d15f4454e26a2532c1c98 90a9b102eddf "powerpc/pseries: Do not initiate shutdown when system is running on UPS" [Test Case] * Setup a Power system on (D)LPAR and run it on UPS with Ubuntu 16.04 or higher (kernel 4.x is needed). * Verify that the user space tool (rtas_errd) is active and running. * Define a time for a potential shutdown in case an EPOW_SHUTDOWN_ON_UPS event occurs. * Trigger an EPOW_SHUTDOWN_ON_UPS event. * Verify if the system got shutdown immediately - or after the pre- defined time. [Regression Potential] * The regression risk is very low, because of the very limited modification in a case statement for EPOW_SHUTDOWN_ON_UPS events. * What may happen is that the system doesn't power off anymore if running on UPS due to the EPOW_SHUTDOWN_ON_UPS case changes - especially if there is a potential problem with rtas_errd that should monitor for these events and should initiate the delayed shutdown. * Other than that I cannot see much potential harm. [Other] * The patch got upstream accepted in v5.9-rc2 and already landed in groovy's kernel 'Ubuntu-5.8.0-18.19', based on the v5.8.4 upstream stable release ticket LP 1893048. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1893897/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1893117] Re: Touchpad not working in Lenovo Ideapad Slim 3i
I have the same problem with a different model laptop in the same line. A new bios update from the vendor appeared on 2nd September, but the pci BAR problem persists after the BIOS update. Trackpad continues to not work and not show up anywhere. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1893117 Title: Touchpad not working in Lenovo Ideapad Slim 3i Status in linux package in Ubuntu: Incomplete Bug description: Touchpad is not working, cat /proc/bus/input/devices doesn't show the touchpad. Ubuntu version : 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: surenmoh 1418 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Aug 26 23:37:06 2020 InstallationDate: Installed on 2020-08-25 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 046d:c018 Logitech, Inc. Optical Wheel Mouse Bus 001 Device 002: ID 13d3:5a08 IMC Networks Integrated Camera Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81WD ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=45c6c6d6-b6f5-4a51-ade2-aaa67a430b03 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EMCN14WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55724 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 3 14IIL05 dmi.modalias: dmi:bvnLENOVO:bvrEMCN14WW:bd05/11/2020:svnLENOVO:pn81WD:pvrIdeaPad314IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55724WIN:cvnLENOVO:ct10:cvrIdeaPad314IIL05: dmi.product.family: IdeaPad 3 14IIL05 dmi.product.name: 81WD dmi.product.sku: LENOVO_MT_81WD_BU_idea_FM_IdeaPad 3 14IIL05 dmi.product.version: IdeaPad 3 14IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893117/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: bluez (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm testing with Sony bluetooth headset SBH20, works fine in A2DP profile, but I can't get audio input and output work in HSP/HFP profile. [Reproduce steps] 1. Scan and pair BT headset in Bluetooth setting 2. Switch to HSP/HFP profile in Sound setting 3. Test sound output/input [Machine information] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 16:26:52 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SBH20 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio Symptom_Type: No sound at all Title: [SBH20, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.13 dmi.board.name: 0188D1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1871794/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1879290] Re: pc: no message on the screen for ~30s on fast HW
Has anything happened that would change the status of this bug or does it still need fixing for uc20? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1879290 Title: pc: no message on the screen for ~30s on fast HW Status in linux package in Ubuntu: Incomplete Status in snapd package in Ubuntu: New Bug description: The boot on real HW (ARock B450, Ryzen, NVME 240Gb) takes a long time without any visible feedback. Video: https://photos.app.goo.gl/RmaLviXNorjeh5BP7 With grub debug: https://photos.app.goo.gl/PJuXdxp8uedr7fWp9 (google photos has degraded quality quite a bit, may upload the originals if too bad) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879290/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1521173] Re: AER: Corrected error received: id=00e0
"me too" - Dell Latitude w/ a Dell WD16 USB-C dock. After recent firmware updates it got significantly worse and nearly never properly re-attaches after suspend/resume. Dell 5400 Latitude: (0.1.9.1=same, 0.1.7.4=older, 0.1.6.5=older, 0.1.5.1=older, 0.1.4.2=older) dock: ``` No upgrades for RTS5413 in Dell dock, current is 01.21: 01.21=same No upgrades for RTS5487 in Dell dock, current is 01.47: 01.47=same No upgrades for WD19, current is 01.00.00.00: 01.00.00.00=same No upgrades for Package level of Dell dock, current is 01.00.04.01: 01.00.04.01=same No upgrades for VMM5331 in Dell dock, current is 05.03.10: 05.03.10=same ``` spammed by ``` [Tue Sep 15 18:50:06 2020] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 [Tue Sep 15 18:50:06 2020] pcieport :00:1d.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID) [Tue Sep 15 18:50:06 2020] pcieport :00:1d.0: device [8086:9db1] error status/mask=1000/2000 [Tue Sep 15 18:50:06 2020] pcieport :00:1d.0:[12] Timeout ``` ``` lspci -v | grep 9db1 00:1d.0 PCI bridge: Intel Corporation Device 9db1 (rev f0) (prog-if 00 [Normal decode]) ``` -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1521173 Title: AER: Corrected error received: id=00e0 Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: WORKAROUND: add pci=noaer to your kernel command line: 1) edit /etc/default/grub and and add pci=noaer to the line starting with GRUB_CMDLINE_LINUX_DEFAULT. It will look like this: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=noaer" 2) run "sudo update-grub" 3) reboot My dmesg gets completely spammed with the following messages appearing over and over again. It stops after one s3 cycle; it only happens after reboot. [ 5315.986588] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5315.987249] pcieport :00:1c.0: can't find device of ID00e0 [ 5315.995632] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5315.995664] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5315.995674] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5315.995683] pcieport :00:1c.0:[ 0] Receiver Error [ 5316.002772] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5316.002811] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5316.002826] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5316.002838] pcieport :00:1c.0:[ 0] Receiver Error [ 5316.009926] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5316.009964] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5316.009979] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5316.009991] pcieport :00:1c.0:[ 0] Receiver Error ProblemType: BugDistroRelease: Ubuntu 16.04 Package: linux-image-4.2.0-19-generic 4.2.0-19.23 [modified: boot/vmlinuz-4.2.0-19-generic] ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: david 1502 F...m pulseaudio /dev/snd/controlC0: david 1502 F pulseaudio CurrentDesktop: Unity Date: Mon Nov 30 13:19:00 2015 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=fe528b90-b4eb-4a20-82bd-6a03b79cfb14 InstallationDate: Installed on 2015-11-28 (2 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127) MachineType: Dell Inc. Inspiron 13-7359 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic.efi.signed root=UUID=94d54f88-5d18-4e2b-960a-8717d6e618bb ro noprompt persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-19-generic N/A linux-backports-modules-4.2.0-19-generic N/A linux-firmware1.153SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.00.00 dmi.board.name: 0NT3WX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.00.00:bd08/07/2015:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0NT3WX:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 13-7359 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go t
[Kernel-packages] [Bug 1862559] Re: ubuntu 19.10: unresponsive/freezes on ThunderX2 if system is idle for ~22min
Thank you for reporting this bug to Ubuntu. Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Changed in: gdm3 (Ubuntu) Status: New => Incomplete ** Bug watch removed: gitlab.gnome.org/GNOME/gnome-control-center/issues #22 https://gitlab.gnome.org/GNOME/gnome-control-center/issues/22 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1862559 Title: ubuntu 19.10: unresponsive/freezes on ThunderX2 if system is idle for ~22min Status in gdm3 package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: UBUNTU 19.10 installed on ThunderX2 saber ARM64 machine. If the system left idle for ~22min it becomes unresponsive. The system will not take any inputs like from UART, ping ..etc. The system will completely freeze and we need to hard reset the system. It could be possible the system goes to hibernate state and could not able to come out of the state. Dmesg log when system halts/no response on Saber boards (TX2) Ubuntu 19.10 ubuntu ttyAMA0 ubuntu login: ubuntu Password: Last login: Wed Jan 29 20:08:22 PST 2020 on ttyAMA0 Welcome to Ubuntu 19.10 (GNU/Linux 5.3.0-26-generic aarch64) * Documentation: https://help.ubuntu.com * Management: https://landscape.canonical.com * Support:https://ubuntu.com/advantage ubuntu@ubuntu:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 19.10 Release: 19.10 Codename: eoan [ +0.732512] audit: type=1400 audit(1580358920.412:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="lsb_release" pid=3087 comm="apparmor_parser" [ +0.64] audit: type=1400 audit(1580358920.412:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/ippusbxd" pid=3091 comm="apparmor_parser" [ +0.000168] audit: type=1400 audit(1580358920.412:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe" pid=3086 comm="apparmor_parser" [ +0.05] audit: type=1400 audit(1580358920.412:5): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe//kmod" pid=3086 comm="apparmor_parser" [ +0.000546] audit: type=1400 audit(1580358920.412:6): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/man" pid=3085 comm="apparmor_parser" [ +0.06] audit: type=1400 audit(1580358920.412:7): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_filter" pid=3085 comm="apparmor_parser" [ +0.05] audit: type=1400 audit(1580358920.412:8): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_groff" pid=3085 comm="apparmor_parser" [ +0.000854] audit: type=1400 audit(1580358920.412:9): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=3089 comm="apparmor_parser" [ +0.002667] audit: type=1400 audit(1580358920.416:10): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=3093 comm="apparmor_parser" [ +0.04] audit: type=1400 audit(1580358920.416:11): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=3093 comm="apparmor_parser" [ +1.382579] igb :92:00.1 enp146s0f1: igb: enp146s0f1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX [ +0.000299] IPv6: ADDRCONF(NETDEV_CHANGE): enp146s0f1: link becomes ready [ +3.131173] mpt3sas_cm0: port enable: SUCCESS [Jan29 20:36] random: crng init done [ +0.04] random: 7 urandom warning(s) missed due to ratelimiting *[Jan29 20:37] rfkill: input handler disabled* *[Jan29 20:57] PM: suspend entry (deep)* To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1862559/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855757] Re: [nvidia] Background image corrupted after standby or resume from suspend
Yes that's related and will need a similar fix, but different. Please open a new bug for that. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1855757 Title: [nvidia] Background image corrupted after standby or resume from suspend Status in mutter package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-390 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-435 package in Ubuntu: Won't Fix Status in mutter source package in Focal: Triaged Status in nvidia-graphics-drivers-340 source package in Focal: Won't Fix Status in nvidia-graphics-drivers-390 source package in Focal: Won't Fix Status in nvidia-graphics-drivers-435 source package in Focal: Won't Fix Bug description: Looks similar to https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1809407 When the computer goes to standby, the background image becomes corrupted. I am able to fix by "killall Xorg" , change the background image (settings > background) and restart. Haven't tried login logout. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.107 Thu May 24 21:54:01 PDT 2018 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Dec 9 10:58:35 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.107, 5.3.0-23-generic, x86_64: installed nvidia-340, 340.107, 5.3.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GT215M [GeForce GTS 360M] [10de:0cb1] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GT215M [GeForce GTS 360M] [1043:203c] InstallationDate: Installed on 2019-11-29 (10 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUSTek Computer Inc. G60JX ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=65117975-c95f-4406-a7cf-da912cda0e70 ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G60JX dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: PEGATRON Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr204:bd12/25/2009:svnASUSTekComputerInc.:pnG60JX:pvr1.0:rvnPEGATRONCORPORATION:rnG60JX:rvr1.0:cvnPEGATRONComputerInc.:ct10:cvr1.0: dmi.product.family: PEGA Family dmi.product.name: G60JX dmi.product.sku: 0 dmi.product.version: 1.0 dmi.sys.vendor: ASUSTek Computer Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1855757/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Legion 15 82GR, known as Legion R7000P2020H 82GR in China has the same issue. Device id is MSFT0001:00 04F3:3186 Touchpad. See full hardware info at https://linux-hardware.org/index.php?probe=dae1221cfd. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in Pop!_OS: New Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Status in linux package in Arch Linux: Confirmed Status in linux package in Fedora: Confirmed Status in linux package in openSUSE: New Bug description: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 20:14:25 2020 InstallationDate: Installed on 2020-07-02 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN19WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05 dmi.modalias: dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05: dmi.product.family: Legion 5 15ARH05 dmi.product.name: 82B5 dmi.product.sku: LENOVO_MT_82B5_B
[Kernel-packages] [Bug 1892860] Re: af_alg07 in crypto / cve-2019-8912 in cve from ubuntu_ltp failed on B-arm64
Still affecting AWS 4.15.0-1083.87 ARM64 (passed on AMD64)
** Tags added: sru-20200831
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1892860
Title:
af_alg07 in crypto / cve-2019-8912 in cve from ubuntu_ltp failed on
B-arm64
Status in ubuntu-kernel-tests:
New
Status in linux package in Ubuntu:
Incomplete
Bug description:
Issue found on 4.15.0-114.115-generic with ARM64 node appleton-kernel
and wright-kernel.
Looks like this is a new test case added 13 days ago:
https://github.com/linux-test-project/ltp/commit/fdff6139e43aa9b19f27907f6d7f2cb4765632a1#diff-8a83d6b2c6c7d74e750e3af47e3f4a79
The test will fail with:
startup='Fri Aug 14 10:13:27 2020'
tst_test.c:1247: INFO: Timeout per run is 0h 05m 00s
tst_taint.c:88: CONF: Ignoring already set kernel warning taint
../../../include/tst_fuzzy_sync.h:507: INFO: Minimum sampling period ended
../../../include/tst_fuzzy_sync.h:331: INFO: loop = 1024, delay_bias = 0
../../../include/tst_fuzzy_sync.h:320: INFO: start_a - start_b: { avg =
-2259470ns, avg_dev = 13695382ns, dev_ratio = 6.06 }
../../../include/tst_fuzzy_sync.h:320: INFO: end_a - start_a : { avg =
13968ns, avg_dev = 4310ns, dev_ratio = 0.31 }
../../../include/tst_fuzzy_sync.h:320: INFO: end_b - start_b : { avg =
15975ns, avg_dev = 50ns, dev_ratio = 0.00 }
../../../include/tst_fuzzy_sync.h:320: INFO: end_a - end_b : { avg =
-2261477ns, avg_dev = 13699742ns, dev_ratio = 6.06 }
../../../include/tst_fuzzy_sync.h:320: INFO: spins : { avg = 3575095 ,
avg_dev = 4553 , dev_ratio = 0.00 }
../../../include/tst_fuzzy_sync.h:637: INFO: Exceeded execution time,
requesting exit
af_alg07.c:97: FAIL: fchownat() failed to fail, kernel may be vulnerable
HINT: You _MAY_ be missing kernel fixes, see:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9060cb719e61
HINT: You _MAY_ be vulnerable to CVE(s), see:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-8912
Summary:
passed 0
failed 1
skipped 1
warnings 0
tag=af_alg07 stime=159747 dur=150 exit=exited stat=33 core=no cu=15051
cs=0
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1892860/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895669] Re: Add more support to Lenovo ThinkStation P620
debdiff for focal ** Patch added: "alsa-ucm-conf_1.2.2-1ubuntu0.4.debdiff" https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1895669/+attachment/5411202/+files/alsa-ucm-conf_1.2.2-1ubuntu0.4.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1895669 Title: Add more support to Lenovo ThinkStation P620 Status in HWE Next: New Status in alsa-ucm-conf package in Ubuntu: New Status in alsa-ucm-conf source package in Focal: New Status in alsa-ucm-conf source package in Groovy: New Bug description: [Impact] After upgrading the audio device firmware and doing more testing, we found some new audio issue on Lenovo P620: 1) Rear mic doesn't work. 2) Front and rear mic/line-in don't use hardware gain to control capture volume. [Fix] For 1), add proper PCM stream assignment to the rear microphone. For 2), add MixerElem to let alsa-lib and PulseAudio to pick correct mixer to change HW gain. [Test] With the new UCM applied, rear mic starts to work, and PulseAudio can control the hardware gain. [Regression Potential] The system hasn't hit the market so there's no chance to regression any system in the wild. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1895669/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1893778] Re: [UBUNTU 20.04] zPCI device hot-plug during boot may result in unusable device
** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1893778 Title: [UBUNTU 20.04] zPCI device hot-plug during boot may result in unusable device Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Released Bug description: SRU Justification: == [Impact] * If a PCI device (incl. virtio-pci) is hot-plugged during boot-up on s390x, it can be detected as an entry in CLP List PCI functions and via the hot-plug event. * (This is basically equivalent to boot time probing on other architectures.) * In such a case the hot-plug event will be stale, but Linux still tries to add and enable the device which leads to: * a) a duplicate entry in zPCI internal device list * b) an attempt to enable the device with a stale function handle * In case b) the device will be placed in error state which makes it unusable. [Fix] * b76fee1bc56c31a9d2a49592810eba30cc06d61a b76fee1bc56c "s390/pci: ignore stale configuration request event" [Test Case] * Setup an Ubuntu Server 20.04 (focal) Linux operating system on an IBM Z or LinuxONE III LPAR. * It's now easiest to test on KVM using virtio-pci (on s390x). * Start a test virtual machine: sudo virsh start * Attach and hotplug a virtio-pci device: sudo virsh attach-device hotplug_pci_block.xml * Where hotplug_pci_block.xml looks like: [Regression Potential] * The regression risk is moderate, since the modification is very limited and therefore manageable (additional if statement - two lines of code) and easily testable on KVM using virtio-pci. * The changes are in the zPCI event code, so in worst-case it can happen that the event handling get harmed which may break zPCI entirely, affecting all PCI devices incl. virtio-pci (on s390x). * A bug in PCI 'availability' handling also just lead to wrong states of PCI devices which make them unavailable, hence unusable. * Notice that zPCI is the s390x-specific PCI implementation, modifications here do not affect any other architecture. * And zPCI devices are less wide-spread compared to ccw devices on s390x. * On top a test kernel was build and made available for further testing atesting can be easily done with virtio-pci on KVM. [Other] * The fix/patch got upstream accepted with kernel v5.9-rc2. * But it landed already in groovy's proposed kernel 5.8 (Ubuntu-5.8.0-18.19), due to 'Groovy update: v5.8.4 upstream stable release' that is handled in LP 1893048. * Hence this fix/patch need to be applied to focal only. __ When a PCI device (including virtio-pci for which this is easiest to test) is hot-plugged while Linux is still booting, it can be detected as an entry in CLP List PCI Functions (basically equivalent to boot time probing on other architectures) and with the hot-plug event. In this case the hot-plug event will be stale but Linux still tried to add and enable the device leading a) to a duplicate entry in zPCI internal device list b) an attempt to enable the device witha stale function handle Part b) would lead to the device being place in the error state and make it unusable. This can most easily be reproduced using KVM and doing # sudo virsh start myguest && sudo virsh attach-device myguest hotplug_pci_block.xml Where hotplug_pci_block.xml looks like the following: The problem is fixed with the 3-line upstream commit b76fee1bc56c31a9d2a49592810eba30cc06d61a s390/pci: ignore stale configuration request event I also confirmed that as of the focal tag Ubuntu-5.4.0-46.50 this cherry-picks cleanly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1893778/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895174] Re: Focal update: v5.4.62 upstream stable release
** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1895174 Title: Focal update: v5.4.62 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.62 upstream stable release from git://git.kernel.org/ binfmt_flat: revert "binfmt_flat: don't offset the data start" gre6: Fix reception with IP6_TNL_F_RCV_DSCP_COPY net: Fix potential wrong skb->protocol in skb_vlan_untag() net: nexthop: don't allow empty NHA_GROUP net: qrtr: fix usage of idr in port assignment to socket net: sctp: Fix negotiation of the number of data streams. net/smc: Prevent kernel-infoleak in __smc_diag_dump() tipc: fix uninit skb->data in tipc_nl_compat_dumpit() net: ena: Make missed_tx stat incremental net/sched: act_ct: Fix skb double-free in tcf_ct_handle_fragments() error flow ipvlan: fix device features ALSA: pci: delete repeated words in comments ALSA: hda/realtek: Fix pin default on Intel NUC 8 Rugged ASoC: img: Fix a reference count leak in img_i2s_in_set_fmt ASoC: img-parallel-out: Fix a reference count leak ASoC: tegra: Fix reference count leaks. mfd: intel-lpss: Add Intel Emmitsburg PCH PCI IDs arm64: dts: qcom: msm8916: Pull down PDM GPIOs during sleep powerpc/xive: Ignore kmemleak false positives media: pci: ttpci: av7110: fix possible buffer overflow caused by bad DMA value in debiirq() blktrace: ensure our debugfs dir exists scsi: target: tcmu: Fix crash on ARM during cmd completion mfd: intel-lpss: Add Intel Tiger Lake PCH-H PCI IDs iommu/iova: Don't BUG on invalid PFNs drm/amdkfd: Fix reference count leaks. drm/radeon: fix multiple reference count leak drm/amdgpu: fix ref count leak in amdgpu_driver_open_kms drm/amd/display: fix ref count leak in amdgpu_drm_ioctl drm/amdgpu: fix ref count leak in amdgpu_display_crtc_set_config drm/amdgpu/display: fix ref count leak when pm_runtime_get_sync fails scsi: lpfc: Fix shost refcount mismatch when deleting vport xfs: Don't allow logging of XFS_ISTALE inodes scsi: target: Fix xcopy sess release leak selftests/powerpc: Purge extra count_pmc() calls of ebb selftests f2fs: fix error path in do_recover_data() omapfb: fix multiple reference count leaks due to pm_runtime_get_sync PCI: Fix pci_create_slot() reference count leak ARM: dts: ls1021a: output PPS signal on FIPER2 rtlwifi: rtl8192cu: Prevent leaking urb mips/vdso: Fix resource leaks in genvdso.c cec-api: prevent leaking memory through hole in structure HID: quirks: add NOGET quirk for Logitech GROUP f2fs: fix use-after-free issue drm/nouveau/drm/noveau: fix reference count leak in nouveau_fbcon_open drm/nouveau: fix reference count leak in nv50_disp_atomic_commit drm/nouveau: Fix reference count leak in nouveau_connector_detect locking/lockdep: Fix overflow in presentation of average lock-time btrfs: file: reserve qgroup space after the hole punch range is locked btrfs: make btrfs_qgroup_check_reserved_leak take btrfs_inode scsi: iscsi: Do not put host in iscsi_set_flashnode_param() ceph: fix potential mdsc use-after-free crash ceph: do not access the kiocb after aio requests scsi: fcoe: Memory leak fix in fcoe_sysfs_fcf_del() EDAC/ie31200: Fallback if host bridge device is already initialized hugetlbfs: prevent filesystem stacking of hugetlbfs media: davinci: vpif_capture: fix potential double free KVM: arm64: Fix symbol dependency in __hyp_call_panic_nvhe powerpc/spufs: add CONFIG_COREDUMP dependency USB: sisusbvga: Fix a potential UB casued by left shifting a negative value brcmfmac: Set timeout value when configuring power save efi: provide empty efi_enter_virtual_mode implementation arm64: Fix __cpu_logical_map undefined issue Revert "ath10k: fix DMA related firmware crashes on multiple devices" sched/uclamp: Protect uclamp fast path code with static key sched/uclamp: Fix a deadlock when enabling uclamp static key usb: cdns3: gadget: always zeroed TRB buffer when enable endpoint PM / devfreq: rk3399_dmc: Add missing of_node_put() PM / devfreq: rk3399_dmc: Disable devfreq-event device when fails PM / devfreq: rk3399_dmc: Fix kernel oops when rockchip,pmu is absent drm/xen: fix passing zero to 'PTR_ERR' warning drm/xen-front: Fix misuse
[Kernel-packages] [Bug 1887829] Re: graphic card not working
[Expired for nvidia-graphics-drivers-340 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: nvidia-graphics-drivers-340 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1887829 Title: graphic card not working Status in nvidia-graphics-drivers-340 package in Ubuntu: Expired Status in nvidia-graphics-drivers-390 package in Ubuntu: Invalid Bug description: graphic card not working properly so I have to switch to custom graphic driver |If i use nvidia driver the system freezes after few minutes ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jul 16 22:06:22 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 390.138, 5.4.0-40-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G98 [GeForce 8400 GS Rev. 2] [10de:06e4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. G98 [GeForce 8400 GS Rev. 2] [1043:8322] InstallationDate: Installed on 2020-07-15 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=2f89e325-7cba-46e0-8714-d8d6cbab9ff2 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2009 dmi.bios.vendor: Intel Corp. dmi.bios.version: TCIBX10H.86A.0027.2009.1119.1517 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH55TC dmi.board.vendor: Intel Corporation dmi.board.version: AAE70932-206 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrTCIBX10H.86A.0027.2009.1119.1517:bd11/19/2009:svn:pn:pvr:rvnIntelCorporation:rnDH55TC:rvrAAE70932-206:cvn:ct3:cvr: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1887829/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888023] Re: Please ship apparmor features files
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1888023 Title: Please ship apparmor features files Status in linux package in Ubuntu: Expired Bug description: To allow prebuilding apparmor profiles during cloud-images build, the chroot where cloud-image is created need access to the /sys/kernel/security/apparmor/features of the target kernel. It would be nice, if kernels were booted, that file stored, and installed in the linux-image package for every kernel we ship. This way we can precreate binary cached apparmor profiles during image build time speeding up first boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888023/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884910] Re: Very slow boot with kernel 5.4.0-37-generic
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884910 Title: Very slow boot with kernel 5.4.0-37-generic Status in linux package in Ubuntu: Expired Bug description: Booting on Lubuntu 20.04LTS is very slow when using kernel 5.4.0-37-generic, but OK with 5.4.0-33-generic.Delay seems to be due to this or similar error messages which are repeated many times before timing out. [ 62.776599] snd_hda_intel :00:0e.0: No response from codec, disabling MSI: last cmd=0x20bf8100 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ianb 2420 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: LXQt DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-12-06 (200 days ago) InstallationMedia: Lubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017.1) MachineType: Chillblast WAP PRO Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=cae501ec-3727-4d42-8fbb-d21cdb1dd5a5 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux-backports-modules-5.4.0-37-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True dmi.bios.date: 08/15/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GB3V35 dmi.board.asset.tag: Default string dmi.board.name: GB3 dmi.board.vendor: IP3 Tech dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: IP3 dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGB3V35:bd08/15/2019:svnChillblast:pnWAPPRO:pvrDefaultstring:rvnIP3Tech:rnGB3:rvrDefaultstring:cvnIP3:ct35:cvrDefaultstring: dmi.product.family: Mini PC dmi.product.name: WAP PRO dmi.product.sku: CBFUSWAPPRO dmi.product.version: Default string dmi.sys.vendor: Chillblast To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884910/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825636] Re: Battery drain during sleep. System suspended before kernel suspends all tasks
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1825636 Title: Battery drain during sleep. System suspended before kernel suspends all tasks Status in linux package in Ubuntu: Expired Bug description: Description: Ubuntu 18.04.2 LTS Release: 18.04 Expected behaviour: No battery drain during suspend. Ubuntu 18.04 running on a Thinkpad L390 has battery drain during suspend (~10% in 5 hours) in. I excluded wake ups during sleep and checking the logs I have realized that the kernel suspends too fast, before the full system is put to sleep. Here are the syslogs after initiating the suspend mode: Apr 19 11:59:53 ThinkPad-L390 systemd[1]: Starting TLP suspend/resume... Apr 19 11:59:53 ThinkPad-L390 systemd[1]: Started TLP suspend/resume. Apr 19 11:59:53 ThinkPad-L390 systemd[1]: Reached target Sleep. Apr 19 11:59:53 ThinkPad-L390 systemd[1]: Starting Suspend... Apr 19 11:59:53 ThinkPad-L390 kernel: [15459.897941] PM: suspend entry (deep) Apr 19 11:59:53 ThinkPad-L390 systemd-sleep[28261]: Suspending system... Apr 19 11:59:53 ThinkPad-L390 kernel: [15459.897944] PM: Syncing filesystems ... done. And here the syslogs directly after waking up: Apr 19 12:37:50 ThinkPad-L390 kernel: [15459.906928] Freezing user space processes ... (elapsed 0.004 seconds) done. Apr 19 12:37:50 ThinkPad-L390 kernel: [15459.910995] OOM killer disabled. Apr 19 12:37:50 ThinkPad-L390 kernel: [15459.910996] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. Apr 19 12:37:50 ThinkPad-L390 kernel: [15459.912868] Suspending console(s) (use no_console_suspend to debug) Apr 19 12:37:50 ThinkPad-L390 kernel: [15460.032873] e1000e: EEE TX LPI TIMER: 0011 Apr 19 12:37:50 ThinkPad-L390 kernel: [15460.204567] ACPI: EC: interrupt blocked Apr 19 12:37:50 ThinkPad-L390 kernel: [15460.243401] ACPI: Preparing to enter system sleep state S3 Apr 19 12:37:50 ThinkPad-L390 kernel: [15460.249397] ACPI: EC: event blocked Apr 19 12:37:50 ThinkPad-L390 kernel: [15460.249398] ACPI: EC: EC stopped Apr 19 12:37:50 ThinkPad-L390 kernel: [15460.249399] PM: Saving platform NVS memory Apr 19 12:37:50 ThinkPad-L390 kernel: [15460.249432] Disabling non-boot CPUs ... Apr 19 12:37:50 ThinkPad-L390 kernel: [15460.263401] irq_migrate_all_off_this_cpu: 5 callbacks suppressed Apr 19 12:37:50 ThinkPad-L390 kernel: [15460.263403] IRQ 141: no longer affine to CPU1 Apr 19 12:37:50 ThinkPad-L390 kernel: [15460.264445] smpboot: CPU 1 is now offline Apr 19 12:37:50 ThinkPad-L390 kernel: [15460.296469] smpboot: CPU 2 is now offline Apr 19 12:37:50 ThinkPad-L390 kernel: [15460.320478] smpboot: CPU 3 is now offline Apr 19 12:37:50 ThinkPad-L390 kernel: [15460.343319] IRQ 149: no longer affine to CPU4 Apr 19 12:37:50 ThinkPad-L390 kernel: [15460.345025] smpboot: CPU 4 is now offline Apr 19 12:37:50 ThinkPad-L390 kernel: [15460.375279] IRQ 17: no longer affine to CPU5 Apr 19 12:37:50 ThinkPad-L390 kernel: [15460.375285] IRQ 18: no longer affine to CPU5 Apr 19 12:37:50 ThinkPad-L390 kernel: [15460.375298] IRQ 148: no longer affine to CPU5 Apr 19 12:37:50 ThinkPad-L390 kernel: [15460.376311] smpboot: CPU 5 is now offline Apr 19 12:37:50 ThinkPad-L390 kernel: [15460.399234] IRQ 124: no longer affine to CPU6 Apr 19 12:37:50 ThinkPad-L390 kernel: [15460.400265] smpboot: CPU 6 is now offline Apr 19 12:37:50 ThinkPad-L390 kernel: [15460.423211] IRQ 123: no longer affine to CPU7 Apr 19 12:37:50 ThinkPad-L390 kernel: [15460.423222] IRQ 139: no longer affine to CPU7 Apr 19 12:37:50 ThinkPad-L390 kernel: [15460.423228] IRQ 140: no longer affine to CPU7 Apr 19 12:37:50 ThinkPad-L390 kernel: [15460.423235] IRQ 142: no longer affine to CPU7 Apr 19 12:37:50 ThinkPad-L390 kernel: [15460.424278] smpboot: CPU 7 is now offline Apr 19 12:37:50 ThinkPad-L390 kernel: [15460.428456] ACPI: Low-level resume complete Apr 19 12:37:50 ThinkPad-L390 kernel: [15460.428541] ACPI: EC: EC started Apr 19 12:37:50 ThinkPad-L390 kernel: [15460.428541] PM: Restoring platform NVS memory Apr 19 12:37:50 ThinkPad-L390 kernel: [15460.429356] Enabling non-boot CPUs ... Apr 19 12:37:50 ThinkPad-L390 kernel: [15460.429403] x86: Booting SMP configuration: Apr 19 12:37:50 ThinkPad-L390 kernel: [15460.429404] smpboot: Booting Node 0 Processor 1 APIC 0x2 Apr 19 12:37:50 ThinkPad-L390 kernel: [15460.429761] cache: parent cpu1 should not be sleeping Apr 19 12:37:50 ThinkPad-L390 kernel: [15460.429898] CPU1 is up Apr 19 12:37:50 ThinkPad-L390 kernel: [15460.429929] smpboot: Booting Node 0 Processor 2 APIC 0x4 Apr 19 12:37:50 ThinkPad-L390 kernel: [15460.430294] cache: parent cpu2 should not be sle
[Kernel-packages] [Bug 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration
Seeing similar problems on Xenial and I suspect it's similar to the problems occurring with Bionic and Focal: http://autopkgtest.ubuntu.com/packages/s/systemd/xenial/amd64 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1892358 Title: autopkgtest success rate dropped inhibiting proposed migration Status in build-essential package in Ubuntu: Invalid Status in glib2.0 package in Ubuntu: Invalid Status in iputils package in Ubuntu: Invalid Status in kbd package in Ubuntu: Invalid Status in linux-meta package in Ubuntu: Invalid Status in ntpsec package in Ubuntu: Invalid Status in qemu package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in util-linux package in Ubuntu: Invalid Status in linux-meta source package in Bionic: New Status in systemd source package in Bionic: New Status in build-essential source package in Focal: Confirmed Status in linux-meta source package in Focal: New Status in qemu source package in Focal: Confirmed Status in systemd source package in Focal: Confirmed Status in util-linux source package in Focal: Confirmed Bug description: Hi, we had such cases in the past like bug 1817721 for bionic and maybe bug 1892130 is about the same as well. There were more but I didn't want to search for all of them - what I checked is that there are no open ones clearly pointing out the recent further drop in already flaky subtests. In particular the tests "tests-in-lxd" and "systemd-fsckd" were known to be flaky before, but got even worse. Here stats of the last 40 runs, it might be a coincidences that this is after 246-2ubuntu1 landed. Could as well be any other change groovy amd64 tests-in-lxd (F 42% S 0% B 10% => P 45%/) BFFFBFF.B.F.F...FBF build-login(F 0% S 0% B 10% => P 87%/) B...B...BB. unit-config(F 0% S 0% B 10% => P 87%/) B...B...BB. networkd-testpy(F 0% S 0% B 10% => P 87%/) B...B...BB. boot-and-services (F 0% S 0% B 10% => P 87%/) B...B...BB. boot-smoke (F 0% S 0% B 10% => P 87%/) B...B...BB. logind (F 0% S 0% B 10% => P 87%/) B...B...BB. storage(F 0% S 0% B 10% => P 87%/) B...B...BB. upstream (F 35% S 0% B 10% => P 52%/) ..FFB.FFF.FFBFF.B.F.F..FFBF udev (F 0% S 0% B 10% => P 87%/) B...B...BB. systemd-fsckd (F 37% S 0% B 10% => P 50%/) BFFFB.FF...FB.F..B. root-unittests (F 0% S 0% B 10% => P 87%/) B...B...BB. ppc64el tests-in-lxd (F 25% S 0% B 0% => P 75%/) FFFFF.F. systemd-fsckd (F 35% S 0% B 0% => P 65%/) FFF...FFFFF.F..F root-unittests (F 2% S 0% B 0% => P 97%/) ..F. s390x tests-in-lxd (F 52% S 0% B 0% => P 47%/) FFF.FFF.FF....F. timedated (F 2% S 0% B 0% => P 97%/) ...F upstream (F 17% S 0% B 0% => P 82%/) .F..F.F.FFF...F. systemd-fsckd (F 32% S 0% B 0% => P 67%/) FFF..FF..F.FF..F root-unittests (F 10% S 0% B 0% => P 90%/) FFF...F. arm64 tests-in-lxd (F 40% S 0% B 2% => P 57%/) F.B...FFF.FF..F..F.FFF.F logind (F 2% S 0% B 2% => P 95%/) ..B...F. upstream (F 22% S 0% B 2% => P 75%/) ...F.FB.F.F.F..FFF.F root-unittests (F 12% S 0% B 2% => P 85%/) ..B.F...F.FF...F (I'm sure LP will make this unreadable, but is is nice in monospace) Whatever the root cause is - the success rate of these has reduced so much that the (even formerly questionable) practice of retry-until- success won't work anymore. I have run the two tests in a local VM and systemd-fsckd works there while tests-in-lxd seems to trip over the old flaky fellow being "boot-and-services". We had the discussion in the past, but I think I need to again bring up the suggestion to skip "tests-in-lxd" and "systemd-fsckd" until they are on reasonable success rates. To manage notifications about this bug go to: ht
[Kernel-packages] [Bug 1891454] Re: [UBUNTU 20.04] kernel: s390/cpum_cf, perf: changeDFLT_CCERROR counter name
** Changed in: linux (Ubuntu Bionic)
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/1891454
Title:
[UBUNTU 20.04] kernel: s390/cpum_cf,perf: changeDFLT_CCERROR counter
name
Status in Ubuntu on IBM z Systems:
In Progress
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Groovy:
Fix Committed
Bug description:
SRU Justification:
==
[Impact]
* Change the counter name DLFT_CCERROR to DLFT_CCFINISH on IBM z15 to
avoid confusion.
* This counter counts completed DEFLATE instructions with exit code 0,
1 or 2.
* And since exit code 0 means success and exit code 1 or 2 indicate
errors the name can be ambiguous.
[Fix]
* Rename s390 z15 counter named DFLT_CCERROR to DFLT_CCFINISH.
* Backport Focal: https://launchpadlibrarian.net/493272507/0001-s390
-cpum_cf-perf-change-DFLT_CCERROR-counter-name.patch
* Backport Bionic:
https://launchpadlibrarian.net/493439681/u18-0001-s390-cpum_cf-Add-
new-extended-counters-for-IBM-z15.patch
[Test Case]
* Enable hardware counters in the activation profile of a z15 LPAR.
* Just check the countername in sysfs with: ls
/sys/devices/cpum_cf/events/{DFLT_CCERROR,DFLT_CCFINISH}
[Regression Potential]
* The regression potential can be considered as low, since:
* Counters like these are usually not activated by default and need to
be explicitly enabled.
* No code functionality is changed with that patch, only a renaming is
done at 3 places in one code file
arch/s390/kernel/perf_cpum_cf_events.c as well as in /tools/perf/pmu-
events/arch/s390/cf_z15/extended.json.
* The fix got already upstream accepted in 5.8-rc7, hence it got
upstream reviewed,
* and the modifications are limited to s390x, are only relevant for
the z15 / LinuxONE III hw generation that are relatively new.
* Issue with the renaming I can think of are that people don't know
about the new name and may look for the old one and don't find it
anymore,
* and with that also if the old counter name is used in scripts or
applications, these may fails due to an unknown counter name.
[Other Info]
* The backports are based on commit
3d3af181d370069861a3be94608464e2ff3682e2 ("s390/cpum_cf,perf: change
DFLT_CCERROR counter name") that is upstream accepted since v5.8-rc7.
* Hence this SRU is not requested for groovy, since it's already in groovys
kernel 5.8 in proposed, but only requested for focal and bionic.
__
Description: kernel: s390/cpum_cf,perf: change DFLT_CCERROR counter name
Symptom: Counter name CCERROR is misleading.
Problem: Change the counter name DLFT_CCERROR to DLFT_CCFINISH on
IBM z15. This counter counts completed DEFLATE instructions
with exit code 0, 1 or 2. Since exit code 0 means success
and exit code 1 or 2 indicate errors, change the counter
name to avoid confusion. This counter is incremented each
time the DEFLATE instruction completed regardless if an
error was detected or not.
Solution: Rename s390 z15 counter named DFLT_CCERROR to DFLT_CCFINISH
Reproduction: Command # ls /sys/devices/cpum_cf/events/DFLT_CCERROR
currently succeeds. After this patch has been applied the
command does not work anymore. The file does not exist
anymore. Use command
# ls /sys/devices/cpum_cf/events/DFLT_CCFINISH
instead.
Upstream-ID: 5ce1a24dd98c00a57a8fa13660648abf7e08e3ef
Component: kernel 5.8
Will be integrated into 20.10 by kernel 5.8 integration.
Backport available for 20.04.
To be checked for 18.04 and 16.04, update will be provided
Here is the backported patch.
The upstream commit id is 3d3af181d370069861a3be94608464e2ff3682e2
("s390/cpum_cf,perf: change DFLT_CCERROR counter name")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1891454/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1893778] Re: [UBUNTU 20.04] zPCI device hot-plug during boot may result in unusable device
** Changed in: ubuntu-z-systems 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/1893778 Title: [UBUNTU 20.04] zPCI device hot-plug during boot may result in unusable device Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Released Bug description: SRU Justification: == [Impact] * If a PCI device (incl. virtio-pci) is hot-plugged during boot-up on s390x, it can be detected as an entry in CLP List PCI functions and via the hot-plug event. * (This is basically equivalent to boot time probing on other architectures.) * In such a case the hot-plug event will be stale, but Linux still tries to add and enable the device which leads to: * a) a duplicate entry in zPCI internal device list * b) an attempt to enable the device with a stale function handle * In case b) the device will be placed in error state which makes it unusable. [Fix] * b76fee1bc56c31a9d2a49592810eba30cc06d61a b76fee1bc56c "s390/pci: ignore stale configuration request event" [Test Case] * Setup an Ubuntu Server 20.04 (focal) Linux operating system on an IBM Z or LinuxONE III LPAR. * It's now easiest to test on KVM using virtio-pci (on s390x). * Start a test virtual machine: sudo virsh start * Attach and hotplug a virtio-pci device: sudo virsh attach-device hotplug_pci_block.xml * Where hotplug_pci_block.xml looks like: [Regression Potential] * The regression risk is moderate, since the modification is very limited and therefore manageable (additional if statement - two lines of code) and easily testable on KVM using virtio-pci. * The changes are in the zPCI event code, so in worst-case it can happen that the event handling get harmed which may break zPCI entirely, affecting all PCI devices incl. virtio-pci (on s390x). * A bug in PCI 'availability' handling also just lead to wrong states of PCI devices which make them unavailable, hence unusable. * Notice that zPCI is the s390x-specific PCI implementation, modifications here do not affect any other architecture. * And zPCI devices are less wide-spread compared to ccw devices on s390x. * On top a test kernel was build and made available for further testing atesting can be easily done with virtio-pci on KVM. [Other] * The fix/patch got upstream accepted with kernel v5.9-rc2. * But it landed already in groovy's proposed kernel 5.8 (Ubuntu-5.8.0-18.19), due to 'Groovy update: v5.8.4 upstream stable release' that is handled in LP 1893048. * Hence this fix/patch need to be applied to focal only. __ When a PCI device (including virtio-pci for which this is easiest to test) is hot-plugged while Linux is still booting, it can be detected as an entry in CLP List PCI Functions (basically equivalent to boot time probing on other architectures) and with the hot-plug event. In this case the hot-plug event will be stale but Linux still tried to add and enable the device leading a) to a duplicate entry in zPCI internal device list b) an attempt to enable the device witha stale function handle Part b) would lead to the device being place in the error state and make it unusable. This can most easily be reproduced using KVM and doing # sudo virsh start myguest && sudo virsh attach-device myguest hotplug_pci_block.xml Where hotplug_pci_block.xml looks like the following: The problem is fixed with the 3-line upstream commit b76fee1bc56c31a9d2a49592810eba30cc06d61a s390/pci: ignore stale configuration request event I also confirmed that as of the focal tag Ubuntu-5.4.0-46.50 this cherry-picks cleanly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1893778/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1891454] Re: [UBUNTU 20.04] kernel: s390/cpum_cf, perf: changeDFLT_CCERROR counter name
** Changed in: ubuntu-z-systems
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/1891454
Title:
[UBUNTU 20.04] kernel: s390/cpum_cf,perf: changeDFLT_CCERROR counter
name
Status in Ubuntu on IBM z Systems:
Fix Committed
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Groovy:
Fix Committed
Bug description:
SRU Justification:
==
[Impact]
* Change the counter name DLFT_CCERROR to DLFT_CCFINISH on IBM z15 to
avoid confusion.
* This counter counts completed DEFLATE instructions with exit code 0,
1 or 2.
* And since exit code 0 means success and exit code 1 or 2 indicate
errors the name can be ambiguous.
[Fix]
* Rename s390 z15 counter named DFLT_CCERROR to DFLT_CCFINISH.
* Backport Focal: https://launchpadlibrarian.net/493272507/0001-s390
-cpum_cf-perf-change-DFLT_CCERROR-counter-name.patch
* Backport Bionic:
https://launchpadlibrarian.net/493439681/u18-0001-s390-cpum_cf-Add-
new-extended-counters-for-IBM-z15.patch
[Test Case]
* Enable hardware counters in the activation profile of a z15 LPAR.
* Just check the countername in sysfs with: ls
/sys/devices/cpum_cf/events/{DFLT_CCERROR,DFLT_CCFINISH}
[Regression Potential]
* The regression potential can be considered as low, since:
* Counters like these are usually not activated by default and need to
be explicitly enabled.
* No code functionality is changed with that patch, only a renaming is
done at 3 places in one code file
arch/s390/kernel/perf_cpum_cf_events.c as well as in /tools/perf/pmu-
events/arch/s390/cf_z15/extended.json.
* The fix got already upstream accepted in 5.8-rc7, hence it got
upstream reviewed,
* and the modifications are limited to s390x, are only relevant for
the z15 / LinuxONE III hw generation that are relatively new.
* Issue with the renaming I can think of are that people don't know
about the new name and may look for the old one and don't find it
anymore,
* and with that also if the old counter name is used in scripts or
applications, these may fails due to an unknown counter name.
[Other Info]
* The backports are based on commit
3d3af181d370069861a3be94608464e2ff3682e2 ("s390/cpum_cf,perf: change
DFLT_CCERROR counter name") that is upstream accepted since v5.8-rc7.
* Hence this SRU is not requested for groovy, since it's already in groovys
kernel 5.8 in proposed, but only requested for focal and bionic.
__
Description: kernel: s390/cpum_cf,perf: change DFLT_CCERROR counter name
Symptom: Counter name CCERROR is misleading.
Problem: Change the counter name DLFT_CCERROR to DLFT_CCFINISH on
IBM z15. This counter counts completed DEFLATE instructions
with exit code 0, 1 or 2. Since exit code 0 means success
and exit code 1 or 2 indicate errors, change the counter
name to avoid confusion. This counter is incremented each
time the DEFLATE instruction completed regardless if an
error was detected or not.
Solution: Rename s390 z15 counter named DFLT_CCERROR to DFLT_CCFINISH
Reproduction: Command # ls /sys/devices/cpum_cf/events/DFLT_CCERROR
currently succeeds. After this patch has been applied the
command does not work anymore. The file does not exist
anymore. Use command
# ls /sys/devices/cpum_cf/events/DFLT_CCFINISH
instead.
Upstream-ID: 5ce1a24dd98c00a57a8fa13660648abf7e08e3ef
Component: kernel 5.8
Will be integrated into 20.10 by kernel 5.8 integration.
Backport available for 20.04.
To be checked for 18.04 and 16.04, update will be provided
Here is the backported patch.
The upstream commit id is 3d3af181d370069861a3be94608464e2ff3682e2
("s390/cpum_cf,perf: change DFLT_CCERROR counter name")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1891454/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888202] Re: package zfsutils-linux 0.8.3-1ubuntu12.1 failed to install/upgrade: installed zfsutils-linux package post-installation script subprocess returned error exit status
This bug appears every time I upgrade. I'm using zfs exclusively. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1888202 Title: package zfsutils-linux 0.8.3-1ubuntu12.1 failed to install/upgrade: installed zfsutils-linux package post-installation script subprocess returned error exit status 1 Status in zfs-linux package in Ubuntu: Won't Fix Bug description: the upgrade process assumes ZFS-utils is not configured and has exit code 1 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: zfsutils-linux 0.8.3-1ubuntu12.1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 AptOrdering: gir1.2-webkit2-4.0:amd64: Install gir1.2-javascriptcoregtk-4.0:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Jul 20 10:22:00 2020 ErrorMessage: installed zfsutils-linux package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2016-05-15 (1526 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: zfs-linux Title: package zfsutils-linux 0.8.3-1ubuntu12.1 failed to install/upgrade: installed zfsutils-linux package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-05-24 (56 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1888202/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1893897] Re: [Regression] Do not initiate shutdown for EPOW_SHUTDOWN_ON_UPS event
** Changed in: linux (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Groovy) Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: linux (Ubuntu Groovy) Assignee: Canonical Kernel Team (canonical-kernel-team) => (unassigned) ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1893897 Title: [Regression] Do not initiate shutdown for EPOW_SHUTDOWN_ON_UPS event Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Groovy: Fix Released Bug description: SRU Justification: [Impact] * With commit 79872e35469b "powerpc/pseries: All events of EPOW_SYSTEM_SHUTDOWN must initiate shutdown" it was introduced that all EPOW_SYSTEM_SHUTDOWN events cause immediate shutdowns. * But on LPARs there is a user space tool (rtas_errd) that monitor for EPOW_SHUTDOWN_ON_UPS events. * Once rtas_errd gets an event it initiates a shutdown after predefined time. * Therefore immediate shutdowns must not be triggered if the system is running on UPS (means for EPOW_SHUTDOWN_ON_UPS events). [Fix] * 90a9b102eddf6a3f987d15f4454e26a2532c1c98 90a9b102eddf "powerpc/pseries: Do not initiate shutdown when system is running on UPS" [Test Case] * Setup a Power system on (D)LPAR and run it on UPS with Ubuntu 16.04 or higher (kernel 4.x is needed). * Verify that the user space tool (rtas_errd) is active and running. * Define a time for a potential shutdown in case an EPOW_SHUTDOWN_ON_UPS event occurs. * Trigger an EPOW_SHUTDOWN_ON_UPS event. * Verify if the system got shutdown immediately - or after the pre- defined time. [Regression Potential] * The regression risk is very low, because of the very limited modification in a case statement for EPOW_SHUTDOWN_ON_UPS events. * What may happen is that the system doesn't power off anymore if running on UPS due to the EPOW_SHUTDOWN_ON_UPS case changes - especially if there is a potential problem with rtas_errd that should monitor for these events and should initiate the delayed shutdown. * Other than that I cannot see much potential harm. [Other] * The patch got upstream accepted in v5.9-rc2 and already landed in groovy's kernel 'Ubuntu-5.8.0-18.19', based on the v5.8.4 upstream stable release ticket LP 1893048. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1893897/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1893248] Re: Xenial update: v4.4.234 upstream stable release
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1893248
Title:
Xenial update: v4.4.234 upstream stable release
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Xenial:
Fix Committed
Bug description:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v4.4.234 upstream stable release
from git://git.kernel.org/
cxl: Fix kobject memleak
UBUNTU: upstream stable to v4.4.233
drm/imx: imx-ldb: Disable both channels for split mode in enc->disable()
perf probe: Fix memory leakage when the probe point is not found
net/compat: Add missing sock updates for SCM_RIGHTS
watchdog: f71808e_wdt: indicate WDIOF_CARDRESET support in
watchdog_info.options
watchdog: f71808e_wdt: remove use of wrong watchdog_info option
coredump: fix race condition between collapse_huge_page() and core dumping
khugepaged: khugepaged_test_exit() check mmget_still_valid()
khugepaged: adjust VM_BUG_ON_MM() in __khugepaged_enter()
btrfs: export helpers for subvolume name/id resolution
btrfs: don't show full path of bind mounts in subvol=
romfs: fix uninitialized memory leak in romfs_dev_read()
mm: include CMA pages in lowmem_reserve at boot
mm, page_alloc: fix core hung in free_pcppages_bulk()
ext4: clean up ext4_match() and callers
ext4: fix checking of directory entry validity for inline directories
media: budget-core: Improve exception handling in budget_register()
media: vpss: clean up resources in init
Input: psmouse - add a newline when printing 'proto' by sysfs
m68knommu: fix overwriting of bits in ColdFire V3 cache control
xfs: fix inode quota reservation checks
jffs2: fix UAF problem
scsi: libfc: Free skb in fc_disc_gpn_id_resp() for valid cases
virtio_ring: Avoid loop when vq is broken in virtqueue_poll
xfs: Fix UBSAN null-ptr-deref in xfs_sysfs_init
alpha: fix annotation of io{read,write}{16,32}be()
ext4: fix potential negative array index in do_split()
ASoC: intel: Fix memleak in sst_media_open
powerpc: Allow 4224 bytes of stack expansion for the signal frame
epoll: Keep a reference on files added to the check list
do_epoll_ctl(): clean the failure exits up a bit
mm/hugetlb: fix calculation of adjust_range_if_pmd_sharing_possible
xen: don't reschedule in preemption off sections
omapfb: dss: Fix max fclk divider for omap36xx
KVM: arm/arm64: Don't reschedule in unmap_stage2_range()
Linux 4.4.234
UBUNTU: upstream stable to v4.4.234
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893248/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1892546] Re: Novalink (mkvterm command failure)
** Changed in: linux (Ubuntu Groovy) Status: New => In Progress ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Xenial) Status: New => In Progress ** Changed in: ubuntu-power-systems Status: Triaged => In Progress ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1892546 Title: Novalink (mkvterm command failure) Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Groovy: In Progress Bug description: SRU Justification: [Impact] * drmgr command is failing while trying to open console for IBMi on PowerVM LPAR [Fix] * 63ffcbdad738 "tty: hvcs: Don't NULL tty->driver_data until hvcs_cleanup()" [Test Case] * Create a VM from PowerVC on a Novalink managed host. * Unmanage and manage the VM, this problem gets reproduced. * grep the logs for "drmgr" [Regression Potential] The regression can be considered as very low, since: * limited to the IBM Hypervisor Virtual Console Server. * patched kernel where shared and successfully tested by IBM. * the worse case, if the cleanup is broken a new opened connection might break. [Other] * The patch got upstream accepted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1892546/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867428] Re: /dev/vcsm-cma missing on Ubuntu 18.04.4 aarch64
@ahb can you verify that this works now with a recent bionic image? Bionic is using the 5.4 kernel now. -- 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/1867428 Title: /dev/vcsm-cma missing on Ubuntu 18.04.4 aarch64 Status in linux-raspi2 package in Ubuntu: New Status in linux-raspi2 source package in Bionic: New Bug description: On fully upgraded Ubuntu 18.04 aarch64 the vc_sm_cma kernel module does not expose /dev/vcsm-cma, thus application working with the Raspberry Pi Camera, e.g. raspivid, do not work properly. $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.4 LTS Release:18.04 Codename: bionic Test with both linux-image-5.3.0-1017-raspi2 and linux- image-5.3.0-1018-raspi2 in combination with with https://github.com/raspberrypi/userland at 6e6a2c859a17a195fbb6a97c9da584dd2b9b0178 compiled using ./buildme --aarch64 on Raspberry Pi 4 and 3+. Everything works, if I use a recent Raspbian kernel on the Ubuntu image: Copy RASPBIAN/boot/kernel8.img to UBUNTU/boot/firmware/vmlinuz, RASPBIAN/boot/bcm2711-rpi-4-b.dtb to UBUNTU/boot/firmware/ and RASPBIAN/lib/modules/4.19.97-v8+ to UBUNTU/lib/modules. I cannot tell whether the problem is specific to the 5.3.0 kernel compiled for Ubuntu or a general issue with the 5.3.0 kernel as the Raspbian kernel is still based on 4.19. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1867428/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895725] Re: Wifi adapter missing
Please run `sudo apt install bcmwl-kernel-source`. ** Tags added: hwe-networking-wifi ** Summary changed: - Wifi adapter missing + Broadcom BCM43142 802.11b/g/n [14e4:4365] Subsystem [103c:804a] Wifi adapter missing ** 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/1895725 Title: Broadcom BCM43142 802.11b/g/n [14e4:4365] Subsystem [103c:804a] Wifi adapter missing Status in linux package in Ubuntu: Invalid Bug description: No wifiadater found on HP G246, Ubuntu 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-47-generic 5.4.0-47.51 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mtnai 1901 F pulseaudio /dev/snd/controlC0: mtnai 1901 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Sep 16 00:54:51 2020 IwConfig: enp1s0no wireless extensions. lono wireless extensions. usb0 no wireless extensions. MachineType: HP HP 246 G4 Notebook PC ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic root=UUID=02f6b563-4d4c-48f8-a25a-c7adfabd9aba ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-47-generic N/A linux-backports-modules-5.4.0-47-generic N/A linux-firmware1.187.3 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/13/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.1A dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80BC dmi.board.vendor: HP dmi.board.version: KBC Version 94.10 dmi.chassis.asset.tag: 5CG6060NKW dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.1A:bd10/13/2015:svnHP:pnHP246G4NotebookPC:pvrCNB1:rvnHP:rn80BC:rvrKBCVersion94.10:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5336AN G=N L=CON B=HP S=246 dmi.product.name: HP 246 G4 Notebook PC dmi.product.sku: N3S55PT#AB2 dmi.product.version: CNB1 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895725/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration
Focal test hint was accepted tonight and things moved there. @Kelsey - Steve denied the hint as a reset since recently a few results were good. Maybe you want to submit the same as force-badtest and bring it up like that for X&B? The results for xenial really look similarly bad ... xenial amd64 boot-and-services (F 45% f 0% S 0% B 5% => P 50%/) .FF...BFF.F. boot-smoke (F 80% f 0% S 0% B 5% => P 15%/) F.FF..BF systemd-fsckd (F 65% f 0% S 0% B 5% => P 30%/) FF.FFF.F..B.FF.F ppc64el no failures s390x no failures I know that ddstreet is considering the SRU updates for systemd to also mark those flaky. I'm still +1 to mark them force-badtest until then but I'm not the one to decide. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1892358 Title: autopkgtest success rate dropped inhibiting proposed migration Status in build-essential package in Ubuntu: Invalid Status in glib2.0 package in Ubuntu: Invalid Status in iputils package in Ubuntu: Invalid Status in kbd package in Ubuntu: Invalid Status in linux-meta package in Ubuntu: Invalid Status in ntpsec package in Ubuntu: Invalid Status in qemu package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in util-linux package in Ubuntu: Invalid Status in linux-meta source package in Bionic: New Status in systemd source package in Bionic: New Status in build-essential source package in Focal: Confirmed Status in linux-meta source package in Focal: New Status in qemu source package in Focal: Confirmed Status in systemd source package in Focal: Confirmed Status in util-linux source package in Focal: Confirmed Bug description: Hi, we had such cases in the past like bug 1817721 for bionic and maybe bug 1892130 is about the same as well. There were more but I didn't want to search for all of them - what I checked is that there are no open ones clearly pointing out the recent further drop in already flaky subtests. In particular the tests "tests-in-lxd" and "systemd-fsckd" were known to be flaky before, but got even worse. Here stats of the last 40 runs, it might be a coincidences that this is after 246-2ubuntu1 landed. Could as well be any other change groovy amd64 tests-in-lxd (F 42% S 0% B 10% => P 45%/) BFFFBFF.B.F.F...FBF build-login(F 0% S 0% B 10% => P 87%/) B...B...BB. unit-config(F 0% S 0% B 10% => P 87%/) B...B...BB. networkd-testpy(F 0% S 0% B 10% => P 87%/) B...B...BB. boot-and-services (F 0% S 0% B 10% => P 87%/) B...B...BB. boot-smoke (F 0% S 0% B 10% => P 87%/) B...B...BB. logind (F 0% S 0% B 10% => P 87%/) B...B...BB. storage(F 0% S 0% B 10% => P 87%/) B...B...BB. upstream (F 35% S 0% B 10% => P 52%/) ..FFB.FFF.FFBFF.B.F.F..FFBF udev (F 0% S 0% B 10% => P 87%/) B...B...BB. systemd-fsckd (F 37% S 0% B 10% => P 50%/) BFFFB.FF...FB.F..B. root-unittests (F 0% S 0% B 10% => P 87%/) B...B...BB. ppc64el tests-in-lxd (F 25% S 0% B 0% => P 75%/) FFFFF.F. systemd-fsckd (F 35% S 0% B 0% => P 65%/) FFF...FFFFF.F..F root-unittests (F 2% S 0% B 0% => P 97%/) ..F. s390x tests-in-lxd (F 52% S 0% B 0% => P 47%/) FFF.FFF.FF....F. timedated (F 2% S 0% B 0% => P 97%/) ...F upstream (F 17% S 0% B 0% => P 82%/) .F..F.F.FFF...F. systemd-fsckd (F 32% S 0% B 0% => P 67%/) FFF..FF..F.FF..F root-unittests (F 10% S 0% B 0% => P 90%/) FFF...F. arm64 tests-in-lxd (F 40% S 0% B 2% => P 57%/) F.B...FFF.FF..F..F.FFF.F logind (F 2% S 0% B 2% => P 95%/) ..B...F. upstream (F 22% S 0% B 2% => P 75%/) ...F.FB.F.F.F..FFF.F root-unittests (F 12% S 0% B 2% => P 85%/) ..B.F...F.FF...F
[Kernel-packages] [Bug 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration
The problem with Xenial is that there it isn't just flaky "systemd- fsckd" much more seems to be broken. I'll revise my Bionic MP, but for Xenial I'd like to hear from ddstreet/rbalint how they think we should go on there ... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1892358 Title: autopkgtest success rate dropped inhibiting proposed migration Status in build-essential package in Ubuntu: Invalid Status in glib2.0 package in Ubuntu: Invalid Status in iputils package in Ubuntu: Invalid Status in kbd package in Ubuntu: Invalid Status in linux-meta package in Ubuntu: Invalid Status in ntpsec package in Ubuntu: Invalid Status in qemu package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in util-linux package in Ubuntu: Invalid Status in linux-meta source package in Bionic: New Status in systemd source package in Bionic: New Status in build-essential source package in Focal: Confirmed Status in linux-meta source package in Focal: New Status in qemu source package in Focal: Confirmed Status in systemd source package in Focal: Confirmed Status in util-linux source package in Focal: Confirmed Bug description: Hi, we had such cases in the past like bug 1817721 for bionic and maybe bug 1892130 is about the same as well. There were more but I didn't want to search for all of them - what I checked is that there are no open ones clearly pointing out the recent further drop in already flaky subtests. In particular the tests "tests-in-lxd" and "systemd-fsckd" were known to be flaky before, but got even worse. Here stats of the last 40 runs, it might be a coincidences that this is after 246-2ubuntu1 landed. Could as well be any other change groovy amd64 tests-in-lxd (F 42% S 0% B 10% => P 45%/) BFFFBFF.B.F.F...FBF build-login(F 0% S 0% B 10% => P 87%/) B...B...BB. unit-config(F 0% S 0% B 10% => P 87%/) B...B...BB. networkd-testpy(F 0% S 0% B 10% => P 87%/) B...B...BB. boot-and-services (F 0% S 0% B 10% => P 87%/) B...B...BB. boot-smoke (F 0% S 0% B 10% => P 87%/) B...B...BB. logind (F 0% S 0% B 10% => P 87%/) B...B...BB. storage(F 0% S 0% B 10% => P 87%/) B...B...BB. upstream (F 35% S 0% B 10% => P 52%/) ..FFB.FFF.FFBFF.B.F.F..FFBF udev (F 0% S 0% B 10% => P 87%/) B...B...BB. systemd-fsckd (F 37% S 0% B 10% => P 50%/) BFFFB.FF...FB.F..B. root-unittests (F 0% S 0% B 10% => P 87%/) B...B...BB. ppc64el tests-in-lxd (F 25% S 0% B 0% => P 75%/) FFFFF.F. systemd-fsckd (F 35% S 0% B 0% => P 65%/) FFF...FFFFF.F..F root-unittests (F 2% S 0% B 0% => P 97%/) ..F. s390x tests-in-lxd (F 52% S 0% B 0% => P 47%/) FFF.FFF.FF....F. timedated (F 2% S 0% B 0% => P 97%/) ...F upstream (F 17% S 0% B 0% => P 82%/) .F..F.F.FFF...F. systemd-fsckd (F 32% S 0% B 0% => P 67%/) FFF..FF..F.FF..F root-unittests (F 10% S 0% B 0% => P 90%/) FFF...F. arm64 tests-in-lxd (F 40% S 0% B 2% => P 57%/) F.B...FFF.FF..F..F.FFF.F logind (F 2% S 0% B 2% => P 95%/) ..B...F. upstream (F 22% S 0% B 2% => P 75%/) ...F.FB.F.F.F..FFF.F root-unittests (F 12% S 0% B 2% => P 85%/) ..B.F...F.FF...F (I'm sure LP will make this unreadable, but is is nice in monospace) Whatever the root cause is - the success rate of these has reduced so much that the (even formerly questionable) practice of retry-until- success won't work anymore. I have run the two tests in a local VM and systemd-fsckd works there while tests-in-lxd seems to trip over the old flaky fellow being "boot-and-services". We had the discussion in the past, but I think I need to again bring up the suggestion to skip "tests-in-lxd" and "systemd-fsckd" until they are on reasonable success ra
[Kernel-packages] [Bug 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration
And on Bionic we only need to do so for amd64&i386. Here is a new MP for Bionic: https://code.launchpad.net/~paelzer/britney/hints-ubuntu-bionic-disable-systemd-v2/+merge/390793 ** Branch linked: lp:~paelzer/britney/hints-ubuntu-bionic-disable- systemd-v2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1892358 Title: autopkgtest success rate dropped inhibiting proposed migration Status in build-essential package in Ubuntu: Invalid Status in glib2.0 package in Ubuntu: Invalid Status in iputils package in Ubuntu: Invalid Status in kbd package in Ubuntu: Invalid Status in linux-meta package in Ubuntu: Invalid Status in ntpsec package in Ubuntu: Invalid Status in qemu package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in util-linux package in Ubuntu: Invalid Status in linux-meta source package in Bionic: New Status in systemd source package in Bionic: New Status in build-essential source package in Focal: Confirmed Status in linux-meta source package in Focal: New Status in qemu source package in Focal: Confirmed Status in systemd source package in Focal: Confirmed Status in util-linux source package in Focal: Confirmed Bug description: Hi, we had such cases in the past like bug 1817721 for bionic and maybe bug 1892130 is about the same as well. There were more but I didn't want to search for all of them - what I checked is that there are no open ones clearly pointing out the recent further drop in already flaky subtests. In particular the tests "tests-in-lxd" and "systemd-fsckd" were known to be flaky before, but got even worse. Here stats of the last 40 runs, it might be a coincidences that this is after 246-2ubuntu1 landed. Could as well be any other change groovy amd64 tests-in-lxd (F 42% S 0% B 10% => P 45%/) BFFFBFF.B.F.F...FBF build-login(F 0% S 0% B 10% => P 87%/) B...B...BB. unit-config(F 0% S 0% B 10% => P 87%/) B...B...BB. networkd-testpy(F 0% S 0% B 10% => P 87%/) B...B...BB. boot-and-services (F 0% S 0% B 10% => P 87%/) B...B...BB. boot-smoke (F 0% S 0% B 10% => P 87%/) B...B...BB. logind (F 0% S 0% B 10% => P 87%/) B...B...BB. storage(F 0% S 0% B 10% => P 87%/) B...B...BB. upstream (F 35% S 0% B 10% => P 52%/) ..FFB.FFF.FFBFF.B.F.F..FFBF udev (F 0% S 0% B 10% => P 87%/) B...B...BB. systemd-fsckd (F 37% S 0% B 10% => P 50%/) BFFFB.FF...FB.F..B. root-unittests (F 0% S 0% B 10% => P 87%/) B...B...BB. ppc64el tests-in-lxd (F 25% S 0% B 0% => P 75%/) FFFFF.F. systemd-fsckd (F 35% S 0% B 0% => P 65%/) FFF...FFFFF.F..F root-unittests (F 2% S 0% B 0% => P 97%/) ..F. s390x tests-in-lxd (F 52% S 0% B 0% => P 47%/) FFF.FFF.FF....F. timedated (F 2% S 0% B 0% => P 97%/) ...F upstream (F 17% S 0% B 0% => P 82%/) .F..F.F.FFF...F. systemd-fsckd (F 32% S 0% B 0% => P 67%/) FFF..FF..F.FF..F root-unittests (F 10% S 0% B 0% => P 90%/) FFF...F. arm64 tests-in-lxd (F 40% S 0% B 2% => P 57%/) F.B...FFF.FF..F..F.FFF.F logind (F 2% S 0% B 2% => P 95%/) ..B...F. upstream (F 22% S 0% B 2% => P 75%/) ...F.FB.F.F.F..FFF.F root-unittests (F 12% S 0% B 2% => P 85%/) ..B.F...F.FF...F (I'm sure LP will make this unreadable, but is is nice in monospace) Whatever the root cause is - the success rate of these has reduced so much that the (even formerly questionable) practice of retry-until- success won't work anymore. I have run the two tests in a local VM and systemd-fsckd works there while tests-in-lxd seems to trip over the old flaky fellow being "boot-and-services". We had the discussion in the past, but I think I need to again bring up the suggestion to skip "tests-in-lxd" and "systemd-fsckd" until th
[Kernel-packages] [Bug 1893752] Re: Get the right configuration according to the related field of dpcd
** Description changed: [Impact] + Connect the 4K@60Hz monitor on WD19, the monitor can't light. [Fix] + As per DP spec, at first check DP_EXTENDED_RECEIVER_CAP_FIELD_PRESENT. + If DP_EXTENDED_RECEIVER_CAP_FIELD_PRESENT is 1, read the DP_DP13_DPCD_REV to get the faster capability. If DP_EXTENDED_RECEIVER_CAP_FIELD_PRESENT is 0, read DP_DPCD_REV. [Test] + With the patches, connect 4K@60Hz monitor on WD19, the machine can output the video to the monitor and the monitor can light. [Regression] + low, Just get one more DPCD from the extended register, compare them and get the faster one. ** Summary changed: - Get the right configuration according to the related field of dpcd + Get the extended DPCD according to the related field in the DPCD registers. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1893752 Title: Get the extended DPCD according to the related field in the DPCD registers. Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.6 package in Ubuntu: New Status in linux source package in Focal: Incomplete Status in linux-oem-5.6 source package in Focal: New Status in linux source package in Groovy: Incomplete Status in linux-oem-5.6 source package in Groovy: New Bug description: [Impact] Connect the 4K@60Hz monitor on WD19, the monitor can't light. [Fix] As per DP spec, at first check DP_EXTENDED_RECEIVER_CAP_FIELD_PRESENT. If DP_EXTENDED_RECEIVER_CAP_FIELD_PRESENT is 1, read the DP_DP13_DPCD_REV to get the faster capability. If DP_EXTENDED_RECEIVER_CAP_FIELD_PRESENT is 0, read DP_DPCD_REV. [Test] With the patches, connect 4K@60Hz monitor on WD19, the machine can output the video to the monitor and the monitor can light. [Regression] low, Just get one more DPCD from the extended register, compare them and get the faster one. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1893752/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1893752] Re: Get the extended DPCD according to the related field in the DPCD registers.
** Tags added: oem-priority originate-from-1880831 somerville -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1893752 Title: Get the extended DPCD according to the related field in the DPCD registers. Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.6 package in Ubuntu: New Status in linux source package in Focal: Incomplete Status in linux-oem-5.6 source package in Focal: New Status in linux source package in Groovy: Incomplete Status in linux-oem-5.6 source package in Groovy: New Bug description: [Impact] Connect the 4K@60Hz monitor on WD19, the monitor can't light. [Fix] As per DP spec, at first check DP_EXTENDED_RECEIVER_CAP_FIELD_PRESENT. If DP_EXTENDED_RECEIVER_CAP_FIELD_PRESENT is 1, read the DP_DP13_DPCD_REV to get the faster capability. If DP_EXTENDED_RECEIVER_CAP_FIELD_PRESENT is 0, read DP_DPCD_REV. [Test] With the patches, connect 4K@60Hz monitor on WD19, the machine can output the video to the monitor and the monitor can light. [Regression] low, Just get one more DPCD from the extended register, compare them and get the faster one. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1893752/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
