[Kernel-packages] [Bug 1886775] [NEW] kernel 5.4.0-40 hangs system when using nfs home directories
Public bug reported: We use nfs mounted (using autofs), kerberos authenticated home directories for most users. Booting with kernel 5.4.0-40, users with nfs mounted home directories find the system freezes not long after use, somewhat randomly. Power off is then the only thing to do. Some specific things that caused crashes - opening a second tab on firefox; opening a terminal and running "cat" on log files, and running ubuntu-bug linux to try to generate this report :-( Sometimes before the crash just one window freezes, and the rest of the GUI is responsive. A full freeze usually occurs within several seconds. No such crashes were observed using an account without nfs mounted home directories (and the output from "ubuntu-bug linux" for one of these working users is at the end of this report). Reverting to 5.4.0-39, everything is good. Exactly the same behaviour is observed on a modern AMD Zen2 processor with a graphics card, and a several year old Intel processor with integrated graphics. Looking at /var/log/syslog there are several suspicious messages like the one below. The general protection fault occurs always just before the freeze, and occasionally some times before. Jul 4 16:23:37 emu kernel: [ 350.263903] [ cut here ] Jul 4 16:23:37 emu kernel: [ 350.263904] virt_to_cache: Object is not a Slab page! Jul 4 16:23:37 emu kernel: [ 350.263917] WARNING: CPU: 13 PID: 4009 at mm/slab.h:473 kmem_cache_free+0x237/0x2b0 Jul 4 16:23:37 emu kernel: [ 350.263917] Modules linked in: rfcomm rpcsec_gss_krb5 nfsv4 nfs fscache vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) edac_mce_amd kvm_amd xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c nf_tables nfnetlink ip6table_filter ip6_tables iptable_filter bpfilter cmac algif_hash algif_skcipher af_alg bnep snd_hda_codec_hdmi binfmt_misc nvidia_uvm(OE) kvm nvidia_drm(POE) nvidia_modeset(POE) iwlmvm snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_intel snd_intel_dspcfg snd_hda_codec nls_iso8859_1 snd_hda_core snd_hwdep snd_pcm btusb btrtl btbcm btintel snd_seq_midi mac80211 bluetooth snd_seq_midi_event crct10dif_pclmul snd_rawmidi bridge ecdh_generic stp ghash_clmulni_intel llc libarc4 input_leds joydev ecc nvidia(POE) snd_seq iwlwifi aesni_intel crypto_simd cryptd glue_helper drm_kms_helper snd_seq_device cfg80211 snd_timer ipmi_devintf Jul 4 16:23:37 emu kernel: [ 350.263952] wmi_bmof ipmi_msghandler snd fb_sys_fops syscopyarea sysfillrect sysimgblt soundcore k10temp ccp mac_hid sch_fq_codel parport_pc ppdev lp parport drm nfsd nfs_acl auth_rpcgss lockd grace sunrpc ip_tables x_tables autofs4 hid_generic usbhid hid crc32_pclmul igb i2c_piix4 ahci i2c_algo_bit nvme libahci dca nvme_core wmi Jul 4 16:23:37 emu kernel: [ 350.263971] CPU: 13 PID: 4009 Comm: kworker/u64:4 Tainted: P OE 5.4.0-40-generic #44-Ubuntu Jul 4 16:23:37 emu kernel: [ 350.263972] Hardware name: Gigabyte Technology Co., Ltd. X570 I AORUS PRO WIFI/X570 I AORUS PRO WIFI, BIOS F4h 07/17/2019 Jul 4 16:23:37 emu kernel: [ 350.263986] Workqueue: rpciod rpc_async_schedule [sunrpc] Jul 4 16:23:37 emu kernel: [ 350.263989] RIP: 0010:kmem_cache_free+0x237/0x2b0 Jul 4 16:23:37 emu kernel: [ 350.263990] Code: ff ff ff 80 3d 16 4f 56 01 00 0f 85 39 ff ff ff 48 c7 c6 20 44 67 86 48 c7 c7 08 25 98 86 c6 05 fb 4e 56 01 01 e8 64 8a df ff <0f> 0b e9 18 ff ff ff 48 8b 57 58 49 8b 4f 58 48 c7 c6 30 44 67 86 Jul 4 16:23:37 emu kernel: [ 350.263991] RSP: 0018:c1ebc3077d20 EFLAGS: 00010282 Jul 4 16:23:37 emu kernel: [ 350.263993] RAX: RBX: a040c01358e2 RCX: 0006 Jul 4 16:23:37 emu kernel: [ 350.263993] RDX: 0007 RSI: 0092 RDI: a040beb578c0 Jul 4 16:23:37 emu kernel: [ 350.263994] RBP: c1ebc3077d48 R08: 0506 R09: 0004 Jul 4 16:23:37 emu kernel: [ 350.263995] R10: R11: 0001 R12: a041401358e2 Jul 4 16:23:37 emu kernel: [ 350.263995] R13: R14: a040a7e47600 R15: a04065a99cb0 Jul 4 16:23:37 emu kernel: [ 350.263997] FS: () GS:a040beb4() knlGS: Jul 4 16:23:37 emu kernel: [ 350.263997] CS: 0010 DS: ES: CR0: 80050033 Jul 4 16:23:37 emu kernel: [ 350.263998] CR2: 7fe66802dfe0 CR3: 000717722000 CR4: 00340ee0 Jul 4 16:23:37 emu kernel: [ 350.263999] Call Trace: Jul 4 16:23:37 emu kernel: [ 350.264005] mempool_free_slab+0x17/0x20 Jul 4 16:23:37 emu kernel: [ 350.264007] mempool_free+0x2f/0x80 Jul 4 16:23:37 emu kernel: [ 350.264018] rpc_free+0x47/0x60 [sunrpc] Jul 4 16:23:37 emu kernel: [ 350.264028] xprt_release+0x91/0x1a0 [sunrpc] Jul 4 16:23:37 emu kernel: [ 350.264037] rpc_release_resources_task+0x13/0x50 [sunrp
[Kernel-packages] [Bug 1886775] 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 1886775 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1886775 Title: kernel 5.4.0-40 hangs system when using nfs home directories Status in linux package in Ubuntu: Incomplete Bug description: We use nfs mounted (using autofs), kerberos authenticated home directories for most users. Booting with kernel 5.4.0-40, users with nfs mounted home directories find the system freezes not long after use, somewhat randomly. Power off is then the only thing to do. Some specific things that caused crashes - opening a second tab on firefox; opening a terminal and running "cat" on log files, and running ubuntu-bug linux to try to generate this report :-( Sometimes before the crash just one window freezes, and the rest of the GUI is responsive. A full freeze usually occurs within several seconds. No such crashes were observed using an account without nfs mounted home directories (and the output from "ubuntu-bug linux" for one of these working users is at the end of this report). Reverting to 5.4.0-39, everything is good. Exactly the same behaviour is observed on a modern AMD Zen2 processor with a graphics card, and a several year old Intel processor with integrated graphics. Looking at /var/log/syslog there are several suspicious messages like the one below. The general protection fault occurs always just before the freeze, and occasionally some times before. Jul 4 16:23:37 emu kernel: [ 350.263903] [ cut here ] Jul 4 16:23:37 emu kernel: [ 350.263904] virt_to_cache: Object is not a Slab page! Jul 4 16:23:37 emu kernel: [ 350.263917] WARNING: CPU: 13 PID: 4009 at mm/slab.h:473 kmem_cache_free+0x237/0x2b0 Jul 4 16:23:37 emu kernel: [ 350.263917] Modules linked in: rfcomm rpcsec_gss_krb5 nfsv4 nfs fscache vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) edac_mce_amd kvm_amd xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c nf_tables nfnetlink ip6table_filter ip6_tables iptable_filter bpfilter cmac algif_hash algif_skcipher af_alg bnep snd_hda_codec_hdmi binfmt_misc nvidia_uvm(OE) kvm nvidia_drm(POE) nvidia_modeset(POE) iwlmvm snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_intel snd_intel_dspcfg snd_hda_codec nls_iso8859_1 snd_hda_core snd_hwdep snd_pcm btusb btrtl btbcm btintel snd_seq_midi mac80211 bluetooth snd_seq_midi_event crct10dif_pclmul snd_rawmidi bridge ecdh_generic stp ghash_clmulni_intel llc libarc4 input_leds joydev ecc nvidia(POE) snd_seq iwlwifi aesni_intel crypto_simd cryptd glue_helper drm_kms_helper snd_seq_device cfg80211 snd_timer ipmi_devintf Jul 4 16:23:37 emu kernel: [ 350.263952] wmi_bmof ipmi_msghandler snd fb_sys_fops syscopyarea sysfillrect sysimgblt soundcore k10temp ccp mac_hid sch_fq_codel parport_pc ppdev lp parport drm nfsd nfs_acl auth_rpcgss lockd grace sunrpc ip_tables x_tables autofs4 hid_generic usbhid hid crc32_pclmul igb i2c_piix4 ahci i2c_algo_bit nvme libahci dca nvme_core wmi Jul 4 16:23:37 emu kernel: [ 350.263971] CPU: 13 PID: 4009 Comm: kworker/u64:4 Tainted: P OE 5.4.0-40-generic #44-Ubuntu Jul 4 16:23:37 emu kernel: [ 350.263972] Hardware name: Gigabyte Technology Co., Ltd. X570 I AORUS PRO WIFI/X570 I AORUS PRO WIFI, BIOS F4h 07/17/2019 Jul 4 16:23:37 emu kernel: [ 350.263986] Workqueue: rpciod rpc_async_schedule [sunrpc] Jul 4 16:23:37 emu kernel: [ 350.263989] RIP: 0010:kmem_cache_free+0x237/0x2b0 Jul 4 16:23:37 emu kernel: [ 350.263990] Code: ff ff ff 80 3d 16 4f 56 01 00 0f 85 39 ff ff ff 48 c7 c6 20 44 67 86 48 c7 c7 08 25 98 86 c6 05 fb 4e 56 01 01 e8 64 8a df ff <0f> 0b e9 18 ff ff ff 48 8b 57 58 49 8b 4f 58 48 c7 c6 30 44 67 86 Jul 4 16:23:37 emu kernel: [ 350.263991] RSP: 0018:c1ebc3077d20 EFLAGS: 00010282 Jul 4 16:23:37 emu kernel: [ 350.263993] RAX: RBX: a040c01358e2 RCX: 0006 Jul 4 16:23:37 emu kernel: [ 350.263993] RDX: 0007 RSI: 0092 RDI: a040beb578c0 Jul 4 16:23:37 emu kernel: [ 350.263994] RBP: c1ebc3077d48 R08: 0506 R09: 0
[Kernel-packages] [Bug 1886769] 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 1886769 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/1886769 Title: [ 0.00] Initramfs unpacking failed: Decoding failed Status in grub2 package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in syslinux package in Ubuntu: New Bug description: Steps to reproduce: 1. Download MATE Groovy daily (sha256sum = 7d2fdad36b8fcf0409aa0a484755e5fc5ef3798fd256eeebbde905a71ad474b7 ) 2. Insert ISO into VirtualBox with EFI enabled 3. Boot VM Expected results: * VM boots normally Actual results: * VM hangs during early boot with message [ 0.00] Initramfs unpacking failed: Decoding failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1886769/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886775] Re: kernel 5.4.0-40 hangs system when using nfs home directories
Possible duplicate of lp: #1886277? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1886775 Title: kernel 5.4.0-40 hangs system when using nfs home directories Status in linux package in Ubuntu: Incomplete Bug description: We use nfs mounted (using autofs), kerberos authenticated home directories for most users. Booting with kernel 5.4.0-40, users with nfs mounted home directories find the system freezes not long after use, somewhat randomly. Power off is then the only thing to do. Some specific things that caused crashes - opening a second tab on firefox; opening a terminal and running "cat" on log files, and running ubuntu-bug linux to try to generate this report :-( Sometimes before the crash just one window freezes, and the rest of the GUI is responsive. A full freeze usually occurs within several seconds. No such crashes were observed using an account without nfs mounted home directories (and the output from "ubuntu-bug linux" for one of these working users is at the end of this report). Reverting to 5.4.0-39, everything is good. Exactly the same behaviour is observed on a modern AMD Zen2 processor with a graphics card, and a several year old Intel processor with integrated graphics. Looking at /var/log/syslog there are several suspicious messages like the one below. The general protection fault occurs always just before the freeze, and occasionally some times before. Jul 4 16:23:37 emu kernel: [ 350.263903] [ cut here ] Jul 4 16:23:37 emu kernel: [ 350.263904] virt_to_cache: Object is not a Slab page! Jul 4 16:23:37 emu kernel: [ 350.263917] WARNING: CPU: 13 PID: 4009 at mm/slab.h:473 kmem_cache_free+0x237/0x2b0 Jul 4 16:23:37 emu kernel: [ 350.263917] Modules linked in: rfcomm rpcsec_gss_krb5 nfsv4 nfs fscache vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) edac_mce_amd kvm_amd xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c nf_tables nfnetlink ip6table_filter ip6_tables iptable_filter bpfilter cmac algif_hash algif_skcipher af_alg bnep snd_hda_codec_hdmi binfmt_misc nvidia_uvm(OE) kvm nvidia_drm(POE) nvidia_modeset(POE) iwlmvm snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_intel snd_intel_dspcfg snd_hda_codec nls_iso8859_1 snd_hda_core snd_hwdep snd_pcm btusb btrtl btbcm btintel snd_seq_midi mac80211 bluetooth snd_seq_midi_event crct10dif_pclmul snd_rawmidi bridge ecdh_generic stp ghash_clmulni_intel llc libarc4 input_leds joydev ecc nvidia(POE) snd_seq iwlwifi aesni_intel crypto_simd cryptd glue_helper drm_kms_helper snd_seq_device cfg80211 snd_timer ipmi_devintf Jul 4 16:23:37 emu kernel: [ 350.263952] wmi_bmof ipmi_msghandler snd fb_sys_fops syscopyarea sysfillrect sysimgblt soundcore k10temp ccp mac_hid sch_fq_codel parport_pc ppdev lp parport drm nfsd nfs_acl auth_rpcgss lockd grace sunrpc ip_tables x_tables autofs4 hid_generic usbhid hid crc32_pclmul igb i2c_piix4 ahci i2c_algo_bit nvme libahci dca nvme_core wmi Jul 4 16:23:37 emu kernel: [ 350.263971] CPU: 13 PID: 4009 Comm: kworker/u64:4 Tainted: P OE 5.4.0-40-generic #44-Ubuntu Jul 4 16:23:37 emu kernel: [ 350.263972] Hardware name: Gigabyte Technology Co., Ltd. X570 I AORUS PRO WIFI/X570 I AORUS PRO WIFI, BIOS F4h 07/17/2019 Jul 4 16:23:37 emu kernel: [ 350.263986] Workqueue: rpciod rpc_async_schedule [sunrpc] Jul 4 16:23:37 emu kernel: [ 350.263989] RIP: 0010:kmem_cache_free+0x237/0x2b0 Jul 4 16:23:37 emu kernel: [ 350.263990] Code: ff ff ff 80 3d 16 4f 56 01 00 0f 85 39 ff ff ff 48 c7 c6 20 44 67 86 48 c7 c7 08 25 98 86 c6 05 fb 4e 56 01 01 e8 64 8a df ff <0f> 0b e9 18 ff ff ff 48 8b 57 58 49 8b 4f 58 48 c7 c6 30 44 67 86 Jul 4 16:23:37 emu kernel: [ 350.263991] RSP: 0018:c1ebc3077d20 EFLAGS: 00010282 Jul 4 16:23:37 emu kernel: [ 350.263993] RAX: RBX: a040c01358e2 RCX: 0006 Jul 4 16:23:37 emu kernel: [ 350.263993] RDX: 0007 RSI: 0092 RDI: a040beb578c0 Jul 4 16:23:37 emu kernel: [ 350.263994] RBP: c1ebc3077d48 R08: 0506 R09: 0004 Jul 4 16:23:37 emu kernel: [ 350.263995] R10: R11: 0001 R12: a041401358e2 Jul 4 16:23:37 emu kernel: [ 350.263995] R13: R14: a040a7e47600 R15: a04065a99cb0 Jul 4 16:23:37 emu kernel: [ 350.263997] FS: () GS:a040beb4() knlGS: Jul 4 16:23:37 emu kernel: [ 350.263997] CS: 0010 DS: ES: CR0: 80050033 Jul 4 16:23:37 emu kernel: [ 350.263998] CR2: 7fe66802dfe0 CR3: 000717722000 CR4: 00340ee0 Jul 4 16:23:37 emu kernel: [
[Kernel-packages] [Bug 1883511] Re: High load from process irq/65-i2c-INT3 - kernel module tps6598x
Ok, please raise the issues to the following recipient via email: Heikki Krogerus (maintainer:USB TYPEC CLASS) Greg Kroah-Hartman (supporter:USB SUBSYSTEM) linux-...@vger.kernel.org (open list:USB TYPEC CLASS) linux-ker...@vger.kernel.org (open list) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1883511 Title: High load from process irq/65-i2c-INT3 - kernel module tps6598x Status in linux package in Ubuntu: Incomplete Bug description: There seems to be an issue with the kernel module tps6598x which puts the CPU on a high load: https://forums.intel.com/s/question/0D50P4fWnUeSAK/nuc10i3-irq- problem As soon as the module is unloaded, cpu load is back to normal. According to a post in the link above the issue is the following: "My guess is that the IRQ resource is not correct for the PD controller causing you to see irq flood. The problem is that the ACPI device entry (the node) on this platform has 4 I2CSerialBus resources and 4 IRQ resources. The idea is that the single ACPI device entry can represent up to 4 USB PD controllers. The problem is that there is no way to know which IRQ resource belongs to which I2CSerialBus resource :-(. Andy, this is one of those multi-instantiate I2C slave devices with HID INT3515. The only solution I can think of is that we start maintaining DMI quirk table in drivers/platform/x86/i2c-multi-instantiate.c where we supply the correct i2c to irq resource mapping for every platform that has this device(s)." Description: Ubuntu 20.04 LTS Release: 20.04 Hardware: Intel NUC10i5FNK ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-37-generic 5.4.0-37.41 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-37-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: pass Date: Mon Jun 15 11:04:57 2020 InstallationDate: Installed on 2020-04-26 (49 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Intel(R) Client Systems NUC10i5FNK ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-37-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux-backports-modules-5.4.0-37-generic N/A linux-firmware1.187 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2020 dmi.bios.vendor: Intel Corp. dmi.bios.version: FNCML357.0041.2020.0518.1045 dmi.board.asset.tag: Default string dmi.board.name: NUC10i5FNB dmi.board.vendor: Intel Corporation dmi.board.version: K61361-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.0041.2020.0518.1045:bd05/18/2020:svnIntel(R)ClientSystems:pnNUC10i5FNK:pvrK61339-302:rvnIntelCorporation:rnNUC10i5FNB:rvrK61361-302:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: FN dmi.product.name: NUC10i5FNK dmi.product.sku: BXNUC10i5FNK dmi.product.version: K61339-302 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883511/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886769] Re: [ 0.000000] Initramfs unpacking failed: Decoding failed
@Ubuntu Kernel Bot (ubuntu-kernel-bot) It is impossible, system hung on boot. ** 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/1886769 Title: [ 0.00] Initramfs unpacking failed: Decoding failed Status in grub2 package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in syslinux package in Ubuntu: New Bug description: Steps to reproduce: 1. Download MATE Groovy daily (sha256sum = 7d2fdad36b8fcf0409aa0a484755e5fc5ef3798fd256eeebbde905a71ad474b7 ) 2. Insert ISO into VirtualBox with EFI enabled 3. Boot VM Expected results: * VM boots normally Actual results: * VM hangs during early boot with message [ 0.00] Initramfs unpacking failed: Decoding failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1886769/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853665] Re: Realtek RTL8821CE [10ec:c821] Subsystem [103c:831a] Bluetooth not probed
I checked the BIOS and it is enabled there. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1853665 Title: Realtek RTL8821CE [10ec:c821] Subsystem [103c:831a] Bluetooth not probed Status in linux package in Ubuntu: Incomplete Status in linux-oem package in Ubuntu: Confirmed Status in rtl8821ce package in Ubuntu: Confirmed Bug description: The driver installed just fine and wifi is working but bluetooth does not. I will gladly provide further debugging information. Ubuntu 19.10 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: steven 2090 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-11-17 (75 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0408:5321 Quanta Computer, Inc. HP Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP 250 G7 Notebook PC Package: rtl8821ce 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=/boot/vmlinuz-5.3.0-29-generic root=UUID=a0cdf605-0b72-4674-a76e-ad1dbae26043 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-29-generic N/A linux-backports-modules-5.3.0-29-generic N/A linux-firmware1.183.3 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: eoan Uname: Linux 5.3.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/05/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.16 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8532 dmi.board.vendor: HP dmi.board.version: 70.22 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.16:bd12/05/2018:svnHP:pnHP250G7NotebookPC:pvrType1ProductConfigId:rvnHP:rn8532:rvr70.22:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5336AN HP 200 dmi.product.name: HP 250 G7 Notebook PC dmi.product.sku: 6MQ54EA#ABD dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: steven 1931 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-11-17 (231 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0408:5321 Quanta Computer, Inc. HP Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 5: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M |__ Port 5: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M MachineType: HP HP 250 G7 Notebook PC Package: rtl8821ce 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=/boot/vmlinuz-5.4.0-40-generic root=UUID=a0cdf605-0b72-4674-a76e-ad1dbae26043 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no StagingDrivers: ashmem_linux Tags: focal staging staging Uname: Linux 5.4.0-40-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-18 (47 days ago) UserGroups: adm audio cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/05/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.16 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8532 dmi.board.vendor: HP dmi.board.version: 70.22 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.16:bd12/05/2018:svnHP:pnHP250G7Notebo
[Kernel-packages] [Bug 1853665] Re: Realtek RTL8821CE [10ec:c821] Subsystem [103c:831a] Bluetooth not probed
Please test latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8-rc4/ Install the kernel, cold boot and and attach `dmesg` here, thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1853665 Title: Realtek RTL8821CE [10ec:c821] Subsystem [103c:831a] Bluetooth not probed Status in linux package in Ubuntu: Incomplete Status in linux-oem package in Ubuntu: Confirmed Status in rtl8821ce package in Ubuntu: Confirmed Bug description: The driver installed just fine and wifi is working but bluetooth does not. I will gladly provide further debugging information. Ubuntu 19.10 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: steven 2090 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-11-17 (75 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0408:5321 Quanta Computer, Inc. HP Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP 250 G7 Notebook PC Package: rtl8821ce 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=/boot/vmlinuz-5.3.0-29-generic root=UUID=a0cdf605-0b72-4674-a76e-ad1dbae26043 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-29-generic N/A linux-backports-modules-5.3.0-29-generic N/A linux-firmware1.183.3 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: eoan Uname: Linux 5.3.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/05/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.16 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8532 dmi.board.vendor: HP dmi.board.version: 70.22 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.16:bd12/05/2018:svnHP:pnHP250G7NotebookPC:pvrType1ProductConfigId:rvnHP:rn8532:rvr70.22:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5336AN HP 200 dmi.product.name: HP 250 G7 Notebook PC dmi.product.sku: 6MQ54EA#ABD dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: steven 1931 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-11-17 (231 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0408:5321 Quanta Computer, Inc. HP Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 5: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M |__ Port 5: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M MachineType: HP HP 250 G7 Notebook PC Package: rtl8821ce 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=/boot/vmlinuz-5.4.0-40-generic root=UUID=a0cdf605-0b72-4674-a76e-ad1dbae26043 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no StagingDrivers: ashmem_linux Tags: focal staging staging Uname: Linux 5.4.0-40-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-18 (47 days ago) UserGroups: adm audio cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/05/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.16 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8532 dmi.board.vendor: HP dmi.board.version: 70.22 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor
[Kernel-packages] [Bug 1886785] [NEW] [SRU][PATCH 0/1][oem-5.6] fix amd RENOIR screen backlight issue.
Public bug reported: [Impact] On AMD RENOIR gpu, after S3 backlight brightness can not be changed. [Fix] Pevious patch prevent loading iram, then dmcu can not work. Remove unused check to load iram right. Then backlight works well. [Test] Verified on hardware, after 10 times of S3, backlight can be changed by hotkey. [Regression Potential] Low Upstream fix, backports is minimal. RENOIR is only supported on oem-5.6, no focal patch. Harry Wentland (1): Revert "drm/amd/display: disable dcn20 abm feature for bring up" drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 11 --- 1 file changed, 4 insertions(+), 7 deletions(-) ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: oem-priority originate-from-1868640 sutton ** Tags added: oem-priority originate-from-1868640 sutton -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1886785 Title: [SRU][PATCH 0/1][oem-5.6] fix amd RENOIR screen backlight issue. Status in HWE Next: New Status in linux package in Ubuntu: New Bug description: [Impact] On AMD RENOIR gpu, after S3 backlight brightness can not be changed. [Fix] Pevious patch prevent loading iram, then dmcu can not work. Remove unused check to load iram right. Then backlight works well. [Test] Verified on hardware, after 10 times of S3, backlight can be changed by hotkey. [Regression Potential] Low Upstream fix, backports is minimal. RENOIR is only supported on oem-5.6, no focal patch. Harry Wentland (1): Revert "drm/amd/display: disable dcn20 abm feature for bring up" drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 11 --- 1 file changed, 4 insertions(+), 7 deletions(-) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1886785/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886769] Re: [ 0.000000] Initramfs unpacking failed: Decoding failed
Do you think this bug is somehow related to the following bug? https://bugs.launchpad.net/bugs/1886148 For example, are there problems to boot into a live system from a USB drive in a real system, or booted from a virtual hard disk drive with the image in a virtual machine? (I know that it boots in VirtualBox from the iso file when seen as an optical (CD/DVD) drive.) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1886769 Title: [ 0.00] Initramfs unpacking failed: Decoding failed Status in grub2 package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in syslinux package in Ubuntu: New Bug description: Steps to reproduce: 1. Download MATE Groovy daily (sha256sum = 7d2fdad36b8fcf0409aa0a484755e5fc5ef3798fd256eeebbde905a71ad474b7 ) 2. Insert ISO into VirtualBox with EFI enabled 3. Boot VM Expected results: * VM boots normally Actual results: * VM hangs during early boot with message [ 0.00] Initramfs unpacking failed: Decoding failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1886769/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1883229] Re: Ubuntu server installation on S3260M4 server fails
No even with separate installer legacy is working fine. ** Changed in: subiquity 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/1883229 Title: Ubuntu server installation on S3260M4 server fails Status in subiquity: Confirmed Status in grub2 package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Details/Description: - Ubuntu 20.04 fails on S3260 M4 with Gonga Beach in UEFI mode. Os get installed. However, upon rebooting OS never came up. Grub loads only to get hanged in a black screen. No options work later. Unable to collect Installer logs. How to reproduce: -- 1.Update S3260M4 M4 to bios build ucs-s3260-huu-4.1.2S36 2.Deploy Ubuntu 20.04 on S3260 M4. 3.Observe the installation proceeding and after installation OS reboots and loads the kernel and gets hanged on the black screen 4. The same OS works in Legacy mode in C3000 RAID controller card of LSI. Expected behavior: - Ubuntu 20.04 should get deployed in GB/DD-Raid in UEFI mode Screenshots -- Screenshot attached. Please let us know how to collect logs on this scenario Note :With MASS deployment we are able to deploy OS successfully with USFI method. Attached the logs of MASS server in this bug. --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Jun 17 09:07 seq crw-rw+ 1 root audio 116, 33 Jun 17 09:07 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-16 (0 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 003: ID 0624:0402 Avocent Corp. Cisco Virtual Keyboard and Mouse Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Cisco Systems Inc UCSC-C3K-M4SRB Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=1db32ed4-cafc-4d2c-b57c-d0b6a3943066 ro 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 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: WifiSyslog: _MarkForUpload: True dmi.bios.date: 03/06/2020 dmi.bios.vendor: Cisco Systems, Inc. dmi.bios.version: C3X60M4.4.1.1.13.0306200116 dmi.board.name: UCSC-C3K-M4SRB dmi.board.vendor: Cisco Systems Inc dmi.board.version: 73-17622-03 dmi.chassis.type: 23 dmi.chassis.vendor: Cisco Systems Inc dmi.chassis.version: 68-5829-03 dmi.modalias: dmi:bvnCiscoSystems,Inc.:bvrC3X60M4.4.1.1.13.0306200116:bd03/06/2020:svnCiscoSystemsInc:pnUCSC-C3K-M4SRB:pvrA0:rvnCiscoSystemsInc:rnUCSC-C3K-M4SRB:rvr73-17622-03:cvnCiscoSystemsInc:ct23:cvr68-5829-03: dmi.product.name: UCSC-C3K-M4SRB dmi.product.version: A0 dmi.sys.vendor: Cisco Systems Inc --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Jun 17 09:07 seq crw-rw+ 1 root audio 116, 33 Jun 17 09:07 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-16 (0 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 003: ID 0624:0402 Avocent Corp. Cisco Virtual Keyboard and Mouse Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[Kernel-packages] [Bug 1886785] 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 1886785 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/1886785 Title: [SRU][PATCH 0/1][oem-5.6] fix amd RENOIR screen backlight issue. Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: [Impact] On AMD RENOIR gpu, after S3 backlight brightness can not be changed. [Fix] Pevious patch prevent loading iram, then dmcu can not work. Remove unused check to load iram right. Then backlight works well. [Test] Verified on hardware, after 10 times of S3, backlight can be changed by hotkey. [Regression Potential] Low Upstream fix, backports is minimal. RENOIR is only supported on oem-5.6, no focal patch. Harry Wentland (1): Revert "drm/amd/display: disable dcn20 abm feature for bring up" drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 11 --- 1 file changed, 4 insertions(+), 7 deletions(-) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1886785/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886245] Re: BCM20702A bluetooth mouse freezing for 4-9 seconds
** Description changed: Boot system, the Bluetooth mouse will stop for about 4-9 seconds, then it will work as normal. I am using a plugable USB Bluetooth adapter for Bluetooth connections. I am using blueman to connect. Mouse used is a Kensington Exper Mouse Wireless Trackball Issue does not occur with bluetooth speakers, or headphones. Computer- Dell Precision 5520. - Logs show these errors as below bt_uhid_send: Invalid argument (22) Bluetooth: hci0: advertising data len corrected - Description: Ubuntu 20.04 LTS Release: 20.04 blueman: - Installed: 2.1.2-1 - Candidate: 2.1.2-1 - Version table: - *** 2.1.2-1 500 - 500 http://au.archive.ubuntu.com/ubuntu focal/universe amd64 Packages - 100 /var/lib/dpkg/status + Installed: 2.1.2-1 + Candidate: 2.1.2-1 + Version table: + *** 2.1.2-1 500 + 500 http://au.archive.ubuntu.com/ubuntu focal/universe amd64 Packages + 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluetooth (not installed) 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 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jul 4 13:24:01 2020 InstallationDate: Installed on 2020-06-03 (30 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 001 Device 003: ID 0c45:6713 Microdia Integrated_Webcam_HD - Bus 001 Device 002: ID 0a5c:21e8 Broadcom Corp. BCM20702A0 Bluetooth 4.0 - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 003: ID 0c45:6713 Microdia Integrated_Webcam_HD + Bus 001 Device 002: ID 0a5c:21e8 Broadcom Corp. BCM20702A0 Bluetooth 4.0 + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Precision 5520 ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_ezfsem@/vmlinuz-5.4.0-40-generic root=ZFS=rpool/ROOT/ubuntu_ezfsem ro quiet splash pcie_aspm=off vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/22/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.19.2 dmi.board.name: 06X96V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.19.2:bd05/22/2020:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn06X96V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5520 dmi.product.sku: 07BF dmi.sys.vendor: Dell Inc. hciconfig: - hci0:Type: Primary Bus: USB - BD Address: 5C:F3:70:7E:32:2F ACL MTU: 1021:8 SCO MTU: 64:1 - UP RUNNING PSCAN ISCAN - RX bytes:193521 acl:13666 sco:0 events:137 errors:0 - TX bytes:5858 acl:61 sco:0 commands:82 errors:0 + hci0:Type: Primary Bus: USB + BD Address: 5C:F3:70:7E:32:2F ACL MTU: 1021:8 SCO MTU: 64:1 + UP RUNNING PSCAN ISCAN + RX bytes:193521 acl:13666 sco:0 events:137 errors:0 + TX bytes:5858 acl:61 sco:0 commands:82 errors:0 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1886245 Title: BCM20702A bluetooth mouse freezing for 4-9 seconds Status in linux package in Ubuntu: Incomplete Bug description: Boot system, the Bluetooth mouse will stop for about 4-9 seconds, then it will work as normal. I am using a plugable USB Bluetooth adapter for Bluetooth connections. I am using blueman to connect. Mouse used is a Kensington Exper Mouse Wireless Trackball Issue does not occur with bluetooth speakers, or headphones. Computer- Dell Precision 5520. Logs show these errors as below bt_uhid_send: Invalid argument (22) Bluetooth: hci0: advertising data len corrected Description: Ubuntu 20.04 LTS Release: 20.04 blueman: Installed: 2.1.2-1 Candidate: 2.1.2-1 Version table: *** 2.1.2-1 500 500 http://au.archive.ubuntu.com/ubuntu focal/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluetooth (not installed) 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 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jul 4 13:24:01 2020 InstallationDate: Installed on 2020-06-03 (30 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Int
[Kernel-packages] [Bug 1844410] Re: [TGL] Thunderbolt support (Tiger Lake)
Verified on oem-5.6 1019, thunderbolt nvme device probed correctly.
** 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/1844410
Title:
[TGL] Thunderbolt support (Tiger Lake)
Status in HWE Next:
New
Status in intel:
Fix Committed
Status in linux package in Ubuntu:
Confirmed
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:
Confirmed
Status in linux-oem-5.6 source package in Groovy:
Invalid
Bug description:
[SRU Justification]
[Impact]
TigerLake platforms fail to probe thunderbolt controller and leaving an
error message:
[2.069944] input: PS/2 Generic Mouse as
/devices/platform/i8042/serio1/input/input5
[ 21.772011] thunderbolt: probe of :00:0d.2 failed with error -110
It also introduces a nearly 20 second idle at boot.
[Fix]
Commit 57d8df68eb53 ("thunderbolt: Add support for Intel Tiger Lake")
recently landed to v5.8-rc1 addressed this issue.
[Test Case]
Check thunderbolt controller probe messages from dmesg:
thunderbolt :00:0d.2: 0: unsupported switch device id 0x9a1b
thunderbolt :00:0d.2: 0: uid crc8 mismatch (expected: 0x8e, got: 0x59)
[Regression Potential]
Low. This only enables devices which are previously failed in device
initialization.
== Original Bug Description ==
Description
TBT enabling in TGL
* 386e5e29d81c ("thunderbolt: Make tb_find_port() available to other files")
v5.6-rc1
* 4deb200d34a7 ("thunderbolt: Call tb_eeprom_get_drom_offset() from
tb_eeprom_read_n()") v5.6-rc1
* 210e9f56e9e1 ("thunderbolt: Populate PG field in hot plug acknowledgment
packet") v5.6-rc1
* b04079837b20 ("thunderbolt: Add initial support for USB4") v5.6-rc1
* 690ac0d20d40 ("thunderbolt: Update Kconfig entries to USB4") v5.6-rc1
* aa43a9dcf7fc ("thunderbolt: Make tb_switch_find_cap() available to other
files") v5.6-rc1
* cf29b9afb121 ("thunderbolt: Add support for Time Management Unit") v5.6-rc1
* e6f818585713 ("thunderbolt: Add support for USB 3.x tunnels") v5.6-rc1
Target Kernel: 5.6
Target Release: 20.10
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1844410/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882850] Re: Touchpad not detected
*** This bug is a duplicate of bug 1885573 *** https://bugs.launchpad.net/bugs/1885573 ** Tags added: hwe-touchpad -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1882850 Title: Touchpad not detected 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/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=PNP0C0C/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 U: Uniq= H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab83 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input3 U: Uniq= H: Handlers=sysrq kbd event3 leds B: PROP=0 B: EV=120013 B: KEY=40200 3803078f800d001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0019 Vendor= Product= Version= N: Name="Ideapad extra buttons" P: Phys=ideapad/input0 S: Sysfs=/devices/pci:00/:00:1f.0/PNP0C09:00/VPC2004:00/input/input8 U: Uniq= H: Handlers=rfkill kbd event8 B: PROP=0 B: EV=13 B: KEY=81000800100c03 4430 0 2 B: MSC=10 I: Bus=0003 Vendor=04f2 Product=b6d9 Version=2699 N: Name="Integrated Camera: Integrated C" P: Phys=usb-:00:14.0-6/button S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-6/3-6:1.0/input/input9 U: Uniq= H: Handlers=kbd event9 B: PROP=0 B: EV=3 B: KEY=10 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/input10 U: Uniq= H: Handlers=kbd event10 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Mic" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input11 U: Uniq= H: Handlers=event11 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/input12 U: Uniq= H: Handlers=event12 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/input13 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=7" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input14 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=8" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input15 U: Uniq= H: Handlers=event15 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/input16 U: Uniq= H: Handlers=event16 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/input17 U: Uniq= H: Handlers=event17 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=11" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input18 U: Uniq= H: Handlers=event18 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=12" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input19 U: Uniq= H: Handlers=event19 B: PROP=0 B: EV=21 B: SW=140 I: Bus=0003 Vendor=3938 Product=1080 Version=0200 N: Name="YK 2.4G Wireless Device Mouse" P: Phys=usb-:00:14.0-3/input0 S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-3/3-3:1.0/0003:3938:1080.0003/input/input20 U: Uniq= H: Handlers=mouse0 event4 B: PROP=0 B: EV=17 B: KEY=1f 0 0 0 0 B: REL=903 B: MSC=10 I: Bus=0003 Vendor=3938 Product=1080 Version=0200 N: Name="YK 2.4G Wireless Device System Control" P: Phys=usb-:00:14.0-3/inp
[Kernel-packages] [Bug 1886366] Re: USB External Drive Stalls and Timeouts
If it's a regression, can you please find out what was the last kernel that doesn't have this issue? ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1886366 Title: USB External Drive Stalls and Timeouts Status in linux package in Ubuntu: Incomplete Bug description: Not sure of the package naming for the Linux Kernel. However since version 4.15.0.28 I've been getting timeouts like this in dmesg: [63075.835488] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [63075.835491] scsi_eh_7 D0 273 2 0x80004000 [63075.835494] Call Trace: [63075.835504] __schedule+0x2b9/0x6c0 [63075.835507] schedule+0x42/0xb0 [63075.835510] schedule_preempt_disabled+0xe/0x10 [63075.835513] __mutex_lock.isra.0+0x182/0x4f0 [63075.835515] ? __switch_to_asm+0x40/0x70 [63075.835517] ? __switch_to_asm+0x34/0x70 [63075.835519] ? __switch_to_asm+0x34/0x70 [63075.835520] ? __switch_to_asm+0x40/0x70 [63075.835523] __mutex_lock_slowpath+0x13/0x20 [63075.835526] mutex_lock+0x2e/0x40 [63075.835531] device_reset+0x22/0x50 [usb_storage] [63075.835535] scsi_eh_ready_devs+0x56c/0xa30 [63075.835540] ? __pm_runtime_resume+0x60/0x80 [63075.835543] scsi_error_handler+0x432/0x500 [63075.835548] kthread+0x104/0x140 [63075.835550] ? scsi_eh_get_sense+0x210/0x210 [63075.835553] ? kthread_park+0x80/0x80 [63075.83] ret_from_fork+0x35/0x40 The drive works fine on kernels 4.15.0.28 and older. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: nick 2943 F pulseaudio /dev/snd/controlC0: nick 2943 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=2e62fe89-0a58-42ff-95bd-80760e43753b InstallationDate: Installed on 2014-12-31 (2014 days ago) InstallationMedia: Lubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=f21814d2-6d82-426b-a5e0-cb4734f1a929 ro quiet splash init=/lib/systemd/systemd vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 RfKill: Tags: focal Uname: Linux 5.4.0-40-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-06-29 (7 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/17/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3506 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z68-V LE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3506:bd01/17/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VLE:rvrRevX.0x: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/+bug/1886366/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1870260] Re: initramfs unpacking failed: Decoding failed", message appears on boot up.
update-initramfs -u gives the following error message: /usr/bin/update- initramfs: 185: cannot create /var/lib/initramfs-tools/5.4.0-40-generic: Directory nonexistent I completely stuck after first boot of freshly installed ubuntu 20.04. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1870260 Title: initramfs unpacking failed: Decoding failed", message appears on boot up. Status in linux package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: OS : Ubuntu 20.04(20200401) Problem: "initramfs unpacking failed: Decoding failed", message appears on boot up solution: If we edit /etc/initramfs-tools/initramfs.conf and COMPRESS=lz4, to COMPRESS=gzip then the error is fixing . Expected solution: This but in there from a long time I have seen this from Ubuntu 18.04,19.04,19.10 now in 20.04 So please fix it or change it from lz4 to gzip. an early reply is highly appreciated Thank you . --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tamal 1451 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-02 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:b009 Realtek Semiconductor Corp. 802.11n WLAN Adapter Bus 001 Device 003: ID 0408:5365 Quanta Computer, Inc. HP TrueVision HD Camera Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 15-da0xxx Package: ubuntu-meta ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=29f895bf-ab7b-4df8-8e9a-c277376a2685 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/29/2019 dmi.bios.vendor: Insyde dmi.bios.version: F.23 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 84A6 dmi.board.vendor: HP dmi.board.version: 80.43 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.23:bd11/29/2019:svnHP:pnHPLaptop15-da0xxx:pvrType1ProductConfigId:rvnHP:rn84A6:rvr80.43:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-da0xxx dmi.product.sku: 5AY34PA#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1870260/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1885352] Re: touchpad not working at all
*** This bug is a duplicate of bug 1885573 *** https://bugs.launchpad.net/bugs/1885573 pci :00:1f.5: can't claim BAR 0 [mem 0xfe01-0xfe010fff]: no compatible bridge window -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1885352 Title: touchpad not working at all Status in linux package in Ubuntu: Confirmed Bug description: Just bought a brand new lenovo IdeaPad S145-15IIL and switched it to linux. The touchpad was working before swapping os. Can't find the manufacturer of the touchpad. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-39-generic 5.4.0-39.43 ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Uname: Linux 5.4.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: draal 1458 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jun 27 08:14:20 2020 InstallationDate: Installed on 2020-06-26 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b624 Chicony Electronics Co., Ltd Integrated Camera Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81W8 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-39-generic root=UUID=88c27fbd-2ac5-47e8-9181-d8307885944c ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-39-generic N/A linux-backports-modules-5.4.0-39-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/09/2019 dmi.bios.vendor: LENOVO dmi.bios.version: DKCN21WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad S145-15IIL dmi.modalias: dmi:bvnLENOVO:bvrDKCN21WW:bd10/09/2019:svnLENOVO:pn81W8:pvrLenovoIdeaPadS145-15IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS145-15IIL: dmi.product.family: IdeaPad S145-15IIL dmi.product.name: 81W8 dmi.product.sku: LENOVO_MT_81W8_BU_idea_FM_IdeaPad S145-15IIL dmi.product.version: Lenovo IdeaPad S145-15IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885352/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881322] Re: Touchpad not detected in 'Lenovo V15-IIL model 82C5' after installing Ubuntu 20.04
*** This bug is a duplicate of bug 1885573 *** https://bugs.launchpad.net/bugs/1885573 @Federico, please help attach your acpi dump info: $ sudo apt install acpica-tools $ sudo acpidump -o acpi.dump And attach that `acpi.dump` file. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881322 Title: Touchpad not detected in 'Lenovo V15-IIL model 82C5' after installing Ubuntu 20.04 Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 20.04 is installed in a brand new Lenovo V15-IIL alongside Windows 10. According to lenovo's support page, the driver for windows is Synaptics 19.5.10.149_Elan 22.4.18.1. In windows the touchpad works fine. This model has two options in BIOS regarding Fn Keys, a "Smart Fn key" that toogles the Fn key on/off each time you press it and a "Foolproof Fn Key" that maps the Fn key to Ctrl when you press a combinations of keys that does not have a Fn assigned. When I enable the "foolproof fn key" in the BIOS, the Fn + F1...F12 and the sound driver stop working (i dont have sound, i can't change the volume and the volume icon in the GUI does not show). Fn+F6 (to enable/disable touchpad) can't enable it. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fdadam 1434 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri May 29 13:08:24 2020 InstallationDate: Installed on 2020-05-28 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b624 Chicony Electronics Co., Ltd Integrated Camera Bus 001 Device 002: ID 0458:0186 KYE Systems Corp. (Mouse Systems) Genius DX-120 Mouse Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 82C5 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=fd0c8ed1-6032-467c-9902-3094e6740be8 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/04/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DKCN26WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo V15-IIL dmi.modalias: dmi:bvnLENOVO:bvrDKCN26WW:bd03/04/2020:svnLENOVO:pn82C5:pvrLenovoV15-IIL:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoV15-IIL: dmi.product.family: V15-IIL dmi.product.name: 82C5 dmi.product.sku: LENOVO_MT_82C5_BU_idea_FM_V15-IIL dmi.product.version: Lenovo V15-IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881322/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886297] Re: Touchpad Lenovo IdeaPad S145-15IIL Not working
*** This bug is a duplicate of bug 1885573 *** https://bugs.launchpad.net/bugs/1885573 pci :00:1f.5: can't claim BAR 0 [mem 0xfe01-0xfe010fff]: no compatible bridge window Please help attach your acpi dump info: $ sudo apt install acpica-tools $ sudo acpidump -o acpi.dump And attach that `acpi.dump` file. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1886297 Title: Touchpad Lenovo IdeaPad S145-15IIL Not working Status in linux package in Ubuntu: Confirmed Bug description: Have buyed this laptop today, the laptop was preinstalled with Windows 10 (touchpad working). Reinstalled it with Kubuntu 20.04 and touchpad wasnt working. Help. sjaak@lenovoSS -- OS: Ubuntu 20.04 LTS x86_64 Host: 81W8 Lenovo IdeaPad S145-15IIL Kernel: 5.4.0-40-generic Uptime: 24 mins Packages: 2149 (dpkg) Shell: bash 5.0.16 Resolution: 1920x1080 DE: Plasma WM: KWin WM Theme: ChromeOS-dark Theme: ChromeOSDark [Plasma], Breeze [GTK2/3] Icons: McMuse [Plasma], McMuse [GTK2/3] Terminal: konsole CPU: Intel i3-1005G1 (4) @ 3.400GHz GPU: Intel Device 8a56 Memory: 1904MiB / 7758MiB ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sjaak 786 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sun Jul 5 02:52:30 2020 InstallationDate: Installed on 2020-07-04 (0 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 174f:1176 Syntek Integrated Camera Bus 001 Device 002: ID 046d:c03d Logitech, Inc. M-BT96a Pilot Optical Mouse Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81W8 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=c478aa91-fd7e-4659-af74-447a643491cf 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: 03/04/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DKCN26WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32866 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad S145-15IIL dmi.modalias: dmi:bvnLENOVO:bvrDKCN26WW:bd03/04/2020:svnLENOVO:pn81W8:pvrLenovoIdeaPadS145-15IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0R32866WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS145-15IIL: dmi.product.family: IdeaPad S145-15IIL dmi.product.name: 81W8 dmi.product.sku: LENOVO_MT_81W8_BU_idea_FM_IdeaPad S145-15IIL dmi.product.version: Lenovo IdeaPad S145-15IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886297/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1880593] Re: TouchPad not working
*** This bug is a duplicate of bug 1885573 *** https://bugs.launchpad.net/bugs/1885573 pci :00:1f.5: can't claim BAR 0 [mem 0xfe01-0xfe010fff]: no compatible bridge window Please help attach your acpi dump info: $ sudo apt install acpica-tools $ sudo acpidump -o acpi.dump And attach that `acpi.dump` file. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1880593 Title: TouchPad not working Status in linux package in Ubuntu: Incomplete Bug description: Hi Support team, in a fresh installation in a lenovo laptop, touchpad is not working. mouse is working fine though. Attaching /proc/bus/input/devices as per debugging wiki. https://wiki.ubuntu.com/DebuggingTouchpadDetection#generalinfo Kind regards, Pablo. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-31-generic 5.4.0-31.35 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pali 1214 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 25 15:05:38 2020 InstallationDate: Installed on 2020-05-25 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 062a:4102 MosArt Semiconductor Corp. 2.4G Wireless Mouse Bus 001 Device 002: ID 04f2:b624 Chicony Electronics Co., Ltd Integrated Camera Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 82C5 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=3b0502a4-3082-45eb-ac7e-12a3c6b934ee ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/04/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DKCN26WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo V15-IIL dmi.modalias: dmi:bvnLENOVO:bvrDKCN26WW:bd03/04/2020:svnLENOVO:pn82C5:pvrLenovoV15-IIL:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoV15-IIL: dmi.product.family: V15-IIL dmi.product.name: 82C5 dmi.product.sku: LENOVO_MT_82C5_BU_idea_FM_V15-IIL dmi.product.version: Lenovo V15-IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880593/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882850] Re: Touchpad not detected
*** This bug is a duplicate of bug 1885573 *** https://bugs.launchpad.net/bugs/1885573 pci :00:1f.5: can't claim BAR 0 [mem 0xfe01-0xfe010fff]: no compatible bridge window Please help attach your acpi dump info: $ sudo apt install acpica-tools $ sudo acpidump -o acpi.dump And attach that `acpi.dump` file. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1882850 Title: Touchpad not detected 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/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=PNP0C0C/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 U: Uniq= H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab83 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input3 U: Uniq= H: Handlers=sysrq kbd event3 leds B: PROP=0 B: EV=120013 B: KEY=40200 3803078f800d001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0019 Vendor= Product= Version= N: Name="Ideapad extra buttons" P: Phys=ideapad/input0 S: Sysfs=/devices/pci:00/:00:1f.0/PNP0C09:00/VPC2004:00/input/input8 U: Uniq= H: Handlers=rfkill kbd event8 B: PROP=0 B: EV=13 B: KEY=81000800100c03 4430 0 2 B: MSC=10 I: Bus=0003 Vendor=04f2 Product=b6d9 Version=2699 N: Name="Integrated Camera: Integrated C" P: Phys=usb-:00:14.0-6/button S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-6/3-6:1.0/input/input9 U: Uniq= H: Handlers=kbd event9 B: PROP=0 B: EV=3 B: KEY=10 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/input10 U: Uniq= H: Handlers=kbd event10 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Mic" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input11 U: Uniq= H: Handlers=event11 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/input12 U: Uniq= H: Handlers=event12 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/input13 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=7" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input14 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=8" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input15 U: Uniq= H: Handlers=event15 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/input16 U: Uniq= H: Handlers=event16 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/input17 U: Uniq= H: Handlers=event17 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=11" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input18 U: Uniq= H: Handlers=event18 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=12" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input19 U: Uniq= H: Handlers=event19 B: PROP=0 B: EV=21 B: SW=140 I: Bus=0003 Vendor=3938 Product=1080 Version=0200 N: Name="YK 2.4G Wireless Device Mouse" P: Phys=usb-:00:14.0-3/input0 S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-3/3-3:1.0/0003:3938:1080.0003/input/input20 U: Uniq= H: Handlers=mouse0 event4
[Kernel-packages] [Bug 1886714] Re: Bluetooth disconnects, and then sound fails on reconnect
>From second paragraph “I wonder if I started noticing the problem under Ubuntu 14.x, but I'm pretty sure it was there already at Ubuntu 16.x. I'm now running Ubuntu 19.10 and Gnome 3.34.2. (Just for the record, the bug also persisted in Ubu 18.04 for as long as I was using it.)” The bug was infact the reason I updated to 19.04 and later to 19.10, but it did not go away. -- 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/1886714 Title: Bluetooth disconnects, and then sound fails on reconnect Status in bluez package in Ubuntu: Won't Fix Bug description: This bug has persisted over several years, and several versions, and after a lot of investigation I'm not really any closer on what's going on. I have two pretty old GA MA78gm S2H mainboards, configured slightly different, and otherwise working properly. Both of them have run both Ubuntu and Windows. The problem seems to have been minimized when running Win10, and even if it is there it seems like Win10 recover when it happen. I wonder if I started noticing the problem under Ubuntu 14.x, but I'm pretty sure it was there already at Ubuntu 16.x. I'm now running Ubuntu 19.10 and Gnome 3.34.2. (Just for the record, the bug also persisted in Ubu 18.04 for as long as I was using it.) It isn't really an option to switch the mainboards, as there are too much custom-builds running on them for the moment. They will probably be replaced when I have time to rebuild everything. ;) To make Bluetooth work I use an ASUS USB-BT400, which report as “BCM920702 Bluetooth 4.0”, or more accurately “BCM20702A1 (001.002.014) build 1467”. I have also used other dongles, but it seems like all of them has the same chipset. Now… Given I restart the computer And boot into Ubuntu 19.10 And log in as myself And attach a pair of Sony MDR-ZX770BN When I listen to sound from a movie with A2DP Then at some random point it start to lag noticeably (sound becomes scratchy) And suddenly disconnects (at this point it seems like it is Bluetooth that disconnects) It may take 5–10 minutes and up to several hours before it disconnects. Given I turn the headphones off And back on When it reconnects to the computer Then the computer fails to enable the sound device (visible in the preference manager f.ex.) There are several reports of various equipments that disconnect, and I wonder if this could be the same problem. Problem 1 The dongle is rather hot when it disconnects. This is mere speculation, but I wonder if the disconnect happen because either the mainboard gives to little current and thus it fails due to voltage drop, or it fails due to overheating. It seems like the port should have enough current to sustain the dongle, but I wonder if the mainboard could let several ports share the same power source, and thus it fail to deliver enough current. There are other devices powered by the USB ports, and they don't seem to fail, which seems likely to happen if power is the issue. The issue seems to be somewhat related to the quality of the audio, which makes me wonder whether higher quality gives more transferred data, which again gives higher power consumption. It also seems like the issue can be triggered by moving away from the computer. That would give higher tx power, which could make the dongle overheat or mainboard could fail to provide enough current. Is there any way to get a more specific failure report from the dongle? Problem 2 After the headphone reconnects it seems like the sound system isn't working properly. I've been checking, and everything seems correct, still the headphone is missing as an output device. I have not been able to figure out what makes the sound system fail, and I have not been able to make it recover. Only way to recover seems to be to do a cold reboot. A simple warm reboot does not fix the problem, but this can be related to problem 1. A few dumps john@hydra:~$ dmesg | fgrep 'Blue' [3.089584] usb 1-2.2: Product: BCM920702 Bluetooth 4.0 [8.417252] Bluetooth: Core ver 2.22 [8.417280] Bluetooth: HCI device and connection manager initialized [8.417284] Bluetooth: HCI socket layer initialized [8.417286] Bluetooth: L2CAP socket layer initialized [8.417301] Bluetooth: SCO socket layer initialized [8.779706] Bluetooth: hci0: BCM: chip id 63 [8.780703] Bluetooth: hci0: BCM: features 0x07 [8.796682] Bluetooth: hci0: hydra [8.800667] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467 [9.671568] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467 [9.687584] Bluetooth: hci0: Broadcom Bluetooth Device [ 10.571440] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 10.571442] Bluetooth: BNEP filters: protocol multicast [ 10.571448] Bluetooth: BNEP s
[Kernel-packages] [Bug 1886245] Re: BCM20702A bluetooth mouse freezing for 4-9 seconds
@Sam, please try following kernel boot parameters, reboot and attach output of `journalctl -b`: btusb.enable_autosuspend=0 For detailed steps, please see https://wiki.ubuntu.com/Kernel/KernelBootParameters#Temporarily_Add_a_Kernel_Boot_Parameter_for_Testing ** Summary changed: - BCM20702A bluetooth mouse freezing for 4-9 seconds + 0a5c:21e8 Broadcom BCM20702A0: bluetooth mouse freezing for 4-9 seconds -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1886245 Title: 0a5c:21e8 Broadcom BCM20702A0: bluetooth mouse freezing for 4-9 seconds Status in linux package in Ubuntu: Incomplete Bug description: Boot system, the Bluetooth mouse will stop for about 4-9 seconds, then it will work as normal. I am using a plugable USB Bluetooth adapter for Bluetooth connections. I am using blueman to connect. Mouse used is a Kensington Exper Mouse Wireless Trackball Issue does not occur with bluetooth speakers, or headphones. Computer- Dell Precision 5520. Logs show these errors as below bt_uhid_send: Invalid argument (22) Bluetooth: hci0: advertising data len corrected Description: Ubuntu 20.04 LTS Release: 20.04 blueman: Installed: 2.1.2-1 Candidate: 2.1.2-1 Version table: *** 2.1.2-1 500 500 http://au.archive.ubuntu.com/ubuntu focal/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluetooth (not installed) 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 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jul 4 13:24:01 2020 InstallationDate: Installed on 2020-06-03 (30 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:6713 Microdia Integrated_Webcam_HD Bus 001 Device 002: ID 0a5c:21e8 Broadcom Corp. BCM20702A0 Bluetooth 4.0 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Precision 5520 ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_ezfsem@/vmlinuz-5.4.0-40-generic root=ZFS=rpool/ROOT/ubuntu_ezfsem ro quiet splash pcie_aspm=off vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/22/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.19.2 dmi.board.name: 06X96V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.19.2:bd05/22/2020:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn06X96V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5520 dmi.product.sku: 07BF dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 5C:F3:70:7E:32:2F ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN ISCAN RX bytes:193521 acl:13666 sco:0 events:137 errors:0 TX bytes:5858 acl:61 sco:0 commands:82 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886245/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1885862] Re: Add in-tree Realtek 8821CE wireless module support
PPA: https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1885862 . So far only linux-firmware was added. ** Description changed: - TBD. + 8821ce is being upstreamed in https://lore.kernel.org/linux- + wireless/20200603094218.19942-1-yhchu...@realtek.com/ . To backport it + to ubuntu kernel so that we may obsolete the usage of rtl8821ce-dkms + from https://bugs.launchpad.net/ubuntu/+source/rtl8821ce . -- 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/1885862 Title: Add in-tree Realtek 8821CE wireless module support Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-firmware package in Ubuntu: Invalid Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: Incomplete Status in linux-firmware source package in Focal: Triaged Status in linux-oem-5.6 source package in Focal: New Status in linux source package in Groovy: Incomplete Status in linux-firmware source package in Groovy: Invalid Status in linux-oem-5.6 source package in Groovy: Invalid Bug description: 8821ce is being upstreamed in https://lore.kernel.org/linux- wireless/20200603094218.19942-1-yhchu...@realtek.com/ . To backport it to ubuntu kernel so that we may obsolete the usage of rtl8821ce-dkms from https://bugs.launchpad.net/ubuntu/+source/rtl8821ce . To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1885862/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1885862] Re: Add in-tree Realtek 8821CE wireless module support
Upstream commit 401bd6de ("rtw88: RTL8821C: add firmware file v24.5")
already in groovy
** Changed in: linux-firmware (Ubuntu Groovy)
Status: New => Invalid
** Changed in: linux-firmware (Ubuntu Focal)
Status: New => Triaged
** Changed in: linux-firmware (Ubuntu Focal)
Assignee: (unassigned) => You-Sheng Yang (vicamo)
--
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/1885862
Title:
Add in-tree Realtek 8821CE wireless module support
Status in HWE Next:
New
Status in linux package in Ubuntu:
Incomplete
Status in linux-firmware package in Ubuntu:
Invalid
Status in linux-oem-5.6 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Incomplete
Status in linux-firmware source package in Focal:
Triaged
Status in linux-oem-5.6 source package in Focal:
New
Status in linux source package in Groovy:
Incomplete
Status in linux-firmware source package in Groovy:
Invalid
Status in linux-oem-5.6 source package in Groovy:
Invalid
Bug description:
8821ce is being upstreamed in https://lore.kernel.org/linux-
wireless/20200603094218.19942-1-yhchu...@realtek.com/ . To backport it
to ubuntu kernel so that we may obsolete the usage of rtl8821ce-dkms
from https://bugs.launchpad.net/ubuntu/+source/rtl8821ce .
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1885862/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1875263] Re: linux-firmware: missing sof-cfl.ri symbol link for Bionic and Eoan
Test Dell Inspiron 7591 on bionic. 1. sudo apt dist-upgrade 2. sudo reboot not alsa card, show 'Dummy output' in gnome-control-center 4. add proposed source list 5. sudo apt update 6. sudo apt install linux-firmware 7. sudo reboot 8. sound card is appeared in gnome-control-center [test] speaker + DMIC: ok headset input + headset output: ok -- 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/1875263 Title: linux-firmware: missing sof-cfl.ri symbol link for Bionic and Eoan Status in OEM Priority Project: New Status in linux-firmware package in Ubuntu: Fix Committed Status in linux-firmware source package in Bionic: Incomplete Status in linux-firmware source package in Eoan: Fix Committed Bug description: [Impact] some ubuntu eoan/bionic users reported that the audio driver failed to initialize, then the audio didn't work. I checked the dmesg, found the sof driver planed to load sof-cfl.ri, but there is no this firmware under eoan or bionic. [Fix] I consulted with Intel audio team, they told me that the coffeelake platform could share the firmware with cnl/whl platoforms, so we could build a symbol link sof-cfl->sof-cnl. [Test Case] A couple of ubuntu users already tested it on Dell and Asus coffeelake laptops, it worked well. [Regression Risk] Low, users already tested it, and Intel audio team confirmed it is safe. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1875263/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881338] Autopkgtest regression report (linux-base/4.5ubuntu2.2)
All autopkgtests for the newly accepted linux-base (4.5ubuntu2.2) for eoan have finished running. The following regressions have been reported in tests triggered by the package: makedumpfile/1:1.6.6-2ubuntu2.1 (ppc64el, i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/eoan/update_excuses.html#linux-base [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-base in Ubuntu. https://bugs.launchpad.net/bugs/1881338 Title: linux-azure: Update SGX version to version LD_1.33 Status in linux-azure package in Ubuntu: In Progress Status in linux-azure-4.15 package in Ubuntu: New Status in linux-base package in Ubuntu: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-4.15 source package in Xenial: Invalid Status in linux-base source package in Xenial: Fix Released Status in linux-azure source package in Bionic: Fix Committed Status in linux-azure-4.15 source package in Bionic: Fix Released Status in linux-base source package in Bionic: Fix Released Status in linux-azure source package in Eoan: Fix Released Status in linux-azure-4.15 source package in Eoan: Invalid Status in linux-base source package in Eoan: Fix Released Status in linux-azure source package in Focal: Fix Released Status in linux-azure-4.15 source package in Focal: Invalid Status in linux-base source package in Focal: Fix Released Bug description: [Impact] We have included the DCAP version of SGX into the linux-azure kernels in order to provide a signed version of this driver that can be used with secure boot in Azure instances. Since a new version of this driver was released, we should update the embedded driver: https://github.com/intel/SGXDataCenterAttestationPrimitives/tree/LD_1.33/driver/linux [Test Case] - Install the new kernel on an ACC azure instance. - Ensure the module loads properly. - Check if ECL (provided on the azure images) is working properly. [Regression Potential] The changes are extensive, but both Canonical and Microsoft perform validation tests on SGX. Besides that, the change is restricted to linux-azure running on specific instances. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1881338/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882442] Re: Upgrade from 18.04 to 20.04 deactivates internal monitor in display manager
Yes, it worked on 18.04. The problem came with the upgrade to 20.04. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1882442 Title: Upgrade from 18.04 to 20.04 deactivates internal monitor in display manager Status in linux package in Ubuntu: Incomplete Status in linux package in Fedora: Unknown Bug description: output of lsb_release -rd: Description: Ubuntu 20.04 LTS Release: 20.04 I recently upgraded from 18.04 to 20.04 and was using MATE. When the upgrade was run my external HDMI monitor was plugged in, after the update, when I reboot, the internal monitor shows the beginning of the boot process (I deactivated 'silent splash' by editing grub.cfg) then it switches to the HDMI monitor and the internal monitor goes dark. I can also get the tty consoles on the external monitor but not on the internal monitor. In MATE it was a real problem because the panel is apparently still on the invisible part of the desktop; I used a tty to install gnome, then I could get the display settings by right-clicking on the desktop, and setting the monitors to mirror, so I can reach applications, etc. Computer is a Dell Inspiron 3275 AIO with touch screen and Intel on-board video, I think. I had no problems with Ubuntu 18.04 with MATE. The problem seems to be similar to this bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874194 but sort of the reverse, in that the internal monitor is the problem. Thank you for your help. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: david 2012 F pulseaudio /dev/snd/controlC1: david 2012 F pulseaudio /dev/snd/controlC0: david 2012 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jun 7 11:43:37 2020 HibernationDevice: RESUME=UUID=3b1a8a2e-1937-4785-b4bb-49f9a251b292 InstallationDate: Installed on 2020-03-07 (91 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Inspiron 3275 AIO ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=95b8de7f-9de3-4cea-b947-e135a738948c ro RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-06-06 (1 days ago) dmi.bios.date: 03/15/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 04NJ6P dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 00 dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd03/15/2019:svnDellInc.:pnInspiron3275AIO:pvr1.7.0:rvnDellInc.:rn04NJ6P:rvrA02:cvnDellInc.:ct13:cvr00: dmi.product.family: Inspiron dmi.product.name: Inspiron 3275 AIO dmi.product.sku: 0855 dmi.product.version: 1.7.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882442/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1875459] Re: System hangs when loading google maps on chrome with navi AMD GPU
Hi! Any news regarding this issue? Can I help with more information? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1875459 Title: System hangs when loading google maps on chrome with navi AMD GPU Status in linux package in Ubuntu: Confirmed Bug description: Since upgrading to 20.04 from 19.10 I can reliably hang my system by loading Google Maps in Chrome and zooming in and out. After turning on DRM debugging: echo 0x1ff | sudo tee /sys/module/drm/parameters/debug I can see the following message in the kernel log: [16333.092468] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=2542114, emitted seq=2542116 [16333.092537] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process pid 0 thread pid 0 [16333.092540] [drm] GPU recovery disabled. It seems to be this upstream bug: https://gitlab.freedesktop.org/drm/amd/issues/892 I have two workarounds: * Running Chrome with AMD_DEBUG=nongg fixes the issue on 5.4.0-26 * With the latest upstream kernel, 5.6.7-050607, Chrome can load google maps with no issues. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-26-generic 5.4.0-26.30 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-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: nicholas 5696 F pulseaudio /dev/snd/controlC0: nicholas 5696 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Apr 27 18:36:12 2020 InstallationDate: Installed on 2019-11-04 (174 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_e02uh9@/vmlinuz-5.4.0-26-generic root=ZFS=rpool/ROOT/ubuntu_e02uh9 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-04-26 (0 days ago) dmi.bios.date: 07/12/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.30 dmi.board.name: X570 Phantom Gaming 4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.30:bd07/12/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX570PhantomGaming4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875459/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886337] Re: Qualcomm Atheros QCA6174 802.11ac - Ubuntu 20.04
Can i do something else ? -- 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/1886337 Title: Qualcomm Atheros QCA6174 802.11ac - Ubuntu 20.04 Status in linux-firmware package in Ubuntu: Incomplete Bug description: My notebook has the Qualcomm Atheros QCA6174 802.11ac wireless network adapter (rev 32). I have no problem using this device on Ubuntu 19.10, works well. So, After I Format and Install Ubuntu 20.04 stopped working I Used to use Ubuntu 19.04 and linux-firmware 1.183 - Wifi - OK Now, I tried Ubuntu 20.04 with linux-firmware is 1.187 and it stopped working. After I tried Ubuntu 20.04 with linux-firmware is 1.187.1 and it stopped working. Now I need Using Ubuntu 20.04 with linux-firmware is 1.183 and it working well, But I need hold linux-firmware. So after I download 19.10's linux-firmware package from the ubuntu repositories, which is at 1.183. After I installed and apt-marked hold the package, so that it would not be upgrade, and rebooted, my wifi worked well. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.183 Uname: Linux 5.4.0-40-generic x86_64 Architecture: amd64 NonfreeKernelModules: nvidia_modeset nvidia ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dmenezes 2470 F pulseaudio /dev/snd/controlC0: dmenezes 2470 F pulseaudio CasperMD5CheckResult: skip Dependencies: DistroRelease: Ubuntu 20.04 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e007 Qualcomm Atheros Communications Bus 001 Device 003: ID 0c45:6a08 Microdia Integrated_Webcam_HD Bus 001 Device 002: ID 093a:2533 Pixart Imaging, Inc. Gaming Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. G7 7588 NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice talpa_vcdevice talpa_core talpa_linux talpa_syscallhook nvidia_modeset nvidia Package: linux-firmware 1.187.1 PackageArchitecture: all 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.4.0-40-generic root=UUID=330509ee-8a3f-4851-b437-1a9b3a72c353 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 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.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 Tags: focal Uname: Linux 5.4.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 07/15/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.1 dmi.board.name: 0PK2PP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.1:bd07/15/2019:svnDellInc.:pnG77588:pvr:rvnDellInc.:rn0PK2PP:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: GSeries dmi.product.name: G7 7588 dmi.product.sku: 0825 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1886337/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886188] 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 1886188 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: linux (Ubuntu Focal) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1886188 Title: linux-libc-dev broken for crossbuilding, Multi-Arch:same violation Status in linux package in Ubuntu: Incomplete Status in linux-riscv package in Ubuntu: New Status in linux source package in Focal: Incomplete Status in linux-riscv source package in Focal: New Status in linux source package in Groovy: Incomplete Status in linux-riscv source package in Groovy: New Bug description: # apt install linux-libc-dev:amd64 linux-libc-dev:riscv64 Reading package lists... Done Building dependency tree Reading state information... Done linux-libc-dev is already the newest version (5.4.0-26.30). Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: linux-libc-dev : Breaks: linux-libc-dev:riscv64 (!= 5.4.0-26.30) but 5.4.0-27.31 is to be installed linux-libc-dev:riscv64 : Breaks: linux-libc-dev (!= 5.4.0-27.31) but 5.4.0-26.30 is to be installed E: Unable to correct problems, you have held broken packages. $ rmadison -S linux-libc-dev | grep -e riscv64 -e amd64 | grep -e focal -e groovy linux-libc-dev | 5.4.0-24.28| focal| riscv64 linux-libc-dev | 5.4.0-26.30| focal| amd64, arm64, armhf, i386, ppc64el, s390x linux-libc-dev | 5.4.0-26.30| groovy | amd64, arm64, armhf, i386, ppc64el, s390x linux-libc-dev | 5.4.0-27.31| groovy | riscv64 linux-libc-dev | 5.4.0-28.32| focal-security | riscv64 linux-libc-dev | 5.4.0-28.32| focal-updates| riscv64 linux-libc-dev | 5.4.0-40.44| focal-security | amd64, arm64, armhf, i386, ppc64el, s390x linux-libc-dev | 5.4.0-40.44| focal-updates| amd64, arm64, armhf, i386, ppc64el, s390x linux-libc-dev | 5.4.0-40.44| groovy-proposed | amd64, arm64, armhf, i386, ppc64el, s390x This is broken. linux-libc-dev must have identical content for common files, across all architectures, and must have identical version number. A few ways to fix this: * Either enforce that src:linux & src:linux-riscv are at the same version number. But then reasons for splitting riscv into a separate build dissappear * Make src:linux build _just_ the headers linux-libc-dev for risv64, and nothing else. And stop bulding linux-libc-dev form the src:linux- riscv package. Just like it does for i386. * Or create new src:linux-headers that only builds linux-libc-dev for all architectures, without building any kernels. This way for example, we could rev userspace headers to v5.8/v5.9 ahead of said kernel landing, to shake out build-failures / userspace issues, whilst the kernel itself is still baking in bootstrap/proposed PPA. This must be address in Focal and Groovy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886188/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886188] Re: linux-libc-dev broken for crossbuilding, Multi-Arch:same violation
** Changed in: linux (Ubuntu Focal) Status: Incomplete => New ** Changed in: linux (Ubuntu Groovy) Status: Incomplete => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1886188 Title: linux-libc-dev broken for crossbuilding, Multi-Arch:same violation Status in linux package in Ubuntu: Incomplete Status in linux-riscv package in Ubuntu: New Status in linux source package in Focal: Incomplete Status in linux-riscv source package in Focal: New Status in linux source package in Groovy: Incomplete Status in linux-riscv source package in Groovy: New Bug description: # apt install linux-libc-dev:amd64 linux-libc-dev:riscv64 Reading package lists... Done Building dependency tree Reading state information... Done linux-libc-dev is already the newest version (5.4.0-26.30). Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: linux-libc-dev : Breaks: linux-libc-dev:riscv64 (!= 5.4.0-26.30) but 5.4.0-27.31 is to be installed linux-libc-dev:riscv64 : Breaks: linux-libc-dev (!= 5.4.0-27.31) but 5.4.0-26.30 is to be installed E: Unable to correct problems, you have held broken packages. $ rmadison -S linux-libc-dev | grep -e riscv64 -e amd64 | grep -e focal -e groovy linux-libc-dev | 5.4.0-24.28| focal| riscv64 linux-libc-dev | 5.4.0-26.30| focal| amd64, arm64, armhf, i386, ppc64el, s390x linux-libc-dev | 5.4.0-26.30| groovy | amd64, arm64, armhf, i386, ppc64el, s390x linux-libc-dev | 5.4.0-27.31| groovy | riscv64 linux-libc-dev | 5.4.0-28.32| focal-security | riscv64 linux-libc-dev | 5.4.0-28.32| focal-updates| riscv64 linux-libc-dev | 5.4.0-40.44| focal-security | amd64, arm64, armhf, i386, ppc64el, s390x linux-libc-dev | 5.4.0-40.44| focal-updates| amd64, arm64, armhf, i386, ppc64el, s390x linux-libc-dev | 5.4.0-40.44| groovy-proposed | amd64, arm64, armhf, i386, ppc64el, s390x This is broken. linux-libc-dev must have identical content for common files, across all architectures, and must have identical version number. A few ways to fix this: * Either enforce that src:linux & src:linux-riscv are at the same version number. But then reasons for splitting riscv into a separate build dissappear * Make src:linux build _just_ the headers linux-libc-dev for risv64, and nothing else. And stop bulding linux-libc-dev form the src:linux- riscv package. Just like it does for i386. * Or create new src:linux-headers that only builds linux-libc-dev for all architectures, without building any kernels. This way for example, we could rev userspace headers to v5.8/v5.9 ahead of said kernel landing, to shake out build-failures / userspace issues, whilst the kernel itself is still baking in bootstrap/proposed PPA. This must be address in Focal and Groovy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886188/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886341] Re: Kernel Regression between 5.4.0-26 and 5.4.0-40 causes laptop internal audio devices to fail to load w/o unacceptable workaround
Maybe it is: apport-collect 1886341 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1886341 Title: Kernel Regression between 5.4.0-26 and 5.4.0-40 causes laptop internal audio devices to fail to load w/o unacceptable workaround Status in linux package in Ubuntu: Confirmed Bug description: On Ubuntu 20.04, running kernel 5.4.0-40-generic, the internal speakers, headphone jack, and mic do not work at all. No audio devices appear in the Sound settings or in pavucontrol. By appending options snd_hda_intel dmic_detect=0 to /etc/modprobe.d/alsa-base.conf, I can get audio working, but the microphone (unsuprisingly) does not work. Appending options snd-intel-dspcfg dsp_driver=1 to alsa_base.conf as the same effect as dmic_detect=0. Attempts to fix with option snd_hda_intel device=generic or deveice=auto have had no effect. This bug does NOT manifest on 5.4.0-26-generic, the kernel version featured on the 20.04 live media. After installation, and updating to 5.4.0-40-generic, the bug manifests on the next boot. Note that the audio hardware seems to work properly w/o workaround on a small (< 5%) percentage of boots, but I have been unable to reproduce this. With the workaround enabled, inxi -A gives Audio: Device-1: Intel Smart Sound Audio driver: snd_hda_intel Sound Server: ALSA v: k5.4.0-40-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jill 1374 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 5 13:32:58 2020 InstallationDate: Installed on 2020-07-03 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YK 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.4.0-40-generic root=UUID=dc3e058d-42fc-4de4-b94a-749c1295dc68 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: 03/18/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DPCN40WW 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 5 15IIL05 dmi.modalias: dmi:bvnLENOVO:bvrDPCN40WW:bd03/18/2020:svnLENOVO:pn81YK:pvrIdeaPad515IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrIdeaPad515IIL05: dmi.product.family: IdeaPad 5 15IIL05 dmi.product.name: 81YK dmi.product.sku: LENOVO_MT_81YK_BU_idea_FM_IdeaPad 5 15IIL05 dmi.product.version: IdeaPad 5 15IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886341/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1885271] Re: kernel oops xr-usb-serial
Rebuilt with the following rollbacks solves the issue: commit e8bf446f. commit a0b8e0a5. commit ea3d6ff7. commit 69ffb0b1. Of course it would be nicer to solve without rolling back all those commits -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1885271 Title: kernel oops xr-usb-serial Status in linux package in Ubuntu: Confirmed Bug description: # Steps to reproduce # Working case uname -a Linux ubuntu 4.15.0-91-generic #92-Ubuntu SMP Fri Feb 28 11:09:48 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux lsusb -d 04e2:1411 -v > xr-usb-serial-devices.txt lsusb -t >> xr-usb-serial-devices.txt # Unbind 2 xr-usb-serial devices echo '3-14.1' | tee /sys/bus/usb/drivers/usb/unbind echo '3-14.3' | tee /sys/bus/usb/drivers/usb/unbind dmesg > dmesg.txt # Non working case uname -a Linux ubuntu 4.15.0-99-generic #100-Ubuntu SMP Wed Apr 22 20:32:56 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux lsusb -d 04e2:1411 -v > xr-usb-serial-devices.txt dmesg > dmesg.txt This regression is almost certainly caused by one of the 2020-03-11 commits: https://kernel.ubuntu.com/git/ubuntu/ubuntu-bionic.git/log/ubuntu/xr-usb-serial?h=Ubuntu-4.15.0-99.100&id=5966ed54d467fa77e7dbd7355177a5a6d1db7004 files attached in tar file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885271/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886341] Re: Kernel Regression between 5.4.0-26 and 5.4.0-40 causes laptop internal audio devices to fail to load w/o unacceptable workaround
ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: XFCE DistroRelease: Linux Mint 20 InstallationDate: Installed on 2020-07-04 (3 days ago) InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624 MachineType: LENOVO 81YK Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=2e46f6f5-ae2b-4993-988a-aecc4571b463 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 Tags: ulyana Uname: Linux 5.4.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/15/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DPCN39WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 5 15IIL05 dmi.modalias: dmi:bvnLENOVO:bvrDPCN39WW:bd01/15/2020:svnLENOVO:pn81YK:pvrIdeaPad515IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrIdeaPad515IIL05: dmi.product.family: IdeaPad 5 15IIL05 dmi.product.name: 81YK dmi.product.sku: LENOVO_MT_81YK_BU_idea_FM_IdeaPad 5 15IIL05 dmi.product.version: IdeaPad 5 15IIL05 dmi.sys.vendor: LENOVO ** Tags added: apport-collected ulyana -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1886341 Title: Kernel Regression between 5.4.0-26 and 5.4.0-40 causes laptop internal audio devices to fail to load w/o unacceptable workaround Status in linux package in Ubuntu: Confirmed Bug description: On Ubuntu 20.04, running kernel 5.4.0-40-generic, the internal speakers, headphone jack, and mic do not work at all. No audio devices appear in the Sound settings or in pavucontrol. By appending options snd_hda_intel dmic_detect=0 to /etc/modprobe.d/alsa-base.conf, I can get audio working, but the microphone (unsuprisingly) does not work. Appending options snd-intel-dspcfg dsp_driver=1 to alsa_base.conf as the same effect as dmic_detect=0. Attempts to fix with option snd_hda_intel device=generic or deveice=auto have had no effect. This bug does NOT manifest on 5.4.0-26-generic, the kernel version featured on the 20.04 live media. After installation, and updating to 5.4.0-40-generic, the bug manifests on the next boot. Note that the audio hardware seems to work properly w/o workaround on a small (< 5%) percentage of boots, but I have been unable to reproduce this. With the workaround enabled, inxi -A gives Audio: Device-1: Intel Smart Sound Audio driver: snd_hda_intel Sound Server: ALSA v: k5.4.0-40-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jill 1374 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 5 13:32:58 2020 InstallationDate: Installed on 2020-07-03 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YK 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.4.0-40-generic root=UUID=dc3e058d-42fc-4de4-b94a-749c1295dc68 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: 03/18/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DPCN40WW 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 5 15IIL05 dmi.modalias: dmi:bvnLENOVO:bvrDPCN40WW:bd03/18/2020:svnLENOVO:pn81YK:pvrIdeaPad515IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrIdeaPad515IIL05: dmi.product.family: IdeaPad 5 15IIL05 dmi.product.name: 81YK dmi.product.sku: LENOVO_MT_81YK_BU_idea_FM_IdeaPad 5 15IIL05 dmi.product.version: IdeaPad 5 15IIL
[Kernel-packages] [Bug 1886341] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1886341/+attachment/5390767/+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/1886341 Title: Kernel Regression between 5.4.0-26 and 5.4.0-40 causes laptop internal audio devices to fail to load w/o unacceptable workaround Status in linux package in Ubuntu: Confirmed Bug description: On Ubuntu 20.04, running kernel 5.4.0-40-generic, the internal speakers, headphone jack, and mic do not work at all. No audio devices appear in the Sound settings or in pavucontrol. By appending options snd_hda_intel dmic_detect=0 to /etc/modprobe.d/alsa-base.conf, I can get audio working, but the microphone (unsuprisingly) does not work. Appending options snd-intel-dspcfg dsp_driver=1 to alsa_base.conf as the same effect as dmic_detect=0. Attempts to fix with option snd_hda_intel device=generic or deveice=auto have had no effect. This bug does NOT manifest on 5.4.0-26-generic, the kernel version featured on the 20.04 live media. After installation, and updating to 5.4.0-40-generic, the bug manifests on the next boot. Note that the audio hardware seems to work properly w/o workaround on a small (< 5%) percentage of boots, but I have been unable to reproduce this. With the workaround enabled, inxi -A gives Audio: Device-1: Intel Smart Sound Audio driver: snd_hda_intel Sound Server: ALSA v: k5.4.0-40-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jill 1374 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 5 13:32:58 2020 InstallationDate: Installed on 2020-07-03 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YK 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.4.0-40-generic root=UUID=dc3e058d-42fc-4de4-b94a-749c1295dc68 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: 03/18/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DPCN40WW 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 5 15IIL05 dmi.modalias: dmi:bvnLENOVO:bvrDPCN40WW:bd03/18/2020:svnLENOVO:pn81YK:pvrIdeaPad515IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrIdeaPad515IIL05: dmi.product.family: IdeaPad 5 15IIL05 dmi.product.name: 81YK dmi.product.sku: LENOVO_MT_81YK_BU_idea_FM_IdeaPad 5 15IIL05 dmi.product.version: IdeaPad 5 15IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886341/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886341] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1886341/+attachment/5390779/+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/1886341 Title: Kernel Regression between 5.4.0-26 and 5.4.0-40 causes laptop internal audio devices to fail to load w/o unacceptable workaround Status in linux package in Ubuntu: Confirmed Bug description: On Ubuntu 20.04, running kernel 5.4.0-40-generic, the internal speakers, headphone jack, and mic do not work at all. No audio devices appear in the Sound settings or in pavucontrol. By appending options snd_hda_intel dmic_detect=0 to /etc/modprobe.d/alsa-base.conf, I can get audio working, but the microphone (unsuprisingly) does not work. Appending options snd-intel-dspcfg dsp_driver=1 to alsa_base.conf as the same effect as dmic_detect=0. Attempts to fix with option snd_hda_intel device=generic or deveice=auto have had no effect. This bug does NOT manifest on 5.4.0-26-generic, the kernel version featured on the 20.04 live media. After installation, and updating to 5.4.0-40-generic, the bug manifests on the next boot. Note that the audio hardware seems to work properly w/o workaround on a small (< 5%) percentage of boots, but I have been unable to reproduce this. With the workaround enabled, inxi -A gives Audio: Device-1: Intel Smart Sound Audio driver: snd_hda_intel Sound Server: ALSA v: k5.4.0-40-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jill 1374 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 5 13:32:58 2020 InstallationDate: Installed on 2020-07-03 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YK 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.4.0-40-generic root=UUID=dc3e058d-42fc-4de4-b94a-749c1295dc68 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: 03/18/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DPCN40WW 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 5 15IIL05 dmi.modalias: dmi:bvnLENOVO:bvrDPCN40WW:bd03/18/2020:svnLENOVO:pn81YK:pvrIdeaPad515IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrIdeaPad515IIL05: dmi.product.family: IdeaPad 5 15IIL05 dmi.product.name: 81YK dmi.product.sku: LENOVO_MT_81YK_BU_idea_FM_IdeaPad 5 15IIL05 dmi.product.version: IdeaPad 5 15IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886341/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886341] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1886341/+attachment/5390776/+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/1886341 Title: Kernel Regression between 5.4.0-26 and 5.4.0-40 causes laptop internal audio devices to fail to load w/o unacceptable workaround Status in linux package in Ubuntu: Confirmed Bug description: On Ubuntu 20.04, running kernel 5.4.0-40-generic, the internal speakers, headphone jack, and mic do not work at all. No audio devices appear in the Sound settings or in pavucontrol. By appending options snd_hda_intel dmic_detect=0 to /etc/modprobe.d/alsa-base.conf, I can get audio working, but the microphone (unsuprisingly) does not work. Appending options snd-intel-dspcfg dsp_driver=1 to alsa_base.conf as the same effect as dmic_detect=0. Attempts to fix with option snd_hda_intel device=generic or deveice=auto have had no effect. This bug does NOT manifest on 5.4.0-26-generic, the kernel version featured on the 20.04 live media. After installation, and updating to 5.4.0-40-generic, the bug manifests on the next boot. Note that the audio hardware seems to work properly w/o workaround on a small (< 5%) percentage of boots, but I have been unable to reproduce this. With the workaround enabled, inxi -A gives Audio: Device-1: Intel Smart Sound Audio driver: snd_hda_intel Sound Server: ALSA v: k5.4.0-40-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jill 1374 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 5 13:32:58 2020 InstallationDate: Installed on 2020-07-03 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YK 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.4.0-40-generic root=UUID=dc3e058d-42fc-4de4-b94a-749c1295dc68 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: 03/18/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DPCN40WW 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 5 15IIL05 dmi.modalias: dmi:bvnLENOVO:bvrDPCN40WW:bd03/18/2020:svnLENOVO:pn81YK:pvrIdeaPad515IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrIdeaPad515IIL05: dmi.product.family: IdeaPad 5 15IIL05 dmi.product.name: 81YK dmi.product.sku: LENOVO_MT_81YK_BU_idea_FM_IdeaPad 5 15IIL05 dmi.product.version: IdeaPad 5 15IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886341/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886341] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1886341/+attachment/5390782/+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/1886341 Title: Kernel Regression between 5.4.0-26 and 5.4.0-40 causes laptop internal audio devices to fail to load w/o unacceptable workaround Status in linux package in Ubuntu: Confirmed Bug description: On Ubuntu 20.04, running kernel 5.4.0-40-generic, the internal speakers, headphone jack, and mic do not work at all. No audio devices appear in the Sound settings or in pavucontrol. By appending options snd_hda_intel dmic_detect=0 to /etc/modprobe.d/alsa-base.conf, I can get audio working, but the microphone (unsuprisingly) does not work. Appending options snd-intel-dspcfg dsp_driver=1 to alsa_base.conf as the same effect as dmic_detect=0. Attempts to fix with option snd_hda_intel device=generic or deveice=auto have had no effect. This bug does NOT manifest on 5.4.0-26-generic, the kernel version featured on the 20.04 live media. After installation, and updating to 5.4.0-40-generic, the bug manifests on the next boot. Note that the audio hardware seems to work properly w/o workaround on a small (< 5%) percentage of boots, but I have been unable to reproduce this. With the workaround enabled, inxi -A gives Audio: Device-1: Intel Smart Sound Audio driver: snd_hda_intel Sound Server: ALSA v: k5.4.0-40-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jill 1374 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 5 13:32:58 2020 InstallationDate: Installed on 2020-07-03 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YK 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.4.0-40-generic root=UUID=dc3e058d-42fc-4de4-b94a-749c1295dc68 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: 03/18/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DPCN40WW 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 5 15IIL05 dmi.modalias: dmi:bvnLENOVO:bvrDPCN40WW:bd03/18/2020:svnLENOVO:pn81YK:pvrIdeaPad515IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrIdeaPad515IIL05: dmi.product.family: IdeaPad 5 15IIL05 dmi.product.name: 81YK dmi.product.sku: LENOVO_MT_81YK_BU_idea_FM_IdeaPad 5 15IIL05 dmi.product.version: IdeaPad 5 15IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886341/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886341] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1886341/+attachment/5390784/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1886341 Title: Kernel Regression between 5.4.0-26 and 5.4.0-40 causes laptop internal audio devices to fail to load w/o unacceptable workaround Status in linux package in Ubuntu: Confirmed Bug description: On Ubuntu 20.04, running kernel 5.4.0-40-generic, the internal speakers, headphone jack, and mic do not work at all. No audio devices appear in the Sound settings or in pavucontrol. By appending options snd_hda_intel dmic_detect=0 to /etc/modprobe.d/alsa-base.conf, I can get audio working, but the microphone (unsuprisingly) does not work. Appending options snd-intel-dspcfg dsp_driver=1 to alsa_base.conf as the same effect as dmic_detect=0. Attempts to fix with option snd_hda_intel device=generic or deveice=auto have had no effect. This bug does NOT manifest on 5.4.0-26-generic, the kernel version featured on the 20.04 live media. After installation, and updating to 5.4.0-40-generic, the bug manifests on the next boot. Note that the audio hardware seems to work properly w/o workaround on a small (< 5%) percentage of boots, but I have been unable to reproduce this. With the workaround enabled, inxi -A gives Audio: Device-1: Intel Smart Sound Audio driver: snd_hda_intel Sound Server: ALSA v: k5.4.0-40-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jill 1374 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 5 13:32:58 2020 InstallationDate: Installed on 2020-07-03 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YK 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.4.0-40-generic root=UUID=dc3e058d-42fc-4de4-b94a-749c1295dc68 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: 03/18/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DPCN40WW 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 5 15IIL05 dmi.modalias: dmi:bvnLENOVO:bvrDPCN40WW:bd03/18/2020:svnLENOVO:pn81YK:pvrIdeaPad515IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrIdeaPad515IIL05: dmi.product.family: IdeaPad 5 15IIL05 dmi.product.name: 81YK dmi.product.sku: LENOVO_MT_81YK_BU_idea_FM_IdeaPad 5 15IIL05 dmi.product.version: IdeaPad 5 15IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886341/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886341] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1886341/+attachment/5390773/+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/1886341 Title: Kernel Regression between 5.4.0-26 and 5.4.0-40 causes laptop internal audio devices to fail to load w/o unacceptable workaround Status in linux package in Ubuntu: Confirmed Bug description: On Ubuntu 20.04, running kernel 5.4.0-40-generic, the internal speakers, headphone jack, and mic do not work at all. No audio devices appear in the Sound settings or in pavucontrol. By appending options snd_hda_intel dmic_detect=0 to /etc/modprobe.d/alsa-base.conf, I can get audio working, but the microphone (unsuprisingly) does not work. Appending options snd-intel-dspcfg dsp_driver=1 to alsa_base.conf as the same effect as dmic_detect=0. Attempts to fix with option snd_hda_intel device=generic or deveice=auto have had no effect. This bug does NOT manifest on 5.4.0-26-generic, the kernel version featured on the 20.04 live media. After installation, and updating to 5.4.0-40-generic, the bug manifests on the next boot. Note that the audio hardware seems to work properly w/o workaround on a small (< 5%) percentage of boots, but I have been unable to reproduce this. With the workaround enabled, inxi -A gives Audio: Device-1: Intel Smart Sound Audio driver: snd_hda_intel Sound Server: ALSA v: k5.4.0-40-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jill 1374 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 5 13:32:58 2020 InstallationDate: Installed on 2020-07-03 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YK 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.4.0-40-generic root=UUID=dc3e058d-42fc-4de4-b94a-749c1295dc68 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: 03/18/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DPCN40WW 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 5 15IIL05 dmi.modalias: dmi:bvnLENOVO:bvrDPCN40WW:bd03/18/2020:svnLENOVO:pn81YK:pvrIdeaPad515IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrIdeaPad515IIL05: dmi.product.family: IdeaPad 5 15IIL05 dmi.product.name: 81YK dmi.product.sku: LENOVO_MT_81YK_BU_idea_FM_IdeaPad 5 15IIL05 dmi.product.version: IdeaPad 5 15IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886341/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886341] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1886341/+attachment/5390777/+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/1886341 Title: Kernel Regression between 5.4.0-26 and 5.4.0-40 causes laptop internal audio devices to fail to load w/o unacceptable workaround Status in linux package in Ubuntu: Confirmed Bug description: On Ubuntu 20.04, running kernel 5.4.0-40-generic, the internal speakers, headphone jack, and mic do not work at all. No audio devices appear in the Sound settings or in pavucontrol. By appending options snd_hda_intel dmic_detect=0 to /etc/modprobe.d/alsa-base.conf, I can get audio working, but the microphone (unsuprisingly) does not work. Appending options snd-intel-dspcfg dsp_driver=1 to alsa_base.conf as the same effect as dmic_detect=0. Attempts to fix with option snd_hda_intel device=generic or deveice=auto have had no effect. This bug does NOT manifest on 5.4.0-26-generic, the kernel version featured on the 20.04 live media. After installation, and updating to 5.4.0-40-generic, the bug manifests on the next boot. Note that the audio hardware seems to work properly w/o workaround on a small (< 5%) percentage of boots, but I have been unable to reproduce this. With the workaround enabled, inxi -A gives Audio: Device-1: Intel Smart Sound Audio driver: snd_hda_intel Sound Server: ALSA v: k5.4.0-40-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jill 1374 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 5 13:32:58 2020 InstallationDate: Installed on 2020-07-03 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YK 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.4.0-40-generic root=UUID=dc3e058d-42fc-4de4-b94a-749c1295dc68 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: 03/18/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DPCN40WW 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 5 15IIL05 dmi.modalias: dmi:bvnLENOVO:bvrDPCN40WW:bd03/18/2020:svnLENOVO:pn81YK:pvrIdeaPad515IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrIdeaPad515IIL05: dmi.product.family: IdeaPad 5 15IIL05 dmi.product.name: 81YK dmi.product.sku: LENOVO_MT_81YK_BU_idea_FM_IdeaPad 5 15IIL05 dmi.product.version: IdeaPad 5 15IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886341/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886341] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1886341/+attachment/5390768/+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/1886341 Title: Kernel Regression between 5.4.0-26 and 5.4.0-40 causes laptop internal audio devices to fail to load w/o unacceptable workaround Status in linux package in Ubuntu: Confirmed Bug description: On Ubuntu 20.04, running kernel 5.4.0-40-generic, the internal speakers, headphone jack, and mic do not work at all. No audio devices appear in the Sound settings or in pavucontrol. By appending options snd_hda_intel dmic_detect=0 to /etc/modprobe.d/alsa-base.conf, I can get audio working, but the microphone (unsuprisingly) does not work. Appending options snd-intel-dspcfg dsp_driver=1 to alsa_base.conf as the same effect as dmic_detect=0. Attempts to fix with option snd_hda_intel device=generic or deveice=auto have had no effect. This bug does NOT manifest on 5.4.0-26-generic, the kernel version featured on the 20.04 live media. After installation, and updating to 5.4.0-40-generic, the bug manifests on the next boot. Note that the audio hardware seems to work properly w/o workaround on a small (< 5%) percentage of boots, but I have been unable to reproduce this. With the workaround enabled, inxi -A gives Audio: Device-1: Intel Smart Sound Audio driver: snd_hda_intel Sound Server: ALSA v: k5.4.0-40-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jill 1374 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 5 13:32:58 2020 InstallationDate: Installed on 2020-07-03 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YK 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.4.0-40-generic root=UUID=dc3e058d-42fc-4de4-b94a-749c1295dc68 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: 03/18/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DPCN40WW 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 5 15IIL05 dmi.modalias: dmi:bvnLENOVO:bvrDPCN40WW:bd03/18/2020:svnLENOVO:pn81YK:pvrIdeaPad515IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrIdeaPad515IIL05: dmi.product.family: IdeaPad 5 15IIL05 dmi.product.name: 81YK dmi.product.sku: LENOVO_MT_81YK_BU_idea_FM_IdeaPad 5 15IIL05 dmi.product.version: IdeaPad 5 15IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886341/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886341] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1886341/+attachment/5390769/+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/1886341 Title: Kernel Regression between 5.4.0-26 and 5.4.0-40 causes laptop internal audio devices to fail to load w/o unacceptable workaround Status in linux package in Ubuntu: Confirmed Bug description: On Ubuntu 20.04, running kernel 5.4.0-40-generic, the internal speakers, headphone jack, and mic do not work at all. No audio devices appear in the Sound settings or in pavucontrol. By appending options snd_hda_intel dmic_detect=0 to /etc/modprobe.d/alsa-base.conf, I can get audio working, but the microphone (unsuprisingly) does not work. Appending options snd-intel-dspcfg dsp_driver=1 to alsa_base.conf as the same effect as dmic_detect=0. Attempts to fix with option snd_hda_intel device=generic or deveice=auto have had no effect. This bug does NOT manifest on 5.4.0-26-generic, the kernel version featured on the 20.04 live media. After installation, and updating to 5.4.0-40-generic, the bug manifests on the next boot. Note that the audio hardware seems to work properly w/o workaround on a small (< 5%) percentage of boots, but I have been unable to reproduce this. With the workaround enabled, inxi -A gives Audio: Device-1: Intel Smart Sound Audio driver: snd_hda_intel Sound Server: ALSA v: k5.4.0-40-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jill 1374 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 5 13:32:58 2020 InstallationDate: Installed on 2020-07-03 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YK 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.4.0-40-generic root=UUID=dc3e058d-42fc-4de4-b94a-749c1295dc68 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: 03/18/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DPCN40WW 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 5 15IIL05 dmi.modalias: dmi:bvnLENOVO:bvrDPCN40WW:bd03/18/2020:svnLENOVO:pn81YK:pvrIdeaPad515IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrIdeaPad515IIL05: dmi.product.family: IdeaPad 5 15IIL05 dmi.product.name: 81YK dmi.product.sku: LENOVO_MT_81YK_BU_idea_FM_IdeaPad 5 15IIL05 dmi.product.version: IdeaPad 5 15IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886341/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886341] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1886341/+attachment/5390771/+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/1886341 Title: Kernel Regression between 5.4.0-26 and 5.4.0-40 causes laptop internal audio devices to fail to load w/o unacceptable workaround Status in linux package in Ubuntu: Confirmed Bug description: On Ubuntu 20.04, running kernel 5.4.0-40-generic, the internal speakers, headphone jack, and mic do not work at all. No audio devices appear in the Sound settings or in pavucontrol. By appending options snd_hda_intel dmic_detect=0 to /etc/modprobe.d/alsa-base.conf, I can get audio working, but the microphone (unsuprisingly) does not work. Appending options snd-intel-dspcfg dsp_driver=1 to alsa_base.conf as the same effect as dmic_detect=0. Attempts to fix with option snd_hda_intel device=generic or deveice=auto have had no effect. This bug does NOT manifest on 5.4.0-26-generic, the kernel version featured on the 20.04 live media. After installation, and updating to 5.4.0-40-generic, the bug manifests on the next boot. Note that the audio hardware seems to work properly w/o workaround on a small (< 5%) percentage of boots, but I have been unable to reproduce this. With the workaround enabled, inxi -A gives Audio: Device-1: Intel Smart Sound Audio driver: snd_hda_intel Sound Server: ALSA v: k5.4.0-40-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jill 1374 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 5 13:32:58 2020 InstallationDate: Installed on 2020-07-03 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YK 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.4.0-40-generic root=UUID=dc3e058d-42fc-4de4-b94a-749c1295dc68 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: 03/18/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DPCN40WW 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 5 15IIL05 dmi.modalias: dmi:bvnLENOVO:bvrDPCN40WW:bd03/18/2020:svnLENOVO:pn81YK:pvrIdeaPad515IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrIdeaPad515IIL05: dmi.product.family: IdeaPad 5 15IIL05 dmi.product.name: 81YK dmi.product.sku: LENOVO_MT_81YK_BU_idea_FM_IdeaPad 5 15IIL05 dmi.product.version: IdeaPad 5 15IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886341/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886341] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1886341/+attachment/5390772/+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/1886341 Title: Kernel Regression between 5.4.0-26 and 5.4.0-40 causes laptop internal audio devices to fail to load w/o unacceptable workaround Status in linux package in Ubuntu: Confirmed Bug description: On Ubuntu 20.04, running kernel 5.4.0-40-generic, the internal speakers, headphone jack, and mic do not work at all. No audio devices appear in the Sound settings or in pavucontrol. By appending options snd_hda_intel dmic_detect=0 to /etc/modprobe.d/alsa-base.conf, I can get audio working, but the microphone (unsuprisingly) does not work. Appending options snd-intel-dspcfg dsp_driver=1 to alsa_base.conf as the same effect as dmic_detect=0. Attempts to fix with option snd_hda_intel device=generic or deveice=auto have had no effect. This bug does NOT manifest on 5.4.0-26-generic, the kernel version featured on the 20.04 live media. After installation, and updating to 5.4.0-40-generic, the bug manifests on the next boot. Note that the audio hardware seems to work properly w/o workaround on a small (< 5%) percentage of boots, but I have been unable to reproduce this. With the workaround enabled, inxi -A gives Audio: Device-1: Intel Smart Sound Audio driver: snd_hda_intel Sound Server: ALSA v: k5.4.0-40-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jill 1374 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 5 13:32:58 2020 InstallationDate: Installed on 2020-07-03 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YK 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.4.0-40-generic root=UUID=dc3e058d-42fc-4de4-b94a-749c1295dc68 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: 03/18/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DPCN40WW 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 5 15IIL05 dmi.modalias: dmi:bvnLENOVO:bvrDPCN40WW:bd03/18/2020:svnLENOVO:pn81YK:pvrIdeaPad515IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrIdeaPad515IIL05: dmi.product.family: IdeaPad 5 15IIL05 dmi.product.name: 81YK dmi.product.sku: LENOVO_MT_81YK_BU_idea_FM_IdeaPad 5 15IIL05 dmi.product.version: IdeaPad 5 15IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886341/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886341] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1886341/+attachment/5390770/+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/1886341 Title: Kernel Regression between 5.4.0-26 and 5.4.0-40 causes laptop internal audio devices to fail to load w/o unacceptable workaround Status in linux package in Ubuntu: Confirmed Bug description: On Ubuntu 20.04, running kernel 5.4.0-40-generic, the internal speakers, headphone jack, and mic do not work at all. No audio devices appear in the Sound settings or in pavucontrol. By appending options snd_hda_intel dmic_detect=0 to /etc/modprobe.d/alsa-base.conf, I can get audio working, but the microphone (unsuprisingly) does not work. Appending options snd-intel-dspcfg dsp_driver=1 to alsa_base.conf as the same effect as dmic_detect=0. Attempts to fix with option snd_hda_intel device=generic or deveice=auto have had no effect. This bug does NOT manifest on 5.4.0-26-generic, the kernel version featured on the 20.04 live media. After installation, and updating to 5.4.0-40-generic, the bug manifests on the next boot. Note that the audio hardware seems to work properly w/o workaround on a small (< 5%) percentage of boots, but I have been unable to reproduce this. With the workaround enabled, inxi -A gives Audio: Device-1: Intel Smart Sound Audio driver: snd_hda_intel Sound Server: ALSA v: k5.4.0-40-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jill 1374 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 5 13:32:58 2020 InstallationDate: Installed on 2020-07-03 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YK 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.4.0-40-generic root=UUID=dc3e058d-42fc-4de4-b94a-749c1295dc68 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: 03/18/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DPCN40WW 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 5 15IIL05 dmi.modalias: dmi:bvnLENOVO:bvrDPCN40WW:bd03/18/2020:svnLENOVO:pn81YK:pvrIdeaPad515IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrIdeaPad515IIL05: dmi.product.family: IdeaPad 5 15IIL05 dmi.product.name: 81YK dmi.product.sku: LENOVO_MT_81YK_BU_idea_FM_IdeaPad 5 15IIL05 dmi.product.version: IdeaPad 5 15IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886341/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886341] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1886341/+attachment/5390774/+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/1886341 Title: Kernel Regression between 5.4.0-26 and 5.4.0-40 causes laptop internal audio devices to fail to load w/o unacceptable workaround Status in linux package in Ubuntu: Confirmed Bug description: On Ubuntu 20.04, running kernel 5.4.0-40-generic, the internal speakers, headphone jack, and mic do not work at all. No audio devices appear in the Sound settings or in pavucontrol. By appending options snd_hda_intel dmic_detect=0 to /etc/modprobe.d/alsa-base.conf, I can get audio working, but the microphone (unsuprisingly) does not work. Appending options snd-intel-dspcfg dsp_driver=1 to alsa_base.conf as the same effect as dmic_detect=0. Attempts to fix with option snd_hda_intel device=generic or deveice=auto have had no effect. This bug does NOT manifest on 5.4.0-26-generic, the kernel version featured on the 20.04 live media. After installation, and updating to 5.4.0-40-generic, the bug manifests on the next boot. Note that the audio hardware seems to work properly w/o workaround on a small (< 5%) percentage of boots, but I have been unable to reproduce this. With the workaround enabled, inxi -A gives Audio: Device-1: Intel Smart Sound Audio driver: snd_hda_intel Sound Server: ALSA v: k5.4.0-40-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jill 1374 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 5 13:32:58 2020 InstallationDate: Installed on 2020-07-03 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YK 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.4.0-40-generic root=UUID=dc3e058d-42fc-4de4-b94a-749c1295dc68 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: 03/18/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DPCN40WW 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 5 15IIL05 dmi.modalias: dmi:bvnLENOVO:bvrDPCN40WW:bd03/18/2020:svnLENOVO:pn81YK:pvrIdeaPad515IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrIdeaPad515IIL05: dmi.product.family: IdeaPad 5 15IIL05 dmi.product.name: 81YK dmi.product.sku: LENOVO_MT_81YK_BU_idea_FM_IdeaPad 5 15IIL05 dmi.product.version: IdeaPad 5 15IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886341/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886341] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1886341/+attachment/5390780/+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/1886341 Title: Kernel Regression between 5.4.0-26 and 5.4.0-40 causes laptop internal audio devices to fail to load w/o unacceptable workaround Status in linux package in Ubuntu: Confirmed Bug description: On Ubuntu 20.04, running kernel 5.4.0-40-generic, the internal speakers, headphone jack, and mic do not work at all. No audio devices appear in the Sound settings or in pavucontrol. By appending options snd_hda_intel dmic_detect=0 to /etc/modprobe.d/alsa-base.conf, I can get audio working, but the microphone (unsuprisingly) does not work. Appending options snd-intel-dspcfg dsp_driver=1 to alsa_base.conf as the same effect as dmic_detect=0. Attempts to fix with option snd_hda_intel device=generic or deveice=auto have had no effect. This bug does NOT manifest on 5.4.0-26-generic, the kernel version featured on the 20.04 live media. After installation, and updating to 5.4.0-40-generic, the bug manifests on the next boot. Note that the audio hardware seems to work properly w/o workaround on a small (< 5%) percentage of boots, but I have been unable to reproduce this. With the workaround enabled, inxi -A gives Audio: Device-1: Intel Smart Sound Audio driver: snd_hda_intel Sound Server: ALSA v: k5.4.0-40-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jill 1374 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 5 13:32:58 2020 InstallationDate: Installed on 2020-07-03 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YK 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.4.0-40-generic root=UUID=dc3e058d-42fc-4de4-b94a-749c1295dc68 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: 03/18/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DPCN40WW 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 5 15IIL05 dmi.modalias: dmi:bvnLENOVO:bvrDPCN40WW:bd03/18/2020:svnLENOVO:pn81YK:pvrIdeaPad515IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrIdeaPad515IIL05: dmi.product.family: IdeaPad 5 15IIL05 dmi.product.name: 81YK dmi.product.sku: LENOVO_MT_81YK_BU_idea_FM_IdeaPad 5 15IIL05 dmi.product.version: IdeaPad 5 15IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886341/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886341] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1886341/+attachment/5390783/+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/1886341 Title: Kernel Regression between 5.4.0-26 and 5.4.0-40 causes laptop internal audio devices to fail to load w/o unacceptable workaround Status in linux package in Ubuntu: Confirmed Bug description: On Ubuntu 20.04, running kernel 5.4.0-40-generic, the internal speakers, headphone jack, and mic do not work at all. No audio devices appear in the Sound settings or in pavucontrol. By appending options snd_hda_intel dmic_detect=0 to /etc/modprobe.d/alsa-base.conf, I can get audio working, but the microphone (unsuprisingly) does not work. Appending options snd-intel-dspcfg dsp_driver=1 to alsa_base.conf as the same effect as dmic_detect=0. Attempts to fix with option snd_hda_intel device=generic or deveice=auto have had no effect. This bug does NOT manifest on 5.4.0-26-generic, the kernel version featured on the 20.04 live media. After installation, and updating to 5.4.0-40-generic, the bug manifests on the next boot. Note that the audio hardware seems to work properly w/o workaround on a small (< 5%) percentage of boots, but I have been unable to reproduce this. With the workaround enabled, inxi -A gives Audio: Device-1: Intel Smart Sound Audio driver: snd_hda_intel Sound Server: ALSA v: k5.4.0-40-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jill 1374 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 5 13:32:58 2020 InstallationDate: Installed on 2020-07-03 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YK 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.4.0-40-generic root=UUID=dc3e058d-42fc-4de4-b94a-749c1295dc68 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: 03/18/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DPCN40WW 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 5 15IIL05 dmi.modalias: dmi:bvnLENOVO:bvrDPCN40WW:bd03/18/2020:svnLENOVO:pn81YK:pvrIdeaPad515IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrIdeaPad515IIL05: dmi.product.family: IdeaPad 5 15IIL05 dmi.product.name: 81YK dmi.product.sku: LENOVO_MT_81YK_BU_idea_FM_IdeaPad 5 15IIL05 dmi.product.version: IdeaPad 5 15IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886341/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886341] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1886341/+attachment/5390781/+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/1886341 Title: Kernel Regression between 5.4.0-26 and 5.4.0-40 causes laptop internal audio devices to fail to load w/o unacceptable workaround Status in linux package in Ubuntu: Confirmed Bug description: On Ubuntu 20.04, running kernel 5.4.0-40-generic, the internal speakers, headphone jack, and mic do not work at all. No audio devices appear in the Sound settings or in pavucontrol. By appending options snd_hda_intel dmic_detect=0 to /etc/modprobe.d/alsa-base.conf, I can get audio working, but the microphone (unsuprisingly) does not work. Appending options snd-intel-dspcfg dsp_driver=1 to alsa_base.conf as the same effect as dmic_detect=0. Attempts to fix with option snd_hda_intel device=generic or deveice=auto have had no effect. This bug does NOT manifest on 5.4.0-26-generic, the kernel version featured on the 20.04 live media. After installation, and updating to 5.4.0-40-generic, the bug manifests on the next boot. Note that the audio hardware seems to work properly w/o workaround on a small (< 5%) percentage of boots, but I have been unable to reproduce this. With the workaround enabled, inxi -A gives Audio: Device-1: Intel Smart Sound Audio driver: snd_hda_intel Sound Server: ALSA v: k5.4.0-40-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jill 1374 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 5 13:32:58 2020 InstallationDate: Installed on 2020-07-03 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YK 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.4.0-40-generic root=UUID=dc3e058d-42fc-4de4-b94a-749c1295dc68 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: 03/18/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DPCN40WW 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 5 15IIL05 dmi.modalias: dmi:bvnLENOVO:bvrDPCN40WW:bd03/18/2020:svnLENOVO:pn81YK:pvrIdeaPad515IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrIdeaPad515IIL05: dmi.product.family: IdeaPad 5 15IIL05 dmi.product.name: 81YK dmi.product.sku: LENOVO_MT_81YK_BU_idea_FM_IdeaPad 5 15IIL05 dmi.product.version: IdeaPad 5 15IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886341/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886341] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1886341/+attachment/5390775/+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/1886341 Title: Kernel Regression between 5.4.0-26 and 5.4.0-40 causes laptop internal audio devices to fail to load w/o unacceptable workaround Status in linux package in Ubuntu: Confirmed Bug description: On Ubuntu 20.04, running kernel 5.4.0-40-generic, the internal speakers, headphone jack, and mic do not work at all. No audio devices appear in the Sound settings or in pavucontrol. By appending options snd_hda_intel dmic_detect=0 to /etc/modprobe.d/alsa-base.conf, I can get audio working, but the microphone (unsuprisingly) does not work. Appending options snd-intel-dspcfg dsp_driver=1 to alsa_base.conf as the same effect as dmic_detect=0. Attempts to fix with option snd_hda_intel device=generic or deveice=auto have had no effect. This bug does NOT manifest on 5.4.0-26-generic, the kernel version featured on the 20.04 live media. After installation, and updating to 5.4.0-40-generic, the bug manifests on the next boot. Note that the audio hardware seems to work properly w/o workaround on a small (< 5%) percentage of boots, but I have been unable to reproduce this. With the workaround enabled, inxi -A gives Audio: Device-1: Intel Smart Sound Audio driver: snd_hda_intel Sound Server: ALSA v: k5.4.0-40-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jill 1374 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 5 13:32:58 2020 InstallationDate: Installed on 2020-07-03 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YK 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.4.0-40-generic root=UUID=dc3e058d-42fc-4de4-b94a-749c1295dc68 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: 03/18/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DPCN40WW 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 5 15IIL05 dmi.modalias: dmi:bvnLENOVO:bvrDPCN40WW:bd03/18/2020:svnLENOVO:pn81YK:pvrIdeaPad515IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrIdeaPad515IIL05: dmi.product.family: IdeaPad 5 15IIL05 dmi.product.name: 81YK dmi.product.sku: LENOVO_MT_81YK_BU_idea_FM_IdeaPad 5 15IIL05 dmi.product.version: IdeaPad 5 15IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886341/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886341] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1886341/+attachment/5390778/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1886341 Title: Kernel Regression between 5.4.0-26 and 5.4.0-40 causes laptop internal audio devices to fail to load w/o unacceptable workaround Status in linux package in Ubuntu: Confirmed Bug description: On Ubuntu 20.04, running kernel 5.4.0-40-generic, the internal speakers, headphone jack, and mic do not work at all. No audio devices appear in the Sound settings or in pavucontrol. By appending options snd_hda_intel dmic_detect=0 to /etc/modprobe.d/alsa-base.conf, I can get audio working, but the microphone (unsuprisingly) does not work. Appending options snd-intel-dspcfg dsp_driver=1 to alsa_base.conf as the same effect as dmic_detect=0. Attempts to fix with option snd_hda_intel device=generic or deveice=auto have had no effect. This bug does NOT manifest on 5.4.0-26-generic, the kernel version featured on the 20.04 live media. After installation, and updating to 5.4.0-40-generic, the bug manifests on the next boot. Note that the audio hardware seems to work properly w/o workaround on a small (< 5%) percentage of boots, but I have been unable to reproduce this. With the workaround enabled, inxi -A gives Audio: Device-1: Intel Smart Sound Audio driver: snd_hda_intel Sound Server: ALSA v: k5.4.0-40-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jill 1374 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 5 13:32:58 2020 InstallationDate: Installed on 2020-07-03 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YK 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.4.0-40-generic root=UUID=dc3e058d-42fc-4de4-b94a-749c1295dc68 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: 03/18/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DPCN40WW 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 5 15IIL05 dmi.modalias: dmi:bvnLENOVO:bvrDPCN40WW:bd03/18/2020:svnLENOVO:pn81YK:pvrIdeaPad515IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrIdeaPad515IIL05: dmi.product.family: IdeaPad 5 15IIL05 dmi.product.name: 81YK dmi.product.sku: LENOVO_MT_81YK_BU_idea_FM_IdeaPad 5 15IIL05 dmi.product.version: IdeaPad 5 15IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886341/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886814] [NEW] posix_spawn usage in gnu make causes failures on s390x
Public bug reported: posix_spawn usage in gnu make causes failures on s390x Recently in gnu-make v4.3 https://paste.ubuntu.com/p/tYhbJFKN76/ it started to use posix_spawn, instead of fork()/exec(). This has caused failure of an unrelated package flatpak-builder autopkgtests on s390x only, like so echo Building make: echo: Operation not permitted make: *** [Makefile:2: all] Error 127 Julian Klaude investigated this in-depth. His earlier research also indicated that this is a heisenbug, if one tries to print to stderr before printing to stdout, no issue occurs. We are configuring GNU make to be build with --disable-posix-spawn on s390x only. We passed these details to Debian https://bugs.debian.org /cgi-bin/bugreport.cgi?bug=964541 too. But I do wonder, if there is something different or incorrect about posix_spawn() implementation in either glibc, or linux kernel, on s390x. Or gnu-make's usage of posix_spawn(). As otherise, using posix_spawn() in gnu-make works on other architectures, and flatpak-builder autopkgtests pass too. It seems very weird that stdout does not appear to be functional, unless stderr was opened/written to, from gnu-make execution compiled with posix-spawn feature. ** Affects: ubuntu-z-systems Importance: Medium Status: New ** Affects: glibc (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: make-dfsg (Ubuntu) Importance: Undecided Status: New ** Tags: reverse-proxy-bugzilla s390x ** Also affects: glibc (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1886814 Title: posix_spawn usage in gnu make causes failures on s390x Status in Ubuntu on IBM z Systems: New Status in glibc package in Ubuntu: New Status in linux package in Ubuntu: New Status in make-dfsg package in Ubuntu: New Bug description: posix_spawn usage in gnu make causes failures on s390x Recently in gnu-make v4.3 https://paste.ubuntu.com/p/tYhbJFKN76/ it started to use posix_spawn, instead of fork()/exec(). This has caused failure of an unrelated package flatpak-builder autopkgtests on s390x only, like so echo Building make: echo: Operation not permitted make: *** [Makefile:2: all] Error 127 Julian Klaude investigated this in-depth. His earlier research also indicated that this is a heisenbug, if one tries to print to stderr before printing to stdout, no issue occurs. We are configuring GNU make to be build with --disable-posix-spawn on s390x only. We passed these details to Debian https://bugs.debian.org /cgi-bin/bugreport.cgi?bug=964541 too. But I do wonder, if there is something different or incorrect about posix_spawn() implementation in either glibc, or linux kernel, on s390x. Or gnu-make's usage of posix_spawn(). As otherise, using posix_spawn() in gnu-make works on other architectures, and flatpak-builder autopkgtests pass too. It seems very weird that stdout does not appear to be functional, unless stderr was opened/written to, from gnu-make execution compiled with posix-spawn feature. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1886814/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886814] Re: posix_spawn usage in gnu make causes failures on s390x
** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Tags added: reverse-proxy-bugzilla s390x ** Changed in: ubuntu-z-systems Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1886814 Title: posix_spawn usage in gnu make causes failures on s390x Status in Ubuntu on IBM z Systems: New Status in glibc package in Ubuntu: New Status in linux package in Ubuntu: New Status in make-dfsg package in Ubuntu: New Bug description: posix_spawn usage in gnu make causes failures on s390x Recently in gnu-make v4.3 https://paste.ubuntu.com/p/tYhbJFKN76/ it started to use posix_spawn, instead of fork()/exec(). This has caused failure of an unrelated package flatpak-builder autopkgtests on s390x only, like so echo Building make: echo: Operation not permitted make: *** [Makefile:2: all] Error 127 Julian Klaude investigated this in-depth. His earlier research also indicated that this is a heisenbug, if one tries to print to stderr before printing to stdout, no issue occurs. We are configuring GNU make to be build with --disable-posix-spawn on s390x only. We passed these details to Debian https://bugs.debian.org /cgi-bin/bugreport.cgi?bug=964541 too. But I do wonder, if there is something different or incorrect about posix_spawn() implementation in either glibc, or linux kernel, on s390x. Or gnu-make's usage of posix_spawn(). As otherise, using posix_spawn() in gnu-make works on other architectures, and flatpak-builder autopkgtests pass too. It seems very weird that stdout does not appear to be functional, unless stderr was opened/written to, from gnu-make execution compiled with posix-spawn feature. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1886814/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1880421] Re: zfsutils-linux fails to install if `modprobe zfs` fails
Testing -proposed spl: Tested: spl now builds fine on 4.15, 5.3 and 5.4 kernels Tested: ubuntu ZFS autotest smoke and fs on kernels: 5.4 - OK 5.3 - OK 4.15 - OK Looks good to me. -- 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/1880421 Title: zfsutils-linux fails to install if `modprobe zfs` fails Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Focal: Fix Committed Status in zfs-linux source package in Groovy: Fix Released Bug description: == SRU Justification, Focal == Justification: Installing zfsutils with zfs modules not available causes the package to installation to fail. The package should install cleanly rather than break. == Test Case == # Prevent module loading $ sudo sysctl kernel.modules_disabled=1 # Install the package $ sudo apt install -y zfsutils-linux This should succeed. Without the fix this fails. (See below for the failure message). With the fix modules don't install but the package install succeeds. == Regression Potential == There may be users who expect the package to fail to install when the zfs utils fail to install when the modules are not available. However, this is a corner case where users are expecting broken behaviour to occur and should not be relying on this. The changes to the systemd rules are already in Ubuntu groovy and have been tested, so I believe the regression potential is limited. Description: When installing zfsutils-linux, failure to `modprobe zfs` cause the package installation to fail. Ideally, modprobe should be attempted but not fatal. Steps to reproduce: # Prevent module loading $ sudo sysctl kernel.modules_disabled=1 # Install the package $ sudo apt install -y zfsutils-linux This should succeed but fails with: Reading package lists... Done Building dependency tree Reading state information... Done zfsutils-linux is already the newest version (0.8.3-1ubuntu12). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 2 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Setting up zfsutils-linux (0.8.3-1ubuntu12) ... insmod /lib/modules/5.4.0-31-generic/kernel/zfs/zlua.ko modprobe: ERROR: could not insert 'zfs': Operation not permitted zfs-import-scan.service is a disabled or a static unit, not starting it. A dependency job for zfs-import-cache.service failed. See 'journalctl -xe' for details. Job for zfs-load-module.service failed because the control process exited with error code. See "systemctl status zfs-load-module.service" and "journalctl -xe" for details. zfs-import-scan.service is a disabled or a static unit, not starting it. Job for zfs-load-module.service failed because the control process exited with error code. See "systemctl status zfs-load-module.service" and "journalctl -xe" for details. A dependency job for zfs-import-cache.service failed. See 'journalctl -xe' for details. Job for zfs-share.service failed because the control process exited with error code. See "systemctl status zfs-share.service" and "journalctl -xe" for details. invoke-rc.d: initscript zfs-share, action "start" failed. ● zfs-share.service - ZFS file system shares Loaded: loaded (/lib/systemd/system/zfs-share.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Sun 2020-05-24 16:56:03 UTC; 52ms ago Docs: man:zfs(8) Process: 9283 ExecStartPre=/bin/rm -f /etc/dfs/sharetab (code=exited, status=0/SUCCESS) Process: 9284 ExecStart=/sbin/zfs share -a (code=exited, status=1/FAILURE) Main PID: 9284 (code=exited, status=1/FAILURE) May 24 16:56:03 ocelot systemd[1]: Starting ZFS file system shares... May 24 16:56:03 ocelot zfs[9284]: The ZFS modules are not loaded. May 24 16:56:03 ocelot zfs[9284]: Try running '/sbin/modprobe zfs' as root to load them. May 24 16:56:03 ocelot systemd[1]: zfs-share.service: Main process exited, code=exited, status=1/FAILURE May 24 16:56:03 ocelot systemd[1]: zfs-share.service: Failed with result 'exit-code'. May 24 16:56:03 ocelot systemd[1]: Failed to start ZFS file system shares. dpkg: error processing package zfsutils-linux (--configure): installed zfsutils-linux package post-installation script subprocess returned error exit status 1 dpkg: dependency problems prevent configuration of zfs-zed: zfs-zed depends on zfsutils-linux (>= 0.8.3-1ubuntu12); however: Package zfsutils-linux is not configured yet. dpkg: error processing package zfs-zed (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: zfsutils-linux zfs-zed E: Sub-process /usr/bin/dpkg returned an error code (1) Additional information: $ lsb_release -rd Descript
[Kernel-packages] [Bug 1886341] Re: Kernel Regression between 5.4.0-26 and 5.4.0-40 causes laptop internal audio devices to fail to load w/o unacceptable workaround
OK, think I got it. I'm adding apport file apport.linux.yukw0jij.apport as an attachment. Keep in mind that after installing Mint 20 Xfce with kernel 5.4.0-26, and updating to 5.4.0-40.44, I did two things that changed what I get from the sound system, one for the better, the other for the worse (see forum discussion https://forums.linuxmint.com/viewtopic.php?f=49&t=323823): sudo tee /etc/modprobe.d/alsa-fix.conf <<<'options snd-intel-dspcfg dsp_driver=1' sudo tee /etc/modprobe.d/alsa-fix.conf <<<'options snd-intel-dspcfg dsp_driver=2' ** Attachment added: "apport.linux.yukw0jij.apport" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886341/+attachment/5390786/+files/apport.linux.yukw0jij.apport -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1886341 Title: Kernel Regression between 5.4.0-26 and 5.4.0-40 causes laptop internal audio devices to fail to load w/o unacceptable workaround Status in linux package in Ubuntu: Confirmed Bug description: On Ubuntu 20.04, running kernel 5.4.0-40-generic, the internal speakers, headphone jack, and mic do not work at all. No audio devices appear in the Sound settings or in pavucontrol. By appending options snd_hda_intel dmic_detect=0 to /etc/modprobe.d/alsa-base.conf, I can get audio working, but the microphone (unsuprisingly) does not work. Appending options snd-intel-dspcfg dsp_driver=1 to alsa_base.conf as the same effect as dmic_detect=0. Attempts to fix with option snd_hda_intel device=generic or deveice=auto have had no effect. This bug does NOT manifest on 5.4.0-26-generic, the kernel version featured on the 20.04 live media. After installation, and updating to 5.4.0-40-generic, the bug manifests on the next boot. Note that the audio hardware seems to work properly w/o workaround on a small (< 5%) percentage of boots, but I have been unable to reproduce this. With the workaround enabled, inxi -A gives Audio: Device-1: Intel Smart Sound Audio driver: snd_hda_intel Sound Server: ALSA v: k5.4.0-40-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jill 1374 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 5 13:32:58 2020 InstallationDate: Installed on 2020-07-03 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YK 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.4.0-40-generic root=UUID=dc3e058d-42fc-4de4-b94a-749c1295dc68 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: 03/18/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DPCN40WW 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 5 15IIL05 dmi.modalias: dmi:bvnLENOVO:bvrDPCN40WW:bd03/18/2020:svnLENOVO:pn81YK:pvrIdeaPad515IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrIdeaPad515IIL05: dmi.product.family: IdeaPad 5 15IIL05 dmi.product.name: 81YK dmi.product.sku: LENOVO_MT_81YK_BU_idea_FM_IdeaPad 5 15IIL05 dmi.product.version: IdeaPad 5 15IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886341/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1880421] Re: zfsutils-linux fails to install if `modprobe zfs` fails
Ignore comment above, wrong bug! -- 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/1880421 Title: zfsutils-linux fails to install if `modprobe zfs` fails Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Focal: Fix Committed Status in zfs-linux source package in Groovy: Fix Released Bug description: == SRU Justification, Focal == Justification: Installing zfsutils with zfs modules not available causes the package to installation to fail. The package should install cleanly rather than break. == Test Case == # Prevent module loading $ sudo sysctl kernel.modules_disabled=1 # Install the package $ sudo apt install -y zfsutils-linux This should succeed. Without the fix this fails. (See below for the failure message). With the fix modules don't install but the package install succeeds. == Regression Potential == There may be users who expect the package to fail to install when the zfs utils fail to install when the modules are not available. However, this is a corner case where users are expecting broken behaviour to occur and should not be relying on this. The changes to the systemd rules are already in Ubuntu groovy and have been tested, so I believe the regression potential is limited. Description: When installing zfsutils-linux, failure to `modprobe zfs` cause the package installation to fail. Ideally, modprobe should be attempted but not fatal. Steps to reproduce: # Prevent module loading $ sudo sysctl kernel.modules_disabled=1 # Install the package $ sudo apt install -y zfsutils-linux This should succeed but fails with: Reading package lists... Done Building dependency tree Reading state information... Done zfsutils-linux is already the newest version (0.8.3-1ubuntu12). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 2 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Setting up zfsutils-linux (0.8.3-1ubuntu12) ... insmod /lib/modules/5.4.0-31-generic/kernel/zfs/zlua.ko modprobe: ERROR: could not insert 'zfs': Operation not permitted zfs-import-scan.service is a disabled or a static unit, not starting it. A dependency job for zfs-import-cache.service failed. See 'journalctl -xe' for details. Job for zfs-load-module.service failed because the control process exited with error code. See "systemctl status zfs-load-module.service" and "journalctl -xe" for details. zfs-import-scan.service is a disabled or a static unit, not starting it. Job for zfs-load-module.service failed because the control process exited with error code. See "systemctl status zfs-load-module.service" and "journalctl -xe" for details. A dependency job for zfs-import-cache.service failed. See 'journalctl -xe' for details. Job for zfs-share.service failed because the control process exited with error code. See "systemctl status zfs-share.service" and "journalctl -xe" for details. invoke-rc.d: initscript zfs-share, action "start" failed. ● zfs-share.service - ZFS file system shares Loaded: loaded (/lib/systemd/system/zfs-share.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Sun 2020-05-24 16:56:03 UTC; 52ms ago Docs: man:zfs(8) Process: 9283 ExecStartPre=/bin/rm -f /etc/dfs/sharetab (code=exited, status=0/SUCCESS) Process: 9284 ExecStart=/sbin/zfs share -a (code=exited, status=1/FAILURE) Main PID: 9284 (code=exited, status=1/FAILURE) May 24 16:56:03 ocelot systemd[1]: Starting ZFS file system shares... May 24 16:56:03 ocelot zfs[9284]: The ZFS modules are not loaded. May 24 16:56:03 ocelot zfs[9284]: Try running '/sbin/modprobe zfs' as root to load them. May 24 16:56:03 ocelot systemd[1]: zfs-share.service: Main process exited, code=exited, status=1/FAILURE May 24 16:56:03 ocelot systemd[1]: zfs-share.service: Failed with result 'exit-code'. May 24 16:56:03 ocelot systemd[1]: Failed to start ZFS file system shares. dpkg: error processing package zfsutils-linux (--configure): installed zfsutils-linux package post-installation script subprocess returned error exit status 1 dpkg: dependency problems prevent configuration of zfs-zed: zfs-zed depends on zfsutils-linux (>= 0.8.3-1ubuntu12); however: Package zfsutils-linux is not configured yet. dpkg: error processing package zfs-zed (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: zfsutils-linux zfs-zed E: Sub-process /usr/bin/dpkg returned an error code (1) Additional information: $ lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 $ apt-cache policy zfsutils-linux zfsutils-linux: Installed: 0.8.3-1ubuntu12 Candidate: 0.8.3-1ubuntu
[Kernel-packages] [Bug 1886814] 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 1886814 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/1886814 Title: posix_spawn usage in gnu make causes failures on s390x Status in Ubuntu on IBM z Systems: New Status in glibc package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in make-dfsg package in Ubuntu: New Bug description: posix_spawn usage in gnu make causes failures on s390x Recently in gnu-make v4.3 https://paste.ubuntu.com/p/tYhbJFKN76/ it started to use posix_spawn, instead of fork()/exec(). This has caused failure of an unrelated package flatpak-builder autopkgtests on s390x only, like so echo Building make: echo: Operation not permitted make: *** [Makefile:2: all] Error 127 Julian Klaude investigated this in-depth. His earlier research also indicated that this is a heisenbug, if one tries to print to stderr before printing to stdout, no issue occurs. We are configuring GNU make to be build with --disable-posix-spawn on s390x only. We passed these details to Debian https://bugs.debian.org /cgi-bin/bugreport.cgi?bug=964541 too. But I do wonder, if there is something different or incorrect about posix_spawn() implementation in either glibc, or linux kernel, on s390x. Or gnu-make's usage of posix_spawn(). As otherise, using posix_spawn() in gnu-make works on other architectures, and flatpak-builder autopkgtests pass too. It seems very weird that stdout does not appear to be functional, unless stderr was opened/written to, from gnu-make execution compiled with posix-spawn feature. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1886814/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1880421] Re: zfsutils-linux fails to install if `modprobe zfs` fails
Set: sudo sysctl kernel.modules_disabled=1 Installed -proposed zfsutils-linux, no breakage now. Issue is fixed. ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1880421 Title: zfsutils-linux fails to install if `modprobe zfs` fails Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Focal: Fix Committed Status in zfs-linux source package in Groovy: Fix Released Bug description: == SRU Justification, Focal == Justification: Installing zfsutils with zfs modules not available causes the package to installation to fail. The package should install cleanly rather than break. == Test Case == # Prevent module loading $ sudo sysctl kernel.modules_disabled=1 # Install the package $ sudo apt install -y zfsutils-linux This should succeed. Without the fix this fails. (See below for the failure message). With the fix modules don't install but the package install succeeds. == Regression Potential == There may be users who expect the package to fail to install when the zfs utils fail to install when the modules are not available. However, this is a corner case where users are expecting broken behaviour to occur and should not be relying on this. The changes to the systemd rules are already in Ubuntu groovy and have been tested, so I believe the regression potential is limited. Description: When installing zfsutils-linux, failure to `modprobe zfs` cause the package installation to fail. Ideally, modprobe should be attempted but not fatal. Steps to reproduce: # Prevent module loading $ sudo sysctl kernel.modules_disabled=1 # Install the package $ sudo apt install -y zfsutils-linux This should succeed but fails with: Reading package lists... Done Building dependency tree Reading state information... Done zfsutils-linux is already the newest version (0.8.3-1ubuntu12). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 2 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Setting up zfsutils-linux (0.8.3-1ubuntu12) ... insmod /lib/modules/5.4.0-31-generic/kernel/zfs/zlua.ko modprobe: ERROR: could not insert 'zfs': Operation not permitted zfs-import-scan.service is a disabled or a static unit, not starting it. A dependency job for zfs-import-cache.service failed. See 'journalctl -xe' for details. Job for zfs-load-module.service failed because the control process exited with error code. See "systemctl status zfs-load-module.service" and "journalctl -xe" for details. zfs-import-scan.service is a disabled or a static unit, not starting it. Job for zfs-load-module.service failed because the control process exited with error code. See "systemctl status zfs-load-module.service" and "journalctl -xe" for details. A dependency job for zfs-import-cache.service failed. See 'journalctl -xe' for details. Job for zfs-share.service failed because the control process exited with error code. See "systemctl status zfs-share.service" and "journalctl -xe" for details. invoke-rc.d: initscript zfs-share, action "start" failed. ● zfs-share.service - ZFS file system shares Loaded: loaded (/lib/systemd/system/zfs-share.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Sun 2020-05-24 16:56:03 UTC; 52ms ago Docs: man:zfs(8) Process: 9283 ExecStartPre=/bin/rm -f /etc/dfs/sharetab (code=exited, status=0/SUCCESS) Process: 9284 ExecStart=/sbin/zfs share -a (code=exited, status=1/FAILURE) Main PID: 9284 (code=exited, status=1/FAILURE) May 24 16:56:03 ocelot systemd[1]: Starting ZFS file system shares... May 24 16:56:03 ocelot zfs[9284]: The ZFS modules are not loaded. May 24 16:56:03 ocelot zfs[9284]: Try running '/sbin/modprobe zfs' as root to load them. May 24 16:56:03 ocelot systemd[1]: zfs-share.service: Main process exited, code=exited, status=1/FAILURE May 24 16:56:03 ocelot systemd[1]: zfs-share.service: Failed with result 'exit-code'. May 24 16:56:03 ocelot systemd[1]: Failed to start ZFS file system shares. dpkg: error processing package zfsutils-linux (--configure): installed zfsutils-linux package post-installation script subprocess returned error exit status 1 dpkg: dependency problems prevent configuration of zfs-zed: zfs-zed depends on zfsutils-linux (>= 0.8.3-1ubuntu12); however: Package zfsutils-linux is not configured yet. dpkg: error processing package zfs-zed (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: zfsutils-linux zfs-zed E: Sub-process /usr/bin/dpkg returned an error code (1) Additional information: $ lsb_release -rd Description: Ubuntu 20.04 LTS Release:
[Kernel-packages] [Bug 1886814] Re: posix_spawn usage in gnu make causes failures on s390x
Is this a native s390x build, or something qemu-user? 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/1886814 Title: posix_spawn usage in gnu make causes failures on s390x Status in Ubuntu on IBM z Systems: New Status in glibc package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in make-dfsg package in Ubuntu: New Bug description: posix_spawn usage in gnu make causes failures on s390x Recently in gnu-make v4.3 https://paste.ubuntu.com/p/tYhbJFKN76/ it started to use posix_spawn, instead of fork()/exec(). This has caused failure of an unrelated package flatpak-builder autopkgtests on s390x only, like so echo Building make: echo: Operation not permitted make: *** [Makefile:2: all] Error 127 Julian Klaude investigated this in-depth. His earlier research also indicated that this is a heisenbug, if one tries to print to stderr before printing to stdout, no issue occurs. We are configuring GNU make to be build with --disable-posix-spawn on s390x only. We passed these details to Debian https://bugs.debian.org /cgi-bin/bugreport.cgi?bug=964541 too. But I do wonder, if there is something different or incorrect about posix_spawn() implementation in either glibc, or linux kernel, on s390x. Or gnu-make's usage of posix_spawn(). As otherise, using posix_spawn() in gnu-make works on other architectures, and flatpak-builder autopkgtests pass too. It seems very weird that stdout does not appear to be functional, unless stderr was opened/written to, from gnu-make execution compiled with posix-spawn feature. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1886814/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884288] Re: LapBook Pro touchpad (HTIX5288:00) sometimes does not work when machine is restarted
@Kai-Heng, unfortunately after a cold boot this afternoon the touchpad is not working again. The machine was off for the best part of 15 hours. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884288 Title: LapBook Pro touchpad (HTIX5288:00) sometimes does not work when machine is restarted Status in linux package in Ubuntu: Incomplete Bug description: Touchpad completely ceases to work sometimes upon startup / restart. When this happens, I have to plug in an external mouse to navigate as touchpad is not even recognised as a device when I use xinput command in terminal. I removed and reinstalled xserver-xorg-input-synaptics which may have got it working again, although I am not too sure. When the trackpad is working, it's device name is listed as HTIX5288:00 0911:5288 Touchpad. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 19 18:03:47 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 605 [8086:3185] (rev 03) (prog-if 00 [VGA controller]) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:6366 Microdia USB 2.0 Camera Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=c549aad1-cbca-42d0-abc5-e73556f0921b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/29/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E.G140J.D8.E1.016.bin dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE.G140J.D8.E1.016.bin:bd11/29/2019:svn:pnLapBookPro:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: LapBook Pro dmi.product.sku: Default string dmi.product.version: Default string version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.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 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ian1619 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:6366 Microdia USB 2.0 Camera Bus 001 Device 008: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=c549aad1-cbca-42d0-abc5-e73556f0921b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 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.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: _MarkForUpload: True dmi.bios.date: 11/29/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E.G140J.D8.E1.016.bin dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Def
[Kernel-packages] [Bug 1886564] Re: ath9k BOGUS urb xfer
OK, the full dmesg is attached. thanks, Paul ** Attachment added: "dmesg.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886564/+attachment/5390789/+files/dmesg.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1886564 Title: ath9k BOGUS urb xfer Status in linux package in Ubuntu: Incomplete Bug description: There seems to be a bug in the USB/ath9k. I see many messages like this, and have to unplug/replug the adapter many times a day: [48001.541124] [ cut here ] [48001.541128] usb 3-3: BOGUS urb xfer, pipe 1 != type 3 [48001.541186] WARNING: CPU: 0 PID: 27317 at drivers/usb/core/urb.c:478 usb_submit_urb+0x561/0x5e0 [48001.541187] Modules linked in: r8712u(C) ccm snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi ledtrig_audio snd_hda_intel snd_intel_dspcfg snd_hda_codec snd_usb_audio snd_hda_core snd_usbmidi_lib snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event edac_mce_amd snd_rawmidi ath9k_htc ath9k_common ath9k_hw snd_seq uvcvideo v4l2_common videobuf2_vmalloc videobuf2_memops ath ccp videobuf2_v4l2 videobuf2_common snd_seq_device mac80211 kvm snd_timer videodev irqbypass snd serio_raw mc wmi_bmof joydev cfg80211 k10temp input_leds fam15h_power libarc4 soundcore mac_hid sch_fq_codel cuse parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_logitech_hidpp hid_logitech_dj hid_generic usbhid hid amdgpu crct10dif_pclmul crc32_pclmul ghash_clmulni_intel amd_iommu_v2 gpu_sched i2c_algo_bit aesni_intel ttm drm_kms_helper aes_x86_64 crypto_simd syscopyarea cryptd sysfillrect glue_helper sysimgblt pata_acpi fb_sys_fops psmouse drm pata_atiixp i2c_piix4 ahci r8169 libahci realtek wmi [48001.541254] CPU: 0 PID: 27317 Comm: kworker/u48:2 Tainted: GWC 5.3.0-62-generic #56-Ubuntu [48001.541256] Hardware name: MSI MS-7641/760GMA-P34(FX) (MS-7641), BIOS V25.1 04/20/2015 [48001.541310] Workqueue: phy1 ieee80211_scan_work [mac80211] [48001.541316] RIP: 0010:usb_submit_urb+0x561/0x5e0 [48001.541320] Code: 00 89 4d c4 44 89 55 c8 44 89 45 d4 e8 68 5e f1 ff 44 8b 45 d4 8b 4d c4 4c 89 fa 48 89 c6 48 c7 c7 38 d3 bd 88 e8 aa 28 8d ff <0f> 0b 44 8b 55 c8 e9 e9 fb ff ff 0f 1f 44 00 00 b8 a6 ff ff ff e9 [48001.541323] RSP: 0018:c2e9c15abaf0 EFLAGS: 00010286 [48001.541325] RAX: RBX: 0002 RCX: 0006 [48001.541327] RDX: 0007 RSI: 0096 RDI: 9ee667617440 [48001.541329] RBP: c2e9c15abb30 R08: 037e780c R09: 0004 [48001.541331] R10: R11: 0001 R12: 9ee4d4737500 [48001.541332] R13: 9ee60499e800 R14: 0002 R15: 9ee660959348 [48001.541335] FS: () GS:9ee66760() knlGS: [48001.541337] CS: 0010 DS: ES: CR0: 80050033 [48001.541339] CR2: 0b9c80186000 CR3: 000293f22000 CR4: 000406f0 [48001.541341] Call Trace: [48001.541353] hif_usb_send+0x189/0x320 [ath9k_htc] [48001.541360] htc_issue_send.constprop.0+0x5e/0x70 [ath9k_htc] [48001.541367] htc_send_epid+0x15/0x20 [ath9k_htc] [48001.541373] ath9k_wmi_cmd+0x11c/0x1c0 [ath9k_htc] [48001.541381] ath9k_regread+0x48/0x70 [ath9k_htc] [48001.541398] ath9k_hw_wait+0x5d/0xa0 [ath9k_hw] [48001.541412] ath9k_hw_set_reset+0x291/0x420 [ath9k_hw] [48001.541426] ath9k_hw_set_reset_reg+0x9b/0x240 [ath9k_hw] [48001.541441] ath9k_hw_reset+0xd21/0x1110 [ath9k_hw] [48001.541449] ath9k_htc_config+0x203/0x640 [ath9k_htc] [48001.541454] ? __switch_to_asm+0x34/0x70 [48001.541457] ? __switch_to_asm+0x40/0x70 [48001.541459] ? __switch_to_asm+0x34/0x70 [48001.541461] ? __switch_to_asm+0x40/0x70 [48001.541463] ? __switch_to_asm+0x34/0x70 [48001.541501] ieee80211_hw_config+0x95/0x360 [mac80211] [48001.541542] ieee80211_scan_work+0x29d/0x520 [mac80211] [48001.541547] process_one_work+0x1db/0x380 [48001.541551] worker_thread+0x4d/0x400 [48001.541555] kthread+0x104/0x140 [48001.541559] ? process_one_work+0x380/0x380 [48001.541562] ? kthread_park+0x80/0x80 [48001.541565] ret_from_fork+0x22/0x40 [48001.541569] ---[ end trace fa2f8d48d479093d ]--- The kernel version is: Linux version 5.3.0-62-generic (buildd@lcy01-amd64-018) (gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2)) #56-Ubuntu SMP Tue Jun 23 11:20:52 UTC 2020 I specifically bought a wireless adapter from thinkpenguin.com linked to here: https://help.ubuntu.com/community/WifiDocs/WirelessCardsSupported Because I was having trouble with other adapters. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886564/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.
[Kernel-packages] [Bug 1886277] Re: unable to handle page fault in mempool_alloc_slab
I also have this problem, which I reported as a new bug 1886775 which is probably just a duplicate of this bug. Same issue, -40 dies with NFS with similar stack trace and similar timing, -39 is fine, and multiple hardware has the identical issues. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1886277 Title: unable to handle page fault in mempool_alloc_slab Status in linux package in Ubuntu: Incomplete Bug description: On kernel 5.4.0-40-generic in focal I'm getting errors like this on several machines with different hardware in the first hour after boot: Jul 04 16:58:32 hostname kernel: BUG: unable to handle page fault for address: 9083e222e632 Jul 04 16:58:32 hostname kernel: #PF: supervisor read access in kernel mode Jul 04 16:58:32 hostname kernel: #PF: error_code(0x) - not-present page Jul 04 16:58:32 hostname kernel: PGD 3ac205067 P4D 3ac205067 PUD 0 Jul 04 16:58:32 hostname kernel: Oops: [#1] SMP NOPTI Jul 04 16:58:32 hostname kernel: CPU: 4 PID: 289 Comm: kworker/u16:4 Tainted: G OE 5.4.0-40-generic #44-Ubuntu Jul 04 16:58:32 hostname kernel: Hardware name: LENOVO 20N2CTO1WW/20N2CTO1WW, BIOS N2IET88W (1.66 ) 04/22/2020 Jul 04 16:58:32 hostname kernel: Workqueue: rpciod rpc_async_schedule [sunrpc] Jul 04 16:58:32 hostname kernel: RIP: 0010:kmem_cache_alloc+0x7e/0x230 Jul 04 16:58:32 hostname kernel: Code: 99 01 00 00 4d 8b 07 65 49 8b 50 08 65 4c 03 05 40 9d 56 44 4d 8b 20 4d 85 e4 0f 84 85 01 00 00 41 8b 47 20 49 8b 3f 4c 01 e0 <48> 8b 18 48 89 c1 49 33 9f 70 01 00 00 4c 89 e0 48 0f c9 48 31 cb Jul 04 16:58:32 hostname kernel: RSP: 0018:bc38c046fcc8 EFLAGS: 00010282 Jul 04 16:58:32 hostname kernel: RAX: 9083e222e632 RBX: RCX: 0002 Jul 04 16:58:32 hostname kernel: RDX: 0009 RSI: 00092800 RDI: 00031fb0 Jul 04 16:58:32 hostname kernel: RBP: bc38c046fcf8 R08: 90836c331fb0 R09: c1436a94 Jul 04 16:58:32 hostname kernel: R10: 908368178d2c R11: 0018 R12: 9083e222e632 Jul 04 16:58:32 hostname kernel: R13: 00092800 R14: 908367ca6140 R15: 908367ca6140 Jul 04 16:58:32 hostname kernel: FS: () GS:90836c30() knlGS: Jul 04 16:58:32 hostname kernel: CS: 0010 DS: ES: CR0: 80050033 Jul 04 16:58:32 hostname kernel: CR2: 9083e222e632 CR3: 0003ab80a003 CR4: 003606e0 Jul 04 16:58:32 hostname kernel: Call Trace: Jul 04 16:58:32 hostname kernel: ? mempool_alloc_slab+0x17/0x20 Jul 04 16:58:32 hostname kernel: mempool_alloc_slab+0x17/0x20 Jul 04 16:58:32 hostname kernel: mempool_alloc+0x64/0x180 Jul 04 16:58:32 hostname kernel: rpc_malloc+0xa1/0xb0 [sunrpc] Jul 04 16:58:32 hostname kernel: call_allocate+0xd1/0x1b0 [sunrpc] Jul 04 16:58:32 hostname kernel: ? call_refreshresult+0x100/0x100 [sunrpc] Jul 04 16:58:32 hostname kernel: __rpc_execute+0x8c/0x3a0 [sunrpc] Jul 04 16:58:32 hostname kernel: rpc_async_schedule+0x30/0x50 [sunrpc] Jul 04 16:58:32 hostname kernel: process_one_work+0x1eb/0x3b0 Jul 04 16:58:32 hostname kernel: worker_thread+0x4d/0x400 Jul 04 16:58:32 hostname kernel: kthread+0x104/0x140 Jul 04 16:58:32 hostname kernel: ? process_one_work+0x3b0/0x3b0 Jul 04 16:58:32 hostname kernel: ? kthread_park+0x90/0x90 Jul 04 16:58:32 hostname kernel: ret_from_fork+0x35/0x40 Jul 04 16:58:32 hostname kernel: Modules linked in: rfcomm rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) msr ccm cmac algif_hash algif_skcipher af_alg aufs bnep overlay nls_iso8859_1 mei_hdcp intel_rapl_msr snd_s> Jul 04 16:58:32 hostname kernel: nvram ledtrig_audio mei_me cfg80211 mei processor_thermal_device snd_seq ucsi_acpi typec_ucsi intel_rapl_common intel_soc_dts_iosf snd_seq_device typec intel_pch_thermal snd_timer snd int3403_thermal soundcore int340x_thermal_zone i> Jul 04 16:58:32 hostname kernel: pinctrl_cannonlake video pinctrl_intel Jul 04 16:58:32 hostname kernel: CR2: 9083e222e632 Jul 04 16:58:32 hostname kernel: ---[ end trace cbbaed921eb439ce ]--- Jul 04 16:58:32 hostname kernel: RIP: 0010:kmem_cache_alloc+0x7e/0x230 Jul 04 16:58:32 hostname kernel: Code: 99 01 00 00 4d 8b 07 65 49 8b 50 08 65 4c 03 05 40 9d 56 44 4d 8b 20 4d 85 e4 0f 84 85 01 00 00 41 8b 47 20 49 8b 3f 4c 01 e0 <48> 8b 18 48 89 c1 49 33 9f 70 01 00 00 4c 89 e0 48 0f c9 48 31 cb Jul 04 16:58:32 hostname kernel: RSP: 0018:bc38c046fcc8 EFLAGS: 00010282 Jul 04 16:58:32 hostname kernel: RAX: 9083e222e632 RBX: RCX: 0002 Jul 04 16:58:32 hostname kernel: RDX: 0009 RSI: 00092800 RDI: 00031fb0 Jul 04 16:58:32 hostname kernel: RBP: bc38c046fcf8 R08: 90836c331fb0 R09: c14
[Kernel-packages] [Bug 1886775] Re: kernel 5.4.0-40 hangs system when using nfs home directories
#3: Agreed that it is a duplicate of lp: #1886277 . Sorry, I looked for similar bugs but did a lousy job it appears. I just made a comment to this effect in #1886277. #2: I believe the apport files are attached in comment #1, though it is the first time I have used it and may be confusing it. ** 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/1886775 Title: kernel 5.4.0-40 hangs system when using nfs home directories Status in linux package in Ubuntu: Confirmed Bug description: We use nfs mounted (using autofs), kerberos authenticated home directories for most users. Booting with kernel 5.4.0-40, users with nfs mounted home directories find the system freezes not long after use, somewhat randomly. Power off is then the only thing to do. Some specific things that caused crashes - opening a second tab on firefox; opening a terminal and running "cat" on log files, and running ubuntu-bug linux to try to generate this report :-( Sometimes before the crash just one window freezes, and the rest of the GUI is responsive. A full freeze usually occurs within several seconds. No such crashes were observed using an account without nfs mounted home directories (and the output from "ubuntu-bug linux" for one of these working users is at the end of this report). Reverting to 5.4.0-39, everything is good. Exactly the same behaviour is observed on a modern AMD Zen2 processor with a graphics card, and a several year old Intel processor with integrated graphics. Looking at /var/log/syslog there are several suspicious messages like the one below. The general protection fault occurs always just before the freeze, and occasionally some times before. Jul 4 16:23:37 emu kernel: [ 350.263903] [ cut here ] Jul 4 16:23:37 emu kernel: [ 350.263904] virt_to_cache: Object is not a Slab page! Jul 4 16:23:37 emu kernel: [ 350.263917] WARNING: CPU: 13 PID: 4009 at mm/slab.h:473 kmem_cache_free+0x237/0x2b0 Jul 4 16:23:37 emu kernel: [ 350.263917] Modules linked in: rfcomm rpcsec_gss_krb5 nfsv4 nfs fscache vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) edac_mce_amd kvm_amd xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c nf_tables nfnetlink ip6table_filter ip6_tables iptable_filter bpfilter cmac algif_hash algif_skcipher af_alg bnep snd_hda_codec_hdmi binfmt_misc nvidia_uvm(OE) kvm nvidia_drm(POE) nvidia_modeset(POE) iwlmvm snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_intel snd_intel_dspcfg snd_hda_codec nls_iso8859_1 snd_hda_core snd_hwdep snd_pcm btusb btrtl btbcm btintel snd_seq_midi mac80211 bluetooth snd_seq_midi_event crct10dif_pclmul snd_rawmidi bridge ecdh_generic stp ghash_clmulni_intel llc libarc4 input_leds joydev ecc nvidia(POE) snd_seq iwlwifi aesni_intel crypto_simd cryptd glue_helper drm_kms_helper snd_seq_device cfg80211 snd_timer ipmi_devintf Jul 4 16:23:37 emu kernel: [ 350.263952] wmi_bmof ipmi_msghandler snd fb_sys_fops syscopyarea sysfillrect sysimgblt soundcore k10temp ccp mac_hid sch_fq_codel parport_pc ppdev lp parport drm nfsd nfs_acl auth_rpcgss lockd grace sunrpc ip_tables x_tables autofs4 hid_generic usbhid hid crc32_pclmul igb i2c_piix4 ahci i2c_algo_bit nvme libahci dca nvme_core wmi Jul 4 16:23:37 emu kernel: [ 350.263971] CPU: 13 PID: 4009 Comm: kworker/u64:4 Tainted: P OE 5.4.0-40-generic #44-Ubuntu Jul 4 16:23:37 emu kernel: [ 350.263972] Hardware name: Gigabyte Technology Co., Ltd. X570 I AORUS PRO WIFI/X570 I AORUS PRO WIFI, BIOS F4h 07/17/2019 Jul 4 16:23:37 emu kernel: [ 350.263986] Workqueue: rpciod rpc_async_schedule [sunrpc] Jul 4 16:23:37 emu kernel: [ 350.263989] RIP: 0010:kmem_cache_free+0x237/0x2b0 Jul 4 16:23:37 emu kernel: [ 350.263990] Code: ff ff ff 80 3d 16 4f 56 01 00 0f 85 39 ff ff ff 48 c7 c6 20 44 67 86 48 c7 c7 08 25 98 86 c6 05 fb 4e 56 01 01 e8 64 8a df ff <0f> 0b e9 18 ff ff ff 48 8b 57 58 49 8b 4f 58 48 c7 c6 30 44 67 86 Jul 4 16:23:37 emu kernel: [ 350.263991] RSP: 0018:c1ebc3077d20 EFLAGS: 00010282 Jul 4 16:23:37 emu kernel: [ 350.263993] RAX: RBX: a040c01358e2 RCX: 0006 Jul 4 16:23:37 emu kernel: [ 350.263993] RDX: 0007 RSI: 0092 RDI: a040beb578c0 Jul 4 16:23:37 emu kernel: [ 350.263994] RBP: c1ebc3077d48 R08: 0506 R09: 0004 Jul 4 16:23:37 emu kernel: [ 350.263995] R10: R11: 0001 R12: a041401358e2 Jul 4 16:23:37 emu kernel: [ 350.263995] R13: R14: a040a7e47600 R15: a04065a99cb0 Jul 4 16:23:37 emu kernel: [ 35
[Kernel-packages] [Bug 1885271] Re: kernel oops xr-usb-serial
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Jesse Sung (wenchien) ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Jesse Sung (wenchien) ** Changed in: linux (Ubuntu Bionic) 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/1885271 Title: kernel oops xr-usb-serial Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: # Steps to reproduce # Working case uname -a Linux ubuntu 4.15.0-91-generic #92-Ubuntu SMP Fri Feb 28 11:09:48 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux lsusb -d 04e2:1411 -v > xr-usb-serial-devices.txt lsusb -t >> xr-usb-serial-devices.txt # Unbind 2 xr-usb-serial devices echo '3-14.1' | tee /sys/bus/usb/drivers/usb/unbind echo '3-14.3' | tee /sys/bus/usb/drivers/usb/unbind dmesg > dmesg.txt # Non working case uname -a Linux ubuntu 4.15.0-99-generic #100-Ubuntu SMP Wed Apr 22 20:32:56 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux lsusb -d 04e2:1411 -v > xr-usb-serial-devices.txt dmesg > dmesg.txt This regression is almost certainly caused by one of the 2020-03-11 commits: https://kernel.ubuntu.com/git/ubuntu/ubuntu-bionic.git/log/ubuntu/xr-usb-serial?h=Ubuntu-4.15.0-99.100&id=5966ed54d467fa77e7dbd7355177a5a6d1db7004 files attached in tar file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885271/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886814] Re: posix_spawn usage in gnu make causes failures on s390x
** Tags added: architecture-s39064 bugnameltc-186737 severity-high targetmilestone-inin2004 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1886814 Title: posix_spawn usage in gnu make causes failures on s390x Status in Ubuntu on IBM z Systems: New Status in glibc package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in make-dfsg package in Ubuntu: New Bug description: posix_spawn usage in gnu make causes failures on s390x Recently in gnu-make v4.3 https://paste.ubuntu.com/p/tYhbJFKN76/ it started to use posix_spawn, instead of fork()/exec(). This has caused failure of an unrelated package flatpak-builder autopkgtests on s390x only, like so echo Building make: echo: Operation not permitted make: *** [Makefile:2: all] Error 127 Julian Klaude investigated this in-depth. His earlier research also indicated that this is a heisenbug, if one tries to print to stderr before printing to stdout, no issue occurs. We are configuring GNU make to be build with --disable-posix-spawn on s390x only. We passed these details to Debian https://bugs.debian.org /cgi-bin/bugreport.cgi?bug=964541 too. But I do wonder, if there is something different or incorrect about posix_spawn() implementation in either glibc, or linux kernel, on s390x. Or gnu-make's usage of posix_spawn(). As otherise, using posix_spawn() in gnu-make works on other architectures, and flatpak-builder autopkgtests pass too. It seems very weird that stdout does not appear to be functional, unless stderr was opened/written to, from gnu-make execution compiled with posix-spawn feature. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1886814/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886564] Re: ath9k BOGUS urb xfer
** Tags added: hwe-networking-wifi -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1886564 Title: ath9k BOGUS urb xfer Status in linux package in Ubuntu: Incomplete Bug description: There seems to be a bug in the USB/ath9k. I see many messages like this, and have to unplug/replug the adapter many times a day: [48001.541124] [ cut here ] [48001.541128] usb 3-3: BOGUS urb xfer, pipe 1 != type 3 [48001.541186] WARNING: CPU: 0 PID: 27317 at drivers/usb/core/urb.c:478 usb_submit_urb+0x561/0x5e0 [48001.541187] Modules linked in: r8712u(C) ccm snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi ledtrig_audio snd_hda_intel snd_intel_dspcfg snd_hda_codec snd_usb_audio snd_hda_core snd_usbmidi_lib snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event edac_mce_amd snd_rawmidi ath9k_htc ath9k_common ath9k_hw snd_seq uvcvideo v4l2_common videobuf2_vmalloc videobuf2_memops ath ccp videobuf2_v4l2 videobuf2_common snd_seq_device mac80211 kvm snd_timer videodev irqbypass snd serio_raw mc wmi_bmof joydev cfg80211 k10temp input_leds fam15h_power libarc4 soundcore mac_hid sch_fq_codel cuse parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_logitech_hidpp hid_logitech_dj hid_generic usbhid hid amdgpu crct10dif_pclmul crc32_pclmul ghash_clmulni_intel amd_iommu_v2 gpu_sched i2c_algo_bit aesni_intel ttm drm_kms_helper aes_x86_64 crypto_simd syscopyarea cryptd sysfillrect glue_helper sysimgblt pata_acpi fb_sys_fops psmouse drm pata_atiixp i2c_piix4 ahci r8169 libahci realtek wmi [48001.541254] CPU: 0 PID: 27317 Comm: kworker/u48:2 Tainted: GWC 5.3.0-62-generic #56-Ubuntu [48001.541256] Hardware name: MSI MS-7641/760GMA-P34(FX) (MS-7641), BIOS V25.1 04/20/2015 [48001.541310] Workqueue: phy1 ieee80211_scan_work [mac80211] [48001.541316] RIP: 0010:usb_submit_urb+0x561/0x5e0 [48001.541320] Code: 00 89 4d c4 44 89 55 c8 44 89 45 d4 e8 68 5e f1 ff 44 8b 45 d4 8b 4d c4 4c 89 fa 48 89 c6 48 c7 c7 38 d3 bd 88 e8 aa 28 8d ff <0f> 0b 44 8b 55 c8 e9 e9 fb ff ff 0f 1f 44 00 00 b8 a6 ff ff ff e9 [48001.541323] RSP: 0018:c2e9c15abaf0 EFLAGS: 00010286 [48001.541325] RAX: RBX: 0002 RCX: 0006 [48001.541327] RDX: 0007 RSI: 0096 RDI: 9ee667617440 [48001.541329] RBP: c2e9c15abb30 R08: 037e780c R09: 0004 [48001.541331] R10: R11: 0001 R12: 9ee4d4737500 [48001.541332] R13: 9ee60499e800 R14: 0002 R15: 9ee660959348 [48001.541335] FS: () GS:9ee66760() knlGS: [48001.541337] CS: 0010 DS: ES: CR0: 80050033 [48001.541339] CR2: 0b9c80186000 CR3: 000293f22000 CR4: 000406f0 [48001.541341] Call Trace: [48001.541353] hif_usb_send+0x189/0x320 [ath9k_htc] [48001.541360] htc_issue_send.constprop.0+0x5e/0x70 [ath9k_htc] [48001.541367] htc_send_epid+0x15/0x20 [ath9k_htc] [48001.541373] ath9k_wmi_cmd+0x11c/0x1c0 [ath9k_htc] [48001.541381] ath9k_regread+0x48/0x70 [ath9k_htc] [48001.541398] ath9k_hw_wait+0x5d/0xa0 [ath9k_hw] [48001.541412] ath9k_hw_set_reset+0x291/0x420 [ath9k_hw] [48001.541426] ath9k_hw_set_reset_reg+0x9b/0x240 [ath9k_hw] [48001.541441] ath9k_hw_reset+0xd21/0x1110 [ath9k_hw] [48001.541449] ath9k_htc_config+0x203/0x640 [ath9k_htc] [48001.541454] ? __switch_to_asm+0x34/0x70 [48001.541457] ? __switch_to_asm+0x40/0x70 [48001.541459] ? __switch_to_asm+0x34/0x70 [48001.541461] ? __switch_to_asm+0x40/0x70 [48001.541463] ? __switch_to_asm+0x34/0x70 [48001.541501] ieee80211_hw_config+0x95/0x360 [mac80211] [48001.541542] ieee80211_scan_work+0x29d/0x520 [mac80211] [48001.541547] process_one_work+0x1db/0x380 [48001.541551] worker_thread+0x4d/0x400 [48001.541555] kthread+0x104/0x140 [48001.541559] ? process_one_work+0x380/0x380 [48001.541562] ? kthread_park+0x80/0x80 [48001.541565] ret_from_fork+0x22/0x40 [48001.541569] ---[ end trace fa2f8d48d479093d ]--- The kernel version is: Linux version 5.3.0-62-generic (buildd@lcy01-amd64-018) (gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2)) #56-Ubuntu SMP Tue Jun 23 11:20:52 UTC 2020 I specifically bought a wireless adapter from thinkpenguin.com linked to here: https://help.ubuntu.com/community/WifiDocs/WirelessCardsSupported Because I was having trouble with other adapters. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886564/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886564] Re: ath9k BOGUS urb xfer
https://dev.archive.openwrt.org/ticket/21929.html https://github.com/qca/open-ath9k-htc-firmware/wiki/usb-related-issues https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/net/wireless/ath/ath9k/hif_usb.c?id=2b721118b7821107757eb1d37af4b60e877b27e7 But this should have been included long ago? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1886564 Title: ath9k BOGUS urb xfer Status in linux package in Ubuntu: Incomplete Bug description: There seems to be a bug in the USB/ath9k. I see many messages like this, and have to unplug/replug the adapter many times a day: [48001.541124] [ cut here ] [48001.541128] usb 3-3: BOGUS urb xfer, pipe 1 != type 3 [48001.541186] WARNING: CPU: 0 PID: 27317 at drivers/usb/core/urb.c:478 usb_submit_urb+0x561/0x5e0 [48001.541187] Modules linked in: r8712u(C) ccm snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi ledtrig_audio snd_hda_intel snd_intel_dspcfg snd_hda_codec snd_usb_audio snd_hda_core snd_usbmidi_lib snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event edac_mce_amd snd_rawmidi ath9k_htc ath9k_common ath9k_hw snd_seq uvcvideo v4l2_common videobuf2_vmalloc videobuf2_memops ath ccp videobuf2_v4l2 videobuf2_common snd_seq_device mac80211 kvm snd_timer videodev irqbypass snd serio_raw mc wmi_bmof joydev cfg80211 k10temp input_leds fam15h_power libarc4 soundcore mac_hid sch_fq_codel cuse parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_logitech_hidpp hid_logitech_dj hid_generic usbhid hid amdgpu crct10dif_pclmul crc32_pclmul ghash_clmulni_intel amd_iommu_v2 gpu_sched i2c_algo_bit aesni_intel ttm drm_kms_helper aes_x86_64 crypto_simd syscopyarea cryptd sysfillrect glue_helper sysimgblt pata_acpi fb_sys_fops psmouse drm pata_atiixp i2c_piix4 ahci r8169 libahci realtek wmi [48001.541254] CPU: 0 PID: 27317 Comm: kworker/u48:2 Tainted: GWC 5.3.0-62-generic #56-Ubuntu [48001.541256] Hardware name: MSI MS-7641/760GMA-P34(FX) (MS-7641), BIOS V25.1 04/20/2015 [48001.541310] Workqueue: phy1 ieee80211_scan_work [mac80211] [48001.541316] RIP: 0010:usb_submit_urb+0x561/0x5e0 [48001.541320] Code: 00 89 4d c4 44 89 55 c8 44 89 45 d4 e8 68 5e f1 ff 44 8b 45 d4 8b 4d c4 4c 89 fa 48 89 c6 48 c7 c7 38 d3 bd 88 e8 aa 28 8d ff <0f> 0b 44 8b 55 c8 e9 e9 fb ff ff 0f 1f 44 00 00 b8 a6 ff ff ff e9 [48001.541323] RSP: 0018:c2e9c15abaf0 EFLAGS: 00010286 [48001.541325] RAX: RBX: 0002 RCX: 0006 [48001.541327] RDX: 0007 RSI: 0096 RDI: 9ee667617440 [48001.541329] RBP: c2e9c15abb30 R08: 037e780c R09: 0004 [48001.541331] R10: R11: 0001 R12: 9ee4d4737500 [48001.541332] R13: 9ee60499e800 R14: 0002 R15: 9ee660959348 [48001.541335] FS: () GS:9ee66760() knlGS: [48001.541337] CS: 0010 DS: ES: CR0: 80050033 [48001.541339] CR2: 0b9c80186000 CR3: 000293f22000 CR4: 000406f0 [48001.541341] Call Trace: [48001.541353] hif_usb_send+0x189/0x320 [ath9k_htc] [48001.541360] htc_issue_send.constprop.0+0x5e/0x70 [ath9k_htc] [48001.541367] htc_send_epid+0x15/0x20 [ath9k_htc] [48001.541373] ath9k_wmi_cmd+0x11c/0x1c0 [ath9k_htc] [48001.541381] ath9k_regread+0x48/0x70 [ath9k_htc] [48001.541398] ath9k_hw_wait+0x5d/0xa0 [ath9k_hw] [48001.541412] ath9k_hw_set_reset+0x291/0x420 [ath9k_hw] [48001.541426] ath9k_hw_set_reset_reg+0x9b/0x240 [ath9k_hw] [48001.541441] ath9k_hw_reset+0xd21/0x1110 [ath9k_hw] [48001.541449] ath9k_htc_config+0x203/0x640 [ath9k_htc] [48001.541454] ? __switch_to_asm+0x34/0x70 [48001.541457] ? __switch_to_asm+0x40/0x70 [48001.541459] ? __switch_to_asm+0x34/0x70 [48001.541461] ? __switch_to_asm+0x40/0x70 [48001.541463] ? __switch_to_asm+0x34/0x70 [48001.541501] ieee80211_hw_config+0x95/0x360 [mac80211] [48001.541542] ieee80211_scan_work+0x29d/0x520 [mac80211] [48001.541547] process_one_work+0x1db/0x380 [48001.541551] worker_thread+0x4d/0x400 [48001.541555] kthread+0x104/0x140 [48001.541559] ? process_one_work+0x380/0x380 [48001.541562] ? kthread_park+0x80/0x80 [48001.541565] ret_from_fork+0x22/0x40 [48001.541569] ---[ end trace fa2f8d48d479093d ]--- The kernel version is: Linux version 5.3.0-62-generic (buildd@lcy01-amd64-018) (gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2)) #56-Ubuntu SMP Tue Jun 23 11:20:52 UTC 2020 I specifically bought a wireless adapter from thinkpenguin.com linked to here: https://help.ubuntu.com/community/WifiDocs/WirelessCardsSupported Because I was having trouble with other adapters. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886564/+subscriptio
[Kernel-packages] [Bug 1881525] Update Released
The verification of the Stable Release Update for linux-firmware has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1881525 Title: in kernel amdgpu failed with W5500 [1002:7341] Status in HWE Next: Fix Committed Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Bionic: Fix Released Bug description: [SRU Justfication] [Impact] amdgpu is always failed on bionic 5.4 kernel. Since bionic's kernel will upgrade to 5.4 in the future, but bionic's linux-firmware didn't support navi14. So if a user update kernel to 5.4, he/she still can't use the related navi14 devices. # dmesg | grep amdgpu [drm] amdgpu kernel modesetting enabled. amdgpu remove_conflicting_pci_framebuffers: bar 0: 0x60 -> 0x600fff amdgpu remove_conflicting_pci_framebuffers: bar 2: 0x601000 -> 0x60101f amdgpu remove_conflicting_pci_framebuffers: bar 5: 0x7e80 -> 0x7e87 fb0: switching to amdgpudrmfb from EFI VGA amdgpu vgaarb: deactivate vga console amdgpu enabling device (0106 -> 0107) amdgpu Direct firmware load for amdgpu/navi14_gpu_info.bin failed with error -2 amdgpu Failed to load gpu_info firmware "amdgpu/navi14_gpu_info.bin" amdgpu Fatal error during GPU init [Fix] Patchset[1] for navi14's support currently landed in focal's linux-firmware, so we backported them to bionic's linux-firmware. [1]: aa95e90b2c638f1ca6647d12b2d1b18284428f9c d4f88ea76e442e6652de1367050e33314594d533 40656437f476ef7c47972731671ddcc9e4c4225b 7319341e6e40f8bae1f2623eb5e4ddc0e2b50076 b5b176ac09b6d1211da1e5db8e0c31ac830e4b8c [Test] The amdgpu can be recognized and initialized when booting. # dmesg | grep amdgpu [drm] amdgpu kernel modesetting enabled. amdgpu remove_conflicting_pci_framebuffers: bar 0: 0x60 -> 0x600fff amdgpu remove_conflicting_pci_framebuffers: bar 2: 0x601000 -> 0x60101f amdgpu remove_conflicting_pci_framebuffers: bar 5: 0x7e80 -> 0x7e87 amdgpu enabling device (0106 -> 0107) amdgpu VRAM: 8176M 0x0080 - 0x0081FEFF (8176M used) amdgpu GART: 512M 0x - 0x1FFF [drm] amdgpu: 8176M of VRAM memory ready [drm] amdgpu: 8176M of GTT memory ready. ... [drm] Initialized amdgpu 3.35.0 20150101 for :03:00.0 on minor 1 [Regression Potential] Low, just adding new navi14 firmware, no change to existing firmware. X-HWE-Bug: Bug #1880678 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-hotpie+X34 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-05-25 (6 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Package: linux-firmware 1.173.18+navi14 [origin: LP-PPA-shanelin-linux-firmware] PackageArchitecture: all ProcVersionSignature: Ubuntu 5.4.0-31.35~18.04.2-generic 5.4.34 Tags: bionic uec-images third-party-packages Uname: Linux 5.4.0-31-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1881525/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1875263] Re: linux-firmware: missing sof-cfl.ri symbol link for Bionic and Eoan
This bug was fixed in the package linux-firmware - 1.173.19 --- linux-firmware (1.173.19) bionic; urgency=medium * Missing sof-cfl.ri symbol link for Bionic and Eoan (LP: #1875263) - SAUCE: linux-firmware: symbol link sof-cfl.ri and sof-cfl.ldc * Missing amdgpu navi14 firmware (LP: #1881525) - amdgpu: add initial navi14 firmware form 19.30 - amdgpu: update navi14 firmware for 19.30 - amdgpu: add new navi14 wks gfx firmware for 19.30 - amdgpu: update navi14 vcn firmware - amdgpu: update navi14 microcode for 19.50 * Add missing sof-hda-generic-2ch/4ch.tplg symlinks (LP: #1880623) - SAUCE: generate 2 symbollinks for sof-hda-generic.tplg -- Seth Forshee Wed, 17 Jun 2020 08:01:09 -0500 ** Changed in: linux-firmware (Ubuntu Bionic) Status: Incomplete => Fix Released -- 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/1875263 Title: linux-firmware: missing sof-cfl.ri symbol link for Bionic and Eoan Status in OEM Priority Project: New Status in linux-firmware package in Ubuntu: Fix Committed Status in linux-firmware source package in Bionic: Fix Released Status in linux-firmware source package in Eoan: Fix Released Bug description: [Impact] some ubuntu eoan/bionic users reported that the audio driver failed to initialize, then the audio didn't work. I checked the dmesg, found the sof driver planed to load sof-cfl.ri, but there is no this firmware under eoan or bionic. [Fix] I consulted with Intel audio team, they told me that the coffeelake platform could share the firmware with cnl/whl platoforms, so we could build a symbol link sof-cfl->sof-cnl. [Test Case] A couple of ubuntu users already tested it on Dell and Asus coffeelake laptops, it worked well. [Regression Risk] Low, users already tested it, and Intel audio team confirmed it is safe. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1875263/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1875263] Update Released
The verification of the Stable Release Update for linux-firmware has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1875263 Title: linux-firmware: missing sof-cfl.ri symbol link for Bionic and Eoan Status in OEM Priority Project: New Status in linux-firmware package in Ubuntu: Fix Committed Status in linux-firmware source package in Bionic: Fix Released Status in linux-firmware source package in Eoan: Fix Released Bug description: [Impact] some ubuntu eoan/bionic users reported that the audio driver failed to initialize, then the audio didn't work. I checked the dmesg, found the sof driver planed to load sof-cfl.ri, but there is no this firmware under eoan or bionic. [Fix] I consulted with Intel audio team, they told me that the coffeelake platform could share the firmware with cnl/whl platoforms, so we could build a symbol link sof-cfl->sof-cnl. [Test Case] A couple of ubuntu users already tested it on Dell and Asus coffeelake laptops, it worked well. [Regression Risk] Low, users already tested it, and Intel audio team confirmed it is safe. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1875263/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1880623] Re: linux-firmware: generate the symbollink of sof-hda-generic-2ch/4ch.tplg for bionic
This bug was fixed in the package linux-firmware - 1.173.19 --- linux-firmware (1.173.19) bionic; urgency=medium * Missing sof-cfl.ri symbol link for Bionic and Eoan (LP: #1875263) - SAUCE: linux-firmware: symbol link sof-cfl.ri and sof-cfl.ldc * Missing amdgpu navi14 firmware (LP: #1881525) - amdgpu: add initial navi14 firmware form 19.30 - amdgpu: update navi14 firmware for 19.30 - amdgpu: add new navi14 wks gfx firmware for 19.30 - amdgpu: update navi14 vcn firmware - amdgpu: update navi14 microcode for 19.50 * Add missing sof-hda-generic-2ch/4ch.tplg symlinks (LP: #1880623) - SAUCE: generate 2 symbollinks for sof-hda-generic.tplg -- Seth Forshee Wed, 17 Jun 2020 08:01:09 -0500 ** Changed in: linux-firmware (Ubuntu Bionic) Status: Incomplete => Fix Released -- 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/1880623 Title: linux-firmware: generate the symbollink of sof-hda-generic- 2ch/4ch.tplg for bionic Status in HWE Next: New Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Bionic: Fix Released Bug description: [Impact] Users install the focal kernel on the bionic, the sof driver in focal kernel will fail to load the tplg files. [Fix] generate the symbollinks according to the requirement of sof driver in the focal kernel. [Test Case] booting the focal kernel on bionic, the sof driver could load the tplg successfully, and the audio works well. [Regression Risk] Low, the bionic kernel will still load sof-hda-generic.tplg, there is no any impact on the original bionic kernel + linux-firmware. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1880623/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1880623] Update Released
The verification of the Stable Release Update for linux-firmware has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1880623 Title: linux-firmware: generate the symbollink of sof-hda-generic- 2ch/4ch.tplg for bionic Status in HWE Next: New Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Bionic: Fix Released Bug description: [Impact] Users install the focal kernel on the bionic, the sof driver in focal kernel will fail to load the tplg files. [Fix] generate the symbollinks according to the requirement of sof driver in the focal kernel. [Test Case] booting the focal kernel on bionic, the sof driver could load the tplg successfully, and the audio works well. [Regression Risk] Low, the bionic kernel will still load sof-hda-generic.tplg, there is no any impact on the original bionic kernel + linux-firmware. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1880623/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1875263] Re: linux-firmware: missing sof-cfl.ri symbol link for Bionic and Eoan
This bug was fixed in the package linux-firmware - 1.183.6 --- linux-firmware (1.183.6) eoan; urgency=medium * Missing sof-cfl.ri symbol link for Bionic and Eoan (LP: #1875263) - SAUCE: linux-firmware: symbol link sof-cfl.ri and sof-cfl.ldc -- Seth Forshee Wed, 17 Jun 2020 07:48:49 -0500 ** Changed in: linux-firmware (Ubuntu Eoan) Status: Fix Committed => Fix Released -- 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/1875263 Title: linux-firmware: missing sof-cfl.ri symbol link for Bionic and Eoan Status in OEM Priority Project: New Status in linux-firmware package in Ubuntu: Fix Committed Status in linux-firmware source package in Bionic: Fix Released Status in linux-firmware source package in Eoan: Fix Released Bug description: [Impact] some ubuntu eoan/bionic users reported that the audio driver failed to initialize, then the audio didn't work. I checked the dmesg, found the sof driver planed to load sof-cfl.ri, but there is no this firmware under eoan or bionic. [Fix] I consulted with Intel audio team, they told me that the coffeelake platform could share the firmware with cnl/whl platoforms, so we could build a symbol link sof-cfl->sof-cnl. [Test Case] A couple of ubuntu users already tested it on Dell and Asus coffeelake laptops, it worked well. [Regression Risk] Low, users already tested it, and Intel audio team confirmed it is safe. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1875263/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881525] Re: in kernel amdgpu failed with W5500 [1002:7341]
This bug was fixed in the package linux-firmware - 1.173.19 --- linux-firmware (1.173.19) bionic; urgency=medium * Missing sof-cfl.ri symbol link for Bionic and Eoan (LP: #1875263) - SAUCE: linux-firmware: symbol link sof-cfl.ri and sof-cfl.ldc * Missing amdgpu navi14 firmware (LP: #1881525) - amdgpu: add initial navi14 firmware form 19.30 - amdgpu: update navi14 firmware for 19.30 - amdgpu: add new navi14 wks gfx firmware for 19.30 - amdgpu: update navi14 vcn firmware - amdgpu: update navi14 microcode for 19.50 * Add missing sof-hda-generic-2ch/4ch.tplg symlinks (LP: #1880623) - SAUCE: generate 2 symbollinks for sof-hda-generic.tplg -- Seth Forshee Wed, 17 Jun 2020 08:01:09 -0500 ** Changed in: linux-firmware (Ubuntu Bionic) Status: Fix Committed => Fix Released -- 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/1881525 Title: in kernel amdgpu failed with W5500 [1002:7341] Status in HWE Next: Fix Committed Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Bionic: Fix Released Bug description: [SRU Justfication] [Impact] amdgpu is always failed on bionic 5.4 kernel. Since bionic's kernel will upgrade to 5.4 in the future, but bionic's linux-firmware didn't support navi14. So if a user update kernel to 5.4, he/she still can't use the related navi14 devices. # dmesg | grep amdgpu [drm] amdgpu kernel modesetting enabled. amdgpu remove_conflicting_pci_framebuffers: bar 0: 0x60 -> 0x600fff amdgpu remove_conflicting_pci_framebuffers: bar 2: 0x601000 -> 0x60101f amdgpu remove_conflicting_pci_framebuffers: bar 5: 0x7e80 -> 0x7e87 fb0: switching to amdgpudrmfb from EFI VGA amdgpu vgaarb: deactivate vga console amdgpu enabling device (0106 -> 0107) amdgpu Direct firmware load for amdgpu/navi14_gpu_info.bin failed with error -2 amdgpu Failed to load gpu_info firmware "amdgpu/navi14_gpu_info.bin" amdgpu Fatal error during GPU init [Fix] Patchset[1] for navi14's support currently landed in focal's linux-firmware, so we backported them to bionic's linux-firmware. [1]: aa95e90b2c638f1ca6647d12b2d1b18284428f9c d4f88ea76e442e6652de1367050e33314594d533 40656437f476ef7c47972731671ddcc9e4c4225b 7319341e6e40f8bae1f2623eb5e4ddc0e2b50076 b5b176ac09b6d1211da1e5db8e0c31ac830e4b8c [Test] The amdgpu can be recognized and initialized when booting. # dmesg | grep amdgpu [drm] amdgpu kernel modesetting enabled. amdgpu remove_conflicting_pci_framebuffers: bar 0: 0x60 -> 0x600fff amdgpu remove_conflicting_pci_framebuffers: bar 2: 0x601000 -> 0x60101f amdgpu remove_conflicting_pci_framebuffers: bar 5: 0x7e80 -> 0x7e87 amdgpu enabling device (0106 -> 0107) amdgpu VRAM: 8176M 0x0080 - 0x0081FEFF (8176M used) amdgpu GART: 512M 0x - 0x1FFF [drm] amdgpu: 8176M of VRAM memory ready [drm] amdgpu: 8176M of GTT memory ready. ... [drm] Initialized amdgpu 3.35.0 20150101 for :03:00.0 on minor 1 [Regression Potential] Low, just adding new navi14 firmware, no change to existing firmware. X-HWE-Bug: Bug #1880678 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-hotpie+X34 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-05-25 (6 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Package: linux-firmware 1.173.18+navi14 [origin: LP-PPA-shanelin-linux-firmware] PackageArchitecture: all ProcVersionSignature: Ubuntu 5.4.0-31.35~18.04.2-generic 5.4.34 Tags: bionic uec-images third-party-packages Uname: Linux 5.4.0-31-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1881525/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884288] Re: LapBook Pro touchpad (HTIX5288:00) sometimes does not work when machine is restarted
"Not working" right after boot? If it stops working in the middle of usage, it's a different bug. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884288 Title: LapBook Pro touchpad (HTIX5288:00) sometimes does not work when machine is restarted Status in linux package in Ubuntu: Incomplete Bug description: Touchpad completely ceases to work sometimes upon startup / restart. When this happens, I have to plug in an external mouse to navigate as touchpad is not even recognised as a device when I use xinput command in terminal. I removed and reinstalled xserver-xorg-input-synaptics which may have got it working again, although I am not too sure. When the trackpad is working, it's device name is listed as HTIX5288:00 0911:5288 Touchpad. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 19 18:03:47 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 605 [8086:3185] (rev 03) (prog-if 00 [VGA controller]) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:6366 Microdia USB 2.0 Camera Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=c549aad1-cbca-42d0-abc5-e73556f0921b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/29/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E.G140J.D8.E1.016.bin dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE.G140J.D8.E1.016.bin:bd11/29/2019:svn:pnLapBookPro:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: LapBook Pro dmi.product.sku: Default string dmi.product.version: Default string version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.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 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ian1619 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:6366 Microdia USB 2.0 Camera Bus 001 Device 008: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=c549aad1-cbca-42d0-abc5-e73556f0921b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 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.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: _MarkForUpload: True dmi.bios.date: 11/29/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E.G140J.D8.E1.016.bin dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default str
[Kernel-packages] [Bug 1886668] Re: linux 4.15.0-109-generic network DoS regression vs -108
** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1886668 Title: linux 4.15.0-109-generic network DoS regression vs -108 Status in linux package in Ubuntu: Incomplete Bug description: Reported from a user: Several of our infrastructure VMs recently started crashing (oops attached), after they upgraded to -109. -108 appears to be stable. Analysing the crash, it appears to be a wild pointer access in a BPF filter, which makes this (probably) a network-traffic triggered crash. [ 696.396831] general protection fault: [#1] SMP PTI [ 696.396843] Modules linked in: iscsi_target_mod target_core_mod ipt_MASQUERADE nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_filter xt_conntrack nf_nat nf_conntrack br_netfilter bridge nfsv3 cmac arc4 md4 rpcsec_gss_krb5 nfsv4 nls_utf8 cifs nfs aufs ccm fscache binfmt_misc overlay xfs libcrc32c intel_rapl crct10dif_pclmul crc32_pclmul ghash_clmulni_intel ppdev pcbc aesni_intel aes_x86_64 crypto_simd glue_helper cryptd input_leds joydev intel_rapl_perf serio_raw parport_pc parport mac_hid sch_fq_codel nfsd 8021q auth_rpcgss garp nfs_acl mrp lockd stp llc grace xenfs sunrpc xen_privcmd ip_tables x_tables autofs4 hid_generic usbhid hid psmouse i2c_piix4 pata_acpi floppy [ 696.396966] CPU: 6 PID: 0 Comm: swapper/6 Not tainted 4.15.0-109-generic #110-Ubuntu [ 696.396979] Hardware name: Xen HVM domU, BIOS 4.7.6-1.26 12/03/2018 [ 696.396993] RIP: 0010:__cgroup_bpf_run_filter_skb+0xbb/0x1e0 [ 696.397005] RSP: 0018:893fdcb83a70 EFLAGS: 00010292 [ 696.397015] RAX: 6d69546e6f697469 RBX: RCX: 0014 [ 696.397028] RDX: RSI: 893fd036 RDI: 893fb5154800 [ 696.397041] RBP: 893fdcb83ad0 R08: 0001 R09: [ 696.397058] R10: R11: 0003 R12: 0014 [ 696.397075] R13: 893fb5154800 R14: 0020 R15: 893fc6ba4d00 [ 696.397091] FS: () GS:893fdcb8() knlGS: [ 696.397107] CS: 0010 DS: ES: CR0: 80050033 [ 696.397119] CR2: 00c0001b4000 CR3: 0006dce0a004 CR4: 003606e0 [ 696.397135] DR0: DR1: DR2: [ 696.397152] DR3: DR6: fffe0ff0 DR7: 0400 [ 696.397169] Call Trace: [ 696.397175] [ 696.397183] sk_filter_trim_cap+0xd0/0x1b0 [ 696.397191] tcp_v4_rcv+0x8b7/0xa80 [ 696.397199] ip_local_deliver_finish+0x66/0x210 [ 696.397208] ip_local_deliver+0x7e/0xe0 [ 696.397215] ? ip_rcv_finish+0x430/0x430 [ 696.397223] ip_rcv_finish+0x129/0x430 [ 696.397230] ip_rcv+0x296/0x360 [ 696.397238] ? inet_del_offload+0x40/0x40 [ 696.397249] __netif_receive_skb_core+0x432/0xb80 [ 696.397261] ? skb_send_sock+0x50/0x50 [ 696.397271] ? tcp4_gro_receive+0x137/0x1a0 [ 696.397280] __netif_receive_skb+0x18/0x60 [ 696.397290] ? __netif_receive_skb+0x18/0x60 [ 696.397300] netif_receive_skb_internal+0x45/0xe0 [ 696.397309] napi_gro_receive+0xc5/0xf0 [ 696.397317] xennet_poll+0x9ca/0xbc0 [ 696.397325] net_rx_action+0x140/0x3a0 [ 696.397334] __do_softirq+0xe4/0x2d4 [ 696.397344] irq_exit+0xc5/0xd0 [ 696.397352] xen_evtchn_do_upcall+0x30/0x50 [ 696.397361] xen_hvm_callback_vector+0x90/0xa0 [ 696.397371] [ 696.397378] RIP: 0010:native_safe_halt+0x12/0x20 [ 696.397390] RSP: 0018:94c4862cbe80 EFLAGS: 0246 ORIG_RAX: ff0c [ 696.397405] RAX: 8efc1800 RBX: 0006 RCX: [ 696.397419] RDX: RSI: RDI: [ 696.397435] RBP: 94c4862cbe80 R08: 0002 R09: 0001 [ 696.397449] R10: 0010 R11: 0397 R12: 0006 [ 696.397462] R13: R14: R15: [ 696.397479] ? __sched_text_end+0x1/0x1 [ 696.397489] default_idle+0x20/0x100 [ 696.397499] arch_cpu_idle+0x15/0x20 [ 696.397507] default_idle_call+0x23/0x30 [ 696.397515] do_idle+0x172/0x1f0 [ 696.397522] cpu_startup_entry+0x73/0x80 [ 696.397530] start_secondary+0x1ab/0x20
[Kernel-packages] [Bug 1886277] Re: unable to handle page fault in mempool_alloc_slab
I tried bisecting the kernel as described in #22. However, I used the URL git://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/focal instead of git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/bionic, I hope that's correct. The fakeroot command works and builds the kernel. However, doing make later fails with: *** *** Configuration file ".config" not found! *** *** Please run some configurator (e.g. "make oldconfig" or *** "make menuconfig" or "make xconfig"). *** make: *** [Makefile:695: .config] Error 1 I don't know how to go from here. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1886277 Title: unable to handle page fault in mempool_alloc_slab Status in linux package in Ubuntu: Incomplete Bug description: On kernel 5.4.0-40-generic in focal I'm getting errors like this on several machines with different hardware in the first hour after boot: Jul 04 16:58:32 hostname kernel: BUG: unable to handle page fault for address: 9083e222e632 Jul 04 16:58:32 hostname kernel: #PF: supervisor read access in kernel mode Jul 04 16:58:32 hostname kernel: #PF: error_code(0x) - not-present page Jul 04 16:58:32 hostname kernel: PGD 3ac205067 P4D 3ac205067 PUD 0 Jul 04 16:58:32 hostname kernel: Oops: [#1] SMP NOPTI Jul 04 16:58:32 hostname kernel: CPU: 4 PID: 289 Comm: kworker/u16:4 Tainted: G OE 5.4.0-40-generic #44-Ubuntu Jul 04 16:58:32 hostname kernel: Hardware name: LENOVO 20N2CTO1WW/20N2CTO1WW, BIOS N2IET88W (1.66 ) 04/22/2020 Jul 04 16:58:32 hostname kernel: Workqueue: rpciod rpc_async_schedule [sunrpc] Jul 04 16:58:32 hostname kernel: RIP: 0010:kmem_cache_alloc+0x7e/0x230 Jul 04 16:58:32 hostname kernel: Code: 99 01 00 00 4d 8b 07 65 49 8b 50 08 65 4c 03 05 40 9d 56 44 4d 8b 20 4d 85 e4 0f 84 85 01 00 00 41 8b 47 20 49 8b 3f 4c 01 e0 <48> 8b 18 48 89 c1 49 33 9f 70 01 00 00 4c 89 e0 48 0f c9 48 31 cb Jul 04 16:58:32 hostname kernel: RSP: 0018:bc38c046fcc8 EFLAGS: 00010282 Jul 04 16:58:32 hostname kernel: RAX: 9083e222e632 RBX: RCX: 0002 Jul 04 16:58:32 hostname kernel: RDX: 0009 RSI: 00092800 RDI: 00031fb0 Jul 04 16:58:32 hostname kernel: RBP: bc38c046fcf8 R08: 90836c331fb0 R09: c1436a94 Jul 04 16:58:32 hostname kernel: R10: 908368178d2c R11: 0018 R12: 9083e222e632 Jul 04 16:58:32 hostname kernel: R13: 00092800 R14: 908367ca6140 R15: 908367ca6140 Jul 04 16:58:32 hostname kernel: FS: () GS:90836c30() knlGS: Jul 04 16:58:32 hostname kernel: CS: 0010 DS: ES: CR0: 80050033 Jul 04 16:58:32 hostname kernel: CR2: 9083e222e632 CR3: 0003ab80a003 CR4: 003606e0 Jul 04 16:58:32 hostname kernel: Call Trace: Jul 04 16:58:32 hostname kernel: ? mempool_alloc_slab+0x17/0x20 Jul 04 16:58:32 hostname kernel: mempool_alloc_slab+0x17/0x20 Jul 04 16:58:32 hostname kernel: mempool_alloc+0x64/0x180 Jul 04 16:58:32 hostname kernel: rpc_malloc+0xa1/0xb0 [sunrpc] Jul 04 16:58:32 hostname kernel: call_allocate+0xd1/0x1b0 [sunrpc] Jul 04 16:58:32 hostname kernel: ? call_refreshresult+0x100/0x100 [sunrpc] Jul 04 16:58:32 hostname kernel: __rpc_execute+0x8c/0x3a0 [sunrpc] Jul 04 16:58:32 hostname kernel: rpc_async_schedule+0x30/0x50 [sunrpc] Jul 04 16:58:32 hostname kernel: process_one_work+0x1eb/0x3b0 Jul 04 16:58:32 hostname kernel: worker_thread+0x4d/0x400 Jul 04 16:58:32 hostname kernel: kthread+0x104/0x140 Jul 04 16:58:32 hostname kernel: ? process_one_work+0x3b0/0x3b0 Jul 04 16:58:32 hostname kernel: ? kthread_park+0x90/0x90 Jul 04 16:58:32 hostname kernel: ret_from_fork+0x35/0x40 Jul 04 16:58:32 hostname kernel: Modules linked in: rfcomm rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) msr ccm cmac algif_hash algif_skcipher af_alg aufs bnep overlay nls_iso8859_1 mei_hdcp intel_rapl_msr snd_s> Jul 04 16:58:32 hostname kernel: nvram ledtrig_audio mei_me cfg80211 mei processor_thermal_device snd_seq ucsi_acpi typec_ucsi intel_rapl_common intel_soc_dts_iosf snd_seq_device typec intel_pch_thermal snd_timer snd int3403_thermal soundcore int340x_thermal_zone i> Jul 04 16:58:32 hostname kernel: pinctrl_cannonlake video pinctrl_intel Jul 04 16:58:32 hostname kernel: CR2: 9083e222e632 Jul 04 16:58:32 hostname kernel: ---[ end trace cbbaed921eb439ce ]--- Jul 04 16:58:32 hostname kernel: RIP: 0010:kmem_cache_alloc+0x7e/0x230 Jul 04 16:58:32 hostname kernel: Code: 99 01 00 00 4d 8b 07 65 49 8b 50 08 65 4c 03 05 40 9d 56 44 4d 8b 20 4d 85 e4 0f 84 85 01 00 00 41 8b 47 20 49 8b 3f 4c 01 e0 <48> 8b 18 48 89 c1 49 33 9f 70 01 00 00 4c 89 e0 48 0f c9 48 31 cb Jul 04 16:58:32 hostname kernel: RSP: 0018:b
[Kernel-packages] [Bug 1886668] 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 1886668 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1886668 Title: linux 4.15.0-109-generic network DoS regression vs -108 Status in linux package in Ubuntu: Incomplete Bug description: Reported from a user: Several of our infrastructure VMs recently started crashing (oops attached), after they upgraded to -109. -108 appears to be stable. Analysing the crash, it appears to be a wild pointer access in a BPF filter, which makes this (probably) a network-traffic triggered crash. [ 696.396831] general protection fault: [#1] SMP PTI [ 696.396843] Modules linked in: iscsi_target_mod target_core_mod ipt_MASQUERADE nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_filter xt_conntrack nf_nat nf_conntrack br_netfilter bridge nfsv3 cmac arc4 md4 rpcsec_gss_krb5 nfsv4 nls_utf8 cifs nfs aufs ccm fscache binfmt_misc overlay xfs libcrc32c intel_rapl crct10dif_pclmul crc32_pclmul ghash_clmulni_intel ppdev pcbc aesni_intel aes_x86_64 crypto_simd glue_helper cryptd input_leds joydev intel_rapl_perf serio_raw parport_pc parport mac_hid sch_fq_codel nfsd 8021q auth_rpcgss garp nfs_acl mrp lockd stp llc grace xenfs sunrpc xen_privcmd ip_tables x_tables autofs4 hid_generic usbhid hid psmouse i2c_piix4 pata_acpi floppy [ 696.396966] CPU: 6 PID: 0 Comm: swapper/6 Not tainted 4.15.0-109-generic #110-Ubuntu [ 696.396979] Hardware name: Xen HVM domU, BIOS 4.7.6-1.26 12/03/2018 [ 696.396993] RIP: 0010:__cgroup_bpf_run_filter_skb+0xbb/0x1e0 [ 696.397005] RSP: 0018:893fdcb83a70 EFLAGS: 00010292 [ 696.397015] RAX: 6d69546e6f697469 RBX: RCX: 0014 [ 696.397028] RDX: RSI: 893fd036 RDI: 893fb5154800 [ 696.397041] RBP: 893fdcb83ad0 R08: 0001 R09: [ 696.397058] R10: R11: 0003 R12: 0014 [ 696.397075] R13: 893fb5154800 R14: 0020 R15: 893fc6ba4d00 [ 696.397091] FS: () GS:893fdcb8() knlGS: [ 696.397107] CS: 0010 DS: ES: CR0: 80050033 [ 696.397119] CR2: 00c0001b4000 CR3: 0006dce0a004 CR4: 003606e0 [ 696.397135] DR0: DR1: DR2: [ 696.397152] DR3: DR6: fffe0ff0 DR7: 0400 [ 696.397169] Call Trace: [ 696.397175] [ 696.397183] sk_filter_trim_cap+0xd0/0x1b0 [ 696.397191] tcp_v4_rcv+0x8b7/0xa80 [ 696.397199] ip_local_deliver_finish+0x66/0x210 [ 696.397208] ip_local_deliver+0x7e/0xe0 [ 696.397215] ? ip_rcv_finish+0x430/0x430 [ 696.397223] ip_rcv_finish+0x129/0x430 [ 696.397230] ip_rcv+0x296/0x360 [ 696.397238] ? inet_del_offload+0x40/0x40 [ 696.397249] __netif_receive_skb_core+0x432/0xb80 [ 696.397261] ? skb_send_sock+0x50/0x50 [ 696.397271] ? tcp4_gro_receive+0x137/0x1a0 [ 696.397280] __netif_receive_skb+0x18/0x60 [ 696.397290] ? __netif_receive_skb+0x18/0x60 [ 696.397300] netif_receive_skb_internal+0x45/0xe0 [ 696.397309] napi_gro_receive+0xc5/0xf0 [ 696.397317] xennet_poll+0x9ca/0xbc0 [ 696.397325] net_rx_action+0x140/0x3a0 [ 696.397334] __do_softirq+0xe4/0x2d4 [ 696.397344] irq_exit+0xc5/0xd0 [ 696.397352] xen_evtchn_do_upcall+0x30/0x50 [ 696.397361] xen_hvm_callback_vector+0x90/0xa0 [ 696.397371] [ 696.397378] RIP: 0010:native_safe_halt+0x12/0x20 [ 696.397390] RSP: 0018:94c4862cbe80 EFLAGS: 0246 ORIG_RAX: ff0c [ 696.397405] RAX: 8efc1800 RBX: 0006 RCX: [ 696.397419] RDX: RSI: RDI: 0
[Kernel-packages] [Bug 1882442] Re: Upgrade from 18.04 to 20.04 deactivates internal monitor in display manager
Can you please test kernel v4.15, which is used by 18.04: https://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15.18/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1882442 Title: Upgrade from 18.04 to 20.04 deactivates internal monitor in display manager Status in linux package in Ubuntu: Incomplete Status in linux package in Fedora: Unknown Bug description: output of lsb_release -rd: Description: Ubuntu 20.04 LTS Release: 20.04 I recently upgraded from 18.04 to 20.04 and was using MATE. When the upgrade was run my external HDMI monitor was plugged in, after the update, when I reboot, the internal monitor shows the beginning of the boot process (I deactivated 'silent splash' by editing grub.cfg) then it switches to the HDMI monitor and the internal monitor goes dark. I can also get the tty consoles on the external monitor but not on the internal monitor. In MATE it was a real problem because the panel is apparently still on the invisible part of the desktop; I used a tty to install gnome, then I could get the display settings by right-clicking on the desktop, and setting the monitors to mirror, so I can reach applications, etc. Computer is a Dell Inspiron 3275 AIO with touch screen and Intel on-board video, I think. I had no problems with Ubuntu 18.04 with MATE. The problem seems to be similar to this bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874194 but sort of the reverse, in that the internal monitor is the problem. Thank you for your help. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: david 2012 F pulseaudio /dev/snd/controlC1: david 2012 F pulseaudio /dev/snd/controlC0: david 2012 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jun 7 11:43:37 2020 HibernationDevice: RESUME=UUID=3b1a8a2e-1937-4785-b4bb-49f9a251b292 InstallationDate: Installed on 2020-03-07 (91 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Inspiron 3275 AIO ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=95b8de7f-9de3-4cea-b947-e135a738948c ro RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-06-06 (1 days ago) dmi.bios.date: 03/15/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 04NJ6P dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 00 dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd03/15/2019:svnDellInc.:pnInspiron3275AIO:pvr1.7.0:rvnDellInc.:rn04NJ6P:rvrA02:cvnDellInc.:ct13:cvr00: dmi.product.family: Inspiron dmi.product.name: Inspiron 3275 AIO dmi.product.sku: 0855 dmi.product.version: 1.7.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882442/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886337] Re: Qualcomm Atheros QCA6174 802.11ac - Ubuntu 20.04
1: phy0: Wireless LAN Soft blocked: no Hard blocked: yes Can you please boot 19.10 live USB and see if it's still hard blocked? -- 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/1886337 Title: Qualcomm Atheros QCA6174 802.11ac - Ubuntu 20.04 Status in linux-firmware package in Ubuntu: Incomplete Bug description: My notebook has the Qualcomm Atheros QCA6174 802.11ac wireless network adapter (rev 32). I have no problem using this device on Ubuntu 19.10, works well. So, After I Format and Install Ubuntu 20.04 stopped working I Used to use Ubuntu 19.04 and linux-firmware 1.183 - Wifi - OK Now, I tried Ubuntu 20.04 with linux-firmware is 1.187 and it stopped working. After I tried Ubuntu 20.04 with linux-firmware is 1.187.1 and it stopped working. Now I need Using Ubuntu 20.04 with linux-firmware is 1.183 and it working well, But I need hold linux-firmware. So after I download 19.10's linux-firmware package from the ubuntu repositories, which is at 1.183. After I installed and apt-marked hold the package, so that it would not be upgrade, and rebooted, my wifi worked well. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.183 Uname: Linux 5.4.0-40-generic x86_64 Architecture: amd64 NonfreeKernelModules: nvidia_modeset nvidia ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dmenezes 2470 F pulseaudio /dev/snd/controlC0: dmenezes 2470 F pulseaudio CasperMD5CheckResult: skip Dependencies: DistroRelease: Ubuntu 20.04 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e007 Qualcomm Atheros Communications Bus 001 Device 003: ID 0c45:6a08 Microdia Integrated_Webcam_HD Bus 001 Device 002: ID 093a:2533 Pixart Imaging, Inc. Gaming Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. G7 7588 NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice talpa_vcdevice talpa_core talpa_linux talpa_syscallhook nvidia_modeset nvidia Package: linux-firmware 1.187.1 PackageArchitecture: all 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.4.0-40-generic root=UUID=330509ee-8a3f-4851-b437-1a9b3a72c353 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 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.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 Tags: focal Uname: Linux 5.4.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 07/15/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.1 dmi.board.name: 0PK2PP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.1:bd07/15/2019:svnDellInc.:pnG77588:pvr:rvnDellInc.:rn0PK2PP:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: GSeries dmi.product.name: G7 7588 dmi.product.sku: 0825 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1886337/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884288] Re: LapBook Pro touchpad (HTIX5288:00) sometimes does not work when machine is restarted
It's an all or nothing bug for my machine, if it doesn't work directly after boot it will never spontaneously start working again in the middle of a session. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884288 Title: LapBook Pro touchpad (HTIX5288:00) sometimes does not work when machine is restarted Status in linux package in Ubuntu: Incomplete Bug description: Touchpad completely ceases to work sometimes upon startup / restart. When this happens, I have to plug in an external mouse to navigate as touchpad is not even recognised as a device when I use xinput command in terminal. I removed and reinstalled xserver-xorg-input-synaptics which may have got it working again, although I am not too sure. When the trackpad is working, it's device name is listed as HTIX5288:00 0911:5288 Touchpad. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 19 18:03:47 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 605 [8086:3185] (rev 03) (prog-if 00 [VGA controller]) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:6366 Microdia USB 2.0 Camera Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=c549aad1-cbca-42d0-abc5-e73556f0921b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/29/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E.G140J.D8.E1.016.bin dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE.G140J.D8.E1.016.bin:bd11/29/2019:svn:pnLapBookPro:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: LapBook Pro dmi.product.sku: Default string dmi.product.version: Default string version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.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 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ian1619 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:6366 Microdia USB 2.0 Camera Bus 001 Device 008: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=c549aad1-cbca-42d0-abc5-e73556f0921b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 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.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: _MarkForUpload: True dmi.bios.date: 11/29/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E.G140J.D8.E1.016.bin dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chass
[Kernel-packages] [Bug 1884288] Re: LapBook Pro touchpad (HTIX5288:00) sometimes does not work when machine is restarted
Likewise when it is working, it will never spontaneously stop working in the middle of a session. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884288 Title: LapBook Pro touchpad (HTIX5288:00) sometimes does not work when machine is restarted Status in linux package in Ubuntu: Incomplete Bug description: Touchpad completely ceases to work sometimes upon startup / restart. When this happens, I have to plug in an external mouse to navigate as touchpad is not even recognised as a device when I use xinput command in terminal. I removed and reinstalled xserver-xorg-input-synaptics which may have got it working again, although I am not too sure. When the trackpad is working, it's device name is listed as HTIX5288:00 0911:5288 Touchpad. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 19 18:03:47 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 605 [8086:3185] (rev 03) (prog-if 00 [VGA controller]) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:6366 Microdia USB 2.0 Camera Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=c549aad1-cbca-42d0-abc5-e73556f0921b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/29/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E.G140J.D8.E1.016.bin dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE.G140J.D8.E1.016.bin:bd11/29/2019:svn:pnLapBookPro:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: LapBook Pro dmi.product.sku: Default string dmi.product.version: Default string version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.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 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ian1619 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:6366 Microdia USB 2.0 Camera Bus 001 Device 008: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=c549aad1-cbca-42d0-abc5-e73556f0921b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 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.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: _MarkForUpload: True dmi.bios.date: 11/29/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E.G140J.D8.E1.016.bin dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default str
[Kernel-packages] [Bug 1667750] Re: xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13
The issue was raised to ASMedia and they confirm this can only be fixed by firmware upgrade. Please push the hardware/motherboard vendor to roll out firmware update for your device. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1667750 Title: xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Zesty: Fix Released Status in linux source package in Artful: Fix Released Status in linux package in Arch Linux: New Status in linux package in Debian: New Status in linux package in Fedora: Confirmed Bug description: [SRU Justification] [Impact] Dell TB16 docking station has issue to use gigabit ethernet. The ethernet will disconnect unless it's changed to 100Mb/s. [Test Case] Download some big files from the web. User confirms the patch fixes the issue. [Regression Potential] This patch only effects ASMEDIA's ASM1042A. The regression potential is low, also limited to the specific device. --- My system contains a Realtek Semiconductor Corp. RTL8153 Gigabit Ethernet Adapter which is on usb3 bus in my docking station (Dell TB16) which is attached to my laptop (Dell XPS9550) via Thunderbolt 3. I get usb related kernel error messages when I initiate a high speed transfer (by issuing wget http://cdimage.ubuntu.com/daily-live/current /zesty-desktop-amd64.iso) and the download fails. This does not happened when the Ethernet adapter is connected to a 100Mb/s switch, but only when connected to 1000Mb/s. It also does not happened with slow traffic (e.g. web page browsing). This is not a new bug with kernel 4.10, but has been going on since at least 4.7 and maybe (probably?) since forever. I'm aware of several others with this configuration (RTL8153 on usb3 behind thunderbolt 3) that have the same issue. This bug is also not specific to Ubuntu; I also get it on Arch Linux. I've also tested and seen this bug with several different models of thunderbolt 3 docks. Here are the relevant kernel log messages: Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 0004777d9010 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 000475a14000 seg-end 000475a14ff0 Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 0004777d9020 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 000475a14000 seg-end 000475a14ff0 Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 0004777d9030 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 000475a14000 seg-end 000475a14ff0 Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 0004777d9040 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 000475a14000 seg-end 000475a14ff0 Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 0004777d9050 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 000475a14000 seg-end 000475a14ff0 Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 0004777d9060 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 000475a14000 seg-end 000475a14ff0 Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 0004777d9070 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 000475a14000 seg-end 000475a14ff0 Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 0004777d9080 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 000475a
Re: [Kernel-packages] [Bug 1886269] Re: ps/2 mouse not working
Thanks for the update Mr. Daniel and Mr. Feng, it was indeed kernel problem , now the mouse is working fine and system is updating properly. Keep up the good work and stay healthy. On Mon, 6 Jul, 2020, 09:45 Kai-Heng Feng, <1886...@bugs.launchpad.net> wrote: > Please boot with kernel parameter "i8042.nopnp". > > ** Changed in: linux (Ubuntu) >Status: Confirmed => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1886269 > > Title: > ps/2 mouse not working > > Status in linux package in Ubuntu: > Incomplete > > Bug description: > ps/2 mouse not working , gave some command in terminal , this bug came > out. > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: xorg 1:7.7+19ubuntu7.1 > ProcVersionSignature: Ubuntu 4.15.0-109.110-generic 4.15.18 > Uname: Linux 4.15.0-109-generic x86_64 > .tmp.unity_support_test.0: > > ApportVersion: 2.20.9-0ubuntu7.15 > Architecture: amd64 > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Sat Jul 4 19:25:07 2020 > DistUpgraded: 2020-07-03 12:12:10,464 DEBUG Running PostInstallScript: > './xorg_fix_proprietary.py' > DistroCodename: bionic > DistroVariant: ubuntu > GraphicsCard: >Intel Corporation 4 Series Chipset Integrated Graphics Controller > [8086:2e32] (rev 03) (prog-if 00 [VGA controller]) > Subsystem: Intel Corporation 4 Series Chipset Integrated Graphics > Controller [8086:d613] > InstallationDate: Installed on 2020-06-30 (4 days ago) > InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 > (20160420.1) > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-109-generic > root=UUID=7093ceae-5eb7-497e-8809-023c282ce7a1 ro quiet splash vt.handoff=1 > SourcePackage: xorg > UpgradeStatus: Upgraded to bionic on 2020-07-03 (1 days ago) > dmi.bios.date: 01/08/2009 > dmi.bios.vendor: Intel Corp. > dmi.bios.version: RQG4110H.86A.0009.2009.0108.1005 > dmi.board.asset.tag: To be filled by O.E.M. > dmi.board.name: DG41RQ > dmi.board.vendor: Intel Corporation > dmi.board.version: AAE54511-203 > dmi.chassis.type: 3 > dmi.modalias: > dmi:bvnIntelCorp.:bvrRQG4110H.86A.0009.2009.0108.1005:bd01/08/2009:svn:pn:pvr:rvnIntelCorporation:rnDG41RQ:rvrAAE54511-203:cvn:ct3:cvr: > version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 > version.libdrm2: libdrm2 2.4.101-2~18.04.1 > version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 > version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 > version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev > 1:2.10.5-1ubuntu1 > version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 > version.xserver-xorg-video-intel: xserver-xorg-video-intel > 2:2.99.917+git20171229-1 > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 > xserver.bootTime: Fri Jul 3 08:17:23 2020 > xserver.configfile: default > xserver.errors: > > xserver.logfile: /var/log/Xorg.0.log > xserver.outputs: > > xserver.version: 2:1.18.4-0ubuntu0.8 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886269/+subscriptions > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1886269 Title: ps/2 mouse not working Status in linux package in Ubuntu: Incomplete Bug description: ps/2 mouse not working , gave some command in terminal , this bug came out. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-109.110-generic 4.15.18 Uname: Linux 4.15.0-109-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jul 4 19:25:07 2020 DistUpgraded: 2020-07-03 12:12:10,464 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e32] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:d613] InstallationDate: Installed on 2020-06-30 (4 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-109-generic root=UUID=7093ceae-5eb7-497e-8809-023c282ce7a1 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2020-07-03 (1 days ago) dmi.bios.date: 01/08/2009 dmi.bios.vendor: Intel Corp. dmi.bios.version: RQG4110H.86A.0009.2009.0108.1005 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DG41RQ dmi.board.vendor: Intel Corporation dmi.boa
[Kernel-packages] [Bug 1884288] Re: LapBook Pro touchpad (HTIX5288:00) sometimes does not work when machine is restarted
Not working directly after boot, this was always the issue, never in the middle of usage. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884288 Title: LapBook Pro touchpad (HTIX5288:00) sometimes does not work when machine is restarted Status in linux package in Ubuntu: Incomplete Bug description: Touchpad completely ceases to work sometimes upon startup / restart. When this happens, I have to plug in an external mouse to navigate as touchpad is not even recognised as a device when I use xinput command in terminal. I removed and reinstalled xserver-xorg-input-synaptics which may have got it working again, although I am not too sure. When the trackpad is working, it's device name is listed as HTIX5288:00 0911:5288 Touchpad. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 19 18:03:47 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 605 [8086:3185] (rev 03) (prog-if 00 [VGA controller]) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:6366 Microdia USB 2.0 Camera Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=c549aad1-cbca-42d0-abc5-e73556f0921b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/29/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E.G140J.D8.E1.016.bin dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE.G140J.D8.E1.016.bin:bd11/29/2019:svn:pnLapBookPro:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: LapBook Pro dmi.product.sku: Default string dmi.product.version: Default string version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.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 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ian1619 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:6366 Microdia USB 2.0 Camera Bus 001 Device 008: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=c549aad1-cbca-42d0-abc5-e73556f0921b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 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.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: _MarkForUpload: True dmi.bios.date: 11/29/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E.G140J.D8.E1.016.bin dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dm
[Kernel-packages] [Bug 1886277] Re: unable to handle page fault in mempool_alloc_slab
Please ignore "Repeat to "make -j`nproc` deb-pkg" until you find the offending commit." it's the other way to build a kernel. Please install newly build kernel package, reboot and test. Then continue the process with `git bisect good` or `git bisect bad`. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1886277 Title: unable to handle page fault in mempool_alloc_slab Status in linux package in Ubuntu: Incomplete Bug description: On kernel 5.4.0-40-generic in focal I'm getting errors like this on several machines with different hardware in the first hour after boot: Jul 04 16:58:32 hostname kernel: BUG: unable to handle page fault for address: 9083e222e632 Jul 04 16:58:32 hostname kernel: #PF: supervisor read access in kernel mode Jul 04 16:58:32 hostname kernel: #PF: error_code(0x) - not-present page Jul 04 16:58:32 hostname kernel: PGD 3ac205067 P4D 3ac205067 PUD 0 Jul 04 16:58:32 hostname kernel: Oops: [#1] SMP NOPTI Jul 04 16:58:32 hostname kernel: CPU: 4 PID: 289 Comm: kworker/u16:4 Tainted: G OE 5.4.0-40-generic #44-Ubuntu Jul 04 16:58:32 hostname kernel: Hardware name: LENOVO 20N2CTO1WW/20N2CTO1WW, BIOS N2IET88W (1.66 ) 04/22/2020 Jul 04 16:58:32 hostname kernel: Workqueue: rpciod rpc_async_schedule [sunrpc] Jul 04 16:58:32 hostname kernel: RIP: 0010:kmem_cache_alloc+0x7e/0x230 Jul 04 16:58:32 hostname kernel: Code: 99 01 00 00 4d 8b 07 65 49 8b 50 08 65 4c 03 05 40 9d 56 44 4d 8b 20 4d 85 e4 0f 84 85 01 00 00 41 8b 47 20 49 8b 3f 4c 01 e0 <48> 8b 18 48 89 c1 49 33 9f 70 01 00 00 4c 89 e0 48 0f c9 48 31 cb Jul 04 16:58:32 hostname kernel: RSP: 0018:bc38c046fcc8 EFLAGS: 00010282 Jul 04 16:58:32 hostname kernel: RAX: 9083e222e632 RBX: RCX: 0002 Jul 04 16:58:32 hostname kernel: RDX: 0009 RSI: 00092800 RDI: 00031fb0 Jul 04 16:58:32 hostname kernel: RBP: bc38c046fcf8 R08: 90836c331fb0 R09: c1436a94 Jul 04 16:58:32 hostname kernel: R10: 908368178d2c R11: 0018 R12: 9083e222e632 Jul 04 16:58:32 hostname kernel: R13: 00092800 R14: 908367ca6140 R15: 908367ca6140 Jul 04 16:58:32 hostname kernel: FS: () GS:90836c30() knlGS: Jul 04 16:58:32 hostname kernel: CS: 0010 DS: ES: CR0: 80050033 Jul 04 16:58:32 hostname kernel: CR2: 9083e222e632 CR3: 0003ab80a003 CR4: 003606e0 Jul 04 16:58:32 hostname kernel: Call Trace: Jul 04 16:58:32 hostname kernel: ? mempool_alloc_slab+0x17/0x20 Jul 04 16:58:32 hostname kernel: mempool_alloc_slab+0x17/0x20 Jul 04 16:58:32 hostname kernel: mempool_alloc+0x64/0x180 Jul 04 16:58:32 hostname kernel: rpc_malloc+0xa1/0xb0 [sunrpc] Jul 04 16:58:32 hostname kernel: call_allocate+0xd1/0x1b0 [sunrpc] Jul 04 16:58:32 hostname kernel: ? call_refreshresult+0x100/0x100 [sunrpc] Jul 04 16:58:32 hostname kernel: __rpc_execute+0x8c/0x3a0 [sunrpc] Jul 04 16:58:32 hostname kernel: rpc_async_schedule+0x30/0x50 [sunrpc] Jul 04 16:58:32 hostname kernel: process_one_work+0x1eb/0x3b0 Jul 04 16:58:32 hostname kernel: worker_thread+0x4d/0x400 Jul 04 16:58:32 hostname kernel: kthread+0x104/0x140 Jul 04 16:58:32 hostname kernel: ? process_one_work+0x3b0/0x3b0 Jul 04 16:58:32 hostname kernel: ? kthread_park+0x90/0x90 Jul 04 16:58:32 hostname kernel: ret_from_fork+0x35/0x40 Jul 04 16:58:32 hostname kernel: Modules linked in: rfcomm rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) msr ccm cmac algif_hash algif_skcipher af_alg aufs bnep overlay nls_iso8859_1 mei_hdcp intel_rapl_msr snd_s> Jul 04 16:58:32 hostname kernel: nvram ledtrig_audio mei_me cfg80211 mei processor_thermal_device snd_seq ucsi_acpi typec_ucsi intel_rapl_common intel_soc_dts_iosf snd_seq_device typec intel_pch_thermal snd_timer snd int3403_thermal soundcore int340x_thermal_zone i> Jul 04 16:58:32 hostname kernel: pinctrl_cannonlake video pinctrl_intel Jul 04 16:58:32 hostname kernel: CR2: 9083e222e632 Jul 04 16:58:32 hostname kernel: ---[ end trace cbbaed921eb439ce ]--- Jul 04 16:58:32 hostname kernel: RIP: 0010:kmem_cache_alloc+0x7e/0x230 Jul 04 16:58:32 hostname kernel: Code: 99 01 00 00 4d 8b 07 65 49 8b 50 08 65 4c 03 05 40 9d 56 44 4d 8b 20 4d 85 e4 0f 84 85 01 00 00 41 8b 47 20 49 8b 3f 4c 01 e0 <48> 8b 18 48 89 c1 49 33 9f 70 01 00 00 4c 89 e0 48 0f c9 48 31 cb Jul 04 16:58:32 hostname kernel: RSP: 0018:bc38c046fcc8 EFLAGS: 00010282 Jul 04 16:58:32 hostname kernel: RAX: 9083e222e632 RBX: RCX: 0002 Jul 04 16:58:32 hostname kernel: RDX: 0009 RSI: 00092800 RDI: 00031fb0 Jul 04 16:58:32 hostname kernel: RBP: bc38c046fcf8 R08: 90836c331fb0 R09: ff
[Kernel-packages] [Bug 1886339] Re: Ubuntu freezes after PCIe Bus Error
Please test latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8-rc4/ ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1886339 Title: Ubuntu freezes after PCIe Bus Error Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu freezes after some time because of an error with the PCIe bus (see journalctl.log). After changing a kernelflag in /etc/default/grub 'GRUB_CMDLINE_LINUX_DEFAULT="quiet pcie_aspm=off"' the problem is solved. Desired outcome: implement this fix (automatically). I hope apport added everything important. If you have any further questions, feel free to contact me. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alex 1256 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sun Jul 5 20:09:51 2020 InstallationDate: Installed on 2020-07-04 (0 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20U2S04S00 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=/dev/mapper/vgkubuntu-root ro quiet pcie_aspm=off 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: 04/16/2020 dmi.bios.vendor: LENOVO dmi.bios.version: R17ET19W (1.02 ) dmi.board.asset.tag: Not Available dmi.board.name: 20U2S04S00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR17ET19W(1.02):bd04/16/2020:svnLENOVO:pn20U2S04S00:pvrThinkPadL14Gen1:rvnLENOVO:rn20U2S04S00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L14 Gen 1 dmi.product.name: 20U2S04S00 dmi.product.sku: LENOVO_MT_20U2_BU_Think_FM_ThinkPad L14 Gen 1 dmi.product.version: ThinkPad L14 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886339/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886339] Re: Ubuntu freezes after PCIe Bus Error
FWIW the culprit is NVMe in this bug. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1886339 Title: Ubuntu freezes after PCIe Bus Error Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu freezes after some time because of an error with the PCIe bus (see journalctl.log). After changing a kernelflag in /etc/default/grub 'GRUB_CMDLINE_LINUX_DEFAULT="quiet pcie_aspm=off"' the problem is solved. Desired outcome: implement this fix (automatically). I hope apport added everything important. If you have any further questions, feel free to contact me. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alex 1256 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sun Jul 5 20:09:51 2020 InstallationDate: Installed on 2020-07-04 (0 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20U2S04S00 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=/dev/mapper/vgkubuntu-root ro quiet pcie_aspm=off 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: 04/16/2020 dmi.bios.vendor: LENOVO dmi.bios.version: R17ET19W (1.02 ) dmi.board.asset.tag: Not Available dmi.board.name: 20U2S04S00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR17ET19W(1.02):bd04/16/2020:svnLENOVO:pn20U2S04S00:pvrThinkPadL14Gen1:rvnLENOVO:rn20U2S04S00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L14 Gen 1 dmi.product.name: 20U2S04S00 dmi.product.sku: LENOVO_MT_20U2_BU_Think_FM_ThinkPad L14 Gen 1 dmi.product.version: ThinkPad L14 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886339/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853665] Re: Realtek RTL8821CE [10ec:c821] Subsystem [103c:831a] Bluetooth not probed
[0.00] microcode: microcode updated early to revision 0xd6, date = 2020-04-27 [0.00] Linux version 5.8.0-050800-generic (kernel@gloin) (gcc (Ubuntu 9.3.0-13ubuntu1) 9.3.0, GNU ld (GNU Binutils for Ubuntu) 2.34) #202007052030 SMP Mon Jul 6 00:37:33 UTC 2020 [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.8.0-050800-generic root=UUID=a0cdf605-0b72-4674-a76e-ad1dbae26043 ro quiet splash vt.handoff=7 [0.00] KERNEL supported cpus: [0.00] Intel GenuineIntel [0.00] AMD AuthenticAMD [0.00] Hygon HygonGenuine [0.00] Centaur CentaurHauls [0.00] zhaoxin Shanghai [0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' [0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' [0.00] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers' [0.00] x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers' [0.00] x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR' [0.00] x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256 [0.00] x86/fpu: xstate_offset[3]: 832, xstate_sizes[3]: 64 [0.00] x86/fpu: xstate_offset[4]: 896, xstate_sizes[4]: 64 [0.00] x86/fpu: Enabled xstate features 0x1f, context size is 960 bytes, using 'compacted' format. [0.00] BIOS-provided physical RAM map: [0.00] BIOS-e820: [mem 0x-0x000937ff] usable [0.00] BIOS-e820: [mem 0x00093800-0x0009] reserved [0.00] BIOS-e820: [mem 0x000e-0x000f] reserved [0.00] BIOS-e820: [mem 0x0010-0x7a6aefff] usable [0.00] BIOS-e820: [mem 0x7a6af000-0x7b49efff] reserved [0.00] BIOS-e820: [mem 0x7b49f000-0x7bb8efff] ACPI NVS [0.00] BIOS-e820: [mem 0x7bb8f000-0x7bc0efff] ACPI data [0.00] BIOS-e820: [mem 0x7bc0f000-0x7bc0] usable [0.00] BIOS-e820: [mem 0x7bc1-0x7f7f] reserved [0.00] BIOS-e820: [mem 0xe000-0xefff] reserved [0.00] BIOS-e820: [mem 0xfe00-0xfe010fff] reserved [0.00] BIOS-e820: [mem 0xfed1-0xfed19fff] reserved [0.00] BIOS-e820: [mem 0xfed84000-0xfed84fff] reserved [0.00] BIOS-e820: [mem 0xfee0-0xfee00fff] reserved [0.00] BIOS-e820: [mem 0xff30-0x] reserved [0.00] BIOS-e820: [mem 0x0001-0x00027e7f] usable [0.00] NX (Execute Disable) protection: active [0.00] SMBIOS 3.0 present. [0.00] DMI: HP HP 250 G7 Notebook PC/8532, BIOS F.16 12/05/2018 [0.00] tsc: Detected 1800.000 MHz processor [0.001822] e820: update [mem 0x-0x0fff] usable ==> reserved [0.001825] e820: remove [mem 0x000a-0x000f] usable [0.001832] last_pfn = 0x27e800 max_arch_pfn = 0x4 [0.001837] MTRR default type: uncachable [0.001838] MTRR fixed ranges enabled: [0.001840] 0-9 write-back [0.001841] A-B uncachable [0.001842] C-F write-protect [0.001843] MTRR variable ranges enabled: [0.001845] 0 base 00FF00 mask 7FFF00 write-protect [0.001846] 1 base 007D00 mask 7FFF00 uncachable [0.001847] 2 base 00 mask 7F8000 write-back [0.001849] 3 base 01 mask 7F write-back [0.001850] 4 base 02 mask 7E write-back [0.001851] 5 base 007E00 mask 7FFE00 uncachable [0.001851] 6 disabled [0.001852] 7 disabled [0.001853] 8 disabled [0.001853] 9 disabled [0.002485] x86/PAT: Configuration [0-7]: WB WC UC- UC WB WP UC- WT [0.002730] last_pfn = 0x7bc10 max_arch_pfn = 0x4 [0.013768] found SMP MP-table at [mem 0x000fe1b0-0x000fe1bf] [0.013869] check: Scanning 1 areas for low memory corruption [0.013874] Using GB pages for direct mapping [0.014148] RAMDISK: [mem 0x31f2d000-0x34f8dfff] [0.014159] ACPI: Early table checksum verification disabled [0.014162] ACPI: RSDP 0x000FE020 24 (v02 HPQOEM) [0.014167] ACPI: XSDT 0x7BBEA188 FC (v01 HPQOEM SLIC-MPC HP 0113) [0.014174] ACPI: FACP 0x7BBEC000 00010C (v05 HPQOEM SLIC-MPC HP 0004) [0.014180] ACPI: DSDT 0x7BBA7000 04013F (v02 HPQOEM SLIC-MPC ACPI 0004) [0.014184] ACPI: FACS 0x7BB2E000 40 [0.014187] ACPI: UEFI 0x7BC0D000 000236 (v01 HPQOEM INSYDE 0001 HP 0004) [0.014191] ACPI: SSDT 0x7BC09000 0031C6 (v02 HPQOEM INSYDE 3000 ACPI 0004) [0.014194] ACPI: SSDT 0x7BC07000 0017C6 (v02 HPQOEM INSYDE 3000 ACPI 0004) [0.014198] ACPI: SSDT 0x7BC06000 F5 (v02
[Kernel-packages] [Bug 1886269] Re: ps/2 mouse not working
Does "i8042.nopnp" help? We'll need to make the change into the kernel itself. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1886269 Title: ps/2 mouse not working Status in linux package in Ubuntu: Incomplete Bug description: ps/2 mouse not working , gave some command in terminal , this bug came out. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-109.110-generic 4.15.18 Uname: Linux 4.15.0-109-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jul 4 19:25:07 2020 DistUpgraded: 2020-07-03 12:12:10,464 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e32] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:d613] InstallationDate: Installed on 2020-06-30 (4 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-109-generic root=UUID=7093ceae-5eb7-497e-8809-023c282ce7a1 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2020-07-03 (1 days ago) dmi.bios.date: 01/08/2009 dmi.bios.vendor: Intel Corp. dmi.bios.version: RQG4110H.86A.0009.2009.0108.1005 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DG41RQ dmi.board.vendor: Intel Corporation dmi.board.version: AAE54511-203 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrRQG4110H.86A.0009.2009.0108.1005:bd01/08/2009:svn:pn:pvr:rvnIntelCorporation:rnDG41RQ:rvrAAE54511-203:cvn:ct3:cvr: version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Fri Jul 3 08:17:23 2020 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886269/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884288] Re: LapBook Pro touchpad (HTIX5288:00) sometimes does not work when machine is restarted
Hmm. Ok. Then my patch doesn't work. Does a reboot from Windows to Linux always 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/1884288 Title: LapBook Pro touchpad (HTIX5288:00) sometimes does not work when machine is restarted Status in linux package in Ubuntu: Incomplete Bug description: Touchpad completely ceases to work sometimes upon startup / restart. When this happens, I have to plug in an external mouse to navigate as touchpad is not even recognised as a device when I use xinput command in terminal. I removed and reinstalled xserver-xorg-input-synaptics which may have got it working again, although I am not too sure. When the trackpad is working, it's device name is listed as HTIX5288:00 0911:5288 Touchpad. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 19 18:03:47 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 605 [8086:3185] (rev 03) (prog-if 00 [VGA controller]) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:6366 Microdia USB 2.0 Camera Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=c549aad1-cbca-42d0-abc5-e73556f0921b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/29/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E.G140J.D8.E1.016.bin dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE.G140J.D8.E1.016.bin:bd11/29/2019:svn:pnLapBookPro:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: LapBook Pro dmi.product.sku: Default string dmi.product.version: Default string version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.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 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ian1619 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:6366 Microdia USB 2.0 Camera Bus 001 Device 008: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=c549aad1-cbca-42d0-abc5-e73556f0921b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 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.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: _MarkForUpload: True dmi.bios.date: 11/29/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E.G140J.D8.E1.016.bin dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.m
[Kernel-packages] [Bug 1886188] Re: linux-libc-dev broken for crossbuilding, Multi-Arch:same violation
linux-riscv in groovy is still copied forward from focal and will pick up the change applied from focal when it is updated. Therefore I'm marking that task invalid. ** Changed in: linux (Ubuntu Focal) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Seth Forshee (sforshee) ** Changed in: linux (Ubuntu Groovy) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Groovy) Assignee: (unassigned) => Seth Forshee (sforshee) ** Changed in: linux-riscv (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-riscv (Ubuntu Focal) Assignee: (unassigned) => Seth Forshee (sforshee) ** Changed in: linux-riscv (Ubuntu Groovy) Status: New => Invalid ** Description changed: + SRU Justificatoin + + Impact: Building linux-libc-dev for riscv64 from the linux-riscv package + means that it can have a different version from the package on other + architectures. This makes it uninstallable for cross building. + + Fix: Move the riscv64 linux-libc-dev build back to the main kernel + package so that the version will match. + + Test Case: See below. + + Regression Potential: This could cause trouble if the main kernel + package version is behind the linux-riscv package version, and may + require artificially inflating the version of the linux package. + Currently this is not necessary, but it needs to be kept in mind when + preparing packages for upload with the fixes applied. + + --- + # apt install linux-libc-dev:amd64 linux-libc-dev:riscv64 Reading package lists... Done - Building dependency tree + Building dependency tree Reading state information... Done linux-libc-dev is already the newest version (5.4.0-26.30). Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: - linux-libc-dev : Breaks: linux-libc-dev:riscv64 (!= 5.4.0-26.30) but 5.4.0-27.31 is to be installed - linux-libc-dev:riscv64 : Breaks: linux-libc-dev (!= 5.4.0-27.31) but 5.4.0-26.30 is to be installed + linux-libc-dev : Breaks: linux-libc-dev:riscv64 (!= 5.4.0-26.30) but 5.4.0-27.31 is to be installed + linux-libc-dev:riscv64 : Breaks: linux-libc-dev (!= 5.4.0-27.31) but 5.4.0-26.30 is to be installed E: Unable to correct problems, you have held broken packages. $ rmadison -S linux-libc-dev | grep -e riscv64 -e amd64 | grep -e focal -e groovy - linux-libc-dev | 5.4.0-24.28| focal| riscv64 - linux-libc-dev | 5.4.0-26.30| focal| amd64, arm64, armhf, i386, ppc64el, s390x - linux-libc-dev | 5.4.0-26.30| groovy | amd64, arm64, armhf, i386, ppc64el, s390x - linux-libc-dev | 5.4.0-27.31| groovy | riscv64 - linux-libc-dev | 5.4.0-28.32| focal-security | riscv64 - linux-libc-dev | 5.4.0-28.32| focal-updates| riscv64 - linux-libc-dev | 5.4.0-40.44| focal-security | amd64, arm64, armhf, i386, ppc64el, s390x - linux-libc-dev | 5.4.0-40.44| focal-updates| amd64, arm64, armhf, i386, ppc64el, s390x - linux-libc-dev | 5.4.0-40.44| groovy-proposed | amd64, arm64, armhf, i386, ppc64el, s390x + linux-libc-dev | 5.4.0-24.28| focal| riscv64 + linux-libc-dev | 5.4.0-26.30| focal| amd64, arm64, armhf, i386, ppc64el, s390x + linux-libc-dev | 5.4.0-26.30| groovy | amd64, arm64, armhf, i386, ppc64el, s390x + linux-libc-dev | 5.4.0-27.31| groovy | riscv64 + linux-libc-dev | 5.4.0-28.32| focal-security | riscv64 + linux-libc-dev | 5.4.0-28.32| focal-updates| riscv64 + linux-libc-dev | 5.4.0-40.44| focal-security | amd64, arm64, armhf, i386, ppc64el, s390x + linux-libc-dev | 5.4.0-40.44| focal-updates| amd64, arm64, armhf, i386, ppc64el, s390x + linux-libc-dev | 5.4.0-40.44| groovy-proposed | amd64, arm64, armhf, i386, ppc64el, s390x This is broken. linux-libc-dev must have identical content for common files, across all architectures, and must have identical version number. A few ways to fix this: * Either enforce that src:linux & src:linux-riscv are at the same version number. But then reasons for splitting riscv into a separate build dissappear * Make src:linux build _just_ the headers linux-libc-dev for risv64, and nothing else. And stop bulding linux-libc-dev form the src:linux-riscv package. Just like it does for i386. * Or create new src:linux-headers that only builds linux-libc-dev for all architectures, without building any kernels. This way for example, we could rev userspace headers to v5.8/v5.9 ahead of said kernel landing, to shake out build-failures / userspace issues, whilst the
[Kernel-packages] [Bug 1853665] Re: Realtek RTL8821CE [10ec:c821] Subsystem [103c:831a] Bluetooth not probed
There's only WebCam on USB bus. Have you tried Windows? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1853665 Title: Realtek RTL8821CE [10ec:c821] Subsystem [103c:831a] Bluetooth not probed Status in linux package in Ubuntu: Incomplete Status in linux-oem package in Ubuntu: Confirmed Status in rtl8821ce package in Ubuntu: Confirmed Bug description: The driver installed just fine and wifi is working but bluetooth does not. I will gladly provide further debugging information. Ubuntu 19.10 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: steven 2090 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-11-17 (75 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0408:5321 Quanta Computer, Inc. HP Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP 250 G7 Notebook PC Package: rtl8821ce 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=/boot/vmlinuz-5.3.0-29-generic root=UUID=a0cdf605-0b72-4674-a76e-ad1dbae26043 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-29-generic N/A linux-backports-modules-5.3.0-29-generic N/A linux-firmware1.183.3 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: eoan Uname: Linux 5.3.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/05/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.16 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8532 dmi.board.vendor: HP dmi.board.version: 70.22 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.16:bd12/05/2018:svnHP:pnHP250G7NotebookPC:pvrType1ProductConfigId:rvnHP:rn8532:rvr70.22:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5336AN HP 200 dmi.product.name: HP 250 G7 Notebook PC dmi.product.sku: 6MQ54EA#ABD dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: steven 1931 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-11-17 (231 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0408:5321 Quanta Computer, Inc. HP Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 5: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M |__ Port 5: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M MachineType: HP HP 250 G7 Notebook PC Package: rtl8821ce 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=/boot/vmlinuz-5.4.0-40-generic root=UUID=a0cdf605-0b72-4674-a76e-ad1dbae26043 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no StagingDrivers: ashmem_linux Tags: focal staging staging Uname: Linux 5.4.0-40-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-18 (47 days ago) UserGroups: adm audio cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/05/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.16 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8532 dmi.board.vendor: HP dmi.board.version: 70.22 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.16:bd12/05/2018:svnHP:pnH
[Kernel-packages] [Bug 1886188] Re: linux-libc-dev broken for crossbuilding, Multi-Arch:same violation
https://lists.ubuntu.com/archives/kernel-team/2020-July/111881.html https://lists.ubuntu.com/archives/kernel-team/2020-July/111884.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1886188 Title: linux-libc-dev broken for crossbuilding, Multi-Arch:same violation Status in linux package in Ubuntu: In Progress Status in linux-riscv package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Status in linux-riscv source package in Focal: In Progress Status in linux source package in Groovy: In Progress Status in linux-riscv source package in Groovy: Invalid Bug description: SRU Justificatoin Impact: Building linux-libc-dev for riscv64 from the linux-riscv package means that it can have a different version from the package on other architectures. This makes it uninstallable for cross building. Fix: Move the riscv64 linux-libc-dev build back to the main kernel package so that the version will match. Test Case: See below. Regression Potential: This could cause trouble if the main kernel package version is behind the linux-riscv package version, and may require artificially inflating the version of the linux package. Currently this is not necessary, but it needs to be kept in mind when preparing packages for upload with the fixes applied. --- # apt install linux-libc-dev:amd64 linux-libc-dev:riscv64 Reading package lists... Done Building dependency tree Reading state information... Done linux-libc-dev is already the newest version (5.4.0-26.30). Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: linux-libc-dev : Breaks: linux-libc-dev:riscv64 (!= 5.4.0-26.30) but 5.4.0-27.31 is to be installed linux-libc-dev:riscv64 : Breaks: linux-libc-dev (!= 5.4.0-27.31) but 5.4.0-26.30 is to be installed E: Unable to correct problems, you have held broken packages. $ rmadison -S linux-libc-dev | grep -e riscv64 -e amd64 | grep -e focal -e groovy linux-libc-dev | 5.4.0-24.28| focal| riscv64 linux-libc-dev | 5.4.0-26.30| focal| amd64, arm64, armhf, i386, ppc64el, s390x linux-libc-dev | 5.4.0-26.30| groovy | amd64, arm64, armhf, i386, ppc64el, s390x linux-libc-dev | 5.4.0-27.31| groovy | riscv64 linux-libc-dev | 5.4.0-28.32| focal-security | riscv64 linux-libc-dev | 5.4.0-28.32| focal-updates| riscv64 linux-libc-dev | 5.4.0-40.44| focal-security | amd64, arm64, armhf, i386, ppc64el, s390x linux-libc-dev | 5.4.0-40.44| focal-updates| amd64, arm64, armhf, i386, ppc64el, s390x linux-libc-dev | 5.4.0-40.44| groovy-proposed | amd64, arm64, armhf, i386, ppc64el, s390x This is broken. linux-libc-dev must have identical content for common files, across all architectures, and must have identical version number. A few ways to fix this: * Either enforce that src:linux & src:linux-riscv are at the same version number. But then reasons for splitting riscv into a separate build dissappear * Make src:linux build _just_ the headers linux-libc-dev for risv64, and nothing else. And stop bulding linux-libc-dev form the src:linux- riscv package. Just like it does for i386. * Or create new src:linux-headers that only builds linux-libc-dev for all architectures, without building any kernels. This way for example, we could rev userspace headers to v5.8/v5.9 ahead of said kernel landing, to shake out build-failures / userspace issues, whilst the kernel itself is still baking in bootstrap/proposed PPA. This must be address in Focal and Groovy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886188/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884288] Re: LapBook Pro touchpad (HTIX5288:00) sometimes does not work when machine is restarted
I stripped my machine of Windows in favour of Ubuntu without a partition, unfortunately I could not foresee this problem with the touchpad. @Califa may be able to answer your question as I think they still have Windows on their machine. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884288 Title: LapBook Pro touchpad (HTIX5288:00) sometimes does not work when machine is restarted Status in linux package in Ubuntu: Incomplete Bug description: Touchpad completely ceases to work sometimes upon startup / restart. When this happens, I have to plug in an external mouse to navigate as touchpad is not even recognised as a device when I use xinput command in terminal. I removed and reinstalled xserver-xorg-input-synaptics which may have got it working again, although I am not too sure. When the trackpad is working, it's device name is listed as HTIX5288:00 0911:5288 Touchpad. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 19 18:03:47 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 605 [8086:3185] (rev 03) (prog-if 00 [VGA controller]) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:6366 Microdia USB 2.0 Camera Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=c549aad1-cbca-42d0-abc5-e73556f0921b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/29/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E.G140J.D8.E1.016.bin dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE.G140J.D8.E1.016.bin:bd11/29/2019:svn:pnLapBookPro:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: LapBook Pro dmi.product.sku: Default string dmi.product.version: Default string version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.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 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ian1619 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:6366 Microdia USB 2.0 Camera Bus 001 Device 008: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=c549aad1-cbca-42d0-abc5-e73556f0921b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 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.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: _MarkForUpload: True dmi.bios.date: 11/29/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E.G140J.D8.E1.016.bin dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default
[Kernel-packages] [Bug 1884288] Re: LapBook Pro touchpad (HTIX5288:00) sometimes does not work when machine is restarted
Tour kernel does seem to dramatically lower the chances of the touchpad not working upon reboot if that makes any sense. The newer Ubuntu kernel is very hit nad miss with the touchpad after 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/1884288 Title: LapBook Pro touchpad (HTIX5288:00) sometimes does not work when machine is restarted Status in linux package in Ubuntu: Incomplete Bug description: Touchpad completely ceases to work sometimes upon startup / restart. When this happens, I have to plug in an external mouse to navigate as touchpad is not even recognised as a device when I use xinput command in terminal. I removed and reinstalled xserver-xorg-input-synaptics which may have got it working again, although I am not too sure. When the trackpad is working, it's device name is listed as HTIX5288:00 0911:5288 Touchpad. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 19 18:03:47 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 605 [8086:3185] (rev 03) (prog-if 00 [VGA controller]) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:6366 Microdia USB 2.0 Camera Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=c549aad1-cbca-42d0-abc5-e73556f0921b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/29/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E.G140J.D8.E1.016.bin dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE.G140J.D8.E1.016.bin:bd11/29/2019:svn:pnLapBookPro:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: LapBook Pro dmi.product.sku: Default string dmi.product.version: Default string version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.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 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ian1619 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:6366 Microdia USB 2.0 Camera Bus 001 Device 008: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=c549aad1-cbca-42d0-abc5-e73556f0921b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 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.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: _MarkForUpload: True dmi.bios.date: 11/29/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E.G140J.D8.E1.016.bin dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default
[Kernel-packages] [Bug 1884288] Re: LapBook Pro touchpad (HTIX5288:00) sometimes does not work when machine is restarted
Apologies, I meant Your -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884288 Title: LapBook Pro touchpad (HTIX5288:00) sometimes does not work when machine is restarted Status in linux package in Ubuntu: Incomplete Bug description: Touchpad completely ceases to work sometimes upon startup / restart. When this happens, I have to plug in an external mouse to navigate as touchpad is not even recognised as a device when I use xinput command in terminal. I removed and reinstalled xserver-xorg-input-synaptics which may have got it working again, although I am not too sure. When the trackpad is working, it's device name is listed as HTIX5288:00 0911:5288 Touchpad. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 19 18:03:47 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 605 [8086:3185] (rev 03) (prog-if 00 [VGA controller]) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:6366 Microdia USB 2.0 Camera Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=c549aad1-cbca-42d0-abc5-e73556f0921b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/29/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E.G140J.D8.E1.016.bin dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE.G140J.D8.E1.016.bin:bd11/29/2019:svn:pnLapBookPro:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: LapBook Pro dmi.product.sku: Default string dmi.product.version: Default string version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.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 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ian1619 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:6366 Microdia USB 2.0 Camera Bus 001 Device 008: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=c549aad1-cbca-42d0-abc5-e73556f0921b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 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.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: _MarkForUpload: True dmi.bios.date: 11/29/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E.G140J.D8.E1.016.bin dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE.G140J.D8.E1.016.bi
