[Kernel-packages] [Bug 1744270] Re: ubuntu_lttng_smoke_test failed on Xenial zVM
Xenial (zVM) kernel01 has passed with this test in this cycle (4.4.0-117.141). 03/15 00:52:44 INFO |ubuntu_ltt:0033| Summary: 8 passed, 0 failed Thanks ** Changed in: linux (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1744270 Title: ubuntu_lttng_smoke_test failed on Xenial zVM Status in linux package in Ubuntu: Invalid Bug description: This test failed with the proposed Xenial kernel 4.4.0-111.134 on zVM It's not a regression since this can be reproduced with the older 4.4.0-108 on the very same node. Command returned non-zero exit status * Command: /home/ubuntu/autotest/client/tests/ubuntu_lttng_smoke_test/ubuntu_lttng_s moke_test.sh Exit status: 1 Duration: 0.447135210037 stdout: == lttng smoke test of session create/destroy == Spawning a session daemon Session test-kernel-session created. Traces will be written in /tmp/lttng-kernel-trace-32862-session PASSED (lttng create) Session test-kernel-session destroyed PASSED (lttng destroy) == lttng smoke test list kernel events == FAILED (lttng list --kernel) FAILED (lttng list --kernel more output expected) lttng smoke test trace open/close system calls SKIPPED for s390x == lttng smoke test trace context switches == Session test-kernel-session created. Traces will be written in /tmp/lttng-kernel-trace-32862-session PASSED (lttng create) FAILED (lttng enable-event) Session test-kernel-session destroyed Summary: 3 passed, 3 failed stderr: Error: Unable to list kernel events: Kernel tracer not available Error: Command error Error: Event sched_switch: Kernel tracer not available (channel channel0, session test-kernel-session) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-111-generic 4.4.0-111.134 ProcVersionSignature: Ubuntu 4.4.0-111.134-generic 4.4.98 Uname: Linux 4.4.0-111-generic s390x AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.15 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDmesg: Date: Fri Jan 19 05:11:39 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=UUID=44b0b919-a1a4-4849-9425-e71d4ac87d85 crashkernel=196M nogmb BOOT_IMAGE=0 RelatedPackageVersions: linux-restricted-modules-4.4.0-111-generic N/A linux-backports-modules-4.4.0-111-generic N/A linux-firmware 1.157.15 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1744270/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1756240] Re: Unable to build lttng-module with Artful kernel
This issue can be reproduced with Xenial HWE kernel as well (4.13) 03/20 05:22:06 DEBUG| utils:0153| [stdout] Building initial module for 4.15.0-13-lowlatency 03/20 05:22:14 DEBUG| utils:0153| [stdout] Error! Bad return status for module build on kernel: 4.15.0-13-lowlatency (x86_64) 03/20 05:22:14 DEBUG| utils:0153| [stdout] Consult /var/lib/dkms/lttng-modules/2.8.0/build/make.log for more information. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1756240 Title: Unable to build lttng-module with Artful kernel Status in linux package in Ubuntu: Incomplete Bug description: The lttng module failed to build with the proposed Artful kernel (4.13.0-38), it works with 4.13.0-37 Please find the build log here: http://paste.ubuntu.com/p/ybwnBJB9yj/ ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-38-generic 4.13.0-38.43 ProcVersionSignature: User Name 4.13.0-38.43-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 16 04:13 seq crw-rw 1 root audio 116, 33 Mar 16 04:13 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Fri Mar 16 04:17:14 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Intel Corporation S1200RP PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb 1 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro RelatedPackageVersions: linux-restricted-modules-4.13.0-38-generic N/A linux-backports-modules-4.13.0-38-generic N/A linux-firmware 1.169.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2015 dmi.bios.vendor: Intel Corp. dmi.bios.version: S1200RP.86B.03.02.0003.070120151022 dmi.board.asset.tag: dmi.board.name: S1200RP dmi.board.vendor: Intel Corporation dmi.board.version: G62254-407 dmi.chassis.asset.tag: dmi.chassis.type: 17 dmi.chassis.vendor: .. dmi.chassis.version: .. dmi.modalias: dmi:bvnIntelCorp.:bvrS1200RP.86B.03.02.0003.070120151022:bd07/01/2015:svnIntelCorporation:pnS1200RP:pvr:rvnIntelCorporation:rnS1200RP:rvrG62254-407:cvn..:ct17:cvr..: dmi.product.family: To be filled by O.E.M. dmi.product.name: S1200RP dmi.product.version: dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1756240/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1756240] Re: Unable to build lttng-module with Artful kernel
Sorry in comment #3 it's the Xenial Edge kernel (4.15), this is the Xenial HWE one: 03/16 01:12:07 DEBUG| utils:0153| [stdout] Error! Bad return status for module build on kernel: 4.13.0-38-lowlatency (x86_64) 03/16 01:12:07 DEBUG| utils:0153| [stdout] Consult /var/lib/dkms/lttng-modules/2.8.0/build/make.log for more information. 03/16 01:12:07 DEBUG| utils:0153| [stdout] Setting up lttng-tools (2.7.1-2ubuntu1) ... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1756240 Title: Unable to build lttng-module with Artful kernel Status in linux package in Ubuntu: Incomplete Bug description: The lttng module failed to build with the proposed Artful kernel (4.13.0-38), it works with 4.13.0-37 Please find the build log here: http://paste.ubuntu.com/p/ybwnBJB9yj/ ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-38-generic 4.13.0-38.43 ProcVersionSignature: User Name 4.13.0-38.43-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 16 04:13 seq crw-rw 1 root audio 116, 33 Mar 16 04:13 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Fri Mar 16 04:17:14 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Intel Corporation S1200RP PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb 1 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro RelatedPackageVersions: linux-restricted-modules-4.13.0-38-generic N/A linux-backports-modules-4.13.0-38-generic N/A linux-firmware 1.169.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2015 dmi.bios.vendor: Intel Corp. dmi.bios.version: S1200RP.86B.03.02.0003.070120151022 dmi.board.asset.tag: dmi.board.name: S1200RP dmi.board.vendor: Intel Corporation dmi.board.version: G62254-407 dmi.chassis.asset.tag: dmi.chassis.type: 17 dmi.chassis.vendor: .. dmi.chassis.version: .. dmi.modalias: dmi:bvnIntelCorp.:bvrS1200RP.86B.03.02.0003.070120151022:bd07/01/2015:svnIntelCorporation:pnS1200RP:pvr:rvnIntelCorporation:rnS1200RP:rvrG62254-407:cvn..:ct17:cvr..: dmi.product.family: To be filled by O.E.M. dmi.product.name: S1200RP dmi.product.version: dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1756240/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1754913] Re: ASUS w/ Atom N270 - Ubuntu 16.04.4 doesn't work properly.
4. Kernel v4.16-rc6 works well. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1754913 Title: ASUS w/ Atom N270 - Ubuntu 16.04.4 doesn't work properly. Status in linux package in Ubuntu: Confirmed Bug description: I installed Ubuntu 16.04.4, then restarted my netbook. After restart, ubuntu 16.04.4 doesn't work properly. See Imgur images. https://i.imgur.com/nayCd6X.jpg -- ASUS 1000HE CPU: Single Core Intel Atom N270 Graphics: Card: Intel Mobile 945GSE Express Integrated Graphics Controller To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1754913/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1754913] Re: ASUS w/ Atom N270 - Ubuntu 16.04.4 doesn't work properly.
1. "Recovery Mode" from the GRUB menu is working good. 2. "GRUB_GFXPAYLOAD_LINUX=text" is working good. 3. "GRUB_TERMINAL=console" is working good. ** Tags added: kernel-fixed-upstream ** 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/1754913 Title: ASUS w/ Atom N270 - Ubuntu 16.04.4 doesn't work properly. Status in linux package in Ubuntu: Confirmed Bug description: I installed Ubuntu 16.04.4, then restarted my netbook. After restart, ubuntu 16.04.4 doesn't work properly. See Imgur images. https://i.imgur.com/nayCd6X.jpg -- ASUS 1000HE CPU: Single Core Intel Atom N270 Graphics: Card: Intel Mobile 945GSE Express Integrated Graphics Controller To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1754913/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1741655] Re: Regression: KVM no longer supports Intel CPUs without Virtual NMI
tested it on artful and 16.04 LTE. On 16.04 LTE the kernel from comment #6 working since mid of January without any problems. added tag verification-done-artful ** Tags removed: verification-needed-artful ** Tags added: verification-done-artful -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1741655 Title: Regression: KVM no longer supports Intel CPUs without Virtual NMI Status in linux package in Ubuntu: Fix Committed Status in linux source package in Artful: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: == SRU Justification == The following mainline commit introduced a regression in v4.12-rc1: 2c82878b0cb3 ("KVM: VMX: require virtual NMI support") This regression caused the kvm-intel module fail to load with the following error: "modprobe: ERROR: could not insert 'kvm_intel': Input/output error" This error would happen because suppor for CPUs without virtual NMI was removed by commit 2c82878b0cb3. Mainline commit 8a1b43922d0d fixes this regression and was added to mainline in v4.15-rc1. == Fix == commit 8a1b43922d0d1279e7936ba85c4c2a870403c95f Author: Paolo Bonzini Date: Mon Nov 6 13:31:12 2017 +0100 kvm: vmx: Reinstate support for CPUs without virtual NMI == Regression Potential == Low. This patch fixes a current regression. It was cc'd to upstream stable so had additional upstream review. ## Original Bug Description ## Since upgrading from zesty to artful, I'm not longer able to use KVM on my server: # modprobe kvm-intel modprobe: ERROR: could not insert 'kvm_intel': Input/output error Searching tells me this is caused by requiring Virtual NMI support[1] Running the script provided on the mailing list[1] to check virtualization features confirms my CPU (Xeon E5345) doesn't support Virtual NMIs: # python features.py | grep NMI NMI exiting yes Virtual NMIs no NMI-window exiting no Virtual NMI support was required in v4.12[1] and later reverted in v4.14.3[2] as some models (including Xeons) don't support it, even if others with the same core do. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1490803 [2] https://lkml.org/lkml/2017/8/7/231 [3] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/arch/x86/kvm/vmx.c?h=linux-4.13.y&id=2c82878b0cb38fd516fd612c67852a6bbf282003 [4] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/arch/x86/kvm/vmx.c?h=linux-4.14.y&id=a77360e989f3dc06e4f177a0837d533d13a20d91 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1741655/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1736794] Re: iwlwifi driver for Intel 7260 crashing
This is a duplicate of https://bugzilla.kernel.org/show_bug.cgi?id=191601, which also contains a script that might be able to reset your card without a reboot. Please see my longer comments here: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1673344. In summary, I believe this to be a longstanding hardware-software bug in Linux due to a hardware degraded 7260 NIC. Replacing the 7260 card fixed it for me. ** Bug watch added: Linux Kernel Bug Tracker #191601 https://bugzilla.kernel.org/show_bug.cgi?id=191601 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1736794 Title: iwlwifi driver for Intel 7260 crashing Status in linux-firmware package in Ubuntu: New Bug description: Intel NUC's from Axiomtek with Intel Corporation Wireless 7260 (rev bb) chipsets. We have this running on almost 200 of these devices. Ubuntu 16.04.3 as well as Ubuntu 14.04.5 "loaded firmware version 17.608620.0 op_mode iwlmvm" linux-firmware trusty: 1.127.24 linux-firmware xenial: 1.157.14 The wireless driver will crash at least daily, if not multiple times in a day depending on the machine. Swapping the chipset out for an Atheros works just fine. I have followed the many other bug reports related to this same chipset and they are either marked incomplete, refer to hardware we aren't running or have been marked as fix released. The latest linux-firmware did not resolve or change the behavior of the issue. Output from dmesg when the crash occurs: [Wed Dec 6 18:56:38 2017] iwlwifi :02:00.0: Queue 16 stuck for 1 ms. [Wed Dec 6 18:56:38 2017] iwlwifi :02:00.0: Current SW read_ptr 236 write_ptr 88 [Wed Dec 6 18:56:38 2017] [ cut here ] [Wed Dec 6 18:56:38 2017] WARNING: CPU: 3 PID: 0 at /build/linux-lts-xenial-CtFtiH/linux-lts-xenial-4.4.0/drivers/net/wireless/iwlwifi/pcie/trans.c:1552 iwl_trans_pcie_grab_nic_access+0xf5/0x100 [iwlwifi]() [Wed Dec 6 18:56:38 2017] Timeout waiting for hardware access (CSR_GP_CNTRL 0x) [Wed Dec 6 18:56:38 2017] Modules linked in: drbg ansi_cprng ctr ccm uvcvideo videobuf2_vmalloc btusb videobuf2_memops btrtl videobuf2_v4l2 btbcm btintel videobuf2_core hid_generic bluetooth v4l2_common videodev usbhid media arc4 snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic iwlmvm mac80211 intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass iwlwifi crct10dif_pclmul crc32_pclmul ghash_clmulni_intel cfg80211 aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd snd_soc_rt5640 snd_soc_rl6231 snd_soc_ssm4567 serio_raw lpc_ich i915 shpchp binfmt_misc snd_hda_intel snd_soc_core snd_compress snd_hda_codec ac97_bus snd_seq_midi snd_seq_midi_event snd_rawmidi snd_pcm_dmaengine snd_hda_core snd_hwdep snd_pcm 8250_fintek snd_seq video snd_seq_device snd_timer drm_kms_helper snd elan_i2c 8250_dw drm dw_dmac i2c_hid hid dw_dmac_core mei_me fb_sys_fops syscopyarea snd_soc_sst_acpi i2c_designware_platform mac_hid sysfillrect spi_pxa2xx_platform mei i2c_designware_core soundcore acpi_pad sysimgblt acpi_als kfifo_buf industrialio lp parport igb psmouse ahci e1000e i2c_algo_bit libahci dca ptp pps_core fjes sdhci_acpi sdhci [Wed Dec 6 18:56:38 2017] CPU: 3 PID: 0 Comm: swapper/3 Not tainted 4.4.0-101-generic #124~14.04.1-Ubuntu [Wed Dec 6 18:56:38 2017] Hardware name: To be filled by O.E.M. To be filled by O.E.M./CRESCENTBAY, BIOS 5.6.5 12/14/2016 [Wed Dec 6 18:56:38 2017] 88012dd83d00 813dfc6c 88012dd83d48 [Wed Dec 6 18:56:38 2017] c07ca6e0 88012dd83d38 8107ea26 8800ca47 [Wed Dec 6 18:56:38 2017] 8800ca4735f0 88012dd83dd8 880128108bc0 [Wed Dec 6 18:56:38 2017] Call Trace: [Wed Dec 6 18:56:38 2017][] dump_stack+0x63/0x87 [Wed Dec 6 18:56:38 2017] [] warn_slowpath_common+0x86/0xc0 [Wed Dec 6 18:56:38 2017] [] warn_slowpath_fmt+0x4c/0x50 [Wed Dec 6 18:56:38 2017] [] ? iwl_read32+0x1f/0x90 [iwlwifi] [Wed Dec 6 18:56:38 2017] [] iwl_trans_pcie_grab_nic_access+0xf5/0x100 [iwlwifi] [Wed Dec 6 18:56:38 2017] [] iwl_trans_pcie_read_mem+0x2f/0xa0 [iwlwifi] [Wed Dec 6 18:56:38 2017] [] iwl_pcie_txq_stuck_timer+0xd8/0x390 [iwlwifi] [Wed Dec 6 18:56:38 2017] [] ? intel_pstate_timer_func+0x2db/0x3a0 [Wed Dec 6 18:56:38 2017] [] ? iwl_pcie_enqueue_hcmd+0xa90/0xa90 [iwlwifi] [Wed Dec 6 18:56:38 2017] [] call_timer_fn+0x35/0x130 [Wed Dec 6 18:56:38 2017] [] ? iwl_pcie_enqueue_hcmd+0xa90/0xa90 [iwlwifi] [Wed Dec 6 18:56:38 2017] [] run_timer_softirq+0x20e/0x2c0 [Wed Dec 6 18:56:38 2017] [] __do_softirq+0xdd/0x290 [Wed Dec 6 18:56:38 2017] [] irq_exit+0x95/0xa0 [Wed Dec 6 18:56:38 2017] [] smp_apic_timer_interrupt+0x42/0x50 [Wed Dec 6 18:56:38 2017] [] apic
[Kernel-packages] [Bug 1520343] Re: Qualcomm Atheros wireless card [168c:003e] (rev 32) not supported
** Changed in: oem-priority Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1520343 Title: Qualcomm Atheros wireless card [168c:003e] (rev 32) not supported Status in HWE Next: New Status in OEM Priority Project: Fix Released Status in linux-firmware package in Ubuntu: Confirmed Bug description: --- STATUS 2016-03-17: == WARNING: You need at least kernel 4.5.0 for the following new fix to work, else refer to the old method described in post #22 == The support for this card has now been merged to https://github.com/kvalo/ath10k-firmware. The repository now contains the required board.bin, board-2.bin and firmware-4.bin files for the card to initialize and connect to a bgn-access point (5GHz (ac- protocol) is still untested, feel free to modify this if you can confirm it works). Here are the new commands to get you online: sudo mkdir -p /lib/firmware/ath10k/QCA6174/hw3.0/ sudo rm /lib/firmware/ath10k/QCA6174/hw3.0/* 2> /dev/null sudo wget -O /lib/firmware/ath10k/QCA6174/hw3.0/board.bin https://github.com/kvalo/ath10k- firmware/blob/master/QCA6174/hw3.0/board.bin?raw=true sudo wget -O /lib/firmware/ath10k/QCA6174/hw3.0/board-2.bin https://github.com/kvalo/ath10k- firmware/blob/master/QCA6174/hw3.0/board-2.bin?raw=true sudo wget -O /lib/firmware/ath10k/QCA6174/hw3.0/firmware-4.bin https://github.com/kvalo/ath10k- firmware/blob/master/QCA6174/hw3.0/firmware-4.bin_WLAN.RM.2.0-00180-QCARMSWPZ-1?raw=true Reboot or reload the ath10k_pci module and you should be able to connect! --- STATUS 2015-12-22: Currently there is a fix for this problem in post #22 (originally post #19, but reposted due to command typos!) which seems to have fixed the issue for many. This bug is unique to revision 32 of the card [168c:003e], fixes for older revisions don't seem to work. There are a couple of issues regarding the fix for some people (not all): 1. Wireless works, but network throughput stops some time after connecting to access point 2. Bluetooth communications take a noticeable performance hit when transferring something over WiFi --- Original description: I have recently installed Ubuntu 15.10 (64-bit) alongside Windows 10 on an Acer Aspire VN7-792G-76ZH and discovered, that the Qualcomm wireless card doesn't work in it or 16.04. The card has the device id 168c:003e as many other cards, for example the Qualcomm Atheros Killer (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1383184), but it has a newer revision number (32) and the suggested fixes work only partially and the wireless is unusable. The computer has just been released this summer and is Intel Skylake -based. I've tried the patch from bug 1383184, which has a fix for the card revision 20: Make the directory /lib/firmware/ath10k/QCA6174/hw3.0/ and put in the patch files: board.bin firmware-4.bin notice_ath10k_firmware-4.txt ath10k_pci succeeds in loading the firmware, but it seems that the firmware is not working correctly: dmesg | grep ath [5.452683] ath10k_pci :07:00.0: pci irq msi-x interrupts 8 irq_mode 0 reset_mode 0 [5.678420] ath10k_pci :07:00.0: Direct firmware load for ath10k/cal-pci-:07:00.0.bin failed with error -2 [5.678773] ath10k_pci :07:00.0: Direct firmware load for ath10k/QCA6174/hw3.0/board-pci-168c:003e:11ad:0807.bin failed with error -2 [5.678781] ath10k_pci :07:00.0: failed to load spec board file, falling back to generic: -2 [5.679445] ath10k_pci :07:00.0: Direct firmware load for ath10k/QCA6174/hw3.0/firmware-5.bin failed with error -2 [5.679453] ath10k_pci :07:00.0: could not fetch firmware file 'ath10k/QCA6174/hw3.0/firmware-5.bin': -2 [7.802316] ath10k_pci :07:00.0: qca6174 hw3.2 (0x0503, 0x00340aff, 168c:003e:11ad:0807 fallback) fw WLAN.RM.2.0-00180-QCARMSWPZ-1 api 4 htt 3.26 wmi 4 cal otp max_sta 32 [7.802329] ath10k_pci :07:00.0: debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [8.200607] ath: EEPROM regdomain: 0x6c [8.200614] ath: EEPROM indicates we should expect a direct regpair map [8.200619] ath: Country alpha2 being used: 00 [8.200621] ath: Regpair used: 0x6c [8.216605] ath10k_pci :07:00.0 wlp7s0: renamed from wlan0 [ 13.462029] ath10k_pci :07:00.0: failed to enable dynamic BW: -11 [ 16.461416] ath10k_pci :07:00.0: could not suspend target (-11) [ 24.760062] ath10k_pci :07:00.0: failed to enable dynamic BW: -11 [ 27.759534] ath10k_pci :07:00.0: could not suspend target (-11) [ 36.
[Kernel-packages] [Bug 1673344] Re: Ubuntu 16.04 doesn't recongnize wifi card after loosing signal completely (intel 7260) even when I try to restart network manager
Final update on this. It turned out that using the 2.4 Ghz band was much more stable than 5 Ghz, which got wedged within minutes, but conditions eventually worsened until even on 2.4 Ghz without much internet usage it would get wedged every few hours. I then tried out various kernel versions on 16.04 LTS going all the way back to 4.4.9 and different versions of iwlwifi ucode with no success and different variations of dmesg output, even though I recalled the wifi working just fine back before upgrading to 17.10. Looking through other bugs, this one is very similar https://bugzilla.kernel.org/show_bug.cgi?id=191601 and there is a script that worked for me to reset the wifi without having to reboot, which was a major improvement. Clearly there wasn't a specific recent software change in Linux that caused this issue. Other people reporting this bug have reported it cropping up at different OS/kernel versions. The wifi still works perfectly fine on Windows 10, and the script to remove/re-add the PCI card via sysfs can recover the wifi. Based on all of these facts, I believe this is a longstanding hardware-software bug in Linux where it can't recover from certain conditions when there is hardware degradation on the PCI card - perhaps some timeout deadlock - that Windows either shrugs off or can recover from. Based on that hunch, I ordered a new 7260 half height PCI-E card, replaced it in my desktop, and wifi has been working perfectly since (a week or so). At this stage, this card is very old and no specific bug can be easily pinpointed. Furthermore it requires a somehow hardware degraded 7260 card to reproduce so a fix will be unlikely. In my opinion it is your best shot to buy a replacement 7260 card to tide you over until you upgrade your PC. ** Bug watch added: Linux Kernel Bug Tracker #191601 https://bugzilla.kernel.org/show_bug.cgi?id=191601 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1673344 Title: Ubuntu 16.04 doesn't recongnize wifi card after loosing signal completely (intel 7260) even when I try to restart network manager Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Confirmed Bug description: My wireless connection completely disappears and isn't recognized along with my NIC card and doesn't come back until I reboot even if I restart network manager. I've attached the required files showing what my wifi information looks like connected and what it looks like when the problem occurs hopefully a fix or workaround can be found this happens several times a day. Steps: 1) I boot up type in sudo iwconfig wlp3s0 power off (turn off power management) 2) $ iwconfig enp4s0f2 no wireless extensions. lono wireless extensions. wlp3s0IEEE 802.11 ESSID:"2.4ghz" Mode:Managed Frequency:2.437 GHz Access Point: E0:3F:29:93:3F:20 Bit Rate=144.4 Mb/s Tx-Power=22 dBm Retry short limit:7 RTS thr:off Fragment thr:off Power Management:off Link Quality=60/70 Signal level=-50 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:55 Missed beacon:0 3) I loose wifi using 5ghz or 2.4ghz after a certain amount of time 4) sudo rmmod iwlmvm iwlwifi && sudo modprobe iwlmvm iwlwifi 5) sudo systemctl restart network-manager.service I do a **iwconfig** and **I'm missing wlp3s0IEEE 802.11 ESSID:"2.4ghz"** $ iwconfig enp4s0f2 no wireless extensions. lono wireless extensions. I have to reboot to get my wifi back and for ubunutu to recognize my wifi card back how can I prevent this. $ uname -a Linux sys76 4.8.0-41-generic #44~16.04.1-Ubuntu SMP Fri Mar 3 17:11:16 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux $ dmesg | grep iwlwifi 876.891600] iwlwifi :03:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: enqueue_hcmd failed: -5 [ 876.891602] iwlwifi :03:00.0: Scan failed! ret -5 [ 877.909370] iwlwifi :03:00.0: Failed to wake NIC for hcmd [ 877.909397] iwlwifi :03:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: enqueue_hcmd failed: -5 [ 877.909409] iwlwifi :03:00.0: Scan failed! ret -5 [ 878.928277] iwlwifi :03:00.0: Failed to wake NIC for hcmd [ 878.928364] iwlwifi :03:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: enqueue_hcmd failed: -5 [ 878.928366] iwlwifi :03:00.0: Scan failed! ret -5 [ 879.947120] iwlwifi :03:00.0: Failed to wake NIC for hcmd [ 879.947170] iwlwifi :03:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: enqueue_hcmd failed: -5 [ 879.947172] iwlwifi :03:00.0: Scan failed!
[Kernel-packages] [Bug 1746418] Re: System freezes when starting Xorg after installing linux-image-4.13.0-32-generic
@jsalisbury : linux-image version 4.13.0-38.43 from artful-proposed still hangs. :( -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1746418 Title: System freezes when starting Xorg after installing linux- image-4.13.0-32-generic Status in linux package in Ubuntu: In Progress Status in linux source package in Artful: In Progress Bug description: My laptop (Lenovo T440) freezes when starting Xorg (lightdm) only after installing the latest ubuntu kernel for 17.10, linux- image-4.13.0-32-generic. Am running Xorg instead of MIR due to MIR crashing when I initially upgraded from 17.04 to 17.10, but that's a different problem for a different day. It's been running with Xorg stably for at least 2-3 months. If I boot with the previous kernel version on my /boot (linux- image-4.13.0-25-generic), everything works fine. If I boot with the latest mainline kernel from the Ubuntu mainline repo (4.15.0), everything works. Using grub's option to run "Recovery Mode" for the 4.13.0-32 kernel, I am able to use the CLI and access the encrypted root filesystem, which is how I generated the apport repo that's attached. It's only when telling it to continue Normal booting that it freezes, which is why I suspect the problem of being Xorg. When the system freezes, the fan starts to spin up. I cannot switch virtual consoles using CTRL-ALT-F{1-7}. CTRL-ALT-DEL pressed repeatedly doesn't do anything. To reboot, I have to hold the power button until the system powers off. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746418/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1730150] Re: Nautilus unable to see the storage in my Fuji HS30EXR PTP canera since upgrading from Ubuntu 17.04 to 17.10
[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/1730150 Title: Nautilus unable to see the storage in my Fuji HS30EXR PTP canera since upgrading from Ubuntu 17.04 to 17.10 Status in linux package in Ubuntu: Expired Bug description: What happens: Something appears to have changed in Nautilus after Nautilus version 1:3.20.4-0ubuntu2 (as in Ubuntu 17.04) and by version 1:3.26.0.0ubuntu1 (as in Ubuntu 17.10)*, causing the storage on my USB PTP camera (a Fujifilm HS30EXR) not to be visible to Nautilus when the camera is connected to the computer via USB and switched on. (Camera firmware was updated and the camera retested on two Ubuntu 17.10 computers) What is expected to happen: On my remaining Ubuntu 17.04 computer (and earlier versions) the camera always pops up in the Nautilus left-hand sidebar when the camera is connected via USB and switched on. To reproduce the bug: 1. Launch "Files" from the Dock 2. Connect a Fujifilm HS30EXR camera (WITH an SD card installed) via USB 3. Observe if camera can be browsed in Nautilus. What is still working: Three other cameras were tested and found not to have this problem with Nautilus: Acorn Ltl5310A (with SD card storage), Nikon P340 (SD card) and Olympus C8080WZ (xD and CF cards). More detail: Apport information report attached. Problem occurs when logged in to either Gnome or Unity Desktop in Ubuntu 17.10. On a prompt from an askubuntu.com user I also tested the Fuji camera on a Ubuntu 17.10 live USB (64 bit ISO downloaded 2 Nov 2017) and found the problem to occur there as well. Problems with Fuji cameras may have occurred in the past and been fixed - see Bug #1273498 * Problem may have appeared on or before Nautilus version 3.24.2.1 (Fedora WS 26), but was not observed in Fedora 25 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-generic 4.13.0-16.19 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: alan 1376 F pulseaudio /dev/snd/controlC0: alan 1376 F pulseaudio /dev/snd/controlC1: alan 1376 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Nov 5 11:33:43 2017 GvfsMonitorError: This tool has been deprecated, use 'gio mount' instead. See 'gio help mount' for more info. GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit. HibernationDevice: RESUME=UUID=d20ac35f-b382-4cd9-8e3d-89b62ff15b02 HotplugNewDevices: HotplugNewMounts: InstallationDate: Installed on 2017-02-09 (268 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: MSI MS-7817 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=4f5ff60f-71fa-4354-8c46-85a532f5e205 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 RfKill: SourcePackage: linux Symptom: storage UdisksMonitorLog: Monitoring the udisks daemon. Press Ctrl+C to exit. 11:34:19.352: The udisks-daemon is running (name-owner :1.1). UpgradeStatus: Upgraded to artful on 2017-10-20 (15 days ago) dmi.bios.date: 04/21/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V10.9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-E45 (MS-7817) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV10.9:bd04/21/2015:svnMSI:pnMS-7817:pvr2.0:rvnMSI:rnB85M-E45(MS-7817):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7817 dmi.product.version: 2.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730150/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1742867] Re: Screen blank, audio choppy, system locked
[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/1742867 Title: Screen blank, audio choppy, system locked Status in linux package in Ubuntu: Expired Bug description: While watching a YouTube video, screen went blank. Audio cut out, after a few seconds the audio started playing normally for a few more seconds then kept repeating the last half a second of audio for a few more seconds. Then it stopped and nothing responded. It did this a few times over the course of an hour. Had to power off the PC to get a reboot. Last time it did this I ssh'd from another PC to get dmesg and syslog info as it happened. Attaching those captures. clickwir@mach:~$ uname -a Linux mach 4.13.0-25-generic #29-Ubuntu SMP Mon Jan 8 21:14:41 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux clickwir@mach:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 17.10 Release:17.10 Codename: artful dmesg [ 10.136445] bond0: Enslaving enp7s0f1 as an active interface with an up link [ 10.136497] IPv6: ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready [ 10.144317] e1000e :07:00.0 enp7s0f0: changing MTU from 1500 to 9000 [ 10.310070] e1000e :07:00.1 enp7s0f1: changing MTU from 1500 to 9000 [ 10.625965] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 10.730200] r8169 :02:00.0 eth0: link down [ 10.730246] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 12.573052] e1000e: enp7s0f0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None [ 12.633055] e1000e: enp7s0f1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None [ 16.875586] FS-Cache: Loaded [ 16.896010] FS-Cache: Netfs 'nfs' registered for caching [ 16.914353] NFS: Registering the id_resolver key type [ 16.914364] Key type id_resolver registered [ 16.914364] Key type id_legacy registered [ 17.485539] ip6_tables: (C) 2000-2006 Netfilter Core Team [ 17.513074] Ebtables v2.0 registered [ 17.564084] radeon_dp_aux_transfer_native: 74 callbacks suppressed [ 17.863232] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this. [ 17.864899] virbr0: port 1(virbr0-nic) entered blocking state [ 17.864903] virbr0: port 1(virbr0-nic) entered disabled state [ 17.864995] device virbr0-nic entered promiscuous mode [ 17.960322] nf_conntrack version 0.5.0 (65536 buckets, 262144 max) [ 18.038385] virbr0: port 1(virbr0-nic) entered blocking state [ 18.038388] virbr0: port 1(virbr0-nic) entered listening state [ 18.095412] virbr0: port 1(virbr0-nic) entered disabled state [ 89.815180] radeon_dp_aux_transfer_native: 74 callbacks suppressed [ 92.062606] show_signal_msg: 27 callbacks suppressed [ 92.062608] xembedsniproxy[2507]: segfault at 2 ip 55ea4a6890d7 sp 7fff6c7a7c30 error 4 in xembedsniproxy[55ea4a67d000+13000] [ 95.955166] radeon_dp_aux_transfer_native: 74 callbacks suppressed ### abnormal begins here ### [ 1429.496584] sched: RT throttling activated [ 1429.706303] clocksource: timekeeping watchdog on CPU3: Marking clocksource 'tsc' as unstable because the skew is too large: [ 1429.706305] clocksource: 'hpet' wd_now: c4741f2e wd_last: c3bcdb60 mask: [ 1429.706306] clocksource: 'tsc' cs_now: 4acf553cc2d cs_last: 4ac71a54967 mask: [ 1429.706309] tsc: Marking TSC unstable due to clocksource watchdog [ 1434.739539] nfs: server 10.1.0.4 not responding, still trying [ 1437.469449] nfs: server 10.1.0.4 OK [ 1439.143494] TSC found unstable after boot, most likely due to broken BIOS. Use 'tsc=unstable'. [ 1439.143498] sched_clock: Marking unstable (1439092126811, 50992985)<-(1439477690212, -334199655) [ 1440.403916] clocksource: Switched to clocksource hpet [ 1443.553969] hrtimer: interrupt took 629117003 ns [ 1454.039245] INFO: NMI handler (nmi_cpu_backtrace_handler) took too long to run: 209.684 msecs [ 1454.454671] INFO: NMI handler (perf_event_nmi_handler) took too long to run: 44.646 msecs [ 1454.454673] perf: interrupt took too long (349007 > 2500), lowering kernel.perf_event_max_sample_rate to 500 [ 1455.293492] INFO: NMI handler (perf_event_nmi_handler) took too long to run: 61.329 msecs [ 1455.293494] perf: interrupt took too long (479410 > 436258), lowering kernel.perf_event_max_sample_rate to 250 [ 1463.284343] INFO: NMI handler (perf_event_nmi_handler) took too long to run: 172.103 msecs [ 1463.284345] perf: interrupt took too long (1344829 > 599262), lowering kernel.perf_event_max_sample_rate to 250 [ 14
[Kernel-packages] [Bug 1744094] Re: keyboard not working properly
[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/1744094 Title: keyboard not working properly Status in linux package in Ubuntu: Expired Bug description: I have installed ubuntu mate in lenovo g50 80 laptop. Some keys such as angular brackets,t,m,c are not working with shift key. only one shift key is working. Sometime keyboard stops working --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sandeep1679 F pulseaudio /dev/snd/controlC0: sandeep1679 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=d17a7ae9-6742-4d84-88e0-4b0b74a5ffcf InstallationDate: Installed on 2018-01-18 (0 days ago) InstallationMedia: Ubuntu-MATE 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:07dc Intel Corp. Bus 001 Device 003: ID 0bda:579a Realtek Semiconductor Corp. Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80E5 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-28-generic.efi.signed root=UUID=5362de9e-c844-4f1c-a8e0-321e8f998e35 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17 RelatedPackageVersions: linux-restricted-modules-4.10.0-28-generic N/A linux-backports-modules-4.10.0-28-generic N/A linux-firmware 1.157.14 Tags: xenial Uname: Linux 4.10.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/31/2015 dmi.bios.vendor: LENOVO dmi.bios.version: B0CN95WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo G50-80 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-80 dmi.modalias: dmi:bvnLENOVO:bvrB0CN95WW:bd07/31/2015:svnLENOVO:pn80E5:pvrLenovoG50-80:rvnLENOVO:rnLenovoG50-80:rvrNODPK:cvnLENOVO:ct10:cvrLenovoG50-80: dmi.product.name: 80E5 dmi.product.version: Lenovo G50-80 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1744094/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1744083] Re: 4.13 USB 03f0:3a1d HP hs2340 HSPA+ MobileBroadband fails to resume from S3 suspend
[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/1744083 Title: 4.13 USB 03f0:3a1d HP hs2340 HSPA+ MobileBroadband fails to resume from S3 suspend Status in linux package in Ubuntu: Expired Bug description: On 16.04 with linux-image-lowlatency-hwe-16.04 a mini-PCIe form-factor GSM cellular modem fails to resume after S3 suspend: [ 6632.711063] PM: resume of devices complete after 1659.009 msecs [ 6632.711290] usb 7-2.1:1.0: rebind failed: -517 [ 6632.711306] usb 7-2.1:1.1: rebind failed: -517 [ 6632.711844] PM: Finishing wakeup. lsusb Bus 002 Device 003: ID 03f0:3a1d Hewlett-Packard --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: tj 3968 F pulseaudio CurrentDesktop: LXDE DistroRelease: Ubuntu 16.04 EcryptfsInUse: Yes MachineType: Dell Inc. XPS M1530 Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-25-lowlatency root=/dev/mapper/VG_OS-ubuntu_16.04_rootfs ro pci=use_crs,realloc,assign-busses,pcie_scan_all acpi_osi=! "acpi_osi=Windows 2006" splash crashkernel=384M-2G:128M,2G-:256M vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-25.29~16.04.2-lowlatency 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-25-lowlatency N/A linux-backports-modules-4.13.0-25-lowlatency N/A linux-firmware1.157.15 Tags: xenial Uname: Linux 4.13.0-25-lowlatency x86_64 UpgradeStatus: Upgraded to xenial on 2017-09-17 (122 days ago) UserGroups: adm audio cdrom dialout disk floppy libvirtd lp lpadmin lxd plugdev root sudo users video wireshark _MarkForUpload: True dmi.bios.date: 11/19/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA12:bd11/19/2008:svnDellInc.:pnXPSM1530:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: XPS M1530 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1744083/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1744109] Re: Kernel Bug When High Memory Usage
[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/1744109 Title: Kernel Bug When High Memory Usage Status in linux package in Ubuntu: Expired Bug description: Dmesg shows that there is a kernel bug [825979.477960] /build/linux-SwhOyu/linux-4.4.0/mm/pgtable-generic.c:33: bad pmd 8809452bcc00(000dc62009e2) [826927.570746] huge_memory: mapcount 0 page_mapcount 1 [826927.570920] [ cut here ] [826927.571060] kernel BUG at /build/linux-SwhOyu/linux-4.4.0/mm/huge_memory.c:1941! [826927.571300] invalid opcode: [#1] SMP At the same time, we observed high memory usage. (I'm not sure which is the cause, in other words, high memory usage causes this bug or this bug causes high memory usage) $uname -a Linux sat-10 4.4.0-104-generic #127-Ubuntu SMP Mon Dec 11 12:16:42 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-104-generic 4.4.0-104.127 ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98 Uname: Linux 4.4.0-104-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 8 15:21 seq crw-rw 1 root audio 116, 33 Jan 8 15:21 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.15 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: Thu Jan 18 10:39:00 2018 HibernationDevice: RESUME=/dev/mapper/satx--vg-swap_1 InstallationDate: Installed on 2017-12-19 (30 days ago) InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge T630 PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-104-generic.efi.signed root=/dev/mapper/satx--vg-root ro RelatedPackageVersions: linux-restricted-modules-4.4.0-104-generic N/A linux-backports-modules-4.4.0-104-generic N/A linux-firmware 1.157.14 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/17/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.4 dmi.board.name: 0NT78X dmi.board.vendor: Dell Inc. dmi.board.version: A06 dmi.chassis.type: 17 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.4:bd08/17/2017:svnDellInc.:pnPowerEdgeT630:pvr:rvnDellInc.:rn0NT78X:rvrA06:cvnDellInc.:ct17:cvr: dmi.product.name: PowerEdge T630 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1744109/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1620762] Re: Support AverMedia DVD EZMaker 7 USB video capture dongle
I added the device ID to the kernel, so need to verify if this work out of the box. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1620762 Title: Support AverMedia DVD EZMaker 7 USB video capture dongle Status in linux package in Ubuntu: Confirmed Bug description: Linux doesn't support this capture. Link to patch https://www.linuxtv.org/wiki/index.php/AVerMedia_DVD_EZMaker_7_(C039). I tested it on Ubuntu 16.04 - OK. It will be great if this patch is built-in to kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1620762/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1729010] Re: USB hub stops working after suspend(s?)
having some trouble with the bisect: -in order to be able to test this, the built kernel needs to include commit 13cfc732160f7bc7e596128ce34cda361c556966 which allows suspend on this machine to work -the bisect is picking commits like 6afafa7799cf6fa3c0efb6887704506d21965ad6 that don't descend from the suspend fix commit -I've tried starting the bisect from 13cfc732160f7bc7e596128ce34cda361c556966 as 'good', but am still getting commits picked by the bisect that don't include that change. any pointers on bisecting bewteen 13cfc732160f7bc7e596128ce34cda361c556966 and v4.13-rc3 ? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1729010 Title: USB hub stops working after suspend(s?) Status in linux package in Ubuntu: Confirmed Bug description: On initial boot, my usb hub works fine, but after a (series of?) suspends, I stop being able to see devices that are plugged into it. journalctl output on plugging it in: Oct 31 07:08:36 spiny kernel: usb 1-1: new high-speed USB device number 21 using xhci_hcd Oct 31 07:08:36 spiny kernel: usb 1-1: New USB device found, idVendor=0409, idProduct=005a Oct 31 07:08:36 spiny kernel: usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 Oct 31 07:08:36 spiny kernel: hub 1-1:1.0: USB hub found Oct 31 07:08:36 spiny kernel: hub 1-1:1.0: 4 ports detected Oct 31 07:08:36 spiny kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC= SRC=fe80::::a299:9bff:fe17:9047 DST=ff02:::::::0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=32325 PROTO=UDP SPT=8612 DPT=8612 LEN=24 Oct 31 07:08:36 spiny kernel: usb 1-1.1: new high-speed USB device number 22 using xhci_hcd Oct 31 07:08:36 spiny kernel: usb 1-1.1: New USB device found, idVendor=0b95, idProduct=772a Oct 31 07:08:36 spiny kernel: usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Oct 31 07:08:36 spiny kernel: usb 1-1.1: Product: AX88x72A Oct 31 07:08:36 spiny kernel: usb 1-1.1: Manufacturer: ASIX Elec. Corp. Oct 31 07:08:36 spiny kernel: usb 1-1.1: SerialNumber: 47EDE2 Oct 31 07:08:37 spiny kernel: asix 1-1.1:1.0 eth0: register 'asix' at usb-:00:14.0-1.1, ASIX AX88772 USB 2.0 Ethernet, 00:50:b6:47:ed:e2 Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.0438] manager: (eth0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/7) Oct 31 07:08:37 spiny mtp-probe[13207]: checking bus 1, device 22: "/sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.1" Oct 31 07:08:37 spiny mtp-probe[13207]: bus: 1, device: 22 was not an MTP device Oct 31 07:08:37 spiny systemd-udevd[13206]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable. Oct 31 07:08:37 spiny kernel: asix 1-1.1:1.0 enx0050b647ede2: renamed from eth0 Oct 31 07:08:37 spiny pkexec[13215]: pam_unix(polkit-1:session): session opened for user root by (uid=1000) Oct 31 07:08:37 spiny pkexec[13215]: jbarnett: Executing command [USER=root] [TTY=unknown] [CWD=/home/jbarnett] [COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 31] Oct 31 07:08:37 spiny pkexec[13214]: gdm: Error executing command as another user: Not authorized [USER=root] [TTY=unknown] [CWD=/var/lib/gdm3] [COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 48] Oct 31 07:08:37 spiny org.gnome.SettingsDaemon.Power.desktop[2273]: Error executing command as another user: Not authorized Oct 31 07:08:37 spiny org.gnome.SettingsDaemon.Power.desktop[2273]: This incident has been reported. Oct 31 07:08:37 spiny systemd-networkd[1119]: eth0: Renamed to enx0050b647ede2 Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1066] device (eth0): interface index 10 renamed iface from 'eth0' to 'enx0050b647ede2' Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1214] devices added (path: /sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.1/1-1.1:1.0/net/enx0050b647ede2, iface: enx0050b647ede2) Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1214] device added (path: /sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.1/1-1.1:1.0/net/enx0050b647ede2, iface: enx0050b647ede2): no ifupdown configuration found. Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1217] device (enx0050b647ede2): state change: unmanaged -> unavailable (reason 'managed', internal state 'external') Oct 31 07:08:37 spiny kernel: IPv6: ADDRCONF(NETDEV_UP): enx0050b647ede2: link is not ready Oct 31 07:08:37 spiny kernel: IPv6: ADDRCONF(NETDEV_UP): enx0050b647ede2: link is not ready Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1274] keyfile: add connection in-memory (9365f42f-9dd9-3bdc-bbad-e7062efcaf7c,"Wired connection 4") Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1284] settings: (enx0050b647ede2): created default wired connection 'Wired c
[Kernel-packages] [Bug 1729010] Re: USB hub stops working after suspend(s?)
(I have confirmed that building at 13cfc732160f7bc7e596128ce34cda361c556966 does not exhibit the bug, fwiw) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1729010 Title: USB hub stops working after suspend(s?) Status in linux package in Ubuntu: Confirmed Bug description: On initial boot, my usb hub works fine, but after a (series of?) suspends, I stop being able to see devices that are plugged into it. journalctl output on plugging it in: Oct 31 07:08:36 spiny kernel: usb 1-1: new high-speed USB device number 21 using xhci_hcd Oct 31 07:08:36 spiny kernel: usb 1-1: New USB device found, idVendor=0409, idProduct=005a Oct 31 07:08:36 spiny kernel: usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 Oct 31 07:08:36 spiny kernel: hub 1-1:1.0: USB hub found Oct 31 07:08:36 spiny kernel: hub 1-1:1.0: 4 ports detected Oct 31 07:08:36 spiny kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC= SRC=fe80::::a299:9bff:fe17:9047 DST=ff02:::::::0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=32325 PROTO=UDP SPT=8612 DPT=8612 LEN=24 Oct 31 07:08:36 spiny kernel: usb 1-1.1: new high-speed USB device number 22 using xhci_hcd Oct 31 07:08:36 spiny kernel: usb 1-1.1: New USB device found, idVendor=0b95, idProduct=772a Oct 31 07:08:36 spiny kernel: usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Oct 31 07:08:36 spiny kernel: usb 1-1.1: Product: AX88x72A Oct 31 07:08:36 spiny kernel: usb 1-1.1: Manufacturer: ASIX Elec. Corp. Oct 31 07:08:36 spiny kernel: usb 1-1.1: SerialNumber: 47EDE2 Oct 31 07:08:37 spiny kernel: asix 1-1.1:1.0 eth0: register 'asix' at usb-:00:14.0-1.1, ASIX AX88772 USB 2.0 Ethernet, 00:50:b6:47:ed:e2 Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.0438] manager: (eth0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/7) Oct 31 07:08:37 spiny mtp-probe[13207]: checking bus 1, device 22: "/sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.1" Oct 31 07:08:37 spiny mtp-probe[13207]: bus: 1, device: 22 was not an MTP device Oct 31 07:08:37 spiny systemd-udevd[13206]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable. Oct 31 07:08:37 spiny kernel: asix 1-1.1:1.0 enx0050b647ede2: renamed from eth0 Oct 31 07:08:37 spiny pkexec[13215]: pam_unix(polkit-1:session): session opened for user root by (uid=1000) Oct 31 07:08:37 spiny pkexec[13215]: jbarnett: Executing command [USER=root] [TTY=unknown] [CWD=/home/jbarnett] [COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 31] Oct 31 07:08:37 spiny pkexec[13214]: gdm: Error executing command as another user: Not authorized [USER=root] [TTY=unknown] [CWD=/var/lib/gdm3] [COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 48] Oct 31 07:08:37 spiny org.gnome.SettingsDaemon.Power.desktop[2273]: Error executing command as another user: Not authorized Oct 31 07:08:37 spiny org.gnome.SettingsDaemon.Power.desktop[2273]: This incident has been reported. Oct 31 07:08:37 spiny systemd-networkd[1119]: eth0: Renamed to enx0050b647ede2 Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1066] device (eth0): interface index 10 renamed iface from 'eth0' to 'enx0050b647ede2' Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1214] devices added (path: /sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.1/1-1.1:1.0/net/enx0050b647ede2, iface: enx0050b647ede2) Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1214] device added (path: /sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.1/1-1.1:1.0/net/enx0050b647ede2, iface: enx0050b647ede2): no ifupdown configuration found. Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1217] device (enx0050b647ede2): state change: unmanaged -> unavailable (reason 'managed', internal state 'external') Oct 31 07:08:37 spiny kernel: IPv6: ADDRCONF(NETDEV_UP): enx0050b647ede2: link is not ready Oct 31 07:08:37 spiny kernel: IPv6: ADDRCONF(NETDEV_UP): enx0050b647ede2: link is not ready Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1274] keyfile: add connection in-memory (9365f42f-9dd9-3bdc-bbad-e7062efcaf7c,"Wired connection 4") Oct 31 07:08:37 spiny NetworkManager[11575]: [1509458917.1284] settings: (enx0050b647ede2): created default wired connection 'Wired connection 4' Oct 31 07:08:37 spiny systemd[1]: Starting systemd-resolved-update-resolvconf.service... Oct 31 07:08:37 spiny systemd[1]: Started systemd-resolved-update-resolvconf.service. Oct 31 07:08:37 spiny kernel: usb 1-1.2: new full-speed USB device number 23 using xhci_hcd Oct 31 07:08:37 spiny kernel: usb 1-1.2: New USB device found, idVendor=0d8c, idProduct=0105 Oct 31 07:08:37 spiny kernel: usb 1-1.2: New USB device strings: Mfr=3, Product=1, SerialNumber
[Kernel-packages] [Bug 1661876] Re: [Asus UX360UA] battery status in unity-panel is not changing when battery is being charged
The first mainline kernel that support this is v4.16-rc1. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1661876 Title: [Asus UX360UA] battery status in unity-panel is not changing when battery is being charged Status in linux package in Ubuntu: Fix Released Status in linux source package in Artful: Fix Committed Bug description: === SRU Justification === [Impact] Some Asus laptops report "discharging" when the battery is full and AC is plugged [Test] Charge battery to full, the issue appears. Users report with the patch the behaviour is correct. [Fix] The discharge rate is 0 on those machines. Use that to detect the wrong status report. [Regression Potential] Low. The quirk uses strict DMI to match affected systems. === Original Bug Report === I've just installed Ubuntu 16.04.1 in dualboot on top of an Asus UX360UA, alongside with Windows 10. I've already installed the updates meanwhile. When I start charging my computer the battery icon on the unity-panel is not changing (it stays in the 98% complete). This is strange because this is a fresh installation so I didn't change any configuration yet. Also, when I tried this ubuntu in the live pen, I noticed that the icon changed when I started charging the laptop. That's why I think it is a bug. --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tjiagom1806 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0eaf9255-c29a-41b7-8449-1eb52f637933 InstallationDate: Installed on 2017-02-04 (0 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 04f2:b56b Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX360UA Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic.efi.signed root=UUID=6ca1f963-632a-401d-80db-610ef37f1f26 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40 RelatedPackageVersions: linux-restricted-modules-4.4.0-62-generic N/A linux-backports-modules-4.4.0-62-generic N/A linux-firmware1.157.6 Tags: xenial Uname: Linux 4.4.0-62-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/17/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX360UA.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX360UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX360UA.300:bd06/17/2016:svnASUSTeKCOMPUTERINC.:pnUX360UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX360UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX360UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1661876/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1733605] Re: elantech touchpad of Lenovo L480/580 failed to detect hw_version
** Tags removed: verification-needed-artful verification-needed-xenial ** Tags added: verification-done-artful verification-done-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/1733605 Title: elantech touchpad of Lenovo L480/580 failed to detect hw_version Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Committed Status in linux-oem source package in Xenial: Fix Released Status in linux source package in Artful: Fix Committed Status in linux-oem source package in Artful: Invalid Bug description: Elantech touchpad on Lenovo laptops L480/580 report it's version as 15, and current kernel can not support this hw_version, so driver didn't support horizontal,vertical and multi-touch. error log: kernel: psmouse serio1: elantech: unknown hardware version, aborting... To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1733605/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1748345] Re: QCA9377 requires more IRAM banks for its new firmware
** No longer affects: linux-firmware (Ubuntu) ** No longer affects: linux-firmware (Ubuntu Xenial) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1748345 Title: QCA9377 requires more IRAM banks for its new firmware Status in HWE Next: Fix Released Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Xenial: Fix Released Bug description: [Impact] The new firmware for QCA9377 supports Qualcomm's RED(Radio Equipment Directive) compliance and requires more IRAM banks. The origin 4 banks doesn't fit the new BDF and firmware. [Fix] Change the bank number from 4 to 9. [Regression Potential] Low, increasing the number of IRAM banks should be no harm. [Misc] Currently, both driver patch and new firmware do not upstream yet. For the sake of avoiding dkms package, we can change t he IRAM bank number before their patch is ready. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1748345/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1738523] Re: [SRU] External HDMI monitor failed to show screen on Lenovo X1 series
** Tags removed: verification-needed-artful ** Tags added: verification-done-artful ** Changed in: hwe-next Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1738523 Title: [SRU] External HDMI monitor failed to show screen on Lenovo X1 series Status in HWE Next: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Status in linux-oem source package in Xenial: Fix Released Status in linux source package in Artful: Fix Committed Status in linux-oem source package in Artful: Invalid Bug description: Thinkpad X1 yoga: CPU: Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz (family: 0x6, model: 0x8e, stepping: 0xa) GPU: Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Steps: 1, Connect an external monitor 2, Try to switch display modes in mirrored, extended, displayed on external or internal. [Impact] External HDMI monitor failed to show screen on Lenovo X1 yoga/carbon [Fix] Add a workaround to bypass this TMDS_OE writing on identified laptop models. [Test Case] Tested on ThinkPad X1 yoga 2nd/3rd and Carbon 6th, external HDMI output OK. [Regression Potential] Low, it limits to ThinkPad specific laptops. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1738523/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1746002] Re: [SRU] TrackPoint: middle button doesn't work on TrackPoint-compatible device.
** Tags removed: verification-needed-artful ** Tags added: verification-done-artful ** Changed in: hwe-next Status: New => Fix Released ** Changed in: linux (Ubuntu) Status: Incomplete => 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/1746002 Title: [SRU] TrackPoint: middle button doesn't work on TrackPoint-compatible device. Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Status in linux-oem source package in Xenial: Fix Released Status in linux source package in Artful: Fix Committed Status in linux-oem source package in Artful: Invalid Bug description: Lenovo introduced 4 new TrackPoint compatible sticks those only support the minimum commands described in the spec, which has been used in the current Windows driver. Legacy TrackPoint: 0101 – 0E01 ALPS: 0102 – FF02 ELAN:0103 – FF03 NXP: 0104 – FF04 TrackPoint (ID: 01/02) report 0 button when reading the EXT_BUTTON command. Setting middle button enabled to make it work. Upstream patch: commit f5d07b9e98022d50720e38aa936fc11c67868ece Author: Aaron Ma Date: Fri Jan 19 09:43:39 2018 -0800 Input: trackpoint - force 3 buttons if 0 button is reported Lenovo introduced trackpoint compatible sticks with minimum PS/2 commands. They supposed to reply with 0x02, 0x03, or 0x04 in response to the "Read Extended ID" command, so we would know not to try certain extended commands. Unfortunately even some trackpoints reporting the original IBM version (0x01 firmware 0x0e) now respond with incorrect data to the "Get Extended Buttons" command: thinkpad_acpi: ThinkPad BIOS R0DET87W (1.87 ), EC unknown thinkpad_acpi: Lenovo ThinkPad E470, model 20H1004SGE psmouse serio2: trackpoint: IBM TrackPoint firmware: 0x0e, buttons: 0/0 Since there are no trackpoints without buttons, let's assume the trackpoint has 3 buttons when we get 0 response to the extended buttons query. Signed-off-by: Aaron Ma Fixes: https://bugzilla.kernel.org/show_bug.cgi?id=196253 Cc: sta...@vger.kernel.org Signed-off-by: Dmitry Torokhov SRU justification: == [Impact] Middle button on some TrackPoints with ThinkPad can't work on Ubuntu 16.04. Lenovo introduced 4 new TrackPoint compatible sticks those only support minimum commands, Sticks with ID 01/02 reported the external button 0, TrackPoint always have 3 buttons. [Fix] Set 3 buttons when 0 button is reported via PS/2 commands. [Test Case] Tested on Finn and E470, middle button works with this patch. [Regression Potential] No regression is expected. This patch had been send to stable kernel, so Bionic should have it with stable updates. Aaron Ma (1): Input: trackpoint - force 3 buttons if 0 button is reported drivers/input/mouse/trackpoint.c | 3 +++ 1 file changed, 3 insertions(+) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1746002/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1753347] Re: [SRU] Lenovo E41 Mic mute hotkey is not responding
** Changed in: hwe-next Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1753347 Title: [SRU] Lenovo E41 Mic mute hotkey is not responding Status in HWE Next: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Artful: Fix Committed Bug description: [Impact] Mic mute hotkey (F1) is not working due to the delay answer when reading EC VPC. The ideapad_laptop module didn't wait enough time to read VPC. [Fix] Add more time to wait for reading EC VPC, the correct data will be got. Hotkey works well then. [Test Case] Tested on Lenovo E41, hotkey works well with this patch. [Regression Potential] No regression is expected. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1753347/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1741166] Re: [0cf3:e010] QCA6174A XR failed to pair with bt 4.0 device
** Tags removed: verification-needed-artful ** Tags added: verification-done-artful -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1741166 Title: [0cf3:e010] QCA6174A XR failed to pair with bt 4.0 device Status in OEM Priority Project: Triaged Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Status in linux-oem source package in Xenial: Fix Released Status in linux source package in Artful: Fix Committed Status in linux-oem source package in Artful: Invalid Bug description: [Impact] QCA6174A XR can scan but can't pair with bt 4.0 device. [Fix] [0cf3:e010] is one of the QCA ROME family and should be listed in btusb driver. [Test Case] Applied the patch and can pair with bt 4.0 keyboard without any issue. [Regression Potential] Adding the device to the list won't have any regression potential. impacted tickets: LP: #1736330 LP: #1742849 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1741166/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1755227] Re: linux: 3.13.0-144.193 -proposed tracker
3.13.0-144.193 - generic Regression test CMPL. Issue to note in amd64: ubuntu_kvm_smoke_test - uvt-kvm wait issue (bug 1732883) ubuntu_kvm_unit_tests - 40 failed on amaura, 39 failed on pepe Issue to note in arm64: hwclock - issue for HP m400 (bug 1716603) libhugetlbfs - noresv-preserve-resv-page failed (bug 1747823) chunk-overcommit failed (bug 1747828) ubuntu_cts_kernel - lp1262692 failed, bug for iproute2 (bug 1715376) ubuntu_kvm_smoke_test - uvt-kvm wait issue (bug 1732883) ubuntu_qrt_apparmor - test_old_trusty_regression_testsuite failed to build, bug 1699987 ubuntu_qrt_kernel_security - test 060 should be skipped (bug 1712038) test 021, 022 (bug 1747847) test 050 (bug 1684776) test 072 (bug 1747850) test 072 (bug 1747852) test 075 (bug 1712007) test 82 (bug 1747853) test 140 (bug 1747855) Issue to note in i386: ubuntu_kvm_smoke_test - uvt-kvm wait issue (bug 1732883) ubuntu_kvm_unit_tests - 15 failed on pepe (vmexit*, msr, realmode, syscall, tsc, hyperv_clock) Issue to note in ppc64le: ubuntu_cts_kernel - lp1262692 failed, bug for iproute2 (bug 1715376) ubuntu_kvm_smoke_test - no supported architecture for 'hvm' (bug 1752550) ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin (cypressyew) ** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1755227 Title: linux: 3.13.0-144.193 -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: Fix Released 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 Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1755228 (linux-lts-trusty) derivatives: -- swm properties -- boot-testing-requested: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1755227/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1757008] Re: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.2: bcmwl kernel module failed to build [error: implicit declaration of function ‘init_timer’]
** Summary changed: - bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.2: bcmwl kernel module failed to build + bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.2: bcmwl kernel module failed to build [error: implicit declaration of function ‘init_timer’] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1757008 Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.2: bcmwl kernel module failed to build [error: implicit declaration of function ‘init_timer’] Status in bcmwl package in Ubuntu: New Bug description: The module fails to build, as it is missing the necessary patches for the latest HWE kernel. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.2 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 DKMSKernelVersion: 4.15.0-13-generic Date: Mon Mar 19 15:02:46 2018 DuplicateSignature: dkms:bcmwl-kernel-source:6.30.223.271+bdcom-0ubuntu1~1.2:/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:2359:2: error: implicit declaration of function ‘init_timer’ [-Werror=implicit-function-declaration] InstallationDate: Installed on 2017-06-05 (287 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageVersion: 6.30.223.271+bdcom-0ubuntu1~1.2 RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.2: bcmwl kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1757008/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1753347] Re: [SRU] Lenovo E41 Mic mute hotkey is not responding
** Tags removed: verification-needed-artful ** Tags added: verification-done-artful -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1753347 Title: [SRU] Lenovo E41 Mic mute hotkey is not responding Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Artful: Fix Committed Bug description: [Impact] Mic mute hotkey (F1) is not working due to the delay answer when reading EC VPC. The ideapad_laptop module didn't wait enough time to read VPC. [Fix] Add more time to wait for reading EC VPC, the correct data will be got. Hotkey works well then. [Test Case] Tested on Lenovo E41, hotkey works well with this patch. [Regression Potential] No regression is expected. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1753347/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 424215] Re: Bluetooth mouse usage makes A2DP audio stutter
This bug is closed, rightly or wrongly. And has been closed for several years. If you have any ongoing issues then please log a new bug by running this command: ubuntu-bug bluez -- 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/424215 Title: Bluetooth mouse usage makes A2DP audio stutter Status in bluez package in Ubuntu: Fix Released Bug description: Binary package hint: bluez When I use my Bluetooth A2DP headset (Philips SHB7102) together with my mouse (Lenovo Bluetooth Laser Mouse), I notice this: Whenever I leave the mouse still for a few seconds (it seems to enter some kind of lower-power-mode) and then start to move it, my music most of the time skips for a second. This makes using these two bluetooth devices together quite annoying... The adapter is a Lenovo "ThinkPad Bluetooth with Enhanced Data Rate II" (Bus 004 Device 005: ID 0a5c:2145 Broadcom Corp.) I am running current karmic amd64 (linux 2.6.31-9). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/424215/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1757021] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1757021 Title: ubuntu restarts on resume from hibernate Status in linux package in Ubuntu: Confirmed Bug description: Whenever I sleep the computer, upon waking/opening the lid, it reboots. I tried Xorg instead of Wayland, gdm3 instead of lightdm, adding "GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_sleep=nonvs"" to /etc/default/grub. Nothing seems to help. I believe this started after updating to 17.10. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-32-generic 4.13.0-32.35 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: eric 1809 F pulseaudio /dev/snd/controlC0: eric 1809 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Mar 19 20:50:52 2018 HibernationDevice: RESUME=UUID=8b38df66-5f13-4d9d-8f86-9dd588521691 InstallationDate: Installed on 2017-05-29 (294 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Dell Inc. Inspiron 7352 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-32-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi_sleep=nonvs vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-32-generic N/A linux-backports-modules-4.13.0-32-generic N/A linux-firmware 1.169.3 SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-11-02 (137 days ago) dmi.bios.date: 11/13/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0H9K1J dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A08 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd11/13/2015:svnDellInc.:pnInspiron7352:pvrA08:rvnDellInc.:rn0H9K1J:rvrA00:cvnDellInc.:ct10:cvrA08: dmi.product.name: Inspiron 7352 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757021/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1711283] Re: few kernel selftest failed on Ubuntu 17.10
** Tags removed: bugnameltc-157168 kernel-da-key severity-high triage-a -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1711283 Title: few kernel selftest failed on Ubuntu 17.10 Status in The Ubuntu-power-systems project: Won't Fix Status in linux package in Ubuntu: Won't Fix Bug description: == Comment: #0 - Harish Sriram - 2017-08-01 05:11:09 == Problem Description Few kernel selftest failed on Ubuntu 17.10 Environment -- Kernel Build: 4.11.0-10-generic System Name : ltc-test-ci2 Model : 8247-22L Platform: PowerNV ( P8 ) Uname output --- # uname -a Linux ltc-test-ci2 4.11.0-10-generic #15-Ubuntu SMP Thu Jun 29 15:02:54 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux Steps to reproduce: 1. Get kernel source using apt source 2. Start powerpc specific tests The following FAILS are observed. selftests: cycles_test [FAIL] selftests: cycles_with_freeze_test [FAIL] selftests: pmc56_overflow_test [FAIL] selftests: ebb_vs_cpu_event_test [FAIL] selftests: cpu_event_vs_ebb_test [FAIL] selftests: task_event_vs_ebb_test [FAIL] selftests: multi_ebb_procs_test [FAIL] selftests: multi_counter_test [FAIL] selftests: pmae_handling_test [FAIL] selftests: close_clears_pmcc_test [FAIL] selftests: instruction_count_test [FAIL] selftests: ebb_on_willing_child_test [FAIL] selftests: back_to_back_ebbs_test [FAIL] selftests: lost_exception_test [FAIL] selftests: cycles_with_mmcr2_test [FAIL] selftests: tm-vmxcopy [FAIL] Full run log is attached. == Comment: #5 - Harish Sriram - 2017-08-08 03:33:36 == With the latest ubuntu mainline kernel 4.13-rc4 from http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13-rc4/, I see following additional failures selftests: ptrace-gpr [FAIL] selftests: ptrace-tm-gpr [FAIL] selftests: ptrace-tm-spd-gpr [FAIL] # uname -a Linux ltc-test-ci2 4.13.0-041300rc4-generic #201708062231 SMP Mon Aug 7 03:29:19 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux Thanks, Harish To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1711283/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1740972] Re: No external microphone be detected via headset jack on a dell machine
** Tags removed: verification-needed-artful ** Tags added: verification-done-artful -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1740972 Title: No external microphone be detected via headset jack on a dell machine Status in HWE Next: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux-oem package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Status in linux-oem source package in Xenial: Fix Released Status in linux source package in Artful: Fix Committed Status in linux-oem source package in Artful: Invalid Bug description: Plug a headset into the headset jack check external microphone Expected results: external microphone should wrok well Actual results: No external microphone be detected To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1740972/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1740971] Re: Can't detect external headset via line-out jack on some Dell machines
** Tags removed: verification-needed-artful ** Tags added: verification-done-artful -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1740971 Title: Can't detect external headset via line-out jack on some Dell machines Status in HWE Next: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux-oem package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Status in linux-oem source package in Xenial: Fix Released Status in linux source package in Artful: Fix Committed Status in linux-oem source package in Artful: Invalid Bug description: insert a headset to line-out jack Expected results: system should detect line-out port and sound output through line-out jack Actual results: Can't detect external headset via line-out jack To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1740971/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1737873] Re: [Feature][GLK] Enable L2 CDP (Code and Data Prioritization)
** Changed in: linux (Ubuntu Bionic) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1737873 Title: [Feature][GLK] Enable L2 CDP (Code and Data Prioritization) Status in intel: New Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: Description: L2 CDP separates code and data in L2 cache allocation. First implemented in Gemini Lake processor. It's an extension of L2 CAT and similar to already released L3 CDP. The L2 CDP is supposed to be published in Dec SDM. Target Kernel: 4.16 Target Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1737873/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1740974] Re: [800 G3 SFF] [800 G3 DM]External microphone of headset(3-ring) is working, 2-ring mic not working, both not shown in sound settings
** Tags removed: verification-needed-artful ** Tags added: verification-done-artful -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1740974 Title: [800 G3 SFF] [800 G3 DM]External microphone of headset(3-ring) is working, 2-ring mic not working, both not shown in sound settings Status in HWE Next: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux-oem package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Status in linux-oem source package in Xenial: Fix Released Status in linux source package in Artful: Fix Committed Status in linux-oem source package in Artful: Invalid Bug description: External microphone of headset(3-ring) is working, 2-ring mic not working, both not shown in sound settings. Steps: 1. Plug headset(3-ring) or microphone (2-ring) 2. Observe input device in sound setting Expected results: Microphone should be detected and working Actual results: Microphone is not detected, only 3-ring mic (from headset) is working To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1740974/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1757021] [NEW] ubuntu restarts on resume from hibernate
Public bug reported: Whenever I sleep the computer, upon waking/opening the lid, it reboots. I tried Xorg instead of Wayland, gdm3 instead of lightdm, adding "GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_sleep=nonvs"" to /etc/default/grub. Nothing seems to help. I believe this started after updating to 17.10. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-32-generic 4.13.0-32.35 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: eric 1809 F pulseaudio /dev/snd/controlC0: eric 1809 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Mar 19 20:50:52 2018 HibernationDevice: RESUME=UUID=8b38df66-5f13-4d9d-8f86-9dd588521691 InstallationDate: Installed on 2017-05-29 (294 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Dell Inc. Inspiron 7352 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-32-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi_sleep=nonvs vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-32-generic N/A linux-backports-modules-4.13.0-32-generic N/A linux-firmware 1.169.3 SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-11-02 (137 days ago) dmi.bios.date: 11/13/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0H9K1J dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A08 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd11/13/2015:svnDellInc.:pnInspiron7352:pvrA08:rvnDellInc.:rn0H9K1J:rvrA00:cvnDellInc.:ct10:cvrA08: dmi.product.name: Inspiron 7352 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful ** Attachment added: "info.log" https://bugs.launchpad.net/bugs/1757021/+attachment/5084563/+files/info.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1757021 Title: ubuntu restarts on resume from hibernate Status in linux package in Ubuntu: New Bug description: Whenever I sleep the computer, upon waking/opening the lid, it reboots. I tried Xorg instead of Wayland, gdm3 instead of lightdm, adding "GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_sleep=nonvs"" to /etc/default/grub. Nothing seems to help. I believe this started after updating to 17.10. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-32-generic 4.13.0-32.35 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: eric 1809 F pulseaudio /dev/snd/controlC0: eric 1809 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Mar 19 20:50:52 2018 HibernationDevice: RESUME=UUID=8b38df66-5f13-4d9d-8f86-9dd588521691 InstallationDate: Installed on 2017-05-29 (294 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Dell Inc. Inspiron 7352 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-32-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi_sleep=nonvs vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-32-generic N/A linux-backports-modules-4.13.0-32-generic N/A linux-firmware 1.169.3 SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-11-02 (137 days ago) dmi.bios.date: 11/13/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0H9K1J dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A08 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd11/13/2015:svnDellInc.:pnInspiron7352:pvrA08:rvnDellInc.:rn0H9K1J:rvrA00:cvnDellInc.:ct10:cvrA08: dmi.product.name: Inspiron 7352 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757021/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1743672] Re: the wifi driver is always hard blocked on a lenovo laptop
** Tags removed: verification-needed-artful ** Tags added: verification-done-artful -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1743672 Title: the wifi driver is always hard blocked on a lenovo laptop Status in HWE Next: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux-oem package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Status in linux-oem source package in Xenial: Fix Released Status in linux source package in Artful: Fix Committed Status in linux-oem source package in Artful: Invalid Bug description: On this machine, there is no wifi enable/disable hw switch, but the wifi driver is always reported the wifi radio is hard blocked by switch. The kernel is Artful and OEM kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1743672/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1748807] Re: headset mic can't be detected on two Dell machines
** Tags removed: verification-needed-artful ** Tags added: verification-done-artful -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1748807 Title: headset mic can't be detected on two Dell machines Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Status in linux-oem source package in Xenial: Fix Released Status in linux source package in Artful: Fix Committed Status in linux-oem source package in Artful: Invalid Bug description: == SRU Justification == [Test Case] plug the headset and record the sound [Fix] two upstream commits [Regression Potential] low, since the 0001-xxx.patch just adds vendor id to existing driver to let them support headset mode, it doesn't change existing functions, the 0002-xxx.patch adds a group of pin definition, it doesn't change existing funcitons too. Hui Wang (1): ALSA: hda - Fix headset mic detection problem for two Dell machines Kailang Yang (1): ALSA: hda/realtek - Support headset mode for ALC215/ALC285/ALC289 sound/pci/hda/patch_realtek.c | 27 +++ 1 file changed, 27 insertions(+) --- One machine is with the codec alc289, the other one is with the codec alc256. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1748807/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1740973] Re: Two front mics can't work on a lenovo machine
** Tags removed: verification-needed-artful ** Tags added: verification-done-artful -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1740973 Title: Two front mics can't work on a lenovo machine Status in HWE Next: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux-oem package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Status in linux-oem source package in Xenial: Fix Released Status in linux source package in Artful: Fix Committed Status in linux-oem source package in Artful: Invalid Bug description: There are two front mics on this lenovo machine. The test case 'audio/microphone-plug-detection' is always failed To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1740973/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1738911] Re: Support realtek new codec alc257 in the alsa hda driver
** Tags removed: verification-needed-artful ** Tags added: verification-done-artful -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1738911 Title: Support realtek new codec alc257 in the alsa hda driver Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Status in linux-oem source package in Xenial: Fix Released Status in linux source package in Artful: Fix Committed Status in linux-oem source package in Artful: Invalid Bug description: Otherwise, the kernel will load generic codec driver, this will introduce lots of problem like mute/micmute hotkey can't work. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1738911/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 696435] Re: wait-for-root fails to detect nbd root
** Branch unlinked: lp:~xnox/britney/custom-kernels-cannot-pass -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/696435 Title: wait-for-root fails to detect nbd root Status in linux package in Ubuntu: Fix Released Status in nbd package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in systemd source package in Xenial: Fix Committed Bug description: [Impact] Kernel does not generate any events when ndb-client connects /dev/nbd0 devices, therefore it is impossible to monitor/react to the state of /dev/nbd0. [Fix] Generate change uevent when size of /dev/nbd0 changes [Testcase] * Start udevadm monitor * modprobe nbd * use ndb-client to connect something to /dev/nbd0 * observe that there are change udev events generated on /dev/nbd0 itself [Regression Potential] There is no change to existing uevents, or their ordering. There is now an addition change event which will cause systemd to mark ndb devices as ready and trigger appropriate actions [Original Bug Report] When using an nbd root, wait-for-root blocks for 30 seconds before booting continues successfully. Using Ubuntu Natty, related packages versions: nbd-client 1:2.9.16-6ubuntu1 initramfs-tools 0.98.1ubuntu9 The wait-for-root call from /usr/share/initramfs-tools/scripts/local: while [ -z "${FSTYPE}" ]; do FSTYPE=$(wait-for-root "${ROOT}" ${ROOTDELAY:-30}) # Run failure hooks, hoping one of them can fix up the system # and we can restart the wait loop. If they all fail, abort # and move on to the panic handler and shell. if [ -z "${FSTYPE}" ] && ! try_failure_hooks; then break fi done I replaced wait-for-root with a sh script that did `set >&2`, here are the relevant environment variables at the time wait-for-root was called: ROOT='/dev/nbd0' ROOTDELAY='' ROOTFLAGS='' ROOTFSTYPE='' nbdroot='192.168.0.1,2011' It's probably worth noting that "nbd0: unknown partition table" was displayed asynchronously 1-2 seconds after wait-for-root was invoked and while it was still waiting. But I tried adding a "sleep 5" as the last line of local-top/nbd, so that the nbd message was displayed a lot before wait-for-root was called, and it didn't make a difference. So I don't think a race condition is involved in this problem. Temporarily I'm passing rootdelay=1 in the kernel command line to work around the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/696435/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1742316] Re: DVB Card with SAA7146 chipset not working
Kernel 4.13.0-38-generic #43-Ubuntu SMP Wed Mar 14 15:23:42 UTC 2018 i686 i686 i686 GNU/Linux from artful-proposed is working. ** Tags removed: verification-needed-artful ** Tags added: verification-done-artful -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1742316 Title: DVB Card with SAA7146 chipset not working Status in linux package in Ubuntu: Fix Released Status in linux source package in Artful: Fix Committed Bug description: === SRU Justification === [Impact] Callers vmalloc_32() expect the page is not located in highmem. All users of vmalloc_32() have this issue, module saa7146 is one of them. [Test] saa7146 crashes at probing. The issue is fixed with the patch. [Fix] Add GFP_DMA32 to GFP_VMALLOC32 flag for 32bits systems. The patch is in stable trees, so only Artful needs this patch. [Regression Potential] Low. It's a crucial fix for 32bits systems. === Original Bug Report === After upgrading to 17.10 (from 16.04 with 4.4 kernel) my PCI DVB card Terratec Cinergy DVB-1200 with SAA7146 chipset is not working anymore. There is a kernel bug message while booting and no /dev/dvb device is created. Tried also with newest mainline 4.14 kernel - same error. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-25-generic 4.13.0-25.29 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.13.0-25-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.7 Architecture: i386 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Date: Wed Jan 10 00:42:24 2018 HibernationDevice: RESUME=UUID=342e30a6-d71f-47c0-b65a-5ba657a80456 InstallationDate: Installed on 2016-02-13 (696 days ago) InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release i386 (20151021) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 psbdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-25-generic root=UUID=97ea5186-d18d-4c06-a8b2-2dd1417477be ro splash quiet acpi=force video=LVDS-1:d vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-25-generic N/A linux-backports-modules-4.13.0-25-generic N/A linux-firmware 1.169.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to artful on 2016-07-07 (551 days ago) dmi.bios.date: 04/19/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.60 dmi.board.name: AD2700-ITX dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.60:bd04/19/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAD2700-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742316/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1753662] Re: [i40e] LACP bonding start up race conditions
I built the next test kernel, up to the following commit: ea094f3c830a67f252677aacba5d04ebcf55c4d9 The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1753662 Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results. Thanks in advance -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1753662 Title: [i40e] LACP bonding start up race conditions Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: When provisioning Ubuntu servers with MAAS at once, some bonding pairs will have unexpected LACP status such as "Expired". It randomly happens at each provisioning with the default xenial kernel(4.4), but not reproducible with HWE kernel(4.13). I'm using Intel X710 cards (Dell-branded). Using the HWE kernel works as a workaround for short term, but it's not ideal since 4.13 is not covered by Canonical Livepatch service. How to reproduce: 1. configure LACP bonding with MAAS 2. provision machines 3. check the bonding status in /proc/net/bonding/bond* frequency of occurrence: About 5 bond pairs in 22 pairs at each provisioning. [reproducible combination] $ uname -a Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 1.4.25-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes [non-reproducible combination] $ uname -a Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 2.1.14-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-116-generic 4.4.0-116.140 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 6 06:37 seq crw-rw 1 root audio 116, 33 Mar 6 06:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.15 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 Mar 6 06:46:32 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R730 PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.5 dmi.board.name: 072T6D dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.asset.tag: 0018880 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R730 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1661876] Re: [Asus UX360UA] battery status in unity-panel is not changing when battery is being charged
I'm using kernel 4.15.10 in Ubuntu 16.04 but didn't see any change. Is it maybe the previous configurations I have or not this kernel the one with the fix? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1661876 Title: [Asus UX360UA] battery status in unity-panel is not changing when battery is being charged Status in linux package in Ubuntu: Fix Released Status in linux source package in Artful: Fix Committed Bug description: === SRU Justification === [Impact] Some Asus laptops report "discharging" when the battery is full and AC is plugged [Test] Charge battery to full, the issue appears. Users report with the patch the behaviour is correct. [Fix] The discharge rate is 0 on those machines. Use that to detect the wrong status report. [Regression Potential] Low. The quirk uses strict DMI to match affected systems. === Original Bug Report === I've just installed Ubuntu 16.04.1 in dualboot on top of an Asus UX360UA, alongside with Windows 10. I've already installed the updates meanwhile. When I start charging my computer the battery icon on the unity-panel is not changing (it stays in the 98% complete). This is strange because this is a fresh installation so I didn't change any configuration yet. Also, when I tried this ubuntu in the live pen, I noticed that the icon changed when I started charging the laptop. That's why I think it is a bug. --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tjiagom1806 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0eaf9255-c29a-41b7-8449-1eb52f637933 InstallationDate: Installed on 2017-02-04 (0 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 04f2:b56b Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX360UA Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic.efi.signed root=UUID=6ca1f963-632a-401d-80db-610ef37f1f26 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40 RelatedPackageVersions: linux-restricted-modules-4.4.0-62-generic N/A linux-backports-modules-4.4.0-62-generic N/A linux-firmware1.157.6 Tags: xenial Uname: Linux 4.4.0-62-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/17/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX360UA.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX360UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX360UA.300:bd06/17/2016:svnASUSTeKCOMPUTERINC.:pnUX360UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX360UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX360UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1661876/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1753662] Re: [i40e] LACP bonding start up race conditions
ff5a20169b98d84ad8d7f99f27c5ebbb008204d6 looks bad. [xenial configs] v4.12-rc3 #201803161156 - relatively bad (36 of 249 - 14.5%) v4.12.0-041200rc3 #201803191316 relatively bad (21 of 150 - 14.0%) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1753662 Title: [i40e] LACP bonding start up race conditions Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: When provisioning Ubuntu servers with MAAS at once, some bonding pairs will have unexpected LACP status such as "Expired". It randomly happens at each provisioning with the default xenial kernel(4.4), but not reproducible with HWE kernel(4.13). I'm using Intel X710 cards (Dell-branded). Using the HWE kernel works as a workaround for short term, but it's not ideal since 4.13 is not covered by Canonical Livepatch service. How to reproduce: 1. configure LACP bonding with MAAS 2. provision machines 3. check the bonding status in /proc/net/bonding/bond* frequency of occurrence: About 5 bond pairs in 22 pairs at each provisioning. [reproducible combination] $ uname -a Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 1.4.25-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes [non-reproducible combination] $ uname -a Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 2.1.14-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-116-generic 4.4.0-116.140 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 6 06:37 seq crw-rw 1 root audio 116, 33 Mar 6 06:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.15 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 Mar 6 06:46:32 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R730 PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.5 dmi.board.name: 072T6D dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.asset.tag: 0018880 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R730 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1753662] Re: [i40e] LACP bonding start up race conditions
ff5a20169b98d84ad8d7f99f27c5ebbb008204d6 looks bad. [xenial configs] v4.12-rc3 #201803161156 - relatively bad (36 of 249 - 14.5%) v4.12.0-041200rc3 #201803191316 relatively bad (21 of 150 - 14.0%) ff5a20169b98d84ad8d7f99f27c5ebbb008204d6 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1753662 Title: [i40e] LACP bonding start up race conditions Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: When provisioning Ubuntu servers with MAAS at once, some bonding pairs will have unexpected LACP status such as "Expired". It randomly happens at each provisioning with the default xenial kernel(4.4), but not reproducible with HWE kernel(4.13). I'm using Intel X710 cards (Dell-branded). Using the HWE kernel works as a workaround for short term, but it's not ideal since 4.13 is not covered by Canonical Livepatch service. How to reproduce: 1. configure LACP bonding with MAAS 2. provision machines 3. check the bonding status in /proc/net/bonding/bond* frequency of occurrence: About 5 bond pairs in 22 pairs at each provisioning. [reproducible combination] $ uname -a Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 1.4.25-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes [non-reproducible combination] $ uname -a Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 2.1.14-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-116-generic 4.4.0-116.140 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 6 06:37 seq crw-rw 1 root audio 116, 33 Mar 6 06:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.15 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 Mar 6 06:46:32 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R730 PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.5 dmi.board.name: 072T6D dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.asset.tag: 0018880 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R730 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1757012] Re: Upgrade ZFS to v0.7.7
v0.7.7 is out with many bugfixes. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1757012 Title: Upgrade ZFS to v0.7.7 Status in zfs-linux package in Ubuntu: New Bug description: v0.7.7 is out: https://github.com/zfsonlinux/zfs/releases/tag/zfs-0.7.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1757012/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1757012] [NEW] Upgrade ZFS to v0.7.7
Public bug reported: v0.7.7 is out: https://github.com/zfsonlinux/zfs/releases/tag/zfs-0.7.7 ** Affects: zfs-linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1757012 Title: Upgrade ZFS to v0.7.7 Status in zfs-linux package in Ubuntu: New Bug description: v0.7.7 is out: https://github.com/zfsonlinux/zfs/releases/tag/zfs-0.7.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1757012/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1757008] Re: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.2: bcmwl kernel module failed to build
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1757008 Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.2: bcmwl kernel module failed to build Status in bcmwl package in Ubuntu: New Bug description: The module fails to build, as it is missing the necessary patches for the latest HWE kernel. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.2 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 DKMSKernelVersion: 4.15.0-13-generic Date: Mon Mar 19 15:02:46 2018 DuplicateSignature: dkms:bcmwl-kernel-source:6.30.223.271+bdcom-0ubuntu1~1.2:/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:2359:2: error: implicit declaration of function ‘init_timer’ [-Werror=implicit-function-declaration] InstallationDate: Installed on 2017-06-05 (287 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageVersion: 6.30.223.271+bdcom-0ubuntu1~1.2 RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.2: bcmwl kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1757008/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1757008] [NEW] bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.2: bcmwl kernel module failed to build
Public bug reported: The module fails to build, as it is missing the necessary patches for the latest HWE kernel. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.2 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 DKMSKernelVersion: 4.15.0-13-generic Date: Mon Mar 19 15:02:46 2018 DuplicateSignature: dkms:bcmwl-kernel-source:6.30.223.271+bdcom-0ubuntu1~1.2:/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:2359:2: error: implicit declaration of function ‘init_timer’ [-Werror=implicit-function-declaration] InstallationDate: Installed on 2017-06-05 (287 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageVersion: 6.30.223.271+bdcom-0ubuntu1~1.2 RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.2: bcmwl kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: bcmwl (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1757008 Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.2: bcmwl kernel module failed to build Status in bcmwl package in Ubuntu: New Bug description: The module fails to build, as it is missing the necessary patches for the latest HWE kernel. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.2 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 DKMSKernelVersion: 4.15.0-13-generic Date: Mon Mar 19 15:02:46 2018 DuplicateSignature: dkms:bcmwl-kernel-source:6.30.223.271+bdcom-0ubuntu1~1.2:/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:2359:2: error: implicit declaration of function ‘init_timer’ [-Werror=implicit-function-declaration] InstallationDate: Installed on 2017-06-05 (287 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageVersion: 6.30.223.271+bdcom-0ubuntu1~1.2 RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.2: bcmwl kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1757008/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1754076] Re: i2c-thunderx: erroneous error message "unhandled state: 0"
artful verification: dannf@alekhin:~$ cat /proc/version Linux version 4.13.0-38-generic (buildd@bos02-arm64-005) (gcc version 5.4.0 20160609 (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.9)) #43~16.04.1-Ubuntu SMP Wed Mar 14 17:49:43 UTC 2018 dannf@alekhin:~$ dmesg | grep i2c [7.330023] i2c /dev entries driver [ 15.653953] i2c-thunderx :01:09.2: Probed. Set system clock to 8 [ 15.653968] i2c-thunderx :01:09.2: SMBUS alert not active on this bus [ 15.693445] ipmi_ssif: Trying SMBIOS-specified SSIF interface at i2c address 0x10, adapter Cavium ThunderX i2c adapter at :01:09.4, slave address 0x20 [ 16.061478] i2c-thunderx :01:09.4: Probed. Set system clock to 8 [ 16.061486] i2c-thunderx :01:09.4: SMBUS alert not active on this bus xenial verification: dannf@alekhin:~$ cat /proc/version Linux version 4.4.0-117-generic (buildd@bos02-arm64-028) (gcc version 5.4.0 20160609 (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.9) ) #141-Ubuntu SMP Tue Mar 13 11:59:25 UTC 2018 dannf@alekhin:~$ dmesg | grep i2c [6.357620] i2c /dev entries driver [ 13.428865] i2c-thunderx :01:09.2: Probed. Set system clock to 8 [ 13.428880] i2c-thunderx :01:09.2: SMBUS alert not active on this bus [ 13.430986] i2c-thunderx :01:09.4: Probed. Set system clock to 8 [ 13.430992] i2c-thunderx :01:09.4: SMBUS alert not active on this bus [ 47.044130] ipmi_ssif: Trying SMBIOS-specified SSIF interface at i2c address 0x10, adapter Cavium ThunderX i2c adapter at :01:09.4, slave address 0x0 ** Tags removed: verification-needed-artful verification-needed-xenial ** Tags added: verification-done-artful verification-done-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/1754076 Title: i2c-thunderx: erroneous error message "unhandled state: 0" Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Artful: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: [Impact] A misleading error is occasionally emitted by the kernel. [Test Case] Boot a ThunderX system and watch for the error: i2c-thunderx :01:09.4: unhandled state: 0 [Regression Risk] Driver is specific to a platform, and the only functional change is skipping the emission of an error message. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1754076/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1748710] Re: Linux 4.4.0-113.136 (i386/x86_32): failed to boot when 'kaslr' option is in use.
** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Changed in: linux (Ubuntu Xenial) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1748710 Title: Linux 4.4.0-113.136 (i386/x86_32): failed to boot when 'kaslr' option is in use. Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Incomplete Bug description: Hello. On Thu Feb 8, Linux kernel for Ubuntu 16.04.3 LTS has been updated to the 4.4.0-113.136 version (xenial-proposed). However, after reboot, plymouth freezes during start, and keys on an USB keyboard were in- active. After several seconds, the BusyBox shell screen appeared. It looks this way: ,-- | BusyBox v1.22.1 (Ubuntu 1:1.22.0-15ubuntu1) built-in shell (ash) | Enter 'help' for a list of built-in commands. | | (initramfs) _ `-- Unfortunately, the USB keyboard does not work and does not respond. The only way to solve this issue is a "hard reset" and in GRUB menu choosing an earlier kernel, which is linux 4.4.0-112.135. Now, everything works okay. Proposed update to the Linux 4.4.0-113.136 contains many new updates (please see 1.) It's an i386/x86_32 architecture, which does not contain PTI yet, right? I'm asking, because mentioned -proposed updates contains a couple of PTI-related patches and bugs in PTI can cause a few different signatures of crashes etc. For example: → Crashes in early boot, especially around CPU bringup. Bugs in the trampoline code or mappings cause these. → Userspace segfaults early in boot, sometimes manifesting as mount(8) failing to mount the rootfs. These have tended to be TLB invalidation issues. Usually invalidating the wrong PCID, or otherwise missing an invalidation. NOTE: if it's about PCID, which is mentioned in a second point, there is one patch in -proposed update: "x86/mm/32: Move setup_clear_cpu_cap(X86_FEATURE_PCID) earlier". Maybe that's is the cause of a boot failure? There are no errors in log files, such as '/var/log/syslog' or '/var/log/kern.log'. However, it's a Celeron, "E" series. So, I don't know if mentioned patches are good for this type of processor etc.? Especially on i386/x86_32 architecture. ● UPDATE/WARNING: It seems, that 'kaslr' option is responsible for this issue. After booting the latest v4.4.0-115.139 kernel, I've had the same problems as described above. However, after removing 'kaslr' option from a command line via GRUB menu, system started normally etc. The latest, working kernel with 'kaslr' option is v4.4.0-112.135. According to all of this I think, that 'kaslr' is not compatible with some "Spectre & Meltdown" mitigation patches and fixes etc. ✗ Release ('/proc/version_signature'): Ubuntu 4.4.0-112.135-generic 4.4.98 ✗ Architecture: i386/x86_32 ✗ PCI ('lspci -vnvn'): 00:0a.0 PCI bridge [0604]: NVIDIA Corporation MCP73 PCI Express bridge [10de:056d] (rev a1) (prog-if 01 [Subtractive decode]) Capabilities: [b8] Subsystem: Gigabyte Technology Co., Ltd MCP73 PCI Express bridge [1458:026f] Thanks, regards. 1. https://lists.ubuntu.com/archives/xenial- changes/2018-February/020108.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748710/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1745938] Re: System Freezes while starting VM in virtualbox after Kernrel Upgrade 4.13.0-31.34
Would it be possible for you to test the proposed kernel and post back if it resolves this bug? See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1745938 Title: System Freezes while starting VM in virtualbox after Kernrel Upgrade 4.13.0-31.34 Status in linux package in Ubuntu: Incomplete Bug description: On Ubuntu 16.04.3 , I upgraded Kernel 4.13.0-31.34 , which includes specter and meltdown fixes. After Upgrade when I was going to start VM in virtualbox System is getting freezes. Reboot required to resume system. I faced 4 times. I rollback to kernel 4.10.0-42. Now I am able to start vm perfectly. Please look into this kernel issue. --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ketankumar.patel 2098 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=2a3a4447-c93a-46fc-96e9-56023bb774f8 InstallationDate: Installed on 2017-09-11 (139 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. MachineType: LENOVO 20FL000FMS Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-42-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17 RelatedPackageVersions: linux-restricted-modules-4.10.0-42-generic N/A linux-backports-modules-4.10.0-42-generic N/A linux-firmware 1.157.14 Tags: xenial Uname: Linux 4.10.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: docker WifiSyslog: _MarkForUpload: True dmi.bios.date: 02/10/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1KET30W (1.17 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FL000FMS dmi.board.vendor: LENOVO dmi.board.version: 0B98417 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1KET30W(1.17):bd02/10/2017:svnLENOVO:pn20FL000FMS:pvrThinkPadP50s:rvnLENOVO:rn20FL000FMS:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20FL000FMS dmi.product.version: ThinkPad P50s dmi.sys.vendor: LENOVO --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kk 1403 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=fadbc245-ccb0-42f5-82ff-b5d99ccdb2fe InstallationDate: Installed on 2018-01-31 (0 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IwConfig: lono wireless extensions. enp0s3no wireless extensions. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: linux (not installed) ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic root=UUID=fafc16a4-e3f4-42a7-84d9-99ec94651ad2 ro quiet splash ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-32-generic N/A linux-backports-modules-4.13.0-32-generic N/A linux-firmware 1.157.15 RfKill: Tags: xenial Uname: Linux 4.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745938/+subscriptions -- Mailing list: http
[Kernel-packages] [Bug 1748936] Re: kASLR: unable to boot Linux v4.4.0-113.136 - v4.4.0-115.139 kernels; i386/x86_32 ("Spectre & Meltdown")
** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1748936 Title: kASLR: unable to boot Linux v4.4.0-113.136 - v4.4.0-115.139 kernels; i386/x86_32 ("Spectre & Meltdown") Status in linux package in Ubuntu: Incomplete Bug description: Hello. It seems, that 'kaslr' option is responsible for issues with system booting. The latest working kernel is v4.4.0-112.135. Every next release: v4.4.0-113.136 and v4.4.0-115.139 are unable to boot if 'kaslr' option is in use etc. Everything is described in my previous bug report (please see 1.), but I've decided to create a new one, because it seems, that some of the "Spectre & Meltdown" patches are not compatible with kASLR and are responsible for this regressions. Thanks, best regards. [1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748710 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748936/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1745007] Re: Support cppc-cpufreq driver on ThunderX2 systems
Verified: ubuntu@starbuck:~$ cat /proc/version Linux version 4.13.0-38-generic (buildd@bos02-arm64-005) (gcc version 5.4.0 20160609 (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.9)) #43~16.04.1-Ubuntu SMP Wed Mar 14 17:49:43 UTC 2018 ubuntu@starbuck:~$ lsmod | grep cppc cppc_cpufreq 16384 0 ** Tags removed: verification-needed-artful ** Tags added: verification-done-artful -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1745007 Title: Support cppc-cpufreq driver on ThunderX2 systems Status in linux package in Ubuntu: Fix Committed Status in linux source package in Artful: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: [Impact] The cppc-cpufreq driver fails to initialize on ThunderX2 systems, which is used to communicate power configuration to firmware. [Test Case] sudo modprobe cppc-cpufreq || echo "Fail" [Regression Risk] The fix consists of clean cherry-picks from upstream that are restricted to a single driver. Regressions would therefore be restricted to platforms that support ACPI CPPC power management. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745007/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1755499] Re: zfs returns enosys when calling fsetxattr
..and HAVE_XATTR_SYSCALLS is not defined because it does not have arch specific #defines for arm64. I'll add them in tomorrow and fix this up. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1755499 Title: zfs returns enosys when calling fsetxattr Status in linux package in Ubuntu: In Progress Status in stress-ng package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Status in stress-ng source package in Bionic: Invalid Bug description: When xfstests are run on zfs, they expect acl calls (like fsetxattr) to either work or return ENOTSUP. zfs fails with ENOSYS, at least on arm64. The result on calling the immutable tests of xfstests are: acl: Function not implemented To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1755499/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1755499] Re: zfs returns enosys when calling fsetxattr
Looks like the wrapper in xfstests-bld/attr/libattr/syscalls.c returns the dreaded ENOSYS becuase XATTR_SYSCALLS is not defined. Silent and deadly. #if HAVE_XATTR_SYSCALLS # define SYSCALL(args...) syscall(args) #else # define SYSCALL(args...) ( errno = ENOSYS, -1 ) #endif -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1755499 Title: zfs returns enosys when calling fsetxattr Status in linux package in Ubuntu: In Progress Status in stress-ng package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Status in stress-ng source package in Bionic: Invalid Bug description: When xfstests are run on zfs, they expect acl calls (like fsetxattr) to either work or return ENOTSUP. zfs fails with ENOSYS, at least on arm64. The result on calling the immutable tests of xfstests are: acl: Function not implemented To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1755499/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1735420] Re: Avoid creation of /dev/kvm in Xenial KVM virtual machines on s390x
Since we don't know the commit that would solve this off hand, we can perform a "Reverse" bisect to identify that commit. Can you see if the following kernel has the bug: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.8/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1735420 Title: Avoid creation of /dev/kvm in Xenial KVM virtual machines on s390x Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: Since nested virtualization with KVM is not supported on s390x, please disable this in Xenial - in case it's doable with reasonable effort. (I think it was already disabled for later Ubuntu releases ... was also discussed on IRC) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1735420/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1746340] Re: Samsung SSD corruption (fsck needed)
I do it a lot. However the errors don't happen right afetr waking from suspend. They take some time. Before the NVME quirk I tried to see if suspend/resume influenced in the error. I experienced botting the PC and leaving it open until the error ocurred, proving the suspend wasn't causing it. However now with the NVME quirk the computer takes a lot of time to show the error, so I always en dup closing it. However I think there was one time the error happened right after turning the PC on, though I'm not 100% sure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 4.13.0-21.24-generic 4.13.13 I have a Razer Blade Stealth 2016. The first Ubuntu I installed was Ubuntu 17.04, which gave me this error after 2 weeks of usage. After that, I installed 16.04 and used it for MONTHS without any problems, until it produced the same error this week. I think it has to do with the ubuntu updates, because I did one recently and one today, just before this problem. Could be a coincidence though. I notice the error when I try to save something on disk and it says me that the disk is in read-only mode: lz@lz:/var/log$ touch something touch: cannot touch 'something': Read-only file system lz@lz:/var/log$ cat syslog Jan 29 01:07:39 lz kernel: [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 lz@lz:/var/log$ dmesg [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.377374] Aborting journal on device nvme0n1p2-8. [62984.379343] EXT4-fs (nvme0n1p2): Remounting filesystem read-only [62984.379516] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.381486] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.383484] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.385469] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.387278] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.389262] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.391252] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.393341] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [63285.618078] audit: type=1400 audit(1517195560.393:63): apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=22495 comm="cupsd" capability=12 capname="net_admin" Rebooting the ubuntu will give me a black terminal where I can run fsck /dev/nvm30n1p2 (something like that) and it fill fix a lot of orphaned inodes. The majority of time it boots back to the Ubuntu working good, but some times it boots to a broken ubuntu (no images, lots of things broken). I have to reinstall ubuntu then. Every time I reinstall my Ubuntu, I have to try lots of times until it installs without an Input/Output error. When it installs, I can use it for some hours without having the problem, but if I run the software updates, it ALWAYS crashes and enters in read-only mode, specifically in the part that is installing kernel updates. I noticed that Ubuntu installs updates automatically when they're for security reasons. Could this be the reason my Ubuntu worked for months without the problem, but then an update was applied and it broke? I thought that this bug was happening: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 and tried different nvme_core.default_ps_max_latency_us= combinations, all them gave errors. I just changed to 0 and I had no error while using ubuntu (however I didn't test for a long time) but I still had the error after trying to update my ubuntu. My Samsung 512gb SSD is: SAMSUNG MZVLW512HMJP-0, FW REV: CXY7501Q on a Razer Blade Stealth. I also asked this on ask ubuntu, without success: https://askubuntu.com/questions/998471/razer-blade-stealth-disk- corruption-fsck-needed-probably-samsung-ssd-bug-afte Please help me, as I need this computer to work on lots of things :c --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID AC
[Kernel-packages] [Bug 1756998] Re: GPU HANG: ecode 9:0:0x84dfbffc, in Xorg [1250], reason: Hang on rcs0, action: reset drm/i915: Resetting chip after gpu hang RC6 on
** Attachment added: "lspci-vvnn.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1756998/+attachment/5084481/+files/lspci-vvnn.log ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux (Ubuntu) ** Also affects: libdrm (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/1756998 Title: GPU HANG: ecode 9:0:0x84dfbffc, in Xorg [1250], reason: Hang on rcs0, action: reset drm/i915: Resetting chip after gpu hang RC6 on Status in libdrm package in Ubuntu: New Status in mesa package in Ubuntu: New Bug description: This error message is in syslog when the Desktop freeze before the Display goes black and the login screen came up. This apparently happens without any apparent connection. Sometimes not for days even though the CPU is 100% full all the time, then again after 20-30 minutes several times in a row. lsb_release -rd Description: Ubuntu 16.04.4 LTS Release: 16.04 mesa 17.2.8-0ubuntu0~16.04.1 libdrm 2.4.83-1~16.04.1 Mar 19 20:12:22 michael-ThinkPad-E470 kernel: [255789.072708] [drm] GPU HANG: ecode 9:0:0x84dfbffc, in Xorg [1250], reason: Hang on rcs0, action: reset Mar 19 20:12:22 michael-ThinkPad-E470 kernel: [255789.072763] drm/i915: Resetting chip after gpu hang Mar 19 20:12:22 michael-ThinkPad-E470 kernel: [255789.073059] [drm] RC6 on Mar 19 20:12:30 michael-ThinkPad-E470 kernel: [255797.047275] drm/i915: Resetting chip after gpu hang Mar 19 20:12:30 michael-ThinkPad-E470 kernel: [255797.047556] [drm] RC6 on Mar 19 20:12:43 michael-ThinkPad-E470 kernel: [255810.039289] drm/i915: Resetting chip after gpu hang Mar 19 20:12:43 michael-ThinkPad-E470 kernel: [255810.039429] [drm] RC6 on Mar 19 20:12:55 michael-ThinkPad-E470 kernel: [255822.007247] drm/i915: Resetting chip after gpu hang Mar 19 20:12:55 michael-ThinkPad-E470 kernel: [255822.007407] [drm] RC6 on Mar 19 20:13:03 michael-ThinkPad-E470 kernel: [255830.071164] drm/i915: Resetting chip after gpu hang Mar 19 20:13:03 michael-ThinkPad-E470 kernel: [255830.071304] [drm] RC6 on Mar 19 20:13:25 michael-ThinkPad-E470 gnome-session-binary[31279]: Entering running state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1756998/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1744754] Re: qemu-efi-aarch64 in >= artful can't boot xenial cloud images
** Attachment added: "dmesg-bionic-host.txt" https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/1744754/+attachment/5084479/+files/dmesg-bionic-host.txt ** Tags removed: verification-needed-xenial ** Tags added: verification-done-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/1744754 Title: qemu-efi-aarch64 in >= artful can't boot xenial cloud images Status in cloud-images: Invalid Status in edk2 package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Released Status in edk2 source package in Xenial: Invalid Status in linux source package in Xenial: Fix Committed Bug description: [Impact] After upgrading an Ubuntu/arm64 KVM host past xenial, your xenial-based guests will fail to boot. [Test Case] Boot a xenial cloud image with qemu-efi-aarch64 from artful/bionic. [Regression Risk] I've tested booting a xenial cloud image in bionic (ACPI mode), and regression tested w/ xenial's qemu-efi (DTB mode). I've regression tested on a Cavium ThunderX CRB1S, Caviumt ThunderX CRB2S and an APM X-Gene 2 Merlin board. Patches 1-5 change only code in the GICv3 driver. The xenial GA kernel only supported 2 GICv3 systems - the 1 socket and 2 socket variants of the Cavium ThunderX CRB - and I've regression tested on those systems. Patch 6 only adds new macro definitions. Patch 7 is restricted to devicetree code, except for a change to earlycon.c:param_setup_earlycon(). In the case that 'earlycon' is passed on the cmdline (vs. earlycon=something), this function used to return 0 - but now it will return -ENODEV on non-devicetree systems, which is a subtle API change. However, according to kernel- parameters.txt (and the code itself), 'earlycon' by itself is only valid on devicetree systems. Just to be sure, I booted an x86 system up w/ 'earlycon' with and without this series, and observed no difference. Patch 8 adds the SPCR table parser, but no caller to it yet. It also modifies the same earlycon code as Patch 7 - here it avoids earlycon init in the case that the devicetree-specific 'earlycon' was passed. As mentioned in my analysis Patch 7, this codepath is only supported for devicetree systems, and has been regression tested on x86. Patch 9 turns on CONFIG_ACPI_SPCR_TABLE - however, this driver will only be built for arm64. TBH, I'm not 100% sure how Kconfig knows not to build this for other archs - but I checked the logs, and there's no spcr.o built on other archs. (Not that that should be a problem - they would just grow a bit of unused code). Patch 10 only touches arm64-specific code, adding the call to parse_spcr(), so risk is limited to arm64. Patch 11 adds a new match method to the ARM-specific pl011 console driver, so regression risk to other architectures is negligible. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1744754/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1744754] Re: qemu-efi-aarch64 in >= artful can't boot xenial cloud images
After updating to the proposed kernel, I was able to boot a xenial cloud image with qemu-efi from both xenial (DTB mode) and bionic (ACPI mode). ** Attachment added: "dmesg-xenial-host.txt" https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/1744754/+attachment/5084478/+files/dmesg-xenial-host.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1744754 Title: qemu-efi-aarch64 in >= artful can't boot xenial cloud images Status in cloud-images: Invalid Status in edk2 package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Released Status in edk2 source package in Xenial: Invalid Status in linux source package in Xenial: Fix Committed Bug description: [Impact] After upgrading an Ubuntu/arm64 KVM host past xenial, your xenial-based guests will fail to boot. [Test Case] Boot a xenial cloud image with qemu-efi-aarch64 from artful/bionic. [Regression Risk] I've tested booting a xenial cloud image in bionic (ACPI mode), and regression tested w/ xenial's qemu-efi (DTB mode). I've regression tested on a Cavium ThunderX CRB1S, Caviumt ThunderX CRB2S and an APM X-Gene 2 Merlin board. Patches 1-5 change only code in the GICv3 driver. The xenial GA kernel only supported 2 GICv3 systems - the 1 socket and 2 socket variants of the Cavium ThunderX CRB - and I've regression tested on those systems. Patch 6 only adds new macro definitions. Patch 7 is restricted to devicetree code, except for a change to earlycon.c:param_setup_earlycon(). In the case that 'earlycon' is passed on the cmdline (vs. earlycon=something), this function used to return 0 - but now it will return -ENODEV on non-devicetree systems, which is a subtle API change. However, according to kernel- parameters.txt (and the code itself), 'earlycon' by itself is only valid on devicetree systems. Just to be sure, I booted an x86 system up w/ 'earlycon' with and without this series, and observed no difference. Patch 8 adds the SPCR table parser, but no caller to it yet. It also modifies the same earlycon code as Patch 7 - here it avoids earlycon init in the case that the devicetree-specific 'earlycon' was passed. As mentioned in my analysis Patch 7, this codepath is only supported for devicetree systems, and has been regression tested on x86. Patch 9 turns on CONFIG_ACPI_SPCR_TABLE - however, this driver will only be built for arm64. TBH, I'm not 100% sure how Kconfig knows not to build this for other archs - but I checked the logs, and there's no spcr.o built on other archs. (Not that that should be a problem - they would just grow a bit of unused code). Patch 10 only touches arm64-specific code, adding the call to parse_spcr(), so risk is limited to arm64. Patch 11 adds a new match method to the ARM-specific pl011 console driver, so regression risk to other architectures is negligible. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1744754/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1756998] Re: GPU HANG: ecode 9:0:0x84dfbffc, in Xorg [1250], reason: Hang on rcs0, action: reset drm/i915: Resetting chip after gpu hang RC6 on
** Attachment added: "uname-a.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1756998/+attachment/5084477/+files/uname-a.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1756998 Title: GPU HANG: ecode 9:0:0x84dfbffc, in Xorg [1250], reason: Hang on rcs0, action: reset drm/i915: Resetting chip after gpu hang RC6 on Status in libdrm package in Ubuntu: New Status in mesa package in Ubuntu: New Bug description: This error message is in syslog when the Desktop freeze before the Display goes black and the login screen came up. This apparently happens without any apparent connection. Sometimes not for days even though the CPU is 100% full all the time, then again after 20-30 minutes several times in a row. lsb_release -rd Description: Ubuntu 16.04.4 LTS Release: 16.04 mesa 17.2.8-0ubuntu0~16.04.1 libdrm 2.4.83-1~16.04.1 Mar 19 20:12:22 michael-ThinkPad-E470 kernel: [255789.072708] [drm] GPU HANG: ecode 9:0:0x84dfbffc, in Xorg [1250], reason: Hang on rcs0, action: reset Mar 19 20:12:22 michael-ThinkPad-E470 kernel: [255789.072763] drm/i915: Resetting chip after gpu hang Mar 19 20:12:22 michael-ThinkPad-E470 kernel: [255789.073059] [drm] RC6 on Mar 19 20:12:30 michael-ThinkPad-E470 kernel: [255797.047275] drm/i915: Resetting chip after gpu hang Mar 19 20:12:30 michael-ThinkPad-E470 kernel: [255797.047556] [drm] RC6 on Mar 19 20:12:43 michael-ThinkPad-E470 kernel: [255810.039289] drm/i915: Resetting chip after gpu hang Mar 19 20:12:43 michael-ThinkPad-E470 kernel: [255810.039429] [drm] RC6 on Mar 19 20:12:55 michael-ThinkPad-E470 kernel: [255822.007247] drm/i915: Resetting chip after gpu hang Mar 19 20:12:55 michael-ThinkPad-E470 kernel: [255822.007407] [drm] RC6 on Mar 19 20:13:03 michael-ThinkPad-E470 kernel: [255830.071164] drm/i915: Resetting chip after gpu hang Mar 19 20:13:03 michael-ThinkPad-E470 kernel: [255830.071304] [drm] RC6 on Mar 19 20:13:25 michael-ThinkPad-E470 gnome-session-binary[31279]: Entering running state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1756998/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1756998] Re: GPU HANG: ecode 9:0:0x84dfbffc, in Xorg [1250], reason: Hang on rcs0, action: reset drm/i915: Resetting chip after gpu hang RC6 on
** Attachment added: "dmesg.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1756998/+attachment/5084480/+files/dmesg.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1756998 Title: GPU HANG: ecode 9:0:0x84dfbffc, in Xorg [1250], reason: Hang on rcs0, action: reset drm/i915: Resetting chip after gpu hang RC6 on Status in libdrm package in Ubuntu: New Status in mesa package in Ubuntu: New Bug description: This error message is in syslog when the Desktop freeze before the Display goes black and the login screen came up. This apparently happens without any apparent connection. Sometimes not for days even though the CPU is 100% full all the time, then again after 20-30 minutes several times in a row. lsb_release -rd Description: Ubuntu 16.04.4 LTS Release: 16.04 mesa 17.2.8-0ubuntu0~16.04.1 libdrm 2.4.83-1~16.04.1 Mar 19 20:12:22 michael-ThinkPad-E470 kernel: [255789.072708] [drm] GPU HANG: ecode 9:0:0x84dfbffc, in Xorg [1250], reason: Hang on rcs0, action: reset Mar 19 20:12:22 michael-ThinkPad-E470 kernel: [255789.072763] drm/i915: Resetting chip after gpu hang Mar 19 20:12:22 michael-ThinkPad-E470 kernel: [255789.073059] [drm] RC6 on Mar 19 20:12:30 michael-ThinkPad-E470 kernel: [255797.047275] drm/i915: Resetting chip after gpu hang Mar 19 20:12:30 michael-ThinkPad-E470 kernel: [255797.047556] [drm] RC6 on Mar 19 20:12:43 michael-ThinkPad-E470 kernel: [255810.039289] drm/i915: Resetting chip after gpu hang Mar 19 20:12:43 michael-ThinkPad-E470 kernel: [255810.039429] [drm] RC6 on Mar 19 20:12:55 michael-ThinkPad-E470 kernel: [255822.007247] drm/i915: Resetting chip after gpu hang Mar 19 20:12:55 michael-ThinkPad-E470 kernel: [255822.007407] [drm] RC6 on Mar 19 20:13:03 michael-ThinkPad-E470 kernel: [255830.071164] drm/i915: Resetting chip after gpu hang Mar 19 20:13:03 michael-ThinkPad-E470 kernel: [255830.071304] [drm] RC6 on Mar 19 20:13:25 michael-ThinkPad-E470 gnome-session-binary[31279]: Entering running state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1756998/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1756998] Re: GPU HANG: ecode 9:0:0x84dfbffc, in Xorg [1250], reason: Hang on rcs0, action: reset drm/i915: Resetting chip after gpu hang RC6 on
** Attachment added: "lspci-vv.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1756998/+attachment/5084464/+files/lspci-vv.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1756998 Title: GPU HANG: ecode 9:0:0x84dfbffc, in Xorg [1250], reason: Hang on rcs0, action: reset drm/i915: Resetting chip after gpu hang RC6 on Status in libdrm package in Ubuntu: New Status in mesa package in Ubuntu: New Bug description: This error message is in syslog when the Desktop freeze before the Display goes black and the login screen came up. This apparently happens without any apparent connection. Sometimes not for days even though the CPU is 100% full all the time, then again after 20-30 minutes several times in a row. lsb_release -rd Description: Ubuntu 16.04.4 LTS Release: 16.04 mesa 17.2.8-0ubuntu0~16.04.1 libdrm 2.4.83-1~16.04.1 Mar 19 20:12:22 michael-ThinkPad-E470 kernel: [255789.072708] [drm] GPU HANG: ecode 9:0:0x84dfbffc, in Xorg [1250], reason: Hang on rcs0, action: reset Mar 19 20:12:22 michael-ThinkPad-E470 kernel: [255789.072763] drm/i915: Resetting chip after gpu hang Mar 19 20:12:22 michael-ThinkPad-E470 kernel: [255789.073059] [drm] RC6 on Mar 19 20:12:30 michael-ThinkPad-E470 kernel: [255797.047275] drm/i915: Resetting chip after gpu hang Mar 19 20:12:30 michael-ThinkPad-E470 kernel: [255797.047556] [drm] RC6 on Mar 19 20:12:43 michael-ThinkPad-E470 kernel: [255810.039289] drm/i915: Resetting chip after gpu hang Mar 19 20:12:43 michael-ThinkPad-E470 kernel: [255810.039429] [drm] RC6 on Mar 19 20:12:55 michael-ThinkPad-E470 kernel: [255822.007247] drm/i915: Resetting chip after gpu hang Mar 19 20:12:55 michael-ThinkPad-E470 kernel: [255822.007407] [drm] RC6 on Mar 19 20:13:03 michael-ThinkPad-E470 kernel: [255830.071164] drm/i915: Resetting chip after gpu hang Mar 19 20:13:03 michael-ThinkPad-E470 kernel: [255830.071304] [drm] RC6 on Mar 19 20:13:25 michael-ThinkPad-E470 gnome-session-binary[31279]: Entering running state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1756998/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1756998] Re: GPU HANG: ecode 9:0:0x84dfbffc, in Xorg [1250], reason: Hang on rcs0, action: reset drm/i915: Resetting chip after gpu hang RC6 on
** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1756998/+attachment/5084463/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1756998 Title: GPU HANG: ecode 9:0:0x84dfbffc, in Xorg [1250], reason: Hang on rcs0, action: reset drm/i915: Resetting chip after gpu hang RC6 on Status in libdrm package in Ubuntu: New Status in mesa package in Ubuntu: New Bug description: This error message is in syslog when the Desktop freeze before the Display goes black and the login screen came up. This apparently happens without any apparent connection. Sometimes not for days even though the CPU is 100% full all the time, then again after 20-30 minutes several times in a row. lsb_release -rd Description: Ubuntu 16.04.4 LTS Release: 16.04 mesa 17.2.8-0ubuntu0~16.04.1 libdrm 2.4.83-1~16.04.1 Mar 19 20:12:22 michael-ThinkPad-E470 kernel: [255789.072708] [drm] GPU HANG: ecode 9:0:0x84dfbffc, in Xorg [1250], reason: Hang on rcs0, action: reset Mar 19 20:12:22 michael-ThinkPad-E470 kernel: [255789.072763] drm/i915: Resetting chip after gpu hang Mar 19 20:12:22 michael-ThinkPad-E470 kernel: [255789.073059] [drm] RC6 on Mar 19 20:12:30 michael-ThinkPad-E470 kernel: [255797.047275] drm/i915: Resetting chip after gpu hang Mar 19 20:12:30 michael-ThinkPad-E470 kernel: [255797.047556] [drm] RC6 on Mar 19 20:12:43 michael-ThinkPad-E470 kernel: [255810.039289] drm/i915: Resetting chip after gpu hang Mar 19 20:12:43 michael-ThinkPad-E470 kernel: [255810.039429] [drm] RC6 on Mar 19 20:12:55 michael-ThinkPad-E470 kernel: [255822.007247] drm/i915: Resetting chip after gpu hang Mar 19 20:12:55 michael-ThinkPad-E470 kernel: [255822.007407] [drm] RC6 on Mar 19 20:13:03 michael-ThinkPad-E470 kernel: [255830.071164] drm/i915: Resetting chip after gpu hang Mar 19 20:13:03 michael-ThinkPad-E470 kernel: [255830.071304] [drm] RC6 on Mar 19 20:13:25 michael-ThinkPad-E470 gnome-session-binary[31279]: Entering running state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1756998/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1756998] Re: GPU HANG: ecode 9:0:0x84dfbffc, in Xorg [1250], reason: Hang on rcs0, action: reset drm/i915: Resetting chip after gpu hang RC6 on
** Attachment added: "lspci-vvn.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1756998/+attachment/5084465/+files/lspci-vvn.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1756998 Title: GPU HANG: ecode 9:0:0x84dfbffc, in Xorg [1250], reason: Hang on rcs0, action: reset drm/i915: Resetting chip after gpu hang RC6 on Status in libdrm package in Ubuntu: New Status in mesa package in Ubuntu: New Bug description: This error message is in syslog when the Desktop freeze before the Display goes black and the login screen came up. This apparently happens without any apparent connection. Sometimes not for days even though the CPU is 100% full all the time, then again after 20-30 minutes several times in a row. lsb_release -rd Description: Ubuntu 16.04.4 LTS Release: 16.04 mesa 17.2.8-0ubuntu0~16.04.1 libdrm 2.4.83-1~16.04.1 Mar 19 20:12:22 michael-ThinkPad-E470 kernel: [255789.072708] [drm] GPU HANG: ecode 9:0:0x84dfbffc, in Xorg [1250], reason: Hang on rcs0, action: reset Mar 19 20:12:22 michael-ThinkPad-E470 kernel: [255789.072763] drm/i915: Resetting chip after gpu hang Mar 19 20:12:22 michael-ThinkPad-E470 kernel: [255789.073059] [drm] RC6 on Mar 19 20:12:30 michael-ThinkPad-E470 kernel: [255797.047275] drm/i915: Resetting chip after gpu hang Mar 19 20:12:30 michael-ThinkPad-E470 kernel: [255797.047556] [drm] RC6 on Mar 19 20:12:43 michael-ThinkPad-E470 kernel: [255810.039289] drm/i915: Resetting chip after gpu hang Mar 19 20:12:43 michael-ThinkPad-E470 kernel: [255810.039429] [drm] RC6 on Mar 19 20:12:55 michael-ThinkPad-E470 kernel: [255822.007247] drm/i915: Resetting chip after gpu hang Mar 19 20:12:55 michael-ThinkPad-E470 kernel: [255822.007407] [drm] RC6 on Mar 19 20:13:03 michael-ThinkPad-E470 kernel: [255830.071164] drm/i915: Resetting chip after gpu hang Mar 19 20:13:03 michael-ThinkPad-E470 kernel: [255830.071304] [drm] RC6 on Mar 19 20:13:25 michael-ThinkPad-E470 gnome-session-binary[31279]: Entering running state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1756998/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1756998] [NEW] GPU HANG: ecode 9:0:0x84dfbffc, in Xorg [1250], reason: Hang on rcs0, action: reset drm/i915: Resetting chip after gpu hang RC6 on
Public bug reported: This error message is in syslog when the Desktop freeze before the Display goes black and the login screen came up. This apparently happens without any apparent connection. Sometimes not for days even though the CPU is 100% full all the time, then again after 20-30 minutes several times in a row. lsb_release -rd Description:Ubuntu 16.04.4 LTS Release:16.04 mesa 17.2.8-0ubuntu0~16.04.1 libdrm 2.4.83-1~16.04.1 Mar 19 20:12:22 michael-ThinkPad-E470 kernel: [255789.072708] [drm] GPU HANG: ecode 9:0:0x84dfbffc, in Xorg [1250], reason: Hang on rcs0, action: reset Mar 19 20:12:22 michael-ThinkPad-E470 kernel: [255789.072763] drm/i915: Resetting chip after gpu hang Mar 19 20:12:22 michael-ThinkPad-E470 kernel: [255789.073059] [drm] RC6 on Mar 19 20:12:30 michael-ThinkPad-E470 kernel: [255797.047275] drm/i915: Resetting chip after gpu hang Mar 19 20:12:30 michael-ThinkPad-E470 kernel: [255797.047556] [drm] RC6 on Mar 19 20:12:43 michael-ThinkPad-E470 kernel: [255810.039289] drm/i915: Resetting chip after gpu hang Mar 19 20:12:43 michael-ThinkPad-E470 kernel: [255810.039429] [drm] RC6 on Mar 19 20:12:55 michael-ThinkPad-E470 kernel: [255822.007247] drm/i915: Resetting chip after gpu hang Mar 19 20:12:55 michael-ThinkPad-E470 kernel: [255822.007407] [drm] RC6 on Mar 19 20:13:03 michael-ThinkPad-E470 kernel: [255830.071164] drm/i915: Resetting chip after gpu hang Mar 19 20:13:03 michael-ThinkPad-E470 kernel: [255830.071304] [drm] RC6 on Mar 19 20:13:25 michael-ThinkPad-E470 gnome-session-binary[31279]: Entering running state ** Affects: libdrm (Ubuntu) Importance: Undecided Status: New ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Attachment added: "version.log" https://bugs.launchpad.net/bugs/1756998/+attachment/5084462/+files/version.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1756998 Title: GPU HANG: ecode 9:0:0x84dfbffc, in Xorg [1250], reason: Hang on rcs0, action: reset drm/i915: Resetting chip after gpu hang RC6 on Status in libdrm package in Ubuntu: New Status in mesa package in Ubuntu: New Bug description: This error message is in syslog when the Desktop freeze before the Display goes black and the login screen came up. This apparently happens without any apparent connection. Sometimes not for days even though the CPU is 100% full all the time, then again after 20-30 minutes several times in a row. lsb_release -rd Description: Ubuntu 16.04.4 LTS Release: 16.04 mesa 17.2.8-0ubuntu0~16.04.1 libdrm 2.4.83-1~16.04.1 Mar 19 20:12:22 michael-ThinkPad-E470 kernel: [255789.072708] [drm] GPU HANG: ecode 9:0:0x84dfbffc, in Xorg [1250], reason: Hang on rcs0, action: reset Mar 19 20:12:22 michael-ThinkPad-E470 kernel: [255789.072763] drm/i915: Resetting chip after gpu hang Mar 19 20:12:22 michael-ThinkPad-E470 kernel: [255789.073059] [drm] RC6 on Mar 19 20:12:30 michael-ThinkPad-E470 kernel: [255797.047275] drm/i915: Resetting chip after gpu hang Mar 19 20:12:30 michael-ThinkPad-E470 kernel: [255797.047556] [drm] RC6 on Mar 19 20:12:43 michael-ThinkPad-E470 kernel: [255810.039289] drm/i915: Resetting chip after gpu hang Mar 19 20:12:43 michael-ThinkPad-E470 kernel: [255810.039429] [drm] RC6 on Mar 19 20:12:55 michael-ThinkPad-E470 kernel: [255822.007247] drm/i915: Resetting chip after gpu hang Mar 19 20:12:55 michael-ThinkPad-E470 kernel: [255822.007407] [drm] RC6 on Mar 19 20:13:03 michael-ThinkPad-E470 kernel: [255830.071164] drm/i915: Resetting chip after gpu hang Mar 19 20:13:03 michael-ThinkPad-E470 kernel: [255830.071304] [drm] RC6 on Mar 19 20:13:25 michael-ThinkPad-E470 gnome-session-binary[31279]: Entering running state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1756998/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1755499] Re: zfs returns enosys when calling fsetxattr
debugged further into fadd_acl, this calls acl_set_fd libacl/acl_set_fd.c:47, and this calls: fsetxattr (filedes=filedes@entry=3, name=name@entry=0xaaab6958 "system.posix_acl_access", value=value@entry=0xaaacbc00, size=, flags=flags@entry=0) ..which returns -1 and errno = 38 (ENOSYS 38 Function not implemented) this also occurs on a non-ZFS file system (e.g. ext4). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1755499 Title: zfs returns enosys when calling fsetxattr Status in linux package in Ubuntu: In Progress Status in stress-ng package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Status in stress-ng source package in Bionic: Invalid Bug description: When xfstests are run on zfs, they expect acl calls (like fsetxattr) to either work or return ENOTSUP. zfs fails with ENOSYS, at least on arm64. The result on calling the immutable tests of xfstests are: acl: Function not implemented To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1755499/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1752002] Re: [P9, POwer NV][WSP][DD2.1][Ubuntu 1804][Perf fuzzer] : Call trace is seen while running perf fuzzer (perf:)
Has the patch been accepted upstream? If so, do you happen to have the SHA1 or patch subject? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1752002 Title: [P9,POwer NV][WSP][DD2.1][Ubuntu 1804][Perf fuzzer] : Call trace is seen while running perf fuzzer (perf:) Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: == Comment: #0 - Shriya R. Kulkarni - 2018-02-02 01:21:36 == Problem Description : = Warn on message is seen while running perf fuzzer tests. Machine details : == Hardware : Witherspoon (wsp12) + DD2.1 OS : Ubuntu 1804 uname -a : 4.13.0-32-generic #35~lp1746225 ( Kernel from the bug : https://bugzilla.linux.ibm.com/show_bug.cgi?id=164107#c7 ) Steps to reproduce : Build Kernel : To avoid the kernel crash due to Perf fuzzer , use the kernel mentioned in the link : https://bugzilla.linux.ibm.com/show_bug.cgi?id=164107#c7 #! /bin/bash set -x git clone https://github.com/deater/perf_event_tests.git cd perf_event_tests/include mkdir asm cd asm wget http://9.114.13.132/repo/shriya/perf_regs.h cd ../../lib make sleep 10 cd ../fuzzer make sleep 10 echo 0 > /proc/sys/kernel/nmi_watchdog echo 2 > /proc/sys/kernel/perf_event_paranoid echo 10 > /proc/sys/kernel/perf_event_max_sample_rate ./perf_fuzzer -r 1492143527 Call trace : === [ 329.228031] [ cut here ] [ 329.228039] WARNING: CPU: 43 PID: 9088 at /home/jsalisbury/bugs/lp1746225/ubuntu-artful/kernel/events/core.c:3038 perf_pmu_sched_task+0x170/0x180 [ 329.228040] Modules linked in: ofpart at24 uio_pdrv_genirq uio cmdlinepart powernv_flash mtd ipmi_powernv vmx_crypto ipmi_devintf ipmi_msghandler ibmpowernv opal_prd crct10dif_vpmsum sch_fq_codel ip_tables x_tables autofs4 crc32c_vpmsum lpfc ast i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt mlx5_core fb_sys_fops ttm tg3 nvmet_fc drm ahci nvmet nvme_fc libahci nvme_fabrics mlxfw nvme_core devlink scsi_transport_fc [ 329.228068] CPU: 43 PID: 9088 Comm: perf_fuzzer Not tainted 4.13.0-32-generic #35~lp1746225 [ 329.228070] task: c03f776ac900 task.stack: c03f77728000 [ 329.228071] NIP: c0299b70 LR: c02a4534 CTR: c029bb80 [ 329.228073] REGS: c03f7772b760 TRAP: 0700 Not tainted (4.13.0-32-generic) [ 329.228073] MSR: 9282b033 [ 329.228079] CR: 24008822 XER: [ 329.228080] CFAR: c0299a70 SOFTE: 0 GPR00: c02a4534 c03f7772b9e0 c1606200 c03fef858908 GPR04: c03f776ac900 0001 003fee73 GPR08: c11220d8 0002 GPR12: c029bb80 c7a3d900 GPR16: GPR20: c03f776ad090 c0c71354 GPR24: c03fef716780 003fee73 c03fe69d4200 c03f776ad330 GPR28: c11220d8 0001 c14c6108 c03fef858900 [ 329.228098] NIP [c0299b70] perf_pmu_sched_task+0x170/0x180 [ 329.228100] LR [c02a4534] __perf_event_task_sched_in+0xc4/0x230 [ 329.228101] Call Trace: [ 329.228102] [c03f7772b9e0] [c02a0678] perf_iterate_sb+0x158/0x2a0 (unreliable) [ 329.228105] [c03f7772ba30] [c02a4534] __perf_event_task_sched_in+0xc4/0x230 [ 329.228107] [c03f7772bab0] [c01396dc] finish_task_switch+0x21c/0x310 [ 329.228109] [c03f7772bb60] [c0c71354] __schedule+0x304/0xb80 [ 329.228111] [c03f7772bc40] [c0c71c10] schedule+0x40/0xc0 [ 329.228113] [c03f7772bc60] [c01033f4] do_wait+0x254/0x2e0 [ 329.228115] [c03f7772bcd0] [c0104ac0] kernel_wait4+0xa0/0x1a0 [ 329.228117] [c03f7772bd70] [c0104c24] SyS_wait4+0x64/0xc0 [ 329.228121] [c03f7772be30] [c000b184] system_call+0x58/0x6c [ 329.228121] Instruction dump: [ 329.228123] 3beafea0 7faa4800 409eff18 e8010060 eb610028 ebc10040 7c0803a6 38210050 [ 329.228127] eb81ffe0 eba1ffe8 ebe1fff8 4e800020 <0fe0> 4bbc 6000 6042 [ 329.228131] ---[ end trace 8c46856d314c1811 ]--- [ 375.755943] hrtimer: interrupt took 31601 ns == Comment: #4 - SEETEENA THOUFEEK - 2018-02-05 06:34:09 == == Comment: #5 - SEETEENA THOUFEEK - 2018-02-05 06:36:12 == We have similar issue reported on different distro where Anju Provided the patch. Patch attached above. . Will che
[Kernel-packages] [Bug 1737873] Re: [Feature][GLK] Enable L2 CDP (Code and Data Prioritization)
** Information type changed from Proprietary to Public ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => Triaged ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1737873 Title: [Feature][GLK] Enable L2 CDP (Code and Data Prioritization) Status in intel: New Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: Description: L2 CDP separates code and data in L2 cache allocation. First implemented in Gemini Lake processor. It's an extension of L2 CAT and similar to already released L3 CDP. The L2 CDP is supposed to be published in Dec SDM. Target Kernel: 4.16 Target Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1737873/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1755499] Re: zfs returns enosys when calling fsetxattr
#0 __GI___libc_write (fd=4, buf=0xaaacbc40, nbytes=30) at ../sysdeps/unix/sysv/linux/write.c:25 #1 0xb7ebf878 in _IO_new_file_write (f=0xaaac9850, data=0xaaacbc40, n=30) at fileops.c:1255 #2 0xb7ebec28 in new_do_write (fp=0xaaac9850, data=0xaaacbc40 "acl: Function not implemented\n", to_do=to_do@entry=30) at fileops.c:510 #3 0xb7ec0994 in _IO_new_do_write (fp=, data=, to_do=30) at fileops.c:486 #4 0xb7ebff6c in _IO_new_file_xsputn (f=0xaaac9850, data=, n=1) at fileops.c:1323 #5 0xb7e97064 in _IO_vfprintf_internal (s=0xaaac9850, format=0xb7f76008 "%s%s%s\n", ap=...) at vfprintf.c:1674 #6 0xb7eb2180 in locked_vfxprintf (fp=fp@entry=0xaaac9850, fmt=, ap=...) at fxprintf.c:30 #7 0xb7eb22e0 in __fxprintf (fp=fp@entry=0xaaac9850, fmt=fmt@entry=0xb7f76008 "%s%s%s\n") at fxprintf.c:74 #8 0xb7eaf588 in perror_internal (fp=fp@entry=0xaaac9850, s=s@entry=0xaaab64d0 "acl", errnum=errnum@entry=38) at perror.c:39 #9 0xb7eaf65c in __GI_perror (s=0xaaab64d0 "acl") at perror.c:74 #10 0xaaab256c in create_test_area (dir=0xf886 "foo") at t_immutable.c:2008 #11 0xba88 in main (argc=3, argv=0xf638) at t_immutable.c:2277 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1755499 Title: zfs returns enosys when calling fsetxattr Status in linux package in Ubuntu: In Progress Status in stress-ng package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Status in stress-ng source package in Bionic: Invalid Bug description: When xfstests are run on zfs, they expect acl calls (like fsetxattr) to either work or return ENOTSUP. zfs fails with ENOSYS, at least on arm64. The result on calling the immutable tests of xfstests are: acl: Function not implemented To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1755499/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1755499] Re: zfs returns enosys when calling fsetxattr
Looking at the termination of t_immutable test program: ARM: mprotect(0x86092000, 4096, PROT_READ) = 0 mprotect(0x860b3000, 4096, PROT_READ) = 0 munmap(0x86295000, 38279) = 0 openat(AT_FDCWD, "/etc/passwd", O_RDONLY|O_CLOEXEC) = 4 lseek(4, 0, SEEK_CUR) = 0 fstat(4, {st_mode=S_IFREG|0644, st_size=1682, ...}) = 0 mmap(NULL, 1682, PROT_READ, MAP_SHARED, 4, 0) = 0x8629e000 lseek(4, 1682, SEEK_SET)= 1682 munmap(0x8629e000, 1682)= 0 close(4)= 0 dup(2) = 4 fcntl(4, F_GETFL) = 0x20002 (flags O_RDWR|0x2) fstat(4, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 0), ...}) = 0 write(4, "acl: Function not implemented\n", 30acl: Function not implemented ) = 30 close(4)= 0 exit_group(1) = ? +++ exited with 1 +++ x86 at same place: mprotect(0x7f677e46f000, 4096, PROT_READ) = 0 mprotect(0x7f677e67d000, 4096, PROT_READ) = 0 munmap(0x7f677f097000, 165753) = 0 openat(AT_FDCWD, "/etc/passwd", O_RDONLY|O_CLOEXEC) = 4 lseek(4, 0, SEEK_CUR) = 0 fstat(4, {st_mode=S_IFREG|0644, st_size=3023, ...}) = 0 mmap(NULL, 3023, PROT_READ, MAP_SHARED, 4, 0) = 0x7f677f0bf000 lseek(4, 3023, SEEK_SET)= 3023 munmap(0x7f677f0bf000, 3023)= 0 close(4)= 0 fsetxattr(3, "system.posix_acl_access", "\2\0\0\0\1\0\6\0\377\377\377\377\2\0\6\0\376\377\0\0\4\0\6\0\377\377\377\377\20\0\6", 44, 0) = -1 EOPNOTSUPP (Operation not supported) fsetxattr(3, "trusted.test", "readonly", 8, XATTR_CREATE) = 0 fsetxattr(3, "user.test", "readonly", 8, XATTR_CREATE) = 0 ..etc So it's something different in the test program in the acl handling side -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1755499 Title: zfs returns enosys when calling fsetxattr Status in linux package in Ubuntu: In Progress Status in stress-ng package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Status in stress-ng source package in Bionic: Invalid Bug description: When xfstests are run on zfs, they expect acl calls (like fsetxattr) to either work or return ENOTSUP. zfs fails with ENOSYS, at least on arm64. The result on calling the immutable tests of xfstests are: acl: Function not implemented To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1755499/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1746418] Re: System freezes when starting Xorg after installing linux-image-4.13.0-32-generic
Would it be possible for you to test the proposed kernel and post back if it resolves this bug? See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1746418 Title: System freezes when starting Xorg after installing linux- image-4.13.0-32-generic Status in linux package in Ubuntu: In Progress Status in linux source package in Artful: In Progress Bug description: My laptop (Lenovo T440) freezes when starting Xorg (lightdm) only after installing the latest ubuntu kernel for 17.10, linux- image-4.13.0-32-generic. Am running Xorg instead of MIR due to MIR crashing when I initially upgraded from 17.04 to 17.10, but that's a different problem for a different day. It's been running with Xorg stably for at least 2-3 months. If I boot with the previous kernel version on my /boot (linux- image-4.13.0-25-generic), everything works fine. If I boot with the latest mainline kernel from the Ubuntu mainline repo (4.15.0), everything works. Using grub's option to run "Recovery Mode" for the 4.13.0-32 kernel, I am able to use the CLI and access the encrypted root filesystem, which is how I generated the apport repo that's attached. It's only when telling it to continue Normal booting that it freezes, which is why I suspect the problem of being Xorg. When the system freezes, the fan starts to spin up. I cannot switch virtual consoles using CTRL-ALT-F{1-7}. CTRL-ALT-DEL pressed repeatedly doesn't do anything. To reboot, I have to hold the power button until the system powers off. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746418/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1745349] Re: Hard lockup during boot with linux-image-4.4.0-112-generic
Would it be possible for you to test the proposed kernel and post back if it resolves this bug? See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1745349 Title: Hard lockup during boot with linux-image-4.4.0-112-generic Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: Systems on ASUS H110M-C Boards don't boot here with Kernel 4.4.0-112 instead they show NMI watchdog: Watchdog detected hard lockup on cpu 0 NMI watchdog: Watchdog detected hard lockup on cpu 1 NMI watchdog: Watchdog detected hard lockup on cpu 3 NMI watchdog: Watchdog detected hard lockup on cpu 2 I cannot provide any logs of course. Booting with 4.4.0-109 works. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-112-generic 4.4.0-112.135 ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98 Uname: Linux 4.4.0-109-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lr3200 2013 F pulseaudio Date: Thu Jan 25 11:38:55 2018 HibernationDevice: RESUME=UUID=8e35131d-6d40-4f4f-a3db-c7336e72cbce IwConfig: lono wireless extensions. enp5s0no wireless extensions. enp3s0no wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-109-generic root=UUID=4dc5bb0a-ab7c-48fa-ac23-bcdf23755d93 ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-109-generic N/A linux-backports-modules-4.4.0-109-generic N/A linux-firmware 1.157.15 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/12/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3601 dmi.board.asset.tag: Default string dmi.board.name: H110M-C dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3601:bd12/12/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-C:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745349/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 504038] Re: Cannot activate STA Broadcom Driver
i'm on ubuntu 16.04 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/504038 Title: Cannot activate STA Broadcom Driver Status in bcmwl package in Ubuntu: Invalid Bug description: Binary package hint: bcmwl-kernel-source I installed STA Broadcom Driver for Broadcom BCM4312 wireless card from the Ubuntu 9.10 installation CD. After installing it, I go to Administration>Hardware Drivers to activate the driver. I click "activate", type my password and then click "authenticate", but nothing happens. It still says "This driver is not activated" at the bottom of the window. ProblemType: Package Architecture: i386 Date: Wed Jan 6 23:16:38 2010 DistroRelease: Ubuntu 9.10 ErrorMessage: bcmwl kernel module failed to build InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5) LiveMediaBuild: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5) Package: bcmwl-kernel-source 5.10.91.9+bdcom-0ubuntu4 PackageVersion: N/A ProcVersionSignature: Ubuntu 2.6.31-14.48-generic SourcePackage: bcmwl Title: package bcmwl-kernel-source 5.10.91.9+bdcom-0ubuntu4 failed to install/upgrade: bcmwl kernel module failed to build Uname: Linux 2.6.31-14-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/504038/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1756978] Re: Bionic update to 4.15.11 stable release
** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1756978 Title: Bionic update to 4.15.11 stable release Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The 4.15.11 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the 4.15.11 stable release shall be applied: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1756978/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1755499] Re: zfs returns enosys when calling fsetxattr
arm64: statfs("/mnt/scratch/079", {f_type=ZFS_SUPER_MAGIC, f_bsize=131072, f_blocks=15097, f_bfree=15097, f_bavail=15097, f_files=3864945, f_ffree=3864939, f_fsid={val=[2326582274, 8984039]}, f_namelen=255, f_frsize=131072, f_flags=ST_VALID|ST_RELATIME}) = 0 openat(AT_FDCWD, "/mnt/scratch/079/immutable.f", O_RDWR) = -1 EACCES (Permission denied) openat(AT_FDCWD, "/mnt/scratch/079/immutable.f", O_WRONLY) = -1 EACCES (Permission denied) openat(AT_FDCWD, "/mnt/scratch/079/immutable.f", O_RDWR|O_TRUNC) = -1 EACCES (Permission denied) openat(AT_FDCWD, "/mnt/scratch/079/immutable.f", O_WRONLY|O_TRUNC) = -1 EACCES (Permission denied) openat(AT_FDCWD, "/mnt/scratch/079/immutable.f", O_RDWR|O_APPEND) = -1 EACCES (Permission denied) openat(AT_FDCWD, "/mnt/scratch/079/immutable.f", O_WRONLY|O_APPEND) = -1 EACCES (Permission denied) openat(AT_FDCWD, "/mnt/scratch/079/immutable.f", O_RDWR|O_TRUNC|O_APPEND) = -1 EACCES (Permission denied) openat(AT_FDCWD, "/mnt/scratch/079/immutable.f", O_WRONLY|O_TRUNC|O_APPEND) = -1 EACCES (Permission denied) truncate("/mnt/scratch/079/immutable.f", 0) = -1 EACCES (Permission denied) utimensat(AT_FDCWD, "/mnt/scratch/079/immutable.f", [{tv_sec=0, tv_nsec=0}, {tv_sec=0, tv_nsec=0}], 0) = -1 EPERM (Operation not permitted) utimensat(AT_FDCWD, "/mnt/scratch/079/immutable.f", NULL, 0) = -1 EPERM (Operation not permitted) x86: statfs("/mnt/scratch/079", {f_type=ZFS_SUPER_MAGIC, f_bsize=131072, f_blocks=15102, f_bfree=15102, f_bavail=15102, f_files=3866273, f_ffree=3866267, f_fsid={val=[4130572324, 1396799]}, f_namelen=255, f_frsize=131072, f_flags=ST_VALID|ST_RELATIME}) = 0 openat(AT_FDCWD, "/mnt/scratch/079/immutable.f", O_RDWR) = -1 EPERM (Operation not permitted) openat(AT_FDCWD, "/mnt/scratch/079/immutable.f", O_WRONLY) = -1 EPERM (Operation not permitted) openat(AT_FDCWD, "/mnt/scratch/079/immutable.f", O_RDWR|O_TRUNC) = -1 EPERM (Operation not permitted) openat(AT_FDCWD, "/mnt/scratch/079/immutable.f", O_WRONLY|O_TRUNC) = -1 EPERM (Operation not permitted) openat(AT_FDCWD, "/mnt/scratch/079/immutable.f", O_RDWR|O_APPEND) = -1 EPERM (Operation not permitted) openat(AT_FDCWD, "/mnt/scratch/079/immutable.f", O_WRONLY|O_APPEND) = -1 EPERM (Operation not permitted) openat(AT_FDCWD, "/mnt/scratch/079/immutable.f", O_RDWR|O_TRUNC|O_APPEND) = -1 EPERM (Operation not permitted) openat(AT_FDCWD, "/mnt/scratch/079/immutable.f", O_WRONLY|O_TRUNC|O_APPEND) = -1 EPERM (Operation not permitted) truncate("/mnt/scratch/079/immutable.f", 0) = -1 EPERM (Operation not permitted) utime("/mnt/scratch/079/immutable.f", {actime=0, modtime=0}) = -1 EPERM (Operation not permitted) utime("/mnt/scratch/079/immutable.f", NULL) = -1 EPERM (Operation not permitted) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1755499 Title: zfs returns enosys when calling fsetxattr Status in linux package in Ubuntu: In Progress Status in stress-ng package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Status in stress-ng source package in Bionic: Invalid Bug description: When xfstests are run on zfs, they expect acl calls (like fsetxattr) to either work or return ENOTSUP. zfs fails with ENOSYS, at least on arm64. The result on calling the immutable tests of xfstests are: acl: Function not implemented To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1755499/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1729145] Re: /dev/bcache/by-uuid links not created after reboot
Xenial verified. root@ubuntu:~# lsb_release -rd Description:Ubuntu 16.04.4 LTS Release:16.04 root@ubuntu:~# uname -a Linux ubuntu 4.4.0-117-generic #141-Ubuntu SMP Tue Mar 13 11:58:07 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 4.4.0.117.123 Candidate: 4.4.0.117.123 Version table: *** 4.4.0.117.123 500 500 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 Packages 100 /var/lib/dpkg/status 4.4.0.116.122 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 4.4.0.21.22 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages root@ubuntu:~# ls -al /dev/bcache/* /dev/bcache/by-label: total 0 drwxr-xr-x 2 root root 120 Mar 19 19:07 . drwxr-xr-x 4 root root 80 Mar 19 19:07 .. lrwxrwxrwx 1 root root 13 Mar 19 19:07 backing-sdb -> ../../bcache0 lrwxrwxrwx 1 root root 13 Mar 19 19:07 backing-sdd -> ../../bcache3 lrwxrwxrwx 1 root root 13 Mar 19 19:07 backing-sde -> ../../bcache2 lrwxrwxrwx 1 root root 13 Mar 19 19:07 backing-sdf -> ../../bcache1 /dev/bcache/by-uuid: total 0 drwxr-xr-x 2 root root 120 Mar 19 19:07 . drwxr-xr-x 4 root root 80 Mar 19 19:07 .. lrwxrwxrwx 1 root root 13 Mar 19 19:07 1f531b44-437f-49cc-b7db-16db6d699c41 -> ../../bcache1 lrwxrwxrwx 1 root root 13 Mar 19 19:07 31474eb7-687d-4bb7-8c6b-b4efd472e860 -> ../../bcache0 lrwxrwxrwx 1 root root 13 Mar 19 19:07 3653ce1f-b6aa-43ad-9a91-506530db2d50 -> ../../bcache3 lrwxrwxrwx 1 root root 13 Mar 19 19:07 94041d44-4bb2-4e4d-8641-21d4ae410595 -> ../../bcache2 root@ubuntu:~# ls -al /dev/bcache/by-label/backing-sdb lrwxrwxrwx 1 root root 13 Mar 19 19:07 /dev/bcache/by-label/backing-sdb -> ../../bcache0 root@ubuntu:~# ls -al /sys/class/block/bcache0/slaves total 0 drwxr-xr-x 2 root root 0 Mar 19 19:08 . drwxr-xr-x 8 root root 0 Mar 19 19:07 .. lrwxrwxrwx 1 root root 0 Mar 19 19:08 sda -> ../../../../pci:00/:00:04.0/virtio1/host2/target2:0:0/2:0:0:0/block/sda lrwxrwxrwx 1 root root 0 Mar 19 19:08 sdb -> ../../../../pci:00/:00:04.0/virtio1/host2/target2:0:1/2:0:1:0/block/sdb root@ubuntu:~# ls -al /dev/bcache/by-label/backing-sdd lrwxrwxrwx 1 root root 13 Mar 19 19:07 /dev/bcache/by-label/backing-sdd -> ../../bcache3 root@ubuntu:~# ls -al /sys/class/block/bcache3/slaves total 0 drwxr-xr-x 2 root root 0 Mar 19 19:09 . drwxr-xr-x 8 root root 0 Mar 19 19:07 .. lrwxrwxrwx 1 root root 0 Mar 19 19:09 sda -> ../../../../pci:00/:00:04.0/virtio1/host2/target2:0:0/2:0:0:0/block/sda lrwxrwxrwx 1 root root 0 Mar 19 19:09 sdd -> ../../../../pci:00/:00:04.0/virtio1/host2/target2:0:3/2:0:3:0/block/sdd root@ubuntu:~# ls -al /dev/bcache/by-label/backing-sde lrwxrwxrwx 1 root root 13 Mar 19 19:07 /dev/bcache/by-label/backing-sde -> ../../bcache2 root@ubuntu:~# ls -al /sys/class/block/bcache2/slaves total 0 drwxr-xr-x 2 root root 0 Mar 19 19:09 . drwxr-xr-x 8 root root 0 Mar 19 19:07 .. lrwxrwxrwx 1 root root 0 Mar 19 19:09 sdc -> ../../../../pci:00/:00:04.0/virtio1/host2/target2:0:2/2:0:2:0/block/sdc lrwxrwxrwx 1 root root 0 Mar 19 19:09 sde -> ../../../../pci:00/:00:04.0/virtio1/host2/target2:0:4/2:0:4:0/block/sde root@ubuntu:~# ls -al /dev/bcache/by-label/backing-sdf lrwxrwxrwx 1 root root 13 Mar 19 19:07 /dev/bcache/by-label/backing-sdf -> ../../bcache1 root@ubuntu:~# ls -al /sys/class/block/bcache1/slaves total 0 drwxr-xr-x 2 root root 0 Mar 19 19:09 . drwxr-xr-x 8 root root 0 Mar 19 19:07 .. lrwxrwxrwx 1 root root 0 Mar 19 19:09 sdc -> ../../../../pci:00/:00:04.0/virtio1/host2/target2:0:2/2:0:2:0/block/sdc lrwxrwxrwx 1 root root 0 Mar 19 19:09 sdf -> ../../../../pci:00/:00:04.0/virtio1/host2/target2:0:5/2:0:5:0/block/sdf root@ubuntu:~# dmesg | grep bcache [1.271827] bcache: register_bdev() registered backing device sdb [1.276685] bcache: register_bdev() registered backing device sdf [1.286218] bcache: bch_journal_replay() journal replay done, 0 keys in 2 entries, seq 13 [1.309504] bcache: bch_cached_dev_attach() Caching sdb as bcache0 on set 0dbdcc17-7af0-4318-bd57-bbdf5c7f1bfa [1.313789] bcache: register_cache() registered cache device sda [1.365415] bcache: bch_journal_replay() journal replay done, 0 keys in 2 entries, seq 13 [1.380090] bcache: bch_cached_dev_attach() Caching sdf as bcache1 on set d36b419d-a49d-42e2-95af-710138a20700 [1.382049] bcache: register_cache() registered cache device sdc [1.383332] bcache: register_bdev() registered backing device sde [1.391625] bcache: bch_cached_dev_attach() Caching sde as bcache2 on set d36b419d-a49d-42e2-95af-710138a20700 [1.395701] bcache: register_bdev() registered backing device sdd [1.405870] bcache: bch_cached_dev_attach() Caching sdd as bcache3 on set 0dbdcc17-7af0-4318-bd57-bbdf5c7f1bfa [4.533291] bcache:
[Kernel-packages] [Bug 1756978] [NEW] Bionic update to 4.15.11 stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The 4.15.11 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the 4.15.11 stable release shall be applied: ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: kernel-stable-tracking-bug ** Tags added: kernel-stable-tracking-bug -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1756978 Title: Bionic update to 4.15.11 stable release Status in linux package in Ubuntu: New Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The 4.15.11 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the 4.15.11 stable release shall be applied: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1756978/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1739665] Re: [Feature] KVM CLX avx512_vnni
** Also affects: qemu (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: qemu (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: xen (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => Confirmed ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: linux (Ubuntu Bionic) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1739665 Title: [Feature] KVM CLX avx512_vnni Status in linux package in Ubuntu: Fix Committed Status in qemu package in Ubuntu: New Status in xen package in Ubuntu: New Status in linux source package in Bionic: Fix Committed Status in qemu source package in Bionic: New Status in xen source package in Bionic: New Bug description: This feature has been released in ICX platform and the definition of AVX512_VNNI as below AVX512_VNNI Vector Nerual Network Instructions, an addition to AVX512. cpuid.(7,0). ECX[11] This is a new instruction to support machine learning. This instructions is pure HW features, currently, there is no test cases for this new instruction, we only check CPUID info by cpuid tool. Target Kernel: 4.16 Target Qemu: 2.12 Target Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1739665/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1730829] Re: [Feature]Crystal Ridge:add support for the platform capabilities NFIT sub-table in ACPI 6.2A
** Changed in: linux (Ubuntu Bionic) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1730829 Title: [Feature]Crystal Ridge:add support for the platform capabilities NFIT sub-table in ACPI 6.2A Status in intel: New Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: Description: Enable support for: "5.2.25.9 Platform Capabilities Structure" in ACPI 6.2A. This involves NFIT driver changes for the new table, and then detecting if the platform has cache flush on fail support. If it does, plumb that through as a region property so that we can pick the proper default to pass to the dax_write_cache() call in pmem_attach_disk(). Target Kernel: 4.15 Target Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1730829/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1756941] Re: linux-kvm: 4.15.0-1002.2 -proposed tracker
The package has been published and the bug is being set to Fix Released ** Changed in: kernel-sru-workflow Status: In Progress => Fix Released ** Description changed: This bug is for tracking the 4.15.0-1002.2 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-master-bug: 1751285 phase: Uploaded + kernel-phase-changed:Monday, 19. March 2018 17:49 UTC + kernel-phase:Released ** Description changed: This bug is for tracking the 4.15.0-1002.2 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-master-bug: 1751285 - phase: Uploaded - kernel-phase-changed:Monday, 19. March 2018 17:49 UTC - kernel-phase:Released + phase: Released ** Tags removed: kernel-release-tracking-bug-live -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1756941 Title: linux-kvm: 4.15.0-1002.2 -proposed tracker Status in Kernel SRU Workflow: Fix Released Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-release series: Fix Released Status in Kernel SRU Workflow regression-testing series: New Status in linux-kvm package in Ubuntu: Confirmed Status in linux-kvm source package in Bionic: Confirmed Bug description: This bug is for tracking the 4.15.0-1002.2 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-master-bug: 1751285 phase: Released To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1756941/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1756941] Re: linux-kvm: 4.15.0-1002.2 -proposed tracker
** Tags removed: block-proposed block-proposed-bionic ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/promote-to-release Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1756941 Title: linux-kvm: 4.15.0-1002.2 -proposed tracker Status in Kernel SRU Workflow: Fix Released Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-release series: Fix Released Status in Kernel SRU Workflow regression-testing series: New Status in linux-kvm package in Ubuntu: Confirmed Status in linux-kvm source package in Bionic: Confirmed Bug description: This bug is for tracking the 4.15.0-1002.2 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-master-bug: 1751285 phase: Released To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1756941/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1703742] Re: Transparent hugepages should default to enabled=madvise
I've been exercising the -proposed kernel all day on amd64 using stress- ng memory tests without any observed regressions. Benchmark comparisons between the current -proposed kernel and the previous xenial kernel show that: 1. stream test: stream test (stress-ng): stress-ng --stream 1 --stream-l3-size 1M -t 60 --metrics-brief -v a 1% to 7% improvement on bogo stream ops per second with stream memory sizes ranging from 1M through to 512M. 2. malloc test: a 13-30% improvement on bogo malloc/free allocations (indirectly using mmap/munmap) for memory sizes ranging from 1M through to 1024M I believe this vindicates the default enabling of THP using enabled=madvise ** Tags removed: verification-needed-xenial ** Tags added: verification-done-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/1703742 Title: Transparent hugepages should default to enabled=madvise Status in linux package in Ubuntu: Fix Released Status in linux-gke package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux-gke source package in Xenial: Fix Released Status in linux source package in Yakkety: Won't Fix Status in linux source package in Zesty: Won't Fix Status in linux source package in Artful: Fix Released Bug description: SRU Justification, Zesty, Xenial [Impact] Ubuntu kernels should default transparent_hugepages to enabled=madvise, not enabled=always (this corresponds to TRANSPARENT_HUGEPAGE_MADVISE=y in .config). I've blogged about this at some length here: https://blog.nelhage.com/post/transparent-hugepages/ but here is a summary: Transparent Hugepages are a feature that allows the kernel to attempt to automatically back any anonymous maps with "huge" 2MiB page tables, instead of the normal 4k entries. It can produce small net performance gains in certain benchmarks, but also has numerous downsides, in the form of apparent memory leaks and 30% slowdowns or worse for some applications. Many popular pieces of software now refuse to run with hugepages enabled because of known performance issues. Examples of problem reports: MongoDB: https://docs.mongodb.com/manual/tutorial/transparent-huge-pages/ Oracle: https://blogs.oracle.com/linux/entry/performance_issues_with_transparent_huge Splunk: https://docs.splunk.com/Documentation/Splunk/6.5.2/ReleaseNotes/SplunkandTHP Go runtime: https://github.com/golang/go/issues/8832 jemalloc: https://blog.digitalocean.com/transparent-huge-pages-and-alternative-memory-allocators/ node.js: https://github.com/nodejs/node/issues/11077 Setting `enabled=madvise` enables applications that know they benefit from transparent huge pages to opt-in to this feature, while eliminating all the problematic behavior for other applications. Note also that transparent hugepage settings don't affect the use of explicit hugepages via hugetlbfs or mmap(…, MAP_HUGETLB, …) [Fix] Enable CONFIG_TRANSPARENT_HUGEPAGE_MADVISE=y [Regression Potential] May marginally impact performance, but the benefits of madvise'd huge transparent hugepage over-weigh this considerably. This has been enabled in Artful since July (and in Bionic) and we've not seen any regression reports, so we are confident this has minimal impact. [Testcase] Kernel ADT tests and stress-ng memory tests should not show any regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1703742/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1756941] Re: linux-kvm: 4.15.0-1002.2 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-bionic ** Tags added: block-proposed ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Kamal Mostafa (kamalmostafa) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => Confirmed ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Kamal Mostafa (kamalmostafa) ** Description changed: This bug is for tracking the 4.15.0-1002.2 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-master-bug: 1751285 phase: Released + kernel-phase:Uploaded + kernel-phase-changed:Monday, 19. March 2018 18:04 UTC ** Description changed: This bug is for tracking the 4.15.0-1002.2 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-master-bug: 1751285 - phase: Released - kernel-phase:Uploaded - kernel-phase-changed:Monday, 19. March 2018 18:04 UTC + phase: Uploaded ** Changed in: kernel-sru-workflow Status: In Progress => Invalid ** Changed in: kernel-sru-workflow/automated-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => Invalid ** Changed in: kernel-sru-workflow/promote-to-release Status: New => Invalid ** Changed in: kernel-sru-workflow/regression-testing Status: New => Invalid ** Changed in: linux-kvm (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1756941 Title: linux-kvm: 4.15.0-1002.2 -proposed tracker Status in Kernel SRU Workflow: Invalid Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Invalid Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-release series: Invalid Status in Kernel SRU Workflow regression-testing series: Invalid Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Bionic: Invalid Bug description: This bug is for tracking the 4.15.0-1002.2 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-master-bug: 1751285 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1756941/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1620762] Re: Support AverMedia DVD EZMaker 7 USB video capture dongle
For why I should to try this kernel? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1620762 Title: Support AverMedia DVD EZMaker 7 USB video capture dongle Status in linux package in Ubuntu: Confirmed Bug description: Linux doesn't support this capture. Link to patch https://www.linuxtv.org/wiki/index.php/AVerMedia_DVD_EZMaker_7_(C039). I tested it on Ubuntu 16.04 - OK. It will be great if this patch is built-in to kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1620762/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1729145] Re: /dev/bcache/by-uuid links not created after reboot
Artful verified: ubuntu@ubuntu:~$ lsb_release -rd Description:Ubuntu 17.10 Release:17.10 ubuntu@ubuntu:~$ uname -a Linux ubuntu 4.13.0-38-generic #43-Ubuntu SMP Wed Mar 14 15:20:44 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux ubuntu@ubuntu:~$ apt-cache policy linux-image-virtual linux-image-virtual: Installed: 4.13.0.38.41 Candidate: 4.13.0.38.41 Version table: *** 4.13.0.38.41 500 500 http://archive.ubuntu.com/ubuntu artful-proposed/main amd64 Packages 100 /var/lib/dpkg/status 4.13.0.37.40 500 500 http://archive.ubuntu.com/ubuntu artful-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu artful-security/main amd64 Packages 4.13.0.16.17 500 500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages ubuntu@ubuntu:~$ ls -al /dev/bcache/by-* /dev/bcache/by-label: total 0 drwxr-xr-x 2 root root 120 Mar 19 18:32 . drwxr-xr-x 4 root root 80 Mar 19 18:32 .. lrwxrwxrwx 1 root root 13 Mar 19 18:32 backing-sdb -> ../../bcache1 lrwxrwxrwx 1 root root 13 Mar 19 18:32 backing-sdd -> ../../bcache0 lrwxrwxrwx 1 root root 13 Mar 19 18:32 backing-sde -> ../../bcache3 lrwxrwxrwx 1 root root 13 Mar 19 18:32 backing-sdf -> ../../bcache2 /dev/bcache/by-uuid: total 0 drwxr-xr-x 2 root root 120 Mar 19 18:32 . drwxr-xr-x 4 root root 80 Mar 19 18:32 .. lrwxrwxrwx 1 root root 13 Mar 19 18:32 1f531b44-437f-49cc-b7db-16db6d699c41 -> ../../bcache2 lrwxrwxrwx 1 root root 13 Mar 19 18:32 31474eb7-687d-4bb7-8c6b-b4efd472e860 -> ../../bcache1 lrwxrwxrwx 1 root root 13 Mar 19 18:32 3653ce1f-b6aa-43ad-9a91-506530db2d50 -> ../../bcache0 lrwxrwxrwx 1 root root 13 Mar 19 18:32 94041d44-4bb2-4e4d-8641-21d4ae410595 -> ../../bcache3 ubuntu@ubuntu:~$ ls -al /dev/bcache/by-label/ total 0 drwxr-xr-x 2 root root 120 Mar 19 18:32 . drwxr-xr-x 4 root root 80 Mar 19 18:32 .. lrwxrwxrwx 1 root root 13 Mar 19 18:32 backing-sdb -> ../../bcache1 lrwxrwxrwx 1 root root 13 Mar 19 18:32 backing-sdd -> ../../bcache0 lrwxrwxrwx 1 root root 13 Mar 19 18:32 backing-sde -> ../../bcache3 lrwxrwxrwx 1 root root 13 Mar 19 18:32 backing-sdf -> ../../bcache2 ubuntu@ubuntu:~$ ls -al /dev/bcache/by-label/backing-sdb lrwxrwxrwx 1 root root 13 Mar 19 18:32 /dev/bcache/by-label/backing-sdb -> ../../bcache1 ubuntu@ubuntu:~$ ls -al /sys/class/block/bcache1/slaves/ total 0 drwxr-xr-x 2 root root 0 Mar 19 18:36 . drwxr-xr-x 8 root root 0 Mar 19 18:36 .. lrwxrwxrwx 1 root root 0 Mar 19 18:36 sda -> ../../../../pci:00/:00:04.0/virtio1/host2/target2:0:0/2:0:0:0/block/sda lrwxrwxrwx 1 root root 0 Mar 19 18:36 sdb -> ../../../../pci:00/:00:04.0/virtio1/host2/target2:0:1/2:0:1:0/block/sdb ubuntu@ubuntu:~$ ls -al /dev/bcache/by-label/backing-sdd lrwxrwxrwx 1 root root 13 Mar 19 18:32 /dev/bcache/by-label/backing-sdd -> ../../bcache0 ubuntu@ubuntu:~$ ls -al /sys/class/block/bcache0/slaves/ total 0 drwxr-xr-x 2 root root 0 Mar 19 18:36 . drwxr-xr-x 8 root root 0 Mar 19 18:36 .. lrwxrwxrwx 1 root root 0 Mar 19 18:36 sda -> ../../../../pci:00/:00:04.0/virtio1/host2/target2:0:0/2:0:0:0/block/sda lrwxrwxrwx 1 root root 0 Mar 19 18:36 sdd -> ../../../../pci:00/:00:04.0/virtio1/host2/target2:0:3/2:0:3:0/block/sdd ubuntu@ubuntu:~$ ls -al /dev/bcache/by-label/backing-sde lrwxrwxrwx 1 root root 13 Mar 19 18:32 /dev/bcache/by-label/backing-sde -> ../../bcache3 ubuntu@ubuntu:~$ ls -al /sys/class/block/bcache3/slaves/ total 0 drwxr-xr-x 2 root root 0 Mar 19 18:36 . drwxr-xr-x 8 root root 0 Mar 19 18:36 .. lrwxrwxrwx 1 root root 0 Mar 19 18:36 sdc -> ../../../../pci:00/:00:04.0/virtio1/host2/target2:0:2/2:0:2:0/block/sdc lrwxrwxrwx 1 root root 0 Mar 19 18:36 sde -> ../../../../pci:00/:00:04.0/virtio1/host2/target2:0:4/2:0:4:0/block/sde ubuntu@ubuntu:~$ ls -al /dev/bcache/by-label/backing-sdf lrwxrwxrwx 1 root root 13 Mar 19 18:32 /dev/bcache/by-label/backing-sdf -> ../../bcache2 ubuntu@ubuntu:~$ ls -al /sys/class/block/bcache2/slaves/ total 0 drwxr-xr-x 2 root root 0 Mar 19 18:37 . drwxr-xr-x 8 root root 0 Mar 19 18:32 .. lrwxrwxrwx 1 root root 0 Mar 19 18:37 sdc -> ../../../../pci:00/:00:04.0/virtio1/host2/target2:0:2/2:0:2:0/block/sdc lrwxrwxrwx 1 root root 0 Mar 19 18:37 sdf -> ../../../../pci:00/:00:04.0/virtio1/host2/target2:0:5/2:0:5:0/block/sdf $ dmesg | grep bcache [1.210989] bcache: register_bdev() registered backing device sdd [1.214956] bcache: bch_journal_replay() journal replay done, 0 keys in 2 entries, seq 9 [1.216142] bcache: register_cache() registered cache device sdc [1.216436] bcache: register_bdev() registered backing device sdb [1.220348] bcache: bch_journal_replay() journal replay done, 0 keys in 2 entries, seq 9 [1.233925] bcache: bch_cached_dev_attach() Caching sdb as bcache1 on set 0dbdcc17-7af0-4318-bd57-bbdf5c7f1bfa [1.270172] bcache: bch_cached_dev_attach() Caching sdd as bcache0 on set 0dbdcc17-7af0-4318-bd57-bbdf5c7f1bfa [1.272236] bcache: register_c
[Kernel-packages] [Bug 1685723] Re: [Feature] GLK/CNL:eMMC 5.1 support
This is a huge series that affects a lot of users out there as it changes lots of common MMC code. We should target 18.10 for that. Cascardo. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1685723 Title: [Feature] GLK/CNL:eMMC 5.1 support Status in intel: New Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: CNL will have eMMC5.1 capable host controller that includes new features: 1) Command queue support – making the data transfers highly efficient by offloading the software overhead into the controller. 2) eMMC 5.1 further improves the reliability of operation by utilizing an “enhanced strobe” at the PHY layer. The eMMC5.1 is backward compatible with the existing eMMC 4.51 and eMMC 5.0 Devices. Target Kernel:4.16 Target Release: 18.04 Target Platform: GLK/CNL To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1685723/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1755219] Re: linux-kvm: 4.4.0-1020.25 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1755219 Title: linux-kvm: 4.4.0-1020.25 -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 promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1755208 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/1755219/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1729145] Re: /dev/bcache/by-uuid links not created after reboot
Not sure if this was supposed to also be fixed in bionic-proposed yet, but I assumed so and it's not working there; I'll test -proposed in artful and xenial next. ubuntu@ubuntu:~$ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu Bionic Beaver (development branch)" ubuntu@ubuntu:~$ uname -a Linux ubuntu 4.15.0-13-generic #14-Ubuntu SMP Sat Mar 17 13:44:27 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux ubuntu@ubuntu:~$ apt-cache policy linux-image-virtual linux-image-virtual: Installed: 4.15.0.13.14 Candidate: 4.15.0.13.14 Version table: *** 4.15.0.13.14 500 500 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 Packages 100 /var/lib/dpkg/status 4.15.0.12.13 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages ubuntu@ubuntu:~$ uname -a Linux ubuntu 4.15.0-13-generic #14-Ubuntu SMP Sat Mar 17 13:44:27 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux ubuntu@ubuntu:~$ ls -al /dev/bcache* brw-rw 1 root disk 251, 0 Mar 19 18:09 /dev/bcache0 brw-rw 1 root disk 251, 128 Mar 19 18:09 /dev/bcache1 brw-rw 1 root disk 251, 256 Mar 19 18:09 /dev/bcache2 brw-rw 1 root disk 251, 384 Mar 19 18:09 /dev/bcache3 ubuntu@ubuntu:~$ dmesg | grep bcache [1.005037] bcache: register_bdev() registered backing device sdb [1.011078] bcache: bch_journal_replay() journal replay done, 0 keys in 1 entries, seq 5 [1.023834] bcache: bch_cached_dev_attach() Caching sdb as bcache0 on set 0dbdcc17-7af0-4318-bd57-bbdf5c7f1bfa [1.029237] bcache: register_cache() registered cache device sda [1.029555] bcache: register_bdev() registered backing device sdd [1.050543] bcache: bch_cached_dev_attach() Caching sdd as bcache1 on set 0dbdcc17-7af0-4318-bd57-bbdf5c7f1bfa [1.052124] bcache: register_bdev() registered backing device sde [1.054044] bcache: register_bdev() registered backing device sdf [1.058398] bcache: bch_journal_replay() journal replay done, 0 keys in 1 entries, seq 5 [1.068618] bcache: bch_cached_dev_attach() Caching sdf as bcache3 on set d36b419d-a49d-42e2-95af-710138a20700 [1.070652] bcache: bch_cached_dev_attach() Caching sde as bcache2 on set d36b419d-a49d-42e2-95af-710138a20700 [1.076326] bcache: register_cache() registered cache device sdc [4.090280] bcache: register_bcache() error /dev/sdc: device already registered [4.091070] bcache: register_bcache() error /dev/sdd: device already registered [4.094397] bcache: register_bcache() error /dev/sde: device already registered [4.095253] bcache: register_bcache() error /dev/sda: device already registered [4.103178] bcache: register_bcache() error /dev/sdb: device already registered [4.115378] bcache: register_bcache() error /dev/sdf: device already registered On Mon, Mar 19, 2018 at 5:56 AM, Stefan Bader wrote: > 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- > artful' to 'verification-done-artful'. If the problem still exists, > change the tag 'verification-needed-artful' to 'verification-failed- > artful'. > > 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 subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1729145 > > Title: > /dev/bcache/by-uuid links not created after reboot > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729145/+subscriptions -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1729145 Title: /dev/bcache/by-uuid links not created after reboot Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: Fix Committed Status in linux source package in Zesty: Won't Fix Status in linux source package in Artful: Fix Committed Status in linux source package in Bionic: In Progress Bug description: 1. $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 2. $ apt-cache policy linux-image-`uname -r` linux-image-4.13.0-16-generic: Installed: 4.13.0-16.19 Candidate: 4.13.0-16.19 Version table: *** 4.13.0-16.19 500 500 http://nova.clouds.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status 3. After creating some bcache devices and rebooting /dev/bcache/by-uuid/ -> ../../bcacheN symlinks point to the current bcache device which is caching the dev.uuid found after creating a backing device. 4. /dev/bcache/by-uuid does not exist and there are not s
[Kernel-packages] [Bug 1756963] [NEW] /sys/module//sections/.text is now 0400 instead of 0444
Public bug reported: When running the kernel security tests from qa-regression-testing, it fails to run 'sudo -u cat /sys/module//sections/.text', because it's now only owner-readable, instead of world-readable. The failure is copied below. This has been changes on 4.15-rc1 by commit 277642dcca765a1955d4c753a5a315ff7f2eb09d ("modules: make sysfs attribute files readable by owner only"). We either want to revert that upstream or fix the test. == FAIL: test_095_kernel_symbols_missing (__main__.KernelSecurityTest) kernel addresses in kallsyms and modules are zeroed out -- Traceback (most recent call last): File "./test-kernel-security.py", line 1508, in test_095_kernel_symbols_missing self._check_pK_files(expected) File "./test-kernel-security.py", line 1449, in _check_pK_files expected) File "./test-kernel-security.py", line 1387, in _read_twice self.assertEqual(rc, 0, regular) AssertionError: cat: /sys/module/virtio_blk/sections/.text: Permission denied -- Ran 76 tests in 22.227s FAILED (failures=1) END ERROR ubuntu_qrt_kernel_security.test-kernel-security.py ubuntu_qrt_kernel_security.test-kernel-security.py timestamp=1521472107 localtime=Mar 19 15:08:27 ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Confirmed ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1756963 Title: /sys/module//sections/.text is now 0400 instead of 0444 Status in linux package in Ubuntu: Confirmed Bug description: When running the kernel security tests from qa-regression-testing, it fails to run 'sudo -u cat /sys/module//sections/.text', because it's now only owner- readable, instead of world-readable. The failure is copied below. This has been changes on 4.15-rc1 by commit 277642dcca765a1955d4c753a5a315ff7f2eb09d ("modules: make sysfs attribute files readable by owner only"). We either want to revert that upstream or fix the test. == FAIL: test_095_kernel_symbols_missing (__main__.KernelSecurityTest) kernel addresses in kallsyms and modules are zeroed out -- Traceback (most recent call last): File "./test-kernel-security.py", line 1508, in test_095_kernel_symbols_missing self._check_pK_files(expected) File "./test-kernel-security.py", line 1449, in _check_pK_files expected) File "./test-kernel-security.py", line 1387, in _read_twice self.assertEqual(rc, 0, regular) AssertionError: cat: /sys/module/virtio_blk/sections/.text: Permission denied -- Ran 76 tests in 22.227s FAILED (failures=1) END ERROR ubuntu_qrt_kernel_security.test-kernel-security.py ubuntu_qrt_kernel_security.test-kernel-security.py timestamp=1521472107 localtime=Mar 19 15:08:27 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1756963/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1756941] Re: linux-kvm: 4.15.0-1002.2 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-bionic ** Tags added: block-proposed ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Kamal Mostafa (kamalmostafa) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => Confirmed ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Kamal Mostafa (kamalmostafa) ** Description changed: This bug is for tracking the 4.15.0-1002.2 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 -- kernel-master-bug: 1751285 + kernel-phase-changed:Monday, 19. March 2018 17:45 UTC + kernel-phase:Uploaded ** Description changed: This bug is for tracking the 4.15.0-1002.2 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- + boot-testing-requested: true kernel-master-bug: 1751285 - kernel-phase-changed:Monday, 19. March 2018 17:45 UTC - kernel-phase:Uploaded + phase: Uploaded -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1756941 Title: linux-kvm: 4.15.0-1002.2 -proposed tracker Status in Kernel SRU Workflow: Fix Released Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-release series: Fix Released Status in Kernel SRU Workflow regression-testing series: New Status in linux-kvm package in Ubuntu: Confirmed Status in linux-kvm source package in Bionic: Confirmed Bug description: This bug is for tracking the 4.15.0-1002.2 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-master-bug: 1751285 phase: Released To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1756941/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1756941] Re: linux-kvm: 4.15.0-1002.2 -proposed tracker
** Changed in: kernel-sru-workflow Status: Fix Released => In Progress ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Released => New ** Changed in: kernel-sru-workflow/prepare-package Assignee: Kamal Mostafa (kamalmostafa) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Released => New ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Kamal Mostafa (kamalmostafa) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Released => New ** Changed in: kernel-sru-workflow/promote-to-release Status: Fix Released => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1756941 Title: linux-kvm: 4.15.0-1002.2 -proposed tracker Status in Kernel SRU Workflow: Invalid Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Invalid Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-release series: Invalid Status in Kernel SRU Workflow regression-testing series: Invalid Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Bionic: Invalid Bug description: This bug is for tracking the 4.15.0-1002.2 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-master-bug: 1751285 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1756941/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1755219] Re: linux-kvm: 4.4.0-1020.25 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/certification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => Fix Released ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1755208 phase: Uploaded + kernel-stable-phase:Promoted to proposed + kernel-stable-phase-changed:Monday, 19. March 2018 18:01 UTC ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1755208 - phase: Uploaded - kernel-stable-phase:Promoted to proposed - kernel-stable-phase-changed:Monday, 19. March 2018 18:01 UTC + phase: Promoted to proposed + proposed-announcement-sent: true + proposed-testing-requested: true -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1755219 Title: linux-kvm: 4.4.0-1020.25 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: 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 promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1755208 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/1755219/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1748408] Re: Servers going OOM after updating kernel from 4.10 to 4.13
Running the -proposed kernel on two machines now, will provide the results in a couple of days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1748408 Title: Servers going OOM after updating kernel from 4.10 to 4.13 Status in linux package in Ubuntu: Fix Committed Status in linux source package in Artful: Fix Committed Bug description: == SRU Justification == We are seeing this on multiple servers after upgrading from previous 4.10 series HWE kernels to the new 4.13 HWE series. With the new kernel, free memory is continously decreasing at a high rate and the servers start swapping and finally OOMing services within days. With the 4.10 kernel, decrease of free memory is slower and stabilizes after a while. Latest kernel tested is linux-image-4.13.0-32-generic but the issue also affects older kernels from that series, tested back to linux- image-4.13.0-19-generic. No issue with linux-image-4.10.0-42-generic. The servers are running as OpenStack controller nodes using either Ocata or Pike UCA plus ceph. See attached graph for the memory behaviour. == Fix == 2b9478ffc550("i40e: Fix memory leak related filter programming status") 62b4c6694dfd("i40e: Add programming descriptors to cleaned_count") == Regression Potential == Low. Limited to i40e and fix existing regression. == Test Case == A test kernel was built with these patches and tested by the original bug reporter. The bug reporter states the test kernel resolved the bug. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1 ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Fri Feb 9 09:45:50 2018 ProcEnviron: LANGUAGE=en_US: TERM=screen PATH=(custom, no user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748408/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1756941] [NEW] linux-kvm: 4.15.0-1002.2 -proposed tracker
Public bug reported: This bug is for tracking the 4.15.0-1002.2 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-master-bug: 1751285 phase: Released ** Affects: kernel-sru-workflow Importance: Medium Status: Fix Released ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Kamal Mostafa (kamalmostafa) Status: Fix Released ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Kamal Mostafa (kamalmostafa) Status: Fix Released ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Fix Released ** Affects: kernel-sru-workflow/promote-to-release Importance: Medium Assignee: Ubuntu Package Archive Administrators (ubuntu-archive) Status: Fix Released ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux-kvm (Ubuntu) Importance: Medium Status: Confirmed ** Affects: linux-kvm (Ubuntu Bionic) Importance: Medium Status: Confirmed ** Tags: bionic kernel-release-tracking-bug ** Tags added: kernel-release-tracking-bug ** Tags added: kernel-release-tracking-bug-live ** Also affects: linux-kvm (Ubuntu Bionic) Importance: Undecided Status: New ** Tags added: bionic ** Changed in: linux-kvm (Ubuntu Bionic) Status: New => Confirmed ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-release Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-proposed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-release Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-release Assignee: (unassigned) => Ubuntu Package Archive Administrators (ubuntu-archive) ** Changed in: kernel-sru-workflow/regression-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/regression-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: linux-kvm (Ubuntu) Importance: Undecided => Medium ** Changed in: kernel-sru-workflow Status: New => In Progress ** Changed in: kernel-sru-workflow Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1756941 Title: linux-kvm: 4.15.0-1002.2 -proposed tracker Status in Kernel SRU Workflow: Fix Released Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-release series: Fix Released Status in Kernel SRU Workflow regression-testing series: New Status in linux-kvm package in Ubuntu: Confirmed Status in linux-kvm source package in Bionic: Confirmed Bug description: This bug is for tracking the 4.15.0-1002.2 upload package. This bug will contain status and testing results related to that
[Kernel-packages] [Bug 1756254] Re: Ubuntu18.04[P9 DD2.2 Boston]:Unable to boot power8 compat mode guests(ubuntu14.04.5) (kvm)
** Tags added: triage-g -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1756254 Title: Ubuntu18.04[P9 DD2.2 Boston]:Unable to boot power8 compat mode guests(ubuntu14.04.5) (kvm) Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: == Comment: #0 - Praveen K. Pandey - 2018-03-15 03:18:46 == Problem Description : As Ubuntu18.04 as KVM Host installation of ubuntu ubuntu14.04.5 kvm guest is hung to so not able to install using virt-install command Reproducible Step: 1- Install ubuntu18.04 on Boston DD2.2 2- Configure system as KVM host 3- get ubuntu-14.04.5-server-ppc64el iso 4- start installation using virt-install using ubuntu-14.04.5 iso LOG: OF stdout device is: /vdevice/vty@3000 Preparing to boot Linux version 4.4.0-31-generic (buildd@bos01-ppc64el-007) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #50~14.04.1-Ubuntu SMP Wed Jul 13 01:03:56 UTC 2016 (Ubuntu 4.4.0-31.50~14.04.1-generic 4.4.13) Detected machine type: 0101 Max number of cores passed to firmware: 2048 (NR_CPUS = 2048) Calling ibm,client-architecture-support... - it hung here -- root@system :/var/lib/libvirt/images/praveen# uname -a Linux system4.15.0-12-generic #13-Ubuntu SMP Wed Mar 7 21:37:03 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux root@lsystem:/var/lib/libvirt/images/praveen# root@system:/var/lib/libvirt/images/praveen# qemu-img create -f qcow2 pra-ubuntu14.qcow2 30G Formatting 'pra-ubuntu14.qcow2', fmt=qcow2 size=32212254720 cluster_size=65536 lazy_refcounts=off refcount_bits=16 root@system:/var/lib/libvirt/images/praveen# virt-install --name PRA-1404.5_vm1 --ram 2048 --disk path=/var/lib/libvirt/images/praveen/pra-ubuntu14.qcow2 --vcpus 4 --os-type linux --os-variant generic --network bridge=virbr0 --graphics none --console pty,target_type=serial --cdrom /var/lib/libvirt/images/isos/ubuntu-14.04.5-server-ppc64el.iso WARNING CDROM media does not print to the text console by default, so you likely will not see text install output. You might want to use --location. See the man page for examples of using --location with CDROM media Starting install... Connected to domain PRA-1404.5_vm1 Escape character is ^] Populating /vdevice methods Populating /vdevice/vty@3000 Populating /vdevice/nvram@7100 Populating /pci@8002000 00 0800 (D) : 1af4 1000virtio [ net ] 00 1000 (D) : 1af4 1004virtio [ scsi ] Populating /pci@8002000/scsi@2 SCSI: Looking for devices 100 CD-ROM : "QEMU QEMU CD-ROM 2.5+" 00 1800 (D) : 1b36 000dserial bus [ usb-xhci ] 00 2000 (D) : 1af4 1001virtio [ block ] 00 2800 (D) : 1af4 1002unknown-legacy-device* No NVRAM common partition, re-initializing... Scanning USB XHCI: Initializing Using default console: /vdevice/vty@3000 Welcome to Open Firmware Copyright (c) 2004, 2017 IBM Corporation All rights reserved. This program and the accompanying materials are made available under the terms of the BSD License available at http://www.opensource.org/licenses/bsd-license.php Trying to load: from: /pci@8002000/scsi@2/disk@100 ... Successfully loaded GNU GRUB version 2.02~beta2-9ubuntu1.11 |*Install | Press enter to boot the selected OS, `e' to edit the commands before booting or `c' for a command-line. OF stdout device is: /vdevice/vty@3000 Preparing to boot Linux version 4.4.0-31-generic (buildd@bos01-ppc64el-007) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #50~14.04.1-Ubuntu SMP Wed Jul 13 01:03:56 UTC 2016 (Ubuntu 4.4.0-31.50~14.04.1-generic 4.4.13) Detected machine type: 0101 Max number of cores passed to firmware: 2048 (NR_CPUS = 2048) Calling ibm,client-architecture-support... Regards Praveen == Comment: #1 -
[Kernel-packages] [Bug 1673250] Re: Internal HUAWEI Mobile Broadband Module not showing up as USB device
There is a solution/workaround for the Acer Trabelmate P648 (successor of the P645, possibly with the same / similar modem) in comment https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1735981/comments/8 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1673250 Title: Internal HUAWEI Mobile Broadband Module not showing up as USB device Status in linux package in Ubuntu: Expired Bug description: Hi, I am running an Acer P645 with internal USB UMTS modem. The modem works using a 16.04.1 live USB stick, but not on the installed on-disk 16.04.2. Below is the lsusb -v in from the live-USB where the UMTS modem works, first the USB Hub usb2, then the Huawei device. The information from the running system where the modem does not show up is attached through apport. I also have access to dmesg on both systems, see further below for the successful case. I also tried to copy kernel and modules from the live-USB to the hadr disk, booted successfully, but still nothing in lsusb. I also tried a few times to use for i in /sys/bus/pci/drivers/[uoex]hci_hcd/*:*; do echo "${i##*/}" > "${i%/*}/unbind" echo "${i##*/}" > "${i%/*}/bind" done for resetting the bus, still the same. I would welcome some suggestions what to test, if there could be a firmware issue blocking the UMTS, if teh modem could be blacklisted (how do I check that ?) whether udev or systemd could be a problem, whether there could be a missing package in the HDD installation (which?!) or if UEFI in the boot chain ("sdhci: Secure Digital Host Controller Interface driver") could cause an issue. Or if it makes sense to manually run usb_modeswitch (how?) without the device even be in lsusb ? Yours, Steffen Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass9 Hub bDeviceSubClass 0 Unused bDeviceProtocol 1 Single TT bMaxPacketSize064 idVendor 0x1d6b Linux Foundation idProduct 0x0002 2.0 root hub bcdDevice4.04 iManufacturer 3 Linux 4.4.0-31-generic xhci-hcd iProduct2 xHCI Host Controller iSerial 1 :00:14.0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 25 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower0mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 Hub bInterfaceSubClass 0 Unused bInterfaceProtocol 0 Full speed (or root) hub iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0004 1x 4 bytes bInterval 12 Hub Descriptor: bLength 11 bDescriptorType 41 nNbrPorts 9 wHubCharacteristic 0x000a No power switching (usb 1.0) Per-port overcurrent protection TT think time 8 FS bits bPwrOn2PwrGood 10 * 2 milli seconds bHubContrCurrent 0 milli Ampere DeviceRemovable0x88 0x00 PortPwrCtrlMask0xff 0xff Hub Port Status: Port 1: .0503 highspeed power enable connect Port 2: .0100 power Port 3: .0100 power Port 4: .0100 power Port 5: .0503 highspeed power enable connect Port 6: .0503 highspeed power enable connect Port 7: .0103 power enable connect Port 8: .0103 power enable connect Port 9: .0100 power Device Status: 0x0001 Self Powered Bus 002 Device 006: ID 12d1:1570 Huawei Technologies Co., Ltd. Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 255 Vendor Specific Class bDeviceSubClass 2 bDeviceProtocol 1 bMaxPacketSize064 idVendor 0x12d1 Huawei Technologies Co., Ltd. idProduct 0x1570 bcdDevice0.01 iManufacturer 5 Huawei Technologies Co., Ltd. iProduct
[Kernel-packages] [Bug 1755268] Re: Kernel panic when using KVM and Mellanox OFED driver (bonding and sriov enabled)
Hi Joseph, thanks for your answer. Currnetly I have two various hardware configuration: - HPE ProLiant m710p Server Cartridge (have no this problem) - HPE ProLiant m710x Server Cartridge (have this problem) > Did this issue start happening after an update/upgrade? > Was there a prior kernel version where you were not having this particular > problem? Well, I uses debootstrap script for install all needed software automatically and build image with base system. After that I uses this image for boot my nodes via PXE. So each boot I have system that installed from scratch. I've tested the next kernels: - Ubuntu 16.04 with stock kernel: 4.4.0-116-generic - Ubuntu 16.04 with hwe kernel: 4.13.0-36-generic - Ubuntu 16.04 with pve kernel: 4.13.13-6-pve - Debian 9 with pve kernel: 4.13.13-6-pve - Debian 9 with stock kernel: 4.9.0-6-amd64 All of them have this problem, but stock kernels can drops after some time. (I had no this error only on debian with 4.9.0-6-amd64 but presume it exists there because I'm not tested it properly) Another thing, that if I do this steps AFTER the system is boot up: rmmod mlx4_en mlx4_ib mlx4_core modprobe mlx4_core num_vfs=1 port_type_array=2,2 probe_vf=1 systemctl restart networking Everything starts working fine. > Please test the latest v4.16 kernel[0]. Ok, I'll do this -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1755268 Title: Kernel panic when using KVM and Mellanox OFED driver (bonding and sriov enabled) Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Incomplete Status in linux source package in Artful: Incomplete Bug description: # System information # # uname -a Linux m5c37 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux # cat /etc/os-release NAME="Ubuntu" VERSION="16.04.4 LTS (Xenial Xerus)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 16.04.4 LTS" VERSION_ID="16.04" HOME_URL="http://www.ubuntu.com/"; SUPPORT_URL="http://help.ubuntu.com/"; BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"; VERSION_CODENAME=xenial UBUNTU_CODENAME=xenial # ethtool -i eno1 driver: mlx4_en version: 4.3-1.0.1 firmware-version: 2.42.5004 expansion-rom-version: bus-info: :11:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: no supports-register-dump: no supports-priv-flags: yes # ethtool -i bond0 driver: bonding version: 3.7.1 firmware-version: 2 expansion-rom-version: bus-info: supports-statistics: no supports-test: no supports-eeprom-access: no supports-register-dump: no supports-priv-flags: no # ethtool -i vmbr0 driver: bridge version: 2.3 firmware-version: N/A expansion-rom-version: bus-info: N/A supports-statistics: no supports-test: no supports-eeprom-access: no supports-register-dump: no supports-priv-flags: no Mellanox driver was installed from http://content.mellanox.com/ofed/MLNX_OFED-4.3-1.0.1.0/MLNX_OFED_LINUX-4.3-1.0.1.0-ubuntu16.04-x86_64.tgz ./mlnxofedinstall --kernel 4.13.0-36-generic --without-dkms --add- kernel-support # Steps for reproduce # This is my /etc/network/interfaces file: auto lo iface lo inet loopback auto openibd iface openibd inet manual pre-up /etc/init.d/openibd start pre-down /etc/init.d/openibd force-stop auto bond0 iface bond0 inet manual pre-up ip link add bond0 type bond || true pre-up ip link set bond0 down pre-up ip link set bond0 type bond mode active-backup arp_interval 2000 arp_ip_target 10.36.0.1 arp_validate 3 primary eno1 pre-up ip link set eno1 down pre-up ip link set eno1d1 down pre-up ip link set eno1 master bond0 pre-up ip link set eno1d1 master bond0 pre-up ip link set bond0 up pre-down ip link del bond0 auto vmbr0 iface vmbr0 inet static address 10.36.128.217 netmask 255.255.0.0 gateway 10.36.0.1 bridge_ports bond0 bridge_stp off bridge_fd 0 I execute these commands: wget http://dl-cdn.alpinelinux.org/alpine/v3.7/releases/x86_64/alpine-virt-3.7.0-x86_64.iso -O alpine.iso qemu-system-x86_64 -boot d -cdrom alpine.iso -m 512 -nographic -device e1000,netdev=net0 -netdev tap,id=net0 And after few moments I have hang kernel, and theese messages in console: [74390.187908] mlx4_core :11:00.0: bond for multifunction failed [74390.486476] m