[Kernel-packages] [Bug 1772434] Re: Broadcom: IT (HBA) Driver Enablement in 18.04 (Patches)
Can you guys share the release plans for kernel-4.15.0-33.36? We have a installation/boot failure with HBA330 and the patches in this list are fixing it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1772434 Title: Broadcom: IT (HBA) Driver Enablement in 18.04 (Patches) Status in dellserver: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: The purpose of this bug is to track the patches needed to enable the IT (HBA) driver into 18.04. Below are upstream commit ids of IT driver which went in over the in- box driver of Ubuntu18.04 OS’s base kernel, 864449eea7c600596e305ffdc4a6a846414b222c scsi: mpt3sas: Do not mark fw_event workqueue as WQ_MEM_RECLAIM 6f9e09fd6488de7661ee20efb5d8ab4e05a59735 scsi: mpt3sas: clarify mmio pointer types 40114bde9773ccaf9ad77233ac2cc9039f0f2941 scsi: mpt3sas: Do not use 32-bit atomic request descriptor for Ventura controllers. b4472d7180894c96b6133ef5ff3df50836591eaa scsi: mpt3sas: Introduce function to clone mpi reply. e5747439366c1079257083f231f5dd9a84bf0fd7 scsi: mpt3sas: Introduce function to clone mpi request. 182ac784b41faee02e8b44cd7149575258ad6858 scsi: mpt3sas: Introduce Base function for cloning. 22ae5a3c2599381cf7aaa5aca25c515a3166adcc scsi: mpt3sas: Introduce API to get BAR0 mapped buffer address 0448f0195124e33f11d15b7d1e1cab959989eee7 scsi: mpt3sas: Configure reply post queue depth, DMA and sgl tablesize. c520691b38cde1d94f53e5782feba892f5645043 scsi: mpt3sas: Add PCI device ID for Andromeda. 4a8842de8db4953fdda7866626b78b12fb8adb97 scsi: mpt3sas: fix an out of bound write 61dfb8a5fb7e93e692856026fa4c778a27f28984 scsi: mpt3sas: make function _get_st_from_smid static dbec4c9040edc15442c3ebdb65408aa9d3b82c24 scsi: mpt3sas: lockless command submission 272e253c7bcabfeef5f4d0aaed94a413e13e520f scsi: mpt3sas: simplify _wait_for_commands_to_complete() 6da999fe5a9285c2a78f3cf1e768abcd48d7607e scsi: mpt3sas: simplify mpt3sas_scsi_issue_tm() 74fcfa5371b7a681e864d3a9d3b9ecfd5737d8ea scsi: mpt3sas: simplify task management functions b0cd285eb57cd3cb18d882565c22d39bccffe7f0 scsi: mpt3sas: always use first reserved smid for ioctl passthrough 9961c9bbf2b43acaaf030a0fbabc9954d937ad8c scsi: mpt3sas: check command status before attempting abort 12e7c6782bc58128392b768fc2a87b230414a2a5 scsi: mpt3sas: Introduce mpt3sas_get_st_from_smid() 02a386df3678275b01eec71fee39735c379e4a2a scsi: mpt3sas: open-code _scsih_scsi_lookup_get() 6a2d4618aef3d4ffb83514e5e58a091d61e54a03 scsi: mpt3sas: separate out _base_recovery_check() 05303dfb738066ad597d7feb422ff9fa2d3d8ef3 scsi: mpt3sas: use list_splice_init() ba4494d47bd02e5757b449a2ccfa3ff87bc8 scsi: mpt3sas: set default value for cb_idx f49d4aed1315a7b766d855f1367142e682b0cc87 scsi: mpt3sas: Proper handling of set/clear of "ATA command pending" flag. 45b7aef7fb7d5f5bfa3a2a6727f1accf7660f6fd scsi: mpt3sas: Remove unused variable requeue_event To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1772434/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1760647] Re: Unable to build lttng module on 4.4/4.15 KVM kernel
After discussion with Kamal, we will disable this test instead of enabling that CONFIG_TRACEPOINTS for KVM kernels. Thanks ** Changed in: linux-kvm (Ubuntu) Status: New => Won't Fix ** No longer affects: linux (Ubuntu) ** Also affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Changed in: ubuntu-kernel-tests Status: New => In Progress ** No longer affects: linux (Ubuntu Xenial) ** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Po-Hsu Lin (cypressyew) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1760647 Title: Unable to build lttng module on 4.4/4.15 KVM kernel Status in ubuntu-kernel-tests: In Progress Status in linux-kvm package in Ubuntu: Won't Fix Status in linux-kvm source package in Xenial: New Bug description: Tested with the lttng module in -proposed (2.8.0-1ubuntu1~16.04.5), it looks like this is the CONFIG issue. Build log: DKMS make.log for lttng-modules-2.8.0 for kernel 4.4.0-1019-kvm (x86_64) Mon Apr 2 17:05:48 UTC 2018 make: Entering directory '/usr/src/linux-headers-4.4.0-1019-kvm' /var/lib/dkms/lttng-modules/2.8.0/build/Makefile:12: *** The option CONFIG_TRACEPOINTS needs to be enabled in your kernel configuration. Stop. Makefile:1423: recipe for target '_module_/var/lib/dkms/lttng-modules/2.8.0/build' failed make: *** [_module_/var/lib/dkms/lttng-modules/2.8.0/build] Error 2 make: Leaving directory '/usr/src/linux-headers-4.4.0-1019-kvm' ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-1019-kvm 4.4.0-1019.24 ProcVersionSignature: User Name 4.4.0-1019.24-kvm 4.4.98 Uname: Linux 4.4.0-1019-kvm x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Mon Apr 2 16:38:25 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1760647/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1785780] Re: TB 16 issue on Dell Lattitude 7490 with large amount of data
Yes. https://lkml.org/lkml/2018/8/20/42 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1785780 Title: TB 16 issue on Dell Lattitude 7490 with large amount of data Status in Dell Sputnik: New Status in linux package in Ubuntu: Confirmed Bug description: Hi. Large amount of data gets corrupted when using the TB16 ethernet port. (rsync synchronization, etc... ) We can confirm this issue on this kernel. Creating new issue as stated in this bug (#1729674) Linux E7490 4.15.0-29-generic #31-Ubuntu SMP Tue Jul 17 15:39:52 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux On my Fedora is this still an issue even with announced bugfix (link copied from this discussion #78. Linux username-localdomain 4.17.9-200.fc28.x86_64 #1 SMP Mon Jul 23 21:41:29 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux It's fixed by turning the checksum offload off (tested on the Fedora . sudo ethtool --offload enp11s0u1u2 rx off https://bugs.launchpad.net/dell-sputnik/+bug/1729674 related in bugzilla: --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1955 F pulseaudio CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Latitude 7490 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed boot=casper quiet splash --- ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-29-generic N/A linux-backports-modules-4.15.0-29-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/07/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.1 dmi.board.name: 0KP0FT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.1:bd06/07/2018:svnDellInc.:pnLatitude7490:pvr:rvnDellInc.:rn0KP0FT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 7490 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1785780/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774752] Re: Ubuntu 18.04 Desktop UEFI OS Install options in Grub.cfg
[Expired for grub2 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: grub2 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774752 Title: Ubuntu 18.04 Desktop UEFI OS Install options in Grub.cfg Status in grub2 package in Ubuntu: Expired Status in linux package in Ubuntu: Expired Status in grub2 source package in Bionic: Expired Status in linux source package in Bionic: Expired Bug description: We are facing issue installing Ubuntu 18.04 Desktop, but if we change linux to linuxefi and initrd to initrdefi, it works. We wanted to make that change permanently in ISO/USB file. We cannot mount the /dev/sdb1 rw, and make the changes. So every boot, we have to edit. Can you please help us, how we can get around this, and make this change permanent in the grub.cfg file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1774752/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774752] Re: Ubuntu 18.04 Desktop UEFI OS Install options in Grub.cfg
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774752 Title: Ubuntu 18.04 Desktop UEFI OS Install options in Grub.cfg Status in grub2 package in Ubuntu: Expired Status in linux package in Ubuntu: Expired Status in grub2 source package in Bionic: Expired Status in linux source package in Bionic: Expired Bug description: We are facing issue installing Ubuntu 18.04 Desktop, but if we change linux to linuxefi and initrd to initrdefi, it works. We wanted to make that change permanently in ISO/USB file. We cannot mount the /dev/sdb1 rw, and make the changes. So every boot, we have to edit. Can you please help us, how we can get around this, and make this change permanent in the grub.cfg file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1774752/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774752] Re: Ubuntu 18.04 Desktop UEFI OS Install options in Grub.cfg
[Expired for linux (Ubuntu Bionic) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu Bionic) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774752 Title: Ubuntu 18.04 Desktop UEFI OS Install options in Grub.cfg Status in grub2 package in Ubuntu: Expired Status in linux package in Ubuntu: Expired Status in grub2 source package in Bionic: Expired Status in linux source package in Bionic: Expired Bug description: We are facing issue installing Ubuntu 18.04 Desktop, but if we change linux to linuxefi and initrd to initrdefi, it works. We wanted to make that change permanently in ISO/USB file. We cannot mount the /dev/sdb1 rw, and make the changes. So every boot, we have to edit. Can you please help us, how we can get around this, and make this change permanent in the grub.cfg file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1774752/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774752] Re: Ubuntu 18.04 Desktop UEFI OS Install options in Grub.cfg
[Expired for grub2 (Ubuntu Bionic) because there has been no activity for 60 days.] ** Changed in: grub2 (Ubuntu Bionic) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774752 Title: Ubuntu 18.04 Desktop UEFI OS Install options in Grub.cfg Status in grub2 package in Ubuntu: Expired Status in linux package in Ubuntu: Expired Status in grub2 source package in Bionic: Expired Status in linux source package in Bionic: Expired Bug description: We are facing issue installing Ubuntu 18.04 Desktop, but if we change linux to linuxefi and initrd to initrdefi, it works. We wanted to make that change permanently in ISO/USB file. We cannot mount the /dev/sdb1 rw, and make the changes. So every boot, we have to edit. Can you please help us, how we can get around this, and make this change permanent in the grub.cfg file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1774752/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1777311] Re: System freezes randomly
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1777311 Title: System freezes randomly Status in linux package in Ubuntu: Expired Bug description: System freezes randomly on a daily basis. First the mouse pointer actions are getting slow for a few seconds and after that the screen freezes. Various SysCtl key combinations I found on the net do not work. Switching to a console does not work. Remote login via SSH is not possible. The only way to get the system working again is a hard reboot. I did not find valueable information in the log files indicating what wents wrong here. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-45-generic 4.13.0-45.50 ProcVersionSignature: Ubuntu 4.13.0-45.50-generic 4.13.16 Uname: Linux 4.13.0-45-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: frank 1365 F pulseaudio /dev/snd/controlC1: frank 1365 F pulseaudio CurrentDesktop: KDE Date: Sun Jun 17 12:52:50 2018 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=a55f25fd-fc0f-486e-a5c5-cd88e26c2ff7 InstallationDate: Installed on 2018-06-10 (6 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.2) MachineType: Gigabyte Technology Co., Ltd. AB350-Gaming 3 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-45-generic root=UUID=7a70a4b3-b224-412a-9c2c-523467a214f3 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-45-generic N/A linux-backports-modules-4.13.0-45-generic N/A linux-firmware 1.169.3 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/17/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F23d dmi.board.asset.tag: Default string dmi.board.name: AB350-Gaming 3-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.:bvrF23d:bd04/17/2018:svnGigabyteTechnologyCo.,Ltd.:pnAB350-Gaming3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350-Gaming3-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AB350-Gaming 3 dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777311/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1777398] Re: dm thin block allocation failure
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1777398 Title: dm thin block allocation failure Status in linux package in Ubuntu: Expired Bug description: When using the bionic kernel (hwe-edge) on xenial we randomly trigger a kernel bug when creating a thin provisioned lvm volume. kernel: [146487.421278] [ cut here ] kernel: [146487.421281] kernel BUG at /build/linux-hwe-edge-eBL7So/linux-hwe-edge-4.15.0/drivers/md/persistent-data/dm-space-map-disk.c:178! kernel: [146487.421435] invalid opcode: [#1] SMP PTI kernel: [146487.421528] Modules linked in: dm_snapshot cmac arc4 md4 nls_utf8 cifs ccm fscache dccp_diag dccp tcp_diag udp_diag inet_diag unix_diag af_packet_diag netlink_diag xt_CHECKSUM xt_nat iptable_nat nf_nat_ipv4 nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack iptable_filter veth dummy bridge iptable_mangle xt_CT iptable_raw ip_tables x_tables vhost_net vhost tap ipmi_ssif dm_thin_pool dm_persistent_data dm_bio_prison dm_bufio intel_rapl skx_edac x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd glue_helper cryptd intel_cstate intel_rapl_perf lpc_ich ioatdma shpchp dca acpi_power_meter acpi_pad mac_hid ipmi_si ipmi_devintf ipmi_msghandler kernel: [146487.421859] nf_nat_ftp nf_conntrack_ftp nf_nat_sip nf_conntrack_sip nf_nat_pptp nf_conntrack_pptp nf_nat_proto_gre nf_nat nf_conntrack_proto_gre nf_conntrack tcp_htcp 8021q garp mrp stp llc bonding autofs4 btrfs zstd_compress raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid0 multipath linear raid10 raid1 i2c_algo_bit ttm i40e drm_kms_helper syscopyarea ptp sysfillrect pps_core sysimgblt fb_sys_fops nvme ahci drm nvme_core libahci wmi kernel: [146487.422080] CPU: 13 PID: 2274450 Comm: kworker/u576:1 Not tainted 4.15.0-22-generic #24~16.04.1-Ubuntu kernel: [146487.422211] Hardware name: Quanta Cloud Technology Inc. QuantaGrid D52B-1U/S5B-MB (LBG-4), BIOS 3A10.03 11/17/2017 kernel: [146487.422349] Workqueue: dm-thin do_worker [dm_thin_pool] kernel: [146487.422443] RIP: 0010:sm_disk_new_block+0xa1/0xb0 [dm_persistent_data] kernel: [146487.422536] RSP: 0018:9efc5e4d3c68 EFLAGS: 00010297 kernel: [146487.422626] RAX: RBX: 88b122d34000 RCX: kernel: [146487.422749] RDX: 8868d8631e00 RSI: 0282 RDI: 88b137691200 kernel: [146487.422872] RBP: 9efc5e4d3c90 R08: R09: 9efc5e4d39f0 kernel: [146487.422994] R10: 9efc5e4d38f8 R11: 9efc5e4d3b48 R12: kernel: [146487.423117] R13: 9efc5e4d3d40 R14: 9efc5e4d3d40 R15: 882de1769fa0 kernel: [146487.423240] FS: () GS:8868ee54() knlGS: kernel: [146487.423366] CS: 0010 DS: ES: CR0: 80050033 kernel: [146487.423457] CR2: 7f0f30b083c0 CR3: 002ab260a004 CR4: 007626e0 kernel: [146487.423580] DR0: DR1: DR2: kernel: [146487.423703] DR3: DR6: fffe0ff0 DR7: 0400 kernel: [146487.423826] PKRU: 5554 kernel: [146487.423906] Call Trace: kernel: [146487.423989] dm_pool_alloc_data_block+0x44/0x60 [dm_thin_pool] kernel: [146487.424082] alloc_data_block.isra.53+0x6f/0x180 [dm_thin_pool] kernel: [146487.424175] process_cell+0x2cf/0x4d0 [dm_thin_pool] kernel: [146487.424267] ? mempool_alloc_slab+0x15/0x20 kernel: [146487.424354] ? mempool_alloc+0x73/0x180 kernel: [146487.424440] ? process_prepared+0x8d/0xc0 [dm_thin_pool] kernel: [146487.424531] do_worker+0x25c/0x8b0 [dm_thin_pool] kernel: [146487.424621] process_one_work+0x14d/0x410 kernel: [146487.424708] ? process_discard_cell_passdown+0x1e0/0x1e0 [dm_thin_pool] kernel: [146487.424802] ? process_one_work+0x14d/0x410 kernel: [146487.424888] worker_thread+0x4b/0x460 kernel: [146487.424973] kthread+0x105/0x140 kernel: [146487.425055] ? process_one_work+0x410/0x410 kernel: [146487.425142] ? kthread_associate_blkcg+0xa0/0xa0 kernel: [146487.425230] ? do_syscall_64+0x73/0x130 kernel: [146487.425315] ? SyS_exit_group+0x14/0x20 kernel: [146487.425401] ret_from_fork+0x35/0x40 kernel: [146487.425485] Code: c0 01 48 89 83 20 22 00 00 49 8b 75 00 e8 68 f7 ff ff 85 c0 75 10 83 7d dc 01 75 0f 48 83 83 28 22 00 00 01 eb af 41 89 c4 eb aa <0f> 0b e8 e8 1b cf d2 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 kernel: [146487.425703] RIP: sm_disk_new_block+0xa1/0xb0
[Kernel-packages] [Bug 1787187] Re: linux: 3.13.0-156.206 -proposed tracker
Time is limited and we would refer to the previous kernel (3.13.0-154.204) test result. ** Changed in: kernel-sru-workflow/certification-testing Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1787187 Title: linux: 3.13.0-156.206 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Fix Released Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1787188 (linux-lts-trusty) derivatives: -- swm properties -- boot-testing-requested: true phase: Promoted to updates To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1787187/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1787544] Re: linux-oem: 4.15.0-1017.20 -proposed tracker
** Changed in: kernel-sru-workflow/certification-testing Status: Confirmed => Invalid -- 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/1787544 Title: linux-oem: 4.15.0-1017.20 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-oem package in Ubuntu: Confirmed Status in linux-oem source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1787149 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1787544/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1725836] 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 1725836 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/1725836 Title: [radeon] No more than 2 displays work simultaneously Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Status in xserver-xorg-video-ati package in Ubuntu: Incomplete Bug description: I have three displays that worked fine in 17.04. Now ith 17.10 I can only use two of them. Either 1 & 2, 1& 3 or 2 2 & 3. All three seem to be properly specified in monitors.xml. The display setup scree detects all three. UBUNTU 17.10 AMD PitcairnLSB Version: core-9.20160110ubuntu5-amd64:core-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.20160110ubuntu5-noarch --- ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-02-23 (242 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) Package: mutter PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Tags: artful Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-10-20 (3 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1725836/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1725836] Re: No more than 2 displays work simultaneously
Thanks. Comment #33 seems to be the most important one now. If the bug occurs in XFCE as well then this is not a gnome-shell bug. Instead it should be assigned to xorg-server, or the driver, or the kernel. ** No longer affects: mutter ** No longer affects: gnome-shell (Ubuntu) ** No longer affects: mutter (Ubuntu) ** Summary changed: - No more than 2 displays work simultaneously + [radeon] No more than 2 displays work simultaneously ** Tags added: radeon ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1725836 Title: [radeon] No more than 2 displays work simultaneously Status in linux package in Ubuntu: New Status in xorg-server package in Ubuntu: Incomplete Status in xserver-xorg-video-ati package in Ubuntu: Incomplete Bug description: I have three displays that worked fine in 17.04. Now ith 17.10 I can only use two of them. Either 1 & 2, 1& 3 or 2 2 & 3. All three seem to be properly specified in monitors.xml. The display setup scree detects all three. UBUNTU 17.10 AMD PitcairnLSB Version: core-9.20160110ubuntu5-amd64:core-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.20160110ubuntu5-noarch --- ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-02-23 (242 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) Package: mutter PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Tags: artful Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-10-20 (3 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1725836/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1690085]
(In reply to Antoine Pitrou from comment #398) > @Daniel what makes you think this bug is fixed? It certainly isn't for me. > I have a ASRock Fatal1ty X370 Gaming X motherboard, a Ryzen 7 1700 CPU, have > updated the motherboard BIOS to its latest version (4.80 with > PinnaclePI-AM4_1.0.0.2 Patch A) and am still getting idle lockups with > kernel 4.15.0-32-generic (Ubuntu 18.04.1 kernel). The workaround for me is > to disable C6 states using the Zenstates.py script (which has the > unfortunate side effect of lowering the max CPU frequency in single-threaded > mode). Please remember, this is the upstream Linux kernel bug tracker. So, reports should only be for the latest stable releases, which currently is 4.18.3 [1]. Some distributions make it easy to install those. Packages are available for Ubuntu [2]. Please report issues with the heavily patched Ubuntu default Linux kernel to the Ubuntu bug tracker [3]. [1]: https://www.kernel.org/ [2]: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18.3/ [3]: https://bugs.launchpad.net/ubuntu/+source/linux/+bugs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hi, We aregetting various kernel crash on a pretty new config. We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using latest BIOS available (1.52) We are running Ubuntu 17.04 (amd64), we've tried different kernel version, native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too. Tested kernel version: native 17.04 kernel 4.10.15 Issues are the same, we're getting random freeze on the machine. Here is kern.log entry when happening : May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=913449 May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 jiffies, g=10001, c=1, q=4656) May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0: May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0 R running task 0 0 0 0x0008 May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace: May 10 22:41:56 dev2 kernel: [24366.190354] ? native_safe_halt+0x6/0x10 May 10 22:41:56 dev2 kernel: [24366.190355] ? default_idle+0x20/0xd0 May 10 22:41:56 dev2 kernel: [24366.190358] ? arch_cpu_idle+0xf/0x20 May 10 22:41:56 dev2 kernel: [24366.190360] ? default_idle_call+0x23/0x30 May 10 22:41:56 dev2 kernel: [24366.190362] ? do_idle+0x16f/0x200 May 10 22:41:56 dev2 kernel: [24366.190364] ? cpu_startup_entry+0x71/0x80 May 10 22:41:56 dev2 kernel: [24366.190366] ? rest_init+0x77/0x80 May 10 22:41:56 dev2 kernel: [24366.190368] ? start_kernel+0x464/0x485 May 10 22:41:56 dev2 kernel: [24366.190369] ? early_idt_handler_array+0x120/0x120 May 10 22:41:56 dev2 kernel: [24366.190371] ? x86_64_start_reservations+0x24/0x26 May 10 22:41:56 dev2 kernel: [24366.190372] ? x86_64_start_kernel+0x14d/0x170 May 10 22:41:56 dev2 kernel: [24366.190373] ? start_cpu+0x14/0x14 May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=935027 May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 jiffies, g=10001, c=1, q=4740) May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0: May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0 R running task 0 0 0 0x0008 May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace: May 10 22:44:56 dev2 kernel: [24546.192199] ? native_safe_halt+0x6/0x10 May 10 22:44:56 dev2 kernel: [24546.192201] ? default_idle+0x20/0xd0 May 10 22:44:56 dev2 kernel: [24546.192203] ? arch_cpu_idle+0xf/0x20 May 10 22:44:56 dev2 kernel: [24546.192204] ? default_idle_call+0x23/0x30 May 10 22:44:56 dev2 kernel: [24546.192206] ? do_idle+0x16f/0x200 May 10 22:44:56 dev2 kernel: [24546.192208] ? cpu_startup_entry+0x71/0x80 May 10 22:44:56 dev2 kernel: [24546.192210] ? rest_init+0x77/0x80 May 10 22:44:56 dev2 kernel: [24546.192211] ? start_kernel+0x464/0x485 May 10 22:44:56 dev2 kernel: [24546.192213] ? early_idt_handler_array+0x120/0x120 May 10 22:44:56 dev2 kernel: [24546.192214] ? x86_64_start_reservations+0x24/0x26 May 10 22:44:56 dev2 kernel: [24546.192215] ? x86_64_start_kernel+0x14d/0x170 May 10 22:44:56 dev2 kernel: [24546.192217] ? start_cpu+0x14/0x14 Depending on the kernel version, we've got NMI watchdog errors related to CPU stuck (mentioning the CPU core id, which is random). Crash is
[Kernel-packages] [Bug 1690085]
(In reply to Antoine Pitrou from comment #407) > (In reply to Michaël Colignon from comment #400) > > > > Hi Antoine, i checked the manual of your Asrock motherboard quickly. > > For your machine the "typical idle current" is named "c6 mode" > > Disable it and you get the "typical idle current", i think. > > While keeping the boost monothread. > > Hi Michaël, that option was removed in the latest BIOS updates. Probably > because it didn't work at all. Oh yes it works. On others boards it fix the crashes in idle. Contact asrock support about the "typical idle current" needed option. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hi, We aregetting various kernel crash on a pretty new config. We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using latest BIOS available (1.52) We are running Ubuntu 17.04 (amd64), we've tried different kernel version, native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too. Tested kernel version: native 17.04 kernel 4.10.15 Issues are the same, we're getting random freeze on the machine. Here is kern.log entry when happening : May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=913449 May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 jiffies, g=10001, c=1, q=4656) May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0: May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0 R running task 0 0 0 0x0008 May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace: May 10 22:41:56 dev2 kernel: [24366.190354] ? native_safe_halt+0x6/0x10 May 10 22:41:56 dev2 kernel: [24366.190355] ? default_idle+0x20/0xd0 May 10 22:41:56 dev2 kernel: [24366.190358] ? arch_cpu_idle+0xf/0x20 May 10 22:41:56 dev2 kernel: [24366.190360] ? default_idle_call+0x23/0x30 May 10 22:41:56 dev2 kernel: [24366.190362] ? do_idle+0x16f/0x200 May 10 22:41:56 dev2 kernel: [24366.190364] ? cpu_startup_entry+0x71/0x80 May 10 22:41:56 dev2 kernel: [24366.190366] ? rest_init+0x77/0x80 May 10 22:41:56 dev2 kernel: [24366.190368] ? start_kernel+0x464/0x485 May 10 22:41:56 dev2 kernel: [24366.190369] ? early_idt_handler_array+0x120/0x120 May 10 22:41:56 dev2 kernel: [24366.190371] ? x86_64_start_reservations+0x24/0x26 May 10 22:41:56 dev2 kernel: [24366.190372] ? x86_64_start_kernel+0x14d/0x170 May 10 22:41:56 dev2 kernel: [24366.190373] ? start_cpu+0x14/0x14 May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=935027 May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 jiffies, g=10001, c=1, q=4740) May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0: May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0 R running task 0 0 0 0x0008 May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace: May 10 22:44:56 dev2 kernel: [24546.192199] ? native_safe_halt+0x6/0x10 May 10 22:44:56 dev2 kernel: [24546.192201] ? default_idle+0x20/0xd0 May 10 22:44:56 dev2 kernel: [24546.192203] ? arch_cpu_idle+0xf/0x20 May 10 22:44:56 dev2 kernel: [24546.192204] ? default_idle_call+0x23/0x30 May 10 22:44:56 dev2 kernel: [24546.192206] ? do_idle+0x16f/0x200 May 10 22:44:56 dev2 kernel: [24546.192208] ? cpu_startup_entry+0x71/0x80 May 10 22:44:56 dev2 kernel: [24546.192210] ? rest_init+0x77/0x80 May 10 22:44:56 dev2 kernel: [24546.192211] ? start_kernel+0x464/0x485 May 10 22:44:56 dev2 kernel: [24546.192213] ? early_idt_handler_array+0x120/0x120 May 10 22:44:56 dev2 kernel: [24546.192214] ? x86_64_start_reservations+0x24/0x26 May 10 22:44:56 dev2 kernel: [24546.192215] ? x86_64_start_kernel+0x14d/0x170 May 10 22:44:56 dev2 kernel: [24546.192217] ? start_cpu+0x14/0x14 Depending on the kernel version, we've got NMI watchdog errors related to CPU stuck (mentioning the CPU core id, which is random). Crash is happening randomly, but in general after some hours (3-4h). Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning and waiting for crash... For now, the machine is not "used", at least, it's not CPU stressed... Thanks --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-05-09 (1 days ago) InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 (20170412)
[Kernel-packages] [Bug 1690085]
@Paul I understand this. I'm also monitoring the corresponding Ubuntu issue. Still, I was asking whether there was a specific reason to believe this bug was fixed upstream (as opposed to the fact that a single person doesn't experience the issue anymore). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hi, We aregetting various kernel crash on a pretty new config. We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using latest BIOS available (1.52) We are running Ubuntu 17.04 (amd64), we've tried different kernel version, native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too. Tested kernel version: native 17.04 kernel 4.10.15 Issues are the same, we're getting random freeze on the machine. Here is kern.log entry when happening : May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=913449 May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 jiffies, g=10001, c=1, q=4656) May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0: May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0 R running task 0 0 0 0x0008 May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace: May 10 22:41:56 dev2 kernel: [24366.190354] ? native_safe_halt+0x6/0x10 May 10 22:41:56 dev2 kernel: [24366.190355] ? default_idle+0x20/0xd0 May 10 22:41:56 dev2 kernel: [24366.190358] ? arch_cpu_idle+0xf/0x20 May 10 22:41:56 dev2 kernel: [24366.190360] ? default_idle_call+0x23/0x30 May 10 22:41:56 dev2 kernel: [24366.190362] ? do_idle+0x16f/0x200 May 10 22:41:56 dev2 kernel: [24366.190364] ? cpu_startup_entry+0x71/0x80 May 10 22:41:56 dev2 kernel: [24366.190366] ? rest_init+0x77/0x80 May 10 22:41:56 dev2 kernel: [24366.190368] ? start_kernel+0x464/0x485 May 10 22:41:56 dev2 kernel: [24366.190369] ? early_idt_handler_array+0x120/0x120 May 10 22:41:56 dev2 kernel: [24366.190371] ? x86_64_start_reservations+0x24/0x26 May 10 22:41:56 dev2 kernel: [24366.190372] ? x86_64_start_kernel+0x14d/0x170 May 10 22:41:56 dev2 kernel: [24366.190373] ? start_cpu+0x14/0x14 May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=935027 May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 jiffies, g=10001, c=1, q=4740) May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0: May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0 R running task 0 0 0 0x0008 May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace: May 10 22:44:56 dev2 kernel: [24546.192199] ? native_safe_halt+0x6/0x10 May 10 22:44:56 dev2 kernel: [24546.192201] ? default_idle+0x20/0xd0 May 10 22:44:56 dev2 kernel: [24546.192203] ? arch_cpu_idle+0xf/0x20 May 10 22:44:56 dev2 kernel: [24546.192204] ? default_idle_call+0x23/0x30 May 10 22:44:56 dev2 kernel: [24546.192206] ? do_idle+0x16f/0x200 May 10 22:44:56 dev2 kernel: [24546.192208] ? cpu_startup_entry+0x71/0x80 May 10 22:44:56 dev2 kernel: [24546.192210] ? rest_init+0x77/0x80 May 10 22:44:56 dev2 kernel: [24546.192211] ? start_kernel+0x464/0x485 May 10 22:44:56 dev2 kernel: [24546.192213] ? early_idt_handler_array+0x120/0x120 May 10 22:44:56 dev2 kernel: [24546.192214] ? x86_64_start_reservations+0x24/0x26 May 10 22:44:56 dev2 kernel: [24546.192215] ? x86_64_start_kernel+0x14d/0x170 May 10 22:44:56 dev2 kernel: [24546.192217] ? start_cpu+0x14/0x14 Depending on the kernel version, we've got NMI watchdog errors related to CPU stuck (mentioning the CPU core id, which is random). Crash is happening randomly, but in general after some hours (3-4h). Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning and waiting for crash... For now, the machine is not "used", at least, it's not CPU stressed... Thanks --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-05-09 (1 days ago) InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 (20170412) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Tags: zesty Uname: Linux 4.11.0-041100-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh
[Kernel-packages] [Bug 1690085]
The title of the bug should be changed to include Ryzen 7 1700X, and the reporter should follow up, if the problem still occurs with Linux 4.18. For the other issues, separate bug reports should be submitted. Though the mailing lists might be the better forum for this, as the Linux kernel developers for the subsystem do not seem to use the Kernel.org Bugzilla. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hi, We aregetting various kernel crash on a pretty new config. We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using latest BIOS available (1.52) We are running Ubuntu 17.04 (amd64), we've tried different kernel version, native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too. Tested kernel version: native 17.04 kernel 4.10.15 Issues are the same, we're getting random freeze on the machine. Here is kern.log entry when happening : May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=913449 May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 jiffies, g=10001, c=1, q=4656) May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0: May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0 R running task 0 0 0 0x0008 May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace: May 10 22:41:56 dev2 kernel: [24366.190354] ? native_safe_halt+0x6/0x10 May 10 22:41:56 dev2 kernel: [24366.190355] ? default_idle+0x20/0xd0 May 10 22:41:56 dev2 kernel: [24366.190358] ? arch_cpu_idle+0xf/0x20 May 10 22:41:56 dev2 kernel: [24366.190360] ? default_idle_call+0x23/0x30 May 10 22:41:56 dev2 kernel: [24366.190362] ? do_idle+0x16f/0x200 May 10 22:41:56 dev2 kernel: [24366.190364] ? cpu_startup_entry+0x71/0x80 May 10 22:41:56 dev2 kernel: [24366.190366] ? rest_init+0x77/0x80 May 10 22:41:56 dev2 kernel: [24366.190368] ? start_kernel+0x464/0x485 May 10 22:41:56 dev2 kernel: [24366.190369] ? early_idt_handler_array+0x120/0x120 May 10 22:41:56 dev2 kernel: [24366.190371] ? x86_64_start_reservations+0x24/0x26 May 10 22:41:56 dev2 kernel: [24366.190372] ? x86_64_start_kernel+0x14d/0x170 May 10 22:41:56 dev2 kernel: [24366.190373] ? start_cpu+0x14/0x14 May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=935027 May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 jiffies, g=10001, c=1, q=4740) May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0: May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0 R running task 0 0 0 0x0008 May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace: May 10 22:44:56 dev2 kernel: [24546.192199] ? native_safe_halt+0x6/0x10 May 10 22:44:56 dev2 kernel: [24546.192201] ? default_idle+0x20/0xd0 May 10 22:44:56 dev2 kernel: [24546.192203] ? arch_cpu_idle+0xf/0x20 May 10 22:44:56 dev2 kernel: [24546.192204] ? default_idle_call+0x23/0x30 May 10 22:44:56 dev2 kernel: [24546.192206] ? do_idle+0x16f/0x200 May 10 22:44:56 dev2 kernel: [24546.192208] ? cpu_startup_entry+0x71/0x80 May 10 22:44:56 dev2 kernel: [24546.192210] ? rest_init+0x77/0x80 May 10 22:44:56 dev2 kernel: [24546.192211] ? start_kernel+0x464/0x485 May 10 22:44:56 dev2 kernel: [24546.192213] ? early_idt_handler_array+0x120/0x120 May 10 22:44:56 dev2 kernel: [24546.192214] ? x86_64_start_reservations+0x24/0x26 May 10 22:44:56 dev2 kernel: [24546.192215] ? x86_64_start_kernel+0x14d/0x170 May 10 22:44:56 dev2 kernel: [24546.192217] ? start_cpu+0x14/0x14 Depending on the kernel version, we've got NMI watchdog errors related to CPU stuck (mentioning the CPU core id, which is random). Crash is happening randomly, but in general after some hours (3-4h). Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning and waiting for crash... For now, the machine is not "used", at least, it's not CPU stressed... Thanks --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-05-09 (1 days ago) InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 (20170412) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Tags: zesty Uname: Linux 4.11.0-041100-generic x86_64
[Kernel-packages] [Bug 1690085]
(In reply to Michaël Colignon from comment #400) > > Hi Antoine, i checked the manual of your Asrock motherboard quickly. > For your machine the "typical idle current" is named "c6 mode" > Disable it and you get the "typical idle current", i think. > While keeping the boost monothread. Hi Michaël, that option was removed in the latest BIOS updates. Probably because it didn't work at all. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hi, We aregetting various kernel crash on a pretty new config. We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using latest BIOS available (1.52) We are running Ubuntu 17.04 (amd64), we've tried different kernel version, native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too. Tested kernel version: native 17.04 kernel 4.10.15 Issues are the same, we're getting random freeze on the machine. Here is kern.log entry when happening : May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=913449 May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 jiffies, g=10001, c=1, q=4656) May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0: May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0 R running task 0 0 0 0x0008 May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace: May 10 22:41:56 dev2 kernel: [24366.190354] ? native_safe_halt+0x6/0x10 May 10 22:41:56 dev2 kernel: [24366.190355] ? default_idle+0x20/0xd0 May 10 22:41:56 dev2 kernel: [24366.190358] ? arch_cpu_idle+0xf/0x20 May 10 22:41:56 dev2 kernel: [24366.190360] ? default_idle_call+0x23/0x30 May 10 22:41:56 dev2 kernel: [24366.190362] ? do_idle+0x16f/0x200 May 10 22:41:56 dev2 kernel: [24366.190364] ? cpu_startup_entry+0x71/0x80 May 10 22:41:56 dev2 kernel: [24366.190366] ? rest_init+0x77/0x80 May 10 22:41:56 dev2 kernel: [24366.190368] ? start_kernel+0x464/0x485 May 10 22:41:56 dev2 kernel: [24366.190369] ? early_idt_handler_array+0x120/0x120 May 10 22:41:56 dev2 kernel: [24366.190371] ? x86_64_start_reservations+0x24/0x26 May 10 22:41:56 dev2 kernel: [24366.190372] ? x86_64_start_kernel+0x14d/0x170 May 10 22:41:56 dev2 kernel: [24366.190373] ? start_cpu+0x14/0x14 May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=935027 May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 jiffies, g=10001, c=1, q=4740) May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0: May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0 R running task 0 0 0 0x0008 May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace: May 10 22:44:56 dev2 kernel: [24546.192199] ? native_safe_halt+0x6/0x10 May 10 22:44:56 dev2 kernel: [24546.192201] ? default_idle+0x20/0xd0 May 10 22:44:56 dev2 kernel: [24546.192203] ? arch_cpu_idle+0xf/0x20 May 10 22:44:56 dev2 kernel: [24546.192204] ? default_idle_call+0x23/0x30 May 10 22:44:56 dev2 kernel: [24546.192206] ? do_idle+0x16f/0x200 May 10 22:44:56 dev2 kernel: [24546.192208] ? cpu_startup_entry+0x71/0x80 May 10 22:44:56 dev2 kernel: [24546.192210] ? rest_init+0x77/0x80 May 10 22:44:56 dev2 kernel: [24546.192211] ? start_kernel+0x464/0x485 May 10 22:44:56 dev2 kernel: [24546.192213] ? early_idt_handler_array+0x120/0x120 May 10 22:44:56 dev2 kernel: [24546.192214] ? x86_64_start_reservations+0x24/0x26 May 10 22:44:56 dev2 kernel: [24546.192215] ? x86_64_start_kernel+0x14d/0x170 May 10 22:44:56 dev2 kernel: [24546.192217] ? start_cpu+0x14/0x14 Depending on the kernel version, we've got NMI watchdog errors related to CPU stuck (mentioning the CPU core id, which is random). Crash is happening randomly, but in general after some hours (3-4h). Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning and waiting for crash... For now, the machine is not "used", at least, it's not CPU stressed... Thanks --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-05-09 (1 days ago) InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 (20170412) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Tags: zesty Uname: Linux
[Kernel-packages] [Bug 1690085]
I don't think there is any reason to think that the "c6 mode" option had anything to do with "typical idle current". Its name implied that it disabled C6 states, which it actually didn't (according to the Zenstates script). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hi, We aregetting various kernel crash on a pretty new config. We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using latest BIOS available (1.52) We are running Ubuntu 17.04 (amd64), we've tried different kernel version, native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too. Tested kernel version: native 17.04 kernel 4.10.15 Issues are the same, we're getting random freeze on the machine. Here is kern.log entry when happening : May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=913449 May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 jiffies, g=10001, c=1, q=4656) May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0: May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0 R running task 0 0 0 0x0008 May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace: May 10 22:41:56 dev2 kernel: [24366.190354] ? native_safe_halt+0x6/0x10 May 10 22:41:56 dev2 kernel: [24366.190355] ? default_idle+0x20/0xd0 May 10 22:41:56 dev2 kernel: [24366.190358] ? arch_cpu_idle+0xf/0x20 May 10 22:41:56 dev2 kernel: [24366.190360] ? default_idle_call+0x23/0x30 May 10 22:41:56 dev2 kernel: [24366.190362] ? do_idle+0x16f/0x200 May 10 22:41:56 dev2 kernel: [24366.190364] ? cpu_startup_entry+0x71/0x80 May 10 22:41:56 dev2 kernel: [24366.190366] ? rest_init+0x77/0x80 May 10 22:41:56 dev2 kernel: [24366.190368] ? start_kernel+0x464/0x485 May 10 22:41:56 dev2 kernel: [24366.190369] ? early_idt_handler_array+0x120/0x120 May 10 22:41:56 dev2 kernel: [24366.190371] ? x86_64_start_reservations+0x24/0x26 May 10 22:41:56 dev2 kernel: [24366.190372] ? x86_64_start_kernel+0x14d/0x170 May 10 22:41:56 dev2 kernel: [24366.190373] ? start_cpu+0x14/0x14 May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=935027 May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 jiffies, g=10001, c=1, q=4740) May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0: May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0 R running task 0 0 0 0x0008 May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace: May 10 22:44:56 dev2 kernel: [24546.192199] ? native_safe_halt+0x6/0x10 May 10 22:44:56 dev2 kernel: [24546.192201] ? default_idle+0x20/0xd0 May 10 22:44:56 dev2 kernel: [24546.192203] ? arch_cpu_idle+0xf/0x20 May 10 22:44:56 dev2 kernel: [24546.192204] ? default_idle_call+0x23/0x30 May 10 22:44:56 dev2 kernel: [24546.192206] ? do_idle+0x16f/0x200 May 10 22:44:56 dev2 kernel: [24546.192208] ? cpu_startup_entry+0x71/0x80 May 10 22:44:56 dev2 kernel: [24546.192210] ? rest_init+0x77/0x80 May 10 22:44:56 dev2 kernel: [24546.192211] ? start_kernel+0x464/0x485 May 10 22:44:56 dev2 kernel: [24546.192213] ? early_idt_handler_array+0x120/0x120 May 10 22:44:56 dev2 kernel: [24546.192214] ? x86_64_start_reservations+0x24/0x26 May 10 22:44:56 dev2 kernel: [24546.192215] ? x86_64_start_kernel+0x14d/0x170 May 10 22:44:56 dev2 kernel: [24546.192217] ? start_cpu+0x14/0x14 Depending on the kernel version, we've got NMI watchdog errors related to CPU stuck (mentioning the CPU core id, which is random). Crash is happening randomly, but in general after some hours (3-4h). Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning and waiting for crash... For now, the machine is not "used", at least, it's not CPU stressed... Thanks --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-05-09 (1 days ago) InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 (20170412) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Tags: zesty Uname: Linux 4.11.0-041100-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups:
[Kernel-packages] [Bug 1787571] Re: Bluetooth keyboard won't connect again after connection was lost
This is surprising. It sounds like reconnecting is disabled by default unless you specify exactly which devices to reconnect in /etc/bluetooth/main.conf: # The ReconnectUUIDs defines the set of remote services that should try # to be reconnected to in case of a link loss (link supervision # timeout). The policy plugin should contain a sane set of values by # default, but this list can be overridden here. By setting the list to # empty the reconnection feature gets disabled. #ReconnectUUIDs=1112--1000-8000-00805f9b34fb, 111f--1000-8000-00805f9b34fb, 110a--1000-8000-00805f9b34fb So maybe try editing /etc/bluetooth/main.conf and change: #ReconnectUUIDs=1112--1000-8000-00805f9b34fb, 111f--1000-8000-00805f9b34fb, 110a--1000-8000-00805f9b34fb to: ReconnectUUIDs=1124--1000-8000-00805f9b34fb, 1812--1000-8000-00805f9b34fb in an attempt to auto-reconnect your Human Interface Devices. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1787571 Title: Bluetooth keyboard won't connect again after connection was lost Status in bluez package in Ubuntu: New Bug description: After my Bluetooth keyboard from Logitech (K380) looses its connection, either after a Ubuntu restart or by manually turning the keyboard off an on, it won't connect any more. Additionally, while the keyboard tries to reestablish the connection, my Logitech Bluetooth mouse (M590) looses its connection too! After that I can't establish any Bluetooth connection at all. Only a "sudo service bluetooth restart" helps. Then my mouse reconnects easily, if it's not disrupted by my keyboard. So I'm only possible to use my mouse and not the keyboard, because while it tries to reconnect, it kills the connection of my mouse and everything starts over again. I've also tried to reconnect the keyboard through "bluetoothctl", but without success: $ bluetoothctl paired-devices Device 34:88:5D:42:7E:03 Keyboard K380 Device FA:6A:9E:DA:2B:30 M585/M590 $ bluetoothctl connect 34:88:5D:42:7E:03 Attempting to connect to 34:88:5D:42:7E:03 Failed to connect: org.bluez.Error.Failed Both devices are "trusted": $ bluetoothctl info 34:88:5D:42:7E:03 Device 34:88:5D:42:7E:03 (public) Name: Keyboard K380 Alias: Keyboard K380 Class: 0x2540 Icon: input-keyboard Paired: yes Trusted: yes Blocked: no Connected: no LegacyPairing: no UUID: Service Discovery Serve.. (1000--1000-8000-00805f9b34fb) UUID: Human Interface Device... (1124--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb) Modalias: usb:v046DpB342d4200 $ bluetoothctl info FA:6A:9E:DA:2B:30 Device FA:6A:9E:DA:2B:30 (random) Name: M585/M590 Alias: M585/M590 Appearance: 0x03c2 Icon: input-mouse Paired: yes Trusted: yes Blocked: no Connected: yes LegacyPairing: no UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb) UUID: Device Information(180a--1000-8000-00805f9b34fb) UUID: Battery Service (180f--1000-8000-00805f9b34fb) UUID: Human Interface Device(1812--1000-8000-00805f9b34fb) UUID: Vendor specific (0001--1000-8000-011f246d) Modalias: usb:v046DpB01Bd0007 $ bluetoothctl show Controller 2C:6F:C9:44:57:E0 (public) Name: mir Alias: mir Class: 0x000c010c Powered: yes Discoverable: yes Pairable: yes UUID: Headset AG(1112--1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: Audio Source (110a--1000-8000-00805f9b34fb) UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: Headset (1108--1000-8000-00805f9b34fb) Modalias: usb:v1D6Bp0246d0532 Discovering: no The only way to use my Bluetooth keyboard is to pair it again, f.i. by doing: bluetoothctl remove XX:XX:XX:XX:XX:XX exit sudo service bluetooth restart bluetoothctl scan on trust XX:XX:XX:XX:XX:XX pair XX:XX:XX:XX:XX:XX connect XX:XX:XX:XX:XX:XX exit This keyboard works flawlessly with my Android device and also
[Kernel-packages] [Bug 1770166] 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/1770166 Title: The brightness of the notebook Status in linux package in Ubuntu: Confirmed Bug description: The brightness of the notebook does not lower or rise with the FN key. Acer Aspire 5742 i3-380m 6gb ram ssd kingston 120gb. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Core Processor Integrated Graphics Controller [1025:0487] InstallationDate: Installed on 2018-06-14 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Acer Aspire 5742 Package: xorg 1:7.7+19ubuntu7 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=921bc593-7a3c-4ced-8659-695cfe311ce9 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Tags: bionic ubuntu Uname: Linux 4.15.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/14/2011 dmi.bios.vendor: Acer dmi.bios.version: V1.18 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Aspire 5742 dmi.board.vendor: Acer dmi.board.version: V1.18 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.18 dmi.modalias: dmi:bvnAcer:bvrV1.18:bd03/14/2011:svnAcer:pnAspire5742:pvrV1.18:rvnAcer:rnAspire5742:rvrV1.18:cvnAcer:ct10:cvrV1.18: dmi.product.family: Intel_Mobile dmi.product.name: Aspire 5742 dmi.product.version: V1.18 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770166/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1759836] Re: systemd-udevd consumes 100% of CPU
But the directions mentioned elsewhere from https://dev.solus- project.com/T5224 do work even thought they appear to break Bluetooth (even with the updated instructions workaround mentioned in that thread). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1759836 Title: systemd-udevd consumes 100% of CPU Status in linux: Confirmed Status in The Ubuntu Power Consumption Project: New Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Confirmed Bug description: The systemd-udevd proccess consumes 100% of a thread everytime, but i'm not noticing any difference in my computer. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 29 08:52:54 2018 InstallationDate: Installed on 2018-03-05 (23 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304) MachineType: Dell Inc. Inspiron N5010 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=1 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 08R0GW dmi.board.vendor: Dell Inc. dmi.board.version: A12 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A12 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12: dmi.product.name: Inspiron N5010 dmi.product.version: A12 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/kernel/+bug/1759836/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1770166] Re: The brightness of the notebook
Brightness and other custom keybindings are the responsibility of the kernel. Although in some cases a BIOS update helps too. ** Changed in: xorg (Ubuntu) Status: Expired => New ** Package changed: xorg (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/1770166 Title: The brightness of the notebook Status in linux package in Ubuntu: New Bug description: The brightness of the notebook does not lower or rise with the FN key. Acer Aspire 5742 i3-380m 6gb ram ssd kingston 120gb. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Core Processor Integrated Graphics Controller [1025:0487] InstallationDate: Installed on 2018-06-14 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Acer Aspire 5742 Package: xorg 1:7.7+19ubuntu7 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=921bc593-7a3c-4ced-8659-695cfe311ce9 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Tags: bionic ubuntu Uname: Linux 4.15.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/14/2011 dmi.bios.vendor: Acer dmi.bios.version: V1.18 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Aspire 5742 dmi.board.vendor: Acer dmi.board.version: V1.18 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.18 dmi.modalias: dmi:bvnAcer:bvrV1.18:bd03/14/2011:svnAcer:pnAspire5742:pvrV1.18:rvnAcer:rnAspire5742:rvrV1.18:cvnAcer:ct10:cvrV1.18: dmi.product.family: Intel_Mobile dmi.product.name: Aspire 5742 dmi.product.version: V1.18 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770166/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1770166] [NEW] The brightness of the notebook
You have been subscribed to a public bug: The brightness of the notebook does not lower or rise with the FN key. Acer Aspire 5742 i3-380m 6gb ram ssd kingston 120gb. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Core Processor Integrated Graphics Controller [1025:0487] InstallationDate: Installed on 2018-06-14 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Acer Aspire 5742 Package: xorg 1:7.7+19ubuntu7 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=921bc593-7a3c-4ced-8659-695cfe311ce9 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Tags: bionic ubuntu Uname: Linux 4.15.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/14/2011 dmi.bios.vendor: Acer dmi.bios.version: V1.18 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Aspire 5742 dmi.board.vendor: Acer dmi.board.version: V1.18 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.18 dmi.modalias: dmi:bvnAcer:bvrV1.18:bd03/14/2011:svnAcer:pnAspire5742:pvrV1.18:rvnAcer:rnAspire5742:rvrV1.18:cvnAcer:ct10:cvrV1.18: dmi.product.family: Intel_Mobile dmi.product.name: Aspire 5742 dmi.product.version: V1.18 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: linux (Ubuntu) Importance: Low Status: New ** Tags: apport-collected bionic bios-outdated-1.30 ubuntu -- The brightness of the notebook https://bugs.launchpad.net/bugs/1770166 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 1775717] Re: CPU/GPU Fans suddenly go 100% RPM on Asus ROG G752VT
Regarding 2) - no 3d-party fan software on 16.04.
3) - running on 4.4.5-040405-generic now, but not for very long, can't be sure
yet if the issue is still present or not.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1775717
Title:
CPU/GPU Fans suddenly go 100% RPM on Asus ROG G752VT
Status in linux package in Ubuntu:
Incomplete
Bug description:
After upgrading from Ubuntu 16.04 to 18.04, I've noticed that CPU and
GPU fans suddenly go full throttle. It doesn't seem to depend on
temperature, could happen when 32 °C reported, sometimes the laptop
can work for day or two without this issue, but eventually it happens.
The only way to stop fans is to power off the laptop, power on (fans
go 100% at this point again), power off during BIOS splash screen and
power on again. Seems to happen more often after waking up from a
sleep.
Things tried:
Upgrading BIOS to latest available on ASUS site to the date of
writing. No change.
asus-fan kernel module (https://github.com/daringer/asus-fan). Detects
both fans and shows correct speed in /sys/class/hwmon/*/fan{1,2}*, but
does not seem to control it and does not prevent going full throttle.
4.17.0 kernel from Ubuntu mainline builds. Doesn't seem to affect the
issue.
Userspace fan control software (https://github.com/hirschmann/nbfc).
Can control speed of both fans to the point where they go full
throttle, after that has no effect on them.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: whale 3068 F pulseaudio
/dev/snd/controlC0: whale 3068 F pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
HibernationDevice: RESUME=UUID=ada9b595-bbf2-40a3-8575-5908492bb969
InstallationDate: Installed on 2014-10-20 (1333 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64+mac
(20140722.2)
MachineType: ASUSTeK COMPUTER INC. G752VT
NonfreeKernelModules: nvidia_modeset nvidia wl
Package: linux (not installed)
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic
root=UUID=f6509d56-6183-464c-90bb-9c3be2c8abdf ro quiet splash
acpi_backlight=vendor vt.handoff=1
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
RelatedPackageVersions:
linux-restricted-modules-4.15.0-23-generic N/A
linux-backports-modules-4.15.0-23-generic N/A
linux-firmware 1.173.1
Tags: bionic
Uname: Linux 4.15.0-23-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dip docker lpadmin plugdev sambashare sudo tty
video
_MarkForUpload: True
dmi.bios.date: 06/29/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: G752VT.304
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: G752VT
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrG752VT.304:bd06/29/2017:svnASUSTeKCOMPUTERINC.:pnG752VT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: G
dmi.product.name: G752VT
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/1775717/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1787869] [NEW] package libnvidia-compute-390 (not installed) failed to install/upgrade: a tentar sobreescrever '/etc/OpenCL/vendors/nvidia.icd' partilhado, que é diferente de ou
Public bug reported: Description:Ubuntu 18.04.1 LTS Release:18.04 libnvidia-compute-390: Instalado: (nenhum) Candidato: 390.48-0ubuntu3 Tabela de versão: 390.77-0ubuntu0~gpu18.04.1 -1 100 /var/lib/dpkg/status 390.48-0ubuntu3 500 500 http://br.archive.ubuntu.com/ubuntu bionic/restricted amd64 Packages # apt --fix-broken install Lendo listas de pacotes... Pronto Construindo árvore de dependências Lendo informação de estado... Pronto Corrigindo dependências... Pronto The following additional packages will be installed: libnvidia-compute-390 Os NOVOS pacotes a seguir serão instalados: libnvidia-compute-390 0 pacotes atualizados, 1 pacotes novos instalados, 0 a serem removidos e 0 não atualizados. 28 pacotes não totalmente instalados ou removidos. É preciso baixar 0 B/20,6 MB de arquivos. Depois desta operação, 85,8 MB adicionais de espaço em disco serão usados. Você quer continuar? [S/n] s (Lendo banco de dados ... 153679 ficheiros e directórios actualmente instalados.) A preparar para desempacotar .../libnvidia-compute-390_390.48-0ubuntu3_amd64.deb ... A descompactar libnvidia-compute-390:amd64 (390.48-0ubuntu3) ... dpkg: erro ao processar o arquivo /var/cache/apt/archives/libnvidia-compute-390_390.48-0ubuntu3_amd64.deb (--unpack): a tentar sobreescrever '/etc/OpenCL/vendors/nvidia.icd' partilhado, que é diferente de outras instâncias do pacote libnvidia-compute-390:amd64 dpkg-deb: erro: colar subprocess was killed by signal (Pipe quebrado) Erros foram encontrados durante o processamento de: /var/cache/apt/archives/libnvidia-compute-390_390.48-0ubuntu3_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libnvidia-compute-390 (not installed) Uname: Linux 4.14.41-041441-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Sun Aug 19 21:29:44 2018 ErrorMessage: a tentar sobreescrever '/etc/OpenCL/vendors/nvidia.icd' partilhado, que é diferente de outras instâncias do pacote libnvidia-compute-390:amd64 InstallationDate: Installed on 2018-08-15 (4 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3 SourcePackage: nvidia-graphics-drivers-390 Title: package libnvidia-compute-390 (not installed) failed to install/upgrade: a tentar sobreescrever '/etc/OpenCL/vendors/nvidia.icd' partilhado, que é diferente de outras instâncias do pacote libnvidia-compute-390:amd64 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- 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/1787869 Title: package libnvidia-compute-390 (not installed) failed to install/upgrade: a tentar sobreescrever '/etc/OpenCL/vendors/nvidia.icd' partilhado, que é diferente de outras instâncias do pacote libnvidia-compute-390:amd64 Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: Description: Ubuntu 18.04.1 LTS Release: 18.04 libnvidia-compute-390: Instalado: (nenhum) Candidato: 390.48-0ubuntu3 Tabela de versão: 390.77-0ubuntu0~gpu18.04.1 -1 100 /var/lib/dpkg/status 390.48-0ubuntu3 500 500 http://br.archive.ubuntu.com/ubuntu bionic/restricted amd64 Packages # apt --fix-broken install Lendo listas de pacotes... Pronto Construindo árvore de dependências Lendo informação de estado... Pronto Corrigindo dependências... Pronto The following additional packages will be installed: libnvidia-compute-390 Os NOVOS pacotes a seguir serão instalados: libnvidia-compute-390 0 pacotes atualizados, 1 pacotes novos instalados, 0 a serem removidos e 0 não atualizados. 28 pacotes não totalmente instalados ou removidos. É preciso baixar 0 B/20,6 MB de arquivos. Depois desta operação, 85,8 MB adicionais de espaço em disco serão usados. Você quer continuar? [S/n] s (Lendo banco de dados ... 153679 ficheiros e directórios actualmente instalados.) A preparar para desempacotar .../libnvidia-compute-390_390.48-0ubuntu3_amd64.deb ... A descompactar libnvidia-compute-390:amd64 (390.48-0ubuntu3) ... dpkg: erro ao processar o arquivo /var/cache/apt/archives/libnvidia-compute-390_390.48-0ubuntu3_amd64.deb (--unpack): a tentar sobreescrever '/etc/OpenCL/vendors/nvidia.icd' partilhado, que é diferente de outras instâncias do pacote libnvidia-compute-390:amd64 dpkg-deb: erro: colar subprocess was killed by signal (Pipe quebrado) Erros foram
[Kernel-packages] [Bug 1759836] Re: systemd-udevd consumes 100% of CPU
Nope, getting rid of '/lib/udev/rules.d/71-nvidia.rules' does nothing. It's a Mint 19 (Tara) with Cinnamon installation that I sometimes use on a Dell E6400 which used to work well with it before with earlier kernels. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1759836 Title: systemd-udevd consumes 100% of CPU Status in linux: Confirmed Status in The Ubuntu Power Consumption Project: New Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Confirmed Bug description: The systemd-udevd proccess consumes 100% of a thread everytime, but i'm not noticing any difference in my computer. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 29 08:52:54 2018 InstallationDate: Installed on 2018-03-05 (23 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304) MachineType: Dell Inc. Inspiron N5010 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=1 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 08R0GW dmi.board.vendor: Dell Inc. dmi.board.version: A12 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A12 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12: dmi.product.name: Inspiron N5010 dmi.product.version: A12 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/kernel/+bug/1759836/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1787861] 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/1787861 Title: Displays not detected/positioned correctly when disconnected/reconnected Status in linux package in Ubuntu: Confirmed Bug description: I just upgraded from Ubuntu 16.04 LTS to 18.04 LTS. Previously, this was all working correctly: I have 3 displays connected to an nVidia GT 730. VGA-0 (an old 21-inch CRT) is never enabled (just haven't got around to removing it). DVI-D-0 is the primary display, always connected and turned on, in 1920x1080 60hz. HDMI-0 is a secondary display (actually, linked to my AV receiver and then to my 55" HDTV), and it is turned on when I want the big screen (1920x1080 60hz, positioned to the left of the primary), turned off the rest of the time. Now, whenever I turn off my secondary HDMI display, my third (VGA) display is automatically enabled. Furthermore, when I then turn the secondary display back on, it is set to the wrong mode (interlaced at 30 Hz instead of progressive scan at 60 Hz) and in the wrong position (to the right of the main display, when I want it to the left). Running the correct 'xrandr' command to reset all three displays to the correct conditions instead results in random behavior--instead of a 3840x1080 screen, with the primary display offset to +1920x0, I usually end up with both displays set to span the entire 3840x1080 area, offset to +0x0 (so they're mirroring each other). Sometimes the VGA display remains turned on with a random (not actually displayable) resolution, sometimes it does not. Trying to force the displays into the correct mode with further 'xrandr' commands does not work; I have to reboot the machine to get the displays back to where they belong. This is the 'xrandr' command that SHOULD reset the displays to the correct modes/positions (the primary DVI display is already in the correct mode, so I don't specify that): xrandr --output VGA-0 --off --output DVI-D-0 --primary --output HDMI-0 --size 1920x1080 --rate 60 --left-of DVI-D-0 Occasionally, it does work correctly, but most of the time, it does not (see above). Under 16.04 LTS, I did have an issue for a long time where the secondary HDMI display would be set to an interlaced mode when I turned it back on (but otherwise, everything was correct--and a simple 'xrandr -output HDMI-0 --auto' fixed it); that problem was corrected with a kernel upgrade a short time ago (maybe 3 months?-- unfortunately, I never filed a bug and just lived with it, so I'm not sure exactly when the problem went away, either). Attached is the output of 'xrandr' with everything set correctly. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-32-generic 4.15.0-32.35 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jonathan 2183 F pulseaudio /dev/snd/controlC1: jonathan 2183 F pulseaudio /dev/snd/controlC0: jonathan 2183 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Aug 19 15:38:09 2018 HibernationDevice: RESUME=UUID=e0d7d646-78bf-474b-916a-ad6f8523c1b5 InstallationDate: Installed on 2015-08-17 (1098 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic root=UUID=2cd20c22-0c69-4ae2-b81c-11fd8501a2ec ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.15.0-32-generic N/A linux-backports-modules-4.15.0-32-generic N/A linux-firmware 1.173.1 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-08-15 (4 days ago) dmi.bios.date: 06/14/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0307 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A88T-M LE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0307:bd06/14/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A88T-MLE:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name
[Kernel-packages] [Bug 1787861] [NEW] Displays not detected/positioned correctly when disconnected/reconnected
Public bug reported: I just upgraded from Ubuntu 16.04 LTS to 18.04 LTS. Previously, this was all working correctly: I have 3 displays connected to an nVidia GT 730. VGA-0 (an old 21-inch CRT) is never enabled (just haven't got around to removing it). DVI-D-0 is the primary display, always connected and turned on, in 1920x1080 60hz. HDMI-0 is a secondary display (actually, linked to my AV receiver and then to my 55" HDTV), and it is turned on when I want the big screen (1920x1080 60hz, positioned to the left of the primary), turned off the rest of the time. Now, whenever I turn off my secondary HDMI display, my third (VGA) display is automatically enabled. Furthermore, when I then turn the secondary display back on, it is set to the wrong mode (interlaced at 30 Hz instead of progressive scan at 60 Hz) and in the wrong position (to the right of the main display, when I want it to the left). Running the correct 'xrandr' command to reset all three displays to the correct conditions instead results in random behavior--instead of a 3840x1080 screen, with the primary display offset to +1920x0, I usually end up with both displays set to span the entire 3840x1080 area, offset to +0x0 (so they're mirroring each other). Sometimes the VGA display remains turned on with a random (not actually displayable) resolution, sometimes it does not. Trying to force the displays into the correct mode with further 'xrandr' commands does not work; I have to reboot the machine to get the displays back to where they belong. This is the 'xrandr' command that SHOULD reset the displays to the correct modes/positions (the primary DVI display is already in the correct mode, so I don't specify that): xrandr --output VGA-0 --off --output DVI-D-0 --primary --output HDMI-0 --size 1920x1080 --rate 60 --left-of DVI-D-0 Occasionally, it does work correctly, but most of the time, it does not (see above). Under 16.04 LTS, I did have an issue for a long time where the secondary HDMI display would be set to an interlaced mode when I turned it back on (but otherwise, everything was correct--and a simple 'xrandr -output HDMI-0 --auto' fixed it); that problem was corrected with a kernel upgrade a short time ago (maybe 3 months?--unfortunately, I never filed a bug and just lived with it, so I'm not sure exactly when the problem went away, either). Attached is the output of 'xrandr' with everything set correctly. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-32-generic 4.15.0-32.35 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jonathan 2183 F pulseaudio /dev/snd/controlC1: jonathan 2183 F pulseaudio /dev/snd/controlC0: jonathan 2183 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Aug 19 15:38:09 2018 HibernationDevice: RESUME=UUID=e0d7d646-78bf-474b-916a-ad6f8523c1b5 InstallationDate: Installed on 2015-08-17 (1098 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic root=UUID=2cd20c22-0c69-4ae2-b81c-11fd8501a2ec ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.15.0-32-generic N/A linux-backports-modules-4.15.0-32-generic N/A linux-firmware 1.173.1 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-08-15 (4 days ago) dmi.bios.date: 06/14/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0307 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A88T-M LE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0307:bd06/14/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A88T-MLE:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic display multimonitor xrandr ** Attachment added: "'xrandr' output with correct modes & positions" https://bugs.launchpad.net/bugs/1787861/+attachment/5177693/+files/xrandr.output -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1787861 Title: Displays not detected/positioned
[Kernel-packages] [Bug 1774359] Re: could not find module by name='off'
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: New => Confirmed -- 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 1740231] Re: Add support for Realtek WiFi device [10ec:c821]
This is still broken in 18.10 and 18.04. Are there any plans to fix for 18.10? I can test if you give me instructions. -- 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/1740231 Title: Add support for Realtek WiFi device [10ec:c821] Status in HWE Next: Fix Released Status in HWE Next bionic series: New Status in linux package in Ubuntu: Incomplete Status in linux-oem package in Ubuntu: Fix Released Status in linux-oem source package in Xenial: Fix Released Bug description: PCI ID: 10ec:c821 The off-tree driver is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1740231/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1764645] Re: Bluetooth not working
I tried 4.15.0-33 in the hope of bluetooth again.
I should not have done. No ethernet, no wifi, and no bluetooth at all.
I know it's 'proposed', but I've been without a bionic bluetooth for
many months now. I just hope any official version is OK.
Yes, I know it's free. This is, however, the first time I've had serious
problems go on for this long.
All I have to do now is try to undo all the -33 changes (you guessed -
I'm not an expert!).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1764645
Title:
Bluetooth not working
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Committed
Bug description:
== SRU Justification ==
A regression was discovered in Bionic. The regression was introduced by
mainline commit f44cb4b19ed4, which then made it's way into Bionic in
4.15.0-14 as commit c91729972ac6 via stable updates.
This regression is fixed by mainline commit 803cdb8ce584. Commit
803cdb8ce584 was also cc'd to stable. However, it has not landed in
upstream stable 4.15 or Bionic.
== Fix ==
803cdb8ce584 ("Bluetooth: btusb: Apply QCA Rome patches for some ATH3012
models")
== Regression Potential ==
Low. This fix has also been cc'd to upstream stable, so it has had
additonal upstream review.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
I've installed the Ubuntu Bionic Beta 2 and everything works fine but
the bluetooth (perfectly working with Xenial). In bluetooth control
panel the slider is impossible to move to "on".
1) Ubuntu Release (via 'lsb_release -rd')
Description: Ubuntu Bionic Beaver (development branch)
Release: 18.04
2) Version of package (apt-cache policy gnome-bluetooth)
gnome-bluetooth:
Installato: 3.28.0-2
Candidato: 3.28.0-2
Tabella versione:
*** 3.28.0-2 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status
3) What you expected to happen
I expected to switch on the bluetooth.
4) What happened instead
Bluetooth won't switch on.
5) Output of rfkill list is:
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
6) Output of lspci -knn | grep Net -A3; lsusb; dmesg | grep -i blue is:
03:00.0 Network controller [0280]: Qualcomm Atheros AR9462 Wireless
Network Adapter [168c:0034] (rev 01)
Subsystem: Bigfoot Networks, Inc. Killer Wireless-N 1202 Half-
size Mini PCIe Card [1a56:2003]
Kernel driver in use: ath9k
Kernel modules: ath9k
04:00.0 Ethernet controller [0200]: Qualcomm Atheros QCA8171 Gigabit
Ethernet [1969:10a1] (rev 10)
Bus 002 Device 002: ID 8087:8000 Intel Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8008 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 004: ID 04f2:b414 Chicony Electronics Co., Ltd
Bus 003 Device 003: ID 0cf3:3004 Atheros Communications, Inc.
AR3012 Bluetooth 4.0
Bus 003 Device 002: ID 0b05:17c4 ASUSTek Computer, Inc.
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[ 17.715399] Bluetooth: Core ver 2.22
[ 17.715414] Bluetooth: HCI device and connection manager initialized
[ 17.715416] Bluetooth: HCI socket layer initialized
[ 17.715418] Bluetooth: L2CAP socket layer initialized
[ 17.715422] Bluetooth: SCO socket layer initialized
[ 17.723207] Bluetooth: hci0: don't support firmware rome 0x1102
[ 18.600648] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 18.600649] Bluetooth: BNEP filters: protocol multicast
[ 18.600651] Bluetooth: BNEP socket layer initialized
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-15-generic 4.15.0-15.16
ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
Uname: Linux 4.15.0-15-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: stormy 1484 F pulseaudio
/dev/snd/controlC0: stormy 1484 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 17 08:46:30 2018
HibernationDevice: RESUME=UUID=3f513ca9-6817-4099-9718-fee68d68ec11
InstallationDate: Installed on 2018-04-16 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
MachineType: ASUSTeK COMPUTER INC. G750JH
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
[Kernel-packages] [Bug 1670706] Re: Kernel Call Trace After Disabling an ath10k Wireless Device (Atheros QCA6174 802.11ac (rev 32))
I have the same issue with Linux Mint 19 (Ubuntu 18.04 based) using kernel 4.15 but for QCA9377 chipset. I compiled the 4.18 kernel using `make localmodconfig` and have the same problem. I had sources for kernel version 4.9.24 and it exhibits the same behavior (failed to wake target for write32) after going to suspend and then turning back on. Computer is a Dell Inspiron 14 3473. I've tried numerous debug steps like restarting network-manager, removing mac80211 cfg80211 ath10k ath10k_core and ath10k_pci modules then reinserting them and then restarting network-manager with no improvement. I have not played with "Wake on Wireless" settings yet (https://wireless.wiki.kernel.org/en/users/documentation/wowlan) While I have the QCA9377 I do believe this post is quite relavant: https://patchwork.kernel.org/patch/7548331/ so I'm going to check if that patch works for the QCA9377 and report back. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1670706 Title: Kernel Call Trace After Disabling an ath10k Wireless Device (Atheros QCA6174 802.11ac (rev 32)) Status in linux package in Ubuntu: Confirmed Bug description: Disabled a wireless adapter via NetworkManager. Got a kernel trace in dmesg. 3b:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32) uname -r 4.10.0-9-generic https://paste.ubuntu.com/24131142/ There are also usb hot-plug messages in between ath10k related ones - this is because I disabled a wireless adapter and immediately plugged in a usb type-c dock so don't mind those. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-9-generic 4.10.0-9.11 ProcVersionSignature: Ubuntu 4.10.0-9.11-generic 4.10.0 Uname: Linux 4.10.0-9-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dima 3007 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Tue Mar 7 17:28:37 2017 InstallationDate: Installed on 2017-02-27 (8 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170227) MachineType: Razer Blade ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-9-generic.efi.signed root=UUID=3f515c94-cd91-48b4-80f6-84ec24cb7b8f ro rootflags=subvol=@ quiet button.lid_init_state=open pcie_aspm=off RelatedPackageVersions: linux-restricted-modules-4.10.0-9-generic N/A linux-backports-modules-4.10.0-9-generic N/A linux-firmware1.163 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/10/2017 dmi.bios.vendor: Razer dmi.bios.version: 1.00 dmi.board.name: Razer dmi.board.vendor: Razer dmi.chassis.type: 9 dmi.chassis.vendor: Razer dmi.modalias: dmi:bvnRazer:bvr1.00:bd01/10/2017:svnRazer:pnBlade:pvr6.06:rvnRazer:rnRazer:rvr:cvnRazer:ct9:cvr: dmi.product.name: Blade dmi.product.version: 6.06 dmi.sys.vendor: Razer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1670706/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1781364] Re: Kernel error "task zfs:pid blocked for more than 120 seconds"
The bug will be fixed once the zfs package and the bionic kernel (that contains the zfs driver changes) will be released. So far, just the zfs package has been released and we are waiting for the kernel to complete the SRU update and verification phase - this takes a bit longer as the kernel contains a lot more other changes and we have to do more exhaustive testing. -- 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/1781364 Title: Kernel error "task zfs:pid blocked for more than 120 seconds" Status in Linux: Fix Released Status in linux package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in zfs-linux source package in Xenial: Confirmed Status in linux source package in Bionic: Fix Committed Status in zfs-linux source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in zfs-linux source package in Cosmic: Fix Released Bug description: == SRU Justification, XENIAL, BIONIC == Exercising ZFS with lxd with many mount/umounts can cause lockups and 120 second timeout messages. == How to reproduce bug == In a VM, 2 CPUs, 16GB of memory running Bionic: sudo apt update sudo apt install lxd lxd-client lxd-tools zfsutils-linux sudo lxd init (and with the default init options) then run: lxd-benchmark launch --count 96 --parallel 96 This will reliably show the lockup every time without the fix. With the fix (detailed below) one cannot reproduce the lockup. == Fix == Upstream ZFS commit commit ac09630d8b0bf6c92084a30fdaefd03fd0adbdc1 Author: Brian Behlendorf Date: Wed Jul 11 15:49:10 2018 -0700 Fix zpl_mount() deadlock == Regression Potential == This just changes the locking in the mount path of ZFS and will only affect ZFS mount/unmounts. The regression potential is small as this touches a very small code path that has been exhaustively exercises this code under multiple thread/CPU contention and shown not to break. -- ZFS bug report: https://github.com/zfsonlinux/zfs/issues/7691 "I am using LXD containers that are configured to use a ZFS storage backend. I create many containers using a benchmark tool, which probably stresses the use of ZFS. In two out of four attempts, I got [ 725.970508] INFO: task lxd:4455 blocked for more than 120 seconds. [ 725.976730] Tainted: P O 4.15.0-20-generic #21-Ubuntu [ 725.983551] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 725.991624] INFO: task txg_sync:4202 blocked for more than 120 seconds. [ 725.998264] Tainted: P O 4.15.0-20-generic #21-Ubuntu [ 726.005071] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 726.013313] INFO: task lxd:99919 blocked for more than 120 seconds. [ 726.019609] Tainted: P O 4.15.0-20-generic #21-Ubuntu [ 726.026418] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 726.034560] INFO: task zfs:100513 blocked for more than 120 seconds. [ 726.040936] Tainted: P O 4.15.0-20-generic #21-Ubuntu [ 726.047746] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 726.055791] INFO: task zfs:100584 blocked for more than 120 seconds. [ 726.062170] Tainted: P O 4.15.0-20-generic #21-Ubuntu [ 726.068979] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Describe how to reproduce the problem Start an Ubuntu 18.04 LTS server. Install LXD if not already installed. sudo apt update sudo apt install lxd lxd-client lxd-tools zfsutils-linux Configure LXD with sudo lxd init. When prompted for the storage backend, select ZFS and specify an empty disk. $ sudo lxd init Would you like to use LXD clustering? (yes/no) [default=no]: Do you want to configure a new storage pool? (yes/no) [default=yes]: Name of the new storage pool [default=default]: Name of the storage backend to use (dir, zfs) [default=zfs]: Create a new ZFS pool? (yes/no) [default=yes]: Would you like to use an existing block device? (yes/no) [default=no]: yes Path to the existing block device: /dev/sdb Would you like to connect to a MAAS server? (yes/no) [default=no]: Would you like to create a new local network bridge? (yes/no) [default=yes]: no Would you like to configure LXD to use an existing bridge or host interface? (yes/no) [default=no]: no Would you like LXD to be available over the network? (yes/no) [default=no]: Would you like stale cached images to be updated automatically? (yes/no) [default=yes] Would you like a YAML "lxd init" preseed to be printed? (yes/no) [default=no]: Now run the
[Kernel-packages] [Bug 1781364] Re: Kernel error "task zfs:pid blocked for more than 120 seconds"
I don't see the confirmation for Bionic in this bug report. Any update when the 4.17 kernel lands in bionic-proposed? Or do I need another kernel version for Bionic? What do I need exactly for my Bionic server? This bug prevents me from updating my lxd containers, it will hang the system consistently. -- 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/1781364 Title: Kernel error "task zfs:pid blocked for more than 120 seconds" Status in Linux: Fix Released Status in linux package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in zfs-linux source package in Xenial: Confirmed Status in linux source package in Bionic: Fix Committed Status in zfs-linux source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in zfs-linux source package in Cosmic: Fix Released Bug description: == SRU Justification, XENIAL, BIONIC == Exercising ZFS with lxd with many mount/umounts can cause lockups and 120 second timeout messages. == How to reproduce bug == In a VM, 2 CPUs, 16GB of memory running Bionic: sudo apt update sudo apt install lxd lxd-client lxd-tools zfsutils-linux sudo lxd init (and with the default init options) then run: lxd-benchmark launch --count 96 --parallel 96 This will reliably show the lockup every time without the fix. With the fix (detailed below) one cannot reproduce the lockup. == Fix == Upstream ZFS commit commit ac09630d8b0bf6c92084a30fdaefd03fd0adbdc1 Author: Brian Behlendorf Date: Wed Jul 11 15:49:10 2018 -0700 Fix zpl_mount() deadlock == Regression Potential == This just changes the locking in the mount path of ZFS and will only affect ZFS mount/unmounts. The regression potential is small as this touches a very small code path that has been exhaustively exercises this code under multiple thread/CPU contention and shown not to break. -- ZFS bug report: https://github.com/zfsonlinux/zfs/issues/7691 "I am using LXD containers that are configured to use a ZFS storage backend. I create many containers using a benchmark tool, which probably stresses the use of ZFS. In two out of four attempts, I got [ 725.970508] INFO: task lxd:4455 blocked for more than 120 seconds. [ 725.976730] Tainted: P O 4.15.0-20-generic #21-Ubuntu [ 725.983551] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 725.991624] INFO: task txg_sync:4202 blocked for more than 120 seconds. [ 725.998264] Tainted: P O 4.15.0-20-generic #21-Ubuntu [ 726.005071] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 726.013313] INFO: task lxd:99919 blocked for more than 120 seconds. [ 726.019609] Tainted: P O 4.15.0-20-generic #21-Ubuntu [ 726.026418] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 726.034560] INFO: task zfs:100513 blocked for more than 120 seconds. [ 726.040936] Tainted: P O 4.15.0-20-generic #21-Ubuntu [ 726.047746] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 726.055791] INFO: task zfs:100584 blocked for more than 120 seconds. [ 726.062170] Tainted: P O 4.15.0-20-generic #21-Ubuntu [ 726.068979] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Describe how to reproduce the problem Start an Ubuntu 18.04 LTS server. Install LXD if not already installed. sudo apt update sudo apt install lxd lxd-client lxd-tools zfsutils-linux Configure LXD with sudo lxd init. When prompted for the storage backend, select ZFS and specify an empty disk. $ sudo lxd init Would you like to use LXD clustering? (yes/no) [default=no]: Do you want to configure a new storage pool? (yes/no) [default=yes]: Name of the new storage pool [default=default]: Name of the storage backend to use (dir, zfs) [default=zfs]: Create a new ZFS pool? (yes/no) [default=yes]: Would you like to use an existing block device? (yes/no) [default=no]: yes Path to the existing block device: /dev/sdb Would you like to connect to a MAAS server? (yes/no) [default=no]: Would you like to create a new local network bridge? (yes/no) [default=yes]: no Would you like to configure LXD to use an existing bridge or host interface? (yes/no) [default=no]: no Would you like LXD to be available over the network? (yes/no) [default=no]: Would you like stale cached images to be updated automatically? (yes/no) [default=yes] Would you like a YAML "lxd init" preseed to be printed? (yes/no) [default=no]: Now run the following to launch 48 containers in batches of 12.
[Kernel-packages] [Bug 1780358] Re: 4.15.0-24 kernel doesn't return from sleep mode
Linux Mint 19 Tara Live ISO has same issue with sleep (suspend) mode. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1780358 Title: 4.15.0-24 kernel doesn't return from sleep mode Status in linux package in Ubuntu: Incomplete Bug description: Linux Mint 18.3 Cinnamon Lenovo Thinkpad Yoga 11e doesn't return from sleep mode after updating from 4.13.0-45 kernel to 4.15.0-24. The power light never indicates that the laptop is in sleep mode in the first place (it usually blinks). Then it won't wake up, black screen, ctrl-alt-f1 ctrl-alt-f8 have no effect. Must force power off and restart. --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alan 1315 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux 18.3 HibernationDevice: RESUME=UUID=1b994e5a-820b-4d88-90e8-574ba5c5a3c2 InstallationDate: Installed on 2018-04-13 (83 days ago) InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124 MachineType: LENOVO Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-45-generic root=UUID=c8750a76-04e5-4a28-a47d-9c8682606471 ro quiet splash intel_idle.max_cstate=1 vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16 RelatedPackageVersions: linux-restricted-modules-4.13.0-45-generic N/A linux-backports-modules-4.13.0-45-generic N/A linux-firmware 1.157.19 Tags: sylvia Uname: Linux 4.13.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom crontab dialout dip disk lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/17/2015 dmi.bios.vendor: LENOVO dmi.bios.version: N15ET66W (1.26) dmi.board.asset.tag: Not Available dmi.board.name: dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrN15ET66W(1.26):bd12/17/2015:svnLENOVO:pn:pvrThinkPadYoga11e:rvnLENOVO:rn:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad Yoga 11e dmi.product.name: dmi.product.version: ThinkPad Yoga 11e dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780358/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1787807] 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/1787807 Title: boot oops/4.15.0-32 regression Status in linux package in Ubuntu: Confirmed Bug description: 4.15.0-32 is failing to boot on this core2 laptop, 4.15.0-30 (and earlier) is fine. (I'll attach the screenshot of the panic in a second) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-30-generic 4.15.0-30.32 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 Uname: Linux 4.15.0-30-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dg 1504 F pulseaudio CurrentDesktop: XFCE Date: Sun Aug 19 13:07:20 2018 HibernationDevice: RESUME=/dev/mapper/davros--vg-swap_1 InstallationDate: Installed on 2015-12-25 (967 days ago) InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: TOSHIBA Equium A100 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-30-generic root=/dev/mapper/hostname--vg-root ro RelatedPackageVersions: linux-restricted-modules-4.15.0-30-generic N/A linux-backports-modules-4.15.0-30-generic N/A linux-firmware 1.173.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-03-30 (141 days ago) WifiSyslog: dmi.bios.date: 10/23/2006 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 2.10 dmi.board.name: MPAD-MSAE Customer Reference Boards dmi.board.vendor: Intel Corporation dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr2.10:bd10/23/2006:svnTOSHIBA:pnEquiumA100:pvrPSAABE-00J008EN:rvnIntelCorporation:rnMPAD-MSAECustomerReferenceBoards:rvrNotApplicable:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: Equium A100 dmi.product.version: PSAABE-00J008EN dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787807/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1733194] Re: kernel NULL pointer dereference in iwlmvm iwl_mvm_enable_txq
please report this NULL pointer exception to bugzilla.kernel.org and CC linuxw...@intel.com to the bug. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1733194 Title: kernel NULL pointer dereference in iwlmvm iwl_mvm_enable_txq Status in linux package in Ubuntu: Confirmed Bug description: When in AP mode after some time, get this BUG: Nov 18 23:21:31 bifrost kernel: [18345.860393] BUG: unable to handle kernel NULL pointer dereference at 0070 Nov 18 23:21:31 bifrost kernel: [18345.860552] IP: iwl_trans_pcie_txq_enable+0x62/0x440 [iwlwifi] Nov 18 23:21:31 bifrost kernel: [18345.860644] PGD 0 Nov 18 23:21:31 bifrost kernel: [18345.860646] P4D 0 Nov 18 23:21:31 bifrost kernel: [18345.860682] Nov 18 23:21:31 bifrost kernel: [18345.860747] Oops: 0002 [#1] SMP Nov 18 23:21:31 bifrost kernel: [18345.860800] Modules linked in: nfnetlink_queue nfnetlink_log nfnetlink dummy ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs ccm xfrm_user xfrm4_tunnel tunnel4 ipcomp xfrm_ipcomp esp4 ah4 af_key xfrm_algo xt_policy xt_multiport ip6table_filter ip6_tables ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat ipt_REJECT nf_reject_ipv4 xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack iptable_filter nls_iso8859_1 cmdlinepart intel_spi_platform intel_spi spi_nor mtd arc4 intel_rapl intel_soc_dts_thermal intel_soc_dts_iosf intel_powerclamp coretemp kvm_intel bridge kvm stp llc iwlmvm irqbypass punit_atom_debug mac80211 intel_cstate snd_hda_codec_hdmi iwlwifi snd_hda_codec_realtek snd_hda_codec_generic cfg80211 btusb snd_hda_intel lpc_ich btrtl snd_hda_codec snd_intel_sst_acpi Nov 18 23:21:31 bifrost kernel: [18345.861897] mei_txe snd_hda_core mei snd_hwdep shpchp snd_intel_sst_core snd_soc_sst_atom_hifi2_platform hci_uart snd_soc_sst_match snd_soc_core btbcm serdev snd_compress btqca ac97_bus btintel snd_pcm_dmaengine snd_pcm dw_dmac dw_dmac_core snd_timer bluetooth snd soundcore mac_hid intel_int0002_vgpio ecdh_generic spi_pxa2xx_platform rfkill_gpio pwm_lpss_platform pwm_lpss 8250_dw ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear i915 drm_kms_helper crct10dif_pclmul igb syscopyarea sysfillrect crc32_pclmul sysimgblt fb_sys_fops dca ghash_clmulni_intel i2c_algo_bit cryptd ahci ptp drm pps_core libahci video Nov 18 23:21:31 bifrost kernel: [18345.862995] i2c_hid hid sdhci_acpi sdhci Nov 18 23:21:31 bifrost kernel: [18345.863068] CPU: 1 PID: 1202 Comm: kworker/1:2 Tainted: GW 4.13.0-16-generic #19-Ubuntu Nov 18 23:21:31 bifrost kernel: [18345.863203] Hardware name: NF541 NF541/NF541, BIOS BAR1NA02 02/25/2016 Nov 18 23:21:31 bifrost kernel: [18345.863326] Workqueue: events iwl_mvm_add_new_dqa_stream_wk [iwlmvm] Nov 18 23:21:31 bifrost kernel: [18345.863428] task: 96862c1c5800 task.stack: a98a817c Nov 18 23:21:31 bifrost kernel: [18345.863539] RIP: 0010:iwl_trans_pcie_txq_enable+0x62/0x440 [iwlwifi] Nov 18 23:21:31 bifrost kernel: [18345.863635] RSP: 0018:a98a817c3be0 EFLAGS: 00010246 Nov 18 23:21:31 bifrost kernel: [18345.863718] RAX: 09c4 RBX: 001f RCX: Nov 18 23:21:31 bifrost kernel: [18345.863824] RDX: RSI: 001f RDI: 2710 Nov 18 23:21:31 bifrost kernel: [18345.863932] RBP: a98a817c3c30 R08: 2710 R09: 0001 Nov 18 23:21:31 bifrost kernel: [18345.864039] R10: R11: 9686344ce010 R12: Nov 18 23:21:31 bifrost kernel: [18345.864145] R13: 96862c9d0018 R14: R15: Nov 18 23:21:31 bifrost kernel: [18345.864253] FS: () GS:96863fc8() knlGS: Nov 18 23:21:31 bifrost kernel: [18345.864373] CS: 0010 DS: ES: CR0: 80050033 Nov 18 23:21:31 bifrost kernel: [18345.864461] CR2: 0070 CR3: 00023068b000 CR4: 001006e0 Nov 18 23:21:31 bifrost kernel: [18345.864568] Call Trace: Nov 18 23:21:31 bifrost kernel: [18345.864633] iwl_mvm_enable_txq+0x212/0x3a0 [iwlmvm] Nov 18 23:21:31 bifrost kernel: [18345.864732] iwl_mvm_add_new_dqa_stream_wk+0x7e8/0x15e0 [iwlmvm] Nov 18 23:21:31 bifrost kernel: [18345.864843] ? iwl_mvm_add_new_dqa_stream_wk+0x7e8/0x15e0 [iwlmvm] Nov 18 23:21:31 bifrost kernel: [18345.864945] ? __switch_to+0x211/0x520 Nov 18 23:21:31 bifrost kernel: [18345.865008] ? put_prev_entity+0x23/0xf0 Nov 18 23:21:31 bifrost kernel: [18345.865075] process_one_work+0x1e7/0x410 Nov 18 23:21:31 bifrost kernel: [18345.865143] worker_thread+0x4a/0x410 Nov 18 23:21:31 bifrost kernel:
[Kernel-packages] [Bug 1787807] Re: boot oops/4.15.0-32 regression
** Attachment added: "screenshot of boot oops" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787807/+attachment/5177502/+files/bootoops-32.jpg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1787807 Title: boot oops/4.15.0-32 regression Status in linux package in Ubuntu: New Bug description: 4.15.0-32 is failing to boot on this core2 laptop, 4.15.0-30 (and earlier) is fine. (I'll attach the screenshot of the panic in a second) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-30-generic 4.15.0-30.32 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 Uname: Linux 4.15.0-30-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dg 1504 F pulseaudio CurrentDesktop: XFCE Date: Sun Aug 19 13:07:20 2018 HibernationDevice: RESUME=/dev/mapper/davros--vg-swap_1 InstallationDate: Installed on 2015-12-25 (967 days ago) InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: TOSHIBA Equium A100 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-30-generic root=/dev/mapper/hostname--vg-root ro RelatedPackageVersions: linux-restricted-modules-4.15.0-30-generic N/A linux-backports-modules-4.15.0-30-generic N/A linux-firmware 1.173.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-03-30 (141 days ago) WifiSyslog: dmi.bios.date: 10/23/2006 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 2.10 dmi.board.name: MPAD-MSAE Customer Reference Boards dmi.board.vendor: Intel Corporation dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr2.10:bd10/23/2006:svnTOSHIBA:pnEquiumA100:pvrPSAABE-00J008EN:rvnIntelCorporation:rnMPAD-MSAECustomerReferenceBoards:rvrNotApplicable:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: Equium A100 dmi.product.version: PSAABE-00J008EN dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787807/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1787807] [NEW] boot oops/4.15.0-32 regression
Public bug reported: 4.15.0-32 is failing to boot on this core2 laptop, 4.15.0-30 (and earlier) is fine. (I'll attach the screenshot of the panic in a second) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-30-generic 4.15.0-30.32 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 Uname: Linux 4.15.0-30-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dg 1504 F pulseaudio CurrentDesktop: XFCE Date: Sun Aug 19 13:07:20 2018 HibernationDevice: RESUME=/dev/mapper/davros--vg-swap_1 InstallationDate: Installed on 2015-12-25 (967 days ago) InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: TOSHIBA Equium A100 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-30-generic root=/dev/mapper/hostname--vg-root ro RelatedPackageVersions: linux-restricted-modules-4.15.0-30-generic N/A linux-backports-modules-4.15.0-30-generic N/A linux-firmware 1.173.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-03-30 (141 days ago) WifiSyslog: dmi.bios.date: 10/23/2006 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 2.10 dmi.board.name: MPAD-MSAE Customer Reference Boards dmi.board.vendor: Intel Corporation dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr2.10:bd10/23/2006:svnTOSHIBA:pnEquiumA100:pvrPSAABE-00J008EN:rvnIntelCorporation:rnMPAD-MSAECustomerReferenceBoards:rvrNotApplicable:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: Equium A100 dmi.product.version: PSAABE-00J008EN dmi.sys.vendor: TOSHIBA ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug 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/1787807 Title: boot oops/4.15.0-32 regression Status in linux package in Ubuntu: New Bug description: 4.15.0-32 is failing to boot on this core2 laptop, 4.15.0-30 (and earlier) is fine. (I'll attach the screenshot of the panic in a second) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-30-generic 4.15.0-30.32 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 Uname: Linux 4.15.0-30-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dg 1504 F pulseaudio CurrentDesktop: XFCE Date: Sun Aug 19 13:07:20 2018 HibernationDevice: RESUME=/dev/mapper/davros--vg-swap_1 InstallationDate: Installed on 2015-12-25 (967 days ago) InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: TOSHIBA Equium A100 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-30-generic root=/dev/mapper/hostname--vg-root ro RelatedPackageVersions: linux-restricted-modules-4.15.0-30-generic N/A linux-backports-modules-4.15.0-30-generic N/A linux-firmware 1.173.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-03-30 (141 days ago) WifiSyslog: dmi.bios.date: 10/23/2006 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 2.10 dmi.board.name: MPAD-MSAE Customer Reference Boards dmi.board.vendor: Intel Corporation dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr2.10:bd10/23/2006:svnTOSHIBA:pnEquiumA100:pvrPSAABE-00J008EN:rvnIntelCorporation:rnMPAD-MSAECustomerReferenceBoards:rvrNotApplicable:cvnNoEnclosure:ct1:cvrN/A:
[Kernel-packages] [Bug 1787775] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1787775/+attachment/5177477/+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/1787775 Title: touchpad not working on lenovo yoga 530 Status in linux package in Ubuntu: Incomplete Bug description: The touchpad is not working and does not show up in cat /proc/bus/input/devices on multiple kernels. I've tried the newest kernel to date (19.08.18) and a few others. The touchpad works on windows. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-08-18 (0 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) Package: linux (not installed) Tags: bionic Uname: Linux 4.18.3-041803-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to bionic on 2018-08-18 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787775/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1787775] Re: touchpad not working on lenovo yoga 530
apport information ** Tags added: apport-collected bionic ** Description changed: The touchpad is not working and does not show up in cat /proc/bus/input/devices on multiple kernels. I've tried the newest kernel to date (19.08.18) and a few others. The touchpad works on windows. + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.2 + Architecture: amd64 + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2018-08-18 (0 days ago) + InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) + Package: linux (not installed) + Tags: bionic + Uname: Linux 4.18.3-041803-generic x86_64 + UnreportableReason: The running kernel is not an Ubuntu kernel + UpgradeStatus: Upgraded to bionic on 2018-08-18 (0 days ago) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1787775/+attachment/5177476/+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/1787775 Title: touchpad not working on lenovo yoga 530 Status in linux package in Ubuntu: Incomplete Bug description: The touchpad is not working and does not show up in cat /proc/bus/input/devices on multiple kernels. I've tried the newest kernel to date (19.08.18) and a few others. The touchpad works on windows. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-08-18 (0 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) Package: linux (not installed) Tags: bionic Uname: Linux 4.18.3-041803-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to bionic on 2018-08-18 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787775/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1730331] Re: ath10k_pci: firmware crashed!
For me the firmware also crashes on a > 02:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless > Network Adapter (rev 32) And it is always the same log. I changed nothing on my wifi, so the issue must have been introduced by some change in ubuntu. ** Attachment added: "ath10k_firmware_crash.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730331/+attachment/5177475/+files/ath10k_firmware_crash.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1730331 Title: ath10k_pci: firmware crashed! Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Confirmed Bug description: ... Nov 4 18:35:50 akane kernel: [ 10.216896] ath10k_pci :04:00.0: qca988x hw2.0 target 0x4100016c chip_id 0x043222ff sub : Nov 4 18:35:50 akane kernel: [ 10.216908] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 Nov 4 18:35:50 akane kernel: [ 10.217641] ath10k_pci :04:00.0: firmware ver 10.2.4.70.63-2 api 5 features no-p2p,raw-mode,mfp,allows-mesh-bcast crc32 4ff9e14d Nov 4 18:35:50 akane kernel: [ 10.228600] kvm: Nested Virtualization enabled Nov 4 18:35:50 akane kernel: [ 10.228611] kvm: Nested Paging enabled Nov 4 18:35:50 akane kernel: [ 10.258913] ath10k_pci :04:00.0: board_file api 1 bmi_id N/A crc32 bebc7c08 Nov 4 18:35:50 akane kernel: [ 10.263535] MCE: In-kernel MCE decoding enabled. Nov 4 18:35:50 akane kernel: [ 10.271401] EDAC amd64: Node 0: DRAM ECC enabled. Nov 4 18:35:50 akane kernel: [ 10.271416] EDAC amd64: F16h_M30h detected (node 0). Nov 4 18:35:50 akane kernel: [ 10.271491] EDAC MC: DCT0 chip selects: Nov 4 18:35:50 akane kernel: [ 10.271494] EDAC amd64: MC: 0: 4096MB 1: 0MB Nov 4 18:35:50 akane kernel: [ 10.271523] EDAC amd64: MC: 2: 0MB 3: 0MB Nov 4 18:35:50 akane kernel: [ 10.271526] EDAC amd64: MC: 4: 0MB 5: 0MB Nov 4 18:35:50 akane kernel: [ 10.271528] EDAC amd64: MC: 6: 0MB 7: 0MB Nov 4 18:35:50 akane kernel: [ 10.271530] EDAC MC: DCT1 chip selects: Nov 4 18:35:50 akane kernel: [ 10.271532] EDAC amd64: MC: 0: 0MB 1: 0MB Nov 4 18:35:50 akane kernel: [ 10.271534] EDAC amd64: MC: 2: 0MB 3: 0MB Nov 4 18:35:50 akane kernel: [ 10.271537] EDAC amd64: MC: 4: 0MB 5: 0MB Nov 4 18:35:50 akane kernel: [ 10.271539] EDAC amd64: MC: 6: 0MB 7: 0MB Nov 4 18:35:50 akane kernel: [ 10.271541] EDAC amd64: using x4 syndromes. Nov 4 18:35:50 akane kernel: [ 10.271542] EDAC amd64: MCT channel count: 1 Nov 4 18:35:50 akane kernel: [ 10.271829] EDAC MC0: Giving out device to module amd64_edac controller F16h_M30h: DEV :00:18.3 (INTERRUPT) Nov 4 18:35:50 akane kernel: [ 10.271892] EDAC PCI0: Giving out device to module amd64_edac controller EDAC PCI controller: DEV :00:18.2 (POLLED) Nov 4 18:35:50 akane kernel: [ 10.271894] AMD64 EDAC driver v3.5.0 Nov 4 18:35:50 akane kernel: [ 10.532131] EXT4-fs (sdc1): mounted filesystem with ordered data mode. Opts: errors=remount-ro Nov 4 18:35:50 akane kernel: [ 10.575859] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: errors=remount-ro Nov 4 18:35:50 akane kernel: [ 11.397803] ath10k_pci :04:00.0: firmware crashed! (uuid f75dd562-d1bb-40a7-8454-fdc5f86cb8aa) Nov 4 18:35:50 akane kernel: [ 11.407389] ath10k_pci :04:00.0: qca988x hw2.0 target 0x4100016c chip_id 0x043222ff sub : Nov 4 18:35:50 akane kernel: [ 11.407395] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 Nov 4 18:35:50 akane kernel: [ 11.408085] ath10k_pci :04:00.0: firmware ver 10.2.4.70.63-2 api 5 features no-p2p,raw-mode,mfp,allows-mesh-bcast crc32 4ff9e14d Nov 4 18:35:50 akane kernel: [ 11.408148] ath10k_pci :04:00.0: board_file api 1 bmi_id N/A crc32 bebc7c08 Nov 4 18:35:50 akane kernel: [ 11.408156] ath10k_pci :04:00.0: htt-ver 0.0 wmi-op 5 htt-op 2 cal otp max-sta 128 raw 0 hwcrypto 1 Nov 4 18:35:50 akane kernel: [ 11.410197] ath10k_pci :04:00.0: firmware register dump: Nov 4 18:35:50 akane kernel: [ 11.416213] ath10k_pci :04:00.0: [00]: 0x4100016C 0x15B3 0x009BFF84 0x00955B31 Nov 4 18:35:50 akane kernel: [ 11.424559] ath10k_pci :04:00.0: [04]: 0x009BFF84 0x00060130 0x0013 0x Nov 4 18:35:50 akane kernel: [ 11.432767] ath10k_pci :04:00.0: [08]: 0x009C8EA4 0x7170 0x0001 0x00435300 Nov 4 18:35:50 akane kernel: [ 11.441059] ath10k_pci :04:00.0: [12]: 0x0009 0x 0x00958360 0x0095836B Nov 4 18:35:50 akane kernel: [ 11.449397] ath10k_pci :04:00.0: [16]: 0x00958080 0x0094078E 0x 0x Nov 4 18:35:50 akane kernel: [ 11.457686] ath10k_pci :04:00.0: [20]:
[Kernel-packages] [Bug 1786890] Re: AR3012 Bluetooth
*** This bug is a duplicate of bug 1542743 *** https://bugs.launchpad.net/bugs/1542743 I don't think the duplicate status is correct as this device is 0930:0219 and the duplicate was device 0cf3:3004 and bug #1542743 should be fixed in 4.15.0-31 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1764645 This user seems to have an issue with the USB bus as the bluetooth is disconnecting and reconnecting and doesn't appear to be the firmware issue that plagued the 2 different 0cf3:3004 Atheros Bluetooth devices -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1786890 Title: AR3012 Bluetooth Status in linux package in Ubuntu: Incomplete Bug description: Qualcomm Atheros AR3012, sometimes can't work ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-30-generic 4.15.0-30.32 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 Uname: Linux 4.15.0-30-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rafael 1660 F pulseaudio CurrentDesktop: communitheme:ubuntu:GNOME Date: Mon Aug 13 22:26:37 2018 InstallationDate: Installed on 2018-05-09 (96 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: TOSHIBA Satellite L845 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=947b919c-6edd-4dc8-8592-b3a5cc7a25c4 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-30-generic N/A linux-backports-modules-4.15.0-30-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/27/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 6.50 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name1 dmi.board.vendor: Type2 - Board Vendor Name1 dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvr6.50:bd12/27/2012:svnTOSHIBA:pnSatelliteL845:pvrPSK8GM-025TM4:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.family: Type1Family dmi.product.name: Satellite L845 dmi.product.version: PSK8GM-025TM4 dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786890/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1787191] Re: Crash due to BUG: Bad page map in process X & BUG: Bad rss-counter state X
*** This bug is a duplicate of bug 1787127 *** https://bugs.launchpad.net/bugs/1787127 Just confirm, the 3.13.0-156 build from duplicate bug 1787127 resolved this. 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/1787191 Title: Crash due to BUG: Bad page map in process X & BUG: Bad rss-counter state X Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Bug description: Multiple SuperMicro based servers running 14.04 are experiencing continual kernel errors since upgrading to 3.13.0-155 which quickly leads to the system becoming unresponsive. The errors start immediately after boot. Small excerpt from the attached kern.log: Aug 15 09:54:15 server kernel: [0.00] CPU0 microcode updated early to revision 0x713, date = 2018-01-26 ... Aug 15 09:54:17 server kernel: [ 14.381553] ipmi device interface Aug 15 09:54:17 server kernel: [ 14.610493] NFS: Registering the id_resolver key type Aug 15 09:54:17 server kernel: [ 14.610504] Key type id_resolver registered Aug 15 09:54:17 server kernel: [ 14.610505] Key type id_legacy registered Aug 15 09:54:26 server kernel: [ 23.412042] BUG: Bad page map in process plymouthd pte:800860a3d966 pmd:465c17067 Aug 15 09:54:26 server kernel: [ 23.442867] addr:7fb8cc137000 vm_flags:08100073 anon_vma:880866695ab0 mapping:88086543a870 index:7 Aug 15 09:54:26 server kernel: [ 23.472375] vma->vm_ops->fault: filemap_fault+0x0/0x400 Aug 15 09:54:26 server kernel: [ 23.484454] vma->vm_file->f_op->mmap: ext4_file_mmap+0x0/0x60 Aug 15 09:54:26 server kernel: [ 23.496669] CPU: 4 PID: 523 Comm: plymouthd Tainted: GB 3.13.0-155-generic #205-Ubuntu Aug 15 09:54:26 server kernel: [ 23.496670] Hardware name: Supermicro X9DRD-iF/LF/X9DRD-iF, BIOS 3.0b 12/05/2013 Aug 15 09:54:26 server kernel: [ 23.496671] 880465f37d00 8173983f 7fb8cc137000 Aug 15 09:54:26 server kernel: [ 23.496675] 8808652c63c0 880465f37d50 8117e374 800860a3d966 Aug 15 09:54:26 server kernel: [ 23.496678] 000465c17067 0007 880465c179b8 800860a3d966 Aug 15 09:54:26 server kernel: [ 23.496681] Call Trace: Aug 15 09:54:26 server kernel: [ 23.496684] [] dump_stack+0x64/0x80 Aug 15 09:54:26 server kernel: [ 23.496687] [] print_bad_pte+0x1a4/0x250 Aug 15 09:54:26 server kernel: [ 23.496690] [] vm_normal_page+0x6e/0x80 Aug 15 09:54:26 server kernel: [ 23.496701] [] change_protection_range+0x55f/0x720 Aug 15 09:54:26 server kernel: [ 23.496706] [] change_protection+0x65/0xb0 Aug 15 09:54:26 server kernel: [ 23.496709] [] change_prot_numa+0x1b/0x40 Aug 15 09:54:26 server kernel: [ 23.496712] [] task_numa_work+0x1d2/0x300 Aug 15 09:54:26 server kernel: [ 23.496714] [] task_work_run+0xaf/0xd0 Aug 15 09:54:26 server kernel: [ 23.496717] [] do_notify_resume+0x97/0xb0 Aug 15 09:54:26 server kernel: [ 23.496720] [] int_signal+0x12/0x17 ... Aug 15 09:54:54 server kernel: [ 50.902769] BUG: Bad rss-counter state mm:880466869880 idx:1 val:338 Aug 15 09:55:25 server kernel: [ 82.513872] BUG: Bad rss-counter state mm:880866d6b800 idx:1 val:249 ... Aug 15 09:56:30 server kernel: [ 144.954186] CPU: 18 PID: 4139 Comm: php-cgi Tainted: GB 3.13.0-155-generic #205-Ubuntu Aug 15 09:56:30 server kernel: [ 144.954189] 880467cefd00 8173983f 02d2e000 Aug 15 09:56:30 server kernel: [ 144.954193] 000468950067 2d2e 880468950970 80042a764966 Aug 15 09:56:30 server kernel: [ 144.954195] [] dump_stack+0x64/0x80 Aug 15 09:56:30 server kernel: [ 144.954199] [] vm_normal_page+0x6e/0x80 Aug 15 09:56:30 server kernel: [ 144.954203] [] change_protection+0x65/0xb0 Aug 15 09:56:30 server kernel: [ 144.954207] [] change_prot_numa+0x1b/0x40 Aug 15 09:56:30 server kernel: [ 144.954211] [] task_work_run+0xaf/0xd0 Aug 15 09:56:30 server kernel: [ 144.954214] [] retint_signal+0x48/0x86 Aug 15 09:56:30 server kernel: [ 144.954216] addr:02d2f000 vm_flags:08100073 anon_vma:880467651c18 mapping: (null) index:2d2f Aug 15 09:56:30 server kernel: [ 144.954218] CPU: 18 PID: 4139 Comm: php-cgi Tainted: GB 3.13.0-155-generic #205-Ubuntu Aug 15 09:56:30 server kernel: [ 144.954218] Hardware name: Supermicro X9DRD-iF/LF/X9DRD-iF, BIOS 3.0b 12/05/2013 Aug 15 09:56:30 server kernel: [ 144.954221] 880467cefd00 8173983f 02d2f000 Aug 15 09:56:30 server kernel: [ 144.954223] 880868111800 880467cefd50 8117e374 80042a765966 Aug 15 09:56:30 server kernel: [ 144.954225] 000468950067 2d2f
[Kernel-packages] [Bug 1764645] Re: Bluetooth not working
It was in proposed 31, but not in the official release. How can I tell
if it will make official 33?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1764645
Title:
Bluetooth not working
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Committed
Bug description:
== SRU Justification ==
A regression was discovered in Bionic. The regression was introduced by
mainline commit f44cb4b19ed4, which then made it's way into Bionic in
4.15.0-14 as commit c91729972ac6 via stable updates.
This regression is fixed by mainline commit 803cdb8ce584. Commit
803cdb8ce584 was also cc'd to stable. However, it has not landed in
upstream stable 4.15 or Bionic.
== Fix ==
803cdb8ce584 ("Bluetooth: btusb: Apply QCA Rome patches for some ATH3012
models")
== Regression Potential ==
Low. This fix has also been cc'd to upstream stable, so it has had
additonal upstream review.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
I've installed the Ubuntu Bionic Beta 2 and everything works fine but
the bluetooth (perfectly working with Xenial). In bluetooth control
panel the slider is impossible to move to "on".
1) Ubuntu Release (via 'lsb_release -rd')
Description: Ubuntu Bionic Beaver (development branch)
Release: 18.04
2) Version of package (apt-cache policy gnome-bluetooth)
gnome-bluetooth:
Installato: 3.28.0-2
Candidato: 3.28.0-2
Tabella versione:
*** 3.28.0-2 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status
3) What you expected to happen
I expected to switch on the bluetooth.
4) What happened instead
Bluetooth won't switch on.
5) Output of rfkill list is:
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
6) Output of lspci -knn | grep Net -A3; lsusb; dmesg | grep -i blue is:
03:00.0 Network controller [0280]: Qualcomm Atheros AR9462 Wireless
Network Adapter [168c:0034] (rev 01)
Subsystem: Bigfoot Networks, Inc. Killer Wireless-N 1202 Half-
size Mini PCIe Card [1a56:2003]
Kernel driver in use: ath9k
Kernel modules: ath9k
04:00.0 Ethernet controller [0200]: Qualcomm Atheros QCA8171 Gigabit
Ethernet [1969:10a1] (rev 10)
Bus 002 Device 002: ID 8087:8000 Intel Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8008 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 004: ID 04f2:b414 Chicony Electronics Co., Ltd
Bus 003 Device 003: ID 0cf3:3004 Atheros Communications, Inc.
AR3012 Bluetooth 4.0
Bus 003 Device 002: ID 0b05:17c4 ASUSTek Computer, Inc.
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[ 17.715399] Bluetooth: Core ver 2.22
[ 17.715414] Bluetooth: HCI device and connection manager initialized
[ 17.715416] Bluetooth: HCI socket layer initialized
[ 17.715418] Bluetooth: L2CAP socket layer initialized
[ 17.715422] Bluetooth: SCO socket layer initialized
[ 17.723207] Bluetooth: hci0: don't support firmware rome 0x1102
[ 18.600648] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 18.600649] Bluetooth: BNEP filters: protocol multicast
[ 18.600651] Bluetooth: BNEP socket layer initialized
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-15-generic 4.15.0-15.16
ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
Uname: Linux 4.15.0-15-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: stormy 1484 F pulseaudio
/dev/snd/controlC0: stormy 1484 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 17 08:46:30 2018
HibernationDevice: RESUME=UUID=3f513ca9-6817-4099-9718-fee68d68ec11
InstallationDate: Installed on 2018-04-16 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
MachineType: ASUSTeK COMPUTER INC. G750JH
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=it_IT.UTF-8
SHELL=/bin/bash
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic.efi.signed
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
RelatedPackageVersions:
linux-restricted-modules-4.15.0-15-generic N/A
linux-backports-modules-4.15.0-15-generic N/A
[Kernel-packages] [Bug 1764645] Re: Bluetooth not working
Just installed the proposed 4.15.0-33. The fix is in. Bluetooth is
working.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1764645
Title:
Bluetooth not working
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Committed
Bug description:
== SRU Justification ==
A regression was discovered in Bionic. The regression was introduced by
mainline commit f44cb4b19ed4, which then made it's way into Bionic in
4.15.0-14 as commit c91729972ac6 via stable updates.
This regression is fixed by mainline commit 803cdb8ce584. Commit
803cdb8ce584 was also cc'd to stable. However, it has not landed in
upstream stable 4.15 or Bionic.
== Fix ==
803cdb8ce584 ("Bluetooth: btusb: Apply QCA Rome patches for some ATH3012
models")
== Regression Potential ==
Low. This fix has also been cc'd to upstream stable, so it has had
additonal upstream review.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
I've installed the Ubuntu Bionic Beta 2 and everything works fine but
the bluetooth (perfectly working with Xenial). In bluetooth control
panel the slider is impossible to move to "on".
1) Ubuntu Release (via 'lsb_release -rd')
Description: Ubuntu Bionic Beaver (development branch)
Release: 18.04
2) Version of package (apt-cache policy gnome-bluetooth)
gnome-bluetooth:
Installato: 3.28.0-2
Candidato: 3.28.0-2
Tabella versione:
*** 3.28.0-2 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status
3) What you expected to happen
I expected to switch on the bluetooth.
4) What happened instead
Bluetooth won't switch on.
5) Output of rfkill list is:
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
6) Output of lspci -knn | grep Net -A3; lsusb; dmesg | grep -i blue is:
03:00.0 Network controller [0280]: Qualcomm Atheros AR9462 Wireless
Network Adapter [168c:0034] (rev 01)
Subsystem: Bigfoot Networks, Inc. Killer Wireless-N 1202 Half-
size Mini PCIe Card [1a56:2003]
Kernel driver in use: ath9k
Kernel modules: ath9k
04:00.0 Ethernet controller [0200]: Qualcomm Atheros QCA8171 Gigabit
Ethernet [1969:10a1] (rev 10)
Bus 002 Device 002: ID 8087:8000 Intel Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8008 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 004: ID 04f2:b414 Chicony Electronics Co., Ltd
Bus 003 Device 003: ID 0cf3:3004 Atheros Communications, Inc.
AR3012 Bluetooth 4.0
Bus 003 Device 002: ID 0b05:17c4 ASUSTek Computer, Inc.
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[ 17.715399] Bluetooth: Core ver 2.22
[ 17.715414] Bluetooth: HCI device and connection manager initialized
[ 17.715416] Bluetooth: HCI socket layer initialized
[ 17.715418] Bluetooth: L2CAP socket layer initialized
[ 17.715422] Bluetooth: SCO socket layer initialized
[ 17.723207] Bluetooth: hci0: don't support firmware rome 0x1102
[ 18.600648] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 18.600649] Bluetooth: BNEP filters: protocol multicast
[ 18.600651] Bluetooth: BNEP socket layer initialized
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-15-generic 4.15.0-15.16
ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
Uname: Linux 4.15.0-15-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: stormy 1484 F pulseaudio
/dev/snd/controlC0: stormy 1484 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 17 08:46:30 2018
HibernationDevice: RESUME=UUID=3f513ca9-6817-4099-9718-fee68d68ec11
InstallationDate: Installed on 2018-04-16 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
MachineType: ASUSTeK COMPUTER INC. G750JH
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=it_IT.UTF-8
SHELL=/bin/bash
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic.efi.signed
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
RelatedPackageVersions:
linux-restricted-modules-4.15.0-15-generic N/A
linux-backports-modules-4.15.0-15-generic N/A
linux-firmware
