[Kernel-packages] [Bug 1618600] Re: Unclaimed register detected after reading register 0x65f10
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1618600 Title: Unclaimed register detected after reading register 0x65f10 Status in linux package in Ubuntu: Expired Bug description: [ 215.297470] [ cut here ] [ 215.297522] WARNING: CPU: 0 PID: 1673 at /build/linux-rTsl6N/linux-4.4.0/ubuntu/i915/intel_uncore.c:804 __unclaimed_reg_debug+0x6b/0x80 [i915_bpo]() [ 215.297525] Unclaimed register detected after reading register 0x65f10 [ 215.297527] Modules linked in: nvram msr rfcomm cmac bnep uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core v4l2_common btusb videodev btrtl media snd_hda_codec_hdmi dell_led snd_hda_codec_realtek snd_hda_codec_generic hid_multitouch i2c_designware_platform dell_laptop i2c_designware_core dcdbas dell_wmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp nls_iso8859_1 kvm_intel kvm irqbypass snd_soc_skl snd_soc_skl_ipc snd_hda_ext_core crct10dif_pclmul snd_soc_sst_ipc crc32_pclmul snd_soc_sst_dsp snd_soc_core brcmfmac snd_compress ac97_bus snd_pcm_dmaengine dw_dmac_core snd_hda_intel brcmutil cfg80211 snd_hda_codec rtsx_pci_ms snd_hda_core memstick snd_hwdep aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper snd_pcm cryptd snd_seq_midi snd_seq_midi_event snd_rawmidi [ 215.297587] input_leds snd_seq snd_seq_device snd_timer serio_raw snd soundcore shpchp mei_me idma64 mei virt_dma intel_lpss_pci processor_thermal_device intel_soc_dts_iosf hci_uart btbcm btqca btintel bluetooth intel_lpss_acpi intel_lpss acpi_pad int3403_thermal int340x_thermal_zone int3400_thermal acpi_thermal_rel intel_hid sparse_keymap acpi_als kfifo_buf industrialio joydev mac_hid parport_pc ppdev lp parport ip_tables x_tables autofs4 rtsx_pci_sdmmc i915_bpo intel_ips i2c_algo_bit psmouse drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops nvme drm rtsx_pci ahci libahci wmi i2c_hid hid pinctrl_sunrisepoint video pinctrl_intel fjes [ 215.297642] CPU: 0 PID: 1673 Comm: alsa-source-ALC Not tainted 4.4.0-9136-generic #55-Ubuntu [ 215.297645] Hardware name: Dell Inc. XPS 13 9350/0RH0V2, BIOS 1.4.4 06/14/2016 [ 215.297648] 0086 e4fd464c 880060e23778 813f13e3 [ 215.297652] 880060e237c0 c02a17b8 880060e237b0 810810f2 [ 215.297657] 00065f10 0001 88026eba [ 215.297661] Call Trace: [ 215.297670] [] dump_stack+0x63/0x90 [ 215.297676] [] warn_slowpath_common+0x82/0xc0 [ 215.297680] [] warn_slowpath_fmt+0x5c/0x80 [ 215.297722] [] __unclaimed_reg_debug+0x6b/0x80 [i915_bpo] [ 215.297760] [] gen9_read32+0x373/0x3a0 [i915_bpo] [ 215.297799] [] i915_audio_component_codec_wake_override+0x39/0xb0 [i915_bpo] [ 215.297810] [] snd_hdac_set_codec_wakeup+0x3f/0xa0 [snd_hda_core] [ 215.297815] [] azx_runtime_resume+0x187/0x1b0 [snd_hda_intel] [ 215.297821] [] pci_pm_runtime_resume+0x7b/0xa0 [ 215.297827] [] __rpm_callback+0x33/0x70 [ 215.297831] [] ? pci_restore_standard_config+0x40/0x40 [ 215.297836] [] rpm_callback+0x24/0x80 [ 215.297840] [] ? pci_restore_standard_config+0x40/0x40 [ 215.297844] [] rpm_resume+0x497/0x6a0 [ 215.297849] [] rpm_resume+0x2e1/0x6a0 [ 215.297854] [] __pm_runtime_resume+0x4e/0x70 [ 215.297862] [] snd_hdac_power_up+0x13/0x20 [snd_hda_core] [ 215.297876] [] azx_pcm_open+0x1d2/0x370 [snd_hda_codec] [ 215.297886] [] snd_pcm_open_substream+0x7b/0x130 [snd_pcm] [ 215.297895] [] snd_pcm_open+0xb7/0x240 [snd_pcm] [ 215.297900] [] ? kmem_cache_alloc_trace+0x183/0x1f0 [ 215.297905] [] ? ttwu_do_wakeup+0x19/0xe0 [ 215.297908] [] ? wake_up_q+0x70/0x70 [ 215.297916] [] snd_pcm_capture_open+0x47/0x70 [snd_pcm] [ 215.297924] [] snd_open+0xb1/0x180 [snd] [ 215.297930] [] chrdev_open+0xbf/0x1b0 [ 215.297934] [] do_dentry_open+0x1ff/0x310 [ 215.297938] [] ? cdev_put+0x30/0x30 [ 215.297942] [] vfs_open+0x54/0x80 [ 215.297946] [] ? may_open+0x5b/0xf0 [ 215.297951] [] path_openat+0x1b7/0x1330 [ 215.297956] [] ? inotify_handle_event+0xba/0x160 [ 215.297962] [] do_filp_open+0x91/0x100 [ 215.297966] [] ? dput+0xb3/0x220 [ 215.297970] [] ? __alloc_fd+0x46/0x190 [ 215.297975] [] do_sys_open+0x138/0x2a0 [ 215.297979] [] SyS_open+0x1e/0x20 [ 215.297983] [] entry_SYSCALL_64_fastpath+0x16/0x71 [ 215.297987] ---[ end trace 9dec7bbe5062d261 ]--- ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.4.0-9136-generic 4.4.0-9136.55 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture
[Kernel-packages] [Bug 1624339] Re: Elantech v4 trackpad no longer working after resuming for hibernate
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1624339 Title: Elantech v4 trackpad no longer working after resuming for hibernate Status in linux package in Ubuntu: Expired Bug description: This is a Gigabyte AERO 14 laptop (http://www.gigabyte.com.au/products /product-page.aspx?pid=5902#kf) When laptop goes into hibernate mode, the trackpad will no longer work. Rebooting will not make the trackpad work again. The only work around I've found so far is to reboot into windows and then reboot into ubuntu. It is similar to bug 1490130; however here it's with hibernating and can't be recovered with rebooting (additionally, the kernel patch provided there doesn't work) Suspend works just fine. *** before hibernate I: Bus=0011 Vendor=0001 Product=0001 Version=ab83 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input0 U: Uniq= H: Handlers=sysrq kbd leds event0 B: PROP=0 B: EV=120013 B: KEY=40200 3803078f800d001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:18/PNP0C09:01/PNP0C0D:00/input/input2 U: Uniq= H: Handlers=event1 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0003 Version= N: Name="Sleep Button" P: Phys=PNP0C0E/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:18/PNP0C09:01/PNP0C0E:00/input/input3 U: Uniq= H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=4000 0 0 I: Bus=0019 Vendor= Product=0003 Version= N: Name="Sleep Button" P: Phys=PNP0C0E/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:01/input/input4 U: Uniq= H: Handlers=kbd event3 B: PROP=0 B: EV=3 B: KEY=4000 0 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=PNP0C0C/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input5 U: Uniq= H: Handlers=kbd event4 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input6 U: Uniq= H: Handlers=kbd event5 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0019 Vendor= Product=0006 Version= N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input8 U: Uniq= H: Handlers=kbd event6 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus=0011 Vendor=0002 Product=000e Version= N: Name="ETPS/2 Elantech Touchpad" P: Phys=isa0060/serio1/input0 S: Sysfs=/devices/platform/i8042/serio1/input/input7 U: Uniq= H: Handlers=mouse1 event8 B: PROP=5 B: EV=b B: KEY=e420 1 0 0 0 0 B: ABS=66180001103 I: Bus=0003 Vendor=1044 Product=7a06 Version=0110 N: Name="E-Signal Keyboard" P: Phys=usb-:00:14.0-5/input0 S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/0003:1044:7A06.0002/input/input10 U: Uniq= H: Handlers=sysrq kbd leds event9 B: PROP=0 B: EV=120013 B: KEY=10007 ff9f207ac14057ff febeffdfffef fffe B: MSC=10 B: LED=7 I: Bus=0003 Vendor=1044 Product=7a06 Version=0110 N: Name="E-Signal Keyboard" P: Phys=usb-:00:14.0-5/input1 S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.1/0003:1044:7A06.0003/input/input11 U: Uniq= H: Handlers=kbd mouse2 event10 js0 B: PROP=0 B: EV=10001f B: KEY=3f0003007f 0 0 48317aff32d bf56 1f0001 130f938b17c000 677bfad9415fed 9ed6804400 1002 B: REL=1c0 B: ABS=10003 B: MSC=10 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Headphone" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input12 U: Uniq= H: Handlers=event11 B: PROP=0 B: EV=21 B: SW=4 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=3" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input13 U: Uniq= H: Handlers=event12 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=7" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input14 U: Uniq= H: Handlers=event13 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=8" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input15 U: Uniq= H:
[Kernel-packages] [Bug 1640613] ms10-34-mcdivittB0-kernel (arm64) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/3.19.0-75.83-generic/ms10-34-mcdivittB0-kernel__3.19.0-75.83__2016-11-17_04-26-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1640613 Title: linux: 3.19.0-75.83 -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: Confirmed 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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress 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: Invalid Status in linux source package in Vivid: Confirmed Bug description: This bug is for tracking the 3.19.0-75.83 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 derivative-trackers-created: 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/1640613/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1641083] s2lp6g002 (s390x.zKVM) - tests ran: 33, failed: 1
tests ran: 33, failed: 1; http://kernel.ubuntu.com/testing/4.8.0-28.30-generic/s2lp6g002__4.8.0-28.30__2016-11-17_03-55-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1641083 Title: linux: 4.8.0-28.30 -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: Confirmed 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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-28.30 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 derivative-trackers-created: 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/1641083/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1640613] Re: linux: 3.19.0-75.83 -proposed tracker
As per http://kernel.ubuntu.com/sru/sru-report.html Looks like there is no bug need to be verified this time. ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin (cypressyew) ** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => 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/1640613 Title: linux: 3.19.0-75.83 -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: Confirmed 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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress 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: Invalid Status in linux source package in Vivid: Confirmed Bug description: This bug is for tracking the 3.19.0-75.83 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 derivative-trackers-created: 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/1640613/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1640921] kernel01 (s390x.zVM) - tests ran: 18, failed: 1
tests ran: 18, failed: 1; http://kernel.ubuntu.com/testing/4.4.0-49.70-generic/kernel01__4.4.0-49.70__2016-11-17_04-08-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1640921 Title: linux: 4.4.0-49.70 -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: Confirmed 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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.4.0-49.70 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 derivative-trackers-created: 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/1640921/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1640621] Re: linux-lts-vivid: 3.19.0-75.83~14.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-vivid in Ubuntu. https://bugs.launchpad.net/bugs/1640621 Title: linux-lts-vivid: 3.19.0-75.83~14.04.1 -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: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-vivid source package in Trusty: Confirmed Bug description: This bug is for tracking the 3.19.0-75.83~14.04.1 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 derivative-trackers-created: true kernel-stable-master-bug: 1640613 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/1640621/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1630554] Comment bridged from LTC Bugzilla
--- Comment From bssrika...@in.ibm.com 2016-11-16 23:51 EDT--- I have tested the patch on 4.8.0-28-generic.. now I do not see any errors while booting guest with VFIO device.. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1630554 Title: QEMU throws failure msg while booting guest with SRIOV VF Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Fix Committed Status in linux source package in Zesty: Fix Released Bug description: == Comment: #10 - VIPIN K. PARASHAR - 2016-10-04 02:39:30 == (In reply to comment #9) > I took a quick look to this one and also noticed these 2 links: > https://bugzilla.redhat.com/show_bug.cgi?id=1237034 > http://marc.info/?l=linux-kernel&m=143737274332400&w=2 > and it looks like to avoid these message maybe just need to have this in > config file: > CONFIG_KVM_VFIO=y > I think we have that in powerkvm but not in Ubuntu KVM. On x86 running Ubuntu 16.04 == $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04.1 LTS Release: 16.04 Codename: xenial $ head /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family: 6 model : 61 model name: Intel(R) Core(TM) i5-5300U CPU @ 2.30GHz stepping : 4 microcode : 0x22 cpu MHz : 2300.179 cache size: 3072 KB physical id : 0 $ uname -a Linux Workstation 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:42:33 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux $ grep CONFIG_KVM_VFIO /boot/config-4.4.0-38-generic CONFIG_KVM_VFIO=y $ On PowerPC # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Yakkety Yak (development branch) Release: 16.10 Codename: yakkety # head /proc/cpuinfo processor : 0 cpu : POWER8E (raw), altivec supported clock : 2061.00MHz revision : 2.1 (pvr 004b 0201) processor : 1 cpu : POWER8E (raw), altivec supported clock : 2061.00MHz revision : 2.1 (pvr 004b 0201) # uname -a Linux c158f2u09os 4.8.0-17-generic #19 SMP Thu Sep 29 12:03:21 CDT 2016 ppc64le ppc64le ppc64le GNU/Linux # grep CONFIG_KVM_VFIO /boot/config-4.8.0-17-generic # I see that CONFIG_KVM_VFIO is enabled on x86 running Ubuntu 16.04 while ppc64 running 16.10 doesn't have it enabled. == Comment: #9 - Carol L. Soto - 2016-09-30 16:25:32 == I took a quick look to this one and also noticed these 2 links: https://bugzilla.redhat.com/show_bug.cgi?id=1237034 http://marc.info/?l=linux-kernel&m=143737274332400&w=2 and it looks like to avoid these message maybe just need to have this in config file: CONFIG_KVM_VFIO=y I think we have that in powerkvm but not in Ubuntu KVM. == Comment: #6 - VIPIN K. PARASHAR - 2016-09-23 06:50:22 == $ git log 178a787502123b0 -1 commit 178a787502123b01499c5a4617b94bb69ad49dd5 Author: David Gibson Date: Mon Feb 1 11:14:15 2016 +1100 vfio: Enable VFIO device for powerpc ec53500f "kvm: Add VFIO device" added a special KVM pseudo-device which is used to handle any necessary interactions between KVM and VFIO. Currently that device is built on x86 and ARM, but not powerpc, although powerpc does support both KVM and VFIO. This makes things awkward in userspace Currently qemu prints an alarming error message if you attempt to use VFIO and it can't initialize the KVM VFIO device. We don't want to remove the warning, because lack of the KVM VFIO device could mean coherency problems on x86. On powerpc, however, the error is harmless but looks disturbing, and a test based on host architecture in qemu would be ugly, and break if we do need the KVM VFIO device for something important in future. There's nothing preventing the KVM VFIO device from being built for powerpc, so this patch turns it on. It won't actually do anything, since we don't define any of the arch_*() hooks, but it will make qemu happy and we can extend it in future if we need to. Signed-off-by: David Gibson Reviewed-by: Eric Auger Signed-off-by: Paul Mackerras $ $ git describe --contains 178a787502123b v4.6-rc1~141^2~49^2~20 $ Commit (178a7875) seems to have enabled VFIO devices for powerpc. But this commit should already be available since 4.6 kernel and ubuntu is using 4.7 kernel here, so this should be already in. == Comment: #0 - SRIKANTH B. AITHAL - 2016-09-15 12:31:49 == ---Problem Description--- QEMU throwing false failure message while booting guest with SRIOV VF device ---una
[Kernel-packages] [Bug 1640921] kernel01 (s390x.zVM) - tests ran: 5, failed: 3
tests ran: 5, failed: 3; http://kernel.ubuntu.com/testing/4.4.0-49.70-generic/kernel01__4.4.0-49.70__2016-11-17_04-42-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1640921 Title: linux: 4.4.0-49.70 -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: Confirmed 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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.4.0-49.70 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 derivative-trackers-created: 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/1640921/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1641083] s2lp6g002 (s390x.zKVM) - tests ran: 19, failed: 7
tests ran: 19, failed: 7; http://kernel.ubuntu.com/testing/4.8.0-28.30-generic/s2lp6g002__4.8.0-28.30__2016-11-17_04-39-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1641083 Title: linux: 4.8.0-28.30 -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: Confirmed 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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-28.30 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 derivative-trackers-created: 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/1641083/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1640921] s2lp6g001 (s390x.zKVM) - tests ran: 33, failed: 0
tests ran: 33, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-49.70-generic/s2lp6g001__4.4.0-49.70__2016-11-17_04-22-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1640921 Title: linux: 4.4.0-49.70 -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: Confirmed 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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.4.0-49.70 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 derivative-trackers-created: 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/1640921/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1642470] [NEW] SRU. Please re-enable CONFIG_DRM_MGAG200.
Public bug reported: For some new Dell laptops, they are using Matrox graphics cards. And in order to let Xorg mga driver work. We need to enable CONFIG_DRM_MGAG200. MGAG200 is disabled by this bug. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1042903 Since Dell's laptops needs this to be enabled. I think we need to test lp:1042903 again because it's 4 years ago on HP. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: originate-from-1630501 somerville ** Tags added: originate-from-1630501 somerville -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1642470 Title: SRU. Please re-enable CONFIG_DRM_MGAG200. Status in HWE Next: New Status in linux package in Ubuntu: New Bug description: For some new Dell laptops, they are using Matrox graphics cards. And in order to let Xorg mga driver work. We need to enable CONFIG_DRM_MGAG200. MGAG200 is disabled by this bug. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1042903 Since Dell's laptops needs this to be enabled. I think we need to test lp:1042903 again because it's 4 years ago on HP. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1642470/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1640921] s2lp6g001 (s390x.zKVM) - tests ran: 19, failed: 7
tests ran: 19, failed: 7; http://kernel.ubuntu.com/testing/4.4.0-49.70-generic/s2lp6g001__4.4.0-49.70__2016-11-17_05-05-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1640921 Title: linux: 4.4.0-49.70 -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: Confirmed 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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.4.0-49.70 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 derivative-trackers-created: 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/1640921/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1591810] Re: [Feature] SKX: perf uncore PMU support
** Tags removed: verification-needed-yakkety ** Tags added: verification-done-yakkety -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1591810 Title: [Feature] SKX: perf uncore PMU support Status in intel: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Yakkety: Fix Committed Status in linux source package in Zesty: Fix Released Bug description: Enable Linux perf tool to support Intel Skylake server CPU uncore events. uncore provides additional performance monitoring information for advance user. HW: Purley Upstream schedule: 4.9 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1591810/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1642470] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1642470 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/1642470 Title: SRU. Please re-enable CONFIG_DRM_MGAG200. Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: For some new Dell laptops, they are using Matrox graphics cards. And in order to let Xorg mga driver work. We need to enable CONFIG_DRM_MGAG200. MGAG200 is disabled by this bug. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1042903 Since Dell's laptops needs this to be enabled. I think we need to test lp:1042903 again because it's 4 years ago on HP. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1642470/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1641083] s2lp6g002 (s390x.zKVM) - tests ran: 2, failed: 0
tests ran: 2, failed: 0; http://kernel.ubuntu.com/testing/4.8.0-28.30-generic/s2lp6g002__4.8.0-28.30__2016-11-17_05-30-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1641083 Title: linux: 4.8.0-28.30 -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: Confirmed 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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-28.30 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 derivative-trackers-created: 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/1641083/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1641083] s2lp6g002 (s390x.zKVM) - tests ran: 141, failed: 28
tests ran: 141, failed: 28; http://kernel.ubuntu.com/testing/4.8.0-28.30-generic/s2lp6g002__4.8.0-28.30__2016-11-17_05-02-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1641083 Title: linux: 4.8.0-28.30 -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: Confirmed 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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-28.30 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 derivative-trackers-created: 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/1641083/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1640921] s2lp3 (s390x.LPAR) - tests ran: 33, failed: 0
tests ran: 33, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-49.70-generic/s2lp3__4.4.0-49.70__2016-11-17_04-20-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1640921 Title: linux: 4.4.0-49.70 -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: Confirmed 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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.4.0-49.70 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 derivative-trackers-created: 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/1640921/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1640921] s2lp6g001 (s390x.zKVM) - tests ran: 141, failed: 28
tests ran: 141, failed: 28; http://kernel.ubuntu.com/testing/4.4.0-49.70-generic/s2lp6g001__4.4.0-49.70__2016-11-17_05-21-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1640921 Title: linux: 4.4.0-49.70 -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: Confirmed 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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.4.0-49.70 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 derivative-trackers-created: 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/1640921/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1640613] ms10-34-mcdivittB0-kernel (arm64) - tests ran: 10, failed: 7
tests ran: 10, failed: 7; http://kernel.ubuntu.com/testing/3.19.0-75.83-generic/ms10-34-mcdivittB0-kernel__3.19.0-75.83__2016-11-17_04-49-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1640613 Title: linux: 3.19.0-75.83 -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: Confirmed 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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress 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: Invalid Status in linux source package in Vivid: Confirmed Bug description: This bug is for tracking the 3.19.0-75.83 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 derivative-trackers-created: 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/1640613/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1640921] s2lp6g001 (s390x.zKVM) - tests ran: 2, failed: 0
tests ran: 2, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-49.70-generic/s2lp6g001__4.4.0-49.70__2016-11-17_05-38-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1640921 Title: linux: 4.4.0-49.70 -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: Confirmed 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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.4.0-49.70 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 derivative-trackers-created: 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/1640921/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1641083] s2lp6g002 (s390x.zKVM) - tests ran: 64, failed: 0
tests ran: 64, failed: 0; http://kernel.ubuntu.com/testing/4.8.0-28.30-generic/s2lp6g002__4.8.0-28.30__2016-11-17_05-34-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1641083 Title: linux: 4.8.0-28.30 -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: Confirmed 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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-28.30 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 derivative-trackers-created: 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/1641083/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1640921] s2lp3 (s390x.LPAR) - tests ran: 19, failed: 7
tests ran: 19, failed: 7; http://kernel.ubuntu.com/testing/4.4.0-49.70-generic/s2lp3__4.4.0-49.70__2016-11-17_05-40-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1640921 Title: linux: 4.4.0-49.70 -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: Confirmed 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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.4.0-49.70 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 derivative-trackers-created: 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/1640921/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1640921] s2lp6g001 (s390x.zKVM) - tests ran: 64, failed: 0
tests ran: 64, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-49.70-generic/s2lp6g001__4.4.0-49.70__2016-11-17_05-41-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1640921 Title: linux: 4.4.0-49.70 -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: Confirmed 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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.4.0-49.70 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 derivative-trackers-created: 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/1640921/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1641083] onibi (i386) - tests ran: 4, failed: 1
tests ran: 4, failed: 1; http://kernel.ubuntu.com/testing/4.8.0-28.30-generic/onibi__4.8.0-28.30__2016-11-17_04-56-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1641083 Title: linux: 4.8.0-28.30 -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: Confirmed 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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-28.30 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 derivative-trackers-created: 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/1641083/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1640921] s2lp3 (s390x.LPAR) - tests ran: 2, failed: 0
tests ran: 2, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-49.70-generic/s2lp3__4.4.0-49.70__2016-11-17_06-20-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1640921 Title: linux: 4.4.0-49.70 -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: Confirmed 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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.4.0-49.70 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 derivative-trackers-created: 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/1640921/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1640921] s2lp3 (s390x.LPAR) - tests ran: 141, failed: 28
tests ran: 141, failed: 28; http://kernel.ubuntu.com/testing/4.4.0-49.70-generic/s2lp3__4.4.0-49.70__2016-11-17_05-54-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1640921 Title: linux: 4.4.0-49.70 -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: Confirmed 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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.4.0-49.70 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 derivative-trackers-created: 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/1640921/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1640921] kernel01 (s390x.zVM) - tests ran: 33, failed: 5
tests ran: 33, failed: 5; http://kernel.ubuntu.com/testing/4.4.0-49.70-generic/kernel01__4.4.0-49.70__2016-11-17_04-57-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1640921 Title: linux: 4.4.0-49.70 -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: Confirmed 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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.4.0-49.70 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 derivative-trackers-created: 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/1640921/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1640921] kernel01 (s390x.zVM) - tests ran: 19, failed: 8
tests ran: 19, failed: 8; http://kernel.ubuntu.com/testing/4.4.0-49.70-generic/kernel01__4.4.0-49.70__2016-11-17_06-16-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1640921 Title: linux: 4.4.0-49.70 -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: Confirmed 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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.4.0-49.70 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 derivative-trackers-created: 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/1640921/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1640613] dwalin (amd64) - tests ran: 30, failed: 0
tests ran: 30, failed: 0; http://kernel.ubuntu.com/testing/3.19.0-75.83-generic/dwalin__3.19.0-75.83__2016-11-17_05-31-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1640613 Title: linux: 3.19.0-75.83 -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: Confirmed 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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress 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: Invalid Status in linux source package in Vivid: Confirmed Bug description: This bug is for tracking the 3.19.0-75.83 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 derivative-trackers-created: 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/1640613/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1640921] s2lp3 (s390x.LPAR) - tests ran: 64, failed: 0
tests ran: 64, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-49.70-generic/s2lp3__4.4.0-49.70__2016-11-17_06-23-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1640921 Title: linux: 4.4.0-49.70 -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: Confirmed 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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.4.0-49.70 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 derivative-trackers-created: 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/1640921/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1641083] modoc (ppc64el) - tests ran: 36, failed: 3
tests ran: 36, failed: 3; http://kernel.ubuntu.com/testing/4.8.0-28.30-generic/modoc__4.8.0-28.30__2016-11-17_04-49-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1641083 Title: linux: 4.8.0-28.30 -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: Confirmed 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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-28.30 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 derivative-trackers-created: 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/1641083/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1640921] kernel01 (s390x.zVM) - tests ran: 141, failed: 140
tests ran: 141, failed: 140; http://kernel.ubuntu.com/testing/4.4.0-49.70-generic/kernel01__4.4.0-49.70__2016-11-17_06-32-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1640921 Title: linux: 4.4.0-49.70 -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: Confirmed 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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.4.0-49.70 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 derivative-trackers-created: 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/1640921/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1640921] kernel01 (s390x.zVM) - tests ran: 2, failed: 0
tests ran: 2, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-49.70-generic/kernel01__4.4.0-49.70__2016-11-17_06-42-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1640921 Title: linux: 4.4.0-49.70 -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: Confirmed 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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.4.0-49.70 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 derivative-trackers-created: 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/1640921/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1640921] kernel01 (s390x.zVM) - tests ran: 64, failed: 1
tests ran: 64, failed: 1; http://kernel.ubuntu.com/testing/4.4.0-49.70-generic/kernel01__4.4.0-49.70__2016-11-17_06-45-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1640921 Title: linux: 4.4.0-49.70 -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: Confirmed 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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.4.0-49.70 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 derivative-trackers-created: 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/1640921/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1626436] Re: [4.8 regression] boot has become very slow
> I noticed the comment does not have the download link. It is: > http://kernel.ubuntu.com/~jsalisbury/lp1626436/mailine-with-two-commits/ Bazinga! Perhaps unexpectedly, this is a GOOD kernel -- boot speed is comparable with 4.4, there is no high load after booting any more, and shutdown is fast as well. Thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1626436 Title: [4.8 regression] boot has become very slow Status in linux package in Ubuntu: In Progress Status in linux source package in Yakkety: In Progress Bug description: With yakkety's recent update from linux 4.4 to 4.8 booting has become a lot slower. It's not one service in particular, but without "quiet" and "splash" you can now easily read every single line instead of that whole wall of text zipping by. It now takes over 20s instead of ~10 seconds to boot. This is even more dramatic when factoring out the recent boot hang of NetworkManager (bug 1622893) and disabling lightdm: sudo systemctl mask NetworkManager NetworkManager-wait-online lightdm then booting with 4.4 takes 1.5s and with 4.8 19.5s (!). Some excerps from systemd-analyze blame: 4.4: 474ms postfix@-.service 395ms lxd-containers.service 305ms networking.service 4.8: 4.578s postfix@-.service 7.300s lxd-containers.service 6.285s networking.service I attach the full outputs of critical-chain and analyze for 4.4 and 4.8 for reference. This is much less noticeable in the running system. There is no immediate feeling of sluggishness (although my system is by and large idle). I compared the time of sbuilding colord under similar circumstances (-j4, building on tmpfs, thus no hard disk delays; running with fully pre-loaded apt-cacher-ng thus no random network delays), and with 4.4 it takes 6.5 minutes and with 4.8 it takes 7.5. So that got a bit slower, but much less dramatically than during boot, so this is either happening when a lot of processes run in parallel, or is perhaps related to setting up cgroups. One thing I noticed that during sbuild in 4.8 "top" shows ridiculous loads (~ 250) under 4.8, while it's around 4 or 5 under 4.4. But that doesn't reflect in actual sluggishness, so this might be just an unrelated bug. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-11-generic 4.8.0-11.12 ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6 Uname: Linux 4.8.0-11-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: martin 3049 F...m pulseaudio /dev/snd/pcmC0D0p: martin 3049 F...m pulseaudio /dev/snd/controlC0: martin 3049 F pulseaudio Date: Thu Sep 22 09:42:56 2016 EcryptfsInUse: Yes MachineType: LENOVO 2324CTO ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-11-generic.efi.signed root=UUID=f86539b0-3a1b-4372-83b0-acdd029ade68 ro rootflags=subvol=@ systemd.debug-shell RelatedPackageVersions: linux-restricted-modules-4.8.0-11-generic N/A linux-backports-modules-4.8.0-11-generic N/A linux-firmware1.161 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/09/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET95WW (2.55 ) dmi.board.asset.tag: Not Available dmi.board.name: 2324CTO dmi.board.vendor: LENOVO dmi.board.version: 0B98401 Pro dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET95WW(2.55):bd07/09/2013:svnLENOVO:pn2324CTO:pvrThinkPadX230:rvnLENOVO:rn2324CTO:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2324CTO dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626436/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1641083] modoc (ppc64el) - tests ran: 19, failed: 6
tests ran: 19, failed: 6; http://kernel.ubuntu.com/testing/4.8.0-28.30-generic/modoc__4.8.0-28.30__2016-11-17_07-15-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1641083 Title: linux: 4.8.0-28.30 -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: Confirmed 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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.8.0-28.30 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 derivative-trackers-created: 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/1641083/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1628061] Re: iwl4965 crashes randomly
@Christopher M. Penalver: The newest kernel 4.9-rc5-generic gives a kernel panic at boot. "stack guard page was hit at ..." What to do 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/1628061 Title: iwl4965 crashes randomly Status in linux package in Ubuntu: Incomplete Bug description: On my Lenovo X61s, WLAN randomly stops working, typically after a few hours of running time. I don't know any remedy but to reboot. This behavior started maybe 2 or 3 months ago. My maching is usually kept up to date, so the problem might be caused by some kernel update at that time. The relevant part in dmesg (attached) starts with [ 5812.412141] iwl4965 :03:00.0: Error sending C_POWER_TBL: time out after 500ms. [ 5812.412156] iwl4965 :03:00.0: set power fail, ret = -110 [ 5813.424145] iwl4965 :03:00.0: Error sending C_ADD_STA: time out after 500ms. [ 5813.424162] wls3: HW problem - can not stop rx aggregation for **:**:**:**:**:** tid 0 [ 5813.924092] iwl4965 :03:00.0: Error sending C_ADD_STA: time out after 500ms. [ 5813.924107] wls3: HW problem - can not stop rx aggregation for **:**:**:**:**:** tid 5 [ 5814.052099] iwl4965 :03:00.0: Queue 4 stuck for 2500 ms. [ 5814.052124] iwl4965 :03:00.0: On demand firmware reload [ 5814.424142] iwl4965 :03:00.0: Error sending C_ADD_STA: time out after 500ms. [ 5814.424168] wls3: HW problem - can not stop rx aggregation for **:**:**:**:**:** tid 6 [ 5814.424421] iwl4965 :03:00.0: Master Disable Timed Out, 100 usec [ 5814.424468] ieee80211 phy0: Hardware restart was requested [ 5814.448160] iwl4965 :03:00.0: idx 0 not used in uCode key table. [ 5814.948182] iwl4965 :03:00.0: Error sending C_ADD_STA: time out after 500ms. [ 5814.948201] wls3: failed to remove key (0, **:**:**:**:**:**) from hardware (-110) [ 5818.964158] iwl4965 :03:00.0: START_ALIVE timeout after 4000ms. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-38-generic 4.4.0-38.57 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mki2093 F pulseaudio CurrentDesktop: XFCE Date: Tue Sep 27 13:29:36 2016 HibernationDevice: RESUME=/dev/mapper/vgubuntu-swap InstallationDate: Installed on 2016-06-05 (113 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) MachineType: LENOVO 76693JG PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-38-generic root=/dev/mapper/vgubuntu-system ro RelatedPackageVersions: linux-restricted-modules-4.4.0-38-generic N/A linux-backports-modules-4.4.0-38-generic N/A linux-firmware1.157.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/22/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 7NETC2WW (2.22 ) dmi.board.name: 76693JG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7NETC2WW(2.22):bd03/22/2011:svnLENOVO:pn76693JG:pvrThinkPadX61s:rvnLENOVO:rn76693JG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 76693JG dmi.product.version: ThinkPad X61s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1628061/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1640181] Re: [ 4.9 ] Greeter loop with a nvidia driver
** Summary changed: - Need a patched 4.9 kernel to compile nvidia drivers + [ 4.9 ] Greeter loop with a nvidia driver ** Description changed: - As the unstable kernel ppa now has 4.9 kernel, i've installed it on a - system using a nvidia-370/375 driver, but both fails at compile dkms - time. - - This is an identified problem and a proposed patch is already ready: - https://devtalk.nvidia.com/default/topic/972761/linux/linux-4-9-git-rc1-375-10-build-errors/ - - note: there is no full working patch found yet (the above one allow - compilation but the kernel fails to load) + Can't go past the greeter loop with a nvidia driver. + Compilation fails at dkms level. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.8.0-27-generic 4.8.0-27.29 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: oem1777 F pulseaudio /dev/snd/controlC0: oem1777 F pulseaudio CurrentDesktop: GNOME Date: Tue Nov 8 15:01:20 2016 HibernationDevice: RESUME=UUID=0a9ca7f0-6eeb-4b21-b70f-670fa600de16 IwConfig: eth1 no wireless extensions. lono wireless extensions. eth0 no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse] Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-27-generic root=UUID=7c755ed6-51cc-4b75-88ac-9c75acf82749 ro RelatedPackageVersions: linux-restricted-modules-4.8.0-27-generic N/A linux-backports-modules-4.8.0-27-generic N/A linux-firmware1.161 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5W DH Deluxe 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.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5W DH Deluxe dmi.product.version: System Version dmi.sys.vendor: ASUSTEK COMPUTER INC ** No longer affects: virtualbox (Ubuntu) ** Attachment added: "dkms build errors" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1640181/+attachment/4778017/+files/make.log ** Also affects: ubuntu-drivers-common (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/1640181 Title: [ 4.9 ] Greeter loop with a nvidia driver Status in linux package in Ubuntu: Confirmed Status in ubuntu-drivers-common package in Ubuntu: New Bug description: Can't go past the greeter loop with a nvidia driver. Compilation fails at dkms level. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.8.0-27-generic 4.8.0-27.29 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: oem1777 F pulseaudio /dev/snd/controlC0: oem1777 F pulseaudio CurrentDesktop: GNOME Date: Tue Nov 8 15:01:20 2016 HibernationDevice: RESUME=UUID=0a9ca7f0-6eeb-4b21-b70f-670fa600de16 IwConfig: eth1 no wireless extensions. lono wireless extensions. eth0 no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse] Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-27-generic root=UUID=7c755ed6-51cc-4b75-88ac-9c75acf82749 ro RelatedPackageVersions: linux-restricted-modules-4.8.0-27-generic N/A linux-backports-modules-4.8.0-27-generic N/A linux-firmware1.161 RfKill: Source
[Kernel-packages] [Bug 1642192] [NEW] i386 4.9 in -proposed fails to boot in cloud instances
Public bug reported: I noticed a forever-looping test of linuxinfo on i386 this morning. This test upgrades the kernel to 4.9 in -proposed; as soon as that reboots, the VM never comes back. nova console-log shows: [1.581188] Freeing unused kernel memory: 996K (dcc37000 - dcd3) [1.582525] Write protecting the kernel text: 8300k [1.583624] Write protecting the kernel read-only data: 3344k [1.584845] NX-protecting the kernel data: 6036k [1.585921] [ cut here ] [1.586861] WARNING: CPU: 0 PID: 1 at /build/linux-UWDXbt/linux-4.9.0/arch/x86/mm/dump_pagetables.c:225 note_page+0x6a1/0x880 [1.589199] x86/mm: Found insecure W+X mapping at address c00a/0xc00a [1.590657] Modules linked in: [1.591305] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.9.0-1-generic #2-Ubuntu [1.592809] Hardware name: OpenStack Foundation OpenStack Nova, BIOS Bochs 01/01/2011 [1.593188] dae89e70 dc3e0b05 dae89eb4 dca47958 dae89ea0 dc07299a dca47920 dae89ed4 [1.593188] 0001 dca47958 00e1 dc068db1 00e1 dae89f34 8000 [1.593188] dae89ec0 dc072a06 0009 dae89eb4 dca47920 dae89ed4 76601e21 [1.593188] Call Trace: [1.593188] [] dump_stack+0x58/0x73 [1.593188] [] __warn+0xea/0x110 [1.593188] [] ? note_page+0x6a1/0x880 [1.593188] [] warn_slowpath_fmt+0x46/0x60 [1.593188] [] note_page+0x6a1/0x880 [1.593188] [] ptdump_walk_pgd_level_core+0x1f5/0x300 [1.593188] [] ptdump_walk_pgd_level_checkwx+0x16/0x20 [1.593188] [] mark_rodata_ro+0xfd/0x130 [1.593188] [] ? rest_init+0x70/0x70 [1.593188] [] kernel_init+0x2c/0x100 [1.593188] [] ? schedule_tail+0x11/0x50 [1.593188] [] ? rest_init+0x70/0x70 [1.593188] [] ret_from_fork+0x1b/0x28 [1.613361] ---[ end trace d63b34644638754d ]--- [1.614368] x86/mm: Checked W+X mappings: FAILED, 96 W+X pages found. ... Begin: Waiting for root file system ... Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. [... repeating some 50 times... ] Begin: Running /scripts/local-block ... done. done. Gave up waiting for root device. Common problems: - Boot args (cat /proc/cmdline) - Check rootdelay= (did the system wait long enough?) - Check root= (did the system wait for the right device?) - Missing modules (cat /proc/modules; ls /dev) ALERT! UUID=ac6eb865-17d6-469d-b58e-8c0d49174fe4 does not exist. Dropping to a shell! BusyBox v1.22.1 (Ubuntu 1:1.22.0-19ubuntu2) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bot-stop-nagging ** Tags added: bot-stop-nagging -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1642192 Title: i386 4.9 in -proposed fails to boot in cloud instances Status in linux package in Ubuntu: New Bug description: I noticed a forever-looping test of linuxinfo on i386 this morning. This test upgrades the kernel to 4.9 in -proposed; as soon as that reboots, the VM never comes back. nova console-log shows: [1.581188] Freeing unused kernel memory: 996K (dcc37000 - dcd3) [1.582525] Write protecting the kernel text: 8300k [1.583624] Write protecting the kernel read-only data: 3344k [1.584845] NX-protecting the kernel data: 6036k [1.585921] [ cut here ] [1.586861] WARNING: CPU: 0 PID: 1 at /build/linux-UWDXbt/linux-4.9.0/arch/x86/mm/dump_pagetables.c:225 note_page+0x6a1/0x880 [1.589199] x86/mm: Found insecure W+X mapping at address c00a/0xc00a [1.590657] Modules linked in: [1.591305] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.9.0-1-generic #2-Ubuntu [1.592809] Hardware name: OpenStack Foundation OpenStack Nova, BIOS Bochs 01/01/2011 [1.593188] dae89e70 dc3e0b05 dae89eb4 dca47958 dae89ea0 dc07299a dca47920 dae89ed4 [1.593188] 0001 dca47958 00e1 dc068db1 00e1 dae89f34 8000 [1.593188] dae89ec0 dc072a06 0009 dae89eb4 dca47920 dae89ed4 76601e21 [1.593188] Call Trace: [1.593188] [] dump_stack+0x58/0x73 [1.593188] [] __warn+0xea/0x110 [1.593188] [] ? note_page+0x6a1/0x880 [1.593188] [] warn_slowpath_fmt+0x46/0x60 [1.593188] [] note_page+0x6a1/0x880 [1.593188] [] ptdump_walk_pgd_level_core+0x1f5/0x300 [1.593188] [] ptdump_walk_pgd_level_checkwx+0x16/0x20 [1.593188] [] mark_rodata_ro+0xfd/0x130 [1.593188] [] ? rest_init+0x70/0x70 [1.593188] [] kernel_init+0x2c/0x100 [1.593188] [] ? schedule_tail+0x11/0x50 [1.593188] [] ? rest_init+0x70/0x70 [1.593188] [] ret_from_fork+0x1b/0x28 [1.613361] ---[ end trace d63b34644638754d ]--- [1.614368] x86/mm: Checked W+X mappings: FAI
[Kernel-packages] [Bug 1642192] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1642192 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/1642192 Title: i386 4.9 in -proposed fails to boot in cloud instances Status in linux package in Ubuntu: Incomplete Bug description: I noticed a forever-looping test of linuxinfo on i386 this morning. This test upgrades the kernel to 4.9 in -proposed; as soon as that reboots, the VM never comes back. nova console-log shows: [1.581188] Freeing unused kernel memory: 996K (dcc37000 - dcd3) [1.582525] Write protecting the kernel text: 8300k [1.583624] Write protecting the kernel read-only data: 3344k [1.584845] NX-protecting the kernel data: 6036k [1.585921] [ cut here ] [1.586861] WARNING: CPU: 0 PID: 1 at /build/linux-UWDXbt/linux-4.9.0/arch/x86/mm/dump_pagetables.c:225 note_page+0x6a1/0x880 [1.589199] x86/mm: Found insecure W+X mapping at address c00a/0xc00a [1.590657] Modules linked in: [1.591305] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.9.0-1-generic #2-Ubuntu [1.592809] Hardware name: OpenStack Foundation OpenStack Nova, BIOS Bochs 01/01/2011 [1.593188] dae89e70 dc3e0b05 dae89eb4 dca47958 dae89ea0 dc07299a dca47920 dae89ed4 [1.593188] 0001 dca47958 00e1 dc068db1 00e1 dae89f34 8000 [1.593188] dae89ec0 dc072a06 0009 dae89eb4 dca47920 dae89ed4 76601e21 [1.593188] Call Trace: [1.593188] [] dump_stack+0x58/0x73 [1.593188] [] __warn+0xea/0x110 [1.593188] [] ? note_page+0x6a1/0x880 [1.593188] [] warn_slowpath_fmt+0x46/0x60 [1.593188] [] note_page+0x6a1/0x880 [1.593188] [] ptdump_walk_pgd_level_core+0x1f5/0x300 [1.593188] [] ptdump_walk_pgd_level_checkwx+0x16/0x20 [1.593188] [] mark_rodata_ro+0xfd/0x130 [1.593188] [] ? rest_init+0x70/0x70 [1.593188] [] kernel_init+0x2c/0x100 [1.593188] [] ? schedule_tail+0x11/0x50 [1.593188] [] ? rest_init+0x70/0x70 [1.593188] [] ret_from_fork+0x1b/0x28 [1.613361] ---[ end trace d63b34644638754d ]--- [1.614368] x86/mm: Checked W+X mappings: FAILED, 96 W+X pages found. ... Begin: Waiting for root file system ... Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. [... repeating some 50 times... ] Begin: Running /scripts/local-block ... done. done. Gave up waiting for root device. Common problems: - Boot args (cat /proc/cmdline) - Check rootdelay= (did the system wait long enough?) - Check root= (did the system wait for the right device?) - Missing modules (cat /proc/modules; ls /dev) ALERT! UUID=ac6eb865-17d6-469d-b58e-8c0d49174fe4 does not exist. Dropping to a shell! BusyBox v1.22.1 (Ubuntu 1:1.22.0-19ubuntu2) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1642192/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1642114] Re: ThinkPad T460 hotkeys stop working in Ubuntu 16.04
** Changed in: hwe-next 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/1642114 Title: ThinkPad T460 hotkeys stop working in Ubuntu 16.04 Status in HWE Next: Triaged Status in linux package in Ubuntu: In Progress Bug description: Hotkeys of ThinkPad T460 no longer works in Ubuntu 16.04, and dmesg shows an thinkpad_acpi: unknown version of the HKEY interface: 0x200. Commit 0118c2d3eac0545d4095877e5a015b5dc763b3c2 is required to support HKEY interface 0x200 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1642114/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1641139] Re: Infiniband driver (kernel module) needed for Azure
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1641139 Title: Infiniband driver (kernel module) needed for Azure Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Committed Bug description: The Infiniband driver (kernel module) needed for Azure A8/A9, H-series, and NC24/NV24 instances is different than the typical upstream Infiniband driver. Also, the WALA agent must be customized to ensure that the host driver for IB and the guest driver for IB match. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641139/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1637165] Re: Module sha1-mb fails to load
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1637165 Title: Module sha1-mb fails to load Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: The module sha1-mb always fails to load with "No such device": $ sudo modprobe sha1-mb modprobe: ERROR: could not insert 'sha1_mb': No such device This is a problem related to missing export/import functions and statesize in the algorithm definition. It's similar to the bug #1633058. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1637165/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1634964] Re: Allow fuse user namespace mounts by default in xenial
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1634964 Title: Allow fuse user namespace mounts by default in xenial Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: This is a requirement for supporting snaps within lxd containers in xenial. It is already allowed in yakkety, so enablement in xenial consists of backporting some changes and changing the fuse userns_mounts parameter to be enabled by default. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1634964/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1636733] Re: [LTCTest] vfio_pci not loaded on Ubuntu 16.10 by default
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1636733 Title: [LTCTest] vfio_pci not loaded on Ubuntu 16.10 by default Status in linux package in Ubuntu: Fix Released Status in kernel-package source package in Xenial: New Status in linux source package in Xenial: Fix Committed Status in kernel-package source package in Yakkety: New Status in linux source package in Yakkety: Fix Committed Status in kernel-package source package in Zesty: Invalid Status in linux source package in Zesty: Fix Released Bug description: == Comment: #0 - SRIKANTH B. AITHAL - 2016-10-26 01:40:39 == ---Problem Description--- vfio_pci is not loaded by default on Ubuntu 16.10 host boot. All VFIO related tasks would fail without that module. For instance I was trying to boot guest with QEMU directly and it was failing complaining "/sys/bus/pci/drivers/vfio-pci/new_id" not present. root@c158f2u09os:~# lsmod | grep -i vfio root@c158f2u09os:~# modprobe vfio_pci <-- need to load explicitly root@c158f2u09os:~# lsmod | grep -i vfio vfio_pci 51735 0 irqbypass 5567 1 vfio_pci vfio_iommu_spapr_tce14567 0 vfio_virqfd 4859 1 vfio_pci vfio 31351 2 vfio_iommu_spapr_tce,vfio_pci vfio_spapr_eeh 3441 2 vfio_iommu_spapr_tce,vfio_pci Either > we need to have these modules loaded by kernel by default or > we need to update https://wiki.ubuntu.com/ppc64el/CommonQuestions telling customers to load vfio_pci module explicitly before attempting any vfio tasks. Contact Information = Srikanth/bssrika...@in.ibm.com ---uname output--- Linux c158f2u09os 4.8.0-26-generic #28-Ubuntu SMP Tue Oct 18 14:41:40 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux Machine Type = 8247-22L ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. After booting into Ubuntu 16.10, see if vfio_pci modules are loaded: root@c158f2u09os:~# lsmod | grep -i vfio 2. After that we need to manually load vfio_pci root@c158f2u09os:~# modprobe vfio_pci root@c158f2u09os:~# To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1636733/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1633321] Re: Fix alps driver for multitouch function.
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1633321 Title: Fix alps driver for multitouch function. Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Fix Committed Bug description: We need to cherry-pick 9a54cf462d6f3c383a5a4f5fe15c020a03db44e6 for alps touchpads. Otherwise the touchpad will stop working when we put more than 3 fingers on the pad. Please consider SRU this commit. Impact: Alps driver doesn't work when users put more than 3 fingers on it. Fix: Alps touchpad still works good after multitouch for more than 3 fingers. Tested: The patch is tested on new Dell Inspiron laptops and works very good. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1633321/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1635223 Title: please include mlx5_core modules in linux-image-generic package Status in cloud-images: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Fix Committed 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 1634380] Re: BT still shows off after resume by wireless hotkey
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1634380 Title: BT still shows off after resume by wireless hotkey Status in HWE Next: Fix Committed Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: Fix Committed Bug description: Summary: BT still shows off after resume by wireless hotkey Steps: 1) Install ubuntu 16.04 2) Press the wireless hotkey 3) Check the WiFi/BT status 4) Press the wireless hotkey again 5) Check the WiFi/BT status Expected results: Can turn on/off the WiFi/BT by wireless hotkey Actual results: Can turn off the WiFi/BT by wireless hotkey, but the BT is still off after press the hotkey again. WiFi didn't has this issue. Can't turn on the BT in the system setting, need reboot the system. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1634380/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1634607] Re: kernel generates ACPI Exception: AE_NOT_FOUND, Evaluating _DOD incorrectly
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1634607 Title: kernel generates ACPI Exception: AE_NOT_FOUND, Evaluating _DOD incorrectly Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Fix Committed Bug description: Many system supports hybrid graphics and its discrete VGA does not have any connectors and therefore has no _DOD method. However, kernel assumes the control method, _DOD, is required. As a result, an exception is thrown incorrectly. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1634607/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1637978] Re: take 'P' command from upstream xmon
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1637978 Title: take 'P' command from upstream xmon Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Fix Released Status in linux source package in Zesty: Fix Released Bug description: upstream commit 6dfb54049f9a99b24fe5d5cd2d3af19eadc8f31f contains an enhancement to xmon to allow listing running tasks. This is vital to debugging efforts, and so needs to be added to as many release streams as possible, as soon as possible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1637978/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1633506] Re: backport fwts UEFI test driver to Xenial
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1633506 Title: backport fwts UEFI test driver to Xenial Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: [SRU Justification, XENIAL] The fwts UEFI test driver is now upstream in Linux 4.9 and also in the Ubuntu Yakkety 4.8 kernel, so it would be useful for fwts support to add it into the Xenial kernel as default (for example Xenial bases fwts snaps as we can dispense with the DKMS module support). [Fix] Upstream commit ff6301dabc3ca20ab8f50f8d0252ac05da610d8 "efi: Add efi_test driver for exporting UEFI runtime service interfaces" This patch requires a minor patch wiggle on the Makefile and Kconfig to backport to Xenial. [Test] Build fwts from the source and run on a Xenial kernel w/o the fwts dpkg based efi driver and run "sudo fwts --uefitests -" and the tests will fail. Install the fixed kernel with the driver and the tests will now run because the module is loaded by fwts and we can now exercise the UEFI run time interfaces from fwts as root. [Regression Potential] This adds test functionality and will not impact on any other driver or subsystem. To access these test interfaces one requires root privileges, so risk of normal unprivileged uses accessing UEFI run time services are zero. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633506/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1634705] Re: Add ipvlan module to 16.04 kernel
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1634705 Title: Add ipvlan module to 16.04 kernel Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Fix Committed Status in linux source package in Zesty: Fix Released Bug description: Currently, ipvlan is included in the linux-image-extra package however users have requested that it be included as a module in the primary kernel package. Users running docker with mesos require ipvlan for container networking to function (and likely other container use cases). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1634705/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1620979] Re: Hotkey doesn't work on HP x360
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1620979 Title: Hotkey doesn't work on HP x360 Status in HWE Next: Confirmed Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: Fix Committed Bug description: [Impact] When pinctrl-cherryview probing gpio device it clear interrupt mask and status, and in the later procedures the interrupt mask isn't set back correctly, leads to hotkeys fail. [Fix] Upstream fixes this in 4.8-rc3 by not clearing interrupt masks: commit bcb48cca23ec9852739e4a464307fa29515bbe48 Author: Mika Westerberg Date: Mon Aug 22 14:42:52 2016 +0300 pinctrl: cherryview: Do not mask all interrupts in probe To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1620979/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1632527] Re: [Dell][XPS]Touchscreen fails to function after resume from s3 by Lid close/open
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1632527 Title: [Dell][XPS]Touchscreen fails to function after resume from s3 by Lid close/open Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Fix Released Status in linux source package in Zesty: Fix Released Bug description: Touchscreen fails to function after resume from s3 by Lid close/open Suspend from power menu/ power button cannot reproduce this issue Steps: 1. Install ubuntu 16.04 and boot to OS 2. suspend the system by Lid close action 3. resume the session by Lid open 4. check if touchscreen function works Expected results: Touchscreen should still works after Lid open Actual results: Touchscreen fails to work after lid open To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1632527/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1632045] Re: KVM: PPC: Book3S HV: Migrate pinned pages out of CMA
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1632045 Title: KVM: PPC: Book3S HV: Migrate pinned pages out of CMA Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Fix Committed Status in linux source package in Zesty: Fix Released Bug description: ---Problem Description--- https://github.com/open-power/supermicro-openpower/issues/59 SW/HW Configuration PNOR image version: 5/3/2016 BMC image version: 0.25 CPLD Version: B2.81.01 Host OS version: Ubuntu 16.04 LTS UbuntuKVM Guest OS version: Ubuntu 14.04.4 LTS HTX version: 394 Processor: 00UL865 * 2 Memory: SK hynix 16GB 2Rx4 PC4-2133P * 16 Summary of Issue Two UbuntuKVM guests are each configured with 8 processors, 64 GB of memory, 1 disk of 128 GB, 1 network interface, and 1 GPU (pass- through'd from the Host OS's K80). The two guests are each put into a Create/Destroy loop, with HTX running on each of the guests (NOT HOST) in between its creation and destruction. The mdt.bu profile is used, and the processors, memory, and the GPU are put under load. The HTX session lasts 9 minutes. While this is running, the amount of available memory (free memory) in the Host OS will slowly decrease, and this can continue until the point wherein there's no more free memory for the Host OS to do anything, including creating the two VM guests. It seems to be that after every cycle, a small portion of the memory that was allocated to the VM guest does not get released back to the Host OS, and eventually, this can and will add up to take up all the available memory in the Host OS. At some point, the VM guest(s) might get disconnected and will display the following error: error: Disconnected from qemu:///system due to I/O error error: One or more references were leaked after disconnect from the hypervisor Then, when the Host OS tries to start the VM guest again, the following error shows up: error: Failed to create domain from guest2_trusty.xml error: internal error: early end of file from monitor, possible problem: Unexpected error in spapr_alloc_htab() at /build/qemu-c3ZrbA/qemu-2.5+dfsg/hw/ppc/spapr.c:1030: 2016-05-23T16:18:16.871549Z qemu-system-ppc64: Failed to allocate HTAB of requested size, try with smaller maxmem The Host OS syslog, as seen HERE, also contains quite some errors. To just list a few: May 13 20:27:44 191-136 kernel: [36827.151228] alloc_contig_range: [3fb800, 3fd8f8) PFNs busy May 13 20:27:44 191-136 kernel: [36827.151291] alloc_contig_range: [3fb800, 3fd8fc) PFNs busy May 13 20:27:44 191-136 libvirtd[19263]: *** Error in `/usr/sbin/libvirtd': realloc(): invalid next size: 0x01000a780400 *** May 13 20:27:44 191-136 libvirtd[19263]: === Backtrace: = May 13 20:27:44 191-136 libvirtd[19263]: /lib/powerpc64le-linux-gnu/libc.so.6(+0x8720c)[0x3fffaf6a720c] May 13 20:27:44 191-136 libvirtd[19263]: /lib/powerpc64le-linux-gnu/libc.so.6(+0x96f70)[0x3fffaf6b6f70] May 13 20:27:44 191-136 libvirtd[19263]: /lib/powerpc64le-linux-gnu/libc.so.6(realloc+0x16c)[0x3fffaf6b87fc] May 13 20:27:44 191-136 libvirtd[19263]: /usr/lib/powerpc64le-linux-gnu/libvirt.so.0(virReallocN+0x68)[0x3fffaf90ccc8] May 13 20:27:44 191-136 libvirtd[19263]: /usr/lib/libvirt/connection-driver/libvirt_driver_qemu.so(+0x8ef6c)[0x3fff9346ef6c] May 13 20:27:44 191-136 libvirtd[19263]: /usr/lib/libvirt/connection-driver/libvirt_driver_qemu.so(+0xa826c)[0x3fff9348826c] May 13 20:27:44 191-136 libvirtd[19263]: /usr/lib/powerpc64le-linux-gnu/libvirt.so.0(virEventPollRunOnce+0x8b4)[0x3fffaf9332b4] May 13 20:27:44 191-136 libvirtd[19263]: /usr/lib/powerpc64le-linux-gnu/libvirt.so.0(virEventRunDefaultImpl+0x54)[0x3fffaf931334] May 13 20:27:44 191-136 libvirtd[19263]: /usr/lib/powerpc64le-linux-gnu/libvirt.so.0(virNetDaemonRun+0x1f0)[0x3fffafad2f70] May 13 20:27:44 191-136 libvirtd[19263]: /usr/sbin/libvirtd(+0x15d74)[0x52e45d74] May 13 20:27:44 191-136 libvirtd[19263]: /lib/powerpc64le-linux-gnu/libc.so.6(+0x2319c)[0x3fffaf64319c] May 13 20:27:44 191-136 libvirtd[19263]: /lib/powerpc64le-linux-gnu/libc.so.6(__libc_start_main+0
[Kernel-packages] [Bug 1625232] Re: xgene i2c slimpro driver fails to load
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1625232 Title: xgene i2c slimpro driver fails to load Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Fix Released Status in linux source package in Zesty: Fix Released Bug description: [Impact] The X-Gene I2C slimpro driver fails to load, which is needed for ipmitool to communicate with the bmc, locally. [Test Case] Ensure the slimpro driver loads and that ipmitool can communicate with the bmc. [Regression Risk] The slimpro driver is a standalone, xgene driver, so any issues with it will only affect that platform. The patches were specified by APM as needed for local bmc access to work. Outside of the driver causing a crash, a regression in the driver itself would leave us in the same state we currently are, the driver not loading or no access to the bmc locally. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1625232/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1630554] Re: QEMU throws failure msg while booting guest with SRIOV VF
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1630554 Title: QEMU throws failure msg while booting guest with SRIOV VF Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Fix Committed Status in linux source package in Zesty: Fix Released Bug description: == Comment: #10 - VIPIN K. PARASHAR - 2016-10-04 02:39:30 == (In reply to comment #9) > I took a quick look to this one and also noticed these 2 links: > https://bugzilla.redhat.com/show_bug.cgi?id=1237034 > http://marc.info/?l=linux-kernel&m=143737274332400&w=2 > and it looks like to avoid these message maybe just need to have this in > config file: > CONFIG_KVM_VFIO=y > I think we have that in powerkvm but not in Ubuntu KVM. On x86 running Ubuntu 16.04 == $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04.1 LTS Release: 16.04 Codename: xenial $ head /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family: 6 model : 61 model name: Intel(R) Core(TM) i5-5300U CPU @ 2.30GHz stepping : 4 microcode : 0x22 cpu MHz : 2300.179 cache size: 3072 KB physical id : 0 $ uname -a Linux Workstation 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:42:33 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux $ grep CONFIG_KVM_VFIO /boot/config-4.4.0-38-generic CONFIG_KVM_VFIO=y $ On PowerPC # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Yakkety Yak (development branch) Release: 16.10 Codename: yakkety # head /proc/cpuinfo processor : 0 cpu : POWER8E (raw), altivec supported clock : 2061.00MHz revision : 2.1 (pvr 004b 0201) processor : 1 cpu : POWER8E (raw), altivec supported clock : 2061.00MHz revision : 2.1 (pvr 004b 0201) # uname -a Linux c158f2u09os 4.8.0-17-generic #19 SMP Thu Sep 29 12:03:21 CDT 2016 ppc64le ppc64le ppc64le GNU/Linux # grep CONFIG_KVM_VFIO /boot/config-4.8.0-17-generic # I see that CONFIG_KVM_VFIO is enabled on x86 running Ubuntu 16.04 while ppc64 running 16.10 doesn't have it enabled. == Comment: #9 - Carol L. Soto - 2016-09-30 16:25:32 == I took a quick look to this one and also noticed these 2 links: https://bugzilla.redhat.com/show_bug.cgi?id=1237034 http://marc.info/?l=linux-kernel&m=143737274332400&w=2 and it looks like to avoid these message maybe just need to have this in config file: CONFIG_KVM_VFIO=y I think we have that in powerkvm but not in Ubuntu KVM. == Comment: #6 - VIPIN K. PARASHAR - 2016-09-23 06:50:22 == $ git log 178a787502123b0 -1 commit 178a787502123b01499c5a4617b94bb69ad49dd5 Author: David Gibson Date: Mon Feb 1 11:14:15 2016 +1100 vfio: Enable VFIO device for powerpc ec53500f "kvm: Add VFIO device" added a special KVM pseudo-device which is used to handle any necessary interactions between KVM and VFIO. Currently that device is built on x86 and ARM, but not powerpc, although powerpc does support both KVM and VFIO. This makes things awkward in userspace Currently qemu prints an alarming error message if you attempt to use VFIO and it can't initialize the KVM VFIO device. We don't want to remove the warning, because lack of the KVM VFIO device could mean coherency problems on x86. On powerpc, however, the error is harmless but looks disturbing, and a test based on host architecture in qemu would be ugly, and break if we do need the KVM VFIO device for something important in future. There's nothing preventing the KVM VFIO device from being built for powerpc, so this patch turns it on. It won't actually do anything, since we don't define any of the arch_*() hooks, but it will make qemu happy and we can extend it in future if we need to. Signed-off-by: David Gibson Reviewed-by: Eric Auger Signed-off-by: Paul Mackerras $ $ git describe --contains 178a787502123b v4.6-rc1~141^2~49^2~20 $ Commit (178a7875) seems to have e
[Kernel-packages] [Bug 1559194] Re: Bad page state in process genwqe_gunzip pfn:3c275 in the genwqe device driver
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1559194 Title: Bad page state in process genwqe_gunzip pfn:3c275 in the genwqe device driver Status in Release Notes for Ubuntu: Fix Released Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Fix Committed Bug description: == Comment: #0 - Dmitry Gorbachev - 2016-03-17 08:52:41 == An error occurs when running zEDC compression/decompression and hotplugging PCI devices. There was 1G of memory, 2 pci functions and 50 threads of gunzipping enabled. Mar 14 23:59:01 s8330018 kernel: [ 4972.486883] BUG: Bad page state in process genwqe_gunzip pfn:3c275 Mar 14 23:59:01 s8330018 kernel: [ 4972.486888] page:03d100f09d40 count:-1 mapcount:0 mapping: (null) index:0x0 Mar 14 23:59:01 s8330018 kernel: [ 4972.486891] flags: 0x0() Mar 14 23:59:01 s8330018 kernel: [ 4972.486895] page dumped because: nonzero _count Mar 14 23:59:01 s8330018 kernel: [ 4972.486897] Modules linked in: xt_CHECKSUM(E) iptable_mangle(E) ipt_MASQUERADE(E) nf_nat_masquerade_ipv4(E) iptable_nat(E) nf_conntrack_ipv4(E) nf_defrag_ipv4(E) nf_nat_ipv4(E) nf_nat(E) nf_conntrack(E) xt_tcpudp(E) bridge(E) stp(E) llc(E) iptable_filter(E) ip_tables(E) x_tables(E) genwqe_card(E) crc_itu_t(E) qeth_l2(E) qeth(E) vmur(E) ccwgroup(E) dm_multipath(E) ib_iser(E) rdma_cm(E) iw_cm(E) ib_cm(E) ib_sa(E) ib_mad(E) ib_core(E) ib_addr(E) iscsi_tcp(E) libiscsi_tcp(E) libiscsi(E) scsi_transport_iscsi(E) btrfs(E) zlib_deflate(E) raid10(E) raid456(E) async_memcpy(E) async_raid6_recov(E) async_pq(E) async_xor(E) async_tx(E) xor(E) raid6_pq(E) libcrc32c(E) raid1(E) raid0(E) linear(E) ghash_s390(E) prng(E) aes_s390(E) des_s390(E) des_generic(E) sha512_s390(E) sha256_s390(E) sha1_s390(E) sha_common(E) zfcp(E) qdio(E) scsi_transport_fc(E) dasd_eckd_mod(E) dasd_mod(E) Mar 14 23:59:01 s8330018 kernel: [ 4972.486916] CPU: 0 PID: 37867 Comm: genwqe_gunzip Tainted: GW E 4.4.0-8-generic #23-Ubuntu Mar 14 23:59:01 s8330018 kernel: [ 4972.486916]209176f8 20917788 0002 Mar 14 23:59:01 s8330018 kernel: [ 4972.486916]20917828 209177a0 209177a0 00114182 Mar 14 23:59:01 s8330018 kernel: [ 4972.486916]0011 0092345a 03d1000a 000a Mar 14 23:59:01 s8330018 kernel: [ 4972.486916]209177e8 20917788 20914000 Mar 14 23:59:01 s8330018 kernel: [ 4972.486916] 00114182 20917788 209177e8 Mar 14 23:59:01 s8330018 kernel: [ 4972.486922] Call Trace: Mar 14 23:59:01 s8330018 kernel: [ 4972.486927] ([<0011406e>] show_trace+0xf6/0x148) Mar 14 23:59:01 s8330018 kernel: [ 4972.486929] [<00114136>] show_stack+0x76/0xe8 Mar 14 23:59:01 s8330018 kernel: [ 4972.486934] [<00518c26>] dump_stack+0x6e/0x90 Mar 14 23:59:01 s8330018 kernel: [ 4972.486937] [<0027c376>] bad_page+0xe6/0x148 Mar 14 23:59:01 s8330018 kernel: [ 4972.486938] [<00280516>] get_page_from_freelist+0x49e/0xba8 Mar 14 23:59:01 s8330018 kernel: [ 4972.486940] [<00280ede>] __alloc_pages_nodemask+0x166/0xb00 Mar 14 23:59:01 s8330018 kernel: [ 4972.486941] [<0015635a>] s390_dma_alloc+0x82/0x1a0 Mar 14 23:59:01 s8330018 kernel: [ 4972.486944] [<03ff805ea142>] __genwqe_alloc_consistent+0x7a/0x90 [genwqe_card] Mar 14 23:59:01 s8330018 kernel: [ 4972.486947] [<03ff805ea344>] genwqe_alloc_sync_sgl+0x17c/0x2e0 [genwqe_card] Mar 14 23:59:01 s8330018 kernel: [ 4972.486950] [<03ff805e52da>] do_execute_ddcb+0x1da/0x348 [genwqe_card] Mar 14 23:59:01 s8330018 kernel: [ 4972.486952] [<03ff805e5964>] genwqe_ioctl+0x51c/0xc20 [genwqe_card] Mar 14 23:59:01 s8330018 kernel: [ 4972.486953] [<003145ee>] do_vfs_ioctl+0x3b6/0x518 Mar 14 23:59:01 s8330018 kernel: [ 4972.486955] [<003147f4>] SyS_ioctl+0xa4/0xb8 Mar 14 23:59:01 s8330018 kernel: [ 4972.486956] [<007ad1be>] system_call+0xd6/0x264 Mar 14 23:59:01 s8330018 kernel: [ 4972.486957] [<03ffa9df2492>] 0x3ffa9df2492
[Kernel-packages] [Bug 1632739] Re: xgene merlin crashes when running as iperf server
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1632739 Title: xgene merlin crashes when running as iperf server Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: [Impact] The X-Gene Merlin board will hang and then crash. [Test Case] Have both the 1G and 10G interfaces connected, configured, and up. Bring down the 1G interface via 'ifconfig eth0 down'. Start the iperf server, i.e. iperf -s. From a separate system on the same 10G network, run the client, i.e. iperf -c <10G ip address for merlin board under test>. [Regression Risk] The patches are well tested, upstream and in yakkety, and only impacts the xgene enet driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1632739/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1632578] Re: Add support for KabeLake i219-LOM chips
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1632578 Title: Add support for KabeLake i219-LOM chips Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Fix Committed Bug description: There's a commit add device ids to support new i219 Lan-on- motherboard: commit deaa1d226af725d4e3a56527cdb506c3c30f9fd0 e1000e: Initial support for KabeLake [Impact] Add support for devices [8086:15e3], [8086:15d7], [8086:15d6], [8086:15d8]. This patch only add device ids so no further regressions are expected. [Test] Though the commit log says it's "Initial support", but it's been successfully tested on multiple platforms and no further issues are spotted, so at the moment no further patches are needed. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1632578/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1612006] Re: I2C touchpad does not work on AMD platform
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1612006 Title: I2C touchpad does not work on AMD platform Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Fix Committed Bug description: Recent AMD platform has problems with I2C touchpads because its GPIO controller is not configured correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1612006/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1638700] Re: hio: SSD data corruption under stress test
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: verification-needed-xenial
** Tags added: verification-needed-yakkety
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1638700
Title:
hio: SSD data corruption under stress test
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
Fix Committed
Status in linux source package in Yakkety:
Fix Committed
Status in linux source package in Zesty:
In Progress
Bug description:
{forward from James Troup}:
Just to followup to this with a little more information, we have now
reproduced this in the following scenarios:
* Ubuntu kernel 4.4 (i.e. 16.04) and kernel 4.8 (i.e. HWE-Y)
* With and without Bcache involved
* With both XFS and ext4
* With HIO driver versions 2.1.0-23 and 2.1.0-25
* With HIO Firmware 640 and 650
* With and without the following two patches
-
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/xenial/commit/?id=7290fa97b945c288d8dd8eb8f284b98cb495b35b
-
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/xenial/commit/?id=901a3142db778ddb9ed6a9000ce8e5b0f66c48ba
In all cases, we applied the following two patches in order to get hio
to build at all with a 4.4 or later kernel:
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/xenial/commit/?id=0abbb90372847caeeedeaa9db0f21e05ad8e9c74
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/xenial/commit/?id=a0705c5ff3d12fc31f18f5d3c8589eaaed1aa577
We've confirmed that we can reproduce the corruption on any machine in
Tele2's Vienna facility.
We've confirmed that, other than 1 machine, the 'hio_info' command
says the health is 'OK'.
Our most common reproducer is one of two scenarios:
a) http://paste.ubuntu.com/23405150/
b) http://paste.ubuntu.com/23405234/
In the last example, it's possible to see corruption faster by
increasing the 'count' argument to dd and avoid it by lowering it.
e.g. on the machine I'm currently testing on count=52450 doesn't
appear to show corruption, but a count of even 53000 would show it
immediately every time.
I hope this helps - please let us know what further information we can
provide to debug this problem.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1638700/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1637303] Re: Move some device drivers build from kernel built-in to modules
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- yakkety' to 'verification-done-yakkety'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-yakkety -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1637303 Title: Move some device drivers build from kernel built-in to modules Status in linux package in Ubuntu: Fix Released Status in linux source package in Yakkety: Fix Committed Status in linux source package in Zesty: Fix Released Bug description: Some drivers in Ubuntu are built as kernel built-in components, not allowing some module interesting features like blacklist on boot command-line or module removal/replacement. Also, modules has debug advantages compared to built-in kernel components, like the possibility to easy build custom-debug modules against kernel tree and replace them using modprobe on running system. This feature is a request to Canonical move some currently built-in drivers to module build system on Power platform, by changing the kernel config file. The drivers in question are: tg3, virtio-blk and virtio-net. The kernel config file parameters related to those 3 drivers are: CONFIG_TIGON3, CONFIG_VIRTIO_BLK and CONFIG_VIRTIO_NET. They all are currently set as "=y"; we're requesting a change to "=m". Thanks in advance, Guilherme To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1637303/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1637473] Re: cleanup primary tree for linux-hwe layering issues
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- yakkety' to 'verification-done-yakkety'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-yakkety -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1637473 Title: cleanup primary tree for linux-hwe layering issues Status in linux package in Ubuntu: Fix Released Status in linux source package in Yakkety: Fix Committed Bug description: We have some minor issues in the primary tree which are highlighted by delta comparison with linux-hwe. Fix them up. 1) Vcs-Git: still points to xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1637473/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- yakkety' to 'verification-done-yakkety'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-yakkety -- You 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: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Fix Committed 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 1633058] Re: ghash-clmulni-intel module fails to load
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: verification-needed-xenial
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1633058
Title:
ghash-clmulni-intel module fails to load
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Trusty:
Fix Committed
Status in linux source package in Xenial:
Fix Committed
Bug description:
The module ghash-clmulni-intel always fails to load with "Invalid
argument":
$ sudo modprobe ghash-clmulni-intel
modprobe: ERROR: could not insert 'ghash_clmulni_intel': Invalid argument
That was caused by the commit 8996eafdc ("crypto: ahash - ensure
statesize is non-zero"), that added a requirement that all ahash
algorithms now need to implement import() and export() and define a
non zero statesize.
The fix is composed by two commits:
3a020a7 crypto: ghash-clmulni - Fix load failure
1a07834 crypto: cryptd - Assign statesize properly
Xenial and Trusty are affected and Yakkety already included the
solution above.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633058/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1636330] Re: guest experiencing Transmit Timeouts on CX4
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- yakkety' to 'verification-done-yakkety'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-yakkety -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1636330 Title: guest experiencing Transmit Timeouts on CX4 Status in linux package in Ubuntu: Fix Released Status in linux source package in Yakkety: Fix Committed Status in linux source package in Zesty: Fix Released Bug description: This patch fixes a race condition that was reintroduced in the 4.8 kernel, as part of the P9 changes, after having been originally fixed in 3.19. The effect of the race condition is that a secondary thread can start trying to execute code from the guest while the thread is still in hypervisor mode, so it can cause many different symptoms, one of which seems to be the timebase corruption that leads to the lockup in ktime_get_ts64. It could cause other problems such as CPU cores locking up hard or memory corruption. This patch is only needed on the host. It should be applied to any 4.8 kernel being used as a host, including the Ubuntu 16.10 kernel. Hi Paul I built a kernel with your patch and put at the host and in the guest. I can still see some ktime_get_ts64 at the host. The guest dmesg is clean. This patch fixes another race condition I found in the fastsleep code. Please apply this patch as well and test. Sure will do and provide feedback. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1636330/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1634271] Re: arm64: kprobes disabled
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- yakkety' to 'verification-done-yakkety'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-yakkety -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1634271 Title: arm64: kprobes disabled Status in linux package in Ubuntu: Fix Released Status in linux source package in Yakkety: Fix Committed Status in linux source package in Zesty: Fix Released Bug description: [Impact] kprobes is currently enabled for all Ubuntu architectures except arm64. This excludes a useful debug feature, which is required by certain userspace provided by Ubuntu, such as perf's probe command. I failed to notice this in my yakkety config review because it is a new feature in v4.8. [Test Case] = Failure case = ubuntu@arm64:~$ sudo perf probe schedule kprobe_events file does not exist - please rebuild kernel with CONFIG_KPROBE_EVENTS. Error: Failed to add events. = Success case = ubuntu@arm64:~$ sudo perf probe schedule Added new event: probe:schedule (on schedule) You can now use it in all perf tools, such as: perf record -e probe:schedule -aR sleep 1 ubuntu@arm64:~$ sudo perf record -e probe:schedule -aR sleep 1 [ perf record: Woken up 1 times to write data ] [ perf record: Captured and wrote 0.185 MB perf.data (61 samples) ] [Regression Risk] The proposed fix enables a config for an already-upstream feature, so regressions will have upstream support. The config change mostly results in building new code vs. modifying existing code. The notable exception is that arm64's notify_page_fault() will now get code to call kprobe_fault_handler() - but only in the case that this newly enabled feature is being used (if kprobe_running()). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1634271/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1636517] Re: zfs: importing zpool with vdev on zvol hangs kernel
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: verification-needed-xenial
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1636517
Title:
zfs: importing zpool with vdev on zvol hangs kernel
Status in linux package in Ubuntu:
Triaged
Status in zfs-linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Fix Committed
Status in zfs-linux source package in Xenial:
Fix Committed
Status in linux source package in Yakkety:
Fix Committed
Status in zfs-linux source package in Yakkety:
Fix Committed
Status in linux source package in Zesty:
Triaged
Status in zfs-linux source package in Zesty:
Fix Released
Bug description:
[SRU Request][Xenial][Yakkety]
if a zvol of an existing, already imported zpool is a vdev of another
zpool, a call to "zpool import" will everything zfs related. the stack
trace is as follows:
[] taskq_wait+0x74/0xe0 [spl]
[] taskq_destroy+0x4b/0x100 [spl]
[] vdev_open_children+0x12d/0x180 [zfs]
[] vdev_root_open+0x3c/0xc0 [zfs]
[] vdev_open+0xf5/0x4d0 [zfs]
[] spa_load+0x39e/0x1c60 [zfs]
[] spa_tryimport+0xad/0x450 [zfs]
[] zfs_ioc_pool_tryimport+0x64/0xa0 [zfs]
[] zfsdev_ioctl+0x44b/0x4e0 [zfs]
[] do_vfs_ioctl+0x29f/0x490
[] SyS_ioctl+0x79/0x90
[] entry_SYSCALL_64_fastpath+0x16/0x71
[] 0x
[Fix]
zfsutils-linux:
Zesty: https://launchpadlibrarian.net/290907232/zfs-
linux_0.6.5.8-0ubuntu4_0.6.5.8-0ubuntu5.diff.gz
Yakkety, likewise
Xenial, likewise
Sync'd fixes into kernel repos, patches in:
http://kernel.ubuntu.com/~cking/zfs-lp-1636517
[Regression Potential]
Minimal. This just touched one line in the zfs module
module/zfs/zvol.cand a shim wrapper in include/linux/blkdev_compat.h
Tested and passes with the ubuntu kernel team autotest client zfs
regression tests.
=
I traced this back to 193fb6a2c94fab8eb8ce70a5da4d21c7d4023bee (erged
in 4.4.0-6.21), which added a second parameter to lookup_bdev without
patching the zfs module (which needs to special case the vdev-on-zvol
case, and uses this exact method only in this special casing code
path).
attached you can find the output of "zfs send -R" ing such a zvol
("brokenvol.raw"), running "zfs receive POOL/TARGET < FILE" followed
by "zpool import" should reproduce the hang.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-45-generic 4.4.0-45.66
ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
Uname: Linux 4.4.0-45-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Oct 25 15:46 seq
crw-rw 1 root audio 116, 33 Oct 25 15:46 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
Date: Tue Oct 25 15:49:51 2016
HibernationDevice: RESUME=/dev/mapper/xenial--vg-swap_1
InstallationDate: Installed on 2016-10-25 (0 days ago)
InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64
(20160719)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
PciMultimedia:
ProcFB: 0 qxldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-45-generic
root=/dev/mapper/hostname--vg-root ro
RelatedPackageVersions:
linux-restricted-modules-4.4.0-45-generic N/A
linux-backports-modules-4.4.0-45-generic N/A
linux-firmware1.157.4
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: rel-1.9.3-0-ge2fc41e-prebuilt.qemu-project.org
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-2.7
dmi.modalias:
dmi:bvnSeaBIOS:bvrrel-1.9.3-0-ge2fc41e-prebuilt.qemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.7:cvnQEMU:ct1:cvrpc-i440fx-2.7:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.
[Kernel-packages] [Bug 1630554] Re: QEMU throws failure msg while booting guest with SRIOV VF
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- yakkety' to 'verification-done-yakkety'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-yakkety -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1630554 Title: QEMU throws failure msg while booting guest with SRIOV VF Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Fix Committed Status in linux source package in Zesty: Fix Released Bug description: == Comment: #10 - VIPIN K. PARASHAR - 2016-10-04 02:39:30 == (In reply to comment #9) > I took a quick look to this one and also noticed these 2 links: > https://bugzilla.redhat.com/show_bug.cgi?id=1237034 > http://marc.info/?l=linux-kernel&m=143737274332400&w=2 > and it looks like to avoid these message maybe just need to have this in > config file: > CONFIG_KVM_VFIO=y > I think we have that in powerkvm but not in Ubuntu KVM. On x86 running Ubuntu 16.04 == $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04.1 LTS Release: 16.04 Codename: xenial $ head /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family: 6 model : 61 model name: Intel(R) Core(TM) i5-5300U CPU @ 2.30GHz stepping : 4 microcode : 0x22 cpu MHz : 2300.179 cache size: 3072 KB physical id : 0 $ uname -a Linux Workstation 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:42:33 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux $ grep CONFIG_KVM_VFIO /boot/config-4.4.0-38-generic CONFIG_KVM_VFIO=y $ On PowerPC # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Yakkety Yak (development branch) Release: 16.10 Codename: yakkety # head /proc/cpuinfo processor : 0 cpu : POWER8E (raw), altivec supported clock : 2061.00MHz revision : 2.1 (pvr 004b 0201) processor : 1 cpu : POWER8E (raw), altivec supported clock : 2061.00MHz revision : 2.1 (pvr 004b 0201) # uname -a Linux c158f2u09os 4.8.0-17-generic #19 SMP Thu Sep 29 12:03:21 CDT 2016 ppc64le ppc64le ppc64le GNU/Linux # grep CONFIG_KVM_VFIO /boot/config-4.8.0-17-generic # I see that CONFIG_KVM_VFIO is enabled on x86 running Ubuntu 16.04 while ppc64 running 16.10 doesn't have it enabled. == Comment: #9 - Carol L. Soto - 2016-09-30 16:25:32 == I took a quick look to this one and also noticed these 2 links: https://bugzilla.redhat.com/show_bug.cgi?id=1237034 http://marc.info/?l=linux-kernel&m=143737274332400&w=2 and it looks like to avoid these message maybe just need to have this in config file: CONFIG_KVM_VFIO=y I think we have that in powerkvm but not in Ubuntu KVM. == Comment: #6 - VIPIN K. PARASHAR - 2016-09-23 06:50:22 == $ git log 178a787502123b0 -1 commit 178a787502123b01499c5a4617b94bb69ad49dd5 Author: David Gibson Date: Mon Feb 1 11:14:15 2016 +1100 vfio: Enable VFIO device for powerpc ec53500f "kvm: Add VFIO device" added a special KVM pseudo-device which is used to handle any necessary interactions between KVM and VFIO. Currently that device is built on x86 and ARM, but not powerpc, although powerpc does support both KVM and VFIO. This makes things awkward in userspace Currently qemu prints an alarming error message if you attempt to use VFIO and it can't initialize the KVM VFIO device. We don't want to remove the warning, because lack of the KVM VFIO device could mean coherency problems on x86. On powerpc, however, the error is harmless but looks disturbing, and a test based on host architecture in qemu would be ugly, and break if we do need the KVM VFIO device for something important in future. There's nothing preventing the KVM VFIO device from being built for powerpc, so this patch turns it on. It won't actually do anything, since we don't define any of the arch_*() hooks, but it will make qemu happy and we can extend it in future if we need to. Signed-off-by: David Gibson Reviewed-by: Eric Auger Signed-off-by: Paul Mackerras $ $ git describe --contains 178a787502123b v4.6-rc1~141^2~49^2~20 $ Commit (178a7875) seems to hav
[Kernel-packages] [Bug 1633128] Re: ISST-LTE:pVM nvme 0000:a0:00.0: iommu_alloc failed on NVMe card
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: verification-needed-xenial
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1633128
Title:
ISST-LTE:pVM nvme :a0:00.0: iommu_alloc failed on NVMe card
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
Fix Committed
Status in linux source package in Yakkety:
Fix Committed
Bug description:
== Comment: #0 - Chanh H. Nguyen - 2016-06-02 14:22:00
==
There are a huge iommu_alloc failure on the dmesg log during our ST run on
the nvme card.
root@br502lp2:~# uname -r
4.4.0-22-generic
root@br502lp2:~# free -g
totalusedfree shared buff/cache
available
Mem:376 1 101 0 273
373
Swap:10 0 10
root@br502lp2:~# dmesg |grep "iommu_alloc"
[ 844.572656] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00
vaddr c001c1a7 npages 16
[ 844.572658] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00
vaddr c000c351 npages 16
[ 844.572664] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00
vaddr c023c026 npages 16
[ 844.572694] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00
vaddr c000c35b npages 16
[ 844.572700] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00
vaddr c001c1a7 npages 16
[ 844.572703] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00
vaddr c023c7a9 npages 16
[ 844.572718] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00
vaddr c000c35b npages 16
[ 844.572727] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00
vaddr c001c1a7 npages 16
[ 844.572730] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00
vaddr c023c7a9 npages 16
[ 844.572746] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00
vaddr c023c7a9 npages 16
[ 1033.500635] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00
vaddr c02a6450 npages 16
[ 1033.500894] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00
vaddr c02a6450 npages 16
[ 1033.501290] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00
vaddr c03b80d1 npages 16
[ 1033.501337] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00
vaddr c0290391 npages 16
[ 1033.501590] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00
root@br502lp2:~# cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinux-4.4.0-22-generic
root=UUID=2852021a-6954-42a9-8c69-7a58ccfbb65d ro xmon=on disable_ddw splash
quiet crashkernel=384M-:128M
root@br502lp2:~# lsmcode
Version of System Firmware is FW840.20 (SC840_100) (t) FW840.10 (SC840_079)
(p) FW840.20 (SC840_100) (b)
Version of PFW is 14492016042881CF0681
== Comment: #4 - Mauricio Faria De Oliveira -
2016-10-13 10:16:40 ==
Hi Canonical,
This patch series that resolves this problem made linux mainline in the 4.9
merge window:
("dma-mapping, powerpc, nvme: introduce the DMA_ATTR_NO_WARN attribute")
Can you please apply it on 16.04.x?
Thanks!
Links/commits
---
[1] "dma-mapping: introduce the DMA_ATTR_NO_WARN attribute"
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=a9a62c9384417545620aee1b5ad1d9357350c17a
[2] "powerpc: implement the DMA_ATTR_NO_WARN attribute"
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=af8a24988e48f9ed20acf4d5230ac216d5baf723
[3] "nvme: use the DMA_ATTR_NO_WARN attribute"
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=2b6b535d9158b822a45080b3d6d5b2993fd49e5a
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633128/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1642192] Re: i386 4.9 in -proposed fails to boot in cloud instances
** 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/1642192 Title: i386 4.9 in -proposed fails to boot in cloud instances Status in linux package in Ubuntu: Confirmed Bug description: I noticed a forever-looping test of linuxinfo on i386 this morning. This test upgrades the kernel to 4.9 in -proposed; as soon as that reboots, the VM never comes back. nova console-log shows: [1.581188] Freeing unused kernel memory: 996K (dcc37000 - dcd3) [1.582525] Write protecting the kernel text: 8300k [1.583624] Write protecting the kernel read-only data: 3344k [1.584845] NX-protecting the kernel data: 6036k [1.585921] [ cut here ] [1.586861] WARNING: CPU: 0 PID: 1 at /build/linux-UWDXbt/linux-4.9.0/arch/x86/mm/dump_pagetables.c:225 note_page+0x6a1/0x880 [1.589199] x86/mm: Found insecure W+X mapping at address c00a/0xc00a [1.590657] Modules linked in: [1.591305] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.9.0-1-generic #2-Ubuntu [1.592809] Hardware name: OpenStack Foundation OpenStack Nova, BIOS Bochs 01/01/2011 [1.593188] dae89e70 dc3e0b05 dae89eb4 dca47958 dae89ea0 dc07299a dca47920 dae89ed4 [1.593188] 0001 dca47958 00e1 dc068db1 00e1 dae89f34 8000 [1.593188] dae89ec0 dc072a06 0009 dae89eb4 dca47920 dae89ed4 76601e21 [1.593188] Call Trace: [1.593188] [] dump_stack+0x58/0x73 [1.593188] [] __warn+0xea/0x110 [1.593188] [] ? note_page+0x6a1/0x880 [1.593188] [] warn_slowpath_fmt+0x46/0x60 [1.593188] [] note_page+0x6a1/0x880 [1.593188] [] ptdump_walk_pgd_level_core+0x1f5/0x300 [1.593188] [] ptdump_walk_pgd_level_checkwx+0x16/0x20 [1.593188] [] mark_rodata_ro+0xfd/0x130 [1.593188] [] ? rest_init+0x70/0x70 [1.593188] [] kernel_init+0x2c/0x100 [1.593188] [] ? schedule_tail+0x11/0x50 [1.593188] [] ? rest_init+0x70/0x70 [1.593188] [] ret_from_fork+0x1b/0x28 [1.613361] ---[ end trace d63b34644638754d ]--- [1.614368] x86/mm: Checked W+X mappings: FAILED, 96 W+X pages found. ... Begin: Waiting for root file system ... Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. [... repeating some 50 times... ] Begin: Running /scripts/local-block ... done. done. Gave up waiting for root device. Common problems: - Boot args (cat /proc/cmdline) - Check rootdelay= (did the system wait long enough?) - Check root= (did the system wait for the right device?) - Missing modules (cat /proc/modules; ls /dev) ALERT! UUID=ac6eb865-17d6-469d-b58e-8c0d49174fe4 does not exist. Dropping to a shell! BusyBox v1.22.1 (Ubuntu 1:1.22.0-19ubuntu2) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1642192/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1638700] Re: hio: SSD data corruption under stress test
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1638700
Title:
hio: SSD data corruption under stress test
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
Fix Committed
Status in linux source package in Yakkety:
Fix Committed
Status in linux source package in Zesty:
In Progress
Bug description:
{forward from James Troup}:
Just to followup to this with a little more information, we have now
reproduced this in the following scenarios:
* Ubuntu kernel 4.4 (i.e. 16.04) and kernel 4.8 (i.e. HWE-Y)
* With and without Bcache involved
* With both XFS and ext4
* With HIO driver versions 2.1.0-23 and 2.1.0-25
* With HIO Firmware 640 and 650
* With and without the following two patches
-
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/xenial/commit/?id=7290fa97b945c288d8dd8eb8f284b98cb495b35b
-
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/xenial/commit/?id=901a3142db778ddb9ed6a9000ce8e5b0f66c48ba
In all cases, we applied the following two patches in order to get hio
to build at all with a 4.4 or later kernel:
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/xenial/commit/?id=0abbb90372847caeeedeaa9db0f21e05ad8e9c74
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/xenial/commit/?id=a0705c5ff3d12fc31f18f5d3c8589eaaed1aa577
We've confirmed that we can reproduce the corruption on any machine in
Tele2's Vienna facility.
We've confirmed that, other than 1 machine, the 'hio_info' command
says the health is 'OK'.
Our most common reproducer is one of two scenarios:
a) http://paste.ubuntu.com/23405150/
b) http://paste.ubuntu.com/23405234/
In the last example, it's possible to see corruption faster by
increasing the 'count' argument to dd and avoid it by lowering it.
e.g. on the machine I'm currently testing on count=52450 doesn't
appear to show corruption, but a count of even 53000 would show it
immediately every time.
I hope this helps - please let us know what further information we can
provide to debug this problem.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1638700/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1635594] Re: [yakkety] hio driver missing
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- yakkety' to 'verification-done-yakkety'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-yakkety -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1635594 Title: [yakkety] hio driver missing Status in linux package in Ubuntu: In Progress Status in linux source package in Yakkety: Fix Committed Status in linux source package in Zesty: In Progress Bug description: == SRU Justification == Huawei servers, including Huawei PCIe SSD's require the hio driver which is currently not included in our kernels. We would like to carry this driver in our kernels for Xenial and newer in order to support platforms with these drives. This was original ported to Xenial and is now missing in Yakkety creating a regression in that release. == Source == http://support.huawei.com/enterprisesearch/ebgSearch#sp.keyword=HUAWEI%20ES3000%20V2%20Driver%20SRC == Testing == The reporter has hardware to test these kernels. == Regression potential == The driver does not exist currently, so no regression potential exists in Yakkety. Upgrades from Xenial are currently regressing and will need to be tested. --- The hio ubuntu driver in Xenial seems to be MIA in yakkety. Reported to us by Elmo. --- Kernel-Description: hio Ubuntu sauce driver needs porting to 4.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1635594/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1637526] Re: [Feature] AVX-512 new instruction sets (avx512_4vnniw, avx512_4fmaps)
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- yakkety' to 'verification-done-yakkety'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-yakkety -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1637526 Title: [Feature] AVX-512 new instruction sets (avx512_4vnniw, avx512_4fmaps) Status in intel: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Yakkety: Fix Committed Bug description: The following instruction set are extension to AVX512 on Intel's Xeon and Xoen Phi processors: • avx512_4vnniw - Vector instructions for deep learning enhanced word variable precision. • avx512_4fmaps - Vector instructions for deep learning floating-point single precision. We will detect the features in CPUID:eax=7:ecx=0->edx[2:3]. Patch merged in 4.9rc-2 http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=8214899342981dbd49ae24aadbbd19e9e7830684 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1637526/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1636517] Re: zfs: importing zpool with vdev on zvol hangs kernel
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: verification-needed-yakkety
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1636517
Title:
zfs: importing zpool with vdev on zvol hangs kernel
Status in linux package in Ubuntu:
Triaged
Status in zfs-linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Fix Committed
Status in zfs-linux source package in Xenial:
Fix Committed
Status in linux source package in Yakkety:
Fix Committed
Status in zfs-linux source package in Yakkety:
Fix Committed
Status in linux source package in Zesty:
Triaged
Status in zfs-linux source package in Zesty:
Fix Released
Bug description:
[SRU Request][Xenial][Yakkety]
if a zvol of an existing, already imported zpool is a vdev of another
zpool, a call to "zpool import" will everything zfs related. the stack
trace is as follows:
[] taskq_wait+0x74/0xe0 [spl]
[] taskq_destroy+0x4b/0x100 [spl]
[] vdev_open_children+0x12d/0x180 [zfs]
[] vdev_root_open+0x3c/0xc0 [zfs]
[] vdev_open+0xf5/0x4d0 [zfs]
[] spa_load+0x39e/0x1c60 [zfs]
[] spa_tryimport+0xad/0x450 [zfs]
[] zfs_ioc_pool_tryimport+0x64/0xa0 [zfs]
[] zfsdev_ioctl+0x44b/0x4e0 [zfs]
[] do_vfs_ioctl+0x29f/0x490
[] SyS_ioctl+0x79/0x90
[] entry_SYSCALL_64_fastpath+0x16/0x71
[] 0x
[Fix]
zfsutils-linux:
Zesty: https://launchpadlibrarian.net/290907232/zfs-
linux_0.6.5.8-0ubuntu4_0.6.5.8-0ubuntu5.diff.gz
Yakkety, likewise
Xenial, likewise
Sync'd fixes into kernel repos, patches in:
http://kernel.ubuntu.com/~cking/zfs-lp-1636517
[Regression Potential]
Minimal. This just touched one line in the zfs module
module/zfs/zvol.cand a shim wrapper in include/linux/blkdev_compat.h
Tested and passes with the ubuntu kernel team autotest client zfs
regression tests.
=
I traced this back to 193fb6a2c94fab8eb8ce70a5da4d21c7d4023bee (erged
in 4.4.0-6.21), which added a second parameter to lookup_bdev without
patching the zfs module (which needs to special case the vdev-on-zvol
case, and uses this exact method only in this special casing code
path).
attached you can find the output of "zfs send -R" ing such a zvol
("brokenvol.raw"), running "zfs receive POOL/TARGET < FILE" followed
by "zpool import" should reproduce the hang.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-45-generic 4.4.0-45.66
ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
Uname: Linux 4.4.0-45-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Oct 25 15:46 seq
crw-rw 1 root audio 116, 33 Oct 25 15:46 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
Date: Tue Oct 25 15:49:51 2016
HibernationDevice: RESUME=/dev/mapper/xenial--vg-swap_1
InstallationDate: Installed on 2016-10-25 (0 days ago)
InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64
(20160719)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
PciMultimedia:
ProcFB: 0 qxldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-45-generic
root=/dev/mapper/hostname--vg-root ro
RelatedPackageVersions:
linux-restricted-modules-4.4.0-45-generic N/A
linux-backports-modules-4.4.0-45-generic N/A
linux-firmware1.157.4
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: rel-1.9.3-0-ge2fc41e-prebuilt.qemu-project.org
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-2.7
dmi.modalias:
dmi:bvnSeaBIOS:bvrrel-1.9.3-0-ge2fc41e-prebuilt.qemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.7:cvnQEMU:ct1:cvrpc-i440fx-2.7:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.produ
[Kernel-packages] [Bug 1635656] Re: SRU: sync zfsutils-linux and spl-linux changes to linux
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- yakkety' to 'verification-done-yakkety'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-yakkety -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1635656 Title: SRU: sync zfsutils-linux and spl-linux changes to linux Status in linux package in Ubuntu: Fix Released Status in linux source package in Yakkety: Fix Committed Bug description: [SRU Justification][Yakkety] SPL (spl-linux) is currently now sync'd to Debian and ZFS has been updated to -0ubuntu4, so sync these changes to yakkety as a SRU. Changes to the kernel are minimal, just to spl/module/spl/spl- generic.c, where a redundant (and somewhat alarming) warning message has been removed. Other than that, the changes are just to do with the autotools config scripts. I've build and tested these changes against the kernel-team autotest-client-tests ZFS regression tests and no regressions have been found. [Test case] Run against all the kernel-team autotest-client-tests ZFS regression tests - all should pass [Regression Potential] 1. Minor changes to autotools config scripts - however these have been tested and will only affect the build and not the run time binary 2. No major code change to drivers except for removing a redundant warning message that should not be issued, so only this may break any weird code that is scraping the kernel log for such non-standard messages (which is not expected). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1635656/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1632045] Re: KVM: PPC: Book3S HV: Migrate pinned pages out of CMA
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- yakkety' to 'verification-done-yakkety'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-yakkety -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1632045 Title: KVM: PPC: Book3S HV: Migrate pinned pages out of CMA Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Fix Committed Status in linux source package in Zesty: Fix Released Bug description: ---Problem Description--- https://github.com/open-power/supermicro-openpower/issues/59 SW/HW Configuration PNOR image version: 5/3/2016 BMC image version: 0.25 CPLD Version: B2.81.01 Host OS version: Ubuntu 16.04 LTS UbuntuKVM Guest OS version: Ubuntu 14.04.4 LTS HTX version: 394 Processor: 00UL865 * 2 Memory: SK hynix 16GB 2Rx4 PC4-2133P * 16 Summary of Issue Two UbuntuKVM guests are each configured with 8 processors, 64 GB of memory, 1 disk of 128 GB, 1 network interface, and 1 GPU (pass- through'd from the Host OS's K80). The two guests are each put into a Create/Destroy loop, with HTX running on each of the guests (NOT HOST) in between its creation and destruction. The mdt.bu profile is used, and the processors, memory, and the GPU are put under load. The HTX session lasts 9 minutes. While this is running, the amount of available memory (free memory) in the Host OS will slowly decrease, and this can continue until the point wherein there's no more free memory for the Host OS to do anything, including creating the two VM guests. It seems to be that after every cycle, a small portion of the memory that was allocated to the VM guest does not get released back to the Host OS, and eventually, this can and will add up to take up all the available memory in the Host OS. At some point, the VM guest(s) might get disconnected and will display the following error: error: Disconnected from qemu:///system due to I/O error error: One or more references were leaked after disconnect from the hypervisor Then, when the Host OS tries to start the VM guest again, the following error shows up: error: Failed to create domain from guest2_trusty.xml error: internal error: early end of file from monitor, possible problem: Unexpected error in spapr_alloc_htab() at /build/qemu-c3ZrbA/qemu-2.5+dfsg/hw/ppc/spapr.c:1030: 2016-05-23T16:18:16.871549Z qemu-system-ppc64: Failed to allocate HTAB of requested size, try with smaller maxmem The Host OS syslog, as seen HERE, also contains quite some errors. To just list a few: May 13 20:27:44 191-136 kernel: [36827.151228] alloc_contig_range: [3fb800, 3fd8f8) PFNs busy May 13 20:27:44 191-136 kernel: [36827.151291] alloc_contig_range: [3fb800, 3fd8fc) PFNs busy May 13 20:27:44 191-136 libvirtd[19263]: *** Error in `/usr/sbin/libvirtd': realloc(): invalid next size: 0x01000a780400 *** May 13 20:27:44 191-136 libvirtd[19263]: === Backtrace: = May 13 20:27:44 191-136 libvirtd[19263]: /lib/powerpc64le-linux-gnu/libc.so.6(+0x8720c)[0x3fffaf6a720c] May 13 20:27:44 191-136 libvirtd[19263]: /lib/powerpc64le-linux-gnu/libc.so.6(+0x96f70)[0x3fffaf6b6f70] May 13 20:27:44 191-136 libvirtd[19263]: /lib/powerpc64le-linux-gnu/libc.so.6(realloc+0x16c)[0x3fffaf6b87fc] May 13 20:27:44 191-136 libvirtd[19263]: /usr/lib/powerpc64le-linux-gnu/libvirt.so.0(virReallocN+0x68)[0x3fffaf90ccc8] May 13 20:27:44 191-136 libvirtd[19263]: /usr/lib/libvirt/connection-driver/libvirt_driver_qemu.so(+0x8ef6c)[0x3fff9346ef6c] May 13 20:27:44 191-136 libvirtd[19263]: /usr/lib/libvirt/connection-driver/libvirt_driver_qemu.so(+0xa826c)[0x3fff9348826c] May 13 20:27:44 191-136 libvirtd[19263]: /usr/lib/powerpc64le-linux-gnu/libvirt.so.0(virEventPollRunOnce+0x8b4)[0x3fffaf9332b4] May 13 20:27:44 191-136 libvirtd[19263]: /usr/lib/powerpc64le-linux-gnu/libvirt.so.0(virEventRunDefaultImpl+0x54)[0x3fffaf931334] May 13 20:27:44 191-136 libvirtd[19263]: /usr/lib/powerpc64le-linux-gnu/libvirt.so.0(virNetDaemonRun+0x1f0)[0x3fffafad2f70] May 13 20:27:44 191-136 libvirtd[19263]: /usr/sbin/libvirtd(+0x15d74)[0x52e45d74] May 13 20:27:44 191-136 libvirtd[19263]: /lib/powerpc64le-linux-gnu/libc.so.6(+0x2319c)[0x3fffaf64319c] May 13 20:27:44 191-136 libvirtd[19263]: /lib/powerpc64le-linux-gnu/libc.so.6(__libc_start_mai
[Kernel-packages] [Bug 1633128] Re: ISST-LTE:pVM nvme 0000:a0:00.0: iommu_alloc failed on NVMe card
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: verification-needed-yakkety
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1633128
Title:
ISST-LTE:pVM nvme :a0:00.0: iommu_alloc failed on NVMe card
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
Fix Committed
Status in linux source package in Yakkety:
Fix Committed
Bug description:
== Comment: #0 - Chanh H. Nguyen - 2016-06-02 14:22:00
==
There are a huge iommu_alloc failure on the dmesg log during our ST run on
the nvme card.
root@br502lp2:~# uname -r
4.4.0-22-generic
root@br502lp2:~# free -g
totalusedfree shared buff/cache
available
Mem:376 1 101 0 273
373
Swap:10 0 10
root@br502lp2:~# dmesg |grep "iommu_alloc"
[ 844.572656] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00
vaddr c001c1a7 npages 16
[ 844.572658] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00
vaddr c000c351 npages 16
[ 844.572664] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00
vaddr c023c026 npages 16
[ 844.572694] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00
vaddr c000c35b npages 16
[ 844.572700] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00
vaddr c001c1a7 npages 16
[ 844.572703] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00
vaddr c023c7a9 npages 16
[ 844.572718] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00
vaddr c000c35b npages 16
[ 844.572727] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00
vaddr c001c1a7 npages 16
[ 844.572730] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00
vaddr c023c7a9 npages 16
[ 844.572746] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00
vaddr c023c7a9 npages 16
[ 1033.500635] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00
vaddr c02a6450 npages 16
[ 1033.500894] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00
vaddr c02a6450 npages 16
[ 1033.501290] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00
vaddr c03b80d1 npages 16
[ 1033.501337] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00
vaddr c0290391 npages 16
[ 1033.501590] nvme 0001:01:00.0: iommu_alloc failed, tbl c0466a2bfc00
root@br502lp2:~# cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinux-4.4.0-22-generic
root=UUID=2852021a-6954-42a9-8c69-7a58ccfbb65d ro xmon=on disable_ddw splash
quiet crashkernel=384M-:128M
root@br502lp2:~# lsmcode
Version of System Firmware is FW840.20 (SC840_100) (t) FW840.10 (SC840_079)
(p) FW840.20 (SC840_100) (b)
Version of PFW is 14492016042881CF0681
== Comment: #4 - Mauricio Faria De Oliveira -
2016-10-13 10:16:40 ==
Hi Canonical,
This patch series that resolves this problem made linux mainline in the 4.9
merge window:
("dma-mapping, powerpc, nvme: introduce the DMA_ATTR_NO_WARN attribute")
Can you please apply it on 16.04.x?
Thanks!
Links/commits
---
[1] "dma-mapping: introduce the DMA_ATTR_NO_WARN attribute"
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=a9a62c9384417545620aee1b5ad1d9357350c17a
[2] "powerpc: implement the DMA_ATTR_NO_WARN attribute"
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=af8a24988e48f9ed20acf4d5230ac216d5baf723
[3] "nvme: use the DMA_ATTR_NO_WARN attribute"
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=2b6b535d9158b822a45080b3d6d5b2993fd49e5a
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633128/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1636847] Re: unexpectedly large memory usage of mounted snaps
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- yakkety' to 'verification-done-yakkety'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-yakkety -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1636847 Title: unexpectedly large memory usage of mounted snaps Status in Snappy: New Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Released Status in linux source package in Yakkety: Fix Committed Status in linux source package in Zesty: Fix Committed Bug description: This is a tracking bug for what might be kernel bugs or kernel configuration changes. As described [1], memory used by simply mounting a squashfs file (even an empty one) is ranging from almost nothing (on certain distributions) to 131MB on Ubuntu 16.04 and 16.10 on a single-core machine or VM. The amount is excessive and should be investigated by the kernel team. We may need to change the kernel or at least the configuration we ship in our packages and kernel snaps. [1] https://github.com/zyga/mounted-fs-memory-checker To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1636847/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1634705] Re: Add ipvlan module to 16.04 kernel
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- yakkety' to 'verification-done-yakkety'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-yakkety -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1634705 Title: Add ipvlan module to 16.04 kernel Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Fix Committed Status in linux source package in Zesty: Fix Released Bug description: Currently, ipvlan is included in the linux-image-extra package however users have requested that it be included as a module in the primary kernel package. Users running docker with mesos require ipvlan for container networking to function (and likely other container use cases). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1634705/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1636733] Re: [LTCTest] vfio_pci not loaded on Ubuntu 16.10 by default
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- yakkety' to 'verification-done-yakkety'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-yakkety -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1636733 Title: [LTCTest] vfio_pci not loaded on Ubuntu 16.10 by default Status in linux package in Ubuntu: Fix Released Status in kernel-package source package in Xenial: New Status in linux source package in Xenial: Fix Committed Status in kernel-package source package in Yakkety: New Status in linux source package in Yakkety: Fix Committed Status in kernel-package source package in Zesty: Invalid Status in linux source package in Zesty: Fix Released Bug description: == Comment: #0 - SRIKANTH B. AITHAL - 2016-10-26 01:40:39 == ---Problem Description--- vfio_pci is not loaded by default on Ubuntu 16.10 host boot. All VFIO related tasks would fail without that module. For instance I was trying to boot guest with QEMU directly and it was failing complaining "/sys/bus/pci/drivers/vfio-pci/new_id" not present. root@c158f2u09os:~# lsmod | grep -i vfio root@c158f2u09os:~# modprobe vfio_pci <-- need to load explicitly root@c158f2u09os:~# lsmod | grep -i vfio vfio_pci 51735 0 irqbypass 5567 1 vfio_pci vfio_iommu_spapr_tce14567 0 vfio_virqfd 4859 1 vfio_pci vfio 31351 2 vfio_iommu_spapr_tce,vfio_pci vfio_spapr_eeh 3441 2 vfio_iommu_spapr_tce,vfio_pci Either > we need to have these modules loaded by kernel by default or > we need to update https://wiki.ubuntu.com/ppc64el/CommonQuestions telling customers to load vfio_pci module explicitly before attempting any vfio tasks. Contact Information = Srikanth/bssrika...@in.ibm.com ---uname output--- Linux c158f2u09os 4.8.0-26-generic #28-Ubuntu SMP Tue Oct 18 14:41:40 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux Machine Type = 8247-22L ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. After booting into Ubuntu 16.10, see if vfio_pci modules are loaded: root@c158f2u09os:~# lsmod | grep -i vfio 2. After that we need to manually load vfio_pci root@c158f2u09os:~# modprobe vfio_pci root@c158f2u09os:~# To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1636733/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1630774] Re: kernel invalid opcode in intel_powerclamp
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: verification-needed-yakkety
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1630774
Title:
kernel invalid opcode in intel_powerclamp
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Yakkety:
Fix Committed
Bug description:
kernel error on VMware Fusion when booting to graphical login
invalid opcode: [#1] SMP
Modules linked in: ipmi_msghandler intel_powerclamp coretemp crct10dif_pclmul
crc32_pclmul ghash_clmulni_intel vmw_balloon aesni_intel aes_x86_64 lrw
glue_helper ablk_helper cryptd intel_rapl_perf joydev input_leds serio_raw
snd_ens1371 snd_ac97_codec gameport ac97_bus snd_pcm binfmt_misc snd_seq_midi
snd_seq_midi_event snd_rawmidi uvcvideo videobuf2_vmalloc videobuf2_memops
videobuf2_v4l2 videobuf2_core videodev media snd_seq btusb btrtl btbcm
snd_seq_device btintel snd_timer bluetooth snd soundcore shpchp i2c_piix4
vmw_vmci nfit floppy(+) mac_hid parport_pc ppdev lp parport ip_tables x_tables
autofs4 hid_generic usbhid hid psmouse vmwgfx ttm drm_kms_helper syscopyarea
sysfillrect sysimgblt fb_sys_fops drm ahci libahci e1000 mptspi mptscsih
mptbase scsi_transport_spi pata_acpi fjes
CPU: 0 PID: 806 Comm: kidle_inject/0 Not tainted 4.8.0-19-generic #21-Ubuntu
Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference
Platform, BIOS 6.00 07/02/2015
task: 9e70f1ce1c80 task.stack: 9e70f679
RIP: 0010:[] [] clamp_thread+0x2b8/0x5d0
[intel_powerclamp]
RSP: 0018:9e70f6793e00 EFLAGS: 00010246
RAX: 9e70f6790008 RBX: fffee2fe RCX:
RDX: RSI: 0246 RDI: 0246
RBP: 9e70f6793ec0 R08: 9e70f679 R09:
R10: afb504000afb5041 R11: 9e70fa619ac0 R12: 93958160
R13: 9e70f679 R14: R15: 9e70f679
FS: () GS:9e70fa60() knlGS:
CS: 0010 DS: ES: CR0: 80050033
CR2: 7ffd50464ff8 CR3: b89db000 CR4: 001406f0
Stack:
0005 c073e5d8 c073ea40
0003 9e70f6790008
9e70fa60ff68 fffee2fe c073c0a0
Call Trace:
[] ? pkg_state_counter+0xa0/0xa0 [intel_powerclamp]
[] ? powerclamp_set_cur_state+0x170/0x170
[intel_powerclamp]
[] ? powerclamp_set_cur_state+0x170/0x170
[intel_powerclamp]
[] kthread+0xd8/0xf0
[] ret_from_fork+0x1f/0x40
[] ? kthread_create_on_node+0x1e0/0x1e0
Code: d2 e9 ba 00 00 00 eb 19 0f 1f 00 0f ae f0 65 48 8b 04 25 04 69 01 00 0f
ae b8 08 c0 ff ff 0f ae f0 31 d2 48 8b 44 24 38 48 89 d1 <0f> 01 c8 49 8b 45 08
a8 08 75 0b b9 01 00 00 00 4c 89 f0 0f 01
RIP [] clamp_thread+0x2b8/0x5d0 [intel_powerclamp]
RSP
---[ end trace fb2ec9f1e269d231 ]---
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1630774/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1621088] Re: Fix bugs under virtual scsi server driver for Power
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- yakkety' to 'verification-done-yakkety'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-yakkety -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1621088 Title: Fix bugs under virtual scsi server driver for Power Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: Fix Released Status in linux source package in Yakkety: Fix Committed Bug description: == Comment: #0 - BRYANT G. LY - 2016-09-06 12:16:14 == All three of these have been accepted into the 4.9/scsi-queue and scsi tree under misc ibmvscsis: Properly deregister target sessions - http://git.kernel.org/cgit/linux/kernel/git/jejb/scsi.git/commit/?id=712db3eb2c35e79986268bcd694ba8075445737d ibmvscsis: Code cleanup of print statements - http://git.kernel.org/cgit/linux/kernel/git/jejb/scsi.git/commit/?id=812902159d4174df9a82948c0445becb865dabec ibmvscsis: Fixed a bug reported by Dan Carpenter - http://git.kernel.org/cgit/linux/kernel/git/jejb/scsi.git/commit/?id=f6dbe38edf1ef4929847c90e244204ef4c6b3ce7 Still pending Review in target-devel mailing list: target/user: Return TCMU-generated sense data to fabric module - Is still under review under scsi and target-devel mailing list. http://www.spinics.net/lists/target-devel/msg13449.html TCM-User fixes and cleanups - http://www.spinics.net/lists/target-devel/msg13444.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1621088/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1559194] Re: Bad page state in process genwqe_gunzip pfn:3c275 in the genwqe device driver
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- yakkety' to 'verification-done-yakkety'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-yakkety -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1559194 Title: Bad page state in process genwqe_gunzip pfn:3c275 in the genwqe device driver Status in Release Notes for Ubuntu: Fix Released Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Fix Committed Bug description: == Comment: #0 - Dmitry Gorbachev - 2016-03-17 08:52:41 == An error occurs when running zEDC compression/decompression and hotplugging PCI devices. There was 1G of memory, 2 pci functions and 50 threads of gunzipping enabled. Mar 14 23:59:01 s8330018 kernel: [ 4972.486883] BUG: Bad page state in process genwqe_gunzip pfn:3c275 Mar 14 23:59:01 s8330018 kernel: [ 4972.486888] page:03d100f09d40 count:-1 mapcount:0 mapping: (null) index:0x0 Mar 14 23:59:01 s8330018 kernel: [ 4972.486891] flags: 0x0() Mar 14 23:59:01 s8330018 kernel: [ 4972.486895] page dumped because: nonzero _count Mar 14 23:59:01 s8330018 kernel: [ 4972.486897] Modules linked in: xt_CHECKSUM(E) iptable_mangle(E) ipt_MASQUERADE(E) nf_nat_masquerade_ipv4(E) iptable_nat(E) nf_conntrack_ipv4(E) nf_defrag_ipv4(E) nf_nat_ipv4(E) nf_nat(E) nf_conntrack(E) xt_tcpudp(E) bridge(E) stp(E) llc(E) iptable_filter(E) ip_tables(E) x_tables(E) genwqe_card(E) crc_itu_t(E) qeth_l2(E) qeth(E) vmur(E) ccwgroup(E) dm_multipath(E) ib_iser(E) rdma_cm(E) iw_cm(E) ib_cm(E) ib_sa(E) ib_mad(E) ib_core(E) ib_addr(E) iscsi_tcp(E) libiscsi_tcp(E) libiscsi(E) scsi_transport_iscsi(E) btrfs(E) zlib_deflate(E) raid10(E) raid456(E) async_memcpy(E) async_raid6_recov(E) async_pq(E) async_xor(E) async_tx(E) xor(E) raid6_pq(E) libcrc32c(E) raid1(E) raid0(E) linear(E) ghash_s390(E) prng(E) aes_s390(E) des_s390(E) des_generic(E) sha512_s390(E) sha256_s390(E) sha1_s390(E) sha_common(E) zfcp(E) qdio(E) scsi_transport_fc(E) dasd_eckd_mod(E) dasd_mod(E) Mar 14 23:59:01 s8330018 kernel: [ 4972.486916] CPU: 0 PID: 37867 Comm: genwqe_gunzip Tainted: GW E 4.4.0-8-generic #23-Ubuntu Mar 14 23:59:01 s8330018 kernel: [ 4972.486916]209176f8 20917788 0002 Mar 14 23:59:01 s8330018 kernel: [ 4972.486916]20917828 209177a0 209177a0 00114182 Mar 14 23:59:01 s8330018 kernel: [ 4972.486916]0011 0092345a 03d1000a 000a Mar 14 23:59:01 s8330018 kernel: [ 4972.486916]209177e8 20917788 20914000 Mar 14 23:59:01 s8330018 kernel: [ 4972.486916] 00114182 20917788 209177e8 Mar 14 23:59:01 s8330018 kernel: [ 4972.486922] Call Trace: Mar 14 23:59:01 s8330018 kernel: [ 4972.486927] ([<0011406e>] show_trace+0xf6/0x148) Mar 14 23:59:01 s8330018 kernel: [ 4972.486929] [<00114136>] show_stack+0x76/0xe8 Mar 14 23:59:01 s8330018 kernel: [ 4972.486934] [<00518c26>] dump_stack+0x6e/0x90 Mar 14 23:59:01 s8330018 kernel: [ 4972.486937] [<0027c376>] bad_page+0xe6/0x148 Mar 14 23:59:01 s8330018 kernel: [ 4972.486938] [<00280516>] get_page_from_freelist+0x49e/0xba8 Mar 14 23:59:01 s8330018 kernel: [ 4972.486940] [<00280ede>] __alloc_pages_nodemask+0x166/0xb00 Mar 14 23:59:01 s8330018 kernel: [ 4972.486941] [<0015635a>] s390_dma_alloc+0x82/0x1a0 Mar 14 23:59:01 s8330018 kernel: [ 4972.486944] [<03ff805ea142>] __genwqe_alloc_consistent+0x7a/0x90 [genwqe_card] Mar 14 23:59:01 s8330018 kernel: [ 4972.486947] [<03ff805ea344>] genwqe_alloc_sync_sgl+0x17c/0x2e0 [genwqe_card] Mar 14 23:59:01 s8330018 kernel: [ 4972.486950] [<03ff805e52da>] do_execute_ddcb+0x1da/0x348 [genwqe_card] Mar 14 23:59:01 s8330018 kernel: [ 4972.486952] [<03ff805e5964>] genwqe_ioctl+0x51c/0xc20 [genwqe_card] Mar 14 23:59:01 s8330018 kernel: [ 4972.486953] [<003145ee>] do_vfs_ioctl+0x3b6/0x518 Mar 14 23:59:01 s8330018 kernel: [ 4972.486955] [<003147f4>] SyS_ioctl+0xa4/0xb8 Mar 14 23:59:01 s8330018 kernel: [ 4972.486956] [<007ad1be>] system_call+0xd6/0x264 Mar 14 23:59:01 s8330018 kernel: [ 4972.486957] [<03ffa9df2492>] 0x3ffa9df249
[Kernel-packages] [Bug 1591804] Re: [Feature] Purley: Memory Protection Keys
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- yakkety' to 'verification-done-yakkety'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-yakkety -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1591804 Title: [Feature] Purley: Memory Protection Keys Status in intel: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Yakkety: Fix Committed Status in linux source package in Zesty: Fix Released Bug description: Memory Protection Keys for Userspace (PKU aka PKEYs) is a Skylake-SP server feature that provides a mechanism for enforcing page-based protections, but without requiring modification of the page tables when an application changes protection domains. It works by dedicating 4 previously ignored bits in each page table entry to a "protection key", giving 16 possible keys. There is also a new user-accessible register (PKRU) with two separate bits (Access Disable and Write Disable) for each key.Being a CPU register, PKRU is inherently thread-local,potentially giving each thread a different set of protectionsfrom every other thread. There are two new instructions (RDPKRU/WRPKRU) for reading and writing to the new register. The feature is only available in 64-bit mode, even though there is theoretically space in the PAE PTEs. These permissions are enforced on data access only and have no effect on instruction fetches. HW: Purley Upstream status: v4.6 kernel implement basic and execute-only support v4.9 kernel will have new interface To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1591804/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1591618] Re: [Feature] KBL - New device ID for Kabypoint(KbP)
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- yakkety' to 'verification-done-yakkety'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1591618 Title: [Feature] KBL - New device ID for Kabypoint(KbP) Status in intel: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Fix Committed Status in linux source package in Zesty: Fix Released Bug description: identify what new device IDs are required for Kabypoint (KBP): HS- UART,SPI, I2C, SMBUS,SPI-NOR,NPK,xHCI,usb device, SD Platform: Kabylake-S with Kabypoint PCH upstream schedule: 4.9 X-HWE-Bug: Bug #1622469 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1591618/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1535802] Re: Bluetooth 04ca:3011 [Asus Aspire V3-371] doesn't work
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: verification-needed-yakkety
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1535802
Title:
Bluetooth 04ca:3011 [Asus Aspire V3-371] doesn't work
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Yakkety:
Fix Committed
Bug description:
USB device 04ca:3011 is a combo Atheros device's bluetooth adapter.
In back of laptop the adapter's label states as: PPD-QCNFA34AC
WORKAROUND for kernel 4.4:
wget
https://launchpad.net/~hanipouspilot/+archive/ubuntu/bluetooth/+files/btusb-lp1535802-dkms_0.1_all.deb
sudo dpkg -i btusb-lp1535802-dkms_0.1_all.deb
By default my kernel recognize as generic Bluetooth,
I can switch on/off, make it visible,
BUT actually it cannot see anything and no other devices can see it.
However
It works well (tested) as "QCA ROME chipset" so adding a line:
{ USB_DEVICE(0x04ca, 0x3011), .driver_info = BTUSB_QCA_ROME },
in btusb.c (compile, install as module, and modprobe) made the trick.
lsusb:
Bus 003 Device 004: ID 04ca:3011 Lite-On Technology Corp.
I added the diff file of drivers/bluetooth/btusb.c
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: linux-image-4.2.0-23-generic 4.2.0-23.28
ProcVersionSignature: Ubuntu 4.2.0-23.28-generic 4.2.6
Uname: Linux 4.2.0-23-generic i686
ApportVersion: 2.19.1-0ubuntu5
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: mark 1476 F pulseaudio
/dev/snd/controlC0: mark 1476 F pulseaudio
CurrentDesktop: Unity
Date: Tue Jan 19 17:03:18 2016
HibernationDevice: RESUME=UUID=66dc8cfd-62d6-411b-9edf-c509aac14318
InstallationDate: Installed on 2015-10-26 (85 days ago)
InstallationMedia: Ubuntu "Wily" - Build i386 LIVE Binary 20151022-23:55
MachineType: Acer Aspire V3-371
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-23-generic
root=UUID=403e935b-5da2-4b34-8dd7-14f1c0cf0846 ro quiet splash
RelatedPackageVersions:
linux-restricted-modules-4.2.0-23-generic N/A
linux-backports-modules-4.2.0-23-generic N/A
linux-firmware1.149.3
SourcePackage: linux
UdevLog: Error: [Errno 2] Nincs ilyen fájl vagy könyvtár: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/21/2015
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.28
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Aspire V3-371
dmi.board.vendor: Acer
dmi.board.version: V1.28
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.28
dmi.modalias:
dmi:bvnInsydeCorp.:bvrV1.28:bd08/21/2015:svnAcer:pnAspireV3-371:pvrV1.28:rvnAcer:rnAspireV3-371:rvrV1.28:cvnAcer:ct10:cvrV1.28:
dmi.product.name: Aspire V3-371
dmi.product.version: V1.28
dmi.sys.vendor: Acer
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1535802/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1591810] Re: [Feature] SKX: perf uncore PMU support
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- yakkety' to 'verification-done-yakkety'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-yakkety -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1591810 Title: [Feature] SKX: perf uncore PMU support Status in intel: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Yakkety: Fix Committed Status in linux source package in Zesty: Fix Released Bug description: Enable Linux perf tool to support Intel Skylake server CPU uncore events. uncore provides additional performance monitoring information for advance user. HW: Purley Upstream schedule: 4.9 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1591810/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1591618] Re: [Feature] KBL - New device ID for Kabypoint(KbP)
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-xenial ** Tags added: verification-needed-yakkety -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1591618 Title: [Feature] KBL - New device ID for Kabypoint(KbP) Status in intel: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Fix Committed Status in linux source package in Zesty: Fix Released Bug description: identify what new device IDs are required for Kabypoint (KBP): HS- UART,SPI, I2C, SMBUS,SPI-NOR,NPK,xHCI,usb device, SD Platform: Kabylake-S with Kabypoint PCH upstream schedule: 4.9 X-HWE-Bug: Bug #1622469 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1591618/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1612006] Re: I2C touchpad does not work on AMD platform
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- yakkety' to 'verification-done-yakkety'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-yakkety -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1612006 Title: I2C touchpad does not work on AMD platform Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Fix Committed Bug description: Recent AMD platform has problems with I2C touchpads because its GPIO controller is not configured correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1612006/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1641620] Re: conected external seagate drive, dosent mount automatically
Hi I've worked out I had a problem with micro usb cable. Ive replaced the cables and it is working fine now. sorry about all the trouble. Thanks Koli -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1641620 Title: conected external seagate drive, dosent mount automatically Status in linux package in Ubuntu: Incomplete Bug description: see attached file ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-47-generic 4.4.0-47.68 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: koli 1857 F pulseaudio /dev/snd/controlC1: koli 1857 F pulseaudio CurrentDesktop: Unity Date: Mon Nov 14 14:29:30 2016 GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit. HibernationDevice: RESUME=UUID=7f093ee2-a093-4cde-99c6-a60706e7059f HotplugNewDevices: HotplugNewMounts: InstallationDate: Installed on 2016-06-11 (155 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 20354 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic.efi.signed root=UUID=0954c6f9-fd74-4c40-ad0b-03e7f73f5153 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-47-generic N/A linux-backports-modules-4.4.0-47-generic N/A linux-firmware1.157.4 SourcePackage: linux Symptom: storage UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 9BCN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lancer 5A5 dmi.board.vendor: LENOVO dmi.board.version: 31900058WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Z50-70 dmi.modalias: dmi:bvnLENOVO:bvr9BCN29WW:bd10/20/2014:svnLENOVO:pn20354:pvrLenovoZ50-70:rvnLENOVO:rnLancer5A5:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoZ50-70: dmi.product.name: 20354 dmi.product.version: Lenovo Z50-70 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641620/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1641075] Re: connected my android phone, htc one m8, unabe to mount.
Hi, all resolved, it was due to a faulty micro usb cable. Sorry about all the trouble and thanks. Koli -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1641075 Title: connected my android phone, htc one m8, unabe to mount. Status in linux package in Ubuntu: Confirmed Bug description: Unable to mount phone. It used to work fine in the past, now gone completely out. If I connect it, sometimes I get a message on the phone screen indidcating if I want to use it for file transfers or charging. When I choose file transfers phone tries to mount but fails. I get the message: Unable to open MTP device '[usb:002,073]' This is the output from:lsusb Bus 001 Device 002: ID 8087:8000 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 007: ID 8087:07dc Intel Corp. Bus 002 Device 006: ID 5986:055e Acer, Inc Bus 002 Device 005: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 002 Device 004: ID 046d:c077 Logitech, Inc. M105 Optical Mouse Bus 002 Device 096: ID 04e8:3469 Samsung Electronics Co., Ltd Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub as you can see device is not listed, ie htc. this is the other output: dmesg | grep error [4.513851] usb 2-1: device not accepting address 10, error -71 [5.329827] usb 2-1: device not accepting address 12, error -71 [6.825737] usb 2-1: device not accepting address 15, error -71 [9.974461] EXT4-fs (sda3): re-mounted. Opts: errors=remount-ro [ 11.284758] iwlwifi :02:00.0: Direct firmware load for iwlwifi-3160-17.ucode failed with error -2 [ 17.657095] usb 2-1: can't read configurations, error -110 [ 23.776699] usb 2-1: device not accepting address 21, error -71 [ 25.324569] usb 2-1: device not accepting address 25, error -71 [ 30.748339] usb 2-1: device descriptor read/all, error -110 [ 31.564231] usb 2-1: device not accepting address 29, error -71 [ 2724.182039] usb 2-1: device not accepting address 75, error -71 [ 2741.132996] usb 2-1: device not accepting address 81, error -71 [ 2747.276635] usb 2-1: device not accepting address 84, error -71 [ 2763.979585] usb 2-1: device not accepting address 89, error -71 [ 2765.163503] usb 2-1: device not accepting address 92, error -71 [ 2889.015888] usb 2-1: device not accepting address 97, error -71 [ 2967.527023] usb 2-1: device not accepting address 125, error -71 [ 3056.901541] usb 2-1: device not accepting address 25, error -71 [ 3138.452524] usb 2-1: device descriptor read/all, error -110 [ 3227.907019] usb 2-1: device not accepting address 71, error -71 [ 3338.788209] usb 2-1: device descriptor read/all, error -110 This is not a cable issue as I checked it on an old ubuntu box, ie the firs 16.04 with no updates, ie kernel 31 one and it works fine on it. Could you pls look at it, thanks. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-45-generic 4.4.0-45.66 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: koli 1952 F pulseaudio /dev/snd/controlC1: koli 1952 F pulseaudio CurrentDesktop: Unity Date: Fri Nov 11 10:00:59 2016 GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit. HibernationDevice: RESUME=UUID=7f093ee2-a093-4cde-99c6-a60706e7059f HotplugNewDevices: HotplugNewMounts: InstallationDate: Installed on 2016-06-11 (152 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 20354 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed root=UUID=0954c6f9-fd74-4c40-ad0b-03e7f73f5153 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-45-generic N/A linux-backports-modules-4.4.0-45-generic N/A linux-firmware1.157.4 SourcePackage: linux Symptom: storage UdevMonitorLog: monitor will print the received events for: UDEV - the event which udev sends out after rule processing UdisksMonitorLog: Monitoring the udisks daemon. Press Ctrl+C to exit. 10:01:38.818: The udisks-daemon is running (name-owner :1.77). UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 9BCN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lancer 5A5 dmi.board.vendor: LENOVO dmi.board.version: 31900058WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Z50-70 dmi.modalia
[Kernel-packages] [Bug 1633583] Re: Can not connect to Bluetooth headset
DimanNe See https://workingninja.com/installing-asus-bt400-raspberry-pi-raspbian-wheezy It will show how to get the firmware needed for the broadcom bluetooth device and see if the issue still exists after the firmware install -- 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/1633583 Title: Can not connect to Bluetooth headset Status in bluez package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: I managed to pair with my wireless headset, but I was unable to connect to it. Every time I try to do it, I get this message in syslog: Oct 14 21:38:09 localhost bluetoothd[2246]: Unable to get Headset Voice gateway SDP record: Host is down Relating info is below Info from bluetoothctl: bluetooth]# devices Device 00:1B:66:03:C4:66 MOMENTUM M2 AEBT bluetooth]# info 00:1B:66:03:C4:66 Device 00:1B:66:03:C4:66 Name: MOMENTUM M2 AEBT Alias: MOMENTUM M2 AEBT Class: 0x240404 Icon: audio-card Paired: yes Trusted: yes Blocked: no Connected: no LegacyPairing: yes UUID: Headset (1108--1000-8000-00805f9b34fb) UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: Handsfree (111e--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb) UUID: Vendor specific (1ddce62a-ecb1-4455-8153-0743c87aec9f) Modalias: bluetooth:v0082p004Bd010E Info from hciconfig $ sudo hciconfig -a [sudo] password for dimanne: hci0: Type: Primary Bus: USB BD Address: 5C:F3:70:73:F2:B1 ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN ISCAN RX bytes:14866 acl:33 sco:0 events:2022 errors:0 TX bytes:17848 acl:33 sco:0 commands:1639 errors:0 Features: 0xbf 0xfe 0xcf 0xfe 0xdb 0xff 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH SNIFF Link mode: SLAVE ACCEPT Name: 'impedance #1' Class: 0x1c0104 Service Classes: Rendering, Capturing, Object Transfer Device Class: Computer, Desktop workstation HCI Version: 4.0 (0x6) Revision: 0x1000 LMP Version: 4.0 (0x6) Subversion: 0x220e Manufacturer: Broadcom Corporation (15) hci1: Type: Primary Bus: USB BD Address: 54:27:1E:33:4B:85 ACL MTU: 1021:8 SCO MTU: 64:1 DOWN RX bytes:2926 acl:0 sco:0 events:161 errors:0 TX bytes:5699 acl:0 sco:0 commands:157 errors:0 Features: 0xbf 0xfe 0xcf 0xfe 0xdb 0xff 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH SNIFF Link mode: SLAVE ACCEPT rfkill: $ rfkill list 1: hci1: Bluetooth Soft blocked: no Hard blocked: no 2: hci0: Bluetooth Soft blocked: no Hard blocked: no Info from dmesg: $ dmesg | grep -i blue [5.170808] Bluetooth: Core ver 2.21 [5.170819] Bluetooth: HCI device and connection manager initialized [5.170821] Bluetooth: HCI socket layer initialized [5.170822] Bluetooth: L2CAP socket layer initialized [5.170826] Bluetooth: SCO socket layer initialized [5.185923] Bluetooth: hci0: BCM: chip id 63 [5.186665] Bluetooth: hci1: BCM: chip id 63 [5.202506] Bluetooth: hci0: impedance #2 [5.203150] Bluetooth: hci1: ChromeLinux_5818 [5.203498] Bluetooth: hci0: BCM20702A1 (001.002.014) build [5.203670] bluetooth hci0: Direct firmware load for brcm/BCM20702A1-0b05-17cb.hcd failed with error -2 [5.203671] Bluetooth: hci0: BCM: Patch brcm/BCM20702A1-0b05-17cb.hcd not found [5.204662] Bluetooth: hci1: BCM20702A1 (001.002.014) build [5.204671] bluetooth hci1: Direct firmware load for brcm/BCM20702A1-0b05-17cf.hcd failed with error -2 [5.204671] Bluetooth: hci1: BCM: Patch brcm/BCM20702A1-0b05-17cf.hcd not found [ 11.359871] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 11.359872] Bluetooth: BNEP filters: protocol multicast [ 11.359874] Bluetooth: BNEP socket layer initialized [ 34.046364] Bluetooth: RFCOMM TTY layer initialized [ 34.046368] Bluetooth: RFCOMM socket layer initialized [ 34.046371] Bluetooth: RFCOMM ver 1.11 [ 1193.523500] Bluetooth: hci0: BCM: chip id 63 [ 1193.539525] Bluetooth: hci0: BCM20702A [ 1193.540524] Blu
[Kernel-packages] [Bug 1642228] [NEW] Move some kernel modules to the main kernel package
You have been subscribed to a public bug: == Comment: #0 - Breno Henrique Leitao - 2016-10-20 08:51:24 == Hello Canonical, There are important kernel modules that are required on POWER systems, and they are currently on the linux-image-extra packages. So, in this case, every Power system needs to install the -extra package, which makes the -extra package required. My suggestion is to add these important modules to the main archive, so, we do not require the installation of the -extra package. We are working on the full list of packages, but I would like to anticipate these modules: 01. lpfc 02. qla2xxx 03. be2net 04. bnx2x 05. i40e 06. igb 07. ixgbe 08. cxl 09. cxlflash 10. jsm 11. ohci-platform 12. xhci 13. aacraid 14. ipr 15. megaraid_sas 16. mpt3sas 17. powernv-rng 18. ipmi_powernv 19. leds-powernv 20. ibmpowernv 21. opal-prd 22. powernv_flash 23. nx-compress-powernv 24. vfio (all modules: vfio.ko, vfio-pci.ko, vfio_iommu_spapr_tce.ko, vfio_virqfd.ko, vfio_spapr_eeh.ko) *Notice* The driver "qlge" is presented in the preliminary list but it's not necessary. Thanks in advance, ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Taco Screen team (taco-screen-team) Status: New ** Tags: architecture-ppc64le bugnameltc-147746 severity-high targetmilestone-inin1704 -- Move some kernel modules to the main kernel package https://bugs.launchpad.net/bugs/1642228 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 1581088] Re: Middle mouse (wheel-click) button stopped working after upgrade to 16.04
Got the same problem with Logitech RX250 on Xubuntu 16.04.01 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1581088 Title: Middle mouse (wheel-click) button stopped working after upgrade to 16.04 Status in linux package in Ubuntu: Incomplete Bug description: Since upgrading to 16.04 clicking the middle mouse button (scroll wheel) on my Logitech M185 stopped working. xev does not even show the event for clicking the wheel, while it shows other button clicks and scroll wheel up/down events. xinput list shows the USB receiver 2 times: ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Logitech USB Receiver id=9[slave pointer (2)] ⎜ ↳ Logitech USB Receiver id=10 [slave pointer (2)] ⎜ ↳ HID 046a:0023 id=13 [slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=16 [slave pointer (2)] ⎜ ↳ TPPS/2 IBM TrackPoint id=17 [slave pointer (2)] Listing the capabilities looks like this: $ xinput list 9 Logitech USB Receiver id=9[slave pointer (2)] Reporting 7 classes: Class originated from: 9. Type: XIButtonClass Buttons supported: 24 Button labels: "Button Left" "Button Middle" "Button Right" "Button Wheel Up" "Button Wheel Down" "Button Horiz Wheel Left" "Button Horiz Wheel Right" "Button Side" "Button Extra" "Button Forward" "Button Back" "Button Task" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" Button state: Class originated from: 9. Type: XIValuatorClass Detail for Valuator 0: Label: Rel X Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 9. Type: XIValuatorClass Detail for Valuator 1: Label: Rel Y Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 9. Type: XIValuatorClass Detail for Valuator 2: Label: Rel Horiz Wheel Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 9. Type: XIValuatorClass Detail for Valuator 3: Label: Rel Vert Wheel Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 9. Type: XIScrollClass Scroll info for Valuator 2 type: 2 (horizontal) increment: 1.00 flags: 0x0 Class originated from: 9. Type: XIScrollClass Scroll info for Valuator 3 type: 1 (vertical) increment: -1.00 flags: 0x2 ( preferred ) $ xinput list 10 Logitech USB Receiver id=10 [slave pointer (2)] Reporting 6 classes: Class originated from: 10. Type: XIButtonClass Buttons supported: 7 Button labels: "Button 0" "Button Unknown" "Button Unknown" "Button Wheel Up" "Button Wheel Down" "Button Horiz Wheel Left" "Button Horiz Wheel Right" Button state: Class originated from: 10. Type: XIKeyClass Keycodes supported: 248 Class originated from: 10. Type: XIValuatorClass Detail for Valuator 0: Label: Rel X Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 10. Type: XIValuatorClass Detail for Valuator 1: Label: Rel Y Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 10. Type: XIValuatorClass Detail for Valuator 2: Label: Rel Horiz Wheel Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 10. Type: XIScrollClass Scroll info for Valuator 2 type: 2 (horizontal) increment: 1.00 flags: 0x0 Does anyone have an idea how I can attempt to further debug that issue? Or maybe even a solution? Should I consider this issue a bug? Can I provide more info? --- ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: toby 11625 F pulseaudio /dev/snd/controlC0: toby 11625 F pulseaudio /dev/snd/pcmC1D0p: toby 11625 F...m pulseaudio /dev/snd/controlC1: toby 11625 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=5e3a6d2e-05f8-4d01-b80c-a9f200e6 InstallationDate: Installed on 2014-04-24 (749 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: LENOVO 20AL00C6
[Kernel-packages] [Bug 1642228] [NEW] Move some kernel modules to the main kernel package
Public bug reported: == Comment: #0 - Breno Henrique Leitao - 2016-10-20 08:51:24 == Hello Canonical, There are important kernel modules that are required on POWER systems, and they are currently on the linux-image-extra packages. So, in this case, every Power system needs to install the -extra package, which makes the -extra package required. My suggestion is to add these important modules to the main archive, so, we do not require the installation of the -extra package. We are working on the full list of packages, but I would like to anticipate these modules: 01. lpfc 02. qla2xxx 03. be2net 04. bnx2x 05. i40e 06. igb 07. ixgbe 08. cxl 09. cxlflash 10. jsm 11. ohci-platform 12. xhci 13. aacraid 14. ipr 15. megaraid_sas 16. mpt3sas 17. powernv-rng 18. ipmi_powernv 19. leds-powernv 20. ibmpowernv 21. opal-prd 22. powernv_flash 23. nx-compress-powernv 24. vfio (all modules: vfio.ko, vfio-pci.ko, vfio_iommu_spapr_tce.ko, vfio_virqfd.ko, vfio_spapr_eeh.ko) *Notice* The driver "qlge" is presented in the preliminary list but it's not necessary. Thanks in advance, ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Taco Screen team (taco-screen-team) Status: New ** Tags: architecture-ppc64le bugnameltc-147746 severity-high targetmilestone-inin1704 ** Tags added: architecture-ppc64le bugnameltc-147746 severity-high targetmilestone-inin1704 ** Changed in: ubuntu Assignee: (unassigned) => Taco Screen team (taco-screen-team) ** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1642228 Title: Move some kernel modules to the main kernel package Status in linux package in Ubuntu: New Bug description: == Comment: #0 - Breno Henrique Leitao - 2016-10-20 08:51:24 == Hello Canonical, There are important kernel modules that are required on POWER systems, and they are currently on the linux-image-extra packages. So, in this case, every Power system needs to install the -extra package, which makes the -extra package required. My suggestion is to add these important modules to the main archive, so, we do not require the installation of the -extra package. We are working on the full list of packages, but I would like to anticipate these modules: 01. lpfc 02. qla2xxx 03. be2net 04. bnx2x 05. i40e 06. igb 07. ixgbe 08. cxl 09. cxlflash 10. jsm 11. ohci-platform 12. xhci 13. aacraid 14. ipr 15. megaraid_sas 16. mpt3sas 17. powernv-rng 18. ipmi_powernv 19. leds-powernv 20. ibmpowernv 21. opal-prd 22. powernv_flash 23. nx-compress-powernv 24. vfio (all modules: vfio.ko, vfio-pci.ko, vfio_iommu_spapr_tce.ko, vfio_virqfd.ko, vfio_spapr_eeh.ko) *Notice* The driver "qlge" is presented in the preliminary list but it's not necessary. Thanks in advance, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1642228/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1581088] Re: Middle mouse (wheel-click) button stopped working after upgrade to 16.04
Thats kernel 4.4.07.68 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1581088 Title: Middle mouse (wheel-click) button stopped working after upgrade to 16.04 Status in linux package in Ubuntu: Incomplete Bug description: Since upgrading to 16.04 clicking the middle mouse button (scroll wheel) on my Logitech M185 stopped working. xev does not even show the event for clicking the wheel, while it shows other button clicks and scroll wheel up/down events. xinput list shows the USB receiver 2 times: ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Logitech USB Receiver id=9[slave pointer (2)] ⎜ ↳ Logitech USB Receiver id=10 [slave pointer (2)] ⎜ ↳ HID 046a:0023 id=13 [slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=16 [slave pointer (2)] ⎜ ↳ TPPS/2 IBM TrackPoint id=17 [slave pointer (2)] Listing the capabilities looks like this: $ xinput list 9 Logitech USB Receiver id=9[slave pointer (2)] Reporting 7 classes: Class originated from: 9. Type: XIButtonClass Buttons supported: 24 Button labels: "Button Left" "Button Middle" "Button Right" "Button Wheel Up" "Button Wheel Down" "Button Horiz Wheel Left" "Button Horiz Wheel Right" "Button Side" "Button Extra" "Button Forward" "Button Back" "Button Task" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" Button state: Class originated from: 9. Type: XIValuatorClass Detail for Valuator 0: Label: Rel X Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 9. Type: XIValuatorClass Detail for Valuator 1: Label: Rel Y Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 9. Type: XIValuatorClass Detail for Valuator 2: Label: Rel Horiz Wheel Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 9. Type: XIValuatorClass Detail for Valuator 3: Label: Rel Vert Wheel Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 9. Type: XIScrollClass Scroll info for Valuator 2 type: 2 (horizontal) increment: 1.00 flags: 0x0 Class originated from: 9. Type: XIScrollClass Scroll info for Valuator 3 type: 1 (vertical) increment: -1.00 flags: 0x2 ( preferred ) $ xinput list 10 Logitech USB Receiver id=10 [slave pointer (2)] Reporting 6 classes: Class originated from: 10. Type: XIButtonClass Buttons supported: 7 Button labels: "Button 0" "Button Unknown" "Button Unknown" "Button Wheel Up" "Button Wheel Down" "Button Horiz Wheel Left" "Button Horiz Wheel Right" Button state: Class originated from: 10. Type: XIKeyClass Keycodes supported: 248 Class originated from: 10. Type: XIValuatorClass Detail for Valuator 0: Label: Rel X Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 10. Type: XIValuatorClass Detail for Valuator 1: Label: Rel Y Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 10. Type: XIValuatorClass Detail for Valuator 2: Label: Rel Horiz Wheel Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 10. Type: XIScrollClass Scroll info for Valuator 2 type: 2 (horizontal) increment: 1.00 flags: 0x0 Does anyone have an idea how I can attempt to further debug that issue? Or maybe even a solution? Should I consider this issue a bug? Can I provide more info? --- ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: toby 11625 F pulseaudio /dev/snd/controlC0: toby 11625 F pulseaudio /dev/snd/pcmC1D0p: toby 11625 F...m pulseaudio /dev/snd/controlC1: toby 11625 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=5e3a6d2e-05f8-4d01-b80c-a9f200e6 InstallationDate: Installed on 2014-04-24 (749 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: LENOVO 20AL00C6GE Package: linux (not installed) P
[Kernel-packages] [Bug 1566302] Re: Ubuntu 16.04: Suspend freezes the system after upgrade to linux image 4.4.0-16
@acarbura yes it does -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1566302 Title: Ubuntu 16.04: Suspend freezes the system after upgrade to linux image 4.4.0-16 Status in linux package in Ubuntu: Won't Fix Bug description: I'm using ubuntu 16.04 on a XPS 15 9550. Suspend/resume worked flawlessly with linux image 4.4.0-15, and after standard upgrade yesterday (5/04/2016) which installed image 4.4.0-16, the system freezes when attempting a suspend. I get no response from the system (nor keyboard, nor screen, nor touchpad), but it gets very hot, so that it must be running something. Booting with 4.4.0-15 makes the suspend to work perfectly. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.4.0-16-generic 4.4.0-16.32 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: macias 1770 F pulseaudio CurrentDesktop: X-Cinnamon Date: Tue Apr 5 14:56:17 2016 HibernationDevice: RESUME=UUID=4180adfa-3852-4a96-86b4-f3696448c743 InstallationDate: Installed on 2016-03-07 (28 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9550 ProcEnviron: LANGUAGE=es_ES PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic.efi.signed root=UUID=673f4658-75f8-4c01-bcd8-0af860269699 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-15-generic N/A linux-backports-modules-4.4.0-15-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.01.19 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.01.19:bd01/25/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1566302/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
