[Kernel-packages] [Bug 1854213] Re: RTL8821CE 802.11ac PCIe Wireless Network Adapter [10ec:c821] subsystem [17aa:38a8]: No Wifi Adapter found - Lenevo Ideapad 330 series
** 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/1854213 Title: RTL8821CE 802.11ac PCIe Wireless Network Adapter [10ec:c821] subsystem [17aa:38a8]: No Wifi Adapter found - Lenevo Ideapad 330 series Status in linux package in Ubuntu: Confirmed Status in rtl8821ce package in Ubuntu: New Bug description: Commands executed 1. ubuntu-bug linux 2. cat /proc/version_signature Ubuntu 5.3.0-23.25~18.04.2-generic 5.3.7 3. sudo lspci -vnvn > lspci-vnvn.log pcilib: sysfs_read_vpd: read failed: Input/output error 4. lsb_release -rd Description: Ubuntu 18.04.3 LTS Release: 18.04 5. apt-cache policy pkgname N: Unable to locate package pkgname What you expected to happen? Connect to the Internet after installing the update What happened instead? No Wifi Adapter found message displayed instead ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.3.0-23-generic 5.3.0-23.25~18.04.2 ProcVersionSignature: Ubuntu 5.3.0-23.25~18.04.2-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Nov 28 00:44:57 2019 InstallationDate: Installed on 2019-06-05 (175 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: linux-signed-hwe-edge UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: athena 1573 F pulseaudio /dev/snd/controlC0: athena 1573 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-06-05 (212 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: enp3s0f3u3 no wireless extensions. enp2s0no wireless extensions. lono wireless extensions. MachineType: LENOVO 81D2 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=29a08da7-0f52-4ee8-8424-f2b37885999f ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-24.26~18.04.2-generic 5.3.10 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.173.13 Tags: bionic Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/10/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 7VCN46WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330-15ARR dmi.modalias: dmi:bvnLENOVO:bvr7VCN46WW:bd12/10/2018:svnLENOVO:pn81D2:pvrLenovoideapad330-15ARR:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad330-15ARR: dmi.product.family: ideapad 330-15ARR dmi.product.name: 81D2 dmi.product.sku: LENOVO_MT_81D2_BU_idea_FM_ideapad 330-15ARR dmi.product.version: Lenovo ideapad 330-15ARR dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1854213/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1872964] Re: Reliable crash in lowlatency kernel with LXD
Hi Seth I have been deploying charmed-kubernetes on a LXD cluster. I didn't think the kernel crash was workload-specific, but of course it might be. It looked more likely to be ZFS + lowlatency + snaps triggering the issue. For now I have had to move to -generic on the machine which was causing the problem. I have ordered some more NUCs and will add -lowlatency nodes to a cluster when they arrive, to see if different workloads behave differently. Mark -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1872964 Title: Reliable crash in lowlatency kernel with LXD Status in linux-signed package in Ubuntu: Confirmed Bug description: Hello, I am able to crash 5.4.0-21-lowlatency running LXD. This machine in an Intel NUC, part of a three-member LXD cluster. The other machines do not show this crash and they are not running the lowlatency kernel, but that might be incidental. I will swap out the generic kernel for a while to see if the behaviour continues there. Here is the crash: [ 3222.385724] [ cut here ] [ 3222.385732] WARNING: CPU: 1 PID: 59852 at kernel/rcu/tree_plugin.h:293 rcu_note_context_switch+0x46/0x460 [ 3222.385733] Modules linked in: binfmt_misc veth nft_masq nft_chain_nat vxlan ip6_udp_tunnel udp_tunnel dummy bridge stp llc ebtable_filter ebtables ip6table_raw ip6table_mangle ip6table_nat ip6table_filter ip6_tables iptable_raw iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_filter bpfilter nf_tables nfnetlink unix_diag ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs pps_ldisc zfs(PO) zunicode(PO) zavl(PO) icp(PO) nls_iso8859_1 zcommon(PO) znvpair(PO) spl(O) dm_multipath zlua(PO) scsi_dh_rdac scsi_dh_emc scsi_dh_alua snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio intel_rapl_msr snd_hda_intel mei_hdcp snd_intel_nhlt snd_hda_codec snd_hda_core snd_hwdep intel_rapl_common x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_pcm kvm snd_timer intel_cstate mei_me intel_rapl_perf mei snd soundcore mac_hid acpi_pad sch_fq_codel ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor [ 3222.385779] async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_pclmul crc32_pclmul ghash_clmulni_intel i915 aesni_intel i2c_algo_bit crypto_simd cryptd glue_helper drm_kms_helper syscopyarea sysfillrect sysimgblt e1000e i2c_i801 fb_sys_fops ahci drm libahci lpc_ich video [ 3222.385795] CPU: 1 PID: 59852 Comm: systemd-resolve Tainted: P O 5.4.0-21-lowlatency #25-Ubuntu [ 3222.385796] Hardware name: /NUC5i5MYBE, BIOS MYBDWi5v.86A.0034.2017.0116.2148 01/16/2017 [ 3222.385801] RIP: 0010:rcu_note_context_switch+0x46/0x460 [ 3222.385803] Code: 54 53 48 c7 c3 80 ba 02 00 65 48 03 1d 8b 57 ce 6d 0f 1f 44 00 00 41 8b 85 80 07 00 00 45 84 f6 0f 85 55 02 00 00 85 c0 7e 0c <0f> 0b 41 80 bd 84 07 00 00 00 74 33 4c 89 ef e8 36 fb ff ff 65 66 [ 3222.385804] RSP: 0018:a7bf48e3bcf8 EFLAGS: 00010002 [ 3222.385806] RAX: 0001 RBX: 9817c5caba80 RCX: 0001 [ 3222.385807] RDX: RSI: 92ce6379 RDI: [ 3222.385808] RBP: a7bf48e3bd20 R08: R09: [ 3222.385808] R10: R11: R12: 9817c5caad00 [ 3222.385809] R13: 9816c39ecd00 R14: R15: 0002ad00 [ 3222.385811] FS: 7f9c0f530940() GS:9817c5c8() knlGS: [ 3222.385812] CS: 0010 DS: ES: CR0: 80050033 [ 3222.385812] CR2: 55988bb4b080 CR3: 0003b5e9a005 CR4: 003606e0 [ 3222.385813] DR0: DR1: DR2: [ 3222.385814] DR3: DR6: fffe0ff0 DR7: 0400 [ 3222.385815] Call Trace: [ 3222.385823] __schedule+0x9d/0x750 [ 3222.385826] ? ___sys_sendmsg+0x95/0xd0 [ 3222.385829] schedule+0x49/0xd0 [ 3222.385831] schedule_hrtimeout_range_clock+0xf9/0x110 [ 3222.385834] ? __seccomp_filter+0x85/0x6b0 [ 3222.385837] schedule_hrtimeout_range+0x13/0x20 [ 3222.385839] ep_poll+0x3c8/0x410 [ 3222.385843] ? wake_up_q+0x70/0x70 [ 3222.385845] do_epoll_wait+0xb8/0xd0 [ 3222.385847] __x64_sys_epoll_wait+0x1e/0x30 [ 3222.385850] do_syscall_64+0x57/0x190 [ 3222.385852] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 3222.385854] RIP: 0033:0x7f9c0f04eb77 [ 3222.385856] Code: 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 8d 05 91 ed 2c 00 41 89 ca 8b 00 85 c0 75 18 b8 e8 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 61 f3 c3 0f 1f 80 00 00 00 00 41 55 41 54 41 [ 3222.385857] RSP: 002b:7ffc6fd86d88 EFLAGS: 0246 ORIG_RAX: 00e8 [ 3222.385859] RAX: ffda RBX: 55988d0ad3c0 RCX:
[Kernel-packages] [Bug 1874605] 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 1874605 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/1874605 Title: focal live usb fails to boot Status in linux package in Ubuntu: Incomplete Bug description: Apr 23 14:36:46 ubuntu kernel: [ cut here ] Apr 23 14:36:46 ubuntu kernel: kernel BUG at fs/ext4/extents_status.c:884! Apr 23 14:36:46 ubuntu kernel: invalid opcode: [#1] SMP PTI Apr 23 14:36:46 ubuntu kernel: CPU: 1 PID: 530 Comm: mount Not tainted 5.4.0-21-generic #25-Ubuntu Apr 23 14:36:46 ubuntu kernel: Hardware name: Micro-Star International Co., Ltd. MS-7B22/B360-A PRO (MS-7B22), BIOS 2.90 12/26/2019 Apr 23 14:36:46 ubuntu kernel: RIP: 0010:ext4_es_cache_extent+0xfd/0x100 Apr 23 14:36:46 ubuntu kernel: Code: 1f 49 8b 06 49 8b 7e 08 49 83 c6 18 48 8d 55 b0 4c 89 ee e8 b5 5d a6 00 49 8b 06 48 85 c0 75 e4 e9 56 ff ff ff e8 b3 64 d0 ff <0f> 0b 90 0f 1f 44 00 00 55 48 89 e5 41 57 49 89 ff 41 56 41 55 49 Apr 23 14:36:46 ubuntu kernel: RSP: 0018:a4cf00737938 EFLAGS: 00010213 Apr 23 14:36:46 ubuntu kernel: RAX: 07ff RBX: 18007da7 RCX: 07ff Apr 23 14:36:46 ubuntu kernel: RDX: 453a3a8e RSI: d2c6431a RDI: 95ac094b4928 Apr 23 14:36:46 ubuntu kernel: RBP: a4cf00737988 R08: 47ff R09: 95ac1b841708 Apr 23 14:36:46 ubuntu kernel: R10: 000301c0 R11: 000d R12: d2c6431a Apr 23 14:36:46 ubuntu kernel: R13: 95ac094b4928 R14: 7911 R15: 95ac0a787740 Apr 23 14:36:46 ubuntu kernel: FS: 7f22f1bff600() GS:95ac1da4() knlGS: Apr 23 14:36:46 ubuntu kernel: CS: 0010 DS: ES: CR0: 80050033 Apr 23 14:36:46 ubuntu kernel: CR2: 7f22f1baa688 CR3: 00044a2b6005 CR4: 003606e0 Apr 23 14:36:46 ubuntu kernel: DR0: DR1: DR2: Apr 23 14:36:46 ubuntu kernel: DR3: DR6: fffe0ff0 DR7: 0400 Apr 23 14:36:46 ubuntu kernel: Call Trace: Apr 23 14:36:46 ubuntu kernel: __read_extent_tree_block+0x18c/0x270 Apr 23 14:36:46 ubuntu kernel: ? __kmalloc+0x266/0x270 Apr 23 14:36:46 ubuntu kernel: ext4_find_extent+0x147/0x300 Apr 23 14:36:46 ubuntu kernel: ext4_ext_map_blocks+0x77/0xea0 Apr 23 14:36:46 ubuntu kernel: ? bit_wait_timeout+0xa0/0xa0 Apr 23 14:36:46 ubuntu kernel: ? io_schedule+0x16/0x40 Apr 23 14:36:46 ubuntu kernel: ? ext4_es_lookup_extent+0xa0/0x210 Apr 23 14:36:46 ubuntu kernel: ext4_map_blocks+0x34c/0x600 Apr 23 14:36:46 ubuntu kernel: ? var_wake_function+0x30/0x30 Apr 23 14:36:46 ubuntu kernel: _ext4_get_block+0x95/0x110 Apr 23 14:36:46 ubuntu kernel: ? ext4_data_block_valid+0x21/0x30 Apr 23 14:36:46 ubuntu kernel: ext4_get_block+0x16/0x20 Apr 23 14:36:46 ubuntu kernel: generic_block_bmap+0x4f/0x70 Apr 23 14:36:46 ubuntu kernel: ext4_bmap+0x77/0xf0 Apr 23 14:36:46 ubuntu kernel: bmap+0x1f/0x30 Apr 23 14:36:46 ubuntu kernel: jbd2_journal_init_inode+0x18/0xb0 Apr 23 14:36:46 ubuntu kernel: ext4_load_journal+0x121/0x460 Apr 23 14:36:46 ubuntu kernel: ext4_fill_super+0x1f7d/0x2ef0 Apr 23 14:36:46 ubuntu kernel: ? pointer+0x2fe/0x350 Apr 23 14:36:46 ubuntu kernel: ? vsnprintf+0x1ec/0x4e0 Apr 23 14:36:46 ubuntu kernel: mount_bdev+0x17f/0x1b0 Apr 23 14:36:46 ubuntu kernel: ? ext4_calculate_overhead+0x4a0/0x4a0 Apr 23 14:36:46 ubuntu kernel: ? mount_bdev+0x17f/0x1b0 Apr 23 14:36:46 ubuntu kernel: ? ext4_calculate_overhead+0x4a0/0x4a0 Apr 23 14:36:46 ubuntu kernel: ext4_mount+0x15/0x20 Apr 23 14:36:46 ubuntu kernel: legacy_get_tree+0x2b/0x50 Apr 23 14:36:46 ubuntu kernel: vfs_get_tree+0x2a/0xc0 Apr 23 14:36:46 ubuntu kernel: ? capable+0x19/0x20 Apr 23 14:36:46 ubuntu kernel: do_mount+0x7b6/0x9c0 Apr 23 14:36:46 ubuntu kernel: ksys_mount+0x82/0xd0 Apr 23 14:36:46 ubuntu kernel: __x64_sys_mount+0x25/0x30 Apr 23 14:36:46 ubuntu kernel: do_syscall_64+0x57/0x190 Apr 23 14:36:46 ubuntu kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 Apr 23 14:36:46 ubuntu kernel: RIP: 0033:0x7f22f1b2ec9e Apr 23 14:36:46 ubuntu kernel: Code: 48 8b 0d f5 81 0c 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 49 89 ca b8 a5 00 00
[Kernel-packages] [Bug 1808957] Re: Dell XPS 13 (9370) defaults to s2idle sleep/suspend instead of deep, NVMe drains lots of power under s2idle
XPS 9370 at my hand consumes 0.6W during s2idle. It's pretty much on par with S3. -- 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/1808957 Title: Dell XPS 13 (9370) defaults to s2idle sleep/suspend instead of deep, NVMe drains lots of power under s2idle Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-oem source package in Bionic: Fix Released Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Committed Status in linux-oem source package in Cosmic: Invalid Status in linux-oem-osp1 source package in Cosmic: Invalid Status in linux source package in Disco: Fix Released Status in linux-oem source package in Disco: Fix Released Status in linux-oem-osp1 source package in Disco: Fix Released Bug description: It seems that the Dell 9370 is set to go into s2idle mode rather than deep sleep, forgoing significant power savings. I have confirmed this by suspending and then checking: sudo journalctl | grep "PM: suspend" | tail -2. If the output is PM: suspend entry (s2idle) PM: suspend exit cat /sys/power/mem_sleep showed [s2idle] deep As a temporary fix, I typed echo deep > /sys/power/mem_sleep as a root user (sudo -i). Then the output of cat /sys/power/mem_sleep was s2idle [deep] After suspending now, sudo journalctl | grep "PM: suspend" | tail -2 returns PM: suspend entry (deep) PM: suspend exit I have made this permanent by editing /etc/default/grub and replacing GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" with GRUB_CMDLINE_LINUX_DEFAULT="quiet splash mem_sleep_default=deep" then regenerating my grub configuration (sudo grub-mkconfig -o /boot/grub/grub.cfg). This appears to be working with no ill effects. Credit to https://askubuntu.com/a/1036122/470077 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-11-generic 4.18.0-11.12 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aaron-work 3672 F pulseaudio /dev/snd/pcmC0D0p: aaron-work 3672 F...m pulseaudio Date: Tue Dec 18 09:52:44 2018 EcryptfsInUse: Yes HibernationDevice: RESUME=/dev/ubuntu-vg/swap_1 InstallationDate: Installed on 2018-09-04 (104 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-11-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.175.1 SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-10-26 (52 days ago) dmi.bios.date: 08/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/09/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808957/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861610] Re: 'Elan touchpad' not detected on 'Lenovo ThinkBook 15 IIL'
I've encountered the same issue on a Thinkbook 14-iil running kububuntu
20.04. ELAN0634 is the culprit for me as well. I haven't quite figured
out how to apply the kernel patch where one adds { "ELAN064", 0} to
elan-ic2-ids.h to my system. I can confirm that the fixes for the
thinkbook 15iil do not work for the thinkbook 14iil -- i tried.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1861610
Title:
'Elan touchpad' not detected on 'Lenovo ThinkBook 15 IIL'
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Bionic:
New
Status in linux source package in Eoan:
New
Status in linux source package in Focal:
Confirmed
Bug description:
The Elan touchpad on my Lenovo Thinkbook isn't being detected, and
hence isn't working.
`sudo acpidump | grep -C3 ELAN` gives me the device's ACPI id:
```bash
ghosthawkzero@EchelonV:~$ sudo acpidump | grep -C3 ELAN
2A060: 49 4E 54 31 70 0A 20 49 44 41 44 A4 84 53 42 46 INT1p. IDAD..SBF
2A070: 53 53 42 46 49 00 5B 82 42 0E 54 50 44 32 08 5F SSBFI.[.B.TPD2._
2A080: 41 44 52 00 08 49 44 41 44 00 08 48 49 44 32 00 ADR..IDAD..HID2.
2A090: 08 5F 48 49 44 0D 45 4C 41 4E 30 36 33 34 00 08 ._HID.ELAN0634..
2A0A0: 5F 43 49 44 0D 50 4E 50 30 43 35 30 00 08 5F 55 _CID.PNP0C50.._U
2A0B0: 49 44 01 14 4B 04 5F 44 53 4D 04 A0 3C 93 68 11 ID..K._DSM..<.h.
2A0C0: 13 0A 10 F7 F6 DF 3C 67 42 55 45 AD 05 B3 0A 3D ..https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861610/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874605] Re: focal live usb fails to boot
** Package changed: syslinux (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874605 Title: focal live usb fails to boot Status in linux package in Ubuntu: New Bug description: Apr 23 14:36:46 ubuntu kernel: [ cut here ] Apr 23 14:36:46 ubuntu kernel: kernel BUG at fs/ext4/extents_status.c:884! Apr 23 14:36:46 ubuntu kernel: invalid opcode: [#1] SMP PTI Apr 23 14:36:46 ubuntu kernel: CPU: 1 PID: 530 Comm: mount Not tainted 5.4.0-21-generic #25-Ubuntu Apr 23 14:36:46 ubuntu kernel: Hardware name: Micro-Star International Co., Ltd. MS-7B22/B360-A PRO (MS-7B22), BIOS 2.90 12/26/2019 Apr 23 14:36:46 ubuntu kernel: RIP: 0010:ext4_es_cache_extent+0xfd/0x100 Apr 23 14:36:46 ubuntu kernel: Code: 1f 49 8b 06 49 8b 7e 08 49 83 c6 18 48 8d 55 b0 4c 89 ee e8 b5 5d a6 00 49 8b 06 48 85 c0 75 e4 e9 56 ff ff ff e8 b3 64 d0 ff <0f> 0b 90 0f 1f 44 00 00 55 48 89 e5 41 57 49 89 ff 41 56 41 55 49 Apr 23 14:36:46 ubuntu kernel: RSP: 0018:a4cf00737938 EFLAGS: 00010213 Apr 23 14:36:46 ubuntu kernel: RAX: 07ff RBX: 18007da7 RCX: 07ff Apr 23 14:36:46 ubuntu kernel: RDX: 453a3a8e RSI: d2c6431a RDI: 95ac094b4928 Apr 23 14:36:46 ubuntu kernel: RBP: a4cf00737988 R08: 47ff R09: 95ac1b841708 Apr 23 14:36:46 ubuntu kernel: R10: 000301c0 R11: 000d R12: d2c6431a Apr 23 14:36:46 ubuntu kernel: R13: 95ac094b4928 R14: 7911 R15: 95ac0a787740 Apr 23 14:36:46 ubuntu kernel: FS: 7f22f1bff600() GS:95ac1da4() knlGS: Apr 23 14:36:46 ubuntu kernel: CS: 0010 DS: ES: CR0: 80050033 Apr 23 14:36:46 ubuntu kernel: CR2: 7f22f1baa688 CR3: 00044a2b6005 CR4: 003606e0 Apr 23 14:36:46 ubuntu kernel: DR0: DR1: DR2: Apr 23 14:36:46 ubuntu kernel: DR3: DR6: fffe0ff0 DR7: 0400 Apr 23 14:36:46 ubuntu kernel: Call Trace: Apr 23 14:36:46 ubuntu kernel: __read_extent_tree_block+0x18c/0x270 Apr 23 14:36:46 ubuntu kernel: ? __kmalloc+0x266/0x270 Apr 23 14:36:46 ubuntu kernel: ext4_find_extent+0x147/0x300 Apr 23 14:36:46 ubuntu kernel: ext4_ext_map_blocks+0x77/0xea0 Apr 23 14:36:46 ubuntu kernel: ? bit_wait_timeout+0xa0/0xa0 Apr 23 14:36:46 ubuntu kernel: ? io_schedule+0x16/0x40 Apr 23 14:36:46 ubuntu kernel: ? ext4_es_lookup_extent+0xa0/0x210 Apr 23 14:36:46 ubuntu kernel: ext4_map_blocks+0x34c/0x600 Apr 23 14:36:46 ubuntu kernel: ? var_wake_function+0x30/0x30 Apr 23 14:36:46 ubuntu kernel: _ext4_get_block+0x95/0x110 Apr 23 14:36:46 ubuntu kernel: ? ext4_data_block_valid+0x21/0x30 Apr 23 14:36:46 ubuntu kernel: ext4_get_block+0x16/0x20 Apr 23 14:36:46 ubuntu kernel: generic_block_bmap+0x4f/0x70 Apr 23 14:36:46 ubuntu kernel: ext4_bmap+0x77/0xf0 Apr 23 14:36:46 ubuntu kernel: bmap+0x1f/0x30 Apr 23 14:36:46 ubuntu kernel: jbd2_journal_init_inode+0x18/0xb0 Apr 23 14:36:46 ubuntu kernel: ext4_load_journal+0x121/0x460 Apr 23 14:36:46 ubuntu kernel: ext4_fill_super+0x1f7d/0x2ef0 Apr 23 14:36:46 ubuntu kernel: ? pointer+0x2fe/0x350 Apr 23 14:36:46 ubuntu kernel: ? vsnprintf+0x1ec/0x4e0 Apr 23 14:36:46 ubuntu kernel: mount_bdev+0x17f/0x1b0 Apr 23 14:36:46 ubuntu kernel: ? ext4_calculate_overhead+0x4a0/0x4a0 Apr 23 14:36:46 ubuntu kernel: ? mount_bdev+0x17f/0x1b0 Apr 23 14:36:46 ubuntu kernel: ? ext4_calculate_overhead+0x4a0/0x4a0 Apr 23 14:36:46 ubuntu kernel: ext4_mount+0x15/0x20 Apr 23 14:36:46 ubuntu kernel: legacy_get_tree+0x2b/0x50 Apr 23 14:36:46 ubuntu kernel: vfs_get_tree+0x2a/0xc0 Apr 23 14:36:46 ubuntu kernel: ? capable+0x19/0x20 Apr 23 14:36:46 ubuntu kernel: do_mount+0x7b6/0x9c0 Apr 23 14:36:46 ubuntu kernel: ksys_mount+0x82/0xd0 Apr 23 14:36:46 ubuntu kernel: __x64_sys_mount+0x25/0x30 Apr 23 14:36:46 ubuntu kernel: do_syscall_64+0x57/0x190 Apr 23 14:36:46 ubuntu kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 Apr 23 14:36:46 ubuntu kernel: RIP: 0033:0x7f22f1b2ec9e Apr 23 14:36:46 ubuntu kernel: Code: 48 8b 0d f5 81 0c 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d c2 81 0c 00 f7 d8 64 89 01 48 Apr 23 14:36:46 ubuntu kernel: RSP: 002b:7ffeed62afb8 EFLAGS: 0202 ORIG_RAX: 00a5 Apr 23 14:36:46 ubuntu kernel: RAX: ffda RBX: 8401 RCX: 7f22f1b2ec9e Apr 23 14:36:46 ubuntu kernel: RDX: 7ffeed62cdcd RSI: 7ffeed62cde9 RDI: 7ffeed62cde0 Apr 23 14:36:46 ubuntu kernel: RBP: R08: R09: 007f Apr 23 14:36:46 ubuntu kernel: R10: 8401 R11:
[Kernel-packages] [Bug 1748105] Re: port80 test in ubuntu_kvm_unit_tests failed with timeout
It needs about 90 second to run on Azure Standard_D48_v3 $ time sudo ./tests/port80 BUILD_HEAD=5c052c90 timeout -k 1s --foreground 180 /usr/bin/qemu-system-x86_64 --no-reboot -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.cKEDR6Z0v0 -smp 1 # -initrd /tmp/tmp.o2ZRnk8tmj qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.8001H:ECX.svm [bit 2] enabling apic begining port 0x80 write test done PASS port80 real1m20.377s user0m42.160s sys 0m38.299s -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1748105 Title: port80 test in ubuntu_kvm_unit_tests failed with timeout Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Incomplete Status in linux-azure package in Ubuntu: Confirmed Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux-kvm package in Ubuntu: Confirmed Status in linux-oracle-5.0 package in Ubuntu: Confirmed Bug description: With Joshua's comment in bug 1719524: "Nested KVM can only be tried on instance sizes with nested Hypervisor support: Ev3 and Dv3.", although the instance name is E4v3 here but I can start a KVM on it. Test port80 test will timeout on it. Steps: 1. git clone --depth=1 https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git 2. cd kvm-unit-tests; ./configure; make 3. Run the port80 test as root: # TESTNAME=port80 TIMEOUT=90s ACCEL= ./x86/run x86/port80.flat -smp 1 timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel x86/port80.flat -smp 1 # -initrd /tmp/tmp.3p9PWc2SRi enabling apic begining port 0x80 write test qemu-system-x86_64: terminating on signal 15 from pid 7790 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.14.0-1004-azure-edge 4.14.0-1004.4 ProcVersionSignature: User Name 4.14.0-1004.4-username-edge 4.14.14 Uname: Linux 4.14.0-1004-azure-edge x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Thu Feb 8 06:13:18 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-azure-edge UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1748105/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874605] [NEW] focal live usb fails to boot
You have been subscribed to a public bug: Apr 23 14:36:46 ubuntu kernel: [ cut here ] Apr 23 14:36:46 ubuntu kernel: kernel BUG at fs/ext4/extents_status.c:884! Apr 23 14:36:46 ubuntu kernel: invalid opcode: [#1] SMP PTI Apr 23 14:36:46 ubuntu kernel: CPU: 1 PID: 530 Comm: mount Not tainted 5.4.0-21-generic #25-Ubuntu Apr 23 14:36:46 ubuntu kernel: Hardware name: Micro-Star International Co., Ltd. MS-7B22/B360-A PRO (MS-7B22), BIOS 2.90 12/26/2019 Apr 23 14:36:46 ubuntu kernel: RIP: 0010:ext4_es_cache_extent+0xfd/0x100 Apr 23 14:36:46 ubuntu kernel: Code: 1f 49 8b 06 49 8b 7e 08 49 83 c6 18 48 8d 55 b0 4c 89 ee e8 b5 5d a6 00 49 8b 06 48 85 c0 75 e4 e9 56 ff ff ff e8 b3 64 d0 ff <0f> 0b 90 0f 1f 44 00 00 55 48 89 e5 41 57 49 89 ff 41 56 41 55 49 Apr 23 14:36:46 ubuntu kernel: RSP: 0018:a4cf00737938 EFLAGS: 00010213 Apr 23 14:36:46 ubuntu kernel: RAX: 07ff RBX: 18007da7 RCX: 07ff Apr 23 14:36:46 ubuntu kernel: RDX: 453a3a8e RSI: d2c6431a RDI: 95ac094b4928 Apr 23 14:36:46 ubuntu kernel: RBP: a4cf00737988 R08: 47ff R09: 95ac1b841708 Apr 23 14:36:46 ubuntu kernel: R10: 000301c0 R11: 000d R12: d2c6431a Apr 23 14:36:46 ubuntu kernel: R13: 95ac094b4928 R14: 7911 R15: 95ac0a787740 Apr 23 14:36:46 ubuntu kernel: FS: 7f22f1bff600() GS:95ac1da4() knlGS: Apr 23 14:36:46 ubuntu kernel: CS: 0010 DS: ES: CR0: 80050033 Apr 23 14:36:46 ubuntu kernel: CR2: 7f22f1baa688 CR3: 00044a2b6005 CR4: 003606e0 Apr 23 14:36:46 ubuntu kernel: DR0: DR1: DR2: Apr 23 14:36:46 ubuntu kernel: DR3: DR6: fffe0ff0 DR7: 0400 Apr 23 14:36:46 ubuntu kernel: Call Trace: Apr 23 14:36:46 ubuntu kernel: __read_extent_tree_block+0x18c/0x270 Apr 23 14:36:46 ubuntu kernel: ? __kmalloc+0x266/0x270 Apr 23 14:36:46 ubuntu kernel: ext4_find_extent+0x147/0x300 Apr 23 14:36:46 ubuntu kernel: ext4_ext_map_blocks+0x77/0xea0 Apr 23 14:36:46 ubuntu kernel: ? bit_wait_timeout+0xa0/0xa0 Apr 23 14:36:46 ubuntu kernel: ? io_schedule+0x16/0x40 Apr 23 14:36:46 ubuntu kernel: ? ext4_es_lookup_extent+0xa0/0x210 Apr 23 14:36:46 ubuntu kernel: ext4_map_blocks+0x34c/0x600 Apr 23 14:36:46 ubuntu kernel: ? var_wake_function+0x30/0x30 Apr 23 14:36:46 ubuntu kernel: _ext4_get_block+0x95/0x110 Apr 23 14:36:46 ubuntu kernel: ? ext4_data_block_valid+0x21/0x30 Apr 23 14:36:46 ubuntu kernel: ext4_get_block+0x16/0x20 Apr 23 14:36:46 ubuntu kernel: generic_block_bmap+0x4f/0x70 Apr 23 14:36:46 ubuntu kernel: ext4_bmap+0x77/0xf0 Apr 23 14:36:46 ubuntu kernel: bmap+0x1f/0x30 Apr 23 14:36:46 ubuntu kernel: jbd2_journal_init_inode+0x18/0xb0 Apr 23 14:36:46 ubuntu kernel: ext4_load_journal+0x121/0x460 Apr 23 14:36:46 ubuntu kernel: ext4_fill_super+0x1f7d/0x2ef0 Apr 23 14:36:46 ubuntu kernel: ? pointer+0x2fe/0x350 Apr 23 14:36:46 ubuntu kernel: ? vsnprintf+0x1ec/0x4e0 Apr 23 14:36:46 ubuntu kernel: mount_bdev+0x17f/0x1b0 Apr 23 14:36:46 ubuntu kernel: ? ext4_calculate_overhead+0x4a0/0x4a0 Apr 23 14:36:46 ubuntu kernel: ? mount_bdev+0x17f/0x1b0 Apr 23 14:36:46 ubuntu kernel: ? ext4_calculate_overhead+0x4a0/0x4a0 Apr 23 14:36:46 ubuntu kernel: ext4_mount+0x15/0x20 Apr 23 14:36:46 ubuntu kernel: legacy_get_tree+0x2b/0x50 Apr 23 14:36:46 ubuntu kernel: vfs_get_tree+0x2a/0xc0 Apr 23 14:36:46 ubuntu kernel: ? capable+0x19/0x20 Apr 23 14:36:46 ubuntu kernel: do_mount+0x7b6/0x9c0 Apr 23 14:36:46 ubuntu kernel: ksys_mount+0x82/0xd0 Apr 23 14:36:46 ubuntu kernel: __x64_sys_mount+0x25/0x30 Apr 23 14:36:46 ubuntu kernel: do_syscall_64+0x57/0x190 Apr 23 14:36:46 ubuntu kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 Apr 23 14:36:46 ubuntu kernel: RIP: 0033:0x7f22f1b2ec9e Apr 23 14:36:46 ubuntu kernel: Code: 48 8b 0d f5 81 0c 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d c2 81 0c 00 f7 d8 64 89 01 48 Apr 23 14:36:46 ubuntu kernel: RSP: 002b:7ffeed62afb8 EFLAGS: 0202 ORIG_RAX: 00a5 Apr 23 14:36:46 ubuntu kernel: RAX: ffda RBX: 8401 RCX: 7f22f1b2ec9e Apr 23 14:36:46 ubuntu kernel: RDX: 7ffeed62cdcd RSI: 7ffeed62cde9 RDI: 7ffeed62cde0 Apr 23 14:36:46 ubuntu kernel: RBP: R08: R09: 007f Apr 23 14:36:46 ubuntu kernel: R10: 8401 R11: 0202 R12: 7f22f1bff580 Apr 23 14:36:46 ubuntu kernel: R13: R14: 7ffeed62b228 R15: Apr 23 14:36:46 ubuntu kernel: Modules linked in: nls_iso8859_1 dm_mirror dm_region_hash dm_log hid_generic usbhid hid uas usb_storage crct10dif_pclmul crc32_pclmul ghash_clmulni_intel i915 mxm_wmi i2c_algo_bit aesni_intel crypto_simd cryptd drm_kms_helper glue_helper
[Kernel-packages] [Bug 1788321] Re: swapon failed: invalid argument
Just did a fresh install of 20.04 as a Proxmox VM and see this "invalid argument" in the start up messages and syslog. Trying to start it manually also fails. Tried recreating it, also failed. root@changeme:/# fallocate -l 2G /swap.img root@changeme:/# chmod 600 /swap.img root@changeme:/# ls -lah /swap.img -rw--- 1 root root 2.0G Apr 24 04:07 /swap.img root@changeme:/# mkswap /swap.img mkswap: /swap.img: warning: wiping old swap signature. Setting up swapspace version 1, size = 2 GiB (2147479552 bytes) no label, UUID=bd9bdc4f-4c53-4b0b-ad92-687ed5f669e6 root@changeme:/# swapon /swap.img swapon: /swap.img: swapon failed: Invalid argument root@changeme:/# swapon -v /swap.img swapon: /swap.img: found signature [pagesize=4096, signature=swap] swapon: /swap.img: pagesize=4096, swapsize=2147483648, devsize=2147483648 swapon /swap.img swapon: /swap.img: swapon failed: Invalid argument -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1788321 Title: swapon failed: invalid argument Status in linux package in Ubuntu: Confirmed Status in util-linux package in Ubuntu: Invalid Bug description: Environment: - Ubuntu 18.04.1 LTS - Linux 4.15.0-32-generic i686 Description: When I try to mount my swap partition or my swap file, I get "swapon failed: invalid argument" . Steps to reproduce: 1) sudo bash 2) dd if=/dev/zero of=/swapfile bs=1024 count=524288 3) mkswap /swapfile 4) chown root:root /swapfile 5) chmod 0600 /swapfile 6) swapon /swapfile Last execution returns "swapon failed: invalid argument" . I'm almost sure it's a bug because I have no problems using Linux 4.15.0-29-generic instead of Linux 4.15.0-32-generic. Also, no problems using Ubuntu 18.04.1 LTS Live CD. Regards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788321/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1866681] Re: [HP Pavilion dv9000] Mute toggles on/off while plugged into the headphone/speaker jack (19.04+)
I've just tried installing 20.04 LTS, and the audio issue still persists. I've tried reinstalling both pulseaudio and ALSA, and nothing works. I'm out of ideas. What do I do? How should I go about fixing the problem? On Tue, Mar 17, 2020 at 11:04 AM Kuroš Taheri-Golværzi wrote: > > Alrighty, so, I installed Xubuntu 16.04. `uname -or` outputs: > 4.4.0-21-generic GNU/Linux > and `pulseaudio --version` outputs: > pulseaudio 8.0 > In AlsaMixer, "Auto-Mute Mode" is set to "Enabled", and the audio > works perfectly exactly as expected. > > This is definitely something that started happening in the 19.04 versions. > > On 3/12/20, Kai-Heng Feng wrote: > > Can you please test older kernels like 4.15? > > > > -- > > You received this bug notification because you are subscribed to the bug > > report. > > https://bugs.launchpad.net/bugs/1866681 > > > > Title: > > [HP Pavilion dv9000] Mute toggles on/off while plugged into the > > headphone/speaker jack (19.04+) > > > > Status in alsa-driver package in Ubuntu: > > New > > Status in linux package in Ubuntu: > > Confirmed > > Status in pulseaudio package in Ubuntu: > > New > > > > Bug description: > > I'm on an HP Pavilion dv9000 (https://www.cnet.com/products/hp- > > pavilion-dv9000/specs/) built many years ago. > > > > > > Whenever I'm using any distro that's based on Ubuntu which was published > > from Version 19.04 onwards, I've been having a major issue with the mute > > button toggling on and off whenever I have something plugged into the audio > > out jack. I know that it's not the fault of XFCE, because I also use the > > latest version of Manjaro with XFCE on this same computer, and it works > > fine. I also know it's not any Red Hat-based distro, because I use Stella > > (which is a remix of CentOS 6) also on this exact same computer, and it also > > works fine. Qubes, Mageia, and Fedora 31 also work perfectly fine and don't > > have this issue. > > > > My "lsb-release" is: > > DISTRIB_ID=Ubuntu > > DISTRIB_RELEASE=19.10 > > DISTRIB_CODENAME=eoan > > DISTRIB_DESCRIPTION="Ubuntu 19.10" > > > > and "apt-cache policy pulseaudio" outputs: > > pulseaudio: > > Installed: 1:13.0-1ubuntu1.1 > > Candidate: 1:13.0-1ubuntu1.1 > > Version table: > >*** 1:13.0-1ubuntu1.1 500 > > 500 http://us.archive.ubuntu.com/ubuntu eoan-updates/main amd64 > > Packages > > 100 /var/lib/dpkg/status > >1:13.0-1ubuntu1 500 > > 500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages > > > > I've uploaded a short video of the problem that I recorded with my phone > > here: > > https://www.youtube.com/watch?v=GXaHXQA-5uQ > > > > > > The problem appears with Kali 2019 and 2020, Peppermint 19.04, Lubuntu > > 19.04, Xubuntu 19.04, and Sparky 5.10 and 2020.02. > > > > > > I've checked pretty much everything I can think of. There's a log for my > > ALSA help diagnostics results on my current computer (which works properly > > with 18.04) at: > > http://alsa-project.org/db/?f=4859b85cd7fc32e7f01f8df63591b5a43dbf6829 > > > > > > the result output of lspci is: > > [code]00:00.0 RAM memory: NVIDIA Corporation C51 Host Bridge (rev a2) > > 00:00.1 RAM memory: NVIDIA Corporation C51 Memory Controller 0 (rev a2) > > 00:00.2 RAM memory: NVIDIA Corporation C51 Memory Controller 1 (rev a2) > > 00:00.3 RAM memory: NVIDIA Corporation C51 Memory Controller 5 (rev a2) > > 00:00.4 RAM memory: NVIDIA Corporation C51 Memory Controller 4 (rev a2) > > 00:00.5 RAM memory: NVIDIA Corporation C51 Host Bridge (rev a2) > > 00:00.6 RAM memory: NVIDIA Corporation C51 Memory Controller 3 (rev a2) > > 00:00.7 RAM memory: NVIDIA Corporation C51 Memory Controller 2 (rev a2) > > 00:02.0 PCI bridge: NVIDIA Corporation C51 PCI Express Bridge (rev a1) > > 00:03.0 PCI bridge: NVIDIA Corporation C51 PCI Express Bridge (rev a1) > > 00:04.0 PCI bridge: NVIDIA Corporation C51 PCI Express Bridge (rev a1) > > 00:09.0 RAM memory: NVIDIA Corporation MCP51 Host Bridge (rev a2) > > 00:0a.0 ISA bridge: NVIDIA Corporation MCP51 LPC Bridge (rev a3) > > 00:0a.1 SMBus: NVIDIA Corporation MCP51 SMBus (rev a3) > > 00:0a.3 Co-processor: NVIDIA Corporation MCP51 PMU (rev a3) > > 00:0b.0 USB controller: NVIDIA Corporation MCP51 USB Controller (rev a3) > > 00:0b.1 USB controller: NVIDIA Corporation MCP51 USB Controller (rev a3) > > 00:0d.0 IDE interface: NVIDIA Corporation MCP51 IDE (rev f1) > > 00:0e.0 IDE interface: NVIDIA Corporation MCP51 Serial ATA Controller (rev > > f1) > > 00:0f.0 IDE interface: NVIDIA Corporation MCP51 Serial ATA Controller (rev > > f1) > > 00:10.0 PCI bridge: NVIDIA Corporation MCP51 PCI Bridge (rev a2) > > 00:10.1 Audio device: NVIDIA Corporation MCP51 High Definition Audio (rev > > a2) > > 00:14.0 Bridge: NVIDIA Corporation MCP51 Ethernet Controller (rev a3) > > 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 > > [Athlon64/Opteron] HyperTransport Technology
[Kernel-packages] [Bug 1872001] Re: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0
The test kernel 5.3.0-48.41+lp1861395v1 seems to be a major improvement! On 5.3.0-45.37 pauses still happened rarely i.e. a single 2 second pause every 15 hrs and I hadn't noticed them until I was watching the logs for them. 5.3.0-46 and later were pausing several times a minute and the system was unusable. This test kernel 5.3.0-48.41+lp1861395v1 has yet to pause at all. I will keep testing it but I suspect we have a winner 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/1872001 Title: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0 Status in linux package in Ubuntu: Confirmed Status in linux source package in Eoan: In Progress Bug description: Hi, Since update to HWE kernel 5.3.0-46-generic I am experiencing frequent (every couple of minutes) GPU hangs and reset manifesting as 2-3 seconds freezes of the GUI (other than the mouse pointer). No particular triggers identified although have Chrome / Chromium running with Hardware Acceleration enabled does appear to increase the frequency. I have seen incidences of these hangs in jounralctl output using previous kernels in the 5.3.0-xx series but they were very infrequent (one or twice in a week of daily usage) System Info steve@steve-Inspiron-5580:~$ inxi -SCGxxxz System:Host: steve-Inspiron-5580 Kernel: 5.3.0-46-generic x86_64 bits: 64 compiler: gcc v: 7.5.0 Desktop: Cinnamon 4.4.8 wm: muffin 4.4.2 dm: LightDM 1.26.0 Distro: Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic CPU: Topology: Quad Core model: Intel Core i5-8265U bits: 64 type: MT MCP arch: Kaby Lake rev: B L2 cache: 6144 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 28800 Speed: 1173 MHz min/max: 400/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 Graphics: Device-1: Intel vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:3ea0 Display: x11 server: X.Org 1.20.5 driver: modesetting unloaded: fbdev,vesa resolution: 1920x1080~60Hz OpenGL: renderer: Mesa DRI Intel UHD Graphics (Whiskey Lake 3x8 GT2) v: 4.5 Mesa 19.2.8 compat-v: 3.0 direct render: Yes steve@steve-Inspiron-5580:~$ journalctl -b | grep i915 Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: vgaarb: deactivate vga console Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem Apr 10 06:15:17 steve-Inspiron-5580 kernel: [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4) Apr 10 06:15:17 steve-Inspiron-5580 kernel: [drm] Initialized i915 1.6.0 20190619 for :00:02.0 on minor 0 Apr 10 06:15:17 steve-Inspiron-5580 kernel: fbcon: i915drmfb (fb0) is primary device Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: fb0: i915drmfb frame buffer device Apr 10 06:15:17 steve-Inspiron-5580 kernel: snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) Apr 10 06:16:28 steve-Inspiron-5580 kernel: i915 :00:02.0: GPU HANG: ecode 9:0:0x, hang on rcs0 Apr 10 06:16:28 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:31:46 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:37:48 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:40:46 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 I note another user has reported similar issues on the same kernel at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861395/comments/52 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: steve 3920 F pulseaudio /dev/snd/pcmC0D0p: steve 3920 F...m pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.3 HibernationDevice: RESUME=none InstallationDate: Installed on 2019-12-27 (104 days ago) InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213 MachineType: Dell Inc. Inspiron 5580 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic root=UUID=b0eaa5bb-0276-42d4-938f-ee6ce1627906 ro usb_storage.quirks=0bc2:2320: quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-46-generic N/A linux-backports-modules-5.3.0-46-generic N/A linux-firmware1.173.17 Tags: tricia Uname: Linux 5.3.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install)
[Kernel-packages] [Bug 1869672] Re: kdump kernel can't be loaded using kernel 4.15.0-76
Excellent! Of course I'll try your kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1869672 Title: kdump kernel can't be loaded using kernel 4.15.0-76 Status in makedumpfile package in Ubuntu: In Progress Status in makedumpfile source package in Bionic: In Progress Bug description: Thank you for reading this report. This may caused by bugs in kernel, not in kdump. If so, I will report this to kernel team. I need your comment to solve this. [Impact] * Kdump kernel can't be loaded using linux kernel 4.15.0-76. [Environment] Description:Ubuntu 18.04.4 LTS Release:18.04 uname: Linux ubuntu 4.15.0-76-generic #86-Ubuntu SMP Fri Jan 17 17:24:28 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Secure boot is enabled. Versions: * kexec-tools/bionic-updates,now 1:2.0.16-1ubuntu1.1 * kdump-tools/bionic-updates,now 1:1.6.5-1ubuntu1~18.04.4 [Test case] 1)After OS booted, run systemctl status kdump-tools shows these messages below: ● kdump-tools.service - Kernel crash dump capture service Loaded: loaded (/lib/systemd/system/kdump-tools.service; enabled; vendor preset: enabled) Active: active (exited) since Fri 2020-03-27 16:40:31 JST; 5min ago Process: 895 ExecStart=/etc/init.d/kdump-tools start (code=exited, status=0/SUCCESS) Main PID: 895 (code=exited, status=0/SUCCESS) Mar 27 16:40:31 ubuntu systemd[1]: Starting Kernel crash dump capture service... Mar 27 16:40:31 ubuntu kdump-tools[895]: Starting kdump-tools: * Creating symlink /var/lib/kdump/vmlinuz Mar 27 16:40:31 ubuntu kdump-tools[895]: * Creating symlink /var/lib/kdump/initrd.img Mar 27 16:40:31 ubuntu kdump-tools[895]: kexec_file_load failed: Exec format error Mar 27 16:40:31 ubuntu kdump-tools[895]: * failed to load kdump kernel Mar 27 16:40:31 ubuntu systemd[1]: Started Kernel crash dump capture service. 2)Run kexec directly: $ sudo /sbin/kexec -p --command-line="/boot/vmlinuz-4.15.0-76-generic root=UUID=29a89ad8-8923-435e-a88c-aaf5cb379568 ro mce=ignore_ce reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1 irqpoll nousb ata_piix.prefer_ms_hyperv=0" --initrd=/boot/initrd.img-4.15.0-76-generic /boot/vmlinuz-4.15.0-64-generic Then,these messages are shown: Cannot open /proc/kcore: Operation not permitted Cannot read /proc/kcore: Operation not permitted Cannot load /boot/vmlinuz-4.15.0-76-generic On dmesg, these messages are shown: [ 538.524718] Lockdown: /proc/kcore is restricted; see man kernel_lockdown.7 3) Changing OS kernel to older one(I used 4.15.0-64), kdump kernel can be loaded. $ sudo systemctl status kdump-tools ● kdump-tools.service - Kernel crash dump capture service Loaded: loaded (/lib/systemd/system/kdump-tools.service; enabled; vendor preset: enabled) Active: active (exited) since Wed 2020-03-25 13:39:03 JST; 5 days ago Main PID: 832 (code=exited, status=0/SUCCESS) Tasks: 0 (limit: 4915) CGroup: /system.slice/kdump-tools.service Mar 25 13:39:02 ubuntu systemd[1]: Starting Kernel crash dump capture service... Mar 25 13:39:02 ubuntu kdump-tools[832]: Starting kdump-tools: * Creating symlink /var/lib/kdump/vmlinuz Mar 25 13:39:02 ubuntu kdump-tools[832]: * Creating symlink /var/lib/kdump/initrd.img Mar 25 13:39:03 ubuntu kdump-tools[832]: * loaded kdump kernel Mar 25 13:39:03 ubuntu kdump-tools[938]: loaded kdump kernel Mar 25 13:39:03 ubuntu systemd[1]: Started Kernel crash dump capture service. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1869672/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
As per my earlier comment, I have a GTX 1080. I'm happy to provide any log information if @Alberto can tell me what he needs to help him figure out what's going on. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Invalid Status in gdm3 source package in Eoan: Confirmed Status in gnome-session source package in Eoan: Confirmed Status in nvidia-graphics-drivers-435 source package in Eoan: Confirmed Bug description: I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A67 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1874588] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874588 Title: Flickering screen after waking up from Suspend Status in linux package in Ubuntu: Confirmed Bug description: Just did a fresh install of Ubuntu 20.04 LTS and everything was fine, display worked perfect. Then I put the machine in Suspend mode (by clicking on GUI button), left for 5 minutes, came back, woke up the machine (by clicking a key on the keyboard), and upon waking up, the display started flickering heavily. Relevant Specs (Sorry if I missed anything): AMD® Ryzen 9 3900x 12-core processor × 24 AMD® Radeon rx 5700 xt GNOME version 3.36.1 Windowing System X11 I am running 3 monitors: Samsung with resolution 3840x2160 and 2 LG monitors with resolution 1920x1080, all at 60Hz Most of the flickering is happening on Samsung, although once in a while, other monitors flicker a little bit as well. Things to note: When I switch Samsung to lower resolution, the flickering goes away. When I come back to 3840x2160, it comes back. When I switch to lower resolution, suspend and come back, everything is fine. If I reboot the machine, the display is fine until I suspend and wake up again (if I am in higher resolution). I tried changing the refresh rate of Samsung to 30.00 and 29.97 (the only two available when I turn off FreeSync), and the issue still persists. Turning FreeSync on and off does nothing. Thank you, Pavel. 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 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: pavel 1870 F pulseaudio /dev/snd/controlC0: pavel 1870 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 23 21:14:00 2020 InstallationDate: Installed on 2020-04-23 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=02f6301e-c22b-462d-a4e5-71a78b7eb203 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1405 dmi.board.asset.tag: Default string dmi.board.name: TUF GAMING X570-PLUS (WI-FI) dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1405:bd11/19/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX570-PLUS(WI-FI):rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874588/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1872001] Re: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0
@arighi I'm testing your kernel on an affected dell xps 13 9300, and it looks like there are momentary hangs but no crashing any more with your patches. In dmesg just after a hang, I see: [ 338.955106] i915 :00:02.0: GPU HANG: ecode 11:1:0xfffe, in Xorg [1315], hang on rcs0 [ 338.956204] i915 :00:02.0: Resetting rcs0 for hang on rcs0 ...and then things resume. In 5.3.0-46 without your patches, this would have crashed my session. If it helps with more debugging, I've attached the log from /sys/class/drm/card0/error ** Attachment added: "/sys/class/drm/card0/error" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872001/+attachment/5358921/+files/i915.error.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/1872001 Title: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0 Status in linux package in Ubuntu: Confirmed Status in linux source package in Eoan: In Progress Bug description: Hi, Since update to HWE kernel 5.3.0-46-generic I am experiencing frequent (every couple of minutes) GPU hangs and reset manifesting as 2-3 seconds freezes of the GUI (other than the mouse pointer). No particular triggers identified although have Chrome / Chromium running with Hardware Acceleration enabled does appear to increase the frequency. I have seen incidences of these hangs in jounralctl output using previous kernels in the 5.3.0-xx series but they were very infrequent (one or twice in a week of daily usage) System Info steve@steve-Inspiron-5580:~$ inxi -SCGxxxz System:Host: steve-Inspiron-5580 Kernel: 5.3.0-46-generic x86_64 bits: 64 compiler: gcc v: 7.5.0 Desktop: Cinnamon 4.4.8 wm: muffin 4.4.2 dm: LightDM 1.26.0 Distro: Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic CPU: Topology: Quad Core model: Intel Core i5-8265U bits: 64 type: MT MCP arch: Kaby Lake rev: B L2 cache: 6144 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 28800 Speed: 1173 MHz min/max: 400/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 Graphics: Device-1: Intel vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:3ea0 Display: x11 server: X.Org 1.20.5 driver: modesetting unloaded: fbdev,vesa resolution: 1920x1080~60Hz OpenGL: renderer: Mesa DRI Intel UHD Graphics (Whiskey Lake 3x8 GT2) v: 4.5 Mesa 19.2.8 compat-v: 3.0 direct render: Yes steve@steve-Inspiron-5580:~$ journalctl -b | grep i915 Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: vgaarb: deactivate vga console Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem Apr 10 06:15:17 steve-Inspiron-5580 kernel: [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4) Apr 10 06:15:17 steve-Inspiron-5580 kernel: [drm] Initialized i915 1.6.0 20190619 for :00:02.0 on minor 0 Apr 10 06:15:17 steve-Inspiron-5580 kernel: fbcon: i915drmfb (fb0) is primary device Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: fb0: i915drmfb frame buffer device Apr 10 06:15:17 steve-Inspiron-5580 kernel: snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) Apr 10 06:16:28 steve-Inspiron-5580 kernel: i915 :00:02.0: GPU HANG: ecode 9:0:0x, hang on rcs0 Apr 10 06:16:28 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:31:46 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:37:48 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:40:46 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 I note another user has reported similar issues on the same kernel at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861395/comments/52 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: steve 3920 F pulseaudio /dev/snd/pcmC0D0p: steve 3920 F...m pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.3 HibernationDevice: RESUME=none InstallationDate: Installed on 2019-12-27 (104 days ago) InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213 MachineType: Dell Inc. Inspiron 5580 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic root=UUID=b0eaa5bb-0276-42d4-938f-ee6ce1627906 ro usb_storage.quirks=0bc2:2320: quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18 RelatedPackageVersions:
[Kernel-packages] [Bug 1874588] [NEW] Flickering screen after waking up from Suspend
Public bug reported: Just did a fresh install of Ubuntu 20.04 LTS and everything was fine, display worked perfect. Then I put the machine in Suspend mode (by clicking on GUI button), left for 5 minutes, came back, woke up the machine (by clicking a key on the keyboard), and upon waking up, the display started flickering heavily. Relevant Specs (Sorry if I missed anything): AMD® Ryzen 9 3900x 12-core processor × 24 AMD® Radeon rx 5700 xt GNOME version 3.36.1 Windowing System X11 I am running 3 monitors: Samsung with resolution 3840x2160 and 2 LG monitors with resolution 1920x1080, all at 60Hz Most of the flickering is happening on Samsung, although once in a while, other monitors flicker a little bit as well. Things to note: When I switch Samsung to lower resolution, the flickering goes away. When I come back to 3840x2160, it comes back. When I switch to lower resolution, suspend and come back, everything is fine. If I reboot the machine, the display is fine until I suspend and wake up again (if I am in higher resolution). I tried changing the refresh rate of Samsung to 30.00 and 29.97 (the only two available when I turn off FreeSync), and the issue still persists. Turning FreeSync on and off does nothing. Thank you, Pavel. 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 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: pavel 1870 F pulseaudio /dev/snd/controlC0: pavel 1870 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 23 21:14:00 2020 InstallationDate: Installed on 2020-04-23 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=02f6301e-c22b-462d-a4e5-71a78b7eb203 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1405 dmi.board.asset.tag: Default string dmi.board.name: TUF GAMING X570-PLUS (WI-FI) dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1405:bd11/19/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX570-PLUS(WI-FI):rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874588 Title: Flickering screen after waking up from Suspend Status in linux package in Ubuntu: Confirmed Bug description: Just did a fresh install of Ubuntu 20.04 LTS and everything was fine, display worked perfect. Then I put the machine in Suspend mode (by clicking on GUI button), left for 5 minutes, came back, woke up the machine (by clicking a key on the keyboard), and upon waking up, the display started flickering heavily. Relevant Specs (Sorry if I missed anything): AMD® Ryzen 9 3900x 12-core processor × 24 AMD® Radeon rx 5700 xt GNOME version 3.36.1 Windowing System X11 I am running 3 monitors: Samsung with resolution 3840x2160 and 2 LG monitors with resolution 1920x1080, all at 60Hz Most of the flickering is happening on Samsung, although once in a while, other monitors flicker a little bit as well. Things to note: When I switch Samsung to lower resolution, the flickering goes away. When I come back to 3840x2160, it comes back. When I switch to lower resolution, suspend and come back, everything is fine. If I reboot the machine, the display is fine until I suspend and wake up again (if I am in higher resolution). I tried changing the refresh rate of Samsung to 30.00 and 29.97 (the only two available when I turn off FreeSync), and the issue still persists. Turning FreeSync on and off does nothing. Thank you, Pavel. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-26-gen
[Kernel-packages] [Bug 1860754] Re: ASUS T100HAN boots to a blank screen with a cursor [i965: Failed to submit batchbuffer: Input/output error]
Hi Kai-Heng Feng, Thank you very much for your information. I will learn more about SSH. Should I have some action on this or not yet? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860754 Title: ASUS T100HAN boots to a blank screen with a cursor [i965: Failed to submit batchbuffer: Input/output error] Status in linux package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Bug description: === SRU Justification === [Impact] PMIC_OPREGION is required to make GFX works on Bay Trail and Cherry Trial based tablets. [Fix] Enable CONFIG_PMIC_OPREGION. CONFIG_GPIO_CRYSTAL_COVE needs to be loaded before i915 to control panel, so change it to builtin. These configs are aligned with Fedora kernel. [Test] The i915 can now kinda work albeit hitting another bug. That's a different issue though. [Regression Potential] Low. These configs only affects Intel-based budget tablets, GFX never worked. It's a bit late for Focal so only enable configs in Unstable. === Original Bug Report === - After installed Ubuntu 19.10 with nomodeset i915.modeset=0, it won't recognize graphic driver. - run udo apt-get install xserver-xorg-video-intel 0 upgraded, 0 newly installed, 0 to remove and 144 not upgraded. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jan 24 14:29:01 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b0] (rev 20) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers [1043:1bdd] InstallationDate: Installed on 2020-01-24 (0 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 003: ID 0b05:1807 ASUSTek Computer, Inc. USB2.0 Hub Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. T100HAN ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=/dev/mapper/vgubuntu-root ro nomodeset i915.modeset=0 quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: T100HAN.221 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: T100HAN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrT100HAN.221:bd05/18/2016:svnASUSTeKCOMPUTERINC.:pnT100HAN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnT100HAN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: T dmi.product.name: T100HAN dmi.product.sku: ASUS-TabletSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860754/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1871248] Re: amdgpu kernel errors in Linux 5.4
** Description changed: + [Impact] + + amdgpu generates assert warning messages when retimer is not supported. + This behaviour can cause confusions to users. + + [Fix] + + This is fixed by commit a0e40018dcc3f59a. It silences ASSERTs by + outputing a debug message and exiting when retimer is not supported by + hardware. + + [Test] + + Verified on B450 I AORUS PRO WIFI with AMD Ryzen 3 3200G as discussed + on LP:1871248. + + [Regression Potential] + + Low. It is for unsupported hardware features, and the patch was cherry-picked + from upstream kernel 5.7 rc1. + + == + Linux atlas 5.4.0-21-generic #25-Ubuntu SMP Sat Mar 28 13:10:28 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Ubuntu 20.04 beta fresh installation. Upgrades applied. AMD Ryzen 3 3200G with Radeon Vega Graphics Motherboard: Gigabyte B450 I AORUS PRO WIFI/B450 I AORUS PRO WIFI-CF, BIOS F50 11/27/2019 - These errors keep appearing in the kernel messages. + These errors keep appearing in the kernel messages. [3.258890] [ cut here ] [3.258944] WARNING: CPU: 1 PID: 621 at drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_link.c:1737 write_i2c_retimer_setting+0xc8/0x3e0 [amdgpu] [3.258945] Modules linked in: amd64_edac_mod(-) cmac algif_hash algif_skcipher af_alg bnep edac_mce_amd ccp kvm snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi snd_hda_intel snd_intel_nhlt snd_hda_codec snd_hda_core snd_hwdep snd_pcm crct10dif_pclmul ghash_clmulni_intel snd_seq_midi nls_iso8859_1 snd_seq_midi_event snd_rawmidi snd_seq aesni_intel iwlmvm crypto_simd mac80211 amdgpu cryptd libarc4 glue_helper snd_seq_device amd_iommu_v2 btusb iwlwifi gpu_sched btrtl wmi_bmof ttm btbcm k10temp snd_timer btintel input_leds drm_kms_helper bluetooth snd fb_sys_fops syscopyarea cfg80211 sysfillrect soundcore sysimgblt ecdh_generic ecc mac_hid sch_fq_codel parport_pc ppdev lp drm parport ip_tables x_tables autofs4 hid_generic usbhid hid nvme crc32_pclmul i2c_piix4 ahci igb nvme_core i2c_algo_bit dca libahci wmi video gpio_amdpt gpio_generic [3.258966] CPU: 1 PID: 621 Comm: gpu-manager Not tainted 5.4.0-21-generic #25-Ubuntu [3.258967] Hardware name: Gigabyte Technology Co., Ltd. B450 I AORUS PRO WIFI/B450 I AORUS PRO WIFI-CF, BIOS F50 11/27/2019 [3.259012] RIP: 0010:write_i2c_retimer_setting+0xc8/0x3e0 [amdgpu] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-21-generic 5.4.0-21.25 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC1: kirt 1293 F pulseaudio - /dev/snd/controlC0: kirt 1293 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC1: kirt 1293 F pulseaudio + /dev/snd/controlC0: kirt 1293 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Apr 6 15:52:30 2020 InstallationDate: Installed on 2020-04-06 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: Gigabyte Technology Co., Ltd. B450 I AORUS PRO WIFI ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=9940ba5b-7683-413e-92a2-854b3816799b ro quiet splash vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-5.4.0-21-generic N/A - linux-backports-modules-5.4.0-21-generic N/A - linux-firmware1.187 + linux-restricted-modules-5.4.0-21-generic N/A + linux-backports-modules-5.4.0-21-generic N/A + linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/27/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F50 dmi.board.asset.tag: Default string dmi.board.name: B450 I AORUS PRO WIFI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF50:bd11/27/2019:svnGigabyteTechnologyCo.,Ltd.:pnB450IAORUSPROWIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450IAORUSPROWIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B450 I AORUS PRO WIFI dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. -- You received this bug notification because you are a member of Kernel
[Kernel-packages] [Bug 1871917] Re: Unable to boot 20.04 installer on Dell XPS 15 9560
Can confirm multiple USB sticks (16 and 32GB) exhibit same symptoms whilst booting without issue on other laptops (Acer Swift 5 in my case). Occurs both when bootable USB is created via startup dis creator and dd. Have successfully installed 19.10 via startup disk creator using one of the USB sticks exhibiting issue. Appears to only be focal iso. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1871917 Title: Unable to boot 20.04 installer on Dell XPS 15 9560 Status in linux package in Ubuntu: Confirmed Bug description: I tried to boot the 20.04 nightly image (focal-desktop-amd64.iso 2020-04-05 11:06 ) as well as an older one (a week ago) on my Dell XPS 15 9560, and I got the same error message each time. The live system performs a filesystem check while showing a progress bar on a screen with dell and ubuntu logo, then the linux console shows with following error: sd 2:0:0:0: [sda] tag#0 access beyond end of device blk_update_request: I/O error, dev sda, sector 30529408 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 sd 2:0:0:0: [sda] tag#0 access beyond end of device blk_update_request: I/O error, dev sda, sector 30529408 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Buffer I/O error on dev sda, logical block 3816176 async page read This happens with two different 16GB usb sticks on the Dell XPS 15. They both worked fine on an old samsung netbook. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871917/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
Confirmed, after adding the nvidia-drm.modeset=1 to the GRUB file it worked. I tested 3 cases: 1. Reboot without Log out afterwards. 2. Reboot with a Log out afterwards and then try to log in again. 3. Reboot with a Log out afterwards, try to log in again and then reboot. It worked for all cases. Of course this is still a workaround, but it works for the time being. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Invalid Status in gdm3 source package in Eoan: Confirmed Status in gnome-session source package in Eoan: Confirmed Status in nvidia-graphics-drivers-435 source package in Eoan: Confirmed Bug description: I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A67 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to:
[Kernel-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
This is exactly what is happening to me. I installed Ubuntu 20.04 today (The official released version, not beta), and if I set the auto login on, it will give me the same issue the original poster said. You can't login afterwards and if your logout, it enter a loop where you will never come out from unless you purge gdm3 and install it back or other workarounds that I can't guarantee work alone. I have an Nvidia GTX 1080 running on the Proprietary 440 Driver. My user is "luis" and the password is "x" in case anyone would want to literally try it out with the same user/pass/hardware combination. If I disable the auto login then everything related to logout/login works correctly. The hardware is down below of an Asus Hero Alpha VII, Intel 6700k and 64 GB of RAM. The SSD is a Samsung 850 Pro 1TB. 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers (rev 07) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x16) (rev 07) 00:14.0 USB controller: Intel Corporation 100 Series/C230 Series Chipset Family USB 3.0 xHCI Controller (rev 31) 00:16.0 Communication controller: Intel Corporation 100 Series/C230 Series Chipset Family MEI Controller #1 (rev 31) 00:17.0 SATA controller: Intel Corporation Q170/Q150/B150/H170/H110/Z170/CM236 Chipset SATA Controller [AHCI Mode] (rev 31) 00:1b.0 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #17 (rev f1) 00:1c.0 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #1 (rev f1) 00:1c.2 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #3 (rev f1) 00:1c.4 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #5 (rev f1) 00:1c.7 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #8 (rev f1) 00:1d.0 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #9 (rev f1) 00:1d.4 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #13 (rev f1) 00:1f.0 ISA bridge: Intel Corporation Z170 Chipset LPC/eSPI Controller (rev 31) 00:1f.2 Memory controller: Intel Corporation 100 Series/C230 Series Chipset Family Power Management Controller (rev 31) 00:1f.3 Audio device: Intel Corporation 100 Series/C230 Series Chipset Family HD Audio Controller (rev 31) 00:1f.4 SMBus: Intel Corporation 100 Series/C230 Series Chipset Family SMBus (rev 31) 00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (2) I219-V (rev 31) 01:00.0 VGA compatible controller: NVIDIA Corporation GP104 [GeForce GTX 1080] (rev a1) 01:00.1 Audio device: NVIDIA Corporation GP104 High Definition Audio Controller (rev a1) 03:00.0 PCI bridge: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] 04:00.0 PCI bridge: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] 04:01.0 PCI bridge: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] 04:02.0 PCI bridge: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] 04:04.0 PCI bridge: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] 07:00.0 USB controller: Intel Corporation DSL6540 USB 3.1 Controller [Alpine Ridge] 09:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32) 0a:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 02) 0b:00.0 USB controller: Fresco Logic FL1100 USB 3.0 Host Controller (rev 10) I will try the removing of splash and then adding nvidia-drm.modeset=1 to see how it goes. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Invalid Status in gdm3 source package in Eoan: Confirmed Status in gnome-session source package in Eoan: Confirmed Status in nvidia-graphics-drivers-435 source package in Eoan: Confirmed Bug description: I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts
Re: [Kernel-packages] [Bug 1870260] Re: initramfs unpacking failed: Decoding failed", message appears on boot up.
*** This bug is a duplicate of bug 1835660 *** https://bugs.launchpad.net/bugs/1835660 Thank you. Problem solved, have a good day! Paul Kowalzyk On Thu, Apr 23, 2020 at 8:39 AM Blaze <1870...@bugs.launchpad.net> wrote: > *** This bug is a duplicate of bug 1835660 *** > https://bugs.launchpad.net/bugs/1835660 > > ** This bug has been marked a duplicate of bug 1835660 >initramfs unpacking failed > > -- > You received this bug notification because you are subscribed to the bug > report. > 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 > -- You 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)
[Kernel-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
I installed Ubuntu 20.04 5 days ago (using the daily iso) and works fine with Quadro P3200 Mobile and default proprietary drivers installed. I installed it setting up the user with autologon from the installer. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Invalid Status in gdm3 source package in Eoan: Confirmed Status in gnome-session source package in Eoan: Confirmed Status in nvidia-graphics-drivers-435 source package in Eoan: Confirmed Bug description: I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A67 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1874553] [NEW] bionic/oracle-5.3: Move bnxt_en driver from -modules-extras to -modules
Public bug reported: Title is self-explanatory. There's a salesforce: https://canonical.my.salesforce.com/5003z25rjtc ** Affects: linux-oracle (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oracle (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-oracle (Ubuntu) Importance: Undecided Status: New ** No longer affects: kernel-sru-workflow ** Also affects: linux-oracle (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1874553 Title: bionic/oracle-5.3: Move bnxt_en driver from -modules-extras to -modules Status in linux-oracle package in Ubuntu: New Status in linux-oracle source package in Bionic: New Bug description: Title is self-explanatory. There's a salesforce: https://canonical.my.salesforce.com/5003z25rjtc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oracle/+bug/1874553/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1869672] Re: kdump kernel can't be loaded using kernel 4.15.0-76
Hi yamato, I'm sorry but I found yet another issue that I need to take care in my fix, hopefully by tomorrow I'll have a new test kernel. Also, I've noticed that in order to test PPA kernels on secure boot systems, you'll need to enroll the PPA sign key on shim, to make the kernel bootable - I'll present the details when kernel is ready. Thanks, Guilherme -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1869672 Title: kdump kernel can't be loaded using kernel 4.15.0-76 Status in makedumpfile package in Ubuntu: In Progress Status in makedumpfile source package in Bionic: In Progress Bug description: Thank you for reading this report. This may caused by bugs in kernel, not in kdump. If so, I will report this to kernel team. I need your comment to solve this. [Impact] * Kdump kernel can't be loaded using linux kernel 4.15.0-76. [Environment] Description:Ubuntu 18.04.4 LTS Release:18.04 uname: Linux ubuntu 4.15.0-76-generic #86-Ubuntu SMP Fri Jan 17 17:24:28 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Secure boot is enabled. Versions: * kexec-tools/bionic-updates,now 1:2.0.16-1ubuntu1.1 * kdump-tools/bionic-updates,now 1:1.6.5-1ubuntu1~18.04.4 [Test case] 1)After OS booted, run systemctl status kdump-tools shows these messages below: ● kdump-tools.service - Kernel crash dump capture service Loaded: loaded (/lib/systemd/system/kdump-tools.service; enabled; vendor preset: enabled) Active: active (exited) since Fri 2020-03-27 16:40:31 JST; 5min ago Process: 895 ExecStart=/etc/init.d/kdump-tools start (code=exited, status=0/SUCCESS) Main PID: 895 (code=exited, status=0/SUCCESS) Mar 27 16:40:31 ubuntu systemd[1]: Starting Kernel crash dump capture service... Mar 27 16:40:31 ubuntu kdump-tools[895]: Starting kdump-tools: * Creating symlink /var/lib/kdump/vmlinuz Mar 27 16:40:31 ubuntu kdump-tools[895]: * Creating symlink /var/lib/kdump/initrd.img Mar 27 16:40:31 ubuntu kdump-tools[895]: kexec_file_load failed: Exec format error Mar 27 16:40:31 ubuntu kdump-tools[895]: * failed to load kdump kernel Mar 27 16:40:31 ubuntu systemd[1]: Started Kernel crash dump capture service. 2)Run kexec directly: $ sudo /sbin/kexec -p --command-line="/boot/vmlinuz-4.15.0-76-generic root=UUID=29a89ad8-8923-435e-a88c-aaf5cb379568 ro mce=ignore_ce reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1 irqpoll nousb ata_piix.prefer_ms_hyperv=0" --initrd=/boot/initrd.img-4.15.0-76-generic /boot/vmlinuz-4.15.0-64-generic Then,these messages are shown: Cannot open /proc/kcore: Operation not permitted Cannot read /proc/kcore: Operation not permitted Cannot load /boot/vmlinuz-4.15.0-76-generic On dmesg, these messages are shown: [ 538.524718] Lockdown: /proc/kcore is restricted; see man kernel_lockdown.7 3) Changing OS kernel to older one(I used 4.15.0-64), kdump kernel can be loaded. $ sudo systemctl status kdump-tools ● kdump-tools.service - Kernel crash dump capture service Loaded: loaded (/lib/systemd/system/kdump-tools.service; enabled; vendor preset: enabled) Active: active (exited) since Wed 2020-03-25 13:39:03 JST; 5 days ago Main PID: 832 (code=exited, status=0/SUCCESS) Tasks: 0 (limit: 4915) CGroup: /system.slice/kdump-tools.service Mar 25 13:39:02 ubuntu systemd[1]: Starting Kernel crash dump capture service... Mar 25 13:39:02 ubuntu kdump-tools[832]: Starting kdump-tools: * Creating symlink /var/lib/kdump/vmlinuz Mar 25 13:39:02 ubuntu kdump-tools[832]: * Creating symlink /var/lib/kdump/initrd.img Mar 25 13:39:03 ubuntu kdump-tools[832]: * loaded kdump kernel Mar 25 13:39:03 ubuntu kdump-tools[938]: loaded kdump kernel Mar 25 13:39:03 ubuntu systemd[1]: Started Kernel crash dump capture service. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1869672/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1870614] Re: Unable to boot ubuntu 19.10 or newer on dell xps 9570
I cannot boot off 20.04 final release with the same issue. I am going to attempt an upgrade from 18.04 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/1870614 Title: Unable to boot ubuntu 19.10 or newer on dell xps 9570 Status in linux package in Ubuntu: Confirmed Bug description: Hi, Since updating my dell xps 9570 (latest BIOS 1.15.0 and a few previous versions) from 19.04 to 19.10 I have been unable to boot ubuntu. It fails with the following error quickly flashing: error: file `/boot/` not found Then followed by: error: cannot allocate kernel buffer. error: you need to load the kernel first. press any key to continue... This occurs when doing an update from 19.04 to 19.10 and also when just booting off a usb drive with 19.10. When booting off the usb drive. The first error flashes quickly before displaying the usb installer options. Selecting any install / boot option results in the second error about kernel buffer. I have tried all combinations of bios settings I can think of, such as toggling secure boot and other options. The only thing that made a difference is booting via USB with LEGACY EXTERNAL DEVICE BOOT. This allows the installer to complete, but I cannot then boot off the hard drive. I have tried the same USB drive with 19.10 on a Dell XPS 7590 with BIOS 1.2.3 and the USB stick boots fine. I have also tried many different USB drives on my 9570. I have tried a few daily builds of 20.04 with the same result. I tested with 20.04 beta as well. Note: 19.04 and earlier continues to work no problem. I have asked for help previously: * https://askubuntu.com/questions/1183129/19-10-usb-installer-boot-fail * https://answers.launchpad.net/ubuntu/+question/689546/+index ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: ubuntu-release-upgrader-core 1:19.04.16.9 ProcVersionSignature: Ubuntu 5.0.0-38.41-generic 5.0.21 Uname: Linux 5.0.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27.3 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 06:55:59 2020 InstallationDate: Installed on 2019-10-24 (162 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bananan2456 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-04-13 (2 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: Dell Inc. XPS 15 9570 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-46-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-46-generic N/A linux-backports-modules-5.3.0-46-generic N/A linux-firmware1.173.17 Tags: bionic Uname: Linux 5.3.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 07GHH0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd12/25/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn07GHH0:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1870614/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
I have just built a brand new Ubuntu 20.04 system (nVidia GTX1070) and the bug existed on 2 fresh reinstalls. When enabling Autologin, the system fails. Disabling it and there is no issues. Running Proprietary 440 driver build, installed by the installer. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Invalid Status in gdm3 source package in Eoan: Confirmed Status in gnome-session source package in Eoan: Confirmed Status in nvidia-graphics-drivers-435 source package in Eoan: Confirmed Bug description: I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A67 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages
[Kernel-packages] [Bug 1873885] Re: USB keyboard / mouse does not wake computer from sleep
Workaround :
Put in /etc/udev/rules.d/10-wakeup.rules
The folliwing lines
ACTION=="add", SUBSYSTEM=="usb", ATTRS{idVendor}=="046d",
ATTRS{idProduct}=="c52b" RUN+="/bin/sh -c 'echo enabled >
/sys/bus/usb/devices/1-1/power/wakeup'"
ACTION=="add", SUBSYSTEM=="usb", ATTRS{idVendor}=="046d",
ATTRS{idProduct}=="c52b" RUN+="/bin/sh -c 'echo enabled >
/sys/bus/usb/devices/1-2/power/wakeup'"
ACTION=="add", SUBSYSTEM=="usb", ATTRS{idVendor}=="046d",
ATTRS{idProduct}=="c52b" RUN+="/bin/sh -c 'echo enabled >
/sys/bus/usb/devices/1-3/power/wakeup'"
But this will only work for my computer and my dongle.
I guess something has changed in the kernel config or somewhere else, because
- this same workaround did not work a few days ago (cf. comment #2)
- the use of battery or AC power does not change anything (contrary to comment
#20)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1873885
Title:
USB keyboard / mouse does not wake computer from sleep
Status in linux package in Ubuntu:
Confirmed
Bug description:
I use a USB Logitech keyboard & mouse combo with a Logitech USB "Unifying"
receiver.
With Ubuntu 19.10, moving the mouse or hitting a key woke the computer from
sleep.
With Ubuntu 20.04, it does not work anymore.
~$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 8087:0a2b Intel Corp.
Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC
WebCam
Bus 001 Device 015: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: guillaume 1726 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: GNOME
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2020-04-11 (9 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 8087:0a2b Intel Corp.
Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC
WebCam
Bus 001 Device 008: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. UX410UAK
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=fr_FR.UTF-8
SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-25-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30
RelatedPackageVersions:
linux-restricted-modules-5.4.0-25-generic N/A
linux-backports-modules-5.4.0-25-generic N/A
linux-firmware1.187
Tags: focal wayland-session
Uname: Linux 5.4.0-25-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: 04/17/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX410UAK.312
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX410UAK
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.312:bd04/17/2019:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: ZenBook
dmi.product.name: UX410UAK
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873885/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1873885] Re: USB keyboard / mouse does not wake computer from sleep
New testing today, with latest kernel update. Booting with Unifying dongle plugged in: guillaume@massada:~$ uname -a Linux massada 5.4.0-26-generic #30-Ubuntu SMP Mon Apr 20 16:58:30 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux guillaume@massada:~$ grep . /sys/bus/usb/devices/*/power/wakeup /sys/bus/usb/devices/1-2/power/wakeup:enabled /sys/bus/usb/devices/1-8/power/wakeup:disabled /sys/bus/usb/devices/usb1/power/wakeup:disabled /sys/bus/usb/devices/usb2/power/wakeup:disabled Unplugging the dongle, and then plugging it again, same USB port: guillaume@massada:~$ grep . /sys/bus/usb/devices/*/power/wakeup /sys/bus/usb/devices/1-2/power/wakeup:disabled /sys/bus/usb/devices/1-8/power/wakeup:disabled /sys/bus/usb/devices/usb1/power/wakeup:disabled /sys/bus/usb/devices/usb2/power/wakeup:disabled Waking the computer from sleep with mouse or keyboard does not work anymore. guillaume@massada:~$ sudo -s root@massada:/home/guillaume# echo "enabled" > /sys/bus/usb/devices/1-2/power/wakeup root@massada:/home/guillaume# exit guillaume@massada:~$ grep . /sys/bus/usb/devices/*/power/wakeup /sys/bus/usb/devices/1-2/power/wakeup:enabled /sys/bus/usb/devices/1-8/power/wakeup:disabled /sys/bus/usb/devices/usb1/power/wakeup:disabled /sys/bus/usb/devices/usb2/power/wakeup:disabled Waking the computer from sleep with mouse or keyboard works again! >> This should be re-enabled by default whenever you (re)plug such a dongle. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1873885 Title: USB keyboard / mouse does not wake computer from sleep Status in linux package in Ubuntu: Confirmed Bug description: I use a USB Logitech keyboard & mouse combo with a Logitech USB "Unifying" receiver. With Ubuntu 19.10, moving the mouse or hitting a key woke the computer from sleep. With Ubuntu 20.04, it does not work anymore. ~$ lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC WebCam Bus 001 Device 015: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: guillaume 1726 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-11 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC WebCam Bus 001 Device 008: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-25-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-25-generic N/A linux-backports-modules-5.4.0-25-generic N/A linux-firmware1.187 Tags: focal wayland-session Uname: Linux 5.4.0-25-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: 04/17/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.312 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.312:bd04/17/2019:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873885/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1872001] Re: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0
@hbogert I've uploaded all the required deb's, it should be easier to install the test kernel now: https://kernel.ubuntu.com/~arighi/LP-1861395/5.3/ 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/1872001 Title: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0 Status in linux package in Ubuntu: Confirmed Status in linux source package in Eoan: In Progress Bug description: Hi, Since update to HWE kernel 5.3.0-46-generic I am experiencing frequent (every couple of minutes) GPU hangs and reset manifesting as 2-3 seconds freezes of the GUI (other than the mouse pointer). No particular triggers identified although have Chrome / Chromium running with Hardware Acceleration enabled does appear to increase the frequency. I have seen incidences of these hangs in jounralctl output using previous kernels in the 5.3.0-xx series but they were very infrequent (one or twice in a week of daily usage) System Info steve@steve-Inspiron-5580:~$ inxi -SCGxxxz System:Host: steve-Inspiron-5580 Kernel: 5.3.0-46-generic x86_64 bits: 64 compiler: gcc v: 7.5.0 Desktop: Cinnamon 4.4.8 wm: muffin 4.4.2 dm: LightDM 1.26.0 Distro: Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic CPU: Topology: Quad Core model: Intel Core i5-8265U bits: 64 type: MT MCP arch: Kaby Lake rev: B L2 cache: 6144 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 28800 Speed: 1173 MHz min/max: 400/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 Graphics: Device-1: Intel vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:3ea0 Display: x11 server: X.Org 1.20.5 driver: modesetting unloaded: fbdev,vesa resolution: 1920x1080~60Hz OpenGL: renderer: Mesa DRI Intel UHD Graphics (Whiskey Lake 3x8 GT2) v: 4.5 Mesa 19.2.8 compat-v: 3.0 direct render: Yes steve@steve-Inspiron-5580:~$ journalctl -b | grep i915 Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: vgaarb: deactivate vga console Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem Apr 10 06:15:17 steve-Inspiron-5580 kernel: [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4) Apr 10 06:15:17 steve-Inspiron-5580 kernel: [drm] Initialized i915 1.6.0 20190619 for :00:02.0 on minor 0 Apr 10 06:15:17 steve-Inspiron-5580 kernel: fbcon: i915drmfb (fb0) is primary device Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: fb0: i915drmfb frame buffer device Apr 10 06:15:17 steve-Inspiron-5580 kernel: snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) Apr 10 06:16:28 steve-Inspiron-5580 kernel: i915 :00:02.0: GPU HANG: ecode 9:0:0x, hang on rcs0 Apr 10 06:16:28 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:31:46 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:37:48 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:40:46 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 I note another user has reported similar issues on the same kernel at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861395/comments/52 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: steve 3920 F pulseaudio /dev/snd/pcmC0D0p: steve 3920 F...m pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.3 HibernationDevice: RESUME=none InstallationDate: Installed on 2019-12-27 (104 days ago) InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213 MachineType: Dell Inc. Inspiron 5580 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic root=UUID=b0eaa5bb-0276-42d4-938f-ee6ce1627906 ro usb_storage.quirks=0bc2:2320: quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-46-generic N/A linux-backports-modules-5.3.0-46-generic N/A linux-firmware1.173.17 Tags: tricia Uname: Linux 5.3.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 07/02/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 0K0DFT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10
[Kernel-packages] [Bug 1812128] Re: No IRQ handler for Vector
Wow, this is really old. I am sorry for the lack of information. The built-in system is obviously flawed, as previously noted. Further, I no longer use Xubuntu, and have been very happy moving to Debian for a long time now. No more errors and screw-ups from trying to reinvent the wheel, and no more bad tech support. Thanks anyway. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1812128 Title: No IRQ handler for Vector Status in linux package in Ubuntu: Confirmed Bug description: This message appears on screen first during bootup. Description: Ubuntu 16.04.5 LTS Release: 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812128/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850439] Re: No sound on ASUS UX534FT
Fresh install Ubuntu 20.04 Sound works with bluetooth speakers and HDMI BUT still no sound through internal speakers 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/1850439 Title: No sound on ASUS UX534FT Status in linux package in Ubuntu: Confirmed Bug description: Hi, after instal Ubuntu in dual boot alongside Windows 10, I've realised there is no sound coming out of mine new ASUS Zenbook 15 UX534FT- AA024R in Ubuntu. In Windows there is no problem. Found this topic https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810214 which had the same problem with driver for Realtek ALC294 which is also mine sound card. But even with this fix it is not working on UX534FT. Can you please add fix also for this newer model? Description: Ubuntu 18.04.3 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.0.0-32-generic 5.0.0-32.34~18.04.2 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 29 15:11:25 2019 InstallationDate: Installed on 2019-10-29 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1812128] Re: No IRQ handler for Vector
Can you provide a dmesg log at least? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1812128 Title: No IRQ handler for Vector Status in linux package in Ubuntu: Confirmed Bug description: This message appears on screen first during bootup. Description: Ubuntu 16.04.5 LTS Release: 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812128/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874444] 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 187
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/187
Title:
Bionic ubuntu ethtool doesn't check ring parameters boundaries
Status in linux package in Ubuntu:
Incomplete
Bug description:
Upstream linux kernel implemented ring parameter boundaries check in commit:
37e2d99b59c4 ("ethtool: Ensure new ring parameters are within bounds during
SRINGPARAM")
(see link
https://patchwork.ozlabs.org/project/netdev/patch/1515420026-11970-2
-git-send-email-tar...@mellanox.com/)
Due to this commit, the community doesn't allow ring parameter
boundary checks in driver code.
The Bionic ubuntu kernel does not include this patch. And some network
drivers rely on this patch for
boundary checking of ring params.
This causes bugs in case a ringparam was given an illegal value.
Reproduction steps in AWS:
1. Create new c5.4xlarge instance with the ubuntu 18.04 official ami (uses
the ENA network driver) and update to latest kernel using apt-get dist-upgrade
and reboot for the new kernel to load.
2. Run ethtool -g ens5
output:
Ring parameters for ens5:
Pre-set maximums:
RX: 16384
RX Mini: 0
RX Jumbo: 0
TX: 1024
Current hardware settings:
RX: 1024
RX Mini: 0
RX Jumbo: 0
TX: 1024
3. Change the tx ring size to a legal number within boundaries - works!
4. Change the tx ring size to an illegal number such as 2048 with the command
- sudo ethtool -G ens5 tx 2048.
Expected behavior - operation not allowed
Actual behavior - causes a crash of the driver since boundaries are not
checked by ethtool.
Proposed fix - include the above commit 37e2d99b59c4 ("ethtool: Ensure
new ring parameters are within bounds during SRINGPARAM") in bionic
(and probably other ubuntu releases as well)
More data about the machine where the bug occured:
ubuntu@ip-172-31-80-28:~/bionic$ lsb_release -rd
Description: Ubuntu 18.04.4 LTS
Release: 18.04
ubuntu@ip-172-31-80-28:~/bionic$ uname -r
4.15.0-1065-aws
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/187/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856433] Re: do_IRQ: 1.55 No irq handler for vector
As you can see in the dmesg log it happens when the kernel is initializing the second CPU core. I believe this started after the AMD microcode update against Spectre/Meltdown mitigations. Should be reported also to https://bugzilla.kernel.org/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1856433 Title: do_IRQ: 1.55 No irq handler for vector Status in linux package in Ubuntu: Confirmed Bug description: 1) Ubuntu 19.10 2) system 3) no error. 4) Error in log app. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: htpc 9157 F pulseaudio /dev/snd/controlC1: htpc 9157 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-10-28 (48 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lxcbr0no wireless extensions. lono wireless extensions. enp3s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. GA-MA780G-UD3H Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic root=UUID=0fa008d8-2279-4e78-9043-161b7f514243 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 RelatedPackageVersions: linux-restricted-modules-5.3.0-23-generic N/A linux-backports-modules-5.3.0-23-generic N/A linux-firmware1.183.2 RfKill: Tags: wayland-session eoan Uname: Linux 5.3.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/13/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F6b dmi.board.name: GA-MA780G-UD3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF6b:bd07/13/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA780G-UD3H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA780G-UD3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-MA780G-UD3H dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856433/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1872001] Re: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0
@eggie Yes, you should actually blacklist the nouveau module. Or instead, if you don't want your Nvidia card to drain power while you're using exclusively Intel graphics, run the following commands: sudo -i cat << EOF | sudo tee /etc/udev/rules.d/00-pcidevices.rules ACTION=="add", KERNEL==":01:00.0", SUBSYSTEM=="pci", RUN+="/bin/sh -c 'echo 1 > /sys/bus/pci/devices/:01:00.0/remove'" EOF This adds a permanent rule to eject the Nvidia card from your system so that it won't use any power. Reboot for it to take effect. On some laptops this doesn't stop the Nvidia card from draining power, but on Dell laptops it does. This is what I use on my Precision 5540, which is essentially the same laptop as yours. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1872001 Title: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0 Status in linux package in Ubuntu: Confirmed Status in linux source package in Eoan: In Progress Bug description: Hi, Since update to HWE kernel 5.3.0-46-generic I am experiencing frequent (every couple of minutes) GPU hangs and reset manifesting as 2-3 seconds freezes of the GUI (other than the mouse pointer). No particular triggers identified although have Chrome / Chromium running with Hardware Acceleration enabled does appear to increase the frequency. I have seen incidences of these hangs in jounralctl output using previous kernels in the 5.3.0-xx series but they were very infrequent (one or twice in a week of daily usage) System Info steve@steve-Inspiron-5580:~$ inxi -SCGxxxz System:Host: steve-Inspiron-5580 Kernel: 5.3.0-46-generic x86_64 bits: 64 compiler: gcc v: 7.5.0 Desktop: Cinnamon 4.4.8 wm: muffin 4.4.2 dm: LightDM 1.26.0 Distro: Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic CPU: Topology: Quad Core model: Intel Core i5-8265U bits: 64 type: MT MCP arch: Kaby Lake rev: B L2 cache: 6144 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 28800 Speed: 1173 MHz min/max: 400/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 Graphics: Device-1: Intel vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:3ea0 Display: x11 server: X.Org 1.20.5 driver: modesetting unloaded: fbdev,vesa resolution: 1920x1080~60Hz OpenGL: renderer: Mesa DRI Intel UHD Graphics (Whiskey Lake 3x8 GT2) v: 4.5 Mesa 19.2.8 compat-v: 3.0 direct render: Yes steve@steve-Inspiron-5580:~$ journalctl -b | grep i915 Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: vgaarb: deactivate vga console Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem Apr 10 06:15:17 steve-Inspiron-5580 kernel: [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4) Apr 10 06:15:17 steve-Inspiron-5580 kernel: [drm] Initialized i915 1.6.0 20190619 for :00:02.0 on minor 0 Apr 10 06:15:17 steve-Inspiron-5580 kernel: fbcon: i915drmfb (fb0) is primary device Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: fb0: i915drmfb frame buffer device Apr 10 06:15:17 steve-Inspiron-5580 kernel: snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) Apr 10 06:16:28 steve-Inspiron-5580 kernel: i915 :00:02.0: GPU HANG: ecode 9:0:0x, hang on rcs0 Apr 10 06:16:28 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:31:46 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:37:48 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:40:46 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 I note another user has reported similar issues on the same kernel at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861395/comments/52 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: steve 3920 F pulseaudio /dev/snd/pcmC0D0p: steve 3920 F...m pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.3 HibernationDevice: RESUME=none InstallationDate: Installed on 2019-12-27 (104 days ago) InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213 MachineType: Dell Inc. Inspiron 5580 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic root=UUID=b0eaa5bb-0276-42d4-938f-ee6ce1627906 ro usb_storage.quirks=0bc2:2320: quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18 RelatedPackageVersions:
[Kernel-packages] [Bug 1872984] Re: RTL8822BE network driver rtl_wifi crashes on boot in Focal Fossa 20.04 - 5.4.0-21-generic and mainline 5.7.0-050700rc1-generic
The system is Asus Vivobook 14. See https://gist.github.com/ayush-- s/46489a2c8ae2a42e58219c4b22fef6ef#file-dmesg-log-L781 for full hardware details captured in dmesg. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1872984 Title: RTL8822BE network driver rtl_wifi crashes on boot in Focal Fossa 20.04 - 5.4.0-21-generic and mainline 5.7.0-050700rc1-generic Status in linux package in Ubuntu: Incomplete Bug description: RTL8822BE crashes after rtw_pci starts on boot after kernel update to 5.4.0-21 (fails to read DBI register -- see attached dmesg). Issue is still present on latest mainline kernel version 5.7.0-050700rc1-generic . [ 10.627501] rtw_pci :3a:00.0: start vif 5c:ea:1d:b6:17:11 on port 0 [ 10.714544] [ cut here ] [ 10.714545] failed to read DBI register, addr=0x0719 [ 10.714577] WARNING: CPU: 0 PID: 939 at drivers/net/wireless/realtek/rtw88/pci.c:1156 rtw_dbi_read8.constprop.0+0xaa/0xc0 [rtwpci] [ 10.714577] Modules linked in: (see attached dmesg) [ 10.714614] CPU: 0 PID: 939 Comm: wpa_supplicant Not tainted 5.7.0-050700rc1-generic #202004122032 [ 10.714614] Hardware name: LENOVO 81CU/LNVNB161216, BIOS 7KCN22WW(V1.03) 01/23/2018 [ 10.714616] RIP: 0010:rtw_dbi_read8.constprop.0+0xaa/0xc0 [rtwpci] [ 10.714617] Code: 03 00 00 48 8b 40 50 e8 24 c3 4b e0 5b 41 5c 41 88 45 00 31 c0 41 5d 5d c3 be 19 07 00 00 48 c7 c7 70 73 94 c0 e8 bb de 75 df <0f> 0b b8 fb ff ff ff 5b 41 5c 41 5d 5d c3 0f 1f 84 00 00 00 00 00 [ 10.714618] RSP: 0018:b466007e7880 EFLAGS: 00010282 [ 10.714618] RAX: RBX: RCX: 0007 [ 10.714619] RDX: 0007 RSI: 0092 RDI: 933cc9e19c80 [ 10.714619] RBP: b466007e7898 R08: 03d2 R09: 0004 [ 10.714620] R10: R11: 0001 R12: 933cbdf31ea0 [ 10.714620] R13: b466007e78af R14: 933cbdf35bc8 R15: [ 10.714622] FS: 7fbcedc6efc0() GS:933cc9e0() knlGS: [ 10.714622] CS: 0010 DS: ES: CR0: 80050033 [ 10.714623] CR2: 563278766000 CR3: 0002be7a4002 CR4: 003606f0 [ 10.714623] Call Trace: [ 10.714627] rtw_pci_link_ps+0x4e/0x90 [rtwpci] [ 10.714630] ? _raw_spin_unlock_bh+0x1e/0x20 [ 10.714637] rtw_leave_ips+0x1f/0x80 [rtw88] [ 10.714640] rtw_ops_config+0xa3/0xe0 [rtw88] [ 10.714658] ieee80211_hw_config+0x95/0x390 [mac80211] [ 10.714669] ieee80211_recalc_idle+0x27/0x30 [mac80211] [ 10.714679] __ieee80211_start_scan+0x334/0x750 [mac80211] [ 10.714688] ieee80211_request_scan+0x30/0x50 [mac80211] [ 10.714699] ieee80211_scan+0x5c/0xa0 [mac80211] [ 10.714719] nl80211_trigger_scan+0x59a/0x6c0 [cfg80211] [ 10.714722] genl_rcv_msg+0x1a8/0x470 [ 10.714724] ? ep_poll_callback+0x2a0/0x2c0 [ 10.714725] ? genl_family_rcv_msg_attrs_parse+0x100/0x100 [ 10.714726] netlink_rcv_skb+0x50/0x120 [ 10.714728] genl_rcv+0x29/0x40 [ 10.714729] netlink_unicast+0x1a8/0x250 [ 10.714730] netlink_sendmsg+0x233/0x460 [ 10.714739] ? _copy_from_user+0x31/0x60 [ 10.714750] sock_sendmsg+0x65/0x70 [ 10.714751] sys_sendmsg+0x212/0x280 [ 10.714752] ? copy_msghdr_from_user+0x5c/0x90 [ 10.714755] ? __check_object_size+0x4d/0x150 [ 10.714756] ___sys_sendmsg+0x81/0xc0 [ 10.714757] ? __check_object_size+0x4d/0x150 [ 10.714759] ? unix_ioctl+0x99/0x180 [ 10.714760] ? sock_getsockopt+0x198/0xc04 [ 10.714761] ? sock_do_ioctl+0x47/0x140 [ 10.714763] ? __cgroup_bpf_run_filter_setsockopt+0xae/0x2c0 [ 10.714765] ? _cond_resched+0x19/0x30 [ 10.714767] ? aa_sk_perm+0x43/0x1b0 [ 10.714768] __sys_sendmsg+0x5c/0xa0 [ 10.714770] __x64_sys_sendmsg+0x1f/0x30 [ 10.714772] do_syscall_64+0x57/0x1b0 [ 10.714773] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 10.714774] RIP: 0033:0x7fbcedffb5b7 [ 10.714775] Code: 64 89 02 48 c7 c0 ff ff ff ff eb bb 0f 1f 80 00 00 00 00 f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 2e 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 51 c3 48 83 ec 28 89 54 24 1c 48 89 74 24 10 [ 10.714776] RSP: 002b:7fff88e22288 EFLAGS: 0246 ORIG_RAX: 002e [ 10.714777] RAX: ffda RBX: 5632787355d0 RCX: 7fbcedffb5b7 [ 10.714777] RDX: RSI: 7fff88e222c0 RDI: 0006 [ 10.714778] RBP: 563278761380 R08: 0004 R09: 563278761380 [ 10.714778] R10: 7fff88e22394 R11: 0246 R12: 5632787354e0 [ 10.714779] R13: 7fff88e222c0 R14: 7fff88e22394 R15: 563278766710 [ 10.714780] ---[ end trace f00c16109236af6f ]--- [ 10.714782] rtw_pci :3a:00.0: failed to read ASPM, ret=-5 Device
[Kernel-packages] [Bug 1874444] Re: Bionic ubuntu ethtool doesn't check ring parameters boundaries
This can't be fixed in ethtool, it has to be fixed in the kernel.
** Package changed: ethtool (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/187
Title:
Bionic ubuntu ethtool doesn't check ring parameters boundaries
Status in linux package in Ubuntu:
New
Bug description:
Upstream linux kernel implemented ring parameter boundaries check in commit:
37e2d99b59c4 ("ethtool: Ensure new ring parameters are within bounds during
SRINGPARAM")
(see link
https://patchwork.ozlabs.org/project/netdev/patch/1515420026-11970-2
-git-send-email-tar...@mellanox.com/)
Due to this commit, the community doesn't allow ring parameter
boundary checks in driver code.
The Bionic ubuntu kernel does not include this patch. And some network
drivers rely on this patch for
boundary checking of ring params.
This causes bugs in case a ringparam was given an illegal value.
Reproduction steps in AWS:
1. Create new c5.4xlarge instance with the ubuntu 18.04 official ami (uses
the ENA network driver) and update to latest kernel using apt-get dist-upgrade
and reboot for the new kernel to load.
2. Run ethtool -g ens5
output:
Ring parameters for ens5:
Pre-set maximums:
RX: 16384
RX Mini: 0
RX Jumbo: 0
TX: 1024
Current hardware settings:
RX: 1024
RX Mini: 0
RX Jumbo: 0
TX: 1024
3. Change the tx ring size to a legal number within boundaries - works!
4. Change the tx ring size to an illegal number such as 2048 with the command
- sudo ethtool -G ens5 tx 2048.
Expected behavior - operation not allowed
Actual behavior - causes a crash of the driver since boundaries are not
checked by ethtool.
Proposed fix - include the above commit 37e2d99b59c4 ("ethtool: Ensure
new ring parameters are within bounds during SRINGPARAM") in bionic
(and probably other ubuntu releases as well)
More data about the machine where the bug occured:
ubuntu@ip-172-31-80-28:~/bionic$ lsb_release -rd
Description: Ubuntu 18.04.4 LTS
Release: 18.04
ubuntu@ip-172-31-80-28:~/bionic$ uname -r
4.15.0-1065-aws
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/187/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874444] [NEW] Bionic ubuntu ethtool doesn't check ring parameters boundaries
You have been subscribed to a public bug:
Upstream linux kernel implemented ring parameter boundaries check in commit:
37e2d99b59c4 ("ethtool: Ensure new ring parameters are within bounds during
SRINGPARAM")
(see link
https://patchwork.ozlabs.org/project/netdev/patch/1515420026-11970-2
-git-send-email-tar...@mellanox.com/)
Due to this commit, the community doesn't allow ring parameter boundary
checks in driver code.
The Bionic ubuntu kernel does not include this patch. And some network drivers
rely on this patch for
boundary checking of ring params.
This causes bugs in case a ringparam was given an illegal value.
Reproduction steps in AWS:
1. Create new c5.4xlarge instance with the ubuntu 18.04 official ami (uses the
ENA network driver) and update to latest kernel using apt-get dist-upgrade and
reboot for the new kernel to load.
2. Run ethtool -g ens5
output:
Ring parameters for ens5:
Pre-set maximums:
RX: 16384
RX Mini:0
RX Jumbo: 0
TX: 1024
Current hardware settings:
RX: 1024
RX Mini:0
RX Jumbo: 0
TX: 1024
3. Change the tx ring size to a legal number within boundaries - works!
4. Change the tx ring size to an illegal number such as 2048 with the command -
sudo ethtool -G ens5 tx 2048.
Expected behavior - operation not allowed
Actual behavior - causes a crash of the driver since boundaries are not checked
by ethtool.
Proposed fix - include the above commit 37e2d99b59c4 ("ethtool: Ensure
new ring parameters are within bounds during SRINGPARAM") in bionic (and
probably other ubuntu releases as well)
More data about the machine where the bug occured:
ubuntu@ip-172-31-80-28:~/bionic$ lsb_release -rd
Description:Ubuntu 18.04.4 LTS
Release:18.04
ubuntu@ip-172-31-80-28:~/bionic$ uname -r
4.15.0-1065-aws
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: bot-comment
--
Bionic ubuntu ethtool doesn't check ring parameters boundaries
https://bugs.launchpad.net/bugs/187
You received this bug notification because you are a member of Kernel Packages,
which is subscribed to linux in Ubuntu.
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874503] [NEW] Mellanox Check For Write Combining Support
Public bug reported: Microsoft and Mellanox would like to request the following two commits in the releases that run on Azure: 3f89b01f4bba IB/mlx5: Align usage of QP1 create flags with rest of mlx5 defines 11f552e21755 IB/mlx5: Test write combining support These commits landed in mainline as of v5.5-rc1. These commits will improved network performance of RDMA out of the VF when WC can be used. The highest benefit is to RDMA and DPDK, but UCX should also see improved latency. The Mellanox driver uses WC to optimize posting work to the HCA, and getting this wrong in either direction can cause a significant performance loss. These patches prevent the possible performance loss. ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1874503 Title: Mellanox Check For Write Combining Support Status in linux-azure package in Ubuntu: New Bug description: Microsoft and Mellanox would like to request the following two commits in the releases that run on Azure: 3f89b01f4bba IB/mlx5: Align usage of QP1 create flags with rest of mlx5 defines 11f552e21755 IB/mlx5: Test write combining support These commits landed in mainline as of v5.5-rc1. These commits will improved network performance of RDMA out of the VF when WC can be used. The highest benefit is to RDMA and DPDK, but UCX should also see improved latency. The Mellanox driver uses WC to optimize posting work to the HCA, and getting this wrong in either direction can cause a significant performance loss. These patches prevent the possible performance loss. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1874503/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874502] Re: Bionic update: upstream stable patchset 2020-04-23
** Description changed:
+ SRU Justification
- SRU Justification
+ Impact:
+ The upstream process for stable tree updates is quite similar
+ in scope to the Ubuntu SRU process, e.g., each patch has to
+ demonstrably fix a bug, and each patch is vetted by upstream
+ by originating either directly from a mainline/stable Linux tree or
+ a minimally backported form of that patch. The following upstream
+ stable patches should be included in the Ubuntu kernel:
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The following upstream
-stable patches should be included in the Ubuntu kernel:
+ upstream stable patchset 2020-04-23
-upstream stable patchset 2020-04-23
-from git://git.kernel.org/
+ Ported from the following upstream stable releases:
+v4.19.116
+
+ from git://git.kernel.org/
+
+ ARM: dts: sun8i-a83t-tbs-a711: HM5065 doesn't like such a high voltage
+ bus: sunxi-rsb: Return correct data when mixing 16-bit and 8-bit reads
+ net: vxge: fix wrong __VA_ARGS__ usage
+ hinic: fix a bug of waitting for IO stopped
+ hinic: fix wrong para of wait_for_completion_timeout
+ cxgb4/ptp: pass the sign of offset delta in FW CMD
+ qlcnic: Fix bad kzalloc null test
+ i2c: st: fix missing struct parameter description
+ firmware: arm_sdei: fix double-lock on hibernate with shared events
+ null_blk: Fix the null_add_dev() error path
+ null_blk: Handle null_add_dev() failures properly
+ null_blk: fix spurious IO errors after failed past-wp access
+ xhci: bail out early if driver can't accress host in resume
+ x86: Don't let pgprot_modify() change the page encryption bit
+ block: keep bdi->io_pages in sync with max_sectors_kb for stacked devices
+ irqchip/versatile-fpga: Handle chained IRQs properly
+ sched: Avoid scale real weight down to zero
+ selftests/x86/ptrace_syscall_32: Fix no-vDSO segfault
+ PCI/switchtec: Fix init_completion race condition with poll_wait()
+ libata: Remove extra scsi_host_put() in ata_scsi_add_hosts()
+ gfs2: Don't demote a glock until its revokes are written
+ x86/boot: Use unsigned comparison for addresses
+ efi/x86: Ignore the memory attributes table on i386
+ genirq/irqdomain: Check pointer in irq_domain_alloc_irqs_hierarchy()
+ block: Fix use-after-free issue accessing struct io_cq
+ usb: dwc3: core: add support for disabling SS instances in park mode
+ irqchip/gic-v4: Provide irq_retrigger to avoid circular locking dependency
+ md: check arrays is suspended in mddev_detach before call quiesce operations
+ locking/lockdep: Avoid recursion in lockdep_count_{for,back}ward_deps()
+ block, bfq: fix use-after-free in bfq_idle_slice_timer_body
+ btrfs: qgroup: ensure qgroup_rescan_running is only set when the worker is at
least queued
+ btrfs: remove a BUG_ON() from merge_reloc_roots()
+ btrfs: track reloc roots based on their commit root bytenr
+ uapi: rename ext2_swab() to swab() and share globally in swab.h
+ slub: improve bit diffusion for freelist ptr obfuscation
+ ASoC: fix regwmask
+ ASoC: dapm: connect virtual mux with default value
+ ASoC: dpcm: allow start or stop during pause for backend
+ ASoC: topology: use name_prefix for new kcontrol
+ usb: gadget: f_fs: Fix use after free issue as part of queue failure
+ usb: gadget: composite: Inform controller driver of self-powered
+ ALSA: usb-audio: Add mixer workaround for TRX40 and co
+ ALSA: hda: Add driver blacklist
+ ALSA: hda: Fix potential access overflow in beep helper
+ ALSA: ice1724: Fix invalid access for enumerated ctl items
+ ALSA: pcm: oss: Fix regression by buffer overflow fix
+ ALSA: doc: Document PC Beep Hidden Register on Realtek ALC256
+ ALSA: hda/realtek - Set principled PC Beep configuration for ALC256
+ ALSA: hda/realtek - Remove now-unnecessary XPS 13 headphone noise fixups
+ ALSA: hda/realtek - Add quirk for MSI GL63
+ media: ti-vpe: cal: fix disable_irqs to only the intended target
+ acpi/x86: ignore unspecified bit positions in the ACPI global lock field
+ thermal: devfreq_cooling: inline all stubs for CONFIG_DEVFREQ_THERMAL=n
+ nvme-fc: Revert "add module to ops template to allow module references"
+ nvme: Treat discovery subsystems as unique subsystems
+ PCI/ASPM: Clear the correct bits when enabling L1 substates
+ PCI: Add boot interrupt quirk mechanism for Xeon chipsets
+ PCI: endpoint: Fix for concurrent memory allocation in OB address region
+ irqchip/versatile-fpga: Apply clear-mask earlier
+ pstore: pstore_ftrace_seq_next should increase position index
+ MIPS/tlbex: Fix LDDIR usage in setup_pw() for Loongson-3
+ MIPS: OCTEON: irq: Fix potential NULL pointer
[Kernel-packages] [Bug 1806681]
HP ProBook 455 G3 (BIOS Version: N80 Ver. 01.45) [ 18.373200] hp_wmi: query 0x4 returned error 0x5 [ 18.377701] hp_wmi: query 0x4 returned error 0x5 [ 18.385171] hp_wmi: query 0xd returned error 0x5 [ 18.397105] hp_wmi: query 0x1b returned error 0x5 Linux 5.4.0-26-generic x86_64 (*buntu 20.04 LTS) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1806681 Title: hp_wmi: query 0xd returned error 0x5 Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hello, dmesg: [ 18.296366] hp_wmi: query 0xd returned error 0x5 Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-4.18.0-11-generic 4.18.0-11.12 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 2739 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Dec 4 09:05:38 2018 HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57 InstallationDate: Installed on 2018-12-02 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-11-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.176 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2018-12-02 (1 days ago) dmi.bios.date: 06/14/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.19 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1806681/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874502] [NEW] Bionic update: upstream stable patchset 2020-04-23
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2020-04-23 from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Bionic) Importance: Undecided Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874502 Title: Bionic update: upstream stable patchset 2020-04-23 Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2020-04-23 from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874502/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1872311] Re: Brightness hotkeys not working on Lenovo S740
It may worth a shot to ask on Lenovo's forum (https://forums.lenovo.com/t5/English-Community/ct-p/Community-EN). Perhaps they will forward this to developers who can take a look and release a fix for everybody. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1872311 Title: Brightness hotkeys not working on Lenovo S740 Status in linux package in Ubuntu: Confirmed Bug description: Brightness hotkeys (Fn + F11 for decrease and Fn + F12 for increase) do not work on Ubuntu 20.04 and Lenovo S740 laptop. The brightness hotkeys did not work on 19.10 either. I followed the guide here: https://wiki.ubuntu.com/Hotkeys/Troubleshooting In "Step-by-step Troubleshooting", none of the steps (1-7) did produce any reaction to brightness change key combinations. However, I am able to change the laptop screen brightness through the brightness applet. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-21-generic 5.4.0-21.25 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: elias 1447 F pulseaudio /dev/snd/controlC0: elias 1447 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 12 16:12:01 2020 InstallationDate: Installed on 2019-11-19 (144 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 81RS ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=101c7da4-860d-4496-ae06-d98699795f9a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-04-04 (7 days ago) dmi.bios.date: 03/10/2020 dmi.bios.vendor: LENOVO dmi.bios.version: BYCN33WW 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 Yoga S740-14IIL dmi.modalias: dmi:bvnLENOVO:bvrBYCN33WW:bd03/10/2020:svnLENOVO:pn81RS:pvrLenovoYogaS740-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYogaS740-14IIL: dmi.product.family: Yoga S740-14IIL dmi.product.name: 81RS dmi.product.sku: LENOVO_MT_81RS_BU_idea_FM_Yoga S740-14IIL dmi.product.version: Lenovo Yoga S740-14IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872311/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874481] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874481 Title: Can not use Wifi, Wifi on/off automaticallly and also airplane mode automatuc on and i can not disable it. It saying disable switch from adapter. Status in linux package in Ubuntu: Confirmed Bug description: My network adapter is RT3290 Wireless 802.11n 1T/1R PCIe vendor: Ralink corp. Also it shows no adapter found for bluetooth. 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 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rishiawsm 1789 F pulseaudio /dev/snd/controlC0: rishiawsm 1789 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 23 21:24:27 2020 InstallationDate: Installed on 2019-12-28 (117 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Lsusb: Bus 001 Device 003: ID 04f2:b40e Chicony Electronics Co., Ltd HP Truevision HD camera Bus 001 Device 002: ID 8087:8000 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard HP 15 Notebook PC ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=57275fbf-36f6-4902-b56b-5d9645019f60 ro quiet splash vt.handoff=7 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-23 (0 days ago) dmi.bios.date: 05/21/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.18 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2212 dmi.board.vendor: Hewlett-Packard dmi.board.version: 86.28 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.18:bd05/21/2014:svnHewlett-Packard:pnHP15NotebookPC:pvr097710405F0610180:rvnHewlett-Packard:rn2212:rvr86.28:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP 15 Notebook PC dmi.product.sku: G8D32PA#ACJ dmi.product.version: 097710405F0610180 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874481/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1873083] Re: Lenovo Yoga C940 frequently does thermal shutdown
Hi, no, its indoors while charging. Could it be a hardware issue? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1873083 Title: Lenovo Yoga C940 frequently does thermal shutdown Status in linux package in Ubuntu: Incomplete Status in thermald package in Ubuntu: Confirmed Bug description: On a bit higher load and especially if Laptop is charging, very often Kernel does an emergency thermal shutdown. thermal thermal_zone3: critical temperature reached (80 C), shutting down It says 80 C, but sensors command shows that temperatures hovering close to 100C before the shutdown happens. dmesg is often also full of these (for each core): mce: CPU2: Core temperature above threshold, cpu clock throttled (total events = 246766) When I boot to Windows, it seems that CPU is throttled more aggressively on load and thermal shutdown doesn't happen with a similar load, but CPU frequencies drop to 1600 range, while in Ubuntu they are 2800 range. I would rather have more throttling that computer shutting down randomly without the ability to save work. Is there a workaround? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-21-generic 5.4.0-21.25 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: anton 1874 F pulseaudio /dev/snd/pcmC0D0p: anton 1874 F...m pulseaudio /dev/snd/pcmC0D6c: anton 1874 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Apr 15 23:54:21 2020 InstallationDate: Installed on 2019-11-29 (137 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 81Q9 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=24af2874-e109-44f9-a5b9-8a9ce34b3f0f ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-04-04 (11 days ago) dmi.bios.date: 01/09/2020 dmi.bios.vendor: LENOVO dmi.bios.version: AUCN54WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga C940-14IIL dmi.modalias: dmi:bvnLENOVO:bvrAUCN54WW:bd01/09/2020:svnLENOVO:pn81Q9:pvrLenovoYogaC940-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct31:cvrLenovoYogaC940-14IIL: dmi.product.family: Yoga C940-14IIL dmi.product.name: 81Q9 dmi.product.sku: LENOVO_MT_81Q9_BU_idea_FM_Yoga C940-14IIL dmi.product.version: Lenovo Yoga C940-14IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873083/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1872311] Re: Brightness hotkeys not working on Lenovo S740
Thanks, "sudo showkey -s" does not show anything for the brightness key combination. Neither do the interrupts increase when the brightness key combination is pressed. So I assume this cannot be fixed from the software side. The brightness keys are working on Windows. However, the laptop is quite new so maybe the support just isn't there yet. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1872311 Title: Brightness hotkeys not working on Lenovo S740 Status in linux package in Ubuntu: Confirmed Bug description: Brightness hotkeys (Fn + F11 for decrease and Fn + F12 for increase) do not work on Ubuntu 20.04 and Lenovo S740 laptop. The brightness hotkeys did not work on 19.10 either. I followed the guide here: https://wiki.ubuntu.com/Hotkeys/Troubleshooting In "Step-by-step Troubleshooting", none of the steps (1-7) did produce any reaction to brightness change key combinations. However, I am able to change the laptop screen brightness through the brightness applet. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-21-generic 5.4.0-21.25 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: elias 1447 F pulseaudio /dev/snd/controlC0: elias 1447 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 12 16:12:01 2020 InstallationDate: Installed on 2019-11-19 (144 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 81RS ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=101c7da4-860d-4496-ae06-d98699795f9a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-04-04 (7 days ago) dmi.bios.date: 03/10/2020 dmi.bios.vendor: LENOVO dmi.bios.version: BYCN33WW 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 Yoga S740-14IIL dmi.modalias: dmi:bvnLENOVO:bvrBYCN33WW:bd03/10/2020:svnLENOVO:pn81RS:pvrLenovoYogaS740-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYogaS740-14IIL: dmi.product.family: Yoga S740-14IIL dmi.product.name: 81RS dmi.product.sku: LENOVO_MT_81RS_BU_idea_FM_Yoga S740-14IIL dmi.product.version: Lenovo Yoga S740-14IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872311/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874481] Re: Can not use Wifi, Wifi on/off automaticallly and also airplane mode automatuc on and i can not disable it. It saying disable switch from adapter.
** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874481 Title: Can not use Wifi, Wifi on/off automaticallly and also airplane mode automatuc on and i can not disable it. It saying disable switch from adapter. Status in linux package in Ubuntu: New Bug description: My network adapter is RT3290 Wireless 802.11n 1T/1R PCIe vendor: Ralink corp. Also it shows no adapter found for bluetooth. 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 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rishiawsm 1789 F pulseaudio /dev/snd/controlC0: rishiawsm 1789 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 23 21:24:27 2020 InstallationDate: Installed on 2019-12-28 (117 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Lsusb: Bus 001 Device 003: ID 04f2:b40e Chicony Electronics Co., Ltd HP Truevision HD camera Bus 001 Device 002: ID 8087:8000 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard HP 15 Notebook PC ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=57275fbf-36f6-4902-b56b-5d9645019f60 ro quiet splash vt.handoff=7 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-23 (0 days ago) dmi.bios.date: 05/21/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.18 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2212 dmi.board.vendor: Hewlett-Packard dmi.board.version: 86.28 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.18:bd05/21/2014:svnHewlett-Packard:pnHP15NotebookPC:pvr097710405F0610180:rvnHewlett-Packard:rn2212:rvr86.28:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP 15 Notebook PC dmi.product.sku: G8D32PA#ACJ dmi.product.version: 097710405F0610180 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874481/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874481] [NEW] Can not use Wifi, Wifi on/off automaticallly and also airplane mode automatuc on and i can not disable it. It saying disable switch from adapter.
You have been subscribed to a public bug: My network adapter is RT3290 Wireless 802.11n 1T/1R PCIe vendor: Ralink corp. Also it shows no adapter found for bluetooth. 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 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rishiawsm 1789 F pulseaudio /dev/snd/controlC0: rishiawsm 1789 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 23 21:24:27 2020 InstallationDate: Installed on 2019-12-28 (117 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Lsusb: Bus 001 Device 003: ID 04f2:b40e Chicony Electronics Co., Ltd HP Truevision HD camera Bus 001 Device 002: ID 8087:8000 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard HP 15 Notebook PC ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=57275fbf-36f6-4902-b56b-5d9645019f60 ro quiet splash vt.handoff=7 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-23 (0 days ago) dmi.bios.date: 05/21/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.18 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2212 dmi.board.vendor: Hewlett-Packard dmi.board.version: 86.28 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.18:bd05/21/2014:svnHewlett-Packard:pnHP15NotebookPC:pvr097710405F0610180:rvnHewlett-Packard:rn2212:rvr86.28:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP 15 Notebook PC dmi.product.sku: G8D32PA#ACJ dmi.product.version: 097710405F0610180 dmi.sys.vendor: Hewlett-Packard ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- Can not use Wifi, Wifi on/off automaticallly and also airplane mode automatuc on and i can not disable it. It saying disable switch from adapter. https://bugs.launchpad.net/bugs/1874481 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1872001] Re: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0
Right, comment #57 is missing the non-generic headers package (which the -generic package depends on). The kernel is installable but makes dpkg sad. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1872001 Title: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0 Status in linux package in Ubuntu: Confirmed Status in linux source package in Eoan: In Progress Bug description: Hi, Since update to HWE kernel 5.3.0-46-generic I am experiencing frequent (every couple of minutes) GPU hangs and reset manifesting as 2-3 seconds freezes of the GUI (other than the mouse pointer). No particular triggers identified although have Chrome / Chromium running with Hardware Acceleration enabled does appear to increase the frequency. I have seen incidences of these hangs in jounralctl output using previous kernels in the 5.3.0-xx series but they were very infrequent (one or twice in a week of daily usage) System Info steve@steve-Inspiron-5580:~$ inxi -SCGxxxz System:Host: steve-Inspiron-5580 Kernel: 5.3.0-46-generic x86_64 bits: 64 compiler: gcc v: 7.5.0 Desktop: Cinnamon 4.4.8 wm: muffin 4.4.2 dm: LightDM 1.26.0 Distro: Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic CPU: Topology: Quad Core model: Intel Core i5-8265U bits: 64 type: MT MCP arch: Kaby Lake rev: B L2 cache: 6144 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 28800 Speed: 1173 MHz min/max: 400/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 Graphics: Device-1: Intel vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:3ea0 Display: x11 server: X.Org 1.20.5 driver: modesetting unloaded: fbdev,vesa resolution: 1920x1080~60Hz OpenGL: renderer: Mesa DRI Intel UHD Graphics (Whiskey Lake 3x8 GT2) v: 4.5 Mesa 19.2.8 compat-v: 3.0 direct render: Yes steve@steve-Inspiron-5580:~$ journalctl -b | grep i915 Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: vgaarb: deactivate vga console Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem Apr 10 06:15:17 steve-Inspiron-5580 kernel: [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4) Apr 10 06:15:17 steve-Inspiron-5580 kernel: [drm] Initialized i915 1.6.0 20190619 for :00:02.0 on minor 0 Apr 10 06:15:17 steve-Inspiron-5580 kernel: fbcon: i915drmfb (fb0) is primary device Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: fb0: i915drmfb frame buffer device Apr 10 06:15:17 steve-Inspiron-5580 kernel: snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) Apr 10 06:16:28 steve-Inspiron-5580 kernel: i915 :00:02.0: GPU HANG: ecode 9:0:0x, hang on rcs0 Apr 10 06:16:28 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:31:46 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:37:48 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:40:46 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 I note another user has reported similar issues on the same kernel at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861395/comments/52 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: steve 3920 F pulseaudio /dev/snd/pcmC0D0p: steve 3920 F...m pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.3 HibernationDevice: RESUME=none InstallationDate: Installed on 2019-12-27 (104 days ago) InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213 MachineType: Dell Inc. Inspiron 5580 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic root=UUID=b0eaa5bb-0276-42d4-938f-ee6ce1627906 ro usb_storage.quirks=0bc2:2320: quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-46-generic N/A linux-backports-modules-5.3.0-46-generic N/A linux-firmware1.173.17 Tags: tricia Uname: Linux 5.3.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 07/02/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 0K0DFT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10
[Kernel-packages] [Bug 1874465] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874465 Title: dummy output ubuntu 20.04 LTS dell inspiron 3420 Status in linux package in Ubuntu: Confirmed Bug description: in sound settings there is only dummy output, everything worked until April, 21 2020 when updated 18.04 LTS to 20.04 LTS via terminal. Description: Ubuntu 20.04 LTS Release: 20.04 alsa-base: Installed: 1.0.25+dfsg-0ubuntu5 Candidate: 1.0.25+dfsg-0ubuntu5 Version table: *** 1.0.25+dfsg-0ubuntu5 500 500 http://br.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://br.archive.ubuntu.com/ubuntu focal/main i386 Packages 100 /var/lib/dpkg/status pavucontrol: Installed: 4.0-1build1 Candidate: 4.0-1build1 Version table: *** 4.0-1build1 500 500 http://br.archive.ubuntu.com/ubuntu focal/universe amd64 Packages 100 /var/lib/dpkg/status 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 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ploosh 1949 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 23 11:35:40 2020 InstallationDate: Installed on 2019-10-06 (199 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Dell Inc. Inspiron 3420 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=ec870298-2798-4d1b-a6d2-6118c2078d5e ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-04-22 (1 days ago) dmi.bios.date: 11/04/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 04XGDT dmi.board.vendor: Dell Inc. dmi.board.version: A11 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA11:bd11/04/2013:svnDellInc.:pnInspiron3420:pvrNotSpecified:rvnDellInc.:rn04XGDT:rvrA11:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3420 dmi.product.sku: To be filled by O.E.M. dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874465/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1872964] Re: Reliable crash in lowlatency kernel with LXD
My attempts to reproduce this have been unsuccessful. Can you give me an idea of how many containers you're running on the machine and what kind of workloads they are running? ** Changed in: linux-signed (Ubuntu) Status: New => Confirmed ** Changed in: linux-signed (Ubuntu) Assignee: (unassigned) => Seth Forshee (sforshee) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1872964 Title: Reliable crash in lowlatency kernel with LXD Status in linux-signed package in Ubuntu: Confirmed Bug description: Hello, I am able to crash 5.4.0-21-lowlatency running LXD. This machine in an Intel NUC, part of a three-member LXD cluster. The other machines do not show this crash and they are not running the lowlatency kernel, but that might be incidental. I will swap out the generic kernel for a while to see if the behaviour continues there. Here is the crash: [ 3222.385724] [ cut here ] [ 3222.385732] WARNING: CPU: 1 PID: 59852 at kernel/rcu/tree_plugin.h:293 rcu_note_context_switch+0x46/0x460 [ 3222.385733] Modules linked in: binfmt_misc veth nft_masq nft_chain_nat vxlan ip6_udp_tunnel udp_tunnel dummy bridge stp llc ebtable_filter ebtables ip6table_raw ip6table_mangle ip6table_nat ip6table_filter ip6_tables iptable_raw iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_filter bpfilter nf_tables nfnetlink unix_diag ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs pps_ldisc zfs(PO) zunicode(PO) zavl(PO) icp(PO) nls_iso8859_1 zcommon(PO) znvpair(PO) spl(O) dm_multipath zlua(PO) scsi_dh_rdac scsi_dh_emc scsi_dh_alua snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio intel_rapl_msr snd_hda_intel mei_hdcp snd_intel_nhlt snd_hda_codec snd_hda_core snd_hwdep intel_rapl_common x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_pcm kvm snd_timer intel_cstate mei_me intel_rapl_perf mei snd soundcore mac_hid acpi_pad sch_fq_codel ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor [ 3222.385779] async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_pclmul crc32_pclmul ghash_clmulni_intel i915 aesni_intel i2c_algo_bit crypto_simd cryptd glue_helper drm_kms_helper syscopyarea sysfillrect sysimgblt e1000e i2c_i801 fb_sys_fops ahci drm libahci lpc_ich video [ 3222.385795] CPU: 1 PID: 59852 Comm: systemd-resolve Tainted: P O 5.4.0-21-lowlatency #25-Ubuntu [ 3222.385796] Hardware name: /NUC5i5MYBE, BIOS MYBDWi5v.86A.0034.2017.0116.2148 01/16/2017 [ 3222.385801] RIP: 0010:rcu_note_context_switch+0x46/0x460 [ 3222.385803] Code: 54 53 48 c7 c3 80 ba 02 00 65 48 03 1d 8b 57 ce 6d 0f 1f 44 00 00 41 8b 85 80 07 00 00 45 84 f6 0f 85 55 02 00 00 85 c0 7e 0c <0f> 0b 41 80 bd 84 07 00 00 00 74 33 4c 89 ef e8 36 fb ff ff 65 66 [ 3222.385804] RSP: 0018:a7bf48e3bcf8 EFLAGS: 00010002 [ 3222.385806] RAX: 0001 RBX: 9817c5caba80 RCX: 0001 [ 3222.385807] RDX: RSI: 92ce6379 RDI: [ 3222.385808] RBP: a7bf48e3bd20 R08: R09: [ 3222.385808] R10: R11: R12: 9817c5caad00 [ 3222.385809] R13: 9816c39ecd00 R14: R15: 0002ad00 [ 3222.385811] FS: 7f9c0f530940() GS:9817c5c8() knlGS: [ 3222.385812] CS: 0010 DS: ES: CR0: 80050033 [ 3222.385812] CR2: 55988bb4b080 CR3: 0003b5e9a005 CR4: 003606e0 [ 3222.385813] DR0: DR1: DR2: [ 3222.385814] DR3: DR6: fffe0ff0 DR7: 0400 [ 3222.385815] Call Trace: [ 3222.385823] __schedule+0x9d/0x750 [ 3222.385826] ? ___sys_sendmsg+0x95/0xd0 [ 3222.385829] schedule+0x49/0xd0 [ 3222.385831] schedule_hrtimeout_range_clock+0xf9/0x110 [ 3222.385834] ? __seccomp_filter+0x85/0x6b0 [ 3222.385837] schedule_hrtimeout_range+0x13/0x20 [ 3222.385839] ep_poll+0x3c8/0x410 [ 3222.385843] ? wake_up_q+0x70/0x70 [ 3222.385845] do_epoll_wait+0xb8/0xd0 [ 3222.385847] __x64_sys_epoll_wait+0x1e/0x30 [ 3222.385850] do_syscall_64+0x57/0x190 [ 3222.385852] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 3222.385854] RIP: 0033:0x7f9c0f04eb77 [ 3222.385856] Code: 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 8d 05 91 ed 2c 00 41 89 ca 8b 00 85 c0 75 18 b8 e8 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 61 f3 c3 0f 1f 80 00 00 00 00 41 55 41 54 41 [ 3222.385857] RSP: 002b:7ffc6fd86d88 EFLAGS: 0246 ORIG_RAX: 00e8 [ 3222.385859] RAX: ffda RBX: 55988d0ad3c0 RCX: 7f9c0f04eb77 [ 3222.385859] RDX: 000e RSI: 7ffc6fd86d90 RDI: 0004 [ 3222.385861]
[Kernel-packages] [Bug 1808418] Re: Thinkpad T430u won't boot without noapic workaround
> Maybe the bcmwl-kernel-source package just isn't compatible with 5.7 yet? I see now in the logs that's the case: Building module: cleaning build area... make -j4 KERNELRELEASE=5.7.0-050700rc2-generic -C /lib/modules/5.7.0-050700rc2-generic/build M=/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build(bad exit status: 2) ERROR (dkms apport): kernel package linux-headers-5.7.0-050700rc2-generic is not supported Error! Bad return status for module build on kernel: 5.7.0-050700rc2-generic (x86_64) But I won't say anything more about that here since it's a separate issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1808418 Title: Thinkpad T430u won't boot without noapic workaround Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: New Bug description: I've used Ubuntu on this specific machine for years without problems, but starting with the 4.13 kernel that came with the 17.10 HWE and continuing into 18.04 kernels my computer would no longer boot, hanging at various screens: - A blank screen with a flashing cursor - A screen with this message: Loading Linux 4.13.0.36-generic ... Loading initial ramdisk ... - A screen with kernel messages, ending in: APCI: EC: interrupt blocked I've encountered the bug in a number of kernels, including: - 4.13.0-32 - 4.13.0-36 - 4.13.0-37 - 4.15.0-24 - 4.15.0-34 - 4.15.0-36 - 4.15.0-38 - 4.15.0-42 - 4.20.0-rc7 I was able to work around the issue by adding noapic to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default grub, e.g.: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash noapic" I'm not entirely sure of the consequences of this workaround, but one thing I've noticed is significantly reduced battery life. This bug seems very similar to what's described here for the Thinkpad E485/E585: https://evilazrael.de/node/401 I'll attach screenshots of various times I've encountered this bug over the last year. $ lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 $ apt-cache policy linux-image-4.15.0-42-generic linux-image-4.15.0-42-generic: Installed: 4.15.0-42.45 Candidate: 4.15.0-42.45 Version table: *** 4.15.0-42.45 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-42-generic 4.15.0-42.45 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bryan 2349 F pulseaudio CurrentDesktop: XFCE Date: Thu Dec 13 15:31:15 2018 HibernationDevice: RESUME=UUID=4afa8032-cfe5-45f4-a626-738ab33904ac InstallationDate: Installed on 2014-05-08 (1680 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: LENOVO 3351CTO ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID=cffbc87d-956b-4986-94df-b3b64ae5237f ro quiet splash noapic vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-42-generic N/A linux-backports-modules-4.15.0-42-generic N/A linux-firmware 1.173.2 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-07-12 (154 days ago) dmi.bios.date: 06/01/2018 dmi.bios.vendor: LENOVO dmi.bios.version: H6ETA0WW (2.18 ) dmi.board.asset.tag: Not Available dmi.board.name: 3351CTO dmi.board.vendor: LENOVO dmi.board.version: Win8 STD DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrH6ETA0WW(2.18):bd06/01/2018:svnLENOVO:pn3351CTO:pvrThinkPadT430u:rvnLENOVO:rn3351CTO:rvrWin8STDDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430u dmi.product.name: 3351CTO dmi.product.version: ThinkPad T430u dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808418/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874465] [NEW] dummy output ubuntu 20.04 LTS dell inspiron 3420
Public bug reported: in sound settings there is only dummy output, everything worked until April, 21 2020 when updated 18.04 LTS to 20.04 LTS via terminal. Description:Ubuntu 20.04 LTS Release:20.04 alsa-base: Installed: 1.0.25+dfsg-0ubuntu5 Candidate: 1.0.25+dfsg-0ubuntu5 Version table: *** 1.0.25+dfsg-0ubuntu5 500 500 http://br.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://br.archive.ubuntu.com/ubuntu focal/main i386 Packages 100 /var/lib/dpkg/status pavucontrol: Installed: 4.0-1build1 Candidate: 4.0-1build1 Version table: *** 4.0-1build1 500 500 http://br.archive.ubuntu.com/ubuntu focal/universe amd64 Packages 100 /var/lib/dpkg/status 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 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ploosh 1949 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 23 11:35:40 2020 InstallationDate: Installed on 2019-10-06 (199 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Dell Inc. Inspiron 3420 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=ec870298-2798-4d1b-a6d2-6118c2078d5e ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-04-22 (1 days ago) dmi.bios.date: 11/04/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 04XGDT dmi.board.vendor: Dell Inc. dmi.board.version: A11 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA11:bd11/04/2013:svnDellInc.:pnInspiron3420:pvrNotSpecified:rvnDellInc.:rn04XGDT:rvrA11:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3420 dmi.product.sku: To be filled by O.E.M. dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Description changed: in sound settings there is only dummy output, everything worked until April, 21 2020 when updated 18.04 LTS to 20.04 LTS via terminal. Description: Ubuntu 20.04 LTS Release: 20.04 alsa-base: - Installed: 1.0.25+dfsg-0ubuntu5 - Candidate: 1.0.25+dfsg-0ubuntu5 - Version table: - *** 1.0.25+dfsg-0ubuntu5 500 - 500 http://br.archive.ubuntu.com/ubuntu focal/main amd64 Packages - 500 http://br.archive.ubuntu.com/ubuntu focal/main i386 Packages - 100 /var/lib/dpkg/status + Installed: 1.0.25+dfsg-0ubuntu5 + Candidate: 1.0.25+dfsg-0ubuntu5 + Version table: + *** 1.0.25+dfsg-0ubuntu5 500 + 500 http://br.archive.ubuntu.com/ubuntu focal/main amd64 Packages + 500 http://br.archive.ubuntu.com/ubuntu focal/main i386 Packages + 100 /var/lib/dpkg/status pavucontrol: - Installed: 4.0-1build1 - Candidate: 4.0-1build1 - Version table: - *** 4.0-1build1 500 - 500 http://br.archive.ubuntu.com/ubuntu focal/universe amd64 Packages - 100 /var/lib/dpkg/status + Installed: 4.0-1build1 + Candidate: 4.0-1build1 + Version table: + *** 4.0-1build1 500 + 500 http://br.archive.ubuntu.com/ubuntu focal/universe amd64 Packages + 100 /var/lib/dpkg/status 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 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: ploosh 1949 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: ploosh 1949 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 23 11:35:40 2020 InstallationDate: Installed on 2019-10-06 (199 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Dell Inc. Inspiron 3420 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=ec870298-2798-4d1b-a6d2-6118c2078d5e ro quiet splash vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-5.4.0-26-generic N/A - linux-backports-modules-5.4.0-26-generic N/A - linux-firmware1.187 + linux-restricted-modules-5.4.0-26-generic N/A + linux-backports-modules-5.4.0-26-generic N/A + linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-04-22 (1 days ago)
[Kernel-packages] [Bug 1874286] Re: Add debian/rules targets to compile/run kernel selftests
** No longer affects: linux (Ubuntu Precise) ** No longer affects: linux (Ubuntu Trusty) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874286 Title: Add debian/rules targets to compile/run kernel selftests Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Eoan: In Progress Status in linux source package in Focal: In Progress Bug description: [Impact] When compiling and building the Ubuntu kernels, the kernel selftests located under 'tools/testing/selftests/' do not get compiled. Some of these testcases are used by our test infrastructure, which downloads the kernel source, compiles and run them. The problem with this approach is that patches applied to the testcases can break the compilation and this is detected only after the kernels are already released to -proposed. I am proposing that we add some simple debian/rules targets that will keep a list of the selftests that Ubuntu cares about, compile and run them. This could be plugged into our test build infrastructure in order to be able to detect such breaks. [Test Case] With these changes, one would be able to run the following to compile/run the selftests: # fakeroot debian/rules clean # fakeroot debian/rules compileselftests # fakeroot debian/rules runselftests [Regression Potential] None. This only adds new rules targets that will not break any existing targets. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874286/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
If you can't reproduce the big, then I will nuke my absolutely functional system and post output here. I see you have a 1080 Card, I have a 1070, mine is an HP OMEN from 2017. Will post here soon. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Invalid Status in gdm3 source package in Eoan: Confirmed Status in gnome-session source package in Eoan: Confirmed Status in nvidia-graphics-drivers-435 source package in Eoan: Confirmed Bug description: I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A67 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net
[Kernel-packages] [Bug 1349028] Re: getitimer returns it_value=0 erroneously
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Focal)
Importance: Medium
Assignee: Colin Ian King (colin-king)
Status: Fix Released
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Eoan)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Status: New => In Progress
** Changed in: linux (Ubuntu Bionic)
Status: New => In Progress
** Changed in: linux (Ubuntu Eoan)
Status: New => In Progress
** Changed in: linux (Ubuntu Eoan)
Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1349028
Title:
getitimer returns it_value=0 erroneously
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Trusty:
Fix Released
Status in linux source package in Utopic:
Fix Released
Status in linux source package in Xenial:
In Progress
Status in linux source package in Bionic:
In Progress
Status in linux source package in Eoan:
In Progress
Status in linux source package in Focal:
Fix Released
Bug description:
According to the 'getitimer()' man page: "The element it_value is set
to the amount of time remaining on the timer, or zero if the timer is
disabled. Similarly, it_interval is set to the reset value."
As such the following Perl program should never exit:
use Time::HiRes;
$SIG{VTALRM} = sub { };
Time::HiRes::setitimer(::HiRes::ITIMER_VIRTUAL, 0.5, 0.4);
while (1) {
my @t = Time::HiRes::getitimer(::HiRes::ITIMER_VIRTUAL);
exit 0 if $t[0] == 0;
}
and on linux-image 3.11.0-18-generic (and all other systems tested) it
loops forever but 3.13.0-32-generic it exits. Have not bisected
between those kernels, nor am I likely to be able to do so soon.
This Perl program shows the timer countdown:
use Time::HiRes;
my $r = [Time::HiRes::gettimeofday()];
sub display {
my ($desc) = @_;
my @t = Time::HiRes::getitimer(::HiRes::ITIMER_VIRTUAL);
my $i = Time::HiRes::tv_interval($r);
printf "%s: elasped=%.8f; time left=%.6f reset time=%.6f\n", $desc,
$i,@t;
}
$SIG{VTALRM} = sub {
display('VTALRM');
exit;
};
Time::HiRes::setitimer(::HiRes::ITIMER_VIRTUAL, 0.5, 0.4);
while (1) {
display('inloop');
}
on other (working) systems it gives:
inloop: elasped=1.65178400; time left=0.001000 reset time=0.401000
inloop: elasped=1.65184200; time left=0.001000 reset time=0.401000
inloop: elasped=1.65186800; time left=0.001000 reset time=0.401000
inloop: elasped=1.65192300; time left=0.001000 reset time=0.401000
inloop: elasped=1.65198100; time left=0.001000 reset time=0.401000
VTALRM: elasped=1.65209800; time left=0.40 reset time=0.401000
(end of file)
but on the 3.13.0-32-generic or later kernel I get:
inloop: elasped=0.54692100; time left=0.33 reset time=0.40
inloop: elasped=0.54692800; time left=0.26 reset time=0.40
inloop: elasped=0.54693500; time left=0.20 reset time=0.40
inloop: elasped=0.54694100; time left=0.13 reset time=0.40
inloop: elasped=0.54694800; time left=0.07 reset time=0.40
inloop: elasped=0.54695500; time left=0.00 reset time=0.40
inloop: elasped=0.54696200; time left=0.004000 reset time=0.40
[...]
VTALRM: elasped=0.55013600; time left=0.397062 reset time=0.40
(end of file)
The reset time also looks dodgy.
Hardware is an Intel Core i7-920 on Asus P6T Deluxe v2 (X58)
motherboard and hasn't changed.
Requested information:
Ubuntu 3.13.0-32.57-generic 3.13.11.4
Description: Ubuntu 14.04.1 LTS
Release: 14.04
# apt-cache policy linux-image-generic
linux-image-generic:
Installed: 3.13.0.32.38
Candidate: 3.13.0.32.38
Version table:
*** 3.13.0.32.38 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64
Packages
500 http://us.archive.ubuntu.com/ubuntu/ trusty-security/main amd64
Packages
500 http://us.archive.ubuntu.com/ubuntu/ trusty-proposed/main amd64
Packages
500 http://ppa.launchpad.net/canonical-kernel-team/ppa/ubuntu/
trusty/main amd64 Packages
100 /var/lib/dpkg/status
3.13.0.24.28 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
---
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: tivrusky 3009 F pulseaudio
[Kernel-packages] [Bug 1874464] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874464 Title: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out Status in linux package in Ubuntu: Confirmed Bug description: Running focal on a desktop, I accidentally clicked "Enable networking" in nm-applet, disabling my networking. When I clicked it again to reenable it, my networking did not return. After unsuccessfully poking at it for a while, I rebooted and saw the below (and still no networking). `rmmod r8169; modprobe r8169` had no (apparent) effect, nor did further reboots. I rebooted onto two different kernels, both exhibited the same behaviour: 5.4.0-21-generic, 5.4.0-26-generic. I was finally only able to restore networking by _rebooting into Windows_ and then rebooting back into Ubuntu. (My supposition is that NetworkManager/the kernel set *waves hands* something on the network card that persists across boots when it was disabled, and that wasn't correctly unset when I reenabled networking (or on following boots), but Windows _does_ correctly handle that case on boot, and reset it to a working state.) Apr 23 10:07:43 surprise kernel: [ cut here ] Apr 23 10:07:43 surprise kernel: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out Apr 23 10:07:43 surprise kernel: WARNING: CPU: 9 PID: 0 at net/sched/sch_generic.c:447 dev_watchdog+0x258/0x260 Apr 23 10:07:43 surprise kernel: Modules linked in: zfs(PO) zunicode(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) zlua(PO) xt_comment dummy xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_> Apr 23 10:07:43 surprise kernel: autofs4 btrfs xor zstd_compress raid6_pq libcrc32c dm_crypt hid_microsoft ff_memless hid_logitech_hidpp hid_logitech_dj hid_generic usbhid hid nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) crct10dif_pclmul crc32_pclmul ghash_clmulni_intel drm_km> Apr 23 10:07:43 surprise kernel: CPU: 9 PID: 0 Comm: swapper/9 Tainted: P OE 5.4.0-26-generic #30-Ubuntu Apr 23 10:07:43 surprise kernel: Hardware name: Gigabyte Technology Co., Ltd. B450M DS3H/B450M DS3H-CF, BIOS F4 01/25/2019 Apr 23 10:07:43 surprise kernel: RIP: 0010:dev_watchdog+0x258/0x260 Apr 23 10:07:43 surprise kernel: Code: 85 c0 75 e5 eb 9f 4c 89 ff c6 05 bf 06 e8 00 01 e8 6d bb fa ff 44 89 e9 4c 89 fe 48 c7 c7 50 6d a3 b4 48 89 c2 e8 83 3f 71 ff <0f> 0b eb 80 0f 1f 40 00 0f 1f 44 00 00 55 48 89 e5 41 57 49 89 d7 Apr 23 10:07:43 surprise kernel: RSP: 0018:a90d40378e30 EFLAGS: 00010286 Apr 23 10:07:43 surprise kernel: RAX: RBX: 8a7578b00400 RCX: Apr 23 10:07:43 surprise kernel: RDX: 8a758ee67740 RSI: 8a758ee578c8 RDI: 0300 Apr 23 10:07:43 surprise kernel: RBP: a90d40378e60 R08: 8a758ee578c8 R09: 0004 Apr 23 10:07:43 surprise kernel: R10: R11: 0001 R12: 0001 Apr 23 10:07:43 surprise kernel: R13: R14: 8a758cadc480 R15: 8a758cadc000 Apr 23 10:07:43 surprise kernel: FS: () GS:8a758ee4() knlGS: Apr 23 10:07:43 surprise kernel: CS: 0010 DS: ES: CR0: 80050033 Apr 23 10:07:43 surprise kernel: CR2: 7f4d2000d5eb CR3: 0003fcfe2000 CR4: 003406e0 Apr 23 10:07:43 surprise kernel: Call Trace: Apr 23 10:07:43 surprise kernel: Apr 23 10:07:43 surprise kernel: ? pfifo_fast_enqueue+0x150/0x150 Apr 23 10:07:43 surprise kernel: call_timer_fn+0x32/0x130 Apr 23 10:07:43 surprise kernel: __run_timers.part.0+0x180/0x280 Apr 23 10:07:43 surprise kernel: ? tick_sched_handle+0x33/0x60 Apr 23 10:07:43 surprise kernel: ? tick_sched_timer+0x3d/0x80 Apr 23 10:07:43 surprise kernel: ? ktime_get+0x3e/0xa0 Apr 23 10:07:43 surprise kernel: run_timer_softirq+0x2a/0x50 Apr 23 10:07:43 surprise kernel: __do_softirq+0xe1/0x2d6 Apr 23 10:07:43 surprise kernel: ? hrtimer_interrupt+0x13b/0x220 Apr 23 10:07:43 surprise kernel: irq_exit+0xae/0xb0 Apr 23 10:07:43 surprise kernel: smp_apic_timer_interrupt+0x7b/0x140 Apr 23 10:07:43 surprise kernel: apic_timer_interrupt+0xf/0x20 Apr 23 10:07:43 surprise kernel: Apr 23 10:07:43 surprise kernel: RIP: 0010:cpuidle_enter_state+0xc5/0x450 Apr 23 10:07:43 surprise kernel: Code: ff e8 df 0d 81 ff 80 7d c7 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 65 03 00 00 31 ff e8 32 7a 87 ff fb 66 0f 1f 44 00 00 <45> 85 ed 0f 88 8f 02 00 00 49 63 cd 4c 8b 7d d0 4c 2b 7d c8 48 8d Apr 23 10:07:43 surprise kernel: RSP: 0018:a90d4016fe38 EFLAGS: 0246 ORIG_RAX: ff13 Apr 23 10:07:43 surprise kernel: RAX:
[Kernel-packages] [Bug 1874464] Re: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out
Here are the NetworkManager logs when I first disabled my networking (note that ensp5s0 does get its link up reported correctly, but no traffic seems to go over it): Apr 23 09:42:54 surprise NetworkManager[1281]: [1587649374.1626] manager: disable requested (sleeping: no enabled: yes) Apr 23 09:42:54 surprise NetworkManager[1281]: [1587649374.1627] manager: NetworkManager state is now ASLEEP Apr 23 09:42:54 surprise dbus-daemon[1280]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.9' (uid=0 pid=1281 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined") Apr 23 09:42:54 surprise NetworkManager[1281]: [1587649374.1654] device (enp5s0): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: 'managed') Apr 23 09:42:54 surprise NetworkManager[1281]: [1587649374.1695] device (virbr0): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: 'external') Apr 23 09:42:54 surprise NetworkManager[1281]: [1587649374.1703] device (lxdbr0): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: 'external') Apr 23 09:42:54 surprise NetworkManager[1281]: [1587649374.1711] device (docker0): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: 'external') Apr 23 09:42:54 surprise NetworkManager[1281]: [1587649374.1718] device (tun0): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: 'external') Apr 23 09:42:54 surprise NetworkManager[1281]: [1587649374.1744] device (mpqemubr0): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: 'external') Apr 23 09:42:54 surprise NetworkManager[1281]: [1587649374.1754] device (tap-2eb5e2d1a05): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: 'external') Apr 23 09:42:54 surprise NetworkManager[1281]: [1587649374.1756] device (mpqemubr0): bridge port tap-2eb5e2d1a05 was detached Apr 23 09:42:54 surprise NetworkManager[1281]: [1587649374.1756] device (tap-2eb5e2d1a05): released from master device mpqemubr0 Apr 23 09:42:54 surprise NetworkManager[1281]: [1587649374.1764] device (tap-8b9ffd8bf3f): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: 'external') Apr 23 09:42:54 surprise NetworkManager[1281]: [1587649374.1765] device (mpqemubr0): bridge port tap-8b9ffd8bf3f was detached Apr 23 09:42:54 surprise NetworkManager[1281]: [1587649374.1765] device (tap-8b9ffd8bf3f): released from master device mpqemubr0 Apr 23 09:42:54 surprise NetworkManager[1281]: [1587649374.2065] device (enp5s0): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-state: 'managed') Apr 23 09:42:54 surprise NetworkManager[1281]: [1587649374.2124] dhcp4 (enp5s0): canceled DHCP transaction Apr 23 09:42:54 surprise NetworkManager[1281]: [1587649374.2124] dhcp4 (enp5s0): state changed extended -> done Apr 23 09:42:54 surprise NetworkManager[1281]: [1587649374.2132] dhcp6 (enp5s0): canceled DHCP transaction Apr 23 09:42:54 surprise NetworkManager[1281]: [1587649374.2133] dhcp6 (enp5s0): state changed bound -> done Apr 23 09:42:54 surprise NetworkManager[1281]: [1587649374.2455] vpn-connection[0x55a3ea09c330,6c36b60c-84e0-42b3-85d0-8ddb549add83,"us-dwatkins",0]: VPN plugin: state changed: stopping (5) Apr 23 09:42:54 surprise NetworkManager[1281]: [1587649374.2455] vpn-connection[0x55a3ea09c330,6c36b60c-84e0-42b3-85d0-8ddb549add83,"us-dwatkins",0]: VPN plugin: state changed: stopped (6) Apr 23 09:42:54 surprise NetworkManager[1281]: [1587649374.2466] device (enp5s0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed') Apr 23 09:42:54 surprise NetworkManager[1281]: [1587649374.3121] device (virbr0): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-state: 'external') Apr 23 09:42:54 surprise NetworkManager[1281]: [1587649374.3588] device (lxdbr0): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-state: 'external') Apr 23 09:42:54 surprise NetworkManager[1281]: [1587649374.3655] device (docker0): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-state: 'external') Apr 23 09:42:54 surprise NetworkManager[1281]: [1587649374.3760] device (tun0): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-state: 'external') Apr 23 09:42:54 surprise NetworkManager[1281]: [1587649374.3819] device (mpqemubr0): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-state: 'external') Apr 23 09:42:54 surprise NetworkManager[1281]: [1587649374.4358] device (tap-2eb5e2d1a05): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-state: 'external') Apr 23 09:42:54 surprise NetworkManager[1281]: [1587649374.4381] device (tap-8b9ffd8bf3f): state change:
[Kernel-packages] [Bug 1874464] [NEW] NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out
Public bug reported: Running focal on a desktop, I accidentally clicked "Enable networking" in nm-applet, disabling my networking. When I clicked it again to reenable it, my networking did not return. After unsuccessfully poking at it for a while, I rebooted and saw the below (and still no networking). `rmmod r8169; modprobe r8169` had no (apparent) effect, nor did further reboots. I rebooted onto two different kernels, both exhibited the same behaviour: 5.4.0-21-generic, 5.4.0-26-generic. I was finally only able to restore networking by _rebooting into Windows_ and then rebooting back into Ubuntu. (My supposition is that NetworkManager/the kernel set *waves hands* something on the network card that persists across boots when it was disabled, and that wasn't correctly unset when I reenabled networking (or on following boots), but Windows _does_ correctly handle that case on boot, and reset it to a working state.) Apr 23 10:07:43 surprise kernel: [ cut here ] Apr 23 10:07:43 surprise kernel: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out Apr 23 10:07:43 surprise kernel: WARNING: CPU: 9 PID: 0 at net/sched/sch_generic.c:447 dev_watchdog+0x258/0x260 Apr 23 10:07:43 surprise kernel: Modules linked in: zfs(PO) zunicode(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) zlua(PO) xt_comment dummy xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_> Apr 23 10:07:43 surprise kernel: autofs4 btrfs xor zstd_compress raid6_pq libcrc32c dm_crypt hid_microsoft ff_memless hid_logitech_hidpp hid_logitech_dj hid_generic usbhid hid nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) crct10dif_pclmul crc32_pclmul ghash_clmulni_intel drm_km> Apr 23 10:07:43 surprise kernel: CPU: 9 PID: 0 Comm: swapper/9 Tainted: P OE 5.4.0-26-generic #30-Ubuntu Apr 23 10:07:43 surprise kernel: Hardware name: Gigabyte Technology Co., Ltd. B450M DS3H/B450M DS3H-CF, BIOS F4 01/25/2019 Apr 23 10:07:43 surprise kernel: RIP: 0010:dev_watchdog+0x258/0x260 Apr 23 10:07:43 surprise kernel: Code: 85 c0 75 e5 eb 9f 4c 89 ff c6 05 bf 06 e8 00 01 e8 6d bb fa ff 44 89 e9 4c 89 fe 48 c7 c7 50 6d a3 b4 48 89 c2 e8 83 3f 71 ff <0f> 0b eb 80 0f 1f 40 00 0f 1f 44 00 00 55 48 89 e5 41 57 49 89 d7 Apr 23 10:07:43 surprise kernel: RSP: 0018:a90d40378e30 EFLAGS: 00010286 Apr 23 10:07:43 surprise kernel: RAX: RBX: 8a7578b00400 RCX: Apr 23 10:07:43 surprise kernel: RDX: 8a758ee67740 RSI: 8a758ee578c8 RDI: 0300 Apr 23 10:07:43 surprise kernel: RBP: a90d40378e60 R08: 8a758ee578c8 R09: 0004 Apr 23 10:07:43 surprise kernel: R10: R11: 0001 R12: 0001 Apr 23 10:07:43 surprise kernel: R13: R14: 8a758cadc480 R15: 8a758cadc000 Apr 23 10:07:43 surprise kernel: FS: () GS:8a758ee4() knlGS: Apr 23 10:07:43 surprise kernel: CS: 0010 DS: ES: CR0: 80050033 Apr 23 10:07:43 surprise kernel: CR2: 7f4d2000d5eb CR3: 0003fcfe2000 CR4: 003406e0 Apr 23 10:07:43 surprise kernel: Call Trace: Apr 23 10:07:43 surprise kernel: Apr 23 10:07:43 surprise kernel: ? pfifo_fast_enqueue+0x150/0x150 Apr 23 10:07:43 surprise kernel: call_timer_fn+0x32/0x130 Apr 23 10:07:43 surprise kernel: __run_timers.part.0+0x180/0x280 Apr 23 10:07:43 surprise kernel: ? tick_sched_handle+0x33/0x60 Apr 23 10:07:43 surprise kernel: ? tick_sched_timer+0x3d/0x80 Apr 23 10:07:43 surprise kernel: ? ktime_get+0x3e/0xa0 Apr 23 10:07:43 surprise kernel: run_timer_softirq+0x2a/0x50 Apr 23 10:07:43 surprise kernel: __do_softirq+0xe1/0x2d6 Apr 23 10:07:43 surprise kernel: ? hrtimer_interrupt+0x13b/0x220 Apr 23 10:07:43 surprise kernel: irq_exit+0xae/0xb0 Apr 23 10:07:43 surprise kernel: smp_apic_timer_interrupt+0x7b/0x140 Apr 23 10:07:43 surprise kernel: apic_timer_interrupt+0xf/0x20 Apr 23 10:07:43 surprise kernel: Apr 23 10:07:43 surprise kernel: RIP: 0010:cpuidle_enter_state+0xc5/0x450 Apr 23 10:07:43 surprise kernel: Code: ff e8 df 0d 81 ff 80 7d c7 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 65 03 00 00 31 ff e8 32 7a 87 ff fb 66 0f 1f 44 00 00 <45> 85 ed 0f 88 8f 02 00 00 49 63 cd 4c 8b 7d d0 4c 2b 7d c8 48 8d Apr 23 10:07:43 surprise kernel: RSP: 0018:a90d4016fe38 EFLAGS: 0246 ORIG_RAX: ff13 Apr 23 10:07:43 surprise kernel: RAX: 8a758ee6ad00 RBX: b4d69160 RCX: 001f Apr 23 10:07:43 surprise kernel: RDX: RSI: 239f52d0 RDI: Apr 23 10:07:43 surprise kernel: RBP: a90d4016fe78 R08: 011276ac078f R09: 000148ba Apr 23 10:07:43 surprise kernel: R10: 8a758ee69a00 R11: 8a758ee699e0 R12: 8a757a318000 Apr 23 10:07:43 surprise kernel: R13: 0002 R14: 0002 R15: 8a757a318000 Apr 23 10:07:43
[Kernel-packages] [Bug 1864061] Re: PCI/internal sound card not detected
Affected by this same bug. Workaround described on https://bugs.launchpad.net/ubuntu/+source/linux- oem-osp1/+bug/1864061/comments/9 did not do the trick either. The only solution that worked (but not always, sometimes it just duplicates "Dummy output") was `pulseaudio -k && sudo alsa force- reload`. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1864061 Title: PCI/internal sound card not detected Status in linux package in Ubuntu: Invalid Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Eoan: Fix Released Status in linux-oem-osp1 source package in Eoan: Fix Released Bug description: The sof-pci-dev and snd-soc-skl all contains the same pciid, if the soc-skl is loaded ahead of sof-pci-dev, the sof driver will not work anymore, in the oem project, we manually put the soc-skl in the blacklist. From kernel-5.4 (focal kernel), the driver soc-skl is disabled by default, and there is no users report any issues on it. So let us disable soc-skl in the eoan and osp1 kernel too. The patch for eoan kernel doesn't remove the modules because looks like the abi folder are not controlled by git. This will break the modulecheck, so if this patch could be merged, please help remove those modules: snd-soc-skl snd-soc-skl-ipc snd-soc-skl-ssp-clk [Impact] If soc-skl driver is loaded ahead of sof driver, the sof could not work anymore, we need to blacklist the soc-skl manually [Fix] Like the focal kernel, we disable the soc_skl driver in the kernel config [Test Case] Tested on Lenovo and Dell machines which has dmic, the sof driver could be loaded successfully. Tested on the machinces without the dmic, the legacy hda driver worked well as before. [Regression Risk] Low, Focal kernel and mainine-5.5, 5.6-rc kernel all disabled this dirver; and We have not met a machine need the soc_skl driver yet; and Intel claim that the sof could replace the soc_skl driver. In the -41 kernel, we introduced a patch from stable kernel, that make the sof driver crash, and there is a fix patch in the 5.6-rc1, and this fix patch is already in the stable and is merged to focal kernel, now we backport this patch to Eoan kernel if -42 doesn't introduce this fix patch from stable. The patch introduced the crash: commit 063821115e02229d5fd3de31bad270d5e30aeb41 Author: Dragos Tarcatu Date: Mon Dec 9 18:39:38 2019 -0600 ASoC: topology: Check return value for snd_soc_add_dai_link() BugLink: https://bugs.launchpad.net/bugs/1861929 [ Upstream commit 76d2703649321c296df7ec0dafd50add96215de4 ] snd_soc_add_dai_link() might fail. This situation occurs for instance in a very specific use case where a PCM device and a Back End DAI link are given identical names in the topology. When this happens, soc_new_pcm_runtime() fails and then snd_soc_add_dai_link() returns -ENOMEM when called from soc_tplg_fe_link_create(). Because of that, the link will not get added into the card list, so any attempt to remove it later ends up in a panic. Fix that by checking the return status and free the memory in case of an error. Reviewed-by: Ranjani Sridharan Signed-off-by: Dragos Tarcatu Signed-off-by: Pierre-Louis Bossart Link: https://lore.kernel.org/r/20191210003939.15752-2-pierre-louis.boss...@linux.intel.com Signed-off-by: Mark Brown Signed-off-by: Sasha Levin Signed-off-by: Kamal Mostafa Signed-off-by: Khalid Elmously [Impact] During the boot, the sof driver crash because the hdmi_pcm_list is not initialized before it is used. [Fix] This bug is fixed in the mainline kernel v5.6-rc1, now backport this patch to ubuntu kernel [Test Case] Boot the -41 kernel with this patch added. blacklist the snd_soc_skl the kernel can boot successfully, and sof driver worked well [Regression Risk] Low, the patches are backported from upstream kernel, and I tested this patch on Lenovo and Dell dmic machines. Focal kernel already has this patch and works well. Probably a kernel bug. The sound card isn't detected in 5.3.0-41-generic Booting 5.3.0-40-generic does work. The relevant dmesg message is: [9.845441] skl_hda_dsp_generic skl_hda_dsp_generic: Unsupported HDAudio/iDisp configuration found [9.845447] skl_hda_dsp_generic: probe of skl_hda_dsp_generic failed with error -22 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-41.33-generic 5.3.18 Uname: Linux 5.3.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64
[Kernel-packages] [Bug 1808418] Re: Thinkpad T430u won't boot without noapic workaround
Very odd... 5.7 boots (without noapic or intremap=off), but not consistently. It boots a number of times just fine (in my tests, anywhere from 3-5 successful boots) and then after that it will hang at boot. Most of the time after powering off/powering back on it boots fine again, without needing to modify the kernel parameters. There is one other unrelated issue with 5.7: my BCM43228 wireless doesn't work. Maybe the bcmwl-kernel-source package just isn't compatible with 5.7 yet? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1808418 Title: Thinkpad T430u won't boot without noapic workaround Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: New Bug description: I've used Ubuntu on this specific machine for years without problems, but starting with the 4.13 kernel that came with the 17.10 HWE and continuing into 18.04 kernels my computer would no longer boot, hanging at various screens: - A blank screen with a flashing cursor - A screen with this message: Loading Linux 4.13.0.36-generic ... Loading initial ramdisk ... - A screen with kernel messages, ending in: APCI: EC: interrupt blocked I've encountered the bug in a number of kernels, including: - 4.13.0-32 - 4.13.0-36 - 4.13.0-37 - 4.15.0-24 - 4.15.0-34 - 4.15.0-36 - 4.15.0-38 - 4.15.0-42 - 4.20.0-rc7 I was able to work around the issue by adding noapic to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default grub, e.g.: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash noapic" I'm not entirely sure of the consequences of this workaround, but one thing I've noticed is significantly reduced battery life. This bug seems very similar to what's described here for the Thinkpad E485/E585: https://evilazrael.de/node/401 I'll attach screenshots of various times I've encountered this bug over the last year. $ lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 $ apt-cache policy linux-image-4.15.0-42-generic linux-image-4.15.0-42-generic: Installed: 4.15.0-42.45 Candidate: 4.15.0-42.45 Version table: *** 4.15.0-42.45 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-42-generic 4.15.0-42.45 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bryan 2349 F pulseaudio CurrentDesktop: XFCE Date: Thu Dec 13 15:31:15 2018 HibernationDevice: RESUME=UUID=4afa8032-cfe5-45f4-a626-738ab33904ac InstallationDate: Installed on 2014-05-08 (1680 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: LENOVO 3351CTO ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID=cffbc87d-956b-4986-94df-b3b64ae5237f ro quiet splash noapic vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-42-generic N/A linux-backports-modules-4.15.0-42-generic N/A linux-firmware 1.173.2 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-07-12 (154 days ago) dmi.bios.date: 06/01/2018 dmi.bios.vendor: LENOVO dmi.bios.version: H6ETA0WW (2.18 ) dmi.board.asset.tag: Not Available dmi.board.name: 3351CTO dmi.board.vendor: LENOVO dmi.board.version: Win8 STD DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrH6ETA0WW(2.18):bd06/01/2018:svnLENOVO:pn3351CTO:pvrThinkPadT430u:rvnLENOVO:rn3351CTO:rvrWin8STDDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430u dmi.product.name: 3351CTO dmi.product.version: ThinkPad T430u dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808418/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874437] Re: Intel 82579LM [8086:1502] Subsystem [1028:0498] Network driver for e1000 card not loaded on boot on beta 20.04
** Summary changed: - Network driver for e1000 card not loaded on boot on beta 20.04 + Intel 82579LM [8086:1502] Subsystem [1028:0498] Network driver for e1000 card not loaded on boot on beta 20.04 ** Tags added: hwe-networking-ethernet -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874437 Title: Intel 82579LM [8086:1502] Subsystem [1028:0498] Network driver for e1000 card not loaded on boot on beta 20.04 Status in linux package in Ubuntu: Confirmed Bug description: Hi The symptons are: I was running 20.04 Desktop Beta - everything was ok, I have an on board network card 00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network Connection (Lewisville) (rev 04) After patching on 20th April - the network dissappeard - not the device mind you. When you did ip a - you got 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever I tried downloading the latest as in the build on 20th but on boot from USB - it does not gring up the network My hack - install another 100M pci card - this caused the network drivers to be loaded and both cards to work. Current state of play: 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: enp5s2: mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000 link/ether 00:40:f4:28:8f:30 brd ff:ff:ff:ff:ff:ff 3: enp0s25: mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 18:03:73:d8:e9:94 brd ff:ff:ff:ff:ff:ff inet 192.168.0.25/24 brd 192.168.0.255 scope global noprefixroute enp0s25 valid_lft forever preferred_lft forever inet6 fe80::1a03:73ff:fed8:e994/64 scope link valid_lft forever preferred_lft forever 6: enx424d7f654382: mtu 1500 qdisc fq_codel state DOWN group default qlen 1000 link/ether 42:4d:7f:65:43:82 brd ff:ff:ff:ff:ff:ff enp0s25 is detected and working. If I unplug the ethernet to the 100M card that is a: 05:02.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8100/8101L/8139 PCI Fast Ethernet Adapter (rev 10) then the network stops working! Well weird. Many thanks for the help. But I expect I cant be the only person with this issue the intel 1000m card is quite popular - the system is a Dell t1600 xeon 5.4.0-26-generic #30-Ubuntu SMP Mon Apr 20 16:58:30 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Cheers Naveed 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 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Thu Apr 23 13:43:52 2020 InstallationDate: Installed on 2020-04-21 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200417) MachineType: Dell Inc. Precision T1600 ProcFB: 0 nouveaudrmfb 1 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=423f52c8-113b-4bd6-bebe-62233a48aceb ro quiet splash vt.handoff=7 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: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/07/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 06NWYK dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd05/07/2017:svnDellInc.:pnPrecisionT1600:pvr01:rvnDellInc.:rn06NWYK:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: Precision T1600 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874437/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874435] Re: Bluetooth not working with Atheros AR9287
https://wireless.wiki.kernel.org/en/users/drivers/ath9k/btcoex does this work for you? ** Tags added: hwe-bluetooth -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874435 Title: Bluetooth not working with Atheros AR9287 Status in linux package in Ubuntu: Incomplete Bug description: Bluetooth adapter not visible. In bluetooth menu, we see "no bluetooth found". (Ubuntu 20.04, kernel 5.4.0-26-generic #30-Ubuntu) $ lspci -nnk | grep -iA3 atheros 02:00.0 Network controller [0280]: Qualcomm Atheros AR9287 Wireless Network Adapter (PCI-Express) [168c:002e] (rev 01) Subsystem: Foxconn International, Inc. T77H167.00 [105b:e034] Kernel driver in use: ath9k Kernel modules: ath9k I tried to load the module with btcoex_enable=1, does not help : $ cat /etc/modprobe.d/ath9k-bt.conf options ath9k btcoex_enable=1 $ cat /sys/module/ath9k/parameters/btcoex_enable 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874435/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874305] Re: Qualcomm Atheros QCA9377 [168c:0042] Subsystem [1028:1810]: Wifi goes down when change bluetooth configuration
** Summary changed: - Wifi goes down when change bluetooth configuration + Qualcomm Atheros QCA9377 [168c:0042] Subsystem [1028:1810]: Wifi goes down when change bluetooth configuration -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874305 Title: Qualcomm Atheros QCA9377 [168c:0042] Subsystem [1028:1810]: Wifi goes down when change bluetooth configuration Status in linux package in Ubuntu: Incomplete Bug description: WiFi connection goes down when having a Bluetooth headset connected and change from A2DP to HSP. The connection goes down instantly. If you change back to A2DP connection works again, but in some cases it goes down forever till you disconnect from the current WiFi and connect again. [How to reproduce] 1. connect a Bluetooth headset and change from A2DP to HSP. [System Info] Ubuntu 5.4.0-24.28-generic 5.4.30 03:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 31) No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 20.04 LTS Release: 20.04 Codename:focal [DMESG info] 348674.114861] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114864] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114866] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114869] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114873] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114876] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114879] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114882] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114885] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114888] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114891] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114894] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114897] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114900] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114903] Bluetooth: hci0: SCO packet for unknown connection handle 3072 [348674.114906] Bluetooth: hci0: SCO packet for unknown connection handle 48 [348674.114909] Bluetooth: hci0: SCO packet for unknown connection handle 0 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: leosilva 6150 F pulseaudio /dev/snd/pcmC1D7p: leosilva 6150 F...m pulseaudio /dev/snd/controlC0: leosilva 6150 F pulseaudio /dev/snd/pcmC0D8p: leosilva 6150 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-02 (111 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200102) MachineType: Dell Inc. XPS 8930 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA 1 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-24-generic root=UUID=bb691d80-94d7-4044-844f-c0df45ba89ca ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-24-generic N/A linux-backports-modules-5.4.0-24-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-24-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 libvirt lpadmin lxd plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 10/31/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.10 dmi.board.name: 06HKRH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.1.10:bd10/31/2019:svnDellInc.:pnXPS8930:pvr1.1.10:rvnDellInc.:rn06HKRH:rvrA00:cvnDellInc.:ct3:cvrNotSpecified: dmi.product.family: XPS dmi.product.name: XPS 8930 dmi.product.sku: 0859 dmi.product.version: 1.1.10 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874305/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874104] Re: Very slow boot, wake from sleep and shutdown with 5.4 kernel
I hope this is what you were looking for. In your message, you noted that the login bug is likely a separate issue and it could be reported as new. I thought that this is what I already did. If not, should I report it again? And with what attachments? Thanks. ** Attachment added: "dmesg.0" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874104/+attachment/5358452/+files/dmesg.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/1874104 Title: Very slow boot, wake from sleep and shutdown with 5.4 kernel Status in linux package in Ubuntu: Confirmed Bug description: I upgraded a Ubuntu 18.04 installation to 20.04 beta on my late 2015 5k 27" iMac. The new 5.4 kernel was installed and has been updated a few times. The former LTS kernel (4.15) was retained. When I start up the computer with the new kernel, the process is very slow and it takes about 2 1/2 minutes to get to a working desktop. Doing the same startup with the old 4.15 kernel (in the 20.04 beta) takes approximately 25 seconds to a working desktop. Similarly, changing display settings, waking from sleep and shutting down the computer all take several minutes with the 5.4 kernel, vs 10-30 seconds with the 4.15 kernel. To provide more information, I tried starting up this computer with the 5.3 kernel from a 19.10 live USB, and from a 5.0 kernel in the Peppermint Linux live USB that is based on Ubuntu. The 5.3 kernel is as slow as the 5.4 kernel, whereas the 5.0 kernel works similarly to the 4.15 LTS kernel. I suspect that the problem relates to the Radeon m9 390x video card in my iMac, but I have no idea what might have changed in the newer kernels to affect their compatibility with this iMac. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-25-generic 5.4.0-25.29 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Uname: Linux 5.4.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: mfox 2497 F pulseaudio /dev/snd/controlC0: mfox 2497 F pulseaudio /dev/snd/controlC1: mfox 2497 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 21 10:55:18 2020 HibernationDevice: # RESUME=UUID=5e4ca488-e781-4ee7-aeb3-8adc968cd22a InstallationDate: Installed on 2018-05-09 (712 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Apple Inc. iMac17,1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: \boot\vmlinuz-5.4.0-25-generic ro root=UUID=0559983a-7175-4ab1-af46-7a117ee78ead initrd=boot\initrd.img-5.4.0-25-generic RelatedPackageVersions: linux-restricted-modules-5.4.0-25-generic N/A linux-backports-modules-5.4.0-25-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2020 dmi.bios.vendor: Apple Inc. dmi.bios.version: 176.0.0.0.0 dmi.board.name: Mac-B809C3757DA9BB8D dmi.board.vendor: Apple Inc. dmi.board.version: iMac17,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-B809C3757DA9BB8D dmi.modalias: dmi:bvnAppleInc.:bvr176.0.0.0.0:bd01/31/2020:svnAppleInc.:pniMac17,1:pvr1.0:rvnAppleInc.:rnMac-B809C3757DA9BB8D:rvriMac17,1:cvnAppleInc.:ct9:cvrMac-B809C3757DA9BB8D: dmi.product.family: iMac17,1 dmi.product.name: iMac17,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874104/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861235] Re: zfs recv PANIC at range_tree.c:304:range_tree_find_impl()
** Changed in: linux Status: Unknown => New -- 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/1861235 Title: zfs recv PANIC at range_tree.c:304:range_tree_find_impl() Status in Linux: New Status in zfs-linux package in Ubuntu: Incomplete Status in zfs-linux source package in Bionic: New Bug description: Same as bug 1861228 but with a newer kernel installed. [ 790.702566] VERIFY(size != 0) failed [ 790.702590] PANIC at range_tree.c:304:range_tree_find_impl() [ 790.702611] Showing stack for process 28685 [ 790.702614] CPU: 17 PID: 28685 Comm: receive_writer Tainted: P O 4.15.0-76-generic #86-Ubuntu [ 790.702615] Hardware name: Supermicro SSG-6038R-E1CR16L/X10DRH-iT, BIOS 2.0 12/17/2015 [ 790.702616] Call Trace: [ 790.702626] dump_stack+0x6d/0x8e [ 790.702637] spl_dumpstack+0x42/0x50 [spl] [ 790.702640] spl_panic+0xc8/0x110 [spl] [ 790.702645] ? __switch_to_asm+0x41/0x70 [ 790.702714] ? arc_prune_task+0x1a/0x40 [zfs] [ 790.702740] ? dbuf_dirty+0x43d/0x850 [zfs] [ 790.702745] ? getrawmonotonic64+0x43/0xd0 [ 790.702746] ? getrawmonotonic64+0x43/0xd0 [ 790.702775] ? dmu_zfetch+0x49a/0x500 [zfs] [ 790.702778] ? getrawmonotonic64+0x43/0xd0 [ 790.702805] ? dmu_zfetch+0x49a/0x500 [zfs] [ 790.702807] ? mutex_lock+0x12/0x40 [ 790.702833] ? dbuf_rele_and_unlock+0x1a8/0x4b0 [zfs] [ 790.702866] range_tree_find_impl+0x88/0x90 [zfs] [ 790.702870] ? spl_kmem_zalloc+0xdc/0x1a0 [spl] [ 790.702902] range_tree_clear+0x4f/0x60 [zfs] [ 790.702930] dnode_free_range+0x11f/0x5a0 [zfs] [ 790.702957] dmu_object_free+0x53/0x90 [zfs] [ 790.702983] dmu_free_long_object+0x9f/0xc0 [zfs] [ 790.703010] receive_freeobjects.isra.12+0x7a/0x100 [zfs] [ 790.703036] receive_writer_thread+0x6d2/0xa60 [zfs] [ 790.703040] ? set_curr_task_fair+0x2b/0x60 [ 790.703043] ? spl_kmem_free+0x33/0x40 [spl] [ 790.703048] ? kfree+0x165/0x180 [ 790.703073] ? receive_free.isra.13+0xc0/0xc0 [zfs] [ 790.703078] thread_generic_wrapper+0x74/0x90 [spl] [ 790.703081] kthread+0x121/0x140 [ 790.703084] ? __thread_exit+0x20/0x20 [spl] [ 790.703085] ? kthread_create_worker_on_cpu+0x70/0x70 [ 790.703088] ret_from_fork+0x35/0x40 [ 967.636923] INFO: task txg_quiesce:14810 blocked for more than 120 seconds. [ 967.636979] Tainted: P O 4.15.0-76-generic #86-Ubuntu [ 967.637024] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 967.637076] txg_quiesce D0 14810 2 0x8000 [ 967.637080] Call Trace: [ 967.637089] __schedule+0x24e/0x880 [ 967.637092] schedule+0x2c/0x80 [ 967.637106] cv_wait_common+0x11e/0x140 [spl] [ 967.637114] ? wait_woken+0x80/0x80 [ 967.637122] __cv_wait+0x15/0x20 [spl] [ 967.637210] txg_quiesce_thread+0x2cb/0x3d0 [zfs] [ 967.637278] ? txg_delay+0x1b0/0x1b0 [zfs] [ 967.637286] thread_generic_wrapper+0x74/0x90 [spl] [ 967.637291] kthread+0x121/0x140 [ 967.637297] ? __thread_exit+0x20/0x20 [spl] [ 967.637299] ? kthread_create_worker_on_cpu+0x70/0x70 [ 967.637304] ret_from_fork+0x35/0x40 [ 967.637326] INFO: task zfs:28590 blocked for more than 120 seconds. [ 967.637371] Tainted: P O 4.15.0-76-generic #86-Ubuntu [ 967.637416] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 967.637467] zfs D0 28590 28587 0x8080 [ 967.637470] Call Trace: [ 967.637474] __schedule+0x24e/0x880 [ 967.637477] schedule+0x2c/0x80 [ 967.637486] cv_wait_common+0x11e/0x140 [spl] [ 967.637491] ? wait_woken+0x80/0x80 [ 967.637498] __cv_wait+0x15/0x20 [spl] [ 967.637554] dmu_recv_stream+0xa51/0xef0 [zfs] [ 967.637630] zfs_ioc_recv_impl+0x306/0x1100 [zfs] [ 967.637679] ? dbuf_read+0x34a/0x920 [zfs] [ 967.637725] ? dbuf_rele+0x36/0x40 [zfs] [ 967.637728] ? _cond_resched+0x19/0x40 [ 967.637798] zfs_ioc_recv_new+0x33d/0x410 [zfs] [ 967.637809] ? spl_kmem_alloc_impl+0xe5/0x1a0 [spl] [ 967.637816] ? spl_vmem_alloc+0x19/0x20 [spl] [ 967.637828] ? nv_alloc_sleep_spl+0x1f/0x30 [znvpair] [ 967.637834] ? nv_mem_zalloc.isra.0+0x2e/0x40 [znvpair] [ 967.637840] ? nvlist_xalloc.part.2+0x50/0xb0 [znvpair] [ 967.637905] zfsdev_ioctl+0x451/0x610 [zfs] [ 967.637913] do_vfs_ioctl+0xa8/0x630 [ 967.637917] ? __audit_syscall_entry+0xbc/0x110 [ 967.637924] ? syscall_trace_enter+0x1da/0x2d0 [ 967.637927] SyS_ioctl+0x79/0x90 [ 967.637930] do_syscall_64+0x73/0x130 [ 967.637935] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [ 967.637938] RIP: 0033:0x7fc305a905d7 [ 967.637940] RSP: 002b:7ffc45e39618 EFLAGS: 0246 ORIG_RAX: 0010 [ 967.637943] RAX: ffda RBX: 5a46 RCX: 7fc305a905d7 [ 967.637945]
[Kernel-packages] [Bug 1862165] Re: /usr/local leak in /etc/default/zfs
** Changed in: zfs
Status: New => Fix Released
--
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/1862165
Title:
/usr/local leak in /etc/default/zfs
Status in Native ZFS for Linux:
Fix Released
Status in zfs-linux package in Ubuntu:
New
Bug description:
While updating my focal server this morning, I got a dpkg prompt about
/etc/default/zfs. Inspecting the diff showed some paths changed from
/etc to /usr/local/etc:
...
Setting up zfsutils-linux (0.8.3-1ubuntu2) ...
Installing new version of config file /etc/cron.d/zfsutils-linux ...
Configuration file '/etc/default/zfs'
==> Modified (by you or by a script) since installation.
==> Package distributor has shipped an updated version.
What would you like to do about it ? Your options are:
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
The default action is to keep your current version.
*** zfs (Y/I/N/O/D/Z) [default=N] ? d
# Full path to the ZFS cache file?
# See "cachefile" in zpool(8).
-# The default is "/etc/zfs/zpool.cache".
-#ZPOOL_CACHE="/etc/zfs/zpool.cache"
+# The default is "/usr/local/etc/zfs/zpool.cache".
+#ZPOOL_CACHE="/usr/local/etc/zfs/zpool.cache"
#
# Setting ZPOOL_CACHE to an empty string ('') AND setting ZPOOL_IMPORT_OPTS
to
-# "-c /etc/zfs/zpool.cache" will _enforce_ the use of a cache file.
+# "-c /usr/local/etc/zfs/zpool.cache" will _enforce_ the use of a cache file.
# This is needed in some cases (extreme amounts of VDEVs, multipath etc).
# Generally, the use of a cache file is usually not recommended on Linux
# because it sometimes is more trouble than it's worth (laptops with external
# devices or when/if device nodes changes names).
-#ZPOOL_IMPORT_OPTS="-c /etc/zfs/zpool.cache"
+#ZPOOL_IMPORT_OPTS="-c /usr/local/etc/zfs/zpool.cache"
#ZPOOL_CACHE=""
To manage notifications about this bug go to:
https://bugs.launchpad.net/zfs/+bug/1862165/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1872964] Re: Reliable crash in lowlatency kernel with LXD
Please disregard comment #2. These warnings are related to preempt rcu, which is only used in the lowlatency kernel. This seems likely to be caused by an unbalanced rcu_read_lock()/rcu_read_unlock() happening somewhere before the task schedules. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1872964 Title: Reliable crash in lowlatency kernel with LXD Status in linux-signed package in Ubuntu: New Bug description: Hello, I am able to crash 5.4.0-21-lowlatency running LXD. This machine in an Intel NUC, part of a three-member LXD cluster. The other machines do not show this crash and they are not running the lowlatency kernel, but that might be incidental. I will swap out the generic kernel for a while to see if the behaviour continues there. Here is the crash: [ 3222.385724] [ cut here ] [ 3222.385732] WARNING: CPU: 1 PID: 59852 at kernel/rcu/tree_plugin.h:293 rcu_note_context_switch+0x46/0x460 [ 3222.385733] Modules linked in: binfmt_misc veth nft_masq nft_chain_nat vxlan ip6_udp_tunnel udp_tunnel dummy bridge stp llc ebtable_filter ebtables ip6table_raw ip6table_mangle ip6table_nat ip6table_filter ip6_tables iptable_raw iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_filter bpfilter nf_tables nfnetlink unix_diag ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs pps_ldisc zfs(PO) zunicode(PO) zavl(PO) icp(PO) nls_iso8859_1 zcommon(PO) znvpair(PO) spl(O) dm_multipath zlua(PO) scsi_dh_rdac scsi_dh_emc scsi_dh_alua snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio intel_rapl_msr snd_hda_intel mei_hdcp snd_intel_nhlt snd_hda_codec snd_hda_core snd_hwdep intel_rapl_common x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_pcm kvm snd_timer intel_cstate mei_me intel_rapl_perf mei snd soundcore mac_hid acpi_pad sch_fq_codel ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor [ 3222.385779] async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_pclmul crc32_pclmul ghash_clmulni_intel i915 aesni_intel i2c_algo_bit crypto_simd cryptd glue_helper drm_kms_helper syscopyarea sysfillrect sysimgblt e1000e i2c_i801 fb_sys_fops ahci drm libahci lpc_ich video [ 3222.385795] CPU: 1 PID: 59852 Comm: systemd-resolve Tainted: P O 5.4.0-21-lowlatency #25-Ubuntu [ 3222.385796] Hardware name: /NUC5i5MYBE, BIOS MYBDWi5v.86A.0034.2017.0116.2148 01/16/2017 [ 3222.385801] RIP: 0010:rcu_note_context_switch+0x46/0x460 [ 3222.385803] Code: 54 53 48 c7 c3 80 ba 02 00 65 48 03 1d 8b 57 ce 6d 0f 1f 44 00 00 41 8b 85 80 07 00 00 45 84 f6 0f 85 55 02 00 00 85 c0 7e 0c <0f> 0b 41 80 bd 84 07 00 00 00 74 33 4c 89 ef e8 36 fb ff ff 65 66 [ 3222.385804] RSP: 0018:a7bf48e3bcf8 EFLAGS: 00010002 [ 3222.385806] RAX: 0001 RBX: 9817c5caba80 RCX: 0001 [ 3222.385807] RDX: RSI: 92ce6379 RDI: [ 3222.385808] RBP: a7bf48e3bd20 R08: R09: [ 3222.385808] R10: R11: R12: 9817c5caad00 [ 3222.385809] R13: 9816c39ecd00 R14: R15: 0002ad00 [ 3222.385811] FS: 7f9c0f530940() GS:9817c5c8() knlGS: [ 3222.385812] CS: 0010 DS: ES: CR0: 80050033 [ 3222.385812] CR2: 55988bb4b080 CR3: 0003b5e9a005 CR4: 003606e0 [ 3222.385813] DR0: DR1: DR2: [ 3222.385814] DR3: DR6: fffe0ff0 DR7: 0400 [ 3222.385815] Call Trace: [ 3222.385823] __schedule+0x9d/0x750 [ 3222.385826] ? ___sys_sendmsg+0x95/0xd0 [ 3222.385829] schedule+0x49/0xd0 [ 3222.385831] schedule_hrtimeout_range_clock+0xf9/0x110 [ 3222.385834] ? __seccomp_filter+0x85/0x6b0 [ 3222.385837] schedule_hrtimeout_range+0x13/0x20 [ 3222.385839] ep_poll+0x3c8/0x410 [ 3222.385843] ? wake_up_q+0x70/0x70 [ 3222.385845] do_epoll_wait+0xb8/0xd0 [ 3222.385847] __x64_sys_epoll_wait+0x1e/0x30 [ 3222.385850] do_syscall_64+0x57/0x190 [ 3222.385852] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 3222.385854] RIP: 0033:0x7f9c0f04eb77 [ 3222.385856] Code: 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 8d 05 91 ed 2c 00 41 89 ca 8b 00 85 c0 75 18 b8 e8 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 61 f3 c3 0f 1f 80 00 00 00 00 41 55 41 54 41 [ 3222.385857] RSP: 002b:7ffc6fd86d88 EFLAGS: 0246 ORIG_RAX: 00e8 [ 3222.385859] RAX: ffda RBX: 55988d0ad3c0 RCX: 7f9c0f04eb77 [ 3222.385859] RDX: 000e RSI: 7ffc6fd86d90 RDI: 0004 [ 3222.385861] RBP: 7ffc6fd86f40 R08: 7ffc6fd86d90 R09: 55988d0b645c [ 3222.385861] R10:
[Kernel-packages] [Bug 1872757] Re: shiftfs: O_TMPFILE reports ESTALE
** No longer affects: linux (Ubuntu Bionic)
** No longer affects: linux (Ubuntu Xenial)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1872757
Title:
shiftfs: O_TMPFILE reports ESTALE
Status in linux package in Ubuntu:
In Progress
Bug description:
SRU Justification
Impact: Christian Kellner reported that creating temporary files via
O_TMPFILE shiftfs reports ESTALE. This can be reproduced via:
import tempfile
import os
def test():
with tempfile.TemporaryFile() as fd:
fd.write("data".encode('utf-8'))
# re-open the file to get a read-only file descriptor
return open(f"/proc/self/fd/{fd.fileno()}", "r")
def main():
fd = test()
fd.close()
if __name__ == "__main__":
main()
a similar issue was reported here:
https://github.com/systemd/systemd/issues/14861
Fix: Our revalidate methods were very opinionated about whether or not
a dentry was valid when we really should've just let the underlay tell
us what's what. This has led to bugs where a ESTALE was returned for
e.g. temporary files that were created and directly re-opened
afterwards through /proc//fd/. When a file is
re-opened through /proc//fd/ LOOKUP_JUMP is set and the vfs
will revalidate via d_weak_revalidate(). Since the file has been
unhashed or even already gone negative we'd fail the open when we
should've succeeded.
I had also foolishly provided a .tmpfile method which so far only has
caused us trouble. If we really need this then we can reimplement it
properly but I doubt it. Remove it for now.
Regression Potential: Limited to shiftfs.
Test Case: Build a kernel with fix applied and run above reproducer.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872757/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1871688] Re: LIO hanging in iscsit_free_session and iscsit_stop_session
** Changed in: linux (Ubuntu Focal) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1871688 Title: LIO hanging in iscsit_free_session and iscsit_stop_session Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: New Status in linux source package in Bionic: In Progress Status in linux source package in Focal: In Progress Bug description: The target subsystem (LIO) can hang if multiple threads try to destroy iSCSI sessions simultaneously. This is reproducible on systems that have multiple targets with initiators regularly connecting/disconnecting. This may happen when a "targetcli iscsi/iqn.../tpg1 disable" command is executed when a logout operation is underway. The iscsi target doesn't handle such events in a correct way: two or more threads may end up sleeping while waiting for the driver to close the remaining connections on the session. When the connections are closed, the driver wakes up only the first thread that will then proceed to destroy the session structure. The remaining threads are blocked there forever, waiting on a completion synchronization mechanism that doesn't exist in memory anymore because it has been freed by the first thread. Note that if the blocked threads are somehow forced to wake up, they will try to free the same iSCSI session structure destroyed by the first thread, causing double frees, memory corruptions, etc. The driver has been reorganized so the concurrent threads will set a flag in the session structure to notify the driver that the session should be destroyed; then, they wait for the driver to close the remaining connections. When the connections are all closed, the driver will wake up all the threads and will wait for the refcount of the iSCSI session structure to reach zero. When the last thread wakes up, the refcount is decreased to zero and the driver can proceed to destroy the session structure because no one is referencing it anymore. I've witnessed this happening on hundreds of Ubuntu 16.04.5 systems. It is a regression, because this did not occur several years ago. Unfortunately, I don't have detailed records from that far back to determine exactly which kernel I was running that was not affected by this bug (I believe it was either 4.8.x or 4.10.x). I've attached the requested uname, version_signature, dmesg, and lspci from my system. However, I've seen this happen on a wide array of hardware: 2 to 24 cores, 8GB to 256GB RAM, both AMD and Intel CPUs, onboard storage and PCIe SAS cards, etc. This has been fixed in the upstream master branch, but it hasn't yet been backported to "-stable". To fix this in the Ubuntu kernel, these three commits should be backported: * https://github.com/torvalds/linux/commit/e49a7d994379278d3353d7ffc7994672752fb0ad * https://github.com/torvalds/linux/commit/57c46e9f33da530a2485fa01aa27b6d18c28c796 * https://github.com/torvalds/linux/commit/626bac73371eed79e2afa2966de393da96cf925e I'd like these commits to be added to the xenial, bionic, and focal kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871688/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874389] Re: touchpad stops working
Adding psmouse.elantech_smbus=0 into GRUB disabled it completely :D But using only intel graphics instead of nvidia seems to work! Thank you very much! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874389 Title: touchpad stops working Status in linux package in Ubuntu: Triaged Bug description: cat /proc/bus/input/devices I: Bus=0019 Vendor= Product=0003 Version= N: Name="Sleep Button" P: Phys=PNP0C0E/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input0 U: Uniq= H: Handlers=kbd event0 B: PROP=0 B: EV=3 B: KEY=4000 0 0 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/input1 U: Uniq= H: Handlers=event1 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/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=ab54 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=0018 Vendor=04f3 Product=0020 Version= N: Name="Elan Touchpad" P: Phys= S: Sysfs=/devices/pci:00/:00:1f.4/i2c-0/0-0015/input/input7 U: Uniq= H: Handlers=mouse0 event4 B: PROP=5 B: EV=b B: KEY=e520 1 0 0 0 0 B: ABS=66380001303 I: Bus=0018 Vendor=04f3 Product=0020 Version= N: Name="Elan TrackPoint" P: Phys= S: Sysfs=/devices/pci:00/:00:1f.4/i2c-0/0-0015/input/input8 U: Uniq= H: Handlers=mouse1 event5 B: PROP=21 B: EV=7 B: KEY=7 0 0 0 0 B: REL=3 I: Bus=0019 Vendor=17aa Product=5054 Version=4101 N: Name="ThinkPad Extra Buttons" P: Phys=thinkpad_acpi/input0 S: Sysfs=/devices/platform/thinkpad_acpi/input/input6 U: Uniq= H: Handlers=rfkill kbd event6 B: PROP=0 B: EV=33 B: KEY=10040 0 1804 0 50 0 1701b02102004 c000280051115000 10e 0 B: MSC=10 B: SW=8 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/input9 U: Uniq= H: Handlers=kbd event7 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus=0019 Vendor= Product=0006 Version= N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:35/LNXVIDEO:01/input/input10 U: Uniq= H: Handlers=kbd event8 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=event9 B: PROP=0 B: EV=21 B: SW=10 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Headphone" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input12 U: Uniq= H: Handlers=event10 B: PROP=0 B: EV=21 B: SW=4 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=3" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input13 U: Uniq= H: Handlers=event11 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=7" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input14 U: Uniq= H: Handlers=event12 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=8" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input15 U: Uniq= H: Handlers=event13 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=9" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input16 U: Uniq= H: Handlers=event14 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=10" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input17 U: Uniq= H: Handlers=event15 B: PROP=0 B: EV=21 B: SW=140 I: Bus=0003 Vendor=04f2 Product=b604 Version=0027 N: Name="Integrated Camera: Integrated C" P: Phys=usb-:00:14.0-8/button S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-8/1-8:1.0/input/input18 U: Uniq= H: Handlers=kbd eventcat /proc/bus/input/devices 16 B: PROP=0 B: EV=3 B: KEY=10 0 0 0
[Kernel-packages] [Bug 1874435] [NEW] Bluetooth not working with Atheros AR9287
Public bug reported: Bluetooth adapter not visible. In bluetooth menu, we see "no bluetooth found". (Ubuntu 20.04, kernel 5.4.0-26-generic #30-Ubuntu) $ lspci -nnk | grep -iA3 atheros 02:00.0 Network controller [0280]: Qualcomm Atheros AR9287 Wireless Network Adapter (PCI-Express) [168c:002e] (rev 01) Subsystem: Foxconn International, Inc. T77H167.00 [105b:e034] Kernel driver in use: ath9k Kernel modules: ath9k I tried to load the module with btcoex_enable=1, does not help : $ cat /etc/modprobe.d/ath9k-bt.conf options ath9k btcoex_enable=1 $ cat /sys/module/ath9k/parameters/btcoex_enable 1 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "apport report" https://bugs.launchpad.net/bugs/1874435/+attachment/5358422/+files/apport.linux-image-5.4.0-26-generic.8a9o2bv_.apport ** Description changed: Bluetooth adapter not visible. In bluetooth menu, we see "no bluetooth - found". + found". (Ubuntu 20.04, kernel 5.4.0-26-generic #30-Ubuntu) + $ lspci -nnk | grep -iA3 atheros 02:00.0 Network controller [0280]: Qualcomm Atheros AR9287 Wireless Network Adapter (PCI-Express) [168c:002e] (rev 01) - Subsystem: Foxconn International, Inc. T77H167.00 [105b:e034] - Kernel driver in use: ath9k - Kernel modules: ath9k + Subsystem: Foxconn International, Inc. T77H167.00 [105b:e034] + Kernel driver in use: ath9k + Kernel modules: ath9k I tried to load the module with btcoex_enable=1, does not help : - $ cat /etc/modprobe.d/ath9k-bt.conf + $ cat /etc/modprobe.d/ath9k-bt.conf options ath9k btcoex_enable=1 - $ cat /sys/module/ath9k/parameters/btcoex_enable + $ cat /sys/module/ath9k/parameters/btcoex_enable 1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874435 Title: Bluetooth not working with Atheros AR9287 Status in linux package in Ubuntu: New Bug description: Bluetooth adapter not visible. In bluetooth menu, we see "no bluetooth found". (Ubuntu 20.04, kernel 5.4.0-26-generic #30-Ubuntu) $ lspci -nnk | grep -iA3 atheros 02:00.0 Network controller [0280]: Qualcomm Atheros AR9287 Wireless Network Adapter (PCI-Express) [168c:002e] (rev 01) Subsystem: Foxconn International, Inc. T77H167.00 [105b:e034] Kernel driver in use: ath9k Kernel modules: ath9k I tried to load the module with btcoex_enable=1, does not help : $ cat /etc/modprobe.d/ath9k-bt.conf options ath9k btcoex_enable=1 $ cat /sys/module/ath9k/parameters/btcoex_enable 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874435/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1872726] Comment bridged from LTC Bugzilla
--- Comment From niklas.schne...@ibm.com 2020-04-23 08:56 EDT--- Sebastian has supplied me with the following information for reproducing the issue and is currently working on a backport: echo 1 > /sys/class/net/p0/device/sriov_numvfs echo 0101:00:00.0 > /sys/bus/pci/drivers/mlx5_core/unbind devlink dev eswitch set pci/0100:00:00.0 mode switchdev ethtool -K p0 hw-tc-offload on echo 0101:00:00.0 > /sys/bus/pci/drivers/mlx5_core/bind tc qdisc add dev p0 ingress tc qdisc add dev p0v0_r ingress tc filter add dev p0v0_r protocol ip parent :0 prio 1 flower skip_sw action pedit ex munge eth dst set 11:22:33:44:55:66 action goto chain 1 Without the patch the last command would fail with the following output in dmesg [ 548.966006] mlx5_core 0100:00:00.0: mlx5_cmd_check:711:(pid 5220): SET_FLOW_TABLE_ENTRY(0x936) op_mod(0x0) failed, status bad parameter(0x3), syndrome (0x144b7a) This was only tested on Z but we suspect that the same problem should also occur on other Big Endian architectures -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1872726 Title: [Ubuntu 20.04] net/mlx5e: Fix endianness handling in pedit mask Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: New Bug description: Issue found in the Mellanox mlx5 device driver: The mask value is provided as 64 bit and has to be casted in either 32 or 16 bit. On big endian systems the wrong half was casted which resulted in an all zero mask. We need to get the upstream commit picked up for the Ubuntu 20.04 kernel. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=404402abd5f90aa90a134eb9604b1750c1941529 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1872726/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1872757] Re: shiftfs: O_TMPFILE reports ESTALE
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Status: New => In Progress
** Changed in: linux (Ubuntu Bionic)
Status: New => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1872757
Title:
shiftfs: O_TMPFILE reports ESTALE
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
In Progress
Status in linux source package in Bionic:
In Progress
Bug description:
SRU Justification
Impact: Christian Kellner reported that creating temporary files via
O_TMPFILE shiftfs reports ESTALE. This can be reproduced via:
import tempfile
import os
def test():
with tempfile.TemporaryFile() as fd:
fd.write("data".encode('utf-8'))
# re-open the file to get a read-only file descriptor
return open(f"/proc/self/fd/{fd.fileno()}", "r")
def main():
fd = test()
fd.close()
if __name__ == "__main__":
main()
a similar issue was reported here:
https://github.com/systemd/systemd/issues/14861
Fix: Our revalidate methods were very opinionated about whether or not
a dentry was valid when we really should've just let the underlay tell
us what's what. This has led to bugs where a ESTALE was returned for
e.g. temporary files that were created and directly re-opened
afterwards through /proc//fd/. When a file is
re-opened through /proc//fd/ LOOKUP_JUMP is set and the vfs
will revalidate via d_weak_revalidate(). Since the file has been
unhashed or even already gone negative we'd fail the open when we
should've succeeded.
I had also foolishly provided a .tmpfile method which so far only has
caused us trouble. If we really need this then we can reimplement it
properly but I doubt it. Remove it for now.
Regression Potential: Limited to shiftfs.
Test Case: Build a kernel with fix applied and run above reproducer.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872757/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874437] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874437 Title: Network driver for e1000 card not loaded on boot on beta 20.04 Status in linux package in Ubuntu: Confirmed Bug description: Hi The symptons are: I was running 20.04 Desktop Beta - everything was ok, I have an on board network card 00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network Connection (Lewisville) (rev 04) After patching on 20th April - the network dissappeard - not the device mind you. When you did ip a - you got 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever I tried downloading the latest as in the build on 20th but on boot from USB - it does not gring up the network My hack - install another 100M pci card - this caused the network drivers to be loaded and both cards to work. Current state of play: 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: enp5s2: mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000 link/ether 00:40:f4:28:8f:30 brd ff:ff:ff:ff:ff:ff 3: enp0s25: mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 18:03:73:d8:e9:94 brd ff:ff:ff:ff:ff:ff inet 192.168.0.25/24 brd 192.168.0.255 scope global noprefixroute enp0s25 valid_lft forever preferred_lft forever inet6 fe80::1a03:73ff:fed8:e994/64 scope link valid_lft forever preferred_lft forever 6: enx424d7f654382: mtu 1500 qdisc fq_codel state DOWN group default qlen 1000 link/ether 42:4d:7f:65:43:82 brd ff:ff:ff:ff:ff:ff enp0s25 is detected and working. If I unplug the ethernet to the 100M card that is a: 05:02.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8100/8101L/8139 PCI Fast Ethernet Adapter (rev 10) then the network stops working! Well weird. Many thanks for the help. But I expect I cant be the only person with this issue the intel 1000m card is quite popular - the system is a Dell t1600 xeon 5.4.0-26-generic #30-Ubuntu SMP Mon Apr 20 16:58:30 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Cheers Naveed 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 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Thu Apr 23 13:43:52 2020 InstallationDate: Installed on 2020-04-21 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200417) MachineType: Dell Inc. Precision T1600 ProcFB: 0 nouveaudrmfb 1 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=423f52c8-113b-4bd6-bebe-62233a48aceb ro quiet splash vt.handoff=7 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: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/07/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 06NWYK dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd05/07/2017:svnDellInc.:pnPrecisionT1600:pvr01:rvnDellInc.:rn06NWYK:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: Precision T1600 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874437/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874437] [NEW] Network driver for e1000 card not loaded on boot on beta 20.04
Public bug reported: Hi The symptons are: I was running 20.04 Desktop Beta - everything was ok, I have an on board network card 00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network Connection (Lewisville) (rev 04) After patching on 20th April - the network dissappeard - not the device mind you. When you did ip a - you got 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever I tried downloading the latest as in the build on 20th but on boot from USB - it does not gring up the network My hack - install another 100M pci card - this caused the network drivers to be loaded and both cards to work. Current state of play: 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: enp5s2: mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000 link/ether 00:40:f4:28:8f:30 brd ff:ff:ff:ff:ff:ff 3: enp0s25: mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 18:03:73:d8:e9:94 brd ff:ff:ff:ff:ff:ff inet 192.168.0.25/24 brd 192.168.0.255 scope global noprefixroute enp0s25 valid_lft forever preferred_lft forever inet6 fe80::1a03:73ff:fed8:e994/64 scope link valid_lft forever preferred_lft forever 6: enx424d7f654382: mtu 1500 qdisc fq_codel state DOWN group default qlen 1000 link/ether 42:4d:7f:65:43:82 brd ff:ff:ff:ff:ff:ff enp0s25 is detected and working. If I unplug the ethernet to the 100M card that is a: 05:02.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8100/8101L/8139 PCI Fast Ethernet Adapter (rev 10) then the network stops working! Well weird. Many thanks for the help. But I expect I cant be the only person with this issue the intel 1000m card is quite popular - the system is a Dell t1600 xeon 5.4.0-26-generic #30-Ubuntu SMP Mon Apr 20 16:58:30 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Cheers Naveed 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 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Thu Apr 23 13:43:52 2020 InstallationDate: Installed on 2020-04-21 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200417) MachineType: Dell Inc. Precision T1600 ProcFB: 0 nouveaudrmfb 1 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=423f52c8-113b-4bd6-bebe-62233a48aceb ro quiet splash vt.handoff=7 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: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/07/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 06NWYK dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd05/07/2017:svnDellInc.:pnPrecisionT1600:pvr01:rvnDellInc.:rn06NWYK:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: Precision T1600 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874437 Title: Network driver for e1000 card not loaded on boot on beta 20.04 Status in linux package in Ubuntu: Confirmed Bug description: Hi The symptons are: I was running 20.04 Desktop Beta - everything was ok, I have an on board network card 00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network Connection (Lewisville) (rev 04) After patching on 20th April - the network dissappeard - not the device mind you. When you did ip a - you got 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever I tried downloading the latest as in the build on 20th but on boot from USB - it does not gring up the network My hack - install another 100M pci card - this caused the network drivers to be loaded and both cards to work. Current state of play: 1: lo: mtu 65536
[Kernel-packages] [Bug 1874435] 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 1874435 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/1874435 Title: Bluetooth not working with Atheros AR9287 Status in linux package in Ubuntu: Incomplete Bug description: Bluetooth adapter not visible. In bluetooth menu, we see "no bluetooth found". (Ubuntu 20.04, kernel 5.4.0-26-generic #30-Ubuntu) $ lspci -nnk | grep -iA3 atheros 02:00.0 Network controller [0280]: Qualcomm Atheros AR9287 Wireless Network Adapter (PCI-Express) [168c:002e] (rev 01) Subsystem: Foxconn International, Inc. T77H167.00 [105b:e034] Kernel driver in use: ath9k Kernel modules: ath9k I tried to load the module with btcoex_enable=1, does not help : $ cat /etc/modprobe.d/ath9k-bt.conf options ath9k btcoex_enable=1 $ cat /sys/module/ath9k/parameters/btcoex_enable 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874435/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874422] Re: [Ubuntu 20.04] FIPS: libica: TDES key check must change
** Package changed: linux (Ubuntu) => libica (Ubuntu) ** Also affects: ubuntu-z-systems 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/1874422 Title: [Ubuntu 20.04] FIPS: libica: TDES key check must change Status in Ubuntu on IBM z Systems: New Status in libica package in Ubuntu: New Bug description: Please add the problem description and the git-commit to this BZ. Following versions are available. xenial (16.04LTS) 2.6.1-1ubuntu1 [ports]: s390x bionic (18.04LTS) 3.2.1-0ubuntu1 [ports]: s390x eoan (19.10) 3.6.0-0ubuntu1 [ports]: s390x focal (20.04) 3.6.1-0ubuntu1 [ports]: s390x Fixed upstream with commit: https://github.com/opencryptoki/libica/commit/db1ad6f64d96c6dba2be5af5a4ecd7ceb8f92cf2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874422/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1748103] Re: apic test in kvm-unit-test failed with timeout
On E-KVM, the apic test will take about 1 minute to run: SUMMARY: 51 tests, 1 unexpected failures FAIL apic-split (51 tests, 1 unexpected failures) real1m7.991s user2m0.543s sys 0m11.881s On B-Oracle (VM.Standard2.16). the apic test will take about 3 minute to run: SUMMARY: 51 tests, 1 unexpected failures, 1 skipped FAIL apic (51 tests, 1 unexpected failures, 1 skipped) real2m59.177s user2m24.763s sys 3m32.041s ** Summary changed: - apic test in kvm-unit-test failed + apic test in kvm-unit-test failed with timeout -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1748103 Title: apic test in kvm-unit-test failed with timeout Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Incomplete Status in linux-azure package in Ubuntu: New Status in linux-azure-edge package in Ubuntu: New Status in linux source package in Xenial: New Status in linux-azure source package in Xenial: New Status in linux-azure-edge source package in Xenial: New Status in linux source package in Bionic: New Status in linux-azure source package in Bionic: New Status in linux-azure-edge source package in Bionic: New Bug description: With Joshua's comment in bug 1719524: "Nested KVM can only be tried on instance sizes with nested Hypervisor support: Ev3 and Dv3.", although the instance name is E4v3 here but I can start a KVM on it. Test apic will timeout on it. Steps: 1. git clone --depth=1 https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git 2. cd kvm-unit-tests; ./configure; make 3. Run the apic test as root: # TESTNAME=apic TIMEOUT=30 ACCEL= ./x86/run x86/apic.flat -smp 2 -cpu qemu64,+x2apic,+tsc-deadline timeout -k 1s --foreground 30 /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel x86/apic.flat -smp 2 -cpu qemu64,+x2apic,+tsc-deadline # -initrd /tmp/tmp.onXtr5JVp7 enabling apic enabling apic paging enabled cr0 = 80010011 cr3 = 459000 cr4 = 20 apic version: 1050014 PASS: apic existence PASS: xapic id matches cpuid PASS: writeable xapic id PASS: non-writeable x2apic id PASS: sane x2apic id FAIL: x2apic id matches cpuid PASS: correct xapic id after reset PASS: apic_disable: Local apic enabled PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is set PASS: apic_disable: Local apic disabled PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is clear PASS: apic_disable: Local apic enabled PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is set x2apic enabled PASS: x2apic enabled to invalid state PASS: x2apic enabled to apic enabled PASS: disabled to invalid state PASS: disabled to x2apic enabled PASS: apic enabled to invalid state PASS: apicbase: relocate apic PASS: apicbase: reserved physaddr bits PASS: apicbase: reserved low bits PASS: self ipi starting broadcast (x2apic) PASS: APIC physical broadcast address PASS: APIC physical broadcast shorthand PASS: nmi-after-sti qemu-system-x86_64: terminating on signal 15 from pid 7246 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.14.0-1004-azure-edge 4.14.0-1004.4 ProcVersionSignature: User Name 4.14.0-1004.4-username-edge 4.14.14 Uname: Linux 4.14.0-1004-azure-edge x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Thu Feb 8 06:00:55 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-azure-edge UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 DistroRelease: Ubuntu 16.04 Package: linux-azure-edge PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: User Name 4.13.0-1009.12-username 4.13.13 Tags: xenial uec-images Uname: Linux 4.13.0-1009-azure x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy libvirtd lxd netdev plugdev sudo video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1748103/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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.
*** This bug is a duplicate of bug 1835660 *** https://bugs.launchpad.net/bugs/1835660 ** This bug has been marked a duplicate of bug 1835660 initramfs unpacking failed -- You 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 1774359] Re: could not find module by name='off'
Just upgraded from Ubuntu 16 to 18.04. In my case the problem arises when I unload the driver and then try to load it again. After the error dmesg states the possible cause: [ 966.030549] NVRM: API mismatch: the client has the version 390.116, but NVRM: this kernel module has the version 384.130. Please NVRM: make sure that this kernel module and all NVIDIA driver NVRM: components have the same version. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1774359 Title: could not find module by name='off' Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: When I try to load the nvidia module it doesn't load. $ sudo modprobe nvidia modprobe: ERROR: ../libkmod/libkmod-module.c:832 kmod_module_insert_module() could not find module by name='off' modprobe: ERROR: could not insert 'off': Unknown symbol in module, or unknown parameter (see dmesg) $ sudo prime-select query intel $ sudo prime-offload $ cat /var/log/prime-supported.log Requires offloading $ cat /var/log/prime-offload.log Sorry the nvidia kernel module is not is loaded ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-kernel-common-390 390.48-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu May 31 09:42:42 2018 Dependencies: InstallationDate: Installed on 2018-05-30 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-graphics-drivers-390 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1774359/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1871430] Re: iwlwifi/iwlmvm & Intel 9260 [8086:2526] subsystem [8086:0014] made kernel unstable since 4.15.0-91
With kernel 4.15.0-96 it started rebooting with weekly intervals (did so on Apr 9th, 16th, 23rd). Also as you know AR9271 is notorious for its hanging firmware, so for some of these reboots I had to unplug-replug it in its USB port, else Linux could not complete its boot. In the nearest weekend I would get a Raspberry Pi to make a netconsole log collector and provide more information. Please keep this bug open, don't close it by any timeout. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1871430 Title: iwlwifi/iwlmvm & Intel 9260 [8086:2526] subsystem [8086:0014] made kernel unstable since 4.15.0-91 Status in linux package in Ubuntu: Incomplete Bug description: My home server/router/access point runs under Ubuntu 18.04.4 with all updates and has 2 wifi adapters operated by hostapd one is USB AR9271 (0cf3:9271, driver ath9k_htc), another is PCIe Intel AC 9260 (8086:2526, driver iwlwifi). with kernel 4.15.0-88 it worked quite stable, with reboots required mostly after kernel upgrades (much less frequent reboots due to panics) with kernel 4.15.0-91 and -96 it started rebooting by itself by panic when a lot of activity happening via Intel 9260. In /etc/sysctl* I have kernel.panic=10 , kernel.softlockup_panic=1 and kernel.panic_on_oops=1 overrides of default values. In dmesg logs preceding the reboot, I see multiple warnings with stacks inside iwl_mvm functions which I could provide by apport. Also, multiple messages like "Command LQ_CMD: a command is already active!" or "Error sending LQ_CMD: time out after 2000ms" Unfortunately I run this box headless and I don't have another wired Ethernet host to capture its panics by netconsole The rest of hardware is pretty standard. Asus B85M-G mobo, Core i3-4130T CPU, nothing overly special. More details I would provide in your further requests but the current kernel behavior is very annoying. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 HibernationDevice: #RESUME=UUID=f7bcdeb1-6c61-4012-81c4-a43a492ffb6e InstallationDate: Installed on 2009-11-01 (3810 days ago) InstallationMedia: Kubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) MachineType: ASUS All Series Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-96-generic root=/dev/mapper/vg00-root64 ro rootflags=commit=3600 rootflags=commit=3600 loop.max_part=63 ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-96-generic N/A linux-backports-modules-4.15.0-96-generic N/A linux-firmware 1.173.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-96-generic x86_64 UpgradeStatus: Upgraded to bionic on 2010-10-11 (3466 days ago) UserGroups: adm admin audio cdrom dialout dip disk dos fuse jabber kvm libvirt libvirtd lpadmin plugdev proxy pulse pulse-access sambashare src _MarkForUpload: True dmi.bios.date: 07/22/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-G 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.:bvr2501:bd07/22/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB85M-G:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871430/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1872001] Re: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0
#57 this works. Hard to install on 18.04 though, you need the headers package (linux- headers-5.3.0-48_5.3.0-48.41_all.deb) from eoan -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1872001 Title: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0 Status in linux package in Ubuntu: Confirmed Status in linux source package in Eoan: In Progress Bug description: Hi, Since update to HWE kernel 5.3.0-46-generic I am experiencing frequent (every couple of minutes) GPU hangs and reset manifesting as 2-3 seconds freezes of the GUI (other than the mouse pointer). No particular triggers identified although have Chrome / Chromium running with Hardware Acceleration enabled does appear to increase the frequency. I have seen incidences of these hangs in jounralctl output using previous kernels in the 5.3.0-xx series but they were very infrequent (one or twice in a week of daily usage) System Info steve@steve-Inspiron-5580:~$ inxi -SCGxxxz System:Host: steve-Inspiron-5580 Kernel: 5.3.0-46-generic x86_64 bits: 64 compiler: gcc v: 7.5.0 Desktop: Cinnamon 4.4.8 wm: muffin 4.4.2 dm: LightDM 1.26.0 Distro: Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic CPU: Topology: Quad Core model: Intel Core i5-8265U bits: 64 type: MT MCP arch: Kaby Lake rev: B L2 cache: 6144 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 28800 Speed: 1173 MHz min/max: 400/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 Graphics: Device-1: Intel vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:3ea0 Display: x11 server: X.Org 1.20.5 driver: modesetting unloaded: fbdev,vesa resolution: 1920x1080~60Hz OpenGL: renderer: Mesa DRI Intel UHD Graphics (Whiskey Lake 3x8 GT2) v: 4.5 Mesa 19.2.8 compat-v: 3.0 direct render: Yes steve@steve-Inspiron-5580:~$ journalctl -b | grep i915 Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: vgaarb: deactivate vga console Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem Apr 10 06:15:17 steve-Inspiron-5580 kernel: [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4) Apr 10 06:15:17 steve-Inspiron-5580 kernel: [drm] Initialized i915 1.6.0 20190619 for :00:02.0 on minor 0 Apr 10 06:15:17 steve-Inspiron-5580 kernel: fbcon: i915drmfb (fb0) is primary device Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: fb0: i915drmfb frame buffer device Apr 10 06:15:17 steve-Inspiron-5580 kernel: snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) Apr 10 06:16:28 steve-Inspiron-5580 kernel: i915 :00:02.0: GPU HANG: ecode 9:0:0x, hang on rcs0 Apr 10 06:16:28 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:31:46 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:37:48 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:40:46 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 I note another user has reported similar issues on the same kernel at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861395/comments/52 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: steve 3920 F pulseaudio /dev/snd/pcmC0D0p: steve 3920 F...m pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.3 HibernationDevice: RESUME=none InstallationDate: Installed on 2019-12-27 (104 days ago) InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213 MachineType: Dell Inc. Inspiron 5580 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic root=UUID=b0eaa5bb-0276-42d4-938f-ee6ce1627906 ro usb_storage.quirks=0bc2:2320: quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-46-generic N/A linux-backports-modules-5.3.0-46-generic N/A linux-firmware1.173.17 Tags: tricia Uname: Linux 5.3.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 07/02/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 0K0DFT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell
[Kernel-packages] [Bug 1870275] Re: initramfs unpacking failed: Decoding failed after every boot
*** This bug is a duplicate of bug 1835660 *** https://bugs.launchpad.net/bugs/1835660 ** This bug is no longer a duplicate of bug 1870260 initramfs unpacking failed: Decoding failed", message appears on boot up. ** This bug has been marked a duplicate of bug 1835660 initramfs unpacking failed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1870275 Title: initramfs unpacking failed: Decoding failed after every boot Status in linux 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: USER PID 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-firmware 1.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 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tamal 1456 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: linux (not installed) 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
[Kernel-packages] [Bug 1872964] Re: Reliable crash in lowlatency kernel with LXD
When you see this in -24, is that still the lowlatency kernel or had you switched it out for generic like you mentioned in the description? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1872964 Title: Reliable crash in lowlatency kernel with LXD Status in linux-signed package in Ubuntu: New Bug description: Hello, I am able to crash 5.4.0-21-lowlatency running LXD. This machine in an Intel NUC, part of a three-member LXD cluster. The other machines do not show this crash and they are not running the lowlatency kernel, but that might be incidental. I will swap out the generic kernel for a while to see if the behaviour continues there. Here is the crash: [ 3222.385724] [ cut here ] [ 3222.385732] WARNING: CPU: 1 PID: 59852 at kernel/rcu/tree_plugin.h:293 rcu_note_context_switch+0x46/0x460 [ 3222.385733] Modules linked in: binfmt_misc veth nft_masq nft_chain_nat vxlan ip6_udp_tunnel udp_tunnel dummy bridge stp llc ebtable_filter ebtables ip6table_raw ip6table_mangle ip6table_nat ip6table_filter ip6_tables iptable_raw iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_filter bpfilter nf_tables nfnetlink unix_diag ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs pps_ldisc zfs(PO) zunicode(PO) zavl(PO) icp(PO) nls_iso8859_1 zcommon(PO) znvpair(PO) spl(O) dm_multipath zlua(PO) scsi_dh_rdac scsi_dh_emc scsi_dh_alua snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio intel_rapl_msr snd_hda_intel mei_hdcp snd_intel_nhlt snd_hda_codec snd_hda_core snd_hwdep intel_rapl_common x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_pcm kvm snd_timer intel_cstate mei_me intel_rapl_perf mei snd soundcore mac_hid acpi_pad sch_fq_codel ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor [ 3222.385779] async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_pclmul crc32_pclmul ghash_clmulni_intel i915 aesni_intel i2c_algo_bit crypto_simd cryptd glue_helper drm_kms_helper syscopyarea sysfillrect sysimgblt e1000e i2c_i801 fb_sys_fops ahci drm libahci lpc_ich video [ 3222.385795] CPU: 1 PID: 59852 Comm: systemd-resolve Tainted: P O 5.4.0-21-lowlatency #25-Ubuntu [ 3222.385796] Hardware name: /NUC5i5MYBE, BIOS MYBDWi5v.86A.0034.2017.0116.2148 01/16/2017 [ 3222.385801] RIP: 0010:rcu_note_context_switch+0x46/0x460 [ 3222.385803] Code: 54 53 48 c7 c3 80 ba 02 00 65 48 03 1d 8b 57 ce 6d 0f 1f 44 00 00 41 8b 85 80 07 00 00 45 84 f6 0f 85 55 02 00 00 85 c0 7e 0c <0f> 0b 41 80 bd 84 07 00 00 00 74 33 4c 89 ef e8 36 fb ff ff 65 66 [ 3222.385804] RSP: 0018:a7bf48e3bcf8 EFLAGS: 00010002 [ 3222.385806] RAX: 0001 RBX: 9817c5caba80 RCX: 0001 [ 3222.385807] RDX: RSI: 92ce6379 RDI: [ 3222.385808] RBP: a7bf48e3bd20 R08: R09: [ 3222.385808] R10: R11: R12: 9817c5caad00 [ 3222.385809] R13: 9816c39ecd00 R14: R15: 0002ad00 [ 3222.385811] FS: 7f9c0f530940() GS:9817c5c8() knlGS: [ 3222.385812] CS: 0010 DS: ES: CR0: 80050033 [ 3222.385812] CR2: 55988bb4b080 CR3: 0003b5e9a005 CR4: 003606e0 [ 3222.385813] DR0: DR1: DR2: [ 3222.385814] DR3: DR6: fffe0ff0 DR7: 0400 [ 3222.385815] Call Trace: [ 3222.385823] __schedule+0x9d/0x750 [ 3222.385826] ? ___sys_sendmsg+0x95/0xd0 [ 3222.385829] schedule+0x49/0xd0 [ 3222.385831] schedule_hrtimeout_range_clock+0xf9/0x110 [ 3222.385834] ? __seccomp_filter+0x85/0x6b0 [ 3222.385837] schedule_hrtimeout_range+0x13/0x20 [ 3222.385839] ep_poll+0x3c8/0x410 [ 3222.385843] ? wake_up_q+0x70/0x70 [ 3222.385845] do_epoll_wait+0xb8/0xd0 [ 3222.385847] __x64_sys_epoll_wait+0x1e/0x30 [ 3222.385850] do_syscall_64+0x57/0x190 [ 3222.385852] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 3222.385854] RIP: 0033:0x7f9c0f04eb77 [ 3222.385856] Code: 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 8d 05 91 ed 2c 00 41 89 ca 8b 00 85 c0 75 18 b8 e8 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 61 f3 c3 0f 1f 80 00 00 00 00 41 55 41 54 41 [ 3222.385857] RSP: 002b:7ffc6fd86d88 EFLAGS: 0246 ORIG_RAX: 00e8 [ 3222.385859] RAX: ffda RBX: 55988d0ad3c0 RCX: 7f9c0f04eb77 [ 3222.385859] RDX: 000e RSI: 7ffc6fd86d90 RDI: 0004 [ 3222.385861] RBP: 7ffc6fd86f40 R08: 7ffc6fd86d90 R09: 55988d0b645c [ 3222.385861] R10: R11: 0246 R12: 00cf [ 3222.385862] R13: R14:
[Kernel-packages] [Bug 1874305] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1874305/+attachment/5358417/+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/1874305 Title: Wifi goes down when change bluetooth configuration Status in linux package in Ubuntu: Incomplete Bug description: WiFi connection goes down when having a Bluetooth headset connected and change from A2DP to HSP. The connection goes down instantly. If you change back to A2DP connection works again, but in some cases it goes down forever till you disconnect from the current WiFi and connect again. [How to reproduce] 1. connect a Bluetooth headset and change from A2DP to HSP. [System Info] Ubuntu 5.4.0-24.28-generic 5.4.30 03:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 31) No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 20.04 LTS Release: 20.04 Codename:focal [DMESG info] 348674.114861] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114864] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114866] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114869] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114873] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114876] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114879] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114882] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114885] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114888] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114891] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114894] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114897] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114900] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114903] Bluetooth: hci0: SCO packet for unknown connection handle 3072 [348674.114906] Bluetooth: hci0: SCO packet for unknown connection handle 48 [348674.114909] Bluetooth: hci0: SCO packet for unknown connection handle 0 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: leosilva 6150 F pulseaudio /dev/snd/pcmC1D7p: leosilva 6150 F...m pulseaudio /dev/snd/controlC0: leosilva 6150 F pulseaudio /dev/snd/pcmC0D8p: leosilva 6150 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-02 (111 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200102) MachineType: Dell Inc. XPS 8930 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA 1 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-24-generic root=UUID=bb691d80-94d7-4044-844f-c0df45ba89ca ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-24-generic N/A linux-backports-modules-5.4.0-24-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-24-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 libvirt lpadmin lxd plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 10/31/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.10 dmi.board.name: 06HKRH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.1.10:bd10/31/2019:svnDellInc.:pnXPS8930:pvr1.1.10:rvnDellInc.:rn06HKRH:rvrA00:cvnDellInc.:ct3:cvrNotSpecified: dmi.product.family: XPS dmi.product.name: XPS 8930 dmi.product.sku: 0859 dmi.product.version: 1.1.10 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874305/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874305] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1874305/+attachment/5358418/+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/1874305 Title: Wifi goes down when change bluetooth configuration Status in linux package in Ubuntu: Incomplete Bug description: WiFi connection goes down when having a Bluetooth headset connected and change from A2DP to HSP. The connection goes down instantly. If you change back to A2DP connection works again, but in some cases it goes down forever till you disconnect from the current WiFi and connect again. [How to reproduce] 1. connect a Bluetooth headset and change from A2DP to HSP. [System Info] Ubuntu 5.4.0-24.28-generic 5.4.30 03:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 31) No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 20.04 LTS Release: 20.04 Codename:focal [DMESG info] 348674.114861] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114864] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114866] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114869] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114873] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114876] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114879] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114882] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114885] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114888] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114891] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114894] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114897] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114900] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114903] Bluetooth: hci0: SCO packet for unknown connection handle 3072 [348674.114906] Bluetooth: hci0: SCO packet for unknown connection handle 48 [348674.114909] Bluetooth: hci0: SCO packet for unknown connection handle 0 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: leosilva 6150 F pulseaudio /dev/snd/pcmC1D7p: leosilva 6150 F...m pulseaudio /dev/snd/controlC0: leosilva 6150 F pulseaudio /dev/snd/pcmC0D8p: leosilva 6150 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-02 (111 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200102) MachineType: Dell Inc. XPS 8930 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA 1 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-24-generic root=UUID=bb691d80-94d7-4044-844f-c0df45ba89ca ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-24-generic N/A linux-backports-modules-5.4.0-24-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-24-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 libvirt lpadmin lxd plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 10/31/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.10 dmi.board.name: 06HKRH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.1.10:bd10/31/2019:svnDellInc.:pnXPS8930:pvr1.1.10:rvnDellInc.:rn06HKRH:rvrA00:cvnDellInc.:ct3:cvrNotSpecified: dmi.product.family: XPS dmi.product.name: XPS 8930 dmi.product.sku: 0859 dmi.product.version: 1.1.10 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874305/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874305] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1874305/+attachment/5358409/+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/1874305 Title: Wifi goes down when change bluetooth configuration Status in linux package in Ubuntu: Incomplete Bug description: WiFi connection goes down when having a Bluetooth headset connected and change from A2DP to HSP. The connection goes down instantly. If you change back to A2DP connection works again, but in some cases it goes down forever till you disconnect from the current WiFi and connect again. [How to reproduce] 1. connect a Bluetooth headset and change from A2DP to HSP. [System Info] Ubuntu 5.4.0-24.28-generic 5.4.30 03:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 31) No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 20.04 LTS Release: 20.04 Codename:focal [DMESG info] 348674.114861] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114864] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114866] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114869] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114873] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114876] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114879] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114882] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114885] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114888] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114891] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114894] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114897] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114900] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114903] Bluetooth: hci0: SCO packet for unknown connection handle 3072 [348674.114906] Bluetooth: hci0: SCO packet for unknown connection handle 48 [348674.114909] Bluetooth: hci0: SCO packet for unknown connection handle 0 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: leosilva 6150 F pulseaudio /dev/snd/pcmC1D7p: leosilva 6150 F...m pulseaudio /dev/snd/controlC0: leosilva 6150 F pulseaudio /dev/snd/pcmC0D8p: leosilva 6150 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-02 (111 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200102) MachineType: Dell Inc. XPS 8930 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA 1 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-24-generic root=UUID=bb691d80-94d7-4044-844f-c0df45ba89ca ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-24-generic N/A linux-backports-modules-5.4.0-24-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-24-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 libvirt lpadmin lxd plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 10/31/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.10 dmi.board.name: 06HKRH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.1.10:bd10/31/2019:svnDellInc.:pnXPS8930:pvr1.1.10:rvnDellInc.:rn06HKRH:rvrA00:cvnDellInc.:ct3:cvrNotSpecified: dmi.product.family: XPS dmi.product.name: XPS 8930 dmi.product.sku: 0859 dmi.product.version: 1.1.10 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874305/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874305] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1874305/+attachment/5358419/+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/1874305 Title: Wifi goes down when change bluetooth configuration Status in linux package in Ubuntu: Incomplete Bug description: WiFi connection goes down when having a Bluetooth headset connected and change from A2DP to HSP. The connection goes down instantly. If you change back to A2DP connection works again, but in some cases it goes down forever till you disconnect from the current WiFi and connect again. [How to reproduce] 1. connect a Bluetooth headset and change from A2DP to HSP. [System Info] Ubuntu 5.4.0-24.28-generic 5.4.30 03:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 31) No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 20.04 LTS Release: 20.04 Codename:focal [DMESG info] 348674.114861] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114864] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114866] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114869] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114873] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114876] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114879] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114882] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114885] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114888] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114891] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114894] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114897] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114900] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114903] Bluetooth: hci0: SCO packet for unknown connection handle 3072 [348674.114906] Bluetooth: hci0: SCO packet for unknown connection handle 48 [348674.114909] Bluetooth: hci0: SCO packet for unknown connection handle 0 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: leosilva 6150 F pulseaudio /dev/snd/pcmC1D7p: leosilva 6150 F...m pulseaudio /dev/snd/controlC0: leosilva 6150 F pulseaudio /dev/snd/pcmC0D8p: leosilva 6150 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-02 (111 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200102) MachineType: Dell Inc. XPS 8930 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA 1 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-24-generic root=UUID=bb691d80-94d7-4044-844f-c0df45ba89ca ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-24-generic N/A linux-backports-modules-5.4.0-24-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-24-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 libvirt lpadmin lxd plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 10/31/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.10 dmi.board.name: 06HKRH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.1.10:bd10/31/2019:svnDellInc.:pnXPS8930:pvr1.1.10:rvnDellInc.:rn06HKRH:rvrA00:cvnDellInc.:ct3:cvrNotSpecified: dmi.product.family: XPS dmi.product.name: XPS 8930 dmi.product.sku: 0859 dmi.product.version: 1.1.10 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874305/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874305] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1874305/+attachment/5358413/+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/1874305 Title: Wifi goes down when change bluetooth configuration Status in linux package in Ubuntu: Incomplete Bug description: WiFi connection goes down when having a Bluetooth headset connected and change from A2DP to HSP. The connection goes down instantly. If you change back to A2DP connection works again, but in some cases it goes down forever till you disconnect from the current WiFi and connect again. [How to reproduce] 1. connect a Bluetooth headset and change from A2DP to HSP. [System Info] Ubuntu 5.4.0-24.28-generic 5.4.30 03:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 31) No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 20.04 LTS Release: 20.04 Codename:focal [DMESG info] 348674.114861] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114864] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114866] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114869] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114873] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114876] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114879] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114882] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114885] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114888] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114891] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114894] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114897] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114900] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114903] Bluetooth: hci0: SCO packet for unknown connection handle 3072 [348674.114906] Bluetooth: hci0: SCO packet for unknown connection handle 48 [348674.114909] Bluetooth: hci0: SCO packet for unknown connection handle 0 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: leosilva 6150 F pulseaudio /dev/snd/pcmC1D7p: leosilva 6150 F...m pulseaudio /dev/snd/controlC0: leosilva 6150 F pulseaudio /dev/snd/pcmC0D8p: leosilva 6150 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-02 (111 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200102) MachineType: Dell Inc. XPS 8930 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA 1 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-24-generic root=UUID=bb691d80-94d7-4044-844f-c0df45ba89ca ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-24-generic N/A linux-backports-modules-5.4.0-24-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-24-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 libvirt lpadmin lxd plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 10/31/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.10 dmi.board.name: 06HKRH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.1.10:bd10/31/2019:svnDellInc.:pnXPS8930:pvr1.1.10:rvnDellInc.:rn06HKRH:rvrA00:cvnDellInc.:ct3:cvrNotSpecified: dmi.product.family: XPS dmi.product.name: XPS 8930 dmi.product.sku: 0859 dmi.product.version: 1.1.10 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874305/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874305] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1874305/+attachment/5358411/+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/1874305 Title: Wifi goes down when change bluetooth configuration Status in linux package in Ubuntu: Incomplete Bug description: WiFi connection goes down when having a Bluetooth headset connected and change from A2DP to HSP. The connection goes down instantly. If you change back to A2DP connection works again, but in some cases it goes down forever till you disconnect from the current WiFi and connect again. [How to reproduce] 1. connect a Bluetooth headset and change from A2DP to HSP. [System Info] Ubuntu 5.4.0-24.28-generic 5.4.30 03:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 31) No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 20.04 LTS Release: 20.04 Codename:focal [DMESG info] 348674.114861] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114864] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114866] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114869] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114873] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114876] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114879] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114882] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114885] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114888] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114891] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114894] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114897] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114900] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114903] Bluetooth: hci0: SCO packet for unknown connection handle 3072 [348674.114906] Bluetooth: hci0: SCO packet for unknown connection handle 48 [348674.114909] Bluetooth: hci0: SCO packet for unknown connection handle 0 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: leosilva 6150 F pulseaudio /dev/snd/pcmC1D7p: leosilva 6150 F...m pulseaudio /dev/snd/controlC0: leosilva 6150 F pulseaudio /dev/snd/pcmC0D8p: leosilva 6150 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-02 (111 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200102) MachineType: Dell Inc. XPS 8930 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA 1 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-24-generic root=UUID=bb691d80-94d7-4044-844f-c0df45ba89ca ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-24-generic N/A linux-backports-modules-5.4.0-24-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-24-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 libvirt lpadmin lxd plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 10/31/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.10 dmi.board.name: 06HKRH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.1.10:bd10/31/2019:svnDellInc.:pnXPS8930:pvr1.1.10:rvnDellInc.:rn06HKRH:rvrA00:cvnDellInc.:ct3:cvrNotSpecified: dmi.product.family: XPS dmi.product.name: XPS 8930 dmi.product.sku: 0859 dmi.product.version: 1.1.10 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874305/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874305] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1874305/+attachment/5358415/+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/1874305 Title: Wifi goes down when change bluetooth configuration Status in linux package in Ubuntu: Incomplete Bug description: WiFi connection goes down when having a Bluetooth headset connected and change from A2DP to HSP. The connection goes down instantly. If you change back to A2DP connection works again, but in some cases it goes down forever till you disconnect from the current WiFi and connect again. [How to reproduce] 1. connect a Bluetooth headset and change from A2DP to HSP. [System Info] Ubuntu 5.4.0-24.28-generic 5.4.30 03:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 31) No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 20.04 LTS Release: 20.04 Codename:focal [DMESG info] 348674.114861] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114864] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114866] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114869] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114873] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114876] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114879] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114882] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114885] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114888] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114891] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114894] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114897] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114900] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114903] Bluetooth: hci0: SCO packet for unknown connection handle 3072 [348674.114906] Bluetooth: hci0: SCO packet for unknown connection handle 48 [348674.114909] Bluetooth: hci0: SCO packet for unknown connection handle 0 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: leosilva 6150 F pulseaudio /dev/snd/pcmC1D7p: leosilva 6150 F...m pulseaudio /dev/snd/controlC0: leosilva 6150 F pulseaudio /dev/snd/pcmC0D8p: leosilva 6150 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-02 (111 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200102) MachineType: Dell Inc. XPS 8930 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA 1 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-24-generic root=UUID=bb691d80-94d7-4044-844f-c0df45ba89ca ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-24-generic N/A linux-backports-modules-5.4.0-24-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-24-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 libvirt lpadmin lxd plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 10/31/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.10 dmi.board.name: 06HKRH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.1.10:bd10/31/2019:svnDellInc.:pnXPS8930:pvr1.1.10:rvnDellInc.:rn06HKRH:rvrA00:cvnDellInc.:ct3:cvrNotSpecified: dmi.product.family: XPS dmi.product.name: XPS 8930 dmi.product.sku: 0859 dmi.product.version: 1.1.10 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874305/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874305] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1874305/+attachment/5358414/+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/1874305 Title: Wifi goes down when change bluetooth configuration Status in linux package in Ubuntu: Incomplete Bug description: WiFi connection goes down when having a Bluetooth headset connected and change from A2DP to HSP. The connection goes down instantly. If you change back to A2DP connection works again, but in some cases it goes down forever till you disconnect from the current WiFi and connect again. [How to reproduce] 1. connect a Bluetooth headset and change from A2DP to HSP. [System Info] Ubuntu 5.4.0-24.28-generic 5.4.30 03:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 31) No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 20.04 LTS Release: 20.04 Codename:focal [DMESG info] 348674.114861] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114864] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114866] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114869] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114873] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114876] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114879] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114882] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114885] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114888] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114891] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114894] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114897] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114900] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114903] Bluetooth: hci0: SCO packet for unknown connection handle 3072 [348674.114906] Bluetooth: hci0: SCO packet for unknown connection handle 48 [348674.114909] Bluetooth: hci0: SCO packet for unknown connection handle 0 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: leosilva 6150 F pulseaudio /dev/snd/pcmC1D7p: leosilva 6150 F...m pulseaudio /dev/snd/controlC0: leosilva 6150 F pulseaudio /dev/snd/pcmC0D8p: leosilva 6150 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-02 (111 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200102) MachineType: Dell Inc. XPS 8930 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA 1 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-24-generic root=UUID=bb691d80-94d7-4044-844f-c0df45ba89ca ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-24-generic N/A linux-backports-modules-5.4.0-24-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-24-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 libvirt lpadmin lxd plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 10/31/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.10 dmi.board.name: 06HKRH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.1.10:bd10/31/2019:svnDellInc.:pnXPS8930:pvr1.1.10:rvnDellInc.:rn06HKRH:rvrA00:cvnDellInc.:ct3:cvrNotSpecified: dmi.product.family: XPS dmi.product.name: XPS 8930 dmi.product.sku: 0859 dmi.product.version: 1.1.10 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874305/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874305] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1874305/+attachment/5358416/+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/1874305 Title: Wifi goes down when change bluetooth configuration Status in linux package in Ubuntu: Incomplete Bug description: WiFi connection goes down when having a Bluetooth headset connected and change from A2DP to HSP. The connection goes down instantly. If you change back to A2DP connection works again, but in some cases it goes down forever till you disconnect from the current WiFi and connect again. [How to reproduce] 1. connect a Bluetooth headset and change from A2DP to HSP. [System Info] Ubuntu 5.4.0-24.28-generic 5.4.30 03:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 31) No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 20.04 LTS Release: 20.04 Codename:focal [DMESG info] 348674.114861] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114864] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114866] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114869] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114873] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114876] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114879] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114882] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114885] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114888] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114891] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114894] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114897] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114900] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114903] Bluetooth: hci0: SCO packet for unknown connection handle 3072 [348674.114906] Bluetooth: hci0: SCO packet for unknown connection handle 48 [348674.114909] Bluetooth: hci0: SCO packet for unknown connection handle 0 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: leosilva 6150 F pulseaudio /dev/snd/pcmC1D7p: leosilva 6150 F...m pulseaudio /dev/snd/controlC0: leosilva 6150 F pulseaudio /dev/snd/pcmC0D8p: leosilva 6150 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-02 (111 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200102) MachineType: Dell Inc. XPS 8930 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA 1 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-24-generic root=UUID=bb691d80-94d7-4044-844f-c0df45ba89ca ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-24-generic N/A linux-backports-modules-5.4.0-24-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-24-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 libvirt lpadmin lxd plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 10/31/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.10 dmi.board.name: 06HKRH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.1.10:bd10/31/2019:svnDellInc.:pnXPS8930:pvr1.1.10:rvnDellInc.:rn06HKRH:rvrA00:cvnDellInc.:ct3:cvrNotSpecified: dmi.product.family: XPS dmi.product.name: XPS 8930 dmi.product.sku: 0859 dmi.product.version: 1.1.10 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874305/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874305] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1874305/+attachment/5358407/+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/1874305 Title: Wifi goes down when change bluetooth configuration Status in linux package in Ubuntu: Incomplete Bug description: WiFi connection goes down when having a Bluetooth headset connected and change from A2DP to HSP. The connection goes down instantly. If you change back to A2DP connection works again, but in some cases it goes down forever till you disconnect from the current WiFi and connect again. [How to reproduce] 1. connect a Bluetooth headset and change from A2DP to HSP. [System Info] Ubuntu 5.4.0-24.28-generic 5.4.30 03:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 31) No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 20.04 LTS Release: 20.04 Codename:focal [DMESG info] 348674.114861] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114864] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114866] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114869] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114873] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114876] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114879] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114882] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114885] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114888] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114891] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114894] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114897] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114900] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114903] Bluetooth: hci0: SCO packet for unknown connection handle 3072 [348674.114906] Bluetooth: hci0: SCO packet for unknown connection handle 48 [348674.114909] Bluetooth: hci0: SCO packet for unknown connection handle 0 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: leosilva 6150 F pulseaudio /dev/snd/pcmC1D7p: leosilva 6150 F...m pulseaudio /dev/snd/controlC0: leosilva 6150 F pulseaudio /dev/snd/pcmC0D8p: leosilva 6150 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-02 (111 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200102) MachineType: Dell Inc. XPS 8930 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA 1 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-24-generic root=UUID=bb691d80-94d7-4044-844f-c0df45ba89ca ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-24-generic N/A linux-backports-modules-5.4.0-24-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-24-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 libvirt lpadmin lxd plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 10/31/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.10 dmi.board.name: 06HKRH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.1.10:bd10/31/2019:svnDellInc.:pnXPS8930:pvr1.1.10:rvnDellInc.:rn06HKRH:rvrA00:cvnDellInc.:ct3:cvrNotSpecified: dmi.product.family: XPS dmi.product.name: XPS 8930 dmi.product.sku: 0859 dmi.product.version: 1.1.10 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874305/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874305] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1874305/+attachment/5358405/+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/1874305 Title: Wifi goes down when change bluetooth configuration Status in linux package in Ubuntu: Incomplete Bug description: WiFi connection goes down when having a Bluetooth headset connected and change from A2DP to HSP. The connection goes down instantly. If you change back to A2DP connection works again, but in some cases it goes down forever till you disconnect from the current WiFi and connect again. [How to reproduce] 1. connect a Bluetooth headset and change from A2DP to HSP. [System Info] Ubuntu 5.4.0-24.28-generic 5.4.30 03:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 31) No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 20.04 LTS Release: 20.04 Codename:focal [DMESG info] 348674.114861] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114864] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114866] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114869] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114873] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114876] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114879] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114882] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114885] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114888] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114891] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114894] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114897] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114900] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114903] Bluetooth: hci0: SCO packet for unknown connection handle 3072 [348674.114906] Bluetooth: hci0: SCO packet for unknown connection handle 48 [348674.114909] Bluetooth: hci0: SCO packet for unknown connection handle 0 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: leosilva 6150 F pulseaudio /dev/snd/pcmC1D7p: leosilva 6150 F...m pulseaudio /dev/snd/controlC0: leosilva 6150 F pulseaudio /dev/snd/pcmC0D8p: leosilva 6150 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-02 (111 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200102) MachineType: Dell Inc. XPS 8930 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA 1 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-24-generic root=UUID=bb691d80-94d7-4044-844f-c0df45ba89ca ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-24-generic N/A linux-backports-modules-5.4.0-24-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-24-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 libvirt lpadmin lxd plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 10/31/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.10 dmi.board.name: 06HKRH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.1.10:bd10/31/2019:svnDellInc.:pnXPS8930:pvr1.1.10:rvnDellInc.:rn06HKRH:rvrA00:cvnDellInc.:ct3:cvrNotSpecified: dmi.product.family: XPS dmi.product.name: XPS 8930 dmi.product.sku: 0859 dmi.product.version: 1.1.10 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874305/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874305] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1874305/+attachment/5358410/+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/1874305 Title: Wifi goes down when change bluetooth configuration Status in linux package in Ubuntu: Incomplete Bug description: WiFi connection goes down when having a Bluetooth headset connected and change from A2DP to HSP. The connection goes down instantly. If you change back to A2DP connection works again, but in some cases it goes down forever till you disconnect from the current WiFi and connect again. [How to reproduce] 1. connect a Bluetooth headset and change from A2DP to HSP. [System Info] Ubuntu 5.4.0-24.28-generic 5.4.30 03:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 31) No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 20.04 LTS Release: 20.04 Codename:focal [DMESG info] 348674.114861] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114864] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114866] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114869] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114873] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114876] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114879] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114882] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114885] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114888] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114891] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114894] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114897] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114900] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114903] Bluetooth: hci0: SCO packet for unknown connection handle 3072 [348674.114906] Bluetooth: hci0: SCO packet for unknown connection handle 48 [348674.114909] Bluetooth: hci0: SCO packet for unknown connection handle 0 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: leosilva 6150 F pulseaudio /dev/snd/pcmC1D7p: leosilva 6150 F...m pulseaudio /dev/snd/controlC0: leosilva 6150 F pulseaudio /dev/snd/pcmC0D8p: leosilva 6150 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-02 (111 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200102) MachineType: Dell Inc. XPS 8930 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA 1 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-24-generic root=UUID=bb691d80-94d7-4044-844f-c0df45ba89ca ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-24-generic N/A linux-backports-modules-5.4.0-24-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-24-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 libvirt lpadmin lxd plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 10/31/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.10 dmi.board.name: 06HKRH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.1.10:bd10/31/2019:svnDellInc.:pnXPS8930:pvr1.1.10:rvnDellInc.:rn06HKRH:rvrA00:cvnDellInc.:ct3:cvrNotSpecified: dmi.product.family: XPS dmi.product.name: XPS 8930 dmi.product.sku: 0859 dmi.product.version: 1.1.10 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874305/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874305] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1874305/+attachment/5358408/+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/1874305 Title: Wifi goes down when change bluetooth configuration Status in linux package in Ubuntu: Incomplete Bug description: WiFi connection goes down when having a Bluetooth headset connected and change from A2DP to HSP. The connection goes down instantly. If you change back to A2DP connection works again, but in some cases it goes down forever till you disconnect from the current WiFi and connect again. [How to reproduce] 1. connect a Bluetooth headset and change from A2DP to HSP. [System Info] Ubuntu 5.4.0-24.28-generic 5.4.30 03:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 31) No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 20.04 LTS Release: 20.04 Codename:focal [DMESG info] 348674.114861] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114864] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114866] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114869] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114873] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114876] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114879] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114882] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114885] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114888] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114891] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114894] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114897] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114900] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114903] Bluetooth: hci0: SCO packet for unknown connection handle 3072 [348674.114906] Bluetooth: hci0: SCO packet for unknown connection handle 48 [348674.114909] Bluetooth: hci0: SCO packet for unknown connection handle 0 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: leosilva 6150 F pulseaudio /dev/snd/pcmC1D7p: leosilva 6150 F...m pulseaudio /dev/snd/controlC0: leosilva 6150 F pulseaudio /dev/snd/pcmC0D8p: leosilva 6150 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-02 (111 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200102) MachineType: Dell Inc. XPS 8930 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA 1 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-24-generic root=UUID=bb691d80-94d7-4044-844f-c0df45ba89ca ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-24-generic N/A linux-backports-modules-5.4.0-24-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-24-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 libvirt lpadmin lxd plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 10/31/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.10 dmi.board.name: 06HKRH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.1.10:bd10/31/2019:svnDellInc.:pnXPS8930:pvr1.1.10:rvnDellInc.:rn06HKRH:rvrA00:cvnDellInc.:ct3:cvrNotSpecified: dmi.product.family: XPS dmi.product.name: XPS 8930 dmi.product.sku: 0859 dmi.product.version: 1.1.10 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874305/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874305] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1874305/+attachment/5358412/+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/1874305 Title: Wifi goes down when change bluetooth configuration Status in linux package in Ubuntu: Incomplete Bug description: WiFi connection goes down when having a Bluetooth headset connected and change from A2DP to HSP. The connection goes down instantly. If you change back to A2DP connection works again, but in some cases it goes down forever till you disconnect from the current WiFi and connect again. [How to reproduce] 1. connect a Bluetooth headset and change from A2DP to HSP. [System Info] Ubuntu 5.4.0-24.28-generic 5.4.30 03:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 31) No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 20.04 LTS Release: 20.04 Codename:focal [DMESG info] 348674.114861] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114864] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114866] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114869] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114873] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114876] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114879] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114882] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114885] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114888] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114891] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114894] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114897] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114900] Bluetooth: hci0: SCO packet for unknown connection handle 0 [348674.114903] Bluetooth: hci0: SCO packet for unknown connection handle 3072 [348674.114906] Bluetooth: hci0: SCO packet for unknown connection handle 48 [348674.114909] Bluetooth: hci0: SCO packet for unknown connection handle 0 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: leosilva 6150 F pulseaudio /dev/snd/pcmC1D7p: leosilva 6150 F...m pulseaudio /dev/snd/controlC0: leosilva 6150 F pulseaudio /dev/snd/pcmC0D8p: leosilva 6150 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-02 (111 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200102) MachineType: Dell Inc. XPS 8930 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA 1 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-24-generic root=UUID=bb691d80-94d7-4044-844f-c0df45ba89ca ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-24-generic N/A linux-backports-modules-5.4.0-24-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-24-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 libvirt lpadmin lxd plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 10/31/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.10 dmi.board.name: 06HKRH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.1.10:bd10/31/2019:svnDellInc.:pnXPS8930:pvr1.1.10:rvnDellInc.:rn06HKRH:rvrA00:cvnDellInc.:ct3:cvrNotSpecified: dmi.product.family: XPS dmi.product.name: XPS 8930 dmi.product.sku: 0859 dmi.product.version: 1.1.10 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874305/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
