[Kernel-packages] [Bug 1638779] Re: [arm] Missing AHCI driver in Ubuntu Xenial Installer for ARM
Why the Ubuntu Server installer always require the CD-ROM detection to continue installation? In other OSes such as SUSE, CentOS, Fedora, ... I can install without the need of CD-ROM. Just dd-ing the ISO file into a USB key drive and use it for installation. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1638779 Title: [arm] Missing AHCI driver in Ubuntu Xenial Installer for ARM Status in linux package in Ubuntu: Confirmed Bug description: Download the media installation ISO file at https://www.ubuntu.com/download/server/arm and burn it to a CD-ROM. Then, put it into the SATA CD drive to install Ubuntu into Mustang/Merlin boards (XGene platform), the Installer does not detect the CD-ROM so it report a dialog with below content: "Your installation CD-ROM couldn't be mounted. This probably means that the CD-ROM was not in the drive. If so you can insert it and try again. Retry mounting the CD-ROM?". Investigate more on the installer media, I found that the AHCI driver is not enabled. Below steps I have done to check: - Mount ISO file and copy initrd.gz: # mkdir mnt # mount -o loop ubuntu-16.04.1-server-arm64.iso ./mnt # cp ./mnt/install/initrd.gz . - Extract initrd.gz: # gunzip initrd.gz # cpio -id < initrd - List the drivers/ata folder # ls lib/modules/4.4.0-31-generic/kernel/drivers block gpio gpu hid i2c input media mfd power regulator rtc usb video No lib/modules/4.4.0-31-generic/kernel/drivers/ata folder exist. Try to check with x86 installer media: # ls lib/modules/4.4.0-31-generic/kernel/drivers/ ata block char firewire gpio gpu hid hv i2c infiniband input media mfd net parport pcmcia power regulator rtc scsi tty usb video # lib/modules/4.4.0-31-generic/kernel/drivers/ata/ | grep ahci acard-ahci.ko ahci.ko ahci_platform.ko libahci.ko libahci_platform.ko Can you help to add AHCI support for Ubuntu ARM Media installer? Thanks, Thang Q. Nguyen PS: I submitted bug at https://bugs.launchpad.net/santacruz/+bug/1632559 but Thad asked to report here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1638779/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1706891] Re: ZFS 0.7.0 will require new userland tools
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: zfs-linux (Ubuntu) Status: New => Confirmed -- 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/1706891 Title: ZFS 0.7.0 will require new userland tools Status in zfs-linux package in Ubuntu: Confirmed Bug description: ZFS 0.7.0 has been released: http://list.zfsonlinux.org/pipermail/zfs- announce/2017-July/15.html. It is important to note it will require an update of the userland tools (zpool command). This can be an issue especially for the HWE kernel stack if ZFS module versions would bump to 0.7.0 without an update of the zfsutils and zfs-initramfs packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1706891/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1680904] Re: zesty unable to handle kernel NULL pointer dereference
** Also affects: linux-hwe (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/1680904 Title: zesty unable to handle kernel NULL pointer dereference Status in linux package in Ubuntu: In Progress Status in linux-hwe package in Ubuntu: New Status in linux source package in Zesty: In Progress Status in linux-hwe source package in Zesty: New Bug description: Upgraded to zesty about a week ago. Ran into this on latest kernel. (during high load, nothing in particular seems to cause it to happen). Did not happen with previous (4.10.0.14.16) kernel. Only after update to 4.10.0.15.17, has happened about 3 times since then (or other crashes), this is the one I could capture. kern.log entries below. Let me know if you need anything else from me. Thanks! Apr 7 11:20:28 doe kernel: [26003.796278] BUG: unable to handle kernel NULL pointer dereference at 0018 Apr 7 11:20:28 doe kernel: [26003.796375] IP: gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] Apr 7 11:20:28 doe kernel: [26003.796404] PGD 0 Apr 7 11:20:28 doe kernel: [26003.796405] Apr 7 11:20:28 doe kernel: [26003.796427] Oops: 0002 [#1] SMP Apr 7 11:20:28 doe kernel: [26003.796441] Modules linked in: xt_REDIRECT nf_nat_redirect xt_hl scsi_transport_iscsi binfmt_misc veth ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_filter ip6_tables ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_CHECKSUM xt_comment xt_tcpudp iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack libcrc32c iptable_mangle iptable_filter ccm rfcomm bridge stp llc cmac bnep zfs(PO) zunicode(PO) zavl(PO) zcommon(PO) znvpair(PO) spl(O) nls_iso8859_1 hid_multitouch joydev i2c_designware_platform i2c_designware_core snd_hda_codec_hdmi snd_soc_skl snd_soc_skl_ipc snd_soc_sst_ipc snd_soc_sst_dsp snd_hda_codec_realtek snd_hda_ext_core snd_soc_sst_match snd_hda_codec_generic snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel snd_hda_codec snd_hda_core asus_nb_wmi Apr 7 11:20:28 doe kernel: [26003.796722] snd_hwdep asus_wmi sparse_keymap snd_pcm arc4 snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device iwlmvm snd_timer mac80211 intel_rapl x86_pkg_temp_thermal snd intel_powerclamp uvcvideo coretemp kvm_intel iwlwifi videobuf2_vmalloc kvm videobuf2_memops irqbypass videobuf2_v4l2 intel_cstate videobuf2_core intel_rapl_perf cfg80211 videodev input_leds serio_raw media shpchp soundcore btusb btrtl hci_uart btbcm elan_i2c btqca btintel acpi_als int3403_thermal bluetooth kfifo_buf industrialio mac_hid idma64 mei_me virt_dma intel_pch_thermal acpi_pad int3400_thermal intel_lpss_pci int3402_thermal mei intel_lpss_acpi acpi_thermal_rel processor_thermal_device intel_lpss tpm_crb int340x_thermal_zone int3406_thermal intel_soc_dts_iosf asus_wireless parport_pc ppdev lp parport ip_tables Apr 7 11:20:28 doe kernel: [26003.797026] x_tables autofs4 algif_skcipher af_alg dm_crypt crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc i915 aesni_intel aes_x86_64 crypto_simd glue_helper cryptd i2c_algo_bit drm_kms_helper syscopyarea sysfillrect ahci sysimgblt libahci fb_sys_fops drm wmi i2c_hid hid pinctrl_sunrisepoint video pinctrl_intel fjes Apr 7 11:20:28 doe kernel: [26003.797142] CPU: 0 PID: 8418 Comm: chromium-browse Tainted: P O4.10.0-15-generic #17-Ubuntu Apr 7 11:20:28 doe kernel: [26003.797175] Hardware name: ASUSTeK COMPUTER INC. UX305CA/UX305CA, BIOS UX305CA.201 09/11/2015 Apr 7 11:20:28 doe kernel: [26003.797206] task: 9bbaa201dc00 task.stack: c25b5ea8c000 Apr 7 11:20:28 doe kernel: [26003.797250] RIP: 0010:gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] Apr 7 11:20:28 doe kernel: [26003.797279] RSP: 0018:c25b5ea8f880 EFLAGS: 00010246 Apr 7 11:20:28 doe kernel: [26003.797299] RAX: 9bba689be580 RBX: 0003 RCX: 0003 Apr 7 11:20:28 doe kernel: [26003.797325] RDX: RSI: 9bbae7c0a000 RDI: 9bbba0418000 Apr 7 11:20:28 doe kernel: [26003.797351] RBP: c25b5ea8f8d8 R08: R09: Apr 7 11:20:28 doe kernel: [26003.797378] R10: R11: 0041 R12: 9bbb5f00a000 Apr 7 11:20:28 doe kernel: [26003.797405] R13: 9bbba932bb10 R14: fff97000 R15: 8000 Apr 7 11:20:28 doe kernel: [26003.797440] FS: 7f70bd1df6c0() GS:93c0() knlGS: Apr 7 11:20:28 doe kernel: [26003.797470] CS: 0010 DS: ES: CR0: 80050033 Apr 7 11:20:28 doe kernel: [26003.797497] CR2: 0018 CR3: 00016942 CR4: 003406f0 Apr 7 11:20:28 doe kernel: [26003.797523] Call Trace: Apr 7 11:20:28 doe kernel: [26003.797553]
[Kernel-packages] [Bug 1680904] Re: zesty unable to handle kernel NULL pointer dereference
@Rex Tsai (chihchun) It will be ridiculous... $ uname -a Linux tro-T460p 4.10.0-28-generic #32-Ubuntu SMP Fri Jun 30 05:32:18 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1680904 Title: zesty unable to handle kernel NULL pointer dereference Status in linux package in Ubuntu: In Progress Status in linux source package in Zesty: In Progress Bug description: Upgraded to zesty about a week ago. Ran into this on latest kernel. (during high load, nothing in particular seems to cause it to happen). Did not happen with previous (4.10.0.14.16) kernel. Only after update to 4.10.0.15.17, has happened about 3 times since then (or other crashes), this is the one I could capture. kern.log entries below. Let me know if you need anything else from me. Thanks! Apr 7 11:20:28 doe kernel: [26003.796278] BUG: unable to handle kernel NULL pointer dereference at 0018 Apr 7 11:20:28 doe kernel: [26003.796375] IP: gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] Apr 7 11:20:28 doe kernel: [26003.796404] PGD 0 Apr 7 11:20:28 doe kernel: [26003.796405] Apr 7 11:20:28 doe kernel: [26003.796427] Oops: 0002 [#1] SMP Apr 7 11:20:28 doe kernel: [26003.796441] Modules linked in: xt_REDIRECT nf_nat_redirect xt_hl scsi_transport_iscsi binfmt_misc veth ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_filter ip6_tables ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_CHECKSUM xt_comment xt_tcpudp iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack libcrc32c iptable_mangle iptable_filter ccm rfcomm bridge stp llc cmac bnep zfs(PO) zunicode(PO) zavl(PO) zcommon(PO) znvpair(PO) spl(O) nls_iso8859_1 hid_multitouch joydev i2c_designware_platform i2c_designware_core snd_hda_codec_hdmi snd_soc_skl snd_soc_skl_ipc snd_soc_sst_ipc snd_soc_sst_dsp snd_hda_codec_realtek snd_hda_ext_core snd_soc_sst_match snd_hda_codec_generic snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel snd_hda_codec snd_hda_core asus_nb_wmi Apr 7 11:20:28 doe kernel: [26003.796722] snd_hwdep asus_wmi sparse_keymap snd_pcm arc4 snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device iwlmvm snd_timer mac80211 intel_rapl x86_pkg_temp_thermal snd intel_powerclamp uvcvideo coretemp kvm_intel iwlwifi videobuf2_vmalloc kvm videobuf2_memops irqbypass videobuf2_v4l2 intel_cstate videobuf2_core intel_rapl_perf cfg80211 videodev input_leds serio_raw media shpchp soundcore btusb btrtl hci_uart btbcm elan_i2c btqca btintel acpi_als int3403_thermal bluetooth kfifo_buf industrialio mac_hid idma64 mei_me virt_dma intel_pch_thermal acpi_pad int3400_thermal intel_lpss_pci int3402_thermal mei intel_lpss_acpi acpi_thermal_rel processor_thermal_device intel_lpss tpm_crb int340x_thermal_zone int3406_thermal intel_soc_dts_iosf asus_wireless parport_pc ppdev lp parport ip_tables Apr 7 11:20:28 doe kernel: [26003.797026] x_tables autofs4 algif_skcipher af_alg dm_crypt crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc i915 aesni_intel aes_x86_64 crypto_simd glue_helper cryptd i2c_algo_bit drm_kms_helper syscopyarea sysfillrect ahci sysimgblt libahci fb_sys_fops drm wmi i2c_hid hid pinctrl_sunrisepoint video pinctrl_intel fjes Apr 7 11:20:28 doe kernel: [26003.797142] CPU: 0 PID: 8418 Comm: chromium-browse Tainted: P O4.10.0-15-generic #17-Ubuntu Apr 7 11:20:28 doe kernel: [26003.797175] Hardware name: ASUSTeK COMPUTER INC. UX305CA/UX305CA, BIOS UX305CA.201 09/11/2015 Apr 7 11:20:28 doe kernel: [26003.797206] task: 9bbaa201dc00 task.stack: c25b5ea8c000 Apr 7 11:20:28 doe kernel: [26003.797250] RIP: 0010:gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] Apr 7 11:20:28 doe kernel: [26003.797279] RSP: 0018:c25b5ea8f880 EFLAGS: 00010246 Apr 7 11:20:28 doe kernel: [26003.797299] RAX: 9bba689be580 RBX: 0003 RCX: 0003 Apr 7 11:20:28 doe kernel: [26003.797325] RDX: RSI: 9bbae7c0a000 RDI: 9bbba0418000 Apr 7 11:20:28 doe kernel: [26003.797351] RBP: c25b5ea8f8d8 R08: R09: Apr 7 11:20:28 doe kernel: [26003.797378] R10: R11: 0041 R12: 9bbb5f00a000 Apr 7 11:20:28 doe kernel: [26003.797405] R13: 9bbba932bb10 R14: fff97000 R15: 8000 Apr 7 11:20:28 doe kernel: [26003.797440] FS: 7f70bd1df6c0() GS:93c0() knlGS: Apr 7 11:20:28 doe kernel: [26003.797470] CS: 0010 DS: ES: CR0: 80050033 Apr 7 11:20:28 doe kernel: [26003.797497] CR2: 0018 CR3: 00016942 CR4: 003406f0 Apr 7 11:20:28 doe kernel: [26003.797523] Call Trace: Apr 7 11:20:28 doe kernel: [26003.797553]
[Kernel-packages] [Bug 1644056] Re: kernel BUG at /build/linux-lts-xenial-gUF4JR/linux-lts-xenial-4.4.0/mm/huge_memory.c:1931!
I have the same issue: [Thu Jul 27 05:37:43 2017] /build/linux-5EyXrQ/linux-4.4.0/mm/pgtable-generic.c:33: bad pmd 880ff7409df8(00019b0009e2) [Thu Jul 27 06:10:03 2017] BUG: Bad rss-counter state mm:8804f6f26400 idx:1 val:512 [Thu Jul 27 06:10:03 2017] BUG: non-zero nr_ptes on freeing mm: 1 Would it be fixed by that patch: https://lkml.org/lkml/2017/4/10/152 which has been withdrawn in favor of https://lkml.org/lkml/2017/3/2/347 ? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1644056 Title: kernel BUG at /build/linux-lts-xenial-gUF4JR/linux-lts- xenial-4.4.0/mm/huge_memory.c:1931! Status in linux package in Ubuntu: Confirmed Bug description: Hi, While running IO on the following kernel/Ubuntu version: $ lsb_release -rd Description:Ubuntu 14.04.5 LTS Release:14.04 $ uname -a Linux 4.4.0-31-generic #50~14.04.1-Ubuntu SMP Wed Jul 13 01:07:32 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux $ cat /etc/issue Ubuntu 14.04.5 LTS \n \l [1133672.985186] /build/linux-lts-xenial-gUF4JR/linux-lts-xenial-4.4.0/mm/pgtable-generic.c:33: bad pmd 881fd6790240(80004b8008e7) [1135572.440941] huge_memory: mapcount 0 page_mapcount 1 [1135572.441607] [ cut here ] [1135572.442059] kernel BUG at /build/linux-lts-xenial-gUF4JR/linux-lts-xenial-4.4.0/mm/huge_memory.c:1931! [1135572.442571] invalid opcode: [#1] SMP [1135572.443028] Modules linked in: intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm joydev input_leds sb_edac irqbypass crct10dif_pclmul crc32_pclmul aesni_intel edac_core aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd dm_multipath lpc_ich ipmi_ssif ipmi_devintf shpchp 8250_fintek mac_hid acpi_power_meter ipmi_si ipmi_msghandler iTCO_wdt iTCO_vendor_support raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid0 multipath linear ses enclosure raid1 ast ttm ixgbe hid_generic igb vxlan drm_kms_helper syscopyarea ip6_udp_tunnel usbhid dca sysfillrect udp_tunnel sysimgblt hid mxm_wmi fb_sys_fops mpt3sas ptp drm ahci raid_class pps_core libahci i2c_algo_bit mdio scsi_transport_sas fjes wmi [1135572.448909] CPU: 15 PID: 2018 Comm: sh Not tainted 4.4.0-31-generic #50~14.04.1-Ubuntu [1135572.450082] Hardware name: Quanta Computer Inc. X-100.Column.01/S2PC-MB(Dual 1G LOM), BIOS S2P_3B04.HGT02 09/21/2016 [1135572.451346] task: 8814923ae040 ti: 882eba658000 task.ti: 882eba658000 [1135572.452494] RIP: 0010:[] [] __split_huge_page+0x691/0x6d0 [1135572.453580] RSP: 0018:882eba65b7e0 EFLAGS: 00010292 [1135572.454589] RAX: 0027 RBX: ea00012e RCX: [1135572.455742] RDX: 0001 RSI: 883fff3cdc78 RDI: 883fff3cdc78 [1135572.457040] RBP: 882eba65b860 R08: R09: 881fe93eaf00 [1135572.458271] R10: 03ff R11: 0ac1 R12: [1135572.459539] R13: 882eba65ba10 R14: ea00012e R15: ea00012e [1135572.460746] FS: 7fcf6b305740() GS:883fff3c() knlGS: [1135572.461972] CS: 0010 DS: ES: CR0: 80050033 [1135572.463237] CR2: 558db9da0bb8 CR3: 0021667eb000 CR4: 003406e0 [1135572.464515] DR0: DR1: DR2: [1135572.465831] DR3: DR6: fffe0ff0 DR7: 0400 [1135572.467177] Stack: [1135572.468502] 882eba65b840 811bdfe9 883fed2e51d0 [1135572.469769] 811c67c8 883fee9bb760 0007f43c9000 882eba65ba10 [1135572.471040] 7b6d 81c72fa0 883ff17340f4 ea00012e [1135572.472277] Call Trace: [1135572.473574] [] ? rmap_walk+0x239/0x2d0 [1135572.475079] [] split_huge_page_to_list+0x67/0xd0 [1135572.476473] [] add_to_swap+0x57/0x70 [1135572.477852] [] shrink_page_list+0x62c/0x770 [1135572.479246] [] shrink_inactive_list+0x1e9/0x500 [1135572.480688] [] shrink_lruvec+0x58e/0x730 [1135572.482077] [] ? __queue_work+0x130/0x350 [1135572.483615] [] ? __queue_work+0x130/0x350 [1135572.485078] [] shrink_zone+0xdc/0x2c0 [1135572.486661] [] do_try_to_free_pages+0x164/0x440 [1135572.488354] [] ? throttle_direct_reclaim+0x8d/0x230 [1135572.490068] [] try_to_free_pages+0xb5/0x170 [1135572.491535] [] __alloc_pages_nodemask+0x597/0xac0 [1135572.493287] [] alloc_kmem_pages_node+0x4d/0xd0 [1135572.495083] [] copy_process+0x185/0x1c70 [1135572.496792] [] ? from_kgid_munged+0x12/0x20 [1135572.498404] [] ? cp_new_stat+0x13d/0x160 [1135572.500116] [] _do_fork+0x8a/0x310 [1135572.501866] [] SyS_clone+0x19/0x20 [1135572.503672] [] entry_SYSCALL_64_fastpath+0x16/0x75 [1135572.505395] Code: 16 d0 fe ff e9 37
[Kernel-packages] [Bug 1644056] Re: kernel BUG at /build/linux-lts-xenial-gUF4JR/linux-lts-xenial-4.4.0/mm/huge_memory.c:1931!
$ uname -a Linux batch2 4.4.0-87-generic #110-Ubuntu SMP Tue Jul 18 12:55:35 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -rd Description:Ubuntu 16.04.1 LTS Release:16.04 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1644056 Title: kernel BUG at /build/linux-lts-xenial-gUF4JR/linux-lts- xenial-4.4.0/mm/huge_memory.c:1931! Status in linux package in Ubuntu: Confirmed Bug description: Hi, While running IO on the following kernel/Ubuntu version: $ lsb_release -rd Description:Ubuntu 14.04.5 LTS Release:14.04 $ uname -a Linux 4.4.0-31-generic #50~14.04.1-Ubuntu SMP Wed Jul 13 01:07:32 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux $ cat /etc/issue Ubuntu 14.04.5 LTS \n \l [1133672.985186] /build/linux-lts-xenial-gUF4JR/linux-lts-xenial-4.4.0/mm/pgtable-generic.c:33: bad pmd 881fd6790240(80004b8008e7) [1135572.440941] huge_memory: mapcount 0 page_mapcount 1 [1135572.441607] [ cut here ] [1135572.442059] kernel BUG at /build/linux-lts-xenial-gUF4JR/linux-lts-xenial-4.4.0/mm/huge_memory.c:1931! [1135572.442571] invalid opcode: [#1] SMP [1135572.443028] Modules linked in: intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm joydev input_leds sb_edac irqbypass crct10dif_pclmul crc32_pclmul aesni_intel edac_core aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd dm_multipath lpc_ich ipmi_ssif ipmi_devintf shpchp 8250_fintek mac_hid acpi_power_meter ipmi_si ipmi_msghandler iTCO_wdt iTCO_vendor_support raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid0 multipath linear ses enclosure raid1 ast ttm ixgbe hid_generic igb vxlan drm_kms_helper syscopyarea ip6_udp_tunnel usbhid dca sysfillrect udp_tunnel sysimgblt hid mxm_wmi fb_sys_fops mpt3sas ptp drm ahci raid_class pps_core libahci i2c_algo_bit mdio scsi_transport_sas fjes wmi [1135572.448909] CPU: 15 PID: 2018 Comm: sh Not tainted 4.4.0-31-generic #50~14.04.1-Ubuntu [1135572.450082] Hardware name: Quanta Computer Inc. X-100.Column.01/S2PC-MB(Dual 1G LOM), BIOS S2P_3B04.HGT02 09/21/2016 [1135572.451346] task: 8814923ae040 ti: 882eba658000 task.ti: 882eba658000 [1135572.452494] RIP: 0010:[] [] __split_huge_page+0x691/0x6d0 [1135572.453580] RSP: 0018:882eba65b7e0 EFLAGS: 00010292 [1135572.454589] RAX: 0027 RBX: ea00012e RCX: [1135572.455742] RDX: 0001 RSI: 883fff3cdc78 RDI: 883fff3cdc78 [1135572.457040] RBP: 882eba65b860 R08: R09: 881fe93eaf00 [1135572.458271] R10: 03ff R11: 0ac1 R12: [1135572.459539] R13: 882eba65ba10 R14: ea00012e R15: ea00012e [1135572.460746] FS: 7fcf6b305740() GS:883fff3c() knlGS: [1135572.461972] CS: 0010 DS: ES: CR0: 80050033 [1135572.463237] CR2: 558db9da0bb8 CR3: 0021667eb000 CR4: 003406e0 [1135572.464515] DR0: DR1: DR2: [1135572.465831] DR3: DR6: fffe0ff0 DR7: 0400 [1135572.467177] Stack: [1135572.468502] 882eba65b840 811bdfe9 883fed2e51d0 [1135572.469769] 811c67c8 883fee9bb760 0007f43c9000 882eba65ba10 [1135572.471040] 7b6d 81c72fa0 883ff17340f4 ea00012e [1135572.472277] Call Trace: [1135572.473574] [] ? rmap_walk+0x239/0x2d0 [1135572.475079] [] split_huge_page_to_list+0x67/0xd0 [1135572.476473] [] add_to_swap+0x57/0x70 [1135572.477852] [] shrink_page_list+0x62c/0x770 [1135572.479246] [] shrink_inactive_list+0x1e9/0x500 [1135572.480688] [] shrink_lruvec+0x58e/0x730 [1135572.482077] [] ? __queue_work+0x130/0x350 [1135572.483615] [] ? __queue_work+0x130/0x350 [1135572.485078] [] shrink_zone+0xdc/0x2c0 [1135572.486661] [] do_try_to_free_pages+0x164/0x440 [1135572.488354] [] ? throttle_direct_reclaim+0x8d/0x230 [1135572.490068] [] try_to_free_pages+0xb5/0x170 [1135572.491535] [] __alloc_pages_nodemask+0x597/0xac0 [1135572.493287] [] alloc_kmem_pages_node+0x4d/0xd0 [1135572.495083] [] copy_process+0x185/0x1c70 [1135572.496792] [] ? from_kgid_munged+0x12/0x20 [1135572.498404] [] ? cp_new_stat+0x13d/0x160 [1135572.500116] [] _do_fork+0x8a/0x310 [1135572.501866] [] SyS_clone+0x19/0x20 [1135572.503672] [] entry_SYSCALL_64_fastpath+0x16/0x75 [1135572.505395] Code: 16 d0 fe ff e9 37 fa ff ff 0f 0b 0f 0b 0f 0b 0f 0b 0f 0b 41 8b 57 18 8b 75 a4 48 c7 c7 48 f0 ac 81 31 c0 83 c2 01 e8 01 8d f9 ff <0f> 0b 48 8b 55 c0 4c 89 ee 4c 89 f7 89 4d a8 e8 5b d0 fe ff 8b [1135572.509080] RIP [] __split_huge_page+0x691/0x6d0 [1135572.510823]
[Kernel-packages] [Bug 1680904] Re: zesty unable to handle kernel NULL pointer dereference
@Nazar Gerasymchuk (troyan3) Could you provide the output of "uname -a" on your testing kernel? you might have installed the version from Ubuntu archive without the fix, but not the deb version I built. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1680904 Title: zesty unable to handle kernel NULL pointer dereference Status in linux package in Ubuntu: In Progress Status in linux source package in Zesty: In Progress Bug description: Upgraded to zesty about a week ago. Ran into this on latest kernel. (during high load, nothing in particular seems to cause it to happen). Did not happen with previous (4.10.0.14.16) kernel. Only after update to 4.10.0.15.17, has happened about 3 times since then (or other crashes), this is the one I could capture. kern.log entries below. Let me know if you need anything else from me. Thanks! Apr 7 11:20:28 doe kernel: [26003.796278] BUG: unable to handle kernel NULL pointer dereference at 0018 Apr 7 11:20:28 doe kernel: [26003.796375] IP: gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] Apr 7 11:20:28 doe kernel: [26003.796404] PGD 0 Apr 7 11:20:28 doe kernel: [26003.796405] Apr 7 11:20:28 doe kernel: [26003.796427] Oops: 0002 [#1] SMP Apr 7 11:20:28 doe kernel: [26003.796441] Modules linked in: xt_REDIRECT nf_nat_redirect xt_hl scsi_transport_iscsi binfmt_misc veth ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_filter ip6_tables ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_CHECKSUM xt_comment xt_tcpudp iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack libcrc32c iptable_mangle iptable_filter ccm rfcomm bridge stp llc cmac bnep zfs(PO) zunicode(PO) zavl(PO) zcommon(PO) znvpair(PO) spl(O) nls_iso8859_1 hid_multitouch joydev i2c_designware_platform i2c_designware_core snd_hda_codec_hdmi snd_soc_skl snd_soc_skl_ipc snd_soc_sst_ipc snd_soc_sst_dsp snd_hda_codec_realtek snd_hda_ext_core snd_soc_sst_match snd_hda_codec_generic snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel snd_hda_codec snd_hda_core asus_nb_wmi Apr 7 11:20:28 doe kernel: [26003.796722] snd_hwdep asus_wmi sparse_keymap snd_pcm arc4 snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device iwlmvm snd_timer mac80211 intel_rapl x86_pkg_temp_thermal snd intel_powerclamp uvcvideo coretemp kvm_intel iwlwifi videobuf2_vmalloc kvm videobuf2_memops irqbypass videobuf2_v4l2 intel_cstate videobuf2_core intel_rapl_perf cfg80211 videodev input_leds serio_raw media shpchp soundcore btusb btrtl hci_uart btbcm elan_i2c btqca btintel acpi_als int3403_thermal bluetooth kfifo_buf industrialio mac_hid idma64 mei_me virt_dma intel_pch_thermal acpi_pad int3400_thermal intel_lpss_pci int3402_thermal mei intel_lpss_acpi acpi_thermal_rel processor_thermal_device intel_lpss tpm_crb int340x_thermal_zone int3406_thermal intel_soc_dts_iosf asus_wireless parport_pc ppdev lp parport ip_tables Apr 7 11:20:28 doe kernel: [26003.797026] x_tables autofs4 algif_skcipher af_alg dm_crypt crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc i915 aesni_intel aes_x86_64 crypto_simd glue_helper cryptd i2c_algo_bit drm_kms_helper syscopyarea sysfillrect ahci sysimgblt libahci fb_sys_fops drm wmi i2c_hid hid pinctrl_sunrisepoint video pinctrl_intel fjes Apr 7 11:20:28 doe kernel: [26003.797142] CPU: 0 PID: 8418 Comm: chromium-browse Tainted: P O4.10.0-15-generic #17-Ubuntu Apr 7 11:20:28 doe kernel: [26003.797175] Hardware name: ASUSTeK COMPUTER INC. UX305CA/UX305CA, BIOS UX305CA.201 09/11/2015 Apr 7 11:20:28 doe kernel: [26003.797206] task: 9bbaa201dc00 task.stack: c25b5ea8c000 Apr 7 11:20:28 doe kernel: [26003.797250] RIP: 0010:gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] Apr 7 11:20:28 doe kernel: [26003.797279] RSP: 0018:c25b5ea8f880 EFLAGS: 00010246 Apr 7 11:20:28 doe kernel: [26003.797299] RAX: 9bba689be580 RBX: 0003 RCX: 0003 Apr 7 11:20:28 doe kernel: [26003.797325] RDX: RSI: 9bbae7c0a000 RDI: 9bbba0418000 Apr 7 11:20:28 doe kernel: [26003.797351] RBP: c25b5ea8f8d8 R08: R09: Apr 7 11:20:28 doe kernel: [26003.797378] R10: R11: 0041 R12: 9bbb5f00a000 Apr 7 11:20:28 doe kernel: [26003.797405] R13: 9bbba932bb10 R14: fff97000 R15: 8000 Apr 7 11:20:28 doe kernel: [26003.797440] FS: 7f70bd1df6c0() GS:93c0() knlGS: Apr 7 11:20:28 doe kernel: [26003.797470] CS: 0010 DS: ES: CR0: 80050033 Apr 7 11:20:28 doe kernel: [26003.797497] CR2: 0018 CR3: 00016942 CR4: 003406f0 Apr 7 11:20:28 doe kernel: [26003.797523] Call Trace: Apr 7 11:20:28 doe
[Kernel-packages] [Bug 1696541] Re: orangefs kernel module not compiled for amd64, i386
Should I report another bug for enabling CONFIG_ORANGEFS_FS=m in Zesty, Yakkety and Xenial LTS kernel packages? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1696541 Title: orangefs kernel module not compiled for amd64, i386 Status in linux package in Ubuntu: Fix Released Status in linux source package in Artful: Fix Released Bug description: The OrangeFS kernel module (/lib/modules//kernel/fs/orangefs/orangefs.ko) has been available as part of the Linux kernel since version 4.6, but has not been compiled as part of the ubuntu kernel-image package or any other package for the amd64 and i386 architectures. According to Ubuntu Package Search, it is being compiled for the arm64, armhf, and powerpc architectures. This bug report is to add support for OrangeFS by compiling the orangefs module and including it with the all kernel packages >= 4.6. This can be done by enabling CONFIG_ORANGEFS_FS as a module in the kernel config file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1696541/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1678477] Re: Kernel has troule recognizing Corsair Strafe RGB keyboard
I'm using the keyboard using Ubuntu 17.04 stock kernel with an external, independent powered, usb 2.0. It has a 3.0 Ampere power supply, not so big for these days, but powerful enough to avoid power problems for this keyboard. I'm using it for a while, several reboots and power-cycles, and I haven't had any error in dmesg, yet. It seems to confirm that it is a problem of power management on usb ports... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1678477 Title: Kernel has troule recognizing Corsair Strafe RGB keyboard Status in linux package in Ubuntu: Confirmed Bug description: I recently bought a Corsair Strafe RGB keyboard, and while it works well when successfully recognized by Ubuntu at boot, that doesn't always happen. I see messages like this when booting my desktop up: [6.619510] usb 3-10: unable to read config index 0 descriptor/all [6.619543] usb 3-10: can't read configurations, error -110 They sometimes repeat at 5-second intervals, culminating on a "can't set config #1" message or even "unable to enumerate USB device". This happens on the logic that deals with a new USB device being connected, so when it doesn't work it never gets to the HID drivers part of the code. When it does, hid-generic is quite able to control the keyboard, though this message appears on dmesg: [6.883811] usbhid 3-10:1.2: couldn't find an input interrupt endpoint From what I have been able to determine, the Corsair Strafe RGB has three inputs, with the last one being used as input/output and having something to do with the LEDs. It only has a single USB configuration, though I don't know why it times out. Searching on Google has a lot of people recommending this userspace drive to me: https://github.com/mattanger/ckb-next , and I've tried it, but it seems to be more about programming lighting effects into the keyboard than in controlling its basic operation, which is all I'm interested in. Its daemon was supposed to handle that part too, but it didn't fix those connection errors on boot. I have the following boot parameter set in my kernel, following advice from ckb-next's README, but it doesn't see to have an appreciable effect on my success rate: usbhid.quirks=0x1B1C:0x1B20:0x2448 ckb-next recommended 0x2408, but I added the HID_QUIRK_MULTI_INPUT as well in an attempt to improve things, without success. GRUB is always able to correctly identify the keyboard and get it to work, too, which makes the fact that the full kernel can't always do it a little more frustrating. I would be happy to provide any extra information you require on this issue. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-45-generic 4.8.0-45.48 ProcVersionSignature: Ubuntu 4.8.0-45.48-generic 4.8.17 Uname: Linux 4.8.0-45-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bira 2322 F pulseaudio /dev/snd/controlC0: bira 2322 F pulseaudio CurrentDesktop: i3 Date: Sat Apr 1 10:23:52 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2015-02-24 (767 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. Z97M-D3H ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-45-generic root=UUID=d1db423d-2a50-49ac-b4e7-fd50d73afaff ro quiet splash usbhid.quirks=0x1B1C:0x1B20:0x2448 RelatedPackageVersions: linux-restricted-modules-4.8.0-45-generic N/A linux-backports-modules-4.8.0-45-generic N/A linux-firmware1.161.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/30/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd05/30/2014:svnGigabyteTechnologyCo.,Ltd.:pnZ97M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: Z97M-D3H dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to:
[Kernel-packages] [Bug 1696154] Re: [17.10 FEAT] Sign POWER host/NV kernels
One open technical question from the Canonical side: can you confirm that the POWER firmware implementation will support embedded certificate chains as part of the vmlinux signature data? Our existing SecureBoot signing regime uses an on-line signing key which is chained to a our CA certificate, and it is the latter that we would normally provide for db. It appears that the kmodsign tools support embedded certificates in the signature data, but we would like to confirm that the firmware implementation is also compatible with this. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1696154 Title: [17.10 FEAT] Sign POWER host/NV kernels Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Bug description: Feature Description: Sign POWER host and NV kernels with sign-file in anticipation of POWER secure boot. Provide the associated certificate. Ideally it would be possible to reuse the UEFI shim private key and certificate used to sign and verify x86_64 kernels. More details to follow. Guest kernels will be addressed in a future separate feature request. Business Case: As a system administrator I want to verify the integrity of my kernels so that I can prevent malicious kernels from being executed. Use Case: Signed POWER kernels will be validated by OPAL as OpenPOWER systems boot when keys are properly installed and the system is booted in secure mode. Test Case: Sign and install a POWER kernel on an OpenPOWER machine with a firmware level that supports secure boot. Install a PK, distro KEK certificat, and distro DB certificate. Boot the system and verify that it will boot the kernel. Negative tests: Separately remove the signature, install an usigned kernel, and modify the kernel image and test that the kernel will not boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1696154/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1706891] [NEW] ZFS 0.7.0 will require new userland tools
Public bug reported: ZFS 0.7.0 has been released: http://list.zfsonlinux.org/pipermail/zfs- announce/2017-July/15.html. It is important to note it will require an update of the userland tools (zpool command). This can be an issue especially for the HWE kernel stack if ZFS module versions would bump to 0.7.0 without an update of the zfsutils and zfs-initramfs packages. ** Affects: zfs-linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1706891 Title: ZFS 0.7.0 will require new userland tools Status in zfs-linux package in Ubuntu: New Bug description: ZFS 0.7.0 has been released: http://list.zfsonlinux.org/pipermail/zfs- announce/2017-July/15.html. It is important to note it will require an update of the userland tools (zpool command). This can be an issue especially for the HWE kernel stack if ZFS module versions would bump to 0.7.0 without an update of the zfsutils and zfs-initramfs packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1706891/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1112898] Re: video error with ubuntu 12.10 and kernels after 3.50.21
** Attachment removed: "423690F5E6FFC934.jpg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1112898/+attachment/4920181/+files/423690F5E6FFC934.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/1112898 Title: video error with ubuntu 12.10 and kernels after 3.50.21 Status in Linux: Confirmed Status in linux package in Ubuntu: Fix Released Bug description: After the update to the kernel 3.50.22 when I rebooted the computer It only displayed some orange vertical lines instead of the login page (image 3), moving the mouse up it's point appears (over a black line)(image 5) and moving the mouse on the top-right corner the lines became grey(image 4) and clicking they became dark grey (the color of the shut-down menu) (image 6). Sometimes instead of the lines it shows the screen as shifted to the right (the right half of the screen ison the left and the left part on the right)(images 1 and 2 are of two different times I used the computer). The same happens with the 3.50.23 kernel. Booting with the 3.50.21 it works fine. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: linux-image-3.5.0-21-generic 3.5.0-21.32 ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1 Uname: Linux 3.5.0-21-generic x86_64 ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: carlo 1942 F pulseaudio /dev/snd/controlC0: carlo 1942 F pulseaudio CRDA: country CN: (2402 - 2482 @ 40), (N/A, 20) (5735 - 5835 @ 40), (N/A, 30) Date: Fri Feb 1 20:50:31 2013 HibernationDevice: RESUME=UUID=f7396edd-251d-4f47-8145-4a527cc77325 InstallationDate: Installed on 2012-11-26 (67 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: Hewlett-Packard p6-2312el MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-21-generic root=UUID=2e9203a8-b83b-4542-9464-0573af420737 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.5.0-21-generic N/A linux-backports-modules-3.5.0-21-generic N/A linux-firmware1.95 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/29/2012 dmi.bios.vendor: AMI dmi.bios.version: 8.07 dmi.board.name: 2ADA dmi.board.vendor: Foxconn dmi.board.version: 1.00 dmi.chassis.asset.tag: CZC2388M2J dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAMI:bvr8.07:bd08/29/2012:svnHewlett-Packard:pnp6-2312el:pvr:rvnFoxconn:rn2ADA:rvr1.00:cvnHewlett-Packard:ct3:cvr: dmi.product.name: p6-2312el dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1112898/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1680904] Re: zesty unable to handle kernel NULL pointer dereference
@Nazar Gerasymchuk (troyan3) No, you are not using my version. mime is built at Sat Jul 22 12:39:20 UTC 2017. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1680904 Title: zesty unable to handle kernel NULL pointer dereference Status in linux package in Ubuntu: In Progress Status in linux-hwe package in Ubuntu: New Status in linux source package in Zesty: In Progress Status in linux-hwe source package in Zesty: New Bug description: Upgraded to zesty about a week ago. Ran into this on latest kernel. (during high load, nothing in particular seems to cause it to happen). Did not happen with previous (4.10.0.14.16) kernel. Only after update to 4.10.0.15.17, has happened about 3 times since then (or other crashes), this is the one I could capture. kern.log entries below. Let me know if you need anything else from me. Thanks! Apr 7 11:20:28 doe kernel: [26003.796278] BUG: unable to handle kernel NULL pointer dereference at 0018 Apr 7 11:20:28 doe kernel: [26003.796375] IP: gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] Apr 7 11:20:28 doe kernel: [26003.796404] PGD 0 Apr 7 11:20:28 doe kernel: [26003.796405] Apr 7 11:20:28 doe kernel: [26003.796427] Oops: 0002 [#1] SMP Apr 7 11:20:28 doe kernel: [26003.796441] Modules linked in: xt_REDIRECT nf_nat_redirect xt_hl scsi_transport_iscsi binfmt_misc veth ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_filter ip6_tables ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_CHECKSUM xt_comment xt_tcpudp iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack libcrc32c iptable_mangle iptable_filter ccm rfcomm bridge stp llc cmac bnep zfs(PO) zunicode(PO) zavl(PO) zcommon(PO) znvpair(PO) spl(O) nls_iso8859_1 hid_multitouch joydev i2c_designware_platform i2c_designware_core snd_hda_codec_hdmi snd_soc_skl snd_soc_skl_ipc snd_soc_sst_ipc snd_soc_sst_dsp snd_hda_codec_realtek snd_hda_ext_core snd_soc_sst_match snd_hda_codec_generic snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel snd_hda_codec snd_hda_core asus_nb_wmi Apr 7 11:20:28 doe kernel: [26003.796722] snd_hwdep asus_wmi sparse_keymap snd_pcm arc4 snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device iwlmvm snd_timer mac80211 intel_rapl x86_pkg_temp_thermal snd intel_powerclamp uvcvideo coretemp kvm_intel iwlwifi videobuf2_vmalloc kvm videobuf2_memops irqbypass videobuf2_v4l2 intel_cstate videobuf2_core intel_rapl_perf cfg80211 videodev input_leds serio_raw media shpchp soundcore btusb btrtl hci_uart btbcm elan_i2c btqca btintel acpi_als int3403_thermal bluetooth kfifo_buf industrialio mac_hid idma64 mei_me virt_dma intel_pch_thermal acpi_pad int3400_thermal intel_lpss_pci int3402_thermal mei intel_lpss_acpi acpi_thermal_rel processor_thermal_device intel_lpss tpm_crb int340x_thermal_zone int3406_thermal intel_soc_dts_iosf asus_wireless parport_pc ppdev lp parport ip_tables Apr 7 11:20:28 doe kernel: [26003.797026] x_tables autofs4 algif_skcipher af_alg dm_crypt crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc i915 aesni_intel aes_x86_64 crypto_simd glue_helper cryptd i2c_algo_bit drm_kms_helper syscopyarea sysfillrect ahci sysimgblt libahci fb_sys_fops drm wmi i2c_hid hid pinctrl_sunrisepoint video pinctrl_intel fjes Apr 7 11:20:28 doe kernel: [26003.797142] CPU: 0 PID: 8418 Comm: chromium-browse Tainted: P O4.10.0-15-generic #17-Ubuntu Apr 7 11:20:28 doe kernel: [26003.797175] Hardware name: ASUSTeK COMPUTER INC. UX305CA/UX305CA, BIOS UX305CA.201 09/11/2015 Apr 7 11:20:28 doe kernel: [26003.797206] task: 9bbaa201dc00 task.stack: c25b5ea8c000 Apr 7 11:20:28 doe kernel: [26003.797250] RIP: 0010:gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] Apr 7 11:20:28 doe kernel: [26003.797279] RSP: 0018:c25b5ea8f880 EFLAGS: 00010246 Apr 7 11:20:28 doe kernel: [26003.797299] RAX: 9bba689be580 RBX: 0003 RCX: 0003 Apr 7 11:20:28 doe kernel: [26003.797325] RDX: RSI: 9bbae7c0a000 RDI: 9bbba0418000 Apr 7 11:20:28 doe kernel: [26003.797351] RBP: c25b5ea8f8d8 R08: R09: Apr 7 11:20:28 doe kernel: [26003.797378] R10: R11: 0041 R12: 9bbb5f00a000 Apr 7 11:20:28 doe kernel: [26003.797405] R13: 9bbba932bb10 R14: fff97000 R15: 8000 Apr 7 11:20:28 doe kernel: [26003.797440] FS: 7f70bd1df6c0() GS:93c0() knlGS: Apr 7 11:20:28 doe kernel: [26003.797470] CS: 0010 DS: ES: CR0: 80050033 Apr 7 11:20:28 doe kernel: [26003.797497] CR2: 0018 CR3: 00016942 CR4: 003406f0 Apr 7 11:20:28 doe kernel: [26003.797523] Call Trace: Apr 7 11:20:28 doe
[Kernel-packages] [Bug 1704614] Re: very long kernel boot time with some KVM switch
I followed the upstream bug report guidelines but I can't see my report being processed on the kernel ML, so I guess something made my report rejected... Any idea ? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1704614 Title: very long kernel boot time with some KVM switch Status in linux package in Ubuntu: Confirmed Bug description: I am using a Aten KVM switch CS1794 hooked on my computer. It allows the switching for USB, HDMI, and audio. http://www.aten.com/global/en/products/kvm/desktop-kvm-switches/cs1794/#.WWrnguk9iUk I run a Ubuntu 17.04 system. I experience a very long boot time, having done an analysis it appears that the main problem is the kernel boot time and more specifically the time it takes to start its USB subsystem. when you look at the dsmg output you can clearly see a gap between 4-78s and 79-91s, all in the USB sub-process. --- ApportVersion: 2.20.4-0ubuntu4.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: stranche 3670 F pulseaudio /dev/snd/controlC1: stranche 3670 F pulseaudio /dev/snd/controlC0: stranche 3670 F pulseaudio DistroRelease: Ubuntu 17.04 HibernationDevice: RESUME=UUID=28d4f703-2b20-4dd3-ba8b-aa363ad5141d InstallationDate: Installed on 2017-07-14 (2 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: System manufacturer System Product Name NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic.efi.signed root=UUID=4fde9883-6d7f-4954-90d6-779f37bbdc93 ro console=tty console=ttyUSB0,57600 noplymouth debug ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.10.0-26-generic N/A linux-backports-modules-4.10.0-26-generic N/A linux-firmware 1.164.1 RfKill: Tags: zesty Uname: Linux 4.10.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 08/13/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2104 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: SABERTOOTH Z77 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2104:bd08/13/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHZ77:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1704614/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1705921] Re: Wifi isn't identified for Ampak AP6212
My mainline is 4.10. Is it o.k? ** Attachment added: "dmesg_kernel_mainline" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705921/+attachment/4922379/+files/dmesg_kernel_mainline -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1705921 Title: Wifi isn't identified for Ampak AP6212 Status in linux package in Ubuntu: Confirmed Bug description: Even after I upgraded kernel to 4.10 Ubuntu doesn't identify my Ampak AP6212 card (neither for wifi nor for bluetooth). Here is the output of dmesg |less: file.io/PkdSHh --- ApportVersion: 2.20.1-0ubuntu2.9 Architecture: i386 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/comprC0D2', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: country IL: DFS-ETSI (2402 - 2482 @ 40), (N/A, 20), (N/A) (5150 - 5250 @ 80), (N/A, 23), (N/A), NO-OUTDOOR (5250 - 5350 @ 80), (N/A, 23), (0 ms), NO-OUTDOOR, DFS CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0feb912e-ce6a-440c-876e-2caa387a8241 InstallationDate: Installed on 2017-04-06 (108 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719) MachineType: Insyde BayTrail Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-27-generic root=UUID=d7a6add7-815e-46f2-8333-b73e0b6918ae ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-27.30~16.04.2-generic 4.10.17 RelatedPackageVersions: linux-restricted-modules-4.10.0-27-generic N/A linux-backports-modules-4.10.0-27-generic N/A linux-firmware 1.157.11 RfKill: 1: phy1: Wireless LAN Soft blocked: no Hard blocked: no Tags: xenial Uname: Linux 4.10.0-27-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/29/2014 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: DSO.00 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name dmi.board.vendor: Type2 - Board Manufacturer dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrDSO.00:bd10/29/2014:svnInsyde:pnBayTrail:pvrType1-TBDbyOEM:rvnType2-BoardManufacturer:rnType2-BoardProductName:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: BayTrail dmi.product.version: Type1 - TBD by OEM dmi.sys.vendor: Insyde To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705921/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1706977] [NEW] Issues with Nvidia GeForce GT 240M. Can't define monitor and set proper resolution. Also, Redshift doesn't work.
Public bug reported: Kernel: 4.4.0-87. Nvidia screen (after boot) has disappeared. System: Linux Mint 18.1 MATE Laptop: Fujitsu Amilo Pi 3560 I'm using 4.4.0-72 kernel for now with no such issues. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: 4.4.0-87 ** Tags added: 4.4.0-87 ** Description changed: Kernel: 4.4.0-87. Nvidia screen (after boot) disappeared. System: Linux Mint 18.1 MATE + Laptop: Fujitsu Amilo Pi 3560 I'm using 4.4.0-72 kernel for now with no such issues. ** Description changed: - Kernel: 4.4.0-87. Nvidia screen (after boot) disappeared. + Kernel: 4.4.0-87. Nvidia screen (after boot) has disappeared. System: Linux Mint 18.1 MATE - Laptop: Fujitsu Amilo Pi 3560 + Laptop: Fujitsu Amilo Pi 3560 I'm using 4.4.0-72 kernel for now with no such issues. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1706977 Title: Issues with Nvidia GeForce GT 240M. Can't define monitor and set proper resolution. Also, Redshift doesn't work. Status in linux package in Ubuntu: New Bug description: Kernel: 4.4.0-87. Nvidia screen (after boot) has disappeared. System: Linux Mint 18.1 MATE Laptop: Fujitsu Amilo Pi 3560 I'm using 4.4.0-72 kernel for now with no such issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1706977/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 153768] Re: External SATA (eSATA) removable disk not auto mounted
** Attachment removed: "578F10B724F785F39179C7F3583DA9F8.jpg" https://bugs.launchpad.net/ubuntu/+source/hal/+bug/153768/+attachment/4875732/+files/578F10B724F785F39179C7F3583DA9F8.jpg ** Attachment removed: "4F6C691672CBDC93618FEBD49F3086C0.jpg" https://bugs.launchpad.net/ubuntu/+source/hal/+bug/153768/+attachment/4886885/+files/4F6C691672CBDC93618FEBD49F3086C0.jpg ** Attachment removed: "272C6A3166687543AAB0D215D50CE643.jpg" https://bugs.launchpad.net/ubuntu/+source/hal/+bug/153768/+attachment/4904626/+files/272C6A3166687543AAB0D215D50CE643.jpg ** Attachment removed: "A96170A81F4666BE77EBB2DC04343C57.jpg" https://bugs.launchpad.net/ubuntu/+source/hal/+bug/153768/+attachment/4914409/+files/A96170A81F4666BE77EBB2DC04343C57.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/153768 Title: External SATA (eSATA) removable disk not auto mounted Status in HAL: Fix Released Status in Linux: Invalid Status in OEM Priority Project: Won't Fix Status in OEM Priority Project oneiric series: Won't Fix Status in hal package in Ubuntu: Won't Fix Status in linux package in Ubuntu: Won't Fix Status in udisks2 package in Ubuntu: Triaged Bug description: eSATA disks are are not auto mounted when plugged in. This is because udisks uses a heuristic to decide if it should auto mount a drive. The heuristic is motivated by the desire to not auto mount internal disks/partitions that belong to other operating systems. The heuristic currently makes the assumption that disks connected via a usb bus are external, and disks connected with other buses ( sata, scsi ) are internal, and thus does not mount them. This heuristic is inherently unreliable as usb disks can potentially be internal, and sas/sata disks can be external. Thus, the heuristic needs to be disabled, and all unknown disks need to be auto mounted. Disks detected but left unconfigured at install time should have entries in /etc/fstab set to noauto to prevent their being auto mounted. To manage notifications about this bug go to: https://bugs.launchpad.net/hal/+bug/153768/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1706946] [NEW] Sync crash 7.1.9-1 (main) from Debian unstable (main)
Public bug reported: Please sync crash 7.1.9-1 (main) from Debian unstable (main) Explanation of the Ubuntu delta and why it can be dropped: * Use only available repository pockets in autopkgtest (LP: #1693387) * Use isolation-machine in autopkgtest to ensure that the running kernel has available debug packages in the archive in use * Merge from Debian unstable (LP: #1672361). Remaining changes: - Build for armhf, ppc64el. - Minor fixes for live autopkgtest. * Merge from Debian unstable (LP: #1672361). Remaining changes: - Build for armhf, ppc64el. - Minor fixes for live autopkgtest. * d/p/0001-Fix-for-Linux-4.6-commit-b03a017bebc403d40aa53a092e7.patch : Fix additional kernel 4.6 issue introduced post-7.1.7 release. * d/p/0002-Fix-for-support-of-proc-kcore-as-the-live-memory-sou.patch : Fix live crash usage failure identified by autopkgtest. This commit was introduced post-7.1.7 release. * Merge from Debian unstable. Remaining changes: - Build for armhf, arm64, ppc64el. - Minor fixes for live autopkgtest. - debian/tests/live: Redirect gpg stderr to stdout, as that's the only known and expected stderr source. - Simplify ddeb archive requirements. * Dropped patches: - 0001-Fix-for-the-changes-made-to-the-kernel-module-struct.patch - 0002-Fix-for-the-changes-made-to-the-kernel-module-struct.patch * Merge from Debian unstable. Remaining changes: - Build for armhf, arm64, ppc64el. - Minor fixes for live autopkgtest. - debian/tests/live: Redirect gpg stderr to stdout, as that's the only known and expected stderr source. - Simplify ddeb archive requirements. * Dropped patches: - 0001-Fix-for-the-changes-made-to-the-kernel-module-struct.patch - 0002-Fix-for-the-changes-made-to-the-kernel-module-struct.patch * d/p/0002-Fix-for-the-changes-made-to-the-kernel-module-struct.patch: Cherry-pick additional crash commit needed to fix issues related to kernel commit 8244062e. (LP: #1564487) * d/p/0002-Fix-for-the-changes-made-to-the-kernel-module-struct.patch: Cherry-pick additional crash commit needed to fix issues related to kernel commit 8244062e. (LP: #1564487) * debian/tests/live: Use the new ddebs.ubuntu.com key C8CAB6595FDFF622 * d/p/0001-Fix-for-the-changes-made-to-the-kernel-module-struct.patch: Fix launch failure on kernel newer than 4.4 (LP: #1555244) * Merge from Debian unstable. Remaining changes: - Build for armhf, arm64, ppc64el. - Minor fixes for live autopkgtest. - debian/tests/live: Redirect gpg stderr to stdout, as that's the only known and expected stderr source. - Simplify ddeb archive requirements. * Dropped patches: - 4_2_support.patch The last delta consisted of fixing autopkgtest, building on more architectures and one one line to d/rules which is obsolete. The former changes are now integrated in Debian. Changelog entries since current artful version 7.1.8-1ubuntu2: crash (7.1.9-1) unstable; urgency=medium * Patch from Balint Reczey: Build crash on all Linux architectures (Closes: #763856, #757450) * Patch from Balint Reczey : Continuous integration tests can fail due to missing packages for the running kernel and missing *-updates packages (Closes: #869367) * Fixes to address three gcc-7.0.1 compiler warnings that are generated when building with "make warn". The warning types are "[-Wnonnull]" in filesys.c, and "[-Wformat-overflow=]" in kernel.c and cmdline.c. * Fix for the PPC64 "mach -o" option to update the OPAL console buffer size from 256K to 1MB, based upon the latest skiboot firmware source. * Fix for the "mod -[sS]" option to prevent the erroneous reassignment of one or more symbol values of a kernel module. Without the patch, when loading a kernel module, a message may indicate "mod: : last symbol: is not _MODULE_END_?" may be displayed, and one or more symbols may be reassigned an incorrect symbol value. If none of the erroneous symbol value reassignments are beyond the end of the module's address space, then there will be no message. * Linux 4.10 commit 401721ecd1dcb0a428aa5d6832ee05ffbdbffbbe finally exports the x86_64 "phys_base" value in the VMCOREINFO note, so utilize it whenever it exists. * Implemented a new "log -a" option that dumps the audit logs remaining in kernel audit buffers that have not been copied out to the user-space audit daemon. * Fix for the "kmem " option and the "search" command in x86_64 kernels that contain, or have backports of, kernel commit 7c1da8d0d046174a4188b5729d7579abf3d29427, titled "crypto: sha - SHA1 transform x86_64 AVX2", which introduced an "_end" text symbol. Without the patch, if a base kernel symbol address that is larger than the "_end" text symbol is passed to "kmem ", its symbol/filename information will
[Kernel-packages] [Bug 1700972] Re: Please only recommend or suggest initramfs-tools | linux-initramfs-tool for kernels able to boot without initramfs
** Changed in: linux-aws (Ubuntu) Status: New => Triaged ** Changed in: linux-aws (Ubuntu Xenial) Status: New => Triaged ** Changed in: linux-gke (Ubuntu) Status: New => Triaged ** Changed in: linux-gke (Ubuntu Xenial) Status: New => Triaged ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Marcelo Cerri (mhcerri) ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Marcelo Cerri (mhcerri) ** Changed in: linux-aws (Ubuntu) Assignee: (unassigned) => Marcelo Cerri (mhcerri) ** Changed in: linux-aws (Ubuntu Xenial) Assignee: (unassigned) => Marcelo Cerri (mhcerri) ** Changed in: linux-gke (Ubuntu) Assignee: (unassigned) => Marcelo Cerri (mhcerri) ** Changed in: linux-gke (Ubuntu Xenial) Assignee: (unassigned) => Marcelo Cerri (mhcerri) ** Changed in: linux-gke (Ubuntu) Importance: Undecided => Low ** Changed in: linux-gke (Ubuntu Xenial) Importance: Undecided => Low ** Changed in: linux-aws (Ubuntu Xenial) Importance: Undecided => Low ** Changed in: linux-aws (Ubuntu) Importance: Undecided => Low ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Low ** Changed in: linux (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1700972 Title: Please only recommend or suggest initramfs-tools | linux-initramfs- tool for kernels able to boot without initramfs Status in linux package in Ubuntu: Triaged Status in linux-aws package in Ubuntu: Triaged Status in linux-azure package in Ubuntu: In Progress Status in linux-gke package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Status in linux-aws source package in Xenial: Triaged Status in linux-azure source package in Xenial: In Progress Status in linux-gke source package in Xenial: Triaged Bug description: Linux kernel packages depend on initramfs-tools | linux-initramfs- tool, even when systems using the kernel can be booted without it. Demoting the dependency to Recommends: or Suggests: would allow creating smaller images without initramfs-tools installed and fully skipping initramfs updates upon kernel updates saving time. Please consider changing the Depends: to Recommends: or Suggests: for kernels capable of booting without initramfs. initramfs-tools is still a dependency of ubuntu-minimal thus accidental removal of initramfs-tools resulting an unbootable system would still be unlikely. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1700972/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1702910] Re: System freeze after in6_dev_finish_destroy errors
I can confirm the bug: Jul 12 16:45:39 k8s-agent-C5675ACA-0 kernel: [117514.320092] [ cut here ] Jul 12 16:45:39 k8s-agent-C5675ACA-0 kernel: [117514.320100] WARNING: CPU: 1 PID: 42381 at /build/linux-0uniEn/linux-4.4.0/net/ipv6/addrconf_core.c:159 in6_dev_finish_destroy+0x6b/0xc0() Jul 12 16:45:39 k8s-agent-C5675ACA-0 kernel: [117514.320102] Modules linked in: cmac arc4 md4 nls_utf8 cifs fscache xt_statistic sch_htb ebt_ip ebtable_filter xt_nat xt_recent ipt_REJECT nf_reject_ipv4 xt_tcpudp xt_mark xt_comment veth ebtable_nat ebtables ipt_MASQUERADE nf_nat_masquerade_ipv4 xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_filter ip_tables xt_conntrack x_tables nf_nat nf_conntrack br_netfilter bridge stp llc overlay i2c_piix4 8250_fintek input_leds joydev mac_hid serio_raw ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr sunrpc iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic crct10dif_pclmul crc32_pclmul ghash_clmulni_intel hv_netvsc hv_utils hid_hyperv hv_storvsc hid scsi_transport_fc hyperv_keyboard aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_he lper hyperv_fb cryptd psmouse pata_acpi hv_vmbus floppy fjes Jul 12 16:45:39 k8s-agent-C5675ACA-0 kernel: [117514.320149] CPU: 1 PID: 42381 Comm: kworker/u128:3 Not tainted 4.4.0-83-generic #106-Ubuntu Jul 12 16:45:39 k8s-agent-C5675ACA-0 kernel: [117514.320151] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090006 05/23/2012 Jul 12 16:45:39 k8s-agent-C5675ACA-0 kernel: [117514.320155] Workqueue: netns cleanup_net Jul 12 16:45:39 k8s-agent-C5675ACA-0 kernel: [117514.320156] 0286 174b4ae5 880686863ba0 813f9513 Jul 12 16:45:39 k8s-agent-C5675ACA-0 kernel: [117514.320158] 81d75940 880686863bd8 81081322 Jul 12 16:45:39 k8s-agent-C5675ACA-0 kernel: [117514.320160] 88048ff82800 88048ff8 0006 880686863ca8 Jul 12 16:45:39 k8s-agent-C5675ACA-0 kernel: [117514.320162] Call Trace: Jul 12 16:45:39 k8s-agent-C5675ACA-0 kernel: [117514.320166] [] dump_stack+0x63/0x90 Jul 12 16:45:39 k8s-agent-C5675ACA-0 kernel: [117514.320170] [] warn_slowpath_common+0x82/0xc0 Jul 12 16:45:39 k8s-agent-C5675ACA-0 kernel: [117514.320172] [] warn_slowpath_null+0x1a/0x20 Jul 12 16:45:39 k8s-agent-C5675ACA-0 kernel: [117514.320173] [] in6_dev_finish_destroy+0x6b/0xc0 Jul 12 16:45:39 k8s-agent-C5675ACA-0 kernel: [117514.320176] [] ip6_route_dev_notify+0x116/0x130 Jul 12 16:45:39 k8s-agent-C5675ACA-0 kernel: [117514.320178] [] notifier_call_chain+0x4a/0x70 Jul 12 16:45:39 k8s-agent-C5675ACA-0 kernel: [117514.320180] [] raw_notifier_call_chain+0x16/0x20 Jul 12 16:45:39 k8s-agent-C5675ACA-0 kernel: [117514.320182] [] call_netdevice_notifiers_info+0x35/0x60 Jul 12 16:45:39 k8s-agent-C5675ACA-0 kernel: [117514.320185] [] netdev_run_todo+0x16d/0x320 Jul 12 16:45:39 k8s-agent-C5675ACA-0 kernel: [117514.320187] [] rtnl_unlock+0xe/0x10 Jul 12 16:45:39 k8s-agent-C5675ACA-0 kernel: [117514.320189] [] default_device_exit_batch+0x147/0x170 Jul 12 16:45:39 k8s-agent-C5675ACA-0 kernel: [117514.320193] [] ? __wake_up_sync+0x20/0x20 Jul 12 16:45:39 k8s-agent-C5675ACA-0 kernel: [117514.320195] [] ops_exit_list.isra.4+0x52/0x60 Jul 12 16:45:39 k8s-agent-C5675ACA-0 kernel: [117514.320196] [] cleanup_net+0x1c2/0x2a0 Jul 12 16:45:39 k8s-agent-C5675ACA-0 kernel: [117514.320199] [] process_one_work+0x165/0x480 Jul 12 16:45:39 k8s-agent-C5675ACA-0 kernel: [117514.320201] [] worker_thread+0x4b/0x4c0 Jul 12 16:45:39 k8s-agent-C5675ACA-0 kernel: [117514.320202] [] ? process_one_work+0x480/0x480 Jul 12 16:45:39 k8s-agent-C5675ACA-0 kernel: [117514.320204] [] kthread+0xe5/0x100 Jul 12 16:45:39 k8s-agent-C5675ACA-0 kernel: [117514.320205] [] ? kthread_create_on_node+0x1e0/0x1e0 Jul 12 16:45:39 k8s-agent-C5675ACA-0 kernel: [117514.320209] [] ret_from_fork+0x3f/0x70 Jul 12 16:45:39 k8s-agent-C5675ACA-0 kernel: [117514.320210] [] ? kthread_create_on_node+0x1e0/0x1e0 Jul 12 16:45:39 k8s-agent-C5675ACA-0 kernel: [117514.320211] ---[ end trace b549322d7d3fedbf ]--- Jul 12 16:45:39 k8s-agent-C5675ACA-0 kernel: [117514.320212] [ cut here ] Jul 12 16:45:39 k8s-agent-C5675ACA-0 kernel: [117514.320214] WARNING: CPU: 1 PID: 42381 at /build/linux-0uniEn/linux-4.4.0/net/ipv6/addrconf_core.c:160 in6_dev_finish_destroy+0x83/0xc0() Jul 12 16:45:39 k8s-agent-C5675ACA-0 kernel: [117514.320214] Modules linked in: cmac arc4 md4 nls_utf8 cifs fscache xt_statistic sch_htb ebt_ip ebtable_filter xt_nat xt_recent ipt_REJECT nf_reject_ipv4 xt_tcpudp xt_mark xt_comment veth ebtable_nat ebtables ipt_MASQUERADE nf_nat_masquerade_ipv4 xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4
[Kernel-packages] [Bug 1705921] Re: Wifi isn't identified for Ampak AP6212
KHF ** Attachment added: "dmesg_kernelKHF" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705921/+attachment/4922380/+files/dmesg_kernelKHF -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1705921 Title: Wifi isn't identified for Ampak AP6212 Status in linux package in Ubuntu: Confirmed Bug description: Even after I upgraded kernel to 4.10 Ubuntu doesn't identify my Ampak AP6212 card (neither for wifi nor for bluetooth). Here is the output of dmesg |less: file.io/PkdSHh --- ApportVersion: 2.20.1-0ubuntu2.9 Architecture: i386 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/comprC0D2', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: country IL: DFS-ETSI (2402 - 2482 @ 40), (N/A, 20), (N/A) (5150 - 5250 @ 80), (N/A, 23), (N/A), NO-OUTDOOR (5250 - 5350 @ 80), (N/A, 23), (0 ms), NO-OUTDOOR, DFS CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0feb912e-ce6a-440c-876e-2caa387a8241 InstallationDate: Installed on 2017-04-06 (108 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719) MachineType: Insyde BayTrail Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-27-generic root=UUID=d7a6add7-815e-46f2-8333-b73e0b6918ae ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-27.30~16.04.2-generic 4.10.17 RelatedPackageVersions: linux-restricted-modules-4.10.0-27-generic N/A linux-backports-modules-4.10.0-27-generic N/A linux-firmware 1.157.11 RfKill: 1: phy1: Wireless LAN Soft blocked: no Hard blocked: no Tags: xenial Uname: Linux 4.10.0-27-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/29/2014 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: DSO.00 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name dmi.board.vendor: Type2 - Board Manufacturer dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrDSO.00:bd10/29/2014:svnInsyde:pnBayTrail:pvrType1-TBDbyOEM:rvnType2-BoardManufacturer:rnType2-BoardProductName:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: BayTrail dmi.product.version: Type1 - TBD by OEM dmi.sys.vendor: Insyde To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705921/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1700657] Re: Touchpad not detected in Lenovo X1 Yoga / Yoga 720-15IKB
There was a commit regarding the elan_i2c driver: https://github.com/torvalds/linux/commit/a2eaf299d134cfe780c68c771f88d81516c1e70d -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1700657 Title: Touchpad not detected in Lenovo X1 Yoga / Yoga 720-15IKB Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: Touchpad is not automatically detected in 14.04, 16.04 or 17.04. I tried in live mode and after full installation. I was able to connect an external mouse and a bluetooth mouse and both worked. I checked my xinput list and no sign: ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Wacom HID 50FE Finger touch id=12 [slave pointer (2)] ⎜ ↳ Wacom HID 50FE Pen stylus id=13[slave pointer (2)] ⎜ ↳ Wacom HID 50FE Pen eraser id=16[slave pointer (2)] ⎜ ↳ byron's trackpad id=17[slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)]↳ Virtual core XTEST keyboard id=5[slave keyboard (3)]↳ Power Button id=6[slave keyboard (3)]↳ Video Bus id=7[slave keyboard (3)]↳ Video Bus id=8[slave keyboard (3)]↳ Power Button id=9[slave keyboard (3)]↳ Apple Inc. Magic Keyboard id=10[slave keyboard (3)]↳ EasyCamera id=11[slave keyboard (3)]↳ Ideapad extra buttons id=14[slave keyboard (3)]↳ AT Translated Set 2 keyboard id=15[slave keyboard (3)] ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-24-generic 4.10.0-24.28 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: byron 1794 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Mon Jun 26 16:51:37 2017 InstallationDate: Installed on 2017-06-26 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 80X7 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-24-generic.efi.signed root=UUID=39280165-1a70-4b0d-b1fa-3b01e8bc1e25 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-24-generic N/A linux-backports-modules-4.10.0-24-generic N/A linux-firmware 1.164 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/12/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 4MCN20WW(V1.06) dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo YOGA 720-15IKB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 720-15IKB dmi.modalias: dmi:bvnLENOVO:bvr4MCN20WW(V1.06):bd04/12/2017:svnLENOVO:pn80X7:pvrLenovoYOGA720-15IKB:rvnLENOVO:rnLenovoYOGA720-15IKB:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA720-15IKB: dmi.product.name: 80X7 dmi.product.version: Lenovo YOGA 720-15IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1700657/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1680904] Re: zesty unable to handle kernel NULL pointer dereference
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-hwe (Ubuntu Zesty) 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/1680904 Title: zesty unable to handle kernel NULL pointer dereference Status in linux package in Ubuntu: In Progress Status in linux-hwe package in Ubuntu: Confirmed Status in linux source package in Zesty: In Progress Status in linux-hwe source package in Zesty: Confirmed Bug description: Upgraded to zesty about a week ago. Ran into this on latest kernel. (during high load, nothing in particular seems to cause it to happen). Did not happen with previous (4.10.0.14.16) kernel. Only after update to 4.10.0.15.17, has happened about 3 times since then (or other crashes), this is the one I could capture. kern.log entries below. Let me know if you need anything else from me. Thanks! Apr 7 11:20:28 doe kernel: [26003.796278] BUG: unable to handle kernel NULL pointer dereference at 0018 Apr 7 11:20:28 doe kernel: [26003.796375] IP: gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] Apr 7 11:20:28 doe kernel: [26003.796404] PGD 0 Apr 7 11:20:28 doe kernel: [26003.796405] Apr 7 11:20:28 doe kernel: [26003.796427] Oops: 0002 [#1] SMP Apr 7 11:20:28 doe kernel: [26003.796441] Modules linked in: xt_REDIRECT nf_nat_redirect xt_hl scsi_transport_iscsi binfmt_misc veth ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_filter ip6_tables ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_CHECKSUM xt_comment xt_tcpudp iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack libcrc32c iptable_mangle iptable_filter ccm rfcomm bridge stp llc cmac bnep zfs(PO) zunicode(PO) zavl(PO) zcommon(PO) znvpair(PO) spl(O) nls_iso8859_1 hid_multitouch joydev i2c_designware_platform i2c_designware_core snd_hda_codec_hdmi snd_soc_skl snd_soc_skl_ipc snd_soc_sst_ipc snd_soc_sst_dsp snd_hda_codec_realtek snd_hda_ext_core snd_soc_sst_match snd_hda_codec_generic snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel snd_hda_codec snd_hda_core asus_nb_wmi Apr 7 11:20:28 doe kernel: [26003.796722] snd_hwdep asus_wmi sparse_keymap snd_pcm arc4 snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device iwlmvm snd_timer mac80211 intel_rapl x86_pkg_temp_thermal snd intel_powerclamp uvcvideo coretemp kvm_intel iwlwifi videobuf2_vmalloc kvm videobuf2_memops irqbypass videobuf2_v4l2 intel_cstate videobuf2_core intel_rapl_perf cfg80211 videodev input_leds serio_raw media shpchp soundcore btusb btrtl hci_uart btbcm elan_i2c btqca btintel acpi_als int3403_thermal bluetooth kfifo_buf industrialio mac_hid idma64 mei_me virt_dma intel_pch_thermal acpi_pad int3400_thermal intel_lpss_pci int3402_thermal mei intel_lpss_acpi acpi_thermal_rel processor_thermal_device intel_lpss tpm_crb int340x_thermal_zone int3406_thermal intel_soc_dts_iosf asus_wireless parport_pc ppdev lp parport ip_tables Apr 7 11:20:28 doe kernel: [26003.797026] x_tables autofs4 algif_skcipher af_alg dm_crypt crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc i915 aesni_intel aes_x86_64 crypto_simd glue_helper cryptd i2c_algo_bit drm_kms_helper syscopyarea sysfillrect ahci sysimgblt libahci fb_sys_fops drm wmi i2c_hid hid pinctrl_sunrisepoint video pinctrl_intel fjes Apr 7 11:20:28 doe kernel: [26003.797142] CPU: 0 PID: 8418 Comm: chromium-browse Tainted: P O4.10.0-15-generic #17-Ubuntu Apr 7 11:20:28 doe kernel: [26003.797175] Hardware name: ASUSTeK COMPUTER INC. UX305CA/UX305CA, BIOS UX305CA.201 09/11/2015 Apr 7 11:20:28 doe kernel: [26003.797206] task: 9bbaa201dc00 task.stack: c25b5ea8c000 Apr 7 11:20:28 doe kernel: [26003.797250] RIP: 0010:gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] Apr 7 11:20:28 doe kernel: [26003.797279] RSP: 0018:c25b5ea8f880 EFLAGS: 00010246 Apr 7 11:20:28 doe kernel: [26003.797299] RAX: 9bba689be580 RBX: 0003 RCX: 0003 Apr 7 11:20:28 doe kernel: [26003.797325] RDX: RSI: 9bbae7c0a000 RDI: 9bbba0418000 Apr 7 11:20:28 doe kernel: [26003.797351] RBP: c25b5ea8f8d8 R08: R09: Apr 7 11:20:28 doe kernel: [26003.797378] R10: R11: 0041 R12: 9bbb5f00a000 Apr 7 11:20:28 doe kernel: [26003.797405] R13: 9bbba932bb10 R14: fff97000 R15: 8000 Apr 7 11:20:28 doe kernel: [26003.797440] FS: 7f70bd1df6c0() GS:93c0() knlGS: Apr 7 11:20:28 doe kernel: [26003.797470] CS: 0010 DS: ES: CR0: 80050033 Apr 7 11:20:28 doe kernel: [26003.797497] CR2: 0018 CR3: 00016942 CR4: 003406f0 Apr 7 11:20:28 doe kernel:
[Kernel-packages] [Bug 1680904] Re: zesty unable to handle kernel NULL pointer dereference
@chichun I've tried installing you debs, but my uname keeps reflecting the Jun 30 date. I pull all the debs and install them with `sudo dpkg -i --force-overwrite *.deb`. Is there some other magik incantation to force this? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1680904 Title: zesty unable to handle kernel NULL pointer dereference Status in linux package in Ubuntu: In Progress Status in linux-hwe package in Ubuntu: Confirmed Status in linux source package in Zesty: In Progress Status in linux-hwe source package in Zesty: Confirmed Bug description: Upgraded to zesty about a week ago. Ran into this on latest kernel. (during high load, nothing in particular seems to cause it to happen). Did not happen with previous (4.10.0.14.16) kernel. Only after update to 4.10.0.15.17, has happened about 3 times since then (or other crashes), this is the one I could capture. kern.log entries below. Let me know if you need anything else from me. Thanks! Apr 7 11:20:28 doe kernel: [26003.796278] BUG: unable to handle kernel NULL pointer dereference at 0018 Apr 7 11:20:28 doe kernel: [26003.796375] IP: gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] Apr 7 11:20:28 doe kernel: [26003.796404] PGD 0 Apr 7 11:20:28 doe kernel: [26003.796405] Apr 7 11:20:28 doe kernel: [26003.796427] Oops: 0002 [#1] SMP Apr 7 11:20:28 doe kernel: [26003.796441] Modules linked in: xt_REDIRECT nf_nat_redirect xt_hl scsi_transport_iscsi binfmt_misc veth ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_filter ip6_tables ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_CHECKSUM xt_comment xt_tcpudp iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack libcrc32c iptable_mangle iptable_filter ccm rfcomm bridge stp llc cmac bnep zfs(PO) zunicode(PO) zavl(PO) zcommon(PO) znvpair(PO) spl(O) nls_iso8859_1 hid_multitouch joydev i2c_designware_platform i2c_designware_core snd_hda_codec_hdmi snd_soc_skl snd_soc_skl_ipc snd_soc_sst_ipc snd_soc_sst_dsp snd_hda_codec_realtek snd_hda_ext_core snd_soc_sst_match snd_hda_codec_generic snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel snd_hda_codec snd_hda_core asus_nb_wmi Apr 7 11:20:28 doe kernel: [26003.796722] snd_hwdep asus_wmi sparse_keymap snd_pcm arc4 snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device iwlmvm snd_timer mac80211 intel_rapl x86_pkg_temp_thermal snd intel_powerclamp uvcvideo coretemp kvm_intel iwlwifi videobuf2_vmalloc kvm videobuf2_memops irqbypass videobuf2_v4l2 intel_cstate videobuf2_core intel_rapl_perf cfg80211 videodev input_leds serio_raw media shpchp soundcore btusb btrtl hci_uart btbcm elan_i2c btqca btintel acpi_als int3403_thermal bluetooth kfifo_buf industrialio mac_hid idma64 mei_me virt_dma intel_pch_thermal acpi_pad int3400_thermal intel_lpss_pci int3402_thermal mei intel_lpss_acpi acpi_thermal_rel processor_thermal_device intel_lpss tpm_crb int340x_thermal_zone int3406_thermal intel_soc_dts_iosf asus_wireless parport_pc ppdev lp parport ip_tables Apr 7 11:20:28 doe kernel: [26003.797026] x_tables autofs4 algif_skcipher af_alg dm_crypt crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc i915 aesni_intel aes_x86_64 crypto_simd glue_helper cryptd i2c_algo_bit drm_kms_helper syscopyarea sysfillrect ahci sysimgblt libahci fb_sys_fops drm wmi i2c_hid hid pinctrl_sunrisepoint video pinctrl_intel fjes Apr 7 11:20:28 doe kernel: [26003.797142] CPU: 0 PID: 8418 Comm: chromium-browse Tainted: P O4.10.0-15-generic #17-Ubuntu Apr 7 11:20:28 doe kernel: [26003.797175] Hardware name: ASUSTeK COMPUTER INC. UX305CA/UX305CA, BIOS UX305CA.201 09/11/2015 Apr 7 11:20:28 doe kernel: [26003.797206] task: 9bbaa201dc00 task.stack: c25b5ea8c000 Apr 7 11:20:28 doe kernel: [26003.797250] RIP: 0010:gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] Apr 7 11:20:28 doe kernel: [26003.797279] RSP: 0018:c25b5ea8f880 EFLAGS: 00010246 Apr 7 11:20:28 doe kernel: [26003.797299] RAX: 9bba689be580 RBX: 0003 RCX: 0003 Apr 7 11:20:28 doe kernel: [26003.797325] RDX: RSI: 9bbae7c0a000 RDI: 9bbba0418000 Apr 7 11:20:28 doe kernel: [26003.797351] RBP: c25b5ea8f8d8 R08: R09: Apr 7 11:20:28 doe kernel: [26003.797378] R10: R11: 0041 R12: 9bbb5f00a000 Apr 7 11:20:28 doe kernel: [26003.797405] R13: 9bbba932bb10 R14: fff97000 R15: 8000 Apr 7 11:20:28 doe kernel: [26003.797440] FS: 7f70bd1df6c0() GS:93c0() knlGS: Apr 7 11:20:28 doe kernel: [26003.797470] CS: 0010 DS: ES: CR0: 80050033 Apr 7 11:20:28 doe kernel: [26003.797497] CR2: 0018
[Kernel-packages] [Bug 1706988] 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/1706988 Title: package linux-image-extra-4.4.0-87-generic (not installed) failed to install/upgrade: unable to open '/lib/modules/4.4.0-87-generic/kernel/fs/nls/nls_koi8-r.ko.dpkg-new': Operation not permitted Status in linux package in Ubuntu: Confirmed Bug description: I seem to have issues with kernel updates while using encrypted SSD. version.log Ubuntu 4.4.0-83.106-generic 4.4.70 lspci-vnvn.log 00:00.0 Host bridge [0600]: Intel Corporation Haswell-ULT DRAM Controller [8086:0a04] (rev 0b) Subsystem: Dell Haswell-ULT DRAM Controller [1028:05cb] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: hsw_uncore 00:02.0 VGA compatible controller [0300]: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) DeviceName: Onboard IGD Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05cb] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- [disabled] Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee00018 Data: Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [a4] PCI Advanced Features AFCap: TP+ FLR+ AFCtrl: FLR- AFStatus: TP- Kernel driver in use: i915 Kernel modules: i915 00:03.0 Audio device [0403]: Intel Corporation Haswell-ULT HD Audio Controller [8086:0a0c] (rev 0b) Subsystem: Dell Haswell-ULT HD Audio Controller [1028:05cb] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [40] Express (v2) Root Port (Slot-), MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend- LnkCap: Port #1, Speed 5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s <1us, L1 <4us ClockPM- Surprise- LLActRep+ BwNot+ ASPMOptComp- LnkCtl: ASPM L0s L1 Enabled; RCB 64 bytes Disabled- CommClk- ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x0, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna- CRSVisible- RootCap: CRSVisible- RootSta: PME ReqID , PMEStatus- PMEPending- DevCap2: Completion Timeout: Range ABC, TimeoutDis+, LTR+, OBFF Via WAKE# ARIFwd- DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR+, OBFF Disabled ARIFwd- LnkCtl2: Target Link Speed: 5GT/s, EnterCompliance- SpeedDis- Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS- Compliance De-emphasis: -6dB LnkSta2: Current De-emphasis Level: -3.5dB, EqualizationComplete-, EqualizationPhase1- EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest- Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit- Address: Data: Capabilities: [90] Subsystem: Dell 8 Series PCI Express Root Port 1 [1028:05cb] Capabilities: [a0] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Kernel driver in use: pcieport Kernel modules: shpchp 00:1c.3 PCI bridge [0604]: Intel Corporation 8 Series PCI Express Root Port 4 [8086:9c16] (rev e4) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV-
[Kernel-packages] [Bug 1680904] Re: zesty unable to handle kernel NULL pointer dereference
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-hwe (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/1680904 Title: zesty unable to handle kernel NULL pointer dereference Status in linux package in Ubuntu: In Progress Status in linux-hwe package in Ubuntu: Confirmed Status in linux source package in Zesty: In Progress Status in linux-hwe source package in Zesty: Confirmed Bug description: Upgraded to zesty about a week ago. Ran into this on latest kernel. (during high load, nothing in particular seems to cause it to happen). Did not happen with previous (4.10.0.14.16) kernel. Only after update to 4.10.0.15.17, has happened about 3 times since then (or other crashes), this is the one I could capture. kern.log entries below. Let me know if you need anything else from me. Thanks! Apr 7 11:20:28 doe kernel: [26003.796278] BUG: unable to handle kernel NULL pointer dereference at 0018 Apr 7 11:20:28 doe kernel: [26003.796375] IP: gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] Apr 7 11:20:28 doe kernel: [26003.796404] PGD 0 Apr 7 11:20:28 doe kernel: [26003.796405] Apr 7 11:20:28 doe kernel: [26003.796427] Oops: 0002 [#1] SMP Apr 7 11:20:28 doe kernel: [26003.796441] Modules linked in: xt_REDIRECT nf_nat_redirect xt_hl scsi_transport_iscsi binfmt_misc veth ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_filter ip6_tables ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_CHECKSUM xt_comment xt_tcpudp iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack libcrc32c iptable_mangle iptable_filter ccm rfcomm bridge stp llc cmac bnep zfs(PO) zunicode(PO) zavl(PO) zcommon(PO) znvpair(PO) spl(O) nls_iso8859_1 hid_multitouch joydev i2c_designware_platform i2c_designware_core snd_hda_codec_hdmi snd_soc_skl snd_soc_skl_ipc snd_soc_sst_ipc snd_soc_sst_dsp snd_hda_codec_realtek snd_hda_ext_core snd_soc_sst_match snd_hda_codec_generic snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel snd_hda_codec snd_hda_core asus_nb_wmi Apr 7 11:20:28 doe kernel: [26003.796722] snd_hwdep asus_wmi sparse_keymap snd_pcm arc4 snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device iwlmvm snd_timer mac80211 intel_rapl x86_pkg_temp_thermal snd intel_powerclamp uvcvideo coretemp kvm_intel iwlwifi videobuf2_vmalloc kvm videobuf2_memops irqbypass videobuf2_v4l2 intel_cstate videobuf2_core intel_rapl_perf cfg80211 videodev input_leds serio_raw media shpchp soundcore btusb btrtl hci_uart btbcm elan_i2c btqca btintel acpi_als int3403_thermal bluetooth kfifo_buf industrialio mac_hid idma64 mei_me virt_dma intel_pch_thermal acpi_pad int3400_thermal intel_lpss_pci int3402_thermal mei intel_lpss_acpi acpi_thermal_rel processor_thermal_device intel_lpss tpm_crb int340x_thermal_zone int3406_thermal intel_soc_dts_iosf asus_wireless parport_pc ppdev lp parport ip_tables Apr 7 11:20:28 doe kernel: [26003.797026] x_tables autofs4 algif_skcipher af_alg dm_crypt crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc i915 aesni_intel aes_x86_64 crypto_simd glue_helper cryptd i2c_algo_bit drm_kms_helper syscopyarea sysfillrect ahci sysimgblt libahci fb_sys_fops drm wmi i2c_hid hid pinctrl_sunrisepoint video pinctrl_intel fjes Apr 7 11:20:28 doe kernel: [26003.797142] CPU: 0 PID: 8418 Comm: chromium-browse Tainted: P O4.10.0-15-generic #17-Ubuntu Apr 7 11:20:28 doe kernel: [26003.797175] Hardware name: ASUSTeK COMPUTER INC. UX305CA/UX305CA, BIOS UX305CA.201 09/11/2015 Apr 7 11:20:28 doe kernel: [26003.797206] task: 9bbaa201dc00 task.stack: c25b5ea8c000 Apr 7 11:20:28 doe kernel: [26003.797250] RIP: 0010:gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] Apr 7 11:20:28 doe kernel: [26003.797279] RSP: 0018:c25b5ea8f880 EFLAGS: 00010246 Apr 7 11:20:28 doe kernel: [26003.797299] RAX: 9bba689be580 RBX: 0003 RCX: 0003 Apr 7 11:20:28 doe kernel: [26003.797325] RDX: RSI: 9bbae7c0a000 RDI: 9bbba0418000 Apr 7 11:20:28 doe kernel: [26003.797351] RBP: c25b5ea8f8d8 R08: R09: Apr 7 11:20:28 doe kernel: [26003.797378] R10: R11: 0041 R12: 9bbb5f00a000 Apr 7 11:20:28 doe kernel: [26003.797405] R13: 9bbba932bb10 R14: fff97000 R15: 8000 Apr 7 11:20:28 doe kernel: [26003.797440] FS: 7f70bd1df6c0() GS:93c0() knlGS: Apr 7 11:20:28 doe kernel: [26003.797470] CS: 0010 DS: ES: CR0: 80050033 Apr 7 11:20:28 doe kernel: [26003.797497] CR2: 0018 CR3: 00016942 CR4: 003406f0 Apr 7 11:20:28 doe kernel: [26003.797523]
[Kernel-packages] [Bug 1706531] Re: ath10k doesn't report full RSSI information
** Also affects: linux (Ubuntu Zesty) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) 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/1706531 Title: ath10k doesn't report full RSSI information Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: New Status in linux source package in Zesty: New Bug description: [Impact] ASA (Active Steering Antenna) requires per chain RSSI info. Intel WLAN driver has full support for per-chain RSSI information, but ath10k doesn't. [Fix] The fix is pretty simple just fills up RSSI value to the structure. [Test Case] RSSI information can be polled from userspace using NL80211 wireless stack. [Regression Potential] No any regression concern. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1706531/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1706132] Re: xfs slab objects (memory) leak when xfs shutdown is called
** Also affects: linux (Ubuntu Xenial) 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/1706132 Title: xfs slab objects (memory) leak when xfs shutdown is called Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: New Bug description: [Impact] * xfs kernel memory leak in case of xfs shutdown due to i/o errors * if xfs on iscsi, iscsi disconnection and module unload will case mem leak [Test Case] * configure tgtd with 1 lun and make it available through tcp/ip * configure open-iscsi to map this lun * make sure node.session.timeo.replacement_timeout = 0 in iscsid.conf * mount a xfs volume using the lun from tgtd host, run bonnie -d /xfsdir * in tgtd server, drop iscsi packets and watch client to have i/o errors * after sometime (depending on timeout) xfs will call shutdown * make sure the i/o errors led to xfs shutdown (comment #3) * after shutdown you try to remove xfs module and it will leak [Regression Potential] * based on upstream fix * tested in the same environment * potential damage to xfs [Other Info] Original Description: This scenario is testing [iscsi <-> scsi <-> disk <-> xfs] [ 551.125604] sd 2:0:0:1: rejecting I/O to offline device [ 551.125615] sd 2:0:0:1: rejecting I/O to offline device [ 551.125627] sd 2:0:0:1: rejecting I/O to offline device [ 551.125639] sd 2:0:0:1: rejecting I/O to offline device [ 551.135216] XFS (sda1): metadata I/O error: block 0xeffe01 ("xfs_trans_read_buf_map") error 5 numblks 1 [ 551.135274] XFS (sda1): page discard on page ea0002a89cc0, inode 0x83, offset 6442385408. # when XFS shuts down because of an error (or offline disk, example): [ 551.850498] XFS (sda1): xfs_do_force_shutdown(0x2) called from line 1197 of file /build/linux-lts-xenial-roXrYH/linux-lts-xenial-4.4.0/fs/xfs/xfs_log.c. Return address = 0xc0300388 [ 551.850568] XFS (sda1): Log I/O Error Detected. Shutting down filesystem [ 551.850618] XFS (sda1): xfs_log_force: error -5 returned. [ 551.850630] XFS (sda1): Failing async write on buffer block 0x77ff08. Retrying async write. [ 551.850634] XFS (sda1): Failing async write on buffer block 0x77ff10. Retrying async write. [ 551.850638] XFS (sda1): Failing async write on buffer block 0x77ff01. Retrying async write. [ 551.853171] XFS (sda1): Please umount the filesystem and rectify the problem(s) [ 551.874131] XFS (sda1): metadata I/O error: block 0x1dffc49 ("xlog_iodone") error 5 numblks 64 [ 551.877993] XFS (sda1): xfs_do_force_shutdown(0x2) called from line 1197 of file /build/linux-lts-xenial-roXrYH/linux-lts-xenial-4.4.0/fs/xfs/xfs_log.c. Return address = 0xc0300388 [ 551.899036] XFS (sda1): xfs_log_force: error -5 returned. [ 569.323074] XFS (sda1): xfs_log_force: error -5 returned. [ 599.403085] XFS (sda1): xfs_log_force: error -5 returned. [ 629.483111] XFS (sda1): xfs_log_force: error -5 returned. [ 659.563115] XFS (sda1): xfs_log_force: error -5 returned. [ 689.643014] XFS (sda1): xfs_log_force: error -5 returned. # when I execute: # sudo umount /dev/sda1: [81634.923043] XFS (sda1): xfs_log_force: error -5 returned. [81640.739097] XFS (sda1): xfs_log_force: error -5 returned. [81640.739137] XFS (sda1): Unmounting Filesystem [81640.739463] XFS (sda1): xfs_log_force: error -5 returned. [81640.739508] XFS (sda1): xfs_log_force: error -5 returned. [81640.742741] sd 2:0:0:1: rejecting I/O to offline device [81640.745576] blk_update_request: 25 callbacks suppressed [81640.745601] blk_update_request: I/O error, dev sda, sector 0 # i was able to umount and then to remove iscsi disk. # but if i try to unload the xfs module: inaddy@(trustyiscsicli):~$ sudo rmmod xfs [82211.059301] = [82211.063764] BUG xfs_log_ticket (Tainted: G OE ): Objects remaining in xfs_log_ticket on kmem_cache_close() [82211.067450] - [82211.067450] [82211.070580] INFO: Slab 0xea0002eb7640 objects=22 used=1 fp=0x8800badd9f18 flags=0xc00080 [82211.074430] INFO: Object 0x8800badd9228 @offset=552 [82211.076133] kmem_cache_destroy xfs_log_ticket: Slab cache still has objects AND [82211.059301] = [82211.063764] BUG xfs_log_ticket (Tainted: G OE ): Objects remaining in xfs_log_ticket on kmem_cache_close() [82211.067450] - [82211.067450] [82211.070570] Disabling lock debugging due to kernel taint [82211.070580] INFO:
[Kernel-packages] [Bug 1680904] Re: zesty unable to handle kernel NULL pointer dereference
I've been experimenting with 4.12.3-041203-generic, not crashes but sometimes the screen goes blank for 3 seconds, from syslog Jul 27 14:50:45 XPS13 org.gnome.Shell.desktop[1986]: intel_do_flush_locked failed: Cannot allocate memory it recovers nicely, no apps gets killed and nothing gets restarted ( other than gnome desktop ??? ) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1680904 Title: zesty unable to handle kernel NULL pointer dereference Status in linux package in Ubuntu: In Progress Status in linux-hwe package in Ubuntu: New Status in linux source package in Zesty: In Progress Status in linux-hwe source package in Zesty: New Bug description: Upgraded to zesty about a week ago. Ran into this on latest kernel. (during high load, nothing in particular seems to cause it to happen). Did not happen with previous (4.10.0.14.16) kernel. Only after update to 4.10.0.15.17, has happened about 3 times since then (or other crashes), this is the one I could capture. kern.log entries below. Let me know if you need anything else from me. Thanks! Apr 7 11:20:28 doe kernel: [26003.796278] BUG: unable to handle kernel NULL pointer dereference at 0018 Apr 7 11:20:28 doe kernel: [26003.796375] IP: gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] Apr 7 11:20:28 doe kernel: [26003.796404] PGD 0 Apr 7 11:20:28 doe kernel: [26003.796405] Apr 7 11:20:28 doe kernel: [26003.796427] Oops: 0002 [#1] SMP Apr 7 11:20:28 doe kernel: [26003.796441] Modules linked in: xt_REDIRECT nf_nat_redirect xt_hl scsi_transport_iscsi binfmt_misc veth ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_filter ip6_tables ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_CHECKSUM xt_comment xt_tcpudp iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack libcrc32c iptable_mangle iptable_filter ccm rfcomm bridge stp llc cmac bnep zfs(PO) zunicode(PO) zavl(PO) zcommon(PO) znvpair(PO) spl(O) nls_iso8859_1 hid_multitouch joydev i2c_designware_platform i2c_designware_core snd_hda_codec_hdmi snd_soc_skl snd_soc_skl_ipc snd_soc_sst_ipc snd_soc_sst_dsp snd_hda_codec_realtek snd_hda_ext_core snd_soc_sst_match snd_hda_codec_generic snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel snd_hda_codec snd_hda_core asus_nb_wmi Apr 7 11:20:28 doe kernel: [26003.796722] snd_hwdep asus_wmi sparse_keymap snd_pcm arc4 snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device iwlmvm snd_timer mac80211 intel_rapl x86_pkg_temp_thermal snd intel_powerclamp uvcvideo coretemp kvm_intel iwlwifi videobuf2_vmalloc kvm videobuf2_memops irqbypass videobuf2_v4l2 intel_cstate videobuf2_core intel_rapl_perf cfg80211 videodev input_leds serio_raw media shpchp soundcore btusb btrtl hci_uart btbcm elan_i2c btqca btintel acpi_als int3403_thermal bluetooth kfifo_buf industrialio mac_hid idma64 mei_me virt_dma intel_pch_thermal acpi_pad int3400_thermal intel_lpss_pci int3402_thermal mei intel_lpss_acpi acpi_thermal_rel processor_thermal_device intel_lpss tpm_crb int340x_thermal_zone int3406_thermal intel_soc_dts_iosf asus_wireless parport_pc ppdev lp parport ip_tables Apr 7 11:20:28 doe kernel: [26003.797026] x_tables autofs4 algif_skcipher af_alg dm_crypt crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc i915 aesni_intel aes_x86_64 crypto_simd glue_helper cryptd i2c_algo_bit drm_kms_helper syscopyarea sysfillrect ahci sysimgblt libahci fb_sys_fops drm wmi i2c_hid hid pinctrl_sunrisepoint video pinctrl_intel fjes Apr 7 11:20:28 doe kernel: [26003.797142] CPU: 0 PID: 8418 Comm: chromium-browse Tainted: P O4.10.0-15-generic #17-Ubuntu Apr 7 11:20:28 doe kernel: [26003.797175] Hardware name: ASUSTeK COMPUTER INC. UX305CA/UX305CA, BIOS UX305CA.201 09/11/2015 Apr 7 11:20:28 doe kernel: [26003.797206] task: 9bbaa201dc00 task.stack: c25b5ea8c000 Apr 7 11:20:28 doe kernel: [26003.797250] RIP: 0010:gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] Apr 7 11:20:28 doe kernel: [26003.797279] RSP: 0018:c25b5ea8f880 EFLAGS: 00010246 Apr 7 11:20:28 doe kernel: [26003.797299] RAX: 9bba689be580 RBX: 0003 RCX: 0003 Apr 7 11:20:28 doe kernel: [26003.797325] RDX: RSI: 9bbae7c0a000 RDI: 9bbba0418000 Apr 7 11:20:28 doe kernel: [26003.797351] RBP: c25b5ea8f8d8 R08: R09: Apr 7 11:20:28 doe kernel: [26003.797378] R10: R11: 0041 R12: 9bbb5f00a000 Apr 7 11:20:28 doe kernel: [26003.797405] R13: 9bbba932bb10 R14: fff97000 R15: 8000 Apr 7 11:20:28 doe kernel: [26003.797440] FS: 7f70bd1df6c0() GS:93c0() knlGS: Apr 7 11:20:28 doe kernel: [26003.797470] CS: 0010 DS:
[Kernel-packages] [Bug 1705275] Re: linux-aws: 4.4.0-1027.36 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1705275 Title: linux-aws: 4.4.0-1027.36 -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 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: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: 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: 1705270 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/1705275/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1706977] 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 1706977 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/1706977 Title: Issues with Nvidia GeForce GT 240M. Can't define monitor and set proper resolution. Also, Redshift doesn't work. Status in linux package in Ubuntu: Incomplete Bug description: Kernel: 4.4.0-87. Nvidia screen (after boot) has disappeared. System: Linux Mint 18.1 MATE Laptop: Fujitsu Amilo Pi 3560 I'm using 4.4.0-72 kernel for now with no such issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1706977/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1680904] Re: zesty unable to handle kernel NULL pointer dereference
@chihchun Out of interest: could you give the procedure how you build this (I've seen various recipes online)? On my system, your debs are considered a lower version to the repositories that have 4.10.0-28 as well and will offer to "upgrade" it to the official ones every apt upgrade cycle. So I guess a version bump would be the easiest way to fix this. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1680904 Title: zesty unable to handle kernel NULL pointer dereference Status in linux package in Ubuntu: In Progress Status in linux-hwe package in Ubuntu: New Status in linux source package in Zesty: In Progress Status in linux-hwe source package in Zesty: New Bug description: Upgraded to zesty about a week ago. Ran into this on latest kernel. (during high load, nothing in particular seems to cause it to happen). Did not happen with previous (4.10.0.14.16) kernel. Only after update to 4.10.0.15.17, has happened about 3 times since then (or other crashes), this is the one I could capture. kern.log entries below. Let me know if you need anything else from me. Thanks! Apr 7 11:20:28 doe kernel: [26003.796278] BUG: unable to handle kernel NULL pointer dereference at 0018 Apr 7 11:20:28 doe kernel: [26003.796375] IP: gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] Apr 7 11:20:28 doe kernel: [26003.796404] PGD 0 Apr 7 11:20:28 doe kernel: [26003.796405] Apr 7 11:20:28 doe kernel: [26003.796427] Oops: 0002 [#1] SMP Apr 7 11:20:28 doe kernel: [26003.796441] Modules linked in: xt_REDIRECT nf_nat_redirect xt_hl scsi_transport_iscsi binfmt_misc veth ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_filter ip6_tables ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_CHECKSUM xt_comment xt_tcpudp iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack libcrc32c iptable_mangle iptable_filter ccm rfcomm bridge stp llc cmac bnep zfs(PO) zunicode(PO) zavl(PO) zcommon(PO) znvpair(PO) spl(O) nls_iso8859_1 hid_multitouch joydev i2c_designware_platform i2c_designware_core snd_hda_codec_hdmi snd_soc_skl snd_soc_skl_ipc snd_soc_sst_ipc snd_soc_sst_dsp snd_hda_codec_realtek snd_hda_ext_core snd_soc_sst_match snd_hda_codec_generic snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel snd_hda_codec snd_hda_core asus_nb_wmi Apr 7 11:20:28 doe kernel: [26003.796722] snd_hwdep asus_wmi sparse_keymap snd_pcm arc4 snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device iwlmvm snd_timer mac80211 intel_rapl x86_pkg_temp_thermal snd intel_powerclamp uvcvideo coretemp kvm_intel iwlwifi videobuf2_vmalloc kvm videobuf2_memops irqbypass videobuf2_v4l2 intel_cstate videobuf2_core intel_rapl_perf cfg80211 videodev input_leds serio_raw media shpchp soundcore btusb btrtl hci_uart btbcm elan_i2c btqca btintel acpi_als int3403_thermal bluetooth kfifo_buf industrialio mac_hid idma64 mei_me virt_dma intel_pch_thermal acpi_pad int3400_thermal intel_lpss_pci int3402_thermal mei intel_lpss_acpi acpi_thermal_rel processor_thermal_device intel_lpss tpm_crb int340x_thermal_zone int3406_thermal intel_soc_dts_iosf asus_wireless parport_pc ppdev lp parport ip_tables Apr 7 11:20:28 doe kernel: [26003.797026] x_tables autofs4 algif_skcipher af_alg dm_crypt crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc i915 aesni_intel aes_x86_64 crypto_simd glue_helper cryptd i2c_algo_bit drm_kms_helper syscopyarea sysfillrect ahci sysimgblt libahci fb_sys_fops drm wmi i2c_hid hid pinctrl_sunrisepoint video pinctrl_intel fjes Apr 7 11:20:28 doe kernel: [26003.797142] CPU: 0 PID: 8418 Comm: chromium-browse Tainted: P O4.10.0-15-generic #17-Ubuntu Apr 7 11:20:28 doe kernel: [26003.797175] Hardware name: ASUSTeK COMPUTER INC. UX305CA/UX305CA, BIOS UX305CA.201 09/11/2015 Apr 7 11:20:28 doe kernel: [26003.797206] task: 9bbaa201dc00 task.stack: c25b5ea8c000 Apr 7 11:20:28 doe kernel: [26003.797250] RIP: 0010:gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] Apr 7 11:20:28 doe kernel: [26003.797279] RSP: 0018:c25b5ea8f880 EFLAGS: 00010246 Apr 7 11:20:28 doe kernel: [26003.797299] RAX: 9bba689be580 RBX: 0003 RCX: 0003 Apr 7 11:20:28 doe kernel: [26003.797325] RDX: RSI: 9bbae7c0a000 RDI: 9bbba0418000 Apr 7 11:20:28 doe kernel: [26003.797351] RBP: c25b5ea8f8d8 R08: R09: Apr 7 11:20:28 doe kernel: [26003.797378] R10: R11: 0041 R12: 9bbb5f00a000 Apr 7 11:20:28 doe kernel: [26003.797405] R13: 9bbba932bb10 R14: fff97000 R15: 8000 Apr 7 11:20:28 doe kernel: [26003.797440] FS: 7f70bd1df6c0() GS:93c0() knlGS: Apr 7 11:20:28 doe kernel:
[Kernel-packages] [Bug 1706991] [NEW] ubuntu/rsi driver downlink wifi throughput drops to 5-6 Mbps when BT keyboard is connected
Public bug reported: In STA+BT+BLE mode, we get expected wifi throughput numbers when BT device is not connected. It drops to 5-6 Mbps from 30+Mbps as soon as BT keyboard is connected. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Summary changed: - Downlink wifi throughput drops to 5-6 Mbps when BT keyboard is connected + ubuntu/rsi driver downlink wifi throughput drops to 5-6 Mbps when BT keyboard is connected -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1706991 Title: ubuntu/rsi driver downlink wifi throughput drops to 5-6 Mbps when BT keyboard is connected Status in linux package in Ubuntu: Incomplete Bug description: In STA+BT+BLE mode, we get expected wifi throughput numbers when BT device is not connected. It drops to 5-6 Mbps from 30+Mbps as soon as BT keyboard is connected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1706991/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1706991] 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 1706991 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/1706991 Title: ubuntu/rsi driver downlink wifi throughput drops to 5-6 Mbps when BT keyboard is connected Status in linux package in Ubuntu: Incomplete Bug description: In STA+BT+BLE mode, we get expected wifi throughput numbers when BT device is not connected. It drops to 5-6 Mbps from 30+Mbps as soon as BT keyboard is connected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1706991/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1705495] Re: Adt tests of src:linux time out often on armhf lxc containers
** Also affects: linux (Ubuntu Zesty) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Trusty) 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/1705495 Title: Adt tests of src:linux time out often on armhf lxc containers Status in linux package in Ubuntu: Triaged Status in linux source package in Trusty: New Status in linux source package in Xenial: New Status in linux source package in Zesty: New Bug description: http://autopkgtest.ubuntu.com/packages/linux/artful/armhf quite often the tests time out on armhf. Maybe this is due to running inside a lxc container, rather than in a full VM. Could you please consider disabling rebuild test on armhf? Or for example lowering its parallelism during adt tests. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705495/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1706988] Re: package linux-image-extra-4.4.0-87-generic (not installed) failed to install/upgrade: unable to open '/lib/modules/4.4.0-87-generic/kernel/fs/nls/nls_koi8-r.ko.dpkg
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1706988 Title: package linux-image-extra-4.4.0-87-generic (not installed) failed to install/upgrade: unable to open '/lib/modules/4.4.0-87-generic/kernel/fs/nls/nls_koi8-r.ko.dpkg-new': Operation not permitted Status in linux package in Ubuntu: Confirmed Bug description: I seem to have issues with kernel updates while using encrypted SSD. version.log Ubuntu 4.4.0-83.106-generic 4.4.70 lspci-vnvn.log 00:00.0 Host bridge [0600]: Intel Corporation Haswell-ULT DRAM Controller [8086:0a04] (rev 0b) Subsystem: Dell Haswell-ULT DRAM Controller [1028:05cb] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: hsw_uncore 00:02.0 VGA compatible controller [0300]: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) DeviceName: Onboard IGD Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05cb] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- [disabled] Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee00018 Data: Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [a4] PCI Advanced Features AFCap: TP+ FLR+ AFCtrl: FLR- AFStatus: TP- Kernel driver in use: i915 Kernel modules: i915 00:03.0 Audio device [0403]: Intel Corporation Haswell-ULT HD Audio Controller [8086:0a0c] (rev 0b) Subsystem: Dell Haswell-ULT HD Audio Controller [1028:05cb] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [40] Express (v2) Root Port (Slot-), MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend- LnkCap: Port #1, Speed 5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s <1us, L1 <4us ClockPM- Surprise- LLActRep+ BwNot+ ASPMOptComp- LnkCtl: ASPM L0s L1 Enabled; RCB 64 bytes Disabled- CommClk- ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x0, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna- CRSVisible- RootCap: CRSVisible- RootSta: PME ReqID , PMEStatus- PMEPending- DevCap2: Completion Timeout: Range ABC, TimeoutDis+, LTR+, OBFF Via WAKE# ARIFwd- DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR+, OBFF Disabled ARIFwd- LnkCtl2: Target Link Speed: 5GT/s, EnterCompliance- SpeedDis- Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS- Compliance De-emphasis: -6dB LnkSta2: Current De-emphasis Level: -3.5dB, EqualizationComplete-, EqualizationPhase1- EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest- Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit- Address: Data: Capabilities: [90] Subsystem: Dell 8 Series PCI Express Root Port 1 [1028:05cb] Capabilities: [a0] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Kernel driver in use: pcieport Kernel modules: shpchp 00:1c.3 PCI bridge [0604]: Intel Corporation 8 Series PCI Express Root Port 4 [8086:9c16] (rev e4) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
[Kernel-packages] [Bug 1706988] Re: package linux-image-extra-4.4.0-87-generic (not installed) failed to install/upgrade: unable to open '/lib/modules/4.4.0-87-generic/kernel/fs/nls/nls_koi8-r.ko.dpkg
** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1706988 Title: package linux-image-extra-4.4.0-87-generic (not installed) failed to install/upgrade: unable to open '/lib/modules/4.4.0-87-generic/kernel/fs/nls/nls_koi8-r.ko.dpkg-new': Operation not permitted Status in linux package in Ubuntu: Confirmed Bug description: I seem to have issues with kernel updates while using encrypted SSD. version.log Ubuntu 4.4.0-83.106-generic 4.4.70 lspci-vnvn.log 00:00.0 Host bridge [0600]: Intel Corporation Haswell-ULT DRAM Controller [8086:0a04] (rev 0b) Subsystem: Dell Haswell-ULT DRAM Controller [1028:05cb] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: hsw_uncore 00:02.0 VGA compatible controller [0300]: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) DeviceName: Onboard IGD Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05cb] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- [disabled] Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee00018 Data: Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [a4] PCI Advanced Features AFCap: TP+ FLR+ AFCtrl: FLR- AFStatus: TP- Kernel driver in use: i915 Kernel modules: i915 00:03.0 Audio device [0403]: Intel Corporation Haswell-ULT HD Audio Controller [8086:0a0c] (rev 0b) Subsystem: Dell Haswell-ULT HD Audio Controller [1028:05cb] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [40] Express (v2) Root Port (Slot-), MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend- LnkCap: Port #1, Speed 5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s <1us, L1 <4us ClockPM- Surprise- LLActRep+ BwNot+ ASPMOptComp- LnkCtl: ASPM L0s L1 Enabled; RCB 64 bytes Disabled- CommClk- ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x0, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna- CRSVisible- RootCap: CRSVisible- RootSta: PME ReqID , PMEStatus- PMEPending- DevCap2: Completion Timeout: Range ABC, TimeoutDis+, LTR+, OBFF Via WAKE# ARIFwd- DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR+, OBFF Disabled ARIFwd- LnkCtl2: Target Link Speed: 5GT/s, EnterCompliance- SpeedDis- Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS- Compliance De-emphasis: -6dB LnkSta2: Current De-emphasis Level: -3.5dB, EqualizationComplete-, EqualizationPhase1- EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest- Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit- Address: Data: Capabilities: [90] Subsystem: Dell 8 Series PCI Express Root Port 1 [1028:05cb] Capabilities: [a0] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Kernel driver in use: pcieport Kernel modules: shpchp 00:1c.3 PCI bridge [0604]: Intel Corporation 8 Series PCI Express Root Port 4 [8086:9c16] (rev e4) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR-
[Kernel-packages] [Bug 1706833] Re: atheros bt failed after S3
** Also affects: linux (Ubuntu Xenial) 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/1706833 Title: atheros bt failed after S3 Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: New Bug description: [Impact] BT fails to load firmware after S3. On my system it's atheros' chip, but the same issue can be seen with broadcom's chip, too. [542.6274] WARNING: CPU: 0 PID: 20729 at /build/linux-MD8jsN/linux-4.4.0/drivers/base/firmware_class.c:1148 _request_firmware+0x7c2/0xaf0() The root cause of this issue is request_firmware() is being called at the wrong time. [Fix] The fix is from this old thread[1], but the patch didn't be accepted by the maintainer. It prevents the work queue from being re-created and calls request_firmware() immediately before usermodehelper is fully resumed. Making the workqueue freezable preserves the delay and will postpone the firmware loading time. [Test Case] Verified on the machine has this issue, and confirm this patch works. [Regression Potential] From what I can see, I think this change should be safe, and after 240 times S3 test, the system and BT functions are still working. 1. http://lists.openwall.net/netdev/2015/05/06/3 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1706833/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1700657] Re: Touchpad not detected in Lenovo X1 Yoga / Yoga 720-15IKB
I just checked my dmesg: If ACPI is the problem, shouldn't dmesg show some "elan0651" device (although it does not bind any driver to it)? So, if I cannot find any "elan" string in my dmesg, this should mean that the kernel does not find ANY i2c device with a similar hardware name, shouldn't it? => ACPI might not be the problem, rather the hardware identification of the linux kernel..? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1700657 Title: Touchpad not detected in Lenovo X1 Yoga / Yoga 720-15IKB Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: Touchpad is not automatically detected in 14.04, 16.04 or 17.04. I tried in live mode and after full installation. I was able to connect an external mouse and a bluetooth mouse and both worked. I checked my xinput list and no sign: ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Wacom HID 50FE Finger touch id=12 [slave pointer (2)] ⎜ ↳ Wacom HID 50FE Pen stylus id=13[slave pointer (2)] ⎜ ↳ Wacom HID 50FE Pen eraser id=16[slave pointer (2)] ⎜ ↳ byron's trackpad id=17[slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)]↳ Virtual core XTEST keyboard id=5[slave keyboard (3)]↳ Power Button id=6[slave keyboard (3)]↳ Video Bus id=7[slave keyboard (3)]↳ Video Bus id=8[slave keyboard (3)]↳ Power Button id=9[slave keyboard (3)]↳ Apple Inc. Magic Keyboard id=10[slave keyboard (3)]↳ EasyCamera id=11[slave keyboard (3)]↳ Ideapad extra buttons id=14[slave keyboard (3)]↳ AT Translated Set 2 keyboard id=15[slave keyboard (3)] ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-24-generic 4.10.0-24.28 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: byron 1794 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Mon Jun 26 16:51:37 2017 InstallationDate: Installed on 2017-06-26 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 80X7 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-24-generic.efi.signed root=UUID=39280165-1a70-4b0d-b1fa-3b01e8bc1e25 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-24-generic N/A linux-backports-modules-4.10.0-24-generic N/A linux-firmware 1.164 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/12/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 4MCN20WW(V1.06) dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo YOGA 720-15IKB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 720-15IKB dmi.modalias: dmi:bvnLENOVO:bvr4MCN20WW(V1.06):bd04/12/2017:svnLENOVO:pn80X7:pvrLenovoYOGA720-15IKB:rvnLENOVO:rnLenovoYOGA720-15IKB:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA720-15IKB: dmi.product.name: 80X7 dmi.product.version: Lenovo YOGA 720-15IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1700657/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1706247] [NEW] Possible to turn on 16g huge pages on Ubuntu 16.04.2 PowerNV
You have been subscribed to a public bug: 16G Huge Pages are not supported on PowerNV (bare metal) installations. Ubuntu 16.04.2 still allows 16G huge pages to be turned on. Contact Information = Mike Hollinger (mchol...@us.ibm.com) ---uname output--- Linux aprilmin4 4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:53:54 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux Machine Type = 8335-GTB ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. Add the following to the kernel boot args (either via editing the petitboot boot option manually, or updating /boot/grub/grub.cfg: default_hugepagesz=16G hugepagesz=16G hugepages=4 2. Boot Linux 3. Observe that the kernel believes 16G huge pages are available: ubuntu@aprilmin7:~$ cat /proc/meminfo | grep -i huge AnonHugePages:475136 kB HugePages_Total: 0 HugePages_Free:0 HugePages_Rsvd:0 HugePages_Surp:0 Hugepagesize: 16777216 kB ubuntu@aprilmin7:~$ ls /sys/devices/system/node/node0/hugepages hugepages-1024kB hugepages-16384kB hugepages-16777216kB Stack trace output: no Oops output: no System Dump Info: The system is not configured to capture a system dump. *Additional Instructions for Mike Hollinger (mchol...@us.ibm.com): -Post a private note with access information to the machine that the bug is occuring on. -Attach sysctl -a output output to the bug. This may be recreated on any bare metal POWER8 server with Ubuntu 16.04.2; I haven't checked other versions of Ubuntu. ** Affects: ubuntu-power-systems Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) Status: New ** Tags: architecture-ppc64le bugnameltc-156931 severity-medium targetmilestone-inin--- -- Possible to turn on 16g huge pages on Ubuntu 16.04.2 PowerNV https://bugs.launchpad.net/bugs/1706247 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 1706833] Re: atheros bt failed after S3
** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1706833 Title: atheros bt failed after S3 Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: New Bug description: [Impact] BT fails to load firmware after S3. On my system it's atheros' chip, but the same issue can be seen with broadcom's chip, too. [542.6274] WARNING: CPU: 0 PID: 20729 at /build/linux-MD8jsN/linux-4.4.0/drivers/base/firmware_class.c:1148 _request_firmware+0x7c2/0xaf0() The root cause of this issue is request_firmware() is being called at the wrong time. [Fix] The fix is from this old thread[1], but the patch didn't be accepted by the maintainer. It prevents the work queue from being re-created and calls request_firmware() immediately before usermodehelper is fully resumed. Making the workqueue freezable preserves the delay and will postpone the firmware loading time. [Test Case] Verified on the machine has this issue, and confirm this patch works. [Regression Potential] From what I can see, I think this change should be safe, and after 240 times S3 test, the system and BT functions are still working. 1. http://lists.openwall.net/netdev/2015/05/06/3 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1706833/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1706275] Re: Kernel Panic from intel_dp_set_idle_link_train
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.13 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13-rc2 ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Tags added: kernel-da-key -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1706275 Title: Kernel Panic from intel_dp_set_idle_link_train Status in linux package in Ubuntu: Incomplete Bug description: When putting my laptop on a docking station the system did not detect the external monitor attached via DP. I took the laptop of the station and put it back on. Still nothing happend so I decided to reboot the system. I opened a browser when the system froze. The mouse was still moving but X was dead in all other regards. To see whether something was alive I tried to switch to the console via Ctr-Alt-F1. Nothing happend for about 5 to 10 seconds and then the kernel panic came up. I took a quick photo of the screen which I attached. My system is running Ubuntu 17.04. I'm using an upstream kernel: Linux 4.11.11-04-generic #201707150838 SMP x86_64 x86_64 x86_64 GNU/Linux My Laptop is a ThinkPad T460s and I'm using the graphics drivers from intel. If you need any more information please do not hesitate to contact me! --- ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CurrentDesktop: Unity:Unity7 DistroRelease: Ubuntu 17.04 EcryptfsInUse: Yes InstallationDate: Installed on 2016-08-01 (358 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Package: linux (not installed) Tags: zesty Uname: Linux 4.11.12-041112-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to zesty on 2017-04-26 (90 days ago) UserGroups: adm cdrom dip docker kvm lp lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1706275/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1706402] Re: fullscreen does not work correctly
** Changed in: linux (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1706402 Title: fullscreen does not work correctly Status in linux package in Ubuntu: Incomplete Bug description: in fullscreen mode, after moving the mouse, the window is maximized instead ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: cheese 3.18.1-2ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73 Uname: Linux 4.4.0-87-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jul 25 18:31:22 2017 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 EcryptfsInUse: Yes InstallationDate: Installed on 2014-08-29 (1061 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20130203-13:50 MachineType: Dell Inc. XPS13 9333 RelatedPackageVersions: cheese3.18.1-2ubuntu3 cheese-common 3.18.1-2ubuntu3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/19/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0D13CR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA04:bd03/19/2014:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0D13CR:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS13 9333 dmi.sys.vendor: Dell Inc. --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: benedikt 2691 F pulseaudio /dev/snd/controlC0: benedikt 2691 F pulseaudio CurrentDesktop: Unity DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 DistroRelease: Ubuntu 16.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=df019d1b-7a79-4508-bdfc-2c1166a87d38 InstallationDate: Installed on 2014-08-29 (1061 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20130203-13:50 MachineType: Dell Inc. XPS13 9333 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-87-generic root=UUID=0ded76d6-3843-4156-855c-8ae7a04cadc1 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73 RelatedPackageVersions: linux-restricted-modules-4.4.0-87-generic N/A linux-backports-modules-4.4.0-87-generic N/A linux-firmware1.157.11 Tags: xenial Uname: Linux 4.4.0-87-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip libvirtd lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 03/19/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0D13CR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA04:bd03/19/2014:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0D13CR:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS13 9333 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1706402/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1706977] Re: Issues with Nvidia GeForce GT 240M. Can't define monitor and set proper resolution. Also, Redshift doesn't work.
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.13 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13-rc2 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1706977 Title: Issues with Nvidia GeForce GT 240M. Can't define monitor and set proper resolution. Also, Redshift doesn't work. Status in linux package in Ubuntu: Incomplete Bug description: Kernel: 4.4.0-87. Nvidia screen (after boot) has disappeared. System: Linux Mint 18.1 MATE Laptop: Fujitsu Amilo Pi 3560 I'm using 4.4.0-72 kernel for now with no such issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1706977/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1699845] Re: System not booting after kernel upgrade to 4.10.0-22, problem persists with 4.10.0-23
Does the system boot if you select the prior kernel version from the GRUB menu? ** Changed in: linux (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1699845 Title: System not booting after kernel upgrade to 4.10.0-22, problem persists with 4.10.0-23 Status in linux package in Ubuntu: Incomplete Bug description: I am on Ubuntu Studio Zesty (17.04). Since upgrade to Linux 4.10.0-22 system boot freezes, only way out is hard shutdown. I am currently booting from 4.10.0-21. I can provide journalctl -b1 (where previous boot is with faulty kernel) on request. Thank you ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: ubuntu-release-upgrader-core 1:17.04.8 ProcVersionSignature: Ubuntu 4.10.0-21.23-lowlatency 4.10.11 Uname: Linux 4.10.0-21-lowlatency x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: XFCE Date: Thu Jun 22 17:46:53 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-03-21 (92 days ago) InstallationMedia: Ubuntu-Studio 16.10 "Yakkety Yak" - Release amd64 (20161012.1) PackageArchitecture: all ProcEnviron: LANGUAGE=it_IT PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeAptlog: Log time: 2017-06-06 21:25:15.195734 Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1699845/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1699845] Re: System not booting after kernel upgrade to 4.10.0-22, problem persists with 4.10.0-23
Would it be possible for you to test the latest upstream stable kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.10 stable kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10.17/ ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Tags added: kernel-da-key -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1699845 Title: System not booting after kernel upgrade to 4.10.0-22, problem persists with 4.10.0-23 Status in linux package in Ubuntu: Incomplete Bug description: I am on Ubuntu Studio Zesty (17.04). Since upgrade to Linux 4.10.0-22 system boot freezes, only way out is hard shutdown. I am currently booting from 4.10.0-21. I can provide journalctl -b1 (where previous boot is with faulty kernel) on request. Thank you ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: ubuntu-release-upgrader-core 1:17.04.8 ProcVersionSignature: Ubuntu 4.10.0-21.23-lowlatency 4.10.11 Uname: Linux 4.10.0-21-lowlatency x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: XFCE Date: Thu Jun 22 17:46:53 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-03-21 (92 days ago) InstallationMedia: Ubuntu-Studio 16.10 "Yakkety Yak" - Release amd64 (20161012.1) PackageArchitecture: all ProcEnviron: LANGUAGE=it_IT PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeAptlog: Log time: 2017-06-06 21:25:15.195734 Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1699845/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1706141] Re: [ARM64] config EDAC_GHES=y depends on EDAC_MM_EDAC=y
** Also affects: linux (Ubuntu Zesty) 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/1706141 Title: [ARM64] config EDAC_GHES=y depends on EDAC_MM_EDAC=y Status in linux package in Ubuntu: Incomplete Status in linux source package in Zesty: New Bug description: [Impact] In configs Zesty and Artful, EDAC_MM_EDAC is set to =m, this disables EDAC_GHES. Customers using RAS on ARM64 may want this functionality. According to RAS expert at QTI. EDAC_GHES is essential for ARMv8.0 Server systems, as it enables firmware-first error handling of memory and CPU errors. Due to a lack of standard RAS architecture (or machine check architecture equivalent) on ARMv8.0 systems, APEI/GHES is the only mechanism available for reporting hardware errors (e.g. memory and CPU errors). This enables reporting of hardware errors, and also helps enable memory fault recovery mechanisms to extend the life of the system by offlining pages when recoverable uncorrected errors are encountered. Note that other ARM vendors will be going in this direction for hardware error handling. [Test] Test kernel available in https://launchpad.net/~centriq-team/+archive/ubuntu/lp1706141 Boot the kernel and check dmesg for the following: $ dmesg | grep -i -E "edac|hest|ghes" [0.00] ACPI: HEST 0x0916 000288 (v01 QCOM QDF2400 0001 INTL 20150515) [0.620278] HEST: Table parsing has been initialized. [4.178298] EDAC MC: Ver: 3.0.0 [5.664499] ghes_edac: This EDAC driver relies on BIOS to enumerate memory and get error reports. [5.673371] ghes_edac: Unfortunately, not all BIOSes reflect the memory layout correctly. [5.681542] ghes_edac: So, the end result of using this driver varies from vendor to vendor. [5.689972] ghes_edac: If you find incorrect reports, please contact your hardware vendor [5.698142] ghes_edac: to correct its BIOS. [5.702320] ghes_edac: This system has 12 DIMM sockets. [5.707717] EDAC MC0: Giving out device to module ghes_edac.c controller ghes_edac: DEV ghes (INTERRUPT) [5.717264] EDAC MC1: Giving out device to module ghes_edac.c controller ghes_edac: DEV ghes (INTERRUPT) [5.726806] EDAC MC2: Giving out device to module ghes_edac.c controller ghes_edac: DEV ghes (INTERRUPT) [5.736344] EDAC MC3: Giving out device to module ghes_edac.c controller ghes_edac: DEV ghes (INTERRUPT) [5.745883] EDAC MC4: Giving out device to module ghes_edac.c controller ghes_edac: DEV ghes (INTERRUPT) [5.755469] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC. [Fix] 1. Apply RAS patch series submitted for SRU in Bug #1696570 2. Set config option EDAC_MM_EDAC=y for ARM64, this will automatically set EDAC_GHES=y 3. Remove edac_core from debian.master/abi//arm64/generic.modules [Regression Potential] The config change is limited to ARM64 architecture, and does not impact any other architecture. Potential for regressions is low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1706141/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1704841] Re: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127
** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1704841 Title: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 Status in bcmwl package in Ubuntu: New Bug description: I am unable to download any thing due to this error.I guessthis error due t snapd ProblemType: Package DistroRelease: Ubuntu 17.10 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.5-0ubuntu5 AptOrdering: NULL: ConfigurePending Architecture: amd64 Date: Mon Jul 17 18:32:50 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 127 InstallationDate: Installed on 2017-04-18 (90 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5~beta1 SourcePackage: bcmwl Title: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 UpgradeStatus: Upgraded to artful on 2017-07-02 (14 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1704841/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1704841] Re: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1704841 Title: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 Status in bcmwl package in Ubuntu: New Bug description: I am unable to download any thing due to this error.I guessthis error due t snapd ProblemType: Package DistroRelease: Ubuntu 17.10 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.5-0ubuntu5 AptOrdering: NULL: ConfigurePending Architecture: amd64 Date: Mon Jul 17 18:32:50 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 127 InstallationDate: Installed on 2017-04-18 (90 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5~beta1 SourcePackage: bcmwl Title: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 UpgradeStatus: Upgraded to artful on 2017-07-02 (14 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1704841/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1704840] Re: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127
*** This bug is a duplicate of bug 1704841 *** https://bugs.launchpad.net/bugs/1704841 ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1704840 Title: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 Status in bcmwl package in Ubuntu: New Bug description: I am unable to download any thing due to this error.I guessthis error due t snapd ProblemType: Package DistroRelease: Ubuntu 17.10 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.5-0ubuntu5 AptOrdering: NULL: ConfigurePending Architecture: amd64 Date: Mon Jul 17 18:32:50 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 127 InstallationDate: Installed on 2017-04-18 (90 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5~beta1 SourcePackage: bcmwl Title: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 UpgradeStatus: Upgraded to artful on 2017-07-02 (14 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1704840/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1706991] Re: ubuntu/rsi driver downlink wifi throughput drops to 5-6 Mbps when BT keyboard is connected
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.13 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13-rc2 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1706991 Title: ubuntu/rsi driver downlink wifi throughput drops to 5-6 Mbps when BT keyboard is connected Status in linux package in Ubuntu: Incomplete Bug description: In STA+BT+BLE mode, we get expected wifi throughput numbers when BT device is not connected. It drops to 5-6 Mbps from 30+Mbps as soon as BT keyboard is connected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1706991/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1706380] Re: Revert 'Auto-online hotplugged memory'" patch
Commit 849d9b98df759 is in Zesty as of kernel version: Ubuntu-4.10.0-12. There is also a revert in Artful as of version: Ubuntu-4.11.0-3.8. Commit 943db62c316c was never added to Xenial, so it does not need to be reverted there. ** Changed in: linux (Ubuntu) Status: New => Triaged ** Tags added: kernel-da-key ** Also affects: linux (Ubuntu Zesty) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Zesty) Status: New => Fix Released ** Changed in: linux (Ubuntu Zesty) Importance: Undecided => Critical ** Changed in: linux (Ubuntu Zesty) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu) Importance: Undecided => Critical ** Also affects: linux (Ubuntu Artful) Importance: Critical Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) Status: Triaged ** Changed in: linux (Ubuntu Artful) Status: Triaged => Fix Released ** Changed in: linux (Ubuntu Artful) Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) => Joseph Salisbury (jsalisbury) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1706380 Title: Revert 'Auto-online hotplugged memory'" patch Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Zesty: Fix Released Status in linux source package in Artful: Fix Released Bug description: == Comment: #2 - Gustavo Luiz Ferreira Walbon - 2017-07-24 16:00:16 == This backport patch reverts to the previous behavior hotplug memory, and to ensure that CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE is unset in the kernel config as well. == Comment: #3 - Reza A. Arbab - 2017-07-24 16:34:45 == The patch to backport is 943db62c316c ("powerpc/pseries: Revert 'Auto-online hotplugged memory'") To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1706380/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1706290] Re: Marvell 88W8897 wifi throughput
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.13 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13-rc2 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1706290 Title: Marvell 88W8897 wifi throughput Status in linux package in Ubuntu: Incomplete Bug description: recently when we use the chip 88w8897 ,we found that there were some probles abuot the wifi,the topo is as follows: 88w8897wirelessrouter88w8897 we have two devices which use the chip,when we test the throughput between the two devices, we found some probles: 1.the throughput of upload is much lower than the download,at the idel environment,the upload throughput is about 200Mbps but the download throughput is 350Mbps. 2.when we restart the device and test the throughput between the two devices,the upload throughput is very low at the first time,then it gos up to the normal value slowly,sometimes it can't, the value is between 1mbps to 10mbps. so i want to know how can i fix the two probles,can you help me. our platform is linux(arm64) ,kernel is 4.4.16 ,the motherboard is rk3399 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1706290/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1706247] Re: Possible to turn on 16g huge pages on Ubuntu 16.04.2 PowerNV
** Package changed: kernel-package (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Triaged ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Tags added: kernel-da-key -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1706247 Title: Possible to turn on 16g huge pages on Ubuntu 16.04.2 PowerNV Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: Triaged Bug description: 16G Huge Pages are not supported on PowerNV (bare metal) installations. Ubuntu 16.04.2 still allows 16G huge pages to be turned on. Contact Information = Mike Hollinger (mchol...@us.ibm.com) ---uname output--- Linux aprilmin4 4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:53:54 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux Machine Type = 8335-GTB ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. Add the following to the kernel boot args (either via editing the petitboot boot option manually, or updating /boot/grub/grub.cfg: default_hugepagesz=16G hugepagesz=16G hugepages=4 2. Boot Linux 3. Observe that the kernel believes 16G huge pages are available: ubuntu@aprilmin7:~$ cat /proc/meminfo | grep -i huge AnonHugePages:475136 kB HugePages_Total: 0 HugePages_Free:0 HugePages_Rsvd:0 HugePages_Surp:0 Hugepagesize: 16777216 kB ubuntu@aprilmin7:~$ ls /sys/devices/system/node/node0/hugepages hugepages-1024kB hugepages-16384kB hugepages-16777216kB Stack trace output: no Oops output: no System Dump Info: The system is not configured to capture a system dump. *Additional Instructions for Mike Hollinger (mchol...@us.ibm.com): -Post a private note with access information to the machine that the bug is occuring on. -Attach sysctl -a output output to the bug. This may be recreated on any bare metal POWER8 server with Ubuntu 16.04.2; I haven't checked other versions of Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1706247/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1706033] Re: [P9, Power NV][ WSP][Ubuntu 16.04.03] : perf hw breakpoint command results in call traces and system goes for reboot.
I built a Xenial test kernel with commit d89ba5353f301971dd7. The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1706033/ Can you test this kernel and see if it resolves this bug? Thanks in advance! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1706033 Title: [P9, Power NV][ WSP][Ubuntu 16.04.03] : perf hw breakpoint command results in call traces and system goes for reboot. Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: In Progress Bug description: == Comment: #0 - Shriya R. Kulkarni <> - 2017-06-14 04:38:16 == Problem Description : = While running perftool - testsuite, the perf hw breakpoint fails and it result in call traces , hence system goes for reboot . Machine details : == System : P9 , WSP , Bare metal. OS : Ubuntu 16.04.03 uname -a : Linux ltc-wspoon3 4.10.0-23-generic #25~16.04.1-Ubuntu SMP Fri Jun 9 10:43:34 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux Steps to reproduce: 1. Install perf. 2. git clone perftool-testsuite. https://github.com/rfmvh/perftool-testsuite 3. Do make. 4. Test fails at step : -- [ FAIL ] -- perf_stat :: test_hw_breakpoints :: kspace address execution mem:0xc035c020:x (command exitcode + output regexp parsing and call trace is seen as system goes for reboot. Call traces : === ubuntu@ltc-wspoon3:~$ [1602513.518414] Unable to handle kernel paging request for data at address 0xc135d3b8 [1602513.518553] Faulting instruction address: 0xc02869bc [1602513.518694] Oops: Kernel access of bad area, sig: 11 [#1] [1602513.518782] SMP NR_CPUS=2048 [1602513.518784] NUMA [1602513.518842] PowerNV [1602513.518922] Modules linked in: vmx_crypto ofpart ipmi_powernv cmdlinepart ipmi_devintf powernv_flash ipmi_msghandler ibmpowernv opal_prd mtd at24 nvmem_core uio_pdrv_genirq uio autofs4 ast i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops crc32c_vpmsum ttm drm tg3 ahci libahci [1602513.519399] CPU: 27 PID: 4069 Comm: sysctl Not tainted 4.10.0-22-generic #24 [1602513.519524] task: c000203968c42c00 task.stack: c00020396571 [1602513.519624] NIP: c02869bc LR: c03f7348 CTR: c0286990 [1602513.519747] REGS: c000203965713a40 TRAP: 0300 Not tainted (4.10.0-22-generic) [1602513.519876] MSR: 90009033[1602513.519889] CR: 22002448 XER: [1602513.520058] CFAR: c03f7344 DAR: c135d3b8 DSISR: 0040 SOFTE: 1 [1602513.520058] GPR00: c03f7348 c000203965713cc0 c145d100 c134af00 [1602513.520058] GPR04: 4ee50300 c000203965713d20 c000203965713e00 [1602513.520058] GPR08: c135d100 c0b71020 [1602513.520058] GPR12: c0286990 c7b4f300 [1602513.520058] GPR16: [1602513.520058] GPR20: 0001 [1602513.520058] GPR24: 3fffc542f5a0 0400 c000203965713e00 4ee50300 [1602513.520058] GPR28: c134af00 c03fee038800 [1602513.521280] NIP [c02869bc] dirty_ratio_handler+0x2c/0x90 [1602513.521374] LR [c03f7348] proc_sys_call_handler+0x138/0x1c0 [1602513.521481] Call Trace: [1602513.521526] [c000203965713cc0] [c000203965713d00] 0xc000203965713d00 (unreliable) [1602513.521655] [c000203965713d00] [c03f7348] proc_sys_call_handler+0x138/0x1c0 [1602513.521797] [c000203965713d70] [c03436ec] __vfs_read+0x3c/0x70 [1602513.521907] [c000203965713d90] [c034516c] vfs_read+0xbc/0x1b0 [1602513.522016] [c000203965713de0] [c0346dd8] SyS_read+0x68/0x110 [1602513.522112] [c000203965713e30] [c000b184] system_call+0x38/0xe0 [1602513.522243] Instruction dump: [1602513.522303] 6042 3c4c011d 38426770 7c0802a6 6000 7c0802a6 fbc1fff0 fbe1fff8 [1602513.522445] f8010010 f821ffc1 3d22fff0 7c9f2378 4be66da9 6000 3d22fff0 [1602513.522564] ---[ end trace 17c76e13e641d3c6 ]--- [1602513.522657] It goes for reboot : After booting to Ubuntu , I see series of call traces. Ubuntu 16.04.2 LTS ltc-wspoon3 hvc0 ltc-wspoon3 login: [ 3476.626263] Unable to handle kernel paging request for data at address 0xc13ad438 [ 3476.626422] Faulting instruction address: 0xc029a140 [ 3476.626537] Oops: Kernel access of bad area, sig: 11 [#1] [ 3476.626615] SMP NR_CPUS=2048 [ 3476.626616] NUMA [ 3476.626673] PowerNV [ 3476.626746] Modules linked in: ipmi_powernv at24 ipmi_devintf nvmem_core ipmi_msghandler ofpart
[Kernel-packages] [Bug 1706977] Re: Issues with Nvidia GeForce GT 240M. Can't define monitor and set proper resolution. Also, Redshift doesn't work.
Yes, after a kernel update. 100%. I've seen that before after installing 4.4.0-75 kernel (or newer version, I don't remember). Ignored kernel updates for a while, today I've tried to update to 4.4.0-87 and got the same issues. Sorry, but I won't install 4.13-rc2 upstream kernel. The process is complicated + I'm on Linux Mint 18.1 (it's based on 16.04 but obviously it's not pure 16.04) and I don't wanna risk. Maybe I could find time to add some log files (if I'll figure out how), I don't know. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1706977 Title: Issues with Nvidia GeForce GT 240M. Can't define monitor and set proper resolution. Also, Redshift doesn't work. Status in linux package in Ubuntu: Incomplete Bug description: Kernel: 4.4.0-87. Nvidia screen (after boot) has disappeared. System: Linux Mint 18.1 MATE Laptop: Fujitsu Amilo Pi 3560 I'm using 4.4.0-72 kernel for now with no such issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1706977/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1706033] Re: [P9, Power NV][ WSP][Ubuntu 16.04.03] : perf hw breakpoint command results in call traces and system goes for reboot.
** Changed in: linux (Ubuntu) Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1706033 Title: [P9, Power NV][ WSP][Ubuntu 16.04.03] : perf hw breakpoint command results in call traces and system goes for reboot. Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: In Progress Bug description: == Comment: #0 - Shriya R. Kulkarni <> - 2017-06-14 04:38:16 == Problem Description : = While running perftool - testsuite, the perf hw breakpoint fails and it result in call traces , hence system goes for reboot . Machine details : == System : P9 , WSP , Bare metal. OS : Ubuntu 16.04.03 uname -a : Linux ltc-wspoon3 4.10.0-23-generic #25~16.04.1-Ubuntu SMP Fri Jun 9 10:43:34 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux Steps to reproduce: 1. Install perf. 2. git clone perftool-testsuite. https://github.com/rfmvh/perftool-testsuite 3. Do make. 4. Test fails at step : -- [ FAIL ] -- perf_stat :: test_hw_breakpoints :: kspace address execution mem:0xc035c020:x (command exitcode + output regexp parsing and call trace is seen as system goes for reboot. Call traces : === ubuntu@ltc-wspoon3:~$ [1602513.518414] Unable to handle kernel paging request for data at address 0xc135d3b8 [1602513.518553] Faulting instruction address: 0xc02869bc [1602513.518694] Oops: Kernel access of bad area, sig: 11 [#1] [1602513.518782] SMP NR_CPUS=2048 [1602513.518784] NUMA [1602513.518842] PowerNV [1602513.518922] Modules linked in: vmx_crypto ofpart ipmi_powernv cmdlinepart ipmi_devintf powernv_flash ipmi_msghandler ibmpowernv opal_prd mtd at24 nvmem_core uio_pdrv_genirq uio autofs4 ast i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops crc32c_vpmsum ttm drm tg3 ahci libahci [1602513.519399] CPU: 27 PID: 4069 Comm: sysctl Not tainted 4.10.0-22-generic #24 [1602513.519524] task: c000203968c42c00 task.stack: c00020396571 [1602513.519624] NIP: c02869bc LR: c03f7348 CTR: c0286990 [1602513.519747] REGS: c000203965713a40 TRAP: 0300 Not tainted (4.10.0-22-generic) [1602513.519876] MSR: 90009033[1602513.519889] CR: 22002448 XER: [1602513.520058] CFAR: c03f7344 DAR: c135d3b8 DSISR: 0040 SOFTE: 1 [1602513.520058] GPR00: c03f7348 c000203965713cc0 c145d100 c134af00 [1602513.520058] GPR04: 4ee50300 c000203965713d20 c000203965713e00 [1602513.520058] GPR08: c135d100 c0b71020 [1602513.520058] GPR12: c0286990 c7b4f300 [1602513.520058] GPR16: [1602513.520058] GPR20: 0001 [1602513.520058] GPR24: 3fffc542f5a0 0400 c000203965713e00 4ee50300 [1602513.520058] GPR28: c134af00 c03fee038800 [1602513.521280] NIP [c02869bc] dirty_ratio_handler+0x2c/0x90 [1602513.521374] LR [c03f7348] proc_sys_call_handler+0x138/0x1c0 [1602513.521481] Call Trace: [1602513.521526] [c000203965713cc0] [c000203965713d00] 0xc000203965713d00 (unreliable) [1602513.521655] [c000203965713d00] [c03f7348] proc_sys_call_handler+0x138/0x1c0 [1602513.521797] [c000203965713d70] [c03436ec] __vfs_read+0x3c/0x70 [1602513.521907] [c000203965713d90] [c034516c] vfs_read+0xbc/0x1b0 [1602513.522016] [c000203965713de0] [c0346dd8] SyS_read+0x68/0x110 [1602513.522112] [c000203965713e30] [c000b184] system_call+0x38/0xe0 [1602513.522243] Instruction dump: [1602513.522303] 6042 3c4c011d 38426770 7c0802a6 6000 7c0802a6 fbc1fff0 fbe1fff8 [1602513.522445] f8010010 f821ffc1 3d22fff0 7c9f2378 4be66da9 6000 3d22fff0 [1602513.522564] ---[ end trace 17c76e13e641d3c6 ]--- [1602513.522657] It goes for reboot : After booting to Ubuntu , I see series of call traces. Ubuntu 16.04.2 LTS ltc-wspoon3 hvc0 ltc-wspoon3 login: [ 3476.626263] Unable to handle kernel paging request for data at address 0xc13ad438 [ 3476.626422] Faulting instruction address: 0xc029a140 [ 3476.626537] Oops: Kernel access of bad area, sig: 11 [#1] [ 3476.626615] SMP NR_CPUS=2048 [ 3476.626616] NUMA [ 3476.626673] PowerNV [ 3476.626746] Modules linked in: ipmi_powernv at24 ipmi_devintf nvmem_core ipmi_msghandler ofpart cmdlinepart powernv_flash mtd
[Kernel-packages] [Bug 1705900] Re: Lenovo e73 USB webcam problems
Will do as soon as I have access to the computer in question. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1705900 Title: Lenovo e73 USB webcam problems Status in linux package in Ubuntu: Incomplete Bug description: I'm experiencing problems with USB webcam on Lenovo e73 with Ubuntu 16.04.2 Xenial 32bit. Originally with 4.4 connecting the camera often resulted in complete hang of the system (apparently not even SysRq worked, though I did not test that personally since it is a system I'm administering remotely for a family member). There was always a null pointer dereference just before the hang, so I suspect that is the culprit (see the attached kernel log). After some updates the system no longer hangs. I suspect this was fixed by going from linux 4.4 to 4.8. However, the webcam still often doesn't work and most application just return error. This is usually fixed after several tries, but sometimes it is necessary to reboot computer. Updating BIOS didn't help. The kernel logs still contain the same null pointer dereference with exactly the same stack trace for both 4.8 and 4.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705900/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1692538] Re: Ubuntu 16.04.02: ibmveth: Support to enable LSO/CSO for Trunk VEA
I had a build failure with Xenial. There are some prereq commits required that I am working on identifying now. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1692538 Title: Ubuntu 16.04.02: ibmveth: Support to enable LSO/CSO for Trunk VEA Status in The Ubuntu-power-systems project: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: == Comment: #0 - BRYANT G. LY- 2017-05-22 08:40:16 == ---Problem Description--- - Issue 1: ibmveth doesn't support largesend and checksum offload features when configured as "Trunk". Driver has explicit checks to prevent enabling these offloads. - Issue 2: SYN packet drops seen at destination VM. When the packet originates, it has CHECKSUM_PARTIAL flag set and as it gets delivered to IO server's inbound Trunk ibmveth, on validating "checksum good" bits in ibmveth receive routine, SKB's ip_summed field is set with CHECKSUM_UNNECESSARY flag. This packet is then bridged by OVS (or Linux Bridge) and delivered to outbound Trunk ibmveth. At this point the outbound ibmveth transmit routine will not set "no checksum" and "checksum good" bits in transmit buffer descriptor, as it does so only when the ip_summed field is CHECKSUM_PARTIAL. When this packet gets delivered to destination VM, TCP layer receives the packet with checksum value of 0 and with no checksum related flags in ip_summed field. This leads to packet drops. So, TCP connections never goes through fine. - Issue 3: First packet of a TCP connection will be dropped, if there is no OVS flow cached in datapath. OVS while trying to identify the flow, computes the checksum. The computed checksum will be invalid at the receiving end, as ibmveth transmit routine zeroes out the pseudo checksum value in the packet. This leads to packet drop. - Issue 4: ibmveth driver doesn't have support for SKB's with frag_list. When Physical NIC has GRO enabled and when OVS bridges these packets, OVS vport send code will end up calling dev_queue_xmit, which in turn calls validate_xmit_skb. In validate_xmit_skb routine, the larger packets will get segmented into MSS sized segments, if SKB has a frag_list and if the driver to which they are delivered to doesn't support NETIF_F_FRAGLIST feature. Contact Information = Bryant G. Ly/b...@us.ibm.com ---uname output--- 4.8.0-51.54 Machine Type = p8 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Increases performance greatly The patch has been accepted upstream: https://patchwork.ozlabs.org/patch/764533/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1692538/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1706243] Re: Stranded with ENODEV after mdadm --readonly
** Changed in: linux (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1706243 Title: Stranded with ENODEV after mdadm --readonly Status in linux package in Ubuntu: Confirmed Bug description: Please backport upstream fix. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?h=v4.12.3=065e519e71b2c1f41936cce75b46b5ab34adb588 --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: trent 10668 F...m pulseaudio /dev/snd/pcmC0D0p: trent 10668 F...m pulseaudio /dev/snd/controlC0: trent 10668 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=848108cd-a607-494c-a6ea-626267ed0a12 InstallationDate: Installed on 2014-12-23 (944 days ago) InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.3) IwConfig: p11p1 no wireless extensions. lono wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 002: ID 1307:0163 Transcend Information, Inc. 256MB/512MB/1GB Flash Drive Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic root=UUID=7afb765b-b26b-44cc-ace1-654320cd85b2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17 RelatedPackageVersions: linux-restricted-modules-4.10.0-26-generic N/A linux-backports-modules-4.10.0-26-generic N/A linux-firmware 1.157.11 RfKill: Tags: xenial xenial Uname: Linux 4.10.0-26-generic x86_64 UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: Upgraded to xenial on 2017-07-01 (24 days ago) UserGroups: adm audio cdrom dip glftpd lpadmin plugdev sambashare sudo _MarkForUpload: False dmi.bios.date: 06/16/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0808 dmi.board.asset.tag: Default string dmi.board.name: PRIME B250M-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0808:bd06/16/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB250M-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1706243/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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] Re: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks
I've ran into this problem several times. After disabling C-states in the motherboard, my system has been running stable for ~5 weeks uptime so far. -- You 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: Unknown 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: _MarkForUpload: True To manage notifications about this bug go to:
[Kernel-packages] [Bug 1696375] Re: cpupower suggests installation of non-existent linux-cloud-tools-generic package
** Tags removed: kernel-da-key ** Tags added: kernel-key ** Changed in: linux (Ubuntu) Importance: Medium => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1696375 Title: cpupower suggests installation of non-existent linux-cloud-tools- generic package Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: Triaged Bug description: Problem Description === cpupower suggests installation of non-existent linux-cloud-tools-generic package Problem occurs on an IBM POWER 16.04 LTS system. Unknown whether it occurs on other architectures or later releases. When run _without package "linux-tools-$(uname -r)" installed_, cpupower will issue a complaint, suggesting to install (among others), some linux-cloud-tools-*-generic packages: $ cpupower WARNING: cpupower not found for kernel 4.4.0-75 You may need to install the following packages for this specific kernel: linux-tools-4.4.0-75-generic linux-cloud-tools-4.4.0-75-generic You may also want to install one of the following packages to keep up to date: linux-tools-generic linux-cloud-tools-generic However, those linux-cloud-tools-*-generic package appear not to exist --at least not in the default repos. Package linux-cloud-tools-common exists, but none of the *-generic packages are available: $ apt-cache policy "linux-cloud-*" $ cat xxx linux-cloud-tools-common: Installed: (none) Candidate: 4.4.0-78.99 Version table: 4.4.0-78.99 500 500 http://ports.ubuntu.com/ubuntu-ports xenial-proposed/main ppc64el Packages 4.4.0-77.98 500 500 http://us.ports.ubuntu.com/ubuntu-ports xenial-updates/main ppc64el Packages 4.4.0-75.96 500 500 http://us.ports.ubuntu.com/ubuntu-ports xenial-updates/main ppc64el Packages 500 http://ports.ubuntu.com/ubuntu-ports xenial-security/main ppc64el Packages [...] 4.4.0-21.37 500 500 http://us.ports.ubuntu.com/ubuntu-ports xenial/main ppc64el Packages The cpupower command works (at least doesn't give this complaint) if the appropriate linux-tools-$(uname -r) (perhaps via linux-tools-generic) is installed, so the cloud package is maybe not needed (as least for some functionality). I think the fix is to either: a) supply the cloud packages for POWER, or b) remove the non-existent packages from cpupower's complaint message. ---uname output--- Linux fs3 4.4.0-75-generic #96-Ubuntu SMP Thu Apr 20 09:55:30 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux Machine Type = Firestone ---Steps to Reproduce--- Install linux-tools-common but NOT linux-tools-*-generic on a POWER 16.04 LTS system, then run cpupower. Userspace rpm: linux-tools-common To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1696375/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1635223] Re: please include mlx5_core modules in linux-image-generic package
** Changed in: cloud-images Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1635223 Title: please include mlx5_core modules in linux-image-generic package Status in cloud-images: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Yakkety: Fix Released Status in linux source package in Zesty: Fix Released Bug description: Because linux-image-generic pkg doesn't include mlx5_core, stock ubuntu cloud-images can't be used by VM guests using mellanox VFs, forcing the creation of an ad-hoc cloud image with added linux-image-extra-virtual To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1635223/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1707075] 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/1707075 Title: package linux-image-4.4.0-87-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in linux package in Ubuntu: Confirmed Bug description: having problems updating ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-87-generic (not installed) ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70 Uname: Linux 4.4.0-83-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: laurence 1647 F pulseaudio Date: Thu Jul 27 22:58:52 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 HibernationDevice: RESUME=UUID=80df043f-2917-407a-8050-b2477b65b385 InstallationDate: Installed on 2016-09-13 (316 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 20FU0007UK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-83-generic.efi.signed root=UUID=b8f58a9d-2806-4032-9a5e-2085d6a04fcf ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A SourcePackage: linux Title: package linux-image-4.4.0-87-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/20/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R08ET40W (1.14 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FU0007UK dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR08ET40W(1.14):bd04/20/2016:svnLENOVO:pn20FU0007UK:pvrThinkPadL460:rvnLENOVO:rn20FU0007UK:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20FU0007UK dmi.product.version: ThinkPad L460 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1707075/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1695780] Re: On VMware ESXi with PCI passthru enabled for Intel NVMe Ubuntu Xenial VM does not boot
Sorry to be a bother. Any luck in further bisection? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1695780 Title: On VMware ESXi with PCI passthru enabled for Intel NVMe Ubuntu Xenial VM does not boot Status in linux package in Ubuntu: Confirmed Bug description: My set up is a Cisco UCS c240 server with an Intel NVMe 1.6TB drive running VMware ESXi version 6.0U2. NVMe device is made available as a PCI passthru device and not claimed by ESXi kernel. This NVMe device when added to a Ubuntu 16.04.2 running kernel version 4.4.0-62 and above does not boot, kernel does not boot fully and hangs for while before the VM powers off. However, running kernel versions 4.4.0-43, 4.4.0-53, 4.4.0-57, and 4.4.0-59 everything works as expected. Earlier versions of the kernel also do not work. Here is a short list of the I tested with 4.4.0-31 -> kernel panic (different issue) 4.4.0-43 -> works 4.4.0-53 -> works 4.4.0-57 -> works 4.4.0-59 -> works 4.4.0-62 -> fail 4.4.0-64 -> fail 4.4.0-75 -> fail 4.4.0-77 -> fail 4.8.0-51 -> fail ~# cat /proc/version_signature Ubuntu 4.4.0-75.96-generic 4.4.59 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1695780/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1694859] Re: arm64 kernel crashdump support
This bug was fixed in the package kexec-tools - 1:2.0.10-1ubuntu2.3 --- kexec-tools (1:2.0.10-1ubuntu2.3) xenial; urgency=medium * Add backport of upstream arm64 crashdump support (LP: #1694859). -- dann frazierFri, 23 Jun 2017 12:27:52 -0600 ** Changed in: kexec-tools (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/1694859 Title: arm64 kernel crashdump support Status in kexec-tools package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in makedumpfile package in Ubuntu: Fix Released Status in kexec-tools source package in Xenial: Fix Released Status in linux source package in Xenial: Won't Fix Status in makedumpfile source package in Xenial: Fix Committed Status in kexec-tools source package in Yakkety: In Progress Status in linux source package in Yakkety: Won't Fix Status in makedumpfile source package in Yakkety: Won't Fix Status in kexec-tools source package in Zesty: Fix Released Status in linux source package in Zesty: Fix Released Status in makedumpfile source package in Zesty: Fix Released Bug description: Note: Updates are being staged at ppa:dannf/arm64-kdump. [Impact] It is not possible to collect a kernel crash dump from a crashed arm64 server for later debugging. [Test Case] sudo apt install kdump-tools (reboot, so crashkernel= is added to the kernel commandline) echo c | sudo tee /proc/sysrq-trigger Crash dump should occur, with artifacts collected in /var/crash. If you want to verify that the dump is usable, install the corresponding linux-image--dbgsym package and run: sudo crash /usr/lib/debug/boot/vmlinux- /var/crash//dump. crash should successfully load, placing you at a "crash>" prompt. At that prompt, you can issue the 'bt' command to see a backtrace. Note: you need crash from zesty (7.1.8-1ubuntu1) or later. [Regression Risk] = Kernel = 3 patches here touch code outside of arch/arm64/: memblock: add memblock_clear_nomap() This adds a new function with no callers, so regression risk is negligible. (A later patch adds a call to it under arch/arm64/). memblock: add memblock_cap_memory_range() This refactors some of the code in memblock_mem_limit_remove_map() into a new function. The only existing caller of memblock_mem_limit_remove_map() is under arch/arm64/, so the regression risk outside of arm64 is negligible. efi/libstub/arm*: Set default address and size cells values for an empty dtb Because this code is for EFI platforms that support device-tree, it is de-facto ARM-specific (as noted in the patch title). For arm64, we have mitigated the risk by explicit regression testing on several platforms: - Qualcomm QDF2400 - Cavium ThunderX CRB1S - HP m400 (X-Gene) - HiSilicon D05 (Hi07) = kexec-tools = == zesty == For zesty, 10 patches are required to add kdump support. 0001-kexec-extend-the-semantics-of-kexec_iomem_for_each_l.patch: This modifies a function used on armhf & x86. The description explains the change, and why it does not impact those archs: - The current users of kexec_iomem_for_each_line(), arm, sh and x86, will not be affected by this change because * arm The callback function only returns -1 or 0, and the return value of kexec_iomem_for_each_line() will never be used. * sh, x86 The callback function may return (-1 for sh,) 0 or 1, but always returns 1 once we have reached the maximum number of entries allowed. Even so the current kexec_iomem_for_each_line() counts them up. This change actually fixes this bug. - 0002-kexec-generalize-and-rename-get_kernel_stext_sym.patch: This generalizes a function that was duplicated by arm & x86 and makes it common so arm64 can use it. The remaining 8 of these only touch code in kexec/arch/arm64, so regression risk for other architectures is negligible. Finally, I have tested this update on both i386 and amd64 VMs. i386 crashes do not currently work in zesty (filed LP: #1699874), and my test results show no change there. amd64 worked before, and continues to work with these changes. == yakkety == Since yakkety is based on an older upstream, 6 additional patches are required: arm-fix-get_kernel_stext_sym-to-close-its-file.patch: This is a cleanup patch, cherry-picked because it allows later patches to apply w/o backporting. ARM-specific. kexec-add-max_size-to-memory_ranges.patch: Adds a new element to struct, to be used by later commits. kexec-add-generic-helper-to-add-to-memoryq_regions.patch, kexec-add-mem_regions-sorting-implementation.patch, kexec-add-helper-to-exlude-a-region-from-a-set-of-me.patch, kexec-fix-mem_regions_sort.patch: These patches only add new functions,
[Kernel-packages] [Bug 1694859] Update Released
The verification of the Stable Release Update for kexec-tools has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/1694859 Title: arm64 kernel crashdump support Status in kexec-tools package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in makedumpfile package in Ubuntu: Fix Released Status in kexec-tools source package in Xenial: Fix Released Status in linux source package in Xenial: Won't Fix Status in makedumpfile source package in Xenial: Fix Committed Status in kexec-tools source package in Yakkety: In Progress Status in linux source package in Yakkety: Won't Fix Status in makedumpfile source package in Yakkety: Won't Fix Status in kexec-tools source package in Zesty: Fix Released Status in linux source package in Zesty: Fix Released Status in makedumpfile source package in Zesty: Fix Released Bug description: Note: Updates are being staged at ppa:dannf/arm64-kdump. [Impact] It is not possible to collect a kernel crash dump from a crashed arm64 server for later debugging. [Test Case] sudo apt install kdump-tools (reboot, so crashkernel= is added to the kernel commandline) echo c | sudo tee /proc/sysrq-trigger Crash dump should occur, with artifacts collected in /var/crash. If you want to verify that the dump is usable, install the corresponding linux-image--dbgsym package and run: sudo crash /usr/lib/debug/boot/vmlinux- /var/crash//dump. crash should successfully load, placing you at a "crash>" prompt. At that prompt, you can issue the 'bt' command to see a backtrace. Note: you need crash from zesty (7.1.8-1ubuntu1) or later. [Regression Risk] = Kernel = 3 patches here touch code outside of arch/arm64/: memblock: add memblock_clear_nomap() This adds a new function with no callers, so regression risk is negligible. (A later patch adds a call to it under arch/arm64/). memblock: add memblock_cap_memory_range() This refactors some of the code in memblock_mem_limit_remove_map() into a new function. The only existing caller of memblock_mem_limit_remove_map() is under arch/arm64/, so the regression risk outside of arm64 is negligible. efi/libstub/arm*: Set default address and size cells values for an empty dtb Because this code is for EFI platforms that support device-tree, it is de-facto ARM-specific (as noted in the patch title). For arm64, we have mitigated the risk by explicit regression testing on several platforms: - Qualcomm QDF2400 - Cavium ThunderX CRB1S - HP m400 (X-Gene) - HiSilicon D05 (Hi07) = kexec-tools = == zesty == For zesty, 10 patches are required to add kdump support. 0001-kexec-extend-the-semantics-of-kexec_iomem_for_each_l.patch: This modifies a function used on armhf & x86. The description explains the change, and why it does not impact those archs: - The current users of kexec_iomem_for_each_line(), arm, sh and x86, will not be affected by this change because * arm The callback function only returns -1 or 0, and the return value of kexec_iomem_for_each_line() will never be used. * sh, x86 The callback function may return (-1 for sh,) 0 or 1, but always returns 1 once we have reached the maximum number of entries allowed. Even so the current kexec_iomem_for_each_line() counts them up. This change actually fixes this bug. - 0002-kexec-generalize-and-rename-get_kernel_stext_sym.patch: This generalizes a function that was duplicated by arm & x86 and makes it common so arm64 can use it. The remaining 8 of these only touch code in kexec/arch/arm64, so regression risk for other architectures is negligible. Finally, I have tested this update on both i386 and amd64 VMs. i386 crashes do not currently work in zesty (filed LP: #1699874), and my test results show no change there. amd64 worked before, and continues to work with these changes. == yakkety == Since yakkety is based on an older upstream, 6 additional patches are required: arm-fix-get_kernel_stext_sym-to-close-its-file.patch: This is a cleanup patch, cherry-picked because it allows later patches to apply w/o backporting. ARM-specific. kexec-add-max_size-to-memory_ranges.patch: Adds a new element to struct, to be used by later commits. kexec-add-generic-helper-to-add-to-memoryq_regions.patch, kexec-add-mem_regions-sorting-implementation.patch,
[Kernel-packages] [Bug 1694859] Re: arm64 kernel crashdump support
This bug was fixed in the package kexec-tools - 1:2.0.14-1ubuntu3.1 --- kexec-tools (1:2.0.14-1ubuntu3.1) zesty; urgency=medium * Add backport of upstream arm64 crashdump support (LP: #1694859). -- dann frazierWed, 21 Jun 2017 15:15:25 -0600 ** Changed in: kexec-tools (Ubuntu Zesty) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/1694859 Title: arm64 kernel crashdump support Status in kexec-tools package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in makedumpfile package in Ubuntu: Fix Released Status in kexec-tools source package in Xenial: Fix Released Status in linux source package in Xenial: Won't Fix Status in makedumpfile source package in Xenial: Fix Committed Status in kexec-tools source package in Yakkety: In Progress Status in linux source package in Yakkety: Won't Fix Status in makedumpfile source package in Yakkety: Won't Fix Status in kexec-tools source package in Zesty: Fix Released Status in linux source package in Zesty: Fix Released Status in makedumpfile source package in Zesty: Fix Released Bug description: Note: Updates are being staged at ppa:dannf/arm64-kdump. [Impact] It is not possible to collect a kernel crash dump from a crashed arm64 server for later debugging. [Test Case] sudo apt install kdump-tools (reboot, so crashkernel= is added to the kernel commandline) echo c | sudo tee /proc/sysrq-trigger Crash dump should occur, with artifacts collected in /var/crash. If you want to verify that the dump is usable, install the corresponding linux-image--dbgsym package and run: sudo crash /usr/lib/debug/boot/vmlinux- /var/crash//dump. crash should successfully load, placing you at a "crash>" prompt. At that prompt, you can issue the 'bt' command to see a backtrace. Note: you need crash from zesty (7.1.8-1ubuntu1) or later. [Regression Risk] = Kernel = 3 patches here touch code outside of arch/arm64/: memblock: add memblock_clear_nomap() This adds a new function with no callers, so regression risk is negligible. (A later patch adds a call to it under arch/arm64/). memblock: add memblock_cap_memory_range() This refactors some of the code in memblock_mem_limit_remove_map() into a new function. The only existing caller of memblock_mem_limit_remove_map() is under arch/arm64/, so the regression risk outside of arm64 is negligible. efi/libstub/arm*: Set default address and size cells values for an empty dtb Because this code is for EFI platforms that support device-tree, it is de-facto ARM-specific (as noted in the patch title). For arm64, we have mitigated the risk by explicit regression testing on several platforms: - Qualcomm QDF2400 - Cavium ThunderX CRB1S - HP m400 (X-Gene) - HiSilicon D05 (Hi07) = kexec-tools = == zesty == For zesty, 10 patches are required to add kdump support. 0001-kexec-extend-the-semantics-of-kexec_iomem_for_each_l.patch: This modifies a function used on armhf & x86. The description explains the change, and why it does not impact those archs: - The current users of kexec_iomem_for_each_line(), arm, sh and x86, will not be affected by this change because * arm The callback function only returns -1 or 0, and the return value of kexec_iomem_for_each_line() will never be used. * sh, x86 The callback function may return (-1 for sh,) 0 or 1, but always returns 1 once we have reached the maximum number of entries allowed. Even so the current kexec_iomem_for_each_line() counts them up. This change actually fixes this bug. - 0002-kexec-generalize-and-rename-get_kernel_stext_sym.patch: This generalizes a function that was duplicated by arm & x86 and makes it common so arm64 can use it. The remaining 8 of these only touch code in kexec/arch/arm64, so regression risk for other architectures is negligible. Finally, I have tested this update on both i386 and amd64 VMs. i386 crashes do not currently work in zesty (filed LP: #1699874), and my test results show no change there. amd64 worked before, and continues to work with these changes. == yakkety == Since yakkety is based on an older upstream, 6 additional patches are required: arm-fix-get_kernel_stext_sym-to-close-its-file.patch: This is a cleanup patch, cherry-picked because it allows later patches to apply w/o backporting. ARM-specific. kexec-add-max_size-to-memory_ranges.patch: Adds a new element to struct, to be used by later commits. kexec-add-generic-helper-to-add-to-memoryq_regions.patch, kexec-add-mem_regions-sorting-implementation.patch, kexec-add-helper-to-exlude-a-region-from-a-set-of-me.patch, kexec-fix-mem_regions_sort.patch: These patches only add new functions, which will
[Kernel-packages] [Bug 1706290] Re: Marvell 88W8897 wifi throughput
kernel-bug-exists-upstream it happens that many users have the same problem with the chip of 88w8897. Is it possible for compatibility reasons? Or because of the RF circuit caused. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1706290 Title: Marvell 88W8897 wifi throughput Status in linux package in Ubuntu: Confirmed Bug description: recently when we use the chip 88w8897 ,we found that there were some probles abuot the wifi,the topo is as follows: 88w8897wirelessrouter88w8897 we have two devices which use the chip,when we test the throughput between the two devices, we found some probles: 1.the throughput of upload is much lower than the download,at the idel environment,the upload throughput is about 200Mbps but the download throughput is 350Mbps. 2.when we restart the device and test the throughput between the two devices,the upload throughput is very low at the first time,then it gos up to the normal value slowly,sometimes it can't, the value is between 1mbps to 10mbps. so i want to know how can i fix the two probles,can you help me. our platform is linux(arm64) ,kernel is 4.4.16 ,the motherboard is rk3399 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1706290/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1706247] Re: Possible to turn on 16g huge pages on Ubuntu 16.04.2 PowerNV
** Changed in: ubuntu-power-systems Status: New => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1706247 Title: Possible to turn on 16g huge pages on Ubuntu 16.04.2 PowerNV Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: Triaged Bug description: 16G Huge Pages are not supported on PowerNV (bare metal) installations. Ubuntu 16.04.2 still allows 16G huge pages to be turned on. Contact Information = Mike Hollinger (mchol...@us.ibm.com) ---uname output--- Linux aprilmin4 4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:53:54 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux Machine Type = 8335-GTB ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. Add the following to the kernel boot args (either via editing the petitboot boot option manually, or updating /boot/grub/grub.cfg: default_hugepagesz=16G hugepagesz=16G hugepages=4 2. Boot Linux 3. Observe that the kernel believes 16G huge pages are available: ubuntu@aprilmin7:~$ cat /proc/meminfo | grep -i huge AnonHugePages:475136 kB HugePages_Total: 0 HugePages_Free:0 HugePages_Rsvd:0 HugePages_Surp:0 Hugepagesize: 16777216 kB ubuntu@aprilmin7:~$ ls /sys/devices/system/node/node0/hugepages hugepages-1024kB hugepages-16384kB hugepages-16777216kB Stack trace output: no Oops output: no System Dump Info: The system is not configured to capture a system dump. *Additional Instructions for Mike Hollinger (mchol...@us.ibm.com): -Post a private note with access information to the machine that the bug is occuring on. -Attach sysctl -a output output to the bug. This may be recreated on any bare metal POWER8 server with Ubuntu 16.04.2; I haven't checked other versions of Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1706247/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1705054] Re: Trusty kexec-tools suffer from upstream code regression. Fix not included.
## VERIFICATION TRUSTY ### I was easily able to reproduce the situation explained by Rafael above using Trusty with the "kexec-tools" package prior to version "2.0.6-0ubuntu2.3". I confirm the situation is fix now with "2.0.6-0ubuntu2.3". [Confirmation] # release root@ubuntu:~# cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=14.04 DISTRIB_CODENAME=trusty DISTRIB_DESCRIPTION="Ubuntu 14.04.5 LTS" # dpkg ii kexec-tools1:2.0.6-0ubuntu2.3 amd64tools to support fast kexec reboots # Reproducer output : root@ubuntu:~# kexec -l --reuse-cmdline --initrd=/boot/initrd.img-`uname -r` /boot/vmlinuz-`uname -r` root@ubuntu:~# /usr/sbin/kdump-config load * loaded kdump kernel - Eric ** Tags removed: verification-needed-trusty ** Tags added: verification-done-trusty ** Tags removed: verification-needed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/1705054 Title: Trusty kexec-tools suffer from upstream code regression. Fix not included. Status in kexec-tools package in Ubuntu: Fix Released Status in kexec-tools source package in Trusty: Fix Committed Bug description: [Impact] * kdump doesn't work on non-efi systems * a kernel dump can't be generated [Test Case] * install kdump-tools * configure kdump-tools (/etc/default/kdump-tools) * try to start kdump-tools service (kdump-config start) * while executing kexec, you will get: "efi memory descriptor version 0 is not supported!" [Regression Potential] * in theory it could brake kdump for efi systems * in practice, its based on upstream regression fix (not included in Trusty) * it has also been tested in 3 different setups and it worked [Other Info] Based on upstream code commit explanation: """ On non-EFI systems, efi_info section of boot_params is zero filled resulting in an erroneous message from kexec regarding "efi memory descriptor" version. Caused by commit: e1ffc9e9a0769e1f54185003102e9bec428b84e8 "Passing efi related data via setup_data" # od -j 448 -N 32 -v -x /sys/kernel/boot_params/data 700 720 740 # kexec -l --reuse-cmdline --initrd=/boot/initrd-`uname -r` /boot/vmlinuz-`uname -r` efi memory descriptor version 0 is not supported! """ It was brought to my attention to some of our users are facing this: ## TRUSTY with kernel 4.4.0-83-generic # /usr/sbin/kdump-config load efi memory descriptor version 0 is not supported! * loaded kdump kernel /var/log/syslog: Jul 18 13:37:06 kdump-config: /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-4.4.0-83-generic root=UUID=-20e4-4325-ad92-7aef2af0beac ro KDUMP_CMDLINE_APPEND=irqpoll maxcpus=1 nousb irqpoll maxcpus=1 nousb" --initrd=/boot/initrd.img-4.4.0-83-generic /boot/vmlinuz-4.4.0-83-generic Jul 18 13:37:06 kdump-config: loaded kdump kernel Despite the message of kdump being loaded, it doesn't look that it is operational. Dump files could be generated using Xenial kdump-tools, but not Trusty's. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1705054/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1706033] Re: [P9, Power NV][ WSP][Ubuntu 16.04.03] : perf hw breakpoint command results in call traces and system goes for reboot.
** Changed in: ubuntu-power-systems Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1706033 Title: [P9, Power NV][ WSP][Ubuntu 16.04.03] : perf hw breakpoint command results in call traces and system goes for reboot. Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Bug description: == Comment: #0 - Shriya R. Kulkarni <> - 2017-06-14 04:38:16 == Problem Description : = While running perftool - testsuite, the perf hw breakpoint fails and it result in call traces , hence system goes for reboot . Machine details : == System : P9 , WSP , Bare metal. OS : Ubuntu 16.04.03 uname -a : Linux ltc-wspoon3 4.10.0-23-generic #25~16.04.1-Ubuntu SMP Fri Jun 9 10:43:34 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux Steps to reproduce: 1. Install perf. 2. git clone perftool-testsuite. https://github.com/rfmvh/perftool-testsuite 3. Do make. 4. Test fails at step : -- [ FAIL ] -- perf_stat :: test_hw_breakpoints :: kspace address execution mem:0xc035c020:x (command exitcode + output regexp parsing and call trace is seen as system goes for reboot. Call traces : === ubuntu@ltc-wspoon3:~$ [1602513.518414] Unable to handle kernel paging request for data at address 0xc135d3b8 [1602513.518553] Faulting instruction address: 0xc02869bc [1602513.518694] Oops: Kernel access of bad area, sig: 11 [#1] [1602513.518782] SMP NR_CPUS=2048 [1602513.518784] NUMA [1602513.518842] PowerNV [1602513.518922] Modules linked in: vmx_crypto ofpart ipmi_powernv cmdlinepart ipmi_devintf powernv_flash ipmi_msghandler ibmpowernv opal_prd mtd at24 nvmem_core uio_pdrv_genirq uio autofs4 ast i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops crc32c_vpmsum ttm drm tg3 ahci libahci [1602513.519399] CPU: 27 PID: 4069 Comm: sysctl Not tainted 4.10.0-22-generic #24 [1602513.519524] task: c000203968c42c00 task.stack: c00020396571 [1602513.519624] NIP: c02869bc LR: c03f7348 CTR: c0286990 [1602513.519747] REGS: c000203965713a40 TRAP: 0300 Not tainted (4.10.0-22-generic) [1602513.519876] MSR: 90009033[1602513.519889] CR: 22002448 XER: [1602513.520058] CFAR: c03f7344 DAR: c135d3b8 DSISR: 0040 SOFTE: 1 [1602513.520058] GPR00: c03f7348 c000203965713cc0 c145d100 c134af00 [1602513.520058] GPR04: 4ee50300 c000203965713d20 c000203965713e00 [1602513.520058] GPR08: c135d100 c0b71020 [1602513.520058] GPR12: c0286990 c7b4f300 [1602513.520058] GPR16: [1602513.520058] GPR20: 0001 [1602513.520058] GPR24: 3fffc542f5a0 0400 c000203965713e00 4ee50300 [1602513.520058] GPR28: c134af00 c03fee038800 [1602513.521280] NIP [c02869bc] dirty_ratio_handler+0x2c/0x90 [1602513.521374] LR [c03f7348] proc_sys_call_handler+0x138/0x1c0 [1602513.521481] Call Trace: [1602513.521526] [c000203965713cc0] [c000203965713d00] 0xc000203965713d00 (unreliable) [1602513.521655] [c000203965713d00] [c03f7348] proc_sys_call_handler+0x138/0x1c0 [1602513.521797] [c000203965713d70] [c03436ec] __vfs_read+0x3c/0x70 [1602513.521907] [c000203965713d90] [c034516c] vfs_read+0xbc/0x1b0 [1602513.522016] [c000203965713de0] [c0346dd8] SyS_read+0x68/0x110 [1602513.522112] [c000203965713e30] [c000b184] system_call+0x38/0xe0 [1602513.522243] Instruction dump: [1602513.522303] 6042 3c4c011d 38426770 7c0802a6 6000 7c0802a6 fbc1fff0 fbe1fff8 [1602513.522445] f8010010 f821ffc1 3d22fff0 7c9f2378 4be66da9 6000 3d22fff0 [1602513.522564] ---[ end trace 17c76e13e641d3c6 ]--- [1602513.522657] It goes for reboot : After booting to Ubuntu , I see series of call traces. Ubuntu 16.04.2 LTS ltc-wspoon3 hvc0 ltc-wspoon3 login: [ 3476.626263] Unable to handle kernel paging request for data at address 0xc13ad438 [ 3476.626422] Faulting instruction address: 0xc029a140 [ 3476.626537] Oops: Kernel access of bad area, sig: 11 [#1] [ 3476.626615] SMP NR_CPUS=2048 [ 3476.626616] NUMA [ 3476.626673] PowerNV [ 3476.626746] Modules linked in: ipmi_powernv at24 ipmi_devintf nvmem_core ipmi_msghandler ofpart cmdlinepart powernv_flash mtd opal_prd vmx_crypto ibmpowernv uio_pdrv_genirq uio autofs4 ast i2c_algo_bit ttm crc32c_vpmsum drm_kms_helper syscopyarea
[Kernel-packages] [Bug 1704158] Re: snapd 2.26.8+17.10 ADT test failure with linux 4.12.0-6.7
Committed a revert to our 4.12 and 4.13 trees until we have a proper fix. ** Changed in: linux (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1704158 Title: snapd 2.26.8+17.10 ADT test failure with linux 4.12.0-6.7 Status in linux package in Ubuntu: Fix Committed Bug description: Testing failed on: i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/i386/s/snapd/20170712_204217_cd0b1@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/ppc64el/s/snapd/20170712_204129_cd0b1@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1704158/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1687273] Re: Shared folder randomly not mounted
seems to be resolved, issue did not occured again ** Changed in: linux (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1687273 Title: Shared folder randomly not mounted Status in Linux: Unknown Status in cifs-utils package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Released Status in cifs-utils source package in Xenial: New Status in linux source package in Xenial: In Progress Status in linux package in Debian: Fix Released Bug description: Hello Everybody, since last update from ubuntu 16.04.2, last night, my servers are randomly not able to read and write from shared folders. I got this message: lsof: WARNING: can't stat() cifs file system /mnt/record Output information may be incomplete. lsof: WARNING: can't stat() cifs file system /mnt/record Output information may be incomplete. lsof: WARNING: can't stat() cifs file system /mnt/record Output information may be incomplete. ... rsync: ERROR: cannot stat destination "/mnt/record/": Host is down (112) rsync error: errors selecting input/output files, dirs (code 3) at main.c(652) [Receiver=3.1.1] This comes from my cron script. When I type df -h it takes sometimes very long to get the list. And it also can be that the mounted share is disconnected and I have to mount -a (what also takes long) again. My fstab have this command: //address /mnt/storage cifs auto,nofail,iocharset=utf8,rw,credentials=/path/.smb,uid=1000,gid=1000,file_mode=0660,dir_mode=0770 0 0 My update list from last night was this: linux-image-4.4.0-75-generic:amd64 (4.4.0-75.96, automatic) linux-image-extra-4.4.0-75-generic:amd64 (4.4.0-75.96, automatic) linux-headers-4.4.0-75-generic:amd64 (4.4.0-75.96, automatic) linux-headers-4.4.0-75:amd64 (4.4.0-75.96, automatic) Upgrade: libdns-export162:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.5, 1:9.10.3.dfsg.P4-8ubuntu1.6) linux-headers-generic:amd64 (4.4.0.72.78, 4.4.0.75.81) linux-libc-dev:amd64 (4.4.0-72.93, 4.4.0-75.96) mysql-client-5.7:amd64 (5.7.17-0ubuntu0.16.04.2, 5.7.18-0ubuntu0.16.04.1) libapt-inst2.0:amd64 (1.2.19, 1.2.20) mysql-server-5.7:amd64 (5.7.17-0ubuntu0.16.04.2, 5.7.18-0ubuntu0.16.04.1) libsystemd0:amd64 (229-4ubuntu16, 229-4ubuntu17) linux-image-generic:amd64 (4.4.0.72.78, 4.4.0.75.81) apt:amd64 (1.2.19, 1.2.20) mysql-server:amd64 (5.7.17-0ubuntu0.16.04.2, 5.7.18-0ubuntu0.16.04.1) udev:amd64 (229-4ubuntu16, 229-4ubuntu17) libapt-pkg5.0:amd64 (1.2.19, 1.2.20) libudev1:amd64 (229-4ubuntu16, 229-4ubuntu17) cifs-utils:amd64 (2:6.4-1ubuntu1, 2:6.4-1ubuntu1.1) dpkg:amd64 (1.18.4ubuntu1.1, 1.18.4ubuntu1.2) mysql-client-core-5.7:amd64 (5.7.17-0ubuntu0.16.04.2, 5.7.18-0ubuntu0.16.04.1) libisc-export160:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.5, 1:9.10.3.dfsg.P4-8ubuntu1.6) linux-virtual:amd64 (4.4.0.72.78, 4.4.0.75.81) systemd-sysv:amd64 (229-4ubuntu16, 229-4ubuntu17) distro-info-data:amd64 (0.28ubuntu0.2, 0.28ubuntu0.3) systemd:amd64 (229-4ubuntu16, 229-4ubuntu17) mysql-common:amd64 (5.7.17-0ubuntu0.16.04.2, 5.7.18-0ubuntu0.16.04.1) apt-utils:amd64 (1.2.19, 1.2.20) libmysqlclient20:amd64 (5.7.17-0ubuntu0.16.04.2, 5.7.18-0ubuntu0.16.04.1) linux-headers-virtual:amd64 (4.4.0.72.78, 4.4.0.75.81) linux-image-extra-virtual:amd64 (4.4.0.72.78, 4.4.0.75.81) thermald:amd64 (1.5-2ubuntu3, 1.5-2ubuntu4) qemu-guest-agent:amd64 (1:2.5+dfsg-5ubuntu10.10, 1:2.5+dfsg-5ubuntu10.11) libfreetype6:amd64 (2.6.1-0.1ubuntu2.1, 2.6.1-0.1ubuntu2.2) linux-image-virtual:amd64 (4.4.0.72.78, 4.4.0.75.81) libdpkg-perl:amd64 (1.18.4ubuntu1.1, 1.18.4ubuntu1.2) mysql-server-core-5.7:amd64 (5.7.17-0ubuntu0.16.04.2, 5.7.18-0ubuntu0.16.04.1) libxslt1.1:amd64 (1.1.28-2.1, 1.1.28-2.1ubuntu0.1) dpkg-dev:amd64 (1.18.4ubuntu1.1, 1.18.4ubuntu1.2) I saw that somebody else has the same problem: https://askubuntu.com/questions/910058/updates-broke-cifs-smb-mounts- in-16-04 I had to remove the latest kernel update, after that it works. Regards To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1687273/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1704158] Re: snapd 2.26.8+17.10 ADT test failure with linux 4.12.0-6.7
** Package changed: snapd (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Status: New => In Progress ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Seth Forshee (sforshee) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1704158 Title: snapd 2.26.8+17.10 ADT test failure with linux 4.12.0-6.7 Status in linux package in Ubuntu: In Progress Bug description: Testing failed on: i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/i386/s/snapd/20170712_204217_cd0b1@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/ppc64el/s/snapd/20170712_204129_cd0b1@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1704158/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1700972] Re: Please only recommend or suggest initramfs-tools | linux-initramfs-tool for kernels able to boot without initramfs
** Changed in: linux-azure (Ubuntu) Status: In Progress => Fix Committed ** Changed in: linux-azure (Ubuntu Xenial) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1700972 Title: Please only recommend or suggest initramfs-tools | linux-initramfs- tool for kernels able to boot without initramfs Status in linux package in Ubuntu: Triaged Status in linux-aws package in Ubuntu: Triaged Status in linux-azure package in Ubuntu: Fix Committed Status in linux-gke package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Status in linux-aws source package in Xenial: Triaged Status in linux-azure source package in Xenial: Fix Committed Status in linux-gke source package in Xenial: Triaged Bug description: Linux kernel packages depend on initramfs-tools | linux-initramfs- tool, even when systems using the kernel can be booted without it. Demoting the dependency to Recommends: or Suggests: would allow creating smaller images without initramfs-tools installed and fully skipping initramfs updates upon kernel updates saving time. Please consider changing the Depends: to Recommends: or Suggests: for kernels capable of booting without initramfs. initramfs-tools is still a dependency of ubuntu-minimal thus accidental removal of initramfs-tools resulting an unbootable system would still be unlikely. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1700972/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1690174] Re: [Hyper-V] hv_netvsc: Exclude non-TCP port numbers from vRSS hashing
** Changed in: linux-azure (Ubuntu Xenial) Status: In Progress => Fix Committed ** Changed in: linux-azure (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1690174 Title: [Hyper-V] hv_netvsc: Exclude non-TCP port numbers from vRSS hashing Status in linux package in Ubuntu: Fix Committed Status in linux-azure package in Ubuntu: Fix Committed Status in linux source package in Xenial: In Progress Status in linux-azure source package in Xenial: Fix Committed Status in linux source package in Yakkety: Won't Fix Status in linux source package in Zesty: In Progress Status in linux source package in Artful: Fix Committed Bug description: Azure hosts are not supporting non-TCP port numbers in vRSS hashing for now. For example, UDP packet loss rate will be high if port numbers are also included in vRSS hash. So, we created this patch to use only IP numbers for hashing in non-TCP traffic. https://git.kernel.org/pub/scm/linux/kernel/git/next/linux- next.git/commit/?id=f72860afa2e32cdc674cbdd7f354f8fb62e908a6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1690174/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1680904] Re: zesty unable to handle kernel NULL pointer dereference
@chihchun Actually I could not install your kernel on 16.04 without breaking dependencies. It requires binutils >= 2.29 (or 2.28, not sure if I remember correctly) but Ubuntu 16.04 only includes version 2.26. So I manually edited the config file in your archive to remove that restriction. I guess other users will be affected by this, too... Nevertheless, your kernel (4.10.0-28-generic #32 SMP Sat Jul 22 12:39:20 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux) seems to fix the problem. At least I never had any additional crashes since then... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1680904 Title: zesty unable to handle kernel NULL pointer dereference Status in linux package in Ubuntu: In Progress Status in linux-hwe package in Ubuntu: Confirmed Status in linux source package in Zesty: In Progress Status in linux-hwe source package in Zesty: Confirmed Bug description: Upgraded to zesty about a week ago. Ran into this on latest kernel. (during high load, nothing in particular seems to cause it to happen). Did not happen with previous (4.10.0.14.16) kernel. Only after update to 4.10.0.15.17, has happened about 3 times since then (or other crashes), this is the one I could capture. kern.log entries below. Let me know if you need anything else from me. Thanks! Apr 7 11:20:28 doe kernel: [26003.796278] BUG: unable to handle kernel NULL pointer dereference at 0018 Apr 7 11:20:28 doe kernel: [26003.796375] IP: gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] Apr 7 11:20:28 doe kernel: [26003.796404] PGD 0 Apr 7 11:20:28 doe kernel: [26003.796405] Apr 7 11:20:28 doe kernel: [26003.796427] Oops: 0002 [#1] SMP Apr 7 11:20:28 doe kernel: [26003.796441] Modules linked in: xt_REDIRECT nf_nat_redirect xt_hl scsi_transport_iscsi binfmt_misc veth ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_filter ip6_tables ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_CHECKSUM xt_comment xt_tcpudp iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack libcrc32c iptable_mangle iptable_filter ccm rfcomm bridge stp llc cmac bnep zfs(PO) zunicode(PO) zavl(PO) zcommon(PO) znvpair(PO) spl(O) nls_iso8859_1 hid_multitouch joydev i2c_designware_platform i2c_designware_core snd_hda_codec_hdmi snd_soc_skl snd_soc_skl_ipc snd_soc_sst_ipc snd_soc_sst_dsp snd_hda_codec_realtek snd_hda_ext_core snd_soc_sst_match snd_hda_codec_generic snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel snd_hda_codec snd_hda_core asus_nb_wmi Apr 7 11:20:28 doe kernel: [26003.796722] snd_hwdep asus_wmi sparse_keymap snd_pcm arc4 snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device iwlmvm snd_timer mac80211 intel_rapl x86_pkg_temp_thermal snd intel_powerclamp uvcvideo coretemp kvm_intel iwlwifi videobuf2_vmalloc kvm videobuf2_memops irqbypass videobuf2_v4l2 intel_cstate videobuf2_core intel_rapl_perf cfg80211 videodev input_leds serio_raw media shpchp soundcore btusb btrtl hci_uart btbcm elan_i2c btqca btintel acpi_als int3403_thermal bluetooth kfifo_buf industrialio mac_hid idma64 mei_me virt_dma intel_pch_thermal acpi_pad int3400_thermal intel_lpss_pci int3402_thermal mei intel_lpss_acpi acpi_thermal_rel processor_thermal_device intel_lpss tpm_crb int340x_thermal_zone int3406_thermal intel_soc_dts_iosf asus_wireless parport_pc ppdev lp parport ip_tables Apr 7 11:20:28 doe kernel: [26003.797026] x_tables autofs4 algif_skcipher af_alg dm_crypt crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc i915 aesni_intel aes_x86_64 crypto_simd glue_helper cryptd i2c_algo_bit drm_kms_helper syscopyarea sysfillrect ahci sysimgblt libahci fb_sys_fops drm wmi i2c_hid hid pinctrl_sunrisepoint video pinctrl_intel fjes Apr 7 11:20:28 doe kernel: [26003.797142] CPU: 0 PID: 8418 Comm: chromium-browse Tainted: P O4.10.0-15-generic #17-Ubuntu Apr 7 11:20:28 doe kernel: [26003.797175] Hardware name: ASUSTeK COMPUTER INC. UX305CA/UX305CA, BIOS UX305CA.201 09/11/2015 Apr 7 11:20:28 doe kernel: [26003.797206] task: 9bbaa201dc00 task.stack: c25b5ea8c000 Apr 7 11:20:28 doe kernel: [26003.797250] RIP: 0010:gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] Apr 7 11:20:28 doe kernel: [26003.797279] RSP: 0018:c25b5ea8f880 EFLAGS: 00010246 Apr 7 11:20:28 doe kernel: [26003.797299] RAX: 9bba689be580 RBX: 0003 RCX: 0003 Apr 7 11:20:28 doe kernel: [26003.797325] RDX: RSI: 9bbae7c0a000 RDI: 9bbba0418000 Apr 7 11:20:28 doe kernel: [26003.797351] RBP: c25b5ea8f8d8 R08: R09: Apr 7 11:20:28 doe kernel: [26003.797378] R10: R11: 0041 R12: 9bbb5f00a000 Apr 7 11:20:28 doe kernel: [26003.797405] R13: 9bbba932bb10 R14:
[Kernel-packages] [Bug 1706380] Re: Revert 'Auto-online hotplugged memory'" patch
** Changed in: ubuntu-power-systems Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1706380 Title: Revert 'Auto-online hotplugged memory'" patch Status in The Ubuntu-power-systems project: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Zesty: Fix Released Status in linux source package in Artful: Fix Released Bug description: == Comment: #2 - Gustavo Luiz Ferreira Walbon - 2017-07-24 16:00:16 == This backport patch reverts to the previous behavior hotplug memory, and to ensure that CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE is unset in the kernel config as well. == Comment: #3 - Reza A. Arbab - 2017-07-24 16:34:45 == The patch to backport is 943db62c316c ("powerpc/pseries: Revert 'Auto-online hotplugged memory'") To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1706380/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1706141] Re: [ARM64] config EDAC_GHES=y depends on EDAC_MM_EDAC=y
** Changed in: linux (Ubuntu) Status: Incomplete => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1706141 Title: [ARM64] config EDAC_GHES=y depends on EDAC_MM_EDAC=y Status in linux package in Ubuntu: Fix Committed Status in linux source package in Zesty: New Bug description: [Impact] In configs Zesty and Artful, EDAC_MM_EDAC is set to =m, this disables EDAC_GHES. Customers using RAS on ARM64 may want this functionality. According to RAS expert at QTI. EDAC_GHES is essential for ARMv8.0 Server systems, as it enables firmware-first error handling of memory and CPU errors. Due to a lack of standard RAS architecture (or machine check architecture equivalent) on ARMv8.0 systems, APEI/GHES is the only mechanism available for reporting hardware errors (e.g. memory and CPU errors). This enables reporting of hardware errors, and also helps enable memory fault recovery mechanisms to extend the life of the system by offlining pages when recoverable uncorrected errors are encountered. Note that other ARM vendors will be going in this direction for hardware error handling. [Test] Test kernel available in https://launchpad.net/~centriq-team/+archive/ubuntu/lp1706141 Boot the kernel and check dmesg for the following: $ dmesg | grep -i -E "edac|hest|ghes" [0.00] ACPI: HEST 0x0916 000288 (v01 QCOM QDF2400 0001 INTL 20150515) [0.620278] HEST: Table parsing has been initialized. [4.178298] EDAC MC: Ver: 3.0.0 [5.664499] ghes_edac: This EDAC driver relies on BIOS to enumerate memory and get error reports. [5.673371] ghes_edac: Unfortunately, not all BIOSes reflect the memory layout correctly. [5.681542] ghes_edac: So, the end result of using this driver varies from vendor to vendor. [5.689972] ghes_edac: If you find incorrect reports, please contact your hardware vendor [5.698142] ghes_edac: to correct its BIOS. [5.702320] ghes_edac: This system has 12 DIMM sockets. [5.707717] EDAC MC0: Giving out device to module ghes_edac.c controller ghes_edac: DEV ghes (INTERRUPT) [5.717264] EDAC MC1: Giving out device to module ghes_edac.c controller ghes_edac: DEV ghes (INTERRUPT) [5.726806] EDAC MC2: Giving out device to module ghes_edac.c controller ghes_edac: DEV ghes (INTERRUPT) [5.736344] EDAC MC3: Giving out device to module ghes_edac.c controller ghes_edac: DEV ghes (INTERRUPT) [5.745883] EDAC MC4: Giving out device to module ghes_edac.c controller ghes_edac: DEV ghes (INTERRUPT) [5.755469] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC. [Fix] 1. Apply RAS patch series submitted for SRU in Bug #1696570 2. Set config option EDAC_MM_EDAC=y for ARM64, this will automatically set EDAC_GHES=y 3. Remove edac_core from debian.master/abi//arm64/generic.modules [Regression Potential] The config change is limited to ARM64 architecture, and does not impact any other architecture. Potential for regressions is low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1706141/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1704158] [NEW] snapd 2.26.8+17.10 ADT test failure with linux 4.12.0-6.7
You have been subscribed to a public bug: Testing failed on: i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/i386/s/snapd/20170712_204217_cd0b1@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/ppc64el/s/snapd/20170712_204129_cd0b1@/log.gz ** Affects: linux (Ubuntu) Importance: High Assignee: Seth Forshee (sforshee) Status: In Progress ** Tags: kernel-adt-failure -- snapd 2.26.8+17.10 ADT test failure with linux 4.12.0-6.7 https://bugs.launchpad.net/bugs/1704158 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 1706531] Re: ath10k doesn't report full RSSI information
** Changed in: linux (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1706531 Title: ath10k doesn't report full RSSI information Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: New Status in linux source package in Zesty: New Bug description: [Impact] ASA (Active Steering Antenna) requires per chain RSSI info. Intel WLAN driver has full support for per-chain RSSI information, but ath10k doesn't. [Fix] The fix is pretty simple just fills up RSSI value to the structure. [Test Case] RSSI information can be polled from userspace using NL80211 wireless stack. [Regression Potential] No any regression concern. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1706531/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1706243] Re: Stranded with ENODEV after mdadm --readonly
I built a Zesty(4.10 based) test kernel with a pick of commit 065e519e71b2c1f4. The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1706243/ Can you test this kernel and see if it resolves this bug? Thanks in advance! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1706243 Title: Stranded with ENODEV after mdadm --readonly Status in linux package in Ubuntu: Confirmed Bug description: Please backport upstream fix. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?h=v4.12.3=065e519e71b2c1f41936cce75b46b5ab34adb588 --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: trent 10668 F...m pulseaudio /dev/snd/pcmC0D0p: trent 10668 F...m pulseaudio /dev/snd/controlC0: trent 10668 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=848108cd-a607-494c-a6ea-626267ed0a12 InstallationDate: Installed on 2014-12-23 (944 days ago) InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.3) IwConfig: p11p1 no wireless extensions. lono wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 002: ID 1307:0163 Transcend Information, Inc. 256MB/512MB/1GB Flash Drive Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic root=UUID=7afb765b-b26b-44cc-ace1-654320cd85b2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17 RelatedPackageVersions: linux-restricted-modules-4.10.0-26-generic N/A linux-backports-modules-4.10.0-26-generic N/A linux-firmware 1.157.11 RfKill: Tags: xenial xenial Uname: Linux 4.10.0-26-generic x86_64 UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: Upgraded to xenial on 2017-07-01 (24 days ago) UserGroups: adm audio cdrom dip glftpd lpadmin plugdev sambashare sudo _MarkForUpload: False dmi.bios.date: 06/16/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0808 dmi.board.asset.tag: Default string dmi.board.name: PRIME B250M-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0808:bd06/16/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB250M-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1706243/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1705378] Re: ideapad_laptop don't support v310-14isk
** Also affects: linux (Ubuntu Zesty) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1705378 Title: ideapad_laptop don't support v310-14isk Status in HWE Next: New Status in Linux: Incomplete Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: New Status in linux source package in Zesty: New Bug description: we found the wireless and bluetooth can't work, the device had driver already, just wereo blocked by ideapad_laptop module. After remove it, it works fine. $ sudo rfkill list 0: ideapad_wlan: Wireless LAN Soft blocked: no Hard blocked: yes 1: ideapad_bluetooth: Bluetooth Soft blocked: no Hard blocked: yes 2: hci0: Bluetooth Soft blocked: no Hard blocked: no 3: phy0: Wireless LAN Soft blocked: no Hard blocked: no SRU Justification = [Impact] wireless and bluetooth were blocked by ideapad_laptop module. [Fix] Fix it by adding those models to no_hw_rfkill_list. [Test Case] Wireless and BT works fine. [Regression Potential] This patch add several dmi entry in struct. Regression Potential is low. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1705378/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1690174] Re: [Hyper-V] hv_netvsc: Exclude non-TCP port numbers from vRSS hashing
** Changed in: linux (Ubuntu Artful) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1690174 Title: [Hyper-V] hv_netvsc: Exclude non-TCP port numbers from vRSS hashing Status in linux package in Ubuntu: Fix Committed Status in linux-azure package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux-azure source package in Xenial: In Progress Status in linux source package in Yakkety: Won't Fix Status in linux source package in Zesty: In Progress Status in linux source package in Artful: Fix Committed Bug description: Azure hosts are not supporting non-TCP port numbers in vRSS hashing for now. For example, UDP packet loss rate will be high if port numbers are also included in vRSS hash. So, we created this patch to use only IP numbers for hashing in non-TCP traffic. https://git.kernel.org/pub/scm/linux/kernel/git/next/linux- next.git/commit/?id=f72860afa2e32cdc674cbdd7f354f8fb62e908a6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1690174/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1275161] Re: Realtek driver r8169 slow network speed
Is the dirver r8169 bug still persisting? On the realtek site the solution is to run the script: 'autorun.sh' and switch to the r8168 driver. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1275161 Title: Realtek driver r8169 slow network speed Status in linux package in Ubuntu: Opinion Status in linux package in Gentoo Linux: New Bug description: Network speed variable, some sites not open or very slow (example: amazon.com). Replace driver with r8168 from this http://www.realtek.com/downloads/downloadsView.aspx?Langid=1=5=5=5=4=3=false#2 not help. ubuntu amd64 13.10 (also tested daily build 14.04 30 Jan 2014) kernel 3.11.0-15-generic lspci -nn | grep Ethernet 02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 0c) --- ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dem1250 F pulseaudio /dev/snd/controlC1: dem1250 F pulseaudio /dev/snd/pcmC1D0c: dem1250 F...m pulseaudio /dev/snd/pcmC1D0p: dem1250 F...m pulseaudio CRDA: Error: [Errno 2] No such file or directory CurrentDmesg: [ 712.730809] hda-intel :00:1b.0: Unstable LPIB (19200 >= 1920); disabling LPIB delay counting DistroRelease: Ubuntu 13.10 IwConfig: Error: [Errno 2] No such file or directory MachineType: MSI MS-7817 MarkForUpload: True Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic root=UUID=2982e0ae-6485-4894-9306-01c72c340d13 ro ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10 RelatedPackageVersions: linux-restricted-modules-3.11.0-15-generic N/A linux-backports-modules-3.11.0-15-generic N/A linux-firmware 1.116 RfKill: Error: [Errno 2] No such file or directory Tags: saucy Uname: Linux 3.11.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo video dmi.bios.date: 06/20/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-P33 (MS-7817) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.0:bd06/20/2013:svnMSI:pnMS-7817:pvr1.0:rvnMSI:rnH81M-P33(MS-7817):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7817 dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1275161/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1706243] Re: Stranded with ENODEV after mdadm --readonly
Confirmed working! Thanks for the quick response! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1706243 Title: Stranded with ENODEV after mdadm --readonly Status in linux package in Ubuntu: Confirmed Bug description: Please backport upstream fix. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?h=v4.12.3=065e519e71b2c1f41936cce75b46b5ab34adb588 --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: trent 10668 F...m pulseaudio /dev/snd/pcmC0D0p: trent 10668 F...m pulseaudio /dev/snd/controlC0: trent 10668 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=848108cd-a607-494c-a6ea-626267ed0a12 InstallationDate: Installed on 2014-12-23 (944 days ago) InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.3) IwConfig: p11p1 no wireless extensions. lono wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 002: ID 1307:0163 Transcend Information, Inc. 256MB/512MB/1GB Flash Drive Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic root=UUID=7afb765b-b26b-44cc-ace1-654320cd85b2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17 RelatedPackageVersions: linux-restricted-modules-4.10.0-26-generic N/A linux-backports-modules-4.10.0-26-generic N/A linux-firmware 1.157.11 RfKill: Tags: xenial xenial Uname: Linux 4.10.0-26-generic x86_64 UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: Upgraded to xenial on 2017-07-01 (24 days ago) UserGroups: adm audio cdrom dip glftpd lpadmin plugdev sambashare sudo _MarkForUpload: False dmi.bios.date: 06/16/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0808 dmi.board.asset.tag: Default string dmi.board.name: PRIME B250M-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0808:bd06/16/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB250M-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1706243/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1705054] Update Released
The verification of the Stable Release Update for kexec-tools has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/1705054 Title: Trusty kexec-tools suffer from upstream code regression. Fix not included. Status in kexec-tools package in Ubuntu: Fix Released Status in kexec-tools source package in Trusty: Fix Released Bug description: [Impact] * kdump doesn't work on non-efi systems * a kernel dump can't be generated [Test Case] * install kdump-tools * configure kdump-tools (/etc/default/kdump-tools) * try to start kdump-tools service (kdump-config start) * while executing kexec, you will get: "efi memory descriptor version 0 is not supported!" [Regression Potential] * in theory it could brake kdump for efi systems * in practice, its based on upstream regression fix (not included in Trusty) * it has also been tested in 3 different setups and it worked [Other Info] Based on upstream code commit explanation: """ On non-EFI systems, efi_info section of boot_params is zero filled resulting in an erroneous message from kexec regarding "efi memory descriptor" version. Caused by commit: e1ffc9e9a0769e1f54185003102e9bec428b84e8 "Passing efi related data via setup_data" # od -j 448 -N 32 -v -x /sys/kernel/boot_params/data 700 720 740 # kexec -l --reuse-cmdline --initrd=/boot/initrd-`uname -r` /boot/vmlinuz-`uname -r` efi memory descriptor version 0 is not supported! """ It was brought to my attention to some of our users are facing this: ## TRUSTY with kernel 4.4.0-83-generic # /usr/sbin/kdump-config load efi memory descriptor version 0 is not supported! * loaded kdump kernel /var/log/syslog: Jul 18 13:37:06 kdump-config: /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-4.4.0-83-generic root=UUID=-20e4-4325-ad92-7aef2af0beac ro KDUMP_CMDLINE_APPEND=irqpoll maxcpus=1 nousb irqpoll maxcpus=1 nousb" --initrd=/boot/initrd.img-4.4.0-83-generic /boot/vmlinuz-4.4.0-83-generic Jul 18 13:37:06 kdump-config: loaded kdump kernel Despite the message of kdump being loaded, it doesn't look that it is operational. Dump files could be generated using Xenial kdump-tools, but not Trusty's. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1705054/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1705054] Re: Trusty kexec-tools suffer from upstream code regression. Fix not included.
This bug was fixed in the package kexec-tools - 1:2.0.6-0ubuntu2.3 --- kexec-tools (1:2.0.6-0ubuntu2.3) trusty; urgency=medium * Fixes non-efi systems, upstream code regression not present (LP: #1705054) -- Rafael David TinocoTue, 18 Jul 2017 15:11:24 + ** Changed in: kexec-tools (Ubuntu Trusty) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/1705054 Title: Trusty kexec-tools suffer from upstream code regression. Fix not included. Status in kexec-tools package in Ubuntu: Fix Released Status in kexec-tools source package in Trusty: Fix Released Bug description: [Impact] * kdump doesn't work on non-efi systems * a kernel dump can't be generated [Test Case] * install kdump-tools * configure kdump-tools (/etc/default/kdump-tools) * try to start kdump-tools service (kdump-config start) * while executing kexec, you will get: "efi memory descriptor version 0 is not supported!" [Regression Potential] * in theory it could brake kdump for efi systems * in practice, its based on upstream regression fix (not included in Trusty) * it has also been tested in 3 different setups and it worked [Other Info] Based on upstream code commit explanation: """ On non-EFI systems, efi_info section of boot_params is zero filled resulting in an erroneous message from kexec regarding "efi memory descriptor" version. Caused by commit: e1ffc9e9a0769e1f54185003102e9bec428b84e8 "Passing efi related data via setup_data" # od -j 448 -N 32 -v -x /sys/kernel/boot_params/data 700 720 740 # kexec -l --reuse-cmdline --initrd=/boot/initrd-`uname -r` /boot/vmlinuz-`uname -r` efi memory descriptor version 0 is not supported! """ It was brought to my attention to some of our users are facing this: ## TRUSTY with kernel 4.4.0-83-generic # /usr/sbin/kdump-config load efi memory descriptor version 0 is not supported! * loaded kdump kernel /var/log/syslog: Jul 18 13:37:06 kdump-config: /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-4.4.0-83-generic root=UUID=-20e4-4325-ad92-7aef2af0beac ro KDUMP_CMDLINE_APPEND=irqpoll maxcpus=1 nousb irqpoll maxcpus=1 nousb" --initrd=/boot/initrd.img-4.4.0-83-generic /boot/vmlinuz-4.4.0-83-generic Jul 18 13:37:06 kdump-config: loaded kdump kernel Despite the message of kdump being loaded, it doesn't look that it is operational. Dump files could be generated using Xenial kdump-tools, but not Trusty's. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1705054/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1707111] Re: Hardware clock isn't updated anymore
Unfortunately apport-collect does now start Firefox with a new profile to request the authentication which makes it actually tricky to authenticate it. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1707111 Title: Hardware clock isn't updated anymore Status in linux package in Ubuntu: Confirmed Bug description: For some months I'm noticing that my hardware clock doesn't get updated anymore while the software clock successfully updates ("ntpd -q" runs every hour). This appears on my laptop (kernel version 4.11.10) and my PC (kernel version 4.8.17). Could it be that the 11 minute mode was enabled in past kernel versions but not anymore in recent kernel versions? --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.8.0-48-generic. ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Card hw:0 'SB'/'HDA ATI SB at 0xfcff4000 irq 16' Mixer name : 'Realtek ALC662 rev1' Components : 'HDA:10ec0662,18497662,00100101' Controls : 37 Simple ctrls : 19 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xfe97c000 irq 19' Mixer name : 'Nvidia GPU 42 HDMI/DP' Components : 'HDA:10de0042,14583555,00100100' Controls : 21 Simple ctrls : 3 CurrentDesktop: LXDE DistroRelease: Ubuntu 17.10 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=23b2ee46-5930-41bc-a3e5-33800a236db2 IwConfig: Error: [Errno 2] No such file or directory JournalErrors: No journal files were found. -- No entries -- Lsusb: Error: [Errno 2] No such file or directory MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-48-generic root=UUID=05338ff8-a226-421b-90a4-1dd45199f783 ro elevator=cfq ProcVersionSignature: Ubuntu 4.8.0-48.51-generic 4.8.17 RelatedPackageVersions: linux-restricted-modules-4.8.0-48-generic N/A linux-backports-modules-4.8.0-48-generic N/A linux-firmware1.167 RfKill: Error: [Errno 2] No such file or directory Tags: artful Uname: Linux 4.8.0-48-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark WifiSyslog: _MarkForUpload: True dmi.bios.date: 07/23/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.50 dmi.board.name: 960GM/U3S3 FX dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd07/23/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn960GM/U3S3FX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1707111/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1707111] Re: Hardware clock isn't updated anymore
apport information ** Tags added: apport-collected artful ** Description changed: - For some months I'm noticing that my hardware clock doesn't get updated - anymore while the software clock successfully updates ("ntpd -q" runs - every hour). This appears on my laptop (kernel version 4.11.10) and my - PC (kernel version 4.8.17). Could it be that the 11 minute mode was - enabled in past kernel versions but not anymore in recent kernel - versions? + For some months I'm noticing that my hardware clock doesn't get updated anymore while the software clock successfully updates ("ntpd -q" runs every hour). This appears on my laptop (kernel version 4.11.10) and my PC (kernel version 4.8.17). Could it be that the 11 minute mode was enabled in past kernel versions but not anymore in recent kernel versions? + --- + AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.8.0-48-generic. + ApportVersion: 2.20.6-0ubuntu4 + Architecture: amd64 + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + Card0.Amixer.info: + Card hw:0 'SB'/'HDA ATI SB at 0xfcff4000 irq 16' +Mixer name : 'Realtek ALC662 rev1' +Components : 'HDA:10ec0662,18497662,00100101' +Controls : 37 +Simple ctrls : 19 + Card1.Amixer.info: + Card hw:1 'NVidia'/'HDA NVidia at 0xfe97c000 irq 19' +Mixer name : 'Nvidia GPU 42 HDMI/DP' +Components : 'HDA:10de0042,14583555,00100100' +Controls : 21 +Simple ctrls : 3 + CurrentDesktop: LXDE + DistroRelease: Ubuntu 17.10 + EcryptfsInUse: Yes + HibernationDevice: RESUME=UUID=23b2ee46-5930-41bc-a3e5-33800a236db2 + IwConfig: Error: [Errno 2] No such file or directory + JournalErrors: + No journal files were found. + -- No entries -- + Lsusb: Error: [Errno 2] No such file or directory + MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. + NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia + Package: linux (not installed) + ProcEnviron: + TERM=xterm + PATH=(custom, no user) + LANG=de_DE.UTF-8 + SHELL=/bin/bash + ProcFB: 0 VESA VGA + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-48-generic root=UUID=05338ff8-a226-421b-90a4-1dd45199f783 ro elevator=cfq + ProcVersionSignature: Ubuntu 4.8.0-48.51-generic 4.8.17 + RelatedPackageVersions: + linux-restricted-modules-4.8.0-48-generic N/A + linux-backports-modules-4.8.0-48-generic N/A + linux-firmware1.167 + RfKill: Error: [Errno 2] No such file or directory + Tags: artful + Uname: Linux 4.8.0-48-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark + WifiSyslog: + + _MarkForUpload: True + dmi.bios.date: 07/23/2015 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: P1.50 + dmi.board.name: 960GM/U3S3 FX + dmi.board.vendor: ASRock + dmi.chassis.asset.tag: To Be Filled By O.E.M. + dmi.chassis.type: 3 + dmi.chassis.vendor: To Be Filled By O.E.M. + dmi.chassis.version: To Be Filled By O.E.M. + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd07/23/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn960GM/U3S3FX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: + dmi.product.name: To Be Filled By O.E.M. + dmi.product.version: To Be Filled By O.E.M. + dmi.sys.vendor: To Be Filled By O.E.M. ** Attachment added: "AlsaDevices.txt" https://bugs.launchpad.net/bugs/1707111/+attachment/4922777/+files/AlsaDevices.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/1707111 Title: Hardware clock isn't updated anymore Status in linux package in Ubuntu: Confirmed Bug description: For some months I'm noticing that my hardware clock doesn't get updated anymore while the software clock successfully updates ("ntpd -q" runs every hour). This appears on my laptop (kernel version 4.11.10) and my PC (kernel version 4.8.17). Could it be that the 11 minute mode was enabled in past kernel versions but not anymore in recent kernel versions? --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.8.0-48-generic. ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Card hw:0 'SB'/'HDA ATI SB at 0xfcff4000 irq 16' Mixer name :
[Kernel-packages] [Bug 1707111] Card1.Amixer.values.txt
apport information ** Attachment added: "Card1.Amixer.values.txt" https://bugs.launchpad.net/bugs/1707111/+attachment/4922783/+files/Card1.Amixer.values.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/1707111 Title: Hardware clock isn't updated anymore Status in linux package in Ubuntu: Confirmed Bug description: For some months I'm noticing that my hardware clock doesn't get updated anymore while the software clock successfully updates ("ntpd -q" runs every hour). This appears on my laptop (kernel version 4.11.10) and my PC (kernel version 4.8.17). Could it be that the 11 minute mode was enabled in past kernel versions but not anymore in recent kernel versions? --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.8.0-48-generic. ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Card hw:0 'SB'/'HDA ATI SB at 0xfcff4000 irq 16' Mixer name : 'Realtek ALC662 rev1' Components : 'HDA:10ec0662,18497662,00100101' Controls : 37 Simple ctrls : 19 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xfe97c000 irq 19' Mixer name : 'Nvidia GPU 42 HDMI/DP' Components : 'HDA:10de0042,14583555,00100100' Controls : 21 Simple ctrls : 3 CurrentDesktop: LXDE DistroRelease: Ubuntu 17.10 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=23b2ee46-5930-41bc-a3e5-33800a236db2 IwConfig: Error: [Errno 2] No such file or directory JournalErrors: No journal files were found. -- No entries -- Lsusb: Error: [Errno 2] No such file or directory MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-48-generic root=UUID=05338ff8-a226-421b-90a4-1dd45199f783 ro elevator=cfq ProcVersionSignature: Ubuntu 4.8.0-48.51-generic 4.8.17 RelatedPackageVersions: linux-restricted-modules-4.8.0-48-generic N/A linux-backports-modules-4.8.0-48-generic N/A linux-firmware1.167 RfKill: Error: [Errno 2] No such file or directory Tags: artful Uname: Linux 4.8.0-48-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark WifiSyslog: _MarkForUpload: True dmi.bios.date: 07/23/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.50 dmi.board.name: 960GM/U3S3 FX dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd07/23/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn960GM/U3S3FX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1707111/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1707118] Re: bluetoothd crashed with SIGSEGV in match_disconn_id() from queue_remove_if() from bt_att_unregister_disconnect() from attio_cleanup() from browse_request_cancel()
*** This bug is a duplicate of bug 1689451 *** https://bugs.launchpad.net/bugs/1689451 In progress (this bug is fixed in v5.46 by ded317e9c2848e16e0616b961df2b3dc4e836c6e) ** Summary changed: - /usr/lib/bluetooth/bluetoothd:11:match_disconn_id:queue_remove_if:bt_att_unregister_disconnect:attio_cleanup:browse_request_cancel + bluetoothd crashed with SIGSEGV in match_disconn_id() from queue_remove_if() from bt_att_unregister_disconnect() from attio_cleanup() from browse_request_cancel() ** Changed in: bluez (Ubuntu) Assignee: (unassigned) => Konrad Zapałowicz (kzapalowicz) ** Changed in: bluez (Ubuntu) Importance: Undecided => Medium ** Changed in: bluez (Ubuntu) Status: New => In Progress ** This bug has been marked a duplicate of bug 1689451 bluetoothd crashed with SIGSEGV in queue_remove_if from bt_att_unregister_disconnect from attio_cleanup from browse_request_cancel from device_remove -- 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/1707118 Title: bluetoothd crashed with SIGSEGV in match_disconn_id() from queue_remove_if() from bt_att_unregister_disconnect() from attio_cleanup() from browse_request_cancel() Status in bluez package in Ubuntu: In Progress Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.41-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/b86e972703b50f75c651ff912f65b7e88af9c592 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1707118/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1689451] Re: bluetoothd crashed with SIGSEGV in queue_remove_if from bt_att_unregister_disconnect from attio_cleanup from browse_request_cancel from device_remove
In progress (this bug is fixed in v5.46 by ded317e9c2848e16e0616b961df2b3dc4e836c6e) ** Changed in: bluez (Ubuntu) Status: Confirmed => In Progress ** Changed in: bluez (Ubuntu) Assignee: (unassigned) => Konrad Zapałowicz (kzapalowicz) -- 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/1689451 Title: bluetoothd crashed with SIGSEGV in queue_remove_if from bt_att_unregister_disconnect from attio_cleanup from browse_request_cancel from device_remove Status in bluez package in Ubuntu: In Progress Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.41-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/686eb99935548ae15300b85caf382f510d0c074f contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689451/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1705003] Re: linux: 3.19.0-89.97 -proposed tracker
** Tags added: kernel-block-proposed ** Changed in: kernel-sru-workflow/promote-to-security Status: Confirmed => New ** Changed in: kernel-sru-workflow/promote-to-updates Status: Confirmed => 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/1705003 Title: linux: 3.19.0-89.97 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released 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: Invalid 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: Fix Released Status in linux package in Ubuntu: Confirmed Status in linux source package in Vivid: 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 backports: 1705004 derivatives: -- swm properties -- boot-testing-requested: true 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/1705003/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1707111] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1707111/+attachment/4922788/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1707111 Title: Hardware clock isn't updated anymore Status in linux package in Ubuntu: Confirmed Bug description: For some months I'm noticing that my hardware clock doesn't get updated anymore while the software clock successfully updates ("ntpd -q" runs every hour). This appears on my laptop (kernel version 4.11.10) and my PC (kernel version 4.8.17). Could it be that the 11 minute mode was enabled in past kernel versions but not anymore in recent kernel versions? --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.8.0-48-generic. ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Card hw:0 'SB'/'HDA ATI SB at 0xfcff4000 irq 16' Mixer name : 'Realtek ALC662 rev1' Components : 'HDA:10ec0662,18497662,00100101' Controls : 37 Simple ctrls : 19 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xfe97c000 irq 19' Mixer name : 'Nvidia GPU 42 HDMI/DP' Components : 'HDA:10de0042,14583555,00100100' Controls : 21 Simple ctrls : 3 CurrentDesktop: LXDE DistroRelease: Ubuntu 17.10 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=23b2ee46-5930-41bc-a3e5-33800a236db2 IwConfig: Error: [Errno 2] No such file or directory JournalErrors: No journal files were found. -- No entries -- Lsusb: Error: [Errno 2] No such file or directory MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-48-generic root=UUID=05338ff8-a226-421b-90a4-1dd45199f783 ro elevator=cfq ProcVersionSignature: Ubuntu 4.8.0-48.51-generic 4.8.17 RelatedPackageVersions: linux-restricted-modules-4.8.0-48-generic N/A linux-backports-modules-4.8.0-48-generic N/A linux-firmware1.167 RfKill: Error: [Errno 2] No such file or directory Tags: artful Uname: Linux 4.8.0-48-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark WifiSyslog: _MarkForUpload: True dmi.bios.date: 07/23/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.50 dmi.board.name: 960GM/U3S3 FX dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd07/23/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn960GM/U3S3FX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1707111/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1707111] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1707111/+attachment/4922780/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1707111 Title: Hardware clock isn't updated anymore Status in linux package in Ubuntu: Confirmed Bug description: For some months I'm noticing that my hardware clock doesn't get updated anymore while the software clock successfully updates ("ntpd -q" runs every hour). This appears on my laptop (kernel version 4.11.10) and my PC (kernel version 4.8.17). Could it be that the 11 minute mode was enabled in past kernel versions but not anymore in recent kernel versions? --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.8.0-48-generic. ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Card hw:0 'SB'/'HDA ATI SB at 0xfcff4000 irq 16' Mixer name : 'Realtek ALC662 rev1' Components : 'HDA:10ec0662,18497662,00100101' Controls : 37 Simple ctrls : 19 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xfe97c000 irq 19' Mixer name : 'Nvidia GPU 42 HDMI/DP' Components : 'HDA:10de0042,14583555,00100100' Controls : 21 Simple ctrls : 3 CurrentDesktop: LXDE DistroRelease: Ubuntu 17.10 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=23b2ee46-5930-41bc-a3e5-33800a236db2 IwConfig: Error: [Errno 2] No such file or directory JournalErrors: No journal files were found. -- No entries -- Lsusb: Error: [Errno 2] No such file or directory MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-48-generic root=UUID=05338ff8-a226-421b-90a4-1dd45199f783 ro elevator=cfq ProcVersionSignature: Ubuntu 4.8.0-48.51-generic 4.8.17 RelatedPackageVersions: linux-restricted-modules-4.8.0-48-generic N/A linux-backports-modules-4.8.0-48-generic N/A linux-firmware1.167 RfKill: Error: [Errno 2] No such file or directory Tags: artful Uname: Linux 4.8.0-48-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark WifiSyslog: _MarkForUpload: True dmi.bios.date: 07/23/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.50 dmi.board.name: 960GM/U3S3 FX dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd07/23/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn960GM/U3S3FX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1707111/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1707111] AplayDevices.txt
apport information ** Attachment added: "AplayDevices.txt" https://bugs.launchpad.net/bugs/1707111/+attachment/4922778/+files/AplayDevices.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/1707111 Title: Hardware clock isn't updated anymore Status in linux package in Ubuntu: Confirmed Bug description: For some months I'm noticing that my hardware clock doesn't get updated anymore while the software clock successfully updates ("ntpd -q" runs every hour). This appears on my laptop (kernel version 4.11.10) and my PC (kernel version 4.8.17). Could it be that the 11 minute mode was enabled in past kernel versions but not anymore in recent kernel versions? --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.8.0-48-generic. ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Card hw:0 'SB'/'HDA ATI SB at 0xfcff4000 irq 16' Mixer name : 'Realtek ALC662 rev1' Components : 'HDA:10ec0662,18497662,00100101' Controls : 37 Simple ctrls : 19 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xfe97c000 irq 19' Mixer name : 'Nvidia GPU 42 HDMI/DP' Components : 'HDA:10de0042,14583555,00100100' Controls : 21 Simple ctrls : 3 CurrentDesktop: LXDE DistroRelease: Ubuntu 17.10 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=23b2ee46-5930-41bc-a3e5-33800a236db2 IwConfig: Error: [Errno 2] No such file or directory JournalErrors: No journal files were found. -- No entries -- Lsusb: Error: [Errno 2] No such file or directory MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-48-generic root=UUID=05338ff8-a226-421b-90a4-1dd45199f783 ro elevator=cfq ProcVersionSignature: Ubuntu 4.8.0-48.51-generic 4.8.17 RelatedPackageVersions: linux-restricted-modules-4.8.0-48-generic N/A linux-backports-modules-4.8.0-48-generic N/A linux-firmware1.167 RfKill: Error: [Errno 2] No such file or directory Tags: artful Uname: Linux 4.8.0-48-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark WifiSyslog: _MarkForUpload: True dmi.bios.date: 07/23/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.50 dmi.board.name: 960GM/U3S3 FX dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd07/23/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn960GM/U3S3FX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1707111/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1707111] PciMultimedia.txt
apport information ** Attachment added: "PciMultimedia.txt" https://bugs.launchpad.net/bugs/1707111/+attachment/4922787/+files/PciMultimedia.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/1707111 Title: Hardware clock isn't updated anymore Status in linux package in Ubuntu: Confirmed Bug description: For some months I'm noticing that my hardware clock doesn't get updated anymore while the software clock successfully updates ("ntpd -q" runs every hour). This appears on my laptop (kernel version 4.11.10) and my PC (kernel version 4.8.17). Could it be that the 11 minute mode was enabled in past kernel versions but not anymore in recent kernel versions? --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.8.0-48-generic. ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Card hw:0 'SB'/'HDA ATI SB at 0xfcff4000 irq 16' Mixer name : 'Realtek ALC662 rev1' Components : 'HDA:10ec0662,18497662,00100101' Controls : 37 Simple ctrls : 19 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xfe97c000 irq 19' Mixer name : 'Nvidia GPU 42 HDMI/DP' Components : 'HDA:10de0042,14583555,00100100' Controls : 21 Simple ctrls : 3 CurrentDesktop: LXDE DistroRelease: Ubuntu 17.10 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=23b2ee46-5930-41bc-a3e5-33800a236db2 IwConfig: Error: [Errno 2] No such file or directory JournalErrors: No journal files were found. -- No entries -- Lsusb: Error: [Errno 2] No such file or directory MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-48-generic root=UUID=05338ff8-a226-421b-90a4-1dd45199f783 ro elevator=cfq ProcVersionSignature: Ubuntu 4.8.0-48.51-generic 4.8.17 RelatedPackageVersions: linux-restricted-modules-4.8.0-48-generic N/A linux-backports-modules-4.8.0-48-generic N/A linux-firmware1.167 RfKill: Error: [Errno 2] No such file or directory Tags: artful Uname: Linux 4.8.0-48-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark WifiSyslog: _MarkForUpload: True dmi.bios.date: 07/23/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.50 dmi.board.name: 960GM/U3S3 FX dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd07/23/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn960GM/U3S3FX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1707111/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1707111] Card0.Codecs.codec.0.txt
apport information ** Attachment added: "Card0.Codecs.codec.0.txt" https://bugs.launchpad.net/bugs/1707111/+attachment/4922782/+files/Card0.Codecs.codec.0.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/1707111 Title: Hardware clock isn't updated anymore Status in linux package in Ubuntu: Confirmed Bug description: For some months I'm noticing that my hardware clock doesn't get updated anymore while the software clock successfully updates ("ntpd -q" runs every hour). This appears on my laptop (kernel version 4.11.10) and my PC (kernel version 4.8.17). Could it be that the 11 minute mode was enabled in past kernel versions but not anymore in recent kernel versions? --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.8.0-48-generic. ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Card hw:0 'SB'/'HDA ATI SB at 0xfcff4000 irq 16' Mixer name : 'Realtek ALC662 rev1' Components : 'HDA:10ec0662,18497662,00100101' Controls : 37 Simple ctrls : 19 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xfe97c000 irq 19' Mixer name : 'Nvidia GPU 42 HDMI/DP' Components : 'HDA:10de0042,14583555,00100100' Controls : 21 Simple ctrls : 3 CurrentDesktop: LXDE DistroRelease: Ubuntu 17.10 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=23b2ee46-5930-41bc-a3e5-33800a236db2 IwConfig: Error: [Errno 2] No such file or directory JournalErrors: No journal files were found. -- No entries -- Lsusb: Error: [Errno 2] No such file or directory MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-48-generic root=UUID=05338ff8-a226-421b-90a4-1dd45199f783 ro elevator=cfq ProcVersionSignature: Ubuntu 4.8.0-48.51-generic 4.8.17 RelatedPackageVersions: linux-restricted-modules-4.8.0-48-generic N/A linux-backports-modules-4.8.0-48-generic N/A linux-firmware1.167 RfKill: Error: [Errno 2] No such file or directory Tags: artful Uname: Linux 4.8.0-48-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark WifiSyslog: _MarkForUpload: True dmi.bios.date: 07/23/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.50 dmi.board.name: 960GM/U3S3 FX dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd07/23/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn960GM/U3S3FX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1707111/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp